RNC Test Guide

ZXWR RNC (V3.07.310) Test Guide For Internal Use Only

Confidential and Proprietary Information of ZTE CORPORATION.

ZXWR RNC (V3.07.310) Radio Network Controller Test Guide

(V1.0)

ZTE CORPORATION



ZXWR RNC (V3.07.310) Radio Network Controller Test Guide (V1.0)

Planned by: Mobile Product Support Center, ZTE Sales Engineering & Service Division

Compiled by: Xu Jian-yu

Reviewed by: Chen Tai-ming, Shang Zi-yuan, and Li Chun-he

* * * *

ZTE CORPORATION

Address: ZTE Plaza, #889 Bibo Road, Zhangjiang Hi-tech Park, Shanghai, P. R. China

Post code: 201203

Technical support website: http://tsm.zte.com.cn

Hotline: +86 755 26770800 800-830-1118

Fax: +86 755 26770801

* * * *



Legal Information All rights reserved. No part of this documentation may be excerpted, reproduced, translated, annotated or duplicated, in any form or by any means without the prior written permission of ZTE Corporation.

and are the registered trade marks of ZTE Corporation. The names and logos of ZTE products are proprietary logos or registered trade marks. The names of other products and companies mentioned in this manual may be proprietary to their owners respectively. Without the prior written permission of ZTE or the owners of third-party trade marks or trade names, this manual does not grant the reader any permission or right to use any marker appeared in the manual.

The product described herein conforms to the design requirements of environment protection and human security. The storage, usage, and discard of the product shall comply with the manual, related contract, or laws and regulations of related countries.

The actual product may differ from what is described in this standard due to frequent update of ZTE products and fast development of technologies. Please contact the local ZTE office for the latest updating information of the product.

For the latest document information, please visit our website: http://tsm.zte.com.cn



Feedback Table

You are invited to give your suggestions and opinions to improve ZTE user manuals and

enjoy better service by sending emails to [email protected]. Thank you for your cooperation!

Document

Name ZXWR RNC(V3.07.310) Test Guide V1.0

Product

Version No. V3.07.310

Document

Version No. V1.0

Please provide your information for further contact:

Name Company

Post Code Address

Tel E-mail

Comments

Very Good Good Ordinary Bad Very Bad

General View

Work instruction

Convenient to

consult

Complete test items

Feasibility of test

items

Correct acceptance

criteria

Well-organized

structure

Suggestions

You may give suggestions from any perspective such as the content, structure, details, depth,

expression, figures/tables, special tools, FAQ and so on. The suggestions are not confined to

this document.



Revision Records

Document

Version No.

Prepared/

Revised by

Prepared/Revi

sed on

Total

Pages

Reason for

Revision

Contents of Revision

(Key Points Only)

V1.0 Chen Yan-hao 2008-12-30 119 None None

Note 1: This table must be completed before updating the archived document (the document archived in the

archival room of the division or the Company).

Note 2: Fill "None" in "Reason for Revision" and "Contents of Revision" when archiving this document for the

first time.



Preface

This manual serves to guide the commissioning test or acceptance test. It

describes each test item in details in terms of Prerequisites, Procedure,

Acceptance Criteria and Remarks.

The test items in this manual combine the test items in the commissioning test

record and those in the acceptance test record. Each test item has an

exclusive number, which corresponds to the test number in the commissioning

test/acceptance test record.

Reference documents:

1. ZXWR RNC(V3.07.310) Operation Manual

2. ZXWR RNC(V3.07.310) Hardware Manual

3. ZXWR RNC(V3.07.310) Maintenance Manual

General Care Overview

To make the ZXWR RNC (V3.07.310) test secure, standard, and orderly and

avoid accidents, please read this chapter carefully before you conduct the test.

The engineers in charge of ZXWR RNC (V3.07.310) test shall have basic

knowledge of the secure operation, master the correct manipulation means via

technical training, and bear corresponding work qualifications.

During the course of ZXWR RNC (V3.07.310) test, the operators must strictly

observer the precautions and the special security instructions given by ZTE.

During the course of ZXWR RNC (V3.07.310) test, all-round preparations,

including software and hardware, shall be well arranged to ensure sound test

implementation.

In addition, the precautions listed in this manual are special cautions advised

by ZTE and ZTE shall not bear any responsibility for any problem caused by

disobedience against the general operation criteria or the equipment

design/production/use security criteria.

Electrical Security

High-voltage AC



High voltage is dangerous. Direct contact with high voltage/civil electricity or

contact with high voltage/ civil electricity through the moist object mediate can

bring the fatal danger. For operation on high-voltage or AC electricity, the

operators must use the special tools, and the ordinary tools are prohibited.

The operators of the AC power supply equipment must observer the local

security specifications.

The operators of the AC equipment must have work qualifications on the high

voltage and AC.

The operators shall not wear electricity conductors such as watches, bracelets,

rings and so on.

For operation and maintenance in a moist environment, measures shall be

taken to prevent the moisture entering the equipment.

Power Cables

Before the assembly/disassembly of the power cables, do power off the power

supply.

Before a cable is connected, make sure the cable and the cable label are

consistent with the actual connection.

Anti-static Precaution

Static is produced by friction of human’s body movement. In a dry environment,

a person can carry at most 30 KV of static voltage for quite a long period. If an

operator carrying static contacts the parts and discharges through the parts, the

parts maybe damaged.

Before the operator contacts the equipment or touches the electrical parts such

as cards, circuit board and IC chips with hand, he/she shall wear the anti-static

bracelet and the other end of the bracelet shall be well grounded so as to avoid

damages to the sensitive parts by the static carried in human body.

A resistance over 1 MΩ must be connected between the anti-static bracelet

and the grounding points to protect the operator from sudden electric shock.

And remember that 1 MΩ is quite low for the static discharge.

The anti-static bracelet shall be inspected regularly. It is prohibited to replace

the bracelet cables with other ones.

Keep the static-sensitive boards from the objects with static or the objects easy

to produce static. If plastic packing bags, plastic transport boxes or plastic



transport belts rub the parts, the parts will then carry static. Once these parts

contact the human body or the ground, they will discharge and be damaged.

The static-sensitive boards can only contact the material with good electricity

conductivity, such as the anti-static packing bags. And the anti-static bags shall

be used for board storage and transport.

The testing equipment shall discharge before they are connected to the boards,

that is, the testing equipment shall be grounded in advance.

Keep the boards far from the strong DC magnetic fields such as the CRT

display. The safe distance shall be at least 10 cm.

Inserting/Unplugging Boards

To avoid man-made damages to the RNC modules, the operator shall try not to

insert or unplug the electriferous modules. For those that must be inserted or

unplugged, the operator must wear an antistatic bracelet.

When you insert the boards, don’t force it in and avoid damages to the pins in

the sub-rack.

Insert the board by the slot. And avoid the contact between board circuit panels,

which may cause short circuit.

When you take a board by hands, don’t touch the circuit, parts, connectors or

cabling troughs in it.

Personnel Arrangement

Decide the participants. During the test, the user’s representative, ZTE

representative, the project supervisor, and the constructor’s representative

shall be present.

Tools and Instruments

The ZXWR RNC (V3.07.310) test needs many tools and instruments. Related

preparations shall be made in advance.

Tools:

Phillips screwdrivers (one 4”, one 6” and one 8”)

Slotted screwdrivers (one 4”, one 6” and one 8”)

Anti-static bracelet

Instruments:

One multimeter



At least 2 sets of testing mobile phone and UIM card (with the network

service available)

One signaling tracing instrument


Confidential and Proprietary Information of ZTE CORPORATION. i

Contents

Chapter 1 RNC Hardware Test ................................................................................................. 1-1

1.1 Hardware Test .................................................................................................................. 1-1

1.1.1 Rack Fan Test ......................................................................................................... 1-1

1.1.2 RNC Board Test ...................................................................................................... 1-2

1.2 Reset and Switchover Test............................................................................................... 1-3

1.2.1 Foreground Manual Board Reset ........................................................................... 1-3

1.2.2 OMC Server Restart ............................................................................................... 1-4

1.2.3 Foreground Manual Switchover .............................................................................. 1-5

1.2.4 Background Master/Slave Switchover .................................................................... 1-6

Chapter 2 OMC O&M Test ........................................................................................................ 2-1

2.1 Log Management Test ..................................................................................................... 2-1

2.1.1 Log Query ............................................................................................................... 2-1

2.1.2 Log Export .............................................................................................................. 2-2

2.2 Dynamic Resource Management Test ............................................................................. 2-3

2.2.1 Soft Reset and Block Test ....................................................................................... 2-3

2.2.2 CPU/DSP Dynamic Management ........................................................................... 2-4

2.2.3 ATM Link Configuration Information Dynamic Management ................................... 2-5

2.2.4 ATM Optical Port Dynamic Management ................................................................ 2-6

2.2.5 IMA/TC Configuration Dynamic Management ........................................................ 2-7

2.2.6 E1 Configuration Dynamic Management ................................................................ 2-8

2.2.7 Serving Cell Dynamic Management........................................................................ 2-9

2.2.8 Adjacent Office Dynamic Management ................................................................. 2-10

2.2.9 Signaling Link Dynamic Management .................................................................... 2-11

2.3 Configuration Management Test .................................................................................... 2-12

2.3.1 Physical Equipment Configuration Management .................................................. 2-12

2.3.2 ATM Configuration Management .......................................................................... 2-13

2.3.3 No.7 Configuration Management .......................................................................... 2-14

2.3.4 Configuration of ATM and IP Binding Relation ...................................................... 2-15

2.3.5 Radio Resource Configuration Management ........................................................ 2-16

2.3.6 Foreground and Background Data Synchronization ............................................. 2-17

2.4 Fault Management Test ................................................................................................. 2-18

2.4.1 Alarm Management ............................................................................................... 2-18


Confidential and Proprietary Information of ZTE CORPORATION. ii

2.4.2 Test Management ................................................................................................. 2-19

2.5 Performance Management Test ..................................................................................... 2-20

2.5.1 Measurement Task Management .......................................................................... 2-20

2.5.2 Index Management ............................................................................................... 2-22

2.5.3 Performance Data Query ...................................................................................... 2-23

2.6 Security Management Test............................................................................................. 2-25

2.6.1 Security Policy Management ................................................................................ 2-25

2.6.2 Role Management ................................................................................................ 2-27

2.6.3 User Management ................................................................................................ 2-29

2.6.4 Department Management ..................................................................................... 2-30

2.6.5 Login User Management ...................................................................................... 2-31

2.7 Alarm Box Monitoring Test ............................................................................................. 2-32

2.7.1 Alarm Box Monitoring Test .................................................................................... 2-32

2.8 Software Version Management Test .............................................................................. 2-33

2.8.1 Software Version Management Test ..................................................................... 2-33

Chapter 3 Service Test ............................................................................................................. 3-1

3.1 Basic Service Test ............................................................................................................ 3-1

3.1.1 Voice Call Service Test ........................................................................................... 3-1

3.1.2 Videophone Service Test ........................................................................................ 3-2

3.1.3 PS Domain Service Test ......................................................................................... 3-3

3.1.4 HSPA Service Test .................................................................................................. 3-4

3.1.5 Concurrent Service Test ......................................................................................... 3-6

3.2 Handover Test .................................................................................................................. 3-9

3.2.1 Softer Handover ...................................................................................................... 3-9

3.2.2 Intra-RNC Inter-NodeB Soft handover between Two Cells ................................... 3-13

3.2.3 Intra-CN Inter-RNC Soft Handover between Two Cells ........................................ 3-17

3.2.4 Intra-NodeB Hard Handover between Two Cells .................................................. 3-21

3.2.5 Intra-RNC Inter-NodeB Handover between Two Cells .......................................... 3-25

3.2.6 Intra-CN Inter-RNC Hard Handover between Two Cells of Different Frequency ... 3-29

3.2.7 Intra-CN Inter-RNC Hard Handover between Two Cells of Common Frequency . 3-33

3.3 IOT between UMTS and GSM/GPRS ............................................................................ 3-37

3.3.1 Cell Reselection in CS (UMTS→ GSM) ................................................................ 3-37

3.3.2 Cell Reselection in CS (GSM→ UMTS) ................................................................ 3-38

3.3.3 Inter-System Handover of CS12.2K Voice Call (UMTS→ GSM) .......................... 3-39

3.3.4 Inter-System Handover of CS12.2K Voice Service (GSM→ UMTS) ..................... 3-40


Confidential and Proprietary Information of ZTE CORPORATION. iii

3.3.5 PS Cell Reselection (UMTS→ GSM/GPRS) ......................................................... 3-41

3.3.6 PS Handover (UMTS→ GSM/GPRS) ................................................................... 3-42

3.3.7 PS Handover (GSM/GPRS→ UMTS) ................................................................... 3-43

Appendix A Board LED Indicators .......................................................................................... A-1

A.1 LED Indicators ................................................................................................................. A-1

A.2 LED Control Rules ........................................................................................................... A-2

A.2.1 Board Power-on ..................................................................................................... A-2

A.2.2 Hardware Reset ..................................................................................................... A-3

A.2.3 ENUM LED Indicator .............................................................................................. A-3

A.2.4 Master/Slave (ACT) LED Indicator ......................................................................... A-4

A.2.5 RUN and ALM LED Indicators ................................................................................ A-4

A.2.6 Special LED Indicators ........................................................................................... A-4

A.3 Supplementary Description.............................................................................................. A-7

A.3.1 LED Indicator Status upon Board Startup ............................................................... A-7

A.3.2 Fault Alarm LED Indicator ...................................................................................... A-7

A.3.3 ICM LED Description .............................................................................................. A-8

A.3.4 Plane LED Indicators .............................................................................................. A-9

A.3.5 PWRD LED Description ....................................................................................... A-10

A.3.6 LED Lightening for Clock Missing......................................................................... A-11

Appendix B Basic Service Signaling Flows ........................................................................... B-1

B.1 Signaling Flowchart of CS Domain .................................................................................. B-1

B.2 Signaling Flowchart of PS Domain .................................................................................. B-2

B.2.1 UE Attaching Flowchart .......................................................................................... B-2

B.2.2 PDP Context Activation Flowchart .......................................................................... B-3

B.3 UMTS Soft Handover Signaling Flow .............................................................................. B-4

B.3.1 Intra-NodeB Softer Handover Signaling Flow ......................................................... B-4

B.3.2 Intra-RNC Inter-NodeB Soft Handover Flow .......................................................... B-5

B.3.3 Inter-RNC Soft Handover Flow ............................................................................... B-6

B.4 UMTS Hard Handover Signaling Flow ............................................................................. B-7

B.4.1 Intra-NodeB Hard Handover Flow between Different Cells .................................... B-7

B.4.2 Intra-RNC Inter-NodeB Hard Handover Flow ......................................................... B-8

B.4.3 Inter-RNC Hard Handover Flow ............................................................................. B-9

B.5 Intersystem Handover Signaling Flow ........................................................................... B-11

B.5.1 2G→3G Handover Flow ....................................................................................... B-11

B.5.2 3G→2G Handover Flow ....................................................................................... B-13


Confidential and Proprietary Information of ZTE CORPORATION. 1-1

Chapter 1 RNC Hardware Test

1.1 Hardware Test

No. and Item 1.1.1 Rack Fan Test

Prerequisites: 1. The general power switch of the RNC rack has been turned on.

2. There is no alarm (undervoltage/overvoltage) on the RNC power distribution module.

Procedure: 1. Put a fan box into the rack.

2. Plug out all the boards in the shelf under the fan box.

3. Put a 20cm-long paper slip into the box under the fan box.

4. For the fan box on the bottom of the rack, reach the paper slip into the box ON it to perform the test.

Acceptance Criteria: 1. The fan LED indicator is in normal status (green light on).

2. The paper slip is blown upward, indicating the wind direction is upward.

Remarks: 1. If the paper slip is blown downward, it indicates that the wind direction is wrong, and the fan box

requires replacement, or the power cable connection inside the rack need examination.



No. and Item 1.1.2 RNC Board Test

Prerequisites: 1. The power module of the RNC rack works normally.

2. The board configurations of the RNC rack are all ready.

Procedure: 1. Turn on the power switch on the back of each shelf.

Acceptance Criteria: 1. Each board LED indicator is in normal status

Remarks: 1. Please refer to Appendix A for description of the board LED state.



1.2 Reset and Switchover Test

No. and Item 1.2.1 Foreground Manual Board Reset

Prerequisites: 1. Each board LED indicator is in normal status.

2. A voice service (CS 12. 2K) can be accomplished before the RNC board is reset.

Procedure: 1. Press key RST to reset the board.

2. If the equipment is configured with active and standby boards, it is only necessary to reset the active

board.

Acceptance Criteria: 1. After restart, LED RUN of the board flashes at 1Hz.

2. The voice service (CS 12. 2K) is successful.

Remarks: 1. If a board has no Master/Slave configuration, services on it will be released after it is reset.

2. For the board with Master/Slave configuration, the active board is reset, the standby board will

become the active one, and the original active board will stand by after being reset.

3. For the ROMB and RCB boards, both have two CPU indicators to indicate the status.



No. and Item 1.2.2 OMC Server Restart

Prerequisites: 1. The OMC server is running normally.

2. The OMC system has been logged in normally.

Procedure: 1. Shut down the OMC server.

2. Turn on the OMC server after about 2--3 minutes.

3. Run the OMC server application program.

Acceptance Criteria: 1. After the OMC server is shut down, the state bar at the bottom displays “Link is broken and the

system is trying to recover it. Please wait and retry later!” After that, a timeout prompt will appear

indicating the link is broken and dialog is deleted. Click <OK> to exit the maintenance platform.

2. After the OMC server application program is successfully launched, run the maintenance platform

again and it can be logged in normally.

Remarks: 1. The restart of the OMC server does not influence the services.



No. and Item 1.2.3 Foreground Manual Switchover

Prerequisites: 1. Each board LED indicator is in normal status, and the master/slave boards to be tested are all in the

right slots.

2. A voice service (CS 12. 2K) can be accomplished before switchover.

Procedure: 1. Originate and keep a CS12. 2K voice service (skip this step in RCB master/slave switchover test).

2. Make master/slave switchover by pressing key EXCH on the panel of the master board.

Acceptance Criteria: 1. Each RUN LED indicator flashes at 1 Hz, and each board runs normally after the switchover.

2. After the switchover, LED ACT of the original master board becomes off, and that of the original

standby board becomes on.

3. During the switchover, voice service in step one is normal, without pause or interruption (This item is

unnecessary for RCB master/slave switchover test).

Remarks: 1. The ROMB, UIMC, UIMU, CHUB, GIPI, and RCB boards all support Master/Slave switchover. During

the process of master/slave switchover, calls on RCB will be released. After its switchover has been

completed, the cell will be reestablished, and calls can be successfully established in the new master

board.

2. When the data are being synchronized, it is prohibited to manually start master/slave switchover again

within 5 minutes after a master/slave switchover is completed. Otherwise, it could lead to the second

master/slave switchover failure.

3. Both ROMB and RCB boards have two CPUs and respective EXCH keys, RUN, LED indicators and

ACT LED indicators.



No. and Item 1.2.4 Background Master/Slave Switchover

Prerequisites: 1. Each board LED indicator is in normal status, and the master/slave boards to be tested are all in their

right slots.

2. A voice service (CS 12.2K) can be accomplished before master/slave switchover.

Procedure: 1. Originate and keep a CS12.2K voice service (skip this step in RCB master/slave switchover test).

2. Open the configuration management interface. In the left pane click [OMC→ UTRAN SubNetwork→

RNC Managed Element→ RNC Config Set→ RNC Ground Resource Management→ Rack]. Double-

click [Rack], and the rack figure will appear in the right pane.

3. Right-click the board to be tested with the mouse and choose [normal master-slave state switch]. A

dialog box will pop up: “Do you want to perform master/slave switchover?“ Click <OK> to execute the

master/slave switchover, or click [Cancel] to exit.

4. For ROMB and RCB (each board has two CPUs), choose the correct CPU number to perform the

master/slave switchover.

Acceptance Criteria: 1. Each RUN LED indicator flashes at 1 Hz and each board runs normally after the switchover.

2. After the switchover, the LED ACT of the original master board becomes off, and that of the original

standby board becomes on.

3. During the switchover, voice service in Step 1 is normal, without pause or interruption (This item is

unnecessary for RCB master/slave switchover test).

Remarks: 1. The ROMB, UIMC, UIMU, CHUB, PSN, GLI, and RCB boards all support master/slave switchover.

2. When the data are being synchronized, it is prohibited to manually start master/slave switchover

again within 5 minutes after a master/slave switchover is completed. Otherwise, it could lead to the

second master/slave switchover failure.

3. Both ROMB and RCB have two CPUs, and those CPUs have their respective RUN LED indicators

and ACT LED indicators.



Chapter 2 OMC O&M Test 2.1 Log Management Test

No. and Item 2.1.1 Log Query

Prerequisites: 1. Each board LED indicator is in normal status, and the voice service (CS 12.2K) is supported.

2. The OMC runs normally, and the client can access the server.

Procedure: 1. Log in and open the OMC interface.

2. Click [View→ Log Management] from the interface of the client to open the log management interface.

3. Collapse [Query Log] in the left pane, choose [Operation log], [Security log], or [System log] as

needed, and choose [Query Operation/Security/System Log] or [Query All Operation/Security/System

Log] from the right-click menu, then choose query conditions from the pop-up window, and click

<OK>.

4. Check query result in the right pane.

Acceptance Criteria: 1. Log records are correctly displayed according to query conditions.

Remarks: None



No. and Item 2.1.2 Log Export

Prerequisites: 1. Each board LED indicator is in normal status, and the voice service (CS 12.2K) is supported.

2. The OMC runs normally, and the client can access the server.


2. Click [View→ Log Management] from the interface of the client to open the log management interface.

3. Collapse [Query Log] in the left pane, choose [Operation log], [Security log], or [System log] as

needed, and choose [Query Operation/Security/System Log] or [Query All Operation/Security/System

Log] from the right-click menu, then choose query conditions from the pop-up window, and click

<OK>.

4. Check query result in the right pane.

5. Click the icon [Query and Export Result According to Current Condition] in the toolbar at the top of the

right pane, and choose the directory and file name to save the log in the pop-up dialog box, and click

<Save>.

6. A prompt box will pop up: “Export log successfully”. Click <OK>.

Acceptance Criteria: 1. Find the saved log file via the save path and open it by Excel. The exported log file can be opened by

Excel.

Remarks: 1. When the log file is saved, all the records meeting the query conditions will be saved. If no query

condition is set, all the log records will be displayed and saved.



2.2 Dynamic Resource Management Test

No. and Item 2.2.1 Soft Reset and Block Test

Prerequisites: 1. The OMC server runs normally, and the client can access the server.

2. The communication between OMC and RNC is normal.

3. All the RNC boards run normally.

4. CS and PS services are normal.


2. In the topology management tab, right-click [UTRAN SubNetwork] to select [Navigate to CM] to open

the configuration management interface.

3. In the left pane of the configuration management interface, click [OMC→ UTRAN SubNetwork→ RNC

Managed Element] and right-click to choose [Apply Mutex Right].

4. After the mutex right is applied, double-click [RNC Ground Resource Management]. Click the [RNC

Reset] or [Iu Port Reset] icon in the toolbar at the top of the right pane, and click <OK>. For [Iu Port

Reset], choose “Iu CS” or “Iu PS” for reset and then input the verification code to execute the reset.

5. In the configuration management interface, click the main menu [RNC Managed Element→ Open

RNC Configuration Centralized management]. In the pop-up window, click [Dynamic data

management object→ AAL2 Path] to perform block/unblock operation.

6. Click [RNC Managed Element→ Open RNC Configuration Centralized management]. In the pop-up

window, click [Dynamic data management object→ Cell and Channel], select the proper cell and click

[Cell reset].

Acceptance Criteria: 1. The RNC, Iu interface, and cell can be successfully reset. DSP and the AAL2 channel can be

blocked/unblocked successfully.

2. The CS and PS services are as normal as before.

Remarks: None



No. and Item 2.2.2 CPU/DSP Dynamic Management








3. In the left pane click [OMC→ UTRAN SubNetwork→ RNC Managed Element→ RNC Ground

Resource Management→ Rack]. Double-click [Rack], and the rack figure will appear in the right pane.

Choose a board, right-click it and choose [CPU→ Usage Rate Query], [Unit→ Block] or [Unit→

Unblock] from the menu. For RUB, you can firstly choose [Subunit→ Block/Unblock] and then choose

the number of the DSP to be operated.

Acceptance Criteria: 1. [Usage Rate Query] operation can be correctly performed on CPU.

2. [Block] and [Unblock] operations can be correctly performed on Unit/Subunit.

Remarks: 1. CLKG and ICM do not support [Observer], [Block] or [Block delay] operation.

2. DTB, IMAB, APBE, GIPI, and RUB (including CPU and DSP) support [Block] and [Unblock]

operations.



No. and Item 2.2.3 ATM Link Configuration Information Dynamic Management








3. In the left pane click [RNC Ground Resource Management→ Transmission Configuration→ PVC

Configuration→ PVC Configuration ID]. Double-click [PVC Configuration ID], and then click the icon

[Get Status], or [Observer]/[Unobserver] in the toolbar at the top of the right pane.

Acceptance Criteria: 1. [Get Status] operation can correctly return the status of the PVC link.

2. [Observer] and [Unobserver] operations can be correctly performed on the PVC link.

Remarks: None



No. and Item 2.2.4 ATM Optical Port Dynamic Management








3. In the left pane click [RNC Ground Resource Management→ Rack]. Double-click [Rack] and the rack

figure will appear in the right pane. Right-click APBE and then choose [Show Board Properties Page]

from the right-click menu. Choose the button [Optical port APS protection] in the board properties

page and click [Create] to create APS protection.

4. Right-click the APBE board and select [Get APS status]. Choose the query type and the port number,

and then the status window will appear.

Acceptance Criteria: 1. The query result of ATM optical port status can be displayed correctly.

Remarks: 1. The boards must be configured with master-slave configuration before this operation is performed.



No. and Item 2.2.5 IMA/TC Configuration Dynamic Management








3. In the left pane click [RNC Ground Resource Management→ Transmission Configuration→ IMA

Group Configuration→ IMA Group Configuration (ID)]. Double-click [IMA group configuration (ID)], and

click the icon [Get Status], [Restart], [Inhibit]/[Uninhibit] or [Observer]/[Unobserver] in the toolbar at the

top of the right pane.

Acceptance Criteria: 1. [Get Status] operation can correctly return the state of the IMA/TC configuration object.

2. [ReStart] operation can be correctly performed on the IMA/TC configuration object.

3. [Inhibit] and [Uninhibit] operations can be correctly performed on the IMA/TC configuration object.

After the [Uninhibit] operation, the CS and PS services are as normal as before.

4. [Observer] and [Unobserver] operations can be correctly performed on the IMA/TC configuration

object.

Remarks: None



No. and Item 2.2.6 E1 Configuration Dynamic Management








3. In the left pane click [RNC Ground Resource Management→ Transmission Configuration→ IMA

Group Configuration→ IMA Group Configuration (ID)→ IMA Link Configuration (ID)]. Double-click [IMA

Link Configuration (ID)], and click the icon [Get Status], [Inhibit]/[Uninhibit] or [Observer]/[Unobserver]

in the toolbar at the top of the right pane.

Acceptance Criteria: 1. [Get Status] operation can correctly return the state of the E1 configuration object.

2. [Inhibit] and [Uninhibit] operations can be correctly performed on the E1 configuration object. After

the [Uninhibit] operation, the CS and PS services are as normal as before.

3. [Observer] and [Unobserver] operations can be correctly performed on the E1 configuration object.

Remarks: None



No. and Item 2.2.7 Serving Cell Dynamic Management








3. In the left pane of the configuration management interface, click [RNC Radio Resource

Management→ UTRAN Cell→ UTRAN Cell (ID)]. Double-click [UTRAN Cell (ID)], and click the icon

[Get Status], [Cell Reset] or [Spy]/[Unspy] in the toolbar at the top of the right pane.

Acceptance Criteria: 1. [Get Status] operation can correctly return the state of the UTRAN cell.

2. [Spy] and [Unspy] operations can be correctly performed on the UTRAN cell.

Remarks: None



No. and Item 2.2.8 Adjacent Office Dynamic Management









RNC Configuration Centralized management→ Dynamic data management object→ Adjacent office

signaling point], and then click the button [Status Refresh] and [Show status information] at the bottom

of the pop-up window.

Acceptance Criteria: 1. [Show status information] operation can correctly return the state of the adjacent office.

2. [Status Refresh] operation can be correctly performed on the adjacent office.

Remarks: None



No. and Item 2.2.9 Signaling Link Dynamic Management









RNC Configuration Centralized management→ Dynamic data management object→ No.7 link], and

then click the button [Status Refresh], [Observer]/[Unobserver], or [Interdict]/[Uninterdict] at the bottom

of the pop-up window.

Acceptance Criteria: 1. [Get Status] operation can correctly return the state of the signaling link.

2. [Interdict] and [Uninterdict] operations can be correctly performed on the signaling link. After the

[Uninterdict] operation, the CS and PS services are as normal as before.

3. [Observer] and [Unobserver] operations can be correctly performed on the signaling link.

4. [Interdict] and [Uninterdict] operations can be correctly performed even if there are several SS7 links.

After the [Uninterdict] operation, the CS and PS services are as normal as before.

Remarks: None



2.3 Configuration Management Test

No. and Item 2.3.1 Physical Equipment Configuration Management








3. In the left pane click [OMC→ UTRAN SubNetwork→ RNC Managed Element→ RNC Config Set→

RNC Ground Resource Management], right-click it to choose [Create→ Rack], input the rack number

to create a rack.

4. Double-click the newly created rack, and the rack figure will appear in the right pane. Right-click the

rack figure to choose [Create→ Shelf], input the shelf number and choose a shelf type to create a

shelf.

5. Right-click the newly created shelf figure to choose [Create→ Board], and choose a board type to

create a board.

6. Delete the board, shelf, and rack one by one through the right-click menu in a reverse order against

the above steps.

Acceptance Criteria: Physical equipment such as racks, shelves, and boards, can be successfully created and deleted.

Remarks: To delete a shelf, all the boards in that shelf should have been deleted. To delete a rack, all the shelves in

that rack should have been deleted.



No. and Item 2.3.2 ATM Configuration Management








3. In the left pane click [RNC Managed Element→ RNC Config Set→ RNC Ground Resource

Management→ Transmission Configuration→ IMA Group Configuration]. Right-click it to choose

[Create→ IMA Group Configuration].

4. Right-click the newly created [IMA Group Configuration] and choose [Create→ IMA Link

Configuration].

5. Click [RNC Ground Resource Management→ Transmission Configuration→ NE Information

Configuration] and right-click it to choose [Create→ (an element)] to create the NE information.

6. Click [RNC Ground Resource Management→ Transmission Configuration→ NE Information

Configuration→ PVC Configuration], right-click it to choose [Create→ PVC Configuration] to create the

PVC link information.

7. Double-click an element in the NE Information Configuration tree to show the NE configuration tabs.

Click the tab [Path Configuration], input corresponding parameters and click the button [Create

commit] to create the NE path.

8. Click the tab [ATM Office Configuration], input corresponding parameters and click [Create commit] to

create the ATM office.

9. Click the tab [Signaling Link Configuration], input corresponding parameters and click [Create commit]

to create the ATM signaling link.

10. Click the tab [AAL2 Path Configuration], input corresponding parameters and click [Create commit] to

create the AAL2 path.

11. Delete the configured office items in a reverse order against the above steps.

Acceptance Criteria: 1. The configured ATM items can be correctly created and deleted.

Remarks: 1. The methods of ATM configuration created to other CN offices are similar as above, but there is no

IMA configuration (because usually optical fibers are adopted for transmission).



No. and Item 2.3.3 No.7 Configuration Management









RNC Ground Resource Management→ Transmission Configuration→ NE Information Configuration].

Double-click an NE to show the RNC NE information tabs. Click the tab [Signaling Link Configuration],

input corresponding parameters and click the button [Create commit] to finish the No.7 signaling

configuration.

4. Click the tab [Local Office Signaling Point Configuration], input corresponding parameters and click the

button [Create commit] to configure the local office signaling point.

5. Double-click an adjacent RNC office to show its information tabs. Click [Adjacent Office Signaling

Point Configuration], input corresponding parameters and click the button [Create commit] to configure

the adjacent office signaling point. Click the tab [Signaling Link Configuration], input corresponding

parameters and click the button [Create commit] to configure the signaling link.

6. Click the tab [Office Route], input corresponding parameters and click the button [Create commit] to

configure the office route.

7. Click the tab [AAL2 Path Configuration], input corresponding parameters and click the button [Create

commit] to configure the AAL2 path (this step is unnecessary for the PS domain.)

8. Delete the configured No.7 signaling items in a reverse order against the above steps.

Acceptance Criteria: 1. All the No.7 signaling items can be correctly created and deleted.

Remarks: 1. There is no direct route between RNC and MSCS, so it is unnecessary to configure the signaling link

group or the signaling link.



No. and Item 2.3.4 Configuration of ATM and IP Binding Relation









RNC Ground Resource Management→ Transmission Configuration→ ATM And IP Binding Relation].

Right-click it to choose [Create→ ATM And IP Binding Relation].

4. Delete configured IPOA items in a reverse order against the above steps.

Acceptance Criteria: 1. The configured IPOA items can be correctly created and deleted.

Remarks: None



No. and Item 2.3.5 Radio Resource Configuration Management









Managed Element→ RNC Config Set→ RNC Radio Resource Management→ NodeB Configuration

Information]. Right-click it and choose [Create→ NodeB Configuration Information] to create the

NodeB configuration information.

4. Click [RNC Radio Resource Management→ UTRAN Cell]. Right-click it and choose [Create→ UTRAN

Cell]. In the pop-up window, configure parameters such as cell frequency band, primary scrambling

code, local cell identity.

5. Click [RNC Radio Resource Management→ External UTRAN Cell]. Right-click it and choose

[Create→ External UTRAN Cell].

6. Click [RNC Radio Resource Management→ UTRAN Cell→ UTRAN Cell (ID)→ Neighbouring Cell].

Right-click it and choose [Create→ Neighbouring Cell].

7. Delete the configured radio resource items in a reverse order against the above steps.

Acceptance Criteria: 1. The radio resource items can be correctly created and deleted.

Remarks: 1. To create an [External UTRAN Cell], basic information of that cell should be firstly created in [ URA

Cell].



No. and Item 2.3.6 Foreground and Background Data Synchronization









Managed Element]. Double-click it and in the right pane click the icon [Synchronize All Tables] or

[Synchronize Modified Table]. In the pop-up window, select the check type, input the verify code and

click <OK> to perform synchronization.

Acceptance Criteria: 1. After the [Synchronize All Tables] operation is performed, all the tables in the background database

are synchronized to the foreground NE.

2. After the [Synchronize Modified Tables] operation is performed, the modified tables in the background

database are synchronized to the foreground NE.

Remarks: 1. Before the [Synchronize Modified Tables] operation, make sure the tables are modified. Otherwise,

there are no modified data and thus the [Synchronize Modified Tables] operation can not be

performed.



2.4 Fault Management Test

No. and Item 2.4.1 Alarm Management





Procedure: 1. Log in and open the OMC interface. Click the menu [View→ Fault management] to open the fault

management interface. Choose the tab [Management View] in the left pane.

2. Click the menu [Setting] and there are the following down-drop submenus:

Alarm Box Setting, Management Rule Setting, Maintenance Suggestion Setting, Severity Regrading

Setting, and Preferences.

3. Click the menu [Query] and there are the following down-drop submenus:

View Current Alarms, View Historical Alarms, View Notifications, Realtime Alarm Monitor, Realtime

Notification Monitor, Alarm Synchronization and History Alarm Statistics.

Acceptance Criteria: 1. The alarm rules can be created, queried, edited, and deleted.

2. The alarm data can be correctly queried by different conditions.

3. The alarm threshold can be correctly set.

Remarks: None



No. and Item 2.4.2 Test Management





1. Procedure:

2. Log in and open the OMC interface.

3. Click the main menu [View→ Test Management] to open the test management interface.

4. Create test task: open the test management interface, collapse the navigation tree, right-click the

proper RNC NE and choose [Create Test Task] to create a test task and set parameters.

5. Maintain test task: open the test management interface, collapse the navigation tree, right-click the

proper RNC NE and choose [Maintain Test Task] from the pop-up menu to modify the test task

parameters.

6. Execute instant test: open the test management interface, right-click the proper [rncCpu1], choose

[Execute Instant Test] and click <OK> in the pop-up dialog box to start the test.

7. Manage test result: open the test management interface, right-click the proper [rncCpu1], choose

[Test Result Query], confirm the basic conditions in the pop-up dialog box, and then click <OK> to

query the test result. Or right-click the proper object and choose [Test Result Clean] to delete the test

result.

Acceptance Criteria: 1. The test task can be correctly created, modified, and deleted.

2. The instant test can be correctly performed.

3. The test result can be correctly viewed and deleted.

Remarks: None



2.5 Performance Management Test

2.5.1 Measurement Task Management

No. and Item 2.5.1.1 Measurement Task Management





Procedure: 1. Log in and open the OMC interface. Click the main menu [View→ Performance Management] to open

the performance management interface.

2. In the performance management interface, click the main menu [Performance Management→

Measure Task Management] to open the measure task management interface in the right pane.

3. In the toolbar at the top of the right pane, click the icon [Create task] to start the measure task

creation wizard, and then fill in the parameters as required to create a measure task.

4. Choose a created measure task, and click the icon [View task] to query its property.

5. Choose a created measure task in suspended state and click the icon [Activate task] to activate it.

6. Choose a created measure task in activated state, and click the icon [Suspend task] to suspend it.

7. Choose a created measure task, and click the icon [Modify task] to modify its property.

8. Choose a created measure task, and click the icon [Delete task] to delete it.

Acceptance Criteria: 1. The measure task can be correctly created, activated, suspended, viewed, modified, and deleted.

Remarks: 1. The measure task cannot be modified or deleted unless it is in the suspended state.



No. and Item 2.5.1.2 History Measurement Task Management








Measure Task Management] to open the measure task management interface in the right pane.

3. Select [History Task] from the [Status Type] down-drop list in the right pane to open the history task

management interface.

4. Click an NE in the left pane, and all the history tasks related to that NE will be displayed in the history

task list in the history task management interface.

5. Select a history task from the list, and right-click it to choose [View history task] to query its detailed

information.

6. Select a history task from the list, and right-click it to choose [Delete history task] to delete it.

Acceptance Criteria: 1. The history measurement task can be queried and deleted.

Remarks: None



2.5.2 Index Management

No. and Item 2.5.2.1 Index Management







2. In the performance management interface, click the main menu [Performance Management→ Index

Management] to open the index management interface in the right pane.

3. In the toolbar at the top of the right pane, click the icon [New Index] to start the index task creation

wizard, and then fill in the parameters as required to create an index task.

4. Choose a created index task, and click the icon [View Index] to query its property.

5. Choose a created index task, and click the icon [Modify Index] to modify its property.

6. Choose a created index task, and click the icon [Delete Index] to delete it.

Acceptance Criteria: 1. The index task can be correctly created, viewed, deleted and modified.

Remarks: 1. The setting of alarm threshold and delta shall follow the rules below:

The value types of threshold and delta must be both integers and meet the following conditions: Each

threshold plus the delta of the same level shall be less than the threshold one level above it, and each

threshold minus the delta of the same level shall be larger than the threshold one level below it.

Especially, the alarm threshold of the lowest level of minus the delta of the same level shall be larger

than 0, and the alarm threshold of the highest level plus the delta of the same level shall be less than

100.

2. Each NE supports thirty index tasks at most.



2.5.3 Performance Data Query

No. and Item 2.5.3.1 Performance Data Query-by Task





5. The log server runs normally.




Performance Data Query -by Task] to start the [Query] wizard. Fill in the parameters as required and

execute data query.

3. In the toolbar above the right [Query Result] pane, click the icon [Export] to save the query result.

4. In the toolbar above the right [Query Result] pane, click the icon [Print] to print the query result.

5. In the toolbar above the right [Query Result] pane, click the icon [Chart Setting] to save the query

result.

Acceptance Criteria: 1. The counter history data can be queried by the measurement type and the measurement task.

2. The query result can be saved, printed and changed into chart.

Remarks: None



No. and Item 2.5.3.2 Performance Data Query





5. The log server runs normally.




Performance Data Query] to open the tab [Data query] in the right pane.

3. Select the query index and counters in the tab [Query Index], set the start time and finish time in the

tab [Query Time].

4. And then choose the query object in the tab [Query Object]: choose a management NE from the left

query objects, choose the available object from the right objects, and finally choose a query object.

Click <OK> to perform query.

5. In toolbar above the [Query Result] pane, click the icon <Export> to save the data in a file.

6. In toolbar above the [Query Result] pane, click the icon <Print> to print the data.

7. In toolbar above the [Query Result] pane, click the icon <Chart> to show the result in the form of a

chart.

Acceptance Criteria: 1. The related history data can be queried.

2. The query result can be saved, printed and changed into chart.

Remarks: None



2.6 Security Management Test

2.6.1 Security Policy Management

No. and Item 2.6.1.1 View Assigned Operation Rights





Procedure: 1. Log in and open the OMC interface. Click [View→ Security Management] in the main menu to open

the security management interface.

2. The left [Security Management Tree] pane displays all operation rights. Click a node in the operation

tree, and its detailed description will appear in the right pane.

Acceptance Criteria: 1. Detailed description of all operation rights in security policy management can be queried.

Remarks: None



No. and Item 2.6.1.2 Query & Customize User Account Rules







2. Click [Security Policy Management].

3. Double-click [User Account Rules] in the security policy management list in the right pane to modify

the user account rules, including [Password Length] and [Account Restriction].

Acceptance Criteria: 1. [Password Length] settings are valid.

2. [Account Restriction] setting is valid.

Remarks: 1. A locked user can be manually unlocked by the “admin” user. The “admin” user can’t be locked.

2. If a user is locked at a certain client, that user can still log on from other clients.



2.6.2 Role Management

No. and Item 2.6.2.1 Role Management







2. Create a role: Right-click [Role Management] in Security Management Tree and select [Create Role].

In the pop-up window, fill in [Basic Information], choose the rights in the tab [Access Rights], and add

the login address range in the tab [Login Address]. Finally, click <OK> to create a new role.

3. Modify a role: Choose a role from the role list, right-click it to select [Modify] or click the icon [Modify

Role] in the toolbar above the role list. In the pop-up [Modify Role] window, modify the role’s basic

information, including the role description, operation rights, managed object and login address range,

and then click <OK> to submit the modification.

4. Delete a role: Choose a role to be deleted from the role list, and right-click it to select [Delete] or click

the icon [Delete Role] in the toolbar above the role list. Click <Yes> to delete it.

5. Duplicate a role: Choose a role to be duplicated from the role list, right-click it to select [Duplicate] to

open the [Create Role] window. In the tab of [Basic information], fill in [Role Name] and [Role

Description] and click <OK>, and then a role will be created with the same operation rights, managed

object, and login address range as the duplicated one.

6. Refresh roles: Right-click [Role Management] in Security Management Tree and select [Refresh].

7. Search a role: Right-click [Role Management] in Security Management Tree and select [Find]. Input

the role name in the window and click <Find> to start the search.

8. View the role assignment: select the role to be viewed and right-click it to select [Assignment].

Acceptance Criteria: 1. Roles can be created, modified, and deleted.

2. Roles can be copied and refreshed.

3. Roles can be searched and the role assignment can be viewed.

Remarks: None



No. and Item 2.6.2.2 Role Set Management







2. Create a role set: Right-click [Role Set Management] in Security Management Tree and select

[Create Role Set]. In the [Basic information] tab, fill in the role set name and description, and assign

roles for the role set in the [Assign Roles] tab.

3. Modify a role set: Choose a role set from the role set list, right-click it to select [Modify] or click the

icon [Modify Role Set] in the toolbar above the role set list. In the pop-up [Modify Role Set] window,

modify the role set name and description in the [Basic Information] tab, and assign roles in the [Assign

Roles] tab.

4. Delete a role set: Choose a role set to be deleted from the role set list, and right-click it to select

[Delete] or click the icon [Delete Role Set] in the toolbar above the role set list. Click <Yes> to delete

it.

5. View the role set assignment: Choose the role set to be viewed and right-click it to select

[Assignment].

6. Search a role set: Right-click [Role Set Management] in Security Management Tree and select [Find].

Input the role set name in the window and click [Find] to start the search.

Acceptance Criteria: 1. Role sets can be created, modified, and deleted.

2. Role sets can be searched and the role set assignment can be viewed.

Remarks: None



2.6.3 User Management

No. and Item 2.6.3.1 User Management







2. Create a user: Right-click [User Management] in Security Management Tree and select [Create User].

Input corresponding information and click <OK>.

3. View and modify a user’s property: To show a user’s property, double-click the user in the user list or

right-click it to select [View]. To modify a user’s property, right-click it to select [Modify] and then

modify the user’s information in the pop-up [Modify User] window.

4. Modify a user’s password: Right-click the user in the user list, select [Modify] and then modify the

user’s password in the pop-up [Modify User] window.

5. Delete a user: Right-click the user to be deleted in the user list and select [Delete]. Click <Yes> in the

[Confirm] dialog box.

6. Refresh users: Right-click [User Management] in Security Management Tree, and select [Refresh].

7. Unlock a user: Right-click the user to be unlocked, click [Modify] to open the [Modify User] window. In

the [Login] tab, click the button [View User Lockup Records], choose the user to be unlocked, right-

click it and choose [Unlock].

Acceptance Criteria: 1. Users can be created, modified, and deleted. And the user password can be modified.

2. Users can be refreshed and unlocked.

Remarks: None



2.6.4 Department Management

No. and Item 2.6.4.1 Department Management







2. Create a department: Right-click [Department Management] in Security Management Tree and select

[Create Sub-department].Input the department name and description in the [Basic Information] tab,

choose its superior department in the [Superior Department] tab, and then click <OK>.

3. Modify a department: Right-click the department to be modified in the department list, select [Modify].

4. Delete a department: Right-click the department to be modified in the department list and then select

[Delete]. Click <Yes> in the [Confirm] dialog box.

5. Search a department: Right-click [Department Management] in Security Management Tree and

choose [Find]. Input the department name in the window and click [Find] to start the search.

6. Refresh department: Right-click [Department Management] in Security Management Tree and select

[Refresh].

Acceptance Criteria: 1. Departments can be created, modified, and deleted.

2. Departments can be searched and refreshed.

Remarks: 1. A department that has sub departments or users cannot be deleted.



2.6.5 Login User Management

No. and Item 2.6.5.1 Login User Management







2. Click the main menu [Function→ Login User Management] to show the connected users in the pop-up

[Login User] window.

3. Disconnect a connected user compulsorily: Right-click a user in the [Login User] window and choose

[Disconnect Compulsorily].

Acceptance Criteria: 1. Information of the connected users can be queried.

2. The connected users can be compulsorily disconnected.

Remarks: None



2.7 Alarm Box Monitoring Test

No. and Item 2.7.1 Alarm Box Monitoring Test




4. The alarm box has been installed and powered on.

5. The alarm box has been configured with correct parameters and connected to OMC. And it

communicates with RNC and OMC normally.

Procedure: 1. At the RNC side, manually trigger an alarm whose alarm rank can be indicated by the alarm box.

2. Query this alarm in the OMC fault management interface.

3. View this alarm in the screen of the alarm box.

4. This alarm box gives corresponding sound and light alarm as per the preset conditions.

5. After this alarm is restored, the alarm box does not show this alarm any more.

Acceptance Criteria: 1. The alarm can be correctly sent to the alarm box.

2. The alarm box can show the alarm rank and gives corresponding sound and light alarm as per the

preset conditions.

Remarks: None



2.8 Software Version Management Test

No. and Item 2.8.1 Software Version Management Test





2. Click [View→ Software Management] in the main menu to open the software management interface.

3. Create version file: Click the icon [Create Version File] in the toolbar at the top of the right pane,

select version type and the file, and finally confirm the creation.

4. Download version to NE: Right-click the target version in the [Lib Version] tag and choose the menu

[Add Version to ROMP] to download the version file to NE.

5. Switch default version: Right-click the target version in the [Default Version] tag and choose the menu

[Default Version Switching]. In the [New Version No.] pull-down list, click the target version file. In the

[If restart immediately] pull-down list, click [Yes]. In the [If force to load] pull-down list, select [Yes] or

[No]. And finally Click <Confirm>.

6. Delete version: Right-click the target version in the [Lib Version] tag and choose the menu [Delete

Version File from ROMP] to delete the version from the background.

Acceptance Criteria: 1. Version files can be successfully created and deleted.

2. Version files can be successfully uploaded to the foreground and the default versions can be

successfully switched.

Remarks: 1. It is prohibited to delete the version file that is serving as the current default version.



Chapter 3 Service Test

3.1 Basic Service Test

3.1.1 Voice Call Service Test

No. and Item 3.1.1.1 AMR Voice 12.2Kbps

Prerequisites: 1. RNC runs normally.

2. Testing UE A and testing UE B have finished PLMN selection, cell selection, and location update.

And they are in the idle state.

3. RNC static AMR rate is set as 12.2Kbps.

4. Use the signaling tracing software to monitor signaling at the Iu interface.

5. The cell should support R99 and the network runs normally.

Procedure: 1. Testing UE A calls testing UE B.

2. Testing UE A and B both finish RRC connection and RAB establishment.

3. Testing UE B hears the ring or vibrates, and successfully answers the call from testing UE A. The

call quality is satisfying.

4. Testing UE B or A hangs up to release the call.

Acceptance Criteria: 1. The vibration or ring of testing UE B and the ring-back tone of testing UE A are both normal.

2. Testing UE A and B can talk normally. The call quality is satisfying and there is no obvious delay.

3. The testing UEs can correctly release the call by hanging up. 4. The UL and DL signaling of the voice call is normal.

Remarks: None



3.1.2 Videophone Service Test

No. and Item 3.1.2.1 Videophone Service Test


2. Testing UE A and testing UE B have finished PLMN selection, cell selection, and location update.

And they are in the idle state.

3. Testing UE A and B should both support videophone service.

4. Use the signaling tracing software to monitor signaling at the Iu interface.

5. The cell should support R99 and the network runs normally.

Procedure: 1. Testing UE A originates a videophone call to testing UE B.

2. Testing UE B hears the ring or vibrates, and successfully answers the call from testing UE A. The

call quality is satisfying and they can see each other’s image via the testing UE.

3. Testing UE B or A hangs up to release the call.

Acceptance Criteria: 1. The vibration or ring of testing UE B and the ring back tone of testing UE A are both normal.

2. Testing UE A and B can talk normally. The audio quality is satisfying and there is no obvious delay.

3. Testing UE A and B can show each other’s image, and the image is stable (image definition depends

on the UE specification), with a certain delay allowed.

Remarks: None



3.1.3 PS Domain Service Test

No. and Item 3.1.3.1 PS Domain Service Test


2. USIM card of testing UE A has subscribed for the interactive services: UL 64Kbps and DL 64Kbps.

3. USIM card of testing UE B has subscribed for the interactive services: UL 64Kbps and DL 128Kbps.

4. USIM card of testing UE C has subscribed for the interactive services: UL 64Kbps and DL 384Kbps.

5. All the radio performance indices of the cell (the cell provides both CS and PS services) are good.

6. Testing UE A, B and C have all finished PLMN selection, cell selection, and location update. And

they are in the idle state.

7. Through a special data cable, testing UE is connected to a computer with USB interfaces and dial-up

connection.

Procedure: 1. The computer dials up via testing UE and then PDP is activated successfully.

2. Testing UE accesses the FTP server via the PING command.

3. Log into the FTP server with an FTP tool in testing UE, and then upload files to the FTP server and

download files from it. The uploading and downloading processes should both last for 5 minutes, and

the actual traffic and speed should be counted via Dumeter or Wireshark.

4. After file uploading and downloading are completed, exit the FTP server.

5. Disconnect the dial-up connection to release the call originated by testing UE.

Acceptance Criteria: 1. Testing UE can log into the FTP server successfully.

2. Files can be successfully downloaded from the FTP site, and the downloaded files remain complete.

3. For testing UE A, the average DL speed is no less than 60Kbps. For testing UE B, the average DL

speed is no less than 120Kbps. For testing UE C, the average DL speed is no less than 350Kbps

4. Files can be successfully uploaded to the FTP site, and the uploaded files remain complete. The

average UL speed is no less than 56Kbps.

5. The signaling of PS service establishment is normal.

Remarks: None



3.1.4 HSPA Service Test

No. and Item 3.1.4.1 HSDPA Service


2. The HSDPA cell has been established successfully.

3. Testing UE A and B have finished PLMN selection, cell selection, and location update. And they are

in the idle state.

4. USIM card of testing UE A has subscribed for the Type-I or Type-B services: UL 128Kbps and DL

4096Kbps. And the maximum DL speed of testing UE A can reach 3.6Mbps.

5. USIM card of testing UE B has subscribed for the Type-I or Type-B services: UL 128Kbps and DL

8192Kbps. And the maximum DL speed of testing UE A can reach 7.2Mbps.

6. All the radio performance indices of the cell are fine.


connection.

Procedure: 1. The computer dials up via testing UE and originates the PS service in the HSDPA cell. After that,

PDP is activated successfully.


3. Log into the FTP server with an FTP tool in testing UE, and then download files from the FTP server.

The downloading process should last for 5 minutes, and the actual traffic and speed should be

counted via Dumeter or Wireshark.

4. After file downloading is completed, exit the FTP server.


Acceptance Criteria: 1. For testing UE A, the average DL speed is no less than 3Mbps.

2. For testing UE B, the average DL speed is no less than 5Mbps.

3. The signaling of HSDPA service establishment is normal.

Remarks: 1. If the transmission bandwidth of the site or the cell throughput is limited, the tests on testing UE A

and testing UE B shall not be conducted simultaneously.

2. HSPA services have a heavier demand on the network - for UE A test point, CQI should be larger

than 20, and it is the same for UE B test point.

3. For testing UE A, the HSDPA cell shall have at least 5 HS-PDSCH code channels.

4. For testing UE B, the HSDPA cell shall have at least 10 HS-PDSCH code channels.

5. There is no other HSDPA user in the tested cell.



No. and Item 3.1.4.2 HSUPA Service


2. The HSUPA cell has been established successfully.

3. Testing UE has finished PLMN selection, cell selection, and location update. And it is in the idle

state.

4. USIM card of testing UE has subscribed for the Type-I or Type-B services: UL 2048Kbps and DL

384Kbps. And the maximum UL speed of testing UE A can reach 1.8Mbps.

5. All the radio performance indices of the cell are fine.


connection.

Procedure: 1. The computer dials up via testing UE and originates the PS service in the HSUPA cell. After that,

PDP is activated successfully.


3. Log into the FTP server with an FTP tool in testing UE, and then upload files to the FTP server. The

uploading process should last for 5 minutes, and the actual traffic and speed should be counted via

Dumeter or Wireshark.

4. After file uploading is completed, exit the FTP server.


Acceptance Criteria: 1. The average UL speed is no less than 1.5Mbps.

2. The signaling of HSUPA service establishment is normal.

Remarks: 1. The transmission bandwidth of the site and the cell throughput shall not be limited. 2. There is no other HSUPA user in the tested cell.



3.1.5 Concurrent Service Test

No. and Item 3.1.5.1 AMR 12.2Kbps, PS Domain UL64Kbps DL64Kbps


2. USIM card of testing UE has subscribed for the interactive services: UL 64Kbps and DL 64Kbps.

3. The signaling tracing software is used to monitor the Iu interface.

4. The cell should support R99 and all the radio performance indices of the cell are fine.


connection.


state.

Procedure: 1. Testing UE originates a CS12.2K call. Hold on the call after it is put through.

2. The computer dials up via testing UE and PDP is activated successfully.






6. Disconnect the dial-up connection and PDP is deactivated successfully.

7. Testing UE hangs up to release the call.

Acceptance Criteria: 1. Testing UE can talk. The audio quality is satisfying and there is no obvious delay.

2. When testing UE originates the PS service during the talk, the CS service is not affected.

3. After the PS service is finished, the CS service is still not affected.

Remarks: 1. Testing UE must support the concurrent service of AMR 12.2Kbps and PS Domain UL64Kbps

DL64Kbps.









connection.


state.














DL128Kbps.









connection.


state.














DL384Kbps.



3.2 Handover Test

3.2.1 Softer Handover

No. and Item 3.2.1.1 Softer Handover of CS12.2K Voice Service

Prerequisites: 1. Cell 1 and Cell 2 of the same frequency are set up under the same NodeB. They are adjacent cells

and some of their coverage areas overlap.


in the idle state.

3. The signaling tracing software is used to monitor the Uu interface.

Procedure: 1. Testing UE A and B are both in the area where is only covered by Cell 1. Testing UE A originates a

CS12.2K call to testing UE B. Hold on the call after it is put through.

2. Testing UE A moves from the area where is only covered by Cell 1 into the area covered by both

Cell 1 and Cell 2, then moves into the area only covered by Cell 2. Testing UE B remains still in the

original place.

3. Observe the signaling statistics of “Active Set Update” and “Active Set Update Complete” at the Uu

interface.

Acceptance Criteria: 1. When testing UE A is moving, the call remains normal and the voice is clear without interruption or

delay.

2. In the signaling statistics of testing UE A, the signaling flow of radio link adding and deleting appears

at least once, and the flow of active set update appears at least twice.

3. In one of the active set updates, the scrambling code of one added cell is the same as that of Cell 2;

while in another active set update, the scrambling code of one deleted cell is the same as that of Cell

1.

Remarks: 1. Step 2 “Testing UE A moves from the area where is only covered by Cell 1 into the area covered by

both Cell 1 and Cell 2, then moves into the area only covered by Cell 2. Testing UE B remains still in

the original place.” is equivalent to “Testing UE A is located in the overlapped coverage area of Cell

1 and Cell 2. Gradually reduce the transmitting power of Cell 1 and increase that of Cell 2 gradually.”

Either of the above test methods can be used according to the specific test environment.

2. The subsequent handover test items are the same as this one. Besides, refer to Appendix B Basic Service Signaling Flow to see the related signaling flows for handovers.



No. and Item 3.2.1.2 Softer Handover of Videophone Service

Prerequisites: 1. Cell 1 and Cell 2 of the same frequency are set up under the same NodeB. They are adjacent cells

and some of their coverage areas overlap.


in the idle state.

3. Testing UE A and B both support the videophone service.



videophone call to testing UE B. Hold on the call after it is put through.



original place.


interface.

Acceptance Criteria: 1. When testing UE A is moving, the call remains normal and the voice is clear. The image is good and

stable. There is no obvious interruption or delay.





1.

Remarks: None



No. and Item 3.2.1.3 Softer Handover of PS384K Service

Prerequisites: 1. Cell 1 and Cell 2 of the same frequency are set up under the same Node. Some of their coverage

areas overlap.

2. Testing UE A has finished PLMN selection, cell selection, and location update. And it is in the idle

state.

3. The USIM card of testing UE A has subscribed for the PS service UL 64Kbps/DL 384Kbps.


Procedure: 1. Testing UE A is in the area where is only covered by Cell 1. It originates a PS service.


Cell 1 and Cell 2, then moves into the area only covered by Cell 2.


interface.

Acceptance Criteria: 1. When testing UE A is moving, the PS service remains normal, and there is no obvious interruption or

delay.





1.

Remarks: None



No. and Item 3.2.1.4 Softer Handover of CS12.2K+PS128Kbps Concurrent Service

Prerequisites: 1. Cell 1 and Cell 2 of the same frequency are set up under the same Node. Some of their coverage

areas overlap.


in the idle state.





2. Testing UE A originates a PS service.



original place.


interface.

Acceptance Criteria: 1. When testing UE A is moving, the call remains normal and the voice is clear. There is no obvious

interruption or delay. And the PS service also remains normal and has no obvious interruption or

delay.





1.

Remarks: None



3.2.2 Intra-RNC Inter-NodeB Soft handover between Two Cells

No. and Item 3.2.2.1 Soft Handover of CS12.2K Voice Service

Prerequisites: 1. In the same RNC, Cell 1 is set up under NodeB A and Cell 2 is set up under NodeB B. They are

adjacent cells and have the same frequency. Besides, some of their coverage areas overlap.


in the idle state.






original place.


interface.


delay.





1.

Remarks: None



No. and Item 3.2.2.2 Soft Handover of Videophone Service




in the idle state.







original place.


interface.

Acceptance Criteria: 1. When testing UE A is moving, the call remains normal and the voice is clear. The image is good and

stable. There is no obvious interruption or delay.





1.

Remarks: None



No. and Item 3.2.2.3 Soft Handover of PS384K Service




state.







interface.

Acceptance Criteria: 1. When testing UE A is moving, the PS service remains normal, and there is no obvious interruption or

delay.





1.

Remarks: None



No. and Item 3.2.2.4 Soft Handover of CS12.2K+PS128K Concurrent Service




in the idle state.








original place.


interface.



delay.





1.

Remarks: None



3.2.3 Intra-CN Inter-RNC Soft Handover between Two Cells

No. and Item 3.2.3.1 Soft Handover of CS12.2K Voice Service

Prerequisites: 1. In the same CN, there are RNC A and RNC B. Cell 1 is set up under RNC A and Cell 2 is set up

under RNC B. They are adjacent cells and have the same frequency. Besides, some of their

coverage areas overlap.


in the idle state.

3. There is Iur interface connection between RNC A and B.

4. The signaling tracing software is used to monitor the Uu interface of RNC A.



2. Testing UE A moves from the area only covered by Cell 1 into the area covered by both Cell 1 and

Cell 2 until the signaling trace software shows the soft handover is triggered, and then testing UE A

returns to the area where is only covered by Cell 1. Testing UE B remains still in the original place.


interface of RNC A.


interruption or delay.

2. In the signaling statistics of testing UE A, the signaling flow of radio link adding and deleting

appears at least once, and the flow of active set update appears at least twice.

3. In one of the active set updates, the scrambling code of one added cell is the same as that of Cell

2; while in another active set update, the scrambling code of one deleted cell is the same as that of

Cell 2.

Remarks: None



No. and Item 3.2.3.2 Soft Handover of Videophone Service





in the idle state.










interface of RNC A.

Acceptance Criteria: 1. When testing UE A is moving, the call remains normal and the voice is clear. The image is good

and stable. There is no obvious interruption or delay.





Cell 2.

Remarks: None



No. and Item 3.2.3.3 Soft Handover of PS384K Service





state.







returns to the area where is only covered by Cell 1.


interface of RNC A.

Acceptance Criteria: 1. When testing UE A is moving, the PS service is normal and there is no obvious interruption or

delay.





Cell 2.

Remarks: None



No. and Item 3.2.3.4 Soft Handover of CS12.2K+PS128K Concurrent Service





in the idle state.











interface of RNC A.



delay.




while in another active set update, the scrambling code of one deleted cell is the same as that of

Cell 2.

Remarks: None



3.2.4 Intra-NodeB Hard Handover between Two Cells

No. and Item 3.2.4.1 Hard Handover of CS12.2K Voice Service

Prerequisites: 1. Cell 1 and Cell 2 are set up under the same NodeB, but they have different frequencies. Some of

their coverage areas overlap.

2. Testing UE A has finished location update in Cell 1, and testing UE B has finished location update in

Cell 2.


Procedure: 1. Testing UE A originates a CS12.2K call to testing UE B. Hold on the call after it is put through.



original place.

3. Observe the signaling statistics of testing UE A, such as “Physical Channel Reconfiguration” and

“Physical Channel Reconfiguration Complete” at the Uu interface.


delay.

2. In the signaling statistics of testing UE A, the signaling flow of radio link reconfiguration appears at

least once.

Remarks: None



No. and Item 3.2.4.2 Hard Handover of Videophone Service



2. Testing UE A has finished location update in Cell 1, and testing UE B has finished location update in

Cell 2.


Procedure: 1. Testing UE A is in the area where is only covered by Cell 1and it originates a videophone call to

testing UE B. Hold on the call after it is put through.



original place.






least once.

Remarks: None



No. and Item 3.2.4.3 Hard Handover of PS384K Service



2. Testing UE A has finished location update in Cell 1.









delay.


least once.

Remarks: None



No. and Item 3.2.4.4 Hard Handover of CS12.2K+PS128K Concurrent Service




in the idle state.

3. The static AMR of RNC is set as 12.2Kbps.








original place.





delay.


least once.

Remarks: None



3.2.5 Intra-RNC Inter-NodeB Handover between Two Cells

No. and Item 3.2.5.1 Hard Handover of CS12.2K Voice Service

Prerequisites: 1. In the same RNC, Cell 1 is set up under NodeB A and Cell 2 is set up under the NodeB B. Cell 1

and Cell 2 have different frequencies. Some of their coverage areas overlap.

2. Testing UE A has finished location update in Cell 1, and testing UE B has finished location update

in Cell 2.





original place.






least once.

Remarks: None



No. and Item 3.2.5.2 Hard Handover of Videophone Service




in Cell 2.






original place.






least once.

Remarks: None



No. and Item 3.2.5.3 Hard Handover of PS384K Service












delay.


least once.

Remarks: None



No. and Item 3.2.5.4 Hard Handover of CS12.2K+PS128K Concurrent Service




in the idle state.








original place.





delay.


least once.

Remarks: None



3.2.6 Intra-CN Inter-RNC Hard Handover between Two Cells of Different Frequency

No. and Item 3.2.6.1 Inter-frequency Hard Handover of CS12.2K Voice Service

Prerequisites: 1. In the same CN, Cell 1 is set up under RNC A and Cell 2 is set up under RNC B. Cell 1 and Cell 2

have different frequencies. Some of their coverage areas overlap.


in Cell 2.





original place.






least once.

Remarks: None



No. and Item 3.2.6.2 Inter-frequency Hard Handover of Videophone Service




in Cell 2.






original place.






least once.

Remarks: None



No. and Item 3.2.6.3 Inter-frequency Hard Handover of PS384K Service









3. Observe the signaling statistics of “Physical Channel Reconfiguration” and “Physical Channel

Reconfiguration Complete” at the Uu interface.


delay.


least once.

Remarks: None



No. and Item 3.2.6.4 Inter-frequency Hard Handover of CS12.2K+PS128K Concurrent Service



2. Testing UE A and B have finished PLMN selection, cell selection, and location update. And they

are in the idle state.









original place.





delay.


least once.

Remarks: None



3.2.7 Intra-CN Inter-RNC Hard Handover between Two Cells of Common Frequency

No. and Item 3.2.7.1 Common-frequency Hard Handover of CS12.2K Voice Service


have the same frequency. Some of their coverage areas overlap.



in Cell 2.

4. There is no Iur interface between RNC A and RNC B.





original place.






least once.

Remarks: None



No. and Item 3.2.7.2 Common-frequency Hard Handover of Videophone Service




in Cell 2.







original place.






least once.

Remarks: None



No. and Item 3.2.7.3 Common-frequency Hard Handover of PS384K Service










3. Observe the signaling statistics of “Physical Channel Reconfiguration” and “Physical Channel

Reconfiguration Complete” at the Uu interface.


delay.


least once.

Remarks: None



No. and Item 3.2.7.4 Common-frequency Hard Handover of CS12.2K+PS128K Concurrent Service



2. Testing UE A and B have finished PLMN selection, cell selection, and location update. And they

are in the idle state.










original place.





delay.


least once.

Remarks: None



3.3 IOT between UMTS and GSM/GPRS

No. and Item 3.3.1 Cell Reselection in CS (UMTS→ GSM)

Prerequisites: 1. All the equipment in the UMTS and GSM systems work normally, and the links between the two

systems are in the normal state.

2. The UMTS and GSM systems have both been configured with correct parameters.

3. Cell 1 is set up in the UMTS system, Cell 2 is set up in the GSM system, and some of their


4. Testing UE A and B have finished location update in Cell 1.

5. Testing UE A supports dual modes of UMTS and GSM.

6. The signaling tracing software is used to monitor the signaling of testing UE A at the Uu, Iu and A

interfaces.

Procedure: 1. Testing UE A and B are both in the idle state;



original place.

3. Observe the signaling statistics at the Uu, Iu and A interfaces to see testing UE A reselect and

access Cell 2 of the GSM system, and complete location update in Cell 2.

4. Testing UE A originates a CS12.2K voice call to testing UE B in Cell 2.

Acceptance Criteria: 1. The call can be completed successfully and the call quality is satisfying.

2. In the signaling statistics at the Iu interface of testing UE A, the signaling flow of “Relocation

Required” appears at least once. In the signaling statistics at the A interface of testing UE A, the

flow of location update appears at least once.

Remarks: None



No. and Item 3.3.2 Cell Reselection in CS (GSM→ UMTS)








6. The signaling tracing software is used to monitor the signaling of testing UE A at the Uu and Iu

interfaces.

Procedure: 1. Testing UE A and B are both in the idle state;



original place.

3. Observe the signaling statistics at the Uu and Iu interfaces to see testing UE A reselect and access

Cell 1 of the UMTS system, and complete location update in Cell 1.

4. Testing UE A originates a CS12.2K voice call to testing UE B in Cell 1.

Acceptance Criteria: 1. In the signaling statistics at the Uu and Iu interfaces of testing UE A, the signaling flow of location

update appears at least once.

2. After testing UE A updates the location successfully, it can successfully originate and complete the

call to testing UE B. And the call quality is satisfying.

Remarks: None



No. and Item 3.3.3 Inter-System Handover of CS12.2K Voice Call (UMTS→ GSM)







5. Testing UE A and B both support dual modes of UMTS and GSM.


interfaces.

Procedure: 1. Testing UE A is both in the area where is only covered by Cell 1. It originates a CS12.2K call to




original place.

3. Observe the signaling statistics at the Uu and Iu interfaces to see the inter-system handover flow is

triggered and there is a “Relocation Required” message at the Iu interface.



2. In the signaling statistics at the Iu interface of the testing UE A, the signaling flow of “Relocation

Required” appears at least once. In the signaling statistics at the Uu interface, the signaling flow of

“Handover from UTRAN” appears at least once.

Remarks: None



No. and Item 3.3.4 Inter-System Handover of CS12.2K Voice Service (GSM→ UMTS)









interfaces.

Procedure: 1. Testing UE A is both in the area where is only covered by Cell 2. It originates a CS12.2K call to




original place.

3. Observe the signaling statistics at the Uu and Iu interfaces to see the inter-system handover flow is

triggered and there is a “Relocation Request” message at the Iu interface.



2. In the signaling statistics at the Iu interface of the testing UE A, the signaling flow of “Relocation

Request” appears at least once. In the signaling statistics at the Uu interface, the signaling flow of

“Handover To UTRAN Complete” appears at least once.

Remarks: None



No. and Item 3.3.5 PS Cell Reselection (UMTS→ GSM/GPRS)







5. Testing UE A supports dual modes of UMTS and GSM/GPRS.

6. The signaling tracing software is used to monitor the signaling of testing UE A at the Uu, Iu and Gb

interfaces.

Procedure: 1. Testing UE A launches a PS service in Cell 1, pings through the FTP server, completes the file

downloading, and finally stops all operations.

2. During a period (e.g. 20 minutes, which can be set according to the network parameters), UE

keeps in the idle state and the network designates the UE to change into the CELL_PCH status.



original place.

4. Observe the signaling statistics at the Uu, Iu and Gb interfaces to see testing UE A complete

reselection, access Cell 2 of the GPRS system, and then complete the routing area update in Cell

2.

5. Testing UE B launches a GPRS service in Cell 2 and pings through the server.

Acceptance Criteria: 1. Testing UE A in Cell 2 can successfully download files from the FTP site, and the downloaded files

are complete.

2. In the signaling statistics of testing UE A at the Iu interface, the signaling flow of “SRNS

ContextRequest/Response” appears at least once. And in the signaling statistics at the Gb

interface, the signaling flow of routing area update appears at least once.

Remarks: None



No. and Item 3.3.6 PS Handover (UMTS→ GSM/GPRS)









interfaces.

7. The subscribed services include the background service.

Procedure: 1. Testing UE A launches a PS service in Cell 1 and pings through the FTP server.


Cell 1 and Cell 2, then moves into the area only covered by Cell 2. Testing UE A has an instant

attenuation from Cell 1 but has no handover.

3. Observe the signaling statistics at the Uu and Iu interfaces to see testing UE A complete

reselection, access Cell 2 of the GPRS system, and then complete the routing area update in Cell

2.

4. UE A switches to the GPRS service and successfully pings through the FTP server.

5. Use Wireshark or Dumeter software to monitor the PS transmission rate.

Acceptance Criteria: 1. During the whole test process, testing UE A can always ping through the FTP server and

successfully download files.


ContextRequest/Response” appears at least once. In the signaling statistics of testing UE A at the

Gb interface, the signaling flow of routing area update appears at least once.

Remarks: None



No. and Item 3.3.7 PS Handover (GSM/GPRS→ UMTS)









interfaces.

7. The subscribed services include the background service.

Procedure: 1. Testing UE A launches a PS service in Cell 2, successfully pings through the FTP server and

downloads the file.


Cell 1 and Cell 2, then moves into the area only covered by Cell 1. Testing UE A has an instant

attenuation from Cell 2 but has no handover.

3. Observe the signaling statistics at the Uu and Iu interfaces to see testing UE A complete

reselection, access Cell 1 of the UMTS system, and then complete the routing area update in Cell

1.

4. UE A switches to the PS service and successfully pings through the FTP server.

Acceptance Criteria: 1. Testing UE A in Cell 1 can successfully download files from the FTP server, and the downloaded

files are complete.


ContextRequest/Response” appears at least once. In the signaling statistics of testing UE A at the

Uu interface, the signaling flow of routing area update appears at least once.

3. The handover signaling is normal.

4. The PS data transmission interval is shorter than 5 seconds.

Remarks: None


Confidential and Proprietary Information of ZTE CORPORATION. A-1

Appendix A Board LED Indicators

A.1 LED Indicators There are all kinds of LED indicators on the panels of RNC boards. Working state of the board is shown by the LED indicator status. Table A-1 lists the LED indicator states.

Table A-1 LED State Description

SN. State Description

1 ON LED indicator is bright all the time

2 OFF LED indicator is extinguished all the time

3 Flash at 5 Hz Period is 0.2s: keep ON for 0.1s and OFF for 0.1s

4 Flash at 2 Hz Period is 0.5s: keep ON for 0.25s and OFF for 0.25s

5 Flash at 1 Hz Period is 1s: keep ON for 0.5s and OFF for 0.5s

6 Flash at 0.5 Hz Period is 2s: keep ON for 1s and OFF for 1s



A.2 LED Control Rules

A.2.1 Board Power-on See Figure A-1 below to check the LED changes when the board is powered on.

Start

All LEDs are on

ENUM is onOther LEDs are off

Whether all board spanners are well

plugged?

ENUM LED is off

RUN LED flashes quickly

RUN LED is off

RUN LED flashes slowly

The end

Yes

No

Figure A-1 LED Changes for Board Power-on



A.2.2 Hardware Reset See Figure A-2 to check the LED changes in the hardware reset procedure.

Start

All LEDs are on

The End

ALM LED is off for about 200ms

All LEDs are on

After BOOT is successfully loaded, software controls the

LEDs.

Figure A-2 LED changes of Hardware Reset

A.2.3 ENUM LED Indicator ENUM is separate from other LED indicators, which is used to indicating the status of the board connection/ disconnection with tact switch. Refer to Table A-2 for detailed description of ENUM.

Table A-2 Board ENUM LED Status and Description

Running Phase ENUM Status Description

Turn on tact switch ON The board is not properly plugged, so the process

of power-up is paused (tact switch is open).

Tact switch alarm Flash at 5 Hz Tact switch is turned off to alarm during the board

running.

Board may be unplugged Flash at 1 Hz

During the board running, tact switch is turned off,

the board is in standby status or released the

resources, and can be unplugged.

Tact switch is normal OFF Board is in normal state (Tact switch is close).



A.2.4 Master/Slave (ACT) LED Indicator LED ACT status indicates the status of Master/Slave board. The boards without backup ones are defaulted as the active ones. See the Table A-3 for detailed information.

Table A-3 Board ACT LED Status and Description

Running Phase ACT Status Description

Active board ON The board is in active status.

Standby board OFF The board is in standby status.

A.2.5 RUN and ALM LED Indicators All kinds of the LED status in the sequence from power-up to work are listed in Table A-4.

Table A-4 RUN&ALM Status and Description

Running Phase RUN Status ALM Status Description

Normal running Flash at 1 Hz OFF Normal running

Version download

Flash at 5 Hz OFF Downloading

Flash at 1 Hz Flash at 5 Hz Configuration error, version download

can not start up

ON OFF Download succeeded, in process of

version start up

Self-check failed OFF Flash at 5 Hz Board self check failure

OFF Flash at 2 Hz OS start up failure

Fault alarm in the

running course

Flash at 5 Hz Flash at 5 Hz Logic address acquisition failure

Flash at 5 Hz Flash at 2 Hz Basic Procedure power-on failure or

timeout

Flash at 5 Hz Flash at 1 Hz Core data area initialization failure

Flash at 2 Hz Flash at 5 Hz Alarm for version not matching

hardware and configuration

Flash at 2 Hz Flash at 2 Hz Communication with the media plane

disconnected

Flash at 2 Hz Flash at 1 Hz HW broken

Flash at 1 Hz Flash at 2 Hz Link with OMP broken

Flash at 1 Hz Flash at 1 Hz Media plane communication broken

Unchanged ON Hardware clock missing

A.2.6 Special LED Indicators Besides General LED (ENUM/ALM/RUN/ACT), some boards have their special LED indicators (E/AL/R/AC). Refer to for the descriptions.

Table A-5 Status Description of all LED indicators

Board LED Software

controllableDescription



Board LED Software


UIM-2

E/AL/R/AC Yes

The LED ACT cannot be controlled by software. It,

as the main LED of board, is ON when CS or PS is

mainly used.

ACT-P No It is the main LED in PS, which is ON when the

board PS is in main use.

ACT-T No It is the main LED in CS, which is ON when the

board CS is in main use.

ACT1 No Optical port 1 is in use when GXS subcard is

plugged

ACT2 No Optical port 2 is in use when GXS subcard is

plugged

LINK1 No It is ON if the back-board FE-C1 port is link up



LINK4 No It is ON if the back-board FE-C4port is link up

SD1 No There are signals through optical port 1 when

plugging GXS subcard.

SD2 No There are signals through optical port 2 when

plugging GXS subcard.

SD3 No There are signals through No.1 TDM optical port

when TDM optical port used.

SD4 No There are signals through No.2 TDM optical port

when TDM optical port used.

CHUB E/AL/R/AC Yes

The same as the description in A.2.3, A.2.4 and

A.2.5, where the LED ACT is not controlled by

software.

L1~46 No On: corresponding port on CHUB is UP

GIPI

ENUM

RUN

ALM

ACT

Yes The general LED, please refer to the description in

A.2.3, A.2.4 and A.2.5.

MPX86 E/AL/R/AC Yes The same as the description in A.2.3, A.2.4 and

A.2.5.

DTB

E/AL/R/AC Yes The same as the description in A.2.3, A.2.4 and

A.2.5.

E1 LED Yes

OFF: E1 link not configured

ON: E1 link configured but not connected

Flash at 1Hz: E1 link configured and connected

IMAB E/AL/R/AC Yes The same as the description in A.2.3, A.2.4 and

A.2.5.

APBE E/AL/R/AC Yes The same as the description in A.2.3, A.2.4 and

A.2.5.



Board LED Software


Optical port

LED ACT No

indicating Master/Slave state. ACT LED indicator is

ON when optical port is active and ACT LED

indicator is OFF when optical port is standby.

Optical port

LED SD No

SD1-SD4 are 4 optical port LED indicators. SD LED

indicator is ON when fiber plugged, and SD LED

indicator is OFF when fiber unplugged.

PSN E/AL/R/AC Yes The same as the description in A.2.3, A.2.4 and

A.2.5.

GLI


A.2.5.

Optical port

ACT No

The LED indicator is ON until there are program

running in FPGA. The LED starts flashing according

to running data after program runs normal.

Optical port SD No ON: there are data running through optical port

ICM


A.2.5.

CATCH Yes Working status LED of ICM board swift catching

TRACE Yes Working status LED of ICM board tracing

KEEP Yes Working status LED of ICM board holding

FREE Yes Working status LED of ICM board free running

2Mbits1 Yes 2Mbits1 clock reference selection LED. LED ON

shows this clock reference is selected.

2Mbits2 Yes 2Mbits2 clock reference selection LED. LED ON


2MHZ1 Yes 2MHZ1 clock reference selection LED. LED ON


Yes 2MHZ2 clock reference selection LED. LED ON


8K1 Yes ON shows clock reference is 8K from transmission.

8K2 Yes ON shows clock reference is 8K from active GPS

board.

8K3 Yes ON shows clock reference is 8K from UIM.

NULL Yes ON shows no clock reference is available.

QUTD Yes Clock reference quality debased LED. Red light ON

shows current clock reference quality debased.

MANI Yes ON shows manual selection is enabled.

PWRD

RUN Yes

It flashes at 1Hz when the board is running normally.

It flashes at 5Hz when the version software is

updating,

-48VI Yes -48VI alarm LED. ON shows alarm, OFF shows no

alarm

-48VII Yes -48VII alarm LED. ON shows alarm, OFF shows no

alarm



Board LED Software


FAN Yes Fan alarm LED. ON shows at least one fan is faulty,

OFF shows no alarm

HOT Yes Temperature alarm LED. ON shows alarm, OFF

shows no alarm

SMOKE Yes Smoke alarm LED, ON shows alarm, OFF shows no

alarm

DOOR Yes Door alarm LED. ON shows alarm for door opened,

OFF shows no alarm for door closed.

ARRESTER Yes Lightning strike alarm LED. ON shows alarm, OFF

shows no alarm

A.3 Supplementary Description

A.3.1 LED Indicator Status upon Board Startup During the BSP initialization and reset, all the LED indicators shall be ON for 0.5 seconds, and then all be off, which shall indicates that whether there are LED indicators broken. If any software controlled LED has not been ON in this procedure, then it is broken.

BSP shall check whether the tact switch is turned off: if not, LED ENUM shall be on while other LED indicators can be controlled shall be turned off, and it continues to query the tact switch status till the switch is turned off. Then the ENUM is off and enter into the version download procedure.

When the version is downloading, LED RUN flashes at 5 Hz and ALM is off.

Version Debug: the process of downloading VxWork. After VxWorks download is completed, the LED RUN is off, and turn on the LED RUN to remind that the downloading and running of VxWorks are successful. Wait for downloading and running of *.o version.

Version Release: during downloading the CPU version, if the board is inconsistent with the configuration, the version download failed or is incapable to download, as a result, the LED RUN flashes at 1 Hz, ALM flashes at 5 Hz, and board starting stops. Otherwise, reboot the boards. After version download is completed, turn off the LED Run to show the version download is successfully completed. When the version starts running, the LED RUN should be on till it runs normally.

A.3.2 Fault Alarm LED Indicator If some faults occur during the version running, light the LED according to the specifications, and reboot the board 1 minute later.



A.3.3 ICM LED Description See Table A-6 for the ICM LED description.

Table A-6 ICM LED Description

LED Color Meaning Description

RUN Green Running

Flash at 1Hz: the board runs normally.

ON: the crystal inside is preheating.

OFF: the board is abnormal.

ENUM Yellow

Board

Plugging/unplu

gging

ON: the board is plugged into the slots. Defaulted as

ON, that is, it is ON during the power-on procedure

and the software has not been started yet.

OFF: the software has detected the ENUM signaling

and the spanners of board have been closed. It is

OFF to show the system starts working.

Board plugging/unplugging: if the boards need be

unplugged, open the spanner and the tact switch

shall generate a ENUM intermitting signaling to the

CPU, then the CPU under the system control shall

show the work status. The LED ENUM is ON

(meantime, check whether the ENUM signaling is

changing) to show the boards are ready to be

unplugged. If LED ENUM is OFF, you cannot unplug

the boards by force, otherwise the service may be

missing.

If the maintenance personnel did not unplug the

boards, but close the spanner, the software can

query the change of ENUM signaling. The software

shall restart working; meantime, the LED ENUM is

off.

ACT Green Master/Slave ON: the board is active

OFF: the board is standby

ALM Red Alarm ON: it shows the board has detected the SRAM

failure and the output clock missing.

CATCH Green Catching ON: the board is in the quick-catch status, that is,

there are clock references, but board is not locked.

TRACE Green Tracing ON: the board is in the tracing status, that is, there

are clock reference, but board is not locked.

KEEP Green Keeping ON: the board is locked, but the clock reference is

missing during the process.

FREE Green Free running ON: the board has is not locked, has no clock

reference, and is in free status.

2Mbps1 Green Clock

reference

It is used to indicating the clock reference selected

by ICM board.

ON: the No. 1 2M clock reference provided by BITS

in the HDB3 code transmission format is selected.



LED Color Meaning Description

2Mbps2 Green Clock

reference


by ICM board.


in the HDB3 code transmission format is selected.

2MHz1 Green Clock

reference


by ICM board.


in the TTL difference transmission format is selected.

2MHz2 Green Clock

reference


by ICM board.

ON: the No.2 2M clock reference provided by in the

TTL difference transmission format is selected.

8K1 Green Clock

reference

It is used to indicate the clock reference selected by

ICM board.

ON: the clock reference is 8K from the boards such

as DTB, APBE, SDTB and SPB.

8K2 Green Clock

reference


ICM board.

ON: the clock reference is 8K from GPS.

8K3 Green Clock

reference


ICM board.

ON: the clock reference is 8K from UIM.

NULL Green Clock

reference


ICM board.

ON: no external clock reference is available.

QUID Red Quality

degrade

ON: the clock reference is debased, on level III or

lower standards.

MANI Green

Manual

operations are

allowed

ON: clock reference can be manually selected.

OFF: clock reference cannot be manually selected.

A.3.4 Plane LED Indicators 1. The LED indicators RUN, CATCH, TRACE, KEEP and FREE flash

simultaneously.

It shows the board is preheating. Board usually takes 8 minutes to preheat during the power-on procedure.

2. RUN is flashing.

It shows the MCU board works normally.

3. ALM is ON.

It shows the board alarms may caused by following reasons:

SRAM self-check failure

16M, 32M, 8K_16M, or 8K_32M input clock missing

There is PP2S clock input, but the PP2S clock is missing after broadening.



The OCXO constant temperature slot alarm is used in the phase-locked loop.

4. LED QUTD is ON.

It shows the clock reference used in board has been debased.

5. LED CATCH is ON.

It shows the board is in the quick-catch status, that is, there is clock reference, but the board is not locked.

6. LED TRACE is ON. It shows the board is in the tracing status, that is, there is clock reference, and the board is locked.

7. LED KEEP is ON. It shows the board is in the keeping stats, that is, there is no clock reference, and the board is locked.

8. LED FREE is ON. It shows the board is in free stats, that is, there is no clock reference, and the board is not locked.

9. LED CATCH or TRACE is flashing. It shows the current authorization of the phase-locked loop failed, which usually caused by the input clock reference fault.

10. LED CATCH and TRACE are flashing simultaneously. It shows the current clock reference exceeds the catching scope of the clock board and cannot be locked.

11. When the board is reset or powered on, all the LED shall be ON and then be OFF. This process shall be repeated for twice.

The first time is to open the BOOT program, and the second time is to open the version program.

12. LED RUN is flashing at 5 Hz. The single-chip microcomputer version program is auto-updating.

A.3.5 PWRD LED Description See Table A-7 for the PWRD LED description.

Table A-7 PWRD LED Description

LED Description

RUN It flashes at 1Hz when the board is running normally. It flashes at 5Hz

when the version software is updating,

-48 VI -48VI alarm LED. ON shows alarm, OFF shows no alarm

-48 VII -48VII alarm LED. ON shows alarm, OFF shows no alarm

FAN Fan alarm LED. ON shows at least one fan is faulty, OFF shows no

alarm

HOT Temperature alarm LED. ON shows alarm, OFF shows no alarm

SMOKE Smoke alarm LED, ON shows alarm, OFF shows no alarm

DOOR Door alarm LED. ON shows alarm for door opened, OFF shows no

alarm for door closed.

ARRESTER Lightning strike alarm LED. ON shows alarm, OFF shows no alarm



A.3.6 LED Lightening for Clock Missing If the software found the clock is missing, the ALARM indicator should be ON.


Confidential and Proprietary Information of ZTE CORPORATION. B-1

Appendix B Basic Service Signaling Flows B.1 Signaling Flowchart of CS Domain

UE(MT)RNCCNRNCUE(MO)

MSC SignallingWcdma

Downlink Direct Transfer

(Connect Acknowledge )

Direct Transfer


Direct Transfer


Uplink Direct Transfer



( Connect)

Direc t Transfer

( Connect)

Direct Transfer

( Conncect)Uplink Direct Transfer

( Connect)


(Alerting)

Direc t Transfer

(Alerting)

Direct Transfer

(Alerting)


(Alerting)

Direct T ransfer

(Call proceeding)Downlink Direct Transfer

( Call proceeding)

RAB Assignment ResponseRadio Bearer Setup Complete

Radio Bearer SetupRAB Assignment Request

(Establish)

RAB Assignment Request

( Establish)

Direct Transfer

(Call Confirm)


(Call Confirm)


(Call Setup)

Direct Transfer(Call Setup )

Paging

Initial UE Message

( Paging Response)

Initial Direct Transfer

(Paging Response)

RAB Assignment Response

Radio Bearer Setup

Radio Bearer Setup Complete

Paging Type 1

Direct Transfer

(Call Setup )


(Call Setup)


( CM Service Accept)

Direct T ransfer

( CM Service Accept)

Initial Ue Message

(CM Service Request )

Initial Direct Transfer

(CM Service Request )

Figure B-1 CS Paging Signaling Flowchart



B.2 Signaling Flowchart of PS Domain

B.2.1 UE Attaching Flowchart RNCUE NodeB

(1)UL-CCCH:RRC Connection Request

(2)C_NBAP:Rdaio Link Setup Request

(3)C_NBAP:Radio Link Setup Response

(4)ALCAP:ERQ

(5)ALCAP:ECF

(8)DL_CCCH:RRC Connection Setup

(9)UL_DCCH:RRC Connection Setup Complete

(10)D_NBAP:Radio Link Restore Indication

(11)UL_DCCH:Initial Direct Transfer(Attach Req)

CN

(12)Initial UE Message

(Attach Req)

(13)Direct Transfer(Attach Accept)(14)DL_DCCH:Downlink Direct Transfer

(Attach Accept)

(6)DCCH_FP:Downlink SYNC

(7)DCCH_FP:Uplink SYNC

Figure B-2 UE Attaching Flowchart



B.2.2 PDP Context Activation Flowchart RNCUE NodeB CN

(1)UL_DCCH:Uplink Direct Transfer(ACT. PDP Context Req)

(3)RAB Assginment Request

(Establishment)(4)D_NBAP:Radio Link Reconfiguration Prepare

(5)D:NBAP Radio Link Reconfiguration Ready

(10)D_NBAP:Radio Link Reconfiguration Commit

(11)DL_DCCH:Radio Bearer Setup

(12)UL_DCCH:Radio Bearer Setup Complete(13)RAB Assignment Response

(15)DL_DCCH:Downlink Direct Transfer

(ACT. PDP Context Accept)

(2)Direct Transfer(ACT. PDP Context Req)

(14)Direct Transfer

(ACT. PDP Context Accept)

(8)DTCH_FP:Downlink SYNC

(9)DCCH_FP:Uplink SYNC

(6)ALCAP-ERQ

(7)ALCAP-ECF

Figure B-3 PDP Context Activation Flowchart



B.3 UMTS Soft Handover Signaling Flow

B.3.1 Intra-NodeB Softer Handover Signaling Flow

Figure B-4 Intra-NodeB Softer Handover Signaling Flowchart



B.3.2 Intra-RNC Inter-NodeB Soft Handover Flow

Figure B-5 Intra-RNC Inter-NodeB Soft Handover Flowchart



B.3.3 Inter-RNC Soft Handover Flow

Figure B-6 Inter-RNC Soft Handover Flowchart



B.4 UMTS Hard Handover Signaling Flow

B.4.1 Intra-NodeB Hard Handover Flow between Different Cells

Radio Link Setup Req

Radio Link Setup Resp

Compressed Mode Command

Physical Channel ReconfigurationRRC RRC

Physical Channel Reconfiguration CompleteRRC RRC

NBAPNBAPRadio Link Failure Indication

NBAPNBAP

NBAP NBAP

Radio Link Deletion Req

Radio Link Deletion Resp

UE Node Bsource

RNC

NBAP NBAP

RRC RRC

RRC RRC

Measurement Control

Measurement Report

NBAP

NBAP

NBAP

NBAP

Radio Link RestoreNBAPNBAP

Figure B-7 Intra-NodeB Hard Handover Flowchart between Different Cells



B.4.2 Intra-RNC Inter-NodeB Hard Handover Flow

NBAP

Radio Link Deletion Request

Radio Link Failure Indication

NBAP

NBAPRadio Link Setup Req

Radio Link Deletion Response

Compressed Mode Command

NBAP

NBAPRadio Link Setup Resp

RRC

RRCPhysical Channel Reconfiguration Complete

RRCPhysical Channel Reconfiguration

RRC

NBAPNBAP

NBAP

NBAPNBAP

UE Node Bsource

Node Btarget

RNC

NBAPNBAP

Measurement ControlRRCRRC

Measurement ReportRRCRRC

Figure B-8 Intra-RNC Inter-NodeB Hard Handover Flowchart



B.4.3 Inter-RNC Hard Handover Flow

Figure B-9 Inter-RNC Hard Handover Flowchart (with Iur)



Figure B-10 Inter-RNC Hard Handover Flowchart (without Iur)



B.5 Intersystem Handover Signaling Flow

B.5.1 2G→3G Handover Flow

RA N A P RA N A P 3 . Relo catio n

Requ est

B SSM A P BSS M A P

1 . H an do ver Req ui red

RA N A P RA N A P

4 . Relo catio n R equ est A ck .

M A P/E M A P /E 5 . Prep are Ha n do ver

Resp on s e

M A P/E M A P /E

2 . Prepa re H an d ov er

B SSM A P BSS M A P 6 . H an do ver

Co m m an d

M A P/E M A P /E 1 1 . Sen d E nd Si gn al

Req u es t

B SSM A P BSS M A P 12 . Cl ear Co m m an d

B SSM A P BSS M A P

1 3. C lear Co m pl ete

RA N A P RA N A P

10 . Rel ocati on Co m p lete

U E N od e B

RN C Ta rg et

C N M S C BSC BT S

M A P/E M A P /E 1 4 . Sen d E nd Si gn al

Resp on s e

RR C 9 . D CC H : H an d ov er to U T R A N Co m p lete R RC

RR 7. H an d o ver C om m an d

RR

RA N A P RA N A P

8 . Rel ocati on D etect

Figure B-11 CS 2G→3G Handover Flowchart



3. Security Functions

MS BSS 2G+3G-SGSNSRNS

2. Routing Area Update Request

11. RAB Assignment Request

11. RAB Assignment

13. Packet Transfer Resume

1. Intersystem change decision

12. Packet Transfer Resume

7. Routing Area Update Accept

8. Routing Area Update Complete

Set up RadioResources

C1

newMSC/VLR

HLR oldMSC/VLR

4. Location Update Request

5a. Update Location 5b. Cancel Location

5c. Cancel Location Ac

5d. Insert Subscriber Data

5e. Insert Subscriber Data

5f. Update Location

6. Location Update Accept

9. TMSI Reallocation Complete10. Service Request

Figure B-12 PS 2G→3G Handover Flow (Intra-SGSN)



B.5.2 3G→2G Handover Flow

M A P/E M A P/E

2 . P repare H andover

B SSM A P B SSM A P

4 . H andover R equest A ck

R AN A P RA N AP

13 . Iu R elease Com plete

B SSM A P B SSM A P 3 . H andover

Request

M A P/E M A P/E

5 . P repare H andover Response

R AN A P RA N AP

6. Relocation Com m and

B SSM AP B SSM A P

8. H andover D etect

B SSM A P B SSM A P

10. H andover Com plete

M A P/E M A P/E

11. Send E nd S ignal

Request

M A P/E M A P/E

14. Send E nd Signal Response

R AN A P RA N AP

1 . Relocation Required

U E N ode B

RN C Serving

CN M SC B SC B T S

RRC

7 . D CCH : H andover from U T RA N C om m and

RRC

RR 9. H andover C om plete

RR

RA N A P RA N A P12. Iu Release

C om m and

Figure B-13 CS 3G→2G Handover Flowchart



5. Security Functions

MS SRNS 2G+3G-SGSNBSS

8. Iu Release Command

8. Iu Release Complete

6. SRNS Data Forward Command

7. Forward Packets

1. Intersystem change decision

3. SRNS Context Request

4. SRNS Context Response

2. Routeing Area Update Request

12. Routeing Area Update Accept

13. Routeing Area Update Complete

15. BSS Packet Flow Context Procedure

C1

newMSC/VLR

oldMSC/VLR

HLR

9. Location Update Request

10a. Update Location

10b. Cancel Location

10d. Insert Subscriber Data

10e. Insert Subscriber Data Ack

11. Location Update Accept

10f. Update Location

14. TMSI Reallocation Complete

10c. Cancel Location Ac

Figure B-14 PS 3G→2G Handover Flowchart (Intra-SGSN)

Documents

RNC Test Guide