G_ZXSDR (V4.

14) Quick Data

Configuration Guide
 G_ZXSDR (V4.14) Quick Data Configuration Guide

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 © 2015 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.

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,
estoppel 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
Website: http://support.zte.com.cn
Email: 800@zte.com.cn

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. I
G_ZXSDR (V4.14) Quick Data Configuration Guide

Revision History

Product Version Document Version Serial Number Reason for Revision

ZXSDR V4.14 R1.0 First published

Intended audience: Base station commissioning engineers

II ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

About This Document

Summary
Chapter Description
1 Overview Describes the application scope of this guide.
2 Basic Operations of OMMB Data Describes the features of OMMBV12.14 and the basic
Configuration functions of configuration management.
3 OMMB Plan Template Filling Describes the OMMB data to be configured in SDR
Specifications commissioning.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. III
G_ZXSDR (V4.14) Quick Data Configuration Guide

TABLE OF CONTENTS

1  Overview ........................................................................................................... 1 
1.1  Instructions ......................................................................................................... 1 
1.2  Version Requirement ......................................................................................... 1 

2  Basic Operations of OMMB Data Configuration............................................ 2 

2.1  Introduction to OMMB Data Configuration ......................................................... 2 
2.2  Planning Data Import Flow ................................................................................. 3 
2.2.1  Filling in the Planning Data ................................................................................ 3 
2.2.2  Importing Planning Data ..................................................................................... 4 
2.2.3  Data Synchronization ......................................................................................... 7 
2.3  Planning Data Export Flow ................................................................................. 9 
2.4  Planning Data Modification Flow ...................................................................... 12 
2.5  Online Data Modification Flow ......................................................................... 13 
2.5.1  Online Data Modification of Single Site ............................................................ 13 
2.5.2  Online Batch Modification ................................................................................ 14 
2.6  XML Data Import/Export Flow .......................................................................... 16 
2.6.1  XML Data Import Flow ..................................................................................... 16 
2.6.2  OMMB XML Data Export Flow ......................................................................... 18 
2.6.3  SDR XML Data Export Flow ............................................................................. 20 
2.7  BCT Configuration Flow ................................................................................... 21 

3  OMMB Plan Template Filling Specifications................................................ 25 

3.1  Ground Plan Template Filling Specifications.................................................... 25 
3.1.1  Ground Template Customizing ........................................................................ 28 
3.1.2  Basic Parameters ............................................................................................. 29 
3.1.3  Equipment Parameters .................................................................................... 39 
3.1.4  Transmission Parameters ................................................................................ 66 
3.2  GSM Wireless Plan Template Filling Specifications......................................... 80 
3.2.1  GSM Wireless Template Customizing.............................................................. 80 
3.2.2  BtsFunction ...................................................................................................... 81 
3.2.3  RU(GSM) ......................................................................................................... 82 
3.2.4  GSM Carrier ..................................................................................................... 84 

IV ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

FIGURES

Figure 2-1 Select Planning Data Import ................................................................................. 4 

Figure 2-2 Planning Data Import ............................................................................................ 5 
Figure 2-3 Error Information in the Result File ....................................................................... 6 
Figure 2-4 Details of Parameter Error in the Result File ........................................................ 6 
Figure 2-5 Result in the Result File ........................................................................................ 7 
Figure 2-6 Select Data Synchronization ................................................................................ 8 
Figure 2-7 Execute Data Synchronization ............................................................................. 8 
Figure 2-8 Select Configuration Data Upload from NE .......................................................... 9 
Figure 2-9 Perform Configuration Data Upload from NE ..................................................... 10 
Figure 2-10 Successful Configuration Data Upload from NE ............................................... 10 
Figure 2-11 Select Planning Data Export ............................................................................. 11 
Figure 2-12 Planning Data Export ........................................................................................ 12 
Figure 2-13 Online Data Modification Flow .......................................................................... 14 
Figure 2-14 Data Batch Configuration Management – 1...................................................... 14 
Figure 2-15 Data Batch Configuration Management – 2...................................................... 15 
Figure 2-16 Data Batch Configuration Management – 3...................................................... 15 
Figure 2-17 Data Batch Configuration Management – 4...................................................... 15 
Figure 2-18 Data Batch Configuration Management – 5...................................................... 16 
Figure 2-19 Select Data Import ............................................................................................ 16 
Figure 2-20 Perform Data Import ......................................................................................... 17 
Figure 2-21 Verification Code for Executing Data Import..................................................... 18 
Figure 2-22 Data Import Executed Successfully .................................................................. 18 
Figure 2-23 Select Data Export ............................................................................................ 19 
Figure 2-24 Perform Data Export ......................................................................................... 20 
Figure 2-25 Generate file ..................................................................................................... 21 
Figure 3-1 Template Customizing ........................................................................................ 28 
Figure 3-2 GSM Wireless Template Customizing ................................................................ 81

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. V
 G_ZXSDR (V4.14) Quick Data Configuration Guide

TABLES

Table 1-1 Version Information ................................................................................................ 1 

Table 3-1 Instructions on Filling in Sheets in Ground Plan Template .................................. 25 
Table 3-2 ManagedElement Sheet ...................................................................................... 29 
Table 3-3 Cabinet Sheet ...................................................................................................... 39 
Table 3-4 IpClock Sheet ...................................................................................................... 41 
Table 3-5 Clock Sheet ......................................................................................................... 43 
Table 3-6 RU Sheet ............................................................................................................. 46 
Table 3-7 FiberDevice Sheet ............................................................................................... 49 
Table 3-8 PA Sheet .............................................................................................................. 51 
Table 3-9 FCE Sheet ........................................................................................................... 53 
Table 3-10 FCE Sheet ......................................................................................................... 54 
Table 3-11 AISG Sheet ........................................................................................................ 56 
Table 3-12 PowerOutlet Sheet ............................................................................................. 58 
Table 3-13 Epme Sheet ....................................................................................................... 61 
Table 3-14 AntEntity Sheet .................................................................................................. 63 
Table 3-15 FiberCable Sheet ............................................................................................... 63 
Table 3-16 RfCable Sheet ................................................................................................... 64 
Table 3-17 PhyLayerPort Sheet ........................................................................................... 67 
Table 3-18 HDLC Sheet ....................................................................................................... 69 
Table 3-19 PPP Sheet ......................................................................................................... 71 
Table 3-20 IpLayerConfig Sheet .......................................................................................... 73 
Table 3-21 BandwidthResource Sheet ................................................................................ 75 
Table 3-22 Sctp Sheet ......................................................................................................... 76 
Table 3-23 OmcChnnel Sheet ............................................................................................. 77 
Table 3-24 ServiceMap Sheet ............................................................................................. 79 
Table 3-25 Description of Sheets in GSM Wireless Plan Template ..................................... 80 
Table 3-26 BtsFunction Sheet ............................................................................................. 81 
Table 3-27 RU(GSM) Sheet ................................................................................................. 82 
Table 3-28 GSM Carrier Sheet ............................................................................................ 84 

VI ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

1 Overview
This chapter focuses on the following subjects:

 Instructions

 Version Requirement

1.1 Instructions

This guide is the SDRV4.14 commissioning guide based on BSCV4 (ZXUR9000)+

SDRV4.14. It describes mainly the quick configuration method based on the Plan
template. It applies to GSM single-mode base stations.

1.2 Version Requirement

Table 1-1 Version Information

NE Example Version Applicable Versions

SDR V4.13.10.10 V4.14 series

OMMB OMMBV12.14.50 V12.14 Series

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 1
G_ZXSDR (V4.14) Quick Data Configuration Guide

2 Basic Operations of OMMB Data

Configuration
This chapter introduces the data configuration of SDR base station on OMMBV12.14.

This chapter focuses on the following subjects:

 The features of OMMB configuration management and data configuration flow

 The data import/export/modification flow

 XML data import/export flow

2.1 Introduction to OMMB Data Configuration

OMMBV12.14 (hereafter referred to as OMMB) is a multi-mode network manager based

on the MO structure, supporting the SDR base station of all radio products, such as GSM,
UMTS, CDMA, TD-SCDMA, TDD-LTE, and FDD-LTE, etc.

The NE data of OMMBV12.14 has two formats, Excel and Xml.

 Excel data is is mainly for data configuration and data modification.

 The XML data is mainly for configuration upgrade, import & export of LMT, and BCT.

OMMB data can be configured through the following methods:

1. Configuration through GUI

GUI supports both single-site configuration/modification and site

batch-configuration/modification.

The configuration through GUI is very simple, so it is not described further here.

2. Configuration through templates

The data can be configured through either MO template or Plan template. The MO
template can be used only on EMS, while the Plan template can be used on both

2 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

EMS and OMMB. Because the filling of MO template is very complicated, Plan
template is recommended.

The Plan template is stored under the Template directory of the OMMB tools
package released with OMMBV12.14. This directory contains the PUBLIC
templates of different versions and the RADIO templates of different modes. The
PUBLIC template of the corresponding version and one or more RADIO templates
need to be filled in the site commissioning process.

GU site commissioning uses the Plan template in most cases, so this guide is
focused on the Plan template.

3. Configuration through BCT.

BCT is a batch-copy tool. If the configuration of most parameters except very few
parameters (e.g., IP) is the same in some sites, the batch-configuration of XML data
can be achieved in these sites through BCT.

 Knowledge:

Different from OMMBV12.13, which supports only the latest Plan template, OMMBV12.14
supports the Plan template import of V4.12, V12.13, and V12.14series. In other words,
OMMBV12.14 supports base station commissioning of V4.12/V4.13/V4.14 series through
the Plan template.

OMMB V12.14 provides different ground and radio Plan templates for V4.12 series, V12.13
series, and V12.14 series. These templates are stored in the corresponding folders named in
the actual version.

2.2 Planning Data Import Flow

2.2.1 Filling in the Planning Data

Refer to Chapter 3 for the method of filling in parameters.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 3
 G_ZXSDR (V4.14) Quick Data Configuration Guide

2.2.2 Importing Planning Data

1. Select Planning Data Import from the drop-down menu of Configuration

Management in the view of ZXSDR OMMB.

Figure 2-1 Select Planning Data Import

2. In the pop-up window, perform the following operations:

i. Click Add in the pop-up window, and select the planning template to be
imported. Import the PUBLIC template first and then the Radio template, or
import the PUBLIC template and the RADIO template together. (Click Remove
to remove the selected template from the Task List.)

ii. It is recommended that “Roll back NE failed to import” be set to “YES.” (If “Yes”
is selected, once the data of a base station fails to be imported in the Plan
template importing process, the data of the base station will be rolled back to
the pre-modification status, i.e., no data will be modified. If “No” is selected,
only the imported data of the base station will be modified and the data that
fails to be imported will not be modified in the template importing process.)

iii. When the data fails to be exported, the result file containing the failure
information will be generated under the directory defined in “Result file save
path.”

4 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

iv. “Back up data before performing the operation” is used to configure whether to
back up the current data before importing data. It is recommended that this
item be selected.

v. Click Import to import the template.

vi. After the data is imported successfully, click Close to exit.

Figure 2-2 Planning Data Import

3. Error Information in Data Import

If the data import fails, the Status will be “Failed” and the “Confirm” dialog box will
pop up automatically. Click Yes to open the directory of the exported file.

i. Open the result file.When there are two or more files under a directory,
sequence the files by time and select the latest one.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 5
G_ZXSDR (V4.14) Quick Data Configuration Guide

ii. In the sheet of Error Informaiton in the result file, we can see the sheets with
errors and click sheet name to link to the sheet.

Figure 2-3 Error Information in the Result File

iii. In the column of Result in the Error Information sheet, we can see the
detailed cause of error of each parameter.

Figure 2-4 Details of Parameter Error in the Result File

iv. If there is no error in a line, the status of the corresponding Result column is
“Success”, and the MODIND column is “P”.

6 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-5 Result in the Result File

Note:

If “Status” is “There is no data in the planning template to be imported,” it is possible that

the operator A, M, or D is not filled in the Plan template. At this time, there is no result file
generated.

If “Yes” is selected for “Roll back NE failed to import,” modify the data in the original Plan
template after the import failure and import the template again.

If “No” is selected for “Roll back NE failed to import,” modify the data in the result file after
the import failure and import the template again.

2.2.3 Data Synchronization

The data synchronization here is to synchronize the data from OMMB to SDR.

Data synchronization includes all-data synchronization and incremental synchronization.

 In the site with initial configuration, all-data synchronization must be used.

 In the sites where the data is modified online or through Plan template, incremental
synchronization can be used, so that base station reboot due to all-data
synchronization can be avoided. However, some parameters can only be modified
in the incremental synchronization mode. The corresponding prompts will be
displayed during the execution of incremental synchronization.

1. Select Data Synchronization from the drop-down menu of Configuration

Management in the view of ZXSDR OMMB.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 7
G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-6 Select Data Synchronization

2. In the window of Data Synchronization, perform the following steps.

i. Select the sites that require data synchronization.

ii. Select data synchronization mode, “Synchronize modified data” or

“Synchronize all data”.

iii. Select radio mode (e.g., for GU dual-mode sites, if only GSM wireless data or
only GSM related data in the PUBLIC tale is modified, select GSM here).

iv. Find out whether it is necessary to perform data validity check before data
synchronization. If it is required, select the box before “Check parameter
before synchronization”.

v. Click Synchronize to start data synchronization.

vi. Click Close to close the window.

Figure 2-7 Execute Data Synchronization

8 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

3. If only data validity is to be checked only and data synchronization is not needed,
click Check parameters in the Data Synchronization window, as shown in the
green box in the above figure.

2.3 Planning Data Export Flow

The operator must confirm whether data upload from NE is needed before exporting the
data.

 If only the data in OMMB is involved, do not perform data upload from NE before
data export, no matter whether it is consistent with the data in SDR or not.

 If the exported data is required to be consistent with the data in SDR (eg. data
backup before upgrade), data upload from NE must be performed before data
export.

2.3.1.1 Configuration Data Upload from NE

1. Select Configuration Management > Configuration Data Upload from NE in the

view of ZXSDR OMMB.

Figure 2-8 Select Configuration Data Upload from NE

2. In the Configuration Data Upload from NE window, perform the following

operations.

i. Select the sites on which the configuration data needs to be uploaded from NE.

ii. Click Execute to perform data synchronization.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 9
 G_ZXSDR (V4.14) Quick Data Configuration Guide

iii. Type the verification code in the Important Operation dialog box.

iv. Click “OK.”

v. Click Close to close the window.

Figure 2-9 Perform Configuration Data Upload from NE

3. After Configuration Data Upload from NE is completed successfully, the Status

will become “Successful” and the Progress will become 100%.

Figure 2-10 Successful Configuration Data Upload from NE

2.3.1.2 Data Export

1. Select Planning Data Export from the drop-down menu of Configuration

Management.

10 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-11 Select Planning Data Export

2. In the window of Planning Data Export, perform the following operations:

i. Select the site for planning data export.

ii. Select the Data Area for data export: Snapshot Area or Modify Area.

iii. Select the file type for the exported data. Select XML file, unless otherwise
required.

iv. Set the path for saving the exported file and the file name.

v. Click Execute to export the data.

vi. After the data is exported successfully, “Successful” under Status and “100%”
under Progress will be displayed, and a dialog box of Confirm will pop up.

vii. Click Yes to open the directory of the exported file.

viii. Click Close to close the window.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 11
G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-12 Planning Data Export

2.4 Planning Data Modification Flow

Data modification with the planning table is also referred to as offline data modification,
i.e. to export the data to local for modification. This method is applicable to the scenario
when a large amount of data needs to be modified.

The major data modification steps are as follows:

1. Confirm the planning template that the data to be modified belong to.

2. Export the planning data of the target site from OMMB.

3. Modify the data in the planning table. What needs to be noted is that the
Modification Indication in the line of the modified data must be set correctly.

4. Import the modified planning data into OMMB.

5. Perform data synchronization (default: incremental synchronization).

12 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

2.5 Online Data Modification Flow

2.5.1 Online Data Modification of Single Site

Online data modification of single site is to modify parameters through GUI.

The relations between the data on the GUI interface and the data in the planning
template are as follows:

 The data presented on the GUI interface are all the data configured for the site,
while the data in the planning template are only part of the site data.

 Some data cannot be directly modified on the GUI interface, but can be directly
modified through the planning template, for example, the modification of board type.

The flow of online modification to parameters is shown in the following figure.

1. Apply for mutex right.

2. Double-click Modify Area.

3. Double-click the node to be modified in the lower left pane.

4. Click the icon for modification.

5. Modify data.

6. Save the modification.

7. Perform data synchronization.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 13
 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-13 Online Data Modification Flow

2.5.2 Online Batch Modification

Online batch modification is to modify parameters through Data Batch Configuration

Management.

1. Enter Data Batch Configuration Management.

Figure 2-14 Data Batch Configuration Management – 1

2. Select a Site

14 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-15 Data Batch Configuration Management – 2

3. Select the parameter to be modified, right-click it, and select Modify.

Figure 2-16 Data Batch Configuration Management – 3

4. Input the target value in the pop-up dialog box.

Figure 2-17 Data Batch Configuration Management – 4

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 15
 G_ZXSDR (V4.14) Quick Data Configuration Guide

5. The data batch modification finishes successfully.

Figure 2-18 Data Batch Configuration Management – 5

6. Perform incremental synchronization.

2.6 XML Data Import/Export Flow

2.6.1 XML Data Import Flow

1. Select Data Import from the drop-down menu of Configuration Management in the
view of ZXSDR OMMB.

Figure 2-19 Select Data Import

16 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

2. In the window of Data Import, perform the following operations.

i. Click Browse.

ii. In the pop-up window, select the xml file to be imported.

iii. Click Open.

iv. Before importing the data, decide whether to back up the original data. If the
site data exists in the OMMB, it is strongly recommended that the data be
backed up (select Back up Data Before Executing Operation).

v. Click Execute to import the data.

Figure 2-20 Perform Data Import

3. Input the verification code in the dialog box of Important Operation, and click OK.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 17
 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-21 Verification Code for Executing Data Import

4. After the data is imported successfully, “Successful” under Status and “100%”
under Progress will be displayed.

Figure 2-22 Data Import Executed Successfully

5. Click Close to close the window.

2.6.2 OMMB XML Data Export Flow

In OMMBV12.13, the xml file format in OMMB is different from the xml file format in SDR.
The xml file of the OMMB format is mainly used for importing data into OMMB and
configuring BCT. The xml file of the SDR format is mainly used for site commissioning
and configuration through the USB, LMT or PMT.

The data exported through Data Export in OMMB cannot be imported into SDR through
LMT. However, the data exported from SDR through LMT can be imported into
OMMBV12.14.

1. Select Data Export from the drop-down menu of Configuration Management in

the view of ZXSDR OMMB.

18 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-23 Select Data Export

2. In the window of Data Export, perform the following operations.

i. Select the site for xml file export.

ii. Select the Data Area for data export: Snapshot Area or Modify Area.

iii. Select the file type for the exported data. Select XML file, unless otherwise
required.

iv. Set the path for saving the exported file and the file name.

v. Click Execute to export the data.

vi. After the data is exported successfully, “Successful” under Status and “100%”
under Progress will be displayed, and a dialog box of Confirm will pop up.

vii. Click Yes to open the directory of the exported file.

viii. Click Close to close the window.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 19
 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-24 Perform Data Export

2.6.3 SDR XML Data Export Flow

Due to the difference in data file format in OMMB and SDR, when the data is
synchronized from OMMB to SDR, it is first converted to the format accepted by SDR,
and then synchronized to SDR. In this way, the data recognizable by SDR can be
acquired from OMMB. The deletion method is as follows:

1. Select Data Synchronization from the drop-down menu of Configuration

Management in the view of ZXSDR OMMB.

2. In the window of Data Synchronization, perform the following steps.

i. Select the sites that require data synchronization.

ii. For Synchronization Mode, select “Generate Synchronize File”; click Browse to
appoint the path for saving the generated file.

iii. Click Generate File to export the data.

20 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 2-25 Generate file

3. The generated file is in the zip format. It will be the xml file after being unzipped.

2.7 BCT Configuration Flow

BCT is a tool that can copy the initial XML file and create many XML files in batch, in
which some parameters can be set differently for different base stations.

The method of configuring BCT is as shown below:

1. Get the BCT tool.

BCT is released with OMMB version. It is in the ZXSDR_OMMB_Tools_V12.14.xxxx

package.

2. Get the initial configuration file.

Finish the configuration of the first base station through the GUI of OMMB. Export
the XML file of the base station through the Data Export function, and use it as the
initial configuration data.

3. Copy the initial XML file to the Input directory of the BCT tool.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 21
G_ZXSDR (V4.14) Quick Data Configuration Guide

4. Open the QuickConfig_MutiMode.xlsm or QuickConfig_MutiMode.xls file under the

Input directory (when there are a lot of target base stations, select the xlsm format),
and input the file name of the initial configuration data. Set Import Enable to “Yes,”
and save the Excel file as GU.xls (the file name can be self-defined.

5. Run BCT.jar. The following interface pops up.

6. Click Browse in the “Excel Template” column, and select the file saved at the last
step, which is GU.xls in this example. Use the default value of the “Output
Directory” column. Click the Auto Filling button. After the operation succeeds, the
following prompt will appear.

“Auto Filling” is used to extract the parameters of the initial configuration from the
XML file and fill them in the Excel template. The result file is automatically named as
xx.autofill.xls. It is GU.autofill.xls in this example. In the following example, the
parameters such as Subnetwork ID and MEID of the record in “Auto Filling” are set
to the actual values automatically.

22 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

7. In the GU_autofill.xls file, copy the first row and paste it to following rows manually.
Keep the “Quote Template Name” column unchanged, and modify other columns
according to the site configuration. Finally, save the configuration.

8. In the BCT tool, click Browse in the “Excel Template” column, and select the file
saved in the previous step, which is GU_autofill.xls in this example. Keep the default
configuration for Output Directory (or select another directory). Click the Auto
Filling button. After the operation succeeds, the following prompt will appear.

9. Click the Process button in the BCT tool, and start the batch-generation of the XML
file. If the following prompt appears, click OK. If “Process Information” needs to be
saved, click the Save Info button. Then, click Exit to quit BCT.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 23
G_ZXSDR (V4.14) Quick Data Configuration Guide

10. The XML files are generated under the Output Directory (the default output directory
of BCT).

11. Import the above-mentioned XML files into OMMB.

24 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

3 OMMB Plan Template Filling

Specifications
This Guide is based on the Plan Template released with OMMBV12.14.50.The methods
for filling the Plan templates of different versions are almost the same.

It should be noted that, the Modification Indication attribute (i.e., add (A), delete (D),
modify (M), or pass over (P) a row of data) must be configured in the PLAN template of
OMMBV12.14. This is not required in OMCBV4.11.In some sheets (e.g., "PA" sheet), the
Modification Indication attribute can only be set as “M.” For initial site configuration, this
attribute must be left blank (i.e., it is not necessary to fill in “M”).

3.1 Ground Plan Template Filling Specifications

The Ground Plan template has 35 sheets. Some of the sheets do not need to be filled in
some scenarios. This Guide introduces the GU related sheets. The specifications of filling
in the sheets are detailed in the following sections.

Table 3-1 Instructions on Filling in Sheets in Ground Plan Template

No. Sheet Name Description

This sheet is used to define the template. Different
1 Choose scenarios can be selected to generate the
corresponding template.

“Managed Element” sheet: The NE here refers to SDR

Managed Network base station. It involves subnetwork and NE.NE
2
Element parameters: NE Name, ManagedElement ID, NE Type,
External IP, NE Version, Longitude, and Latitude.

This sheet provides the information of the operator and

3 Operator
PLMN.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 25
G_ZXSDR (V4.14) Quick Data Configuration Guide

This sheet is used to configure the data of the slave

cabinet. The primary cabinet and the auxiliary cabinet
are not configured in this sheet, because the primary
4 Cabinet cabinet has been created with the creation of NE.
Currently, the auxiliary cabinet is used to put FCE
board. When FCE is created, the auxiliary cabinet is
created together.

This sheet provides the configuration information of the

5 Equipment
board on the main rack of BBU.

This sheet is about the 1588 clock configuration. If

6 IpClock master/slave configuration is used, each site should be
configured with two or more records.

This sheet provides the configuration of clock

reference source and the configuration of related
7 Clock parameters when GNSS reference source is selected.
If 1588 clock reference source is selected, IpClock
must be configured before the configuration of Clock.

This sheet is about the configuration of RU device,

8 RU
including RRU and RSU related information.

Optical port device. When the board of RU, BPL, FS,

or BBU is created, the related information of the optical
port device is created together. The value of the
parameter is the default value. If the default value is
9 Fiber Device not consistent with the actual value, modify it through
this sheet. Therefore, only the “M” operation can be
performed in this sheet, including Optical Port Module,
Protocol Type of Optical Module, FS Optical Module
Type, etc.

It is the power amplifier of RU device. PA related

information has been created with the creation of RU,
BPL, or FS. Use the default value of the parameter. If
10 PA the default value is not consistent with the actual value,
modify it through this sheet. Therefore, only the “M”
operation can be performed in this sheet, including
Radio Mode, Dual Mode Working Mode, etc.

26 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

It is the board for fan control and environment

monitoring. The FCEs of the primary cabinet, auxiliary
cabinet, and slave cabinet are all configured in this
11 FCE
sheet. For the auxiliary cabinet, it is necessary to fill in
the Cabinet No, and the related records will also be
generated in this process.

This sheet is about dry contact configuration. Currently,

12 DryContact
there is dry contact on SA, SE, and FCE.

13 Tma TMA equipment related parameters

This sheet is about AISG device configuration. It is an

14 AISG abstract AISG control port. It is used for RET to control
down tilt and for TMA to amplify signals

It is about power output configuration. Currently, power

15 PowerOutlet
output exists on the TAM board and RU.

Embedded power supply equipment is a device

16 EPm
connected externally.

17 AntEntity For antenna configuration.

Fiber resource. It is about the connection between

18 Fiber Cable
BBU and RU and between RUs.

RF connection and RF feeder resources. It refers to

the connection among RU port, antenna, and TMA. If
19 RfCable the RU port configured is connected with the antenna,
the antEntity record will be created automatically
according the contents filled in by the user.

This sheet is used to configure RF extension cable. It

20 RfExtendCable
is about the connection between RU ports.

Overall transmission parameters. The parameters in

this sheet include Transmission Type, ATM Address,
21 Transmission
etc. Currently this sheet is required to be configured for
the GU and the TDS mode only.

The physical layer in the IP or the ATM transmission

22 PhyLayerPort protocol. Physical layer bearer includes E1, T1, and
Ethernet.

HDLC protocol related parameters include HDLC link

23 Hdlc No., E1T1 link No., HDLC timeslot, TSI, etc. This sheet
applies only to GU.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 27
 G_ZXSDR (V4.14) Quick Data Configuration Guide

This is the sheet of PPP protocol-related parameters.

24 Ppp
This sheet applies only to GU.

IP Layer
25 IP layer parameters configuration.
Configuration

26 Static Route Static route parameters configuration.

27 BandwidthResource This sheet contains bandwidth resource parameters.

This sheet is about SCTP parameters configuration.

SCTP protocol provides a stable and continuous data
28 SCTP
transfer service between two points. It is used to
transmit signaling in the IP network.

29 OmcChannel OMC channel parameters

This sheet is used to configure the mapping between

30 ServiceMap
service and DSCP.

The sheets in the Ground Plan template can be divided into three types according to their
functions, which are the sheets of basic parameters, the sheets of equipment parameters,
and the sheets of transmission parameters. The instructions for filling in the data of the
functional modules are described in the following sections.

3.1.1 Ground Template Customizing

In the Choose sheet of the Public template, the customized template can be generated
according to the radio mode, transmission type, and special configuration scenarios.

Figure 3-1 Template Customizing

In this sheet, no option is selected by default, i.e., the scene related sheets and the some
parameters in these sheets are hidden by default. After the radio mode, transmission

28 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

type, and the special scene are selected, click Generate Template to display related
sheets.

Note:

 For the Plan template exported from OMMB, no option is selected in the Choose
sheet. Therefore, the data to be modified cannot be found. In this case, select the
scene (or radio mode or transmission type) of the parameters in the Choose sheet,
and then modify the data.

 After the sheet is hidden, the parameter itself will not change.

3.1.2 Basic Parameters

3.1.2.1 ManagedElement

Fill in the basic information of NEs in this sheet, such as IP, NE Type, NE version,
Longitude, Latitude, etc.

The filling of this sheet is mandatory. Each NE occupies one row.

Refer to the following table for the key parameters.

Table 3-2 ManagedElement Sheet

Parameter
Item Value Description Instructions
Name

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 29
G_ZXSDR (V4.14) Quick Data Configuration Guide

1:UMTS{UMTS},
2:GSM{GSM},
4:TD-SCDMA{TD-S
The property of this parameter is
CDMA},
“W,” which means this parameter
8:CDMA{CDMA},
can be modified, but there is a
16:LTE FDD{LTE restriction on the modification, i.e.,
FDD}, this parameter can only be
RADIOMOD Radio 32:TD-LTE{LTE modified when the radio mode is
E Mode TDD} expanded, e. g., from GU to GUL,
For multi-mode but not from GUL to GU or from G
versions, it is to U.
necessary to type in This parameter should be
several figures, modified together with the
which should be SWVERSION parameter.
separated by
English character “;”,
for example, 4;32

30 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

For OMMBV12.13 and earlier

versions, only the SDR data of the
latest version supported by the
OMMB can be imported. Besides
the SDR data of the latest version,
OMMBV12.14 also supports the
data import of earlier versions
such as OMMBV12.12 and
OMMBV12.13.
The property of this parameter is
“W,” which means this parameter
can be modified, but there is a
restriction on the modification, i.e.,
it can only be modified in the
mode expansion scenario.
This parameter should be
SWVERSIO NE Version, e.g.,
NE version modified together with the
N L_V3.10.01
RADIOMODE parameter.
Different SDR software versions
may correspond to the same
SWVERSION or different
SWVERSION on OMMB, for
example, the SWVERSION
corresponding to
SDRV4.12.10.15P10, P20, and
P50 is SDRV4.12.10.15P10, while
the SWVERSION corresponding
to SDRV4.12.10.23P60 is
SDRV4.12.10.23.
For the relation between them,
refer to Section NE Compatibility
in the ZXSDR ZXSDR OMMB
V12.1x.xxPxx Release Notes.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 31
G_ZXSDR (V4.14) Quick Data Configuration Guide

BS8700
CS200
BS8800
BS8900A
BS8906
BS8900B
ZXSDR BC8900S
BS8906E
BS8912
B8901A
B8901B
BS8964 Note: There is more than one
option for BS8800 and BS8900.
And BS8900,
NE Type For GSM, BS8800 GU360 and
METYPE BS8908,
BS8900 GU360 should be
BS8800 U120, configured.
BS8800 U240,
BS8800 GU360,
BS8900 U240,
BS8900 GU360,
BS8800 U120A,
BS8900 Z01S80,
BS8900 Z01S18,
BS8900 Z02USG,
BS8912 U2100,
BS8912,BS8112,
BS8912 U2100

Select BBU-2U for B8200.

Select BBU-3U for B8300.
0:BBU-2U,
For BS8908 and BS8112 of which
BBUTYPE BBU Type 4:BBU-3U,
the functions of BBU and RRU are
5: Integration
integrated in a module (not a
rack), select integration.

32 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

It is the IP address of
the base station. It
can be configured as
IPv4 address or IPv6
address. The IPv4
address format is
decimal notation
separated by dots,
e.g., 10.0.0.1.IPv6
NE Master address is The IP for the link establishment
MEADDR
External IP hexadecimal between SDR and OMMB.
notation separated
by colon, e.g.,
2011:0db8:85a3:000
0:1319:8a2e:0370:7
366.
Do not set it to the IP
of the 127 subnet,
the 192.254 subnet,
and the 200 subnet.

User-defined information. Do not

USERLABEL NE Name - use invalid characters
`~!?@#$%^*|\/&'"<>

Network User-defined information. Do not

LOCATIONN
Element - use invalid characters
AME
Address `~!?@#$%^*|\/&'"<>

The home UMTS RNC ID. This

parameter should be filled in
UMTS correctly. Otherwise, OMMR
RNCID -
RNC ID alarms and OMMB alarms of a
base station cannot be matched
on EMS.UMTS RNC ID

GSM BSC ID of the NE. This

parameter should be filled in
GSM BSC correctly. Otherwise, OMMR
GBSCID -
ID alarms and OMMB alarms of a
base station cannot be matched
on EMS.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 33
G_ZXSDR (V4.14) Quick Data Configuration Guide

For multi-PLMN of an operator or

multi-operator, separate different
:OperatorName#mc values by “;” e.g., CMCC#460#01;
Operator c#mnc&mcc#mnc;O CMCC#460#13.
operator
and PLMN peratorName#mcc# Note: The “0” before MNC cannot
mnc&mcc#mnc;... be omitted, e.g., CMCC#460#01
cannot be written as
CMCC#460#1.
NTP
ntpServerIpA It is usually set as the external
Server IP -
ddr Ethernet IP of OMMB server.
Address

For BS8800, set CABINETTYPE

to “BC8810.” For BS8900A, set
Main
CABINETTY CABINETTYPE to “BC8910A.”
cabinet -
PE No need to configure this item for
type
BS8700 or integrated base station
or set it to “default.”
Default: 1: Normal
CutoverStatu Cutover 0:Swapping, If it is set to “0:Swapping,” the
s Status 1:Normal alarms of the base station will not
be reported to NMS.

34 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Indicate automatic
chain-establishment switch.
The automatic
chain-establishment function
means that the base station
automatically establishes the
0: Close
O&M channel between various
1:Enable automatic
Transmissi physical media and OMC.
establishment of
on (This function is different from the
transportSelf chain
auto-conn direct chain connection of IPOE
Setup 2:Enable FE
ection base station. Direct connection is
auxiliary
enabled much quicker (the CC of the
establishment of
delivered IPOE can perform direct
chain
chain connection), while the
automatic chain establishment is
much slower, about one hour.
Therefore, it is recommended that
this function be disabled in the
field).
transportSelfSetup=0 or
transportSelfSetup=1
0:Try Ethernet/PPP/ATM mode
1:Try Ethernet/PPP mode
Automatic 2:Try Ethernet/ATM mode
autoConnecti chain-esta
long:[0..6] 3:Try Ethernet mode
onMode blishment
4:Try PPP/ATM mode
mode
5:Try PPP mode
6:Try ATM mode
transportSelfSetup=2:
3:Try Ethernet mode

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 35
G_ZXSDR (V4.14) Quick Data Configuration Guide

Indicate when to initiate automatic

connection after the link is broken
for the first time. The automatic
Tolerance
connection is started by the base
duration of
firstBrokenTo station if the broken duration of
the first long:[1..300]
lerantTime the following parameters exceeds
link broken
this value: Transmission-layer
(min)
control link (SCTP, SSCOP), LMT
O&M channel, and OMC O&M
channel.

Indicate when to initiate automatic

connection after the link is broken
after the first time. The automatic
Tolerance
connection is started by the base
duration of
nextBrokenT long:[1..300],0xFFF station if the broken duration of
the second
olerantTime FFFFF: invalid the following parameters exceeds
link broken
this value: Transmission-layer
(min)
control link (SCTP, SSCOP), LMT
O&M channel, and OMC O&M
channel.

SON configuration recovery:

Enable or disable the function of
configuration rollback.
Configurati
0: Close If the link is broken after the data
configFallbac on for
is modified, after the
k rollback 1: Open
brokenTolerantTime exceeds the
switch
limit, the configuration data of will
be automatically rolled back to the
pre-configuration status.
SON configuration recovery:
Defines the time for initiating
configuration rollback after the link
Tolerance
is broken for the first time. When
brokenTolera duration of long:[15..1000]
the link-broken time of LMT O&M
ntTime the first unit:min
channel and OMC O&M channel
link broken
exceeds this duration, the
configuration data of base station
is automatically rolled back.

36 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

The running mode of NE

Default: 0 (if only one CC is used,
0:Master&slave,
NE this item must be set to 0)
1: Load-sharing,
RUNMODE running 1: dual-CC multi-mode load
2:Overlay load
mode sharing
sharing
2:Overlay load sharing (only for
CDMA)
If NE running mode is
Load-sharing, the attribute must
be configured.
1:UMTS,
2:GSM,
4:TD-SCDMA,
8:CDMA,
RUNRADIO Running
sequence<long, 8> 16:LTE FDD,
MODE mode1
32:TD-LTE
Multi-mode, e.g., 4;32
When the dual-CC load-sharing
mode is used, set this parameter
to the mode of the first CC and set
RUNRADIOMODE1 to the mode of
the second CC.

0: commissioning default: 3

2: testing Set this parameter to “0:

MAINTAINST Maintenan commissioning,” otherwise, the
3: configuring
ATUS ce status link of the base station is
5: FM testing
displayed as disconnected on
6: PM testing OMMB.

Maintenan 0: commissioning
maintainstatu ce Status 2: testing Default: 2.
sLTEFDD of LTE 5: FM testing Recommended value: 0.
FDD 6: PM testing

Maintenan 0: commissioning
maintainstatu ce Status 2: testing Default: 2.
sLTETDD of LTE 5: FM testing Recommended value: 0.
TDD 6: PM testing

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 37
G_ZXSDR (V4.14) Quick Data Configuration Guide

The base station ID (unique within

Network
Do not use invalid the network) planned by the
operatorPlan Element ID
characters operator. Do not set the parameter
nedId planned by
`~!?@#$%^*|\/&'"<> if it is not planned.
operator

Network This is the only base station ID

Do not use invalid
vendorPlann Element ID globally planned by the vendor. Do
characters
edId planned by not configure the parameter if it is
`~!?@#$%^*|\/&'"<>
vendor not planned.

User
USERDEFIN User Defined NE ID
Defined -
EDMEID Default: undefined
NE ID

When the dual-CC load-sharing

mode is used, set this parameter
RUNRADIO Running
- to the mode of the first CC and set
MODE1 mode2
RUNRADIOMODE1 to the mode of
the second CC.

When dual-CC multi-mode

load-sharing mode is used, set
NE MEADDR to the management NE
MEADDR1 -
External IP IP of the first CC and set
MEADDR1 to the management
NE IP of the second CC.

When dual-CC multi-mode

load-sharing mode is used, set
MAINTAINST Maintenan MEADDR to the maintenance
-
ATUS1 ce Status status of the first CC and set
MEADDR1 to the maintenance
status of the second CC.

 Tip:

After the RADIOMODE parameter is modified, it is required to perform all-data

synchronization.

If the base station data is imported through the plan template, the status of
MAINTAINSTATUS can be set in the plan template. If the base station data is imported
through the XML file, the MAINTAINSTATUS is “3:configuring" by default, and you need to

38 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

modify it to “normal manually on the OMMB interface. Otherwise, the link of the base station is
disconnected.

3.1.3 Equipment Parameters

3.1.3.1 Cabinet

This sheet needs to be configured for BS8800, BS8900, BS8900A, and BS8900B. The
configuration is not needed for BS8700 and BS8908.

This sheet is used only to configure the slave cabinet. The master cabinet is configured in
the ManagedElement sheet.

Note: For the same type of cabinet, the cabinet type may be different in different modes.
Select the cabinet of the corresponding mode as needed.

Refer to the following table for the key parameters.

Table 3-3 Cabinet Sheet

Item Parameter Name Value Description

“cabinetNo” should be unique. The “cabinetNo” of
the primary cabinet is fixed to “1.”
cabinetNo Cabinet number The primary cabinet and the secondary cabinet do
not need to be configured. This sheet is used only
to configure the secondary cabinet.

For the secondary cabinet of BS8800, set this

parameter to RC8810.
For the secondary cabinet of BS8900, set this
parameter to RC8910, RC8911, or RC8931.
Cabinet type
cabineType For the secondary cabinet of BS8900A, set this
information
parameter to RC8910A or RC8911A.
For the secondary cabinet of BS8900B, set this
parameter to RC8910B,RC8910B-7-RC, or
RC8910B-9-RC

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 39
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.2 Equipment

This sheet is used to configure the information of the board on the main rack of BBU. All
slots have been listed in the sheet. It is only necessary to fill in the corresponding slot
according to the actual configuration. The sheet supports 2U and 3U BBU configuration.

Each NE occupies one row. One row represents the board configuration of one main rack
of BBU. Because the main rack cannot be deleted, the data in this sheet does not support
the “D” operation.

Board type, radio mode, and function mode should be configured for each slot. Separate
these three parameters with comma. If there are two or more slots, separate the
configuration of the slots with “;”.

 CC: the board type, radio mode, function mode, and power supply mode of CC (the
last two can use the default values)

Set CC0 and CC2 to CC, set CC16/CC17/CC16B/CC17B to CCC, set CCE to CCE,
and set CCE1 to CCE1.

 Taking CC2 as the example, when non-dual-CC-dual-master is used, it can be

set to “CC,0,0” or “CC,2,0” for GSM single mode.
Taking CC16 as the example, when non-dual-CC-dual-master is used, it can
be set to “CCC,0,0” or “CCC,1;2,0” for GU dual-mode.

 Taking CC16 as the example, when dual-CC-dual-master is used (suppose

slot 1 is GU and slot 2 is FL), slot 1 can be set to “CCC,1;2,0” and slot 2 can be
set to “CCC,16,0.” (When dual-CC-dual-master is used, radioMode cannot be
set to 0. Instead, it should be set to the actual mode. )

 FS board: board type, radio mode, function mode, physical board type

Example: “FS,0,1,3” means the board type is FS, the radio mode is 0, i.e., all modes,
the function mode is 1, i.e., general mode (if UBPG3 is used, the function mode of
FS must be set to 4:GSM 36 carriers), and the physical board is 3, i.e., FS3.

 No matter which mode is used, this item should be set to “FS,0,1,x.” x=0: FS0,
x=3: FS3, x=5: FS5, x=9: FS3A.

40 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

 When there is the FS0 board in a base station (only FS0, or both FS0 and
FS3/FS5) and the base station uses GSM single-mode, it is necessary to set
the function mode of FS0 to “GSM 36 carriers,” i.e., FS,0,4,0, so that UBPG3
can support 24 carriers. If the function mode of FS0 is set to other types,
UBPG3 supports only 12 carriers. (the UBPG2 of the non-GSM single-mode
base station with FS0 configured supports only 12 carriers)

 GSM/UMTS single-mode or GU dual-mode base station (FS3): FS,0,1,1

 GSM/UMTS single-mode or GU dual-mode base station (FS3A): FS,0,1,9

 BP board: Board type, radio type, and function mode

 UBPG1: UBPG,2,0

 UBPG3: UBPG3,2,0

 BPK_d: BPK_d,1,0

 If BPN2 supports 12G+9U, set this item to BPN2,1;2,0.

 Other boards: Board type, radio mode, function mode (use the default value).

3.1.3.3 IpClock

This sheet is used to configure 1588 clock server. When the “ClockType” in the “Clock”
sheet is 1588 clock, this sheet is required to be filled in.

This sheet supports the configuration of 1588 slave server. The data of the master server
and the slave server occupy two separate rows.

Refer to the following table for the key parameters.

Table 3-4 IpClock Sheet

Item Parameter Name Value Description

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 41
G_ZXSDR (V4.14) Quick Data Configuration Guide

1: Ordinary clock
2: Boundary clock
It indicates the 1588 clock device type adopted by
1588 Clock
clockType the base station.
Device Type
The parameter must be configured the same on
the master server and the slave server.
Default: Ordinary clock

Value range: 1 – 32.

linkPriority Link Priority
Link priority of IP clock
1:IPV4,
networkPro PTP Network 2:IPV6,
tocol Protocol 3: Ethernet
Default: IPV4
Transmission mode of 1588 clock packets:
IP Clock 0: Multicast
transType Transmission 1: Unicast
Mode 2: Hybridcast
Default: Unicast

This item must be configured for IP 1588 clock

IP Address of
reference source. This attribute is valid only when
syncServer 1588
Ethernet transmission is used.
Addr Synchronization
Normally, this parameter is set to the Abis interface
Server
IP at the BSC corresponding to the base station.

Select the IP link used by the IP clock.

Used IP Layer
refIpLayerC The value of this parameter is from the “ipNo” field
Configuration by
onfig in the “IpLayerConfig” sheet. Therefore, it is
1588 IPClock
required that the “ipNo” field has been configured.
refPhyLaye Used Physical
It is not necessary to configure this parameter.
rPort Layer Port
vid VLAN ID It is not necessary to configure this parameter.

enableNeg
- Default: 1:Yes
otiation

42 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.4 Clock

This sheet is used to configure the clock reference source. If the clock reference resource
is configured, this sheet must be filled in.

One clock reference source occupies one row. One NE can be configured with two or
more clock reference sources of different priority.

Refer to the following table for the key parameters.

Table 3-5 Clock Sheet

Item Parameter Name Value Description

This parameter is used to synchronize base
station and clock reference source.
0: Frequency synchronization
1: Phase synchronization
Actually, synchronization Ethernet is a physical
synchronization mode. It provides only frequency
synchronization mode. The 1588 clock carries
Clock
clockSyncMod time stamp in the packets. The clock information
Synchronization
e can be measured and estimated by measuring
Mode
the transmission period of the time stamp carried
in the packets. This can achieve both frequency
synchronization and time synchronization.
Normally, frequency synchronization is used for
GU base stations, and phase synchronization is
used for LTE base stations and GUL base
stations.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 43
G_ZXSDR (V4.14) Quick Data Configuration Guide

1: Inner GNSS
2: Outer facepanel GNSS
3: Outer backpanel GNSS
17: RRU inner GNSS
4:1PPS+TOD
5: GNSS cascade clock
Clock Reference 14: 1PPS+TOD backup
clockType Source Type of 6: BITS-2MHz clock
Clock Device 7: BITS-2Mbps clock
8: Line clock-local board
13: SyncE clock,
10: SyncE+1588 clock
11:1588{1588}
1: GNSS, 8: Line clock-local board, 11: 1588,
and 13: SyncE clock are often used.

Clock Priority of Value range: 1 – 8.

clockPriority Clock Reference This parameter indicates the priority of clock
Source Type reference resource.“1” refers to the top priority.

1:USR1_A{USR1_A},
2: Outer compass receiver
3:RGPS{RGPS},
4:UCI_RGPS{UCI_RGPS},
receiverHardw GNSS Receiver 5:UCI_COMPASS{UCI_COMPASS}
areType Hardware Type If built-in GNSS is used, this parameter is invalid
and does not need to be configured.
External panel GNSS CDMA: 0,2,3,4; TDS: 4,5;
TDL:4.5
Value range of outer backplane GNSS: 0,4,5

1:GPS{GPS},
2:GLONASS{GLONASS},
3:GPS+GLONASS{GPS+GLONASS},
GNSS Receiver
receiverType 5: COMPASS
Working Type
7: COMPASS priority
8: GPS priority
13: Receiver self-adaptive

44 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

This parameter is used to configure the

operating mode of GNSS receiver. "Survey In" is
recommended but "Fixed Mode" is not
recommended.
receiverOperat Receiver
1: Survey In
ingMode Operating Mode
2: Fixed Mode
For GU, LTE-FDD, TD-SCDMA, and LET-TDD,
this parameter can be configured. For other
products, this parameter cannot be configured.

long:[1..4]
GNSS Minimum It indicates the minimum number of satellites for
minStarNum Number of Search satellite timing. It is also the parameter of
Stars satellite alarm threshold and the default value is
4.

1: Yes
0: No
enableSyncE Enable SyncE This parameter can be configured only when
“clockType” is “SyncE+1588 clock.”
Default: 0: No.

1: Yes
0: No
This parameter can be configured only when
“clockType” is “SyncE+1588 clock” or “SyncE
clock.”
This parameter indicates whether the clock
upload mode is Synchronization Status Message
(SSM).SSM is the quality level for sending timing
signals through the timing synchronization link in
isSSM Enable SSM the synchronization network. The node clock in
the synchronization network obtains the
parent-node clock information by reading the
SSM, and performs related operations on the
clock of local node, such as tracing and
changeover. Meanwhile the synchronization
message of local node is sent to the subordinate
node.
If “3: SyncE Clock” is adopted, this parameter
should be set to “1:Yes”.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 45
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.5 RU

This sheet is used to configure RU and related information. The filling of this sheet is
mandatory. Each RU occupies one row.

IMPORTANT:

RU falls into RRU and RSU. There are two kinds of RSU configuration: 1. Configure RSU
in the primary cabinet. If the RSU rack has been created during the creation process of
the primary cabinet, configure the RSU directly in this sheet; 2. Configure RSU in the
slave cabinet. It is necessary to create the slave cabinet in the Cabinet sheet and then
configure RSU in this sheet.

Refer to the following table for the key parameters.

Table 3-6 RU Sheet

Item Parameter Name Value Description

Format: RackNo, ShelfNo, SlotNo,
The value ranges are:
RU Board, incl. RackNo: RRU:51..201, RSU:2..50
RUDevice
RRU and RSU ShelfNo: 1
SlotNo: 1
For example: 51,1,1
Type of RRU Refer to the last sheet of the Plan template,
RUType
Name of RRU i.e., RUInfo.
1:RRU,
subRackType Sub-rack type 2:RSU,
6:PB1000 (for Qcell)

If RRU is in
Cabinet, the
attribute should be
filled in, RSU
refCabinet No information required to be filled here
doesn't need.
The value is
"cabinetNo" from
Cabinet sheet.

46 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

For multi-mode configuration, the values

need to be separated by English character
“;”, for example, 4;32
0:ALL{ALL},
1:UMTS{UMTS},
radioMode Radio Mode
2:GSM{GSM},
4:TD-SCDMA{TD-SCDMA},
8:CDMA{CDMA},
16:LTE FDD{LTE FDD},
32:TD-LTE{LTE TDD}

The value should be configured according

to the board type actually used.
0:GSM/LTE FDD Mixed Mode(Ignore the
radio mode of PA),
1:UMTS Single Mode,
2:GSM Single Mode,
5:LTE-FDD Single-carrier,
functionMode Function Mode 1280:LTE-FDD Single Mode,
1281:LTEFDD Two-carrier,
100663297:LTE-IR,
452984833:LTE-IR,
452984841:LTE-IR(IQ Compressed),
50331653:TD-SCDMA IR,
24:GSM/UMTS Mixed Mode,
26:GSM/LTE FDD Mixed Mode

The same as the configuration of

manageId -
RUDevice.

This parameter indicates the attributes of

RU optical port device set. It is an optional
parameter and should be configured
according to the actual requirements.
connectModeWith Uplink Connection
0:single up-link optical line
UpRack Mode
1:double master&slave optical lines
2:multiple load-sharing optical lines. For
GSM, only “0:single up-link optical line” is
supported currently.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 47
 G_ZXSDR (V4.14) Quick Data Configuration Guide

This parameter is used to configure the

attributes of RU RF port device set. It is an
optional parameter and should be
Diversity Reception
diversityMode configured according to the actual
Mode
requirements.
0:Normal diversity reception
1:Cross diversity reception
User-defined information. Do not use invalid
RRU description characters &'"<>
userLabel
information The alarm information of RU will contain this
parameter.

 Knowledge:

There are three methods to achieve diversity, as listed below:

Normal diversity: This is for the single-Tx RU or a PA of a dual-Tx RU. Every PA is

single-Tx-dual-Rx. In this case, for the dual-Tx RU, the two Pas are often used for different
cells.

Cross diversity: This is for the two PAs of a dual-Tx RU. Both PAs are connected only to the
TX/RX port, and the TX/RX of each PA is also the diversity reception of the other PA. In
this sense, each PA actually has the single-Tx-dual-Rx function. Therefore, the two PA s of
the dual-Tx must cover the same cell.

RF extension: This is for single-Tx RU, i.e., two single-Tx RUs are needed to cover the same
cell (it is the same as the case that the two Pas of a dual-Tx RU cover the same cell). In this
case, these two RUs are connected only to the TX/RX port and the TX/RX of each RU is
also the diversity reception of the other RU. Because they are two independent RUs, an RF
extension is needed between these two RUs, so that they can get the diversity reception
signals from each other. (For the cross diversity reception of dual-Tx RU, the RF extension
cable is connected inside RRU.)

3.1.3.6 FiberDevice

This sheet is used to configure optical port related information. This sheet is optional for
configuration.

48 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

When this sheet is not configured, the optical port rate of FS is 1.25G by default.

Optical port device data will be created with the creation of the boards with optical port
device such as RU, BPL, and FS. If the values of the optical port device related
parameters are not consistent with the default values, they may need to be modified in
this sheet. Therefore, only the “Modify” (M) operation is allowed in this sheet, while the
“Add” (A) or “Delete” (D) operations cannot be performed.

In other cases, do not fill in this sheet.

Table 3-7 FiberDevice Sheet

Item Parameter Name Value Description

FiberDevic Physical port of Ir Format: RackNo, ShelfNo, SlotNo
e interface e.g., 1,1,3 or 51,1,1

Port No. of the physical port.

Connected board
port Port Number of FS: 0-5
port No.
Port Number of RU: 1-2

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 49
G_ZXSDR (V4.14) Quick Data Configuration Guide

Values:
1:1.25G,
2:2.5G,
3:3G,
4:4G,
6:6G,
10:10G,
255: adaptive
Set FS as needed. Set RU to 255.
Set the optical module rate on RU to 255. It will
adapt to the rate of the upper-level optical port
connected.
opticalMod
Optical port rate The FS optical module rate configured here should
uleType
be equal to or smaller than the actual optical
module rate.
The optical port rate configured on FS should not
exceed the maximum rate supported by RU, e.g.,
R8881 is configured with the 1.25G optical
module, so the rate of the corresponding FS port
can only be set to 1.25G. Do not set it to 2.5G or
higher.
For GU dual-mode, 1.25G supports “N+6*M<=24”
(N is the number of TRXs, M is the number of
CSs), while 2.5G supports “N+6*M<=48” (N is the
number of TRXs, M is the number of CSs).

50 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

{FiberDevice is not RRU}

0:PHY CPRI,
1:PHY LTE IR,
2:PHY OBSAI,
3:PHY OBRI,
4:PHY GBRS,
5:PHY TD-SCDMAIR,
protocolTyp Protocol type of
{FiberDevice is RRU}
e optical module
10:APP ZTE,
11:APP LTE IR,
12:APP TD-SCDMAIR,
13:APP OBRI
For GSM or GU dual-mode, select 0 when the
FiberDevice is not RRU; select 10 when the
FiberDevice is RRU.

3.1.3.7 PA

This sheet is used to configure the PA related information of RU devices.

PA related parameters will be created with the creation of RU. When the values of the PA
parameters are inconsistent with the default values, they may need to be modified in this
sheet. In other cases, it is not necessary to fill in this sheet. Therefore, only the “Modify”
(M) operation is allowed in this sheet, while the “Add” (A) or “Delete” (D) operations
cannot be performed

Refer to the following table for the key parameters.

Table 3-8 PA Sheet

Item Parameter Name Value Description

Format: RackNo, ShelfNo, SlotNo,
The value ranges are:
RackNo: RRU:51..201, RSU:2..50
RUDevice RU Board of PA
ShelfNo: 1
SlotNo: 1
For example: 51,1,1

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 51
G_ZXSDR (V4.14) Quick Data Configuration Guide

Port No. on the The antenna feeder port No. on RU.(It is

port
RU device of PA consistent with the silkprint).

It is the frequency band ID of the port on the RU

Frequency Band
suppBand device of PA. It is used together with the RU
ID of PA
Device and port to define one PA.

Note: For multi-mode configuration, the values

need to be separated by English character “;”,
e.g., 1;2, which means GU dual-mode.
0:ALL{ALL},
1:UMTS{UMTS},
radioMode Radio standard
2:GSM{GSM},
4:TD-SCDMA{TD-SCDMA},
8:CDMA{CDMA},
16:LTE FDD{LTE FDD},
32:TD-LTE{LTE TDD}

The allocation method of PA resources in

Dual-mode
dual-mode, for example, 2G+2U indicates the
dualMode Working Mode of
PA supports two GSM carriers and two UMTS
PA
cells.

1,2,3,255: Invalid
Sub-frequency
branchBand The sub-frequency band supported by PA.
Band of PA
Default: 255

It is the central transmission frequency point of

Tx Channel.
The “txCenterFreq” should not be set to the
Tx Central
txCenterFreq minimum or maximum bandwidth supported by
Frequency Point
PA (at least 200 k).
Default: 0, which indicates automatic
calculation by SDR.
It is the central reception frequency point of Rx
Rx Central Channel.
rxCenterFreq
Frequency Point Default: 0, which indicates automatic
calculation by SDR.

52 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

0: No; 1: Yes
Enable primary Configure it to “1: Yes”. When the primary
detectSwitch diversity balance diversity reception is not balanced, PA will
detection report alarm.
Recommended value: 1.

3.1.3.8 FCE

The FCEs of the primary cabinet and the secondary cabinet do not need to be configured.
When data is imported into OMMB, OMMB will create the corresponding FCE
automatically according to the primary/secondary cabinet.

In the process of configuring the FCE of the auxiliary cabinet, it is not necessary to create
an auxiliary cabinet separately, because the cabinet will be created automatically by this
sheet when the CTRL_AUX_CABINET_NO field (auxiliary cabinet No.) is filled in.

Table 3-9 FCE Sheet

Item Parameter Name Value Description

Format: RackNo, ShelfNo, SlotNo
FCE Board FCE board e.g., 1,1,18
Location of FCE board

It is the No. of the auxiliary cabinet where the

FCE board is located. The No. must not be
repeated.
Auxiliary cabinet
AuxCabinetNo This field is only required for the FCE board on
No.
the auxiliary cabinet. This field shall not be
configured for the FCE board on the primary
cabinet or the slave cabinet.

If BS8900B is used and FCE is installed on the

auxiliary cabinet, this attribute is valid and must
AuxCabinetTy Auxiliary cabinet be configured. Its values can be:
pe type BC8910B-SC
BC8910A-SC
RC8910B-7-BC-SC

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 53
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.9 DryContact

This sheet is about dry contact configuration. This sheet is optional for configuration.

Dry contact data will be created when the SA, SE, and FCE boards are created. This
sheet also supports the configuration of customized dry contact.

Refer to the following table for the key parameters.

Table 3-10 FCE Sheet

Parameter
Item Value Description
Name
Dry contact needs to be configured on the slot,
shelf, and rack of the SA, SE, FCE, and RU
DryContact
Dry Contact Info board.
Board
Format: RackNo, ShelfNo, SlotNo,
For example: 51,1,1
It indicates the No. of the dry contact alarm to
be configured. The boards that support dry
dryNo Dry Contact No.
contact alarms include the SA, SE, and FCE
boards, and RF boards.
Dry contact It contains 128 bytes at most. Default: null. Do
userLabel
description not use symbols like & ' " < > # % / \ ? @ : ,
0: Input dry contact
dryType Dry Contact Type
1: Output dry contact

It is used to configure the output dry contact

configuration status. This parameter is valid
Output Dry
outDryType only when the dry contact type is output dry
Contact Status
contact.
0: Output low level. 1: Output high level.

The output dry contact description is

Output Dry user-defined. This parameter is valid only
outDryName
Contact Name when the dry contact type is output dry
contact. It contains 128 bytes at most

54 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

This parameter is used to configure dry

contact alarms. It is valid only when the dry
almStatus Alarm Status contact type is input dry contact.
0: Alarm when closed
1: Alarm when open

This parameter is used to configure the

contents of dry contact alarms. This parameter
Dry Contact is valid only when the dry contact type is
almNo
Alarm Name output dry contact. The user can either define
the contents of the dry contact or choose the
dry contact alarm preconfigured in the system.
When dryType=0, this attribute is valid.
The user can either define the contents of the
dry contact or choose the dry contact alarm
preconfigured in the system.
isSelfDefineAlm==0
198092044:Cabinet door alarm,
198092045:Flooding alarm,
198092046:Smog alarm,
198092268:PWR monitoring unit alarm,
Dry Contact isSelfDefineAlm==1
almNo
Alarm Name
198092550:Self Define Drycontact 1,
198092551:Self Define Drycontact 2,
…
198092599:Self Define Drycontact 50
isSelfDefineAlm==1 and GU
198096424:Self Define Drycontact 51,
198096425:Self Define Drycontact 52,
…
198096473:Self Define Drycontact 100

 Tip:

For the base stations of BS8900A and BS8900B, the dry contacts connected in the factory
settings (such as the dry contacts of cabinet door and smog alarms) do not need to be

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 55
 G_ZXSDR (V4.14) Quick Data Configuration Guide

configured, because the configuration can be generated automatically after the data is
imported into OMM. The dry contacts that need self-definition should be configured
manually. The Nos. of these self-defined dry contacts shall not occupy the Nos. of internal
dry contacts.

3.1.3.10 Tma

This sheet is used to configure TMA equipment. This sheet is optional for configuration.
One TMA occupies one row.

The configuration in this sheet is used to configure TMA gain and other related
parameters.

The filling of the fields in this sheet is very simple (refer to the instruction of the template),
and no further description will be given in this Guide.

3.1.3.11 AISG

This sheet is used to configure the PA related information for the AISG devices. This
sheet is optional for configuration. One AISG device occupies one row.

AISG device is used for RET to control down tilt and for TMA to amplify signals.

When AISG device is commissioned, the RfCable sheet must be configured first. Only
when RF connection is configured can AISG devices work normally.

Refer to the following table for the key parameters.

Table 3-11 AISG Sheet

Item Parameter Name Value Description

56 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Format: RackNo, ShelfNo, SlotNo, which

should be configured in the “RU” sheet in
advance.
The value ranges are:
Aisg Board RU Board Info
RackNo: RRU:51..201, RSU:2..50
ShelfNo: 1
SlotNo: 1
For example: 51,1,1
aisgDeviceId AISG Device Id Unique within a base station

Device Serial Value range: 1 – 32.

uniqueId
Number This is the unique SN of the device.

1:RETC,
17:MULTI_RET,
3:ATMA,
90:NOTCH_FILTER,
2:MULTI_TMA,
devType Device Type 241:ACOM,
226:AETMA,
209:NSNRET,
210:LGPTMA
Users should select a device type according to
the actual situation.

vendorCode Vendor Code 127 bytes at most

1:1.1
aisgVersion AISG Version
2:2.0

multiAntNo Multi-sub-unit No. Value range: 1 – 4. 255: Invalid.

It contains 128 bytes at most, and can be left

Customized
userLabel unconfigured.
Descriptive Field
Do not use symbols like & ' " < > # % / \ ? @ : ,
Integer: 0 – 12
fatherPort Superior Channel It is used for SDTMA device of NSN private
protocol. The value for other devices is 0.

Integer: 0 – 12
selfPort Local Channel It is used for SDTMA device of NSN private
protocol. The value for other devices is 0.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 57
 G_ZXSDR (V4.14) Quick Data Configuration Guide

It indicates the antenna connected with RF

cable.
For GU and LTE FDD, the value of the
parameter is from the value of the “antEntityNo”
field, which is in the “RfCable” sheet and should
refAntEntity Connected Antenna
be configured in advance.
For TDS and LTE TDD, the value of the
parameter is from the value of the “antEntityNo”
field, which is in the “IrAntGroup” sheet and
should be configured in advance.
Connected TMA Integer: 1 – 96. The TmaNo field in the “TMA”
refTma
Device should have been configured.

3.1.3.12 PowerOutlet

This sheet is used to configure the power output port. The filling of this sheet is optional.
Only when the TAM board or the RU of some models is configured can the data in this
sheet be configured.

The power output mainly supplies power for AISG equipment.

RU has two voltage output ports, NSBT (old RU) and AISG (new RU). After the switch of
NSBT is enabled, the AISG port will also output voltage. Both can be connected with
AISG devices and supply power to AISG devices.

The TAM board is used mainly to supply power for TMA. There are 6 ports on this board,
and each port can support the power supply of one device.

One power output port occupies one row. The same power output device can be
configured with two or more power output port records, but the values of the switchStatus
field and the voltage field must be consistent.

Refer to the following table for the key parameters.

Table 3-12 PowerOutlet Sheet

Item Parameter Name Value Description

58 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Currently, only the TAM board and some RU

models support power output.
It is required that TAM should have been
PowerOutlet PowerOutletBoard configured in the “Equipment” sheet or the
Board Info RU supporting power output have been
configured in the “RU” sheet.
Format: RackNo, ShelfNo, SlotNo, for
example, 51,1,1
Value Range: 0~5
port Port No.
Power Output Port No.

It indicates the working current value of the

port.
Working current Value Range:
currentValue
value {voltage == 0}[75..400],
{voltage == 1}[75..300],
{voltage == 4294967295}[0.. 4294967295]

0: currentDetect
1: pulsewidthDetect
Alarm Detection When the current on this port is abnormal,
almDetectMode
Mode alarms will be reported. This attribute is
used to set the detection mode of output
current.

0: Close
1: AISG RS485{AISG RS485},
2: NSBT RS485{NSBT RS485}
If the TAM board is configured, set this
parameter to “0.”If RU is configured, set this
parameter to “1” or “2” according to the
switchStatus Switch Status actual situation.
If the RU of an inner NSBT is connected, fill
in “2:NSBT RS485.” Otherwise, fill in
“1:AISG RS485.”
Currently, only RSU40 U218 (B8B) and
RSU82 S2100 (B8B) use inner NSBT, while
others use outer NSBT.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 59
G_ZXSDR (V4.14) Quick Data Configuration Guide

0:140{140},
1:220{220},
4294967295: Invalid
Set the output voltage of RU to 14 V or 22 V
according to the requirements for the power
supply of AISG devices.
voltage Voltage
0: 14 V; 1: 22 V.(unit: 100 mV)
Select 22 V unless otherwise required.
Because some old TAM devices need 14 V
power supply, the RU of inner NSBT
launched later supports 14 V output voltage
too.

Value Range: 20~80,100

Under Current When the actual current of the TAM board
lowerLimitPerce
Alarm Threshold power supply channel is less than “Working
nt
Percent Current Value*local value/100,” under
current alarm is reported.

Value Range: 100,120~180

When the actual current of the TAM board
upperLimitPerce Over Current Alarm
power supply channel is greater than
nt Threshold Percent
“Working Current Value*local value/100,”
over current alarm is reported.
Value Range:
0: Close
portSwitchStatu 1: Open
Port Switch Status
s This parameter is used to configure the
switch status of whether to enable current
control.

Note:

When a new RU is connected to an AISG (RET, ATMA, etc.), the switchStatus parameter is
added to control the power of AISG in the configuration data. Because this switch is disabled
by default, it is necessary to set the status of the switch to make sure RU supply power to the
AISG device normally. Otherwise, the “link disconnected” alarms may appear.

60 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

The AISG of old RUs does not have the switchStatus parameter. Therefore, the status is
enabled by default and does not need to be configured.

The simplest way to find out whether an RU is a new RU is checking whether there is the
PID data on the label of the RU. If there is the PID data on the label, the RU is a new RU.
Otherwise, it is an old RU.

The following are examples of the labels of RSU60E and R8881.

3.1.3.13 Epm

This sheet is used to configure embedded power equipment.

Refer to the following table for the key parameters.

Table 3-13 Epme Sheet

Item Parameter Name Value Description

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 61
 G_ZXSDR (V4.14) Quick Data Configuration Guide

It indicates the board for BBU to connect with

refSdrDeviceG the embedded power device (SA/ SE/RU).
Connected RRU
roup Format: RackNo, ShelfNo, SlotNo,
For example: 51,1,1
0:ZXDU58 B900,
1:ZXDU58 B121,
2:ZXDU68 B201,
3:ZXDU150,
4:ZXDU45,
5:ZXDU75,
Built-in Power
powerType 6:ZXDU58 B121(V4.5),
Device Type
7:ZXDU68 B201(V5.0),
8:ZXDU68 W301,
9:ZXDU68 S301,
10:ZXDU58 B121(V2.2),
11:ZXDU68 B201(V5.0R99M03),
100:Shelter JZ9
0: Transparent transmission
1: Parse
Transparent transmission means that OMMB
does not display the alarm of the power supply
equipment, but transmits the message header
Data Processing to the OMM of the power supply equipment.
dataProcessM
Mode of built-in Base station parse means that OMMB can
ode
power device display the alarms of the power supply
equipment.
If the power supply device is deployed with
Netnumen, do not set this parameter to
“parse.” Otherwise, power related alarms will
be reported repeatedly on OMMB.

3.1.3.14 AntEntity

This sheet is used to configure antenna type and gain. This sheet is hidden by default
and it does not need to be configured. This sheet needs to be configured only when there
is TMA or RET.

62 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Table 3-14 AntEntity Sheet

Item Parameter Name Value Description

Antenna entity
antEntityNo Antenna Entity No.
number

Used antenna
AntProfile Antenna gain
attribute

retDeviceType RET device type Antenna type.

3.1.3.15 FiberCable

This sheet is used to configure fiber connection, i.e., the topology of fiber connection.

Refer to the following table for the key parameters in this sheet.

Table 3-15 FiberCable Sheet

Item Parameter Name Value Description

Optical Port of Format: (RackNo,ShelfNo,BoardNo):

ref1FiberDevice Previous Hop in Ports of BBU: 0-5, e.g., (1,1,3):0.
Topology Structure ports of RRU: 1-3

Format: (RackNo,ShelfNo,BoardNo):
Ports of RRU: 1-3 (R8882C has three
Optical Port of Next optical ports, while other RUs only have two
ref2FiberDevice Hop in Topology optical ports).
Structure Normally, the next level of an RU is an RU.
For CRAN, the next level of the last RRU is
RS.

 Tip:

Port Number of FS: 0, 1, 2, 3, 4, 5

Port Number of BPL: 0, 1, 2

Port Number of RU: 1, 2, 3(R8882C has three optical ports, while other RUs only have 1-2
optical ports)

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 63
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.16 RfCable

This sheet is used to configure RF connection. This sheet is hidden by default. Normally it
does not need to be configured. Fill in this sheet only when TMA is configured.

RF connection shows the connection relation between RU port, antenna, and TMA.

One connection relation occupies one row. Therefore, only two of RU port, antenna, and
TMA can be configured in one row. In the same NE, the same connection relation cannot
be repeated.

Refer to the following table for the key parameters.

Table 3-16 RfCable Sheet

Item Parameter Name Value Description

It indicates the RF port connected with the
RF cable, i.e., the RU port.
refRfDevice RU Port Info Format: (RackNo,ShelfNo,BoardNo):Port
If RU device is used, the port No. is 1 and 2,
for example, (1,1,3):1

It indicates the antenna connected with RF

cable.
Value range: 1 – 65535. For TDS or LTE
Antenna Entity TDD, this value may come from the value of
antEntityNo
Number the antEntityNo field in the “IrAntGroup”
sheet. For other modes, a record of
antenna entity will be generated
automatically according to this No.

64 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

It indicates the type of the device connected

with the antenna entity. If antEntityNo is
configured, this parameter should also be
configured.
0: Non-RET

retDeviceType RET Device Type 1: Uni-antenna RET

2: Uni-direction TMA
3: Continuous power antenna system
4: Bi-direction TMA
5: LNA
17: Multi-antenna RET

It indicates the TMA connected with the RF

cable.
refTma TMA No. The value is from the value of the tmaNo
field, which is in the “Tma” sheet and
should have been configured.
double:[0..8]
Downlink Step length: 0.1, unit: dB
dlAttenuation
attenuation DL attenuation of RF cable.
Default: 0
double:[0..8]
Step length: 0.1, unit: dB
UL attenuation of RF cable. When an RF
ulAttenuation Uplink attenuation
cable is used to connect RU and TMA
equipment, 0.5dB is recommended. 0dB is
recommended in other situations.

 Tip:

If TMA or AISG is not used, it is not necessary to configure the rfcable sheet. This sheet can
be created automatically when RU is created.

When RU is deleted, delete the rfcable sheet (and the FiberCable sheet and other related
sheets) first, and then delete the RU. Because the Plan template can be customized, you need
to select “TMA/RET” in the Choose sheet first to see the rfcable sheet.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 65
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.3.17 RfExtendCable

This sheet is used to configure RF extension cable. It shows the connection relation
between two RU ports (RxOut and RxIn).This sheet is hidden by default. The filling of this
sheet is optional. It needs to be filled only when the two single-Tx RUs need RF
extension.

It should be noted that the two RUs in RF extension configuration are in mutual exclusive
relation, e.g., it is necessary to configure both the extension from RU 51 to RU 21 and the
extension from RU 52 to RU 51.

3.1.4 Transmission Parameters

3.1.4.1 Transmission

This sheet is used to configure GU transmission mode, transmission medium, and ATM
transmission address.

The filling of the fields in this sheet is very simple (refer to the instruction of the template),
and no further description will be given in this Guide.

3.1.4.2 PhyLayerPort

This sheet is used to configure physical layer port. The filling of this sheet is mandatory.

66 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

One physical layer port occupies one row, and an NE can occupy two or more rows.

It is the physical layer of FE or E1 (IPOE or ATM) transmission. Physical layer bearer

includes, E1, T1, and Ethernet.

Refer to the following table for the key parameters.

Table 3-17 PhyLayerPort Sheet

Item Parameter Name Value Description

It is used to uniquely identify the physical
phyLayerPortN Physical Layer Port
layer resource. It can be customized within
o No.
its value range by the user.

This sheet is hidden by default. It needs to

be configured only in the dual-CC
load-sharing scenario. Because the two CCs
are independent and are connected with
transmission equipment respectively, create
two records in the “PhyLayerPort” sheet,
corresponding to the two CCs respectively,
TransportNetw Object ID of for example,
orkId transmission network If “Object ID of transmission network” is set
to 1, the transmission is used for “Running
mode1.”
If “Object ID of transmission network” is set
to 2, the transmission is used for “Running
mode2.”
Running mode1 and Running mode2 are
configured in the ManagedElement sheet.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 67
G_ZXSDR (V4.14) Quick Data Configuration Guide

0:RNC/BSC/CN/MME,
1:SDR,
2:Third-party
Opposite network element connected by the
object. In the case of base station
connectObject Connection Object cascading, set this property of upper-level
base station or upper-level CC to "SDR." If
its value is set as a third-party device, it
indicates that the base station provides the
data transmission channel for the third-party
device in case of ATM+FE cascading.

It is the Ethernet used by the port in case of

IP transmission mode.
The boards that support the GE equipment
are the main control boards like CC and
refGeDevice Used Ethernet CCC.
Format: SlotNo.:Port
Port value: 0, 1
e.g., 1:0, Port 0 of Slot 1 (Port 1 is the
cascading port, i.e., Debug port)

It is used to decide whether the transmission

media is a Relay port or an Ethernet port
whether mediumtype when refGeDevice is configured.
isRelay
is relay port 0: No
1: Yes
Default value: 0: No

This parameter can be configured when

Ethernet is used.
The Ethernet operating mode has to be
operatingMode Operating Mode
consistent with the configuration at the peer
end. For the rate mode, we need to consider
whether it is supported by the network cable.

68 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

This parameter can be configured when

Ethernet is used.
Under the Ethernet transmission mode, the
TX bandwidths are:
{operatingMode==0}[100..1000000] step
egressPeakBit Transmitting 100,
Rate bandwidth (Mbps)
{operatingMode==1}[100..10000] step 100,
{operatingMode==2}[100..100000] step 100,
{operatingMode==3}[100..1000000] step
100,
{operatingMode==4}[100..100000] step 100
The port uses E1 as bearing for the ATM
transmission mode or the IPoverPPP
transmission mode.
The boards that support E1 include SA and
refE1Device Used E1
SE.
Format: SlotNo.:Port
Port value: 0..7
For example: 13:0

The port uses T1 as bearing for the ATM

transmission mode or the IPoverPPP
transmission mode.
The boards that support T1 include SA and
refT1Device Used T1
SE.
Format: SlotNo.:Port
Port value: 0..7
For example: 13:0

3.1.4.3 Hdlc

This sheet is about HDLC channel related configuration. Refer to the following table for
the details of the main parameters.

Table 3-18 HDLC Sheet

Item Parameter Name Value Description

hdlcNo HDLC Link Number [0..16]

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 69
G_ZXSDR (V4.14) Quick Data Configuration Guide

The value is the same as the value of the

Used Physical Layer
refPhyLayerPort phyLayerPortNo field in the
Port
“PhyLayerPort” sheet

Time Slot Bit For OMMBV12.12.40P24 and earlier

timeSlotBitMap
Mapping versions.

It indicates the slot of the E1/T1 used by

the HDLC link.
Just fill in the number of the slots used.
Example1: 8-15, meaning the slots
TransportNetwork Time Slot Bit
numbered from 8 to 15 are used.
Id Mapping
Example1: 2-5.7, meaning the slots
numbered from 2 to 5 and the 7th slot
are used.
Default: 1-31

TSI cascade configuration

BTS cascade number. Indicates the
BTS cascade
btsCascadeNo cascading configuration of different lower
number
level NEs under the same base station in
the E1 cascading scenario.

TSI cascade configuration

ingressTimeSlotBi Inlet time slot bit Indicates the time slot cross link ID in TSI
tMap mapping cascading mode. Indicate the routing
number in ATM cascading mode.
TSI cascade configuration
Describes which time slots in the inlet
E1/T1 are reserved for the lower-level
base station. Each bit corresponds to
one time slot. 0 indicates not reserved for
ref2PhyLayerPort Used E1/T1/FE outlet the lower-level base station. 1 indicates
reserved for the lower-level base station.
Example1: 8-15, meaning the slots
numbered from 8 to 15 are used.
Example1: 2-5.7, meaning the slots 2-5
and slots 5-7 are used.

70 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

TSI cascade configuration

Describes which time slots in the outlet
E1/T1 are reserved for the lower-level
egressTimeSlotBit Outlet time slot bit
base station.
Map mapping
The value of this parameter is from the
value of the phyLayerPortNo field in the
PhyLayerPort sheet.

3.1.4.4 Ppp

This sheet is about PPP link related configuration. Refer to the following table for the
details of the main parameters in this sheet.

Table 3-19 PPP Sheet

Item Parameter Name Value Description

pppLinkNo PPP Link No. [0..15]

This sheet is hidden by default. It needs to be

configured only in the dual-CC load-sharing
scenario. Because the two CCs are
independent and are connected with
transmission equipment respectively, create
two records in the “Transmission” sheet,
corresponding to the two CCs respectively,
TransportNetw Object ID of for example,
orkId transmission network If “Object ID of transmission network” is set
to 1, the transmission is used for “Running
mode1.”
If “Object ID of transmission network” is set to
2, the transmission is used for “Running
mode2.”
Running mode1 and Running mode2 are
configured in the ManagedElement sheet.
It is the IP address of the base station.
A base station can be configured with several
localIp Base Station IP
IPs, which are used for operation &
maintenance and services of different modes.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 71
G_ZXSDR (V4.14) Quick Data Configuration Guide

0:PPP{PPP},
PPP Encapsulation 1:ML-PPP{ML-PPP}
protocolType
Type This parameter must be set to “1:ML-PPP”
unless otherwise required.
The value of this parameter is from the value
refHdlc Used HDLC Channel
of hdlcNo in the HDLC sheet.

2:Long sequence,
6:Short sequence,
Long/short Sequence
mpCode 0xFF: Invalid
of MP Head
This parameter must be set to “2:Long
sequence” unless otherwise required.
{mpCode==2}[1..8],
{mpCode==6}[1..4],
mpClass MP Priority 0xFF: Invalid
This parameter must be set to “4” unless
otherwise required.

1: Yes
0: No
For the integration of SDR and BSC V3
non-MO, it should be configured through the
Whether Support IP negotiation with BSC. When the bandwidth is
ipCompress
Compression sufficient, configure it to “0:No”; when the
bandwidth is insufficient, configure it to
“1:Yes”.
If SDR is integrated with BSCV3 MO or
BSCV4, this parameter must be set to “Yes.”
1: Yes
0: No
Whether this PPP link is used for cascading.
isUsedToFECa Whether Used for FE The cascading mode is E1/T1+Ethernet, i.e.,
scade Cascading the upper-level base station uses the IPOE
mode and the lower-level base station uses
the FE mode.
Default: 0:No

72 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.4.5 IpLayerConfig

This sheet is about IP related configuration. When IP transmission is used, it is required

to fill in this sheet.

This sheet is used mainly to configure Gateway IP, Network Mask, Prefix Length of IPv6
address, Used Ethernet Link, IP Domain, and VLAN ID.

Refer to the following table for the key parameters.

Table 3-20 IpLayerConfig Sheet

Item Parameter Name Value Description

IP configuration ID. It can be customized by
IP parameter link
ipNo users within the value range. It will be used for
number
the configuration of SCTP and ItfUniBts.

This sheet is hidden by default. It needs to be

configured only in the dual-CC load-sharing
scenario. Because the two CCs are
independent and are connected with
transmission equipment respectively, create
two records in the “IpLayerConfig” sheet,
corresponding to the two CCs respectively, for
Object ID of example,
TransportNetw
transmission
orkId If “Object ID of transmission network” is set to
network
1, the transmission is used for “Running
mode1.”
If “Object ID of transmission network” is set to
2, the transmission is used for “Running
mode2.”
Running mode1 and Running mode2 are
configured in the ManagedElement sheet.

The Ethernet physical layer port that bears IP.

The value of this parameter is from the value of
refPhyLayerPo Used Physical the phyLayerPortNo field in the PhyLayerPort
rt Layer Port sheet. This parameter is mutual exclusive with
refPppLink. refPhyLayerPort isfor IPOFE.
refPppLink is for IPOE1.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 73
G_ZXSDR (V4.14) Quick Data Configuration Guide

Configure this parameter according to the

vid VLAN ID
Planned VLAN

The PPP link that bears IP.

The value of this parameter is from the value of
refPppLink Used PPP Link the pppLinkNo field in the PPP sheet.
refPhyLayerPort and refPppLink are mutually
exclusive. One of them must be configured.

It is the IP address of the base station.

Configure this parameter if FE transmission is
used.
A base station can be configured with several
ipAddr IP Address IPs, which are used for operation &
maintenance and services of different modes.
The IP address of the 127 subnet, the 192.254
subnet, and the 200 subnet cannot be
configured.
Subnet Mask. Only IPv4 address can be
networkMask Network mask
configured.
Gateway.
When FE transmission is used, it should be
gatewayIp Gateway IP
configured. It is usually the port address of the
exchange connected with SDR.

Configuration of prefix length. Only IPv6

prefixLength Prefix Length
address can be configured.

It is necessary to configure this item if the

UMTS mode is used. It is the information of the
ipField IP Domain domain which IP address belongs to. “255”
indicates that it does not belong to any domain.
Set it to “255” for GSM.

If the attribute is filled in, the system will create

the corresponding "ServiceMap" record, and
there is no need to fill the "ServiceMap" sheet,
except LTE.
radioMode Radio Standard
multimode format, e.g., 1;2
1:UMTS,
2:GSM,
4:TD-SCDMA

74 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.1.4.6 StaticRoute

This sheet is used to configure static route. Normally, this sheet does not need to be
configured. Just set the gateway in the IpLayerConfig sheet.

3.1.4.7 BandwidthResource

This sheet is used to configure bandwidth resource group and bandwidth resource. It is
required to fill in this sheet when LTE is used.

It is not necessary to configure this sheet in GSM single mode, UMTS single mode, or GU
dual-mode.

Refer to the following table for the key parameters.

Table 3-21 BandwidthResource Sheet

Item Parameter Name Value Description

Specify the bandwidth resource group
Bandwidth resource number, which must be unique in the
groupNo
group number same bearer mode. In the Ethernet
bearer mode, the value range is 0-7.

Specify bandwidth resource number.

Bandwidth resource
resourceNoList format: resourceNo;resourceNo;…
number
e.g.,1;2

It is used to configure transmission

bandwidth weight.
Transmission It is an array. The array length is
weightList
bandwidth weight consistent with resourceNoList. Format:
weight;weight;…
e.g., 0;1

Indicates on which Ethernet link the

bandwidth allocation rule is applied. It is
Used Physical Layer mutually exclusive with refPppLink.
refPhyLayerPort
Port The value of this parameter is from the
value of the phyLayerPortNo field in the
PhyLayerPort sheet.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 75
 G_ZXSDR (V4.14) Quick Data Configuration Guide

Maximum bandwidth of Indicates the maximum available

egressMBR
egress (Mbps) bandwidth of egress.

3.1.4.8 Sctp

This sheet is about SCTP related configuration, including mainly Local Port Number,
Used IP Layer Configuration, Remote Port Number, Remote Address, Number of
In-and-out Streams, DSCP, Used Bandwidth Resource, and Radio Standard.

Refer to the following table for the key parameters.

Table 3-22 Sctp Sheet

Item Parameter Name Value Description

SCTP link number. It can be customized by
sctpNo SCTP Link No.
users within the value range.
Local port Local port number of SCTP link. It is the
localPort
number integration parameter.
Configuration of IP layer that bears SCTP.
Used IP Layer Format:ipNo;ipNo, e.g.,1;2 (separate multiple
refIpLayerConfig
Configuration IP layers with “;”)
The value is "ipNo" of IpLayerConfig sheet.
Remote Port Remote port number of SCTP link. It is the
remotePort
Number integration parameter.
Remote IP address of SCTP link. It is the
integration parameter.
Separate multiple addresses with “;”, for
example, 10.0.0.1;20.0.0.1.
It can be IPv4 address or IPv6 address. The
remoteAddr Remote Address
IPv4 address format is decimal notation
separated by dots, e.g., 10.0.0.1.IPv6
address is hexadecimal notation separated
by colon, e.g.,
2011:0db8:85a3:0000:1319:8a2e:0370:7366.

76 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

multimode format, e.g., 4;32

1:UMTS,
2:GSM,
4:TD-SCDMA,
8:CDMA,
16:LTE FDD,
32:TD-LTE
radioMode Radio Standard If there are two or more modes, separate
them with English character “;”, for example,
4;32
In the LTE FDD mode and the LTE TDD
mode, the records of S1AP and X2AP will be
created according to the value of SCTP. It is
consistent with the configuration created
through the GUI configuration module.

Number of incoming and outgoing streams of

Number of SCTP association. A maximum of six
inOutStreamNum in-and-out incoming and outgoing streams can be
Streams configured.
Default: 2.

IP service model configuration. .Select

different models according to different
dscp DSCP
scenarios.
Default: 46.

Configure the bandwidth resource used for

SCTP.
refBandwidthRes Used Bandwidth
Format: groupNo,resourceNo, The value is
ource Resource
from the corresponding field in the
BandwidthResource sheet.

3.1.4.9 OmcChnnel

This sheet is about OMC channel related configuration.

Refer to the following table for the key parameters.

Table 3-23 OmcChnnel Sheet

Item Parameter Name Value Description

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 77
G_ZXSDR (V4.14) Quick Data Configuration Guide

OMC Interface Link

omcChannelNo [1..65535]
number

This sheet is hidden by default. It needs to

be configured only in the dual-CC
load-sharing scenario. Because the two
CCs are independent and are connected
with transmission equipment respectively,
and two O&M channels exist
simultaneously, create two records in the
Object ID of “PhyLayerPort” sheet, corresponding to
TransportNetwork the two CCs respectively, for example,
transmission
Id
network If “Object ID of transmission network” is
set to 1, the transmission is used for
“Running mode1.”
If “Object ID of transmission network” is
set to 2, the transmission is used for
“Running mode2.”
Running mode1 and Running mode2 are
configured in the ManagedElement sheet.

0:IPINIP,
1:IPOA,
2: Independent Networking
Type of Operation
omcChannelType and Maintenance Select IPINIP for GU, i.e. SDR is

Interface connected to OMC server through

BSC/RNC. Select independent networking
if LTE is used, i.e., SDR is directly
connected with OMC server.

Used IP Layer The value is "ipNo" of IpLayerConfig

refIpLayerConfig
Configuration sheet.

The inner IP address of base station

Base station inner configured in the IPINIP mode. It is used
innerIp
IP for OMC and it is an integration parameter
(integrated with OMC).

78 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

It is the virtual address on the RPU at the

RNC side. For the UMTS mode, it is
usually set to 10.9.X.63.For GSM BSC V3,
this parameter corresponds to the OMCB
gatewayIp OMC Gateway IP channel IP at the BSC side; for GSM BSC
V4, this parameter corresponds to the Abis
loopback address at the BSC side (at the
BSC side, this interface is named is
OMCAgent.)

The internal IP of OMCB. For the UMTS

mode, it is the IP address of eth6:2.For the
GSM mode, it is the IP address of eth4:1.
omcServerIp OMC Server IP For either GSM mode or UMTS mode, this
parameter can be left unconfigured. This
parameter must be configured if LTE
networking is used.

OMC Network It is the subnet mask of the internal IP of

omcNetworkMask
Mask OMMB server.

The value is from the value of

refBandwidthRes Used Bandwidth
"ResourceNo" in the “BandwidthResource”
ource Resource
sheet.

Dscp DSCP [0..63]

3.1.4.10 ServiceMap

This sheet is about service and DSCP mapping related configuration. Configure it in the
way that one radio mode occupies one row, and one row can be configured with the
DSCP value of only one radio mode. Do not use one row for multiple radio modes.

Refer to the following table for the key parameters.

Table 3-24 ServiceMap Sheet

Item Parameter Name Value Description

Used IP Layer The value comes from the value of “ipNo” in
refIpLayerConfig
Configuration the “IpLayerConfig” sheet.

refBandwidthRe Used IP Layer The value is from the value of "ResourceNo"

source Configuration in the “BandwidthResource” sheet.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 79
 G_ZXSDR (V4.14) Quick Data Configuration Guide

The value is the same as the value of

refOperator Operator Name
“operatorName” in the “Operator” sheet.

gsmServiceDsc GSM service DSCP

Default: 36;2
pMap mapping

umtsServiceDsc UMTS service

Default: 46;36;36;36;20;0;38;38;22;0
pMap DSCP mapping

3.2 GSM Wireless Plan Template Filling

Specifications

Compared with OMMBV12.12 and OMMBV12.13, the Choose sheet is added in the GSM
Wireless Plan Template of OMMBV12.14, and the parameters of some seldom-used
scenes are hidden. Therefore, the template of OMMBV12.14 is simpler and easier to fill
in.

There are three sheets in the GSM Wireless Plan template, as detailed in the following
table.

Table 3-25 Description of Sheets in GSM Wireless Plan Template

No. Sheet Name Description

This item is newly added in OMMBV12.14. It is
used to configure GSM ID and GSM station ID
1 BtsFunction
respectively (they cannot be configured separately
in previous versions, so they are set the same).

Fill in the resource using status of the PAs on the

RU, including Carrier Number, Carrier Power, GSM
2 RU(GSM)
Cell Channel Resource No., and Multi-carrier
Combination Group No.

Fill in the TRX information allocated to each GSM

3 GSM Carrier
cell.

3.2.1 GSM Wireless Template Customizing

Currently, there are three scenes available in the Choose sheet of the GSM_RADIO
template, i.e., Muli-carrier Combination, More Cells in one PA, and Combined Cabinet.

80 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

Figure 3-2 GSM Wireless Template Customizing

By default, no special scene is selected, i.e., the scene related parameters are hidden.
After a configuration scene is selected, the parameters of the scene will be displayed in
the related sheets.

Note:

For the Plan template exported from OMMB, no option is selected in the Choose sheet.
Therefore, the data to be modified cannot be found. In this case, select the scene (or radio
mode or transmission type) of the parameters in the Choose sheet, and then modify the data.

After the sheet is hidden, the parameter itself will not change.

3.2.2 BtsFunction

Table 3-26 BtsFunction Sheet

Item Parameter Name Value Description

It is recommended that this parameter be
BtsFunction GSM ID
planned the same as ME ID.

This parameter must be set the same as the

SITEID of the base stations at the OMCR
side. Otherwise, OMMR alarms and OMMB
siteId GSM station ID alarms of the base stations on EMS cannot be
matched.
It is recommended that this parameter be
planned the same as ME ID.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 81
 G_ZXSDR (V4.14) Quick Data Configuration Guide

3.2.3 RU(GSM)

Fill in RU properties in GSM network in the RU(GSM) sheet, including Carrier Number,
Carrier Power, GSM Cell Channel Resource No., Multi-carrier Combination Group No.,
Rx Mode, and Tx Mode. The PA of each RU occupies one row. For the RUs with two PA

units (RSU82 and R8882), fill in two rows at most.

Table 3-27 RU(GSM) Sheet

Item Parameter Name Value Description

GSM Cell Channel Each PA corresponds to a No., which
gCellEquipmentFuncNo
Resource No. is unique.

Select the Tx port (i.e., PA) of an

RU.NOTE: The Tx ports of R8882 are
TxDevice Tx Device
ports 1 and 4 (this is different from
that in OMCBV4.11).

Multi-carrier
This parameter is hidden by default.
multiCarrierGroupNo Combination
Default value: 0.
Group No.

GSM Cell Channel This parameter is hidden by default.

channelGroupNo
Group No. Default value: 0.

This parameter is used to configure

carrierPower Carrier Power the Tx power of each carrier, which
should be accurate to 1W.

For GU RUs of DTR, ADTR, RSU 82,

powerLevel Static power level
and R8882, the value range is 0-6.

0:Normal mode: Each PA transmit

different carriers independently.
1:DPCT: Two PAs transmit the same
carrier, which is applicable only to
RU02.
txMode Tx Mode 2:DDT: Two PAs transmit the same
carrier, but not at the same time
(there is DDT delay between the two
carriers).
3:Antenna hopping: Two antennas
transmit different carriers in turn.

82 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

0:2-antenna diversity reception:

Corresponding to normal
transmission mode
rxMode Rx Mode
1:4-antenna diversity reception:
Corresponding to DPCT, DDT, and
antenna hopping

ddtOffset DDT Delay DDT Delay

Whether to use primary and

secondary reception simultaneously
or use one of them depends on the
Primary-secondary
actual antenna connection in the
rxConfig antenna receiving
field. When the Tx Mode is normal
setting
mode and the Rx Mode is 2-antenna
diversity reception, this parameter
needs to be configured.

Combined cabinet connected

RxChannel port(Only used for R8863
Combined cabinet combined cabinet)
refRxChannel
receiving port e.g., (51,1,1):1;(52,1,1):3 means PA1
of RRU51 is combined with PA3 of
RRU52.

CELL_ID_1 First GSM Cell No. The GSM cell No. of the carriers.

When GPS clock is configured, this

GPS Synchronized parameter should be configured.
gpsOffset_1
Frame Head Offset Otherwise, it is not necessary to
configure this parameter.

Number of Used The total number of carriers in CELLx

carrierNum_1
Carriers on the PA.

It is the End ID of High-speed

Railway Cell. In the scenario of high
End ID of speed railways configured with
hsrCellOutInletFlag_1 High-speed mutli-carrier combination group, it is
Railway Cell used to identify whether a PA is the
PA at the very edge of the cell. This
parameter can be left unconfigured.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 83
 G_ZXSDR (V4.14) Quick Data Configuration Guide

It defines whether a PA is the BCCH

preferred PA when there are two or
more PAs in a cell.
Is BCCH Preferred
ISBCCH_1 Default: No
Channel
When MCUM is used,
bcchCarrierNo_x cannot be
configured.

It defines the carrier preferred by

BCCH when there are two or more
carriers on the PA.
BCCH preferential
bcchCarrierNo_1 Default: No
Carrier No.
When MCUM is used,
bcchCarrierNo_x cannot be
configured.

3.2.4 GSM Carrier

Fill in carrier related information in the GSM Carrier sheet, including trxNo,
operatingMode, mainBand, etc.

When single-channel is used, the corresponding multiCarrierGroupNo of RRU should be

“0” (no grouping). When dual-channel or multi-channel is configured,
multiCarrierGroupNo should not be “0,” i.e., they must be grouped.

The total number of carriers in the same frequency band or sub-frequency band of the
same cell cannot be greater than the total number of carriers of the frequency band or
sub-frequency band, which are provided by the channel used by the cell.

Refer to the following table for detailed description of parameters.

Table 3-28 GSM Carrier Sheet

Item Parameter Name Value Description

SubNetwork SubNetwork ID It is the SubNetwork ID

MEID ManagedElement ID NE ID

The Cell No. should be corresponding to

cellNo Cell No.
the e Cell No. at OMCR side.

84 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

 G_ZXSDR (V4.14) Quick Data Configuration Guide

The Logic Carrier Frequency No. should

Logic Carrier
trxNo be corresponding to the TRX No. at
Frequency No.
OMCR side.

Select single carrier (0) in general cases.

Select dual-carrier when DDT and DPCT
operatingMode Operating Mode
are used.
Select multi-carrier when MCUM is used.
Multi-carrier It defines the Multi-carrier Combination
multiCarrierGroup
Combination Group Group No. The value should be set as “0”
No
No. in the single carrier mode.

Parent Frequency It defines the Tx frequency band

mainBand
Band supported by the PA.
It defines the value of sub-frequency
band, which is usually set as “255.”The
sub-frequency band configured here can
branchBand Sub frequency band only use the PA carrier of the same
sub-frequency.PA sub-frequency is
configured in the PA sheet. Refer to
related Technical Notice for details.

It defines whether to enable the

"ZGO-04-01-005 Uplink Interference
Rejection Combining (IRC)" feature,
which can improve the uplink receiving
enableIRC Use IRC
signal quality. Default: 1.
STIRC is the enhanced IRC, which is not
stable currently. So it is not
recommended to select STIRC.

This parameter should be configured in

the ultra-wide coverage scenario. Two
timeslots are combined into one (in this
case, each TRX has 4 timeslots instead
of 4 timeslots), so as to improve TA to
Extend carrier
isExtendTrx increase the coverage distance of the
frequency
site.
isExtendTrx and RfExtend (in the
“RfExtendCable” sheet) are two different
concepts which are not related to each
other in any way. Do not mix them up.

ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 85
G_ZXSDR (V4.14) Quick Data Configuration Guide

It defines whether CIR or RxLev is used

Is uplink signal
as the basis to select the RRU to receive
mcumRxSelMode selected according to
uplink/downlink signals, when MCUM is
CIR
used. Default: 0, i.e., RxLev

It defines whether to use some RUs or all

Select RU
mcumTxSelMode RUs to transmit signals, when MCUM is
transmission
used. Default: 0, i.e., select all RUs.

86 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.