Base Station Equipment Reliability (SRAN10.1 - 02)

SingleRAN
Base Station Equipment Reliability

Feature Parameter Description
Issue 02
Date 2016-04-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2016-04-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 2
2 Overview......................................................................................................................................... 3
3 Redundancy Design...................................................................................................................... 8
3.1 RF Channel Cooperation................................................................................................................................................ 8
3.2 RRU Channel Cross Connection Under MIMO.............................................................................................................8
4 Hardware Reliability.................................................................................................................. 10
4.1 Cold Backup of Main Control Boards.......................................................................................................................... 10
4.1.1 Overview................................................................................................................................................................... 10
4.1.2 Active/Standby Competition......................................................................................................................................11
4.1.3 Data Backup...............................................................................................................................................................11
4.1.4 Active/Standby Switchover....................................................................................................................................... 11
4.2 Inter-Board Baseband Resource Redundancy.............................................................................................................. 13
4.3 Intra-Board Baseband Resource Pool...........................................................................................................................15
4.3.1 Overview................................................................................................................................................................... 15
4.3.2 Intra-Board Cell-Level Resource Pool...................................................................................................................... 16
4.3.3 Intra-Board User-Level Resource Pool..................................................................................................................... 17
4.4 Heat Dissipation Reliability for Fans........................................................................................................................... 17
4.5 Power Supply Redundancy...........................................................................................................................................18
4.5.1 Power Supply Redundancy for a Base Station.......................................................................................................... 18
4.5.2 Power Supply Redundancy for a BBU...................................................................................................................... 18
4.6 Power Supply Reliability..............................................................................................................................................18
4.6.1 Power Supply Reliability for a Base Station............................................................................................................. 19
4.6.2 Power Supply Reliability for a BBU......................................................................................................................... 20
4.7 Anti-Misinsertion Design of Boards.............................................................................................................................21
4.8 Overtemperature Protection for BBU Boards.............................................................................................................. 22
4.8.1 Overtemperature Power-Off for Non-Main-Control Boards..................................................................................... 22
4.8.2 Overtemperature Power-Off for Main Control Boards..............................................................................................23
4.9 Surge Protection Design............................................................................................................................................... 23
Issue 02 (2016-04-30) Huawei Proprietary and Confidential ii

SingleRAN
4.9.1 Standards................................................................................................................................................................... 23
4.9.2 Surge Protection Capability of Different Ports..........................................................................................................24
5 Related Features...........................................................................................................................26
6 Network Impact........................................................................................................................... 27
7 Engineering Guidelines for RRU Channel Cross Connection Under MIMO.................28
7.1 When to Use RRU Channel Cross Connection Under MIMO..................................................................................... 28
7.2 Required Information................................................................................................................................................... 28
7.3 Planning........................................................................................................................................................................ 28
7.4 Deployment.................................................................................................................................................................. 29
7.4.1 Requirements............................................................................................................................................................. 29
7.4.2 Data Preparation........................................................................................................................................................ 29
7.4.3 Precautions.................................................................................................................................................................30
7.4.4 Hardware Adjustment................................................................................................................................................30
7.4.5 Activation.................................................................................................................................................................. 30
7.4.6 Activation Observation..............................................................................................................................................32
7.4.7 Deactivation...............................................................................................................................................................32
7.4.8 Reconfiguration......................................................................................................................................................... 33
7.5 Performance Monitoring...............................................................................................................................................33
7.6 Parameter Optimization................................................................................................................................................ 33
7.7 Troubleshooting............................................................................................................................................................ 33
8 Engineering Guidelines for Cold Backup of Main Control Boards.................................. 35

8.1 When to Use Cold Backup of Main Control Boards.................................................................................................... 35
8.3 Planning........................................................................................................................................................................ 35
8.4 Deployment.................................................................................................................................................................. 37
8.4.1 Requirements............................................................................................................................................................. 37
8.4.3 Precautions.................................................................................................................................................................38
8.4.5 Activation.................................................................................................................................................................. 39
8.4.6 Commissioning.......................................................................................................................................................... 41
8.4.8 Deactivation...............................................................................................................................................................43
9 Engineering Guidelines for Inter-Board Baseband Resource Redundancy

(GSM&UMTS)................................................................................................................................ 45
9.1 When to Use Inter-Board Baseband Resource Redundancy (GSM&UMTS)..............................................................45
Issue 02 (2016-04-30) Huawei Proprietary and Confidential iii

SingleRAN
9.3 Planning........................................................................................................................................................................ 45
9.4 Deployment.................................................................................................................................................................. 46
9.4.1 Requirements............................................................................................................................................................. 46
9.4.3 Precautions.................................................................................................................................................................48
9.4.5 Activation.................................................................................................................................................................. 48
9.4.7 Deactivation...............................................................................................................................................................49
10 Engineering Guidelines for Inter-Board Baseband Resource Redundancy (LTE)....... 51

10.1 When to Use Inter-Board Baseband Resource Redundancy (LTE)............................................................................51
10.2 Required Information................................................................................................................................................. 51
10.3 Planning...................................................................................................................................................................... 52
10.4 Deployment................................................................................................................................................................ 52
10.4.1 Requirements........................................................................................................................................................... 53
10.4.2 Data Preparation...................................................................................................................................................... 53
10.4.3 Precautions...............................................................................................................................................................55
10.4.4 Hardware Adjustment..............................................................................................................................................55
10.4.5 Activation................................................................................................................................................................ 56
10.4.6 Activation Observation............................................................................................................................................58
10.4.7 Deactivation.............................................................................................................................................................59
10.4.8 Reconfiguration....................................................................................................................................................... 60
10.5 Performance Monitoring.............................................................................................................................................60
10.6 Parameter Optimization.............................................................................................................................................. 60
10.7 Troubleshooting.......................................................................................................................................................... 60
11 Engineering Guidelines for Intra-Board Baseband Resource Pool (LTE)...................... 62

11.1 When to Use Intra-Board Baseband Resource Pool (LTE)........................................................................................ 62
11.2 Required Information..................................................................................................................................................62
11.3 Planning...................................................................................................................................................................... 62
11.4 Deployment.................................................................................................................................................................62
11.4.1 Requirements........................................................................................................................................................... 63
11.4.3 Precautions...............................................................................................................................................................63
11.4.4 Hardware Adjustment.............................................................................................................................................. 63
11.4.5 Activation.................................................................................................................................................................63
11.4.6 Activation Observation............................................................................................................................................ 63
11.4.7 Deactivation............................................................................................................................................................. 64
Issue 02 (2016-04-30) Huawei Proprietary and Confidential iv

SingleRAN

12 Engineering Guidelines for Intelligent Shutdown of Carriers Due to PSU Failure....65

12.1 When to Use Intelligent Shutdown of Carriers Due to PSU Failure.......................................................................... 65
12.2 Required Information................................................................................................................................................. 65
12.3 Planning...................................................................................................................................................................... 65
12.4 Deployment................................................................................................................................................................ 65
12.4.1 Requirements........................................................................................................................................................... 66
12.4.3 Precautions...............................................................................................................................................................67
12.4.4 Hardware Adjustment..............................................................................................................................................67
12.4.5 Activation................................................................................................................................................................ 67
12.4.6 Activation Observation............................................................................................................................................68
12.4.7 Deactivation.............................................................................................................................................................69
13 Parameters................................................................................................................................... 71
14 Counters...................................................................................................................................... 81
15 Glossary....................................................................................................................................... 82
16 Reference Documents............................................................................................................... 83
Issue 02 (2016-04-30) Huawei Proprietary and Confidential v

SingleRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the reliability design of base station equipment, including its related
features, network impact, and engineering guidelines. The reliability design includes the
redundancy design and hardware reliability design.
The base stations mentioned in this document refer to macro base stations (including
BTS3900, BTS3900L, BTS3900A, BTS3900AL, BTS3900C, and DBS3900) and LampSite
base stations.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
In this document, LTE is used where LTE TDD does not need to be distinguished from LTE
FDD. In scenarios where LTE TDD needs to be distinguished from LTE FDD, LTE TDD and
LTE FDD are used. The same rules apply to eNodeB.
Abbreviations G, U, L, and T in this document stand for GSM, UMTS, LTE FDD, and LTE
TDD, respectively.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
Issue 02 (2016-04-30) Huawei Proprietary and Confidential 1

SingleRAN
Description 1 About This Document
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN10.1 02 (2016-04-30)
This issue includes the following changes.
Change Type Change Description Parameter Change
Feature change None None
Editorial change Modified some descriptions in None

section Inter-Board Baseband
Resource Redundancy for LTE
of 4.2 Inter-Board Baseband
Resource Redundancy. Added
the description of the difference
between the impact of an LBBP/
UBBPd_L board failure on cells
served by the failed board in
inter-board cold backup ring
topology and the impact of the
board failure in hot backup ring
topology.
SRAN10.1 01 (2015-03-23)
This issue includes no any changes.
SRAN10.1 Draft A (2015-01-15)

Compared with Issue 02 (2014-06-30) of SRAN9.0, Draft A (2015-01-15) of SRAN10.1
includes the following changes.
Change Type Change Description Parameter Change
Feature change Added the description as follows: None

eGBTS(GTMUb) does not
support Cold Backup of Main
Control Boards feature. For
details, see 2 Overview.
Editorial change None None
1.4 Differences Between Base Station Types

The features described in this document are implemented in the same way on macro base
stations and LampSite base stations.

SingleRAN
Description 2 Overview
2 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 2-1 describes the base station equipment reliability features/functions supported by
each mode. In this table, "Y" means "supported" and "N" means "not supported."
Table 2-1 Base station equipment reliability features/functions supported by each mode
Reliabil Feature/Function Whether This Feature/Function Description
ity Type Is Supported
G U L T
Redund RF Channel GBTS: Y Y N N For details, see section

ancy Cooperation eGBTS: Y 3.1 RF Channel
design Cooperation.
For details about the
principles and
engineering guidelines
for the GBTS and
eGBTS, see TRX
Cooperation Feature
Parameter Description.
principles and
for the NodeB, see RRU
Redundancy Feature

SingleRAN
RRU Channel GBTS: N N Y N For details about the

Cross eGBTS: N principles and the
Connection engineering guidelines
Under MIMO for RRU Channel Cross
Connection Under
MIMO, see section 3.2
RRU Channel Cross
Connection Under
MIMO and chapter 7
Engineering Guidelines
for RRU Channel
Cross Connection
Under MIMO,
respectively.
Hardwa Cold Backup of GBTS: N Y Y N For details about the

re Main Control eGBTS(G principles and the
reliabili Boards TMUb): N engineering guidelines
ty for Cold Backup of Main
eGBTS(U Control Boards, see
MPT): Y section 4.1 Cold Backup
of Main Control
Boards and chapter 8
Engineering Guidelines
for Cold Backup of
Main Control Boards.
Inter-Board GBTS: Y Y Y Y For details about the

Baseband eGBTS: Y principles of Inter-Board
Resource Baseband Resource
Redundancy Redundancy, see section
4.2 Inter-Board
Baseband Resource
Redundancy.
for the GBTS, eGBTS,
and NodeB, see chapter
9 Engineering
Guidelines for Inter-
Board Baseband
Resource Redundancy
(GSM&UMTS).
for the eNodeB, see
chapter 10 Engineering
Guidelines for Inter-
Board Baseband
Resource Redundancy
(LTE).

SingleRAN
Intra-Board GBTS: Y Y Y Y For details about the

Baseband eGBTS: Y principles of Intra-Board
Resource Pool Baseband Resource Pool,
see section 4.3 Intra-
Board Baseband
Resource Pool.
For the GBTS, eGBTS,
and NodeB, Intra-Board
Baseband Resource Pool
is a basic function and
has no feature ID. In
addition, it does not
require any software
configurations.
for the eNodeB, see
Guidelines for Intra-
Board Baseband
Resource Pool (LTE).
Heat Dissipation GBTS: Y Y Y Y For details, see section

Reliability for eGBTS: Y 4.4 Heat Dissipation
Fans Reliability for Fans. A
base station only
supports this function if
it is configured with a
TCU, FMU, or BBU
FAN. This function is a
basic function and only
requires software
configuration of the
TCU, FMU, or BBU
FAN. For details about
the initial configuration
of the TCU, FMU, or
BBU FAN, see 3900
Series Base Station
Initial Configuration.

SingleRAN
Power Supply GBTS: Y Y Y Y For details about the

Redundancy eGBTS: Y principles of Power
Supply Redundancy, see
section 4.5 Power
Supply Redundancy.
principles and
for Power Supply
Redundancy for a base
station, see Power
Supply Management
Feature Parameter
Description.
Power Supply
Redundancy for a BBU
is a basic function and
does not require any
software configurations.
Power Supply GBTS: Y Y Y Y For details about the

Reliability eGBTS: Y principles of Power
Supply Reliability, see
section 4.6 Power
Supply Reliability.
engineering guidelines of
the function of intelligent
shutdown of carriers due
to PSU failure, see
Guidelines for
Intelligent Shutdown of
Carriers Due to PSU
Failure. For details
about the engineering
guidelines of other
functions involved in
Power Supply Reliability
for a base station, see
Power Supply
Management Feature
Power Supply Reliability
for a BBU is a basic
function and does not
configurations.

SingleRAN
Anti- GBTS: Y Y Y Y For details, see section

Misinsertion eGBTS: Y 4.7 Anti-Misinsertion
Design of Design of Boards. This
Boards is a basic function and
does not require any
software configurations.
Overtemperature GBTS: Y Y Y Y For details, see section

Protection for eGBTS: Y 4.8 Overtemperature
BBU Boards Protection for BBU
Boards. This is a basic
configurations.
Surge Protection GBTS: Y Y Y Y For details, see section

Design eGBTS: Y 4.9 Surge Protection
Design. This is a basic
configurations.

SingleRAN
Description 3 Redundancy Design
3 Redundancy Design
3.1 RF Channel Cooperation

With the development of mobile communications, wireless network coverage increasingly
extends to remote areas along with a rapid increase in demand for network services.
However, the terrain, climate, or traffic conditions in remote areas may be extreme. As a
result, network maintenance is difficult and services may be interrupted for an extended
period of time if a remote radio unit (RRU) is faulty. To facilitate site maintenance, RF
Channel Cooperation is introduced. With RF Channel Cooperation, when one RF channel
becomes faulty, the system automatically switches the services carried on the faulty RF
channel to a functional RF channel. This shortens the period of service interruption caused by
a fault in the RF channel and improves system reliability.
Table 3-1 describes the features involved in RF Channel Cooperation. For details about these
features, see the corresponding feature parameter description.
Table 3-1 Features involved in RF Channel Cooperation

Mode Feature Feature Parameter Description
GSM GBFD-113801 TRX Cooperation TRX Cooperation Feature Parameter

Description
UMTS WRFD-040203 RRU RRU Redundancy Feature Parameter

Redundancy Description
3.2 RRU Channel Cross Connection Under MIMO

Only LTE FDD supports LBFD-002034 RRU Channel Cross Connection Under MIMO.
In sparely populated areas, the RRU or radio frequency unit (RFU) may be installed in a
remote area, for example, on top of a tower. This makes subsequent equipment maintenance
difficult. If one RRU or RFU fails, the entire sector may lose services for an extended period

SingleRAN
Description 3 Redundancy Design
of time. With RRU Channel Cross-Connection Under MIMO, the failure of one RRU or RFU
will not lead to service interruption for the entire sector. This feature increases RRU or RFU
reliability without increasing hardware costs.
As shown in Figure 3-1 (using three sectors as an example), an LBBP is connected to
multiple RRUs. In this case, the data on two TX/RX channels of a cell is transmitted over two
fiber optic cables and processed by two RRUs. When a fiber optic cable fails 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.
Figure 3-1 RF cable connections for RRU channel cross connection under MIMO
For details about the engineering guidelines for this feature, see chapter 7 Engineering
Guidelines for RRU Channel Cross Connection Under MIMO.

SingleRAN
Description 4 Hardware Reliability
4 Hardware Reliability
4.1 Cold Backup of Main Control Boards
4.1.1 Overview
The following table lists the features involved in Cold Backup of Main Control Boards.
Mode Feature
GSM MRFD-210101 System Redundancy
UMTS MRFD-210101 System Redundancy
LTE FDD LBFD-00202101 Main Processing and Transport Unit Cold Backup
When a base station is configured with only one main control board, services will be
interrupted for an extended period of time if this main control board is faulty. To support Cold
Backup of Main Control Boards, two main control boards working in active/standby mode are
required. During cold backup, the standby main control board is powered on but does not
back up the signaling and service data carried by the active main control board. 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 4
to 7 minutes. This improves base station reliability. This feature requires that the two main
control boards are of the same type.
Services are interrupted for more than 7 minutes in the following scenarios:
l The switchover between the two main control boards is triggered by running the SWP
BRD command. In this scenario, services will be recovered within 7 to 9 minutes.
l The switchover between the two main control boards is triggered after the running active
main control board is removed. In this scenario, services will be recovered within 7 to 9
minutes.
l In a secure networking scenario, if the new active main control board does not have a
digital certificate or the digital certificate is invalid or expired, services will be recovered

SingleRAN
within 7 to 9 minutes. For details about secure networking scenarios, see Transmission
Security Feature Parameter Description.
Cold Backup of Main Control Boards involves three processes: active/standby competition,
data backup, and active/standby switchover.
For details about the engineering guidelines for Cold Backup of Main Control Boards, see
chapter 8 Engineering Guidelines for Cold Backup of Main Control Boards.
4.1.2 Active/Standby Competition

The active/standby competition process determines the role of the two main control boards.
When a BBU with two main control boards is powered on, the system determines the active
main control board using active/standby competition if both main control boards function
properly. If one main control board is not configured or is not functioning properly, the other
main control board becomes the active one. You can run the DSP BRD command to query the
active/standby status of the main control boards.
4.1.3 Data Backup

The main control boards work in cold backup mode. Only static data (for example,
configuration data, software data, and logs) must be synchronized between the active and
standby main control boards. Operating data, which requires real-time synchronization in hot
backup mode, does not need to be synchronized in real time in cold backup mode.
Data backup consists of initial backup and routine backup, which are described as follows:
l Initial backup: After 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 using the File Transfer Protocol (FTP).
l 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 using the FTP.
NOTE
l During a fault-triggered active/standby switchover, the base station copies only configuration data
on the active board to the standby board to minimize service interruption duration. Other data is not
backed up. As a result, data updated between the previous periodic backup and the fault occurrence
may be lost. However, this impact is negligible because the data backup period is brief and the
purpose of the active/standby switchover is to ensure service continuity.
l If an active/standby switchover is triggered during a routine backup, the system backs up data before
performing the active/standby switchover. In this case, services are interrupted for 1 to 2 minutes
more than that for a regular active/standby switchover.
4.1.4 Active/Standby Switchover

An active/standby switchover between the two main control boards is triggered in one of the
following scenarios:
l The active main control board experiences a major hardware fault.

l A user delivers an MML command to trigger an active/standby switchover.

SingleRAN
The prerequisites and methods for active/standby switchover vary with triggering conditions,
as described in Table 4-1.
Table 4-1 Prerequisites and methods for active/standby switchover

Switcho Prerequisites Method Remarks
ver Type
Fault- The standby main control board is The system When the active main
triggered functioning properly, the links of the automaticall control board
switchov standby board are normal, and the y triggers experiences major
er standby board has no major hardware the faults, services
faults. switchover. carried on this board
must be switched
over to the standby
main control board to
prevent service
interruption.
Therefore, the
switchover
prerequisites are
relatively simple.
Comman l The standby main control board is A user Before a user delivers
d- functioning properly, the links of delivers a a command to trigger
triggered the standby board are normal, and command to an active/standby
switchov the standby board has no major trigger the switchover, the base
er hardware faults. switchover. station works
l The backup status of the active and For details, properly. The impact
standby main control boards is see chapter of the switchover on
Idle. The backup status can be 8 the base station must
queried by running the DSP Engineerin be minimized.
BKPSTATUS command. g Therefore, the
Guidelines switchover
NOTE
The command-triggered switchover
for Cold prerequisites are
cannot be performed before the initial Backup of relatively complex.
or routine backup between the active Main
and standby main control boards is Control
complete. Perform the command- Boards.
triggered switchover after the hardware
installation is complete and the base
station has been running for more than
two hours.
l The base station is not performing
a software upgrade (including
downloading and activating
software packages or patches).
l More than 3 minutes have elapsed
since the last active/standby
switchover. This is to prevent
frequent switchovers.

SingleRAN
4.2 Inter-Board Baseband Resource Redundancy

The following table lists the features involved in Inter-Board Baseband Resource
Redundancy.
Mode Feature
LTE FDD LBFD-00202102 Cell Re-build Between Baseband Processing Units
LTE TDD TDLBFD-00202102 Cell Re-build Between Baseband Processing Units
When a baseband board fails, the cells or carriers served by this failed baseband board will be
affected. With Inter-Board Baseband Resource Redundancy, the cells or carriers served by a
failed baseband board can be reestablished on another operational baseband board with
available resources. This improves base station reliability.
To implement this feature, a base station must be equipped with at least two baseband boards
and these two baseband boards must be installed in the same BBU.
Inter-Board Baseband Resource Redundancy for GSM

Figure 4-1 illustrates a GBTS S2/2/2 configuration scenario where the GBTS is configured
with two UBBPd_G boards. If one UBBPd_G board fails due to a hardware fault or a
communication port failure, the GBTS can detect and identify the fault and then attempt to
reestablish the carriers served by the failed UBBPd_G board on another UBBPd_G board that
has available baseband resources. Services carried on the BCCH carrier preferentially recover.
For details about the engineering guidelines for this function, see chapter 9 Engineering
Guidelines for Inter-Board Baseband Resource Redundancy (GSM&UMTS).
Figure 4-1 GBTS S2/2/2

SingleRAN
NOTICE
l For GSM, only the UBBP board supports inter-board baseband resource redundancy.
Configure the two UBBP boards in slots 0 and 1.
l Inter-board baseband resource redundancy for GSM does not require CPRI-based
topologies and is only supported if 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 Feature Parameter Description.
Inter-Board Baseband Resource Redundancy for UMTS

Figure 4-2 illustrates a NodeB S1/1/1 configuration scenario where the NodeB is configured
with at least two WBBP or UBBPd_U boards. If one WBBP or UBBPd_U board fails due to a
hardware fault or a communication port failure, the NodeB can detect and identify the fault
and then attempt to reestablish the cells served by the failed WBBP or UBBPd_U board on
another WBBP or UBBPd_U board that has available baseband resources. Services recover
within 20s. For details about the engineering guidelines for this function, see chapter 9
Engineering Guidelines for Inter-Board Baseband Resource Redundancy
(GSM&UMTS).
Figure 4-2 NodeB S1/1/1
NOTE
Inter-board baseband resource redundancy for UMTS does not require CPRI-based topologies and is only
supported if two baseband boards are configured. However, the hot backup ring topology is not supported in
UMTS. For details, see RF Unit and Topology Management Feature Parameter Description.
Inter-Board Baseband Resource Redundancy for LTE

Inter-board baseband resource redundancy for LTE is only supported in the inter-board cold
backup ring topology and hot backup ring topology.
Figure 4-3 illustrates a 3 x 10 MHz 2T2R configuration scenario where the eNodeB is
configured with two LBBP or UBBPd_L boards and the two baseband boards are connected
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 UBBPd_L board fails due to a hardware fault or a

SingleRAN
communication port failure, the eNodeB can detect and identify the fault. The impact of an
LBBP or UBBPd_L board failure on cells served by the failed board is different in the
following scenarios:
l In inter-board cold backup ring topology, one or more cells served by the failed LBBP or
UBBPd_L board will be established on the target LBBP or UBBPd_L board that is also
connected to the RRUs.
l In inter-board hot backup ring topology, the cells served by the failed LBBP or
UBBPd_L board will be established on the target LBBP or UBBPd_L board but will not
if the CPRI port on the failed board is faulty.
The target LBBP or UBBPd_L board is chosen based on the available resources in all
candidate target LBBP or UBBPd_L boards. In Figure 4-3, the blue lines indicate the
communication channels between the source LBBP or UBBPd_L board and RRUs, and the
red lines indicate the communication channels between the target LBBP or UBBPd_L board
and the RRUs. For details about the engineering guidelines for this function, see chapter 10
Engineering Guidelines for Inter-Board Baseband Resource Redundancy (LTE).
Figure 4-3 LTE 3x10M 2T2R
NOTICE
An LBBPc board can only work as a backup for another LBBPc board. An LBBPd board and
a UBBPd_L board can work as a backup for each other.
4.3 Intra-Board Baseband Resource Pool
4.3.1 Overview
The following table lists the features involved in Inter-Board Baseband Resource Pool.

SingleRAN
Mode Feature
LTE FDD LBFD-00202104 Intra-baseband Card Resource Pool (user level/cell

level)
LTE TDD TDLBFD-00202104 Intra-baseband Card Resource Pool (user level/cell

level)
The base station supports the share of resources in a baseband board. Resources are
aggregated into a resource pool to be shared for user data processing by 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 the LTE, only the LBBPc board supports intra-board baseband resource pool.
4.3.2 Intra-Board Cell-Level Resource Pool

Intra-Board Cell-Level Resource Pool for a Single Cell
For GSM and LTE, when a baseband board allocates several resources to a single cell for load
sharing (as shown in Figure 4-4), the common processing parts, for example, RACH
detection, on a failed processing resource can be transferred to other normal resources. This
process ensures service continuity and automatic and quick service recovery because it does
not require manual intervention and generally takes less than 500 ms.
Figure 4-4 Intra-board cell-level resource pool for a single cell
For UMTS, when a baseband board 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.
Intra-Board Cell-Level Resource Pool for Multiple Cells

When a baseband board allocates several resources to multiple cells (as shown in Figure 4-5),
the cells served by a failed processing resource can be reestablished on other normal
processing resources within 20s. This ensures service recovery.
GSM, UMTS, and LTE support the function of intra-board cell-level resource pool for
multiple cells.

SingleRAN
Figure 4-5 Intra-board cell-level resource pool for multiple cells
4.3.3 Intra-Board User-Level Resource Pool

When multiple processing resources are available for one cell, the baseband board can
dynamically allocate these processing resources to users that access the cell
Intra-board user-level resource pool is supported in UMTS and LTE, but not in GSM.
If a baseband board in an eNodeB provides multiple processing resources for one cell,
multiple users that attempt to access the cell can share these processing resources. When the
cell has a small number of users, more processing resources can be allocated to a single user
to increase the data rate for the user. After being admitted, the UE cannot use other resources
on the baseband board.
If a baseband board in a NodeB provides multiple processing resources for one cell, multiple
users that attempt to access the cell can share these processing resources. However, a single
user can use only one processing resource. After being admitted, the UE can use other
resources on the baseband board when the attributes of the user must be modified.
4.4 Heat Dissipation Reliability for Fans

Fans are used for inner and outer air circulation, allowing heat to dissipate from the
equipment through a ventilation channel. When a fan on a ventilation channel 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:
l When the FMU works in intelligent 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.
l 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.
l When the TCU cannot obtain the temperature at the air exhaust vent, 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.
l 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 in the FAN unit
rotate at full speed to ensure heat dissipation.

SingleRAN
l 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.
l When ALM-26101 Inter-Board CANBUS Communication Failure is reported, fans in
the BBU rotate at full speed.
4.5 Power Supply Redundancy

Power supply redundancy consists of power supply redundancy for a base station and power
supply redundancy for a BBU.
4.5.1 Power Supply Redundancy for a Base Station

PSUs in a base station should be configured in N+1 backup mode. After power supply
redundancy for a base station is enabled for a Huawei AC-powered base station equipped with
a PMU, ALM-25636 Loss of Power Supply Redundancy is reported if PSUs in the base
station are not configured in N+1 mode. The reported alarm alerts the customer to the
insufficiency of PSUs.
Power supply redundancy for a base station does not have a feature ID and is supported by
GSM, UMTS, and LTE base stations. For details about the principles and engineering
guidelines for this feature, 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 Feature Parameter Description.
4.5.2 Power Supply Redundancy for a BBU

The BBU supports 1+1 backup mode for power boards.
Currently, only the UPEUc and UPEUd boards can work in 1+1 backup mode. When the
configured power consumption of the whole BBU exceeds the power supply capability of a
single UPEUc board, the UPEUc boards cannot work in 1+1 backup mode.
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:
l Each power board can undertake the power load of the whole BBU.
l 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.
4.6 Power Supply Reliability

Power supply reliability consists of power supply reliability for a base station and power
supply reliability for a BBU.

SingleRAN
4.6.1 Power Supply Reliability for a Base Station

Protection Against Overvoltage and Overcurrent
The base station supports a wide range of input voltage and provides protection against
overcurrent.
l The base station supports a wide range of input voltage. For details about the supported
voltage range, see section "Engineering Specifications of Cabinets" in the chapter
"Product Specifications" of 3900 Series Base Station Technical Description.
l In AC input scenarios, the PSUs provide protection against overcurrent and overvoltage
for its DC outputs. Once overcurrent or overvoltage occurs, the PSUs stop providing DC
outputs.
l In DC input scenarios, the DCDU provides a circuit breaker or fuse for each DC output.
Once short-circuit or overload occurs on a DC output, the corresponding circuit breaker
or fuse is disconnected automatically. This does not affect upper-level equipment.
Enhanced Power Supply for Huawei AC-Powered Base Stations Equipped with
the PMU
In addition to basic power supply functions, the features in the following table are provided
for Huawei AC-powered base stations equipped with the PMU to improve power supply
reliability.
Function Feature ID and Name Description
Intelligent GSM: GBFD-510710 Intelligent Intelligent battery management

battery Battery Management provides the following functions:
management automatic switching between
UMTS: WRFD-140220 different charge-and-discharge
Intelligent Battery Management modes, self-protection under high
LTE FDD: LOFD-001071 temperature, and battery runtime
Intelligent Battery Management display.
LTE TDD: TDLOFD-001071

Intelligent Battery Management
Automatic GSM: GBFD-111601 BTS Power Automatic battery and load

battery and load Management disconnection provides the
disconnection This is a basic function for following functions: automatic
UMTS and LTE base stations and battery disconnection under low
does not have a feature ID. voltage, automatic battery
disconnection under high
temperature, and automatic load
disconnection.

SingleRAN
Function Feature ID and Name Description
Intelligent This is a basic function for GSM, Base stations supplied with solar
diesel generator UMTS, and LTE base stations power support intelligent diesel
management and does not have a feature ID. generator management. Using
either RS485 or dry contact ports,
the PMU monitors the status, fuel
level, and faults of the diesel
generator.
Intelligent GSM: GBFD-117804 Intelligent When some PSUs become faulty

shutdown of Shutdown of TRX Due to PSU and the remaining PSUs cannot
carriers due to Failure meet the base station's power
PSU failure This is a basic function for requirements, the base station
UMTS and LTE base stations and enters energy saving mode to
does not have a feature ID. reduce power consumption if this
function is enabled. In energy
saving mode, the base station shuts
down the power amplifiers of the
carriers that consume excessive
electricity.
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 Feature Parameter Description.
The function of intelligent shutdown of carriers due to PSU failure is described as follows:
In scenarios where a base station uses the AC power input, the PSU converts the AC power to
DC power and then supplies the DC power to boards in the base station. Generally, multiple
PSUs are required to provide sufficient electricity for a base station and these PSUs work in
parallel. If one or several PSUs are faulty, the load of the PSUs that work properly increases.
As a result, all PSUs may stop working due to overcurrent protection and all the services
carried on the base station may be interrupted. To prevent this from happening, intelligent
shutdown of carriers due to PSU failure is introduced. With this function, when one or several
PSUs are faulty, the base station shuts down the power amplifiers of the carriers that consume
excessive electricity, based on the power supply capability of the PSUs that work properly. In
this manner, other carriers continue to work properly, minimizing the impact of service
interruption. For details about the configurations for this function, see chapter 12
Engineering Guidelines for Intelligent Shutdown of Carriers Due to PSU Failure.
4.6.2 Power Supply Reliability for a BBU

Power supply reliability for a BBU includes good environment adaptability, improved fault
handling mechanism, and sound power consumption management for BBU boards.
l Good environment adaptability

– Wide range of input voltage: The BBU supports -48 V DC power input and an
actual input voltage range of -57 V DC to -38.4 V DC.
– Wide range of operating temperatures: The BBU supports an operating temperature
range of -20°C to 60°C.

SingleRAN
– Satisfied indoor protection: The BBU does not require an additional surge
protection unit.
l Improved fault handling mechanism
– Protection against reverse connection: When the input positive and negative poles
are reversely connected, the power board is not powered on, preventing the power
board from being damaged.
– Protection against undervoltage: When the input voltage is lower than the lower
threshold of the operating voltage range, the power board stops working, preventing
the power board from being damaged. When the input voltage becomes normal, the
power board restarts.
– Protection against output overload: When the power supply requirements of the
BBU exceed the power supply capability of power boards, the power board enters
hiccup protection mode, preventing the power board, power-consuming devices,
and system from being damaged. In this case, the BBU will be reset.
– Protection against output short-circuits: If an output short-circuit occurs, the power
board enters hiccup protection mode, preventing the power board, power-
consuming devices, and system from being damaged. In this case, the BBU will be
reset.
– Protection against output overvoltage: If the output overvoltage occurs, the power
board enters hiccup protection mode, preventing the power board, power-
consuming devices, and system from being damaged. In this case, the BBU will be
reset.
– Protection against overtemperature: The power board stops working when its
temperature is too high and restarts when its temperature returns to the normal
operating temperature range. In this case, the BBU will be reset.
NOTE
Hiccup protection mode: When a power board experiences a fault that may damage itself, the
power board stops the power supply and at the same time continues detecting whether the fault is
rectified. Once the fault is rectified, the power board resumes the power supply.
l Sound power consumption management for BBU boards
– When the power supply capability of power boards in the BBU is insufficient
because of a board expansion or power board failure, the baseband boards with a
low power-on priority are powered off, preventing power overload in the BBU.
– After a BBU is reset due to insufficient power supply, the BBU attempts to power
on the baseband boards after it is powered on again. If the BBU is reset for a second
time due to insufficient power supply after powering on baseband boards, some
baseband boards 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
configurations.
4.7 Anti-Misinsertion Design of Boards

When a board of one type is inserted into a slot for a board of another type, the board cannot
connect to the backplane. This prevents the board from being damaged.

SingleRAN
4.8 Overtemperature Protection for BBU Boards

When the temperature of a BBU board exceeds its maximum operating temperature, the
lifespan of the board may be shortened or its reliability may be affected. In the worst-case
scenario, the board may be burnt out, imposing safety risks. To prevent this from happening,
Huawei provides the Power-Off on Overtemperature function.
4.8.1 Overtemperature Power-Off for Non-Main-Control Boards
Power-Off Requirements
l 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 common
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 common overtemperature alarm exists on the main control board for more than 2 minutes, the
main control board powers off the WBBPa or WBBPb and reports ALM-26214 Board Powered Off.
l A non-main-control board can power off itself and reports ALM-26214 Board Powered
Off when it detects that its temperature is higher than the overtemperature power-off
threshold.
Power-On Requirements
The overtemperature alarm reported on a non-main-control board can be manually or
automatically cleared only if the main control board is not powered off due to
overtemperature.
l 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
common 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.
l Manual mode: Users can deliver an MML command to forcibly power on a non-main-
control board. In this case, reported alarms will not be cleared unless the alarm clearing
threshold for automatic alarm clearing is 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.

SingleRAN
Impact of Overtemperature Power-Off of Non-Main-Control Boards on

Multimode Base Stations
In a multimode base station, a main control board detects the temperature of boards working
in the same mode as itself and does not manage boards working in other modes or boards that
are not configured.
When a non-main-control board is powered off due to overtemperature, services of the peer
mode may be affected or even interrupted in scenarios such as co-transmission or CPRI
MUX. The impact of overtemperature power-off on services of the peer mode is the same as
that caused by other faults on the board.
4.8.2 Overtemperature Power-Off for Main Control Boards
Power-Off Requirements
When the temperature of a main control board is higher than the common overtemperature
alarm threshold, a common overtemperature alarm is reported. If the temperature continues to
rise and becomes higher than the severe overtemperature alarm threshold, a severe
overtemperature alarm is reported. In this case, all baseband boards in the same BBU subrack
as the main control board are powered off. 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 and powers off all other boards in the
BBU subrack and then 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.
Impact of Overtemperature Power-Off of Main Control Boards on Multimode

Base Stations
l In a multimode base station, the impact of overtemperature power-off of a main control
board on services is the same as that caused by a reset or fault of the main control board.
In a separate-MPT multimode base station, each main control board only manages itself and
boards working in the same mode as the main control board. In a co-MPT multimode base
station, the active main control board manages all the boards in the BBU subrack. In this case,
the active main control board powers off all the boards at the same time when necessary,
without considering the RAT priority.
4.9 Surge Protection Design

The surge protection design of Huawei products complies with related standards. Different
surge protection solutions are provided for different ports.
4.9.1 Standards
No. File No. File Name
1 IEC62305-1 Protection against lightning -Part 1: General principles

SingleRAN
No. File No. File Name
2 IEC62305-2 Protection against lightning -Part 2: Risk management
3 IEC62305-3 Protection against lightning -Part 3: Physical damage to

structures and life hazard
4 IEC62305-4 Protection against lightning - Part 4: Electrical and

electronic systems within structures
5 IUT-T K.56 Protection of radio base stations against lightning

discharges
6 ITU-T K.35 Bonding configurations and earthing at remote electronic

sites
7 ITU-T Handbook ITU-T Earthing and Bonding Handbook
8 IEC 60364-5-54 Electrical installations of buildings - Part 5-54 Selection

and erection of electrical equipment - Earthing
arrangement, protective conductors and protective bonding
conductors
9 YD 5098 Specifications on Engineering Design of Lightning

Protection and Earthing for Telecommunication Bureaus
(Stations)
10 GB50689-2011 Code for design of lightning protection and earthing

engineering for telecommunication bureaus (stations)
4.9.2 Surge Protection Capability of Different Ports

The following table lists the surge protection capability of different ports.
No. Port Type Surge Protection Capability
1 AC In a BTS3900A, surge protection of 30 kA (8/20 us)

is required and no external surge protector is
required.
In a BTS3900, surge protection of 5 kA (8/20 us) is
required.
2 DC Surge protection of 4 kV (1.2/50 us) is required is

indoor scenarios and surge protection of 20 kA (8/20
us) is required in outdoor scenarios.
3 Antenna port A built-in surge protection of 40 kA meets the surge

protection requirements in all scenarios and no
external surge protector is required.
4 E1/T1 Different surge protection solutions are provided in

indoor and outdoor scenarios and no surge protector
is required.

SingleRAN
No. Port Type Surge Protection Capability
5 GE/FE Different surge protection solutions are provided in

is required.
6 RGPS Built-in surge protection is used on the equipment

and no surge protector is required.
7 GPS A surge protector is required on the equipment side.
8 Dry contact/485 Different surge protection solutions are provided in

is required.
9 AISG Built-in surge protection is used on the equipment

and no surge protector is required.

SingleRAN
Description 5 Related Features
5 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Description 6 Network Impact
6 Network Impact
System Capacity
No impact.
Network Performance
No impact.

SingleRAN
Base Station Equipment Reliability Feature Parameter 7 Engineering Guidelines for RRU Channel Cross
Description Connection Under MIMO
7 Engineering Guidelines for RRU Channel

Cross Connection Under MIMO
7.1 When to Use RRU Channel Cross Connection Under

MIMO
RRU Channel Cross Connection Under MIMO can be enabled when RRUs are installed on
top of a tower. Cross-connections between a baseband board and RRUs enable the data on
two TX/RX channels of a cell to be transmitted using two fiber optic cables and to be
processed by two RRUs. When a fiber optic cable fails 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.
This feature cannot be used together with MRFD-231806 GSM and LTE Dynamic Power
Sharing(LTE).
7.2 Required Information

N/A
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A

SingleRAN
7.4 Deployment
7.4.1 Requirements
Hardware
l This feature applies only to macro base stations and LampSite base stations.
l This feature is recommended for tower-mounted RRUs.
l All RF units must be of the same model and support the same set of frequency bands.
l The number of RF units is equal to or greater than two.
l Cells with RRU channel cross-connection under MIMO applied must work on the same
frequency and have the same bandwidth.
l The antenna mode must be 2T2R for sectors enabled with RRU Channel Cross
Connection Under MIMO. The two TX/RX channels must be configured on different RF
units.
l The difference in length of fiber optic cables that connect RRUs and baseband boards
must be less than 100 m.
l The LRRUs or LRFUs must form a star topology and connect to the same baseband
board.
NOTE
In multimode base stations where the dual-star topology is used, RRUs must be connected to the same
baseband board.
License
None
7.4.2 Data Preparation

There are three types of data sources:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameters values negotiated with core network or
transmission equipment
l User-defined: parameter values set by users
Table 7-1 describes the parameters for RRU Channel Cross Connection Under MIMO.
Table 7-1 Parameters for RRU Channel Cross Connection Under MIMO
MO Parameter Parameter ID Setting Data Source

Name Notes
SECTOR Sector ID SECTORID None Network plan

(negotiation not required)

SingleRAN
MO Parameter Parameter ID Setting Data Source

Name Notes
SECTOR Sector SECTORANTENNA None Network plan

Antenna (negotiation not required)
7.4.3 Precautions
The precautions for deploying RRU Channel Cross Connection Under MIMO are as follows:
l All RF units must be of the same model and support the same set of frequency bands.
l The number of RF units is equal to or greater than two.
l The antenna mode must be 2T2R for sectors enabled with RRU Channel Cross
Connection Under MIMO. Each sector must be configured on a unique RF unit, and the
RF units must be correctly connected to antennas.
l The RF units must form a star topology and connect to the same baseband board.
l For LBBPc boards, optical fibers that connect the LBBPc boards and RF units must have
approximately the same length. Any difference in lengths must be less than 100 m. There
is no such restriction for LBBPd boards.
l If faults on the fiber optic cable or RRU are rectified when the cell has rolled back to
1T1R and is in active mode, the system triggers cell reestablishment to change the cell
configuration from 1T1R to 2T2R only when no RRC-connected user exists in the cell.
In multimode scenarios, RRU Channel Cross Connection Under MIMO is supported in LTE
mode. For other modes, support for this feature depends on the capability of the mode.
7.4.4 Hardware Adjustment

Connect RRUs or RFUs to antennas according to Figure 3-1.
7.4.5 Activation
Using MML Commands

Add and remove configurations in the following orders:
l Configure sectors, operators, tracking areas, cells, cell sector equipment, cell operators,
and cells successively.
l Remove cells and sectors successively
Perform the following operations to activate RRU Channel Cross Connection Under MIMO:
Step 1 Run the ADD SECTOR command to add a sector.

NOTE
Two antennas are configured, and antenna channels R0A and R0B are configured on different RRU
ports. Cable connections must be consistent with the configurations.
Step 2 Run the ADD CNOPERATOR command to add an operator.
Step 3 Run the ADD CNOPERATORTA command to add a tracking area.

SingleRAN
Step 4 Run the ADD CELL command to add a cell.
Step 5 Run the ADD EUCELLSECTOREQM command to add cell sector equipment.
Step 6 Run the ADD CELLOP command to add a cell operator.
Step 7 Run the ACT CELL command to activate the cell.
----End
MML Command Examples

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 CNOPERATOR: CnOperatorId=0, CnOperatorName="cmcc",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="00";
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33;
ADD CELL: LocalCellId=0, CellName="MIMO", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1600, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0,
PhyCellId=0, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ACT CELL: LocalCellId=0;
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the 7.4.2 Data Preparation section for a single base
station. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.

SingleRAN
Using the CME to Perform Batch Configuration

NOTE
l When configuring this feature on the CME, you must perform a single configuration first, and then
perform batch modifications if required. You must perform a single configuration for a parameter
before batch modifications of the parameter. You are advised to perform batch modifications before
logging out of the parameter setting interface.
l The default display style of the U2000 client is the application style. However, traditional style is
more convenient for operations described in this document. All operation guides related to the
U2000 client described in this document is based on the traditional style.
l To change the display change to the traditional style, choose System > Preferences > Client
Display Style in the upper left corner of the U2000 client main window.
Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data
File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME
client mode), to customize a summary data file for batch configuration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-1 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts.
----End
7.4.6 Activation Observation

For details about activation observation procedures for RRU Channel Cross Connection
Under MIMO, see Cell Management Feature Parameter Description.
7.4.7 Deactivation
To deactivate RRU Channel Cross Connection Under MIMO, remove the related
configurations and then remove the cables.
Using MML Commands

Remove cells and sectors successively.
Step 1 Run the RMV CELL command to remove the cell.
Step 2 Run the RMV SECTOR command to remove the sector.
----End

SingleRAN

RMV CELL: LocalCellId=0;
RMV SECTOR: SECTORID=0;

Configure the MO described in Table 7-2 on the CME configuration interface. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide.
Table 7-2 Configuring the MOs on the CME

SN MO Configuration Description
1 CELL Remove the configuration data of the

cell.
2 SECTOR Remove the configuration data of the

sector.

You cannot use the CME to perform batch configuration to deactivate this feature.
7.4.8 Reconfiguration
None
7.5 Performance Monitoring

N/A
7.6 Parameter Optimization

None
7.7 Troubleshooting
If an alarm described in Table 7-3 is generated, clear the alarm by referring to the alarm
handling suggestions in 3900 Series Base Station Alarm Reference.

SingleRAN
Table 7-3 Related alarms

Alarm ID Alarm Name Alarm Alarm Network
Type Severity Management
Level Type
ALM-26234 BBU CPRI Interface Error Fault Major Hardware

system
ALM-29243 Cell Capability Degraded Fault Major Signaling

system
ALM-26236 RRU Cascading Levels and Fault Major Hardware

Configuration Mismatch system
ALM-26238 RRU Network Topology Type Fault Major Hardware

and Configuration Mismatch system
ALM-26504 RF Unit CPRI Interface Error Fault Major Communicatio

n system

SingleRAN
Base Station Equipment Reliability Feature Parameter 8 Engineering Guidelines for Cold Backup of Main Control
Description Boards
8 Engineering Guidelines for Cold Backup of

Main Control Boards
8.1 When to Use Cold Backup of Main Control Boards

Cold Backup of Main Control Boards is recommended if the customer has a high requirement
on the base station reliability. This feature provides the following benefits:
l Services recover within several minutes after the main control board experiences a
hardware failure.
l In a co-MPT multimode base station, when the main control experiences a severe
hardware failure, services of all modes are interrupted simultaneously. This feature
ensures that services can recover automatically. This improves base station reliability.

N/A
8.3 Planning
RF Planning
N/A
Network Planning
l Two UMPT or LMPT boards with the active/standby transmission capability are
supported only in Ethernet networks.
l Two UMPT, LMPT, or WMPT boards with the active/standby transmission capability do
not support HUB transmission cascading.
l Cold backup of main control boards has the following restrictions on the secure
networking planning:

SingleRAN
Description Boards
– When two WMPT boards work in cold backup mode, functions such as IPSec,
802.1x-based authentication, and public key infrastructure (PKI) authentication are
not supported.
– If UMPT or LMPT 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.
– If UMPT or LMPT boards work in cold backup mode, and IPSec and digital
certificate authentication are used, the IDTYPE parameter can be set to IP or
FQDN for the base station. When the IDTYPE parameter is set to FQDN, the
Security Gateway (SeGW) must not authenticate the ID value of the base station.
Otherwise, the IDTYPE parameter must be set to IP and the base station must be
deployed using a USB flash drive.
Hardware Planning
l Only UMPT, LMPT, and WMPT boards support Cold Backup of Main Control Boards.
– Cold backup of UMPT boards applies to LampSite base stations and macro base
stations that use BBU3900 or BBU3910, including NodeBs, eNodeBs FDD, and co-
MPT base stations.
– Cold backup of LMPT boards applies only to eNodeBs FDD.
– Cold backup of WMPT boards applies only to NodeBs.
l To support Cold Backup of Main Control Boards, two main control boards of the same
hardware type are required in the same BBU subrack, for example, two UMPTb1 boards.
l When two WMPT boards with the active/standby transmission capability are configured
as active/standby main control boards and use E1 transmission, a bifurcated E1 cable is
required. If the bifurcated E1 cable is used indoors, a surge protection board and a surge
protection box are required.
NOTE
When two WMPT boards work in cold backup mode, functions such as IPSec, 802.1x-based
authentication, and public key infrastructure (PKI) authentication are not supported.
l 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
automatically but not for GSM or UMTS. When two WMPT or LMPT boards work in
cold backup mode, the standby WMPT or LMPT board cannot work as a signaling
extension board.
NOTE
When the standby UMPT board works as a signaling extension board for LTE, the LTE 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.
l In UCIU+UMPT BBU interconnection scenarios, only the primary BBU supports Cold
Backup of Main Control Boards.
l In UMPT+UMPT BBU interconnection scenarios, Cold Backup of Main Control Boards
is not recommended for the UMPT board in the primary BBU.

SingleRAN
Description Boards
NOTICE
In BBU interconnection scenarios, only the primary BBU supports Cold Backup of Main
Control Boards. Therefore, two main control boards must be installed in the primary BBU.
8.4 Deployment
8.4.1 Requirements
Hardware
l To support cold backup of UMPT, WMPT, or LMPT boards, two UMPT, WMPT, or
LMPT boards of the same hardware type must be installed in slots 6 and 7 in the same
BBU subrack.
l 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.
l When two WMPT boards with the active/standby transmission capability are configured
as active/standby main control boards and use E1 transmission, a bifurcated E1 cable is
required. If the bifurcated E1 cable is used indoors, a surge protection board and a surge
protection box are required.
License
None

l Configuring main control boards
Main control boards in active/standby mode must be configured on the same logical NE.
Table 8-1 describes the key parameters for configuring main control boards.
Table 8-1 Key parameters for configuring main control boards
Parameter Parameter Setting Notes Data Source

Name ID
Cabinet No. CN Set this parameter to 0. Network plan

(negotiation not
required)
Subrack No. SRN Set this parameter to 0. Network plan

(negotiation not
required)
Slot No. SN Set this parameter to 6 and 7 for Network plan

two main control boards. (negotiation not
required)

SingleRAN
Description Boards

Name ID
Board Type TYPE Set this parameter to UMPT, Network plan

LMPT, or WMPT based on the (negotiation not
actual configuration. Boards in required)
slots 6 and 7 must be of the same
type.
l Configuring an HAGRP
Table 8-2 describes the parameters that must be set in the HAGRP MO to configure two
boards with the active/standby transmission capability as two boards working in active/
standby mode.
Table 8-2 Key parameters for configuring an HAGRP

Name ID
Cabinet No. CN None Network plan

(negotiation not
required)
Subrack No. SRN None Network plan

(negotiation not
required)
Logical Slot SN This parameter can be set to a Network plan

No. value different from the number (negotiation not
of the slot where the main control required)
boards are installed.
8.4.3 Precautions
l 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 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.
l Adding or removing an HAGRP MO changes the connection between the base station
and the transport network and resets the base station.

Both of the two main control boards in active/standby mode must be UMPT, LMPT, or
WMPT boards.

SingleRAN
Description Boards
NOTE
l 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 working modes, the spare UMPT board automatically
switches to the working mode of the replaced UMPT board and works in active and standby mode
with the other original UMPT board after the replacement.
l WMPT and LMPT boards support only one mode and therefore do not involve mode switching.
8.4.5 Activation
The operations on the CME for single-mode base stations such as eGBTS, NodeB, and
eNodeB FDD are the same as those for multimode base stations. The operations on the CME
in this section are described based on multimode base stations.
It is recommended that the Cold Backup of Main Control Boards feature be activated on the
CME.
This section describes the steps for activating the Cold Backup of Main Control Boards
feature for a base station that meets the following requirements:
l A main control board has been configured in the base station and the transmission data
has been configured for this board.
l The base station is operating properly.
Using MML Commands

Step 1 Modify the base station configurations on the CME. For details, see Step 1 in Using the
CME to Perform Single Configuration.
Step 2 Export the deployment list of the base station. For details, see Step 2 in Using the CME to
Perform Single Configuration.
Step 3 Upload the deployment list of the base station to the U2000. For details, see Step 3 in Using
the CME to Perform Single Configuration.
Step 4 Run the ADD BRD command to add another main control board.
Step 5 Run the DSP BRD command to query the slot No. of the active main control board.
Step 6 Run the ADD HAGRP command to add an HAGRP MO. In this HAGRP MO, the value of
the Logical Slot No. parameter must be the same as the slot No. of the active main control
board.
----End
NOTE
The preceding steps do not apply to separate-MPT base stations that are running properly. If you need to
active the Cold Backup of Main Control Boards feature for such a base station, contact Huawei
engineers.

ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT;
ADD BRD: CN=0, SRN=0, SN=7, BT=UMPT;
ADD HAGRP: CN=0, SRN=0, SN=6;

SingleRAN
Description Boards

Step 1 Modify the base station configurations.
Configure the MOs described in the following table on the CME configuration interface. For
Operation Guide.
Table 8-3 MOs to be configured on the CME

1 MPT Add a standby main control board.
2 EHTPORT Delete the EHTPORT MOs that are

automatically configured on the standby main
control board.
3 HAGRP Add an HAGRP MO.
Step 2 Export the deployment list of the base station. For details, see section "Preparing a Data
Configuration File and a Deployment List" in 3900 Series Base Station Commissioning
Guide.
Step 3 Upload the deployment list of the base station to the U2000 so that the DHCP server-related
configurations on the U2000 are updated. For details, see section "Creating an NE
Commissioning Task" in 3900 Series Base Station Commissioning Guide.
Step 4 Deliver incremental configurations.
----End

NOTE
l When configuring this feature on the CME, you must perform a single configuration first, and then
perform batch modifications if required. You must perform a single configuration for a parameter
before batch modifications of the parameter. You are advised to perform batch modifications before
logging out of the parameter setting interface.
l The default display style of the U2000 client is the application style. However, traditional style is
more convenient for operations described in this document. All operation guides related to the
U2000 client described in this document is based on the traditional style.
l To change the display change to the traditional style, choose System > Preferences > Client
Display Style in the upper left corner of the U2000 client main window.
NOTE
Step 2 Choose CME > GSM Application/UMTS Application/LTE Application > Export Data >
Export Base Station Bulk Configuration Data (U2000 client mode), or choose GSM
Application/UMTS Application/LTE Application > Export Data > Export Base Station

SingleRAN
Description Boards
Bulk Configuration Data (CME client mode), to export the base station data stored on the
CME into the customized summary data file.
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 4 Choose CME > GSM Application/UMTS Application/LTE Application > Import Data >
Import Base Station Bulk Configuration Data (U2000 client mode), or choose GSM
Application/UMTS Application/LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Delete the redundant data that is automatically generated on the standby main control board,
including the Ethernet port data, which corresponds to the ETHPORT MO.
Step 8 In the summary data file, set the parameters related to the HAGRP MO for the standby main
control board, and close the file.
----End
8.4.6 Commissioning
Cold backup of UMPT, LMPT, or WMPT boards supports base station deployment using a
USB flash drive. To deploy a base station configured with two UMPT, LMPT, or WMPT
boards using a USB flash drive, perform the following steps.
Step 1 Remove a main control board.
Step 2 Insert the USB flash drive into the other main control board to deploy the base station.

SingleRAN
Description Boards
Step 3 Remove the USB flash drive.
Step 4 Reinstall the main control board that was removed in step 1. After reinstallation, the two main
control boards work in active/standby mode. The active main control board is designated by
an illuminated ACT indicator
----End
Cold backup of UMPT boards supports base station deployment using plug and play (PnP). In
scenarios where the transport network works properly and the UMPT boards do not work in
active and standby mode, the UMPT boards will be reset so that they work in the target
working mode and in active and standby mode after the base station receives the DHCP
packets. Therefore, the deployment of the base station enabled with Cold Backup of Main
Control Boards requires an additional 9 to 10.5 minutes compared with that of a base station
configured with only one UMPT board.
When a base station with cold backup of UMPT boards is to be deployed using PnP, the
following requirements must be met:
l Two UMPT boards have been installed and configured.

l The two UMPT boards communicate with the transport network properly.
l If IPSec is deployed, the SN parameter in the CERTDEPLOY MO must be set to the
value of the Logical Slot No. parameter in the HAGRP MO.
l The other requirements are the same as those for the base station with only one UMPT
board. For details about these requirements, see 3900 Series Base Station
Commissioning Guide.
NOTE
Cold backup of WMPT or LMPT boards does not support base station deployment using PnP.

Step 1 Run the DSP BRD command to check whether the boards in slots 6 and 7 are normal. If the
value of StandBy Status is Active for one board and is Standby for the other board and the
value of Availability Status is Normal for both boards, the two boards are normal.
Step 2 Run the LST HAGRP command to check whether two boards with the active/standby
transmission capability have been configured as two boards working in active/standby mode.
If configuration of the transport high availability (HA) group is available, the two boards with
the active/standby transmission capability have been configured as two boards working in
active/standby mode.
Step 3 Run the DSP BKPSTATUS command to check the backup status. If Backup Switch is On,
cold backup of main control boards is activated. If Backup Status is Idle, initial backup is
complete.
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 Run the SWP BRD command to switch the active and standby roles of the main control
boards. Upon execution of this board, the base station will automatically perform routine
backup, reset, and switchover between the active and standby main control boards, which take
about 30 minutes. Base station resets will interrupt ongoing services.

SingleRAN
Description Boards
Step 5 When the base station becomes normal after the reset, and the connection to the LMT or
U2000 is restored, perform Step1 to Step3 to check whether the active and standby roles of
the main control boards have been swapped.
----End
8.4.8 Deactivation
Using MML Commands

Step 1 Modify the base station configurations on the CME. For details, see Step 1 in Using the
CME to Perform Single Configuration.
Step 2 Export the deployment list of the base station. For details, see Step 2 in Using the CME to
Perform Single Configuration.
Step 3 Upload the deployment list of the base station to the U2000. For details, see Step 3 in Using
the CME to Perform Single Configuration.
Step 4 Run the LST HAGRP command to query the logical slot No. of the HAGRP.
Step 5 Run the DSP BRD command to query the slot No. of the active main control board. Check
whether the slot No. of the active main control board is the same as the logical slot No. of the
HAGRP.
Step 6 (Optional) If the slot No. of the active main control board is different from the logical slot No.
of the HAGRP, run the SWP BRD command to switch over the active and standby main
control boards. After this command is executed, the base station resets.
Step 7 Run the RMV HAGRP command to remove the HAGRP MO. After this command is
executed, the base station resets.
Step 8 Run the RMV BRD command to remove the standby main control board.
----End

//Querying the logical slot No. of the HAGRP
LST HAGRP:;
//Querying the slot No. of the active main control board

DSP BRD:;
//Switching over the active and standby main control boards

SWP BRD:;
//Removing the HAGRP MO.

RMV HAGRP: CN=0, SRN=0, SN=6;
//Removing the standby main control board

RMV BRD: CN=0, SRN=0, SN=7;

SingleRAN
Description Boards

Step 1 Modify the base station configurations.
Configure the MOs described in Table 8-4 on the CME configuration interface. For
Operation Guide.
1 HAGRP Remove the HAGRP MO.
2 MPT Remove the configuration data for the

cold backup of main control boards.
Step 2 Export the deployment list of the base station. For details, see section "Preparing a Data
Configuration File and a Deployment List" in 3900 Series Base Station Commissioning
Guide.
Step 3 Upload the deployment list of the base station to the U2000 so that the DHCP server-related
configurations on the U2000 are updated. For details, see section "Creating an NE
Commissioning Task" in 3900 Series Base Station Commissioning Guide.
Step 4 Deliver incremental configurations.
----End

You cannot use the CME to perform batch configuration to deactivate this feature.
N/A

N/A

N/A
8.7 Troubleshooting
N/A

SingleRAN
Base Station Equipment Reliability Feature Parameter 9 Engineering Guidelines for Inter-Board Baseband
Description Resource Redundancy (GSM&UMTS)
9 Engineering Guidelines for Inter-Board

Baseband Resource Redundancy
(GSM&UMTS)
9.1 When to Use Inter-Board Baseband Resource

Redundancy (GSM&UMTS)
It is recommended that this feature be activated in scenarios with high requirements for
reliability. For example, services are required to recover within 30s after a baseband board
becomes faulty. If multiple UBBPs are configured in a multimode base station, it is
recommended that each mode be deployed on all UBBPs. This improves system reliability by
using the inter-board baseband resource redundancy.

None
9.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
The base station must be equipped with a minimum of two BBPs. This feature applies only to
macro base stations and LampSite base stations that use BBU3900 or BBU3910.

SingleRAN
9.4 Deployment
NOTE
In a multimode base station, the inter-board baseband resource pool is configured for each mode. The
configuration method is the same as that for a single-mode base station.
9.4.1 Requirements
Hardware
l The NodeB is configured with two or more WBBPs/UBBPs, which are installed in slots
0 to 5.
l The GBTS or eGBTS is configured with two or more UBBPs, which are installed in
slots 0 and 1.
l This feature applies only to macro base stations and LampSite base stations that use
BBU3900 or BBU3910.
License
None

For GSM (eGBTS) and UMTS, Table 9-1 describes the key parameters that must be set for a
BBP.
Table 9-1 Key parameters configured for a BBP

Paramete Paramete Setting Notes Data Source
r Name r ID
Cabinet CN Set this parameter to 0. Network plan (negotiation

No. not required)
Subrack SRN Set this parameter to 0. Network plan (negotiation

No. not required)
Slot No. SN Set this parameter to 0 and 1 for Network plan (negotiation
two BBPs in an eGBTS. The not required)
NodeB has no special
requirement.
Board TYPE Set this parameter to UBBP for Network plan (negotiation
Type the eGBTS. Set this parameter to not required)
WBBP or UBBP for the NodeB as
required.
Base Band BBWS Set this parameter to the modes for Engineering design
Work which the UBBP board provides
Standard baseband processing resources.

SingleRAN
For GSM (GBTS), Table 9-2 describes the key parameters that must be set for a BBP.
Table 9-2 Key parameters configured for a BBP (GBTS)

Paramete Paramete Setting Notes Data Source
r Name r ID
Cabinet CN Set this parameter to 0. Network plan (negotiation

No. not required)
Subrack SRN Set this parameter to 0. Network plan (negotiation

No. not required)
Slot No. SN Set this parameter to 0 and 1 for Network plan (negotiation
two BBPs. not required)
Board BT Set this parameter to UBBP. Network plan (negotiation

Type not required)
Table 9-3 describes the key parameters that must be set in a BASEBANDEQM MO. For
GSM, the BASEBANDEQM MO is required by the eGBTS and is not required by the
GBTS.
Table 9-3 Key parameters for configuring the baseband equipment

Parameter Parameter ID Setting Notes Data Source
Name
Baseband BASEBANDEQMID For an eGBTS, this Radio network plan

Equipment ID parameter is set to 0. (internal)
For a NodeB, two
baseband boards are
required (set to 1 and
2, respectively).
Baseband BASEBANDEQMTY For an eGBTS, this Radio network plan

Equipment Type PE parameter is set to (internal)
ULDL. For a NodeB,
BASEBANDEQMI
D 1 and
BASEBANDEQMI
D 2 are set to UL and
DL, respectively.
UMTS UL UMTSDEMMODE For an eGBTS, this Radio network plan

Demodulation parameter is invalid (internal)
Mode and should be set to
NULL. For a NodeB,
this parameter is set
based on the network
plan.

SingleRAN
Parameter Parameter ID Setting Notes Data Source

Name
Baseband BASEBANDEQMBO This parameter is set Equipment plan

Equipment ARD based on the cabinet
Board number, subrack
number, and slot
number of the
baseband processing
board.
9.4.3 Precautions
None

N/A
9.4.5 Activation
Using MML Commands
NodeB
Step 1 Run the MML command ADD BRD to add BBPs.

Step 2 Run the MML command ADD BASEBANDEQM to add all BBPs requiring backup to the
same baseband equipment. Set the UL and DL baseband equipment types, respectively.
----End
GBTS
Run the MML command ADD BTSBRD to add two UBBPs.
eGBTS
Step 1 Run the MML command ADD BRD to add UBBPs.

Step 2 Run the MML command ADD BASEBANDEQM to add the baseband equipment.
----End

NodeB
ADD BRD: CN=0, SRN=0, SN=2, BT=UBBP, BBWS=GSM-0&UMTS-1&LTE_FDD-0&LTE_TDD-0;
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

SingleRAN
ADD BTSBRD: IDTYPE=BYID, BTSID=120, CN=0, SRN=0, SN=0, BT=UBBP;

ADD BTSBRD: IDTYPE=BYID, BTSID=120, CN=0, SRN=0, SN=1, BT=UBBP;
eGBTS
ADD BASEBANDEQM: BASEBANDEQMID=0, UMTSDEMMODE=NULL, BASEBANDEQMTYPE=ULDL,
UMTSDEMMODE=NULL, CN1=0, SRN1=0, SN1=0, CN2=0, SRN2=0, SN2=1;

On the CME, set the parameters listed in the 9.4.2 Data Preparation section for a single base
station. For instructions on how to perform the CME single configuration, see CME Single
Using the CME to Perform Batch Modification

This feature does not support batch modification using the CME.

Step 1 Query the carriers deployed on each BBP.
l GBTS: Run the MML command DSP BTSBRDBBINFO to query the carriers deployed
on each BBP.
l eGBTS: Run the MML command DSP GTRX to query the carriers deployed on each
BBP.
l NodeB: Run the MML command DSP ULOCELLRES to query the cells served by
each BBP.
Step 2 Run the MML command BLK BRD to block one BBP. Cells served by this BBP will be
dynamically reestablished on another operational BBP and services will automatically
recover.
----End
9.4.7 Deactivation
This feature does not need to be deactivated.
N/A

N/A

N/A

SingleRAN
9.7 Troubleshooting
Table 9-4 lists alarms related to the Inter-Board Baseband Resource Redundancy feature for
the NodeB. If an alarm described in Table 9-4 is generated, clear the alarm by referring to the
alarm handling suggestions in 3900 Series Base Station Alarm Reference.

Type Severity Manage
ment
Type
ALM-26200 Board Hardware Fault Fault Major/ Hardware

Minor system
ALM-26204 Board Not In Position Fault Major Hardware

system
ALM-26210 Board Blocked Fault Major Operating

system
ALM-26214 Board Powered Off Fault Major Hardware

system

SingleRAN
Description Resource Redundancy (LTE)
10 Engineering Guidelines for Inter-Board

Baseband Resource Redundancy (LTE)
10.1 When to Use Inter-Board Baseband Resource

Redundancy (LTE)
When a BBP fails or some resources of the BBP become unavailable, the cells served by the
failed BBP cannot be dynamically reestablished on the BBP due to resource insufficiency.
With Inter-Board Baseband Resource Redundancy for LTE, the cells served by the failed BBP
can be reestablished on another operational BBP with available resources or on a backup BBP,
if available. This ensures that services can recover automatically, reduces service interruption
duration, and improves eNodeB reliability.

This section describes information required before deploying Inter-Board Baseband Resource
Redundancy for LTE.
The following table describes the parameters that must be set in an RRUCHAIN MO.
Parameter Parame Descriptio Setting Notes Data

Name ter ID n Source
Topo Type TT This Set this parameter to Network

parameter RING(RING). plan
indicates the (negotiatio
type of the n not
topology. required)
Backup BM This Set this parameter to Network

Mode parameter COLD(COLD) or HOT(HOT) plan
indicates the based on the network plan. (negotiatio
backup n not
mode. required)

SingleRAN
The following table describes the parameters that must be set in an RRU MO.
Parameter Paramet Descripti Setting Notes Data

Name er ID on Source
RRU Chain RCN This Set this parameter based on the Network
No. parameter network plan. plan
indicates
the ID of
the RRU
chain/ring.
RRU PS This If the RRUCHAIN BM Network

Position parameter parameter in the associated plan
indicates RRUCHAIN MO is set to
the RRU COLD(COLD), RRUs are
position. installed into different positions.
For example, the two RRUs in a
two-level ring are installed into
positions 0 and 1, respectively.
If the RRUCHAIN BM
parameter in the associated
RRUCHAIN MO is set to
HOT(HOT), the RRU in a one-
level ring is installed into
position 0.
10.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
The eNodeB is configured with two or more LBBPs or UBBPs. This feature applies only to
macro base stations and LampSite base stations that use BBU3900 or BBU3910.
10.4 Deployment

SingleRAN
10.4.1 Requirements
Hardware
l The eNodeB is configured with two or more LBBPs or UBBPs.
l The LBBPcs that achieve redundancy must both be LBBPc. The LBBPd and UBBP can
be a backup board for each other.
License
None

Table 10-1 describes the key parameters that must be set for a BBP.
Table 10-1 Key parameters configured for a BBP

Name ID
Cabinet No. CN Set this parameter to 0. Network plan

(negotiation not
required)
Subrack No. SRN Set this parameter to 0. Network plan

(negotiation not
required)
Slot No. SN Set this parameter to 1 and 3 for Network plan

two BBPs, respectively. (negotiation not
required)
Board Type TYPE Set this parameter to LBBP for Network plan
an LBBP board. (negotiation not
Set this parameter to UBBP for required)
a UBBP board.
Work Mode WM This parameter must be Network plan

specified for an LBBP board. (negotiation not
For LTE (FDD), set this required)
parameter to FDD. For LTE
(TDD), set this parameter to
TDD.
Base Band BBWS This parameter must be Engineering

Work Standard specified for a UBBP board. Set Design
this parameter to the modes for
which the UBBP board provides
baseband processing resources.
Table 10-2 describes the key parameters that must be set in an RRUCHAIN MO.

SingleRAN
Table 10-2 Key parameters for configuring RRU chains

Name ID
Topo Type TT Set this parameter to Network plan

RING(RING). (negotiation not
required)
Backup Mode BM Set this parameter to Network plan

COLD(COLD) or HOT(HOT) (negotiation not
based on the network plan. required)
Head Cabinet HCN Set these parameters based on Network plan

No. hardware connections. (negotiation not
required)
Head Subrack HSRN Network plan

No. (negotiation not
required)
Head Slot No. HSN Network plan

(negotiation not
required)
Head Port No. HPN Network plan

(negotiation not
required)
Tail Cabinet No. TCN Network plan

(negotiation not
required)
Tail Subrack TSRN Network plan

No. (negotiation not
required)
Tail Slot No. TSN Network plan

(negotiation not
required)
Tail Port No. TPN Network plan

(negotiation not
required)
Table 10-3 describes the key parameters that must be set in an RRU MO.

SingleRAN
Table 10-3 Key parameters for configuring RF units

Name ID
RRU Chain No. RCN Set this parameter based on the Network plan
network plan.
RRU Position PS If the RRUCHAIN BM Network plan

COLD(COLD), RRUs are
installed into different positions.
For example, the two RRUs in a
two-level ring are installed into
positions 0 and 1, respectively.
If the RRUCHAIN BM
HOT(HOT), the RRU in a one-
level ring is installed into
position 0.
10.4.3 Precautions
None

Connect RRUs to BBPs by referring to Figure 3-1. You can connect all RRUs to one ring.
l If cold backup rings are used, the two BBPs can be configured in any slots.
l If hot backup rings are used, the two BBPs must be configured in the slots specified in
the following table.
If... Then...
Two LBBPc boards One LBBPc board must be configured in slot 2 or 3, and the
are to be configured other LBBPc can be configured in any slot from slot 0 to slot
5. A maximum of three hot backup rings are supported.
An LBBPc board can be configured with only one hot
backup LBBPc board at a time.
Two LBBPd boards, One BBP board must be configured in slot 2 or 3, and the
two UBBP boards, or other BBP can be configured in any slot from slot 0 to slot 5.
one LBBPd and one A maximum of six hot backup rings are supported.
UBBP board are to be
configured

SingleRAN
10.4.5 Activation
Using MML Commands
You must remove the configurations of all boards before modifying the configurations related
to subracks and cabinets. Therefore, you must perform the operations described below locally.
You are not advised to use MML commands to initially configure newly deployed eNodeBs.
Before delivery of the 3900 series base stations, the main equipment has been preconfigured.
Before reconfiguring the site type and cabinets, query the configurations of the main
equipment by running the LST ENODEBFUNCTION and LST CABINET commands and
remove configurations of all main equipment. Remove and add configurations in the
following order:
l Remove cells, sector, RRUs, RRU chains, and boards, successively.
l Configure boards, RRU chains, and RRUs, successively. Then modify RRU chains.
NOTE
The execution of RMV BRD or ADD BRD may lead to eNodeB reset.
Scenario 1: Setting up a Cell on a Cold Backup Ring
Step 1 Run the ADD BRD command to add a board.

Step 2 Run the ADD RRUCHAIN command to add an RRU ring.
Set Topo Type to RING and Backup Mode to HOT when configuring the RRU ring.
Step 3 Run the MOD RRUCHAIN command to add breakpoints on the RRU ring before adding the
RRU.
Step 4 Run the ADD RRU command to add an RRU.
Step 5 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding
all the RRUs.
----End
Scenario 2: Setting up a Cell on a Hot Backup Ring
Step 1 Run the ADD BRD command to add a board.

Step 2 Run the ADD RRUCHAIN command to add an RRU ring.
Step 3 Set Topo Type to RING and Backup Mode to COLD when configuring the RRU ring.
RRU.
Step 5 Run the ADD RRU command to add an RRU.
Step 6 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding
all the RRUs.
----End


SingleRAN
ADD BRD: SN=1, BT=LBBP;

ADD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HSN=1, HPN=0, TSN=3, TPN=0;
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=LRRU, RS=LO, RXNUM=2,
TXNUM=2;

ADD RRUCHAIN: RCN=0, TT=RING, BM=HOT, HSN=1, HPN=0, TSN=3, TPN=0;
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=LRRU, RS=LO, RXNUM=2,
TXNUM=2;

On the CME, set the parameters listed in the 10.4.2 Data Preparation section for a single
NodeB. For instructions on how to perform the CME single configuration, see CME Single

NOTE
When configuring a feature on the CME, perform a single configuration first, and then perform a batch
modification if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
The default display style of the U2000 client is the application style. However, traditional style is more
convenient for operations described in this document. All operation guides related to the U2000 client
described in this document is based on the traditional style.
To change the display change to the traditional style, choose System > Preferences > Client Display
Style in the upper left corner of the U2000 client main window.
NOTE
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-1, Table 10-2, and
Table 10-3 and then close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.

SingleRAN
----End

On the U2000 client or LMT, perform the following steps to check whether Inter-Board
Baseband Resource Redundancy has been activated in a cold backup ring scenario.
Step 1 Check the status of the cell.

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 LBBP information to
identify the BBP on which the cell is established.
Step 2 Check whether the cell is functional by using UEs to access the cell.
If the UEs can successfully access the cell, the cell is functional.
Step 3 Trigger cell reestablishment by running the BLK BRD command to block the BBP on which
the cell is established.
Step 4 Repeat Step 1 and Step 2.
If the values of the parameters are the same as those in Step1, the cell is functional, the cell
has been reestablished on another BBP, and Inter-Board Baseband Resource Redundancy has
been activated in a cold backup ring scenario.
----End

On the U2000 client or LMT, perform the following steps to check whether Inter-Board
Baseband Resource Redundancy has been activated in a hot backup ring scenario.

Normal, the cell has been activated. Then, check the value of Primary LBBP information to
identify the BBP on which the cell is established.
Step 2 Check whether the cell is functional by using UEs to access the cell and start UDP services.
If the UEs can successfully access the cell and retain their RRC connections, and the data
rates of the UDP services are stable, the cell is functional.
Step 3 Run the BLK CPRIPORT command to block the CPRI port on which the cell is established.
Alternatively, remove the fiber optic cable from the current baseband processing board. Either
of the operations causes the cell to use a CPRI port on another baseband processing board and
the following can be observed:
Cell reestablishment is not triggered but the UEs can still retain their RRC connections. The
UDP data rates do not fluctuate greatly.

SingleRAN
Normal, the cell has been activated. Check the value of Bbi slot to determine the BBP on
which the cell is currently established. If the BBP on which the cell is established stays the
same and Inter-Board Baseband Resource Redundancy has been activated in a hot backup
ring scenario.
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
10.4.7 Deactivation
To deactivate Inter-Board Baseband Resource Redundancy, remove the preceding
configurations. Add breakpoints on the RF unit ring according to the MML command
prompts and MML command help before removing the RF units. To remove an RF unit from
a ring, you need to interrupt the logical connection between the RF unit and the BBP and then
remove the physical connections.
NOTE
To remove an RF unit from a ring, you need to interrupt the logical connection between the RF unit and
the BBP and then remove the physical connections. To interrupt the logical connection, run the MOD
RRUCHAIN command to add two break points to the ring, with one's position being 0 and the other's
position being a value equal to the number of RF units on the ring.
Using MML Commands

NOTE
The execution of RMV BRD may lead to an eNodeB reset.
Step 1 Run the RMV CELL command to remove the cell.
Step 2 Run the RMV SECTOR command to remove the sector.
RRU.
Step 4 Run the RMV RRU command to remove the RRU.
Step 5 Run the RMV RRUCHAIN command to remove the RRU ring.
Step 6 Run the RMV BRD command to remove the board.
----End

RMV CELL: LocalCellId=0;
RMV SECTOR: SECTORID=0;
RMV RRU: CN=0, SRN=60, SN=0;
RMV RRUCHAIN: RCN=0;
RMV BRD: SN=2;

SingleRAN

Configure the MO described in Table 10-4 on the CME configuration interface. For
Operation Guide.

1 CELL Remove the configuration data of the

cell.
2 SECTOR Remove the configuration data of the

sector.
3 RRUCHAIN Set breakpoints of the RRU chain or

ring.
4 RRU Remove the configuration data of the

RRU.
5 RRUCHAIN Remove the configuration data of the

RRU chain or ring.
6 BBP Remove the configuration data of the

baseband board.

You cannot use the CME to perform batch configuration to deactivate the Inter-Board
Baseband Resource Redundancy feature.
N/A

N/A

N/A
10.7 Troubleshooting
Table 10-5 lists alarms related to the Inter-Board Baseband Resource Redundancy feature for
the eNodeB. If an alarm described in Table 10-5 is generated, clear the alarm by referring to
the alarm handling suggestions in 3900 Series Base Station Alarm Reference.

SingleRAN

Type Severity Manage
ment
Type
ALM-26210 Board Blocked Fault Major Operating

system
ALM-26234 BBU CPRI Interface Error Fault Major Hardware

system
ALM-26235 RF Unit Maintenance Link Failure Fault Major Hardware

system
ALM-26236 RRU Cascading Levels and Fault Major Hardware

ALM-26238 RRU Network Topology Type and Fault Major Hardware


SingleRAN
Base Station Equipment Reliability Feature Parameter 11 Engineering Guidelines for Intra-Board Baseband
Description Resource Pool (LTE)
11 Engineering Guidelines for Intra-Board

Baseband Resource Pool (LTE)
11.1 When to Use Intra-Board Baseband Resource Pool

(LTE)
This feature is activated by default.

N/A
11.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
11.4 Deployment

SingleRAN
11.4.1 Requirements
Hardware
eNodeBs use LBBPc boards.
License
None

None
11.4.3 Precautions
None

None
11.4.5 Activation
The Intra-Board Baseband Resource Pool feature for LTE is activated by default.
To observe this feature, see the engineering guidelines section in Cell Management Feature
Parameter Description. The Intra-Board Baseband Resource Pool for LTE has different
requirements on cell configurations as described below.
Scenario 1: Intra-Board Cell-Level Resource Pool

Configure three 2T2R, three 1T2R, or three 1T1R cells for Intra-Board Cell-Level Resource
Pool for multiple cells.
Configure one 4T4R cell with a bandwidth of 20 MHz or one 4T4R cell with the bandwidth
of 15 MHz for Intra-Board Cell-Level Resource Pool for a single cell.
Scenario 2: Intra-Board User-Level Resource Pool

Configure one 4T4R cell with the bandwidth of 20 MHz or one 4T4R cell with the bandwidth
of 15 MHz.
For details, see the engineering guidelines section in Cell Management Feature Parameter
Description.
Scenario 1: Intra-Board Cell-Level Resource Pool

The prerequisite for activation observation is that a DSP chip on the LBBP is faulty and
ALM-26200 Board Hardware Fault is reported. Perform the following steps on the U2000 or
LMT to check whether the Intra-Board Cell-Level Resource Pool takes effect:

SingleRAN
NOTE
If any hardware unit on the LBBP is faulty, ALM-26200 Board Hardware Fault is reported. Intra-Board
Cell-Level 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 query the cell status and the LBBP that serves the cell.
If Cell instance state is Normal, the cell has been activated. Only one LBBP serves the cell.
Step 2 Check whether the cell is functional by using UEs to access the cell.
If the UEs can successfully access the cell and work properly, the cell is functional and Intra-
Board Cell-Level Resource Pool takes effect.
----End
Scenario 2: Intra-Board User-Level Resource Pool

The prerequisites for activation observation are that the cell configuration is complete, at least
two UEs have accessed the cell, and the UEs are performing uplink services such as FTP
services. Perform the following operation on the U2000 or LMT to check whether Intra-Board
User-Level Resource Pool takes effect:
Run the DSP CPUUSAGE command with Cabinet No., Subrack No., and Slot No. set to
the cabinet number, subrack number, and slot number of the LBBP, respectively, to query the
DSP chip loads.
The DSP chip loads depend on the number of UEs and the traffic volume of services. If the
loads of three DSP chips on an LBBP are similar, Intra-Board User-Level Resource Pool takes
effect.
11.4.7 Deactivation
N/A
N/A

N/A

N/A
N/A

SingleRAN
Base Station Equipment Reliability Feature Parameter 12 Engineering Guidelines for Intelligent Shutdown of
Description Carriers Due to PSU Failure
12 Engineering Guidelines for Intelligent

Shutdown of Carriers Due to PSU Failure
12.1 When to Use Intelligent Shutdown of Carriers Due to

PSU Failure
For macro base stations and LampSite base stations, basic power modules such as PMU and
PSU must be configured to ensure the power supply and power distribution functions. It is
recommended that the Intelligent Shutdown of Carriers Due to PSU Failure feature be
activated for Huawei AC-powered base stations configured with the PMU and PSU.

N/A
12.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
12.4 Deployment

SingleRAN
12.4.1 Requirements
Hardware
l The PMU and PSU must be provided by Huawei.
l For details about how to install the PMU and PSU, see "Monitoring Signal Cable
Connections" in the "Cable Connections" section of 3900 Series Base Station Cables.
License
None

Table 12-1 describes the parameters that must be set in the BTSPSUFP MO for activating
this feature in a GBTS.
Table 12-1 Parameters for activating this feature in a GBTS

MO Paramet Parameter Description Data
er Name ID Source
BTSPS Tran. ISTRANCAB If this parameter is set to Network

UFP Cabinet CON CONFIG(CONFIG), the power plan
Configure consumption of transmission
d cabinet must be considered. You
are advised to set this parameter to
ENABLE.
GTRX Is Main ISMAINBCC This parameter indicates whether to Network

BCCH H enable the TRX to carry the main plan
TRX BCCH in the cell.
BTSPS Service SRVPRIPOL This parameter specifies which Network

UFP Priority ICY type of service should be plan
Policy preferentially processed when the
PSU is faulty.
TRXBI TRX TRXTP This parameter indicates the type Network

ND2PH Board of the TRX board bound to the plan
YBRD Type TRX.
Table 12-2 describes the parameter that must be set in the EQUIPMENT MO for activating
this feature in an eGBTS, NodeB, or eNodeB.

SingleRAN
Table 12-2 Parameter for activating this feature in an eGBTS, NodeB, or eNodeB
MO Paramet Parameter Description Data
er Name ID Source
EQUIP PSU PSUFP This parameter indicates whether Network

MENT Fault the BS enters the energy saving plan
Shutdow mode when some PSUs become
n TRX faulty. If this parameter is set to
Enabled ON, the BS enters the energy
saving mode to reduce power
consumption when some PSUs
become faulty and the remaining
PSUs cannot meet the BS's power
requirements. In energy saving
mode, the BS shuts down TRXs or
reduces their transmit power.
12.4.3 Precautions
None

None
12.4.5 Activation
Using MML Commands
GBTS
Run the SET BTSPSUFP command to configure the parameters of the Intelligent Shutdown
of Carriers Due to PSU Failure feature.
l Set Board Parameter Configuration Enabled to YES(YES).
l Set Tran. Cabinet Configured based on the actual configurations on the BTS.
l Set Service Priority Policy to GSM_PRIOR(GSM Traffic Prior).
l Do not specify GSM Multi Carrier BTS Standard.
eGBTS/NodeB/eNodeB
Run the SET EQUIPMENT command to set PSU Fault Shutdown TRX Enabled to
ON(ON) to enable the Intelligent Shutdown of TRX Due to PSU Failure feature.

GBTS
SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=YES,
ISTRANCABCON=CONFIG,SRVPRIPOLICY=GSM_PRIOR;
eGBTS/NodeB/eNodeB

SingleRAN
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=ON;

Only GBTS supports the single configuration using the CME.
On the CME, set the parameters listed in the 12.4.2 Data Preparation section for a GBTS.
For instructions on how to perform the CME single configuration, see CME Single

This feature does not support batch modification using the CME.
GBTS
Step 1 Run the LST BTSPSUFP command to query the parameters about TRX shutdown due to
PSU failures.
l Expected result:
– The value of Board Parameter Configuration Enabled is YES.
– The value of Tran. Cabinet Configured is consistent with that configured in the
activation procedure.
– The value of Service Priority Policy is GSM_PRIOR(GSM Traffic Prior).
Step 2 Remove some PSUs from the BTS. Ensure that the power supplied by remaining PSUs cannot
meet requirements of all TRXs at the site but can meet requirements of other devices.
Step 3 Run the DSP CHNSTAT command to query the channel status of all TRXs at the site. In this
step, set Object Type to SITE(Site).
Expected result: Some channels on TRXs are available and some are not. The GBTS 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

SingleRAN
12.4.7 Deactivation
Using MML Commands
GBTS
Run the SET BTSPSUFP command with Board Parameter Configuration Enabled set to
NO(NO).
eGBTS/NodeB/eNodeB
Run the SET EQUIPMENT command to disable the Intelligent Shutdown of Carriers Due to
PSU Failure feature. In this step, set PSU Fault Shutdown TRX Enabled to OFF(OFF).

GBTS
SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=NO;
eGBTS/NodeB/eNodeB
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=OFF;

Set the parameters described in Table 12-3 or Table 12-4 on the CME configuration interface.
For instructions on how to perform the CME single configuration, see CME Single
Table 12-3 Configuring the parameter on the CME (GBTS)

SN MO NE Parameter Parameter Setting
Name ID Notes
1 BTSPSUFP BSC6900/ Board CFGFLAG To

BSC6910 Parameter deactivate
Configuratio this feature,
n Enabled set this
parameter to
NO.
Table 12-4 Configuring the parameter on the CME (eGBTS/NodeB/eNodeB)

SN MO NE Parameter Parameter Setting
Name ID Notes
1 EQUIPMENT eGBTS/ PSU Fault PSUFP To

NodeB/ Shutdown deactivate
eNodeB TRX this feature,
Enabled set this
parameter to
OFF.

SingleRAN

You cannot use the CME to perform batch configuration to deactivate the Intelligent
Shutdown of Carriers Due to PSU Failure feature.
N/A

N/A

N/A
Table 12-5 lists alarms related to Intelligent Shutdown of Carriers Due to PSU Failure. If an
alarm described in Table 12-4 is generated, clear the alarm by referring to alarm handling
suggestions in 3900 Series Base Station Alarm Reference.

Alarm ID Alarm Name Alarm Severity
25630 Power Module and Monitoring Module Major

Communication Failure
25626 Power Module Abnormal Major/Warning

SingleRAN
Description 13 Parameters
13 Parameters
Table 13-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
SECTO SECTO ADD None None Meaning: Indicates the number of the sector.
R RID SECTO GUI Value Range: 0~65535
R
Unit: None
DSP
SECTO Actual Value Range: 0~65535
R Default Value: None
LST
SECTO
R
MOD
SECTO
R
RMV
SECTO
R
SECTO SECTO None None None Meaning: Indicates the information about the sector
R RANTE antenna.
NNA GUI Value Range: 0~576
Unit: None
Actual Value Range: 0~576
Default Value: None

SingleRAN

nd
MPT CN LST None None Meaning: Indicates the cabinet number of the main
MPT control and transmission board.
MOD GUI Value Range: 0~7
MPT Unit: None
Default Value: None
MPT SRN LST None None Meaning: Indicates the subrack number of the main
MPT Unit: None
Default Value: None
MPT SN LST None None Meaning: Indicates the slot number of the main
MPT Unit: None
Default Value: None
MPT TYPE None None None Meaning: Indicates the type of the board.
GUI Value Range: UMPT(UMPT), WMPT(WMPT),
LMPT(LMPT)
Unit: None
Actual Value Range: UMPT, WMPT, LMPT
Default Value: None
HAGRP CN ADD LBFD-0 Main Meaning: Indicates the number of the cabinet housing
HAGRP 0202101 Processi the board where the HA group is established.
RMV ng and GUI Value Range: 0~7
MRFD- Transpo
HAGRP 210101 Unit: None
rt Unit
LST Cold Actual Value Range: 0~7
HAGRP Backup Default Value: 0
System
Redunda
ncy

SingleRAN

nd
HAGRP SRN ADD LBFD-0 Main Meaning: Indicates the number of the subrack housing
HAGRP 0202101 Processi the board where the HA group is established.
RMV ng and GUI Value Range: 0~1
MRFD- Transpo
HAGRP 210101 Unit: None
rt Unit
LST Cold Actual Value Range: 0~1
HAGRP Backup Default Value: 0
System
Redunda
ncy
HAGRP SN ADD LBFD-0 Main Meaning: Indicates the logical slot number of the HA
HAGRP 0202101 Processi group. The logical slot number of an HA group is the
RMV ng and number of the physical slot housing one of the two
MRFD- Transpo boards constituting the HA group.
HAGRP 210101 rt Unit GUI Value Range: 6~7
LST Cold
HAGRP Backup Unit: None
System
Redunda Default Value: 6
ncy
RRUCH TT ADD None None Meaning: Indicates the type of the topology. In a ring
AIN RRUCH topology, the service data is transmitted on the fiber
AIN optic cable that carries the HDLC link. In a load
MOD sharing topology, the service data is transmitted on
RRUCH two fiber optic cables simultaneously, which enhances
AIN the transmission capability. The physical connection
in the ring topology is similar to that in the load
DSP sharing topology.
RRUCH
AINPH GUI Value Range: CHAIN(CHAIN), RING(RING),
YTOPO LOADBALANCE(LOADBALANCE)
LST Unit: None
RRUCH Actual Value Range: CHAIN, RING,
AIN LOADBALANCE
Default Value: None

SingleRAN

nd
RRUCH BM ADD None None Meaning: Indicates the backup mode of the RRU
AIN RRUCH chain/ring. There are two modes: cold backup and hot
AIN backup. Cold backup indicates that when the link on
MOD one end of the chain/ring fails, the service is disrupted
RRUCH for a short period of time, and then re-established on
AIN the other end of the chain/ring. Hot backup indicates
that when the link on one end of the chain/ring fails,
LST the service is taken over by the other end of the chain/
RRUCH ring immediately. There is only one RRU on the
AIN chain/ring in hot backup mode. In the RRUCHAIN
MO, if TT is set to RING and BM is set to HOT, the
head CPRI port and the tail CPRI port of the RRU
ring must be on different baseband boards.
GUI Value Range: COLD(COLD), HOT(HOT)
Unit: None
Actual Value Range: COLD, HOT
Default Value: COLD(COLD)
RRU RCN ADD None None Meaning: Indicates the ID of the RRU or RFU chain/
RRU ring.
LST GUI Value Range: 0~249
RRU Unit: None
Default Value: None
RRU PS ADD None None Meaning: Indicates the position of the RRU, RFU, or
RRU RHUB on the chain or ring. It is calculated from the
LST start port one by one.
RRU GUI Value Range: 0~20
Unit: None
Default Value: None
BBP CN DSP None None Meaning: Indicates the cabinet number of the
BBPTC baseband processing board.
BBP Unit: None
MOD Actual Value Range: 0~7
BBP
Default Value: 0

SingleRAN

nd
BBP SRN DSP None None Meaning: Indicates the subrack number of the
BBPTC baseband processing board.
BBP Unit: None
MOD Actual Value Range: 0~1
BBP
Default Value: 0
BBP SN DSP None None Meaning: Indicates the slot number of the baseband
BBPTC processing board. Baseband processing boards can be
LST configured only in slots 0 to 5 and the multimode
BBP digital unit can be configured only in slot 6.
BBP Unit: None
Default Value: None
BBP TYPE MOD None None Meaning: Indicates the type of the board.
BBP GUI Value Range: UBBP(UBBP), GBBP(GBBP),
WBBP(WBBP), LBBP(LBBP), LPMP(LPMP)
Unit: None
Actual Value Range: UBBP, GBBP, WBBP, LBBP,
LPMP
Default Value: None

SingleRAN

nd
BBP WM ADD None None Meaning: Indicates the working mode of the baseband
BRD processing board. There are seven working modes:
MOD FDD, TDD, HYBRID, TDD_ENHANCE,
BBP TDD_8T8R, TDD_TL and FDD_ATG. The
Frequency Division Duplex (FDD) mode carries the
LST traditional voice and data services. TDD is short for
BBP Time Division Duplex. The HYBRID mode is a
combination of FDD and IMB modes. In Integrated
Mobile Broadcasting (IMB) mode, the baseband
processing board carries the mobile TV services. The
value TDD_ENHANCE indicates the TDD mode
integrated with the BeamForming (BF) function. The
BF function provides the data transmission service in
transmission modes 7 and 8 defined in protocols. For
details, see 3GPP TS 36.213. In TDD_8T8R mode,
the baseband processing board supports TD-LTE
single-mode 8T8R. In addition, the baseband
processing board supports the BF function and CPRI
specifications are applied between the BBU and RRU.
In TDD_TL mode, the baseband processing board
supports the TD-LTE&TDS-CDMA dual mode and
the TD-LTE single mode. In addition, the baseband
processing board supports 8T8R BF and 2T2R
Multiple-Input Multiple-Output (MIMO) and CMCC
TD-LTE IR specifications are applied between the
BBU and RRU. In FDD_ATG mode, the baseband
processing board supports communication between
Air and Ground. The FDD_ATG mode applies only to
communication between air and ground.
GUI Value Range: FDD(Frequency Division Duplex),
TDD(Time Division Duplex), HYBRID(HYBRID),
TDD_ENHANCE(Support TDD BF),
TDD_8T8R(Support CPRI ports), TDD_TL(Support
CMCC TDS and TDL dual modes),
FDD_ATG(Support air-ground communication)
Unit: None
Actual Value Range: FDD, TDD, HYBRID,
TDD_ENHANCE, TDD_8T8R, TDD_TL, FDD_ATG
Default Value: FDD(Frequency Division Duplex)

SingleRAN

nd
BBP BBWS ADD None None Meaning: Indicates the modes for which the UBBP or
BRD UMDU provides baseband processing resources. If the
MOD UBBP or UMDU provides only CPRI ports for a
BBP mode, you do not need to configure this mode for the
UBBP or UMDU.
LST
BBP GUI Value Range: GSM(GSM), UMTS(UMTS),
LTE_FDD(LTE FDD), LTE_TDD(LTE TDD)
Unit: None
Actual Value Range: GSM, UMTS, LTE_FDD,
LTE_TDD
Default Value: GSM:NO, UMTS:NO, LTE_FDD:NO,
LTE_TDD:NO
RRUCH HCN ADD None None Meaning: Indicates the cabinet number of the board
AIN RRUCH where the head CPRI port is located.
AIN GUI Value Range: 0~7
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~7
DSP Default Value: 0

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN
RRUCH HSRN ADD None None Meaning: Indicates the subrack number of the board
AIN GUI Value Range: 0~1,60~254
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~1,60~254
DSP Default Value: 0

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN

SingleRAN

nd
RRUCH HSN ADD None None Meaning: Indicates the slot number of the board
AIN GUI Value Range: 0~6
MOD Unit: None
RRUCH
AIN Actual Value Range: 0~6
DSP Default Value: None

RRUCH
AINPH
YTOPO
LST
RRUCH
AIN
RRUCH HPN ADD None None Meaning: Indicates the number of the head CPRI port.
AIN RRUCH GUI Value Range: 0~7
AIN
Unit: None
MOD
RRUCH Actual Value Range: 0~7
AIN Default Value: None
DSP
RRUCH
AINPH
YTOPO
LST
RRUCH
AIN
RRUCH TCN ADD None None Meaning: Indicates the cabinet number of the board
AIN RRUCH where the tail CPRI port is located.Value NULL is
AIN displayed for the RRU chain which does not have a
MOD tail CPRI port.
RRUCH GUI Value Range: 0~7
AIN Unit: None
DSP Actual Value Range: 0~7
RRUCH
AINPH Default Value: 0
YTOPO
LST
RRUCH
AIN

SingleRAN

nd
RRUCH TSRN ADD None None Meaning: Indicates the subrack number of the board
MOD tail CPRI port.
RRUCH GUI Value Range: 0~1,60~254
AIN Unit: None
DSP Actual Value Range: 0~1,60~254
RRUCH
AINPH Default Value: 0
YTOPO
LST
RRUCH
AIN
RRUCH TSN ADD None None Meaning: Indicates the slot number of the board
MOD tail CPRI port.
RRUCH GUI Value Range: 0~6
AIN Unit: None
DSP Actual Value Range: 0~6
RRUCH
AINPH Default Value: None
YTOPO
LST
RRUCH
AIN
RRUCH TPN ADD None None Meaning: Indicates the number of the tail CPRI port.
AIN RRUCH Value NULL is displayed for the RRU chain which
AIN does not have a tail CPRI port.
RRUCH Unit: None
AIN
DSP
RRUCH Default Value: None
AINPH
YTOPO
LST
RRUCH
AIN

SingleRAN

nd
EQUIP PSUFP SET GBFD-1 Intellige Meaning: Indicates whether the BS enters the energy
MENT EQUIP 17804 nt saving mode when some PSUs become faulty. If this
MENT Shutdow parameter is set to ON, the BS enters the energy
LST n of saving mode to reduce power consumption when
EQUIP TRX some PSUs become faulty and the remaining PSUs
MENT Due to cannot meet the BS's power requirements. In energy
PSU saving mode, the BS shuts down TRXs or reduces
Failure their transmit power.
GUI Value Range: ON(ON), OFF(OFF)
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF(OFF)

SingleRAN
Description 14 Counters
14 Counters
There are no specific counters associated with this feature.

SingleRAN
Description 15 Glossary
15 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

SingleRAN
Description 16 Reference Documents
16 Reference Documents
1. TRX Cooperation Feature Parameter Description for GBSS

2. RRU Redundancy Feature Parameter Description for RAN
3. 3900 Series Base Station Initial Configuration Guide
4. Power Supply Management Feature Parameter Description for SingleRAN
5. Cell Management Feature Parameter Description for eRAN


Base Station Equipment Reliability (SRAN10.1 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Base Station Equipment Reliability (SRAN10.1 - 02)

Uploaded by

Copyright:

Available Formats

SingleRAN

Base Station Equipment Reliability

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2016-04-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 02 (2016-04-30) Huawei Proprietary and Confidential ii

8 Engineering Guidelines for Cold Backup of Main Control Boards.................................. 35

9 Engineering Guidelines for Inter-Board Baseband Resource Redundancy

Issue 02 (2016-04-30) Huawei Proprietary and Confidential iii

10 Engineering Guidelines for Inter-Board Baseband Resource Redundancy (LTE)....... 51

11 Engineering Guidelines for Intra-Board Baseband Resource Pool (LTE)...................... 62

Issue 02 (2016-04-30) Huawei Proprietary and Confidential iv

11.5 Performance Monitoring.............................................................................................................................................64

12 Engineering Guidelines for Intelligent Shutdown of Carriers Due to PSU Failure....65

Issue 02 (2016-04-30) Huawei Proprietary and Confidential v

1 About This Document

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 1

Change Type Change Description Parameter Change

Feature change None None

Editorial change Modified some descriptions in None

SRAN10.1 Draft A (2015-01-15)

Change Type Change Description Parameter Change

Feature change Added the description as follows: None

Editorial change None None

1.4 Differences Between Base Station Types

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 2

Redund RF Channel GBTS: Y Y N N For details, see section

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 3

RRU Channel GBTS: N N Y N For details about the

Hardwa Cold Backup of GBTS: N Y Y N For details about the

Inter-Board GBTS: Y Y Y Y For details about the

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 4

Intra-Board GBTS: Y Y Y Y For details about the

Heat Dissipation GBTS: Y Y Y Y For details, see section

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 5

Power Supply GBTS: Y Y Y Y For details about the

Power Supply GBTS: Y Y Y Y For details about the

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 6

Anti- GBTS: Y Y Y Y For details, see section

Overtemperature GBTS: Y Y Y Y For details, see section

Surge Protection GBTS: Y Y Y Y For details, see section

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 7

3.1 RF Channel Cooperation

Table 3-1 Features involved in RF Channel Cooperation

GSM GBFD-113801 TRX Cooperation TRX Cooperation Feature Parameter

UMTS WRFD-040203 RRU RRU Redundancy Feature Parameter

3.2 RRU Channel Cross Connection Under MIMO

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 8

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 9

4.1 Cold Backup of Main Control Boards

GSM MRFD-210101 System Redundancy

UMTS MRFD-210101 System Redundancy

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 10

4.1.2 Active/Standby Competition

4.1.3 Data Backup

4.1.4 Active/Standby Switchover

l The active main control board experiences a major hardware fault.

Issue 02 (2016-04-30) Huawei Proprietary and Confidential 11