U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide_R.1

U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide R1.0

U_ST_ZXSDR(V4.09.21) U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide Internal Use Only ▲

LEGAL INFORMATION By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do not agree to the following terms, please notice that you are not allowed to use this document. Copyright © 2012 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This document docum ent conta contains ins propri proprietary etary infor information mation of ZTE CORPORATION CORPORATION.. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. and are regist registered ered tradem trademarks arks of ZTE COR CORPORAT PORATION. ION. ZTE ZTE’s ’s compa company ny name name,, logo and pro produc ductt nam names es ref refere erenced nced her herein ein are eit either her tra tradem demark arkss or reg regist istered ered tra tradem demarks arks of ZT ZTE E CORPORATION. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyone’s access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any marks appearing in the document. The design of this product complies with requirements of environmental protection and personal securit sec urity. y. Thi Thiss pro produc ductt sha shallll be sto stored red,, use used d or dis discard carded ed in acc accord ordanc ance e wi with th pro produc ductt man manual, ual, relevant contract or laws and regulations in relevant country (countries). This document is provided “as is” and “as available”. Information contained in this document is subject sub ject to con continu tinuous ous upd update ate wit without hout fur furthe therr not notice ice due to im improv proveme ement nt and upd update ate of ZT ZTE E CORPORATION’s CORPORATION ’s products and technologies.

ZTE CORPORATION NO. 55 Hi-tech Road South ShenZhen P.R.China 518057 http://dms.zte.com.cn (Technical Support) [email protected]

ZTE Confidential Pr Proprietary

© 2012 ZTE CORPORATION. Al All rights reserved.

I


LEGAL INFORMATION By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do not agree to the following terms, please notice that you are not allowed to use this document. Copyright © 2012 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This document docum ent conta contains ins propri proprietary etary infor information mation of ZTE CORPORATION CORPORATION.. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. and are regist registered ered tradem trademarks arks of ZTE COR CORPORAT PORATION. ION. ZTE ZTE’s ’s compa company ny name name,, logo and pro produc ductt nam names es ref refere erenced nced her herein ein are eit either her tra tradem demark arkss or reg regist istered ered tra tradem demarks arks of ZT ZTE E CORPORATION. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyone’s access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any marks appearing in the document. The design of this product complies with requirements of environmental protection and personal securit sec urity. y. Thi Thiss pro produc ductt sha shallll be sto stored red,, use used d or dis discard carded ed in acc accord ordanc ance e wi with th pro produc ductt man manual, ual, relevant contract or laws and regulations in relevant country (countries). This document is provided “as is” and “as available”. Information contained in this document is subject sub ject to con continu tinuous ous upd update ate wit without hout fur furthe therr not notice ice due to im improv proveme ement nt and upd update ate of ZT ZTE E CORPORATION’s CORPORATION ’s products and technologies.

ZTE CORPORATION NO. 55 Hi-tech Road South ShenZhen P.R.China 518057 http://dms.zte.com.cn (Technical Support) [email protected]

ZTE Confidential Pr Proprietary

© 2012 ZTE CORPORATION. Al All rights reserved.

I


Revision History Product Version V4.09.21

Document Version

Serial Number

R1.0

Reason for Revision First published

Author Date 2010-10-13

Document Version R1.0

ZTE Confidential Proprietary

Prepared by Zhao Lijie

Reviewed by Chen Taiming

Approved by Chen Taiming

© 2012 ZTE CORPORATION. All rights reserved.

II


About This Document Summary Chapter

Description

1 Description of Version Change

Changes in different versions

2 Introduction to Quick Data Configuration

Quick data configuration

3 Specifications for Template Template Filling

Specifications for template filling

4 Examples of Template Filling

Examples of template filling

5 Special Subject Subject for Quick Quick Data Configuration

Special subject for quick data configuration

Applicable Applicable to: UMTS UMTS NodeB NodeB comm commissioni issioning ng engine engineers ers



III

U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide Internal Use Only ▲

TABLE OF CONTENTS

1 Description of Version Change.....................................................................................1 1.1 ZXSDRConfTool (V2.8.0).................................................................................................1 2 Introduction to Quick Data Configuration....................................................................1 2.1 Brief Introduction.............................................................................................................. 1 2.2 Workflow.............................................................................................................. .............2 2.3 Data Conversion............................................................................................................... 3 2.3.1 Generating Configuration Data in Batch (XLS to XML) ..........................................3 2.3.2 Batch Offline Reverse (XML to M31)................................................................ ......5 2.3.3 Exporting NE Data in Batch (M31 to XML) .............................................................7 2.3.4 Converting Configuration Data in Batch (XML to XLS)...........................................9 2.3.5 Synchronizing Configuration Data on Site (XML to SDR)....................................10 3 Specifications for Template Filling.............................................................................11 3.1 Introduction to Templates...............................................................................................11 3.1.1 Classification of Templates...................................................................................11 3.1.2 Description of Each Sheet..................................................................................... 11 3.2 Specifications for Template Filling.................................................................................12 3.2.1 SubNetwork...........................................................................................................12 3.2.2 Base Station.......................................................................................................... 13 3.2.3 Equipment.............................................................................................................. 13 3.2.4 Time 16 3.2.5 Clock...................................................................................................................... 16 3.2.6 Transmission......................................................................................................... 17 3.2.7 Transmission(IP)........................................................................................ ...........18 3.2.8 Transmission(E1T1)..............................................................................................20 3.2.9 Transmission(ATM)...............................................................................................21 3.2.10 RU 21 3.2.11 UMTS Radio........................................................................................................25 3.2.12 UMTS Baseband Resource Pool........................................................................26 3.2.13 UMTS Sector ....................................................................................................... 27 3.2.14 UMTS Local Cell.................................................................................................. 28 3.2.15 GSM Sector......................................................................................................... 31 3.2.16 GSM Carrier......................................................................................................... 32 3.2.17 Dry Contact.......................................................................................................... 33 4 Examples of Template Filling......................................................................................35 4.1 Example 1: SDR_8700_STSR_ATM.............................................................................35 4.2 Example 2: SDR_8700_OTSR_ATM+IP...................................................................... 3 .5 4.3 Example 3: SDR_8800_STSR_IP.................................................................................36 4.4 Example 4: SDR_8800_OTSR_IPOE ............................................................................36 5 Special Subject for Quick Data Configuration...........................................................36 5.1 Rules for Naming RUs.................................................................................................... 36 5.2 Special Subject for IUB Bandwidth Configuration ........................................................38



IV


FIGURES Figure 2-1 SDR Data Quick Configuration System.........................................................2 Figure 2-2 Workflow at the Initial Stage of Commissioning..........................................3 Figure 2-3 Configuring Output SDR XML File Directory................................................4 Figure 2-4 Generating NodeB Configuration Data.........................................................5 Figure 2-5 Batch Offline Reverse.....................................................................................6 Figure 2-6 Setting ConfigSet Label.................................................................................6 Figure 2-7 Applying for Mutex Right in Batch................................................................7 Figure 2-8 Batch Switch ConfigSet.................................................................................7 Figure 2-9 Batch Export NE Data.....................................................................................8 Figure 2-10 Choosing NE Export Directory....................................................................8 Figure 2-11 Selecting an SDR XML File Directory..........................................................9 Figure 2-12 Output Directory and File Name................................................................10 Figure 2-13 Prepared Data of Entire Table Configuration............................................10 Figure 5-14 Rules for Naming RRUs .............................................................................37 Figure 5-15 Rules for Naming RSUs..............................................................................38

TABLES



V


Table 3-1 Sheets in ZXSDRConfTool Template............................................................11 Table 3-2 SubNetwork Sheet..........................................................................................12 Table 3-3 Base Station Sheet.........................................................................................13 Table 3-4 Equipment Sheet............................................................................................14 Table 3-5 Time Sheet......................................................................................................16 Table 3-6 Clock Sheet.....................................................................................................16 Table 3-7 Transmission Sheet.......................................................................................17 Table 3-8 Transmission(IP) Sheet..................................................................................19 Table 3-9 Transmission(E1T1) Sheet.............................................................................20 Table 3-10 Transmission(ATM) Sheet...........................................................................21 Table 3-11 RU Sheet.......................................................................................................22 Table 3-12 Range of GSM Sub-frequency Band...........................................................25 Table 3-13 UMTS Radio Sheet........................................................................................25 Table 3-14 Rules of CE Configuration ..........................................................................26 Table 3-15 UMTS Baseband Resource Pool Sheet.......................................................26 Table 3-16 UMTS Sector Sheet......................................................................................27 Table 3-17 UMTS Local Cell Sheet.................................................................................28 Table 3-18 Frequency Band Range...............................................................................31 Table 3-19 GSM Sector Sheet........................................................................................32 Table 3-20 GSM Carrier Sheet........................................................................................32 Table 3-21 Dry Contact Sheet........................................................................................33 Table 3-22 Description of Dry Contact Alarms.............................................................34



VI


1

Description of Version Change This chapter describes the changes in the templates and functions of SDR Quick Configuration Tools (ZXSDRConfTool). Each ZXSDRConfTool version is updated within six months. Please use the latest ZXSDRConfTool version.

1.1

ZXSDRConfTool (V2.8.0) ZXSDRConfTool(V2.8.0) supports only SDR base station V4.09.21.05, and is incompatible with SDR base station V4.00 and earlier versions. The templates of ZXSDRConfTool(V2.8.0) are quite different from those of SdrConfTool versions, as detailed below. 1.

The templates support SDR base station V4.09.21.05 only.

2.

Specifications for template filling are added in the templates, and the planning data starts from the fourth line.

3.

XML files generated by LMT can be loaded into the templates, only one file each time.

2

Introduction to Quick Data Configuration

2.1

Brief Introduction SDR data quick configuration, based on NodeB configuration data, aims to fulfill quick configuration of SDR data, through inter-conversion between NodeB configuration data in the XLS format (filled in ZXSDRConftool template) and that in the XML format (recognizable to OMC) with data import & export function on OMC and ZXSDRConfTool, as shown in Figure 2-1. Please refer to 2.3 Data Conversion for detailed operation.



1


Figure 2-1 SDR Data Quick Configuration System Generate NodeB configuration data with ZXSDRConfTool

ZXSDRConfTool template in the XLS format

Load NodeB configuration data into OMC with Batch Offline Reverse function

NodeB configuration data (XML format )

Switch data with ZXSDRConfTool

NodeB configuration data on OMC

Export NE data in batch

Synchronize data to NodeB with EOMS

SDR base station

2.2

Workflow Fill in the ZXSDRConfTool template at the initial stage of commissioning, and generate NodeB configuration data (in the XML format) with ZXSDRConfTool. Then, we can fulfill quick configuration of NodeB through two ways: 1. synchronize the data to the NodeB with EOMS, 2. load the data into OMC with Batch Offline Reverse function and then synchronize the data to the NodeB. The integration data in the ZXSDRConfTool template must be the same as that in both the NodeB Ground Resource Template and the RNS Radio Parameter Template on OMCR.



2


Figure 2-2 Workflow at the Initial Stage of Commissioning Start

STEP 1: Template filling NodeB Ground Resource Template

ZXSDRConfTool template

RNS Radio Parameter Template

STEP 2: Data generation Run SdrQuickConf.jar to generate NodeB configuration data in the XML format

STEP 3: Data synchronization Load data to OMC with Batch Offline Reverse or synchronize data to NodeB directly

End

At the later maintenance stage, if the data filled in the ZXSDRConfTool template is not the same as the data on the OMC, we can use Batch Export NE Data function to generate NodeB configuration data (in the XML format), and then restore the data to a ZXSDRConfTool template with data conversion function, so as to fulfill data batch modification.

2.3

Data Conversion

2.3.1

Generating Configuration Data in Batch (XLS to XML) Files in the XLS format can be converted to files in the XML format with ZXSDRConfTool. The same as EOMS, JRE should be installed if ZXSDRConfTool is used for the first time. If EMOS was run, this means JRE has been installed. Otherwise, run BLMT_V4.00.xx\JRE\jre-6u10-windows-i586-p.exe to install JRE.



3


As to the methods for filling in templates, please refer to 3 Specifications for Template Filling for details. The method for data generation is as below: STEP 1: Run ZXSDRConfTool.jar, and set an output directory in Output SDR XML File Directory and a template in SDR EXCEL File, as shown in Figure 2-3.

Figure 2-3 Configuring Output SDR XML File Directory

STEP 2: Click Generate XML File, and the corresponding XML file will be generated in the specified output directory, as shown in Figure 2-4.



4


Figure 2-4 Generating NodeB Configuration Data

Caution: If data generation fails, the detailed error information will be displayed in the Operation Result, and the content in the ZXSDRConfTool template should be modified.

2.3.2

Batch Offline Reverse (XML to M31) Put XML files in a folder, and then we can use the Batch Offline Reverse function on the OMC to generate OMC data in batch. STEP 1: Choose SDR Management > Data Configuration > Batch Offline Reverse. It is unnecessary to create an OMCB Managed Element before performing Batch Offline Reverse, because OMC will create an OMCB Managed Element automatically. If an NE already exists, a new Configuration Set will be created, as shown in Figure 2-5.



5


Figure 2-5 Batch Offline Reverse

STEP 2: Select the folder of XML files, fill in ConfigSet Label, and Select the correct subnetwork. Click OK, as shown in Figure 2-6.

Figure 2-6 Setting ConfigSet Label

STEP 3: Choose Configuration Management > Mutex Management > Select All, and switch to the master configuration set, as shown in Figure 2-7. After OMCB link is set up, perform all-table synchronization, as shown in Figure 2-7.



6


Figure 2-7 Applying for Mutex Right in Batch

STEP 4: Perform Batch Switch ConfigSet and switch the batch-offline-reversed configuration set to a master configuration set, as shown in Figure 2-8.

Figure 2-8 Batch Switch ConfigSet

2.3.3

Exporting NE Data in Batch (M31 to XML) STEP 1: Choose SDR Management > Data Configuration > Batch Export NE Data, as shown in Figure 2-9.



7


Figure 2-9 Batch Export NE Data

STEP 2: Select the NE to be exported and an export directory, and click OK, as shown in Figure 2-10.

Figure 2-10 Choosing NE Export Directory

Caution: The master configuration set of an NE shall not be an empty configuration set with only Inventory Unit Configuration. Otherwise, the export will fail.



8


2.3.4

Converting Configuration Data in Batch (XML to XLS) The data conversion function of ZXSDRConfTool can convert NodeB configuration files to XLS format in batch, as detailed below.

Caution:

XML files generated by EMOS cannot be converted to XLS files directly. Only XML files exported from OMMB or generated by ZXSDRConfToolV2.1.1 (or later versions) can be converted to XLS files directly. STEP 1: Run the SdrQuickConf.jar file of ZXSDRConfTool, choose File > XML -> XLS, and set SDR XML File Directory. Click Next, as shown in Figure 2-11.

Figure 2-11 Selecting an SDR XML File Directory

STEP 2: Set Output Directory and File Name (i.e. the name of the EXCEL file), and click Next, as shown in Figure 2-12.



9


Figure 2-12 Output Directory and File Name

2.3.5

Synchronizing Configuration Data on Site (XML to SDR) STEP 1: Start EOMS, and log in to a base station. STEP 2: Choose System > Entire Table Configuration > Prepared Data and select the XML file and click OK. Then the configuration data is loaded to the base station, as shown in Figure 2-13.

Figure 2-13 Prepared Data of Entire Table Configuration



10


STEP 3: After restarting the base station, check its running status, and perform commissioning test or service test.

3

Specifications for Template Filling This chapter deals with the methods and notices of fi lling in ZXSDRConfTool templates.

3.1

Introduction to Templates

3.1.1

Classification of Templates ZXSDRConfTool has three templates, used for GSM/UMTS dual mode, GSM mode and UMTS mode respectively. 

SDR_4.09.21.05_QUICKCONF_TEMPLATE_GSM



SDR_4.09.21.05_QUICKCONF_TEMPLATE_GU



SDR_4.09.21.05_QUICKCONF_TEMPLATE_UMTS

In the three templates above, the number of fields is variable in each sheet. In special scenarios, the fields in template “SDR_4.09.21.05_QUICKCONF_TEMPLATE_GU” might be copied into the other two sheets as required, so as to perform data configuration. Parameters in each template should be configured according to the actual situation.

3.1.2

Description of Each Sheet An EXCEL file in a special format is used for filling in SDR parameters. Sites in one EXCEL file are in the same sub-network. An EXCEL file has 17 sheets at most, and some sheets may be omitted in different application scenarios. Please refer to 3.2 Specifications for Template Filling for details.

Table 3-1 Sheets in ZXSDRConfTool Template SN

Sheet

Description

1

SubNetwork

SubNetwork ID

2

Base Station

NE parameters: BTS Name, NE ID, SDR Type, NE IP, SDR Version, Longitude, and Latitude, etc.

3

Equipment

Ground resource parameters: CC Slot, FS Slot, PM Slot, SE Slot, BPC Slot, UBPG Slot, Rack Topology, and Radio Mode, etc.

4

Time

Time Zone, NTP Server IP, and etc.

5

Clock

Clock ID, GPS Sync Mode, GPS Cable Type, GPS Receiver Type, and GPS Feeder Delay, etc.



11


SN

Sheet

Description

Transmission

“Transmission” sheet: Transmission Type, Ethernet Work Mode, FE Bandwidth, FE Link Type, OMCB Gateway IP, and 1588 Sync Server IP, etc.

7

Transmission(IP)

“Transmission (IP)” sheet: SCTP Radio Mode, SCTP, Local Port, SCTP Remote Port, SCTP Remote IP, SCTP Inout Stream, SCTP QoS, IP VLAN ID, OMM VLAN IP, IP VLAN IP Addr, OMM VLAN IP Addr, IP VLAN Mask, PPP E1T1 LinkID, PPP IP Address, PPP Protocol, PPP Link Type, PPP Compression, and MP Priority, etc.

8

Transmission(E1T1)

E1T1 Link ID, E1T1 Link Type, and HDLC Timeslot Map, etc.

9

Transmission(ATM)

“Transmission(ATM)” sheet: ATM Transmission Medium, E1/T1 Number, and ATM Address, etc.

10

RU

RU No., Radio Mode, GW Config Mode, Board Type, Downlink Freq, Uplink Freq, Carrier Number, Carrier Power Para, Sub Freq Band, Carrier Group, TRX Number, and Antenna Type, etc.

11

UMTS Radio

12

UMTS Baseband Resource Pool

BPC Group, and etc.

13

UMTS Sector

UMTS Sector ID, UMTS Sector Info, Related RU, and RX Type, etc.

14

UMTS Local Cell

Local Cell ID, LCG ID, UMTS Sector ID, Transmitting Freq, Carrier Indication, Freq Spacing, Cell Radius, and Local Cell Type, etc.

15

GSM Sector

Sector ID, GPS Offset, and etc.

16

GSM Carrier

TRX No., Channel Mode, Carrier Number of Logic Freq, Carrier Group, and Use IRC, etc.

17

Dry Contact

Dry contact related parameters

6

UMTS wireless parameters: NodeB ID, CE Up, CE Down, Dynamic Power Track, and Telecom Operator, etc.

3.2

Specifications for Template Filling

3.2.1

SubNetwork This sheet contains only one line, which is used for filling in subnetwork ID. All base stations in this Excel file are in this subnetwork.

Table 3-2 SubNetwork Sheet Item SubNetwork

Specifications If OMMB channel is managed by BSC (GSM), SubNetwork ID is the



12


Item

Specifications same as the BSC ID. If OMMB channel is managed by RNC (UMTS), SubNetwork ID is the same as RNC ID.

ID

3.2.2

Base Station Each base station occupies one line (including GSM/UMTS dual mode base station). Items in this sheet are corresponding to that in the SDR Managed Element on OMMB.

Table 3-3 Base Station Sheet Item

3.2.3

Specifications

BTS_NAME

80 bytes at most.

NE_ID

Value range: 0-65535; unique within a subnetwork. The NE ID is the same as the NodeB ID when UMTS mode is adopted, and is the same as the Site ID when GSM mode is adopted.

NE_IP

This IP is unique in the whole network. It is the NodeB Managed IP.

SDR_TYPE

BS8700, BS8800 GU360, BS8800 U240, BS8800 U120, BS8800 U120A, BS8900 GU360, BS8900 U240, BS8800 GU360 E, BS8900 GU360 E, BS8900A, and BS8906

SDR_VERSION

4.09.21.05.

RNC_ID

Value range: 0-4095. Do not fill in this item for single mode GSM sites.

BSC_ID

Value range: 0-65535. Do not fill in this item for single mode GSM sites.

LONGITUDE

Value range: -180-180, accurate to six decimal places.

LATITUDE

Value range: -90-90, accurate to six decimal places.

LOCATION

Optional. 40 bytes at most.

VENDOR_NAME


USER_DEFINED_STATE


Equipment This sheet deals with the configuration of SDR hardware, and must be filled in. Each NE occupies one line, corresponding to a base station (including GSM/UMTS dual mode base station). Base stations with the same hardware configuration in a subnetwork might be



13


reduced to one line. Please refer to Table 3-4 for details.

Table 3-4 Equipment Sheet Item

Specifications

NE_ID

Corresponding to the NE ID in “Base Station” sheet. If all base stations within a subnetwork have the same ground resource parameters, fill in “ALL” for this item, instead of using one line for each NE. If there are a few base stations with different ground resource parameters, fill them in the first lines before the “ALL” line.

RADIO_MODE

Options: UMTS, GSM, GSM+UMTS. Please check and confirm the configuration during the planning stage, because it is very difficult to modify this parameter on OMCB.

CC_SLOT

Value range: 1, 2. If there are two boards, fill in “1, 2” for this item. The CC board at Slot 1 is required.

FS_SLOT

Value range: 3, 4. If there are two boards, fill in “3, 4” for this item.

PM_SLOT

Value range: 14, 15. If there are two boards, fill in “14, 15” for this item.

SE_SLOT

Value range: 5-8 slot; only one board can be installed. Do not fill in this item if SE board is not configured. SE board supports 16 E1 cables.

BPC_SLOT

Required if UMTS mode is adopted. Value range: 4-8. Separate the values with coma if there are two or more BPC boards, e.g. 6,7,8.

UBPG_SLOT

Required if UMTS mode is adopted. Value range: 4-8. Separate the values with coma if there are two or more UBPG boards, e.g. 6,7,8.

TAM_SLOT

Value range: 4-8. Do not fill in this item if no TAM is configured. TAM refers to tower amplifier.

TAM_BOARD

0: TAM0. 1:TAM1. Do not fill in this item if no TAM board is configured.

TAM_WORKING_CUR RENT

Value range of TAM0: 75, 400. Default: 250. Value range of TAM1: 75, 600. Default: 120.

RACK_TOPOLOGY

Example: “1-2-3, 1-4, 1-51-52,” i.e. RSU 2 and RSU 4 are connected to an FS optical port, RSU 3 is cascaded with RSU 2, RRU 51 is also connected to an FS optical port, and RRU 52 is cascaded with RRU 51. Each FS optical port can have four cascaded RUs at most. Do not fill in this item if there is no cascaded RU.



14


Item

Specifications

FS_PORT_ASSIGN

Options: Auto, Manual. Manual allocation is required if two FS boards are configured, i.e. the filed FS_PORT in “RU” sheet is required.

BATTERY_SAVING

Y: Enable; N: Disable.

UES_SLOT

Integer: 3-8.

EPM_PWR_TYPE

ZXDU58 B900, ZXDU B121, ZXDU45-75, and ZXDU150

EPM_DEAL_MODE

0: Transparent transmission. 1: Parse

It is recommended that boards in single mode B8200 rack be installed according to the following figure.

The slots for installing boards in B8200 rack are as shown below.

If TAM is configured, it is recommended that the boards in GSM/UMTS dual mode B8200 rack be installed according to the figure below.

6HP

PM2

6HP

PM1

4HP

SA


FS2/BPC5/UBPG5 /

TAM/BPC2/UBPG1

FS1

BPC1/UBPG2

CC－2

BPC3/UBPG3

CC－1

SE/BPC4/UBPG4


4HP F

4HP

A A

4HP 4HP

15


3.2.4

Time This sheet must be filled in. It deals with time synchronization of NodeB.

Table 3-5 Time Sheet Item

3.2.5

Specifications

NE_ID

Corresponding to the NE ID in “Base Station” sheet. Usually, all base stations within a subnetwork contain the same time parameters, and we may fill in “ALL” for this item, instead of using one line for each NE.

NTP_SERVER_IP

Required. It is the IP of OMMB server.

TIME_ZONE

Required. Format: GMT + H:MM, or GMT – H:MM

SUMMER_TIME_START

Format: MM-DD HH:mm. Fill in “0” if this parameter is not enabled.

SUMMER_TIME_END

Format: MM-DD HH:mm. Fill in “0” if this parameter is not enabled.

Clock Each NE occupies one line, corresponding to a base station (including GSM/UMTS dual mode base stations). The NE ID must be in column A, which applies to all of the following sheets.

Table 3-6 Clock Sheet Item

NE_ID

Specifications Corresponding to the NE ID in “Base Station” sheet. If all base stations within a subnetwork have the same clock parameters, fill in “ALL” for this item, instead of using one line for each NE.

CLOCK_ID1

CLOCK_ID2

GPS: Built-in GPS. BITS-2MHz: BITS-2MHz clock. BITS-2Mbps: BITS-2Mbps clock. LINE: The reference clock acquired from E1/T1 cable – CC board. 1588: IP reference clock source. SyncE: Synchronization Ethernet clock.

CLOCK_ID3



16


Item

3.2.6

Specifications

GPS_SYNC_MODE

This parameter is valid only when GPS clock is adopted. Do not fill in this item if other clocks are adopted. 0: GSM/UMTS frequency synchronization 1: GSM frame No. entire network synchronization 2: GSM frequency synchronization, UMTS frame No. entire network synchronization. 3: GSM/UMTS frame No. entire network synchronization.

GPS_CABLE_TYPE

0: Input through cable 1. 1: Input through cable 2.

GPS_RECEIVER_TYPE

0: Built-in. 2: Slave shelf.

GPS_FEEDER_DELAY

Used for configuring cascaded GPS clock. Value range: 0-32767. Unit: ns.

Transmission This sheet must be filled in, one line for each base station (including GSM/UMTS dual mode base stations). All base stations with the same configuration might be reduced to one line.

Table 3-7 Transmission Sheet Item

Specifications

NE_ID

Corresponding to the NE ID in “Base Station” sheet. If all base stations within a subnetwork have the same transmission parameters, fill in “ALL” for this item, instead of using one line for each NE.

TRANSMISSION_TYPE

IUB interface transmission protocol: IP, ATM, ATM+IP. GSM supports only IP.

TRANSMISSION_MEDIUM

Physical transmission medium of IUB interface: FE,GE,E1,T1

ETHERNET_WORK_MOD E

Options: Auto/1000M/100M/10M. Auto means selfadaptation. Default: Auto.

FE_BANDWIDTH

Maximum bandwidth for Ethernet transmission: 1000000kbps (1000M). Minimum bandwidth for Ethernet transmission: 100kbps.

FE_LINK_TYPE

Options: RNC/BSC/CN or SDR. Configure the lower-level base station as SDR, if cascaded configuration is adopted.

OMCB_GATEWAY_IP

If IP is adopted for IUB interface transmission protocol,



17


Item

Specifications this item is filled in GLOBAL Supplemented Configuration. OMCB Gateway IP (also Agent IP) is used for NodeB management.

3.2.7

OMCB_QOS

BE: Try the best (default). EF: EF service, accelerated retransmission, shortest time delay, and maximum flow. AF42: service class 4. Discarding priority: medium. AF22: service class 2. Discarding priority: medium. AF43: service class 4. Discarding priority: high. AF23: service class 2. Discarding priority: high.

OMCB_CHANNEL

Required when GSM/UMTS dual mode is adopted. This parameter indicates whether OMC-B channel is established on iBSC or on RNC. Do not fill in this item, if single mode is adopted.

1588_SYNC_SERVER_IP

Required when IEEE1588 is used for reference clock source. Valid only in Ethernet transmission. If there are two or more 1588 servers, format “IP1;IP2; …” might be adopted. Four IP addresses are allowed at most.

1588_IP_CHANNEL

Required when GSM/UMTS dual mode is adopted and IEEE1588 is used for reference clock source. Value GSM/UMTS indicates whether IP channel is established on iBSC or on RNC. Do not fill in this item, if single mode is adopted.

1588_QOS

BE: Try the best. EF: EF service, accelerated retransmission, shortest time delay, and maximum flow (default). AF42: service class 4. Discarding priority: medium. AF22: service class 2. Discarding priority: medium. AF43: service class 4. Discarding priority: high. AF23: service class 2. Discarding priority: high.

Transmission(IP) Please fill in this sheet if IP, ATM+IP, or IPOE transmission is adopted. For GSM single mode or WCDMA single mode, each NE occupies one line. For GSM/WCDMA dual mode, each NE occupies two lines, one line for GSM, the other for WCDMA. For Ethernet transmission, two IP VLANs at most can be configured at each line, one for service channel, the other for OMC channel. If each site is configured with only one IP address, i.e. only one IP VLAN, fill in only IP VLAN property. If Ethernet transmission is adopted, do not fill in PPP related parameters. If PPP



18


transmission is adopted, do not fill in VLAN related parameters. If the transmission media is E1/T1, please set E1T1 Link Type and HDLC Timeslot Map in “Transmission (E1T1)”sheet.

Table 3-8 Transmission(IP) Sheet Item

Specifications

NE_ID

Corresponding to the NE ID in “Base Station” sheet.

SCTP_RADIO_MODE

GSM or UMTS.

SCTP_LOCAL_PORT

Value range: 0-65535. It is the GSM Site ID if GSM mode is adopted, and the value range is 1-1536. GSM NE ID is the same as t he Site ID.

SCTP_REMOTE_PORT

Value range: 0-65535. For GSM mode, the value is iBSC CMP module No. + 0x3900, which must be converted to a decimal number.

SCTP_REMOTE_IP

Remote IP should not be the same as service IP, OMCB IP, or PPP IP.

SCTP_INOUT_STREAM

Value range: 1-6.

SCTP_QOS

BE: Try the best. EF: EF service, accelerated retransmission, shortest time delay, and maximum flow (default). AF42: service class 4. Discarding priority: medium. AF22: service class 2. Discarding priority: medium. AF43: service class 4. Discarding priority: high. AF23: service class 2. Discarding priority: high.

IP_VLAN_ID

Value range: 2-4094. 65535 or null: Invalid.

IP_VLAN_IP_ADDR

IP address and gateway address should be in the same network segment.

IP_VLAN_MASK

Mask.

IP_VLAN_GATEWAY

The gateway of signaling service IP.

OMM_VLAN_ID

Value range: 2-4094. 65535 or null: Invalid

OMM_VLAN_IP_ADDR

OMM IP address and OMM gateway address should be in the same network segment.

OMM_VLAN_MASK

Mask.

OMM_VLAN_GATEWAY

The gateway of OMM IP address.

PPP_E1T1_LINKID

Value range: 0-15. Separate the values with coma if there are two or more links, e.g. “0,1,2”. This item is required for PPP transmission. 8 links can be filled in at most.

PPP_IP_ADDRESS

Required for PPP transmission. 0.0.0.0: Auto-negotiation



19


Item

3.2.8

Specifications

PPP_PROTOCOL

Required for PPP transmission. Options: PPP or ML-PPP. Default: ML-PPP.

PPP_LINK_TYPE

Options: RNC/BSC/CN or SDR. Default: RNC/BSC/CN.

PPP_COMPRESSION

0: Not support. 1: Support. Default: Not support. PPP transmission does not support IP header compression.

MP_HEAD

Options: LONG, SHORT, and INVALID. Default: LONG. Valid when PPP Protocol is ML-PPP.

MP_PRIORITY

Options: 1,2,3,4, and INVALID. Valid when PPP Protocol is ML-PPP.

Transmission(E1T1) Fill in this sheet, if PPP transmission is adopted. Each NE occupies one line or more lines, with one line for each E1 link.

Table 3-9 Transmission(E1T1) Sheet Item

Specifications

NE_ID


E1T1_LINK_ID

Value range: 0-15.

E1T1_LINK_TYPE

Options: RNC/BSC/CN or SDR. Note: If there is only one E1 cable, it cannot be connected with RNC and BSC at the same time.

HDLC_TIMESLOT_MAP

Except Timeslot 0, Timeslots 1-31are available. Format: Start timeslot – end timeslot. Segment the timeslots if they are discontinuous, e.g. “15,10-20.”

TSI_IN_TIMESLOT_MAP

Fill in this item only when cascaded connection is adopted. The format is the same as that of HDLC timeslot, but the TSI IN TIMESLOT MAP should not be the same as HDLC timeslot No.

TSI_OUT_LINK_ID

Fill in this item only when cascaded connection is adopted. Value range: 0-7.

TSI_OUT_TIMESLOT_MAP


Fill in this item only when cascaded connection is adopted.


20


Item

Specifications The format is the same as that of HDLC timeslot.

3.2.9

Transmission(ATM) Fill in this sheet if it is ATM transmission or ATM+IP transmission, with one line for each NE. ATM transmission is supported only when WCDMA mode and 4.00.200 series NodeB are adopted. E1/T1 link is numbered from 0. Default configuration: IMA; Length of frame:128cell; ITC Clock mode: ITC; Cell Payload Scrambling; IMA version: 1.1. All of E1/T1 links are put in IMA Group 0. Use CBR for AAL5 signaling, and rt-VBR and UBR for AAL2. The physical bandwidth usage is 100%. The default configuration above should be the same as RNC quick configuration data, both complying with “ZXWR RNC IubPVC_configurationTool_English.xls.” Please refer to the attached file in 5.2 Special Subject for IUB Bandwidth Configuration for details. When ATM+IP transmission is adopted and IP parameters have been configured, an OMCB dual protocol stack channel, and IP, NCP and CCP parameters of an IPOA will be created automatically.

Table 3-10 Transmission(ATM) Sheet Item

3.2.10

Specifications

NE_ID


ATM_TRANSMISSION_MEDIUM

E1,T1.

E1T1_NUMBER

Value range: 0-15, e.g. 0,1,3.

ATM_ADDRESS

It is an integration parameter, and should be configured the same as the address on OMMR. It has 20 bytes in total. Just fill in the valid length, and the rest bytes will be filled with 0 automatically.

RNC_IUB_BOARD

IMAB/APBE or APBI/SDTA/ET3A. This item determines the average bandwidth and the minimum bandwidth in AAL2. Fill in this item according to the actual situation.

RU Each RRU and each RSU occupy one line respectively. Therefore, each NE in this sheet may involve several lines of data.



21


RRU is numbered from 2, and 24 RRUs can be configured at most. Only when there is one FS board can auto allocation of FS optical ports be performed, which should be in the ascending order of RU No. BS8800 GU360 and BS8800 U240 can be configured with six RSUs at most. BS8800 U120 and BS8800 U120A can be configured with three RSUs at most. BS8900 can be configured with 12 RSUs at most. BS8906 can be configured with two RSUs at most. BS8800 GU360 E can be configured with 12 RSUs at most. BS8900 GU360 E can be configured with 18 RSUs at most. BS8900A can be configured with nine RSUs at most. BS8700 can be configured with 12 RSUs at most.

Table 3-11 RU Sheet Item

Specifications

NE_ID


RU_NO

Value range of RRU No.: 51-74. Value range of RSU No.: 2-19.

RRU_NAME

Optional. 80 bytes at most. Do not use characters < > & ' and ".

RADIO_MODE

UMTS, GSM, and GSM+UMTS.

GW_CONFIG_MODE

4G+1U, 2G+2U, INVALID. Adopt INVALID for single mode.

BOARD_TYPE

RTR:RTR-U212/RTR-U852/RTR-U902/RTR-U182/RTRU192/RTR-U214/RTR-U854/RTR-U904/RTR-U184/RTRU194/RTR-U216/RTR-U856/RTR-U906/RTR-U186/RTRU196/RTR-UAWS6 RSU40:RSU40-UAWS6/RSU40-U214/RSU40U854/RSU40-U904/RSU40-U184/RSU40-U194/RSU40U216/RSU40-U856/RSU40-U906/RSU40-U186/RSU40U196 DTR: DTR-GU216/DTR-GU856/DTR-GU906/DTRGU186/DTR-GU196/DTR-GU218/DTR-GU858/DTRGU908/DTR-GU188/DTR-GU198 RSU60: RSU60-GU216/RSU60-GU856/RSU60GU906RSU60-GU186/RSU60-GU196/RSU60GU218/RSU60-GU858/RSU60-GU908/RSU60GU188/RSU60-GU198 R8880:R8880A-U2112 TTR:TTR-G902/TTR-G182/TTR-G904/TTR-G184 RSU02:RSU02-G902/RSU02-G182/RSU02-G904/RSU02G184 RTR series are installed in the R8840 rack. DTR series are installed in the R8860 rack. R8880A series are installed in the R8880 rack. TTR series are installed in the R8802 rack. RSU series are installed in the main rack.

DOWNLINK_FREQ


It must be an integral multiple of 0.2MHz. “0” or Null means auto calculation by the base st ation


22


Item

Specifications equipment.

UPLINK_FREQ

It must be an integral multiple of 0.2MHz. “0” or Null means auto calculation by the base st ation equipment. If DOWNLINK_FREQ is not “0,” do not configure UPLINK_FREQ as “0.”

FS_PORT

0-5: refer to the 6 optical ports on the first FS board. 20-25: refer to the 6 optical ports on the second FS board. Do not fill in this item, if the FS optical port is allocated automatically or is cascaded to a higher level RU.

CARRIER_GROUP

For GSM only. Value range: 0-32. 0: Not group

CARRIER_NUMBER

For GSM only. 1-6 are for DTR board series, and 1-2 are for TTR series

CARRIER_POWER_PA RA

For GSM only. Value range: 1-80.

STATIC_POWER_LEVE L

For GSM only. 0db, 2db, 4db, 6db, 8db, 10db, 12db, 14db, 16db, 18db, and 20db.

RX_PORT_ANTENNA

N: Not connect with antenna. Y: Connect with antenna. If it is set as Y, RX Extension RU cannot be configured.

RX_EXTENSION_RU

The associated RUs should have the same frequency band. Each RU can be associated once only.

SECTOR_ID_1

For GSM only. This Sector ID must exist in GSM Sector sheet. 255: Invalid.

TRX_NUMBER_1

For GSM only/ Value range: 0-6. The number of carriers in all sectors should be less t han or equal to the total number of carriers.

SECTOR_ID_2

For GSM only. Value range: 0-6. The number of carriers in all sectors should be less t han or equal to the total number of carriers.

TRX_NUMBER_2


SECTOR_ID_3

For GSM only Value range: 0-6. The number of carriers in all sectors should be less than or equal to the total number of carriers.

TRX_NUMBER_3


For GSM only/ Value range: 0-6. The number of carriers in all sectors should be less t han or


23


Item

Specifications equal to the total number of carriers.

SECTOR_ID_4


TRX_NUMBER_4


SECTOR_ID_5


TRX_NUMBER_5

For GSM only Value range: 0-6. The number of carriers in all sectors should be less than or equal to the total number of carriers.

SECTOR_ID_6


TRX_NUMBER_6


SUB_FREQ_BAND

For GSM only. Value range: 0-3. 0: Not enable sub-frequency band.

ANTENNA_TYPE

ANT/RET. ANT: Common antenna; RET: Electric tilt antenna

TM_TYPE

TMA, A-TMA, ETMA, and A-ETMA. This parameter and the following four ones are valid only for antenna type RET.

RX_POWER_GAIN

TMA: 110-130 (0.1dB). A-TMA: 44-100(0.25dB). ETMA: 230-250 (0.1dB). A-ETMA: 92-100 (0.25dB). Invalid: 255.

TX_POWER_GAIN

Value range: 70-170. Invalid: 255.

TMA_NOISE

Value range: 10-30.

LINE_LOSS

Value range: 0-80.

Fill in only the category of Board Type, it is not necessary to divide the category to subcategories B/C/D/E. The type of boards can be found out automatically according to the frequency band of Downlink Frequency, e.g. 2.1G is corresponding to DTR, and 900M



24


is corresponding to DTR-C. DTR/DRSU supports sub-frequency band, but it is not necessary to configure subfrequency band to TTR/GRSU/RTR/RSU series. 900MHz frequency band includes three sub-frequency bands (1-3); 1800MHz frequency band includes two sub-frequency bands (1-2). It is not necessary to configure other frequency bands. Please refer to Table 3-12 for detailed frequency range. The Downlink Frequency of RRUs in the same Carrier Group should be in the same frequency band.

Table 3-12 Range of GSM Sub-frequency Band Frequency Band

Sub-frequency Band

GSM900M

DCS1800M

3.2.11

Transmitting (downlink) Frequency Range(MHz)

1

935-960

2

925-950

3

935-951

1

1805-1860

2

1825-1880

UMTS Radio Fill this sheet when UMTS mode is adopted. This sheet is corresponding to the wireless resource management of SDR NE on OMMB.

Table 3-13 UMTS Radio Sheet Item

Specifications

NE_ID


NODEB_ID

Value range: 0-65535. NodeB ID is the same as NE ID when UMTS mode is adopted.

CE_UP

Value range: 1-1920. 65535: Invalid.

CE_DOWN


DYNAMIC_POWER_TRAC K

Y: Enable. N: Disable.

TELECOM_OPERATOR


PASHARE_PER

Value range: 0-50. Default: 0.



25


Table 3-14 Rules of CE Configuration Site Configuration

3.2.12

Number of Uplink CEs

Number of Downlink CEs

Number of Cells

S111H

189

123

3

S111M

114

79

3

S111L

83

48

3

S11H

126

82

2

S11M

76

53

2

S11L

55

32

2

S222

308

171

6

S333

426

219

9

S444

545

267

12

O1M

38

27

1

O1L

29

16

1

O1Indoor

40

16

1

O2Indoor

79

32

2

S11Indoor

79

32

2

S111Indoor

119

48

3

S222Indoor

237

96

6

UMTS Baseband Resource Pool Fill this sheet when UMTS mode is adopted. Each baseband resource pool occupies one line. Thus, each NE in this sheet may have two or more lines of data.

Table 3-15 UMTS Baseband Resource Pool Sheet Item

Specifications

NE_ID


LCG_ID

Value range: 0-35; unique in the same NodeB. If there are two or more carriers, they should be in different baseband resource pools.

LCG_INFO

Optional. 199 bytes at most. Do not use characters < > & ‘ and “.

BPC_GROUP


Format: BPCSlot&BPCSlot&…. e.g. “8” means there is one baseband board in this group, and the slot No. is “8”; “7&8” means there are two baseband boards


26


Item

Specifications in this group, and the slot Nos. are “7” and “8” respectively.

3.2.13

UMTS Sector Fill this sheet when UMTS mode is adopted. Each baseband resource pool occupies one line. Thus, each NE in this sheet may have two or more lines of data. When two or more RRUs/RSUs are configured in a sector, all RUs should be in the same frequency band and connected to the same FS board. RUs of different frequency bands should not be configured together in the same base station. RTRs of different power consumptions can be configured in the same RU, DTRs and dual mode RSU boards should have the same frequency band. If RX Type MIMO-II is adopted, boards of different power consumptions should not be configured in the same RU.

Table 3-16 UMTS Sector Sheet Item

Specifications

NE_ID


UMTS_SECTOR_ID

Value range: 0-255; unique in the same site.

UMTS_SECTOR_INFO


RELATED_RU

RU No. If OTSR/M-RRU is adopted, the format should be RU1&RU2&….

RX_TYPE

Y: Diversity. N: Non-diversity. MIMO. MIMO-II. The MINO RU should be R8880, and only one RU can be used. The MIMO-II RU should be R8880, and two RUs should be used.

RFRX_ORDER

This parameter is used to set RF cable connections for POI sites. For receiving diversity, 0 means normal sequence, i.e. port 0 of the RF board is configured first; 1 means the reverse sequence, i.e. port 1 of the RF board is configured first. For receiving non-diversity, 0 means using the primary antenna, and 1 means using the secondary antenna.



27


3.2.14

UMTS Local Cell Fill this sheet when UMTS mode is adopted. Each local cell occupies one line. Thus, each NE in this sheet may have two or more lines of data.

Table 3-17 UMTS Local Cell Sheet Item

Specifications

NE_ID


LOCAL_CELL_ID

Value range: 0-268435455; unique in the same subnetwork.

LOCAL_CELL_INFO


UMTS_SECTOR_ID

Cited from “UMTS Sector” sheet.

LCG_ID

Cited from “UMTS Baseband Resource Pool” sheet.

TRANSMITTING_FREQ

Refer to Table 3-18 for the value range. The value should be an integral multiple of 0.2MHz.

CARRIER_INDICATION

DTR/RTR series: 0-2. R8880A: 0-5. Only carriers with Carrier ID 0 can be configured to dual mode 4G+1U. Only carriers with Carrier ID 0 and 1 can be configured to dual mode 2G+2U.

FREQ_SPACING

5M, 4.8M, 4.6M, 4.4M, 4.2M, 4.4M and 4.2M are applicable only to single mode UMTS R8860.

CELL_RADIUS

2.5km/5km/10km/20km/40km/80km/120km.

LOCAL_CELL_POWER


LOCAL_CELL_TYPE

0: Common cell. 1: High-speed railway cell. As to the specifications of configuring high-speed railway cells, please refer to the following text.

DC_LOCAL_CELL

If the local cell is a dual carrier master cell, it should be in the same sector as the slave cell, both the Carrier Indication and the Tx power should be in an ascending order, and the master cell and the slave cell should be neighbor cells (Frequency Spacing: 4.2-5MHz). The Rx Type of the sector should not be MIMO or MIMO-II.

TRANSMIT_DELAY

Value range: 0-65535. Default: 23

RECEIVE_DELAY

Value range: 0-65535. Default: 13.

BATTERY_SAVING

Y: Enable. N: Disable



28


Item

Specifications

LOCAL_CELL_2MS_GAIN

Enable: Support. Disable: Not support.

LOCAL_CELL_VAM

Y: Support. N: Not support. Configure this parameter as Y only when the RX Type is MIMO/MIMO-II.

The Downlink Frequency should be an integral multi ple of 0.2 MHz. The Uplink Frequency is calculated according to the Downlink Frequency and the Frequency Spacing between the transmitting frequency and the receiving frequency in Table 3-18. Carrier Indication and Frequency Spacing should meet the foll owing requirements: 1.

The Carrier Indication should be unique within the same sector;

2.

The bandwidth of each carrier should be an integral multiple of 0.2MHz and within 4.6-5.0MHz. The overlapped bandwidth of every two carriers should not exceed 0.1MHz

3.

The frequency spacing of every two carriers should be <=5MHz and >=4.2MHz, or >=8.4MHz and <= 10MHz, i.e. the spacing of Downlink Frequency for two carriers should be within “4.2, 5” or “8.4, 10.”

The cell with two or more RRUs/RSUs in its sector is an M-RRU (M is the number of RUs) cell (referred to as OTSR cell before). The cell with only one RRU/RSU in its sector is an STSR cell. Baseband resource pool, composed of one or more BPC baseband boards, is configured in “UMTS Baseband Resource Pool” sheet. Baseband resource pool was called local cell group (LCG). The capacity of a baseband resource pool is as listed below: 1.

The baseband resource pool with only non-MRRU cells can be configured with six cells at most.

2.

If there are more than three STSR cells and only one BP board in the baseband resource pool with only STSR cells, the radius of each local cell should be within 2.5 km.

3.

The resource pool with only 2-RRU cells can be configured with three local cells at most.

4.

The baseband resource pool with only M-RRU(M>2) cells can be configured with two cells at most.

5.

When both M-RRU(M>2) cells and 2-RRU cells are configured, only one M-



29


RRU(M>2) cell and one 2-RRU cell can be configured in a resource pool at the same time. 6.

If there is only one BP board in the resource pool with both M-RRU(M>2) cells and 2RRU cells, the radius of each local cell should be within 2.5km.

7.

If there is only one M-RRU(M>2) cell and one BP board in the baseband resource pool, the radius of each local cell should be within 2.5km.

8.

The baseband resource pool with both M-RRU(M>2) cells and STSR cells can be configured with one local M-RRU(M>2) cell and three STSR cells at most.

9.

If four local cells are configured in the baseband resource pool configured with both 2-RRU local cells and STSR local cells, only one 2-RRU cell and three STSR cells can be configured at the same time.

10. If there is only one BP board in the resource pool with both M-RRU(M>2) cells and STSR cells, the radius of each local cell should be within 2.5km. Cells with a radius of 80km or 120km are of ultra-wide coverage cells, to which the capacity is as listed below. 1.

A cell of ultra-wide coverage supports only receiving diversity and does not support receiving non-diversity;

2.

A cell of ultra-wide coverage should be configured with a separate resource pool, in which three cells with ultra-wide coverage can be configured at most.

3.

A Baseband resource pool with only one baseband board can be configured with only one cell with ultra-wide coverage at most.

4.

A Baseband resource pool with two baseband boards can be configured with only two cells with ultra-wide coverage at most.

5.

A Baseband resource pool with three or more baseband boards can be configured with three cells with ultra-wide coverage at most.

The capacity for high-speed railway cells is as listed below. 1.

High-speed railway cells and common cells cannot share the same baseband resource pool.

2.

The radius of high-speed railway cells can only be 2.5km or 5km.

3.

M-RRU(M>2) high-speed railway cells and OTSR high-speed railway cells cannot share the same baseband resource pool.

4.

If there is only one baseband board in a baseband resource pool with only STSR high-speed railway cells, three cells can be configured at most.



30


5.

If there is only one baseband board in a baseband resource pool with both STSR and 2-RRU high-speed railway cells, one STSR cell and one 2-RRU cells can be configured at most at the same time.

6.

If there is only one baseband board in a baseband resource pool with only MRRU(M>2) high-speed railway cells, one cell can be configured at most.

7.

If there are two or more baseband boards in a baseband resource pool with only STSR high-speed railway cells, six cells can be configured at most.

8.

If there are three or more baseband boards in a baseband resource pool with only 2RRU high-speed railway cells, three cells can be configured at most.

9.

If there are two baseband boards in a baseband resource pool with only 2-RRU highspeed railway cells, two cells can be configured at most.

10. If there are two or more baseband boards in a baseband resource pool with only MRRU high-speed railway cells, two cells can be configured at most. It is necessary to check the sum of the power consumptions on dual mode DTR/DRSU. The product of “GSM Carrier Power X Number of carriers + Power of local WCDMA cells” shall not exceed the total power on the board.

Table 3-18 Frequency Band Range Receiving Frequency Frequency Band

Lower Limit(M Hz)

Upper Limit (MHz)

Transmitting Frequency Lower Limit(M Hz)

Upper Limit(M Hz)

Spacing Between Receiving and Transmitting Frequency (MHz)

Board Type

2.1G(Band I)

1920

1980

2110

2170

190

A

1900M(Band II)

1850

1910

1930

1990

80

E

1800M(Band III)

1710

1785

1805

1880

95

D

850M(Band V)

824

849

869

894

45

B

900M(Band VIII)

880

915

925

960

45

C

If the Downlink Frequency of the RU for local cells is not “0,” the receiving frequency of the cell and the Uplink Frequency of the RU should meet the following condition: The absolute value of “Uplink Frequency of the RU – the receiving frequency of the local cell” + a half of the bandwidth of the local cell ≤ 10MHz.

3.2.15

GSM Sector Fill this sheet when GSM mode is adopted. Each sector occupies one line. Thus, each NE



31


in this sheet may have two or more lines of data.

Table 3-19 GSM Sector Sheet List

3.2.16

Specifications

NE_ID


SECTOR_ID

Value range: 1-24.

GPS_OFFSET

Value range: 0-50.

POINT1_RU_NO

POINT1 RU NO and POINT2 RU NO should be configured together. It is not necessary to fill this item if it is not configured.

POINT2_RU_NO

It is not necessary to fill this item if it is not configured.

GSM Carrier Fill this table when GSM mode is adopted. Each sector occupies one line or more lines. Thus, each NE in this sheet may have two or more lines of data. If an OTSR cell is to be configured, the number of carriers should be set to “2” or a larger value, and the Channel Mode should be “Multiple Channel Mode.” If the Channel Mode is set as single channel, the Carrier Group of the corresponding RRU should be “0” (i.e. Not group), and there can only be one carrier; if it is set as dual channels, there can only be two carriers. In dual or multiple channel modes, the Carrier Group must be configured, and grouping must be performed. If the RRUs associated with the base station are in the same Carrier Group, they should be in the same frequency band, and the number of RRUs should be the same as that of carriers in the same group.

Table 3-20 GSM Carrier Sheet Item

Specifications

NE_ID


SECTOR_ID

Value range: 1-24.

TRX_NO

Value range: 1-54. Fill in “auto,” if the generated logic TRX No. of a sector starts from 1, and no CoBCCH is configured, and the sub-frequency bands are “0.” For all sectors of a site, the same mode should be adopted to generate data of logic TRXs. If “auto” mode is adopted for generating data of logic TRXs, please check whether the generated data is consistent with the data of cell TRX data on OMCR.



32


Item

3.2.17

Specifications

CHANNEL_MODE

SINGLE: channel. DUAL: Dual channel. MULTI: Multi-channel

CARRIER_NUMBER_OF_LOGIC_FREQ

Value range: 1-12. This value should be smaller than the sum of carriers on all RRUs in this cell.

CARRIER_GROUP

Value range: 0-32. 0: Not group. Do not fill in this item, if the logic TRX No. is generated automatically.

FREQ_BAND

2.1G,1900M,1800M,850M,900M Do not fill in this item, if the logic TRX No. is generated automatically.

SUB_FREQ_BAND

Value range:0-3. 0 or 255: Not enable sub-frequency Do not fill in this item, if the logic TRX No. is generated automatically.

USE_IRC

1: Use. 0: Not use.

EXTENSION_CARRIER

1: Yes. 0: No.

Dry Contact Each dry contact occupies one line. Thus, each NE in this sheet may have two or more lines of data.

Table 3-21 Dry Contact Sheet Item

Specifications

NE_ID


RACK_NO

Main rack No.: 1. Remote racks are numbered from 2.

SHELF_NO

The Shelf No. of B8200(B8700) and RRU can only be 1. The Shelf Nos. of B8800 can be 1/2/5. The Shelf No. of FCE board is 2. The Shelf No. of RSU is 5. The Slot No. of B8900 can be 1/6/8/10/12/13/15, in which the Shelf Nos. of FCE/FCEA are 6/10/13. The Shelf Nos. of RSU are 8/12/15.

SLOT_NO


The Slot No. of the SA board on B8200(B8700) is13. The Slot No. of the SE board is 5.


33


Item

Specifications The Slot No. of the RRU board is 1. The Slot No. of the FCE board for B8800 is 1. The Slot No. of the FCE board for B8900 is 3(1.13.3). The Slot No. of the FCEA board is 1(1.6.1)/2(1.10.2).

DRY_CONTACT_NO

SA/SE supports 8 dry contact inputs, i.e. Dry Contact Nos. 0-7. The dry contact Nos. of RF boards are 0-3. The dry contact Nos. for FCE series are 0-4, but No. 0 can only be configured for “198092049 Cabinet’s lightning arrestor alarm” (or not configured); No. 1 cannot be configured; for 200 series, Nos. 24 cannot not be configured.

DRY_CONTACT_AL ARM_CODE

Value range: 1556-1605. Valid only when the Dry Contact No. is “0.” Supported by version 4.00.30.09. Note: It is necessary to set user-defined alarm code on OMCB. Choose Alarm Management > Setting > AlarmCode Description Setting, and modify the description of the code to be used, then this alarm code can be used in Configuration Management.

DRY_CONTACT_TY PE

DRY_CONTACT_CO NTENT ALARM_STATUS DRY_CONTACT_OU TPUT_STATUS

Input: Input dry contact. Output: Output dry contact. Output dry contact can only be configured on Dry Contact No. 6 and No. 7 of SA board or SE board. Refer to Table 3-22. One rack can only be configured with one dry contact, which is corresponding to “Main power supply has fault alarm.” OPEN/CLOSE. Valid for output dry contact. 0: Output low level. 1: Output high level.

Table 3-22 Description of Dry Contact Alarms Value

Description

198092044

Cabinet door alarm

198092045

Flooding Fault

198092046

Smoke alarm/SMOG Fault

198092047

Infrared alarm

198092048

Air-condition fault

198092049

Cabinet’s lightning arrestor alarm

198092051

PSU alarm

198092052

PSU fan alarm

198092068

Base station master power supply break alarm

198092206

Battery Fault

198092207

AC power-cut alarm



34


Value

4

Description

198092208

Rectifier model alarm

198092209

Thermoelectric cooling alarm

Examples of Template Filling ZXSDRConfTool templates provide some examples for the four types of bearers, as shown in the attached file below. The following basic items must be filled in: in “SubNetwork” sheet, only the fourth line can be filled in; for both the “Base Station” sheet and the “Equipment” sheet, use one line for each base station, but base stations with the same site configuration might be reduced to one line; for “Time” and “Clock” sheet, base stations with the same property might be reduced to one line.

SDR_CONFTOOL_UMTS_DEMO_V2. 8. 0. zi p

4.1

Example 1: SDR_8700_STSR_ATM Ground resource part: Besides the basic items, items in “Transmission” sheet and “Transmission(ATM)” sheet should be filled in. Please note: In the “Transmission(ATM)” sheet, the E1 Number, instead of the number of E1 cables, must be configured. Keep the default value for PVC and other parameters. Wireless resource part: In this example, there are three STSR cells with star networking, in which Cell 10013 is configured as receiving non-diversity.

4.2

Example 2: SDR_8700_OTSR_ATM+IP Ground resource part: Because the IP configuration is added, besides the basic items, the three sheets of “Transmission,” “Transmission(IP),” and “Transmission(ATM)” must be filled in. Please note: In the “Equipment” sheet, the Slot Number, instead of the number of slots, must be filled in. In the “Transmission(IP)” sheet, it is unnecessary fill in the following fields: PPP_E1T1_LINKID, PPP_IP_ADDRESS, PPP_PROTOCOL, PPP_COMPRESSION, MP_HEAD, and MP_PRIORITY. Wireless resource part: There are four RRUs in this example. The fourth RRU is cascaded to the third one, forming an OTSR cell. In the “ Equipment” sheet, the connection between RUs should be described in the RACK_TOPOLOGY filed (1-51, 1-52, and 1-5354 in this example). In the “UMTS Sector” sheet, the Related RU should be “53&54,” indicating an OTSR cell.



35


4.3

Example 3: SDR_8800_STSR_IP Ground resource part: Besides the basic items, “Transmission” sheet and “Transmission(IP)” sheet must be filled in. In the “Transmission(IP)” sheet, it is unnecessary to fill in the following fields: PPP_E1T1_LINKID, PPP_IP_ADDRESS, PPP_PROTOCOL, PPP_COMPRESSION, MP_HEAD, and MP_PRIORITY. Wireless resource part: In this example, three RSUs are configured in three STSR cells. When filling in the “RSU” sheet, please note the changes in the meaning of RSU_NO field: “2” refers to the RSU at the first slot, “3” refers to the RSU at the second slot, and so on.

4.4

Example 4: SDR_8800_OTSR_IPOE Ground resource part: Besides the basic items, “Transmission” sheet, “Transmission(IP)” sheet, and “Transmission(E1T1)” sheet must be filled in. But in “Transmission(IP)” sheet, it is unnecessary to fill in the fields starting with “IP_VLAN.” Wireless resource part: In this example, there are one RRU and three RSUs. The RRU is connected to the optical port 0 of FS board, and the RSUs are connected to optical ports 1-3. The RRU and the last RSU form an OTSR cell. The parameter FS Port Assignment in the “Equipment” sheet should be set as “Manual.” The FS Port in the “RRU” sheet and the “RSU” sheet must be filled in.

5

Special Subject for Quick Data Configuration

5.1

Rules for Naming RUs Figure 5-14 shows the rules for naming RRUs and Figure 5-15 shows the rules for naming RSUs.



36


Figure 5-14 Rules for Naming RRUs

Rules for Naming RRUs Xn - Xn Xn X

Power Frequency band (n characters , two digits usually adopted ) Radio mode (n characters) TRX board (n characters) Remarks: Power 4: 40W, 6: 60W, 8: 80W Frequency band: 21, 85, 90, 18, 19, AWS: 2100M, 850M, 900M, 1800M, 1900M, AWS frequency band Radio mode: U: UMTS, G: GSM, GU: GSM/UMTS TRX board: RTR, DTR, TTR, TRMD



37

U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide_R.1

Recommend Documents