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. ZTE’s 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, 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 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 CORPORATION’s products and technologies. ZTE CORPORATION Address : NO. 55 Hi-tech Road South ShenZhen P.R.China 518057 http://dms.zte.com.cn (Technical Support) [email protected] Website : Email: ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. I U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide Internal Use Only ▲ 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 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. II U_ST_ZXSDR(V4.09.21) Quick Data Configuration Guide Internal Use Only ▲ 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 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. All rights reserved. III ................2...............................................................2.................11 3..........5 Synchronizing Configuration Data on Site (XML to SDR)...............4 Converting Configuration Data in Batch (XML to XLS).................2..................................................9 2...............................................3 2........................................2.................................2 2.................................1 Introduction to Templates.......2.............................20 3........................................36 5 Special Subject for Quick Data Configuration...................................2 Base Station...................................12 UMTS Baseband Resource Pool................2 Specifications for Template Filling.....................0)..............................4 Example 4: SDR_8800_OTSR_IPOE................................................................12 3..........1 2 Introduction to Quick Data Configuration......1 Brief Introduction.........................................................2....................................................................................2.... All rights reserved..........2 Example 2: SDR_8700_OTSR_ATM+IP..............................17 3............................................09........3...35 4....9 Transmission(ATM)..............................................................................................................................26 3.........................13 3...............................................................3 2.............................2........... IV ..................3 Equipment...1.................................................................33 4 Examples of Template Filling.....................................10 RU 21 3..................................................................................1........................................................15 GSM Sector.....................................35 4...................................2..............................................35 4.........18 3......................................3 Exporting NE Data in Batch (M31 to XML)...........................................13 3............................5 Clock..............12 3....................................................3..............................11 UMTS Radio...8.....21) Quick Data Configuration Guide Internal Use Only ▲ TABLE OF CONTENTS 1 Description of Version Change.............7 2.........31 3.....................................U_ST_ZXSDR(V4............2..................2 Workflow......................................7 Transmission(IP)..................................32 3..................1 2...1 Rules for Naming RUs.11 3..................................2...........27 3.................................................................................................2..............................17 Dry Contact......................................14 UMTS Local Cell......28 3...............5 2.......10 3 Specifications for Template Filling............................................................................2............................................................1 Example 1: SDR_8700_STSR_ATM..............13 UMTS Sector......36 5...............................................................................1 2......4 Time 16 3........................................................3.................................2.................................................................................2.....1 Generating Configuration Data in Batch (XLS to XML)................1 SubNetwork...........................................................2.......................25 3...6 Transmission.16 GSM Carrier....3 Data Conversion.............................................................1 1........................................................16 3....................3.3 Example 3: SDR_8800_STSR_IP..............................................................................................38 ZTE Confidential Proprietary © 2012 ZTE CORPORATION.......................................................2.......................1 Classification of Templates................................................1 ZXSDRConfTool (V2......2 Description of Each Sheet...................11 3...........................................................2 Special Subject for IUB Bandwidth Configuration ...............................3........................................................................................................................8 Transmission(E1T1)...21 3...........11 3..............................................36 4................................................36 5................................................2 Batch Offline Reverse (XML to M31).......................................... ........5 Figure 2-5 Batch Offline Reverse.................................................................................6 Figure 2-7 Applying for Mutex Right in Batch...........................................................................................4 Figure 2-4 Generating NodeB Configuration Data..............................6 Figure 2-6 Setting ConfigSet Label...........7 Figure 2-8 Batch Switch ConfigSet..............................................................................................................................10 Figure 5-14 Rules for Naming RRUs ......................... All rights reserved...............................................................................................................7 Figure 2-9 Batch Export NE Data..................8 Figure 2-11 Selecting an SDR XML File Directory............................................................................9 Figure 2-12 Output Directory and File Name............37 Figure 5-15 Rules for Naming RSUs.10 Figure 2-13 Prepared Data of Entire Table Configuration..............................................U_ST_ZXSDR(V4.... V ......................................................09...................................................................8 Figure 2-10 Choosing NE Export Directory........................................................38 TABLES ZTE Confidential Proprietary © 2012 ZTE CORPORATION..3 Figure 2-3 Configuring Output SDR XML File Directory................................................................................................2 Figure 2-2 Workflow at the Initial Stage of Commissioning..................................21) Quick Data Configuration Guide Internal Use Only ▲ FIGURES Figure 2-1 SDR Data Quick Configuration System............................................. ...............................................25 Table 3-14 Rules of CE Configuration ...........................................32 Table 3-21 Dry Contact Sheet............................................................................................................31 Table 3-19 GSM Sector Sheet...................................14 Table 3-5 Time Sheet.........................................26 Table 3-15 UMTS Baseband Resource Pool Sheet....28 Table 3-18 Frequency Band Range.................................................21 Table 3-11 RU Sheet..........................................................................................17 Table 3-8 Transmission(IP) Sheet............................32 Table 3-20 GSM Carrier Sheet......13 Table 3-4 Equipment Sheet..................... VI ......26 Table 3-16 UMTS Sector Sheet....................................................12 Table 3-3 Base Station Sheet.......................................................25 Table 3-13 UMTS Radio Sheet..............................................................................................21) Quick Data Configuration Guide Internal Use Only ▲ Table 3-1 Sheets in ZXSDRConfTool Template......................................................................................................................27 Table 3-17 UMTS Local Cell Sheet.......22 Table 3-12 Range of GSM Sub-frequency Band.....................................................................................................................................................................................................................19 Table 3-9 Transmission(E1T1) Sheet.................................................................................................................................U_ST_ZXSDR(V4......................................................20 Table 3-10 Transmission(ATM) Sheet................................................................34 ZTE Confidential Proprietary © 2012 ZTE CORPORATION.............16 Table 3-7 Transmission Sheet.......................................................................................................................................................33 Table 3-22 Description of Dry Contact Alarms...................................................................................................16 Table 3-6 Clock Sheet..................................................... All rights reserved................................11 Table 3-2 SubNetwork Sheet.................................................................................................................................................................................................09..... 1. and is incompatible with SDR base station V4.0) ZXSDRConfTool(V2.0) are quite different from those of SdrConfTool versions. as shown in Figure 2-1.05 only. The templates support SDR base station V4. All rights reserved.21.09. aims to fulfill quick configuration of SDR data.21) Quick Data Configuration Guide Internal Use Only ▲ 1 Description of Version Change This chapter describes the changes in the templates and functions of SDR Quick Configuration Tools (ZXSDRConfTool). and the planning data starts from the fourth line. 1.U_ST_ZXSDR(V4.21. 3. Please refer to 2.00 and earlier versions.09. Please use the latest ZXSDRConfTool version.1 Introduction to Quick Data Configuration Brief Introduction SDR data quick configuration.05. as detailed below. 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.8.1 ZXSDRConfTool (V2. 1 . Each ZXSDRConfTool version is updated within six months.8.09.3 Data Conversion for detailed operation. XML files generated by LMT can be loaded into the templates. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. based on NodeB configuration data. 2 2. only one file each time. The templates of ZXSDRConfTool(V2.0) supports only SDR base station V4.8. 2. Specifications for template filling are added in the templates. Then. we can fulfill quick configuration of NodeB through two ways: 1. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. and generate NodeB configuration data (in the XML format) with ZXSDRConfTool.09. 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. synchronize the data to the NodeB with EOMS. 2 .21) Quick Data Configuration Guide Internal Use Only ▲ 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.U_ST_ZXSDR(V4. load the data into OMC with Batch Offline Reverse function and then synchronize the data to the NodeB. All rights reserved. 3.21) Quick Data Configuration Guide Internal Use Only ▲ 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. and then restore the data to a ZXSDRConfTool template with data conversion function. The same as EOMS. 2.09. All rights reserved. Otherwise. JRE should be installed if ZXSDRConfTool is used for the first time. if the data filled in the ZXSDRConfTool template is not the same as the data on the OMC.U_ST_ZXSDR(V4.exe to install JRE.xx\JRE\jre-6u10-windows-i586-p. 3 . run BLMT_V4. we can use Batch Export NE Data function to generate NodeB configuration data (in the XML format).3 2.00. If EMOS was run. so as to fulfill data batch modification. ZTE Confidential Proprietary © 2012 ZTE CORPORATION.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.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. this means JRE has been installed. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. The method for data generation is as below: STEP 1: Run ZXSDRConfTool. Figure 2-3 Configuring Output SDR XML File Directory STEP 2: Click Generate XML File.09. as shown in Figure 2-3. please refer to 3 Specifications for Template Filling for details.U_ST_ZXSDR(V4. as shown in Figure 2-4. and set an output directory in Output SDR XML File Directory and a template in SDR EXCEL File.jar. and the corresponding XML file will be generated in the specified output directory. 4 .21) Quick Data Configuration Guide Internal Use Only ▲ As to the methods for filling in templates. All rights reserved. the detailed error information will be displayed in the Operation Result. as shown in Figure 2-5. 2.09. because OMC will create an OMCB Managed Element automatically.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 2-4 Generating NodeB Configuration Data Caution: If data generation fails. 5 .U_ST_ZXSDR(V4.3. It is unnecessary to create an OMCB Managed Element before performing Batch Offline Reverse. STEP 1: Choose SDR Management > Data Configuration > Batch Offline Reverse. and then we can use the Batch Offline Reverse function on the OMC to generate OMC data in batch.2 Batch Offline Reverse (XML to M31) Put XML files in a folder. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. and the content in the ZXSDRConfTool template should be modified. All rights reserved. If an NE already exists. a new Configuration Set will be created. 6 . and Select the correct subnetwork. Click OK. fill in ConfigSet Label. and switch to the master configuration set. as shown in Figure 2-6.U_ST_ZXSDR(V4. perform all-table synchronization. Figure 2-6 Setting ConfigSet Label STEP 3: Choose Configuration Management > Mutex Management > Select All. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. as shown in Figure 2-7.09.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 2-5 Batch Offline Reverse STEP 2: Select the folder of XML files. All rights reserved. After OMCB link is set up. as shown in Figure 2-7. 7 .3 Exporting NE Data in Batch (M31 to XML) STEP 1: Choose SDR Management > Data Configuration > Batch Export NE Data. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Figure 2-8 Batch Switch ConfigSet 2.09. as shown in Figure 2-9. as shown in Figure 2-8.3.21) Quick Data Configuration Guide Internal Use Only ▲ 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. All rights reserved.U_ST_ZXSDR(V4. Otherwise.09. 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. and click OK. All rights reserved. as shown in Figure 2-10. the export will fail.U_ST_ZXSDR(V4.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 2-9 Batch Export NE Data STEP 2: Select the NE to be exported and an export directory. 8 . ZTE Confidential Proprietary © 2012 ZTE CORPORATION. 09.3. 9 . Only XML files exported from OMMB or generated by ZXSDRConfToolV2.U_ST_ZXSDR(V4.jar file of ZXSDRConfTool. and click Next. as shown in Figure 2-11. STEP 1: Run the SdrQuickConf. as detailed below. the name of the EXCEL file).1 (or later versions) can be converted to XLS files directly.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. and set SDR XML File Directory. All rights reserved. Caution: XML files generated by EMOS cannot be converted to XLS files directly. choose File > XML -> XLS. Figure 2-11 Selecting an SDR XML File Directory STEP 2: Set Output Directory and File Name (i.1. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Click Next.e.21) Quick Data Configuration Guide Internal Use Only ▲ 2. as shown in Figure 2-12. 3. STEP 2: Choose System > Entire Table Configuration > Prepared Data and select the XML file and click OK.09.U_ST_ZXSDR(V4.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 2-12 Output Directory and File Name 2. All rights reserved. and log in to a base station. Then the configuration data is loaded to the base station. as shown in Figure 2-13. 10 . Figure 2-13 Prepared Data of Entire Table Configuration ZTE Confidential Proprietary © 2012 ZTE CORPORATION.5 Synchronizing Configuration Data on Site (XML to SDR) STEP 1: Start EOMS. U_ST_ZXSDR(V4. NTP Server IP. GPS Receiver Type.21. Rack Topology.05_QUICKCONF_TEMPLATE_GU” might be copied into the other two sheets as required. SE Slot. BPC Slot.09.05_QUICKCONF_TEMPLATE_UMTS In the three templates above. Sites in one EXCEL file are in the same sub-network. NE IP. Parameters in each template should be configured according to the actual situation. and some sheets may be omitted in different application scenarios. Please refer to 3. and etc. etc.21) Quick Data Configuration Guide Internal Use Only ▲ STEP 3: After restarting the base station. 3. and Radio Mode. 11 . Time Zone. Clock ID.05_QUICKCONF_TEMPLATE_GU SDR_4.09.09. GPS Cable Type.09. etc. Description ZTE Confidential Proprietary © 2012 ZTE CORPORATION.1. SDR Version. etc. In special scenarios. GSM mode and UMTS mode respectively. 3 Specifications for Template Filling This chapter deals with the methods and notices of filling in ZXSDRConfTool templates.21. and Latitude. check its running status.21. so as to perform data configuration. the fields in template “SDR_4. Ground resource parameters: CC Slot. Longitude.    SDR_4. 3. and GPS Feeder Delay. used for GSM/UMTS dual mode. and perform commissioning test or service test. FS Slot.21.05_QUICKCONF_TEMPLATE_GSM SDR_4. NE ID. 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.2 Specifications for Template Filling for details. SDR Type. All rights reserved.1. UBPG Slot. GPS Sync Mode.09. the number of fields is variable in each sheet.1 3. An EXCEL file has 17 sheets at most.2 Description of Each Sheet An EXCEL file in a special format is used for filling in SDR parameters.1 Introduction to Templates Classification of Templates ZXSDRConfTool has three templates. PM Slot. CE Up. PPP Compression. BPC Group. Dry contact related parameters 7 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. Related RU. Table 3-2 SubNetwork Sheet Item SubNetwork Specifications If OMMB channel is managed by BSC (GSM). etc. Transmitting Freq. etc. All rights reserved. SCTP Remote Port. and ATM Address. etc. etc.2 3. FE Link Type. OMCB Gateway IP.09. etc. PPP IP Address. 12 . Carrier Number of Logic Freq. etc. “Transmission (IP)” sheet: SCTP Radio Mode. GW Config Mode. CE Down. and MP Priority. FE Bandwidth. Carrier Number. E1T1 Link ID. Carrier Group. “Transmission(ATM)” sheet: ATM Transmission Medium. E1T1 Link Type. SCTP QoS. OMM VLAN IP. and etc. etc. Sector ID. and 1588 Sync Server IP. PPP Protocol. and HDLC Timeslot Map. Radio Mode. which is used for filling in subnetwork ID. SCTP Inout Stream. TRX No. Carrier Power Para.U_ST_ZXSDR(V4. Dynamic Power Track. Sub Freq Band. IP VLAN Mask. All base stations in this Excel file are in this subnetwork. RU No. Freq Spacing.1 Specifications for Template Filling SubNetwork This sheet contains only one line. Ethernet Work Mode. Carrier Indication.2. PPP E1T1 LinkID. Cell Radius. PPP Link Type. Channel Mode. GPS Offset. and etc. Local Port. SCTP. Board Type. LCG ID. UMTS Sector ID. Local Cell ID.21) Quick Data Configuration Guide Internal Use Only ▲ SN 6 Sheet Transmission Description “Transmission” sheet: Transmission Type. and RX Type. and Use IRC. UMTS wireless parameters: NodeB ID. Downlink Freq. IP VLAN IP Addr. IP VLAN ID. and Antenna Type. Carrier Group. UMTS Sector Info. etc. SubNetwork ID is the ZTE Confidential Proprietary © 2012 ZTE CORPORATION. and Local Cell Type. TRX Number. OMM VLAN IP Addr.. Uplink Freq. E1/T1 Number. and Telecom Operator.. UMTS Sector ID. etc. SCTP Remote IP. 09. SubNetwork ID is the same as RNC ID. BS8900 GU360 E. accurate to six decimal places.21) Quick Data Configuration Guide Internal Use Only ▲ Item ID Specifications same as the BSC ID.2. Optional. BS8700. BS8900A. 3. This IP is unique in the whole network. 40 bytes at most. corresponding to a base station (including GSM/UMTS dual mode base station). unique within a subnetwork. Value range: -180-180. accurate to six decimal places. Base stations with the same hardware configuration in a subnetwork might be ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Value range: 0-65535. If OMMB channel is managed by RNC (UMTS). Optional. Do not fill in this item for single mode GSM sites. BS8800 GU360. Table 3-3 Base Station Sheet Item BTS_NAME NE_ID 80 bytes at most.21. It is the NodeB Managed IP. All rights reserved.2. Each NE occupies one line. and must be filled in. 80 bytes at most. Do not fill in this item for single mode GSM sites. 13 . Value range: -90-90. BS8800 U120A.2 Base Station Each base station occupies one line (including GSM/UMTS dual mode base station). BS8900 U240. BS8800 U120. Optional. Items in this sheet are corresponding to that in the SDR Managed Element on OMMB. The NE ID is the same as the NodeB ID when UMTS mode is adopted.3 Equipment This sheet deals with the configuration of SDR hardware. BS8900 GU360. Value range: 0-4095.05. and is the same as the Site ID when GSM mode is adopted. and BS8906 4. BS8800 GU360 E. 40 bytes at most.U_ST_ZXSDR(V4.09. Specifications NE_IP SDR_TYPE SDR_VERSION RNC_ID BSC_ID LONGITUDE LATITUDE LOCATION VENDOR_NAME USER_DEFINED_STATE 3. Value range: 0-65535. BS8800 U240. 6. If there are two boards. Separate the values with coma if there are two or more BPC boards.09.7. Value range of TAM0: 75. RRU 51 is also connected to an FS optical port. fill in “ALL” for this item.g. Default: 250. fill in “3. 1:TAM1. Please check and confirm the configuration during the planning stage. because it is very difficult to modify this parameter on OMCB. The CC board at Slot 1 is required. 15” for this item. TAM refers to tower amplifier. If all base stations within a subnetwork have the same ground resource parameters.7. 14 . SE board supports 16 E1 cables. 600. Do not fill in this item if SE board is not configured. Do not fill in this item if there is no cascaded RU. Each FS optical port can have four cascaded RUs at most. Value range: 3. Options: UMTS. 400.8. Value range: 5-8 slot. Do not fill in this item if no TAM board is configured. 0: TAM0.8. GSM. If there are two boards. All rights reserved. 1-4. only one board can be installed. 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 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. 2.e. Separate the values with coma if there are two or more UBPG boards. If there are two boards. instead of using one line for each NE. RSU 3 is cascaded with RSU 2. 1-51-52. Please refer to Table 3-4 for details. e. and RRU 52 is cascaded with RRU 51. fill in “14. RSU 2 and RSU 4 are connected to an FS optical port. If there are a few base stations with different ground resource parameters. Value range: 4-8. Do not fill in this item if no TAM is configured. 15. Required if UMTS mode is adopted.U_ST_ZXSDR(V4. Default: 120. Required if UMTS mode is adopted. 2” for this item. 6. Value range: 4-8. Value range: 4-8. Example: “1-2-3. Table 3-4 Equipment Sheet Item Specifications Corresponding to the NE ID in “Base Station” sheet. Value range: 14.21) Quick Data Configuration Guide Internal Use Only ▲ reduced to one line. fill them in the first lines before the “ALL” line. fill in “1. Value range of TAM1: 75. 4. 4” for this item.g.” i. GSM+UMTS. Value range: 1. e. N: Disable. If TAM is configured. ZXDU58 B900. The slots for installing boards in B8200 rack are as shown below. i.09.e.21) Quick Data Configuration Guide Internal Use Only ▲ Item FS_PORT_ASSIGN BATTERY_SAVING UES_SLOT EPM_PWR_TYPE EPM_DEAL_MODE Specifications Options: Auto. 6HP 6HP 4HP PM 2 PM 1 SA FS2/BPC5/UBPG5 / FS1 CC－2 CC－1 TAM/BPC2/UBPG1 BPC1/UBPG2 BPC3/UBPG3 SE/BPC4/UBPG4 F A A 4HP 4HP 4HP 4HP ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Manual allocation is required if two FS boards are configured. the filed FS_PORT in “RU” sheet is required. ZXDU45-75. 1: Parse It is recommended that boards in single mode B8200 rack be installed according to the following figure. All rights reserved. Manual. and ZXDU150 0: Transparent transmission. Y: Enable. ZXDU B121. 15 .U_ST_ZXSDR(V4. it is recommended that the boards in GSM/UMTS dual mode B8200 rack be installed according to the figure below. Integer: 3-8. Table 3-5 Time Sheet Item NE_ID Specifications Corresponding to the NE ID in “Base Station” sheet. instead of using one line for each NE.09. which applies to all of the following sheets. corresponding to a base station (including GSM/UMTS dual mode base stations).2. If all base stations within a subnetwork have the same clock parameters. LINE: The reference clock acquired from E1/T1 cable – CC board. All rights reserved. It deals with time synchronization of NodeB.4 Time This sheet must be filled in. 16 . BITS-2Mbps: BITS-2Mbps clock. Required. NTP_SERVER_IP TIME_ZONE SUMMER_TIME_START SUMMER_TIME_END 3. SyncE: Synchronization Ethernet clock. or GMT – H:MM Format: MM-DD HH:mm. fill in “ALL” for this item. CLOCK_ID1 GPS: Built-in GPS. CLOCK_ID2 CLOCK_ID3 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Table 3-6 Clock Sheet Item NE_ID Specifications Corresponding to the NE ID in “Base Station” sheet. instead of using one line for each NE.U_ST_ZXSDR(V4. Usually. 1588: IP reference clock source. BITS-2MHz: BITS-2MHz clock.2. Required. It is the IP of OMMB server. and we may fill in “ALL” for this item. Format: GMT + H:MM. Fill in “0” if this parameter is not enabled.5 Clock Each NE occupies one line. Format: MM-DD HH:mm. all base stations within a subnetwork contain the same time parameters. Fill in “0” if this parameter is not enabled.21) Quick Data Configuration Guide Internal Use Only ▲ 3. The NE ID must be in column A. 2: Slave shelf. GSM supports only IP. 17 . All rights reserved. TRANSMISSION_TYPE TRANSMISSION_MEDIUM ETHERNET_WORK_MOD E FE_BANDWIDTH FE_LINK_TYPE OMCB_GATEWAY_IP ZTE Confidential Proprietary © 2012 ZTE CORPORATION.2. 0: Input through cable 1. Unit: ns. Default: Auto. Used for configuring cascaded GPS clock. 1: Input through cable 2. 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. 0: GSM/UMTS frequency synchronization 1: GSM frame No. Minimum bandwidth for Ethernet transmission: 100kbps. Auto means selfadaptation. GPS_SYNC_MODE GPS_CABLE_TYPE GPS_RECEIVER_TYPE GPS_FEEDER_DELAY 3. one line for each base station (including GSM/UMTS dual mode base stations). Maximum bandwidth for Ethernet transmission: 1000000kbps (1000M). Do not fill in this item if other clocks are adopted.E1.6 Transmission This sheet must be filled in. Physical transmission medium of IUB interface: FE.T1 Options: Auto/1000M/100M/10M. All base stations with the same configuration might be reduced to one line. Options: RNC/BSC/CN or SDR.09. Value range: 0-32767. UMTS frame No.U_ST_ZXSDR(V4. if cascaded configuration is adopted. Configure the lower-level base station as SDR.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications This parameter is valid only when GPS clock is adopted. 3: GSM/UMTS frame No. If IP is adopted for IUB interface transmission protocol. entire network synchronization. 0: Built-in. ATM+IP. instead of using one line for each NE. IUB interface transmission protocol: IP. ATM. entire network synchronization. entire network synchronization 2: GSM frequency synchronization.GE. one line for GSM. …” might be adopted. one for service channel. 18 . AF23: service class 2. If Ethernet transmission is adopted. BE: Try the best (default). Discarding priority: medium. Required when GSM/UMTS dual mode is adopted. Required when GSM/UMTS dual mode is adopted and IEEE1588 is used for reference clock source. AF42: service class 4. or IPOE transmission is adopted. Discarding priority: high. if single mode is adopted. each NE occupies one line. EF: EF service. AF22: service class 2. This parameter indicates whether OMC-B channel is established on iBSC or on RNC. and maximum flow (default).U_ST_ZXSDR(V4. BE: Try the best. EF: EF service. Do not fill in this item. shortest time delay. AF43: service class 4.2. For GSM/WCDMA dual mode. format “IP1. Discarding priority: high. accelerated retransmission. Discarding priority: high. If each site is configured with only one IP address. AF22: service class 2. Four IP addresses are allowed at most. If PPP ZTE Confidential Proprietary © 2012 ZTE CORPORATION. the other for OMC channel. each NE occupies two lines. i. ATM+IP. OMCB Gateway IP (also Agent IP) is used for NodeB management. OMCB_QOS OMCB_CHANNEL 1588_SYNC_SERVER_IP 1588_IP_CHANNEL 1588_QOS 3. two IP VLANs at most can be configured at each line. Discarding priority: medium. Discarding priority: high.09. Value GSM/UMTS indicates whether IP channel is established on iBSC or on RNC. shortest time delay. only one IP VLAN.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications this item is filled in GLOBAL Supplemented Configuration. fill in only IP VLAN property. Discarding priority: medium. Required when IEEE1588 is used for reference clock source. Discarding priority: medium.e. accelerated retransmission. and maximum flow. AF42: service class 4. For GSM single mode or WCDMA single mode. Valid only in Ethernet transmission.7 Transmission(IP) Please fill in this sheet if IP. if single mode is adopted.IP2. AF23: service class 2. Do not fill in this item. If there are two or more 1588 servers. do not fill in PPP related parameters. AF43: service class 4. For Ethernet transmission. All rights reserved. the other for WCDMA. AF42: service class 4. shortest time delay.21) Quick Data Configuration Guide Internal Use Only ▲ transmission is adopted. Separate the values with coma if there are two or more links. It is the GSM Site ID if GSM mode is adopted. and the value range is 1-1536.0. AF23: service class 2.1. Value range: 2-4094. e.U_ST_ZXSDR(V4. Remote IP should not be the same as service IP. 65535 or null: Invalid. Table 3-8 Transmission(IP) Sheet Item NE_ID SCTP_RADIO_MODE SCTP_LOCAL_PORT GSM or UMTS. 0. or PPP IP. This item is required for PPP transmission. 65535 or null: Invalid OMM IP address and OMM gateway address should be in the same network segment. “0. If the transmission media is E1/T1.2”. accelerated retransmission. Mask. AF43: service class 4. do not fill in VLAN related parameters. GSM NE ID is the same as the Site ID. AF22: service class 2. IP address and gateway address should be in the same network segment. 19 . Discarding priority: high.0. All rights reserved. For GSM mode. Mask. EF: EF service.0: Auto-negotiation Specifications Corresponding to the NE ID in “Base Station” sheet. + 0x3900.09. Discarding priority: medium. Discarding priority: medium.g. Required for PPP transmission. 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 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Value range: 1-6. Value range: 0-15. which must be converted to a decimal number. BE: Try the best. The gateway of OMM IP address. Discarding priority: high. OMCB IP. The gateway of signaling service IP. please set E1T1 Link Type and HDLC Timeslot Map in “Transmission (E1T1)”sheet. Value range: 0-65535. the value is iBSC CMP module No. and maximum flow (default). Value range: 0-65535. 8 links can be filled in at most. Value range: 2-4094. “15. if PPP transmission is adopted. Valid when PPP Protocol is ML-PPP. Default: RNC/BSC/CN. Options: RNC/BSC/CN or SDR.21) Quick Data Configuration Guide Internal Use Only ▲ Item PPP_PROTOCOL Specifications Required for PPP transmission.3. e. and INVALID. Options: RNC/BSC/CN or SDR. Valid when PPP Protocol is ML-PPP. Segment the timeslots if they are discontinuous. 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. Default: LONG. Table 3-9 Transmission(E1T1) Sheet Item NE_ID E1T1_LINK_ID E1T1_LINK_TYPE Value range: 0-15. Default: Not support. Timeslots 1-31are available. Options: LONG. Default: ML-PPP. and INVALID. HDLC_TIMESLOT_MAP TSI_IN_TIMESLOT_MAP TSI_OUT_LINK_ID TSI_OUT_TIMESLOT_MAP ZTE Confidential Proprietary © 2012 ZTE CORPORATION. 20 . Except Timeslot 0. 0: Not support.” Fill in this item only when cascaded connection is adopted.4. Specifications Corresponding to the NE ID in “Base Station” sheet. Options: 1.g. it cannot be connected with RNC and BSC at the same time. PPP transmission does not support IP header compression.2. Options: PPP or ML-PPP. All rights reserved. Note: If there is only one E1 cable. 1: Support.8 Transmission(E1T1) Fill in this sheet.U_ST_ZXSDR(V4. Value range: 0-7. Each NE occupies one line or more lines. SHORT. Fill in this item only when cascaded connection is adopted.2.10-20. with one line for each E1 link.09. PPP_LINK_TYPE PPP_COMPRESSION MP_HEAD MP_PRIORITY 3. The format is the same as that of HDLC timeslot. Format: Start timeslot – end timeslot. 200 series NodeB are adopted. The default configuration above should be the same as RNC quick configuration data. NCP and CCP parameters of an IPOA will be created automatically. E1. and rt-VBR and UBR for AAL2.T1. It has 20 bytes in total. an OMCB dual protocol stack channel. E1/T1 link is numbered from 0.” Please refer to the attached file in 5. e.3. All of E1/T1 links are put in IMA Group 0. IMA version: 1. Value range: 0-15.00. ZTE Confidential Proprietary © 2012 ZTE CORPORATION.1. and IP.10 RU Each RRU and each RSU occupy one line respectively. Cell Payload Scrambling. This item determines the average bandwidth and the minimum bandwidth in AAL2. and should be configured the same as the address on OMMR. The physical bandwidth usage is 100%. Table 3-10 Transmission(ATM) Sheet Item NE_ID ATM_TRANSMISSION_MEDIUM E1T1_NUMBER Specifications Corresponding to the NE ID in “Base Station” sheet. 3.9 Transmission(ATM) Fill in this sheet if it is ATM transmission or ATM+IP transmission.U_ST_ZXSDR(V4.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications The format is the same as that of HDLC timeslot. Fill in this item according to the actual situation. with one line for each NE. Use CBR for AAL5 signaling. It is an integration parameter.2. ITC Clock mode: ITC. Just fill in the valid length. When ATM+IP transmission is adopted and IP parameters have been configured. IMAB/APBE or APBI/SDTA/ET3A. 0.1. both complying with “ZXWR RNC IubPVC_configurationTool_English.g. ATM_ADDRESS RNC_IUB_BOARD 3.2 Special Subject for IUB Bandwidth Configuration for details.2. Length of frame:128cell. 21 . Default configuration: IMA. All rights reserved. each NE in this sheet may involve several lines of data. ATM transmission is supported only when WCDMA mode and 4.09.xls. and the rest bytes will be filled with 0 automatically. Therefore. 2MHz.21) Quick Data Configuration Guide Internal Use Only ▲ RRU is numbered from 2. BS8900A can be configured with nine RSUs at most. It must be an integral multiple of 0. BS8800 GU360 E can be configured with 12 RSUs at most. Do not use characters < > & ' and ".U_ST_ZXSDR(V4. which should be in the ascending order of RU No. 4G+1U. R8880A series are installed in the R8880 rack. and GSM+UMTS. All rights reserved.: 2-19. Optional. UMTS. BS8700 can be configured with 12 RSUs at most. Only when there is one FS board can auto allocation of FS optical ports be performed. 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. BS8906 can be configured with two RSUs at most. BS8800 GU360 and BS8800 U240 can be configured with six RSUs at most. BS8900 can be configured with 12 RSUs at most. GSM. 80 bytes at most. 2G+2U. “0” or Null means auto calculation by the base station RRU_NAME RADIO_MODE GW_CONFIG_MODE BOARD_TYPE DOWNLINK_FREQ ZTE Confidential Proprietary © 2012 ZTE CORPORATION.: 51-74. and 24 RRUs can be configured at most. Value range of RSU No. BS8800 U120 and BS8800 U120A can be configured with three RSUs at most.09. 22 . BS8900 GU360 E can be configured with 18 RSUs at most. TTR series are installed in the R8802 rack. Adopt INVALID for single mode. Value range of RRU No. INVALID. RSU series are installed in the main rack. DTR series are installed in the R8860 rack. Table 3-11 RU Sheet Item NE_ID RU_NO Specifications Corresponding to the NE ID in “Base Station” sheet. 0db. 6db. Value range: 0-6. “0” or Null means auto calculation by the base station equipment. if the FS optical port is allocated automatically or is cascaded to a higher level RU.” do not configure UPLINK_FREQ as “0. 23 . For GSM only Value range: 0-6. Value range: 0-32.09. The number of carriers in all sectors should be less than or equal to the total number of carriers. All rights reserved. If DOWNLINK_FREQ is not “0. The number of carriers in all sectors should be less than or equal to the total number of carriers. 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 ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Do not fill in this item.21) Quick Data Configuration Guide Internal Use Only ▲ Item equipment. 20-25: refer to the 6 optical ports on the second FS board.U_ST_ZXSDR(V4. Value range: 1-80. UPLINK_FREQ Specifications It must be an integral multiple of 0.” 0-5: refer to the 6 optical ports on the first FS board. N: Not connect with antenna. 4db. For GSM only. and 20db. RX Extension RU cannot be configured. The associated RUs should have the same frequency band. 14db. For GSM only. 2db. Y: Connect with antenna. 16db. For GSM only/ Value range: 0-6. Value range: 0-6. 10db. 18db. The number of carriers in all sectors should be less than or equal to the total number of carriers. Each RU can be associated once only. If it is set as Y.2MHz. For GSM only. The number of carriers in all sectors should be less than or equal to the total number of carriers. 0: Not group For GSM only. This Sector ID must exist in GSM Sector sheet. and 1-2 are for TTR series For GSM only. 12db. For GSM only/ Value range: 0-6. 255: Invalid. For GSM only. 1-6 are for DTR board series. For GSM only. 8db. ANT/RET.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications equal to the total number of carriers.09.g. For GSM only. Value range: 0-6.U_ST_ZXSDR(V4.25dB).1dB). The number of carriers in all sectors should be less than or equal to the total number of carriers. e. 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. and 900M ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Value range: 0-6. A-TMA. For GSM only. All rights reserved. The number of carriers in all sectors should be less than or equal to the total number of carriers. Value range: 0-6. A-TMA: 44-100(0. For GSM only Value range: 0-6. Value range: 0-6. For GSM only. Invalid: 255. ETMA. Value range: 70-170. and A-ETMA. 0: Not enable sub-frequency band. For GSM only. The number of carriers in all sectors should be less than or equal to the total number of carriers. TMA: 110-130 (0. RET: Electric tilt antenna TMA. 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. Value range: 0-80. ETMA: 230-250 (0. The number of carriers in all sectors should be less than or equal to the total number of carriers. This parameter and the following four ones are valid only for antenna type RET. 2. The type of boards can be found out automatically according to the frequency band of Downlink Frequency. 24 . For GSM only. The number of carriers in all sectors should be less than or equal to the total number of carriers.1dB). it is not necessary to divide the category to subcategories B/C/D/E. Value range: 0-6. ANT: Common antenna.25dB). Invalid: 255. A-ETMA: 92-100 (0. Value range: 10-30.1G is corresponding to DTR. It is not necessary to configure other frequency bands. Value range: 0-65535. All rights reserved. N: Disable. Default: 0. but it is not necessary to configure subfrequency band to TTR/GRSU/RTR/RSU series. Value range: 0-50.2. 65535: Invalid.09. The Downlink Frequency of RRUs in the same Carrier Group should be in the same frequency band.11 UMTS Radio Fill this sheet when UMTS mode is adopted. 65535: Invalid. PASHARE_PER ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Y: Enable. This sheet is corresponding to the wireless resource management of SDR NE on OMMB. 25 . Value range: 1-1920. Optional. 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. 1800MHz frequency band includes two sub-frequency bands (1-2). Do not use characters < > & ' and ". Please refer to Table 3-12 for detailed frequency range. Value range: 1-1920. 127 bytes at most.21) Quick Data Configuration Guide Internal Use Only ▲ is corresponding to DTR-C. NodeB ID is the same as NE ID when UMTS mode is adopted.U_ST_ZXSDR(V4. 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. 900MHz frequency band includes three sub-frequency bands (1-3). DTR/DRSU supports sub-frequency band. Do not use characters < > & ‘ and “.12 UMTS Baseband Resource Pool Fill this sheet when UMTS mode is adopted. If there are two or more carriers.09. is “8”. All rights reserved. Table 3-15 UMTS Baseband Resource Pool Sheet Item NE_ID LCG_ID Specifications Corresponding to the NE ID in “Base Station” sheet. Format: BPCSlot&BPCSlot&…. Thus.2. they should be in different baseband resource pools. Value range: 0-35. “7&8” means there are two baseband boards LCG_INFO BPC_GROUP ZTE Confidential Proprietary © 2012 ZTE CORPORATION. unique in the same NodeB. Optional.U_ST_ZXSDR(V4.21) Quick Data Configuration Guide Internal Use Only ▲ 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. each NE in this sheet may have two or more lines of data. 26 . Each baseband resource pool occupies one line. and the slot No.g. “8” means there is one baseband board in this group. 199 bytes at most. e. all RUs should be in the same frequency band and connected to the same FS board. All rights reserved.13 UMTS Sector Fill this sheet when UMTS mode is adopted. Value range: 0-255.e. Thus.2. RELATED_RU RX_TYPE RFRX_ORDER ZTE Confidential Proprietary © 2012 ZTE CORPORATION. are “7” and “8” respectively.e. If OTSR/M-RRU is adopted. RU No. MIMO. The MINO RU should be R8880. and two RUs should be used. and 1 means using the secondary antenna. i. RTRs of different power consumptions can be configured in the same RU. and the slot Nos. Optional. The MIMO-II RU should be R8880. RUs of different frequency bands should not be configured together in the same base station. port 0 of the RF board is configured first. boards of different power consumptions should not be configured in the same RU. When two or more RRUs/RSUs are configured in a sector. DTRs and dual mode RSU boards should have the same frequency band. Do not use characters < > & ' and ". N: Non-diversity. For receiving non-diversity. 199 bytes at most. 27 . Y: Diversity. 0 means using the primary antenna. unique in the same site. For receiving diversity. each NE in this sheet may have two or more lines of data. Each baseband resource pool occupies one line. 1 means the reverse sequence. This parameter is used to set RF cable connections for POI sites. and only one RU can be used.U_ST_ZXSDR(V4. If RX Type MIMO-II is adopted. port 1 of the RF board is configured first. i. 3. the format should be RU1&RU2&….09. MIMO-II.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications in this group. 0 means normal sequence. 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. Default: 23 Value range: 0-65535. If the local cell is a dual carrier master cell.8M. Value range: 0-268435455. it should be in the same sector as the slave cell. N: Disable CARRIER_INDICATION FREQ_SPACING CELL_RADIUS LOCAL_CELL_POWER LOCAL_CELL_TYPE DC_LOCAL_CELL TRANSMIT_DELAY RECEIVE_DELAY BATTERY_SAVING ZTE Confidential Proprietary © 2012 ZTE CORPORATION.2-5MHz). 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. 4. The Rx Type of the sector should not be MIMO or MIMO-II. 4. Only carriers with Carrier ID 0 can be configured to dual mode 4G+1U. 5M. Do not use characters < > & ' and ". Each local cell occupies one line. 0: Common cell. 199 bytes at most. Only carriers with Carrier ID 0 and 1 can be configured to dual mode 2G+2U. please refer to the following text. As to the specifications of configuring high-speed railway cells.5km/5km/10km/20km/40km/80km/120km. unique in the same subnetwork. R8880A: 0-5.2M are applicable only to single mode UMTS R8860. and the master cell and the slave cell should be neighbor cells (Frequency Spacing: 4. Default: 13. 1: High-speed railway cell.4M and 4.21) Quick Data Configuration Guide Internal Use Only ▲ 3. 255: Invalid. 2. Y: Enable. Value range: 0-200. DTR/RTR series: 0-2.2MHz. Refer to Table 3-18 for the value range.14 UMTS Local Cell Fill this sheet when UMTS mode is adopted. 4. both the Carrier Indication and the Tx power should be in an ascending order. Cited from “UMTS Baseband Resource Pool” sheet. All rights reserved. Value range: 0-65535. 4.6M.09.2M. The value should be an integral multiple of 0.4M.2. 4. 28 . Thus.U_ST_ZXSDR(V4. each NE in this sheet may have two or more lines of data. Cited from “UMTS Sector” sheet. Optional. 10. LOCAL_CELL_VAM The Downlink Frequency should be an integral multiple of 0. 5” or “8. The Carrier Indication should be unique within the same sector.2MHz and within 4. Baseband resource pool. composed of one or more BPC baseband boards.6-5.09. 4.4MHz and <= 10MHz. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. The bandwidth of each carrier should be an integral multiple of 0. All rights reserved.0MHz. Baseband resource pool was called local cell group (LCG). the radius of each local cell should be within 2. The baseband resource pool with only non-MRRU cells can be configured with six cells at most.4. N: Not support.5 km.U_ST_ZXSDR(V4. is configured in “UMTS Baseband Resource Pool” sheet. the spacing of Downlink Frequency for two carriers should be within “4. 5. i.1MHz The frequency spacing of every two carriers should be <=5MHz and >=4. Disable: Not support. 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. If there are more than three STSR cells and only one BP board in the baseband resource pool with only STSR cells.21) Quick Data Configuration Guide Internal Use Only ▲ Item LOCAL_CELL_2MS_GAIN Specifications Enable: Support.e.2MHz. The overlapped bandwidth of every two carriers should not exceed 0. The baseband resource pool with only M-RRU(M>2) cells can be configured with two cells at most. only one M- 2. Carrier Indication and Frequency Spacing should meet the following requirements: 1. 3. 2.2 MHz. Y: Support. 29 . When both M-RRU(M>2) cells and 2-RRU cells are configured. 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). Configure this parameter as Y only when the RX Type is MIMO/MIMO-II. The capacity of a baseband resource pool is as listed below: 1. The cell with only one RRU/RSU in its sector is an STSR cell. or >=8.2.” 3. The resource pool with only 2-RRU cells can be configured with three local cells at most. 10.5km or 5km. 2. If four local cells are configured in the baseband resource pool configured with both 2-RRU local cells and STSR local cells. 3. A Baseband resource pool with only one baseband board can be configured with only one cell with ultra-wide coverage at most. three cells can be configured at most. All rights reserved. in which three cells with ultra-wide coverage can be configured at most. M-RRU(M>2) high-speed railway cells and OTSR high-speed railway cells cannot share the same baseband resource pool. 4. 5. If there is only one baseband board in a baseband resource pool with only STSR high-speed railway cells. 1. 7.5km. 3. 4. If there is only one M-RRU(M>2) cell and one BP board in the baseband resource pool.5km. A cell of ultra-wide coverage should be configured with a separate resource pool. The radius of high-speed railway cells can only be 2.5km. the radius of each local cell should be within 2. A Baseband resource pool with three or more baseband boards can be configured with three cells 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 cell of ultra-wide coverage supports only receiving diversity and does not support receiving non-diversity. the radius of each local cell should be within 2. 6.09. High-speed railway cells and common cells cannot share the same baseband resource pool. the radius of each local cell should be within 2. If there is only one BP board in the resource pool with both M-RRU(M>2) cells and 2RRU cells. 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. Cells with a radius of 80km or 120km are of ultra-wide coverage cells. only one 2-RRU cell and three STSR cells can be configured at the same time. to which the capacity is as listed below. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. If there is only one BP board in the resource pool with both M-RRU(M>2) cells and STSR cells. 8. The capacity for high-speed railway cells is as listed below. 1.21) Quick Data Configuration Guide Internal Use Only ▲ RRU(M>2) cell and one 2-RRU cell can be configured in a resource pool at the same time. 30 .U_ST_ZXSDR(V4. 2. 9.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. two 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. two cells can be configured at most. three cells can be configured at most. 3. Thus.09. 31 . 7. 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. The product of “GSM Carrier Power X Number of carriers + Power of local WCDMA cells” shall not exceed the total power on the board. If there are two or more baseband boards in a baseband resource pool with only STSR high-speed railway cells. each NE ZTE Confidential Proprietary © 2012 ZTE CORPORATION.” 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. If there is only one baseband board in a baseband resource pool with both STSR and 2-RRU high-speed railway cells. 8. 6.2.U_ST_ZXSDR(V4. If there are two baseband boards in a baseband resource pool with only 2-RRU highspeed railway cells. If there are two or more baseband boards in a baseband resource pool with only MRRU high-speed railway cells. 10. All rights reserved. one STSR cell and one 2-RRU cells can be configured at most at the same time.21) Quick Data Configuration Guide Internal Use Only ▲ 5. Each sector occupies one line. 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. It is necessary to check the sum of the power consumptions on dual mode DTR/DRSU. six cells can be configured at most.15 GSM Sector Fill this sheet when GSM mode is adopted. the number of carriers should be set to “2” or a larger value. each NE in this sheet may have two or more lines of data. It is not necessary to fill this item if it is not configured. the Carrier Group must be configured. if it is set as dual channels. the same mode should be adopted to generate data of logic TRXs. If the RRUs associated with the base station are in the same Carrier Group. It is not necessary to fill this item if it is not configured. they should be in the same frequency band.2.U_ST_ZXSDR(V4. there can only be two carriers. of a sector starts from 1.09. 3. and the sub-frequency bands are “0. Fill in “auto. In dual or multiple channel modes. TRX_NO ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Table 3-20 GSM Carrier Sheet Item NE_ID SECTOR_ID Specifications Corresponding to the NE ID in “Base Station” sheet. 32 . If “auto” mode is adopted for generating data of logic TRXs.21) Quick Data Configuration Guide Internal Use Only ▲ in this sheet may have two or more lines of data.” For all sectors of a site. and the Channel Mode should be “Multiple Channel Mode. and the number of RRUs should be the same as that of carriers in the same group. Not group). Table 3-19 GSM Sector Sheet List NE_ID SECTOR_ID GPS_OFFSET POINT1_RU_NO POINT2_RU_NO Value range: 1-24. and no CoBCCH is configured.” if the generated logic TRX No. If an OTSR cell is to be configured. Specifications Corresponding to the NE ID in “Base Station” sheet. Value range: 1-54.” If the Channel Mode is set as single channel. Value range: 1-24. All rights reserved. POINT1 RU NO and POINT2 RU NO should be configured together. and grouping must be performed. the Carrier Group of the corresponding RRU should be “0” (i. please check whether the generated data is consistent with the data of cell TRX data on OMCR. Each sector occupies one line or more lines.16 GSM Carrier Fill this table when GSM mode is adopted. Thus.e. Value range: 0-50. and there can only be one carrier. U_ST_ZXSDR(V4. The Shelf No. 1: Use. in which the Shelf Nos. The Shelf No. SHELF_NO SLOT_NO ZTE Confidential Proprietary © 2012 ZTE CORPORATION. is generated automatically. Main rack No.850M. 0: Not group. 1: Yes. Table 3-21 Dry Contact Sheet Item NE_ID RACK_NO Specifications Corresponding to the NE ID in “Base Station” sheet. 0: No. 33 . Remote racks are numbered from 2. The Slot No. of FCE board is 2.900M Do not fill in this item. Thus. Do not fill in this item. DUAL: Dual channel. of the SE board is 5. each NE in this sheet may have two or more lines of data.09. MULTI: Multi-channel Value range: 1-12. of B8200(B8700) and RRU can only be 1. Value range: 0-32. 0: Not use. of RSU are 8/12/15.1800M.1900M.2. is generated automatically. All rights reserved.17 Dry Contact Each dry contact occupies one line. The Shelf No. The Slot No. is generated automatically.: 1. 2. of B8800 can be 1/2/5. The Shelf Nos. This value should be smaller than the sum of carriers on all RRUs in this cell. of FCE/FCEA are 6/10/13. of the SA board on B8200(B8700) is13. 0 or 255: Not enable sub-frequency Do not fill in this item. The Slot No. Value range:0-3. if the logic TRX No. if the logic TRX No. of B8900 can be 1/6/8/10/12/13/15. if the logic TRX No. of RSU is 5. CARRIER_NUMBER_OF_LOGIC_FREQ CARRIER_GROUP FREQ_BAND SUB_FREQ_BAND USE_IRC EXTENSION_CARRIER 3.1G.21) Quick Data Configuration Guide Internal Use Only ▲ Item CHANNEL_MODE Specifications SINGLE: channel. The Shelf Nos. The Slot No. of the FCEA board is 1(1. but No. 34 . 0-7. Refer to Table 3-22. 1: Output high level. of the FCE board for B8800 is 1. 0: Output low level. The Slot No. Choose Alarm Management > Setting > AlarmCode Description Setting. 1 cannot be configured. is “0.21) Quick Data Configuration Guide Internal Use Only ▲ Item Specifications The Slot No.10. No. for 200 series.30. for FCE series are 0-4. The dry contact Nos. The dry contact Nos. Value range: 1556-1605. 6 and No. Valid only when the Dry Contact No.09. of the RRU board is 1. which is corresponding to “Main power supply has fault alarm. then this alarm code can be used in Configuration Management. and modify the description of the code to be used.U_ST_ZXSDR(V4. SA/SE supports 8 dry contact inputs. 0 can only be configured for “198092049 Cabinet’s lightning arrestor alarm” (or not configured).6. The Slot No.09. Nos.” Supported by version 4. Dry Contact Nos. All rights reserved. 7 of SA board or SE board.1)/2(1. Input: Input dry contact. One rack can only be configured with one dry contact.2). of RF boards are 0-3.13. i. 24 cannot not be configured. of the FCE board for B8900 is 3(1. Valid for output dry contact.e. 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 Cabinet’s lightning arrestor alarm PSU alarm PSU fan alarm Base station master power supply break alarm Battery Fault AC power-cut alarm Description ZTE Confidential Proprietary © 2012 ZTE CORPORATION. Output: Output dry contact.” OPEN/CLOSE. Output dry contact can only be configured on Dry Contact No.3). Note: It is necessary to set user-defined alarm code on OMCB.00. 0. the Slot Number.21) Quick Data Configuration Guide Internal Use Only ▲ Value 198092208 198092209 Description Rectifier model alarm Thermoelectric cooling alarm 4 Examples of Template Filling ZXSDRConfTool templates provide some examples for the four types of bearers. instead of the number of slots. The fourth RRU is cascaded to the third one. must be configured. the connection between RUs should be described in the RACK_TOPOLOGY filed (1-51. PPP_PROTOCOL. only the fourth line can be filled in. use one line for each base station. the E1 Number. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. In the “Transmission(IP)” sheet. Please note: In the “Equipment” sheet. PPP_IP_ADDRESS. 1-52.” “Transmission(IP). for “Time” and “Clock” sheet. Keep the default value for PVC and other parameters. 35 .” indicating an OTSR cell.2 Example 2: SDR_8700_OTSR_ATM+IP Ground resource part: Because the IP configuration is added. The following basic items must be filled in: in “SubNetwork” sheet. All rights reserved. besides the basic items. MP_HEAD. as shown in the attached file below. must be filled in.1 Example 1: SDR_8700_STSR_ATM Ground resource part: Besides the basic items. SD O R_C NFTO L_UM O TS_D O EM _V2. and MP_PRIORITY. In the “UMTS Sector” sheet. items in “Transmission” sheet and “Transmission(ATM)” sheet should be filled in. for both the “Base Station” sheet and the “Equipment” sheet.” and “Transmission(ATM)” must be filled in. instead of the number of E1 cables. In the “Equipment” sheet. in which Cell 10013 is configured as receiving non-diversity. base stations with the same property might be reduced to one line. forming an OTSR cell. there are three STSR cells with star networking. and 1-5354 in this example). Wireless resource part: There are four RRUs in this example. 4. the Related RU should be “53&54. zi p 4. but base stations with the same site configuration might be reduced to one line.09. Wireless resource part: In this example. Please note: In the “Transmission(ATM)” sheet.U_ST_ZXSDR(V4. the three sheets of “Transmission. it is unnecessary fill in the following fields: PPP_E1T1_LINKID. PPP_COMPRESSION. 8. “Transmission(IP)” sheet.3 Example 3: SDR_8800_STSR_IP Ground resource part: Besides the basic items. three RSUs are configured in three STSR cells. 4. and “Transmission(E1T1)” sheet must be filled in. “3” refers to the RSU at the second slot. When filling in the “RSU” sheet. there are one RRU and three RSUs. PPP_PROTOCOL. PPP_IP_ADDRESS. In the “Transmission(IP)” sheet. “Transmission” sheet. and so on. The RRU and the last RSU form an OTSR cell. But in “Transmission(IP)” sheet. 36 . All rights reserved. please note the changes in the meaning of RSU_NO field: “2” refers to the RSU at the first slot.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. and the RSUs are connected to optical ports 1-3. and MP_PRIORITY. it is unnecessary to fill in the following fields: PPP_E1T1_LINKID.” The FS Port in the “RRU” sheet and the “RSU” sheet must be filled in.4 Example 4: SDR_8800_OTSR_IPOE Ground resource part: Besides the basic items. The RRU is connected to the optical port 0 of FS board. The parameter FS Port Assignment in the “Equipment” sheet should be set as “Manual. “Transmission” sheet and “Transmission(IP)” sheet must be filled in.” Wireless resource part: In this example. PPP_COMPRESSION. it is unnecessary to fill in the fields starting with “IP_VLAN. ZTE Confidential Proprietary © 2012 ZTE CORPORATION.09. 5 5. Wireless resource part: In this example. MP_HEAD.U_ST_ZXSDR(V4.21) Quick Data Configuration Guide Internal Use Only ▲ 4. two digits usually adopted ) Radio mode (n characters ) TRX board (n characters ) Remarks: Power 4: 40W. 900M. 90. TTR.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 5-14 Rules for Naming RRUs Rules for Naming RRUs Xn . 18. AWS frequency band Radio mode: U: UMTS. AWS: 2100M. 19. GU: GSM/UMTS TRX board: RTR. 37 . DTR. 6: 60W.Xn Xn X Power Frequency band (n characters .U_ST_ZXSDR(V4.09. 1800M. 8: 80W Frequency band : 21. G: GSM. All rights reserved. 850M. TRMD ZTE Confidential Proprietary © 2012 ZTE CORPORATION. 85. 1900M. G: GSM. the quick data configuration should be based on the rules in “ZXWR RNC IubPVC_configurationTool_English.xls.Xn Xn X Power Frequency band (n characters .U_ST_ZXSDR(V4. AWS frequency band Radio mode: U: UMTS. 85. two digits usually adopted ) Radio mode (n characters) Structure type (n characters ) Remarks: Power 4: 40W. AWS: 2100M. GU: GSM/UMTS Structure type 40: R8840. 80: R8880. 850M. ZTE Confidential Proprietary © 2012 ZTE CORPORATION. 60: R8860.09. 19.2 Special Subject for IUB Bandwidth Configuration On the IUB interface for E1/T1 transmission. All rights reserved.new xl s . 1800M. 900M. 90. 8: 80W Frequency band: 21. 02: RU02 5.’ ZXW RN R C I ubPVC_conf i gurat i onTool _Engl i sh. 1900M. 18. 6: 60W.21) Quick Data Configuration Guide Internal Use Only ▲ Figure 5-15 Rules for Naming RSUs Rules for Naming RSUs RSU Xn . 38 .