Flow Control (RAN13.0 03)

Flow Control RAN13.
Feature Parameter Description
Issue Date
03 2012-05-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. 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 the 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: Email: http://www.huawei.com support@huawei.com
WCDMA RAN Flow Control
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History.............................................................................................................................. 1-1
2 Overview .....................................................................................................................................2-1
2.1 Definition ....................................................................................................................................... 2-1 2.2 Overall Picture of Flow Control ..................................................................................................... 2-1
3 Flow Control for Overloaded RNC Units.............................................................................3-1

3.1 Principle......................................................................................................................................... 3-1 3.1.1 Overview ............................................................................................................................... 3-1 3.1.2 CPU Usage Monitoring ......................................................................................................... 3-2 3.1.3 Message Block Occupancy Rate Monitoring........................................................................ 3-2 3.2 Whole Picture of Flow Control for Overloaded RNC Units............................................................ 3-3 3.3 Flow Control Triggered by CPUS Overload .................................................................................. 3-6 3.3.1 Overview ............................................................................................................................... 3-6 3.3.2 CPUS Basic Flow Control..................................................................................................... 3-6 3.3.3 Access Control...................................................................................................................... 3-7 3.3.4 Paging Control ...................................................................................................................... 3-8 3.3.5 RRC Flow Control................................................................................................................. 3-9 3.3.6 Flow Control on Signaling Messages over the Iur Interface................................................3-11 3.3.7 CBS Flow Control ............................................................................................................... 3-12 3.3.8 Cell/URA Update Flow Control ........................................................................................... 3-12 3.3.9 Flow Control over the Iur-g Interface .................................................................................. 3-13 3.3.10 Measurement Report Flow Control .................................................................................. 3-14 3.3.11 Queue-based RRC Shaping ............................................................................................. 3-14 3.4 Flow Control Triggered by MPU Overload .................................................................................. 3-16 3.4.1 Basic Flow Control for the MPU ......................................................................................... 3-16 3.4.2 MPU Overload Backpressure ............................................................................................. 3-17 3.5 Flow Control Triggered by INT Overload..................................................................................... 3-18 3.5.1 INT Basic Flow Control ....................................................................................................... 3-18 3.5.2 Flow Control Triggered by INT Overload on the Control Plane .......................................... 3-19 3.5.3 Flow Control Triggered by Iub Interface Board Overload on the User Plane ..................... 3-20 3.6 Flow Control Triggered by DPU Overload ................................................................................... 3-20 3.6.1 DPU Basic Flow Control ..................................................................................................... 3-20 3.6.2 Flow Control Triggered by DSP CPU Overload.................................................................. 3-20 3.7 Flow Control Triggered by SCU Overload ................................................................................... 3-21 3.7.1 Principle .............................................................................................................................. 3-21 3.7.2 Overload Indication............................................................................................................. 3-21 3.8 Flow Control Triggered by GCU Overload .................................................................................. 3-21
Issue 03 (2012-05-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Contents
3.8.1 Principle .............................................................................................................................. 3-21 3.8.2 Overload Indication............................................................................................................. 3-22
4 Flow Control Triggered by NodeB/Cell Overload .............................................................4-1

4.1 CAPS Control ................................................................................................................................ 4-1 4.1.1 Principle ................................................................................................................................ 4-1 4.1.2 Overload Indication............................................................................................................... 4-3 4.2 PCH Congestion Control ............................................................................................................... 4-4 4.2.1 Principle ................................................................................................................................ 4-4 4.2.2 Overload Indication............................................................................................................... 4-4 4.3 FACH Congestion Control ............................................................................................................. 4-4 4.3.1 Overview ............................................................................................................................... 4-4 4.3.2 Flow Control Based on Limited Number of UEs in the CELL_FACH State .......................... 4-5 4.3.3 CCCH Flow Control .............................................................................................................. 4-7 4.3.4 DCCH Flow Control .............................................................................................................. 4-9 4.3.5 DTCH Flow Control .............................................................................................................4-11 4.3.6 FACH Efficiency Boost ....................................................................................................... 4-12
5 Flow Control over the Iu Interface ........................................................................................5-1

5.1 SCCP Flow Control ....................................................................................................................... 5-1 5.1.1 Overview ............................................................................................................................... 5-1 5.1.2 Flow Control Based on Iu Signaling Load ............................................................................ 5-2 5.1.3 Flow Control Based on SCCP Setup Success Rate ............................................................ 5-2 5.1.4 CN SCCP Congestion Control ............................................................................................. 5-3 5.2 Flow Control Triggered by CN RANAP Overload .......................................................................... 5-3
6 Service Flow Control ...............................................................................................................6-1 7 Load Sharing ..............................................................................................................................7-1

7.1 Overview ....................................................................................................................................... 7-1 7.2 Load Sharing on the Control Plane ............................................................................................... 7-2 7.2.1 Procedure for Load Sharing on the Control Plane ............................................................... 7-2 7.2.2 Service Request Processing by a CPUS ............................................................................. 7-4 7.3 Load Sharing on the User Plane ................................................................................................... 7-6 7.3.1 Overview ............................................................................................................................... 7-6 7.3.2 Procedure for Load Sharing on the User Plane ................................................................... 7-6
8 Engineering Guidelines...........................................................................................................8-1
8.1 Access Control and Domain-Specific Access Control ................................................................... 8-1 8.1.1 Factors That Affect Access control and Domain-Specific Access Control ............................ 8-1 8.1.2 Configuration Principles and Suggestions............................................................................ 8-1 8.1.3 Performance Optimization .................................................................................................... 8-2 8.1.4 Key Parameter Settings........................................................................................................ 8-2 8.2 Queue-based RRC Shaping ......................................................................................................... 8-2 8.2.1 Factors That Affect Queue-based RRC Shaping ................................................................. 8-2
Issue 03 (2012-05-30)
ii
Contents
8.2.2 Configuration Principles and Suggestions............................................................................ 8-2 8.3 CAPS Control ................................................................................................................................ 8-2 8.3.1 Factors That Affect CAPS Control ........................................................................................ 8-2 8.3.2 Configuration Principles and Suggestions............................................................................ 8-2 8.3.3 Performance Optimization .................................................................................................... 8-3
9 Parameters .................................................................................................................................9-3 10 Counters .................................................................................................................................10-1 11 Glossary ..................................................................................................................................11-1 12 References .............................................................................................................................12-1 13 Appendix - Flow Control Algorithms ...............................................................................13-1
13.1 Switch Algorithm ........................................................................................................................ 13-1 13.2 Linear Algorithm ........................................................................................................................ 13-1 13.3 Hierarchical Algorithm ............................................................................................................... 13-2
Issue 03 (2012-05-30)
iii
1 Introduction
1 Introduction
1.1 Scope
This document concerns the feature WRFD-040100 Flow Control. It describes the functions and principles of RNC flow control, as well as the overload indications. Load control includes admission control and overload control. The goal is to ensure service quality and maximize system capacity. Flow control is part of overload control. Overload control works for the air interface, equipment, and the Iub/Iu interface. In addition, end-to-end (E2E) flow control can be implemented for the radio access network (RAN). This document describes flow control for overloaded RNC units, flow control triggered by NodeB/cell overload, flow control over the Iu interface, and flow control on user services. For details about E2E flow control for the RAN, see the E2E Flow Control Feature Parameter Description. For details about other types of overload control, see the Load Control Feature Parameter Description.
This document describes the principles of flow control. If you need specific overload control measures for mass gathering events, contact Huaweis professional service teams, who can provide tailored solutions. To learn more about admission control, see the Call Admission Control Feature Parameter Description.
1.2 Intended Audience

This document is intended for:

Personnel who have a good understanding of WCDMA principles Personnel who need to learn about flow control Personnel who work on Huawei products
1.3 Change History

This section describes the change history of this document. There are two types of changes:

Feature change: refers to a change in the flow control feature of a specific product version. Editorial change: refers to a change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The issues of this document are as follows:

03 (2012-05-30) 02 (2011-10-30) 01 (2011-04-30) Draft B (2011-03-30) Draft A (2010-12-30)
03 (2012-05-30)
This is the third commercial release of the document for RAN13.0. Compared with 02 (2011-10-30) of RAN13.0, this issue incorporates the changes described in the following table.
Issue 03 (2012-05-30)
1-1
1 Introduction
Change Type Feature change
Change Description
Parameter Change
The switch for changing the maximum number of UEs in the None FACH state from 30 to 60 is now RESERVED_SWITCH_0_BIT1 under ReservedSwitch0, instead of PERFENH_FACH_USER_NUM_SWITCH under PerfEnhanceSwitch. PERFENH_FACH_USER_NUM_SWITCH is no loger used. For details, see section 4.3.2 "Flow Control Based on Limited Number of UEs in the CELL_FACH State." The wait time for RRC connection attempts can be configured Added the based on service types. For details, see 4.1 "CAPS Control." RsvdPara3 parameter, which is used for configuring the wait time for RRC connection attempts. Corrected the function of the DSPRestrainCpuThd parameter None in user-plane load sharing. For details, see 7.3.2 "Procedure for Load Sharing on the User Plane."
Editorial change Optimized wording for the following functions: flow control None triggered by CN RANAP overload. For details, see section 5.2 "Flow Control Triggered by CN RANAP Overload."
02 (2011-10-30)
This is the second commercial release of RAN13.0. Compared with issue 01 (2011-04-30) of RAN13.0, this issue incorporates the changes described in the following table: Change Type Feature change Change Description None Parameter Change None
Issue 03 (2012-05-30)
1-2
1 Introduction
Change Type
Change Description
Parameter Change For changes in parameters, see related descriptions in the chapters.
Editorial change Optimized the entire document and added the following sections:

3.3.3 "Access Control" 3.3.4 "Paging Control" 3.3.5 "RRC Flow Control" 3.3.6 "Flow Control on Signaling Messages over the Iur Interface" 3.3.7 "CBS Flow Control" 3.3.8 "Cell/URA Update Flow Control" 3.3.9 "Flow Control over the Iur-g Interface" 3.3.10 "Measurement Report Flow Control" 3.3.11 "Queue-based RRC Shaping" 3.5.2 "Flow Control Triggered by INT Overload on the Control Plane" 3.6.2 "Flow Control Triggered by DSP CPU Overload" 4.2 "PCH Congestion Control" 4.3 "FACH Congestion Control
01 (2011-04-30)
This is the first commercial release for RAN13.0. Compared with issue Draft B (2011-03-30) of RAN13.0, this issue optimizes the description.
Draft B (2011-03-30)
This is an updated draft for RAN13.0. Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.
Draft A (2010-12-30)
This is the first draft for RAN13.0. Compared with issue 01 (2010-03-30) of RAN12.0, this issue incorporates the changes described in the following table: Change Type Feature change Change Description None Parameter Change None None
Editorial change Added "MPU Overload Backpressure."
Issue 03 (2012-05-30)
1-3
2 Overview
2 Overview
2.1 Definition
Flow control is a protective measure for communications between the RNC and its peer equipment. Flow control provides protection in the following ways:
It restricts incoming traffic to:

Protect Ensure
equipment from overload, thereby maintaining system stability. that equipment can properly process services even during heavy traffic.
It restricts outgoing traffic to reduce the load on the peer equipment.
2.2 Overall Picture of Flow Control

During mass gathering events, the amount of services surges, generating a significantly increased traffic volume that exceeds the processing capabilities of the system. As a result, the system becomes overloaded, which may lead to messages being randomly discarded and NE resetting, as well as response failures, call drops, service access failures, and other unexpected events. Resources in a WCDMA system are limited, so how they are used affects system performance. The resources concerned here are:

Equipment system resources, including CPU resources and memory Air interface resources, including channels, codes, and power Transmission resources Core network processing capabilities
To keep system stability and capabilities at the maximum possible level, Huawei RNCs perform flow control at five points in the system, which are numbered in Figure 2-1. Figure 2-1 Five points in flow control
Flow control involves discarding originating messages (such as RRC connection requests) that overload the system when system resources are insufficient, refusing to process low-priority services, and rejecting access requests for low-priority services.
Issue 03 (2012-05-30)
2-1
2 Overview
To address problems caused by limited RNC resources (labeled in Figure 2-1), the RNC performs flow control for RNC units. The software of each RNC board monitors the system resource usage. When necessary, the RNC starts basic flow control functions that suspend non-critical functions, such as recording logs and printing to reduce the system load. Then, based on the system load and the switch status of flow control functions, the RNC may perform other flow control functions to ensure system stability. For details, see chapter 3 "Flow Control for Overloaded RNC Units." To address problems caused by limited air interface resources (labeled in Figure 2-1), the RNC performs CAPS (Call Attempts Per Second) control, PCH congestion control and FACH congestion control.
When When
the NodeB or cell is overloaded with services, RNC limits the number of RRC connection requests admitted to a cell or NodeB each second. For details, see 4.1 "CAPS Control." the paging channel is congested, 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. For details, see section 4.2 "PCH Congestion Control." the FACH (Forward Access Channel) is congested, the RNC restricts message retransmissions on the logical channels, rejects certain PS service requests, and triggers state transitions such as CELL_PCH to CELL_DCH (P2D) and CELL_DCH to idle (D2Idle). This gives priority to access requests for high-priority services such as CS services, keeps the cell update success rate high, and reduces call drops. For details, see section 4.3 "FACH Congestion Control."
When
The RNC performs admission control, load reshuffling, and overload control on code and power resources. For details about admission control, see the Call Admission Control Feature Parameter Description. For details about load reshuffling and overload control, see the Load Control Feature Parameter Description.
To address problems caused by limited signaling bandwidth over the Iu interface (labeled in Figure 2-1), the RNC works with the core network to perform flow control over the Iu interface. Based on link congestion conditions detected at the local end and congestion indications reported from the peer end, the RNC performs flow control on initial UE messages to reduce the signaling traffic over the Iu interface. This prevents severe congestion on the signaling link between the RNC and the core network and reduces the load on the core network when it is overloaded. For details, see chapter 5 "Flow Control over the Iu Interface." The RNC supports user-plane congestion control over the Iub interface to restrict transmission rates when there is transmission congestion over the Iub interface. This prevents packet loss and makes more efficient use of the bandwidth. For details, see chapter 6 "Service Flow Control."
For access requests, the RNC supports load sharing within one subrack or between subracks on the user plane and control plane. This achieves dynamic sharing of resources, balancing the load among subracks and boards and improving service processing efficiency. For details, see chapter 7 "Load Sharing."
Issue 03 (2012-05-30)
2-2
3 Flow Control for Overloaded RNC Units

3.1 Principle
3.1.1 Overview
Each RNC board monitors the following in real time to keep track of resource consumption:

CPU usage: The CPU resources of a board determine the processing capabilities of the board. All functions running on the board use CPU resources. Message block occupancy rate: Message blocks are resources used to send and receive messages within the RNC.
When the CPU usage or message block occupancy rate of a board is high, the board processing capabilities may become insufficient. When this occurs, the board triggers flow control to ensure that basic functions can continue to run properly. Flow control based on message block occupancy rate is independent of flow control based on CPU usage. Related flow control functions will be triggered when either the message block occupancy rate or the CPU usage is excessively high. Generally, it is rare to run out of message blocks. Figure 3-1 shows the flow control model that each board follows based on CPU usage and message block occupancy rate. Figure 3-1 Flow control model
The XPUs, interface boards (collectively known as INTs), DPUs, SCUs and GCUs mentioned in this document are board types displayed on the LMT. An XPU comprises MPUs and CPUSs, which have the following functions:

An MPU manages resources on the user plane, control plane, and transport plane, informs MPUs in other subracks about the load on the current subrack, and makes decisions regarding load sharing. A CPUS processes services on the control plane.
Issue 03 (2012-05-30)
3-1
The XPU, INT, DPU, SCU, and GCU boards correspond to the following physical boards:

XPU: SPUa or SPUb INT: AEUa, AOUa, AOUc, FG2a, FG2c, GOUa, or GOUc DPU: DPUb or DPUe SCU: SCUa or SCUb GCU: GCUa or GCGa
For the detailed functions of each board, see the BSC6900 UMTS Hardware Description.
3.1.2 CPU Usage Monitoring

The system checks CPU usage in real time. If the CPU usage has reached the threshold for starting a flow control function that is based on the CPU usage and currently enabled, this function is started.
For details about flow control switches and CPU usage thresholds, see sections 3.3 "Flow Control Triggered by CPUS Overload," 3.4 "Flow Control Triggered by MPU Overload," 3.5 "Flow Control Triggered by INT Overload," 3.6 "Flow Control Triggered by DPU Overload," 3.7 "Flow Control Triggered by SCU Overload,", 3.8 "Flow Control Triggered by GCU Overload."
To prevent frequent flow control triggered by CPU usage fluctuations, the system also calculates the average CPU usage during a period of time that has just elapsed, and determines whether to perform flow control based on this CPU usage. The CPU usage values used to calculate the average CPU constitute a filter window, as shown in Figure 3-2. Figure 3-2 Filter window for calculating the average CPU usage
The filter window of a flow control function is configurable only if this function is controlled by using the SET FCSW command. For details, see section 3.2 "Whole Picture of Flow Control for Overloaded RNC Units."
3.1.3 Message Block Occupancy Rate Monitoring

Once it has allocated message blocks ten times, the system checks the message block occupancy rate. If the message block occupancy rate has reached the threshold for starting a flow control function that is based on the message block occupancy rate and currently enabled, this function is started.
For details about flow control switches and CPU usage thresholds, see sections 3.3 "Flow Control Triggered by CPUS Overload," 3.4 "Flow Control Triggered by MPU Overload," 3.5 "Flow Control Triggered by INT Overload," 3.6 "Flow Control Triggered by DPU Overload," 3.7 "Flow Control Triggered by SCU Overload,", 3.8 "Flow Control Triggered by GCU Overload."
To prevent frequent flow control triggered by message block occupancy rate fluctuations, the system also calculates the average message block occupancy rate. The message block occupancy rate values used to calculate the average message block occupancy rate constitutes a filter window, as shown in Figure 3-3.
Issue 03 (2012-05-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-2
Figure 3-3 Filter window for calculate the average message block occupancy rate
The filter window of a flow control function is configurable only if this function is controlled by using the SET FCSW command. For details, see section 3.2 "Whole Picture of Flow Control for Overloaded RNC Units."
3.2 Whole Picture of Flow Control for Overloaded RNC Units

Table 3-1 provides a whole picture of flow control for overloaded RNC units. Table 3-1 Whole picture of flow control for overloaded RNC units Overload Source Flow Control Function Printing flow control Debugging flow control Performance monitoring flow control Logging flow control Resource audit flow control MR flow control Paging control Access control RRC flow control High CPU usage High CPU usage or message block Queue-based RRC shaping Flow control on signaling messages over the Iur interface Flow Control Object Impact on Services No Controlling Command SET FCSW
CPUS
High CPU usage or message block occupancy rate
Printing Debugging Performance monitoring Logging Resource audit MR function Paging messages Users in AC0 to AC9 RRC connection requests RRC connection requests Some signaling messages over the Iur interface
Yes
SET FCSW SET FCSW None SET UCACALGOSWITCH SET FCSW
Issue 03 (2012-05-30)
3-3
Overload Source
Flow Control Function Flow control over the Iur-g interface CBS flow control
Flow Control Object
Impact on Services
Controlling Command
occupancy rate
All messages over the Iur-g interface All broadcast messages delivered by the CBC Some cell/URA update messages Printing Debugging Logging RRC connection requests Printing Debugging Logging RRC connection requests Yes SET TNSOFTPARA Yes None SET URRCTRLSWITCH SET FCSW None SET FCSW
Cell/URA update flow control MPU High CPU usage or message block occupancy rate Printing flow control Debugging flow control Logging flow control MPU overload backpressure Printing flow control Debugging flow control Logging flow control Flow control triggered by INT overload on the control plane Flow control triggered by Iub interface board overload on the user plane
High CPU usage INT High CPU usage or message block occupancy rate
High CPU usage
Congestion in queues at the ports
BE service rates
See related descriptions in 3.5.3 "Flow Control Triggered by Iub Interface Board Overload on the User Plane." None SET FCSW
DPU
Printing flow control Debugging flow control Logging flow control Flow control
Printing Debugging Logging BE service rates
High DSP
Yes
None
Issue 03 (2012-05-30)
3-4
Overload Source
Flow Control Function triggered by DSP CPU overload Printing flow control Debugging flow control Performance monitoring flow control Logging flow control
Flow Control Object
Impact on Services
Controlling Command
CPU usage SCU High CPU usage or message block occupancy rate
Printing Debugging Performance monitoring Logging Printing Debugging Logging
None
SET FCSW
GCU
Printing flow control Debugging flow control Logging flow control
None
SET FCSW
The filter windows for flow control functions configured by the SET FCSW command are configurable. The details are as follows:

For flow control decisions based on CPU usage, the SMWINDOW parameter of the SET FCCPUTHD command is used to configure the filter window. For flow control decisions based on message block occupancy rate, the SMWINDOW parameter of the SET FCMSGQTHD command is used to configure the filter window.
For flow control functions configured by the SET FCSW command, the system also uses a fast judgment window to prevent the CPU usage and message block occupancy rate from rapidly rising to a high level. The details are as follows:
If all CPU usage values during this fast judgment window are greater than or equal to a critical threshold, all currently enabled flow control functions based on CPU usage are started. The FDWINDOW and CTHD parameters of the SET FCCPUTHD command are used to configure the fast judgment window and critical threshold, respectively. The value of SMWINDOW should be at least twice the value of FDWINDOW. If the current message block occupancy rate value is greater than or equal to a critical threshold, all currently enabled flow control functions based on message block occupancy rate are started. The size of the fast judgment window for flow control based on the message block occupancy rate is 1. That is, the critical threshold decision does not use the filter mechanism. The CTHD parameter of the SET FCMSGQTHD command is used to configure the critical threshold.
When the FCSW parameter is set to OFF for a board, all flow control functions configured by the SET FCSW command are disabled for this board.
Issue 03 (2012-05-30)
3-5
3.3 Flow Control Triggered by CPUS Overload

3.3.1 Overview
The CPUS software monitors the CPU usage and message block occupancy rate of the CPUS in real time. Upon detecting a high CPU usage or message block occupancy rate, the CPUS software starts basic flow control, which is performed on non-critical functions, such as printing and logging. When the CPU usage or message block occupancy rate reaches or exceeds their respective thresholds, the CPUS software starts the following flow control functions if they are enabled:

Access control RRC flow control Flow control over the Iur interface CBS flow control Cell or URA update flow control Flow control over the Iur-g interface MR flow control
In addition, the CPUS software supports queue-based RRC shaping, which helps stabilize the CPU usage.
3.3.2 CPUS Basic Flow Control

Principle
Basic flow control for a CPUS is performed on printing, debugging, performance monitoring, logging, and resource auditing. The CPUS software monitors the CPU usage and message block occupancy rate of the CPUS in real time. Based on the monitored data, the CPUS software starts or stops all or some of the basic flow control functions.

When the CPU usage or message block occupancy rate reaches the threshold, the CPUS software starts flow control. When the CPU usage and message block occupancy rate fall below their respective thresholds, the CPUS software stops flow control.
The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled. The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Basic flow control for the CPUS has no impact on services.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. The following counters indicate the CPU usage and message block occupancy rate.
Issue 03 (2012-05-30)
3-6
Counter VS.XPU.CPULOAD.MEAN VS.XPU.MSGLOAD.MEAN
Description Average CPU usage of the XPU Average message block occupancy rate of the XPU
3.3.3 Access Control

Principle
When the network is heavily loaded, an access class (AC) identifies the access priority of specific UEs. ACs are numbered from 0 to 15. If the CPU usage of a CPUS is higher than the preset threshold, the CPUS software restricts the access of UEs of AC0 through AC9. This reduces the impact of traffic on the network. The RNC starts access control when the CPU usage of the CPUS exceeds the value of ACCTHD configured with the SET FCCPUTHD command or the message block occupancy rate exceeds the value of ACCTHD configured with the SET FCMSGQTHD command.
After the RNC starts access control for the CPUS, all cells under the CPUS are affected. The RNC first starts access control for a random cell. After a period of time defined by AcIntervalOfCell, the RNC starts access control for another random cell. This pattern continues until access control has been started for all cells under the CPUS. Users of certain ACs cannot access the access-controlled cell for each period of time defined by AcRstrctIntervalLen. The number of ACs affected by access control in each period is 10 times the value of AcRstrctPercent, and the ACs are chosen in turn. Assuming that the value of AcRstrctPercent is 20%, AC0 and AC1 users cannot initiate RRC connections under the cell during the first period of time defined by AcRstrctIntervalLen, and AC2 and AC3 users cannot initiate RRC connections under the cell during the second such period. This pattern continues under a cell this way until access control is stopped for this cell, as shown in Figure 3-4.
Figure 3-4 Access control on users under a cell when the value of AcRstrctPercent is 20%
Issue 03 (2012-05-30)
3-7
The RNC stops access control when the CPU usage of the CPUS falls below the value of ACRTHD configured with the SET FCCPUTHD command and the message block occupancy rate of the CPUS falls below the value of ACRTHD configured with the SET FCMSGQTHD command. Whether access control yields noticeable effects depends on the following factors:
How the operator defines users If SIM cards are evenly distributed among ACs before being sold, access control or DSAC can yield noticeable effects. If SIM cards are unevenly or incorrectly distributed among ACs, do not enable access control or DSAC because it may fail to yield noticeable effects.
UE compliance DSAC is applicable only to UEs that comply with 3GPP Release 6 or later. Access control is applicable to all UEs.
To determine whether AC is yielding notable effects, run the DSP UCELLACR command or check the value of the counter VS.RRC.AttConnEstab.Msg. Assuming AcRstrctPercent is set to 20%, access control is considered yielding noticeable effects if the value of this counter is 20% less than its value before access control was enabled. By default, access control is disabled. To enable it, set the values of ACSW and AcRstrctSwitch to ON. Users making emergency calls are all put into AC10 and are not subject to access control. The RNC can perform domain-specific access control (DSAC) to differentiate between the CS domain and the PS domain. When one domain is overloaded or unavailable, DSAC keeps the other domain from being negatively affected. This makes the network more resilient in the event of service interruption. For more details about DSAC, see the DSAC Feature Parameter Description.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. Access control uses system information to prevent users in certain ACs from accessing the network. To determine access control effects on the RNC side, compare the values of the counter VS.RRC.AttConnEstab.Msg before and after access control is enabled. This counter indicates the total number of RRC connection requests that the RNC has received from UEs.
3.3.4 Paging Control

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts paging control to reduce paging traffic and ensure high paging success rates for high-priority services. The PAGESW parameter in the SET FCSW command is used to enable paging control. By default, it is enabled.

When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts paging control and discards paging messages. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops paging control.
Paging control based on CPU usage varies by service. The SET FCCPUTHD command is used to configure paging control thresholds for different services, as described in Table 3-2. The higher the threshold for starting a flow control function, the more difficult it is for the flow control function to start.
Issue 03 (2012-05-30)
3-8
Table 3-2 Thresholds for paging control based on CPU usage Service Types Real-time services BE services (background and interactive services), supplementary services, and location services SMS Threshold for Starting Paging Control CPAGECTHD SLPAGECTHD Threshold for Stopping Paging Control CPAGERTHD SLPAGERTHD
SMPAGECTHD
SMPAGERTHD
To ensure a high paging success rate for high-priority services, such as CS services, the thresholds for starting paging control should be ranked as follows: CPAGECTHD > SLPAGECTHD > SMPAGECTHD This way, when paging control is in progress, SMS paging messages are the first to be discarded. Paging control applies to terminating UEs, and load sharing is not used for paging messages. As a result, paging control for one CPUS affects all paging processes within the same RNC. The thresholds for starting paging control should be higher than the thresholds for starting other flow control functions triggered by CPUS overload. Paging control based on message block occupancy rate does not vary by service. The threshold for starting this flow control function is configured by using the PAGECTHD parameter, and the threshold for stopping this flow control function is configured by using the PAGERTHD parameter.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The following counters are related to paging control. Counter VS.Paging.FC.Disc.Num.CPUS VS.Paging.FC.Disc.Time.CPUS Description Number of paging messages discarded because of paging control Duration of paging control in a measurement period
3.3.5 RRC Flow Control

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts rejecting or discarding RRC connection requests to avoid raising the CPU load further. RRC Flow Control is enabled by default. It is started after load sharing fails for RRC connection requests. For more details on load sharing for RRC connection requests, see chapter 7 "Load Sharing."
Issue 03 (2012-05-30)
3-9
When the CPU usage or message block occupancy rate of the CPUS exceeds the threshold, the RNC starts RRC flow control and rejects RRC connection requests. When the number of rejected RRC connection requests per second exceeds the value of SysRrcRejNum configured with the SET UCALLSHOCKCTRL command, the CPUS starts discarding subsequent RRC connection requests messages, without responding with RRC CONNECTION REJECT messages. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops RRC flow control. RRC flow control varies by service. The SET SHARETHD command is used to configure the necessary thresholds for the different services, as shown in Table 3-3. Table 3-3 Thresholds for RRC flow control Service Type Threshold for Starting RRC Flow Control Based on CPU Usage CRRCCONNCCPU THD Threshold for Stopping RRC Flow Control Based on CPU Usage CRRCCONNRC PUTHD Threshold for Starting RRC Flow Control Based on Message Block Occupancy Rate CRRCCONNCMSG THD Threshold for Stopping RRC Flow Control Based on Message Block Occupancy Rate CRRCCONNRMSGT HD
Inter-RAT cell reselection, IMSI detach procedure, registration, and incoming voice calls BE services and UE-originated voice calls SMS
LRRCCONNCCPU THD
LRRCCONNRC PUTHD
LRRCCONNCMSG THD
LRRCCONNRMSGT HD
SMRRCCONNCCP UTHD
SMRRCCONNR CPUTHD
SMRRCCONNCMS GTHD
SMRRCCONNRMS GTHD
To ensure high-priority services such as CS services are processed first, the thresholds for starting RRC flow control should be ranked as follows: CRRCCONNCCPUTHD > LRRCCONNCCPUTHD > SMRRCCONNCCPUTHD This way, when RRC flow control is in progress, RRC connection requests for SMS are the first to be discarded. When the CPU usage of the CPUS exceeds 90%, the RNC starts discarding all RRC connection requests except those for emergency calls.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The following counters indicate the number of RRC connection requests discarded because of RRC flow control.
Issue 03 (2012-05-30)
3-10
Counter VS.LowPriRRC.FC.Disc.Num.CPUS VS.NormPriRRC.FC.Disc.Num.CPUS
Description Number of discarded RRC connection requests for SMS because of RRC flow control based on CPU usage Number of discarded RRC connection requests for BE services and outgoing voice services because of RRC flow control based on CPU usage Number of discarded RRC connection requests for registration and incoming voice services because of RRC flow control based on CPU usage
VS.HighPriRRC.FC.Disc.Num.CPUS
3.3.6 Flow Control on Signaling Messages over the Iur Interface

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts flow control to reduce signaling traffic over the Iur interface so that the CPU load does not rise further.

When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts flow control over the Iur interface and discards signaling messages over the Iur interface. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops flow control over the Iur interface.
Flow control on signaling messages over the Iur interface consists of uplink transmission flow control over the Iur interface and downlink transmission flow control over the Iur interface, as described in Table 3-4. Table 3-4 Flow control over the Iur interface Flow Control Function Uplink transmission flow control over the Iur interface Downlink transmission flow control over the Iur interface Flow Control Objects UPLINK SIGNALLING TRANSFER INDICATION messages RADIO LINK SETUP REQUEST messages PAGING REQUEST messages COMMON TRANSPORT CHANNEL RESOURCES REQUEST messages Switch IURULSW IURDLSW
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Flow control over the Iur interface affects cell updates, handovers, and paging over the Iur interface. In addition, It affects ongoing service procedures because signaling messages are discarded. This may increase call drop rates.
Issue 03 (2012-05-30)
3-11
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm.
3.3.7 CBS Flow Control

Principle
In cases where the UTRAN uses an external cell broadcast center (CBC) to provide the cell broadcast service (CBS), the RNC starts CBS flow control upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold. This reduces signaling traffic over the Iu-BC interface and thereby prevents the CPU load from rising further. The CBSSW parameter in the SET FCSW command is used to enable CBS flow control. By default, it is enabled.

When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts CBS flow control and discards all CBC broadcast messages. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops CBS flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. CBS flow control affects cell broadcast services.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The following counters are related to CBS flow control. Counter VS.CBS.FC.Disc.Num.CPUS VS.CBS.FC.Disc.Time.CPUS Description Number of broadcast messages discarded because of CBS flow control Duration of CBS flow control in a measurement period
3.3.8 Cell/URA Update Flow Control

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts cell/URA update flow control to reduce the number of cell/URA update messages so that the CPU load does not rise further. The CELLURASW parameter in the SET FCSW command is used to enable cell/URA update flow control. By default, it is enabled.
When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts cell/URA update flow control. During cell/URA update flow control, the RNC discards cell or URA update requests originated by a UE in the CELL_PCH or URA_PCH state that involves a P2P
Issue 03 (2012-05-30)
3-12
transition (CELL_PCH to URA_PCH or URA_PCH to CELL_PCH) or a P2F transition (CELL_PCH or URA_PCH to CELL_FACH).
When the CPU usage and message block occupancy rate fall below the threshold, the RNC stops cell/URA update flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Cell/URA update flow control lowers the cell update success rate and affects uplink data transmission. In addition, UE locations recorded by the RNC may not be accurate because cell update messages are discarded. This may affect paging. For more details about UE state transitions, see the State Transition Feature Parameter Description.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The following counters are related to cell/URA update flow control. Counter VS.CU.FC.Disc.Num.CPUS VS.CU.FC.Disc.Time.CPUS Description Number of cell update requests discarded because of cell/URA update flow control Duration of cell/URA update flow control in a measurement period
3.3.9 Flow Control over the Iur-g Interface

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts Iur-g flow control to reduce signaling traffic over the Iur-g interface so that the CPU load does not rise further. The IURGSW parameter in the SET FCSW command is used to enable flow control over the Iur-g interface. By default, it is disabled.

When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts flow control and discards all messages sent over the Iur-g interface. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops flow control over the Iur-g interface.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. When flow control over the Iur-g interface is started, the RNC is not informed of real-time information about the GSM network load. This may cause the following problems:

When the GSM network load is heavy, inter-RAT handovers initiated by the RNC fail. When the GSM network load is light, the RNC does not initiate inter-RAT handovers, service distribution cannot be performed for UMTS services, and load sharing cannot be achieved between the UMTS and GSM networks.
Issue 03 (2012-05-30)
3-13
For more details about load-based handovers, service distribution, and load balancing over the Iur-g interface, see the Common Radio Resource Management Feature Parameter Description.
Overload Indication
3.3.10 Measurement Report Flow Control

Principle
Upon detecting that the CPU usage or message block occupancy rate of a CPUS is higher than the preset threshold, the RNC starts measurement report (MR) flow control to reduce the number of MR messages so that the CPU load does not rise further. The MRFCSW parameter in the SET FCSW command is used to enable MR flow control. By default, it is enabled.
When the CPU usage or message block occupancy rate exceeds the threshold, the RNC starts MR flow control. After MR flow control is started, the RNC stops sending MR measurement control messages to newly admitted UEs. Consequently, NodeBs and these UEs stop submitting MR measurement reports. MR flow control does not apply to UEs admitted before MR flow control is started. When the CPU usage and message block occupancy rate fall below their respective thresholds, the RNC stops MR flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. The MR function collects the following measurement reports:

Intra-frequency cell measurement reports Inter-frequency cell measurement reports Inter-RAT cell measurement reports DL BLER (downlink block error ratio) measurement reports Iub SIR (signal-to-interference ratio) measurement reports UE transmit power measurement reports LCS (location services) measurement reports, including UE location reports, Iub RTT (round trip time) measurement reports, and UE RX/TX (reception-transmission) measurement reports RACH (random access channel) measurements reports
Overload Indication
3.3.11 Queue-based RRC Shaping

Principle
When new service attempts generate a traffic volume that exceeds the maximum processing capability of the CPU in a CPUS, the CPU usage rises to a high level. When a large number of service setup attempts are made in a short period of time, the CPU usage fluctuates sharply. To address these
Issue 03 (2012-05-30)
3-14
problems, the RNC adopts a token- and queue-based shaping solution, which performs flow control on RRC connection requests. This solution stabilizes the CPU usage and increase RRC and RAB setup success rates when traffic is heavy. Tokens are permits to use the CPU resources of the CPUS. When an RRC connection request arrives, it applies for a token. RRC connection processing can proceed only after being granted a token. If the RRC connection request fails to obtain a token, it attempts to enter a specific queue and remains there until a token is available. If the queue is full, the RRC connection request is discarded. Figure 3-5 shows how queue-based RRC shaping works. Figure 3-5 Queue-based RRC shaping
By default, queue-based RRC shaping is disabled. To enable it, run the SET UCACALGOSWITCH command with the RsvdPara1 parameter set to RSVDBIT14-1. When an RRC connection request arrives, if the CPU usage of a CPUS is higher than 90%, the CPUS discards all RRC connection requests that are not from emergency calls. If the CPU usage is not higher than 90%, the CPUS checks whether the CPU load meets the conditions for load sharing. If so, the CPUS forwards the RRC connection request to the MPU for load sharing. If not, RNC performs queue-based RRC shaping. For details about load sharing, see chapter 7 "Load Sharing." Queue-based RRC shaping is as follows: 1. The RRC connection request applies for a token.
If If If
the request manages to obtain a token, the request is processed and this procedure is done.
the request fails to obtain a token and the queue is not full, the request enters the queue. Step 2 starts. the request fails to obtain a token and the queue is full, the request is discarded and this procedure ends.
2. The RRC connection request enters the queue. 3. The RRC connection request leaves the queue.
Issue 03 (2012-05-30)
3-15

The If
CPUS periodically scans the queues. If the RRC connection request has remained in a queue for longer than half of the value of T300, the CPUS discards the message. a token is available for the request, the request leaves the queue and is processed. Step 4 starts.
The CPUS first processes RRC connection requests from emergency calls and terminated voice calls. 4. The CPUS processes the RRC connection request. The RNC does not perform flow control on emergency calls, and emergency calls do not enter queues.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The counter VS.RRC.FC.Disc.Num.RRCQueue.CPUS indicates the number of RRC connection requests discarded because of queue-based RRC shaping.
3.4 Flow Control Triggered by MPU Overload

Flow control triggered by MPU overload is twofold: basic flow control for the MPU and MPU overload backpressure.
3.4.1 Basic Flow Control for the MPU

Principle
Basic flow control for an MPU is performed on printing, debugging, and logging. The MPU software monitors the CPU usage and message block occupancy rate of the MPU in real time. Based on the monitored data, the MPU software starts or stops all or some of the basic flow control functions.

When the CPU usage or message block occupancy rate reaches the threshold, the MPU software starts flow control. When the CPU usage and message block occupancy rate fall below the threshold, the MPU software stops flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled. Basic flow control for the MPU has no impact on services.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. The following counters indicate the CPU usage and message block occupancy rate. Counter VS.XPU.CPULOAD.MEAN Description Average CPU usage of the XPU
Issue 03 (2012-05-30)
3-16
Counter VS.XPU.MSGLOAD.MEAN
Description Average message block occupancy rate of the XPU
3.4.2 MPU Overload Backpressure

Principle
Under heavy traffic, the CPU of the MPU may be overloaded and fail to process services properly as a result. The RNC adopts an overload backpressure function. With this function, CPUSs work with MPUs to perform flow control on RRC CONNECTION REQUEST messages to alleviate the impact of heavy traffic on MPUs. Congestion detection is performed based on the instantaneous CPU usage of the MPU. When the CPU usage of the MPU reaches 80% (this percentage is unconfigurable) or higher, the MPU sends a congestion message to the CPUS bound to it, as shown in Figure 3-6. Figure 3-6 Flow control based on MPU overload
Upon receipt of the congestion message from the MPU, the CPUS adjusts the flow control level. The RNC adjusts the number of RRC connection requests that can be admitted on the CPUS each second according to the flow control level change. Flow control for the CPUS is performed on a scale of 30 levels. A higher flow control level means fewer RRC connection requests admitted each second. The CPUS adjusts the flow control level by using two timers, one with a value of 2.2 seconds, the other with a value of 0.8 seconds.
Upon receiving a congestion message from the MPU, the CPUS increases the flow control level by one and starts the two timers.
Issue 03 (2012-05-30)
3-17

If MPU congestion messages are received before the 0.8-second timer expires, the CPUS does not take any actions. If MPU congestion messages are received after the 0.8-second timer expires but before the 2.2-second timer expires, the CPUS increases the flow control level by one and restarts the two timers. After the 2.2-second timer expires, the CPUS decreases the flow control level by one.
When the RsvdPara1 parameter in the SET URRCTRLSWITCH command is set to RSVDBIT1_BIT19-1, MPU overload backpressure is enabled. By default, it is enabled.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an XPU, check the subrack number and slot number in the alarm. The counter VS.RRC.FC.Disc.Num.MPU.CPUS indicates the number of RRC connection requests discarded because of MPU overload backpressure.
3.5 Flow Control Triggered by INT Overload

Flow control triggered by INT overload is threefold: basic flow control for the INT, flow control triggered by INT overload on the control plane, and flow control triggered by Iub interface board overload on the user plane.
3.5.1 INT Basic Flow Control

Principle
When an interface board (INT) is heavily loaded, it starts basic flow control. Basic flow control for an INT is performed on printing, debugging, and logging. The INT software monitors the CPU usage and message block occupancy rate of the INT in real time. Based on the monitored data, the INT software starts or stops all or some of the basic flow control functions.

When the CPU usage or message block occupancy rate reaches the threshold, the INT software starts flow control. When the CPU usage and message block occupancy rate fall below the threshold, the INT software stops flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Basic flow control for the INT has no impact on services. The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an INT, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. The counter VS.INT.CPULOAD.MEAN indicates the CPU usage.
Issue 03 (2012-05-30)
3-18
3.5.2 Flow Control Triggered by INT Overload on the Control Plane

Principle
After a UE initiates an RRC connection request and obtains transmission resources on the MPU, the CPUS sends a session setup request to the interface board. When a large number of service setup requests are made in a short period of time, the interface board needs to process a large number of session setup requests and may be overloaded. The MPU adopts a flow control process based on service priorities and the instantaneous CPU usage of the interface board. This type of flow control improves the RAB setup success rate when the interface board is heavily loaded. The interface board reports its CPU usage to the MPU each second, as shown in Figure 3-7. Based on the CPU usage of the interface board, the MPU adjusts the maximum number of session setup requests admitted by the interface board. If the number of RRC connection requests already admitted is larger than the maximum number allowed, the RNC only processes RRC connection requests from emergency calls and high-priority services. The FcOnItfBrd parameter in the SET TNSOFTPARA command is used to enable this type of flow control. It is enabled by default and applies to Iub, Iu, and Iur interface boards. The maximum number of session setup requests allowed determines the signaling processing capability of the interface board. High-priority services involved in this type of flow control refer to incoming and outgoing voice calls, inter-RAT cell reselection, and registration. Figure 3-7 Flow control triggered by INT overload
When the CPU usage of the interface board exceeds 90%, the MPU starts discarding RRC connection requests from all UEs.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an INT, check the subrack number and slot number in the alarm.
Issue 03 (2012-05-30)
3-19
3.5.3 Flow Control Triggered by Iub Interface Board Overload on the User Plane
When the amount of user-plane data sent from the DPU to the interface board exceeds the processing capability of the interface board, the interface board throughput decreases and the packet loss rate increases. To address this problem, the RNC adopts backpressure-based downlink congestion control. For more details, see the Transmission Resource Management Feature Parameter Description.
3.6 Flow Control Triggered by DPU Overload

3.6.1 DPU Basic Flow Control
Principle
When a DPU is heavily loaded, it starts basic flow control. Basic flow control for a DPU is performed on printing, debugging, and logging. The DPU software monitors the CPU usage and message block occupancy rate of the DPU in real time. Based on the monitored data, the DPU software starts or stops all or some of the basic flow control functions.

When the CPU usage or message block occupancy rate reaches the threshold, the DPU software starts flow control. When the CPU usage and message block occupancy rate fall below the threshold, the DPU software stops flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Basic flow control for the DPU has no impact on services. The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled.
Overload Indication
When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for a DPU, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. When all DSPs under the RNC have been heavily loaded for an extended period of time, the RNC reports ALM-22305 Resource overload on the user plane.
3.6.2 Flow Control Triggered by DSP CPU Overload

Principle
To ensure admission of CS services and quality of ongoing CS services, the RNC lowers the rates of BE services when the CPU of a DSP is heavily loaded. By default, this type of flow control is enabled. Each DSP of the DPU periodically monitors its own CPU usage.

When the CPU usage is between SSDSPAVEUSAGEALMTHD and SSDSPMAXUSAGEALMTHD, the RNC lowers the rates of BE services. When the CPU usage is lower than the threshold SSDSPAVEUSAGEALMTHD, the RNC raises the rates of BE services.
Issue 03 (2012-05-30)
3-20
To prevent the DSP from crashing, if the CPU usage is higher than 90% during a monitoring period, the RNC further lowers BE service rates and discards some packets of BE services and AMR services.
When the RNC raises or lowers service rates, the current monitoring period is ended. To prevent frequent changes in service rates, the RNC waits a period of time before starting the next monitoring period. During this period, the RNC does not increase or decrease rates of BE services.
Overload Indication
There are no indications when the CPU of a DSP is overloaded.
3.7 Flow Control Triggered by SCU Overload

3.7.1 Principle
When an SCU is heavily loaded, it starts basic flow control. Basic flow control for an SCU is performed on printing, debugging, performance monitoring, and logging. The SCU software monitors the CPU usage and message block occupancy rate of the SCU in real time. Based on the monitored data, the SCU software starts or stops all or some of the basic flow control functions.
When the CPU usage or message block occupancy rate reaches the threshold, the SCU software starts flow control. When the CPU usage and message block occupancy rate fall below the threshold, the SCU software stops flow control.
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Basic flow control for the SCU has no impact on services. The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled.
3.7.2 Overload Indication

When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for an SCU, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. The counter VS.SCU.CPULOAD.MEAN indicates the CPU usage.
3.8 Flow Control Triggered by GCU Overload

3.8.1 Principle
When a GCU is heavily loaded, it starts basic flow control. Basic flow control for a GCU is performed on printing, debugging, and logging. The GCU software monitors the CPU usage and message block occupancy rate of the GCU in real time. Based on the monitored data, the GCU software starts or stops all or some of the basic flow control functions.
When the CPU usage or message block occupancy rate reaches the threshold, the GCU software starts flow control. When the CPU usage and message block occupancy rate fall below the threshold, the GCU software stops flow control.
Issue 03 (2012-05-30)
3-21
The SET FCCPUTHD command is used to configure the thresholds for flow control based on CPU usage, and the SET FCMSGQTHD command is used to configure the thresholds for flow control based on message block occupancy rate. Basic flow control for the GCU has no impact on services. The SET FCSW command is used to enable the basic flow control functions. By default, all basic flow control functions are enabled.

When the CPU usage reaches the preset threshold (configured by the SET CPUTHD command), ALM-20256 CPU Overload is reported. To find out whether the alarm was reported for a GCU, check the subrack number and slot number in the alarm. EVT-22835 Flow Control is reported when a basic flow control function is started. To find out which basic flow control function was started, check the flow control type in the event. The counter VS. GCU.CPULOAD.MEAN indicates the CPU usage.
Issue 03 (2012-05-30)
3-22
4 Flow Control Triggered by NodeB/Cell Overload

4.1 CAPS Control
4.1.1 Principle
When the number of calls in a cell or NodeB sharply increases, most system resources (mainly radio resources) are consumed processing the enormous amount of RRC connection setup requests. Therefore, the remaining resources are insufficient for processing subsequent RAB assignment requests, resulting in call failures. To solve this problem, the RNC implements the CAPS control function. This function limits the number of RRC connection requests admitted to a cell or NodeB each second. By preventing the traffic of a single cell or NodeB from surging, CAPS control helps maintain a stable traffic volume on the network. Figure 4-1 shows the procedure for CAPS control. Figure 4-1 Procedure for CAPS control
By default, CAPS control is disabled.
To enable cell-level CAPS control:

Set
the CallShockCtrlSwitch parameter to SYS_LEVEL-0&NODEB_LEVEL-0&CELL_LEVEL-1;
and
Set
the RsvdPara1 parameter (by running the ADD UCELLALGOSWITCH command) to RSVDBIT4-1.
Issue 03 (2012-05-30)
4-1
To enable NodeB-level CAPS control:

Set
the CallShockCtrlSwitch parameter to SYS_LEVEL-0&NODEB_LEVEL-1&CELL_LEVEL-0;
and
Set
the RsvdPara1 parameter (by running the ADD UNODEBALGOPARA command) to RSVDBIT1-1. the CallShockCtrlSwitch parameter to SYS_LEVEL-0&NODEB_LEVEL-1&CELL_LEVEL-1;
To enable both cell-level and NodeB-level CAPS control:

Set
and
Set
the RsvdPara1 parameter (by running the ADD UCELLALGOSWITCH command) to RSVDBIT4-1. Set the RsvdPara1 parameter (by running the ADD UNODEBALGOPARA command) to RSVDBIT1-1.
The CallShockCtrlSwitch parameter is for the RNC. To enable cell- or NodeB-level CAPS control, you need to set the associated parameter for the cell or NodeB. The SYS_LEVEL field of the CallShockCtrlSwitch parameter is used to enable CPUS-level CAPS control, which is no longer applicable. After CAPS control is enabled, the RNC periodically checks the total number of RRC connection requests received by a cell or NodeB. When this number exceeds the preset threshold, the RNC triggers the cell- or NodeB-level flow control. The check period is set with the CallShockJudgePeriod parameter. Table 4-1 describes the conditions for triggering the cell- and NodeB-level flow control. Table 4-1 Conditions for triggering the cell- and NodeB-level flow control
Flow Control Level Cell NodeB Triggering Condition The total number of RRC connection requests received by a cell during a specified period exceeds the value of CellTotalRrcNumThd.
The total number of RRC connection requests received by a NodeB during a specified period exceeds the value of NBTotalRrcNumThd; or NCP link congestion over the Iub interface is detected.
Table 4-2 describes the flow control policy for different services. Table 4-2 Flow control policy
Service Flow Control Policy
PS BE services (interactive service and background service), streaming service, short message service (SMS), and inter-RAT cell change AMR service
The RNC rejects the access requests of these services.
Cell-level flow control:
The number of RRC connection requests admitted for AMR services in a cell each second must not exceed the value of the CellAmrRrcNum parameter. Once the limit is reached, the RNC rejects all subsequent requests.
NodeB-level flow control:
The number of RRC connection requests admitted for AMR services in a
Issue 03 (2012-05-30)
4-2
WCDMA RAN Flow Control Service Flow Control Policy
NodeB each second must not exceed the value of the NBAmrRrcNum parameter. Once the limit is reached, the RNC rejects all subsequent requests. Registration and inter-RAT cell reselection When the RegByFachSwitch parameter is set to ON, the RNC forcibly sets up the RRC connection of registrations on the FACH.
Cell-level flow control:
The number of RRC connection requests for registrations and inter-RAT cell reselections in a cell each second must not exceed the value of the CellHighPriRrcNum parameter. Once the limit is reached, the RNC rejects all subsequent requests.
NodeB-level flow control:
The number of RRC connection requests for registrations and inter-RAT cell reselections in a NodeB each second must not exceed the value of the NBHighPriRrcNum parameter. Once the limit is reached, the RNC rejects all subsequent requests. Emergency call Flow control is not applied to emergency calls.
To prevent a UE from frequently retransmitting the RRC connection requests, the RNC adds an IE "wait time" to the RRC connection reject message sent to the UE. The UE waits for the length of time specified by RrcConnRejWaitTmr and then retransmits the RRC connection request. In this way, network congestion will not be aggravated. The UE needs to support the processing associated with "wait time." To prevent the UE from frequently triggering RRC connection attempts and aggravating network congestion, the RNC carries the wait time in the RRC CONNECTION REJECT message sent to the UE, requesting the UE to wait the specified period of time before making the next attempt. This requires the UE to support the wait time function. The wait time can be configured by using a parameter. Different parameters are used for different service types, as shown in Table 4-3. Table 4-3 Parameters for the wait time Service Type Conversational services and emergency calls BE services and streaming services Parameter RrcConnRejWaitTmr RsvdPara3
If the value of the RsvdPara3 parameter is set to 0, this parameter has no impact on BE services and streaming services. The wait time for BE services and streaming services is configured by using the RrcConnRejWaitTmr parameter. When the number of RRC connection requests rejected per second exceeds the value of the SysRrcRejNum parameter, the RNC discards subsequent RRC connection requests.

The counter VS.RRC.FC.Disc.Num.CallShock.CPUS indicates the number of RRC connection requests discarded on the CPUS because of CAPS control.
Issue 03 (2012-05-30)
4-3
4.2 PCH Congestion Control

4.2.1 Principle
Because PS services are growing so rapidly, the number of paging messages consuming a large amount of paging resources is also increasing rapidly. As a result, the paging success rate of CS services may be affected. To address this issue, the RNC implements PCH congestion control. With PCH congestion control, CS services are allowed to preempt the paging resources of PS services in the event of PCH congestion, increasing the paging success rate of CS services. When the number of transmitted paging messages in a transmission time interval (TTI) reaches the maximum (known as PCH congestion), push to talk (PTT) services and conversational services can start preempting the paging resources of other services. If preemption fails, the paging message for a PTT or conversational service is discarded. The rules for PCH congestion control are as follows:

PTT services can preempt the paging resources of other services but its resources cannot be preempted by other services. Conversational services can preempt the paging resources of non-conversational services. The paging messages of other services (except PTT services and conversational services) are discarded.
By default, PCH congestion control is disabled. To enable PCH congestion control and allow the conversational services to preempt the paging resources of non-conversational services, run the SET UDPUCFGDATA command to set PAGINGSWITCH to ON. If the value of the counter VS.RRC.Paging1.Loss.PCHCong.Cell is not 0, the PCH is congested. If this happens, enable PCH congestion control and do not disable it once it is enabled.

When the PCH is congested, the paging messages are discarded. The counter VS.RRC.Paging1.Loss.PCHCong.Cell indicates the number of discarded paging messages. When the PCH congestion control function is enabled, CS services can preempt the paging resources of PS services. The counter VS.RRC.Paging1.PCHCong.CSPreemptAtt indicates the number of paging preemptions by CS services in a cell due to PCH congestion.
4.3 FACH Congestion Control

4.3.1 Overview
The Forward Access Channel (FACH) is a downlink common transport channel that carries control messages to a UE during initial access and state transition. The FACH may also carry a small quantity of user-plane data. FACH congestion may block information exchange between UEs and the network, affecting service provisioning. To address this issue, the RNC implements FACH congestion control. FACH congestion may be due to the fact that the number of UEs in the CELL_FACH state is limited, or the fact that the resources of the logical channels (CCCH/DCCH/DTCH) on the FACH are congested. Table 4-4 describes how flow control is implemented in different scenarios where FACH congestion is the problem. Table 4-4 FACH flow control Cause of FACH Congestion Limited number of UEs Flow Control Actions The P2D transitions is triggered.
Issue 03 (2012-05-30)
4-4
in the CELL_FACH state CCCH congestion
The D2Idle transitions of PS BE services is triggered. Message retransmission is stopped. New PS BE services are rejected and data transmission of admitted PS BE services is forbidden.
DCCH congestion
The P2D transitions of CS services is triggered. The D2Idle transitions of PS BE services is triggered. The F2D transitions of PS BE services is forbidden. The P2F transitions of PS BE services is forbidden.
DTCH congestion
The traffic volume-based P2D transitions of PS services is triggered.
When there is CCCH/DCCH/DTCH congestion on the FACH, the RNC performs flow control based on the congestion level. The congestion level is determined by comparing the channel buffer size and the preset thresholds, as described in Table 4-5. Table 4-5 Determination on CCCH/DCCH/DTCH congestion level Congestion Level Non-congestion Determining Condition Channel buffer size less than the congestion clearance threshold Channel buffer size greater than or equal to the congestion threshold Channel buffer size greater than or equal to the discard threshold Parameter for CCCH CCCHCongClearThd Parameter for DCCH/DTCH FachCongClearThd
Minor congestion Major congestion
CCCHCongThd
FachCongThd
None
N/A
The congestion and congestion clearance thresholds are set by using the SET UDPUCFGDATA command. Keep the default values (60 for the congestion threshold and 30 for the congestion clearance threshold). If you need to modify the parameter settings, consult Huawei technical support because the modification affects flow control. For details about WCDMA channels, see the Radio Bearers Feature Parameter Description. For details about state transitions, see the State Transition Feature Parameter Description.
4.3.2 Flow Control Based on Limited Number of UEs in the CELL_FACH State
Principle
Generally, a state transition from CELL_DCH to CELL_FACH (referred to as a D2F transition) shall occur if Event 4B is triggered, as indicated by procedure in Figure 4-2. Event 4B is triggered when the traffic volume of the UE is low for some time. If a UE in the CELL_PCH or URA_PCH state needs to
Issue 03 (2012-05-30)
4-5
transmit data or respond to a paging message, it initiates a cell update message to enter the CELL_FACH state, as shown in procedure in Figure 4-2. The number of UEs on the FACH (UEs in the CELL_FACH state) is limited in a cell. The two types of state transition previously mentioned may fail if the number of UEs in the CELL_FACH state reaches the limit. As a result, UEs in the CELL_DCH state, having little or no data to transmit, may continuously occupy the dedicated channels and cell resource utilization may decrease as a result. UEs in the CELL_PCH or URA_PCH state may also fail to perform data transmission or respond to paging messages and finally enter the idle state, leading to PS service drops. Generally, the maximum number of UEs in the CELL_FACH state is 30. To raise the maximum number of UEs in the FACH state to 60, select RESERVED_SWITCH_0_BIT1 under the ReservedSwitch0 parameter of the SET UNBMPARA command. Figure 4-2 UE state transitions
The RNC allows D2Idle transitions (procedure in Figure 4-2) and P2D transitions (procedure in Figure 4-2), when the number of UEs in the CELL_FACH state has reached the upper limit. Table 4-6 describes the triggering conditions for these state transitions. Table 4-6 Triggering conditions for a D2Idle transition and a P2D transition UE State CELL_DCH State Transition D2Idle Triggering Condition The IE "Volume" of all Event 4Bs is 0, triggering a D2F transition. The D2F transition fails because the number of UEs in the CELL_FACH state has reached the upper limit. CELL_PCH/ URA_PCH P2D The cause of a cell update is "uplink data transmission" or "paging response", triggering a P2F transition. The P2F transition fails because the number of UEs in the CELL_FACH state has reached the upper limit. Switch The ReservedSwitch0 parameter is set to RESERVED_SWITCH_ 0_BIT16-1.
The RsvdPara1 parameter is set to RSVDBIT1_BIT20-1.
Issue 03 (2012-05-30)
4-6
The D2Idle transition function is disabled by default, and can be enabled by running the SET UCORRMALGOSWITCH command. After a UE moves to the idle state, the RNC releases the dedicated channel for the UE in order to improve the cell resource utilization. The P2D transition function is disabled by default, and can be enabled by running the SET URRCTRLSWITCH command. During a P2D transition, the RNC delivers the UE a cell update confirm message on the CCCH, which prevents call drops because the delivery does not use up resources designated for UEs in the CELL_FACH state. The initial access rate of a PS service is 8 kbit/s after the UE has entered the CELL_DCH state.
The
rate of PS BE services (non-PTT services) can be limited to 8 kbit/s to prevent excess usage of the DCH resources. This function can be enabled by running the SET UCORRMALGOSWITCH command with the ReservedSwitch1 parameter set to RESERVED_SWITCH_1_BIT6-1. This function is enabled by default. PS BE service (non-PTT services) can be set up on the HS-DSCH or E-DCH when the call drop rate increases because of a large number of P2D transitions as well as H attempts or DCCC rate increase attempts of users on the DCH. An H attempt refers to a channel shift from DCH to HS-DSCH or E-DCH. This function is disabled by default. To enable it, run the SET UCORRMPARA command with the PerfEnhanceSwitch parameter set to PERFENH_PSTraffic_P2H_SWITCH-1.
The
If the number of UEs in the CELL_FACH state reaches the upper limit, cell updates may fail, including those triggered by radio link setup failures. As a result, call drops may occur. To prevent this, you can reserve some UEs in the CELL_FACH state for cell updates. To set the number of reserved users, run the SET UCORRMALGOSWITCH command and modify the ReservedU32Para1 parameter. If the maximum number of UEs in the CELL_FACH state is 30 and the number of reserved UEs in the CELL_FACH state is 5, the D2F transition shown in Figure 4-2 will not be implemented when the number of UEs in the CELL_FACH state reaches 25. Instead, the D2Idle transition may be triggered. The resources for reserved UEs are for the users who send cell update messages. If the value of the counter VS.CellFACHUEs (the number of UEs in the CELL_FACH state) is greater than or equal to 25, set the ReservedSwitch0 parameter to RESERVED_SWITCH_0_BIT1-1 so that the maximum number of UEs in the CELL_FACH state can be 60. In addition, enable the P2D transition and the D2Idle transition. For details about UE state transition in normal cases, see the State Transition Feature Parameter Description.
Overload Indication
The counter VS.CellFACHUEs indicates the number of UEs in the CELL_FACH state.
4.3.3 CCCH Flow Control

Principle
The common control channel (CCCH) is a logical channel that transmits control messages, such as RRC messages and cell update confirm messages, between the RNC and UEs. The CCCH processes the received messages in its buffer in sequence. The CCCH processes the following messages:

RRC CONNECTION SETUP RRC CONNECTION REJECT RRC CONNECTION RELEASE CELL/URA UPDATE CONFIRM (used during a P2D transition for cell update)
The CCCH may be congested in either of the following situations:
Issue 03 (2012-05-30)
4-7

UEs with PS services frequently send RRC connection requests. A large number of UE registrations (including 2G/3G cell reselections) occur within a short period.
CCCH congestion may become severer in either of the following situations:
The RNC repeatedly sends a UE the RRC connection setup message or cell update confirm message within the time specified by T381, aiming to increase the success rate of the UE receiving the RRC connection setup message or cell update confirm message. A UE repeatedly sends the RRC connection request or cell update message to the RNC if the UE does not receive the RRC connection setup message within T300 or the cell update confirm message within T302. This is because the RRC connection setup message and cell update confirm message sent by the RNC the first time may have been discarded if the CCCH is congested.
To guarantee the success rate of RRC connection setup and cell update in case of CCCH congestion, the RNC implements CCCH flow control. The RNC performs CCCH flow control differentiating the RRC connection requests and the P2D transitions for cell update according to the CCCH congestion level. The CCCH congestion level is determined by comparing the CCCH buffer size and the preset thresholds, as described in Table 4-5. Figure 4-3 shows CCCH flow control. Figure 4-3 CCCH flow control
In the event of minor CCCH congestion, the RNC performs flow control as follows:
For For
CS service requests, the RNC handles the RRC connection requests and cell update messages as it normally does, but it does not retransmit these messages because T381 is stopped. PS BE service requests, the RNC discards the retransmitted RRC connection requests after T300 expires and cell update messages after T302 expires. This means that the RNC only handles the service request transmitted for the first time. In addition, the RNC stops T381.
In the event of major CCCH congestion, the RNC performs flow control as follows: The RNC discards RRC connection requests, rejects new PS BE services, discards the cell update messages, and forbids existing PS BE services from transmitting data. The RNC stops T381 for CS service requests.
CCCH flow control stops once the CCCH is no longer congested.
Issue 03 (2012-05-30)
4-8
CCCH flow control is disabled by default. To enable it, run the MOD UCELLALGOSWITCH command and set the RsvdPara1 parameter to RSVDBIT5-1. Enable CCCH flow control in mass gathering events, in which case the traffic volume surges. Keep CCCH flow control enabled to increase the success rate of RRC connection setup and cell update when the CCCH is congested. If CCCH congestion and Uu-interface resource (code/power/CE) congestion are detected, the RNC adds an IE "wait time" to the RRC connection reject message sent to the UE. The UE waits for the length of time specified by this IE and then retransmits an RRC connection request. When the FACH is congested, the RNC automatically sets the RrcConnRejWaitTmr parameter to 15.
Overload Indication
None
4.3.4 DCCH Flow Control

Principle
The dedicated control channel (DCCH) is a logical channel that transmits dedicated control messages, such as reconfiguration messages and cell update confirm messages, between a UE and the RNC. The DCCH processes the received messages in its buffer in sequence. The DCCH processes the following messages:

RADIO BEARER RECONFIGURATION (F2D/F2P transitions) CELL/URA UPDATE CONFIRM (P2F cell updates) DOWNLINK DIRECT TRANSFER/SECURITY MODE COMMAND
The DCCH may be congested if:

UEs in the CELL_PCH state frequently initiate the PS service access requests, triggering the frequent transitions from P2F to F2D to D2F to F2P. UEs in the CELL_PCH state frequently receive the paging messages from the CN, triggering the frequent transitions from P2F to F2D to D2F to F2P. When a UE in unacknowledged mode (UM) initiates a F2D/F2P/P2F transition, the RNC periodically retransmits the radio bearer reconfiguration messages on the DCCH, resulting in severer DCCH congestion.
When there is minor or major congestion on the DCCH, the RNC enables P2D transitions for CS service to guarantee the CS service access. The function of P2D transition for CS service access is disabled by default. To enable it, run the SET URRCTRLSWITCH command with the RsvdPara1 parameter set to RSVDBIT1_BIT20-1. As shown in Figure 4-4, the RNC enables P2D transitions for UEs to set up CS services when the DCCH is congested. The cell update confirm message in the P2D transition can be delivered on the CCCH without affecting CS service access or user experience. If the CCCH is congested, the RNC performs CCCH flow control to ensure CS service access. For details, see section 4.3.3 "CCCH Flow Control" DCCH flow control requires UEs of Release 5 or a later version. The RNC performs flow control for PS BE services when there is congestion on the DCCH. Table 4-7 describes the triggering conditions and how DCCH flow control is implemented for PS BE services. Table 4-7 Triggering conditions and actions of DCCH flow control for PS BE services Triggering Conditions The IE "Cell update cause" in the cell update message is "uplink data transmission" or "paging response", and the DCCH Flow Control Actions The P2F transitions are forbidden.
Issue 03 (2012-05-30)
4-9
Triggering Conditions IE "Establishment cause" is not reported. Event 4A Event 4B
DCCH Flow Control Actions
The F2D transitions are forbidden. D2F transitions are replaced with D2Idle transitions.
D2F transitions can be replaced by D2Idle transitions only when the ReservedSwitch0 parameter is set to RESERVED_SWITCH_0_BIT16-1. By default, this parameter is set to RESERVED_SWITCH_0_BIT16-0. You can run the SET UCORRMALGOSWITCH command to modify this parameter value. P2F and F2D transitions of UEs with PS BE services are forbidden only when the PROCESSSWITCH3 parameter is set to FACH_DCCH_CONG_CTRL_SWITCH-1. By default, this parameter is set to FACH_DCCH_CONG_CTRL_SWITCH-0. You can run the SET URRCTRLSWITCH command to modify this parameter value. DCCH flow control stops once the DCCH is no longer congested. The DCCH congestion level is determined by comparing the DCCH buffer size and the preset thresholds, as described in Table 4-5. If the value of the counter VS.FACH.DCCH.CONG.TIME is not 0, the DCCH is congested. If this happens, enable DCCH congestion control and do not disable it once it is enabled. Figure 4-4 shows the UE state transition when DCCH flow control is enabled. Figure 4-4 UE state transition when DCCH flow control is enabled
Issue 03 (2012-05-30)
4-10
For details about UE state transition in normal cases, see the State Transition Feature Parameter Description.
Overload Indication
The counter VS.FACH.DCCH.CONG.TIME indicates the duration of DCCH congestion.
4.3.5 DTCH Flow Control

Principle
The dedicated traffic channel (DTCH) is dedicated to one UE for the transfer of a small quantity of user-plane data. The DTCH may be congested in either of the following situations:

The FACH carries a large number of signaling messages, resulting in insufficient DTCH bandwidth. A large number of UEs in the CELL_FACH state are transmitting data.
DTCH congestion results in an increased call drop rate and affects the experience of PS users transmitting data. To solve this problem, RNC implements DTCH flow control. When the DTCH is congested, RNC triggers P2D transition for UE with PS services. The triggering conditions and how DTCH flow control is implemented are as follows:When a UE with PS services in the CELL_PCH state initiates a cell update, a P2D transition is triggered if the following conditions are met:

The PROCESSSWITCH2 parameter is set to FACH_DTCH_CONGEST_P2D-1. The UE is of Release 5 or a later version. The DTCH is congested but the CCCH and DCCH are not. In the cell update message triggered by PS data transmission, the value of IE "Cell update cause" is "uplink data transmission" or "paging response", and the IE "Establishment cause" is not reported.
DTCH flow control stops once the DTCH is no longer congested. The DTCH congestion level is determined by comparing the DTCH buffer size and the preset thresholds, as described in Table 4-5. Figure 4-5 shows the UE state transition when DTCH flow control is enabled. Figure 4-5 UE state transition when DTCH flow control is enabled
Issue 03 (2012-05-30)
4-11
For details about UE state transition in normal cases, see the State Transition Feature Parameter Description. The P2D transition is disabled by default, and can be enabled by running the SET URRCTRLSWITCH command. The initial access rate of a PS service is 8 kbit/s after the UE has entered the CELL_DCH state.
The rate of PS BE services (non-PTT services) can be limited to 8 kbit/s to prevent excess usage of the DCH resources. This function can be enabled by running the SET UCORRMALGOSWITCH command with the ReservedSwitch1 parameter set to RESERVED_SWITCH_1_BIT6-1. This function is enabled by default. The PS BE service (non-PTT services) can be set up on the HS-DSCH or E-DCH when the call drop rate increases because of a large number of P2D transitions as well as H attempts or DCCC rate increase attempts of users on the DCH. An H attempt refers to a channel shift from DCH to HS-DSCH or E-DCH. This function is disabled by default. To enable it, run the SET UCORRMPARA command with the PerfEnhanceSwitch parameter set to PERFENH_PSTraffic_P2H_SWITCH-1.
If the value of the counter VS.FACH.DTCH.CONG.TIME is not 0, the DTCH is congested. If this happens, enable DTCH congestion control and do not disable it once it is enabled.
Overload Indication
The counter VS.FACH.DTCH.CONG.TIME indicates the duration of DTCH congestion.
4.3.6 FACH Efficiency Boost

RLC Data Transmission Suspension
To reduce the FACH load, the RNC can suspend the RLC data transmission for a certain period of time. If the PROCESSSWITCH3 parameter is set to RNC_F2D_RLC_SUSPEND_SWITCH-1 by running the SET URRCTRLSWITCH command, the RNC will suspend the RLC data transmission when triggering a F2D transition. The RLC data transmission is restored when the F2D transition is complete or the UE returns to the CELL_FACH state. In this way, the user-plane data can be transmitted on the DCH whenever possible and the FACH bandwidth utilization can be improved. This function is disabled by default. If the value of the counter VS.FACH.DTCH.CONG.TIME is not 0, the DTCH is congested. In this case, enable RLC data transmission suspension.
TVM-based P2D Transition

A UE with PS services in the CELL_PCH state initiates a P2D transition based on the Traffic Volume Measurement (TVM), when the following conditions are met:

The PROCESSSWITCH3 parameter is set to RNC_TVM_BASED_P2D_SWITCH-0. The traffic volume from the CN is higher than the 4A threshold; or in the cell update message initiated by the UE, the value of the IE "traffic volume indicator" is TRUE and the value of the IE "Cell update cause" is "uplink data transmission."
TVM indicates 4A measurements in the uplink or measurements on traffic volume from the CN in the downlink. This function enables UEs in the CELL_PCH state to enter the CELL_DCH state when the amount of data to be transmitted exceeds the 4A threshold. This eliminates the need for P2F transitions prior to F2D transitions and thereby improves the FACH resource utilization efficiency. This function is disabled by default. To enable it, run the SET URRCTRLSWITCH command. If the value of the counter VS.FACH.DTCH.CONG.TIME is not 0, the DTCH is congested. In this case, enable TVM-based P2D transition.
5 Flow Control over the Iu Interface

5.1 SCCP Flow Control
5.1.1 Overview
In cases where the bandwidth configured for signaling links over the Iu interface is insufficient or some signaling links over the Iu interface are faulty, signaling link congestion will occur when there are a large number of calls, location updates, or group short messages. Signaling link congestion must be quickly alleviated. Otherwise, it will lead to extended delays or even timeouts in signaling exchanges between UEs and the core network. Severe congestion may cause services to break down. To address these problems, the RNC supports Signaling Connection Control Part (SCCP) flow control, which prevents severe congestion on the signaling link between the RNC and the core network. By default, SCCP flow control is enabled. The RNC uses a scale of 13 levels (0 to 12) to perform SCCP flow control based on service type. When the flow control level changes, the RNC adjusts the signaling traffic over the Iu interface. The higher the flow control level, the more initial UE messages will be discarded. At Level 0, flow control is not performed. The RNC performs SCCP flow control on short message services, paging, location updates and registrations. Of these, short message service has the lowest priority, and location updates and registrations have the highest priority. At a particular flow control level, the RNC proportionally discards the initial UE messages of these services. The proportion is based on service priorities and is not configurable. Of all the messages discarded during flow control, initial UE messages for lower-priority services account for the largest proportions. Assuming that 30 initial UE messages are to be discarded and the proportion of SMS messages discarded to paging messages discarded to location updates discarded is 3:2:1, the numbers of initial UE messages for different services to be discarded are calculated as follows: SMS: 30 x 3/(3 + 2 + 1) = 15 Paging: 30 x 2/(3 + 2 + 1) = 10 Location registrations: 30 x 1/(3 + 2 + 1) = 5 SCCP flow control includes:

Flow control based on Iu signaling load Flow control based on the SCCP setup success rate CN SCCP congestion control
These three flow control functions have their own flow control levels, and the RNC performs SCCP flow control according to the highest among them. Table 5-1 provides details about SCCP flow control. Table 5-1 SCCP flow control Flow Control Method Flow control based on Iu signaling load Switch IUFCSW Criteria for Adjusting Flow Control Levels The SCCP receives an unsolicited SCCP-SSC message from the core network. The SCTP link (in the case of IP transmission) or the SAAL/MTP3 link (in the case of ATM transmission) becomes congested. Flow control based on the SCCP setup success rate FcSwicthByRatioB etweenCCAndCR The ratio of the sum of CC and CREF to CR changes.
Issue 03 (2012-05-30)
5-1
Flow Control Method CN SCCP congestion control
Switch CREFCongFc
Criteria for Adjusting Flow Control Levels The RNC receives a CN CREF congestion indication after sending a CR.
5.1.2 Flow Control Based on Iu Signaling Load

Principle
When the CN SCCP is congested, the RNC receives an SCCP Subsystem-Congested (SCCP-SSC) message from the CN. This message carries the CN SCCP congestion level. The RNC maps the CN SCCP congestion level to an RNC SCCP flow control level. In addition, the RNC monitors the load on the SCTP, SAAL, or MTP3 link in real time and adjusts the flow control level based on the congestion status.
Overload Indication
When a signaling link over the Iu interface is congested, the following alarms and counters are reported: Transmission Mode over Alarms the Iu Interface IP transmission ALM-21542 SCTP Link Congestion Counters
VS.SCTP.CONGESTION.INTERVA L OS.M3UA.Lnk.Cong.Dur OS.MTP3.Lnk.Cong.Dur OS.MTP3.Lnk.ConG VS.SAAL.LnkErr.BufferLoss
ATM transmission
ALM-21501 MTP3 Signaling Link Congestion ALM-21502 MTP3 DSP Congestion ALM-21532 SAAL Link Congestion
The following counters indicate the number of initial UE messages discarded because of flow control over the Iu interface. Counter Description
VS.IU.FlowCtrl.DiscInitDT. Number of initial UE messages in the CS domain that are discarded because CS of flow control over the Iu interface VS.IU.FlowCtrl.Disc.InitDT. Number of initial UE messages in the PS domain that are discarded because PS of flow control over the Iu interface
5.1.3 Flow Control Based on SCCP Setup Success Rate

Principle
In each flow control period, the RNC SCCP checks the number of connection requests (CRs) sent to the CN and the total number of Connection Confirm (CC) and Connection Refused (CREF) messages received from the CN. Each period is 5 seconds long.
Issue 03 (2012-05-30)
5-2
Based on the changes in the ratio of the number of CCs plus the number of CREFs to the number of CRs, the RNC SCCP adjusts the flow control level to ensure that the number of messages received by the CN does not exceed its capabilities. The flow control level is adjusted based on the following criteria:
When (CC+CREF)/CR shows an increasing trend in a flow control period:

Flow Flow
control is lowered by one level if it is weaker than the previous period. control is raised by one level if it is stronger than the previous period. control is raised by one level if it is weaker than the previous period. control is lowered by one level if it is stronger than the previous period.
If (CC+CREF)/CR shows a decreasing trend in a flow control period:

Flow Flow
If the number of CRs sent to the CN from the RNC increases, flow control weakens. If the number of CRs sent from the RNC decreases, flow control strengthens.
Overload Indication
There are no indications when the CN is overloaded by CRs sent from the RNC.
5.1.4 CN SCCP Congestion Control

Principle
When the CN SCCP is congested, the RNC receives a CREF message carrying a congestion indication after sending a CR. The RNC SCCP periodically checks whether it has received CREF messages carrying congestion indications. When it does, it raises the flow control level by one. Otherwise, the RNC lowers the flow control level by one.
Overload Indication
The following counters indicate the number of initial UE messages discarded because of CN SCCP congestion control. Counter VS.IU.FlowCtrl.DiscInitDT.CS VS.IU.FlowCtrl.Disc.InitDT.PS Description Number of initial UE messages in the CS domain that are discarded because of flow control over the Iu interface Number of initial UE messages in the PS domain that are discarded because of flow control over the Iu interface
5.2 Flow Control Triggered by CN RANAP Overload

Principle
When the CN RANAP is overloaded (CPU overload, for example), it sends a RANAP OVERLOAD message to the RNC. Upon receipt of this message, the RNC adjusts the traffic level to the CN over the Iu interface in order to decrease the load on the CN. The IUCTHD parameter in the SET FCSW command is used to configure the percentage of the total traffic the RNC is restricted from sending to the CN. The default value of this parameter is 70, which means the RNC can only send 30% of the total traffic to the CN.
Issue 03 (2012-05-30)
5-3
Flow control triggered by CN RANAP overload is performed on a scale of 21 levels (0 to 20). The lower the level, the more initial UE messages are discarded. The RNC uses two timers when adjusting the flow control level: IntrTmr and IgorTmr, as shown in Table 5-2, where T2 is IntrTmr and T1 is IgorTmr. Table 5-2 Adjusting the flow control level Current Status Idle Event The RNC receives an overload message from the CN. The RNC receives an overload message from the CN. T1 expires. T2 is running. The RNC receives an overload message from the CN. T2 expires. Action

Next Status T1 and T2 are running. T1 and T2 are running. T2 is running. T1 and T2 are running. T2 is running.
Lower flow control by one level. Start T1 and T2.
T1 and T2 are running.
None.
None.

Lower flow control by one level. Start T1 and T2. Restarts T2 if the flow control level is not 20. Resets and stops T1 and T2 if the flow control level is 20.
Raise flow control by one level.
Idle
Figure 5-1 shows how T1 and T2 work. Figure 5-1 T1 and T2
By default, this type of flow control is enabled.
Issue 03 (2012-05-30)
5-4
Overload Indication
When the CN is overloaded, ALM-22301 UMTS CN Overload is reported. The following counters indicate the number of initial UE messages discarded because of flow control over the Iu interface. Counter VS.IU.FlowCtrl.DiscInitDT.CS Description Number of initial UE messages in the CS domain that are discarded because of flow control over the Iu interface
VS.IU.FlowCtrl.Disc.InitDT.PS Number of initial UE messages in the PS domain that are discarded because of flow control over the Iu interface
Issue 03 (2012-05-30)
5-5
6 Service Flow Control
6 Service Flow Control

The RNC and NodeB adopt congestion control algorithms on the user plane over the Iub interface to perform flow control on BE services. This restricts user transmission rates, prevents congestion and packet loss, and optimizes bandwidth utilization over the Iub interface. For more details, see the Transmission Resource Management Feature Parameter Description.
Issue 03 (2012-05-30)
6-1
7 Load Sharing
7 Load Sharing
7.1 Overview
Load sharing is performed on both the control plane and the user plane. CPUSs, DSPs, and other boards can be bound to an MPU to form a logical subrack. The subracks mentioned in this chapter are all logical subracks. Each CPUS controls some NodeBs and their cells. The CPUS performs signaling processing for service requests from the UEs under these cells, and the UEs are admitted to the CPUS. The MPU in each subrack keeps a record of the user-plane load on the current subrack and shares this information with the MPUs in other subracks. When a service request arrives and the controlling CPUS is heavily loaded, the CPUS forwards the request to the MPU in the current subrack. The MPU selects the CPUS with the lightest load for signaling processing. The selected CPUS may be in the current subrack or another subrack. Figure 7-1 shows how load sharing works between two subracks. Figure 7-1 Load sharing between two subracks
When a UE attempts to access the network and user-plane resources need to be allocated to the UE, the controlling CPUS sends a resource request to the MPU in the current subrack. The MPU attempts to allocate the user-plane resources of the current subrack to the UE. If this attempt fails, the MPU forwards the resource request to the MPU in the subrack with the lightest load. User-plane resources in this chapter refer to DSP resources. Figure 7-2 shows resource management on the user plane.
Issue 03 (2012-05-30)
7-1
7 Load Sharing
Figure 7-2 Resource management on the user plane
If the CPU usage of a CPUS is 90% or higher, the CPUS discards all service requests except those for emergency calls. Load sharing does not work for the CPUS. When the CPU usage of an MPU is 95% or higher, the MPU discards the following requests to avoid resetting:

Resource requests from each UE, for example, requests for DSP resources and transmission resources Load sharing requests
When this occurs, load sharing does not work.
7.2 Load Sharing on the Control Plane

7.2.1 Procedure for Load Sharing on the Control Plane
When a CPUS receives a service request, the controlling CPUS determines whether to perform load sharing. If so, the CPUS follows the procedure described in Figure 7-3.
Issue 03 (2012-05-30)
7-2
7 Load Sharing
Figure 7-3 Load sharing on the control plane
Details are as follows: Step 1 The CPUS receives a service request. Step 2 Based on the current load, the CPUS determines whether to perform load sharing. For more details, see section 7.2.2 "Service Request Processing by a CPUS."
If If
load sharing is to be performed, Step 3 starts. load sharing is not to be performed, the CPUS processes the request, and the procedure ends.
Issue 03 (2012-05-30)
7-3
7 Load Sharing
Step 3 The CPUS forwards the request to the MPU in the current subrack. Step 4 Upon receipt of the load sharing request from the CPUS, the MPU checks the control-plane load on all subracks in the RNC.
If the control-plane load on the current subrack minus CtrlPlnSharingOutOffset is higher than the control-plane load on any other subrack, load sharing is performed between subracks. The MPU forwards the request to the MPU in the subrack with the lightest load on the control plane, which is known as the target MPU. Following the criteria described in Table 7-1, the target MPU searches for all CPUSs that can take up the request.
If If
the target MPU can find such CPUSs, it selects a CPUS with the lightest CPU load to process the request. the target MPU cannot find such a CPUS, load sharing is performed within the current subrack.
If the control-plane load on the current subrack minus CtrlPlnSharingOutOffset is lower than or equal to the control-plane load on any other subrack, load sharing is performed within the current subrack. Following the criteria described in Table 7-1, the MPU in the current subrack attempts to find CPUSs that can take up the request from within the current subrack.
If If
the target MPU can find such CPUSs, it selects a CPUS with the lightest CPU load to process the request. the MPU cannot find such a CPUS, service access is rejected.
The control-plane load on a subrack is the average CPU usage of the CPUSs managed by the MPU. Load sharing is yielding noticeable effects if the load is balanced across the CPUs of the CPUSs. To check the CPU load of the CPUSs, run the DSP CPUUSAGE command. If the load is not balanced, consult Huawei engineers to adjust the thresholds for load sharing or adjust the configuration of XPUs in the subracks.
7.2.2 Service Request Processing by a CPUS

Generally, CPUSs are not heavily loaded. When a user initiates a service request, the controlling CPUS processes it. If the controlling CPUS is heavily loaded, load sharing is performed and the request is forwarded to a lightly loaded CPUS. Service requests cannot be forwarded to an overloaded CPUS. The CPUS load is indicated by the CPU load (CPU usage) and CAPS. The RNC considers a CPUS overloaded when any of the following conditions is met:

The CPU load is low and the CAPS is high. The CPU load is high and the CAPS is low. The CPU load is greater than or equal to the CPU overload threshold, which cannot be configured.
Based on the CPUS load, the RNC defines three CPUS states, as shown in Figure 7-4.
Issue 03 (2012-05-30)
7-4
7 Load Sharing
Figure 7-4 CPUS load and states
The state of a CPUS determines how it processes service requests, as described in Table 7-1. Table 7-1 Service request processing by CPUS state CPUS State Definition State I The CPUS is lightly loaded. The CPUS load is considered light when both the following are true:

Processing The CPUS directly processes new and forwarded requests.
CPU load CtrlPlnSharingOutThd CAPS MaxCAPSLowLoad
State II
The CPUS is heavily loaded. The CPUS load is The CPUS forwards all new requests to considered heavy when both the following are the MPU for load sharing. true: The MPUs can forward requests to the CtrlPlnSharingOutThd < CPU load < CPU CPUS. overload threshold
CAPS MaxCAPSMidLoad
State III
The CPUS is overloaded. The CPUS is The CPUS forwards all new requests to considered overloaded when any of the following the MPU for load sharing. is true: The MPUs cannot forward requests to

CPU overload threshold < CPU load CPU load <= CtrlPlnSharingOutThd, and MaxCAPSLowLoad < CAPS CtrlPlnSharingOutThd < CPU load < CPU overload threshold, and MaxCAPSMidLoad < CAPS
the CPUS.
Issue 03 (2012-05-30)
7-5
7 Load Sharing
7.3 Load Sharing on the User Plane

7.3.1 Overview
The RNC measures the following aspects of the DSP processing capability:

GBR capability of the DSP (DSP resources used for service access procedures are measured as GBRs) Processing capability of the DSP CPU
Accordingly, the RNC measures the user-plane load of a subrack with the following:

Total GBRs consumed by admitted services on the DSPs (GBR consumption) Average CPU usage of all DSP CPUs in a subrack (CPU load)
The remaining GBRs of a subrack refer to the total DSP GBR capabilities of the subrack minus GBR consumption in the subrack. The remaining CPU processing capability of a subrack is the average CPU processing capability of all DSPs in the subrack minus the CPU load.
7.3.2 Procedure for Load Sharing on the User Plane

When user-plane resources need to be allocated to a new user, the MPU in the current subrack determines whether to allocate resources in the current subrack or forward the resource request to another subrack based on the GBR consumption and CPU load. Figure 7-5 shows the procedure for load sharing on the user plane.
Issue 03 (2012-05-30)
7-6
7 Load Sharing
Figure 7-5 Load sharing on the user plane
Step 1 The MPU receives a resource allocation request from the CPUS. Step 2 The MPU uses the user-plane load on the current subrack to determine whether to perform load sharing.
If
GBR consumption in the current subrack is equal to or lower than UserPlnSharingOutThd and the CPU load on the current subrack is less than or equal to UserPlnCpuSharingOutThd, the MPU in the current subrack attempts to allocate user-plane resources to the user in the current subrack. Substep 1 starts.
Issue 03 (2012-05-30)
7-7

Otherwise,
7 Load Sharing
the MPU forwards the request to the MPU in the subrack with the lightest load, known as the target subrack. The MPU of this subrack will determine whether load sharing can be performed. Step 3 starts.
1. The MPU in the current subrack determines whether resources can be allocated. If... The MPU finds in the current subrack the DSP with the lowest GBR consumption Then... The MPU selects this DSP as the target DSP, and substep 2 starts.
Note: If this DSP has no GBR resources to consume and has a CPU load below DSPRestrainCpuThd, The MPU in the current subrack also selects this DSP as the target DSP.
The MPU cannot find such a DSP
The RNC rejects the service access.
2. The target DSP allocates user-plane resources to the user. Step 3 The target MPU determines whether load sharing can be performed. 1. If either of the following conditions is met, substep 2 starts:
GBR CPU
consumption in the current subrack > UserPlnSharingOutThd, and remaining GBRs in the current subrack x (1 + UserPlnSharingOutOffset) < remaining GBRs in the target subrack load in the current subrack > UserPlnCpuSharingOutThd, and the remaining CPU processing capability in the current subrack x (1 + UserPlnCpuSharingOutOffset) < remaining CPU processing capability in the target subrack. If neither of these conditions is met, load sharing fails, and the MPU in the current subrack selects a DSP from the current subrack for resource allocation.
2. The MPU in the target subrack determines whether resources can be allocated. If... The MPU in the target subrack finds in the target subrack a DSP whose GBR consumption is the lowest Then... This DSP is selected as the target DSP, and substep 3 starts.
Note: If this DSP has no GBR resources to consume and has a CPU load below DSPRestrainCpuThd, The MPU in the target subrack also selects this DSP as the target DSP.
The MPU in the target subrack cannot find such a DSP
The RNC rejects the service access.
3. The target DSP allocates user-plane resources to the user. The SET UUSERPLNSHAREPARA command configures thresholds for load sharing on the user plane. Load sharing is considered yielding noticeable effects if the load is balanced across the CPUs of the MPUs. To check the CPU load on an MPU, run the DSP CPUUSAGE command. If the load is not balanced, consult Huawei engineers to adjust the thresholds for load sharing or adjust the configuration of DPUs in the subracks.
Issue 03 (2012-05-30)
7-8
7 Load Sharing
When all DSPs under the RNC have been heavily loaded for an extended period of time, the RNC reports ALM-22305 Resource overload on the user plane. This indicates DSP resources are insufficient and a capacity expansion is recommended.
Issue 03 (2012-05-30)
7-9
8 Engineering Guidelines
8.1 Access Control and Domain-Specific Access Control
8.1.1 Factors That Affect Access control and Domain-Specific Access Control
Whether access control or DSAC yields noticeable effects depends on the following factors:
How the operator defines users If SIM cards are evenly distributed among ACs before being sold, access control or DSAC can yield noticeable effects. If SIM cards are unevenly or incorrectly distributed among ACs, do not enable access control or DSAC because it may fail to yield noticeable effects.
UE compliance DSAC is applicable only to UEs that comply with 3GPP Release 6 or later. Access control is applicable to all UEs.
After access control or DSAC is enabled, run the DSP UCELLACR or DSP UCELLDSAC command, respectively, to check the running status. To find out whether access control is creating noticeable effects, check the value of the counter VS.RRC.AttConnEstab.Msg. Assuming AcRstrctPercent is set to 20%, access control is yielding noticeable effects if the value of this counter is 20% less than its value before access control was enabled.
8.1.2 Configuration Principles and Suggestions

Enable DSAC PS ahead of mass gatherings and disable it afterwards. Enable access control or DSAC PS according to the values of the related counters.
Check RRC If If If
the RRC setup success rate of the cell. If the value of this KPI is significantly lower than it was on the same day last week, check the value of VS.RRC.FailConnEstab.NoReply. setup success rate = RRC.SuccConnEstab.sum/VS.RRC.AttConnEstab.Sum VS.RRC.FailConnEstab.NoReply is significantly higher than it was on the same day last week, check the value of VS.MeanRTWP. VS.MeanRTWP is significantly higher than it was on the same day last week, check the value of VS.RRC.AttConnEstab.Sum. VS.RRC.AttConnEstab.Sum is significantly higher than it was the same day last week, the low RRC setup success rate has been caused by heavy traffic. In this case, enable DSAC PS to alleviate the traffic impact. the RRC setup success rate is still low, enable access control.
If
To enable DSAC PS, set PsRestriction to TRUE and AcRestriction to the number of ACs on which DSAC is performed. To enable access control, set AcRstrctSwitch to ON and AcRstrctPercent to the number of ACs on which access control is performed. After access control or DSAC PS is enabled, observe the value of VS.RRC.AttConnEstab.Sum, which indicates the number of RRC setup attempts. If the value of this counter keeps decreasing, the network is not subject to traffic impacts anymore and you can disable access control and DSAC PS.
Issue 03 (2012-05-30)
8-1
8.1.3 Performance Optimization

If access control or DSAC fails to yield the expected effects, change the number of ACs on which access control or DSAC is performed. It is recommended that this value be adjusted in steps of 10%.
8.1.4 Key Parameter Settings

Increasing the number of ACs on which access control or DSAC is performed decreases the number of RRC setup requests and increases the RRC setup success rate. Decreasing the number of ACs on which access control or DSAC is performed increases the number of RRC setup requests and decreases the RRC setup success rate.
8.2 Queue-based RRC Shaping

8.2.1 Factors That Affect Queue-based RRC Shaping
During mass gatherings, CPU usage soars and fluctuates with changes in traffic volume. When CPU usage exceeds the critical threshold (90%), the RRC and RAB setup success rates decrease. In this case, enable queue-based RRC shaping, which stabilizes the influx of RRC connection requests into the system. This stabilizes the CPU usage and increases RRC and RAC setup success rates. Once queue-based RRC shaping is enabled, the load-sharing threshold and the parameters for other flow control functions that affect the CPU usage (such as CAPS control) need to be adjusted.

Enable queue-based RRC shaping ahead of mass gatherings. At the same time, increase the values of the parameters for flow control functions that affect the CPU usage. Contact Huawei technical support to determine a detailed plan.
8.3 CAPS Control

8.3.1 Factors That Affect CAPS Control
The effect of CAPS control depends on the accuracy of the estimation of the allowed number of RRC connection requests in the cell. If the allowed number of RRC connection requests is too large, CAPS control cannot yield noticeable effects. If the allowed number of RRC connection requests is too small, resources may not be fully utilized. The SET UCALLSHOCKCTRL command configures the allowed number of RRC connection requests per second in a cell. Contact Huawei technical support to adjust this number.

Check the value of VS.RRC.AttConnEstab.Sum. If the value is significantly higher than it was on the same day last week and the service setup success rate is low, it is recommended that CAPS control be enabled. CS service setup success rate = (VS.RAB.SuccEstabCS.Conv + VS.RAB.SuccEstabCS.Str)/(VS.RAB.AttEstabCS.Conv + VS.RAB.AttEstabCS.Str) PS service setup success rate = (VS.RAB.SuccEstabPS.Conv + VS.RAB.SuccEstabPS.Str + VS.RAB.SuccEstabPS.Int + VS.RAB.SuccEstabPS.Bkg)/(VS.RAB.AttEstabPS.Conv + VS.RAB.AttEstabPS.Str + VS.RAB.AttEstabPS.Int + VS.RAB.AttEstabPS.Bkg)
Issue 03 (2012-05-30)
8-2
9 Parameters
8.3.3 Performance Optimization

Check the service-setup success rate of the cell. If the service-setup success rate is low, run the SET UCALLSHOCKCTRL command to reduce the allowed number of RRC connection requests per second in the cell. The minimum number is 2. If the service-setup success rate is high, run the SET UCALLSHOCKCTRL command. Table 9-1 Parameter description Parameter ID ACCTHD NE MML Command Description
Parameters
BSC6900 SET Meaning:Access packet queue usage threshold. FCMSGQTHD(Optional When the average packet queue usage of sliding ) windows exceeds the threshold, AC flow control is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:80
ACCTHD
BSC6900 SET Meaning:Access flow control threshold. When the FCCPUTHD(Optional) average CPU usage of sliding windows exceeds the threshold, AC flow control is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:80
AcIntervalOfCell BSC6900 SET Meaning:Interval of automatic access classes UACALGO(Mandatory) restriction between cells. When a subsystem of an RNC performs access classes restriction on cells managed by this subsystem, it selects the first cell at random. After waiting for the time specified in this parameter, the subsystem selects the second cell and the first cell is still with access classes restriction. The process lasts until all the cells are going through access classes restriction. For detailed information of this parameter, refer to 3GPP TS 22.011. GUI Value Range:1~36000 Actual Value Range:10~360000 Unit:10ms Default Value:50 AcRestriction BSC6900 ADD Meaning:Specifies the access classes that are UCELLDSACMANUALP
Issue 03 (2012-05-30)
9-3
9 Parameters
Parameter ID
NE
MML Command ARA(Mandatory)
Description restricted according to the fixed restriction mode.
MOD GUI Value Range:AC0(Access Class 0 UCELLDSACMANUALP Restriction), AC1(Access Class 1 Restriction), ARA(Mandatory) AC2(Access Class 2 Restriction), AC3(Access Class 3 Restriction), AC4(Access Class 4 Restriction), AC5(Access Class 5 Restriction), AC6(Access Class 6 Restriction), AC7(Access Class 7 Restriction), AC8(Access Class 8 Restriction), AC9(Access Class 9 Restriction), AC10(Access Class 10 Restriction), AC11(Access Class 11 Restriction), AC12(Access Class 12 Restriction), AC13(Access Class 13 Restriction), AC14(Access Class 14 Restriction), AC15(Access Class 15 Restriction) Actual Value Range:AC0, AC1, AC2, AC3, AC4, AC5, AC6, AC7, AC8, AC9, AC10, AC11, AC12, AC13, AC14, AC15 Unit:None Default Value:None AcRstrctInterval BSC6900 SET Meaning:Interval of access classes restriction. Len UACALGO(Mandatory) When a cell performs access classes restriction, it selects some access classes and after the restriction on these access classes lasts for the time specified in this parameter, the access classes restriction is released and the cell selects other access classes for restriction. GUI Value Range:6~3600 Actual Value Range:6~3600 Unit:s Default Value:10 AcRstrctPercent BSC6900 SET Meaning:Access restriction ratio. When a cell UACALGO(Mandatory) performs access classes restriction, you can select some access classes from AC0 to AC9 based on the ratio specified in this parameter and perform access classes restriction on the selected access classes. After access classes restriction goes on for AcRstrctIntervalLen, the original access classes restriction is released and other access classes of the local cell are selected for access classes restriction based on the ratio specified in this parameter. GUI Value Range:1~10 Actual Value Range:0.1~1
Issue 03 (2012-05-30)
9-4
9 Parameters
Parameter ID
NE
MML Command
Description Unit:0.1 Default Value:2
AcRstrctSwitch BSC6900 SET UACALGO(Optional)
Meaning:OFF indicates that the AC algorithm is automatically disabled. ON indicates that the AC algorithm is automatically enabled. GUI Value Range:OFF, ON Actual Value Range:OFF, ON Unit:None Default Value:OFF
ACRTHD
BSC6900 SET Meaning:Access packet recovery threshold. When FCMSGQTHD(Optional the average packet queue usage of sliding windows ) is lower than the threshold, AC flow control is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70
ACRTHD
BSC6900 SET Meaning:Access flow control recovery threshold. FCCPUTHD(Optional) When the average CPU usage of sliding windows is lower than the threshold, AC flow control is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70
ACSW
BSC6900 SET FCSW(Optional)
Meaning:Whether to control AC flow GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
CallShockCtrlS BSC6900 SET Meaning:The parameter specifies whether to witch UCALLSHOCKCTRL(O perform Call Attempt Per Second (CAPS) control ptional) for the number of RRC connection requests at SPU subsystem level, NodeB level, or cell level.
Issue 03 (2012-05-30)
9-5
9 Parameters
Parameter ID
NE
MML Command
Description SYS_LEVEL indicates that the RNC will perform flow control for the RRC connection requests at SPU subsystem level.This switch is configurable in the current version. The RNC, however, does not use this switch any longer. Later versions will not support this switch. Therefore, users are not advised to use this switch. NODEB_LEVEL indicates that the RNC will perform flow control for the RRC connection requests at NodeB level. CELL_LEVEL indicates that the RNC will perform flow control for the RRC connection requests at cell level. GUI Value Range:SYS_LEVEL(SYS_LEVEL), NODEB_LEVEL(NODEB_LEVEL), CELL_LEVEL(CELL_LEVEL) Actual Value Range:SYS_LEVEL, NODEB_LEVEL, CELL_LEVEL Unit:None Default Value:None
CallShockJudge BSC6900 SET Meaning:The parameter specifies the period of Period UCALLSHOCKCTRL(O entering flow control at SPU subsystem level, ptional) NodeB level, or cell level. In the period, if the number of RRC connection requests that the SPU subsystem, NodeB, or cell receives exceed relative trigger threshold (the threshold can be set by "SysTotalRrcNumThd", "NBTotalRrcNumThd", or "CellTotalRrcNumThd"), RNC will perform flow control for the RRC establishment request. GUI Value Range:1~5 Actual Value Range:1~5 Unit:s Default Value:3 CBSSW BSC6900 SET FCSW(Optional) Meaning:Whether to control CBS flow GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
Issue 03 (2012-05-30)
9-6
9 Parameters
Parameter ID
NE
MML Command
Description
CCCHCongClea BSC6900 SET Meaning:This parameter specifies the threshold for rThd UDPUCFGDATA(Option FACH CCCH congestion clear. al) GUI Value Range:1~80 Actual Value Range:1~80 Unit:None Default Value:30 CCCHCongThd BSC6900 SET Meaning:This parameter specifies the threshold for UDPUCFGDATA(Option FACH CCCH congestion. al) GUI Value Range:1~80 Actual Value Range:1~80 Unit:None Default Value:60 CellAmrRrcNum BSC6900 SET Meaning:The parameter specifies the number of UCALLSHOCKCTRL(O RRC connection requests per second for ptional) originating conversational call at cell level. This parameter is configurable in the current version. The RNC, however, does not use this parameter any longer. Later versions will not support this parameter. Therefore, users are not advised to use this parameter. GUI Value Range:1~100 Actual Value Range:1~100 Unit:None Default Value:15 CellHighPriRrcN BSC6900 SET Meaning:The parameter specifies the number of um UCALLSHOCKCTRL(O RRC connection requests per second for ptional) registration and inter-RAT cell reselection at cell level. This parameter is configurable in the current version. The RNC, however, does not use this parameter any longer. Later versions will not support this parameter. Therefore, users are not advised to use this parameter. GUI Value Range:1~100 Actual Value Range:1~100 Unit:None
Issue 03 (2012-05-30)
9-7
9 Parameters
Parameter ID
NE
MML Command
Description Default Value:15
CellTotalRrcNu BSC6900 SET Meaning:The parameter specifies the threshold of mThd UCALLSHOCKCTRL(O entering flow control for RRC connection requests ptional) at cell level.
During the call shock judgment period (CallShockJudgePeriod), when the number of RRC connection requests exceed the value of the parameter, RNC will perform flow control. The flow control strategies for RRC connection requests are as follows: The number of RRC connection requests that will be accepted by the RNC per second within a cell equals the value of this parameter divided by the value of the parameter Call Shock Judge Period time length. If the number of RRC connection requests received by the RNC per second within a cell exceeds the limit, the RNC performs flow control based on service priorities. GUI Value Range:1~100 Actual Value Range:1~100 Unit:None Default Value:45 CELLURASW BSC6900 SET FCSW(Optional) Meaning:Whether to control cell updates GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON CPAGECTHD BSC6900 SET Meaning:CPU usage threshold for paging flow FCCPUTHD(Optional) control over real-time services. BE services uses the same paging flow control thresholds as SS and LCS to ensure the paging success rate of real-time services. When the average CPU usage within several sliding windows reaches or exceeds "Call page restore threshold", the linear paging flow control on real-time services is started. When the average CPU usage within several sliding windows reaches or exceeds "Call page control threshold", the 100% paging flow control on real-time services is started.
Issue 03 (2012-05-30)
9-8
9 Parameters
Parameter ID
NE
MML Command
Description GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:90
CPAGERTHD
BSC6900 SET Meaning:CPU usage threshold for paging control FCCPUTHD(Optional) over real-time services. BE services uses the same paging flow control thresholds as SS and LCS to ensure the paging success rate of real-time services. When the average CPU usage within several sliding windows reaches or exceeds "Call page restore threshold", the linear paging flow control on real-time services is started. When the average CPU usage within several sliding windows is lower than "Call page restore threshold", paging control over real-time services is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:75
CREFCongFc
BSC6900 SET Meaning:Whether to enable Connection Refused TNSOFTPARA(Optional (CREF) congestion flow control. If this switch is ) turned on, flow control is started automatically if the SCCP receives a CREF frame with a rejection cause of congestion. GUI Value Range:OFF(OFF), ON(ON) Actual Value Range:OFF, ON Unit:None Default Value:ON
CRRCCONNCC BSC6900 SET Meaning:CPU usage threshold for stopping load PUTHD SHARETHD(Optional) sharing on call service RRC connection setup requests. When the CPU usage of an XPU subsystem reaches this threshold or CtrlPlnSharingOutThd, whichever is smaller, later call service RRC connection setup requests will be carried by other XPU subsystems. CtrlPlnSharingOutThd is set by using the command "SET UCTRLPLNSHAREPARA". If the CPU usage of all candidate XPU subsystems exceeds this threshold, flow control on call service RRC connection setup requests is triggered. GUI Value Range:30~100
Issue 03 (2012-05-30)
9-9
9 Parameters
Parameter ID
NE
MML Command
Description Actual Value Range:30~100 Unit:% Default Value:85
CRRCCONNCM BSC6900 SET Meaning:Packet usage threshold for stopping load SGTHD SHARETHD(Optional) sharing on call service RRC connection setup requests. When the packet usage of an XPU subsystem reaches this threshold, later call service packets will be carried by other XPU subsystems. If the packet usage of all candidate XPU subsystems exceeds this threshold, flow control on call service RRC connection setup request packets is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:75 CRRCCONNRC BSC6900 SET Meaning:CPU usage threshold for recoverying load PUTHD SHARETHD(Optional) sharing on call service RRC connection setup requests. If the CPU usage of an XPU subsystem is lower than this threshold, this XPU subsystem is the candidate subsystem for the load sharing on call service RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:75 CRRCCONNRM BSC6900 SET Meaning:Packet usage threshold for recoverying SGTHD SHARETHD(Optional) load sharing on call service RRC connection setup requests. When the packet usage of an XPU subsystem is lower than this threshold, this XPU subsystem is a candidate subsystem for load sharing on call service RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:65 CTHD BSC6900 SET Meaning:Critical threshold for CPU usage. When all FCCPUTHD(Optional) the CPU usages in "fast judgement window" reach
Issue 03 (2012-05-30)
9-10
9 Parameters
Parameter ID
NE
MML Command
Description or exceed this threshold, all active flow control mechanisms start to work immediately. Otherwise, the corresponding flow control mechanism is used. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:95
CTHD
BSC6900 SET Meaning:Critical threshold of packet queue usage. FCMSGQTHD(Optional When the packet queue usage reaches or exceeds ) the threshold, all active flow control functions are implemented. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:95
CtrlPlnSharingO BSC6900 SET Meaning:The sharing offset should be added to the utOffset UCTRLPLNSHAREPAR target subrack or subsystem. This parameter is A(Optional) used for preferable selection of the homing subrack and homing subsystem during call forwarding. GUI Value Range:1~10 Actual Value Range:0.01~0.1 Unit:% Default Value:5 CtrlPlnSharingO BSC6900 SET Meaning:Forwarding threshold of control plane load utThd UCTRLPLNSHAREPAR sharing. When the CPU usage is between the A(Optional) sharing threshold and overload threshold, and call number in each second reaches "Sharing out capability middle load", new arrival call attempts will be shared out to other SPU subsystem. GUI Value Range:0~100 Actual Value Range:0~1 Unit:% Default Value:50 DSPRestrainCp BSC6900 SET Meaning:The parameter is added to stop SPU from uThd UUSERPLNSHAREPA assigning users to a DSP whose CPU usage has RA(Optional) exceeded this threshold.
Issue 03 (2012-05-30)
9-11
9 Parameters
Parameter ID
NE
MML Command
Description GUI Value Range:0~100 Actual Value Range:0~100 Unit:% Default Value:0
FachCongClear BSC6900 SET Meaning:Threshold for clearing FACH congestion. Thd UDPUCFGDATA(Option GUI Value Range:0~200 al) Actual Value Range:{0~200} Unit:None Default Value:10 FachCongThd BSC6900 SET Meaning:Threshold for reporting FACH congestion. UDPUCFGDATA(Option GUI Value Range:1~200 al) Actual Value Range:{1~200} Unit:None Default Value:60 FcOnItfBrd BSC6900 SET Meaning:Whether to enable interface board flow TNSOFTPARA(Optional control. ) If this switch is turned on, the BSC6900 adjusts the traffic load on the interface board according to the CPU usage of the interface board. GUI Value Range:OFF(OFF), ON(ON) Actual Value Range:OFF, ON Unit:None Default Value:ON FCSW BSC6900 SET FCSW(Mandatory) Meaning:Main switch for the flow control on a subsystem. Other flow control switches can take effect only when this switch is set to ON. GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON FcSwicthByRati BSC6900 SET Meaning:Whether to enable Connection oBetweenCCAn TNSOFTPARA(Optional Confirm/Connection Request (CC/CR) flow control. The SCCP periodically measures the number of
Issue 03 (2012-05-30)
9-12
9 Parameters
Parameter ID dCR
NE
MML Command )
Description connection setup requests that are sent and received by the BSC6900 for each signaling point. If this switch is turned on, the BSC6900 starts flow control if the proportion of the connection setup responses to the connection setup requests is lower than the flow control threshold. GUI Value Range:OFF(OFF), ON(ON) Actual Value Range:OFF, ON Unit:None Default Value:ON
FDWINDOW
BSC6900 SET Meaning:Number of CPU usage sampling times FCCPUTHD(Optional) involved in fast judgment. The value of this parameter must be smaller than or equal to half of the value of "Filter window". "Fast judgment window" is applied to control the flow in the case that the CPU usage is too high in a short time. After "fast judgment window" is applied, the system compares the CPU usage in a short period of time before the current time with Critical threshold. If all CPU usages in the "fast judgment window" reach or exceed Critical threshold, all active flow control mechanisms start to work immediately. GUI Value Range:1~1000 Actual Value Range:1~1000 Unit:None Default Value:4
IgorTmr
BSC6900 SET Meaning:CN flow control timer (short). The UIUTIMERANDNUM(O OVERLOAD message received repeatedly in this ptional) period will be discarded. GUI Value Range:5000~30000 Actual Value Range:5000~30000 Unit:ms Default Value:20000
IntrTmr
BSC6900 SET Meaning:CN flow control timer (long). If the UIUTIMERANDNUM(O OVERLOAD message is not received in this period, ptional) the traffic volume will be increased by a degree. GUI Value Range:15000~120000 Actual Value Range:15000~120000
Issue 03 (2012-05-30)
9-13
9 Parameters
Parameter ID
NE
MML Command
Description Unit:ms Default Value:60000
IUCTHD
Meaning:Maximum traffic rate for restriction in the case of congestion on the IU interface. This parameter is valid only when "Board Class" is "XPU". GUI Value Range:0~100 Actual Value Range:0~100 Unit:None Default Value:70
IUFCSW
Meaning:Whether to control signaling traffic on the IU interface GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
IURDLSW
Meaning:Whether to control the traffic on the Iur downlink GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
IURGSW
Meaning:Whether to control traffic on the Iur-g interface GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
IURULSW
Meaning:Whether to control the traffic on the Iur uplink GUI Value Range:ON, OFF Actual Value Range:ON, OFF
Issue 03 (2012-05-30)
9-14
9 Parameters
Parameter ID
NE
MML Command
Description Unit:None Default Value:ON
LRRCCONNCC BSC6900 SET Meaning:CPU usage threshold for stopping load PUTHD SHARETHD(Optional) sharing on location service RRC connection setup requests. When the CPU usage of an XPU subsystem reaches this threshold or CtrlPlnSharingOutThd, whichever is smaller, later location service RRC connection setup requests will be carried by other XPU subsystems. CtrlPlnSharingOutThd is set by using the command "SET UCTRLPLNSHAREPARA". If the CPU usage of all candidate XPU subsystems exceeds this threshold, flow control on location service RRC connection setup requests is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:90 LRRCCONNCM BSC6900 SET Meaning:Packet usage threshold for stopping load SGTHD SHARETHD(Optional) sharing on location service RRC connection setup requests. When the packet usage of an XPU subsystem reaches this threshold, later call service packets will be carried by other XPU subsystems. If the packet usage of all candidate XPU subsystems exceeds this threshold, flow control on location service RRC connection setup request packets is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:75 LRRCCONNRC BSC6900 SET Meaning:CPU usage threshold for recoverying load PUTHD SHARETHD(Optional) sharing on location service RRC connection setup requests. If the CPU usage of an XPU subsystem is lower than this threshold, this XPU subsystem is the candidate subsystem for load sharing on location service RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:%
Issue 03 (2012-05-30)
9-15
9 Parameters
Parameter ID
NE
MML Command
Description Default Value:80
LRRCCONNRM BSC6900 SET Meaning:Packet usage threshold for recoverying SGTHD SHARETHD(Optional) load sharing on location service RRC connection setup requests. When the packet usage of an XPU subsystem is lower than this threshold, this XPU subsystem is a candidate subsystem for load sharing on location service RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:65 MaxCAPSLowL BSC6900 SET Meaning:Maximum numbers of incoming calls in oad UCTRLPLNSHAREPAR one second when the load is lower than the A(Optional) forwarding threshold. When the CPU usage is lower than the sharing out threshold and overload threshold, and call numbers in each second reach the threshold, new arrival call attempts will be shared out to other SPU subsystem and none will be shared in this SPU subsystem. GUI Value Range:0~255 Actual Value Range:0~255 Unit:None Default Value:150 MaxCAPSMidLo BSC6900 SET Meaning:Maximum numbers of incoming calls in ad UCTRLPLNSHAREPAR one second when the load exceeds the forwarding A(Optional) threshold. When the CPU usage is between the sharing out threshold and overload threshold, and call number in one second reaches the threshold, new arrival call attempts will be shared out to other SPU subsystem and none will be shared in this SPU subsystem. GUI Value Range:0~255 Actual Value Range:0~255 Unit:None Default Value:100 MRFCSW BSC6900 SET FCSW(Optional) Meaning:Whether to control MR flow GUI Value Range:ON, OFF
Issue 03 (2012-05-30)
9-16
9 Parameters
Parameter ID
NE
MML Command
Description Actual Value Range:ON, OFF Unit:None Default Value:ON
NBAmrRrcNum BSC6900 SET Meaning:The parameter specifies the number of UCALLSHOCKCTRL(O RRC connection requests per second for ptional) originating conversational call at NodeB level. This parameter is configurable in the current version. The RNC, however, does not use this parameter any longer. Later versions will not support this parameter. Therefore, users are not advised to use this parameter. GUI Value Range:1~200 Actual Value Range:1~200 Unit:None Default Value:20 NBHighPriRrcN BSC6900 SET Meaning:The parameter specifies the number of um UCALLSHOCKCTRL(O RRC connection requests per second for ptional) registration and inter-RAT cell reselection at NodeB level. This parameter is configurable in the current version. The RNC, however, does not use this parameter any longer. Later versions will not support this parameter. Therefore, users are not advised to use this parameter. GUI Value Range:1~200 Actual Value Range:1~200 Unit:None Default Value:20 NBTotalRrcNum BSC6900 SET Meaning:The parameter specifies the threshold of Thd UCALLSHOCKCTRL(O entering flow control for RRC connection requests ptional) at NodeB level.
During the call shock judgment period (CallShockJudgePeriod), when the number of RRC connection requests exceed the value of the parameter, RNC will perform flow control. The flow control strategies for RRC connection requests are as follows: The number of RRC connection requests that will
9 Parameters
Parameter ID
NE
MML Command
Description be accepted by the RNC per second within a base station equals the value of this parameter divided by the value of the parameter Call Shock Judge Period time length. If the number of RRC connection requests that have been received by the RNC per second within a base station exceeds the limit, the RNC performs flow control based on service priorities. Note: The actual value of this threshold is five times the configured value. GUI Value Range:1~200 Actual Value Range:1~1000, Step: 5 Unit:None Default Value:60
PAGECTHD
BSC6900 SET Meaning:Packet queue usage threshold for paging FCMSGQTHD(Optional flow control. When the average packet usage within ) several sliding windows reaches or exceeds "Paging restore threshold", linear flow control is started on paging messages. When the average packet usage within several sliding windows reaches or exceeds "Paging control threshold", 100% flow control is started on paging messages. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70
PAGERTHD
BSC6900 SET Meaning:Packet queue usage threshold for paging FCMSGQTHD(Optional flow control. When the average packet usage within ) several sliding windows reaches or exceeds "Paging restore threshold", linear flow control is started on paging messages. When the average packet usage within several sliding windows is lower than "Paging restore threshold", paging flow control is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:60
PAGESW
Meaning:Whether to control paging flow
Issue 03 (2012-05-30)
9-18
9 Parameters
Parameter ID
NE
MML Command
Description GUI Value Range:ON, OFF Actual Value Range:ON, OFF Unit:None Default Value:ON
PagingSwitch
BSC6900 SET Meaning:Paging preemption switch. When the UDPUCFGDATA(Option switch is turned on, the paging preemption function al) is supported. GUI Value Range:OFF(OFF), ON(ON) Actual Value Range:OFF, ON Unit:None Default Value:OFF
PerfEnhanceSwi BSC6900 SET Meaning:Switches for system performance tch UNBMPARA(Optional) enhancement. 1) PERFENH_R99_BRDCSTHSPA_SWITCH(R99Cel lBroadcastHspaCapSwitch): When this switch is turned on, R99 cells broadcast HSPA capability of neighboring cells in a system information message. 2) PERFENH_FACH_USER_NUM_SWITCH(Fach User Select Switch): This switch is configurable in the current version. The RNC, however, does not use this switch any longer. Later versions will not support this switch. Therefore, users are not advised to use this switch. GUI Value Range:PERFENH_R99_BRDCSTHSPA_SWITCH( R99CellBroadcastHspaCapSwitch), PERFENH_FACH_USER_NUM_SWITCH(FachUs erNumSelectSwitch) Actual Value Range:PERFENH_R99_BRDCSTHSPA_SWITCH, PERFENH_FACH_USER_NUM_SWITCH
Issue 03 (2012-05-30)
9-19
9 Parameters
Parameter ID
NE
MML Command
Description Unit:None Default Value:None
PerfEnhanceSwi BSC6900 SET Meaning:Whether the performance enhancement tch UCORRMPARA(Option function is enabled: al) 1) PERFENH_AMR_SPEC_BR_SWITCH: When the switch is set to ON, the procedure specific to AMR service establishment takes effect. 2) PERFENH_AMR_TMPLT_SWITCH: When the switch is set to ON, the AMR template takes effect. 3) PERFENH_SRB_TMPLT_SWITCH: When the switch is set to ON, the SRB template takes effect. 4) PERFENH_OLPC_TMPLT_SWITCH: When the switch is set to ON, the OLPC template takes effect. 5) PERFENH_AMR_SP_TMPLT_SWITCH: When the switch is set to ON, the AMR parameter template takes effect. 6) PERFENH_INTRAFREQ_MC_TMPLT_SWITCH: When the switch is set to ON, the intra-frequency measurement control template takes effect. 7) PERFENH_INTERRAT_PENALTY_50_SWITCH: After a UE fails to be handed over to a 2G cell during an inter-RAT handover, the RNC forbids the UE to attempt a handover to the 2G cell in a certain period. When the switch is set to ON, the period is 50s. When the switch is set to OFF, the period is 30s. 8) PERFENH_SRB_OVER_HSUPA_TTI10_SWITCH: When the switch is set to ON, the uplink SRBs of HSUPA 10 ms non-conversational services are always carried on DCHs, and the original parameter Type of Channel Preferably Carrying Signaling RB is invalid. When the switch is set to OFF, SRBs for HSUPA 10 ms non-conversational services can be carried on HSUPA channels when the original parameter Type of Channel Preferably Carrying Signaling RB is set to HSUPA or HSPA. The switch is set to OFF by default. 9) PERFENH_HSUPA_TTI2_ENHANCE_SWITCH: When the switch is set to ON, the single-user peak-rate improvement algorithm of HSUPA 2 ms TTI is enabled. When the switch is set to OFF, the algorithm is disabled. The switch is set to OFF by
Issue 03 (2012-05-30)
9-20
9 Parameters
Parameter ID
NE
MML Command
Description default. 10) PERFENH_UU_P2D_CUC_OPT_SWITCH: When this switch is turned on, the P2D cell update confirm message simplification algorithm takes effect. When this switch is turned off, the algorithm does not take effect. By default, this switch is turned off. 11) PERFENH_RL_RECFG_SIR_CONSIDER_SWITC H: This check box controls whether the RNC considers the converged SIRTarget value that is used before radio link reconfiguration in outer loop power control performed after radio link reconfiguration. If the check box is not selected, the RNC sends the initial SIRTarget value used after radio link reconfiguration to the NodeB. If the check box is selected, the RNC selects a more appropriate value from the initial SIRTarget value used after radio link reconfiguration and the converged SIRTarget value used before radio link reconfiguration. Then the RNC sends the selected value to the NodeB. Setting of this check box takes effect only when the PC_RL_RECFG_SIR_TARGET_CARRY_SWITCH check box is selected. 12) PERFENH_RRC_REDIR_PROTECT_SWITCH: When the switch is set to ON, The mechanism to avoid endless back-and-forth RRC-redirections takes effect. The switch is set to OFF by default. 13) PERFENH_H2F_OPT_SWITCH: whether to enable the optimized algorithm for HSPA UE state transition from CELL_DCH to CELL_FACH (also referred to as H2F state transition). When the switch is turned on, the optimized H2F state transition algorithm is enabled, and event 4A measurement of traffic volume or throughput is added to the state transition procedure. The added event 4A measurement prevents an H2F state transition when data is being transmitted. 14) PERFENH_PSTRAFFIC_P2H_SWITCH: When the switch is turned on and a CELL_PCH/URA_PCH-to-CELL_DCH (P2D for short) state transition is triggered for a PS service, the PS service can be set up on HSPA channels after the state transition. When the switch is turned off, PS services can be set up only on DCHs after a
Issue 03 (2012-05-30)
9-21
9 Parameters
Parameter ID
NE
MML Command
Description P2D state transition. This switch is turned off by default. 15) PERFENH_D2IDLE_OPT_SWITCH: When the switch is turned on, a state transition from the CELL_DCH state to idle mode (D2IDLE for short) is triggered if the trigger conditions of CELL_DCH to CELL_FACH (D2F for short) state transition are met, the number of UEs carried on the FACH reaches the upper limit, and the value of the buffer occupancy in all event 4B reports is 0. When the switch is turned off, a D2IDLE state transition is triggered if the trigger conditions of D2F state transition are met and the number of UEs carried on the FACH reaches the upper limit. This switch is configurable in the current version. Later versions will not support this parameter. The RNC, however, no longer uses this switch. Therefore, users are not advised to use this switch. GUI Value Range:PERFENH_AMR_SPEC_BR_SWITCH, PERFENH_AMR_TMPLT_SWITCH, PERFENH_SRB_TMPLT_SWITCH, PERFENH_OLPC_TMPLT_SWITCH, PERFENH_AMR_SP_TMPLT_SWITCH, PERFENH_INTRAFREQ_MC_TMPLT_SWITCH, PERFENH_INTERRAT_PENALTY_50_SWITCH, PERFENH_SRB_OVER_HSUPA_TTI10_SWITCH, PERFENH_HSUPA_TTI2_ENHANCE_SWITCH, PERFENH_UU_P2D_CUC_OPT_SWITCH, PERFENH_RL_RECFG_SIR_CONSIDER_SWITC H, PERFENH_RRC_REDIR_PROTECT_SWITCH, PERFENH_H2F_OPT_SWITCH, PERFENH_PSTRAFFIC_P2H_SWITCH, PERFENH_D2IDLE_OPT_SWITCH Actual Value Range:PERFENH_AMR_SPEC_BR_SWITCH, PERFENH_AMR_TMPLT_SWITCH, PERFENH_SRB_TMPLT_SWITCH, PERFENH_OLPC_TMPLT_SWITCH, PERFENH_AMR_SP_TMPLT_SWITCH, PERFENH_INTRAFREQ_MC_TMPLT_SWITCH, PERFENH_INTERRAT_PENALTY_50_SWITCH, PERFENH_SRB_OVER_HSUPA_TTI10_SWITCH, PERFENH_HSUPA_TTI2_ENHANCE_SWITCH, PERFENH_UU_P2D_CUC_OPT_SWITCH, PERFENH_RL_RECFG_SIR_CONSIDER_SWITC H, PERFENH_RRC_REDIR_PROTECT_SWITCH, PERFENH_H2F_OPT_SWITCH,
Issue 03 (2012-05-30)
9-22
9 Parameters
Parameter ID
NE
MML Command
Description PERFENH_PSTRAFFIC_P2H_SWITCH, PERFENH_D2IDLE_OPT_SWITCH Unit:None Default Value:None
PROCESSSWIT BSC6900 SET Meaning:1) LOAD_IRAT_HO_RNC_FILL_TL (Cell CH2 URRCTRLSWITCH(Opt Load Information TL Input Switch) ional) During inter-RAT handovers from 3G cells to 2G cells, the RNC can records information about load on 3G cells in the RELOCATION REQUIRED container in the Tag Length Value (TLV) format. When the switch is turned on, the RNC records the Tag Length in the container. When the switch is turned off, the RNC does not record the Tag Length. 2) SEND_IDT_JUDGE_IU_RESET (Switch for Transferring INITIAL UE Messages in the IU Reset State) When the switch is turned on, the RNC discards the INITIAL UE message from a CN node if the Iu interface is in the reset state. When the switch is turned off, the RNC handles the INITIAL UE message from a CN node if the Iu interface is in the reset state. 3) RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITC H (RB Reconfiguration DRD Rollback Switch) When the switch is turned on, the RNC supports rollback caused by failed directed retry decisions (DRDs) of RB reconfiguration. When the switch is turned off, the RNC does not support rollback caused by failed DRDs of RB reconfiguration. 4) RNC_CS_QUERY_UE_IMEI_SWITCH (CS IMEI Request Switch) When the switch is turned on, the RNC, rather than the CN, sends an IDENTITY REQUEST message to obtain the IMEI of a UE.when the switch is turned on, it is need to ensure whether the MSC will check the secquence number or not. If yes, the switch SET UCORRMPARA : ReservedSwitch0 = RESERVED_SWITCH_0_BIT29 -1 also should be truned on. Otherwise, the CS traffic will be failed. When the switch is turned off, the RNC does not
9 Parameters
Parameter ID
NE
MML Command
Description send an IDENTITY REQUEST message to obtain the IMEI of a UE. 5) RNC_PS_QUERY_UE_IMEI_SWITCH (PS IMEI Request Switch) When the switch is turned on, the RNC, rather than the CN, sends an IDENTITY REQUEST message to obtain the IMEI of a UE. When the switch is turned off, the RNC does not send an IDENTITY REQUEST message to obtain the IMEI of a UE. 6) FACH_DTCH_CONGEST_P2D (P2D Switch for Congested FACH or DTCH) When the switch is turned on, UEs using PS services trigger the CELL_PCH-to-CELL_DCH procedure (P2D procedure for short) on a congested FACH or DTCH. When the switch is turned off, UEs using PS services do not trigger the P2D procedure on a congested FACH or DTCH. 7) RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITC H (RB Establishment DRD Rollback Switch) When the switch is turned on, the RNC supports rollback caused by failed DRDs of RB establishment. When the switch is turned off, the RNC does not support rollback caused by failed DRDs of RB establishment. 8) RNC_FD_SCRI_FORCE_REL_SWITCH (Signaling Connection Release Switch for UEs Supporting Fast Dormancy) When the switch is turned on, if the RNC receives a SIGNALING CONNECTION RELEASE INDICATION from UE with the cause of "UE Requested PS Data session end", the RNC triggers the state transition for the UE. Otherwise, the RNC releases the signaling connection. When the switch is turned off, if the RNC receives a SIGNALING CONNECTION RELEASE INDICATION from UE, the RNC triggers the state transition for the UE. 9) USRPLN_PRORATION_SHARED_ALO (Algorithm Switch for Inter-Subrack Load Sharing on the User Plane)
Issue 03 (2012-05-30)
9-24
9 Parameters
Parameter ID
NE
MML Command
Description When the switch is turned on, load sharing can be performed based on the ratio of available user plane resources to total user plane resources in a subrack. When the switch is turned off, load sharing cannot be performed based on the ratio of available user plane resources to total user plane resources in a subrack. 10) FP_IUUP_TRACE_SWITCH (Switch for Tracing UEs Failing in FP Synchronization) When the switch is turned on, UEs using FP or Iu UP can be traced in terms of data streams. When the switch is turned off, UEs using FP or Iu UP cannot be traced in terms of data streams. GUI Value Range:LOAD_IRAT_HO_RNC_FILL_TL, SEND_IDT_JUDGE_IU_RESET, RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITC H, RNC_CS_QUERY_UE_IMEI_SWITCH, RNC_PS_QUERY_UE_IMEI_SWITCH, FACH_DTCH_CONGEST_P2D, RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITC H, RNC_FD_SCRI_FORCE_REL_SWITCH, USRPLN_PRORATION_SHARED_ALO, FP_IUUP_TRACE_SWITCH Actual Value Range:This parameter is set to 0 or 1according to the related domains. Unit:None Default Value:None
PROCESSSWIT BSC6900 SET Meaning:1) FACH_DCCH_CONG_CTRL_SWITCH CH3 URRCTRLSWITCH(Opt (Congestion Control Switch for FACH or DCCH) ional) When the switch is turned on, the RNC restricts the P2F or CELL_FACH-to-CELL_DCH (F2D for short) procedure triggered by heavy PS traffic. When the switch is turned off, the RNC does not restrict the P2F or F2D procedure triggered by heavy PS traffic. 2) RNC_F2D_RLC_SUSPEND_SWITCH (RLC Suspension Switch for Event 4A) When the switch is turned on, the RNC triggers RLC suspension during the F2D procedure for a UE, and it resumes RLC transmission after the RNC receives an RB RECONFIGURATION COMPLETE message or after the UE rolls back to
Issue 03 (2012-05-30)
9-25
9 Parameters
Parameter ID
NE
MML Command
Description the CELL_FACH state. When the switch is turned off, the RNC does not trigger RLC suspension during the F2D procedure for a UE, and it resumes RLC transmission after the RNC receives an RB RECONFIGURATION COMPLETE message or after the UE rolls back to the CELL_FACH state. 3) UM_RRCRELCMP_RLDEL_DELAY_SWITCH (RL Deletion Delay Switch for RRC CONNECTION RELEASE COMPLETE Messages) When the switch is turned on, the RNC starts the timer for radio link deletion if it receives an RRC CONNECTION RELEASE COMPLETE message. After the timer has expired, the RNC restarts to delete radio links. When the switch is turned off, the RNC immediately starts to delete radio links if it receives an RRC CONNECTION RELEASE COMPLETE message. 4) RNC_TVM_BASED_P2D_SWITCH (TVM-based P2D Switch) When the switch is turned on, for UEs in the CELL_PCH state, the RNC triggers the P2D procedure if the RNC receives from a UE a cell update message in which the value of the IE "Traffic volume indicator" is TRUE, or if the dynamic traffic volume measured on the CN meets a specified threshold. When the switch is turned off, the RNC does not trigger the P2D procedure based on the value of the IE "Traffic volume indicator" or on the dynamic traffic volume measured on the CN. 5) CS_RLFAIL_RRCSETUP_STAT_SWITCH (Measurement Switch for Released CS Services of UEs Resending RRC Connection Requests Caused by RL Synchronization Loss) When the switch is turned on, if radio links for a UE experience synchronization loss on the network side and the UE has released its RRC connection and resends an RRC connection request, the resulting CS services released are considered call drops. When the switch is turned off, if radio links for a UE experience synchronization loss on the network side and the UE has released its RRC connection and resends an RRC connection request, the resulting CS services released are not considered
Issue 03 (2012-05-30)
9-26
9 Parameters
Parameter ID
NE
MML Command
Description call drops. GUI Value Range:FACH_DCCH_CONG_CTRL_SWITCH, RNC_F2D_RLC_SUSPEND_SWITCH, UM_RRCRELCMP_RLDEL_DELAY_SWITCH, RNC_TVM_BASED_P2D_SWITCH, CS_RLFAIL_RRCSETUP_STAT_SWITCH Actual Value Range:This parameter is set to 0 or 1according to the related domains. Unit:None Default Value:None
PsRestriction
BSC6900 ADD Meaning:Specifies whether to impose the access UCELLDSACMANUALP restriction on the PS domain. ARA(Mandatory) GUI Value Range:FALSE, TRUE MOD UCELLDSACMANUALP Actual Value Range:FALSE, TRUE ARA(Optional) Unit:None Default Value:None
RegByFachSwit BSC6900 SET Meaning:The parameter specifies whether to set up ch UCALLSHOCKCTRL(O RRC connection for registration on the FACH ptional) instead of on the DCH in the call shock. When ON is selected, RNC will perform flow control at cell level or NodeB level, the RRC connection for registration is set up on the FACH instead of on the DCH. When OFF is selected, the channel setup strategy of RRC connection request for registration can be set by running the SET URRCESTCAUSE command. GUI Value Range:OFF, ON Actual Value Range:OFF, ON Unit:None Default Value:ON ReservedSwitch BSC6900 SET Meaning:NBM algorithm reserved switch 0. The 0 UNBMPARA(Optional) switch is reserved for further change request use. GUI Value Range:RESERVED_SWITCH_0_BIT1, RESERVED_SWITCH_0_BIT2, RESERVED_SWITCH_0_BIT3, RESERVED_SWITCH_0_BIT4, RESERVED_SWITCH_0_BIT5,
Issue 03 (2012-05-30)
9-27
9 Parameters
Parameter ID
NE
MML Command
Description RESERVED_SWITCH_0_BIT6, RESERVED_SWITCH_0_BIT7, RESERVED_SWITCH_0_BIT8, RESERVED_SWITCH_0_BIT9, RESERVED_SWITCH_0_BIT10, RESERVED_SWITCH_0_BIT11, RESERVED_SWITCH_0_BIT12, RESERVED_SWITCH_0_BIT13, RESERVED_SWITCH_0_BIT14, RESERVED_SWITCH_0_BIT15, RESERVED_SWITCH_0_BIT16, RESERVED_SWITCH_0_BIT17, RESERVED_SWITCH_0_BIT18, RESERVED_SWITCH_0_BIT19, RESERVED_SWITCH_0_BIT20, RESERVED_SWITCH_0_BIT21, RESERVED_SWITCH_0_BIT22, RESERVED_SWITCH_0_BIT23, RESERVED_SWITCH_0_BIT24, RESERVED_SWITCH_0_BIT25, RESERVED_SWITCH_0_BIT26, RESERVED_SWITCH_0_BIT27, RESERVED_SWITCH_0_BIT28, RESERVED_SWITCH_0_BIT29, RESERVED_SWITCH_0_BIT30, RESERVED_SWITCH_0_BIT31, RESERVED_SWITCH_0_BIT32 Actual Value Range:RESERVED_SWITCH_0_BIT1, RESERVED_SWITCH_0_BIT2, RESERVED_SWITCH_0_BIT3, RESERVED_SWITCH_0_BIT4, RESERVED_SWITCH_0_BIT5, RESERVED_SWITCH_0_BIT6, RESERVED_SWITCH_0_BIT7, RESERVED_SWITCH_0_BIT8, RESERVED_SWITCH_0_BIT9, RESERVED_SWITCH_0_BIT10, RESERVED_SWITCH_0_BIT11, RESERVED_SWITCH_0_BIT12, RESERVED_SWITCH_0_BIT13, RESERVED_SWITCH_0_BIT14, RESERVED_SWITCH_0_BIT15, RESERVED_SWITCH_0_BIT16, RESERVED_SWITCH_0_BIT17, RESERVED_SWITCH_0_BIT18, RESERVED_SWITCH_0_BIT19, RESERVED_SWITCH_0_BIT20, RESERVED_SWITCH_0_BIT21, RESERVED_SWITCH_0_BIT22, RESERVED_SWITCH_0_BIT23, RESERVED_SWITCH_0_BIT24, RESERVED_SWITCH_0_BIT25,
Issue 03 (2012-05-30)
9-28
9 Parameters
Parameter ID
NE
MML Command
Description RESERVED_SWITCH_0_BIT26, RESERVED_SWITCH_0_BIT27, RESERVED_SWITCH_0_BIT28, RESERVED_SWITCH_0_BIT29, RESERVED_SWITCH_0_BIT30, RESERVED_SWITCH_0_BIT31, RESERVED_SWITCH_0_BIT32 Unit:None Default Value:None
ReservedSwitch BSC6900 SET Meaning:CORRM algorithm reserved switch 0. The 0 UCORRMALGOSWITC switch is reserved for further change request use. H(Optional) 1) RESERVED_SWITCH_0_BIT2: When the switch is set to ON, only uplink RLC or downlink RLC can be re-established during the state transition from CELL_FACH to CELL_DCH (F2D for short). 2) RESERVED_SWITCH_0_BIT3: When the switch is set to ON, signaling radio bearers (SRBs) cannot be changed from DCHs to HSPA channels (including the channel change from DCH to E-DCH in the uplink and from DCH to HS-DSCH in the downlink) during directed retry. 3) RESERVED_SWITCH_0_BIT4: When the switch is turned on, the RNC does not consider whether the cell is congested during AMR service establishment. That is, parameters are set on the precondition that the cell is not congested. This prevents inconsistency in uplink and downlink AMR modes. 4) RESERVED_SWITCH_0_BIT5: When the switch is set to ON, the RNC establishes the BE service of a UE on R99 channels instead of on HSUPA channels if the uplink coverage of the UE is limited. The RNC determines whether the uplink coverage of a UE is limited on the basis of the Ec/N0 reported by the UE during RRC connection establishment. 5) RESERVED_SWITCH_0_BIT6: When the switch is set to ON, the directed retry algorithm based on downlink load balance is enabled. When the switch is set to OFF, this algorithm is disabled. This algorithm is an optimization of the original downlink load balance algorithm. 6) RESERVED_SWITCH_0_BIT7: When the switch is set to ON, BE services that are already established on E-DCHs can be re-established on DCHs due to insufficient coverage. 7) RESERVED_SWITCH_0_BIT8: When the
Issue 03 (2012-05-30)
9-29
9 Parameters
Parameter ID
NE
MML Command
Description switch is turned on, D2F state transition is allowed regardless of whether the CCCH exists on the Iur interface. If D2F state transition fails, DSCR is triggered. When the switch is turned off, the RNC needs to determine whether the CCCH exists on the Iur interface before determining whether to trigger D2F state transition. 8) RESERVED_SWITCH_0_BIT9: When the switch is set to ON, the uplink 0 kbit/s transport format of subflow A of an AMR service (WB AMR service or NB AMR service) is 0*TbSize. When the switch is set to OFF, the uplink 0 kbit/s transport format of subflow A of an AMR service is 1*0. 9) RESERVED_SWITCH_0_BIT10: When the switch is turned on, multiple cross-Iur radio links (RLs) belonging to the same DRNC can be added simultaneously. If an RL fails to be added with the failure cause of RadioNetwork:unspecified (14), the RNC attempts to reestablish the RL for only once. 10) RESERVED_SWITCH_0_BIT11: When the switch is turned on, the PS service must be carried by DCHs in the uplink if both CS and PS services exist. 11) RESERVED_SWITCH_0_BIT15: When the switch is turned on, the PS service must be carried by DCHs in the downlink if both CS and PS services exist. GUI Value Range:RESERVED_SWITCH_0_BIT1, RESERVED_SWITCH_0_BIT2, RESERVED_SWITCH_0_BIT3, RESERVED_SWITCH_0_BIT4, RESERVED_SWITCH_0_BIT5, RESERVED_SWITCH_0_BIT6, RESERVED_SWITCH_0_BIT7, RESERVED_SWITCH_0_BIT8, RESERVED_SWITCH_0_BIT9, RESERVED_SWITCH_0_BIT10, RESERVED_SWITCH_0_BIT11, RESERVED_SWITCH_0_BIT12, RESERVED_SWITCH_0_BIT13, RESERVED_SWITCH_0_BIT14, RESERVED_SWITCH_0_BIT15, RESERVED_SWITCH_0_BIT16, RESERVED_SWITCH_0_BIT17, RESERVED_SWITCH_0_BIT18, RESERVED_SWITCH_0_BIT19, RESERVED_SWITCH_0_BIT20, RESERVED_SWITCH_0_BIT21, RESERVED_SWITCH_0_BIT22, RESERVED_SWITCH_0_BIT23,
Issue 03 (2012-05-30)
9-30
9 Parameters
Parameter ID
NE
MML Command
Description RESERVED_SWITCH_0_BIT24, RESERVED_SWITCH_0_BIT25, RESERVED_SWITCH_0_BIT26, RESERVED_SWITCH_0_BIT27, RESERVED_SWITCH_0_BIT28, RESERVED_SWITCH_0_BIT29, RESERVED_SWITCH_0_BIT30, RESERVED_SWITCH_0_BIT31, RESERVED_SWITCH_0_BIT32 Actual Value Range:RESERVED_SWITCH_0_BIT1, RESERVED_SWITCH_0_BIT2, RESERVED_SWITCH_0_BIT3, RESERVED_SWITCH_0_BIT4, RESERVED_SWITCH_0_BIT5, RESERVED_SWITCH_0_BIT6, RESERVED_SWITCH_0_BIT7, RESERVED_SWITCH_0_BIT8, RESERVED_SWITCH_0_BIT9, RESERVED_SWITCH_0_BIT10, RESERVED_SWITCH_0_BIT11, RESERVED_SWITCH_0_BIT12, RESERVED_SWITCH_0_BIT13, RESERVED_SWITCH_0_BIT14, RESERVED_SWITCH_0_BIT15, RESERVED_SWITCH_0_BIT16, RESERVED_SWITCH_0_BIT17, RESERVED_SWITCH_0_BIT18, RESERVED_SWITCH_0_BIT19, RESERVED_SWITCH_0_BIT20, RESERVED_SWITCH_0_BIT21, RESERVED_SWITCH_0_BIT22, RESERVED_SWITCH_0_BIT23, RESERVED_SWITCH_0_BIT24, RESERVED_SWITCH_0_BIT25, RESERVED_SWITCH_0_BIT26, RESERVED_SWITCH_0_BIT27, RESERVED_SWITCH_0_BIT28, RESERVED_SWITCH_0_BIT29, RESERVED_SWITCH_0_BIT30, RESERVED_SWITCH_0_BIT31, RESERVED_SWITCH_0_BIT32 Unit:None Default Value:None
ReservedSwitch BSC6900 SET Meaning:CORRM algorithm reserved switch 1. The 1 UCORRMALGOSWITC switch is reserved for further change request use. H(Optional) 1) RESERVED_SWITCH_1_BIT1: When the switch is set to ON, the RNC instructs the cells involved in the active set to report cell synchronization
Issue 03 (2012-05-30)
9-31
9 Parameters
Parameter ID
NE
MML Command
Description information by using an intra-frequency measurement control message. When the switch is set to OFF, the RNC instructs the cells involved in the active set not to report cell synchronization information by using an intra-frequency measurement control message. This avoids the transmission of too large measurement reports. 2) RESERVED_SWITCH_1_BIT2: When the switch is set to ON, the intra-frequency ReadSFNInd of a cell in system information SIB11/SIB12 is set to the fixed value READ. GUI Value Range:RESERVED_SWITCH_1_BIT1, RESERVED_SWITCH_1_BIT2, RESERVED_SWITCH_1_BIT3, RESERVED_SWITCH_1_BIT4, RESERVED_SWITCH_1_BIT5, RESERVED_SWITCH_1_BIT6, RESERVED_SWITCH_1_BIT7, RESERVED_SWITCH_1_BIT8, RESERVED_SWITCH_1_BIT9, RESERVED_SWITCH_1_BIT10, RESERVED_SWITCH_1_BIT11, RESERVED_SWITCH_1_BIT12, RESERVED_SWITCH_1_BIT13, RESERVED_SWITCH_1_BIT14, RESERVED_SWITCH_1_BIT15, RESERVED_SWITCH_1_BIT16, RESERVED_SWITCH_1_BIT17, RESERVED_SWITCH_1_BIT18, RESERVED_SWITCH_1_BIT19, RESERVED_SWITCH_1_BIT20, RESERVED_SWITCH_1_BIT21, RESERVED_SWITCH_1_BIT22, RESERVED_SWITCH_1_BIT23, RESERVED_SWITCH_1_BIT24, RESERVED_SWITCH_1_BIT25, RESERVED_SWITCH_1_BIT26, RESERVED_SWITCH_1_BIT27, RESERVED_SWITCH_1_BIT28, RESERVED_SWITCH_1_BIT29, RESERVED_SWITCH_1_BIT30, RESERVED_SWITCH_1_BIT31, RESERVED_SWITCH_1_BIT32 Actual Value Range:RESERVED_SWITCH_1_BIT1, RESERVED_SWITCH_1_BIT2, RESERVED_SWITCH_1_BIT3, RESERVED_SWITCH_1_BIT4, RESERVED_SWITCH_1_BIT5, RESERVED_SWITCH_1_BIT6, RESERVED_SWITCH_1_BIT7,
Issue 03 (2012-05-30)
9-32
9 Parameters
Parameter ID
NE
MML Command
Description RESERVED_SWITCH_1_BIT8, RESERVED_SWITCH_1_BIT9, RESERVED_SWITCH_1_BIT10, RESERVED_SWITCH_1_BIT11, RESERVED_SWITCH_1_BIT12, RESERVED_SWITCH_1_BIT13, RESERVED_SWITCH_1_BIT14, RESERVED_SWITCH_1_BIT15, RESERVED_SWITCH_1_BIT16, RESERVED_SWITCH_1_BIT17, RESERVED_SWITCH_1_BIT18, RESERVED_SWITCH_1_BIT19, RESERVED_SWITCH_1_BIT20, RESERVED_SWITCH_1_BIT21, RESERVED_SWITCH_1_BIT22, RESERVED_SWITCH_1_BIT23, RESERVED_SWITCH_1_BIT24, RESERVED_SWITCH_1_BIT25, RESERVED_SWITCH_1_BIT26, RESERVED_SWITCH_1_BIT27, RESERVED_SWITCH_1_BIT28, RESERVED_SWITCH_1_BIT29, RESERVED_SWITCH_1_BIT30, RESERVED_SWITCH_1_BIT31, RESERVED_SWITCH_1_BIT32 Unit:None Default Value:None
ReservedU32Pa BSC6900 SET Meaning:CORRM algorithm reserved U32 para 1. ra1 UCORRMALGOSWITC The para of 32 bits is reserved for further change H(Optional) request use. GUI Value Range:0~4294967295 Actual Value Range:0~4294967295 Unit:None Default Value:4294967295 RrcConnRejWai BSC6900 SET Meaning:Wait time in high-priority RRC connection tTmr USTATETIMER(Optiona reject message, the time period the UE has to wait l) before repeating the rejected procedure of RRC connection GUI Value Range:0~15 Actual Value Range:0~15 Unit:s Default Value:4
Issue 03 (2012-05-30)
9-33
9 Parameters
Parameter ID RsvdPara1
NE
MML Command
Description
BSC6900 ADD Meaning:Reserved Parameter1. UNODEBALGOPARA( GUI Value Range:RSVDBIT1(Reserved Switch 1), Optional) RSVDBIT2(Reserved Switch 2), MOD RSVDBIT3(Reserved Switch 3), UNODEBALGOPARA( RSVDBIT4(Reserved Switch 4), Optional) RSVDBIT5(Reserved Switch 5), RSVDBIT6(Reserved Switch 6), RSVDBIT7(Reserved Switch 7), RSVDBIT8(Reserved Switch 8), RSVDBIT9(Reserved Switch 9), RSVDBIT10(Reserved Switch 10), RSVDBIT11(Reserved Switch 11), RSVDBIT12(Reserved Switch 12), RSVDBIT13(Reserved Switch 13), RSVDBIT14(Reserved Switch 14), RSVDBIT15(Reserved Switch 15), RSVDBIT16(Reserved Switch 16) Actual Value Range:RSVDBIT1, RSVDBIT2, RSVDBIT3, RSVDBIT4, RSVDBIT5, RSVDBIT6, RSVDBIT7, RSVDBIT8, RSVDBIT9, RSVDBIT10, RSVDBIT11, RSVDBIT12, RSVDBIT13, RSVDBIT14, RSVDBIT15, RSVDBIT16 Unit:None Default Value:None
RsvdPara1
BSC6900 ADD Meaning:The algorithms with the above values UCELLALGOSWITCH( represent are Optional) as follow: RSVDBIT1~RSVDBIT16:Reserved MOD Switch. UCELLALGOSWITCH( GUI Value Range:RSVDBIT1(Reserved Switch 1), Optional) RSVDBIT2(Reserved Switch 2), RSVDBIT3(Reserved Switch 3), RSVDBIT4(Reserved Switch 4), RSVDBIT5(Reserved Switch 5), RSVDBIT6(Reserved Switch 6), RSVDBIT7(Reserved Switch 7), RSVDBIT8(Reserved Switch 8), RSVDBIT9(Reserved Switch 9), RSVDBIT10(Reserved Switch 10), RSVDBIT11(Reserved Switch 11), RSVDBIT12(Reserved Switch 12), RSVDBIT13(Reserved Switch 13), RSVDBIT14(Reserved Switch 14), RSVDBIT15(Reserved Switch 15),
Issue 03 (2012-05-30)
9-34
9 Parameters
Parameter ID
NE
MML Command
Description RSVDBIT16(Reserved Switch 16) Actual Value Range:RSVDBIT1, RSVDBIT2, RSVDBIT3, RSVDBIT4, RSVDBIT5, RSVDBIT6, RSVDBIT7, RSVDBIT8, RSVDBIT9, RSVDBIT10, RSVDBIT11, RSVDBIT12, RSVDBIT13, RSVDBIT14, RSVDBIT15, RSVDBIT16 Unit:None Default Value:None
RsvdPara1
BSC6900 SET Meaning:Reserved Parameter1. UCACALGOSWITCH(O GUI Value Range:RSVDBIT1(Reserved Switch 1), ptional) RSVDBIT2(Reserved Switch 2), RSVDBIT3(Reserved Switch 3), RSVDBIT4(Reserved Switch 4), RSVDBIT5(Reserved Switch 5), RSVDBIT6(Reserved Switch 6), RSVDBIT7(Reserved Switch 7), RSVDBIT8(Reserved Switch 8), RSVDBIT9(Reserved Switch 9), RSVDBIT10(Reserved Switch 10), RSVDBIT11(Reserved Switch 11), RSVDBIT12(Reserved Switch 12), RSVDBIT13(Reserved Switch 13), RSVDBIT14(Reserved Switch 14), RSVDBIT15(Reserved Switch 15), RSVDBIT16(Reserved Switch 16) Actual Value Range:RSVDBIT1, RSVDBIT2, RSVDBIT3, RSVDBIT4, RSVDBIT5, RSVDBIT6, RSVDBIT7, RSVDBIT8, RSVDBIT9, RSVDBIT10, RSVDBIT11, RSVDBIT12, RSVDBIT13, RSVDBIT14, RSVDBIT15, RSVDBIT16 Unit:None Default Value:None
RsvdPara1
BSC6900 SET Meaning:2) NAS_QOS_MOD_SWITCH (QoS URRCTRLSWITCH(Opt Change Switch for NAS) ional) When the switch is turned on, for UEs whose HS-DSCH category is smaller than 13, if the maximum downlink rate specified in the PDP
Issue 03 (2012-05-30)
9-35
9 Parameters
Parameter ID
NE
MML Command
Description activation requests from the UEs exceeds 16 Mbit/s, the requests are sent to the CN after the rate is changed to 16 Mbit/s. When the switch is turned off, the PDP activation requests are sent to the CN without changing the maximum downlink rate. 15) RSVDBIT1_BIT15 (Reserved Parameter 1 Bit 15) When the switch is turned on, the RNC enables the function of AMR mute detection. When the switch is turned off, the RNC disables the function of AMR mute detection. 16) RSVDBIT1_BIT16 (Reserved Parameter 1 Bit 16) When the switch is turned on, the RNC can perform DRDs during the P2D procedure. When the switch is turned off, the RNC cannot perform DRDs during the P2D procedure. 17) SYSHO_CSIN_PERMIT_SWITCH (2G-to-3G CS Handover Switch) When the switch is turned on, inter-RAT CS handovers from 2G cells to 3G cells are allowed. When the switch is turned off, inter-RAT CS handovers from 2G cells to 3G cells are not allowed. 20) RSVDBIT1_BIT20 (Reserved Parameter 1 Bit 20) When this switch is turned on, the RNC performs a state transition from CELL_PCH or URA_PCH to CELL_FACH (P2F) upon receiving a CELL UPDATE message with the cause value "uplink data transmission" or "paging response". When this switch is turned off, if receiving a CELL UPDATE message with the cause value "uplink data transmission" or "paging response," the RNC performs a state transition from CELL_PCH or URA_PCH to CELL_DCH (P2D) in either of the following scenarios: (1)Congestion occurs on the FACH. (2)Congestion occurs on the DCCH, and the value of the Establishment cause information element (IE) in the message is Originating Conversational Call, Terminating Conversational Call, or
Issue 03 (2012-05-30)
9-36
9 Parameters
Parameter ID
NE
MML Command
Description Emergency Call. 21) RSVDBIT1_BIT21 (Reserved Parameter 1 Bit 21) When the switch is turned on, for UEs that are establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state, the RNC stops establishing AMR services to handle cell update if the RNC receives from the UEs a cell update message containing the cause value "cell reselection." When the switch is turned off, for UEs that are establishing AMR services and shifting from the CELL_FACH state to the CELL_DCH state, if the RNC receives from the UEs a cell update message containing the cause value "cell reselection," the RNC stops establishing AMR services to handle cell update and resumes AMR services only after cell update is completed. 22) RSVDBIT1_BIT22 (Reserved Parameter 1 Bit 22) When the switch is turned on, the RNC does not trigger cell update with the cause value "RL Failure" if the RNC detects interrupted downlink transmission on SRB2. When the switch is turned off, the RNC triggers cell update with the cause value "RL Failure" and reestablishes radio links if the RNC detects interrupted downlink transmission on SRB2. 23) RSVDBIT1_BIT23 (Reserved Parameter 1 Bit 23) When the switch is turned on, the RNC does not trigger cell update with the cause value "RL Failure" reported by a UE if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. When the switch is turned off, the RNC triggers cell update with the cause value "RL Failure" reported by a UE and reestablishes radio links, if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. 24) RSVDBIT1_BIT24 (Reserved Parameter 1 Bit 24) When the switch is turned on, for UEs using CS services, the RNC does not trigger cell update with the cause value "RL Failure" reported by a UE, if the RNC detects interrupted downlink transmission
Issue 03 (2012-05-30)
9-37
9 Parameters
Parameter ID
NE
MML Command
Description on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. When the switch is turned off, for UEs using CS services, the RNC triggers cell update with the cause value "RL Failure" reported by a UE and reestablishes radio links, if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. 25) RSVDBIT1_BIT25 (Reserved Parameter 1 Bit 25) When the switch is turned on, for UEs using PS services only, the RNC does not reestablish radio links for a UE if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. When the switch is turned off, for UEs using PS services only, the RNC triggers cell update with the cause value "RL Failure" reported by a UE and reestablishes radio link, if the RNC detects interrupted downlink transmission on SRB2, or if the associated NodeB reports to the RNC that all radio links for the UE experience synchronization loss. 26) RSVDBIT1_BIT26 (Reserved Parameter 1 Bit 26) When the switch is turned on, the RNC does not reestablish radio links for a UE if the UE reports to the RNC cell update caused by SRB reset. When the switch is turned off, the RNC reestablishes radio links for a UE if the UE reports to the RNC cell update caused by SRB reset. 28) RSVDBIT1_BIT28 (Reserved Parameter 1 Bit 28) When the switch is turned on, for UEs using CS services, if a NodeB reports to the RNC that all radio links for a UE experience synchronization loss, the RNC starts the RL Restore timer whose duration is specified by the RlRstrTmr parameter in the SET USTATETIMER command. After the timer has expired, the RNC triggers cell update with the cause value "radio link failure" and reestablishes radio links for the UE. When the switch is turned off, for UEs using CS
Issue 03 (2012-05-30)
9-38
9 Parameters
Parameter ID
NE
MML Command
Description services, if a NodeB reports to the RNC that all radio links for a UE experience synchronization loss, the RNC starts the RL Restore timer whose duration is specified by the T313 parameter in the SET UCONNMODETIMER command. After the timer has expired, the RNC triggers cell update with the cause value "radio link failure" and reestablishes radio links for the UE. 29) RSVDBIT1_BIT29 (Reserved Parameter 1 Bit 29) When the switch is turned off, the RNC performs the CELL_DCH-to-CELL_FACH (D2F for short) procedure on UEs that support fast dormancy. When the switch is turned on, the RNC performs the CELL_DCH-to-CELL_PCH (D2P for short) procedure on UEs that support fast dormancy. GUI Value Range:RSVDBIT1_BIT1, NAS_QOS_MOD_SWITCH, RSVDBIT1_BIT3, RSVDBIT1_BIT4, RSVDBIT1_BIT5, RSVDBIT1_BIT6, RSVDBIT1_BIT7, RSVDBIT1_BIT8, RSVDBIT1_BIT9, RSVDBIT1_BIT10, RSVDBIT1_BIT11, RSVDBIT1_BIT12, RSVDBIT1_BIT13, RSVDBIT1_BIT14, RSVDBIT1_BIT15, RSVDBIT1_BIT16, SYSHO_CSIN_PERMIT_SWITCH, RSVDBIT1_BIT18, RSVDBIT1_BIT19, RSVDBIT1_BIT20, RSVDBIT1_BIT21, RSVDBIT1_BIT22, RSVDBIT1_BIT23, RSVDBIT1_BIT24, RSVDBIT1_BIT25, RSVDBIT1_BIT26, RSVDBIT1_BIT27, RSVDBIT1_BIT28, RSVDBIT1_BIT29, RSVDBIT1_BIT30, RSVDBIT1_BIT31, RSVDBIT1_BIT32 Actual Value Range:This parameter is set to 0 or 1 according to the related domains. Unit:None Default Value:None
RsvdPara3
BSC6900 SET Meaning:Reserved parameter 3. URRRSVDPARA(Optio GUI Value Range:0~4294967295 nal) Actual Value Range:0~4294967295 Unit:None Default Value:0
Issue 03 (2012-05-30)
9-39
9 Parameters
Parameter ID
NE
MML Command
Description
SLPAGECTHD BSC6900 SET Meaning:CPU usage threshold for paging flow FCCPUTHD(Optional) control over best effort (BE) services, supplementary services (SS), and the location service (LCS). BE services uses the same paging flow control thresholds as SS and LCS to ensure the paging success rate of real-time services. When the average CPU usage within several sliding windows reaches or exceeds "SS and LCS page restore threshold", the linear paging flow control on BE services, SS, and LCS is started. When the average CPU usage within several sliding windows reaches or exceeds "SS and LCS page control threshold", the 100% paging flow control on BE services, SS, and LCS is started. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:80 SLPAGERTHD BSC6900 SET Meaning:CPU usage threshold for paging flow FCCPUTHD(Optional) control over best effort (BE) services, supplementary services (SS), and location service (LCS). BE services uses the same paging flow control thresholds as SS and LCS to ensure the paging success rate of real-time services. When the average CPU usage within several sliding windows reaches or exceeds "SS and LCS page restore threshold", the linear paging flow control on BE services, SS, and LCS is started. When the average CPU usage within several sliding windows is lower than the "SS and LCS page restore threshold", paging flow control over BE services, SS, and LCS is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70 SMPAGECTHD BSC6900 SET Meaning:CPU usage threshold for paging flow FCCPUTHD(Optional) control over the short message service (SMS). When the average CPU usage within several sliding windows reaches or exceeds "SMS page restore threshold", the linear paging flow control on SMS is started. When the average CPU usage within several sliding windows reaches or exceeds the "SMS page control threshold", the 100% paging
Issue 03 (2012-05-30)
9-40
9 Parameters
Parameter ID
NE
MML Command
Description flow control on SMS is started. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70
SMPAGERTHD BSC6900 SET Meaning:CPU usage threshold for paging flow FCCPUTHD(Optional) control over the short message service (SMS). When the average CPU usage within several sliding windows reaches or exceeds "SMS page restore threshold", the linear paging flow control on SMS is started. When the average CPU usage within several sliding windows is lower than "SMS page restore threshold", the flow control on SMS is stopped. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:60 SMRRCCONNC BSC6900 SET Meaning:CPU usage threshold for stopping load CPUTHD SHARETHD(Optional) sharing on SMS RRC connection setup requests. When the CPU usage of an XPU subsystem reaches this threshold or CtrlPlnSharingOutThd, whichever is smaller, later SMS RRC connection setup requests will be carried by other XPU subsystems. CtrlPlnSharingOutThd is set by using the command "SET UCTRLPLNSHAREPARA". If the CPU usage of all candidate XPU subsystems exceeds this threshold, flow control on SMS RRC connection setup requests is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:70 SMRRCCONNC BSC6900 SET Meaning:Packet usage threshold for stopping load MSGTHD SHARETHD(Optional) sharing on SMS RRC connection setup requests. When the packet usage of an XPU subsystem reaches this threshold, later SMS packets will be carried by other XPU subsystems. If the packet usage of all candidate XPU subsystems exceeds this threshold, flow control on SMS RRC
Issue 03 (2012-05-30)
9-41
9 Parameters
Parameter ID
NE
MML Command
Description connection setup request packets is triggered. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:75
SMRRCCONNR BSC6900 SET Meaning:CPU usage threshold for recoverying load CPUTHD SHARETHD(Optional) sharing on SMS RRC connection setup requests. If the CPU usage of an XPU subsystem is lower than this threshold, this XPU subsystem is a candidate subsystem for the load sharing on SMS RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:60 SMRRCCONNR BSC6900 SET Meaning:Packet usage threshold for recoverying MSGTHD SHARETHD(Optional) load sharing on SMS RRC connection setup requests. When the packet usage of an XPU subsystem is lower than this threshold, this XPU subsystem is a candidate subsystem for load sharing on SMS RRC connection setup requests. GUI Value Range:30~100 Actual Value Range:30~100 Unit:% Default Value:65 SMWINDOW BSC6900 SET Meaning:Number of CPU usage sampling times FCMSGQTHD(Optional involved in the calculation of the average CPU ) usage in the sliding window. "Filter window" is applied to avoid the change of the flow control status due to instantaneous overhigh CPU usage. After "filter window" is applied, the system compares the average CPU usage in a period before the current time with the corresponding threshold. In the case that the flow control switch is turned on, when the average CPU usage in "filter window" reaches or exceeds a flow control threshold, the corresponding flow control mechanism is triggered. When the average CPU usage is lower than a flow control threshold, the corresponding flow control mechanism is disabled.
Issue 03 (2012-05-30)
9-42
9 Parameters
Parameter ID
NE
MML Command
Description GUI Value Range:2~2000 Actual Value Range:2~2000 Unit:None Default Value:10
SMWINDOW
BSC6900 SET Meaning:Number of CPU usage sampling times FCCPUTHD(Optional) involved in the calculation of the average CPU usage in the sliding window. "Filter window" is applied to avoid the change of the flow control status due to instantaneous overhigh CPU usage. After "filter window" is applied, the system compares the average CPU usage in a period before the current time with the corresponding threshold. In the case that the flow control switch is turned on, when the average CPU usage in "filter window" reaches or exceeds a flow control threshold, the corresponding flow control mechanism is triggered. When the average CPU usage is lower than a flow control threshold, the corresponding flow control mechanism is disabled. GUI Value Range:2~2000 Actual Value Range:2~2000 Unit:None Default Value:10
SSDSPAVEUSA BSC6900 SET CPUTHD(Optional) Meaning:DSP usage alarm clearance threshold. GEALMTHD When the DSP usage is lower than the threshold, the DSP usage alarm is cleared. "DSP occupancy alarm clearance threshold" must be smaller than "DSP occupancy alarm threshold". GUI Value Range:20~99 Actual Value Range:20~99 Unit:% Default Value:80 SSDSPMAXUS BSC6900 SET CPUTHD(Optional) Meaning:DSP usage alarm threshold. When the AGEALMTHD DSP usage exceeds the threshold, a DSP usage alarm is reported. "DSP occupancy alarm clearance threshold" must be smaller than "DSP occupancy alarm threshold". GUI Value Range:30~100 Actual Value Range:30~100
Issue 03 (2012-05-30)
9-43
9 Parameters
Parameter ID
NE
MML Command
Description Unit:% Default Value:85
SysRrcRejNum BSC6900 SET Meaning:The parameter specifies the maximum UCALLSHOCKCTRL(O number of RRC Connection Reject messages per ptional) second from SPU subsystem to UE. When the SPU subsystem is in flow control state, the system will respond RRC Connection Reject message to UE. If the number of RRC Connection Reject messages exceeds the value of the parameter, RNC will discard the RRC connection request. GUI Value Range:1~500 Actual Value Range:1~500 Unit:None Default Value:100 T300 BSC6900 SET Meaning:T300 is started when UE sends the RRC UIDLEMODETIMER(Op CONNECTION REQUEST message. It is stopped tional) when UE receives the RRC CONNECTION SETUP message. RRC CONNECTION REQUEST will be resent upon the expiry of the timer if V300 is lower than or equal to N300, else enter idle mode. GUI Value Range:D100, D200, D400, D600, D800, D1000, D1200, D1400, D1600, D1800, D2000, D3000, D4000, D6000, D8000 Actual Value Range:100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000 Unit:ms Default Value:D2000 T302 BSC6900 SET Meaning:T302 is started after the UE transmits the UCONNMODETIMER( CELL UPDATE/URA UPDATE message and Optional) stopped after the UE receives the CELL UPDATE CONFIRM/URA UPDATE CONFIRM message. CELL UPDATE/URA UPDATE will be resent upon the expiry of the timer if V302 less than or equal to N302; otherwise, the UE will enter idle mode. Protocol default value is 4000. GUI Value Range:D100, D200, D400, D600, D800, D1000, D1200, D1400, D1600, D1800, D2000, D3000, D4000, D6000, D8000 Actual Value Range:100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000,
Issue 03 (2012-05-30)
9-44
9 Parameters
Parameter ID
NE
MML Command
Description 8000 Unit:ms Default Value:D2000
T381
BSC6900 SET Meaning:T381 is started after the RNC send UCONNMODETIMER( message "RRC CONNECTION SETUP"(or "CELL Optional) UPDATE CONFIRM"). If T381 expire and RNC does not receive "RRC CONNECTION SETUP COMPLETE"(or the response of "CELL UPDATE CONFIRM") and V381 is smaller than N381, RNC resend "RRC CONNECTION SETUP"(or "CELL UPDATE CONFIRM") and restart timer T381 and increase V381. If RNC receive "RRC CONNECTION SETUP COMPLETE"(or the response of "CELL UPDATE CONFIRM"), T381 will be stopped. Default value is 600ms. GUI Value Range:D0, D100, D200, D300, D400, D500, D600, D700, D800, D900, D1000, D1200, D1500, D2000 Actual Value Range:0, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1200, 1500, 2000 Unit:ms Default Value:D600
UserPlnCpuSha BSC6900 SET Meaning:The parameter is added to avoid ringOutOffset UUSERPLNSHAREPA ping-pong handovers during the load sharing RA(Optional) triggered by DSP CPU usage. GUI Value Range:5~20 Actual Value Range:5~20 Unit:% Default Value:5 UserPlnCpuSha BSC6900 SET Meaning:The parameter is added to trigger the load ringOutThd UUSERPLNSHAREPA sharing when the DSP CPU usage exceeds this RA(Optional) threshold, thus achieving load balance between subracks. GUI Value Range:0~100 Actual Value Range:0~100 Unit:% Default Value:100 UserPlnSharing BSC6900 SET Meaning:Percentage of User Plane Sharing Out
Issue 03 (2012-05-30)
9-45
9 Parameters
Parameter ID OutOffset
NE
MML Command
Description
UUSERPLNSHAREPA Offset. RA(Optional) GUI Value Range:5~20 Actual Value Range:5~20 Unit:% Default Value:5
UserPlnSharing BSC6900 SET Meaning:Percentage of User Plane Sharing Out OutThd UUSERPLNSHAREPA threshold. RA(Optional) GUI Value Range:0~100 Actual Value Range:0~100 Unit:% Default Value:90
Issue 03 (2012-05-30)
9-46
10 Counters
10 Counters
Table 10-1 Counter description Counter ID Counter Name Counter Description Feature ID Feature Name
67193095
VS.IU.FlowCtrl.DiscInitDT.CS
Number of Discarded CS Initial UE Messages when Signaling Flow Control is Triggered Number of Discarded PS Initial UE Messages when Signaling Flow Control is Triggered HR9750:Maximum CPU Usage of the GCU HR9760:Maximum CPU Usage of the DPU HR9730:Maximum CPU Usage of the SCU
WRFD-040100 Flow Control
67193096
VS.IU.FlowCtrl.Disc.InitDT.PS
67194447
VS.GCU.CPULOAD.MAX
WRFD-040100 Flow Control WRFD-040100 Flow Control WRFD-040100 Flow Control WRFD-040100 Flow Control
67194743
VS.DPU.CPULOAD.MAX
67194751
VS.SCU.CPULOAD.MAX
67203413
VS.CSLoad.Erlang.Equiv.CPUS Equivalent CS Conversational Erlang for CPUS VS.GCU.CPULOAD.MEAN AR9750:Average CPU Usage of the GCU
67204336
67204337
VS.GCU.CPULOAD.OVER
TR9750a:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the GCU Exceeds the Alarm Threshold TR9750b:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the GCU is Lower than the Alarm Threshold AR9760:Average CPU Usage of the DPU WRFD-040100 Flow Control
67204338
VS.GCU.CPULOAD.LESS
67204463
VS.DPU.CPULOAD.MEAN
67204464
VS.DPU.CPULOAD.OVER
TR9760a:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the DPU Exceeds the Alarm Threshold
Issue 03 (2012-05-30)
10-1
10 Counters
Counter ID Counter Name
Counter Description
Feature ID
Feature Name
67204465
VS.DPU.CPULOAD.LESS
TR9760b:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the DPU is Lower than the Alarm Threshold AR9730:Average CPU Usage of the SCU WRFD-040100 Flow Control
67204467
VS.SCU.CPULOAD.MEAN
67204468
VS.SCU.CPULOAD.OVER
TR9730a:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the SCU Exceeds the Alarm Threshold TR9730b:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the SCU is Lower than the Alarm Threshold Throughput of PS Uplink Data for MPU WRFD-040100 Flow Control
67204469
VS.SCU.CPULOAD.LESS
67204521
VS.PSLoad.ULThruput.MPU
67204522
VS.PSLoad.DLThruput.MPU
Throughput of PS Downlink WRFD-040100 Flow Data for MPU Control HR9780:Maximum CPU Usage of the XPU HR9782:Maximum Packet Usage of the XPU WRFD-040100 Flow Control WRFD-040100 Flow Control
73390062
VS.XPU.CPULOAD.MAX
73390070
VS.XPU.MSGLOAD.MAX
73393776
VS.LowPriRRC.RanFC.Disc.Nu Number of Low-Priority RRC WRFD-040100 Flow m Connection Setup Requests Control Discarded During RAN Integrated Flow Control for Cell VS.NormPriRRC.RanFC.Disc.N Number of Middle-Priority WRFD-040100 Flow um RRC Connection Setup Control Requests Discarded During RAN Integrated Flow Control for Cell VS.HighPriRRC.RanFC.Disc.Nu Number of High-Priority WRFD-040100 Flow m RRC Connection Setup Control Requests Discarded During RAN Integrated Flow Control for Cell
73393777
73393778
Issue 03 (2012-05-30)
10-2
10 Counters
Counter ID Counter Name
Counter Description
Feature ID
Feature Name
73403674
VS.INT.CPULOAD.MAX
HR9700:Maximum CPU Usage of the INT Duration of CPU Resource Insufficiency Reported by NodeB for Cell AR9780:Average CPU Usage of the XPU
WRFD-040100 Flow Control WRFD-040100 Flow Control
73411191
VS.NodeB.CPU.Cong.Dur
73415210
VS.XPU.CPULOAD.MEAN
73415211
VS.XPU.CPULOAD.OVER
TR9780a:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the XPU Exceeds the Alarm Threshold TR9780b:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the XPU is Lower than the Alarm Threshold AR9782:Average Packet Usage of the XPU AR9700:Average CPU Usage of the INT WRFD-040100 Flow Control WRFD-040100 Flow Control
73415212
VS.XPU.CPULOAD.LESS
73415214
VS.XPU.MSGLOAD.MEAN
73415843
VS.INT.CPULOAD.MEAN
73415844
VS.INT.CPULOAD.OVER
TR9700a:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the INT Exceeds the Alarm Threshold TR9700b:Rate of the Period WRFD-040100 Flow in Which the CPU Usage of Control the INT is Lower than the Alarm Threshold
73415845
VS.INT.CPULOAD.LESS
73421890
VS.LowPriRRC.FC.Disc.Num.C Number of Low-Priority RRC WRFD-040100 Flow PUS Requests Discarded Due to Control Flow Control for CPUS Subsystem VS.NormPriRRC.FC.Disc.Num. Number of Normal-Priority CPUS RRC Requests Discarded Due to Flow Control for CPUS Subsystem VS.HighPriRRC.FC.Disc.Num.CNumber of High-Priority WRFD-040100 Flow Control
73421891
73421892
WRFD-040100 Flow
Issue 03 (2012-05-30)
10-3
10 Counters
Counter ID Counter Name PUS
Counter Description RRC Requests Discarded Due to Flow Control for CPUS Subsystem
Feature ID
Feature Name Control
73421893
VS.LowPriRRC.FC.Disc.Time.C Duration of Rejection of WRFD-040100 Flow PUS Low-Priority RRC Requests Control Due to Flow Control for CPUS Subsystem VS.NormPriRRC.FC.Disc.Time. Duration of Rejection of CPUS Normal-Priority RRC Requests Due to Flow Control for CPUS Subsystem WRFD-040100 Flow Control
73421894
73421895
VS.HighPriRRC.FC.Disc.Time. Duration of Rejection of WRFD-040100 Flow CPUS High-Priority RRC Requests Control Due to Flow Control for CPUS Subsystem VS.CBS.FC.Disc.Num.CPUS Number of CBS Requests Discarded Due to Flow Control for CPUS Subsystem Duration of CBS Flow Control for CPUS Subsystem WRFD-040100 Flow Control
73421896
73421897
VS.CBS.FC.Disc.Time.CPUS
73421898
VS.Paging.FC.Disc.Num.CPUS Number of Paging WRFD-040100 Flow Messages Discarded Due to Control Flow Control for CPUS Subsystem VS.Paging.FC.Disc.Time.CPUS Duration of Paging Message WRFD-040100 Flow Flow Control for CPUS Control Subsystem VS.CU.FC.Disc.Num.CPUS Number of Cell Update WRFD-040100 Flow Requests Discarded Due to Control Flow Control for CPUS Subsystem Duration of Cell Update Flow WRFD-040100 Flow Control for CPUS Control Subsystem
73421899
73421900
73421901
VS.CU.FC.Disc.Time.CPUS
73423464
VS.RRC.FC.Disc.Num.CallShocNumber of Discarded RRC WRFD-040100 Flow
Issue 03 (2012-05-30)
10-4
10 Counters
Counter ID Counter Name k.CPUS
Counter Description Connection Requests Due to Burst Traffic for CPUS Subsystem
Feature ID
Feature Name Control
73423465
VS.RRC.FC.Disc.Num.MPU.CP Number of Discarded RRC WRFD-040100 Flow US Connection Requests Due to Control MPU Overload for CPUS Subsystem VS.RRC.FC.Disc.Num.RRCQu Number of Discarded RRC WRFD-040100 Flow eue.CPUS Connection Requests Due to Control RRC Queue Overflow for CPUS Subsystem VS.RRC.FC.Disc.Num.CPU.CP Number of Discarded RRC WRFD-040100 Flow US Connection Requests Due to Control High CPU Usage for CPUS Subsystem VS.RRC.FC.Disc.Num Number of Discarded RRC WRFD-040100 Flow Connection Requests Due to Control Various Flow Control Functions for Cell WRFD-040100 Flow Control
73423466
73423467
73423468
73423829
VS.INT.CFG.INTERWORKING. T6900:Number of Call NUM Establishment Attempts on an Interface Board VS.INT.CFG.INTERWORKING.F T6920:Number of Call AIL.NUM Establishment Failures on an Interface Board
73423830
Issue 03 (2012-05-30)
10-5
11 Glossary
11 Glossary
For terms that appear in this document, see Glossary.
Issue 03 (2012-05-30)
11-1
12 References
12 References
[1] Load Control Feature Parameter Description [2] Call Admission Control Feature Parameter Description [3] DSAC Feature Parameter Description [4] Common Radio Resource Management Feature Parameter Description [5] Transmission Resource Management Feature Parameter Description [6] Radio Bearers Feature Parameter Description [7] State Transition Feature Parameter Description
Issue 03 (2012-05-30)
12-1
13 Appendix - Flow Control Algorithms

The RNC uses three types of flow control algorithms for overloaded RNC units: the switch algorithm, linear algorithm, and hierarchical algorithm. Different algorithms are used for different services. These algorithms, however, cannot be set on the LMT.
13.1 Switch Algorithm

The principles of the switch algorithm are as follows:

When resource usage, such as CPU usage or message block usage, exceeds the control threshold of a flow control item, flow control is performed. When resource usage is lower than the restore threshold, flow control is not performed.
Figure 13-1 Switch algorithm
The following flow control functions use switch algorithms: printing flow control, debugging flow control, performance monitoring flow control, logging flow control, resource audit flow control, AC, paging control, RRC flow control based on the CPU usage and message block, Iur flow control, CBS flow control, cell/URA update flow control, Iur-g flow control, and MR flow control.
13.2 Linear Algorithm

The principles of the linear algorithm are as follows:

When resource usage is higher than the control threshold of a flow control item, flow control is performed. When resource usage is lower than the restore threshold of a flow control item, flow control is not performed. When resource usage is between the restore threshold and the control threshold of a flow control item, the flow control level changes linearly with the resource usage.
Issue 03 (2012-05-30)
13-1
Figure 13-2 Linear algorithm
The flow control level of the linear algorithm, that is, the probability (P) of performing flow control, is calculated as follows: P = (resource usage restore threshold) x 100%/ (control threshold restore threshold) The following flow control function uses a liner algorithm: Flow Control Triggered by DSP CPU Overload.
13.3 Hierarchical Algorithm

The principles of the hierarchical algorithm are as follows:

When resource usage is higher than the control threshold of a flow control item, flow control is performed. When resource usage is lower than the restore threshold of a flow control item, flow control is not performed. When resource usage is between the restore threshold and the control threshold of a flow control item, the flow control level changes hierarchically with the resource usage.
Figure 13-3 Hierarchical algorithm
Issue 03 (2012-05-30)
13-2
The flow control level of the hierarchical algorithm is calculated as follows: Flow control level = [ (resource usage restore threshold) x total number of flow control grades for the flow control item/ (control threshold restore threshold)]
The [ ] symbol indicates an integer value.
The total flow control grades for each flow control item are specified in the system software and cannot be set on the LMT. They vary according to the flow control items. The following flow control function uses hierarchical algorithm: MPU overload backpressure.
Issue 03 (2012-05-30)
13-3

Flow Control (RAN13.0 03)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Flow Control (RAN13.0 03)

Загружено:

Авторское право:

Доступные форматы

Flow Control RAN13.

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units.............................................................................3-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

3.8.1 Principle .............................................................................................................................. 3-21 3.8.2 Overload Indication............................................................................................................. 3-22

4 Flow Control Triggered by NodeB/Cell Overload .............................................................4-1

5 Flow Control over the Iu Interface ........................................................................................5-1

6 Service Flow Control ...............................................................................................................6-1 7 Load Sharing ..............................................................................................................................7-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

1.2 Intended Audience

1.3 Change History

03 (2012-05-30) 02 (2011-10-30) 01 (2011-04-30) Draft B (2011-03-30) Draft A (2010-12-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

Change Type Feature change

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

Editorial change Added "MPU Overload Backpressure."

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

It restricts incoming traffic to:

It restricts outgoing traffic to reduce the load on the peer equipment.

2.2 Overall Picture of Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units

3 Flow Control for Overloaded RNC Units

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units

3.1.2 CPU Usage Monitoring

3.1.3 Message Block Occupancy Rate Monitoring

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units

3.2 Whole Picture of Flow Control for Overloaded RNC Units

High CPU usage or message block occupancy rate

SET FCSW SET FCSW None SET UCACALGOSWITCH SET FCSW

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units

Flow Control Object

High CPU usage

Congestion in queues at the ports

High CPU usage or message block occupancy rate

Printing Debugging Logging BE service rates

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Flow Control

3 Flow Control for Overloaded RNC Units

Flow Control Object

Printing Debugging Performance monitoring Logging Printing Debugging Logging

High CPU usage or message block occupancy rate

Printing flow control Debugging flow control Logging flow control