HCIA-LTE Lab Guide V1.0

Recommendations
 Huawei Learning Website

 http://learning.huawei.com/en
 Huawei e-Learning
 http://support.huawei.com/learning/NavigationAction!createNavi?navId=MW
n
000001_term1000025144&lang=en it o
i c a
 Huawei Certification if
r t
Ce
http://support.huawei.com/learning/NavigationAction!createNavi?navId=_31
&

&lang=en g
n in
 Find Training
rai
i T

e
http://support.huawei.com/learning/NavigationAction!createNavi?navId=_trai
a w
ningsearch&lang=en
Hu
More Information n
it o
ic a
t i f
 Huawei learning APP e r
C
&
i ng
a in
T r
ei
a w
Hu
版权所有© 2018 华为技术有限公司

eNodeB LTE V100R013C10 Initial
n
it o
Configuration by MML Practice Guideica
t if
r
(Cover) Ce
&
ing
ISSUE 1.00 i n
T ra
e i
aw
Hu
n
atio
ic
rtif
C e
&
ng
ni
r ai
T
ei
a w
H u
Contents
1 eNodeB Data Configuration Preparation ..............................................................................1-4

1.1 Network Topology......................................................................................................................................... 1-4
1.2 Data Configuration Flow ............................................................................................................................... 1-5
1.3 Negotiated Data Preparation ......................................................................................................................... 1-5
1.4 LMT Tool ...................................................................................................................................................... 1-6
n
2 eNodeB Common Device Data Configuration .....................................................................2-7 it o
i c a
i f 2-8
2.1 eNodeB Basic Data Configuration ................................................................................................................ 2-7
t
r 2-9
2.1.1 Task: Configuring eNodeB Basic Data ................................................................................................
C e
2.2 eNodeB Hardware Data Configuration .........................................................................................................
&
2.2.1 Task: Configuring Cabinets and Subracks of the eNodeB ................................................................... 2-9
ng
2.2.2 Task: Configuring Boards for the BBU.............................................................................................. 2-10
i
in
2.2.3 Task: Configuring RF Unit Data ........................................................................................................ 2-12
r a
2.3 eNodeB Time and Clock Data Configuration ............................................................................................. 2-14
T
ei
2.3.1 Task: Configuring Time Data ............................................................................................................. 2-14
2.3.2 Task: Configuring Clock Data ........................................................................................................... 2-15
a w
3 eNodeB Transport Data Configuration ............................................................................... 3-16
H u
3.1 Low Layer IP Transport Data Configuration ............................................................................................... 3-17
3.1.2 Task: Configuring a Service and OM IPn

3.1.1 Task: Configuring a Physical Port ...................................................................................................... 3-17
t i o ............................................................................................ 3-18
c a
3.1.3 Task: Configuring an IP Route ........................................................................................................... 3-18
i
t i f
3.1.4 Task: Configuring VLAN................................................................................................................... 3-19
e r
3.2 High Layer Transport Data Configuration .................................................................................................. 3-19
C
3.2.1 Task: (Optional) Configuring S1 Interface Data in Link Mode ......................................................... 3-19
& S1 Interface Data in Endpoint Mode (Simplified Configuration) ........................ 3-23

3.2.2 Task: Configuring S1 Interface Data in Endpoint Mode .................................................................... 3-21
ng OM Channel Data ................................................................................................ 3-25

3.2.3 Task: Configuring
3.2.4 Task:iConfiguring
a in Data Configuration ......................................................................................4-25

Tr Data Configuration........................................................................................................................... 4-25
4 eNodeB Radio
4.1i Sector
e 4.1.1 Task: Configuring a Sector................................................................................................................. 4-26
w
a 4.2 Cell Data Configuration .............................................................................................................................. 4-26
H u 4.2.1 Task: Configuring a Cell .................................................................................................................... 4-27
4.3 *(Optional) Neighboring Cell Data Configuration ...................................................................................... 4-28
4.3.1 Task: Adding an Intra-Frequency Neighboring Cell .......................................................................... 4-28
4.3.2 Task: Adding an Inter-Frequency Neighboring Cell .......................................................................... 4-30
4.4 *(Optional) TDD Cell Configuration .......................................................................................................... 4-31
4.5 *(Optional) Massive MIMO Cell Configuration ......................................................................................... 4-33
5 eNodeB Script Verification ....................................................................................................5-37

5.1 Single-eNodeB Script Execution and Verification ...................................................................................... 5-37
5.1.1 Logging In to the eNodeB Using the U2000 Client in Web Mode .................................................... 5-37
5.1.2 Executing MML Scripts in Batches ................................................................................................... 5-38
5.2 Single-eNodeB Verification Experience...................................................................................................... 5-38
5.2.1 Procedure ........................................................................................................................................... 5-38
6 RAN Sharing Data Configuration ........................................................................................6-40

6.1 RAN Sharing with Common Carriers Data Configuration.......................................................................... 6-41
n
it o
6.1.1 Task: Configuring RAN Sharing with Common Carriers Data .......................................................... 6-41
i c a
r t if
Ce
&
i ng
i n
T ra
e i
aw
Hu
n
a tio
ic
rt if
C e
&
n g
ni
r ai
T
ei
a w
H u
1 eNodeB Data Configuration Preparation
About This Chapter
The following table lists the contents of this chapter.

n
Section Describes
it o
i c a
if
1.1 Network Topology Know the topology of the lab network.
r t
Ce
1.2 Data Configuration Flow Know the procedure of data configuration.
1.3 Negotiated Data Preparation Prepare the negotiated data.
&
ng
1.4 LMT Tool LMT tool instruction.
n i
i
1.1 Network Topology T ra
e i
Description
aw
Know the topology of the lab networking.
Hu
n
tio
Figure 1-1 Topology of the lab networking
ic a
rt if
C e
&
n g
ni
r ai
T
ei
a w
H u
Figure 1-2 Hardware configuration
n
it o
i c a
r tif
1.2 Data Configuration Flow
Ce
&
ing
i n
T ra
e i
aw
Hu
n
atio
ic
rt if
C e
&
n g
i ni
ra Data Preparation
1.3 Negotiated
T
i
e 1-3 Control plane protocol stack
w
Figure
a
Hu
Figure 1-4 User plane protocol stack
n
it o
i c a
if
This practice is based on the dedicated negotiated data. Use the planned data when you config the live network.
r t
Ce
1.4 LMT Tool
&
ng
Figure 1-5 LMT offline MML login window
n i
i
T ra
e i
aw
Hu
n
a tio
ic
rt if
C e
&
n g
ni
r ai
T
ei
a w
H u
Figure 1-6 LMT offline MML configuration window
n
it o
i c a
r tif
Ce
&
ing
i n
ra
2 eNodeB Common Device Data Configuration
T
e i
a w
About This Chapter
Hu
n
tio
ic a
if
Section Describes
e rt
2.1 eNodeB Basic Data Configuration Learn how to configure the basic data.
C
2.2 eNodeB Hardware Data Configuration Learn how to configure the device hardware data.
&Data Configuration
g
2.3 eNodeB Time and Clock Learn how to configure the time and clock data.
n in
ai
2.1 eNodeB r
T Basic Data Configuration
ei
a w
Description
u
H Learn how to configure the basic data
Reference
LMT MML/U2000 Client, LMT Offline MML
2.1.1 Task: Configuring eNodeB Basic Data
Table 2-1 Configuring eNodeB basic data
Step Description Fulfilled
1 Log in the U2000 client or LMT MML, use DSP APP to check the application ID with □Yes
application type set to be eNodeB. □No
n
it o
i c a
r if
t
2 C
(Optional) Add an application for the eNodeB if there is no specified application running e □Yes
on the base station.
& □No
i ng
a in
T r
ei
a w
Open LMT Offline MML, use this command to add u
3
H an eNodeB function. □Yes
□No
n
it o
ic a
t i f
4 Set Network Element Name,
e r Location, Deployment Identifier, Site Name and □Yes
Site
User Label.
C □No
&
i ng
a in
T r
eiAdd an operator.
5
a w □Yes
H u □No
6 Add tracking area configuration for the CN Operator. TAC is negotiated data, determined □Yes
by the EPC. □No
7 Set special status of the NE. □Yes

□No
n
it o
i c a
r tif
Ce
2.2 eNodeB Hardware Data Configuration &
Description ing
i n
Learn how to configure the device hardware data.
T ra
Reference e i
LMT Offline MML awu
2.2.1 Task: Configuring Cabinets and Subracks of the eNodeB
H
o n
i
Table 2-2 Configuring cabinets and subrackst of the eNodeB
ic a
Step Description
t i f Fulfilled
1 Add a cabinet.
e r □Yes
C □No
&
i ng
a in
T r
ei
a w
Hu2 Add a subrack for BBU. □Yes
□No
n
it o
i c a
r tif
Ce □No
3 (Optional for an RFU) Add a subrack for an RFU. □Yes
&
ing
i n
T ra
e i
2.2.2 Task: Configuring Boards for the BBU a
w
Hu
Table 2-3 Configuring boards for the BBU
n
Step Description it o Fulfilled
ic a
1 Add a UMPT board.
t i f □Yes
e r □No
C
&
i ng
a in
T r
ei
a w
Hu2 Add an LBBP board. □Yes
□No
n
it o
i c a
r tif
3 (Optional) Add a UBBP board. Ce □Yes
& □No
ng
ni
rai
T
ei
a w
Hu
n
atio
(Optional) Add an LPMP board.if ic
rt
4 □Yes
C e □No
&
i ng
a in
T ra FAN board.
ei
5 Add □Yes
aw
□No
Hu
6 Add a UPEU board. □Yes
□No
n
it o
2.2.3 Task: Configuring RF Unit Data
i c a
r t if
Ce Fulfilled
Table 2-4 Configuring RF unit data
Step Description
&
ng
1 Add an RRU chain. □Yes
ni
□No
rai
T
ei
a w
Hu
n
atio
ic
rt if
e
Repeat this command to add more RRU chains.
2 Add an RRU (if the RFC
unit is an RRU). □Yes
& □No
i ng
a in
T r
ei
a w
H u
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
Hu
n
a tio
ic
rt if
C e
&
Repeat this command to add more.
ng
3 Add an RFU, if the RF unit is an RFU. □Yes
ni
□No
i
Tra
ei
a w
H u
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
Hu
n
tio Configuration
2.3 eNodeB Time and Clock Data
a
ic
Description
rt if
C e
Learn how to configure the time and clock data.
Reference &
ng
i ni
LMT Offline MML
2.3.1 Task:raConfiguring Time Data

i T
e 2-5 Configuring time data
a wTable
H uStep Description Fulfilled
1 Set the time zone and the daylight saving time (DST) information about the NE. □Yes
□No
n
it o
i c a
2 Set the time source.
r if
□Yes
t
□No
Ce
&
ing
i n
T ra
e i
2.3.2 Task: Configuring Clock Data aw
Hu
n
Table 2-6 Configure clock data
tio
ic a □Yes
if
1 Add a GPS.
t □No
C er
&
n g
ni
r ai
SetTthe working mode of the reference clock source.
ei
2 □Yes
aw
□No
Hu
3 Set the clock synchronization mode of a BS. Fulfilled

n
it o
3 eNodeB Transport Data Configuration i c a
r t if
About This Chapter Ce
&
ing
i n
ra
Section Describes
i T
e
aw
3.1 Low Layer IP Transport Data Learn how to configure the layer 1, layer 2, and layer 3 transport
Hu
Configuration data.
3.2 High Layer Transport Data Learn how to configure transport layer data.
Configuration
n
a tio
f ic
rt i
Figure 3-1 Network transport interfaces
C e
&
Uu S1-C
ng
MME
UE eNB S1-U
i
X2
in
OM
a
S-GW
T r eNB
ei
U2000
aw
Hu
Figure 3-2 S1 Interface & OM channel topology
Client&..&2100
10.20.1.100/24
10.20.1.1
n
10.1.20.100/24
10.1.20.1
10.20.1.100/24 it o
i c a
r tif
Ce
&
ing
3.1 Low Layer IP Transport Data Configuration
i n
T ra
Description
e i
aw
Learn how to configure the layer 1, layer 2, and layer 3 transport data.
Reference Hu
LMT Offline MML
o n
i
t Port
3.1.1 Task: Configuring a Physical
ic a
i f
e rt
Table 3-1 Configure a physical port
Step Description C Fulfilled
&port.
ng
1 Configure an Ethernet □Yes
i □No
a in
T r
ei
a w
Hu
3.1.2 Task: Configuring a Service and OM IP
Table 3-2 Configure a service and OM IP
1 Add device IP addresses for control plane, user plane, and OM channel. □Yes
□No
n
it o
i c a
r t if
Ce
&
ing
3.1.3 Task: Configuring an IP Route i n
T ra
Table 3-3 Configuring an IP Route
e i
Step Description
aw Fulfilled
1
Hu
Based on the actual network, multiple IP routes can be added to different destination IP by
executing the following MML multiple times.
□Yes
□No
ti on
ic a
t i f
C er
&
ng
ni
r ai
T
ei
a w
H u
3.1.4 Task: Configuring VLAN
Table 3-4 Configuring VLAN
1 Add an entry of mapping from a next-hop IP address to single VLAN. □Yes

□No
n
it o
i c a
r tif
Ce
&
3.2 High Layer Transport Data Configuration
ing
i n
Description
T ra
Learn how to configure the high layer transport data.
e i
aw
Hu
Reference
LMT Offline MML
n
3.2.1 Task: (Optional) ConfiguringioS1 Interface Data in Link Mode
a t
i f ic
t
Table 3-5 Configuring S1 interface data in link mode
Step Description
C er Fulfilled
1
&
Configure the user plane link: Add an IP path. □Yes
ng
□No
i
a in
T r
ei
a w
H u
2 Configure the control plane link: Add an SCTP link. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
3 Add a control port bearer. □Yes
Hu
□No
n
a tio
ic □Yes
if
4 Add an S1 interface.
t
er
□No
C
&
n g
ni
r ai
i T the application type of the IP path for S1 interface. □Yes
e
5 Add
aw
□No
Hu
3.2.2 Task: Configuring S1 Interface Data in Endpoint Mode
Table 3-6 Configuring S1 interface data in endpoint mode
1 Configure the S1-C: Add an SCTP parameter template. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
a
Tr
2 Configure the S1-C: Add an SCTP host. □Yes
ei
□No
a w
Hu
n
a tio
ic
rt if
C e
□Yes
&
3 Configure the S1-C: Add an SCTP peer.
ng
□No
i
ain
T r
ei
a w
H u
4 Configure the S1-U: Add a user-plane host. □Yes

□No
□Yes
n
5 Configure the S1-U: Add a user-plane peer.
□No
it o
i c a
r tif
Ce
&
ing
6 Add an endpoint group.
i n □Yes
T ra □No
e i
aw
Hu
n
a tio
ic
if
7 Add the control-plane and user-plane hosts and control-plane and user-plane peers to the □Yes
t
er
endpoint group. □No
C
&
ng
ni
r ai
T
ei
a w
H u
8 Add an S1 object. □Yes
□No
n
it o
i c a
r t
3.2.3 Task: Configuring S1 Interface Data in Endpoint Mode (Simplified if
Configuration) Ce
&
ng
Simplified configuration is suitable when the S1 control plane and user plane of the eNodeB use the same IP
i
address. Set the global transport parameters using the SET GTRANSPARA command, and then set S1 and
i n
SCTPHOST MOs. The eNodeB then automatically generates USERPLANEHOST and EPGROUP MOs,
ra
and adds them to the EPGROUP MO.
i T
e
aw
Hu
n
atio
ic
rt if
C e
&
n g
The MOs in n i
eNodeB.a i redeNodeB
need to be manually configured. The MOs in black are automatically generated by the
T r The automatically adds MOs to the EPGROUP MO, without manual intervention.
i
e 3-7 Configuring S1 interface data in endpoint mode (simplified configuration)
Table
a w Description
u
Step Fulfilled
H 1 Set the global transport parameters, where the End Point Configure Mode parameter □Yes
must be set to S1SIMPLE_MODE. □No
n
it o
i c a
r tif
Ce
&
ng □Yes
ni
2 Configure the S1-C: Add the SCTP host, and enable the simplified configuration mode.
ai
□No
T r
ei
a w
Hu
n
atio
ic
rtif
C e
3 Add an S1 object.
& □Yes
g □No
in
ain
Tr
ei
a w
H u
3.2.4 Task: Configuring OM Channel Data
Table 3-8 Configuring OM channel data
1 Add a remote maintenance channel. □Yes

□No
n
it o
i c a
r t if
Ce
&
ing
4 eNodeB Radio Data Configuration i n
T ra
e i
About This Chapter
aw
Hu
n
tio
ica
Section Describes
4.1 Sector Data Configuration

t i f Learn how to configure sector data.
e r
C
4.2 Cell Data Configuration Learn how to configure cell data.
&
4.3 *(Optional) Neighboring Cell Data Configuration Learn how to configure a neighboring cell.
i ng
4.1 Sector aData in Configuration
T r
ei
Description
a wLearn how to configure sector data.
Hu Reference
LMT Offline MML
4.1.1 Task: Configuring a Sector
Table 4-1 Configuring a sector
1 Add a sector. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
ei
aw
Hu
Repeat this command to add more sectors.
2 Add a set of sector equipment. □Yes
on
□No
ti
ic a
t i f
C er
&
ng
ni
r ai
T
ei
a w
u
Repeat this command to add more sets of sector equipment.
H
4.2 Cell Data Configuration
Description
Learn how to configure cell data.
Reference
LMT Offline MML
4.2.1 Task: Configuring a Cell
Table 4-2 Configuring a cell

n
it o
1 Add a cell. □Yes
□No
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
Hu
n
atio
ic
rt if
C e
&
n g
i
n command to add more cells.
a i
Repeat this
Bindr the cell with the sector equipment.
T □Yes
ei
2
□No
a w
H u
Repeat this command to add more bind the cell with the sector equipment.
3 Add an operator for the cell. □Yes
□No
n
it o
i c a
r tif
Ce
&
i ng
i n
T ra
ei
aw
Repeat this command to add an operator for the other cell.
4 Activate the cell.
Hu □Yes
on
□No
ti
ic a
t i f
er
Repeat this command to activate another cell.
C
&
g
4.3 *(Optional)nNeighboring Cell Data Configuration
i ni
Description
T ra
ei how to configure a neighboring cell.
Learn
a w
Hu
Reference
LMT Offline MML
4.3.1 Task: Adding an Intra-Frequency Neighboring Cell

1 Add an external E-UTRAN cell. □Yes

□No
n
it o
i c a
r tif
Ce
&
ng
2 (Optional) Add an additional PLMN ID for an external E-UTRAN cell. □Yes
n i □No
i
T ra
e i
aw
3 Hu
Add the neighbor relationship with an intra-frequency E-UTRAN cell. □Yes
n
it o
□No
ic a
rtif
C e
&
ng
ni
r ai
T
ei
a w
H u
4.3.2 Task: Adding an Inter-Frequency Neighboring Cell
1 Add an external E-UTRAN cell. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
2
T ra
(Optional) Add an additional PLMN ID for an external E-UTRAN cell. □Yes
e i □No
a w
Hu
o n
t i
3 Add a neighboring E-UTRAN frequency.
ic a □Yes
i f □No
e rt
C
&
i ng
a in
T r
4
eiAdd the neighbor relationship with an inter-frequency E-UTRAN cell. □Yes
a w □No
H u
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
4.4 *(Optional) TDD Cell Configuration e i
aw
Hu
on
1 Add a TDD LBBP Board. □Yes
i □No
icat
i f
rt
Ce
&
ng
ni
r ai
T
ei
a w
u
2 Add a TDD RRU. □Yes
H □No
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
Hu
n
atio
ic
rtif
3 Add a TDD cell.
C e □Yes
& □No
ng
ni
r ai
T
ei
a w
H u
n
it o
i c a
r t if
Ce
&
ing
i n
T ra
e i
aw
Hu
n
atio
ic
rt if
C e
& MIMO Cell Configuration
4.5 *(Optional) Massive
ng
ni
ai
Massive MIMO is a leading multiple-antenna technology and a key technology for 4.5G. It features the use of
massive antenna arrays (up to 64 antenna arrays) on a single eNodeB for 3D beamforming and multi-user
T r
multiplexing. This technology reduces the demand for site resources, improves network coverage, and
ei
enhances user experience with various services.
a w Traditional multiple-antenna technologies support beam adjustment only on the horizontal plane. Massive
u
MIMO, in contrast, supports adjustment of broadcast beams and downlink traffic beams in both the
H horizontal and vertical planes, significantly enhancing system coverage.

Massive MIMO supports multi-user spatial multiplexing using up to 8 layers in the uplink and 16 layers in
the downlink, significantly improving system capacity.
n
it o
i c a
r t if
Ce
&
ing
i n
T ra
e i
uaw
H
n MIMO is typically deployed in hotspot areas and for
Massive MIMO mainly aims to improve cell coverage and capacity. A massive MIMO site can be deployed
ti o
on new sites or by reconstructing existing sites. Massive
covering tall buildings.
a
iaccommon
f
of the UMPTe are the same as that iof
Massive MIMO requires the deployment of the UMPTe, UBBPe, and 64T64R AAU. The MML commands
t
configure the UBBP, AAU, cellrand massive MIMO.
main control board. The following describes how to
C e
Step Description
& Fulfilled
n g with the CPRI interface type set to XCI_QSFP. □Yes
ni
1 Configure a UBBP,
i
□No
T ra
ei
a w
Hu
2 Add an RRU chain between BBU and AAU, with the topology type set to □Yes
TRUNK_CHAIN. □No
n
it o
i c a
r tif
Ce □No
2 Configure a 64T64R AAU with the RRU type set to AIRU and the numbers of TX and RX □Yes
channels set to 0.
&
ing
i n
T ra
e i
aw
Hu
n
tio □Yes
ica
3 Configure a sector with the number of antennas set to 0.
□No
t i f
C er
&
ng
ni
r ai
4
T
Configure a set of sector equipment with the antenna configuration mode set to BEAM. □Yes
ei □No
a w
H u
5 Activate a weight database file for a beamforming antenna. □Yes

□No
6 Add an antenna device. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
T ra □Yes
i
7 Add a TDD cell with 64T64R and enhanced compression.
e □No
a w
Hu
n
atio
ic
rtif
C e
&
ng
ni
r ai
T
ei
a w
H u
n
it o
8 Set the weight number of the cell sector equipment to the same value as the antenna device □Yes
i c a
if
number. □No
r t
Ce
&
ing
i n
T ra
e i
aw
Hu
5 eNodeB Script Verification ion
a t
f
5.1 Single-eNodeB Script Execution ic
and Verification
rti
5.1.1 Logging In to the eNodeB
Ce Using the U2000 Client in Web Mode
& in the address box of the Internet Explorer: https://U2000_IP
Enter the following address
nghttps://10.77.199.42/10.20.9.94/ in Microsoft Windows 7 or Windows 8 operating system,

address/eNodeB_omIP/.
i
in
For example, enter
a
r
or enter https://10.77.199.42/10.20.9.94/ in Microsoft Windows XP operating system.
i Tto the Web LMT using the default user name admin and password hwbs@com.
e
Log in
a w
H u
Figure 5-1 Logging in to the eNodeB using the OMC in web mode
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
ei
aw
5.1.2 Executing MML Scripts in Batches
Figure 5-2 Executing MML scripts in batches

Hu
n
a tio
ic
rtif
C e
&
n g
ni
r ai
i T
5.2w e
Single-eNodeB Verification Experience
a
Hu5.2.1 Procedure
1. Run the DSP CELL command to check whether Cell Status is Normal
%%DSP CELL: LocalCellId=72;%%
RETCODE = 0 Operation succeeded.
Display dynamic parameters of cells

-----------------------------------
Local Cell ID = 72
Cell Name = 0
Cell instance state = Normal
Reason for latest state change = Cell setup succeeded.
Cell latest setup time = 2018-04-25 11:52:44
Cell latest setup operate type = Act Cell
Cell latest remove time = 0000-00-00 00:00:00
Cell latest remove operate type = No Operation
Cell power save state = Uninstall
Symbol shutdown state = Uninstall
Anti Interfere Status in High Speed Scenario = Disable
n
Primary BBP information = 0-0-2
it o
Cell topology type = Basic Type
a
Maximum transmit power(0.1dBm) = 400
(Number of results = 1)
i c
r t if
Ce
Information About the RF module and BBP Serving the Cell
--------------------------------------------------------
eNodeB ID RF Module Information TX Channel No. RX Channel No. Served BBP Information Work
Status MPT information
&
ng
ni
8787 0-62-0 R0A-R0B R0A-R0B 0-0-2 Normal
0-0-7
a i
Run the DSP BRDVER command to check whether the version T r
2.
e i
version number is displayed, it indicates that the board status is
number of the board is displayed. If the
normal
%%DSP BRDVER:;%%
a w
H u
n
Result of current board software query
it o
--------------------------------------
a
Cabinet No. Subrack No. Slot No. Type Application Type Software Version Hardware Version
ic
BootROM Version Operation Result
t i f
0 0
e
0
r UTRP Node 500.007.10.000 96 00.317.01.001
C
Operation succeeded.
0 0 1 WBBP NodeB 200.019.10.000 17955 01.017.01.002
&
ng
0 0 6 UMPT Node 500.007.10.000 2576 00.010.01.003
i
0
a in 0 6 UMPT GBTS 100.019.10.000 2576 00.010.01.003
Tr
ei
0 0 6 UMPT NodeB 200.019.10.000 2576 00.010.01.003
aw
0 0 6 UMPT eNodeB 100.012.10.000 2576 00.010.01.003
Hu
0 0 16 FAN NULL 3 FAN.0 NULL
0 0 19 UPEU NULL NULL NULL NULL
3. Run the DSP S1INTERFACE command to check the status of the S1-C interface.
%%DSP S1INTERFACE:;%%
Display S1 Interface Information

--------------------------------
S1 Interface ID = 0
S1 Interface CP Bearer ID = 0
CN Operator ID = 0
MME Release = Release 9
S1 Interface Is Blocked = FALSE
Control Mode = MANUAL_MODE
Auto Config Flag = Manual Created
MME Selection Priority = 255
n
CN Operator Sharing Group ID = 255
it o
S1 Interface State = Normal
a
S1 CP Bearer State = Normal
MME Is Overloaded = FALSE
i c
S1 Interface User Number = 0
r tif
Ce
MME Name = NULL
Served PLMNs = 460-01
Served GUMMEIs = 460-01-32769-1
MME Relative Capacity = 255
&
ng
S1 Interface Fault Reason = NULL
n i
i
ra
4. Run the DSP IPPATH command to check the status of the S1-U interface (link mode).
%%DSP IPPATH: PATHID=0;%%
i T
e
DSP IP Path Result

aw
Hu
------------------
Path ID = 0
n
TX Bandwidth(kbit/s) = 0
tio
RX Bandwidth(kbit/s) = 0
a
Non-Realtime Reserved TX Bandwidth(kbit/s) = 0
ic
Non-Realtime Reserved RX Bandwidth(kbit/s) = 0
t if
Realtime TX Bandwidth(kbit/s) = 0
er
Realtime RX Bandwidth(kbit/s) = 0
C
Non-Realtime TX Bandwidth(kbit/s) = 0
Non-Realtime RX Bandwidth(kbit/s) = 0
& Transport Resource Type = High Quality
ng
IP Path Check Result = IP Path Check Disabled
ni
IPMUX Switch Flag = Disable
i Service Type = NULL
ra
Fault Generation Time = NULL
i T (Number of results = 1)
e Sharing Data Configuration

w
6 RAN
H ua
About This Chapter
Section Describes
6.1 RAN Sharing with Common Carriers Data Learn how to configure RAN sharing with common
Section Describes
Configuration carriers data.
6.1 RAN Sharing with Common Carriers Data Configuration
Description
n
Learn how to configure RAN Sharing with Common Carriers data.
it o
i c a
Reference
r tif
Ce
LMT MML
Figure 6-1 RAN sharing with common carriers &

ing
i n
T ra
ei
aw
Hu
n
atio
ic
rt if
C e
&
g
in
6.1.1 Task: Configuring RAN Sharing with Common Carriers Data
a in
Figure r
i T 6-2 Configuring RAN sharing with common carriers data
Step e Description Fulfilled
1a
w Modify the eNodeB sharing mode.
Hu
□Yes
□No
2 Configure the primary and secondary operators. The primary operator must be added □Yes
before the secondary operators are added. □No
n
3 Add a tracking area for the eNodeB. □Yes it o
□No
i c a
r tif
Ce
4 Add a cell operator. & □Yes
ng □No
ni
rai
T
ei
a w
Hu
n
a tio
ic
rt if
C e
&
g
in
5 Configure the number of active users. □Yes
ain □No
T r
ei
a w
H u6 Configure the traffic volume. □Yes
□No
7 Set the traffic sharing type. □Yes

□No
8 Set the portion of traffic of different operators. □Yes

□No
n
it o
i c a
r tif
Ce
&
ing
i n
T ra
e i
aw
Hu
n
a tio
ic
rt if
C e
&
ng
ni
r ai
T
ei
a w
H u
eNodeB LTE V100R013C10 Initial n
atio
i c
Configuration by CME r tif
Ce
Practice Guide &
ing
i n
Tra
e i
u aw
ISSUEH1.00
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Contents
1 Laboratory Networking Introduction ....................................................................................1-1

1.1 Lab Networking ............................................................................................................................................ 1-1
2 Customizing the Summary Data File .....................................................................................2-2

2.1 Task: Logging In to the U2000 ...................................................................................................................... 2-2
n
tio
2.2 Task: Customizing the Summary Data File Base on the Transmission Scenario .......................................... 2-3
a
2.3 Task: (Optional) Basic Edit Operation on Summary Data File ................................................................... 2-11
i c
f 3-16
3 Filling in the Summary Data File .........................................................................................3-15
r t i
e
3.1 Task: Filling in the Common Data Sheet.....................................................................................................
C
3.2 Task: Filling in the Transport Data Sheet .................................................................................................... 3-18
&
3.3 Task: Filling in the Radio Data Sheet .......................................................................................................... 3-19
n g
i
3.4 Task: Filling in the DevIPPattern Sheet ...................................................................................................... 3-21
in
3.5 Task: Filling in the IPRoutePattern Sheet.................................................................................................... 3-22
r a
3.6 Task: Filling in the VLANMAPPattern Sheet ............................................................................................. 3-23
i T
3.7 Task: Filling in the Auto Deployment Sheet ............................................................................................... 3-23
e
a w
4 Creating eNodeBs .................................................................................................................... 4-23
H u
4.1 Task: Creating a Single eNodeB..................................................................................................................
4.1.1 Creating the CME Planned Area ........................................................................................................
4-24
4-24
n
it o
4.1.2 Creating Initial Data of a Single eNodeB........................................................................................... 4-25
4.1.3 Configuring eNodeB Data ................................................................................................................. 4-26
ic
4.1.4 Checking eNodeB Data and Exporting a Data...................................................................................... 4-28
t i f ............................................................................................................ 4-30
r Data..................................................................................................... 4-30
4.2 Task: Creating eNodeBs in Batches
4.2.2 Checking eNodeBC

e
4.2.1 Importing eNodeB Summary
Data and Exporting Data...................................................................................... 4-30
&
i ng
a in
T r
ei
a w
Hu
Figures
Figure 1-1 Lab networking ................................................................................................................................. 1-1
Figure 1-2 Hardware configuration and slot assignment .................................................................................... 1-1
n
a tio
i c
r tif
Ce
&
i ng
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Tables
Table 2-1 Logging in to the U2000 MBB server ................................................................................................ 2-2
Table 2-2 Customizing the summary data file .................................................................................................... 2-3
Table 2-3 Customizing the summary data file .................................................................................................. 2-11
n
Table 3-1 CnOperator ....................................................................................................................................... 3-16
tio
Table 3-2 MME information ............................................................................................................................. 3-16
i
Table 3-3 S-GW information ............................................................................................................................ 3-16
c a
t i f 3-17
r 3-17
Table 3-4 Time source ......................................................................................................................................
C e
Table 3-5 Network time protocol ......................................................................................................................
&
Table 3-6 Time zone and daylight saving time ................................................................................................. 3-17
g
in
Table 3-7 System clock..................................................................................................................................... 3-17
n
a i
Table 3-8 GPS clock information ..................................................................................................................... 3-17
T r
i
Table 3-9 eNodeB data ..................................................................................................................................... 3-18
e
w
Table 3-10 Ethernet port attribute ..................................................................................................................... 3-18
u a
Table 3-11 IP address ........................................................................................................................................ 3-18
H
Table 3-12 GPS Info ......................................................................................................................................... 3-18
o n
i
Table 3-13 IP route (part 1)............................................................................................................................... 3-19
a t
c
Table 3-14 IP route (part 2)............................................................................................................................... 3-19
Table 3-15 LTE cell basic parametersfi(part 1) .................................................................................................. 3-19
r t i
C e (part 2) .................................................................................................. 3-19
Table 3-16 LTE cell basic parameters
& parameters (part 4) .................................................................................................. 3-20

Table 3-17 LTE cell basic parameters (part 3) .................................................................................................. 3-20
n g
Table 3-18 LTE cell basic
i
n cell basic parameters (part 5) .................................................................................................. 3-20
i
Table 3-19 LTE
T ra LTE cell basic parameters (part 6) .................................................................................................. 3-20

Table 3-20
i 3-21 LTE cell basic parameters (part 7) .................................................................................................. 3-21
eTable
a w Table 3-22 Cell sector equipment parameters................................................................................................... 3-21
H u Table 3-23 DevIPPattern sheet (part 1) ............................................................................................................. 3-21
Table 3-24 DevIPPattern sheet (part 2) ............................................................................................................. 3-21
Table 3-25 IPRoutePattern sheet (part 1) .......................................................................................................... 3-22
Table 3-28 VLANMAPPattern Sheet ............................................................................................................... 3-23
Table 3-29 PnP Parameters ............................................................................................................................... 3-23
Table 4-1 Creating the CME planned area ........................................................................................................ 4-24
Table 4-2 Creating initial data of a single eNodeB ........................................................................................... 4-25
Table 4-3 Configuring eNodeB Data ................................................................................................................ 4-26
Table 4-4 Checking eNodeB data and exporting Data ...................................................................................... 4-28
Table 4-5 Importing eNodeB summary data ..................................................................................................... 4-30
n
tio
Table 4-6 Checking eNodeB data and exporting data....................................................................................... 4-30
i c a
r tif
Ce
&
i ng
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
1 Laboratory Networking Introduction
About This Chapter

n
tio
Section Description
i c a
tif
1.1 Lab Networking Describe introduction to the lab networking.
e r
1.1 Lab Networking
C
&
ing
n
Figure 1-1 Lab networking
i
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
Figure 1-2 Hardware configuration and slot assignment
ei
a w
H u
1-1
2 Customizing the Summary Data File
About This Chapter
n
tio
Section Description
2.1 Task: Logging In to the U2000

i c
Describes how to use the U2000 MBB client to log in toa
tif
U2000 MBB server.
2.2 Task: Customizing the Summary Data File
e r
Describes how to customize a summary data file base on
Base on the Transmission Scenario the transmission scenario on the CME. C
&
ng
2.3 Task: (Optional) Basic Edit Operation on Describes how to edit the summary data file on the CME.
i
Summary Data File
i n
Tra
2.1 Task: Logging In to the U2000
e i
aw
Hu
Table 2-1 Logging in to the U2000 MBB server

n
io
1 On the PC, click Start > iManager U2000 MBB Client > U2000 MBB Client. Input the □Yes
a t
user name, password and server IP address, and click Login. □No
i f ic
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
2-2
2.2 Task: Customizing the Summary Data File Base on the
Transmission Scenario
Table 2-2 Customizing the summary data file
1 On the U2000 MBB client, click CME > Advanced > Customize Summary Data File. □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
u aw
H
n
Open a default summary data file that is released with the CME product or a customized
it o
one.
ic a
t i f
e r
C
&
i ng
a in
T r
ei
a w
H u
Click the red zone, and select the transmission scenario. □Yes
2-3
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2-4
2 Select the NE transport configuration mode. □Yes

□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
io
Select the Base station Port Type and set the port count.
a t
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Set the Base station IP Count and select the Vlan Mode. □Yes
2-5
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Set the Base station Interface IP Type.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Set the Base station EPGroup. □Yes

□No
2-6
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Add the IP of SCTPHost.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Add the IP of UserPlaneHost. □Yes

□No
2-7
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Set the S1/X2 Count.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Set the EPGroup used by RAT. □Yes

□No
2-8
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Set the IP of OMCH.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Select the Base station reference clock source. □Yes

□No
2-9
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Finish the customization task.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2-10
2.3 Task: (Optional) Basic Edit Operation on Summary Data File
Table 2-3 Customizing the summary data file
1 On the U2000 MBB client, click CME > Advanced > Customize Summary Data File. □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Open a default summary data file that is released with the CME product or a customized
one.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2-11
□Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra □Yes
i
2 Edit the summary data file as needed.
Modify the group name or the summary data name.
e □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u Modify an attribute.
2-12
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Move lists up or down.
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Select the related tree node to locate the list in the right table to the corresponding node of
the left tree.
2-13
n
atio
i c
r tif
Ce
&
ing
i n
Tra
Add and delete some attribute references in the below table.
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
3 Set whether the Parameters display in the LLD template or not. □Yes
□No
2-14
n
a tio
i c
r tif
Ce
4 &
Save the completed customized summary data file as a data template for later data filling □Yes
in.
n g □No
ni
rai
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ni
r ai
3 Filling
i T in the Summary Data File
e
a w
u
H About This chapter
Section Description
3.1 Task: Filling in the Common Data Sheet Describes how to fill in the common data sheet according
to the network structure.
3-15
Section Description
3.2 Task: Filling in the Transport Data Sheet Describes how to fill in the transport data sheet according
3.3 Task: Filling in the Radio Data Sheet Describes how to fill in the radio data sheet according to
the network structure.
3.4 Task: Filling in the DevIPPattern Sheet Describes how to fill in the DevIPPattern sheet according
n
tio
3.5 Task: Filling in the IPRoutePattern Sheet Describes how to fill in the IPRoutePattern sheet
according to the network structure.
i c a
tif
3.6 Task: Filling in the VLANMAPPattern Sheet Describes how to fill in the PnP Parameters according to
the network structure.
e r
C
&
3.1 Task: Filling in the Common Data Sheet
ing
i n
ra
Open a user-defined summary data file.
Fill the common data in the following tables.
i T
e
aw
Table 3-1 CnOperator
CnOperator
Hu
n
*CN Operator *CN Operator *CN Operator type *Mobile *Mobile network
ID name
ti o country code code
0 0
ic a
CNOPERATOR_PRIMARY 441 00
i f
rt
Ce
&
Table 3-2 MME information
MME Info
n g
ni
ai
*SCTP *First Peer IP First Peer IP Second Peer IP Second Peer IP *Peer SCTP
Peer ID Address Address Mask Address Address Mask Port No.
T r176.11.180.10
0
e i 36412
aw
Hu Table 3-3 S-GW information
S-GW Info
*User Plane Peer ID *Peer IP Address Peer IP Address Mask
0 176.11.41.100
3-16
Table 3-4 Time source
Time Source
Time Source
NTP
n
tio
Table 3-5 Network time protocol
a
Network Time Protocol
i c
tif
*IPv4 Address NTP IP Port Synchronization Authentication Authentication Authentication Master
of NTP Server Mask Number Period(min) Mode Key Key Index Flag
e r
10.175.165.166 123 30 PLAIN C Slave
&
ing
i n
ra
Table 3-6 Time zone and daylight saving time
Time Zone and Daylight Saving Time
i T
e
w
*Time DST Tag DST DST DST DST Start DST Start DST DST DST DST DST End DST End DST DST Time
Zone Information Start Start Start Week Weekday Start End End
a End Week Weekday End Offset(min) Difference(min)
Hu
Mode Month Day Sequence Time Mode Month Day Sequence Time
GM NO
n
io
T+0
t
800
ic a
i f
e rt
C
Table 3-7 System clock
& Source
System Clock Link Management
ngNo.
Clock Working Clock Selected Clock Clock Synchronization Quality
i
in 0
Mode Source Mode Level
MANUAL a
T r GPS TIME QL-SSU-B
ei
a wTable 3-8 GPS clock information
Hu GPS Clock Link Management
GPS Clock No. Cabinet No. Subrack No. Slot No. GPS Work Mode Priority
0 0 0 7 GPS 4
3-17
3.2 Task: Filling in the Transport Data Sheet
Fill in the Transport data in the following tables.
Table 3-9 eNodeB data

eNodeB
*eNodeB *eNodeB *Product Cabinet Mode *eNodeB Base Station BTS *eNodeB
Name ID Type Type Template Configuration Design Radio
n
io
File Template
a t
_SA2 ic
196.11.11 611112 DBS3900 VIRTUAL TDD DBS3900_Vir 611112 Radio_TDD
.12 _LTE tual_TDD_S1
ti f
11_8T8R
e r
C
&
Table 3-10 Ethernet port attribute
n g
ni
ai
Ethernet Port
r
iT
*Port No. *Port Attribute *Speed *Duplex
1 AUTO AUTO e AUTO
a w
Hu
n
tio
ic a
f
Table 3-11 IP address
IP address
rt i
*IP 1 Ce *IP 1 Mask
&
ng
176.11.11.12 255.255.255.0
ni
r ai
i T
Table 3-12 GPS Info
e
w
GPS Clock Link Management
u a Length(m)
Cable
H 0
3-18
Table 3-13 IP route (part 1)
IPRoute
Destination IP1 Destination Mask1 Next Hop IP Address1 VLAN ID1 VLAN Priority1
177.12.164.100 255.255.255.255 177.11.12.1
n
atio
i c
tif
Table 3-14 IP route (part 2)
IPRoute
e r
Destination IP2 Destination Mask2 Next Hop IP Address2 VLAN ID2 C Priority2
VLAN
&
172.12.180.10 255.255.255.255 177.11.12.1
n g
ni
rai
3.3 Task: Filling in the Radio Data Sheet
e iT
Fill in the Radio Data in the following tables.
aw
Table 3-15 LTE cell basic parameters (part 1) Hu
eNodeB LTE Cell
o n
i
t *Cell
*eNodeB *Local BTS Design *Cell
a
icName ID
*TrackingAreaId *Tracking *CN
Name CellID Cell ID
i f area code Operator
rt TCell0 0
ID
192.11.11.12 0 0
C e 0 9 0
&
n g
i ni
a
Tr
Table 3-16 LTE cell basic parameters (part 2)
ei
LTE Cell
a w
NB-IoT TA Csg indicator Uplink cyclic Downlink NB-IoT Coverage Frequency
H uFlag prefix length cyclic prefix Cell Flag Level Type band
length
BOOLEAN BOOLEAN_FA NORMAL_CP NORMAL_CP FLASE 42

_FALSE LSE
3-19
LTE Cell
Uplink Uplink Downlink Downlink Uplink *Physical Additional Cell Cell

EARFCN EARFCN EARFCN bandwidth bandwidth cell ID spectrum active admin
indication emission state state
NOT_CFG 43290 CELL_BW_ CELL_BW_ 1 CELL_A CELL_UN

N100 N100 CTIVE BLOCK
n
atio
i c
r tif
e
LTE Cell C
&
ng
Cell middle *Cell FDD TDD Subframe Special subframe Cell specific Frequency
block timer(min) indication assignment patterns
i
offset(dB)
n
offset(dB)
i
ra
CELL_TDD SA2 SSP7 dB0 dB0
i T
e
aw
Table 3-19 LTE cell basic parameters (part 5) Hu
LTE Cell
o n
i
Preamble tCell
format ca radius(m)
*Root High speed Customized Customized uplink
sequence flag
i f i bandwidth bandwidth(0.1MHz)
rt
index configure indicator
0e
1 LOW_SPEED
C 10000 NOT_CFG
&
n g
i ni
a
Tr
ei
LTE Cell
a w
Customized downlink Reference signal Cell Ue max power Max transmit
H ubandwidth(0.1MHz) power (0.1 dBm) reselection

priority
allowed configure
indicator
power
allowed(dBm)
120 7 NOT_CFG
3-20
LTE Cell
Flag of Multi-RRU Mode of *Cell Cell Radius *Cell Template

Cell Multi-RRU transmission Start
Cell and Location(m)
reception mode
BOOLEAN_FALSE 8T8R Cell_TDD_20M_S1_8T8R_TDL

n
a tio
i c
r tif
Table 3-22 Cell sector equipment parameters
Ce
eNodeB Cell Sector Equipment
&
ng
*eNodeB *LocalCe Sector Baseband Azimuth Electrical Mechanical
Name llID Equipment ID equipment ID
n i
Tilt Tilt
i
196.11.11.12 0 0 255
Tra
e i
3.4 Task: Filling in the DevIPPattern Sheet a w
Hu
Table 3-23 DevIPPattern sheet (part 1)
n
Device IP Address it o
a
*Subrack *Slot No. ic Subboard Type
*Cabinet
i f Port Type Port No.
rt BASE_BOARD ETH
No. No.
7 e
0 0
C Base Station Transport
&7
Data\Ethernet Port\*Port No.
g
in
0 0 BASE_BOARD ETH Base Station Transport
n
Data\Ethernet Port\*Port No.
r ai
i T
e
w
a Table 3-24 DevIPPattern sheet (part 2)
u
H Device IP Address
*VRF Index *IP Address *Mask User Label Borrow IFIP
0 Base Station Transport Base Station Transport Data\IP

Data\IP address\*IP 1 address\*IP 1 Mask
0 Base Station Transport Base Station Transport Data\IP
Data\IP address\*IP 2 address\*IP 2 Mask
3-21
Device IP Address
*VRF Index *IP Address *Mask User Label Borrow IFIP
3.5 Task: Filling in the IPRoutePattern Sheet

n
Table 3-25 IPRoutePattern sheet (part 1)
a tio
IP Route
fi c
*Route Cabinet Subrack *Slot No. Subboard Route Type Port
r
Port tiVRF
Index No. No. Type Type
Ce
No. Index
0 0 0 7 BASE_BOARD NEXTHOP
& 0
n g
ni
0 0 0 7 BASE_BOARD NEXTHOP 0
rai
e iT
IP Route
aw
*Destination IP *Mask Hu Next Hop IP
n
it o
Base Station Transport Base Station Transport Base Station Transport
Data\IPRoute\*Destination IP1 Data\IPRoute\*Destination Mask1 Data\IPRoute\Next Hop IP Address1
ic a
if
Base Station Transport Base Station Transport Base Station Transport
t
Data\IPRoute\*Destination IP2 Data\IPRoute\*Destination Mask2 Data\IPRoute\Next Hop IP Address2
e r
C
&
g
n
ni
Peer IP MTU Switch Maximum Transmission Unit(byte) Preference Description Info
a i
Tr
60
ei
60
a w
H u
3-22
3.6 Task: Filling in the VLANMAPPattern Sheet
Table 3-28 VLANMAPPattern Sheet
VLAN Mapping Based on Next Hop IP
*VRF *Next Hop *Mask *VLAN VLAN ID Set VLAN VLAN

Index IP Mode VLAN Priority Group
Priority No.
n
tio
0 177.11.12.1 255.255.255.255 SINGLEVL 101 DISABLE
a
AN
i c
r tif
Ce
3.7 Task: Filling in the Auto Deployment Sheet &
ing
Table 3-29 PnP Parameters
i n
PnP Parameters
T ra
*Name ESN Sub Sub *Software Cold Patch Hot Patch
ei *Connection Authentication
Network Area Version Version
w
Version
a
Type Type
H u
o n
ti
4 Creating eNodeBs
ic a
i f
e rt
About This Chapter C
&
nglists the contents of this chapter.
The following itable
a in
Section
T r Description
ei Creating a Single eNodeB aDescribes

4.1 Task: how to create and a planned area and create initial data of
a w single eNodeB using the CME.
Hu4.2 Task: Creating eNodeBs in Batches Describes how to create eNodeBs in batches using the CME.
4-23
4.1 Task: Creating a Single eNodeB
4.1.1 Creating the CME Planned Area
Table 4-1 Creating the CME planned area
1 □Yes
n
tio
□No
i c a
r tif
Ce
&
ing
2 Input the area name and click OK.
i n □Yes
Tra □No
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
4-24
n
atio
i c
r tif
Ce
&
ing
i n
After a while, an empty planned area will be created.
Tra
e i
a w
4.1.2 Creating Initial Data of a Single eNodeB
H u
Table 4-2 Creating initial data of a single eNodeB
n
Step Description it o Fulfilled
ic aApplication >Create Base Station, and start the

1 On the U2000 MBB client, click LTE
t i f □Yes
r
wizard on the CME. □No
C e
&
i ng
a in
T r
ei
a w
Hu Fill the eNodeB basic data, and select the corresponding template to finish the creation.
4-25
n
atio
i c
r tif
Ce
&
ing
i n
ra
Click Next, and then click Finish.
i T
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
ra
4.1.3 Configuring
T eNodeB Data
e i
a w Table 4-3 Configuring eNodeB Data
H u1 Modify the device data. □Yes

□No
4-26
n
atio
i c
r tif
Ce
&
ing
i n
ra
2 Modify the transmission data. □Yes
i T □No
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a wModify the radio data.
H u3 □Yes
□No
4-27
n
atio
i c
r tif
Ce
&
ing
i n
T ra
4.1.4 Checking eNodeB Data and Exporting Data ei
a w
Table 4-4 Checking eNodeB data and exporting Data
H u
o n
1
i
the Main View window. Right-click theteNodeB, select the Check eNodeB Data menu to
After creating the eNodeB successfully, you can find the "eNodeB" you've configured in □Yes
ic a □No
i f
check the data
r t
C e
&
i ng
a in
T r
ei
a w
Hu
2 If the eNodeB data check is successful, right-click the eNodeB, and select Export NE □Yes
Files. □No
4-28
n
atio
i c
r tif
Ce
&
ing
The Export NE Files window is displayed. Set the file path and cancel the check flags
n
(because you already do it in previous step), select the base station, and click OK. The
i
ra
eNodeB configuration file (in XML format) will be exported to your PC.
T
The file can be used for LMT local commissioning or USB commissioning.
i
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
4-29
4.2 Task: Creating eNodeBs in Batches
4.2.1 Importing eNodeB Summary Data
Table 4-5 Importing eNodeB summary data
1 □Yes
n
tio
□No
i c a
r tif
Ce
&
ing
i n
Tra
e i
u aw
H Data
4.2.2 Checking eNodeB Data and Exporting
n
tio
Table 4-6 Checking eNodeB data and exporting data
Step Description a
ic Fulfilled
i f
t to CME
1
e r
After the summary data is imported successfully, you can find the eNodeB you've □Yes
Data menu to check the C

configured in the Main View window. Right-click the eNodeB, select the Check eNodeB □No
data.
&
i ng
a in
T r
ei
a w
H u
2 If the eNodeB data check is successful, right-click the eNodeB, and select Export NE □Yes
Files.
4-30
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
io
The Export NE Files window is displayed. Set the file path and cancel the check flags
a t
(because you already do it in previous step), select the base station, and click OK. The
ic
eNodeB configuration file (in XML format) will be exported to your PC.
i f
rt
The file can be used for LMT local commissioning or USB commissioning.
Ce
&
n g
i ni
a
Tr
ei
a w
H u
4-31
3 If you want to perform remote commissioning, you can select the menu shown in the □Yes
following figure. The configuration file can be exported to U2000 MBB server for remote □No
commissioning (Auto Deployment).
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
4-32
eNodeB LTE V100R013C10 Reconfiguration n
atio
i c
tif
Practice Guide
e r
ISSUE1.00 C
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Contents
1 Adding an FDD/NB-IoT Cell (Common) ................................................................................. 6

1.1 Application Scenario ........................................................................................................................................ 6
1.2 Task Description ............................................................................................................................................... 6
1.3 Engineering Preparation ................................................................................................................................... 6
1.3.1 Information Collection ............................................................................................................................ 6
n
tio
1.3.2 Data Preparation...................................................................................................................................... 7
1.4 Engineering Implementation ..........................................................................................................................a18
i f ic 18
t 21
1.4.1 CME-based Operations .........................................................................................................................
r
Ce
1.4.2 MML-based Operations ........................................................................................................................
1.5 Engineering Verification................................................................................................................................. 24
&
2 Changing the Cell Bandwidth ..................................................................................................
n g 24
i
in
2.1 Application Scenario ...................................................................................................................................... 24
r a
2.2 Task Description ............................................................................................................................................. 25
i T
2.3 Engineering Preparation ................................................................................................................................. 25
e
2.3.1 Information Collection .......................................................................................................................... 25
a w
2.3.2 Data Preparation.................................................................................................................................... 25
H u
2.4 Engineering Implementation .......................................................................................................................... 33
2.4.1 CME-based Operations ......................................................................................................................... 33
o n
2.4.2 MML-based Operations ........................................................................................................................ 36
a ti
f ic
3 Changing the Cell EARFCNs....................................................................................................
i
40
r t
e
C
& .......................................................................................................................... 41
ng .................................................................................................................................... 41
3.3.1 Information Collection
3.3.2 Data iPreparation
a in Implementation .......................................................................................................................... 47
r CME-based Operations ......................................................................................................................... 47
3.4 Engineering
T
e3.5i Engineering Verification................................................................................................................................. 50
3.4.1
4a
w
Hu 4.1 Application Scenario ...................................................................................................................................... 50
Changing the Neighboring Cell Parameters.......................................................................... 50

5 Changing the Cell ID ................................................................................................................. 61

n
tio
a
6 Adding a Neighboring eNodeB ............................................................................................... 71 i

f 71c
r t i
e
6.1 Application Scenario ......................................................................................................................................
C
&
g
in
n
ai
T r
e i
w
6.4.2 MML-based Operations ........................................................................................................................ 81
a
Hu
7 Adding an S-GW Connection ................................................................................................... 84
n
it o
ic a
t i f
r
7.4 Engineering Implementation

e
7.3.2 Data Preparation....................................................................................................................................
C .......................................................................................................................... 93
86
& ......................................................................................................................... 93
g Operations ........................................................................................................................ 96
7.4.1 CME-based Operations
i n
7.4.2 MML-based
i n Verification............................................................................................................................... 100
a
7.5 Engineering
8 Changingrthe VLAN Mode from VLAN Group to Single VLAN ................................... 101
T
i Application Scenario .................................................................................................................................... 101
e8.1
a w 8.2 Task Description........................................................................................................................................... 101
Hu
8.3 Engineering Preparation ............................................................................................................................... 101
8.3.1 Information Collection ........................................................................................................................ 101
8.3.2 Data Preparation.................................................................................................................................. 101
8.4 Engineering Implementation ........................................................................................................................ 109
8.4.1 CME-based Operations ....................................................................................................................... 109
8.4.2 MML-based Operations ...................................................................................................................... 113
8.5 Engineering Verification............................................................................................................................... 116
9 Changing the eNodeB ID ........................................................................................................ 117

9.1 Application Scenario .................................................................................................................................... 117
9.2 Task Description ........................................................................................................................................... 117
9.3 Engineering Preparation ............................................................................................................................... 117
9.3.1 Information Collection ........................................................................................................................ 117
9.3.2 Data Preparation.................................................................................................................................. 118
9.4 Engineering Implementation ........................................................................................................................ 122
9.4.1 CME-based Operations ....................................................................................................................... 122
9.5 Engineering Verification............................................................................................................................... 126
n
10 Changing Cabinet and Subrack No..................................................................................... 126
a tio
i c
f 126
10.1 Application Scenario .................................................................................................................................. 126
t
r 127i
10.2 Task Description .........................................................................................................................................
C e
10.3 Engineering Preparation .............................................................................................................................
&
10.3.1 Information Collection ...................................................................................................................... 127
ng
10.3.2 Data Preparation................................................................................................................................ 127
i
in
10.4 Engineering Implementation ...................................................................................................................... 130
a
10.5 Engineering Verification............................................................................................................................. 134
T r
11 Replacing the Main Control Board ...................................................................................... 134
e i
w
u a
11.2 Task Description ......................................................................................................................................... 134
H
n
i o
11.3.2 Data Preparation ................................................................................................................................
t
135
ic a
11.3.3 Commissioning Preparation .............................................................................................................. 140
i f
11.4 Engineering Implementation ......................................................................................................................
t
144
e r
11.5 Engineering Verification ............................................................................................................................. 151
12 Transmission CapacityC Expansion from One UMPT Board to Two UMPT Boards
&
(FDD/NB-IoT) ............................................................................................................................... 151
n g .................................................................................................................................. 151
i
12.1 Application Scenario
in Preparation ............................................................................................................................. 152

a
T r Information Collection ...................................................................................................................... 152
12.3 Engineering
ei 12.3.2 Data Preparation................................................................................................................................ 153

12.3.1
a w 12.4 Engineering Implementation ...................................................................................................................... 160

Hu 12.4.1 Local Operations ............................................................................................................................... 160
12.4.2 Remote Operations............................................................................................................................ 160
12.4.3 CME-based Operations ..................................................................................................................... 160
12.4.4 MML-based Operations .................................................................................................................... 164
13 Replacing BBPs ........................................................................................................................ 168

13.3 Engineering Preparation ............................................................................................................................. 168
13.3.2 Data Preparation................................................................................................................................ 169
13.4.1 CME-based Operations ..................................................................................................................... 176
13.4.2 MML-based Operations .................................................................................................................... 180
n
a tio
i c
r tif
Ce
&
i ng
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
1 Adding an FDD/NB-IoT Cell (Common)
 There are weak-signal areas or coverage holes in the current eNodeB coverage, requiring an additional
cell to supplement coverage.
 As the eNodeB traffic increases, the capacity requirements of cell edge UEs (CEUs) cannot be met. In
this situation, the coverage areas of the existing cells need to be reduced and an additional cell needs
to be added.
n
 The operator uses a new frequency band.
a tio
i c
tif
1.2 Task Description
e r
C
There is a weak-signal area in the current eNodeB coverage. We need to add an additional FDD/NB-IoT
cell to supplement coverage. We adopt the following scheme: add an LBBP and an RF module. Figure 1
shows the topology changes after an LBBP and an RF module are added.
&
ing
n
Figure 1-1 Topology changes
i
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
1.3 Engineering Preparation
g
in Collection
in
1.3.1 Information
Whether… r
a
i T Judging Writing the specific information
e resources are insufficient □Yes

w
The baseband
u a □No
H The RF resources are insufficient □Yes

□No
An RET is to be configured □Yes
□No
A TMA is to be configured □Yes
□No
Whether… Judging Writing the specific information
A new Sector is to be configured □Yes

□No
A new Cell is to be configured □Yes
□No
A new License is to be prepared □Yes
□No
n
A new Software is to be prepared □Yes
a tio
i c
tif
□No
e r
C
1.3.2 Data Preparation
&
Task 1 Data preparation by using the "batch reconfiguration"in
g
mode of the CME
n
Step Description
r ai Fulfilled
i T File (CME client □Yes

1. On the menu bar, choose Advanced > Customize Summary Data
e (U2000 client mode). □No
mode) or CME > Advanced > Customize Summary Data File
A dialog box is displayed for you to open the summary a w
u
data file.
H
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
2.
eiInBulktheConfiguration
dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
a w function of customizing a summary data file.

> eNodeB > base station version, Click OK to enable the □No
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
. Select a scenario-based template: Cell Data a
w □Yes
u
3.
Click Reconfigurations > Adding
an FDD Cell (or Adding an NB-IoT Cell), select MOs
click OK.
H you want to change, and then □No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
4. □Yes
Click , specify a save path for the exported file, save the summary data file to a
local PC. The CME automatically customizes the parameter names contained in the □No
template in the summary data file.
n
a tio
i c
tif
r
e
C □Yes
5.
& □No
Based on the parameter names in the summary data file, export the eNodeB data to be
g
reconfigured from the planned data area to the summary data file.
i
On the menu bar of the planned data area, choose LTE Application > Export n >Data >
Export Base Station Bulk Configuration Data (CME client mode) or CME
a inData LTE
Application > Export Data > Export Base Station Bulk Configuration
T r
ei
(U2000 client mode). The data export function is enabled.
a w
Hu
n
it o
ic a
t i f
e rin sequence "Scenario > Adjust data by NE >
version >NEs need to C
6. Select the following options □Yes
&
be adjusted" in the pop-up dialog box. Click "Next". □No
i ng
a in
Tr
ei
a w
H u
7. 1. Select Bulk configuration template. □Yes

□No
2. In Bulk configuration data file, select the prepared file and export configuration
data from the CME based on the MOs in this file.
3. In Export path, specify a save path for the file that contains the exported data.
4. Click "Next", the CME verifies the configuration data to be exported. After the
n
tio
export is complete, click "Finish".
i c a
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio □Yes
a
8. Open the local summary data file and reconfigure data in the summary data file based
ic
on planned data. □No
i f
t file into the CME.
r □Yes
Ce Configuration
9. Import the edited summary data
On the menu bar of the planned data area, choose LTE Application > Import Data > □No
& Data > Import Base Station Bulk Configuration Data

Import Base Station Bulk Data (CME client mode) or CME > LTE
(U2000 client g
Application > Import
n
ni
mode). The data import function is enabled.
i
T ra
ei
aw
Hu
10. Select files to import and data types to adjust, select "I have read the note" and click □Yes
Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
11. Select base stations whose data you want to import and click Next. □Yes
Hu
□No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u 12. After the import is complete, click "Finish". Finish the data preparation by using
"batch reconfiguration" mode of CME.
□Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
Task 2 Data preparation by using the GUI mode of CME e i
aw
Hu
1 Configure baseband equipment data of the base station. □Yes
o nthe shortcut
In the left pane of the planned data area, right-click an eNodeB you want to □No
reconfigure and choose Device Panel from
ti menu. The eNodeB device
panel is displayed.
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
2 Add an LBBP board. □Yes

Select the slot for installing a board. Right-click the slot and choose to add a required □No
board.
n
atio
i c
r tif
Ce
&
ng
3 Set board parameters and click OK. □Yes
ni
□No
rai
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ni
i
4
r a
Add an RRU chain.
InTthe lower left part of the device panel, right-click TOPO and choose Add Chain
□Yes
eifrom the shortcut menu.

□No
a w
H u
5 Based on the planned data, set the related information such as the number and □Yes
networking mode of the RXU chain/ring and the port on the board to which the RXU □No
chain/ring head is connected. Click OK. The configured RXU chain/ring is displayed
under the TOPO node.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hauconfigured RXU chain, and
6 Add an RRU. □Yes
In the lower left part of the device panel, right-click □No
n
choose Add Board > Board Type from the shortcut menu. A dialog box is displayed
for you to add an RF board.
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
7 In the dialog box, set the working mode and other related attributes for the RRU. □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra □Yes
i
8 Configure ALDs on the device panel.
e □No
w
In the right pane of the device panel, click RET and configure RET and
a
RETSUBUNIT. After the configuration is complete, click OK.
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i
9 Configure sectors and cells. □Yes
i nand
In the left pane of the planned data area, right-click a base station you want to □No
r aresourcechoose
configure Carrier Resource Management from the shortcut menu. The
iT
carrier management window is displayed.
e
aw
Hu
n
a tio
i c
r tif
e
C □Yes
10
& □No
Right-click in the blank area of sector zone and choose Add Sector from the shortcut
g
menu. In the displayed dialog box, set the sector attributes and antennas. Click "OK".
n in
rai
i T
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu11 Right-click the sector icon to add sector equipment, In the displayed dialog box, set the
sector equipment attributes. Click "OK".
□Yes
□No
n
a tio
i c
rtif
12 Right-click in the blank area of cell zone and choose to create LTE cell from the e
C □No
□Yes
&
shortcut menu. In the displayed dialog box, set the cell attributes. Click "OK".
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ni
r ai
T can search another MOs in the object navigation tree, click the Search tab and type
eithe MO information you want to configure. The CME automatically finds the
13 We □Yes
□No
aw
corresponding MOs. Double-click the MO you want to configure and edit the planned
Hu
data in the right pane. Click to save the configured data.
n
atio
i c
r tif
Ce
&
ng
Task 3 Data preparation by using the MML
n i
Step Description
i Fulfilled
1 Prepare MML configuration scripts

Tra □Yes
e i □No
a w
1.4 Engineering Implementation Hu
n
1.4.1 CME-based Operations tio
ic a
Step Description
i f Fulfilled
rt
Ce
1 Set the eNodeB engineering maintenance mode to expand status to prevent any alarm □Yes
from being reported during the reconfiguration. □No
&
On the U2000 Client, choose Configuration > Settings > Maintenance Mode
n g
(application style) or Maintenance > Maintenance Mode (traditional style).
ini
a
Tr
ei
a w
H u
2 □Yes
Click at the upper left corner of the Maintenance Mode window.
□No
In the Set Maintenance Mode dialog box, select the eNodeBs to be configured. Set
NE maintenance mode to a customized expand status. Click OK to complete the
setting. In the displayed Confirm dialog box, click Yes.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
3 Hu
Deliver and activate the configuration on the eNodeB. □Yes
n
it o
On the menu bar of the planned data area, choose Area Management > Planned □No
Area > Export Incremental Scripts (CME client mode) or CME > Planned Area >
ic a
Export Incremental Scripts (U2000 client mode) to start the wizard of exporting
if
scripts.
r t
Ce
&
n g
ini
a
Tr
ei
a w
H u4 Select Launch script executor only in the wizard to activate exported scripts for data
to take effect on the live network.
□Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
ie
a w
5 Set the Maintenance Mode of the eNodeB to NORMAL.
u
H > Maintenance Mode
□Yes
□No
On the U2000 Client, choose Configuration > Settings
n
it o
ic a
t i f
e r
C
&
i ng
Click in at the upper left corner of the Maintenance Mode window. In the Set
□Yes
a Mode dialog box, select the eNodeBs to be configured. Set NE
6
T r
Maintenance □No
imaintenance mode to NORMAL. Click OK to complete the setting. In the displayed
e Confirm dialog box, click Yes.
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
1.4.2 MML-based Operations tio
ic a
Step Description
i f Fulfilled
rt
Ce
&
Run the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in
n g
MML input window.
i ni
a
Tr
ei
a w
H u
3 From the main menu of the U2000 client, choose Trace and Maintenance > □Yes
Maintenance > MML Command (application style) or Maintenance > MML □No
Command (traditional style).
n
□Yes
a tio
c
4 In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, select
i
tif
the eNodeBs to be reconfigured, click to enter the script mode. □No
e r
C
&
ing
i n
Tra
e i
aw
Hu
n
tio
a
ic
i f
5
e rt the MML commands to be executed in sequence to
In the right pane, copy and paste □Yes
to C
□No
&
area 1, Click create a batch processing task.
i ng
a in
Tr
ei
a w
H u
6 In the New Task dialog box, enter a name in Task Name. Choose Other > MML □Yes
Script in Task Type. Set Execution Type, and click Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
7 Set the time or period to execute the task and click Next.
Tra □Yes
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u8 Select the Select NE option. In the Confirm dialog box displayed, click OK. Select □Yes
the eNodeBs on which the MML scripts are to be executed, set Run Mode and □No
Execution Result, and click Finish.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
9 Set the Maintenance Mode of the eNodeB to NORMAL. □Yes
Hu
Run the following command: SET MNTMODE: MNTMODE=NORMAL in MML □No
input window.
n
tio
ic a
i f
rt
Ce
&
n g
ni Verification
1.5 Engineering
i
r a
Step
T
Description Fulfilled
eiCheck whether MOs have been modified. □Yes

aw
1
□No
Hu
2 Changing the Cell Bandwidth
The current bandwidth is less than 20 MHz and cannot meet service requirements due to the growing
number of users.
As the growing number of users, we need to expand bandwidth to meet service requirement. We adopt the
following scheme: change cell bandwidth into 20Mhz. Figure 2 shows the changes of topology.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
2.3 Engineering Preparation aw
2.3.1 Information Collection Hu
n
Whether…
tio Judging Writing the specific information
c a
it fi
The baseband resources are insufficient □Yes
r
□No
The RF resources are insufficient e
C □Yes
& □No
The transmission rate ofg
in
the optical module is insufficient □Yes
n
aiis to be collected
□No
T r
Cell information □Yes
e i □No
a w
H u
Task 1 Data preparation by using the "batch reconfiguration" mode of the CME
1. On the menu bar, choose Advanced > Customize Summary Data File (CME client □Yes
mode) or CME > Advanced > Customize Summary Data File (U2000 client mode). □No
A dialog box is displayed for you to open the summary data file.
n
atio
i c
r tif
Ce
& □Yes
ng
2. In the dialog box, select the following options in sequence Default > NodeB/eNodeB
Bulk Configuration > eNodeB > base station version, Click OK to enable the
ni
□No
function of customizing a summary data file.
rai
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
3.w
a □Yes
H u Click . Select a scenario-based template: Cell Data Reconfigurations >Changing

the Cell Bandwidth, select MOs you want to change, and then click OK. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
4. □Yes
Hu
Click to perform rule check against the template. If the check is passed, the
"Rule check is successful." message will be displayed. □No
n
tio
ic a
i f
rt
Ce
5.
Click &
, specify a save path for the exported file, save the summary data file to a
□Yes
ng
local PC. The CME automatically customizes the parameter names contained in the □No
n i
r ai
i T
e
aw
Hu
6. Based on the parameter names in the summary data file, export the eNodeB data to be □Yes
reconfigured from the planned data area to the summary data file. □No
On the menu bar of the planned data area, choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode) or CME > LTE
Application > Export Data > Export Base Station Bulk Configuration Data
n
atio
i c
r tif
Ce
&
ng
□Yes
ni
7. Select the following options in sequence "Scenario > Adjust data by NE >
ai
version >NEs need to be adjusted" in the pop-up dialog box. Click "Next". □No
r
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u

□No
n
tio
i c a
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio □Yes
a
ic
i f
r □Yes
Ce Configuration

(U2000 client g
n
ni
i
T ra
ei
aw
Hu
Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
□No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
13. After the import is complete, click "Finish". Finish the data preparation by using □Yes
"batch reconfiguration" mode of CME. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
Task 2 Data preparation by using the GUI mode of CME
on
t i □Yes
a
1 Configure baseband equipment data of the base station.
f ic from the shortcut menu. The eNodeB device

In the left pane of the planned data area, right-click an eNodeB you want to
i
□No
rt
reconfigure and choose Device Panel
e
panel is displayed.
C
&
i ng
a in
T r
ei
aw
Hu
2 Add an LBBP board. □Yes

Select the slot for installing a board. Right-click the slot and choose to add a required □No
board.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
3 Set board parameters and click OK.
e i □Yes
aw
□No
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u4 We can search another MOs in the object navigation tree, click the Search tab and type
the MO information you want to configure. The CME automatically finds the
□Yes
□No
corresponding MOs. Double-click the MO you want to configure and edit the planned
data in the right pane. Click to save the configured data.
n
atio
i c
r tif
Ce
&
ng
n i
Step Description
i Fulfilled
1 Prepare MML configuration scripts

Tra □Yes
e i □No
a w
2.4 Engineering Implementation Hu
n
2.4.1 CME-based Operations tio
ic a
Step Description
i f Fulfilled
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2 □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ica
i f
t on the eNodeB.
3
e r
Deliver and activate the configuration □Yes
C Scripts (CME client mode) or CME > Planned Area >

& Scripts (U2000 client mode) to start the wizard of exporting

Area > Export Incremental
ng
Export Incremental
i
scripts.
a in
T r
ei
aw
Hu
4 Select Launch script executor only in the wizard to activate exported scripts for data □Yes
to take effect on the live network. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
a w
u
□Yes
□No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
6 □Yes
Click at the upper left corner of the Maintenance Mode window. In the Set
Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE □No
maintenance mode to NORMAL. Click OK to complete the setting. In the displayed
Confirm dialog box, click Yes.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
e rt
C
2.4.2 MML-based Operations
&
Step Description
n g Fulfilled
i
1
from a in reported
Set the eNodeB engineering maintenance mode to expand status to prevent any alarm □Yes
r being during the reconfiguration.
T the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in
□No
iRun
e MML input window.
a w
H u
n
a tio
i c
r tif
3 In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, selecte
C □No
□Yes
&
the eNodeBs to be reconfigured, click to enter the script mode.
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
4 eiIn the right pane, copy and paste the MML commands to be executed in sequence to □Yes
a w □No
H u area 1, Click to create a batch processing task.

n
a tio
i c
tif
Script in Task Type. Set Execution Type, and click Next.
e r
□No
C
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
ert
C
6
&
Set the time or period to execute the task and click Next. □Yes
ng
□No
i
a in
Tr
ei
a w
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
7 Select the Select NE option. In the Confirm dialog box displayed, click OK. Select □Yes
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u

input window.
n
a tio
2.5 Engineering Verification
fi c
r ti
e
1 Check whether MOs have been modified. C □Yes

& □No
ing
i n
3 Changing the Cell EARFCNs Tra
e i
u aw

H
The current EARFCNs of the cell are inappropriate.
n

The operator needs to re-plan frequency resources.
3.2 Task Description ti o

a
ic resources. Figure 3 shows the cell information changes.
i f
rt
One operator needs to re-plan frequency
C e
Figure 3-1 Cell information changes
&
i ng
a in
T r
ei
a w
Hu
The EARFCNs of cells need to be collected □Yes

□No
n
3.3.2 Data Preparation a tio
i c
r tif
Task 1 Data preparation by using the CME-provided "radio data planning file".
e
C Fulfilled
Step Description
&
ng
1. To ensure that the associated parameters of the external cells in the current data area □Yes
are consistent, choose System > Options (CME client mode) or CME > Options
n i □No
i
ra
(U2000 client mode) on the menu bar of the main window. The setting function is
T
started.
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
g
 The CME-provided "radio data planning file" supports automatic update of the information about
n
external cells when cell-related parameters are modified.
i ni
 On the LTE network, this option applies only to radio network planning data and ID/name
a
modification.
T r □Yes
eisynchronize cell parameters in the entire network and click OK.

2. On the Cell Parameter Auto-Synchronization Policy tab page, select Auto
□No
a w
H u
n
a tio
i c
r tif
Ce
&
ing
i n
3.
Tra
On the menu bar of the planned data area, choose CME > LTE Application > Export □Yes
e i
Data > Export Radio Network Planning Data (U2000 client mode) or LTE □No
w
Application > Export Data > Export Radio Network Planning Data (CME client
a
mode). Export planned radio data from the CME to the file.
Hu
n
tio
ic a
i f
rt
Ce
&
n g □Yes
ni
4. A dialog box is displayed for you to select NEs. Choose NE version, add the NEs to be
ai
reconfigured from the left pane to the right pane, and click Next. □No
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
5. Add the Cells to be reconfigured from the left pane to the right pane, and click Next. □Yes
Hu
□No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
6. Select the radio network planning objects those need to be reconfigured, and click □Yes
Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
7.
Tra □Yes
Click
e i
, specify a save path for the exported file, and click Next. The CME starts
□No
w
the export. After the export is complete, click Finish.
a
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
8. Edit data in the file based on the prepared data. Then, close the file. □Yes
□No
9. Import the edited data file into the CME. □Yes
On the menu bar of the planned data area, choose CME > LTE Application > Import □No
Data > Import Radio Network Planning Data (U2000 client mode) or LTE
Application > Import Data > Import Radio Network Planning Data (CME client
mode). A dialog box is displayed for you to import planned radio data.
n
atio
i c
r tif
Ce
&
ng
10. Click Add, select the file to be imported. Then, click Next. □Yes
ni
□No
rai
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w □No
H u
n
atio
i c
r tif
Ce
&
ng
i
n
12.
r ai click Next.
Select the radio network planning objects those need to be imported, and □Yes
i T
The CME starts the import. After the import is complete, click Finish. □No
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
n
tio
i c a
r tif
Ce
&
ing
2
i n □Yes
ra
□No
T
i
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
3 Run the MOD GLOBALPROCSWITCH command to set the values of the options □Yes
under the X2-based Neighboring Cell Configuration Update Switch to OFF □No
n
a tio
□Yes
i c
□Noif
4 Run the MOD ENODEBALGOSWITCH command to set the values of the options
under the ANR algorithm switch to OFF.
r t
Ce
&
ing
i n
Tra
e i
u aw
5
H
Deliver and activate the configuration on the eNodeB. □Yes
Area > Export Incremental Scripts (CMEn

it o mode) to start the wizard of exporting

client mode) or CME > Planned Area >
a
Export Incremental Scripts (U2000 client
scripts.
f ic
r t i
C e
&
i ng
a in
T r
ei
6 w
u a Select Launch script executor only in the wizard to activate exported scripts for data □Yes
H
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
a w
u
□Yes
□No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
8 □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
e rt
C
&
Step Description
i ng Fulfilled
1
a in MOs have been modified.
Check whether □Yes
T r □No
e i
aw
Hu4 Changing the Neighboring Cell Parameters
The previous neighboring cell parameter plan is inappropriate and a new plan is required.

Add the cells of LTE "ADDNENB" and UMTS "NODEB" to be the neighboring cells of LTE
"LTETEST010". Figure 4 shows the topology information.
Figure 4-1 Topology information
n
atio
i c
r tif
Ce
&
ing
4.3 Engineering Preparation i n
Tra
e i
Base Station Frequency Bandwidth
aw
CELLID MCC MNC LAC TAC
Hu
band
LTE ADDNENB
n
LTETEST010
tio
UMTS NODEB
ic a
i f
e rt
4.3.2 Data PreparationC
&
n g
ni
Task 1 Data preparation by using the CME-provided "radio data planning file".
Step
ai
Description
r
Fulfilled
Tensure that the associated parameters of the external cells in the current data area
eiare consistent, choose System > Options (CME client mode) or CME > Options
1. To □Yes
aw
□No
Hu
started.
n
atio
i c
r tif
Ce
&
ng
modification.
n i
2. On the Cell Parameter Auto-Synchronization Policy tab page, select Auto
i □Yes
synchronize cell parameters in the entire network and click OK.
Tra □No
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
eiOn □Yes
w
3. the menu bar of the planned data area, choose CME > LTE Application > Export
a
Data > Export Radio Network Planning Data (U2000 client mode) or LTE □No
H u Application > Export Data > Export Radio Network Planning Data (CME client
mode). Export planned radio data from the CME to the file.
n
atio
i c
tif
4. A dialog box is displayed for you to select NEs. Choose NE version, add the NEs to be □Yes
reconfigured from the left pane to the right pane, and click Next.
e r
□No
C
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g □Yes
ni
5. Add the Cells to be reconfigured from the left pane to the right pane, and click Next.
ai
□No
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
6. Select the radio network planning objects those need to be reconfigured, and click □Yes
Hu
Next. □No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
7. □Yes
Click , specify a save path for the exported file, and click Next. The CME starts
the export. After the export is complete, click Finish. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
8.
tio
Edit data in the file based on the planning data. Then, close the file. □Yes
a
icCME.
□No
f
Import the edited data file into ithe
rt data area, choose CME > LTE Application > Import
9. □Yes
e
On the menu bar of the planned
Data > Import Radio C Network Planning Data (U2000 client mode) or LTE
□No
&is displayed for you to import planned radio data.

Application > Import Data > Import Radio Network Planning Data (CME client
ng
mode). A dialog box
i
a in
Tr
ei
a w
H u
10. Click Add, select the file to be imported. Then click Next. □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
w
a Next.
11.
u
Select base stations whose data you want to import, click
H
□Yes
□No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu 12. Select the radio network planning objects those need to be imported, and click Next. □Yes
The CME starts the import. After the import is complete, click Finish. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
4.4 Engineering Implementation e i
aw
Hu
Step Description
o n Fulfilled
i
t mode to expand status to prevent any alarm
a □Yes
fic
1 Set the eNodeB engineering maintenance
i
On the U2000 Client, choosetConfiguration
r > Settings > Maintenance Mode
Ce
&
i ng
a in
T r
ei
aw
Hu
2 □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
t Cell Configuration
3
r
Run the MOD GLOBALPROCSWITCH command to set the values of the options □Yes
Ce
under the X2-based Neighboring Update Switch to OFF □No
&
i ng
a in
T r
ei
aw
Hu4 Run the MOD ENODEBALGOSWITCH command to set the values of the options
under the ANR algorithm switch to OFF.
□Yes
□No
n
atio
fi c
i
5 Deliver and activate the configuration on the eNodeB. □Yes
r
□Not
Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > e
On the menu bar of the planned data area, choose Area Management > Planned
Export Incremental Scripts (U2000 client mode) to start the wizard of exporting C
scripts. &
g
n in
r ai
i T
e
a w
H u
o n
i
Select Launch script executor only intthe wizard to activate exported scripts for data
to take effect on the live network. a
6 □Yes
i f ic □No
e rt
C
&
i ng
a in
Tr
ei
a w
H u

On the U2000 Client, choose Configuration > Settings > Maintenance Mode □No
n
a tio
i c
rtif
8
Click at the upper left corner of the Maintenance Mode window. In the Set e□Yes
C □No
&
Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE
ng
n i
i
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
1 Check whether MOs have been modified. □Yes

□No
5 Changing the Cell ID
The previous cell ID plan is inappropriate and a new plan is required.
n
The cell ID of an LTE cell served by an eNodeB needs to be changed to 200. The eNodeB has
tio
intra-frequency and inter-frequency neighboring cells, as shown in figure 5.
i c a
tif
Figure 5-1 Cell ID changes
e r
C
&
ing
i n
Tra
e i
aw
Hu
n
tio
a
fic
ti
r
Ce
Whether… & Judging Writing the specific information
i ntogbe changed. □Yes

in
Cell information needs
a
rcell information needs to be changed.
□No
T
ei
Neighboring □Yes
w
□No
a
Hu
Task 1 Data preparation by using the CME-provided ID/Name Adjustment Data

1. On the menu bar of the main window, choose System > Options (CME client mode) □Yes
or CME > Options (U2000 client mode). The setting function is started. □No
n
atio
i c
r tif
Ce
&
i ng
i n
Tra
modification.
e i
On the LTE network, this option applies only to radio network planning data and ID/name
aw □Yes
Hu
2. Select Cell Parameter Auto-Synchronization Policy from the navigation tree on the
left pane of the Options dialog box. Then, select Auto synchronize cell parameters □No
in the entire network on the right pane and click OK.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
3. On the menu bar of the planned data area, choose LTE Application > Export Data > □Yes
Export ID/Name Adjustment Data (CME client mode) or CME > LTE □No
Application > Export Data > Export ID/Name Adjustment Data (U2000 client
mode). The data export function is enabled.
n
atio
i c
In the displayed dialog box, select the NEs to be adjusted and then set a file path. Click □Yesif
4.
r t
Ce
Next to export the names and IDs of the eNodeB and cells to a file. □No
&
g
n in
r ai
i T
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a inexport succeeded, click Finish. □Yes
r
5. After the
iT
□No
e
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
6. Open the exported file, modify the corresponding MOs according to the planned data. □Yes
Then, save the modification and close the file. □No
n
io
7. On the menu bar of the planned data area, choose LTE Application > Import Data > □Yes
a t
Import ID/Name Adjustment Data (CME client mode) or CME > LTE □No
ic
Application > Import Data > Import ID/Name Adjustment Data (U2000 client
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u 8. In the displayed Import ID/Name Adjustment Data dialog box, select the file to be □Yes
imported, and then click Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
9. After the "Operation succeeded." message is displayed, click Finish. □Yes
The data in the file has been successfully imported into the CME. □No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
10. On the menu bar of the planned data area, choose CME > Advanced > Check Data
(U2000 client mode) or Advanced > Check Data (CME client mode) to start verifying
data.
n
atio
i c
r tif
Ce
&
ing
i n
ra
11. Select the NEs to be verified on the left pane of the Check Data dialog box and add
them to the right pane. Then, click OK to start verification. A maximum of 50
eNodeBs can be verified at a time.
i T
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
12. During data verification, modify the configuration data based on the verification
prompt until the verification succeeds.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2 □Yes
□No
NE maintenance mode to a customized expand status.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio □Yes
a
3 If any options of the X2-based Neighboring Cell Configuration Update Switch
c
it fi
parameter are selected, run the MOD GLOBALPROCSWITCH command to □No
deselect them all.
e r
C
&
n g
ini
a
Tr
ei
a w □Yes
u
4 If any options of the ANR algorithm switch parameter are selected, run the MOD
H
ENODEBALGOSWITCH command to deselect them all. □No
n
atio
□Yes
fi c
i
5 Deliver and activate the configuration on the eNodeB.
Area > Export Incremental Scripts (CME client mode) or CME > Planned Area > er
On the menu bar of the planned data area, choose Area Management > Planned t
□No
Export Incremental Scripts (U2000 client mode) to start the wizard of exporting C
scripts.
Select Launch script executor only in the wizard to activate exported scripts g
&
in
for data
n
r ai
i T
e
a w
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
Tr
ei
a w
H u6 Run the MOD GLOBALPROCSWITCH command to restore the setting of the
parameter modified in step 3.
□Yes
□No
7 Run the MOD ENODEBALGOSWITCH command to restore the setting of the □Yes
parameter modified in step 3. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
9
Hu □Yes
Click
n
at the upper left corner of the Maintenance Mode window. In the Set
io
a t
maintenance mode to NORMAL. Click OK to complete the setting.
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u

□No
6 Adding a Neighboring eNodeB n

a tio
6.1 Application Scenario i c
r tif
The capacity or coverage of the eNodeB cannot meet the requirement and therefore a neighboring eNodeB
is required.
Ce
6.2 Task Description &
ing
i n
A neighboring eNodeB is added. We need to configure the parameters related to neighboring EUTRAN
ra
cells and information about X2 self-setup. Figure 5 shows the topology changes after an X2 interface
between the local eNodeB and the neighboring eNodeB is added.
i T
e
aw
Figure 6-1 Topology changes after an X2 interface is added.
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei Reconfiguration modes of MOs for neighboring cells have been introduced in the chapter 4. This section will only
a w
H u introduce reconfiguration modes of MOs for X2.
The information of Neighboring eNodeB needs to be □Yes

collected, such as Frequency, BandWidth, PLMN, and □No
CELL ID.
n
tio
The information of Routing information of the X2 link. □Yes
□No
i c a
r tif
6.3.2 Data Preparation Ce
&
ng
n i
Step Description
i Fulfilled
Tra □Yes
i
1. On the menu bar, choose Advanced > Customize Summary Data File (CME client
e
w
a
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ni
i
r a
InTthe dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
ei Bulk Configuration > eNodeB > base station version, Click OK to enable the
2.
□No
a w function of customizing a summary data file.
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
w
. Select a scenario-based template: AdjustingaeNodeB
□Yes
u
3.
Click
Configurations >Adding a Neighboring eNodeB, H select MOs you want to change, □No
n
and then click OK.
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
4.
"Rule check is successful." message will be displayed.
□Yes
n
tio
5.
Click , specify a save path for the exported file, save the summary data file to a
□No
a
local PC. The CME automatically customizes the parameter names contained in the
i c
r tif
Ce
&
ing
i n
Tra
e i
u aw
H
6.
n summary data file.
o
□Yes
i
reconfigured from the planned data area to the □No
a t choose LTE Application > Export Data >
ic BaseData
On the menu bar of the planned data area,
f
Export Base Station Bulk Configuration (CME client mode) or CME > LTE
Application > Export Data > iExport
rt export function is enabled.
Station Bulk Configuration Data
e
(U2000 client mode). The data
C
&
i ng
a in
T r
ei
aw
Hu
7. Select the following options in sequence "Scenario > Adjust data by NE > □Yes
version >NEs need to be adjusted" in the pop-up dialog box. Click "Next". □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw □Yes
Hu
8. 1. Select Bulk configuration template.
□No
n
tio
ic a
f
rt i
Ce
&
n g
ini
a
Tr
ei
a w
H u
9. Open the local summary data file and reconfigure data in the summary data file based □Yes
10. Import the edited summary data file into the CME. □Yes
Import Base Station Bulk Configuration Data (CME client mode) or CME > LTE
Application > Import Data > Import Base Station Bulk Configuration Data
(U2000 client mode). The data import function is enabled.
n
atio
i c
r tif
Ce
& □Yes
ng
11. Select files to import and data types to adjust, select "I have read the note" and click
ni
Next. □No
rai
e iT
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
13.
e i
After the import is complete, click "Finish". Finish the data preparation by using □Yes
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
1 Select an eNodeB from the left pane of the planned data area. The object navigation □Yes
tree is displayed in the lower left part of the window. In the object navigation tree, □No
click the Search tab and type the MO information you want to configure. The CME
automatically finds the corresponding MOs.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
u aw
H
n
2 Select the required MO from the search result and edit the planned data in the right □Yes
pane. Click
it o
to save the configured data. □No
ic a
t i f
e r
C
&
i ng
a in
Tr
ei
a w
H u1 Prepare MML configuration scripts □Yes

□No
n
tio
i c a
r tif
Ce
&
ing
2
i n □Yes
ra
□No
T
i
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u

scripts.
n
a tio
i c
rtif
4 Select Launch script executor only in the wizard to activate exported scripts for data
Ce□Yes
□No
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ni
□Yes
i
a □No
Tr
ei
a w
H u
6 □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
e rt
C
&
Step Description
n g Fulfilled
i
1
from a in reported
r being during the reconfiguration.
T the following command: SET MNTMODE: MNTMODE=ExpandStatus1 in
□No
iRun
e MML input window.
a w
H u
n
atio
fi c
r
In the left pane, select a base station type: BTS3900 LTE. In the navigation tree, select □Yesti
e
4
C □No
the eNodeBs to be reconfigured, click to enter the script mode.
&
g
n in
r ai
i T
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in pane, copy and paste the MML commands to be executed in sequence to □Yes
Tr
5 In the right
ei
□No
area 1, Click to create a batch processing task.
a w
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i □Yes
aw
□No
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u8 Select the Select NE option. In the Confirm dialog box displayed, click OK. Select □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
9
w
Set the Maintenance Mode of the eNodeB to NORMAL.
a
□Yes
input window.
Hu
n
it o
ic a
t i f
e r
C
&
6.5 Engineering i ngVerification
a in
Step
T r
1
a w □No
Hu
7 Adding an S-GW Connection
The existing S-GW cannot meet the service requirements.
As the existing S-GW cannot meet the service requirements, an S-GW connection needs to be added.
Figure 8 shows the topology changes after an S-GW connection is added.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
7.3 Engineering Preparationic
a
t i f
7.3.1 Information Collection e r
C
Whether… & Judging Writing the specific information
n gis required for a new S-GW

i
A new device IP address □Yes
connection.
a in □No
T r the eNodeB and the new S-GW needs

ei
A route between □Yes
to be added. □No
a w
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
on
2. In the dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
i
at
Bulk Configuration > eNodeB > base station version, Click OK to enable the □No
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
3. □Yes
Click . Select a scenario-based template: Interface and Link Data
Reconfigurations > Adding an S-GW Connection(Endpoint)/Adding an S-GW □No
Connection(Link), select MOs you want to change, and then click OK.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
4.
tio □Yes
a
c
□No
ifi
"Rule check is successful." message will be displayed.
r t
Ce
&
n g
ini
a
Tr
5. □Yes
Click and select a save path to save the customized summary data file to the local
eiEach MO to be configured is an independent List sheet. The values of parameters on

PC. □No
a w
u
all sheets of the summary data file are blank.
H
n
a tio
i c
tif
r
e
C □Yes
6.
& □No
g
reconfigured from the planned data area to the summary data file.
i
On the menu bar of the planned data area, choose LTE Application > Exportn >Data >
Export Base Station Bulk Configuration Data (CME client mode) or CME
a inData LTE
Application > Export Data > Export Base Station Bulk Configuration
T r
ei
a w
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
Tr
ei
a w
H u
7. In the displayed dialog box, specify the scenario, adjustment mode, base station □Yes
version, and select the NE to be reconfigured. Then, click Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
□No
o n
i
a t
c
4. Click Next, the CME verifies the configuration data to be exported. After the
i f i
rt
export is complete, click Finish.
C e
&
i ng
a in
Tr
ei
a w
H u
9. Open the local summary data file and reconfigure data in the summary data file based □Yes
10. Import the edited summary data file into the CME. □Yes
n
atio
i c
r tif
Ce
&
ing
i n □Yes
ra
11. Select files to import and data types to adjust, check "I have read the note" and click
T
Next. □No
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
eiSelect base stations whose data you want to import and click Next. □Yes
aw
12.
□No
Hu
n
atio
i c
r tif
Ce
&
ng
i
n
thei "Operation
The CME verifies the imported data. If the verification is successful, a
13.
T r □Yes
i
succeeded." message will be displayed. Then, click Finish. □No
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
1. In the left pane of the planned data area, click an eNodeB you want to reconfigure. The □Yes
object navigation tree is displayed in the lower left area. □No
You can search MOs in the object navigation tree by clicking the Search tab and
typing the MO information you want to configure. The CME automatically finds the
corresponding MOs.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
2. Double-click the MO you want to configure and edit the planned data in the right pane. □Yes
Click to save the configured data. □No
n
a tio
i c
r tif
Step Description
CeFulfilled
& □Yes
ng
1 Prepare MML configuration scripts.
ni
□No
rai
e iT
aw
Hu
n
1
tio
c a
t ifi
r
Ce
&
n g
ini
a
Tr
ei
a w
H u
2 □Yes
□No
setting.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio □Yes
a
3 Deliver and activate the configuration on the eNodeB.
c
it fi
r
scripts.
C e
&live network.
Select Launch script executor only in the wizard to activate exported scripts for data
ng
to take effect on the
i
a in
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
a w
u
□Yes
□No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
5 □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
7.4.2 MML-based Operationsic a
t i f
Step Description
e r Fulfilled
C
&during the reconfiguration.
g command: SET MNTMODE: MNTMODE=Expand in MML

from being reported □No
i n
Run the following
in
input window.
a
T r
ei
aw
Hu2 From the main menu of the U2000 client, choose Trace and Maintenance > □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
uaw
H □Yes
n
3 In the left pane, select a base station type, for example, BTS3900 LTE. In the
it o □No
navigation tree, select the eNodeBs to be reconfigured, click to enter the script
a
mode.
f ic
r t i
C e
&
i ng
a in
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
4 In the right pane, copy and paste the MML commands to be executed in sequence to □Yes
Ce
□No
area 1. Click to create a batch processing task.
&
n g
ini
a
Tr
ei
a w
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra □Yes
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
7 Select the Select NE option. Select the eNodeBs on which the MML scripts are to be □Yes
executed, set Run Mode and Execution Result, and click Finish. In the displayed □No
Confirm dialog box, select the Continue to execute the MML script task option, and
then click Yes.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
o n
8
ti
Set the Maintenance Mode of the eNodeB to NORMAL. □Yes
c a
Run the following command: SET MNTMODE:
i
MNTMODE=NORMAL in MML □No
i f
input window.
e rt
C
&
i ng
a in
T r
e i
7.5w
Engineering Verification
u a
H Step Description Fulfilled

□No
8 Changing the VLAN Mode from VLAN Group to Single VLAN
 The VLAN mode is re-planned: changing from VLAN group to single VLAN. The VLAN groups
meet both of the following conditions:
− In each VLAN group, all service types are mapped to the same VLAN ID. That is, the service
types are not isolated using VLANs.
− Throughout the VLAN groups, each service type is assigned a unique differentiated services code
n
tio
point (DSCP) value, or service types with an identical DSCP value are assigned the same VLAN
priority.
i c a
r tif
The VLAN mode is re-planned: changing from VLAN group to single VLAN.
Ce
8.3 Engineering Preparation &
ing
8.3.1 Information Collection i n
Tra
Information Description
e i
aw
VLAN ID The VLAN ID of each VLAN.
Hu
DSCP The DSCP values of user data, signaling, high-priority OM data, low-priority OM data, and
priority other data, and the mapping priorities.
n
tio
ic a
i f
rt
Ce
8.3.2.1 Task 1 Data preparation by using the "batch reconfiguration" mode of the
CME
&
ng
n i
ai
Tr
ei
a w
H u
n
atio
i c
r tif
Ce
&
ing
2.
i n
In the dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
Tra
i
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
3. □Yes
Click . Select a scenario-based template: Security Networking Data
Reconfigurations > Changing the VLAN Mode from VLAN Group to Single □No
VLAN, select MOs you want to change, and then click OK.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
4. □Yes
"Rule check is successful." message will be displayed. □No
n
tio
ic a
i f
rt
Ce
& □Yes
g
5. Click and select a save path to save the customized summary data file to the local
PC.
i n □No
i nofto the
a
Each MO be configured is an independent List sheet. The values of parameters on
r
iT
all sheets summary data file are blank.
e
aw
Hu
6. Based on the parameter names in the summary data file, export the eNodeB data to be □Yes
n
atio
i c
r tif
Ce
&
ing
n
i station
7.
r a
In the displayed dialog box, specify the scenario, adjustment mode, base
version, and select the NE to be reconfigured. Then, click Next. T
□Yes
ei
□No
a w
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
i
e 1. Select Bulk configuration template.
aw
8. □Yes
Hu
□No
n
atio
i c
r tif
Ce
&
ng
i
n
idata file based
9. Open the local summary data file and reconfigure data in the summary
r a □Yes
on planned data.
i T □No
e
10. Import the edited summary data file into the CME.
On the menu bar of the planned data area, choose LTE a
w □Yes
Import Base Station Bulk Configuration Data (CME u Application > Import Data >
H Bulkclient mode) or CME > LTE
□No
Application > Import Data > Import Base Station Configuration Data
o
(U2000 client mode). The data import function n is enabled.
a ti
i f ic
e rt
C
&
i ng
a in
T r
11. iSelect files to import and data types to adjust, select "I have read the note" and click
e Next. □Yes
a w □No
H u
n
atio
i c
r tif
Ce
&
ing
i n
12. Select base stations whose data you want to import and click Next.
Tra □Yes
e i □No
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
13.
eiThe CME verifies the imported data. If the verification is successful, the "Operation □Yes
a w succeeded." message will be displayed. Then, click Finish. □No
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
corresponding MOs.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
n
a tio
i c
r tif
Step Description
CeFulfilled
& □Yes
ng
1 Prepare MML configuration scripts.
ni
□No
rai
e iT
aw
Hu
n
1
tio
c a
t ifi
r
Ce
&
n g
ini
a
Tr
ei
a w
H u
2 □Yes
□No
setting.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u

scripts.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ica
i f
4
e
Set the Maintenance Mode of rtthe eNodeB to NORMAL. □Yes
C Configuration > Settings > Maintenance Mode
On the U2000 Client, choose □No
&
i ng
a in
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
5
Hu □Yes
Click
n
io
a t
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Run the following command: SET MNTMODE: MNTMODE=Expand in MML
input window.
n
a tio
i c
rtif
2 From the main menu of the U2000 client, choose Trace and Maintenance >
Maintenance > MML Command (application style) or Maintenance > MML
Ce□Yes
□No
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w □Yes
u
H navigation tree, select the eNodeBs to be reconfigured, click

mode.
to enter the script □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
□No
&
n g
ini
a
Tr
ei
a w
H u5 In the New Task dialog box, enter a name in Task Name. Choose Other > MML □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra □Yes
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
7 Select the Select NE option. Select the eNodeBs on which the MML scripts are to be □Yes
then click Yes.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
8
a w
input window.
Hu
n
it o
ic a
t i f
e r
C
&
8.5 Engineering i ngVerification
a in
Step
T r

w
1
a □No
Hu
9 Changing the eNodeB ID
The previous eNodeB ID plan is inappropriate and a new plan is required.
n
The eNodeB ID of LTETEST010 needs to be changed from 10 to 100 as figure 6 shows.
Figure 9-1 eNodeB ID changes

atio
i c
r tif
eNodeB ID:10→100 Ce
&
ing
i n
Tra
e i
9.3 Engineering Preparation aw
Hu
n
Whether… it oJudging Writing the specific information
ic a
The eNodeB ID needs to be collected.
i f □Yes
rt □No
Ce
&
n g
i ni
a
Tr
ei
a w
H u

1. To ensure that the associated parameters of the external cells in the current data area □Yes
are consistent, choose System > Options (CME client mode) or CME > Options □No
started.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
modification.
n
2.
io
On the Cell Parameter Auto-Synchronization Policy tab page, select Auto
t
□Yes
a
synchronize cell parameters in the entire network and click OK. □No
i f ic
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
3. On the menu bar of the planned data area, choose CME > LTE Application > Export □Yes
Data > Export ID/Name Adjustment Data (U2000 client mode) or LTE □No
Application > Export Data > Export ID/Name Adjustment Data (CME client
mode). Export the eNodeB names and IDs, and cell and local cell IDs and names to a
file.
n
a tio
i c
rtif
4. A dialog box is displayed for you to select NEs. Add the NEs to be reconfigured from
the left pane to the right pane, and click Next.
e□Yes
C □No
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
5. □Yes
Click . Specify a save path for the exported file, and click Next. The CME starts
the export. After the export is complete, click Finish. □No
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
it o
6. Open the exported file, in the ID Modification Of eNodeB sheet of the file, modify □Yes
the eNodeB ID parameter value of the eNodeB to the target value. Then, save the □No
ica
modification and close the file.
t i f
r
Ce
&
n g
i ni
a
Tr
eiImport the changed IDs and names to CME.
a
7.w □Yes
H u On the menu bar of the planned data area, choose LTE Application > Import Data >
Import ID/Name Adjustment Data (CME client mode) or CME > LTE
□No
Application > Import Data > Import ID/Name Adjustment Data (U2000 client
mode). A dialog box is displayed for you to select files.
n
atio
i c
, select the file to be imported, and click Next. The CME starts the import. □Yesif
8. Click
r t
Ce
□No
&
g
n in
rai
i T
e
a w
H u
n
it o
ic a
t i f
e r
C
&
g
n in
i □Yes
ra
9. After the import is complete, click Finish.
iT
□No
e
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
9.4 Engineering Implementation aw
9.4.1 CME-based Operations Hu
n
Step Description
it o Fulfilled
ic a mode to expand status to prevent any alarm □Yes

f
1 Set the eNodeB engineering maintenance
t i
from being reported during the reconfiguration.
r Configuration
□No
Ce
On the U2000 Client, choose
(application style) or Maintenance
> Settings > Maintenance Mode
> Maintenance Mode (traditional style).
&
i ng
a in
T r
ei
aw
Hu
2 □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
t i f
r □Yes
Ce
3 Run MOD GLOBALPROCSWITCH to set Update eNB Configuration Via X2
Switch to OFF. □No
&
i ng
a in
T r
ei
aw
Hu
4 Run MOD ENODEBALGOSWITCH to set ANR algorithm switch to CLEAR □Yes

ALL. □No
n
a tio
i c
rtif
5 Deliver and activate the configuration on the eNodeB. e□Yes
C □No
&
On the menu bar of the planned data area, choose Area Management > Planned
ng
scripts.
n i
i
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
6 Select Launch script executor only in the wizard to activate exported scripts for data □Yes
Ce
&
n g
ini
a
Tr
ei
a w
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
i e
a w
7 Set the Maintenance Mode of the eNodeB to NORMAL
u
□Yes
□No
n
it o
ic a
t i f
e r
C
&
n g
i
n at theMode
□Yes
i
8
Click upper left corner of the Maintenance Mode window. In the Set
r a mode todialog
Maintenance box, select the eNodeBs to be configured. Set NE □No
T dialog box, click Yes.
iConfirm
maintenance NORMAL. Click OK to complete the setting. In the displayed
e
aw
Hu
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
o n
9.5 Engineering Verification t i
ic a
Step Description
t i f Fulfilled
r
Check whether MOs haveebeen modified.
C
1 □Yes
&
□No
i ng
10 Changing a in Cabinet and Subrack No.
T r
ei
w
a The cabinet and subrack numbers of an eNodeB were inappropriately planned and require replanning.
H u
Change the RRU subrack number of the eNodeB "FDD eNodeB102" to 66.
Information Description
Cabinet number
Subrack number within the cabinet
n
tio
RRU subrack number
i c a
10.3.2 Data Preparation tif
r
Ce
&
Step Description
n g Fulfilled
i
1.
a
On the menu bar of the planned data area, choose CME > LTE Application in > Export □Yes
Data > Export Cabinet and Subrack No. Adjustment Data (U2000
T rNo. Adjustment □No
client mode) or
Data (CME client mode) to enable the data export function. i

LTE Application > Export Data > Export Cabinet and Subrack
e
a w
H u
n
it o
ic a
t i f
e r
In the displayed dialogC
box, specify the export scenario, export mode, related eNodeB, □Yes
&
2.
g
and export path. Then, click Next to export the cabinet and subrack numbers of the □No
in
eNodeB from the CME to a file.
n
r ai
i T
e
a w
H u
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
3. After the export is complete, click Finish.
aw □Yes
Hu □No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
4. Open the exported file. In the Base Station CN SRN Adjustment sheet of the file, □Yes
modify the cabinet and subrack numbers of the eNodeB to the target values. Then, save □No
the modification and close the file.
5. On the menu bar of the planned data area, choose CME > LTE Application > Import □Yes
Data > Import Cabinet and Subrack No. Adjustment Data (U2000 client mode) or □No
LTE Application > Import Data > Import Cabinet and Subrack No. Adjustment
Data (CME client mode) to enable the data import function.
n
atio
i c
r tif
Ce
&
ing
n
idialog box,
ra □Yes
T
6. In the displayed Import Cabinet and Subrack No. Adjustment Data
i
specify the save path, select the NE, and click Next. □No
e
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
7. Observe the adjustment progress. After the adjustment is complete, the "Operation □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
o n
10.4 Engineering Implementation ti
ic a
Step Description
t i f Fulfilled
e rmaintenance
1
C the reconfiguration.
Set the eNodeB engineering mode to expand status to prevent any alarm □Yes
& choose Configuration > Settings > Maintenance Mode

from being reported during □No
ng or Maintenance > Maintenance Mode (traditional style).

On the U2000 Client,
i
(application style)
a in
T r
ei
a w
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu □Yes
n
2
io
□No
t
a
ic
setting.
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u

scripts.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
e rt
C
(application style)&
g
or Maintenance > Maintenance Mode (traditional style).
n in
r ai
eiT
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
5
Hu □Yes
Click
n
io
a t
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u

□No
11 Replacing the Main Control Board n

atio
11.1 Application Scenario i c
r tif
e
When the current main control board cannot meet service requirements, it needs to be replaced.
C
&
ing
Initially, the eNodeB is configured with LMPT board. With the increase of traffic, we need to replace the
i n
LMPT board with UMPT board. Figure 7 shows the topology changes when an LMPT using optical port 0
ra
is replaced with a UMPT using optical port 1.
i T
e
aw
Hu
n
tio
ic a
i f
rt
Ce
&
g Implementation
11.3 Engineering
n in
r ai
i T
e
Thew
u a MPT information needs to be collected. □Yes
H
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
i e
w
a Default > NodeB/eNodeB
2.
Bulk Configuration > eNodeB > base station version,
H u
In the dialog box, select the following options in sequence
Click OK to enable the
□Yes
□No
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
3. □Yes
Click . Select a scenario-based template: Device Data Reconfiguration >
Replacing the Main Control Board When No SeGW Is Deployed, select MOs you □No
want to change, and then click OK.
n
atio
i c
r tif
Ce
&
ing
i n
T ra
4.
local PC. The CME automatically customizes the parameter e
Click i data file to a
, specify a save path for the exported file, save the summary
□Yes
w names contained in the □No

a
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r on the parameter names in the summary data file, export the eNodeB data to be
5.
ireconfigured from the planned data area to the summary data file.
Based
e On the menu bar of the planned data area, choose LTE Application > Export Data >
□Yes
□No
aw
Hu
n
a tio
□Yes
fi c
i
6. Select the following options in sequence "Scenario > Adjust data by NE >
version >NEs need to be adjusted" in the pop-up dialog box. Click "Next".
r
□Not
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u

□No
n
tio
i c a
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio □Yes
a
ic
i f
r □Yes
Ce Configuration

(U2000 client g
n
ni
i
T ra
ei
aw
Hu
Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
□No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
12. After the import is complete, click "Finish". Finish the data preparation by using □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
11.3.3 Commissioning Preparation
on
1.
a ti
Upload the software package of a target version that you have obtained from Huawei □Yes
ic
engineers and decompressed the software package on a local PC to the U2000 server. □No
tif
On the U2000 client, choose SON > Self Planning > Auto Deployment (application
e r
style) or SON > Auto Deployment (traditional style). The Auto Deployment window
is displayed.
C
&
n g
ini
a
Tr
ei
a w
H u
2. Select tab page Prepare File & Data > Software & Cold Patch, Click Transfer, and □Yes
choose From OSS Client to OSS Server from the shortcut menu. The NE File □No
Transfer dialog box is displayed.
n
atio
i c
r tif
Ce
&
ing
i n □Yes
ra
3. Select the NE type and file type from the NE Type and File Type drop-down lists,
T
respectively. Click in the Source Path area. The Select Folder dialog □No
e i
box is displayed. Select the folder that contains the software package to be uploaded,
aw
and click OK. The NE File Transfer dialog box is displayed.
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
4. Click OK. The NE File Transfer dialog box is closed, and the upload starts. Wait for □Yes
the upload over. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
5. Uploading a Commissioning License
e i □Yes
□No
w
On the U2000 client, choose SON > Self Planning > Auto Deployment (application
a
Hu
style) or SON > Auto Deployment (traditional style). The Auto Deployment window
is displayed.
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
6. Click the Prepare File & Data tab and then the License tab. Click Transfer, and □Yes
choose From OSS Client to OSS Server from the shortcut menu. The Upload □No
License dialog box is displayed.
n
atio
i c
r tif
Ce
&
ing
i n
7.
Click
Tra
in the Source Path area. The Select Folder dialog box is displayed.
□Yes
e i
Select the file to be uploaded, and click Open. The Upload License dialog box is □No
aw
displayed. Click OK. The Upload License dialog box is closed, and the upload starts.
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
8. The local engineer reports the site position and ESN of each base station to the remote □Yes
engineer, helps remote engineers use the ESN to bind the base station to the U2000. □No
n
atio
i c
r tif
Ce
11.4 Engineering Implementation &
ng i
n
a i any alarm
1
r
Set the eNodeB engineering maintenance mode to expand status to prevent
T
□Yes
i
(application style) or Maintenance > Maintenance Modew

e
u a (traditional style).
H
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
2 □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
(Local operation) Power offrthe
i f
t eNodeB and remove the main control board to be
e
3
replaced.
C
4
&
(Local operation) Install the new main control board and power on the eNodeB.
n g from the main topology.

5
i
Remove the eNodeB
From thenmain menu of the U2000, choose Topology > Main Topology(application
oritraditional style).
style a
r
eiT
aw
Hu
6 Right-click the eNodeB to be removed and choose Delete. In the displayed Confirm
dialog box, click Yes. In the displayed Deletion Result dialog box, verify that Result
is Succeeded, and then click Close.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
7 Deliver and activate the configuration on the eNodeB. i
e Data (CME client
□Yes
w
a Data
On the menu bar, choose Advanced > Export Auto Deployment □No
u
mode) or CME > Advanced > Export Auto Deployment (U2000 client mode).
H
A dialog box is displayed for you to export auto-deployment data.
n
it o
ic a
t i f
e r
C
&
i ng
a in
Tr
eiSelect Site creation/expansion scenario, and click Next. □Yes
w
8
u a □No
H
n
atio
i c
r tif
Ce
&
ing
i n
T ra
Select the base stations whose auto-deployment data you want ito export, and click
e
9
Next.
a w
H u
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu10 Click . Select a save path for the exported file and a method for processing data,
and click Next.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
ie
w
a the software version is
11
u
View data in the base station deployment list, ensure that
H to verify data correctness and
correct, input new ESN, and click Next. The CME starts
exports the data.
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
12 If the export is successful in U2000, select Open the Auto Deployment window, click
Finish. The CME automatically switches to the auto-deployment window and creates a
commissioning task.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
ei
w
a commissioning tasks. Click
13
u
Select one or more commission tasks and right-click these
H
Start. The Task Parameter Settings window is displayed.
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
i
e Set Step Parameters and Extended Parameters as planned. Click OK.
aw
14
Hu
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
15
e i
After the project quality check of an NE is complete, the commissioning tasks enter the
aw
Waiting for Confirmation state. Manually confirm that the commissioning is
complete.
Hu
Right-click the tasks and choose Confirm Completion from the shortcut menu to
confirm the completion.
n
tio
ic a
i f
rt
Ce
&
n g
ni
16
r ai
T the U2000 Client, choose Configuration > Settings > Maintenance Mode
ei(application style) or Maintenance > Maintenance Mode (traditional style).
On □No
a w
H u
17 □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
c a
ifi
r t
Step Description Ce Fulfilled
& □Yes
ng
1 Check whether MOs have been modified.
ni
□No
a i
Tr
ei
12 Transmission Capacity Expansion from One UMPT Board to
aw UMPT Boards (FDD/NB-IoT)
Two
Hu12.1 Application Scenario
 You can expand transmission capacity from one UMPT board to two UMPT boards if the volume of
traffic that flows over the eNodeB configured with a single UMPT board cannot meet service
requirements.
 Currently, the model of the UMPT board used for LTE is UMPTb. The total uplink and downlink
traffic volume supported by UMPTb+UMPTb can reach 4 Gbit/s.
After the UMPT board is added, two UMPT boards must be connected to different ports of transmission
equipment to ensure transmission traffic. Assume that the two UMPT boards are connected to different
ports of the same switch and router. Figure 8 shows the topology changes before and after the
reconfiguration.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
a
fic
ti
r
Ce
Information & Description
Device IP address ofin

g
in
the new UMPT board Including the device IP address, subnet mask, and
a
number of the physical port in use.
T r the route from the new UMPT

board toithe S-GW
Information about Including the local device IP address and the next hop
e IP address.
a w
HuID of the end point group to which the new local end
VLAN ID for the new UMPT board
on the user plane is added

n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
on
2 In the dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
i
at
i f ic
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
3 □Yes
Transmission Capacity Expansion from One UMPT Board to Two UMPT □No
Boards, select MOs you want to change, and then click OK.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
o n
i
t the customized summary data file to the local □Yes
a
4 Click and select a save path to save
ic
Each MO to be configured is anifindependent List sheet. The values of parameters on
PC. □No
e
all sheets of the summary datart file are blank.
C
&
i ng
a in
Tr
ei
a w
H u
5 Based on the parameter names in the summary data file, export the eNodeB data to be □Yes
n
a tio
i c
rtif
6 In the displayed dialog box, specify the scenario, adjustment mode, base station e
C □No
□Yes
&
version, and select the NE to be reconfigured. Then, click Next.
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
7 1. Select Bulk configuration template. □Yes

□No
n
tio
i c a
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
o n
ti
8
ic a
Open the local summary data file and reconfigure data in the summary data file based □Yes
i f
Import the edited summary r t file into the CME.
9
On the menu bar of theC
e data
planned data area, choose LTE Application > Import Data >
□Yes
□No
&
ngmode). The data import function is enabled.

i
(U2000 client
a in
T r
ei
aw
Hu
10 Select files to import and data types to adjust, select "I have read the note" and click □Yes
Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
11 Select base stations whose data you want to import and click Next. □Yes
Hu
□No
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
12 The CME verifies the imported data. If the verification is successful, the "Operation □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Task 2 Data preparation by using the GUI mode of CME Hu
Step Description
o n Fulfilled
i
t click an eNodeB you want to reconfigure. The
1.
object navigation tree is displayedic
a
In the left pane of the planned data area, □Yes
i f in the lower left area.

t wantnavigation
□No
e r
You can search MOs in the object tree by clicking the Search tab and
corresponding MOs. C
typing the MO information you to configure. The CME automatically finds the
&
i ng
a in
Tr
ei
a w
H u
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
1 Prepare MML configuration scripts. □Yes

□No
12.4 Engineering Implementation n

12.4.1 Local Operations atio
i c
1. Insert the new UMPT board into the subrack.
r tif
2. Connect the transmission port of the new UMPT board to the gateway.
Ce
12.4.2 Remote Operations &
12.4.3 CME-based Operations ing
i n
Step Description
T ra Fulfilled
1.
ei to prevent any alarm
Set the eNodeB engineering maintenance mode to expand status □Yes
w
On the U2000 Client, choose Configuration > Settingsa> Maintenance Mode
□No
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
T r
e i
aw
Hu
2. □Yes
□No
setting.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
3. Deliver and activate the configuration on the eNodeB. □Yes

scripts.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce Configuration > Settings > Maintenance Mode
4. Set the Maintenance Mode of the eNodeB to NORMAL. □Yes
□No
(application style)&
On the U2000 Client, choose
ng
or Maintenance > Maintenance Mode (traditional style).
i
a in
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
u
5.
Click H
□Yes
maintenance mode to NORMAL. Clicko

n
it OK to complete the setting.
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
input window.
n
a tio
i c
rtif
2 From the main menu of the U2000 client, choose Trace and Maintenance >
Maintenance > MML Command (application style) or Maintenance > MML
Ce□Yes
□No
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w □Yes
u
H navigation tree, select the eNodeBs to be reconfigured, click

mode.
to enter the script □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
□No
&
n g
ini
a
Tr
ei
a w
H u5 In the New Task dialog box, enter a name in Task Name. Choose Other > MML □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra □Yes
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u7 Select the Select NE option. Select the eNodeBs on which the MML scripts are to be □Yes
then click Yes.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
8
a w
input window. Hu
n
it o
ic a
t i f
e r
C
&
12.5 Engineering i ng Verification
a in
Step
T r

w
1
a □No
Hu
13 Replacing BBPs
 The baseband processing unit (BBP) in use is faulty and must be replaced with one of other BBP
types.
 The BBP in use does not meet service requirements and must be upgraded. For example, upgrade the
LBBPd to the UBBP or upgrade the LBBPc to the LBBPd or UBBP.
n
tio
i c a
tif
Replacing BBPs Reconfiguration Schemes
Replacing an Modify Delta shift in the PUCCHCfg MO:

e r
LBBPc with an ● If this parameter is set to 2, change the value to 1. C
&
LBBPd
● If this parameter is set to 1 or 3, no change is required.
n g
Replacing an
i
inConfiguration Index to the
Modify Indication of PRACH Configuration Index in the RACHCfg MO:
a
LBBPd with an
● If this parameter is set to CFG(Configure), set PRACH
LBBPc
T r
target value, ensuring that the values of PRACH Configuration Index for all cells in
ei no change is required.
the same eNodeB are unique.
aw
● If this parameter is set to NOT_CFG(Not configure),
Modify Board Type in the BBP MO tou

Standard to LTE_FDD(LTE FDD)H
Replacing an UBBP(UBBP) and modify Base Band Work
LBBPc with a or LTE_TDD(LTE TDD).
UBBP
o n MO:
Modify Delta shift in the PUCCHCfg
● If this parameter is setttoi 2, change the value to 1.
a to 1 or 3, no change is required.
● If this parameter iscset
i
Modify BoardrType tif in the BBP MO to UBBP(UBBP) and modify Base Band Work
Standard toe
Replacing an
LBBPd with a
C LTE_FDD(LTE FDD) or LTE_TDD(LTE TDD).
& Type in the BBP MO to LBBP(LBBP) and set Work Mode to
UBBP
Replacing a UBBP
g
nFDD(Frequency
Set Board
with an LBBPd
n i Division Duplex).
r ai
i T
e
a w
H u13.3.1 Information Collection
Information Information
The delta shift of cells of the replaced BBP Modify the delta shift of the new BBP based on the
information.
The PRACH configuration index of cells of the Constraints on the setting of PRACH configuration indexes
replaced BBP are different for the LBBPd and the LBBPc.
The number of the slot where the baseband -
Information Information
processing board to be replaced is located
The maximum number of cells that can be Check whether the new BBP supports the establishment of
established on the replaced BBP cells of such a quantity.

n
a tio
i c
tif
e r
□Yes
C □No
1 On the menu bar, choose Advanced > Customize Summary Data File (CME client
mode) or CME > Advanced > Customize Summary Data File (U2000 client mode).
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
2 In the dialog box, select the following options in sequence Default > NodeB/eNodeB □Yes
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
it o
3 □Yes
ica
Replacing Baseband Processing Units, select MOs you want to change, and then □No
i f
click OK.
r t
Ce
&
n g
i ni
a
Tr
ei
a w
H u
4 Click and select a save path to save the customized summary data file to the local □Yes
PC. □No
Each MO to be configured is an independent List sheet. The values of parameters on
all sheets of the summary data file are blank.
n
a tio
i c
r tif
Ce
&
ing
i n
5
Tra
Based on the parameter names in the summary data file, export the eNodeB data to be □Yes
e
reconfigured from the planned data area to the summary data file.i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
6 In the displayed dialog box, specify the scenario, adjustment mode, base station □Yes
version, and select the NE to be reconfigured. Then, click Next. □No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
7 1. Select Bulk configuration template. □Yes
Hu
□No
n
data from the CME based on the MOs in this file. In Export path, specify a save
i o
path for the file that contains the exported data.
t
ic a
Click Next, the CME verifies the configuration data to be exported. After the
i f
export is complete, click Finish.
e rt
C
&
i ng
a in
Tr
ei
a w
H u
8 Open the local summary data file and reconfigure data in the summary data file based □Yes
9 Import the edited summary data file into the CME. □Yes
n
atio
i c
r tif
Ce
&
ing
i n
10
Tra
On the Import Base Station Bulk Configuration Data page, select a path for saving □Yes
e i
the configuration file and select Adjust Data by NE. Select I have read the note and □No
w
click Next.
a
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u11 Select base stations whose data you want to import and click Next. □Yes
□No
n
atio
i c
r tif
Ce
&
ing
i n
12
Tra
The CME verifies the imported data. If the verification is successful, the "Operation □Yes
succeeded." message will be displayed. Then, click Finish.
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
u
H Task 2 Data preparation by using the GUI mode of CME
corresponding MOs.
n
a tio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u
1 Prepare MML configuration scripts. □Yes

□No
13.4 Engineering Implementation n

13.4.1 CME-based Operations atio
fi c
Step Description
r ti
Fulfilled
1. Set the eNodeB engineering maintenance mode to expand status to prevent any alarm Ce
□Yes
& □No
ng
i
a in
T r
ei
a w
Hu
n
it o
ic a
t i f
e r
C
&
i ng
a in
Tr
ei
a w
H u
2. □Yes
□No
setting.
n
atio
i c
r tif
Ce
&
i ng
i n
Tra
e i
aw
Hu
o n
i
t Type set to IMMEDIATE(Immediate) to
3.
ic a
Run the BLK BRD command with Block □Yes
block a BBP.
i f □No
e rt
C
&
i ng
a in
Runrthe DEA CELL command to deactivate the cells bound to the BBP by
T □Yes
ei
4.
configuring the eUCellSectorEqm or EuSectorEqmGroup MO. □No
a w
H u
5. (Local operation) Replace the BBP. □Yes
□No
Notice
In any of the following situations, ensure that the time interval between board removal and
installations is greater than 5 minutes so that the cell can be activated.
 A UBBP is replaced with an LBBP
 An LBBP is replaced with a UBBP
6. Deliver and activate the configuration on the eNodeB. □Yes

scripts.
n
tio
i c a
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
7. Ce
Run the UBL BRD command to unblock the BBP. □Yes
& □No
n g
ini
a
Tr
ei
a w
H u 8. Run the ACT CELL command to activate the cells that are deactivated owing to BBP
replacement.
□Yes
□No
9. Set the Maintenance Mode of the eNodeB to NORMAL. □Yes

n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
u
10. H □Yes
n to complete
□No
o
Maintenance Mode dialog box, select the eNodeBs to be configured. Set NE
maintenance mode to NORMAL. Click
ti OK the setting.
ic a
t i f
e r
C
&
i ng
a in
T r
ei
aw
Hu
1. Set the eNodeB engineering maintenance mode to expand status to prevent any alarm □Yes
input window.
n
a tio
i c
rtif
2. Run the BLK BRD command with Block Type set to IMMEDIATE(Immediate) to
block a BBP.
Ce□Yes
□No
&
i ng
i n
Tra
e i
aw □Yes
Hu
3. Run the DEA CELL command to deactivate the cells bound to the BBP by
configuring the eUCellSectorEqm or EuSectorEqmGroup MO. □No
n
tio
a
ic
(Local operation) Replace thetBBP. i f
4.
e r □Yes
C □No
&
Notice
In any of the following situations, ensure that the time interval between board removal and
A UBBP n
g
installations is greater than 5 minutes so that the cell can be activated.
i
in is replaced with a UBBP
 is replaced with an LBBP
a
Tr the main menu of the U2000 client, choose Trace and Maintenance >
 An LBBP
□Yes
eiMaintenance > MML Command (application style) or Maintenance > MML
5. From
□No
a w Command (traditional style).
H u
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
uaw
H □Yes
n
6. In the left pane, select a base station type, for example, BTS3900 LTE. In the
it o □No
navigation tree, select the eNodeBs to be reconfigured, click to enter the script
a
mode.
f ic
r t i
C e
&
i ng
a in
T r
ei
aw
Hu
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
7. In the right pane, copy and paste the MML commands to be executed in sequence to □Yes
Ce
□No
&
n g
ini
a
Tr
ei
a w
H u 8. In the New Task dialog box, enter a name in Task Name. Choose Other > MML □Yes
n
atio
i c
r tif
Ce
&
ing
i n
9. Set the time or period to execute the task and click Next.
Tra □Yes
e i □No
a w
Hu
n
tio
ic a
i f
rt
Ce
&
n g
ini
a
Tr
ei
a w
H u 10. Select the Select NE option. Select the eNodeBs on which the MML scripts are to be □Yes
then click Yes.
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
11. Run the UBL BRD command to unblock the BBP. □Yes
Hu
□No
n
tio
ic a
i f
rt
Ce
12. Run the ACT CELL command to activate the cells that are deactivated owing to BBP □Yes
replacement. □No
&
n g
ni
r ai
T the Maintenance Mode of the eNodeB to NORMAL.
eiRun the following command: SET MNTMODE: MNTMODE=NORMAL in MML
13. Set □Yes
□No
aw input window.
Hu

□No
n
atio
i c
r tif
Ce
&
ing
i n
Tra
e i
aw
Hu
n
tio
ic a
i f
rt
Ce
&
n g
i ni
a
Tr
ei
a w
H u
Recommendations
 Huawei Learning Website
 http://learning.huawei.com/en
 Huawei e-Learning
 http://support.huawei.com/learning/NavigationAction!createNavi?navId=MW
n
000001_term1000025144&lang=en it o
i c a
 Huawei Certification if
r t
Ce
http://support.huawei.com/learning/NavigationAction!createNavi?navId=_31
&

&lang=en g
n in
 Find Training
rai
i T

e
http://support.huawei.com/learning/NavigationAction!createNavi?navId=_trai
a w
ningsearch&lang=en
Hu
More Information n
it o
ic a
t i f
 Huawei learning APP e r
C
&
i ng
a in
T r
ei
a w
Hu
版权所有© 2018 华为技术有限公司

HCIA-LTE Lab Guide V1.0

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

HCIA-LTE Lab Guide V1.0

Hochgeladen von

Copyright:

Verfügbare Formate

Recommendations

 Huawei Learning Website

版权所有© 2018 华为技术有限公司

1 eNodeB Data Configuration Preparation ..............................................................................1-4

3.1.2 Task: Configuring a Service and OM IPn

& S1 Interface Data in Endpoint Mode (Simplified Configuration) ........................ 3-23

ng OM Channel Data ................................................................................................ 3-25

a in Data Configuration ......................................................................................4-25

5 eNodeB Script Verification ....................................................................................................5-37

6 RAN Sharing Data Configuration ........................................................................................6-40

About This Chapter

The following table lists the contents of this chapter.

Table 2-1 Configuring eNodeB basic data

Step Description Fulfilled

7 Set special status of the NE. □Yes

2.3.1 Task:raConfiguring Time Data

H uStep Description Fulfilled

3 Set the clock synchronization mode of a BS. Fulfilled

Table 3-2 Configure a service and OM IP

Step Description Fulfilled

Table 3-4 Configuring VLAN

Step Description Fulfilled

1 Add an entry of mapping from a next-hop IP address to single VLAN. □Yes

2 Configure the control plane link: Add an SCTP link. □Yes

Table 3-6 Configuring S1 interface data in endpoint mode

Step Description Fulfilled

1 Configure the S1-C: Add an SCTP parameter template. □Yes

4 Configure the S1-U: Add a user-plane host. □Yes

Table 3-8 Configuring OM channel data

Step Description Fulfilled

1 Add a remote maintenance channel. □Yes

4.1 Sector Data Configuration

Table 4-1 Configuring a sector

Step Description Fulfilled

1 Add a sector. □Yes

4.2.1 Task: Configuring a Cell

Table 4-2 Configuring a cell

4.3.1 Task: Adding an Intra-Frequency Neighboring Cell

1 Add an external E-UTRAN cell. □Yes

1 Add an external E-UTRAN cell. □Yes

H horizontal and vertical planes, significantly enhancing system coverage.

n g with the CPRI interface type set to XCI_QSFP. □Yes

5 Activate a weight database file for a beamforming antenna. □Yes

6 Add an antenna device. □Yes

nghttps://10.77.199.42/10.20.9.94/ in Microsoft Windows 7 or Windows 8 operating system,

Figure 5-2 Executing MML scripts in batches

Display dynamic parameters of cells

a in 0 6 UMPT GBTS 100.019.10.000 2576 00.010.01.003

Display S1 Interface Information

DSP IP Path Result

& Transport Resource Type = High Quality

i Service Type = NULL

e Sharing Data Configuration

The following table lists the contents of this chapter.

6.1 RAN Sharing with Common Carriers Data Configuration

Figure 6-1 RAN sharing with common carriers &

Step e Description Fulfilled

7 Set the traffic sharing type. □Yes

8 Set the portion of traffic of different operators. □Yes

1 Laboratory Networking Introduction ....................................................................................1-1

2 Customizing the Summary Data File .....................................................................................2-2

4.2.2 Checking eNodeBC

& parameters (part 4) .................................................................................................. 3-20

T ra LTE cell basic parameters (part 6) .................................................................................................. 3-20

User Plane Peer ID Peer IP Address Peer IP Address Mask

Flag of Multi-RRU Mode of Cell Cell Radius Cell Template

VRF Index IP Address *Mask User Label Borrow IFIP

VRF Next Hop Mask VLAN VLAN ID Set VLAN VLAN