tdd lte icell iot test item v2.0

Title

TDD LTE iCell IoT Test Item

TDD

PT

Date Doc. No Checked by

21-03-2015 Comba

Proprietary & Confidential

© Comba Telecom

LTE iCell IoT Test Item

FOR

T. SMART TELECOM

Page

1 / 27

1 / 27

Title


Related Document

No. File Number

1 3GPP TS 24.008 V8.2

2 3GPP TS 24.301 9.5.0

3 3GPP TS 36.413 V9.4

Glossary

CRL Certificate Re

CSG Closed Subsc

DPD Dead Peer D

eNodeB Evolved Node

EPC Evolved Pack

FQDN Fully Qualifie

GUMMEI Globally Uniq

L-GW Local Gatewa

LIPA Local IP Acce

LTE Long Term E

MME Mobility Mana

MTU Maximum Tra

NAT-T NAT-Travers

OCSP Online Certifi

S-GW Serving Gate

SeGW Security Gate

TrE Trusted Envir


21-03-2015 Comba


© Comba Telecom

File Name

.2.0 Mobile radio interface Layer 3

specification

5.0 Non-Access-Stratum (NAS) protocol

for Evolved Packet System (EPS)

.4.0 S1 Application Protocol (S1AP)

Revocation List

scriber Group

Detection

deB

cket Core

fied Domain Name

ique MME Identifier

way

cess

Evolution

nagement Entity

ransmission Unit

rsal

tificate Status Protocol

teway

teway

vironment

Page

2 / 27

2 / 27

Comment

Title


1 Introduction ................................

2 IoT Test Topology ................................

3 Basic Test Items ................................

3.1 NAS Layer Transmis

3.1.1 UE Initiate Attach

3.1.2 UE Initiate Detac

3.1.3 TAU in ECM-IDL

3.1.4 TAU in ECM-CO

3.1.5 EPC Initiates S-T

3.1.6 UE Initiates Serv

3.2 Context Managemen

3.2.1 Establish default

3.3 E-RAB Setup Proces

3.3.1 Non GBR Setup

3.3.2 GBR Setup Succ

3.4 E-RAB Release Proc

3.4.1 MME initiates E-

3.5 IoT function Test ................................

3.5.1 Reselection betw

3.5.2 Handover Proce

3.5.3 Handover Proce

3.5.4 ICIC ................................

3.5.5 2X2 MIMO ................................

3.6 Management Functio

3.6.1 iCell initiates S1

4 Service Test ................................

4.1 Ping Test ................................

4.2 FTP Upload/Downloa

5 Handover between iCell a

6 Air Synchronization Test ................................

6.1 Air Synchronization T

6.2 ANR Test ................................

6.3 Automatic PCI Detec

6.4 RACH optimization ................................


21-03-2015 Comba


© Comba Telecom

Table of Contents

................................................................

................................................................

................................................................

ission ..........................................................

chment Procedure ................................

achment Procedure ................................

LE state .......................................................

ONNECTED state ................................

TMSI paging ................................

rvice Request ................................

nt .............................................................

ult EPS bearer, UE context setup succeed. ..........................

ess ...........................................................

p Success .....................................................

ccess .........................................................

ocess .........................................................

-RAB Release Process ................................

................................................................

tween iCell and Macro Cell ................................

ess between iCells Based on S1 Interface .........................

ess between iCells Based on X2 Interface .........................

................................................................

................................................................

tion ...........................................................

1 Setup .......................................................

................................................................

................................................................

oad Service ................................

l and Macro based on X2 interface ................................

..............................................................

Test ..........................................................

................................................................

ction and assignment ................................

..............................................................

Page

2 / 27

2 / 27

.......................................... 1

.................................... 1

..................................... 1

.......................... 1

............................................... 1

.............................................. 3

....................... 4

............................................... 5

................................................... 6

................................................... 7

............................. 8

.......................... 8

........................... 10

..................... 10

......................... 11

......................... 12

......................................... 12

................................ 13

...................................... 13

......................... 14

......................... 18

....................................... 18

................................. 19

........................... 20

....................... 20

........................................ 20

....................................... 21

.................................................... 21

................................ 21

.............................. 22

.......................... 22

....................................... 23

........................................... 24

.............................. 24

Title Date Doc. No Checked by Page

TDD LTE iCell IoT Test Item 21-03-2015 Comba 1 / 27

1

1 Introduction

This document introduces TDD LTE iCell IoT test items and testing procedure.

2 IoT Test Topology

IoT test topology is showed in the figure below:

-*One layer 3 switch is suggested to deploy between iCell and EPC for the

signaling capture.

Reference types of switch are H3C S5500, Huawei 5300 or Cisco 3560.

3 Basic Test Items

3.1 NAS Layer Transmission

3.1.1 UE Initiate Attachment Procedure

Test item UE initiate attachment process

Reference 3GPP TS 36.412/36.331

Test Condition

1. iCell connects to MME via S1-MME interface

2. UE resides in the Cell A under iCell1 coverage.

3. UE is in EMM_EMM_DEREGISTERED state

Test Procedure



2

Expected Result

1. iCell sends INITIAL UE MESSAGE to MME, it includes:

a) TAI;

b) E-UTRAN CGI;

c) NAS-PDU Attach Request message;

d) RRC Establishment Cause

2. Check the INITIAL CONTEXT SETUP REQUEST message received by iCell, it

includes:

a) MME UE S1AP ID;

b) iCell UE S1AP ID;

c) UE Aggregate Maximum Bit Rate;

d) E-RAB to be Setup List:

i. E-RAB ID;

ii. E-RAB Level QoS Parameters，contains QCI 5~9(default E-RAB);

iii. Transport Layer Address;

iv. GTP-TEID;

v. NAS-PDU;

e) UE security capabilities;

f) Security Key;

g) Trace Activation(Optional);

h) Handover Restriction List(Optional);

i) UE Radio Capability(Optional);



3

j) Subscriber Profile ID for RAT/Frequency priority(Optional);

k) CS Fallback Indicator(Optional);

l) SRVCC Operation Possible(Optional);

3. After iCell receives INITIAL CONTEXT SETUP REQUEST message and succeed in

setup UE context, iCell sends INITIAL CONTEXT SETUP RESPONSE message to

MME, this message includes:

The RAB ID and transmission address of established E-RAB

4. iCell sends UPLINK NASTRANSPORT message to MME, it includes:

a) NAS-PDU NAS layer message (Such as Attach Complete);

b) E-UTRAN CGI

c) TAI

5. iCell works in normal condition during testing process, and UE succeeds in

attachment.

3.1.2 UE Initiate Detachment Procedure

Item UE initiate detachment procedure


Test Condition


2. UE resides in the Cell A under iCell1 coverage

3. UE is in EMM_REGISTERED state

4. UE is in ECM-IDLE state

5. UE initiates detachment process by powering off

Test Procedure



4

Expected Result


a) iCell UE S1AP ID;

b) TAI;

c) E-UTRAN CGI;

d) NAS-PDU Detach Request message;

e) RRC Establishment Cause;

2. iCell works in normal condition during the testing process, and then UE powers off.

3.1.3 TAU in ECM-IDLE state

Item TAU in ECM-IDLE state


Test Condition

1. iCell1 and iCell2 connect to MME via S1-MME interfaces, configure TAC1 in iCell1 for

Cell A, and configure TAC2 in iCell2 for Cell B

2. UE resides in Cell A under iCell1 coverage

3. UE is in EMM_REGISTERED state.


5. UE reselects from Cell A to Cell B, it requires EPC provide a new GUTI for UE

6. UE initiates Tracking Area Updating Request(TA in idle state causes TAU)

Test Procedure



5

Expected Result

1. iCell sends initial UE message to MME , it includes:

a. iCell UE S1AP ID;

b. TAI;

c. E-UTRAN CGI;

d. NAS-PDU: Tracking Area Updating Request message;

e. RRC Establishment Cause;

2. MME sends Downlink NAS Transport to iCell, it includes TAU Accept message;

3. iCell sends Uplink NAS Transport message to MM, it includes TAU COMPLETE

message(require GUTI modification

Comments: EPC assigns 2 TAC for iCells

3.1.4 TAU in ECM-CONNECTED state

Item TAU in ECM-CONNECTED state


Test Condition

1. iCell1 and iCell2 connect to MME via S1-MME interface, configure TAC1 in iCell1 for

Cell A, and configure TAC2 in iCell2 for Cell B, TAC1 and TAC2 are in different TA

List

2. UE resides Cell A under iCell1 coverage


4. UE is in ECM-CONNECTED state

5. UE handovers form Cell A to Cell B, in this moment Tracking Area of the Cell where

UE resides has changed.



6

6. UE initiates Tracking Area Updating Request(TAU due to TA changes in

CONNECTED state)

Test Procedure

Expected Result

1. iCell sends Uplink NAS Transport message to MME, it includes:

a) iCell UE S1AP ID

b) TAI

c) E-UTRAN CGI

d) NAS-PDU : Tracking Area Updating Request message;

2. MME sends Downlink NAS Transport to iCell, it includes TAU Accept message;

3. iCell sends Uplink NAS Transport message including TAU Complete message to

MME(iCell initiates this signaling due to GUTI changes)

3.1.5 EPC Initiates S-TMSI paging

Item EPC initiates S-TMSI paging


Test Condition

1. iCell connect to MME via S1-MME interface




5. EPC requires sending data to UE.

Test Procedure



7

Expected Result

1. MME has business request to notify UE, so it sends PAGING message to iCell, the

message includes:

a) CN Domain Indicator “PS domain”

b) UE Identity Index value

c) UE Paging Identity UE S-TMSI

d) List of TAIs (PAGING)

2. iCell sends Initial UE message, carrying NAS layer message “Service Request”

3. MME initiates context setup process, and sends “Initial Context Setup Request” to

iCell

4. iCell replies MME “Initial Context Setup Response”;

5. iCell works in normal condition during the testing process.

3.1.6 UE Initiates Service Request

Item UE initiates Service Request


Test Condition





5. UE initiates a EPS context setup process



8

Test Procedure

Expected Result


a) iCell UE S1AP ID

b) TAI

c) E-UTRAN CGI

d) NAS-PDU: Service Request message;

e) RRC Establishment Cause

2. MME initiates Initial Context Setup process and sends “Initial Context Setup Request”

to iCell

3. iCell replies “Initial Context Setup Response” to MME.


3.2 Context Management

3.2.1 Establish default EPS bearer, UE context setup succeed.

Item Establish default EPS bearer, UE context setup succeed.


Test Condition


2. UE powers on under iCell coverage, the default EPS bearer will be established in

attachment procedure.

Test Procedure:



9

Expected Result

1. iCell receives INITIAL CONTEXT SETUP REQUEST message, the message

includes the parameters which is listed below:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) UE Aggregate Maximum Bit Rate Optional

d) E-RAB to Be Setup Item

i. E-RAB ID

ii. E-RAB Level QoS Parameters，includes QCI=9(default E-RAB)

iii. Transport Layer Address

iv. GTP-TEID

v. NAS-PDU ATTACH ACCEPT (carrying ACTIVATE DEFAULT EPS

BEARER CONTEXT REQUEST)

e) UE security capabilities

f) Security Key

2. After iCell receives INITIAL CONTEXT SETUP REQUEST message and succeeds in

setup UE context, iCell sends INITIAL CONTEXT SETUP RESPONSE to MME, the

message should include:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) The setup EPS should include:

i. E-RAB ID

ii. Transport Layer Address

iii. GTP-TEID



10


3.3 E-RAB Setup Process

3.3.1 Non GBR Setup Success

Item Non GBR Setup Success


Test Condition:





5. Network initiates Dedicated EPS bearer setup.

Test procedures:

Expected Results:

1. Check E-RAB SETUP REQUEST message received by iCell, it should include the

parameters listed below:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) The items listed below are included in E-RAB to be Setup

i. E-RAB ID

ii. E-RAB Level QoS Parameters, QCI is 5(6~9), NGBR business.

iii. Transport Layer Address

iv. GTP-TEID

v. NAS-PDU



11

2. After E-RAB SETUP REQUEST is received, and E-RAB is established successfully,

iCell sends E-RAB SETUP RESPONSE message to MME, and the message

includes:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) The setup E-RAB includes:

i. E-RAB ID

ii. Transport Layer Address

iii. GTP-TEID

3. The following message and process work correctly, and uplink and downlink data

transmit correctly.

4. Reset to initial state, change QCI into 6~9(NGBR business) and repeat steps above

1~3.

3.3.2 GBR Setup Success

Item GBR Setup Success


Test Condition:





5. Network initiates Dedicated EPS bearer setup.

Test procedures:

Expected Results:



12



d) MME UE S1AP ID

e) iCell UE S1AP ID

f) The items listed below are included in E-RAB to be Setup

vi. E-RAB ID

vii. E-RAB Level QoS Parameters, QCI is 1(2~4), GBR business.

viii. Transport Layer Address

ix. GTP-TEID

x. NAS-PDU

2. After E-RAB SETUP REQUEST is received, and E-RAB is established successfully,

iCell sends E-RAB SETUP RESPONSE message to MME, and the message

includes:

d) MME UE S1AP ID

e) iCell UE S1AP ID

f) The setup E-RAB includes:

iv. E-RAB ID

v. Transport Layer Address

vi. GTP-TEID

3. The following message and process work correctly, and uplink and downlink data

transmit correctly.

4. Reset to initial state, change QCI into 2~4(GBR business) and repeat steps above

1~3.

3.4 E-RAB Release Process

3.4.1 MME initiates E-RAB Release Process

Item MME initiates E-RAB Release Process


Test Condition:



13



3. UE establishes at least one dedicated E-RAB bearer.

Test Procedures:

Expected Results



a) MME UE S1AP ID

b) iCell UE S1AP ID

c) E-RAB To Be Released List

i. E-RAB ID

ii. Cause

d) NAS-PDU carrying DEACTIVATE EPS BEARER CONTEXT REQUEST

2. After iCell receives E-RAB RELEASE COMMAND message and succeed in deleting

E-RAB, iCell sends E-RAB RELEASE RESPONSE to MME, the message should

include:

a) MME UE S1AP ID and iCell UE S1AP ID

b) Successfully released E-RAB ID

3. The message and process conform to the specification.

3.5 IoT function Test

3.5.1 Reselection between iCell and Macro Cell

Test Item:Reselction between iCell and Macro Cell



14

Test Condition:

1. iCell connect to LTE network

2. Verify iCell works normally

3. Synchronize the Cell covered by iCell and Macro Cell, configure neighboring cell

relation in iCell and Macro Cell, and configure reselection threshold, priority and

so on parameters.

Test Procedure:

1. UE registers in the Cell A under iCell coverage. UE is in IDLE state.

2. UE moves from Cell A to neighboring Macro Cell until Cell reselection occurs.

3. After reselection finished, UE tests FTP service and then stops service and return

to IDLE state.

4. UE returns from neighboring Macro Cell to Cell A until Cell reselection occurs

again.

5. After reselection finished, UE tests FTP service.

Expected Results:

1. The two times reselection succeed and the service works normally after the

reselection.

2. Check UE log via UE monitor software and reselection is triggered by the

configured reselection threshold.

Comments Neiborghing Cell relation and related parameters should be configured

both in iCell and Macro Cell. It requires macro cell configuration.

3.5.2 Handover Process between iCells Based on S1 Interface

Item Handover Process between iCells Based on S1 Interface


Test Condition:

1. Source iCell (iCell1) and Target iCell (iCell2) connect to the same MME via S1

interface.

2. Source iCell(iCell1) covers Cell A; Target iCell(iCell2) covers Cell B



15

3. UE resides in Cell A (Source iCell).

4. UE is in UE ECM_CONNECTED state and transmitting data.

5. UE moves to Cell B or adjust iCell1 and iCell2 output power to trigger UE to report

neighboring Cell measurement report.

6. Source iCell(iCell1 decide to trigger S1 Interface handover.

Test Procedure:

Source

iCell

MME

HANDOVER COMMAND

Target

iCell

HANDOVER REQUEST

HANDOVER REQUEST ACKNOWLEDGE

HANDOVER NOTIFY

eNB STATUS TRANSFER

MME STATUS TRANSFER

UE CONTEXT RELEASE

HANDOVER REQUIRED

Expected Results

1. Source iCell(iCell1) sends HANDOVER REQUIRED to MME, the message includes

the listed parameters:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) Handover type: intra LTE

d) cause

e) Target ID

f) Source to Target Transparent Container (Coding based on Source iCell to

Target iCell Transparent Container)

2. Target iCell(iCell2) receives HANDOVER REQUEST message from MME, and



16

prepare resource for this UE, this message includes:

a) MME UE S1AP ID

b) handover type: intra LTE

c) cause

d) UE Aggregate Maximum Bit Rate

e) E-RAB To Be Setup, includes E-RAB ID Transport Layer Address

GTP-TEID E-RAB Level QoS Parameters;

f) Source to Target Transparent Container :Coding based on Source iCell to

Target iCell Transparent Container;

g) UE Security capabilities

h) security Context

3. Target iCell(iCell2) finishes resource arrangement , and sends HANDOVER

REQUEST ACKNOWLEDGE to MME, this message includes the parameters listed

below:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) E-RABs Admitted List

E-RABs Admitted Item

i. E-RAB ID;

ii. Transport Layer Address;

iii. GTP-TEID;

iv. DL Transport Layer Address(Optional);

v. DL GTP-TEID(Optional，To deliver forwarded DL PDCP SDUs);

vi. UL Transport Layer Address(Optional);

vii. UL GTP-TEID(Optional, To deliver forwarded UL PDCP SDUs) etc.;

d) d. Target to Source Transparent Container : Coding based on Target iCell to

Source iCell Transparent Container;

4. Source iCell(iCell1) receives HANDOVER COMMAND message from MME, the

message includes:



17

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) Handover type: intra LTE

d) E-RABs Subject to Forwarding List(Optional)

E-RABs Subject to Forwarding Item

i. E-RAB ID

ii. DL Transport Layer Address Optional

iii. 和 DL GTP-TEID Optional，To deliver forwarded DL PDCP SDUs

iv. UL Transport Layer Address Optional

v. UL GTP-TEID Optional，To deliver forwarded UL PDCP SDUs etc.;

e) Target to Source Transparent Container: Coding based on Target iCell to

Source iCell Transparent Container;

5. Source iCell(iCell1) sends iCell STATUS TRANSFER message to MME, it includes

the following parameters :

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) iCell Status Transfer Transparent Container, including E-RABs Subject to

Status Transfer List

6. MME sends MME STATUS TRANSFER message to Target iCell iCell2 , it includes:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) iCell Status Transfer Transparent Container, including E-RABs Subject to

Status Transfer List;

7. After Target iCell (iCell2) detects that UE has handovered to this iCell, it sends

HANDOVER NOTIFY to MME for notification, this message includes:

a) MME UE S1AP ID

b) iCell UE S1AP ID

c) E-UTRAN CGI

d) TAI



18


3.5.3 Handover Process between iCells Based on X2 Interface

Item Handover between iCells based on X2 interface

Test Condition

1. Source iCell(iCell1) and Target iCell(iCell2) under test works correctly.

2. iCell synchronize with Macro Cell and configure neighboring Cell

relation ,handover threshold and so on parameters with Macro Cell

3. ICell1 connect to iCell2 with X2 interface and configure X2 related parameters.

Test Procedure

1. UE registers in iCell covered by source iCell (iCell1) and makes ftp service.

2. UE moves from the source iCell (iCell1) to target iCell (iCell2) until handover

occurs.

3. Handover finishes and check UE ftp service status

4. UE returns from iCell2 to iCell1 until handover occurs.


Expected Result:

1. The two times handover succeed and data service works correctly during

handover.

2. The handover process viewed by UE monitor software is correct and the

handover is triggered based on the configured threshold.

3. X2-AP related handover signaling caught from network works correctly.

Comments

1. It requires to configure X2 interface between iCells

2. Neighboring Cell relation and related parameters should be configured both in

iCell1 and iCell2.

3.5.4 ICIC

Test Item: ICIC



19

Test Condition:

1. iCell1 and iCell2 both have ICIC function and the function has turned off at the

begining.

2. iCell1 and iCell2 configure the same frequency spectrum, and configure PRACH

Root parameter with N*5 gaps, PCI configure without MOD3 interference. The

main carrier of two iCells set at different frequencies.

Test Procedure:

1. Power on iCell1 and UE1 is registered in iCell1. UE1 makes data service at the

edge of iCell1’s coverage, check UE1’s bler and SNR.

2. Power on iCell2 and UE2 is registered in iCell2. UE2 makes data service at the

edge of iCell2’s coverage, check UE2’s bler and SNR.

3. iCell1 and iCell2 turn on ICIC function,and set measurement and control

parameter of A2 event.

4. Repeat step1 and step 2.

Expected Results

1. The bler and SNR value with ICIC function are better than the value without ICIC

function.

3.5.5 2X2 MIMO

Item: 2X2 MIMO

Test Condition:

1. Verfity iCell support MIMO function.

Test Procedure:

1. Setup iCell1 with single antenna mode.

2. UE is registered in iCell1. Under iCell1 coverage, check UE data speed.

3. Change iCell1 into dual antenna mode. Under iCell1 coverage, check UE data

speed again..



20

Expected Results

1. The data speed in dual antenna mode is much higher than in single antenna

mode.

3.6 Management Function

3.6.1 iCell initiates S1 Setup

Item iCell initiates S1 Setup


Test Condition:

1. The transmission link between iCell and MME works normally.

2. There is at least one Cell under this MME

Test Procedure:

Expected Result:

1. iCell sends S1 SETUP REQUEST message to MME, which transports served cell list,

this message includes:

a) Global iCell ID

b) Supported TAs, including TAC，PLMN identity

c) Default Paging DRX

2. After MME received the message above, it replies S1 SETUP RESPONSE message

which includes:

a) Served GUMMEIs

b) b. Relative MME Capacity

4 Service Test



21

4.1 Ping Test

Item Ping Test


Test Condition 1.UE is attached and in ECM-CONNECTED state

2. FTP service works correctly.

Test Procedure UE ping test:

1. ping 64byte packet for 10 minutes




Expected Results 1. UE can ping normally

2. UE is in EMM-REGISTERED and ECM-CONNECTED state

4.2 FTP Upload/Download Service

Item FTP upload/download Service


Test Condition 1. UE is attached and in ECM-CONNECTED state

2. FTP service works correctly

Test Procedure UE keeps FTP uploading /downloading for long term

Expected Result 1. UE can normally upload and download.

2. UE is in EMM-REGISTERED state and ECM-CONNECTED

state

5 Handover between iCell and Macro based on X2 interface

Item Handover between iCell and Macro based on X2 interface



22

Test Condition

1. iCell under test works correctly

2. iCell synchronize with Macro Cell and configure neighboring Cell relation,

handover threshold and so on parameters with Macro Cell

3. iCell connect to Macro Cell with X2 interface and configure X2 related

parameters.

Test Procedure

1. UE registers in Cell A covered by iCell and makes ftp service.

2. UE moves from the Cell A to neighboring Macro Cell B until handover occurs.


4. UE returns from Macro Cell B to Cell A until handover occurs.


Expected Result:

1. The two times handover succeed and data service works correctly during

handover.

2. The handover process viewed by UE monitor software is correct and the

handover is triggered based on the configured threshold.

3. X2-AP related handover signaling caught from network works correctly.

Comments

1. It requires to configure X2 interface between Macro Cell and X2

2. Neighboring Cell relation and related parameters should be configured both in

iCell and Macro Cell. It requires macro cell configuration.

6 Air Synchronization Test

6.1 Air Synchronization Test

Item Air synchronization test



23

Test Condition:

1. There is TDD LTE Macro cell near the iCell under the test.

2. iCell under the test chooses air synchronization mode.

3. Neighboring Macro Cell has configured neighboring cell relation with iCell under

the test

Test Procedure

1. Turn on iCell and check iCell synchronization status.

2. UE is attached to iCell and then handover with neighboring cell.

Expected Result

1. Air synchronization succeed in iCell

2. iCell automatically self-configure nearby Macro cell as its neighbor cell.

3. Handover process viewed by UE monitor software is correct and data service

works normally during handover.

Comments

1. There is TDD LTE Macro cell near the iCell under the test.

2. Neighboring Macro Cell has configured neighboring cell relation with iCell under

the test

6.2 ANR Test

Item Automatic Neighbor Relation

Test Condition:

1. iCell1 under test works correctly

2. iCell1 receives nearby eNodeB/iCell’s signal

Test Procedure

1. Turn on ANR function in iCell1, empty iCell1’s neighbor cell list

2. Reboot iCell1 and then check iCell1’s neighbor cell list



24

Expected Result

1. After the step 1 above, the neighbor cell list of iCell1 is blank.

2. After the step 2, iCell1 has updated neighbor cell list according to the nearby wireless

status.

6.3 Automatic PCI Detection and assignment

Item Automatic PCI Detection and Assignment

Test Condition:

1. iCell1 and iCell2 under test work correctly and iCell2 can receive iCell1’s signal

2. Turn on automatic PCI detection and assignment function.

Test Procedure

Reboot iCell2 and check iCell2’s PCI.

Expected Result

ICell2 can automatically configure PCI and avoiding PCI conflict with iCell1.

6.4 RACH optimization

Item RACH optimization

Test Condition:

1. iCell1 and iCell2 configure with the same frequency and the same PRACH

parameters

2. iCell1 has powered on and works normally

Test Procedure

1. Power on iCell2 and turn on ANR function, set PrachConfigEnable on.

2. After iCell 2 has been established, Check the RootSequenceIndex value of iCell1

and iCell2

Expected Result

1. the RootSequenceIndex value of iCell1 and iCell2 are different.

tdd lte icell iot test item v2.0

Documents

iot function test

iot test topology

anr test

service test

ping test

basic test items

icell initiates s1

mme initiates e