www.ccpu.com Confidential and Proprietary

R1.0_HNB_TEST_STRATEGY forCELL_FACH

Ranjeet B Taloskar

2www.ccpu.com Confidential and Proprietary

This feature is a means to more efficiently handle UEs which are camped or attempting to camp on the HNB cell. The feature is intended to address the following situations:

Currently UEs attempting any registration procedures with the HNB are directed to the CELL_DCH state for the signalling exchange. This presents an issue if the maximum number of CELL_DCH users has been reached. CELL_FACH provides a means for the UE to register without needing to move the UE into the CELL_DCH state.

Currently a UE requiring any data transfer is directed to the CELL_DCH state. For many smart phone use cases the exchange of data is often bursty in nature. Implementing the CELL_FACH state allows the HNB to drop UEs back to the CELL_FACH state when data volumes are low. This optimizes the number of UEs which can use the CELL_DCH state.

Feature Description

3www.ccpu.com Confidential and Proprietary

Feature Requirements

FSRS: FSRS_Cell_FACH_v1-0-0_Compliance

# Complied Requirements : 26

# Non Complied Requirement : 0

4www.ccpu.com Confidential and Proprietary

Generic Approach

QA (SIT) will monitor and consider all related feature FSRS/UTP/SIT TP reviews/results strictly.

Deployment testing and HSM usage (O&M) will be a Low priority for Phase1 (Upgrade/Configuration/Reboot/Alarms/Logs)-Attempt for Zero CLI/Console usage.

Femto setups used will run overnight and never be rebooted unless otherwise manually triggered.

(Find RCA if any issues)

Code changes during mid of TS-TF/TF-TD will be held accountable.

Basic feature sanity regression on related areas will be run by tester on every nightly builds depending on Code changes due to bug fixes or due to new features introduced to verify any broken functionality.

Write new cases for CRs with non associated cases or any generic bug fixes at any point of Test cycle.

Defect raised during the testing will be resolve immediately by SIT/QA team

Testing Logs – HNB Logs, wire shark Traces , QXDM logs will be stored in common repository

5www.ccpu.com Confidential and Proprietary

Test Methodology All P1/P2 test cases will be verified on- HNB<->SGW<->CNE Simulator<->Iperf

Femtocell always operating with its max allowed configuration with all features enabled. (REM scan, Logging, Max Users etc.)

6www.ccpu.com Confidential and Proprietary

Test Coverage1. Use case scenarios similar to verify Customer deployment environment

2. Validate Message in call flow by using QXDM analyzing tool.

3. HSDPA,HSUPA , PS64, 128,384 should be part of this feature testing.

4. HNB regression should be cover as apart of this feature with regression suite from 1.0 release

5. MultiRAB feature is cross functional Feature for cellfach

6. This test plan covers major Cellfach functionality with different types of call models

7www.ccpu.com Confidential and Proprietary

L3 SWITCH

HNB10.204.1.3

LAB PC (Window XP)

BANK OF UEs 10.204.1.1

CNE simulator ( HNBGW+CN simulator )

Lab Laptop 2

FTP,HTTPSERVER (Linux box)

IPerf

CCPU Lab Diagram-1

8www.ccpu.com Confidential and Proprietary

L3 SWITCH

HNB10.204.1.3

LAB PC (Window XP) for 1) logs collection

2) QXDM Logs

BANK OF UEs 10.204.1.1

G35 simulator ( HNBGW+CN simulator )

Lab Laptop 2

FTP,HTTPSERVER (Linux box)

IPerf

CCPU Lab Diagram-2

9www.ccpu.com Confidential and Proprietary

FEMTO 1192.168.1.2

BANK OF UEs

DSL Modem

L3 SWITCH

10.204.1.1

IPerf

LAB PC (Window XP)

CNE simulator (Sec-Gw+ HNBGW+CN simulator

FTP,HTTPSERVER (Linux box)

Lab Diagram

ISP / PublicInternet

G35 simulator ( HNBGW+CN simulator )

CCPU Firewall with single port open for Public IP

FEMTO 1 IP after NAT

122.166.x.x

IP mapping at Firewall

10www.ccpu.com Confidential and Proprietary

Test Bed Requirements

Test Beds 2 HNB 1 Sec-GW 2 CNE Simulator (Ubuntu machine) or G35 simulator UE( Rel99 -1 , HSDPA Data cards -2 , E51 -2, E71-2) 1 Laptops QXDM dongle PC with QXDM software installed on it. IPERF to generate IP packets FTP server

11www.ccpu.com Confidential and Proprietary

Assumptions

1) CNE simulator supports traffic between two HNB , so that we can configure

UE to latch on two different HNBs

2) Pico Chip Platforms supports CLI , to enable Cell_Fach parameters

3) QXDM dongle can be used to collect air interface logs for multiple UEs

4) G35 scripts provides Iu and Iuh interface from HNB to HNB GW.

5) HNB debug level can be increased to verify the messages.

12www.ccpu.com Confidential and Proprietary

Limitations

HNB CLI is used to configure HNB Parameters. HNB LED indication has to be more robust. Macro Network simulation is done on HNB . HNB’s DSL Connectivity with HNB GW with NAT traversal device should be

working fine

13www.ccpu.com Confidential and Proprietary

Risk Factors

Sl.No Details Occurrence Severity Category Mitigation Plan

1Unavailability of G35 servers H H Risks This will delay LAB setup process

2

UE which support SMS on PS with paging type 2 need to be tested

H H Risks Cell_fach feature wont work as defined in specs

3WiFi Router or DSL connectivity M M Open Issues This will help us to simulate Customer network.

4TR069 support M M Open Issues This will help us to simulate Customer network.

5

6

7

8

14www.ccpu.com Confidential and Proprietary

Thank You