Base Station Equipment Reliability(SRAN10.1_01)

SingleRAN

Base Station Equipment Reliability Feature Parameter Description Issue

01

Date

2015-03-23

HUAWEI TECHNOLOGIES CO., LTD.

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 trademarks and trade names mentioned mentioned in this this document are are the property of of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. 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, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial 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

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 trademarks and trade names mentioned mentioned in this this document are are the property of of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. 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, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations 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 recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2015-03-23)


i

SingleRAN Base Station Equipment Reliability Feature Parameter Description

Contents

Contents 1 About This This Document........... Document................................. ............................................ ............................................. ............................................. .................................... .............. 1 1.1 Scope........................................................................................................... Scope....... ....................................................................................................................................................................... ................................................................... 1 1.2 Intended Audience..........................................................................................................................................................1 1.3 Change History................................................................................................... H istory............................................................................................................................................................... ............................................................ 1 1.4 Differences Differences Between Base Station Types....................................................................................................................... Types....................................................................................................................... 2

2 Overview........... Overview................................. ............................................ ............................................ ............................................. ............................................. ..................................... ............... 3 3 Redundancy Redundancy Design.............. Design.................................... ............................................ ............................................ ............................................ ...................................... ................8 8 3.1 RF Channel Chann el Cooperation................................................................................................. Cooperation................................................................................................................................................ ............................................... 8 3.2 RRU Channel Cha nnel Cross Connection Under MIMO.............................................................................................................8

4 Hardware Hardware Reliability................... Reliability......................................... ............................................ ............................................ ............................................ ............................. ....... 10 4.1 Cold Back up up of Main Control Boards..........................................................................................................................10 4.1.1 Overview................................................................................ Overvie w................................................................................................................................................................... ................................................................................... 10 4.1.2 Active/Standby Active/S tandby Competition..................................................................... Competition......................................................................................................................................1 .................................................................11 1 4.1.3 Data Backup...............................................................................................................................................................11 Ba ckup...............................................................................................................................................................11 4.1.4 Active/Standby Active/S tandby Switchover............................................................................................................................. Switchover....................................................................................................................................... .......... 11 4.2 Inter-Boar d Baseband Resource Redundancy....................................................................................................... Redundancy.............................................................................................................. ....... 13 4.3 Intra-Boar d Baseband Resource Pool...........................................................................................................................15 4.3.1 Overview................................................................................ Overvie w................................................................................................................................................................... ................................................................................... 15 4.3.2 Intra-Board Intra-Board Cell-Level Resource Pool...................................................................................................... Pool...................................................................................................................... ................ 16 4.3.3 Intra-Board Intra-Board User-Level Resource Pool..................................................................................................................... Pool..................................................................................................................... 17 4.4 Heat Dissi pation pation Reliability for Fans........................................................................................................................... Fans........................................................................................................................... 17 4.5 Power Supply Redundancy.................................................... Redundancy...........................................................................................................................................17 .......................................................................................17 4.5.1 Power Supply S upply Redundancy for a Base Station.......................................................................................................... Station.......................................................................................................... 18 4.5.2 Power Supply S upply Redundancy for a BBU...................................................................................................................... BBU...................................................................................................................... 18 4.6 Power Su pply Reliability..............................................................................................................................................18 Reliability..............................................................................................................................................18 4.6.1 Power Supply S upply Reliability for a Base Station............................................................................................................. Station............................................................................................................. 18 4.6.2 Power Supply S upply Reliability for a BBU......................................................................................................................... BBU......................................................................................................................... 20 4.7 Anti-Misinsertion Anti-Misinsertion Design of Boards........................................................................................... Boards.............................................................................................................................21 ..................................21 4.8 Overtemperature Protection for BBU Boards.............................................................................................................. Boards.............................................................................................................. 21 4.8.1 Overtemperature Power-Off for Non-Main-Control Boards..................................................................................... Boards..................................................................................... 21 4.8.2 Overtemperature Power-Off for Main Control Boards............................................................................................ Boards..............................................................................................22 ..22 4.9 Surge Protection Design............................................................................................................................................... Design............................................................................................................................................... 23 Issue 01 (2015-03-23)


ii


Contents

4.9.1 Standards................................................................................................... Standards................................................................................................................................................................... ................................................................ 23 4.9.2 Surge Protection Capability of Different Ports..........................................................................................................24

5 Related Features........ Features.............................. ............................................ ............................................. ............................................. ............................................ .......................... ....25 25 5.1 Prerequisite Features............................................................................... Features.....................................................................................................................................................25 ......................................................................25 5.2 Mutually Exclusive Features............................................................................................................................ Features........................................................................................................................................ ............ 25 5.3 Impacted Features.........................................................................................................................................................25

6 Network Impact............ Impact.................................. ............................................ ............................................ ............................................ ............................................ ........................ 26 6.1 System Ca pacity............................................................................ pacity........................................................................................................................................................... ............................................................................... 26 6.2 Network Performance...................................................................................................................................................26 P erformance...................................................................................................................................................26

7 Engineering Engineering Guidelines for RRU Channel Cross Connection Under MIMO.................27 7.1 When to Use U se RRU Channel Cross Connection Under MIMO.....................................................................................27 7.2 Required Information................................................................................ I nformation................................................................................................................................................... ................................................................... 27 7.3 Planning............................................................................................... Planning........................................................................................................................................................................ ......................................................................... 27 7.4 Deployment................................................................................................ Deployment.................................................................................................................................................................. .................................................................. 27 7.4.1 Requirements.................................................................................................. Requirements............................................................................................................................................................. ........................................................... 28 7.4.2 Data Pre paration........................................................................................ paration........................................................................................................................................................ ................................................................ 28 7.4.3 Precautions.................................................................................................................................................................29 Precauti ons.................................................................................................................................................................29 7.4.4 Hardwar e Adjustment................................................................................................................................................ Adjustment................................................................................................................................................29 29 7.4.5 Activation................................................................................. Activati on.................................................................................................................................................................. ................................................................................. 29 7.4.6 Activation Activati on Observation.............................................................................................................................................. Observation..............................................................................................................................................31 31 7.4.7 Deactivation...............................................................................................................................................................31 Deactiva tion...............................................................................................................................................................31 7.4.8 Reconfiguration........................................................................................................... Reconfiguration......................................................................................................................................................... .............................................. 32 7.5 Performance Performance Monitoring.......................................................................................... Monitoring...............................................................................................................................................32 .....................................................32 7.6 Parameter Optimization................................................................................................................................................ Optimization................................................................................................................................................ 32 7.7 Troubleshooting............................................................................................................................................................32 Troubleshooting............................................................................................................................................................32

8 Engineering Engineering Guidelines for Cold Backup of Main Control Boards................................. Boards................................... 33 8.1 When to Use U se Cold Backup of Main Control Boards.................................................................................................... Boards.................................................................................................... 33 8.2 Required Information................................................................................ I nformation................................................................................................................................................... ................................................................... 33 8.3 Planning............................................................................................... Planning........................................................................................................................................................................ ......................................................................... 33 8.4 Deployment................................................................................................ Deployment.................................................................................................................................................................. .................................................................. 35 8.4.1 Requirements.................................................................................................. Requirements............................................................................................................................................................. ........................................................... 35 8.4.2 Data Pre paration........................................................................................ paration........................................................................................................................................................ ................................................................ 35 8.4.3 Precautions.................................................................................................................................................................36 Precauti ons.................................................................................................................................................................36 8.4.4 Hardwar e Adjustment................................................................................................................................................ Adjustment................................................................................................................................................36 36 8.4.5 Activation................................................................................. Activati on.................................................................................................................................................................. ................................................................................. 36 8.4.6 Commissioning..........................................................................................................................................................39 Commissioning..........................................................................................................................................................39 8.4.7 Activation Activati on Observation.............................................................................................................................................. Observation..............................................................................................................................................40 40 8.4.8 Deactivation...............................................................................................................................................................40 Deactiva tion...............................................................................................................................................................40 8.4.9 Reconfiguration........................................................................................................... Reconfiguration......................................................................................................................................................... .............................................. 42 8.5 Performance Monitoring.......................................................................................... Monitoring...............................................................................................................................................42 .....................................................42 8.6 Parameter Optimization................................................................................................................................................ Optimization................................................................................................................................................ 42 Issue 01 (2015-03-23)


iii


Contents

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)..............................................................43 9.2 Required Information................................................................................................................................................... 43 9.3 Planning........................................................................................................................................................................ 43 9.4 Deployment.................................................................................................................................................................. 44 9.4.1 Requirements............................................................................................................................................................. 44 9.4.2 Data Pre paration........................................................................................................................................................ 44 9.4.3 Precautions.................................................................................................................................................................46 9.4.4 Hardwar e 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 Parameter Optimization................................................................................................................................................ 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 Required Information................................................................................................................................................. 49 10.3 Planning...................................................................................................................................................................... 50 10.4 Deployment................................................................................................................................................................ 50 10.4.1 Requir ements........................................................................................................................................................... 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 Reconf iguration....................................................................................................................................................... 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 Required Information..................................................................................................................................................60 11.3 Planning...................................................................................................................................................................... 60 11.4 Deployment.................................................................................................................................................................60 11.4.1 Requir ements........................................................................................................................................................... 61 11.4.2 Data Pr eparation...................................................................................................................................................... 61 Issue 01 (2015-03-23)


iv


Contents

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

Issue 01 (2015-03-23)


v


1 About This Document

1

About This Document

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

1.2 Intended Audience This document is intended for personnel who: l l

Need to understand the features described herein Work with Huawei products

1.3 Change History This section provides information about the changes in different document versions. There are two types of changes, which are defined as follows: l

Feature change Changes in features of a specific product version

Issue 01 (2015-03-23)


1

SingleRAN Base Station Equipment Reliability Feature Parameter Description l

1 About This Document

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: None eGBTS(GTMUb) does not support Cold Backup of Main Control Boards feature. For details, see 2 Overview2 Overview.

Editorial change

None.

None

1.4 Differences Between Base Station Types The features described in this document are implemented in the same way on macro base stations and LampSite base stations.

Issue 01 (2015-03-23)


2


2 Overview

2

Overview

The reliability design feature includes redundancy design and hardware reliability design. With reliability design, base station equipment can continue to provide services even when some parts are faulty. This avoids or reduces the impact on services caused by equipment faults and improves system reliability. Table 2-1 describes the base station equipment reliability features/functions supported by each mode. In this table, "Y" means "supported" and "N" means "not supported." Table 2-1 Base station equipment reliability features/functions supported by each mode

Reliabil ity Type

Redund ancy design

Feature/Function

RF Channel Cooperation

Whether This Feature/Function Is Supported G

U

L

T

GBTS: Y

Y

N

N

eGBTS: Y

Description

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, see RRU Redundancy Feature Parameter Description.

Issue 01 (2015-03-23)


3


Hardwa re reliabili ty

2 Overview

RRU Channel Cross Connection Under MIMO

GBTS: N

Cold Backup of Main Control Boards

GBTS: N

N

Y

N

For details about the principles and the engineering guidelines for RRU Channel Cross Connection Under MIMO, see section 3.2 RRU Channel Cross Connection Under MIMO and chapter 7 Engineering Guidelines for RRU Channel Cross Connection Under MIMO, respectively.

Y

Y

N

For details about the principles and the engineering guidelines for Cold Backup of Main Control Boards, see section 4.1 Cold Backup of Main Control Boards and chapter 8 Engineering Guidelines for Cold Backup of Main Control Boards.

Y

Y

Y

For details about the principles of Inter-Board Baseband Resource Redundancy, see section 4.2 Inter-Board Baseband Resource Redundancy .

eGBTS: N

eGBTS(G TMUb): N eGBTS(U MPT): Y

Inter-Board Baseband Resource Redundancy

GBTS: Y eGBTS: Y

For details about the engineering guidelines for the GBTS, eGBTS, and NodeB, see chapter 9 Engineering Guidelines for InterBoard Baseband Resource Redundancy (GSM&UMTS) . For details about the engineering guidelines for the eNodeB, see chapter 10 Engineering Guidelines for InterBoard Baseband Resource Redundancy (LTE) .

Issue 01 (2015-03-23)


4


Intra-Board Baseband Resource Pool

2 Overview

GBTS: Y

Y

Y

Y

eGBTS: Y

For details about the principles of Intra-Board Baseband Resource Pool, see section 4.3 IntraBoard Baseband Resource Pool. For the GBTS, eGBTS, and NodeB, Intra-Board Baseband Resource Pool is a basic function and has no feature ID. In addition, it does not require any software configurations. For details about the engineering guidelines for the eNodeB, see chapter 11 Engineering Guidelines for IntraBoard Baseband Resource Pool (LTE).

Heat Dissipation Reliability for Fans

Issue 01 (2015-03-23)

GBTS: Y

Y

Y

eGBTS: 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.

5


Power Supply Redundancy

2 Overview

GBTS: Y

Y

Y

Y

eGBTS: 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, see Power Supply Management Feature Parameter Description. Power Supply Redundancy for a BBU is a basic function and does not require any software configurations.

Power Supply Reliability

GBTS: Y

Y

Y

eGBTS: 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 intelligent shutdown 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, see Power Supply Management Feature Parameter Description. Power Supply Reliability for a BBU is a basic function and does not require any software configurations.

Issue 01 (2015-03-23)


6


Issue 01 (2015-03-23)

2 Overview

AntiMisinsertion Design of Boards

GBTS: Y

Overtemperature Protection for BBU Boards

GBTS: Y

Surge Protection Design

GBTS: Y

Y

Y

Y

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

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.

Y

Y

Y

For details, see section 4.9 Surge Protection Design. This is a basic function and does not require any software configurations.

eGBTS: Y

eGBTS: Y

eGBTS: Y


7


3 Redundancy Design

3

Redundancy Design

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

Mode

Feature

Feature Parameter Description

GSM

GBFD-113801 TRX Cooperation

TRX Cooperation Feature Parameter Description

UMTS

WRFD-040203 RRU 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 maintenance difficult. If one RRU or RFU fails, the entire sector may lose services for an extended period Issue 01 (2015-03-23)


8


3 Redundancy Design

of time. With RRU Channel Cross-Connection Under MIMO, the failure of one RRU or RFU will not lead to service interruption for the entire sector. This feature increases RRU or RFU reliability without increasing hardware costs. As shown in Figure 3-1 (using three sectors as an example), an LBBP is connected to multiple RRUs. In this case, the data on two TX/RX channels of a cell is transmitted over two fiber optic cables and processed by two RRUs. When a fiber optic cable fails or an RRU has a hardware fault, the antenna mode changes from 2T2R to 1T1R to keep the cell working normally. This prevents long-time service interruption and increases system reliability. Figure 3-1 RF cable connections for RRU channel cross connection under MIMO

For details about the engineering guidelines for this feature, see chapter 7 Engineering Guidelines for RRU Channel Cross Connection Under MIMO.

Issue 01 (2015-03-23)


9


4 Hardware Reliability

4

Hardware Reliability

4.1 Cold Backup of Main Control Boards 4.1.1 Overview The following table lists the features involved in Cold Backup of Main Control Boards.

Mode

Feature

GSM

MRFD-210101 System Redundancy

UMTS

MRFD-210101 System Redundancy

LTE FDD

LBFD-00202101 Main Processing and Transport Unit Cold Backup

When a base station is configured with only one main control board, services will be interrupted for an extended period of time if this main control board is faulty. To support Cold Backup of Main Control Boards, two main control boards working in active/standby mode are required. During cold backup, the standby main control board is powered on but does not back up the signaling and service data carried by the active main control board. When a fault is detected on the active main control board, the active and standby boards switch roles. Services carried on the original active board are interrupted but automatically recover within 4 to 7 minutes. This improves base station reliability. 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.

Issue 01 (2015-03-23)


10



Cold Backup of Main Control Boards involves three processes: active/standby competition, data backup, and active/standby switchover. For details about the engineering guidelines for Cold Backup of Main Control Boards, see chapter 8 Engineering Guidelines for Cold Backup of Main Control Boards .

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

4.1.3 Data Backup The main control boards work in cold backup mode. Only static data (for example, configuration data, software data, and logs) must be synchronized between the active and standby main control boards. Operating data, which requires real-time synchronization in hot backup mode, does not need to be synchronized in real time in cold backup mode. Data backup consists of initial backup and routine backup, which are described as follows: l

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). 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. Issue 01 (2015-03-23)


11



Table 4-1 Prerequisites and methods for active/standby switchover

Switcho ver Type

Prerequisites

Method

Remarks

Faulttriggered switchov er

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.

The system automaticall y triggers the switchover.

When the active main control 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 are relatively simple.

Comman dtriggered 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 BKPSTATUS command. 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 commandtriggered switchover after the hardware installation is complete and the base station has been running for more than two hours.

Issue 01 (2015-03-23)

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.

A user Before a user delivers delivers a a command to trigger command to an active/standby trigger the switchover, the base switchover. station works For details, properly. The impact see chapter of the switchover on 8 the base station must Engineerin be minimized. g Therefore, the switchover Guidelines for Cold prerequisites are relatively complex. Backup of Main Control Boards.


12



4.2 Inter-Board Baseband Resource Redundancy The following table lists the features involved in Inter-Board Baseband Resource Redundancy.

Mode

Feature

LTE FDD

LBFD-00202102 Cell Re-build Between Baseband Processing Units

LTE TDD

TDLBFD-00202102 Cell Re-build Between Baseband Processing Units

When a baseband board fails, the cells or carriers served by this failed baseband board will be affected. With Inter-Board Baseband Resource Redundancy, the cells or carriers served by a failed baseband board can be reestablished on another operational baseband board with available resources. This improves base station reliability. To implement this feature, a base station must be equipped with at least two baseband boards and these two baseband boards must be installed in the same BBU.

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

Issue 01 (2015-03-23)


13



NOTICE l

l

For GSM, only the UBBP board supports inter-board baseband resource redundancy. Configure the two UBBP boards in slots 0 and 1. Inter-board baseband resource redundancy for GSM does not require CPRI-based topologies and is only supported if two UBBP boards are configured. However, the inter board cold backup ring topology and hot backup ring topology are not supported in GSM. For details, see RF Unit and Topology Management Feature Parameter Description.

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

NOTE

Inter-board baseband resource redundancy for UMTS does not require CPRI-based topologies and is only supported if two baseband boards are configured. However, the hot backup ring topology is not supported in UMTS. For details, see RF Unit and Topology Management Feature Parameter Description.

Inter-Board Baseband Resource Redundancy for LTE Figure 4-3 illustrates a 3 x 10 MHz 2T2R configuration scenario where the eNodeB is configured with two LBBP or UBBPd_L boards and the two baseband boards are connected to the same RRUs so that an inter-board one-level cold backup ring topology 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 or UBBPd_L board. If more than two LBBP or UBBPd_L boards are configured, the eNodeB Issue 01 (2015-03-23)


14



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-3 LTE 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.

Issue 01 (2015-03-23)

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)


15



The base station supports the share of resources in a baseband board. Resources are aggregated into a resource pool to be shared for user data processing by multiple cells or carriers. If a processing unit is faulty, services carried on the processing unit are interrupted and then reestablished on other processing units with available resources. If a processing unit is overloaded or the resources for the processing unit are exhausted, the base station can transfer users on the processing resource to other resources. This improves system reliability. For the LTE, only the LBBPc board supports intra-board baseband resource pool.

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

For UMTS, when a baseband board allocates several resources to a single cell for load sharing, the common processing parts of the cell can use only one resource. If this resource fails, the cells served by this resource can be reestablished on other normal processing resources within 20s. This ensures service recovery.

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

Issue 01 (2015-03-23)


16



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

4.4 Heat Dissipation Reliability for Fans Fans are used for inner and outer air circulation, allowing heat to dissipate from the equipment through a ventilation channel. When a fan on a ventilation channel is faulty, heat dissipation will be affected. Fans do not support redundancy design in hardware due to inconvenient installation. To ensure adequate heat dissipation, the following functions are provided: l

When the FMU works in intelligent temperature control mode, the FMU adjusts the rotation speed of fans based on the temperature control parameters delivered by the BBU. If a fan becomes faulty, ALM-25673 Fan Stalled is reported and the policy for adjusting the rotation speed of other fans remains unchanged.

l

When the FMU works in temperature control mode and cannot obtain the temperature information of the equipment, the FMU adjusts the rotation speed of fans based on the ambient temperature. If a fan becomes faulty, ALM-25673 Fan Stalled is reported and other fans in the same fan group rotate at full speed to ensure heat dissipation.

l

When the TCU cannot obtain the temperature at the air exhaust vent, fans in the TCU rotate at full speed. If a fan becomes faulty, ALM-25673 Fan Stalled is reported and other fans in the same fan group rotate at full speed to ensure heat dissipation.

l

When a fan in the FAN unit of the BBU becomes faulty, ALM-26110 BBU Fan Stalled and ALM-26111 BBU Fan Not at Full Speed are reported and other fans in the FAN unit rotate at full speed to ensure heat dissipation.

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.

Issue 01 (2015-03-23)


17



4.5.1 Power Supply Redundancy for a Base Station PSUs in a base station should be configured in N+1 backup mode. After power supply redundancy for a base station is enabled for a Huawei AC-powered base station equipped with a PMU, ALM-25636 Loss of Power Supply Redundancy is reported if PSUs in the base station are not configured in N+1 mode. The reported alarm alerts the customer to the insufficiency of PSUs. Power supply redundancy for a base station does not have a feature ID and is supported by GSM, UMTS, and LTE base stations. For details about the principles and engineering guidelines for this feature, see sections "Reporting of ALM-25636 Loss of Power Supply Redundancy" and "Deployment of Reporting of ALM-25636 Loss of Power Supply Redundancy" in Power Supply Management Feature Parameter Description.

4.5.2 Power Supply Redundancy for a BBU The BBU supports 1+1 backup mode for power boards. Currently, only the UPEUc and UPEUd boards can work in 1+1 backup mode. When the configured power consumption of the whole BBU exceeds the power supply capability of a single UPEUc board, the UPEUc boards cannot work in 1+1 backup mode. In the normal working state, the two power boards share the power load. When a power board becomes faulty, the power load on the faulty board automatically switches to the other board, avoiding service interruption. To work in 1+1 backup mode, power boards in the BBU must meet the following requirements: l

Each power board can undertake the power load of the whole BBU.

l

The two power boards are of the same type and have the same specifications.

Power Supply Redundancy for a BBU is a basic function and does not require any software configurations.

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

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" i n 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.

Issue 01 (2015-03-23)


18



In DC input scenarios, the DCDU provides a circuit breaker or fuse for each DC output. Once short-circuit or overload occurs on a DC output, the corresponding circuit breaker or fuse is disconnected automatically. This does not affect upper-level equipment.

Enhanced Power Supply for Huawei AC-Powered Base Stations Equipped with the PMU In addition to basic power supply functions, the features in the following table are provided for Huawei AC-powered base stations equipped with the PMU to improve power supply reliability.

Function

Feature ID and Name

Description

Intelligent battery management

GSM: GBFD-510710 Intelligent Battery Management

Intelligent battery management provides the following functions: automatic switching between different charge-and-discharge modes, self-protection under high temperature, and battery runtime display.

UMTS: WRFD-140220 Intelligent 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

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

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.

Issue 01 (2015-03-23)

This is a basic function for UMTS and LTE base stations and does not have a feature ID.

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 battery disconnection under high temperature, and automatic load disconnection.


19



For details about the principles and engineering guidelines for the functions of intelligent battery management, automatic battery and load disconnection, and intelligent diesel generator management, see Power Supply Management Feature Parameter Description. The function of intelligent shutdown of carriers due to PSU failure is described as follows: In scenarios where a base station uses the AC power input, the PSU converts the AC power to DC power and then supplies the DC power to boards in the base station. Generally, multiple PSUs are required to provide sufficient electricity for a base station and these PSUs work in parallel. If one or several PSUs are faulty, the load of the PSUs that work properly increases. As a result, all PSUs may stop working due to overcurrent protection and all the services carried on the base station may be interrupted. To prevent this from happening, intelligent shutdown of carriers due to PSU failure is introduced. With this function, when one or several PSUs are faulty, the base station shuts down the power amplifiers of the carriers that consume excessive electricity, based on the power supply capability of the PSUs that work properly. In this manner, other carriers continue to work properly, minimizing the impact of service interruption. For details about the configurations for this function, see chapter 12 Engineering Guidelines for Intelligent Shutdown of Carriers Due to PSU Failure.

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

l

Issue 01 (2015-03-23)

Good environment adaptability

–

Wide range of input voltage: The BBU supports -48 V DC power input and an actual input voltage range of -57 V DC to -38.4 V DC.

–

Wide range of operating temperatures: The BBU supports an operating temperature range of -20°C to 60°C.

–

Satisfied indoor protection: The BBU does not require an additional surge protection unit.

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, powerconsuming devices, and system from being damaged. In this case, the BB U will be reset.

–

Protection against output overvoltage: If the output overvoltage occurs, the power board enters hiccup protection mode, preventing the power board, powerconsuming devices, and system from being damaged. In this case, the BB U will be reset. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

20


–


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 B BU 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 Boards When the temperature of a BBU board exceeds its maximum operating temperature, the lifespan of the board may be shortened or its reliability may be affected. In the worst-case scenario, the board may be burnt out, imposing safety risks. To prevent this from happening, Huawei provides the Power-Off on Overtemperature function.

4.8.1 Overtemperature Power-Off for Non-Main-Control Boards Power-Off Requirements l

The main control board powers off a non-main-control board and reports ALM-26214 Board Powered Off when any of the following conditions is met: a common overtemperature alarm exists on the non-main-control board for more than 24 hours, a severe overtemperature alarm exists on the non-main-control board for more than one hour, or the temperature of the non-main-control board is higher than the overtemperature power-off threshold. NOTE

When a common overtemperature alarm exists on the main control board for more than 2 minutes, the main control board powers off the WBBPa or WBBPb and reports ALM-26214 Board Powered Off. l

Issue 01 (2015-03-23)

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. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

21



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 nonmain-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. – l

More than 10 minutes have elapsed since the non-main-control board has been powered off.

Manual mode: Users can deliver an MML command to forcibly power on a non-maincontrol 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.

Issue 01 (2015-03-23)


22



Power-On Requirements If a main control board is powered off due to overtemperature, users must troubleshoot the fault onsite and then power on the main control board.

Impact of Overtemperature Power-Off of Main Control Boards on Multimode Base Stations l

In a multimode base station, the impact of overtemperature power-off of a main control board on services is the same as that caused by a reset or fault of the main control board.

In a separate-MPT multimode base station, each main control board only manages itself and boards working in the same mode as the main control board. In a co-MPT multimode base station, the active main control board manages all the boards in the BBU subrack. In this case, the active main control board powers off all the boards at the same time when necessary, without considering the RAT priority.

4.9 Surge Protection Design The surge protection design of Huawei products complies with related standards. Different surge protection solutions are provided for different ports.

4.9.1 Standards

Issue 01 (2015-03-23)

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)


23



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.

Issue 01 (2015-03-23)

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


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


9

AISG

Built-in surge protection is used on the equipment and no surge protector is required.


24


5 Related Features

5

Related Features

5.1 Prerequisite Features None

5.2 Mutually Exclusive Features None

5.3 Impacted Features 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.

Issue 01 (2015-03-23)


25


6 Network Impact

6

Network 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 Performance No impact.

Issue 01 (2015-03-23)


26


7 Engineering Guidelines for RRU Channel Cross Connection Under MIMO

7

Engineering Guidelines for RRU Channel Cross Connection Under MIMO

7.1 When to Use RRU Channel Cross Connection Under MIMO RRU Channel Cross Connection Under MIMO can be enabled when RRUs are installed on top of a tower. Cross-connections between a baseband board and RRUs enable the data on two TX/RX channels of a cell to be transmitted using two fiber optic cables and to be processed by two RRUs. When a fiber optic cable fails or an RRU has a hardware fault, the antenna mode changes from 2T2R to 1T1R to keep the cell working normally. This prevents long-time service interruption and increases system reliability.

7.2 Required Information N/A

7.3 Planning RF Planning N/A

Network Planning N/A

Hardware Planning N/A

7.4 Deployment Issue 01 (2015-03-23)


27



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-1 describes the parameters for RRU Channel Cross Connection Under MIMO. Table 7-1 Parameters for RRU Channel Cross Connection Under MIMO

Issue 01 (2015-03-23)

MO

Parameter Name

SECTOR

Sector ID

SECTOR

Sector Antenna

Parameter ID SECTORID

SECTORANTENNA

Setting Notes

Data Source

None

Network plan (negotiation not required)

None



28



7.4.3 Precautions The precautions for deploying RRU Channel Cross Connection Under MIMO are as follows: l

All RF units must be of the same model and support the same set of frequency bands.

l

The number of RF units is equal to or greater than two.

l

The antenna mode must be 2T2R for sectors enabled with RRU Channel Cross Connection Under MIMO. Each sector must be configured on a unique RF unit, and the RF units must be correctly connected to antennas.

l

The RF units must form a star topology and connect to the same baseband board.

l

For LBBPc boards, optical fibers that connect the LBBPc boards and RF units must have approximately the same length. Any difference in lengths must be less than 100 m. There is no such restriction for LBBPd boards.

l

If faults on the fiber optic cable or RRU are rectified when the cell has rolled back to 1T1R and is in active mode, the system triggers cell reestablishment to change the cell configuration from 1T1R to 2T2R only when no RRC-connected user exists in the cell.

In multimode scenarios, RRU Channel Cross Connection Under MIMO is supported in LTE mode. For other modes, support for this feature depends on the capability of the mode.

7.4.4 Hardware Adjustment Connect RRUs or RFUs to antennas according to Figure 3-1.

7.4.5 Activation Using MML Commands Add and remove configurations in the following orders: l

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 RRU ports. Cable connections must be consistent with the configurations.

Step 2 Run the ADD CNOPERATOR command to add an operator. Step 3 Run the ADD CNOPERATORTA command to add a tracking area. Step 4 Run the ADD CELL command to add a cell. Step 5 Run the ADD EUCELLSECTOREQM command to add cell sector equipment. Step 6 Run the ADD CELLOP command to add a cell operator. Step 7 Run the ACT CELL command to activate the cell. ----End Issue 01 (2015-03-23)


29



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 Preparation section 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 before logging out of the parameter setting interface.

l

The default display style of the U2000 client is the application style. However, traditional style is more convenient for operations described in this document. All operation guides related to the U2000 client described in this document is based on the traditional style.

l

To change the display change to the traditional style, choose System > Preferences > Client Display Style in the upper left corner of the U2000 client main window.

Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode), to customize a summary data file for batch configuration. NOTE

For context-sensitive help on a current task in the client, press F1.

Issue 01 (2015-03-23)


30



Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-1 and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification.

Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

7.4.6 Activation Observation For details about activation observation procedures for RRU Channel Cross Connection Under MIMO, see Cell Management Feature Parameter Description.

7.4.7 Deactivation To deactivate RRU Channel Cross Connection Under MIMO, remove the related configurations and then remove the cables.

Using MML Commands Remove cells and sectors successively.

Step 1 Run the RMV CELL command to remove the cell. Step 2 Run the RMV SECTOR command to remove the sector. ----End

MML Command Examples RMV CELL: LocalCellId=0; RMV SECTOR: SECTORID=0;

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

Issue 01 (2015-03-23)

SN

MO

Configuration Description

1

CELL

Remove the configuration data of the cell.


31



SN

MO


2

SECTOR

Remove the configuration data of the sector.

Using the CME to Perform Batch Configuration You cannot use the CME to perform batch configuration to deactivate this feature.

7.4.8 Reconfiguration None

7.5 Performance Monitoring N/A

7.6 Parameter Optimization None

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

Issue 01 (2015-03-23)

Alarm ID

Alarm Name

Alarm Type

Alarm Severity Level

Network Management Type

ALM-26234

BBU CPRI Interface Error

Fault

Major

Hardware system

ALM-29243

Cell Capability Degraded

Fault

Major

Signaling system

ALM-26236

RRU Cascading Levels and Configuration Mismatch

Fault

Major

Hardware system

ALM-26238

RRU Network Topology Type and Configuration Mismatch

Fault

Major

Hardware system

ALM-26504

RF Unit CPRI Interface Error

Fault

Major

Communicatio n system


32


8 Engineering Guidelines for Cold Backup of Main Control Boards

8

Engineering Guidelines for Cold Backup of Main Control Boards

8.1 When to Use Cold Backup of Main Control Boards Cold Backup of Main Control Boards is recommended if the customer has a high requirement on the base station reliability. This feature provides the following benefits: l

Services recover within several minutes after the main control board experiences a hardware failure.

l

In a co-MPT multimode base station, when the main control experiences a severe hardware failure, services of all modes are interrupted simultaneously. This feature ensures that services can recover automatically. This improves base station reliability.



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:

Issue 01 (2015-03-23)


33



–

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

l

l

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 coMPT base stations.

–

Cold backup of LMPT boards applies only to eNodeBs FDD.

–

Cold backup of WMPT boards applies only to NodeBs.

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. 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. 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 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.

Issue 01 (2015-03-23)


34



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

8.4.2 Data Preparation l

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

Parameter Name

Parameter ID

Setting Notes

Data Source

Cabinet No.

CN

Set this parameter to 0.


Subrack No.

SRN



Slot No.

SN

Set this parameter to 6 and 7 for two main control boards.


Set this parameter to UMPT, LMPT, or WMPT based on the actual configuration. Boards in slots 6 and 7 must be of the same type.


Board Type TYPE

Issue 01 (2015-03-23)


35



Configuring an HAGRP Table 8-2 describes the parameters that must be set in the HAGRP MO to configure two boards with the active/standby transmission capability as two boards working in active/ standby mode. Table 8-2 Key parameters for configuring an HAGRP

Parameter Name

Parameter ID

Setting Notes

Data Source

Cabinet No.

CN

None


Subrack No.

SRN

None


Logical Slot No.

SN

This parameter can be set to a Network plan value different from the number (negotiation not of the slot where the main control required) boards are installed.

8.4.3 Precautions l

After an HAGRP MO is configured, users must enter the value of the Logic Slot No. parameter specified in the HAGRP MO as the slot number when running ADD XXX, RMV XXX, MOD XXX, LST XXX, or DSP XXX commands related to transmission or clock. The output of a DSP XXX command contains the number of the slot housing the active main control board.

l

Adding or removing an HAGRP MO changes the connection between the base station and the transport network and resets the base station.

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

In scenarios where two UMPT boards work in cold backup mode, if the spare UMPT board and the UMPT board to be replaced are of different working modes, the spare UMPT board automatically switches to the working mode of the replaced UMPT board and works in active and standby mode with the other original UMPT board after the replacement.

l

WMPT and LMPT boards support only one mode and therefore do not involve mode switching.

8.4.5 Activation The operations on the CME for single-mode base stations such as eGBTS, NodeB, and eNodeB FDD are the same as those for multimode base stations. The operations on the CME in this section are described based on multimode base stations. It is recommended that the Cold Backup of Main Control Boards feature be activated on the CME. Issue 01 (2015-03-23)


36



This section describes the steps for activating the Cold Backup of Main Control Boards feature for a base station that meets the following requirements: l

A main control board has been configured in the base station and the transmission data has been configured for this board.

l

The base station is operating properly.

Using MML Commands Step 1 Modify the base station configurations on the CME. For details, see Step 1 in Using the CME to Perform Single Configuration.

Step 2 Export the deployment list of the base station. For details, see Step 2 in Using the CME to Perform Single Configuration.

Step 3 Upload the deployment list of the base station to the U2000. For details, see Step 3 in Using the CME to Perform Single Configuration.

Step 4 Run the ADD BRD command to add another main control board. Step 5 Run the DSP BRD command to query the slot No. of the active main control board. Step 6 Run the ADD HAGRP command to add an HAGRP MO. In this HAGRP MO, the value of the Logical Slot No. parameter must be the same as the slot No. of the active main control board. ----End NOTE

The preceding steps do not apply to separate-MPT base stations that are running properly. If you need to active the Cold Backup of Main Control Boards feature for such a base station, contact Huawei engineers.

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

Using the CME to Perform Single Configuration Step 1 Modify the base station configurations. Configure the MOs described in the following table on the CME configuration interface. For instructions on how to perform the CME single configuration, see CME Single Configuration Operation Guide. Table 8-3 MOs to be configured on the CME

Issue 01 (2015-03-23)

SN

MO


1

MPT

Add a standby main control board.

2

EHTPORT

Delete the EHTPORT MOs that are automatically configured on the standby main control board.


37



SN

MO


3

HAGRP

Add an HAGRP MO.

Step 2 Export the deployment list of the base station. For details, see section "Preparing a Data Configuration File and a Deployment List" in 3900 Series Base Station Commissioning Guide.

Step 3 Upload the deployment list of the base station to the U2000 so that the DHCP server-related configurations on the U2000 are updated. For details, see section "Creating an NE Commissioning Task" in 3900 Series Base Station Commissioning Guide.

Step 4 Deliver incremental configurations. ----End

Using the CME to Perform Batch Configuration NOTE l

When configuring this feature on the CME, you must perform a single configuration first, and then perform batch modifications if required. You must perform a single configuration for a parameter before batch modifications of the parameter. You are advised to perform batch modifications before logging out of the parameter setting interface.

l

The default display style of the U2000 client is the application style. However, traditional style is more convenient for operations described in this document. All operation guides related to the U2000 client described in this document is based on the traditional style.

l

To change the display change to the traditional style, choose System > Preferences > Client Display Style in the upper left corner of the U2000 client main window.



Step 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 related to the MPT MO for the standby main control board, and close the file.

Step 4 Choose CME > GSM Application/UMTS Application/LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose GSM Application/UMTS Application/LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification.

Step 5 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. Issue 01 (2015-03-23)


38



Delete the redundant data that is automatically generated on the standby main control board, including the Ethernet port data, which corresponds to the ETHPORT MO.


Step 7 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 8 In the summary data file, set the parameters related to the HAGRP MO for the standby main control board, and close the file.



8.4.6 Commissioning Cold backup of UMPT, LMPT, or WMPT boards supports base station deployment using a USB flash drive. To deploy a base station configured with two UMPT, LMPT, or WMPT boards using a USB flash drive, perform the following steps.

Step 1 Remove a main control board. Step 2 Insert the USB flash drive into the other main control board to deploy the base station. Step 3 Remove the USB flash drive. Step 4 Reinstall the main control board that was removed in step 1. After reinstallation, the two main control boards work in active/standby mode. The active main control board is designated by an illuminated ACT indicator ----End

Cold backup of UMPT boards supports base station deployment using plug and play (PnP). In scenarios where the transport network works properly and the UMPT boards do not work in active and standby mode, the UMPT boards will be reset so that they work in the target working mode and in active and standby mode after the base station receives the DHCP packets. Therefore, the deployment of the base station enabled with Cold Backup of Main Control Boards requires an additional 9 to 10.5 minutes compared with that of a base station configured with only one UMPT board. When a base station with cold backup of UMPT boards is to be deployed using PnP, the following requirements must be met: Issue 01 (2015-03-23)


39



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.

8.4.7 Activation Observation Step 1 Run the DSP BRD command to check whether the boards in slots 6 and 7 are normal. If the value of StandBy Status is Active for one board and is Standby for the other board and the value of Availability Status is Normal for both boards, the two boards are normal.

Step 2 Run the LST HAGRP command to check whether two boards with the active/standby transmission capability have been configured as two boards working in active/standby mode. If configuration of the transport high availability (HA) group is available, the two boards with the active/standby transmission capability have been configured as two boards working in active/standby mode.

Step 3 Run the DSP BKPSTATUS command to check the backup status. If Backup Switch is On, cold backup of main control boards is activated. If Backup Status is Idle, initial backup is complete. NOTE

After the standby main control board is configured, initial backup is automatically performed. This initial backup process takes approximately 150 minutes. You can run the DSP BKPSTATUS command to query the backup progress.

Step 4 Run the SWP BRD command to switch the active and standby roles of the main control boards. Upon execution of this board, the base station will automatically perform routine backup, reset, and switchover between the active and standby main control boards, which take about 30 minutes. Base station resets will interrupt ongoing services.

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. Issue 01 (2015-03-23)


40



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

MML Command Examples //Querying the logical slot No. of t he HAGRP LST HAGRP:;

//Querying the slot No. of the active main control board DSP BRD:;

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

//Removing the HAGRP MO. RMV HAGRP: CN=0, SRN=0, SN=6;

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

Using the CME to Perform Single Configuration Step 1 Modify the base station configurations. 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. Table 8-4 Configuring the MOs on the CME

SN

MO


1

HAGRP

Remove the HAGRP MO.

2

MPT

Remove the configuration data for the cold backup of main control boards.

Step 2 Export the deployment list of the base station. For details, see section "Preparing a Data Configuration File and a Deployment List" in 3900 Series Base Station Commissioning Guide. Issue 01 (2015-03-23)


41



Step 3 Upload the deployment list of the base station to the U2000 so that the DHCP server-related configurations on the U2000 are updated. For details, see section "Creating an NE Commissioning Task" in 3900 Series Base Station Commissioning Guide.

Step 4 Deliver incremental configurations. ----End

Using the CME to Perform Batch Configuration You cannot use the CME to perform batch configuration to deactivate this feature.

8.4.9 Reconfiguration N/A


8.6 Parameter Optimization N/A

8.7 Troubleshooting N/A

Issue 01 (2015-03-23)


42


9 Engineering Guidelines for Inter-Board Baseband Resource Redundancy (GSM&UMTS)

9

Engineering Guidelines for Inter-Board Baseband Resource Redundancy (GSM&UMTS)

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

9.2 Required Information None



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. Issue 01 (2015-03-23)


43



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 .


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

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

Paramete r Name

Paramete r ID

Setting Notes

Data Source

Cabinet No.

CN



Subrack No.

SRN



Slot No.

SN

Set this parameter to 0 and 1 for two BBPs in an eGBTS. The NodeB has no special requirement.


Board Type

TYPE

Set this parameter to UBBP for Network plan (negotiation the eGBTS. Set this parameter to not required) WBBP or UBBP for the NodeB as required.

Base Band Work Standard

BBWS

Set this parameter to the modes for Engineering design which the UBBP board provides baseband processing resources.

Issue 01 (2015-03-23)


44



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

Paramete r Name

Paramete r ID

Setting Notes

Data Source

Cabinet No.

CN



Subrack No.

SRN



Slot No.

SN

Set this parameter to 0 and 1 for two BBPs.


Board Type

BT

Set this parameter to UBBP.


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

Issue 01 (2015-03-23)

Parameter Name

Parameter ID

Setting Notes

Baseband Equipment ID

BASEBANDEQMID

For an eGBTS, this parameter is set to 0. For a NodeB, two baseband boards are required (set to 1 and 2, respectively).

Radio network plan (internal)

Baseband Equipment Type

BASEBANDEQMTY PE

For an eGBTS, this parameter is set to ULDL. For a NodeB, BASEBANDEQMI D 1 and BASEBANDEQMI D 2 are set to UL and DL, respectively.

Radio network plan (internal)

UMTS UL Demodulation Mode

UMTSDEMMODE

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


Data Source

45


Parameter Name

Parameter ID

Baseband Equipment Board

BASEBANDEQMBO ARD


Setting Notes This parameter is set based on the cabinet number, subrack number, and slot number of the baseband processing board.

Data Source Equipment plan

9.4.3 Precautions None

9.4.4 Hardware Adjustment N/A

9.4.5 Activation Using MML Commands NodeB

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

Run the MML command ADD BTSBRD to add two UBBPs. eGBTS

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

MML Command Examples NodeB ADD BRD: CN=0, SRN=0, SN=2, BT=UBBP, BBWS=GSM-0&UMTS-1<E_FDD-0<E_TDD-0; ADD BRD: CN=0, SRN=0, SN=1, BT=UBBP, BBWS=GSM-0&UMTS-1<E_FDD-0<E_TDD-0; ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=DL, CN1=0, SRN1=0, SN1=2, CN2=0, SRN2=0, SN2=1; ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=UL, CN1=0, SRN1=0, SN1=2, CN2=0, SRN2=0, SN2=1;

GBTS Issue 01 (2015-03-23)


46



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;

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

Using the CME to Perform Batch Modification This feature does not support batch modification using the CME.

9.4.6 Activation Observation Step 1 Query the carriers deployed on each BBP. l

GBTS: Run the MML command DSP BTSBRDBBINFO to query the carriers deployed on each BBP.

l

eGBTS: Run the MML command DSP GTRX to query the carriers deployed on each BBP.

l

NodeB: Run the MML command DSP ULOCELLRES to query the cells served by each BBP.

Step 2 Run the MML command BLK BRD to block one BBP. Cells served by this BBP will be dynamically reestablished on another operational BBP and services will automatically recover. ----End

9.4.7 Deactivation This feature does not need to be deactivated.



9.6 Parameter Optimization N/A Issue 01 (2015-03-23)


47



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

Issue 01 (2015-03-23)

Alarm ID

Alarm Name

Alarm Type

Alarm Severity

Network Manage ment Type

ALM-26200

Board Hardware Fault

Fault

Major/ Minor

Hardware system

ALM-26204

Board Not In Position

Fault

Major

Hardware system

ALM-26210

Board Blocked

Fault

Major

Operating system

ALM-26214

Board Powered Off

Fault

Major

Hardware system


48


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

10

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

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

10.2 Required Information This section describes information required before deploying Inter-Board Baseband Resource Redundancy for LTE. The following table describes the parameters that must be set in an RRUCHAIN MO.

Issue 01 (2015-03-23)

Parameter Name

Parame ter ID

Descriptio n

Setting Notes

Data Source

Topo Type

TT

This parameter indicates the type of the topology.

Set this parameter to RING(RING) .

Network plan (negotiatio n not required)

Backup Mode

BM

This parameter indicates the backup mode.

Set this parameter to COLD(COLD) or HOT(HOT) based on the network plan.

Network plan (negotiatio n not required)


49



The following table describes the parameters that must be set in an RRU MO.

Parameter Name

Paramet er ID

Descripti on

Setting Notes

Data Source

RRU Chain No.

RCN

This parameter indicates the ID of the RRU chain/ring.

Set this parameter based on the network plan.

Network plan

RRU Position

PS

This parameter indicates the RRU position.

If the RRUCHAIN BM parameter in the associated RRUCHAIN MO is set to COLD(COLD) , RRUs are installed into different positions. For example, the two RRUs in a two-level ring are installed into positions 0 and 1, respectively.

Network plan

If the RRUCHAIN BM parameter in the associated RRUCHAIN MO is set to HOT(HOT) , the RRU in a onelevel ring is installed into position 0.



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

Issue 01 (2015-03-23)


50



10.4.1 Requirements Hardware l l

The eNodeB is configured with two or more LBBPs or UBBPs. The LBBPcs that achieve redundancy must both be LBBPc. The LBBPd and UBBP can be a backup board f or each other.

License None

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

Parameter Name

Parameter ID

Setting Notes

Data Source

Cabinet No.

CN



Subrack No.

SRN



Slot No.

SN

Set this parameter to 1 and 3 for Network plan two BBPs, respectively. (negotiation not required)

TYPE

Set this parameter to LBBP for an LBBP board.

Board Type

Set this parameter to UBBP for a UBBP board.


Work Mode

WM

This parameter must be specified for an LBBP board. For LTE (FDD), set this parameter to FDD. For LTE (TDD), set this parameter to TDD.


Base Band Work Standard

BBWS

This parameter must be specified for a UBBP board. Set this parameter to the modes for which the UBBP board provides baseband processing resources.

Engineering Design

Table 10-2 describes the key parameters that must be set in an RRUCHAIN MO. Issue 01 (2015-03-23)


51



Table 10-2 Key parameters for configuring RRU chains

Parameter Name

Parameter ID

Setting Notes

Data Source

Topo Type

TT

Set this parameter to RING(RING) .


Backup Mode

BM

Set this parameter to COLD(COLD) or HOT(HOT) based on the network plan.


Head Cabinet No.

HCN

Set these parameters based on hardware connections.


Head Subrack No.

HSRN


Head Slot No.

HSN


Head Port No.

HPN


Tail Cabinet No.

TCN


Tail Subrack No.

TSRN


Tail Slot No.

TSN


Tail Port No.

TPN


Table 10-3 describes the key parameters that must be set in an RRU MO.

Issue 01 (2015-03-23)


52



Table 10-3 Key parameters for configuring RF units

Parameter Name

Parameter ID

Setting Notes

Data Source

RRU Chain No.

RCN

Set this parameter based on the network plan.

Network plan

RRU Position

PS

If the RRUCHAIN BM parameter in the associated RRUCHAIN MO is set to COLD(COLD) , RRUs are installed into different positions. For example, the two RRUs in a two-level ring are installed into positions 0 and 1, respectively.

Network plan

If the RRUCHAIN BM parameter in the associated RRUCHAIN MO is set to HOT(HOT) , the RRU in a onelevel ring is installed into position 0.


10.4.4 Hardware Adjustment Connect RRUs to BBPs by referring to Figure 3-1. You can connect all RRUs to one ring. l

If cold backup rings are used, the two BBPs can be configured in any slots.

l

If hot backup rings are used, the two BBPs must be configured in the slots specified in the following table.

If...

Then...

Two LBBPc boards are to be configured

One LBBPc board must be configured in slot 2 or 3, and the 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, two UBBP boards, or one LBBPd and one UBBP board are to be configured

Issue 01 (2015-03-23)

One BBP board must be configured in slot 2 or 3, and the other BBP can be configured in any slot from slot 0 to slot 5. A maximum of six hot backup rings are supported.


53



10.4.5 Activation Using MML Commands You must remove the configurations of all boards before modifying the configurations related to subracks and cabinets. Therefore, you must perform the operations described below locally. You are not advised to use MML commands to initially configure newly deployed eNodeBs. Before delivery of the 3900 series base stations, the main equipment has been preconfigured. Before reconfiguring the site type and cabinets, query the configurations of the main equipment by running the LST ENODEBFUNCTION and LST CABINET commands and remove configurations of all main equipment. Remove and add configurations in the following order: l

Remove cells, sector, RRUs, RRU chains, and boards, successively.

l

Configure boards, RRU chains, and RRUs, successively. Then modify RRU chains. NOTE

The execution of RMV BRD or ADD BRD may lead to eNodeB reset.

Scenario 1: Setting up a Cell on a Cold Backup Ring

Step 1 Run the ADD BRD command to add a board. Step 2 Run the ADD RRUCHAIN command to add an RRU ring. Set Topo Type to RING and Backup Mode to HOT when configuring the RRU ring.

Step 3 Run the MOD RRUCHAIN command to add breakpoints on the RR U ring before adding the RRU.

Step 4 Run the ADD RRU command to add an RRU. Step 5 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding all the RRUs. ----End Scenario 2: Setting up a Cell on a Hot Backup Ring

Step 1 Run the ADD BRD command to add a board. Step 2 Run the ADD RRUCHAIN command to add an RRU ring. Step 3 Set Topo Type to RING and Backup Mode to COLD when configuring the RRU ring. Step 4 Run the MOD RRUCHAIN command to add breakpoints on the RR U ring before adding the RRU.

Step 5 Run the ADD RRU command to add an RRU. Step 6 Run the MOD RRUCHAIN command to remove breakpoints on the RRU ring after adding all the RRUs. ----End

MML Command Examples Scenario 1: Setting up a Cell on a Cold Backup Ring Issue 01 (2015-03-23)


54



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

Scenario 2: Setting up a Cell on a Hot Backup Ring ADD BRD: SN=1, BT=LBBP; ADD BRD: SN=3, BT=LBBP; ADD RRUCHAIN: RCN=0, TT=RING, BM=HOT, HSN=1, HPN=0, TSN=3, TPN=0; MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=0; ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=LRRU, RS=LO, RXNUM=2, TXNUM=2; MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;

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

Using the CME to Perform Batch Modification NOTE

When configuring a feature on the CME, perform a single configuration first, and then perform a batch modification if required. Configure the parameters of a single object before a batch modification. Perform a batch modification before logging out of the parameter setting interface. The default display style of the U2000 client is the application style. However, traditional style is more convenient for operations described in this document. All operation guides related to the U2000 client described in this document is based on the traditional style. To change the display change to the traditional style, choose System > Preferences > Client Display Style in the upper left corner of the U2000 client main window.



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.

Issue 01 (2015-03-23)


55




10.4.6 Activation Observation Scenario 1: Setting up a Cell on a Cold Backup Ring On the U2000 client or LMT, perform the following steps to check whether Inter-Board Baseband Resource Redundancy has been activated in a cold backup ring scenario.

Step 1 Check the status of the cell. Run the DSP CELL command to check the information about a cell. If Cell instance state is Normal, the cell has been activated. Then, check the value of Primary LBBP information to identify the BBP on which the cell is established.

Step 2 Check whether the cell is functional by using UEs to access the cell. If the UEs can successfully access the cell, the cell is functional.

Step 3 Trigger cell reestablishment by running the BLK BRD command to block the BBP on which the cell is established.

Step 4 Repeat Step 1 and Step 2. If the values of the parameters are the same as those in Step1, the cell is functional, the cell has been reestablished on another BBP, and Inter-Board Baseband Resource Redundancy has been activated in a cold backup ring scenario. ----End

Scenario 2: Setting up a Cell on a Hot Backup Ring On the U2000 client or LMT, perform the following steps to check whether Inter-Board Baseband Resource Redundancy has been activated in a hot backup ring scenario.

Step 1 Check the status of the cell. Run the DSP CELL command to check the information about a cell. If Cell instance state is Normal, the cell has been activated. Then, check the value of Primary LBBP information to identify the BBP on which the cell is established.

Step 2 Check whether the cell is functional by using UEs to access the cell 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 t o 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. Issue 01 (2015-03-23)


56



Step 4 Check the status of the cell. Run the DSP CELL command to check the information about a cell. If Cell instance state is Normal, the cell has been activated. Check the value of Bbi slot to determine the BBP on which the cell is currently established. If the BBP on which the cell is established stays the same and Inter-Board Baseband Resource Redundancy has been activated in a hot backup ring scenario. NOTE

When hot backup fails due to insufficient resources, cold backup starts. In this case, UEs served by the cell are released and the cell is reestablished on another BBP.

----End

10.4.7 Deactivation To deactivate Inter-Board Baseband Resource Redundancy, remove the preceding configurations. Add breakpoints on the RF unit ring according to the MML command prompts and MML command help before removing the RF units. To remove an RF unit from a ring, you need to interrupt the logical connection between the RF unit and the BBP and then remove the physical connections. NOTE

To remove an RF unit from a ring, you need to interrupt the logical connection between the RF unit and the BBP and then remove the physical connections. To interrupt the logical connection, run the MOD RRUCHAIN command to add two break points to the ring, with one's position being 0 and the other's position being a value equal to the number of RF units on the ring.

Using MML Commands NOTE

The execution of RMV BRD may lead to an eNodeB reset.

Step 1 Run the RMV CELL command to remove the cell. Step 2 Run the RMV SECTOR command to remove the sector. Step 3 Run the MOD RRUCHAIN command to add breakpoints on the RRU ring before adding the RRU.

Step 4 Run the RMV RRU command to remove the RRU. Step 5 Run the RMV RRUCHAIN command to remove the RRU ring. Step 6 Run the RMV BRD command to remove the board. ----End

MML Command Examples RMV RMV MOD RMV RMV RMV

Issue 01 (2015-03-23)

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


57



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

SN

MO


1

CELL

Remove the configuration data of the cell.

2

SECTOR

Remove the configuration data of the sector.

3

RRUCHAIN

Set breakpoints of the RRU chain or ring.

4

RRU

Remove the configuration data of the RRU.

5

RRUCHAIN

Remove the configuration data of the RRU chain or ring.

6

BBP

Remove the configuration data of the baseband board.

Using the CME to Perform Batch Configuration You cannot use the CME to perform batch configuration to deactivate the Inter-Board Baseband Resource Redundancy feature.




10.7 Troubleshooting Table 10-5 lists alarms related to the Inter-Board Baseband Resource Redundancy feature for the eNodeB. If an alarm described in Table 10-5 is generated, clear the alarm by referring to the alarm handling suggestions in 3900 Series Base Station Alarm Reference. Issue 01 (2015-03-23)


58



Table 10-5 Related alarms

Issue 01 (2015-03-23)

Alarm ID

Alarm Name

Alarm Type

Alarm Severity

Network Manage ment Type

ALM-26210

Board Blocked

Fault

Major

Operating system

ALM-26234

BBU CPRI Interface Error

Fault

Major

Hardware system

ALM-26235

RF Unit Maintenance Link Failure

Fault

Major

Hardware system

ALM-26236

RRU Cascading Levels and Configuration Mismatch

Fault

Major

Hardware system

ALM-26238

RRU Network Topology Type and Configuration Mismatch

Fault

Major

Hardware system


59


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

11

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

11.1 When to Use Intra-Board Baseband Resource Pool (LTE) This feature is activated by default.





11.4 Deployment

Issue 01 (2015-03-23)


60



11.4.1 Requirements Hardware eNodeBs use LBBPc boards.

License None

11.4.2 Data Preparation None


11.4.4 Hardware Adjustment None

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

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

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

11.4.6 Activation Observation Scenario 1: Intra-Board Cell-Level Resource Pool The prerequisite for activation observation is that a DSP chip on the LBBP is faulty and ALM-26200 Board Hardware Fault is reported. Perform the following steps on the U2000 or LMT to check whether the Intra-Board Cell-Level Resource Pool takes effect: Issue 01 (2015-03-23)


61



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 IntraBoard Cell-Level Resource Pool takes effect. ----End

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

11.4.7 Deactivation N/A




11.7 Troubleshooting N/A Issue 01 (2015-03-23)


62


12

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

Engineering Guidelines for Intelligent

Shutdown of Carriers Due to PSU Failure

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





12.4 Deployment Issue 01 (2015-03-23)


63




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

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

MO

Paramet er Name

Parameter ID

Description

Data Source

BTSPS UFP

ISTRANCAB Tran. Cabinet CON Configure d

If this parameter is set to CONFIG(CONFIG) , the power consumption of transmission cabinet must be considered. You are advised to set this parameter to ENABLE.

Network plan

GTRX

Is Main BCCH TRX

ISMAINBCC This parameter indicates whether to Network H enable the TRX to carry the main plan BCCH in the cell.

BTSPS UFP

Service Priority Policy

SRVPRIPOL ICY

This parameter specifies which type of service should be preferentially processed when the PSU is faulty.

Network plan

TRXBI ND2PH YBRD

TRX Board Type

TRXTP

This parameter indicates the type of the TRX board bound to the TRX.

Network plan

Table 12-2 describes the parameter that must be set in the EQUIPMENT MO for activating this feature in an eGBTS, NodeB, or eNodeB.

Issue 01 (2015-03-23)


64



Table 12-2 Parameter for activating this feature in an eGBTS, NodeB, or eNodeB

MO

Paramet er Name

Parameter ID

Description

Data Source

EQUIP MENT

PSU Fault Shutdow n TRX Enabled

PSUFP

This parameter indicates whether Network the BS enters the energy saving plan mode when some PSUs become faulty. If this parameter is set to ON, the BS enters the energy saving mode to reduce power consumption when some PSUs become faulty and the remaining PSUs cannot meet the BS's power requirements. In energy saving mode, the BS shuts down TRXs or reduces their transmit power.


12.4.4 Hardware Adjustment None

12.4.5 Activation Using MML Commands GBTS

Run the SET BTSPSUFP command to configure the parameters of the Intelligent Shutdown of Carriers Due to PSU Failure feature. l

Set Board Parameter Configuration Enabled to YES(YES) .

l

Set Tran. Cabinet Configured based on the actual configurations on the B TS.

l

Set Service Priority Policy to GSM_PRIOR(GSM Traffic Prior) .

l

Do not specify GSM Multi Carrier BTS Standard .

eGBTS/NodeB/eNodeB

Run the SET EQUIPMENT command to set PSU Fault Shutdown TRX Enabled to ON(ON) to enable the Intelligent Shutdown of TRX Due to PSU Failure feature.

MML Command Examples GBTS SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=YES, ISTRANCABCON=CONFIG,SRVPRIPOLICY=GSM_PRIOR;

eGBTS/NodeB/eNodeB Issue 01 (2015-03-23)


65



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

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

Using the CME to Perform Batch Modification This feature does not support batch modification using the CME.

12.4.6 Activation Observation 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

Issue 01 (2015-03-23)


66



12.4.7 Deactivation Using MML Commands GBTS

Run the SET BTSPSUFP command with Board Parameter Configuration Enabled set to NO(NO). eGBTS/NodeB/eNodeB

Run the SET EQUIPMENT command to disable the Intelligent Shutdown of Carriers Due to PSU Failure feature. In this step, set PSU Fault Shutdown TRX Enabled to OFF(OFF) .

MML Command Examples GBTS SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=NO;

eGBTS/NodeB/eNodeB SET EQUIPMENT: BATIMS=ON, PAE=ON, ODIID=67, PSUFP=OFF;

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

SN

MO

NE

Parameter Name

Parameter ID

Setting Notes

1

BTSPSUFP

BSC6900/ BSC6910

Board Parameter Configuratio n Enabled

CFGFLAG

To deactivate this feature, set this parameter to NO.

Table 12-4 Configuring the parameter on the CME (eGBTS/NodeB/eNodeB)

Issue 01 (2015-03-23)

SN

MO

NE

Parameter Name

Parameter ID

Setting Notes

1

EQUIPMENT

eGBTS/ NodeB/ eNodeB

PSU Fault Shutdown TRX Enabled

PSUFP

To deactivate this feature, set this parameter to OFF.


67



Using the CME to Perform Batch Configuration You cannot use the CME to perform batch configuration to deactivate the Intelligent Shutdown of Carriers Due to PSU Failure feature.




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. Table 12-5 Related alarms

Issue 01 (2015-03-23)

Alarm ID

Alarm Name

Alarm Severity

25630

Power Module and Monitoring Module Communication Failure

Major

25626

Power Module Abnormal

Major/Warning


68


13 Parameters

13

Parameters

Table 13-1 Parameters

MO

Parame ter ID

MML Feature Comma ID nd

Feature Name

Description

SECTO R

SECTO RID

ADD SECTO R

None

Meaning: Indicates the number of the sector.

None

GUI Value Range: 0~65535 Unit: None

DSP SECTO R

Actual Value Range: 0~65535 Default Value: None

LST SECTO R MOD SECTO R RMV SECTO R SECTO R

SECTO RANTE NNA

None

None

None

Meaning: Indicates the information about the sector antenna. GUI Value Range: 0~216 Unit: None Actual Value Range: 0~216 Default Value: None

Issue 01 (2015-03-23)


69


13 Parameters

MO

Parame ter ID


Feature Name

Description

MPT

CN

None

None

Meaning: Indicates the cabinet number of the main control and transmission board.

None

GUI Value Range: 0~7 Unit: None Actual Value Range: 0~7 Default Value: None MPT

SRN

None

None

None

Meaning: Indicates the subrack number of the main control and transmission board. GUI Value Range: 0~1 Unit: None Actual Value Range: 0~1 Default Value: None

MPT

SN

None

None

None

Meaning: Indicates the slot number of the main control and transmission board. GUI Value Range: 6~7 Unit: None Actual Value Range: 6~7 Default Value: None

MPT

TYPE

None

None

None

Meaning: Indicates the type of the board. GUI Value Range: UMPT(UMPT), WMPT(WMPT), LMPT(LMPT) Unit: None Actual Value Range: UMPT, WMPT, LMPT Default Value: None

HAGRP

CN

ADD HAGRP

LBFD-0 0202101

RMV HAGRP

MRFD210101

LST HAGRP

Main Processi ng and Transpo rt Unit Cold Backup

Meaning: Indicates the number of the cabinet housing the board where the HA group is established. GUI Value Range: 0~7 Unit: None Actual Value Range: 0~7 Default Value: 0

System Redunda ncy

Issue 01 (2015-03-23)


70


13 Parameters

MO

Parame ter ID


Feature Name

Description

HAGRP

SRN

ADD HAGRP

LBFD-0 0202101

Meaning: Indicates the number of the subrack housing the board where the HA group is established.

RMV HAGRP

MRFD210101

Main Processi ng and Transpo rt Unit Cold Backup

LST HAGRP

GUI Value Range: 0~1 Unit: None Actual Value Range: 0~1 Default Value: 0

System Redunda ncy HAGRP

SN

ADD HAGRP

LBFD-0 0202101

RMV HAGRP

MRFD210101

LST HAGRP

Main Processi ng and Transpo rt Unit Cold Backup System Redunda ncy

RRUCH AIN

TT

ADD None RRUCH AIN MOD RRUCH AIN DSP RRUCH AINPH YTOPO LST RRUCH AIN

None

Meaning: Indicates the logical slot number of the HA group. The logical slot number of an HA group is the number of the physical slot housing one of the two boards constituting the HA group. GUI Value Range: 6~7 Unit: None Actual Value Range: 6~7 Default Value: 6

Meaning: Indicates the type of the topology.In a ring topology, the service data is transmitted on the fiber optic cable that carries the HDLC link. In a load sharing topology, the service data is transmitted on two fiber optic cables simultaneously, which enhances the transmission capability. The physical connection in the ring topology is similar to that in the load sharing topology. GUI Value Range: CHAIN(CHAIN), RING(RING), LOADBALANCE(LOADBALANCE) Unit: None Actual Value Range: CHAIN, RING, LOADBALANCE Default Value: None

Issue 01 (2015-03-23)


71


13 Parameters

MO

Parame ter ID


Feature Name

Description

RRUCH AIN

BM

ADD None RRUCH AIN

None

Meaning: Indicates the backup mode of the RRU chain/ring. There are two modes: cold backup and hot backup. Cold backup indicates that when the link on one end of the chain/ring fails, the service is disrupted for a short period of time, and then re-established on the other end of the chain/ring. Hot backup indicates that when the link on one end of the chain/ring fails, the service is taken over by the other end of the chain/ ring immediately. There is only one RRU on the chain/ring in hot backup mode.In the RRUCHAIN MO, if TT is set to RING and BM is set to HOT, the head CPRI port and the tail CPRI port of the RRU ring must be on different baseband boards.

MOD RRUCH AIN LST RRUCH AIN

GUI Value Range: COLD(COLD), HOT(HOT) Unit: None Actual Value Range: COLD, HOT Default Value: COLD(COLD) RRU

RCN

ADD RRU

None

None

LST RRU

Meaning: Indicates the ID of the RRU or RFU chain/ ring. GUI Value Range: 0~249 Unit: None Actual Value Range: 0~249 Default Value: None

RRU

PS

ADD RRU

None

None

LST RRU

Meaning: Indicates the position of the RRU, RFU, or RHUB on the chain or ring. It is calculated from the start port one by one. GUI Value Range: 0~20 Unit: None Actual Value Range: 0~20 Default Value: None

BBP

CN

Issue 01 (2015-03-23)

DSP BBPTC

None

None

Meaning: Indicates the cabinet number of the baseband processing board.

LST BBP

GUI Value Range: 0~7

MOD BBP

Actual Value Range: 0~7

Unit: None Default Value: 0


72


13 Parameters

MO

Parame ter ID


Feature Name

Description

BBP

SRN

DSP BBPTC

None

Meaning: Indicates the subrack number of the baseband processing board.

BBP

SN

None

LST BBP

GUI Value Range: 0~1

MOD BBP


DSP BBPTC

Unit: None Default Value: 0 None

None

LST BBP

Meaning: Indicates the slot number of the baseband processing board. Baseband processing boards can be configured only in slots 0 to 5 and the multimode digital unit can be configured only in slot 6. GUI Value Range: 0~6

MOD BBP

Unit: None Actual Value Range: 0~6 Default Value: None

BBP

TYPE

MOD BBP

None

None

Meaning: Indicates the type of the board. GUI Value Range: UBBP(UBBP), GBBP(GBBP), WBBP(WBBP), LBBP(LBBP), LPMP(LPMP) Unit: None Actual Value Range: UBBP, GBBP, WBBP, LBBP, LPMP Default Value: None

Issue 01 (2015-03-23)


73


13 Parameters

MO

Parame ter ID


Feature Name

Description

BBP

WM

ADD BRD

None

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

MOD BBP LST BBP

None

GUI Value Range: FDD(Frequency Division Duplex), TDD(Time Division Duplex), HYBRID(HYBRID), TDD_ENHANCE(Support TDD BF), TDD_8T8R(Support CPRI ports), TDD_TL(Support CMCC TDS and TDL dual modes), FDD_ATG(Support air-ground communication) Unit: None Actual Value Range: FDD, TDD, HYBRID, TDD_ENHANCE, TDD_8T8R, TDD_TL, FDD_ATG Default Value: FDD(Frequency Division Duplex)

Issue 01 (2015-03-23)


74


13 Parameters

MO

Parame ter ID


Feature Name

Description

BBP

BBWS

ADD BRD

None

Meaning: Indicates the modes for which the UBBP or UMDU provides baseband processing resources. If the UBBP or UMDU provides only CPRI ports for a mode, you do not need to configure this mode for the UBBP or UMDU.

None

MOD BBP LST BBP

GUI Value Range: GSM(GSM), UMTS(UMTS), LTE_FDD(LTE FDD), LTE_TDD(LTE TDD) Unit: None Actual Value Range: GSM, UMTS, LTE_FDD, LTE_TDD Default Value: GSM:NO, UMTS:NO, LTE_FDD:NO, LTE_TDD:NO

RRUCH AIN

HCN

ADD None RRUCH AIN

None

Meaning: Indicates the cabinet number of the board where the head CPRI port is located. GUI Value Range: 0~7

MOD RRUCH AIN

Unit: None

DSP RRUCH AINPH YTOPO

Default Value: 0


LST RRUCH AIN RRUCH AIN

HSRN

ADD None RRUCH AIN

None

Meaning: Indicates the subrack number of the board where the head CPRI port is located. GUI Value Range: 0~1,60~254

MOD RRUCH AIN

Unit: None


Default Value: 0

Actual Value Range: 0~1,60~254

LST RRUCH AIN

Issue 01 (2015-03-23)


75


13 Parameters

MO

Parame ter ID


Feature Name

Description

RRUCH AIN

HSN

ADD None RRUCH AIN

None

Meaning: Indicates the slot number of the board where the head CPRI port is located. GUI Value Range: 0~6

MOD RRUCH AIN

Unit: None


Default Value: None



HPN

ADD None RRUCH AIN

None

Meaning: Indicates the number of the head CPRI port. GUI Value Range: 0~7 Unit: None

MOD RRUCH AIN


DSP RRUCH AINPH YTOPO LST RRUCH AIN RRUCH AIN

TCN

ADD None RRUCH AIN MOD RRUCH AIN DSP RRUCH AINPH YTOPO

None

Meaning: Indicates the cabinet number of the board where the tail CPRI port is located.Value located.Value NULL is displayed for the RRU chain which does not have a tail CPRI port. GUI Value Range: 0~7 Unit: None Actual Value Range: 0~7 Default Value: 0

LST RRUCH AIN

Issue 01 (2015-03-23)


76


13 Parameters

MO

Parame ter ID


Feature Name

Description

RRUCH AIN

TSRN

ADD None RRUCH AIN

None

Meaning: Indicates the subrack number of the the board where the tail CPRI port is located.Value located.Value NULL is displayed for the RRU chain which does not have a tail CPRI port.

MOD RRUCH AIN

GUI Value Range: 0~1,60~254 Unit: None


Actual Value Range: 0~1,60~254 Default Value: 0


TSN

ADD None RRUCH AIN

None

MOD RRUCH AIN

Meaning: Indicates the slot number of the board where the tail CPRI port is located.Value located.Value NULL is displayed for the RRU chain which does not have a tail CPRI port. GUI Value Range: 0~6 Unit: None




TPN

ADD None RRUCH AIN MOD RRUCH AIN DSP RRUCH AINPH YTOPO

None

Meaning: Indicates the number of the tail CPRI port. port. Value NULL is displayed for the RRU chain which does not have a tail CPRI port. GUI Value Range: 0~7 Unit: None Actual Value Range: 0~7 Default Value: None

LST RRUCH AIN

Issue 01 (2015-03-23)


77


13 Parameters

MO

Parame ter ID


Feature Name

EQUIP MENT

PSUFP

SET EQUIP MENT

Intellige Meaning: Indicates whether the BS enters the energy nt saving mode when some PSUs become faulty. If this Shutdow parameter is set to ON, ON, the BS enters the energy energy n of saving mode to reduce power consumption when TRX some PSUs become faulty and the remaining PSUs Due to cannot meet the BS's power requirements. In energy PSU saving mode, the BS shuts down TRXs or reduces Failure their transmit power. power.

LST EQUIP MENT

GBFD-1 17804

Description

GUI Value Range: ON(ON), OFF(OFF) Unit: None Actual Value Range: ON, OFF Default Value: OFF(OFF)

Issue 01 (2015-03-23)


78


14 Counters

14

Counters

There are no specific counters associated with this feature.

Issue 01 (2015-03-23)


79


15 Glossary

15

Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 01 (2015-03-23)


80

Base Station Equipment Reliability(SRAN10.1_01)

Recommend Documents