5G RAN

NG and Xn Self-Management
Feature Parameter Description

Issue Draft A
Date 2020-01-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: [email protected]

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description Contents

Contents

1 Change History.........................................................................................................................1
1.1 5G RAN3.1 Draft A (2020-01-20)...................................................................................................................................... 1

2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Features in This Document.................................................................................................................................................. 3
2.3 Differences Between NR FDD and NR TDD................................................................................................................... 4
2.4 Differences Between NSA and SA..................................................................................................................................... 4
2.5 Differences Between High Frequency Bands and Low Frequency Bands............................................................ 4

3 Overview....................................................................................................................................6
4 NG Self-Management.............................................................................................................8
4.1 Principles.................................................................................................................................................................................... 8
4.1.1 NG Self-Setup........................................................................................................................................................................8
4.1.1.1 NG Self-Setup with Peers Manually Configured................................................................................................... 8
4.1.1.2 NG Self-Setup with Peers Automatically Configured........................................................................................ 10
4.1.1.2.1 NG-C Self-Setup.......................................................................................................................................................... 10
4.1.1.2.2 NG-U Self-Setup......................................................................................................................................................... 12
4.1.2 NG Self-Update.................................................................................................................................................................. 14
4.1.3 NG Self-Removal............................................................................................................................................................... 14
4.1.4 Support of TNLA Setup by the NG Interface........................................................................................................... 15
4.1.5 NG-C Interface Specifications....................................................................................................................................... 16
4.1.6 Application Restrictions................................................................................................................................................... 16
4.2 Network Analysis.................................................................................................................................................................. 16
4.2.1 Benefits................................................................................................................................................................................. 16
4.2.2 Impacts.................................................................................................................................................................................. 16
4.3 Requirements......................................................................................................................................................................... 16
4.3.1 Licenses................................................................................................................................................................................. 16
4.3.2 Software................................................................................................................................................................................17
4.3.3 Hardware.............................................................................................................................................................................. 17
4.3.4 Networking.......................................................................................................................................................................... 17
4.3.5 Others.................................................................................................................................................................................... 17
4.4 Operation and Maintenance............................................................................................................................................. 17
4.4.1 When to Use....................................................................................................................................................................... 18

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description Contents

4.4.2 Data Configuration........................................................................................................................................................... 18

4.4.2.1 Data Preparation............................................................................................................................................................ 18
4.4.2.2 Using MML Commands............................................................................................................................................... 30
4.4.2.3 Using the MAE-Deployment...................................................................................................................................... 31
4.4.3 Activation Verification..................................................................................................................................................... 32
4.4.4 Network Monitoring......................................................................................................................................................... 33

5 Xn Self-Management........................................................................................................... 34
5.1 Principles.................................................................................................................................................................................. 34
5.1.1 Xn Self-Setup...................................................................................................................................................................... 34
5.1.1.1 Xn Self-Setup with Peers Manually Configured.................................................................................................. 35
5.1.1.2 Xn Self-Setup with Peers Automatically Configured......................................................................................... 37
5.1.2 Xn Self-Update................................................................................................................................................................... 40
5.1.2.1 Service-Triggered Self-Update of Xn Peer Information..................................................................................... 40
5.1.2.2 Manually Triggered Self-Update of Xn Peer Information................................................................................ 41
5.1.3 Xn Self-Removal................................................................................................................................................................. 41
5.1.4 Xn Blacklist and Xn Whitelist.........................................................................................................................................44
5.1.5 Xn-C Interface Specifications......................................................................................................................................... 44
5.1.6 Application Restrictions................................................................................................................................................... 45
5.2 Network Analysis.................................................................................................................................................................. 45
5.2.1 Benefits................................................................................................................................................................................. 45
5.2.2 Impacts.................................................................................................................................................................................. 45
5.3 Requirements......................................................................................................................................................................... 45
5.3.1 Licenses................................................................................................................................................................................. 45
5.3.2 Software................................................................................................................................................................................45
5.3.3 Hardware.............................................................................................................................................................................. 45
5.3.4 Networking.......................................................................................................................................................................... 46
5.3.5 Others.................................................................................................................................................................................... 46
5.4 Operation and Maintenance............................................................................................................................................. 46
5.4.1 Data Configuration........................................................................................................................................................... 46
5.4.1.1 Data Preparation............................................................................................................................................................ 46
5.4.1.2 Using MML Commands............................................................................................................................................... 51
5.4.1.3 Using the MAE-Deployment...................................................................................................................................... 52
5.4.2 Activation Verification..................................................................................................................................................... 52
5.4.3 Network Monitoring......................................................................................................................................................... 52

6 Direct IPsec for Xn Interface............................................................................................... 53

6.1 Principles.................................................................................................................................................................................. 53
6.1.1 Direct IPsec Setup.............................................................................................................................................................. 54
6.1.1.1 Direct IPv4 IPsec Self-Setup........................................................................................................................................55
6.1.1.2 Direct IPv6 IPsec Self-Setup........................................................................................................................................58
6.1.2 Static Blacklist & Whitelist............................................................................................................................................. 60
6.1.3 Self-Update.......................................................................................................................................................................... 61
6.1.4 Self-Removal....................................................................................................................................................................... 61

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description Contents

6.1.5 Application Restrictions................................................................................................................................................... 62

6.2 Network Analysis.................................................................................................................................................................. 62
6.2.1 Benefits................................................................................................................................................................................. 62
6.2.2 Impacts.................................................................................................................................................................................. 63
6.3 Requirements......................................................................................................................................................................... 63
6.3.1 Licenses................................................................................................................................................................................. 63
6.3.2 Software................................................................................................................................................................................63
6.3.3 Hardware.............................................................................................................................................................................. 63
6.3.4 Others.................................................................................................................................................................................... 64
6.4 Operation and Maintenance............................................................................................................................................. 64
6.4.1 When to Use....................................................................................................................................................................... 64
6.4.2 Precautions.......................................................................................................................................................................... 64
6.4.3 Data Configuration........................................................................................................................................................... 64
6.4.3.1 Data Preparation............................................................................................................................................................ 64
6.4.3.2 Using MML Commands............................................................................................................................................... 71
6.4.3.3 Using the MAE-Deployment...................................................................................................................................... 73
6.4.4 Activation Verification..................................................................................................................................................... 73
6.4.5 Network Monitoring......................................................................................................................................................... 74

7 Parameters.............................................................................................................................. 75
8 Counters.................................................................................................................................. 76
9 Glossary................................................................................................................................... 77
10 Reference Documents........................................................................................................ 78

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 1 Change History

1 Change History

This section describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation

1.1 5G RAN3.1 Draft A (2020-01-20)

This issue introduces the following changes to 5G RAN2.1 03 (2019-09-05).

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 1 Change History

Technical Changes
Change Description Parameter Change Base Station Model

Added support for direct Added the following ● 3900 and 5900 series
IPv6 IPsec self-setup. For parameters: base stations
details, see 6.1.1.2 Direct ● SECURITYHOST.VR ● DBS3900 LampSite
IPv6 IPsec Self-Setup and FIDX and DBS5900
6.4.3 Data Configuration. LampSite
● SECURITYTEMPLAT
E.IPROUTE6PREF
● DIRECTIPSECWHIT
ELIST.SECURITYPEE
RIPV6
● DIRECTIPSECWHIT
ELIST.IPV6PFXLEN
Added the
DIRECTIPSECBLACK-
LIST MO.
Added the value IPV6
to the
DIRECTIPSECWHITEL-
IST.IPVERSION
parameter.

Added the Xn dynamic Added the ● 3900 and 5900 series

blacklist function. For gNBXnDynBlacklist base stations
details, see 5.1.3 Xn Self- MO. ● DBS3900 LampSite
Removal. Added the and DBS5900
XN_SON_DYN_BLACK LampSite
LIST_SW option of the
gNBXnSonConfig.XnS
onConfigSwitch
parameter.

Changed the name of None ● 3900 and 5900 series

U2020 to MAE-Access and base stations
the name of CME to MAE- ● DBS3900 LampSite
Deployment. and DBS5900
LampSite

Editorial Changes
Revised descriptions in this document.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 2 About This Document

2 About This Document

2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance

This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.

2.2 Features in This Document

This document describes the following features.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 2 About This Document

Feature ID Feature Name Section

FBFD-021104 SA Option 2 Architecture 4 NG Self-Management

5 Xn Self-Management

FOFD-010080 IPsec 6 Direct IPsec for Xn

Interface

2.3 Differences Between NR FDD and NR TDD

Function Name Difference Section

NG self-management None 4 NG Self-Management

Xn self-management None 5 Xn Self-Management

Direct IPsec for Xn None 6 Direct IPsec for Xn

interface Interface

2.4 Differences Between NSA and SA

Function Name Difference Section

NG self-management This function is 4 NG Self-Management

supported only in SA
networking.

Xn self-management This function is 5 Xn Self-Management

supported only in SA
networking.

Direct IPsec for Xn This function is 6 Direct IPsec for Xn

interface supported only in SA Interface
networking.

2.5 Differences Between High Frequency Bands and

Low Frequency Bands
In this document, low frequency bands refer to those belonging to FR1 (410–7125
MHz), and high frequency bands refer to those belonging to FR2 (24250–52600
MHz). For details about FR1 and FR2, see section 5.1 "General" in 3GPP TS 38.104
V15.5.0.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 2 About This Document

Function Name Difference Section

NG self-management This function is 4 NG Self-Management

supported only in low
frequency bands.

Xn self-management This function is 5 Xn Self-Management

supported only in low
frequency bands.

Direct IPsec for Xn This function is 6 Direct IPsec for Xn

interface supported only in low Interface
frequency bands.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 3 Overview

3 Overview

3GPP Release 15 starts to support NR standalone (SA) networking. Figure 3-1

illustrates the logical architecture with base stations in integrated deployment
mode.

Figure 3-1 Logical structure of the NR network

The NR SA architecture includes the 5G Core Network (5GC) and NG Radio Access
Network (NG-RAN). The 5GC mainly provides the access and mobility
management function (AMF) and user plane function (UPF), while the NG-RAN
consists of the gNodeB. The following describes the interfaces between network
elements (NEs):

● NG-C: The gNodeB is connected to the AMF through the NG-C interface to
implement NG control plane functions.
● NG-U: The gNodeB is connected to the UPF through the NG-U interface to
implement NG user plane functions.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 3 Overview

● Xn-C: gNodeBs are connected through Xn-C interfaces to implement Xn

control plane functions.
● Xn-U: gNodeBs are connected through Xn-U interfaces to implement Xn user
plane functions.
To simplify configuration operations and reduce operators' operation costs, NG
and Xn Self-Management is introduced. The following sub-functions are
supported:
● NG self-management: self-setup, self-update, and self-removal
● Xn self-management: self-setup, self-update, and self-removal

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4 NG Self-Management

4.1 Principles
Figure 4-1 shows NG self-management.

Figure 4-1 NG self-management

4.1.1 NG Self-Setup
NG self-setup is performed in either of the following modes:
● NG self-setup with peers manually configured
NG peers are manually configured in this mode. If a gNodeB has multiple NG
interfaces, multiple peers must be manually added.
● NG self-setup with peers automatically configured
A domain name server (DNS) is required in this mode, and the mapping
between the AMF domain name and AMF IP address has been configured on
the DNS server. A gNodeB queries and automatically obtains the peer AMF IP
address from the DNS server. The gNodeB then automatically obtains the UPF
IP address from the AMF during NG interface bearer setup.

4.1.1.1 NG Self-Setup with Peers Manually Configured

An NG interface is classified into NG-C and NG-U interfaces. The NG-C interface
transmits control-plane data, and the NG-U interface transmits user-plane data.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 8

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Figure 4-2 shows the relationships between MOs involved in NG self-setup with
peers manually configured.

Figure 4-2 Relationships between MOs involved in NG self-setup with peers

manually configured

The following describes the relationships between the preceding MOs.

● Control plane
SCTPHOST and SCTPPEER MOs are used to set parameters such as the local
and peer IP addresses and port numbers of a control-plane link.
– In IPv4 networking, the SCTP link uses the values of the
SCTPHOST.SIGIP1V4 and SCTPPEER.SIGIP1V4 parameters as the local
and peer IP addresses, respectively.
– In IPv6 networking, the SCTP link uses the values of the
SCTPHOST.SIGIP1V6 and SCTPPEER.SIGIP1V6 parameters as the local
and peer IP addresses, respectively.
The gNodeB automatically sets up a multihoming SCTP link if second IP
addresses are configured in the SCTPHOST and SCTPPEER MOs.

The SCTPTEMPLATE MO consists of optional parameters common for configuring

SCTP links. The template is referenced by a control-plane link through the
SCTPHOST.SCTPTEMPLATEID parameter, whose value is the same as the
SCTPTEMPLATE.SCTPTEMPLATEID parameter.
● User plane
USERPLANEHOST and USERPLANEPEER MOs are used to set parameters
such as the local and peer IP addresses of a user-plane link, respectively.
– In IPv4 networking, the gNodeB uses a local NG user-plane IP address
(specified by USERPLANEHOST.LOCIPV4) and a peer UPF IP address
(specified by USERPLANEPEER.PEERIPV4).
– In IPv6 networking, the gNodeB uses a local NG user-plane IPv6 address
(specified by USERPLANEHOST.LOCIPV6) and a peer IPv6 address
(specified by USERPLANEPEER.PEERIPV6).

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 9

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

● Endpoint group
In the same endpoint group, links are set up between the local control plane
and the peer control plane or set up between the local user plane and the
peer user plane. When adding the local and peer control and user planes to
endpoint groups by using the EPGROUP MO, note the following:
– The local and peer control planes of an NG interface must be added to
the same endpoint group.
– The local and peer user planes of an NG interface must be added to the
same endpoint group.
● NG interface
The gNBCUNg MO can be used to add an NG interface object and bind it
with the endpoint group.

If both IPv4 and IPv6 addresses are configured for the local and peer ends, then both
the IPv4 and IPv6 links will be established, occupying two times of link resources.
Therefore, do not configure IPv4 and IPv6 addresses for the local and peer ends at the
same time.

After the preceding MOs are configured, the gNodeB and AMF automatically
configure SCTP links (control plane) and NG-U links (user plane) of the NG
interface and set up the NG interface and links.

4.1.1.2 NG Self-Setup with Peers Automatically Configured

NG self-setup with peers automatically configured is recommended because it
reduces manual operations and network planning and optimization costs.
NG self-setup with peers automatically configured is classified into NG-C self-
setup and NG-U self-setup. For details about NG-C self-setup and NG-U self-
setup, see 4.1.1.2.1 NG-C Self-Setup and 4.1.1.2.2 NG-U Self-Setup, respectively.

4.1.1.2.1 NG-C Self-Setup

The NGC_SON_SETUP_SW option of the gNBNgSonConfig.NgcSonSwitch
parameter specifies whether to enable this function.
Figure 4-3 shows the relationships between MOs involved in NG-C self-setup.

Figure 4-3 Relationships between MOs involved in NG-C self-setup

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 10

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Figure 4-4 shows the NG-C self-setup procedure.

Figure 4-4 NG-C self-setup procedure

1. The gNodeB acting as a DNS client carries the AMF domain name. The
gNodeB initiates a DNS query process to the DNS server and obtains the AMF
IP address.
Users can run the ADD GNBAMFDOMAINNAME command to configure an
AMF domain name. When a domain name is added, a DNS query is triggered.
After an AMF domain name is configured, the gNodeB periodically queries the
DNS server for the IP address corresponding to the domain name. If an AMF
domain name is not configured, the gNodeB cannot obtain the AMF IP
address from the DNS server. This will result in a failure to automatically
configure the NG-C peer.
The gNodeB acquires only the IP address of the AMF in this step. The SCTP
port number is still unavailable. The gNodeB automatically sets the SCTP peer
port number to 38412 (as recommended in 3GPP specifications) by default. If
this default value is used, the AMF must use 38412 as the local port number.
Otherwise, the NG-C link is abnormal.
2. The gNodeB uses the obtained AMF IP address as the peer IP address. If the
obtained peer IP address is not in the configured peer IP addresses (specified
in the SCTPPEER MOs), the gNodeB automatically generates a new
SCTPPEER MO and automatically adds it to the endpoint group.
The gNodeB automatically specifies the SCTPPEER.USERLABEL parameter
based on the information about the peer AMF. The format is AMF%s%s%s%s
%s%u, as shown in Figure 4-5.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 11

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Figure 4-5 Peer object user label value

3. The gNodeB automatically sets up the NG-C link based on the configured
MOs SCTPHOST, EPGROUP, and gNBCUNg, as well as the automatically
generated MO SCTPPEER.
A gNodeB can connect to a maximum of four DNS servers, which are deployed in
active/standby mode. If the DNS query on a DNS server fails, the gNodeB
automatically queries other DNS servers. If the DNS query fails on all DNS servers,
the gNodeB reports ALM-25958 DNS Resolution Failure. When there are multiple
DNS servers, ensure that the configurations on these DNS servers are the same.

4.1.1.2.2 NG-U Self-Setup

Figure 4-6 shows the relationships between MOs involved in NG-U self-setup.

Figure 4-6 Relationships between MOs involved in NG-U self-setup

During NG-U self-setup, the gNodeB automatically configures the

USERPLANEPEER MO based on the peer transport layer address required for NG
bearer setup contained in the NG control plane signaling messages. The address
can be contained in multiple NG control-plane signaling messages, such as
INITIAL CONTEXT SETUP REQUEST, PDU SESSION RESOURCE SETUP, and
HANDOVER COMMAND. The following uses the automatic configuration of the
NG-U peer during initial context setup as an example. Figure 4-7 shows the
signaling procedure.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 12

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Figure 4-7 Signaling procedure for NG-U self-setup

1. The UE initiates a service.

2. The AMF sends the gNodeB an INITIAL CONTEXT SETUP REQUEST message
containing the UPF IP address.
3. After receiving the UPF IP address, the gNodeB sends the AMF an INITIAL
CONTEXT SETUP RESPONSE message.
If the UPF IP address is different from the existing configuration (specified by
the USERPLANEPEER MO), the gNodeB generates a user-plane peer
(USERPLANEPEER MO) according to the UPF IP address, and automatically
adds the user plane peer to the configured endpoint group (specified by the
EPGROUP MO).
If the peer UPF IP address contains both IPv4 and IPv6 addresses, the gNodeB
automatically selects the peer IP address based on the following rules and
creates a USERPLANEPEER MO:
– If the gNodeB is configured with an IPv4 address, the gNodeB uses the
IPv4 address of the UPF.
– If the gNodeB is configured with an IPv6 address, the gNodeB uses the
IPv6 address of the UPF.
– If the gNodeB is configured with IPv4 and IPv6 addresses, the gNodeB
uses the IP address of the UPF based on the value of the
EPGROUP.IPVERPREFERENCE parameter.
At the same time, the gNodeB automatically fills in the value of
USERPLANEPEER.USERLABEL according to the MCC and MNC information of
the NG interface, in the format of UPF:MCC_xxx MNC_xxx. UPF:MCC_xxx
MNC_xxx specifies the operator for the user-plane peer.
4. The gNodeB automatically sets up an NG-U link based on the configured
MOs USERPLANEHOST, EPGROUP, and gNBCUNg, as well as the
automatically generated MO USERPLANEPEER.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 13

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4.1.2 NG Self-Update
The NGC_SON_SETUP_SW option of the gNBNgSonConfig.NgcSonSwitch
parameter specifies whether to enable this function. NG-C peer configurations are
automatically updated when a DNS server has been deployed and AMF IP
addresses have been updated on the DNS server.

An automatic update of the NG-C peer configurations is triggered when the AMF
transport layer address obtained from the DNS query changes, as shown in Figure
4-8.

Figure 4-8 DNS-based NG self-update

1. The gNodeB periodically performs DNS query or users manually perform DNS
query to obtain the mapping between the AMF and the IP addresses.
2. Based on the new mapping, the gNodeB automatically updates the IP
addresses and the SCTPPER.REMOTEID and re-establishes an NG-C link.

4.1.3 NG Self-Removal

NG-U Self-Removal
The gNodeB supports self-removal of NG-U transmission links and self-removal of
the USERPLANEPEER MO with USERPLANEPEER.CTRLMODE set to
AUTO_MODE.

The gNodeB determines whether to automatically remove NG-U transmission links

as follows:

● Self-removal based on link faults

When the GTP-U check result indicates that all the transmission links
corresponding to USERPLANEPEER MOs are faulty and the fault persists for
more than one hour, the base station removes the corresponding

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 14

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

USERPLANEPEER MOs and transmission links (no more than 50 links are
removed at one time).
● Self-removal based on the aging mechanism
The gNodeB marks a transmission link as aged and processes as follows if the
link has not been used for any UE for more than one hour:
– When the GTP-U check result indicates that all the transmission links
corresponding to USERPLANEPEER are normal or only some of the links
are faulty, the base station checks whether the number of established
transmission links reaches or exceeds 90% of the maximum allowed
number of transmission links. If it does, the base station removes aged
transmission links (no more than 50 links are removed at one time). If it
does not, the base station does not remove aged transmission links.
– If a new transmission link is required for UE services and the number of
established transmission links reaches or exceeds 90% of the maximum
allowed number of transmission links, the gNodeB randomly selects an
aged transmission link, removes it, and then sets up a new link.
Otherwise, the gNodeB does not remove aged transmission links.
– If the number reaches the maximum value and no link is aged, the
gNodeB rejects new UEs' access requests.

4.1.4 Support of TNLA Setup by the NG Interface

After initial NG-C interfaces between a gNodeB and an AMF are set up, the AMF
can request the gNodeB to add or remove NG-C interfaces or update NG-C
interface information. The NG-C links that are not initially set up are called
Transport Network Layer Association (TNLA) in 3GPP specifications.

Figure 4-9 shows the procedure for setting up a TNLA between a gNodeB and an
AMF.

Figure 4-9 Procedure for setting up a TNLA between a gNodeB and an AMF

1. The AMF sends an AMF CONFIGURATION UPDATE message to the gNodeB,

instructing the gNodeB to add, remove, or update the TNLA.
– Adding a TNLA
The AMF sends the gNodeB an AMF CONFIGURATION UPDATE message
that carries the "AMF TNL Association to Add Item" IE.
– Removing a TNLA
The AMF sends the gNodeB an AMF CONFIGURATION UPDATE message
that carries the "AMF TNL Association to Remove Item" IE.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 15

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

– Updating a TNLA
The AMF sends the gNodeB an AMF CONFIGURATION UPDATE message
that carries the "AMF TNL Association to Update Item" IE.
2. After receiving a request from the AMF, the gNodeB adds, removes, or
updates the TNLA, and replies the AMF with an AMF CONFIGURATION
UPDATE ACKNOWLEDGE message.
This function is not subject to the NGC_SON_SETUP_SW and
NGC_SON_DELETE_SW options of the gNBNgSonConfig.NgcSonSwitch
parameter.

4.1.5 NG-C Interface Specifications

NG-C is the interface between a gNodeB and an AMF for implementing control
plane functions. The specifications for a gNodeB are as follows:
● If TNLAs are not configured for the AMF, a maximum of 32 NG-C interfaces
can be configured.
● If TNLAs are configured for the AMF, a maximum of 96 NG-C interfaces can
be configured.

4.1.6 Application Restrictions

The gNodeB supports the self-setup of two USERPLANEPEER MOs at the same
time. The self-setup request of more than two USERPLANEPEER MOs will be
rejected, which may result in UE access failures.

4.2 Network Analysis

4.2.1 Benefits
NG self-management simplifies configuration operations, reduces the operating
expense (OPEX) of operators, and improves gNodeB resource usage.

4.2.2 Impacts
Network Impacts
None

Function Impacts
None

4.3 Requirements

4.3.1 Licenses
None

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 16

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4.3.2 Software
Prerequisite Functions
None

Mutually Exclusive Functions

None

4.3.3 Hardware
Base Station Models
● 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Boards
All NR-capable main control boards support this function. To learn which main
control boards are NR-capable, see technical specifications of the BBU in 3900 &
5900 Series Base Station Product Documentation.

RF Modules
This function does not depend on RF modules.

4.3.4 Networking
For the quality of service (QoS) requirements of NG interface for transmission
networking, see Transmission Resource Management.

4.3.5 Others
If the NG-C self-setup with peer information automatically obtained needs to be
deployed, the following requirements must be met:
● A DNS server is configured on the core network.
● Connection between the gNodeB and DNS server is available.
● The mapping between the AMF domain name and AMF IP address has been
configured on the DNS server.

Ensure that there is a one-to-one mapping between the domain names and IP addresses.
The AMF IP addresses obtained from the DNS server must be IPv4 addresses.

4.4 Operation and Maintenance

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 17

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4.4.1 When to Use

It is recommended that NG self-management be enabled when a large number of
AMFs and UPFs exist in a network. This spares operators from manually
configuring a large number of NG-C and NG-U interfaces.

4.4.2 Data Configuration

4.4.2.1 Data Preparation

The following table describes the parameters that must be set in an
SCTPTEMPLATE MO to configure NG-C negotiation parameters for the NG-C
transmission link.

Parameter Name Parameter ID Setting Notes

SCTP Parameters SCTPTEMPLATE.SCTPTE Set this parameter based

Template ID MPLATEID on the network plan.

The following table describes the parameters that must be set in an SCTPHOST
MO to configure the NG-C host information.

Parameter Name Parameter ID Setting Notes

SCTP Host ID SCTPHOST.SCTPHOSTID Set this parameter based

on the network plan.

IP Version SCTPHOST.IPVERSION The IP protocol version

of the local end must be
the same as that of the
peer end.

First Local IP Address SCTPHOST.SIGIP1V4 If SCTPHOST.IPVERSION

is set to IPv4, configure
a local control-plane
IPv4 address.

First Local IPv6 Address SCTPHOST.SIGIP1V6 If SCTPHOST.IPVERSION

is set to IPv6, configure
a local control-plane
IPv6 address.

Second Local IP Address SCTPHOST.SIGIP2V4 If SCTPHOST.IPVERSION

is set to IPv4, configure
a local control-plane
IPv4 address.

Second Local IPv6 SCTPHOST.SIGIP2V6 If SCTPHOST.IPVERSION

Address is set to IPv6, configure
a local control-plane
IPv6 address.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 18

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Local SCTP Port No. SCTPHOST.PN Set this parameter based

on the network plan.

SCTP Parameters SCTPHOST.SCTPTEMPL You are advised to use

Template ID ATEID the SCTP parameter
template whose ID is 0.
If you do not use this
template, you need to
add an SCTPTEMPLATE
MO and change the
value of
SCTPHOST.SCTPTEMPL
ATEID to reference the
new template.

The following table describes the parameters that must be set in a

USERPLANEHOST MO to configure information about the local gNodeB of the
NG-U interface.

Parameter Name Parameter ID Setting Notes

User Plane Host ID USERPLANEHOST.UPHO This parameter specifies

STID the ID of the user-plane
host.

IP Version USERPLANEHOST.IPVER The IP protocol version

SION of the local end must be
the same as that of the
peer end.

Local IP Address USERPLANEHOST.LOCIP If

V4 USERPLANEHOST.IPVER
SION is set to IPv4,
configure a local user-
plane IPv4 address.

Local IPv6 Address USERPLANEHOST.LOCIP If

V6 USERPLANEHOST.IPVER
SION is set to IPv6,
configure a local user-
plane IPv6 address.

IPSec Auto Configure USERPLANEHOST.IPSEC Set this parameter to

Switch SWITCH ENABLE to deploy direct
IPsec.

Security Host ID USERPLANEHOST.SECH This parameter specifies

OSTID the security host ID used
by the user-plane host.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 19

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Master Flag USERPLANEHOST.FLAG This parameter needs to

be configured when the
user-plane active/
standby function is
required.

(Optional) The following table describes the parameters that must be set in an
SCTPPEER MO to configure information about the peer AMF of the NG-C
interface. This MO is required only during manual NG-C peer configuration.

Parameter Name Parameter ID Setting Notes

SCTP Peer ID SCTPPEER.SCTPPEERID Set this parameter based

on the network plan.

IP Version SCTPPEER.IPVERSION The IP protocol version

of the local end must be
the same as that of the
peer end.

First Peer IP Address SCTPPEER.SIGIP1V4 If SCTPPEER.IPVERSION

is set to IPv4, configure
a peer control-plane IPv4
address.

First Peer IPv6 Address SCTPPEER.SIGIP1V6 If SCTPPEER.IPVERSION

is set to IPv6, configure
a peer control-plane IPv6
address.

Second Peer IP Address SCTPPEER.SIGIP2V4 If SCTPPEER.IPVERSION

is set to IPv4, configure
a peer control-plane IPv4
address.

Second Peer IPv6 SCTPPEER.SIGIP2V6 If SCTPPEER.IPVERSION

Address is set to IPv6, configure
a peer control-plane IPv6
address.

Peer SCTP Port No. SCTPPEER.PN The value recommended

by 3GPP specifications is
38412. For details, see 7
"Transport layer" in 3GPP
TS 38.412 V15.1.0.
Alternatively, set this
parameter based on the
network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 20

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Control Mode SCTPPEER.CTRLMODE ● Set this parameter to

MANUAL_MODE to
manually configure a
peer.
● Set this parameter to
AUTO_MODE to
automatically
configure a peer.

(Optional) The following table describes the parameters that must be set in a
USERPLANEPEER MO to configure information about the peer UPF of the NG-U
interface. This MO is required only during manual NG-U peer configuration.

Parameter Name Parameter ID Setting Notes

User Plane Peer ID USERPLANEPEER.UPPEE Set this parameter based

RID on the network plan.

IP Version USERPLANEPEER.IPVER The IP protocol version

SION of the local end must be
the same as that of the
peer end.

Peer IP Address USERPLANEPEER.PEERI If

PV4 USERPLANEPEER.IPVER
SION is set to IPv4,
configure a peer user-
plane IPv4 address.

Peer IPv6 Address USERPLANEPEER.PEERI If

PV6 USERPLANEPEER.IPVER
SION is set to IPv6,
configure a peer user-
plane IPv6 address.

The following table describes the parameters that must be set in an EPGROUP
MO.

Parameter Name Parameter ID Setting Notes

End Point Group ID EPGROUP.EPGROUPID Set this parameter based

on the network plan.

SCTP Host List EPGROUP.SCTPHOSTLIS Set this parameter based

T on the network plan.
Add an SCTP host to the
endpoint group.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 21

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

SCTP Peer List EPGROUP.SCTPPEERLIS Set this parameter based

T on the network plan.
Add an SCTP peer to the
endpoint group.

User Plane Host List EPGROUP.USERPLANEH Set this parameter based

OSTLIST on the network plan.
Add a user-plane host to
the endpoint group.

User Plane Peer List EPGROUP.USERPLANEP Set this parameter based

EERLIST on the network plan.
Add a user-plane peer to
the endpoint group.

Static Check Switch EPGROUP.STATICCHK If the user-plane load

sharing and active/
standby user plane are
required, set this
parameter to ENABLE,
indicating that the GTP-
U static check function is
enabled on all user-plane
paths in an endpoint
group.

The following table describes the parameters that must be set in an ADD
SCTPHOST2EPGRP command to add the SCTP host to an endpoint group.

Parameter Name Parameter ID Setting Notes

End Point Group ID EPGROUP.EPGROUPID Set this parameter based

on the network plan.

SCTP Host ID SCTPHOSTREF.SCTPHO Set this parameter based

STID on the network plan.

The following table describes the parameters that must be set in an ADD
SCTPPEER2EPGRP command to add the SCTP peer to an endpoint group.

Parameter Name Parameter ID Setting Notes

End Point Group ID EPGROUP.EPGROUPID Set this parameter based

on the network plan.

SCTP Peer ID SCTPPEERREF.SCTPPEER Set this parameter based

ID on the network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 22

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

The following table describes the parameters that must be set in an ADD
UPHOST2EPGRP command to add a user-plane host to the endpoint group.

Parameter Name Parameter ID Setting Notes

End Point Group ID EPGROUP.EPGROUPID Set this parameter based

on the network plan.

User Plane Host ID USERPLANEHOSTREF.U Set this parameter based

PHOSTID on the network plan.

The following table describes the parameters that must be set in an ADD
UPPEER2EPGRP command to add a user-plane peer to the endpoint group.

Parameter Name Parameter ID Setting Notes

End Point Group ID EPGROUP.EPGROUPID Set this parameter based

on the network plan.

User Plane Peer ID USERPLANEPEERREF.UP Set this parameter based

PEERID on the network plan.

The following table describes the parameters that must be set in a gNBCUNg MO
to configure the relationships with the EPGROUP MO.

Parameter Name Parameter ID Setting Notes

gNodeB CU NG ID gNBCUNg.gNBCuNgId Set this parameter based

on the network plan.

Control Plane Endpoint gNBCUNg.CpEpGroupId This parameter specifies

Group ID the endpoint group ID of
the NG control plane.

User Plane Endpoint gNBCUNg.UpEpGroupId This parameter specifies

Group ID the endpoint group ID of
the NG user plane.

(Optional) The following table describes the parameters that must be set in an
RSCGRP MO to add an IP transmission resource group. This MO is required only
when GTRANSPARA.TRANSCFGMODE is set to OLD and a dedicated transmission
resource group needs to be specified.

Parameter Name Parameter ID Setting Notes

Cabinet No. RSCGRP.CN Set this parameter based

on the network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 23

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Subrack No. RSCGRP.SRN Set this parameter based

on the network plan.

Slot No. RSCGRP.SN Set this parameter based

on the network plan.

Bearing Port Type RSCGRP.PT Set this parameter based

on the network plan.

Transmission Resource RSCGRP.RSCGRPID Set this parameter based

Group ID on the network plan.

Rate Unit RSCGRP.RU Set this parameter to

KBPS(kbit/s).

(Optional) The following table describes the parameters that must be set in an
EP2RSCGRP MO to configure the mapping between an endpoint and a
transmission resource group. This MO is required only when
GTRANSPARA.TRANSCFGMODE is set to OLD and a dedicated transmission
resource group needs to be specified.

Parameter Name Parameter ID Setting Notes

End Point ID EP2RSCGRP.ENDPOINTI Set this parameter based

D on the network plan.

Cabinet No. EP2RSCGRP.CN Set this parameter based

on the network plan.

Subrack No. EP2RSCGRP.SRN Set this parameter based

on the network plan.

Slot No. EP2RSCGRP.SN Set this parameter based

on the network plan.

Bearing Port Type EP2RSCGRP.PT Set this parameter based

on the network plan.

Transmission Resource EP2RSCGRP.RSCGRPID Set this parameter based

Group ID on the network plan.

(Optional) The following table describes the parameters that must be set in an
IPRSCGRP MO to add an IP transmission resource group. This MO is required only
when GTRANSPARA.TRANSCFGMODE is set to NEW and a dedicated
transmission resource group needs to be specified.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 24

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

IP Transmission Resource IPRSCGRP.IPRSCGRPID Set this parameter based

Group ID on the network plan.

Bearing Port Type IPRSCGRP.PT Set this parameter based

on the network plan.

Bearing Port ID IPRSCGRP.PORTID Set this parameter based

on the network plan.

Resource Group Number IPRSCGRP.RSCGRPNO Set this parameter based

on the network plan.

Rate Unit IPRSCGRP.RU Set this parameter based

on the network plan.

TX Bandwidth IPRSCGRP.TXBW Set this parameter based

on the network plan.

RX Bandwidth IPRSCGRP.RXBW Set this parameter based

on the network plan.

TX Committed Burst Size IPRSCGRP.TXCBS Set this parameter based

on the network plan.

TX Excessive Burst Size IPRSCGRP.TXEBS Set this parameter based

on the network plan.

(Optional) The following table describes the parameters that must be set in an
EP2IPRSCGRP MO to configure the mapping between an endpoint and an IP
transmission resource group. This MO is required only when
GTRANSPARA.TRANSCFGMODE is set to NEW and a dedicated transmission
resource group needs to be specified.

Parameter Name Parameter ID Setting Notes

Mapping ID EP2IPRSCGRP.MAPID Set this parameter based

on the network plan.

Mapping Type EP2IPRSCGRP.MT You are advised to set

this parameter to
ENDPOINT_GROUP.

End Point ID EP2IPRSCGRP.ENDPOIN If EP2IPRSCGRP.MT is

TID set to
ENDPOINT_GROUP, this
parameter indicates the
ID of the endpoint group.
The value of this
parameter must be the
same as that of
EPGROUP.EPGROUPID.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 25

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

IP Transmission Resource EP2IPRSCGRP.IPRSCGRP Set the value of this

Group ID ID parameter to the same
as that of
IPRSCGRP.IPRSCGRPID.

(Optional) The following table describes the parameter that must be set in a
GNBNGSONCONFIG MO to configure self-setup and self-removal for the NG-C
interface. This MO is required for NG-C self-configuration.

Parameter Name Parameter ID Setting Notes

NG-C SON Switch GNBNGSONCONFIG.Ng ● The

cSonSwitch NGC_SON_SETUP_S
W indicates whether
to enable the NG-C
self-setup function.
● The
NGC_SON_DELETE_S
W indicates whether
to enable the NG-C
self-removal function.

(Optional) The following table describes the parameters that must be set in a
DNSSRV MO to configure DNS server information for automatic NG-C peer
configuration. This MO is required only for NG-C self-setup.

Parameter Name Parameter ID Setting Notes

DNS SERVER ID. DNSSRV.DNSSRVID Set this parameter based

on the network plan.

IP Version DNSSRV.IPVER Set this parameter based

on the network plan.

DNS Client IPv4 DNSSRV.DNSCIP4 Set this parameter based

on the network plan.

DNS Server IPv4 DNSSRV.DNSSIP4 Set this parameter based

on the network plan.

DNS Client IPv6 DNSSRV.DNSCIP6 Set this parameter based

on the network plan.

DNS Server IPv6 DNSSRV.DNSSIP6 Set this parameter based

on the network plan.

DNS Server Port No. DNSSRV.PN Set this parameter based

on the network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 26

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

DSCP DNSSRV.DSCP Set this parameter based

on the network plan.

(Optional) The following table describes the parameters that must be set in a
gNBAmfDomainName MO to specify the domain name of the peer AMF. This
MO is required only for NG-C self-setup.

Parameter Name Parameter ID Setting Notes

gNodeB CU NG ID gNBAmfDomainName.g Set this parameter based

NBCuNgId on the network plan.

AMF Domain Name gNBAmfDomainName. Set this parameter based

AmfDomainName on the network plan.

(Optional) The following table describes the parameters that must be set in the
SRCIPRT MO. This MO is required only when GTRANSPARA.TRANSCFGMODE is
set to OLD and the user-plane load sharing function is required.

Parameter Name Parameter ID Setting Notes

Source Route Index SRCIPRT.SRCRTIDX Set this parameter based

on the network plan.

Slot No. SRCIPRT.SN Set this parameter based

on the network plan.

Source IP Address SRCIPRT.SRCIP Set this parameter based

on the network plan.

Subboard Type SRCIPRT.SBT You are advised to set

this parameter to
BASE_BOARD.

Route Type SRCIPRT.RTTYPE You are advised to set

this parameter to
NEXTHOP.

Next Hop IP SRCIPRT.NEXTHOP This parameter is valid

only when
SRCIPRT.RTTYPE is set
to NEXTHOP.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 27

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Priority SRCIPRT.PREF This parameter can be

configured if IP route
backup is required. The
priority is used for route
identification. A smaller
parameter value
indicates a higher
priority. Generally,
activated routes have
higher priorities.
The system does not
support route load
sharing. Routes to the
same destination
network segment must
have different priorities.

(Optional) The following table describes the parameters that must be set in the
SRCIPROUTE4 MO. This MO is required only when
GTRANSPARA.TRANSCFGMODE is set to NEW and the user-plane load sharing
function is required.

Parameter Name Parameter ID Setting Notes

Source Route Index SRCIPROUTE4. Set this parameter based

SRCRTIDX on the network plan.

Source IP Address SRCIPROUTE4. SRCIP Set this parameter based

on the network plan.

Route Type SRCIPROUTE4. RTTYPE You are advised to set

this parameter to
NEXTHOP.

Next Hop IP SRCIPROUTE4. This parameter is valid

NEXTHOP only when
SRCIPROUTE4.RTTYPE is
set to NEXTHOP.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 28

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Priority SRCIPROUTE4.PREF This parameter can be

configured if IP route
backup is required. The
priority is used for route
identification. A smaller
parameter value
indicates a higher
priority. Generally,
activated routes have
higher priorities.
The system does not
support route load
sharing. Routes to the
same destination
network segment must
have different priorities.

(Optional) The following table describes the parameters that must be set in the
GTPU MO. This MO is required only when the user-plane load sharing and active/
standby user plane are required.

Parameter Name Parameter ID Setting Notes

Static Check Switch GTPU.STATICCHK If the user-plane load

sharing and active/
standby user plane are
required, set this
parameter to ENABLE,
indicating that the GTP-
U static check function is
enabled for the system.

(Optional) The following table describes the parameters that must be set in the
GEPMODELPARA MO. This MO is required only when the user-plane load sharing
and active/standby user plane are required.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 29

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

Parameter Name Parameter ID Setting Notes

Static Check Mode GEPMODELPARA.STATI If the user-plane load

CCHKMODE sharing and active/
standby user plane are
required, set this
parameter to
EPSTATICCHK, indicating
that the GTP-U static
check function is enabled
for the endpoint group.

4.4.2.2 Using MML Commands

Common scenarios: configurations when the user-plane load sharing and active/
standby user plane are not required
//Adding an SCTP parameter template
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
//Adding an NG-C host (IPv4 used as an example)
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="5.5.3.37", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=38412, SCTPTEMPLATEID=0;
//NG-C self-setup can be classified into NG-C self-setup with peers manually configured and with peers
automatically configured (recommended). Use either of the configuration mode.
//Method 1: Adding an NG-C peer for NG-C self-setup with peers manually configured
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="138.32.1.20", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=38412;
//Adding a DNS server, configuring an AMF domain name, and turning on the NG-C self-configuration
switch for NG-C self-setup with peers automatically configured
ADD DNSSRV: DNSSRVID=2, IPVER=IPv4, DNSCIP4="20.2.7.37", DNSSIP4="185.22.63.78";
ADD GNBAMFDOMAINNAME: gNBCuNgId=0, AmfDomainName="amf1";
MOD GNBNGSONCONFIG: NgcSonSwitch=NGC_SON_SETUP_SW-1;

//Adding an NG-U host

ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="5.5.3.37", IPSECSWITCH=DISABLE;
//NG-U self-setup can be classified into NG-U self-setup with peers manually configured and with peers
automatically configured. Use either of the configuration mode.
//(Optional) Adding an NG-U peer. This command is required only for NG-U self-setup with peers manually
configured
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="195.168.1.28", IPSECSWITCH=DISABLE;
//Adding an endpoint group
ADD EPGROUP: EPGROUPID=0;
//Adding the NG-C host to the endpoint group
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
//(Optional) Adding the NG-C peer to the endpoint group. This command is required only for manual NG-C
peer configuration.
ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
//Adding the NG-U host to the endpoint group
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
//(Optional) Adding the NG-U peer to the endpoint group. This command is required only for manual NG-U
peer configuration.
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
//The following two steps are required only when GTRANSPARA.TRANSCFGMODE is set to NEW and a
dedicated transmission resource group needs to be specified.
//Adding an IP transmission resource group
ADD IPRSCGRP: IPRSCGRPID=0, PT=ETH, PORTID=0, RSCGRPNO=0, RU=KBPS;
//Adding the NG user plane to the IP transmission resource group, with ENDPOINTID being the referenced
EPGROUPID
ADD EP2IPRSCGRP: MAPID=1, MT=ENDPOINT_GROUP, ENDPOINTID=0, IPRSCGRPID=0;
//Adding a gNodeB CU NG object, with CpEpGroupId being EPGROUPID of the referenced NG control plane
and UpEpGroupId being EPGROUPID of the referenced NG user plane
ADD GNBCUNG: gNBCuNgId=0, CpEpGroupId=0, UpEpGroupId=0;

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 30

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

When the user-plane load sharing function is required (only IPv4 is supported):
The following configurations are required for the user-plane load sharing function.
Other configurations are the same as those in common scenarios.
//Configuring the source address route when GTRANSPARA.TRANSCFGMODE is set to OLD
ADD SRCIPRT: SRCRTIDX=0, SN=7, SBT=BASE_BOARD, SRCIP="5.5.3.37", RTTYPE=NEXTHOP,
NEXTHOP="10.1.1.2", PREF=60;
ADD SRCIPRT: SRCRTIDX=1, SN=7, SBT=BASE_BOARD, SRCIP="5.5.3.38", RTTYPE=NEXTHOP,
NEXTHOP="10.1.1.3", PREF=60;
//Configuring the source address route when GTRANSPARA.TRANSCFGMODE is set to NEW
ADD SRCIPROUTE4: SRCRTIDX=0, SRCIP="5.5.3.37", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;
ADD SRCIPROUTE4: SRCRTIDX=1, SRCIP="5.5.3.38", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.3", PREF=60;
//Adding two NG-U hosts for load sharing
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="5.5.3.37", IPSECSWITCH=DISABLE;
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="5.5.3.38", IPSECSWITCH=DISABLE;
//Turning on the GTP-U static check switch
MOD GTPU: STATICCHK=ENABLE;
SET GEPMODELPARA: STATICCHKMODE=EPSTATICCHK;
//Adding an endpoint group with the STATICCHK parameter specified
ADD EPGROUP: EPGROUPID=0, STATICCHK=ENABLE;
//Adding the two NG-U hosts for load sharing to the same endpoint group
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=1;

When the user-plane active/standby function is required (IPv4 and IPv6 are
supported): The following configurations are required for the user-plane active/
standby function. Other configurations are the same as those in common
scenarios.
//Configuring the GTP-U static check function
MOD GTPU: STATICCHK=ENABLE;
SET GEPMODELPARA: STATICCHKMODE=EPSTATICCHK;
//Adding two NG-U hosts in active/standby mode with the FLAG parameter specified (in IPv4 networking)
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="5.5.3.37", IPSECSWITCH=DISABLE,
FLAG=MASTER;
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="5.5.3.38", IPSECSWITCH=DISABLE,
FLAG=SLAVE;
//Adding two NG-U hosts in active/standby mode with the FLAG parameter specified (in IPv6 networking)
ADD USERPLANEHOST: UPHOSTID=2, IPVERSION=IPv6, LOCIPV6="2001::25", IPSECSWITCH=DISABLE,
FLAG=MASTER;
ADD USERPLANEHOST: UPHOSTID=3, IPVERSION=IPv6, LOCIPV6="2001::26", IPSECSWITCH=DISABLE,
FLAG=SLAVE;
//Adding an endpoint group with the STATICCHK parameter specified
ADD EPGROUP: EPGROUPID=0, STATICCHK=ENABLE;
//Adding the two NG-U hosts in active/standby mode to the same endpoint group (in IPv4 networking)
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=1;
//Adding the two NG-U hosts in active/standby mode to the same endpoint group (in IPv6 networking)
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=2;
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=3;

Deactivation Command Examples

//Deactivating self-setup of the NG-C peer
MOD GNBNGSONCONFIG: NgcSonSwitch=NGC_SON_SETUP_SW-0;

//Deactivating NG-C self-removal

MOD GNBNGSONCONFIG: NgcSonSwitch=NGC_SON_DELETE_SW-0;

4.4.2.3 Using the MAE-Deployment

For detailed operations, see MAE-Deployment-based Feature Configuration.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 31

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4.4.3 Activation Verification

After the peer IP address of the NG interface is manually configured, perform
the following activation verification procedures for the NG interface.

Step 1 Check the status of the NG interface.

● Run the DSP GNBCUNGINTERFACE command to query the values of gNodeB
CU NG Interface CP Bearer State and gNodeB CU NG Interface CP Bearer
ID.
● Run the DSP CPBEARER command to query the CP bearer state
corresponding to the gNodeB CU NG Interface CP Bearer ID.

Expected result:

● If the value of gNodeB CU NG Interface CP Bearer State is Normal, the

gNodeB CU NG interface is working properly.
● If the CP bearer state corresponding to the gNodeB CU NG Interface CP
Bearer ID is normal, the SCTP link is working properly.

Step 2 Start a service.

After the UE accesses the network, start a service on the UE and observe whether
the service runs properly.

Expected result: The service is successfully established, indicating that the NG self-
setup has taken effect.

----End

After the NG-C peer is automatically configured, perform the following

activation verification procedures for the NG-C self-setup, self-update, and
self-removal.

Step 1 Run the DSP DNS command to check the DNS query results.

Expected result: The resolution succeeds.

Step 2 On the MAE-Access client, choose SON > SON Log.

Step 3 Click Synchronize, select target gNodeBs, and click OK.

Step 4 On the Query SON Log tab page, select NR NG Interface Self Management Log
from the Log Category drop-down list box in the upper left corner. In the Event
Name area, select Automatically Establish Signaling Link, Automatically
Update Signaling Link, Automatically Delete Signalling Link, Automatically
Establish Service Link, and Automatically Delete Service Link. Then, select
target gNodeBs in the Log Source area to check different types of NG self-
configuration SON logs.

----End

Expected result: The SON logs contain NG-C self-setup, self-update, and self-
removal events.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 32

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 4 NG Self-Management

4.4.4 Network Monitoring

If the NG interface is faulty during the gNodeB operation, check whether any of
the alarms listed in Table 4-1 has been reported. If an alarm has been reported,
clear the alarm by referring to the alarm reference.

Table 4-1 Alarms related to the NG interface

Alarm ID Alarm Name Severity

29815 gNodeB NG Interface Major

Fault

29816 gNodeB NG Control Critical

Plane Transmission
Interruption

25954 User Plane Fault Major

25888 SCTP Link Fault Major

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 33

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

5 Xn Self-Management

5.1 Principles
Figure 5-1 shows Xn self-management.

Figure 5-1 Xn self-management

5.1.1 Xn Self-Setup
Depending on the methods of configuring the peers, Xn self-setup is classified into
the following types:

● Xn self-setup with peers manually configured

SCTPPEER and USERPLANEPEER MOs must be configured manually. If
gNodeBs have multiple Xn interfaces in between, multiple peers must be
manually added.
● Xn self-setup with peers automatically configured
The peers do not need to be configured manually. When the UE undergoes
inter-gNodeB handovers and the source gNodeB detects that the Xn links do
not exist or are faulty, the gNodeB exchanges Xn transport layer configuration
information with the peer gNodeB through the AMF. In this procedure, the
local gNodeB obtains the control-plane and user-plane IP addresses of the
peer gNodeB.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 34

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

5.1.1.1 Xn Self-Setup with Peers Manually Configured

An Xn interface is classified into Xn-C and Xn-U interfaces. The Xn-C interface
transmits the control-plane data, and the Xn-U interface transmits the user-plane
data. Figure 5-2 shows the relationships between MOs involved in Xn self-setup
with peers manually configured.

Figure 5-2 Relationships between MOs involved in Xn self-setup with peers

manually configured

Figure 5-2 describes the relationships between MOs.

● Control plane
SCTPHOST and SCTPPEER MOs are used to set parameters such as the local
and peer IP addresses and port numbers of a control-plane link.
– In IPv4 networking, the SCTP link uses the values of the
SCTPHOST.SIGIP1V4 and SCTPPEER.SIGIP1V4 parameters as the local
and peer IP addresses, respectively.
– In IPv6 networking, the SCTP link uses the values of the
SCTPHOST.SIGIP1V6 and SCTPPEER.SIGIP1V6 parameters as the local
and peer IP addresses, respectively.
The gNodeB automatically sets up a multihoming SCTP link if second IP
addresses are configured in the SCTPHOST and SCTPPEER MOs.

The SCTPTEMPLATE MO consists of optional parameters common for configuring

SCTP links. The template is referenced by a control-plane link through the
SCTPHOST.SCTPTEMPLATEID parameter, whose value is the same as the
SCTPTEMPLATE.SCTPTEMPLATEID parameter.
● User plane
USERPLANEHOST and USERPLANEPEER MOs are used to set parameters
such as the local and peer IP addresses of a user-plane link, respectively.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 35

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

– In IPv4 networking, the gNodeB uses a local Xn user-plane IP address

(specified by USERPLANEHOST.LOCIPV4) and a peer Xn user-plane IP
address (specified by USERPLANEPEER.PEERIPV4).
– In IPv6 networking, the gNodeB uses a local Xn user-plane IPv6 address
(specified by USERPLANEHOST.LOCIPV6) and a peer IPv6 address
(specified by USERPLANEPEER.PEERIPV6).
● Endpoint group
In the same endpoint group, links are set up between the local control plane
and the peer control plane or set up between the local user plane and the
peer user plane. When adding the local and peer control and user planes to
endpoint groups by using the EPGROUP MO, note the following:
– The local and peer control planes of an Xn interface must be added to
the same endpoint group.
– The local and peer user planes of an Xn interface must be added to the
same endpoint group.
● Xn interface
The gNBCUXn MO is used to add an Xn object and bind it with the endpoint
group.

The IP protocol version of the Xn-U links between two gNodeBs must be consistent
with that of the corresponding Xn-C links.
If both IPv4 and IPv6 addresses are configured for the local and peer ends, then both
the IPv4 and IPv6 links will be established, occupying two times of link resources.
Therefore, do not configure IPv4 and IPv6 addresses for the local and peer ends at the
same time.
When the Xn and X2 interfaces use the same local and peer user-plane IP addresses:
● The Xn and X2 interfaces must be configured with the same user-plane EPGROUP
MO. Otherwise, only the first user-plane tunnel can be successfully set up.
● If the newly configured EPGROUP MO for which the user-plane tunnel is to be set
up has the same local and peer user-plane IP addresses as an existing EPGROUP
MO, delete the newly configured MO or ensure that the existing EPGROUP MO is
referenced. Otherwise, user-plane tunnel setup will fail.

After the preceding configurations are complete, the gNodeB automatically

initiates Xn self-setup. gNodeB 1 sends an Xn SETUP REQUEST message, as shown
in Figure 5-3. After receiving this message, gNodeB 2 responds with an Xn SETUP
RESPONSE message. Then the Xn interface is set up based on the process defined
in 8.4.1 "Xn Setup" in 3GPP TS 38.423 V15.3.0.

Figure 5-3 Xn self-setup with peers manually configured

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 36

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

5.1.1.2 Xn Self-Setup with Peers Automatically Configured

Xn self-setup with peers automatically configured is recommended because it
reduces manual operations and network planning and optimization costs.

Xn self-setup with peers automatically configured is triggered when an inter-

gNodeB handover is performed for a UE.

The XN_SON_SETUP_SW option of the gNBXnSonConfig.XnSonConfigSwitch

parameter specifies whether to enable this function.

Figure 5-4 shows the Xn self-setup procedure.

The following MOs must have been configured for the Xn self-setup procedure:
SCTPHOST, USERPLANEHOST, gNBCUXn, EPGROUP, and SCTPTEMPLATE.

When the Xn and X2 interfaces use the same local user-plane IP address:
● The Xn and X2 interfaces must be configured with the same user-plane EPGROUP MO.
Otherwise, only the first user-plane tunnel can be successfully set up.
● If the newly configured EPGROUP MO for which the user-plane tunnel is to be set up
has the same local and peer user-plane IP addresses as an existing EPGROUP MO,
delete the newly configured MO or ensure that the existing EPGROUP MO is
referenced. Otherwise, user-plane tunnel setup will fail.
When the source base station initiates an Xn self-setup to a target base station, the second
Xn self-setup to the target base station will not be initiated within 10 minutes.

Figure 5-4 Xn self-setup with peers automatically configured

The detailed procedure is as follows:

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 37

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

1. The Xn self-setup requires the peer gNodeB ID as the input, which is usually
triggered by the inter-gNodeB handover. For details about the handover, see
Mobility Management.
– If the Xn link is available, an Xn self-setup procedure will not be
triggered.
– If the Xn link is unavailable or faulty, an Xn self-setup procedure will be
triggered.
2. The source gNodeB sends an UPLINK RAN CONFIGURATION TRANSFER
message to the AMF. For details, see 8.8.1 "Uplink RAN Configuration
Transfer" in 3GPP TS 38.413 V15.2.0. The message contains the following
information:
– Source gNB-ID IE, which consists of the Global gNB ID and Selected TAI
– Target gNB-ID IE, which consists of the Global gNB ID and Selected TAI
– Control- and user-plane IP addresses of the source gNodeB
3. The AMF forwards the DOWNLINK RAN CONFIGURATION TRANSFER
message that carries the source gNodeB information to the target gNodeB.
For details, see 8.8.2 "Downlink RAN Configuration Transfer" in 3GPP TS
38.413 V15.2.0.
4. Upon receiving this message, the target gNodeB automatically creates related
MOs to set up control-plane and user-plane transmission links.
a. The target gNodeB automatically creates the SCTPPEER and
USERPLANEPEER MOs according to the IP address in the message, and
then automatically adds the MOs containing the SCTPPEER.SCTPPEERID
and USERPLANEPEER.UPPEERID to the EPGROUP MO corresponding to
the Xn interface.

▪ If the local gNodeB is configured with an IPv4 address, the local

gNodeB uses the IPv4 address of the peer gNodeB.

▪ If the local gNodeB is configured with an IPv6 address, the local

gNodeB uses the IPv6 address of the peer gNodeB.

▪ If the local gNodeB is configured with IPv4 and IPv6 addresses, the
local gNodeB uses the IP address of the peer gNodeB based on the
value of the EPGROUP.IPVERPREFERENCE parameter.
b. The target gNodeB automatically creates the SCTPLNK, CPBEARER and
gNBCUXnInterface MOs according to configured SCTPHOST,
USERPLANEHOST, gNBCUXn, EPGROUP, and SCTPTEMPLATE MOs as
well as automatically generated SCTPPEER and USERPLANEPEER MOs.
c. Only the peer IP address can be obtained through the above message
exchange. The SCTP port number is not available. The gNodeB
automatically sets SCTPPEER.PN to the same value as the SCTPHOST.PN
parameter. It is recommended that the local SCTP port number be
configured as 38422.
5. The target gNodeB sends AMF an UPLINK RAN CONFIGURATION TRANSFER
message, which carries the Xn-C and Xn-U IP addresses of the target gNodeB.
6. The AMF forwards the DOWNLINK RAN CONFIGURATION TRANSFER
message to the source gNodeB.
7. Upon receiving this message, the source gNodeB automatically creates related
MOs to set up control-plane and user-plane transmission links.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 38

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

a. The source gNodeB automatically creates the SCTPPEER and

USERPLANEPEER MOs based on the control-plane and user-plane IP
addresses of the target gNodeB contained in the message sent from the
AMF, and then automatically adds the MOs containing the
SCTPPEER.SCTPPEERID and USERPLANEPEER.UPPEERID to the
EPGROUP MO corresponding to the Xn interface.
If both IPv4 and IPv6 addresses are configured for the control plane and
user plane of the target gNodeB, and these addresses are sent to the
source gNodeB through this message, the source gNodeB automatically
selects a peer IP address based on the following rules and creates the
SCTPPEER and USERPLANEPEER MOs:

▪ If the local gNodeB is configured with an IPv4 address, the local

gNodeB uses the IPv4 address of the peer gNodeB.

▪ If the local gNodeB is configured with an IPv6 address, the local

gNodeB uses the IPv6 address of the peer gNodeB.

▪ If the local gNodeB is configured with IPv4 and IPv6 addresses, the
local gNodeB selects the IP address of the peer gNodeB based on the
value of the EPGROUP.IPVERPREFERENCE parameter.

The IP protocol version of the Xn-U links between two gNodeBs must be
consistent with that of the corresponding Xn-C links.
The values of the EPGROUP.IPVERPREFERENCE parameter must be the
same for the Xn-U and Xn-C interfaces.
The modification of the preceding parameter does not take effect for links
that have been set up and takes effect only for a link that will be set up
later.
b. The source gNodeB automatically creates the SCTPLNK, CPBEARER and
gNBCUXnInterface MOs according to manually configured SCTPHOST,
USERPLANEHOST, gNBCUXn, EPGROUP, and SCTPTEMPLATE MOs as
well as automatically generated SCTPPEER and USERPLANEPEER MOs.
If the message sent from the AMF contains two control-plane addresses
of the target gNodeB, the source gNodeB automatically configures two
SCTPPEER IP addresses. If two SCTPHOST IP addresses are configured for
the source gNodeB, the source gNodeB automatically establishes a dual-
homing SCTP link.
c. Only the peer IP address can be obtained through the above message
exchange. The SCTP port number is not available. The gNodeB
automatically sets SCTPPEER.PN to the same value as the SCTPHOST.PN
parameter. It is recommended that the local SCTP port number be
configured as 38422.
8. The source gNodeB initiates an Xn Setup Request message and the target
gNodeB responds with an Xn Setup Response message. Then the Xn interface
is successfully set up.
During the automatic generation of the SCTPPEER and USERPLANEPEER MOs,
the source and target gNodeBs assign the values of the SCTPPEER.USERLABEL
and USERPLANEPEER.USERLABEL parameters according to the following rules:
The gNodeB automatically assigns the values to the SCTPPEER.USERLABEL or
USERPLANEPEER.USERLABEL parameter according to the MCC and MNC for the

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 39

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Xn interface and the peer gNodeB ID. The format is "gNBXn:MCC_xxx MNC_xxx
GlobalgNBId_xxx-xxx-xxxxxxx". Note that "gNBXn:MCC_xxx MNC_xxx" indicates
the operator that triggers the automatic creation of the SCTPPEER and
USERPLANEPEER MOs. The gNodeB automatically assigns the
SCTPPEER.USERLABEL value to the SCTPLNK.DESCRI parameter.

5.1.2 Xn Self-Update
Xn self-update refers to Xn peer information self-update, which can be service-
triggered or manually-triggered.

When changing the IP address of the Xn interface, you are advised to disable the Xn
dynamic blacklist function. For details, see 5.1.3 Xn Self-Removal.

5.1.2.1 Service-Triggered Self-Update of Xn Peer Information

During the network operation, the IP address or operator information of the peer
gNodeB may change in the following three specific scenarios.

IP Address of the Peer End Changes

If the control-plane IP address of the peer end changes, the Xn interface to that
peer end will become faulty. If the interface is faulty, then when the UE initiates a
handover to the target gNodeB, Xn self-setup will be triggered. The local end
obtains the new control-plane IP address of the peer end during the self-setup.
The local end searches for an SCTPPEER MO that contains the same operator
information as indicated by REMOTEID based on operator information such as
MNC, MCC, and global gNodeB/gNodeB ID in the Configuration Transfer message.
The local end then updates the control-plane and user-plane IP addresses in the
located SCTPPEER MO.
If the user-plane IP address of the peer end changes, the Xn interface to that peer
end will become faulty. The local end will obtain the modified user-plane IP
address during the Xn self-setup or Xn-based handover to the target gNodeB. The
local end searches for a USERPLANEPEER MO that contains the same operator
information as indicated by USERPLANEPEER.REMOTEID based on operator
information such as MNC, MCC, and gNodeB ID in the Handover Request
Acknowledge message. The local end then generates a new USERPLANEPEER MO
based on the modified user-plane IP address of the peer end. The faulty user-
plane path is deleted through Xn-U self-removal. For details, see Xn-U Self-
Removal.

Global gNodeB ID of the Peer End Changes

If the Global gNodeB ID (composed of the MNC, MCC, and gNodeB ID) of the
peer end changes, the peer gNodeB resets, and the Xn interface becomes faulty.
The restart of gNodeB will trigger the Xn setup, and the change of Global gNodeB
ID of the neighboring gNodeB is considered as the addition of a new gNodeB. In
this case, the transmission configuration of the Xn interface will not be updated,
and the REMOTEID parameter value will not be automatically updated either. The
local end configuration can be updated to be the same as that of the peer end
only after the Xn interface is re-established (re-establishment triggered when the
IP address is changed or the Xn interface is removed).

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 40

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

IP Address and Global gNodeB ID of the Peer End Change

If the peer IP address and Global gNodeB ID of the Xn interface change, the local
end cannot obtain the peer information, and therefore the local end cannot
update the peer configuration. The change of Global gNodeB ID of the
neighboring gNodeB is considered as the addition of a new gNodeB. When a UE
initiates a handover to the target gNodeB, an Xn interface self-setup is triggered.
During this process, the local end of the Xn interface cannot find the peer end
(specified by the SCTPPEER and USERPLANEPEER MOs) that matches the peer IP
address contained in the Configuration Transfer message. Therefore, an Xn
interface will be set up again based on the new peer IP address and Global
gNodeB ID.

5.1.2.2 Manually Triggered Self-Update of Xn Peer Information

For the Xn interface, the local end's IP address is referenced by the peer end's
SCTPPEER and USERPLANEPEER MOs. If the local and peer gNodeBs are
managed by the same MAE-Deployment, the MAE-Deployment can automatically
associate and modify the local IP address referenced by the peer end. When the
local IP address is modified, the MAE-Deployment can automatically associate and
modify the IP addresses in the SCTPPEER and USERPLANEPEER MOs.

The MAE-Deployment automatically queries the values of REMOTEID in the local

end's SCTPPEER and USERPLANEPEER MOs to obtain the peer end information.
Then, the MAE-Deployment obtains the peer gNodeB ID based on REMOTEID and
updates the local end's IP addresses referenced by the peer gNodeB's SCTPPEER
and USERPLANEPEER MOs. The format of REMOTEID is gNBXn:MCC_xxx
MNC_xxx GlobalgNBId_xxx-xxx-xxxxxxx.

5.1.3 Xn Self-Removal

Xn Self-Removal
gNodeBs may have redundant Xn interfaces due to reasons such as adjustment
during network construction. The maximum number of Xn interfaces that a
gNodeB supports is limited. That is, no new Xn interfaces can be configured if the
total number of configured Xn interfaces of a gNodeB has reached the maximum
allowed number. The Xn self-removal function recognizes and removes redundant
Xn interfaces, reducing manual maintenance costs. The XN_SON_DEL_SW option
of the gNBXnSonConfig.XnSonConfigSwitch parameter specifies whether to
enable this function. Before enabling this function, you are advised to select the
XN_SON_SETUP_SW option of the gNBXnSonConfig.XnSonConfigSwitch
parameter to ensure that removed Xn interfaces can be automatically set up again
when necessary.

When the XN_SON_DEL_SW option of the gNBXnSonConfig.XnSonConfigSwitch

parameter is selected, the gNodeB supports Xn self-removal in the following
scenarios:

● Xn self-removal and Xn dynamic blacklist based on the initial setup fault

An Xn interface is automatically removed if all of the following conditions are
met:

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 41

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

– SCTPPEER.CTRLMODE of the Xn interface is set to AUTO_MODE, and

the format of SCTPPEER.REMOTEID is gNBXn:MCC_xxx MNC_xxx
GlobalgNBId_xxx-xxx-xxxxxxx.
– The Xn interface is initially set up and the lower-layer signaling link is
faulty (in the initial setup phase, the gNodeB takes two to three minutes
to determine whether the lower-layer SCTP link is faulty).
– When the Xn interface is faulty for 10 minutes, the Xn self-removal from
the local end is triggered.
At the initial stage of network construction, lower-layer link faults frequently
occur because network planning is not optimum and the transport network is
unstable. In this case, users can manually remove the faulty Xn interfaces and
manually configure the Xn blacklist to avoid unnecessary self-setup
operations. However, manual operations are complex and prone to errors. The
Xn dynamic blacklist function is introduced to address this issue. After Xn
interfaces are removed by Xn self-removal based on the initial setup fault, the
local gNodeB automatically creates an Xn dynamic blacklist based on the
local and peer base station information about the removed Xn interfaces. This
simplifies the configuration and reduces risks introduced by manual
configurations. The XN_SON_DYN_BLACKLIST_SW option of the
gNBXnSonConfig.XnSonConfigSwitch parameter specifies whether to enable
this function.
Self-setup for the Xn interface is prohibited before the Xn dynamic blacklist
aging timer (420 minutes) expires if the local and peer gNodeBs of the Xn
interface are in the Xn dynamic blacklist. That is, the local gNodeB does not
initiate a self-setup request for the corresponding Xn interface and does not
respond to the Xn self-setup request initiated by the peer gNodeB. When the
420-minute timer expires, the local gNodeB deletes the corresponding
blacklist.
When the Xn dynamic blacklist function is enabled, if the Xn self-update fails
due to transmission faults after the local or peer IP address of the Xn
interface is changed, the peer base station to which the Xn interface belongs
is added to the Xn dynamic blacklist. As a result, services depending on the Xn
link are affected. Therefore, it is recommended that the Xn dynamic blacklist
function be enabled only in the early stage of network deployment when the
transport network is unstable. It is recommended that this function be
disabled when the transport network becomes stable.

● The specifications for the Xn dynamic blacklists are the same as those for Xn
interfaces. If the number of entries in an Xn dynamic blacklist has reached the
maximum and a new entry needs to be added, the new entry will replace the one
with the shortest remaining aging time.
● Users can run the CLR GNBXNDYNBLACKLIST command to delete Xn dynamic
blacklists before the Xn dynamic blacklist aging timer expires.
● The DSP GNBXNDYNBLACKLIST command can be executed to query Xn dynamic
blacklists.
● When the Xn dynamic blacklist switch is turned on, the peer gNodeB is removed
even if it is in the Xn whitelist. This is because the peer gNodeB information cannot
be obtained when an initial Xn self-setup procedure fails.
● Xn self-removal based on link faults
Xn self-removal at the local gNodeB will be triggered when the Xn interface
malfunctions for one hour.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 42

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

● Xn self-removal based on interface usage

The gNodeB periodically collects the Xn interface usage to remove the Xn
links with low usage. The usage is calculated based on the number of
handovers of neighboring gNodeBs in a measurement period (24 hours). The
Xn links with no handovers within seven consecutive measurement periods
will be removed.
The Xn self-removal based on interface usage is performed in accordance with
the procedure defined in 8.4.6 "Xn Removal" in 3GPP TS 38.423 V15.3.0, as
shown in Figure 5-5.

Figure 5-5 Xn self-removal based on interface usage

The detailed procedure is as follows:

a. gNodeB 1 sends gNodeB 2 an XN REMOVAL REQUEST message,
instructing gNodeB 2 to remove its Xn interface. gNodeB 2 sends an XN
REMOVAL RESPONSE message and removes the Xn interface.
b. After receiving the XN REMOVAL RESPONSE message, gNodeB 1 removes
its Xn interface.

In the case of hybrid SA and NSA networking where the user planes of the X2 and Xn
interfaces use the same IP address, the peer of the Xn-U interface is not removed when Xn
self-removal is triggered to ensure that services on the X2 interface are not affected.

Xn-U Self-Removal
The gNodeB supports self-removal of Xn-U transmission links and self-removal of
the USERPLANEPEER MO with USERPLANEPEER.CTRLMODE set to
AUTO_MODE.
The gNodeB determines whether to automatically remove Xn-U transmission links
as follows:
● Self-removal based on link faults
When the GTP-U check result indicates that all the transmission links
corresponding to USERPLANEPEER MOs are faulty and the fault persists for
more than one hour, the base station removes the corresponding
USERPLANEPEER MOs and transmission links (no more than 50 links are
removed at one time).
● Self-removal based on the aging mechanism
The gNodeB marks a transmission link as aged and processes as follows if the
link has not been used for any UE for more than one hour:

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 43

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

– When the GTP-U check result indicates that all the transmission links
corresponding to USERPLANEPEER are normal or only some of the links
are faulty, the base station checks whether the number of established
transmission links reaches or exceeds 90% of the maximum allowed
number of transmission links. If it does, the base station removes aged
transmission links (no more than 50 links are removed at one time). If it
does not, the base station does not remove aged transmission links.
– If a new transmission link is required for UE handover services and the
number of established transmission links reaches or exceeds 90% of the
maximum allowed number of transmission links, the gNodeB randomly
selects an aged transmission link, removes it, and then sets up a new link.
Otherwise, the gNodeB does not remove aged transmission links.
– If the maximum allowed number of transmission links is reached but
there is no aged link, new Xn-U interfaces cannot be generated during
the UE handover.

5.1.4 Xn Blacklist and Xn Whitelist

Operators can define Xn blacklists and whitelists. If the peer gNodeB is in the Xn
blacklist, the Xn interface between the two gNodeBs cannot be automatically set
up. If the peer gNodeB is in the Xn whitelist, the Xn interface between the two
gNodeBs cannot be automatically removed. Users can run the ADD
GNBXNBLACKWHITELIST command to add gNodeBs to an Xn blacklist or
whitelist. The Xn blacklist and whitelist combined can contain a maximum of 64
entries.

If an Xn interface is no longer required after the peer gNodeB that has established
the Xn link is added to the Xn blacklist, you are advised to manually delete the
SCTP peer of the Xn interface.

To remove the SCTP peer corresponding to the peer gNodeB, perform the following steps:
1. Run the DSP GNBCUXNINTERFACE command to obtain the peer IP address of the
control plane of the gNodeB CU Xn interface corresponding to the peer gNodeB ID.
2. Run the LST SCTPPEER command to query the SCTP peer ID corresponding to the peer
IP address.
3. Run the RMV SCTPPEER2EPGRP command to remove the SCTP peer from the endpoint
group.
4. Run the RMV SCTPPEER command to remove the SCTP peer.

5.1.5 Xn-C Interface Specifications

Xn-C is the interface between gNodeBs for implementing control plane functions.
The specifications for a gNodeB are as follows:

● When the UMPTe is used, a maximum of 384 Xn-C interfaces can be

configured.
● When the UMPTg is used, a maximum of 512 Xn-C interfaces can be
configured.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 44

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

5.1.6 Application Restrictions

The gNodeB supports the self-setup of two USERPLANEPEER MOs at the same
time. The self-setup request of more than two USERPLANEPEER MOs will be
rejected, which may result in UE access failures.

5.2 Network Analysis

5.2.1 Benefits
Xn self-management simplifies configuration operations, reduces the OPEX of
operators, and improves gNodeB resource usage.

5.2.2 Impacts

Network Impacts
None

Function Impacts
None

5.3 Requirements

5.3.1 Licenses
N/A

5.3.2 Software

Prerequisite Functions
None

Mutually Exclusive Functions

None

5.3.3 Hardware

Base Station Models

● 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 45

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Boards
All NR-capable main control boards support this function. To learn which main
control boards are NR-capable, see technical specifications of the BBU in 3900 &
5900 Series Base Station Product Documentation.

RF Modules
This function does not depend on RF modules.

5.3.4 Networking
For the QoS requirements of Xn interface for transmission networking, see
Transmission Resource Management.

5.3.5 Others
None

5.4 Operation and Maintenance

5.4.1 Data Configuration

5.4.1.1 Data Preparation

The following table describes the parameters that must be set in an
SCTPTEMPLATE MO.

Parameter Parameter ID Setting Notes

Name

SCTP Parameters SCTPTEMPLATE.SCTPTE Set this parameter based on the

Template ID MPLATEID network plan.

The following table describes the parameters that must be set in an SCTPHOST
MO.

Parameter Parameter ID Setting Notes

Name

SCTP Host ID SCTPHOST.SCTPHOSTID Set this parameter based on the

network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 46

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Parameter Parameter ID Setting Notes

Name

IP Version SCTPHOST.IPVERSION The IP protocol version of the

local end must be the same as
that of the peer end.
The IP protocol version of the
user plane must be the same as
that of the control plane.

First Local IP SCTPHOST.SIGIP1V4 If SCTPHOST.IPVERSION is set

Address to IPv4, configure a local
control-plane IPv4 address.

First Local IPv6 SCTPHOST.SIGIP1V6 If SCTPHOST.IPVERSION is set

Address to IPv6, configure a local
control-plane IPv6 address.

Second Local IP SCTPHOST.SIGIP2V4 If SCTPHOST.IPVERSION is set

Address to IPv4, configure a local
control-plane IPv4 address.

Second Local SCTPHOST.SIGIP2V6 If SCTPHOST.IPVERSION is set

IPv6 Address to IPv6, configure a local
control-plane IPv6 address.

Local SCTP Port SCTPHOST.PN Set this parameter based on the

No. network plan.

SCTP Parameters SCTPHOST.SCTPTEMPL Set this parameter based on the

Template ID ATEID network plan.

(Optional) The following table describes the parameters that must be set in an
SCTPPEER MO. This MO is required only for manual Xn peer configuration.

Parameter Parameter ID Setting Notes

Name

SCTP Peer ID SCTPPEER.SCTPPEERID Set this parameter based on the

network plan.

IP Version SCTPPEER.IPVERSION The IP protocol version of the

local end must be the same as
that of the peer end.
The IP protocol version of the
user plane must be the same as
that of the control plane.

First Peer IP SCTPPEER.SIGIP1V4 If SCTPPEER.IPVERSION is set to

Address IPv4, configure a peer control-
plane IPv4 address.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 47

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Parameter Parameter ID Setting Notes

Name

First Peer IPv6 SCTPPEER.SIGIP1V6 If SCTPPEER.IPVERSION is set to

Address IPv6, configure a peer control-
plane IPv6 address.

Second Peer IP SCTPPEER.SIGIP2V4 If SCTPPEER.IPVERSION is set to

Address IPv4, configure a peer control-
plane IPv4 address.

Second Peer IPv6 SCTPPEER.SIGIP2V6 If SCTPPEER.IPVERSION is set to

Address IPv6, configure a peer control-
plane IPv6 address.

Peer SCTP Port SCTPPEER.PN Set this parameter based on the

No. network plan.

The following table describes the parameters that must be set in a

USERPLANEHOST MO.

Parameter Parameter ID Setting Notes

Name

User Plane Host USERPLANEHOST.UPH Set this parameter based on the

ID OSTID network plan.

IP Version USERPLANEHOST.IPVER The IP protocol version of the

SION local end must be the same as
that of the peer end.
The IP protocol version of the
user plane must be the same as
that of the control plane.

Local IP Address USERPLANEHOST.LOCIP If USERPLANEHOST.IPVERSION

V4 is set to IPv4, configure a local
user-plane IPv4 address.

Local IPv6 USERPLANEHOST.LOCIP If USERPLANEHOST.IPVERSION

Address V6 is set to IPv6, configure a local
user-plane IPv6 address.

(Optional) The following table describes the parameters that must be set in a
USERPLANEPEER MO. This MO is required only for manual Xn peer configuration.

Parameter Parameter ID Setting Notes

Name

User Plane Peer USERPLANEPEER.UPPEE Set this parameter based on the

ID RID network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 48

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Parameter Parameter ID Setting Notes

Name

IP Version USERPLANEPEER.IPVER The IP protocol version of the

SION local end must be the same as
that of the peer end.
The IP protocol version of the
user plane must be the same as
that of the control plane.

Peer IP Address USERPLANEPEER.PEERI If USERPLANEPEER.IPVERSION

PV4 is set to IPv4, configure a peer
user-plane IPv4 address.

Peer IPv6 USERPLANEPEER.PEERI If USERPLANEPEER.IPVERSION

Address PV6 is set to IPv6, configure a peer
user-plane IPv6 address.

The following table describes the parameters that must be set in the EPGROUP
MO. It is recommended that the USERPLANEHOST and USERPLANEPEER MOs
used by Xn interfaces of an operator be configured into the same EPGROUP MO.
SCTPHOST and SCTPPEER MOs used by Xn interfaces of an operator should also
be configured into the same EPGROUP MO.

Parameter Parameter ID Setting Notes

Name

End Point Group EPGROUP.EPGROUPID Set this parameter based on the

ID network plan.

SCTP Host List EPGROUP.SCTPHOSTLIS Set this parameter based on the

T network plan. Add an SCTP host
to the endpoint group.

SCTP Peer List EPGROUP.SCTPPEERLIS Set this parameter based on the

T network plan. Add an SCTP peer
to the endpoint group.

User Plane Host EPGROUP.USERPLANEH Set this parameter based on the

List OSTLIST network plan. Add a user-plane
host to the endpoint group.

User Plane Peer EPGROUP.USERPLANEP Set this parameter based on the

List EERLIST network plan. Add a user-plane
peer to the endpoint group.

The following table describes the parameters that must be set in the
gNBXnSonConfig MO.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 49

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Parameter Name Parameter ID Option Setting Notes

Xn SON Configuration gNBXnSonConfig. ● XN_SON_S Set this

Switch XnSonConfigSwitc ETUP_SW parameter
h ● XN_SON_D based on the
EL_SW network plan.
● XN_SON_D
YN_BLACK
LIST_SW

The following table describes the parameters that must be set to configure the
reference relationship between the gNBCUXn and EPGROUP MOs.

Parameter Parameter ID Setting Notes

Name

gNodeB CU Xn gNBCUXn.gNBCuXnId Set this parameter based on the

ID network plan.

Control Plane gNBCUXn.CpEpGroupId Set this parameter based on the

Endpoint Group network plan.
ID

User Plane gNBCUXn.UpEpGroupId Set this parameter based on the

Endpoint Group network plan.
ID

The following table describes the parameters that must be set in the
gNBXnBlackWhiteList MO.

Parameter Parameter ID Setting Notes

Name

Mobile Country gNBXnBlackWhiteL- Set this parameter based on the

Code ist.MCC network plan.

Mobile Network gNBXnBlackWhiteL- Set this parameter based on the

Code ist.Mnc network plan.

gNodeB ID gNBXnBlackWhiteL- Set this parameter based on the

ist.gNBId network plan.

Xn List Type gNBXnBlackWhiteL- Set this parameter based on the

ist.XnListType network plan.

The following table describes the parameters that must be set to remove a
gNodeB Xn dynamic blacklist.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 50

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

Parameter Parameter ID Setting Notes

Name

Clear Mode ClearMode Set this parameter based on the

network plan.

5.4.1.2 Using MML Commands

Xn Self-Setup
//Configuring common parameters
//(Optional) Adding an SCTP template. By default, the gNodeB has an SCTP template with
SCTPTEMPLATEID set to 0.
ADD SCTPTEMPLATE: SCTPTEMPLATEID=1, SWITCHBACKFLAG=ENABLE;
//Adding an endpoint group for the Xn interface
ADD EPGROUP: EPGROUPID=1;
//Adding an Xn control-plane host (IPv4 used as an example)
ADD SCTPHOST: SCTPHOSTID=1, IPVERSION=IPv4, SIGIP1V4="5.5.3.38", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=38422, SCTPTEMPLATEID=1;
//(Optional) Adding an Xn control-plane peer. This command is required for manually configuring Xn
control-plane's peer gNodeB.
ADD SCTPPEER: SCTPPEERID=1, IPVERSION=IPv4, SIGIP1V4="5.5.3.21", PN=38422;
//Adding an Xn user-plane host
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="5.5.3.38", IPSECSWITCH=DISABLE;
//(Optional) Adding an Xn user-plane peer. This command is required for manually configuring Xn user-
plane's peer gNodeB.
ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, PEERIPV4="5.5.3.21", IPSECSWITCH=DISABLE;
//Adding the Xn user-plane host to the endpoint group
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;
//(Optional) Adding the Xn user-plane peer to the endpoint group. This command is required for manually
configuring Xn user-plane's peer gNodeB.
ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;
//Adding the Xn control-plane host to the endpoint group
ADD SCTPHOST2EPGRP: EPGROUPID=1, SCTPHOSTID=1;
//(Optional) Adding the Xn control-plane peer to the endpoint group. This command is required for
manually configuring Xn control-plane's peer gNodeB.
ADD SCTPPEER2EPGRP: EPGROUPID=1, SCTPPEERID=1;
//Enabling the Xn self-setup function
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_SETUP_SW-1;
//Adding an Xn object on the gNodeB side
ADD GNBCUXN: gNBCuXnId=1, CpEpGroupId=1, UpEpGroupId=1;

Xn Self-Removal
//Enabling the Xn self-removal function
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_DEL_SW-1;
//Turning on the Xn dynamic blacklist switch
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_DYN_BLACKLIST_SW-1;
//Removing a gNodeB Xn dynamic blacklist
CLR GNBXNDYNBLACKLIST: ClearMode=CLR_ALL;

Xn Blacklist and Xn Whitelist

//Adding a gNodeB Xn blacklist and whitelist
ADD GNBXNBLACKWHITELIST: Mcc="262", Mnc="02", gNBId=1, XnListType=XN_BLACKLIST_TYPE;
ADD GNBXNBLACKWHITELIST: Mcc="262", Mnc="02", gNBId=2, XnListType=XN_WHITELIST_TYPE;

Deactivation Command Examples

//Deactivating Xn self-setup
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_SETUP_SW-0;

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 51

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 5 Xn Self-Management

//Deactivating Xn self-removal
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_DEL_SW-0;

//Deactivating Xn dynamic blacklisting

MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_DYN_BLACKLIST_SW-0;

5.4.1.3 Using the MAE-Deployment

For detailed operations, see MAE-Deployment-based Feature Configuration.

5.4.2 Activation Verification

(Automatic Xn peer configuration) The activation verification procedures for Xn
self-setup, self-update, and self-removal are as follows:

Step 1 On the MAE-Access client, choose SON > SON Log.

Step 2 Click Synchronize, select target gNodeBs, and click OK.
Step 3 On the Query SON Log tab page, select NR Xn Interface Self Management Log
from the Log Category drop-down list box in the upper left corner. In the Event
Name area, select Automatically Establish Signaling Link, Automatically
Update Signaling Link, Automatically Delete Signalling Link, Automatically
Establish Service Link, and Automatically Delete Service Link. Then, select
target gNodeBs in the Log Source area to check different types of Xn self-
configuration operation logs.

----End
Expected result: The operation logs contain Xn self-setup, self-update, and self-
removal events.

5.4.3 Network Monitoring

If the Xn interface is faulty, check whether any of the alarms listed in Table 5-1
has been reported. If an alarm has been reported, clear the alarm by referring to
the alarm reference.

Table 5-1 Alarms related to the Xn interface

Alarm ID Alarm Name Severity

29810 gNodeB Xn Interface Major

Fault

25954 User Plane Fault Major

25888 SCTP Link Fault Major

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 52

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

6 Direct IPsec for Xn Interface

6.1 Principles
When two gNodeBs are connected over the Xn interface through an SeGW, the Xn
interface delay is affected by the SeGW location and the network topology. The
data transmission delay in this case is long. With direct IPsec, direct IPsec tunnels
are set up between two gNodeBs to reduce the transmission delay over the Xn
interface.
Figure 6-1 and Figure 6-2 show the typical networking of direct IPsec for the Xn
interface between gNodeBs.

Figure 6-1 Typical networking 1 of direct IPsec

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 53

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Figure 6-2 Typical networking 2 of direct IPsec

6.1.1 Direct IPsec Setup

Xn control plane peer and user plane peer (corresponding to the SCTPPEER and
USERPLANEPEER MOs) can be automatically or manually configured to achieve
direct IPsec setup between gNodeBs. If the SCTPPEER or USERPLANEPEER MO is
manually configured, the SECURITYPEER MO must be configured as well. Figure
6-3 shows the configuration model.

Figure 6-3 Configuration model

Direct IPsec is classified into direct IPv4 IPsec and direct IPv6 IPsec.

● Only one IPv4 address can be configured for direct IPv4 IPsec self-setup, and
only one IPv6 address can be configured for direct IPv6 IPsec self-setup.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 54

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

● In IPv4/IPv6 dual-stack scenarios, only one IPv4 address and one IPv6 address
can be configured for direct IPsec self-setup.
If the local and peer base stations are configured with IPv4 and IPv6 addresses
and enabled with direct IPv4 IPsec self-setup and direct IPv6 IPsec self-setup, the
peer base station selects the address type based on the value of the
EPGROUP.IPVERPREFERENCE parameter.

6.1.1.1 Direct IPv4 IPsec Self-Setup

Direct IPv4 IPsec self-setup for the Xn interface can be implemented in either of
the following methods:
● Method 1: Direct IPv4 IPsec self-setup only for the Xn user plane
● Method 2: Direct IPv4 IPsec self-setup for the Xn control plane and user plane
Inter-gNodeB coordination-based services in non-ideal transmission scenarios have
transmission latency requirements only for the Xn user plane. In addition, the IPv4
IPsec specifications (number of IPv4 IPsec tunnels) of the gNodeB cannot support
direct IPsec for both the Xn control plane and user plane, therefore, Method 1 is
recommended.
The direct IPv4 IPsec self-setup procedure in the two methods is almost the same.
As shown in Figure 6-4, through the AMF, gNodeB 1 and gNodeB 2 send the
UPLINK RAN CONFIGURATION TRANSFER and DOWNLINK RAN
CONFIGURATION TRANSFER messages between each other. These messages carry
the SON Information Request and SON Information Reply messages to implement
the automatic Xn interface configuration for gNodeB 1 and gNodeB 2. The main
difference between Method 1 and Method 2 is that the contents carried in SON
Information Request and SON Information Reply are different.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 55

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Figure 6-4 Procedure for automatically setting up IPv4 IPsec for an Xn interface

The self-setup process is described as follows:

● The USERPLANEHOST.IPSECSWITCH parameter must be set to ENABLE for both the

user planes of the two gNodeBs. Otherwise, the direct IPv4 IPsec setup will not be
enabled during the Xn-U setup.
● The SCTPHOST.SIGIP1SECSWITCH parameter must be set to ENABLE for both the
control planes of the two gNodeBs. Otherwise, the direct IPv4 IPsec setup will not be
enabled during the Xn-C setup.
A peer IKE IP address (specified by SECURITYPEER.PEERIKEIPV4) can be used to establish
only one IPv4 IPsec tunnel.
● Method 1: (Recommended) Automatic direct IPv4 IPsec setup for only the Xn
user plane:
In this mode, the USERPLANEHOST.IPSECSWITCH and
SCTPHOST.SIGIP1SECSWITCH parameters must be set to ENABLE and
DISABLE, respectively. Otherwise, direct IPv4 IPsec self-setup cannot be
achieved for the user plane.
a. The SON Information Request message sent from gNodeB 1 to gNodeB 2
carries the transport network layer addresses of the gNodeB 1 Xn
interface. The addresses include the Xn-C address, Xn-U address, and Xn-
U IPv4 IPsec address.
b. gNodeB 2 automatically configures the Xn-C interface, Xn-U interface,
and Xn-U IPv4 IPsec addresses based on the received information.
c. The SON Information Reply message sent from gNodeB 2 to gNodeB 1
carries the transport network layer addresses of the gNodeB 2 Xn

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 56

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

interface. The addresses include the Xn-C address, Xn-U address, and Xn-
U IPv4 IPsec address.
d. gNodeB 1 automatically configures the Xn-C interface, Xn-U interface,
and Xn-U IPv4 IPsec addresses based on the returned information.

● gNodeB 1 automatically sets up Xn-C and Xn-U transmission links based on

the gNBCUXn, SCTPHOST, USERPLANEHOST, and EPGROUP MOs as well as
the automatically generated SCTPPEER and USERPLANEPEER MOs.
● gNodeB 1 automatically generates the direct IPv4 IPsec tunnel for the Xn user
plane based on the gNodeB 2 Xn-U IPv4 IPsec address, Xn-C address, and Xn-
U address included in the signaling messages, as well as the automatically
generated SECURITYPEER, ACL, ACLRULE, IPSECPOLICY, IKEPEER, and
IPSECBIND (old model)/IPSECBINDITF (new model) MOs. When
GTRANSPARA.TRANSCFGMODE is set to OLD, the old model is used. When
this parameter is set to NEW, the new model is used.

When direct IPv4 IPsec is set up only for the Xn-U interface, the current IPv4
IPsec specifications allow direct IPsec tunnels to be set up for all Xn interfaces
between gNodeBs.
● Method 2: Direct IPv4 IPsec self-setup for the Xn control plane and user plane:
In this mode, the SCTPHOST.SIGIP1SECSWITCH and
USERPLANEHOST.IPSECSWITCH parameters must be set to ENABLE.
Otherwise, direct IPv4 IPsec self-setup cannot be achieved for the user and
control planes.
a. The SON Information Request message sent from gNodeB 1 to gNodeB 2
carries the transport network layer addresses of the gNodeB 1 Xn
interface. The addresses include the Xn-C address, Xn-C IPv4 IPsec
address, Xn-U address, and Xn-U IPv4 IPsec address.
b. gNodeB 2 automatically configures the Xn-C interface, Xn-U IPv4 IPsec,
Xn-U interface, and Xn-U IPv4 IPsec addresses based on the received
information.
c. The SON Information Reply message sent from gNodeB 2 to gNodeB 1
carries the transport network layer addresses of the gNodeB 2 Xn
interface. The addresses include the Xn-C address, Xn-C IPv4 IPsec
address, Xn-U address, and Xn-U IPv4 IPsec address.
d. gNodeB 1 automatically configures the Xn-C interface address, Xn-U IPv4
IPsec address, Xn-U interface address, and Xn-U IPv4 IPsec address based
on the returned information.

● gNodeB 1 automatically sets up Xn-C and Xn-U transmission links based on

the gNBCUXn, SCTPHOST, USERPLANEHOST, and EPGROUP MOs as well as
the automatically generated SCTPPEER and USERPLANEPEER MOs.
● gNodeB 1 automatically generates the direct IPv4 IPsec tunnel for the Xn user
and control planes based on the gNodeB 2 Xn-C IPv4 IPsec address, Xn-U IPv4
IPsec address, Xn-C address, and Xn-U address contained in the signaling
messages, as well as the automatically generated SECURITYPEER, ACL,
ACLRULE, IPSECPOLICY, IKEPEER, and IPSECBIND (old model)/
IPSECBINDITF (new model) MOs.

When the IPv4 IPsec specifications are limited, self-setup of new Xn interfaces
fails and ALM-29810 gNodeB Xn Interface Fault is reported. For details about

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 57

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

IPv4 IPsec specifications, see MOs SECURITYPEER, ACL, ACLRULE,

IPSECPOLICY, IKEPEER, and IPSECBIND (old model)/IPSECBINDITF (new
model) in MO and Parameter Reference in 3900 & 5900 Series Base Station
Product Documentation. The possible fault scenarios are as follows:
– When direct IPv4 IPsec self-setup is required for Xn-C and Xn-U
interfaces, separate direct IPv4 IPsec tunnels are set up for the Xn-C and
Xn-U interfaces. However, due to the limitations of current IPv4 IPsec
specifications, not all Xn-C and Xn-U interfaces can be configured with
direct IPv4 IPsec tunnels.
– When the IPv4 IPsec specifications reach the upper limit, if a non-direct
IPv4 IPsec tunnel manually set up for the Xn interface needs to be
changed to a direct IPv4 IPsec tunnel, the Xn interface will be removed
due to the limitation of direct IPv4 IPsec specifications.
When Xn interface matches multiple IPsec tunnels, the
GTRANSPARA.DIRECTIPSECPRIMATCHSW parameter can be used to adjust
the IPv4 IPsec policy matching priority. That is, the parameter specifies
whether the Xn interface preferentially matches direct IPv4 IPsec tunnels or
IPv4 IPsec tunnels passing through the SeGW.
– When this parameter is set to DISABLE, the IPv4 IPsec policy with a
smaller sequence number (specified by IPSECPOLICY.SPSN) is
preferentially matched.
– When this parameter is set to ENABLE, the IPv4 IPsec policy of a self-
setup direct IPsec tunnel is preferentially matched. If the direct IPsec
tunnel corresponding to the IPsec policy is faulty, the IPv4 IPsec policy of
normal IPsec tunnels is preferentially used.

6.1.1.2 Direct IPv6 IPsec Self-Setup

In direct IPv6 IPsec self-setup for the Xn interface, only direct IPv6 IPsec self-setup
for the Xn control plane and user plane is supported. This method is similar to
direct IPv4 IPsec self-setup for the Xn control plane and user plane. Figure 6-5
shows the procedure for direct IPv6 IPsec self-setup for the Xn interface. The
difference between the two procedures lies in the contents carried in the SON
Information Request and SON Information Reply messages.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 58

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Figure 6-5 Procedure for direct IPv6 IPsec self-setup for the Xn interface

The procedure for direct IPv6 IPsec self-setup for the Xn control plane and user
plane is as follows:

The USERPLANEHOST.IPSECSWITCH and SCTPHOST.SIGIP1SECSWITCH parameters must

be set to ENABLE for the two gNodeBs with direct IPv6 IPsec self-setup for the Xn control
plane and user plane.
When the user plane and control plane of the Xn interface share an IPv6 service address,
both the Xn user plane and control plane are protected by direct IPv6 IPsec if either
USERPLANEHOST.IPSECSWITCH or SCTPHOST.SIGIP1SECSWITCH is set to ENABLE.
A peer IKE IP address (specified by SECURITYPEER.PEERIKEIPV6) can be used to set up
only one IPv6 IPsec tunnel.

1. The SON Information Request message sent from gNodeB 1 to gNodeB 2

carries the transport network layer addresses of the gNodeB 1 Xn interface.
The addresses include the Xn-C address, Xn-C IPv6 IPsec address, Xn-U
address, and Xn-U IPv6 IPsec address.
2. gNodeB 2 automatically configures the Xn-C interface, Xn-U interface, and
Xn-U IPv6 IPsec addresses based on the received information.
3. The SON Information Reply message sent from gNodeB 2 to gNodeB 1 carries
the transport network layer addresses of the gNodeB 2 Xn interface. The
addresses include the Xn-C address, Xn-C IPv6 IPsec address, Xn-U address,
and Xn-U IPv6 IPsec address.
4. gNodeB 1 automatically configures the Xn-C interface address, Xn-U IPv6
IPsec address, Xn-U interface address, and Xn-U IPv6 IPsec address based on
the returned information.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 59

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

● gNodeB 1 automatically sets up Xn-C and Xn-U transmission links based on the
gNBCUXn, SCTPHOST, USERPLANEHOST, and EPGROUP MOs as well as the
automatically generated SCTPPEER and USERPLANEPEER MOs.
● gNodeB 1 sets up direct IPv6 IPsec tunnels for the Xn-C and Xn-U interfaces based on
the information of gNodeB 2 carried in the signaling messages as well as the
automatically generated MOs. The information includes the gNodeB 2 control-plane
IPv6 IPsec address, user-plane IPv6 IPsec address, control-plane IP address, and user-
plane IP address. The automatically generated MOs include SECURITYPEER, ACL,
ACLRULE, IPSECPOLICY, IKEPEER, IPSECBINDITF, TUNNELITF, INTERFACE, and
IPROUTE6.
● After direct IPv6 IPsec is enabled, the control- and user-plane IP addresses of the Xn
interface cannot be directly accessed through external networks. That is, the Xn
interface cannot be negotiated as a plaintext channel.
● When direct IPv6 IPsec self-setup is enabled for base stations, the routing domains of
the control plane and user plane of the Xn interface must be the same. That is, the
values of SCTPHOST.VRFIDX and USERPLANEHOST.VRFIDX parameters must be the
same among all base stations for which direct IPv6 IPsec self-setup is enabled.

When an Xn interface is configured with both a direct IPv6 IPsec tunnel and an
IPv6 IPsec tunnel connected to the SeGW, the route priorities of these two tunnels
can be adjusted to determine whether data streams preferentially match the direct
IPv6 IPsec tunnel or IPv6 IPsec tunnel connected to the SeGW. The route priority of
the direct IPv6 IPsec tunnel is specified by the
SECURITYTEMPLATE.IPROUTE6PREF parameter.

6.1.2 Static Blacklist & Whitelist

Static Blacklist
If a security peer is included in the static blacklist for direct IPsec tunnels of a local
end, the local end will not establish a direct IPsec tunnel to the peer end.
If the gNodeB can establish an Xn interface through the SeGW, the peer gNodeB
can be added to the static blacklist for direct IPsec tunnels.
The ADD DIRECTIPSECBLACKLIST command can be executed to configure a static
direct IPsec blacklist.
You are advised to configure the static direct IPsec blacklist before enabling the
direct IPsec function. If direct IPsec tunnels have been set up between the local
and peer base stations before the blacklist is configured, you need to manually
remove the SECURITYPEER MO before adding a static direct IPsec blacklist.

Static Whitelist
If a network segment is included in the static whitelist for direct IPsec tunnels of a
local end, the local end will only establish direct IPsec tunnels to the peer ends
within the whitelist.
If the gNodeB only needs to establish direct IPsec tunnels to the peer ends on
some network segments, the segments can be added to the static whitelist for
direct IPsec tunnels.
The ADD DIRECTIPSECWHITELIST command can be executed to configure the
static whitelist for direct IPsec tunnels.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 60

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Static blacklist and static whitelist cannot be both configured.

Static whitelist and direct IPsec self-removal cannot be both configured.

6.1.3 Self-Update
gNodeBs support self-update of direct IPsec. This function is controlled by the
GEPMODELPARA.DIRIPSECUPDATESW parameter. Assume that an Xn interface is
functioning properly after self-update of direct IPsec is enabled. An Xn self-setup
procedure is triggered if the Xn control plane is still functioning properly after any
of the following reconfigurations is performed. Then, the local base station sends
information about direct IPsec to the peer base station. A direct IPsec self-update
is performed if direct IPsec is enabled on the peer base station. The
reconfigurations are as follows:
● The value of the USERPLANEHOST.IPSECSWITCH parameter corresponding
to the EPGROUP MO of the Xn interface is changed from DISABLE to
ENABLE, and the corresponding SECURITYHOST.SEGWSWITCH parameter
value is DISABLE.
● (Applied only to direct IPv4 IPsec self-setup) The endpoint group
corresponding to the Xn interface is modified, a new SECURITYHOST MO is
referenced, and the corresponding SECURITYHOST.SEGWSWITCH parameter
value is DISABLE.
● The value of the USERPLANEHOST.IPSECSWITCH parameter corresponding
to the EPGROUP MO of the Xn interface is ENABLE, and the value of the
corresponding SECURITYHOST.SEGWSWITCH parameter is changed from
ENABLE to DISABLE.
● The value of the USERPLANEHOST.IPSECSWITCH parameter corresponding
to the EPGROUP MO of the Xn interface is ENABLE, the value of the
corresponding SECURITYHOST.SEGWSWITCH parameter is DISABLE, and the
SECURITYHOST.LOCIKEIPV4 parameter value is changed.
● The value of the USERPLANEHOST.IPSECSWITCH parameter corresponding
to the endpoint group of an Xn interface is ENABLE, the value of the
corresponding SECURITYHOST.SEGWSWITCH parameter is DISABLE, and the
SECURITYHOST.LOCIKEIPV6 parameter value is changed.
● The ADD GNBCUXN command is executed to add an Xn interface.
There is a 3-minute configuration protection period for the update of direct IPsec.
If any of the preceding configurations is changed, the configuration protection will
be triggered. The base station will wait 3 minutes to see if there is any further
modifications to the configurations when the protection period ends. If there exist
changes, a direct IPsec self-update is triggered.

If the Xn link is normal but no direct IPsec tunnel is set up, you can set the
GEPMODELPARA.DIRIPSECUPDATESW parameter to ENABLE to enable the self-setup of
direct IPsec triggered by Xn self-update.

6.1.4 Self-Removal
Self-removal of direct IPsec applies in the following scenario: Direct IPsec is
enabled on the gNodeB and its connected gNodeBs, but direct IPsec tunnels are

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 61

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

unreachable to the connected gNodeBs in transmission network planning. If such

a scenario does not exist, this function is not recommended. This function is
controlled by the GEPMODELPARA.DIRIPSECAUTODELSW parameter.
When detecting a direct IPsec fault caused by IKE SA negotiation failure, the
gNodeB reports ALM-25891 IKE Negotiation Failure if the
GEPMODELPARA.DIRIPSECAUTODELTIMER parameter is set to a non-zero value.
This facilitates transmission fault locating. The gNodeB waits for a period of time
specified by the GEPMODELPARA.DIRIPSECAUTODELTIMER parameter. If the
fault persists after the timer expires, the gNodeB removes the direct IPsec tunnel
and ALM-25891 IKE Negotiation Failure is cleared. It is recommended that the
GEPMODELPARA.DIRIPSECAUTODELTIMER parameter be set to one week or
longer. If it is set to a too short value, it is possible that the gNodeB has triggered
a direct IPsec self-removal and alarm clearance before users can troubleshoot
transmission faults based on the alarm.
If configuring the gNodeB is prohibited, or there is a large number of to-be-
removed direct IPsec tunnels, the fault recovery time is longer than the time
specified by the GEPMODELPARA.DIRIPSECAUTODELTIMER parameter. This gap
is dependent on the gNodeB configuration prohibition duration or the number of
to-be-removed direct IPsec tunnels.

6.1.5 Application Restrictions

Direct IPsec does not apply to Xn-C interfaces adopting SCTP dual-homing.
When direct IPsec is configured for the user plane of the Xn interface, it is
recommended that the NG and Xn interfaces reference different
USERPLANEHOST MOs. This is because the USERPLANEHOST MO referenced by
the NG interface requires that the IPsec self-setup switch be set to off but the
USERPLANEHOST MO referenced by the Xn interface requires that the IPsec self-
setup switch be set to on.
When direct IPsec is configured only for the user plane of the Xn interface and the
setting of the IPsec self-setup switch of the USERPLANEHOST MO changes, the
configuration changes take effect only when Xn self-setup is performed. When
direct IPsec is configured for the user and control planes of the Xn interface and
the configurations of the IPsec self-setup switch of the USERPLANEHOST and
SCTPHOST MOs change, the configuration changes take effect only when the Xn
self-setup is performed.

6.2 Network Analysis

6.2.1 Benefits
On a network secured using IPsec, the SeGW networking features significant delay
over the Xn interface; the direct IPsec networking reduces the length of the
transmission path, which reduces the delay over the Xn interface.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 62

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

6.2.2 Impacts

Network Impacts
IPsec ensures transmission security by encapsulating and encrypting IP packets.
However, this reduces the transmission efficiency of service packets on the bearer
network. For details, see IPsec.

Function Impacts
Function Function Switch Reference Description
Name

Multi- gNBSharingMode. Multi-Operator Direct IPsec self-setup

Operator gNBMultiOpShari Sharing is incompatible with
Sharing ngMode Multi-Operator
Sharing.

6.3 Requirements

6.3.1 Licenses
Feature ID Feature Name Model Sales Unit

FOFD-010080 IPsec NR0S0IPSEC00 Per gNodeB

6.3.2 Software

Prerequisite Functions
None

Mutually Exclusive Functions

None

6.3.3 Hardware

Base Station Models

● 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910.
● DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 63

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Boards
All NR-capable main control boards support this function. To learn which main
control boards are NR-capable, see technical specifications of the BBU in 3900 &
5900 Series Base Station Product Documentation.

RF Modules
This function does not depend on RF modules.

6.3.4 Others
None

6.4 Operation and Maintenance

6.4.1 When to Use

If Xn interfaces adopt IPsec tunnels across the SeGW and the service delay
requirements are not met, it is recommended that the transmission delays of
direct transmission paths of the Xn interface be measured before direct IPsec is
deployed:

● If the measured delay is less than the transmission delay of indirect

transmission paths of the Xn interface and meets the delay requirements for
to-be-deployed coordination-based features, the transport network
performance allows for direct IPsec deployment.
● If the measured delay is greater than or equal to the transmission delay of
indirect transmission paths of the Xn interface or does not meet the delay
requirements for to-be-deployed coordination-based features, the transport
network performance does not allow for direct IPsec deployment. In this case,
it is recommended that the transport network be optimized until the
requirements for direct IPsec deployment are met.

6.4.2 Precautions
When direct IPsec is configured on the Xn interface where the two gNodeBs at
two ends of the Xn interface are located in different network segments, respective
routes between the two gNodeBs must be configured.

6.4.3 Data Configuration

6.4.3.1 Data Preparation

Direct IPsec for Xn interface is based on Xn self-setup between gNodeBs. For
details about the configurations for Xn self-setup, see 5.4.1.1 Data Preparation.
This section describes only IPsec configurations.

The following table describes the parameters that must be set in a GTRANSPARA
MO to configure the direct IPsec priority matching switch.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 64

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

Direct IPSec Priorities GTRANSPARA.DIRECTIP Set this parameter to

Match Switch SECPRIMATCHSW ENABLE to deploy direct
IPsec. This parameter
applies only to direct
IPv4 IPsec.

The following table describes the parameters that must be set in an

IKEPROPOSAL MO.

Parameter Name Parameter ID Setting Notes

Proposal ID IKEPROPOSAL.PROPID Set this parameter based

on the network plan.

Authentication Method IKEPROPOSAL.AUTHME Set this parameter to

TH IKE_RSA_SIG when
digital certificate
authentication is used.
Set this parameter to the
same value for all
gNodeBs in the entire
network.

The following table describes the parameters that must be set in an

IPSECPROPOSAL MO.

Parameter Name Parameter ID Setting Notes

IPSec Proposal Name IPSECPROPOSAL.PROP Set this parameter based

NAME on the network plan.

The following table describes the parameters that must be set in a

SECURITYTEMPLATE MO. This MO applies only to IPsec-enabled scenarios.

Parameter Name Parameter ID Setting Notes

Security Parameters SECURITYTEMPLATE.SE This parameter specifies

Template ID CURITYTEMPLATEID the ID of the security
parameter template.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 65

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

SeGW Switch SECURITYTEMPLATE.SE Set this parameter to

GWSWITCH DISABLE when you
deploy direct IPsec,
which means that
gNodeBs adopt direct
IPsec negotiation.

IKE Proposal ID SECURITYTEMPLATE.PR Set this parameter based

OPID on the network plan.

IPSec Proposal Name SECURITYTEMPLATE.IPS Set this parameter based

ECPROPNAME on the network plan.

IKE Version SECURITYTEMPLATE.IKE Set this parameter based

VERSION on the network plan.

IPv6 Route Preference SECURITYTEMPLATE.IPR Set this parameter based

OUTE6PREF on the network plan.
This parameter applies
only to direct IPv6 IPsec.

The following table describes the parameters that must be set in a

SECURITYHOST MO.

Parameter Name Parameter ID Setting Notes

Security Host ID SECURITYHOST.SECURI Set this parameter based

TYHOSTID on the network plan.

SeGW Switch SECURITYHOST.SEGWS Set this parameter to

WITCH DISABLE when you
deploy direct IPsec,
which means that
gNodeBs adopt direct
IPsec negotiation.

IP Version SECURITYHOST.IPVERSI Set this parameter based

ON on the network plan.

Local IKE IP Address SECURITYHOST.LOCIKEI Set this parameter based

PV4 on the network plan.

Security Parameters SECURITYHOST.SECURI Set this parameter based

Template ID TYTEMPLATEID on the network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 66

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

VRF Index SECURITYHOST.VRFIDX Set this parameter based

on the network plan. The
value of this parameter
must be different from
the values of
SCTPHOST.VRFIDX and
USERPLANEHOST.VRFI
DX. This parameter
applies only to direct
IPv6 IPsec.

Configure the parameters in an SCTPTEMPLATE MO that is used to set

mandatory parameters for SCTP link setup over the Xn interface. For details about
the parameter settings, see 5.4.1.1 Data Preparation.

The following table describes the parameters that must be set in an SCTPHOST
MO to configure the local gNodeB information of the Xn-C interface.

Parameter Name Parameter ID Setting Notes

SCTP Host ID SCTPHOST.SCTPHOSTID Set this parameter based

on the network plan.

VRF Index SCTPHOST.VRFIDX Set this parameter based

on the network plan. The
value of this parameter
must be the same as
that of the
USERPLANEHOST.VRFID
X parameter but
different from that of the
SECURITYHOST.VRFIDX
parameter. This
parameter applies only
to direct IPv6 IPsec.

IP Version SCTPHOST.IPVERSION The IP protocol version

of the local end must be
the same as that of the
peer end.

First Local IP Address SCTPHOST.SIGIP1V4 If SCTPHOST.IPVERSION

is set to IPv4, configure a
local control-plane IPv4
address.

First Local IPv6 Address SCTPHOST.SIGIP1V6 If SCTPHOST.IPVERSION

is set to IPv6, configure a
local control-plane IPv6
address.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 67

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

IPSec Auto Configure SCTPHOST.SIGIP1SECS Set this parameter to

Switch for First Local IP WITCH ENABLE to deploy direct
IPsec.

Security Host ID for First SCTPHOST.SIGIP1SECH Set this parameter based

Local IP OSTID on the network plan.

Local SCTP Port No. SCTPHOST.PN Set this parameter based

on the network plan.

The following table describes the parameters that must be set in a

USERPLANEHOST MO to configure information about the local gNodeB of the
Xn-U interface.

Parameter Name Parameter ID Setting Notes

User Plane Host ID USERPLANEHOST.UPHO Set this parameter based

STID on the network plan.

VRF Index USERPLANEHOST.VRFI Set this parameter based

DX on the network plan. The
value of this parameter
must be the same as
that of the
SCTPHOST.VRFIDX
parameter but different
from that of the
SECURITYHOST.VRFIDX
parameter. This
parameter applies only
to direct IPv6 IPsec.

IP Version USERPLANEHOST.IPVER The IP protocol version

SION of the local end must be
the same as that of the
peer end.

Local IP Address USERPLANEHOST.LOCIP If

V4 USERPLANEHOST.IPVER
SION is set to IPv4,
configure a local user-
plane IPv4 address.

Local IPv6 Address USERPLANEHOST.LOCIP If

V6 USERPLANEHOST.IPVER
SION is set to IPv6,
configure a local user-
plane IPv6 address.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 68

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

IPSec Auto Configure USERPLANEHOST.IPSEC Set this parameter to

Switch SWITCH ENABLE to deploy direct
IPsec.

Security Host ID USERPLANEHOST.SECH Set this parameter based

OSTID on the network plan.

Configure the parameters in an EPGROUP MO that is used to set the endpoint

resource groups for an Xn interface. For details about the parameter settings, see
5.4.1.1 Data Preparation.
It is recommended that the USERPLANEHOST, USERPLANEPEER, SCTPHOST, and
SCTPPEER MOs that are used by Xn interfaces of one operator be configured in
the same EPGROUP MO. For details about the parameter settings, see 5.4.1.1
Data Preparation.
(Optional) Configure an RSCGRP (old model) or IPRSCGRP (new model) MO to
set a transmission resource group (old model) or an IP transmission resource
group (new model). This operation is required only when a dedicated transmission
resource group needs to be specified for the Xn interface. For details about the
parameter settings, see 5.4.1.1 Data Preparation.
(Optional) Configure an EP2RSCGRP (old model) or EP2IPRSCGRP (new model)
MO to set the mapping relationship between the user-plane endpoint and the
transmission resource group (old model) or IP transmission resource group (new
model). Then, add the corresponding USERPLANEPEER MOs to the user-defined
transmission resource group (old model) or IP transmission resource group (new
model) based on the mapping relationship. This operation is required only when a
dedicated transmission resource group needs to be specified for the Xn interface.
For details about the parameter settings, see 5.4.1.1 Data Preparation.
Configure the reference relationship between the gNBCUXn and EPGROUP MOs.
For details about the parameter settings, see 5.4.1.1 Data Preparation.
(Optional) The following table describes the parameters that must be set in a
GEPMODELPARA MO to configure self-removal of direct IPsec.

Parameter Name Parameter ID Setting Notes

Direct IPsec Automatic GEPMODELPARA.DIRIPS Set this parameter based

Deletion Switch ECAUTODELSW on the network plan.

Direct IPsec Automatic GEPMODELPARA.DIRIPS Set this parameter based

Deletion Timer ECAUTODELTIMER on the network plan.

(Optional) The following table describes the parameters that must be set in a
GEPMODELPARA MO to configure self-update of direct IPsec.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 69

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

Direct IPsec Update GEPMODELPARA.DIRIPS Set this parameter based

Switch ECUPDATESW on the network plan.

The following table describes the parameters that must be set in a

DIRECTIPSECBLACKLIST MO.

Parameter Name Parameter ID Setting Notes

ID of Blacklist for Direct DIRECTIPSECBLACK- Set this parameter based

IPsec Tunnel LIST.DIRECTIPSECBLACK on the network plan.
LISTID
IP Version DIRECTIPSECBLACK- Set this parameter based
LIST.IPVERSION on the network plan.

Security Peer IPv4 DIRECTIPSECBLACK- Set this parameter based

Address LIST.SECURITYPEERIPV4 on the network plan.
This parameter is valid
only when the
DIRECTIPSECBLACK-
LIST.IPVERSION
parameter is set to IPV4.

Security Peer IPv6 DIRECTIPSECBLACK- Set this parameter based

Address LIST.SECURITYPEERIPV6 on the network plan.
This parameter is valid
only when the
DIRECTIPSECBLACK-
LIST.IPVERSION
parameter is set to IPV6.

The following table describes the parameters that must be set in a

DIRECTIPSECWHITELIST MO.

Parameter Name Parameter ID Setting Notes

ID of Whitelist for Direct DIRECTIPSECWHITEL- Set this parameter based

IPsec Tunnel IST.DIRECTIPSECWHITE- on the network plan.
LISTID
IP Version DIRECTIPSECWHITEL- Set this parameter based
IST.IPVERSION on the network plan.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 70

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

Parameter Name Parameter ID Setting Notes

Security Peer IPv4 DIRECTIPSECWHITEL- Set this parameter based

Address IST.SECURITYPEERIPV4 on the network plan.
This parameter is valid
only when the
DIRECTIPSECBLACK-
LIST.IPVERSION
parameter is set to IPV4.

Mask DIRECTIPSECWHITEL- Set this parameter based

IST.MASK on the network plan.

Security Peer IPv6 DIRECTIPSECWHITEL- Set this parameter based

Address IST.SECURITYPEERIPV6 on the network plan.
This parameter is valid
only when the
DIRECTIPSECBLACK-
LIST.IPVERSION
parameter is set to IPV6.

IPv6 Address Prefix DIRECTIPSECWHITEL- Set this parameter based

Length IST.IPV6PFXLEN on the network plan.
This parameter is valid
only when the
DIRECTIPSECBLACK-
LIST.IPVERSION
parameter is set to IPV6.

6.4.3.2 Using MML Commands

Activating Direct IPsec for the Xn Interface

//Enabling the Xn self-setup function
MOD GNBXNSONCONFIG: XnSonConfigSwitch=XN_SON_SETUP_SW-1;
//Setting the direct IPsec matching priority with Direct IPSec Priorities Match Switch set to ENABLE. This
parameter applies only to direct IPv4 IPsec.
SET GTRANSPARA: DIRECTIPSECPRIMATCHSW=ENABLE;
//Adding an IKE security proposal
ADD IKEPROPOSAL: PROPID=10, ENCALG=DES, AUTHALG=MD5, DURATION=86400, REAUTHSW=ON,
REAUTHLT=604800;
//Adding an IPsec proposal
ADD IPSECPROPOSAL: PROPNAME="prop1", ENCAPMODE=TUNNEL, TRANMODE=ESP, ESPAUTHALG=MD5,
ESPENCALG=DES;
//Adding a security parameter template for direct IPv4 IPsec with SeGW Switch set to DISABLE
ADD SECURITYTEMPLATE: SECURITYTEMPLATEID=0, SEGWSWITCH=DISABLE, PROPID=10,
IPSECPROPNAME="prop1", IKEVERSION=IKE_V2, PKEY="******", DPD=PERIODIC, LTCFG=LOCAL;
//Adding a security parameter template for direct IPv6 IPsec with SeGW Switch set to DISABLE
ADD SECURITYTEMPLATE: SECURITYTEMPLATEID=1, SEGWSWITCH=DISABLE, PROPID=10,
IPSECPROPNAME="prop1", IKEVERSION=IKE_V2, PKEY="******", DPD=PERIODIC, LTCFG=LOCAL,
IPROUTE6PREF=20;
//Adding a security host (IPv4) with SeGW Switch set to DISABLE
ADD SECURITYHOST: SECURITYHOSTID=0, SEGWSWITCH=DISABLE, IPVERSION=IPv4,
LOCIKEIPV4="7.7.4.146", SECURITYTEMPLATEID=0;
//Adding a security host (IPv6) with SeGW Switch set to DISABLE
ADD SECURITYHOST: SECURITYHOSTID=1, SEGWSWITCH=DISABLE, IPVERSION=IPv6,
LOCIKEIPV6="2000:0:0:0:0:0:0:1", SECURITYTEMPLATEID=1, VRFIDX=2;
//Adding an endpoint group for the Xn interface

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 71

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

ADD EPGROUP: EPGROUPID=1;

//Adding an SCTP parameter template
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
//Adding an Xn control-plane host (IPv4 used as an example)
ADD SCTPHOST: SCTPHOSTID=1, IPVERSION=IPv4, SIGIP1V4="7.7.42.93", SIGIP1SECSWITCH=DISABLE,
SIGIP2V4="0.0.0.0", SIGIP2SECSWITCH=DISABLE, PN=38422, SIMPLEMODESWITCH=SIMPLE_MODE_OFF,
SCTPTEMPLATEID=0;
//Adding an Xn control-plane host (IPv6 used as an example)
ADD SCTPHOST: SCTPHOSTID=1, VRFIDX=1,IPVERSION=IPv6, SIGIP1V6="2000:0:0:0:0:0:1:1",
SIGIP1SECSWITCH=DISABLE, SIGIP2V6="0::0", SIGIP2SECSWITCH=DISABLE, PN=38422,
SIMPLEMODESWITCH=SIMPLE_MODE_OFF, SCTPTEMPLATEID=0;
//Adding an Xn user-plane host (IPv4 used as an example)
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="7.7.42.93", IPSECSWITCH=ENABLE,
SECHOSTID=0;
//Adding an Xn user-plane host (IPv6 used as an example)
ADD USERPLANEHOST: UPHOSTID=2, VRFIDX=1, IPVERSION=IPv6, LOCIPV6="2000:0:0:0:0:0:1:1",
IPSECSWITCH=ENABLE, SECHOSTID=1;
//Adding the Xn user-plane host to the endpoint group
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;
//Adding the Xn control-plane host to the endpoint group
ADD SCTPHOST2EPGRP: EPGROUPID=1, SCTPHOSTID=1;
//(Optional) Adding a transmission resource group. This command is required only when
GTRANSPARA.TRANSCFGMODE is set to OLD and a dedicated transmission resource group needs to be
specified for the Xn interface.
ADD RSCGRP: CN=0, SRN=1, SN=7, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=0, RU=KBPS;
//(Optional) Adding the Xn-U to the transmission resource group. This command is required only when
GTRANSPARA.TRANSCFGMODE is set to OLD and a dedicated transmission resource group needs to be
specified for the Xn interface.
ADD EP2RSCGRP: ENDPOINTID=1, CN=0, SRN=1, SN=7, SBT=BASE_BOARD, PT=ETH, BEAR=IP, RSCGRPID=0;
//(Optional) Adding an IP transmission resource group. This command is required only when
GTRANSPARA.TRANSCFGMODE is set to NEW and a dedicated IP transmission resource group needs to be
specified for the Xn interface.
ADD IPRSCGRP: IPRSCGRPID=0, PT=ETH, PORTID=0, RSCGRPNO=0, RU=KBPS;
//(Optional) Adding the mapping relationship between the endpoint group and IP transmission resource
group. This command is required only when GTRANSPARA.TRANSCFGMODE is set to NEW and a dedicated
IP transmission resource group needs to be specified for the Xn interface.
ADD EP2IPRSCGRP: MAPID=2, MT=ENDPOINT_GROUP, ENDPOINTID=1, IPRSCGRPID=0;
//Enabling ANR
MOD NRCELLALGOSWITCH: NrCellId=0, AnrSwitch = NR_NR_ANR_SW-1&NR_EUTRAN_ANR_SW-1;
//Adding an Xn MO
ADD GNBCUXN: gNBCuXnId=0, CpEpGroupId=1, UpEpGroupId=1;

Activating Self-Update of Direct IPsec for the Xn Interface

SET GEPMODELPARA: DIRIPSECUPDATESW=ENABLE;

Activating Self-Removal of Direct IPsec for the Xn Interface

//Enabling self-removal of direct IPsec for the Xn interface with the direct IPsec self-removal timer length
set to 10 minutes
SET GEPMODELPARA: DIRIPSECAUTODELSW=ENABLE, DIRIPSECAUTODELTIMER=10;

Configuring a Direct IPsec Blacklist for the Xn Interface

//Adding a direct IPsec blacklist (IPv4 used as an example)
ADD DIRECTIPSECBLACKLIST: DIRECTIPSECBLACKLISTID=0, IPVERSION=IPV4,
SECURITYPEERIPV4="7.7.4.154";

Configuring a Direct IPsec Whitelist for the Xn Interface

//Adding a direct IPsec whitelist (IPv4 used as an example)
ADD DIRECTIPSECWHITELIST: DIRECTIPSECWHITELISTID=0, IPVERSION=IPV4,
SECURITYPEERIPV4="192.168.0.0", MASK="255.255.255.0";

Deactivation Command Examples

//Setting IPSec Auto Configure Switch for First Local IP and IPSec Auto Configure Switch for Second Local IP
in the SCTPHOST MO to DISABLE

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 72

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

MOD SCTPHOST: SCTPHOSTID=1, SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE;

//Setting IPSec Auto Configure Switch in the USERPLANEHOST MO to DISABLE

MOD USERPLANEHOST: UPHOSTID=1, IPSECSWITCH=DISABLE;

6.4.3.3 Using the MAE-Deployment

For detailed operations, see MAE-Deployment-based Feature Configuration.

6.4.4 Activation Verification

Direct IPsec for the Xn-U Interface

Step 1 Run the DSP IKESA command to check the IKE SA negotiation results.

Expected result: The IDs of ACL rules generated during direct IPsec self-setup for
the Xn interface range from 80000 to 84999. If the command output includes an
IKE SA with the rule ID in this range, direct IPsec negotiation between the local
and peer base stations has succeeded, and the state of IKE SA between the base
stations is normal.

Step 2 Run the LST IPSECPOLICY command to obtain Policy Group Name and IPSec
Sequence No. corresponding to the ACL ID of 7164 queried in the previous step.

Step 3 Run the DSP IPSECSA command to display the results of IPsec SA negotiation
based on IPSec Policy Group Name and IPSec Sequence No.

Expected result: The IPsec SA information is displayed, which indicates that direct
IPsec negotiation between the local and peer base stations has succeeded, and the
state of IPsec SA between the base stations is normal.

This procedure uses direct IPsec SA setup for the Xn-U interface as an example. If direct
IPsec is successfully set up for the control plane between the local and the peer gNodeBs,
IPsec SA information about the control plane is also displayed.

----End

Self-Update of Direct IPsec

Observe the Xn interface three minutes after self-update of direct IPsec is enabled.
If an XNAP_PRIVATE_MSG message exits, this function has been successfully
activated.

Self-Removal of Direct IPsec

If ALM-25891 IKE Negotiation Failure is reported, the alarm automatically clears
when the Direct IPsec Automatic Deletion Timer expires (if this timer length is
not 0). Then, run the LST IKEPEER command to view the configurations of the IKE
peer.

Expected result: The peer IP address of the IKE peer is unavailable. This indicates
that this function has taken effect.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 73

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 6 Direct IPsec for Xn Interface

6.4.5 Network Monitoring

None

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 74

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 7 Parameters

7 Parameters

The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.

You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.

FAQ: How do I find the parameters related to a certain feature from

parameter reference?

Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All parameters related to the feature are displayed.

----End

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 75

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 8 Counters

8 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.

You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.

FAQ: How do I find the counters related to a certain feature from

performance counter reference?

Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All counters related to the feature are displayed.

----End

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 76

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 9 Glossary

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 77

(2020-01-20)
5G RAN
NG and Xn Self-Management Feature Parameter
Description 10 Reference Documents

10 Reference Documents

● 3GPP TS 38.412: "NG-RAN; NG signalling transport"

● 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)"
● 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)"
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Transmission Resource Management
● Mobility Management
● IPsec
● Technical Specifications in 3900 & 5900 Series Base Station Product
Documentation

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 78

(2020-01-20)