ZXUR 9000 UMTS (V4.18.10) Test Guide - R1.0

ZXUR 9000 UMTS(V4.18.
10)
Test Guide
ZXUR 9000 UMTS(V4.17.10) Test Guide
LEGAL INFORMATION
Copyright © 2020 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any
reproduction or distribution of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the
contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service
marks, of ZTE CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties,
representations or conditions are disclaimed, including without limitation any implied warranty of
merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and
its licensors shall not be liable for damages resulting from the use of or reliance on the information
contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or
applications covering the subject matter of this document. Except as expressly provided in any
written license between ZTE CORPORATION and its licensee, the user of this document shall not
acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without
further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire
related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: 800@zte.com.cn
ZTE Confidential & Proprietary. © 2020 ZTE CORPORATION. All rights reserved. I
Revision History
Product Version Document Version Serial Number Reason for Revision

V4.18.10 R1.0 First published
Author
Date Document Version Prepared by Reviewed by Approved by

2018-04-02 R1.0 Hu Zhigang Chen Taiming Hu Lihua
Intended audience: RNC commissioning engineers (Internal & outsourced)
ZTE Confidential & Proprietary. © 2020 ZTE CORPORATION. All rights reserved. II
About This Document
Summary
Chapter Description
1 RNC Hardware Test Describes the RNC hardware tests.
2 State Management Test Describes the state management tests.
3 Software Version Management Describes the software version management tests.
Test
4 Service Test Describes the service tests.
ZTE Confidential & Proprietary. © 2020 ZTE CORPORATION. All rights reserved. III
TABLE OF CONTENTS
1 RNC Hardware Test.........................................................................................1

1.1 Hardware Function Test.....................................................................................1
1.1.1 Rack Fan Test....................................................................................................1
1.1.2 RNC Board Test.................................................................................................1
1.2 Reset and Switchover Test................................................................................2
1.2.1 Manual Board Reset Test on the RNC...............................................................2
1.2.2 OMC Server Restart Test...................................................................................3
1.2.3 Manual Master/Slave Changeover Test on RNC...............................................4
1.2.4 Master/Slave Changeover Test on OMC...........................................................5
1.2.5 Manual Load-Share Changeover Test on RNC..................................................6
2 State Management Test...................................................................................7

2.1 Soft Reset and Block Test..................................................................................7
2.1.1 Soft Reset and Block Test..................................................................................7
2.2 CPU Management.............................................................................................9
2.2.1 CPU Management.............................................................................................9
2.3 Dynamic Management of PVC Information......................................................10
2.3.1 Dynamic Management of PVC Information......................................................10
2.4 Dynamic Query of ATM Optical Port................................................................10
2.4.1 Dynamic Query of ATM Optical Port................................................................10
2.5 Dynamic Management of IMA/TC....................................................................11
2.5.1 Dynamic Management of IMA/TC....................................................................11
2.6 IP Protocol Stack Management........................................................................12
2.6.1 IP Protocol Stack Management........................................................................12
2.7 Dynamic Management of Serving Cell and Channel........................................13
2.7.1 Dynamic Management of Serving Cell and Channel........................................13
2.8 SIGTRAN Management...................................................................................14
2.8.1 SIGTRAN Management...................................................................................14
2.9 No.7 Signaling Management............................................................................15
2.9.1 No.7 Signaling Management............................................................................15
3 Software Version Management Test.............................................................16

3.1 Software Version Management Test................................................................16
3.1.1 Software Version Management Test................................................................16
4 Service Test....................................................................................................18
4.1 Basic Service Test...........................................................................................18
4.1.1 CS Service Call Test........................................................................................18
4.1.2 Videophone Service Test.................................................................................19
4.1.3 PS Service Test...............................................................................................20
4.1.4 HSPA Service Test..........................................................................................21
4.1.5 Concurrent Service Test..................................................................................24
4.2 Handover Test.................................................................................................28
4.2.1 Softer Handover...............................................................................................28
ZTE Confidential & Proprietary. © 2020 ZTE CORPORATION. All rights reserved. IV
4.2.2 Intra-RNC Inter-NodeB Soft Handover between Two Cells of the Same
Frequency.......................................................................................................32
4.2.3 Inter-RNC Soft Handover between Two Cells of the Same Frequency............37
4.2.4 Intra-NodeB Hard Handover between Two Cells of Different Frequencies.......41
4.2.5 Intra-RNC Inter-NodeB Hard Handover between Two Cells of Different
Frequencies.....................................................................................................46
4.2.6 Inter-RNC Hard Handover between Different Frequencies (Iur Interface
between two RNCs).........................................................................................50
4.2.7 Inter-RNC Hard Handover between Different Frequencies (No Iur interface
between two RNCs).........................................................................................54
4.2.8 Inter-RNC Hard Handover between Identical Frequencies (No Iur interface
between two RNCs).........................................................................................58
4.3 Interoperability Test between UMTS System and GSM/GPRS System...........62
4.3.1 Reselection in CS Domain (UMTS -> GSM)....................................................62
4.3.2 Reselection in CS Domain (GSM -> UMTS)....................................................63
4.3.3 Inter-system Handover of CS 12.2 K Voice Call (UMTS->GSM).....................64
4.3.4 Inter-system Handover of CS 12.2 K Voice Call (GSM->UMTS)......................65
4.3.5 Cell Reselection in PS Domain (UMTS -> GSM/GPRS)...................................66
4.3.6 Handover in PS Domain (UMTS-> GSM/GPRS)..............................................68
4.3.7 Handover in PS Domain (GSM/GPRS-> UMTS)..............................................69
ZTE Confidential & Proprietary. © 2020 ZTE CORPORATION. All rights reserved. V
1 RNC Hardware Test
1.1 Hardware Function Test

Test No. and Ite
m 1.1.1 Rack Fan Test
Prerequisites:
1. The main power switch of the RNC rack is ON.
2. There are no undervoltage or overvoltage alarms in the power distribution module of
the RNC rack.
Procedure:
1. Plug a fan subrack into the rack.
2. Pull out all boards in the subrack under the fan subrack.
3. Put a 20cm-long paper slip into the subrack under the fan subrack.
4. Place a paper strip of 20 cm long at the back of the wind-guiding subrack.
Acceptance Criteria:
1. 1. The fan indicator is in normal status (green indicator flashing slowly).
2. The paper slip in the service subrack should be sucked/blown upwards, which
indicates the fan is producing upward/downward wind and it is operating.
3. The paper slip at the back of the wind-guiding subrack can obviously feel the wind
force, and the surface wind-guiding subrack converts the wind direction from vertical
to horizontal.
Remarks:
None
Test No. and

Item 1.1.2 RNC Board Test
Prerequisites:
1. The power module of the RNC rack works normally.
2. Check whether the boards of the RNC rack are in position.
Procedure:
1. Turn on the power switches of power distribution subrack A and subrack B.
(Pushing the switches upwards is to turn them on; pushing the switches downwards
is to turn them off. )
2. When the power switches are turned on, the shelves of ECTA can get power input
from the power distribution subracks.
1. The indicators of the boards are in normal status.
Remarks:
1. Refer to the Hardware Description for the criteria of board indicator status. Refer to
Hardware Description for the judgment of board indicator status in the following
contents.
1.2 Reset and Switchover Test

Test No. and
Item 1.2.1 Manual Board Reset Test on the RNC
Prerequisites:
1. The indicators of all the RNC boards are in normal status.
2. Before the RNC boards are reset, at least one voice call (CS 12.2K) can be made
successfully.
Procedure:
1. Press the RST key on the board to be tested to reset it.
2. Reset the active board only, if there are both active board and standby board.
1. The RUN indicator flashes at 1 Hz after the board resets, which means that
the board runs properly.
2. The voice call (CS 12.2K) can be made successfully.
Remarks:
1. If no standby board is configured, resetting a board will release the services on it.
2. If an active board is configured with a standby board, after the active board is reset,
the standby board will serve as the active board and the original active board will be
in standby status.
Test No. and

Item 1.2.2 OMC Server Restart Test
Prerequisites:
1. The OMC server runs normally.
2. The OMC is accessed successfully.
Procedure:
1. Shut down OMM service from the Linux system of the OMM board, and then shut
down the system to pull out the OMM board.
2. Wait for 2-3 minutes and then insert the OMM board again.
3. When the Linux system is started, start the application programs of OMC server.
1. After the OMC server is shut down, the status 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 session has been
deleted.” Click OK to exit the OMC.
2. After the OMC server application program is launched, run the OMC again and it
can be accessed successfully.

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

1.2.3 Manual Master/Slave Changeover Test on
Item RNC
Prerequisites:
1. The indicators of all RNC boards are in normal status. The active/standby boards to
be tested are all in the proper slots.
2. A CS service call (CS 12.2K) can be accomplished before the active/standby
switchover.
Procedure:
1. Make calls to a pair of CS12.2K CS service users, and maintain the conversation
when the calls are established.
2. Locate the boards with active and standby configuration, and press the EXCH key
on the active board to trigger the switchover between the active and standby
boards.
1. The RUN indicators flash at 1 Hz, and both the active board and standby board run
normally after the switchover.
2. After the switchover, the ACT indicator of the original active board becomes OFF,
and that of the original standby board becomes ON.
3. During the switchover, the CS service in step one is normal, without pause or
interruption, and there is no obvious change in the call quality.

Remarks:
1. The boards that support active/standby switchover include: EAPB, EGPB, ESDTA,
ESDTI, EDTA, and EDTI.
2. When the data are being synchronized, no active/standby switchover is allowed
within 5 minutes after the first active/standby switchover. Otherwise, the second
active/standby switchover may fail.
Test No. and

Item 1.2.4 Master/Slave Changeover Test on OMC
Prerequisites:
1. The indicators of all RNC boards are in normal status. The active/standby boards to
be tested are all in the proper slots.
2. A CS service call (CS 12.2K) can be accomplished before the active/standby
switchover.
Procedure:
1. Initiate calls to a pair of CS 12.2K service users, and hold on a while (skip this step
in RCB active/standby switchover test).
2. In the left pane of Status Management interface, click UTRAN subnet > RNC
Managed Element > RNC ConfigSet > Status Management > Rack > Rack 1. The
rack diagram displays in the right pane.
3. 3. Right-click the board to be tested and select Normal Master-slave State Switch.
A dialog box will appear: “Do you want to perform master/slave switchover?” Click
OK to execute the active/standby switchover, or click Cancel to exit.

1. All RUN indicators flash at 1 Hz and both the active and standby boards run
normally after the switchover.
2. After the switchover, the ACT indicator of the original active board becomes OFF,
and that of the original standby board becomes ON. And the original active board is
reset.
3. During the switchover, the CS service in step one is normal, without pause or
interruption, and there is no obvious change in the call quality.
Remarks:
1. The boards that support master/slave board switchover include: OMM,

OMP, CMP, EAPB, EGPB, ESDTA, ESDTI, EDTA, and EDTI.
2. When the data are being synchronized, no active/standby switchover is

allowed within 5 minutes after the first active/standby switchover.
Otherwise, the second active/standby switchover may fail.
3. For the active/standby switchover of OMM board, the active/standby

configuration of OMM must be first configured and set valid.
Test No. and

1.2.5 Manual Load-Share Changeover Test on
Item RNC
Prerequisites:
1. The indicators of all RNC boards are in normal status. The load-share boards to be
tested are all in the proper slots.
2. A CS service call (CS 12.2K) can be accomplished before the load-share
switchover.
Procedure:
1. Locate the load-share boards with the planning configuration, and plug out the
board to trigger the switchover between the load-share boards.

1. For the board that is configured with load-share, the services carried on the board
power-off will suffer from call drops; the newly-started calls will all be carried on the
boards power-on, so that the newly-started services can be fulfilled successfully.
2. The board which be plugged out, the newly-started services can be fulfilled
successfully when re-plug in.
Remarks:
1. The boards that support load-share switchover include: EGBS, EGFS, EGPB, DMP,
and RUP.
2. When the data are being synchronized, no load-share switchover is allowed within 5
minutes after the first load-share switchover. Otherwise, the second load-share
switchover may fail.
2 State Management Test
2.1 Soft Reset and Block Test

Test No. and
Item 2.1.1 Soft Reset and Block Test
Prerequisites:
1. The OMC server runs normally, and the client can access the server.
2. The communications between OMC and RNC are normal.
3. All boards in the RNC rack run normally.
4. CS and PS services are normal.

Procedure:
1. Log in and open the Status Management interface.
2. Click UTRAN Sub-network > UMTS Managed Element > UMTS Radio Resource >
IuCS Link. In the window that pops up on the right, right-click an item to choose
IuCS Reset. Click UTRAN Sub-network > UMTS Managed Element > UMTS Radio
Resource > IuPS Link. In the window that pops up on the right, right-click an item to
choose IuPS Reset.
3. Click UTRAN Sub-network > UMTS Managed Element > Physical Resource >
Controller Rack, and double-click a piece of record to open the rack diagram. Click
the icon on the tool bar on the right view, and reset all network elements. In the
pop-up dialogue box for confirmation, click OK to start the all-NE reset, otherwise
click Cancel.
4. Click UTRAN Sub-network > UMTS Managed Element > Transmission Resource >
AAL2 Path. In the tab of corresponding office, choose the AAL2 path to be tested
and right-click it to execute AAL2 link block/unblock or AAL2 link reset/stop reset.
5. Click UTRAN Sub-network > UMTS Managed Element > Physical Resource > Slave
Sub-unit. In the tab of corresponding office, choose the sub-unit to be tested and
right-click it to perform manual block of sub-unit.
6. Click UTRAN Sub-network > UMTS Managed Element > UMTS Physical Resource
> Cell. Choose the cell to be tested and right-click it to choose Cell Reset.
1. RNC, Iu interface, and cell can be successfully reset. SLAVE sub-unit and the AAL2
channel can be blocked / unblocked successfully.
2. CS and PS services restore.
Remarks:
None
2.2 CPU Management

Test No. and
Item 2.2.1 CPU Management
Prerequisites:
Procedure:
2. Click UTRAN Sub-network > UMTS Managed Element > Physical Resource > Logic
CPU. Choose the CPU to be tested and right-click it to perform the test.
Module to perform Module State Query for the DMP, OMP, and CMP module. Click
UTRAN Sub-network > UMTS Managed Element > Physical Resource > Unit to
perform Unit State Query for the RUP module and DPI Card State Query of RUB.
4. For the CPU module of rear board, Unit State Query, Subunit State Query, and
Query All Block RUP Unit can be performed.
Board. In the tab, CPU Use Rate Query, Process CPU Use Rate Query, and Board
CPU Use Rate Query per Kernel can be performed.
1. The status of corresponding CPU module or unit can be obtained after being
queried.
2. CPU use rate can be obtained after being queried.
Remarks:
1. The OMM board does not support the CPU-related operations.

2.3 Dynamic Management of PVC Information

Test No. and
Item 2.3.1 Dynamic Management of PVC
Information
Prerequisites:
Procedure:
Terminal PVC Management. In this tab, choose the PCV to be queried and right-
click it to execute Query PVC State.
Exchange PVC. In this tab, choose the PCV to be queried and right-click it to
execute Query PVC State.
1. The PVC status can be displayed.
Remarks:
None
2.4 Dynamic Query of ATM Optical Port

Test No. and
Item 2.4.1 Dynamic Query of ATM Optical Port
Prerequisites:
Procedure:
Controller Rack, and double-click a piece of record to open the rack diagram. Right-
click the board to be queried on the rack diagram, and execute Optical Interface
Status Query.
1. After we query the status of ATM optical port, the residual bandwidth and bandwidth
usage rate on the ATM optical port can be displayed correctly.
Remarks:
1. The board must be the interface board of ATM optical port.
2.5 Dynamic Management of IMA/TC

Test No. and
Item 2.5.1 Dynamic Management of IMA/TC
Prerequisites:

Procedure:
2. Click UTRAN sub-network > UMTS Managed Element > Transmission Resource,
and choose IMA Group, IMA Link or TC Link in the tab. Right-click the
corresponding test object to perform the operations.
3. The following operations can be performed for IMA Group: Get Status,
Inhibit/Uninhibit, Test IMA Group/Acquire IMA Group Test Status/Cancel IMA
Group Test, Restart, etc.
4. The following operations can be performed for IMA Link: Get Status,
Inhibit/Uninhibit, etc.
5. The following operations can be performed for TC Link: Get Status,
Inhibit/Uninhibit, etc.
1. The status of corresponding test object can be displayed correctly.
2. The Inhibit and Uninhibit of test object can be completed successfully. After the
Uninhibit is operated, CS and PS services restore.
3. The IMA Group can be tested and the test results can be displayed correctly.
Remarks:
None
2.6 IP Protocol Stack Management

Test No. and
Item 2.6.1 IP Protocol Stack Management
Prerequisites:

Procedure:
RPU Board. Choose the board to be queried and right-click it to perform Interface
Inquiry in RPU, BFD Sessions Brief/Detail query in RPU, and Interface Query
Relates to 802.3ah protocol on RPU, etc.
EPU Board. Choose the board to be queried and right-click it to perform Interface
Inquiry in RPU, BFD Sessions Brief/Detail query in EPU, and Interface Query
Related to 802.3ah Protocol on EPU, etc.
Ethernet OAM. Right-click the corresponding test object to perform the tests:
Ethernet OAM, Ethernet CFM’s MD, Ethernet CFM’s MA, and Ethernet CFM’s MEP.
1. For the test object, the status of corresponding IP protocol stack configuration object
can be displayed correctly.
Remarks:
None
2.7 Dynamic Management of Serving Cell and

Channel
Test No. and
Item 2.7.1 Dynamic Management of Serving Cell
and Channel
Prerequisites:

Procedure:
Cell. Choose the corresponding cell in the tab and right-click it to perform the
operations such as Cell Status Query, Cell Status Update, Observing/Stop
Observing, and Cell Reset.
Channel. Choose the channel in the corresponding cell and right-click it to perform
the operations such as Channel Status Query, and Observe/Stop Observing.
1. After we Perform Cell Status Update, the status of the serving cell can be displayed
correctly.
2. Cell Reset can be performed for the serving cell, and the serving cell works normally
after the reset.
3. After we perform Channel Status Query, the real-time status of channel can be
displayed.
Remarks:
None
2.8 SIGTRAN Management

Test No. and
Item 2.8.1 SIGTRAN Management
Prerequisites:

Procedure:
2. Click UTRAN Sub-network > UMTS Managed Element > Transmission Resource.
Choose M3UA AS, M3UA ASP or Association in the tab, and right-click the test
object to perform the operations.
3. Right-click the corresponding AS to perform AS State Query or Batch AS State
Query.
4. The following operations can be performed by right-clicking the corresponding ASP:
ASP State Query, ASP Up, ASP Down, ASP Active, ASP Inactive, etc.
5. The following operations can be performed by right-clicking the corresponding
Association: Establish, Shutdown, Abort, Stop All Associations, Restart All
Associations, SCTP State Query, and SCTP All Static Association State Query.
1. After AS Status Query, we can view the real-time status of AS.
2. We can query ASP status and get the real-time status of ASP, and perform
operations like activating and restarting ASP.
3. We can query the status of association and get the real-time status of the
association, and perform operations like establishing and releasing association.
Remarks:
None
2.9 No.7 Signaling Management

Test No. and
Item 2.9.1 No.7 Signaling Management
Prerequisites:
Procedure:
2. Click UTRAN Sub-network > UMTS Managed Element > Transmission Resource.
Choose Adjacent No.7 Office, Signaling Link, or Signaling Linkset in the tab, and
right-click the test object to perform the operations.
3. For the adjacent office, we can right-click the corresponding office to perform the
operations such as To Query the Status of Office and To Query the Status of All
Office.
1. After querying the adjacent office status, we can view the status of the
corresponding office and the instant load of MTP3 link.
2. After querying the link group, we can view the configuration and real-time
information of the link group.
3. After querying the MTP3 link, we can view the configuration and real-time
information of the MTP3 link.
Remarks:
None
3 Software Version Management Test
3.1 Software Version Management Test

Test No. and
Item 3.1.1 Software Version Management Test
Prerequisites:
3. 3. All boards in the RNC rack run normally.
Procedure:
1. Enter the Software Version Management interface.
2. Click UTRAN Sub-network > UMTS Managed Element > Shelf-ECMM, and right-
click Shelf-ECMM to perform Version Download, Version Validate, Set Board Master
and Slave Version File Sync, and Set ECMM Initial Configuration.
3. Version upgrade: Click the button on the tool bar to perform version upgrade
management; choose the NE and version in the tab on the right window, and then
carry out version upgrade and installation.
4. Version management: Double-click UTRAN Sub-network > UMTS Managed NE >
Controller-OMP. In the tab of Default Version on the right pane, select the
corresponding version and right-click it to De-activate Version Package or Query
Detailed Information of Version Package.
5. Set OMP boot mode: Click the button on the tool bar to set the OMP boot mode.
1. The initial OMP and CMM versions can be created normally.
2. In the version upgrade, the one-step upgrade can be performed normally.
3. Activate or deactivate the RNC version, and set the OMP start mode to compare
whether the versions are consistent before and after the operation.
Remarks:
1. Deleting the version file serving as the default version is prohibited.

4 Service Test
4.1 Basic Service Test
4.1.1 CS Service Call Test

Test No. and
Item 4.1.1.1 AMR CS Service 12.2 Kbps
Prerequisites:
1. The RNC runs normally.
2. UE A and UE B finish PLMN selection, cell selection, and location update, and they
are in the idle status.
3. The static AMR rate of RNC is configured as 12.2 Kbps.
4. The Signaling Trace software is used to monitor the signaling on the Iu interface.
5. The cell supports R99, and the network runs normally.
Procedure:
1. UE A hooks off, and makes a call to UE B.
2. UE A and UE B complete RRC connection and RAB establishment respectively.
3. UE B rings and hooks off. UE A and UE B are in the conversation status. Perform
normal conversation to verify the step.
4. UE B or UE A hangs up to release the call.
1. The ring of UE B and the ring-back tone of UE A are both normal.
2. The conversation between UE A and UE B is normal. The call quality is satisfying
and there is no obvious delay.
3. When a UE hooks on, the call can be released normally.
4. The signaling of the uplink and downlink CS calls is normal.

Remarks:
None
4.1.2 Videophone Service Test

Test No. and
Item 4.1.2.1 Videophone Service Test
Prerequisites:
2. UE A and UE B finish PLMN selection, cell selection, and location update; and they
are in the idle status.
3. Both UE A and UE B support videophone service.
5. The cell supports R99, and the network runs normally.
Procedure:
1. UE A initiates a videophone call to UE B.
2. When UE B rings and hooks off, both parties are in the conversation status. Verify
whether they can perform the conversation normally, and can see the images of
each other.
3. UE B or UE A hangs up to release the call.
1. The ring of UE B and the ring-back tone of UE A are both normal.
2. The conversation between UE A and UE B is normal. The call quality is satisfying
and there is no obvious delay.
3. UE A and UE B users can see the images of each other. The images are stable (the
resolution of the images is related to the specification of the terminals), and a little
delay of the images is accepted.
Remarks:
None
4.1.3 PS Service Test

Test No. and
Item 4.1.3.1 PS Service Test
Prerequisites:
2. The USIM card of UE A is subscribed with the interactive service: UL 64 Kbps and
DL 64 Kbps.
3. The USIM card of UE B is subscribed with the interactive service: UL 64 Kbps and
DL 128 Kbps.
4. The USIM card of UE C is subscribed with the interactive service: UL 64 Kbps and
DL 384 Kbps.
5. All the radio KPIs of the cell (which supports CS and PS services) meet the
requirements.
6. UE A, UE B, and UE C already finish PLMN selection, cell selection, and location
update, and they are in the idle state.
7. UE is connected to a computer on a USB interface through a special data wire. The
computer is set with dial-up connection.
Procedure:
1. Connect the computer to the internet through the dial-up service of UE. PDP is
activated successfully.
2. Access the ftp server through the UE (log into ftp server with the ping command).
3. Upload and download the test files in the ftp server with an ftp tool in UE. The upload
and download process should last for 5 minutes. Calculate the actual traffic and rate
with Dumeter or Wireshark.
4. After uploading and downloading the files, log out of the ftp server.
5. Disconnect the dial-up connection to finish the call release process of UE.
1. The FTP server can be logged into successfully.
2. The files on the FTP site can be downloaded successfully, and remain intact.
3. The average download speed of UE A is not lower than 60 Kbps. The average
download speed of UE B is not lower than 120 Kbps. The average download speed
of UE C is not lower than 350 Kbps
4. The file is uploaded to the FTP site successfully, and remains intact. The average
upload speed is not lower than 56 Kbps.
5. PS call setup signaling is normal.
Remarks:
None
4.1.4 HSPA Service Test

Test No. and
Item 4.1.4.1 HSDPA Service Download Test
Prerequisites:
2. The HSDPA cell is established successfully.
3. UE A and UE B already finish PLMN selection, cell selection, and location update;
they are in the idle state.
4. USIM card of UE A is subscribed with the Type-I or Type-B service: UL 128Kbps; DL
4096Kbps; maximum HSDPA download rate of UE A ≥3.6Mbps.
5. USIM card of UE B is subscribed with the Type-I or Type-B service: UL 128Kbps; DL
8192Kbps; maximum HSDPA download rate of UE B ≥7.2Mbps.
6. All the radio KPIs of the cell meet the requirements.

Procedure:
1. The PC dials through UE, and starts PS service in the HSDPA cell. PDP activation is
successful.
3. Download the test files from the FTP server with an FTP tool in UE. The download
process should last for 5 minutes. Calculate the actual traffic and rate with Dumeter
or Wireshark.
4. After the download of files is completed, log out of the ftp server.
5. Disconnect the dial-up connection to finish the call release process of UE.
1. Average download rate of UE A is not lower than 3Mbps.
2. Average download rate of UE B is not lower than 5Mbps.
3. HSDPA call setup signaling is normal.
Remarks:
1. If the transmission bandwidth of the site and the cell throughput are limited, the tests
on UE A and UE B should not be conducted simultaneously.
2. HSPA service has a higher requirement for network quality. CQI at UE A test spot
should be higher than 20, and CQI at UE B test spot should be higher than 20.
3. The HSDPA cell where UE A resides should be configured with at least 5 HS-
PDSCH code channels.
4. The HSDPA cell where UE B resides is configured with at least 10 HS-PDSCH code
channels.
5. There are no other HSDPA users in the cell during the tests.
Test No. and

Item 4.1.4.2 HSUPA Service Upload Test
Prerequisites:
2. The HSUPA cell is established successfully.
3. UE already finishes PLMN selection, cell selection, and location update; and it is in
the idle state.
4. USIM card of UE is subscribed with the Type-I or Type-B service: UL 2048Kbps; DL
384Kbps; the maximum HSUPA upload rate of the UE should be not lower than
1.8Mbps.
5. All the radio KPIs of the cell meet the requirements.
Procedure:
1. The computer is connected to the internet with dial-up service via UE. PS service is
initiated in the HSDPA cell. PDP is activated successfully.
3. Upload the test files in the ftp server with an ftp tool in UE. The upload process
should last for 5 minutes. Calculate the actual traffic and rate with Dumeter or
Wireshark.
4. After the upload of files is completed, log out of the ftp server.
5. 5. Disconnect the dial-up connection to finish the call release process of UE.
1. Average UE upload rate should not be lower than 1.5Mbps.
2. HSUPA call setup signaling is normal.
Remarks:
1. The transmission bandwidth of the site and the cell throughput should not be limited.
2. There are no other HSUPA users in the cell during the tests.
4.1.5 Concurrent Service Test
Test No. and

Item
4.1.5.1 AMR 12.2 Kbps, PS UL 64 Kbps DL 64
Kbps
Prerequisites:
1. 1. The RNC runs normally.
2. USIM card of UE is subscribed with the interactive service: UL 64 Kbps and DL 64
Kbps.
4. The cell should support R99 protocol, and all the radio KPIs of the cell meet the
requirement.
the idle state.
Procedure:
1. UE initiates a CS 12.2K call, which is normal and can sustain.
or Wireshark.
6. Disconnect the dial-up service, and PDP is de-activated successfully.
7. End the call from UE, and the call is released.

1. Calls can be initiated with the UE. The audio quality is satisfying and there is no
obvious delay.
2. When UE initiates the PS service, the CS service is not affected.
3. After the PS service is finished, the CS service is still not affected.
Remarks:
None
Test No. and

Item
4.1.5.2 AMR 12.2 Kbps, PS UL 64 Kbps DL 128
Kbps
Prerequisites:
Kbps.
requirement.
the idle state.

Procedure:
or Wireshark.
obvious delay.
Remarks:
None
Test No. and

4.1.5.3 AMR 12.2Kbps, PS UL64Kbps DL384Kbps
Item
Prerequisites:
Kbps.
requirement.
the idle state.
Procedure:
or Wireshark.
obvious delay.

Remarks:
None
UE should support the concurrent service of AMR 12.2Kbps, PS UL64Kbps DL384Kbps.
4.2 Handover Test
4.2.1 Softer Handover

Test No. and
Item 4.2.1.1 Softer Handover of CS 12.2 K Voice Call
Prerequisites:
1. Cell A and Cell B with the same frequency are set up under the same Node B. They
are neighbor cells and some of their coverage areas overlap.
2. UE A and UE B already finish PLMN selection, cell selection, and location update,
and they are in the idle state.
3. The Signaling Trace software is used to monitor the signaling on the Uu interface.
Procedure:
1. UE A and UE B are both in the area only covered by Cell A. UE A initiates a CS
12.2K call to UE B. The call is sustained after it is established.
2. UE A moves from the area only covered by Cell A into the area covered by both Cell
A and Cell B, then moves into the area only covered by Cell B. UE B stays at the
original place.
3. Observe the signaling statistics of “Active Set Update” and “Active Set Update
Complete” on the Uu interface.

1. When UE A is moving, the call remains normal and the voice is clear without
interruption or delay.
2. In the signaling statistics of UE A, there are at least one signaling flow for the
addition of radio link, one for the deletion of radio link, and two for the update of
active set.
3. In one active set update, the primary scrambling code of Cell B is added. In another
active set update, the primary scrambling code of Cell A is deleted.
Remarks:
1. In Procedure Step 2 “UE A moves from the area only covered by Cell A into the area
covered by both Cell A and Cell B, then moves into the area only covered by Cell B.”
is equivalent to “UE A is located in the overlapped coverage area of Cell A and Cell
B. The TX power of Cell A is decreased gradually when that of Cell B is increased
gradually.” Either of the above test methods can be used according to the specific
test environment.
2. The test remarks of the following handover test items are the same as this one. In
addition, refer to Appendix B for the signaling flow of handover, which is not detailed
here.
Test No. and

Item 4.2.1.2 Softer Handover of Videophone Service
Prerequisites:
1. Cell A and Cell B with the same frequency are set up under the same Node B. They
are neighbor cells and some of their coverage areas overlap.
3. Both UE A and UE B support the video phone service.
Procedure:
1. UE A and UE B are both in the area only covered by Cell A. UE A initiates a
videophone call to UE B. The call is sustained after it is established.
original place.
1. When 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.
active set.
Remarks:
None
Test No. and

Item 4.2.1.3 Softer Handover of PS 384Kbps Service
Prerequisites:
1. Cell A and Cell B with the same frequency are set up under the same NodeB, and
some of their coverage areas overlap.
2. UE A already finishes PLMN selection, cell selection, and location update; it is in the
idle state.
3. The USIM card of UE A is subscribed with the PS service UL 64 Kbps/DL 384 Kbps.
Procedure:
1. UE A is in the area only covered by Cell A. It initiates PS service.
A and Cell B, then moves into the area only covered by Cell B.
1. When UE A is moving, the PS service remains normal, and there is no obvious
active set.
Remarks:
None
Test No. and

Item
4.2.1.4 Softer handover of CS 12.2K + PS
128Kbps concurrent service
Prerequisites:
1. Cell A and Cell B with the same frequency are set up under the same NodeB, and
Procedure:
2. UE A initiates PS service.
original place.
Complete” with the signaling trace software on the Uu interface.
1. When UE A is moving, the call remains normal and the voice is clear, without
obvious interruption or delay. And the PS service of UE A also remains normal and
has no obvious interruption or delay.
2. In the signaling statistics of UE A, the signaling flows for radio link addition and radio
link deletion appear at least once respectively, and the flow for active set update
appears at least twice.
Remarks:
None
4.2.2 Intra-RNC Inter-NodeB Soft Handover between Two Cells of the

Same Frequency
Test No. and

Item
4.2.2.1 Soft Handover of CS 12.2 K Voice Call
Service
Prerequisites:
1. In the same RNC, Cell A is set up under NodeB A, and Cell B is set up under NodeB
B. They are configured as the neighbor cells with the same frequency. Besides,
Procedure:
original place.
active set.
Remarks:
None
Test No. and

Item 4.2.2.2 Soft Handover of Videophone Service
Prerequisites:
Procedure:
original place.
active set.
Remarks:
None
Test No. and

Item 4.2.2.3 Soft Handover of PS 384 K Service
Prerequisites:
idle state.
Procedure:
active set.
Remarks:
None
Test No. and

Item
4.2.2.4 Soft Handover of CS 12.2K + PS 128K
Concurrent Service
Prerequisites:
Procedure:
original place.
1. When UE A is moving, the call remains normal and the voice is clear, without obvious
interruption or delay. And the PS service of UE A also remains normal and has no
obvious interruption or delay.
Remarks:
None
4.2.3 Inter-RNC Soft Handover between Two Cells of the Same Frequency
Test No. and

Item
4.2.3.1 Soft Handover of CS 12.2 K Voice Call
Service
Prerequisites:
1. RNC A and RNC B belong to the same CN. Cell A is set up under RNC A, and Cell B
is set up under RNC B. They are configured as the neighbor cells with the same
frequency. Besides, some of their coverage areas overlap.
3. The Iur interface connection exists between RNC A and RNC B.
4. The Signaling Trace software is used to monitor the signaling on the Uu interface of
RNC A.
Procedure:
2. UE A moves from the area only covered by Cell A towards the area covered by both
Cell A and Cell B until soft handover is triggered, as the signaling shows; then it
returns to the area only covered by Cell A. UE B stays at the original place.
Complete” on the Uu interface of RNC A.
2. In the signaling statistics of UE A, there are at least one signaling flow for the addition
of radio link, one for the deletion of radio link, and two for the update of active set.
3. In an active set update, the primary scrambling code of Cell B is added. In another
active set update, the primary scrambling code of Cell B is deleted.

Remarks:
None
Test No. and

Item 4.2.3.2 Soft Handover of Videophone Service
Prerequisites:
RNC A.
Procedure:

Remarks:
None
Test No. and

Item 4.2.3.3 Soft Handover of PS 384 K Service
Prerequisites:
idle state.
5. The Signaling Trace software is used to monitor the signaling on the Uu

interface of RNC A.
Procedure:

Remarks:
None
Test No. and

Item
4.2.3.4 Soft Handover of CS 12.2K + PS 128K
Concurrent Service
Prerequisites:
3. The USIM card in UE A is subscribed with the PS service UL64Kbps/DL 128Kbps.
RNC A.
Procedure:

Remarks:
None
4.2.4 Intra-NodeB Hard Handover between Two Cells of Different

Frequencies
Test No. and

Item
4.2.4.1 Hard Handover of CS 12.2 K Voice Call
Service
Prerequisites:
1. Cell A and Cell B, two cells of different frequencies, are set up under the same
NodeB. Besides, the two cells have an overlapped coverage area.
2. UE A completes its location update in Cell A, and UE B completes its location update
in Cell B.
Procedure:
1. UE A originates the CS 12.2 K voice call to UE B, and the call is sustained.
original place.
3. Observe the signaling of UE A on the Uu interface and collect the statistics of
Physical Channel Reconfiguration and Physical Channel Reconfiguration Complete.
2. The statistics of the signaling of UE A shows that the signaling flow of radio link
reconfiguration appears once at least.
Remarks:
None
Test No. and

Item 4.2.4.2 Hard Handover of Videophone Service
Prerequisites:
in Cell B.
Procedure:
1. UE A originates the videophone call to UE B, and the call is sustained.
original place.
3. Observe the signaling of UE A on the Uu interface and collect the statistics of
Physical Channel Reconfiguration and Physical Channel Reconfiguration Complete.
Remarks:
None
Test No. and

Item 4.2.4.3 Hard Handover of PS 384 K Service
Prerequisites:
2. UE A completes the location update in Cell A.
Procedure:
3. Observe the signaling on the Uu interface and the statistics of Physical Channel
Reconfiguration and Physical Channel Reconfiguration Complete.
Remarks:
None
Test No. and

Item
4.2.4.4 Hard Handover of CS 12.2K + PS 128K
Concurrent Service
Prerequisites:
3. 3. The static AMR rate of RNC is configured as 12.2 Kbps.
Procedure:
original place.
4. Observe the signaling of UE A on the Uu interface and the statistics of Physical
Channel Reconfiguration and Physical Channel Reconfiguration Complete.
Remarks:
None
4.2.5 Intra-RNC Inter-NodeB Hard Handover between Two Cells of

Different Frequencies
Test No. and

Item
Service
Prerequisites:
1. Under the same RNC, Cell A is set up in NodeB A, and Cell B is set up in NodeB B.
Cell A and Cell B use different frequencies, and they have an overlapped coverage
area.
in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item 4.2.5.2 Hard Handover of Videophone Service
Prerequisites:
area.
in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item 4.2.5.3 Hard Handover of PS 384 K Service
Prerequisites:
area.
Procedure:
Remarks:
None
Test No. and

Item
4.2.5.4 Hard Handover of the CS 12.2 K + PS 128
K Concurrent Service
Prerequisites:
area.
Procedure:
original place.
Remarks:
None
4.2.6 Inter-RNC Hard Handover between Different Frequencies (Iur

Interface between two RNCs)
Test No. and

Item
Service (Different Frequencies)
Prerequisites:
1. RNC A and RNC B belong to the same CN. Cell A is created under RNC A, and Cell
B is created under RNC B. Cell A and Cell B use different frequencies, and they have
an overlapped coverage area.
in Cell B.
3. There is an Iur interface between RNC A and RNC B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
4.2.6.2 Hard Handover of Videophone Service
(Different Frequencies)
Prerequisites:
in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
4.2.6.3 Hard Handover of PS 384 K Service
Prerequisites:
Procedure:
Remarks:
None
Test No. and 4.2.6.4 Hard Handover of the CS 12.2 K + PS 128

Item K Concurrent Service (Different
Frequencies)
Prerequisites:
4. The static AMR rate of RNC is configured as 12.2 Kbps.
Procedure:
original place.
Remarks:
None
4.2.7 Inter-RNC Hard Handover between Different Frequencies (No Iur

interface between two RNCs)
Test No. and

Item
Service (Different Frequencies)
Prerequisites:
B is created under RNC B. Cell A and Cell B use different frequencies, and they
have an overlapped coverage area.
2. UE A completes its location update in Cell A, and UE B completes its location
update in Cell B.
3. There is no Iur interface between RNC A and RNC B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
Prerequisites:
update in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
Prerequisites:
3. USIM card in UE A is subscribed with the PS service UL64Kbps/DL 384Kbps.
Procedure:
Remarks:
None

Item K Concurrent Service (Different
Frequencies)
Prerequisites:
Procedure:
original place.
4. Observe the signaling of UE A on the Uu interface and the statistics of

Physical Channel Reconfiguration and Physical Channel Reconfiguration
Complete.
Remarks:
None
4.2.8 Inter-RNC Hard Handover between Identical Frequencies (No Iur

interface between two RNCs)
Test No. and

Item
4.2.8.1 Hard Handover of CS 12.2 K Service
(Identical Frequencies)
Prerequisites:
B is created under RNC B. Cell A and Cell B use the same frequency, and they have
update in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
Prerequisites:
update in Cell B.
Procedure:
original place.
Remarks:
None
Test No. and

Item
Prerequisites:
3. USIM card in UE A is subscribed with the PS service UL64Kbps/DL 384Kbps.
Procedure:
Remarks:
None

Item K Concurrent Service (Identical
Frequencies)
Prerequisites:
Procedure:
original place.
4. Observe the signaling of UE A on the Uu interface and the statistics of

Physical Channel Reconfiguration and Physical Channel Reconfiguration
Complete.
Remarks:
None
4.3 Interoperability Test between UMTS System and

GSM/GPRS System
Test No. and
Item 4.3.1 Reselection in CS Domain (UMTS ->
GSM)
Prerequisites:
1. Both the UMTS system and GSM system work properly, and the link between them
is also in good condition.
2. Corresponding parameters of the UMTS system and GSM system are configured.
3. Create Cell A under the UMTS system and create Cell B under the GSM system.
The two cells have an overlapped coverage area.
4. UE A and UE B complete the location update in Cell A.
5. UE A supports both the UMTS mode and the GSM mode.
6. Use the signaling tracing software to observe the signaling of UE A on the Uu
interface, lu interface, and A interface.
Procedure:
1. UE A and UE B stay in the idle state.
Cell A and Cell B, and then enters the area only covered by Cell B. UE B stays at
the original place.
3. Observe the signaling on the Uu interface, lu interface, and A interface, which shows
that UE A makes a reselection and accesses Cell B of the GSM system, and
completes the location update in Cell B.
4. UE A originates a voice call towards UE B in Cell B.
1. UE A can successfully complete a call with UE B, and the voice quality feels good.
2. The signaling statistics on the lu interface of UE A show that the signaling flow of
Relocation Required appears once at least. The signaling statistics on the A
interface of UE A show that the location update flow appears once at least.
Remarks:
None
Test No. and

Item 4.3.2 Reselection in CS Domain (GSM ->
UMTS)
Prerequisites:
4. UE A and UE B complete the location update in Cell B.
interface and lu interface.
Procedure:
1. UE A and UE B stay in the idle state.
2. UE A moves from the area only covered by Cell B towards the area covered by both
Cell A and Cell B, and then enters the area which is only covered by Cell A. UE B
stays at the original place.
3. Observe the signaling on the Uu interface and lu interface, which shows that UE A
makes a reselection and accesses Cell A of the WCDMA system, and completes the
location update in Cell A.
4. UE A originates a CS 12.2K voice call towards UE B in Cell A.

1. The signaling statistics of UE A on the Uu interface and Iu interface show that the
signaling flow of location update appears once at least.
2. After UE A completes the location update successfully, it can successfully complete
a call with UE B with good voice quality.
Remarks:
None
Test No. and

Item 4.3.3 Inter-system Handover of CS 12.2 K
Voice Call (UMTS->GSM)
Prerequisites:
4. UE A and UE B complete the location update in Cell A.
5. UE A and UE B support both the UMTS mode and the GSM mode.

Procedure:
1. UE A originates a CS 12.2K voice call towards UE B in the area only covered by Cell
A. The call is sustained after it is established.
Cell A and Cell B, and then enters the area only covered by Cell B. UE B stays at
the original place.
3. Observe the signaling on the Uu interface and Iu interface, which shows that
handover between systems is triggered and the lu interface has the Relocation
Required message.
2. The signaling statistics of UE A on the lu interface show that the Relocation
Required signaling flow appears once at least. The signaling statistics on the Uu
interface show that the Handover from UTRAN signaling flow appears once at least.
Remarks:
None
Test No. and

Item 4.3.4 Inter-system Handover of CS 12.2 K
Voice Call (GSM->UMTS)
Prerequisites:
4. UE A and UE B complete the location update in Cell B.

Procedure:
1. UE A originates a voice call towards UE B in the area only covered by Cell B. The
call is sustained after it is established.
Cell A and Cell B, and then enters the area which is only covered by Cell A. UE B
stays at the original place.
3. Observe the signaling on the Uu interface and Iu interface, which shows that the
handover between systems is triggered. Besides, the lu interface has the Relocation
Request message.
2. The signaling statistics on the lu interface of UE A show that the Relocation Request
signaling flow appears once at least. The signaling statistics on Uu interface show
that the Handover To UTRAN Complete signaling flow appears once at least.
Remarks:
None
Test No. and

Item 4.3.5 Cell Reselection in PS Domain (UMTS
-> GSM/GPRS)
Prerequisites:
5. UE A supports both the UMTS mode and the GSM/GPRS mode.
interface, lu interface, and Gb interface.
Procedure:
1. UE A originates the PS service in Cell A. It can ping through to the FTP server and
download the file, and then stop all operations.
2. During a certain period (for example, 20 minutes, or the value set based on the
network parameters), the UE does not transmit data. The network direct the UE to
change to the CELL_PCH state.
4. Observe the signaling on the Uu interface, lu interface, and Gb interface, which
shows that UE A makes a reselection and accesses Cell B of the GPRS system, and
completes the routing area update in Cell B.
5. UE B initiates the GPRS service in Cell B and can connect to the server with the
ping command.
1. UE A downloads the file in Cell B from the FTP site successfully, and the file is
complete.
SRNS Context Request/Response appears once at least. The signaling statistics on
the Gb interface of UE A show that the routing area update flow appears once at
least.
Remarks:
None
Test No. and

Item 4.3.6 Handover in PS Domain (UMTS->
GSM/GPRS)
Prerequisites:
interface, Iu interface, and Gb interface.
7. The subscribed service type should be the background service.

Procedure:
1. UE A originates the service in the PS domain in Cell A, and can ping through to the
FTP server.
Cell A and Cell B, and then enters the area only covered by Cell B. The current cell
has an instantaneous attenuation and no handover is performed.
3. Observe the signaling on the Uu interface and Iu interface, which shows that UE A
makes a reselection and accesses Cell B of the GPRS system, and then completes
the routing area update in Cell B.
4. UE A starts to use the GPRS service, and can ping through to the FTP server.
5. Use the software Wireshark or Dumeter to measure the PS rate.
1. During the whole test procedure, UE A can always ping through to the FTP server,
and can download the file successfully.
SRNS Context Request/Response appears once at least. The signaling statistics on
interface Gb of UE A show that the routing area update flow appears once at least.
3. The handover signaling is normal.
Remarks:
None
Test No. and

Item 4.3.7 Handover in PS Domain (GSM/GPRS->
UMTS)
Prerequisites:
4. UE A completes the location update in Cell B.
interface, Iu interface, and Gb interface.
7. The subscribed service type should be the background service.
Procedure:
1. UE A originates the GPRS service in Cell B. It can ping through to the FTP server
and download the file.
Cell A and Cell B, and then enters the area only covered by Cell A. Cell B has an
instantaneous attenuation and no handover is performed.
3. Observe the signaling on the Uu interface and Iu interface, which shows that UE A
makes a reselection and accesses Cell A of the UMTS system, and then completes
the routing area update in Cell A.
4. UE A starts to use the PS service and makes a connection to the FTP server.
1. UE A downloads the file in Cell A from the FTP site successfully, and the
file is complete.
2. The signaling statistics on the lu interface of UE A show that the signaling

flow of SRNS Context Request/Response appears once at least. The
routing update flow appears once on the Uu interface at least.
3. The handover signaling is normal.
4. The data transmission interval in the PS domain is shorter than five

seconds.
Remarks:
None

ZXUR 9000 UMTS (V4.18.10) Test Guide - R1.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZXUR 9000 UMTS (V4.18.10) Test Guide - R1.0

Încărcat de

Drepturi de autor:

Formate disponibile

ZXUR 9000 UMTS(V4.18.

Copyright © 2020 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Product Version Document Version Serial Number Reason for Revision

Date Document Version Prepared by Reviewed by Approved by

Intended audience: RNC commissioning engineers (Internal & outsourced)

About This Document

1 RNC Hardware Test.........................................................................................1

2 State Management Test...................................................................................7

3 Software Version Management Test.............................................................16

1 RNC Hardware Test

1.1 Hardware Function Test

1. The main power switch of the RNC rack is ON.

2. There are no undervoltage or overvoltage alarms in the power distribution module of

the RNC rack.

1. Plug a fan subrack into the rack.

4. Place a paper strip of 20 cm long at the back of the wind-guiding subrack.

1. 1. The fan indicator is in normal status (green indicator flashing slowly).

indicates the fan is producing upward/downward wind and it is operating.

Test No. and

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

2. Check whether the boards of the RNC rack are in position.

1. Turn on the power switches of power distribution subrack A and subrack B.

is to turn them off. )

from the power distribution subracks.

1. The indicators of the boards are in normal status.

1.2 Reset and Switchover Test

1. The indicators of all the RNC boards are in normal status.

1. Press the RST key on the board to be tested to reset it.

2. The voice call (CS 12.2K) can be made successfully.

Test No. and

1. The OMC server runs normally.

2. The OMC is accessed successfully.

down the system to pull out the OMM board.

deleted.” Click OK to exit the OMC.

can be accessed successfully.

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

Test No. and

be tested are all in the proper slots.

2. A CS service call (CS 12.2K) can be accomplished before the active/standby

when the calls are established.

and that of the original standby board becomes ON.

interruption, and there is no obvious change in the call quality.

ESDTI, EDTA, and EDTI.

2. When the data are being synchronized, no active/standby switchover is allowed

active/standby switchover may fail.

Test No. and

be tested are all in the proper slots.

2. A CS service call (CS 12.2K) can be accomplished before the active/standby

in RCB active/standby switchover test).

rack diagram displays in the right pane.

OK to execute the active/standby switchover, or click Cancel to exit.

normally after the switchover.

interruption, and there is no obvious change in the call quality.

1. The boards that support master/slave board switchover include: OMM,

2. When the data are being synchronized, no active/standby switchover is

3. For the active/standby switchover of OMM board, the active/standby

Test No. and

tested are all in the proper slots.

2. A CS service call (CS 12.2K) can be accomplished before the load-share

board to trigger the switchover between the load-share boards.

boards power-on, so that the newly-started services can be fulfilled successfully.

successfully when re-plug in.