Base Station Equipment Reliability (SRAN18.1 - 01)
Base Station Equipment Reliability (SRAN18.1 - 01)
Base Station Equipment Reliability (SRAN18.1 - 01)
Issue 01
Date 2022-03-08
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: [email protected]
Contents
1 Change History.........................................................................................................................1
1.1 SRAN18.1 01 (2022-03-08)..................................................................................................................................................1
1.2 SRAN18.1 Draft B (2022-02-08)........................................................................................................................................ 1
1.3 SRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 2
3 Overview................................................................................................................................. 10
4 RRU Channel Cross Connection Under MIMO (LTE/NR).............................................. 14
4.1 Principles.................................................................................................................................................................................. 14
4.2 Network Analysis.................................................................................................................................................................. 15
4.2.1 Benefits................................................................................................................................................................................. 15
4.2.2 Impacts.................................................................................................................................................................................. 15
4.3 Requirements......................................................................................................................................................................... 15
4.3.1 Licenses................................................................................................................................................................................. 15
4.3.2 Software................................................................................................................................................................................15
4.3.3 Hardware.............................................................................................................................................................................. 16
4.3.4 Cells........................................................................................................................................................................................ 16
4.3.5 Others.................................................................................................................................................................................... 16
4.4 Operation and Maintenance............................................................................................................................................. 16
4.4.1 When to Use....................................................................................................................................................................... 16
4.4.2 Precautions.......................................................................................................................................................................... 17
4.4.3 Data Configuration........................................................................................................................................................... 17
4.4.3.1 Data Preparation............................................................................................................................................................ 17
4.4.3.2 Using MML Commands............................................................................................................................................... 18
4.4.3.3 Using the MAE-Deployment...................................................................................................................................... 19
4.4.4 Activation Verification..................................................................................................................................................... 19
4.4.5 Network Monitoring......................................................................................................................................................... 19
7.2.1 Benefits................................................................................................................................................................................. 44
7.2.2 Impacts.................................................................................................................................................................................. 44
7.3 Requirements......................................................................................................................................................................... 44
7.3.1 Licenses................................................................................................................................................................................. 44
7.3.2 Software................................................................................................................................................................................44
7.3.3 Hardware.............................................................................................................................................................................. 45
7.3.4 Others.................................................................................................................................................................................... 46
7.4 Operation and Maintenance............................................................................................................................................. 46
7.4.1 When to Use....................................................................................................................................................................... 46
7.4.2 Data Configuration........................................................................................................................................................... 46
7.4.2.1 Data Preparation............................................................................................................................................................ 46
7.4.2.2 Using MML Commands............................................................................................................................................... 49
7.4.2.3 Using the MAE-Deployment...................................................................................................................................... 52
7.4.3 Activation Verification..................................................................................................................................................... 52
7.4.4 Network Monitoring......................................................................................................................................................... 55
9.3.4 Others.................................................................................................................................................................................... 67
9.4 Operation and Maintenance............................................................................................................................................. 67
9.4.1 When to Use....................................................................................................................................................................... 67
9.4.2 Data Configuration........................................................................................................................................................... 67
9.4.2.1 Data Preparation............................................................................................................................................................ 67
9.4.2.2 Using MML Commands............................................................................................................................................... 68
9.4.2.3 Using the MAE-Deployment...................................................................................................................................... 69
9.4.3 Activation Verification..................................................................................................................................................... 69
9.4.4 Network Monitoring......................................................................................................................................................... 70
11.3.4 Others................................................................................................................................................................................. 80
11.4 Operation and Maintenance.......................................................................................................................................... 80
11.4.1 When to Use..................................................................................................................................................................... 80
11.4.2 Data Configuration......................................................................................................................................................... 80
11.4.2.1 Data Preparation..........................................................................................................................................................80
11.4.2.2 Using MML Commands............................................................................................................................................. 81
11.4.2.3 Using the MAE-Deployment.................................................................................................................................... 82
11.4.3 Activation Verification................................................................................................................................................... 82
11.4.4 Network Monitoring...................................................................................................................................................... 83
12 Other Functions................................................................................................................... 84
12.1 RF Channel Cooperation (GSM/UMTS)...................................................................................................................... 84
12.2 Heat Dissipation Reliability for Fans............................................................................................................................84
12.3 Power Supply Redundancy.............................................................................................................................................. 85
12.3.1 Power Supply Redundancy for a BBU...................................................................................................................... 85
12.3.2 Power Supply Redundancy.......................................................................................................................................... 86
12.4 Anti-Misinsertion Design of Boards............................................................................................................................. 86
12.5 Overtemperature Protection for BBU Boards........................................................................................................... 86
12.5.1 Overtemperature Power-off for Non-Main-Control Boards............................................................................ 86
12.5.2 Overtemperature Power-off for Main Control Boards....................................................................................... 87
12.6 Surge Protection Design................................................................................................................................................... 88
12.6.1 Standards........................................................................................................................................................................... 88
12.6.2 Surge Protection Capability of Ports........................................................................................................................ 89
13 Glossary................................................................................................................................. 91
14 Reference Documents........................................................................................................ 92
1 Change History
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station
Model
Editorial Changes
Revised descriptions in this document.
Technical Changes
Change Description Parameter Change Base Station
Model
Added support for Cold Backup of Added parameters: 5900 series base
RF Modules (NR TDD). For details, ● RFHAGRP.MRFCN stations
see:
● RFHAGRP.MRFSRN
● 2.3 Features in This Document
● RFHAGRP.MRFSN
● 2.4 Differences
● RFHAGRP.BRFCN
● 3 Overview
● 9 Cold Backup of RF Modules ● RFHAGRP.BRFSRN
(NR TDD) ● RFHAGRP.BRFSN
Editorial Changes
Revised descriptions in this document.
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
Unless otherwise specified, in this document, LTE and eNodeB always include FDD,
TDD, and NB-IoT. In scenarios where they need to be distinguished, LTE FDD, LTE
TDD, and LTE NB-IoT are used. The same rules apply to eNodeB.
2.4 Differences
Table 2-1 Differences between LTE FDD and LTE TDD
Function Name Difference Chapter/Section
Table 2-5 Differences between high frequency bands and low frequency bands of
NR
Function Name Difference Chapter/Section
3 Overview
The reliability design feature includes redundancy design and hardware reliability
design. With reliability design, base station equipment can continue to provide
services even when some parts are faulty. This avoids or reduces the impact on
services caused by equipment faults and improves system reliability.
Table 3-1 describes the base station equipment reliability features/functions
supported by GSM, UMTS, LTE, and NR. In this table, "Y" means "supported" and
"N" means "not supported."
Inter- Ya Ya Y Y ● GBTS/eGBTS/NodeB: 6
Board Inter-Board Baseband
Baseb Resource
and Redundancy (GSM/
Resou UMTS)
rce ● eNodeB/gNodeB: 7
Redun Inter-Board Baseband
dancy Resource
Redundancy
(LTE/NR)
Intra- Yb Yb Y Y ● 10 Intra-Board
Board (supporte Baseband Resource
Baseb d only in Pool
and LTE FDD ● eNodeB: This feature
Resou and is enabled by default if
rce TDD)b the LBBPc is
Pool configured. For details
about activation
verification, see 10.4.4
Activation
Verification.
RF N N N Y 9 Cold Backup of RF
modul (suppo Modules (NR TDD)
e cold rted
backu only in
p NR
TDD)
RF Y Y N N ● 12.1 RF Channel
Chann Cooperation (GSM/
el UMTS)
Coope ● GBTS/eGBTS: TRX
ration Cooperation
● NodeB: RRU
Redundancy
Heat Y Y Y Y ● 12.2 Heat Dissipation
Dissip Reliability for Fans
ation ● The TCU, FMU, or BBU
Reliab fan modules are
ility required. For details
for about the initial
Fansb configuration, see
3900 & 5900 Series
Base Station Initial
Configuration Guide.
Power Y Y Y Y ● 12.3 Power Supply
Suppl Redundancy
y ● Power Supply
Redun Redundancy of a base
dancy station: Power Supply
Management
● Power Supply
Redundancy for a
BBUb
NOTE
a: This function is a basic function of the base station and has no feature ID. It requires
software configurations.
b: This function is a basic function of the base station and has no feature ID. It does not
require any software configurations.
4.1 Principles
In sparsely populated areas, RRUs or RFUs may be installed on top of a tower and
base stations are installed in inaccessible areas. This makes subsequent equipment
maintenance difficult. If any RRU or RFU is faulty, an entire sector remains
unavailable for a long time. With RRU Channel Cross Connection Under MIMO
enabled on the eNodeB or gNodeB, the failure in one RRU or RFU will not lead to
service interruption of the entire sector. This feature increases RRU or RFU
reliability without increasing hardware costs.
As shown in Figure 4-1 (using three sectors as an example), a baseband
processing unit (BBP) is connected to multiple RRUs. In this case, the data on two
TX/RX channels of a cell is transmitted over two different optical fibers and
processed by two different RRUs. When a fault occurs on an optical fiber or an
RRU has a hardware fault, the antenna mode changes from 2T2R to 1T1R to keep
the cell working normally. This prevents long-time service interruption and
increases system reliability.
NOTE
The implementation method of this feature on the gNodeB is the same as that on the
eNodeB. The following figure uses the eNodeB as an example.
Figure 4-1 RF cable connections for RRU channel cross connection under MIMO
4.2.1 Benefits
None
4.2.2 Impacts
None
4.3 Requirements
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
None
Table 4-1 Mutually exclusive functions of RRU Channel Cross Connection Under
MIMO
RAT Function Name Function Switch Reference
4.3.3 Hardware
● This feature applies only to macro base stations and LampSite base stations. It
is implemented in the same way on macro base stations and LampSite base
stations.
● The RRUs or RFUs must be of the same model and support the same set of
frequency bands.
● The number of RRUs or RFUs must be greater than or equal to two.
● The difference in length of optical fibers for RRUs must be less than or equal
to 100 m.
● The LRRUs or LRFUs must form a star topology and connect to the same BBP.
NOTE
In multimode base stations where the dual-star topology is used, RRUs must be connected
to the same BBP.
4.3.4 Cells
● Cells enabled with RRU channel cross-connection under MIMO must operate
on the same frequency and have the same bandwidth.
● Cells enabled with RRU channel cross-connection under MIMO must be 2T2R
cells.
4.3.5 Others
None
BBP and RRUs/RFUs enable the data on two TX/RX channels of a cell to be
transmitted using two optical fibers and to be processed by two RRUs/RFUs. When
an optical fiber or an RRU/RFU has a hardware fault, the antenna mode changes
from 2T2R to 1T1R to keep the cell working normally. This prevents long-time
service interruption and increases system reliability.
4.4.2 Precautions
The precautions for deploying RRU Channel Cross Connection Under MIMO are as
follows:
● The RRUs or RFUs must be of the same model and support the same set of
frequency bands.
● Two or more RRUs or RFUs are required.
● The antenna mode must be 2T2R for the sectors on which RRU Channel Cross
Connection Under MIMO applies. Two transmit and two receive channels of
each sector must be configured on different RRUs or RFUs, and the RRUs or
RFUs must be correctly connected to antennas.
● The RRUs or RFUs must form a star topology and connect to the same BBP.
● For LBBPc boards, optical fibers that connect the LBBPc boards and RRUs or
RFUs should have the same length if possible. However, if this condition
cannot be satisfied, any differences in lengths must be less than or equal to
100 m (328.08 ft). This restriction does not apply to LBBPd boards.
● If faults on the optical fiber or RRU are rectified when the cell has rolled back
to 1T1R and is in active mode, the system triggers the cell reestablishment to
change the cell configuration from 1T1R to 2T2R only when no user in RRC
connected mode exists in the cell.
In multimode scenarios, RRU Channel Cross Connection Under MIMO is supported
by LTE and NR. For other RATs, support for this feature depends on the RAT
capability.
Table 4-2 Parameters for RRU Channel Cross Connection Under MIMO
Parameter Name Parameter ID Setting Notes
Two antennas are generally configured, and R0A and R0B corresponding to antenna
channels are configured on different antenna ports on the RRU. Physical cable connections
must be consistent with the configurations.
ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=61, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;
ADD SECTOR: SECTORID=1, ANTNUM=2, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=62, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=1;
ADD SECTOR: SECTORID=2, ANTNUM=2, ANT1CN=0, ANT1SRN=62, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=2;
Step 6 Run the ADD EUCELLSECTOREQM command to add cell sector equipment.
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1;
ADD EUCELLSECTOREQM: LocalCellId=2, SectorEqmId=2;
----End
----End
5.1 Principles
When a base station is configured with only one main control board, services will
be interrupted for a long period of time if this main control board is faulty. To
support Cold Backup of Main Control Boards, two main control boards of the
same type must be configured for the base station. When a fault is detected on
the active main control board, the active and standby boards switch roles. Services
carried on the original active board are interrupted but automatically recover
within the expected period, which ensures reliability. For macro base stations, the
expected period for automatic recovery is 4 to 7 minutes. For LampSite base
stations, the expected period is 4 to 10 minutes, as a large number of pRRUs are
used.
In the following scenarios, the service recovery required time is 2 minutes longer
than the expected period for automatic recovery:
● The switchover between the boards is triggered manually by running the SWP
BRD command. The service recovery required time equals the interval
between the time when the command is executed and the time when services
are restored.
● The switchover between the boards is triggered after the running active main
control board is removed.
● In a secure networking scenario, the new active main control board does not
have a digital certificate or the digital certificate is invalid or has expired. For
details about secure networking scenarios, see Transmission Security
Overview.
Cold Backup of Main Control Boards involves three processes: active/standby
competition, data backup, and active/standby switchover.
one main control board cannot be detected or is not functioning properly, the
other main control board becomes the active one.
NOTE
The main control boards in active/standby mode must be in their original system state. If a
main control board has been used at a site, certain configuration data may be left in this
board, which affects the active/standby competition process. As a result, the active/standby
relationship may not be established as expected. For example, the main control board in
slot 6 is expected to be the active board, and the main control board inserted later in slot 7
is expected to be the standby board. If certain configuration data is left in the board in slot
7, it may serve as the active board after the active/standby competition. Therefore, if the
main control board inserted later is not in its original system state and has residual
configuration data, run the ACT CFGFILE command to activate the minimum configuration
before inserting the board.
Data backup consists of initial backup and routine backup, which are described as
follows:
● Initial backup: After the base station and the active and standby main control
boards are started, the base station compares the files on the two boards.
Then, the base station copies the files that are unique on the active board to
the standby board and removes unnecessary files from the standby board.
During initial backup, configuration data, software data, and logs are all
backed up.
● Routine backup: After the base station completes initial backup, the base
station periodically compares the files on the active and standby main control
boards (every 5 minutes by default). Then, the base station copies the files
that are unique on the active board to the standby board.
NOTE
Fault- The standby main control The system When the active main
triggered board is functioning automaticall control board
switchover properly, the links of the y triggers experiences major
standby board are normal, the faults, services carried
the standby board has no switchover. on this board must be
major hardware faults, switched over to the
and the clock is locked. standby main control
board to ensure the
normal operation of
the base station.
Therefore, the
switchover
prerequisites are
relatively simple.
Others The standby main control The system When the status of
board is functioning automaticall the Ethernet ports
properly, the links of the y triggers carrying the IP
standby board are normal, the addresses on the
the standby board has no switchover. active main control
major hardware faults, board are inactive and
and the clock is locked. the status of the
corresponding
Ethernet ports on the
standby main control
board are active,
services carried on the
active board must be
switched over to the
standby board to
ensure normal
operation of the base
station. Therefore, the
switchover
prerequisites are
relatively simple.
NOTE
5.2.1 Benefits
None
5.2.2 Impacts
None
5.3 Requirements
5.3.1 Licenses
None
5.3.2 Software
None
5.3.3 Hardware
● Only the UMPT board supports Cold Backup of Main Control Boards.
Cold backup of UMPT boards applies to macro and LampSite base stations
that use the BBU3910, BBU3900, or BBU5900, including NodeBs, eNodeBs,
gNodeBs, and co-MPT base stations. It is implemented in the same way on
macro and LampSite base stations.
● To support Cold Backup of Main Control Boards, two identical main control
boards are required in the same BBU. For example, the two boards are both
UMPTb1.
NOTE
In scenarios where two UMPT boards work in cold backup mode, if the spare UMPT board
and the UMPT board to be replaced are of different RATs, the spare UMPT board
automatically operates in the RAT of the replaced UMPT board and works in active/
standby mode with the other original UMPT board after the replacement.
● Two transmission cables are required, with one connected to the main control
board in slot 6 and the other connected to the main control board in slot 7.
● In a co-MPT multimode base station where two UMPT boards work in cold
backup mode, the standby UMPT board can work as a signaling extension
board for LTE or NR automatically but not for GSM or UMTS.
NOTE
When the standby UMPT board works as a signaling extension board for LTE or NR,
the LTE or NR services carried on this board will be interrupted if it experiences a
hardware fault or is removed. When the active UMPT board becomes faulty and the
active and standby UMPT boards switch roles, only the new active UMPT board
provides signaling processing capability.
● In UCIU+UMPT BBU interconnection scenarios, only the primary BBU supports
Cold Backup of Main Control Boards.
● In UMPT+UMPT BBU interconnection scenarios, the primary BBU does not
support Cold Backup of Main Control Boards
5.3.4 Networking
● UMPT boards with the active/standby transmission capability are supported
only in Ethernet networks.
● UMPT boards with the active/standby transmission capability do not support
HUB transmission cascading.
● Cold backup of main control boards has the following restrictions on the
secure networking planning:
– If UMPT boards work in cold backup mode and IPsec and digital
certificate authentication are used, the Certificate Authority (CA)
configuration on the base station must allow the standby main control
board to access the CA server and obtain the digital certificate after an
active/standby board switchover.
– If UMPT boards work in cold backup mode, and IPsec and digital
certificate authentication are used, the IDTYPE parameter can be set to
IPV4/FQDN/DN for the base station. When the IDTYPE parameter is set
to FQDN and the security gateway (SeGW) uses the digital certificate
whitelist to verify the base station identity, the SeGW adds both the
active and standby main control boards to the whitelist.
– Cold backup does not support IPv6-related features, direct IPsec, or the
new transmission model.
● The clock source must be the GNSS clock.
5.3.5 Others
None
● Services recover within several minutes after the main control board
experiences a hardware failure.
● In a co-MPT multimode base station, when the main control experiences a
severe hardware failure, services of all RATs are interrupted simultaneously.
This feature ensures that services can recover automatically. This improves
base station reliability.
5.4.2 Precautions
● After an HAGRP MO is configured, users must enter the value of the Logic
Slot No. parameter specified in the HAGRP MO as the slot number when
running the ADD XXX, RMV XXX, MOD XXX, LST XXX, or DSP XXX
commands related to transmission or clock. The output of a DSP XXX
command contains the number of the slot housing the active main control
board.
● Adding or removing an HAGRP MO changes the connection between the
base station and the transport network and resets the base station.
● Configuring an HAGRP MO
Table 5-3 describes the key parameters that must be set in the HAGRP MO.
DSP BRD:;
Step 2 Run the ADD BRD command to add a main control board with a different slot
number as the standby main control board.
ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT;
Step 3 Run the ADD HAGRP command to add a transport high availability (HA) group.
The value of the Logic Slot No. parameter must be the same as the slot number
of the main control board that is configured with transport data.
ADD HAGRP: CN=0, SRN=0, SN=7;
----End
NOTE
Step 1 Run the LST HAGRP command to query the logical slot number of the transport
HA group, for example, 6.
LST HAGRP:;
Step 2 Run the DSP BRD command to query the slot number of the active main control
board. Check whether the slot number of the active main control board (for
example, 7) is the same as the logical slot number of the transport HA group.
DSP BRD:;
Step 3 (Optional) If the slot number of the active main control board is different from
the logical slot number of the transport HA group, run the SWP BRD command to
switch over the active and standby main control boards. After this command is
executed, the base station will be reset.
SWP BRD:;
Step 4 Run the RMV HAGRP command to remove the transport HA group. After this
command is executed, the base station will be reset.
RMV HAGRP: CN=0, SRN=0, SN=6;
Step 5 Run the RMV BRD command to remove the main control board (standby main
control board) whose slot number is different from the slot number of the
transport HA group.
RMV BRD: CN=0, SRN=0, SN=7;
----End
This section describes the steps for activating Cold Backup of Main Control Boards
for a base station that meets the following requirements:
● A main control board has been configured in the base station and the
transport data has been configured for this board.
● The base station is operating properly.
SN MO Configuration Description
SN MO Configuration Description
SN MO Configuration Description
4 RSCGRP For the ATM bearer type, delete the RSCGRP MOs
that are automatically configured by default on
the standby main control board.
Step 2 Export the base station deployment list. For detailed operations, see section
"Preparing a Data Configuration File and a Deployment List" in 3900 & 5900
Series Base Station Commissioning Guide.
Step 3 Upload the base station deployment list to the MAE-Access so that the DHCP
server-related configurations are updated. For detailed operations, see section
"Creating an NE Commissioning Task" in 3900 & 5900 Series Base Station
Commissioning Guide.
----End
Step 1 After creating a planned data area, choose Advanced > Data Management >
Customize Summary Data File from the main menu, to customize a summary
data file for batch configuration.
NOTE
Step 3 In the summary data file, set the parameters related to the MPT MO for the
standby main control board, and close the file.
Step 8 In the summary data file, set the parameters related to the HAGRP MO, and close
the file.
Step 10 After the data verification is completed, choose Area Management > Planned
Area Management > Export Incremental Scripts to export and activate the
incremental scripts in the planned data area.
----End
Step 2 Export the base station deployment list. For detailed operations, see section
"Preparing a Data Configuration File and a Deployment List" in 3900 & 5900
Series Base Station Commissioning Guide.
Step 3 Upload the base station deployment list to the MAE-Access so that the DHCP
server-related configurations on the MAE-Access are updated. For detailed
operations, see section "Creating an NE Commissioning Task" in 3900 & 5900
Series Base Station Commissioning Guide.
Step 4 Deliver incremental configurations.
----End
NOTE
After the standby main control board is configured, initial backup is automatically performed.
This initial backup process takes approximately 150 minutes. You can run the DSP BKPSTATUS
command to query the backup progress.
Step 4 Switch the active and standby roles of the main control boards.
Run the SWP BRD command to perform the switch. Upon execution of this
command, the base station will automatically perform routine backup, reset, and
switchover between the active and standby main control boards. This process
takes approximately 30 minutes. Base station resets will interrupt ongoing
services.
----End
6.1 Principles
When a BBP fails, the cells served by this faulty BBP will be affected. Inter-Board
Baseband Resource Redundancy allows multiple BBPs to be configured in a base
station. This enables the cells or carriers served by a faulty BBP to be reestablished
on another operational BBP with available resources, which improves base station
reliability.
To implement this feature, a base station must be equipped with at least two BBPs
and these two BBPs must be installed in the same BBU.
NOTICE
● For GSM, only the UBBP board supports inter-board baseband resource
redundancy. It is recommended that the two UBBP boards be configured in
slots 0 and 1.
● Inter-board baseband resource redundancy for GSM does not require CPRI-
based topologies and is supported as long as two UBBP boards are configured.
However, the inter-board cold backup ring topology and hot backup ring
topology are not supported in GSM. For details, see RF Unit and Topology
Management.
NOTE
Inter-board baseband resource redundancy for UMTS does not require CPRI-based topologies
and is supported as long as two BBPs are configured. However, the hot backup ring topology is
not supported in UMTS. For details, see RF Unit and Topology Management.
6.2.1 Benefits
None
6.2.2 Impacts
None
6.3 Requirements
6.3.1 Licenses
None
6.3.2 Software
None
6.3.3 Hardware
● The NodeB is configured with two or more WBBP or UBBP boards, which are
installed in slots 0 to 5.
● The GBTS or eGBTS is configured with two or more UBBP boards. If two UBBP
boards are configured, it is recommended that they be installed in slots 0 and
1.
● This feature applies only to macro base stations that use the BBU3910,
BBU3900, or BBU5900.
6.3.4 Others
None
Table 6-2 describes the key parameters that must be set in the BTSBRD MO for
GSM (GBTS).
Table 6-2 Key parameters that must be set in the BTSBRD MO for GSM (GBTS)
Param Parameter ID Setting Notes
eter
Name
Table 6-3 describes the key parameters that must be set in the BASEBANDEQM
MO. For GSM, the BASEBANDEQM MO is required by the eGBTS and is not
required by the GBTS.
2. Run the ADD BASEBANDEQM command to add all BBPs requiring backup to
the same baseband equipment. Set the UL and DL baseband equipment
types, respectively.
ADD BASEBANDEQM: BASEBANDEQMID=0, UMTSDEMMODE=DEM_2_CHAN,
BASEBANDEQMTYPE=DL, CN1=0, SRN1=0, SN1=2, CN2=0, SRN2=0, SN2=1;
ADD BASEBANDEQM: BASEBANDEQMID=0, UMTSDEMMODE=DEM_2_CHAN,
BASEBANDEQMTYPE=UL, CN1=0, SRN1=0, SN1=2, CN2=0, SRN2=0, SN2=1;
GBTS
eGBTS
7.1 Principles
When a BBP is faulty, the cells served by the BBP will be affected. When multiple
BBPs are configured in a base station, Inter-Board Baseband Resource Redundancy
enables the cells or carriers served by a faulty BBP to be reestablished on another
operational BBP with available resources, which improves base station reliability.
To implement this feature, a base station must be equipped with at least two BBPs
and these two BBPs must be installed in the same BBU.
Macro
In CPRI scenarios, Inter-Board Baseband Resource Redundancy for LTE/NR is only
supported in the inter-board cold backup ring topology and hot backup ring
topology. It is required that baseband equipment not be specified. For details
about the ring topology types supported by LTE and NR, see RF Unit and Topology
Management.
In eCPRI scenarios, if RF modules work in cold backup mode, Inter-Board
Baseband Resource Redundancy for LTE/NR is supported in the intra-board load
sharing topology and inter-board load sharing topology. For details about the load
sharing topology types supported by LTE and NR, see RF Unit and Topology
Management.
In eCPRI scenarios, if RF modules are not in cold backup mode, Inter-Board
Baseband Resource Redundancy for NR is only supported in the inter-board load
sharing topology. It is required that baseband equipment not be specified. For
details about the load sharing topology types supported by NR, see RF Unit and
Topology Management.
The topology type is specified by the RRUCHAIN.TT parameter, and the backup
mode is specified by the RRUCHAIN.BM parameter.
NOTE
The implementation on the gNodeB is the same as that on the eNodeB. The following part
uses the eNodeB as an example.
Figure 7-1 illustrates a 3x10 MHz 2T2R configuration scenario for the eNodeB. In
this scenario, the eNodeB is configured with two LBBP or UBBP(L) boards and the
two BBPs connect to the same RRUs so that an inter-board one-level cold backup
ring topology or hot backup ring topology is formed. If one LBBP or UBBP(L)
board is faulty due to a hardware or communication port fault, the eNodeB can
detect and identify the fault. The impacts of an LBBP or UBBP(L) board failure on
cells served by the faulty board in the following two topologies are different:
● In the inter-board cold backup ring topology, one or more cells served by the
faulty LBBP or UBBP(L) board will be reestablished on another LBBP or
UBBP(L) board that connects to the same RRUs as that connected to the
faulty board.
● In the inter-board hot backup ring topology, the cells served by the faulty
LBBP or UBBP(L) board will be reestablished on the target LBBP or UBBP(L)
board, but will not if the CPRI port is not operational.
The target LBBP or UBBP(L) board is chosen based on the available resources of
all candidate target LBBP or UBBP(L) boards. In Figure 7-1, the blue lines indicate
the communication channels between the source board and RRUs, and the orange
lines indicate the communication channels between the target board and the
RRUs.
NOTICE
An LBBPc board can only work as a backup for another LBBPc board. An LBBPd
board and a UBBP(L) board can work as a backup for each other.
When an LBBP is used, the working mode must be configured by using the
BBP.WM (LTE eNodeB, 5G gNodeB) parameter.
When a UBBP(L) is used, the baseband working mode must be configured by
using the BBP.BBWS (LTE eNodeB, 5G gNodeB) parameter.
LampSite
LampSite base stations support Inter-Board Baseband Resource Redundancy. For
LampSite base stations, if the inter-board trunk chain topology is used and cells
are distributed massive MIMO cells, the UBBPg(NR) boards support Inter-Board
Baseband Resource Redundancy. The topology type is specified by the
RRUCHAIN.TT parameter, and the backup mode is specified by the
RRUCHAIN.BM parameter. For details about support for the inter-board trunk
chain topology in NR, see RF Unit and Topology Management. For details about a
distributed massive MIMO cell, see MIMO (TDD) in 5G RAN Feature
Documentation.
Figure 7-2 shows a one-level inter-board trunk chain dual-fiber topology when
the gNodeB is configured with two UBBPg boards connected to the same RHUBs.
If one UBBPg board is faulty or its communication port is faulty, the gNodeB can
detect and identify the fault. A faulty UBBPg board has the following impacts on
the cells served by it:
● If the communication port is faulty, the base station will attempt to
reestablish and recover the cells through the communication port of the
target UBBPg board that is connected to the same RHUB as the faulty UBBPg
board.
● If the UBBPg board is faulty, the cells will be reestablished on the target
UBBPg board.
The target UBBPg board is chosen based on the available resources of all
candidate target UBBPg boards. Inter-Board Baseband Resource Redundancy is
only supported in single-carrier scenarios. Figure 7-2 shows a scenario where
eight pRRUs, two RHUBs, and two UBBPg boards are used. Each RHUB is
connected to BBPs through two fibers in an inter-board trunk chain topology. The
blue and orange lines indicate the communication channels between RHUBs and
the source and target UBBPg boards, respectively. A carrier of a distributed
massive MIMO cell is configured on the pRRUs.
7.2.1 Benefits
None
7.2.2 Impacts
None
7.3 Requirements
7.3.1 Licenses
None
7.3.2 Software
Prerequisite Functions
RAT Function Name Function Switch Reference
7.3.3 Hardware
Macro
● This feature applies to macro base stations that use the BBU3910, BBU3900,
or BBU5900.
● The eNodeB is configured with two or more LBBP/UBBP boards.
● The gNodeB is configured with two or more UBBP boards.
● An LBBPc board can only work as a backup for another LBBPc board. An
LBBPd board and a UBBP board can work as a backup for each other.
● If the cold backup ring topology is used, there is no requirement on slots for
configuring BBPs. If the BBU3900 and hot backup ring topology are used, the
BBPs must be configured in the slots specified in the following table.
If... Then...
Two UBBP One BBP must be configured in slot 2 or 3, and the other
boards, two BBP can be configured in any slot from slot 0 to slot 5. A
LBBPd boards, maximum of six hot backup rings are supported.
or one LBBPd
and one UBBP
board are to
be configured
LampSite
● This feature applies to LampSite base stations that use the BBU5900.
● The gNodeB is configured with two or more BBPs.
● Both the UBBPg boards and BBPs that support distributed massive MIMO cells
support Inter-Board Baseband Resource Redundancy. For details about BBPs
that support distributed massive MIMO cells, see MIMO (TDD) in 5G RAN
Feature Documentation.
● If the inter-board trunk chain dual-fiber topology is used, there is no
requirement on slots for configuring BBPs.
● The inter-board trunk chain dual-fiber topology supports only one-level
RHUBs.
● The length difference between the two links of the trunk chain must not
exceed 90 m.
● Except for the RHUB592x, RHUB593x, and RHUB39xx, all RHUBs that support
the inter-board trunk chain topology, such as the RHUB596x, support Inter-
Board Baseband Resource Redundancy. For details about support for the inter-
board trunk chain topology, see RF Unit and Topology Management.
● All NR-capable pRRUs, except the pRRU592x, pRRU593x, and pRRU595x,
support Inter-Board Baseband Resource Redundancy.
7.3.4 Others
None
This ensures that services can recover automatically, reduces service interruption
duration, and improves eNodeB/gNodeB reliability.
Table 7-2 describes the key parameters that must be set in the RRUCHAIN MO.
Head RRUCHAIN.HSRN
Subrack (LTE eNodeB, 5G
No. gNodeB)
Head Slot RRUCHAIN.HSN (LTE
No. eNodeB, 5G gNodeB)
Head Port RRUCHAIN.HPN (LTE
No. eNodeB, 5G gNodeB)
Tail RRUCHAIN.TCN (LTE
Cabinet eNodeB, 5G gNodeB)
No.
Tail RRUCHAIN.TSRN
Subrack (LTE eNodeB, 5G
No. gNodeB)
Tail Slot RRUCHAIN.TSN (LTE
No. eNodeB, 5G gNodeB)
Tail Port RRUCHAIN.TPN (LTE
No. eNodeB, 5G gNodeB)
Table 7-3 describes the key parameters that must be set in the RHUB MO for
LampSite base stations.
NOTE
For LampSite scenarios, the configurations of pRRUs in the inter-board trunk chain topology
are the same as those of pRRUs in common topologies. For details about the topologies of
pRRUs in LampSite scenarios, see section "LampSite Branch Chain/Ring Topology" in RF
Unit and Topology Management.
Table 7-4 describes the key parameters that must be set in the RRU MO for
macro base stations.
RRU RRU.PS (LTE eNodeB, In the cold backup ring topology, RRUs
Position 5G gNodeB) should be installed into different positions.
For example, the two RRUs in a second-
level ring should be installed in positions 0
and 1, respectively.
In the hot backup ring topology, the RRU
in a first-level ring should be installed in
position 0.
Before delivery of base stations, the main equipment has been preconfigured.
When MML commands are used to configure base stations, you need to consider
the impact of original main equipment configurations. Before reconfiguring the
base station type and cabinets, query the configurations of the main equipment
by running the LST ENODEBFUNCTION and LST CABINET commands and
remove configurations of all equipment. Remove and add configurations in the
following order:
● Macro
– Configuration removal: RMV CELL (LTE)/RMV NRDUCELL (NR), RMV
SECTOR, MOD RRUCHAIN, RMV RRU, RMV RRUCHAIN, RMV BRD
– Configuration addition: ADD BRD, ADD RRUCHAIN, MOD RRUCHAIN,
ADD RRU, MOD RRUCHAIN
● LampSite
– Configuration removal: RMV NRDUCELL, RMV SECTOR, RMV RRU, RMV
RRUCHAIN, RMV RHUB, RMV RRUCHAIN, RMV BRD
– Configuration addition: ADD BRD, ADD RRUCHAIN, ADD RHUB, ADD
RRUCHAIN, ADD RRU
NOTE
The execution of RMV BRD or ADD BRD may lead to a base station reset.
● In the case of setting up a cell in the hot backup ring topology, set
RRUCHAIN.TT (LTE eNodeB, 5G gNodeB) to RING and RRUCHAIN.BM (LTE
eNodeB, 5G gNodeB) to HOT when configuring the RRU chain/ring.
● In the case of setting up a cell in the load sharing topology, set RRUCHAIN.TT
(LTE eNodeB, 5G gNodeB) to LOADBALANCE when configuring the RRU
chain/ring.
Step 3 Run the MOD RRUCHAIN command to add breakpoints on the RRU ring before
adding the RRU.
Step 5 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after
adding all the RRUs.
----End
In the case of setting up a cell in the cold backup trunk chain topology in
LampSite scenarios, set RRUCHAIN.TT (LTE eNodeB, 5G gNodeB) to
TRUNK_CHAIN and RRUCHAIN.BM (LTE eNodeB, 5G gNodeB) to COLD when
configuring the RRU chain/ring.
Step 4 Run the ADD RRUCHAIN command to add an RHUB branch chain/ring.
----End
NOTE
● To remove an RRU from a ring, you need to interrupt the logical connection between
the RRU or RFU and the BBP. Run the MOD RRUCHAIN command to add two
breakpoints to the ring. The position of the first breakpoint is 0, and the position of the
second breakpoint is the number of RRU cascading levels.
● Deleting main equipment (by running the RMV BRD command) may lead to a base
station reset.
Step 1 Run the RMV CELL (LTE)/RMV NRDUCELL (NR) command to remove the cell.
Step 3 (For macro) Run the MOD RRUCHAIN command to add breakpoints to the RRU
ring before removing the RRU.
Step 5 Run the RMV RRUCHAIN command to remove the RRU ring.
Step 6 (For LampSite) Run the RMV RHUB command to remove the RHUB.
----End
eNodeB (Macro)
RMV CELL: LocalCellId=0;
RMV SECTOR: SECTORID=0;
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=1;
RMV RRU: CN=0, SRN=60, SN=0;
RMV RRUCHAIN: RCN=0;
RMV BRD: CN=0, SRN=0, SN=2;
gNodeB (Macro)
RMV NRDUCELL: NrDuCellId=0;
RMV SECTOR: SECTORID=0;
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=1;
RMV RRU: CN=0, SRN=60, SN=0;
RMV RRUCHAIN: RCN=0;
RMV BRD: CN=0, SRN=0, SN=2;
gNodeB (LampSite)
RMV NRDUCELL: NrDuCellId=0;
RMV SECTOR: SECTORID=0;
RMV RRU: CN=0, SRN=61, SN=0;
RMV RRUCHAIN: RCN=61;
RMV RHUB: CN=0, SRN=60, SN=0;
RMV RRUCHAIN: RCN=0;
RMV BRD: CN=0, SRN=0, SN=2;
(For macro) The implementation method on the gNodeB is the same as that on the
eNodeB. The following part uses the eNodeB as an example.
If the parameter values and operation results are the same as those in the
preceding steps, and the cell has been reestablished on another BBP, this feature
has taken effect and cell reestablishment has succeeded.
----End
Run the DSP CELL command to check the information about a cell. If Cell
instance state is Normal, the cell has been activated. Then, check the value of
Primary BBP information to identify the BBP on which the cell is established.
If the UEs can successfully access the cell and the data rates of the UDP services
are stable, the cell is functional.
Run the BLK CPRIPORT command to block the CPRI port on which the cell is
established. Alternatively, remove the CPRI optical fiber from the BBP to trigger
the cell to use a CPRI port on another BBP. It can be observed that the cell
reestablishment is not triggered but the UEs can still retain their connections, and
the UDP data rates do not fluctuate greatly.
Run the DSP CELL command to check the information about a cell. If Cell
instance state is Normal, the cell has been activated. Check the value of Primary
BBP information to determine the BBP on which the cell is currently established.
If the BBP on which the cell is established remains unchanged, this feature has
taken effect.
NOTE
When hot backup fails due to insufficient resources, cold backup starts. In this case, UEs
served by the cell are released and the cell is reestablished on another BBP.
----End
Run the DSP CELL command to check the information about a cell. If Cell
instance state is Normal, the cell has been activated. Then, check the value of
Primary BBP information to identify the BBP on which the cell is established.
NOTE
If the new BBP does not have idle resources, cell reestablishment cannot be triggered.
----End
Step 1 In the topology view on the MAE, check whether each RHUB is connected to the
active and standby BBPs through two optical fibers. LampSite inter-board
baseband resource redundancy requires that each RHUB connects to the active
and standby BBPs through two optical fibers.
Step 2 Check the baseband equipment ID of the cell.
Run the LST NRDUCELLTRP command and check whether the value of Baseband
Equipment ID in the command output is 255. If the value is 255, the baseband
equipment used by the cell is unspecified. LampSite inter-board baseband resource
redundancy does not require a specified baseband equipment.
Run the LST GNODEBPARAM command and check whether Auto Cell Bind
Baseband Equipment Switch is set to OFF. If not, run the MOD GNODEBPARAM
command and change the value to OFF.
Step 3 Check the status of the cell.
Run the DSP NRDUCELL command to check the information about a cell. If the
value of NR DU Cell State is Normal, the cell has been activated.
Step 4 Check the serving BBP information of the cell.
Run the DSP NRDUCELLANTENNA command to check the information about the
serving BBP indicated by the value of Served BBP Information.
Step 5 Check whether the cell is functional.
If the UEs can successfully access the cell, the cell is functional.
----End
8.1 Principles
When Inter-BBP Active/Standby Backup is enabled, the base station configures the
active and standby relationship for two BBPs serving the same cell. In this case,
the cell can recover quickly when a BBP is faulty, which improves base station
reliability. Assuming that a cell is served by two BBPs configured with the active
and standby relationship and the primary BBP becomes faulty, the gNodeB quickly
detects the fault and triggers a cell switchover. The cell is then reestablished on
the secondary BBP.
To implement this function, a base station must be equipped with an even number
of BBPs and these BBPs must be installed in the same BBU.
In LampSite scenarios, Inter-BBP Active/Standby Backup takes effect when all of
the following conditions are met:
● The cell is a distributed massive MIMO cell.
● The inter-board trunk chain topology is used.
● The BBP is configured to work in NR mode.
The inter-board trunk chain topology is specified by the RRUCHAIN.TT parameter,
and the backup mode is specified by the RRUCHAIN.BM parameter. For details
about support for the inter-board trunk chain topology in NR, see RF Unit and
Topology Management. For details about a distributed massive MIMO cell, see
MIMO (TDD) in 5G RAN Feature Documentation.
The primary and secondary BBPs are specified when the master transmission
reception point (TRP) of a distributed massive MIMO cell served by a pRRU is
configured using the NRDUCellTrp MO to implement Inter-BBP Active/Standby
Backup. When the NRDUCellTrp.TrpType parameter is set to MASTER_DM_MIMO
for a TRP, this TRP is the master TRP for a distributed massive MIMO cell. The
primary and secondary BBPs are specified by the NRDUCellTrp.BasebandEqmId
and NRDUCellTrp.SecondaryBasebandEqmId parameters, respectively. When the
NRDUCellTrp.TrpType parameter is set to SLAVE for a TRP, this TRP is a slave TRP.
Primary and secondary BBPs cannot be configured for the TRP. A distributed
massive MIMO cell can be configured with only one master TRP and multiple
slave TRPs.
To implement Inter-BBP Active/Standby Backup, specifications of both the primary
and secondary BBPs must meet the configuration requirements of the
corresponding distributed massive MIMO cell. Otherwise, the switchover may fail.
Inter-BBP Active/Standby Backup can be applied to single-carrier and dual-carrier
scenarios.
● Figure 8-1 shows a single-carrier scenario where eight pRRUs, two RHUBs,
and two UBBPg(NR) boards are used. Each RHUB is connected to BBPs
through two fibers in an inter-board trunk chain topology. The blue and
orange lines indicate the communication channels between RHUBs and the
primary and secondary BBPs, respectively. A carrier of a distributed massive
MIMO cell is configured on the pRRUs. A distributed massive MIMO cell
supports a maximum of 16 TRPs, and requires two UBBPg(NR) boards. The
NRDUCellTrp MO is used to configure the master TRP for the distributed
massive MIMO cell on a pRRU, as well as the active and standby relationship
between the two UBBPg(NR) boards.
● Figure 8-2 shows a dual-carrier scenario where eight pRRUs, four RHUBs, and
four UBBPg(NR) boards are used. Each RHUB is connected to BBPs through
two fibers in an inter-board trunk chain topology. The blue and orange lines
indicate the communication channels between RHUBs and the primary and
secondary BBPs, respectively. Carriers of two distributed massive MIMO cells
are configured on the pRRUs. A distributed massive MIMO cell supports a
maximum of eight TRPs, and requires two UBBPg(NR) boards. The
NRDUCellTrp MO is used to configure the master TRP for each distributed
massive MIMO cell on a pRRU, as well as the active and standby relationship
between the two UBBPg(NR) boards for each distributed massive MIMO cell.
Each cell is configured with a primary BBP and a secondary BBP, and the cell is
preferentially deployed on the primary BBP.
When the primary BBP for a distributed massive MIMO cell or an optical fiber
connected to the BBP is faulty , the gNodeB quickly detects the fault and triggers
a cell switchover.
After the switchover, the cell is always deployed on the secondary BBP, even when
the base station is reset and a cell reestablishment is required. To deploy the cell
on the primary BBP, you need to manually trigger the cell reestablishment.
8.2.1 Benefits
When services of a cell are affected due to a BBP fault, the gNodeB can use the
Inter-BBP Active/Standby Backup function to quickly reestablish the cell on
another BBP.
8.2.2 Impacts
None
8.3 Requirements
8.3.1 Licenses
None
8.3.2 Software
Prerequisite Functions
RAT Function Name Function Switch Reference
8.3.3 Hardware
● This feature applies to LampSite base stations that use the BBU5900.
● The gNodeB must be configured with an even number of BBPs. The models of
primary and secondary BBPs must be the same.
● Both the UBBPg boards and BBPs that support distributed massive MIMO cells
support Inter-BBP Active/Standby Backup. For details about BBPs that support
distributed massive MIMO cells, see MIMO (TDD) in 5G RAN Feature
Documentation.
● If the inter-board trunk chain dual-fiber topology is used, there is no
requirement on slots for configuring BBPs.
● The inter-board trunk chain dual-fiber topology supports only one-level
RHUBs.
● The length difference between the two fibers connected to the same RHUB
must not exceed 90 m.
● Except for the RHUB592x, RHUB593x, and RHUB39xx, all RHUBs that support
the inter-board trunk chain topology support Inter-BBP Active/Standby
Backup. For details about support for the inter-board trunk chain topology,
see RF Unit and Topology Management.
● All NR-capable pRRUs, except the pRRU592x, pRRU593x, and pRRU595x,
support Inter-BBP Active/Standby Backup.
8.3.4 Others
None
Table 8-2 describes the key parameters that must be set in the NRDUCellTrp MO
to bind secondary baseband equipment.
Table 8-3 describes the key parameters that must be set in an RRUCHAIN MO.
Step 2 Run the ADD RRUCHAIN, ADD RHUB, and ADD RRU commands to add main and
branch chains, RHUBs, and pRRUs, respectively.
//Adding main chains with Topo Type set to TRUNK_CHAIN
ADD RRUCHAIN: RCN=0, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=2, CONNSN1=1,
CONNPN1=0, CONNSN2=3, CONNPN2=0;
ADD RRUCHAIN: RCN=1, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=2, CONNSN1=1,
CONNPN1=1, CONNSN2=3, CONNPN2=1;
//Adding RHUBs
ADD RHUB: CN=0, SRN=60, SN=0, RCN=0, PS=0;
ADD RHUB: CN=0, SRN=70, SN=0, RCN=1, PS=0;
//Adding branch chains with Topo Type set to TRUNK_CHAIN and Backup Mode set to COLD
ADD RRUCHAIN: RCN=61, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=62, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=71, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=6;
ADD RRUCHAIN: RCN=72, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=7;
//Adding pRRUs
ADD RRU: CN=0, SRN=61, SN=0, TP=BRANCH, RCN=61, PS=0, RT=MPMU, RS=LN, RXNUM=4, TXNUM=4;
ADD RRU: CN=0, SRN=62, SN=0, TP=BRANCH, RCN=62, PS=0, RT=MPMU, RS=LN, RXNUM=4, TXNUM=4;
ADD RRU: CN=0, SRN=71, SN=0, TP=BRANCH, RCN=71, PS=0, RT=MPMU, RS=LN, RXNUM=4, TXNUM=4;
ADD RRU: CN=0, SRN=72, SN=0, TP=BRANCH, RCN=72, PS=0, RT=MPMU, RS=LN, RXNUM=4, TXNUM=4;
Step 3 Run the ADD BASEBANDEQM command to add the baseband equipment.
ADD BASEBANDEQM: BASEBANDEQMID=1, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=1;
ADD BASEBANDEQM: BASEBANDEQMID=3, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
Step 4 Run the ADD SECTOR and ADD NRDUCELL commands to add sectors and NR DU
cells.
//Adding sectors
ADD SECTOR: SECTORID=61, SECNAME="sector-61", ANTNUM=4, ANT1CN=0, ANT1SRN=61, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=61, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=61, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE,
SECTOREQMID=61;
ADD SECTOR: SECTORID=62, SECNAME="sector-62", ANTNUM=4, ANT1CN=0, ANT1SRN=62, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=62, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=62, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=62, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE,
SECTOREQMID=62;
ADD SECTOR: SECTORID=71, SECNAME="sector-71", ANTNUM=4, ANT1CN=0, ANT1SRN=71, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=71, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=71, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=71, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE,
SECTOREQMID=71;
ADD SECTOR: SECTORID=72, SECNAME="sector-72", ANTNUM=4, ANT1CN=0, ANT1SRN=72, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=72, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=72, ANT3SN=0,
Step 6 Run the ADD NRDUCELLCOVERAGE and ADD NRCELL commands to add NR DU
cell coverage areas and an NR cell.
//Adding NR DU cell coverage areas
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=0, NrDuCellCoverageId=61, SectorEqmId=61;
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=1, NrDuCellCoverageId=62, SectorEqmId=62;
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=2, NrDuCellCoverageId=71, SectorEqmId=71;
ADD NRDUCELLCOVERAGE: NrDuCellTrpId=3, NrDuCellCoverageId=72, SectorEqmId=72;
//Adding an NR cell
ADD NRCELL: NrCellId=0, CellName="2.6G_100M_8:2", CellId=0, FrequencyBand=N41,
DuplexMode=CELL_TDD;
----End
----End
----End
----End
9.1 Principles
When an RF module is faulty, the cells served by this faulty module will be
affected. When two RF modules are configured in a base station to cover the
same area, Cold Backup of RF Modules enables the cells or carriers served by the
master RF module to be reestablished and served by the backup RF module when
the master RF module is faulty. The base station services can be recovered within
3 minutes, improving base station reliability. If cells are successfully reestablished,
EVT-29904 NR DU Cell TRP RF Unit Switchover will be reported. Currently, only 1:1
backup of AAUs using eCPRI is supported when the SECTOREQM.ANTCFGMODE
parameter is set to BEAM in low-frequency NR TDD scenarios.
When both master and backup RF modules are available, the master RF module is
preferentially used to serve the cells. When only one of the master and backup RF
modules is available, cells are served by the available RF module. If the master RF
module changes from unavailable to available, the base station will not
proactively trigger reestablishments for cells served by the backup RF module and
change the serving RF module to the master RF module. Cells are reestablished
and preferentially served by the master RF module only when the base station is
upgraded or reset. Figure 9-1 and Figure 9-2 show the recommended topologies
for this function.
9.2.1 Benefits
None
9.2.2 Impacts
None
9.3 Requirements
9.3.1 Licenses
None
9.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
None
9.3.3 Hardware
Only NR TDD-only AAUs support this function.
The models of the master and backup AAUs must be the same.
9.3.4 Others
None
Table 9-1 Configuration parameters that must be set for the master and backup
RF modules
Table 9-2 describes the configuration parameters that must be set in the
SECTOREQM MO.
Table 9-2 Configuration parameters that must be set for the master AAU sector
equipment
Paramete Parameter ID Setting Notes
r Name
Step 2 Run the MOD RRUCHAIN and ADD RRU commands to add the master and
backup AAUs.
MOD RRUCHAIN: RCN=10, BRKPOS1=0, BRKPOS2=0;
MOD RRUCHAIN: RCN=11, BRKPOS1=0, BRKPOS2=0;
ADD RRU: CN=0, SRN=80, SN=0, TP=TRUNK, RCN=10, PS=0, RT=AIRU, RS=NO, RXNUM=64, TXNUM=64,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF, DORMANCYSW=OFF;
ADD RRU: CN=0, SRN=81, SN=0, TP=TRUNK, RCN=11, PS=0, RT=AIRU, RS=NO, RXNUM=64, TXNUM=64,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF, RFTXSIGNDETECTSW=OFF, DORMANCYSW=OFF;
MOD RRUCHAIN: RCN=10, BRKPOS1=255, BRKPOS2=255;
MOD RRUCHAIN: RCN=11, BRKPOS1=255, BRKPOS2=255;
NOTE
Ensure that the coverage area of the backup AAU is the same as that of the master AAU
(by adjusting the mechanical tilts of the master and backup AAUs).
Step 3 Run the ADD RFHAGRP command to add an RF HA group. Specify the master and
backup RF modules.
Step 4 Run the ADD SECTOR command to add the master AAU sector.
ADD SECTOR: SECTORID=80, SECNAME="80", LOCATIONNAME="80", USERLABEL="80", ANTNUM=0,
CREATESECTOREQM=FALSE;
Step 5 Run the ADD SECTOREQM command to add the master AAU sector equipment.
ADD SECTOREQM: SECTOREQMID=80, SECTORID=80, ANTCFGMODE=BEAM, RRUCN=0, RRUSRN=80,
RRUSN=0, BEAMSHAPE=SEC_120DEG, BEAMLAYERSPLIT=None, BEAMAZIMUTHOFFSET=None;
----End
Step 2 Run the MOD RRUCHAIN and RMV RRU commands to remove the backup AAU.
MOD RRUCHAIN: RCN=11, BRKPOS1=0, BRKPOS2=1;
RMV RRU: CN=0, SRN=81, SN=0;
Step 3 Run the RMV RRUCHAIN command to remove the backup AAU chain/ring.
RMV RRUCHAIN: RCN=11;
----End
----End
10.1 Principles
10.1.1 Overview
A single BBP forms a resource pool of processing capabilities. Services of cells or
carriers are evenly deployed on a BBP according to the processing capabilities of
each processing unit and traffic volume. That is, processing resources are
aggregated into a resource pool and shared by user data of multiple cells or
carriers. If a processing unit is faulty, services carried on the processing unit are
interrupted and then reestablished on other processing units with available
resources. If a processing unit is overloaded or the resources for the processing
unit are exhausted, the base station can transfer users on the processing resource
to other resources. This improves system reliability.
For UMTS, when a BBP allocates several resources to a single cell for load sharing,
the common processing parts of the cell can use only one resource. If this resource
fails, the cells served by this resource can be reestablished on other normal
processing resources within 20s. This ensures service recovery.
If a BBP in a NodeB provides multiple processing resources for one cell, multiple
UEs that attempt to access the cell can share these processing resources. However,
a single UE can use only one processing resource. After accessing the cell
successfully, the UE can use other resources on the BBP if the UE attribute must be
modified.
10.2.1 Benefits
None
10.2.2 Impacts
None
10.3 Requirements
10.3.1 Licenses
None
10.3.2 Software
None
10.3.3 Hardware
The feature described in this document is implemented in the same way on macro
base stations and LampSite base stations.
10.3.4 Others
None
10.4.2 Precautions
None
NOTE
If any hardware unit on the BBP is faulty, ALM-26200 Board Hardware Fault will be
reported. Intra-Board Resource Pool recovers services only when the DSP chip is faulty but
not in all hardware fault scenarios.
Step 1 Run the DSP CELL command to check the information about a cell.
If Cell instance state is Normal, the cell has been activated. The command
output shows that only one BBP serves the cell.
Step 2 Check whether the cell is functional.
If the UEs can successfully access the cell, the cell is functional.
----End
11.1 Principles
Table 11-1 Enhanced power supply for Huawei AC-powered base stations
equipped with the PMU
Function Feature ID and Name Description
For details about the principles and engineering guidelines for the functions of
intelligent battery management, automatic battery and load disconnection, and
intelligent diesel generator management, see Power Supply Management.
Hiccup protection mode: When a power board experiences a fault that may damage itself,
the power board stops supplying power and at the same time continues detecting whether
the fault is rectified. Once the fault is rectified, the power board resumes the power supply.
● Sound power consumption management for BBU boards
– When the power supply capability of power boards in the BBU is
insufficient because of board expansion or power board failure, the BBPs
with a low power-on priority are powered off, preventing power overload
in the BBU.
– After a BBU is restarted due to insufficient power supply, the BBU
attempts to power on the BBPs after it is powered on again. If the BBU is
restarted for a second time due to insufficient power supply after
powering on BBPs, some BBPs will not be powered on after the BBU is
powered on for the third time. This ensures the power supply to other
boards in the BBU.
Power supply reliability for a BBU is a basic function and does not require any
software configuration.
11.2.1 Benefits
None
11.2.2 Impacts
None
11.3 Requirements
11.3.1 Licenses
None
11.3.2 Software
None
11.3.3 Hardware
● The PMU and PSU must be provided by Huawei.
● For details about how to install the PMU and PSU, see the section related to
monitoring signal cable installation in the base station-specific installation
guide.
11.3.4 Others
None
Table 11-3 describes the parameter that must be set for activating this feature in
an eGBTS, NodeB, or eNodeB.
Table 11-3 Parameter for activating this feature in an eGBTS, NodeB, or eNodeB
Parameter Parameter ID Description
Name
eGBTS/NodeB/eNodeB
Run the SET EQUIPMENT command to enable the Intelligent Shutdown of TRX
Due to PSU Failure feature. In this step, set PSU Fault Shutdown TRX Enabled to
ON(ON).
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=ON;
eGBTS/NodeB/eNodeB
Run the SET EQUIPMENT command to disable the Intelligent Shutdown of TRX
Due to PSU Failure feature. In this step, set PSU Fault Shutdown TRX Enabled to
OFF(OFF).
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=OFF;
Expected result: Some channels on TRXs are available and some are not. The site
works properly and is not powered off due to insufficient power supply.
----End
eGBTS/NodeB/eNodeB
Step 1 Run the LST EQUIPMENT command to verify that the value of PSU Fault
Shutdown TRX Enabled is ON(ON).
Step 2 Use a power meter to test the power of the BCCH TRX and record the result.
Step 3 Remove one PSU from the base stations so that the power of all TRXs is halved.
Step 4 Use the power meter to test the power of the BCCH TRX.
Expected result: The power of the BCCH TRX is half of that tested in Step 2.
----End
12 Other Functions
The features described in this document are implemented in the same way on
macro base stations and LampSite base stations.
Table 12-1 describes the features involved in RF Channel Cooperation. For details
about these features, see the corresponding feature parameter description.
is faulty, heat dissipation will be affected. Fans do not support redundancy design
in hardware due to inconvenient installation. To ensure adequate heat dissipation,
the following functions are provided:
● When the FMU works in smart temperature control mode, the FMU adjusts
the rotation speed of fans based on the temperature control parameters
delivered by the BBU. If a fan becomes faulty, ALM-25673 Fan Stalled is
reported and the policy for adjusting the rotation speed of other fans remains
unchanged.
● When the FMU works in temperature control mode and cannot obtain the
temperature information of the equipment, the FMU adjusts the rotation
speed of fans based on the ambient temperature. If a fan becomes faulty,
ALM-25673 Fan Stalled is reported and other fans in the same fan group
rotate at full speed to ensure heat dissipation.
● When the TCU cannot obtain the temperature at the air exhaust vent of the
cabinet, fans in the TCU rotate at full speed. If a fan becomes faulty,
ALM-25673 Fan Stalled is reported and other fans in the same fan group
rotate at full speed to ensure heat dissipation.
● When a fan in the FAN unit of the BBU becomes faulty, ALM-26110 BBU Fan
Stalled and ALM-26111 BBU Fan Not at Full Speed are reported and other
fans rotate at full speed to ensure heat dissipation.
NOTE
If only one fan in the BBU5900A is stalled and there is no ambient overtemperature
risk, fans that are not stalled do not rotate at full speed. Instead, the rotation speed of
the fans is adjusted based on the temperature control mode (specified by the
TCU.TCMODE (5G gNodeB, LTE eNodeB) parameter).
● When the control signals for a fan in the FMU or TCU are unavailable, the fan
in the FMU or TCU rotates at full speed.
● When ALM-26101 Inter-Board CANBUS Communication Failure is reported,
fans in the BBU rotate at full speed.
Currently, only the UPEUe, UPEUc, or UPEUd board can work in 1+1 backup mode.
When the configured power consumption exceeds the power supply capability of a
UPEU board, 1+1 backup mode is not supported.
In the normal working state, the two power boards share the power load. When a
power board becomes faulty, the power load on the faulty board automatically
switches to the other board, avoiding service interruption.
To work in 1+1 backup mode, power boards in the BBU must meet the following
requirements:
● Each power board can undertake the power load of the whole BBU.
● The two power boards are of the same type and have the same specifications.
Power Supply Redundancy for a BBU is a basic function and does not require any
software configurations.
The GSM, UMTS, LTE, and NR base stations support this feature by default. This
feature has no independent feature ID. For the principles and engineering
guidelines, see sections "Reporting of ALM-25636 Loss of Power Supply
Redundancy" and "Deployment of Reporting of ALM-25636 Loss of Power Supply
Redundancy" in Power Supply Management.
Power-off Requirements
● The main control board powers off a non-main-control board and reports
ALM-26214 Board Powered Off when any of the following conditions is met: a
minor overtemperature alarm exists on the non-main-control board for more
than 24 hours, a severe overtemperature alarm exists on the non-main-
control board for more than one hour, or the temperature of the non-main-
control board is higher than the overtemperature power-off threshold.
NOTE
When a minor overtemperature alarm exists on the main control board for more than 2
minutes, the main control board powers off the WBBPb and reports ALM-26214 Board
Powered Off.
Power-on Requirements
The overtemperature alarm reported on a non-main-control board can be
manually or automatically cleared only when the main control board is not
powered off due to overtemperature.
● Automatic mode: When the main control board detects that the temperature
of a non-main-control board meets the alarm clearing threshold, the
overtemperature alarm is automatically cleared. If the non-main-control
board has been powered-off in this case, the main control board powers on
the non-main-control board. The requirements for automatically clearing the
overtemperature alarm or powering on a non-main-control board are as
follows:
– The fans are working properly and ALM-26110 BBU Fan Stalled is not
reported.
– The temperature of the non-main-control board is 5°C lower than the
threshold for a minor overtemperature alarm.
– No severe overtemperature alarm exists on the main control board.
– More than 10 minutes have elapsed since the non-main-control board
has been powered off.
● Manual mode: Users can deliver an MML command to forcibly power on a
non-main-control board. In this case, the reported alarms will not be cleared
unless the conditions for automatically clearing the alarm are met. If the
temperature of the non-main-control board is higher than the
overtemperature power-off threshold after it is forcibly powered on, the main
control board will power off the non-main-control board again. Otherwise,
the non-main-control board will stay in powered-on status.
this case, all baseband processing units in the BBU subrack are powered off. The
main control board powers off itself in the following situations:
● If the temperature of the main control board is higher than the severe
overtemperature alarm threshold for more than one hour, the main control
board reports ALM-26214 Board Powered Off, powers off all boards except
itself and the baseband processing units in the BBU subrack, and then powers
off itself.
● If the temperature of the main control board is higher than the
overtemperature power-off threshold, the main control board reports
ALM-26214 Board Powered Off and powers off itself.
Power-on Requirements
If a main control board is powered off due to overtemperature, users must
troubleshoot the fault onsite and then power on the main control board.
12.6.1 Standards
No. File Code File Name
13 Glossary
14 Reference Documents
1. TRX Cooperation
2. RRU Redundancy
3. 3900 & 5900 Series Base Station Initial Configuration Guide
4. Power Supply Management
5. Cell Management
6. RF Unit and Topology Management
7. 3900 & 5900 Series Base Station Commissioning Guide
8. Transmission Security Overview
9. 3900 & 5900 Series Base Station Technical Description
10. GSM and LTE Dynamic Power Sharing
11. Multi-RAT Coordinated Energy Saving
12. MIMO (TDD)
13. Energy Conservation and Emission Reduction