Date post: | 24-Feb-2018 |
Category: |
Documents |
Upload: | muhammad-abdur-razzaqe |
View: | 249 times |
Download: | 1 times |
of 87
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
1/87
SingleRAN
Base Station Equipment Reliability
Feature Parameter Description
Issue 01
Date 2015-03-23
HUAWEI TECHNOLOGIES CO., LTD.
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
2/87
Copyright Huawei Technologies Co., Ltd. 2015. 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 thepurchase 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: [email protected]
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
http://www.huawei.com/7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
3/87
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
4/87
4.9.1 Standards................................................................................................................................................................... 23
4.9.2 Surge Protection Capability of Different Ports..........................................................................................................24
5 Related Features...........................................................................................................................25
5.1 Prerequisite Features.....................................................................................................................................................255.2 Mutually Exclusive Features........................................................................................................................................ 25
5.3 Impacted Features.........................................................................................................................................................25
6 Network Impact........................................................................................................................... 26
6.1 System Capacity........................................................................................................................................................... 26
6.2 Network Performance...................................................................................................................................................26
7 Engineering Guidelines for RRU Channel Cross Connection Under MIMO.................27
7.1 When to Use RRU Channel Cross Connection Under MIMO.....................................................................................27
7.2 Required Information................................................................................................................................................... 27
7.3 Planning........................................................................................................................................................................27
7.4 Deployment.................................................................................................................................................................. 27
7.4.1 Requirements.............................................................................................................................................................28
7.4.2 Data Preparation........................................................................................................................................................ 28
7.4.3 Precautions.................................................................................................................................................................29
7.4.4 Hardware Adjustment................................................................................................................................................29
7.4.5 Activation.................................................................................................................................................................. 29
7.4.6 Activation Observation..............................................................................................................................................31
7.4.7 Deactivation...............................................................................................................................................................31
7.4.8 Reconfiguration......................................................................................................................................................... 327.5 Performance Monitoring...............................................................................................................................................32
7.6 ParameterOptimization................................................................................................................................................32
7.7 Troubleshooting............................................................................................................................................................32
8 Engineering Guidelines for Cold Backup of Main Control Boards.................................. 33
8.1 When to Use Cold Backup of Main Control Boards....................................................................................................33
8.2 Required Information................................................................................................................................................... 33
8.3 Planning........................................................................................................................................................................33
8.4 Deployment.................................................................................................................................................................. 35
8.4.1 Requirements.............................................................................................................................................................358.4.2 Data Preparation........................................................................................................................................................ 35
8.4.3 Precautions.................................................................................................................................................................36
8.4.4 Hardware Adjustment................................................................................................................................................36
8.4.5 Activation.................................................................................................................................................................. 36
8.4.6 Commissioning..........................................................................................................................................................39
8.4.7 Activation Observation..............................................................................................................................................40
8.4.8 Deactivation...............................................................................................................................................................40
8.4.9 Reconfiguration......................................................................................................................................................... 42
8.5 Performance Monitoring...............................................................................................................................................42
8.6 ParameterOptimization................................................................................................................................................42
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description Contents
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
iii
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
5/87
8.7 Troubleshooting............................................................................................................................................................42
9 Engineering Guidelines for Inter-Board Baseband Resource Redundancy(GSM&UMTS)................................................................................................................................ 43
9.1 When to Use Inter-Board Baseband Resource Redundancy (GSM&UMTS)..............................................................439.2 Required Information................................................................................................................................................... 43
9.3 Planning........................................................................................................................................................................43
9.4 Deployment.................................................................................................................................................................. 44
9.4.1 Requirements.............................................................................................................................................................44
9.4.2 Data Preparation........................................................................................................................................................ 44
9.4.3 Precautions.................................................................................................................................................................46
9.4.4 Hardware Adjustment................................................................................................................................................46
9.4.5 Activation.................................................................................................................................................................. 46
9.4.6 Activation Observation..............................................................................................................................................47
9.4.7 Deactivation...............................................................................................................................................................47
9.4.8 Reconfiguration......................................................................................................................................................... 47
9.5 Performance Monitoring...............................................................................................................................................47
9.6 ParameterOptimization................................................................................................................................................47
9.7 Troubleshooting............................................................................................................................................................48
10 Engineering Guidelines for Inter-Board Baseband Resource Redundancy (LTE)....... 49
10.1 When to Use Inter-Board Baseband Resource Redundancy (LTE)............................................................................49
10.2 RequiredInformation................................................................................................................................................. 49
10.3 Planning......................................................................................................................................................................50
10.4 Deployment................................................................................................................................................................ 50
10.4.1 Requirements...........................................................................................................................................................51
10.4.2 Data Preparation...................................................................................................................................................... 51
10.4.3 Precautions...............................................................................................................................................................53
10.4.4 Hardware Adjustment..............................................................................................................................................53
10.4.5 Activation................................................................................................................................................................ 54
10.4.6 Activation Observation............................................................................................................................................56
10.4.7 Deactivation.............................................................................................................................................................57
10.4.8 Reconfiguration....................................................................................................................................................... 58
10.5 Performance Monitoring.............................................................................................................................................58
10.6 Parameter Optimization..............................................................................................................................................58
10.7 Troubleshooting..........................................................................................................................................................58
11 Engineering Guidelines for Intra-Board Baseband Resource Pool (LTE)......................60
11.1 When to Use Intra-Board Baseband Resource Pool (LTE)........................................................................................ 60
11.2 RequiredInformation..................................................................................................................................................60
11.3 Planning...................................................................................................................................................................... 60
11.4 Deployment.................................................................................................................................................................60
11.4.1 Requirements........................................................................................................................................................... 61
11.4.2 Data Preparation...................................................................................................................................................... 61
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description Contents
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
iv
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
6/87
11.4.3 Precautions...............................................................................................................................................................61
11.4.4 Hardware Adjustment..............................................................................................................................................61
11.4.5 Activation.................................................................................................................................................................61
11.4.6 Activation Observation............................................................................................................................................61
11.4.7 Deactivation.............................................................................................................................................................62
11.4.8 Reconfiguration....................................................................................................................................................... 62
11.5 Performance Monitoring.............................................................................................................................................62
11.6 Parameter Optimization..............................................................................................................................................62
11.7 Troubleshooting..........................................................................................................................................................62
12 Engineering Guidelines for Intelligent Shutdown of Carriers Due to PSU Failure....63
12.1 When to Use Intelligent Shutdown of Carriers Due to PSU Failure..........................................................................63
12.2 Required Information................................................................................................................................................. 63
12.3 Planning......................................................................................................................................................................63
12.4 Deployment................................................................................................................................................................ 63
12.4.1 Requirements...........................................................................................................................................................64
12.4.2 Data Preparation...................................................................................................................................................... 64
12.4.3 Precautions...............................................................................................................................................................65
12.4.4 Hardware Adjustment..............................................................................................................................................65
12.4.5 Activation................................................................................................................................................................ 65
12.4.6 Activation Observation............................................................................................................................................66
12.4.7 Deactivation.............................................................................................................................................................67
12.4.8 Reconfiguration....................................................................................................................................................... 68
12.5 Performance Monitoring.............................................................................................................................................68
12.6 Parameter Optimization..............................................................................................................................................68
12.7 Troubleshooting..........................................................................................................................................................68
13 Parameters...................................................................................................................................69
14 Counters...................................................................................................................................... 79
15 Glossary.......................................................................................................................................80
16 Reference Documents...............................................................................................................81
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description Contents
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
v
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
7/87
1About 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 theproduct 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
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 1 About This Document
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
1
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
8/87
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
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, Issue Draft A (2015-01-15) of
SRAN10.0 includes the following changes.
Change Type Change Description Parameter Change
Feature change Added the description as follows:
eGBTS(GTMUb) does notsupport Cold Backup of Main
Control Boards feature. For
details, see 2 Overview2
Overview.
None
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
Base Station Equipment Reliability Feature Parameter
Description 1 About This Document
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
2
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
9/87
2OverviewThe 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-1describes the base station equipment reliability features/functions supported by
each mode. In this table, "Y" means "supported" and "N" means "not supported."
Table 2-1Base station equipment reliability features/functions supported by each mode
Reliabil
ity Type
Feature/Function Whether This Feature/Function
Is Supported
Description
G U L T
Redund
ancy
design
RF Channel
Cooperation
GBTS: Y
eGBTS: Y
Y N N For details, see section
3.1 RF Channel
Cooperation.
For details about the
principles and
engineering guidelines
for the GBTS and
eGBTS, see TRX
Cooperation Feature
Parameter Description.
For details about the
principles and
engineering guidelines
for the NodeB, seeRRU
Redundancy Feature
Parameter Description.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 2 Overview
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
3
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
10/87
RRU Channel
Cross
Connection
Under MIMO
GBTS: N
eGBTS: N
N Y N For details about the
principles and the
engineering guidelines
for RRU Channel Cross
Connection UnderMIMO, see section 3.2
RRU Channel Cross
Connection Under
MIMOand chapter 7
Engineering Guidelines
for RRU Channel
Cross Connection
Under MIMO,
respectively.
Hardwa
rereliabili
ty
Cold Backup of
Main ControlBoards
GBTS: N
eGBTS(GTMUb): N
eGBTS(U
MPT): Y
Y Y N For details about the
principles and theengineering guidelines
for Cold Backup of Main
Control Boards, see
section 4.1 Cold Backup
of Main Control
Boardsand chapter 8
Engineering Guidelines
for Cold Backup of
Main Control Boards.
Inter-Board
BasebandResource
Redundancy
GBTS: Y
eGBTS: Y
Y Y Y For details about the
principles of Inter-BoardBaseband Resource
Redundancy, see section
4.2 Inter-Board
Baseband Resource
Redundancy.
For details about the
engineering guidelines
for the GBTS, eGBTS,
and NodeB, see chapter
9 Engineering
Guidelines for Inter-
Board BasebandResource Redundancy
(GSM&UMTS).
For details about the
engineering guidelines
for the eNodeB, see
chapter 10 Engineering
Guidelines for Inter-
Board Baseband
Resource Redundancy
(LTE).
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 2 Overview
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
4
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
11/87
Intra-Board
Baseband
Resource Pool
GBTS: Y
eGBTS: Y
Y Y Y For details about the
principles of Intra-Board
Baseband Resource Pool,
see section 4.3 Intra-
Board BasebandResource 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 details about the
engineering guidelinesfor the eNodeB, see
chapter 11 Engineering
Guidelines for Intra-
Board Baseband
Resource Pool (LTE).
Heat Dissipation
Reliability for
Fans
GBTS: Y
eGBTS: Y
Y Y Y For details, see section
4.4 Heat Dissipation
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
Base Station Equipment Reliability Feature Parameter
Description 2 Overview
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
5
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
12/87
Power Supply
Redundancy
GBTS: Y
eGBTS: Y
Y Y Y For details about the
principles of Power
Supply Redundancy, see
section 4.5 Power
Supply Redundancy.For details about the
principles and
engineering guidelines
for Power Supply
Redundancy for a base
station, seePower
Supply Management
Feature Parameter
Description.
Power Supply
Redundancy for a BBUis a basic function and
does not require any
software configurations.
Power Supply
Reliability
GBTS: Y
eGBTS: Y
Y Y Y For details about the
principles of Power
Supply Reliability, see
section 4.6 Power
Supply Reliability.
For details about the
engineering guidelines of
the function of intelligentshutdown of carriers due
to PSU failure, see
chapter 12 Engineering
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, seePower Supply
Management Feature
Parameter Description.
Power Supply Reliability
for a BBU is a basic
function and does not
require any software
configurations.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 2 Overview
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
6
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
13/87
Anti-
Misinsertion
Design of
Boards
GBTS: Y
eGBTS: Y
Y Y Y For details, see section
4.7 Anti-Misinsertion
Design of Boards. This
is a basic function and
does not require anysoftware configurations.
Overtemperature
Protection for
BBU Boards
GBTS: Y
eGBTS: Y
Y Y Y For details, see section
4.8 Overtemperature
Protection for BBU
Boards. This is a basic
function and does not
require any software
configurations.
Surge Protection
Design
GBTS: Y
eGBTS: Y
Y Y Y For details, see section
4.9 Surge ProtectionDesign. This is a basic
function and does not
require any software
configurations.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 2 Overview
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
7
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
14/87
3Redundancy 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-1describes the features involved in RF Channel Cooperation. For details about these
features, see the corresponding feature parameter description.
Table 3-1Features involved in RF Channel Cooperation
Mode Feature Feature Parameter Description
GSM GBFD-113801 TRX Cooperation TRX Cooperation Feature Parameter
Description
UMTS WRFD-040203 RRU
Redundancy
RRU Redundancy Feature Parameter
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 maintenancedifficult. If one RRU or RFU fails, the entire sector may lose services for an extended period
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 3 Redundancy Design
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
8
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
15/87
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 twofiber 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-1RF 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
Base Station Equipment Reliability Feature Parameter
Description 3 Redundancy Design
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
9
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
16/87
4Hardware 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.
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
BRDcommand. 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
within 7 to 9 minutes. For details about secure networking scenarios, see TransmissionSecurity Feature Parameter Description.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
10
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
17/87
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 BRDcommand 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.
The prerequisites and methods for active/standby switchover vary with triggering conditions,as described in Table 4-1.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
11
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
18/87
Table 4-1Prerequisites and methods for active/standby switchover
Switchover Type
Prerequisites Method Remarks
Fault-triggered
switchov
er
The standby main control board isfunctioning properly, the links of the
standby board are normal, and the
standby board has no major hardware
faults.
The systemautomaticall
y triggers
the
switchover.
When the active maincontrol board
experiences major
faults, services
carried on this board
must be switched
over to the standby
main control board to
prevent service
interruption.
Therefore, the
switchover
prerequisites arerelatively simple.
Comman
d-
triggered
switchov
er
l The standby main control board is
functioning properly, the links of
the standby board are normal, and
the standby board has no major
hardware faults.
l The backup status of the active and
standby main control boards is
Idle. The backup status can be
queried by running the DSP
BKPSTATUScommand.
NOTE
The command-triggered switchover
cannot be performed before the initial
or routine backup between the active
and standby main control boards is
complete. Perform the command-
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 (includingdownloading 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.
A user
delivers a
command to
trigger the
switchover.
For details,
see chapter
8
Engineerin
gGuidelines
for Cold
Backup of
Main
Control
Boards.
Before a user delivers
a command to trigger
an active/standby
switchover, the base
station works
properly. The impact
of the switchover on
the base station must
be minimized.
Therefore, theswitchover
prerequisites are
relatively complex.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
12
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
19/87
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 withavailable 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-1illustrates 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 availablebaseband 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-1GBTS S2/2/2
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
13
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
20/87
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, seeRF Unit and Topology Management Feature Parameter Description.
Inter-Board Baseband Resource Redundancy for UMTS
Figure 4-2illustrates 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 onanother 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-2NodeB 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, seeRF Unit and Topology Management Feature Parameter Description.
Inter-Board Baseband Resource Redundancy for LTE
Figure 4-3illustrates 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 and hot backup
ring topology is formed. If one LBBP or UBBPd_L board fails due to a hardware fault or a
communication port failure, the eNodeB can detect and identify the fault and then attempt to
reestablish the cells served by the failed LBBP or UBBPd_L board on the other LBBP orUBBPd_L board. If more than two LBBP or UBBPd_L boards are configured, the eNodeB
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
21/87
chooses a target LBBP or UBBPd_L board by considering the available resources in all
candidate target LBBP or UBBPd_L boards. The target LBBP or UBBPd_L board connects to
the same RRU as the failed LBBP or UBBPd_L board and can serve one or multiple cells. 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-3LTE 3x10MHz 2T2R
NOTICE
l 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.
l Inter-board baseband resource redundancy for LTE is only supported in the inter-board
cold backup ring topology and hot backup ring topology.
4.3 Intra-Board Baseband Resource Pool
4.3.1 Overview
The following table lists the features involved in Inter-Board Baseband Resource Pool.
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)
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
15
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
22/87
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-4Intra-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 formultiple cells.
Figure 4-5Intra-board cell-level resource pool for multiple cells
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
16
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
23/87
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 unitrotate at full speed to ensure heat dissipation.
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.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
17
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
24/87
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 basestation 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" inPower 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.
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 DCoutputs.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
18
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
25/87
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 withthe 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
battery
management
GSM: GBFD-510710 Intelligent
Battery Management
Intelligent battery management
provides the following functions:
automatic switching between
different charge-and-dischargemodes, self-protection under high
temperature, and battery runtime
display.
UMTS: WRFD-140220Intelligent Battery Management
LTE FDD: LOFD-001071
Intelligent Battery Management
LTE TDD: TDLOFD-001071
Intelligent Battery Management
Automatic
battery and load
disconnection
GSM: GBFD-111601 BTS Power
Management
This is a basic function for
UMTS and LTE base stations and
does not have a feature ID.
Automatic battery and load
disconnection provides the
following functions: automatic
battery disconnection under low
voltage, automatic batterydisconnection under high
temperature, and automatic load
disconnection.
Intelligent
diesel generator
management
This is a basic function for GSM,
UMTS, and LTE base stations
and does not have a feature ID.
Base stations supplied with solar
power support intelligent diesel
generator management. Using
either RS485 or dry contact ports,
the PMU monitors the status, fuel
level, and faults of the diesel
generator.
Intelligent
shutdown of
carriers due to
PSU failure
GSM: GBFD-117804 Intelligent
Shutdown of TRX Due to PSU
Failure
This is a basic function for
UMTS and LTE base stations and
does not have a feature ID.
When some PSUs become faulty
and the remaining PSUs cannot
meet the base station's power
requirements, the base station
enters energy saving mode to
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.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
19
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
26/87
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, seePower 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 -20C to 60C. 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 bereset.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
20
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
27/87
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.
4.8 Overtemperature Protection for BBU BoardsWhen 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-26214Board 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-offthreshold.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
21
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
28/87
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 5C 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.
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.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
22
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
29/87
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 MultimodeBase 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
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)
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
23
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
30/87
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.
5 GE/FE Different surge protection solutions are provided in
indoor and outdoor scenarios and no surge protector
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
indoor and outdoor scenarios and no surge protector
is required.
9 AISG Built-in surge protection is used on the equipment
and no surge protector is required.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 4 Hardware Reliability
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
24
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
31/87
5Related Features
5.1 Prerequisite Features
None
5.2 Mutually Exclusive Features
None
5.3 Impacted FeaturesWhen 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.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 5 Related Features
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
25
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
32/87
6Network Impact
6.1 System Capacity
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 but not for GSM or
UMTS. 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. This has no impact on the system capacity of GSM or UMTS.
Other features have no impact on the system capacity.
6.2 Network PerformanceNo impact.
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description 6 Network Impact
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
26
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
33/87
7Engineering Guidelines for RRU ChannelCross Connection Under MIMO
7.1 When to Use RRU Channel Cross Connection UnderMIMO
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.
7.2 Required Information
N/A
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
7.4 Deployment
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description
7 Engineering Guidelines for RRU Channel Cross
Connection Under MIMO
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
27
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
34/87
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.
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-1describes the parameters for RRU Channel Cross Connection Under MIMO.
Table 7-1Parameters for RRU Channel Cross Connection Under MIMO
MO ParameterName
Parameter ID Setting Notes
Data Source
SECTOR Sector ID SECTORID None Network plan
(negotiation not required)
SECTOR Sector
Antenna
SECTORANTENNA None Network plan
(negotiation not required)
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description
7 Engineering Guidelines for RRU Channel Cross
Connection Under MIMO
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
28
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
35/87
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 CommandsAdd and remove configurations in the following orders:
l Remove cells and sectors successively.
l Configure sectors, operators, tracking areas, cells, cell sector equipment, cell operators,
and cells 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 RRUports. Cable connections must be consistent with the configurations.
Step 2 Run the ADD CNOPERATOR command to add an operator.
Step 3 Run the ADD CNOPERATORTAcommand to add a tracking area.
Step 4 Run the ADD CELLcommand to add a cell.
Step 5 Run the ADD EUCELLSECTOREQMcommand to add cell sector equipment.
Step 6 Run the ADD CELLOP command to add a cell operator.
Step 7 Run the ACT CELLcommand to activate the cell.
----End
SingleRAN
Base Station Equipment Reliability Feature Parameter
Description
7 Engineering Guidelines for RRU Channel Cross
Connection Under MIMO
Issue 01 (2015-03-23) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
29
7/25/2019 Base Station Equipment Reliability(SRAN10.1_01)
36/87
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 SECTOR: SECTORID=1, ANTNUM=2, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=62, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=1;
ADD SECTOR: SECTORID=2, ANTNUM=2, ANT1CN=0, ANT1SRN=62, ANT1SN=0, ANT1N=R0A,ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=2;
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 CELL: LocalCellId=1, CellName="MIMO", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1600, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=1,
PhyCellId=1, FddTddInd=CELL_FDD, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
ADD CELL: LocalCellId=2, CellName="MIMO", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1600, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=2,
PhyCellId=2, 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 EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1;
ADD EUCELLSECTOREQM: LocalCellId=2, SectorEqmId=2;
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=1, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=2, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1;
ACT CELL: LocalCellId=2;
Using the CME to Perform Single Configuration
On the CME, set the parameters listed in the 7.4.2 Data Preparationsection for a single base
station. For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.
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 beforelogging 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 Stylein the upper left corner of the U2000 client main window.
Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary DataFile (U2000 client mode), or choose Advanced > Customize Summary Data File(CME
client mode), to customize a summary data file for batch configuration.
NOTE