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) 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 contains proprietary information of ZTE CORPORATION. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. and are registered trademarks of ZTE CORPORATION. ZTEs company name, logo and product names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyones access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any marks appearing in the document. The design of this product complies with requirements of environmental protection and personal security. This product shall be stored, used or discarded in accordance with product manual, relevant contract or laws and regulations in relevant country (countries). This document is provided as is and as available. Information contained in this document is subject to continuous update without further notice due to improvement and update of ZTE CORPORATIONs products and technologies.
ZTE CORPORATION
Address : NO. 55 Hi-tech Road South ShenZhen P.R.China 518057 http://dms.zte.com.cn (Technical Support) TSM.Aftersales@zte.com.cn
Website : Email:
ZTE Confidential Proprietary
2012 ZTE CORPORATION. All rights reserved.
Revision History
Product Version V4.09.21 Document Version R1.0 Serial Number Reason for Revision First published
Author
Date 2010-10-13 Document Version R1.0 Prepared by Zhao Lijie Reviewed by Chen Taiming Approved by Chen Taiming
II
About This Document

Summary
Chapter 1 Description of Version Change 2 Introduction to Quick Data Configuration 3 Specifications for Template Filling 4 Examples of Template Filling 5 Special Subject for Quick Data Configuration Quick data configuration Specifications for template filling Examples of template filling Special subject for quick data configuration Description Changes in different versions
Applicable to: UMTS NodeB commissioning engineers
III
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.......................................................................35 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
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
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. 2. The templates support SDR base station V4.09.21.05 only. Specifications for template filling are added in the templates, and the planning data starts from the fourth line. XML files generated by LMT can be loaded into the templates, only one file each time.
3.
2
2.1
Introduction to Quick Data Configuration

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.
Figure 2-1 SDR Data Quick Configuration System

Generate NodeB configuration data with ZXSDRConfTool Load NodeB configuration data into OMC with Batch Offline Reverse function
ZXSDRConfTool template in the XLS format
NodeB configuration data (XML format )
NodeB configuration data on OMC
Switch data with ZXSDRConfTool
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.
Figure 2-2 Workflow at the Initial Stage of Commissioning

Start
STEP 1: Template filling NodeB Ground Resource Template RNS Radio Parameter Template
ZXSDRConfTool 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
2.3.1
Data Conversion
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.
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.
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.
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.
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.
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.
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.
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.
Specifications for Template Filling

This chapter deals with the methods and notices of filling in ZXSDRConfTool templates.
3.1
3.1.1
Introduction to Templates
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 1 2 3 4 5 Sheet SubNetwork Base Station Equipment Time Clock SubNetwork ID NE parameters: BTS Name, NE ID, SDR Type, NE IP, SDR Version, Longitude, and Latitude, etc. Ground resource parameters: CC Slot, FS Slot, PM Slot, SE Slot, BPC Slot, UBPG Slot, Rack Topology, and Radio Mode, etc. Time Zone, NTP Server IP, and etc. Clock ID, GPS Sync Mode, GPS Cable Type, GPS Receiver Type, and GPS Feeder Delay, etc. Description
11
SN 6
Sheet Transmission
Description Transmission sheet: Transmission Type, Ethernet Work Mode, FE Bandwidth, FE Link Type, OMCB Gateway IP, and 1588 Sync Server IP, etc. 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. E1T1 Link ID, E1T1 Link Type, and HDLC Timeslot Map, etc. Transmission(ATM) sheet: ATM Transmission Medium, E1/T1 Number, and ATM Address, etc. 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. UMTS wireless parameters: NodeB ID, CE Up, CE Down, Dynamic Power Track, and Telecom Operator, etc. BPC Group, and etc. UMTS Sector ID, UMTS Sector Info, Related RU, and RX Type, etc. Local Cell ID, LCG ID, UMTS Sector ID, Transmitting Freq, Carrier Indication, Freq Spacing, Cell Radius, and Local Cell Type, etc. Sector ID, GPS Offset, and etc. TRX No., Channel Mode, Carrier Number of Logic Freq, Carrier Group, and Use IRC, etc. Dry contact related parameters
Transmission(IP)
8 9
Transmission(E1T1) Transmission(ATM)
10 11
RU UMTS Radio
12 13 14
UMTS Baseband Resource Pool UMTS Sector UMTS Local Cell
15 16 17
GSM Sector GSM Carrier Dry Contact
3.2
3.2.1
Specifications for Template Filling

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 ID
Specifications same as the BSC ID. If OMMB channel is managed by RNC (UMTS), SubNetwork ID is the same as RNC 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 BTS_NAME NE_ID 80 bytes at most. 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. This IP is unique in the whole network. It is the NodeB Managed IP. BS8700, BS8800 GU360, BS8800 U240, BS8800 U120, BS8800 U120A, BS8900 GU360, BS8900 U240, BS8800 GU360 E, BS8900 GU360 E, BS8900A, and BS8906 4.09.21.05. Value range: 0-4095. Do not fill in this item for single mode GSM sites. Value range: 0-65535. Do not fill in this item for single mode GSM sites. Value range: -180-180, accurate to six decimal places. Value range: -90-90, accurate to six decimal places. Optional. 40 bytes at most. Optional. 40 bytes at most. Optional. 80 bytes at most. Specifications
NE_IP SDR_TYPE SDR_VERSION RNC_ID BSC_ID LONGITUDE LATITUDE LOCATION VENDOR_NAME USER_DEFINED_STATE
3.2.3
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 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. 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. Value range: 1, 2. If there are two boards, fill in 1, 2 for this item. The CC board at Slot 1 is required. Value range: 3, 4. If there are two boards, fill in 3, 4 for this item. Value range: 14, 15. If there are two boards, fill in 14, 15 for this item. 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. 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. 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. Value range: 4-8. Do not fill in this item if no TAM is configured. TAM refers to tower amplifier. 0: TAM0. 1:TAM1. Do not fill in this item if no TAM board is configured. Value range of TAM0: 75, 400. Default: 250. Value range of TAM1: 75, 600. Default: 120. 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.
NE_ID
RADIO_MODE
CC_SLOT
FS_SLOT PM_SLOT
SE_SLOT
BPC_SLOT
UBPG_SLOT
TAM_SLOT
TAM_BOARD TAM_WORKING_CUR RENT
RACK_TOPOLOGY
14
Item FS_PORT_ASSIGN BATTERY_SAVING UES_SLOT EPM_PWR_TYPE EPM_DEAL_MODE
Specifications Options: Auto, Manual. Manual allocation is required if two FS boards are configured, i.e. the filed FS_PORT in RU sheet is required. Y: Enable; N: Disable. Integer: 3-8. ZXDU58 B900, ZXDU B121, ZXDU45-75, and ZXDU150 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 6HP 4HP
PM 2 PM 1 SA
FS2/BPC5/UBPG5 / FS1 CC2 CC1
TAM/BPC2/UBPG1 BPC1/UBPG2 BPC3/UBPG3 SE/BPC4/UBPG4 F A A
4HP 4HP 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 NE_ID Specifications 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. Required. It is the IP of OMMB server. Required. Format: GMT + H:MM, or GMT H:MM Format: MM-DD HH:mm. Fill in 0 if this parameter is not enabled. Format: MM-DD HH:mm. Fill in 0 if this parameter is not enabled.
NTP_SERVER_IP TIME_ZONE SUMMER_TIME_START SUMMER_TIME_END
3.2.5
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 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_ID2
CLOCK_ID3
16
Item
Specifications 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. 0: Input through cable 1. 1: Input through cable 2. 0: Built-in. 2: Slave shelf. Used for configuring cascaded GPS clock. Value range: 0-32767. Unit: ns.
GPS_SYNC_MODE
GPS_CABLE_TYPE GPS_RECEIVER_TYPE
GPS_FEEDER_DELAY
3.2.6
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 NE_ID Specifications 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. IUB interface transmission protocol: IP, ATM, ATM+IP. GSM supports only IP. Physical transmission medium of IUB interface: FE,GE,E1,T1 Options: Auto/1000M/100M/10M. Auto means selfadaptation. Default: Auto. Maximum bandwidth for Ethernet transmission: 1000000kbps (1000M). Minimum bandwidth for Ethernet transmission: 100kbps. Options: RNC/BSC/CN or SDR. Configure the lower-level base station as SDR, if cascaded configuration is adopted. If IP is adopted for IUB interface transmission protocol,
TRANSMISSION_TYPE TRANSMISSION_MEDIUM ETHERNET_WORK_MOD E FE_BANDWIDTH
FE_LINK_TYPE OMCB_GATEWAY_IP
17
Item
Specifications this item is filled in GLOBAL Supplemented Configuration. OMCB Gateway IP (also Agent IP) is used for NodeB management. 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. 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. 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. 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. 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.
OMCB_QOS
OMCB_CHANNEL
1588_SYNC_SERVER_IP
1588_IP_CHANNEL
1588_QOS
3.2.7
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 NE_ID SCTP_RADIO_MODE SCTP_LOCAL_PORT GSM or UMTS. 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 the Site ID. Value range: 0-65535. For GSM mode, the value is iBSC CMP module No. + 0x3900, which must be converted to a decimal number. Remote IP should not be the same as service IP, OMCB IP, or PPP IP. Value range: 1-6. 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. Value range: 2-4094. 65535 or null: Invalid. IP address and gateway address should be in the same network segment. Mask. The gateway of signaling service IP. Value range: 2-4094. 65535 or null: Invalid OMM IP address and OMM gateway address should be in the same network segment. Mask. The gateway of OMM IP address. 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. Required for PPP transmission. 0.0.0.0: Auto-negotiation Specifications Corresponding to the NE ID in Base Station sheet.
SCTP_REMOTE_PORT SCTP_REMOTE_IP SCTP_INOUT_STREAM
SCTP_QOS
IP_VLAN_ID IP_VLAN_IP_ADDR IP_VLAN_MASK IP_VLAN_GATEWAY OMM_VLAN_ID OMM_VLAN_IP_ADDR OMM_VLAN_MASK OMM_VLAN_GATEWAY
PPP_E1T1_LINKID
PPP_IP_ADDRESS
19
Item PPP_PROTOCOL
Specifications Required for PPP transmission. Options: PPP or ML-PPP. Default: ML-PPP. Options: RNC/BSC/CN or SDR. Default: RNC/BSC/CN. 0: Not support. 1: Support. Default: Not support. PPP transmission does not support IP header compression. Options: LONG, SHORT, and INVALID. Default: LONG. Valid when PPP Protocol is ML-PPP. Options: 1,2,3,4, and INVALID. Valid when PPP Protocol is ML-PPP.
PPP_LINK_TYPE
PPP_COMPRESSION
MP_HEAD
MP_PRIORITY
3.2.8
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 NE_ID E1T1_LINK_ID E1T1_LINK_TYPE Value range: 0-15. 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. Except Timeslot 0, Timeslots 1-31are available. Format: Start timeslot end timeslot. Segment the timeslots if they are discontinuous, e.g. 15,10-20. 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. Fill in this item only when cascaded connection is adopted. Value range: 0-7. Fill in this item only when cascaded connection is adopted. Specifications Corresponding to the NE ID in Base Station sheet.
HDLC_TIMESLOT_MAP
TSI_IN_TIMESLOT_MAP
TSI_OUT_LINK_ID TSI_OUT_TIMESLOT_MAP
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 NE_ID ATM_TRANSMISSION_MEDIUM E1T1_NUMBER Specifications Corresponding to the NE ID in Base Station sheet. E1,T1. Value range: 0-15, e.g. 0,1,3. 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. 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.
ATM_ADDRESS
RNC_IUB_BOARD
3.2.10
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 NE_ID RU_NO Specifications Corresponding to the NE ID in Base Station sheet. Value range of RRU No.: 51-74. Value range of RSU No.: 2-19. Optional. 80 bytes at most. Do not use characters < > & ' and ". UMTS, GSM, and GSM+UMTS. 4G+1U, 2G+2U, INVALID. Adopt INVALID for single mode. 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. It must be an integral multiple of 0.2MHz. 0 or Null means auto calculation by the base station
RRU_NAME RADIO_MODE GW_CONFIG_MODE
BOARD_TYPE
DOWNLINK_FREQ
22
Item equipment. UPLINK_FREQ
Specifications It must be an integral multiple of 0.2MHz. 0 or Null means auto calculation by the base station equipment. If DOWNLINK_FREQ is not 0, do not configure UPLINK_FREQ as 0. 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. For GSM only. Value range: 0-32. 0: Not group For GSM only. 1-6 are for DTR board series, and 1-2 are for TTR series For GSM only. Value range: 1-80. For GSM only. 0db, 2db, 4db, 6db, 8db, 10db, 12db, 14db, 16db, 18db, and 20db. N: Not connect with antenna. Y: Connect with antenna. If it is set as Y, RX Extension RU cannot be configured. The associated RUs should have the same frequency band. Each RU can be associated once only. For GSM only. This Sector ID must exist in GSM Sector sheet. 255: Invalid. 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. 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. 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. 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. For GSM only/ Value range: 0-6. The number of carriers in all sectors should be less than or
FS_PORT
CARRIER_GROUP CARRIER_NUMBER CARRIER_POWER_PA RA STATIC_POWER_LEVE L
RX_PORT_ANTENNA RX_EXTENSION_RU SECTOR_ID_1
TRX_NUMBER_1
SECTOR_ID_2
TRX_NUMBER_2
SECTOR_ID_3 TRX_NUMBER_3
23
Item
Specifications equal to the total number of carriers. 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. 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. 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. 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. 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. 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. For GSM only. Value range: 0-3. 0: Not enable sub-frequency band. ANT/RET. ANT: Common antenna; RET: Electric tilt antenna TMA, A-TMA, ETMA, and A-ETMA. This parameter and the following four ones are valid only for antenna type RET. TMA: 110-130 (0.1dB). A-TMA: 44-100(0.25dB). ETMA: 230-250 (0.1dB). A-ETMA: 92-100 (0.25dB). Invalid: 255. Value range: 70-170. Invalid: 255. Value range: 10-30. Value range: 0-80.
SECTOR_ID_4
TRX_NUMBER_4
SECTOR_ID_5
TRX_NUMBER_5
SECTOR_ID_6
TRX_NUMBER_6
SUB_FREQ_BAND
ANTENNA_TYPE TM_TYPE
RX_POWER_GAIN
TX_POWER_GAIN TMA_NOISE LINE_LOSS
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 1 GSM900M 2 3 DCS1800M 1 2 Sub-frequency Band Transmitting (downlink) Frequency Range(MHz) 935-960 925-950 935-951 1805-1860 1825-1880
3.2.11
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 NE_ID NODEB_ID CE_UP CE_DOWN DYNAMIC_POWER_TRAC K TELECOM_OPERATOR Specifications Corresponding to the NE ID in Base Station sheet. Value range: 0-65535. NodeB ID is the same as NE ID when UMTS mode is adopted. Value range: 1-1920. 65535: Invalid. Value range: 1-1920. 65535: Invalid. Y: Enable. N: Disable. Optional. 127 bytes at most. Do not use characters < > & ' and ". Value range: 0-50. Default: 0.
PASHARE_PER
25
Table 3-14 Rules of CE Configuration Site Configuration S111H S111M S111L S11H S11M S11L S222 S333 S444 O1M O1L O1Indoor O2Indoor S11Indoor S111Indoor S222Indoor Number of Uplink CEs 189 114 83 126 76 55 308 426 545 38 29 40 79 79 119 237 Number of Downlink CEs 123 79 48 82 53 32 171 219 267 27 16 16 32 32 48 96 Number of Cells 3 3 3 2 2 2 6 9 12 1 1 1 2 2 3 6
3.2.12
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 NE_ID LCG_ID Specifications Corresponding to the NE ID in Base Station sheet. Value range: 0-35; unique in the same NodeB. If there are two or more carriers, they should be in different baseband resource pools. Optional. 199 bytes at most. Do not use characters < > & and . 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
LCG_INFO BPC_GROUP
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 NE_ID UMTS_SECTOR_ID UMTS_SECTOR_INFO Specifications Corresponding to the NE ID in Base Station sheet. Value range: 0-255; unique in the same site. Optional. 199 bytes at most. Do not use characters < > & ' and ". RU No. If OTSR/M-RRU is adopted, the format should be RU1&RU2&. 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. 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.
RELATED_RU
RX_TYPE
RFRX_ORDER
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 NE_ID LOCAL_CELL_ID LOCAL_CELL_INFO UMTS_SECTOR_ID LCG_ID TRANSMITTING_FREQ Specifications Corresponding to the NE ID in Base Station sheet. Value range: 0-268435455; unique in the same subnetwork. Optional. 199 bytes at most. Do not use characters < > & ' and ". Cited from UMTS Sector sheet. Cited from UMTS Baseband Resource Pool sheet. Refer to Table 3-18 for the value range. The value should be an integral multiple of 0.2MHz. 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. 5M, 4.8M, 4.6M, 4.4M, 4.2M, 4.4M and 4.2M are applicable only to single mode UMTS R8860. 2.5km/5km/10km/20km/40km/80km/120km. Value range: 0-200. 255: Invalid. 0: Common cell. 1: High-speed railway cell. As to the specifications of configuring high-speed railway cells, please refer to the following text. 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. Value range: 0-65535. Default: 23 Value range: 0-65535. Default: 13. Y: Enable. N: Disable
CARRIER_INDICATION
FREQ_SPACING CELL_RADIUS LOCAL_CELL_POWER
LOCAL_CELL_TYPE
DC_LOCAL_CELL
TRANSMIT_DELAY RECEIVE_DELAY BATTERY_SAVING
28
Item LOCAL_CELL_2MS_GAIN
Specifications Enable: Support. Disable: Not support. Y: Support. N: Not support. Configure this parameter as Y only when the RX Type is MIMO/MIMO-II.
LOCAL_CELL_VAM
The Downlink Frequency should be an integral multiple 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 following requirements: 1. 2. The Carrier Indication should be unique within the same sector; 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 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.
3.
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. 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. The resource pool with only 2-RRU cells can be configured with three local cells at most. The baseband resource pool with only M-RRU(M>2) cells can be configured with two cells at most. When both M-RRU(M>2) cells and 2-RRU cells are configured, only one M-
2.
3.
4.
5.
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. 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. 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. 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.
7.
8.
9.
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; 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. A Baseband resource pool with only one baseband board can be configured with only one cell with ultra-wide coverage at most. A Baseband resource pool with two baseband boards can be configured with only two cells with ultra-wide coverage at most. A Baseband resource pool with three or more baseband boards can be configured with three cells with ultra-wide coverage at most.
2.
3.
4.
5.
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. The radius of high-speed railway cells can only be 2.5km or 5km. M-RRU(M>2) high-speed railway cells and OTSR high-speed railway cells cannot share the same baseband resource pool. 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.
2. 3.
4.
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. 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. 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. 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. 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.
6.
7.
8.
9.
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) 1920 1850 1710 824 880 Upper Limit (MHz) 1980 1910 1785 849 915 Transmitting Frequency Lower Limit(M Hz) 2110 1930 1805 869 925 Upper Limit(M Hz) 2170 1990 1880 894 960 Spacing Between Receiving and Transmitting Frequency (MHz) 190 80 95 45 45
Board Type
2.1G(Band I) 1900M(Band II) 1800M(Band III) 850M(Band V) 900M(Band VIII)
A E D B 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 NE_ID SECTOR_ID GPS_OFFSET POINT1_RU_NO POINT2_RU_NO Value range: 1-24. Value range: 0-50. POINT1 RU NO and POINT2 RU NO should be configured together. It is not necessary to fill this item if it is not configured. It is not necessary to fill this item if it is not configured. Specifications Corresponding to the NE ID in Base Station sheet.
3.2.16
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

NE_ID SECTOR_ID
Specifications Corresponding to the NE ID in Base Station sheet. Value range: 1-24. 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.
TRX_NO
32
Item
CHANNEL_MODE
Specifications SINGLE: channel. DUAL: Dual channel. MULTI: Multi-channel Value range: 1-12. This value should be smaller than the sum of carriers on all RRUs in this cell. Value range: 0-32. 0: Not group. Do not fill in this item, if the logic TRX No. is generated automatically. 2.1G,1900M,1800M,850M,900M Do not fill in this item, if the logic TRX No. is generated automatically. 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. 1: Use. 0: Not use. 1: Yes. 0: No.
CARRIER_NUMBER_OF_LOGIC_FREQ
CARRIER_GROUP
FREQ_BAND
SUB_FREQ_BAND
USE_IRC EXTENSION_CARRIER
3.2.17
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 NE_ID RACK_NO Specifications Corresponding to the NE ID in Base Station sheet. Main rack No.: 1. Remote racks are numbered from 2. 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. The Slot No. of the SA board on B8200(B8700) is13. The Slot No. of the SE board is 5.
SHELF_NO
SLOT_NO
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). 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 Cabinets lightning arrestor alarm (or not configured); No. 1 cannot be configured; for 200 series, Nos. 24 cannot not be configured. 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. 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.
DRY_CONTACT_NO
DRY_CONTACT_AL ARM_CODE
DRY_CONTACT_TY PE
DRY_CONTACT_CO NTENT ALARM_STATUS DRY_CONTACT_OU TPUT_STATUS
Table 3-22 Description of Dry Contact Alarms Value 198092044 198092045 198092046 198092047 198092048 198092049 198092051 198092052 198092068 198092206 198092207 Cabinet door alarm Flooding Fault Smoke alarm/SMOG Fault Infrared alarm Air-condition fault Cabinets lightning arrestor alarm PSU alarm PSU fan alarm Base station master power supply break alarm Battery Fault AC power-cut alarm Description
34
Value 198092208 198092209
Description Rectifier model alarm 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.
SD O R_C NFTO L_UM O TS_D O EM _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
5.1
Special Subject for Quick Data Configuration

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
Figure 5-15 Rules for Naming RSUs
Rules for Naming RSUs

RSU Xn - Xn Xn X
Power Frequency band (n characters , two digits usually adopted ) Radio mode (n characters) Structure type (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
Structure type
40: R8840, 60: R8860, 80: R8880, 02: RU02
5.2
Special Subject for IUB Bandwidth Configuration

On the IUB interface for E1/T1 transmission, the quick data configuration should be based on the rules in ZXWR RNC IubPVC_configurationTool_English.xls.
ZXW RN R C I ubPVC_conf i gurat i onTool _Engl i sh- new xl s .
38

U - ST - ZXSDR (V4.09.21) Quick Data Configuration Guide - R.1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

U - ST - ZXSDR (V4.09.21) Quick Data Configuration Guide - R.1

Hochgeladen von

Copyright:

Verfügbare Formate

U_ST_ZXSDR(V4.09.

21) Quick Data Configuration Guide

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

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

About This Document

Applicable to: UMTS NodeB commissioning engineers

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Description of Version Change

Introduction to Quick Data Configuration

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-1 SDR Data Quick Configuration System

ZXSDRConfTool template in the XLS format

NodeB configuration data (XML format )

NodeB configuration data on OMC

Switch data with ZXSDRConfTool

Export NE data in batch

Synchronize data to NodeB with EOMS

SDR base station

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-2 Workflow at the Initial Stage of Commissioning

STEP 2: Data generation

STEP 3: Data synchronization

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-3 Configuring Output SDR XML File Directory

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-4 Generating NodeB Configuration Data

Batch Offline Reverse (XML to M31)

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-5 Batch Offline Reverse

Figure 2-6 Setting ConfigSet Label

ZTE Confidential Proprietary

2012 ZTE CORPORATION. All rights reserved.

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

Figure 2-7 Applying for Mutex Right in Batch

Figure 2-8 Batch Switch ConfigSet

Exporting NE Data in Batch (M31 to XML)