Security Level:

5900 Base Station Initial

Configuration Training Slides
www.huawei.com

2018-06

HUAWEI TECHNOLOGIES CO., LTD.

 Contents

1 gNodeB Device Configuration

2 gNodeB Transport Configuration

3 gNodeB Radio Configuration

3 Huawei Confidential
 gNodeB Device Configuration
Function Domain Subfunction Area Differences from LTE
Cabinets and subracks In SRAN15.0, 5G supports only BBU5900, and Subrack Type must be set to BBU5900.

Cabinet, subrack, and In SRAN15.0, 5G supports only BBU5900:

BBU data 1. If the baseband processing board is UBBPfw, set Work Mode to NR when adding a BBP. For a full-width
Boards in the BBU
UBBPfw, Slot No. must be set to 0, 2, or 4.
2. If the main control board is UMPTe, set Board Type to UMPT.

AAU Set RF Unit Working Standard to NO(NR_ONLY). Other parameter values are the same as those for LTE.
RF unit and ALD data RRUs must be configured only in uplink & downlink decoupling scenarios. RF Unit Working Mode must be
RRU+ALD
set to LN(LTE_FDD_NR). Other parameter values are the same as those for LTE.
FMU Same as LTE
TCU Same as LTE
(Optional) Monitoring
CCU Same as LTE
unit data
EMU Same as LTE
User-defined alarm Same as LTE
(Optional) Power
Power supply management Same as LTE
module data
Time data Time data Same as LTE
GPS or RGPS reference clock Same as LTE
gNodeB (TDD) clock
IEEE 1588V2 clock reference Same as LTE
data
1PPS+TOD clock Same as LTE
18B: Single RAT. Set Working Mode to NON-CONCURRENT(Non-ConCurrent) and Product Type to
DBS5900_5G.
Node Deployment type and product type
19A: Multi RATs, referring to the co-MPT mode. Set Working Mode to CONCURRENT(ConCurrent) and
Product Type to BTS5900 or DBS5900. Huawei Confidential
4
 Configuration Scripts
LTE
//Set the working mode and product type. The setting takes effect
after the base station is reset.
SET NODE: WM=NON-CONCURRENT,
PRODUCTTYPE=BTS5900_LTE;
//Add a cabinet, a BBU, and 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;
//Add RF unit-related 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;
//Add eNodeB application.
ADD APP: AID=1, AT=eNodeB, AN="eNodeB";
5 Huawei Confidential
5G
//Set the working mode and product type. The setting takes effect after the
base station is reset.
SET NODE: WM=NON-CONCURRENT, PRODUCTTYPE=BTS5900_5G;
//Add a cabinet, a BBU, and 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=NR,
BRDSPEC=UBBPfw1;
//Add a 64T64R C-band AAU.
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=NO, RXNUM=0, TXNUM=0;
//Add a 4T4R RRU for uplink & downlink decoupling.
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT,
HSRN=0, HSN=0, HPN=3;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=1, PS=0,
RT=MRRU, RS=LN, RXNUM=4, TXNUM=4;
//Add gNodeB application.
ADD APP: AID=1, AT=gNodeB, AN="gNodeB",
RUNMODE="INTEGRATED";
 Contents

1 gNodeB Device Configuration

2 gNodeB Transport Configuration

3 gNodeB Radio Configuration

6 Huawei Confidential
 Transmission Configuration Model
• Background: As network traffic volume increases, network transmission scenarios become increasingly complicated. For example,
transmission ports or boards need to be adjusted to support inter-board functions. The traditional transmission network configuration is
complicated and struggles to meet the requirement for fast deployment on the live network. Therefore, a new transmission configuration
model is introduced to decouple transmission configurations from physical devices to simplify operations.
• Transmission configuration model: The transmission configuration model can be the new or old model, depending on the
GTRANSPARA.TRANSCFGMODE parameter setting.
– If this parameter is set to OLD, the old model is used: In this model, information about the cabinet, subrack, and slot is included.
Transmission configurations and physical devices are bound together. IPv4 and IPv6 MOs above the IP layer are independent of each
other.
– If this parameter is set to NEW, the new model is used: In this model, transmission configurations are decoupled from physical devices.
That is, unnecessary cabinet, subrack, and slot configurations are excluded from transmission configurations, and IPv4 and IPv6 MOs
above the IP layer are combined. This facilitates the introduction of new transmission functions and reduces transmission configuration
parameters.
• Value:
– Compared with the old model, the new model introduces an INTERFACE MO to the data link layer to isolate the upper layers from the
physical layer and decouple transmission configurations from physical devices.
– In the new model, device information such as cabinet, subrack, slot, and sub-board needs to be configured only for the physical layer
or data link layer but not for other layers when transmission links need to be configured or transmission boards or ports need to be
adjusted.

7 Huawei Confidential
 Differences Between New and Old Models (Changes Are in Red)
Old model – macro base stations New model – macro base stations
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 interface
Physical interface/Link interface Physical interface/Link interface /Link interface

Physical board Physical board Logical board TRPSUNIT

New model – macro base stations:

Old model – macro base stations: 1. The PORTID parameter is added to the MOs on the physical/link interface. RANCU:
The DEVIP is directly configured on 2. The INTERFACE is configured on the physical/link interface and the No parameter of the cabinet, subrack, or slot on
LOOPBACK is added. VETHPORT
8 the physical/link interface. 3. The IPADDR4 is configured on INTERFACE. Huawei Confidential
 Initial Configuration of 5G 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 source IP
2. If rate limitations for base station cascading and
address-based routing policy).
common transmission are not required, do not
3. (Optional) If common transmission or base station cascading is planned, configure an RSCGRP MO with
configure an RSCGRP MO and related MOs.
TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and configure an
3. S1 self-setup: A gNodeB has only an S1-U
IP2RSCGRP MO. (18B does not involve QoS)
interface, which is automatically set up through
Transport layer 4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template.
an eNodeB.
5. Configure SCTPHOST MOs.
4. X2 self-setup: The X2 interface is automatically
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs.
set up through the U2020.
7. Configure USERPLANEHOST MOs.
* For details about interface self-setup, see X2 and
8. (Optional, required only for manual user-plane peer configuration) Configure USERPLANEPEER MOs.
S1 Self-Management in NSA Networking Feature
9. Configure EPGROUP MOs.
Parameter Description.
10.(Optional) Configure a DIFPRI MO to plan user-defined priorities.
Maintenance
Configure an OMCH MO. None
channel
DHCP (Optional) If base station cascading is planned, configure DHCPSVRIP and DHCPRELAYSWITCH MOs. None
Interface information Configure gNBCUS1 and gNBCUX2 MOs. Interfaces in 5G NSA networking

9 Huawei Confidential
 Initial Configuration of 5G 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 MO None The parameter TRANSCFGMODE
is set to NEW. is 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 MOs 1. Only the endpoint mode is supported. 1. The INTERFACE and
on the INTERFACE MO. It is advised to use loopback IP addresses as the signaling and service IP addresses 2. If rate limitations for base station LOOPBACK MOs are added.
in IPSec scenarios, scenarios with the active and standby routes, or scenarios where OM data and service data cascading and common transmission 2. The DEVIP MO is replaced by
are isolated. In this case, configure LOOPBACK MOs to add signaling and service IP addresses. are not required, do not configure an the IPADDR4 MO.
2. Configure an IPROUTE4 MO (for destination IP address-based routing policy) or an SRCIPROUTE4 MO (for IPRSCGRP MO and related MOs. 3. The IPRT MO is replaced by the
source IP address-based routing policy). 3. S1 self-setup: A gNodeB has only an IPROUTE4 MO.
3. (Optional) If common transmission or base station cascading is planned, configure an IPRSCGRP MO with S1-U interface, which is automatically 4. The SRCIPRT MO is replaced by
TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and configure an set up through an eNodeB. the SRCIPROUTE4 MO.
IP2IPRSCGRP MO. (18B does not involve QoS) 4. X2 self-setup: The X2 interface is 5. The RSCGRP MO is replaced by
4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. automatically set up through the U2020. the IPRSCGRP MO.
5. Configure SCTPHOST MOs. * For details about interface self-setup, see 6. The IP2RSCGRP MO is replaced
6. (Optional, required only for manual SCTP peer configuration) Configure SCTPPEER MOs. X2 and S1 Self-Management in NSA by the IP2IPRSCGRP MO.
7. Configure USERPLANEHOST MOs. Networking Feature Parameter Description.
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.
Maintenance channel Configure an OMCH MO. None None
DHCP (Optional) If base station cascading is planned, configure DHCPSVRIP and DHCPRELAYSWITCH MOs. None None
Interface information Configure gNBCUS1 and gNBCUX2 MOs. Interfaces in 5G NSA networking None

10 Huawei Confidential
 Initial Configuration of RANCU_P Transport Data
• The RANCU_P uses the IP over Ethernet transmission mode. It only supports the new transmission model.

Function Domain Procedure Differences from Macro Base Stations

Physical layer 1. Configure a TRPSUNIT MO. 1. The added TRPSUNIT MO is equal to a
2. Configure a VETHPORT MO. physical board in the macro base station.
2. The VETHPORT MO is a virtual Ethernet port
corresponding to the ETHPORT MO.

Data link layer (Optional) It is recommended that VLAN networking be based on the interface. The interface-based VLAN configuration is
1. Configure an INTERFACE MO. Set Interface Type to VLAN(VLAN). 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 and interface IP addresses, configure the IPADDR4 MOs on the 1. The source IP address-based routing policy is
INTERFACE MO. It is advised to use loopback IP addresses as the IP addresses of the DNS server in F1 self-setup not supported.
scenarios. In this case, configure LOOPBACK MOs to add IP addresses.
2. The dynamic OSPF route is supported.
2. Configure a static route: Configure an IPROUTE4 MO (for destination IP address-based routing policy). A static
route is required for the OMCH.
3. (Optional) Configure an OSPF dynamic route. The dynamic route can be used on service interfaces:
① (Optional) Configure a BFD parameter: Configure a BFDPARA MO.
② (Optional) Configure an OSPF authentication policy: Configure an OSPFAUTH MO.
③ Configure an OSPF progress: Configure an OSPF MO.
④ Configure an OSPF area: Configure an OSPFAREA MO.
⑤ Configure an OSPF interface: Configure an OSPFIF MO.
⑥ (Optional) Configure basic access control rules: Configure an ACL MO with ACLRULEBAS.
⑦ (Optional) Configure an OSPF GR helper: Configure an OSPFGRHLP MO.
⑧ (Optional) Configure an OSPF GR restarter: Configure an OSPFGRRST MO.
4. (Optional) Configure a DIFPRI MO to plan user-defined priorities.
5. Configure the mapping between the service IP and TRPSUNIT: Configure an IP2TRPSUNIT MO.

RANCU_P Configure an OMCH MO. The active and standby OM channels are not
maintenance channel supported.

DNS server (Optional) Configure a DNSERVER MO for planning the F1 self-setup. The DNSERVER MO is added on the RANCU side.

11 Huawei Confidential
 Initial Configuration of RANCU_GNB Transport Data
• The RANCU_GNB uses the IP over Ethernet transmission mode. It only supports the new transmission model.
• 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 Macro Base Stations

Transport layer 1. Configure LOOPBACK MOs. Only the endpoint mode is supported.
2. Configure an INTERFACE MO with Interface Type set to NORMAL(Normal).
3. Configure IPADDR4 MOs on the INTERFACE MO to add OM, signaling, and service
IP addresses.
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.

RANCU_GNB Configure an OMCH MO. The active and standby OM channels are not
maintenance channel supported.

Interface information Configure gNBCUS1 and gNBCUX2 MOs. Interfaces in 5G NSA networking

12 Huawei Confidential
 X2 Self-Setup over the U2020
The X2 interface between a gNodeB and an eNodeB can be automatically set up only after the U2020 obtains the gNodeB IP address. The
detailed procedure is as follows:

1. The source eNodeB finds the corresponding gNodeB ID based on the event B1 measurement report about 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 a Configuration Transfer message.
4. After obtaining the gNodeB IP address, the eNodeB initiates X2 self-setup.

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

UE eNodeB gNodeB MME SGW

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. Bear Modification

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

1. The eNodeB sends an SgNB Addition Request message to the gNodeB. The message carries the S1-U address information on the S-GW side. The gNodeB can send uplink data based on
the information.
2. The gNodeB sends an SgNB Addition Request ACK message to the eNodeB. The message carries the S1-U address on the gNodeB side.
3. The procedure for the UE to access the gNodeB is performed.
4. The eNodeB sends an eRAB Modification Indication message to the MME. The message carries the S1-U address information on the gNodeB side. The S-GW can send downlink data
based on the information.
5. The MME exchanges messages with the S-GW to notify the S-GW of the S1-U address information corresponding to the bearer on the RAN side.
6. The MME sends an eRAB Modification Confirm message to the eNodeB.
7. The S-GW sends downlink data to the gNodeB.

14 Huawei Confidential
 Contents

1 gNodeB Device Configuration

2 gNodeB Transport Configuration

3 gNodeB Radio Configuration

15 Huawei Confidential
 Differences Between 4G/5G Initial Configuration
Scripts
 Top-Layer Nodes
 Transport
 Cell

16 Huawei Confidential
 gNodeB Service Configuration-5G RAT Service Configuration
[CU&DU Integrated Deployment]
DBS5900 NE

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. gNBCULogicNode: indicates the top-layer node in the gNodeB CU function domain.

17 Huawei Confidential
gNodeB Service Configuration-5G RAT Service Configuration [CU&DU
Split Deployment]
DBS5900 NE RANCU_GNB:
MO MO
NE NE

Inclusion Inclusion Inclusion Inclusion

MO MO
Reference MO Reference MO
APP APP
DFU gNodeBFunction
AT = gNodeB AT = gNodeB
Inclusion
Inclusion

MO Reference
MO
gNBDU DFUAgent

Reference

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. gNBDU: indicates the gNBDU MO, which is configured in the gNodeBFuntion MO on the RANCU_GNB.
5. DFUAgent: indicates the DFUAgent MO, which is automatically configured by the platform after the gNBDU MO is configured.
6. DFU: indicates the DFU MO, which is configured on the DBS5900 NE. The DFU MO is associated with the DFUAgent MO by setting
18 the NetworkID parameter. Huawei Confidential
 Configuration Scripts
LTE 5G
//Add eNodeB application. //Add gNodeB application.
ADD APP: AID=1, AT=eNodeB, AN="eNodeB"; ADD APP: AID=1, AT=gNodeB, AN=“gNodeB", RUNMODE="INTEGRATED";

//Add a gNodeB function.

ADD GNODEBFUNCTION: gNodeBFunctionName="NR", gNBId= 9527,
gNBIdLength =22, ApplicationReference=1;
//Add an eNodeB function.
ADD ENODEBFUNCTION: eNodeBFunctionName="LTE",
ADD GNBDU: gNBDuIndex=1, gNBDuId=9527, gNBDuName= "DU",
ApplicationRef=1, eNodeBId=9527;
ResetMode=NORMALRESET, Op="huawei", Pwd="111111"; //The
configuration is required for the CU-DU Split deployment but not for macro
base stations.
//Configure operator information.
//Configure operator information. ADD GNBOPERATOR: OperatorId=0, OperatorName="5G", Mcc="460",
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="CnOP", Mnc="02";
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="02"; ADD GNBTRACKINGAREA: TrackingAreaId=0, Tac=33;
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33; //In NSA networking, TACs do not need to be planned. It is recommended
that TAC be set to 0.

19 Huawei Confidential
 Differences Between 4G/5G Initial Configuration
Scripts
 Top-Layer Nodes
 Transport
 Cell

20 Huawei Confidential
 gNodeB Service Configuration-CU&DU Integrated Deployment Model
Instantiation
gNodeB

NE
BTS5900
MO
gNodeBFunction

Inclusion
Inclusion

MO Reference MO MO MO MO MO
NRDuCell NRCell gNBCUX2 gNBCUS1 gNBDUX2 gNBDUS1

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

2. In CU&DU integrated deployment, there are the X2 and S1 interfaces but no F1 interfaces.

21 Huawei Confidential
gNodeB Service Configuration-CU&DU Split Deployment Model Instantiation
gNodeB

NE NE NE
BTS5900 RANCU_GNB BTS5900
MO MO MO
gNodeBFunction gNodeBFunction gNodeBFunction

Inclusion Inclusion Inclusion

MO Reference MO MO Inclusion MO
NRDuCell NRCell NRCell NRDuCell

MO MO MO MO MO MO
MO MO MO
gNBDUF1 gNBDUX2 gNBDUS1 gNBDUF1 gNBDUX2 gNBDUS1
gNBCUX2 gNBCUS1 gNBCUF1

1. In CU&DU split deployment, each gNodeB corresponds to a RANCU_GNB and one or multiple BTS5900 NEs.
2. In CU&DU split deployment, the CU supports the F1 interface, X2 interface, and S1 interface.
3. In CU&DU split deployment, the DU supports the F1 interface, X2 interface, and optional S1 interface (required
only when the PDCP function is configured on the BTS5900 node in low latency services)

22 Huawei Confidential
 gNodeB Service Configuration-X2 Interface
MO MO
gNBDULogicNode gNodeBFunction

Inclusion Inclusion

MO MO MO
gNBDUX2 gNBCUX2 gNBX2SonConfig

Reference Reference

MO MO
EPGroup EPGroup

Inclusion Inclusion

MO MO MO MO
UserPlaneHost UserPlaneHost SCTPPeer SCTPHost
1. The X2-C interface is supported.
2. The gNBCUX2 MO is used to configure the X2 interface. The gNBCUX2 MO references the EPGroup MO of the BTSNode MO. The
EPGroup MO consists of the UserPlaneHost MO (local user-plane configuration), SCTPHost MO (local SCTP configuration), and optional
SCTPPeer MO (peer SCTP configuration).
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.
4. The gNBCULogicNode MO contains the gNBDUX2 MO, which is used to configure the X2 interface. The gNBDUX2 MO references the
EPGroup MO of the BTSNode MO. The EPGroup MO consists of the UserPlaneHost MO (local user-plane configuration). The DU X2 only
has the user plane but no control plane, so the SON is not included.

23 Huawei Confidential
 gNodeB Service Configuration-S1 Interface
MO
gNodeBFunction

Inclusion

MO
gNBCUS1

Reference

MO
EPGroup

Inclusion

MO
UserPlaneHost

1. The S1-U interface is supported but the S1-C interface (belonging to LTE) is not supported.
2. The gNBCUS1 MO is used to configure the S1 interface. The gNBCUS1 MO references the EPGroup MO of
the BTSNode MO. The EPGroup MO includes the UserPlaneHost MO (local user-plane configuration).

24 Huawei Confidential
gNodeB Service Configuration-F1 Interface
MO MO
gNodeBFunction gNodeBFunction

Inclusion Inclusion

MO MO
gNBDUF1 gNBCUF1

Reference Reference

MO MO
EPGroup EPGroup

Inclusion Inclusion

MO MO MO MO MO MO
UserPlaneHost SCTPPeer SCTPHost UserPlaneHost SCTPPeer SCTPHost

1. Both the CU and the DU support the F1-C interface and the F1-U interface.
2. The CU contains the gNBCUF1 MO, which is used to configure the F1 interface. The gNBCUF1 MO references the EPGroup MO of the
BTSNode MO. The EPGroup MO consists of the UserPlaneHost MO (local user-plane configuration), SCTPHost MO (local SCTP
configuration), and SCTPPeer MO (peer SCTP configuration).
3. The DU contains the gNBDUF1 MO, which is used to configure the F1 interface. The gNBDUF1 MO references the EPGroup MO of the
BTSNode MO. The EPGroup MO consists of the UserPlaneHost MO (local user-plane configuration), SCTPHost MO (local SCTP
configuration), and SCTPPeer MO (peer SCTP configuration).

25 Huawei Confidential
 Initial Configuration Scripts
LTE 5G
ADD GNBCUS1: gNBCuS1Id=0, UpEpGroupId=0;
ADD GNBCUX2: gNBCuX2Id=0, UpEpGroupId=0, CpEpGroupId=0;

ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG,
CpEpGroupId=0, UpEpGroupId=0;
ADD X2: X1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG,
CpEpGroupId=0, UpEpGroupId=0;
ADD GNBCUF1: gNBF1Id=0, UpEpGroupId=0, CpEpGroupId=0;
ADD GNBDUX2: gNBDuX2Id=0, UpEpGroupId=0; //The command is
automatically generated in the CU-DU integrated deployment.
ADD GNBDUF1: gNBF1Id=0, UpEpGroupId=0, CpEpGroupId=0,
gNBDuIndex=0; //The command is automatically generated in the CU-
DU integrated deployment.

26 Huawei Confidential
 Differences Between 4G/5G Initial Configuration
Scripts
 Top-Layer Nodes
 Transport
 Cell

27 Huawei Confidential
gNodeB Service Configuration-Cell MO Model
NE NE
BTS5900 RANCU_GNB
MO MO MO MO MO
NRDUCell Association NRCell gNBDU Belonging to
NRDUCell Reference NRCell

Service Service

MO MO
NRDUCellTrp NRDUCellTrp

Inclusion Inclusion

Reference Reference
MO MO MO MO
NRDUCellCoverage SectorEqm 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.
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.

28 Huawei Confidential
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.

29 Huawei Confidential
gNodeB Service Configuration-Uplink and Downlink Decoupling 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
MO MO
NRDUCellCoverage-2 NRDUCellCoverage-1 1. One NRCell MO is associated with one NRDUCell instance
(NRDUCell-1) by setting the CellId.
Reference Reference 2. NRDUCell-1 is associated with one NRDUCell instance
(NRDUCell-2), which provides SUL resources for NRDUCell-1.
MO MO
SectorEqm-2 SectorEqm-1
3. One NRDUCell MO is served by only one NRDUCellTrp MO.
4. One NRDUCellTrp MO includes only one
NRDUCellCoverage MO.

30 Huawei Confidential
 gNodeB Service Configuration-Cell SectorEqm Configuration (Common 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

MO Inclusion Association
MO Inclusion Association SectorEqmAntPortRef
SectorEqmAntPortRef SectorEqm
SectorEqm
MO
Reference MO Reference
RRU
RRU Inclusion
MO Inclusion MO
SectorAntPortRef SectorAntPortRef Association
Sector Sector
Association

Example of single-carrier/multi-carrier non-co-antenna Example of multi-carrier co-antenna

Sector: A sector is a radio area covered by a set of RF antennas with the same coverage.
SectorEqm: indicates the sector antenna equipment used by a cell and supports 2T2R/4T4R/8T8R.
RRU: An RRU provides ports for sending and receiving baseband and RF signals and processes uplink and downlink RF signals.

SectorEqmAntPortRef: indicates RF antennas that can transmit or receive signals.

SectorAntPortRef: indicates RF antennas.

Generally, a gNodeB is configured with three sectors, the upper left is single-sector single-cell, and the upper right is single-sector multi-cell.

31 Huawei Confidential
 gNodeB Service Configuration-Cell SectorEqm
Configuration (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-band massive MIMO High-band multi-carrier co-antenna

One SectorEqm MO references one sector and one RRU (AAU).
Sector: Antennas are not required for sectors covered by beams.
SectorEqm: indicates the RRU used by the beam of a cell. 2T2R/4T4R/8T8R/32T32R/64T64R is supported. The cell beam shape, azimuth, and splitting information
need to be configured.
RRU: An RRU provides ports for sending and receiving baseband and RF signals and processes uplink and downlink RF signals. Set the RRU type to AIRU.
Generally, a gNodeB is configured with three sectors, the upper left is single-sector single-cell, and the upper right is single-sector multi-cell.

32 Huawei Confidential
 gNodeB Cell Maintenance-Management Operations
(Activate/Deactivate/Block/Unblock)
Operation MML Command

Activate a cell ACT NRCELL

Activate a DU cell ACT NRDUCELL

Deactivate a cell DEA NRCELL

Deactivate a DU cell DEA NRDUCELL

Block a cell BLK NRCELL

Unblock a cell UBL NRCELL

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.

33 Huawei Confidential
 gNodeB Cell Maintenance-NR Cell Information Query

Parameter Name Description

NR Cell ID
NR Local Cell ID
Cell Available State
NR Cell State
Local Cell State
Cell Latest State Change Reason
Latest Time When Cell Become Available
Latest Operation Make Cell Available
Latest Time When Cell Become Unavailable
Latest Operation Make Local Cell Unavailable
Cell Control Node Information
Indicates the ID of an NR cell, which uniquely identifies the NR cell within a gNodeB.
Indicates the ID of an NR local cell, which uniquely identifies the NR local cell within a DU.
Indicates the overall availability status of a 5G cell, including the NR cell status and local cell status.
Indicates the state of an NR cell.
Indicates the state of an NR local cell.
Indicates the reason for the latest state change of an NR cell, which can be an activation success, a
deactivation success, or a setup failure of the NR cell.
Indicates the latest time when an NR cell becomes available.
Indicates the latest operation that makes an NR cell available.
Indicates the latest time when an NR cell becomes unavailable.
Indicates the latest operation that makes an NR cell 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, subrack
number, and slot number of the board where the control-plane functions of the NR cell are deployed.

34 Huawei Confidential
 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
35
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.
Huawei Confidential
 Initial Configuration Scripts
LTE 5G
ADD CELL: LOCALCELLID=0,
CELLNAME="CELL0", FREQBAND=41,
//Add cells.
ULEARFCNCFGIND=NOT_CFG,
ADD NRDUCELL: NrDuCellId=0,DuCellNname="CELL0", FrequencyBand=n3,
DLEARFCN=40340,
UlBandwidth=CELL_BW_N100, DlBandwidth=CELL_BW_N100,
ULBANDWIDTH=CELL_BW_N100,
DuplexMode=CELL_FDD;
DLBANDWIDTH=CELL_BW_N100, CELLID=0,
PhysicalCellId=0, CELLID=0, gNBDuIndex=1, UlEarfcnConfigInd=CONFIG,
PHYCELLID=0, FDDTDDIND=CELL_TDD,
UlEarfcn=331000, DlEarfcn=350000, SlotAssignment=4_1_DDDSU,
SUBFRAMEASSIGNMENT=SA2,
SlotStructure=SS5,SubcarrierSpacing=30KHZ, WorkMode=UL_DL, CellRadius=1000;
SPECIALSUBFRAMEPATTERNS=SSP7,
EUCELLSTANDBYMODE=ACTIVE,
ADD NRCELL: NRCellId=0, CellNname="CELL0", FrequencyBand=n3,CELLID=0,
ROOTSEQUENCEIDX=0,
DuplexMode=CELL_FDD, DlEarfcn=350000, TrackingAreaId=0;
CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,
EMERGENCYAREAIDCFGIND=NOT_CFG,
ADD NRDuCellTrp: NrDuCellTrpId=0, NrDuCellId=0, TxRxMode=64T64R,
UEPOWERMAXCFGIND=NOT_CFG,
BasebandEqmId=0, CpriCompression=2_COMPRESSION, MaxTransmitPower=4,
MULTIRRUCELLFLAG=BOOLEAN_FALSE,
BbResMutualAidSw =OFF;
TXRXMODE=4T4R;
//Add sector equipment.
ADD NRDUCellCoverage: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=1;
ADD EUCELLSECTOREQM: LocalCellId=0,
SectorEqmId=1;
//Add an operator for the cell.
The configuration of this MO is not required because 19A has only one operator.
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
//Activate the cell. //Activate the cell.
ACT CELL: LocalCellId=0; ACT NRCELL: NRCellId=0;
All configurations are implemented on the CU. Huawei Confidential
36
 Initial Configuration Scripts
LTE 5G
//Configure neighboring cells.
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3100,
18B does not support inter-frequency handovers. Therefore, running
UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG,
this command is not required.
SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100,
PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20",
ADD NREXTERNALNCELL: Mcc="460", Mnc="02", gNBId=236,
eNodeBId=236, CellId=0, DlEarfcn=3100, UlEarfcnCfgInd=NOT_CFG,
CellId=0, CellName="22", PhysicalCellId =236, DlNarfcn =40230;
PhyCellId=236, Tac=33;
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460",
ADD NRCELLRELATION: NRCellId=0, Mcc="460", Mnc="02",
Mnc="20", eNodeBId=236, CellId=0, CellIndividualOffset=dB1,
gNodeBId=236, CellId=0, NCellType =INTRA_FREQ;
CellQoffset=dB1, NoHoFlag=PERMIT_HO_ENUM;

37 Huawei Confidential
 Initial Configuration Scripts-Uplink and Downlink
Decoupling
Description
Add a primary cell.
Add a DU cell for the primary cell.
Add a DU cell for the secondary cell.
Bind the DU cell of the primary cell
and the DU cell of the secondary cell.
38
5G
ADD NRCELL: NRCellId=0, CellNname="CELL0",FrequencyBand=n3, CELLID=0,
DuplexMode=CELL_TDD, TrackingAreaId=0;
ADD NRDUCELL: NrDuCellId=0, NrDuCellName="0", FrequencyBand=N3,
UlBandwidth=CELL_BW_100M, DlBandwidth=CELL_BW_100M, DuplexMode=CELL_TDD,
PhysicalCellId =0, CELLID=0, gNBDuIndex=1;
ADD NRDUCELL: NrDuCellId=1, NrDuCellName="0", FrequencyBand=N80,
UlBandwidth=CELL_BW_20M, DlBandwidth=CELL_BW_20M, DuplexMode=CELL_FDD,
PhysicalCellId =1, CELLID=1, gNBDuIndex=1;
ADD NRDUCELLSUL: NrDuCellId=0, SulNrDuCellId=1;
Huawei Confidential
 Thank You
www.huawei.com

Copyright © 2018 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.
 GUI Changes Caused by Parameter Simplification
 Some formal parameters have been changed to reserved parameters.
 Non-configuration parameters have been deleted from the parameter reference.
 Feature parameters have been classified in the navigation tree.

40 Huawei Confidential
 Identical X2 Configuration for CI Interconnection and Transport
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.

41 Huawei Confidential