Security Level:

5900 Base Station Initial Configu

ration Training Slides
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.

Notice

This document provides information about the differences between LTE and 5G base station initial configurations.
For details about initial configuration based on the CME and using MML commands, you can refer to 3900 & 5900 Series Base Station
Initial Configuration Guide in 3900 & 5900 Series Base Station Product Documentation.
Contents

1 gNodeB Device Configuration

2 gNodeB Transport Configuration

3 gNodeB Radio Configuration

gNodeB Equipment Configuration
Function Area Subfunction Area Comparison with LTE
Cabinet, subrack, Cabinet and subrack In the current version, 5G supports BBU5900 and BBU3910, and Subrack Type must be set to BBU5900 or BBU3910.
and BBU data
Boards in the BBU In the current version, 5G supports BBU5900 and BBU3910.
(1) If the baseband processing board is UBBPfw or UBBPg, set the Work Mode to NR to configure UBBP. For a full-width UBBPfw, Slot
No. must be set to 0, 2, or 4 and can be configured only in the BBU5900. UBBPg boards can be configured in both BBU5900 and
BBU3910.
(2) UMPTe/UMPTg is configured as the main control board.
RFU unit and ALD AAU RRU Type must be set to AIRU and RF Unit Working Mode must be set to NO(NR_ONLY). Others are the same as those of LTE.
data
RRU+ALD In the uplink and downlink decoupling scenario, in FDD 8T8R or lower, and in TDD 8T8R or lower, the antenna mode must be set to
RRU, the RRU type must be set to MRRU, the RF unit working mode must be set to NO(NR_ONLY) or LN(LTE_FDD_NR), and others
are the same as those of LTE.
Monitoring unit data FMU Same as LTE
(optional)
TCU Same as LTE
CCU Same as LTE
EMU Same as LTE
User-defined alarms Same as LTE
Power module data Power supply management Same as LTE
(optional)
Time data Time data Same as LTE
gNodeB (TDD) GPS or RGPS reference clock Same as LTE
clock data
IEEE1588 V2 clock source Same as LTE
1PPS+TOD clock Same as LTE
NODE Deployment type & product type (1) Single-RAT: The deployment type must be set to NON-CONCURRENT (non-multimode concurrency). When a BBU5900 is used, the
recommended product type is DBS5900_5G. When a BBU3910 is used, the recommended product type is DBS3900_5G.
(2) Multi-RAT: refers to co-MPT. Set Deployment Type to CONCURRENT (multimode concurrency). If UMPTe is used, set Working Mode
Extension to COMM2. If UMPTg is used, Working Mode Extension can be set to COMM or COMM2. The recommended value is
BTS5900, DBS5900, BTS3900, or DBS3900.
Configuration Script for Site Deployment
LTE
//Setting Working Mode and Product Type (The setting takes effect after the
base station is reset.)
SET NODE: WM=NON-CONCURRENT, PRODUCTTYPE=BTS5900_LTE;
//Adding cabinet, BBU, and BBU boards
ADD CABINET: CN=0, TYPE=VIRTUAL, DESC= "Virtual Cabinet";
ADD SUBRACK: CN=0, SRN=0, TYPE=BBU5900;
ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT, BRDSPEC=UMPTe;
ADD BRD: CN=0, SRN=0, SN=0, BT=UBBP, BBWS=LTE_FDD,
BRDSPEC=UBBPd3;
//Adding RF configurations
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT,
HSRN=0, HSN=0, HPN=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=1, PS=0, RT=AIRU,
RS=LO, RXNUM=4, TXNUM=4;
//Adding the eNodeB application
ADD APP: AID=1, AT=eNodeB, AN="eNodeB";
5G
//Setting Working Mode and Product Type (The setting takes effect after the
base station is reset.)
SET NODE: WM=NON-CONCURRENT, PRODUCTTYPE=DBS5900_5G;
//Adding cabinet, BBU, and BBU boards
ADD CABINET: CN=0, TYPE=VIRTUAL, DESC= "Virtual Cabinet";
ADD SUBRACK: CN=0, SRN=0, TYPE=BBU5900;
ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT, BRDSPEC=UMPTg;
ADD BRD: CN=0, SRN=0, SN=0, BT=UBBP, BBWS=NR,
BRDSPEC=UBBPg3;
Note: The BRDSPEC parameter of the UMPT is used for specification
verification, for example, verification of the number of cells.
//Adding 64T64R eCPRI AAU
ADD RRUCHAIN: RCN=60, TT=CHAIN, BM=COLD, AT=LOCALPORT,
HSRN=0, HSN=0, HPN=3, PROTOCOL=eCPRI;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=60, PS=0, RT=AIRU,
RS=NO, RN= "JINGCI70_TDD_100M", RXNUM=0, TXNUM=0;
//Adding 8T8R CPRI RRU
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT,
HSRN=0, HSN=0, HPN=3, PROTOCOL=CPRI;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=1, PS=0, RT=MRRU,
RS=NO, RXNUM=8, TXNUM=8;
//Adding the gNodeB application
ADD APP: AID=1, AT=gNodeB, AN= "gNodeB", RUNMODE= "INTEGRATED";
Contents

1 gNodeB Device Configuration

2 gNodeB Transmission Configuration

3 gNodeB Radio Configuration

Transmission Configuration Model
 Background: As network traffic volume increases, network transmission scenarios become increasingly complicated. For example, transmission p
orts or boards need to be adjusted to support inter-board functions. The traditional transmission network configuration is complicated and struggl
es to meet the requirement for fast deployment on the live network. Therefore, a new transmission configuration model is introduced to decouple tr
ansmission configurations from physical devices to simplify operations.
 Transmission configuration model: The GTRANSPARA.TRANSCFGMODE parameter specifies which model takes effect.
– If this parameter is set to OLD, the original transmission configuration model is used. The transport objects at the IP layer contain parameters such as the
cabinet number, subrack number, slot number, and port number.
– If this parameter is set to NEW, the new transmission configuration model is used. Unnecessary cabinet, subrack, and slot configurations are removed fro
m the IP layer transmission configuration, which is decoupled from physical devices and reduces transmission configuration parameters.
 The configuration requirements for the transmission configuration model are as follows:
– A co-MPT multimode base station must use the same transmission configuration model for all modes. A separate-MPT multimode base station, which can
be regarded as multiple single-mode base stations, can use the same or different transmission configuration models for different modes.
– If a base station uses IPv4/IPv6 dual stack transmission, IPv4 and IPv6 transmission must use the same configuration model, that is, both use the old mod
el or the new model.
– The new model is recommended for a new single-mode or co-MPT base station with IPv6 transmission.
– In a co-MPT IPv4/IPv6 dual-stack base station, if the NR mode uses IPv6 transmission and the GSM/UMTS/LTE mode uses IPv4 transmission, the followi
ng requirements must be met for the two configuration models. Operators need to consider the transmission model based on network conditions.
 If the new transmission model is used, the old IPv4 transmission model of GSM, UMTS, or LTE needs to be changed to the new transmission model.
The northbound tool must support the new IPv4 model. The old transmission model of the northbound tool must be changed to the new transmission
model.
 If the old transmission model is used, the old IPv4 transmission model of GSM, UMTS, or LTE remains unchanged. However, new VLANs must be pla
nned for IPv6 transmission. These VLANs must be different from the VLANs used for IPv4 transmission.
 Benefits:
– Compared with the old model, the new model decouples upper-layer configuration objects from physical device configurations by adding interface objects
(MO INTERFACE).
– In addition, with the new model, when a transmission link is configured or a transmission board or port is modified, the information such as the cabinet, su
brack, and slot numbers as well as the subboard type only needs to be configured for the physical layer and data link layer.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 8

Differences in Transmission Configuration Models (Modified Parts are
Highlighted in Red Color)
Old model: macro base station New model: macro base station
S1/X2/eX2 S1/X2/eX2

EPGROUP EPGROUP

SCTPHOST USERPLANEHOST SCTPHOST USERPLANEHOST

Application layer Application layer

IPRT DEVIP IPROUTE4 IPADDR4

VRF VRF INTERFACE

IP layer IP layer

ETHPORT ETHPORT LOOPBACK

Physical/link port Physical/link port

Physical board Physical board

Old model: macro base station
1. DEVIP is directly configured
on the physical/link ports.
New model: macro base station
1. The PORTID parameter is added to the MOs of physical and link layer
interfaces.
2. The INTERFACE MO is configured on the physical/data link layer interfaces, and
the loopback interface is added.
3. IPADDR4 is configured on the interface.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 9

Initial Configuration of 5G IPv4 Transport Data (Old Model)
• gNodeBs use the IP over Ethernet transmission mode. Transmission data can be configured only in endpoint mode.
• When configuring a transmission link, set endpoint parameters such as gNodeB control and user planes at the local end as well as S-GW/eNodeB parameters
at the peer end.
• The gNodeB automatically sets up the S1/X2 interface based on the endpoint information.

Function Domain Procedure Differences from LTE

Physical layer Configure an ETHPORT MO. Only IP over Ethernet is supported.
(Optional) It is recommended that VLAN networking be based on the next-hop IP address.
Data link layer 1. Configure a VLANMAP MO with VLAN Priority set to DISABLE(Disable) (recommended). None
2. (Optional) Configure a DSCPMAP MO to set the mappings between DSCPs and VLAN priorities.

1. Configure DEVIP MOs to add OM, service, and signaling IP addresses. 1. Only the endpoint mode is supported.
2. Configure an IPRT MO (for destination IP address-based routing policy) or an SRCIPRT MO (for 2. If rate limitations for base station cascading
source IP address-based routing policy). and common transmission are not required,
3. (Optional) If common transmission or base station cascading is planned, configure an RSCGRP MO do not configure an RSCGRP MO and
with TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and related MOs.
configure an IP2RSCGRP MO. (18B does not involve QoS) 3. S1 self-setup: A gNodeB has only an S1-U
Transport layer 4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. interface, which is automatically set up
5. Configure SCTPHOST MOs. through an eNodeB.
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs. 4. X2 self-setup: The X2 interface is
7. Configure USERPLANEHOST MOs. automatically set up through the U2020.
8. (Optional, required only for manual user-plane peer configuration) Configure USERPLANEPEER MOs. * For details about interface self-setup, see X2
9. Configure EPGROUP MOs. and S1 Self-Management in NSA Networking
10.(Optional) Configure a DIFPRI MO to plan user-defined priorities. Feature Parameter Description.

Maintenance
Configure an OMCH MO. None
channel
DHCP (Optional) If base station cascading is required, configure DHCPSVRIP and DHCPRELAYSWITCH MOs. None
Interface
Configure gNBCUS1 and gNBCUX2 MOs. Interfaces in 5G NSA networking
information

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 10

Initial Configuration of 5G IPv4 Transport Data (New Model)
• gNodeBs use the IP over Ethernet transmission mode. Transmission data can be configured only in endpoint mode.
• When configuring a transmission link, set endpoint parameters such as gNodeB control and user planes at the local end as well as S-GW/eNodeB parameters
at the peer end.
• The gNodeB automatically sets up the S1/X2 interface based on the endpoint information.
Function Domain Procedure Differences from LTE Differences from the Old Model
Global parameter When the new model is recommended for configuring transport data, TRANSCFGMODE in the GTRANSPARA None The parameter TRANSCFGMODE is
MO is set to NEW. added in the GTRANSPARA MO.
Physical layer Configure an ETHPORT MO. Only IP over Ethernet is supported. The configuration of PORTID is
added in the ETHPORT MO.
Data link layer (Optional) It is recommended that VLAN networking be based on the interface. None The interface-based VLAN
1. Configure an INTERFACE MO. Set Interface Type to VLAN(VLAN). configuration is recommended.
2. (Optional) Configure a DSCP2PCPMAP MO to set the mappings between DSCPs and VLAN priorities.
Transport layer 1. Configure IPADDR4 MOs: For adding OM, service, and signaling IP addresses, configure the IPADDR4 1. Only the endpoint mode is 1. The INTERFACE and
MOs on the INTERFACE MO. It is advised to use loopback IP addresses as the signaling and service IP supported. LOOPBACK MOs are added.
addresses in IPsec scenarios, scenarios with the active and standby routes, or scenarios where OM data 2. If rate limitations for base station 2. The DEVIP MO is replaced by the
and service data are isolated. In this case, configure LOOPBACK MOs to add signaling and service IP cascading and common transmission IPADDR4 MO.
addresses. are not required, do not configure an 3. The IPRT MO is replaced by the
2. Configure an IPROUTE4 MO (for destination IP address-based routing policy) or an SRCIPROUTE4 MO IPRSCGRP MO and related MOs. IPROUTE4 MO.
(for source IP address-based routing policy). 3. S1 self-setup: A gNodeB has only an 4. The SRCIPRT MO is replaced by
3. (Optional) If common transmission or base station cascading is planned, configure an IPRSCGRP MO with S1-U interface, which is the SRCIPROUTE4 MO.
TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and configure an automatically set up through an 5. The RSCGRP MO is replaced by
IP2IPRSCGRP MO. (18B does not involve QoS) eNodeB. the IPRSCGRP MO.
4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. 4. X2 self-setup: The X2 interface is 6. The IP2RSCGRP MO is replaced
5. Configure SCTPHOST MOs. automatically set up through the by the IP2IPRSCGRP MO.
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs. U2020.
7. Configure USERPLANEHOST MOs. * For details about interface self-setup,
8. (Optional, required only for manual user-plane peer configuration) Configure USERPLANEPEER MOs. see X2 and S1 Self-Management in NSA
9. Configure EPGROUP MOs. Networking Feature Parameter
10. (Optional) Configure a DIFPRI MO to plan user-defined priorities. Description.

Maintenance channel Configure an OMCH MO. None None

DHCP (Optional) If base station cascading is required, configure DHCPSVRIP and DHCPRELAYSWITCH MOs. None None
Interface information Configure gNBCUS1 and gNBCUX2 MOs. Interfaces in 5G NSA networking None

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 11

Differences Between IPv4 19A and 18B (1/2)
MO Disused in19A New MO in 19A MO in18B Parameter Disused in 19A 19A Change Description
SUBIF ETHPORT MTU This parameter is replaced by INTERFACE.MTU4 in the new model.
Loopback and INTERFACE (The two MOs are shared by IPv4 and IPv6.)
IPITF6 ETHPORT ARPPROXY This parameter is replaced by INTERFACE.ARPPROXY in the new model.
DEVIP IPPATH TRANSCFGMODE This parameter will be deleted in later versions.
IPADDR4 (IPADDR4 for DEVIP and IFIP)
IFIP IPPATH CN This parameter is replaced by IPPATH.PORTID in the new model.
DEVIP6 IPADDR6 IPPATH SRN This parameter is replaced by IPPATH.PORTID in the new model.
IPRT IPROUTE4 IPPATH SN This parameter is replaced by IPPATH.PORTID in the new model.
IPRT6 IPROUTE6 IPPATH PT This parameter is replaced by IPPATH.BPT in the new model.
SRCIPRT SRCIPROUTE4 IPPATH PN This parameter is replaced by IPPATH.PORTID in the new model.
ETHTRK ETHTRUNK
IPPATH RSCGRPID This parameter is replaced by IPPATH.IPRSCGRPID in the new model.
IPPATH SBT This parameter is replaced by IPPATH.PORTID in the new model.
ETHTRKLNK ETHTRUNKLNK
IPPATH JNRSCGRP This parameter is replaced by IPPATH.JNIPRSCGRP in the new model.
BFDSESSION BFD
SCTPLNK CN In the new model, this parameter is configurable but does not take effect.
LR PORTLR
SCTPLNK SRN In the new model, this parameter is configurable but does not take effect.
DSCPMAP DSCP2PCPMAP
SCTPLNK SN In the new model, this parameter is configurable but does not take effect.
PRI2QUE DSCP2QUEMAP
ACL AUTOCFGFLAG This parameter will be deleted in later versions.
ETHOAM3AH ETH3AH
ACLRULE AUTOCFGFLAG This parameter will be deleted in later versions.
CFMMEP CFMLOCALMEP IKEPEER AUTOCFGFLAG This parameter will be deleted in later versions.
LLDPLOCAL LLDP IPSECPOLICY AUTOCFGFLAG This parameter will be deleted in later versions.
PACKETFILTER PACKETFILTERING CFMMA CN This parameter does not take effect in the new model.
IPSECBIND CFMMA SRN This parameter does not take effect in the new model.
IPSECBINDITF (IPSECBINDITF for IPSECBIND and IPSECBIND6)
IPSECBIND6 CFMMA SN This parameter does not take effect in the new model.
LANSWITCHPORT LSWPORT GTRANSPARA MODELSELECT In the new model, the DEVIP and IFIP MOs are no longer controlled.
TUNNEL BACKTUNNEL GTRANSPARA TRANSCFGMODE This parameter will be deleted in later versions.
DOT1X DOT1XAUTH ACL6 AUTOCFGFLAG This parameter will be deleted in later versions.
GPM IPGPM ACLRULE6 AUTOCFGFLAG This parameter will be deleted in later versions.
EP2RSCGRP EP2IPRSCGRP ETHCIPORT MTU This parameter is replaced by INTERFACE.MTU4 in the new model.
IP2RSCGRP ETHCIPORT ARPPROXY This parameter is replaced by INTERFACE.ARPPROXY in the new model.
IP2IPRSCGRP (merged from IP2RSCGRP6 to IP2IPRSCGRP)
IP2RSCGRP6 UDPSESSION CN This parameter will be deleted in later versions.
PPPOELNK PPPOE UDPSESSION SRN This parameter will be deleted in later versions.
PORTIP BRPORTIP UDPSESSION SN This parameter will be deleted in later versions.
IKEPEER6 IKEPEER6 is added to the existing MO IKEPEER.
IPSECPOLICY6 IPSECPOLICY6 is added to the existing MO IPSECPOLICY.
SCTPLNK6 The SCTPLNK6 is incorporated into the existing MO SCTPLNK.
Main transmission differences between 19A and the 18B: A new
IPPATH6 cannot be configured in the new model. IPv6 supports only the End
IPPATH6
Point model. transmission model is added in 19A.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 12

Differences Between IPv4 19A and 18B (2/2)
MO in 18B New Parameter in 19A Parameter Name in19A MO in18B Parameter in 18B 19A Change Description
ETHPORT PORTID Port ID The value SCTP6 (SCTP6 Link)
CPBEARER BEARTYPE
IPPATH TRANSCFGMODE Transmission Configuration Mode is removed from the statement.
IPPATH JNIPRSCGRP Join IP Transmission Resource Group
IPPATH IPRSCGRPID IP Transmission Resource Group ID
IPPATH BPT Bearing Port Type
IPPATH PORTID Port ID
PPPLNK PORTID Port ID
MPGRP PORTID Port ID
SCTPLNK IPVERSION IP Version
SCTPLNK LOCIP6 First Local IPv6 Address
SCTPLNK SECLOCIP6 Second Local IPv6 Address
SCTPLNK PEERIP6 First Peer IPv6 Address
SCTPLNK SECPEERIP6 Second Peer IPv6 Address
IKEPEER IPVERSION IP Version
IKEPEER REMOTEIP6 Remote IPv6 Address
IKEPEER LOCALIP6 Local IPv6 Address
IPSECPOLICY ACLTYPE ACL Type
IKECFG IPSECBINDMODE IPSec Bind Mode
GTRANSPARA MULTICASTIP Multicast IP address
GTRANSPARA TRANSCFGMODE Transmission Configuration Mode
ETHCIPORT PORTID Port ID
SCTPTEMPLATE MAXSCTPPDUSIZE Maximum SCTP PDU Size

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 13

Configuration Differences Between IPv6 Transmission
Configuration Models
ETHPORT

MOs in the new model MOs in the old model

ETHPORT.PORTID

(Optional) LOOPBACK

DSCPMAP
DSCP2PCPMAP

INTERFACE IPITF6

IPADDR6
New model: macro base station
1. The PORTID parameter is added to Old model: macro base station
the MOs of physical and data link IPROUTE6 1. IPITF6 is directly configured on the
layer interfaces. physical/data link layer interface. The
2. The INTERFACE MO is configured cabinet number, subrack number, and
on the physical/data link layer SCTPHOST
slot number need to be configured.
interfaces, and the loopback 2. IPADDR6 is configured on the IPITF6
interface is added. USERPLANEHOST MO.
3. IPADDR6 is configured on the
INTERFACE MO.
EPGROUP MO in the new model

MO in the old model

S1/X2/eX2 MO in the new/old model

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 14

Initial Configuration of 5G IPv6 Transport Data (Old Model)
• The gNodeB supports only Ethernet transmission in IPv6, and only the endpoint configuration mode is supported. It is the same as LTE.
• When adding a transmission link, configure endpoint parameters such as gNodeB control plane and user plane hosts and peers, such as
the peer S-GW/eNodeB.
• gNodeB automatically creates the S1/X2 interface based on the endpoint parameters.

Function Area IPv6 Configuration Model IPv4/IPv6 Dual-Stack Configuration

Global 1. (Optional) Configure the PMTUCFG MO for PMTU detection. The 1. (Optional) PMTUCFG applies only to IPv6 transmission.
parameters default detection mode is PASSIVE (passive mode).

Physical layer 1. Configure the ETHPORT MO. IPv6 and IPv4 transport can share the same ETHPORT MO, or
the ETHPORT MO can be planned separately.

Data link layer 1. (Optional) Configure DSCPMAP and plan user-defined mappings.
2. Configure an IPv6 interface IPITF6. If IPv6 packets without VLAN tags
exist, configure a common interface on the physical interface and set
Interface Type to NORMAL. If VLANs are planned, configure VLAN
subinterfaces and set Interface Type to VLAN.
1. (Optional) DSCPMAP applies to IPv4 and IPv6.
2. Configure IPv4 and IPv6 VLANs. The VLAN ID of IPv6 cannot
be the same as that of IPv4. For the configuration of the IPv4
VLAN, see the initial configuration of the 5G IPv4 transmission
data (old model).

Network layer 1. Configure IPv6 address IPADDR6 and plan O&M, signaling, and user 1. Configure IPv4 and IPv6 addresses.
plane IPv6 addresses. Loopback IP addresses are recommended for O&M 2. Configure IPv4 and IPv6 routes.
and service isolation scenarios and IPsec scenarios. Otherwise, interface
IP addresses can be used. When configuring a loopback IP address,
ensure that the prefix length is 128.
2. Configure static IPv6 route IPROUTE6 and plan IPv6 routes for O&M,
signaling, and user data.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 15

Initial Configuration of 5G IPv6 Transport Data (Old Model) (Continued)
Function Area IPv6 Configuration Model
Transport layer 1. (Optional) Configure SCTPTEMPLATE and plan a
user-defined template.
2. Configure an SCTPHOST MO and configure the
first local IPv6 address.
3. (Optional) Configure the SCTPPEER MO when the
SCTP peer is manually configured.
4. Configure the USERPLANEHOST MO to
configure the local IPv6 address.
5. (Optional, required when the user-plane peer is
manually configured) Configure
USERPLANEPEER and configure the peer IPv6
address.
6. Configure the EPGROUP MO.
7. (Optional) Configure DIFPRI and plan user-defined
priorities.
Maintenance channel Configure the OMCH MO, set the bearer type to IPV6,
and configure the local and peer IPv6 addresses.
Interface information Configure gNBCUS1 and gNBCUX2.
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential
IPv4/IPv6 Dual Stack Configuration
1. (Optional) SCTPTEMPLATE applies to IPv4 and IPv6.
2. Configure an SCTP host for both IPv4 and IPv6 addresses.
3. (Optional) Configure SCTPPEER MOs for IPv4 and IPv6 addresses.
4. Configure the USERPLANEHOST MOs for IPv4 and IPv6 addresses.
5. (Optional) Configure the USERPLANEPEER MOs for IPv4 and IPv6
addresses.
6. Configure the EPGROUP MO. If the peer device is configured with the
IPv4&IPv6 dual stack, the IP version priority parameter must be set to the IP
protocol version used by the interface link, and interface self-setup is
supported. The default value is IPv4. If this parameter is set to IPv4, the
signaling plane or user plane link in the EPGROUP MO is used to establish
an IPv4 link with the peer device. If this parameter is set to IPv6, the
signaling plane or user plane link in the EPGROUP MO is used to establish
an IPv6 link with the peer device. Only one IP protocol can be selected for
link establishment. IPv4 and IPv6 backup is not supported. This parameter is
invalid when the local address or the IP address of the peer device is a single
stack address.
7. (Optional) DIFPRI applies to IPv6 and IPv4 transmission.
The OMCH dual-stack configuration is not supported.
N/A
Page 16
Initial Configuration of 5G IPv6 Transport Data (New Model)
• The gNodeB using IPv6 supports only Ethernet transmission. Only the endpoint configuration mode is supported. It is the same as LTE.
• When adding a transmission link, configure endpoint parameters such as gNodeB control plane and user plane hosts and peers, such as the S-
GW/eNodeB.
• gNodeB automatically creates the S1/X2 interface based on the endpoint parameters.
Function Area IPv6 Configuration Model
Global parameters 1. The new transmission configuration model is recommended: Set
TRANSCFGMODE in the GTRANSPARA MO to NEW.
2. (Optional) Configure the PMTUCFG MO. The default detection mode is
PASSIVE (passive mode).
Physical layer 1. Configure the ETHPORT MO.
Data link layer 1. (Optional) Configuring the LOOPBACK MO.
2. Configure the INTERFACE MO. If IPv6 packets without VLAN tags exist,
configure a common interface on the physical interface and set Interface
Type to NORMAL. If VLANs are planned, configure VLAN subinterfaces and
set Interface Type to VLAN. Enable IPv6.
3. (Optional) Configure DSCP2PCPMAP and plan customized mappings.
Network layer 1. Configure IPv6 address IPADDR6 and plan O&M, signaling, and user
plane IPv6 addresses. Loopback IP addresses are recommended for O&M
and service isolation scenarios and IPsec scenarios. Otherwise, interface IP
addresses can be used. When configuring a loopback IP address, ensure
that the prefix length is 128.
2. Configure static IPv6 route IPROUTE6 and plan IPv6 routes for O&M,
signaling, and user data.
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential
IPv4&IPv6 Dual Stack Configuration
1. The transmission model applies to IPv4 and IPv6 transmission.
2. PMTUCFG applies only to IPv6 transmission.
IPv6 and IPv4 transmission can share the same ETHPORT MO. The
ETHPORT MO can also be planned separately for IPv6 and IPv4
transmission.
1. (Optional) Configure loopback interfaces for IPv4 and IPv6 addresses.
2. Configure INTERFACE MOs for IPv4 and IPv6.
• When IPv6 and IPv4 transport share the same physical port,
common interfaces apply to IPv4 and IPv6 transmission, and IPv6
Enable Switch must be set to ENABLE (Enable).
• VLAN IDs must be configured in interface VLAN mode for IPv4 and
IPv6 transmission. The VLAN IDs for IPv4 and IPv6 transmission
can be the same or different. It is recommended that IPv6 and IPv4
use different VLANs for VLAN isolation.
3. (Optional) Configure DSCP2PCPMAP for IPv4 and IPv6 transmission.
1. Configure IPv4 and IPv6 addresses. When IPv6 and IPv4 transport
share the same physical port, common interface IP addresses are
configured on the same physical port.
2. Configure IPv4 and IPv6 routes.
Page 17
Initial Configuration of 5G IPv6 Transport Data (New Model) (Continued)
Function Area IPv6 Configuration Model
Transport layer 1. (Optional) Configure SCTPTEMPLATE
and plan a user-defined template.
2. Configure the SCTPHOST MO.
3. (Optional) Configure the SCTPPEER MO
when the SCTP peer is manually
configured.
4. Configure the USERPLANEHOST MO.
5. (Optional) Configure the
USERPLANEPEER MO when the user-
plane peer is manually configured.
6. Configure the EPGROUP MO.
7. (Optional) Configure DIFPRI and plan
user-defined priorities.
Maintenance Configure the OMCH MO, set the bearer
channel type to IPV6, and configure the local IPv6
address and peer IPv6 address.
Interface Configure gNBCUS1 and Gnbcux2.
information Add a self-setup parameter.
HUAWEI TECHNOLOGIES CO., LTD.
IPv4&IPv6 Dual-Stack Configuration
1. (Optional) SCTPTEMPLATE applies to IPv4 and IPv6.
2. Configure an SCTPHOST MO for both IPv4 and IPv6 addresses.
3. (Optional) Configure SCTPPEER MOs to add IPv4 and IPv6 addresses.
4. Configure the USERPLANEHOST MOs to add IPv4 and IPv6 addresses.
5. (Optional) Configure the USERPLANEPEER MOs to add IPv4 and IPv6 addresses.
6. Configure the EPGROUP MO. If the peer device is configured with the IPv4&IPv6 dual
stack, the IP version priority parameter must be set to the IP protocol version used by
the interface link. In this case, the interface can be set up automatically. The default
value is IPv4. If this parameter is set to IPv4, the signaling plane or user plane link in
the EPGROUP MO is used to establish an IPv4 link with the peer device. If this
parameter is set to IPv6, the signaling plane or user plane link in the EPGROUP MO is
used to establish an IPv6 link with the peer device. Only one IP protocol can be
selected for link establishment. IPv4 and IPv6 backup is not supported. This
parameter is invalid when the local address or the IP address of the peer device is a
single stack address.
7. (Optional) DIFPRI applies to IPv6 and IPv4 transmission.
The OMCH dual-stack configuration is not supported.
N/A
HUAWEI Confidential Page 18
Transmission Configuration in Dual-MPT Scenarios
Networking 1: A single trunk is enabled on each board Networking 2: Each board of the gNodeB is enabled with  Application scenario: Dual-MPT applies to gNodeBs. Wh
of the base station to be dual-homed to routers. a single Ethernet port. The two Ethernet ports are dual-
homed to routers. en one main control board cannot meet the service bandwi
MME/ S-GW/ MME/ S-GW/
1588v2 AMF UPF U2020 1588v2 AMF UPF U2020 dth and reliability requirements, two main control boards ca
n be configured for a gNodeB.
 Networking supported by dual-MPT:
1. Networking 1: A single trunk is enabled on each bo
1588v2 NG/S1-C NG/S1_U 1588v2 NG/S1-C NG/S1_U ard of the base station to be dual-homed to routers.
OMCH OMCH
Each UMPT of the gNodeB is configured with two Ether
net ports, which are connected to two routers RT 1 and
RT 2, respectively. The two Ethernet ports on the same
UMPT form an Ethernet trunk. The two routers are con
nected to the gNodeB through MC-LAG. The Ethernet t
runks on the gNodeB work in load sharing mode.
Backhaul Backhaul
2. Networking 2: Each board of the gNodeB is enable
X2 X2
d with a single Ethernet port. The two Ethernet port
s are dual-homed to routers.
eNodeB eNodeB Each of the two UMPT boards in the gNodeB is configu
red with one Ethernet port, which is connected to two r
Xn RT1 1 RT 2 Xn RT 1 RT 2 outers RT 1 and RT 2.
MC-LAG IP4 IP2  Dual-MPT configuration restrictions:
gNodeB IP4 MC-LAG gNodeB
1. Only IPv4 transmission is supported.
IP2
2. Only the endpoint configuration mode is supported.
IP1 3. Only source IP address-based routing is supported.
gNodeB IP3 gNodeB
4. The two main control boards must be of the same type.
trunk trunk IP3 IP1
UMPTe Slave UMPTe Master UMPTe Slave UMPTe Master

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 19

Initial Configuration of 5G IPv4 Transport Data in Dual-MPT Scenarios (Old Model)

Function Domain Configuration Model Description

Physical layer Configure MPT and ETHPORT MOs. 1. Add two UMPT boards with the type of UMPT.
2. Each UMPT must be configured with Ethernet ports.
Data link layer 1. (Optional) Networking 1: Configure ETHTRK and ETHTRKLNK MOs. 1. Networking 1: Configure different VLANs for the two Ethernet trunks that
2. (Optional) SingleVLAN for VLAN connect the gNodeB to the routers.
a. Configure a VLANMAP MO with Set VLAN Priority set to DISABLE (recommended). 2. Networking 2: Configure different VLANs for the two Ethernet ports that connect
b. (Optional) Configure a DSCPMAP MO to set the mappings between DSCPs and VLAN the gNodeB to the routers.
priorities.
Transport Layer 1. Configure DEVIP MOs to add OM, service, and signaling IP addresses. 1. Each main control board must be configured with at least one IP address.
2. Configure an SRCIPRT MO for source IP address-based routing policies. 2. The source IP address-based routing policy is used.
3. (Optional) If common transmission or base station cascading is planned, configure an RSCGRP 3. Two user-plane hosts are configured, and the local IP addresses of the two user-
MO with TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic plane hosts are configured on the two main control boards.
and configure an IP2RSCGRP MO. 4. Configure an SCTP host. The two local IP addresses of the SCTP host are
4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. configured on the two main control boards.
5. Configure an SCTPHOST MO. 5. It is recommended that SCTP load sharing be disabled
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs. (GTRANSPARA.CPLBSW is set to DISABLE) when two main control boards
7. Configure USERPLANEHOST MOs. are configured for a gNodeB.
8. (Optional, required only for manual user-plane peer configuration) Configure 6. The MAXASSOCRETR parameter in the SCTP parameter template is set to 20.
USERPLANEPEER MOs. 7. Configure endpoint groups, configure two user-plane hosts for each endpoint
9. Configure EPGROUP MOs. group, and enable GTP-U static detection for the endpoint groups.
10. (Optional) Configure a DIFPRI MO to plan user-defined priorities. 8. Enable GTP-U static detection with STATICCHKMODE set to EPSTATICCHK.
11. Configure GTPU and GEPMODELPARA MOs to enable GTP-U static detection.
OMCH Configure OMCH MOs. Add active and standby OMCHs. The local IP addresses of the active and standby
OMCHs are configured on two main control boards. The U2020 remote HA system is
not supported.
DHCP (Optional) If base station cascading is required, configure DHCPSVRIP and
DHCPRELAYSWITCH MOs.
Interface Configure gNBCUS1 and gNBCUX2 MOs in NSA networking.
information Configure gNBCUNG and gNBCUXN MOs in SA networking.
Clock 1. Set the backup mode of the reference clock source with TASM.BKPMODE set to CLKSRCBRDCFG.
2. If the GPS clock source is used, configure a GPS MO for both main control boards.
3. If the 1588v2 clock source is used, configure one IP clock link (IPCLKLINK MO) on the active main control board.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 20

Initial Configuration of 5G IPv4 Transport Data in Dual-MPT Scenarios (New Model)
Function Domain Configuration Model Description
Global parameters New transmission configuration model is recommended: Set TRANSCFGMODE in the GTRANSPARA MO to NEW.
Physical layer Configure MPT and ETHPORT MOs. 1. Add two UMPT boards with the type of UMPT.
2. Each UMPT must be configured with Ethernet ports.
Data link layer 1. (Optional) Networking 1: Configure ETHTRUNK and ETHTRUNKLNK MOs. 1. Networking 1: Configure different VLANs for the two Ethernet trunks that connect the
2. (Optional) VLAN interface recommended for VLAN planning gNodeB to the routers.
a. Configure an INTERFACE MO with Interface Type set to VLAN. 2. Networking 2: Configure different VLANs for the two Ethernet ports that connect the
b. 2. (Optional) Configure a DSCP2PCPMAP MO to set the mappings between DSCPs and VLAN gNodeB to the routers.
priorities.

Transport Layer 1. Configure IPADDR4 MOs on INTERFACE MOs to add the O&M, signaling, and service IP
addresses.
2. Configure an SRCIPROUTE4 MO for the source IP address-based routing policy.
3. (Optional) If base station cascading is required, configure an IPRSCGRP MO with TXBW, TXCBS,
and TXEBS set to appropriate values to limit the rates of passerby traffic and configure an
IP2IPRSCGRP MO.
4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template.
5. Configure an SCTPHOST MO.
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs.
7. Configure USERPLANEHOST MOs.
8. (Optional, required only for manual user-plane peer configuration) Configure USERPLANEPEER
MOs.
9. Configure EPGROUP MOs.
10. (Optional) Configure a DIFPRI MO to plan user-defined priorities.
11. Configure GTPU and GEPMODELPARA MOs to enable GTP-U static detection.
1. Each main control board must be configured with at least one IP address.
2. The source IP address-based routing policy is used.
3. Two user-plane hosts are configured, and the local IP addresses of the two user-plane
hosts are configured on the two main control boards.
4. Configure an SCTP host. The two local IP addresses of the SCTP host are on the two
main control boards.
5. It is recommended that SCTP load sharing be disabled (GTRANSPARA.CPLBSW is set
to DISABLE) when two main control boards are configured for a gNodeB.
6. The MAXASSOCRETR parameter in the SCTP parameter template is set to 20.
7. Configure endpoint groups, configure two user-plane hosts for each endpoint group, and
enable GTP-U static detection for the endpoint groups.
8. Enable GTP-U static detection with STATICCHKMODE set to EPSTATICCHK.

OMCH Configure OMCH MOs. Add active and standby OMCHs. The local IP addresses of the active and standby OMCHs
are configured on two main control boards. The U2020 remote HA system is not supported.
DHCP (Optional) If base station cascading is required, configure DHCPSVRIP and DHCPRELAYSWITCH
MOs.

Interface Configure gNBCUS1 and gNBCUX2 MOs in NSA networking.

information Configure gNBCUNG and gNBCUXN MOs in SA networking.

Clock 1. Set the backup mode of the reference clock source with TASM.BKPMODE set to CLKSRCBRDCFG.
2. If the GPS clock source is used, configure a GPS MO for both main control boards.
3. If the 1588v2 clock source is used, configure one IP clock link (IPCLKLINK MO) on the active main control board.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 21

 Contents

1 gNodeB Device Configuration

2 gNodeB Transmission Configuration

3 gNodeB Radio Configuration

2
 Differences Between the NSA/SA Configuration Script o
n the RAT Side

 Top-Layer Nodes
 Transport
 Cell

3
 gNodeB Service Configuration - 5G RAT Service Configuration
[CU-DU Integrated Deployment]
DBS5900
MO
NE

Inclusion Inclusion
MO Reference MO
APP
gNodeBFunction
AT = gNodeB

1. NE: indicates an NE node.

2. APP: indicates the application software. For gNodeB APP, set Application Type to gNodeB.
3. gNodeBFunction: indicates the top-layer node in the gNodeB function domain. Before configuring the
gNodeBFunction MO, you need to configure the gNodeB APP and reference the gNodeB APP.

4
 Configuration Script for Site Deployment
NSA
//Adding the gNodeB application
ADD APP: AID=1, AT=gNodeB, AN= "gNodeB", RUNMODE=
"INTEGRATED";
//Adding the gNodeB function
ADD GNODEBFUNCTION: gNodeBFunctionName="NR",
gNBIdLength =22, gNodeBId=9527, ApplicationReference=1;
//Configuring operator information
ADD GNBOPERATOR: OperatorId=0, OperatorName= "5G", Mcc=
"460", Mnc= "02", OperatorType= PRIMARY_OPERATOR,
NrNetworkingOption =NSA;
ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=33;
5
SA
//Adding the gNodeB application
ADD APP: AID=1, AT=gNodeB, AN= "gNodeB", RUNMODE=
"INTEGRATED";
//Adding the gNodeB function
ADD GNODEBFUNCTION: gNodeBFunctionName="NR",
gNBIdLength =22, gNodeBId=9527, ApplicationReference=1;
//Configuring operator information
ADD GNBOPERATOR: OperatorId=0, OperatorName= "5G", Mcc=
"460", Mnc= "02", OperatorType= PRIMARY_OPERATOR,
NrNetworkingOption =SA;
ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=33;
 Differences Between the NSA/SA Configuration Script o
n the RAT Side

 Top-Layer Nodes
 Transport (NSA)
 Cell

6
 gNodeB Service Configuration: MO Examples for CU-DU Inte
grated Deployment
gNodeB

NE
BTS5900

MO
gNodeBFunction

Inclusion

MO
gNBCUX2 MO
gNBCUS1

1. In CU-DU integrated deployment, each BTS5900 NE corresponds to a complete gNodeB.

2. In CU-DU integrated deployment, there are X2 and S1 interfaces, whereas the F1 interface is not
implemented.

7
 gNodeB Service Configuration - X2 Interface
MO
gNodeBFunction

Inclusion

MO MO
gNBCUX2 gNBX2SonConfig

Reference

MO
EPGroup

Inclusion

MO MO MO
UserPlaneHost SCTPPeer SCTPHost

1. The X2-C interface is supported.

2. The gNBCUX2 MO is used to configure the X2 interface and references the EPGROUP MO in the BTSNode
MO. The EPGROUP MO consists of USERPLANEHOST, SCTPHOST, and SCTPPEER (optional).
3. The gNBX2SonConfig MO is used to configure X2 self-setup. When X2 self-configuration is enabled, the peer
SCTP information does not need to be configured. The system uses the U2020 to implement X2 self-
configuration.
8
 gNodeB Service Configuration - S1 Interface

MO
gNodeBFunction

Inclusion

MO
gNBCUS1

Reference

MO
EPGroup

Inclusion

MO
UserPlaneHost

1. The S1-U interface is supported whereas the S1-C interface (LTE) is not supported.
2. The gNBCUS1 MO is used to configure the S1 interface. It also references the EPGROUP MO on the
BTSNode. The EPGROUP MO includes USERPLANEHOST.

9
 Differences in the NSA/SA Configuration Script on the R
AT Side

 Top-Layer Nodes
 Transport (SA)
 Cell

0
 gNodeB Service Configuration: MO Examples for CU-DU Int
egrated Deployment
gNodeB

NE
BTS5900

MO
gNodeBFunction

Inclusion

MO
gNBCUNG MO
gNBCUXN

1. In CU-DU integrated deployment, each BTS5900 NE corresponds to a complete gNodeB.

2. The Xn and NG interfaces exist in CU-DU integrated deployment.

1
 gNodeB Service Configuration - Xn Interface

MO
gNodeBFunction

Inclusion

MO
gNBCUXn

Reference

MO
EPGroup

Inclusion

MO MO MO
UserPlaneHost SCTPPeer SCTPHost

1. The gNBCUX2 MO is used to configure the X2 interface and references the EPGROUP MO on the
BTSNode. The EPGROUP MO consists of USERPLANEHOST, SCTPHOST, and SCTPPEER (optional).

2
 gNodeB Service Configuration - Ng Interface

MO
gNodeBFunction

Inclusion

MO
gNBCUNG

Reference

MO
EPGroup

Inclusion
MO MO MO
UserPlaneHost SCTPPeer SCTPHost

1. The gNBCUX2 MO is used to configure the X2 interface and references the EPGROUP MO on the
BTSNode. The EPGROUP MO consists of USERPLANEHOST, SCTPHOST, and SCTPPEER (optional).

3
 Configuration Script for Site Deployment

NSA SA
ADD GNBCUS1: gNBCuS1Id=0, UpEpGroupId=0; ADD GNBCUNG: gNBCuNgId=0, CpEpGroupId=0,
ADD GNBCUX2: gNBCuX2Id=0, UpEpGroupId=0, UpEpGroupId=0;
CpEpGroupId=0; ADD GNBCUXN: gNBCuXnId=0, CpEpGroupId=0,
UpEpGroupId=0;

4
 Differences in the NSA/SA Configuration Script on the RA
T Side

 Top-Layer Nodes
 Transport
 Cell

5
 gNodeB Service Configuration-Cell MO Model
NE
BTS5900
MO MO
NRDUCell Association NRCell

Service

MO
NRDUCellTrp

Inclusion

Reference
MO MO
NRDUCellCoverage SectorEqm

1. NRCell: indicates a logical cell in the gNodeB CU function domain. Parameters related to the RRC function and control-plane RRM algorithm are
configured and managed based on this MO or derived MOs. Each 5G logical cell corresponds to an NRCell object instance.
2. NRDUCell: indicates a cell resource object in the gNodeB DU function domain. Parameters related to the physical layer, channel function, and
baseband RRM algorithm are configured and managed based on this MO or its derived MOs. Each 5G logical cell corresponds to an NRDUCell
object instance. Their association is created by configuring the CellId on the NRCell MO. Each NRDUCell object must belong to a certain gNBDU
object in the CU-DU Split deployment.
3. NRDUCellTrp: indicates a sending and receiving point (corresponding to an independent physical cell). Each NRDUCellTrp object instance
provides resource services for an NRDUCell object. mTnR, beam, and transmit power are managed based on this MO configuration.
NRDUCellTrp is equivalent to LTE cell sector equipment.
4. NRDUCellCoverage: indicates cell coverage, and designates a radio frequency device that provides coverage for a cell (implemented by
referencing a SectorEqm resource object). Each NRDUCellTrp includes resource of at least one NRDUCellCoverage instance.

6
 gNodeB Service Configuration-Common Cell Instance

MO MO
NRDUCell Association NRCell

Service

MO
NRDUCellTrp

Inclusion gNodeB Cell

MO
NRDUCellCoverage
Common cell
Reference
1. One NRCell MO is associated with one
MO NRDUCell MO by setting the CellId.
SectorEqm 2. One NRDUCell MO is only served by one
NRDUCellTrp MO.
3. One NRDUCellTrp MO includes only one
NRDUCellCoverage MO.

7
 gNodeB Service Configuration-Uplink and Downlink Dec
oupling Cell Instance
SUL TDD

MO MO MO
NRDUCell-2 Association NRDUCell-1 Association NRCell

Service gNodeB Cell

Service

MO MO
NRDUCellTrp-2 NRDUCellTrp-1
gNodeB Cell
Inclusion Inclusion UL/DL decoupling cells
1. One NRCell MO is associated with one NRDUCell instance
MO MO
NRDUCellCoverage-2 NRDUCellCoverage-1 (NRDUCell-1) by setting the CellId.
2. NRDUCell-1 is associated with one NRDUCell instance
Reference Reference (NRDUCell-2), which provides SUL resources for NRDUCell-1.
3. One NRDUCell MO is served by only one NRDUCellTrp MO.
MO MO 4. One NRDUCellTrp MO includes only one
SectorEqm-2 SectorEqm-1
NRDUCellCoverage MO.

8
 gNodeB Service Configuration - Hyper Cell Instance

MO MO
NRDUCell Association NRCell

service

MO MO MO
NRDUCellTrp-3 NRDUCellTrp-2 NRDUCellTrp-1
gNodeB Cell
Inclusion Inclusion Inclusion
HyperCell cell
MO MO MO
NRDUCellCoverage-3 NRDUCellCoverage-2 NRDUCellCoverage-1 1. One NRCell is associated with one
NRDUCell through CellId.
Reference Reference Reference 2. One NRDUCell is served by multiple
NRDUCellTrp.
MO MO MO
SectorEqm-3 SectorEqm-2 SectorEqm-1
3. One NRDUCellTrp contains only one
NRDUCellCoverage.

9
 gNodeB Service Configuration - LampSite Cell Instance

MO MO
NRDUCell Association NRCell 1 3
½ RF combination
service 2 4
¾ RF combination
MO MO
NRDUCellTrp-2 NRDUCellTrp-1 gNodeB Cell
Inclusion Inclusion
LampSite cell
MO MO
NRDUCellCoverage-4 NRDUCellCoverage-2 1. One NRCell is associated with one
NRDUCell through CellId.
MO MO
NRDUCellCoverage-3 NRDUCellCoverage-1 2. One NRDUCell is served by multiple
Reference Reference Reference
NRDUCellTrp and corresponds to
Reference
multiple baseband combination nodes.
MO MO MO MO 3. Each NRDUCellTrp has multiple
SectorEqm-4 SectorEqm-3 SectorEqm-2 SectorEqm-1 NRDUCellCoverage and corresponds
to multiple RF headends.

0
 gNodeB Cell Maintenance-Management Operations (Acti
vate/Deactivate/Block/Unblock)
Operation MML Command

Activate a cell ACT NRCELL

Activate a DU cell (deactivated by default) ACT NRDUCELL

Deactivate a cell DEA NRCELL

Deactivate a DU cell DEA NRDUCELL

Block a cell BLK NRDUCELL

Unblock a cell UBL NRDUCELL

Display the status of a cell DSP NRCELL

Display the status of a DU cell DSP NRDUCELL

Note:
1. All management commands are consistent and are executed on the CU, regardless of whether the cell is a common cell or an uplink
and downlink decoupling cell, and regardless of whether CU-DU integrated deployment or CU-DU split deployment is used.
2. Cells can only be blocked immediately.
3. After a cell is activated, run the DSP NRCELL command to query the cell availability state. If the cell availability state is normal, the cell
is activated normally.
4. Run the DSP NRCELL command to query the status of all cells for the same vendor.

1
 gNodeB Cell Maintenance-NR Cell Information Query

Parameter Name Description

NR Cell ID Indicates the ID of an NR cell, which uniquely identifies the NR cell within a gNodeB.
NR DU Cell ID Indicates the ID of an NR DU cell, which uniquely identifies the NR DU cell within a DU.
Indicates the overall availability status of a 5G cell, including the NR cell status and NR DU cell
Cell Available State
status.
NR Cell State Indicates the state of an NR cell.
NR DU Cell State Indicates the state of an NR DU cell.
Indicates the reason for the latest state change of an NR cell, which can be an activation
Cell Latest State Change Reason
success, a deactivation success, or a setup failure of the NR cell.
Latest Time When Cell Become Available Indicates the latest time when an NR cell becomes available.
Latest Operation Make Cell Available Indicates the latest operation that makes an NR cell available.
Latest Time When Cell Become Unavailable Indicates the latest time when an NR cell becomes unavailable.
Latest Operation Make Local Cell
Indicates the latest operation that makes an NR cell unavailable.
Unavailable
Indicates the information about the cell control node. The value of this parameter is in the
format of "Cabinet number-Subrack number-Slot number", which indicates the cabinet number,
Cell Control Node Information
subrack number, and slot number of the board where the control-plane functions of the NR cell
are deployed.

2
 gNodeB Cell Maintenance-DU Cell Information Query
Parameter Name
NR DU Cell ID
NR Cell ID
NR DU Cell State
DU Cell Latest State Change Reason
Latest Time When DU Cell Become Available
Latest Operation Make DU Cell Available
Latest Time When DU Cell Become Unavailable
Latest Operation Make DU Cell Unavailable
3
Description
Indicates the ID of an NR DU cell, which uniquely identifies the cell within a DU.
Indicates the ID of an NR cell, which uniquely identifies the NR cell within a
gNodeB.
The value of this parameter is NULL if an NR local cell is not bound to any NR
cells.
Indicates the state of an NR DU cell instance.
Indicates the reason for the latest state change of an NR DU cell, which can be
an activation success or a setup failure of the NR DU cell.
Indicates the latest time when an NR DU cell becomes available.
Indicates the latest operation that makes an NR DU cell available.
Indicates the latest time when an NR DU cell becomes unavailable.
Indicates the latest operation that makes an NR DU cell unavailable.
 Site Deployment Configuration Script (Cell)
NSA SA
//Adding a cell Same as that for NSA
ADD NRDUCELL:NrDuCellId=0,DuCellNname="CELL0",FrequencyBand=N77,
UlBandwidth=CELL_BW_N100, DlBandwidth=CELL_BW_N100, DuplexMode=CELL_FDD;
PhysicalCellId =0, CELLID=0, UlEarfcnConfigInd=CONFIG, UlEarfcn=640000, DlEarfcn=640000,
SsbDescMethod=SSB_DESC_TYPE_GSCN, SsbFreqPos=6400, SlotAssignment = 4_1_DDDSU,
SlotStructure = SS5, SubcarrierSpacing= 30KHZ, WorkMode=UL_DL, CellRadius =1000,
TrackingAreaId=0;

ADD NRCELL:NRCellId=0,CellNname="CELL0",FrequencyBand=n3,CELLID=0,
DuplexMode=CELL_FDD;
 
ADD NRDuCellTrp: NrDuCellTrpId=0, NrDuCellId=0, TxRxMode= 64T64R, BasebandEqmId=0,
CpriCompression= 2_COMPRESSION,MaxTransmitPower =4, BbResMutualAidSw =OFF;

ADD NRDUCellCoverage: NrDuCellCoverageId=0,NrDuCellTrpId=0, SectorEqmId=1;

None ADD NRDUCELLOP:
NRDuCellId=0,
OperatorId=0;
//Activating the cell Same as that for NSA
ACT NRCELL: NRCellId=0;

All configurations are performed on the CU: SSB frequency, ARFCN, and downlink central frequency.
For details on FDD configuration, see the training course for FDD differences. For details on mmWave
configuration, see the training course for high- and low-frequency differences.
4
 Site Deployment Configuration Script (Neighboring Cell)
NSA SA

ADD NREXTERNALNCELL: Mcc= "460", Mnc= "02", gNBId=236, CellId=0, CellName= "22", PhysicalCellId Same as that for NSA
=236, DlNarfcn =40230,
SsbDescMethod=SSB_DESC_TYPE_GSCN, SsbFreqPos= 40230, Tac= 33;
ADD NRCELLRELATION: NRCellId=0, Mcc= "460", Mnc= "02", gNodeBId=236, CellId=0, NCellType Same as that for NSA
=INTRA_FREQ;

5
 SSB Frequency-Domain Position
In the NR system, the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH form an SSB.
Each SSB consists of 240 consecutive subcarriers. A UE searches for cells based on received PSS and SSS signals and obtains
necessary information from the received broadcast system messages. Then, the UE selects the most appropriate cell to camp on
using the received information.
The SSB frequency-domain position is not configured for SUL cells, but must be configured for TDD and FDD cells.
Use either of the following description methods to configure the SSB frequency-domain position:
NARFCN:
If NRDUCell.SsbDescMethod is set to SSB_DESC_TYPE_NARFCN, NRDUCell.SsbFreqPos indicates the NARFCN
corresponding to the SSB center frequency.
Global synchronization channel number (GSCN):
If NRDUCell.SsbDescMethod is set to SSB_DESC_TYPE_GSCN, NRDUCell.SsbFreqPos indicates the GSCN corresponding
to the SSB center frequency.
In SA only or SA&NSA networking, set NRDUCell.SsbDescMethod to SSB_DESC_TYPE_GSCN. In NSA networking, set
NRDUCell.SsbDescMethod to SSB_DESC_TYPE_GSCN or SSB_DESC_TYPE_NARFCN.
Whatever any description method is specified, the SSB must be within the carrier bandwidth range of a cell. If the SSB is beyond
the range, the cell cannot be set up or work properly. Unless otherwise specified or requested, the SSB frequency domain
location should be located near the center NARFCN of the cell.

6
 Description of SSB Frequencies
The following table lists the mapping between GSCN and frequency. For details, see section 5.4.3.1 in
3GPP TS 38.104.

Frequency Range SSB Frequency Position Calculation

GSCN Range
(SSREF) Formula for GSCN
N x 1200 kHz + M x 50 kHz,
0–3000 MHz 3N + (M-3)/2 2–7498
N = 1:2499, M ϵ {1,3,5}
3000 MHz + N x 1.44 MHz
3000–24250 MHz 7499 + N 7499–22255
N = 0:14756
24250.08 MHz + N x 17.28 MHz
24250–100000 MHz 22256 + N 22256–26639
N = 0:4383

In the frequency range of 0-3000 MHz, the GSCN must be an integer multiple of 3.
That is, the value of M in the preceding table is always 3.

7
 Thank You
www.huawei.com

Copyright © 2019 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the future financial
and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and
developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for
reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.
 Issues
1. SSB frequency, absolute frequency number, and downlink central frequency
Answer: The SSB frequency and the absolute frequency number are the names of the same object.
2. What are the principles for planning the SSB frequencies?
Answer: Contact the network planning personnel to obtain the frequency planning principles.
3. Give an example of SSB frequency and the absolute frequency number.
Answer: See the value range in the following table.
4. Why the NRCELL does not need to be configured with downlink frequencies?
Answer: The downlink frequency is originally used for the NCellType check of NRCELLRELATION. Currently,
NCellType is deleted. Therefore, the downlink frequency is not required.

GSCN Absolute Frequency Number Downlink Central Frequency

Definition SSB frequency-domain position
The channel number is obtained by
calculating the frequency of the SSB.
Requirements This parameter can be set to any
value, which always complies with
3GPP TS 38.104.
Value Range 2-26639
SSB frequency-domain position The start and end locations of the
The frequency number is obtained by cell frequency is determined based
calculating the frequency of the SSB. on the downlink central frequency
and cell bandwidth.
The configuration cannot be performed
randomly. The configuration must comply
with 3GPP TS 38104.
151600-160600, 361000-376000, 499200-
537999, 620000-680000, 693334-733333,
2016667-2104165, 2229167-2279165

9
 gNodeB Service Configuration - Cell SectorEqm Configu
ration (Traditional Antenna)
MO MO MO MO
NRDuCellTrp NRDuCellTrp-1 NRDuCellTrp-2 NRDuCellTrp-3
Inclusion Inclusion Inclusion Inclusion

MO MO MO MO
NRDUCellCoverage NRDUCellCoverage-1 NRDUCellCoverage-2 NRDUCellCoverage-3
Reference Reference
Reference Reference
Inclusion MO Inclusion Association
MO Association SectorEqmAntPortRef
SectorEqmAntPortRef SectorEqm
SectorEqm
MO MO
Reference
Reference RRU RRU
Inclusion MO Include
MO SectorAntPortRef
SectorAntPortRef Association Sector Association
Sector

Example of single-carrier/multi-carrier not sharing antennas Example of multi-carrier sharing antennas

Sector: A sector is a radio area covered by a set of RF antennas with the same coverage.
SectorEqm: The cell uses the antenna equipment of the sector and supports 2T2R/4T4R/8T8R.
RRU: The RRU provides ports for communication with a baseband board and processes UL and DL RF signals.
SectorEqmAntPortRef: RF antennas with TX and RX attributes
SectorAntPortRef: RF antennas

Generally, a gNodeB is configured with three sectors. The upper left is a single cell with a single sector while the upper right is multi cells
with a single sector.

0
 gNodeB Service Configuration - Cell SectorEqm Configu
ration (AAU)
MO MO MO MO
NRDuCellTrp NRDuCellTrp-1 NRDuCellTrp-2 NRDuCellTrp-3
Inclusion Inclusion Inclusion Inclusion

MO MO MO MO
NRDUCellCoverage NRDUCellCoverage NRDUCellCoverage NRDUCellCoverage
Reference Reference Reference Reference

MO Association MO MO Association MO
SectorEqm RRU SectorEqm RRU

Reference Reference

MO MO
Sector Sector

Low-frequency Massive MIMO High-frequency multi-carrier sharing antennas

One SectorEqm refers to one sector and one RRU (AAU).
Sector: Sectors covered by beams do not require antennas.
SectorEqm: indicates the RRU information used by the cell beam. 2T2R/4T4R/8T8R/32T32R/64T64R is supported. The cell beam shape,
azimuth, and splitting information need to be configured.
RRU: The RRU provides ports for communication with a baseband board and processes UL and DL RF signals. The type is set to AIRU.
Generally, a gNodeB is configured with three sectors. The upper left is a single cell with a single sector while the upper right is multi cells
with a single sector.
1
 Identical X2 Configuration for CI Interconnection and Tra
nsport Network Scenarios
An X2-C interface is an information exchange channel defined by 3GPP technical specifications for wireless
services. An X2-C interface can be set up over the bearer network or a CI interconnection cable.
In a co-BBU separate-MPT scenario, CI communication is implemented through the BBU backplane, and no
special configuration is required.
 

In an inter-BBU CI interconnection scenario, X2 configurations are the same as those configured over the
transport network.
The CI interconnection cable is mainly used in scenarios with a high requirement for the latency.

2
 Differences in Transmission Configuration Models (Modified Parts are
Highlighted in Red Color)
Old model: macro base station New model: macro base station RANCU_E (RAT) S1-C/X2-C/F1-C S1-U/X2-U/F1-U
S1/X2/eX2 S1/X2/eX2
RANCU_E (COM) EPGROUP
EPGROUP EPGROUP

SCTPHOST USERPLANEHOST SCTPHOST USERPLANEHOST SCTPHOST USERPLANEHOST

IPADDR4

INTERFACE

LOOPBACK

Application layer Application layer

RANCU_P

IPRT DEVIP IPROUTE4 IPADDR4

IP2TRPSUNIT IPROUTE4 IPADDR4

VRF VRF INTERFACE

VRF INTERFACE
IP layer IP layer IP layer

ETHPORT ETHPORT LOOPBACK LOOPBACK VETHPORT

Physical/link port Physical/link port Physical/link port

Physical board Physical board Logical board TRPSUNIT

New model: macro base station

Old model: macro base station 1. The PORTID parameter is added to the MOs of physical and data link layer interfaces. RANCU:
1. DEVIP is directly configured 2. INTERFACE is configured on the physical/data link layer interface, and the loopback 1. VETHPORT Interface does not have
on the physical/link ports. interface is added. cabinet, subrack, and slot parameters.
3 3. IPADDR4 is configured on INTERFACE.
 X2 Self-Setup over U2020
Currently, L-NR X2 self-setup can be performed only after obtaining IP addresses of the gNodeB through the U2020. The detailed
procedure is as follows.

1. The source eNodeB finds the corresponding gNodeB ID based on the B1 measurement report of NR and sends a Configuration
Transfer message to the U2020.
2. The U2020 finds the corresponding gNodeB based on the gNodeB ID sent by the eNodeB and obtains the IP address of the gNodeB.
3. The U2020 sends the IP address of the gNodeB to the eNodeB through the Configuration Transfer message.
4. After obtaining the IP address of the gNodeB, the eNodeB initiates X2 self-setup.

4
 S1-U Self-Setup
S1-U self-setup between the gNodeB and S-GW is implemented only in the Option 3X architecture and is not involved in the Option 3
architecture.

UE eNodeB gNodeB MME S-GW

X2 Set Up procedure

1.SgNB Addition Request (carrying the S1-U address on the S-GW side)

2.SgNB Addition Request ACK (carrying the S1-U address on the gNodeB side)

3.UE Access NR Procedure

4.eRAB Modification Indication (carrying the S1-U address on the gNodeB side)

6.eRAB Modification Confirm 5.Bearer Modification

Notifying the S-GW of
the S1-U address of the
7.DL data bearer on the RAN side.

1. The eNodeB sends the gNodeB an SgNB Addition Request message, which carries the S1-U address information on the S-GW side. Then, the gNodeB can send UL data
based on the information.
2. The gNodeB sends the eNodeB an SgNB Addition Request ACK message, which carries the S1-U address on the gNodeB side.
3. The UE initiates random access to the gNodeB.
4. The eNodeB sends the MME an eRAB Modification Indication message, which carries the S1-U address information on the gNodeB side. Then, the S-GW can send DL
data based on the information.
5. The MME exchanges messages with the SG-W to notify the S-GW of the corresponding S1-U address information on the RAN side.
6. The MME sends an eRAB Modification Confirm message to the eNodeB.
7. The S-GW sends DL data to the gNodeB.

5
 Site Deployment Configuration Script: UL and DL Decou
pling

Description 5G
Add an NR Cell. ADD NRCELL:NRCellId=0,CellNname="CELL0",FrequencyBand=N77,CELLID=0, DuplexMode=CELL_TDD, Gscn
=640000;
Add a DU cell for ADD NRDUCELL: NrDuCellId=0, NrDuCellName= "0", FrequencyBand=N77, UlBandwidth=CELL_BW_100M,
the NR cell. DlBandwidth=CELL_BW_100M, DuplexMode=CELL_TDD, PhysicalCellId =0, CELLID=0,
UlEarfcnConfigInd=CONFIG, UlEarfcn=640000, DlEarfcn=640000, Gscn =640000, TrackingAreaId=0;
Add an SUL cell ADD NRDUCELL: NrDuCellId=1, NrDuCellName= "0", FrequencyBand=N3, UlBandwidth=CELL_BW_20M,
for the NR cell. DuplexMode=CELL_SUL, UlEarfcnConfigInd=CONFIG, UlEarfcn=351000, TrackingAreaId=0;
Bind the DU cell ADD NRDUCELLSUL: NrDuCellId=0, SulNrDuCellId=1;
with the SUL cell.