5G RAN Reconfiguration Guide (V100R016C10 - 04) (PDF) - en

5G RAN
V100R016C10
Reconfiguration Guide
Issue 04
Date 2021-02-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. i

5G RAN
Reconfiguration Guide Contents
Contents
1 5G RAN Reconfiguration Guide............................................................................................1

1.1 Changes in 5G RAN Reconfiguration Guide...................................................................................................................2
1.2 Introduction to 5G RAN Reconfiguration........................................................................................................................4
1.2.1 Definition of 5G RAN Reconfiguration......................................................................................................................... 4
1.2.2 General Prerequisites.......................................................................................................................................................... 6
1.2.3 Reconfiguration Tools......................................................................................................................................................... 6
1.3 General Operation Guide................................................................................................................................................... 14
1.3.1 MAE-Deployment Operation Guide............................................................................................................................ 14
1.3.2 Running MML Commands on the LMT..................................................................................................................... 17
1.3.3 Running MML Commands on the MAE-Access...................................................................................................... 17
1.4 Reconfiguration Scenario Overview............................................................................................................................... 21
1.5 Cell Data Reconfigurations................................................................................................................................................ 26
1.5.1 Adding an NR FDD Cell (Common Scenarios)........................................................................................................ 26
1.5.1.1 Scheme Overview.......................................................................................................................................................... 27
1.5.1.2 Engineering Preparation.............................................................................................................................................. 29
1.5.1.3 Engineering Implementation..................................................................................................................................... 33
1.5.1.4 Engineering Verification.............................................................................................................................................. 35
1.5.1.5 Engineering Rollback.................................................................................................................................................... 36
1.5.2 Adding an NR TDD Cell (Common Scenarios)........................................................................................................ 37
1.5.2.1 Scheme Overview.......................................................................................................................................................... 37
1.5.3 Changing the NR Cell Bandwidth................................................................................................................................ 49
1.5.3.1 Scheme Overview.......................................................................................................................................................... 49
1.5.4 Changing the TX/RX Mode of an NR Cell................................................................................................................. 60
1.5.4.1 Scheme Overview.......................................................................................................................................................... 60
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. ii

5G RAN

1.5.5 Changing the Coverage Radius of an NR Cell......................................................................................................... 71
1.5.5.1 Scheme Overview.......................................................................................................................................................... 71
1.5.6 Changing the NR Cell NR-ARFCNs.............................................................................................................................. 76
1.5.6.1 Scheme Overview.......................................................................................................................................................... 76
1.5.7 Changing the NR DU Cell PCI....................................................................................................................................... 83
1.5.7.1 Scheme Overview.......................................................................................................................................................... 83
1.5.8 Changing the Cell ID........................................................................................................................................................ 88
1.5.8.1 Scheme Overview.......................................................................................................................................................... 88
1.5.9 Changing the NR Cell ID................................................................................................................................................. 94
1.5.9.1 Scheme Overview.......................................................................................................................................................... 94
1.5.10 Changing the Cell Name.............................................................................................................................................. 99
1.5.10.1 Scheme Overview........................................................................................................................................................ 99
1.5.10.2 Engineering Preparation............................................................................................................................................ 99
1.5.10.3 Engineering Implementation................................................................................................................................ 101
1.5.10.4 Engineering Verification..........................................................................................................................................102
1.5.10.5 Engineering Rollback............................................................................................................................................... 103
1.5.11 Changing the NR DU Cell Name............................................................................................................................. 103
1.5.11.1 Scheme Overview......................................................................................................................................................103
1.5.11.2 Engineering Preparation......................................................................................................................................... 104
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. iii

5G RAN

1.5.12 Changing the TAC......................................................................................................................................................... 108
1.5.12.1 Scheme Overview......................................................................................................................................................108
1.5.13 Changing the Neighboring Cell Parameters........................................................................................................112
1.5.13.1 Scheme Overview......................................................................................................................................................112
1.5.14 Changing the Intra-Frequency A3 Offset............................................................................................................. 116
1.5.14.1 Scheme Overview......................................................................................................................................................117
1.5.15 Changing the NR Cell Power.................................................................................................................................... 121
1.5.15.1 Scheme Overview......................................................................................................................................................121
1.5.16 Changing the Uplink-Downlink Slot Assignment and Slot Structure of an NR TDD Cell................... 127
1.5.16.1 Scheme Overview......................................................................................................................................................127
1.5.17 Adjusting the Association Relationships Between NR Cells and RF Modules......................................... 131
1.5.17.1 Scheme Overview......................................................................................................................................................132
1.6 Base Station Data Reconfigurations............................................................................................................................ 138
1.6.1 Adding a Neighboring Base Station for a gNodeB (NSA Networking)........................................................138
1.6.1.1 Scheme Overview........................................................................................................................................................ 138
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. iv

5G RAN

1.6.1.3 Engineering Implementation................................................................................................................................... 146
1.6.1.4 Engineering Verification............................................................................................................................................ 147
1.6.1.5 Engineering Rollback.................................................................................................................................................. 148
1.6.2 Changing the Base Station Name............................................................................................................................. 149
1.6.2.1 Scheme Overview........................................................................................................................................................ 149
1.6.3 Changing the gNodeB ID............................................................................................................................................. 152
1.6.3.1 Scheme Overview........................................................................................................................................................ 152
1.7 Device Data Reconfigurations........................................................................................................................................ 157
1.7.1 Replacing the Main Control Board When No SeGW Is Deployed.................................................................. 157
1.7.1.1 Scheme Overview........................................................................................................................................................ 157
1.7.2 Replacing the Main Control Board When an SeGW Is Deployed................................................................... 167
1.7.2.1 Scheme Overview........................................................................................................................................................ 167
1.7.3 Replacing BBPs................................................................................................................................................................. 177
1.7.3.1 Scheme Overview........................................................................................................................................................ 177
1.7.4 Changing CPRI Ports for RF Modules....................................................................................................................... 184
1.7.4.1 Scheme Overview........................................................................................................................................................ 184
1.7.5 Adding or Deleting an RF Module............................................................................................................................ 194
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. v

5G RAN
1.7.5.1 Scheme Overview........................................................................................................................................................ 194

1.8 Interface and Link Data Reconfigurations................................................................................................................. 217
1.8.1 Replacing a MAE-Access............................................................................................................................................... 217
1.8.1.1 Scheme Overview........................................................................................................................................................ 218
1.8.2 Changing the Local Maintenance IP Address........................................................................................................ 229
1.8.2.1 Scheme Overview........................................................................................................................................................ 229
1.8.3 Changing the Device IP Address (IPv4 Old Model and IPv6 New Model).................................................. 234
1.8.3.1 Scheme Overview........................................................................................................................................................ 234
1.8.4 Changing the IPv4 Address (IPv4 New Model).................................................................................................... 248
1.8.4.1 Scheme Overview........................................................................................................................................................ 248
1.8.5 Changing the IP Address of a Clock Server............................................................................................................262
1.8.5.1 Scheme Overview........................................................................................................................................................ 262
1.8.6 Optimizing the Transmission Configuration Model............................................................................................ 276
1.8.6.1 Scheme Overview........................................................................................................................................................ 277
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. vi

5G RAN
1.9 Security Networking Data Reconfigurations............................................................................................................ 283

1.9.1 Changing a Single IPsec Tunnel to an IPsec Tunnel Pair (Only for IPv4 Transmission)......................... 284
1.9.1.1 Scheme Overview........................................................................................................................................................ 284
1.9.2 Changing a Single Virtual Route to Active/Standby Static IP Routes........................................................... 294
1.9.2.1 Scheme Overview........................................................................................................................................................ 295
1.9.3 Replacing an SeGW........................................................................................................................................................ 304
1.9.3.1 Scheme Overview........................................................................................................................................................ 304
1.9.4 Adjusting a VLAN............................................................................................................................................................ 316
1.9.4.1 Scheme Overview........................................................................................................................................................ 317
1.9.5 Changing the VLAN Mode from VLAN Group to Single VLAN (Only for IPv4 Transmission)..............323
1.9.5.1 Scheme Overview........................................................................................................................................................ 323
1.9.6 Changing the VLAN Mode from Single VLAN to Interface VLAN (Only for IPv4 Transmission)........ 329
1.9.6.1 Scheme Overview........................................................................................................................................................ 329
1.10 Reconfigurations Dedicated to the LampSite Solution....................................................................................... 338
1.10.1 Adding an NR TDD Cell.............................................................................................................................................. 340
1.10.1.1 Scheme Overview......................................................................................................................................................340
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. vii

5G RAN

1.10.2 Sharing BBUs Between Macro and LampSite Base Stations......................................................................... 354
1.10.2.1 Scheme Overview......................................................................................................................................................354
1.11 Configuration References.............................................................................................................................................. 366
1.11.1 Setting the gNodeB Maintenance Mode.............................................................................................................. 366
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data............................. 368
1.11.3 Preparing Data in GUI Mode.................................................................................................................................... 368
1.11.4 Delivering Data to Base Stations and Activating the Data............................................................................ 368
1.11.5 Falling Back Configuration Data............................................................................................................................. 368
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. viii

5G RAN
Reconfiguration Guide 1 5G RAN Reconfiguration Guide
1 5G RAN Reconfiguration Guide
Overview
This document provides guidelines for 5G RAN reconfiguration. 5G RAN
reconfiguration consists of NR cell data reconfiguration and gNodeB
reconfiguration. For details about how to configure a gNodeB before it is put into
operation, see 3900 & 5900 Series Base Station Initial Configuration Guide. For
details about how to use or reconfigure a feature, see the related 5G RAN feature
documentation.
Product Versions
The following table lists the product versions related to this document.
Product Name Solution Version Product Version
3900 series base stations 5G RAN3.1 V100R016C10
5900 series base stations
Intended Audience
This document is intended for:
● Network planners
● Network operators
● System engineers
Organization
1.1 Changes in 5G RAN Reconfiguration Guide
This section describes the changes in 5G RAN Reconfiguration Guide.
1.2 Introduction to 5G RAN Reconfiguration
This section defines 5G RAN reconfiguration and describes the general
prerequisites and tools for 5G RAN reconfiguration.
1.3 General Operation Guide
Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 1

5G RAN
This section provides guides for the MAE-Deployment and MML command
operations, either of which can be used for reconfiguration.
1.4 Reconfiguration Scenario Overview
This section describes the typical reconfiguration scenarios and the reconfiguration
methods and tools recommended in these scenarios.
1.5 Cell Data Reconfigurations
This section describes how to reconfigure cells served by gNodeBs in typical
scenarios.
1.6 Base Station Data Reconfigurations
This chapter describes how to reconfigure base station data in typical scenarios.
1.7 Device Data Reconfigurations
This section describes how to reconfigure gNodeB device data in typical scenarios.
1.8 Interface and Link Data Reconfigurations
1.9 Security Networking Data Reconfigurations
1.10 Reconfigurations Dedicated to the LampSite Solution
1.11 Configuration References
This chapter provides the reference documents for data configuration. If you want
to view all the check rules of NE data, obtain the file on the Consistency Check
page.
1.1 Changes in 5G RAN Reconfiguration Guide

This section describes the changes in 5G RAN Reconfiguration Guide.
04 (2021-02-28)
This is the fourth commercial release.
Compared with Issue 03 (2020-07-27), this issue does not include any new topics.
Compared with Issue 03 (2020-07-27), this issue includes the following changes.
Topic Change Description
1.5.6 Changing the NR Cell Added the constraints between MOs when
NR-ARFCNs changing the NR-ARFCNs of an NR cell in
multi-operator sharing scenarios.
1.6.1 Adding a Neighboring Added the data to be prepared for adding a

Base Station for a gNodeB neighboring base station for a gNodeB in
(NSA Networking) NSA networking.
Compared with Issue 03 (2020-07-27), this issue does not exclude any topics.
03 (2020-07-27)
This is the third commercial release.

5G RAN
Compared with Issue 02 (2020-05-21), this issue does not include any new topics.
1.8.6 Optimizing the Updated the engineering rollback operations

Transmission Configuration after optimizing the transmission
Model configuration model.
02 (2020-05-21)
This is the second commercial release.
Compared with Issue 01 (2020-04-07), this issue includes the following new topics:
● 1.5.10 Changing the Cell Name

● 1.5.11 Changing the NR DU Cell Name
1.10.2 Sharing BBUs Between Deleted the restriction that a macro base
Macro and LampSite Base station must be deployed prior to a LampSite
Stations base station when the macro base station
and LampSite base station are deployed at
the same time.
01 (2020-04-07)
This is the first commercial release.
Compared with Draft A (2020-01-20), this issue does not include any new topics.
Compared with Draft A (2020-01-20), this issue includes the following changes.
1.7.1 Replacing the Main ● Changed the recommended data

Control Board When No preparation mode to "Export/Import MPT
SeGW Is Deployed and Port No. Adjustment Data" on the
1.7.2 Replacing the Main MAE-Deployment.
Control Board When an SeGW ● Added the reference document for the
Is Deployed default LMT account and password and
parameter configurations of the FTP server.

5G RAN
1.10.2 Sharing BBUs Between Deleted the description of the UBBPg3a.

Macro and LampSite Base
Stations
Compared with Draft A (2020-01-20), this issue does not exclude any topics.
Draft A (2020-01-20)
This is a draft.
Compared with V100R015C10, this issue includes the following new topics:
1.5.1 Adding an NR FDD Cell (Common Scenarios)
Compared with V100R015C10, this issue includes the following changes.
Entire document ● Added the information about the UMPTga.

● Changed the name of U2020 to MAE-
Access.
● Changed the name of CME to MAE-
Deployment.
1.7.1 Replacing the Main Added the description of replacing the main
Control Board When No control board with a UMPTga and the
SeGW Is Deployed description of replacing the UMPTga with a
1.7.2 Replacing the Main UMPTg.
Control Board When an SeGW
Is Deployed
Compared with V100R015C10, this issue excludes the following information:
Descriptions of USB flash drive-based site deployment
1.2 Introduction to 5G RAN Reconfiguration

This section defines 5G RAN reconfiguration and describes the general
prerequisites and tools for 5G RAN reconfiguration.
1.2.1 Definition of 5G RAN Reconfiguration

This section describes the definition, general prerequisites, and overall procedures
of 5G RAN reconfiguration.

5G RAN
Definition
5G RAN reconfiguration refers to the data addition, deletion, or modification after
a 5G RAN system is put into use. A 5G RAN system includes at least one gNodeB.
Data analysis of live networks and networking schemes after 5G RAN
reconfiguration are determined based on actual network conditions.
5G RAN reconfiguration may be required for either of the following purposes:
● Network capacity expansion: The live network is adjusted to accommodate
increased traffic volume and provide services for more UEs.
● Network reconstruction: The live network is optimized according to customer
requirements on the network structure.
Scope of this document

Figure 1-1 shows the scope of this document.
Figure 1-1 Scope of this document
1. Reconfiguration evaluation: Before network reconfiguration, you must

evaluate the live network to find out the bottleneck of the network and
determine the reconfiguration scheme.

5G RAN
2. Reconfiguration scheme design: Plan and design the target topology, required
equipment, and equipment connections.
3. Engineering preparation: Collect required information and prepare software,
hardware, license file, and configuration data.
4. Engineering implementation: Implement reconfiguration, including hardware
adjustment and data activation.
5. Engineering verification: Check whether the reconfiguration is successful. If
the reconfiguration is successful, no further action is required. If the
reconfiguration fails, rollback is required.
6. Engineering rollback: Roll back the network to its original configuration state.
NOTE
This document does not include Reconfiguration evaluation and Reconfiguration scheme
design. It includes only engineering preparation, engineering implementation, engineering
verification, and engineering rollback after the reconfiguration scheme has been determined.
1.2.2 General Prerequisites

This section describes the general prerequisites for 5G RAN reconfiguration.
● The gNodeB communicates with the MAE or LMT normally, and you have
logged in to the MAE or LMT.
● Information about the status of cells and alarms has been recorded.
Operators must ensure that the status of cells does not change and no new
alarms are generated after the reconfiguration.
● You have read the following documents: technical specifications' documents
under the Technical Description node, hardware description documents
under the Hardware Description node, hardware maintenance documents
under the Hardware Maintenance node, and feature parameter description
documents under the Function Description node
1.2.3 Reconfiguration Tools

This section describes the tools used for 5G RAN reconfiguration, as well as their
characteristics and usage scenarios.
Table 1-1 describes the tools for 5G RAN reconfiguration.
Table 1-1 Reconfiguration Tools

Tools Reconf Usage Characteristic Configuration
igurat Scenari Operation
ion o
Mode
LMT MML Reconfi Data of only one NE is 1.3.2 Running MML

comm guring to be reconfigured Commands on the LMT
ands one NE locally.

5G RAN

ion o
Mode
MAE- MML Batch Data of one or more 1.3.3 Running MML

Access comm reconfi NEs is to be Commands on the MAE-
ands guratio reconfigured remotely. Access
n
MAE- GUI Reconfi Data of only one NE is 1. Select a gNodeB from

Deplo guring to be reconfigured. the left pane of the
yment one NE planned data area.
The object navigation
tree is displayed in the
lower left part of the
window.
2. In the object
navigation tree, click
the Search tab and
type the MO
information you want
to configure. The
MAE-Deployment
automatically finds
the corresponding
MOs.
3. Select the required
MO from the search
result and edit the
planned data in the
right pane.
For detailed
operations, see section
Introduction to Data
Configuration
Operations in the
MAE-Access online
help.
4. Verify data accuracy.
There are many
verification methods.
You need to select one
as required. For details
about the verification
methods, see the
description of the data
verification procedure
in the 1.3.1 MAE-
Deployment
Operation Guide.

5G RAN

ion o
Mode
Batch Batch Data of multiple NEs 1. Use a summary data

reconf reconfi except neighbor file to collect data on
igurati guratio relationship-specific the live network.
on n data is to be configured. a. Prepare a summary
Users can add or delete data file for batch
but cannot modify configuration.
configuration data.a
a. On the menu
bar, choose
Advanced >
Data
Management >
Customize
Summary Data
File. A dialog
box is displayed
for you to open
the summary
data file.
b. Select the
following
options in
sequence:
Select Default.
Choose NodeB/
eNodeB/
gNodeB/USU
Bulk
Configuration.
Select gNodeB.
Specify Version.
c. Click OK to
enable the
function of
customizing a
summary data
file. Click
and select a
scenario-based
template. The
MAE-
Deployment
automatically
customizes the

5G RAN

ion o
Mode
parameter
names
contained in the
template into
the summary
data file. Then,
click to save
the summary
data file to a
local PC.
For detailed
customization
operations, see
section
Customizing a
Summary Data
File for Batch
gNodeB
Configuration
in the MAE-
Access online
help.b
b. Based on the
parameter names
in the summary
data file, export the
gNodeB data to be
reconfigured from
the planned data
area to the
summary data file.
On the menu bar of
the planned data
area, choose NR
Application >
Network
Adjustment >
Export Base
Station Bulk
Configuration
Data to start the
data export.
2. Open the local
summary data file, fill
out the file as

5G RAN

ion o
Mode
planned, and then

close the file.
3. Import the
reconfigured summary
data file into the
MAE-Deployment to
complete batch
reconfiguration of
gNodeB data.
On the menu bar of
the planned data area,
choose NR
Application >
Network Adjustment
> Import Base
Station Bulk
Configuration Data
to start the data
import.
For details about data
import and export, see
the section Importing
and Exporting
gNodeB Data for
Batch Configuration
in the MAE-Access
online help.
There are many
methods, see the
in 1.3.1 MAE-
Deployment
Operation Guide.

5G RAN

ion o
Mode
Applyi Batch ● Data of multiple NEs On the menu bar of the

ng reconfi is to be reconfigured, planned data area,
templ guratio and a data value is choose Advanced > Data
ates n the same for these Management > Apply
NEs. Template. Then, apply
● You can modify the template. For
parameters of detailed operations, see
multiple MOs at a section Applying
time. Templates in the MAE-
Access online help.

5G RAN

ion o
Mode
Radio Batch The neighbor 1. On the menu bar,

data reconfi relationship-related choose NR
planni guratio data is to be Application >
ng file n reconfigured. Network Adjustment
> Network
Adjustment > Export
Radio Network
Planning Data. Then,
export planned radio
data from the MAE-
Deployment to the
file.
2. Edit data in the file
based on the prepared
data. Then, close the
file.
3. On the menu bar,
choose NR
Application >
Network Adjustment
> Import Radio
Network Planning
Data. A dialog box is
displayed for you to
import planned radio
data. Then, import the
data from the file into
the MAE-Deployment
For details about how
to import and export a
radio data planning
file, see section
Importing and
Exporting Planned
Radio Data in the
MAE-Access online
help.

5G RAN

ion o
Mode
ID/ Batch Change the name and 1. On the menu bar,

Name reconfi ID of the gNodeB. choose NR
modifi guratio Application >
cation n Network Adjustment
> Export ID/Name
Adjustment Data.
Then, export the
gNodeB names and
IDs, and cell and local
cell IDs and names to
a file.
2. Edit data in the file
based on the data
preparation. Then,
close the file.
3. On the menu bar,
choose NR
Application >
Network Adjustment
> Import ID/Name
Adjustment Data
Then, import the data
from the file into the
MAE-Deployment
There are many
methods, see the
in the 1.3.1 MAE-
Deployment
Operation Guide.
For detailed import and
export operations, see
section Importing and
Exporting Names and
IDs in the MAE-Access
online help.

5G RAN

ion o
Mode
a: For MOs that support batch reconfiguration, see the Parameter List file. On
the MAE-Deployment menu bar, choose Advanced > Data Management >
Download Reference Files, set filter criteria and obtain the Parameter List file.
b: You can customize only "List" sheets. Customize a unique "List" sheet for each
MO.
1.3 General Operation Guide

This section provides guides for the MAE-Deployment and MML command
operations, either of which can be used for reconfiguration.
MAE-Deployment operations are performed online by default.
MML command operations are performed on the LMT or MAE-Access.
1.3.1 MAE-Deployment Operation Guide

In reconfiguration scenarios, you can prepare and activate data by using the MAE-
Deployment. This section describes the operation process for preparing data by
using the MAE-Deployment. For details about how to activate data, see the
remote activation description of the engineering implementation section in each
scenario.
NOTE
The functions supported by MAE-Deployment vary with versions.
Prerequisites
NEs have been connected to the MAE-Access and the configuration data has been
collected.
MAE-Deployment Operation Process

When preparing data by using the MAE-Deployment, operation process is the
same in each reconfiguration scenario but the reconfiguration mode is different.
Figure 1-2 shows the data preparation process. Table 1-2 describes the process.

5G RAN
Figure 1-2 5G RAN reconfiguration process
NOTE
When preparing 5G RAN data by using MAE-Deployment functions, you can click to
view the MAE-Deployment Help for the detailed function operations and introduction.
Table 1-2 5G RAN reconfiguration process

Procedure Description
Connect an Use the MAE-Deployment to configure NE data only after the NE

NE to the connects to the MAE-Access.
MAE-Access.
Collect Before configuring data, collect the data to be configured.

configuratio
n data.
Start the Start the MAE-Deployment on the MAE-Access.

MAE-
Deployment
.

5G RAN
Procedure Description
Create a Create a planned data area before configuring data. The

planned subsequent operations are performed in this area.a
data area. 1. On the menu bar, choose Area Management > Planned Area
> Planned Area Management. The page for managing
planned data areas is displayed.
2. Click Create in the upper right area. The dialog box for
creating a planned data area is displayed.
For details about how to create a planned data area, click
in the upper right corner to obtain the online help.
Reconfigure Prepare data using different MAE-Deployment functions based

data. on the reconfiguration scenario. The most common function is
batch reconfiguration. The MAE-Deployment provides the
following reconfiguration functions. For detailed operations, see
the section related to data preparation for each scenario.
● Batch configuration:
– Batch reconfiguration
– Radio data planning file
– ID/Name modification
● Single base station configuration: GUI-based configuration
Verify After data reconfiguration is complete, verify the data to ensure

configuratio data accuracy.
n data. On the menu bar of the planned data area, choose Advanced >
Data Management > Check Data to start verification. For
detailed operations, click to obtain the online help.
When verifying configuration data, modify configuration data as
prompted until the verification succeeds.
Export Export the configuration data from the MAE-Deployment as

configuratio scripts and activate it.
n scripts On the menu bar of the planned data area, choose Area
and activate Management > Planned Area > Export Incremental Scripts to
data. export configuration scripts.b
For detailed operations, see Exporting Incremental Scripts from
a Planned Data Area in the MAE-Access online help.
a: To create GBTSs, NodeBs, or multimode base stations, you need to add the
base station controllers managing these base stations to the planned data area
after you create a planned data area.
b: If the OMCH will be disconnected in the reconfiguration scenario, you are
advised to export the full base station script during the script export. The
operation portal is as follows: Choose Advanced > Data Management > Export
NE Files in the current or planned data area.

5G RAN
1.3.2 Running MML Commands on the LMT

The LMT is used to maintain a single gNodeB. The data configuration scripts can
be activated when you run batch MML command scripts on the LMT. Using the
LMT facilitates quick reconfiguration of a gNodeB.
Prerequisites
● The gNodeB and LMT communicate with each other properly.
● You have logged in to the LMT and obtained the batch execution permissions.
Context
When the parameter settings of an MML command depend on the output of
other MML commands, the MML commands must be executed batch by batch.
Procedure
Step 1 On the LMT, click Batch. The Local Maintenance Terminal window is displayed,
and the Batch tab page is displayed within the window.
Step 2 Copy and paste the MML command scripts to be executed in sequence to area 1,
as shown in Figure 1-3.
Figure 1-3 Area for batch executing MML command scripts
Step 3 Click Go. All the MML command scripts in area 1 will be executed one by one.
----End
1.3.3 Running MML Commands on the MAE-Access

You can run MML commands on the MAE-Access to configure base stations. You
can reconfigure one or more base stations that have connected to the MAE-Access
at a time by running batch MML command scripts on the MAE-Access.
Prerequisites
● The gNodeB and MAE-Access communicate with each other properly.
● You have logged in to the MAE-Access and are authorized to run MML
commands.

5G RAN
Context
● If file upload or download is required, it must be performed on each base
station one by one.
● If multiple base stations are reconfigured simultaneously, the software
versions and parameters to be reconfigured must be the same.
Procedure
Step 1 From the main menu of the MAE-Access, choose Maintenance > MML
Command.
Step 2 In the left pane, select a base station type. In the navigation tree, select the NEs to
be reconfigured, as shown in Figure 1-4.
NOTE
Multiple NEs of the same version can be selected at a time.

5G RAN
Figure 1-4 Selecting NEs
Step 3 In the window shown in Figure 1-4, click to enter the script mode.
Step 4 In the right pane, enter the MML commands to be executed, as shown in Figure
1-5.

5G RAN
Figure 1-5 Running MML commands
Step 5 Click to create a batch processing task.

Step 6 In the New Task dialog box, enter a name in Task Name. Choose Other > MML
Script in Task Type. Set Execution Type, and click Next.
Figure 1-6 shows the settings.
Figure 1-6 Creating a task (1)
Step 7 Set the time or period to execute the task and click Next.
Step 8 Select the Select NE option. In the displayed Confirm dialog box, click OK. Select
the NEs on which the MML scripts are to be executed, set Run Mode, Error-
Execution Mode, and Execution Result. Then, click Finish. Figure 1-7 shows the
settings.
The Task Management window appears, displaying all MML script tasks.

5G RAN
If Status and Execution Result are Finished and Successful respectively, the MML
scripts are successfully executed. If Running Results is Failed or Partly
Successful, click the task and view the failed NEs and MML scripts in the Result
Information area or execution result file.
Figure 1-7 Creating a task (2)
----End
1.4 Reconfiguration Scenario Overview

This section describes the typical reconfiguration scenarios and the reconfiguration
methods and tools recommended in these scenarios.
Table 1-3 lists the recommended reconfiguration modes and tools in different
scenarios.

5G RAN
Table 1-3 Recommended reconfiguration modes and tools

Scenario Recommen Recommen Recommend
ded Mode ded Mode ed Tool
for One NE for Batch
Reconfigura NE
tion Reconfigura
tion
Cell Data 1.5.1 Adding an NR GUI Batch MAE-

Reconfigu FDD Cell (Common reconfigurati Deployment
rations Scenarios) on
1.5.2 Adding an NR
TDD Cell (Common
Scenarios)
1.5.3 Changing the
NR Cell Bandwidth
1.5.4 Changing the
TX/RX Mode of an
NR Cell
1.5.5 Changing the
Coverage Radius of
an NR Cell
1.5.6 Changing the Radio data Radio data MAE-

NR Cell NR-ARFCNs planning file planning file Deployment
1.5.7 Changing the
NR DU Cell PCI

Cell ID planning file planning file Deployment
1.5.9 Changing the
NR Cell ID
1.5.10 Changing the
Cell Name
1.5.11 Changing the
NR DU Cell Name

TAC planning file planning file Deployment
1.5.13 Changing the
Neighboring Cell
Parameters

5G RAN

Reconfigura NE
tion Reconfigura
tion
1.5.14 Changing the GUI Batch MAE-

Intra-Frequency A3 reconfigurati Deployment
Offset on
1.5.15 Changing the
NR Cell Power
1.5.16 Changing the
Uplink-Downlink
Slot Assignment and
Slot Structure of an
NR TDD Cell
1.5.17 Adjusting the
Association
Relationships
Between NR Cells
and RF Modules
Base 1.6.1 Adding a GUI Batch MAE-

Station Neighboring Base reconfigurati Deployment
Data Station for a gNodeB on and radio
Reconfigu (NSA Networking) data
rations planning file
1.6.2 Changing the ID/Name ID/Name MAE-

Base Station Name modification modification Deployment
1.6.3 Changing the
gNodeB ID
Device 1.7.1 Replacing the Adjustment Adjustment MAE-

Data Main Control Board of main of main Deployment
Reconfigu When No SeGW Is control control
rations Deployed board and board and
1.7.2 Replacing the port number port number
Main Control Board
When an SeGW Is
Deployed
1.7.3 Replacing BBPs GUI Batch MAE-

1.7.4 Changing CPRI reconfigurati Deployment
Ports for RF Modules on
1.7.5 Adding or
Deleting an RF
Module

5G RAN

Reconfigura NE
tion Reconfigura
tion
Interface 1.8.1 Replacing a GUI Batch MAE-

and Link MAE-Access reconfigurati Deployment
Data on
Reconfigu
rations 1.8.2 Changing the GUI Batch MAE-
Local Maintenance reconfigurati Deployment
IP Address on
1.8.3 Changing the ● MML ● MML ● LMT if

Device IP Address comman command the device
(IPv4 Old Model and ds if the s if the IP address
IPv6 New Model) device IP device IP (old
address address model)/
(old (old IPv4
model)/ model)/ address
IPv4 IPv4 (new
address address model) to
(new (new be
model) model) to changed
to be be is the OM
changed changed IP address
is the is the OM ● MAE-
OM IP IP Deployme
address address nt if the
● Batch ● Batch device IP
reconfigu reconfigu address
ration if ration if (old
the the model)/
device IP device IP IPv4
address address address
(old (old (new
model)/ model)/ model) to
IPv4 IPv4 be
address address changed
(new (new is not the
model) model) to OM IP
to be be address
changed changed
is not the is not the
OM IP OM IP
address address

5G RAN

Reconfigura NE
tion Reconfigura
tion
1.8.4 Changing the ● MML ● MML ● LMT if

IPv4 Address (IPv4 comman command the IPv4
New Model) ds if the s if the address
IPv4 IPv4 (new
address address model) to
(new (new be
model) model) to changed
to be be is the OM
changed changed IP address
is the is the OM ● MAE-
OM IP IP Deployme
address address nt if the
● Batch ● Batch IPv4
reconfigu reconfigu address
ration if ration if (new
the IPv4 the IPv4 model) to
address address be
(new (new changed
model) model) to is not the
to be be OM IP
changed changed address
is not the is not the
OM IP OM IP
address address
1.8.5 Changing the IP GUI Batch MAE-

Address of a Clock reconfigurati Deployment
Server on
1.8.6 Optimizing the Planning file Planning file MAE-

Transmission Deployment
Configuration Model
Security 1.9.1 Changing a MML MML MAE-Access

Networki Single IPsec Tunnel commands commands
ng Data to an IPsec Tunnel
Reconfigu Pair (Only for IPv4
rations Transmission)

5G RAN

Reconfigura NE
tion Reconfigura
tion
1.9.2 Changing a GUI Batch MAE-

Single Virtual Route reconfigurati Deployment
to Active/Standby on
Static IP Routes
1.9.3 Replacing an
SeGW
1.9.4 Adjusting a
VLAN
1.9.5 Changing the
VLAN Mode from
VLAN Group to
Single VLAN (Only
for IPv4
Transmission)
1.9.6 Changing the
VLAN Mode from
Single VLAN to
Interface VLAN
(Only for IPv4
Transmission)
Reconfigu 1.10.1 Adding an NR GUI Batch MAE-

rations TDD Cell reconfigurati Deployment
Dedicated on
to the
LampSite 1.10.2 Sharing BBUs MML MML MAE-Access
Solution Between Macro and commands commands
LampSite Base
Stations
1.5 Cell Data Reconfigurations

This section describes how to reconfigure cells served by gNodeBs in typical
scenarios.
1.5.1 Adding an NR FDD Cell (Common Scenarios)

This section describes how to add an NR FDD cell without adding a new site,
including the scheme overview, engineering preparation, engineering
implementation, engineering verification, and engineering rollback.

5G RAN
1.5.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology changes for adding an NR FDD cell.
Application Scenarios
● There are weak-signal areas or coverage holes in the current gNodeB
coverage, requiring an additional NR cell to supplement coverage.
● As the gNodeB traffic increases, the capacity requirements of cell edge UEs
(CEUs) cannot be met. In this situation, the coverage areas of the existing NR
cells need to be reduced and an additional NR cell needs to be added.
● The operator uses a new frequency band.
Reconfiguration Impact
After an NR FDD cell is added, information about the new cell must be configured
on the neighboring gNodeB based on the network plan.
Reconfiguration Scheme
The following figure shows the reconfiguration procedure for adding an NR FDD
cell. Determine the reconfiguration scheme for adding an NR FDD cell to an
existing site according to the following table.
Table 1-4 Scheme options
If... Then...
Baseband resources are insufficient Add BBPs.
RF resources are insufficient Perform one of the following

operations:
● Add RF modules and antenna line
devices (ALDs) on the existing RRU
chain or ring.
● Add an RRU chain or ring, and then
add RF modules and ALDs.
A BBP to which RF modules are Modify the position of the BBP where
connected is changed the RRU chain or ring is set up.
The downtilt of an antenna needs to Add a remote electrical tilt (RET)

be remotely adjusted antenna.
Uplink coverage is limited due to the Add a tower-mounted amplifier

link quality imbalance between the (TMA).
uplink and the downlink or the uplink
attenuation from the antenna to the
RF module is excessively large

5G RAN
If... Then...
The numbers of TX and RX channels in 1. Add a SECTOR MO without creating

a sector are inconsistent the default sector equipment.
2. Add a set of sector equipment.
Figure 1-8 Reconfiguration procedure for adding an NR FDD cell

5G RAN
Topology Changes
Figure 1-9 shows the topology changes after a BBP and an RF module are added.
Figure 1-9 Topology changes
1.5.1.2 Engineering Preparation

This section describes the engineering preparation for adding an NR FDD cell,
including information collection and preparation of hardware, software, license
files, certificates, and data. It also describes data preparation modes and provides
MML configuration script examples.
Information Collection
Table 1-5 describes the information to be collected for data preparation.

5G RAN
Table 1-5 Information to be collected
Information Description
Base station model Model of the base station to which the NR FDD cell is
to be added, for example, DBS5900 5G
BBP model Model of the BBP, for example, UBBPg
RF module type Type of the RF module to be added
Topology If an RF module is added, obtain the CPRI topology of

the RF module. Currently, only the star topology is
supported.
Antenna equipment Models of the remote electrical tilt (RET) antenna and
tower-mounted amplifier (TMA)
Sector information ● Number of antennas in the sector

● TX/RX mode of the sector
TRP information of TX/RX mode, CPRI compression mode, and maximum

an NR DU cell transmit power of the TRPs foran NR DU cell
NR DU cell Bandwidth, frequency band, PCI, and duplex mode

information
NR cell information NR-ARFCN and others
NOTE
Before the adjustment, run the DSP TXBRANCH/DSP RXBRANCH or DSP RRU command to
query the capability of the RF module. This is to ensure that the NR-ARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
adjustment.
Hardware Preparation
Prepare the hardware listed in Table 1-6.
Table 1-6 Hardware to be prepared
If... Then...
Baseband resources Add BBPs.

are insufficient
RF resources are Add RF modules, CPRI cables, ALDs, and optical

insufficient modules.
An RET antenna is to Add a remote control unit (RCU) and antenna interface
be configured standards group (AISG) multi-wire cables.
A TMA is to be Add a TMA and jumpers.

configured

5G RAN
License File Preparation

If the license file is to be updated, a new license file is required.
Security Certificate Preparation

N/A
Data Preparation
Determine the data to be prepared, based on the reconfiguration procedure. Then,
prepare the data according to the following table.
Table 1-7 Data preparation for adding an FDD cell
SN Operati MO Configuration Reference

on
1 Add RU (using the For details about parameter settings, see

MML Base Station Cabinets and Subracks
commands)/B (Including the BBU Subrack) Configuration
BP (using the Feature Parameter Description.
MAE-
Deployment)
2 Add RRUCHAIN For details about parameter settings, see

RF Unit and Topology Management
3 Add RRU Feature Parameter Description.
4 Add RET For details about parameter settings, see
ALD Management Feature Parameter
Description.
5 Modify ANTENNAPO Change the value of ALD Power Switch to
RT/RETPORT ON.
6 Add TMA For details about parameter settings, see

ALD Management Feature Parameter
Description.
7 Add SECTOR For details about parameter settings, see
Cell Management Feature Parameter
Description.
8 Modify RRUCHAIN Move the RRU chain or ring to the new

BBP.
9 Add SECTOREQM For details about parameter settings, see

10 Add NRDUCell Description.
11 Add NRDUCellTrp

5G RAN

on
12 Add NRCell
Data Preparation Mode

Data preparation can be performed in three different ways using the MAE-
Deployment or MML commands. MAE-Deployment-based data preparation is
preferable in this scenario. You can configure gNodeBs in batches using the MAE-
Deployment batch reconfiguration mode or configure a single gNodeB on the
MAE-Deployment.
NOTE
Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adding an FDD Cell"). For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide 1.11.3 Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.
MML Configuration Script Example

In the following example, a UBBPg, an RRU chain or ring, an RRU, an RET
antenna, and a TMA are added.
Adding an FDD cell
/*Adding a UBBPg*/
ADD BRD: SN=2, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1;
/*Adding an RRU chain*/
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=2, CR=AUTO,
USERDEFRATENEGOSW=OFF;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=NO, RN="5G06_60", RXNUM=4,
TXNUM=4, MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
/*Adding an RET antenna*/
ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Turning on the ALD power supply switch*/
MOD RETPORT: CN=0, SRN=60, SN=0, PWRSWITCH=ON;
/*Adding a TMA*/
ADD TMA: DEVICENO=1, DEVICENAME="TMA1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1,
VENDORCODE="hw", SERIALNO="hw";
/*Adding a sector*/
ADD SECTOR: sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A, ant2Cn=0, ant2Srn=60,
ant2Sn=0, ant2N=R0B, createSectorEqm=FALSE;

5G RAN
/*Adding sector equipment*/

ADD SECTOREQM: sectorEqmId=0, sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A,
antType1=RXTX_MODE, ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B, antType2=RXTX_MODE;
/*Adding an NR DU cell*/
ADD NRDUCELL: NrDuCellId=0, NrDuCellName="DUCELL1", DuplexMode=CELL_FDD, CellId=1,
PhysicalCellId=1, FrequencyBand=N3, DlNarfcn=370000, UlBandwidth=CELL_BW_20M,
DlBandwidth=CELL_BW_20M, LogicalRootSequenceIndex=80, TrackingAreaId=0,
SsbDescMethod=SSB_DESC_TYPE_GSCN, SsbFreqPos=4625;
/*Adding a TRP for the NR DU cell*/
ADD NRDUCELLTRP: NrDuCellTrpId=7, NrDuCellId=0, TxRxMode=4T4R, BasebandEqmId=0,
PowerConfigMode=TRANSMIT_POWER, MaxTransmitPower=100, CpriCompression=NO_COMPRESSION;
/*Adding an NR DU cell coverage item and binding sector equipment to the NR DU cell's TRP.
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=7, NrDuCellCoverageId=1, SectorEqmId=0;
/*Adding an NR cell*/
ADD NRCELL: NrCellId=7, CellName="7", CellId=7, FrequencyBand=N3, DuplexMode=CELL_FDD;
/*(Optional, required when ALM-29870 NR DU Cell TRP Unavailable with "Specific Problem" being
"Configuration conflict" is reported) Starting NR DU cell redeployment (high-risk)*/
STR NRDUCELLREDEPLOY: NrDuCellId=7;
1.5.1.3 Engineering Implementation

This section describes how to add an NR FDD cell locally and remotely.
Prerequisites
Information, hardware, software, and data required for adding an NR FDD cell are
ready.
Context
● Local Operation describes the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operation describes the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.
Procedure
● Local Operation
a. Insert the XBBP into the subrack. For details about the operations, see
Replacing the UBBP in BBU5900 Hardware Maintenance Guide.
b. Install an optical module. For details, see Replacing the Optical Module
in BBU5900 Maintenance Guide.
c. Install an RF module. For details, see the related RRU installation guides.
d. Install the antenna system. For details about the operation, see Antenna
Installation.
● Remote Operation
– Using the MAE-Deployment:
i. To prevent alarms from being generated during reconfiguration, set
the gNodeB engineering maintenance mode to expand status.
For details, see 1.11.1 Setting the gNodeB Maintenance Mode.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to restore the
gNodeB if the reconfiguration fails.

5G RAN
1) To back up the configuration file, run the BKP CFGFILE

command.
2) To export the configuration file, run the ULD CFGFILE command.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Block NR DU cells.
If the RRU is inserted into an existing RRU chain or ring, this step is
required to block all NR DU cells served by the RRUs following this
RRU.
Run the BLK NRDUCELL command with Cell Administrative State
set to CELL_HIGH_BLOCK.
iv. Deliver the configuration data to the base station and activate it. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
v. Activate the new NR cell.
Run the ACT NRCELL command.
For example, ACT NRCELL: NrCellId=77;
vi. Unblock NR DU cells.
Run the UBL NRDUCELL command.
vii. (Optional, required when ALM-29870 NR DU Cell TRP Unavailable
with "Specific Problem" being "Configuration conflict" is reported)
Start NR DU cell redeployment.
If cells of different TRX types or duplex modes are deployed on the
same BBP, ALM-29870 NR DU Cell TRP Unavailable with "Specific
Problem" being "Configuration conflict" may be reported due to
incorrect BBP mode. In this case, run the STR NRDUCELLREDEPLOY
command to trigger the BBP mode adjustment. This is a high-risk
command and will cause automatic reestablishment of all cells on
the BBP.
viii. After the data reconfiguration is complete, set the gNodeB
engineering maintenance mode to NORMAL.
– Using MML commands:
command.

5G RAN
RRU.
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
v. Unblock NR DU cells.
vi. Activate the new NR cell.
the BBP.
----End
1.5.1.4 Engineering Verification

This section describes how to verify the addition of an NR FDD cell.
Procedure
Step 1 Verify that no NR-cell-related alarm is reported, such as ALM-29841 NR Cell
Unavailable, ALM-29870 NR DU Cell TRP Unavailable, and ALM-29871 NR DU Cell
TRP Capability Degraded.
If an NR-cell-related alarm is reported, clear it according to instructions in 3900 &
5900 Series Base Station Alarm Reference.
Step 2 Run the DSP NRCELL command. Verify that Cell Available State is
CELL_INST_AVAILABLE for the NR cell.
If NR Cell State is CELL_INST_UNINSTALL, check the NR cell configuration or
hardware based on the value of Cell Latest State Change Reason in the
command output.
Step 3 Run the LST NRCELL command to check whether the cell information is the same
as planned.

5G RAN
If the cell information is not the same as planned, perform the following steps:
If... Then...
The reconfiguration Check whether the cell information in the modified

is performed on the configuration data file is the same as planned:
MAE-Deployment ● If they are different, modify the configuration data
file again and import it into the system. Then perform
the operations in Engineering Implementation again
to deliver the data to the base station and then
activate it on the base station.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical support
hotline.
The reconfiguration Check whether the parameters in the script are correct:
is performed by ● If they are incorrect, modify the parameters in the
using MML script. Run the RMV NRCELL command to remove the
commands cell. Then run the ADD NRCELL command to add a
cell again.
● If they are correct, contact Huawei technical support
or dial the Huawei technical support hotline.
----End
1.5.1.5 Engineering Rollback

If the reconfiguration fails, the gNodeB configuration can be rolled back to the
original state.
Procedure
Step 1 Restore the configuration data.
● For detailed operations using the MAE-Deployment, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.

5G RAN
i. Run the DSP ROLCFGINFO command to query the configuration

rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE
○ Blind configuration recovery is supported only when the Configuration

Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.
Step 2 Restore the physical connections.
Step 3 Verify the engineering rollback by referring to the procedures in 1.5.1.4

Engineering Verification.
----End
1.5.2 Adding an NR TDD Cell (Common Scenarios)

This section describes how to add an NR TDD cell without adding a new site,
including the scheme overview, engineering preparation, engineering
implementation, engineering verification, and engineering rollback.

reconfiguration scheme, and topology changes for adding an NR TDD cell.
● There are weak-signal areas or coverage holes in the current gNodeB
coverage, requiring an additional NR TDD cell to supplement coverage.
● As the gNodeB traffic increases, the capacity requirements of cell edge UEs
(CEUs) cannot be met. In this situation, the coverage areas of the existing NR
TDD cells need to be reduced and an additional NR TDD cell needs to be
added.
● The operator uses a new frequency band.
None

5G RAN
NOTE
After an NR TDD cell is added, information about the new cell must be configured on the
neighboring gNodeB based on the network plan.
Determine the reconfiguration scheme for adding an NR TDD cell to an existing
site according to the following table.

If... Then...
Baseband resources are insufficient Add BBPs.
RF resources are insufficient Add an RRU chain or ring, and then

RF resources are sufficient Check whether the CPRI resources of

AAUs are sufficient. If they are
insufficient, add CPRI resources.
Alternatively, replace an optical
module to increase the CPRI
bandwidth or change the CPRI
compression mode of existing NR TDD
cells.
The antenna tilts need to be adjusted Upload the license file for adjusting
the antenna tilt.
Figure 1-10 shows the reconfiguration procedure for adding an NR TDD cell.

5G RAN
Figure 1-10 Reconfiguration procedure for adding an NR TDD cell

5G RAN
Topology Changes
Figure 1-11 shows the topology changes after a BBP and an RF module are
added.

5G RAN

This section describes the engineering preparation for adding an NR TDD cell,
files, certificates, and data. It also describes data preparation modes and provides
Table 1-9 describes the information to be collected before adding an NR TDD cell.
Base station model Model of the base station to which the NR TDD cell is
to be added, for example, DBS5900 5G
BBP model Model of the BBP, for example, UBBPfw
RF module type Type of the RF module to be added, for example, AAU

5G RAN
Topology CPRI/eCPRI topology of the RF module, such as the star

topology
Antenna equipment Model of the remote electrical tilt (RET) antenna
Sector information Cabinet number, subrack number, slot number, and port
number of the AAU in a sector
Sector equipment Channel numbers of the transmit and receive antennas,

information and the transmit and receive mode of the antennas in
the sector equipment
NR cell information Basic information about NR cells, such as the

bandwidth, NR-ARFCN, and duplex mode
NR DU cell Cell radius, uplink-downlink subframe configuration,

information subcarrier spacing, and so on
Sector equipment Information about sector equipment of NR cells,

information of NR including sector equipment ID, reference signal power,
cells and baseband equipment ID of each NR cell
TRP information of Baseband equipment, TX/RX mode, CPRI compression,

an NR DU cell maximum transmit power, and so on
NOTE
adjustment.
Table 1-10 describes the hardware to be prepared for adding an NR TDD cell.

5G RAN
If... Then...
Baseband resources ● Check whether the BBP boards in use can provide
are insufficient sufficient baseband resources for the NR TDD cell to
be added, based on the board specifications. For
example, a single UBBPfw supports three TDD MM
cells. If a fourth cell is to be added, a new BBP must
be installed.
● Check whether the cell to be added can be served by
the same BBP as the existing cells. For the constraints
on binding cells with baseband equipment, see the
scenario of "binding cells with baseband equipment."
For example, TDD MM cells with different
bandwidths are not allowed to share the same BBP.
Therefore, a BBP must be added for the newly added
TDD MM cells with bandwidths different from
existing cells.
RF resources are ● Add AAUs for coverage holes and weak coverage
insufficient areas, based on the network plan.
● Check whether the CPRI/eCPRI resources required by
the AAUs are sufficient. If the CPRI resources are
insufficient, change the CPRI compression mode or
add a CPRI optical fiber or optical module.
● RF-related hardware includes RF modules, CPRI/
eCPRI cables, antennas, and optical modules.
An RET is to be Add remote control units (RCUs), Antenna Interface

configured Standards Group (AISG) multi-wire cables, or jumpers
as required.
Software Preparation
If the RET to be added needs to be upgraded, acquire the latest software and data
from the vendor.


N/A
Data Preparation

5G RAN
Table 1-11 Data preparation for adding an NR TDD cell

SN Opera MO Configuration Reference
tion
1 Add RU (using the For details about parameter settings, see

MML Base Station Cabinets and Subracks
commands)/B (Including the BBU Subrack) Configuration
BP (using the Feature Parameter Description.
MAE-
Deployment)
2 Add RRUCHAIN For details about parameter settings, see RF

Unit and Topology Management Feature
3 Add RRU Parameter Description.
If RF resources are sufficient but CPRI
resources are insufficient, change the CPRI
compression mode of the cell to increase the
CPRI bandwidth.
4 Add SECTOR For details about parameter settings, see

5 Add SECTOREQM Description.
6 Add NRCell
7 Add NRDUCell
8 Add NRDUCellTrp

MAE-Deployment.
name of the scenario being "Adding a TDD Cell"). For details, see the
script examples.

In the following example, a baseband processing unit, an RRU chain, and an RRU
are added.
/*(Optional) Adding a UBBPfw*/
ADD BRD: SN=2, BT=UBBP-W, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1;

5G RAN
/*(Optional) Adding a UBBPg*/

ADD BRD: SN=2, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1;
/*Adding an RRU chain*/
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNKCHAIN, RCN=0, PS=0, RT=AIRU, RS=NO,
RN="5G28_TDD_100M", RXNUM=64, TXNUM=64, MNTMODE=NORMAL,
RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF;
/*Adding a sector*/
ADD SECTOR: SECTORID=0, ANTNUM=0, CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=60,
RRUSN=0, BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None;
/*Adding an NR DU cell*/
ADD NRDUCELL: NrDuCellId=7, DuCellName=" NR001", FrequencyBand=N77,
UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M, DuplexMode=CELL_TDD,
CellId=77,PhysicalCellId=77, UlNarfcnConfigInd=CONFIG, UlNarfcn=650000,
SsbDescMethod=SSB_DESC_TYPE_GSCN, SsbFreqPos=6400, DlNarfcn=650000, TrackingAreaId=0;
/*Adding a TRP for the NR DU cell (low frequency band)*/
PowerConfigMode=TRANSMIT_POWER, MaxTransmitPower=300;
/*Adding a TRP for the NR DU cell (high frequency band)*/
PowerConfigMode=EIRP, MaxEirp=590, CpriCompression=2DOT5_COMPRESSION;
/*Adding an NR DU cell coverage item and binding sector equipment to the NR DU cell's TRP/
/*Adding an NR cell*/
ADD NRCELL: NrCellId=77, CellName="77", CellId=77, FrequencyBand=N77, DuplexMode=CELL_TDD;
/*(Optional, required when ALM-29870 NR DU Cell TRP Unavailable with "Specific Problem" being
"Configuration conflict" is reported) Starting NR DU cell redeployment (high-risk)*/
STR NRDUCELLREDEPLOY: NrDuCellId=7;

This section describes how to add an NR TDD cell locally and remotely.
Prerequisites
Information, hardware, and software required for adding an NR TDD cell are
ready.
Context
Local Operation describes the operations that must be performed onsite, such as
hardware installation and operations on the LMT.
Remote Operation describes the operations that must be performed on the
operation and maintenance center (OMC), such as reconfiguring parameters using
the MAE-Access or MAE-Deployment.
Procedure
● Local Operation
a. Insert the XBBP into the subrack. For details about the operations, see
Replacing the UBBP in BBU5900 Hardware Maintenance Guide.
c. Install an RF module. For details, see the related RRU installation guides.
d. Install a CPRI optical fiber. For details, see Installing RRU Cables >
Installing a CPRI Optical Fiber in the installation guide for the RRU.

5G RAN
e. Install the antenna system. For details about the operation, see Antenna
Installation.
command.
RRU.
iv. Deliver the configuration data to the base station and activate it. For
v. Activate the new NR cell.
vi. Unblock NR DU cells.
the BBP.

5G RAN

command.
RRU.
v. Unblock NR DU cells.
vi. Activate the new NR cell.
the BBP.
----End

This section describes how to verify the addition of an NR TDD cell.

5G RAN
Procedure

Step 2 Run the DSP NRCELL command. Verify that Cell Available State is Available for
the NR TDD cell.
If NR Cell State is CELL_INST_UNINSTALL, check the NR TDD cell configuration

or hardware based on the value of Cell Latest State Change Reason in the
command output.
Step 3 Run the LST NRCELL command to check whether the NR TDD cell information is
the same as planned.
If the NR TDD cell information is not the same as planned, perform the following
steps:
● If the reconfiguration is performed by using the MAE-Deployment, view the

modified configuration data file to check whether the NR TDD cell
information is the same as planned.
– If they are different, modify the configuration data file again and import
it into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
– If they are the same, an error has occurred when the data is imported
into the system or delivered to the base station. In this situation, contact
Huawei technical support or dial the Huawei technical support hotline.
● If the reconfiguration is performed by using the MML commands, check
whether the parameters in the scripts are correct.
– If they are incorrect, modify the parameters in the scripts. Run the RMV
NRCELL command to remove the NR TDD cell. Then, run the ADD
NRCELL command to add an NR TDD cell again.
– If they are correct, contact Huawei technical support or dial the Huawei
technical support hotline.
----End

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.
Procedure
Step 1 Roll back the reconfiguration data. For detailed operations using the MAE-
Deployment, see the interactive operation guide Rolling Back Configuration
Data.

5G RAN
NOTICE
The activation of configuration data mentioned in 1.5.2.3 Engineering

Implementation is performed step by step. If the preceding step fails, the
configuration in the next step cannot be performed. You need to roll back to the
original configuration based on Step 1.

----End
1.5.3 Changing the NR Cell Bandwidth

This section describes the scheme overview, engineering preparation, engineering
implementation, engineering verification, and engineering rollback for changing
the bandwidth of an NR cell.

reconfiguration scheme, and topology changes for changing the bandwidth of an
NR cell.
The current bandwidth is less than 20 MHz and cannot meet service requirements
due to the growing number of subscribers.
After the bandwidth of an NR cell is changed, the NR cell automatically resets for
the configuration take effect. During the reset, the NR cell cannot provide services.
Figure 1-12 shows the reconfiguration procedure using the MAE-Deployment.
Figure 1-13 shows the reconfiguration procedure using MML commands.
Determine the reconfiguration scheme according to the following table.
If... Then...
Capacity of the old BBP is insufficient Add a BBP.
The maximum bandwidth supported Replace RF modules.

by the old RF modules is low

5G RAN
If... Then...
The types or the TX/RX modes of the Modify the RF module information.
old RF module and those of the new
RF module are different
The NR Absolute Radio Frequency Modify the NR-ARFCNs.

Channel Numbers (NR-ARFCNs) of the
cell are beyond those supported by the
new bandwidth
NOTE
When the 100 MHz cell bandwidth cannot meet service requirements, another NR cell can be
added. For details about how to add an NR cell, see 1.5.1 Adding an NR FDD Cell (Common
Scenarios) or 1.5.2 Adding an NR TDD Cell (Common Scenarios).

5G RAN
Figure 1-12 Reconfiguration procedure for changing the NR cell bandwidth (using
the MAE-Deployment)

5G RAN
Figure 1-13 Reconfiguration procedure for changing the NR cell bandwidth (using
MML commands)
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for changing the bandwidth of
an NR cell, including information collection and preparation of hardware,
software, certificates, and data. It also describes the data preparation mode and
provides MML configuration script examples.
NR cell information If the NR-ARFCNs of the cell need to be changed,

the downlink NR-ARFCNs of the new NR cell
should also be obtained.
NR DU cell information It includes the NR DU cell ID, uplink and

downlink bandwidths of the new cell, and BBP for
the NR DU cell.
If the NR-ARFCNs of the cell need to be changed,
the uplink and downlink NR-ARFCNs of the new
NR cell should also be obtained.
Information about the new If RF modules are replaced, the following

RF modules information about the new RF modules should be
obtained:
● Mode, for example, FDD.
● Type, for example, AAU or MRRU.
● TX/RX mode, for example, 4T4R, 32T32R, or
64T64R.
NOTE
adjustment.
If... Then...
Capacity of the old BBP is insufficient Add a BBP.

5G RAN
If... Then...
Transmission rate of the old optical Add optical modules.

modules is insufficient
The maximum bandwidth supported Add RF modules.

by the old RF modules is low
N/A

N/A
Data Preparation
Table 1-15 Data preparation for changing the cell bandwidth
Reco SN Oper MO Configuration Description

nfig atio
urati n
on
Mod
e
MAE 1 Add BBP Set the Board Type parameter to UBBP-

- W.
Depl If it is set to UBBP-W, set the Base Band
oyme Work Standard to the actual work
nt standard.
For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Modi RRUCHAIN Move the RRU chain or ring to the new
fy BBP.
3 Modi RRU/RFU Set RRU type to target values.

fy
4 Modi NRCell ● Change Frequency Band and

fy Downlink NARFCN to target values.

5G RAN

nfig atio
urati n
on
Mod
e
5 Modi NRDUCell ● Change Frequency Band, Uplink

fy NARFCN and Downlink NARFCN to
target values. Configuration of the
uplink NR-ARFCN is optional.
● Change Uplink Bandwidth and
Downlink Bandwidth to target
values.
MML 1 Deac NRCell -

com tivat
man e
d
2 Add RU Set Board Type to UBBP-W.
If the board type is UBBP-W, set Base
Band Work Standard to the actual
work standard.
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
3 Modi RRUCHAIN Set breakpoints on the chain or ring as
fy follows:
● For a chain topology, only one
breakpoint is required and its position
is 0.
● For a ring topology, two breakpoints
should be set. The first breakpoint
position is 0 and the second is the
number of the RRU level.
4 Modi RRUCHAIN Move the RRU chain or ring to the new

fy BBP.
5 Modi RRU/RFU Change the value of RRU type.

fy Change the parameter value to any
other RRU type for RRUs.
RF Unit and Topology Management
Feature Parameter Description.
6 Modi NRCell ● Change Frequency Band and
fy Downlink NARFCN to target values.

5G RAN

nfig atio
urati n
on
Mod
e
7 Modi NRDUCell ● Change Frequency Band, Uplink

fy NARFCN and Downlink NARFCN to
target values. Configuration of the
uplink NR-ARFCN is optional.
● Change Uplink Bandwidth and
Downlink Bandwidth to target
values.
8 Activ NRCell -
ate

NOTE
Changing NR cell NR-ARFCNs involves the synchronization of neighboring cell information.

To update the information about external NR neighboring cells at the same time, you are
advised to use the MAE-Deployment-provided "radio data planning file". For details about
how to change NR cell NR-ARFCNs, see 1.5.6 Changing the NR Cell NR-ARFCNs.
MAE-Deployment.
NOTE
name of the scenario being "Changing the Cell Bandwidth"). For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
script examples.

In the following MML configuration script example, the LRRU is used.

5G RAN
NOTE
Since a radio planning data file is recommended for modifying NR cell NR-ARFCNs, this MML
configuration example script does not contain steps for changing NR cell NR-ARFCNs. For details
about how to change NR cell NR-ARFCNs, see 1.5.6 Changing the NR Cell NR-ARFCNs.
/*Deactivating the NR cell*/

DEA NRCELL: NrCellId=0;
/*Adding a UBBPfw*/
/*Changing the NR DU cell bandwidth and setting both the uplink and downlink cell bandwidths to 20
MHz*/
MOD NRDUCELL: NrDuCellId=0, UlBandWidth=CELL_BW_20M, DlBandWidth=CELL_BW_20M;
/*Activating the NR cell*/
ACT NRCELL: NrCellId=0;

This section describes the engineering implementation procedures including local
and remote operations.
Prerequisites
The information, hardware and data required for changing the NR cell bandwidth
are ready.
Context
Procedure
● Local Operation
If... Then...
A new BBP is to be added Perform a and b.
An optical module is to be replaced Perform c.
An RF module is to be replaced Perform d.
a. Optional: Insert a new BBP into the corresponding slot.

b. Optional: Connect the RF module for which the NR cell bandwidth needs
to be changed to the new BBP.
c. Optional: Replace an optical module. For details, see Replacing the
Optical Module in BBU Hardware Maintenance Guide.
d. Optional: Replace an RF module.

5G RAN
▪ To replace an AAU, perform operations by referring to AAU Hardware

Maintenance Guide.
▪ To replace an RRU, perform operations by referring to RRU Hardware

Maintenance Guide.
command.
iii. Use the MAE-Access to deliver the batch configuration scripts
iv. After the data reconfiguration is complete, set the gNodeB
----End

This section describes how to verify the change of the NR cell bandwidth.
Procedure


5G RAN

command output.
Step 3 Run the LST NRCELL command to check whether the uplink and downlink NR cell
bandwidths are the same as planned.
If the uplink and downlink cell bandwidths are not the same as planned, check
whether the parameters in the script are set correctly.
● If they are not set correctly, modify the parameters in the script. Then run the
MOD NRDUCELL command to change the uplink and downlink cell
bandwidths again.
● If they are correct, contact Huawei technical support or dial the Huawei
----End

original state.
Procedure
Step 1 Replace the RF module with the original one.
● To replace an AAU, perform operations by referring to AAU Hardware
Maintenance Guide.
● To replace an RRU, perform operations by referring to RRU Hardware
Maintenance Guide.
configuration file.
configuration file.

5G RAN
data.
NOTE

record table.

----End
1.5.4 Changing the TX/RX Mode of an NR Cell

the TX/RX mode of an NR cell.

reconfiguration scheme, and topology changes for changing the TX/RX mode of
an NR cell.
● NR cell capacity does not meet service requirements.
● Weak-coverage areas or coverage holes exist in the NR cell.
After changing the TX/RX mode of an NR cell, you must reset the NR cell to make
the configuration take effect. During the reset, the NR cell cannot provide services.
Figure 1-14 shows the reconfiguration procedure for changing the TX/RX mode of
an NR cell. Determine the reconfiguration scheme according to the following
table.

5G RAN

If... Then...
RF resources are insufficient ● Add RF modules and antenna line

devices (ALDs) on the existing RRU
chain or ring.
● Add an RRU chain or ring, and then
An RET antenna has been configured Modify the RET antenna configuration.
An RRU has been added, and the Replace the antenna connected to the
number of antenna channels is less RRU. The number of antenna channels
than that of the RRU channels must be greater than that of RRU
channels.
A tower-mounted amplifier (TMA) has Change the TMA configuration a

been configured
a: For TDD, no TMA is installed, and therefore this change is not involved.

5G RAN
Figure 1-14 Reconfiguration procedure for changing the TX/RX mode of an NR

cell

5G RAN
Topology Changes
Figure 1-15 shows the topology changes after two 2T2R RF modules are added
and configured to serve a 4T4R NR cell.

5G RAN

This section describes the engineering preparation for changing the TX/RX mode
of an NR cell, including information collection and preparation of hardware,
software, certificates, and data. It also describes the data preparation mode and

Base station model Model of the base station for which the TX/RX mode of
an NR cell is to be changed, for example, DBS5900 5G
RF module type Type of the RF module to be added, for example, MRRU

or AAU

5G RAN
Topology CPRI/eCPRI topology of RF modules (if new RF modules

are added). Currently, NR supports the start topology
only.
Antenna equipment ● Whether RET antennas and TMAs have been

configured
● Number of channels provided by an antenna of a
gNodeB
Sector information ● Number of antennas in the sector

● TX/RX mode of the sector
NR cell information TX/RX mode of an NR cell, for example, 4T4R
If… Then...
RF resources are RF modules, CPRI/eCPRI cables, and optical modules are

insufficient required.

N/A
Data Preparation
Table 1-19 Data preparation for changing the TX/RX mode of a cell
SN Oper MO Configuration Reference

ation
1 Add RRUCHAIN For details about parameter settings, see RF

2 Add RRU/RFU Parameter Description.
3 Modi RET Set RET Type to MULTI_RET and set RET
fy Subunit Number to the actual number of RET
subunits.

5G RAN

ation
4 Modi TMA Set TMA Subunit Number to the actual

fy number of TMA subunits. a
5 Modi SECTOR Set Antenna Number to the number of

fy antennas added to or deleted from a sector. For
example, if a sector is configured with two
antennas before the modification and four
antennas after the modification, set
Operational Mode to ADD, and set Antenna
Number to 2.a
6 Deact NRCell -
ivate
7 Delet NRDUCellCov -
e erage
8 Modi SECTOREQM Set Antenna Number to the number of

fy/Ad antennas added to or deleted from a sector
d and set the TX/RX mode of each antenna. a
For example, if a sector is configured with two
antennas before the modification and four
antennas after the modification, set
Operational Mode to ADD, and set Antenna
Number to 2.
9 Modi NRDUCellTrp Change Transmit and Receive Mode and

fy Maximum Transmit Power to the target
values. For details, see MIMO Feature
Parameter Description in 5G RAN Feature
Documentation.
10 Add NRDUCellCov -
erage
11 Activ NRCell -
ate
a: For TDD, the number of antennas does not need to be configured, and
therefore this modification is not involved.

MAE-Deployment.

5G RAN
NOTE
● If you use the MAE-Deployment for the reconfiguration, perform 1 through 6 to prepare
data 1 and 7 through 9 to prepare data 2. Deliver both data 1 and data 2 during engineering
implementation.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

name of the scenario being "Changing the TX/RX Mode of a Cell"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
guide Preparing Data in GUI Mode.
script examples.

In the following example, RF resources and an RRU chain or ring are added, and
the configurations of the RET antenna and TMA are changed, and the TX/RX
mode of an NR cell is set to 4T4R.
/*Modifying the RET*/
MOD RET: RETTYPE=MULTI_RET, SUBUNITNUM=1;
/*Modifying the TMA*/
MOD TMA: DEVICENO=1, SUBUNITNUM=1;
/*Deactivating the cell*/
/*Removing an NR DU cell coverage item with NR DU Cell TRP ID set to 0 and NR DU Cell Coverage ID set
to 1*/
RMV NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=1;
/*Adding two antennas to sector equipment*/
MOD SECTOREQM: sectorEqmId=0, opMode=ADD, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0,
ant1N=R0A, antType1=RXTX_MODE, ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B, antType2=RXTX_MODE;
/*Changing the transmit and receive mode of the NR cell to 4T4R*/
MOD NRDUCELLTRP: NrDuCellTrpId=0, MaxTransmitPower=300, TxRxMode=4T4R;
/*Adding an NR DU cell coverage item with NR DU Cell TRP ID set to 1, NR DU Cell Coverage ID set to 1,
and Sector Equipment ID set to 0*/
/*Activating the NR cell*/

This section describes how to change the TX/RX mode of an NR cell locally and
remotely.
Prerequisites
The information, hardware and data required for changing the TX/RX mode of an
NR cell are ready.

5G RAN
Context
Procedure
● Local Operation
a. Install an RF module. For details, see the related RRU installation guides.
c. (Optional. Perform this step if the original antennas have less TX and RX
channels than those required by the modified NR cells.) Replace
antennas. For details about the operation, see Antenna Installation.
ii. Back up the current license file to the MAE-Access server.
Run the command.
For example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
FN="LIC_NR_ON.xml";
iii. Import a new license file.
Run the command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_NR_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver data 1 to the base station and activate the data. For details,
see the interactive operation guide Delivering Data to Base
v. Deliver data 2 to the base station and activate the data. For details,
vi. After the data reconfiguration is complete, set the gNodeB

5G RAN

command.
----End

This section describes how to verify the change of the TX/RX mode of an NR cell.
Procedure
command output.
Step 3 Run the LST SECTOR and LST SECTOREQM commands to verify that the sector
antenna configuration information is the same as planned. Then, run the LST
NRDUCELLTRP command to verify that the Transmit and Receive Mode
parameter in the NRDUCellTrp MO is the same as planned.
If the sector antenna configuration information or the Transmit and Receive
Mode parameter in the NRDUCellTrp MO is not the same as planned, perform the
following operations:
● If the reconfiguration is performed by using the MAE-Deployment, check
whether the number of antennas in the sector and the TX/RX mode of cells in
the modified configuration data file are the same as planned:

5G RAN
● If the reconfiguration is performed by using the MML commands, check
whether the number of antennas and the TX/RX mode of NR cells in the script
are correct.
– If they are incorrect, modify the number of antennas, the TX/RX mode of
NR cells in the script. Then, run the MOD SECTOR, MOD SECTOREQM,
and MOD NRDUCELLTRP command to reconfigure Antenna Number,
Transmit and Receive Mode, and Max Transmit Power.
– If they are correct, contact Huawei technical support or dial the Huawei
----End

original state.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.5.5 Changing the Coverage Radius of an NR Cell

the coverage radius of an NR cell.

reconfiguration scheme, and topology changes for changing the coverage radius
of an NR cell.
● The network topology is changed.
● Overshoot coverage occurs on the NR cell.
After the coverage radius of an NR cell is changed, the NR cell automatically
resets for the configuration to take effect. During the reset, the NR cell cannot
provide services.
NOTE
● Increasing the radius of an NR cell will extend its coverage but may cause interference on
neighboring gNodeBs. In this case, network optimization is required.
● Decreasing the radius of an NR cell may change its neighbor relationships and affect UE
handovers. In this case, network optimization is required.
To change the coverage radius of an NR cell, you only need to change Cell Radius
in the NRDUCell MO to the target value.

5G RAN
Topology Changes
N/A

This section describes the engineering preparation for changing the NR cell radius,
including information collection and preparation of hardware, software,
certificates, and data. It also describes the data preparation mode and provides
NR cell information NR DU cell ID and new NR cell radius
N/A
N/A

N/A

N/A
Data Preparation
Prepare the data according to the following table.
Table 1-21 Data preparation for changing the cell radius

ation
1 Modi NRCell Set Cell Radius to the target

fy value.

5G RAN

MAE-Deployment.
NOTE

name of the scenario being "Changing the Coverage Radius of a Cell"). For
script examples.

The MML command configuration script is as follows:
/*Changing the coverage radius of an NR cell to 10000 m*/
MOD NRDUCELL: NRDuCellId=0, CellRadius=10000;

This section describes how to change the coverage radius of an NR cell locally and
remotely.
Prerequisites
Information for changing the coverage radius of an NR cell has been collected,
and configuration data is ready.
Context
Procedure
● Local Operation

5G RAN
N/A
ii. Deliver the configuration data to the base station and activate it. For
iii. After the data reconfiguration is complete, set the gNodeB
command.
----End

This section describes how to verify the change of the coverage radius of an NR
cell.
Procedure


5G RAN

command output.
Step 3 Run the LST NRCELL command to check whether the cell radius is the same as
planned.
If the cell radius is not the same as planned, check whether the parameters in the
script are set correctly.
● If they are incorrect, modify the parameters in the script. Then run the MOD
NRCELL command to change Cell Radius again.
● If they are correct, contact Huawei technical support or dial the Huawei
----End

original state.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.5.6 Changing the NR Cell NR-ARFCNs

the NR Absolute Radio Frequency Channel Numbers (NR-ARFCNs) of an NR cell.

reconfiguration scheme, and topology changes for changing the NR Absolute
Radio Frequency Channel Numbers (NR-ARFCNs) of an NR cell.
● The current NR-ARFCNs of the NR cell are inappropriate.
● The operator re-plans frequency resources.
After the NR-ARFCNs of an NR cell are changed, the NR cell automatically resets
to make the configuration take effect. During the reset, the NR cell cannot provide
services.
Figure 1-16 shows the reconfiguration procedure for changing the NR-ARFCNs of
an NR cell.

5G RAN
Figure 1-16 Reconfiguration procedure for changing the cell NR-ARFCNs
To change neighboring cell information, remove redundant or incorrect

neighboring cells and add new neighboring cells based on the network plan.
Topology Changes
N/A

This section describes the engineering preparation for changing the NR Absolute
Radio Frequency Channel Numbers (NR-ARFCNs) of an NR cell, including
information collection and preparation of hardware, software, certificates, and
data. It also describes the data preparation mode.

NR cell information The NR DU cell ID and new NR-ARFCNs
Neighboring cell After the NR-ARFCNs of an NR cell are changed, delete

information incorrect neighbor relationships and add new neighbor
relationships based on the network plan.

5G RAN
NOTE
adjustment.
N/A
N/A

N/A

N/A
Data Preparation
Table 1-23 Data preparation for changing NR-ARFCNs

on
1 Modify NRDUCell Change Uplink NARFCN and Downlink

NARFCN to target values. Configuration of
the uplink NR-ARFCN is optional.
2 Modify NRCellRelatio ● When the MAE-Deployment is used for

n reconfiguration, cell NR-ARFCNs-related
parameters will be automatically
3 Modify NRExternalNC changed to the target values. No
ell operation is required.
● When MML commands are used for
reconfiguration, manually configure
related parameters.

5G RAN

on
4 Modify NrExternalCell ● When the MAE-Deployment is used for

(LTE MO) reconfiguration, the ARFCNs in the
NrExternalCell MO will be
automatically changed to the target
values on the NR side. Therefore, you
do not need to set these parameters.
reconfiguration, manually change
Downlink ARFCN in the NrExternalCell
MO on the LTE side to the target SSB
ARFCN on the NR side.
● No matter whether the MAE-
Deployment is or MML commands are
used for reconfiguration, you must
check whether the values of the ARFCN
parameters in the NRNFREQ,
NRSCGFREQCONFIG, and NRMFBIFREQ
MOs on the LTE side contain the target
SSB ARFCN on the NR side. If no, add it
to the ARFCN parameters in these MOs
and determine whether the original
ARFCN needs to be removed.
NOTICE
In multi-operator sharing scenarios, pay attention to the constraints between MOs

when changing the NR-ARFCNs of an NR cell. The combination of SsbFreqPos and
SsbDescMethod in the gNBFreqPriorityGroup MO corresponding to
gNBFreqPriorityGroupId in an NRCellOpPolicy MO must be have been configured
in the NRCellFreqRelation or NRDUCell MO corresponding to the NrCellId
parameter in the NRCellOpPolicy MO.

To update the information about external NR neighboring cells at the same time,
you are advised to use the MAE-Deployment-provided "radio data planning file".

5G RAN
NOTE
● The MAE-Deployment-provided "radio data planning file" supports automatic update of the
information about external neighboring cells when NR cell-related parameters are modified.
● To ensure that the associated parameters of the external cells in the current data area are
consistent, choose Advanced > System > Options on the menu bar of the main window.
The setting function is started. On the Cell Parameter Auto-Synchronization Policy tab
page, select Auto synchronize cell parameters in the entire network and click OK. For
details about the cell parameter auto-synchronization policy, see section Setting System
Options in the MAE-Access online help.
The data preparation using the MAE-Deployment-provided "radio data planning

file" is as follows:
1. On the menu bar, choose NR Application > Network Adjustment >
Network Adjustment > Export Radio Network Planning Data. Then, export
planned radio data from the MAE-Deployment to the file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar, choose NR Application > Network Adjustment > Import
Radio Network Planning Data. A dialog box is displayed for you to import
planned radio data. Then, import the data from the file into the MAE-
Deployment
For details about how to import and export a radio data planning file, see
section Importing and Exporting Planned Radio Data in the MAE-Access
online help.

This section describes how to change the NR Absolute Radio Frequency Channel
Numbers (NR-ARFCNs) of an NR cell locally and remotely.
Prerequisites
Information for changing the NR-ARFCNs of an NR cell has been collected, and
configuration data is ready.
Context
Procedure
● Local Operation
N/A

5G RAN
To update the information about external NR neighboring cells at the same
time, you are advised to use the MAE-Deployment-provided "radio data
planning file". Perform the following steps:
a. To prevent alarms from being generated during reconfiguration, set the
gNodeB engineering maintenance mode to expand status.
b. Deliver and activate the configuration on the gNodeB. For details, see the
interactive operation guide Delivering Data to Base Stations and
Activating the Data.
c. After the data reconfiguration is complete, set the gNodeB engineering
maintenance mode to NORMAL.
----End

This section describes how to verify the reconfiguration for changing the NR
Absolute Radio Frequency Channel Numbers (NR-ARFCNs) of an NR cell.
Procedure
Step 2 Run the DSP NRDUCELL command. Verify that NR DU Cell State is Normal for
the NR DU cell.
If NR DU Cell State is DUCELL_INST_UNINSTALL, check the NR cell configuration
or hardware based on the value of NR DU Cell Latest State Change Reason in
the command output.
Step 3 Run the LST NRDUCELL command to check whether the uplink and downlink NR-
ARFCNs of the NR DU cell are the same as planned.
If the uplink or downlink NR-ARFCN of the NR DU cell is not the same as planned,
check whether the uplink or downlink NR-ARFCN in the modified configuration
data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
----End

5G RAN

original state.
Procedure
configuration file.
configuration file.
data.
NOTE

record table.

----End

5G RAN
1.5.7 Changing the NR DU Cell PCI

the physical cell identifier (PCI) of an NR DU cell.

reconfiguration scheme, and topology changes for changing the PCI of an NR DU
cell.
● The network topology is changed.
● A PCI conflict occurs between cells.
After the PCI of an NR cell is changed, the NR DU cell automatically resets for the
configuration take effect. During the reset, the NR cell cannot provide services.
To change the NR cell PCI, you only need to change the value of Physical Cell ID
in the NRDUCell MO to the target value.
NOTE
You are advised to use the MAE-Deployment-provided "radio data planning file" to perform the
reconfiguration. A gNodeB will automatically update the external neighboring cell information
of an NR cell after you reconfigure PCI of the cell by using the radio data planning file.
Topology Changes
N/A

This section describes the engineering preparation for changing the PCI of an NR
DU cell, including information collection and preparation of hardware, software,
certificates, and data. It also describes the data preparation mode.
NR cell information The NR DU cell ID and the new PCI

5G RAN
N/A
N/A

N/A

N/A
Data Preparation
Table 1-25 Data preparation for changing the PCI of a DU cell

on
1 Modify NRDUCell Set Physical Cell ID to the target value.
2 Modify NRExternalNC ● When the MAE-Deployment is used for

ell reconfiguration, PCI-related parameters
of NR cells will be automatically
changed to the target values. No
operation is required.
related parameters.

(LTE MO) reconfiguration, Physical Cell ID in the
NrExternalCell MO will be
value on the NR side. Therefore, you do
not need to set this parameter.
reconfiguration, manually change
Physical Cell ID in the NrExternalCell
MO on the LTE side to the target value
on the NR side.

5G RAN

To update the information about external NR neighboring cells at the same time
when the PCI for the NR DU cell is changed, you are advised to use the MAE-
Deployment-provided "radio data planning file".
NOTE
● The MAE-Deployment-provided "radio data planning file" supports automatic update of the
information about external neighboring cells when NR cell-related parameters are modified.


Deployment
online help.

This section describes how to change the PCI of an NR DU cell locally and
remotely.
Prerequisites
Information for changing the PCI of an NR DU cell has been collected, and
Context
operation and maintenance center (OMC), such as reconfiguring parameters

5G RAN
Procedure
● Local Operation
N/A
To update the information about external NR neighboring cells at the same

time when the PCI for the NR DU cell is modified, you are advised to use the
MAE-Deployment-provided "radio data planning file". Perform the following
steps:

----End

This section describes how to verify the reconfiguration for changing the PCI of an
NR DU cell.
Procedure

the NR DU cell.

the command output.
Step 3 Run the LST NRDUCELL command to check whether the Physical Cell ID is the
same as planned.
If the Physical Cell ID is not the same as planned, check whether the Physical
Cell ID in the modified configuration data file is the same as planned:

5G RAN
----End

original state.
Procedure
configuration file.
configuration file.
data.
NOTE

record table.

5G RAN

----End
1.5.8 Changing the Cell ID

the ID of an NR cell.

reconfiguration scheme, and topology changes for changing the cell ID.
The previous cell ID plan is inappropriate and a new plan is required.
After the cell ID is changed, the NR cell automatically resets to make the
NOTE
If the current cell serves as a neighboring cell of another intra-site cell, the value of Cell ID
cannot be modified.
● MAE-Deployment-based reconfiguration scheme
To change the cell ID, you only need to change the value of Cell ID in the
NRCell and NRDUCell MOs to the target value.
NOTE
You are advised to use the MAE-Deployment-provided "radio data planning file" to
perform the reconfiguration. After the cell ID is changed on the MAE-Deployment, the
gNodeB will automatically update the cell information of the given cell and the external
neighboring cell information of its adjacent cells as long as the option Auto synchronize
cell parameters in the entire network is selected. You can choose Advanced > System >
Options on the menu bar, click the Cell Parameter Auto-Synchronization Policy tab in
the displayed Options dialog box, and select this option.
● MML-based reconfiguration scheme
– Delete the intra-gNodeB cells with the local cell as an intra-frequency
neighboring cell in the NRCellRelation MO.
– Add the intra-frequency neighboring cells with the local cell as a
neighboring cell in the NRCellRelation MO.
NOTE
The previous operations are dedicated to the local gNodeB. If a cell is an external
neighboring cell of other gNodeBs, you need to manually update the Cell ID parameter in
the NRExternalNCell MO.

5G RAN
Topology Changes
N/A

This section describes the engineering preparation for changing the cell ID,

NR cell information The NR cell ID and new cell ID
NR DU cell The NR DU cell ID and new cell ID

information
Neighboring cell The information about intra-frequency neighboring cells

information
N/A
N/A

N/A

N/A
Data Preparation

5G RAN
Table 1-27 Data preparation for changing the cell ID

on
1 Modify NRCell Set Cell ID to the target value.
2 Modify NRDUCell Set Cell ID to the target value.
3 Modify NRCellRelatio ● When the MAE-Deployment is used for

n reconfiguration, cell ID-related
parameters will be automatically
4 Modify NRExternalNC changed to the target values. No
ell operation is required.
related parameters.

(LTE MO) reconfiguration, cell ID-related
parameters on the LTE side will be
6 Modify NrExternalCell automatically changed to the target
Plmn (LTE values on the NR side. No operation is
MO) required.
7 Modify NrNRelations ● When MML commands are used for
hip (LTE MO) reconfiguration, manually change the
values of cell ID-related parameters on
the LTE side to the target values on the
NR side.

To update external neighboring cell information of the other gNodeBs
simultaneously when you change the cell ID, you are advised to use the MAE-
In the case of data preparation using MML commands, prepare MML
configuration scripts based on the preceding data preparation procedure and the
following MML configuration script examples.

5G RAN
NOTE
● The MAE-Deployment-provided Radio data planning file supports automatic update of the
information about the external neighboring cells of other gNodeBs when the cell ID is
changed.
To prepare data by using the MAE-Deployment-provided "radio data planning

file", perform the following steps:

Deployment
online help.

If an intra-frequency neighboring cell exists, remove it first.
/*Removing cell 2 from the NR cell relationship*/
RMV NRCELLRELATION: NRCELLID=2;
/*Modifying the cell ID*/
MOD NRCELL: NRCELLID=0, CELLID=200;
/*Modifying the cell ID*/
MOD NRDUCELL: NRDUCELLID=0, CELLID=200;
/*Adding an NR cell relationship*/
ADD NRCELLRELATION: NRCELLID =1, MCC="460", MNC="20", GNBID=255, CELLID=200;

This section describes the engineering implementation for changing a cell ID.
Prerequisites
Information for changing the cell ID has been collected, and configuration data is
ready.

5G RAN
Context
Procedure
● Local Operation
N/A
To update external neighboring cell information of the other gNodeBs

simultaneously when you change the cell ID, you are advised to use the MAE-
Deployment-provided "radio data planning file". Perform the following steps:

Using MML commands:

b. Run the following commands to back up and export the configuration
file. The configuration file can be used to restore the gNodeB if the
reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
d. After the data reconfiguration is complete, set the gNodeB engineering
----End

5G RAN

This section describes how to verify the reconfiguration for changing the NR cell
ID.
Procedure


command output.
Step 3 Run the LST NRCELL command to check whether the Cell ID is the same as
planned.
If the Cell ID is not the same as planned, check whether Cell ID in the modified
configuration data file is the same as planned:
----End

original state.
Procedure
Step 1 Roll back the reconfiguration data.
● Using MML commands: Rolling back the configuration data using the one-
click blind configuration rollback function
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
For example, DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
For example, ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

5G RAN
NOTE
▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to view the switch setting.
▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.
▪ The start time at which the system can recover data is the time of the last full
database backup, and the end time is the latest time recorded in the incremental
record table.

----End
1.5.9 Changing the NR Cell ID

the ID of an NR cell.

reconfiguration scheme, and topology changes for changing the ID of an NR cell.
The previous NR cell ID plan is inappropriate and a new plan is required.
After the ID of an NR cell is changed, the NR cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.
To change the NR cell ID, you only need to change NR Cell ID in the NRCell MO
to the target value.
NOTE
reconfiguration. After an NR cell ID is changed using the "radio data planning file", the gNodeB
will automatically update information about the external cells of the NR cell.
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for changing the ID of an NR
cell, including information collection and preparation of hardware, software,
NR cell information The original and new NR cell IDs
N/A
N/A

N/A

N/A
Data Preparation
Table 1-29 Data preparation for changing the NR DU cell ID

on
1 Modify NRCell Change the NR Cell ID to the target value.

To update external cell information of the other gNodeBs simultaneously when
you change the NR cell ID, you are advised to use the MAE-Deployment-provided
"radio data planning file".

5G RAN

NOTE
● The MAE-Deployment-provided Radio data planning file supports automatic update of the
information about the external neighboring cells of other gNodeBs when the cell ID is
changed.


Deployment
online help.

If an intra-frequency neighboring cell exists, remove it first.
/*Removing cell 2 from the NR cell relationship*/
RMV NRCELLRELATION: NRCELLID=2;
/*Modifying the NR cell ID*/
RMV NRCELL: NRCELLID=2, CELLID=200;
ADD NRCELL: NRCELLID=11, CELLID=200;
/*Adding an NR cell relationship*/
ADD NRCELLRELATION: NRCELLID =1, MCC="460", MNC="20", GNBID=255, CELLID=200;

This section describes how to change the NR cell ID locally and remotely.
Prerequisites
Information for changing the NR cell ID has been collected, and configuration
data is ready.
Context

5G RAN

Procedure
● Local Operation
N/A
Using the MAE-Deployment:

Using MML commands:

file. The configuration file can be used to restore the gNodeB if the
reconfiguration fails.
----End

This section describes how to verify the reconfiguration for changing the NR cell
ID.

5G RAN
Procedure
command output.
Step 3 Run the LST NRCELL command to check whether the NR Cell ID is the same as
planned.
If the NR Cell ID is not the same as planned, check whether the NR Cell ID in the
modified configuration data file is the same as planned:
----End

original state.
Procedure
information.

5G RAN
NOTE

the rollback.
record table.

----End
1.5.10 Changing the Cell Name

the name of a cell.

reconfiguration scheme, and topology changes for changing the name of a cell.
Application Scenario
The previous cell name plan is inappropriate and a new plan is required.
None
● Change the name of a cell.
● Change the name of an external NR neighboring cell of a neighboring NR
base station.
Topology Change
N/A

This section describes the engineering preparation for changing the cell name,

5G RAN
Table 1-30 Information Collection
NR cell information The old and new cell names
N/A
N/A
License Preparation
N/A

N/A
Data Preparation
The following table lists the data to be prepared.
Table 1-31 Data preparation for changing the cell name

on
1 Modify NRCell Set Cell Name to the target value.
Table 1-32 Data preparation for changing the name of a cell served by a
neighboring base station

on
1 Modify NRExternalNC Set Cell Name to the target value.

ell

5G RAN

To update the external neighboring cell information of other gNodeBs
simultaneously when you change the cell name, you are advised to use the MAE-
NOTE
● The MAE-Deployment can automatic update the information about external neighboring
cells of other gNodeBs in the planned data area when the "radio data planning file" is used
to change the cell name.

Deployment
online help.

This section describes how to change the cell name.
Prerequisites
Information for changing the cell name has been collected, and configuration data
is ready.
Context

5G RAN
Procedure
● Local Operation
N/A
The MAE-Deployment can automatic update the information about external

neighboring cells of other gNodeBs in the planned data area when the "radio
data planning file" is used to change the cell name. Perform the following
steps:

----End

This section describes how to verify the reconfiguration for changing the cell
name.
Procedure
Step 1 Verify that no cell-related alarms are reported, such as ALM-29841 NR Cell
Unavailable, ALM-29842 NR Cell Blocked, and ALM-29847 NR Cell PCI Conflict.
If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900

Series Base Station Alarm Reference.

command output.
Step 3 Run the LST NRCELL command to check whether the Cell Name is the same as
planned.
If the Cell Name is not the same as planned, check whether Cell Name in the
modified configuration data file is the same as planned:

5G RAN
----End

original state.
Procedure
information.
NOTE

the rollback.
record table.

----End
1.5.11 Changing the NR DU Cell Name

the name of an NR DU cell.

reconfiguration scheme, and topology changes for changing the name of an NR
DU cell.

5G RAN
The previous NR DU cell name plan is inappropriate and a new plan is required.
After the name of an NR DU cell is changed, the cell automatically resets to make
the configuration take effect. During the reset, the cell cannot provide services.
To change the NR DU cell name, you only need to change NR DU Cell Name in
the NRDUCell MO to the target value.
NOTE
reconfiguration. After an NR DU cell name is changed using the "radio data planning file", the
gNodeB will automatically update the information about external cells of the NR DU cell.
Topology Changes
N/A

This section describes the engineering preparation for changing the NR DU cell
name, including information collection and preparation of hardware, software,
Table 1-33 Information Collection
NR DU cell The old and new NR DU cell names

information
N/A
N/A
License Preparation
N/A

5G RAN

N/A
Data Preparation
Table 1-34 Data preparation for changing the NR DU cell name

on
1 Modify NRDUCell Set NR DU Cell Name to the target value.

To update the external neighboring cell information of other gNodeBs
simultaneously when you change the NR DU cell name, you are advised to use the
MAE-Deployment-provided "radio data planning file".

NOTE
● The MAE-Deployment can automatic update the information about external neighboring
cells of other gNodeBs in the planned data area when the "radio data planning file" is used
to change the NR DU cell name.


Deployment

5G RAN
online help.

This section describes how to change the NR DU cell name locally and remotely.
Prerequisites
Information for changing the NR DU cell name has been collected, and
Context
Procedure
● Local Operation
N/A
----End

This section describes how to verify the reconfiguration for changing the NR DU
cell name.
Procedure
Step 1 Verify that no NR DU cell-related alarm is reported, such as ALM-29843 NR DU
Cell Simulated Loading Startup and ALM-29874 NR DU Cell Blocked.

5G RAN
the NR DU cell.

the command output.
Step 3 Run the LST NRDUCELL command to check whether the NR DU Cell Name is the
same as planned.
If the NR DU Cell Name is not the same as planned, check whether NR DU Cell
Name in the modified configuration data file is the same as planned:
----End

original state.
Procedure
information.
NOTE

the rollback.
record table.

5G RAN

----End
1.5.12 Changing the TAC

the tracking area code (TAC).

reconfiguration scheme, and topology changes for changing the tracking area
code (TAC).
The previous TAC plan is inappropriate and a new plan is required.
After the TAC of an NR cell is changed, the cell automatically resets to make the
To change the TAC, change Tracking Area Code in the gNBTrackingArea MO to
the target value.
Topology Changes
N/A

This section describes the engineering preparation for changing the gNodeB
tracking area code (TAC), including information collection and preparation of
hardware, software, certificates, and data. It also describes the data preparation
mode.
gNodeB tracking area The new TAC

information

5G RAN
N/A
N/A

N/A

N/A
Data Preparation
Table 1-36 Data preparation for changing the gNodeB TAC

on
1 Modify gNBTrackingA Change the Tracking Area Code to the

rea target value.
2 Modify NRExternalNC ● When the MAE-Deployment is used for

ell reconfiguration, Tracking Area Code in
the NRExternalNCell MO will be
reconfiguration, manually change the
value of Tracking Area Code in the
NRExternalNCell MO to the target
value.

5G RAN

on

(LTE MO) reconfiguration, Tracking Area Code in
the NrExternalCell MO will be
reconfiguration, manually change the
value of Tracking Area Code in the
NrExternalCell MO on the LTE side to
the target value on the NR side.

You are advised to use the MAE-Deployment-provided "radio data planning file".
NOTE

Deployment
online help.

This section describes how to change the tracking area code (TAC) locally and
remotely.
Prerequisites
Information for changing the TAC has been collected, and configuration data is
ready.

5G RAN
Context
Procedure
● Local Operation
N/A
----End

This section describes how to verify the reconfiguration for changing the tracking
area code (TAC).
Procedure
command output.
Step 2 Run the LST GNBTRACKINGAREA command to check whether the Tracking Area
Code is the same as planned.
If the Tracking Area Code is not the same as planned, check whether the
Tracking Area Code in the modified configuration data file is the same as
planned:

5G RAN
----End

original state.
Procedure
information.
NOTE

the rollback.
record table.

----End
1.5.13 Changing the Neighboring Cell Parameters

the neighboring cell parameters.

reconfiguration scheme, and topology changes for changing the neighboring cell
parameters.

5G RAN
The previous neighboring cell parameter plan is inappropriate and a new plan is
required.
After you change the neighboring cell parameters, the handover target cell will be
changed.
To change the neighboring cell parameters, reconfigure the parameters in the
neighboring cell-related managed objects (MOs).
The involved MOs are as follows:
● NRCellRelation
● NRExternalNCell
Topology Changes
N/A

This section describes the engineering preparation for changing the neighboring
cell parameters, including information collection and preparation of hardware,
software, certificates, and data. It also describes the data preparation mode.

Neighboring cell The new parameters in the MOs to be changed

parameters
N/A
N/A

N/A

5G RAN

N/A
Data Preparation
Based on the planned neighboring cell parameters, data to be prepared is listed in
the following table.
Table 1-38 Data preparation for changing neighboring cell parameters
SN Ope MO Category MO Configuration Reference

rati
on
1 Mod NR external NRCellRelation Change the corresponding

ify neighboring parameters to the target
cell NRExternalNCe values.
ll

You are advised to use the MAE-Deployment-provided "radio data planning file".
NOTE

Deployment
online help.

This section describes how to change the neighboring cell parameters locally and
remotely.

5G RAN
Prerequisites
Information for changing neighboring cell parameters has been collected, and
Context
Procedure
● Local Operation
N/A
----End

This section describes how to verify the reconfiguration for changing the
neighboring cell parameters.
Context
Modifying NRCellRelation is used as an example to describe how to verify the
reconfiguration. You can also run the LST commands to check other MOs.
Procedure
Step 1 Run the LST NRCELLRELATION command to verify that the value is the same as
planned.
If the value is not the same as planned, check whether the value in the modified
configuration data file is the same as planned:

5G RAN
----End

original state.
Procedure
information.
NOTE

the rollback.
record table.

----End
1.5.14 Changing the Intra-Frequency A3 Offset

the intra-frequency A3 offset.

5G RAN

reconfiguration scheme, and topology changes for changing the intra-frequency
A3 offset.
The previous intra-frequency A3 offset plan is inappropriate and a new plan is
required.
None
To change the A3 offset for intra-frequency handovers, change the value of Intra-
frequency Handover A3 Offset in the NRCellIntraFHoMeaGrp MO to the target
value.
Topology Changes
N/A

This section describes the engineering preparation for changing the intra-
frequency A3 offset, including information collection and preparation of hardware,
software, certificates, and data. It also describes the data preparation mode.
gNodeB The NR DU cell ID and measurement common

measurement parameter group ID
common parameter
group
Intra-frequency A3 The new intra-frequency A3 offset

offset
N/A

5G RAN
N/A

N/A

N/A
Data Preparation
Table 1-40 Data preparation for changing the intra-frequency A3 offset

on
1 Modify NRCellIntraFH Change Intra-frequency Handover A3

oMeaGrp Offset to the target value.

MAE-Deployment.
NOTE

name of the scenario being "Changing the Intra-Frequency Handover Offset").
For details, see the interactive operation guide 1.11.2 Using the Batch
script examples.

5G RAN

In the following example, the A3 offset for intra-frequency handovers is changed
to 2.
/*Changing the RSRP offset for intra-frequency event A3 to 2*/
MOD NRCELLINTRAFHOMEAGRP: NrCellId=5, IntraFreqHoMeasGroupId=1, IntraFreqHoA3Offset=2,
IntraFreqHoA3Hyst=3, IntraFreqHoA3TimeToTrig=64MS;

This section describes how to change the A3 offset for intra-frequency handovers
locally and remotely.
Prerequisites
Information for changing the A3 offset for intra-frequency handovers has been
collected, and configuration data is ready.
Context
Procedure
● Local Operation
N/A

5G RAN

command.
----End

This section describes how to verify the reconfiguration for changing the A3 offset
for intra-frequency handovers.
Procedure
Step 1 Run the LST NRCELLINTRAFHOMEAGRP command and verify that the Intra-
frequency Handover A3 Offset parameter value is the same as planned.
If the Intra-frequency Handover A3 Offset parameter value is not the same as

planned, check whether the parameter value in the modified configuration data
file is the same as planned:
----End

original state.
Procedure

5G RAN
configuration file.
configuration file.
data.
NOTE

record table.

----End
1.5.15 Changing the NR Cell Power

the power of an NR cell.

reconfiguration scheme, and topology changes for changing the NR cell power.
The NR cell power needs to be changed due to a network plan change.

5G RAN
None
The following figure shows the reconfiguration procedure for changing the NR cell
power.
NOTE
The change should be based on the maximum RRU/AAU transmit power. You can run the DSP
TXBRANCH command to check the maximum RRU transmit power.
Figure 1-17 Reconfiguration procedure for changing the cell NR cell power
Topology Changes
N/A

This section describes the engineering preparation for changing the NR cell power,
NR cell information The NR cell ID and the new NR cell

power
TRP information of an NR DU cell The TRP for an NR DU cell whose

power is to be changed

5G RAN
Sector equipment information The sector equipment information in a

cell whose power is to be changed,
including the maximum power of the
corresponding RF module
NOTE
adjustment.
N/A
N/A

N/A
Data Preparation
Table 1-42 Data preparation for changing the cell power

atio
n
1 Modi NRDUCellTrp Run the MOD NRDUCELLTRP command to

fy change the maximum transmit power to the
target value.

MAE-Deployment.

5G RAN
NOTE

name of the scenario being "Changing the Cell Power"). For details, see the
script examples.

An NR cell is used as an example to describe the MML configuration script used
for data preparation.
/*Changing the maximum transmit power of the NR DU cell TRP to 300*/
MOD NRDUCELLTRP: NrDuCellTrpId=0, MaxTransmitPower =300;

This section describes how to change the NR cell power locally and remotely.
Prerequisites
Information for changing the NR cell power has been collected, and configuration
data is ready.
NOTE
Before using the MAE-Deployment to change the antenna mode and the reference signal power
simultaneously, run the DEA NRCELL command to deactivate the NR cell. Then, activate the
script on the MAE-Deployment.
Context
Procedure
● Local Operation
N/A

5G RAN

command.
----End

This section describes how to verify the NR cell power change.
Procedure


5G RAN

command output.
Step 3 Verify that the changed parameter values are the same as planned.
● For a common cell, run the LST NRDUCELLTRP command to verify that the
maximum transmit power is the same as planned.
If the value is not the same as planned, check whether the maximum transmit
power in the script is correct.
● If it is incorrect, modify the parameter value. Then run the MOD

NRDUCELLTRP command to change the maximum transmit power again.
● If it is correct, contact local Huawei technical support engineers or dial the
Huawei technical support hotline.
----End

original state.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.5.16 Changing the Uplink-Downlink Slot Assignment and

Slot Structure of an NR TDD Cell
This section describes the application scenario, scheme, reconfiguration impact,
engineering preparation, engineering implementation, engineering verification,
and engineering rollback for changing the uplink-downlink slot assignment and
slot structure of an NR TDD cell. The uplink-downlink slot assignment is used to
configure the uplink and downlink timeslots of an NR TDD cell. The slot structure
of an NR TDD cell is used to configure the uplink or downlink symbols and GP of
special subframes. The slot assignment and structure vary with frequency bands.
The modification of uplink-downlink slot assignment and structure for an NR TDD
cell needs to match the corresponding frequency band.

reconfiguration scheme, and topology changes for changing the uplink-downlink
slot assignment and slot structure of an NR TDD cell.
The requirements for data rate in the uplink and downlink vary in different
scenarios.
● After the modification of uplink-downlink slot assignment and slot structure,
service drops occur and the previous preamble format may not match the
new uplink-downlink slot assignment and slot structure, resulting in an NR
cell setup failure.
● If the new uplink-downlink slot assignment and slot structure are different
from those of the intra-frequency neighboring cell under the neighboring
base station, network interference will occur. In this case, change the
configuration of the intra-frequency neighboring NR cell accordingly.

5G RAN
An NR cell will be deactivated when the uplink-downlink slot assignment and slot
structure are changed. You are advised to manually deactivate the NR cell before
changing the configuration and then activate the NR cell manually. Figure 1-18
shows the reconfiguration procedure for changing the uplink-downlink slot
assignment and slot structure of an NR cell.
Figure 1-18 Reconfiguration procedure for changing the uplink-downlink

subframe configuration and timeslot structure of an NR cell
Topology Changes
N/A

This section describes the engineering preparation for changing the uplink-
downlink slot assignment and slot structure of an NR TDD cell, including
information collection and preparation of hardware, software, license file,
certificates, and data. It also provides an example of MML configuration scripts.
Table 1-43 describes the information to be collected before changing the uplink-
downlink slot assignment and slot structure of an NR cell.
NR cell information The RAT, frequency band, uplink-downlink slot

assignment, and slot structure

5G RAN
N/A
N/A

If the currently used license file does not meet the requirements, prepare a new
license file.
Certificate Preparation
N/A
Data Preparation
Prepare data according to the following instructions:
1. Deactivate the NR cell.
2. Modify the NRDUCell MO to change Slot Assignment and Slot Structure to
the target value.
NOTE
Slot Assignment and Slot Structure must be consistent for all cells on the baseband
processing unit serving the to-be-adjusted cell.
3. Activate the NR cell.
Data preparation can be performed using the MAE-Deployment or MML
commands. The MAE-Deployment-based data preparation is preferable in this
scenario. You can configure base stations in batches using the MAE-Deployment
batch reconfiguration mode or configure a single base station by using the MAE-
Deployment graphical user interface (GUI). The three data preparation modes are
as follows:
name of the scenario being "Changing the Uplink-Downlink Subframe
Configuration (TDD)). For details, see the interactive operation guide 1.11.2
Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
script examples.

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly change the
uplink-downlink subframe configuration.

5G RAN
/*Deactivating the NR cell*/

/*Changing the uplink-downlink slot assignment of the NR cell to 4:1 slot assignment*/
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_TDD, SlotAssignment=4_1_DDDSU,SlotStructure=SS1 ;

This section describes how to change the uplink-downlink slot assignment and slot
structure of an NR cell locally and remotely.
Prerequisites
The information required for changing the uplink-downlink slot assignment and
slot structure of an NR cell is ready.
Context
Procedure
● Local Operation
N/A
the gNodeB engineering maintenance mode to expansion mode
before you perform the reconfiguration.
For detailed operations, see 1.11.1 Setting the gNodeB
Maintenance Mode.
ii. Deliver the data prepared in Data Preparation to the base station
and activate the data on the base station. For details, see the
iii. After the data reconfiguration is completed, set the gNodeB
Maintenance Mode.
– Using MML commands
the gNodeB engineering maintenance mode to expansion mode
before you perform the reconfiguration.
ii. Use the MAE-Access to deliver the batch configuration scripts

5G RAN
iii. After the data reconfiguration is completed, set the gNodeB

Maintenance Mode.
----End

This section describes how to verify an NR cell's uplink-downlink slot assignment
and slot structure change.
Procedure
Step 1 Run the DSP NRCELL command to verify that Cell Available State is Available.
If Cell Available State is Unavailable, check the NR cell configuration, NR cell

reference signal power configuration, or hardware based on the value of Cell
Latest State Change Reason in the command output.
Step 2 Run the LST NRDUCELL command to verify that Slot Assignment is the same as
planned.
Step 3 Verify that no NR cell-related alarm is reported, for example, ALM-29841 NR Cell
Unavailable.
----End

the original state.
Procedure

----End
1.5.17 Adjusting the Association Relationships Between NR

Cells and RF Modules
This section describes how to adjust the association relationships between NR cells
and RF modules, including scheme overview, engineering preparation, engineering
implementation, engineering verification, and engineering rollback

5G RAN

reconfiguration scheme, and topology changes for adjusting the association
relationships between NR cells and RF modules.
The binding relationships between NR cells and sector equipment are inconsistent
with the planned ones.
NR cell services become unavailable during the adjustment of association
Figure 1-19 shows the reconfiguration procedure for adjusting the association
NOTE
If the baseband processing unit where the cell to be adjusted is UBBPfw, the step of
deactivating cells in the following procedure refers to deactivating all cells on the UBBPfw.
Figure 1-19 Reconfiguration procedure for adjusting the association relationships

between NR cells and RF modules
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for adjusting the association
relationships between NR cells and RF modules, including information collection
and preparation of hardware, software, certificates, and data. It also describes the
data preparation mode and provides MML configuration script examples.

Sector information The cabinet number, subrack number, slot number, and
channel number of a sector antenna
Sector equipment The cabinet number, subrack number, slot number,

information channel number, and TX/RX mode of sector equipment
TRP information of The ID, maximum transmit power, and TX/RX mode of
an NR DU cell sector equipment
NR cell information Basic information about NR cells, such as the frequency

band and duplex mode.
N/A
N/A

N/A
Data Preparation

5G RAN
Table 1-45 Data preparation for adjusting the association relationships between
cells and RF modules
SN Operat MO Configuration Reference

ion
1 Deactiv NRCell -
ate
2 Modify NRDUCellCov Adjust the binding relationships between

erage NRDUCellCoverage and sector equipment.
Description.
4 Activat NRCell -
e

MAE-Deployment.
NOTE

name of the scenario-specific template being "Adjusting the Relation Between
Cell and RRU"). For details, see the interactive operation guide 1.11.2 Using
the Batch Reconfiguration Mode of the MAE-Deployment to Prepare
Data.
script examples.

In the following example, the association relationships between cells 0 and 1 and
RF modules are adjusted.
/*Deactivating the NR cells*/
/*Modifying the association relationships between the TRPs for NR DU cells and the sector equipment*/

5G RAN
MOD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=1,SectorEqmId=0;

MOD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=1,SectorEqmId=1;
/*Activating the NR cells*/

This section describes how to adjust the association relationships between NR cells
and RF modules locally and remotely.
Prerequisites
Information for adjusting the association relationships between NR cells and RF
modules has been collected, and hardware, software, and configuration data are
ready.
Context
Procedure
● Local Operation
N/A

ii. Back up the current license file to the MAE-Access server.
Run the command.
For example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
FN="LIC_NR_ON.xml";
Run the command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_NR_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deactivate the NR cell.
Run the DEA NRCELL command.
For example: DEA NRCELL: NrCellId=0;

5G RAN
v. Deliver the configuration data to the base station and activate it. For
vi. Activate the cell.
For example: ACT NRCELL: NrCellId=0;
vii. After the data reconfiguration is complete, set the gNodeB
command.
iii. Deactivate the NR cell.
Run the DEA NRCELL command.
For example: DEA NRCELL: NrCellId=0;
v. Activate the NR cell.
For example: ACT NRCELL: NrCellId=0;
vi. After the data reconfiguration is complete, set the gNodeB
----End

This section describes how to verify that the adjustment of association
relationships between NR cells and RF modules is successful.
Procedure

5G RAN

command output.
----End

original state.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.6 Base Station Data Reconfigurations

This chapter describes how to reconfigure base station data in typical scenarios.
1.6.1 Adding a Neighboring Base Station for a gNodeB (NSA

Networking)
implementation, engineering verification, and engineering rollback for adding a
neighboring base station for a gNodeB.

reconfiguration scheme, and topology changes for adding a neighboring base
station for a gNodeB.
The capacity or coverage of the base station cannot meet the requirement and
therefore a neighboring base station is required.
None
When adding a neighboring base station for the gNodeB, you must configure the
information about X2 self-setup. Then, X2 self-setup will be triggered when a

5G RAN
dual-connectivity (DC) service in non-standalone (NSA) networking is performed

for the first time.
Figure 1-20 shows the reconfiguration procedure for adding a neighboring base
station for the gNodeB. Determine the reconfiguration scheme according to the
following table.

If... Then...
A new device IP address (old model)/ Add a device IP address (old model)/
IPv4 address (new model)/IPv6 IPv4 address (new model)/IPv6
address (new model) is used for address (new model).
connection with the new base station
No route is available from the local Add a route from the local gNodeB to
gNodeB to the newly added base the newly added base station.
station
SCTP parameters for the new X2 link Add an SCTP parameter template.
are different from those for other links
Old Model
The following figure shows the configuration procedure for adding a neighboring
base station when the TRANSCFGMODE parameter in the GTRANSPARA MO is
set to OLD:

5G RAN
Figure 1-20 Configuration procedure for adding a neighboring base station (in the
old model)
The following figure shows the configuration procedure for adding a neighboring
base station when the TRANSCFGMODE parameter in the GTRANSPARA MO is
set to NEW:

5G RAN
Figure 1-21 Configuration procedure for adding a neighboring base station (in the
new model)
Topology Changes
If an X2 link from the gNodeB to an anchor base station is added, the topology of
the gNodeB will change. Figure 1-22 shows the topologies before and after the
reconfiguration.

5G RAN

This section describes the engineering preparation for adding a neighboring base
station for a gNodeB, including information collection and preparation of
hardware, software, certificates, and data. It also describes the data preparation
mode.
Local SCTP port -

number
Routing information ● Local device IP address (old model)/IPv4 address (new

of the X2 link model)/IPv6 address (new model) and next-hop IP
address
● IP address of the peer base station or the gateway
address
Prepare the hardware listed in Table 1-48 before reconfiguration.

5G RAN
Hardware Description
Base station All devices in a base station
N/A

N/A

N/A
Data Preparation
Old Model
When the TRANSCFGMODE parameter in the GTRANSPARA MO is set to OLD:
Table 1-49 Data preparation for adding a neighboring base station

on
1 Add IPv4: DEVIP For details about parameter settings, see

IPv4 Transmission Feature Parameter
Description.
2 Add IPv4: IPRT/ For details about parameter settings, see

SRCIPRT IPv4 Transmission Feature Parameter
Description.
To simplify configurations when one
device IP address corresponds to multiple
destination IP addresses, you are advised
to configure the source IP route.
3 Modify gNBX2SonCo Select the X2SON_SETUP_SWITCH option

nfig of the X2 SON Configuration Switch
parameter.
4 Add SCTPTEMPLA For details about parameter settings, see

TE X2 and S1 Self-Management in NSA
Networking Feature Parameter
5 Add SCTPHOST Description.

5G RAN

on
6 Add USERPLANEH
OST
7 Add EPGROUP
8 Add gNBCUX2
9 Add NRExternalNC Add information about the new

ell neighboring base station based on actual
conditions.
10 Add NRCellRelatio
n
When the TRANSCFGMODE parameter in the GTRANSPARA MO is set to NEW:
Table 1-50 Data preparation for adding a neighboring base station

on
1 Add IPv4: For details about parameter settings, see

IPADDR4 IPv4 Transmission Feature Parameter
IPv6: Description.
IPADDR6
2 Add IPv4: For details about parameter settings, see

IPROUTE4/ IPv4 Transmission Feature Parameter
SRCIPROUTE4 Description.
IPv6: To simplify configurations when one IPv4
IPROUTE6 address maps multiple destination IP
addresses, you are advised to configure
the source IP route.
3 Modify gNBX2SonCo Select the X2SON_SETUP_SWITCH option

nfig of the X2 SON Configuration Switch
parameter.
4 Add SCTPTEMPLA For details about parameter settings, see

TE X2 and S1 Self-Management in NSA
Networking Feature Parameter
5 Add SCTPHOST Description.
6 Add USERPLANEH
OST
7 Add EPGROUP
8 Add gNBCUX2

5G RAN

on
9 Add NRExternalNC Add information about the new

ell neighboring base station based on actual
conditions.
10 Add NRCellRelatio
n
NOTE
In NSA networking, a gNodeB communicates with its anchor base station through the X2
link.
In NSA networking, the neigboring base station of a gNodeB must be another gNodeB.
Therefore, the NRExternalNCell and NRCellRelation MOs need to be added.

commands. You can configure base stations in batches using the MAE-Deployment
batch reconfiguration mode or configure a single base station using the MAE-
Deployment GUI. The data preparation modes are described as follows:
NOTE

name of the scenario-specific template being "Adding a Neighboring gNodeB
(Old Mode)" or "Adding a Neighboring gNodeB (New Mode)"). For details,
see the interactive operation guide 1.11.2 Using the Batch Reconfiguration
script examples.

The following part uses the scenario where a device IP address, an IP route, and
an SCTP parameter template need to be added as an example to describe the
MML configuration for setting up an X2 link during neighboring base station
addition. Parameter settings for configuring neighboring cells are not provided
here.
Old Model
When the TRANSCFGMODE parameter in the GTRANSPARA MO is set to OLD:

5G RAN
/*Adding a device IP address used for communication with the new base station*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.1.203", MASK="255.255.255.0";
/*Adding an IP route from the gNodeB to the new base station*/
ADD IPRT: RTIDX=3, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.1.1", MTUSWITCH=OFF;
/*Selecting the X2SON_SETUP_SWITCH option of the X2 SON Configuration Switch*/
MOD GNBX2SONCONFIG: X2SonConfigSwitch=X2SON_SETUP_SWITCH-1;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=16, IPVERSION=IPv4, SIGIP1V4=" 192.168.1.203",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=1600, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=16, IPVERSION=IPv4, LOCIPV4="192.168.1.203",
IPSECSWITCH=DISABLE;
/*Adding an endpoint group and then adding the user-plane host and the SCTP host to the endpoint group*/
ADD EPGROUP: EPGROUPID=16;
ADD SCTPHOST2EPGRP: EPGROUPID=16, SCTPHOSTID=16;
ADD UPHOST2EPGRP: EPGROUPID=16, UPHOSTID=16;
/*Adding a gNBCUX2 object and configuring its relationship with the endpoint group*/
ADD GNBCUX2: GNBCUX2ID=1, CpEpGroupId=16, UpEpGroupId=16;
New Model
When the TRANSCFGMODE parameter in the GTRANSPARA MO is set to NEW:
/*Setting the attributes of an Ethernet port*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface for the Ethernet port*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
/*Adding an IPv4 address used for communication with the new base station*/
ADD IPADDR4: ITFID=0, IP="192.168.1.203", MASK="255.255.255.0";
/*Adding an IPv6 address with IPv6 Address ID set to 0, Interface ID set to 0, IPv6 Address set to
2001:DB8::1, and Prefix Length set to 32*/
ADD IPADDR6: IPADDR6ID="0", ITFID=0, IPV6="2001:DB8::1", PFXLEN=32;
/*Adding an IP route from the gNodeB to the new base station*/
ADD IPROUTE4: RTIDX=3, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.1.1", MTUSWITCH=OFF;
/*Selecting the X2SON_SETUP_SWITCH option of the X2 SON Configuration Switch*/
MOD GNBX2SONCONFIG: X2SonConfigSwitch=X2SON_SETUP_SWITCH-1;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=16, IPVERSION=IPv4, SIGIP1V4=" 192.168.1.203",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=1600, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=16, IPVERSION=IPv4, LOCIPV4="192.168.1.203", IPSECSWITCH=DISABLE;
/*Adding an endpoint group and then adding the user-plane host and the SCTP host to the endpoint group*/
ADD EPGROUP: EPGROUPID=16;
ADD SCTPHOST2EPGRP: EPGROUPID=16, SCTPHOSTID=16;
ADD UPHOST2EPGRP: EPGROUPID=16, UPHOSTID=16;
/*Adding a gNBCUX2 object and configuring its relationship with the endpoint group*/
ADD GNBCUX2: GNBCUX2ID=1, CpEpGroupId=16, UpEpGroupId=16;

This section describes how to add a neighboring base station locally and remotely.
Prerequisites
The information and data required for adding a neighboring base station are
ready.

5G RAN
Context
Procedure
● Local Operation
N/A
command.
----End

This section describes how to verify the addition of a neighboring base station.

5G RAN
Procedure
Step 1 Enable a UE to perform the network accessing test and initiate an NSA DC service
to the newly added neighboring base station. After the DC service is succeeded,
run the DSP GNBCUX2INTERFACE command. Verify that the value of gNodeB CU
X2 Interface State is Normal.
If the value is not normal, perform the following operations:
1. Check whether the device IP address of the neighboring base station can be
pinged from the device IP address of the X2 interface.
– If the IP address cannot be pinged, go to Step 1.2.
– If the IP address can be pinged, go to Step 1.3.
2. Check the SCTP link configuration, including the IP route from the local
gNodeB to the neighboring base station, and the Ethernet port mode and rate
of the local gNodeB. The Ethernet port mode and rate of the local gNodeB
need to be the same as those of the neighboring base station.
– If the configuration is incorrect, modify the configuration.
– If the configuration is correct, go to Step 1.4.
3. Check whether the value of Peer SCTP Port No. for the SCTP link is the actual
SCTP port number of the neighboring base station.
– If they are not the same, modify the configuration.
– If they are the same, go to Step 1.4.
4. Check the configurations of the devices between the local gNodeB and the
neighboring base station.
– If the configurations or connections are incorrect, modify the
configurations or reconnect the devices.
– If the configurations or cable connections are correct, contact Huawei
----End

original state.
Procedure
configuration file.

5G RAN

configuration file.
data.
NOTE

record table.

----End
1.6.2 Changing the Base Station Name

the base station name.

reconfiguration scheme, and topology changes for changing the base station
name.
The previous base station name plan is inappropriate and a new plan is required.
None

5G RAN
Rename base stations on the MAE-Access by modifying NE attribute in batches.
Topology Changes
N/A

This section describes the engineering preparation for changing the base station
name, including information collection and preparation of hardware, software,

Base station The gNodeB ID, the original base station name, and the
information new base station name
N/A
N/A

N/A

N/A
Data Preparation
Prepare the IDs, original names, and new names of base stations to be renamed.

N/A

This section describes how to change the base station name locally and remotely.

5G RAN
Prerequisites
Information for changing the base station name has been collected, and
Context
Procedure
● Local Operation
N/A
Using the MAE-Access:

b. Open the Batch Modify NEs window.
On the main menu, choose Topology > Batch Modify NEs to open the
Batch Modify NEs window.
c. In the Batch Modify NEs window, click the check box before the base
station to be renamed, click Query in the lower left corner of the
window. After information about the base station is displayed, click
Export in the lower right corner of the window to export the attribute file
to the local PC. The attribute file is named similar to the following: Batch
Modify NEs_20190514_110441.csv.
d. Open the attribute file, change the base station name in the Name
column to the new name, and save the attribute file as a new one with
another name.
e. Click Import in the lower right corner of the Batch Modify NEs window
to import the renamed attribute file.
f. On the main menu of the MAE-Deployment, choose Area Management
> Current Area > Synchronize NEs to synchronize base station
information to the current data area.
g. On the main menu of the MAE-Deployment, choose Area Management
> Planned Area > Synchronize Planned Area NEs to synchronize base
station information to the planned data area.
h. After the data reconfiguration is complete, set the gNodeB engineering
----End

5G RAN

This section describes how to verify the reconfiguration for changing the base
station name.
Procedure
Step 1 Run the LST GNODEBFUNCTION command to check whether the gNodeB
Function Name is the same as planned.
● If it is not the same as planned, perform the operations in Engineering
Implementation again. If the problem persists, contact Huawei technical
support or dial the Huawei technical support hotline.
● If it is the same as planned, the base station is successfully renamed.
----End

If the name of a renamed base station needs to be changed back, the base station
name can be rolled back to its original name.
Procedure
Step 1 Import the base station attribute file before renaming the base station name back
to its original name by referring to e in Engineering Implementation.
----End
1.6.3 Changing the gNodeB ID

the gNodeB ID.

reconfiguration scheme, and topology changes for changing the gNodeB ID.
The previous gNodeB ID plan is inappropriate and a new plan is required.
After the gNodeB ID is changed, the MAE-Deployment activates the changed data
on the live network. When the activation takes effect, the application resets to
make the reconfiguration take effect. During the reset, the base station cannot
provide services.

5G RAN
To change a gNodeB ID, you need to change the gNodeB ID in the
gNodeBFunction MO to the target value.
If the gNodeB ID parameter in any of the following MOs configured on a
neighboring base station references the gNodeB ID parameter of this gNodeB, the
gNodeB ID parameters in these MOs are accordingly changed to the target value:
● NRExternalNCell
● NRCellRelation
Topology Changes
N/A

This section describes the engineering preparation for changing the gNodeB ID,

Base station The original gNodeB ID and new gNodeB ID

information
N/A
N/A

N/A

N/A
Data Preparation
Prepare data according to the following instructions:

5G RAN
Table 1-53 Data preparation for changing the gNodeB ID

tion
1 Modify gNodeBFuncti Set gNodeB ID to the target value.

on
2 Modify NRExternalNC The value of gNodeB ID is accordingly

ell changed to the target value.
3 Modify NRCellRelatio
n
4 Modify NCellPlmnList Set gNodeB ID Length on the LTE side to

(LTE MO) the target value on the NR side.

(LTE MO) reconfiguration, base station ID-related
parameters on the LTE side will be
6 Modify NrExternalCell automatically changed to the target
Plmn (LTE values on the NR side. No operation is
MO) required.
7 Modify NrNRelations ● When MML commands are used for
hip (LTE MO) reconfiguration, manually change the
values of base station ID-related
parameters on the LTE side to the target
values on the NR side.

You are advised to use the MAE-Deployment-provided "ID/Name modification".
Data preparation of this method is as follows:
NOTE
● To prepare data using the MAE-Deployment, choose MAE-Deployment > Advanced >
System > Options. In the displayed Options dialog box, choose Cell Parameter Auto-
Synchronization Policy in the left pane first and then select the check box Auto
synchronize cell parameters in the entire network in the right pane. Then, click OK.
1. On the menu bar, choose NR Application > Network Adjustment > Export
ID/Name Adjustment Data. Then, export the gNodeB names and IDs, and
cell and local cell IDs and names to a file.
2. In the ID Modification of gNodeB sheet of the file, change gNBId of the
base station to the target value. Then, save the modification and close the
file.

5G RAN
ID/Name Adjustment Data Then, import the data from the file into the
MAE-Deployment
NOTE
If some neighboring base stations of the base station are not provided in the planned area
during the data import, a prompt indicating that NEs are missed will be displayed on the
MAE-Deployment and provides the NE names because the Auto synchronize cell
parameters in the entire network check box has been selected. In this case, choose Area
Management > Planned Area > Add Planned Area NEs as prompted to add the NEs
requiring parameter synchronization to the planned area. Then, repeat steps 1 to 3.
For detailed import and export operations, see section Importing and Exporting
Names and IDs in the MAE-Access online help.
NOTE
If the reconfiguration is performed using MML commands, directly modify the configuration of
related MOs. For details about how to modify the configuration of related MOs, see 3900 &
5900 Series Base Station MML Command Reference.

This section describes how to change the gNodeB ID locally and remotely.
Prerequisites
Information for changing the gNodeB ID has been collected, and configuration
data is ready.
Context
Procedure
● Local Operation
N/A

5G RAN
----End

This section describes how to verify the reconfiguration for changing the gNodeB
ID.
Procedure
Step 1 Run the LST GNODEBFUNCTION command to check whether the gNodeB ID are
the same as planned.
If the gNodeB ID is not the same as planned, check whether the gNodeB ID in
the modified configuration data file is the same as planned.
Step 2 Run the LST NREXTERNALNCELL command on the neighboring base station to
check whether the gNodeB ID is the same as planned.
Step 3 Run the LST NRCELLRELATION command on the neighboring base station to
check whether the gNodeB ID is the same as planned.
----End

5G RAN

original state.
Procedure
For detailed operations using the MAE-Deployment to roll back configuration
data, see the interactive operation guide Rolling Back Configuration Data.
----End
1.7 Device Data Reconfigurations

This section describes how to reconfigure gNodeB device data in typical scenarios.
1.7.1 Replacing the Main Control Board When No SeGW Is

Deployed
implementation, engineering verification, and engineering rollback for replacing a
UMPT of a different model in non-secure networking scenarios.

reconfiguration scheme, and topology changes for replacing a main control board.
A main control board needs to be replaced if it cannot meet service requirements.
The transmission interface capabilities and attributes vary with the main control
board types. Therefore, during board replacement, reconfigure data based on
different schemes.
After replacing the main control board, you must power off and power on the
base station to make the configuration take effect. During the operation, the base
station cannot provide services.

5G RAN
NOTE
After the main control board is replaced, the Media Access Control (MAC) address of the board
is changed. If the MAC address is used by the transport network, inform the transport network
maintenance personnel of the change and ask them to modify the configurations.
After the main control board is replaced, the default password of the default LMT account used
for locally logging in to base stations varies between versions. For details, see section "Logging
In to and Logging Out of the LMT" in 3900 & 5900 Series Base Station LMT User Guide.
Table 1-54 Reconfiguration scheme

Replaceme Transmission Transmission Transmission Board Type
nt Scheme Ports Before Ports After Port Reconfigurati
Replacement Replacement Adjustmentb on
UMPTe- Electrical ports Electrical ports Adjustment is Change the

>UMPTg/ 0 and 2 0 and 2 not required. value of the
UMPTga Board
Optical ports 1 Optical ports 1 Adjustment is Specification
and 3 and 3 not required. parameter to
UMPTg/
UMPTga.
UMPTga- Electrical ports Electrical ports Adjustment is Change the

>UMPTg 0 and 2 0 and 2 not required. value of the
Board
UMPTg.
Topology Changes
N/A

This section describes the engineering preparation for replacing a main control
board when no SeGW is deployed, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode.

5G RAN

Configuration data The latest configuration data that is manually exported

file of the original before the reconfiguration. For details, see Exporting
main control board Deployment Lists and Configuration Files of Base
Stations in 3900 & 5900 Series Base Station Initial
Configuration Guide.

If... Then...
A UMPTe needs to be Prepare a UMPTg/UMPTga.

replaced with a
UMPTg/UMPTga
A UMPTga needs to Prepare a UMPTg.

be replaced with a
UMPTg
If the version of the new main control board is different from that of the main
control board to be replaced, collect information about the software version of the
main control board to be replaced.

Keep a new license ready if no license file is loaded to the new main control
board, the control items in the license file cannot meet service requirements, or
the license has expired.

N/A
Data Preparation
Data to be prepared is listed in the following table.

5G RAN
Table 1-57 Data preparation for replacing a main control board
Chan SN Oper MO Configuration Reference

ge ation
Mod
el
Repla 1 Modi MPT Set the Board Specification parameter

ce fy to UMPTg/UMPTga.
the
UMP
Te
with
a
UMP
Tg/
UMP
Tga.

ce a fy to UMPTg.
UMP
Tga
with
a
UMP
Tg.

Use the "Export/Import MPT and Port No. Adjustment Data" mode and batch
reconfiguration mode on the MAE-Deployment. The "Export/Import MPT and Port
No. Adjustment Data" mode is recommended.
● The procedure for the "Export/Import MPT and Port No. Adjustment Data"
mode is as follows:
a. On the MAE-Deployment menu bar, choose NR Application > Network
Adjustment > Export MPT and Port No. Adjustment Data to start the
data export.
b. Select a base station version and base stations to be reconfigured, and
then export the related data.
c. Enter the new MPT board type and new port number in the exported file
based on the plan.
d. On the MAE-Deployment menu bar, choose NR Application > Network
Adjustment > Import MPT and Port No. Adjustment Data to start the
data import.
e. Import the modified file.
● Use the batch reconfiguration mode of the MAE-Deployment (with the name
of the scenario-specific template being "Replacing the Main Control Board
When No SeGW Is Deployed"). For details, see the interactive operation guide

5G RAN
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to

Prepare Data.
NOTE
● Before using the MAE-Deployment to prepare data, ensure that data in the planned
data area is consistent with that in the current data area. If the data is inconsistent, you
can choose Area Management > Planned Area > Synchronize NEs from the menu bar
to synchronize data from the current data area to the planned data area. Then, perform
the following operations.
● You are advised to use the MAE-Deployment, which supports automatic update of the
corresponding port number in the associated MOs when a port number of the main
control board is changed. For details, see iMaster MAE Product Documentation >
Operation and Maintenance > MAE-Deployment Operation and Maintenance >
MAE-Deployment Guidelines > NR Application Management > gNodeB Related
Operations > Changing Base Station MPT Boards and Ports.

This section describes how to replace a main control board locally and remotely.
Prerequisites
Hardware, software, license file, and configuration data for replacing a main
control board are ready.
Context
Replacing a main control board requires cooperation of remote and local
operations. Figure 1-23 shows the procedure for replacing a main control board.

5G RAN
Figure 1-23 Procedure for replacing a main control board
Procedure
Step 1 (Remote operation) Set the gNodeB maintenance engineering mode to the
expand status.
To prevent alarms from being generated during reconfiguration, set the gNodeB
engineering maintenance mode to the expand status before you perform the
reconfiguration.
For detailed operations, see 1.11.1 Setting the gNodeB Maintenance Mode.
Step 2 Back up the license file and configuration data file of the current main control
board.

5G RAN
● (Remote operation) Use the MAE-Access to back up the license file and
configuration data file. The files can be used for restoring the base station to
the pre-reconfiguration status if the reconfiguration fails.
a. Back up the license file in use to the MAE-Access server.
Run the ULD LICENSE command.
For example, INS LICENSE:MODE=IPV4, IP="10.161.18.69",
FN="LIC_LTE_ON.xml";
b. Run the following commands on the MAE-Access to back up and export
the configuration file. The configuration file can be used to restore the
base station to the pre-reconfiguration status if the reconfiguration fails.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
● (Local operation) Use the LMT to back up the license file and configuration
data file. In scenarios where configuration data is not modified, the files are
used for data activation on the LMT.
a. Start the FTP server.
b. Back up the license in use to the LMT PC.
Example: ULD LICENSE: MODE=IPV4, IP="192.169.2.16", USR="admin",
PWD="*****", DIR="ftproot/", FN="D:\FTP",
FN="lic_21021127229TAA016583_1396364568622_1.xml";
c. Back up the configuration data file and export the file to the LMT PC. The
save path is the FTP server directory set in Step 2.a (local operation).
i. Run the BKP CFGFILE command to back up the configuration data
file.
ii. Run the ULD CFGFILE command to export the configuration data
file.
Step 3 (Remote operation) Synchronize data to the planned data area.

● If configuration data does not need to be modified, synchronize the data to
the planned data area first. On the menu bar of the MAE-Deployment, choose
Area Management > Planned Area > Synchronize Planned Area NEs to
synchronize the data in the current data area to the planned data area.
● If the batch reconfiguration function of the MAE-Deployment is used to
reconfigure data, data synchronization is not required. Otherwise, the
reconfigured data will be replaced by the original data after synchronization.
Step 4 (Local operation) Power off the base station and remove the main control board
to be replaced.
Step 5 (Local operation) Install the new main control board and power on the base
station.

5G RAN
Step 6 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Remove the original base station from the main topology.
● On the menu bar of the MAE-Access, choose Topology > Main Topology.
● Right-click the base station to be removed and choose Delete from the
shortcut menu.
● In the displayed Confirm dialog box, click Yes.
● In the displayed Deletion Result dialog box, verify that Result is Succeeded,
and then click Close.
using the MAE-Access.) Export the base station deployment list and configuration
data file.
For details, see step 6 in References > Exporting Deployment Lists and
Configuration Files of Base Stations in 3900 & 5900 Series Base Station
Commissioning Guide. Click Switch to the Auto Deployment window. The
system automatically switches to the auto-deployment window, creates a
commissioning task, and adds the base station to the main topology.
NOTE
Deployment lists are required if configuration data is to be activated using the MAE-Access.
The deployment lists must be exported by using the MAE-Deployment.
Step 8 (Remote operation) Check whether the transport network supports automatic
establishment of the OM channel.
To learn the requirements for the transport network to support automatic

establishment of the OM channel, see Commissioning a Newly Deployed Base
Station > MAE-based Commissioning > Preparation > Checking a Transport
Network in 3900 & 5900 Series Base Station Commissioning Guide.
Step 9 Activate the configuration data.
When activating the configuration data, you need to activate the software for the
old main control board if the software versions of the old and new main control
boards are different. If the license needs to be updated, you must use the new
commercial license file.
● (Remote operation) Activate the configuration data on the MAE-Access and

MAE-Deployment.
a. Upload the original base station's software package to the MAE-Access
server. For details, see Commissioning a Newly Deployed Base Station
> MAE-based Commissioning > Preparation > Uploading the Software
Package in 3900 & 5900 Series Base Station Commissioning Guide.
b. Upload the license file to the MAE-Access server. For details, see
Commissioning a Newly Deployed Base Station > MAE-based
Commissioning > Preparation > Uploading a Commissioning License
(When LTE/NR Services Are to Be Enabled) in 3900 & 5900 Series Base
Station Commissioning Guide.
c. Bind the ESN.
A commissioning task has been created in Step 7. Select this
commissioning task of replacing the main control board from the

5G RAN
commissioning task list. Double-click the cell recording the ESN and
change the value to the current ESN of the base station.
d. Start the commissioning task. For details, see Commissioning a Newly
Deployed Base Station > MAE-based Commissioning > Preparation >
Starting an NE Commissioning Task in 3900 & 5900 Series Base Station
Commissioning Guide.
e. Check whether the gNodeB is working properly. For details, see
Commissioning > Remote Operations > Acquiring an NE
Commissioning Verification Report in 3900 & 5900 Series Base Station
f. Verify that the commissioning task is completed. For details, see
Commissioning > Remote Operations > Confirming that Auto
Deployment Tasks Are Completed in 3900 & 5900 Series Base Station
● (Local operation) Activate the configuration data on the LMT.
a. Log in to the LMT and disable the DHCP function. For details, see
Commissioning a Newly Deployed Base Station > LMT+MAE-based
Commissioning > Local Operations > Logging In to the LMT and
Disabling the DHCP Function in 3900 & 5900 Series Base Station
b. Configure the FTP server. If the FTP server to be configured is provided by
a third party or does not have a Huawei-issued device certificate, set the
FTPCLT.ENCRYMODE parameter to Auto.
c. Download and activate the software and configuration data and install
the license file. For details, see Commissioning a Newly Deployed Base
Station > LMT+MAE-based Commissioning > Local Operations >
Loading the Software, Data Configuration File, and Commissioning
License by Using the LMT in 3900 & 5900 Series Base Station
NOTE
To locally log in to the LMT after configuration data is activated, use the local maintenance
IP address of the old main control board but the login account and password for the new
main control board.
using the MAE-Access.) Delete the commissioning task on the MAE-Access.
1. On the MAE-Access, choose SON > Auto Deployment to open the Auto
Deployment window.
2. Right-click the commissioning task to be deleted and choose Delete from the
shortcut menu.
3. In the displayed confirmation dialog box, click Yes.
normal status on the MAE-Access.
After the data reconfiguration is completed, set the gNodeB engineering


5G RAN
----End

This section describes how to verify the replacement of the main control board.
Procedure
Step 1 Run the DSP CELL command to check whether the value of Cell instance state is
Normal for a cell.
If the value of Cell instance state is Uninstall, check the cell configuration or
hardware based on the value of Reason for latest state change in the command
output.
Step 2 Run the DSP OMCH command to check whether the status of the OM channel
between the gNodeB and the new MAE-Access is normal.
If OM Channel Status is not Normal, perform the following steps:
1. On the menu bar of the MAE-Access, choose Topology > Main Topology to
check whether the gNodeB is in connection. If it is, contact Huawei technical
support or dial the Huawei technical support hotline. If it is not, go to Step
2.2.
2. Check whether the non-IPsec ports in the modified configuration file are the
same as planned.
Step 3 Run LST commands to check whether the values of related parameters in the MOs
are changed. For details about the MOs and parameters, see Engineering
Preparation > Data Preparation.
If Port No. values are not changed, check whether the ports in the modified
configuration file are the same as planned.
Step 4 Verify that no ALM-25880 Ethernet Link Fault has been reported.
If any ALM-25880 Ethernet Link Fault has been reported, clear the alarm by
referring to 3900 & 5900 Series Base Station Alarm Reference.
----End

5G RAN

the original state.
Procedure
Step 1 Power off the base station and remove the new MPT board.
Step 2 Install the original MPT board and power on the base station.
All information such as the software and configuration data file before the
reconfiguration is stored on the original MPT. The base station is automatically
rolled back to its original status after the original MPT is inserted.
Step 3 Check whether the engineering rollback is successful by referring to 1.7.1.4
----End
1.7.2 Replacing the Main Control Board When an SeGW Is

Deployed
UMPT of a different model in secure networking scenarios (including PSK and
PKI).

reconfiguration scheme, and topology changes for replacing a main control board.
A main control board needs to be replaced if it cannot meet service requirements.
The transmission interface capabilities and attributes vary with the main control
board types. Therefore, during board replacement, reconfigure data based on
different schemes.
After replacing the main control board, you must power off and power on the
base station to make the configuration take effect. During the operation, the base
station cannot provide services.

5G RAN
NOTE
After the main control board is replaced, the Media Access Control (MAC) address of the board
is changed. If the MAC address is used by the transport network, inform the transport network
maintenance personnel of the change and ask them to modify the configurations.
After the main control board is replaced, the default password of the default LMT account used
for locally logging in to base stations varies between versions. For details, see section "Logging
In to and Logging Out of the LMT" in 3900 & 5900 Series Base Station LMT User Guide.
Table 1-58 Reconfiguration scheme

Replaceme Transmission Transmission Transmission Board Type
nt Scheme Ports Before Ports After Port Reconfigurati
Replacement Replacement Adjustmentb on
UMPTe- Electrical ports Electrical ports Adjustment is Change the

>UMPTg/ 0 and 2 0 and 2 not required. value of the
UMPTga Board
UMPTg/
UMPTga.
UMPTga- Electrical ports Electrical ports Adjustment is Change the

>UMPTg 0 and 2 0 and 2 not required. value of the
Board
UMPTg.
Topology Changes
N/A

This section describes the engineering preparation for replacing a main control
board when a security gateway (SeGW) is deployed, including information
collection and preparation of hardware, software, license files, certificates, and
data. It also describes the data preparation mode.

5G RAN

Configuration data The latest configuration data that is manually exported

file of the original before the reconfiguration. For details, see Exporting
main control board Deployment Lists and Configuration Files of Base
Stations in 3900 & 5900 Series Base Station Initial
Configuration Guide.

If... Then...
A UMPTe needs to be Prepare a UMPTg/UMPTga.

replaced with a
UMPTg/UMPTga
A UMPTga needs to Prepare a UMPTg.

be replaced with a
UMPTg
If the version of the new main control board is different from that of the main
control board to be replaced, collect information about the software version of the
main control board to be replaced.

Keep a new license ready if no license file is loaded to the new main control
board, the control items in the license file cannot meet service requirements, or
the license has expired.
Ensure that the operator CA-issued certificate is ready.
Data Preparation
Data to be prepared is listed in the following table.

5G RAN
Table 1-61 Data preparation for replacing a main control board
Chan SN Oper MO Configuration Reference

ge ation
Mod
el

ce fy to UMPTg/UMPTga.
the
UMP
Te
with
a
UMP
Tg/
UMP
Tga.

ce a fy to UMPTg.
UMP
Tga
with
a
UMP
Tg.

Use the "Export/Import MPT and Port No. Adjustment Data" mode and batch
reconfiguration mode on the MAE-Deployment. The "Export/Import MPT and Port
No. Adjustment Data" mode is recommended.
● The procedure for the "Export/Import MPT and Port No. Adjustment Data"
mode is as follows:
a. On the MAE-Deployment menu bar, choose NR Application > Network
Adjustment > Export MPT and Port No. Adjustment Data to start the
data export.
b. Select a base station version and base stations to be reconfigured, and
then export the related data.
c. Enter the new MPT board type and new port number in the exported file
based on the plan.
d. On the MAE-Deployment menu bar, choose NR Application > Network
Adjustment > Import MPT and Port No. Adjustment Data to start the
data import.
e. Import the modified file.
of the scenario-specific template being "Replacing the Main Control Board
When No SeGW Is Deployed"). For details, see the interactive operation guide

5G RAN
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to

Prepare Data.
NOTE
● Before using the MAE-Deployment to prepare data, ensure that data in the planned
data area is consistent with that in the current data area. If the data is inconsistent, you
can choose Area Management > Planned Area > Synchronize NEs from the menu bar
to synchronize data from the current data area to the planned data area. Then, perform
the following operations.
● You are advised to use the MAE-Deployment, which supports automatic update of the
corresponding port number in the associated MOs when a port number of the main
control board is changed. For details, see iMaster MAE Product Documentation >
Operation and Maintenance > MAE-Deployment Operation and Maintenance >
MAE-Deployment Guidelines > NR Application Management > gNodeB Related
Operations > Changing Base Station MPT Boards and Ports.

This section describes how to replace a main control board locally and remotely.
Prerequisites
Hardware, software, license file, and configuration data for replacing a main
control board are ready.
Context
Replacing a main control board requires cooperation of remote and local
operations. Figure 1-24 shows the procedure for replacing a main control board.

5G RAN
Figure 1-24 Procedure for replacing a main control board
Procedure
expand status.
To prevent alarms from being generated during reconfiguration, set the gNodeB
engineering maintenance mode to the expand status before you perform the
reconfiguration.
Step 2 Back up the license file and configuration data file of the current main control
board.

5G RAN
● (Remote operation) Use the MAE-Access to back up the license file and
configuration data file. The files can be used for restoring the base station to
the pre-reconfiguration status if the reconfiguration fails.
a. Back up the license file in use to the MAE-Access server.
For example, INS LICENSE:MODE=IPV4, IP="10.161.18.69",
b. Run the following commands on the MAE-Access to back up and export
the configuration file. The configuration file can be used to restore the
base station to the pre-reconfiguration status if the reconfiguration fails.
● (Local operation) Use the LMT to back up the license file and configuration
data file. In scenarios where configuration data is not modified, the files are
used for data activation on the LMT.
a. Start the FTP server.
b. Back up the license in use to the LMT PC.
Example: ULD LICENSE: MODE=IPV4, IP="192.169.2.16", USR="admin",
PWD="*****", DIR="ftproot/", FN="D:\FTP",
FN="lic_21021127229TAA016583_1396364568622_1.xml";
c. Back up the configuration data file and export the file to the LMT PC. The
save path is the FTP server directory set in Step 2.a (local operation).
i. Run the BKP CFGFILE command to back up the configuration data
file.
ii. Run the ULD CFGFILE command to export the configuration data
file.
Step 3 (Remote operation) Synchronize data to the planned data area.

● If configuration data does not need to be modified, synchronize the data to
the planned data area first. On the menu bar of the MAE-Deployment, choose
Area Management > Planned Area > Synchronize Planned Area NEs to
synchronize the data in the current data area to the planned data area.
● If the batch reconfiguration function of the MAE-Deployment is used to
reconfigure data, data synchronization is not required. Otherwise, the
reconfigured data will be replaced by the original data after synchronization.
Step 4 (Local operation) Power off the base station and remove the main control board
to be replaced.
Step 5 (Local operation) Install the new main control board and power on the base
station.

5G RAN
using the MAE-Access.) Remove the original base station from the main topology.
● On the menu bar of the MAE-Access, choose Topology > Main Topology.
● Right-click the base station to be removed and choose Delete from the
shortcut menu.
● In the displayed Confirm dialog box, click Yes.
● In the displayed Deletion Result dialog box, verify that Result is Succeeded,
and then click Close.
using the MAE-Access.) Export the base station deployment list and configuration
data file.
For details, see step 6 in References > Exporting Deployment Lists and
Configuration Files of Base Stations in 3900 & 5900 Series Base Station
Commissioning Guide. Click Switch to the Auto Deployment window. The
system automatically switches to the auto-deployment window, creates a
commissioning task, and adds the base station to the main topology.
NOTE
Deployment lists are required if configuration data is to be activated using the MAE-Access.
The deployment lists must be exported by using the MAE-Deployment.
Step 8 (Remote operation) Check whether the transport network supports automatic
establishment of the OM channel.
To learn the requirements for the transport network to support automatic

establishment of the OM channel, see Commissioning a Newly Deployed Base
Station > MAE-based Commissioning > Preparation > Checking a Transport
Network in 3900 & 5900 Series Base Station Commissioning Guide.
Step 9 Activate the configuration data.
When activating the configuration data, you need to activate the software for the
old main control board if the software versions of the old and new main control
boards are different. If the license needs to be updated, you must use the new
commercial license file.
● (Remote operation) Activate the configuration data on the MAE-Access and

MAE-Deployment.
a. Upload the original base station's software package to the MAE-Access
server. For details, see Commissioning a Newly Deployed Base Station
> MAE-based Commissioning > Preparation > Uploading the Software
Package in 3900 & 5900 Series Base Station Commissioning Guide.
b. Upload the license file to the MAE-Access server. For details, see
Commissioning > Preparation > Uploading a Commissioning License
(When LTE/NR Services Are to Be Enabled) in 3900 & 5900 Series Base
Station Commissioning Guide.
c. Bind the ESN.
A commissioning task has been created in Step 7. Select this
commissioning task of replacing the main control board from the

5G RAN
commissioning task list. Double-click the cell recording the ESN and
change the value to the current ESN of the base station.
d. Start the commissioning task. For details, see Commissioning a Newly
Deployed Base Station > MAE-based Commissioning > Preparation >
Starting an NE Commissioning Task in 3900 & 5900 Series Base Station
e. Check whether the gNodeB is working properly. For details, see
Commissioning > Remote Operations > Acquiring an NE
Commissioning Verification Report in 3900 & 5900 Series Base Station
f. Verify that the commissioning task is completed. For details, see
Commissioning > Remote Operations > Confirming that Auto
Deployment Tasks Are Completed in 3900 & 5900 Series Base Station
● (Local operation) Activate the configuration data on the LMT.
a. Log in to the LMT and disable the DHCP function. For details, see
Commissioning a Newly Deployed Base Station > LMT+MAE-based
Commissioning > Local Operations > Logging In to the LMT and
Disabling the DHCP Function in 3900 & 5900 Series Base Station
b. Configure the FTP server. If the FTP server to be configured is provided by
a third party or does not have a Huawei-issued device certificate, set the
FTPCLT.ENCRYMODE parameter to Auto.
c. Download and activate the software and configuration data and install
the license file. For details, see Commissioning a Newly Deployed Base
Station > LMT+MAE-based Commissioning > Local Operations >
Loading the Software, Data Configuration File, and Commissioning
License by Using the LMT in 3900 & 5900 Series Base Station
NOTE
To locally log in to the LMT after configuration data is activated, use the local maintenance
IP address of the old main control board but the login account and password for the new
main control board.
using the MAE-Access.) Delete the commissioning task from the MAE-Access.
1. Start the MAE-Access client and choose SON > Auto Deployment. The Auto
Deployment window is displayed.
2. Right-click the commissioning task to be deleted and choose Delete from the
shortcut menu.
3. In the displayed Confirm dialog box, click Yes.
normal status on the MAE-Access.
After the data reconfiguration is completed, set the gNodeB engineering


5G RAN
----End

This section describes how to verify the replacement of the main control board
when a security gateway (SeGW) is deployed on the network.
Procedure
Step 1 Verify that no ALM-25880 Ethernet Link Fault has been reported.
If any ALM-25880 Ethernet Link Fault has been reported, clear the alarm by
Step 2 Run LST commands to check whether the values of related parameters in the MOs
are changed. For details about the MOs and parameters, see Engineering
Preparation > Data Preparation.
If Port No. values are not changed, check whether the ports in the modified
configuration file are the same as planned.
Normal for a cell.
output.
Step 4 Run the DSP OMCH command to check whether the status of the OM channel
between the gNodeB and the new MAE-Access is normal.
If OM Channel Status is not Normal, perform the following steps:
1. On the menu bar of the MAE-Access, choose Topology > Main Topology to
check whether the gNodeB is in connection. If it is, contact Huawei technical
support or dial the Huawei technical support hotline. If it is not, go to Step
4.2.
2. Check whether the non-IPsec ports in the modified configuration file are the
same as planned.

5G RAN
----End

the original state.
Procedure
Step 1 Power off the base station and remove the new MPT board.
Step 2 Install the original MPT board and power on the base station.
All information such as the software and configuration data file before the
reconfiguration is stored on the original MPT. The base station is automatically
rolled back to its original status after the original MPT is inserted.
----End
1.7.3 Replacing BBPs

implementation, engineering verification, and engineering rollback for replacing
the UBBPfw with a UBBPg.

reconfiguration scheme, and topology changes for replacing the BBP.
● The baseband processing unit (BBP) in use is faulty and must be replaced
with one of another BBP type.
● The BBP running on the live network does not meet service requirements.
Therefore, the BBP needs to be upgraded.
NOTE
For details about replacing a BBP with the same type of BBP, for example, replacing the UBBPfw
with another UBBPfw or replacing the UBBPg with another UBBPg, see BBU Hardware
Maintenance Guide.
During the replacement, you must power off and then power on the BBP to make
the configuration take effect. During the operation, all the cells established on the
BBP cannot provide services.

5G RAN
NOTE
● When the UBBP is used in multimode concurrence scenarios, configure the UBBP for other
RATs simultaneously. For details, see the reconfiguration guide of the corresponding RAT:
For LTE, see eRAN Reconfiguration Guide.
Reconfiguration schemes of replacing BBPs are as follows:

Replacing the UBBPfw with a UBBPg
● Based on the subboard type of the UBBPg, set Board Specification in the BBP
MO to UBBPg2, UBBPg2a, or UBBPg3 as required.
● Set Board Type in the BBP MO to UBBP(UBBP) and Base Band Work
Standard to NR(NR).
Topology Changes
N/A

This section describes the engineering preparation for replacing the BBP before
reconfiguration, including information collection and preparation of hardware,
software, license files, certificates, and data. It also describes the data preparation
mode.

Slot where the BBP to be replaced is -

located
Number of cells that can be Check whether the new BBP supports
established on the BBP to be replaced the establishment of cells of such a
quantity.

5G RAN
If You Need to... Then...
Replace the UBBPfw Prepare a UBBPg.

with a UBBPg.
If the software version of the new BBP does not match that of the base station,
collect and upload the software version of the base station to the MAE-Access.
After the upload is completed, the base station will automatically supplement the
software version of the BBP when the remote maintenance channel between the
base station and the MAE-Access is normal.

N/A

N/A
Data Preparation
Determine the data to be prepared based on the reconfiguration procedure in
Reconfiguration Scheme. Prepare the data according to the following table.
Table 1-64 Data to be prepared for replacing a BBP

tion
1 Modify BBP ● To replace the UBBPfw with a UBBPg, set

Board Type to UBBP(UBBP), Base Band
Work Standard to NR, and Board
Specification to a value as required.

preferable in this scenario. You can configure base stations in batches using the
MAE-Deployment batch reconfiguration mode or configure a single base station
on the MAE-Deployment. The three data preparation modes are described as
follows:

5G RAN
NOTE
name of the scenario being "Replacing Baseband Processing Units"). For
● Using MML commands: Prepare MML configuration scripts based on the
script examples.

In the following example, the UBBPfw is replaced with a UBBPg2, and one cell has
been established on the old UBBP.
/*Changing the board type of the BBP to UBBP*/
MOD BBP: CN=0, SRN=0, SN=0, TYPE= UBBP, BBWS= NR, BRDSPEC="UBBPg2";

This section describes how to replace BBPs locally and remotely.
Prerequisites
Related information, hardware, software, and data are ready.
Context
Procedure
● Using the MAE-Deployment
NOTE
If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
All the steps are remote operations except 4.

gNodeB engineering maintenance mode to expansion mode before you

5G RAN
perform the reconfiguration. For details, see Setting the gNodeB

Maintenance Mode.
b. Block a BBP.
Run the BLK BRD command with Block Type set to
IMMEDIATE(Immediate).
c. Deactive the cells on the BBP to be replaced.
Run the DEA NRCELL command to deactivate the cells of the to-be-
replaced board that is indicated by Directly Connected BBP Port
Information in the DSP NRDUCELLANTENNA command output.
For example:
DEA NRCELL: NrCellId =0;
d. (Local operation) Replace the BBP.
For details, see Replacing the UBBP in BBU Hardware Maintenance
Guide.
Then, connect cables to the new UBBP according to the cabling scheme
of the original UBBP.
NOTE
If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
e. Deliver the configuration data to the base station and activate it. For
f. Unblock a BBP.
Run the UBL BRD command.
g. Activate the cells that are deactivated due to BBP replacement.
Run the ACT NRCELL command to activate the cells that are deactivated
in c.
For example:
h. After the data reconfiguration is completed, set the gNodeB engineering
For details, see Setting the gNodeB Maintenance Mode.
● Using MML commands
NOTE
All the steps are remote operations except 5.

perform the reconfiguration. For details, see Setting the gNodeB
Maintenance Mode.
file. The configuration file can be used to restore the base station
configurations if the reconfiguration fails.

5G RAN

ii. To upload the configuration file to an FTP server, run the ULD
CFGFILE command.
For example: ULD CFGFILE:MODE=IPV4, IP="10.169.18.69",
c. Block a BBP.
Run the BLK BRD command with Block Type set to
IMMEDIATE(Immediate).
d. Deactive the cells on the BBP to be replaced.
Run the DEA NRCELL command to deactivate the cells of the to-be-
replaced board that is indicated by Directly Connected BBP Port
Information in the DSP NRDUCELLANTENNA command output.
For example:
DEA NRCELL: NrCellId =0;
e. (Local operation) Replace the BBP.
For details, see Replacing the UBBP in BBU Hardware Maintenance
Guide.
Then, connect cables to the new UBBP according to the cabling scheme
of the original UBBP.
NOTE
If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
f. Use the MAE-Access to deliver the batch configuration scripts prepared in
g. Unblock a BBP.
Run the UBL BRD command.
h. Activate the cells that are deactivated due to BBP replacement.
Run the ACT NRCELL command to activate the cells that are deactivated
in 4.
For example:
i. After the data reconfiguration is completed, set the gNodeB engineering
For details, see Setting the gNodeB Maintenance Mode.
----End

This section describes how to verify the replacement of BBPs.

5G RAN
Procedure
Step 1 Ensure that no BBP-related alarms are generated.
If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Step 2 Run the DSP NRDUCELL/DSP NRCELL command to check whether NR DU Cell
State/NR Cell State is Normal.
If NR DU Cell State/NR Cell State is Uninstalled, check the value of NR DU Cell

Latest State Change Reason/Cell Latest State Change, and then check the cell
configuration or hardware environment.
----End

the original state.
Procedure
Step 1 Remove the new BBP and its CPRI cables.
Step 2 Insert the replaced BBP and connect the CPRI cables to the BBP as the original
networking.

configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.7.4 Changing CPRI Ports for RF Modules

common public radio interface (CPRI) ports for radio frequency (RF) modules. It is
applicable to both CPRI and eCPRI protocols.

reconfiguration scheme, and topology changes for changing CPRI ports for RF
modules.
● The board configuration scheme of the BBU has changed, and the slot of the
baseband processing unit (BBP) connecting to the RF module has changed.
● An RF module on live networks does not meet service requirements and
needs to be replaced by another RF module to provide larger capacity or
coverage.
During the CPRI port change, cells served by the chain or ring of the RF module
cannot provide services.
Figure 1-25 shows the reconfiguration procedure using the MAE-Deployment.
Figure 1-26 shows the reconfiguration procedure using MML commands.

5G RAN
Figure 1-25 Procedure for changing CPRI ports for RF modules using the MAE-Deployment

5G RAN
Figure 1-26 Procedure for changing CPRI ports for RF modules using MML
commands
Topology Changes
The CPRI port numbers are changed in the network after the CPRI port change.
Figure 1-27 shows the topology changes when the head CPRI port of a ring
topology is changed from one BBP to another BBP.

5G RAN

This section describes the engineering preparation for changing CPRI ports for RF
modules, including information collection and preparation of hardware, software,
license files, certificates, and data. It also describes the data preparation mode.
CPRI topology of the RF module The ring and chain topologies for the
NR network
CPRI port number after the The slot number of the BBP and the
reconfiguration CPRI port number

5G RAN
CPRI port number before the The slot number of the BBP and the
reconfiguration CPRI port number, which are required
for engineering rollback
N/A
N/A

N/A

N/A
Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.
NOTE
Adjusting the CPRI port connected to an RF module affects the services of the converged party
when a separate-MPT multimode base station works in CPRI MUX scenarios. Therefore, the data
configuration of the converged party needs to be adjusted accordingly. For details about the
adjustment method, see section "Changing CPRI Ports for RF Modules" in the
"Reconfiguration Guide" for the corresponding RAT.

5G RAN
Table 1-66 Data preparation for changing the CPRI port connected to the RF
module
Rec SN Ope MO Configuration Reference
onfi rati
gura on
tion
Mod
e
MAE 1 Mod RRUCHAIN Set breakpoints for the RRU chain or ring:
- ify ● Chain topology: Set one breakpoint with
Depl BreakPoint Position1 set to 0.
oym
ent ● Ring topology: Set two breakpoints with
BreakPoint Position1 set to 0 and
BreakPoint Position2 set to the RRU
level number.
2 Mod RRUCHAIN When the adjusted CPRI ports are located

ify on the same BBP:
● Chain topology: Change Head Port No.
● Ring topology: Change Head Port No.
and (or) Tail Port No. to the target
values based on whether the adjusted
CPRI port numbers are head port number
and (or) tail port number.
When the adjusted CPRI ports are located

on different BBPs:
● Chain topology: Change Head Slot No.
and Head Port No. to the target values.
● Ring topology: Change Head Slot No.
and (or) Tail Slot No. as well as Head
Port No. and (or) Tail Port No. to the
target values based on whether the
adjusted CPRI port numbers are head
port number and (or) tail port number.
3 Mod RRUCHAIN Change the values of BreakPoint Position1

ify and (or) BreakPoint Position2 to 255 to
remove the breakpoints on the RRU chain or
ring.
MM 1 Mod RRUCHAIN Set breakpoints for the RRU chain or ring:

L ify ● For a chain topology, set one breakpoint
com with BreakPoint Position1 set to 0.
man
ds ● For a ring topology, set two breakpoints
with BreakPoint Position1 set to 0 and
BreakPoint Position2 set to the RRU
level number.

5G RAN

onfi rati
gura on
tion
Mod
e
2 Mod RRUCHAIN When the adjusted CPRI ports are located

ify on the same BBP:
● Chain topology: Change Head Port No.
● Ring topology: Change Head Port No.
and (or) Tail Port No. to the target
values based on whether the adjusted
CPRI port numbers are head port number
and (or) tail port number.
When the adjusted CPRI ports are located

on different BBPs:
● Chain topology: Change Head Slot No.
and Head Port No. to the target values.
● Ring topology: Change Head Slot No.
and (or) Tail Slot No. as well as Head
Port No. and (or) Tail Port No. to the
target values based on whether the
adjusted CPRI port numbers are head
port number and (or) tail port number.
3 Mod RRUCHAIN Change the values of BreakPoint Position1

ify and (or) BreakPoint Position2 to 255 to
remove the breakpoints on the RRU chain or
ring.

follows:
NOTE
name of the scenario-specific template being "Changing CPRI Ports for RF

5G RAN
Modules"). For details, see the interactive operation guide 1.11.2 Using the
Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data.
script examples.

In the following example, the topology of the CPRI ports is a ring, the head CPRI
port with the ring number 0 is changed from port 0 of the board in slot 2 to port
0 of the board in slot 3, the tail CPRI port is changed from port 1 of the board in
slot 2 to port 1 of the board in slot 3, and the RRU level number is 2.
/*Setting breakpoints of the RRU chain or ring with BreakPoint Position1 set to 0 and BreakPoint Position2
set to 2*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=2;
/*Modifying the numbers of the CPRI ports connecting to the RRUs*/
MOD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HSN=3, HPN=0, TSN=3, TPN=1;
/*Restoring the breakpoints of the RRU chain or ring*/
/*Resetting the RF module with CN, SRN, and SN set to the cabinet number, subrack number, and slot
number of the RF module, respectively*/
RST BRD: CN=0, SRN=60, SN=0;

This section describes how to change CPRI ports for RF modules locally and
remotely.
Prerequisites
Information and data for changing the CPRI ports for RF modules are ready.
Context
Procedure
● Local Operation
a. (Perform this step if the RF modules need to be connected to another
CPRI port with the BBP position unchanged.) Remove the CPRI cable from
the original port and connect it to the new port.
b. (Perform this step if the RF modules need to be connected to another
CPRI port with the BBP position changed.) Remove the BBP from the
original slot and install it in the new slot.

5G RAN

ii. Deliver the prepared data to the base station after changing the CPRI
port connected to the RF module, and activate it.
NOTE
During script activation, you are advised to activate the incremental scripts for
changing the CPRI port where an RF module is connected, and then activate the
incremental scripts for removing breakpoints after topology adjustment.
base station configurations if the reconfiguration fails.
command.
2) To upload the configuration file to an FTP server, run the ULD
CFGFILE command.
----End

This section describes how to verify the changes of CPRI ports for RF modules.
Procedure
Step 1 Verify that no BBP-related and RF-module-related alarms have been reported.

5G RAN
Step 2 Check whether ALM-26246 BBU CPRI Line Rate Negotiation Abnormal is
reported.
If ALM-26246 BBU CPRI Line Rate Negotiation Abnormal is reported, clear the
alarm according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
Normal for a cell.
output.
----End

the original state.
Procedure
Step 1 (Perform this step if the RF modules need to be connected to another CPRI port
with the BBP position unchanged.) Remove the CPRI cable from the new port and
connect it to the original port.
Step 2 (Perform this step if the RF modules need to be connected to another CPRI port
with the BBP position changed.) Remove the BBP from the new slot and install it
in the original slot.
configuration file.
configuration file.
data.

5G RAN

NOTE

record table.
Step 4 Verify the engineering rollback by referring to the procedure in 1.7.4.4

----End
1.7.5 Adding or Deleting an RF Module

implementation, engineering verification, and engineering rollback for adding or
deleting an RF module.

reconfiguration scheme, and topology changes for adding or deleting an RF
module.
● RF modules running on the live network do not meet service requirements,
and therefore additional RF modules are required to provide larger capacity or
larger coverage.
● RF modules need to be deleted to adapt to service adjustment on the live
network.
● When an RF module is added or deleted, no cells served by the chain or ring
where the RF module is located provide services.
● After you delete an RF module, services supported by the module are
unavailable.
Figure 1-28 and Figure 1-29 show the reconfiguration procedures using the MAE-
Deployment. Figure 1-30 and Figure 1-31 show the reconfiguration procedures
using MML commands.

5G RAN
Figure 1-28 Reconfiguration procedure for adding an RF module to a chain or ring

(MAE-Deployment)
Figure 1-29 Reconfiguration procedure for deleting an RF module from a chain

(MAE-Deployment)

5G RAN
Figure 1-30 Reconfiguration procedure for adding an RF module to a chain (MML

commands)

5G RAN
Figure 1-31 Reconfiguration procedure for deleting an RF module from a chain

(MML commands)
Topology Changes
Scenario 1: Add RF modules to a new RRU chain or ring. Figure 1-32 shows
topologies before and after the reconfiguration using a chain topology as an
example.

5G RAN
Figure 1-32 Topologies before and after the reconfiguration (chain topology)
Scenario 2: Add RF modules to or delete RF modules from an existing RRU ring or

chain: You need to add or delete an RF module in the chain head or center when
the CPRI topology is chain. Figure 1-33 shows the topology changes before and
after the reconfiguration when an RRU is added to the chain head.

5G RAN

chain: You need to add or delete an RF module in the chain tail when the CPRI
topology is chain. Figure 1-34 shows the topology changes before and after the
reconfiguration when an RRU is added to the chain tail.

5G RAN

chain: You need to add or delete an RF module when the CPRI topology is ring.
Figure 1-35 shows the topology changes before and after the reconfiguration
when an RRU is added.

5G RAN
Figure 1-35 Topologies before and after the reconfiguration (ring topology)
Scenario 5: RF modules can be deleted but cannot be added when the CPRI
topology is load sharing.

This section describes the engineering preparation for adding or deleting an RF
module, including information collection and preparation of hardware, software,
license files, certificates, and data. It also describes the data preparation mode.
RF module information The RRU model and supported

frequency band

5G RAN
CPRI topology of the RF module The chain, ring, and load-sharing

topologies for the NR network
Before you add or delete an RF module, you need to prepare the hardware listed
in Table 1-68.

If you need to... Then...
Add an RF module. Prepare a new RF module.
N/A

N/A

N/A
Data Preparation
NOTE
● When an RF module for multiple RATs is added to a co-MPT base station, the data belongs
to the common data of all RATs and needs to be configured only once.
● When an RF module for multiple RATs is added to a separate-MPT base station, the data
needs to be configured separately for each RAT and common parameters must be set
consistently.

5G RAN
Table 1-69 Data preparation for adding an RF module

Rec SN Ope MO/MML Configuration Reference
onfi rati
gura on
tion
Mod
e
MAE 1 Add RRUCHAIN Add an RRU chain or ring before you add RF
- modules to the RRU chain or ring.
Depl For details about parameter settings, see RF
oym Unit and Topology Management Feature
ent Parameter Description.
2 Mod RRUCHAIN When adding RF modules to an existing
ify RRU chain or ring:
● If RRUs are deployed in a ring topology,
skip this operation.
● If RRUs are not deployed in a ring
topology, set breakpoints for the RRU
chain or ring.
– You do not need to set breakpoints for
the RRU chain or ring when adding an
RF module to the chain tail.
– You need to set breakpoints for the
RRU chain or ring in the following
situations:
– Add an RF module in the chain
head or center: Set one breakpoint
by setting BreakPoint Position1 to
0.
3 Mod CPRIPORT When adding RF modules to an existing

ify RRU chain or ring:
● If RRUs are not deployed in a ring
topology, skip this operation.
block the CPRI ports at the ring head and
tail.
4 Add RRU/RFU For details about parameter settings, see RF

Parameter Description.
Using the MAE-Deployment (MO-based):
When adding an RF module to a position in
the chain head/center or in the RXU ring,
you need to modify the location IDs of the
RF modules following this position.

5G RAN

onfi rati
gura on
tion
Mod
e
5 Mod RRUCHAIN If a breakpoint has been set for the RRU

ify chain or ring, restore the breakpoint by
setting BreakPoint Position1 to 255.
6 Mod CPRIPORT If a CPRI port in the RRU ring or chain has

ify been blocked, unblock the CPRI port.
MM 1 Add ADD Add an RRU chain or ring before you add RF

L RRUCHAIN modules to the RRU chain or ring.
Com For details about parameter settings, see RF
man Unit and Topology Management Feature
d Parameter Description.
2 Mod MOD When adding RF modules to an existing
ify RRUCHAIN RRU ring or chain, set breakpoints of the
RRU ring or chain based on the following
rules:
You do not need to set breakpoints for the
RRU chain or ring when adding an RF
module to the chain tail.
You need to set breakpoints for the RRU
chain or ring in the following situations:
● Add an RF module in the chain head or
center: Set one breakpoint by setting
BreakPoint Position1 to 0.
● Add an RF module in the ring topology:
Set two breakpoints by setting
BreakPoint Position1 to 0 and
BreakPoint Position2 to the RRU level
number.
3 Add ADD RRU For details about parameter settings, see RF

4 Mod MOD Restore the breakpoints of the RRU ring or
ify RRUCHAIN chain if you have set the breakpoints of the
RRU ring or chain.
● If you have set only one breakpoint, set
● If you have set two breakpoints, set
BreakPoint Position1 and BreakPoint
Position2 to 255.

5G RAN
NOTE
When the MAE-Deployment is used to prepare data, item 1 to item 4 are required before and
for adding an RF module, and item 5 and item 6 are required after adding an RF module.
Table 1-70 Data preparation for deleting an RF module

onfi rati
gura on
tion
Mod
e
MAE 1 Mod RRUCHAIN ● If RRUs are deployed in a ring topology,

- ify skip this operation.
Depl ● If RRUs are not deployed in a ring
oym topology, set breakpoints for the RRU
ent chain or ring.
– In the following situations, you do not
need to set breakpoints of the RRU
chain or ring.
– Delete an RF module at the chain
tail.
– Delete an RF module in the load-
sharing topology.
– You need to set breakpoints for the
RRU chain or ring in the following
situations:
– Delete an RF module in the chain
head or center: Set one breakpoint
by setting BreakPoint Position1 to
0.
2 Mod CPRIPORT ● If RRUs are not deployed in a ring

ify topology, skip this operation.
block the CPRI ports at the ring head and
tail.
3 Dele RRU/RFU For details about parameter settings, see RF

te Unit and Topology Management Feature
Using the MAE-Deployment (MO-based):
When deleting an RF module at a position in
the chain head/center or in the RXU ring,
you need to modify the location IDs of the
RF modules following this position.

5G RAN

onfi rati
gura on
tion
Mod
e
4 Mod RRUCHAIN If a breakpoint has been set for the RRU

ify chain or ring, restore the breakpoint by
setting BreakPoint Position1 to 255.
5 Mod CPRIPORT If a CPRI port in the RRU ring or chain has

ify been blocked, unblock the CPRI port.
MM 1 Mod MOD Set breakpoints for the RRU chain or ring.

L ify RRUCHAIN In the following situations, you do not need
Com to set breakpoints of the RRU chain or ring.
man
d ● Delete an RF module at the chain tail.
● Delete an RF module in the load-sharing
topology.
You need to set breakpoints for the RRU
chain or ring in the following situations:
● Delete an RF module in the chain head or
center: Set one breakpoint by setting
● Delete an RF module in the ring
topology: Set two breakpoints by setting
BreakPoint Position1 to 0 and
BreakPoint Position2 to the RRU level
number.
2 Dele ADD RRU For details about parameter settings, see RF

te Unit and Topology Management Feature
3 Mod MOD Restore the breakpoints of the RRU ring or
ify RRUCHAIN chain if you have set the breakpoints of the
RRU ring or chain.
● If you have set only one breakpoint, set
● If you have set two breakpoints, set
BreakPoint Position1 and BreakPoint
Position2 to 255.
NOTE
When the MAE-Deployment is used to prepare data, item 1 to item 3 are required before
deleting an RF module, and item 4 and item 5 are required for and after deleting an RF module.

5G RAN

commands. You can configure base stations in batches using the MAE-Deployment
batch reconfiguration mode or configure a single base station using the MAE-
Deployment GUI (based on the device panel).
NOTE
When reconfiguring a base station through the MAE-Deployment GUI, you can use either the
MO-based or the device-panel-based method. To simplify operations, you are advised to use the
device-panel-based method. The device-panel-based method does not require MO-related data
preparation. For detailed operations, see Engineering Implementation > Remote Operation >
Using the MAE-Deployment (based on the device panel on the GUI).
● Using the batch configuration mode of the MAE-Deployment:
NOTE
The following MAE-Deployment operations are performed to prepare script files for later
engineering implementation. When adding or removing RF modules, you need to export
two incremental script files separately based on the following rules:
● When adding RF modules:
1. Based on step 1 through step 4 in Data Preparation, export the incremental script
file before and when adding RF modules.
2. Based on step 5 and step 6 in Data Preparation, export the incremental script files
after adding RF modules.
● When removing RF modules:
1. Based on step 1 through step 3 in Data Preparation, export the incremental script
file before and when deleting RF modules.
2. Based on step 4 and step 5 in Data Preparation, export the incremental script files
after deleting RF modules.
a. On the menu bar of the planned data area, choose NR Application >
Network Adjustment > Export Base Station Bulk Configuration Data
to start the data export function. The Export Base Station Bulk
Configuration Data dialog box is displayed.
b. Select the base station for which you want to add or delete an RF
module, and click Next.
c. Set Export By to Custom MOC, select the MO to be configured, and click
Next to export the batch reconfiguration file.
d. Open the exported file, modify related data as required, save the file, and
close it.
e. On the menu bar of the planned data area, choose NR Application >
Network Adjustment > Export Base Station Bulk Configuration Data
to start the data import function. The Import Base Station Bulk
Configuration Data dialog box is displayed.
f. Select the modified batch reconfiguration file, and then click Next.
g. Select the base station for which you want to add or delete an RF
module, and click Next. After the operation is successful, click Finish.

5G RAN
h. In the left pane of the planned data area, select the base station for
which you want to add or delete an RF module, right-click the base
station, and choose Check Data from the shortcut menu. In the lower
part, check verification results and correct configuration data errors until
the verification is successful.
i. On the menu bar of the planned area, choose Area Management >
Planned Area > Export Incremental Scripts (MAE-Deployment client
mode) or MAE-DeploymentArea Management > Planned Area > Export
Incremental Scripts (MAE-Access client mode). Export incremental
configuration scripts to the base station.
script examples.

Scenario 1: Add RF modules to a new RRU chain or ring. The following describes
MML configuration scripts for data preparation when the CPRI topology is chain.
/*Adding an RRU chain or ring with Topo Type set to CHAIN*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=1, PS=0, RT=LRRU, RS=LO, RXNUM=2, TXNUM=2;

chain. The following describes MML configuration scripts for data preparation
when the CPRI topology is chain, the RRU level is two, and you need to add or
delete an RRU in the chain head or center.
/*Setting a breakpoint of the RRU chain with BreakPoint Position1 set to 0*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
/*(Optional) Adding an RRU*/
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=2, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2;
/*(Optional) Removing an RRU*/
RMV RRU: CN=0, SRN=61, SN=0;
/*Restoring the breakpoint of the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255;

when the CPRI topology is chain and you need to add or delete an RRU in the
chain tail.

when the CPRI topology is ring, the RRU level is two, and you need to add or
delete an RRU in the chain or ring.
/*Setting breakpoints of the RRU chain or ring with BreakPoint Position1 set to 0 and BreakPoint Position2
set to 2*/
/*Restoring the breakpoints of the RRU chain or ring*/
Scenario 5: The following describes MML configuration scripts for data preparation
when the CPRI topology is load-sharing and you need to remove an RRU.

5G RAN


This section describes how to add or delete an RF module locally and remotely.
Prerequisites
Related information and configuration data are ready.
Context
Procedure
● Local Operation
a. For details about how to add or delete an RRU, see RRU Hardware
Maintenance Guide.
b. For details about how to add or delete an AAU, see AAU Hardware
Maintenance Guide.
ii. Deliver the data that you have prepared used before and during RF
module addition or deletion to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. Deliver the data that you have prepared used after RF module
addition or deletion to the base station and activate the data. For
NOTE
You are advised to activate the incremental scripts for adding or deleting RF modules
first. After hardware adjustment is complete, you can activate the incremental scripts
for deleting breakpoints.
– Using the MAE-Deployment (based on the device panel on the GUI):
Add an RF module:

5G RAN
In the left pane of the planned area, right-click a physical based station
and choose Device Panel from the shortcut menu. The device panel is
displayed in the right pane, as shown in Figure 1-36.
Figure 1-36 Device panel
Area 1 Device navigation tree. The cabinet

navigation tree is in the upper part and
the RF module navigation tree is in the
lower part.
After you select a cabinet, subrack, or RF

module in the device navigation tree, area
2 displays the panel of the selected
device.
Area 2 Cabinet, subrack, and board configuration

area
(Optional) Add an RF module to the newly added RRU ring or chain.

i. Add an RXU chain/ring.
1) In the lower left part of the device panel, right-click TOPO and
choose Add Chain from the shortcut menu.
2) Based on the planned data, set the related information such as
the number and networking mode of the RXU chain/ring and
the port on the board to which the RXU chain/ring head is
connected.

5G RAN
3) Click OK. The configured RXU chain/ring is displayed under the

TOPO node.
ii. Add an RF board.
1) In the lower left part of the device panel, right-click a configured
RXU chain/ring, and choose Add Board > Board Type from the
shortcut menu. A dialog box is displayed for you to add an RF
board.
2) Set the working mode and other related attributes for the RF
board.
3) Click OK.
iii. Deliver the data for adding RF modules to the base station and
activate the data.
On the menu bar of the planned area, choose MAE-Deployment >
Area Management > Planned Area > Export Incremental Scripts
to start exporting configuration scripts.
For detailed operations, press F1 on the MAE-Deployment to view
section Exporting Incremental Scripts from a Planned Data Area
in the MAE-Access online help.
(Optional and required when you need to add RF units on the RXU ring
or in the middle of the RXU chain during RXU chain/ring capacity
expansion) Add RF units to the RXU ring or in the middle of the RXU
chain.
▪ Add an RF unit in the middle of the RXU chain.

1) On the RXU Topology tab page, select the board connected to
the RXU chain from the Interface board drop-down list.
2) On the RXU Topology tab page, right-click the RXU chain for
which you want to set breakpoints, and choose Set Break Point
from the shortcut menu.
3) Right-click a position after the breakpoint where you want to
add a board and choose Add Board > Board Type from the
shortcut menu. A dialog box is displayed for you to add an RF
board.
4) Set the working mode and other related attributes for the RF
board.
5) Click OK.
6) Export the incremental scripts for adding RF boards.
On the menu bar of the planned data area, choose Area
Management > Planned Area > Export Incremental Scripts.
Then, export configuration scripts.
For detailed function operations and introduction, click on

the MAE-Deployment to view section Exporting Incremental
Scripts from a Planned Data Area in the MAE Help.
7) On the RXU Topology tab page, right-click a configured
breakpoint and choose Cancel Break Point from the shortcut
menu.
8) Export the incremental scripts for deleting breakpoints.

5G RAN


NOTE
During script activation, you are advised to activate the incremental scripts
for adding RF boards, and then activate the incremental scripts for deleting
breakpoints after hardware reconfiguration.
– Add an RF unit on the RXU ring.
i. On the device panel, right-click the board where the RXU ring is
located and choose Properties from the shortcut menu. A dialog box
is displayed for you to set properties.
ii. On the CPRI Port tab page, set Administrative Status for ports at
the RXU ring head and tail to Blocked and click OK.
iii. On the RXU Topology tab page, select the board connected to the
RXU ring from the Interface board drop-down list.
iv. On the RXU Topology tab page, right-click the RXU ring for which
you want to set breakpoints, and choose Set Break Point from the
shortcut menu.
v. Set start and end positions of two breakpoints and click OK.
vi. Right-click a position between two breakpoints where you want to
add a board and choose Add Board > Board Type from the shortcut
menu. A dialog box is displayed for you to add an RF board.
vii. Set the working mode and other related attributes for the RF board.
viii. Click OK.
ix. On the RXU Topology tab page, right-click a configured breakpoint
and choose Cancel Break Point from the shortcut menu.
x. Export the incremental scripts for adding RF boards.
Management > Planned Area > Export Incremental Scripts. Then,
export configuration scripts.
For detailed function operations and introduction, click on the

MAE-Deployment to view section Exporting Incremental Scripts
from a Planned Data Area in the MAE Help.
xi. On the device panel, right-click the board where the RXU ring is
located and choose Properties from the shortcut menu. A dialog box
is displayed for you to set properties.
xii. On the CPRI Port tab page, set Administrative Status for ports at
the RXU ring head and tail to Unblocked and click OK.
xiii. Export the incremental scripts for unblocking the management status
of CPRI ports.
Management > Planned Area > Export Incremental Scripts. Then,
export configuration scripts.

5G RAN
For detailed function operations and introduction, click on the

from a Planned Data Area in the MAE Help.
NOTE
adding RF boards, and then activate the incremental scripts for unblocking the
management status of CPRI ports after hardware reconfiguration.
– Delete an RF module.
In the left pane of the planned area, right-click a base station you want
to configure and choose Device Panel from the shortcut menu. The
device panel is displayed in the right pane, as shown in Figure 1-37.
Figure 1-37 Device panel
Area 1 Device navigation tree. The cabinet

navigation tree is in the upper part and
the RF module navigation tree is in the
lower part.
After you select a cabinet, subrack, or RF

module in the device navigation tree, area
2 displays the panel of the selected
device.
Area 2 Cabinet, subrack, and board configuration

area
Optional: Delete an independent RF module.

i. In the lower part of area 1, right-click the RF module you want to
delete in the topology view and choose Delete from the shortcut
menu. A confirmation dialog box is displayed.

5G RAN
ii. Click Yes. The system starts to delete the RF module.

iii. Deliver the data for deleting RF modules to the base station and
activate the data.
On the menu bar of the planned area, choose MAE-Deployment >
Area Management > Planned Area > Export Incremental Scripts
to start exporting configuration scripts.
For detailed function operations and introduction, press F1 on the
from a Planned Data Area in the MAE-Access online help.
Optional: To delete an RF module in the RXU ring or in the center of the
RXU chain, you need to set breakpoints on the RXU chain.
▪ Delete an RF module in the center of the RXU chain.

1) On the RXU Topology tab page, select the board connected to
the RXU chain from the Interface board drop-down list.
2) On the RXU Topology tab page, right-click the RXU chain for
which you want to delete an RF module, and choose Set Break
Point from the shortcut menu.
3) In the lower part of area 1, right-click the RF module you want
to delete in the topology view and choose Delete from the
shortcut menu. A confirmation dialog box is displayed.
4) Click Yes. The system starts to delete the RF module.
5) Export the incremental scripts for deleting RF modules.
On the menu bar of the planned area, choose MAE-Deployment
> Area Management > Planned Area > Export Incremental
Scripts to start exporting configuration scripts.
For detailed operations, press F1 on the MAE-Deployment to
view section Exporting Incremental Scripts from a Planned
Data Area in the MAE-Access online help.
menu.
7) Export the incremental scripts for deleting breakpoints.

NOTE
deleting RF modules, and then activate the incremental scripts for removing
▪ Delete an RF module in the RXU ring.

1) On the device panel, right-click the board where the RXU ring is
located and choose Properties from the shortcut menu. A dialog
box is displayed for you to set properties.

5G RAN
2) On the CPRI Port tab page, set Administrative Status for ports
at the RXU ring head and tail to Blocked and click OK.
3) On the RXU Topology tab page, right-click the RXU chain from
which you want to delete an RF module, and choose Set Break
Point from the shortcut menu.
4) Set start and end positions of two breakpoints and click OK.
5) In the lower part of area 1, right-click the RF module you want
to delete in the topology view and choose Delete from the
shortcut menu. A confirmation dialog box is displayed.
6) Click Yes. The system starts to delete the RF module.
menu.
8) Export the incremental scripts for deleting RF modules.
On the menu bar of the planned area, choose MAE-Deployment
> Area Management > Planned Area > Export Incremental
Scripts to start exporting configuration scripts.
For detailed operations, press F1 on the MAE-Deployment to
view section Exporting Incremental Scripts from a Planned
Data Area in the MAE-Access online help.
9) On the device panel, right-click the board where the RXU ring is
located and choose Properties from the shortcut menu. A dialog
box is displayed for you to set properties.
10) On the CPRI Port tab page, set Administrative Status for ports
at the RXU ring head and tail to Unblocked and click OK.
11) Export the incremental scripts for unblocking the management
status of CPRI ports.

NOTE
deleting RF modules, and then activate the incremental scripts for removing
command.

5G RAN

CFGFILE command.
----End

This section describes how to verify that an RF module is added or deleted.
Procedure
Step 1 Verify that no RF-module-related alarms have been reported.
Step 2 Verify that ALM-26236 RRU Cascading Levels and Configuration Mismatch,
ALM-26238 RRU Network Topology Type and Configuration Mismatch,
ALM-26246 BBU CPRI Line Rate Negotiation Abnormal, or ALM-26501 RF Unit
Optical Module or Electrical Port Not Ready is not reported.
If any preceding alarm is reported, clear the alarm according to instructions in
3900 & 5900 Series Base Station Alarm Reference.
Normal for a cell.
output.
----End

the original state.
Procedure
Step 1 If you have added an RF module, you need to remove the added RF module and
restore the CPRI topology to the status before the adjustment.
Step 2 If you have deleted an RF module, you need to insert the deleted RF module into
the original slot and restore the CPRI topology to the status before the
adjustment.

5G RAN

configuration file.
configuration file.
data.
NOTE

record table.

----End
1.8 Interface and Link Data Reconfigurations

This section describes how to reconfigure gNodeB interface and link data in
typical scenarios.
1.8.1 Replacing a MAE-Access


5G RAN
MAE-Access. Data must be configured for the transport network between the
gNodeB and the new MAE-Access in advance.

reconfiguration scheme, and topology changes for replacing a MAE-Access.
A MAE-Access needs to be replaced when the deployment of the MAE-Access and
base station changes.
The OM channel between the gNodeB and the old MAE-Access is disconnected
during MAE-Access replacement before an OM channel is set up between the
gNodeB and the new MAE-Access. As a result, the gNodeB is not managed by any
MAE-Access.
Table 1-71 shows the reconfiguration procedure for replacing a MAE-Access.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
Table 1-71 Scheme options (IPv4)

If... Then...
The device IP addresses of the existing Add a device IP address on the

gNodeB cannot meet requirements gNodeB.
when both the old and new MAE-
Accesses exist
No route is available between the Add a route from the gNodeB to the
gNodeB and the new MAE-Access new MAE-Access and the
corresponding VLANMAP MO.a
A new IP route has been added Remove the route from the gNodeB to
the old MAE-Access.
A new device IP address has been Remove the old device IP address.
added
a: The network segment on which the gNodeB is located can be calculated

based on the values of Mask and IP Address of the corresponding Ethernet
port.
New Model

5G RAN

to NEW.

If... Then...
The existing IPv4 addresses of the Add a device IPv4 address on the
gNodeB cannot meet requirements gNodeB.
when both old and new MAE-Accesses
exist
corresponding VLANMAP MO.a
A new IPv4 route has been added Remove the route between the
gNodeB and the old MAE-Access.
A new IPv4 address has been added Remove the old IPv4 address.

port.

If... Then...
The existing IP addresses of the Add an IP address on the gNodeB.

gNodeB cannot meet requirements
when both old and new MAE-Accesses
exist
corresponding VLANMAP MO. a
A new IPv6 route has been added Remove the route between the
gNodeB and the old MAE-Access.
A new IPv6 address has been added Remove the old IPv6 address.

port.
Old Model
to OLD.

5G RAN
Figure 1-38 Reconfiguration procedure for replacing a MAE-Access
New Model

to NEW.
Figure 1-39 Procedure for replacing a MAE-Access (IPv4)

5G RAN

5G RAN
Figure 1-40 Reconfiguration procedure for replacing a MAE-Access (IPv6)
NOTE
If the original MAE-Access is faulty, you need to set the route mask to 255.255.255.255 in the
blind-start base station deployment list on the target MAE-Access. After the OM channel is
established, perform the replacement according to the normal process.
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for replacing a MAE-Access,
files, certificates, and data. It also describes the data preparation mode and

Information about The next-hop IP address, destination IP address, subnet

the route from the mask (IPv4)/prefix length (IPv6), and route priority
gNodeB to the new
MAE-Access
Information about The next-hop IP address and ID of the VLAN

the VLAN for the
route from the
gNodeB to the new
MAE-Access
IP address and ● If the new MAE-Access uses multi-server load-

subnet mask (IPv4)/ sharing (SLS), you need to obtain the IP address and
prefix length (IPv6) subnet mask (IPv4)/prefix length (IPv6) of the
of the new MAE- network segment where the new master MAE-Access
Access server is located. The master, slave, and standby
servers of the MAE-Access are located on the same
network segment.
● If the new MAE-Access does not use SLS, you need to
obtain the IP address and subnet mask (IPv4)/prefix
length (IPv6) of the new MAE-Access.
Base station version The gNodeB version number and mediation software
information version number

MAE-Access server If no new MAE-Access has been deployed, prepare the

MAE-Access installation server for deploying the MAE-
Access.

5G RAN
Prepare the software listed in Table 1-76 before replacing the MAE-Access.
Table 1-76 Software to be prepared

Software Description
MAE-Access software If no new MAE-Access has been deployed, prepare the

MAE-Access software compatible with the gNodeB for
deploying the MAE-Access.
NE mediation The NE mediation software provides the access

software adaption function for different NEs and versions. NE
mediation software must be installed on the MAE-
Access for the MAE-Access to adapt to NE interfaces
and to obtain and recognize data reported by NEs.

N/A

N/A
Data Preparation
NOTE
This document does not describe how to configure the new MAE-Access. For details, see MAE-
Access-related documentation.

follows:
NOTE
name of the scenario-specific template being "Replacing the MAE-Access (Old

5G RAN
Mode)" or "Replacing the MAE-Access (New Mode)"). For details, see the
script examples.

In the following example, a device IP address and a route are added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
Old Model
to OLD.
/*Adding a new device IP address*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.18", MASK="255.255.255.0";
/*Adding a route from the gNodeB to the new MAE-Access*/
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="172.31.13.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Modifying an OMCH*/
MOD OMCH: FLAG=MASTER, IP="172.31.13.18", MASK="255.255.255.0", PEERIP="10.148.36.103",
PEERMASK="255.255.0.0", BEAR=IPV4, BRT=YES, RTIDX=1, BINDSECONDARYRT=NO,
CHECKTYPE=UDPSESSION, UDPSN=1, USERLABEL=NONE;
/*Removing the IP route from the gNodeB to the old MAE-Access with the Route Index being 0*/
RMV IPRT: RTIDX=0;
/*Removing the old device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.15";
New Model
to NEW.
/*Setting Ethernet port 0*/
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD VLANMAP: NEXTHOPIP= NEXTHOPIP="172.31.13.1", MASK="255.255.255.255",
VLANMODE=SINGLEVLAN, VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address*/
/*Adding an IPv6 address with IPv6 Address ID set to 0, Interface ID set to 0, IPv6 Address set to
2001:DB8::1, and Prefix Length set to 32*/
ADD IPADDR6: IPADDR6ID="0", ITFID=0, IPV6="2001:DB8::1", PFXLEN=32;
/*Adding an IP route from the gNodeB to the new MAE-Access*/

5G RAN

/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="172.31.13.18", MASK="255.255.255.0", PEERIP="10.148.36.103",
PEERMASK="255.255.0.0", BEAR=IPV4, BRT=YES, RTIDX=1, BINDSECONDARYRT=NO,
CHECKTYPE=UDPSESSION, UDPSN=1, USERLABEL=NONE;
/*Removing the IP route from the gNodeB to the old MAE-Access with the Route Index being 0*/
RMV IPROUTE4: RTIDX=0;
/*Removing the old IPv4 address*/
RMV IPADDR4: ITFID=1, IP="172.31.13.15";
RMV INTERFACE: ITFID=1;

This section describes how to replace a MAE-Access locally and remotely.
Prerequisites
Information, software, and data required for replacing a MAE-Access are ready.
Context
NOTICE
To reduce the time when the gNodeB is disconnected from the MAE-Access, set up
the OM channel between the gNodeB and the new MAE-Access first, and then
disconnect the OM channel between the gNodeB and the old MAE-Access.
Procedure
● Local Operation
a. Deploy a new MAE-Access if no MAE-Access has been deployed.
b. Connect the base station to the new MAE-Access.
a. Back up the configuration file so that it can be used to restore the
b. On the MAE-Access menu bar, choose Maintenance > Backup
Management > NE Backup.
c. In the navigation tree of the NE Backup window, select gNodeB. Then,
select the gNodeB whose data is to be backed up in the navigation tree.
d. Click Backup to back up the configuration file to the FTP server.
e. After the backup is successful, click Upload to OSS Server to download
the backup configuration file to the local PC.
f. Deliver the configuration data to the base station and activate it.

5G RAN

command.
CFGFILE command.
iii. Deliver the configuration data to the base station and activate it.
Using MML commands:

command.
CFGFILE command.
----End

This section describes how to verify the reconfiguration for replacing a MAE-
Access.

5G RAN
Procedure
Step 1 Verify that no ALM-25901 Remote Maintenance Link Failure is reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm

according to the instructions in 3900 & 5900 Series Base Station Alarm Reference.
----End

the original state.
Context
The prerequisites for rollback are as follows:
● The original configuration file has been stored on the FTP server.
● The gNodeB communicates with the FTP server properly.
If the reconfiguration fails, the OM channel will be disconnected. Therefore, the

engineering rollback can be performed only locally on the LMT.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.8.2 Changing the Local Maintenance IP Address

the local maintenance IP address.

reconfiguration scheme, and topology changes for changing the local
maintenance IP address.
The local maintenance IP address that was previously planned is inappropriate and
a new plan is required.
During the change of the local maintenance IP address, the base station will be
disconnected from the LMT. After the reconfiguration, use the new local
maintenance IP address to log in to the LMT.
To change the local maintenance IP address, change IP Address and Mask in the
LOCALIP MO (IPv4) or IPv6 Address and Prefix Length in the LOCALIP6 MO
(IPv6) to the target values.
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for changing the local
maintenance IP address, including information collection and preparation of
hardware, software, license files, certificates, and data. It also describes the data
preparation mode.
Base station The base station ID

information
Local maintenance IP The new local maintenance IP address and subnet mask
information
N/A
N/A

N/A

N/A
Data Preparation
Prepare data listed in the following table.
Table 1-78 Data preparation for changing the local maintenance IP address

ation
1 Modi LOCALIP Change the values of IP Address and

fy Mask to the target values.

5G RAN

follows:
NOTE
name of the scenario being "Changing the Local Maintenance IP Address").
For details, see the interactive operation guide 1.11.2 Using the Batch
script examples.

In the following example, the local maintenance IP address is changed to
192.168.0.49, and the subnet mask is changed to 255.255.255.0.

/*Changing the local maintenance IP address to 192.168.0.49*/
SET LOCALIP: IP="192.168.0.49", MASK="255.255.255.0";

This section describes how to change the local maintenance IP address locally and
remotely.
Prerequisites
Information for changing the local maintenance IP address has been collected,

5G RAN
Context
Procedure
● Local Operation
N/A
command.
CFGFILE command.
----End

This section describes how to verify the reconfiguration for changing the local
maintenance IP address.

5G RAN
Procedure
Step 1 Run the LST LOCALIP command to check whether the IP Address and Mask are
consistent with the plan for IPv4 transmission. Check whether the parameter in
the modified configuration data file is correct if the IP Address and Mask are
inconsistent with the plan.
● If it is incorrect, modify the configuration data file again and import the data
file into the MAE-Deployment. Then, perform the operations in Engineering
Implementation again to deliver the data to the base station and activate it.
● If it is correct, an error occurred when the configuration data file was
imported into the MAE-Deployment or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 2 For IPv6 transmission, run the LST LOCALIP6 command to check whether the IPv6
Address is consistent with the plan. Check whether the parameter in the modified
configuration data file is correct if the IPv6 Address is different from the planned
IPv6 address.
● If it is incorrect, modify the configuration data file again and import the data
file into the MAE-Deployment. Then, perform the operations in Engineering
Implementation again to deliver the data to the base station and activate it.
● If it is correct, an error occurred when the configuration data file was
imported into the MAE-Deployment or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei technical
support hotline.
----End

the original state.
Procedure
configuration file.
configuration file.

5G RAN

data.
NOTE

record table.

----End
1.8.3 Changing the Device IP Address (IPv4 Old Model and

IPv6 New Model)
implementation, engineering verification, and engineering rollback for changing a
device IP address.

reconfiguration scheme, and topology changes for changing a device IP address.
The device IP address that was previously planned is inappropriate and a new plan
is required.
● If the device IP address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE after the old OM
channel becomes invalid and before the new OM channel is set up.
● If the device IP address to be changed is used for service transmission, the
service link (for example, an S1 or X2 link) using this IP address will be
reestablished. During the reestablishment, services on the link will be
interrupted.

5G RAN
● If the device IP address to be changed is used for IPsec negotiations, an IPsec

renegotiation is required. During the renegotiation, services on the IPsec
tunnel will be interrupted.
● If related IP information is not completely modified on other NEs and the to-
be-reconstructed base station when you change the device IP address,
network loop may occur.
The following information describes how to reconfigure the device IP address for a
multimode base station (MBTS).
● The same device IP address modification method applies to the separate-MPT
MBTS and single-mode base station. When IP co-transmission is adopted:
– If the IP address is changed on the RAT that does not provide
transmission, the route from the RAT that provides transmission to the
RAT that does not provide transmission needs to be changed, that is,
change "Destination IP" to the new IP address.
– When co-transmission through panel interconnection is adopted, if the IP
address of the interconnected port on the RAT that provides a port for
connecting to the transport network is changed, the route from the RAT
that provides a port for connecting to the transport network to the peer
RAT needs to be changed. That is, change the next-hop IP address to the
new IP address.
The reconfiguration schemes using the MAE-Deployment and using MML
commands are different because you cannot directly change a device IP address
using MML commands.
NOTE
● If the device IP address to be changed is the OM IP address, change the OM IP address to

the new device address for the gNodeB on the MAE-Access after the gNodeB reconfiguration
is completed.
● If the device IP address is used for X2 links and the value of the SCTP Peer ID parameter in
the SCTPPEER MO is the same as the peer base station ID, use the MAE-Deployment to
perform batch configuration to automatically update the configurations on the peer base
station. No manual operation is required.
The DEVIP MO shares associations and configuration restrictions with many MOs.
If the DEVIP MO is modified, these MOs must also be modified. The following
figure shows the associations and restrictions between these MOs.

5G RAN
Figure 1-41 MOs related to the DEVIP MO (IPv4)
MOs highlighted in blue They reference the DEVIP MO.
MOs highlighted in green They share configuration restrictions with the

DEVIP MO.
MOs highlighted in gray They share both reference relationships and

configuration restrictions with the DEVIP MO.
One-way arrows They indicate association relationships.
Figure 1-42 MOs related to the DEVIP MO (IPv6)
MOs highlighted in blue They reference the IPADDR6 MO.

IPADDR6 MO.
The following table describes the reconfiguration scheme using the MAE-
Deployment.
Table 1-79 Reconfiguration scheme (MAE-Deployment, in endpoint mode)
If... Then
- Change the device IP address.

IPv4: DEVIP
IPv6: IPADDR6

5G RAN
If... Then
The device IP address is used for an IP Change the next-hop IP address of the
route, and the new and old device IP IP route to the new gateway IP
addresses are not on the same address.
network segment IPv4: IPRT/SRCIPRT
IPv6: IPROUTE6
Change the next-hop IP address in the

VLANMAP MO to the new gateway IP
address.
VLANMAP
The device IP address is used for an S1 Modify the S1-link-related parameters.

link SCTPHOST
USERPLANEHOST
IP Patha
The device IP address is used for an X2 Modify the X2-link-related parameters.

link SCTPHOST
USERPLANEHOST
IP Patha
The device IP address is used for the Modify the OMCH.

OMCH OMCH
The device IP address is used for an IP Modify the IP clock link.

clock link IPCLKLNK
A link that uses the device IP address Modify the BFD session.
supports Bidirectional Forwarding BFDSESSION
Detection (BFD)
The device IP address is used for IPsec Modify the IPsec-related parameters.
negotiation IKEPEER
ACLRULE
a: Modify the IPPATH MO if an IP path has been configured.
The following table describes the reconfiguration scheme using MML

commands.

5G RAN
Table 1-80 Reconfiguration scheme (MML commands, in endpoint mode)

If... Then
- Add a device IP address by running the

following command:
IPv4: ADD DEVIP
IPv6: ADD IPADDR6
The new and old device IP addresses Modify the services that use the device
are not on the same network segment IP address by running the following
command:
IPv4: ADD VLANMAPa
IPv6: ADD INTERFACE
The device IP address is used for an IP Modify the services that use the device
route IP address by running the following
command:
IPv4: ADD IPRT/ADD SRCIPRTb
IPv6: ADD IPROUTE6
The device IP address is used for an S1 Modify the services that use the device
link IP address by running the following
command:
MOD SCTPHOST
MOD USERPLANEHOST
The device IP address is used for an X2 Modify the services that use the device
link IP address by running the following
command:
MOD SCTPHOST
MOD USERPLANEHOST
The device IP address is used for the Modify the services that use the device
OMCH IP address by running the following
command and change the NE's IP
address using the MAE-Access.
MOD OMCH
The device IP address is used for an IP Modify the services that use the device
clock link IP address by running the following
command:
RMV IPCLKLINK
ADD IPCLKLINK
A link that uses the device IP address Modify the services that use the device
supports Bidirectional Forwarding IP address by running the following
Detection (BFD) command:
MOD BFDSESSION

5G RAN
If... Then
The device IP address is used for IP PM Modify the services that use the device
sessions IP address by running the following
command:
RMV IPPMSESSION
ADD IPPMSESSION
The device IP address is used for Modify the services that use the device
TWAMP IP address by running the following
command:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
The device IP address is used for IPsec Modify the services that use the device
negotiation IP address by running the following
command:
MOD IKEPEER
MOD ACLRULE
The device IP address is used for an IP Remove the MOs that reference the
route device IP address by running the
following command:
IPv4: RMV IPRT/RMV SRCIPRT
IPv6: RMV IPADDR6
The new and old device IP addresses Remove the MOs that reference the
are not on the same network segment device IP address by running the
following command:
IPv4: RMV VLANMAP
- Remove the device IP address by

running the following command:
IPv4: RMV DEVIP
IPv6: RMV IPADDR6
a: After running the command, perform a connectivity test for the next-hop
gateway. You can perform the next step only after the connectivity test is
passed.
b: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.
Topology Changes
N/A

This section describes the engineering preparation for changing a device IP
address, including information collection and preparation of hardware, software,

5G RAN
license files, certificates, and data. It also describes the data preparation mode and
Base station Base station ID

information
Device IP address ● New device IP address and subnet mask

information ● Next hop IP address
● VLANMAP
N/A
N/A

N/A

N/A
Data Preparation
Data to be prepared is listed in the following tables.
Table 1-82 Data preparation for changing a device IP address (MAE-Deployment,

in endpoint mode)

ation
1 Modif IPv4: DEVIP Change IP Address and Mask to their target

y IPv6: values.
IPADDR6

5G RAN

ation
2 Modif IPv4: IPRT/ Change Next Hop IP to the IP address of the

y SRCIPRT gateway for the new device IP address.
IPv6: ● For IPRT, change Next Hop IP to the IP
IPROUTE6 address of the gateway for the new device
IP address.
● For SRCIPRT, change Source IP Address to
the new device IP address and Next Hop IP
to the IP address of the gateway for the
new device IP address.
3 Modif VLANMAP Change Next Hop IP to the IP address of the

y gateway for the new device IP address.
4 Modif SCTPHOST Change First Local IP Address or Second

y Local IP Address to the target value.
5 Modif USERPLANEH Change Local IP Address to the target value.

y OST
6 Modif IP Path If an IP path has been configured, change

y Local IP to the target value.
7 Modif OMCH Change Local IP and Local Mask to their

y target values.
8 Modif IPCLKLNK Change Client IPv4 to the target value.

y
9 Modif BFDSESSION Change Source IP to the target value.

y
10 Modif IKEPEER Change Local IP Address to the target value.

y
11 Modif ACLRULE Change Source IP to the target value.

y
Table 1-83 Data preparation for changing a device IP address (MML commands,
in endpoint mode)
SN Oper MML Configuration Reference
ation Command
Type
1 Add a IPv4: ADD Change the referenced device IP address to the

new DEVIP new device IP address and retain other data
devic IPv6: ADD unchanged.
e IP IPADDR6
addre
ss.

5G RAN

ation Command
Type
2 Modif IPv4: ADD

y the VLANMAP
servic IPv6: ADD
es INTERFACE
that
use IPv4: ADD
the IPRT/ADD
devic SRCIPRT
e IP IPv6: ADD
addre IPROUTE6
ss. MOD
SCTPHOST
MOD
USERPLANEH
OST
MOD OMCH
RMV
IPCLKLINK
ADD
IPCLKLINK
MOD
BFDSESSION
RMV
IPPMSESSION
ADD
IPPMSESSION
MOD
TWAMPCLIEN
T
MOD
TWAMPRESP
ONDER
3 Chan MOD IKEPEER Change Local IP Address to the new device IP

ge address.
the
IKE MOD Change Source IP Address or Destination IP
peer ACLRULE Address to the new device IP address.
and
ACL
rules.

5G RAN

ation Command
Type
4 Remo IPv4: RMV If the device IP address is used for an IP route,

ve IPRT/RMV remove the MOs that reference the device IP
the SRCIPRT address.
MOs IPv6: RMV
that IPADDR6
refere
nce IPv4: RMV If the new and old device IP addresses are not
the VLANMAP on the same network segment, remove the
devic MOs that reference the device IP address.
e IP
addre
ss.
5 Remo IPv4: RMV Remove the old device IP address.

ve DEVIP
the IPv6: RMV
old IPADDR6
devic
e IP
addre
ss.

The recommended reconfiguration methods are as follows:
● If the device IP address to be changed is not the OM IP address, using the
MAE-Deployment for batch reconfiguration is recommended.
● If the device IP address to be changed is used for the X2 interface and it is
expected that the reference to this IP address at the peer base station can be
automatically updated, using the MAE-Deployment for batch reconfiguration
is recommended.
● If the device IP address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE during data delivery
and activation. As a result, the incremental scripts cannot be executed on the
MAE-Deployment. In this case, the reconfiguration using MML commands is
recommended.
Prepare data for each reconfiguration method as follows:
NOTE

name of the scenario being "Changing a Device IP Address"). For details, see

5G RAN

script examples.
Endpoint Mode
In the following example, the device IP address is changed from 192.168.7.186 to
192.168.7.166 and the new device IP address is referenced by the MOs
SCTPHOST, USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
/*Adding a new device IP address*/
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, IP="192.168.7.166", MASK="255.255.252.0";
ADD VLANMAP: NEXTHOPIP="192.168.7.1" , MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an IP route*/
/*If multiple IP routes are associated with the device IP address, add all the associated IP routes.*/
/*Modifying an SCTP host*/
MOD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.7.166";
/*Modifying a user-plane host*/
MOD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.7.166";
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Modifying a BFD session*/
MOD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.168.7.166";
/*Removing an IP PM session*/
RMV IPPMSESSION: IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps:*/
/*Changing the local IP address of the IKE peer to the new device IP address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If Source IP Address in the ACLRULE MO referenced by the IPSECBIND MO is this device IP address,
perform the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the Source IP Address or Destination IP Address that references this
IP address to the new device address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";

5G RAN
/*Removing the IP route*/

/*If multiple IP routes are associated with the device IP address, remove all the associated IP routes. To
query the IP routes associated with the device IP address, run the DSP IPRT command.*/
RMV IPRT: RTIDX=0;
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN mapping
being 192.168.0.1 and the subnet mask being 255.255.255.255*/
RMV VLANMAP: NEXTHOPIP="192.168.0.1", MASK="255.255.255.255";
/*Removing the device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.7.186";

This section describes how to change the device IP address locally and remotely.
Prerequisites
Information for changing device IP addresses has been collected, and
Context
Procedure
● Local Operation
If the device IP address to be changed is the OM IP address, run MML
commands on the LMT to deliver the data to the base station and then
activate the data.
CFGFILE command.
MML Commands on the LMT.

5G RAN
e. (Perform this step if the device IP address is used for the OM channel.)
On the MAE-Access, change the OM IP address of the NE to the new
device IP address.
i. On the menu bar of the MAE-Access, choose Topology > Main
Topology.
ii. In the navigation tree on the left, select the NE.
iii. In the right pane, right-click the NE and choose Property from the
shortcut menu.
iv. In the displayed NE Properties dialog box, set IP Address 1 to the
new device IP address. Then, click OK.
If the device IP address to be changed is not the OM IP address, use the MAE-
Deployment to deliver the data to the base station and activate the data.

perform the reconfiguration.
For details, see Setting the gNodeB Maintenance Mode to Expand
Status.
b. Select a proper method to change the device IP address according to the
following table:
If you need to... Then...
Configure X2 using the endpoint Perform c.

mode
c. Run the LST X2SONCONFIGSWITCH command to query the setting of

X2 SON Configuration Switch.
▪ If the X2SON_SETUP_SWITCH and X2INIT_FAIL_DEL_SWITCH

options are not selected, skip this step.
▪ Otherwise, run the MOD X2SONCONFIGSWITCH command with the

X2SON_SETUP_SWITCH and X2INIT_FAIL_DEL_SWITCH options
deselected.
d. Deliver the configuration data to the base station and activate it.
e. After the data reconfiguration is complete, set the gNodeB engineering
f. Restore the settings of the options changed in c.
----End

This section describes how to verify the reconfiguration for changing a device IP
address.

5G RAN
Procedure
Step 1 Verify that no related alarms have been reported.
For example:
● ALM-25886 IP Path Fault
● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault
If any alarm is reported, clear the alarm by referring to 3900 & 5900 Series Base
Station Alarm Reference.
Step 2 Run the LST DEVIP command. Verify that the values of IP Address and Mask are
the same as the planned values.
If the values of IP Address and Mask are inconsistent with the plan, view the
modified configuration data file to check whether they are the same as the
planned values.
----End

the original state.
Context
If the changed device IP address is used as an OM IP address, a rollback cannot be
performed. The following describes the procedure for rolling back a device IP
address that is not used as an OM IP address:
Procedure

5G RAN

configuration file.
configuration file.
data.
NOTE

record table.

----End
1.8.4 Changing the IPv4 Address (IPv4 New Model)

an IPv4 address (new model).
NOTE
This task is applicable only when the TRANSCFGMODE parameter in the GTRANSPARA
MO is set to NEW.

reconfiguration scheme, and topology changes for changing an IPv4 address.

5G RAN
The previous IPv4 address plan is inappropriate and a new plan is required.
● If the IPv4 address to be changed is the OM IP address, the MAE-Access and
MAE-Deployment will be disconnected from the NE after the old OM channel
becomes invalid and before the new OM channel is set up.
● If the IPv4 address to be changed is used for service transmission, the service
link (for example, an S1 or X2 link) using this IP address will be reestablished.
During the reestablishment, services on the link will be interrupted.
● If the IPv4 address to be changed is used for IPsec negotiations, an IPsec
renegotiation is required. During the renegotiation, services on the IPsec
tunnel will be interrupted.
● If related IP information is not completely modified on other NEs and the to-
be-reconstructed base station when you change the IPv4 address, network
loop may occur.
The following information describes how to reconfigure the IPv4 address for a
multimode base station (MBTS).
● If the IPv4 address to be changed is shared by all RATs in a co-MPT MBTS,
such as the OM IP address, the IP Address parameter in the IPADDR4 MO
needs to be changed only once. After the IPv4 address is changed, the MOs
that reference this IP address must be modified on the base station side,
including the OMCH, IPPATH, SCTPLNK, USERPLANEHOST, and SCTPHOST.
In addition, the IPv4 address must be changed to the new one on the peer
devices, such as the MAE-Access, base station controller, and MME/S-GW.
● The method of changing the IPv4 address for the separate-MPT MBTS is the
same as that for a single-mode base station. When IP co-transmission is
adopted:
– If the IP address is changed on the RAT that does not provide a port for
connecting to the transport network, the route from the RAT that
provides a port for connecting to the transport network to the RAT that
does not provide such as port needs to be changed. That is, change the
destination IP address to the new IP address.
– When co-transmission through panel interconnection is adopted, if the IP
address of the interconnected port on the RAT that provides a port for
connecting to the transport network is changed, the route from the RAT
that provides a port for connecting to the transport network to the peer
RAT needs to be changed. That is, change the next-hop IP address to the
new IP address.

5G RAN
NOTE
● For details about how to change IP addresses for GSM, see Reconfiguring eGBTS
Transmission Data in GBSS Reconfiguration Guide (BSC6900) or GBSS Reconfiguration
Guide (BSC6910).
● For details about how to change IP addresses for UMTS, see Reconfiguring NodeB IP
Address in RAN Reconfiguration Guide (BSC6900) or RAN Reconfiguration Guide
(BSC6910).
● For details about how to change IP addresses for LTE, see eRAN Reconfiguration Guide.
You must also modify related information on other NEs and the to-be-reconstructed
base station when changing the IPv4 address.
The reconfiguration schemes using the MAE-Deployment and using MML

commands are different because you cannot directly change an IPv4 address using
MML commands.
NOTE
● If the IPv4 address to be changed is the OM IP address, change the OM IP address for the NE
to the new IPv4 address on the MAE-Access after the gNodeB reconfiguration is completed.
● If the IPv4 address is used for X2 links and the value of the SCTP Peer ID parameter in the
SCTPPEER MO is the same as the peer base station ID, use the MAE-Deployment to perform
batch configuration to automatically update the IPv4 address referenced by the peer base
station. No manual operation is required.
The IPADDR4 MO shares associations and configuration restrictions with many

MOs. If the IPADDR4 MO is modified, these MOs must also be modified. The
following figure shows the associations and restrictions between these MOs.
Figure 1-43 MOs related to the IPADDR4 MO
MOs highlighted in blue They reference the IPADDR4 MO.

IPADDR4 MO.
MOs highlighted in gray They share both reference relationships and

configuration restrictions with the IPADDR4
MO.
When the MAE-Deployment is used, change the corresponding parameters in the

MOs listed in Table 1-84 and Table 1-85 to the new IPv4 address.

5G RAN
● Reconfiguration scheme for changing an IPv4 address (MAE-Deployment, in

endpoint mode)
Table 1-84 Reconfiguration scheme selection (MAE-Deployment, in endpoint

mode)
If... Then
- Change the IPv4 address.

IPADDR4
The IPv4 address is used for an IP Change the next-hop IP address of

route and the new IP address is not the IP route to the new gateway IP
on the same network segment as address.
the original IP address IPROUTE4/SRCIPROUTE4
Change the next-hop IP address in

the VLANMAP MO to the new
gateway IP address.
VLANMAP
The IPv4 address is used for an S1 Modify the S1-link-related

link parameters.
SCTPHOST
USERPLANEHOST
IP Patha
The IPv4 address is used for an X2 Modify the X2-link-related

link parameters.
SCTPHOST
USERPLANEHOST
IP Patha
The IPv4 address is used for the Modify the OMCH.

OMCH OMCH
The IPv4 address is used for an IP Modify the IP clock link.

clock link IPCLKLNK
A link that uses the IPv4 address Modify the BFD session.
supports BFD BFDSESSION
The IPv4 address is used for IPsec Modify the IPsec-related parameters.
negotiation IKEPEER
ACLRULE
a: Modify the IPPATH MO if an IP path has been configured.
The following table describes the reconfiguration scheme using MML

commands.

5G RAN
● Reconfiguration scheme for changing an IPv4 address (MML commands, in

endpoint mode)
Table 1-85 Reconfiguration scheme (MML commands, in endpoint mode)

If... Then
- Add an IPv4 address by running the

following command:
ADD IPADDR4
The new and old device IP addresses Modify the services that use the IPv4
are not on the same network address by running the following
segment command:
ADD VLANMAP/ADD INTERFACEa
The IPv4 address is used for an IP Modify the services that use the IPv4
route address by running the following
command:
ADD IPROUTE4/ADD SRCIPROUTE4b
The IPv4 address is used for an S1 Modify the services that use the IPv4
link address by running the following
command:
MOD SCTPHOST
MOD USERPLANEHOST
The IPv4 address is used for an X2 Modify the services that use the IPv4
link address by running the following
command:
MOD SCTPHOST
MOD USERPLANEHOST
The IPv4 address is used for the Modify the services that use the IPv4
OMCH address by running the following
command and change the NE's IP
address on the MAE-Access.
MOD OMCH
clock link address by running the following
command:
RMV IPCLKLINK
ADD IPCLKLINK
A link that uses the IPv4 address Modify the services that use the IPv4
supports BFD address by running the following
command:
MOD BFDSESSION

5G RAN
If... Then
PM session address by running the following
command:
RMV IPPMSESSION
ADD IPPMSESSION
The IPv4 address is used for TWAMP Modify the services that use the IPv4
address by running the following
command:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
The IPv4 address is used for IPsec Modify the services that use the IPv4
negotiation address by running the following
command:
MOD IKEPEER
MOD ACLRULE
The IPv4 address is used for an IP Remove the MOs that reference the
route IPv4 address by running the
following commands:
RMV IPROUTE4/RMV SRCIPROUTE4
The new and old device IP addresses Remove the MOs that reference the
are not on the same network IPv4 address by running the
segment following commands:
RMV VLANMAP
- Remove the IPv4 address by running

the following command:
RMV IPADDR4 /RMV INTERFACE
a: After running the command, perform a connectivity test for the next-hop
gateway. You can perform the next step only after the connectivity test is
passed.
b: To simplify configurations when one device IP address maps multiple
Topology Changes
N/A

This section describes the engineering preparation for changing an IPv4 address,
files, certificates, and data. It also describes the data preparation mode and

5G RAN
Base station Base station ID

information
IPv4 address ● New IPv4 address and its subnet mask

information ● Interface of the new IPv4 address
● Next-hop IP address
● VLANMAP
N/A
N/A

N/A

N/A
Data Preparation
Data to be prepared is listed in the following tables.
Table 1-87 Data preparation for changing an IPv4 address (MAE-Deployment, in

endpoint mode)

ation
1 Modi ETHPORT/ Optional:

fy INTERFACE Change Port ID in the ETHPORT MO to
the target value.
Create an INTERFACE MO.
2 Modi IPADDR4 Change IP Address and Mask to their

fy target values.

5G RAN

ation
3 Modi IPROUTE4/ Change Next Hop IP to the IP address of

fy SRCIPROUTE4 the gateway for the new IPv4 address.
4 Modi VLANMAP Change Next Hop IP to the IP address of

fy the gateway for the new IPv4 address.
5 Modi SCTPHOST Change First Local IP Address or Second

fy Local IP Address to the target value.
6 Modi USERPLANEHOST Change Local IP Address to the target

fy value.
7 Modi OMCH Change Local IP and Local Mask to their

fy target values.
8 Modi IPCLKLNK Change Client IPv4 to the target value.

fy
9 Modi BFD Change Source IP to the target value.

fy
10 Modi IPPMSESSION Change Local IP to the target value.

fy
11 Modi TWAMPCLIENT
fy
12 Modi TWAMPRESPONDER
fy
13 Modi IKEPEER
fy
14 Modi ACLRULE Change Source IP to the target value.

fy
Table 1-88 Data preparation for changing an IPv4 address (MML commands, in
endpoint mode)
SN Operati MML Command Configuration Reference
on
Type
1 Add an ADD IPADDR4 Change the referenced IPv4

IPv4 address to the new device IP
address. address and retain other data
unchanged.

5G RAN
SN Operati MML Command Configuration Reference

on
Type
2 Modify ADD VLANMAP

the ADD IPROUTE4/ADD
services SRCIPROUTE4
that use
the IPv4 MOD SCTPHOST
address. MOD USERPLANEHOST
MOD OMCH
RMV IPCLKLINK
ADD IPCLKLINK
MOD BFD
RMV IPPMSESSION
ADD IPPMSESSION
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
3 Change MOD IKEPEER Change Local IP Address to

the IKE the new IPv4 address.
peer
and MOD ACLRULE Change Source IP Address or
ACL Destination IP Address to the
rules. new IPv4 address.
4 Remove RMV IPROUTE4/RMV If the IPv4 address is used for

the SRCIPROUTE4 an IP route, remove the MOs
MOs that reference the IPv4
that address.
referenc
e the RMV VLANMAP If the new and old device IP
IPv4 addresses are not on the same
address. network segment, remove the
MOs that reference the IPv4
address.
5 Remove RMV IPADDR4 /RMV Remove the old IPv4 address.

the old INTERFACE
IPv4
address.

The recommended reconfiguration methods are as follows:
● If the IPv4 address to be changed is not the OM IP address, using the MAE-
Deployment for batch reconfiguration is recommended.

5G RAN
● If the IPv4 address to be changed is used for the X2 interface and it is

expected that the IPv4 address referenced by the peer base station can be
automatically updated, using the MAE-Deployment for batch reconfiguration
is recommended.
● If the IPv4 address to be changed is the OM IP address, the MAE-Access and
MAE-Deployment become disconnected from the NE during data delivery and
activation. As a result, the incremental scripts cannot be executed on the
MAE-Deployment. In this case, the reconfiguration using MML commands is
recommended.
Prepare data for each reconfiguration method as follows:
NOTE

name of the scenario being "Changing the IPv4 Address (New Model)"). For
script examples.
Endpoint Mode
In the following example, the IPv4 address needs to be changed from
192.168.7.186 to 192.168.7.166 and the new IPv4 address is referenced by the
MOs SCTPHOST, USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
/*Setting Ethernet port 0*/
ADD VLANMAP: NEXTHOPIP="192.168.7.1" , MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
/*Adding an IPv4 address*/
/*The new next-hop IP address can be pinged through. */

5G RAN
/*Adding an IP route*/
/*If multiple IP routes are associated with the IPv4 address, add all the associated IP routes.*/
/*Modifying an SCTP host*/
MOD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.7.166";
/*Modifying a user-plane host*/
MOD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.7.166";
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Modifying the BFD configuration*/
MOD BFD: BFDSN=0, SRCIP="192.168.7.166";
/*Removing an IP PM session*/
RMV IPPMSESSION: IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps: */
/*Changing the local IP address of the IKE peer to the new IPv4 address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If Source IP Address in the ACLRULE MO referenced by the IPSECBINDITF MO is this IPv4 address, perform
the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the "Source IP Address" or "Destination IP Address" that references
this IP address to the new IPv4 address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";
/*Removing the IPv4 route*/
/*If multiple IP routes are associated with the IPv4 address, remove all the associated IP routes. To query
the IP routes associated with the IPv4 address, run the DSP IPROUTE4 command.*/
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN mapping
being 192.168.0.1 and the subnet mask being 255.255.255.255*/
/*Removing the IPv4 address*/
RMV IPADDR4: ITFID=1, IP="192.168.7.186";
/*Removing the INTERFACE MO if no IP address is configured on this MO where the old IPv4 address
resides*/
RMV INTERFACE: ITFID=1;

This section describes how to change IPv4 addresses locally and remotely.
Prerequisites
Information for changing IPv4 addresses has been collected, and configuration
data is ready.
Context

5G RAN
Procedure
● Local Operation
If the IPv4 address to be changed is the OM IP address, you are advised to run
MML commands on the LMT to deliver the data to the base station and then
activate the data.

CFGFILE command.
MML Commands on the LMT.
e. (Perform this step if the IPv4 address is used for an OM channel.) On the
MAE-Access, change the OM IP address of the NE to the new IPv4
address.
i. On the menu bar of the MAE-Access, choose Topology > Main
Topology.
ii. In the navigation tree on the left, select the NE.
iii. In the right pane, right-click the NE and choose Property from the
shortcut menu.
iv. In the displayed NE Properties dialog box, set IP Address 1 to the
new IPv4 address, and then click OK.
If the IPv4 address to be changed is not the OM IP address, use the MAE-
Deployment to deliver the data to the base station and then activate the
data.

perform the reconfiguration.
b. Select a proper method to change IPv4 addresses according to the
following table:

5G RAN
If You Need to... Then...
Configure X2 using the endpoint Go to 3.

mode
c. Run the LST GNBX2SONCONFIG command to query the settings of X2

SON Configuration Switch.
▪ If the values of X2 Self-Setup SW and X2 Self-Rmv on Init Self-

Setup Fault SW are Off, perform 4.
▪ Otherwise, run the MOD GNBX2SONCONFIG command with the

X2SON_SETUP_SWITCH and X2INIT_FAIL_DEL_SWITCH options of
the X2 SON Configuration Switch parameter deselected.
d. Deliver the configuration data to the base station and activate it.
e. After the data reconfiguration is complete, set the gNodeB engineering
f. Restore the settings of the options changed in 3.
----End

This section describes how to verify the reconfiguration for changing IPv4
addresses.
Procedure
Step 1 Verify that no related alarms have been reported.
For example:
● ALM-25886 IP Path Fault

● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault
If any alarm is reported, clear the alarm by referring to 3900 & 5900 Series Base
Step 2 Run the LST IPADDR4 command. Verify that the values of IP Address and Mask
are the same as the planned values.

5G RAN
If the values of IP Address and Mask are inconsistent with the plan, view the
modified configuration data file to check whether they are the same as the
planned values.
----End

the original state.
Context
If the changed IPv4 address is used as an OM IP address, a rollback cannot be
performed. The following describes the procedure for rolling back an IPv4 address
that is not used as an OM IP address.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.8.5 Changing the IP Address of a Clock Server

the IP address of a clock server.
Data for the transport network between the gNodeB and the involved clock server
has been configured.

reconfiguration scheme, and topology changes for changing the IP address of a
clock server.
● A gNodeB needs to be connected to another clock server when the serving
clock server becomes unusable.
● The IP address of the serving clock server needs to be changed because of
network replanning.
The gNodeB cannot synchronize with the clock source and handovers associated
with this gNodeB may be affected during the change of the IP address of the clock
server.
Figure 1-44 and Figure 1-47 show the reconfiguration procedures for changing
the IP address of a clock server. Determine the reconfiguration scheme according
to the following table.

5G RAN

If... Then...
gNodeB and the new clock server new clock server and the
corresponding VLANMAP MO.
(MML command) The clock working Change the clock working mode to
mode is manual and the clock source Auto so that operators can remove the
is the IP clock before reconfiguration old IP clock link and add a new IP
clock link.
(MML command) The Clock Working Change Clock Working Mode back to
Mode is changed to Auto Manual.
Old Model
to OLD.
Figure 1-44 Procedure for changing the IP address of a clock server using the
MAE-Deployment (IPv4)
New Model

5G RAN

to NEW.
Figure 1-45 Procedure for changing the IP address of a clock server using the

5G RAN
Figure 1-46 Procedure for changing the IPv6 address of a clock server using the
Old Model
to OLD.

5G RAN
Figure 1-47 Procedure for changing the IP address of a clock server using MML
commands (IPv4)

5G RAN
New Model
to NEW.

5G RAN
commands (IPv4)

5G RAN
commands (IPv6)
Topology Changes
N/A

5G RAN

This section describes the engineering preparation for changing the IP address of a
clock server, including information collection and preparation of hardware,
software, license files, certificates, and data. It also describes the data preparation
mode.

IPv4 address of the new clock server The IPv4 address and subnet mask
IPv6 address of the new clock server The IPv6 address and prefix length
N/A
N/A

N/A

N/A
Data Preparation
NOTE
The clock server setting is common data for a co-MPT multimode base station (MBTS). You only
need to reconfigure the clock server once, and the configuration takes effect for all RATs of the
MBTS.

5G RAN
Table 1-91 Data preparation for changing the IP address of a clock server
onfi rati
gura on
tion
Mod
e
MAE 1 Mod IPCLKL Change the serving IP address to the IP address

- ify NK of the new clock server.
Depl
oym 2 Mod IPv4 Change Destination IP to the IP address of the
ent ify new new clock server.
model:
IPROU
TE4/
SRCIPR
OUTE4
IPv6:
IPROU
TE6
MM 1 Mod TASM Change Clock Working Mode to AUTO(Auto).

L ify
Com
man 2 Dele IPCLKL -
d te NK
3 Add IPCLKL For details about parameter settings, see

NK Synchronization Feature Parameter Description.
4 Add IPv4 To simplify configurations when one device IP

new address corresponds to multiple destination IP
model: addresses, you are advised to configure the
IPROU source IP route.
TE4/ For details about parameter settings, see IP NR
SRCIPR Engineering Guide Feature Parameter
OUTE4 Description.
IPv6:
IPROU
TE6
5 Add IPv4:
VLAN
MAP
IPv6:
N/A
6 Mod IPCLKL Change Clock Working Mode to

ify NK MANUAL(Manual) and set Selected Clock
Source to IP Clock.

5G RAN

follows:
NOTE
name of the scenario-specific template being "Changing the IP Address of a
Clock Server"). For details, see the interactive operation guide 1.11.2 Using
Data.
script examples.

In the following example, the clock working mode is manual, and the device IP
address of the gNodeB is not on the same network segment as the IP address of
the new clock server.
Old Model
to OLD.
/*Setting the clock working mode to AUTO*/
SET CLKMODE: MODE=AUTO;
/*Removing the old IP clock link*/
RMV IPCLKLINK:;
/*Adding a new IP clock link with the serving IP address set to the IP address of the new clock server*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="172.31.13.241", SIP="192.168.0.128",
PROFILETYPE=1588V2;
/*Adding an IP route to the new clock server*/
ADD

5G RAN
PRIO=DISABLE;
/*Setting Clock Working Mode to MANUAL and Selected Clock Source to IPCLK*/
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF;
New Model
to NEW.
/*Setting Clock Working Mode to AUTO*/
SET CLKMODE: MODE=AUTO;
/*Removing the original IP clock link*/
RMV IPCLKLINK:;
/*Adding an IP clock link with the server IP address set to the IP address of the new clock server*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="172.31.13.241", SIP="192.168.0.128",
PROFILETYPE=1588V2;
/*Adding an IP route to the new clock server*/
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group when the
VLANMAP MO is used to configure a VLAN*/
ADD VLANMAP:NEXTHOPIP="172.31.13.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
/*(Optional, required when the INTERFACE MO is used to configure a VLAN) Adding an INTERFACE MO in
which Interface Type is VLAN*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=71, VLAN=101, VRFIDX=0;
/*Setting Clock Working Mode to MANUAL and Selected Clock Source to IPCLK*/
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF;

This section describes how to change the IP address of a clock server locally and
remotely.
Prerequisites
● Information for changing the IP address of a clock server has been collected,
● The new clock server is configured and connected to the gNodeB.
Context
Procedure
● Local Operation
N/A

5G RAN
ii. Deliver the configuration data to the base station and activate it.
command.
----End

This section describes how to verify the modification of the IP address of a clock
server.
Procedure
Step 1 Verify that the following alarms have not been reported:
● ALM-26260 System Clock Failure
● ALM-26262 External Clock Reference Problem
● ALM-26264 System Clock Unlocked
If any alarm is reported, clear the alarm according to the instructions in 3900 &
Step 2 Run the LST IPCLKLINK command to check whether Server IP or Server IPv4/
IPv6 is the same as the IP address of the new clock server.
If not, check whether the Server IP value in the configuration data file is the same
as the IP address of the new clock server.

5G RAN
● If they are not the same, modify the configuration data file and then perform
the operations in Engineering Implementation to deliver the configuration
to the base station and activate the configuration.
● If they are the same, an error has occurred when the data file is imported into
the MAE-Deployment or the configuration is activated on the base station. In
this situation, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 3 Run the DSP IPCLKLINK command, and verify that the value of Link Available
State is Available and the value of Link Active State is Activated.
If the value of Link Available State is Unavailable, ping the IP address of the
clock server to check whether the route between the device IP address (old
model)/IPv4 address (new model)/IPv6 address (new model) of the gNodeB and
the IP address of the clock server is normal.
● If the IP address cannot be pinged, check whether the IP route toward the
clock server is correctly configured.
IPv4 scenario: If the IP route configurations are incorrect, run the RMV IPRT
(old model)/RMV IPROUTE4 (new model) command to remove the IP route,
and then run the ADD IPRT (old model)/ADD IPROUTE4 (new model)
command to add a correct IP route.
IPv6 scenario: If the IPv6 route configurations are incorrect, run the MOD
IPROUTE6/ADD IPROUTE6 command.
If the IP route is correctly configured, check whether the physical link between
the gNodeB and the IP clock server is normal. If the physical link is abnormal,
adjust the physical connection. If the physical link is normal, contact Huawei
● If the IP address can be pinged, contact Huawei technical support or dial the
If the value of Link Active State is Deactivated, run the LST CLKMODE
command to check whether the value of Clock Working Mode is MANUAL and
the value of Selected Clock Source is IP Clock or check whether the value of
Clock Working Mode is AUTO.
● If it is not, run the SET CLKMODE command to change the value of Clock
Working Mode or Selected Clock Source.
● If it is, contact Huawei technical support or dial the Huawei technical support
hotline.
Step 4 Run the DSP CLKSTAT command. Wait for more than 10 minutes, and check
whether the value of PLL Status is Locked.
If it is not Locked, contact Huawei technical support or dial the Huawei technical
support hotline.
----End

the original state.

5G RAN
Procedure
configuration file.
configuration file.
data.
NOTE

record table.

----End
1.8.6 Optimizing the Transmission Configuration Model

This section describes how to optimize the transmission configuration model.

5G RAN

reconfiguration scheme, and topology changes for optimizing the transmission
configuration model.
The traditional transmission network configuration is complicated and struggles to
meet the requirement for fast deployment on the live network. Therefore, the
transmission configuration model needs to be optimized to simplify operations.
During the change of the transmission configuration model, the corresponding
transmission links will be interrupted, and the services carried on these
transmission links will be interrupted for 3–10 minutes. The following alarms may
be reported during the change, and they will be cleared after the change:
ALM-29800 gNodeB X2 Interface Fault, ALM-29810 gNodeB Xn Interface Fault,
ALM-29815 gNodeB NG Interface Fault, and ALM-29816 gNodeB NG Control
Plane Transmission Interruption.
The transmission configuration model can be optimized in the following ways:
1. Change the transmission configuration model from an old model to a new
model. Cancel the need for configuring the cabinet, subrack, and slot numbers
during the transmission configuration.
2. Optimize the VLAN for a base station using the new transmission
configuration model to make it support IPv6.
3. Change the transmission configuration model from an old model to a new
model and optimize the VLAN.
The transmission configuration model can be changed for a maximum of 100 base
stations simultaneously.
NOTE
The base station transmission model cannot be changed from the new model to the old
model.
Restrictions:
1. Changing the transmission configuration model from an old model to a new
model does not apply to a GSM base station that uses the GTMU as a main
control board.
2. Restrictions on the VLAN optimization scheme are as follows:
– The following boards do not support this scheme: WMPT, GTMUb, CMPT,
UTRP2, UTRP3, UTRP4, UTRP9, UTRPa, UCIU, ULPU, CMSU, CBPU, UCCU,
and UBBP.
– This scheme is not supported if L2 packet filtering is configured but the
VLAN ID corresponding to L2 packet filtering does not contain the VLAN
IDs of the VLANMAP, VLANCLASS, and SUBNETVLAN MOs. The specific
configuration scenarios are as follows:

5G RAN
▪ The value of the ACTION parameter of the L2 ACLRULE MO

referenced by packet filtering is DENY, and the VLAN corresponding
to the L2 ACLRULE MO has the VLANMAP and VLANCLASS MOs.

referenced by packet filtering is DENY, the VLAN corresponding to
the L2 ACLRULE MO does not have the VLANMAP or VLANCLASS
MO, and the value of the MB parameter of packet filtering is DENY.

referenced by packet filtering is PERMIT, the VLAN corresponding to
the L2 ACLRULE MO does not have the VLANMAP or VLANCLASS
MO, and the value of the MB parameter of packet filtering is DENY.
▪ Only packet filtering is configured but an ACLRULE MO is not, and

the value of the MB parameter of packet filtering is DENY.
3. VLAN optimization is not supported in the following scenario: The
NEXTHOPIP parameter values of the VLANMAP MO are included in the
subnet (that is, the NEXTHOPIP parameter values of N VLANMAP MOs are
in the same network segment as the DEVIP MO, N is greater than or equal to
2, there are inclusion relationships between NEXTHOPIP and MASK
parameter values) but the VLANID parameter values are different. Figure
1-50 and Figure 1-51 show the details.
Figure 1-50 Local-end network segment containing the next-hop network

segment

5G RAN
Figure 1-51 Next-hop network segment containing the local-end network

segment
4. VLAN optimization is not supported in the following scenario: The VLANID

parameters of the VLANCLASS MOs, which correspond to the DSCPs
referenced by services, are set to different values. In this case, different VLAN
IDs are set for different types of services (based on application layer packets).
Figure 1-52 shows the details.
Figure 1-52 Scenario not supporting VLAN optimization
5. VLAN optimization is not supported in the eMBMS scenario where a VLAN is

configured for IGMP packets.
6. VLAN optimization is not supported if there is no device IP address in the
same network segment as the NEXTHOPIP parameter value of the
VLANMAP MO. (The configuration is incorrect if there is no such device IP
address.)
7. VLAN optimization is not supported if different VLANMAP MOs are
configured with the same VLAN ID but different VRF indexes.
8. VLAN optimization is not supported if IPsec tunnel pairs are used.
9. When the local IP address of the IKEPEER is 0.0.0.0, VLAN optimization is
under the following restrictions:
– When the local IP address of the IKEPEER MO is 0.0.0.0, only one
transmission port can be provided and the port is an ETH port on the
board where the IKE is located.
– VLAN optimization is not supported if the REDIRECTSW parameter of the
IKEPEER MO is set to ON and the local IP address of the IKEPEER MO is
0.0.0.0.

5G RAN
10. VLAN optimization is not supported if the peer IP address of the IKEPEER MO
has multiple routes (active and standby routes and balanced routes) before
the reconstruction and VLAN IDs of the VLANMAP MOs corresponding to the
next hops of the routes are different from each other.
11. VLAN optimization is not supported if a VLANMAP MO is configured for the
lower-level base station in base station cascading scenarios. Otherwise,
services on the lower-level base station may be interrupted, or the related OM
link may be disconnected. (In normal scenarios, you do not need to configure
the VLANMAP MOs for the lower-level base stations. VLAN configurations are
needed only on the higher-level base station.) You can use the LLDP function
on the FMA to check whether base stations are cascaded.
12. VLAN optimization is not supported if a VLANMAP MO is configured for the
panel not providing the transmission port in panel interconnection scenarios.
Otherwise, services of the RAT not providing the transmission port may be
interrupted, and the related OM link may be disconnected. (In normal
scenarios, you do not need to configure the VLANMAP MOs for the RATs not
providing the transmission port. VLAN configurations are needed only for the
RAT providing the transmission port.) You can use the LLDP function on the
FMA to check whether panels are interconnected.
Topology Change
N/A

This section describes the engineering preparation for changing the transmission
configuration model from an old model to a new model, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode.
Information to be collected describes the information to be collected for data
preparation.

Base station information Name of the base station whose

transmission configuration model
needs to be changed

5G RAN
Whether VLAN optimization is VLAN optimization requires that the

supported by the VLAN of the peer same VLAN ID be configured for the
device connected to the base station if interconnected device (switch or
VLAN optimization is required for the router) to send and receive data.
base station Before implementing VLAN
optimization for the base station
whose transmission configuration
model needs to be changed, run the
STR VLANDETECTION command to
check the configuration of the
interconnected device.
● If the value of VLAN
Reconstruction Switch is Yes in the
command output, VLAN
optimization can be implemented
for the base station whose
transmission configuration model
needs to be changed.
● If the value of VLAN
Reconstruction Switch is No in the
command output, you need to
modify the configurations of the
base station or the peer device.
Otherwise, the base station may be
disconnected and services may be
interrupted.
N/A
5G RAN 2.1 or a later version, and the corresponding MAE-Access and MAE-
Deployment software versions

N/A

N/A
Data Preparation
● Obtain the configuration data of the base station whose transmission
configuration model needs to be changed.

5G RAN
On the MAE-Access, right-click the NE whose transmission configuration

model needs to be changed, and choose Synchronize NE Configuration Data
from the shortcut menu to synchronize data of the NE.
● Enter the input options for changing the transmission configuration model:
– Name of the base station whose transmission configuration model needs
to be changed
– Scheme of optimizing the transmission configuration model. The
optimization schemes include:
i. Change the transmission configuration model from an old one to a
new one.
ii. Optimize the VLAN for a base station using the new transmission
configuration model.
iii. Change the transmission configuration model from an old model to
a new model and optimize the VLAN.

Use the Reconstruction Express function of the MAE-Deployment to change the
transmission configuration model.

This section describes the engineering implementation for changing the
transmission configuration model from an old model to a new model, including
prerequisites, context, and procedure. Only remote operations are supported.
Prerequisites
Information and data required for changing the transmission configuration model
are available.
Context
● Local Operations describe the operations that must be performed onsite,
● Remote Operations describe the operations that must be performed on the
Procedure
Remote Operations (Using the MAE-Deployment)
Step 1 On the menu bar, choose Advanced > Network Enhancement > Reconstruction
Express.
Step 2 Click Export Default Template to obtain the template.
Step 3 In the exported template, enter the name of the NE whose transmission
configuration model needs to be optimized and the sequence number of the
optimization scheme.

5G RAN
Step 4 In Planning Data Table, click to upload the filled template and click Execute.
After that, the import result is displayed in the task information pane in the upper
right area of the home page. (You can also click in the upper right area of the
home page to open the task information pane.)
If the import succeeds, you can expand the task and download the script.
If the import fails, you can expand the task and download the error report. You
can modify the data according to the error information and import the template
again.
Step 5 On the menu bar, choose Advanced > System > Script Executor to import the
script downloaded in the previous step and load the project.
Step 6 Select the loaded project and activate it.
----End

This section describes how to verify the change of the transmission configuration
model.
Procedure
Run the LST GTRANSPARA command to check the value of the Transmission
Configuration Mode parameter. If the parameter value is New, the transmission
configuration model is successfully changed.

Perform the following operations to roll back the configuration data:
Step 1 On the menu bar of the MAE-Deployment, choose Advanced > System > Script
Executor.
Step 2 Select the target project and select Activate Fallback Project.
Step 3 Run the LST GTRANSPARA command and check the value of Transmission
Configuration Mode. If it is Old, the old transmission configuration model has
been used and the transmission configuration model has been rolled back.
----End
1.9 Security Networking Data Reconfigurations

This section describes how to reconfigure gNodeB security networking data in
typical scenarios.

5G RAN
1.9.1 Changing a Single IPsec Tunnel to an IPsec Tunnel Pair

(Only for IPv4 Transmission)
reconfiguration scheme, and topology changes for changing a single IPsec tunnel
to an IPsec tunnel pair.
The operator requires the use of an IPsec tunnel pair to enhance transmission
network security.
None
Figure 1-53 shows the reconfiguration procedure for changing a single IPsec
tunnel to an IPsec tunnel pair. Determine the reconfiguration scheme according to
the following table.

If... Then...
The local IP address of the Change the local IP address of the original IKE
original IKE peer is 0.0.0.0 peer to the actual device IP address.
Either of the IPsec tunnels uses Bind the added IPsec tunnel to the IPsec
one port security policy group.
The IPsec tunnel pair uses only Do not bind the added IPsec tunnel to the
one port IPsec security policy group.
Old Model
to OLD.

5G RAN
Figure 1-53 Procedure for changing a single IPsec tunnel to an IPsec tunnel pair
New Model
to NEW.

5G RAN
Figure 1-54 Procedure for changing a single IPsec tunnel to an IPsec tunnel pair
Topology Changes
The following figure shows the topologies before and after the reconfiguration.

5G RAN

This section describes the engineering preparation for changing a single IPsec
tunnel to an IPsec tunnel pair, including information collection and preparation of
hardware, software, license files, certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

IPsec policy group The IKE proposal name, IPsec proposal name, access
information control list (ACL) ID, and IPsec SA life cycle
Local IKE information The local IKE name, pre-shared key, IKE version, and
negotiation mode
Information about The IP address and subnet mask of the new SeGW and
the routes from the the next-hop IP address of the routes
gNodeB to the new
SeGW

5G RAN

the VLAN for the
route from the
gNodeB to the new
SeGW
SeGW Supports the firewall or router that complies

with the IPsec protocol.
N/A


N/A
Data Preparation
Old Model

to OLD.
Table 1-96 Data preparation for changing a single IPsec tunnel to an IPsec tunnel
pair

ation
1 Modif IKEPEER Change Local IP Address of the original IKE

y peer to the actual device IP address.

5G RAN

ation
2 Add IKEPEER For details, see IPsec Feature Parameter

Description.
3 Add IPSECPOLICY
4 Add IPSECBIND
5 Add IPRT/ For details about parameter settings, see IP

SRCIPRTa NR Engineering Guide Feature Parameter
Description.
6 Add VLANMAP
7 Add IPSECDTNL Add an IPsec tunnel pair.

For details, see IPsec Feature Parameter
Description.
a: To simplify configurations when one device IP address maps multiple
New Model
to NEW.

ation
1 Modif IKEPEER Change Local IP Address of the original IKE

y peer to the actual device IP address.
2 Add INTERFACE For details about parameter settings, see IP

NR Engineering Guide Feature Parameter
Description.
2 Add IKEPEER For details, see IPsec Feature Parameter

Description.
3 Add IIPSECPOLICY
4 Add IPSECBIND
5 Add IPROUTE4/ For details about parameter settings, see IP

SRCIPROUTE4 NR Engineering Guide Feature Parameter
a Description.
6 Add VLANMAP
7 Add IPSECDTNL Add an IPsec tunnel pair.

For details, see IPsec Feature Parameter
Description.
a: To simplify configurations when one device IP address maps multiple

5G RAN

In this scenario, the configuration by running MML commands is recommended.
Prepare MML configuration scripts based on the preceding data preparation
procedure and the following example of MML configuration scripts.

In the following example, either of the two IPsec tunnels is set up on one port,
and the PSK authentication mode is used.

NOTE
If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
Old Model

to OLD.
/*Exporting the current license file to the ftproot folder of the MAE-Access server for backup purposes*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
/*Importing a new license file from the ftproot folder on the MAE-Access server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the original IKE peer*/
MOD IKEPEER: PEERNAME="ikepeer1", LOCALIP="192.168.53.13";
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer2", PROPID=2, IKEVERSION=IKE_V1, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.53.8", REMOTENAME="segw", DPD=PERIODIC,
LOCALIP="192.168.53.13";
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol2", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer2", LTCFG=LOCAL;
/*Binding an IPsec policy group to a port*/
ADD IPSECBIND: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, SPGN="ipsecpol2";
/*Adding an IP route from the gNodeB to the new SeGW*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Adding an IPsec tunnel pair*/
ADD IPSECDTNL: DUALID=1, MSPGN="ipsecpol2", MSPSN=1, SSPGN="ipsecpol2", SSPSN=1,
BFDDTCTSW=OFF, IPSECSWITCHBACK=OFF;
New Model

to NEW.

5G RAN
/*Exporting the current license file to the ftproot folder of the MAE-Access server for backup purposes*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
/*Importing a new license file from the ftproot folder on the MAE-Access server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the original IKE peer*/
MOD IKEPEER: PEERNAME="ikepeer1", LOCALIP="192.168.53.13";
/*Adding an interface*/
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, TAGGED=ENABLE, VLANID=101, VRFIDX=0;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer2", PROPID=2, IKEVERSION=IKE_V1,
EXCHMODE=AGGRESSIVE,IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.53.8",
REMOTENAME="segw", DPD=PERIODIC, LOCALIP="192.168.53.14";
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol2", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer2", LTCFG=LOCAL;
/*Binding an IPsec policy group to an interface*/
ADD IPSECBINDITF: IPSECBINDITFID=2, SPGN="ipsecpol2", ITFID=1;
NEXTHOP="192.168.53.110", MTUSWITCH=OFF, PREF=100;
/*Adding an IPsec tunnel pair*/
ADD IPSECDTNL: DUALID=1, MSPGN="ipsecpol2", MSPSN=1, SSPGN="ipsecpol2", SSPSN=1,
BFDDTCTSW=OFF, IPSECSWITCHBACK=OFF;

This section describes how to change a single IPsec tunnel to an IPsec tunnel pair
locally and remotely.
Prerequisites
Information for changing a single IPsec tunnel to an IPsec tunnel pair has been
collected, hardware and configuration data are ready, and the license file is
available in the corresponding path on the FTP server.
Context
Procedure
● Local Operation
a. Deploy a new SeGW, connect it to the core network and MAE-Access.
b. Connect another port (which does not carry the original IPsec tunnel) of
the base station to the new SeGW.
The "MML command" mode on the MAE-Access is recommended for remote
operation. The following describes only this mode.

5G RAN

CFGFILE command.
----End

This section describes how to verify the reconfiguration for changing a single IPsec
tunnel to an IPsec tunnel pair.
Context
The physical link that carries the active or standby tunnel is normal.
NOTE
The active and standby tunnels must be verified during the engineering verification. The
procedures for verifying the active and standby tunnels are the same. You must verify the
active tunnel and then the standby tunnel according to the instructions provided in the
Procedure section.
Procedure
Step 1 Verify that no ALM-29240 Cell Unavailable or ALM-25901 Remote
Maintenance Link Failure has been reported.
If ALM-29240 Cell Unavailable or ALM-25901 Remote Maintenance Link
Failure has been reported, clear the alarm by referring to 3900 & 5900 Series Base
Step 2 Run the DSP IKESA command to check whether each SA Flag is Ready|StayAlive.
In addition, check whether the number of ACL rules at which User Display Phase
is Phase2 (indicating that the IPsec SA is established) is the same as the number
of ACL rules planned for IPsec SA establishment. Then, check whether Rule ID is
unique and not NULL.
If SA Flag is not Ready|StayAlive, perform the following steps:
1. Check whether ALM-25891 IKE Negotiation Failure has been reported.

5G RAN
– If any alarm is reported, clear the alarm according to the instructions in

3900 & 5900 Series Base Station Alarm Reference. After the alarm is
cleared, if the value of SA Flag is still not Ready|StayAlive, go to Step
2.2.
– If no alarm is reported, go to Step 2.2.
2. Run the corresponding commands on the SeGW to query the IKE proposal
and IKE peer based on the SeGW model. Check whether the IKE
configurations of the SeGW are correct, including the device certificate,
operator trust certificate, and pre-shared key.
– If they are incorrect, modify the configurations. If the value of SA Flag is
still not Ready|StayAlive after the configurations are modified, go to
Step 2.3.
– If they are correct, go to Step 2.3.
3. Check whether the configurations of the IPsec proposal and IPsec policy for
the gNodeB are the same as the corresponding parameters of the SeGW.
– If they are not the same, modify the configurations. If the value of SA
Flag is still not Ready|StayAlive after the configurations are modified,
contact Huawei technical support or dial the Huawei technical support
hotline.
– If they are the same, contact Huawei technical support or dial the
If the number of ACL rules at which User Display Phase is Phase2 (indicating that
the IPsec SA is established) is not the same as the number of ACL rules planned
for IPsec SA establishment, perform the following steps:
1. Identify the missing ACL rule or the ACL rule for which the value of SA Flag is
None by comparing the ACL rules with the planned ones.
2. Run the LST ACLRULE command to check whether the ACL rules match those
of the SeGW.
– If they do not match, modify the configurations. If the problem persists
after the configurations are modified, contact Huawei technical support
– If they match, contact Huawei technical support or dial the Huawei
----End

the original state.
Procedure
● On the MAE-Access, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.

5G RAN

USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the configuration file.
● Roll back the configuration data using the one-click blind configuration
rollback function.
information.
NOTE

command to query the value of this parameter.
the rollback.
▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.
Step 2 (Optional. Perform this step if the license file is updated.) Import the pre-
reconfiguration license file.
Run the INS LICENSE command.

----End
1.9.2 Changing a Single Virtual Route to Active/Standby Static

IP Routes
implementation, engineering verification, and engineering rollback for changing a
single virtual route to active/standby static IP routes.
Prerequisites
The standby route has been deployed, and related data has been configured.

5G RAN

reconfiguration scheme, and topology changes for changing a single virtual route
to active/standby static IP routes.
When the transport network does not adopt Virtual Router Redundancy Protocol
(VRRP), a single virtual route needs to be changed to active/standby static routes
for the base station to ensure transmission reliability.
None
Figure 1-56 shows a reconfiguration procedure for changing a single virtual route
to active/standby static routes.
NOTE
The two new routes must have higher priorities than the old route toward the original VRRP
virtual address. Of the two new routes, the active route must have a higher priority than the
standby route.
Old Model
to OLD.
Figure 1-56 Reconfiguration procedure for changing a single virtual route to

active/standby static routes (IPv4)

5G RAN
New Model
to NEW.



5G RAN
Topology Changes
Figure 1-59 shows the topology changes related to the reconfiguration by using
the modification of the route to the MME as an example.

This section describes the engineering preparation for changing a single virtual
route to active/standby static routes, including information collection and
preparation of hardware, software, license files, certificates, and data. It also
describes the data preparation mode and provides MML configuration script
examples.
Information about The next-hop IP address and subnet mask (IPv4)/prefix

the new active route length (IPv6) of the active route

the VLAN for the
new active route
Information about The next-hop IP address and subnet mask of the

the new standby standby route
route

5G RAN

the VLAN for the
new standby route
Information about The next-hop IP address and subnet mask of the old
the old route to the route
original VRRP virtual
address
BFD session The BFD session IDs and DSCP values of the active and
information (old standby routes
model)/Bidirectional
Forwarding Detection
information (new
model)
Cable used to connect the gNodeB to The cables can be Ethernet cables or
a router optical fibers, depending on the peer
router.
N/A
N/A

N/A

N/A
Data Preparation

5G RAN
Table 1-99 Data preparation for changing a single virtual route to active/standby
static routes
ation
1 Add IPv4: IPRT/ Add active and standby IP routes. The two
IPROUTE4 routes have higher priorities than the old
IPv6: route toward the original VRRP virtual
IPROUTE6 address. The active route has a higher priority
than the standby route.
2 Add IPv4: For details about parameter settings, see IP
(optional) NR Engineering Guide Feature Parameter
VLANMAP Description.
IPv6: N/A
3 Add BFDSESSION Add two BFD sessions for the new active and
standby routes.
For details about parameter settings, see IP
Description.
4 Delet IPv4: IPRT/ Delete the IP route that defines the old route
e IPROUTE4 to the original VRRP virtual address.
IPv6:
IPROUTE6

follows:
NOTE
name of the scenario-specific template being "Changing a Single Virtual
Route to Active/Standby Static IP Route"). For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.

5G RAN

script examples.

In the following example, the priority of the old route to the original VRRP virtual
address is 60.
Old Model
to OLD.
/*Adding a new active route that has a higher priority than the old route to the original VRRP virtual
address*/
RTTYPE=NEXTHOP, NEXTHOP="192.81.54.7", MTUSWITCH=OFF, PREF=20;
/*Adding a new standby route that has a higher priority than the old route to the original VRRP virtual
address, and a lower priority than the new active route*/
RTTYPE=NEXTHOP, NEXTHOP="192.81.53.7", MTUSWITCH=OFF, PREF=30;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group for the new
active route*/
ADD
PRIO=DISABLE;
standby route*/
ADD
PRIO=DISABLE;
/*Adding a BFD session for the active route*/
ADD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.81.54.6", DSTIP="192.81.54.7", HT=SINGLE_HOP, DSCP=63;
/*Adding a BFD session for the standby route*/
ADD BFDSESSION: SN=7, BFDSN=1, SRCIP="192.81.53.6", DSTIP="192.81.53.7", HT=SINGLE_HOP, DSCP=63;
/*Removing the old route to the original VRRP virtual address with the Route Index of 3*/
RMV IPRT: RTIDX=3;
New Model
to NEW.
/*Adding a new active route that has a higher priority than the old route toward the original VRRP virtual
address*/
/*Adding a new standby route that has a higher priority than the old route toward the original VRRP virtual
address but a lower priority than the new active route*/
/*Setting an Ethernet port*/

5G RAN
active route*/
ADD
PRIO=DISABLE;
standby route*/
ADD
PRIO=DISABLE;
/*Adding a BFD for the active route*/
ADD BFD: SN=7, BFDSN=0, SRCIP="192.81.54.6", DSTIP="192.81.54.7", HT=SINGLE_HOP, DSCP=63;
/*Adding a BFD for the standby route*/
ADD BFD: BFDSN=1, SRCIP="192.81.53.6", DSTIP="192.81.53.7", MYDISCREAMINATOR =1,
HT=SINGLE_HOP, DSCP=63;
/*Removing the old route toward the original VRRP virtual address with the Route Index of 3*/

This section describes how to change a single virtual route to active/standby static
routes locally and remotely.
Prerequisites
Information for changing a single virtual route to active/standby static routes has
been collected, and hardware and configuration data are ready.
Context
Procedure
● Local Operation
Connect the base station to a router.


5G RAN

command.
CFGFILE command.
----End

This section describes how to verify the change from a single virtual route to
active/standby static routes.
Procedure
Step 1 Disable the active route (for example, by running RMV IPRT (old model)/RMV
IPROUTE4 (new model) to remove the active route), and check whether the
standby route is automatically enabled.
Run DSP IPRT (old model)/DSP IPROUTE4 (new model) to check whether the
standby route is valid.
If the standby route is not automatically enabled, check whether the standby
route configuration is correct:
● If it is incorrect, rectify the standby route configuration.
● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 2 Verify that the services carried on the standby route are normal.
If the services are abnormal, for example, a remote maintenance link, S1 link, X2
link, or clock link is abnormal, check whether the following alarms are reported:
ALM-25901 Remote Maintenance Link Failure, ALM-29201 S1 Interface Fault,
ALM-29204 X2 Interface Fault, and ALM-26262 External Clock Reference
Problem.
● If any alarm is reported, clear the alarm according to the instructions in 3900
& 5900 Series Base Station Alarm Reference.
● If no alarm is reported, contact Huawei technical support or dial the Huawei

5G RAN
NOTICE
After the verification, restore the active route. For example, if you have disabled
the active route by removing the active route, run ADD IPRT (old model)/DSP
IPROUTE4 (new model) to add the active route after the verification.
----End

the original state.
Procedure
configuration file.
configuration file.
data.
NOTE

record table.

5G RAN

----End
1.9.3 Replacing an SeGW

implementation, engineering verification, and engineering rollback for replacing
the security gateway (SeGW) for a gNodeB.
Prerequisites
● An IP address has been configured for the new SeGW, and the routes to the
gNodeB, MAE-Access, and core network have been configured.
● An Internet Key Exchange (IKE) and Internet Protocol Security (IPsec) have
been configured for the new SeGW.
● The trust certificate and device certificate of the operator have been loaded
on the new SeGW if a public key infrastructure (PKI) is used.
● The routes to the gNodeB have been modified on the MAE-Access and core
network if the next hops from the MAE-Access and core network to the
gNodeB have changed.

reconfiguration scheme, and topology changes for replacing a security gateway
(SeGW).
The networking of an operator is adjusted and a gNodeB needs to be connected
to a new SeGW.
The transport links protected by the old SeGW and services carried on the links
will be interrupted.
Figure 1-60 shows the reconfiguration procedure for replacing an SeGW.
If... Then...
gNodeB and the new SeGW new SeGW and the corresponding
VLANMAP MO.

5G RAN
If... Then...
An IKE peer name has been configured Change the IKE peer name to the
on the gNodeB, the local SeGW ID type is FQDN of the new SeGW.
a fully qualified domain name (FQDN),
and the FQDN of the new SeGW is
different from that of the old SeGW
The value of the Destination IP Remove the route from the gNodeB
parameter for the route from the gNodeB to the old SeGW.
to the old SeGW is the IP address of the
old SeGW, but not the IP address of the
network segment where the old SeGW is
located
NOTE
Removing the route from the gNodeB to the old SeGW prevents redundant data. However, if the
Destination IP value configured for the route from the gNodeB to the old SeGW is the IP
address of the network segment where the old SeGW is located, do not remove this route
because the gNodeB may use this IP address to communicate with other devices on the network
segment.
Old Model
to OLD.

5G RAN
Figure 1-60 Procedure for replacing an SeGW (IPv4)
New Model
to NEW.

5G RAN

5G RAN
Topology Changes
N/A

This section describes the engineering preparation for replacing a security gateway
(SeGW), including information collection and preparation of hardware, software,
license files, certificates, and data. It also describes the data preparation mode and
IP address of the new The IP address and subnet mask (IPv4)/prefix length
SeGW (IPv6)

5G RAN
Local ID type of the The following two types are available:

new SeGW ● Fully qualified domain name (FQDN). If the local ID
type is an FQDN, obtain also the local FQDN of the
new SeGW.
● IP. If the local ID type is IP, obtain the IP address of
the new SeGW.
Information about Required for configuring the route from the gNodeB to
the next hop from the new SeGW
the gNodeB to the
new SeGW
Before reconfiguration, prepare the hardware listed in Table 1-102.
SeGW Supports the firewall or router that complies

with the IPsec protocol.
N/A

N/A

N/A
Data Preparation
Old Model

to OLD.

5G RAN
Table 1-103 Data preparation for replacing an SeGW (IPv4)

ation
1 Add IPv4: IPRT/ Add an IP route from the gNodeB to the new
SRCIPRT SeGW.
IPv6: To simplify configurations when one device IP
IPROUTE6 address corresponds to multiple destination IP
addresses, you are advised to configure the
2 Add IPv4: source IP route.
VLANMAP
IPv6: N/A NR Engineering Guide Feature Parameter
Description.
3 Modif IKEPEER ● Change Remote IP Address to the IP

y address of the new SeGW.
● If the peer IKE name has been configured
on the gNodeB, the local SeGW ID type is a
fully qualified domain name (FQDN), and
the FQDN of the new SeGW is different
from that of the old SeGW, you also need
to change Remote Name to the FQDN of
the new SeGW.
4 Delet IPv4: IPRT/ Remove the route from the gNodeB to the old
e SRCIPRT SeGW.
IPv6:
IPROUTE6
New Model

to NEW.
The following table describes the data preparation for replacing an SeGW when
the IPSec Bind Mode parameter in the IKECFG MO is set to SINGLE(Single).

ation
1 Modif (Optional) Add an IP route from the gNodeB to the new

y INTERFACE SeGW.
To simplify configurations when one device IP
2 Add (Optional)
address corresponds to multiple destination IP
VLANMAP
3 Add (Optional) source IP route.
IPADDR4

5G RAN

ation
4 Add IPROUTE4/ For details about parameter settings, see IP

SRCIPROUTE4 NR Engineering Guide Feature Parameter
Description.

the new SeGW.
6 Modif (Optional) Change the interface to which an IPsec policy

y IIPSECBINDIT group is bound by binding the IPsec policy
F group to the new VLAN interface.
7 Delet IPROUTE4/ Remove the route from the gNodeB to the old
ed SRCIPROUTE4 SeGW.

ation
1 Add IPROUTE6 Add an IP route from the gNodeB to the new

SeGW.
To simplify configurations when one device IP
address corresponds to multiple destination IP
source IP route.
Description.

the new SeGW.
4 Delet IPROUTE6 Remove the route from the gNodeB to the old
ed SeGW.

5G RAN

follows:
NOTE
name of the scenario-specific template being "Replacing an SeGW (Old
Mode)" or "Replacing an SeGW (New Mode)"). For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
script examples.

In the following example, the gNodeB and new SeGW are not on the same
network segment, the IKE peer name needs to be modified, and the route from
the gNodeB to the old SeGW needs to be removed.

Old Model

to OLD.
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Changing the remote IP address and remote name of the IKE peer*/
MOD IKEPEER: PEERNAME="enb", REMOTEIP="192.168.52.7", REMOTENAME="newsegw";
/*Removing the IP route from the gNodeB to the old SeGW with the Route Index of 0*/
RMV IPRT: RTIDX=0;

5G RAN
New Model
● The Transmission Configuration Mode parameter in the GTRANSPARA MO

is set to NEW.
● In the following example, the IPSec Bind Mode parameter in the IKECFG MO
is set to SINGLE(Single), and VLAN mapping is used.
ADD VLANMAP:
NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SETPRIO=D
ISABLE;
/*Changing the remote IP address and remote name of the IKE peer*/
MOD IKEPEER: PEERNAME="enb", REMOTEIP="192.168.52.7", REMOTENAME="newsegw";
/*Removing the IP route from the gNodeB to the old SeGW with the Route Index of 0*/

This section describes how to replace a security gateway (SeGW) locally and
remotely.
Prerequisites
Information for replacing an SeGW has been collected, and hardware and
configuration data are ready.
Context
Procedure
● Local Operation
Connect the gNodeB to the new SeGW.


5G RAN

command.
CFGFILE command.
----End
Follow-up Procedure
After the operations in Procedure are performed, modify the configuration of the
router connected to the new SeGW in the transport network. If the destination IP
address is the device IP address of the gNodeB connected to the old SeGW, change
the next-hop IP address to the IP address of the new SeGW. This action ensures
that data exchange between the core network or MAE-Access and the gNodeB
uses the IPsec tunnel.

This section describes how to verify the replacement of a security gateway
(SeGW).
Procedure
Step 1 Verify that no ALM-25891 IKE Negotiation Failure has been reported.
If any ALM-25891 IKE Negotiation Failure has been reported, clear the alarm by
Step 2 Run the DSP IKESA command to check whether each SA Flag is Ready|StayAlive.
In addition, check whether the number of ACL rules at which User Display Phase
is Phase2 (indicating that the IPsec SA is established) is the same as the number
of ACL rules planned for IPsec SA establishment. Then, check whether Rule ID is
unique and not NULL.
If SA Flag is not Ready|StayAlive, perform the following steps:
1. Check whether ALM-25891 IKE Negotiation Failure has been reported.

5G RAN
– If any alarm is reported, clear the alarm according to the instructions in

3900 & 5900 Series Base Station Alarm Reference. After the alarm is
cleared, if the value of SA Flag is still not Ready|StayAlive, go to Step
2.2.
– If no alarm is reported, go to Step 2.2.
2. Run the corresponding commands on the SeGW to query the IKE proposal
and IKE peer based on the SeGW model. Check whether the IKE
configurations of the SeGW are correct, including the device certificate,
operator trust certificate, and pre-shared key.
– If they are incorrect, modify the configurations. If the value of SA Flag is
still not Ready|StayAlive after the configurations are modified, go to
Step 2.3.
– If they are correct, go to Step 2.3.
3. Check whether the configurations of the IPsec proposal and IPsec policy for
the gNodeB are the same as the corresponding parameters of the SeGW.
– If they are not the same, modify the configurations. If the value of SA
Flag is still not Ready|StayAlive after the configurations are modified,
contact Huawei technical support or dial the Huawei technical support
hotline.
– If they are the same, contact Huawei technical support or dial the
If the number of ACL rules at which User Display Phase is Phase2 (indicating that
the IPsec SA is established) is not the same as the number of ACL rules planned
for IPsec SA establishment, perform the following steps:
1. Identify the missing ACL rule or the ACL rule for which the value of SA Flag is
None by comparing the ACL rules with the planned ones.
2. Run the LST ACLRULE command to check whether the ACL rules match those
of the SeGW.
– If they do not match, modify the configurations. If the problem persists
after the configurations are modified, contact Huawei technical support
– If they match, contact Huawei technical support or dial the Huawei
Normal for a cell.
output.
Step 4 Verify that no ALM-25886 IP Path Fault has been reported.
If any ALM-25886 IP Path Fault has been reported, clear the alarm by referring to
----End

5G RAN

the original state.
Procedure
● On the LMT, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.
b. Run the ACT CFGFILE command to activate the configuration file.
● Roll back the configuration data using the one-click blind configuration
rollback function.
information.
NOTE

the rollback.

----End
1.9.4 Adjusting a VLAN

implementation, engineering verification, and engineering rollback for adjusting a
VLAN.

5G RAN
Prerequisites
● The VLAN division for associated transmission equipment has been
completed.
● The VLAN for the switch connected directly to the base station has been
adjusted.

reconfiguration scheme, and topology changes for adjusting a VLAN.
Transmission VLANs are re-planned, and VLANs to which transmission links belong
and the VLAN priorities need to be reconfigured.
During VLAN adjustment, the associated transmission channels are disconnected,
and therefore ongoing services are interrupted. For example:
● When the VLAN to which an OM channel belongs is adjusted, the base
station will be disconnected from the EMS.
● When the VLAN to which an S1 interface belongs is adjusted, the S1 interface
will become unusable.
● When the VLAN to which an X2 interface belongs is adjusted, the X2 interface
● When the VLAN to which an IP clock link belongs is adjusted, the IP clock link
Figure 1-63 shows the reconfiguration procedure for adjusting a VLAN. Determine
the reconfiguration scheme according to the following table.
Table 1-106 Scheme options (IPv4 Transmission)

If... Then...
The VLAN mode is VLAN group Modify the settings of the VLANCLASS
and VLANMAP MOs.
The VLAN mode is single VLAN. Modify only the settings of the
VLANMAP MO.
Table 1-107 Scheme options (IPv6 Transmission)

If... Then...
The VLAN ID needs to be changed Change the VLAN ID.

5G RAN
Figure 1-63 Procedure for adjusting a VLAN (IPv4)
Figure 1-64 Procedure for adjusting a VLAN (IPv6)
Topology Changes
N/A

This section describes the engineering preparation for adjusting a VLAN, including
information collection and preparation of hardware, software, license files,
certificates, and data. It also describes the data preparation mode and provides
VLAN ID ID of the adjusted VLAN
Next-hop IP address Next-hop IP address of the gNodeB toward the target

VLAN after the adjustment

5G RAN
N/A
N/A

N/A

N/A
Data Preparation
NOTE
For a co-MPT MBTS, if all RATs share the same VLAN, you only need to modify the VLAN data
once, and the modification takes effect for all RATs.
Table 1-109 Data preparation for adjusting a VLAN (IPv4 transmission)

tion
1 Modify VLANCLASS Change the values of VLAN Group No.,

Traffic Type, VLAN ID, and VLAN Priority to
the target values.
2 Modify VLANMAP Change the values of VLAN Group No.,

VLAN ID, and VLAN Priority to the target
values.
Table 1-110 Data preparation for adjusting a VLAN (IPv6 transmission)

SN Ope MO Configuration Reference
ratio
n
1 Mod INTERFACE Change the value of VLAN ID to the

ify target value.


5G RAN
follows:
NOTE
name of the scenario being "Adjusting the VLAN"). For details, see the
script examples.

In the following example, you need to change the OM VLAN with the VLAN mode
set to VLAN group.

/*Modifying the mapping between the traffic type OM_HIGH and the VLAN priority*/
MOD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_HIGH, VLANID=3, VLANPRIO=3;
*Modifying the mapping between the traffic type OM_LOW and the VLAN priority*/
MOD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_LOW, VLANID=3, VLANPRIO=3;
/*Modifying the settings of the VLANMAP MO*/
MOD VLANMAP: NEXTHOPIP="172.31.13.1", MASK="255.255.255.255", VLANMODE=VLANGROUP,
VLANGROUPNO=0;

This section describes how to adjust a VLAN locally and remotely.
Prerequisites
Information and data required for VLAN adjustment are ready.
Context

5G RAN

Procedure
● Local Operation
N/A
If MML commands are used for reconfiguration, run MML commands on the
LMT to deliver the prepared data to the base station and activate it.

CFGFILE command.
c. On the LMT, deliver the script that is prepared according to Engineering
Preparation > Data Preparation to the base station and activate it. For
detailed operations, see Running MML Commands on the LMT.
If the MAE-Deployment is used for reconfiguration, use the MAE-Deployment

to deliver the prepared data to the base station and activate it.

b. Deliver the configuration data to the base station and activate it.
----End

This section describes how to verify the reconfiguration for adjusting a virtual local
area network (VLAN).

5G RAN
Procedure
Step 1 If the OM VLAN has been adjusted:
1. Verify that no ALM-25901 Remote Maintenance Link Failure is reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm
according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
Step 2 If the service VLAN has been adjusted:
1. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
Fault, or ALM-26262 External Clock Reference Problem is reported.
If any of the preceding alarms has been reported, check whether the VLAN
configurations are correct.
– If they are incorrect, modify the VLAN configurations.
– If they are correct, clear the alarm according to the instructions in 3900 &
----End

the original state.
Procedure
configuration file.
configuration file.
data.

5G RAN
NOTE

record table.

----End
1.9.5 Changing the VLAN Mode from VLAN Group to Single

VLAN (Only for IPv4 Transmission)
the VLAN mode from VLAN group to single VLAN.

reconfiguration scheme, and topology changes for changing the VLAN mode from
VLAN group to single VLAN.
The VLAN mode needs to be changed from VLAN group to single VLAN. The VLAN
groups meet 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 point (DSCP) value,
or service types with an identical DSCP value are assigned the same VLAN priority.
Adjusting the VLAN mode from VLAN group to single VLAN will interrupt the
involved transmission paths and ongoing services. For example:
station will be disconnected from the EMS.

5G RAN
NOTE
The number of VLAN priorities configured for the base station must be less than or equal to the
number of VLAN priorities supported by the user equipment.
Figure 1-65 shows the reconfiguration procedure for changing the VLAN mode
from VLAN group to single VLAN.
Figure 1-65 Reconfiguration procedure for changing the VLAN mode from VLAN
group to single VLAN
Topology Changes
N/A

This section describes the engineering preparation for changing the VLAN mode
from VLAN group to single VLAN, including information collection and preparation
of hardware, software, license files, certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

5G RAN
VLAN ID ID of each VLAN
DSCP priority DSCP values of user data, signaling, high-priority OM

data, low-priority OM data, and other data, and their
corresponding VLAN priorities
N/A
N/A

N/A

N/A
Data Preparation
NOTE
For a co-MPT MBTS, if all RATs share the same VLAN, you only need to modify the VLAN data
once, and the modification takes effect for all RATs.
Table 1-112 Data preparation for changing the VLAN mode from VLAN group to
single VLAN
SN Opera MO Reference
tion
1 Modify DSCPMAP Set Differentiated Service Codepoint and

VLAN Priority to the target values for
service types except for the other data type
based on the configurations of the original
VLAN group.
Set the VLAN priority for services with
Traffic Type set to Other Data to the
default VLAN priority of the base station.

5G RAN
SN Opera MO Reference
tion
2 Modify VLANMAP ● Set VLAN Mode to SINGLEVLAN.

● Change the value of VLAN ID to the
target value.
● Set Set VLAN Priority to DISABLE.
3 Delete VLANCLASS -

follows:
name of the scenario being "Changing the VLAN Mode from VLAN Group to
Single VLAN"). For details, see the interactive operation guide 1.11.2 Using
Data.
script examples.

The following is an example of the MML configuration script for data preparation.
/*Change the mappings between the DSCP values and the VLAN priorities.*/
SET DSCPMAP: DSCP=25, VLANPRIO=3;
/*Change the mapping between the next-hop IP address and the VLAN with the ID of 1.*/
MOD VLANMAP: NEXTHOPIP="10.10.10.10", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
/*Remove the original VLAN group.*/
RMV VLANCLASS:;

5G RAN

This section describes how to adjust the VLAN mode locally and remotely.
Prerequisites
Information and data required for VLAN mode adjustment are ready.
Context
Procedure
● Local Operation
N/A
command.
CFGFILE command.

5G RAN

----End

This section describes how to verify the reconfiguration for changing the VLAN
mode from VLAN group to single VLAN.
Procedure
● If the OM VLAN has been adjusted:
a. Verify that no ALM-25901 Remote Maintenance Link Failure is
reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the

alarm according to the instructions in 3900 & 5900 Series Base Station
Alarm Reference.
● If the service VLAN has been adjusted:
a. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
If any of the preceding alarms has been reported, check whether the
VLAN configurations are correct.
▪ If they are incorrect, modify the VLAN configurations.
▪ If they are correct, clear the alarm according to the instructions in

----End

the original state.
Context
If the VLAN where the OM channel locates fails to be reconfigured, the OM
channel will be disconnected. Then, engineering rollback can be performed only by
running MML commands on the LMT. If the service VLAN mode fails to be
reconfigured, engineering rollback can be performed on the MAE-Deployment or
by running MML commands on the MAE-Access.
Procedure

5G RAN

configuration file.
configuration file.
data.
NOTE

record table.

----End
1.9.6 Changing the VLAN Mode from Single VLAN to Interface

VLAN (Only for IPv4 Transmission)
This section describes how to change the VLAN mode from single VLAN to
interface VLAN.

reconfiguration scheme, and topology changes for changing the VLAN mode from
single VLAN to interface VLAN.

5G RAN
Prerequisites
Before the reconstruction, check whether the configuration of a single VLAN
meets the following conditions: After the VLAN mode is changed to interface
VLAN, the number of used VLAN priorities cannot exceed the number of VLAN
priorities supported by the customer network equipment.
NOTE
● Generally, the customer equipment supports eight VLAN priorities. In this case, this
condition check can be ignored.
● The next hops of multiple VLANMAP MOs cannot be on the same network segment.
● The GTMUb/WMPT/UTRP/UCCU/UBBPe does not support interface VLANs. In IPsec
scenarios, the LMPT supports only four INTERFACE MOs whose Interface Type is VLAN.
The LMPT supports only four VLAN interfaces.
The VLAN configuration mode of the base station is single VLAN, and the
configurations of a single VLAN meet the requirements for reconstructing a single
VLAN to an interface VLAN. See the following table for details.
Table 1-113 Application scenarios

Scenario Is Reconstruction Supported?
There is a unique device IP address that is on Yes

the same network segment as the next-hop
address in the VLANMAP MO.
The values of the Next Hop IP parameter in No

the N VLANMAP MOs are on the same
network segment as the device IP address. (N
is greater than or equal to 2.)
Adjusting the VLAN mode from single VLAN to interface VLAN will interrupt the
involved transmission paths and ongoing services. For example:
station will be disconnected from the OSS.
Figure 1-66 shows the reconfiguration procedure for changing the VLAN mode
from single VLAN to interface VLAN.

5G RAN
Figure 1-66 Procedure for changing the VLAN mode from single VLAN to interface
VLAN
Topology Change
N/A

This section describes the engineering preparation for changing the VLAN mode
from single VLAN to interface VLAN mode, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

5G RAN
Next-hop IP address Next-hop IP address and subnet mask configured in the

and subnet mask VLANMAP MO
DEVIP Find the device IP address that is on the same network

segment as the next-hop IP address in the VLANMAP
MO.
ETHPORT Find the Ethernet port to which the device IP address

belongs.
VLAN ID VLAN ID configured in the VLANMAP MO
Way of setting the ● SETPRIO configured in the VLANMAP MO: This

VLAN priority parameter indicates whether to set a priority for a
single VLAN.
● When this parameter is set to ENABLE, the VLAN
priority is configured in the current VLANMAP MO.
● When this parameter is set to DISABLE, the VLAN
priority is determined according to the mappings
between DSCPs and VLAN priorities. The mappings
can be configured using the SET DSCPMAP
command.
DSCP priority DSCP priority
VLAN priority VLAN priority configured in the VLANMAP MO
The following table lists the information collected based on the preceding table.
You need to check whether the collected information meets the reconstruction
requirements.
● There is a unique device IP address that is on the same network segment as

the next-hop address in the VLANMAP MO.
● After the VLAN mode is changed to interface VLAN, the number of VLAN
priorities in use should be no more than that of the VLAN priorities supported
by customer network equipment.
Table 1-115 Collected information
Next Hop IP and IP1/MASK1 IP2/MASK2

Mask in the
VLANMAP MO
DEVIP That Is on the IP11/MASK1 IP22/MASK1

Same Network
Segment as the Next
Hop IP in the
VLANMAP MO

5G RAN
ETHPORT to Which a ETHPORT1 ETHPORT2

DEVIP Belongs
VLAN ID Configured 10 11
in the VLANMAP MO
VLAN Priority DISABLE/ENABLE DISABLE/ENABLE

Configured in the
VLANMAP MO
VRF Index, 0/1/1 0/1/1

Differentiated
Service Codepoint,
and VLAN Priority in
the DSCPMAP MO
VLAN Priority 2 3
Configured in the
VLANMAP MO
The GTMUb/WMPT/UTRP/UCCU/UBBPe does not support interface VLANs. The
LMPT supports only four VLAN interfaces.
N/A

N/A

N/A
Data Preparation

5G RAN
Table 1-116 Data preparation for changing the VLAN mode from single VLAN to
interface VLAN
Dat MO Setting Notes Data Source Command
a Reference
Type
Port ETH This parameter is User planning SET ETHPORT

ID POR mandatory and
T must be unique.
Diffe DSC Generate a User planning ADD

renti P2P DSCP-to-PCP DSCP2PCPMAP
ated CPM mapping table ADD
servi AP based on the DSCP2PCPREF
ces VLAN priorities
code before the
poin reconstruction,
t and then set the
and mappings
VLA between DSCPs
N and VLAN
prior priorities.
ity
VLA INTE Based on the User planning ADD INTERFACE

N ID RFA VLAN ID
CE configured in the
VLANMAP MO,
create an
INTERFACE MO
in which the
interface type is
VLAN, and then
associate the
INTERFACE MO
with the
DSCP2PCPMAP
MO.
IPv4 IPAD Add the IP User planning ADD IPADDR4

addr DR4 address
ess configured in the
ETHPORT MO to
the INTERFACE
MO.

commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment

5G RAN
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
of the scenario-specific template being "Changing the VLAN Mode from
Single VLAN to Interface VLAN"): For details, see the interactive operation
guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
script examples.

The following is an example of the MML configuration script for data preparation.
//Removing the original VLAN configurations
RMV DSCPMAP: VRFIDX=0;
RMV DEVIP: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.2.10";
//Setting Transmission Configuration Mode to NEW
SET GTRANSPARA: TRANSCFGMODE=NEW;
//Setting the port ID of the Ethernet port (Determine the Ethernet port of the unique device IP address that
is on the same network segment as the next-hop IP address defined in the VLANMAP MO in advance.)
SET ETHPORT: PORTID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD;
//Generating a DSCP-to-PCP mapping table based on the VLAN priorities before the reconstruction, and
then setting the mappings between DSCPs and VLAN priorities
ADD DSCP2PCPMAP: DSCP2PCPMAPID=0;
ADD DSCP2PCPREF: DSCP2PCPMAPID=0, DSCP2PCPREF.DSCP=0, DSCP2PCPREF.PCP=0;
//Creating an INTERFACE MO in which the interface type is VLAN based on the VLAN ID configured in the
VLANMAP MO, and then associating the INTERFACE MO with the DSCP2PCPMAP MO
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLAN=10, DSCP2PCPMAPID=0, VRFIDX=0,
MTU4=1500, ARPPROXY=ENABLE;
//Adding the IP address configured in the ETHPORT MO to the INTERFACE MO
ADD IPADDR4: ITFID=0, IP="192.168.2.10", MASK="255.255.255.0", VRFIDX=0;

This section describes how to change the VLAN mode locally and remotely.
Prerequisites
The information and data for changing the VLAN mode are ready.
Context

5G RAN

Procedure
● Local Operation
N/A
command.
CFGFILE command.
----End

This section describes how to verify the reconfiguration for changing the VLAN
mode from single VLAN to interface VLAN.

5G RAN
Procedure
● Check whether the VLAN configurations are correct.
a. Run the LST DSCP2PCPMAP command to query the configurations of the
mappings between DSCPs and VLAN priorities.
Expected result: The configurations of the mappings between DSCPs and
VLAN priorities are consistent with the planned data.
b. Run the LST INTERFACE command to query VLAN configurations.
Expected result: The VLAN configurations are consistent with the planned
data.
c. Run the LST IPADDR4 command to query IPv4 address configurations.
Expected result: The IPv4 address configurations are consistent with the
planned data.
● If the OM VLAN has been adjusted:
a. Verify that no ALM-25901 Remote Maintenance Link Failure is
reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the
alarm according to the instructions in 3900 & 5900 Series Base Station
Alarm Reference.
● If the service VLAN has been adjusted:
a. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
If any of the preceding alarms has been reported, check whether the
VLAN configurations are correct.
▪ If they are incorrect, modify the VLAN configurations.
▪ If it is correct, clear the alarm according to the instructions in 3900 &

----End

the original state.
Context
If the VLAN where the OM channel locates fails to be reconfigured, the OM
channel will be disconnected. Then, engineering rollback can be performed only by
running MML commands on the LMT. If the service VLAN mode fails to be
reconfigured, engineering rollback can be performed on the MAE-Deployment or
by running MML commands on the MAE-Access.
Procedure

5G RAN

configuration file.
configuration file.
data.
NOTE

record table.

----End
1.10 Reconfigurations Dedicated to the LampSite

Solution
This section provides guidelines for typical reconfigurations dedicated to the
LampSite solution, including solutions for connections between RHUBs and pRRUs
in the LampSite network architecture (specifications and configuration solutions).
Cell Type
pRRU TRP cell: In a pRRU TRP cell, RF combination is applied on one or several
pRRUs that are connected to one or several RHUBs. A pRRU TRP cell corresponds

5G RAN
to one physical cell. As shown in Figure 1-67, Cell 0 is a pRRU TRP cell served by
one pRRU, and Cell 1 is a pRRU TRP cell served by eight pRRUs. As shown in
Figure 1-68, Cell 0 is a pRRU TRP cell served by one pRRU, and Cell 1 is a pRRU
TRP cell served by 16 pRRUs that are connected to two RHUBs.
NOTE
In NR mode, a gNodeB supports RF combination of pRRUs connected to four cascaded

RHUBs on the same CPRI link, and supports a pRRU TRP cell served by up to 16 pRRUs. A
gNodeB, however, does not support a pRRU TRP cell established on different CPRI links.
One RHUB can serve only one NR cell that is also served by another RHUB.
Figure 1-67 pRRU TRP cell networking (1)
Figure 1-68 pRRU TRP cell networking (2)
LampSite Networking Restrictions

● In NR TDD mode, the LampSite solution supports only pRRU TRP cells with a
bandwidth of 40 MHz, 60 MHz, 80 MHz, or 100 MHz.
● A LampSite base station can have up to 192 pRRUs.

5G RAN
1.10.1 Adding an NR TDD Cell

This section describes the application scenario, engineering preparation,
engineering implementation, engineering verification, and engineering rollback for
adding an NR TDD cell.

This section describes the application scenario, reconfiguration impact, topology
change, and reconfiguration scheme for adding an NR TDD cell.
As mobile networks develop, indoor network performance must be improved for
better user experience. The LampSite solution uses pRRUs to provide indoor radio
coverage for densely-populated and closed areas, such as office buildings,
subways, residential areas, and shopping malls, to ensure good user experience. In
the LampSite solution, pRRUs are connected to RHUBs over Ethernet cables and
RHUBs are connected to baseband processing units in the BBU over optical fibers.
Reconfiguring the chain/ring topology causes cells on the chain/ring to be
unavailable.
If the new cell works in an invalid frequency band and pRRU5936s are newly
deployed, the pRRU5936s will reset for the frequency band to take effect when the
new cell is activated (by running the ACT NRCELL command). This interrupts cell
services in other frequency bands.
Topology Change
This example describes the addition of an RHUB, a BBP, pRRUs, and an NR TDD
cell. Figure 1-69 shows the topologies before and after the reconfiguration.

5G RAN
Figure 1-69 Network topologies before and after adding an intra-RHUB NR TDD
cell
This example describes the addition of an NR TDD cell that is served by 16 pRRUs
connected to two RHUBs, and the addition of a baseband processing unit. Figure
1-70 shows the topologies before and after the reconfiguration.

5G RAN
Figure 1-70 Network topologies before and after adding an inter-RHUB NR TDD
cell
Determine the reconfiguration procedure as follows:
● Add baseband processing units and CPRI links if baseband processing units
are insufficient.
● Add RHUBs and CPRI links if RHUBs are insufficient.
● Add CPRI chains/rings and pRRUs.
● Add sectors.
● Add sector equipment.
● Add an NR DU cell.
● Add a TRP for the NR DU cell.
● Add an NR TDD cell.
Figure 1-71 shows the procedure for adding an NR cell.

5G RAN
Figure 1-71 Procedure for adding an NR cell

This section describes the engineering preparation for adding an NR TDD cell,
files, certificates, and data. It also provides an example of MML configuration
scripts.
Table 1-117 describes the information to be collected before adding an NR TDD
cell.

5G RAN
Table 1-117 Information collection
Cell information ● Basic cell information

● TX/RX mode: 2T2R or 4T4R for LampSite NR TDD cells
Baseband processing ● Model: UBBP

unit model ● UBBP working mode: NR
RF module ● Types of the added RF modules (NR cells support only

information setting of MPMU.)
● Port mapping between pRRUs and RHUBs
Topology Network topology of NR cells

NOTE
NR cells support only the chain topology with RRU Topo
Position set to BRANCH(BRANCH).
NR DU cell TRP Information including the TX/RX mode, CPRI compression

information mode, TRP ID, maximum transmit power, and baseband
equipment ID
Sector equipment Information including the sector equipment ID and

information sector ID
NR DU cell coverage Information including the TRP ID, coverage area ID, and
area information sector equipment ID
Before adding an NR TDD cell, prepare new pRRUs, cables, optical modules, and
hardware listed in Table 1-118.
If... Then...
Baseband processing Prepare new baseband processing units.

units are insufficient
RHUBs are insufficient Prepare new RHUBs, cables, and optical modules.
N/A
License Preparation
If the currently used license file does not meet requirements, prepare a new
license file. Table 1-119 lists required licenses.

5G RAN
Table 1-119 Licenses to be prepared (1)
License Control Item License Description
Cell License(per Cell) Controls the number of cells.
Carrier Controls the cell bandwidth.

Bandwidth(per
5MHz)
Power License Controls the cell power.
Table 1-120 lists LampSite licenses to be prepared based on network

requirements.
Table 1-120 Licenses to be prepared (2)
License Control Item License Description
Intra-BBU Baseband Controls the intra-BBU baseband sharing per cell.

Sharing (2T)(per
Cell)
CPRI Controls the CPRI compression.

Compression(per
Cell)
N/A
Data Preparation
Table 1-121 lists the data to be prepared.
Table 1-121 Data preparation for adding an NR TDD cell
SN Operation MO Configuration Reference
1 Add RU (using MML -

commands) or BBP
(using the MAE-
Deployment)
2 Add RHUB -
3 Add RRUCHAIN -
4 Add RRU -
5 Add SECTOR Set Create Default Sector

Equipment to TRUE(TRUE).

5G RAN
SN Operation MO Configuration Reference
6 Add SECTOREQM -
7 Add NRDUCELL Set LampSite Cell Flag to

YES(LampSite Cell). NR Cell ID
and Cell ID must be set to the
same value.
8 Add NRDUCELLTRP Set Max Transmit Power to

specify the maximum transmit
power of the NR DU cell.
9 Add NRDUCELLCOVERA A one-to-one mapping must be

GE ensured between NR DU Cell
Coverage ID and Sector
Equipment ID. Set NR DU Cell
TRP ID to the same value for all
NR DU cell coverage areas where
pRRUs requiring RF combination.
10 Add NRCELL NR DU Cell ID and Cell ID must

be set to the same value.
11 Activate NRDUCELL -
12 Activate NRCELL -

You can prepare data using the MAE-Deployment or MML commands. You are
advised to use the batch reconfiguration function of the MAE-Deployment to
configure base stations in batches and use the MAE-Deployment GUI to configure
a single base station. The three data preparation modes are described as follows:
NOTE
Before using the MAE-Deployment to prepare data, ensure that data in the planned data
● Use the batch reconfiguration mode of the MAE-Deployment. For details, see
● Using the MAE-Deployment GUI: see Preparing Data in GUI Mode.

5G RAN
NOTE
In addition to the preceding configuration methods, the MAE-Deployment provides the

LampSite Configuration Express function to configure the following information:
● RU, RRUCHAIN, RHUB, MPMU
● NRDUCELL
● NRDUCELLTRP
● NRDUCELLCOVERAGE
● NRCELL
Navigation path to the LampSite Configuration Express: Right-click a LampSite
base station in the navigation tree in the left pane of the planned data area and
choose LampSite RF Configuration Express from the shortcut menu.
For detailed operations, see "Configuring Radio Data Using the LampSite RF
Configuration Express" in the MAE-Access online help.
● Using MML commands: Prepare configuration scripts based on the preceding
data preparation procedures and the following MML command examples.
MML Command Examples

MML configuration scripts listed in the following are for adding RHUBs, pRRUs, a
baseband processing unit, and an NR cell. If the currently used license file does
not meet requirements, load a new license file. If the currently used license file
meets requirements, directly add an NR cell.
/* Exporting the currently used license file to the ftproot folder on the MAE-Access server */
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/", FN="
LIC_NR_OLD.xml";
/* Importing a new license file from the ftproot folder on the MAE-Access server */
INS LICENSE: DIR="ftproot/", FN=" LIC_NR_NEW.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/* In NR mode, adding a baseband processing unit and selecting the NR mode */
/* Adding baseband equipment */
ADD BASEBANDEQM: BASEBANDEQMID=1, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=0;
/* Adding an RRU chain/ring to an RHUB */
/* Adding RHUBs */
ADD RHUB: SRN=60, RCN=30, PS=0, RN="slot_3_0_0";
/* Adding RRU chains/rings to pRRUs */

5G RAN
/* Adding pRRUs */
ADD RRU: CN=0, SRN=61, SN=0, TP=BRANCH, RCN=61, PS=0, RT=MPMU, RS=NO, RN="RRU61", RXNUM=4,
TXNUM=4, MNTMODE=NORMAL, RFTXSIGNDETECTSW=OFF, DORMANCYSW=OFF;

5G RAN

/* Adding sectors and sector equipment */
ADD SECTOR: SECTORID=61, ANTNUM=4, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=61, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0C, ANT4CN=0,
ANT4SRN=61, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE, SECTOREQMID=61;

5G RAN


5G RAN

/* Adding an NR DU cell with LampSite Cell Flag set to YES(LampSite Cell) (NR DU Cell ID and Cell ID
must be set to the same value.) */
ADD NRDUCELL: NrDuCellId=1, NrDuCellName="1", DuplexMode=CELL_TDD, CellId=1, PhysicalCellId=1,
FrequencyBand=N77, UlNarfcnConfigInd=NOT_CONFIG, DlNarfcn=630000, UlBandwidth=CELL_BW_100M,
DlBandwidth=CELL_BW_100M, SlotAssignment=4_1_DDDSU, SlotStructure=SS1, LampSiteCellFlag=ON,
TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN, SsbFreqPos=629988;
/* Adding a TRP for the NR DU cell */
PowerConfigMode=TRANSMIT_POWER, MaxTransmitPower=240, CpriCompression=3DOT2_COMPRESSION;
/* Adding NR DU cell coverage areas with a one-to-one mapping between NR DU Cell Coverage ID Sector
Equipment ID and NR DU Cell TRP ID set to the same value for all NR DU cell coverages where pRRUs
requiring RF combination */
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=68, SectorEqmId=68;BK
/* Adding an NR cell (NR DU Cell ID and Cell ID must be set to the same value.) */
/* Activating the NR cell */

This section describes how to add an NR TDD cell locally and remotely.
Prerequisites
NR TDD-related information, license files, and data are ready.
Context
Local operations must be performed onsite, such as board installation and
operations on the LMT. Remote operations must be performed at the OMC
(including MAE-Access), such as reconfiguring parameters using the MAE-Access.
Procedure
● Local operations
a. Install baseband processing units in the subrack.
b. Install the RHUB. For details, see LampSite RHUB Installation Guide.
c. Install pRRUs. For details, see LampSite pRRU Installation Guide.
● Remote operations
– Using the MAE-Deployment

5G RAN
i. To prevent unnecessary alarms from being reported during

reconfiguration, set the gNodeB engineering maintenance mode to
EXPAND before reconfiguration.
ii. Back up the currently used license file on the MAE-Access server.
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********", DIR="ftproot/", FN="LIC_NR_OLD.xml";
INS LICENSE: DIR="ftproot/", FN="LIC_NR_NEW.xml", FLG=NO,
MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver and activate the configuration on the gNodeB. For details,
v. After the reconfiguration is completed, set the gNodeB engineering
NOTE
If the license file needs to be updated, back up the currently used license file
and import a new license file into the gNodeB. If the license file does not
need to be updated, the backup and import operations are not required.
ii. Back up and export the configuration file so that configurations can
be restored if the reconfiguration fails.
iii. Run the BKP CFGFILE command to back up the configuration file.
iv. Run the ULD CFGFILE command to export the configuration file.
ULD CFGFILE: MODE=IPV4, IP="10.169.18.69", USR="ftpuser",
PWD="***********", DIR="ftproot/";
v. Use the MAE-Access to deliver the configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station
and activate the scripts on the base station. For details, see "Running
MML Commands on the MAE-Access."
NOTE
You can import or export license files for only one NE at a time.
vi. After the reconfiguration is completed, set the gNodeB engineering

This section describes how to check whether an NR TDD cell is successfully added.

5G RAN
Procedure
Step 1 Verify that no cell-related alarms are generated, such as ALM-29841 NR Cell
Unavailable, ALM-29844 NR DU Cell Unavailable, ALM-29870 NR DU Cell TRP
Unavailable, and ALM-29871 NR DU Cell TRP Capability Degraded.
Step 2 Run the DSP NRDUCELL command to check whether the value of NR DU Cell
State is Normal.
If the value of NR DU Cell State is Not Set Up, check the cell configuration, NR
DU cell TRP power configuration, or hardware environment based on the value of
NR DU Cell Latest State Change Reason in the command output.
Step 3 Run the DSP NRCELL command to check whether the value of NR Cell State is
Normal.
If the value of NR Cell State is Not Set Up, check the cell configuration or
hardware environment based on the value of Cell Latest State Change Reason in
the command output.
----End

This section describes how to restore the initial configuration if reconfiguration
fails.
Procedure
Step 1 Roll back the configuration.
Using the MAE-Deployment: see Falling Back Configuration Data.
Using MML commands:

● Method 1: Traditional configuration rollback
a. Run the DLD CFGFILE command to download the original configuration
file.
DLD CFGFILE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
b. Run the ACT CFGFILE command to activate the original configuration
file.
ACT CFGFILE: EFT=IMMEDIATELY;
● Method 2: One-click blind configuration rollback
information.
DSP ROLCFGINFO: OT=BYINFO;
ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

5G RAN
NOTE
– Blind configuration rollback is supported only when the default value ON is

retained for Configuration Rollback Switch. You can run the DSP ROLCFGSW
– Using the one-click blind configuration rollback function to roll back the
configuration may roll back other data reconfigurations made at the same time.
Therefore, determine whether such impact is acceptable before you perform the
rollback.
– The start time at which the system can recover data is the time of the last full
record table.
Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Step 3 Restore physical connections.
Step 4 Check whether the engineering rollback is successful by following instructions
provided in 1.10.1.4 Engineering Verification.
----End
1.10.2 Sharing BBUs Between Macro and LampSite Base

Stations
This section describes how to share BBUs between macro and LampSite base
stations.

reconfiguration scheme, and topology changes for sharing a BBU between a
macro base station and a LampSite base station.
A macro base station and a LampSite base station share a BBU; in which case, an
existing macro base station can be reused with a new LampSite base station, or
both of them can be newly deployed at a time.
No impact
NOTE
● This section describes the hardware installation and data configuration for LampSite base
stations. The hardware to be added for a LampSite base station includes main control
boards, baseband processing units, RHUBs, and pRRUs. Data configuration for a LampSite
base station is dedicated to the added hardware. Neither hardware installation nor data
configuration affects services of the macro base station.
● In macro-LampSite co-BBU scenarios, the software package in use must be a
multimode_ALL software package that is applicable to both base stations, for example,
BTS3900_5900 V100R016C10SPCxxx_ALL(Software).7z.

5G RAN
Topology Change
Figure 1-72 Network topologies before and after configuration for co-MPT
Figure 1-73 shows the reconfiguration procedure. Determine a reconfiguration
scheme according to the following table.

If... Then...
Transmission Replace main control boards by referring to 1.7.1

resources are Replacing the Main Control Board When No SeGW Is
insufficient and more Deployed or 1.7.2 Replacing the Main Control Board
main control boards When an SeGW Is Deployed.
are needed (co-MPT)
More main control Configure the added main control board and the related
boards are needed devices as well as the related transport and radio data,
(separate-MPT) by referring to LampSite Initial Configuration Guide.

5G RAN
Figure 1-73 Procedure for the macro-LampSite co-MPT configuration

This section describes the engineering preparation for sharing BBUs between
macro and LampSite base stations, including information collection and
preparation of hardware, software, license files, certificates, and data. It also
describes the data preparation mode.
Table 1-123 describes the information to be collected before the reconfiguration.

5G RAN

Cell information ● Basic cell information

● TX/RX mode: 2T2R or 4T4R for pRRU-aggregation
cells in an NR TDD network
Baseband processing ● Model of the baseband processing unit in co-MPT

unit model mode (for example, UBBPg2a or UBBPg3)
● UBBP working mode: TDD in pRRU-aggregation cells
● UBBP baseband work standard: NR_TDD(NR TDD) in
pRRU-aggregation cells
RF module ● Types of the added RF units (pRRU-aggregation cells

information support only the settings of MPMU.)
● Port mapping between pRRUs and RHUBs
Topology Network topology of pRRU-aggregation cells a
Cell sector equipment Values of the Sector Equipment Group ID and Sector
group Equipment ID parameters in the EuSectorEqmGroup
MO
Reference signal pRRU reference signal power

power
a: pRRU-aggregation cells support only the chain topology. Set Topo Position to
BRANCH(BRANCH).
Table 1-124 shows the hardware to be prepared before the reconfiguration.

New Hardware Description
Baseband processing ● If no baseband equipment is specified for LampSite

unit cells, the gNodeB automatically allocates LampSite
cells different baseband processing units from macro
cells when allocating baseband resources.
● If you configure LampSite cells and macro cells on
the same baseband processing unit, establishment of
the type of cells established later fails.
Main control board If baseband resources are insufficient, replace main

control boards with ones of higher specifications. For
details, see 1.7 Device Data Reconfigurations.

5G RAN
New Hardware Description
RHUBs, pRRUs, For restrictions on the quantity of RHUBs and pRRUs,

related cables, and see LampSite Technical Description.
optical modules
N/A
License Preparation
N/A
N/A
Data Preparation
Table 1-125 Data preparation for sharing a BBU between macro and LampSite
base stations

ation
1 Add RU -
2 Add MPT
3 Add RRUCHAIN
4 Add RHUB
5 Modif RRU
y
6 Add Sector
7 Add SectorEqm
8 Add Cell Set MultiRruCellFlag to

BOOLEAN_TRUE(True) and
MultiRruCellMode to
MPRU_AGGREGATION(MPRU_AGGREG
ATION). All cells in the LampSite
solutions require the setting of
MPRU_AGGREGATION(MPRU_AGGREG
ATION).
9 Add CellOp -

5G RAN

ation
10 Modif PDSCHCfg Set the reference signal power for a cell,

y for example, to –81 (unit: 0.1 dBm).
11 Add EuSectorEqmGroup Add sector equipment groups for cells

based on network requirements.
Configure the sector equipment of
pRRUs requiring RF combination in the
same cell sector equipment group. a
12 Activa Cell -
te
a: In the LampSite solutions, the mapping between SectorEqm and Cell must
be specified through EuSectorEqmGroup.

script examples.
MML Command Examples

MML configuration scripts listed in the following are for adding RHUBs, pRRUs, a
baseband processing unit, and an NR TDD cell. If the currently used license file
does not meet requirements, load a new license file. If the currently used license
file meets requirements, directly add an NR TDD cell.
/* Exporting the currently used license file to the ftproot folder on the MAE-Access server */
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/", FN="
LIC_NR_OLD.xml";
/* Importing a new license file from the ftproot folder on the MAE-Access server */
INS LICENSE: DIR="ftproot/", FN=" LIC_NR_NEW.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/* In NR mode, adding a baseband processing unit and selecting the NR mode*/
/* Adding baseband equipment */
ADD BASEBANDEQM: BASEBANDEQMID=1, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=0;
/* Adding an RRU chain/ring to an RHUB */
/* Adding RHUBs */
/* Adding RRU chains/rings to pRRUs */

5G RAN
/* Adding pRRUs */

5G RAN
/* Adding sectors and sector equipment */

5G RAN


5G RAN

/* Adding an NR DU cell with LampSite Cell Flag set to YES(LampSite Cell) (NR DU Cell ID and Cell ID
must be set to the same value.) */
ADD NRDUCELL: NrDuCellId=1, NrDuCellName="LampSite_NR", DuplexMode=CELL_TDD, CellId=1,
PhysicalCellId=1, FrequencyBand=N77, UlNarfcnConfigInd=NOT_CONFIG, DlNarfcn=630000,
UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M, SlotAssignment=4_1_DDDSU,
SlotStructure=SS1, LampSiteCellFlag=ON, TrackingAreaId=0, SsbDescMethod=SSB_DESC_TYPE_NARFCN,
SsbFreqPos=629988;
/* Adding a TRP for the NR DU cell */
PowerConfigMode=TRANSMIT_POWER, MaxTransmitPower=240, CpriCompression=3DOT2_COMPRESSION;
/* Adding NR DU cell coverage areas with a one-to-one mapping between NR DU Cell Coverage ID Sector
Equipment ID and NR DU Cell TRP ID set to the same value for all NR DU cell coverages where pRRUs
requiring RF combination */
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=68, SectorEqmId=68;BK
/* Adding an NR cell (NR DU Cell ID and Cell ID must be set to the same value.) */
/* Activating the NR cell */

This section describes how to share BBUs between macro and LampSite base
stations locally and remotely.
Prerequisites
Information and data for sharing BBUs between macro and LampSite base
stations are ready.
Context
● Local operations must be performed onsite, such as board installation and
operations on the LMT.

5G RAN
● Remote operations must be performed on the OMC (including MAE-Access

and MAE-Deployment), such as adjusting parameters using the MAE-Access
or MAE-Deployment.
Procedure
● Local operations
a. (Optional) In macro-LampSite co-BBU co-MPT scenarios, insert baseband
processing units into the subrack.
b. Install the RHUB. For details, see LampSite RHUB Installation Guide.
c. Install pRRUs. For details, see LampSite pRRU Installation Guide.
d. Install CPRI optical fibers and Ethernet cables.
● Remote operations
Maintenance Mode.
command.
CFGFILE command.
NOTE
You can import or export license files for only one NE at a time.
iv. After the reconfiguration is completed, set the gNodeB engineering
Maintenance Mode.
----End

This section describes how to verify the reconfiguration for BBU sharing between
macro and LampSite base stations.

5G RAN
Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
consistent with the configuration data.
----End

the original state.
Procedure
● Using MML commands: traditional method
a. Run the DLD CFGFILE command to download the original configuration
file.
b. Run the ACT CFGFILE command to activate the original configuration
file.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
information.

5G RAN
NOTE
▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa, UMPTb, UMPTe, UMPTg, UMPTga, UMDU, SMPT, and
UEFU.

the rollback.
Step 2 (Optional. Perform this step if the license file is updated.) Import the pre-
reconfiguration license file.
Step 4 Check whether the engineering rollback is successful by following instructions

provided in 1.10.2.4 Engineering Verification.
----End
1.11 Configuration References

This chapter provides the reference documents for data configuration. If you want
to view all the check rules of NE data, obtain the file on the Consistency Check
page.
1.11.1 Setting the gNodeB Maintenance Mode

Before reconfiguring a gNodeB, set its maintenance mode to a customized expand
status or TESTING to avoid alarms generated during reconfiguration. After the
data reconfiguration is completed, set the maintenance mode to NORMAL. The
maintenance mode of a gNodeB running properly is NORMAL.
NOTE
● For a co-MPT base station, you can set the maintenance mode to TESTING for the specified
RAT. For an NR RRU/AAU, you can change its maintenance mode to TESTING.
● For a co-MPT base station, the maintenance mode of only one NE can be reconfigured and
the reconfiguration takes effect on the entire base station. Reconfiguring the maintenance
mode of a RAT takes effect only on this RAT.
● For a separate-MPT base station, maintenance modes of the NEs must be reconfigured
separately and the reconfiguration of an NE affects only the NE.

5G RAN
Setting the gNodeB Maintenance Mode to Expand Status

● On the MAE-Access:
– Set a gNodeB on the MAE-Access as follows:
i. On the MAE-Access, choose Maintenance > Maintenance Mode.
ii. (This step is optional. Perform the operation if the gNodeB does not
have a customized expand status.) Set the maintenance mode.
1) Click the Mode Definition tab and then click New Maintenance
Mode.
2) In the New Maintenance Mode dialog box, set NE
Maintenance Mode, OSS Maintenance Mode, Remarks, and
then click OK.
For example, set NE Maintenance Mode to EXPANDSTATUS1
and OSS Maintenance Mode to Reconfiguration.
iii. Click Set Maintenance Mode at the upper-right corner of the
Maintenance Mode window.
iv. In the Set Maintenance Mode dialog box, select the NE or RRU to
be configured. Set NE Maintenance Mode to a customized expand
status, such as EXPAND, and set the execution time. Click OK to
complete the setting.
v. In the displayed Confirm dialog box, click OK.
vi. The configuration progress is displayed. When the progress reaches
100%, click Close.
– On the LMT:
NOTE
You can specify Start Time and End Time of the maintenance mode as required.
▪ Run the SET MNTMODE command to set the NE maintenance mode

to a customized expand status.
▪ Run the MOD RRU command with Maintenance Mode set to

TESTING(TESTING) for an RF module.
▪ Run the MOD APP command with Application Maintenance Mode

set to TESTING(TESTING) for an RAT of a co-MPT base station.
On the alarm console, the gNodeB does not report the alarms that are
generated during the reconfiguration.
Setting the gNodeB Maintenance Mode to NORMAL

● On the MAE-Access:
– Set a single gNodeB on the MAE-Access as follows:
i. On the MAE-Access, choose Maintenance > Maintenance Mode.
ii. Click Set Maintenance Mode at the upper-right corner of the
Maintenance Mode window.
iii. In the Set Maintenance Mode dialog box, select the NE to be
configured. Set NE Maintenance Mode to NORMAL. Click OK to
complete the setting.

5G RAN
iv. In the displayed Confirm dialog box, click OK.

v. The configuration progress is displayed. When the progress reaches
100%, click Close.
– On the LMT:
NOTE
You can specify Start Time and End Time of the maintenance mode as required.
▪ Run the SET MNTMODE command for an NE or the MOD RRU

command for an RF module with Maintenance Mode set to
NORMAL(NORMAL).
▪ Run the MOD APP command with Application Maintenance Mode

set to NORMAL(NORMAL) for an RAT of a co-MPT base station.
The alarms that are not cleared during the reconfiguration will be
displayed on the alarm console after the gNodeB enters the normal state.
1.11.2 Using the Batch Reconfiguration Mode of the MAE-

Deployment to Prepare Data
NOTE
If the current browser does not support the playback of this tutorial, please try another
browser.
Click to download
1.11.3 Preparing Data in GUI Mode

NOTE
browser.
Click to download
1.11.4 Delivering Data to Base Stations and Activating the

Data
NOTE
browser.
Click to download
1.11.5 Falling Back Configuration Data

NOTE
browser.

5G RAN
Click to download

5G RAN Reconfiguration Guide (V100R016C10 - 04) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G RAN Reconfiguration Guide (V100R016C10 - 04) (PDF) - en

Uploaded by

Copyright:

Available Formats

5G RAN

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. i

1 5G RAN Reconfiguration Guide............................................................................................1

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. ii

1.5.4.3 Engineering Implementation..................................................................................................................................... 67

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. iii

1.5.11.3 Engineering Implementation................................................................................................................................ 106

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. iv

1.6.1.2 Engineering Preparation............................................................................................................................................ 142

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. v

1.7.5.1 Scheme Overview........................................................................................................................................................ 194

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. vi

1.9 Security Networking Data Reconfigurations............................................................................................................ 283

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. vii

1.10.1.4 Engineering Verification..........................................................................................................................................352

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. viii

1 5G RAN Reconfiguration Guide

Product Name Solution Version Product Version

3900 series base stations 5G RAN3.1 V100R016C10

5900 series base stations

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 1

1.1 Changes in 5G RAN Reconfiguration Guide

Topic Change Description

1.6.1 Adding a Neighboring Added the data to be prepared for adding a

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 2

Topic Change Description

1.8.6 Optimizing the Updated the engineering rollback operations

● 1.5.10 Changing the Cell Name

Topic Change Description

Topic Change Description

1.7.1 Replacing the Main ● Changed the recommended data

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 3

Topic Change Description

1.10.2 Sharing BBUs Between Deleted the description of the UBBPg3a.

1.5.1 Adding an NR FDD Cell (Common Scenarios)

Compared with V100R015C10, this issue includes the following changes.

Topic Change Description

Entire document ● Added the information about the UMPTga.

Compared with V100R015C10, this issue excludes the following information:

Descriptions of USB flash drive-based site deployment

1.2 Introduction to 5G RAN Reconfiguration

1.2.1 Definition of 5G RAN Reconfiguration

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 4

Scope of this document

Figure 1-1 Scope of this document

1. Reconfiguration evaluation: Before network reconfiguration, you must

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 5

1.2.2 General Prerequisites

1.2.3 Reconfiguration Tools

Table 1-1 Reconfiguration Tools

LMT MML Reconfi Data of only one NE is 1.3.2 Running MML

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 6

Tools Reconf Usage Characteristic Configuration

MAE- MML Batch Data of one or more 1.3.3 Running MML

MAE- GUI Reconfi Data of only one NE is 1. Select a gNodeB from

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 7

Tools Reconf Usage Characteristic Configuration

Batch Batch Data of multiple NEs 1. Use a summary data

Issue 04 (2021-02-28) Copyright © Huawei Technologies Co., Ltd. 8

Tools Reconf Usage Characteristic Configuration