Sj-20140604172046-024-Zxsdr Uniran Fdd-Lte (v3.20.50) Initial Configuration Guide (Qcell)

ZXSDR UniRAN
FDD-LTE Base Station

Initial Configuration Guide (QCELL)
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: 800@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-09-29 V3.20.50.32
Those topics have been modified:
l 4.1.2 Creating a PBridge,Figure 4-3 Add PBridge Dialog Box

l 4.1.3 Creating a PRRU,Figure 4-5 Add RRU Dialog Box
R1.0 2015-06-15 First edition
Serial Number: SJ-20140604172046-024
Publishing Date: 2015-09-29 (R2.0)
SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Configuration Flow ................................................................... 1-1
Chapter 2 Initial Management Information Configuration ...................... 2-1
2.1 Creating a Subnetwork ....................................................................................... 2-1
2.2 Creating an NE .................................................................................................. 2-2
2.3 Requesting or Releasing Mutually Exclusive Access............................................. 2-4
Chapter 3 Operator Information Configuration ....................................... 3-1

3.1 Creating an Operator.......................................................................................... 3-1
3.2 Creating a PLMN................................................................................................ 3-2
Chapter 4 Physical Resource Configuration ........................................... 4-1

4.1 NE Configuration................................................................................................ 4-1
4.1.1 Creating a BBU ........................................................................................ 4-1
4.1.2 Creating a PBridge ................................................................................... 4-3
4.1.3 Creating a PRRU ..................................................................................... 4-5
4.2 Clock Configuration ............................................................................................ 4-7
4.2.1 Configuring Time ...................................................................................... 4-7
4.2.2 Creating a Clock ...................................................................................... 4-9
Chapter 5 Network Transmission Configuration ..................................... 5-1

5.1 Interface Connection Configuration...................................................................... 5-1
5.1.1 Modifying the Optical Interface Rate of an FS Board................................... 5-1
5.1.2 Creating an Optical Connection Between an FS and a PBridge ................... 5-3
5.1.3 Creating an Optical Cascaded Connection Between Two PBridges ............. 5-4
5.1.4 Creating Ethernet Connections Between a PBridge and PRRUs.................. 5-5
5.2 Creating a Physical Layer Port ............................................................................ 5-6
5.3 Transmission Configuration................................................................................. 5-8
5.3.1 Configuring an Ethernet Link ..................................................................... 5-8
5.3.2 Configuring the IP Layer ........................................................................... 5-9
5.4 Bandwidth Assignment ..................................................................................... 5-12
5.4.1 Creating a Bandwidth Resource Group .................................................... 5-12
5.4.2 Creating a Bandwidth Resource .............................................................. 5-14
5.5 Signaling and Interaction Configuration.............................................................. 5-15
5.5.1 Configuring SCTP Parameters ................................................................ 5-15
5.5.2 Configuring a Service and DSCP Mapping ............................................... 5-17

5.6 Creating an OMC Channel ................................................................................ 5-19
Chapter 6 Radio Parameter Configuration............................................... 6-1

6.1 Configuring LTE FDD Global Parameters............................................................. 6-1
6.2 Configuring Baseband Resources ....................................................................... 6-3
6.3 Configuring a Serving Cell .................................................................................. 6-5
Chapter 7 XML Configuration File Generation......................................... 7-1

7.1 Generating XML Files for an eNodeB .................................................................. 7-1
7.2 Generating XML Files for the EMS ...................................................................... 7-2
Glossary .......................................................................................................... I
II

About This Manual
Purpose
This manual describes the detailed steps of the initial configuration of the ZXSDR UniRAN.
Intended Audience
l Debugging engineers
l Network planning engineers
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters.
Chapter 1, Configuration Flow Describes the initial configuration flow.
Chapter 2, Initial Management Describes how to configure initial management information.

Information Configuration
Chapter 3, Operator Describes how to configure operator information.

Chapter 4, Physical Resource Describes how to configure BBUs, PBridges, PRRUs, and auxiliary
Configuration devices of an eNodeB.
Chapter 5, Network Describes how to configure network transmission.

Transmission Configuration
Chapter 6, Radio Parameter Describes how to configure radio parameters.

Configuration
Chapter 7, XML Configuration Describes how to generate XML configuration files after initial
File Generation configuration is complete.
Related Documentation
l ZXSDR UniRAN FDD-LTE Base Station (V3.20.50) Ground Parameter Reference
l ZXSDR UniRAN FDD-LTE Base Station (V3.20.50) Radio Parameter Reference
Conventions
This manual uses the following convention.
Typeface Meaning
Note: provides additional information about a

topic.

This page intentionally left blank.
II

Chapter 1
Configuration Flow
Figure 1-1 shows the initial configuration flow.
Figure 1-1 Configuration Flow
1-1

ZXSDR UniRAN Initial Configuration Guide (QCELL)
1-2

Chapter 2
Initial Management
Before QCell configuration, you need to create a subnetwork and NE, and apply for the
mutually exclusive access for an NE. This chapter describes how to configure the initial
management information.
Table of Contents
Creating a Subnetwork ...............................................................................................2-1
Creating an NE...........................................................................................................2-2
Requesting or Releasing Mutually Exclusive Access ..................................................2-4
2.1 Creating a Subnetwork

To easily manage adjacent base stations, you can create a subnetwork and place the base
stations into the subnetwork. This procedure describes how to create a subnetwork.
Steps
1. In the Configuration Management window, right-click the configuration resource tree
and select Create Subnetwork. The Subnetwork tab is displayed, see Figure 2-1.
Figure 2-1 Subnetwork Tab
2. Set the parameters as required. For a description of the parameters, refer to Table
2-1.
Table 2-1 Subnetwork Parameter Descriptions
Parameter Description Value Range Default Value
User Label Label of the user. string[0..128] N/A
SubNetwork ID Subnetwork ID, long[0..999999999] N/A

which identifies a
subnetwork.
2-1

3. Click .
End of Steps
2.2 Creating an NE
This procedure describes how to create an NE in a subnetwork.
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
2-2. For a description of the key parameters, refer to Table 2-2.
Figure 2-2 Managed Network Element Tab
Table 2-2 Parameter Descriptions for the Managed Network Element Tab
Radio Standard Radio standard LTE FDD, TD-LTE, LTE FDD

supported by the LTE FDD+TD-LTE
NE.
NE ID Unique ID of the NE. int [0..999999999] 0

It is automatically
generated by the
EMS.
2-2

Chapter 2 Initial Management Information Configuration
NE Configuration Version of the NE. It should be the same Version

Data Version as the actually used corresponding to
version. the first option in the
drop-down list.
NE Type Identifies the type of B8901A,B8901B,B- B8901A

the NE. Available S8700,BS8800,B-
options of this S8900A,BS8900B-
parameter are ,BS8906,BS8906E-
determined by ,BS8912,BS8922
the selected radio L1800(A5A),BS8922
standard. L1800(A5B),BS8922
L2100(A5A),BS8922
L2100(A5B),CS200,
ZXSDR BC8900S
BBU Type The BBU type is B8200[0], Integration[5]

closely related to B8300[4], Integra-
the NE type. If the tion[5],B8210[9]
NE type is set to
BS8700, BS8800,
BS8900B,CS200, or
ZXSDR BC8900S the
BBU type must be
B8200[0], B8300[4]
or B8210[9]. If the
NE type is set to
BS8900A,BS8906
or BS8906E, the
BBU type must be
B8200[0] or B8210[9].
If the NE type is set
to B8901A,B8901
B,BS8912,BS8922
L1800(A5A),BS8922
L1800(A5B),BS8922
L2100(A5A) or
BS8922 L2100(A5B),
the BBU type must be
Integration[5].
2-3

NE Maintenance Maintenance status Normal[0], Testing[2], Configuring[3]

Status of an eNodeB. Configuring[3],
The eNodeB can FM testing[5], PM
establish a link with testing[6]
the EMS only when
the eNodeB is in
Normal state. After
being synchronized,
the eNodeB in Normal
state can report
alarms.
Maintenance Status Maintenance status of Normal[0], Testing[2], Testing[2]

of LTE FDD an LTE FDD eNodeB. FM testing[5], PM
The eNodeB can testing[6]
establish a link with
the EMS only when
the eNodeB is in
Normal state. After
being synchronized,
the eNodeB in Normal
state can report
alarms.
NE running mode Operating mode of the Master and slave[0], Master and slave[0]
NE. Overlay load
sharing[2]
NE address IP address used N/A N/A

by the eNodeB to
communicate with
the EMS. The IP
address may be an
IPv4 address or IPv6
address.
3. Click .
End of Steps
2.3 Requesting or Releasing Mutually Exclusive

Access
This procedure describes how to request or release mutually exclusive access.
2-4

Chapter 2 Initial Management Information Configuration
Steps
Requesting Mutually Exclusive Access
1. In the Configuration Management window, right-click an NE node in the configuration
resource tree, and select Apply For Mutex Right.
2. The icon is displayed before the NE, indicating that you have successfully requested
mutually exclusive access for the NE.
Note:
If the icon is red, it indicates that mutually exclusive access for the NE is being occupied
by another user.
Releasing Mutually Exclusive Access

3. To release mutually exclusive access of an NE after configuring the NE, right-click the
NE node, and select Release Mutex Right.
4. The icon before the NE disappears, indicating that you have successfully released
mutually exclusive access for the NE.
End of Steps
2-5

2-6

Chapter 3
Operator Information
Configuration
Table of Contents
Creating an Operator..................................................................................................3-1
Creating a PLMN........................................................................................................3-2
3.1 Creating an Operator

Before creating the physical resources of an NE, you need to configure the operator and
PLMN information of the NE. This procedure describes how to create an operator.
Prerequisite
An NE is created.
Steps
1. In the Configuration Management window, expand an NE, and select Modify Area.
The Managed Element configuration resource tree is displayed in the lower left area.
2. In the Managed Element tree, double-click Operator. The Operator-List tab is
displayed.
3. On the Operator-List tab, click . The Operator tab is displayed.
4. Set the parameters on the Operator tab, see Figure 3-1. For a description of the
parameters, refer to Table 3-1.
Figure 3-1 Operator Tab
3-1

Table 3-1 Operator Parameter Descriptions
Operator name Name of the operator string[1..127] N/A

using an eNodeB. It
contains a maximum
of 127 characters.
l This parameter
cannot be null.
l Up to eight
records can be
configured for an
operator object.
5. Click . An operator record is displayed on the Operator-List tab.

End of Steps
3.2 Creating a PLMN

This procedure describes how to create a PLMN.
Prerequisite
l A subnetwork is created.
l An NE is created.
l An operator is created.
Steps
1. In the configuration resource tree, select Operator and double-click PLMN. The
PLMN-List tab is displayed.
2. On the PLMN-List tab, click . The PLMN tab is displayed.
3. Set the parameters on the PLMN tab, see Figure 3-2. For a description of the
parameters, refer to Table 3-2.
Figure 3-2 PLMN Tab
3-2

Chapter 3 Operator Information Configuration
Table 3-2 PLMN Parameter Descriptions
MCC Mobile country string[3...3] N/A

code in a PLMN.
The combination of
a mobile country
code and a mobile
network code uniquely
identify the home
network operator
of an eNodeB.
This parameter is
unique and contains
a maximum of three
digits.
MNC Mobile network string[2...3] N/A

code in a PLMN.
The combination of
a mobile country
code and a mobile
network code uniquely
identify the home
network operator
of an eNodeB.
This parameter is
unique and contains
a maximum of three
digits.
4. Click . A PLMN record is displayed on the PLMN-List tab.
End of Steps
3-3

3-4

Chapter 4
Physical Resource
Configuration
The ZXSDR UniRAN is a base station system that uses BBUs as baseband pool
resources, uses PBridges for transmission conversion, and PRRUs for RF transmission.
This procedure describes how to create physical resources for the ZXSDR UniRAN.
Table of Contents
NE Configuration ........................................................................................................4-1
Clock Configuration ....................................................................................................4-7
4.1 NE Configuration
4.1.1 Creating a BBU
This procedure describes how to create a BBU baseband resource board in the EMS
configuration set. The board type and slot number of the BBU in the configuration set
should be consistent with the physical configurations of the BBU.
Prerequisite
l An NE is created.
Steps
1. In the managed element tree, double-click Device. The Rack Graph tab is displayed.
2. In the Physical View on the Rack Graph tab, right-click the slot planned for the board,
and select Add Board. The Add Board dialog box is displayed, see Figure 4-1.
4-1

Figure 4-1 Add Board Dialog Box
3. In the Add Board dialog box, set the type of the baseband resource board according
to the data of the ZXSDR UniRAN, and click OK.
4. Repeat steps 2 and 3 to create CC, BPL, FS, SA, and PM boards according to BBU
board planning.
5. After creating the baseband resource boards, you can view them on the Rack Graph
tab.
6. (Optional) To delete an existing board, perform the following steps:
a. Right-click the board, and select Delete Board.
b. In the pop-up Delete Board dialog box, enter a verification code.
c. Click OK.
End of Steps
Result
After the boards are created, the corresponding board nodes are also created in the
managed element tree, see Figure 4-2.
4-2

Chapter 4 Physical Resource Configuration
Figure 4-2 Board Node Tree
4.1.2 Creating a PBridge

A PBridge is a transmission conversion device used by a PRRU for indoor coverage, and
it implements conversion from an optical CPRI into an Ethernet electrical interface and IQ
data conversion. This procedure describes how to create a PBridge.
Prerequisite
l An NE is created.
Steps
2. In the Physical View, click . The Add PBridge dialog box is displayed, see Figure
4-3.
4-3

Figure 4-3 Add PBridge Dialog Box
3. Set the parameters in the dialog box as required.

4. Click OK.
5. (Optional) To delete an existing PBridge and the corresponding rack, perform the
following steps:
a. Right-click the PBridge, and select Delete Board.
b. In the pop-up Delete Operation dialog box, enter a verification code.
c. Click OK.
d. Right-click the deleted PBridge, and select Delete Rack.
e. In the pop-up Delete Operation dialog box, enter a verification code.
f. Click OK.
End of Steps
Result
After the PBridge is created, it is displayed in the rack graph, see Figure 4-4.
4-4

Figure 4-4 PBridge in the Rack Graph
4.1.3 Creating a PRRU

This procedure describes how to create a PRRU in the EMS configuration set. The type
of the PRRU in the configuration set should be consistent with the physical configuration
of the PRRU.
Prerequisite
l An eNodeB is created.
Steps
2. In the Physical View, click .The Add RRU dialog box is displayed, see Figure 4-5.
4-5

Figure 4-5 Add RRU Dialog Box
3. Set the parameters in the dialog box as required.
4. Click OK.
5. (Optional) To delete an existing PRRU and the corresponding rack, perform the
following steps:
a. Right-click the PRRU, and select Delete Board.

b. In the pop-up Delete Operation dialog box, enter a verification code.
c. Click OK.
d. Right-click the deleted PRRU, and select Delete Rack.
e. In the pop-up Delete Operation dialog box, enter a verification code.
f. Click OK.
End of Steps
Result
After the PRRU is created, it is displayed in the rack graph, see Figure 4-6.
4-6

Figure 4-6 PRRU in the Rack Graph
4.2 Clock Configuration

4.2.1 Configuring Time
This procedure describes how to configure the time for FDD LTE.
Prerequisite
l An 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.
2. Double-click an existing time configuration record, or click . The Time
Configuration tab is displayed.
3. Set the parameters on the Time Configuration tab, see Figure 4-7.For a description
of the key parameters, refer to Table 4-1.
4-7

Figure 4-7 Time Configuration Tab
Table 4-1 Time Configuration Parameters
Clock synchronization This attribute indicates [1..24] 24

period (h) the period (hour) that
the base station
performs time
synchronization with
the NTP.
NTP server IP The base station N/A 0.0.0.0

address obtains time from
the server by NTP
protocol.
SNTP standby server Use standby server N/A 0.0.0.0

IP address to synchronize time
when the active server
is abnormal.
Time zone Indicates the time 0:GMT - 12:00, 2:GMT 40

zone of the base - 11:00, 4:GMT -
station. 10:00, 6:GMT - 9:00,
8:GMT - 8:00, 10:GMT
- 7:00, 12:GMT
- 6:00, 14:GMT
- 5:00, 15:GMT
- 4:30, 16:GMT
- 4:00, 17:GMT
- 3:30, 18:GMT
- 3:00, 20:GMT
4-8

- 2:00, 22:GMT
- 1:00, 24:GMT -
0:00, 26:GMT +
1:00, 28:GMT +
2:00, 30:GMT +
3:00, 31:GMT +
3:30, 32:GMT +
4:00, 33:GMT +
4:30, 34:GMT +
5:00, 35:GMT +
5:30, 51:GMT +
5:45, 36:GMT +
6:00, 37:GMT +
6:30, 38:GMT +
7:00, 40:GMT +
8:00, 42:GMT +
9:00, 43:GMT + 9:30,
44:GMT + 10:00,
46:GMT + 11:00,
48:GMT + 12:00,
50:GMT + 13:00
Daylight saving time This attribute indicates 0:No, 1:MM-DD 0

supported the time format of the HH:MM, 2:MM-
daylight saving time. WK-WD HH:MM
SNTP enabled Indicate whether 0:No, 1:Yes 1

to enable SNTP
time synchronization
function.
Daylight saving time When the daylight [1..42] 4

offset saving time is
enabled, it is used
to configure its offset
(time granularity is 15
minutes).
4. Click .
End of Steps
4.2.2 Creating a Clock

This procedure describes how to create a clock.
4-9

Prerequisite
l An NE is created.
l A BBU is created.
Steps
1. In the managed element tree, select Device > B8200(1,1) > CCC(1.1.1) (B8200 is a
BBU type and used as an example), and double-click Clock Device Set. The Clock
Device Set-List tab is displayed.
2. On the Clock Device Set-List tab, click . The Clock Device Set tab is displayed,
see Figure 4-8. For a description of the parameters, refer to Table 4-2.
Figure 4-8 Clock Device Set Tab
Table 4-2 Clock Device Set Parameters
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.
4-10

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
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
for the lower-level BS BBU.
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 used as an example), and double-click Clock
Device. The Clock Device-List tab is displayed.
4-11

5. On the Clock Device-List tab, click . The Clock Device tab is displayed, see Figure
4-9. Set the parameters as required. For a description of the key parameters, refer to
Table 4-3.
Figure 4-9 Clock Device Tab
Table 4-3 Clock Device Parameters
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]
1: GNSS Clock Category, 2: Phase
1PPS+TOD Clock Category, 3: 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:
1: GNSS Clock Category, 4:
1588 Clock Category.
4-12

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]
is accessed from slot 5 of Network Listening:
BBU-2U or slot 7 of BBU-3U, [Network Listening]
"Backplane 1PPS+TOD" can
be selected.
Priority Priority of the clock reference [1..8] 1

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.
4-13

6. Click .
End of Steps
4-14

Chapter 5
Network Transmission
Configuration
Table of Contents
Interface Connection Configuration ............................................................................5-1
Creating a Physical Layer Port ...................................................................................5-6
Transmission Configuration ........................................................................................5-8
Bandwidth Assignment .............................................................................................5-12
Signaling and Interaction Configuration ....................................................................5-15
Creating an OMC Channel .......................................................................................5-19
5.1 Interface Connection Configuration

5.1.1 Modifying the Optical Interface Rate of an FS Board
This procedure describes how to modify the optical interface rate of an FS board.
Prerequisite
l An NE is created.
l A BBU is created.
Steps
1. In the managed element tree, select Device > B8200(1,1) > FS(1.1.3) > Optical Port
Device Set (B8200 is a BBU type and used as an example), and double-click Optical
Port Device. The Optical Port Device-List tab is displayed.
2. Double-click the target optical interface record, or select the record and click on the
Optical Port Device tab. Modify the optical interface rate of the FS board, see Figure
5-1.For a description of the key parameters, refer to Table 5-1.
5-1

Figure 5-1 Optical Port Device Tab
Table 5-1 Optical Port Device Parameters
Connected board port This attribute indicates [0..15] 0

number the number of a
physical port. It
identifies the number
of optical interface
devices. This
attribute is generated
automatically by the
NMS. It does not need
to be configured and
cannot be modified.
RU board or not This attribute indicates 0:N, 1:Y 1

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
attribute is generated
NMS. It does not need
to be configured and
cannot be modified.
5-2

Chapter 5 Network Transmission Configuration
Ir line bit rate This attribute indicates {isRU==0}[1:1.25G, {isRU==0}[1],

the rate of a physical 2:2.5G, 3:3G, 4:4G, {isRU==1}[255]
port (matched with 6:6G, 10:10G],
the optical module {isRU==1}[ 1:1.25G,
type and the SFP port 2:2.5G, 3:3G, 4:4G,
type). This attribute is 6:6G, 10:10G,
used to calculate the 255:Self adaptive]
number of IQs that an
optical interface can
bear. It is generated
NMS. The user can
modify it as required.
For example, if the
optical module type
is 6G, this attribute
value is set to 6.
3. According to requirements of the PBridge, modify the Ir port line rate from the default
value 1.25G[1] to 10G[10].
4. Click .
End of Steps
5.1.2 Creating an Optical Connection Between an FS and a PBridge

This procedure describes how to create an optical connection between an FS board and
a PBridge.
Prerequisite
l An NE is created.
l A BBU is created.
l A PBridge is created.
l The optical interface rate is modified.
Steps
1. In the managed element tree, select Device > BTS Auxiliary Peripheral Device >
Cable, and double-click Fiber Cable. The Fiber Cable-List tab is displayed.
2. On the Fiber Cable-List tab, click . The Fiber Cable tab is displayed.
3. On the Fiber Cable tab, set an optical connection between the FS and PBridge, see
Figure 5-2.
5-3

Figure 5-2 Creating an Optical Connection Between the FS and PBridge
Note:
In this example, the first optical interface No.0 of the FS board is connected to
PBridge1-51. The first optical interface No.1 of the PBridge is always used for uplink
connection.
4. Click .
End of Steps
5.1.3 Creating an Optical Cascaded Connection Between Two

PBridges
This procedure describes how to create an optical cascaded connection between two
PBridges.
Prerequisite
l An NE is created.
l A BBU is created.
l Two PBridges are created.
l The optical interface rate is modified.
Steps
1. In the managed element tree, select Device > BTS Auxiliary Peripheral Device >
Cable, and double-click Fiber Cable. The Fiber Cable-List tab is displayed.
2. On the Fiber Cable-List tab, click . The Fiber Cable tab is displayed.
3. On the Fiber Cable tab, set an optical connection between the two PBridges, see
Figure 5-3.
5-4

Figure 5-3 Creating an Optical Cascaded Connection Between the Two PBridges
Note:
In this example,
l Lower level optical port,
the first optical interface No.1 of a PBridge(52) is always used for uplink
connection.
l Upper level optical port,
the fourth optical interface No.4 of a PBridge(51) is used for downlink connection.
4. Click .
End of Steps
5.1.4 Creating Ethernet Connections Between a PBridge and

PRRUs
This procedure describes how to create Ethernet connections between a PBridge and
PRRUs.
Prerequisite
l An NE is created.
l A BBU is created.
l A PBridge is created.
l PRRUs are created.
Steps
1. In the managed element tree, select Device > BTS Auxiliary Peripheral Device
> Cable, and double-click Ethernet Interface Cable. The Ethernet Interface
Cable-List tab is displayed.
5-5

2. On the Ethernet Interface Cable-List tab, click . The Ethernet Interface Cable
tab is displayed.
3. On the Ethernet Interface Cable tab, set an Ethernet connection between the PBridge
and each PRRU, see Figure 5-4.
Figure 5-4 Creating an Ethernet Connection Between the PBridge and a PRRU
Note:
Network interfaces No. 1 to 5 of PBridge151 are respectively connected to the first,
second, third, fourth, and fifth PRRU.
4. Click .
End of Steps
5.2 Creating a Physical Layer Port

This procedure describes how to create a physical layer port.
Prerequisite
l An NE is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD > Physical
Hosting, and double-click Physical Layer Port. The Physical Layer Port-List tab is
displayed.
2. On the Physical Layer Port-List tab, click . The Physical Layer Port tab is
displayed.
5-6

3. On the Physical Layer Port tab, set the parameters of a physical layer port, see Figure
Figure 5-5 Physical Layer Port Tab
Table 5-2 Physical Layer Port Parameters
Transmission This attribute sets the physical E1, T1, STM-1, Ethernet
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 N/A N/A

Ethernet Ge device, that is, the Ethernet
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.
4. Click .
End of Steps
5-7

5.3 Transmission Configuration

5.3.1 Configuring an Ethernet Link
This procedure describes how to configure an Ethernet link.
Prerequisite
l An NE is created.
l A physical layer port is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD > IP
Transport, and double-click Ethernet Link Layer. The Ethernet Link Layer-List
tab is displayed.
2. On the Ethernet Link Layer-List tab, click . The Ethernet Link Layer tab is
displayed.
3. On the Ethernet Link Layer tab, set the parameters of an Ethernet link, see Figure
Figure 5-6 Ethernet Link Layer Tab
Table 5-3 Ethernet Link Parameters
MTU (Byte) This attribute sets the [256..1800] 1500

maximum transmitted bytes
of each Ethernet link layer
packet.
5-8

Used physical layer This attribute sets the N/A N/A

port transmission media used
by the physical layer port
object and it must be STM-1.
Used LACP This attribute sets the LACP N/A N/A

aggregation group Aggregation Port that bears
Ethernet.
4. Click .
End of Steps
5.3.2 Configuring the IP Layer

This procedure describes how to configure the IP layer.
Prerequisite
l An NE is created.
l An Ethernet link is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD
> IP Transport, and double-click IP Layer Configuration. The IP Layer
Configuration-List tab is displayed.
2. On the IP Layer Configuration-List tab, click . The IP Layer Configuration tab is
displayed.
3. On the IP Layer Configuration tab, set the parameters of the IP layer, see Figure
5-9

Figure 5-7 IP Layer Configuration Tab
Table 5-4 IP Layer Parameters
Object ID of IP layer This attribute identifies the [1..20] 1

configuration number of IP configurations.
This attribute provides a
Relative Distinguished Name
(RDN). This attribute 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 attribute indentifies the [0..19] 0

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.
5-10

IP address This attribute sets the IP 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 ad-
dress. 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 This attribute sets the subnet N/A 255.255.0.0

mask of an IP address.
Only IPv4 address can be
configured.
Gateway IP This attribute sets the IP N/A 0.0.0.0

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 This attribute sets the Ethernet N/A N/A
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.
5-11

VLAN ID This attribute sets the VLAN [1..4094] N/A

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 Used Ethernet Link Group. N/A N/A

Group
X2 self-setup This attribute is valid only when No, Yes N/A

enabled the IP address is used for LTE
transmission. It is used for the
LTE X2 self-establishment.
4. Click .
End of Steps
5.4 Bandwidth Assignment

5.4.1 Creating a Bandwidth Resource Group
This procedure describes how to create a bandwidth resource group.
Prerequisite
l An NE is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD >
Bandwidth Assignment, and double-click Bandwidth Resource Group. The
Bandwidth Resource Group-List tab is displayed.
2. On the Bandwidth Resource Group-List tab, click . The Bandwidth Resource
Group tab is displayed.
3. On the Bandwidth Resource Group tab, set the parameters of the bandwidth
resource group, see Figure 5-8.For a description of the key parameters, refer to Table
5-5.
5-12

Figure 5-8 Bandwidth Resource Group Tab
Table 5-5 Bandwidth Resource Group Parameters
Bandwidth resource This attribute sets the [0..15] 0

group number bandwidth resource group
number, which must be unique
in the same bearer mode. In
the Ethernet bearer mode,
this attribute value can be set
from 0 to 5. In the PPP bearer
mode, this attribute value can
be set from 0 to 15.
Used Ethernet link This attribute sets on which N/A N/A

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 This attribute sets the [1..1000] N/A

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 [1..1000] N/A

bandwidth of of ingress.
ingress (Mbps)
5-13

4. Click .
End of Steps
5.4.2 Creating a Bandwidth Resource

This procedure describes how to create a bandwidth resource.
Prerequisite
l An NE is created.
l A bandwidth resource group is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD >
Bandwidth Assignment > Bandwidth Resource Group, and double-click
Bandwidth Resource. The Bandwidth Resource-List tab is displayed.
2. On the Bandwidth Resource-List tab, click . The Bandwidth Resource tab is
displayed.
3. On the Bandwidth Resource tab, set the parameters of a bandwidth resource, see
Figure 5-9.For a description of the key parameters, refer to Table 5-6.
Figure 5-9 Bandwidth Resource Tab
Table 5-6 Bandwidth Resource Parameters
Bandwidth This attribute sets the [1..6] 1

resource number bandwidth resource number,
which the user can define.
This attribute value can be set
through 1 to 6.
5-14

Transmission This attribute is used to [0..100] 100

bandwidth weight configure transmission
bandwidth weight. The
maximum bandwidth of
egress of a bandwidth
resource group multiplied by
transmission bandwidth weight
is the minimum guaranteed
bandwidth.
4. Click .
End of Steps
5.5 Signaling and Interaction Configuration

5.5.1 Configuring SCTP Parameters
This procedure describes how to configure SCTP parameters.
Prerequisite
l An NE is created.
l IP layer parameters are configured.
l A bandwidth resource is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD > Signaling
and Business. and double-click SCTP. The SCTP-List tab is displayed.
2. On the SCTP-List tab, click . The SCTP tab is displayed.
3. On the SCTP tab, set the SCTP parameters, see Figure 5-10.For a description of the
key parameters, refer to Table 5-7.
5-15

Figure 5-10 SCTP Tab
Table 5-7 SCTP Parameters
SCTP link number This attribute sets the SCTP [0..63] 0

association link number. The
attribute value ranges from 0 to
63. It is user-defined within the
value range.
Local port number This attribute sets the local port [0..65535] 0
number of an SCTP association
link. It is an interconnection
parameter.
Used IP layer This attribute sets IP-layer N/A N/A

configuration configuration that bears SCTP
association. SCTP can get the
IP address of the local end.
Used bandwidth This attribute is used to N/A N/A

resource configure the bandwidth
resource used for SCTP.
For SCTP, the bandwidth
resource to be used cannot be
configured.
5-16

Remote port This attribute sets the remote [0..65535] 0

number port number of an SCTP
association link. It is an
interconnection parameter.
Remote address This attribute sets the remote IP N/A 0.0.0.0

address of SCTP association.
It is an interconnection parame-
ter. 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:85a3:0000:
1319:8a2e:0370:7366.
Primary path This attribute corresponds [0..3] 0

number to four IP addresses in the
association. It indicates that
one of the four IP addresses is
selected as the primary path.
Number of This attribute sets the number of [2..6] 2

in-and-out streams incoming and outgoing streams
of an SCTP association. A
maximum of six incoming
and outgoing streams can be
configured.
DSCP This attribute sets the IP [0..63] 46

service model configuration.
For various scenarios, different
DSCPs are chosen. The
attribute value ranges from 0 to
63.
4. Click .
End of Steps
5.5.2 Configuring a Service and DSCP Mapping

This procedure describes how to configure a service and DSCP mapping.
5-17

Prerequisite
l An NE is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD > Signaling
and Business, and double-click Service and DSCP Mapping. The Service and
DSCP Mapping-List tab is displayed.
2. On the Service and DSCP Mapping-List tab, click . The Service and DSCP
Mapping tab is displayed.
3. On the Service and DSCP Mapping tab, set the parameters of the service and DSCP
mapping, see Figure 5-11.For a description of the parameters, refer to Table 5-8.
Figure 5-11 Service and DSCP Mapping Tab
Table 5-8 DSCP Mapping Parameters
Used IP layer This attribute configures the IP N/A N/A

configuration parameters of bearer services.
If the IpLayerConfig MO is
configured, this attribute must
be configured.
Used bandwidth This attribute configures N/A N/A

resource the bandwidth resources
of bearer services. If the
BandwidthResourceMO is
configured, this attribute must
be configured.
5-18

LTE FDD service This attribute specifies the N/A N/A

DSCP mapping mapping rules between the
LTE FDD service type and
DSCP. It indicates 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 This attribute sets the operator N/A N/A

to which the bandwidth rules
are allocated. If this attribute
is not set, bandwidth control
is not implemented between
operators.
4. Click .
End of Steps
5.6 Creating an OMC Channel

This procedure describes how to create an OMC channel.
Prerequisite
l An NE is created.
Steps
1. In the managed element tree, select Transmission Network > LTE FDD, and
double-click OMC Channel. The OMC Channel-List tab is displayed.
2. On the OMC Channel-List tab, click . The OMC Channel tab is displayed.
3. On the OMC Channel tab, set the parameters of an OMC channel, see Figure 5-12.For
a description of the key parameters, refer to Table 5-9.
5-19

Figure 5-12 OMC Channel Tab
Table 5-9 OMC Channel Parameters
OMC interface link This attribute sets the number [0..7] 0

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.
Interface type of This attribute 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 This attribute sets the IP N/A 0.0.0.0

address of the OMC server.
It must be filled in when
itfUniBtsType is set to the
independent networking mode.
5-20

OMC subnet mask This attribute sets the subnet N/A 255.255.255.255
mask of the OMC server. It is
used when tfUniBtsType is set
to the independent networking
mode.
DSCP This attribute sets the [0..63] 46

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 attribute sets that IP N/A N/A

configuration layer configurations are used.
The IpLayerConfig object is
involved.
Used bandwidth This attribute is used N/A N/A

resource to configure the
bandwidth resource. The
BandwidthResource object is
involved.
4. Click .
End of Steps
5-21

5-22

Chapter 6
Radio Parameter
Configuration
Table of Contents
Configuring LTE FDD Global Parameters ...................................................................6-1
Configuring Baseband Resources ..............................................................................6-3
Configuring a Serving Cell..........................................................................................6-5
6.1 Configuring LTE FDD Global Parameters

This procedure describes how to configure the global parameters of an LTE FDD network.
Prerequisite
Physical resources of an eNodeB are configured.
Steps
1. In the managed element tree, select Radio Parameter and double-click LTE FDD.
The LTE FDD-List tab is displayed.
2. On the LTE FDD-List tab, click . The LTE FDD tab is displayed.
3. On the LTE FDD tab, set the LTE FDD global parameters, see Figure 6-1. For a
description of the key parameters, refer to Table 6-1.
6-1

Figure 6-1 LTE FDD Tab
Table 6-1 LTE FDD Parameters
LTE FDD ID MO instance Identity. A [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 0: Disable, 1: Enable[1]

Switch Enable
Holdover Time-Out Holdover time-out threshold [0..240] 60

Threshold (min)
4. Click .
End of Steps
6-2

Chapter 6 Radio Parameter Configuration
6.2 Configuring Baseband Resources

Before configuring a device transmitting or receiving radio signals, you should configure
baseband resources. This procedure describes how to configure baseband resources
according to radio resource planning.
Prerequisite
LTE FDD global parameters are configured.
Steps
1. In the managed element tree, select Radio Parameter > LTE FDD > Resource
Interface Configuration, and double-click Baseband Resource. The Baseband
Resource-List tab is displayed.
2. On the Baseband Resource-List tab, click . The Baseband Resource tab is
displayed.
3. On the Baseband Resource tab, set the parameters of a baseband resource, see
Figure 6-2.For a description of the key parameters, refer to Table 6-2.
Figure 6-2 Baseband Resource Tab
6-3

Table 6-2 Baseband Resource Parameters
Baseband MO instance Identity, A [1..9999] 1

Resource Distinguished Name (DN) is
Configuration ID used to uniquely identify a
Names (RDNs). See 3GPP TS
32.300.
CP ID Cell Portion Identity [0..5] 0
RF Unit Application This parameter is Normal Mode[0], Normal Mode[0]

Mode used to configure cell Combination
RF unit application Mode[1], Mergence
mode when configuring mode(PB
ECellEquipmentFunction. Networking)[3],
Normal mode means that Mergence Mode
a single RF unit is used. 2[4]
Combination mode means that
more than one RF unit are
combined logically to offer a
single RF unit with multiple
antenna number. Sharing cell
mode means that more than
one RF unit share the same
cell.
Used RRU Used RRU N/A N/A
RF Port Object RF port object. N/A N/A
Connected Baseband Device for Cable N/A N/A

Baseband Device Cascading Connection.
Mapping of This parameter is not [0..3], [15..15] 0

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
6-4

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.
4. Click .
End of Steps
6.3 Configuring a Serving Cell

This procedure describes how to configure the serving cell of an eNodeB.
Prerequisite
Physical resources of an eNodeB are configured.
Steps
1. In the managed element tree, select Radio Parameter > LTE FDD, and double-click
E-UTRAN FDD Cell. The E-UTRAN FDD Cell-List tab is displayed.
2. On the E-UTRAN FDD Cell-List tab, click . The E-UTRAN FDD Cell tab is
displayed.
3. On the E-UTRAN FDD Cell tab, set the parameters of an E-UTRAN FDD cell, see
Figure 6-3, Figure 6-4, and Figure 6-5.For a description of the key parameters, refer
to Table 6-3.
6-5

Figure 6-3 E-UTRAN FDD Cell Tab1
6-6

Table 6-3 E-UTRAN FDD Cell Parameters
E-UTRAN FDD Cell MO instance Identity, A [1..9999] 1

ID Distinguished Name (DN) is
used to uniquely identify a
Names (RDNs). See 3GPP
TS 32.300.
PLMN List PLMN list N/A N/A
Baseband Baseband resource N/A N/A

Resource configuration
Configuration
6-7

PCI This parameter is used to [0..503] 0

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 PCI list that can be allocated. [0..503] 0;0;0;0;0;0;0;0;0;

Only when distributed PCI 0;0;0
allocation is used, this
parameter is valid.
TAC This parameter is used to [0..65535] N/A

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 This parameter sets the 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
Number of Tx This parameter sets the 0: 1, 1: 2, 2: 4 1[0]

Antenna Port in number of an antenna port
Cell in a cell. Transmit diversity
and spatial multiplexing use
multi-antenna ports.
6-8

Band Indication for This parameter sets the [1..5], [7..14], 1

Frequency frequency band for downlink [17..28], [101..101]
and uplink frequency. The
downlink and uplink frequency
must belong to the same band.
Uplink Center Uplink center carrier {freqBandInd==1}[1 {freqBandInd==1}

Carrier Frequency frequency. Baed on Band 920..1980] step 0.1 [1930]
(MHz) Indication for Frequency, {freqBandInd==2}[1 {freqBandInd==2}
the range is different: (1: 850..1910] step 0.1 [1860]
1920-1980, 2: 1850-1910, 3: {freqBandInd==3}[1 {freqBandInd==3}
1710-1785, 4: 1710-1755, 5: 710..1785] step 0.1 [1720]
880-915, 9: 1749.9-1784.9, 710..1755] step 0.1 [1720]
10: 1710-1770, 11: {freqBandInd==5}[8 {freqBandInd==5}
1427.9-1452.9, 12: 698-716, 24..849] step 0.1 [834]
13: 777-787, 14: 788-798, {freqBandInd==7}[2 {freqBandInd==7}
17: 704-716, 18: 815-830, 500..2570] step 0.1 [2510]
21: 1447.9-1462.9, 22: 80..915] step 0.1 [890]
3410-3490, 23: 2000-2020, {freqBandInd==9}[1 {freqBandInd==9}
24: 1626.5-1660.5, 25: 749.9..1784.9] step [1759.9]
1850-1915, 26: 814-849, 27: 0.1 {freqBandInd==1
07-824, 28: 703-748) MHz. {freqBandInd==10 0}[1720]
}[1710..1770] step {freqBandInd==11
0.1 }[1437.9]
{freqBandInd==11 {freqBandInd==1
}[1427.9..1452.9] 2}[708]
step 0.1 {freqBandInd==1
{freqBandInd==12}[ 3}[787]
698..716] step 0.1 {freqBandInd==1
{freqBandInd==20}[ 1}[1457.9]
832..862] step 0.1
6-9

}[1447.9..1462.9] 2}[3420]
{freqBandInd==22 3}[2010]
0.1 4}[1636.5]
}[2000..2020] step 5}[1860]
0.1 {freqBandInd==2
}[1626.5..1660.5] {freqBandInd==2
step 0.1 7}[817]
}[1850..1915] step 8}[713]
0.1 {freqBandInd==1
814..819] step 0.1
{freqBandInd==27}[
807..824] step 0.1
{freqBandInd==28}[
703..748] step 0.1
{freqBandInd==101
}[962..977] step 0.1
Downlink Center Downlink center carrier {freqBandInd==1}[2 {freqBandInd==1}

Carrier Frequency frequency. Based on Band 110..2170] step 0.1 [2020]
(MHz) Indication for Frequency, {freqBandInd==2}[1 {freqBandInd==2}
the range is different: (1: 930..1990] step 0.1 [1940]
1805-1880, 4: 2110-2155, 5: 805..1880] step 0.1 [1815]
925-960, 9: 1844.9-1879.9, 110..2155] step 0.1 [2120]
10: 2110-2170, 11: {freqBandInd==5}[8 {freqBandInd==5}
1475.9-1500.9, 12: 728-746, 69..894] step 0.1 [879]
17: 734-746, 18: 860-875, 620..2690] step 0.1 [2630]
19: 875-890, 20: 791 -821, {freqBandInd==8}[9 {freqBandInd==8}
21: 1495.9-1510.9, 22: 25..960] step 0.1 [935]
3510-3590, 23: 2180-2200, {freqBandInd==9}[1 {freqBandInd==9}
24: 1525-1559, 25: 844.9..1879.9] step [1854.9]
1930-1995, 26: 859-894, 0.1 {freqBandInd==1
27: 852-869, 28: 758-803) {freqBandInd==10}[ 0}[2120]
MHz. 2110..2170] step 0.1
6-10

}[1475.9..1500.9] }[1485.9]
{freqBandInd==21 1}[1505.9]
}[1495.9..1510.9] {freqBandInd==2
step 0.1 2}[3520]
}[3510..3590] step 3}[2190]
0.1 {freqBandInd==2
0.1 5}[1940]
}[1525..1559] step 6}[869]
0.1 {freqBandInd==2
0.1 8}[768]
{freqBandInd==26}[ {freqBandInd==1
859..894] step 0.1 01}[1047]
{freqBandInd==27}[
852..869] step 0.1
{freqBandInd==28}[
758..803] step 0.1
{freqBandInd==101
}[1037..1057] step
0.1
6-11

Downlink System The parameter sets the 0: 1.4 (6RB), 1: 20(100RB)[5]

Bandwidth (MHz) downlink system bandwidth. 3 (15RB), 2: 5
It is used to determine the (25RB), 3: 10
position of frequency for (50RB), 4: 15
downlink physical channel and (75RB), 5: 20
the resource allocation. (100RB)
Uplink System The parameter sets the uplink 0: 1.4 (6RB), 1: 20(100RB)[5]
Bandwidth (MHz) system band width. It is used 3 (15RB), 2: 5
to determine the position of (25RB), 3: 10
frequency for uplink physical (50RB), 4: 15
channel and the resource (75RB), 5: 20
allocation. (100RB)
CFI Selection The parameter sets the CFI 0: Auto-Adjusted, 1: 2[2]

Value configured by high 1, 2: 2, 3: 3, 4: 4
layer for cell. The CFI Value
could be 1, 2, 3 or could be
configured as auto-adjusted.
4. Click .
End of Steps
6-12

Chapter 7
XML Configuration File
Generation
Table of Contents
Generating XML Files for an eNodeB .........................................................................7-1
Generating XML Files for the EMS .............................................................................7-2
7.1 Generating XML Files for an eNodeB

This procedure describes how to generate XML files for an eNodeB. The XML files are
used by debugging engineers for USB or LMT commissioning on the eNodeB side.
Prerequisite
Initial configuration of eNodeB parameters is complete.
Steps
1. Select Configuration Management > Data Synchronization, see Figure 7-1. The
Data Synchronization dialog box is displayed.
Figure 7-1 Data Synchronization Menu
2. In the left pane, select one or more eNodeBs that you want to synchronize. In the right
pane, select Generate synchronization file, see Figure 7-2.
7-1

Figure 7-2 Data Synchronization Dialog Box
3. Click Generate File, and wait until the progress reaches 100%. The Confirm dialog
box is displayed, see Figure 7-3.
Figure 7-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
7.2 Generating XML Files for the EMS

This procedure describes how to generate XML configuration files for the EMS. The XML
configuration files can be used for quick eNodeB commissioning through the EMS.
7-2

Chapter 7 XML Configuration File Generation
Prerequisite
Initial configuration of eNodeB parameters is complete.
Steps
1. Select Configuration Management > Data Export, see Figure 7-4. The Data Export
dialog box is displayed.
Figure 7-4 Data Export Menu
2. In the left pane, select one or more eNodeBs for which you want to generate
configuration files. In the right pane, select Modify area for Data area, and select
XML file for File type. Click Browse and select a path for exporting the files for File
path, and enter the prefix of the exported files in the File name prefix text box, see
Figure 7-5.
Figure 7-5 Data Export Dialog Box
7-3

3. Click Export, and wait until the progress reaches 100%. The Confirm dialog box is
displayed, see Figure 7-6.
Figure 7-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
7-4

Glossary
BBU
- Base Band Unit
BPL
- Baseband Processing for LTE
CC
- Control and Clock Module
CFI
- Control Format Indicator
CPRI
- Common Public Radio Interface
DSCP
- Differentiated Services Code Point
E-UTRAN
- Evolved Universal Terrestrial Radio Access Network
FDD
- Frequency Division Duplex
FS
- Fabric Switch Module
IP
- Internet Protocol
IPv4
- Internet Protocol version 4
IPv6
- Internet Protocol Version 6
LACP
- Link Aggregation Control Protocol
LMT
- Local Maintenance Terminal
LTE
- Long Time Evolution
MTU
- Maximum Transfer Unit
NE
- Network Element

OMC
- Operation & Maintenance Center
PLMN
- Public Land Mobile Network
PM
- Power Module
RDN
- Relative Distinguished Name
SA
- Site Alarm
SCTP
- Stream Control Transmission Protocol
TD-LTE
- Time Division Long Term Evolution
USB
- Universal Serial Bus
XML
- Extensible Markup Language
eNodeB
- Evolved NodeB
II

Sj-20140604172046-024-Zxsdr Uniran Fdd-Lte (v3.20.50) Initial Configuration Guide (Qcell)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sj-20140604172046-024-Zxsdr Uniran Fdd-Lte (v3.20.50) Initial Configuration Guide (Qcell)

Загружено:

Авторское право:

Доступные форматы

ZXSDR UniRAN

FDD-LTE Base Station

Revision No. Revision Date Revision Reason

R2.0 2015-09-29 V3.20.50.32

Those topics have been modified:

l 4.1.2 Creating a PBridge,Figure 4-3 Add PBridge Dialog Box

R1.0 2015-06-15 First edition

Serial Number: SJ-20140604172046-024

Publishing Date: 2015-09-29 (R2.0)

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Chapter 3 Operator Information Configuration ....................................... 3-1

Chapter 4 Physical Resource Configuration ........................................... 4-1

Chapter 5 Network Transmission Configuration ..................................... 5-1

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Chapter 6 Radio Parameter Configuration............................................... 6-1

Chapter 7 XML Configuration File Generation......................................... 7-1

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Configuration Flow Describes the initial configuration flow.

Chapter 2, Initial Management Describes how to configure initial management information.

Chapter 3, Operator Describes how to configure operator information.

Chapter 5, Network Describes how to configure network transmission.

Chapter 6, Radio Parameter Describes how to configure radio parameters.

Note: provides additional information about a

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Figure 1-1 Configuration Flow

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

2.1 Creating a Subnetwork

Figure 2-1 Subnetwork Tab

Table 2-1 Subnetwork Parameter Descriptions

Parameter Description Value Range Default Value

User Label Label of the user. string[0..128] N/A

SubNetwork ID Subnetwork ID, long[0..999999999] N/A

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Figure 2-2 Managed Network Element Tab

Parameter Description Value Range Default Value

Radio Standard Radio standard LTE FDD, TD-LTE, LTE FDD

NE ID Unique ID of the NE. int [0..999999999] 0

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Parameter Description Value Range Default Value

NE Configuration Version of the NE. It should be the same Version

NE Type Identifies the type of B8901A,B8901B,B- B8901A

BBU Type The BBU type is B8200[0], Integration[5]

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Parameter Description Value Range Default Value

NE Maintenance Maintenance status Normal[0], Testing[2], Configuring[3]

Maintenance Status Maintenance status of Normal[0], Testing[2], Testing[2]

NE address IP address used N/A N/A

2.3 Requesting or Releasing Mutually Exclusive

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Releasing Mutually Exclusive Access

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

3.1 Creating an Operator

Figure 3-1 Operator Tab

SJ-20140604172046-024|2015-09-29 (R2.0) ZTE Proprietary and Confidential

Table 3-1 Operator Parameter Descriptions

Parameter Description Value Range Default Value

Operator name Name of the operator string[1..127] N/A