R1.

0_HNB_TEST_STRATEGY for
CELL_FACH

Ranjeet B Taloskar

www.ccpu.com Confidential and Proprietary 1

 Feature Description

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:

v 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.

v 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.

www.ccpu.com Confidential and Proprietary 2

 Feature Requirements

FSRS:
FSRS_Cell_FACH_v1-0-0_Compliance

# Complied Requirements : 26
# Non Complied Requirement : 0

www.ccpu.com Confidential and Proprietary 3

 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

www.ccpu.com Confidential and Proprietary 4

 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.)

www.ccpu.com Confidential and Proprietary 5

 Test Coverage
1. Use case scenarios similar to verify Customer deployment environment

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

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

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

1. MultiRAB feature is cross functional Feature for cellfach

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

www.ccpu.com Confidential and Proprietary 6

 CCPU Lab Diagram-1
IPerf

HNB
CNE simulator ( HNBGW+CN simulator )
10.204.1.3

L3 SWITCH

BANK
OF
UEs 10.204.1.1

LAB PC (Window XP)

FTP,HTTP
SERVER (Linux box)
Lab Laptop 2

www.ccpu.com Confidential and Proprietary 7

 CCPU Lab Diagram-2
IPerf

HNB
10.204.1.3
G35 simulator ( HNBGW+CN simulator )
L3 SWITCH

BANK
OF
UEs 10.204.1.1

LAB PC (Window XP) for

FTP,HTTP
1) logs collection
SERVER (Linux box)
2) QXDM Logs
Lab Laptop 2

www.ccpu.com Confidential and Proprietary 8

 Lab Diagram
IPerf

CNE simulator (Sec-Gw+ HNBGW+CN

FEMTO 1 IP CCPU Firewall with single port open for simulator
FEMTO 1 after NAT Public IP
192.168.1.2 122.166.x.x
DSL Modem

L3 SWITCH
ISP / Public
Internet
G35 simulator ( HNBGW+CN simulator )
BANK
OF 10.204.1.1
UEs
IP mapping at
Firewall

LAB PC (Window XP)

FTP,HTTP
SERVER (Linux box)

www.ccpu.com Confidential and Proprietary 9

 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

www.ccpu.com Confidential and Proprietary 10

 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.

www.ccpu.com Confidential and Proprietary 11

 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

www.ccpu.com Confidential and Proprietary 12

 Risk Factors

Sl.No Details Occurrence Severity Category Mitigation Plan

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

UE which support SMS on PS with H H Risks Cell_fach feature wont work as defined in specs
paging type 2 need to be tested
2

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

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

www.ccpu.com Confidential and Proprietary 13

 Thank You

www.ccpu.com Confidential and Proprietary 14