Base Station Controller Equipment Reliability (SRAN11.1 - 01) PDF

SingleRAN
Base Station Controller Equipment

Reliability Feature Parameter
Description
Issue 01
Date 2016-02-29
HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 2
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 3
2.3 Architecture.................................................................................................................................................................... 3
3 Reliability Specifications.............................................................................................................7
4 Planned Service Interruption...................................................................................................... 8
4.1 Overview........................................................................................................................................................................ 8
4.2 BSC/RNC Software Management.................................................................................................................................. 8
5 Redundancy Design.................................................................................................................... 11
5.1 Overview.......................................................................................................................................................................11
5.2 RNC Redundancy Design.............................................................................................................................................12
5.2.1 Resource Management Plane.....................................................................................................................................12
5.2.2 Control plane............................................................................................................................................................. 12
5.2.3 User Plane..................................................................................................................................................................14
5.2.4 Transport Plane.......................................................................................................................................................... 14
5.3 BSC Redundancy Design............................................................................................................................................. 15
5.3.1 Resource Management Plane.....................................................................................................................................15
5.3.2 Control Plane............................................................................................................................................................. 16
5.3.3 User Plane..................................................................................................................................................................18
5.3.4 Transport Plane.......................................................................................................................................................... 19
5.4 BSC/RNC Resource Sharing........................................................................................................................................ 19
6 Network Redundancy.................................................................................................................20
7 Fault Management.......................................................................................................................22
8 Flow Control................................................................................................................................. 23
9 Operation and Maintenance Reliability................................................................................. 24
Issue 01 (2016-02-29) Huawei Proprietary and Confidential ii

SingleRAN
Parameter Description Contents
9.1 Overview...................................................................................................................................................................... 24
9.2 Technical Description................................................................................................................................................... 24
10 Hardware Reliability................................................................................................................ 28
11 Related Features.........................................................................................................................31
12 Network Impact......................................................................................................................... 32
13 Engineering Guidelines........................................................................................................... 33
13.1 When to Use Operation & Maintenance System One-Key Recovery........................................................................33
13.2 Deployment................................................................................................................................................................ 33
13.2.1 Process..................................................................................................................................................................... 33
13.2.2 Requirements........................................................................................................................................................... 33
13.2.3 Activation................................................................................................................................................................ 33
13.2.4 Activation Observation............................................................................................................................................34
13.2.5 Deactivation.............................................................................................................................................................34
13.3 Performance Monitoring.............................................................................................................................................34
13.4 Troubleshooting.......................................................................................................................................................... 34
14 Parameters................................................................................................................................... 35
15 Counters...................................................................................................................................... 36
16 Glossary....................................................................................................................................... 39
17 Reference Documents............................................................................................................... 40
Issue 01 (2016-02-29) Huawei Proprietary and Confidential iii

SingleRAN
Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the Base Station Controller Equipment Reliability feature, including
its technical principles, related features, network impact, and engineering guidelines.
1.2 Intended Audience

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

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change:
Changes in features of a specific product version
l Editorial change:
Changes in wording or addition of information that was not described in the earlier
version
SRAN11.1 01 (2016-02-29)
This issue does not include any changes.
SRAN11.1 Draft A (2015-12-30)

Compared with issue 02 (2015-11-30) of SRAN10.1, Draft A (2015-12-30) of SRAN11.1
includes the following changes.
Issue 01 (2016-02-29) Huawei Proprietary and Confidential 1

SingleRAN
Parameter Description 1 About This Document
Change Change Description Parameter Change

Type
Feature Added the descriptions of the board redundancy None

change for EGPUb/EXPUb boards. For details, see the
following sections:
5.4 BSC/RNC Resource Sharing
10 Hardware Reliability
Editorial None None

change
1.4 Differences Between Base Station Types

The features described in this document apply only to macro base stations.

SingleRAN
Parameter Description 2 Overview
2 Overview
2.1 Introduction
Reliability designs enable the controller to continue providing services even when it
experiences a fault, thereby maintaining high system reliability. Objectives of reliability
include:
l Decreasing the number of accidents
l Minimizing the scope of fault influence
l Shortening the duration of service interruption
Controller reliability designs include system availability, planned service interruption,
redundancy design, network redundancy, fault management, flow control, operation and
maintenance reliability, and hardware reliability.
2.2 Benefits
Reliability designs, which include redundancy design and hardware reliability design,
eliminate or reduce the impact of equipment faults on services, thereby improving system
reliability.
2.3 Architecture
Table 1 lists the controller equipment reliability-related features and functions that are
supported by GSM and UMTS.

SingleRAN
Table 2-1 Controller equipment reliability-related features and functions that are supported by
GSM and UMTS
Reliability Feature/ Radio Feature ID/ Remarks
Category Function Access Feature Name
Technology
Planned BSC/RNC GSM and MRFD-210401 For details about

service Software UMTS BSC/RNC engineering
interruption Managemen Software guidelines, see
t Management Operation and
Maintenance Feature
Parameter
Description.
Redundancy RNC UMTS None For details, see 5.2

design Redundancy RNC Redundancy
Design.
BSC GSM None For details, see 5.3

Redundancy BSC Redundancy
Design.
BSC/RNC GSM and MRFD-210104 For details about

Resource UMTS BSC/RNC engineering
Sharing Resource Sharing guidelines, see
Controller Resource
Sharing Feature
Parameter
Description in
WCDMA RAN
documents.
Network RNC in UMTS l WRFD-150211 For details about

redundancy Pool RNC in Pool engineering
Load Sharing guidelines, see RNC
l WRFD-150212 in Pool Feature
RNC in Pool Parameter
Node Description in
Redundancy WCDMA RAN
documents.
l WRFD-150240
RNC in Pool
Multiple
Logical RNCs
RNC Node UMTS WRFD-040202 For details about

Redundancy RNC Node engineering
Redundancy guidelines, see RNC
Node Redundancy
Feature Parameter
Description in
WCDMA RAN
documents.

SingleRAN

Technology
BSC Node GSM GBFD-113725 For details about

Redundancy BSC Node engineering
Redundancy guidelines, see BSC
Node Redundancy
Feature Parameter
Description in GSM
BSS documents.
MSC Pool GSM GBFD-117401 For details about

MSC Pool engineering
guidelines, see MSC
Pool Feature
Parameter
Description in GSM
BSS documents.
SGSN Pool GSM GBFD-119701 For details about

SGSN Pool engineering
guidelines, see SGSN
Pool Feature
Parameter
Description in GSM
BSS documents.
TC Pool GSM GBFD-113726 TC For details about

Pool engineering
guidelines, see TC
Pool Feature
Parameter
Description in GSM
BSS documents.
Fault Fault GSM and MRFD-210304 For details about

management Managemen UMTS Fault Management engineering
t guidelines, see Fault
Management Feature
Parameter
Description in
SingleRAN
documents.
Flow control RNC Flow UMTS WRFD-040100 For details about

Control Flow Control engineering
guidelines, see Flow
Control Feature
Parameter
Description in
WCDMA RAN
documents.

SingleRAN

Technology
BSC Flow GSM l GBFD-111705 For details about

Control GSM Flow engineering
Control guidelines, see Flow
l GBFD-119117 Control Feature
Flow Control Parameter
on Gb Interface Description in GSM
BSS documents.
l GBFD-119116
Packet Uplink
Flow Control
l GBFD-511003
Call-Based
Flow Control
l GBFD-115002
Flow Control
Based on Cell
Priority
l GBFD-115003
Flow Control
Based on User
Priority
Operation Operation GSM and GBFD-111214 For details, see 9

and and UMTS Operation & Operation and
maintenance Maintenanc Maintenance Maintenance
reliability e System System One-Key Reliability.
One-Key Recovery
Recovery
Hardware BSC/RNC GSM and None For details, see 10

reliability Board UMTS Hardware
Redundancy Reliability.

SingleRAN
Parameter Description 3 Reliability Specifications
3 Reliability Specifications
Table 3-1 Reliability specifications

Index Value
System availability > 99.999%
Mean time between failures (MTBF) 525000 hours
Mean time to repair (MTTR) 1 hour

SingleRAN
Parameter Description 4 Planned Service Interruption
4 Planned Service Interruption
4.1 Overview
Planned service interruption aims to reduce the duration of service interruption caused by
upgrades, minimize the impact of planned maintenance on live networks, and improve
equipment availability. Planned service interruption supports hot patches.
4.2 BSC/RNC Software Management

Overview
This section describes the MRFD-210401 BSC/RNC Software Management feature. For
details, see Operation and Maintenance Feature Parameter Description.
Huawei controllers support the uniform software management of GSM base station system
(GBSS) and radio access network (RAN), facilitating the remote management of the
controller software and improving the efficiency of software upgrades and downloads.
With this feature, users can implement the following operations on the U2000.
l Querying the software version and its status

l Uploading, downloading, and activating the program files, patch files, and license files
l Using the OMU of the controller as the FTP server and transmitting files such as
program files and patch files between the FTP server and FTP client
l Using the controller as the transmission medium to transmit files between the U2000 and
the MBTS
In addition, users can manage the programs, patches, licenses, and logs using the Web LMT.
The controller supports the software integrity check. The controller performs the software
integrity check after software loading and before software operation, and then completes
digital signature verification.
The BSC/RNC is upgraded remotely by the dedicated upgrade tool, which consists of the
upgrade client and the upgrade server. Figure 4-1 shows the BSC/RNC remote upgrade
process.

SingleRAN
Figure 4-1 BSC/RNC remote upgrade process
The remote upgrade process is as follows:
Step 1 Upload the upgrade server program and the version files required for the upgrade (such as a
major release or patch version) to a specified directory of the active OMU. In addition,
synchronize the upgrade directory of the standby OMU with the specified directory of the
active OMU.
Step 2 Conduct the pre-upgrade health check, backs up data and files, and upgrades the program and
data files in the standby workspace of the active OMU and standby OMU.
Step 3 Load the host program, BootROM, operating system (OS), and data files in the standby
workspace of the active OMU onto the standby workspaces of the FAM boards so that the
standby workspaces of the FAM boards are synchronized with that of the OMU.
Step 4 After the synchronization is successful, switch over the active and standby workspaces of the
active OMU so that the active OMU is upgraded to the latest version.
Step 5 Switch over the active and standby workspaces of the FAM boards. When the platform host
program, BootROM, OS or data files are upgraded, the FAM boards are reset. When a cold
patch is loaded to a type of FAM boards, only this type of FAM board is reset and the boards
automatically load the program and data files from their flash memories to complete the
upgrade. Hot patches adopt one-click installation.
Step 6 After the service verification is successful, switch over the active and standby workspaces of
the standby OMU so that the standby OMU is upgraded to the latest version. After the
workspace switchover is complete for the standby OMU, the standby OMU automatically
synchronizes its data with the active OMU.
----End
Key Specifications
Table 4-1 lists key specifications for BSC/RNC software management.

SingleRAN
Table 4-1 Key specifications for BSC/RNC software management

Index Version Implementation
Service interruption duration caused by an Service interruption duration 3 min

upgrade for a major release
Service interruption duration caused by a No service interruption for a hot patch

patch upgrade upgrade
Service interruption duration for a cold
patch upgrade 3 min
Reloading time 7 min
Time from power-on to management 10 min

recovery
Time from power-on to first NodeB 10 min

recovery
Time from power-on to the recovery of all 12 min

sites

SingleRAN
Parameter Description 5 Redundancy Design
5 Redundancy Design
5.1 Overview
This section describes the MRFD-210101 System Redundancy feature and the GBFD-111701
Board Switchover feature. System redundancy provides reliability designs that improve
system reliability. These designs include active/standby switchovers and load sharing.
Huawei base station controllers adopt reliability designs, such as load sharing and active/
standby switchovers, to ensure the reliable operation of the system.
l Active/standby switchovers
In active/standby mode, the active board processes services while the standby board acts
as a backup for the active one. When the active board is faulty or needs to be replaced,
services on the active board are switched over to the standby board to ensure normal
service operations.
There are two types of switchovers:
Automatic switchover: automatically triggered by the system if the active board is
faulty.
Manual switchover: performed by maintenance personnel on the LMT.
Maintenance personnel use the immediate switchover command to switch over the
active and standby boards.
A successful active/standby switchover requires the following:
The standby board works normally.
No major or critical alarm is reported on the standby board.
When the standby board is switched over to the active state, the previously active board
is reset automatically. If this board restarts normally, it is switched over to the standby
state.
l Load sharing
In resource pool mode, load sharing is performed among processing units in the pool.
When one or multiple processing units are faulty, new service requests are allocated to
the normal processing units in the resource pool.
l Other reliability designs

SingleRAN
Other reliability designs include the redundancy configuration of power and fan units. In
addition, software versions and important data configuration files are backed up so that
the system works normally even if an exception occurs in the software versions and files.
5.2 RNC Redundancy Design
5.2.1 Resource Management Plane

The BSC6900 main processing unit (MPU) subsystems can be configured on multiple pairs of
SPU boards working in active/standby mode. The MPU subsystems manage transmission
resources and enable control- and user-plane load sharing.
The BSC6910 resource management plane consists of the central layer and local layer.
l The central layer manages global resources, including the control plane, user plane, and
transport plane resources, and troubleshoots system faults.
A pair of Resource Management Processing (RMP) boards perform the central layer
functions.
l The local layer manages board-level resources.
A UCUP board performs the local layer functions.
RMP boards have the following characteristics:
l The CPU usage does not increase noticeably with the increase in the Busy Hour Call
Attempt (BHCA) or throughput. A sudden increase in the CPU usage is allowed within a
short period of time.
l A temporary fault in an RMP board does not interrupt ongoing services. This is because
only global resource scheduling is interrupted if an RMP board is faulty.
5.2.2 Control plane

For the BSC6900, the SPU boards, which work in active/standby mode, process control plane
data.
For the BSC6910, the UCUP boards process control plane data. Processes on the control
plane work in active/standby mode. Every active CP process on a UCUP board has a backup
on another UCUP board, as shown in Figure 5-1.

SingleRAN
Figure 5-1 Control-plane redundancy design for the BSC6910
NOTE
CP stands for the control plane and UP stands for the user plane.
The redundancy design is similar for the BSC6900 and BSC6910 control planes. The
differences are as follows:
l A pair of BSC6900 active and standby control plane boards must be installed in adjacent
slots.
l The BSC6910 control plane uses the process backup mechanism. All active CP
processes on a UCUP board have backups evenly distributed on the two adjacent UCUP
boards.
When the BSC6900 or BSC6910 is running, the cell status, NodeB status, and online UE
information on the active subsystem are sent to the standby subsystem through the backup
channel. The standby subsystem then backs up the data. If the active subsystem is faulty, the
standby subsystem takes over services on the active subsystem to avoid service interruptions.
In addition to the redundancy design, the BSC6910 control plane also supports process
preemption. If a pair of active and standby CP processes of the BSC6910 are both faulty for a
certain period of time (less than 5 minutes), the BSC6910 preempts another standby CP
process to start the active CP process, thereby restoring services promptly.

SingleRAN
5.2.3 User Plane

For the BSC6900, the digital signal processors (DSPs) in DPU boards process user plane data.
The DSPs work in resource pool mode.
For the BSC6910, the UCUP board processes user plane data. The user plane resources work
in resource pool mode, as shown in Figure 5-2.
Figure 5-2 User-plane redundancy design for the BSC6910
If a user plane subsystem is faulty, the common channels for the cells carried on the
subsystem are reestablished, and services are interrupted for less than 5 seconds and then
restored. During the service interruption, CS services are released, and PS services are
interrupted and then reconnected. The user-plane processing capability decreases, but the
other functional user plane subsystems still work in resource pool mode.
The redundancy design is the same for the BSC6900 and BSC6910 user planes. Neither
supports user-plane service backup.
5.2.4 Transport Plane

The redundancy design is the same for the BSC6900 and BSC6910 transport planes. They
both support board redundancy, port backup/load sharing, and resource pool mode.
A transport interface board supports the following:
l 1+1 active/standby redundancy
When detecting that an interface board is faulty, the system performs an active/standby
switchover to reestablish the transmission links for the ongoing services on the standby
board. When detecting that the active channel is unavailable, the system performs an
active/standby switchover to enable the ongoing services to be transmitted through the
standby channel.
l Port backup or load sharing
l Resource pool
In conclusion, the resource management plane, control plane, user plane, and transport plane
all support the redundancy design. Therefore, the BSC6900 and BSC6910 do not experience a
single point of failure.

SingleRAN
Table 5-1 describes the reliability indexes for transmission interface boards in different
scenarios.
Table 5-1 Reliability indexes for transmission interface boards in different scenarios
Scenario Availability Average Quantitative
Downtime Reliability
(Minute/Year) Analysis
1+1 active/standby 0.999999796 0.11 Low task reliability

redundancy and low basic
reliability under the
same traffic volume
1+1 active/standby 0.999999918 0.04 High task reliability

redundancy plus and low basic
resource pool reliability under the
same traffic volume
Independent board 0.999999183 0.43 Low task reliability

plus resource pool and high basic
same traffic volume
N+1 resource pool 0.999999836 0.09 High task reliability

and high basic
same traffic volume
Table 5-2 Key specifications of transmission redundancy

Index Version Implementation
Switchover for interface boards The impact persists within 3s for ongoing services.
Switchover for other boards New services can be admitted in 15s.
NOTE
The delay caused by protocol negotiation with the peer equipment is not considered in the preceding
indexes. For example, if Link Aggregation Control Protocol (LACP) is enabled, the impact of a
switchover between interface boards persists within 9s for ongoing services.
5.3 BSC Redundancy Design
5.3.1 Resource Management Plane

The BSC6900 MPU subsystems can be configured on multiple pairs of XPU boards working
in active/standby mode. The MPU subsystems manage transmission resources and enable
control- and user-plane load sharing.

SingleRAN
The BSC6910 resource management plane consists of the central layer and local layer.
l The central layer manages global resources, including the control plane, user plane, and
transport plane resources, and troubleshoots system faults.
The BSC6900 is configured with a pair of boards whose logical type is resource
management processing (RMP). The boards are responsible for managing global
resources and troubleshooting system faults.
l The local layer manages board-level resources.
NOTE
The boards whose logical type is GCUP or GMCP (referred to as GCUP or GMCP boards) manage
board-level resources. GCUP or GMCP is short for GSM BSC Control plane and User plane Processing.
The boards whose logical type is RMP (referred to as RMP boards) have the following
characteristics:
l The CPU usage does not increase noticeably with the increase in the Busy Hour Call
Attempt (BHCA) or throughput. A sudden increase in the CPU usage is allowed within a
short period of time.
l A temporary fault in an RMP board does not interrupt ongoing services. This is because
only global resource scheduling is interrupted if an RMP board is faulty.
5.3.2 Control Plane

For the BSC6900, the XPU boards, which work in active/standby mode, process control plane
data.
For the BSC6910, the boards whose logical type is GCUP or GMCP process control plane
data. Processes on the control plane work in active/standby mode. Every active CP process on
a board whose logical type is GCUP or GMCP has a backup on another board whose logical
type is GCUP or GMCP, Figure 5-3 shows the control-plane redundancy design for the
BSC6910 using an EGPUa as an example.

SingleRAN
Figure 5-3 Control-plane redundancy design for the BSC6910
NOTE
The redundancy design is similar for the BSC6900 and BSC6910 control planes. The
differences are as follows:
l A pair of BSC6900 active and standby control plane boards must be installed in adjacent
slots.
l The BSC6910 control plane uses the process backup mechanism. All active CP
processes on a board whose logical type is GCUP or GMCP have backups evenly
distributed on the two adjacent boards whose logical type is GCUP or GMCP.
When the BSC6900 or BSC6910 is running, the cell status, BTS status, and online MS
information on the active subsystem are sent to the standby subsystem through the backup
channel. The standby subsystem then backs up the data. If the active subsystem is faulty, the
standby subsystem takes over services on the active subsystem to avoid service interruptions.
In addition to the redundancy design, the BSC6910 control plane also supports process
preemption. If a pair of active and standby CP processes of the BSC6910 are both faulty for a

SingleRAN
certain period of time (less than 5 minutes), the BSC6910 preempts another standby CP
process to start the active CP process, thereby restoring services promptly.
5.3.3 User Plane

For the BSC6900, the digital signal processors (DSPs) in DPU boards process user plane data.
The DSPs work in resource pool mode.
For the BSC6910, the boards whose logical type is GCUP or GMCP process user plane data.
The user plane resources work in resource pool mode, Figure 5-4 shows the user-plane
redundancy design for the BSC6910 using an EGPUa as an example.
Figure 5-4 User-plane redundancy design for the BSC6910
NOTE
If a user plane subsystem is faulty, CS services are released, and PS services are interrupted
and then reconnected. The user-plane processing capability decreases, but the other functional
user plane subsystems still work in resource pool mode.
The redundancy design is the same for the BSC6900 and BSC6910 user planes. Neither
supports user-plane service backup.

SingleRAN
5.3.4 Transport Plane

The transmission redundancy design for a BSC is the same as that for an RNC. For details,
see 5.2.4 Transport Plane.
5.4 BSC/RNC Resource Sharing

This section describes the MRFD-210104 BSC/RNC Resource Sharing feature. For details
about the engineering guidelines, see Controller Resource Sharing Feature Parameter
Description.
l BSC6900 control plane resource sharing
Control plane resource sharing is used to share the CPU usage and memory. When the CPU
usage of a certain control-plane processing unit is too high or the memory of a certain control-
plane processing unit is insufficient, new calls are forwarded to other control-plane processing
units with light load.
l BSC6900 user plane resource sharing
The RNC implements dynamic resource sharing based on the resource pool and load
balancing. If a certain user-plane processing unit is overloaded, new services are forwarded to
other user-plane processing units with light load.
For details on load sharing, see Flow Control Feature Parameter Description.
l BSC6910 UMTS user plane and control plane dynamic sharing
The BSC6910 dynamically adjusts the numbers of multi-core DSPs allocated to the control
plane and user plane based on service requirements. These adjustments improve hardware
utilization by balancing the control-plane and user-plane processing capabilities.
The BSC6910 introduces a new service processing board: GPU. The GPU board can
simultaneously process user-plane and control-plane data. The BSC6910 monitors the user-
plane and control-plane resource usage and adjusts resources (multi-core DSPs) for each
plane proportionately. For details, see the RNC User Plane and Control Plane Resource
Sharing Feature Parameter Description.
l Automatic base station and cell allocation in the BSC6910 UMTS
The BSC6910 automatically allocates a new base station or cell to an EGPUa or EGPUb
board. When configuring a base station or cell on the BSC6910, telecom operators do not
need to specify the subrack, slot, or subsystem. In addition, the BSC6910 monitors the
distribution of base stations and cells on the EGPUa or EGPUb boards. When EGPUa or
EGPUb boards experience a load imbalance because there are hotspot base stations or cells,
the BSC6910 adjusts the distribution of base stations or cells on the EGPUa or EGPUb boards
to achieve load balancing.
Dynamic reallocation of cells can be performed during peak hours, whereas dynamic
reallocation of base stations must be performed during off-peak hours. During cell
reallocation, UEs in the CELL_DCH state in the cell do not drop from the network. During
base station reallocation, services carried by the base station are interrupted, and UEs
controlled by the base station experience call drops. Operators can schedule the time for base
station reallocation. For details, see Controller Resource Sharing Feature Parameter
Description.

SingleRAN
Parameter Description 6 Network Redundancy
6 Network Redundancy
Network redundancy improves the reliability of a network by implementing network-level

redundancy functions. Table 6-1 describes these functions.
Table 6-1 Network redundancy functions of each mode

Mode Function Description Reference
UMTS WRFD-15021 This feature implements redundancy RNC in Pool

2 RNC in among RNCs, which prevents service Feature
Pool Node interruption caused by RNC equipment Parameter
Redundancy faults and improves service reliability. Description
UMTS WRFD-04020 In the RNC node redundancy solution, RNC Node

2 RNC Node each of the two RNCs works as the Redundancy
Redundancy standby RNC for the other. In normal Feature
situations, both RNCs are in service and Parameter
therefore the equipment can be fully Description
utilized. When one of the RNCs fails, the
other automatically takes over all the
dual-homed NodeBs to protect the
NodeBs from being out of service.
GSM GBFD-11372 When IP networking is implemented BSC Node

5 BSC Node over the A interface, Abis interface, and Redundancy
Redundancy interface between BSCs, this feature Feature
enables two BSCs to form a redundancy Parameter
group. If one BSC fails, for example, all Description
the signaling links over the A interface
of the BSC are disconnected, the other
BSC takes over services from the failed
BSC.

SingleRAN
Parameter Description 6 Network Redundancy
Mode Function Description Reference
GSM GBFD-11740 An MSC pool consists of a group of MSC Pool

1 MSC Pool MSCs handling the traffic generated Feature
from one MSC pool. A BSC belonging Parameter
to an MSC pool area is connected to each Description
MSC in the MSC pool. With resource
and load sharing, the traffic is evenly
distributed to all the MSCs in an MSC
pool, reducing inter-MSC handovers and
implementing MSC node redundancy.
GSM GBFD-11970 This feature enables multiple SGSNs to SGSN Pool

1 SGSN Pool form an SGSN pool for resource sharing Feature
and load balancing. A BSC in an SGSN Parameter
pool is connected to all SGSNs in the Description
SGSN pool. Traffic load is evenly
distributed to all SGSNs in the SGSN
pool, reducing the number of inter-SGSN
handovers and implementing SGSN node
redundancy.
GSM GBFD-11372 Huawei GSM base station subsystem TC Pool

6 TC Pool (GBSS) allows a maximum of 16 BSCs Feature
to connect to the transcoder subracks Parameter
(TCSs) of another BSC so that these Description
BSCs can share transcoding (TC)
resources. In this manner, the TCSs form
a TC pool for all BSCs, implementing
load sharing.

SingleRAN
Parameter Description 7 Fault Management
7 Fault Management
Fault management detects and records device faults and notifies users of the detected faults
and associated troubleshooting methods. This helps maintenance personnel quickly locate and
rectify faults, minimizing the impact of faults on network running. For details, see Fault
Management Feature Parameter Description.

SingleRAN
Parameter Description 8 Flow Control
8 Flow Control
Flow control is a protective measure for communications between the BSC or RNC and its
peer equipment. Flow control provides protection in the following ways:
l It restricts incoming traffic to:
Protect equipment from overload, thereby maintaining system stability.
Ensure that equipment can properly process services even under heavy traffic.
l It restricts outgoing traffic to reduce the load on the peer equipment.
For details about flow control for BSCs/RNCs, see Flow Control Feature Parameter
Description.

SingleRAN
Parameter Description 9 Operation and Maintenance Reliability
9 Operation and Maintenance Reliability
9.1 Overview
The Operation & Maintenance System One-Key Recovery feature reduces the complexity of
the backup and recovery of the OS and the complexity of OMU data configuration. In
addition, this feature minimizes the duration of service disruption caused by the operation &
maintenance operations. This feature is applicable only to the DOPRA Linux OS and mainly
used in the following scenarios:
l The DOPRA Linux OS on the OMU board is corrupted.

l OMU applications are corrupted.
l (Only for the BSC6900) The OS on the OMU board is switched from non-DOPRA
Linux to DOPRA Linux.
9.2 Technical Description

This section describes how to implement the Operation & Maintenance System One-Key
Recovery feature.
Scheme 1
The USB creator is used to create the USB disk for installing the DOPRA Linux OS and the
OMU applications. The USB installation disk is plugged into the USB port on the OMU
board. The OMU board is then reset. Five to ten minutes later, the OS or OMU applications
on the OMU board are recovered.
Note that the OS, OMU applications, and the respective configuration information must be
stored onto the USB installation disk during the creation of the USB installation disk. Then,
Bootstrap scripts are generated on the USB installation disk to facilitate the start-up of the
OMU board through the USB installation disk.
The Bootstrap scripts first install the DOPRA Linux OS and configure the information for the
OS. Then, the Bootstrap scripts install the OMU applications and configure the information
for the OMU applications. Figure 9-1 shows the OMU board software recovery process.

SingleRAN
Figure 9-1 OMU board software recovery process
When the OS on the existing OMU boards is switched from non-DOPRA Linux to DOPRA
Linux, the USB creator is used to obtain the configuration information, especially the network
configuration information, the OMU applications configuration information, and the NE
confirmation information, of the OMU board whose OS is to be switched. Based on the
information obtained, the USB creator creates a USB installation disk for installing the
DOPRA Linux OS. The USB installation disk is plugged into the USB port on the OMU
board. The OMU board is then reset. Five to ten minutes later, the switchover of the OS is
complete.

SingleRAN
Scheme 2
When OMU hardware is not damaged, the files are backed up through the existing OS on the
OMU board. In this way, users can recover the OMU OS without using an external storage
medium.
Before recovering the OMU OS, connect a keyboard and a monitor to the OMU board and
then reset the OMU board. When the system boot menu is displayed, select the system
recovery option using the keyboard. The OMU board starts to install the DOPRA Linux OS
automatically. Five to ten minutes later, the OS on the OMU board is recovered. Figure 9-2
shows the OS recovery process for the OMU board.
Figure 9-2 OS recovery process for the OMU board
If no keystroke is detected after the boot menu is displayed, the OMU board boots the default
OS and does not perform OS recovery.

SingleRAN
The Operation & Maintenance System One-Key Recovery feature is activated by default for
the newly delivered OMUs, and the OS backup and the system recovery program are preset.
For the existing OMUs, this feature can be activated through an OS switchover or upgrade.

SingleRAN
Parameter Description 10 Hardware Reliability
10 Hardware Reliability
BSC or RNC board redundancy has two types: board backup and resource pool. Table 10-1
and Table 10-2 describe the BSC6910 and BSC6900 board redundancy, respectively.
NOTE
The BSC or RNC interface boards have an effective mechanism for fault detection and automatic
recovery. When the BSC or RNC detects that a certain proportion of resources of an interface board are
unavailable for a specified period of time, the BSC or RNC resets the interface board. If the faulty board
is the active one in a pair of active and standby boards, the BSC or RNC switches over the active and
standby boards. For example:
l The BSC or RNC resets an Iub interface board if a certain proportion of cells under the Iub interface
board are unavailable for a specified period of time because of a failure in Iub transmission links.
l The BSC or RNC resets an Iub interface board under the following conditions: The RRC connection
setup success rate in a cell is lower than a predefined threshold because of a failure in Iub
transmission links, the proportion of such cells under the Iub interface board reaches a predefined
cell threshold, the proportion of NodeBs having such cells reaches a predefined NodeB threshold,
and this situation persists for a specified period of time.
l If the BSC or RNC detects any transmission fault, the BSC or RNC reports an alarm instead of
resetting the interface board.
Table 10-1 BSC6910 board redundancy

Board Redundancy Type Remarks
Supported
AOUc/UOIc/POUc Board backup Two boards of the same type are

configured in adjacent active and
EXOUa/FG2c/GOUc/ Board backup standby slots.
FG2d/GOUd
SCUb/SCUc Board backup
GCUa/GCUb/GCGa/ Board backup

GCGb
EOMUa Board backup

SingleRAN

Supported
EGPUa/EGPUb/ Resource pool and board An EGPUa or EGPUb board

EXPUa/EXPUb backup provides the following logical
functions: RMP for resource
management, UCUP for UMTS
service processing, and GCUP for
GSM service processing. An
EGPUb also provides the following
logical functions: service awareness
and PS service quality
measurement. An EXPUa or
EXPUb board provides the function
of GCUP for GSM service
processing. The redundancy mode
of a board varies depending on its
logical type.
DPUf Resource pool N/A
ENIUa Resource pool N/A
Table 10-2 BSC6900 board redundancy

Supported
AEUa Board backup Two boards of the same type are

configured in adjacent active and
EIUa/EIUb Board backup standby slots.
OIUa/OIUb Board backup
PEUa/PEUc Board backup
SCUa/SCUb Board backup
TNUa/TNUb Board backup
AOUa/AOUc Board backup
FG2a/FG2c/FG2d Board backup
GCUa/GCUb/GCGa/ Board backup

GCGb
GOUa/GOUc/GOUd Board backup
OMUa/OMUb/OMUc Board backup
POUa/POUc Board backup
UOIa/UOIc Board backup

SingleRAN

Supported
XPUa/XPUb/SPUa/ Board backup

SPUb
DPUa/DPUb/DPUc/ Resource pool N/A

DPUd/DPUe/DPUf/
DPUg
NIUa Resource pool N/A

SingleRAN
Parameter Description 11 Related Features
11 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Parameter Description 12 Network Impact
12 Network Impact
System Capacity
None
Network Performance
None

SingleRAN
Parameter Description 13 Engineering Guidelines
13 Engineering Guidelines
13.1 When to Use Operation & Maintenance System One-

Key Recovery
When the OS of the OMU board malfunctions, use this feature to recover the OS without
using an external storage medium, such as a USB disk or CD-ROM.
13.2 Deployment
13.2.1 Process
l New sites
The feature has been activated for the delivered OMU boards by default.
l Existing sites
Install the latest DOPRA Linux OS using the USB installation disk, or upgrade the
DOPRA Linux OS to the latest version using the controller upgrade tool.
13.2.2 Requirements
l New sites
N/A
l Existing sites
If the USB installation disk is used to install the DOPRA Linux OS, a USB disk
with a capacity of 2 GB or higher must be ready.
If the controller upgrade tool is used to upgrade the DOPRA Linux OS, the
controller must run on the DOPRA Linux OS.
13.2.3 Activation
l Using the USB installation disk to install the latest DOPRA Linux OS
Prepare the USB installation disk for switching the OMU OS from non-DOPRA Linux
to DOPRA Linux. Next, use the USB installation disk to install DOPRA Linux. For

SingleRAN
Parameter Description 13 Engineering Guidelines
detailed operations, see Operation Guide to Switching OMU Operating System Through
USB Disks.
l Upgrading the DOPRA Linux OS to the latest version using the controller upgrade tool
Confirm the controller software version required by DOPRA Linux. For details, see
Guide to Dopra Linux Operating System Remote Patch Upgrade.
Upgrade the controller software version by referring to the controller upgrade
guide.
Upgrade the DOPRA Linux OS. For details, see Guide to Dopra Linux Operating
System Remote Patch Upgrade.
13.2.4 Activation Observation

N/A
13.2.5 Deactivation
N/A
13.3 Performance Monitoring

N/A
13.4 Troubleshooting
N/A

SingleRAN
Parameter Description 14 Parameters
14 Parameters
There are no specific parameters associated with this feature.

SingleRAN
Parameter Description 15 Counters
15 Counters
Table 15-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
67194469 VS.SDH.SWAP. T7041:Number BSC6900 MRFD-210101 System

REASON.REQ of SDH Port Redundancy
UEST.COUNT Switchovers on
S Conditional
Requests

REASON.REQ of SDH Port Redundancy
UEST.COUNT Switchovers on
S Conditional
Requests

REASON.KBY of SDH Port Redundancy
TE.COUNTS Switchovers on
K byte Requests

REASON.KBY of SDH Port Redundancy
TE.COUNTS Switchovers on
K byte Requests

REASON.EXT of SDH Port Redundancy
ERNAL.COUN Switchovers on
TS external
Requests

REASON.EXT of SDH Port Redundancy
ERNAL.COUN Switchovers on
TS external
Requests

SingleRAN

Name Description
67194472 VS.SDH.FAUL T7044:Number BSC6900 MRFD-210101 System

T.CHANNEL.P of SDH Redundancy
ROTECT.COU Protection
NTS Channel
Failures

T.CHANNEL.P of SDH Redundancy
ROTECT.COU Protection
NTS Channel
Failures

T.CHANNEL. of SDH Redundancy
WORK.COUN Working
TS Channel
Failures

T.CHANNEL. of SDH Redundancy
WORK.COUN Working
TS Channel
Failures
73436939 VS.Frame.Flux. HR9732a:Peak BSC6900 MRFD-210104 BSC/RNC

Peak.TxRate Inter-Subrack Resource
Transmitting Sharing
Traffic
73436939 VS.Frame.Flux. HR9732a:Peak BSC6910 MRFD-210104 BSC/RNC

Peak.TxRate Inter-Subrack Resource
Transmitting Sharing
Traffic
73436941 VS.Frame.Flux. AR9732a:Avera BSC6900 MRFD-210104 BSC/RNC

Mean.TxRate ge Inter- Resource
Subrack Sharing
Transmitting
Traffic
73436941 VS.Frame.Flux. AR9732a:Avera BSC6910 MRFD-210104 BSC/RNC

Mean.TxRate ge Inter- Resource
Subrack Sharing
Transmitting
Traffic
73441493 VS.Frame.Flux. R9732a:Numbe BSC6900 MRFD-210104 BSC/RNC

DropPackets r of Discarded Resource
Inter-Subrack Sharing
Packets

SingleRAN

Name Description
73441493 VS.Frame.Flux. R9732a:Numbe BSC6910 MRFD-210104 BSC/RNC

DropPackets r of Discarded Resource
Inter-Subrack Sharing
Packets
73441494 VS.Frame.Flux. R9732b:Numbe BSC6900 MRFD-210104 BSC/RNC

TxPackets r of Sent Inter- Resource
Subrack Packets Sharing
73441494 VS.Frame.Flux. R9732b:Numbe BSC6910 MRFD-210104 BSC/RNC

TxPackets r of Sent Inter- Resource
Subrack Packets Sharing

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

SingleRAN
Parameter Description 17 Reference Documents
17 Reference Documents
1. Operation and Maintenance Feature Parameter Description for GSM BSS or WCDMA
RAN
2. Controller Resource Sharing Feature Parameter Description for WCDMA RAN
3. Flow Control Feature Parameter Description for GSM BSS or WCDMA RAN
4. RNC in Pool Feature Parameter Description for WCDMA RAN
5. RNC Node Redundancy Feature Parameter Description for WCDMA RAN
6. BSC Node Redundancy Feature Parameter Description for GSM BSS
7. MSC Pool Feature Parameter Description for GSM BSS
8. SGSN Pool Feature Parameter Description for GSM BSS
9. TC Pool Feature Parameter Description for GSM BSS
10. Call Admission Control Feature Parameter Description for WCDMA RAN
11. Load Control Feature Parameter Description for WCDMA RAN
12. Overload Control Feature Parameter Description for WCDMA RAN
13. E2E Flow Control Feature Parameter Description for WCDMA RAN
14. Fault Management Feature Parameter Description for SingleRAN


Base Station Controller Equipment Reliability (SRAN11.1 - 01) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Base Station Controller Equipment Reliability (SRAN11.1 - 01) PDF

Uploaded by

Copyright:

Available Formats

SingleRAN

Base Station Controller Equipment

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-02-29) Huawei Proprietary and Confidential i

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

Issue 01 (2016-02-29) Huawei Proprietary and Confidential ii

Issue 01 (2016-02-29) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

SRAN11.1 Draft A (2015-12-30)

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 1

Change Change Description Parameter Change

Feature Added the descriptions of the board redundancy None

Editorial None None

1.4 Differences Between Base Station Types

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 2

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 3

Planned BSC/RNC GSM and MRFD-210401 For details about

Redundancy RNC UMTS None For details, see 5.2

BSC GSM None For details, see 5.3

BSC/RNC GSM and MRFD-210104 For details about

Network RNC in UMTS l WRFD-150211 For details about

RNC Node UMTS WRFD-040202 For details about

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 4

Reliability Feature/ Radio Feature ID/ Remarks

BSC Node GSM GBFD-113725 For details about

MSC Pool GSM GBFD-117401 For details about

SGSN Pool GSM GBFD-119701 For details about

TC Pool GSM GBFD-113726 TC For details about

Fault Fault GSM and MRFD-210304 For details about

Flow control RNC Flow UMTS WRFD-040100 For details about

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 5

Reliability Feature/ Radio Feature ID/ Remarks

BSC Flow GSM l GBFD-111705 For details about

Operation Operation GSM and GBFD-111214 For details, see 9

Hardware BSC/RNC GSM and None For details, see 10

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 6

Table 3-1 Reliability specifications

System availability > 99.999%

Mean time between failures (MTBF) 525000 hours

Mean time to repair (MTTR) 1 hour

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 7

4 Planned Service Interruption

4.2 BSC/RNC Software Management

l Querying the software version and its status

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 8

Figure 4-1 BSC/RNC remote upgrade process

The remote upgrade process is as follows:

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 9

Table 4-1 Key specifications for BSC/RNC software management

Service interruption duration caused by an Service interruption duration 3 min

Service interruption duration caused by a No service interruption for a hot patch

Reloading time 7 min

Time from power-on to management 10 min

Time from power-on to first NodeB 10 min

Time from power-on to the recovery of all 12 min

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 10

Issue 01 (2016-02-29) Huawei Proprietary and Confidential 11

5.2 RNC Redundancy Design