LTE TDD (V3.30.20.00) ENodeB Initial Configuration Guide

Operator Logo
LTE TDD eNodeB Initial

Configuration Guide
Applicable to V3.30.20.00
LTE TDD eNodeB Initial Configuration Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2017 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo and product
names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION.
Other product and company names mentioned herein may be trademarks or trade names of their
respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner
thereof, anyone’s access to this document should not be construed as granting, by implication,
estoppel or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is
subject to continuous update without further notice due to improvement and update of ZTE
CORPORATION’s products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
Shenzhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: 800@zte.com.cn
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. I
Revision History
Product Version Document Version Serial Number Reason for Revision

V3.30.20.00 R1.0 This is the initial release.
Author
Prepared
Date Document Version Reviewed by Approved by
by
Zhou
2016-7-30 R1.0 Guocheng
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. II
Intended audience: Commissioning engineers at the eNodeB side
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ Knowledge and skills Reference material
1 LTE TDD basic theories LTE TDD Basic Theories and Key Technologies
ZXSDR B8300 T100 (V3.30) Multi-Mode Compact
2 Basic knowledge of the B8300
Baseband Pool User Guide
TD-SCDMA ZXSDR B8300&R8928&R31
3 Knowledge about B8300 Installation
Engineering Installation Guide
Follow-up document: After reading this document, you may need the following information.
SEQ Reference material Information
LTE TDD (V3.30.20.00) Networking Principles
1 and Specifications
Networking specifications
LTE TDD (V3.30.20.00) Data Configuration Norm

2 Guide
Data configuration template
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. III
TABLE OF CONTENTS
1 Overview of Site Commissioning .................................................................. 1

1.1 Commissioning Workflow.................................................................................. 1
1.2 Typical Site Topologies..................................................................................... 3
1.3 Commissioning Modes ..................................................................................... 4
2 Data Configurations for Typical Sites ........................................................... 5

2.1 Creating a Subnetwork ..................................................................................... 5
2.2 Creating an NE ................................................................................................. 6
2.3 Creating an Operator ........................................................................................ 9
2.4 System Parameter Configuration .................................................................... 10
2.4.1 Power Saving Parameter ................................................................................ 10
2.4.2 Time Configuration ......................................................................................... 11
2.4.3 SON Function Switch Object .......................................................................... 12
2.4.4 Frequency Adjust Configuration ...................................................................... 13
2.4.5 RRU System Parameters................................................................................ 14
2.5 Device Configuration ...................................................................................... 14
2.5.1 Configuring Boards ......................................................................................... 15
2.5.2 Configuring the RRU....................................................................................... 22
2.5.3 Configuring the Power Device Set .................................................................. 24
2.5.4 Configuring the Clock Device .......................................................................... 27
2.5.5 Configuring the Dry Contact............................................................................ 35
2.6 Configuration of BTS Auxiliary Peripheral Devices ......................................... 43
2.6.1 Antenna Service Function ............................................................................... 43
2.6.2 Configuring Optical Cables ............................................................................. 48
2.7 Transport Network Configuration .................................................................... 50
2.7.1 Configuring the Physical Layer Port ................................................................ 50
2.7.2 Configuring the Ethernet Link Layer ................................................................ 52
2.7.3 Configuring the IP Layer ................................................................................. 53
2.7.4 Configuring a Static Route(optional) ............................................................... 54
2.7.5 Configuring the Bandwidth Resource Group ................................................... 55
2.7.6 Configuring the SCTP Link ............................................................................. 56
2.7.7 Configuring Multi-Homing for the SCTP Link................................................... 59
2.7.8 Configuring Service and DSCP Mapping ........................................................ 60
2.7.9 Configuring the OMCB .................................................................................... 61
2.8 Radio Parameter Configuration....................................................................... 62
2.8.1 LTE TDD ........................................................................................................ 62
3 Advanced Function Configuration .............................................................. 78

3.1 Cell Aggregation and Super Cell ..................................................................... 78
3.1.1 Configuring LTE Super Cell ............................................................................ 78
3.1.2 Modifying Radio Parameters of the LTE Super Cell ........................................ 80
3.1.3 Configuring a LTE Super Cell Crossing Boards .............................................. 81
3.2 Configuring Two Carriers ................................................................................ 81
3.2.1 Configuring Two Carriers for the BPL1+8964 S2300 ...................................... 82
3.3 Configuring a CA ............................................................................................ 84
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. IV
3.3.1 Configuring Neighbor Cell Relations ............................................................... 84

3.3.2 Configuring CA Coordination Relations........................................................... 86
4 Typical Cases................................................................................................ 89
4.1 B8200+BPL1+R8962/R8972EB8200+BPL1+R8962/R8972E ......................... 89
4.2 B8200+BPL1+R8964/ R8984 ......................................................................... 92
4.3 B8200+BPL1+R8978 ...................................................................................... 94
4.4 B8200+BPN2+R8502 S2600/ S2300/S2600U ................................................ 97
4.5 B8300+BPL1+A8712 M192026 .................................................................... 100
5 Version Limit and Legacies ....................................................................... 102

5.1 Version Limit ................................................................................................. 102
5.2 Legacies ....................................................................................................... 103
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. V
FIGURES
Figure 1-1 Commissioning Workflow .................................................................................... 1

Figure 1-2 Typical Outdoor Site Configurations .................................................................... 3
Figure 2-1 Creating a Subnetwork ........................................................................................ 6
Figure 2-2 Creating an NE ................................................................................................... 8
Figure 2-3 Operator.............................................................................................................. 9
Figure 2-4 PLMN .................................................................................................................. 9
Figure 2-5 Power Saving Parameter .................................................................................. 10
Figure 2-6 Enabling the Power Saving Switch .................................................................... 11
Figure 2-7 Time Configuration ............................................................................................ 11
Figure 2-8 SON Function Switch Object ............................................................................. 12
Figure 2-9 Configuration for auto-setup transmission switch .............................................. 13
Figure 2-10 Frequency Adjust Configuration ...................................................................... 13
Figure 2-11 Rack Graph ..................................................................................................... 14
Figure 2-12 Configuration Specifications of the B8300 ....................................................... 15
Figure 2-13 Configuration Specifications of the B8200 ....................................................... 15
Figure 2-14 Add CC board ................................................................................................. 16
Figure 2-15 Add SA board.................................................................................................. 17
Figure 2-16 Change to smart FAN ..................................................................................... 17
Figure 2-17 Add PM ........................................................................................................... 18
Figure 2-18 Adding an FS5C .............................................................................................. 19
Figure 2-19 Configuring the FS5C ...................................................................................... 19
Figure 2-20 Adding a CR0.................................................................................................. 20
Figure 2-21 Configuring the CR0........................................................................................ 20
Figure 2-22 Configuring the BPN2 ..................................................................................... 21
Figure 2-23 Configuring the Optical Port on the BPN2 ....................................................... 22
Figure 2-24 Adding an RRU ............................................................................................... 23
Figure 2-25 UL Connection Mode of the RRU .................................................................... 24
Figure 2-26 Configuring the Power Working Mode ............................................................. 25
Figure 2-27 Clock Device Set Dialog Box........................................................................... 27
Figure 2-28 Clock Device ................................................................................................... 28
Figure 2-29 1PPS+TOD Clock Device ............................................................................... 29
Figure 2-30 Clock Device Set of the Upper Level eNodeB ................................................. 30
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. VI
Figure 2-31 1588 Clock Configuration Options ................................................................... 31

Figure 2-32 1588 Clock Global Parameter ......................................................................... 32
Figure 2-33 IP Clock Parameters ....................................................................................... 33
Figure 2-34 Clock Device ................................................................................................... 34
Figure 2-35 Configuring the UCI Board in Slot No.7 ........................................................... 35
Figure 2-36 Clock Device Dialog Box ................................................................................. 35
Figure 2-37 Configuring the Dry Contact Device on the SA Board ..................................... 36
Figure 2-38 Dry Contact Device Tab Page ......................................................................... 38
Figure 2-39 Configuring the Dry Contact Device on the RRU ............................................. 38
Figure 2-40 Dry Contact Device Tab Page ......................................................................... 39
Figure 2-41 Monitoring Cable of the Dry Contact ............................................................... 40
Figure 2-42 Dry Contact Cable ........................................................................................... 41
Figure 2-43 Specifications of the Dry Contact Cable .......................................................... 41
Figure 2-44 Dry Contact Cable of the RRU ........................................................................ 42
Figure 2-45 Antenna Attribute Object ................................................................................. 43
Figure 2-46 Antenna Attribute Object ................................................................................. 44
Figure 2-47 Antenna Entity Object ..................................................................................... 45
Figure 2-48 RF Cable ......................................................................................................... 46
Figure 2-49 R8964 RF Cable ............................................................................................. 46
Figure 2-50 Ir Antenna Group Object ................................................................................. 47
Figure 2-53 Configuring the Fiber Cable ............................................................................ 49
Figure 2-54 Fiber Cable-List ............................................................................................... 49
Figure 2-56 Configuring the Cascaded Fiber Cable for the R8962 ..................................... 50
Figure 2-57 Configuring the Physical Layer Port ................................................................ 51
Figure 2-58 Used Ethernet ................................................................................................. 52
Figure 2-59 Ethernet parameter configuration .................................................................... 52
Figure 2-60 Configuring the Ethernet Link Layer ................................................................ 53
Figure 2-61 Configuring the IP Address ............................................................................. 54
Figure 2-62 Configuring the IP Address ............................................................................. 54
Figure 2-63 Configuring a Static Route .............................................................................. 55
Figure 2-64 Configuring Bandwidth Resource Group ......................................................... 56
Figure 2-65 Configuring the Bandwidth Resource .............................................................. 56
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. VII
Figure 2-66 Configuring the SCTP Link .............................................................................. 57

Figure 2-67 Configuring the SCTP Link over X2 ................................................................. 58
Figure 2-68 Configuring Dual-Homing for the SCTP Link ................................................... 59
Figure 2-69 Configuring Service and DSCP Mapping ......................................................... 60
Figure 2-70 Configuring LTE TDD service and DSCP mapping.......................................... 61
Figure 2-71 OMC Channel ................................................................................................. 62
Figure 2-72 Creating a LTE TDD Network .......................................................................... 63
Figure 2-73 Creating the Baseband Resource ................................................................... 65
Figure 2-74 Board Application Attribute .............................................................................. 66
Figure 2-75 LTE Cell Parameter-1 ..................................................................................... 71
Figure 2-79 Entering “Neighbor Cell Management” ............................................................ 74
Figure 2-80 Selecting the Cells to be Configured as Neighboring Cells .............................. 75
Figure 2-81 Adding a Neighboring Cell Relation ................................................................. 75
Figure 2-82 Neighboring Cell Information of Site No. 201................................................... 76
Figure 2-83 Neighboring Cell Information of Site No. 373865 ............................................. 77
Figure 2-84 E-UTRAN Neighbor Relation ........................................................................... 77
Figure 3-1 Opening the Super Cell Management Interface................................................. 79
Figure 3-2 Combining Normal Cells into a Super Cell ........................................................ 80
Figure 3-3 Configuring a CR0 Board .................................................................................. 81
Figure 3-4 Configuring the First Baseband Resource ......................................................... 82
Figure 3-5 Creating the Second Baseband Resource ........................................................ 83
Figure 3-6 Creating the Baseband Resource-List ............................................................. 83
Figure 3-7 Creating a LTE TDD Cell................................................................................... 84
Figure 3-8 Entering Neighbor Cell Management ................................................................ 85
Figure 3-9 Configure Neighbor Relation Tab Page ............................................................. 85
Figure 3-10 Modifying Parameters of Neighboring Cells..................................................... 86
Figure 3-11 Entering Cell Coordination Management ......................................................... 87
Figure 3-12 Cell Coordination Management Cell ................................................................ 87
Figure 3-13 Setting Cooperative Relationship Type of Two Cells to DL CA ........................ 88
Figure 3-14 Viewing the Result of a Formed DL CA ........................................................... 88
Figure 4-1 Configuring the BPL1 Board.............................................................................. 89
Figure 4-2 Configuring the Optical Port on the BPN1 ......................................................... 90
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. VIII
Figure 4-3 Configuring the R8962 ...................................................................................... 90

Figure 4-4 Configuring the Optical Port Device Set of the RRU .......................................... 90
Figure 4-5 Configuring the Fiber Cable .............................................................................. 91
Figure 4-6 Configuring the Antenna Entity Object............................................................... 91
Figure 4-7 Configuring the RF Cable .................................................................................. 91
Figure 4-8 Configuring the Ir Antenna Group Object .......................................................... 91
Figure 4-9 Configuring the BPN1 ....................................................................................... 92
Figure 4-10 Configuring the Optical Port on the BPN1 ....................................................... 92
Figure 4-11 Configuring the R8964 S2300 ......................................................................... 93
Figure 4-12 Configuring the Optical Port Device Set of the RRU ........................................ 93
Figure 4-14 Configuring the Antenna Entity Object............................................................. 94
Figure 4-15 Configuring RF Cables .................................................................................... 94
Figure 4-16 Configuring the Ir Antenna Group Object ........................................................ 94
Figure 4-17 Configuring the BPL1 ...................................................................................... 95
Figure 4-18 Configuring the Optical Port Device on the BPL1 ............................................ 95
Figure 4-23 Configuring the RF Cable ................................................................................ 97
Figure 4-24 Configuring the Ir Antenna Group Object ........................................................ 97
Figure 4-25 Configuring the BPN2 ..................................................................................... 98
Figure 4-26 Configuring Optical Ports on the BPN2 ........................................................... 98
Figure 4-29 Configuring Optical Cables .............................................................................. 99
Figure 4-31 Configuring the RF Cable .............................................................................. 100
Figure 4-32 Configuring the Ir Antenna Group Object ...................................................... 100
Figure 4-33 Antenna Entity Object ................................................................................... 101
Figure 4-34 RF Cable ....................................................................................................... 101
Figure 4-35 Ir Antenna Group Object ............................................................................... 101
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. IX
TABLES
Table 1-1 Typical Outdoor Site Configurations ..................................................................... 3

Table 2-1 CCE1 Port No. ................................................................................................... 16
Table 2-2 PM Configuration Table ...................................................................................... 25
Table 2-3 Power and Board Power .................................................................................... 26
Table 2-4 Signal Table of the Dry Contact Cable ............................................................... 42
Table 2-5 An Example of IP Address Planning ................................................................... 53
Table 2-6 An Example of the Association Parameter ......................................................... 57
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. X
LTE TDD eNodeB Commissioning Guide
1 Overview of Site Commissioning
1.1 Commissioning Workflow
The workflow of parameter configurations are shown in the figure below:
Figure 1-1 Commissioning Workflow
ZTE Confidential & Proprietary. © 2017 ZTE CORPORATION. All rights reserved. 1
1.2 Typical Site Topologies
The typical outdoor site configurations are shown in Figure 1-2.Descriptions of data
configurations in Chapter 2 will be based on the typical outdoor scenario. Data
configuration methods among different scenarios are similar.
Figure 1-2 Typical Outdoor Site Configurations
Typical site configurations for outdoor scenarios are shown in Figure 1-2. For
configuration details, see Table 1-1.
Table 1-1 Typical Outdoor Site Configurations
SN Material Name Qty Remarks

The 1.25G GE optical modules or Ethernet
1 CC 1 cables and transmission devices are used
for interconnection.
The BPL1 board is preferentially configured

at slot No. 9. The three optical ports map to
2 BPL1/BPN2 1 their corresponding R8964 devices in
sections 1, 2, and 3. 10 G modules are
used.
3 PM 1
1.3 Commissioning Modes
1. PnP commissioning
The PnP commissioning enables the DHCP server on the OMMB and the PnP policies
are configured on the EMS. That is, the site data and version are configured on the OMC
side before they are automatically downloaded to the eNodeB.
SOW analysis: This is most efficient commissioning mode and is thus highly
recommended as no supervisor is required on site.
For details about how to perform PnP commissioning, refer to the LTE TDD (V3.30.20.00)
eNodeB Ukey Commissioning Guide.
2. USB commissioning
Use the Umaker tool to write configured site data and version into the Ukey. The Ukey is
then directly connected to the eNodeB on site for data and version uploading to perform
site commissioning.
SOW analysis: Ukey commissioning is very efficient for single site scenarios. A
supervisor is required on site, he is unnecessarily a master of technical skills, though.
Such commissioning mode is recommended in scenarios where PnP commissioning is
impossible.
For details about how to perform Ukey commissioning, refer to the LTE TDD
(V3.30.20.00) eNodeB Ukey Commissioning Guide.
3. LMT commissioning
Use the Ethernet cable to connect to the eNodeB directly, and use the LMT tool to upload
the configured site data and version to the eNodeB side to perform site commissioning.
SOW analysis: LMT commissioning is inefficient for single site scenarios. A highly-skilled
supervisor is required on site. Such commissioning mode is recommended in scenarios
where neither PnP nor Ukey commissioning is impossible.
This document is SOP-based and thus all procedures are described in detail. It is
oftentimes applicable to the first site commissioning of a network.
For details about how to perform LMT commissioning, refer to the LTE TDD (V3.30.20.00)
eNodeB LMT Commissioning Guide.
2 Data Configurations for Typical Sites
 Note:
1. After the parameter is added, click to return its upper level node.
2.1 Creating a Subnetwork
[User Label]: This parameter is set as planned.
[SubNetwork ID]: The subnetwork IDs under one OMMB cannot be duplicated. To
configure multiple subnetworks, click the “Recommended” button.
[SubNetwork Type]: select AN[1]. (This setting is applicable to scenarios where no RNC
is available.)
Figure 2-1 Creating a Subnetwork
2.2 Creating an NE
Right-click the subnetwork node, and you can create the eNodeB. The main parameters
are described below:
[Radio Standard]: Select the network according to actual needs; for the LTE TDD single
mode scenario, select LTE TDD.
[NE ID]: This parameter is entered as planned. Note that this parameter needs to be
unique in the entire network.
[NE Configuration Data Version]: Select the version where the NE pertains to.
[NE Type]: The BS8700 is universally accepted as the TDD platform version NE type.
[BBU Type]: Select the BBU subrack type according to the actual BBU subracks available
at the eNodeB side. For the 3U subrack, select B8300, for the 2U
subrack, select B8200.
[NE Maintenance Status]: This parameter includes NE Maintenance Status and

Maintenance Status of LTE TDD.
 NE Maintenance Status includes commissioned {Normal},

uncommissioned {Configuring}, debugging {Testing}, alarm
debugging {FM Testing}, and performance debugging {PM Testing}.
 Maintenance Status of LTE TDD includes commissioned {Normal},

debugging {Testing}, alarm debugging {FM Testing}, and
performance debugging {PM Testing}.
In which, this NE Maintenance Status has an “AND” relation with the OM

status of the other two standards. To be specific, whether alarms or
performance data of a radio standard need to be reported to the EMS
depends on both the NE maintenance status and the OM status of the
corresponding radio standards. That is, whatever the commissioning status
of the radio standards are, when the NE OM status is “debugging”, neither
alarms nor performance data will be reported; when the status of a radio
standard is “debugging”, however, alarms of such radio standard will not be
reported.
Whether the eNodeB is connected to the OMC depends only on the NE

maintenance status, though. When the NE maintenance status is
“uncommissioned”, no connection will be established. The connection
between the eNodeB and the OMC succeeds in all the other applications,
though.
Alarm debugging: NE alarms in such status will not be reported to the

EMS.
Performance debugging: NE performance data in such status will not be

reported to the EMS.
[NE running mode]: Master and slave, Radio standard load sharing, service load
sharing
 For the single CC board scenario, apply the master and slave mode.
 If two CC boards are configured for TD LTE, apply service load

sharing mode.
 If two CC boards are configured and that CC boards support

difference network standards, such as one CC board running TD
LTE and other running FDD LTE, apply the radio standard load
sharing mode.
[NE External IP]: enter the OM IP of the eNodeB.
Use the planned OMC OM IP.
[NE ID Planned by Operator]: enter the content as planned.
[NE ID Planned by Vendor]: enter the content as planned.
[Automatically obtain longitude and latitude]: This parameter is No by default. You need
to change it to Yes before the northbound data reporting succeeds.
Figure 2-2 Creating an NE
2.3 Creating an Operator
Select Modify Area > Operator and double-click Operator to enter the Operator-List
tab page. Click to add an operator. The main parameters are described below:
[Operator name]: indicates the name of the operator.
Figure 2-3 Operator
Figure 2-4 PLMN
[MCC]: Enter the code as planned. Improper entry will cause failure to pass
authentication.
[MNC]: Enter the code as planned. Improper entry will cause failure to pass
authentication.
2.4 System Parameter Configuration
2.4.1 Power Saving Parameter
Keep the system parameters as their default values. The power saving switch is Close by
default. You need to negotiate with the business and R&D staff if you need to enable the
switch as this is a pre-paid function and that some functions need specific instructions
from the R&D staff. The description here serves as just a reference.
[RRU channel power saving switch]: indicates the power saving for RRU timeslots. It is
achieved through the blocking of some RRU channels.
[PA static voltage adjustment switch]: This function enables the PA of the RRU to adjust
its TX power according to the load of traffic so as to save power. You need to consult the
product support engineers if you want to enable this switch.
Keep the other parameters unchanged.
Figure 2-5 Power Saving Parameter
If the power saving function is enabled, “Start time…” and “End time…” will appear in the
data configuration.
Such period indicates the power saving time. As shown in the figure below, such function
is recommended to be enabled in idle hours such as between 00:00 and 06:00 am.
Figure 2-6 Enabling the Power Saving Switch
2.4.2 Time Configuration
[NTP server IP address]: indicates the address of the primary SNTP server. In cases
when the OMM is in dual-server configurations, it corresponds to the OMMB
address of the primary server.
[SNTP standby server IP address]: indicates the address of the secondary SNTP server.
In cases when the OMM is in dual-server configurations, it corresponds to the
OMMB address of the secondary server.
Figure 2-7 Time Configuration
2.4.3 SON Function Switch Object
SON Function Switch Object: is applied to PNP commissioning in most cases.
The SON function involves four switches:
[Configuration for hardware auto-discovery switch]: This switch is used by the OMC to
automatically discover the RRU and BBU boards. This switch is disabled by default.
[Configuration for auto-commissioning switch]: This switch is exclusive to GU products

and is disabled by default.
[Configuration for auto-setup transmission switch]: This parameter should be modified as

Enable FE auxiliary establishment of chain[2].
[Configuration for data rollback switch]: This switch is enabled by default. When a cutover
is performed, this function enables data configuration rollback of the transmission
channel.
Figure 2-8 SON Function Switch Object
Figure 2-9 Configuration for auto-setup transmission switch
2.4.4 Frequency Adjust Configuration
The universal settings of the LTE TDD single-mode scenario are described below:
Use the default values.
 For the band D and band E RRUs, their adjustment mode is “Manual” and its
adjustment value=0.
Figure 2-10 Frequency Adjust Configuration
2.4.5 RRU System Parameters
The LTE TDD single-mode site needs no such configuration item.
2.5 Device Configuration
Select Modify Area > Device and double-click Device to enter the Rack Graph tab page.
Add the other boards and RRU according to actual needs at the eNodeB side.
Figure 2-11 Rack Graph
 Note:
Check whether the controlling board is the CCC board (the CC15 and CC16 are in
most cases the CCC board) or the CCE1 board. Currently, the common LTE TDD
boards include the following:
Switch board: FS5C, CR0
TDL baseband board: BPL1, BPN2.
Note that you need to configure the boards according to actual needs at the eNodeB
side.
The B8300/B8200 configuration specifications are shown in the figures below:
Figure 2-12 Configuration Specifications of the B8300
Figure 2-13 Configuration Specifications of the B8200
2.5.1 Configuring Boards
2.5.1.1 Configuring CC Board
Right click the rack graph slot 1 and choose add board.
The parameters:
[Board type]: Choose the controlling board type.
CC3: Choose CC;
CC16: Choose CCC;
CCE1: Choose CCE1;
[Board standard]: ALL[0].
[Board function mode]: Common[0].
Figure 2-14 Add CC board
1. CCE1 port:
The panel of the CCE1 board provides three electrical ports and two optical
ports. Its corresponding port No. on the OMC is 0\1\2\3\32. The mapping relations
are shown in the table below:
Table 2-1 CCE1 Port No.
CCE1 Port ETH0 ETH1 ETH2 ETH3 DEBUG

(Electric (Electric (Optical (Optical (Electrical
Version No. al Port) al Port) Port) Port) Port)
V3.30.20.00 0 1 2 3 32
If only one physical transmission link(electric or optical), the eth0 or eth2 should
be used priority. Connect the cable to the port that is configured on the OMC. For
example, if electrical port No. 0 is configured on the OMC, you need to connect the
Ethernet cable to eth0; likewise, if optical port No.2 is configured on the OMC,
connect the fiber cable to eth2.
2.5.1.2 Configuring SA
Right click the rack graph slot 13 and choose add board. If the SA board deleted, the
common FAN will be deleted together.
Figure 2-15 Add SA board
2.5.1.3 Configuring smart FAN
If configuring the smart FAN, need to add the SA board first, and the common FAN will be
created automatic by system, then right click the FAN and choose “Change to FAB”, and
delete the SA finally.
Figure 2-16 Change to smart FAN
2.5.1.4 Configuring PM
PM board can be configured only in slot 14 and slot 15; and PMAC only in slot 15.
[Board type]: PM or PMAC. Configuring according the actual board type in the BBU.
Figure 2-17 Add PM
2.5.1.5 Configuring the switch board
When inter-board interactivity is required between the baseband boards or that the
CloudRadio function is enabled, you need to configure the switch board. The B8300 can
be configured slot No. 3 or slot No. 4; the B8200 can only be configured in slot No.3.
1. FS5C
The parameter configurations on the OMC are described below:
[Board type]: FS
[Board standard]: ALL
[Board function mode]: LTE-TDD CloudRadio
[Physical Board name]: FS5C[8]
Figure 2-18 Adding an FS5C
Figure 2-19 Configuring the FS5C
2. CR0
The CR0 board can only be configured in slot No.3 or slot No.4. The CR0 supports
LTE TDD carrier switch and CloudRadio functions.
[Board type]: CR0
[Board standard]: ALL
[Board function mode]: LTE-TDD CloudRadio
Figure 2-20 Adding a CR0
Figure 2-21 Configuring the CR0
2.5.1.6 BPN2 Baseband Board
1. Adding a BPN2 board:

[Board type]: BPN2
[Board standard]: LTE-TDD [32]
[Board function mode]: Select either LTE-TDD Single Mode or LTE-TDD Single
Mode (IQ Compressed).
Figure 2-22 Configuring the BPN2
2. Optical Port of the BPN2
The default optical port on the BPN2 is 6G by rate. Change the configuration when
necessary.
Figure 2-23 Configuring the Optical Port on the BPN2
3. Difference between the BPN2 and the BPN1 in terms of functions:

The BPN2 provides six optical ports (6G/10G by rate), and thus six to eight
channels of a LTE TDD cell can be established at the same time on one
BPN2.When configuring baseband resources and associating baseband devices,
the BPN2 involves two baseband resources: BpDevice1 and BpDevice 2.
BpDevice1 can be configured globally as selection of the chip is executed by the
control panel at the eNodeB side.
The BPN2 provides two chips and six optical ports ranging from 0 to 5, with the
previous three optical ports mapping to the first chip and the latter three optical ports
mapping to the second chip. At most one RRU is allowed for connection across
chips when the RRU is connected to the BPN2 in dual-optical association mode.
2.5.2 Configuring the RRU
1. Add an RRU
Click in the rack graph to add the rack and board of the RRU. The Add RRU dialog
box will be displayed. The RRU rack No. can be automatically generated. Alternatively,
you may also enter it by yourself. Note that the Rack No. ranges from 51 to 107, as
defined by the coding principles at the eNodeB side.
[Rack No.] The coding for the single-mode LTE RRU ranges from 51 to 70.
 [Board standard]: LTE-TDD [32]
 [Board function mode]: LTE-IR
Figure 2-24 Adding an RRU
2. Configure the Optical Port Device Set for the RRU
[Uplink connection mode]: This is relevant with the optical fiber connection mode. It is
single up-link optical line by default.
Parameter configuration principles:
 When a single up-link optical line is used for the RRU to connect to the baseband
board: select single up-link optical line.
 When the RRUs are cascaded: select single up-link optical line.
 When dual-optical cables are connected from the RRU to the BPN2, select multiple
load-sharing optical line.
Figure 2-25 UL Connection Mode of the RRU
2.5.3 Configuring the Power Device Set
2.5.3.1 Configuring the PM
When two PM modules are configured, you need to change the working mode of each
PM to Load-sharing mode. For configuration limits and board power consumption of the
PM, refer to the LTE TDD (V3.30.20.00) Networking Principles and Specifications.
[Power working mode]:
 For a single PM, select the Master/slave mode.
 For two PM modules, select Load-sharing mode.
Figure 2-26 Configuring the Power Working Mode
2.5.3.2 Power Configuration Principles
The publicly admitted maximum number of boards supported by a variety of

combinations of the PM9, the PM10, and PMAC is shown in the table below:
Table 2-2 PM Configuration Table
Number of BPL1 Boards

Number
Equipment Room Non-Equipment Room
Combination of FS
(Temperature: Environment (Temperature:
Boards
below 30℃) below 55℃)
PM9 0 2 2
PM9+PM10 1 5 3
PM9+PM9 0 4 4
3 (The BPL1 board should be
PM9+PM9 1 3 configured in slot No. 11 and
slot No. 12.)
PM10 0 4 4
PM10+PM10 0 6 5
PM10+PM10 1 5 1
PSU (PMAC) 0 4 4
PSU (PMAC) 1 3 3
Note:
 PM9 supports 300 W, PM10 supports 500 W, the PSU supports 550 W, and the
PMAC supports 500 W.
 PM10+PM10 support the power supply of the B8300 in its maximum configuration.
 When AC power supply is provided, use PMAC as a preference. When the number
of baseband boards exceeds four, use the PSU.
The maximum number of boards is calculated according to the table above. As to the
power of different boards, the recommended values are listed below for reference. Note
that the public power of 98 w is reserved by the BBU for the CC16+FA+SA, and the
public power of 108 w is reserved by the BBU for the CCE1+FA+SA. When two power
boards are inserted, each power board will reserve for the public power.
Table 2-3 Power and Board Power
Board Type Board Name Power of V3.30 (Unit: W)
PM8/PM9 300
Output of the
PM10 500
power board
PMAC(3U) 500
Power reservation Reservation (CC x 2 + FA + SA) 98
CC3/CC16 25
CCE1 60
Reservation
SA 3
calculation
SE 5
FAN(3U) 45
FS1 15
FS5C 55
BPL1 85
Peripheral board
BPN0 65
BPN2 80
UES 15
NIS 15
UCI 15
2.5.4 Configuring the Clock Device
Before configuring the clock device, you need to configure the clock device set of the
parent node according to the supported radio standards and synchronization modes.
As shown in the figure below：
[Clock synchronization mode]: Phase synchronization (Note that “Phase synchronization”

needs to be selected for TDD)
Select all the other parameters according to the actual applications or keep the default
settings.
Figure 2-27 Clock Device Set Dialog Box
The clock configuration is started only after the parent node of “clock device set” is
configured. You need to select only one among the synchronization modes: the GPS,
1PPS+TOD, and 1588 clock.
2.5.4.1 Configuring the GPS Clock
[Clock reference resource category]: GNSS clock. GNSS is shortened from the Global
Navigation Satellite System. Currently, the GNSS includes GPS from the
USA, GLONASS from Russia, Galileo system from the EU, and
Compass (Beidou) from China.
[Priority]: “1” indicates the highest priority. When the GPS clock is faulty, this priority
mechanism will ensure automatic switch from the highest priority option
to a second highest priority option.
[GNSS cable length]: set the length of the GPS cable. This should be entered according
to actual conditions.
[GNSS receiver working type]: This is automatically generated.
[Minimum number of search stars]: 4
Figure 2-28 Clock Device
2.5.4.2 Configuring the 1PPS+TOD Clock
When the eNodeB needs to apply TOD as its clock source, its upper level eNodeB
needs to export 1PPS+TOD, which combines the two levels of eNodeBs using the clock
cable.
[Clock reference resource category]: 1PPS+TOD
Figure 2-29 1PPS+TOD Clock Device
Change Clock cascading output type to 1PPS+TOD Channel 1 Output, a shown in the
figure below:
Figure 2-30 Clock Device Set of the Upper Level eNodeB
2.5.4.3 Configuring the 1588 Clock
The 1588 clock has some connections with transmission. If no transmission is

configured, the physical layer port and the Ethernet link layer need to be configured. The
fact is the field must be configured with transmission. Thus, the previous two items need
no repetitive configurations.
Figure 2-31 1588 Clock Configuration Options
After the transmission configurations are finished, you need to select IP Transport > IP
Clock to configure 1588 Clock Global Parameter and IP Clock Parameters before
configuring the 1588 clock in Clock Device.
1. 1588 Clock Global Parameter
Figure 2-32 1588 Clock Global Parameter
Add one 1588 Clock Global Parameter record. Keep the default settings. The
parameters are described below:
[1588 clock device type]: includes an ordinary clock and a boundary clock. For the
boundary clock, the upper level 1588 clock of this device is taken as the reference clock
for its lower level device. For the ordinary clock, the clock acts only as the main clock
(serving the 1588 clock reference for the other devices) or as the secondary clock (using
the 1588 clock reference provided by the main clock).In this scenario, an ordinary clock is
applied by default.
[1588 link selecting mode]: This parameter should be consistent with that at the PTN
side.
2. IP Clock Parameters
Figure 2-33 IP Clock Parameters
Clock Device
Configure relevant parameters under IP Clock Parameters.
[PTP network protocol]: For layer 2 networking, select Ethernet[3]; for layer 3 networking,
select IPv4 or IPv6.
[PTP port mode]: “Master” is set by default at the PTN side; “Slave” is set by default at the
eNodeB side.
[Used Ethernet link]: Select the actual Ethernet link of the eNodeB.
The VLAN ID, the 1588 clock used UDP, and the used bandwidth resources need not to
be configured when the Ethernet protocol is applied.
3. Configure the 1588 clock in Clock Device.
Figure 2-34 Clock Device
If the 1588 clock does not work when the previous configurations are finished, you may
change Announce packet that supports the protocol to “No” to check whether it works
properly upon such operation.
[Clock reference resource category]: 1588 clock[4].
[Clock reference resource type]: SyncE+1588 clock[10]. Keep the others the default
settings.
2.5.4.4 Configuring the Remote GPS Clock
To configure the remote GPS clock, you need to configure the UCI board in slot No.7,
which is connected to the upper level remote GPS device, that is, the RGB. For
configuring the external backplane for the remote GPS in dual-CC load sharing mode,
both CC boards need to be configured.
[Clock reference resource category]: GNSS clock.
[Clock reference resource type]: external backplane GNSS.
[GNSS receiver hardware type]: UCI_RGPS.
[GNSS receiver working type]: This is automatically generated.
[GNSS cable length]: set the length of the GPS cable. This should be entered according
to actual conditions.
Figure 2-35 Configuring the UCI Board in Slot No.7
Figure 2-36 Clock Device Dialog Box
2.5.5 Configuring the Dry Contact
The following operations are performed in the case where BBU dry contacts or RRU dry
contacts are required to monitor the complex environment alarm status of the BBU or
RRU. The OMC configurations and main cable configurations are provided in this section;
for connections of external cables, refer to relevant engineering installation documents.
2.5.5.1 Dry Contact Configurations
As shown in the figure below, the BBU dry contact is configured on the SA board.
Figure 2-37 Configuring the Dry Contact Device on the SA Board
Select Dry Contact Device. As shown in the figure below, the most important
parameters are described below:
[Object ID of dry contact device]: This parameter records the number of dry contact
devices. It starts coding from 1 and is only used on the OMC. Thus, data at the eNodeB
side will not be affected.
[Dry contact description]: This parameter specifies the functions and features of a dry
contact. The function is revealed when you customize the dry contact alarm as the alarm
name is not provided by the system when a dry contact alarm is customized. In such
scenario, only “customized dry contact xx” (“xx” indicates the number) will be shown.
Thus, to identify the type of the alarm, a dry contact description is required.
[Dry contact number]: This parameter is required to start coding from 0 to 15. This
parameter is the dry contact ID actually used at the eNodeB side. The alarms are
identified according the dry contact number. For example, the dry contact number of the
water alarm is 0, the dry contact number of the smoke alarm is 1, the dry contact cables
will be led to the corresponding ports. Either a decimal or a hexadecimal can be used as
the number. That is, when 0 is reported, the eNodeB will be notified of a water alarm;
when 1 is reported, the eNodeB will be notified of a smoke alarm.
[Dry contact type]: Two options are provided: Input dry contact and Output dry contact.
When it is set to “Input dry contact”, signals of the monitoring device are imported to the
BBU through the SA board. The monitoring is performed on the OMC. When it is set to
“Output dry contact”, the dry contact signals collected are forwarded to the upper level
monitoring device through the SA board. For example, a third party device is applied to
monitor the alarm signals of the BBU.
[Alarm status]: Two options are provided: Alarm when closed and Alarm when opened.
When it is set to Alarm when closed, the dry contact alarm will not be reported to the
OMC; Otherwise, it will be reported to the OMC.
[Is Customized dry contact alarm]: “No” and “Yes” are provided as options. “No” indicates
the standard system alarm, that is, the customized “alarm name” can be found in “dry
contact alarm name”; “Yes” indicates that no alarm name is provided by the system.
Therefore, only “customized dry contact xx” (“xx” indicates the number) can be found in
“dry name alarm name”. Dry contact description is required in such scenario.
One SA board can be configured with at most eight dry contact devices. If more than
eight dry contact devices are configured, you may add the SE board. Likewise, the SE
board can generate a maximum of eight records with similar configuration method to the
SA board. Therefore, you can infer that the total number of dry contact devices cannot
exceed 16.
Figure 2-38 Dry Contact Device Tab Page
The dry contact configurations of the RRU correspond to the dry contact devices on
it.
Figure 2-39 Configuring the Dry Contact Device on the RRU
The main parameters are same to that of the BBU.
[Dry contact type]: select the input dry contact.
[Alarm status]: Select either Alarm when closed or Alarm when opened depending
on scenarios.
[Is customized dry contact alarm]: Yes or No.
[Dry contact alarm name]: Set the parameter according to actual applications.
Figure 2-40 Dry Contact Device Tab Page
2.5.5.2 Dry Contact Cables
BBU dry contact:
For the indoor macro eNodeB, the dry contact monitoring cable directly connects to the
SA board of the B8300, with its appearance shown in the figure below:
Figure 2-41 Monitoring Cable of the Dry Contact
The end A of the dry contact cable is SCSI50 connector; and end B1 is DB44
connector, reservation. End B2 is DB9 connector, connect to RS232 interface of the
power monitor mudel. End B3 is the DB25 for dry contact, another end is the
unfinished cable, connect to the dry contact equipment directly. End B4 is the
grounding terminal. End B5 is RJ45 connector, connect to the COM interface of the
FCE board, the dry contact signal connect to BBU with COM interface.
[End A]: This is the SCS150 pin connector that can be directly connected to the port on
the SA board.
[End B1]: This is the DB44 connector, reservation.
[End B2]: This is the DB9 connector.
[End B4]: This is the grounding terminal.
[End B5]:This is the RJ45 connector.
[End B3]: This is the 25-pin DB connector, which is connected to the dry contact cable.
Another side can connect to the dry contact equipment. The dry contact cable is shown in
the figure cable:
Figure 2-42 Dry Contact Cable
End A connects to B3. End B is a twisted pair with coded numbers, which is connected to
the external monitoring device. It maps with six-way input dry contact and two-way
input/output dry contact.
Figure 2-43 Specifications of the Dry Contact Cable
RRU dry contact:
Till V3.30.20.00, apart from R68/68i, 72S/72E/64/84/R08i/R18/R18A/R28/68E/78

supports dry contacts. Note: As R68/68i is restricted by hardware, dry contacts cannot be
supported through mere version upgrade but through hardware replacement. The dry
contact monitoring cable is directly connected to the RRU with its appearance shown in
the figure below:
Figure 2-44 Dry Contact Cable of the RRU
End A is a DB15 connector; End B involves six cables of different colors, in which, two
cables are relevant with the dry contact with their mapping relations shown below:
Table 2-4 Signal Table of the Dry Contact Cable
No. of the DB15 Signal Name Cable Color

3 Dry contact No. 1 Brown
8 Signal GND Yellow
Dry contact connection mode:
When connecting the dry contact, End A connects to the R8972E/R8984. The connection
of End B is described below:
Connect the eighth pin corresponding yellow cable to the signal GND on the device.
Connect the third pin corresponding brown cable to the dry contact signal cable on the
device.
2.6 Configuration of BTS Auxiliary Peripheral

Devices
2.6.1 Antenna Service Function
After the BBU and RRU are configured, you need to add the auxiliary devices. In the
version of V3.30.20.00, the physical antenna entity, RF cables, and IR antenna group
object will be created automatic by OMC; only the fiber need to created manually.
Chapter 2.6.1.1 only describe the configuration which needed in the configuring. The
configuration order is as follows: antenna attribute, physical antenna entity, RF cables,
and IR antenna group. The configuration process is described below.
2.6.1.1 Antenna Attribute Object
The antenna type does not need to be configured as it is already available in the
database. You only need to select the correct antenna type according to your actual
needs.
Figure 2-45 Antenna Attribute Object
Double-click a record, and you can view the detailed information of the antenna type, as
shown below:
Figure 2-46 Antenna Attribute Object
2.6.1.2 Antenna Entity Object
Select Modify area > Device >BTS Auxiliary Peripheral Devices > Antenna Service >
Antenna Entity Object. Double-click the antenna entity object to enter the Antenna Entity
Object-list tab page. Click to add the antenna entity object.
[Object ID of antenna entity/Antenna entity number] These parameters are automatically

generated. You may also adjust the values by yourself. The Object ID of
antenna entity is recommended to be equal to the Antenna entity number
and that both values should be smaller than 10000.
[Used antenna attribute] You may select the antenna attribute from the drop-down list.
The antenna attribute object is referenced by the antenna type.
 The eight-channel dual-polarized smart antenna is selected according to

antenna gains and distances. (For example, when the gain=15 dBi and the
distance between antennas=75 mm, AntProfile=15.)
 The two-channel dual-polarized smart antenna is selected according to

antenna gains and distances. (For example, when the gain=15 dBi and the
distance between antennas=75 mm, AntProfile=254.)
 Distributed antenna (single antenna): In most cases, AntProfile=201.
 Distributed antenna (dual antenna): In most cases, AntProfile=202 for dual

streams.
Figure 2-47 Antenna Entity Object
2.6.1.3 Configuring RF Cables
To configure a RF cable, you need to configure the mapping relation between the
antenna TX/RX port and the antenna port. The R8928/R8968 series/R8978 series should
be configured with eight records.
Select Modify Area > Device > BTS Auxiliary Peripheral Devices > Cable > RF Cable,
and then double-click the RF cable to enter the RF Cable-List interface. Click to
add the RF cable.
Figure 2-48 RF Cable
Four channel RF cables need to be configured for the R8964.
Figure 2-49 R8964 RF Cable
2.6.1.4 Ir Antenna Group Object
The Ir antenna group object should be configured upon the addition of RF cables.
The Ir antenna group object is used to associate the RRU with the physical antenna entity.
The used antenna and RRU can be selected through the drop-down list.
Select Modify area > Device >BTS Auxiliary Peripheral Devices > Antenna Service > Ir
Antenna Group Object. Double-click the Ir antenna group object to enter the Ir Antenna
Group Object tab page. Click to add the Ir antenna group object.
Figure 2-50 Ir Antenna Group Object
 Note:
For the VxWork version of RRU, its Ir antenna group number cannot exceed the
number of RRU channels. The Ir antenna group number is recommended to be set to
1.
2.6.2 Configuring Optical Cables
The optical cable configurations are used for associating the baseband board and the
RRU, or for RRU cascading.
2.6.2.1 Configuring the Fiber Cable Used to Associate the Baseband Board and
RRU
Select Modify Area > Device > BTS Auxiliary Peripheral Devices > Cable > Fiber Cable,
and then double-click Fiber cable to enter the Fiber Cable-List interface. Click to
add a fiber cable.
[Upper level optical port in topology structure]: Baseband board/switch board

corresponding optical ports
[Lower level optical port in topology structure]: RRU corresponding optical ports
Figure 2-53 Configuring the Fiber Cable
Figure 2-54 Fiber Cable-List
2.6.2.2 Configuring RRU Cascading
Requirements on RRU cascading:
 The optical port rate and optical port protocol of the cascaded optical ports
should be consistent.
 At most four-level cascading is allowed.
For a regular RRU cascading condition:
Configuring a fiber cable intends to configure the topology relation between the optical
port board and the RRU. The upper level optical port and the lower level optical port
should exist. The upper level optical port can be on the baseband board or on the RRU.
Whether the RRU supports cascading needs to be checked. The following take the
topology configuration of the three-level cascading optical cable for the R8962 as an
example:
Figure 2-56 Configuring the Cascaded Fiber Cable for the R8962
Note: You need to power off and reset the RRU when the length of the optical cable or
the number of cascaded layers changes.
2.7 Transport Network Configuration
2.7.1 Configuring the Physical Layer Port
Keep the default settings of Transmission medium and Connection object.
[Ethernet configuration parameter]: Transmitting bandwidth is recommended to be

changed to 1000 M; the value of Working mode should be consistent with
that at the PTN side.
[Used Ethernet]: Select the GE port N0.0 on the CC board;
Figure 2-57 Configuring the Physical Layer Port
When the controlling board is CCE1, values of “Used Ethernet” and “Ethernet
configuration parameter” must be consistent.
For example, if “used Ethernet port” is set to the electrical port, “Ethernet configuration
parameter” needs to be electrical port relevant.
If “used Ethernet port” is set to an optical port, “Ethernet configuration parameter” needs
to be optical port relevant.
Figure 2-58 Used Ethernet
Figure 2-59 Ethernet parameter configuration
2.7.2 Configuring the Ethernet Link Layer
Ethernet link layer:
[Used physical layer port]: for this parameter, select the created physical port.
[VLAN ID]: For those with VLANs, enter the corresponding VLAN number. Multiple IDs
can be entered. If no VLAN is available, keep it null.
Figure 2-60 Configuring the Ethernet Link Layer
2.7.3 Configuring the IP Layer
Select Modify Area > Transmission Network > IP Transport > IP Layer Configuration, and
then double-click it to enter the IP Layer Configuration-List tab page. Click to add
an IP address.
If multiple Ethernet links are configured in such environment, note that they need to
correspond with the specific Ethernet link number. Otherwise, the IP addresses will fail to
be obtained. For the IP address, the gateway, mask, and “VLAN ID”, refer to the planned
network-oriented configuration data.
Table 2-5 An Example of IP Address Planning
Radio
User VL
IP Address Mask Gateway IP Standar Remarks
ID AN
d
172.18.22.1 OMCB
OMCB 255.255.0.0 172.18.22.121 PLAT 60
00 channel
PLAT,
Traffic
TDL ,10.1.13.31 255.255.0.0 10.1.0.200 LTE-TD 61
channel
D
Figure 2-61 Configuring the IP Address
Figure 2-62 Configuring the IP Address
 Note:
In IP parameters, the IP link No. will be referenced in later configurations. To make

data consistent and for easy checking, you are recommended that the IP layer
configuration object ID and the IP parameter link No. start coding from 1 and that the
IP layer configuration object ID=IP parameter link No.
2.7.4 Configuring a Static Route(optional)
Whether to add a static route to the MME/SGW depends on transmission planning. The
configuration interface is shown in the figure below:
Figure 2-63 Configuring a Static Route
 Note:
In most cases, two to four static routes need to be added. (1) eNodeBMME; (2)
eNodeBSGW; (3) eNodeBOMM server. The addition depends on the
transmission planning on site.
2.7.5 Configuring the Bandwidth Resource Group
This needs to be referenced when the service and DSCP mapping are configured. The
configuration involves two phases:
1. Configure Bandwidth Resource Group.
Figure 2-64 Configuring Bandwidth Resource Group
2. Configure one Bandwidth Resource. Keep all default settings.
Figure 2-65 Configuring the Bandwidth Resource
2.7.6 Configuring the SCTP Link
1. The network is configured with multiple IP addresses, which involve the OM IP and
the LTE service IP. The IP referenced by the SCTP is the service IP of the LTE.
Table 2-6 An Example of the Association Parameter
Board
Local Port
Local IP Remote IP Radio for
User ID No./Remote
Address Address Standard Signal
Port No.
Access
IP parameter
correspondin PLAT,
LTE 36412/36412 10.11.51.3 CCE1
g LTE service LTE-TDD
IP address
Figure 2-66 Configuring the SCTP Link
[Local port number]: As defined by the LTE protocol, the port No. of S1 is 36412 and the
port No. of X2 is 36422.
[Used IP Layer Configuration]: select the LTE service IP.
[Used bandwidth resource]: select the bandwidth resource for the LTE link.
[Radio standard]: select the corresponding radio standard.
2. Configure X2
Currently, SON and X2 auto-establishment functions are already enabled over X2, that is,
both S1AP and X2AP are automatically established on the OMC when you build the
SCTP link. If manual configurations are required, refer to the following:
[Local port number]: 36422;
[Used IP Layer Configuration]: select the LTE service IP;
[Used bandwidth resource]: select the referenced bandwidth resource;
[Remote port number]: 36422;
[Remote address]: enter the LTE service IP of the destination eNodeB.
Figure 2-67 Configuring the SCTP Link over X2
After SCTP link over X2 is created, the X2AP will be automatically created on the OMC:
2.7.7 Configuring Multi-Homing for the SCTP Link
For one set of MME, only one association link needs to be configured before its
dual-homing or multi-homing configuration; for the MME POOL, different association links
need to be configured for different MMEs before their dual-homing or multi-homing
configurations. Parameter configuration principles:
When one IP1 (LTE service IP) is used at the eNodeB side, two IP addresses (IP2, IP3)
are used at the CN side; when the SCTP link is configured at the eNodeB side, select the
IP twice (IP1, IP1) at the local end and select the IP (IP2, IP3) twice at the remote end.
Figure 2-68 Configuring Dual-Homing for the SCTP Link
2.7.8 Configuring Service and DSCP Mapping
To configure Service and DSCP Mapping, pay attention to the following:
[Used IP layer configuration]: select the LTE service IP;
[Used bandwidth resource]: select the referenced bandwidth resource;
[Operator]: enter the operator.
Figure 2-69 Configuring Service and DSCP Mapping
[LTE TDD service and DSCP mapping]: click to add the mapping. As shown in the
figure below, select all items by default before clicking OK.
Figure 2-70 Configuring LTE TDD service and DSCP mapping
2.7.9 Configuring the OMCB
The OMCB data is used to establish the channel between the eNodeB and the OMM.
Figure 2-71 OMC Channel
[interface type of operation and maintenance]: Independent networking
As for the IP address and network gateway, enter the information according to network
planning.
[Used IP layer configuration]: select the IP address that carries the OMCB channel.
[Used bandwidth resource]: null.
2.8 Radio Parameter Configuration
2.8.1 LTE TDD
2.8.1.1 Creating a LTE TDD Network
Double-click the LTE TDD node to create global parameters for the LTE network. Pay
attention to the following main parameters:
[LTE TDD ID] The internal OMMB SN for the LTE network that whose value range cannot
exceed 1048575;
[eNodeB ID] This parameter is automatically generated according to the LTE TDD ID;
[PLMN] Enter the operator’s PLMN created in section 2.3;
[Holdover Time-Out Switch] Enable [1].
Figure 2-72 Creating a LTE TDD Network
2.8.1.2 Creating the Baseband Resource
Select Modify Area > Radio Network >TD-LTE> Resource Interface Configuration >
Baseband Resource, and then double-click it to enter the Baseband Resource-List tab
page. Click to add a baseband resource.
Main parameters:
[Baseband Resource Configuration ID]: Baseband resource ID, the ID should be unique
under the eNodeB.
[CP ID]: To identify the different CP in one cell, value range should be 0~254. The CP ID
can not conflicted in one super cell.
[RF Unit Application Mode]: choose the radio mode according the actual application
scenarios.
 Normal Mode[0]: normal mode means the single radio unit scenario, including
single channel, dual channel and multiple channel; one RRU means one radio
unit.
 Combination Mode[1]: apply to the high speed rail scenario; single channel
supper cell with 6cp scenario.
 Mergence Mode[2]: apply to single baseband resource which refer to multi

radio units, the baseband signal transmit and receive in all radio units at the
same time. Apply to radio combined scenario, such as dual channel supper cell
with more than 6 CP.
 Mergence mode(PB Networking)[3]: apply to Qcell scenario.
[Ir Antenna Group Object]: choose IR antenna group.
[Connected Baseband Device]: choose the baseband resource that previous created.
[Mapping of Antenna Port and Antenna Channel]: choose the default.
 For eight-channel RRU, default value is 00001111, which indicates that the
previous channels map with port No.0 and the latter four channels map with
port No.1.
 For a dual-path RRU, if the dual-path single antenna is applied, set it to

0,15,15,15,15,15,15,15; if a dual-antenna is used, set it to
0,1,15,15,15,15,15,15."0" means port 0,"1" means port 1, “15” means that
such channel is not used or unavailable.
 For the current version, this part of content needs no configuration as it will be
automatically generated according to the selected transmitter on the OMC.
Keep the automatically generated value.
Maximum Transmission Power of BP Resource(dBm), Real Transmit Power of BP

Resource(dBm), Referenced Signal Power of BP Resource(dBm), these three
parameters will affect the perl throughput, should be set according to the specific RRU.
Maximum transmission power decided by RRU type, and real transmit power
automatically calculate by OMC, just need to configure the referenced signal power
following the planning data.
Figure 2-73 Creating the Baseband Resource
 Note:
When associating baseband devices, the BPN2 involves two baseband resources:
BpDevice1 and BpDevice2. As selection of chips is executed by the control panel at
the eNodeB side. It can be set to BpDevice1 globally.
2.8.1.3 Creating the S1AP Interface
The OMC is automatically created, please double check confirm S1AP data in the OMC.
2.8.1.4 Configuring Board Application Attribute
Select Modify Area > Radio Network >TD-LTE> Baseband Resource > Board Application
Attribute, and then choose one and click to modify.
One Board Application Attribute will be created automatically by OMC when the
baseband board created. And the parameter “Cell mode” is relative with the cell
parameters.
Figure 2-74 Board Application Attribute
Main parameters:
[Cell mode]: choose Mode0[0] or Mode1[1].
The configuration principle as below:
1. BPL1
Normal scenario:
 Indoor 2 channel site: configure Mode1[1].
 Macro 8 channel site: configure Mode0[0].
 International 4 channel site: configure Mode1[1].
High traffic guarantee scenario:
 If the baseband of actual cell number <=3, configure Mode0[0].
 If the baseband of actual cell number > 3, configure Mode1[1].
2. BPN2
Normal scenario:
 Indoor 2 channel site: configure Mode1[1].
 Macro 8 channel site: configure Mode0[0].
 International 4 channel site: configure Mode0[0].
High traffic guarantee scenario:
 If the baseband of actual cell number <=6, configure Mode0[0].
 If the baseband of actual cell number > 6, configure Mode1[1].
3. Pico site configuration
BS8912
 If BS8912 use 2T2R, configure Mode0[0].
 If BS8912 not use 2T2R, configure Mode1[1].
 So far, most the B8912 use 2T2R, so the default value is Mode0[0].
BS8922
 If BS8922 use 8T8R\4T8R\2T8R\1T8R\4T4R\4T2R\4T1R, configure Mode0[0];

others configure Mode1[1].
 So far, most the B8922 use 2T2R, so the default value is Mode1[1].
BS8901B
 If BS8901B use 8T8R\4T8R\2T8R\1T8R\4T4R\4T2R\4T1R, configure

Mode0[0]; others configure Mode1[1].
 Default value is Mode1[1].
[Connected Board]: identify the LTE baseband board type and slot.
2.8.1.5 Creating an E-UTRAN TDD Cell
Select Modify Area > Radio Network >TD-LTE> E-UTRAN TDD Cell, and then
double-click it to enter the E-UTRAN TDD-List tab page. Click to add a cell.
Main parameters:
[E-UTRAN TDD Cell ID] This is the internal cell number of the eNodeB. “1,2, or 3” is
recommended. The value cannot exceed 10000.
[PCI] This parameter is shortened from the physical cell identifier. It needs to be entered
according to network planning. The PCI cannot be modified after determined.
[TAC] This is the tracking area code. It is configured as planned;
[Baseband Resources Configuration] This indicates the RRUs used in this cell and the
RRU corresponding baseband resources;
[Number of Tx Antenna Port in Cell]: This parameter depends on the RRU type and
antenna type;
[Band Indication for Frequency] The band indication for frequency and the ARFCN where
the UL/DL carrier frequency is located will be configured according to the actual
frequency resource usage. The mapping relation between the frequency band indication
and frequency range is as follows: 32:2545-2575, 33:1900-1920, 34:2010-2025,
35:1850-1910, 36:1930-1990, 37:1910-1930, 38:2570-2620, 39:1880-1920,
40:2300-2400, 41:2496-2690.
Band A: 2,010 MHz -2,025 MHz
Band D: 2,496 MHz -2,690 MHz
Band E: 2,320 MHz -2,370 MHz
Band F: 1,880 MHz -1,920 MHz
Note:
Band E should range from 2300 MHz to 2400 MHz. As the current RRU device supports,
however, only the range from 2320 MHz to 2370 MHz, the default ARFCN of band E on
the OMC is 2320. Thus, you need to manually change the setting. For a cell whose
bandwidth is 20 M, you need to change its ARFCN to at least 2330. Otherwise, the cell
could not be established.
As the China Mobile demands, band F is adjusted to 30 M starting from phase three of
the LTE project. The band F RRU device tailed with A supports only the 30 M of the
range from 1885 to 1915. The central frequency band configuration strategy for the new
LTE devices later on depends on the operator’s requests. The market strategy is
described below:
The ARFCN of 1890 M at the 20M bandwidth is not allowed. The previous 5 M of band F
cannot be used and cannot be supported by the device, either.
When no interference or no severe interference exists between 1900 and 1905, the
ARFCN of 1895 M at the 20 M bandwidth should be set;
When interference exists between 1900 and 1905, the ARFCN of 1892.5 M at the 15 M
bandwidth should be set. (The setting is supported by both the current version and the
terminal.);
After the PHS spectrum clearance was performed, the ARFCN of 1895 M at the 20 M
bandwidth was globally applied.
The range of band D 41 includes 38. This is configured according to on-site planning.
[Uplink-Downlink Subframe Configuration/Special Subframe Configuration]: Currently,

the usual configurations are 2/7; 2/5. This parameter depends on the actual site planning;
“2:7” is in most cases applied to independent LTE networking. Thus, no TDS band such
as band D, is involved;
“2:5” is in most cases applied to the hybrid networking of LTE and TDS such as in the
band F scenario. If a variety of manufacturers of a city is available, “2:6” can also be
configured.
[System Band Width]: The LTE TDD supported bandwidth depends on the actual
applications such as 20 M or 10 M.
[Maximum RBs Allocated for Uplink/Downlink UE]: The parameters are relevant with the
previous system bandwidth. If the system bandwidth is 20 M, keep them to 100; if the
system bandwidth is 15 M, both parameters should be changed to 75. For the bandwidth
of 10 M, change them to 50; for that of 5 M, change them to 25; for that of 3 M, change
them to 15; for that of 1.4 M, change them to 6. Currently, these parameters are
automatically changed when the bandwidths are modified on the OMC in accordance
with the rules mentioned previously.
[CFI Selection] If a LTE TDD network is already available in the living network, keep it the
same as that of the previous eNodeB; if no LTE TDD network is available, set it globally
to Auto-Adjusted.
[Sample Rate Mode Configuration]: value range is: 0, 1, 2; default value is 0.
 Parameter 0: normal sampling rate mode, compression or un-compression of

the baseband board are available.
 Parameter 1: the reducing sampling rate mode is enabled, and the IQ

compression mode of baseband should be used together.
 Parameter 2: further reducing sampling rate mode is enabled, and the IQ

compression mode of baseband should be used together, and this scenario
only for Qcell.
Default value is 0, reducing sampling rate mode is closed; value 1 is enable reducing
sampling rate mode. Value 2 only for Qcell scenario. the IQ compression mode of
baseband should be enabled when reducing sampling rate mode enabled.
After this cell is configured, you need to take this cell as parent node and configure the
E-UTRAN cell reselection, measurement parameters as part of these parameters will be
used when the cell is established.
Figure 2-75 LTE Cell Parameter-1
2.8.1.6 Configuring the Neighboring Cell
Take two inter-frequency cells as an example to describe how to configure the

neighboring cell. The cell frequency of cell No. 1 of site No.201 and the cell frequency of
cell No.2 of site No. 373865 are neighboring cells at 2585 MHz.
1. Select Configuration Management > Special Function of Standard > Neighbor Cell
Management to enter the same interface, as shown in the figure below:
Figure 2-79 Entering “Neighbor Cell Management”
2. Select the two cells to be configured as neighboring cells. Select them by

highlighting them. To ensure that the two adjacent NEs are configured as
neighboring cells, select Configure Neighbor Relation to Target Cell.
Figure 2-80 Selecting the Cells to be Configured as Neighboring Cells
Select the neighboring relation to be added, and then click , as shown in the figure
above.
Figure 2-81 Adding a Neighboring Cell Relation
3. Check whether the automatically configured neighboring cell relations are correct.
Check E-UTRAN TDD Neighbor Cell first, as shown in Figure 2-82 and Figure 2-83.
Check the configured neighboring cell relevant information concerning its relevant
eNodeB ID, cell identifier, band indication, center carrier frequency, and PCI.
Figure 2-82 Neighboring Cell Information of Site No. 201
Figure 2-83 Neighboring Cell Information of Site No. 373865
4. Then, check the E-UTRAN neighboring cell, as shown in Figure 2-84. Check
whether Switch for HO is set to No. If Switch for HO is set to Yes, you can infer
that the handover is not supported.
Figure 2-84 E-UTRAN Neighbor Relation
3 Advanced Function Configuration
3.1 Cell Aggregation and Super Cell
Cell merging: indicates the process to combine multiple CPs into one super cell.
Super cell: indicates a TDL cell that involves more than 1 CP.
3.1.1 Configuring LTE Super Cell
In V3.30.20.00, one super cell corresponds to only one logical cell, which is composed of
multiple physical cells.
Configure the cells as normal cells before combining them into a super cell.
A super cell can be composed of multiple Normal Cells. To implement this, you need to
first select Configuration Management > Special Function of Standard > Super Cell
Management.
Figure 3-1 Opening the Super Cell Management Interface
1. Then, select the normal cells to be merged. Combine three normal cells into one
super cell and specify the main CP, as shown in Figure 3-2.
Figure 3-2 Combining Normal Cells into a Super Cell
2. Click OK to finish forming a super cell. The previous three normal cells (170, 171,
and 172) are then combined into one super cell called 170. Cells 171 and 172 can
serve as normal cells for backup. The super cell can be splitted to three normal cells
anytime.
 Note:
When configure the super cell through 1 normal cell + some unused baseband
resources from the super cell management tool, need to unblock the CPs from the
dynamic management. Because if the baseband resources blocked before configure
the super cell, they also blocked after configure the super cell.
3.1.2 Modifying Radio Parameters of the LTE Super Cell
In V3.30.20.00, when multiple normal cells are combined into a super cell, the radio
parameter modifications are performed on the main CP. If the super cell is splitted into
normal cells, the previous main CP corresponding normal cell inherits all radio parameter
data of the previous super cell. The secondary CP corresponding normal cells will
resume their data before the grouping.
3.1.3 Configuring a LTE Super Cell Crossing Boards
To configure a LTE super cell crossing boards, you need to configure the FS5C or CR0
board in slot No. 3 or No.4.Set the “Board function mode” to LTE-TDD
CloudRadio[100663297].
Figure 3-3 Configuring a CR0 Board
“Configuring a super cell crossing boards” cannot be performed on the BPN2 board.
3.2 Configuring Two Carriers
“Two carriers” indicates that two TDL cells of different ARFCNs are established in a same
RRU. Pay attention to the following points:
1. Configure two baseband resources referencing the same RRU antenna group;
2. Two TDL cells are established referencing the previously established baseband
resources. Pay attention to the following points:
 Bands of the two cells cannot be duplicated. For example, if the frequency of
the first cell is 2330, that of the second cell should be configured as 2350.
 The UL/DL subframe configurations, special subframe configuration ratio,

number of antenna ports, and the cell bandwidth of the two cells should be
consistent;
The following section takes the BPL1+8964 S2300 as an example.
3.2.1 Configuring Two Carriers for the BPL1+8964 S2300
3.2.1.1 Creating the Baseband Resource
For the dual-carrier scenario, creating two baseband resources needs to reference a
same IR antenna group.
Figure 3-4 Configuring the First Baseband Resource
Figure 3-5 Creating the Second Baseband Resource
Figure 3-6 Creating the Baseband Resource-List
3.2.1.2 Configuring an E-UTRAN TDD Cell
In the previous baseband resource creation procedures, two baseband resources have
been created and they are:
ECellEquipmentFunctionTDD=1,
ECellEquipmentFunctionTDD=1,
Create one LTE TDD cell that corresponds to each baseband resource. Two ARFCNs of
the LTE TDD cells should be separated. Their bandwidths cannot be duplicated; all the
other parameters should be consistent.
The TDD Cell List is shown in the figure below: (The parameters in the list should be
entered as planned. The values below serve as just examples)
Figure 3-7 Creating a LTE TDD Cell
3.3 Configuring a CA
3.3.1 Configuring Neighbor Cell Relations
Select Configuration Management >Special Function of Standard > Neighbor Cell

Management to enter the Neighbor Cell Management interface.
Figure 3-8 Entering Neighbor Cell Management
Select the cells for CA according to configuration planning requirements. Click the “Add”
button in the Configure Neighbor Relation tab page to configure the cells as
neighboring cells;
Figure 3-9 Configure Neighbor Relation Tab Page
1. Select Modify Area > Radio Parameter > LTE TDD > Neighbor Relation
Configuration > E-UTRAN Neighbor Relation, and then double-click E-UTRAN
Neighbor Relation-List tab page. Set Intra-LTE Neighbor Relation to Same
Coverage, as shown in the figure below:
Figure 3-10 Modifying Parameters of Neighboring Cells
3.3.2 Configuring CA Coordination Relations
1. Select Configuration Management >Special Function of Standard > Cell

Coordination Management, as shown in the figure below:
Figure 3-11 Entering Cell Coordination Management
2. Select the NE and then to check the desired cell in the displayed Cell
Coordination Management interface. Then, click to perform a CA.
Figure 3-12 Cell Coordination Management Cell
3. Set Cooperative Relationship Type of two cells to DL CA, as shown in the figure
below.
Figure 3-13 Setting Cooperative Relationship Type of Two Cells to DL CA
4. After a DL CA is formed, you could view that the cells share the same DL CA ID in
the Cell Coordination Management interface, as shown in the figure below.
Figure 3-14 Viewing the Result of a Formed DL CA
After the previous steps are executed, incrementally synchronize the data to the eNodeB
side. Till then, the CA configurations are finished.
4 Typical Cases
 Note:
This chapter describes the typical-scenario based configurations.
4.1 B8200+BPL1+R8962/R8972EB8200+BPL1+R8962
/R8972E
The configuration process is as follows:
Figure 4-1 Configuring the BPL1 Board
Figure 4-3 Configuring the R8962
Figure 4-4 Configuring the Optical Port Device Set of the RRU
Figure 4-6 Configuring the Antenna Entity Object
 Single stream: “AntProfile=201” indicates the distribution mode of antenna 1,
 Dual stream: “AntProfile=202” indicates the distribution mode of antenna 2.
Figure 4-7 Configuring the RF Cable
Figure 4-8 Configuring the Ir Antenna Group Object
4.2 B8200+BPL1+R8964/ R8984
Figure 4-11 Configuring the R8964 S2300
Figure 4-15 Configuring RF Cables
4.3 B8200+BPL1+R8978
Figure 4-17 Configuring the BPL1
Figure 4-18 Configuring the Optical Port Device on the BPL1
4.4 B8200+BPN2+R8502 S2600/ S2300/S2600U
Overview
ZXSDR R8502, as a pico RRU, is connected to the BBU through optical cables. The
R8502 and the BBU form an integrated base station. And the R8502 also provides for the
BBU with ports to be cascaded with the other RRUs. It is equipped with a built-in antenna:
In some special scenarios, when a living antenna system needs to be used, you may also
apply an external antenna. Note that the material codes for the built-in antenna or
external antenna differ. The R8502 S2600 frequency ranges from 2575 MHz to 2635
MHz. The R8502 S2300 frequency ranges from 2320 MHz to 2370 MHz. The R8502
S2600U frequency ranges from 2325 MHz to 2575 MHz.
Figure 4-26 Configuring Optical Ports on the BPN2
 When the RRUs are connected to it upper level node: select single up-link
optical line.
Figure 4-29 Configuring Optical Cables
 “AntProfile=202” indicates the distribution mode of antenna 2.
 Configure one RF port for each physical channel on the RRU.
 Associate the antenna with the RRU.
4.5 B8300+BPL1+A8712 M192026
1. Overview
The A8712 M192026 is an integrated RRU with a built-in antenna. It has four RF
channels, in which, channel 1 and channel 2 are of band FA (mixed-mode) and channel 3
and channel 4 are of band D (TDL single-mode). Two antenna groups can be configured
on one RRU during data configurations in the field to support band FA and band D
respectively.
2. Networking specifications
“Multiple load-sharing optical line” is not supported.
The supported bands are listed below:
Note: This RRU is 30 M by band F. You need to modify the setting when configuring the
ARFCN of band F.
Band F: 1,885 MHz -1,915 MHz
Band A: 2,010 MHz -2,025 MHz
Band D: 2,575 MHz -2,635 MHz
3. Configuration of an antenna and an antenna group
Configuring antenna physical entity: For band FA, its configurations are similar to those
for the R8972 M1920 or the R8972E M1920. The physical entity type of the antenna can
be set to 20 (smart dual-polarized antenna); for band D, as only LTE single mode is
supported, the antenna entity of the antenna can be configured as 20 or 202 (for
distributed dual-antenna scenario), as shown in the figure below:
Figure 4-33 Antenna Entity Object
RF cable connection: Connect port No.1 and port No.2 of band FA of the RRU to the
antenna entity 1; connect port No.3 and port No.4 of band D to the antenna entity 2, as
shown in the figure below:
Figure 4-34 RF Cable
IR antenna group: Then, create two Ir antenna groups on one same RRU, as shown in
the figure below:
4. Configuration of TDL cells
No special demands are required. The policy is that you need to select different
baseband resources according to various bands. Note that band F range of this RRU is
between 1885 and 1915 with a bandwidth of 30 M; band D ranges from 2575 to 2635 with
a bandwidth of 60 M. When performing configurations in the field, remember that the
band should fall into the specified range.
5 Version Limit and Legacies
5.1 Version Limit
1. When the variety of RRU types is available, synchronous downloading of both the
BBU and RRU version packages might trigger disk insufficiency, causing
downloading failures.
Workaround: Clear the disk files in dynamic management in advance.
Separately download and activate the BBU and RRU version packages.
2. Do not modify the configuration data before the activation takes effect upon
pre-activating.
3. If configure the carrier groups on the RRU, but the carrier groups do not have
frequency, other carrier groups’ frequency can’t set up when the RRU set up.
4. After adding or replacing a PM board, the base station need restarting to distribute
the power supply relations again.
5. Modifying the “Antenna Physical Entity Object” will cause the RRU to reset.
6. When the RRU is configured in the case of a multi-carrier loaded LTE network,
blocking one cell will cause service disruption of the other cells for a short period.
7. If the TX power of the RRU is excessively small (smaller than the power of the RRU
by more than 15 db), the RRU will not report alarms even if the SWR exceeds the
alarm threshold as the SWR measurement is incorrect.
5.2 Legacies
1. A prompt indicating firmware version activation failure is displayed.
If the firmware needs upgrading, do as follows:
(1) Create a task: Download + activate firmware specifications package + software

specifications package.
(2) Create a task that has taken effect.
Note: The data at the OMC side will automatically take effect only when the firmware
activation succeeds. If the firmware activation fails, you need to manually check whether
the boards in question can be ignored. If they can, initiate the validation process again.
Otherwise, activate the firmware again.
2. The R8918 supports only a single-fiber cable rather than a dual-fiber cable for
connection.
3. After the slot for the BPL is changed, do not modify the cell ID. Otherwise, the UE
will fail to access the network.
4. In multi carriers scenarios, blocking one TDL cell will affect the other TDL cells of the
RRU.
5. The port OPT2 of R8972 only for the cascade, which as the upper port is forbidden.

LTE TDD (V3.30.20.00) ENodeB Initial Configuration Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE TDD (V3.30.20.00) ENodeB Initial Configuration Guide

Uploaded by

Copyright:

Available Formats

Operator Logo

LTE TDD eNodeB Initial

Product Version Document Version Serial Number Reason for Revision

Intended audience: Commissioning engineers at the eNodeB side

LTE TDD (V3.30.20.00) Data Configuration Norm

1 Overview of Site Commissioning .................................................................. 1

2 Data Configurations for Typical Sites ........................................................... 5

3 Advanced Function Configuration .............................................................. 78

3.3.1 Configuring Neighbor Cell Relations ............................................................... 84

5 Version Limit and Legacies ....................................................................... 102

Figure 1-1 Commissioning Workflow .................................................................................... 1

Figure 2-31 1588 Clock Configuration Options ................................................................... 31

Figure 2-66 Configuring the SCTP Link .............................................................................. 57

Figure 4-3 Configuring the R8962 ...................................................................................... 90

Table 1-1 Typical Outdoor Site Configurations ..................................................................... 3

1 Overview of Site Commissioning

1.1 Commissioning Workflow

The workflow of parameter configurations are shown in the figure below:

Figure 1-1 Commissioning Workflow

1.2 Typical Site Topologies

Figure 1-2 Typical Outdoor Site Configurations

Table 1-1 Typical Outdoor Site Configurations

SN Material Name Qty Remarks

The BPL1 board is preferentially configured

1.3 Commissioning Modes

2 Data Configurations for Typical Sites

2.1 Creating a Subnetwork

[User Label]: This parameter is set as planned.

Figure 2-1 Creating a Subnetwork

[NE Maintenance Status]: This parameter includes NE Maintenance Status and

 NE Maintenance Status includes commissioned {Normal},

 Maintenance Status of LTE TDD includes commissioned {Normal},

In which, this NE Maintenance Status has an “AND” relation with the OM

Whether the eNodeB is connected to the OMC depends only on the NE

Alarm debugging: NE alarms in such status will not be reported to the

Performance debugging: NE performance data in such status will not be

 If two CC boards are configured for TD LTE, apply service load

 If two CC boards are configured and that CC boards support

[NE External IP]: enter the OM IP of the eNodeB.

Use the planned OMC OM IP.

[NE ID Planned by Operator]: enter the content as planned.

[NE ID Planned by Vendor]: enter the content as planned.

Figure 2-2 Creating an NE

2.3 Creating an Operator

[Operator name]: indicates the name of the operator.

Figure 2-3 Operator

Figure 2-4 PLMN

2.4 System Parameter Configuration

2.4.1 Power Saving Parameter

Keep the other parameters unchanged.

Figure 2-5 Power Saving Parameter

Figure 2-6 Enabling the Power Saving Switch

2.4.2 Time Configuration

Figure 2-7 Time Configuration

2.4.3 SON Function Switch Object

SON Function Switch Object: is applied to PNP commissioning in most cases.

The SON function involves four switches:

[Configuration for auto-commissioning switch]: This switch is exclusive to GU products

[Configuration for auto-setup transmission switch]: This parameter should be modified as

Figure 2-8 SON Function Switch Object

Figure 2-9 Configuration for auto-setup transmission switch

2.4.4 Frequency Adjust Configuration

Use the default values.

Figure 2-10 Frequency Adjust Configuration