Академический Документы
Профессиональный Документы
Культура Документы
Issue 02
Date 2014-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
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...........................................................................................................................................17
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.............................................................................................................18
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..............................................................................................................21
4.8.1 Overtemperature Power-Off for Non-Main-Control Boards.....................................................................................21
4.8.2 Overtemperature Power-Off for Main Control Boards.............................................................................................22
5 Related Features...........................................................................................................................25
5.1 Prerequisite Features.....................................................................................................................................................25
5.2 Mutually Exclusive Features........................................................................................................................................25
5.3 Impacted Features.........................................................................................................................................................25
6 Network Impact...........................................................................................................................26
6.1 System Capacity...........................................................................................................................................................26
6.2 Network Performance...................................................................................................................................................26
11.4 Deployment................................................................................................................................................................61
11.4.1 Requirements...........................................................................................................................................................62
11.4.2 Data Preparation......................................................................................................................................................62
11.4.3 Precautions...............................................................................................................................................................62
11.4.4 Hardware Adjustment..............................................................................................................................................62
11.4.5 Activation................................................................................................................................................................62
11.4.6 Activation Observation............................................................................................................................................62
11.4.7 Deactivation.............................................................................................................................................................63
11.4.8 Reconfiguration.......................................................................................................................................................63
11.5 Performance Monitoring.............................................................................................................................................63
11.6 Parameter Optimization..............................................................................................................................................63
11.7 Troubleshooting..........................................................................................................................................................63
13 Parameters...................................................................................................................................70
14 Counters......................................................................................................................................76
15 Glossary.......................................................................................................................................77
16 Reference Documents...............................................................................................................78
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.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
SRAN9.0 02 (2014-06-30)
Compared with Issue 01 (2014-04-30), Issue 02 (2014-06-30) includes the following changes.
SRAN9.0 01 (2014-04-30)
This issue does not include any changes.
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
G U L T
3 Redundancy Design
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.
4 Hardware Reliability
4.1.1 Overview
The following table lists the features involved in Cold Backup of Main Control Boards.
Mode Feature
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
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 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.
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.
The prerequisites and methods for active/standby switchover vary with triggering conditions, as
described in Table 4-1.
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 carried
faults. switchover. 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 the delivers a a command to trigger
triggered standby board are normal, and the command to an active/standby
switchov 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 Idle. see chapter 8 of the switchover on
The backup status can be queried by Engineerin the base station must
running the DSP BKPSTATUS g be minimized.
command. Guidelines Therefore, the
for Cold switchover
NOTE
The command-triggered switchover
Backup of prerequisites are
cannot be performed before the initial or Main relatively complex.
routine backup between the active and Control
standby main control boards is Boards.
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 (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.
Mode Feature
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.
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.
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.
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).
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 one-
level cold backup ring topology and hot backup ring topology. There is only one-level of
RRUs in the inter-board one-level cold backup ring topology.
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)
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.
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 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.
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.
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.
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.
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.
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.
Intelligent diesel This is a basic function for GSM, Base stations supplied with solar
generator UMTS, and LTE base stations and power support intelligent diesel
management 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 and
shutdown of Shutdown of TRX Due to PSU the remaining PSUs cannot meet the
carriers due to Failure base station's power requirements,
PSU failure This is a basic function for UMTS the base station enters energy saving
and LTE base stations and does not mode to reduce power consumption
have a feature ID. 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 thus 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, thus 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.
– 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.
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.
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.
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.
4.9.1 Standards
No. File No. File Name
5 Related Features
6 Network Impact
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
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 operate 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
Table 7-1 Parameters for RRU Channel Cross Connection Under MIMO
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.5 Activation
Using MML Commands
Add 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:
Two antennas are configured, and antenna channels R0A and R0B are configured on different RRU ports.
Cable connections must be consistent with the configurations.
----End
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
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.7 Deactivation
To deactivate RRU Channel Cross Connection Under MIMO, remove the related configurations
and then remove the cables.
----End
SN MO Configuration Description
7.4.8 Reconfiguration
None
7.7 Troubleshooting
If an alarm described in Table 7-3 is generated, clear alarm by referring to the alarm handling
suggestions in eNodeB Alarm Reference.
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.
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:
– 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.
l In a co-MPT 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 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.
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.
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 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.
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.
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.
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.
Configure the MOs described in Table 8-3 on the CME configuration interface. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
SN MO Configuration Description
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.
----End
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
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
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 in the MOs listed in Table 8-3 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.
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
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.
----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.
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 command, the base station automatically restarts and services are
interrupted.
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
Configure the MOs described in Table 8-4 on the CME configuration interface. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
SN MO Configuration Description
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.
----End
8.4.9 Reconfiguration
N/A
8.7 Troubleshooting
N/A
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.
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
Slot No. SN Set this parameter to 0 and 1 for two Network plan (negotiation
BBPs in an eGBTS. The NodeB has not required)
no special requirement.
Board TYPE Set this parameter to UBBP for the Network plan (negotiation
Type 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.
For GSM (GBTS), Table 9-2 describes the key parameters that must be set for a BBP.
Slot No. SN Set this parameter to 0 and 1 for two Network plan (negotiation
BBPs. 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.
9.4.3 Precautions
None
9.4.5 Activation
Using MML Commands
NodeB
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
eGBTS
Step 2 Run the MML command ADD BASEBANDEQM to add the baseband equipment.
----End
GBTS
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 BRD: CN=0, SRN=0, SN=0, BT=UBBP, BBWS=GSM-1&UMTS-0<E_FDD-0<E_TDD-0;
ADD BRD: CN=0, SRN=0, SN=1, BT=UBBP, BBWS=GSM-1&UMTS-0<E_FDD-0<E_TDD-0;
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, CN1=0,
SRN1=0, SN1=0, CN2=0, SRN2=0, SN2=1;
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.
9.4.8 Reconfiguration
N/A
9.7 Troubleshooting
Table 9-4 lists alarms related to the Inter-Board Baseband Resource Redundancy feature for
NodeB. If an alarm described in Table 9-4 is generated, clear the alarm by referring to alarm
handling suggestions in NodeB Alarm Reference.
The following table describes the parameters that must be set in an RRUCHAIN MO.
The following table describes the parameters that must be set in an RRU MO.
RRU Chain RCN This Set this parameter based on the Network
No. parameter network plan. plan
indicates
the ID of
the RRU
chain/ring.
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
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
Board Type TYPE Set this parameter to LBBP for an Network plan
LBBP board. (negotiation not
Set this parameter to UBBP for a required)
UBBP board.
Table 10-2 describes the key parameters that must be set in an RRUCHAIN MO.
Table 10-3 describes the key parameters that must be set in an RRU MO.
RRU Chain No. RCN Set this parameter based on the Network plan
network plan.
10.4.3 Precautions
None
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 are One LBBPc board must be configured in slot 2 or 3, and the
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 other
two UBBP boards, or BBP can be configured in any slot from slot 0 to slot 5. A
one LBBPd and one maximum of six hot backup rings are supported.
UBBP board are to be
configured
10.4.5 Activation
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:
The execution of RMV BRD or ADD BRD may lead to eNodeB reset.
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 5 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding all
the RRUs.
----End
Step 3 Set Topo Type to RING and Backup Mode to COLD when configuring the RRU ring.
Step 4 Run the MOD RRUCHAIN command to add breakpoints on the RRU ring before adding the
RRU.
Step 6 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding all
the RRUs.
----End
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.
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
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.
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
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.
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
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 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 Trigger CPRI port swap for the cell. Run the BLK BRD command to block the BBP on which
the cell is established. This operation causes the cell to use a CPRI port on another BBP. The
following can be observed:
Cell reestablishment is not triggered but the UEs can still retain their RRC connections. No big
fluctuation occurs in the UDP data rates.
Run the DSP CELL command to check the information about a cell. If Cell instance state is
Normal, the cell has been activated. Check the value of 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.
Step 3 Run the MOD RRUCHAIN command to add breakpoints on the RRU ring before adding the
RRU.
Step 5 Run the RMV RRUCHAIN command to remove the RRU ring.
----End
SN MO Configuration Description
10.4.8 Reconfiguration
N/A
10.7 Troubleshooting
Table 10-5 lists alarms related to the Inter-Board Baseband Resource Redundancy feature for
LTE. If an alarm described in Table 10-5 is generated, clear the alarm by referring to alarm
handling suggestions in eNodeB Alarm Reference.
11.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
11.4 Deployment
11.4.1 Requirements
Hardware
eNodeBs use LBBPc boards.
License
None
11.4.3 Precautions
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.
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
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
11.4.8 Reconfiguration
N/A
11.7 Troubleshooting
N/A
12.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
12.4 Deployment
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-2 describes the parameter that must be set in an EQUIPMENT MO for activating this
feature in an eGBTS, NodeB, or eNodeB.
Table 12-2 Parameter for activating this feature in an eGBTS, NodeB, or eNodeB
12.4.3 Precautions
None
12.4.5 Activation
Run the SET BTSPSUFP command to configure the parameters of the Intelligent Shutdown of
Carriers Due to PSU Failure feature.
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.
eGBTS/NodeB/eNodeB
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=ON;
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 Configuration
Operation Guide.
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
12.4.7 Deactivation
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).
eGBTS/NodeB/eNodeB
SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=OFF;
12.4.8 Reconfiguration
N/A
12.7 Troubleshooting
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.
13 Parameters
CN BTS390 DSP None None Meaning: Indicates the cabinet number of the main
0, LOCAL control and transmission board.
BTS390 USBPO GUI Value Range: 0~7
0 RT
WCDM Unit: None
LST
A, LOCAL Actual Value Range: 0~7
BTS390 USBPO Default Value: None
0 LTE RT
SET
LOCAL
USBPO
RT
SRN BTS390 DSP None None Meaning: Indicates the subrack number of the main
0, LOCAL control and transmission board.
BTS390 USBPO GUI Value Range: 0~1
0 RT
WCDM Unit: None
LST
A, LOCAL Actual Value Range: 0~1
BTS390 USBPO Default Value: None
0 LTE RT
SET
LOCAL
USBPO
RT
SN BTS390 DSP None None Meaning: Indicates the slot number of the main control
0, LOCAL and transmission board.
BTS390 USBPO GUI Value Range: 6~7
0 RT
WCDM Unit: None
LST
A, LOCAL Actual Value Range: 6~7
BTS390 USBPO Default Value: None
0 LTE RT
SET
LOCAL
USBPO
RT
TYPE BTS390 None None None Meaning: Indicates the type of the board.
0, GUI Value Range: UMPT(UMPT), WMPT(WMPT),
BTS390 LMPT(LMPT)
0
WCDM Unit: None
A, Actual Value Range: UMPT, WMPT, LMPT
BTS390 Default Value: None
0 LTE
CN BTS390 ADD LBFD-0 Main Meaning: Indicates the number of the cabinet housing
0, HAGRP 0202101 Processi the board where the HA group is established.
BTS390 RMV ng and GUI Value Range: 0~7
0 MRFD- Transpo
HAGRP 210101 Unit: None
WCDM rt Unit
A, LST Cold Actual Value Range: 0~7
BTS390 HAGRP Backup Default Value: 0
0 LTE
System
Redunda
ncy
SRN BTS390 ADD LBFD-0 Main Meaning: Indicates the number of the subrack housing
0, HAGRP 0202101 Processi the board where the HA group is established.
BTS390 RMV ng and GUI Value Range: 0~1
0 MRFD- Transpo
HAGRP 210101 Unit: None
WCDM rt Unit
A, LST Cold Actual Value Range: 0~1
BTS390 HAGRP Backup Default Value: 0
0 LTE
System
Redunda
ncy
SN BTS390 ADD LBFD-0 Main Meaning: Indicates the logical slot number of the HA
0, HAGRP 0202101 Processi group. The logical slot number of an HA group is the
BTS390 RMV ng and number of the physical slot housing one of the two
0 MRFD- Transpo boards constituting the HA group.
HAGRP 210101
WCDM rt Unit GUI Value Range: 6~7
A, LST Cold
BTS390 HAGRP Backup Unit: None
0 LTE Actual Value Range: 6~7
System
Redunda Default Value: 6
ncy
CN BTS390 DSP None None Meaning: Indicates the cabinet number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~7
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~7
BTS390 BBP
Default Value: 0
0 LTE
SRN BTS390 DSP None None Meaning: Indicates the subrack number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~1
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~1
BTS390 BBP
Default Value: 0
0 LTE
SN BTS390 DSP None None Meaning: Indicates the slot number of the baseband
0, BBPTC processing board.
BTS390 LST GUI Value Range: 0~5
0 BBP
WCDM Unit: None
A, MOD Actual Value Range: 0~5
BTS390 BBP
Default Value: None
0 LTE
TYPE BTS390 MOD None None Meaning: Indicates the type of the board.
0, BBP GUI Value Range: UBBP(UBBP), GBBP(GBBP),
BTS390 WBBP(WBBP), LBBP(LBBP)
0
WCDM Unit: None
A, Actual Value Range: UBBP, GBBP, WBBP, LBBP
BTS390 Default Value: None
0 LTE
BBWS BTS390 ADD None None Meaning: Indicates the modes for which the UBBP
0, BRD provides baseband processing resources. If the UBBP
BTS390 MOD provides only CPRI ports for a mode, you do not need
0 BBP to configure this mode for the UBBP.
WCDM GUI Value Range: GSM(GSM), UMTS(UMTS),
A, LST
BBP LTE_FDD(LTE FDD), LTE_TDD(LTE TDD)
BTS390
0 LTE Unit: None
Actual Value Range: GSM, UMTS, LTE_FDD,
LTE_TDD
Default Value: GSM:NO, UMTS:NO, LTE_FDD:NO,
LTE_TDD:NO
BASEB BTS390 ADD None None Meaning: Indicates the number of the baseband
ANDEQ 0, BASEB equipment.
MID BTS390 ANDEQ GUI Value Range: 0~23
0 M
WCDM Unit: None
LST
A, BASEB Actual Value Range: 0~23
BTS390 ANDEQ Default Value: None
0 LTE M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
BASEB BTS390 ADD None None Meaning: Indicates the type of baseband equipment.
ANDEQ 0, BASEB GUI Value Range: UL(UL), DL(DL), ULDL
MTYPE BTS390 ANDEQ (Combined UL and DL)
0 M
WCDM Unit: None
LST
A, BASEB Actual Value Range: UL, DL, ULDL
BTS390 ANDEQ Default Value: None
0 LTE M
MOD
BASEB
ANDEQ
M
RMV
BASEB
ANDEQ
M
UMTSD BTS390 ADD None None Meaning: Indicates the demodulation mode of an uplink
EMMO 0, BASEB baseband signaling processing equipment for UMTS.
DE BTS390 ANDEQ For a newly added uplink baseband signaling
0 M processing board, the demodulation mode must be
WCDM LST specified. Different sets of uplink baseband signaling
A, BASEB processing board can have different demodulation
BTS390 ANDEQ modes. This parameter is not used for the GSM mode,
0 LTE M and therefore it is recommended that this parameter be
set to NULL for the GSM mode. This parameter cannot
be set to NULL for the UMTS mode. This parameter is
not used for the LTE mode, and therefore it is
recommended that this parameter be set to NULL for
the LTE mode.
GUI Value Range: NULL(NULL), DEM_4_CHAN(4-
Channels Demodulation Mode),
DEM_ECON_4_CHAN(Economical 4-Channels
Demodulation Mode), DEM_2_CHAN(2-Channels
Demodulation Mode)
Unit: None
Actual Value Range: NULL, DEM_4_CHAN,
DEM_ECON_4_CHAN, DEM_2_CHAN
Default Value: None
BASEB BTS390 None None None Meaning: Indicates the information about the baseband
ANDEQ 0, processing unit.
MBOA BTS390 GUI Value Range: 0~12
RD 0
WCDM Unit: None
A, Actual Value Range: 0~12
BTS390 Default Value: None
0 LTE
PSUFP BTS390 SET GBFD-1 Intellige Meaning: Indicates whether the BS enters the energy
0, EQUIP 17804 nt saving mode when some PSUs become faulty. If this
BTS390 MENT Shutdow parameter is set to ON, the BS enters the energy saving
0 LST n of mode to reduce power consumption when some PSUs
WCDM EQUIP TRX become faulty and the remaining PSUs cannot meet the
A, MENT Due to BS's power requirements. In energy saving mode, the
BTS390 PSU BS shuts down TRXs or reduces their transmit power.
0 LTE Failure GUI Value Range: ON(ON), OFF(OFF)
Unit: None
Actual Value Range: ON, OFF
Default Value: OFF(OFF)
14 Counters
15 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
16 Reference Documents