Base Station Controller Equipment Reliability(SRAN9.0_Draft a)

SingleRANBase Station Controller Equipment Reliability Feature Parameter Description Issue Draft A Date 2014-01-20 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2014. 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: [email protected] Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. i 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 2 Overview.........................................................................................................................................2 2.1 Introduction....................................................................................................................................................................2 2.2 Benefits...........................................................................................................................................................................2 2.3 Architecture....................................................................................................................................................................2 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.....................................................................................................................................16 5.3.2 Control Plane.............................................................................................................................................................16 5.3.3 User Plane..................................................................................................................................................................18 5.3.4 Transport Plane..........................................................................................................................................................19 5.4 NewNode......................................................................................................................................................................20 6 Network Redundancy.................................................................................................................22 6.1 RNC in Pool..................................................................................................................................................................22 6.1.1 Overview...................................................................................................................................................................22 6.1.2 Benefits......................................................................................................................................................................23 6.2 RNC Node Redundancy...............................................................................................................................................24 Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. ii ..............47 11 Related Features...........50 13 Engineering Guidelines..........................................................................38 8......................................................................................1........................................................................46 10..........................................................................................................................................................................2......36 8...................................3................................................................................................................................................................2 NE Fault Management.........................................................................................................................49 12 Network Impact............................2 Deployment........................................................................................41 10 Hardware Reliability..........................................................................................................................................................2 Technical Description.........3.................................................SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description Contents 6...................................................................2 EML...................................1 When to Use Operation & Maintenance System One-Key Recovery..................52 13..............................51 13....32 8 Flow Control....................................................................................................3 NML..............................................2 BSC Flow Control...............................................................................................................................................................................................................................................................................................2...................................................................................................................................................3 E2E Flow Control............................................................................................30 7....................................................................................................................2 Benefits..1..........................................................................................3 BSC Node Redundancy..........................................................36 8....................................................................................................................................................................................................................................................................................2 Panorama.............................................1 Overview............5 SGSN Pool......................................................................................................................................................................3 Performance Monitoring..............29 6......................................................................................................................................52 13..............................................................51 13...................................................................................................................................................................................................51 13.............................................................................................. iii .................................................................................41 9...........................1 RNC Flow Control..........................................................................4 Troubleshooting..............................39 8.4 Activation Observation.............................5 Deactivation.................................................................................1 Overview......2.....................2 Panorama.....................................................26 6.2.....................................................................1 Fault Management Architecture.................1 Overview...........................39 8......................................1.........2 Requirements.1 BSC6910 Board Redundancy.............45 10..........................................................................................................................................................................................................................................................................................................................................1.....1.............................................. Ltd.....1..........................................3 Activation.................................51 13......................................................................................................1....................1 BSC/RNC Board Redundancy....................30 7..............................................................................................................27 6................1 NEL...51 13..............................................................................................................................52 Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co...................................................................................................................................................................................................................41 9.............39 9 Operation and Maintenance Reliability.....36 8................................2.........................................28 6......................................................................30 7....................1.........32 7...................................................26 6..4 MSC Pool......6 TC Pool...........................................................52 13.......................................................36 8.............................................2 BSC6900 Board Redundancy.......................................................................................................................1 Process........31 7...............2...................................46 10........................51 13.................................................................................................................................1 Overview.........29 7 Fault Management.........................................2.................................................................................................................... .......................................................................................54 16 Glossary.....................................................................................53 15 Counters................................... iv ....SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description Contents 14 Parameters...................................................................................................58 Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co....................................................................... Ltd......................57 17 Reference Documents................................................................................................................ Ltd. related features.2 Intended Audience This document is intended for personnel who: l Need to understand the features described herein l Work with Huawei products 1. 1 .0..1 Scope This document describes the Base Station Controller Equipment Reliability feature.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 1 1 About This Document About This Document 1. including its technical principles. network impact. 1. and engineering guidelines. There are two types of changes. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 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 Draft A (2014-01-20) This is a new document for SRAN9.3 Change History This section provides information about the changes in different document versions. operation and maintenance reliability. which include redundancy design and hardware reliability design. thereby improving system reliability.1 Introduction Reliability designs enable the controller to continue providing services even when it experiences a fault. 2. network redundancy.2 Benefits Reliability designs. redundancy design. fault management.3 Architecture Table 1 lists the controller equipment reliability-related features and functions that are supported by GSM and UMTS. 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. thereby maintaining high system reliability.. 2 . flow control. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. and hardware reliability. Ltd. planned service interruption. eliminate or reduce the impact of equipment faults on services. 2.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 2 Overview 2 Overview 2. Network redundancy l WRFD-150212 RNC in Pool Node Redundancy l WRFD-150240 RNC in Pool Multiple Logical RNCs Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 2 Overview Table 2-1 Controller equipment reliability-related features and functions that are supported by GSM and UMTS Reliability Category Feature/ Function Radio Access Technology Feature ID/ Feature Name Remarks Planned service interruption BSC/RNC Software Managemen t GSM and UMTS MRFD-210401 BSC/RNC Software Management For details about engineering guidelines. see Controller Resource Sharing Feature Parameter Description in WCDMA RAN documents. BSC/RNC Resource Sharing GSM and UMTS MRFD-210104 BSC/RNC Resource Sharing For details about engineering guidelines. RNC in Pool UMTS l WRFD-150211 RNC in Pool Load Sharing For details about engineering guidelines. BSC Redundancy GSM None For details. see 5.2 RNC Redundancy Design. see Operation and Maintenance Feature Parameter Description. see 5. 3 . Ltd. see RNC in Pool Feature Parameter Description in WCDMA RAN documents.3 BSC Redundancy Design. Redundancy design RNC Redundancy UMTS None For details.. . see MSC Pool Feature Parameter Description in GSM BSS documents. see SGSN Pool Feature Parameter Description in GSM BSS documents. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. BSC Node Redundancy GSM GBFD-113725 BSC Node Redundancy For details about engineering guidelines. see BSC Node Redundancy Feature Parameter Description in GSM BSS documents. 4 . TC Pool GSM GBFD-113726 TC Pool For details about engineering guidelines. Ltd. MSC Pool GSM GBFD-117401 MSC Pool For details about engineering guidelines. SGSN Pool GSM GBFD-119701 SGSN Pool For details about engineering guidelines. see TC Pool Feature Parameter Description in GSM BSS documents. see RNC Node Redundancy Feature Parameter Description in WCDMA RAN documents.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description Reliability Category Issue Draft A (2014-01-20) 2 Overview Feature/ Function Radio Access Technology Feature ID/ Feature Name Remarks RNC Node Redundancy UMTS WRFD-040202 RNC Node Redundancy For details about engineering guidelines. . Ltd.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 2 Overview Reliability Category Feature/ Function Radio Access Technology Feature ID/ Feature Name Remarks Fault management Fault Managemen t GSM and UMTS MRFD-210304 Fault Management For details about engineering guidelines. see 9 Operation and Maintenance Reliability. see Fault Management Feature Parameter Description in SingleRAN documents. For details. Flow control RNC Flow Control UMTS WRFD-040100 Flow Control For details about engineering guidelines. see Flow Control Feature Parameter Description in WCDMA RAN documents. l GBFD-119117 Flow Control on Gb Interface 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 and maintenance reliability Issue Draft A (2014-01-20) Operation and Maintenanc e System One-Key Recovery GSM and UMTS GBFD-111214 Operation & Maintenance System One-Key Recovery Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 5 . BSC Flow Control GSM l GBFD-111705 GSM Flow Control For details about engineering guidelines. see Flow Control Feature Parameter Description in GSM BSS documents. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 2 Overview Reliability Category Feature/ Function Radio Access Technology Feature ID/ Feature Name Remarks Hardware reliability BSC/RNC Board Redundancy GSM and UMTS None For details. Ltd. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. see 10 Hardware Reliability. 6 . Ltd.999% Mean time between failures (MTBF) ≥ 525000 hours Mean time to repair (MTTR) ≤ 1 hour Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 3 3 Reliability Specifications Reliability Specifications Table 3-1 Reliability specifications Index Value System availability > 99.. 7 . Ltd. facilitating the remote management of the controller software and improving the efficiency of software upgrades and downloads. users can implement the following operations on the U2000.. Planned service interruption supports hot patches. With this feature.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. l Querying the software version and its status l Uploading. The controller performs the software integrity check after software loading and before software operation. and improve equipment availability. patches. and then completes digital signature verification. and logs using the Web LMT. 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. 8 . The controller supports the software integrity check.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 4 4 Planned Service Interruption Planned Service Interruption 4. 4. licenses. see Operation and Maintenance Feature Parameter Description. and activating the program files. users can manage the programs. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Huawei controllers support the uniform software management of GSM base station system (GBSS) and radio access network (RAN). For details.2 BSC/RNC Software Management Overview This section describes the MRFD-210401 BSC/RNC Software Management feature. Figure 4-1 shows the BSC/RNC remote upgrade process. which consists of the upgrade client and the upgrade server. downloading. The BSC/RNC is upgraded remotely by the dedicated upgrade tool. patch files. and upgrades the program and data files in the standby workspace of the active OMU and standby OMU. only this type of FAM boards are reset and the boards automatically load the program and data files from their flash memories to complete the upgrade. After the workspace switchover is complete for the standby OMU. When the platform host program. When a cold patch is loaded to a type of FAM boards. Step 4 After the synchronization is successful. switch over the active and standby workspaces of the standby OMU so that the standby OMU is upgraded to the latest version. the FAM boards are reset. BootROM. OS or data files are upgraded. Hot patches adopt one-click installation. backs up data and files. In addition. the standby OMU automatically synchronizes its data with the active OMU. 9 . switch over the active and standby workspaces of the active OMU so that the active OMU is upgraded to the latest version.. synchronize the upgrade directory of the standby OMU with the specified directory of the active OMU.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 4 Planned Service Interruption 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. operating system (OS). Ltd. BootROM. ----End Key Specifications Table 4-1 lists key specifications for BSC/RNC software management. 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 2 Conduct the pre-upgrade health check. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Step 3 Load the host program. Step 6 After the service verification is successful. Step 5 Switch over the active and standby workspaces of the FAM boards. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 4 Planned Service Interruption Table 4-1 Key specifications for BSC/RNC software management Index Version Implementation Service interruption duration caused by an upgrade for a major release Service interruption duration ≤ 3 min Service interruption duration caused by a patch upgrade No service interruption for a hot patch upgrade Service interruption duration for a cold patch upgrade ≤ 3 min Reloading time ≤ 7 min Time from power-on to management recovery ≤ 10 min Time from power-on to first NodeB recovery ≤ 10 min Time from power-on to the recovery of all sites ≤ 12 min Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 10 .. Ltd. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design 5 Redundancy Design 5. it is switched over to the standby state. Ltd. l Active/standby switchovers In active/standby mode. to ensure the reliable operation of the system. There are two types of switchovers: – Automatic switchover: automatically triggered by the system if the active board is faulty. the previously active board is reset automatically. Maintenance personnel use the immediate switchover command to switch over the active and standby boards. 11 . – Manual switchover: performed by maintenance personnel on the LMT. Huawei base station controllers adopt reliability designs. System redundancy provides reliability designs that improve system reliability. If this board restarts normally.. When the active board is faulty or needs to be replaced.1 Overview This section describes the MRFD-210101 System Redundancy feature and the GBFD-111701 Board Switchover feature. These designs include active/standby switchovers and load sharing. new service requests are allocated to the normal processing units in the resource pool. When the standby board is switched over to the active state. – No major or critical alarm is reported on the standby board. l Other reliability designs Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. A successful active/standby switchover requires the following: – The standby board works normally. such as load sharing and active/standby switchovers. l Load sharing In resource pool mode. When one or multiple processing units are faulty. load sharing is performed among processing units in the pool. services on the active board are switched over to the standby board to ensure normal service operations. the active board processes services while the standby board acts as a backup for the active one. Every active CP process on a UCUP board has a backup on another UCUP board. A pair of Resource Management Processing (RMP) boards perform the central layer functions. the SPU boards. 5. 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. 12 .and user-plane load sharing.2. Processes on the control plane work in active/standby mode. and transport plane resources. Ltd. which work in active/standby mode. including the control plane. process control plane data. In addition. the UCUP boards process control plane data. For the BSC6910.2 RNC Redundancy Design 5. l The central layer manages global resources. 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. 5..2. as shown in Figure 5-1. The MPU subsystems manage transmission resources and enable control. The BSC6910 resource management plane consists of the central layer and local layer. user plane.2 Control plane For the BSC6900. A UCUP board performs the local layer functions.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design Other reliability designs include the redundancy configuration of power and fan units. A sudden increase in the CPU usage is allowed within a short period of time. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.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. This is because only global resource scheduling is interrupted if an RMP board is faulty. l The local layer manages board-level resources. l A temporary fault in an RMP board does not interrupt ongoing services. and troubleshoots system faults. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design Figure 5-1 Control-plane redundancy design for the BSC6910 NOTE CP stands for the control plane and UP stands for the user plane. All active CP processes on a UCUP board have backups evenly distributed on the two adjacent UCUP boards. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the cell status. Ltd. thereby restoring services promptly. The differences are as follows: l A pair of BSC6900 active and standby control plane boards must be installed in adjacent slots. the BSC6910 control plane also supports process preemption. l The BSC6910 control plane uses the process backup mechanism. The redundancy design is similar for the BSC6900 and BSC6910 control planes. If the active subsystem is faulty. 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 standby subsystem takes over services on the active subsystem to avoid service interruptions.. The standby subsystem then backs up the data. and online UE information on the active subsystem are sent to the standby subsystem through the backup channel. NodeB status. In addition to the redundancy design. the BSC6910 preempts another standby CP process to start the active CP process. 13 . When the BSC6900 or BSC6910 is running. and PS services are interrupted and then reconnected. The redundancy design is the same for the BSC6900 and BSC6910 user planes. but the other functional user plane subsystems still work in resource pool mode. the UCUP board processes user plane data. The DSPs work in resource pool mode. CS services are released. Figure 5-2 User-plane redundancy design for the BSC6910 If a user plane subsystem is faulty. For the BSC6910. the system performs an active/standby switchover to reestablish the transmission links for the ongoing services on the standby board.4 Transport Plane The redundancy design is the same for the BSC6900 and BSC6910 transport planes. the system performs an active/ standby switchover to enable the ongoing services to be transmitted through the standby channel. port backup/load sharing. l Port backup or load sharing l Resource pool Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2. They both support board redundancy. the digital signal processors (DSPs) in DPU boards process user plane data. and resource pool mode. Neither supports user-plane service backup. the common channels for the cells carried on the subsystem are reestablished. During the service interruption. Ltd. The user-plane processing capability decreases.. When detecting that the active channel is unavailable.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design 5. as shown in Figure 5-2. A transport interface board supports the following: l 1+1 active/standby redundancy When detecting that an interface board is faulty.3 User Plane For the BSC6900. and services are interrupted for less than 5 seconds and then restored.2. 5. 14 . The user plane resources work in resource pool mode. the resource management plane. For example. and transport plane all support the redundancy design. Table 5-1 Reliability indexes for transmission interface boards in different scenarios Scenario Availability Average Downtime (Minute/Year) Quantitative Reliability Analysis 1+1 active/standby redundancy 0. control plane.09 High task reliability and high basic reliability under the same traffic volume Table 5-2 Key specifications of transmission redundancy Index Version Implementation Switchover for interface boards The impact persists within 3s for stable services. if Link Aggregation Control Protocol (LACP) is enabled. Therefore.999999918 0. user plane.3 BSC Redundancy Design Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.04 High task reliability and low basic reliability under the same traffic volume Independent board plus resource pool 0.999999836 0. NOTE The delay caused by protocol negotiation with the peer equipment is not considered in the preceding indexes. 15 .999999183 0.11 Low task reliability and low basic reliability under the same traffic volume 1+1 active/standby redundancy plus resource pool 0. Ltd. Switchover for other boards New services can be admitted in 15s.43 Low task reliability and high basic reliability under the same traffic volume N+1 resource pool 0. the BSC6900 and BSC6910 do not experience a single point of failure.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design In conclusion. 5. Table 5-1 describes the reliability indexes for transmission interface boards in different scenarios.999999796 0. the impact persists within 9s for stable services in a switchover for interface boards.. 5. as shown in Figure 5-3.3.2 Control Plane For the BSC6900. The BSC6900 is configured with a pair of EGPUa boards whose logical type is resource management processing (RMP). GCUP or GMCP is short for GSM BSC Control plane and User plane Processing. Processes on the control plane work in active/standby mode. EGPUa 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. NOTE EGPUa boards whose logical type is GCUP or GMCP (referred to as GCUP or GMCP boards) manage board-level resources. the XPU boards.3.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design 5. The BSC6910 resource management plane consists of the central layer and local layer. The EGPUa boards are responsible for managing global resources and troubleshooting system faults. Every active CP process on an EGPUa board whose logical type is GCUP or GMCP has a backup on another EGPUa board whose logical type is GCUP or GMCP. l The local layer manages board-level resources. l The central layer manages global resources. 16 . user plane. This is because only global resource scheduling is interrupted if an RMP board is faulty.1 Resource Management Plane The BSC6900 MPU subsystems can be configured on multiple pairs of XPU boards working in active/standby mode. which work in active/standby mode.. For the BSC6910. and troubleshoots system faults. Ltd. process control plane data. l A temporary fault in an RMP board does not interrupt ongoing services. and transport plane resources. the EGPUa boards whose logical type is GCUP or GMCP process control plane data. including the control plane. A sudden increase in the CPU usage is allowed within a short period of time. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The MPU subsystems manage transmission resources and enable controland user-plane load sharing. 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. the standby subsystem takes over services on the active subsystem to avoid service interruptions.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design Figure 5-3 Control-plane redundancy design for the BSC6910 NOTE CP stands for the control plane and UP stands for the user plane. l The BSC6910 control plane uses the process backup mechanism. the cell status.. When the BSC6900 or BSC6910 is running. All active CP processes on an EGPUa board whose logical type is GCUP or GMCP have backups evenly distributed on the two adjacent EGPUa boards whose logical type is GCUP or GMCP. If the active subsystem is faulty. In addition to the redundancy design. and online MS information on the active subsystem are sent to the standby subsystem through the backup channel. the BSC6910 control plane also supports process preemption. The standby subsystem then backs up the data. 17 . If a pair of active and standby CP processes of the BSC6910 are both faulty for a Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. BTS status. Ltd. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Figure 5-4 User-plane redundancy design for the BSC6910 NOTE CP stands for the control plane and UP stands for the user plane. as shown in Figure 5-4. thereby restoring services promptly.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design certain period of time (less than 5 minutes). and PS services are interrupted and then reconnected. The redundancy design is the same for the BSC6900 and BSC6910 user planes. the digital signal processors (DSPs) in DPU boards process user plane data. Neither supports user-plane service backup.3. Ltd. the EGPUa boards whose logical type is GCUP or GMCP process user plane data. 18 .. CS services are released. For the BSC6910. the BSC6910 preempts another standby CP process to start the active CP process. The user plane resources work in resource pool mode.3 User Plane For the BSC6900. but the other functional user plane subsystems still work in resource pool mode. The user-plane processing capability decreases. 5. If a user plane subsystem is faulty. The DSPs work in resource pool mode. . the system performs an active/ standby switchover to enable the ongoing services to be transmitted through the standby channel. the BSC6900 and BSC6910 do not experience a single point of failure.999999918 0.3. Table 5-3 describes the reliability indexes for transmission interface boards in different scenarios. Ltd. Therefore. 19 . A transport interface board supports the following: l 1+1 active/standby redundancy When detecting that an interface board is faulty.43 Low task reliability and high basic reliability under the same traffic volume N+1 resource pool 0. and transport plane all support the redundancy design. and resource pool mode.999999183 0.999999796 0.09 High task reliability and high basic reliability under the same traffic volume Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Port backup or load sharing l Resource pool In conclusion.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design 5.4 Transport Plane The redundancy design is the same for the BSC6900 and BSC6910 transport planes. the system performs an active/standby switchover to reestablish the transmission links for the ongoing services on the standby board.04 High task reliability and low basic reliability under the same traffic volume Independent board plus resource pool 0. port backup/load sharing.999999836 0. When detecting that the active channel is unavailable. They both support board redundancy. Table 5-3 Reliability indexes for transmission interface boards in different scenarios Scenario Availability Average Downtime (Minute/Year) Quantitative Reliability Analysis 1+1 active/standby redundancy 0. user plane. the resource management plane. control plane.11 Low task reliability and low basic reliability under the same traffic volume 1+1 active/standby redundancy plus resource pool 0. l BSC6910 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. see the RNC User Plane and Control Plane Resource Sharing Parameter Description. When EGPUa boards experience a load imbalance because there are hotspot base stations or cells. slot.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design Table 5-4 Key specifications of transmission redundancy Index Version Implementation Switchover for interface boards The impact persists within 3s for stable services. the BSC6910 adjusts the distribution of base stations or cells on the EGPUa boards to achieve load balancing. new services are forwarded to other userplane processing units with light load. The BSC6910 introduces a new service processing board: GPU. The GPU board can simultaneously process user-plane and control-plane data. For details. For details on load sharing. l BSC6900 control plane resource sharing Control plane resource sharing is used to share the CPU usage and memory. For details about the engineering guidelines. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. If a certain user-plane processing unit is overloaded. When the CPU usage of a certain control-plane processing unit is too high or the memory of a certain controlplane processing unit is insufficient. if Link Aggregation Control Protocol (LACP) is enabled. For example. new calls are forwarded to other control-plane processing units with light load. see Flow Control Feature Parameter Description. These adjustments improve hardware utilization by balancing the control-plane and user-plane processing capabilities. the BSC6910 monitors the distribution of base stations and cells on the EGPUa boards. 5.4 NewNode This section describes the MRFD-210104 BSC/RNC Resource Sharing feature. telecom operators do not need to specify the subrack. or subsystem.. Switchover for other boards New services can be admitted in 15s. l BSC6900 user plane resource sharing The RNC implements dynamic resource sharing based on the resource pool and load balancing. NOTE The delay caused by protocol negotiation with the peer equipment is not considered in the preceding indexes. The BSC6910 monitors the userplane and control-plane resource usage and adjusts resources (multi-core DSPs) for each plane proportionately. When configuring a base station or cell on the BSC6910. the impact persists within 9s for stable services in a switchover for interface boards. 20 . Ltd. In addition. see Controller Resource Sharing Feature Parameter Description. l Automatic base station and cell allocation in the BSC6910 The BSC6910 automatically allocates a new base station or cell to an EGPUa board. . Operators can schedule the time for base station reallocation. During base station reallocation. For details.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 5 Redundancy Design Dynamic reallocation of cells can be performed during peak hours. and UEs controlled by the base station experience call drops. During cell reallocation. see Controller Resource Sharing Feature Parameter Description. 21 . Ltd. whereas dynamic reallocation of base stations must be performed during off-peak hours. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. UEs in the CELL_DCH state in the cell do not drop from the network. services carried by the base station are interrupted. makes network reconstruction more difficult. which may affect services on the live network and decrease network reliability. When an RNC becomes faulty. Ltd. all NodeBs under it go out of service. This can cause huge losses for operators. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. which requires sustainable network capacity expansion and high reliability of the RNC. 6. interconnected RNCs form a resource pool over Iur-p.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy 6 Network Redundancy 6. RNC splitting.1 RNC in Pool This section describes the RNC in Pool feature. RNC in Pool is an ideal solution for smooth RNC capacity expansion without compromising network reliability. The existing technique for RNC capacity expansion requires an RNC to be split if the RNC cannot accommodate any additional hardware. For details. 22 . a Huawei-proprietary interface.. New technologies need to be introduced in network planning and deployment to ensure network reliability. however. Figure 6-1 shows the network architecture for RNC in Pool.1.1 Overview The rapid development of mobile internet brings fast service growth. see RNC in Pool Feature Parameter Description. With this feature. Ltd. The BSC6900 does not support this feature. l WRFD-150212 RNC in Pool Node Redundancy This feature prevents an RNC failure from causing a massive service interruption. 23 . it can serve as the overflow RNC or backup RNC for three BSC6900s.2 Benefits The benefits of RNC in Pool are as follows: l Load sharing for smooth RNC capacity expansion Load sharing provided by RNC in Pool enables smooth RNC capacity expansion. however. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. For example.Figure 6-2 shows a comparison between capacity expansion using existing techniques and using RNC in Pool.1. can only be enabled when one of the other features or both are also enabled. if a BSC6910 carries three logical RNCs. 6.. l WRFD-150240 RNC in Pool Multiple Logical RNCs This feature allows multiple logical RNCs to be configured on a BSC6910 to implement load sharing or node redundancy. which no longer requires RNC splitting or NodeB reparenting.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy Figure 6-1 Network architecture for RNC in Pool RNC in Pool consists of the following three optional features: l WRFD-150211 RNC in Pool Load Sharing This feature allows load sharing between existing RNCs and another RNC added for capacity expansion. The third feature. You can enable the first or second feature above or both. 6. which increases the hardware resource utilization. l Improved system reliability Node redundancy provided by RNC in Pool allows a backup RNC to take over services of a faulty RNC. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the signaling bursts of an RNC can be processed by idle hardware resources of another RNC in a pool. see RNC Node Redundancy Feature Parameter Description. 24 .2 RNC Node Redundancy This section describes the WRFD-040202 RNC Node Redundancy feature. The redundancy technique enables fast service resumption and improves system reliability. Ltd. For details.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy Figure 6-2 Comparison between capacity expansion using existing techniques and using RNC in Pool l Traffic balancing between RNCs for signaling bursts With load balancing.. the other automatically takes over all the dual-homed NodeBs to protect the NodeBs from being out of service. The RNC is the control center of the RNS. If one RNC fails. where earthquakes occur frequently. each NodeB is configured with two transmission links pointed towards two RNCs. If RNC1 serves as the primary RNC of the NodeBs and fails when an earthquake occurs in area A.. 25 .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy In a traditional WCDMA RAN. Recent technological improvements allow the RNC to provide increasingly higher capacity to meet the rapid growth of mobile services. and transmission redundancy. cells. The RNC controls the radio access services of all the UEs in the RNS coverage area. both RNCs provide services and the equipment can be fully utilized. To achieve high reliability. the NodeB tries to connect to the secondary RNC to resume work. The RNC. water damage. explosion. one NodeB is connected to only one RNC. RNC node redundancy uses 1+1 backup mode. where earthquakes rarely occur. the two RNCs do not work in active/standby mode. Therefore. To increase reliability. interface-board backup. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. All the data related to NodeBs. In this case. Under normal conditions. RNC1 is installed in area A. RNC2 automatically takes over the NodeB control rights. such as control-board backup. or earthquake. When one of the RNCs fails. Huawei provides an RNC node redundancy solution. In normal situations. Assume that RNC1 and RNC2 are grouped into an RNC pool. however. which are the primary RNC and the secondary RNC. the primary RNC serves as the controlling RNC (CRNC) of the NodeB. Figure 6-3 shows the basic principles of 1+1 backup mode. In the RNC node redundancy solution. and the NodeBs resume work. Ltd. resource pool setup for data processing boards. and RNC2 is installed in area B. the RNC uses many redundancy technologies. RNC reliability is a great concern because a failure in the RNC affects the security of the whole RNS. the RNS cannot provide radio access service in the coverage area. Figure 6-3 RNC-supported 1+1 backup mode As shown in Figure 6-3. another RNC automatically takes over all the dual-homed NodeBs under the failed RNC. and their neighboring cells is configured on both the RNCs. When the primary RNC fails. may break down in a disaster such as fire. Figure 6-4 shows the networking diagram of two BSCs working in a redundancy group.3 BSC Node Redundancy This section describes the GBFD-113725 BSC Node Redundancy feature. Ltd.1 Overview In traditional wireless networks. Two BSCs in a redundancy group work in 1+1 backup mode. NOTE This feature applies to the following scenarios: l BSC failure A BSC fails or all the A interface boards are faulty. 6. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. and inter-BSC interfaces all use IP transmission. If a BSC fails or all the signaling links on the A interface are disconnected. In either case. If one BSC fails or all the signaling links on the A interface of one BSC are disconnected. which is a BSClevel redundancy solution. 26 . the BSC cannot provide services and the BTSs served by the BSC cannot access the network. the other BSC takes over the services from the failed BSC. where the A. the BSC cannot process services. Huawei introduces the BSC Node Redundancy feature. see BSC Node Redundancy Feature Parameter Description. each BTS connects to only one BSC.3. To ensure service continuity in the event of the preceding faults. For details. The BSC Node Redundancy feature enables two BSCs to form a redundancy group in all-IP networking mode. Abis..SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy 6. l Failure in signaling links on the A interface All the signaling links on the A interface are disconnected. in a redundancy group.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy Figure 6-4 Networking diagram of two BSCs working in a redundancy group In a redundancy group. set RedundancyMode to an appropriate value. Ltd. 27 . respectively. each BSC considers itself as the local BSC and the other as the peer BSC.2 Benefits This feature provides the following benefits: l More reliable BSCs Two BSCs in a redundancy group work in 1+1 backup mode. 6. GROUPINDEX specifies a redundancy group. To enable or disable this feature on the local and peer BSCs.3. the other BSC immediately takes over services from the failed BSC. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. If one BSC fails. LocalBSCID and PeerBSCID specify the local and peer BSCs.. The MSC Pool feature complies with the 3GPP TS 23. If different pool areas overlap each other. Figure 6-5 Network topology of an MSC pool As shown in Figure 1. LA 3. and location area (LA) 1. The pool area is served by one or more MSCs in parallel. an MS may roam without the need to change the serving MSC. the traffic is evenly distributed to all the MSCs in an MSC pool. and MSC 3. For example. This feature has the following advantages: Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.0. A call made by a roaming MS within the pool area does not trigger an inter-MSC handover. Ltd. Within a pool area. LA 2. For details. the calls in LA 1 can be evenly distributed to MSC 1. The MSC pool area is a service area with one or more radio access network nodes. MSC 2.. With resource and load sharing. MSC 1. If all the signaling links on the A interface of one BSC are disconnected. and LA 4 form an MSC pool area.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description l 6 Network Redundancy More reliable transmission Both BSCs in a redundancy group connect to a core network (CN) over the A interface. one LA can belong to more than one pool area. The traffic from the BSC is evenly distributed to the MSCs in the MSC pool based on Network Resource Identifiers (NRIs) or according to the load sharing principle. An MSC pool consists of a group of MSCs handling the traffic generated from one MSC pool area. A BSC belonging to an MSC pool is connected to each MSC in the MSC pool. 28 . One MSC pool area consists of several LAs. see MSC Pool Feature Parameter Description. 6.4 MSC Pool This section describes the GBFD-117401 MSC Pool feature. MSC 2.236 V6. the other BSC immediately takes over services from the failed BSC. Figure 6-5 shows the network topology of an MSC pool. One BSC is connected to multiple MSCs at the same time. reducing inter-MSC handovers and implementing MSC node redundancy. and MSC 3 form an MSC pool.3. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. For details. and the entire network performance is improved.5 SGSN Pool This section describes the GBFD-119701 SGSN Pool feature. l If an MSC in an MSC pool is faulty or if an MSC is added to or removed from an MSC pool. 6.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 6 Network Redundancy l All the MSCs in an MSC pool implement load balancing and resource sharing. the existing network architecture does not need to be adjusted. all the MSCs in one MSC pool are regarded as one MSC. Ltd. This helps implement MSC node redundancy and improve network reliability. Therefore. see SGSN Pool Feature Parameter Description. inter-MSC handovers and the signaling between the MSCs and the Home Location Registers (HLRs) decrease. see TC Pool Feature Parameter Description. 29 . increasing network capacity and reducing equipment investment. For details. 6.6 TC Pool This section describes the GBFD-113726 TC Pool feature. l Logically. When certain faults need to be rectified with manual operations or using other automation devices.1. such as the environment monitoring device. 30 . The exceptions that cannot be resolved are defined as faults. using Huawei multi-mode base station controller as an example. The NEs mainly include the base station controllers and base stations. Figure 7-1 Fault management on the NEL As shown in Figure 7-1 a controller includes the following devices: l Operation and maintenance unit (OMU) boards Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd. an NE device first filters and judges them based on preset rules. Figure 7-1 shows implementation of fault management on the NEL. alarms are reported. Most of these alarms are generated from main devices of the NEs and peripherals. NE devices can directly rectify faults..1 NEL The NEL is where most alarms are generated.1 Fault Management Architecture 7.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 7 Fault Management 7 Fault Management 7. After detecting exceptions. and filtered. 31 . the Huawei iManager U2000. alarms are received. for example. On certain EMLs. to manage the NEs of the device vendor.1.. devices of multiple vendors can be managed. using Huawei iManager U2000 as an example.2 EML A device vendor generally provides the EML. stored. 7. configures the mapping and correlation for alarms and events. Fault management of the U2000 involves alarm/event setting. Alarms are dispatched through the northbound interface. and alarm/event notification. Figure 7-2 Fault management of the U2000 Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. alarm/event reporting.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description l GE switching network and control unit (SCU) boards l Service processing boards l Monitoring devices 7 Fault Management The OMU collects information about faults detected on the preceding devices. Figure 7-2 shows implementation of fault management on the EML. and post-processes the faults before reporting alarms to the U2000. On the EML. Ltd. and transport network.2 NE Fault Management Fault management provides the following basic functions: l Fault detection After detecting faults. links. a fault detection unit reports the faults to the fault management module. The NMS is generally developed and managed by telecom operators themselves. core network. Only the faults or alarms whose duration exceeds the threshold of the generation delay comply with the transient rule and are reserved for next filtering. such as the radio access network (RAN). Ltd. The devices are deployed on various networks. base stations. the NMS can receive. filter. It collects faults reported by fault detection units and processes in a centralized manner. l Fault collection Fault collection is the most important external interface of fault management. channels. and dispatch work orders for these alarms. Fault detection units can detect faults of all MOs including software and hardware. and fault toggle rule There are two filtering stages: primary filter and secondary filter. such as TRXs. The NMS manages the devices of different vendors and fields on a comprehensive basis. and signaling messages.3 NML In normal cases. so fault 1 or alarm 1 is discarded. and store alarms generated on devices of multiple vendors and fields. With this function. Then. As shown in Figure 7-3.. In the secondary filter.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 7 Fault Management 7.1. telecom operators centrally manage their devices on the network management layer (NML) by using an NMS. alarms to be reported are filtered. cells. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 32 . the duration of fault 1 or alarm 1 is shorter than the delay threshold T. the fault management system reports alarms for these faults to the U2000 or local maintenance terminal (LMT) after processing the faults on each layer. – Transient rule Faults or alarms of short duration can be filtered based on the alarm or fault generation delay. so alarm 2 or an alarm for fault 2 can be reported. boards. 7. Fault management is an important function of the NMS. The duration of fault 2 or alarm 2 is longer than T. ports. fault detection units filter duplicate faults and other faults using the transient rule and toggle rule. l Duplicate fault filtering. fault transient rule. In the primary filter. Faults and events occur in the system and involve system details. l Alarm mapping Alarm mapping is one of the core processes in fault management and aims to isolate fault information from the alarms reported to users. l Alarm box management Alarm box management provides functions. Figure 7-4 Principles of the toggle rule If the number of duplicate faults exceeds a threshold in a period T1.. and automatic fault rectification. which means that the fault does not occur. l Fault troubleshooting Fault troubleshooting involves device status switchover. Base stations and controllers filter faults and automatically rectify them based on preset policies. you only need to locate the units where faults occur and that can be replaced or modified. Rather than obtaining system details. Alarms presented to users are in a uniform format and easy to understand. fault isolation. alarms are reported. If required. and alarms for other duplicate faults are filtered. If the number of duplicate faults is within the threshold in T2. and querying the alarm box version. the preset policies can be modified by adjusting parameters. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Alarm mapping forces faults to map reported alarms. the oscillation ends. When faults fail to be automatically rectified and manual interventions are required. Figure 7-4 shows the principles of the toggle rule.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 7 Fault Management Figure 7-3 Principles of the transient rule – Toggle rule The toggle rule applies to the faults that frequently occur and has oscillation characters. Ltd. Alarms provide fault analysis results and are displayed in a uniform and simple format. resetting the alarm box. After that. 33 . such as specifying the severity of alarms to be reported to the alarm box. the duplicate faults are filtered using the toggle rule. one fault and an alarm for the fault are reserved. You can rectify faults based on alarms. The fault detection units determine oscillation termination conditions once oscillation starts. such as the alarm name. l Alarm correlation Alarm correlation is one of the core processes in fault management. After the severity is changed. humidity. You can define alarms on base stations and controllers for faults related to the status of the environment and devices. l User-defined alarms Base stations and controllers can be connected to external environment monitoring devices to monitor the environment and device status. This prevents redundant work order dispatches. alarms of the specified alarm ID are reported. Ltd. A root fault generally triggers multiple correlative faults. You can also set parameters for these alarms. an alarm severity change message is reported. you can mask specified alarms by alarm ID or object. or digital signal processor (DSP). voltage. the specified alarm will not be reported even if the fault persists. issues a command to the base station to check for alarms that have not been synchronized. such as service-related alarms. Certain critical alarms. – Alarm synchronization between the controller and the U2000. l Supporting common alarms in the SingleRAN solution In a GSM/UMTS dual-mode base station. severity. If alarm correlation is not performed. l Fault log Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. During alarm masking. and network management type. or mask a specified alarm for all objects. all the active alarms of the alarm ID are cleared. In this way. the U2000 can present alarm correlations to maintenance personnel for fast fault location and troubleshooting. l Alarm synchronization between a base station and the U2000 Alarm synchronization between a base station and the U2000 consists of two stages: – Alarm synchronization between the base station and the controller: The controller queries active alarms from the base station. cannot be masked based on alarm correlation even if the critical alarms are generated for correlative faults that include physical device faults or data transmission faults. l Alarm masking With this function. This function filters out non-root faults and presents root faults to users. These alarms carry the serial numbers of their root alarms. In this way. an alarm for only one RAT can be displayed. which affects fault location. respectively.. l Alarm severity change Based on 3GPP specifications. the alarm box provides audible and visual notifications for you to rectify faults in a timely manner. you can dynamically monitor the environment and devices. if two common alarms with the same information are detected and the alarms are for GSM and UMTS. and updates alarm records on the controller based on the check result. 34 . multiple alarms are reported. the severity of an uncleared alarm can be changed. – Masking alarms by alarm ID If Shielded Flag of a specified alarm ID is set to Shielded. If the fault is not rectified after alarm masking is disabled. theft. The RAT displayed in the alarm varies according to the multi-RAT priority settings. – Masking alarms by object You can mask a specified alarm or all alarms for a certain board. port. such as the temperature. and smoke.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 7 Fault Management After you specify concerned alarms to be reported to an alarm box. Central fault logs record the information about all faults. 35 .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 7 Fault Management Fault logs are classified into local fault logs and central fault logs. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. based on which you can obtain all the fault information about an NE.. Local fault logs record faults on faulty boards and are stored in a nonvolatile storage device. Ltd. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 8 Flow Control 8 Flow Control 8. including CPU resources and memory l Air interface resources. 8. which may lead to messages being randomly discarded and NE resetting. thereby maintaining system stability. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Resources in a WCDMA system are limited. Huawei RNCs perform flow control at four points in the system. As a result. as well as response failures.1. Flow control provides protection in the following ways: l It restricts incoming traffic to: – Protect equipment from overload.1. and power l Transmission resources l Core network processing capabilities To keep system stability and capabilities at the maximum possible level. l It restricts outgoing traffic to reduce the load on the peer equipment. the traffic volume may exceed the processing capability of the system. Ltd.2 Panorama During mass gathering events.1 Overview Flow control is a protective measure for communications between the RNC and its peer equipment. including channels. call drops. the system becomes overloaded.. The resources concerned here are: l Equipment system resources. – Ensure that equipment can properly process services even under heavy traffic. 36 . and other unexpected events.1 RNC Flow Control 8. so how they are used affects system performance. which are numbered inFigure 8-1. service access failures. codes. keeps a high cell update success rate. – When the forward access channel (FACH) is congested. For details about load reshuffling and overload control. and overload control on code and power resources. Then. l To address problems caused by limited RNC resources (labeled 1 in Figure 8-1). load reshuffling. and rejecting access requests for low-priority services. The RNC performs admission control. l To address problems caused by limited air interface resources (labeled 2 in Figure 8-1). see Load Control Feature Parameter Description and Overload Control Feature Parameter Description. see Call Admission Control Feature Parameter Description. 37 . and triggers state transitions such as CELL_PCH to CELL_DCH (P2D) and CELL_DCH to idle (D2Idle). the RNC allows CS-domain paging messages to preempt PS-domain paging messages in order to raise the paging success rate in the CS domain. Ltd. the RNC works with the core network to perform flow control over the Iu interface. the RNC performs other flow control functions to ensure system stability and reliability. For details about admission control.. the RNC performs flow control for RNC units. PCH congestion control. such as recording logs and printing to reduce the system load. the RNC starts basic flow control functions that suspend non-critical functions. based on the system load and the switch status of flow control functions. The software of each RNC board monitors the system resource usage. Based on link congestion conditions detected at the local end and congestion Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. This gives priority to access requests for high-priority services such as CS services. This processing is implemented by CAPS control.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 8 Flow Control Figure 8-1 Four points in flow control Flow control involves discarding originating messages (such as RRC connection requests) that overload the system when system resources are insufficient. and FACH congestion control. – When the paging channel is congested. the RNC restricts message retransmissions on the logical channels. and reduces call drops. – When the cell is overloaded with services. l To address problems caused by limited signaling bandwidth over the Iu interface (labeled 3 in Figure 8-1). refusing to process low-priority services. the RNC performs call attempt per second (CAPS) control. rejects certain PS service requests. the RNC limits the number of RRC connection requests admitted to a cell each second. When necessary. see Controller Resource Sharing Feature Parameter Description. NOTE The BSC6910 inherits the flow control function from the BSC6900. the RNC will not know. the RNC performs flow control on initial direct transfer messages to reduce the signaling traffic over the Iu interface. which lower the cell resource utilization. For example. balances the load among subracks and boards. and improves RNC service processing efficiency. In E2E Flow Control Phase 2.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 8 Flow Control indications reported from the peer end. For details about other flow control measures. if the RNC provides service priority information for the NodeB. The only difference is in the RNC units that flow control works on. To address these issues. or when the cell power is congested. 8. the access of high-priority services cannot be guaranteed because the NodeB is unaware of the service priority of each message. Specifically. 38 . This prevents severe congestion on the signaling link between the RNC and the core network and also reduces the load on the core network when it is overloaded. l Better flow control effects can be achieved because of cooperation between NEs. the RNC restricts the data transmission rates when there is transmission congestion over the Iub interface. For RRC connection requests.. This prevents packet loss and makes more efficient use of the bandwidth. the RNC continues to admit a large number of RRC CONNECTION REQUEST messages and send RADIO LINK SETUP REQUEST messages to the NodeB over the Iub interface even when the NodeB is congested or overloaded. the NodeB can implement differentiated flow control based on service priorities to preferentially ensure the access of high-priority services. Compared with flow control performed on a single NE. This achieves dynamic resource sharing. The NEs that participate in flow control are the RNC and NodeB. For details. when the CPU of the baseband board or WMPT is congested or overloaded.1. the following descriptions apply to both the BSC6900 and BSC6910. the RNC supports control-plane load sharing and user-plane load sharing. Ltd. Huawei has introduced the following E2E flow control functions: l E2E flow control based on NodeB CPU load – E2E flow control phase 1 – E2E flow control phase 2 l E2E flow control based on power congestion E2E Flow Control limits the traffic flow that enters NEs and therefore ensures the stable operation of NEs when these NEs are overloaded. Therefore. Without E2E flow control. the RNC supports user-plane congestion control over the Iub interface.3 E2E Flow Control E2E Flow Control protects NEs in a RAN from being overloaded. E2E Flow Control has the following benefits: l More reference information is provided for flow control because of cooperation between NEs. see Flow Control Feature Parameter Description. Unless otherwise stated. the RNC performs flow control on RRC CONNECTION REQUEST Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l To address problems caused by limited transmission resources over the Iub interface (labeled 4 in Figure 8-1). In this case. such as flow control for overloaded RNC units. In addition. the NodeB should reject or discard these RADIO LINK SETUP REQUEST messages. the BSS can process services properly.. the traffic volume surges and sometimes exceeds the planned capacity. For details on the related features. Huawei applies flow control at the six points marked in Figure 8-2. Flow control enables Huawei BSS to discard certain messages. Figure 8-2 Flow control points numbered 1 through 6 The flow control points are described as follows: Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2 BSC Flow Control 8. system performance may deteriorate noticeably and the system may even destabilize. see Flow Control Feature Parameter Description 8. leading to BSS overload. see E2E Flow Control Feature Parameter Description. For details about the engineering guidelines. However.2 Panorama During base station subsystem (BSS) construction.2. and the NodeB performs flow control on RADIO LINK SETUP REQUEST messages. flow control based on user priority.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 8 Flow Control messages. When the traffic volume is lower than or equal to the planned capacity. interface signaling flow control. increasing resources available to admitted UEs and RAN resource utilization. and load sharing. This action reduces the NodeB Application Part (NBAP) signaling traffic on the Iub interface. and to reject low-priority services if system resources are insufficient. Flow control includes BSC flow control. if the NodeB is overloaded.1 Overview This section briefly describes how BSC flow control works. the system capacity is planned according to the estimated traffic volume in the coverage areas. such as random access requests. 39 . in certain situations. such as major events or disasters. If no measures are taken to protect the BSS. the RNC reduces the number of unnecessary RRC CONNECTION REQUEST messages to be processed. 8. network impacts and engineering guidelines. Consequently. Ltd. To ensure system stability and the maximum processing capability.2. BTS/cell service flow control. BSSGP refers to Base Station Subsystem GPRS Protocol. flow control based on LAPD signaling links..SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 8 Flow Control l BSC: Base station controller (BSC) flow control is introduced to address BSC resource insufficiency. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Lb interface: Flow control on location request messages is introduced to address Lbinterface insufficiency. balances the load among subracks and boards. l Um interface: SDCCH flow control and PCH flow control are introduced to address Uminterface resource insufficiency. Huawei BSS introduces flow control based on user priorities. l A interface: CN flow control and A-interface flow control are introduced to address Ainterface resource insufficiency. BSC boards monitor the system resource usage in real time and stop some functions. The SGSN adjusts the downlink data rates for cells and MSs based on their maximum packet switched (PS) data volumes and the data transfer rate reported by the BSC. This achieves dynamic resource sharing. 40 . l Gb interface: BSSGP Virtual Connection (BVC) flow control and mobile station (MS) flow control are introduced to address Gb-interface insufficiency. l Abis interface: Flow control based on the message arrival rate. and improves BSC service processing efficiency. In addition. such as printing and recording logs. control-plane load sharing and user-plane load sharing are introduced to process random access requests. and flow control based on the call type are introduced to address Abisinterface resource insufficiency. Ltd. to decrease the central processing unit (CPU) usage to ensure system stability and reliability. 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. Then. In addition. this feature minimizes the duration of service disruption caused by the operation & maintenance operations. Ltd. Note that the OS.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 9 9 Operation and Maintenance Reliability Operation and Maintenance Reliability 9. 41 . The OMU board is then reset. 9.2 Technical Description This section describes how to implement the Operation & Maintenance System One-Key Recovery feature. 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. the Bootstrap scripts install the OMU applications and configure the information for the OMU applications.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. Five to ten minutes later.. The Bootstrap scripts first install the DOPRA Linux OS and configure the information for the OS. Scheme 1 The USB creator is used to create the USB disk for installing the DOPRA Linux OS and the OMU applications. and the respective configuration information must be stored onto the USB installation disk during the creation of the USB installation disk. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. OMU applications. Bootstrap scripts are generated on the USB installation disk to facilitate the start-up of the OMU board through the USB installation disk. the OS or OMU applications on the OMU board are recovered. Figure 9-1 shows the OMU board software recovery process. The USB installation disk is plugged into the USB port on the OMU board. Then. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 9 Operation and Maintenance Reliability 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 installation disk is plugged into the USB port on the OMU board. Five to ten minutes later. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Based on the information obtained. the switchover of the OS is complete. the USB creator is used to obtain the configuration information. the USB creator creates a USB installation disk for installing the DOPRA Linux OS. The OMU board is then reset. of the OMU board whose OS is to be switched. Ltd.. 42 . and the NE confirmation information. the OMU applications configuration information. especially the network configuration information. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 9 Operation and Maintenance Reliability 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. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 43 SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 9 Operation and Maintenance Reliability 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. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 44 SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 10 10 Hardware Reliability Hardware Reliability For the acronyms, abbreviations, terms, and definitions, see the Glossary. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd. 45 SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 10 Hardware Reliability 10. and this situation persists for a specified period of time. the two boards can be configured to work in board backup mode. the two boards work in board backup mode. The two boards work in board backup mode. For example. l Backup of GCUa/GCUb/GCGa/GCGb boards The BSC6910 is configured with two GCUa/GCUb/GCGa/GCGb boards in adjacent active and standby slots in the MPS. The two boards work in board backup mode. l Independent mode of the ESAUa Board The BSC6910 is configured with one ESAUa board.1 BSC6910 Board Redundancy BSC6910 board redundancy has two types: board backup and resource pool. the proportion of NodeBs having such cells reaches a predefined NodeB threshold. l If the BSC6910 detects any transmission fault. l The BSC6910 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.1 BSC/RNC Board Redundancy 10. the two boards can be configured to work in board backup or optical port backup mode. If the faulty board is the active one in a pair of active and standby boards. l The BSC6910 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. Ltd. l Backup of EOMUa boards When two EOMUa boards are installed in adjacent active and standby slots in the BSC6910 MPS. NOTE The BSC6910 interface boards have an effective mechanism for fault detection and automatic recovery. 46 . the BSC6910 reports an alarm instead of resetting the interface board. l Resource pool of DPUf boards The DPUf boards of the BSC6910 and the GUPTC subsystem of each DPUf work in resource pool mode. the BSC6910 switches over the active and standby boards.1. l Backup of SCUb boards The BSC6910 is configured with two SCUb boards in adjacent active and standby slots in each subrack. the BSC6910 resets the interface board. l Backup of AOUc/UOIc/POUc boards When two AOUc/UOIc/POUc boards are installed in adjacent active and standby slots in a BSC6910 subrack. When the BSC6910 detects that a certain proportion of resources of an interface board are unavailable for a specified period of time. l Resource pool of ENIUa boards The ENIUa boards of the BSC6910 work in resource pool mode. the proportion of such cells under the Iub interface board reaches a predefined cell threshold. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. l Backup of EXOUa/FG2c/GOUc/FG2d/GOUd boards When two EXOUa/FG2c/GOUc/FG2d/GOUd boards are installed in adjacent active and standby slots in a BSC6910 subrack. which works in independent mode. the two boards can be configured to work in board backup mode. UCUP for UMTS service processing. l Backup of AOUa/AOUc boards Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1. the BSC6900 switches over the active and standby boards. When the BSC6900 detects that a certain proportion of resources of an interface board are unavailable for a specified period of time. NOTE The BSC6900 interface boards have an effective mechanism for fault detection and automatic recovery.2 BSC6900 Board Redundancy BSC6900 board redundancy has two types: board backup and resource pool. l Backup of AEUa boards When two AEUa boards are configured in adjacent active and standby slots in a BSC6900 subrack. 10. l Backup of EIUa/EIUb boards When two EIUa/EIUb boards are configured in adjacent active and standby slots in a BSC6900 subrack. the two boards can be configured to work in board backup mode. and this situation persists for a specified period of time. l Backup of SCUa/SCUb boards The BSC6900 is configured with two SCUa/SCUb boards in adjacent active and standby slots in each subrack. the two boards can be configured to work in board backup mode. and GCUP for GSM service processing. The two boards work in board backup mode. Ltd. The redundancy mode of the EGPUa/EXPUa board varies depending on its logical type. l The BSC6900 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 two boards work in board backup mode. the BSC6900 resets the interface board. l Backup of TNUa/TNUb boards The BSC6900 is configured with two TNUa/TNUb boards in adjacent active and standby slots in some subracks. l Backup of OIUa/OIUb boards When two OIUa/OIUb boards are configured in adjacent active and standby slots in a BSC6900 subrack. the two boards can be configured to work in board backup mode. The EXPUa board provides the function of GSM service processing.. If the faulty board is the active one in a pair of active and standby boards. 47 . the BSC6900 reports an alarm instead of resetting the interface board. l If the BSC6900 detects any transmission fault. For example. the proportion of such cells under the Iub interface board reaches a predefined cell threshold.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description l 10 Hardware Reliability Resource pool and board backup of EGPUa/EXPUa boards The EGPUa board provides the following logical functions: RMP for resource management. l Resource pool of NIUa boards The NIUa boards of the BSC6900 work in resource pool mode. l The BSC6900 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 Backup of PEUa/PEUc boards When two PEUa/PEUc boards are configured in adjacent active and standby slots in a BSC6900 subrack. the proportion of NodeBs having such cells reaches a predefined NodeB threshold. . which works in independent mode. l Backup of GOUa/GOUc/GOUd boards When two GOUa/GOUc/GOUd boards are configured in adjacent active and standby slots in a BSC6900 subrack. the two boards can be configured to work in board backup mode or optical port backup mode. l Backup of FG2a/FG2c/FG2d boards When two FG2a/FG2c/FG2d boards are configured in adjacent active and standby slots in a BSC6900 subrack. Ltd. the two boards can be configured to work in board backup mode or optical port backup mode. the two boards work in board backup mode. l Backup of UOIa/UOIc boards When two UOIa/UOIc boards are configured in adjacent active and standby slots in a BSC6900 subrack. l Backup of XPUa/XPUb/SPUa/SPUb boards When two XPUa/XPUb/SPUa/SPUb boards are installed in adjacent active and standby slots in a BSC6900 subrack. l Independent mode of the SAUa/SAUc board The BSC6900 is configured with one SAUa/SAUc board. l Backup of OMUa/OMUb/OMUc boards When two OMUa/OMUb/OMUc boards are installed in adjacent active and standby slots in the BSC6900 MPS. l Backup of POUa/POUc boards When two POUa/POUc boards are configured in adjacent active and standby slots in a BSC6900 subrack. the two boards can be configured to work in either of the following modes: board backup with no port backup and board backup with port backup. l Backup of GCUa/GCUb/GCGa/GCGb boards The BSC6900 is configured with two GCUa/GCUb/GCGa/GCGb boards in adjacent active and standby slots in the MPS. the two boards can be configured to work in board backup mode. l Resource pool of DPUa/DPUb/DPUc/DPUd/DPUe/DPUf/DPUg boards The DPUa/DPUb/DPUc/DPUd/DPUe/DPUf/DPUg boards of the BSC6900 and the digital signal processors (DSPs) in all the DPUa/DPUb/DPUc/DPUd/DPUe/DPUf/DPUg boards work in resource pool mode. The two boards work in board backup mode. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the two boards can be configured to work in board backup mode or optical port backup mode. the two boards can be configured to work in either of the following modes: board backup with no port backup and board backup with port backup. 48 .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 10 Hardware Reliability When two AOUa/AOUc boards are configured in adjacent active and standby slots in a BSC6900 subrack. . Ltd. 49 .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 11 Related Features 11 Related Features Prerequisite Features None Mutually Exclusive Features None Impacted Features None Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 12 Network Impact 12 Network Impact System Capacity None Network Performance None Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 50 . Ltd.. use this feature to recover the OS without using an external storage medium.2. – If the controller upgrade tool is used to upgrade the DOPRA Linux OS.. or upgrade the DOPRA Linux OS to the latest version using the controller upgrade tool. the controller must run on the DOPRA Linux OS. such as a USB disk or CD-ROM. 13. a USB disk with a capacity of 2 GB or higher must be ready.1 Process l New sites The feature has been activated for the delivered OMU boards by default. Ltd.1 When to Use Operation & Maintenance System OneKey Recovery When the OS of the OMU board malfunctions. 51 .2 Requirements l New sites N/A l Existing sites – If the USB installation disk is used to install the DOPRA Linux OS.2 Deployment 13.2.2. 13.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 13 13 Engineering Guidelines Engineering Guidelines 13.3 Activation l Using the USB installation disk to install the latest DOPRA Linux OS Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Existing sites Install the latest DOPRA Linux OS using the USB installation disk. 13. . – Upgrade the controller software version by referring to the controller upgrade guide.5 Deactivation N/A 13. 52 . 13. Next. Ltd. For details. – Upgrade the DOPRA Linux OS. For detailed operations. use the USB installation disk to install DOPRA Linux.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 13 Engineering Guidelines Prepare the USB installation disk for switching the OMU OS from non-DOPRA Linux to DOPRA Linux.4 Troubleshooting N/A Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. l Upgrading the DOPRA Linux OS to the latest version using the controller upgrade tool – Confirm the controller software version required by DOPRA Linux. see Operation Guide to Switching OMU Operating System Through USB Disks.3 Performance Monitoring N/A 13.2.2. For details. see Guide to Dopra Linux Operating System Remote Patch Upgrade. see Guide to Dopra Linux Operating System Remote Patch Upgrade.4 Activation Observation N/A 13. 53 .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 14 Parameters 14 Parameters There are no specific parameters associated with this feature. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd.. P ROTECT.FAUL T.SDH.COUN TS T7043:Number of SDH Port Switchovers on external Requests BSC6900 MRFD-210101 System Redundancy 67194472 VS.SWAP .SDH.COUNTS T7042:Number of SDH Port Switchovers on K byte Requests BSC6900 MRFD-210101 System Redundancy 67194471 VS.REQ UEST. Ltd.REASON. 54 .CHANNEL.REASON.REASON.Flux.SDH.SDH.COUNT S T7041:Number of SDH Port Switchovers on Conditional Requests BSC6900 MRFD-210101 System Redundancy 67194470 VS. Peak.Frame.FAUL T.CHANNEL.EXT ERNAL.KBY TE.COU NTS T7044:Number of SDH Protection Channel Failures BSC6900 MRFD-210101 System Redundancy 67194473 VS. WORK.SDH.SWAP .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 15 Counters 15 Counters Table 15-1 Counter description Counter ID Counter Name Counter Description NE Feature ID Feature Name 67194469 VS.SWAP ..COUN TS T7045:Number of SDH Working Channel Failures BSC6900 MRFD-210101 System Redundancy 73436939 VS.TxRate HR9732a:Peak Inter-Subrack Transmitting Traffic BSC6900 MRFD-210104 BSC/RNC Resource Sharing Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. SDH.SWAP .REASON.Flux.KBY TE.Flux.TxRate HR9732a:Peak Inter-Subrack Transmitting Traffic BSC6910 MRFD-210104 BSC/RNC Resource Sharing Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. DropPackets R9732a:Numbe r of Discarded Inter-Subrack Packets BSC6900 MRFD-210104 BSC/RNC Resource Sharing 73441494 VS.Frame.Frame.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 15 Counters Counter ID Counter Name Counter Description NE Feature ID Feature Name 73436941 VS.SDH. 55 .COU NTS T7044:Number of SDH Protection Channel Failures BSC6910 MRFD-210101 System Redundancy 67194473 VS.COUN TS T7043:Number of SDH Port Switchovers on external Requests BSC6910 MRFD-210101 System Redundancy 67194472 VS.CHANNEL.COUNT S T7041:Number of SDH Port Switchovers on Conditional Requests BSC6910 MRFD-210101 System Redundancy 67194470 VS.COUNTS T7042:Number of SDH Port Switchovers on K byte Requests BSC6910 MRFD-210101 System Redundancy 67194471 VS.Frame.Frame.SWAP . Mean.EXT ERNAL.Flux.REQ UEST.SDH.FAUL T.SDH.TxRate AR9732a:Avera ge Inter-Subrack Transmitting Traffic BSC6900 MRFD-210104 BSC/RNC Resource Sharing 73441493 VS. WORK. Ltd.COUN TS T7045:Number of SDH Working Channel Failures BSC6910 MRFD-210101 System Redundancy 73436939 VS.SWAP .Flux. Peak..SDH.P ROTECT.FAUL T.REASON. TxPackets R9732b:Numbe r of Sent InterSubrack Packets BSC6900 MRFD-210104 BSC/RNC Resource Sharing 67194469 VS.CHANNEL.REASON. Flux. TxPackets R9732b:Numbe r of Sent InterSubrack Packets BSC6910 MRFD-210104 BSC/RNC Resource Sharing Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. Mean. 56 .Frame.Frame. Ltd.Flux.Frame. DropPackets R9732a:Numbe r of Discarded Inter-Subrack Packets BSC6910 MRFD-210104 BSC/RNC Resource Sharing 73441494 VS.Flux.TxRate AR9732a:Avera ge Inter-Subrack Transmitting Traffic BSC6910 MRFD-210104 BSC/RNC Resource Sharing 73441493 VS.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 15 Counters Counter ID Counter Name Counter Description NE Feature ID Feature Name 73436941 VS. .SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 16 Glossary 16 Glossary For the acronyms. see the Glossary. terms. Ltd. abbreviations. Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 57 . and definitions. Fault Management Feature Parameter Description for SingleRAN Issue Draft A (2014-01-20) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Overload Control Feature Parameter Description for WCDMA RAN 13.SingleRAN Base Station Controller Equipment Reliability Feature Parameter Description 17 17 Reference Documents Reference Documents 1. 58 . RNC Node Redundancy Feature Parameter Description for WCDMA RAN 6. Flow Control Feature Parameter Description for GSM BSS or WCDMA RAN 4. Ltd. Call Admission Control Feature Parameter Description for WCDMA RAN 11. Load Control Feature Parameter Description for WCDMA RAN 12. SGSN Pool Feature Parameter Description for GSM BSS 9. E2E Flow Control Feature Parameter Description for WCDMA RAN 14. Operation and Maintenance Feature Parameter Description for GSM BSS or WCDMA RAN 2. Controller Resource Sharing Feature Parameter Description for WCDMA RAN 3. BSC Node Redundancy Feature Parameter Description for GSM BSS 7. RNC in Pool Feature Parameter Description for WCDMA RAN 5. MSC Pool Feature Parameter Description for GSM BSS 8.. TC Pool Feature Parameter Description for GSM BSS 10.