Loading documents preview...
Security Level:
5900 Base Station Initial Configuration Training Slides www.huawei.com
2018-06
HUAWEI TECHNOLOGIES CO., LTD.
Contents
3
1
gNodeB Device Configuration
2
gNodeB Transport Configuration
3
gNodeB Radio Configuration
Huawei Confidential
gNodeB Device Configuration Function Domain
Differences from LTE
Cabinets and subracks
In SRAN15.0, 5G supports only BBU5900, and Subrack Type must be set to BBU5900.
Boards in the BBU
In SRAN15.0, 5G supports only BBU5900: 1. If the baseband processing board is UBBPfw, set Work Mode to NR when adding a BBP. For a full-width 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.
RRU+ALD
RRUs must be configured only in uplink & downlink decoupling scenarios. RF Unit Working Mode must be set to LN(LTE_FDD_NR). Other parameter values are the same as those for LTE.
FMU
Same as LTE
TCU
Same as LTE
CCU
Same as LTE
EMU
Same as LTE
User-defined alarm
Same as LTE
(Optional) Power module data
Power supply management
Same as LTE
Time data
Time data
Same as LTE
GPS or RGPS reference clock
Same as LTE
IEEE 1588V2 clock reference
Same as LTE
1PPS+TOD clock
Same as LTE
Deployment type and product type
18B: Single RAT. Set Working Mode to NON-CONCURRENT(Non-ConCurrent) and Product Type to DBS5900_5G. 19A: Multi RATs, referring to the co-MPT mode. Set Working Mode to CONCURRENT(ConCurrent) and Product Type to BTS5900 or DBS5900. Huawei Confidential
Cabinet, subrack, and BBU data
RF unit and ALD data
(Optional) Monitoring unit data
gNodeB (TDD) clock data
Node
4
Subfunction Area
Configuration Scripts
5
LTE
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_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_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=LTE_FDD, BRDSPEC=UBBPd3;
//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 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 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 eNodeB application. ADD APP: AID=1, AT=eNodeB, AN="eNodeB";
//Add gNodeB application. ADD APP: AID=1, AT=gNodeB, AN="gNodeB", RUNMODE="INTEGRATED"; Huawei Confidential
Contents
6
1
gNodeB Device Configuration
2
gNodeB Transport Configuration
3
gNodeB Radio Configuration
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) New model – macro base stations
Old model – macro base stations
RANCU_E (RAT)
S1-C/X2-C/F1-C
S1/X2/eX2
S1/X2/eX2
RANCU_E (COM)
EPGROUP
EPGROUP
EPGROUP SCTPHOST
S1-U/X2-U/F1-U
SCTPHOST
USERPLANEHOST
SCTPHOST
USERPLANEHOST
USERPLANEHOST
IPADDR4
INTERFACE LOOPBACK Application layer
Application layer
IPRT
DEVIP
RANCU_P
IPROUTE4
IPADDR4
VRF
INTERFACE
VRF
ETHPORT Physical interface/Link interface Physical board
Old model – macro base stations: The DEVIP is directly configured on 8 the physical/link interface.
IPROUTE4
IPADDR4
VRF
INTERFACE
IP layer
IP layer
IP layer
IP2TRPSUNIT
ETHPORT
LOOPBACK
Physical interface/Link interface Physical board New model – macro base stations: 1. The PORTID parameter is added to the MOs on the physical/link interface. 2. The INTERFACE is configured on the physical/link interface and the LOOPBACK is added. 3. The IPADDR4 is configured on INTERFACE.
Physical interface /Link interface Logical board
LOOPBACK
VETHPORT
TRPSUNIT
RANCU: No parameter of the cabinet, subrack, or slot on VETHPORT
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.
Data link layer
(Optional) It is recommended that VLAN networking be based on the next-hop IP address. 1. Configure a VLANMAP MO with VLAN Priority set to DISABLE(Disable) (recommended). 2. (Optional) Configure a DSCPMAP MO to set the mappings between DSCPs and VLAN priorities.
None
Transport layer
1. Configure DEVIP MOs to add OM, service, and signaling IP addresses. 2. Configure an IPRT MO (for destination IP address-based routing policy) or an SRCIPRT MO (for source IP address-based routing policy). 3. (Optional) If common transmission or base station cascading is planned, configure an RSCGRP MO with TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and configure an IP2RSCGRP MO. (18B does not involve QoS) 4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. 5. Configure SCTPHOST MOs. 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.
1. Only the endpoint mode is supported. 2. If rate limitations for base station cascading and common transmission are not required, do not configure an RSCGRP MO and related MOs. 3. S1 self-setup: A gNodeB has only an S1-U interface, which is automatically set up through an eNodeB. 4. X2 self-setup: The X2 interface is automatically set up through the U2020. * For details about interface self-setup, see X2 and S1 Self-Management in NSA Networking Feature Parameter Description.
Maintenance channel
Configure an OMCH MO.
None
DHCP
(Optional) If base station cascading is planned, configure DHCPSVRIP and DHCPRELAYSWITCH MOs.
None
Interface information Configure gNBCUS1 and gNBCUX2 MOs.
9
Interfaces in 5G NSA networking
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 is set to NEW.
None
The parameter TRANSCFGMODE 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. 1. Configure an INTERFACE MO. Set Interface Type to VLAN(VLAN). 2. (Optional) Configure a DSCP2PCPMAP MO to set the mappings between DSCPs and VLAN priorities.
None
The interface-based VLAN configuration is recommended.
Transport layer
1.
Configure IPADDR4 MOs: For adding OM, service, and signaling IP addresses, configure the IPADDR4 MOs on the INTERFACE MO. It is advised to use loopback IP addresses as the signaling and service IP addresses in IPSec scenarios, scenarios with the active and standby routes, or scenarios where OM data and service data are isolated. In this case, configure LOOPBACK MOs to add signaling and service IP addresses. 2. Configure an IPROUTE4 MO (for destination IP address-based routing policy) or an SRCIPROUTE4 MO (for source IP address-based routing policy). 3. (Optional) If common transmission or base station cascading is planned, configure an IPRSCGRP MO with TXBW, TXCBS, and TXEBS set to appropriate values to limit the rates of bypass traffic and configure an IP2IPRSCGRP MO. (18B does not involve QoS) 4. (Optional) Configure an SCTPTEMPLATE MO to plan a user-defined template. 5. Configure SCTPHOST MOs. 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.
1. Only the endpoint mode is supported. 2. If rate limitations for base station cascading and common transmission are not required, do not configure an IPRSCGRP MO and related MOs. 3. S1 self-setup: A gNodeB has only an S1-U interface, which is automatically set up through an eNodeB. 4. X2 self-setup: The X2 interface is automatically set up through the U2020. * For details about interface self-setup, see X2 and S1 Self-Management in NSA Networking Feature Parameter Description.
1. The INTERFACE and LOOPBACK MOs are added. 2. The DEVIP MO is replaced by the IPADDR4 MO. 3. The IPRT MO is replaced by the IPROUTE4 MO. 4. The SRCIPRT MO is replaced by the SRCIPROUTE4 MO. 5. The RSCGRP MO is replaced by the IPRSCGRP MO. 6. The IP2RSCGRP MO is replaced by the IP2IPRSCGRP MO.
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.
11
Function Domain
Procedure
Differences from Macro Base Stations
Physical layer
1. Configure a TRPSUNIT MO. 2. Configure a VETHPORT MO.
1. The added TRPSUNIT MO is equal to a 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. 1. Configure an INTERFACE MO. Set Interface Type to VLAN(VLAN). 2. (Optional) Configure a DSCP2PCPMAP MO to set the mappings between DSCPs and VLAN priorities.
The interface-based VLAN configuration is recommended.
Transport layer
1. Configure IPADDR4 MOs: For adding OM and interface IP addresses, configure the IPADDR4 MOs on the INTERFACE MO. It is advised to use loopback IP addresses as the IP addresses of the DNS server in F1 self-setup scenarios. In this case, configure LOOPBACK MOs to add IP addresses. 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.
1. The source IP address-based routing policy is not supported. 2. The dynamic OSPF route is supported.
RANCU_P maintenance channel
Configure an OMCH MO.
The active and standby OM channels are not supported.
DNS server
(Optional) Configure a DNSERVER MO for planning the F1 self-setup.
The DNSERVER MO is added on the RANCU side.
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 SGW/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. 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.
Only the endpoint mode is supported.
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 maintenance channel
Configure an OMCH MO.
The active and standby OM channels are not 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
7. DL data
1. 2. 3. 4. 5. 6. 7.
14
5. Bear Modification (notifying the S-GW of the S1-U address of the bearer on the RAN side)
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. The gNodeB sends an SgNB Addition Request ACK message to the eNodeB. The message carries the S1-U address on the gNodeB side. The procedure for the UE to access the gNodeB is performed. 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. 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. The MME sends an eRAB Modification Confirm message to the eNodeB. The S-GW sends downlink data to the gNodeB.
Huawei Confidential
Contents
15
1
gNodeB Device Configuration
2
gNodeB Transport Configuration
3
gNodeB Radio Configuration
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
MO APP AT = gNodeB
Inclusion Reference
MO gNodeBFunction
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 NE
MO NE
Inclusion
MO APP AT = gNodeB
Reference
Inclusion
MO DFU
Inclusion
MO APP AT = gNodeB
Reference
Inclusion
MO gNodeBFunction Inclusion Inclusion
MO gNBDU
Reference
MO DFUAgent
Reference
18
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 Huawei Confidential the NetworkID parameter.
Configuration Scripts LTE
5G
//Add eNodeB application. ADD APP: AID=1, AT=eNodeB, AN="eNodeB";
//Add gNodeB application. ADD APP: AID=1, AT=gNodeB, AN=“gNodeB", RUNMODE="INTEGRATED";
//Add an eNodeB function. ADD ENODEBFUNCTION: eNodeBFunctionName="LTE", ApplicationRef=1, eNodeBId=9527;
//Add a gNodeB function. ADD GNODEBFUNCTION: gNodeBFunctionName="NR", gNBId= 9527, gNBIdLength =22, ApplicationReference=1; ADD GNBDU: gNBDuIndex=1, gNBDuId=9527, gNBDuName= "DU", 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 NRDuCell
Reference
MO NRCell
MO gNBCUX2
MO gNBCUS1
MO gNBDUX2
MO 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 BTS5900
NE RANCU_GNB
MO gNodeBFunction
MO gNodeBFunction
Inclusion
MO NRDuCell MO gNBDUF1
MO gNBDUX2
NE BTS5900 MO gNodeBFunction Inclusion
Inclusion Reference
MO gNBDUS1
MO NRCell MO gNBCUX2
MO NRCell MO gNBCUS1
MO gNBCUF1
Inclusion
MO NRDuCell
MO gNBDUF1
MO gNBDUX2
MO gNBDUS1
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 gNBDULogicNode
MO gNodeBFunction
Inclusion
Inclusion
MO gNBDUX2
MO gNBCUX2
Reference
Reference
MO EPGroup
MO EPGroup Inclusion
Inclusion
MO UserPlaneHost
1. 2.
3. 4.
23
MO gNBX2SonConfig
MO UserPlaneHost
MO SCTPPeer
MO SCTPHost
The X2-C interface is supported. 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). 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. 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. 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 gNodeBFunction
MO gNodeBFunction Inclusion
Inclusion
MO gNBDUF1
MO gNBCUF1
Reference
Reference
MO EPGroup
MO EPGroup
Inclusion
MO UserPlaneHost
1. 2.
3.
25
MO SCTPPeer
Inclusion
MO SCTPHost
MO UserPlaneHost
MO SCTPPeer
MO SCTPHost
Both the CU and the DU support the F1-C interface and the F1-U interface. 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). 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).
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;
26
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 CUDU integrated deployment.
Huawei Confidential
Differences Between 4G/5G Initial Configuration Scripts Top-Layer Nodes Transport Cell
27
Huawei Confidential
gNodeB Service Configuration-Cell MO Model NE BTS5900 MO NRDUCell
Association
NE RANCU_GNB MO NRCell
Service
2.
3. 4.
28
Reference
MO NRCell
MO NRDUCellTrp
Inclusion
1.
Belonging to
MO NRDUCell Service
MO NRDUCellTrp
MO NRDUCellCoverage
MO gNBDU
Inclusion
Reference
MO SectorEqm
MO NRDUCellCoverage
Reference
MO SectorEqm
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. 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. 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. 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. Huawei Confidential
gNodeB Service Configuration-Common Cell Instance MO NRDUCell
Association
MO NRCell
Service
MO NRDUCellTrp Inclusion
MO NRDUCellCoverage
gNodeB Cell
Common cell
Reference
MO SectorEqm
29
1. One NRCell MO is associated with one NRDUCell MO by setting the CellId. 2. One NRDUCell MO is only served by one NRDUCellTrp MO. 3. One NRDUCellTrp MO includes only one NRDUCellCoverage MO. Huawei Confidential
gNodeB Service Configuration-Uplink and Downlink Decoupling Cell Instance SUL
TDD
MO NRDUCell-2
MO NRDUCell-1
Association
Service
Service
MO NRDUCellTrp-2
MO NRDUCellTrp-1
Inclusion
Association
MO NRCell gNodeB Cell
gNodeB Cell
Inclusion
UL/DL decoupling cells MO NRDUCellCoverage-2
MO NRDUCellCoverage-1
Reference
Reference
MO SectorEqm-2
30
MO SectorEqm-1
1. One NRCell MO is associated with one NRDUCell instance (NRDUCell-1) by setting the CellId. 2. NRDUCell-1 is associated with one NRDUCell instance (NRDUCell-2), which provides SUL resources for NRDUCell-1. 3. One NRDUCell MO is served by only one NRDUCellTrp MO. 4. One NRDUCellTrp MO includes only one NRDUCellCoverage MO. Huawei Confidential
gNodeB Service Configuration-Cell SectorEqm Configuration (Common Antenna) MO NRDuCellTrp
MO NRDuCellTrp-1
Inclusion
MO NRDUCellCoverage
Inclusion
SectorEqmAntPortRef
Inclusion
Association
MO RRU
Reference
MO Sector
Inclusion
Inclusion
MO NRDUCellCoverage-1
MO NRDUCellCoverage-2
Reference
Reference
MO SectorEqm
MO NRDuCellTrp-2
SectorAntPortRef
Association
MO SectorEqm
Inclusion
MO NRDuCellTrp-3 Inclusion
MO NRDUCellCoverage-3
Reference
SectorEqmAntPortRef
Reference Association
MO RRU
Reference
MO Sector
Inclusion
SectorAntPortRef
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 NRDuCellTrp
MO NRDuCellTrp-1
Inclusion
Inclusion
MO NRDUCellCoverage
MO NRDUCellCoverage Reference
Reference
MO SectorEqm
MO NRDuCellTrp-2
Association
MO RRU
Reference
MO Sector
Low-band massive MIMO
Inclusion
Inclusion
MO NRDUCellCoverage Reference Association
MO SectorEqm
MO NRDuCellTrp-3
MO NRDUCellCoverage Reference
MO RRU
Reference
MO Sector
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
34
Parameter Name NR Cell ID NR Local Cell ID Cell Available State NR Cell State Local Cell State
Description 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.
Cell Latest State Change Reason
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.
Latest Time When Cell Become Available Latest Operation Make Cell Available Latest Time When Cell Become Unavailable Latest Operation Make Local Cell Unavailable
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.
Cell Control Node Information
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.
Huawei Confidential
gNodeB Cell Maintenance-DU Cell Information Query Parameter Name
Description
NR DU Cell ID
Indicates the ID of an NR DU cell, which uniquely identifies the cell within a DU.
Latest Time When DU Cell Become Available
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.
Latest Operation Make DU Cell Available
Indicates the latest operation that makes an NR DU cell available.
Latest Time When DU Cell Become Unavailable Latest Operation Make DU Cell Unavailable
Indicates the latest time when an NR DU cell becomes unavailable. Indicates the latest operation that makes an NR DU cell unavailable.
NR Cell ID NR DU Cell State DU Cell Latest State Change Reason
35
Huawei Confidential
Initial Configuration Scripts LTE ADD CELL: LOCALCELLID=0, CELLNAME="CELL0", FREQBAND=41, ULEARFCNCFGIND=NOT_CFG, DLEARFCN=40340, ULBANDWIDTH=CELL_BW_N100, DLBANDWIDTH=CELL_BW_N100, CELLID=0, PHYCELLID=0, FDDTDDIND=CELL_TDD, SUBFRAMEASSIGNMENT=SA2, SPECIALSUBFRAMEPATTERNS=SSP7, EUCELLSTANDBYMODE=ACTIVE, ROOTSEQUENCEIDX=0, CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG, EMERGENCYAREAIDCFGIND=NOT_CFG, UEPOWERMAXCFGIND=NOT_CFG, MULTIRRUCELLFLAG=BOOLEAN_FALSE, TXRXMODE=4T4R; //Add sector equipment. ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1;
36
5G
//Add cells. ADD NRDUCELL: NrDuCellId=0,DuCellNname="CELL0", FrequencyBand=n3, UlBandwidth=CELL_BW_N100, DlBandwidth=CELL_BW_N100, DuplexMode=CELL_FDD; PhysicalCellId=0, CELLID=0, gNBDuIndex=1, UlEarfcnConfigInd=CONFIG, UlEarfcn=331000, DlEarfcn=350000, SlotAssignment=4_1_DDDSU, SlotStructure=SS5,SubcarrierSpacing=30KHZ, WorkMode=UL_DL, CellRadius=1000; ADD NRCELL: NRCellId=0, CellNname="CELL0", FrequencyBand=n3,CELLID=0, DuplexMode=CELL_FDD, DlEarfcn=350000, TrackingAreaId=0; ADD NRDuCellTrp: NrDuCellTrpId=0, NrDuCellId=0, TxRxMode=64T64R, BasebandEqmId=0, CpriCompression=2_COMPRESSION, MaxTransmitPower=4, BbResMutualAidSw =OFF; ADD NRDUCellCoverage: NrDuCellTrpId=0, NrDuCellCoverageId=0, SectorEqmId=1;
//Add an operator for the cell. ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
The configuration of this MO is not required because 19A has only one operator.
//Activate the cell. ACT CELL: LocalCellId=0;
//Activate the cell. ACT NRCELL: NRCellId=0;
All configurations are implemented on the CU.
Huawei Confidential
Initial Configuration Scripts
37
LTE
5G
//Configure neighboring cells. ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3100, UlEarfcnCfgInd=NOT_CFG, CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG;
18B does not support inter-frequency handovers. Therefore, running this command is not required.
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=236, CellId=0, DlEarfcn=3100, UlEarfcnCfgInd=NOT_CFG, PhyCellId=236, Tac=33;
ADD NREXTERNALNCELL: Mcc="460", Mnc="02", gNBId=236, CellId=0, CellName="22", PhysicalCellId =236, DlNarfcn =40230;
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=236, CellId=0, CellIndividualOffset=dB1, CellQoffset=dB1, NoHoFlag=PERMIT_HO_ENUM;
ADD NRCELLRELATION: NRCellId=0, Mcc="460", Mnc="02", gNodeBId=236, CellId=0, NCellType =INTRA_FREQ;
Huawei Confidential
Initial Configuration Scripts-Uplink and Downlink Decoupling
38
Description
5G
Add a primary cell.
ADD NRCELL: NRCellId=0, CellNname="CELL0",FrequencyBand=n3, CELLID=0, DuplexMode=CELL_TDD, TrackingAreaId=0;
Add a DU cell for the primary cell.
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 a DU cell for the secondary cell.
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;
Bind the DU cell of the primary cell and the DU cell of the secondary cell.
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