SJ-20141110151550-005-ZXSDR UniRAN TDD-LTE (V3.20.50) Performance Indicator Reference

ZXSDR UniRAN
TD-LTE Base Station
Initial Configuration Guide

Version: V3.20.50
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2015 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution 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.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R2.0
2015-04-30
V3.20.50.30
Those topics have been modified:
R1.0
2014-11-15
3.3 Creating an NE
5.1.1 Creating a Baseband Resource Board
5.1.2 Creating an RRU
5.3.1 Configuring the GPS Clock Source
5.3.2 Configuring the 1588 Clock Source
6.1 Configuring a Physical Layer Port
6.4.2 Configuring DSCP Mapping
6.5 Configuring a Static Routing
7.1 Configuring TD-LTE Global Parameters
7.2 Configuring Baseband Resources
7.4 Configuring a Serving Cell
First edition
Serial Number: SJ-20141110151550-006

Publishing Date: 2015-04-30 (R2.0)
SJ-20141110151550-006|2015-04-30 (R2.0)
ZTE Proprietary and Confidential
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
Chapter 2 Configuration Preparations ..................................................... 2-1
Chapter 3 Initial Management Information Configuration ...................... 3-1
3.1 Creating and Starting an NE Agent...................................................................... 3-1
3.2 Creating a Subnetwork ....................................................................................... 3-5
3.3 Creating an NE .................................................................................................. 3-6
3.4 (Optional) Applying For or Releasing the Mutually Exclusive Access...................... 3-9
3.5 (Optional) Configuring System Parameters ........................................................ 3-10
Chapter 4 Operator Information Configuration ....................................... 4-1

4.1 Creating an Operator.......................................................................................... 4-1
4.2 Creating a PLMN................................................................................................ 4-2
Chapter 5 Physical Resource Configuration ........................................... 5-1

5.1 eNodeB Creation................................................................................................ 5-1
5.1.1 Creating a Baseband Resource Board....................................................... 5-1
5.1.2 Creating an RRU...................................................................................... 5-4
5.2 Configuring the SNTP......................................................................................... 5-6
5.3 Clock Source Parameter Configuration ................................................................ 5-9
5.3.1 Configuring the GPS Clock Source............................................................ 5-9
5.3.2 Configuring the 1588 Clock Source ......................................................... 5-14
5.4 Power Module Configuration ............................................................................. 5-23
5.5 Configuring the Baseband Board Attributes........................................................ 5-24
5.6 Configuring the Optical Port Attributes of a Baseband Board ............................... 5-25
5.7 Configuring the RRU Attributes ......................................................................... 5-28
5.8 BTS Auxiliary Peripheral Device Configuration ................................................... 5-32
5.8.1 Querying Antenna Attributes ................................................................... 5-32
5.8.2 Creating an Antenna Entity ..................................................................... 5-35
5.8.3 Configuring an RF Cable ........................................................................ 5-37
5.8.4 Configuring an Ir Antenna Group ............................................................. 5-39
5.8.5 Configuring a Fiber Cable ....................................................................... 5-40
Chapter 6 Network Transmission Configuration ..................................... 6-1

6.1 Configuring a Physical Layer Port........................................................................ 6-2
I
SJ-20141110151550-006|2015-04-30 (R2.0)
6.2 IP Transmission Configuration............................................................................. 6-5

6.2.1 Configuring an Ethernet Link ..................................................................... 6-5
6.2.2 Configuring the IP layer ............................................................................ 6-6
6.3 Bandwidth Configuration..................................................................................... 6-9
6.3.1 Configuring a Bandwidth Resource Group ................................................. 6-9
6.3.2 Configuring Bandwidth Resources............................................................6-11
6.4 Signaling and Business Configuration................................................................ 6-12
6.4.1 Configuring SCTP Parameters ................................................................ 6-12
6.4.2 Configuring DSCP Mapping .................................................................... 6-14
6.5 Configuring a Static Routing.............................................................................. 6-16
6.6 Configuring an OMC Channel ........................................................................... 6-18
Chapter 7 Radio Parameter Configuration............................................... 7-1

7.1 Configuring TD-LTE Global Parameters ............................................................... 7-1
7.2 Configuring Baseband Resources ....................................................................... 7-3
7.3 S1AP Configuration ............................................................................................ 7-5
7.4 Configuring a Serving Cell .................................................................................. 7-6
Chapter 8 XML File Generation ................................................................. 8-1

8.1 Generating XML Files for an eNodeB .................................................................. 8-1
8.2 Generating XML Files for the EMS ...................................................................... 8-3
Glossary .......................................................................................................... I
II
SJ-20141110151550-006|2015-04-30 (R2.0)
About This Manual

Purpose
This manual provides a guide for the initial configuration of the ZXSDR UniRAN.
Intended Audience
This manual is intended for:
l
l
l
Commissioning engineers
Network planning engineers
Maintenance engineers
What Is in This Manual

This manual contains the following chapters.
Chapter 1, Overview
Describes the concept, methods, tools, and flow of initial

configuration.
Chapter 2, Configuration
Describes preparations before initial configuration.
Preparations
Chapter 3, Initial Management
Describes how to configure initial management information.
Information Configuration
Chapter 4, Operator Information
Describes how to configure operator information.
Configuration
Chapter 5, Physical Resource
Describes how to configure the BBU, RRU, and auxiliary
Configuration
devices of an eNodeB.
Chapter 6, Network Transmission
Describes how to configure network transmission.
Configuration
Chapter 7, Radio Parameter
Describes how to configure radio parameters.
Configuration
Chapter 8, XML File Generation
Describes how to generate XML files after initial configuration

is completed.
Related Documentation
l
l
ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Ground Parameter Reference

ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Radio Parameter Reference
Conventions
This manual uses the following conventions.
I
SJ-20141110151550-006|2015-04-30 (R2.0)
Danger:sets an imminently hazardous situation. Failure to comply

can result in death or serious injury, equipment damage, or site
breakdown.
Warning: sets a potentially hazardous situation. Failure to comply
can result in serious injury, equipment damage, or interruption of
major services.
Caution:sets a potentially hazardous situation. Failure to comply
can result in moderate injury, equipment damage, or interruption
of minor services.
Note:provides additional information about a topic.
II
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 1
Overview
Initial Data Configuration
After installing an eNodeB, you can create a complete set of initial configuration files for
the application scenario based on hardware configuration, network planning, and data
negotiated with other Network Elements (NEs). After that, you can create a configuration
file for a new eNodeB by using the BCT tool based on this initial configuration.
Initial Configuration Methods

The eNodeB initial configuration uses the EMS configuration and is used for a new office.
An initial configuration file is provided in XML format, and data contained in the file must
be complete, valid, and match the physical device.
After the eNodeB initial configuration is completed, tow types of basic templates can be
generated in export mode, and apply to the following two scenarios:
l
An XML file for the EMS: the XML file (display values) obtained by executing
Configuration Management > Data Export is used for data backup and restoration
on the EMS.
An XML file for an eNodeB: the XML file (memory values) exported by executing Data
Synchronization > File Generation is loaded as a basic template for the LMT, BCT,
and UMaker tools as a basic template.
Initial Configuration Tools

Because the EMS is easy to be used and provides centralized maintenance, eNodeB initial
configuration is performed on the EMS.
The EMS uses a client-server architecture. The functions of the server and client are
described as follows:
l
l
Server: as the core of the EMS, implements the management function. Sun servers
(with Solaris), IBM servers (with AIX), and Oracle 11g database are used for servers.
Client: allows users to remotely log in to the server and perform NE operation and
maintenance. PCs are used for clients.
Initial Configuration Flow

Because some configurations depend on each other when an eNodeB is configured, it is
recommended to follow the configuration flow, see Figure 1-1, to improve the configuration
procedure.
1-1
SJ-20141110151550-006|2015-04-30 (R2.0)
ZXSDR UniRAN Initial Configuration Guide
Figure 1-1 Initial Configuration Flow
1-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 2
Configuration Preparations
Preparing Configuration Data
Before initial configuration on the EMS, you must create and start an NE agent. For details,
refer to 3.1 Creating and Starting an NE Agent. In addition, you must collect corresponding
configuration data based on hardware configuration, transmission network architecture,
and service planning, and obtain the following files which include:
l
l
l
l
eNodeB equipment data: contains the BOQ and site design result.
eNodeB clock data: clock parameters including the GPS, IEEE 1588,and SNTP.
eNodeB transmission data: contains eNodeB site parameters and parameters related
to transmission planning.
eNodeB radio data:contains parameters related to cell and sector planning.
Preparing Parameter Documents

This document contains a description of the key parameters for initial configuration, and
these key parameters are only used to start basic services of a single base station. For
complete configuration parameters or optimization parameters, refer to the following
documents:
l
l
ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Ground Parameter Reference

ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Radio Parameter Reference
The above parameters come from the following three sources:

l
l
l
User planning: parameters planned by the operator.

Negotiating planning: parameters negotiated between the core network and
transmission equipment.
Internal planning: parameters planned by ZTE engineers in accordance with ZTE
principles.
2-1
SJ-20141110151550-006|2015-04-30 (R2.0)
This page intentionally left blank.
2-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 3
Initial Management
Information Configuration
Before eNodeB initial configuration, you need to create an NE agent, to apply for the
mutually exclusive access for an NE, and to open the Configuration Management
window. This chapter describes how to configure initial management information.
Table of Contents
Creating and Starting an NE Agent.............................................................................3-1
Creating a Subnetwork ...............................................................................................3-5
Creating an NE...........................................................................................................3-6
(Optional) Applying For or Releasing the Mutually Exclusive Access ..........................3-9
(Optional) Configuring System Parameters...............................................................3-10
3.1 Creating and Starting an NE Agent

An NE agent is the agent of the lower-level EMS in the NetNumen U31. The NetNumen
U31 creates an NE agent and sets its attributes, and then accesses a lower-level EMS by
starting this NE agent. This procedure describes how to create and start an NE agent.
Prerequisite
The EMS server is installed.
Context
For the parameters for creating an NE agent, refer to Table 3-1.
Table 3-1 Parameters for Creating an NE Agent
Tab
Parameter
Description
Name
Name of the NE agent. A name that can directly indicate where

the NE agent is located is recommended. This parameter is
required.
Basic
Time zone
Time zone where the NE agent is located. This parameter is

required, and should be set based on the local time zone.
attributes
Vendor
Vendor that manufactures the devices managed by the lower

EMS. The default value can be used.
IP address
IP address of the lower EMS. This parameter is required.

3-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Tab
Parameter
Description
Administrative
Administrative state of the NE agent. This attribute is
state
automatically set by the system, and cannot be modified by

users. When an NE agent is initially created, the state is
"Deactivated" by default. After the NE agent is created and
started, the state changes to "Activated".
Operation problem
Usage state of the NE agent. This attribute has three values:

None, Problem, and Being Stated in the Background. The
values are automatically set by the system, and cannot be
modified by users. When an NE agent is initially created, this
attribute is "None". After the NE agent is created, this attribute
indicates the usage state of the NE agent. For example, if an
error message about the NE agent is displayed on the screen,
this attribute is "Problem". A user can view the administrative
state and usage state by querying this attribute.
Location
Sets where the NE agent is stored. This parameter is optional.
Memo
sets other information of the NE agent. This parameter is

optional.
Port
Port number through which a Socket link is established

between the NE agent and the lower EMS. The default value
(264125) is recommended. This parameter is required.
FTP port
Port number through which an FTP or SFTP link is established

between the NE agent and the lower EMS. The port number
must be the same as the FTP or SFTP port number of the
lower EMS. By default, FTP is used for file transfer. The
default value port number is 64021. If the system indicates
that the FTP or SFTP port number is not correct, maybe the
lower EMS does not use the default value. You can try to
modify the port number, or communicate with the lower EMS
Extended
operator. This parameter is required.
attributes
EMS IP address
IP address of the EMS. This parameter can be modified to the

actual address or be set to the default value.
EMS IP address
IP address of the standby EMS server.
(Stand by)
SSH
Sets whether SSH is used or not. By default, SSH is not used.

If SSH is used, both the EMS and lower EMS must support
SSH.
SSH port
SSH port number. The default value is 21140. If the system

indicates that the SSH port number is not correct, the operator
can communicate with the lower EMS operator.
3-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 3 Initial Management Information Configuration
Steps
1. Double-click the EMS client icon, enter the correct user name, password and server
address in the Login dialog box, and click OK. The main interface of the EMS client
is displayed. Be default, the Topology Management interface is displayed.
2. In the left pane, right-click EMS Server and select Create Object > Basestation
> Multi-mode > MO SDR NE Agent. The Create MO SDR NE Agent window is
displayed.
3. On the Basic Attributes tab, enter the name, time zone, vendor, and IP address of
the NE agent, see Figure 3-1. For a description of the parameters, refer to Table 3-1.
Figure 3-1 Basic Attributes
4. Click the Extended Attributes tab, and enter the port and FTP port, see Figure 3-2.
For a description of the parameters, refer to Table 3-1.
3-3
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 3-2 Extended Attributes
5. Click OK. The Create MO SDR NE Agent dialog box is closed. The NE Agent node
is created.
6. Right-click the NE Agent node, and select NE Agent Management > Start to start
the NE agent.
Note:
It takes about 5 to 10 minutes (depends on the server performance) for an NE agent
to start the first time.
7. Check whether the NE agent is properly started. If yes, the NE Agent node is shown
in blue or red.
3-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Note:
If the NE Agent node is shown in blue, it is properly started. If the node is shown in
red, it is properly started but with alarms.
End of Steps
3.2 Creating a Subnetwork

The purpose of creating a subnetwork is to manage adjacent base stations. This procedure
describes how to create a subnetwork.
Prerequisite
The NE agent is started.
Steps
1. In the EMS client window, select Configuration > NE Management.
Management window is displayed.
The NE
2. In the left pane of the NE Management window, right-click the NE agent and select
Start NE Management. After about one minute, NE management is started, and a
green check mark is displayed on the NE, see Figure 3-3.
Figure 3-3 NE Management Is Started
3. Right-click the NE agent, and select Configuration Management.

Configuration Management window is displayed.
The
4. In the Configuration Management window, right-click the NE agent and select Create
Subnetwork. The SubNetwork tab is displayed.
5. On the SubNetwork tab, set the parameters as required, see Figure 3-4. For a
description of the parameters, refer to Table 3-2.
3-5
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 3-4 Creating a Subnetwork
Table 3-2 Subnetwork Parameters

Parameter
Description
Value Range
Default Value
User Label
Label of the user.
[0..128]
N/A
SubNetwork ID
Subnetwork ID, which
[0..999999]
identifies a subnetwork.
6. Click
End of Steps
3.3 Creating an NE
This procedure describes how to create an NE, that is, an eNodeB in a subnetwork.
Prerequisite
The subnetwork which the eNodeB belongs to is created.
Steps
1. In the Configuration Management window, right-click the created subnetwork and
select Create NE. The Managed Network Element tab is displayed.
2. On the Managed Network Element tab, set the parameters as required, see Figure
3-5. For a description of the key parameters, refer to Table 3-3.
3-6
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 3-5 Managed Network Element Tab
Table 3-3 Managed Network Element Parameters

Parameter
Description
Value Range
Default Value
Radio Standard
Radio standard supported by
LTE FDD, TD-LTE,
LTE FDD
the NE.
LTE FDD+TD-LTE
This attribute is the unique
[1..1500]
Should be the
N/A
NE ID
identification of a network
element. It is used to
distinguish different network
elements. It is generated
automatically by the NMS.
NE Configuration
NE version.
Data Version
same as the actual

version.
NE Type
This attribute identifies the
BS8700, BS8800,
network element type in
BS8900, BS8900A,
various radio modes, such
BS8906
BS8700
as NodeB and BTS. At the

base station side, the network
management type is set to
SDR.
3-7
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
BBU Type
The BBU type is tightly related
B8200, B8300
B8200
Configuring
to the NE type. If the NE type

is set to BS8700, the BBU
type must be BS8200[0] or
BS8300[4]. If the NE type is
set to other values, the BBU
type must be BS8200[0].
NE Maintenance
Maintenance status of a
Normal, Testing,
Status
base station. Only when a
Configuring, FM
base station is in Normal
testing, PM testing
state, may a communication

link be established between
the eNodeB and the EMS.
After being synchronized, the
eNodeB can report alarms.
Maintenance Status
Maintenance status of an LTE
Normal, Testing, FM
of LTE TDD
TDD eNodeB. Only when an
testing, PM testing
Testing
LTE TDD eNodeB is in Normal

state, may a communication
link be established between
the eNodeB and the EMS.
After being synchronized, the
eNodeB can report alarms.
NE running mode
Network element running
Master&slave,
mode.
Load-sharing,
Master&slave
Overlay load sharing

NE address
IP address through which the
N/A
N/A
Normal, C Class, B
Normal
eNodeB communicates with

the EMS. The IP address may
be an IPv4 address or IPv6
address.
Priority
NE priority.
Class, VIP
3. Click
3-8
SJ-20141110151550-006|2015-04-30 (R2.0)
Note:
After an NE is created, the system automatically creates a basic configuration set for
this NE.
End of Steps
3.4 (Optional) Applying For or Releasing the Mutually

Exclusive Access
Only after applying for the mutually exclusive access for an NE, can the operator configure
it. The mutually exclusive access for an NE can be allocated to one operator at a time. An
operator automatically obtains the mutually exclusive access for an NE only when he or
she creates it. This procedure describes how to apply for or release the mutually exclusive
access.
Prerequisite
The configuration management window is displayed.
Steps
Applying For the Mutually Exclusive Access
1. In the Configuration Management window, right-click an NE and select Apply For
Mutex Right. The icon is displayed on the NE, indicating that the operator occupies
the mutually exclusive access for the NE.
Note:
If the icon displayed on the NE is red, it sets that another operator occupies the mutually
exclusive access for the NE.
Releasing the Mutually Exclusive Access

2. Right-click the NE and select Release Mutex Right. The icon on the NE disappears,
indicating that the operator releases the mutually exclusive access for the NE.
End of Steps
3-9
SJ-20141110151550-006|2015-04-30 (R2.0)
3.5 (Optional) Configuring System Parameters

System parameters refer to those parameters that are related to the power saving and SON
functions. System parameters should be configured in accordance with the customer's
requirements. If the power saving and SON functions are required, the operator can
enable the functions by configuring the related system parameters. If the functions are
not required, the default values are used.
Prerequisite
The NE is created, and the functions such as power saving and SON are required.
Steps
Configuring Power Saving Parameters
1. In the managed NE tree, expand the System Parameter node and double-click Power
Saving Parameter. The Power Saving Parameter-List tab is displayed, and there
is a default configuration record of power saving parameters.
2. Click
3-6.
, and set the parameters on the Power Saving Parameter tab, see Figure
Figure 3-6 Power Saving Parameter Tab
3. Click
Configuring SON Function Switch Object Parameters

4. In the managed NE tree, expand the System Parameter node and double-click SON
Function Switch Object. The SON Function Switch Object-List tab is displayed,
and there is a default record of SON function switch object parameters.
5. Click
, and click the parameters on the SON Function Switch Object tab, see
Figure 3-7. For a description of the key parameters, refer to Table 3-4.
3-10
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 3-7 Tab of the SON Function Switch Object
Table 3-4 Parameters of the SON Function Switch Object

Parameter
Description
Value Range
Default Value
Configuration
This parameter sets parameter
N/A
N/A
for hardware
configurations related to the
auto-discovery
hardware auto-discovery
switch
function. The information
N/A
N/A
N/A
N/A
of boards which are not

configured will be scanned if
the hardware auto-discovery
function is enabled.
Configuration
This parameter sets parameter
for auto-
configurations related to
commissioning
auto-commissioning.
switch
Configuration
This parameter sets the
for auto-setup
enable/disable function of
transmission switch
automatic link establishment.

The automatic link
establishment function
refers to the function that
the base station attempts to
establish an OMC channel
between the base station
and the OMC automatically
via various physical medium
(FE/ATM/PPP) when the link
between the NE and the NMS
is broken.
3-11
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Configuration for
This parameter sets
N/A
N/A
data rollback switch
configuration for the data

rollback switch. When the link
between the NE and the NMS
is broken, data is rolled back
and the link between the NE
and the NMS is established
again.
6. Click
End of Steps
3-12
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 4
Operator Information
Configuration
Table of Contents
Creating an Operator..................................................................................................4-1
Creating a PLMN........................................................................................................4-2
4.1 Creating an Operator

Before creating the physical resources of an NE, you need to configure information
(including the operator and PLMN) of the operator which the NE belongs to. This
procedure describes how to create an operator.
Prerequisite
The NE is created.
Steps
1. In the Configuration Management window, expand the NE and select Modify Area.
The Managed Element configuration resource tree is displayed below the NE tree.
2. In the Managed Element tree, double-click Operator. The Operator-List tab is
displayed.
. The Operator tab is displayed.
3. On the Operator-List tab, click
4. Set the parameters on the Operator tab, see Figure 4-1. For a description of the key
parameters, refer to Table 4-1.
4-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 4-1 Operator Tab
Table 4-1 Operator Parameters

Parameter
Description
Value Range
Default Value
Operator name
This parameter specifies
[1..127]
N/A
the name of the network

operator using the base
station, containing up to 128
characters.
l
This parameter must not

be empty.
Up to eight records can be

configured for the operator
object.
5. Click
. An operator record is displayed on the Operator-List tab.
End of Steps
4.2 Creating a PLMN

This procedure describes how to create a PLMN.
Prerequisite
l
l
l
The subnetwork is created.

The NE is created.
The operator is created.
Steps
1. In the configuration resource tree, expand Operator and double-click PLMN. The
PLMN-List tab is displayed.
2. On the PLMN-List tab, click
. The PLMN tab is displayed.

4-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 4 Operator Information Configuration
3. Set the parameters on the PLMN tab, see Figure 4-2. For a description of the key
Figure 4-2 PLMN Tab
Table 4-2 PLMN Parameters

Parameter
Description
Value Range
Default Value
MCC
Mobile country code in a
[3..3]
N/A
[2..3]
N/A
PLMN. The combination of

a mobile country code and a
mobile network code, uniquely
identifying the home network
operator of the base station.
The attribute value must be
unique, containing up to three
digits, such as 362.
MNC
Mobile network code in a

PLMN. The combination of
a mobile country code and a
mobile network code, uniquely
identifying the home network
operator of the base station.
The attribute value must be
unique, containing up to three
digits, such as 362.
4. Click
. A PLMN record is displayed on the PLMN-List tab.
End of Steps
4-3
SJ-20141110151550-006|2015-04-30 (R2.0)
4-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 5
Physical Resource
Configuration
Table of Contents
eNodeB Creation........................................................................................................5-1
Configuring the SNTP ................................................................................................5-6
Clock Source Parameter Configuration.......................................................................5-9
Power Module Configuration ....................................................................................5-23
Configuring the Baseband Board Attributes ..............................................................5-24
Configuring the Optical Port Attributes of a Baseband Board ....................................5-25
Configuring the RRU Attributes ................................................................................5-28
BTS Auxiliary Peripheral Device Configuration .........................................................5-32
5.1 eNodeB Creation

There are several NE types such as BS8700, BS8900A, and BS8900B to be selected
when an NE is created. The steps to create eNodeB resources are the same for different
NE types. This document describes how to create an eNodeB with the NE types listed
inTable 5-1 as an example.
Table 5-1 eNodeB Resource Configuration Steps for Different NE Types
NE Type
Step for Creating eNodeB Resources
BS8700
1. To create a baseband resource board, refer to 5.1.1 Creating a Baseband
BS8900A
BS8900B
Resource Board.
2. To create an RRU, refer to 5.1.2 Creating an RRU.
5.1.1 Creating a Baseband Resource Board

This procedure describes how to create a baseband resource board for the BBU in the
EMS configuration set, and how to make the board type and slot conform to the actual
BBU.
Prerequisite
l
l

The NE is created.
5-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
1. In the managed element tree, double-click Device. The Rack Graph tab is displayed.
2. On the Physical View sub-tab of the Rack Graph tab, right-click the slot in which a
board is to be created and select Add Board. The Add Board dialog box is displayed,
see Figure 5-1.
Figure 5-1 Adding a Board
3. In the Add Board dialog box, set the board type in accordance with the eNodeB type,
click OK. For a description of the key parameters, refer to Table 5-2.
Table 5-2 Parameters for Adding a Board
Parameter
Description
Value Range
Default Value
Board standard
This attribute sets the radio
ALL, UMTS,
N/A
mode that the board supports,
GSM, TD-SCDMA,
including UMTS, GSM,
CDMA, LTE FDD,
TD-SCDMA, CDMA, LTE
TD-LTE
FDD, and TD-LTE. Different

boards support different radio
modes. This attribute must be
configured. The radio mode
is associated with the board
automatically by the NMS in
accordance with the board
configuration. The user can
make a choice easily.
5-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 5 Physical Resource Configuration
Parameter
Description
Value Range
Default Value
Board function
This attribute sets the version
N/A
N/A
mode
information and version file
FS0
dynamically selected for the

board when it is in working
status. This attribute must be
configured. Different boards
support different function
modes. The attribute value is
generated automatically based
on certain rules.
Physical Board
It is used to distinguish different
FS0, FS3, FS4,
name
physical boards of the same
FS5, FS5A, FS5B,
logical type.
FS5C, FS3A, BPL1,

BPL1A, invalid
4. Based on BBU board planning, repeat step 2 and step 3 to create the SA, BPL or
BPL1, and PM boards.
Note:
After the boards are created, you can check them on the Rack Graph tab.
5. (Optional) Delete the created board if required.

a. Right-click the board, and select Delete Board. The Delete Operation dialog box
is displayed.
b. Enter the verification code.
c.
Click OK.
End of Steps
Result
After boards are created, a board node is also created, see Figure 5-2.
5-3
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-2 Board Node
5.1.2 Creating an RRU

This procedure describes how to create an RRU in the EMS configuration set, and how to
make the RRU type conform to the actual RRU.
Prerequisite
l
l

The eNodeB is created.
Steps
1. In the managed-element tree, double-click Device. The Rack Graph tab is displayed.
2. On the Physical View tab, click
Figure 5-3.
. The Add RRU dialog box is displayed, see
5-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-3 Adding an RRU
3. Set the parameters in the dialog box in accordance with the actual device type. For a
description of the parameters, refer to Table 5-3.
Table 5-3 RRU Parameters
Parameter
Description
Value Range
Default Value
Rack No.
RRU rack number. The number
int[1..201],
51
rises in order from 51.
[214..253]
RRU type
Managed resource
RRU type. This parameter
Must be the same
Must be the same
must be the same as the actual
as the actual RRU
as the actual RRU
RRU type.
type.
type.
ID of the Managed resource.
int[0..268435455]
51
Label of the user.
N/A
N/A
ID
User label
4. Click OK.
End of Steps
Result
After RRUs are created, RRU racks are displayed, see Figure 5-4.
5-5
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-4 RRU Racks
5.2 Configuring the SNTP

This procedure describes how to configure the IP address and time zone of the SNTP
server.
Prerequisite
l
l

The NE is created.
Steps
1. In the managed-element tree, select System Parameter and double-click Time
Configuration. The Time Configuration-List tab is displayed, and there is a default
time configuration record.
. The Time Configuration tab is displayed, see Figure 5-5. Set the SNTP
2. Click
clock parameters in accordance with the planning result. For a description of the key
5-6
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-5 Time Configuration Tab
Table 5-4 Time Configuration Parameters

Parameter
Description
Value Range
Default Value
Clock
[1..24]
24
synchronization
time synchronization period
period (s)
between the base station and
N/A
0.0.0.0
the NTP server. After a period,

the base station synchronizes
time with the NTP server
to make its time consistent
with the NTP server. This
parameter is modifiable. In
general, it is set to 24 hours.
NTP server IP
IP address of the NTP server
address
that provides standard time.

The base station obtains time
from the service once after a
time synchronization period
through the NTP protocol.
This parameter is modifiable.
For its format, refer to the
IPV4 address format, such as
10.2.30.21.
5-7
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
SNTP standby
A standby server is used to
N/A
0.0.0.0
server IP address
synchronize time when the
This parameter describes
[GMT-12:00..GMT-
GMT+8
the time zone of the base
+12:00], step: 1:00
active server is abnormal.

Time zone
station for time synchronization

between the base station and
the NTP server. ZTE devices
divide the world time zones
into 50 time zones according
to the international general
standards. A time difference
exists between every two
time zones. The default
value is GMT + 8:00, which is
modifiable.
Daylight saving
This parameter specifies
No
time supported
whether to enable the daylight
MM-DD HH:MM
saving time. When This
MM-WK-WD
parameter is set to 1, the
HH:MM
No
daylight saving time is enabled.

The default value is 0, which is
modifiable.
SNTP enabled
This parameter sets whether
No, Yes
Yes
to enable the SNTP time

synchronization function for
the base station. When This
parameter is set to 1, the SNTP
time synchronization function
is enabled. The default value
is 1, which is modifiable.
Daylight saving
This parameters sets the
[1..42], step: 1
time offset
time deviation value when the
minute
daylight saving time function is

enabled. The time granularity
is 15 minutes. The default
value is 4, which is modifiable.
3. Click
5-8
SJ-20141110151550-006|2015-04-30 (R2.0)
Caution!
After the SNTP is successfully configured, if the SNTP is available, the eNodeB
automatically synchronize its clock with the SNTP server. If the SNTP is not available,
the eNodeB time may differ from the SNTP time, and alarm records reported by the
eNodeB may differ from the LMT records.
End of Steps
5.3 Clock Source Parameter Configuration

An LTE eNodeB supports multiple clock source synchronization technologies. This
document describes the two common clock sources (GPS, and 1588) as examples.
5.3.1 Configuring the GPS Clock Source

This procedure describes how to configure the GPS clock source for an eNodeB.
Prerequisite
l
l

The NE is created.
Steps
1. In the managed-element tree, select Device > B8200(1,1) > CCC(1.1.1) (B8200 is a
BBU type, and is shown as an example) and double-click Clock Device Set. The
Clock Device Set-List tab is displayed.
2. Click
. The Clock Device Set tab is displayed, see Figure 5-6. Set the parameters
as required. For a description of the parameters, refer to Table 5-5.
5-9
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-6 Clock Device Set Tab
Table 5-5 Clock Device Set Parameters

Parameter
Description
Value Range
Default Value
Clock
Mode of a base station to
Frequency
Frequency
synchronization
be synchronized with the
synchronization,
synchronization
mode
clock reference source.
Phase
The clock synchronization
synchronization
mode is related with radio

access systems. TD-SCDMA,
LTE-TDD, and CDMA support
only phase synchronization,
and other systems support two
synchronization modes.
Clock source
Multiple clock reference
No switching,
Switching by
switching strategy
sources are configured on
Switching by
priority
the main control board. This
priority, Switching
parameter specifies the
by status
switching strategy between

clock reference sources when
one clock reference source is
faulty. Clock source priorities
are configured by the Priority
parameter of "Clock Device".
The clock source status refers
to the clock locking status of a
board when the clock source is
used.
5-10
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Clock cascading
Clock cascading output mode
Do not support
Do not support
output type
of the main control board.
cascade, GNSS
cascade
GNSS Cascading Output:
Cascading output,
The base station is the GNSS
1PPS+TOD
cascading clock reference
channel 1 output,
source of the upper-level BBU
1PPS+TOD
provided for the lower-level
channel 2 output
BBU. 1PPS + TOD Channel 1

Output: The base station is the
1PPS+TOD clock reference of
the upper-level BBU provided
for the lower-level BS BBU.
The HDMI interface on the CC
panel provides an 1PPS+TOD
channel. 1PPS + TOD Channel
2 Output: The base station is
the 1PPS+TOD clock reference
of the upper-level BBU provided
The HDMI interface on the
CC panel provides a backup
1PPS+TOD channel.
3. Click
4. In the managed-element tree, select Device > B8200(1,1) > CCC(1.1.1) > Clock
Device Set (B8200 is a BBU type, and is shown as an example) and double-click
Clock Device. The Clock Device-List tab is displayed.
5. Click
. The Clock Device tab is displayed, see Figure 5-7. Set the parameters
as required. For a description of the key parameters, refer to Table 5-6.
5-11
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-7 Clock Device Tab (GPS Clock)
Table 5-6 Clock Device Parameters

Parameter
Description
Value Range
Default Value
Clock reference
Select the corresponding clock
Frequency
GNSS clock
source category
reference source based on
synchronization:
category
different scenarios.
[GNSS clock
TD-SCDMA, LTE-TDD, and
category,
CDMA support:
1PPS+TOD clock
1: GNSS Clock Category, 2:
category, 1588
1PPS+TOD Clock Category, 4:
clock category,
1588 Clock Category.
Line clock category,
LTE-FDD and GU support:
Network Listening]
Phase
synchronization:
Line Clock Category, 4: 1588
[GNSS clock
Clock Category.
category,
LTE-TDD PICO supports:
1PPS+TOD clock
1: GNSS Clock Category,
category, 1588
4: 1588 Clock Category, 5:
clock category,
Network Listening.
Network Listening]
UMTS-PICO supports:
5-12
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Clock reference
Select the clock reference
GNSS clock
GNSS clock
source type
source type in accordance with
category: [Inner
category:
the clock reference source
GNSS, External
[Inner GNSS]
categories. For GNSS clock,
front panel GNSS,
1PPS+TOD
"Inner GNSS" can be selected
External backplane
clock category:
when GPS is accessed from
GNSS, RRU inner
[1PPS+TOD] Line
the SMA interface of the CC
GNSS]
clock category:
board. When UCI or USR
1PPS+TOD
[BITS-2MHz
is accessed from slot 5 of
clock category:
clock] 1588
BBU-2U or slot 7 of BBU-3U,
[1PPS+TOD,
clock category:
"External backplane GNSS"
Cascading
[SyncE+1588
can be selected. When a
GNSS, Backplane
clock] Network
connecting line accesses a
1PPS+TOD]
Listening:
reference source from the
Line clock category:
[Network
HDMI interface on the front
[BITS-2MHz clock,
Listening]
panel of CC, "External front
BITS-2Mbps clock,
panel GNSS" can be selected.
Line clock-local
When a connecting line
board, SyncE clock]
accesses a reference source
1588 clock
from the HDMI interface on the
category:
front panel of CC, "1PPS+TOD"
[SyncE+1588 clock,
can be selected. When UCI
1588]
Network Listening:
[Network Listening]
"Backplane 1PPS+TOD" can

be selected.
Priority
Priority of the clock reference
[1..8]
source. Number 1 sets the

highest priority. By default,
base stations select the clock
reference source with a higher
priority. When the clock
reference source is invalid,
the base stations select the
clock reference source with
a lower priority. When the
clock reference source with a
higher priority is recovered, the
base stations select the source
again.
5-13
SJ-20141110151550-006|2015-04-30 (R2.0)
6. Click
End of Steps
5.3.2 Configuring the 1588 Clock Source

This procedure describes how to configure the 1588 clock source for an eNodeB.
Prerequisite
l
l
l

The eNodeB is created.
Network transmission is configured, refer to Chapter 6 Network Transmission Configuration.
Context
IEEE 1588v2 is a clock synchronization technology based on packet network protocols,
so IP clock parameters should be configured for a 1588 clock.
Steps
1. In the managed-element tree, select Device > B8200(1,1) > CCC(1.1.1) (B8200 is a
BBU type, and is shown as an example) and double-click Clock Device Set. The
Clock Device Set-List tab is displayed.
. The Clock Device Set tab is displayed, see Figure 5-8. Set the parameters
2. Click
as required. For a description of the parameters, refer to Table 5-7.
Figure 5-8 Clock Device Set Tab
5-14
SJ-20141110151550-006|2015-04-30 (R2.0)
Table 5-7 Clock Device Set Parameters

Parameter
Description
Value Range
Default Value
Clock
Mode of a base station to
Frequency
Frequency
synchronization
be synchronized with the
synchronization,
synchronization
mode
clock reference source.
Phase
The clock synchronization
synchronization
mode is related with radio

access systems. TD-SCDMA,
LTE-TDD, and CDMA support
only phase synchronization,
and other systems support two
synchronization modes.
Clock source
Multiple clock reference
No switching,
Switching by
switching strategy
sources are configured on
Switching by
priority
the main control board. This
priority, Switching
parameter specifies the
by status
switching strategy between

clock reference sources when
one clock reference source is
faulty. Clock source priorities
are configured by the Priority
parameter of "Clock Device".
The clock source status refers
to the clock locking status of a
board when the clock source
is used.
Clock cascading
Clock cascading output mode
Do not support
Do not support
output type
of the main control board.
cascade, GNSS
cascade
GNSS Cascading Output:
Cascading output,
The base station is the GNSS
1PPS+TOD
cascading clock reference
channel 1 output,
source of the upper-level BBU
1PPS+TOD
channel 2 output
BBU. 1PPS + TOD Channel 1

Output: The base station is the
1PPS+TOD clock reference
of the upper-level BBU
BS BBU. The HDMI interface
on the CC panel provides an
1PPS+TOD channel. 1PPS
+ TOD Channel 2 Output:
The base station is the
5-15
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
1PPS+TOD clock reference of

the upper-level BBU provided
The HDMI interface on the
CC panel provides a backup
1PPS+TOD channel.
3. Click
4. Select Transmission Network > TD-LTE > IP Clock and double-click 1588 Clock
Global Parameter. The 1588 Clock Global Parameter-List tab is displayed.
5. Click
. The 1588 Clock Global Parameter tab is displayed, see Figure 5-9. Set
the parameters as required. For a description of the key parameters, refer to Table
5-8.
Figure 5-9 1588 Clock Global Parameter Tab
Table 5-8 1588 Clock Global Parameters

Parameter
Description
Value Range
Default Value
1588 clock device
This parameter sets that the
Ordinary clock,
Ordinary clock
type
base station uses the 1588
Boundary clock
clock device type.

Ordinary clock: The clock has
a single PTP port in the domain
and remains the time scale
used in the domain. It can be
used as a time source, such
as a master clock. It can be
synchronized to other clock,
such as a slave clock.
Boundary clock: The clock
has multiple PTP ports in the
5-16
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
domain and remains the time

scale used in the domain. It
can be used as a time source,
such as a master clock. It
can be synchronized to other
clock, such as a slave clock.
An ordinary clock is either in
master or slave status. One
port of the boundary clock is
the slave port, and the other
ports are master ports.
1588 link selecting
This parameter sets that the
Switch by packet
Switch by packet
mode
BS selects 1588 link mode.
loss rate, Switch by
loss rate
Set the attribute as needed.
BMC algorithm
Message
This parameter specifies the
one way, two way
two way
transmission path
transmission path of 1588 clock
[0..255]
packets. In one-way mode,

packets can only measure
one-way transmission delay.
In two-way mode, packets
can only measure two-way
transmission delay. In
frequency synchronization
mode, the path can be set to
"one-way".
PTP domain
Domain number of PTP.
number
6. Click
7. Select Transmission Network > TD-LTE > Signaling and Business and double-click
UDP. The UDP-List tab is displayed.
8. Click
. The UDP tab is displayed, see Figure 5-10. Se the parameters as required.
For a description of the key parameters, refer to Table 5-9.
5-17
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-10 UDP Tab
Table 5-9 UDP Parameters

Parameter
Description
Value Range
Default Value
Used IP layer
This parameter sets an IP link
N/A
N/A
configuration
that bears the UDP object.

The user can select one
from the configured IP layer
parameters.
9. Click
10. Select Transmission Network > TD-LTE > IP Clock and double-click IP Clock
Parameters. The IP Clock Parameters-List tab is displayed.
. The IP Clock Parameters tab is displayed, see Figure 5-11. Set the
11. Click
parameters as required. For a description of the key parameters, refer to Table 5-10.
Figure 5-11 IP Clock Parameters Tab
5-18
SJ-20141110151550-006|2015-04-30 (R2.0)
Table 5-10 IP Clock Parameters

Parameter
Description
Value Range
Default Value
Link priority
This parameter sets the link
[1..32]
This parameter the network
IPV4, IPV6,
IPV4
protocol. The PTP packet
Ethernet
priority of the IP clock. 0 sets

the highest priority while 32
is the lowest. When the 1588
link selection mode (one of the
1588 clock global parameters)
is "handover by packet loss
rate", the lower priority value
sets the higher possibility of
handing over to this link.
PTP network
protocol
format differs with the network

protocol. This parameter
should be kept the same
between the master and slave
clocks. The proper network
protocol should be selected
to suit the networking needs:
IPV4, IPV6 or Ethernet.
IP clock
This parameter the IP clock
Ethernet:[Multicast]
transmission mode
transmission mode. The
IPV4:[Multicast,
proper IP clock transmission
Unicast,
mode should be selected
Hybridcast]
to suit the network protocol
IPV6:[Multicast,
and network architecture
Unicast,
requirements. This parameter
Hybridcast]
Unicast
can be configured as multicast

only when Ethernet is selected
as the network protocol. It can
be configured as multicast,
unicast or hybridcast when
IPV4 or IPV6 is selected as the
network protocol. The IP clock
transmission mode between
the master and slave clocks
need to be the same.
5-19
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Synchronization
This parameter the IP
N/A
0.0.0.0
server IP address
address of the 1588 clock
[0..63]
46
Master, Slave
Slave
Yes, No
Yes
N/A
N/A
N/A
N/A
N/A
N/A
synchronization server. The

device serves as the server
only if it can provide the 1588
master clock functions.
DSCP
This parameter the service

quality priority of the 1588 clock
packet. It can be customized
within the value range. It is
recommended to be 46.
PTP port mode
This parameter the PTP port

mode. Whether the BTS serves
as the master or slave clock
depends on the networking
mode.
Master: The synchronizing
clock port status of a
PTP direct-connection
communication path.
Slave: The synchronized
clock port status of a
PTP direct-connection
communication path.
Enable link setup
This parameter whether to
by negotiation
enable link setup by negotiation

between the master and slave
clocks.
UDP used by 1588
This parameter the UDP link
clock
that bears the 1588 clock, that

is, the UDP link between the
master clock and the slave
clock.
Used bandwidth
This parameter is to configure
resource
the bandwidth resource. The

purpose of configuring This
parameter is traffic control.
Used 1588 clock
1588 clock global parameter
global parameter
when IP clock parameters are

configured.
5-20
SJ-20141110151550-006|2015-04-30 (R2.0)
12. Click
13. In the managed-element tree, select Device > B8200(1,1) > CCC(1.1.1) > Clock
Device Set (B8200 is a BBU type, and is shown as an example) and double-click
Clock Device. The Clock Device-List tab is displayed.
14. Click
. The Clock Device tab is displayed, see Figure 5-12. Set the parameters
Figure 5-12 Clock Device Tab (1588 Clock)
Table 5-11 Clock Device Parameters

Parameter
Description
Value Range
Default Value
Clock reference
Select the corresponding clock
Frequency
GNSS clock
source category
reference source based on
synchronization:
category
different scenarios.
[GNSS clock
TD-SCDMA, LTE-TDD, and
category,
CDMA support:
1PPS+TOD clock
category, 1588
clock category,
Line clock category,
LTE-FDD and GU support:
Network Listening]
Phase
synchronization:
Line Clock Category, 4: 1588
[GNSS clock
Clock Category.
category,
LTE-TDD PICO supports:
1PPS+TOD clock
1: GNSS Clock Category,
category, 1588
4: 1588 Clock Category, 5:
clock category,
Network Listening.
Network Listening]
UMTS-PICO supports:
5-21
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value

Clock reference
Select the clock reference
GNSS clock
GNSS clock
source type
source type in accordance
category: [Inner
category:
with the clock reference
GNSS, External
[Inner GNSS]
source categories. For the
front panel GNSS,
1PPS+TOD
GNSS clock, "Inner GNSS"
External backplane
clock category:
can be selected when GPS
GNSS, RRU inner
[1PPS+TOD] Line
is accessed from the SMA
GNSS]
clock category:
interface of the CC board.
1PPS+TOD
[BITS-2MHz
When UCI or USR is accessed
clock category:
clock] 1588
from slot 5 of BBU-2U or
[1PPS+TOD,
clock category:
slot 7 of BBU-3U, "External
Cascading
[SyncE+1588
backplane GNSS" can be
GNSS, Backplane
clock] Network
selected. When a connecting
1PPS+TOD]
Listening:
line accesses a reference
Line clock category:
[Network
source from the HDMI
[BITS-2MHz clock,
Listening]
interface on the front panel
BITS-2Mbps clock,
of CC, "External front panel
Line clock-local
GNSS" can be selected. When
board, SyncE clock]
a connecting line accesses
1588 clock
a reference source from the
category:
HDMI interface on the front
[SyncE+1588 clock,
panel of CC, "1PPS+TOD"
1588]
can be selected. When UCI
Network Listening:
[Network Listening]

"Backplane 1PPS+TOD" can
be selected.
Priority
Priority of the clock reference
[1..8]
source. Number 1 sets the

highest priority. By default,
base stations select the clock
reference source with a higher
priority. When the clock
reference source is invalid,
the base stations select the
clock reference source with
a lower priority. When the
clock reference source with a
higher priority is recovered, the
base stations select the source
again.
5-22
SJ-20141110151550-006|2015-04-30 (R2.0)
15. Click
End of Steps
5.4 Power Module Configuration

This procedure describes how to configure operation modes for the PM board.
Prerequisite
The PM board is created.
Steps
1. In the managed-element tree, select Device > B8200(1,1) > PM(1,1,14) (B8200 is a
BBU type, and is shown as an example) and double-click PM Device Set. The PM
Device Set-List tab is displayed, and there is a PM configuration record by default.
. The PM Device Set tab is displayed. Set the parameters according to the
2. Click
BTS PM operation mode, see Figure 5-13. For a description of the parameters, refer
to Table 5-12.
Figure 5-13 PM Device Set Configuration
Table 5-12 PM Device Parameters

Parameter
Description
Value Range
Default Value
Power working
Master/slave mode,
Master/slave
mode
operating mode of boards
and load-sharing
mode
with the power supply device
mode
function. Operating modes fall

into Master/Slave Mode and
Load-sharing Mode.
Master/Slave Mode: When
two PM boards are installed,
one PM board is operating in
active mode, and the other
in standby mode. When the
active PM board is damaged
5-23
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
or uninstalled, the standby PM

board supplies power.
Load-sharing Mode: Two
PM boards supply power to
the boards in the BBU shelf
simultaneously.
When only a PM board
is configured, it must be
configured to Master/slave
mode. When two PM
boards are configured,
either Master/slave mode
or load-sharing mode can be
selected.
3. Click
End of Steps
5.5 Configuring the Baseband Board Attributes

This procedure describes how to configure the baseband board attributes including the
radio mode and function mode.
Prerequisite
The BPL or BPL1 baseband board is created.
Steps
1. In the managed-element tree, select Device > B8200(1,1) (B8200 is a BBU type, and
is shown as an example) and double-click BPL or BPN. The Device Group-List tab
is displayed, and there is a configuration record for the baseband board by default.
2. Click
. The Device Group tab is displayed. Set the baseband parameters as
required, see Figure 5-14. For a description of the parameters, refer to Table 5-13.
5-24
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-14 Baseband Device Group Configuration
Table 5-13 Baseband Device Group Parameters

Parameter
Description
Value Range
Default Value
Board Radio Mode
The BPL or BPL1 board
LTE FDD[16], LTE
LTE TDD[32]
supports only LTE FDD or LTE
TDD[32]
TDD mode.
Board Function
Different boards support
Mode
different function modes.
Radio mode: 16
LTE-IR,
Function mode: [1:
100663305
LTE-FDD single
mode]
Default value: 1
Radio mode: 32
Function mode:
[100663297: LTE-IR,
100663305: LTEIR(IQ Compressed)]
Default value:
100663297
3. Click
End of Steps
5.6 Configuring the Optical Port Attributes of a

Baseband Board
This procedure describes how to configure the optical port attributes of a baseband board,
including operation mode, connection mode and optical port bit rate.
Prerequisite
The baseband board is created.
5-25
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
1. In the managed-element tree, select Device > B8200(1,1) > BPL or BPN (B8200 is
a BBU type, and is shown as an example) and double-click Optical Port Device Set.
The Optical Port Device Set-List is displayed, and there is a configuration record for
the optical device set by default.
. The Optical Port Device Set tab is displayed. Set the optical port
2. Click
parameters of the baseband board as required, see Figure 5-15. For a description of
the parameters, refer to Table 5-14.
Figure 5-15 Optical Port Device Set Configuration
Table 5-14 Optical Port Device Set Configuration

Parameter
Description
Value Range
Default Value
Working mode of
Load-sharing mode
Load-sharing
network switching
working mode of IQ switching.
[1]
mode [1]
100000
It identifies the IQ switching

mode of a board. Only the
board that has the IQ switching
function can be configured with
This parameter. At present,
only load sharing mode is
supported.
Fiber delay timing
This parameter sets the fiber
[50000..300000]
advance (LTE
delay timing advance (LTE IR).
step 3125
Fiber delay
[50000..300000]
timing advance
fiber delay timing advance
step 3125
(TD-SCDMA
(TD-SCDMA IR).
IR)(ns)
250000
IR)(ns)
3. Click
5-26
SJ-20141110151550-006|2015-04-30 (R2.0)
4. In the managed-element tree, select Device > B8200(1,1) > BPL or BPN > Optical
Port Device Set (B8200 is a BBU type, and is shown as an example) and double-click
Optical Port Device. The Optical Port Device-List tab is displayed. There are three
configuration records for the optical port device, corresponding to the three optical
ports of the BPL board.
. Optical Port Device tab is displayed. Set parameters as required, see
5. Click
Figure 5-16. For a description of the parameters, refer to Table 5-15.
Figure 5-16 Optical Port Device Configuration
Table 5-15 Optical Port Device Parameters

Parameter
Description
Value Range
Default Value
Connected board
This parameter sets the serial
long[0...5]
port No.
number of a physical port.
N[0],Y[1]
N[0]
It identifies the number of

optical interface devices.
This parameter is generated
automatically by the NMS. It
does not need to be configured
and cannot be modified.
RU board or not
This parameter sets whether

the optical interface device
belongs to the RU board or
not. It is used to verify that
the board is an RRU board.
This parameter is generated
automatically by the NMS. It
and cannot be modified.
5-27
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Ir line bit rate
This parameter sets the rate
None RU board:
None RU board:
of a physical port (matched
[1.25G, 2.5G, 3G,
[1.25G]
with the optical module type
4G, 6G, 110G]
RUboard: [Self
and the SFP port type). This
RU board: [1.25G,
adaptive]
parameter is used to calculate
2.5G, 3G, 4G, 6G,
the number of IQs that an
10G, Self adaptive]
optical interface can bear. It is

generated automatically by the
NMS. The user can modify it as
required. For example, if the
optical module type is 6G, This
parameter value is set to 6G.
Protocol type of
None RU board:
None RU
optical module
protocol type that is used by
[PHY CPRI, PHY
board:[PHY CPRI]
the optical module. It describes
LTE IR, PHY
RU board: [APP
whether the protocol used by
OBSAI, PHY
ZTE]
the optical module is a physical
OBRIPHY , PHY
protocol or an application
GBRS, PHY
protocol. If the board is an
TD-SCDMAIR]
RRU board, the protocol type is
RU board:[APP
set to an application protocol,
Manufacturer
such as APP ZTE, APP LTE IR,
customized, APP
APP TD-SCDMAIR, and APP
LTE IR, APP
OBRI. If the board is not an
TD-SCDMAIR,
RRU board, the protocol type
APP OBRI, Self
is set to a physical protocol,
adaptive]
such as PHY CPRI, PHY

LTE IR, PHY OBSAI, PHY
OBRIPHY, PHY GBRS, and
PHY TD-SCDMAIR.
6. Click
End of Steps
5.7 Configuring the RRU Attributes

This procedure describes how to configure radio mode and optical port attributes for an
RRU.
Prerequisite
The RRU is created.
5-28
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
1. In the managed-element tree, select Device > RRU and double-click R8962 (R8962 is
an RRU type, and is shown as an example). The Device Group-List tab is displayed.
There is a configuration record for the device group by default.
2. Click
. The Device Group tab is displayed. Set parameters based on the RRU
basic attributes, see Figure 5-17. For a description of the parameters, refer to Table
5-16.
Figure 5-17 RRU Device Group Configuration
Table 5-16 RRU Device Group Parameters

Parameter
Description
Value Range
Default Value
Board Radio Mode
This parameter is the same
LTE TDD[32]
LTE TDD[32]
as that of the baseband board

connected to the RRU.
Board Function
This parameter is the same
Radio mode: 32
LTE-
Mode
as that of the baseband board
Function mode:
IR,100663305
connected to the RRU.
[100663297: LTEIR, 100663305:

LTE-IR(IQ
Compressed)]
Default value:
100663297
Note:
The RRU board radio and function modes must be consistent with those of the
connected baseband board. For example, if the R8962(51.1.1) is connected to BPL
(1.1.3), the radio and function modes of R8962(51.1.1) are consistent with those of
BPL(1.1.3) in 5.5 Configuring the Baseband Board Attributes.
5-29
SJ-20141110151550-006|2015-04-30 (R2.0)
3. Click
4. In the managed-element tree, select Device > RRU > R8962 (R8962 is an RRU type,
and is shown as an example) and double-click Optical Port Device Set. The Optical
Port Device Set-List tab is displayed. There is a configuration record for the optical
port device group set by default.
5. Click
. The Optical Port Device Set tab is displayed. Set parameters as required,
see Figure 5-18. For a description of the parameters, refer to Table 5-16.
Figure 5-18 RRU Optical Port Device Set Configuration
Table 5-17 RRU Optical Port Device Set Parameters

Parameter
Description
Value Range
Default Value
Uplink connection
This parameter sets the uplink
Single up-link
Single up-link
mode
connection mode. It describes
optical line, double
optical line
the connection mode between
master/slave
the optical device in the
optical lines,
optical interface device set
multiple load-
of the RRU board with the
sharing optical lines
upper-layer device (including

single-fiber uplink, dual-fiber
active/standby, multiple-fiber
load sharing). Only the RRU
board displays This parameter.
Single-fiber uplink: The optical
interface device of the RRU
board is connected to the
upper-layer device through a
pair of optical fibers.
Dual-fiber active/standby: The
optical interface device of the
RRU board is connected to the
upper-layer device through two
pairs of optical fibers. Only one
pair of optical fibers bears IQ.
5-30
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Multiple-fiber load sharing: The

optical interface device of the
RRU board is connected to
the upper-layer device through
two pairs of optical fibers (at
present, only two pairs of
optical fibers are supported).
Both pairs of optical fibers can
bear IQ.
6. Click
7. In the managed-element tree, select Device > RRU > R8962 > Optical Port Device
Set (R8962 is an RRU type, and is shown as an example) and double-click Optical
Port Device. The Optical Port Device-List tab is displayed. There are three
configuration records for the optical port device by default.
8. Click
. The Optical Port Device tab is displayed. Set parameters as required, see
Figure 5-19. For a description of the parameters, refer to Table 5-16.
Figure 5-19 RRU Optical Port Device Configuration
Table 5-18 RRU Optical Port Device Parameters

Parameter
Description
Value Range
Default Value
Protocol type of
None RU Board:
None RU Board:
optical module
protocol type that is used by
[PHY CPRI, PHY
[PHY CPRI], RU
the optical module. It describes
LTE IR, PHY
Board: [APP ZTE]
whether the protocol used by
OBSAI, PHY OBRI,
the optical module is a physical
PHY GBRS, PHY
protocol or an application
TD-SCDMAIR].
protocol.
RU Board: [APP
If the board is an RRU board,
Manufacturer
the protocol type is set to an
customized, APP
5-31
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
application protocol, such as
LTE IR, APP
APP ZTE, APP LTE IR, APP
TD-SCDMAIR,
TD-SCDMAIR, and APP OBRI.
APP OBRI,Self
If the board is not an RRU
adaptive]
Default Value
board, the protocol type is

set to a physical protocol,
such as PHY CPRI, PHY
LTE IR, PHY OBSAI, PHY
OBRIPHY, PHY GBRS, and
PHY TD-SCDMAIR.
9. Click
End of Steps
5.8 BTS Auxiliary Peripheral Device Configuration

This procedure describes how to configure the antenna instance, optical fiber and RF cable
connection, and optical fiber topology.
5.8.1 Querying Antenna Attributes

Antenna attributes are referenced when an antenna entity is created. This procedure
describes how to query the antenna attribute parameters.
Prerequisite
The BBU and RRU device are configured.
Steps
1. In the managed-element tree, select Device > BTS Auxiliary Peripheral Device
> Antenna Service and double-click Antenna Attribute Object. The Antenna
Attribute Object-List tab is displayed, see Figure 5-20.
5-32
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-20 Antenna Attribute Object-List
2. Double-click any record in the list, the antenna detailed information in this record can
be queried, see Figure 5-21.
Figure 5-21 Antenna Detailed Information
For a description of the parameters in the antenna attribute list, see Figure 5-22.
5-33
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 5-22 Antenna Parameters
3. If the antenna attribute objects cannot satisfy the customer requirements, and the
customized antenna parameters are needed, click
. The Antenna Attribute
Object tab is displayed, see Figure 5-23. For a description of the parameters, refer
to Table 5-19.
Figure 5-23 Antenna Attribute Object Configuration
Table 5-19 Antenna Attribute Object Parameters

Parameter
Description
Value Range
Default Value
Object ID of
unsigned
N/A
antenna attribute
object ID of an antenna.
long[1..600]
This parameter provides a

Relative Distinguished Name
(RDN). It must be unique.
This parameter does not need
to be configured and can
be modified. It is generated
5-34
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
string[0..255]
The antenna type should be
Intelligent antenna
Distributed
selected according to the
circle array,
antenna
antenna used by the customer.
intelligent antenna
automatically starting from 1 by

the NMS.
Antenna
This parameter sets the name
manufacturer
of the intelligent antenna

vendor.
Antenna Type
line array,
distributed antenna,
and intelligent dual
polarized antenna
Antenna Gain
long[0..255]
long[0..65535]
75
long[1..8]
string[1..40]
General Model
intelligent antenna gain.

Antenna Gap

antenna interval (for line array)
or radius (for circle array).
Number of antenna
units
number of antenna array

units. It should be specified
according to the antenna type
and quantity used by the
customer.
Antenna model

antenna type.
4. Click
End of Steps
5.8.2 Creating an Antenna Entity

This procedure describes how to create an physical antenna entity.
Prerequisite
The BTS devices are configured.
Steps
1. In the managed-element tree, select Device > BTS Auxiliary Peripheral Device >
Antenna Service and double-click Antenna Entity Object. The Antenna Entity
5-35
SJ-20141110151550-006|2015-04-30 (R2.0)
Object-List tab is displayed. Each antenna must be configured with an antenna

instance.
2. To modify the exist antenna entity, click
. The Antenna Entity Object tab is
displayed. Set parameters as required, see Figure 5-24. For a description of the
Figure 5-24 Antenna Entity Object Configuration
Table 5-20 Antenna Entity Object Parameters

Parameter
Description
Value Range
Default Value
Object ID of
This parameter sets the object
[1..576]
N/A
antenna entity
ID of the antenna entity. This

parameter provides a Relative
Distinguished Name (RDN) that
is used to identify the number
of antenna entities. It must
be unique. This parameter
and cannot be modified. It
is generated automatically
starting from 1 by the NMS.
5-36
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Antenna entity No.
This parameter sets the number
[1..65535]
N/A
N/A
A coverage scenario should
Indoor, Urban,
Urban
be selected according to the
DenseUrban,
coverage mode of the wireless
SubUrban,
signal.
HighWay, HighRail
An RET device type should
Non RET,
be selected according to the
Uni-antenna RET,
device type connected with the
Uni-direction TMA,
antenna entity.
Continuous power
of a configured antenna entity.

It must be unique and cannot
be modified.
Used antenna
This parameter provides the
attribute
used antenna attribute. It is

used to identify the antenna
attribute of the antenna
entity. This parameter can be
configured by selecting any
suitable one of the already
configured antenna attributes.
Coverage scenario
RET Device type
Non RET
antenna system,
Bi-direction TMA,
LNA, Multi-antenna
RET
3. Click
End of Steps
5.8.3 Configuring an RF Cable

The RF cable configuration is used for configuring the mapping relation between
the antenna TX/RX port and the antenna port, affecting the IR antenna group object
configuration (the relation between the RRU RF port number and the antenna entity).
This procedure describes how to configure the RF cable resources based on different
RRU types.
Prerequisite
l
l
The antenna entity is configured.

The RRU is configured.
5-37
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
Cable and double-click RF Cable. The RF Cable-List tab is displayed.
2. To create a new RF cable, click
. The RF Cable tab is displayed, see Figure 5-25.
Figure 5-25 RF Cable Configuration
Table 5-21 RF Cable Parameters

Parameter
Description
Value Range
Default Value
Connected antenna
N/A
N/A
N/A
N/A
N/A
N/A
antenna connected with the

RF cable. This parameter
references antEntityNo of the
object AntEntity.
Connected TMA
This parameter sets the TMA
device
connected with the RF cable.

This parameter references
tmaNo of the object Tma.
Connected RF port
This parameter sets the RF

port connected with the RF
cable. It is the RF port of RU.
This parameter references
portNo of the object RfDevice.
3. Click
End of Steps
5-38
SJ-20141110151550-006|2015-04-30 (R2.0)
5.8.4 Configuring an Ir Antenna Group

The Ir antenna group object is used for associating the RRU with the antenna entity. This
procedure describes how to adding an Ir antenna group object.
Prerequisite
l
l
The physical antenna entity is configured.

The RF cable is configured.
Steps
Antenna Service and double-click Ir Antenna Group Object. The Ir Antenna Group
Object-List tab is displayed.
. The Ir Antenna Group Object
2. To create a new Ir antenna group object, click
tab is displayed, see Figure 5-26. For a description of the parameters, refer to Table
5-22.
Figure 5-26 Ir Antenna Group Object Configuration
Table 5-22 Ir Antenna Group Object Parameters

Parameter
Description
Value Range
Default Value
long[1...8]
N/A
N/A
N/A
N/A
Ir antenna group
This parameter sets the Ir
number
antenna group number.
Used antenna

antenna entity that is used by
this Ir antenna group.
Connected RRU
board
This parameter sets the RRU

to which this Ir antenna group
belongs.
3. Click
End of Steps
5-39
SJ-20141110151550-006|2015-04-30 (R2.0)
5.8.5 Configuring a Fiber Cable

This procedure describes how to create the fiber device between the BPL and RRU.
Prerequisite
l
l
The BPL board is created.

The RRU is created.
Steps
Cable and double-click Fiber Cable. The Fiber Cable-List tab is displayed.
. The Fiber Cable tab is displayed,
2. On the displayed Fiber Cable-List tab, click
see Figure 5-27. For a description of the parameters, refer to Table 5-23.
Figure 5-27 Fiber Cable Configuration
Table 5-23 Fiber Cable Parameters

Parameter
Description
Value Range
Default Value
Upper level optical
This parameter sets the upper
N/A
N/A
port in topology
level port connected with
structure
optical fiber. Generally it is the
N/A
N/A
BPL optical port.

Lower level optical
This parameter sets the lower
port in topology
level port connected with
structure
optical fiber. Generally it is the

RRU optical port.
3. Click
End of Steps
5-40
SJ-20141110151550-006|2015-04-30 (R2.0)
Example
Using the connection of the No. 0 port to R8882268(51.1.1) as an example, to create a
fiber cable configuration.
1. Select "Fiber:BPL(1.1.6):0" from the Upper level optical port in topology structure
drop-down list.
2. Select "Fiber:R8882268(51.1.1):0" from the Lower level optical port in topology
structure.
3. Click
, a fiber cable configuration record is displayed on the Fiber Cable-List tab.
5-41
SJ-20141110151550-006|2015-04-30 (R2.0)
5-42
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 6
Network Transmission
Configuration
Network transmission should be configured from the bottom layer to the top layer in
accordance with the protocol stack on the interface. Figure 6-1 shows the S1-/X2-interface
protocol stack designed by ZTE.
Figure 6-1 S1-/X2-Interface Protocol Stack
Figure 6-2 shows the configuration structure of eNodeB transmission resources.
6-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-2 Transmission Resource Configuration Structure
Table of Contents
Configuring a Physical Layer Port...............................................................................6-2
IP Transmission Configuration....................................................................................6-5
Bandwidth Configuration ............................................................................................6-9
Signaling and Business Configuration ......................................................................6-12
Configuring a Static Routing .....................................................................................6-16
Configuring an OMC Channel...................................................................................6-18
6.1 Configuring a Physical Layer Port

This procedure describes how to configure Ethernet parameters in accordance with site
transmission planning.
Prerequisite
l
l

The NE is created.
Steps
1. In the managed element tree, select Transmission Network > TD-LTE > Physical
Hosting and double-click Physical Layer Port. The Physical Layer Port-List tab is
displayed.
2. Click
. The Physical Layer Port tab is displayed, see Figure 6-3. Set the
6-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 6 Network Transmission Configuration
Figure 6-3 Physical Layer Port Tab
Table 6-1 Physical Layer Port Parameters

Parameter
Description
Value Range
Default Value
Ethernet
Transmission
This attribute sets the physical
E1, T1, STM-1,
medium
medium used to configure the
Ethernet, Relay
physical layer port.
port, LIPA port
Connection
This attribute sets the opposite NE
RNC/BSC/CN/M-
RNC/BSC/CN-
object
connected with this object. In base
ME, SDR, Third
/MME
station cascading, it is set to SDR for
Party
upper level. If it is set to Third party

device, it means that the local base
station provides data transmission
channel for third-party devices in the
case of ATM+FE cascading.
Used
This attribute sets the associated
Ethernet
Ge device, that is, the Ethernet
N/A
N/A
used by the local port. It is used

in the IP transmission mode. It is
automatically generated by the NMS
in accordance with the LDN of the
parent object.
3. Click
beside Ethernet configuration parameter. The Ethernet configuration
parameter dialog box is displayed, see Figure 6-4. Set the parameters as required.
6-3
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-4 Ethernet Configuration Parameter Dialog Box
Table 6-2 Ethernet Configuration Parameters

Parameter
Description
Value Range
Default Value
Working mode
This attribute sets the working
Electrical port
Electrical port
mode of the backup Ethernet
self-adaptive,
self-adaptive
port.
Electrical port
10 Mbps FDT,
Electrical port 100
Mbps FDT, Optical
port 100 Mbps
FDT, Optical port
1000 Mbps FDT,
Optical port 1000
Mbps self-adaptive,
Optical port 10000
Mbps FDT]
6-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Transmitting
Transmission bandwidth if
[100..1000000]
100
bandwidth (Mbps)
Ethernet is used.
Receiving
Receiving bandwidth if Ethernet
[100..1000000]
100
bandwidth (Mbps)
is used. The value (in Mbps)

differs from working modes.
10 Mbps full duplex: [0..10]
Self-adaptive: [0..100]
4. Click OK.
5. Click
End of Steps
6.2 IP Transmission Configuration

6.2.1 Configuring an Ethernet Link
This procedure describes how to configure an Ethernet link.
Prerequisite
The physical layer port is configured.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > IP
Transport and double click Ethernet Link Layer. The Ethernet Link Layer-List tab
is displayed.
. The Ethernet Link Layer tab is displayed, see Figure 6-5. Set the
2. Click
6-5
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-5 Ethernet Link Layer Tab
Table 6-3 Ethernet Link Parameters

Parameter
MTU (Byte)
Description
Value Range
Default Value
[256..1800]
1500
N/A
N/A
N/A
N/A
maximum transmitted bytes

of each Ethernet link layer
packet.
Used physical layer
port
transmission media used by

the physical layer port object
and it must be STM-1.
Used LACP
This parameter sets the LACP
aggregation group
Aggregation Port that bears

Ethernet.
3. Click
beside VLAN ID. The VLAN ID dialog box is displayed. Configure the
VLAN ID in accordance with network planning.
4. Click OK.
5. Click
End of Steps
6.2.2 Configuring the IP layer

This procedure describes how to configure the IP layer parameters.
Prerequisite
l
l
The physical layer port is configured.

The Ethernet link is configured.
6-6
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE
> IP Transport and double-click IP Layer Configuration.
The IP Layer
Configuration-List tab is displayed.
2. Click
. The IP Layer Configuration tab is displayed, see Figure 6-6. Set the
Figure 6-6 IP Layer Configuration Tab
Table 6-4 IP Layer Parameters

Parameter
Description
Value Range
Default Value
Object ID of IP layer
This parameter identifies the
[1..20]
configuration
number of IP configurations.
[0..19]
This parameter provides a

Relative Distinguished Name
(RDN). This parameter does
not need to be configured
and cannot be modified. It
is generated automatically
starting from 1 by the NMS.
The value is fixed to 1.
IP parameter link
This parameter indentifies the
number
IP configuration number. It
describes the IP configuration
number in the database.
This number is unique in the
database. The user defines
the value range.
6-7
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
IP address
This parameter sets the IP
N/A
N/A
N/A
255.255.0.0
N/A
0.0.0.0
N/A
N/A
address of a base station.

When the PPP link is used,
the IP address cannot be
configured. The IP address
of a base station can be an
IPv4 address or an IPv6 address. An IPv4 address is in
the dotted decimal notation
format, such as 10.0.0.1. An
IPv6 address is in the colon
hexadecimal notation format,
such as 2011:0db8:85a3:00
00:1319:8a2e:0370:7366. It
cannot be configured with the
IP address of the 192.254
network segment and the
127 network segment. It is
one of the interconnection
parameters.
Network mask

subnet mask of an IP address.
Only IPv4 address can be
configured.
Gateway IP

IP address of a gateway.
Only IPv4 address can be
configured. An IPv4 address is
in the dotted decimal notation
format, such as 10.0.0.1.
Used Ethernet link

Ethernet link that bears IP
service. It describes which
Ethernet link bears the IP
service. For example, two
Ethernet links 0 and 1 are
configured. If the user wants
to use link 0, he can select
EthernetLinkNo = 0 from the
drop-down list.
6-8
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
VLAN ID
This parameter sets the VLAN
[1..4094]
N/A
Used Ethernet Link Group.
N/A
N/A
X2 self-setup
This parameter is valid only
No, Yes
N/A
enabled
when the IP address is used for
ID. It is the same as a VLAN in

refEthernetLink. The user can
set the attribute. He can select
one VLAN from the configured
VLANs.
Used Ethernet Link
Group
LTE transmission. It is used for

the LTE X2 self-establishment.
3. Click
End of Steps
6.3 Bandwidth Configuration

6.3.1 Configuring a Bandwidth Resource Group
This procedure describes how to create an IP bandwidth resource group and how to
manage IP bandwidth resources.
Prerequisite
The IP layer parameters are configured.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > Bandwidth
Assignment and double-click Bandwidth Resource Group. The Bandwidth
Resource Group-List tab is displayed.
2. Click
. The Bandwidth Resource Group tab is displayed, see Figure 6-7. Set
6-5.
6-9
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-7 Bandwidth Resource Group Tab
Table 6-5 Bandwidth Resource Group Parameters

Parameter
Description
Value Range
Default Value
Bandwidth resource
[0..15]
group number
bandwidth resource group
N/A
N/A
[1..1000]
N/A
[1..1000]
N/A
number, which must be unique

in the same bearer mode. In
the Ethernet bearer mode, This
parameter value can be set
from 0 to 5. In the PPP bearer
mode, This parameter value
can be set from 0 to 15.
Used Ethernet link
This parameter sets on which

Ethernet link the bandwidth
allocation rule is applied. The
user needs to configure an
Ethernet link first if he wants
to configure the bandwidth
resource group that is borne
on the Ethernet link.
Maximum
bandwidth of egress
maximum available bandwidth
(Mbps)
of egress. If an Ethernet link is

used, the maximum available
bandwidth of egress must be
configured. If a PPP link is
used, the maximum available
bandwidth of egress does not
need to be configured.
Maximum
Maximum available bandwidth
bandwidth of
of ingress.
ingress (Mbps)
6-10
SJ-20141110151550-006|2015-04-30 (R2.0)
3. Click
End of Steps
6.3.2 Configuring Bandwidth Resources

This procedure describes how to configure IP bandwidth resources.
Prerequisite
The IP bandwidth resource group is configured.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > Bandwidth
Assignment > Bandwidth Resource Group and double-click Bandwidth Resource.
The Bandwidth Resource-List tab is displayed.
. The Bandwidth Resource tab is displayed, see Figure 6-8. Set the
2. Click
Figure 6-8 Bandwidth Resource Tab
Table 6-6 Bandwidth Resource Parameters

Parameter
Description
Value Range
Default Value
Bandwidth
[1..6]
resource number
bandwidth resource number,

which the user can define. This
parameter value can be set
through 1 to 6.
6-11
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Transmission
This parameter is used
[0..100]
100
bandwidth weight
to configure transmission
bandwidth weight. The
maximum bandwidth of
egress of a bandwidth
resource group multiplied by
transmission bandwidth weight
is the minimum guaranteed
bandwidth.
3. Click
End of Steps
6.4 Signaling and Business Configuration

6.4.1 Configuring SCTP Parameters
This procedure describes how to configure the SCTP parameters.
Prerequisite
The IP parameters are configured.
Context
The SCTP supports all-IP transmission. The control-plane NBAP signaling in the radio
network layer can be carried by an IP network. A maximum of 36 records can be
configured for the SCTP parameters. The local IP address and the remote IP address
must be paired. After the SCTP parameters are configured, the system automatically
generates the corresponding S1AP parameters or X2AP parameters.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > Signaling
and Business and double-click SCTP. The SCTP-List tab is displayed.
. The SCTP tab is displayed, see Figure 6-9. Set the parameters as
2. Click
required. For a description of the key parameters, refer to Table 6-7.
6-12
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-9 SCTP Tab
Table 6-7 SCTP Parameters

Parameter
Description
Value Range
Default Value
SCTP link number
This parameter sets the SCTP
[0..63]
[0..65535]
N/A
N/A
N/A
N/A
association link number. The

attribute value ranges from 0 to
63. It is user-defined within the
value range.
Local port number
This parameter sets the local

port number of an SCTP
association link. It is an
interconnection parameter.
Used IP layer
This parameter sets IP-layer
configuration
configuration that bears SCTP

association. SCTP can get the
IP address of the local end.
Used bandwidth
resource
This parameter is used to

configure the bandwidth
resource used for SCTP.
For SCTP, the bandwidth
resource to be used cannot be
configured.
6-13
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Remote port
This parameter sets the remote
[0..65535]
number
port number of an SCTP
N/A
0.0.0.0
[0..3]
[2..6]
[0..63]
46
association link. It is an
interconnection parameter.
Remote address
This parameter sets the remote

IP address of SCTP association. It is an interconnection
parameter. The remote IP address can be an IPv4 address
or an IPv6 address. An IPv4
address is in the dotted decimal notation format, such as
10.0.0.1. An IPv6 address is in
the colon hexadecimal notation
format, such as 2011:0db8:85
a3:0000:1319:8a2e:0370:7366.
Primary path
This parameter corresponds
number
to four IP addresses in the

association. It sets that one
of the four IP addresses is
selected as the primary path.
Number of
in-and-out streams
number of incoming and

outgoing streams of an SCTP
association. A maximum of six
incoming and outgoing streams
can be configured.
DSCP

service model configuration.
For various scenarios, different
DSCPs are chosen. The
attribute value ranges from 0 to
63.
3. Click
End of Steps
6.4.2 Configuring DSCP Mapping

This procedure describes how to configure service and DSCP mapping to ensure UE to
successfully access services.
6-14
SJ-20141110151550-006|2015-04-30 (R2.0)
Prerequisite
l
l
IP transmission is configured.
Bandwidth resources are configured.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > Signaling
and Business and double-click Service and DSCP Mapping. The Service and
DSCP Mapping-List tab is displayed.
2. Click
. The Service and DSCP Mapping tab is displayed, see Figure 6-10. Set
the parameters as required. For a description of the parameters, refer to Table 6-8.
Figure 6-10 Service and DSCP Mapping Tab
Table 6-8 DSCP Mapping Parameters

Parameter
Description
Value Range
Default Value
Used IP layer
This parameter configures
N/A
N/A
configuration
the IP parameters of bearer
N/A
N/A
services. If the IpLayerConfig

MO is configured, This
parameter must be configured.
Used bandwidth
This parameter configures
resource
the bandwidth resources

of bearer services. If the
BandwidthResourceMO is
configured, This parameter
must be configured.
6-15
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
LTE TDD service
N/A
N/A
DSCP mapping
mapping rules between the
N/A
N/A
LTE TDD service type and

DSCP. It sets the QoS priority
that the IP layer uses to bear
the corresponding services.
If DSCP is set to 0xFF, the
IP layer does not bear the
corresponding services.
Operator

operator to which the
bandwidth rules are allocated.
If This parameter is not
set, bandwidth control is
not implemented between
operators.
3. Click
End of Steps
6.5 Configuring a Static Routing

When IP packets cannot be sent to the destination network through the default gateway,
a static routing is required to determine the next hop. The destination network address
and next-hop gateway address must be configured for a static routing. This procedure
describes how to configure a static routing in accordance with transmission planning.
Prerequisite
The IP parameters are configured.
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE > Static
Route and double-click Static Routing Configuration.
The Static Routing
Configuration-List tab is displayed.
2. Click
. The Static Routing Configuration tab is displayed, see Figure 6-11. Set
6-9.
6-16
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 6-11 Static Routing Configuration Tab
Table 6-9 Static Routing Parameters

Parameter
Description
Value Range
Default Value
Static routing
This parameter sets the static
[0..99]
number
route number. It specifies the
N/A
0.0.0.0
N/A
255.255.255.0
number of a static route in the

base station. This number is
unique in the base station. It is
user-defined within the value
range.
Destination IP
This parameter sets the des-
address
tination network IP address

of a static route. It can be an
IPv4 or an IPv6 address. An
IPv4 address is in the dotted
decimal notation format, such
as 10.0.0.1. An IPv6 address
is in the colon hexadecimal
notation format, such as
2011:0db8:85a3:0000:1319:8
a2e:0370:7366.
Network mask

destination network mask of a
static route.
6-17
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Next hop IP
This parameter sets the gate-
N/A
0.0.0.0
address
way address configuration
[0..7]
N/A
N/A
[1..4094]
N/A
of the next hop. It can be

an IPv4 address or an IPv6
address. An IPv4 address is
in the dotted decimal notation
format, such as 10.0.0.1. An
IPv6 address is in the colon
hexadecimal notation format,
such as 2011:0db8:85a3:0000:
1319:8a2e:0370:7366.
Routing priority
This parameter sets the priority

of an IP route. 0 sets the
highest priority.
Used Ethernet link

Ethernet link that bears IP.
VLAN ID
This parameter sets the VLAN

ID. It is the same as a certain
VLAN ID in refEthernetLink.
3. Click
End of Steps
6.6 Configuring an OMC Channel

This procedure describes how to create an OMC channel for an eNodeB, and how to
configure the destination address of operation and maintenance information transmitted
by an eNodeB and the link parameters.
Prerequisite
l
l
The IP layer is configured.

Bandwidth is assigned.
Context
eNodeBs and the OMC communicate with each other through IP packets, and the OMC
needs to access an eNodeB through a public network interface to configure and manage
the eNodeB, so OMC parameters such as an IP address used for eNodeB access from
the OMC must be configured.
6-18
SJ-20141110151550-006|2015-04-30 (R2.0)
Steps
1. In the managed-element tree, select Transmission Network > TD-LTE and
double-click OMC Channel. The OMC Channel-List tab is displayed.
2. Click
. The OMC Channel tab is displayed, see Figure 6-12. Set the parameters
Figure 6-12 OMC Channel Tab
Table 6-10 OMC Channel Parameters

Parameter
Description
Value Range
Default Value
OMC interface link
[0..7]
number
number of an Itf-UniBTS
channel, which is unique and
cannot be repeated. It can
be defined by the user within
the value range. The NE is
connected to the NMS only
through one channel at the
same time.
6-19
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Interface type of
This parameter sets that
IPINIP, IPOA,
Independent
operation and
Itf-UniBTS can be used in
Independent
networking
maintenance
IPINIP, IPOA (in ATM mode) or
networking
IP (in independent networking).

The O&M packets can use
IPINIP or IPOA (ATM) mode
through RNC/BSC resolution
transferring. The O&M packets
can use the independent
networking mode without
RNC/BSC resolution.
OMC server IP
N/A
0.0.0.0
N/A
255.255.255.255
[0..63]
46
N/A
N/A
N/A
N/A
address of the OMC server.

It must be filled in when
itfUniBtsType is set to the
independent networking mode.
OMC subnet mask
This parameter sets the subnet

mask of the OMC server. It is
used when tfUniBtsType is set
to the independent networking
mode.
DSCP

transmission quality priority
of O&M packets. It is
defined by the user. It is
recommended to set the
attribute to "46:EF service,
accelerated forwarding,
minimum delay, and maximum
flow".
Used IP layer
This parameter sets that IP
configuration
layer configurations are used.

The IpLayerConfig object is
involved.
Used bandwidth
This parameter is
resource
used to configure the

bandwidth resource. The
BandwidthResource object is
involved.
6-20
SJ-20141110151550-006|2015-04-30 (R2.0)
3. Click
End of Steps
6-21
SJ-20141110151550-006|2015-04-30 (R2.0)
6-22
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 7
Radio Parameter
Configuration
Table of Contents
Configuring TD-LTE Global Parameters .....................................................................7-1
Configuring Baseband Resources ..............................................................................7-3
S1AP Configuration....................................................................................................7-5
Configuring a Serving Cell..........................................................................................7-6
7.1 Configuring TD-LTE Global Parameters

This procedure describes how to configure LTE TDD global parameters.
Prerequisite
The eNodeB physical resources are configured.
Steps
1. In the managed-element tree, select Radio Parameter and double-click TD-LTE. The
TD-LTE-List tab is displayed.
. The TD-LTE tab is displayed, see Figure 7-1. Set the parameters as
2. Click
required. For a description of the key parameters, refer to Table 7-1.
7-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 7-1 TD-LTE Tab
Table 7-1 TD-LTE Parameters

Parameter
Description
Value Range
Default Value
LTE TDD ID
MO instance Identity. A
int[0..1048575]
N/A
Distinguished Name (DN) is

used to uniquely identify an
MO within a name space. A
DN is built from a series of
"name components", referred
to as Relative Distinguished
Names (RDNs). See 3GPP TS
32.300.
PLMN
PLMN
N/A
N/A
Holdover Time-Out
Holdover time-out switch
enum[0: Disable, 1:
Enable[1]
Switch
Enable]
Holdover Time-Out
Holdover time-out threshold
[0..240]
60
Threshold (min)
3. Click
End of Steps
7-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 7 Radio Parameter Configuration
7.2 Configuring Baseband Resources

Baseband resources must be configured for radio signal transmission and receiving.
This procedure describes how to configure baseband resources in accordance with radio
resource planning.
Prerequisite
LTE TDD global parameters are configured.
Steps
1. In the managed-element tree, select Radio Parameter > TD-LTE > Resource
Interface Configuration and double-click Baseband Resource. The Baseband
Resource-List tab is displayed.
. The Baseband Resource tab is displayed, see Figure 7-2. Set the
2. Click
Figure 7-2 Baseband Resource Tab
7-3
SJ-20141110151550-006|2015-04-30 (R2.0)
Table 7-2 Baseband Resource Parameters

Parameter
Description
Value Range
Default Value
Baseband
MO instance Identity, A
[1..9999]
Resource
Configuration ID
used to uniquely identify a
Associated to the
N/A

Names (RDNs). See 3GPP TS
32.300.
Ir Antenna Group
Ir antenna group object
Object
created Ir antenna
group
RF Port Object
RF port object.
Associated to the
N/A
created RRU RF
port
Connected
Baseband Device for Cable
Associated to the
Baseband Device
Cascading Connection.
created baseband
N/A
board
BPL Port
BPL port
[0..2]
Mapping of
This parameter is not
[0..3], [15..15]
Antenna port and
configured manually in most
Antenna Channel
cases. It is automatically
generated by the NMS
in accordance with the
transmission device configured
for the RF port object. For an
8-channel RRU, this parameter
is set to 00001111, indicating
that the first four channels are
mapped to port 0 and the last
four channels are mapped to
port 1. For a 2-channel RRU,
if 2-channel single-antenna
is used, this parameter is set
to 0,15,15,15,15,15,15,15.
If two antennas are used,
this parameter is set to
0,1,15,15,15,15,15,15. 15
means that the channel does
not exist or is not used.
7-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Cell mode
This parameter is adjusted
0: 3-cell 8-antenna
6-cell 4-antenna
and optimized based on the
1: 6-cell 4-antenna
[1]
relationship between the
2: PICO single cell
number of cells and antennas.
3: PICO dual cells
3. Click
End of Steps
7.3 S1AP Configuration

This procedure describes how to configure the S1AP parameters.
Prerequisite
The LTE TDD global parameters are configured.
Steps
1. In the managed-element tree, select Radio Parameter > TD-LTE > Resource
Interface Configuration and double-click S1AP. The S1AP-List tab is displayed.
2. Click
. The S1AP tab is displayed, see Figure 7-3. For a description of the key
Figure 7-3 S1AP Configuration
7-5
SJ-20141110151550-006|2015-04-30 (R2.0)
Table 7-3 S1AP Parameters

Parameter
Description
Value Range
Default Value
S1AP ID
This parameter sets the MO
[1..9999]
N/A
Associated to the
N/A
instance ID. It uniquely identify

an MO record under the same
parent node, and cannot be
the same as the other records
under this parent ID.
Referenced SCTP
Referenced SCTP
SCTP configuration
in the transmission.
MME Type
MME Type
0:MME, 1:RNS
MME[0]
S1 Priority
S1 Priority
0:Master,1:Backup
Master[0]
3. Click
End of Steps
7.4 Configuring a Serving Cell

This procedure describes how to configure an eNodeB serving cell.
Prerequisite
The eNodeB physical resources are configured.
Context
Knowledge related to cell configuration:
l
l
l
l
l
l
The maximum number of cell records is 36.

Blocking a cell refers to releasing the service in the cell if the service is running, and
to disable the transmission channel in the cell, so that the resources in the cell are not
available and personnel can perform routine maintenance.
For a normal cell, unblocking is not required.
One cell record may map to multiple baseband resource records and multiple system
resource scheduling records, but it maps to one baseband resource record in this
version.
If a cell record is deleted, all the related configuration parameters are deleted.
The physical cell ID of a cell must be unique.
Steps
1. In the managed-element tree, select Radio Parameter > TD-LTE and double-click
E-UTRAN TDD Cell. The E-UTRAN TDD Cell-List tab is displayed.
7-6
SJ-20141110151550-006|2015-04-30 (R2.0)
2. Click
. The E-UTRAN TDD Cell tab is displayed, see Figure 7-4, Figure 7-5, and
Figure 7-6. Set the parameters as required. For a description of the key parameters,
refer to Table 7-4.
Figure 7-4 E-UTRAN TDD Cell Tab-1
7-7
SJ-20141110151550-006|2015-04-30 (R2.0)
Table 7-4 E-UTRAN TDD Cell Parameters

Parameter
Description
Value Range
Default Value
E-UTRAN TDD Cell
MO instance Identity, A
int[1..9999]
Associated to the
N/A
ID

used to uniquely identify a
Names (RDNs). See 3GPP
TS 32.300.
PLMN List
PLMN list
configured PLMN
Baseband
Baseband resource
Associated to
Resource
configuration
the configured
Configuration
N/A
baseband resource
7-8
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
PCI
int[0..503]
PCI list that can be allocated.
squence[long:[0..50
0;0;0;0;0;0;0;0;0;
Only when distributed PCI
5],12]
0;0;0
long[0..65535]
N/A
identify a cell. There are 504

unique physical-layer cell
identities. The physical-layer
cell identities are grouped
into 168 unique physical-layer
cell-identity groups, each
group containing three unique
identities. The grouping is
such that each physical-layer
cell identity is part of one
and only one physical-layer
cell-identity group. And
the physical cell identities
are space multiplexing and
programmed by network
programming people.
PCI List
allocation is used, this

parameter is valid.
TAC

identify a tracking area within
the scope of a PLMN. The
parameter is used for UE
location management. The
parameter is configured by the
operator.
Cell Coverage
0: Outdoor Micro
Outdoor Macro
Attribute
cover attribution. It is
Cell, 1: Outdoor
Cell[1]
used to determine some
Macro Cell, 2:
physical channel parameters,
Outdoor Super
for example, it is used to
Cell, 3: Outdoor
determine "cyclic prefix length"
Compensatory Cell,
and so on.
4: Indoor Cell
0: 1, 1: 2, 2: 4
Number of Tx
Antenna Port in
number of an antenna port
Cell
in a cell. Transmit diversity
1[0]
and spatial multiplexing use

multi-antenna ports.
7-9
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
Band Indication for
[30..64]
33
Frequency
frequency band for downlink
2[2]
and uplink frequency. The

downlink and uplink frequency
must belong to the same band.
Uplink-Downlink
The parameter sets
0:0,1:1,2:2,3:3,4:4,5
Subframe
uplink-downlink subframe
:5,6:6
Configuration
allocation and sets whether

the subframe is uplink or
downlink subframe.
Special Subframe
The parameter sets the length
[0..9]
Configuration
of DwPTS and UpPTS.
System Bandwidth
This parameter contains
long[0..5](1.4M(6R-
20M(100RB)[5]
the bandwidth supported
B),(3M(15RB),(5M-
by TD-LTE, and can be
(25RB),(10M(50RB)
selected based on the user's
,(15M(75RB),(20M-
requirements.
(100RB))
Maximum RBs
The parameter sets the
[1..100]
100
Allocated for
maximum RB number for the
Downlink UE
UE in downlink configured by
100[33]
high layer for cell.

Maximum RBs
The parameter sets the
0:1,1:2,2:3,3:4,4:5,5
Allocated for Uplink
maximum RB number for the
:6,6:8,7:9,8:10,9:12,
UE
UE in uplink configured by
10:15,11:16,12:18,1
high layer for cell.
3:20,14:24,15:25,16
:27,17:30,18:32,19:
36,20:40,21:45,22:4
8,23:50,24:54,25:60
,26:64,27:72,28:75,
29:80,30:81,31:90,3
2:96,33:100
Center Carrier
Center carrier frequency,
{bandIndica-
{bandIndica-
Frequency
according to band Indication
tor==30}[380..430]
tor==30}[390],
for frequency, the range is
step 0.1, {bandIndi-
{bandIndica-
different.
cator==31}[1447
tor==31}[1457],
..1467] step 0.1,
{bandIndica-
{bandIndicator==
tor==32}[1795],
32}[1785..1805]
{bandIndica-
tor==33}[1910],
cator==33}[1900
{bandIndica-
..1920] step 0.1,
tor==34}[2020],
7-10
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
{bandIndicator==34
{bandIndica-
}[2010..2025] step
tor==35}[1860],
0.1, {bandIndicato-
{bandIndica-
r==35}[1850..1910]
tor==36}[1940],
{bandIndica-
cator==36}[1930
tor==37}[1920],
..1990] step 0.1,
{bandIndica-
{bandIndicator==37
tor==38}[2580],
}[1910..1930] step
{bandIndica-
0.1, {bandIndicato-
tor==39}[1890],
r==38}[2570..2620]
{bandIndica-
tor==40}[2320],
cator==39}[1880
{bandIndica-
..1920] step 0.1,
tor==41}[2506],
{bandIndicator==40
{bandIndica-
}[2300..2400] step
tor==42}[3410],
0.1, {bandIndicato-
{bandIndica-
r==41}[2496..2690]
tor==43}[3610],
{bandIndica-
cator==42}[3400
tor==44}[0],
..3600] step 0.1,
{bandIndica-
{bandIndicator==43
tor==45}[0],
}[3600..3800] step
{bandIndica-
0.1, {bandIndica-
tor==46}[0],
tor==44}[0..5000]
{bandIndica-
tor==47}[0],
cator==45}[0..5000]
{bandIndica-
tor==48}[0],
cator==46}[0..5000]
{bandIndica-
tor==49}[0],
cator==47}[0..5000]
{bandIndica-
tor==50}[0],
cator==48}[0..5000]
{bandIndica-
tor==51}[0],
cator==49}[0..5000]
{bandIndica-
tor==52}[0],
cator==50}[0..5000]
{bandIndica-
tor==53}[0],
cator==51}[0..5000]
{bandIndica-
tor==54}[0],
cator==52}[0..5000]
{bandIndica-
tor==55}[0],
cator==53}[0..5000]
{bandIndica-
7-11
SJ-20141110151550-006|2015-04-30 (R2.0)
Parameter
Description
Value Range
Default Value
tor==56}[0],
cator==54}[0..5000]
{bandIndica-
tor==57}[0],
cator==55}[0..5000]
{bandIndica-
tor==58}[0],
cator==56}[0..5000]
{bandIndica-
tor==59}[0],
cator==57}[0..5000]
{bandIndica-
tor==60}[0],
cator==58}[0..5000]
{bandIndica-
tor==61}[0],
cator==59}[0..5000]
{bandIndica-
tor==62}[0],
cator==60}[0..5000]
{bandIndica-
tor==63}[0],
cator==61}[0..5000]
{bandIndica-
tor==64}[0]
cator==62}[0..5000]
step 0.1, {bandIndicator==63}[0..5000]
step 0.1, {bandIndicator==64}[0..5000]
step 0.1
CFI Selection
The parameter sets the CFI
0: Auto-Adjusted, 1:
Value configured by high
1, 2: 2, 3: 3, 4: 4
2[2]
layer for cell. The CFI Value

could be 1, 2, 3 or could be
configured as auto-adjusted.
3. Click
Note:
Each cell needs a standalone configuration record.
End of Steps
7-12
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 8
XML File Generation

Table of Contents
Generating XML Files for an eNodeB .........................................................................8-1
Generating XML Files for the EMS .............................................................................8-3
8.1 Generating XML Files for an eNodeB

This procedure describes how to generate XML files for an eNodeB. The XML files are
used by engineers to perform USB commissioning or LMT commissioning.
Prerequisite
The initial configuration of eNodeB parameters are completed.
Steps
1. Select Configuration Management > Data Synchronization, see Figure 8-1. The
Data Synchronization dialog box is displayed, see Figure 8-2.
Figure 8-1 Data Synchronization Menu
8-1
SJ-20141110151550-006|2015-04-30 (R2.0)
Figure 8-2 Data Synchronization Dialog Box
2. In the left pane, select one or multiple eNodeBs that need(s) to be synchronized. In
the right pane, select Generate synchronization file, see Figure 8-2.
3. Click Generate File, and wait until the progress bar reaches 100%. The Confirm
dialog box is displayed, see Figure 8-3.
Figure 8-3 Confirm Dialog Box
4. In the Confirm dialog box, perform the following operations.

To...
Do...
Open the local folder where the generated files
Click Yes.
are saved
Close the Confirm dialog box
Click No.
Show the file exporting result and saving path
Click Show Details.
End of Steps
8-2
SJ-20141110151550-006|2015-04-30 (R2.0)
Chapter 8 XML File Generation
8.2 Generating XML Files for the EMS

This procedure describes how to generate XML files for the EMS. The XML files can be
used for quick eNodeB commissioning through the EMS.
Prerequisite
The initial configuration of eNodeB parameters are completed.
Steps
1. Select Configuration Management > Data Export, see Figure 8-4. The Data Export
dialog box is displayed, see Figure 8-5.
Figure 8-4 Data Export Menu
Figure 8-5 Data Export Dialog Box
8-3
SJ-20141110151550-006|2015-04-30 (R2.0)
2. In the left pane, select one or multiple eNodeBs for which configuration files need to
be generated. In the right pane, select Modify area for Data area, and select XML
file for File type. Click Browse and select a path for the exported files for File path,
and enter XML for File name prefix, see Figure 8-5.
3. Click Export and wait until the progress bar reaches 100%. The Confirm dialog box
is displayed, see Figure 8-6.
Figure 8-6 Confirm Dialog Box
4. In the Confirm dialog box, perform the following operations.

To...
Do...
Open the local folder where the generated files
Click Yes.
are saved
Close the Confirm dialog box
Click No.
Show the file exporting result and saving path
Click Show Details.
End of Steps
8-4
SJ-20141110151550-006|2015-04-30 (R2.0)
Glossary
BBU
- Base Band Unit
BCT
- Barring of Call Transfer
BOQ
- Bill of Quantities
BPL
- Baseband Processing for LTE
CFI
- Control Format Indicator
DSCP
- Differentiated Services Code Point
EMS
- Element Management System
FTP
- File Transfer Protocol
GPS
- Global Positioning System
IP
- Internet Protocol
LACP
- Link Aggregation Control Protocol
LMT
- Local Maintenance Terminal
MTU
- Maximum Transfer Unit
NE
- Network Element
OMC
- Operation & Maintenance Center
PC
- Personal Computer
PLMN
- Public Land Mobile Network
I
SJ-20141110151550-006|2015-04-30 (R2.0)
PTP
- Precision Time Protocol
RDN
- Relative Distinguished Name
RRU
- Remote Radio Unit
SCTP
- Stream Control Transmission Protocol
SFTP
- Secure File Transfer Protocol
SNTP
- Simple Network Time Protocol
SON
- Self-Organizing Network
SSH
- Secure Shell
UDP
- User Datagram Protocol
USB
- Universal Serial Bus
XML
- Extensible Markup Language
eNodeB
- Evolved NodeB
II
SJ-20141110151550-006|2015-04-30 (R2.0)

SJ-20141110151550-005-ZXSDR UniRAN TDD-LTE (V3.20.50) Performance Indicator Reference

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SJ-20141110151550-005-ZXSDR UniRAN TDD-LTE (V3.20.50) Performance Indicator Reference

Enviado por

Direitos autorais:

Formatos disponíveis

ZXSDR UniRAN

TD-LTE Base Station

Initial Configuration Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

5.1.1 Creating a Baseband Resource Board

5.1.2 Creating an RRU

5.3.1 Configuring the GPS Clock Source

5.3.2 Configuring the 1588 Clock Source

6.1 Configuring a Physical Layer Port

6.4.2 Configuring DSCP Mapping

6.5 Configuring a Static Routing

7.1 Configuring TD-LTE Global Parameters

7.2 Configuring Baseband Resources

7.4 Configuring a Serving Cell

Serial Number: SJ-20141110151550-006

ZTE Proprietary and Confidential

Chapter 4 Operator Information Configuration ....................................... 4-1

Chapter 5 Physical Resource Configuration ........................................... 5-1

Chapter 6 Network Transmission Configuration ..................................... 6-1

ZTE Proprietary and Confidential

6.2 IP Transmission Configuration............................................................................. 6-5

Chapter 7 Radio Parameter Configuration............................................... 7-1

Chapter 8 XML File Generation ................................................................. 8-1

ZTE Proprietary and Confidential

About This Manual

What Is in This Manual

Describes the concept, methods, tools, and flow of initial

Describes preparations before initial configuration.

Describes how to configure initial management information.

Describes how to configure operator information.

Describes how to configure the BBU, RRU, and auxiliary

Chapter 6, Network Transmission

Describes how to configure network transmission.

Describes how to configure radio parameters.

Describes how to generate XML files after initial configuration

ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Ground Parameter Reference

ZTE Proprietary and Confidential

Danger:sets an imminently hazardous situation. Failure to comply

ZTE Proprietary and Confidential

Initial Configuration Methods

Initial Configuration Tools

Initial Configuration Flow

ZTE Proprietary and Confidential

ZXSDR UniRAN Initial Configuration Guide

Figure 1-1 Initial Configuration Flow

ZTE Proprietary and Confidential

Preparing Parameter Documents

ZXSDR UniRAN TD-LTE(V3.20.50) Base Station Ground Parameter Reference

The above parameters come from the following three sources:

User planning: parameters planned by the operator.

ZTE Proprietary and Confidential

ZXSDR UniRAN Initial Configuration Guide

This page intentionally left blank.

ZTE Proprietary and Confidential

3.1 Creating and Starting an NE Agent

Name of the NE agent. A name that can directly indicate where

Time zone where the NE agent is located. This parameter is

Vendor that manufactures the devices managed by the lower

IP address of the lower EMS. This parameter is required.

ZTE Proprietary and Confidential

ZXSDR UniRAN Initial Configuration Guide

Administrative state of the NE agent. This attribute is

automatically set by the system, and cannot be modified by