Sjzl20091753-ZXC10 BSSB (v 8.0.2.004) CDMA2000 Base Station System Commissioning Manual

ZXC10 BSSBCDMA2000 Base Station System

Commissioning Manual

Version 8.0.2.004

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis 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 CORPORATIONor 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 theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

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

Revision History

Revision No. Revision Date Revision Reason

R1.0 05/15/2009 First Edition

Serial Number: sjzl20091753

Contents

Preface............................................................... i

Commissioning Workflow..................................1CDMA BSS Commissioning Workflow ................................. 1

BSC Commissioning Workflow .......................................... 3

BTS Commissioning Workflow........................................... 4

Commissioning Preparations.............................5Preparation Flow ............................................................ 5

Commissioning Environment Check................................... 7

Data Collection............................................................... 7

Precautions.................................................................... 8

BSS Power-on ...................................................9BSC 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 ..........................................15Data Configuration.........................................................15

BSSB Commissioning.......................................17OMP 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

Purpose This Manual pro vides procedures and guidelines that support theoper ation of the ZX C10 BSCB CDMA2000 Base Station ControllerData Configur ation.

IntendedAudience

This document is intended for engineers and technicians who per -form configur ation activities on the ZX C10 Base Station Controller .

Prerequisite Skilland Knowledge

To use this document effectiv ely , users should ha ve a gener al un-derstanding of wireless telecommunications technology . Familiar -it y with the following is helpful:

� ZX C10 BSCB CDMA 2000 Base Station Controller system andits various components

� Local oper ating procedures

What is in ThisManual

This Manual contains the following chapters:

Chapter Summary

Chapter 1CommissioningWorkflow

Describes BS S commission workflow .

Chapter 2CommissioningPrepar ations

Describes prepar ations, en vironment check, datacollection and precautions for BS S commissioning.

Chapter 3 BS SPower -on

Describes BSC cabinet power -on, NetNumen™M31 (ZX C10 BS SB) serv er power -on and BTScabinet power -on and precautions.

Chapter 4 DataConfigur ation

Describes data configur ation duringcommissioning.

Chapter 5 BS SBCommissioning

Describes BS S commissioning procedure,including OMP board commissioning, otherBSC board commissioning, BSC versionquery , BS S board running state query , BSCbasic commissioning and Session Serv ercommissioning.

Chapter 6InterconnectionCommissioning

Describes the interconnection commissioningbetween BS S and MSC/MSCe/PDSN/AN -AAAserv er/PDS .

Chapter 7 ServiceCommissioning

Describes commissioning of voice service, 1xRelease A data service, asynchronous circuit dataservice, PT T service and 1xEV -DO service.

Confidential and Proprietary Information of ZTE CORPORA TION i

ZXC10 BSSB Commissioning Manual

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

CommissioningWorkflow

Table of ContentsCDMA BSS Commissioning Workflow ..................................... 1BSC Commissioning Workflow .............................................. 3BTS Commissioning Workflow............................................... 4

CDMA BSS CommissioningWorkflowFigure 1 illustrates the general commissioning flow for CDMA BSSBsystems.

Confidential and Proprietary Information of ZTE CORPORATION 1


FIGURE 1 GENERAL COMMISSIONING FLOW OF CDMA BSSB

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Commissioning Workflow

The flow is described as follows:

The reports numbered 1, 2, 3, 5, 7, 10, 11, 12 and 15 are com-pleted by the system commissioning personnel.

The reports numbered 4, 6, 8, 9, 13 and 14 are completed by theproject acceptance personnel and project coordinator.

The flow given in Figure 1 is for reference only. The BSC and BTScommissioning quality widely decides future work status of BSCand BTS, and hence the necessity of commissioning norms, whichare designed to maximize system stability and performance.

BSC CommissioningWorkflowFigure 2 shows the BSC commissioning workflow.



FIGURE 2 BSC COMMISSIONING WORKFLOW

BTS CommissioningWorkflow

Note: For details, refer to related commissioning manuals forspecific BTS products.


C h a p t e r 2

CommissioningPreparations

Table of ContentsPreparation Flow ................................................................ 5Commissioning Environment Check....................................... 7Data Collection................................................................... 7Precautions........................................................................ 8

Preparation FlowFigure 3 shows the commissioning preparation stages.



FIGURE 3 COMMISSIONING PREPARATION STAGES

Upon receipt of commissioning task, the commissioning personnelshould make the following preparations:

1. Find out detailed address and contact information of the user,responsible person of the concerned office, and the type ofequipment installed.

2. Contact local ZTE office to learn the preparation status of theproject.

3. Look up related documents and consult the production depart-ment and marketing department about the details of the equip-ment involved, including configuration and delivery status (in-cluding shortage status).

4. Prepare necessary tools and software. Software includes ver-sion software and NetNumen™ M3 (ZXC10 BSSB) software.Tools include screwdriver, tweezers, pliers, wrenches, elec-tric iron, solder wire, antistatic wrist strap, chip extractor andmulti-meter.


Chapter 2 Commissioning Preparations

5. Prepare the latest version of technical documents for refer-ence:

� ZXC10 BSCB Hardware Manual

� ZXC10 BSCB Technical Manual

� ZXC10 BSSB Data Configuration Manual

6. Carry all required reports, including:

� Equipment Commissioning Problem Feedback

� Test Records

� Project Change Notification

� Equipment Commissioning Receipt Table

� Commissioning Maintenance Report

� Handover Report

� Project Handover Table

� Project Summary Report

� Installation Acceptance Test Report

� Commissioning Acceptance Report

� Project Memo

� Preliminary Acceptance Certificate

� Project Quality Report

� Preliminary Acceptance Application Report

� Field Training Records

7. Estimate the work time for the commissioning work and theestimated completion time.

Commissioning EnvironmentCheckTo guarantee smooth commissioning and satisfy requirements, itis required to check the equipment installation environment.

� Check the following items: cable connections, grounding andpower supply.

� After completing, fill the Installation Acceptance Test Report.

� Note that the system commissioning cannot proceed unless theinstallation is accepted.

Data CollectionCollect the necessary data before commissioning:



� Make sure the user provides the data about MSC/PDSN/AN-AAA/PDS.

� The network staff should provide information for interconnect-ing BSSB with MSC/PDSN/AN-AAA/PDS, and other informationsuch as SID(System ID), NID(Network ID), Mobile NetworkCode (MNC), CDMA channel frequency assignment, LocationArea Code (LAC), Cell ID (CI), PN Planning, and neighbor celllist.

� Make sure all the necessary data is collected for smooth com-missioning process.

PrecautionsFollowing are the precautions for successful commissioning:

ESD (ElectronicStatic Discharge)

Protection

Follow ESD protection requirements strictly. Antistatic jumper isrequired for admission to equipment room. Antistatic wrist strapis 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 storedin good order.

Switches andJumpers

Make sure the switches and jumpers on the circuit boards of theequipment are set according to the requirements, especially DIPswitches.

TransmissionCircuits

Check the circuits at A interface and Abis interface and make surethe 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.


C h a p t e r 3

BSS Power-on

Table of ContentsBSC Cabinet Power-on ........................................................ 9OMC Server Cabinet Power-on.............................................12

BSC Cabinet Power-onChecking BSC Before Power-on

Prerequisites The BSC cabinet is installed successfully.

Steps 1. Measure the resistance at the –48V/-48VGND connector postson top of the rack using a multi-meter.

Caution:

There are two input pairs to be measured.

2. Measure the resistance at the -48V/-48VGND input terminalsof the power distribution box using the multi-meter. There aretwo input pairs to be measured.

3. Measure the resistance at the -48V/-48VGND output terminalsof the power distribution box using the multi-meter. There is a-48V/-48VGND output pair to be measured.

4. Disconnect the power cables from the fans of BSC.

5. Make sure the power switch of the service shelf is set to OFF.

6. Make sure the two air breakers on the front panel of powerdistribution box are set to OFF.

7. Check the DIP switches of BSC.

END OF STEPS



BSC Power-on Check Requirements

1. Usually the –48V and –48VGND terminals should be open cir-cuit before power-on.

2. Table 2 shows the correct usage of Multi-meter probes.

TABLE 2 MULTI-METER PROBES USAGE

Terminal 48 V 48 VGND

Multi-meter probe Red Black

3. The DC voltage in the equipment room: Standard value -48V(allowed fluctuation range: -40V ~ -57V).

4. The cabinets must be arranged in orderly and firmly assembledmanner. The labels on the cabinets must be correct and clear.

5. The cables must be correctly connected, with their connec-tors securely inserted. Two ends of the cable must be clearlymarked or labeled. The laying of all cables is orderly and easyfor future maintenance and expansion.

6. The pins on the backplane should not be bent or short-cir-cuited.

7. The DIP switches of the BSC cabinet must be correctly set. Thesubrack accommodating OMP must be the second subrack ofrack 1. Other subrack DIP switches comply with the actual con-figurations. Figure 4 shows the settings of BSC DIP switches.

FIGURE 4 BSC DIP SWITCH SETTINGS

Table 3 describes these DIP switches.

TABLE 3 DIP SWITCH DESCRIPTION OF BSCB SERVICE SUBRACKBACKPLANE

DIP Switch Description

TRIB_ID Identifies offices 0–7 in 3–bit binary digit(000–111)

RACK_ID Identifies cabinets 1–16 in 4–bit binary digit(0000~1111)

SHELF_ID Identifies subracks 1–4 in 2–bit binary digit(00–11)


Chapter 3 BSS Power-on

Note:

When a DIP switch bit is set to ON, the corresponding binarydigit is 0; when it is set OFF, the corresponding binary digit is1.

Description of the DIP switch TRIB_ID:

i. TRIB_ID corresponds to DEVS_ID or BSS_ID (AN_ID) onthe OMC and is set during installation of the OMC.

ii. When TRIBID=3, the corresponding binary is 011. Figure5 shows the detailed setting.

FIGURE 5 TRIBID SETTING

– For S1, TRIBID0=1 (theleast significant bit),

TRIB1=1 and TRIBID2=0(the most significant bit).

Settings of DIP switches RACK_ID and SHELF_ID:

i. RACK_ID corresponds to the rack number plus 1 in theOMC; while SHELF_ID corresponds to the subrack numberplus 1.

For example, when RACK_ID is set to 0001, the corre-sponding rack number configured in the OMC is 2.

ii. Figure 6 shows the detailed setting.

FIGURE 6 RACK_ID SETTING



Powering on BSC Cabinet

Prerequisites � All the boards (including their power supply) are at correct po-sitions and have not been inserted in the slots.

� All the power switches are set to OFF.

Steps 1. Close the air breaker to power on the BSC rack.

2. After the BSC rack is powered on, use a multi-meter to mea-sure the input voltage on the top of the BSC rack after –48VDC is led in.

3. Use the multi-meter to measure the output voltage of thepower distribution box.

4. Connect all BSC power cables behind the fans.

5. Set the power switch of the service shelf to ON.

6. Set the two air breakers on the front panel of power distributionbox to ON.

7. Plug all boards into the slots.

END OF STEPS

OMC Server CabinetPower-onChecking OMC Server beforePower-on

Prerequisites The NetNumen™ M3 (ZXC10 BSSB) server has been installed suc-cessfully.

Steps 1. Use a multi-meter to measure the resistance at the L and Nposts on the top of the server rack. There are two input pairsto be measured.

2. Set the two input switches at front panel and three fan airbreakers to OFF.

3. Turn off the NetNumen™ M3 (ZXC10 BSSB) server.

END OF STEPS


Chapter 3 BSS Power-on

OMC Server Power-on CheckRequirements

1. Usually the L and N posts should be open circuit before power-on.

2. Table 4 shows the correct usage of Multi-meter probes.

TABLE 4 MULTI-METER PROBES USAGE

Terminal Post N Post L

Multi-meter probe Red Black

3. Make sure the DC voltage in the equipment room is 220V (al-lowed fluctuation range: 150V-300V, 45 Hz-55Hz)/110V (al-lowed fluctuation range: 80V-150V, 45Hz-55Hz).

4. The cabinets must be arranged in orderly and firmly assembledmanner. The labels on the cabinets must be correct and clear.

5. The cables must be correctly connected, with their connec-tors securely inserted. Two ends of the cable must be clearlymarked or labeled. The laying of all cables is orderly.

Powering on OMC Server Cabinet

Prerequisites The two inputs of the front panel, three air switches of the fan andthe power of the server cabinet are OFF.

Steps 1. Close the air breaker to power on the server rack.

2. After the rack is powered on, measure the input voltage onrack top to see whether it is correct.

3. Turn on the fan switch on front panel and check whether therack top fan runs normally.

4. Close the two inputs on front panel and check whether theoutput voltage of the server rack is normal.

5. Switch ON the power of server.

END OF STEPS


C h a p t e r 4

Data Configuration

Table of ContentsData Configuration.............................................................15

Data ConfigurationZXC10 BSSB data configuration depends on the technical require-ments specified in the contract, project survey report and networkplanning. At the MSC side, cell information, location area code(LAC), A interface related SS7 link, trunk circuit, and signalingpoints 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 neededaccording to the required services.

Six typical BSC data configurations are given below to suit differentoffice scales. It can be used as a reference to configure BSC dataaccording to board configuration status. For more details, refer tothe 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, tosupport 1xEV-DO service alone.

3. Typical BCTC+BUSN configuration for 2-shelf office, to support1X Data, 1xEV-DO and PTT service (unnecessary boards canbe deleted).

4. Typical BUSN+BUSN interconnection for 2-shelf office, to sup-port 1X Data, 1xEV-DO and PTT service (unnecessary boardscan be deleted).

5. Typical configuration for 3-shelf office, to support 1X, 1xEV-DOand 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 canbe deleted).


C h a p t e r 5

BSSB Commissioning

Table of ContentsOMP Board Commissioning .................................................17Other BSC Board Commissioning ........................................30Querying Version...............................................................35Checking Board Running Status...........................................37Basic Commissioning .........................................................38

OMP Board CommissioningChecking Physical Link betweenOMP and OMC Server

Prerequisites 1. Make sure that the BSC system is debugged before it leavesfactory and software versions are usually saved in OMP.

2. When a BSC cabinet connects to power, the OMP board startsrunning and the RUN2 indicator on OMP/RPU front panelflashes.

Context If OMP cannot run normally, download the software version fromthe NE.

Steps 1. Check for the OMC2 indicator on OMP/RPU front panel. If theindicator doesn’t flash, check both the network cable from theOMC2 network interface on NetNumen™ M3 (ZXC10 BSSB)server rear board to Ethernet switch and also the port on Eth-ernet switch.

2. Check whether the IP address of the NetNumen™ M3 (ZXC10BSSB) server is 129.0.31.1/16. Check the network cable fromthe server to the Ethernet switch.

3. Ping OMP IP 129.0.31.0/16 from NetNumen™ M3 (ZXC10BSSB) server. If the pinging fails, connect the Ethernet switchto another PC with IP address 129.0.31.*/16. Now PingNetNumen™ M3 (ZXC10 BSSB) IP 129.0.31.1 and OMP IP129.0.31.0. If fails, check network cable, IP address andEthernet switch port.

END OF STEPS



Setting OMP IP Address

Prerequisites The OMP board is powered on.

Steps 1. Prepare a serial cable whose one end is a RJ45 connector usedto connect to the DEBUG2-232 port on the OMP slot of BCTCbackplane. The other end of the cable is a serial port to connectto a PC (the serial cable is shipped for new deployment).

2. Start the hyper terminal in PC and use the default setting ofhyper terminal.

3. Reset the OMP board and a screen as shown in Figure 7 ap-pears. Press any key to stop the OMP auto-boot.

FIGURE 7 OMP BOOTING

4. Enter 3gplat and a screen appears, as shown in Figure 8.

FIGURE 8 OMP BOOT MODE SELECTION

5. Enter 1 to display a screen as shown in Figure 9.


Chapter 5 BSSB Commissioning

FIGURE 9 CONFIGURATION SELECTION OF OMP

6. Enter 1 to select Set Omp(or Cmp)’s Omc Ip,Mac,GatewayIP. The screen for setting OMP IP address appears, as shownin Figure 10.

FIGURE 10 SETTING OMP IP ADDRESS

Enter the OMP IP address to be set into [Enter OMP’s OMC Ipaddress]. This IP address is used by OMP boards to access theNetNumen™ M3 (ZXC10 BSSB) server. Usually the IP addressof NetNumen™ M3 (ZXC10 BSSB) server is set to 129.0.31.*:ff000000.

The system will give the following messages:

[Enter OMP’s OMC Ip address]: OMP IP address (usually129.0.31.0)

[Enter OMP’s OMC Mac address]: 10.10.10.10.10.10

[Enter OMP’s Gateway Ip address]:

7. Enter 2 in Figure 9 and select Set Omp Boot Paras.

Enter your selection(1/2/3/4/5/6):2

[Enter OMC Ip address]: 129.0.31.245

[Enter OMC FTP port No.]: 21

[Enter OMC FTPSVR User Name]: admin

[Enter OMC FTPSVR PassWord]: admin

[Enter OMC FTPSVR FilePath]:



[Enter OMP CFGINFO FileName]: ompcfg.ini

8. Enter 3 in Figure 9 and select Set Omp Boot Type.

Figure 11 shows the steps of Please Set OMP Boot Type:(0 isBoot From OMC; 1 is Boot From Local Flash).

FIGURE 11 SETTING OMP STARTUP MODE

9. Enter 4 in Figure 9 and select Set Net_Element Bureau No.

Figure 12 shows the steps.

FIGURE 12 SETTING BUREAU NO.

10. Enter 5 in Figure 9 and select Quit config, return to boot-menu!.Enter your selection(1/2/3/4/5/6):5 Quit config and return toBootMenu! [3GPlat Boot]: 0

END OF STEPS

OMP Version Loading

Loading Version from OMC

Prerequisites If OMP works well (the running version is earlier than the deploy-ment version) and normally communicate with the OMM server, itis advisable to download the OMP versions from OMM to updateexisting older version on OMP.



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 > VersionManagement, as shown in Figure13.

FIGURE 13 OPENING VERSION MANAGEMENT WINDOW

3. In the Version Management window, select Version Man-agement > Add Version to display the Add Version window,as shown in Figure 14.



FIGURE 14 ADDING VERSION

4. Click √ on the toolbar and select the directory where the OMPversion file is located, as shown in Figure 15.

FIGURE 15 SELECTING A VERSION FILE

5. Select the directory where the OMP version file lies and clickOK.

6. Right-click the version file to be added and select Add Versionfrom the shortcut menu.



FIGURE 16 ADDING A VERSION

7. Figure 17 shows the version addition result.

FIGURE 17 VERSION ADDITION RESULT

8. Select Version Management > Advanced > ConfigureOMP Version to display the Configure OMP Version win-dow, as shown in Figure 18.



FIGURE 18 CONFIGURING OMP VERSION

9. Select Configure OMP Version > Configure OMP Versionand the boards that can be configured are displayed, as shownin Figure 19.

FIGURE 19 OMP VERSION CONFIGURATION

10.Right—click an record whose Logic Type is OMP and selectSelect Backup Version from the shortcut menu. The SelectBackup Version dialog box appears, as shown in Figure 20.



FIGURE 20 SELECTING A BACKUP OMP VERSION

11.Select a backup version and click OK to return to the Config-ure OMP Version window.

12.Right—click the OMP and select Configure OMP Special Ver-sion to start the OMP version configuration. The progress isdisplayed in this window, as shown in Figure 21.

FIGURE 21 CONFIGURING OMP



13.After the software version is configured successfully, reset thecorresponding OMP board to activate the new software version.

END OF STEPS

Loading Version from NE

Prerequisites When there is no software version in the OMP board of BSC orthe OMP board fails to communicate with NetNumen™ M3 (ZXC10BSSB) server, or the OMP board needs to be formatted for versionupgrading, perform the following steps for commissioning:

Steps 1. Connect the OMP and set the OMP IP address.

2. Create an OMP information file.

Save the OMP version (the CPU version with the suffix of bin,FPGA version with the suffix of fga and MP type file) underthe directory (ums\ums-svr) specified by the FTP server. Rundownload3g.exe and click the Create OMPinfo button in thepop-up window.

As shown in Figure 22, the MP type is MT_3G_OMP. Selectthe OMP CPU version file with the suffix of bin and the versionnumber will be automatically generated (it is version 08.20.01in Figure 22. Select the logic file (the FPGA version file withthe suffix of fga) and the version number will be automaticallygenerated (it is version 08.19.03 in Figure 22. After settinginformation in the left pane, set information in the right panein the same way. After the information setting, click Createconfig file to create an ompcfg.ini file under ums\ums-svr.



Caution:

For the OMP with 85 series chip, set CPU version only. The OMPinformation file creation window is as shown in Figure 23.

FIGURE 22 CREATING INFORMATION FILE FOR OMP WITH 755 SERIESCHIP



FIGURE 23 CREATING INFORMATION FILE FOR OMP WITH 85 SERIESCHIP

3. Start the NetNumen™ M3 (ZXC10 BSSB) server and client andthe NetNumen™ M3 (ZXC10 BSSB) server will automaticallystart an FTP server.

4. OMP automatically downloads the ompcfg..ini file from thespecified directory of the server after being powered on. Itreads file information before downloading corresponding CPUversion software and FPGA version software.

5. Upon completion of the downloading, OMP resets automaticallyto validate the new version software.

END OF STEPS

Synchronizing/Saving OMP Data

Prerequisites BTS and BSC data configuration has been completed.

Context When OMP is started successfully, it downloads data from NetNu-men™ M3 (ZXC10 BSSB) for data synchronization and automati-cally performs data saving.

Steps 1. In the Configuration Management window, right-clickZXC10 BSSB and select Data Synchronization to displaythe Data Synchronization window, as shown in Figure 24.



FIGURE 24 SYNCHRONIZING OMP DATA

2. Select OMP and click Start on the toolbar to start an OMPdata synchronization. The system will give a message uponcompletion of the synchronization.

3. In the Configuration Management window, right-clickZXC10 BSSB and select Save Control to display the SaveControl dialog box, as shown in Figure 25.

FIGURE 25 SAVE CONTROL

4. Select OMP from the navigation tree and Save active boarddata from the right pane and click Start on the toolbar andclick OK in the pop-up dialog box to save the active boarddata, as shown in Figure 26.



FIGURE 26 SAVING OMP DATA

5. Select Active and standby board synchronize to save thestandby OMP data.

6. After saving data, reset the active and standby OMP boards.

END OF STEPS

Other BSC BoardCommissioningAdding Version

Steps 1. Copy all the versions including CPU version, FPGA version andMCU version to the directory \ums\ums-svr\version of theNetNumen™ M3 (ZXC10 BSSB) installation path.

2. Load the software of other boards to OMP.

END OF STEPS

Activating Version

Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > SystemTools > Version Management to display the Version Man-agement window.

2. Select Version Management > Activate Version to displaythe Activate Version window, as shown in Figure 27.



FIGURE 27 ACTIVATING VERSION

3. Select Activate Version > Common Activation to displaythe Common Activation dialog box, as shown in Figure 28.

FIGURE 28 COMMON ACTIVATION WINDOW



4. Select BSCB and then select the boards to be activated in theSelect logic board type area and click OK. The ActivateVersion dialog box appears, as shown in Figure 29.

FIGURE 29 ACTIVATE VERSION DIALOG BOX

5. The record whose Backup Version is marked with a green ar-row indicates the corresponding board has more than one ver-sion in OMP. Right-click such record and select Select BackupVersion to display the Select Backup Version dialog box, asshown in Figure 30.



FIGURE 30 SELECTING BACKUP VERSION

6. Select a backup version and click OK.

7. Right-click a logic board to be activated and select Activationfrom the shortcut menu to activate the board, as shown inFigure 31.

When the board is activated successfully, Succeeded will ap-pear in Task Status.



FIGURE 31 SELECTING A BOARD TO BE ACTIVATED

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 Managementto display the Alarm Management window.

2. Select ZXC10 BSSB > BSSB > BSCB > Rack to display therack diagram.

3. Right-click the board to be reset and select Reset Board Nor-mally, as shown in Figure 32.



FIGURE 32 RESETTING BOARD

4. If a board cannot be reset normally, select Reset BoardForcedly to forcedly reset the board.

END OF STEPS

Querying VersionSteps 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 theQuery Version window, as shown in Figure 33.



FIGURE 33 QUERYING VERSION

3. Select Query VersionQuery Running Version to display theQuery Running Version dialog box, as shown in Figure 34.

FIGURE 34 QUERYING RUNNING VERSION

4. Select the boards to be queried and click OK. The query resultis displayed in the Running Version Info tab, as shown inFigure 35.



FIGURE 35 VERSION QUERY RESULT

5. Check the running version of every board and make sure theyare correct.

END OF STEPS

Checking Board RunningStatus



Context For details of indicator states, refer to the corresponding hardwaremanual.

Steps 1. Open the front door of the BSCB cabinet and observe whetherthe RUN indicator of every board flashes in 1Hz.

2. Check whether the ALM indicator of every board is green. Ifan indicator is red, it means an alarm occurs.

3. View alarm information through the AlarmManagement win-dow of the OMM client.

END OF STEPS



Basic CommissioningPerforming Module Commissioning

Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > FaultManagement > 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 selectSelect All, as shown in Figure 36.

FIGURE 36 SELECTING BOARD

3. Select Operation > Start Board Test to perform commis-sioning test on the boards selected, as shown in Figure 37.

FIGURE 37 STARTING BOARD TEST



4. The test result is displayed upon completion of the test.

END OF STEPS

Performing Media StreamCommunication Test

Context This test is to check if the media stream communication betweenUIMU of BUSN and BPSN is normal.

Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > FaultManagement > Diagnosis Management to display the Di-agnosis Management window.

2. Select BSSB > BSCB > IP Rack to display a rack diagram.

3. Right-click an UIMU in a BUSN and select Media StreamSource from the shortcut menu and the board will turn blue,as shown in Figure 38.

FIGURE 38 SELECTING A MEDIA STREAM TEST SOURCE BOARD

4. Right–lick a GLI board in BPSN and select Media Stream Tar-get from the shortcut menu and the board will turn blue, asshown in Figure 39.



FIGURE 39 SELECTING A MEDIA STREAM TARGET BOARD

5. Select Operation > Test Media Stream to display the TestMedia Stream dialog box, as shown in Figure 40.

FIGURE 40 STARTING A MEDIA STREAM TEST



6. Select CPUs and click Start Test. The system will start testingthe media stream link from BUSN to BPSN. The test result isnormal if the packets sent by UIMU and the packets receivedby GLIQV are the same.

7. Test other boards in BUSN to make sure the media streamcommunication is normal. If loss of packets occurs, check thefiber connection between the UIMU and GLI.

END OF STEPS

Performing Alarm Test



Steps 1. In the NetNumen M3 (ZXC10 BSSB), select Views > FaultManagement > Alarm Management to display the AlarmManagement window.

2. Check whether the alarms displayed in the rack diagram areconsistent with the actual alarms.

3. Open the front door of the BSCB cabinet and unplug and plugevery board and observe the corresponding board in the rackdiagram can correctly generate corresponding alarms in time.

4. Make records.

END OF STEPS

Switchover Test

Performing OMP Switchover Test



Steps 1. Switch over OMP board using command.

1. Select Views > Fault Management > Alarm Manage-ment to display the Alarm Management window.

2. Right-click the active MP board configured with OMP mod-ule and select Switch Board Normally from the shortcutmenu.

3. Select CPU1 (corresponding to OMP) from the pop-up dia-log box and click OK.

4. 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.



5. Open the front door of the BSCB cabinet and observe theACT1 indicator of the active OMP board. It should be onbefore the switchover and be off after the switchover.

6. Switch over the board repeatedly to check whether theswitchover is normal and make records.

2. Switch over OMP board due to failure

1. Right-click the active OMP board (select the CPU1 ofOMP/RPU) and select Switch Board Normally.


3. Open the front door of the BSCB cabinet and observe theACT indicator of the active OMP board. It should be onbefore the switchover and be off after the switchover.


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 shouldbecome an active board and the communication betweenthe NE and OMC should be normal.

2. Unplug and plug the active OMP board repeatedly to checkwhether the switchover is normal and make records.

END OF STEPS

Performing RPU Switchover Test



Steps 1. Switch over OMP board using command.

1. Select Views > Fault Management > Alarm Manage-ment to display the Alarm Management window.

2. Right-click the active MP board configured with OMP mod-ule and select Switch Board Normally from the shortcutmenu.

3. Select CPU2 (corresponding to RPU) from the pop-up dia-log box and click OK.


5. Open the front door of the BSCB cabinet and observe theACT2 indicator of the active OMP board. The indicatorshould be on before the switchover and be off after theswitchover.


2. Switch over OMP board due to failure

1. Right-click the active OMP board (select the CPU1 ofOMP/RPU) and select Switch Board Normally.




3. Open the front door of the BSCB cabinet and observe theACT indicator of the active OMP board. It should be onbefore the switchover and be off after the switchover.


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 shouldbecome an active board and the communication betweenthe NE and OMC should be normal.

2. Unplug and plug the active OMP board repeatedly to checkwhether the switchover is normal and make records.

END OF STEPS

Performing Power-on/off Test

Prerequisites � The BSCB is configured with the version management function.

� The BSCB is configured successfully.

� The BSCB is configured with the data saving control function.

Context Power OFF all shelves except for the GCM shelf and unplug theOMP/RPU board. Power on and power off every shelf repeatedlyto check whether the boards in each shelf can work normally.

Steps 1. Open the rear door of the BSCB cabinet and power off all theshelves except for the GCM shelf.

2. Open the front door of the BSCB cabinet and unplug the OMPboard.

3. Power on shelves one by one.

4. Plug the OMP board and check whether the system can startnormally and whether the communication between the NE andOMC is normal and whether there are alarms generated.

5. Test modules.

END OF STEPS

Postrequisite In case of failure occurring, check the corresponding board andconnection. Perform the test again after making sure that there isno exception and make records.


C h a p t e r 6

InterconnectionCommissioning

Table of ContentsOverview..........................................................................45BSC-MSC Interconnection (A Interface) ................................45BSC-MSCe Interconnection (Ap Interface).............................46BSC-PDSN Interconnection .................................................47Interconnection between BSC and AN-AAA............................48BSC-PDS Interconnection ...................................................48

OverviewThe BSC commissioning should be followed by a joint (connectingBSC to MSC, PDSN, AN-AAA and PDS) system commissioning tomake 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 ofMSCe.

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 SS7data.

3. Connect the BSC to MSC using E1/T1 cable (DTB board) oroptical 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 MSCside with the BSC side.

5. Check whether there is Signaling Link Unavailable alarmon OMP. Then compare the data between BSC and MSC andit should be consistent. If using DTB board, then check theE1/T1 cable between BSC and MSC against that is configuredin 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 aswell as signaling data.

3. The network cable connects IPI and SIPI of BSC to the Ethernetswitch, MGW and Ethernet normally.


1. After data configuration, synchronize the data to the NE andsave data in OMP/RPU. Then Reset RPU, APCMP, SIPI and IPI.

2. Check for the Signaling Link Unavailable alarm on OMP and ifthere is no such alarm, it indicates that BSC is communicatingwith MSCe normally.

3. If there is signaling link unavailable alarm on OMP, then checkthe 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 toSIPI of BSC and MSCe. If any indicator is abnormal, check thenetwork 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 toPC and set the IP in the same network segment of SIPI of BSCand MSCe. Perform the pinging of both SIPI of BSC and MSCeaddress. If the ping operation is not through, check hardware,IP address configuration and the port configuration of Ethernetswitch.


Chapter 6 Interconnection Commissioning

Caution:

After configuring IP addresses of BSC IPI, BSC SIPI, MSC IPIand MSC SIPI, synchronize the data and reset these boards tovalidate the new configuration.

5. Check whether the BSC and MSCe are consistent in intercon-nection parameters.

Caution:

both VE unit No. and ground circuit No. are void and are notshown in Voice Observation because VE is at the MGW side.

BSC-PDSN InterconnectionPrerequisites 1. Make sure that all BSC boards work normally.

2. Configure connection related data in NetNumen™ M3 (ZXC10BSSB) 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 Ethernetswitch and PDSN with the Ethernet normally.


1. After data configuration, synchronize the data to the NE andsave data in OMP/RPU. Then Reset RPU, APCMP, SIPI and IPI.

2. Check for the PDSN not connectable alarm on SPCF. If thereis no alarm, it indicates SPCF is communicating with PDSN nor-mally.

3. If there is PDSN not connectable alarm on SPCF, then checkthe physical link between SPCF and PDSN, checking includes:status of LINK1 of IPCF, network port indicator of PDSN, and theport indicator of Ethernet switch that corresponds to IPCF andPDSN. 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 PCand 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 IPCFsynchronization 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 PDSNand PCF are consistent in interconnection parameters.



Interconnection betweenBSC 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 andA13 configuration.

3. The connection between IPCF of BSC and the Ethernet switchand that between AN-AAA and the Ethernet are normal.


1. After data configuration, synchronize the data to the NE andsave data in OMP/RPU. Then Reset RPU, SPCF and IPCF.

2. Check the physical connection between IPCF and AN-AAA bychecking the status of the LINK1 indicator on the IPCF frontpanel, IPCF and AN-AAA port indicators corresponding to theEthernet switch port.

3. If the physical link is good, connect the Ethernet switch toa PC and set the IP address in the same network segmentof IPCF/AN-AAA. Then ping the addresses of both IPCF andAN-AAA. If the pinging fails, check the relevant hardware, IPaddress 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 areconsistent.

Caution:

The shared key on PSDN side is made up of characters whilethat on BSC side is made up of ASCII codes.

BSC-PDS InterconnectionPrerequisites 1. Make sure that all BSC boards work normally.

2. Configure connection-related data in NetNumen™ M3 (ZXC10BSSB) including PDS, PCF mode, PTT IP interface address, PTTA10 interface parameter, PCF-PDS connection, PTT SPI andstatic route.

3. The network cable connects IPCF of BSC with the Ethernetswitch and PDS with the Ethernet normally.


1. After data configuration, synchronize the data to the NE andsave data in OMP/RPU. Then Reset RPU, SPCF and IPCF.

2. Check whether there is PDS not connectable alarm on SPCF. Ifno, 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 frontpanel, Ethernet switch port that corresponds to IPCF and PDS,


Chapter 6 Interconnection Commissioning

and the network port indicator of PDS. If the indicator is ab-normal, check the status of network cable, IPCF network port,PDS network port and Ethernet switch port.

4. If the physical link is good, connect the Ethernet switch to PCand set the IP as in the same network segment as that ofIPCF/PDS. Then ping the address of both IPCF and PDS. If theping operation is not through, check hardware, IP address con-figuration (the IP address of IPCF takes effect only after IPCFsynchronization and reset once the IP address is configured)and the port configuration of Ethernet switch.

Caution:

The newly configured IP address of IPCF can take effect onlyafter the data is synchronized and the IPCF is reset.

5. If the pinging of IPCF from PDS is through, then check dataconfiguration for the connection.


C h a p t e r 7

Service Commissioning

Table of ContentsVoice Service Commissioning ..............................................511x Release A Data Service Commissioning ............................52Asynchronous Circuit Data Service Commissioning .................54PTT Service Commissioning.................................................551xEV-DO Service Commissioning .........................................57

Voice ServiceCommissioning

Prerequisites 1. BSC is connected to MSC2. 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 lockBTS signals. Numbers are allocated in the HLR and voice callcan be made with the terminals.


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, checkif the E1/T1 line is cross connected from BSC to MSC.

5. If calls cannot be set up normally, check the call status in CallObservation and Signaling Trace. Check in Signaling Trace tosee if BSC has already sent A1r_CMServiceRequest to MSC andif 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 fromBSC.

ii. Check configuration data in MSC, including number analy-sis, office direction configuration, and SSN configuration.



iii. Check if the connection related data are consistent betweenBSC and MSC.

iv. Check if SID, NID, LAC, CI and authentication mode areconsistent between BSC and MSC.

v. Check if service option, IMSI, SID, NID, LAC and CI sentalong with the service request are correct.

6. Perform the following steps if BSS fails to send the service re-quest to MSC, or resource allocation fails after BSS sends therequest:

i. Check the board software versions are consistent betweenBSC and BTS.

ii. Check the configuration of MDM process on the BTS side,and check for the modification of BSC MDM process afterBTS MDM process is configured. If modified, then deleteMDM process of BTS and configure again.

iii. Check whether BTS signaling flow is through with BSC, ifno, check BTS hardware/software and control channel con-figuration.

iv. If it is due to BTS resource allocation failure, then check theCE and carrier resource of BTS, status of search window,cell radius and clock system.

v. If it is due to CIC allocation failure, then check if the circuitCIC matches between A interface and MSC and check in theDynamic management if PCM circuit is blocked.

vi. If it is due to VE allocation failure, then check for the shelfof allocated CIC is configured properly with VTCD board,check the resource and the board hardware/software is innormal condition.

vii.If it is due to SE allocation failure, then check all BSC1XSDU resource and the board hardware/software is in nor-mal condition.

1x Release A Data ServiceCommissioning

Prerequisites 1. BSC is connected to MSC.2. MSC is connected to HLR.3. BSC is connected to PDSN.4. PDSN is connected to PDSN-AAA.5. BTS is connected to BSC and there is no BTS alarm shown in

NetNumen™ M3 (ZXC10 BSSB) monitor.6. SID, NID, LAC and CI of BTS are added to MSC.7. Prepare one test terminals (preferably tested in ZTE network),

whose frequency and IMSI are modified and can lock BTS sig-nal.

8. Complete the number allocation in HLR and check the 1X datacall can be made with the terminals.

9. Complete the number allocation in PDSN-AAA to the terminal.Both user name and password are available for number dialing.


Chapter 7 Service Commissioning

10. The PC that connects with the test terminal has been set fornumber 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 callto 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 ofrouter that connects to PDSN.

5. If the dialup connection interface of PC is unable to make theconnection with the device, then check terminal MODEM con-nection to the PC.

6. If the dialup connection interface of PC shows username andpassword error, then check the username and password areconsistent 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 receiveUmr_OriginationMsg sent by the test terminal. If no, checkthe 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 failsto send A1f_AssignmentRequest message to BSC:

i. Check if the MSC have received the service request sent byBSC.

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 theauthority of data service call.

v. Check the consistency of connection related data betweenBSC 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 sentalong with the service request are correct.

9. Perform the following if BSS fails to send the service requestto MSC after all, or it fails to send A11-RegistrationRequest toPSDN, or resource allocation fails after BSS sends the request:

i. Check the consistency of board software versions betweenBSC and BTS.

ii. Check whether the MDM process is configured on the BTSside, and the modification of BSC MDM process after theBTS MDM process is configured. If modified, then deletethe BTS MDM process and configure again.

iii. Check for the BTS signaling flow with BSC. If no, then checkBTS hardware/software and control channel configuration.

iv. If it is because of BTS resource allocation failure, then checkCE and carrier resource of BTS, status of search window,cell radius and clock system.



v. If it is because of SE allocation failure, then check all 1XSDUresource and board hardware/software is in normal condi-tion.

10.Check the BSC sent A11-RegistrationRequest message toPDSN. In case of failure, do the following:

i. Check the service request sent by to PDSN by BSC.

ii. Check the BSC version is compatible with PDSN version.

iii. Check the version and data configuration of both PDSN andPDSN-AAA.

iv. Check whether the test terminal has been granted the au-thority of data service call and if the IMSI is correct inPDSN-AAA.

v. Check whether the connection related parameters are con-sistent between the BSC and PDSN.

vi. Check whether the service option and IMSI sent along withthe service request are correct.

Asynchronous Circuit DataService 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 as shown

in NetNumen™ M3 (ZXC10 BSSB) monitor.4. SID, NID, LAC and CI of BTS have been added to MSC.5. Prepare at least two test terminals with available fax function

(preferably tested in ZTE network), whose frequency and IMSIare modified and can lock BTS signal.

6. Numbers are allocated in the HLR and the authority of fax callis granted.

7. Prepare two fax machines that can work with the test termi-nals.

Steps Perform the following steps for commissioning the Asynchronouscircuit data service:

1. Use the fax machine to set one test terminal as to send faxand the other to receive fax.

2. Open Call Observation Subsystem to observe the terminals’status of making asynchronous circuit data service call.

3. Open Signaling Trace Subsystem and select to trace IMSI, inputthe IMSI of the fax sending terminal to trace all signaling.

4. Use the fax sending machine to send fax to the fax receivingmachine.

5. If fax call fails, check the call status in Call Observation and Sig-naling Trace to check whether the BTS has received Umr_Orig-inationMsg sent by the terminal. If no, check the connectionbetween terminal and fax machine.

6. If fax call fails, check the call status in Call Observation andSignaling Trace to see if BSC sent the A1r_CMServiceRequestmessage to the MSC. If yes, do the following:



i. Check whether the MSC received service request sent byBSC.

ii. Check data configuration in MSC, including number analy-sis, office direction configuration, and SSN configuration.

iii. Check the consistency of connection related data betweenBSC and MSC.

iv. Check the consistency of SID, NID, LAC, CI and authenti-cation mode between BTS and MSC.

v. Check whether the service option, IMSI, SID, NID, LAC andCI sent along with the service request are correct.

7. Perform the following if BSS has not sent the service requestto MSC or the resource allocation fails after BSS sends therequest:

i. Check the consistency of boards’ software versions be-tween BSC and BTS.

ii. Check whether the MDM process is configured on the BTSside, and check the modification of BSC MDM process af-ter the BTS MDM process is configured. If modified, thendelete BTS MDM process and configure again.

iii. Check whether BTS signaling flow is through to BSC, if no,check BTS hardware/software and control channel config-uration.

iv. If it is because of BTS resource allocation failure, then checkthe CE and carrier resource of BTS, status of search win-dow, cell radius and clock system.

v. If it is because of CIC allocation failure, then check if the cir-cuit CIC matches between A interface and MSC. Also checkthe Dynamic management if PCM circuit is blocked.

vi. If it is because of MODEM allocation failure, then check ifthe allocated CIC shelf is configured with IWFB board, ifthere is resource blocked or suspended, and board hard-ware/software is in normal condition.

vii.If it is because of SE allocation failure, then check all BSC1XSDU resource and board hardware/software is in normalcondition.

PTT Service CommissioningPrerequisites 1. BSC is connected to MSC.

2. MSC is connected to HLR.3. BSC is connected to PDS.4. PDS is connected to PHR and DAS.5. BTS is connected to BSC and there is no BTS alarm as shown

in NetNumen™ M3 (ZXC10 BSSB) monitor.6. SID, NID, LAC and CI of BTS have been added to MSC.7. LAC and DLA_ID of BTS have been added to PHR.8. Prepare at least three test terminals with available fax function

(preferably tested in ZTE network), whose frequency and IMSIare modified and can lock BTS signal.



9. Complete the number allocation in HLR and grant the authorityof PTT calls.

10.Complete the number allocation in PHR and grant the authorityof PTT calls.

11.Complete the number allocation in DAS in the same group.

Steps Perform the following steps for commissioning the PTT service:

1. Open Call Observation Subsystem to observe the terminals’status of making PTT call.

2. Open Signaling Trace Subsystem and select to trace IMSI, inputthe IMSI of the caller to trace it’s signaling.

3. Use the PTT caller terminal to initiate private call and group calland check the call set up process.

4. Check whether BSC sent the A1r_CMServiceRequest messageto MSC. If yes, do the following if MSC initiates call release orfails to send the A1f_AssignmentRequest message to BSC:

i. Check whether MSC have received the service request sentfrom BSC.

ii. Check the BSC version is compatible with MSC version.

iii. Check data configuration in MSC.

iv. Check if PTT service call authority has been granted in HLRfor the terminal.

v. Check the consistency of connection related data betweenBSC and MSC.

vi. Check the consistency of SID, NID, LAC, CI and authenti-cation mode between BTS and MSC.

vii.Check whether the service option, IMSI, SID, NID, LAC andCI sent along with the service request are correct.

5. If BSS hasn’t sent service request to MSC, or it hasn’t sentA10drPTTCallRequest to PDS, or resource allocation fails afterthe service request is sent, then do the following:


ii. Check whether the MDM process is configured on the BTSside, and the modification of BSC MDM process after theconfiguration of BTS MDM process. If modified, then deleteBTS MDM process and configure again.

iii. Check whether the BTS signaling flow is through to BSC,if no, check BTS hardware/software and control channelconfiguration.

iv. If it is because of BTS resource allocation failure, then checkthe CE and BTS carrier resource, status of search window,cell radius and clock system.

v. If it is because of SE allocation failure, then check all BSC1XSDU resource is blocked and if board hardware/softwareis in normal condition.

6. Check whether the BSC sent A10drPTTCallRequest message toPDSN. If yes, do the following:

i. Check the PDS received the service request sent from BSC.

ii. Check if BSC version is compatible with PDS version.

iii. Check data configuration in PDS, PHR and DAS.



iv. Check whether PTT service call authority has been grantedin PHR and DAS for the terminal and the IMSI is correct ornot.

v. Check the consistency of connection related data betweenBSC and PDS.

vi. Check if service option and IMSI, sent along with the ser-vice request are correct.

1xEV-DO ServiceCommissioning

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 theUser name and password for number dialing.

8. Set the PC connected to the test terminal for number dialing.


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 itssignaling.

3. Use the PTT caller terminal to initiate private call and group calland check the call set up process.

4. Check whether BSC sent A1r_CMServiceRequest message toMSC. If yes, do the following if MSC initiates call release orfails A1f_AssignmentRequest message to BSC:

i. Use dialup connection of the PC to initiate a data servicecall 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 settingof 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 terminalMODEM 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.



7. Check whether the BSC sent A12r_AccessQuest message toAN-AAA. If yes, do the following:

i. Check the AN-AAA received the service request sent fromBSC.

ii. Check the BSC version is compatible with AN-AAA version.

iii. Check data configuration in AN-AAA.

iv. Check the consistency of NAI and PASSWORD between theterminal and AN-AAA.

v. Check the consistency of connection related data betweenBSC and AN-AAA.

vi. Check if service option, IMSI, NAI and PASSWORD sentalong with the service request are correct.

8. If BSS has not sent service request to AN-AAA, or it has notsent A11-RegistrationRequest to PDSN, or resource allocationfails after the service request is sent, then do the following:


ii. Check whether the MDM process is configured on the BTSside, and further check the MDM process is modified af-ter the BTS MDM process is configured. If modified, thendelete MDM process of BTS and configure it again.

iii. Check whether the BTS signaling flow is through to BSC,if no, check BTS hardware/software and control channelconfiguration.

iv. If it is because of BTS resource allocation failure, then checkthe CE and carrier resource of BTS, status of search win-dow, cell radius and clock system.

v. If it is because of SE allocation failure, then check all BSCDOSDU resource and board hardware/software is in normalcondition.

vi. Check if GCM of BSC and BTS has hardware or softwareproblem.

9. Check whether the BSC sent A11-RegistrationRequest mes-sage to PDSN. If yes, do the following if PDSN initiates callrelease or fails to send the A11-RegistrationReply message toBSC:

i. Check the PDSN received the service request sent fromBSC.

ii. The BSC version is compatible with PDSN version.

iii. Check data configuration and version of PSDN and PDSN-AAA.

iv. Check the consistency of NAI and PASSWORD between theterminal and AN-AAA.

v. Check the consistency of connection related data betweenBSC and AN-AAA.

vi. Check if service option, IMSI, NAI and PASSWORD sentalong with the service request are correct.

vii.Check whether data service call authority has been grantedin PDSN-AAA and the IMSI is correct or not.



viii.Check the consistency of connection related data betweenBSC and PDSN.

ix. Check if service option and IMSI sent along with the servicerequest are correct.


Figures

Figure 1 General Commissioning Flow of CDMA BSSB .............. 2

Figure 2 BSC Commissioning Workflow .................................. 4

Figure 3 Commissioning Preparation Stages ........................... 6

Figure 4 BSC DIP Switch Settings ........................................10

Figure 5 TRIBID Setting .....................................................11

Figure 6 RACK_ID Setting...................................................11

Figure 7 OMP Booting.........................................................18

Figure 8 OMP Boot Mode Selection .......................................18

Figure 9 Configuration Selection of OMP ...............................19

Figure 10 Setting OMP IP Address........................................19

Figure 11 Setting OMP Startup Mode ...................................20

Figure 12 Setting Bureau No. ..............................................20

Figure 13 Opening Version Management Window ...................21

Figure 14 Adding Version....................................................22

Figure 15 Selecting a Version File ........................................22

Figure 16 Adding a Version .................................................23

Figure 17 Version Addition Result.........................................23

Figure 18 Configuring OMP Version ......................................24

Figure 19 OMP Version Configuration....................................24

Figure 20 Selecting a Backup OMP Version ............................25

Figure 21 Configuring OMP..................................................25

Figure 22 Creating Information File for OMP with 755 Series

Chip ................................................................27

Figure 23 Creating Information File for OMP with 85 Series

Chip ................................................................28

Figure 24 Synchronizing OMP Data.......................................29

Figure 25 Save Control.......................................................29

Figure 26 Saving OMP Data.................................................30

Figure 27 Activating Version................................................31

Figure 28 Common Activation Window..................................31

Figure 29 Activate Version Dialog Box...................................32

Figure 30 Selecting Backup Version......................................33

Figure 31 Selecting a Board to Be Activated ..........................34

Figure 32 Resetting Board...................................................35



Figure 33 Querying Version.................................................36

Figure 34 Querying Running Version.....................................36

Figure 35 Version Query Result............................................37

Figure 36 Selecting Board...................................................38

Figure 37 Starting Board Test..............................................38

Figure 38 Selecting a Media Stream Test Source Board ...........39

Figure 39 Selecting a Media Stream Target Board ..................40

Figure 40 Starting a Media Stream Test ................................40


Tables

Table 2 Multi-meter Probes Usage ........................................10

Table 3 DIP Switch Description of BSCB Service Subrack

Backplane.........................................................10

Table 4 MULTI-METER PROBES USAGE..................................13


Sjzl20091753-ZXC10 BSSB (v 8.0.2.004) CDMA2000 Base Station System Commissioning Manual

Documents

Transcript of Sjzl20091753-ZXC10 BSSB (v 8.0.2.004) CDMA2000 Base Station System Commissioning Manual