6.ZXSDR B8200(V4.1) Commissioning Guide 109p

ZXSDR B8200 (V4.1) Project Commissioning Guide

=;6'5%9 3URMHFW&RPPLVVLRQLQJ*XLGH

TABLE OF CONTENTS 1

B8200 System NE Connection Relationship.................................................. 1

2

B8200 System Commissioning Work Flow Chart ......................................... 1

3

Cautions for Commissioning .......................................................................... 2

4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.2 4.2.1 4.2.2 4.3 4.4

Preparations for Commissioning ................................................................... 3 Preparations at BS ............................................................................................. 3 Tools for BS Equipment ..................................................................................... 3 Software for BS Equipment ................................................................................ 4 Installation Quality Inspection for BS Equipment ............................................... 5 Double Check before Powering on BS Equipment............................................. 5 Preparations at OMC ......................................................................................... 6 OMC Hardware Preparation ............................................................................... 6 OMC Software Preparation ................................................................................ 6 Transmission Preparation .................................................................................. 6 Other Preparations ............................................................................................. 7

5 5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.2.8 5.3 5.3.1 5.3.2 5.3.3 5.4 5.4.1 5.4.2 5.5 5.5.1 5.5.2 5.5.3 5.5.4 5.6 5.7 5.8 5.8.1

Commissioning Process ................................................................................. 7 OMC Configuration Data Backup ....................................................................... 7 Data Configuration at OMC ................................................................................ 9 Data Configuration Work Flow ........................................................................... 9 Prepare Data for Configuration ........................................................................ 10 Configure Network Overall Data ...................................................................... 11 Configure District .............................................................................................. 16 Configure WBTS SDR B8200 .......................................................................... 17 Physical Configuration ..................................................................................... 18 Radio Configuration ......................................................................................... 31 Configure WBTS Status ................................................................................... 43 BS Equipment Power-on & Power-off .............................................................. 44 Power-on .......................................................................................................... 44 Power-off .......................................................................................................... 45 Post-power-on Check ....................................................................................... 45 Synchronize and Save Data between OMC and BS ........................................ 45 Synchronize Data ............................................................................................. 45 Save Data ........................................................................................................ 47 BS Software Version Downloading .................................................................. 49 Version Management ....................................................................................... 49 Add Version ...................................................................................................... 50 Deliver Version ................................................................................................. 52 Activate Version ............................................................................................... 55 Validate Version ............................................................................................... 57 Query Version Query ....................................................................................... 58 Link Test with Pinging ...................................................................................... 60 Test premix： ................................................................................................... 60

ZTE Confidential Proprietary

© 201 ZTE CORPORATION. All rights reserved.


5.8.2 5.8.3 5.9 5.9.1 5.9.2 5.9.3

Acceptance Criteria .......................................................................................... 60 Test Steps ........................................................................................................ 60 BS Information Record ..................................................................................... 61 BBU Board Configuration Record .................................................................... 61 RRU Board Configuration Record .................................................................... 62 BS Software Version Record ........................................................................... 62

6 6.1 6.2 6.3 6.4 6.5 6.6

Add NE ............................................................................................................ 64 Export NE Data ................................................................................................ 64 Add a New NE .................................................................................................. 66 Add New NEs by Batch .................................................................................... 72 Import NE Data ................................................................................................ 79 Import NE Data by Batch ................................................................................. 82 Example of Importing NEs by Batch ................................................................ 88

7

MPIM IP Planning ........................................................................................... 98

8

XBP IP Planning ............................................................................................. 99

9

BSID Configuration Principle at BTS side ................................................... 99

10 10.1 10.2 10.3

5M / 7M / 10M / 10/3M Networking Configuration ...................................... 100 Premix: ........................................................................................................... 100 Configuration Summary ................................................................................. 100 Configuration Steps ........................................................................................ 100

Appendix : Abbreviations .............................................................................................. 106



6


1

B8200 System NE Connection Relationship The connection relationship among NE and NE boards within B8200 system is shown in Figure 1-1 Figure 1-1 Connection Relationships among NE and NE boards within B8200 System

2

B8200 System Commissioning Work Flow Chart Figure 2-1 Network Commissioning Work Flow Chart



1


3

Cautions for Commissioning During commissioning, pay attention to the following instructions: 1.

Wear antistatic wrist strip when plugging, unplugging or checking the module.

2.

In handling a module, strictly follow the related specifications. Handle the modules with care and for those modules that are not used at the moment or that need to be stored, pack them with antistatic bags and keep them in proper places.



2


3.

The co mmissioning pe rsonnel shoul d compl etely prep are related tech documents.

4.

Do not delete the OMC folder and the file s in it; otherwi se, the modification of the installation and future upgrade will be affected. The OMC folder is in the directory of C:\Documents and Settings\All Users\.

4

Preparations for Commissioning

4.1

Preparations at BS

4.1.1

Tools for BS Equipment

nical

Before powering on the BS equipment, prepare necessary tools, such as network cable, screwdrivers and multimeter. The special cables that may be used in commissioning are illustrated in Figure 4-1 Figure 4-1 Special Cables for Network Commissioning



3


4.1.2

Software for BS Equipment Before powering on the BS equipme nt, check and confirm the correct software versions for BBU and RRU boards are available. The software types for each board of B8200 and RRU are listed in Table4-1. Check the version of each type of software. Table 4-1 BSS Software Type & Version Confirmation Equipment Type

Board Type

Software Type

Version Number

Remarks

CC CPU EPLD BOOT XBP CPU EPLD BOOT MMC MMCBOOT SA DSP EPLD FPGA

B8200

BOOT MMC MMCBOOT SE MCU EPLD FPGA BOOT MMC MMCBOOT PM

MMC MMCBOOT CPU

WCTR/WPTR RRU

BOOT EPLD

WDPA CPU BOOT Note: * It is quite important to ensure software versions of the above BSS boards to be consistent with OMC software version. Copy software with special cables in case ZTE Confidential Proprietary


4


Equipment Board Type Software Type Version Number Remarks Type it is necessary. * Add other board types in case this table hasn’t include all board types in a real case.

4.1.3

Installation Quality Inspection for BS Equipment To guarantee a smooth commissio ning proc ess and a prope r op erating e nvironment conditions for BS equipment, before po wering on BS equipme nt, it is requi red to che ck the equip ment installation quality, incl uding whether cable connection quali ty meets requirements, whethe r e quipment groundi ng me ets the sp ecifications, wheth er equipment p ower su pply meets the specifications, etc. Only after installatio n quality is successfully accepted, can the equipment be commissioning be started. Check the In stallation quality according to the in spection items depicted in En gineering Installation Inspection & Acceptance Report: Such as: 1.

Check wh ether BS eq uipment in stallation env ironment meets requirements. E.g. Indoor installation environment inspections include inspections on equipment power supply conditio n, grou nding condition, ai r co nditioning and lig hting conditions;

2.

Check whether BS equipment installat ion complies with related safety regulation s as a whole;

3.

Check whether cables are correctly connected;

4.

Check whether cables are laid in accordance with related specifications;

5.

Check whether cabinets are properly installed;

6.

Check whether antenna feeder system is correctly installed;

7.

In case of indoo r install ation, che ck to see if material remai removed from the equipment room and if the cabinet is clean.

nders have been

8. ……

4.1.4

Double Check before Powering on BS Equipment 1. Measure the resistance of BBU cabinet; 2. Measure the DC voltage of BBU/RRU, maki ng sure they are within the allowed range (i.e. -40 V ~ -57 V).



5


3. Check the conne ctions of power ca ble and gro unding cable of RRU cabinet , making sure they are correct. 4. Check the power plug of RRU cabinet to see if it is disconnected.

Note: The internal cables and modules of BBU cabinet have been assembled before the cabinet leaves the factory. Therefore, it is not required to check them again.

4.2

Preparations at OMC

4.2.1

OMC Hardware Preparation Check OMC server computers and client computers to see if the y work well a nd meet related requirements.

4.2.2

OMC Software Preparation Check OMC software as follows: 1. Main

Software

Before power-on, prepare main software (the software for OMC servers, OMC Clients) of correct version 2. Suppo

rtive Software

Check software a s the d atabase, co mputer operating syste m and antiviru s soft ware provided alo ng with th e equipment a nd ma ke sure the versio n gen uineness of all software.

4.3

Transmission Preparation Before p ower-on, ch eck t ransmission equipment h ardware a nd make sure they are available for use. (After commissioning, transmission system should also pass on-off-power test to ensure the transmission connection quality. In this case, an Ethernet analyzer is used to do the test at both e nds of the transmi ssion system. If the Ethernet a nalyzer is not a vailable, ping the two ends of the transmission to see if there is any delay or jitter.)



6


4.4

Other Preparations Site Information Learn the site location, commissioning-related persons and their contact information.

5

Commissioning Process

5.1

OMC Configuration Data Backup OMC default/existing configuration data should be backed up before new configuration. The steps for backing up configuration data go as follows: 1. Log

on OMC Client interface.

2. Select Views --> Configuration Management from the men Configuration Management window. See Figure 5-1

u to open t

he

Figure 5-1 Open Configuration Management Window

3. Click Configuration Management menu in the Configuration Management window, select Data Backup and Restore from the pop-up menu. See Figure 5-2 Figure 5-2 Configuration Management Window ZTE Confidential Proprietary


7


4.

Data Back and Restore Menu pops up. See Figure 5-3

Figure 5-3 Data Backup and Restore Interface



8


5.

In the Data Backup a nd Restore i nterface (Fig ure 5 -4), click Backup button. The Backup dial og box (Figu re 5-5) will a ppear, wh ere y ou input the backu p data file name and click OK.

Figure 5-4 Backup Dialog Box

6.

Upon co mpletion of config uration data backup, a messag e (Fig ure 2-6) p ops up, prompting you the path of the backup data file.

Figure 5-5 Backup Completion Prompt

7.

Finally, click OK to finish the backup configuration.

5.2

Data Configuration at OMC

5.2.1

Data Configuration Work Flow Figure 5-6 Data Configuration Work Flow Chart



9


5.2.2

Prepare Data for Configuration OMC data configuration is based on proje ct su rvey and project network pl Configuration data to be prepared are listed in three categories as follows: 1.

Overall network configuration data 

AGW basic information



Downlink frequency(provided by network planning engineers)



Paging Group (provided by network planning engineers)

 OMM 2.

anning.

IP

District configuration data



10


3.

WBTS Physical configuration data 

WBTS physical parameter



AGW static route



BBU and RRU board basic information

Note: It sho uld be known t hat the AG W static route should b e co nfigured befo re B82 00 XBP board IP address. 4.

Radio configuration data

Cell information, carrier inf ormation ,segment information, segment AGW Information , TRX board link information 5.

BTS status configuration data

6. Other

configuration data for commercialized project

 Preambl  FA_Index  UL

、Segment ID、

 Central

5.2.3

、

Permbase

 BSID



e Index、

Frequency

Foreign BS (provided by network planning engineers)

Configure Network Overall Data 5.2.3.1

Configure AGW Basic Information

Configuration premix: Enter OMC Vi configuration tree

ew---> Configuration Ma nagement--->Open the

Configuration steps: 1. Log on OMC Client. 2. Select

Views --> Configuration Management from the menu bar to open the

Configuration Management interface. 3. Click “O MM_WiMAX” n ode in the ZTE Confidential Proprietary

left configuration tree


to open the 11


configuration View 4. Select the AWG tab page, as shown in Figure 5-7. Figure 5-7 Network Overall Configuration-Add AGW-Start

5. Click “Data Process” or cli ck

,--->Select “Edit Mode” as sho wn in Figure

5-8. Figure 5-8 Network Overall Configuration-Add AGW - Process

6. Double Click a existing AGW record to pop out “ Add AGW “ interface--->Add a new AG W Alias an d a new A GW IP addre ss with othe r para meters intact--->click “OK ” t o co mplete co nfiguration of AGW ba sic informatio n, a s shown in Figure 5-9. Figure 5-9 Network Overall configuration-Add AGW -Completed ZTE Confidential Proprietary


12


5.2.3.2

Configure OMM IP



Configuration steps: 1. Log on OMC Client. 2. Select Views --> Configuration Management from the me Configuration Management interface.

nu ba r to open th

e

3. Click “OMM_WiMAX” node in the left configuration tree to open the configuration View 4. Select the OMM IP tab page, as shown in Figure 5-10. Figure 5-10 Network Overall Configuration-Add OMM IP -Start



13


5.

Click “Data Process” or click

6.

Double Click a existing OMM IP record to pop out “ Add OMM IP “ interface--->fill in Index and OMM IP--->click “OK” to complete configuration of OMM IP, as shown in Figure 5-11.( the OMM IP should already exists and sho uld be the same as the IP of the server computer. )

Figure 5-11

5.2.3.3

,--->Select “Edit Mode”.

Network Overall Configuration-Add OMM IP - Completion

Configure DL Frequency



Configuration steps: 1. Log on OMC Client. 2. Select Views --> Configuration Management from the menu ba r to open the Configuration Management interface. 3. Click “O MM_WiMAX” n ode in the left configura configuration View ZTE Confidential Proprietary

tion tree to open the


14


4. Select the “Downlink Frequency” tab page, as shown in Figure 5-12. Figure 5-12 Network Overall Configuration-Add Downlink Frequency -Start

5. Click “Data Process” or click

,--->Select “Edit Mode”

6. Double Cli ck an existing OMM IP record to pop o ut “Downlin k Freque ncy” interface--->fill in the “ downlink fre quency” paramete r get from network plan ning engineers. See Figure5-13. Figure 5-13 Network Overall Configuration-OMM IP Configuration- Completion

5.2.3.4

Configure Operator ID Configuration premix: Enter OMC Vi configuration tree


Configuration steps:



15


1. Log on OMC Client. 2. Select Views --> Configuration Management from the menu ba r to open the Configuration Management interface. 3. Click “O MM_WiMAX” n ode in the left configura configuration View

tion tree to open the

4. Select the “NSP” tab page, as shown in Figure 5-14. Figure 5-14 Network Overall Configuration-OMM IP Configuration- Completion

5.2.4

Configure District Configuration Steps: 1. Log on to OMC Client. 2. Select


Configuration Management interface.Unfold the configuration tree in the left of the Config uration Man agement interf ace. Rig ht cli ck on O MM_WiMAX nod e and select Add District from the pop-up menu, as shown in Figure 5-15 Figure 5-15 Select “Add District “Option



16


3. In the Add Di strict interface that displa ys, select District (starting from 1), and input the ali as. Cli ck OK button to fini sh the ope rations, a s shown in Figure 5-16. Figure 5-16 “Add District” Interface

5.2.5

Configure WBTS SDR B8200 Configuration Premix: The “Dist rict” n ode sh ould ha ve been crea ted in the co nfiguration tree of the Configuration Management interface: Configuration steps: 1. Log on the network management client. 2. Select

Views --> Configuration Management fro m the menu b ar to open t he

Configuration Management interface. 3. Unfold the configuration tree in the left of the Configuration Ma nagement interface. Right click o n the Di strict node and select Add S DR from the pop-up m enu, a s shown below. Figure 5-17 Select “Add SDR” Option ZTE Confidential Proprietary


17


4. In the Add BTS(SDR B8200) interface that displays, select system ID (starting from 2001), and i nput sy stem alias. Th en click OK butto n to finish th e ope rations, as shown in Figure 5-. Figure 5-18 “Add BTS(SDR B8200)” Interface

5.2.6

Physical Configuration 5.2.6.1

Configure BBU Rack

Configuration premix:” District” an d “SDR” no des sho uld h ave bee n crea ted in the configuration tree of the Configuration Management interface: ZTE Confidential Proprietary


18


Configuration steps: 1.

Log on to OMC Client.

2. Select Views --> Configuration Management f rom the men u b ar to o pen the Configuration Management interface. 3.

Unfold the configuration tree in the le ft of the Config uration Management interface and select the Physical Configuration node under B8200.

4.

Right click on the Physical Configuration node and select Add BBUB Rack from the pop-up menu, as shown below.

Figure 5-19 Select “Add BBUB Rack” Option

5. In the Add BBUB Rack interface that displays, select BBUB Rack in t he Rack Type field and click OK button to finish the operations, as shown in Figure 5-. Figure 5-20 “Add 8200 W100 Rack” Interface



19


5.2.6.2

Configure BBU Board

Configuration Premix: The BBU rack has already been configured. Configuration steps: 1. Log on the OMC Client. 2. Select

Views --> Configuration Management from the menu ba r to open the

Configuration Management interface. 3. Unfold th e configuration t ree in th e l eft of the Configuration

Management

interface to find the BBU Ra ck node and click it. Th en the BBU Ra ck diagram will be displayed in the right of the interface. 4. Right click on a blank slot in the BBU Rack diagram and select a correct board type from the pop-u p menu to configur e a board in the corresponding slot, as shown below. Figure 5-21 “Add Board” Option

Figure 5-22 Add Board



20


Note: 1. In adding XB P boards, the system first adds a g roup of the boa rds by default. Then the XBP parameter configuration in terface pops up, enabl ing the proper parameters to be set. 2. The CCA is a controlli ng board, so it mode. 3.

5.2.6.3

must be conf igured in active/standby

The boards can be added in any order.

Configure Physical Parameter

Configuration steps: 1. Log on to OMC Client. 2. Select


Configuration Management interface. 3. Unfold the configuration tree in t

he left of the Configuratio

n Manag ement

interface to find the Physi cal Configuration node and click it. Then the Physical Configuration interface will be displ ayed in the right of the in terface, as sh own below. 4. Set each pa rameter in the physical parameter tab p age and the n click the button in the tool bar to save the modifications. Figure 5-23 Physical Configuration Interface-physical parameter



21


5.2.6.4

Configure AGW Static Route

Configuration premix: physical parameter tab page has already been configured. Configuration Steps: 1.


2. Select Views --> Configuration Management from the men u bar to open the Configuration Management interface. 3. Unfold the co nfiguration tree in the left of the Config uration Man agement interface to find the Physical Configuration node and click it. Then the Physical Configuration interface will be displayed in the right of the interface, as shown in Figure 5-23 4.

Select “Static Route” tab page, as shown in Figure 5-24

Figure 5-24 Physical Configuration Interface- Select “Static Route” Tab Page

5.

Right cli ck th e yellow bar unde r Static Route tab pa ge to move out” Add Static Route” dialog ue box, set each para meter in the dialogue box, and pre ss OK to confirm the setting, as shown in Figure 5-25

Figure 5-25 Physical Configuration Interface-“Add Static Route” dialogue box



22


6.

Parameter configuration in “Add Static Route” dialogue box is completed, as shown in Figure 5-26. (Several static routes can be added at once.)

Figure 5-26 Physical Configuration Interface-“Add Static Route” is Completed

5.2.6.5

Configure CCA Board External IP

Configuration premix: CCA board has already been added. Configuration steps: 1.

Log on OMC Client.

2. Select Views --> Configuration Management f rom the men u b ar to o pen the Configuration Management interface.



23


3.

Unfold the configuration tree in the le ft of the Config uration Management interface to find the BBU Rack no de and cli ck it. Then the BBU Rack diagram will be displayed in the right of the interface.

4.

Right cli ck o n CCA boa rd in the BB U Ra ck dia gram and sel ect Config ure BT S External IP from the pop-up menu, as shown below.

Figure 5-27 B8200 Physical Configuration -CCA Board External IP

5.

After the Configure BTS External IP interface displays, set external IP, IP mask and next hop and click OK button to close the interface.

Figure 5-28 B8200 Physical Configuration-CCA Board External IP

Note:



24


1. IP address of CCA must be the IP address shown in NetNumen for B8200 and it must be unique in the network managed by NetNumen. 2. Next hop must be in the same segment with CCA external IP but they must notbe the same. 3. Only one piece of CCA board needs IP configuration. The rest of the CCA boards will automatically adopt the configured IP.

5.2.6.6

Configure XBP Board Parameters

Configuration premix: XBP board has already been added. (Note t hat BBU and RRU are connected via XBP board. One XBP board can be connected with several RRUs. Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the BBU Rack node and click it. Th en the BBU Rack diagram will be displayed in the right of the interface. 4. Right click on XBO board i n the BBU Rack diagram and select Configure XBP Parameters from the pop-up menu, as shown below. Figure 5-29 BBU Basic Information Configuration-XBP parameters

5. After the Con figure WBPM Parameters interface displays, set the parameters and click OK button to close the interface. Figure 5-30 BBU Basic Information Configuration-XBP parameters ZTE Confidential Proprietary


25


5.2.6.7

Configure XBP Board R6 IP

Configuration steps: 1.



Unfold the configuration tree in the le ft of the Config uration Management interface to find the BBU Rack no de and cli ck it. Then the BBU Rack diagram will be displayed in the right of the interface.

4.

Right click on XBO board in the BBU Rack diagram and select Configure XBP R6 IP from the pop-up menu, as shown in Figure 5-31

Figure 5-31 Physical Configuration Interface- XBP R6 IP



26


5.

After the Co nfigure MPXM External IP interface displays, set the parameters and click OK button to close the interface.

Figure 5-32 Physical Configuration Interface- XBP R6 IP

Note: 1. Next hop must be in the same segment with XBP R6 IP and Next hop must be different from XBP R6 External IP. 2. Next hop depends on AGW IP address and AGW Static Route. 3. XBP Next hop here should not be modified.

5.2.6.8

Configure RRU Rack

Configuration premix: 1.

District node has been created.

2.

B8200 node has been created in the configuration tree;

Configuration steps: 1. Log on OMC Client. 2. Select




n Manag ement

interface and select the Physical Configuration node under B8200. 4. Right click on the Physical Config uration node and sel ect Add RRU Rack from ZTE Confidential Proprietary


27


the pop-up menu, as shown in Figure 5-33. Figure 5-33 “Add RRU Rack” Option

5. In the Add RRU Rack interface that displays (Figure 5-34), set such parameters as WBPM un it, WBPM po rt and subsystem a nd click OK b utton to finish the operations. Figure 5-34 Add RRU Rack Interface



28


5.2.6.9

Configure RRU Board

Configuration premix: RRU rack has been configured. Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the RRU Ra ck node and click it. Then the RRU Ra ck diagram will be displayed in the right of the interface. 4. Right cli ck on a blank slot in the RRU Rack diag ram and sel ect Add WTRX Board from the pop-up menu to configure a board in the corresponding slot, as shown in Figure 5-35 and Figure 5-36 Figure 5-35 Add RRU Board

Figure 5-36 Add RRU Board



29


Note: In adding WTRX board, the Configure TRX Parameters interface will display, where you can set the parameters.

5.2.6.10

Configure TRX Board Parameters

Configuration premix: RRU rack and TRX board have already been configured. ( Note that there a re two ways to con figure T RX param eters: when the WT RX boa rd is added an d after the board is added. Here the second one is discussed.) Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the RRU Ra ck node and click it. Then the RRU Ra ck diagram will be displayed in the right of the interface. 4. Right click on WPTR board in the RRU Rack diagram and select Configure TRX Parameters from the pop-up menu, as shown in Figure 5-37 Figure 5-37 Configure TRX Parameters Option



30


5. After the Co nfigure TRX Parameters i nterface (Fig ure 5 -38) di splays, set the parameters and click OK button to close the interface. Figure 5-38 Configure TRX Parameters Interface

Note: If 2 * 4 RFs have to be configured, the antenna mode should be set as 2T4R, which means 2 transmitters and 4 receivers.

5.2.7

Radio Configuration 5.2.7.1

Configure Cell

Configuration premix: SDR B8200 exists in the system. ZTE Confidential Proprietary


31


Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the Radio Configuration node under B8200. 4. Right click on Radio Configuration node and sel ect Add Cell fro m the pop-u p menu, as shown in Figure 5-39 and Figure 5-40. Figure 5-39 Radi o Configuration Node

Figure 5-40 Radio Configuration-Add Cell Option



32


5. The Cell node will be added under the Radio Configuration node. At the same time, the Cell interface will display in the right, as shown in Figure 5-41. Set the parameters in the Cell interface and click

button to save the modifications.

Figure 5-41 Cell Interface

5.2.7.2

Configure Carrier

Configuration premix: At least one cell has been configured. Configuration steps:



33


1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the Cell node under B8200, as shown in Figure 5-42 Figure 5-42 Cell Node

4. Right cli ck o n Cell nod e and sel ect Add Ca rrier from the pop-up menu. Th e Carrier node will be

added in the configuration tree. At the same time, the

Carrier interface will display in the right, as shown in Figure 5-43. Figure 5-43 Carrie r Interface



34


5. Set the parameters in the Carri er interf ace an d click

button to save the

modifications.

5.2.7.3

Configure Segment

Configuration premix: Carrier exists in the system Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the Carrier node under B8200. 4. Right click on Carrier node and select Add Segment from the pop-up menu. The Segment node will be added in the configuration tree, as shown in Figure 5-44. At the same time, the Segment interface will displ ay in the right, as shown in 5-45. Figure 5-44 Carrie r Node



35


Figure 5-45 Segment Interface

5. Set the para meters in the Segment interface and click

button to save the

modifications. Note that p arameters in each tab pa ge should be compl etely configured, otherwise, a Warning prompt box shown in Figure 5-46 will pop up. Figure 5-46 Warning Prompt Box

5.2.7.4

Configure AGW in Segment

Configuration premix: Segment exists in the system. Configuration steps: ZTE Confidential Proprietary


36


1.



Unfold the configuration tree in the le ft of the Config uration Management interface to find Segment node.

4.

Click AGW tab page in Segment interface on the right as shown in Figure 5-47.

Figure 5-47 AGW tab page in Segment interface

5.

Right click the blank yellow bar under AGW tab page, and select Add in the pop-up menu, as shown in Figure 5-48.

Figure 5-48 Add Segment AGW



37


6.

Select the target AGW and configu re re lated parameters in the pop-u p menu, as shown in Figure

Figure 5-49 Configure Segment AGW

5.2.7.5

Configure Port Link between XBP Board (BBU board) and TRX Board(RRU board)

Configuration premix: TRX board parameters have already been configured. Configuration steps: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the BBU Rack node and click it. Th en the BBU Rack diagram will be displayed in the right of the interface. 4. Right click on XBP board i n the BBU Rack diagram and select Configure Port Link from the pop-up menu, as shown in Figure 5-50. Figure 5-50 Select XBP Port Link



38


5. The Configure Port Link interface will display, as shown in.5-51 Figure 5-51 Select Target Port Link Between XBP Board and TRX Board

6. Right click on a target BBU-RRU port link record and select Set Port Link from the pop-u p menu; or sel ect a reco rd and then double cli ck it, the interface shown in Figure 5-52 will display.



39


Figure 5-52 Set Port Link between XBP Board and TRX Board

7. Select the RRU to be connected and click OK button to exit the interface. Then the status o f target port link in Co

nfigure Po rt Link interfa ce be comes

“Connected”. Note: RRUs can be cascaded. That is to say, one WBPM port can be connected to up to 4 RRUs, with these RRUs being connected in a cascaded way. The port whose connection has been configured will turn green.

5.2.7.6

Configure Port Link between TRX Board (RRU Board) and Segment

Configuration premix: 1.

TRX parameters have been configured.

2.

Segment has been configured.

3.

Port link between XBP and TRX has been configured.



40


Configuration steps: The steps for configuring connection between TRX and Segment are as follows: 1. Log on to OMC Client. 2. Select




n Manag ement

interface to find the RRU Ra ck node and click it. Then the RRU Ra ck diagram will be displayed in the right of the interface. 4. Right cli ck o n WPTR boa rd in t he RRU Ra ck dia gram and sele ct Configu re Connection b etween TRX and Segme nt from the pop-up me nu, as shown i n Figure 5-53. Figure 5-53 Select Configure Connection between TRX and Segment Option

5. The Configure Connection between TRX and Segment interface will display, as shown in Figure 5-54 Figure 5-54 Configure Connection between TRX and Segment



41


6. Select a re cord in the

boxes of Available T RX and Availa ble Segme nt

respectively and then click Connect button. The connection will then be shown in the box under “Connection which have been configured”, as shown in Figure 5-55. Figure 5-55 Conn ection between TRX and Segment Has Been Done



42


5.2.8

Configure WBTS Status Configuration premix: both physical and radio configuration have been compelted. Configuration steps: 1.


2. Select




n Manag ement

interface to find the District node and click it. NE Status tab page will display in the right. 4. Click the NE Status tab page, and select a BTS whose status is to be modified, as shown in Figure 5-56. Figure 5-56 NE Status Tab Page

5. Then right click on the re cord and se lect Modify BTS Status from the pop-up menu to enter the Modify NE Status inte

rface, as sho wn in Fig ure . In this

interface, modify the BTS status into “Commi ssioned but not commercial ” or “Commercial” and click OK button.



43


Figure 5-57 Modify NE Status

6. Finally, perform data synchronization and finish OMC configuration. Note: BTS status must be modified from “Not commissioned” into “Commissioned but not commercial” or “Commercial”. Otherwise, data synchronization and saving operations cannot proceed.

5.3

BS Equipment Power-on & Power-off

5.3.1

Power-on Caution: The equipment should not be powered on before the double check is made. Steps of Power-on: 1.

Switch on the external power supply.

2.

Connect the power cable of BBU cabinet to the external power supply.



44


5.3.2

Power-off Steps of power-off:

5.3.3

1.

Disconnect the power cable of BBU cabinet to the external power supply.

2.

Switch off the external power supply.

Post-power-on Check After equipment is powered on, check their power supply status by observing the power light indicator.( green light is continuously on) In case of any problem, power off the equipment right away and check the faults.

5.4

Synchronize and Save Data between OMC and BS

5.4.1

Synchronize Data Synchronization premix: 1.

The data have been completely and corrected configured.

2.

The link between the OMC and WBTS is through.

3.

The BTS status is “Commissioned but not commercial” or “Commercial”.

Note: data synchronization operation starts from software version validation in the each version table, followed by synchronize of all data. B8200 system can provide services normally after data synchronization. Synchronization steps: 1. Log on to OMC Client. 2. Select


Configuration Management interface. Unfold the configuration tree in the left of the Configuration Management interface to find the OMM_WiMAX node. Then right click on the node and select Data Synchronization from the pop-up menu, as shown below. The Data Synchronization interface will then display, as shown below.



45


Figure 5-58 Select Data Synchronization Option

Figure 5-59 Synchronize Data

In the left tree of this interface, select a proper network element and click the button in the tool bar. At the moment, a Confirm dialog box will pop up, as shown in 3. Figure 5-. Note that data synchronization can not proceed if no network element is selected.

Figure 5-60 Confirm Dialog Box ZTE Confidential Proprietary


46


4. Click OK in the Confirm dialog box to begin data synchronization. Note: If the link between the OMC and the selected network element is not through, or the data is virtually configured, timeout or link failure will be prompted, indication the data synchronization fails. On the contrary, if the link between the OMC and the selected network element is through, or the data is not virtually configured, data synchronization and delivery can be successfully done. button If data synchronization takes quite a long time, you can click the in the tool bar to stop the operation and check the link status. After the link is found normal, execute data synchronization again. The progress of data synchronization is displayed in the lower part of the Data Synchronization interface, as shown in 5. Figure 5-14. Figure 5-14 Data Synchronization Result

5.4.2

Save Data Data saving premix: 1.

The data synchronization has been completed.

2.

The link between the OMC and WBTS is through.

Data saving steps: 1. Log on to OMC Client.



47


2. Select




n Manag ement

interface to find the OMM_WiMAX node. Then right click on the node and select Save Cont rol from the p op-up menu, as shown i n Figure 5-15 . The Save Control interface will then display, as shown in Figure 5-16. Figure 5-15 Select Save Control Option

Figure 5-16 Save Control

4. In the left tree of the Save Control in terface, select a prop er network element and select “Save master data” in command box or click the

button in

the tool ba r. At the mome nt, a Conf irm dialog b ox will pop up, as shown in Figure 5-17. ZTE Confidential Proprietary


48


Note: Data control can not be performed if no network element is selected. Figure 5-17 Confirm Dialog Box

5. Click OK in the Confirm dialog box to begin data saving. 6. The progress of data savi ng is di splayed in the lo wer part of the Data Control interface, as shown in Figure 5-18. Figure 5-18 Save Control Result

5.5

BS Software Version Downloading

5.5.1

Version Management BBU softwa re versio ns a re downl oaded in the following o rder: add version --> deliver version --> activate version --> validate version. Before versions are updated, it is required to query current versions after BBU is powered on and compare them with the latest ones.



49


If there is nay change, update the current versions with latest ones. Software versions are saved in OMM server Software types of B8200 boards are listed below. Table 5-1 B8200 Version Types BOOT CPU CCA FCE MMC PM PSA SA TRWA_B TRWC_B TRWC_D WDPA WDPAW WPTR XBP CCA

5.5.2

DSP

√ √ √ √ √ √ √ √ √ √

√

√ √ √

√ √ √

FPGA

MCU

√ √ √ √ √ √

√ √ √

√ √ √ √ √ √

√ √ √

BOOT √ √ √ √ √ √ √ √ √ √ √ √ √

Add Version

This function is to add the versions in the directory rundata\zxcomc\cbwa\version into the version library. 1. Log on to OMC Client. 2. Select

View --> System Tools --> Version Management in the menu bar to

open the Version Management interface. 3. Select

Version Function --> Add Version from th e menu bar to display the

Add Version interface, as shown below. Figure 5-19 Add Version Interface



50


4. Select Add Version --> File into Library from the menu bar (or click the

or

button in the tool bar) to pop up the Select Version File interface or Version Package interface, as shown in Figure 5-20 and Figure 5-21． 5. Figure 5-20 Select Target Versions to be Added

Figure 5-21 Select Package for Added Versions

6. Select a version file o r a version package, and cli ck OK b utton to add this version file or version package into the version library, which will be displayed in ZTE Confidential Proprietary


51


the Add Version interface, as shown in Figure 5-69 and Figure 5-70.

Figure 5-22 Added Version File

Figure 5-23 Added Version Packages

5.5.3

Deliver Version Version delivery premix: versions have been added. Version delivery steps: 1. Log on to OMC Client. 2. Select


open the Version Management interface. 3. Select Version Function --> Deliver Version from the menu bar to display the



52


Deliver Version interface, as shown in Figure 5-24. Figure 5-24 Deliver Version

4. Select

Deliver Version --> Select Downloaded Version File or

Downloaded Version Package from t he menu b ar (or cli ck the button in the tool bar) to

Select or

pop up the Deliver Versi on File or Deliver Versi on

Package interface, as shown in Figure 5-25. 5. In the boxes under NE, Execution mode and Version File, select one or several records respectively and click Confirm button, as shown in Figure 5-72. Figure 5-25 Select Version Package to be Delivered



53


6. The sele cted record s will then be di splayed in th e list of Deli ver Version interface, as shown below. 7. Select one or several records and right click on them, and then select Download Version from the pop-up menu. The d ownloading result will be sho wn in the Details column, as shown below. Figure 5-26 List of Selected Version Files



54


5.5.4

Activate Version Version activation premix: The system has the saved version information. Version activation steps: 1. Log on to OMC Client. 2. Select


open the Version Management interface. 3. Select

Version Function --> Query Version from the menu bar to display the

Query Version interface, as shown in Figure 5-74. Figure 5-27 Query Version

4. Select

Query Version --> Query BTS Saved Version from the menu bar (or

click the

button in the to ol bar) to po p up the Query BS Save d Versi on

interface, as shown below. Figure 5-28 Query BS Saved Version



55


5. Check the consistency between version file records or version package records in the boxes and a standard version check list. If the records are consistent with the standard version check list, right cli ck the valid records and select Activate Version by Package, as shown in Figure 5-76. Figure 5-29 Query and Activate BS Saved Version

6. Right click on a record in the Saved Version Info tab page and select Common ZTE Confidential Proprietary


56


Activation from the pop-up menu. The activation result will be shown in the Task Status column in the Running Version tab page, as shown in Figure 5-77. Figure 5-30 Version Activation Result

5.6

Validate Version Version execution premix: 1.

The board versions have been activated.

Note: reset operation should be performed after board versions are activated so that the activated versions become valid. There are several forms of reset. Here we take forced reset for example. Version Validation steps: 1.


2. Selec t View --> Fault Management --> Alarm Management in the menu bar to open the Alarm Management interface. 3.

Unfold the alarm tree in the left of the Alarm Mana

gement interf ace to find a

rack node and click it. The corresp onding rack diagram will then di splay in the right. In the rack dia gram, right click on a boa rd that sup ports forced reset operation, and select Forced Reset from the pop-up menu. A confirm dialog box shown in Figure 5-78 will then pop up.



57


Figure 5-31 Confirm Dialog Box

4.

Click OK button to close the dialog box. Then you can observe the board to see if the reset operation is successful. If yes, it means the version becomes valid.

5.7

Query Version Query Version query premix: 1.

The system has running versions and saved versions.

Note: Version query enables the user to easily know the versions of a board. Here, we take example for running version query. Version query steps: 1.


2. Select View --> System Tools --> Version Management in the menu bar to open the Version Management interface. 3. Select Version Function --> Query Version from the menu b ar to display the Query Version interface, as shown in Figure 5-79. Figure 5-32 Query Version



58


4. Select

Query Version --> Query Running Version from the menu bar (or click the

button in the tool bar) to pop up the Query Running Version interface, as shown in Figure 5-80. Figure 5-80 Query Running Version

5.

The running version information can then be found in the Running Version Info tab page of the Query Version interface, as shown in Figure 5-81. Figure 5-33 Running Version Query Result



59


5.8

Link Test with Pinging

5.8.1

Test premix：

5.8.2

1.

The performance test environment is available.

2.

At least one terminal has connected with the system.

Acceptance Criteria 1. In case the signal quality meets the requirements, the packet loss rate of pinged packets (400 and 1500) is no more than 1%. 2. The packets delay at an even interval during pinging.

5.8.3

Test Steps 1. Get test environment and configuration information: Let the test terminal to access the system, obse rve and record the uplink/ downlink CINR and RSSI lines, uplink/downlink modulation/encoding schemes as well as backup system configuration data. 2. Obtain Ping test result: First, modify and the Ping script based on expected



60


test times, zo nes, len gth a nd parallelism of Ping packets; then run the script. Upon completion of runni ng, click any key to colle ct the test re sults and save the result file. 3. Repeat tests: Change test para meters a ccording to test requ irements and repeat the above test. After commissioning, it is required to back up the configuration data and generate an SQL file.

5.9

BS Information Record

5.9.1

BBU Board Configuration Record During BBU commissioning and configuration, basic equipment information (Figure 5-82 illustrates board configuration of a BBU) has to be recorded in a table such as Table 5-2. Figure 5-82 BBU Board Configuration

Table 5-2 BBU Board Configuration Information Record

Rack No.


Qty

Board Name

Board Function C C A

Central Controllin and Clock function

S E

Environmental Monitoring function

X B P

Baseband P rocessing function


g

61


S A

5.9.2

Alarm function

RRU Board Configuration Record

During BBU commissioning and configuration, basic equipment information illustrates board configuration of a RRU) has to be recorded in a table below. Figure 5-83 RRU Board Configuration

Table 5-3 RRU Board Configuration Information Record

Rack No.

Qty

Board

Board Description

Central Controlling function

5.9.3

BS Software Version Record

The purpose of collecting versions of BTS modules is to facilitate BTS maintenance. The steps for collecting BTS versions are as follows: 1. Select Version Query --> Query Running Version in the menu bar to pop up the Query Running Version interface. 2. Select a reco rd in the Systems and Boards boxes respectively and then click OK button. The running version of the selected board can be seen in the Running Version Info tab page of the Query Running Version interface, as shown in Figure 5-8. Figure 5-84 Query Result of Running Versions



62


3. Export the queried board information into Excel file and save the file.



63


6

Add NE

6.1

Export NE Data NE export steps: 1.

Choose Vie w—Configuration Mana gement to ent er Configu ration Man agement interface.

2. Right click OMM WiMAX i n the left nav igation tree a nd choo se Export NE Data from the pop-up menu to enter NE Data Export main interface, as shown in Figure 6-1. Figure 6-1 NE Data Export Main Interface

3.

Select nodes: You can check the box before a node in the navigation tree to select the node; click Select All button to select all nodes in the configuration tree; or click Deselect All to deselect all nodes.



64


4. Click Browse button to p op up an Open dialog box, where you can set the ex port file name and its path, as shown in Figure 6-2. Figure 6-2 Setting File Name and Path

Note: 

In the File Name text box, a default name is displayed, which is named by this rule:

Node Number_Date_Time.zip. 

The default path for the export file in the OMC client is as follows:

$NetNumen installation directory$\ums\ums-clnt\cdma\cmdata\btsdata\. The file name should not include such characters as\, /, :, *, ?, ", <, > and |. 5.

Upon setting, click OK button to return to the NE Data Export main interface.

6. In

the NE Data Export main interface, click Export to start the export. You can check the status d uring the export proce ss. Figu re 6-3 i s the in terface when the export is successfully done and the export file has been saved in the path you set. If the export fails, an error message will display accordingly.



65


Figure 6-3 Data Being Exported

6.2

Add a New NE Steps: 1.

Choose Vie w—Configuration Mana gement to ent er Configu ration Man agement interface

2. Right click OMM WiMAX in the left na vigation tree and ch oose Add Batch NEs from the pop-up menu to enter Add Batch NEs interface.



66


Figure 6-4 Add Batch NEs Interface

3.

In the Edit tab, click Open File button to pop up an Open dialog box, where you can select the file to be imported, as shown in Figure 6-5. The file to be imported can be the decompressed file that has been exported already, or the file saved and edited via interface.



67


Figure 6-5 Select File to be Exported

Note: The default import path is the same as t he export one, i.e. $ directory$\ums\ums-clnt\cdma\cmdata\btsdata\..

NetNumen in stallation

Before importing the file you select, make sure the file has been decompressed and only in this way can you find the file in Open dialogue box. 4.

Once you select the export file, click OK to return to the Add Batch NEs, where you can see a record in the table. Right click the record and choose Modify NE from the pop-up menu, as shown in Figure 6-6. Figure 6-6 Selecting Modify NE Option



68


5.

Modify NE interface displays, as shown in Figure 6-7 . Figure 6-7 Modify NE Data



69


6.

Modify the parameters as necessary and click OK to save the modifications.



70


Figure 6-8


Save Modifications


71


6.3

Add New NEs by Batch Steps: 1.

Choose View— Configuration Manag ement men u to enter Configuration Management interface.

2. Right click OMM_WiMAX in the left navigation tree to choose Add Batch NEs from the pop-up menu to enter Add Batch NEs interface.



72


Figure 6-9 Add Batch NEs Interface

3.

In the Edit ta b, click Open File button to pop up a n Open dialogue box, where you can select the template file to be imported. The template file to b e imported can be the decompressed export file or the configuration data edited in the Edit tab of Add Batch NEs interface, shown as the figure below.



73


Figure 6-10 Select the File to be Imported

Note： The default import path is the same as the export one, i.e. $NetNumen installation directory $\ums\ums-clnt\cdma\cmdata\btsdata\. Before importing the file you sele ct, make sure it has been decompressed as .xml file and only in this way can you see the file in the Open dialogue box. 4.

Once you select the export file, click OK to return to the Add Batch NEs interface, where you can see a record in the table. Right click the record and choose Add NE from the pop-up menu, as shown below.



74


Figure 6-11 Add Batch NEs interface

5. The

Add NE interface displays.



75


Figure 6-12 Add NE interface



76


6. Click OK to save the added NE data and return to Add Batch NEs interface, where you can see a new record in the table below. Figure 6-13 Save the Add NE



77


7. Click Save As button and an Open dialogue box pops up. In the box, you can set the file name and type. Figure 6-14 Setting File Name and Type

Note: Before clicking “Save As”, please delete the template file record. 8.

After the correct file name and type is typed or selected, click OK to save the data. A Message box will pop up, prompting you “Save file successfully”.



78


Figure 6-15 Data File Being Saved

6.4

Import NE Data Steps: 1.

After the conf iguration data are edite d, or if you open a data file in the Edit tab of Add Batch NEs interface, click Import Data button to directly import NE data.



79


Figure 6-16 NE Data Import Fail

2.

In importing data, the system first checks the data. If an erro r is found, a Warning message will pop up. Click OK in the Warning message box, you will see the error message, shown as below.



80


Figure 6-17 Erro r Message

3.

Make ne cessary modifi cations according to the Error message and click A pply button. The interface will pop up as below after data are successfully imported.



81


Figure 6-18 Data Being Imported

6.5

Import NE Data by Batch 1.

Choose Vie w—Configuration Mana gement to ent er Configu ration Man agement interface.

2. Right click OMM_WiMAX in the left na vigation tree and ch oose Add Batch NEs from the pop-up menu to enter Add Batch NEs interface. 3. Click Import File button and an Open dialogue box will pop up, select the files to be imported, as shown below.



82


Figure 6-19 Select Import Files

4. Then click OK. The selected files display in the Import file tab of Add Batch NEs interface.



83


Figure 6-20 Import Files Being Selected

5.

Click Import button to start the import. The system start data imp ort, as sho wn in Figure 6-21. If there i s an error, the fo llowing interface shown in Figure 6-22 will pop up. If there is no error, Figure 6-23 will show up.



84


Figure 6-21 Data Import Process



85


Figure 6-22 NE Data Error



86


Figure 6-23 Successful Data Import



87


Figure 6-24 Data Import Fail

6.6

Example of Importing NEs by Batch In the following section, we will take the ex ample of single-carrier 3-sector BT Ss at 10 MHz to explain how to add BTSs in a batch way. 1.

First, select one NE (here BTS [2048]), preferably one with optimized data.



88


2.

Export the data of the BTS to create a template file.



89


3.

Import the template file in the Add Batch NEs interface.



90


4.

Add new BTS (ID 2049) via the Add Batch NEs interface.

Note: Although District field is modifiable, a new NE cannot be generated with a new distri ct ID. As a result, make sure the new NE an d the BTS involved in the template are in the sam e district To use a new district, add the district ID in Configuration Management first and then modify it in the Add NE interface. The seven v alues in the blue ellipses in t he above figure should be uniq ue in the entire network; otherwise, a new NE fails to add. You can add 1 to the settings in the template as the settings for the new NE, as sho wn in the figure below.



91




92


5. Save

settings.

Note: Do not save the settings of the BTS with ID 2048 as this BTS already exists and it cannot be added.



93


6.

After the save operation is done, import new BTS, i.e. 2049.



94


7. In

the Add Batch NEs interface, click Import to execute data import.



95


8.

The figure below is the interface showing the data of B8200 2005 are successfully imported.



96


9.

After the import finishes, wait for dozens of seconds and click Refresh button in the toolbar. Th e new B82 00 2005 will appea r in the left navigations tre eo f Configuration Management interface.



97


Note: In the newly-added NE, connection relationships except AGW have been copied from the template. Hence, before the new NE is put into commercialization, you have to add AG W routing and signaling plane IP and change the status of NE to be “commercial”. Besides, such parameters as the central fr equency, bandwidth, FA index, Preamble ID of the new NE have to be modified as required.

7

MPIM IP Planning CCA board IP address is the IP address of B8200 displayed in OMC NetNumen software. There must be only one unique CCA board IP address for the whole network syste m (even if there are ma ny OMC serve rs). CCA Next Hop mu st be i n the sa me Segment with CCA IP, and the two must be totally different with each other. It is only necessary to configure IP address for one CCA board of B8200. The other CCA board will be automatically synchronized to have the configured IP address. T hus, CCA board IP need be configured within one site for only one time. CCA b oard MAC ad dress do esn’t ne ed config uration a s it is u niversally uni que a nd pre-configured in the equipment.



98


8

XBP IP Planning For the IP address of XBP, it is required to negotiate with persons at the core network. In any case, MPXP IP should be unique within the whole network system. The configuration time of XBP IP address depends on how many XBP boards there are. XBP board Next Hop i s the IP address of t he port connected with AGW (or the IP address of the router in a trip le-layer networking system); XBP Next Hop must be in the same Segment with XBP IP, and the two must be totally different with each other; XBP Next Hop depends on AGW IP address and AGW Static Route; XBP Next Hop cannot be randomly configured. It can only be chosen from the pre-defined parameter. CCA b oard MAC ad dress do esn’t ne ed config uration a s it is u niversally uni que a nd pre-configured in the equipment.

9

BSID Configuration Principle at BTS side At BTS side, the BSID should be configured on the following principle: The hexadecimal number: “00+XXX(serial number of the BTS)+X(Segment ID)”. Examples: 1.

2.

For No. 39 BTS, its BSIDs configured at the BTS side should be as follows: 

Segment 0: 00+039(serial number of the BTS)+0(Segment ID)= 000390







For No. 168 BTS, its BSIDs configured at the BTS side should be as follows: 










99


10

5M / 7M / 10M / 10/3M Networking Configuration

10.1

Premix:

10.2

Configuration Summary

In case of 5M, 7M or 10M networking, each sector occupies all subcarriers. In case of 3/10M networking, each sector occupies some of subcarriers (which are evenly shared by 3 sectors).

The following configurations have to be made before networking. 1. Physical Configuration:  WBPM

parameter

 WPTR

parameter

2. Radi o Parameters: 

Carrier: Ch annel phy sical band width, FFT si

ze, downli nk symbol

number/uplink symbol number and Tx/Rx gap 

Segment: DL PUSC used Subchannel bitmap, UL allocated subchannels bitmap

10.3

Configuration Steps 1. Config ure WPTR parameters For the parameters of BBU WPTR board, select correct bandwidth and antenna mode (2R2T or 2R4T), as shown in the figures below.



100


Figure 10-1 Config ure WPTR Parameters Option

Table 10-1 WPRT board parameter configuration reference table- bandwidth,Antenna Mode Networking Mode

Bandwidth

Antenna Mode

5M

5M

2R2T or 2R4T or4R8T

7M

7M

2R2T or 2R4T

10M

10M

2R2T or 2R4T or4R8T

10/3M

10M

2R2T or 2R4T or4R8T

Note: In addition, for 10/3M networking mode, it is required to configure 3 segments under a carrier node, as shown in Figure 9-2.



101


Figure 10-2 Radi o configuration in 10/3M networking mode

2. In the Carri er page, config ure chan nel band width, F FT size, do wnlink sym bol number/uplink symbol number and Tx/Rx gap, as shown below. Figure 10-3 Configuration In Carrier Page



102


Table 10-2 WPRT board parameter configuration reference table- channel bandwidth, FFT size, downlink symbol number/uplink symbol number and Tx/Rx gap

Networking Mode

Channel Bandwidth

FFT Size

Downlink Symbol number/uplink Symbol number

5M

40-5MHz

2-512

31:15 or 29:18

298

7M

80-10MHz 1-10

24

21:12

376

10M

80-10MHz 1-10

24

31:15

595

10/3M

80-10MHz 1-10

24

31:15

595

3. In Segment page, co

Tx/Rx Gap

nfigure DL PUS C use d Sub channel bitm ap and UL

allocated subchannels bit map, a s sho wn b elow. Except of 1 0/3M networkin g mode, the Segment DL PUSC and UL PUSC in other networking modes will be automatically configured without need of manual configuration. Figure 10-4 Configurations in Segment Page



103


Table 10-3 Segment Configuration Reference Table Networkin

DL PUSC

UL subchannels

UL subchannels

UL subchannels

g Mode

Subchannel

bitmap (Byte1~3)

bitmap (Byte4~6)

bitmap (Byte7~9)

0,0,0

0,0,0

bitmap 5M

21 255,2

55,1

7M

63 255,2

55,255

255,7,0 0,0,0

10M

63 255,2

55,255

255,7,0 0,0,0

10/3M

Seg0: 3 Seg1: 12 Seg2: 48

Sge0: 255,15,0 Seg1: 0,240,255 Seg2: 0,0,0

Seg0:0,0,0 Seg1:0,0,0 Seg2:255,7,0

Seg0:0,0,0 Seg1:0,0,0 Seg2:0,0,0

Note: In Segment configuration unde r 10/3 M netwo rking mode, UL P USC n umber is small. Thus FFB UL max.slot number shoul d be modified a bit smaller from 10(d efault) to 3 or 4(e.g.). Figure 10-5 Warning about UL maximum slot number for

Bit0~Bit5 stands for 1,2,4,8,16,32. Figure 10-6 DL PUSC subchannel bitmap



104




105


Appendix : Abbreviations WiMAX: Worldwide Interoperability for Microwave Access OFDM: Orthogonal-Frequency Division Multiplexing OFDMA: Orthogonal-Frequency Division Multiplexing Access AMC: Adaptive Modulation and Coding MIMO: Multiple-Input Multiple-Output MDHO: Macro Diversity Handover FBSS: Fast BS Switching MBB: Make Before Break BBM: Break Before Make HARQ: Hybrid Auto Repeat Request CC: Chase Combining IR: Incremental Redundancy CS: Convergence Sublayer MAC: CPS MAC Common Part Sublayer PS: Privacy Sublayer PAPR: Peak to Average Power Ratio PDU: Protocol Data Unit AAS: Adaptive Antenna System BBU: BaseBand Unit RRU: Remote Radio Unit ASN: Access Service Network AGW: Access Service Network GateWay UGS: Unsolicited Grant Service rtPS: real-time Polling Service ertPS: Extend real-time Polling Service nrtPS: non-real-time Polling Service BE: Best Effort SM: sleep mode IM: idle mode



106

6.ZXSDR B8200(V4.1) Commissioning Guide 109p

Recommend Documents