ZXUR 9000 GSM (V6.50.20) BSC Commissioning Guide - R1.1

ZXUR 9000 GSM (V6.50.
20) BSC
Commissioning Guide
ZXUR 9000 GSM (V6.50.20) BSC Commissioning Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2018 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure 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.
and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone’s access to this document should not be construed as granting,
by implication, estopped or otherwise, any license or right to use any marks appearing in the
document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual,
relevant contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is
subject to continuous update without further notice due to improvement and update of ZTE
CORPORATION’s products and technologies.
ZTE CORPORATION
Address: Address: NO. 55

Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://dms.zte.com.cn
TSM.Aftersales@zte.com.cn
Email:
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. I

Revision History
Product Version Document Version Serial Number Reason for Revision

V6.50.20 R1.0 First published
V6.50.20 R1.1 Revised
Author
Date Document Version Prepared by Reviewed by Approved by

2014-4-22 R1.0 Wang Long Ma Yun Chen Qi
2014-12-15 R1.1 Wang Long Ma Yun Chen Qi
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. II

Intended audience: GSM after-sales engineers
Proposal: Before reading this document, you had better have the following
knowledge and skills.
SEQ Knowledge and skills Reference material
ZXUR 9000 GSM (V6.50.20) Base Station
1 V6.50.20 ZXUR 9000 hardware knowledge
Controller Hardware Description
V6.50.20 ZXUR 9000 software installation ZXUR 9000 GSM (V6.50.20) BSC Software
2
knowledge Installation Guide
ZXUR 9000 GSM (V6.50.20) BSC Initial
3 V6.50.20 ZXUR 9000 configuration
Configuration Guide
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. III
About This Document
Summary
Chapter Description
1 General Introduction It gives a general introduction of the document.
2 Commissioning Flow It describes the general commissioning flow.
3 Preparations It describes the preparations for the commissioning.
4 Equipment Check before Power- It describes the equipment checks before power-on.
on
5 Equipment Power-Up It describes the operation of equipment power-up.
6 Equipment Check with Power-on It describes the equipment checks with power-on.
7 OMM Installation & It describes the OMM installation and commissioning.
Commissioning
8 Data Configuration It describes the data configuration for the commissioning.
9 Version Loading & State Check It describes the version loading and state check.
10 SDR – Abis Interface Integration It describes the SDR-A interface integration.
11 A Interface Integration It describes the A interface integration.
12 GB Interface Integration It describes the GB interface integration.
13 Commissioning test It describes the commissioning tests.
AppA TDMA Integration It describes the TDMA integration parameters.
Parameters
AppB IP-A Integration Parameters It describes the IP-A integration parameters.
AppC E1-Gb Integration It describes the E1-Gb integration parameters.
Parameters
AppD IP-Gb Integration Parameters It describes the IP-Gb integration parameters.
AppE Checking the Factory Version It describes how to check the factory version of equipment.
of Equipment
AppF Hardware Version Check It describes how to check hardware version.
AppG Common Abbreviations It describes the common abbreviations.
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. IV

TABLE OF CONTENTS
1 General Introduction........................................................................................1
1.1 Overview............................................................................................................1
1.2 Conventions.......................................................................................................1
1.3 Application Scope..............................................................................................1
1.4 Conditions/Prerequisites....................................................................................2
2 Commissioning Flow.......................................................................................3
3 Preparations.....................................................................................................4
3.1 Project Information.............................................................................................5
3.2 Preparation of Tools & Meters............................................................................5
3.3 Preparation of Software.....................................................................................5
3.4 Preparation of Documents.................................................................................5
3.5 Confirmation of System Networking Plan...........................................................6
4 Equipment Check before Power-on................................................................6

4.1 Power Supply Voltage Check.............................................................................6
4.2 Hardware Check................................................................................................7
4.2.1 Cabinet Check...................................................................................................7
4.2.2 ZXUR 9000 GSM Hardware Installation & Cable Connection............................8
4.2.3 Auxiliary Equipment Check..............................................................................18
4.2.4 Other Checks...................................................................................................19
4.3 Check Record before Power-on.......................................................................19
5 Equipment Power-Up.....................................................................................20
6 Equipment Check with Power-on.................................................................21

6.1 Board Check....................................................................................................21
6.2 Fan Rotation Direction Check..........................................................................22
6.3 Check Record with Power-on...........................................................................22
6.4 Power-down Procedure....................................................................................23
7 OMM Installation & Commissioning.............................................................23
8 Data Configuration.........................................................................................23
8.1 Creating SubNetwork.......................................................................................23
8.1.1 Creating SubNetwork.......................................................................................23
8.1.2 Subnetwork Query/Modification.......................................................................24
8.2 Configuring Managed Element.........................................................................25
8.2.1 Adding the Configuration..................................................................................25
8.2.2 Configuration Query/Modification/Deletion.......................................................26
8.3 BSC-OMCR Link Establishment.......................................................................26
8.4 Import of Quick Data Configuration Template...................................................27
9 Version Loading & State Check....................................................................28

9.1 Version Package & Loading Flow.....................................................................28
9.1.1 Version Package..............................................................................................28
9.1.2 Version Loading Flow.......................................................................................29
9.1.3 Generating ZDB Data and Snapshot Area on OMMR......................................29
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. V

9.2 Checking the Factory Version..........................................................................31

9.3 Checking the Firmware of Independent Boards Before Upgrade.....................32
9.4 Loading Software Version................................................................................32
9.4.1 Creating the Initial OMP Package....................................................................32
9.4.2 Setting the Version of Independent Boards......................................................33
9.4.3 One-click Version Upgrade..............................................................................34
9.4.4 OMP Running Version Query...........................................................................37
9.5 Data Synchronization.......................................................................................38
9.5.1 All-data Synchronization..................................................................................38
9.5.2 Modified-data Synchronization.........................................................................40
9.6 Loading ECMM Software Version....................................................................41
9.7 Loading Firmware Version...............................................................................43
9.7.1 ECMM Boot Loading........................................................................................43
9.7.2 Loading PDUMBOOT Version..........................................................................45
9.7.3 Loading Rear Card Boot Version......................................................................46
9.7.4 Loading EPLD..................................................................................................47
9.7.5 Version Consistency Check.............................................................................48
9.8 ZXUR 9000 Running Version Query................................................................49
9.8.1 Software Version Query...................................................................................49
9.8.2 ZXUR 9000 Board Alarm Query.......................................................................50
9.9 Online Configuration of Independent Board.....................................................51
9.9.1 Configuration of Independent Board................................................................51
9.9.2 ECMM Configuration........................................................................................51
9.9.3 Configuration of System Clock.........................................................................52
9.9.4 Configuration of System Environment..............................................................53
9.9.5 Activation......................................................................................................... 53
10 SDR – Abis Interface Integration..................................................................54

10.1 Preparation......................................................................................................54
10.2 Checking SDR Base Station Status.................................................................54
10.3 BTS Alarm Query.............................................................................................56
11 A Interface Integration...................................................................................56
11.1 Preparation......................................................................................................57
11.2 Data for Integration (Narrowband Signaling No.7/3GPP IPA)...........................57
11.3 Integration Data Validity Check........................................................................57
11.4 TDMA Integration State Check.........................................................................59
11.4.1 Checking the Integration Parameters...............................................................59
11.4.2 Observing BSC Board Status...........................................................................60
11.4.3 Observing Alarms in OMCR.............................................................................60
11.4.4 Observing Dynamic Data.................................................................................60
11.5 IPA Integration State Check.............................................................................63
11.6 Integration of TDM-IP Hybrid Scenario.............................................................65
11.6.2 BSC Board Status & Alarm Observation in OMCR...........................................66
11.6.4 Checking Signaling Trace................................................................................67
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. VI

11.7 Test on A Interface...........................................................................................67

11.8 Check Records of A Interface Integration.........................................................67
12 GB Interface Integration................................................................................68
12.1 Preparation......................................................................................................68
12.2 Data for Integration..........................................................................................68
12.3 Explanation of IP Gb........................................................................................68
12.4 Checking E1 Gb Integration.............................................................................70
12.5 Checking IP Gb Integration..............................................................................70
12.5.3 Use of Signaling Trace.....................................................................................70
12.5.4 Observing in Dynamic Data Management........................................................71
12.6 Test on Gb Interface.........................................................................................71
12.7 Check Records of Gb Interface Integration......................................................71
13 Commissioning test.......................................................................................72
AppA TDMA Integration Parameters.......................................................................73
AppB IP-A Integration Parameters..........................................................................74
AppC E1-Gb Integration Parameters......................................................................75
AppD IP-Gb Integration Parameters.......................................................................76
AppE Checking the Factory Version of Equipment...............................................77
AppF Hardware Version Check...............................................................................78
AppG Common Abbreviations....................................................................................89
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. VII
FIGURES
Figure 2-1 Commissioning Flow.............................................................................................3

Figure 4-1 Shelf Data Module CDM......................................................................................10
Figure 4-2 DIP of CDM in Shelf3...........................................................................................11
Figure 4-3 Cabling of Control Plane Inter-Connection Ethernet Cable..................................12
Figure 4-4 Cabling of Media Plane Inter-Connection Fiber...................................................13
Figure 4-5 Cabling of Line Reference Clock Cables.............................................................14
Figure 4-6 Cabling of BITS Reference Clock Cables............................................................15
Figure 4-7 Cabling of Inter-Shelf Clock Cables.....................................................................16
Figure 4-8 Cabling of PD485 Monitoring Cables...................................................................17
Figure 8-1 Create Subnetwork 1...........................................................................................24
Figure 8-2 Create Subnetwork 2...........................................................................................24
Figure 8-3 Querying Subnetwork..........................................................................................25
Figure 8-4 Create Managed Element 1.................................................................................25
Figure 8-5 Create Managed Element 2.................................................................................26
Figure 9-1 Version Loading Flow..........................................................................................29
Figure 9-2 Open MML Terminal............................................................................................30
Figure 9-3 Create Initial Version Package.............................................................................32
Figure 9-4 Upgrade Management Interface..........................................................................35
Figure 9-5 Set OMP Boot Mode............................................................................................37
Figure 9-6 OMP Running Version Query..............................................................................38
Figure 9-7 Synchronize All Data...........................................................................................39
Figure 9-8 Load ECMM Software Version.............................................................................42
Figure 9-9 Load ECMM Boot Firmware Version....................................................................45
Figure 9-10 Load PDUMBOOT Version................................................................................46
Figure 9-11 Load Rear Card Boot Version............................................................................47
Figure 9-12 Load EPLD Version...........................................................................................48
Figure 9-13 Version Consistency Check...............................................................................49
Figure 9-14 Software Version Query.....................................................................................50
Figure 9-15 Online Configuration of Independent Board.......................................................53
Figure 10-1 Check SDR Base Station Status.......................................................................55
Figure 11-1 Check TDMA Integration State...........................................................................62
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. VIII
Figure 11-2 Check IPA Integration State...............................................................................65

Figure 11-3 Check TDM - IP Hybrid Integration State...........................................................67
Figure 12-1 Structure of IPGb Networking............................................................................70
Figure 12-2 Check the IPGB Integration State......................................................................72
TABLES
Table 2-1 Explanation of the Flow Chart.................................................................................3

Table 4-1 Definitions of Jumpers on CDM Module................................................................10
Table 4-2 Check Record Before Power-on............................................................................19
Table 6-1 Check Record after Power-on...............................................................................22
Table 11-1 TDMA Integration Parameters.............................................................................60
Table 11-2 IPA Integration Parameters..................................................................................64
Table 11-3 Integration Parameters for TDM - IP Hybrid Scenario.........................................66
Table 11-4 A Interface Integration Check Record..................................................................68
Table 12-1 Check Records of Gb Interface Integration.........................................................72
ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. IX

1 General Introduction
1.1 Overview
This guide specifies the commissioning criteria of the ZXUR 9000 GSM (V6.50.20), in
order to provide universal and detailed engineering commissioning procedure, regulate
and guide the on-site commissioning work of the commissioning engineers. Readers of
this guide should have mastered the basic hardware knowledge and software installation
knowledge of ZXUR 9000 as well as the knowledge of Linux system commands and
Oracle database commands. Due to the lack of space and the focus of this guide,
theoretical description of the above system commands will not be detailed here.
1.2 Conventions
The commands starting with “#” should be executed under user root.
The commands starting with “$”should be executed under user oracle.
The screenshots used in this guidebook are from the following versions, which may vary
from those sourced from different software versions.
 iBSC V6.50.203DP01
 OMMR V12.13.09
 OMMB V12.12.40
The “OMM” mentioned in this guide all refers to the network management software
installed on the SBCJ board on BSC.
Unless otherwise specified, the “equipment” mentioned in this guide all refers to the
ZXUR 9000 GSM (V6.50.20) BSC.
1.3 Application Scope

This guide is applicable to the new sites to be commissioned with ZXUR 9000 GSM
(V6.50.20).
1.4 Conditions/Prerequisites
1. The “General Introduction” part contains important information. Readers should
read this part before starting the following work.
2. By reading the following contents, you agree to and understand the contents in
Chapter 1 General Introduction.
2 Commissioning Flow
Figure Commissioning Flow-1 Commissioning Flow
Explanation of each step is detailed in Table 2-1.

Table Commissioning Flow-1 Explanation of the Flow Chart
Steps Operation Description

Confirming system networking solution, obtaining the
IP addresses of the Server, Client, OMP, and OMM,
obtaining the system configuration parameters (incl.
1 Preparations the data for integrating with MSC A interface, and the
data for integrating with SGSN GB interface), system
debugging tools, materials (documents) and
software.
Checking the installation of racks, cables, modules,
Equipment Check and the power supply voltage.
2
Before Power-on Refer to ZXUR 9000 GSM (V6.50.20) Hardware
Installation Guide for details.
Checking the power supply for the boards and the
Equipment Check rotation direction of the fan.
3
with Power-on Refer to ZXUR 9000 GSM (V6.50.20) Hardware
Installation Guide for details.
Including the overview of OMCR system, networking
OMM Installation &
4 mode, requirements of OMM installation
Commissioning
environment, and OMM software installation flow.
With the quick data configuration tool, configure the
5 Data Configuration ground resource and radio resource, and
synchronize the configuration to BSC.
Creating board software version file to OMCR and
Version Loading &
6 activating it, setting and loading board software;
State Check
resetting boards on BSC to fulfill the version loading.
SDR – Abis Interface
7 Integrating SDR base station
Integration
Checking the transmission to MSC, integration data;
A Interface
8 observing and testing the data configuration after A
Integration
interface integration.
Checking the transmission to SGSN and the
GB interface
9 integration data; observing and testing the data
integration
configuration after GB interface integration.
Performing ZXUR 9000 hardware test, OMMR
function test, software version test, call test,
handover test, and tests on new functions. For
11 On-site testing details, please refer to ZXUR 9000 GSM (V6.50.20)
BSC Test Guide. When all the services are in normal
condition, it indicates the completion of system
commissioning.
3 Preparations
To guarantee smooth equipment commissioning for ZXUR 9000, the equipment
commissioning engineers should make enough preparation before the operation, such
as mastering the project information, confirming the system networking schemes, and
getting ready the tools, software and documents.
3.1 Project Information

Before commissioning ZXUR 9000 equipment, the engineers should find the customer’s
address and contact information, the person in charge from the customer, and the type
of the installed equipment; and contact with the local representative office in time to
learn the preliminary preparation for the project, and consult the related documents to
learn details about the equipment configuration, version information, equipment
shipment status.
3.2 Preparation of Tools & Meters

Prepare the tools and meters for system commissioning. The meters should be
calibrated to standard by the national measurement bureau. The commonly-used meters
and tools are: (It’s possible that only some of the following tools are used in
commissioning.)
1. Tools: cross screw-driver, flathead screw-driver, diagonal pliers, sharp-nosed pliers,

adjustable wrench, electric iron, solder wire, soldering flux, insulation tape, level
ruler, coaxial self-loop cable, cable peeler, crimping pliers, etc.
2. Meters: grounding resistance tester, multi-meter, testing phone (incl. SIM card), and
error bit tester, etc.
3. Others: laptop computer (installed with the necessary software like FTP and anti-
virus software), direct-connect cable, cross-connect cable, logical download cable,
computer display, keyboard, serial port cable, USB serial port converter, testing
cable for converting serial port to RJ45.
3.3 Preparation of Software

Based on the requirements of functions and performance from the site, prepare the
corresponding ZXUR 9000 and OMM software versions, Oracle database software
(V10), platform operation & maintenance tools (usually only probe and dynamic
management are installed), OMCR DTF tool, Telnet tool SecureCRT, anti-virus software,
in order to ensure smooth commissioning of ZXUR 9000 and realization of its functions.
The versions should be applied for from GU Product Support Dept. by the local
office/representative office. The versions to be used on site must be the officially-
released versions, which have passed the tests.
3.4 Preparation of Documents

Relevant technical documents should be prepared for consultation.
ZXUR 9000 GSM (6.50.20) BSC Hardware Description
ZXUR 9000 GSM (V6.50.20) BSC Hardware Installation Guide
ZXUR 9000 GSM (V6.50.20) Routine Maintenance
3.5 Confirmation of System Networking Plan

 Before system commissioning, the on-site engineers should confirm the system
networking mode according to customer’s requirement, drawing the network
topology map, identity the locations and connection relations of different pieces of
equipment. In the case of remote networking, it is required to identity the locations
and connection relations of routers, exchanges, and other equipment.
 Based on the system networking map, equipment commissioning engineers should

offer suggestions on IP address planning and routing configuration, and confirm the
IP addresses of NEs and configuration of network routing after discussing with the
customer.
 Communicate with the customer to acquire the A interface/GB interface integration

data and radio data. Refer to Appendix A and Appendix B for the forms of A
interface/GB interface integration data.
4 Equipment Check before Power-on

After the ZXUR 9000 equipment is installed, checks must be performed again before
powering up the equipment (checks after equipment installation acceptance) to ensure
correct installation of all pieces of equipment.
Checks before equipment power-up should cover test on power supply voltage, check
on hardware, and check on cables.
4.1 Power Supply Voltage Check

Purpose
Check and confirm that the input power voltage is within the allowed range, in order to
prevent equipment power-up failure.
Preparation
All the power switches on ZXUR 9000 are in the disconnect state.
Procedure
1. Check the quantity of boards according to the system configuration list and make
sure that none of the boards is inserted in the shelf.
2. Make sure that all the switches on power distribution sub-rack are in the OFF state.
3. Turn on the power switch on DC power distribution cabinet, and then test the -48V
power supply input to the cabinet with a multimeter. If the test result falls within -57
DCV ~ -40 DCV, it means the power supply is appropriate.
Result
 Upon the occurrence of problems, disconnect the switch of power supply loop
immediately and ask the power equipment manager of the customer’s equipment
room to locate and remove the cause of problem.
 If no problems appear, proceed to the next step.
Caution:
Mind electric shock! When checking the various power supplies, pay attention to the status
(ON/OFF) of the electric switches and try to avoid getting electric shock.
4.2 Hardware Check
4.2.1 Cabinet Check
Purpose
Make sure that the cabinet installation is up to standard to prevent equipment operation
problems caused by engineering factors.
Procedure
1. Check the horizontal and vertical deviations of cabinet after the installation.
2. Check the completeness of cabinet components and soundness of cabinet paint

coat.
3. Check the completeness of labels on the cabinet.
4. Check whether the bolts are tightly fastened or not.
5. Check whether the cabinet installation is reinforced with earthquake-proof

measures.
6. Check the soundness of boards after they are inserted in the corresponding slots.
Result
1. Cabinet must be installed erect on the base. After it is installed, the horizontal and
vertical deviations should not exceed 3mm.
2. All the parts on the cabinet shall not be detached or damaged; there shall be no
peel-off or damage on the cabinet paint coat. If any part of the coat is peeled off or
damaged, the part shall be painted again.
3. All kinds of labels on the cabinet shall be complete and clear.
4. The fastening bolts must be tightly screwed. The part of bolts of the same type
exposed above the caps should be of the same length and height.
5. Cabinet installation must be reinforced with earthquake-proof measures; fix the

cabinet on the floor with grounding bolts if necessary.
6. The board cards are firmly and reliably connected. It is convenient to insert or
extract the cards. The surface of the slots shall be even after the cards are
inserted.
 If any items fail to meet the requirements/standards, the on-site project manager
should contact the project construction team to make adjustment accordingly.
 If the above requirements are satisfied, proceed to the next step.
4.2.2 ZXUR 9000 GSM Hardware Installation & Cable Connection
Purpose
Make sure that the hardware installation and cable layout are up to standard to prevent
equipment operation problems caused by engineering factors.
Procedure
For details, refer to the following steps and ZXUR 9000 GSM (V6.50.20) Hardware
Installation Guide.
Result
If any items fail to meet the requirements/standards, the on-site project manager should
contact the project construction team to make adjustment accordingly.
4.2.2.1 Shelf & Board Installation
For the newly-delivered equipment on site, the shelves and boards are usually
separately placed. They will be configured and installed according to the planning on
site.
1. ZXUR 9000 GSM all uses single racks, each of which contains three shelves
numbered as Shelf1/2/3 from top to bottom. Only one of them is the main shelf,
which can be set from the CDM DIP. Shelf3 is the main shelf by default.
2. The two UMPs (OMM) should be inserted into Slot5 and Slot6 at the front of the
main shelf.
3. The two UMPs (OMP) should be inserted into Slot7 and Slot8 at the front of the
main shelf.
4. The control plane switch boards (EGBS) should be inserted in to Slot19 and Slot20
at the rear of each shelf (two EGBS boards for each shelf).
5. The media plane switch boards (EGFS) should be inserted in to Slot21 and Slot22
at the rear of each shelf (two EGBS boards for each shelf).
6. The interface boards like EGPB, EDTI, ESDTI, EDTT, ESDTT can only be inserted
in to Slot 15-18 or 23-28 at the rear of each shelf; they should be installed
according to the on-site networking plan.
7. The processing boards (USP and ETCB) should be inserted in to the slots at the
front of each shelf according to the configuration planning.
8. The slots of master/slave boards in BSC V4: the front slots are {1, 3}, {2, 4}, {5, 6},
{7,8}, {9,10}, {11,13}, {12,14}; the rear slots are {15,16}, {17,18}, {19,20}, {21,22},
{23, 24}, {25, 26}, {27, 28}.
Each board is labeled for distinguishing different types of boards. For example, the
server board of OMM is labeled like “UMP-OMM”, and OMP is labeled like “UMP-OMP”.
Other boards are labeled in the similar way. Engineers need to check the labels on the
boards and insert them in to the correct slots.
Warning:
The physical boards of OMM and OMP are the same, but their logical functions and the pre-
set systems in them are different. They must be clearly distinguished. If they are inserted in
to each other’s slot by mistake, faults like abnormal system and full disk space may be
caused.
4.2.2.2 CDM DIP & Check
The shelf data modules (CDM) are located at the two sides of the service sub-rack’s
bottom. Each service sub-rack is configured with two CDMs for storing the shelf-related
information (shelf SN), board power-up information (board type for the slot, board power-
up/down allowed or not, board boot mode, etc.), and other customized information.
The shelf information needs to be set with the DIP and jumper, which are usually set
before they are delivered. The power-up information of boards is configured with the
default value in CDM before the boards are delivered, which is invisible. The third shelf
is the master by default, and the board types and boot mode of the OMM boards in Slot5
& Slot6 and the OMP boards in Slot7 & Slot8 are different from those of the boards in
other slots. Therefore, we must check the DIP and jumper of the CDM in each shelf
during the installation of shelf and boards, and make sure the CDMs of the three shelves
are inserted in to the corresponding shelves according to their own DIP. DO NOT mix up
the CDM modules of each shelf, otherwise, the boards may not be powered up normally.
Figure Equipment Check before Power-on-2 Shelf Data Module CDM
There are 8 jumpers on CDM. Refer to Table4-1 for the meanings of them.
Table Equipment Check before Power-on-2 Definitions of Jumpers on CDM Module
Jumper 1 2 3 4 5 6 7 8
SN ID0 ID1 ID2 ID3 ID0 ID1 - -
DIAG
Meaning RACK SHELF CHECK
Mode
When the jumper cap is plugged, it means the jumper state is ON, which is represented
in 0; when the jumper cap is unplugged, it means the jumper state is OFF, which is
represented in 1. From left to right, the jumpers are ordered from low bit to high bit. For
example, when jumper 1, 2, and 3 are all capped in one cap, but other jumpers are not,
it means the shelf is located in the third shelf on Rack8.
The seventh jumper cap is fixed to be unplugged (OFF).

The eighth jumper (odd check bit) is for checking the odd bit. It is used to ensure that the
total number of jumper caps that are ON on CDM is an odd number. If the total number
of jumper caps that are ON CDM is an even number, the system will display jumper
mistake.
The following figure shows the DIP map of the CDM in the third shelf. Only the caps of
Jumper 2, 3, 4 in the RACK area are ON, represented in 0. For other jumpers, only one
of their two pins is capped, meaning they are OFF, represented in 1. The seventh jumper
(diagnostic bit) is OFF. The eighth jumper (check bit) is OFF, because the caps of three
jumpers (2, 3, 4) (an odd number) are capped.
Figure Equipment Check before Power-on-3 DIP of CDM in Shelf3
Note:
There are two ECDMs on one service rack. Make sure the configurations of jumpers for the
two ECDMs are consistent, and the information of rack and shelf is the same.
4.2.2.3 Cable Connection on Control Plane
The cables on the control plane are connected to the rear board EGBS on the shelves,
which are installed at the rear of the cabinet.
In the case of configuration with 1 master shelf + 2 subordinate shelves:
End A of Cable1 is connected to ETH1 port of master EGBS board of master shelf, end
B is connected to ETH1 port of master EGBS board of subordinate shelf 1;
B is connected to ETH1 port of slave EGBS board of subordinate shelf 1;
B is connected to ETH1 port of master EGBS board of subordinate shelf 2;
B is connected to ETH1 port of slave EGBS board of subordinate shelf 2;
Cables No. 5, 6, 7, 8 are respectively connected to the ETH2 ports of the master/slave
EGBS boards of maser/subordinate shelves.
Refer to Figure4-3:
Figure Equipment Check before Power-on-4 Cabling of Control Plane Inter-Connection

Ethernet Cable
4.2.2.4 Cable Connection on Media Plane
The cables on the media plane are connected to the rear board EGFS on the shelves,
which are installed at the rear of the cabinet.
End A of Fiber1 is connected to RX1-TX1 port of master media plane switch board
EGFS of master shelf, end B is connected to RX1-TX1 port of master EGFS board of
subordinate shelf 1.
End A of Fiber2 is connected to RX2-TX2 port of master EGFS board of master shelf,
end B is connected to RX1-TX1 port of master EGFS of subordinate shelf 2.
Connect Fiber3 and Fiber4 in the same way.
Refer to Figure4-4:
Figure Equipment Check before Power-on-5 Cabling of Media Plane Inter-Connection

Fiber
4.2.2.5 Clock Cable Connection
When the system’s reference clock source comes from the 8K line reference clock
provided by the upper-level and sent by the interface board, the line reference clock
cable should be used, which should be installed at the rear of the cabinet.
End A of one SE1 clock cable is connected to the CKOUT2 reference clock output port
of interface board 1 on the master shelf. End B is connected to the REF1 reference clock
input port of EGFS1 on the master shelf.
End A of one SE1 clock cable is connected to the CKOUT3 clock output port of interface
board 1 on the master shelf. End B is connected to REF1 clock input port of EGFS2 on
the master shelf.
board 2 on the master shelf. End B is connected to the REF2 clock input port of EGFS 1
on the master shelf.
board 2 on the master shelf. End B is connected to the REF2 clock input port of EGFS
board2 on the master shelf.
Refer to Figure4-5:
Figure Equipment Check before Power-on-6 Cabling of Line Reference Clock Cables
When the system’s reference clock source comes from the 2 MBps or 2 MHz reference
clock provided by BITS, the BITS reference clock cable should be used, which should be
installed at the rear of the cabinet.
The cabling direction includes upward cabling and downward cabling.
Upward cabling: All clock cables are threaded out from the top of the cabinet, and then
led upward to the cable tray.
Downward cabling: All clock cables are led along the cable troughs at the two sides in
the cabinet, and then threaded out from the bottom of the cabinet to under the floor.
End A of one SE1 clock cable is connected to the REF1 or REF2 reference clock output
port of master EGFS board on the master shelf. End B is connected to DDF, and a cable
from DDF is connected with the system clock output port of BITS. The other SE1 cable
is connected to the slave clock port.
Whether end B of it is connected to the REF1 port or REF2 port is not defined yet. It is
subject to the networking situation on site.
Cabling route for BITS reference clock is shown in Figure Equipment Check before
Power-on-7 (using upward cabling as an example):
Figure Equipment Check before Power-on-7 Cabling of BITS Reference Clock Cables
Note:
Whether the system reference clock comes from upper-level office or BITS is subject to the
networking situation on site. The two methods can be used independently or together.
For connections of clock cables across shelves, we need to connect the clock
generation board EGFS in the master shelf to the clock signal (8K, 25M, PP2S) on the
EGFS board in the subordinate shelf, and set the distribution of synchronization clock
signal of each sub-rack in the system. Perform the installation at the rear of the cabinet.
End A of one DS-G0505-001 cable is connected to CLK2 clock output port on the switch
board EGFS of master media plane of master shelf, end B1 is connected to PTP1 clock
input port on the switch board EGFS of master media plane of subordinate shelf, and
end B2 is connected to PTP1 on the slave EGFS board of subordinate shelf 1.
End A of the other DS-G0505-001 cable is connected to CLK2 port on the slave EGFS
board of master shelf, end B1 is connected to PTP2 port on the master EGFS board of
subordinate shelf 1, and end B2 is connected to PTP2 port on the slave EGFS board of
subordinate shelf 1.
In the same way, the master/slave CLK3 ports of the master shelf are respectively
connected to the master/slave PTP1 and master/slave PTP2 of the subordinate shelf 2.
Refer to Figure Equipment Check before Power-on-8:
Figure Equipment Check before Power-on-8 Cabling of Inter-Shelf Clock Cables

4.2.2.6 Alarm & Monitoring Cable Connection
Connect the alarm and monitoring cables to realize the communication between the
operation & maintenance board and the power module, and to monitor the PDU status.
Perform the installation at the rear of the cabinet.
End A is connected to the RS485 (IN) port of the PDU sub-rack. End B1 and End B2 are
respectively connected to the RS485 ports on the master/slave EGBS boards of the
control plane switch board on the master shelf. If End B1 is connected to the RS485 port
on the master EGBS of, End B2 should be connected to the RS485 port on the slave
EGBS of the control plane switch board in the master shelf, or vice versa.
Refer to Figure Equipment Check before Power-on-9:
Figure Equipment Check before Power-on-9 Cabling of PD485 Monitoring Cables
4.2.2.7 Connection of Other Cables
For the connection of power cables and grounding cables, refer to the ZXUR 9000 GSM
(V6.50.20) Hardware Installation Guide.
For the connection of E1/T1 cables, network cables, and optical fibers, refer to the
ZXUR 9000 GSM (V6.50.20) Hardware Installation Guide, and install these cables
according to the planning and networking on site.
4.2.3 Auxiliary Equipment Check
4.2.3.1 Alarm Box Check
Purpose
Make sure that the alarm box installation is up to standard to prevent alarm box
operation problems caused by engineering factors.
Procedure
1. The alarm box should be installed at a highlighted position, so that it is easy to be

observed and noticed when the alarm goes off.
2. The height of the alarm installation position should be appropriate for easy
operation on the alarm box.
3. The power cables and network cables connected to the alarm box should be laid in
the tough without cable ends exposed.
4. The alarm box must be firmly installed.
5. In the case that several alarm boxes are installed one by one, they should be
clearly labeled (indicating what equipment they are associated to) for distinction.
Result
If the above requirements are satisfied, proceed to the next step.
4.2.3.2 Sensor Check
Purpose
Make sure that the sensor installation is up to standard to prevent sensor operation
problems caused by engineering factors.
Procedure
1. The infrared sensors are appropriately located with detection range covering the
key entrances/exits of the equipment room.
2. The temperature and humidity sensors are installed appropriately within 1m from
the cabinets.
3. The smog sensors should be installed on the ceilings above the cabinets.
Result
If the above requirements are satisfied, proceed to the next step.
4.2.4 Other Checks
Purpose
To ensure appropriate installation of equipment hardware and prevent equipment

operation problems caused by engineering factors
Procedure
1. The equipment labels are complete, correct and clear.
2. The quantity of boards is correct.
3. The switches on equipment are all in the initial position.
4. The work ground cable, PGND cable, and lightning-proof ground cable of the
equipment are well grounded, and the grounding resistance should meet the
requirement. The lap resistance between racks should be 0.1 Ω–0.3 Ω, and the
grounding resistance in the equipment room is less than 1 Ω.
5. The specification of the fuse used should meet the rated nominal. The pins on the
rear board are not distorted or short-circuited. There is no short-circuiting between
the positive and the negative power supply.
Result
 If any items fail to meet the requirements/standards, the on-site project manager
should contact the project construction team to make adjustment accordingly.
 If the above requirements are satisfied, proceed to the next step.
4.3 Check Record before Power-on
Table Equipment Check before Power-on-3 Check Record Before Power-on
No. Test Content Completion State Data Record Remarks

Power supply
1 □ OK □ NOK
voltage test
2 Hardware Check
Cabinet Check □ OK □ NOK

Cable Check □ OK □ NOK
Auxiliary Equipment
4
Check
Alarm Box Check □ OK □ OK
Sensor Check □ OK □ OK
5 Other Checks □ OK □ OK
5 Equipment Power-Up
Purpose
To power up the ZXUR 9000 shelves.
Preparation
The pre-power-up checks are completed; the hardware and switches on cabinet are in
the required state.
Procedure
1. Set the PWR air break on power distribution sub-rack as ON, and observe the
PWR IN indicator on it. In normal condition the indicator should be on.
2. Set the air break corresponding to a single service sub-rack on the power
distribution sub-rack as ON, and observe the fans in the service sub-rack. In normal
condition the fans should be operating normally. Test the -48V power input to the
service sub-racks with a multimeter. In normal condition the tested voltage should
fall within -57DCV~-40 DCV.
3. Set the air break corresponding to a single service sub-racks on the power
distribution sub-rack as OFF. Now all the fans should stop operating. Test the -48V
power input to the service sub-racks with a multimeter again. Now the test voltage
should be 0V.
4. In the case of more than one sub-rack, repeat step2-3.
5. Confirm the slot IDs and insert the boards one by one accordingly.
6. Set the air break corresponding to a single service sub-rack on the power
distribution sub-rack as ON, and observe whether the state of indicators on panel
and the operation state of fans are normal.
Result
 Upon the occurrence of problems, disconnect the switch on power distribution sub-
rack immediately, and investigate and remove the problem.
Note:
Please plug out the OMP board at Slot 8 before powering on the board. The OMP boards are
configured the same when they are delivered from the factory and there is no master/slave
configuration, with the IP as 129.0.1.1 by default. Therefore, when ZXUR9000 GSM
commissioning and service test are performed with OMM, the configuration will conflict and
the link between ZXUR9000 GSM and OMM cannot be established. In this case, after the
version is loaded and activated and configuration data all-table synchronization is completed
in the commissioning process, it is necessary to plug in the OMP at Slot 8.
Power up the boards in the following sequence: ECMM (EGBS) > OMM > OMP > other
PP. Make sure the main boards such as OMM, OMP, and EGBS are powered up
normally (by observing the indicator flashing state).
6 Equipment Check with Power-on

When the equipment is powered up, the ZXUR 9000 data is not configured in OMCR
yet, therefore the status of boards may appear normal. Therefore, the checks after the
equipment is powered up should be focused on the power supply state of the boards
and the wind direction from the fan.
6.1 Board Check

Purpose
Check whether the boards are powered up or not.
Preparation
The cabinet is powered up and the boards are inserted in the corresponding slots.
Procedure
For the first time of power-up, the board should be inserted to the right position, and the
board indicator should be on. For the description of board indicators, refer to ZXUR 9000
GSM (V6.50.20) Hardware Description.
Result
 If the board indicator fails to light up, extract the board and insert it in a different
slot, and check whether it can be powered up. If yes, it means there is a problem
with power supply to the previous slot; consult the 800 hotline about the problem. If
not, it means there is a problem with the board; replacement of board is
recommended.
Note:
The board may not be in normal operation state, just focus on whether it can be powered up
normally.
6.2 Fan Rotation Direction Check

Purpose
To check whether fans can work normally
Preparation
The equipment is powered up.
Procedure
1. Pull out the board under the fan sub-rack, in order to test the fan’s rotation.
2. Put a 20cm-long paper slip into the sub-rack under the power sub-rack. If the paper
slip is blown upwards, it indicates the wind from the fan blows upwards from the
cabinet bottom, meaning the fan functions well with correct rotation direction.
Result
 If the paper slip does not fly (because the fan is not rotating) or is blown downwards
(due to wrong fan rotation direction), it is necessary to check whether there is any
problem with the fan.
6.3 Check Record with Power-on
Table Equipment Check with Power-on-4 Check Record after Power-on

Board Power
1 □ OK □ NOK
Supply Check
Fan Rotation
2 □ OK □ NOK
Direction Check
Warning:
Blank panels must be installed to fill the idle slots on ZXUR 9000 shelf, so that the wind
channels can be evenly distributed in the V4 shelf and shelf overheat can be avoided.
6.4 Power-down Procedure

1. Turn off the of -48V power switch on the sub-rack filter at the rear of each sub-rack.
2. Turn off the two -48V power switches on the panel of power distribution sub-rack on
top of the cabinet.
3. At the DC power distribution cabinet turn off the -48V power output to the cabinet.
7 OMM Installation & Commissioning

Refer to ZXUR 9000 GSM (V6.50.20) OMM Commissioning Guide.
8 Data Configuration
8.1 Creating SubNetwork

Subnet is a configuration object in the northbound interface information model. Only one
managed NE can be created under one subnet.
8.1.1 Creating SubNetwork
1. On the configuration resource tree, right-click and choose Create Subnetwork, as

shown in Figure Data Configuration -10.
Figure Data Configuration -10 Create Subnetwork 1
2. An interface pops up at the right side. Input the information of Alias and
SubNetwork ID, and click to save the creation of subnetwork. See Figure Data
Configuration -11.
Figure Data Configuration -11 Create Subnetwork 2
8.1.2 Subnetwork Query/Modification
1. After the subnetwork is successfully created, a corresponding node appears on the

configuration resource tree, as shown in Figure Data Configuration -12. Double-
click the node. The configuration attributes of the object will be displayed on the
right side of the Configuration Management interface.
Figure Data Configuration -12 Querying Subnetwork
2. Click on the shortcut menu of the configuration object, and modify the object’s
attributes. After the modification, click to save the modified parameters. When
modifying the object’s attributes, we can cancel the modification by clicking .
8.2 Configuring Managed Element

Managed element is a sub-node of sub-network. One sub-network can only contain one
managed element.
8.2.1 Adding the Configuration
1. On the configuration resource tree, right-click the created sub-network and choose
Create Managed Element, as shown in Figure Data Configuration -13.
Figure Data Configuration -13 Create Managed Element 1

2. Input the correct parameter information in the Element interface, and click to
save the creation, as shown in Figure Data Configuration -14.
Figure Data Configuration -14 Create Managed Element 2
8.2.2 Configuration Query/Modification/Deletion
Query, modification, and deletion of different managed elements are similar. Refer to
8.1.2 Subnetwork Query/Modification.
8.3 BSC-OMCR Link Establishment

When creating managed element, input the system’s default IP address 129.0.1.1 for
managed element IP address. Check whether the icon appears in front of the
created managed element in OMCR. If yes, it means the link between ZXUR 9000 and
OMCR is successfully established. If the icon appears, it means the link is not
established yet.
Troubleshooting for the common faults that may cause link establishment failure:
1. Check whether the IP configuration in the deploy-999split.properties file is

correct or not.
ums.systemproperty.com.zte.ums.uep.localaddress=10.63.208.217
ums.systemproperty.com.zte.ums.bind.socket.client.ip=129.200.0.1
ums.services.bind.multi.local.addresses=129.200.0.1,128.0.30.9
Note: The deploy-999split.properties file is saved in the /ZXM-OMMR/ums-

svr/deploy directory.
For “10.63.208.217”, input the IP of eth2:1 according to on-site planning; for

“129.200.0.1”, input the IP of bond2:1, which is fixed; for “128.0.30.9”, input
“128.0.30.1” for left board, and “128.0.30.9” for right board, which are fixed.
2. Check whether the link establishment IP of OMP is wrongly changed.
Firstly, calculate the internal IP of the board according to the rack/shelf/slot

information of the OMP board. (For example: The internal IP of OMP at Slot 7,
Shelf 3, Rack 1 is “128.129.17.231”.)
Secondly, use the telnet command to connect OMM to OMP as follows:
#telnet 128.129.17.231, user name: zte, password: zte
After connecting to OMP, check the external network port IP of OMP. The
bond0:240 IP address is the IP for OMP link establishment.
Finally, modify the IP for OMP link establishment in OMMR.
 Change the IP of managed element to the IP of “bond0:240” to establishment

the link.
 Change the “Omp’s omc port ip*” under System Global Configuration >
Operation Maintenance Configuration to “129.0.1.1”, and “Omp’s omc port
mask length*” to 8.
 After all-table synchronization, OMP’s IP for link establishment is changed to

“129.0.1.1”.
3. If we can ping through the address of OMP: 129.0.1.1, change the IP of managed
element to a temporary IP, and then change it back to 129.0.1.1, in order to trigger
the OMP link establishment.
8.4 Import of Quick Data Configuration Template

Refer to ZXUR 9000 GSM(V6.50.20) Quick Data Configuration Guide.
Data configuration is the core of base station controller system, which plays a very
important role in the whole system. Any data configuration error can cause serious
impact on the system operation. Data configuration operator must pay attention to the
following points when configuring and modifying the data.
1. Before data configuration, the data related to system operation (like A interface/GB
interface integration data) should be prepared, which must be accurate and
reliable. A complete data configuration plan should be created. A good data
configuration plan can not only increase the clarity and reasonableness of data, but
also enhance the system’s reliability.
2. Before data modification, we need to back up the current data. After the
modification, synchronize the data to ZXUR 9000 and base station. Confirm the
correctness of the data and back it up in time.
3. The data configured or modified from the OMCR client has to be synchronized
before it can take effect. Perform careful checks on modifications to the system
data that is applied in the system operation. Synchronize the data after the
modifications are confirmed correct, otherwise the error data may affect system
operation.
4. After the quick data configuration template is imported, do not perform data
synchronization (because the ZXUR9000 GSM version may be inconsistent with
the OMCR version and error will be reported in data synchronization). Perform data
synchronization after the versions are loaded. Refer to the following chapters for
details.
Note:
There are many parameters involved in data configuration. Only the key parameters and the
ones that need modification are explained in this guidebook; they should be configured
according to the corresponding instructions. Keep the default settings of the rest parameters
that are not explained here.
9 Version Loading & State Check
9.1 Version Package & Loading Flow
9.1.1 Version Package
ZXUR 9000 (V6.50.20) is a new-generation multi-mode controller based on the V4

hardware platform. The directories contained in its version package are as follows:
 pgk: version package file;
 GsmTools: store the tools such as LMT, logservice, and DTF, etc.
 Firmware: the directory saving the firmware version (incl.

boot/fpga/epld/fru/ipmc etc.)
 DSP_MAPOUT: store the DSP fault location files.

Upon equipment commissioning, the following versions may be required: ESMS/ECMM

version package, platform version package, GSM version package.
9.1.2 Version Loading Flow
The version loading flow based on the V4 platform is as follows.
Figure Version Loading & State Check-15 Version Loading Flow

9.1.3 Generating ZDB Data and Snapshot Area on OMMR
Click View > MML Terminal, and execute the MML command to generate ZDB data and
snapshot area.
Figure Version Loading & State Check-16 Open MML Terminal
1. Generate ZDB data with the MML command:
GET
ZDB:POS="SubNetwork=1,MEID=1",RADIOTYPE=2,SYNCTYPE=0,ISCHECK=
0;
POS: should be modified according to the subnetwork ID and MEID in the

configuration data.
RADIOTYPE: radio type. GU = 0; GT = 1;GSM = 2; UMTS = 3;TD = 4; AG = 5;
SYNCTYPE: Synchronization type. 0: Synchronize all table; 1: Synchronize

modified data.
ISCHECK: Whether to perform global check. 0: not perform global check; 1:

perform global check.
2. Generate the snapshot area with the following MML command:
TESTRESNAPSHOT:MEID="1",SYNCTYPE=0;
MEID: Fill in the MEID of BSC in the configuration data.
9.2 Checking the Factory Version

Refer to AppE for details. Make sure the factory version is one of 6.50.20 series.
9.3 Checking the Firmware of Independent Boards

Before Upgrade
Refer to AppF for details.
Note: This step is required only for the factory version of 6.50.10 series. For the boards
of 6.50.20 series, skip this step because the firmware meets the requirement by default.
9.4 Loading Software Version

Note: All-data synchronization will be performed during this step. Therefore, it must be
confirmed the following: the data configuration has been completed, global data validity
has passed the check, and there is no other user occupying the configuration mutex
right.
9.4.1 Creating the Initial OMP Package
Create the initial OMP package with PLAT_V6.50.202EP02.pkg.
Right-click the Created Package Management on the toolbar, and click Initial
Package Create in the opened window. In the pop-up dialog box, set Create type as
“OMP Initial,” add the PLAT_V6.50.202EP02.pkg platform software package, and
click OK, as shown in the figure below.
Figure Version Loading & State Check-17 Create Initial Version Package
Follow the above steps to create the initial version of ECMM, initial version of EGBS,
and initial version of EGFS.
9.4.2 Setting the Version of Independent Boards

1. Ftp the RmEgbsLocalVerFile.py script to the /home/installtmp directory of
the OMM board. Execute the RmEgbsLocalVerFile.py script as the root user
on OMM, and clear space in the FLASH of EGBS.
The format of script RmEgbsLocalVerFile.py is:
python RmEgbsLocalVerFile.py (required) Parameter2 (optional)
Parameter 1: defines the shelf No.; range: 1-3
Parameter 2: defines the slot No.; range: 19-20. If this parameter is null, it means
deleting all the files in the running version directory in the Flash of all EGBS boards
in the specified shelf.
If multi-shelf configuration is used, the script needs to be executed for each shelf.
Example: Execute the following command to clear the space in the FLASH of the
EGBS in Shelf 3.
# python RmEgbsLocalVerFile.py 3
2. Open the MML terminal, and execute the following MML command to set the
versions of independent boards.
Select View > MML Terminal on OMMR, and execute the following MML command
to download, activate, and validate the initially-configured version package of the
independent boards.
SWITCH BRD VER DOWNLOAD:MEID=1,ISACTIVE=TRUE,ISVALIDATE=TRUE;
Note: The MEID here is the RNCID.
9.4.3 One-click Version Upgrade
Starting from V6.50.20, one-click upgrade mode is used to complete the BSC software
version upgrade, version download and activation of independent board, and data
synchronization.
Open Software Version Management > Update Management.

Figure Version Loading & State Check-18 Upgrade Management Interface　
Click the Add button to add the BSC software version and the software version of
independent board.
Select the two version description files at the same time.
Select the NE for upgrade.
Click Start to start the one-click version upgrade.

Note:
The upgrade must not be performed until the configuration data and global data have
passed the validity checks.
The mutex right must be released before the upgrade.
During the upgrade, the system powers down the slave OMP. After the upgrade, click the
Confirm button, so that the system will automatically power up the right OMP board.
9.4.4 OMP Running Version Query
Open the rack diagram in Status Management. Select the OMP board and right-click to
select Board running version query to check whether the running OMP version is the
correct one.
Figure Version Loading & State Check-19 OMP Running Version Query
9.5 Data Synchronization

Data synchronization falls into two types: all-data synchronization and modified-data
synchronization (incremental synchronization). When OMP starts to run normally,
perform all-data synchronization to deploy the configuration data from OMCR.
Note:
Preconditions for data synchronization: normal link establishment between OMP and NE;
global data check result meets the requirements. Otherwise the data cannot be synchronized.
9.5.1 All-data Synchronization
1. In the pane of configuration resource tree, right-click RNC to select Synchronize

All Data.
Figure Version Loading & State Check-20 Synchronize All Data
2. The interface of Global Check pops up.

Click Start to carry out global data check. If the check result meets the
requirement, click Next. The following dialogue box for confirmation pops up.
Note:
Do not reset OMP during data synchronization.
3. Click OK to start the data synchronization. After the synchronization ends

successfully, the following interface pops up.
4. When the progress bar reaches 100% and the Status shows Synchronization
Success, it means all-data synchronization finishes successfully.
5. Click CLOSE to finish the operation.
9.5.2 Modified-data Synchronization
Purpose
When only part of the data is modified, we can just synchronize the modified data to
speed up the synchronization process. This section introduces how to perform the
incremental synchronization.
Preparation
1. Apply for mutex right.
2. The connection link between iBSC and OMCR is normal.
3. The incremental data exists.
Procedure
1. In the configuration resource window, right-click RNC and select Synchronize

Modified Data.
2. The following steps are similar to those of all-data synchronization.
9.6 Loading ECMM Software Version

1. Click Software Version Management and select Update Management, as shown in
the following figure.
Figure Version Loading & State Check-21 Load ECMM Software Version
2. Click Add to enter the \pkg\RELEASE directory of version package and select
“iBSCV6.50.202EP01_1042_ecmm_softwaredesc.xml.”
3. Click Start to start the version upgrade. The version file storage path on the OMM
server is: \ums-svr\tmp\ftp\version\cmm\
4. After the version upgrade is 100% completed, successful upgrade will be displayed
under Update Result.
Note:
After a fresh ECMM upgrade, we need to wait for about 20 minutes before performing the
version consistency check, because it takes some time to write the version information into
ECMM.
9.7 Loading Firmware Version

Currently, the firmware falls into the following types, EPLD, IPMC, FRU, FPGA,
BOOTROM, and PDUM.
FPGA is included in the BSC software and is loaded with the BSC software version.
Other firmware packages are packed separately according to their types. Select the
board version and firmware version on the version upgrade interface in OMM and start
the one-click load to activate the version.
Note: In the upgrade of firmware version, except for PDUM version and the rear card
BOOT version, which are loaded and activated through version management (one-click
upgrade in the current version is flawed, which will be solved in the later OMMR
versions), others all adopt the one-click upgrade mode.
Load the firmware packages in the following sequence.
1. ECMM boot
2. ECDM FRU
3. PDUM board
4. BOOT version of rear cards
5. EPLD
6. IPMC/FRU
Note: The loading of versions that will trigger immediate reset in the loading process
should be performed lastly, in order to reduce the number of board resets.
9.7.1 ECMM Boot Loading
1. In Software Version Management window, click the Update Management

button and open the Version Update Management window.
2. Load the ECMM Boot version package, as shown in the figure below.
Figure Version Loading & State Check-22 Load ECMM Boot Firmware Version
3. Choose the NE to be updated and the ECMM shelf, and click Start to start the
upgrade. An observation of the Alarm Management window shows that ECMM
restart causes control-plane communications alarms, but it does not affect services.
After the alarm disappears, check the consistency of ECMM version.
9.7.2 Loading PDUMBOOT Version
1. Enter Update Management.
2. Add the PDUMBOOT version of the new version in the window, as shown in the
figure below.
Figure Version Loading & State Check-23 Load PDUMBOOT Version
3. Select OMP and click Start.

9.7.3 Loading Rear Card Boot Version
1. Open the Update Management interface.
2. Add the rear card BOOT version of the new version in the window, as
shown in the figure below.
Figure Version Loading & State Check-24 Load Rear Card Boot Version
3. Select OMP and click Start.

9.7.4 Loading EPLD
1. In Software Version Management window, click the Update Management

button and open the Version Update Management window.
2. Add the EPLD version package, as shown in the figure below.
Figure Version Loading & State Check-25 Load EPLD Version
3. Select the NE and the board to be updated, and click Start to start the
upgrade. After the loading is completed, check the consistency of the
EPLD version of the boards.
9.7.5 Version Consistency Check
Select Software Version Management > Version Valid Check to check the version
consistency.
Figure Version Loading & State Check-26 Version Consistency Check

If errors exist, the inconsistent versions will be displayed on the right.
9.8 ZXUR 9000 Running Version Query
9.8.1 Software Version Query
1. Select View > Status Management > SubNetwork > RNC > Physical Resource,
and double-click Controller Rack.
Figure Version Loading & State Check-27 Software Version Query
2. Double-click Rack to view the rack diagram.

Right-click the board to select Board running version query.
9.8.2 ZXUR 9000 Board Alarm Query
Select View > Fault Management > SubNetwork, and right-click RNC to select Show
Alarm Rack. Right-click the board to select Show current board alarm.
9.9 Online Configuration of Independent Board
9.9.1 Configuration of Independent Board

The online configuration of independent board mainly covers the configuration of time
zone and daylight saving time for the ECMM board, the configuration of BSC clock, the
configuration of environment monitoring parameters, and the configuration of board
parameters.
9.9.2 ECMM Configuration

Select Configuration Management > Independent Board Configuration Online, as
shown below.
Figure Version Loading & State Check-28 Online Configuration of Independent Board
Select the shelf for modification, and select Modify to change the time zone and daylight
saving time.
9.9.3 Configuration of System Clock
Select Configuration Management > Independent Board Configuration Online, and then
modify the ETCA clock information.
Note:
For the BITS clock or the clock extracted on the A interface, select REF(1) or REF(2),
and select Invalid for the type. For the GPS clock, select REF(3), and select GPS for the
type.
9.9.4 Configuration of System Environment

Select the ECMM shelf board information configuration to configure the Environmental
monitoring parameters. Modify the environmental monitoring parameters according to
the actual configuration.
9.9.5 Activation
Select Activate to save the online configuration data of independent board.
10 SDR – Abis Interface Integration

In the OMCR of V4 platform, configure the base station data through the quick data
configuration template. For base station data configuration, refer to the details of
V4_Template_TransportNetwork.xls and GSM Radio Quick Configuration
Template.xls in ZXUR 9000 GSM(V6.50.20) Quick Data Configuration Guide.
10.1 Preparation
Before the integration of SDR- A interface starts, the following preparation work should
be done:
1. The installation and commissioning of ZXUR 9000 is completed, and each board
works properly.
2. The Server is already installed and commissioned.
3. The MSC runs normally, and the data configuration on the A interface is completed.
4. The transmission between SDR base station and ZXUR 9000 is normal.
5. The radio parameters of SDR base station are correctly configured on OMMR.
6. SDR base station is commissioned and runs properly.
10.2 Checking SDR Base Station Status

1. Check the SCTP association state according to the planned data. Select Status
Management > SubNetwork > ME > Transmission Resource, double-click SCTP
Association, and right-click the site record in the right pane and choose SCTP
Association Status and Key Information Query.
Figure SDR – Abis Interface Integration-29 Check SDR Base Station Status
If ESTABLISHED is displayed, it means the SCTP association is in normal state.

2. Check the BTS/cell operation state. Select Status Management > SubNetwork >
ME > GSM Radio Resource, and double-click BTS, and then right-click the site
record and choose Query Cell Status. It is the normal state when Manual Block
Status is MANUAL UNBLOCK, and Operational Block Status is BTS Unblock.
3. Check the TRX status. Select Status Management > SubNetwork > ME > GSM
Radio Resource, double-click TRX, and then right-click the site record and choose
Query TRX Status. It is the normal state when TRX Status is UNBLOCK.
4. Check the TS status. Select Status Management > SubNetwork > ME > GSM
Radio Resource, and double-click TS. It is the normal state when Manual Block
Status, Connect Block Status, and Operational Status are all Unblock.
10.3 BTS Alarm Query
If alarm “Abis control link broken” appears, it means the Abis link is blocked and further
investigation is required.
11 A Interface Integration
For the data configuration of A interface, refer to the description of parameter
configuration of the V4_Template_TransportNetwork.xls in ZXUR 9000 GSM(V6.50.20)
Quick Data Configuration Guide.
11.1 Preparation
Before the integration on the A interface starts, the following preparation work should be
done:
works properly.
3. The MSC runs normally, and the data configuration on the A interface is completed.
4. The transmission from ZXUR 9000 to MSC is in good condition.
5. The data relevant to the A interface integration is already obtained from MSC.
11.2 Data for Integration (Narrowband Signaling

No.7/3GPP IPA)
In order to complete the integration with MSC, it is necessary to negotiate with the MSC
side over the parameters for integration, so that the configurations on the two sides are
consistent.
For the details of the parameters for integration, please refer to Appendix.
11.3 Integration Data Validity Check

1. Signaling point code
If the signaling point is unreachable during integration, the reason is usually the
improper division of signaling point. On the ZXUR 9000 side, the signaling point
code of the 14 bits is in the decimal format. However, different manufacturers divide
them in different ways. Some separate the six most significant bits from the eight
least significant bits; some separate the seven most significant bits from the seven
least significant bits. During the integration, the signaling point data provided by the
MSC side is usually already divided. For example, on the MSC side, the signaling
points provided by the MSC side are as follows: 18-50.This value does not
represent 1850 in the decimal system. If the 7-7 division is adopted on the MSC
side, the actual signaling point code is 2354 (decimal). If the 6-8 division is adopted
on the MSC side, the actual signaling point code is 4658 (decimal). Therefore, it is
necessary to get to know how the signaling point code is divided on the MSC side
so as to ensure that the code on the two sides is consistent.
Algorithm:
 The decimal 18 is the binary 10010, and 0010010 as a 7-bit binary number.
 The decimal 50 is the binary 110010, and 0110010 as a 7-bit binary number.
Therefore, 18–50 is equal to 0010010 0110010 in the binary system, and this digit
is equal to 2354 in the decimal system. For the calculation of signaling point code in
case of the 6–8 division, it is quite similar.
Every signaling message on the A interface has a signaling point code and it can be
viewed by the traced signaling. The signaling point code is hexadecimal. In the
traced signaling, if the test and maintenance message of the uplink/downlink
signaling network exists, it means that the signaling points of ZXUR 9000 and MSC
are configured correctly.
2. Signaling point type
Here are the requirements for the type of the signaling point: The type of the
signaling point of ZXUR 9000 should be configured as 1 (Signaling End Point SEP),
and the type of the signaling point of MSC should be configured as 3 (Signaling
Transfer End Point STEP).
3. Signaling link code (SLC)
Usually, the code of SLC starts from zero, and the signaling timeslot usually refers
to TS16. However, it should be noted that the default signaling timeslot of the MSC
provided by some manufacturers is not TS16.
4. Network Type
 ITU-T CCSS7 has four types of NI (network identification): 00 IN

(international network, 24-bit), 01 INS (international slave network, 14-bit), 10
NI (national network, 24-bit) and 11 NIS (national slave network, 14-bit).
 The SIO (service information octet) SSF contains the 2-bit NI (network
identification) of 00/01/10/11, respectively representing international network
(international active), international standby network, national network (national
active), and national standby network. The content of SIO SSF is national
master 1000 or national slave 1100.
 For the integration with MSC, the domestic network type is usually national
standby (NIS) (14-bit). But the international network type is usually national
active (NI). If MSC and ZXUR 9000 have different network type configurations,
the following signaling message will pop up repeatedly:
Signaling network testing and maintenance message
Unknown A message (unknown A-interface message)

5. Subsystem status query
Query R_N7SSN STATUS bits and make sure all the STATUS bits are 0.
6. Frame format of E1 interface and transmission impedance of EDAB/ESDAB board:
 Frame format of E1 interface
The default frame format is: double-frame format Currently, EDAB/ESDAB can
support multi-frame CRC check format. Non-framing format will be provided in
future.
 EDAB/ESDAB transmission impedance setting
The default transmission impedance of EDAB/ESDAB is 75 ohm. However,

the 120-ohm transmission cable (twisted pair) is widely used abroad.
Inconsistent impedances may cause circuit connection failure on the A
interface or frequent transient link disconnections.
7. Configuration of the signaling subsystem status
Configure the local office and adjacent office with the signaling subsystem number
0, 1 and 254. The subsystem ID bit usually represents a single subsystem. The
local office ID is usually set as 0 and that of the adjacent office is set according to
the actual data configuration. Other parameters are set by default.
8. Link error correction method
Usually the basic error correction method is adopted.
9. Type of signaling link group
Usually the 64K narrowband signaling link group is adopted.
11.4 TDMA Integration State Check
11.4.1 Checking the Integration Parameters
The following table shows the location of the integration parameters in the quick
configuration template. The corresponding location of the parameters in GUI can be
found in ZXUR 9000 GSM (V6.50.20)Quick Data Configuration Guide.
Table A Interface Integration-5 TDMA Integration Parameters
Location in Quick Configuration

Name of Integration Parameter
Template
Signaling protocol type TransportNetwork-->Adjacent Office(CN)
MSC signaling point code TransportNetwork-->Adjacent Office(CN)
ZXUR 9000 signaling point code TransportNetwork-->Local Signalling Points
MSC signaling point type TransportNetwork-->Adjacent Office(CN)
ZXUR 9000 signaling point type TransportNetwork-->Local Signalling Points
SSF TransportNetwork-->Adjacent Office(CN)
No.7 PCM SN TransportNetwork-->No.7 PCM
SS7 link TS TransportNetwork-->Mtp2Link
SLC TransportNetwork-->Mtp2Link
LECM (Link Error Correction Method) TransportNetwork-->Mtp2Link
LINKTYPE (Signaling Link Group
TransportNetwork-->Mtp2Link
Type)
Frame format of E1 interface Equipment-->Board Config
11.4.2 Observing BSC Board Status
Observe the indicator state on the interface board EDAB. Make sure the board is
running properly.
11.4.3 Observing Alarms in OMCR
Enter the main interface of the client and choose Fault Management to check the real-
time alarms of the corresponding NE.
1. Check whether there are PCM alarms on the interface board of A interface.
2. Check the ZXUR 9000 alarms to see whether unreachable signaling points or SS7
L3 alarms exist.
If they exist, it means signaling at the two ends has problems and a further check is
required.
11.4.4 Observing Dynamic Data
1. Enter Status Management, select Physical Resource > E1 Sunit to check the
state of the E1 used by the A interface. If Sunit state is unblock, it means that its
state is normal.
Figure A Interface Integration-30 Check TDMA Integration State
2. Choose GSM Radio Resource > GATRUNKPCM to query the state of PCM.
3. Choose GSM Radio Resource > GATRUNKS to check the state of each timeslot.
4. Choose Transmission Resource > Mtp2 Link to check the state of the Mtp2 link.
If Link status is in service status, the state is normal.
5. Choose Transmission Resource > Signaling Link to check the state of the MTP3
Link.
6. Choose Transmission Resource > Signaling Linkset to check the state of the
MTP3 Linkset.
7. Choose Transmission Resource > Adjacent No.7 Office to check the state of
Adjacent No.7 Office.
8. Choose GSM Radio Resource > MSC to check the state of MSC. If MANUAL
UNBLOCK and Available are displayed, it means that the integration is successful.
11.5 IPA Integration State Check
Table A Interface Integration-6 IPA Integration Parameters
Location in Quick Configuration

Name of Integration Parameter
Template
TransportNetwork-->Local Signalling
ZXUR 9000 signaling point code
Points
TransportNetwork-->Local Signalling
ZXUR 9000 signaling point type
Points
TransportNetwork-->Static Route
IP address of MSC TransportNetwork-->IP Path(CN)
TransportNetwork-->SCTP Config(CN)
IP address of MGW TransportNetwork-->Static Route
Static Route TransportNetwork-->Static Route
Physical interface IP of the ZXUR 9000 Equipment-->Interface IP
control plane TransportNetwork-->SCTP Config(CN)
Physical interface IP of the ZXUR 9000
Equipment-->Interface IP
user plane
Loopback IP of the ZXUR 9000 control
plane
Loopback IP of the ZXUR 9000 user plane
Equipment-->Service IP
Application type of ASP TransportNetwork-->SCTP Config(CN)
TransportNetwork-->M3uaAS
AS application server type(TAG)
Config(CN)
Whether exist context for AS
Config(CN)
M3UA ROUTEMODE
Config(CN)
SCTP (A interface) local end port number TransportNetwork-->SCTP Config(CN)
SCTP (A interface) peer end port number TransportNetwork-->SCTP Config(CN)
When IP-A interface is adopted, we can check the A interface status by observing the
indicator of EGPB board. If the indicator flashes, it means the physical link is normal. If
not, checks on network cable and route should be performed.
Check the ZXUR 9000 alarms to see whether unreachable signaling points or SS7 L3
alarms exist. If they exist, it means signaling at the two ends has problems and a further
check is required.
Open Status Management.
1. Choose Transmission Resource > SCTP Association to query the SCTP state.
Figure A Interface Integration-31 Check IPA Integration State
2. Choose Transmission Resource > M3UA AS to query the AS state.
3. Open Status Management and choose Transmission Resource > M3UA ASP to
query the ASP state.
4. Choose GSM Radio Resource > MSC to check the state of MSC. If MANUAL
UNBLOCK and Available are displayed, it means that the integration is successful.
11.6 Integration of TDM-IP Hybrid Scenario

This chapter explains the scenario where TDM is used for user plane and IP link is used
for control plane.
Table A Interface Integration-7 Integration Parameters for TDM - IP Hybrid Scenario
Name of Integration Parameter Location in Quick Configuration Template

ZXUR 9000 signaling point code TransportNetwork-->Local Signalling Points
ZXUR 9000 signaling point type TransportNetwork-->Local Signalling Points
Frame format of E1 interface Equipment-->Board Conf
No.7 PCM SN TransportNetwork-->No.7 PCM
Name of Integration Parameter Location in Quick Configuration Template

TransportNetwork-->Static Route
IP address of MSC TransportNetwork-->IP Path(CN)
Physical interface IP of the ZXUR Equipment-->Interface IP
9000 control plane TransportNetwork-->SCTP Config(CN)
Gateway IP to MSC TransportNetwork-->Static Route
Loopback IP of the ZXUR 9000
control plane
Application type of ASP TransportNetwork-->SCTP Config(CN)
AS application server type (TAG) TransportNetwork-->M3uaAS Config(CN)
Whether exist context for AS TransportNetwork-->M3uaAS Config(CN)
M3UA ROUTEMODE TransportNetwork-->M3uaAS Config(CN)
SCTP (A interface) local end port
number
SCTP (A interface) peer end port
number
11.6.2 BSC Board Status & Alarm Observation in OMCR
Refer to the previous two chapters.
1. Check the physical link status of user plane.
Open Status Management.
Choose Physical Resource > E1 Sunit to check the state of the E1 used by the A
interface. If Sunit state is unblock, it means that its state is normal.
Figure A Interface Integration-32 Check TDM - IP Hybrid Integration State
Choose GSM Radio Resource > GATRUNKPCM to query the state of PCM.
Choose GSM Radio Resource > GATRUNKS to check the state of each timeslot.
2. Query Signaling Link Status.
Open Status Management to query the status of AS, ASP, and MSC office.
11.6.4 Checking Signaling Trace
During A interface integration, we can use RCT for signaling trace to locate and remove
the fault accurately.
11.7 Test on A Interface

To perform tests on the A interface, we should perform call tests on the links and CIC
timeslots one by one.
11.8 Check Records of A Interface Integration
Table A Interface Integration-8 A Interface Integration Check Record

Status of BSC
1 □ OK □ NOK
boards
2 OMCR alarms □ OK □ NOK
3 Observing □ OK □ NOK

signaling trace
Observing
4 □ OK □ NOK
Dynamic Data
12 GB Interface Integration
For the data configuration of Gb interface, refer to the description of parameter
configuration of the V4_Template_TransportNetwork.xls in ZXUR 9000
GSM(V6.50.20)Quick Data Configuration Guide.
12.1 Preparation
Before the integration on the Gb interface starts, the following preparation work should
be done:
works properly.
3. The SGSN runs well, and the data configuration on the Gb interface is completed.
4. The transmission from ZXUR 9000 to SGSN is in good condition.
5. The data relevant to the integration on the Gb interface is already obtained from
SGSN.
12.2 Data for Integration

In order to complete the integration with SGSN, it is necessary to negotiate with the
SGSN side over the parameters for integration, so that the configurations on the two
sides are consistent.
For the details of the parameters for integration, please refer to Appendix C and D.
12.3 Explanation of IP Gb
1. Overview
IPGB is a networking mode that uses IP transmission network on the Gb interface

as the intermediate network to connect ZXUR 9000 and SGSN.
When IP transmission is adopted on the Gb interface, both the point-to-point

dedicated network and public IP transmission network can be adopted.
 For point-to-point dedicated network, the IP port must adopt the static
configuration.
 For public IP transmission network, both static configuration and dynamic

configuration can be adopted for the IP port.
The networking diagram of IPGB is shown in Figure GB Interface Integration-33.
Figure GB Interface Integration-33 Structure of IPGb Networking
2. Hardware requirement
IP transmission is used on the Gb interface; NS layer is borne on UDP/IP; the signaling

and data on the Gb interface are transmitted through the route addressing based on IP.
Besides the RUP board used for service processing, the IP interface board (EGPB) of
Gb interface needs to be added in ZXUR 9000.
3. Configuration description
 Configuration mode: Both static configuration and dynamic configuration can

be used. Static configuration is applied for the point-to-point dedicated
network connection, which requires manual negotiation between ZXUR 9000
and SGSN to make them reach an agreement, i.e. to configure the end points
of NSVC in combination.
 Pre-configuration of SGSN IP address: SGSN IP address is required to be

configured only when dynamic configuration is adopted.
 Pre-configuration of SGSN UDP address: SGSN UDP is required to be

configured only when dynamic configuration is adopted.
 UDP port No.: It has to be consistent with that at the SGSN side.
12.4 Checking E1 Gb Integration
Observe the state of the indicator on the interface board ESDTI and check whether the
board is running well.
Check whether the following alarms are included in ZXUR 9000 alarms: NSE block,
SGSN block. If they exist, it means there is a problem with the integration and a further
check is required.
12.5 Checking IP Gb Integration
When IP-Gb interface is adopted, we can check the Gb interface status by observing the
indicator of EGPB board. If the indicator flashes, it means the physical link is normal. If
not, checks on network cable and route should be performed.
Check whether the following alarms are included in ZXUR 9000 alarms: NSE block,
SGSN block. If they exist, it means there is a problem with the integration and a further
check is required.
12.5.3 Use of Signaling Trace
Use the RCT signaling to trace the signaling on the Gb interface, in order to check
whether the integration is successful or to quickly locate the fault.
12.5.4 Observing in Dynamic Data Management
Enter View > Status Management, and select GSM Radio Resource > SGSN to query
SGSN’s status. If its status if Available and unblock, it means the integration is
successful.
Figure GB Interface Integration-34 Check the IPGB Integration State
12.6 Test on Gb Interface

For detailed information, refer to the ZXUR 9000 GSM (V6.50.20)Test Guide and the
ZXUR 9000 GSM (V6.50.20) Commissioning Test Record.
12.7 Check Records of Gb Interface Integration
Table GB Interface Integration-9 Check Records of Gb Interface Integration

Status of
1 ZXUR9000 □ OK □ NOK
GSM boards
2 OMCR alarms □ OK □ NOK
Observing
3 □ OK □ NOK
signaling trace
Observing
4 □ OK □ NOK
Dynamic Data
Observing
4 □ OK □ NOK
Dynamic Data
13 Commissioning test
After ZXUR 9000 is commissioned, basic tests on OMMR/OMMB functions and
performance should be performed, including test on ZXUR 9000 hardware, test on
OMMR functions, test on software version, test on service calls, test on handovers, and
test on the newly-added functions. For the details of the above tests, refer to ZXUR 9000
GSM (V6.50.20) Base Station Controller Test Guide.
AppA TDMA Integration Parameters

Name of Integration
Description Remarks
Parameter
Signaling protocol type CHINA / ITU / ANSI
MSC signaling point Whether it’s 14bit or 24bit signaling
code code (in decimal) should be noted.
ZXUR 9000 signaling Whether it’s 14bit or 24bit signaling
point code code (in decimal) should be noted.
MSC signaling point
One of SEP, STP, SETP
type
ZXUR 9000 signaling
point type
SSF Sub-service field (SSF)
A interface PCM No.
No.7 PCM SN
Frame format of E1
interface
SLC
CIC
SS7 link TS
LECM (Link Error Usually the basic error correction
Correction Method) method is adopted.
LINKTYPE (Signaling Usually the 64K narrowband
Link Group Type) signaling link group is adopted.
AppB IP-A Integration Parameters

Name of Integration
Description Remarks
Parameter
Signaling protocol type CHINA / ITU / ANSI
MSC signaling point Whether it’s 14bit or 24bit signaling
code code (in decimal) should be noted.
ZXUR 9000 signaling Whether it’s 14bit or 24bit signaling
point code code (in decimal) should be noted.
MSC signaling point
type
ZXUR 9000 signaling
point type
SSF Sub-service field (SSF)
IP address of MSC
IP address of MGW
Gateway to MSC
Gateway to MGW
Physical interface IP of
the ZXUR 9000 control
plane
Physical interface IP of
the ZXUR 9000 user
plane
Loopback IP of the
ZXUR 9000 control
plane
Loopback IP of the
ZXUR 9000 user plane
Protocol type of ASP Usually M3UA is used.
Used for negotiating the application
Application type of ASP attributes of the application server
process (Client/Server).
AS application server
Usually IPSP_CLIENT is selected.
type
Whether exist context
Type YES/NO.
for AS
Sequence of M3UA routes; usually
M3UA ROUTEMODE
the mixed sequence is selected.
SCTP local end port
number
SCTP peer end port
number
AppC E1-Gb Integration Parameters

Name of Integration
Description Remarks
Parameter
Used for identifying NSE; it should
Network Service Entity
be consistent with that at the
Identifier (NSEI)
SGSN side.
Network Service
Virtual Connection
Identifier (NSVCI)
Bearer Chanel (BRCH)
timeslot No.
Digital Link Connection
Identifier (DLCI)
Routing Area Code
(RAC)
AppD IP-Gb Integration Parameters

Name of Integration
Description Remarks
Parameter
IPGB loopback address IPGB loopback address
Configuration of IPGB Configuration of IPGB interface
interface board address board address on EGPB
Static Route
In the case of IP bearing mode,
use static configuration. If
dynamic configuration is
Identifier (NSEI)
selected, the preset SGSN
address needs to be configured.
Configuration of local end
point
Configuration of remote
end point
Data weight
Signaling weight
NSEI is used in the case of
Preset SGSN address
dynamic configuration.
Used for identifying NSE; it
should be consistent with that at
Identifier (NSEI)
the SGSN side.
Routing Area Code
(RAC)
AppE Checking the Factory Version of

Equipment
Because the commissioning steps of equipment vary with the factory version, it is
necessary to ascertain the factory version before commissioning.
According to the factory versions of equipment, the equipment versions can be divided
into three types currently, i.e., UR11, UR12, and UR13.
After BSC is powered on and both EGBS and EGFS are started up, telnet to ECMM and
check the equipment version. (Because a BSC can have a maximum of three shelves,
check the equipment version in each of the three shelves).
-bash-3.2$ telnet 129.7.1.233 24
Note: The ECMM IP is “129.7.1.233” in Shelf 3, “129.5.1.233” in Shelf 1, and

“129.6.1.233” in Shelf 2. The port No. is “24.”
The username and the password are both “root.”
If the prompt is “CLI>", the equipment version is of 6.50.10 series. It is not necessary to
execute the following commands.
If the prompt is “CLI#”, type in “syscfg” and then “show shelf_board_info 19” to check the
board property, e.g.,
CLI#syscfg
CLI(syscfg)#show shelf_board_info 19
Board slot: 19
Board type: INDEPEND_BOARD
Board net number: 200
Boot type: FAST_BOOT
Power on type: INDIRECT_POWER
Power off type: ENABLE_BY_CMM
According to the “Board type: INDEPEND_BOARD” prompted, the equipment version is

of 6.50.20 series. Perform commissioning according to this guide.
If there is more than one shelf, check the configuration in each of the shelves.
AppF Hardware Version Check

It is necessary to check whether the firmware of EGBS and EGFS meets the following
requirements. If not, upgrade the firmware to the following versions before continuing
other upgrade operations.
Requirement for the BOOT version of the switch boards:
The BOOT version of EGBS must be 2.7.59 or a later version.
The BOOT version of EGFS must be 2.5.72 or a later version.
Requirement for the IPMC version of the switch boards:
IPMC version: 01.01.40.59 and later versions
Requirements for the FRU version of the switch boards:
EGBS Batch 090100: 01.01.0004 and later versions
EGBS Batch 090201: 01.01.0009 and later versions
EGFS Batch 090100: 01.01.0003 and later versions
EGFS Batch 090302: 01.01.0009 and later versions
Requirements for the version of Work EPLD:
EGBS Batch 090100: 00.00.00.103 and later versions
EGBS Batch 090201: 00.00.00.108 and later versions
EGFS Batch 090100: 00.00.00.103 and later versions
Requirement for the version of FPGA:

Requirement for the version of ECMM: 01.01.40.05P18,
Query ECMM software version with the following method:
Telnet to the ECMM in the shelf from OMM. If there is more than one shelf, query the
version of each shelf respectively, e.g., to query the version information of the ECMM at
Slot 29, Shelf 3, type in the following commands:
[root@OMM-23989B5A ~]# telnet 129.7.1.233 24
Trying 129.7.1.233...
Connected to 129.7.1.233 (129.7.1.233).
Escape character is '^]'.
Welcome!
********************************************************
******
Welcome to CLI config shell of ZTE Corporation
********************************************************
******
Username:root
Password:****
CLI>en
CLI#cmm
CLI(CMM)#cmmget -l cmm -d versionsall
CMMBootSoftVersion:02.09.45
CmmFPGAVersion:03 /
CmmBOMID:00
CmmPCBVer:00
CmmWorkEPLDVersion:03
CmmSoftVersion:01.01.40.05.06 //The CPU version of ECMM
Query EGBS/EGFS batch and FRU version with the following method:
Telnet to the ECMMs in the shelves of EGBS and EGFS respectively from OMM. If there
is more than one shelf, query the version for each shelf separately. Suppose the
information of EGBS and EGFS in Shelf 3 needs to be queried, type in the following
commands, in which the red part shows the Slot No. of EGBS or EGFS.
Trying 129.7.1.233...
Connected to 129.7.1.233 (129.7.1.233).
Welcome!
********************************************************
******
Welcome to CLI config shell of ZTE Corporation
********************************************************
******
Username:root
Password:****
CLI>en
CLI#cmm
CLI(CMM)#cmmget -l blade19 -t "0:FRU" -d all //19 is the Slot No.
boarddescription:EGBS
boardmanufacturer:ZTE
boardpartnumber:090201 //Batch number
boardserialnumber:262629900007
boardfrufileid:01.01.0009 //fru version
boardmanufacturedatetime:2012-Mar-23 09:14
productdescription:
productmanufacturer:
productmodel:
productpartnumber:
productserialnumber:
productrevision:
productfrufileid:
Query BOOT version with the following method.
Telnet to EGBS/EGFS through the control-plane IP and execute the query command.
For example, to query the version of the EGBS at Slot 19, Shelf 19, type in the following
commands:
(none) login: zte
Password: ***
Welcome to ZTE Linux
~ $
~ $ ushell
====================Notice===================
ushell tool is now replaced by telnet 10000.
=============================================
Entering character mode
-----------------------------------------
Welcome to tulip ushell
-----------------------------------------
login: zte
password: ***
Successfully login into ushell!
[admin]#
[admin]# sh 1
Now switch to SODAMGR shell ...
[SODAMGR]#
[SODAMGR]# TestMenu()
[SODAMGR]
[SODAMGR]
*==========================================================*
[SODAMGR] * ZTE 3G Unified Platform BSP Board Test

Center *
[SODAMGR] * SODA PKG , 2002.10.10,

Nanjing *
[SODAMGR]
*==========================================================*
[SODAMGR] [ 1]: BoardCtrl Pkg...
[SODAMGR] [ 2]: ETHSWITCH Pkg...
[SODAMGR] [ 3]: LSSP Pkg...
[SODAMGR] [ 4]: MAC Pkg...

[SODAMGR] [ 5]: Mts Pkg...
[SODAMGR] [ A]: Test All
[SODAMGR] [ Q]: Quit this Menu
[SODAMGR]
============================================================
Select the following items one by one:
Select [ 1]: BoardCtrl Pkg...
Select [ 1]: Test Soda BoardCtrl FirmLoad...
Select [ 8]: Get Version Info
The query result is shown below.
BoardCtrl ResourceCtl Test->8
[BSP]SPANSION FLASH
[BSP]chi id1
This device is Spansion flash!
[BSP]: tPara.dwBrdId : 0x23a.
[BSP]: tPara.dwPcbVer : 0x0.
[BSP]: tPara.dwBomVer : 0x1.
[BSP]: tPara.dwBootVer : 0x2000007. Current BOOT version
[BSP]: tPara.dwBspVer : 0x10020.
[BSP]: tPara.dwCpuCardPcbVer : 0x1.
[BSP]: tPara.dwCpuCardBomVer : 0x2.
[BSP]: tPara.dwCpuCardEpldVer : 0x3.
[BSP]: tPara.dwBackBoardTypeId: 0x6.
[BSP]: tPara.dwBackPlaneVersion: 0x807.
[BSP]: tPara.dwSlaveBootVer : 0x2000002.

[BSP]: tPara.dwCpuCpldVer : 0x3.
Query the FPGA version or the working EPLD version.
Telnet to EGBS/EGFS through the control-plane IP and execute the query command.
For example, to query the version of the EGBS at Slot 19, Shelf 19, type in the following
commands:
(none) login: zte
Password: ***
Welcome to ZTE Linux
~ $
~ $ ushell
====================Notice===================
ushell tool is now replaced by telnet 10000.
=============================================
Entering character mode
-----------------------------------------
Welcome to tulip ushell
-----------------------------------------
login: zte
password: ***
Successfully login into ushell!
[admin]#
[admin]# sh 1
Now switch to SODAMGR shell ...
[SODAMGR]#
[SODAMGR]# TestMenu()
[SODAMGR]
[SODAMGR]
*==========================================================*
[SODAMGR] * ZTE 3G Unified Platform BSP Board Test

Center *
[SODAMGR] * SODA PKG , 2002.10.10,

Nanjing *
[SODAMGR]
*==========================================================*
[SODAMGR] [ 1]: BoardCtrl Pkg...
[SODAMGR] [ 2]: ETHSWITCH Pkg...
[SODAMGR] [ 3]: LSSP Pkg...
[SODAMGR] [ 4]: MAC Pkg...
[SODAMGR] [ 5]: Mts Pkg...
[SODAMGR] [ A]: Test All
[SODAMGR] [ Q]: Quit this Menu
[SODAMGR]
============================================================
Select the following items one by one:
Select [ 1]: BoardCtrl Pkg...
Select [ 1]: Test Soda BoardCtrl FirmLoad...

Select[ 2]: Get FirmLoad Info, select the firmware type to be queried and location
according to the prompt, e.g., query the FPGA version of the mother board:
BoardCtrl FirmLoad Test->2
Firm Load Info Query test...
Please select the firm type from:1~4
1: BSP_BRDCTRL_FIRM_TYPE_BOOT
2: BSP_BRDCTRL_FIRM_TYPE_FPGA
3: BSP_BRDCTRL_FIRM_TYPE_EPLD
4: BSP_BRDCTRL_FIRM_TYPE_ASIC
select item ( Range: 1 ~ 4)->2 Query FPGA
Please select the location from:0~13
0: BSP_PANEL_BOARD
1: BSP_PANELBOARD_CARD_1
9: BSP_REAR_BOARD
10: BSP_REARBOARD_CARD_1
select item ( Range: 0 ~ 13)->0 Query the mother board
[BSP]: Firm index: 0x0
[BSP]: Firm status: 0xf
[BSP]: Firm version: 0x1 //EPLD version of the mother board
[BSP]: Firm status: 0x0
[BSP]: Firm version: 0xffffffff

There are eight FPGA links in total. The first link exists and supports online upload. The
meanings of the bits of the firmware status are listed below:
bit0:
“1” means this type of firmware exists in this upload location.
“0” means this type of firmware does not exist in this upload location.
bit1:
“1” means online upload is supported.
“0” means online upload is not supported.
bit2:
“1” means the firmware has been uploaded.
“0” means the firmware has not been uploaded.
bit3:
“1” means the firmware verification succeeds.
“0” means the firmware verification fails.

AppG Common Abbreviations

Abbreviation Full Name
A
AC Address Control
AGCH Access Grant Channel
AUC Authentication Center
B
BCH Broadcast Channel
BCCH Broadcast Control Channel
BSIC Base Station Identity Code
BSS Base Station Subsystem
BSSGP BSS GPRS Protocol
BTS Base Transceiver Station
BVC BSSGP Virtual Connection
BVCI BSSGP Virtual Connection Identifier
C
CBCH Cell Broadcast Channel
CCCH Common Control Channel
Conference of European Posts and
CEPT
Telecommunications
CGF Charging Gateway Function
C/I Carrier-To-Interference Ratio
CM Connection Management
CS-i Coding Scheme (GPRS)
E
ECSD Enhanced Circuit Switched Data
EDGE Enhanced Data Rates For GSM Evolution
EGPRS Enhanced GPRS
EIR Equipment Identity Register
European Telecommunications Standards
ETSI
Institute
F
FACCH Fast Associated Control Channel
FCCH Frequency Correction Channel
FDMA Frequency Division Multiple Access
FS Fianl Slot
G
GGSN Gateway GPRS Support Node
GMSC Gateway MSC

GMSK Gaussian Minimum Shift Keying
GPRS General Packet Radio Service
GSM Global System for Mobile Communication
GTP GPRS Tunnel Protocol
H
HLR HOME Location Register
HSCSD High-Speed Circuit Switched Data
I
International Mobile SuZXUR 9000riber
IMSI
Identity
IP Internet Protocol
IR Incremental Redundancy
ISDN Integrated Services Digital Network
ISUP
IWF Interworking Function
L
LA Link Adaptation
LLC Logic Link Control
LQC Link Quality Control
M
MAC Medium Access Control
MAP Mobile Application Protocol
MCS Modulation and Coding Scheme (EDGE)
MGW Media GateWay
MM Mobile Management
MS Mobile Station
MSC Mobile Switching Center
MTP Message Transfer Part
N
NMS Network Management System
NSEI Network Service Entity Identifier
NSS Network Switching Subsystem
O
OMS Operation and Maintenance Subsystem
OSI Open System Interconnect
P
PACCH Packet Associated Control CHannel
PAGCH Packet Access Grant CHannel
PBCCH Packet Broadcast Control CHannel
PCCCH Packet Common Control CHannel

PCH Paging Channel
PCU Packet Control Units
PDN Public Data Networks
PDP Packet Data Protocol
PDTCH Packet Data Traffic Channel
PLMN Public Land Mobile Network
PNCH Packet Notification Channel
PPCH Packet Paging Channel
PRACH Packet Random Access Channel
PSTN Public Switched Telephone Network
PTCCH Packet Timing advance Control Channel
Q
QoS Quality of Service
R
RACH Random Access Channel
RAID Redundant Array of Independent Disk
RAN Radio Access Network
RLC Radio Link Control
Regular Pulse Excitation-Long Term
RPE-LTP
Prediction
RRM Radio Resources Management
S
SACCH Slow Associated Control Channel
SCCP Signaling Connection Control Part
SDCCH Standalone Dedicated Control Channel
SGSN Serving GPRS Support Node
SIM SuZXUR 9000riber Identity Module
SMC Short Message Center
Subnetwork Dependent Convergence
SNDCP
Protocol
SNMP Simple Network Management Protocol
STP Signaling Transfer Point
SCH Synchronization Channel
T
TACS Total Access Communication System
TAI Timing Advance Index
TBF Temporary Block Flow
TCH Traffic Channel
TDMA Time Division Multiple Access
TLLI Temporary Logical Link Identity

Temporary Mobile SuZXUR 9000riber
TMSI
Identity
TRAU Transcoding and Rate Adaptation Unit
U
USF Uplink State Flag
V
VLR Visitor Location Register
VPN Virtual Private Network
8-PSK 8 Phase Shift Keying

ZXUR 9000 GSM (V6.50.20) BSC Commissioning Guide - R1.1

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZXUR 9000 GSM (V6.50.20) BSC Commissioning Guide - R1.1

Загружено:

Авторское право:

Доступные форматы

ZXUR 9000 GSM (V6.50.

Address: Address: NO. 55

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. I

Product Version Document Version Serial Number Reason for Revision

Date Document Version Prepared by Reviewed by Approved by

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. II

Intended audience: GSM after-sales engineers

About This Document

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. IV

4 Equipment Check before Power-on................................................................6

6 Equipment Check with Power-on.................................................................21

7 OMM Installation & Commissioning.............................................................23

9 Version Loading & State Check....................................................................28

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. V

9.2 Checking the Factory Version..........................................................................31

10 SDR – Abis Interface Integration..................................................................54

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. VI

11.7 Test on A Interface...........................................................................................67

AppA TDMA Integration Parameters.......................................................................73

AppB IP-A Integration Parameters..........................................................................74

AppC E1-Gb Integration Parameters......................................................................75

AppD IP-Gb Integration Parameters.......................................................................76

AppE Checking the Factory Version of Equipment...............................................77

AppF Hardware Version Check...............................................................................78

AppG Common Abbreviations....................................................................................89

Figure 2-1 Commissioning Flow.............................................................................................3

Figure 11-2 Check IPA Integration State...............................................................................65

Table 2-1 Explanation of the Flow Chart.................................................................................3

ZTE Confidential Proprietary © 2018 ZTE CORPORATION. All rights reserved. IX

The commands starting with “$”should be executed under user oracle.

1.3 Application Scope

Figure Commissioning Flow-1 Commissioning Flow

Explanation of each step is detailed in Table 2-1.

Table Commissioning Flow-1 Explanation of the Flow Chart

Steps Operation Description

3.1 Project Information

3.2 Preparation of Tools & Meters

1. Tools: cross screw-driver, flathead screw-driver, diagonal pliers, sharp-nosed pliers,

3.3 Preparation of Software

3.4 Preparation of Documents

ZXUR 9000 GSM (6.50.20) BSC Hardware Description

ZXUR 9000 GSM (V6.50.20) BSC Hardware Installation Guide

ZXUR 9000 GSM (V6.50.20) Routine Maintenance

3.5 Confirmation of System Networking Plan

 Based on the system networking map, equipment commissioning engineers should

 Communicate with the customer to acquire the A interface/GB interface integration

4 Equipment Check before Power-on

4.1 Power Supply Voltage Check

4.2 Hardware Check

4.2.1 Cabinet Check

2. Check the completeness of cabinet components and soundness of cabinet paint

3. Check the completeness of labels on the cabinet.

4. Check whether the bolts are tightly fastened or not.

5. Check whether the cabinet installation is reinforced with earthquake-proof

3. All kinds of labels on the cabinet shall be complete and clear.

5. Cabinet installation must be reinforced with earthquake-proof measures; fix the

4.2.2 ZXUR 9000 GSM Hardware Installation & Cable Connection

4.2.2.1 Shelf & Board Installation

4.2.2.2 CDM DIP & Check

Figure Equipment Check before Power-on-2 Shelf Data Module CDM

Table Equipment Check before Power-on-2 Definitions of Jumpers on CDM Module

The seventh jumper cap is fixed to be unplugged (OFF).

Figure Equipment Check before Power-on-3 DIP of CDM in Shelf3