You are on page 1of 23

RAN

Flow Control Parameter Description

Issue

01

Date

2009-03-30

Huawei Proprietary and Confidential
Copyright © Huawei Technologies
Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address:

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

Website:

http://www.huawei.com

Email:

support@huawei.com

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

Ltd 2008-12-09 2009-01-10 2009-03-30 3 ..RAN Flow Control Parameter Description About This Document About This Document Author Prepared by Qian Yan Date 2008-10-16 Edited by Reviewed by Translated by Tested by Approved by Sun Jingshu Date Date Date Date Date 2008-12-09 Issue 01 (2009-03-30) Fang Qin Lu Feng Duan Zhongyi Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

.................................................................2 Linear Algorithm.................3-3 3............................2 Load Balancing on the User Plane.....................................3-3 3...............3-3 3.........................................................................................................................................7 Signaling Flow Control of the Iu Interface..................3 Flow Control Thresholds (Message Block Usage)...................................................................................................................................................................................1 Description.............................................................................................................................3-3 3...............................................................................................................................1 Switch Algorithm.............................. 2-3 3 Flow Control Principles........................................................................................................4-3 5 Reference Documents......1-3 2 Introduction............................................2 Flow Control Items.............................................................3 Hierarchical Algorithm.............................1 Load Balancing on the Control Plane........3-3 3......................7.................................4-3 4...........................................3-3 3............1 System Resources.......................................................3-3 4 Flow Control Parameters.......................................................3-3 3................................3-3 3...........................2 Values and Ranges.........................................................................6 Access Class Restriction..........4................................................................................................4..............................................................1....5.......8 Signaling Flow Control of the Iub Interface...................RAN Flow Control Parameter Description Contents Contents 1 Change History.................................................................3-3 3..................................................................................................................................................................3-3 3....................................................3-3 3...................................................................................7...................1 Flow Control System Model...3-3 3...........5...........3-3 3.......4...............3-3 3.....2 Congestion in the Peer SCCP Subsystem.............1..............................................................................................................................5-3 Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.........................................................................................................................3-3 3............3-3 3...........................................2 Flow Control Thresholds (CPU Usage)............................................................3-3 3......4-3 4...................1 Congestion in Signaling Links on the Iu Interface...........................................................................................4 Flow Control Algorithms....5 RNC Load Balancing........................................................ Ltd 5 ..................

1. 01 (2009-03-30) This is the document for the first commercial release of RAN11.  Editorial change: refers to the change in the information that was inappropriately described or the addition of the information that was not described in the earlier version.0 11.0 11.1. There are two types of changes. draft (2009-03-10) optimizes the description.I. which are defined as follows:  Feature change: refers to the change in the flow control.0.1. this issue optimizes the description. Compared with draft (2009-03-10).0 This document is based on the BSC6810 and 3900 series NodeBs. Draft (2009-01-15) This is the initial draft of the document for RAN11. Compared with draft (2009-01-15).1.0.0. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The available time of each feature is subject to the RAN product roadmap.RAN Flow Control Parameter Description 1 Change History 1 Change History The change history provides information on the changes in different document versions.1 Document and product versions Document Version RAN Version 01 (2009-03-30) Draft (2009-03-10) Draft (2009-01-15) 11. Ltd 1 .. Draft (2009-03-10) This is the second draft of the document for RAN11.1. Document and Product Versions Table 1.

Ltd 3 ..RAN Flow Control Parameter Description Issue 01 (2009-03-30) 1 Change History Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

1.1.1 NEs involved in flow control UE NodeB RNC MSC Server MGW SGS N GGS N HLR - - √ √ √ √ - - Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.I.. Network Elements Involved Table 2. Ltd 1 .  Impact on other features None.1. Flow control is a set of mechanisms applied to the RNC to prevent the system from being overloaded.RAN Flow Control Parameter Description 2 Introduction 2 Introduction Flow control refers to the internal flow control of the Radio Network Controller (RNC) by regulating the input transmission rate. Flow control is performed to:  Ensure system stability and robustness. Flow control suppresses and prevents overload in the RNC. Therefore.1. Thus.  Impact on system performance Impact Frequent flow control decisions affect the system performance.I. flow control ensures the stable performance of the RNC.  Personnel working on Huawei products or systems. which is called feedback flow control mechanism.1 lists the Network Elements (NEs) involved in flow control.1.1.1.1.1.  Ensure that the high-priority services work normally when the traffic is heavy.1. Intended Audience This document is intended for:  System operators who need a general understanding of flow control. Table 2. the interval between flow control decisions cannot be too short.

Ltd 3 . MSC Server = Mobile Service Switching Center Server..RAN Flow Control Parameter Description UE 2 Introduction NodeB RNC MSC Server MGW SGS N GGS N HLR NOTE  -: not involved  √: involved UE = User Equipment. MGW = Media Gateway. RNC = Radio Network Controller. HLR = Home Location Register Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. GGSN = Gateway GPRS Support Node. SGSN = Serving GPRS Support Node.

I.1 Flow control system model 1 System Resources The system determines whether to enable flow control based on the current system flow.1.1.RAN Flow Control Parameter Description 3 3 Flow Control Principles Flow Control Principles 3.1.. Figure 3.1.1.1 Flow Control System Model RNC board software performs real-time monitoring of system resources.1. Ltd 1 .I. Figure 3. Flow control decisions are based on the usage of the key system resources such as the CPU and message blocks.1 shows the flow control system model of the RNC.1. It obtains the internal flow conditions by monitoring the following RNC system resources: Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1.

2.1.  Message block usage The message block is the primary resource for communication in the RNC. This ensures proper functioning of the system. the flow control for the corresponding function is enabled.2.1. When the CPU usage is lower than a specified threshold. or partially disables the functions according to the current CPU usage and message block usage to ensure system stability and robustness. the corresponding function is disabled or partially disabled. disables.I. The system enables.1 lists the flow control items for the RNC boards and subsystems. When the message block usage is lower than a specified threshold. Ltd 3 . the flow control for the corresponding function is disabled.1.1.1. the flow control for corresponding functions is disabled.2 Flow Control Items Each flow control item corresponds to a function in the system.  If a flow control item is restored. In this case..  If a flow control item is controlled. Table 3. 3.1.1.I. the corresponding function is enabled again.1 Flow control items for RNC boards Board Type on the LMT Flow Control Item SCUa  Printing  Debugging  Performance monitoring  Log  Printing  Debugging  Performance monitoring  Resource auditing  Paging  Handover  Iur uplink transfer  Iur downlink transfer  CBS  Log  Access control  Cell URA update  Printing  Debugging  Performance monitoring SPUa DPUb Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.RAN Flow Control Parameter Description  3 Flow Control Principles CPU usage The CPU is the primary resource for the system processing capabilities. When the CPU usage reaches a specified threshold. the flow control for corresponding functions is enabled to ensure proper functioning of the system.1.1. Table 3. High message block usage indicates a risk of insufficient processing capability in the system.

2 Flow Control Thresholds (CPU Usage) The system checks the CPU usage once a second. flow control is performed. the average value of CPU usage measured during the previous seconds is used.1.2.I.1. Ltd 5 .. The data in the previous seconds forms a filter window.2.I.1 Filter window Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. When the CPU usage reaches a specified threshold and the flow control switch is on. as shown in Figure 3. Figure 3.1.1. To minimize the impact of instant fluctuation of the CPU usage on the flow control decision.1.1.1.RAN Flow Control Parameter Description 3 Flow Control Principles Board Type on the LMT AEUa/PEUa/AOUa/UOIa/FG2a/GOUa/POUa GCUa/GCGa MPU Flow Control Item  Log  Printing  Debugging  PVC  Log  Printing  Debugging  Performance monitoring  Log  Printing  Debugging  Performance monitoring  Resource auditing  Paging  Handover  Iur uplink transfer  Iur downlink transfer  CBS  Log  Access control  Cell URA update 3.

The critical threshold takes precedence over the thresholds of other flow control items. and they are defined by the system software. all the flow control items are put under control.RAN Flow Control Parameter Description 3 Flow Control Principles When the average CPU usage in the filter window reaches or exceeds the corresponding control threshold. Each flow control item for the message block flow control has two thresholds: the flow control item control threshold and the flow control item restore threshold. If all the CPU usage values in the fast judgment window reach or exceed the critical threshold. the control mechanism of the critical threshold takes effect when the CPU usage reaches the critical threshold.3 Flow Control Thresholds (Message Block Usage) A decision on the message block usage is made by the system when the system allocates the message for the 10th time. the control mechanism of the critical threshold takes effect when the message block usage reaches the critical threshold. fast judgment window. To prevent state transition of flow control due to instant increase of the message block usage. the associated flow control mechanism is started. The decisions of other flow control thresholds are effective only when the CPU usage is lower than the critical threshold. The decisions of other flow control thresholds are effective only when the message block usage is lower than the critical threshold. When the message block usage reaches a specified threshold. 3. That is. That is. the system provides the filter window. critical threshold. the associated flow control mechanism is started. Message blocks are essential to internal communication of the system. The critical threshold decision does not use the filter mechanism. the associated flow control mechanism is stopped. the size of the filter window is 1. all the flow control items are put under control. the system provides the fast judgment window. When the message block usage reaches or exceeds the critical threshold.. the system compares the average CPU usage measured in the preceding period with the critical threshold. To control the flow in the case that the CPU usage becomes high within a short period. flow control is started. critical threshold.  When the average message block usage in the filter window reaches or exceeds the corresponding control threshold. The filter window.  When the average message block usage is lower than the restore threshold. Ltd 7 . The critical threshold takes precedence over the thresholds of other flow control items. and flow control item control threshold and restore threshold of each type of board are different. the system compares the average message block usage measured in the preceding period with the threshold. Therefore. That is. The system collapses once the message blocks are exhausted. That is. and flow control item control threshold and restore threshold of each type of board are different. the system provides a critical threshold for the message block usage. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. When the average CPU usage is lower than the corresponding restore threshold. the associated flow control mechanism is stopped. The filter window. and they are defined by the system software. That is.

4.2.4. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1 Switch Algorithm The principles of the switch algorithm are as follows:  When the resource usage. the flow control function for the item is disabled.RAN Flow Control Parameter Description 3 Flow Control Principles 3.4.I.  When the resource usage is between the restore threshold and the control threshold.4. is higher than the control threshold of a flow control item.1. flow control is not performed.1. flow control is performed. 3.  When the resource usage is lower than the restore threshold. These algorithms. Figure 3.  When the resource usage is lower than the restore threshold of a flow control item. such as the CPU usage or message block usage. Figure 3.1 shows the switch algorithm.I. the flow control level changes linearly with the resource usage. the flow control function for the item is enabled. Figure 3.4 Flow Control Algorithms Three types of flow control algorithms are adopted in the RNC: switch algorithm.1.4.1.1.1 shows the linear algorithm.1 Switch algorithm 3.1.1.. linear algorithm. and hierarchical algorithm. however. cannot be set on the RNC LMT.2 Linear Algorithm The principles of the linear algorithm are as follows:  When the resource usage is higher than the control threshold of a flow control item. Different services usually use different algorithms.I.1. Ltd 9 .

flow control is not performed.1. that is.1 Linear algorithm The flow control level of the linear algorithm.1..I.4.  When the resource usage is lower than the restore threshold of a flow control item. the flow control level changes hierarchically with the resource usage.RAN Flow Control Parameter Description 3 Flow Control Principles Figure 3.3 Hierarchical Algorithm The principles of the hierarchical algorithm are as follows:  When the resource usage is higher than the control threshold of a flow control item. Figure 3.4.3.1.1.1 shows the hierarchical algorithm.I. flow control is performed.  When the resource usage is between the restore threshold and the control threshold.1 Hierarchical algorithm The flow control level of the hierarchical algorithm is calculated as follows: Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.I.2.1. Ltd 11 .4.1. the probability (P) of the flow control item being disabled. Figure 3.4.3. is calculated as follows: P = (resource usage – restore threshold) x 100%/(control threshold – restore threshold) 3.

3. Hereinafter. 3. The SPU can be in one of the three states shown in Figure 3.I.RAN Flow Control Parameter Description 3 Flow Control Principles Flow control level = [(resource usage – restore threshold) x total number of flow control grades for the flow control item/(control threshold – restore threshold)] [ ] means that an integer value is taken.1.5.5. State I requires the following conditions to be met:  The message block load is lower than the message block overload threshold.1. other than the MPU.1.1 Load Balancing on the Control Plane When a service request arrives.1 Load states of the control plane State I: The SPU has a light load. and they cannot be set on the LMT. and the subrack that is connected to a NodeB over the Iub interface refers to the host subrack of the NodeB. The MPU maintains control plane and user plane resources in the subrack and performs Destination Signaling Point (DSP) status management. the term SPU refers to an SPU subsystem on an SPUa board.5. can be responsible for signaling processing. In the RNC.1.5 RNC Load Balancing Load balancing on the control plane and user plane can be implemented on the basis of resource sharing. Any SPU subsystem. The flow control grades may differ for different flow control items. Ltd 13 ..1. Each SPUa board has four subsystems. The total flow control grades for each flow control item are specified in the system software.I. and the CAPS is lower than the value of MaxCAPSLowLoad. called Main Processing Unit (MPU). the SPU determines whether to process the service request directly or to forward it to the MPU according to the current load and Call Attempts per Second (CAPS).1. subsystem 0 of the main control SPUa board in a subrack is the main control Signaling Process Unit (SPU) subsystem.  The CPU load is lower than the value of CtrlPlnSharingOutThd. Figure 3. the SPU that controls a NodeB refers to the host SPU of the NodeB. By default. Alternatively.1. the CPU load is lower than Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

If the MPU fails to find a proper SPU. In addition. or if the load of the host SPU minus the value of CtrlPlnSharingOutOffset is higher than the load of any other SPU in the host subrack. and the CAPS is lower than the value of SharingOutCAPSMidLoad.1 shows how the MPUs manage and allocate user plane resources. The MPU maintains the user plane resources in the subrack and performs DSP status management. the service request is rejected.. In state II.I. that is. State II requires the following conditions to be met:  The message block load is lower than the message block overload threshold. Ltd 15 . the MPU in the subrack exchanges user plane load information with other MPUs. In state I. the MPU forwards the service request to the SPU with the minimum load in the host subrack.RAN Flow Control Parameter Description 3 Flow Control Principles the CPU overload threshold. State III refers to any state other than states I and II.  The CPU load is between the CPU overload threshold and the value of CtrlPlnSharingOutThd.1. If the load of the host SPU is equal to or higher than the CPU overload threshold. State II: The SPU shares out its load. the SPU processes all received service requests and accepts the service requests forwarded by the MPU.  If the control plane load of the host subrack minus the value of CtrlPlnSharingOutOffset is higher than the control plane load of any other subrack.5. the host subrack. the MPU in the host subrack forwards the service request to the MPU in the RNC with the minimum control plane load.1.  Otherwise. the SPU forwards all received service requests to the MPU and accepts the service requests forwarded by the MPU.2 Load Balancing on the User Plane The MPU in a subrack manages and allocates the user plane resources in the subrack. and the CAPS is between the value of SharingOutCAPSMidLoad and the value of MaxCAPSMidLoad. the SPU forwards all received service requests to the MPU. or the host SPU forwards the service request to the MPU for further processing if the SPU is in state II or III. When a service request arrives.5. State III: The SPU is overloaded. but the MPU does not forward any service request to this SPU. In state III. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The target MPU then forwards the service request to the SPU with the minimum load in the target subrack. the host SPU processes the service request if the SPU is in state I.2. the MPU selects an SPU from the same subrack. the MPU forwards the resource requests to other subracks. 3. Figure 3. When the load of the subrack is heavy. In the case of state II or III. the MPU selects a proper SPU in either the host subrack or a different subrack to process the service request.

Ltd 17 .1.5. or if the user plane load of the host subrack minus the value of UserPlnSharingOutOffset is higher than the user plane load of any other subrack. then the MPU allocates the user plane resources of the DSP with the minimum load in the host subrack to the service. In this case. the access class restriction function provides access flow control. thus reducing the signaling load (call attempts). the service applies for user plane resources. The RNC performs the access class restriction for all cells under the SPU subsystem at intervals specified by AcIntervalOfCell. or if the user plane load of the host subrack plus the value of UserPlnSharingOutOffset is lower than the user plane load of any other subrack. the access class restriction function is enabled.6 Access Class Restriction When the resource usage of the SPU subsystem is high. To enable the access class restriction function.  If the subrack with the minimum load in the RNC is overloaded.RAN Flow Control Parameter Description 3 Flow Control Principles Figure 3.1 User plane resource sharing When a service request arrives. The MPU proceeds as follows:  If the user plane load of the host subrack is lower than the value of UserPlnSharingOutThd.1.2.  Issue 01 (2009-03-30) If the CPU usage or message block usage of an SPU subsystem is higher than the value of AC control threshold. ensure that AcRstrctSwitch is set to ON. The RNC monitors the CPU usage and message block usage of the SPU subsystem in real time. Only specific UEs are permitted to access the network. 3. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the SPU requests the MPU in the host subrack for the resources.I.. The target MPU then allocates the resources of the DSP with the minimum load in the target subrack to the service.  If the user plane load of the host subrack is equal to or higher than the value of UserPlnSharingOutThd. then the MPU selects the subrack with the minimum load in the RNC and forwards the user plane resource request to the MPU in the target subrack. the service request is rejected.

The UE services are categorized into 15 access classes: AC0 to AC14.1.I. 3. The value of AcRstrctPercent determines the number of AC services to be restricted.7 Signaling Flow Control of the Iu Interface When a signaling link on the Iu interface or the peer SCCP subsystem is congested. When a signaling link on the Iu interface is congested.I. The access class restriction is triggered when either of the resource usage reaches its associated AC control threshold. Emergency calls are not rejected.1 Example of 10% access class restriction The monitoring mechanism of the CPU usage and that of the message block usage are independent from each other.RAN Flow Control Parameter Description  3 Flow Control Principles If the CPU usage or message block usage of an SPU subsystem is lower than the value of AC restore threshold.1. only a certain percentage (defined by AcRstrctPercent) of the 10 access classes are restricted.1.  You can run the MML command SET ACALGO to set the value of AcRstrctPercent. If AcRstrctPercent is set to 1.1 shows an example of 10% access class restriction.6. the barred access classes are unrestricted and another set of access classes are restricted. one AC service is restricted during access polling. if AcRstrctPercent is set to 2.  The value of AcRstrctPercent for AC0 to AC9 ranges from 1 to 10.1. Figure 3.. The AC control threshold and the AC restore threshold are defined by the system software. In the next period. The access class restriction applies sequentially to access classes AC0 to AC9 only. two AC services are restricted during access polling.6. At any time during a specified period defined by AcRstrctIntervalLen. the RNC rejects services selectively based on the congestion level.1. Ltd 19 . This process goes on until the CPU usage or message block usage becomes normal.1. the signaling flow control helps the link recover soon by reducing the flow on the link. the access class restriction function is disabled and all restricted access classes of the cells are not barred. When the peer SCCP subsystem is Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Figure 3.

When a Radio Resource Control (RRC) connection is set up. call. the RNC determines whether to start flow control according to the congestion level and the service type of the RRC connection. The RRC connection services are of three types: short message service. the RNC rejects the RRC connection requests of services other than emergency calls and Attach and Detach services. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.1 Congestion in Signaling Links on the Iu Interface The RNC checks the load of signaling links on the Iu interface and takes relevant measures if the load is heavy. and location registration.. In this way. Ltd 21 .RAN Flow Control Parameter Description 3 Flow Control Principles congested. 3.2 Congestion in the Peer SCCP Subsystem If the peer SCCP subsystem is congested. the signaling flow control helps the subsystem recover soon by reducing the signaling exchange between the RNC and the peer SCCP subsystem. the RNC receives an SCCP Subsystem-Congested (SCCP-SSC) message from the peer equipment. With the increase of the load. this RRC connection setup request is rejected. based on the congestion status reported from the lower layer.8 Signaling Flow Control of the Iub Interface The RNC checks the load of signaling links on the Iub interface. All the three types of services use the linear algorithm for flow control. The signaling flow control of the Iub interface helps to ease the congestion caused by the increase of the NCP link load and enables the NCP link to recover more rapidly. the flow control mechanism ensures that the admitted services are effectively processed in the system and that the services beyond the load capacity of the RNC are temporarily barred from the network to avoid continuous overloading of the system. This message indicates the congestion level.7. The congestion levels range from 0 through 8. the RNC rejects setup of services upon congestion in the following order: short message service > call > location registration service. 3. The SCCP over the Iu interface determines the congestion level. where 0 denotes no congestion and 8 denotes the severest congestion. If the flow control conditions are met. According to the characteristics of services.7. When the load is heavy. 3. the RNC rejects the access of services with lower priority and then those with higher priority.

you can select some ACs from AC0 to AC9 based on the ratio specified in this parameter and perform AC restriction on the selected ACs. When a cell performs AC restriction. the subsystem selects the second cell and the first cell is still with AC restriction. and number of incoming calls in each second reaches the threshold.1. ON indicates that the AC algorithm is automatically enabled. After waiting for the time specified in this parameter. OFF indicates that the AC algorithm is automatically disabled. Interval of automatic AC restriction between cells.011. After AC restriction goes on for AcRstrctIntervalLen. Specifies the interval delay between consecutive pollings according to the flexible polling restriction mode.1. When the CPU usage is between the sharing out threshold and overload threshold. This parameter is used for preferable selection of the homing subrack and homing subsystem during call forwarding. When a subsystem of an RNC performs AC restriction on cells managed by this subsystem. new arrival call attempts will be shared out to other SPU. Percentage of User Plane Sharing Out Offset.RAN Flow Control Parameter Description 4 1 4 Flow Control Parameters Flow Control Parameters Description Table 4..I. and call number in each second reaches [SharingOutCAPSMidLoad]. and call number in one second reaches the UserPlnSharingOutThd UserPlnSharingOutOffset AcRstrctSwitch AcRstrctPercent AcIntervalOfCell AcRstrctIntervalLen CtrlPlnSharingOutThd SharingOutCAPSMidLoa d MaxCAPSMidLoad Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the original AC restriction is released and other ACs of the local cell are selected for AC restriction based on the ratio specified in this parameter. it selects the first cell at random.1. Access restriction ratio. Maximum numbers of incoming calls in one second when the load exceeds the forwarding threshold. Ltd 1 .1 Flow control parameter description Parameter ID Description CtrlPlnSharingOutOffset The sharing offset should be added to the target subrack or subsystem. The process lasts until all the cells are going through AC restriction. Forwarding threshold of control plane load sharing. For detailed information of this parameter. Numbers of incoming calls to be shared when the load exceeds the forwarding threshold. new arrival call attempts will be shared out to other CPU. When the CPU usage is between the sharing out threshold and overload threshold. refer to 3GPP TS 22.1. When the CPU usage is between the sharing threshold and overload threshold.1. Percentage of User Plane Sharing Out threshold.

1.. and call numbers in each second reach the threshold. step:10 ms SET ACALGO(Mandatory) RNC AcRstrctInter valLen - 6~3600 6~3600 None SET DSACAUTOALGO(M andatory) SET ACALGO(Mandatory) RNC CtrlPlnShari ngOutThd - 0~100 0~1. step:0. 4.1. When the CPU usage is lower than the sharing out threshold and overload threshold.2.1.1~1.1.2 Values and Ranges Table 4. Maximum numbers of incoming calls in one second when the load is lower than the forwarding threshold. ON None SET ACALGO RNC AcRstrctPerc ent - 1~10 0.01 per cent SET CTRLPLNSHAREPA RA(Optional) RNC SharingOutC APSMidLoa d - 0~255 0~255 None SET CTRLPLNSHAREPA RA(Optional) RNC MaxCAPSM idLoad - 0~255 0~255 None SET CTRLPLNSHAREPA RA(Optional) RNC MaxCAPSL owLoad - 0~255 0~255 None SET CTRLPLNSHAREPA RA(Optional) RNC Issue 01 (2009-03-30) Value Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.RAN Flow Control Parameter Description Parameter ID 4 Flow Control Parameters Description MaxCAPSLowLoad threshold. ON OFF. new arrival call attempts will be shared out to other SPU and none will be shared in this SPU. Ltd 3 .I.01~0. step:0.01 per cent SET CTRLPLNSHAREPA RA(Optional) RNC 50~100 50~100 per cent SET USERPLNSHAREPA RA(Optional) RNC - 5~20 5~20 per cent SET USERPLNSHAREPA RA(Optional) RNC AcRstrctSwit ch - OFF.1 per cent SET ACALGO(Mandatory) RNC AcIntervalOf Cell - 1~36000 10~360000. step:0.1.1 Flow control parameter values and parameter ranges Parameter ID Default Value GUI Value Range Actual Range CtrlPlnShari ngOutOffset - 1~10 UserPlnShari ngOutThd - UserPlnShari ngOutOffset Unit MML Command NE 0. new arrival call attempts will be shared out to other SPU and none will be shared in this SPU.

Ltd 5 . The "-" symbol indicates no default value. Issue 01 (2009-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co..RAN Flow Control Parameter Description 4 Flow Control Parameters The Default Value column is valid for only the optional parameters.

5 .5 Reference Documents The following lists the reference documents related to the feature: 1.0 V1.0 V1. Basic Feature Description of Huawei UMTS RAN11.5 2. Optional Feature Description of Huawei UMTS RAN11.