Professional Documents
Culture Documents
Version 8.0.2.004
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
Revision History
Preface............................................................... i
Commissioning Workflow ..................................1
CDMA BSS Commissioning Workflow ................................. 1
BSC Commissioning Workflow .......................................... 3
BTS Commissioning Workflow........................................... 4
Commissioning Preparations .............................5
Preparation Flow ............................................................ 5
Commissioning Environment Check ................................... 7
Data Collection............................................................... 7
Precautions.................................................................... 8
BSS Power-on ...................................................9
BSC Cabinet Power-on .................................................... 9
Checking BSC Before Power-on .................................... 9
BSC Power-on Check Requirements..............................10
Powering on BSC Cabinet............................................12
OMC Server Cabinet Power-on.........................................12
Checking OMC Server before Power-on .........................12
OMC Server Power-on Check Requirements ...................13
Powering on OMC Server Cabinet.................................13
Data Configuration .......................................... 15
Data Configuration.........................................................15
BSSB Commissioning....................................... 17
OMP Board Commissioning .............................................17
Checking Physical Link between OMP and OMC
Server..............................................................17
Setting OMP IP Address ..............................................18
OMP Version Loading..................................................20
Loading Version from OMC .................................20
Loading Version from NE ....................................26
Synchronizing/Saving OMP Data..........................28
Other BSC Board Commissioning ....................................30
Adding Version ..........................................................30
Activating Version ......................................................30
Validating Version ......................................................34
Querying Version ...........................................................35
Checking Board Running Status .......................................37
Basic Commissioning......................................................38
Performing Module Commissioning ...............................38
Performing Media Stream Communication Test ..............39
Performing Alarm
ZXC10 BSSB Commissioning Manual
Commissioning
Workflow
Table of Contents
CDMA BSS Commissioning Workflow ..................................... 1
BSC Commissioning Workflow .............................................. 3
BTS Commissioning Workflow............................................... 4
BSC Commissioning
Workflow
Figure 2 shows the BSC commissioning workflow.
BTS Commissioning
Workflow
Note: For details, refer to related commissioning manuals for
specific BTS products.
Commissioning
Preparations
Table of Contents
Preparation Flow ................................................................ 5
Commissioning Environment Check....................................... 7
Data Collection................................................................... 7
Precautions........................................................................ 8
Preparation Flow
Figure 3 shows the commissioning preparation stages.
Commissioning Environment
Check
To guarantee smooth commissioning and satisfy requirements, it
is required to check the equipment installation environment.
� Check the following items: cable connections, grounding and
power supply.
� After completing, fill the Installation Acceptance Test Report.
� Note that the system commissioning cannot proceed unless the
installation is accepted.
Data Collection
Collect the necessary data before commissioning:
Precautions
Following are the precautions for successful commissioning:
ESD (Electronic Follow ESD protection requirements strictly. Antistatic jumper is
Static Discharge) required for admission to equipment room. Antistatic wrist strap
Protection is required for board handling.
Board Handling Handle the boards with care. Boards that are not used in the com-
missioning process should be packed in antistatic bags and stored
in good order.
Switches and Make sure the switches and jumpers on the circuit boards of the
Jumpers equipment are set according to the requirements, especially DIP
switches.
Transmission Check the circuits at A interface and Abis interface and make sure
Circuits the transmission is through.
Power on Before power on, make sure:
� The power cable is not short-circuited.
� The equipment is properly grounded.
� The voltage of primary power supply is normal.
� The equipment power switch is set to OFF position.
� The fuses are of proper specifications and correctly installed.
During powering ON/OFF the equipment, strictly follow related re-
quirements and procedures.
BSS Power-on
Table of Contents
BSC Cabinet Power-on ........................................................ 9
OMC Server Cabinet Power-on.............................................12
Caution:
There are two input pairs to be measured.
Terminal 48 V 48 VGND
Note:
When a DIP switch bit is set to ON, the corresponding binary
digit is 0; when it is set OFF, the corresponding binary digit is
1.
Data Configuration
Table of Contents
Data Configuration.............................................................15
Data Configuration
ZXC10 BSSB data configuration depends on the technical require-
ments specified in the contract, project survey report and network
planning. At the MSC side, cell information, location area code
(LAC), A interface related SS7 link, trunk circuit, and signaling
points needs to be modified in the MSC accordingly and promptly.
The configuration varies with board configuration, services re-
quired and system capacity. Remove some boards if not needed
according to the required services.
Six typical BSC data configurations are given below to suit different
office scales. It can be used as a reference to configure BSC data
according to board configuration status. For more details, refer to
the corresponding Data Configuration Manual.
1. Typical 1X system configuration for single-shelf office, to sup-
port 1X service alone.
2. Typical 1xEV-DO system configuration for single-shelf office, to
support 1xEV-DO service alone.
3. Typical BCTC+BUSN configuration for 2-shelf office, to support
1X Data, 1xEV-DO and PTT service (unnecessary boards can
be deleted).
4. Typical BUSN+BUSN interconnection for 2-shelf office, to sup-
port 1X Data, 1xEV-DO and PTT service (unnecessary boards
can be deleted).
5. Typical configuration for 3-shelf office, to support 1X, 1xEV-DO
and PTT services (unnecessary boards can be deleted).
6. Typical configuration for multi-shelf office with a BPSN, to sup-
port 1X, 1xEV-DO and PTT services (unnecessary boards can
be deleted).
BSSB Commissioning
Table of Contents
OMP Board Commissioning .................................................17
Other BSC Board Commissioning ........................................30
Querying Version ...............................................................35
Checking Board Running Status ...........................................37
Basic Commissioning .........................................................38
Steps 1. Copy OMP version files such as .bin file and .fga file to
\ums\ums-svr of the NetNumen™ M3 (ZXC10 BSSB) server.
2. From the NetNumen™ M3 (ZXC10 BSSB) window, select Views
> System Tools > Version Management, as shown in Figure
13.
4. Click √ on the toolbar and select the directory where the OMP
version file is located, as shown in Figure 15.
5. Select the directory where the OMP version file lies and click
OK.
6. Right-click the version file to be added and select Add Version
from the shortcut menu.
Caution:
For the OMP with 85 series chip, set CPU version only. The OMP
information file creation window is as shown in Figure 23.
4. Select OMP from the navigation tree and Save active board
data from the right pane and click Start on the toolbar and
click OK in the pop-up dialog box to save the active board
data, as shown in Figure 26.
Activating Version
Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > System
Tools > Version Management to display the Version Man-
agement window.
2. Select Version Management > Activate Version to display
the Activate Version window, as shown in Figure 27.
8. Select other boards to activate until all the boards are acti-
vated.
END OF STEPS
Validating Version
Prerequisites � The OMM client has logged on to the OMM server.
� The BSC and the OMM server are connected normally.
Context Reset a board to load new version from OMP to the board.
Steps 1. Select Views > Fault Management > Alarm Management
to display the Alarm Management window.
2. Select ZXC10 BSSB > BSSB > BSCB > Rack to display the
rack diagram.
3. Right-click the board to be reset and select Reset Board Nor-
mally, as shown in Figure 32.
Querying Version
Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > System
Tools > Version Management to display the Version Man-
agement window.
2. Select Version Management > Query Version to display the
Query Version window, as shown in Figure 33.
4. Select the boards to be queried and click OK. The query result
is displayed in the Running Version Info tab, as shown in
Figure 35.
5. Check the running version of every board and make sure they
are correct.
END OF STEPS
Basic Commissioning
Performing Module Commissioning
Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > Fault
Management > Diagnosis Management to display the Di-
agnosis Management window.
2. Open a rack diagram and select a board. To perform commis-
sioning test on all the boards, right-click a board and select
Select All, as shown in Figure 36.
6. Select CPUs and click Start Test. The system will start testing
the media stream link from BUSN to BPSN. The test result is
normal if the packets sent by UIMU and the packets received
by GLIQV are the same.
7. Test other boards in BUSN to make sure the media stream
communication is normal. If loss of packets occurs, check the
fiber connection between the UIMU and GLI.
END OF STEPS
Switchover Test
5. Open the front door of the BSCB cabinet and observe the
ACT1 indicator of the active OMP board. It should be on
before the switchover and be off after the switchover.
6. Switch over the board repeatedly to check whether the
switchover is normal and make records.
2. Switch over OMP board due to failure
1. Right-click the active OMP board (select the CPU1 of
OMP/RPU) and select Switch Board Normally.
2. Observe the two OMP boards. If the switchover succeeds,
the active board should be shadowed after the switchover,
which means it becomes the standby board.
3. Open the front door of the BSCB cabinet and observe the
ACT indicator of the active OMP board. It should be on
before the switchover and be off after the switchover.
4. Switch over the board repeatedly to check whether the
switchover is normal and make records.
3. Switch over OMP board by plugging/unplugging it.
1. In the case that the active/standby OMP boards work nor-
mally, unplug the active board. The standby board should
become an active board and the communication between
the NE and OMC should be normal.
2. Unplug and plug the active OMP board repeatedly to check
whether the switchover is normal and make records.
END OF STEPS
3. Open the front door of the BSCB cabinet and observe the
ACT indicator of the active OMP board. It should be on
before the switchover and be off after the switchover.
4. Switch over the board repeatedly to check whether the
switchover is normal and make records.
3. Switch over OMP board by plugging/unplugging it.
1. In the case that the active/standby OMP boards work nor-
mally, unplug the active board. The standby board should
become an active board and the communication between
the NE and OMC should be normal.
2. Unplug and plug the active OMP board repeatedly to check
whether the switchover is normal and make records.
END OF STEPS
Interconnection
Commissioning
Table of Contents
Overview..........................................................................45
BSC-MSC Interconnection (A Interface) ................................45
BSC-MSCe Interconnection (Ap Interface).............................46
BSC-PDSN Interconnection .................................................47
Interconnection between BSC and AN-AAA............................48
BSC-PDS Interconnection ...................................................48
Overview
The BSC commissioning should be followed by a joint (connecting
BSC to MSC, PDSN, AN-AAA and PDS) system commissioning to
make sure the system is able to deliver basic services and func-
tions.
The BSC is connected to MSC/MSCe through:
� A interface: using traditional PCM and the board that con-
nects to MSC is DTB (E1/T1) or SDTB (E1/T1 Over SDH/SONET)
� Ap interface: using SIPI (IP) board that connects to MGW of
MSCe.
BSC connects to PDSN, AN-AAA, and PDS via the IP transmission.
BSC-MSC Interconnection
(A Interface)
Prerequisites 1. Make sure that all BSC boards work normally.
2. Configure the connection related data in NetNumen™ M3
(ZXC10 BSSB) including PCM data, signaling link data and SS7
data.
3. Connect the BSC to MSC using E1/T1 cable (DTB board) or
optical fiber (SDTB board).
Steps Perform the following steps for commissioning:
1. Check for the E1/T1 signaling link alarm on DTB (SDTB). If yes,
check the physical connection from DTB (SDTB) of BSC to MSC.
2. In the NetNumen M3 (ZXC10 BSSB), select Views > Sys-
tem Tools > Dynamic Data Management to display the Dy-
namic Data Management window.
3. Select Dynamic Data Management > Resource Manage-
ment. Expand the configuration tree.
4. Check the CIC of each PCM and NE E1/T1 number that corre-
sponds to this PCM. Also compare the E1/T1 CIC at the MSC
side with the BSC side.
5. Check whether there is Signaling Link Unavailable alarm
on OMP. Then compare the data between BSC and MSC and
it should be consistent. If using DTB board, then check the
E1/T1 cable between BSC and MSC against that is configured
in NetNumen™ M3 (ZXC10 BSSB).
6. Block other normal signaling links and block/unblock A inter-
face circuit in the resource observation of dynamic data man-
agement system.
BSC-MSCe Interconnection
(Ap Interface)
Prerequisites 1. Make sure that all BSC boards work normally.
2. Configure the connection related data in NetNumen™ M3
(ZXC10 BSSB) including IP address of IPI, SIPI and APCMP as
well as signaling data.
3. The network cable connects IPI and SIPI of BSC to the Ethernet
switch, MGW and Ethernet normally.
Steps Perform the following steps for commissioning:
1. After data configuration, synchronize the data to the NE and
save data in OMP/RPU. Then Reset RPU, APCMP, SIPI and IPI.
2. Check for the Signaling Link Unavailable alarm on OMP and if
there is no such alarm, it indicates that BSC is communicating
with MSCe normally.
3. If there is signaling link unavailable alarm on OMP, then check
the physical link between SIPI of BSC and MSCe, checking in-
cludes, status of LINK1 of SIPI, network port indicator of MSCe,
and the port indicator of Ethernet switch that corresponds to
SIPI of BSC and MSCe. If any indicator is abnormal, check the
network cable, SIPI of BSC, network port of MSCe and the Eth-
ernet switch port.
4. If the physical link is normal, connect the Ethernet switch to
PC and set the IP in the same network segment of SIPI of BSC
and MSCe. Perform the pinging of both SIPI of BSC and MSCe
address. If the ping operation is not through, check hardware,
IP address configuration and the port configuration of Ethernet
switch.
Caution:
After configuring IP addresses of BSC IPI, BSC SIPI, MSC IPI
and MSC SIPI, synchronize the data and reset these boards to
validate the new configuration.
Caution:
both VE unit No. and ground circuit No. are void and are not
shown in Voice Observation because VE is at the MGW side.
BSC-PDSN Interconnection
Prerequisites 1. Make sure that all BSC boards work normally.
2. Configure connection related data in NetNumen™ M3 (ZXC10
BSSB) including PDSN, PCF mode, IP interface address, A10 in-
terface parameter, PCF-PDSN connection, SPI and static route.
3. The network cable connects IPCF of BSC with the Ethernet
switch and PDSN with the Ethernet normally.
Steps Perform the following steps for commissioning:
1. After data configuration, synchronize the data to the NE and
save data in OMP/RPU. Then Reset RPU, APCMP, SIPI and IPI.
2. Check for the PDSN not connectable alarm on SPCF. If there
is no alarm, it indicates SPCF is communicating with PDSN nor-
mally.
3. If there is PDSN not connectable alarm on SPCF, then check
the physical link between SPCF and PDSN, checking includes:
status of LINK1 of IPCF, network port indicator of PDSN, and the
port indicator of Ethernet switch that corresponds to IPCF and
PDSN. If any indicator is abnormal, check the network cable,
network port of IPCF and PDSN, and Ethernet switch port.
4. If the physical link is good, connect the Ethernet switch to PC
and set the IP in the same network segment of IPCF/PDSN.
Perform the pinging operation of both IPCF and PDSN address.
If the pinging is not through, check hardware, IP address con-
figuration (the IP address of IPCF takes effect only after IPCF
synchronization and reset once the IP address is configured)
and the port configuration of Ethernet switch.
5. If the ping operation is through, then check whether the PDSN
and PCF are consistent in interconnection parameters.
Interconnection between
BSC and AN-AAA
Prerequisites 1. Make sure that all BSC boards work normally.
2. Configure connection related data in NetNumen™ M3 (ZXC10
BSSB) including A12 interface, AN IP address, and A12 and
A13 configuration.
3. The connection between IPCF of BSC and the Ethernet switch
and that between AN-AAA and the Ethernet are normal.
Steps Perform the following steps for commissioning:
1. After data configuration, synchronize the data to the NE and
save data in OMP/RPU. Then Reset RPU, SPCF and IPCF.
2. Check the physical connection between IPCF and AN-AAA by
checking the status of the LINK1 indicator on the IPCF front
panel, IPCF and AN-AAA port indicators corresponding to the
Ethernet switch port.
3. If the physical link is good, connect the Ethernet switch to
a PC and set the IP address in the same network segment
of IPCF/AN-AAA. Then ping the addresses of both IPCF and
AN-AAA. If the pinging fails, check the relevant hardware, IP
address configuration and the Ethernet switch port configura-
tion.
4. If pinging IPCF from AN-AAA succeeds, check whether the pa-
rameter settings at both sides for AN-AAA interconnection are
consistent.
Caution:
The shared key on PSDN side is made up of characters while
that on BSC side is made up of ASCII codes.
BSC-PDS Interconnection
Prerequisites 1. Make sure that all BSC boards work normally.
2. Configure connection-related data in NetNumen™ M3 (ZXC10
BSSB) including PDS, PCF mode, PTT IP interface address, PTT
A10 interface parameter, PCF-PDS connection, PTT SPI and
static route.
3. The network cable connects IPCF of BSC with the Ethernet
switch and PDS with the Ethernet normally.
Steps Perform the following steps for commissioning:
1. After data configuration, synchronize the data to the NE and
save data in OMP/RPU. Then Reset RPU, SPCF and IPCF.
2. Check whether there is PDS not connectable alarm on SPCF. If
no, it means the SPCF is communicating with PDS normally.
3. If there is such an alarm, check the physical connection be-
tween SPCF and PDS, including LINK2 indicator on IPCF front
panel, Ethernet switch port that corresponds to IPCF and PDS,
Caution:
The newly configured IP address of IPCF can take effect only
after the data is synchronized and the IPCF is reset.
Service Commissioning
Table of Contents
Voice Service Commissioning ..............................................51
1x Release A Data Service Commissioning ............................52
Asynchronous Circuit Data Service Commissioning .................54
PTT Service Commissioning.................................................55
1xEV-DO Service Commissioning .........................................57
Voice Service
Commissioning
Prerequisites 1. BSC is connected to MSC
2. MSC is connected to HLR.
3. BTS is connected to BSC and there is no BTS alarm shown in
NetNumen™ M3 (ZXC10 BSSB) monitor.
4. SID, NID, LAC and CI of BTS are added to MSC.
5. Prepare at least two test terminals (preferably tested in ZTE
network), whose frequency and IMSI are modified and can lock
BTS signals. Numbers are allocated in the HLR and voice call
can be made with the terminals.
Steps Perform the following steps for commissioning:
1. Open Call Observation Subsystem to check the voice call func-
tion of the two test terminals.
2. Open Signaling Trace Subsystem and select to trace IMSI. In-
put the IMSI of caller to trace all the signaling of caller.
3. Use one test terminal as the caller to call the other terminal,
to check for the normal setup of calls.
4. If calls can be set up normally, but there are monologs, check
if the E1/T1 line is cross connected from BSC to MSC.
5. If calls cannot be set up normally, check the call status in Call
Observation and Signaling Trace. Check in Signaling Trace to
see if BSC has already sent A1r_CMServiceRequest to MSC and
if yes, perform the following:
If MSC initiates call release or fails to send A1f_AssignmentRe-
quest to BSC:
i. Check if MSC have received the service request sent from
BSC.
ii. Check configuration data in MSC, including number analy-
sis, office direction configuration, and SSN configuration.
10. The PC that connects with the test terminal has been set for
number dialing.
Steps Perform the following steps for commissioning the 1X data service:
1. Open Call Observation Subsystem to check the data call func-
tion of the test terminal.
2. Open Signaling Trace Subsystem and select to trace IMSI. In-
put the IMSI of test terminal so as to trace all signaling.
3. Use dialup connection of the PC to initiate a data service call
to PDSN, and check if dialup connection can be established.
4. If the call can be set up but no access is allowed to Internet,
then check the PI and DNS of PDSN as well as the setting of
router that connects to PDSN.
5. If the dialup connection interface of PC is unable to make the
connection with the device, then check terminal MODEM con-
nection to the PC.
6. If the dialup connection interface of PC shows username and
password error, then check the username and password are
consistent with those in PDSN-AAA.
7. If no data call can be made, check the call status via Call Ob-
servation and Signaling Trace to see if the BTS can receive
Umr_OriginationMsg sent by the test terminal. If no, check
the connection between PC and test terminal.
8. Check if BSC sent A1r_CMServiceRequest message to MSC.
Perform the following steps if MSC initiates call release or fails
to send A1f_AssignmentRequest message to BSC:
i. Check if the MSC have received the service request sent by
BSC.
ii. Check if BSC version is compatible with MSC version.
iii. Check the data configuration of MSC.
iv. Check the HLR if the test terminal has been granted the
authority of data service call.
v. Check the consistency of connection related data between
BSC and MSC.
vi. Check the consistency of SID, NID, LAC, CI and authenti-
cation mode between BSC and MSC.
vii.Check if service option, IMSI, SID, NID, LAC and CI as sent
along with the service request are correct.
9. Perform the following if BSS fails to send the service request
to MSC after all, or it fails to send A11-RegistrationRequest to
PSDN, or resource allocation fails after BSS sends the request:
i. Check the consistency of board software versions between
BSC and BTS.
ii. Check whether the MDM process is configured on the BTS
side, and the modification of BSC MDM process after the
BTS MDM process is configured. If modified, then delete
the BTS MDM process and configure again.
iii. Check for the BTS signaling flow with BSC. If no, then check
BTS hardware/software and control channel configuration.
iv. If it is because of BTS resource allocation failure, then check
CE and carrier resource of BTS, status of search window,
cell radius and clock system.
iv. Check whether PTT service call authority has been granted
in PHR and DAS for the terminal and the IMSI is correct or
not.
v. Check the consistency of connection related data between
BSC and PDS.
vi. Check if service option and IMSI, sent along with the ser-
vice request are correct.
1xEV-DO Service
Commissioning
Prerequisites 1. BSC is connected to AN-AAA.
2. BSC is connected to PDSN.
3. PDSN is connected to PDSN-AAA.
4. BTS is connected to BSC and there is no BTS alarm as shown
in NetNumen™ M3 (ZXC10 BSSB) monitor.
5. Prepare at least one test terminal with available fax function
(preferably tested in ZTE network), whose frequency, IMSI,
NAI and PASSWORD are modified and can lock BTS signal.
6. Complete the Number allocation in AN-AAA and grant the au-
thority of 1xEV-DO call.
7. Complete the number allocation in PDSN-AAA and allocate the
User name and password for number dialing.
8. Set the PC connected to the test terminal for number dialing.
Steps Perform the following steps for commissioning:
1. Open Call Observation Subsystem to observe the terminal sta-
tus for making 1xEV-DO call.
2. Open Signaling Trace Subsystem and select to trace Hard-
wareID (ESN), input the HardwareID of the caller to trace its
signaling.
3. Use the PTT caller terminal to initiate private call and group call
and check the call set up process.
4. Check whether BSC sent A1r_CMServiceRequest message to
MSC. If yes, do the following if MSC initiates call release or
fails A1f_AssignmentRequest message to BSC:
i. Use dialup connection of the PC to initiate a data service
call to PDSN.
ii. If the call can be set up but no access is allowed to Internet,
then check the PI and DNS of PDSN as well as the setting
of router that connects to PDSN.
iii. If the dialup connection interface of PC shows that con-
nection cannot be made to the device, then check terminal
MODEM connection to the PC.
5. If the dialup connection interface shows username and pass-
word error, then check the username and password are con-
sistent with those in PDSN-AAA.
6. If no data call can be made, check the call status via Call Obser-
vation and Signaling Trace to see if BTS has received Umr_Orig-
inationMsg sent by the test terminal. If no, check the connec-
tion between PC and test terminal.