U - ZXSDR (V4.14) Quick Data Configuration Guide

U_ZXSDR (V4.
14) Quick Data

Configuration Guide
U_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
Revision History
Product Version Document Version Serial Number Reason for Revision

ZXSDR V12.14.10 R1.0 First published
Intended audience: Base station commissioning engineers
II ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

About This Document
Summary
Chapter Description
1 Plan Templates Provides the introduction to the plan templates and the path.
2 Plan Template Filling Introduces the sheets of the plan template and the
Specifications instructions of filling in the fields.
3 Data Import and Export Provides a brief introduction to the plan template import and
Functions export functions.
4 Explanation of Common Provides the description of common operations.
Operations
5 Examples of Data Configuration Provides some examples of data configuration.
AppA Iub-interface E1 Introduces the method of using the Iub-interface E1
Transmission Bandwidth transmission tool.
Configuration Tool
AppB Slot Configuration Tool Introduces how to use the slot configuration tool
ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. III
TABLE OF CONTENTS
1 Plan Templates ................................................................................................. 1

1.1 Introduction to Plan Templates .......................................................................... 1
1.2 Template Acquisition Path ................................................................................. 2
1.3 Description of Template Format ......................................................................... 2
2 Plan Template Filling Specifications .............................................................. 4

2.1 Ground Plan Template Filling Specifications...................................................... 4
2.1.1 Basic Parameters ............................................................................................... 7
2.1.2 Equipment Parameters ...................................................................................... 9
2.1.3 Transmission Parameters ................................................................................ 28
2.2 UMTS Wireless Plan Template Filling Specifications....................................... 35
2.2.1 UMTS Radio ..................................................................................................... 36
2.2.2 UMTS Sector .................................................................................................... 37
2.2.3 UMTS Local Cell .............................................................................................. 38
2.2.4 ULocalCellRelation ........................................................................................... 41
2.2.5 UBasebandPool ............................................................................................... 41
2.2.6 QcellTxResGroup ............................................................................................. 42
2.2.7 QcellRxResGroup ............................................................................................ 42
3 Data Import and Export Functions ............................................................... 43

3.1 Notices in Operation ......................................................................................... 43
3.2 Planning Data Import ....................................................................................... 43
3.3 Planning Data Export ....................................................................................... 45
4 Explanation of Common Operations ............................................................ 48

4.1 Examples of Configuration Scenario ................................................................ 48
4.1.1 Adding Boards and Modifying Board Type ....................................................... 48
4.1.2 E1 Capacity Expansion/Reduction ................................................................... 51
4.1.3 Batch Configuration Data Modification ............................................................. 53
4.1.4 Snapshot Area Data Recovery ......................................................................... 55
4.2 Acquisition of LMT Configuration File .............................................................. 56
5 Examples of Data Configuration ................................................................... 58
AppA Iub-interface E1 Transmission Bandwidth Configuration Tool ................. 59
AppB Slot Configuration Tool ................................................................................. 60
IV ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

FIGURES
Figure 1-1 Generate Template ............................................................................................... 1

Figure 1-2 Template Storage Path ......................................................................................... 2
Figure 3-1 Planning Data Import .......................................................................................... 44
Figure 3-2 Set the Path of Plan Templates .......................................................................... 44
Figure 3-3 View Log File ...................................................................................................... 45
Figure 3-4 Planning Data Emport ........................................................................................ 45
Figure 3-5 Planning Data Export Window ............................................................................ 46
Figure 3-6 Data Type ........................................................................................................... 46
Figure 3-7 File Path ............................................................................................................. 47
Figure 4-1 Add BPC Board .................................................................................................. 48
Figure 4-2 Import Data to OMC ........................................................................................... 49
Figure 4-3 Data Synchronization ......................................................................................... 49
Figure 4-4 Synchronize Modified Data ................................................................................. 50
Figure 4-5 Planning Data Export .......................................................................................... 51
Figure 4-6 Export PLAT Data ............................................................................................... 52
Figure 4-7 Modification to the Transmission Sheet .............................................................. 52
Figure 4-8 Modification to Parameters in the “PhyLayerport” Sheet .................................... 53
Figure 4-9 Batch Configuration Data Modification ............................................................... 54
Figure 4-10 Select a Site ..................................................................................................... 54
Figure 4-11 Batch Modification ............................................................................................ 55
Figure 4-12 Batch NE’s Operation ....................................................................................... 55
Figure 4-13 Copy Snapshot Area Data to Modify Area ........................................................ 56
Figure 4-14 Data Synchronization ....................................................................................... 57
Figure 4-15 Generate Synchronization File ......................................................................... 57
TABLES
Table 2-1 Instructions on Filling in Sheets in Ground Plan Template .................................... 4

Table 2-2 ManagedElement Sheet ........................................................................................ 7
Table 2-3 IpClock Sheet ...................................................................................................... 10
Table 2-4 Clock Sheet ......................................................................................................... 12
ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. V
Table 2-5 RU Sheet ............................................................................................................. 14

Table 2-6 PA Sheet .............................................................................................................. 17
Table 2-7 FCE Sheet ........................................................................................................... 20
Table 2-8 AISG Sheet .......................................................................................................... 21
Table 2-9 PowerOutlet Sheet ............................................................................................... 23
Table 2-10 Epm Sheet ......................................................................................................... 25
Table 2-11 FiberCable Sheet ............................................................................................... 26
Table 2-12 RfCable Sheet ................................................................................................... 27
Table 2-13 Transmission ..................................................................................................... 28
Table 2-14 PhyLayerPort Sheet ........................................................................................... 29
Table 2-15 HDLC Sheet ....................................................................................................... 30
Table 2-16 PPP Sheet ......................................................................................................... 30
Table 2-17 IpLayerConfig Sheet .......................................................................................... 31
Table 2-18 Sctp Sheet ......................................................................................................... 33
Table 2-19 ItfUniBts Sheet ................................................................................................... 34
Table 2-20 ServiceMap Sheet ............................................................................................. 35
Table 2-21 Description of Sheets in UMTS Wireless Plan Template ................................... 36
Table 2-22 UMTS Radio Sheet ............................................................................................ 36
Table 2-23 UMTS Sector Sheet ........................................................................................... 37
Table 2-24 UMTSLocal Cell Sheet ...................................................................................... 38
Table 2-25 ULocalCellRelation Sheet .................................................................................. 41
Table 2-26 UBasebandPool ................................................................................................. 41
VI ©2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

1 Plan Templates
1.1 Introduction to Plan Templates
The Plan Template consists of the Ground Plan template and Wireless Plan template.
Different modes of products share the same Ground Plan template, but each mode has a
different Wireless Plan template. Therefore, for multi-mode sites, it is necessary to fill in a
Ground Plan template and several Wireless Plan templates.
Since the Ground Plan template supports multiple scenarios and network modes, it
consists of many sheets, which are complicated to fill in. Starting from V12.12.40P55, we
can select the template according to the mode, transmission, and scenario. When the
template is acquired, first open the Choose sheet, select the network mode, transmission
type, and special scene based on the field requirement, and click the Generate
Template button. The unwanted irrelevant sheets will be automatically hidden, which
makes the template look simple and convenient for fill-in.
 Tip:
The special scene related sheets are hidden by default, i.e., the related sheets are hidden if
they are not selected. Therefore, when making data for a new site, first select the radio
standard, transmission type, and special scene in the “Choose” sheet to generate the template.
Otherwise, the data filled in may be incomplete because some sheets are hidden.
Figure 1-1 Generate Template
ZTE Confidential & Proprietary. © 2015 ZTE CORPORATION. All rights reserved. 1
1.2 Template Acquisition Path
1. The Ground Plan templates are all stored under the

ums\ums-svr\sdrmanager\sdrmanager-osf\sdrmanager-osf-dataimpexp.par\conf
directory, as shown in the table 1-2. These templates can be divided into two types,
UR12 templates and UR13 templates.
The wireless templates of V12.14 are under the corresponding directory of the
template directory, e.g., ums-svr/template/V1410/plan_describer.
Figure 1-2 Template Storage Path
2. The Ground Plan Templates and Wireless Plan Templates of the existing sites can
also be exported from the OMMB of the same version. Refer to Chapter 3.3 for
details.
1.3 Description of Template Format
1. Conventions of Table Header
The first row is the database name. Do not modify this row. Otherwise, the data in
the Plan Template will fail to be imported.
The second row is the field name displayed on OMM.
The third row gives the description about the value range of a field.
The fourth row is the specifications, restrictions, and examples of the field data
configuration.
2 © 2015ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

The fifth row provides the attributes of a field: whether the field is Primary Key,
whether it can be modified (W), and whether it is required to be filled in (I).
The configuration data of each site starts from the sixth row.
2. Conventions of Sheet Arrangement
The first sheet is the “Choose” sheet, in which the templates can be selected
according to the mode, transmission, and scenario.
The second sheet is the “TemplateInfo” sheet. It contains the description of the
template imported and cannot be modified.
The third sheet is the “Index” sheet. It provides the functions of different sheets.
The sheets starting from the fourth sheet contain the data to be imported. The
names and order of the sheets cannot be changed.
3. Description of Operators
A (ADD): Add a new record.
M (MODIFY): Modify the record.
D (DELETE): Delete the record.
P (PASS): Do not perform any operation to the record of this row.
2 Plan Template Filling Specifications

This Guide is based on the Plan Template released with V12.14.50. The Plan Template
of different versions may be a little different in the parameters, but the filling method is
almost the same.
2.1 Ground Plan Template Filling Specifications
The Ground Plan template has 39 sheets. Some of the sheets do not need to be filled in
some scenarios. This Guide introduces the UMTS related sheets. The specifications of
filling in the sheets are detailed in the following sections.
Table 2-1 Instructions on Filling in Sheets in Ground Plan Template
No. Sheet Name Description

“Managed Element” sheet: The NE here refers to
SDR base station. It involves subnetwork and NE. NE
Managed Network
1 parameters: NE Name, ManagedElement ID, NE
Element
Type, External IP, NE Version, Longitude, and
Latitude.
This sheet is used only to configure the data of the

slave cabinet, because the primary cabinet has been
2 Cabinet
created with the creation of NE. When FCE is created,
the auxiliary cabinet is created together.
This sheet provides the configuration information of

3 Equipment
the board on the main rack of BBU.
This sheet is about the 1588 clock configuration. If

4 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
5 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,

6 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
7 Fiber Device is 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
8 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.
It is the fan control and environment monitoring board.

The FCEs of the primary cabinet, auxiliary cabinet,
and slave cabinet are all configured in this sheet. For
9 FCE
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.

10 DryContact
Currently, there is dry contact on SA, SE, and FCE.
11 TMA TMA equipment related parameters
This sheet is about AISG device configuration. It is an

12 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,

13 PowerOutlet
power output exists on the TAM board and RU.
Embedded power supply equipment is a device

14 EPm
connected externally.
Fiber resource. It is about the connection between

15 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
16 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

17 RfExtendCable
is about the connection between RU ports.
Overall transmission parameters. The parameters in

this sheet include Transmission Type, ATM Address,
18 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

19 PhyLayerPort protocol. Physical layer bearer includes E1, T1, and
Ethernet.
HDLC protocol related parameters include HDLC link

20 Hdlc No., E1T1 link No., HDLC timeslot, TSI, etc. This
sheet applies only to GU.
This is the sheet of PPP protocol-related parameters.

21 Ppp
This sheet applies only to GU.
IP Layer
22 IP layer parameters configuration.
Configuration
23 Static Route Static route parameters configuration.
24 BandwidthResource This sheet contains bandwidth resource parameters.
This sheet is about SCTP parameters configuration.

SCTP protocol provides a stable and continuous data
25 SCTP
transfer service between two points. It is used to
transmit signaling in the IP network.
26 OmcChannel OMC channel parameters
This sheet is used to configure the mapping between

27 ServiceMap
service and DSCP.
The sheets of Ground Plan template can be divided into three types, sheets of basic
parameters, sheets of equipment parameters, and sheets of transmission parameters.
The instructions of filling in the data of the functional modules are described in the
following sections.

2.1.1 Basic Parameters
2.1.1.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 2-2 ManagedElement Sheet
Parameter
Item Value Description Instructions
Name
1:UMTS{UMTS}, The property of this
2:GSM{GSM}, parameter is “W,” which

means this parameter can be
4:TD-SCDMA{TD-SCD
modified, but there is a
MA},
restriction on the
8:CDMA{CDMA},
modification, i.e., this
16:LTE FDD{LTE FDD}, parameter can only be
RADIOMO
Radio Mode 32:TD-LTE{LTE TDD}
DE modified when the radio
For multi-mode versions, mode is expanded, e. g., from
it is necessary to type in GU to GUL, but not from GUL
several figures, which to GU or from G to U.
should be separated by This parameter should be
English character “;”, for modified together with the
example, 4;32 SWVERSION parameter.
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.
SWVERSI L_V3.10.01NE Version, This parameter should be
NE version
ON e.g., L_V3.10.01 modified together with the
RADIOMODE parameter.
For the configuration
specifications, refer to the
chapter of NE Capacity in the
ZXSDR OMMB
V12.12.40P55 Version
Release Notes in the OMMB
version package.
This parameter must be
The home configured correct.
RNCID UMTS RNC 0-65535 Otherwise, the report of
No. northbound data will be
affected.
It must be configured.
Format: operator name
Operator and
operator #mcc#mnc&mcc#mnc
PLMN
For example: China
Telecom#460#01
0: commissioning For the newly-constructed

site, configure it to 0: Normal.
2: testing
MAINTAIN Maintenance Otherwise, after the
3: configuring
STATUS status transmission is set up,
5: FM testing
OMMB cannot set up the link
6: PM testing successfully.

2.1.2 Equipment Parameters
2.1.2.1 Cabinet
This sheet is used to configure the data of the slave cabinet. Each slave cabinet occupies
one row.
The primary cabinet and the auxiliary cabinet are not configured in this sheet, because
the primary cabinet has been created with the creation of NE. Currently, the auxiliary
cabinet is used to place the FCE board. When FCE is created, the auxiliary cabinet is
created together.
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.
2.1.2.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.
IMPORTANT:
It is required to fill in three types of information for each slot, i.e., board type, radio mode,
and function mode, which should be separated with English character “;”. Refer to the filling
instructions and examples in the “Equipment" sheet for the detailed format.
2.1.2.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.
Table 2-3 IpClock Sheet
Item Parameter Name Value Description

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

linkPriority Link Priority
Link priority of IP clock
1:IPV4,
PTP Network
networkProtocol 2:IPV6,
Protocol
3: Ethernet
Transmission mode of 1588 clock packets:

IP Clock 0: Multicast
transType Transmission 1: Unicast
Mode 2: Hybridcast
It can be left blank.
IP Address of
This item must be configured for IP 1588
1588
syncServerAddr clock reference source. This attribute is valid
Synchronization
only when Ethernet transmission is used.
Server

It is the IP link used to configure UDP link.

The planning data import process
automatically creates the UDP link of 1588
clock according to the IP link.
The value of this parameter is from the “ipNo”
Used IP Layer
field in the “IpLayerConfig” sheet. Therefore, it
refIpLayerConfig Configuration by
is required that the “ipNo” field has been
1588 IPClock
configured.
The Ethernet bearer link and the UDP link are
mutually exclusive.This parameter is mutual
exclusive with the refEthernetLink field. It is
only necessary to fill in one of them.
The value of this parameter is from the
“ethernetLinkNo” field in the “EthernetLink”
sheet. Therefore, it is required that the
Used Ethernet “ethernetLinkNo” field has been configured.
refEthernetLink
Link No. The Ethernet link and the UDP link are
mutually exclusive.This parameter is mutually
exclusive with the refIpLayerConfig field. Just
one of them is required to be filled in.
The value of the parameter is from one of the

values of the “vlanMembership” field in the
“EthernetLink” sheet.
vid VLAN ID
The value of this parameter should be the
same as the value of a VLAN in the Ethernet
link.
2.1.2.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.
Table 2-4 Clock Sheet

This parameter is used to synchronize
Clock
base station and clock reference source.
clockSyncMode Synchronization
0: Frequency synchronization
Mode
1: Phase synchronization
1: Inner GNSS
2: Outer facepanel GNSS
3: Outer backpanel GNSS
17: RRU inner GNSS
4:1PPS+TOD{1PPS+TOD},
Clock Reference 5: GNSS cascade clock
clockType Source Type of Clock 14: 1PPS+TOD backup
Device 6: BITS-2MHz clock
7: BITS-2Mbps clock
8: Line clock-local board
13: SyncE clock
10: SyncE+1588 clock
11:1588{1588}
Value range: 1 – 8.
Clock Priority of
This parameter indicates the priority of
clockPriority Clock Reference
clock reference resource.1 refers to the
Source Type
top priority.
1:USR1_A{USR1_A},
2: Outer compass receiver
3:RGPS{RGPS},
4:UCI_RGPS{UCI_RGPS},
5:UCI_COMPASS{UCI_COMPASS}
receiverHardware GNSS Receiver If built-in GNSS is used, this parameter is
Type Hardware Type 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
This parameter is used to configure the

operating mode of GNSS receiver.
"Survey In" is recommended but "Fixed
Mode" is not recommended.
receiverOperating Receiver Operating 1: Survey In
Mode 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
minStarNum Number of Search satellites for satellite timing. It is also the
Stars parameter of 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.”
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
isSSM Enable SSM level for sending timing signals through

the timing synchronization link in 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.
2.1.2.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.
Table 2-5 RU Sheet

Format: RackNo
RU Board, incl. The value ranges are:
RUDevice
RRU and RSU RackNo: RRU:51..201, RSU:2..50
e.g,:51
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,
1280:LTE-FDD Single Mode,
functionMode Function 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
It can be left blank.
This parameter indicates the attributes of RU
optical port device set. It is an optional parameter
and should be configured according to the actual
connectMode Uplink Connection requirements.
WithUpRack Mode
0:single up-link optical line,
1:double master&slave optical lines,
2:multiple load-sharing optical lines
This parameter is used to configure the attributes of

RU RF port device set. It is an optional parameter
and should be configured according to the actual
requirements.
0: Normal diversity reception
Diversity 1: Cross diversity reception
diversityMode
Reception Mode It is used to configure the diversity reception mode
of RU. Cross diversity reception means the signals
of the two reception channels are the main/diversity
reception for each other (dual-PA RU is needed and
only two RX/TX antennas are connected).
Default: 0.
long:[0..8000] step:1 unit: m

It indicates the length of the feeder from RRU
GNSS antenna to the receiver. This feeder is used
rruGnssCable RRU GNSS Cable to improve the clock precision. This attribute should
Length Length be filled in according to the on-site survey result. It
is an optional parameter.
It needs to be configured when RRU is R8964T
S2600 and the clock type is RRU inner GNSS.
2.1.2.6 FiberDevice
This sheet is used to configure optical port related information. The filling of this sheet is
optional.
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.

2.1.2.7 PA
This sheet is used to configure the PA related information of RU devices. The filling of
this sheet is optional.
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
Table 2-6 PA Sheet

Format: RackNo, ShelfNo, SlotNo,
The value ranges are:
RackNo: RRU:51..201, RSU:2..50
RUDevice RU Board of PA
ShelfNo: 1
SlotNo: 1
e.g., :51,1,1
Port No. on the RU
port long
device of PA
It is the frequency band ID of the port on the

Frequency Band ID of
suppBand RU device of PA. It is used together with the
PA
RU Device and port to define one PA.
Note: For multi-mode configuration, the
values need to be separated by English
character “;”, e.g., 4;32
0:ALL{ALL},
1:UMTS{UMTS},
radioMode Radio mode of PA
2:GSM{GSM},
8:CDMA{CDMA},
32:TD-LTE{LTE TDD}
The allocation method of PA resources in

Dual-mode Working dual-mode, for example, 2G+2U indicates
dualMode
Mode of PA the PA supports two GSM carriers and two
UMTS cells.
1,2,3,255: Invalid
The sub-frequency band supported by PA.
Sub-frequency is the special attribute owned
by GSM. Only the RU of 900M and 1800M
use sub-frequency.
900M (BandVIII) sub-frequency consists of:
1: Work band: UL 890MHz~915MHz, DL
935MHz~960MHz;
branchBand Sub-frequency Band
925MHz~950MHz;
935MHz~951MHz;
1800M(BandIII) sub-frequency consists of:
900M (BandVIII) sub-frequency consists of:
1: Work band: UL 880MHz~1,765MHz, DL
925MHz~1,860MHz;
2: Work band: UL 880MHz~1,785MHz, DL
925MHz~1,880MHz;
This parameter is not related to PA. It is the

central transmission frequency point of Tx
Channel.
The configuration of txCenterFreq is
increased by 10 M on the basis of 3GPP
Tx Central Frequency protocol.
txCenterFreq
Point The value range should be selected
according to the frequency band of the
equipment. Every frequency band can be
set as “0”Modification to this parameter
requires prudence.“0” indicates automatic
calculation by SDR.

This parameter is not related to PA. It is the

central transmission frequency point of Rx
Channel.
The configuration of txCenterFreq is
increased by 10 M on the basis of 3GPP
Rx Central Frequency protocol.
rxCenterFreq
Point The value range should be selected
according to the frequency band of the
equipment. Every frequency band can be
set to “0”Modification to this parameter
requires prudence. “0” indicates automatic
calculation by SDR.
2.1.2.8 FCE
This sheet is used to configure the FCE board (fan control and environment control).
One FCE board occupies one row.
The FCEs of the primary cabinet, auxiliary cabinet, and slave cabinet are all configured in
this sheet.
Before configuring the FCE of the slave cabinet, make sure the slave cabinet has been
configured in the “Cabinet” sheet.
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.
2.1.2.9 DryContact
This sheet is about dry contact configuration. The filling of this sheet is optional.
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.
Table 2-7 FCE Sheet

Dry contact needs to be configured on the
slot, shelf, and rack of the SA, SE, FCE, and
DryContact
Dry Contact Info RU 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
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


contents of dry contact alarms. This
parameter is valid only when the dry contact
Dry Contact
almNo type is output dry contact. The user can either
Alarm Name
define the contents of the dry contact or
choose the dry contact alarm preconfigured in
the system.
2.1.2.10 Tma
This sheet is used to configure TMA equipment. The filling of this sheet is optional. One
TMA occupies one row.
The configuration in this sheet is used to configure TMA gain and other related
parameters.
2.1.2.11 AISG
This sheet is used to configure the PA related information for the AISG devices. The
filling of this sheet is optional. One AISG device occupies one row.
The configuration of this sheet is used to configure AISG devices. It is used for RET to
control down tilt and for TMA to amplify signals.
It is necessary to configure RfCable. Only when RF connection is configured can AISG

devices work normally.
Table 2-8 AISG Sheet
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
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.

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 be
Connected
antNo configured in advance.
Antenna
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”
tmaNo
Device should have been configured.
2.1.2.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.
Table 2-9 PowerOutlet Sheet
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
0: Close
1: AISG RS485{AISG RS485},
2: NSBT RS485{NSBT RS485}
switchStatus Switch Status If the TAM board is configured, set this
parameter as “0.”If RU is configured, set this
parameter to “1” or “2” according to the
actual situation.
0:140{140},
1:220{220},
voltage Voltage
4294967295: Invalid
The voltage of AISG and NSBT.
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 (Ma) {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.

Value Range: 20~80,100

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

Over Current When the actual current of the TAM board
upperLimitPercent Alarm Threshold power supply channel is greater than
Percent “Working Current Value*local value/100,”
over current alarm is reported.
Value Range:
0: Close
1: Open
portSwitchStatus Port Switch Status
switch status of whether to enable current
control.
2.1.2.13 Epm
This sheet is used to configure embedded power equipment.
Table 2-10 Epm Sheet

It indicates the board for BBU to connect with the
refSdrDevic embedded power device (SA/ SE/RU).
Connected Board
eGroup 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
Data Processing
dataProces 0: Transparent transmission
Mode of built-in
sMode 1: Parse
power device
2.1.2.14 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 2-11 FiberCable Sheet
Parameter
Item Value Description
Name
Optical Port of
Format: (RackNo,ShelfNo,BoardNo):Pot
Previous Hop in
ref1FiberDevice If RRU is used, the port No. is 1 and 2, for
Topology
example, (1,1,3):0
Structure
Optical Port of
Format: (RackNo,ShelfNo,BoardNo):Pot
Next Hop in
ref2FiberDevice Only RRU can be used, and the port No. is 1
Topology
and 2, for example, (51,1,1):1
Structure

2.1.2.15 RfCable
This sheet is used to configure RF connection.
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.
Table 2-12 RfCable Sheet

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 TDD,
Antenna Entity this value may come from the value of the
antEntityNo
Number antEntityNo field in the “IrAntGroup” sheet. For
other modes, a record of antenna entity will be
generated automatically according to this No.
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
retDeviceTyp 1: Uni-antenna RET

RET Device Type
e 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.
2.1.2.16 RfExtendCable
This sheet is used to configure RF extension cable. It shows the connection relation
between two RU ports (RxOut and RxIn).The filling of this sheet is optional and should be
based on the actual situation.
2.1.3 Transmission Parameters
2.1.3.1 Transmission
This sheet is used to configure GU transmission mode, transmission medium, and ATM
transmission address. For the GU mode, it is required to fill in this sheet.
Table 2-13 Transmission

It is used to configure the normal scenario
and high-load scenario in the case of ATM
ATMConfigTyp ATM configuration
transmission mode.
e type
Normal
HighLoad

It is used to configure the quantity of

AAL2.
For the site that uses the ATM
transmission mode and still has the
No. of UBR AAL2 broadband link congestion alarm after the
ubrNumber
PVC high-load scenario is adopted, we can add
the quantity of AAL2 to solve the problem.
Each site can be configured with at most
19 AAL2 links. Refer to Section 0 for
details.
2.1.3.2 PhyLayerPort
This sheet is used to configure physical layer port. The filling of this sheet is mandatory.
One physical layer port occupies one row, and an NE can occupy two or more rows.
It is the physical layer of IP or ATM transmission. Physical layer bearer includes, E1, T1,
and Ethernet.
Table 2-14 PhyLayerPort Sheet
Parameter
Name
This parameter needs to be configured only
Operating when the “refGeDevice” field is configured.
operatingMode
Mode Refer to the Ground Plan template for the
detailed values.
This parameter needs to be configured only

when the “refGeDevice” field is configured.
The values are as detailed below:
{operatingMode==0}[100..1000000] step
Transmitting 100,
egressPeakBitRate
Bandwidth {operatingMode==1}[100..10000] step 100,
{operatingMode==2}[100..100000] step 100,
{operatingMode==3}[100..1000000] step
100,
{operatingMode==4}[100..100000] step 100
It is required to be configured when STM-1 is
codeType
configured.
2.1.3.3 Hdlc
This sheet is about HDLC channel related configuration. Refer to the following table for
the details of the main parameters.
Table 2-15 HDLC Sheet

hdlcNo HDLC Link Number [0..16]
The value is the same as the value of the

Used Physical Layer
refPhyLayerPort phyLayerPortNo field in the
Port
“PhyLayerPort” sheet
Time Slot Bit If the value is set as “0,” it means this time
timeSlotBitMap
Mapping slot is not used.
2.1.3.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 2-16 PPP Sheet

pppLinkNo PPP Link No. [0..15]

localIp Base Station IP IPV4
PPP Encapsulation 0:PPP{PPP},

protocolType
Type 1:ML-PPP{ML-PPP}
The value of this parameter is from

refHdlc Used HDLC Channel the value of hdlcNo in the HDLC
sheet.
2: Long sequence
Long/short Sequence
mpCode 6: Short sequence
of MP Head
0xFF: Invalid
{mpCode==2}[1..8],
mpClass MP Priority {mpCode==6}[1..4],
0xFF: Invalid
Whether Support IP 1: Yes

ipCompress
Compression 0: No
Whether Used for FE 1: Yes

isUsedToFECascade
Cascading 0: No
2.1.3.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.
Table 2-17 IpLayerConfig Sheet
Parameter
Name
It is the IP address of the base station. When the

PPP link is used, this IP cannot be configured. It can
be configured as IPv4 address or IPv6 address. The
IPv4 address format is decimal notation separated
ipAddr IP Address 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.The
IPv4 address of the 127 subnetwork and the 200
subnetwork cannot be configured.
Gateway. When the PPP link is used, gateway IP

cannot be configured. It can be IPv4 address or IPv6
address. The IPv4 address format is decimal
gatewayIp Gateway IP 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.
Subnet Mask. When the PPP link is used, gateway

Network
networkMask IP cannot be configured. Only IPv4 address can be
Mask
configured.
Configuration of prefix length. Only IPv6 address

prefixLength Prefix Length
can be configured.
This is the Ethernet link used to bear IP. The value is

Used
from the value of "ethernetLinkNo" field, which is in
refEthernetLink Ethernet Link
the EthernetLink sheet and should have been
No.
configured.
Value range: [0..3]. 255: Invalid.

It is the information of the domain which IP address
ipField IP Domain
belongs to. “255” indicates that it does not belong to
any domain.
vid VLAN ID Configure this item according to the actual situation.
It must be configured.
It is used to generate the content in the ServiceMap
radioMode Radio Mode sheet in association.
If it is not configured, the setup of common channel
will end in failure.

2.1.3.6 StaticRoute
Static route is not required to be configured for GSM or UMTS mode.
2.1.3.7 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.
Table 2-18 Sctp Sheet

Local Port
localPort [1..65535]
Number
Used IP Layer The value comes from the value of “ipNo” in

refIpLayerConfig
Configuration the “IpLayerConfig” sheet.
Remote Port
remotePort [0..65535]
Number
remoteAddr Remote Address IP address
Number of
inOutStreamNum In-and-out [2..6]
Streams
dscp DSCP [0..63]
The value is from the value of “groupNo,” or

refBandwidthRes Used Bandwidth
“resourceNo” in the “BandwidthResource”
ource Resource
sheet. The filling of this field is optional.
1:UMTS{UMTS},
2:GSM{GSM},
8:CDMA{CDMA},
32:TD-LTE{LTE TDD}
radioMode Radio Mode 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.
2.1.3.8 OmcChannel
This sheet is about OMC channel related configuration.
Table 2-19 ItfUniBts Sheet

OMC Interface Link
itfUniBtsNo [1..65535]
Number
Type of Operation 0:IPINIP,

itfUniBtsType and Maintenance 1:IPOA,
Interface 2: Independent Networking
Used IP Layer The value comes from the value of “ipNo”

refIpLayerConfig
Configuration in the “IpLayerConfig” sheet.
It is the virtual address on the RPU at the

gatewayIp OMC Gateway IP RNC side. For the UMTS mode, it is
usually set as 10.9.X.63.
If UMTS mode is used, it is the IP address

omcServerIp OMC Server IP
of eth6:2 for V4.

OMC Network
omcNetworkMask Network Mask
Mask
The value is from the value of

refBandwidthRes Used Bandwidth
"ResourceNo" in the “BandwidthResource”
ource Resource
sheet.
Dscp DSCP [0..63]
2.1.3.9 ServiceMap
This sheet is about service and DSCP mapping related configuration. One mode
occupies one row. In multi-mode, one NE needs several pieces of records.
It is not necessary to configure this sheet in GSM single mode, UMTS single mode, or GU
dual-mode. It is automatically created in association with the radioMode field in the
IPLayerConfig sheet.
Table 2-20 ServiceMap Sheet

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

refBandwidthRe Used Bandwidth
"ResourceNo" in the
source Resource
“BandwidthResource” sheet.
The value is the same as the value of

refOperator Operator Name
“operatorName” in the “Operator” sheet.
2.2 UMTS Wireless Plan Template Filling

Specifications
There are four sheets in the UMTS Wireless Plan template, as detailed in the following
table.
Table 2-21 Description of Sheets in UMTS Wireless Plan Template
No. Sheet Name Value Description

1 UMTS Radio Configuration information of UMTS radio mode
2 UMTS Sector Configuration information of UMTS sector
3 UMTS Local Cell Configuration information of UMTS local cell
Configuration information of UMTS local cell

4 ULocalCellRelation
relation
2.2.1 UMTS Radio
This sheet is used to configure UMTS global information. Refer to the following table for
Table 2-22 UMTS Radio Sheet

nodeBId NodeB ID [0..65535]
paShareRatio Power-sharing Ratio [0..50]
Enable Dynamic 1: Yes

enableDPT
Power Track (DPT) 0: No
Maximum Number of [1..3840],[65535..65535]

maxUplinkCE
Uplink CE 65535: Invalid
Maximum Number of [1..3840],[65535..65535]

maxDownlinkCE
Downlink CE 65535: Invalid
Indicate whether to enable the

Baseband Pool in Node B
Baseband Pool in function.
basebandPoolSwitch
NodeB 1:Yes,
0:No
<default:1>

Indicate whether to automatically

allocate the baseband resource
(BpDevice) for the local cell.When
the function is enabled, the
baseband resource will be
Automatic balance in
autoAssignBpResSwitch automatically allocated for local
baseband resource
cell, and the user cannot operate
Baseband Pool Object.When the
function is disabled, the baseband
resource will be configured by the
user.
Automatic balance in baseband resourceAs to the baseband resource pool, pay attention
to the following points:
1. If “basebandPoolSwitch” is enabled, it is necessary to configure the

“UBasebandPool” sheet, which means baseband resource pool configuration is
supported. Meanwhile, “autoAssignBpResSwitch” must be disabled.
2. If “basebandPoolSwitch” is disabled and “autoAssignBpResSwitch” is enabled, the

system will allocate the baseband to the cells automatically.
3. If “basebandPoolSwitch” and “autoAssignBpResSwitch” are both enabled, it is

necessary to configure the “Baseband resource assignment” field in the “UMTS
Local Cell” sheet, i.e., allocate the baseband to the cells manually.
2.2.2 UMTS Sector
This sheet is about UMTS sector related configuration. Refer to the following table for the
details of the main parameters.
Table 2-23 UMTS Sector Sheet

userLabel Sector Name [0..199]
0: No Diversity
2:2-RRU NOT DIV
5:3-RRU NOT DIV
txType Tx Type 3:4-RRU NOT DIV
4:5-RRU NOT DIV
7:6-RRU NOT DIV
8:MIMO{MIMO}
(RackNo, ShelfNo, SlotNo):portNo;(RackNo,

txDevice Tx Device ShelfNo, SlotNo):portNo)
eg:(51,1,1):1;(51,1,1):2
1: No Diversity
2:Diversity
9:2-RRU NOT DIV
4:2-RRU DIV
11:3-RRU NOT DIV
6:3-RRU DIV
rxType Rx Type 8:4-RRU NOT DIV
3:4-RRU DIV
10:5-RRU NOT DIV
5:5-RRU DIV
12:6-RRU NOT DIV
7:6-RRU DIV
13:MIMO{MIMO}
(RackNo, ShelfNo, SlotNo):portNo;(RackNo,

rxDevice Rx Device ShelfNo, SlotNo):portNo)
eg:(51,1,1):1;(51,1,1):2
2.2.3 UMTS Local Cell
This sheet is about UMTS local related configuration. Refer to the following table for the
details of the main parameters.
Table 2-24 UMTSLocal Cell Sheet

Local Cell
userLabel [0..199]
Description
1: Yes
0: No
isAutoAssignBa Automatically
If there is no special requirement, it is
sebandResourc Assign Baseband
recommended that this parameter be set to
e Resource
“1,” i.e., assignment baseband resource
automatically.
Fill in the Slot No. of boards such as BPC,
BPK, etc. The format of boards, e.g., BPK_d
which has several units, is: Slot No.#Unit
No. Default: 0. Separate the Nos. with “&” if
there is more than BP board. In Shelf 2, the
Baseband
actual Slot No. should be “Slot No. of the BP
refBpDevice Resource
boards + 20,” starting from 24.
Assignment
It can be left blank when
“isAutoAssignBasebandResource” is “1.” If it
is not configured, it means the baseband
resource board of cells is automatically
allocated.
USectorId UMTS Sector ID [1..30]
{parent.band==1}[21100..21700],
{parent.band==2}[19300..19900],
{parent.band==3}[18050..18800],
txFreq Tx Frequency {parent.band==4}[21100..21550],
{parent.band==5}[8690..8940],
{parent.band==7}[26200..26900],
{parent.band==8}[9250..9600]
50:5M{5M},
48:4.8M{4.8M},
rcvFilterBandwid UMTS Reception 46:4.6M{4.6M},
th Filter Bandwidth 44:4.4M{4.4M},
42:4.2M{4.2M},
38:3.8M{3.8M}
2500: 2.5km
5000: 5km
10000: 10km
20000: 20km
cellRadius Cell Radius
40000: 40km
80000: 80km
120000: 120km
240000: 240km
Downlink Delay [-63..63]

txOffset
Offset Default: 0.
[-63..63]
rxOffset Uplink Delay Offset
Default: 0.
[1..200],[255..255]
Local Cell Max Tx
maxDlPwr When it is configured to 255, it means the
Power
cell power is allocated at the RNC.
0: 0-250km/h
supportSpeed Support Speed
1: 250-350km/h
0: Indoor
coverageType Coverage Type
1: Outdoor
Enable
enableEnergySa 1: Yes
Electric-saving
ving 0: No
Mode
0:Enable{Enable},
enable2msGain Support 2ms Gain
1:Disable{Disable}
Support VAM 1: Yes

enableVAM
Function 0: No
enhancedVamE Enable E-VAM 1: Yes

nable Function 0: No
Enable Dynamic 1: Yes

enableDynCode
Code 0: No
refOperator Operator operatorName

2.2.4 ULocalCellRelation
This sheet is used to configure UMTS dual-carrier cells. Refer to the following table for
Table 2-25 ULocalCellRelation Sheet

The value of this parameter comes from
ref1ULocalCell Primary Cell ID the value of “USectorId" in the "UMTS
Local Cell" sheet.
The value of this parameter comes from

ref2ULocalCell Secondary Cell ID the value of “USectorId" in the "UMTS
Local Cell" sheet.
2.2.5 UBasebandPool
It is used to configure the baseband resource pool information of a base station. The
details of the related information are as shown in the table below.
Table 2-26 UBasebandPool
Parameter
Name
Baseband Pool It must be unique within the value
basebandPoolId
ID range.
Fill in the Slot No. of boards such

as BPC, BPK, etc. For the boards
such as BPK_d and BPN1 which
has several units, the format is:
Associated
Slot No.#Unit No. Default: 0.
refBpDevice baseband
Separate the Nos. with “&” if there
resource
is more than one board. In Shelf 2,
the actual Slot No. should be “Slot
No. of the BP boards + 20,”
starting from 24.
The local cell associated with the

baseband resource pool. It
Associated local corresponds to the USectorId in
refULocalCell
cell the “UMTS Local Cell” sheet.
Separate the IDs with “&” if there
is more than one ID.
2.2.6 QcellTxResGroup
This sheet is used to configure the Qcell related information.
2.2.7 QcellRxResGroup
This sheet is used to configure the Qcell related information.

3 Data Import and Export Functions

V4.14 OMMB plan data import and export functions have the following features:
1. The data can be exported by template type (Wireless Plan Template or Ground Plan
Template).
2. The NE and object range can be defined to import and export parameters.
3. The exported data, after being edited, can be imported again in to OMMB.
3.1 Notices in Operation
1. It is required to perform data backup before batch data modification (please refer to
the corresponding manual for data backup),
2. Before performing batch data modification, make sure there is no user operating NE
data and there is no time-consuming and resource-consuming tasks running on the
server.
3. Make sure to export only the managed NE object to be modified to save memory
resource.
4. In an overall network parameter modification, at most 500 base stations can be

modified each time.
3.2 Planning Data Import
After the filling of Plan Template is completed, choose Configuration Management >
Planning Data Import on OMMB.
Figure 3-1 Planning Data Import
Select the path for storing the Plan Template and import data.
Figure 3-2 Set the Path of Plan Templates
After the data is imported completely, right-click the record and choose Result File to
view the log.

Figure 3-3 View Log File
3.3 Planning Data Export
Choose Configuration Management > Planning Data Export on OMMB.
Figure 3-4 Planning Data Emport
The following figure shows the Planning Data Export window.
Figure 3-5 Planning Data Export Window
Select the sbunetwork or NE to be exported in the pane on the right of the window. The
description of the parameters to be exported is as shown below.
1. Data area: Select Modify area or Snapshot area.
Modify area: It means exporting the configuration data in the Modify area of the choosen
managed element.
Snapshort area: It means exporting the configuration data in the Snapshot area of the
choosen managed element.
2. Export file: Select the number of the files to be exported.
Single: All configuration data is saved in one Excel file.
Multiple: The data exported is divided by the number of subnetworks, i.e., the data of
each subnetwork is saved as an Excel file.
3. Data Type: Select the type of the template to be exported.Either Ground Plan
template or the Plan template of different modes can be exported.
Figure 3-6 Data Type

4. File path: Select the storage path of the Plan template and set the name of the
exported data.
Figure 3-7 File Path
4 Explanation of Common Operations
4.1 Examples of Configuration Scenario
4.1.1 Adding Boards and Modifying Board Type
It is necessary to add BPC at Slot 6. In the “Equipment” sheet, modify the value of
“MODIND” of the original data of the BPC at Slot 6 from “A” to “M.”The modification
method is as shown in the figure below.
Figure 4-1 Add BPC Board
After the data modification is completed, import the data into OMMB through the Plan
template.

Figure 4-2 Import Data to OMC
After the planning data is successfully imported, perform data synchronization.
Figure 4-3 Data Synchronization
Synchronize modified data to the base station.
Figure 4-4 Synchronize Modified Data
Note:
“Generate synchronization file” is used to generate the xml file that can be imported into
LMT.
For V4.14, the type of some boards can be modified directly, e.g., CC, BPC, and RU.
Modify the board type to the target value in the “Equipment” or “RU,” change the
MODIND to “M,” and import the data to OMM.
The modification to the RU type should meet the following requirements:
1. The maximum number of the new RRUs supported must be equal to or larger than
the number of the old RRUs.
2. The frequency band should be the same (the frequency band of the new RRU
should include that of the old RRU).
3. The rated power of the new RRU must be greater than or equal to that of the old
RRU (replace the small-capacity RU with a large-capacity RRU).
4. If the old RU supports cross-diversity, the new RU should also support it.
5. The functionMode of the new and old RUs should be consistent.

4.1.2 E1 Capacity Expansion/Reduction
For the sites using ATM (E1), the modification of E1 number is a very common scenario
in the field. The data modification flow in this scenario is detailed in the following
example.
Example: NodeB 201 uses ATM (E1) transmission. There are two pieces of E1 in the
initial site commissioning, and now the transmission needs to be expanded to four pieces
of E1. The operation process is as shown below:
1. Export the PLAT template of the existing site.
Figure 4-5 Planning Data Export
2. Select PUBLIC for NE Mode to export the Snapshot Area PLAT template of the site.
Figure 4-6 Export PLAT Data
3. Open the exported PLAT template, and modify the format of the “Transmission”
sheet according to the following description.
The MODIND of the first record is “D,” which means deleting the related PVC and AAL
data generated previously when there are two pieces of E1.
The MODIND of the second record is “A,” which means generating PVC, AAL, and other
related parameters according to the new number of E1 links.
Figure 4-7 Modification to the Transmission Sheet
4. Add two pieces of E1 records in the “PhyLayerPort” sheet.

Figure 4-8 Modification to Parameters in the “PhyLayerport” Sheet
5. After the modification to the above two sheets is completed, import the data to
OMMB and synchronize the data to SDR.
4.1.3 Batch Configuration Data Modification
In V4.12, data modification can be performed on GUI. The batch data modification flow is
as detailed below:
Example: For OMMBV12.12.40, the “Maintenance Status” field is set as “3” by default.
For a newly-commissioned site, the value of the field should be modified to “0” after the
planning data is exported, so as to make sure the link with OMMB can be established
normally after the transmission is normal.
1. Open Batch Configuration Data Modification.
Figure 4-9 Batch Configuration Data Modification
2. Select the NE to be modified, and click the configuration tree ( ).
Figure 4-10 Select a Site
3. Select the site to be modified, right-click it to select Select Column and then select
Modify. Select the target value in the pop-up dialog box, and then click Save to
finish the batch data modification. After the modification, synchronize the modified
data.

Figure 4-11 Batch Modification
4.1.4 Snapshot Area Data Recovery
The data in the Snapshot Area is the data currently running in SDR.The data in the
Modify Area is the data saved in OMMR, which can be modified and synchronized to
SDR through all-data synchronization or modified-data synchronization.In some
scenarios, the data in the Snapshot Area needs to be recovered in the Modify Area with
the following method.
Click Configuration Management > Advanced > Batch NE’s Operation.
Figure 4-12 Batch NE’s Operation
Select the site and click Copy Snapshot Area Data to Modify Area to recover the data
from the Snapshot Area to the Modify Area.
Figure 4-13 Copy Snapshot Area Data to Modify Area
4.2 Acquisition of LMT Configuration File
When commissioning a base station on site, the engineers usually use EOMS to view the
data and configuration.
The EOMS of V4.14 only supports the data import and export of the configuration file in
XML format. The process of acquiring the XML-format file is as follows:
1. Open Configuration Management > Data Synchronization on OMMB.

Figure 4-14 Data Synchronization
2. Select the NE for configuration file export from the NE tree on the left.
For the Synchronization Mode, select Generate synchronization file.
Figure 4-15 Generate Synchronization File
3. After the data synchronization succeeds, the system will automatically generate an
XML file that can be imported into LMT.
5 Examples of Data Configuration

This chapter describes the data configuration for the five common transmission modes
used in the UMTS scenario.
1. NodeB201: ATM transmission
Ground template: Pure ATM transmission is used, and the data configuration is
relatively simple.ATM Configure Type should be configured to the common
scenario.
Wireless template: configure four RRUs, among which RRU53 and RRU54 are for
the STSR cells, and the rest are for the OTSR cells.
2. NodeB202: FE Transmission
Ground template: the O&M address and service address are separated and planned
in different VLANs. For the configuration in the field, the two addresses can be the
same.
3. NodeB203: IPOE
4. NodeB204: ATM+IP transmission
5. NodeB205: IPOE+FE transmission; the RRU for the wireless plan template should
be configured to cross-diversity.
Refer to the following document.
a) OSS_PLAT_CM_Ground_Plan.xls
b) OSS_UMTS_CM_Wireless_Plan.xls

AppA Iub-interface E1 Transmission Bandwidth

Configuration Tool
When a base station uses ATM or ATM+IP transmission, it can be configured with a
general or a high-load scenario. For the corresponding PVC bandwidth and number of
PVCs, refer to the following document.
ZXWR RNC Iub-interface E1 Transmission Bandwidth Configuration Tool

(Corresponding OMMB Version).xls
AppB Slot Configuration Tool

Refer to the following document.
ZXSDR B8200 GUL Board Hardware Configuration Guide_Slot Configuration Tool.xls

U - ZXSDR (V4.14) Quick Data Configuration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

U - ZXSDR (V4.14) Quick Data Configuration Guide

Uploaded by

Copyright:

Available Formats

U_ZXSDR (V4.

14) Quick Data

Product Version Document Version Serial Number Reason for Revision

Intended audience: Base station commissioning engineers

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

About This Document

1 Plan Templates ................................................................................................. 1

2 Plan Template Filling Specifications .............................................................. 4

3 Data Import and Export Functions ............................................................... 43

4 Explanation of Common Operations ............................................................ 48

5 Examples of Data Configuration ................................................................... 58

AppA Iub-interface E1 Transmission Bandwidth Configuration Tool ................. 59

AppB Slot Configuration Tool ................................................................................. 60

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

Figure 1-1 Generate Template ............................................................................................... 1

Table 2-1 Instructions on Filling in Sheets in Ground Plan Template .................................... 4

Table 2-5 RU Sheet ............................................................................................................. 14

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

1.1 Introduction to Plan Templates

Figure 1-1 Generate Template

1.2 Template Acquisition Path

1. The Ground Plan templates are all stored under the

Figure 1-2 Template Storage Path

1.3 Description of Template Format

1. Conventions of Table Header

The second row is the field name displayed on OMM.

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

2. Conventions of Sheet Arrangement

A (ADD): Add a new record.

M (MODIFY): Modify the record.

D (DELETE): Delete the record.

P (PASS): Do not perform any operation to the record of this row.

2 Plan Template Filling Specifications

2.1 Ground Plan Template Filling Specifications

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

No. Sheet Name Description

This sheet is used only to configure the data of the

This sheet provides the configuration information of

This sheet is about the 1588 clock configuration. If

This sheet provides the configuration of clock

This sheet is about the configuration of RU device,

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

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

It is the power amplifier of RU device. PA related

It is the fan control and environment monitoring board.

This sheet is about dry contact configuration.

11 TMA TMA equipment related parameters

This sheet is about AISG device configuration. It is an

It is about power output configuration. Currently,

Embedded power supply equipment is a device

Fiber resource. It is about the connection between

RF connection and RF feeder resources. It refers to

This sheet is used to configure RF extension cable. It

Overall transmission parameters. The parameters in

The physical layer in the IP or the ATM transmission

HDLC protocol related parameters include HDLC link

This is the sheet of PPP protocol-related parameters.

23 Static Route Static route parameters configuration.

24 BandwidthResource This sheet contains bandwidth resource parameters.

This sheet is about SCTP parameters configuration.

26 OmcChannel OMC channel parameters

This sheet is used to configure the mapping between

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