automatic congestion handler(ran16.0_draft a)

WCDMA RAN

Automatic Congestion HandlerFeature Parameter Description

Issue Draft ADate 2014-01-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue Draft A (2014-01-20) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................12 Overview.........................................................................................................................................22.1 Background.....................................................................................................................................................................22.2 Introduction....................................................................................................................................................................22.3 Benefits...........................................................................................................................................................................23 Technical Description...................................................................................................................33.1 Introduction....................................................................................................................................................................33.2 Principles........................................................................................................................................................................33.2.1 Decision Conditions for Different Congestion States.................................................................................................43.2.2 Automatic Congestion Relief Actions.........................................................................................................................64 Related Features...........................................................................................................................115 Network Impact...........................................................................................................................126 Engineering Guidelines.............................................................................................................146.1 When to Use Automatic Congestion Handler..............................................................................................................146.2 Required Information...................................................................................................................................................146.3 Network Planning.........................................................................................................................................................196.4 Deployment..................................................................................................................................................................196.4.1 Requirements.............................................................................................................................................................206.4.2 Data Preparation........................................................................................................................................................206.4.3 Precautions.................................................................................................................................................................236.4.4 Hardware Adjustment................................................................................................................................................236.4.5 Activation..................................................................................................................................................................236.4.5.1 Using MML Commands.........................................................................................................................................246.4.5.2 MML Command Examples....................................................................................................................................276.4.5.3 Using the CME(Applies to features not supported by batch modification)...........................................................286.4.6 Activation Observation..............................................................................................................................................286.4.7 Deactivation...............................................................................................................................................................29

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription Contents


ii

6.4.7.1 Using MML Commands.........................................................................................................................................296.4.7.2 MML Command Examples....................................................................................................................................296.4.7.3 Using the CME.......................................................................................................................................................296.4.8 Reconfiguration.........................................................................................................................................................296.5 Performance Monitoring...............................................................................................................................................296.6 Parameter Optimization................................................................................................................................................316.7 Troubleshooting............................................................................................................................................................317 Parameters.....................................................................................................................................328 Counters........................................................................................................................................959 Glossary.........................................................................................................................................9610 Reference Documents...............................................................................................................97

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription Contents


iii

1 About This Document1.1 Scope

This document describes the WRFD-160253 Automatic Congestion Handler feature, includingthe working principles, related features, network impact, and engineering guidelines.

1.2 Intended AudienceThis document is intended for personnel who:l Need to understand the features described hereinl Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:l Feature change

Changes in features of a specific product versionl Editorial change

Changes in wording or addition of information that was not described in the earlier version

Draft A (2014-01-20)This document is created for RAN16.0.

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 1 About This Document


1

2 Overview2.1 Background

Unplanned events, such as parades or major assemblies, often result in network congestion andthe congestion state is unpredictable. In this case, network configuration optimization cannot beperformed in advance. With Automatic Congestion Handler, congestion relief actions can beautomatically performed in these scenarios.

2.2 IntroductionAutomatic Congestion Handler monitors network congestion in real time. If network congestionoccurs, this feature automatically performs corresponding congestion relief actions based on thecongestion state. This relieves network congestion.

2.3 BenefitsThis feature automatically relieves the congestion in scenarios where unplanned events occur,thereby reducing the operation and maintenance workload. This improves system stability andoptimizes system performance.

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 2 Overview


2

3 Technical Description3.1 Introduction

This feature monitors load-related measurement quantities for a cell in real time. If ameasurement quantity or a set of measurement quantities meets certain requirements, the RNCdetermines that the cell is congested and performs corresponding congestion relief actions, whichcan be implemented by activating existing congestion relief algorithms or adjusting the settingsof existing network configuration parameters.

3.2 PrinciplesWhen the automatic congestion control switch (ADAP_CELL_CONGEST_SWITCH underthe AdapAlgoSwitch parameter) is set to on, the RNC determines the congestion state of a cellbased on measurement quantities such as downlink non-HSPA power load, actual uplink load,and number of users on the DCH.After determining the congestion state, the RNC performs corresponding congestion reliefactions to improve the cell performance. Figure 3-1 shows the mapping between congestionstates and congestion relief actions.

Figure 3-1 Mapping between congestion states and congestion relief actions

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 3 Technical Description


3

NOTE

The preceding figure shows only the working principle of the automatic congestion control algorithm. Fordetails about how to determine the congestion states in actual conditions, see section 3.2.1 DecisionConditions for Different Congestion States.

3.2.1 Decision Conditions for Different Congestion StatesThe RNC determines the load state of a cell based on the following measurement objects:l Downlink power load of a cell: This measurement object includes the downlink non-HSPA

power load. For details about the downlink non-HSPA power load, see section "LoadMeasurement" in Load Control Feature Parameter Description.

l Uplink power load of a cell: This measurement object includes the actual uplink load andnumber of users on the DCH.

NOTE

If the actual uplink load cannot be obtained, the rise over thermal (RoT) is used instead. For details aboutthe actual uplink load, see section "Load Measurement" in Load Control Feature ParameterDescription.

l DTCH carried over the FACH: The state of the DTCH carried over the FACH determineswhether the FACH of a cell is congested.

l Number of users on the FACH: This is determined based on the number of users in theCELL_FACH state.Table 3-1 lists the decision conditions for each measurement object.

Table 3-1 Decision conditions for each measurement objectMeasurementObject

Congestion State

Downlink powerload of a cell

Second-level congestion statel When the downlink non-HSPA power load is greater than or

equal to the second-level congestion triggering threshold for thedownlink non-HSPA power load, the downlink power load ofthe cell enters the second-level congestion state.

l When the downlink non-HSPA power load is less than or equalto the second-level congestion release threshold for the downlinknon-HSPA power load, the downlink power load of the cell exitsthe second-level congestion state.NOTEl The second-level congestion triggering threshold for the downlink

non-HSPA power load is greater than the second-level congestionrelease threshold for the downlink non-HSPA power load.

l By default, a cell entering the second-level congestion state isconsidered in the severe congestion state and a cell exiting thesecond-level congestion state is considered in the light congestionstate.



4

MeasurementObject

Congestion State

First-level congestion statel When the downlink non-HSPA power load is greater than or

equal to the first-level congestion triggering threshold for thedownlink non-HSPA power load, the downlink power load ofthe cell enters the first-level congestion state.

l When the downlink non-HSPA power load is less than or equalto the first-level congestion release threshold for the downlinknon-HSPA power load, the downlink power load of the cell exitsthe first-level congestion state.NOTEl The first-level congestion triggering threshold for the downlink non-

HSPA power load is greater than the first-level congestion releasethreshold for the downlink non-HSPA power load.

l By default, a cell entering the first-level congestion state isconsidered in the light congestion state and a cell exiting the first-level congestion state is considered in the normal state.

Normal stateWhen the downlink non-HSPA power load is greater than or equalto the normal state threshold for the downlink non-HSPA powerload, the downlink power load of the cell enters the normal state.NOTE

The default value of the normal state threshold for the downlink non-HSPApower load is DL_NORMAL_STATE.

Uplink powerload of a cell

Congestion statel When the actual uplink load is greater than or equal to the

congestion triggering threshold for the actual uplink load and thenumber of users on the DCH is greater than or equal to thecongestion triggering threshold for the number of users on theDCH, the uplink power load of the cell enters the congestionstate.

l When the actual uplink load is less than or equal to the congestionrelease threshold for the actual uplink load and the number ofusers on the DCH is less than or equal to the congestion releasethreshold for the number of users on the DCH, the uplink powerload of the cell exits the congestion state.

NOTEl The congestion triggering threshold for the actual uplink load is greater

than the congestion release threshold for the actual uplink load.l The congestion triggering threshold for the number of users on the DCH

is greater than the congestion release threshold for the number of userson the DCH.

l The congestion triggering and release thresholds for the actual uplinkload are 7 dB and 4 dB, respectively.

l The congestion triggering and release thresholds for the number of userson the DCH are 35 and 25, respectively.



5

MeasurementObject

Congestion State

Normal stateWhen the actual uplink load is greater than or equal to the normalstate threshold for the actual uplink load and the number of users onthe DCH is greater than or equal to the normal state threshold forthe number of users on the DCH, the uplink power load of the cellenters the normal state.NOTE

The default value of the normal state threshold for the actual uplink load is4 dB.The default value of the normal state threshold for the number of users onthe DCH is 25.

DTCH carriedover the FACH

l When the DTCH carried over the FACH is congested, the FACHof the cell enters the congestion state.

l When the DTCH carried over the FACH is not congested, theFACH of the cell exits the congestion state.

NOTEFor details about how to decide whether the DTCH carried over the FACHis congested, see Flow Control Feature Parameter Description.

Number of userson the FACH

Normal stateWhen the number of users on the FACH is greater than or equal tothe normal state threshold for the number of users on the FACH, thenumber of users on the FACH enters the normal state.NOTE

The default value of the normal state threshold for the number of users onthe FACH is 15.

Light-load stateWhen the number of users on the FACH is greater than or equal tothe light-load state threshold for the number of users on the FACH,the number of users on the FACH enters the light-load state.NOTE

The default value of the light-load state threshold for the number of users onthe FACH is 5.

All the thresholds in the preceding table are configurable. For details about how to configurethese thresholds, see section 6.4.5 Activation

3.2.2 Automatic Congestion Relief ActionsThe RNC performs corresponding congestion relief actions after determining the load state ofa cell. Table 3-2 lists all the congestion relief actions for each congestion state. Some functionsunder CS Preference and FACH Congestion Control have no negative impact on the networkwhen the cell is not congested. Therefore, these functions are enabled by default when theADAP_CELL_CONGEST_SWITCH under the AdapAlgoSwitch parameter is set to ON andcorresponding conditions are met. Once enabled, these functions will not be disabled.



6

NOTE

l CS Preference includes the following functions: CS RAB setup optimization, CS services preemptingPS BE service resources, preemption algorithm, CS RRC preemption, high SPU CPU load preemption.

l FACH Congestion Control includes the following functions: RLC transmission suspension after UL4A, RLC transmission suspension after DL F2D, P2D in FACH congestion, TVM-based P2D, and F2Pstate transition through physical channel reconfiguration.

Table 3-2 Automatic congestion relief actionsFunction Congestion Relief ActionN300/T300parameteroptimization

l When the downlink power load of a cell enters the second-levelcongestion state or the uplink power load of a cell enters thecongestion state, the cell-level parameter N300 is set to 1.

l When the downlink power load of a cell exits the second-levelcongestion state and the uplink power load of a cell exits thecongestion state, the cell-level parameter N300 is reset to its originalvalue.

RRC connectionrelease wait timeparameteroptimization

l When the downlink power load of a cell enters the second-levelcongestion state or the uplink power load of a cell enters thecongestion state, the cell-level parameter LowRrcConnRej-WaitTmr is set to 15.

l When the downlink power load of a cell exits the second-levelcongestion state and the uplink power load of a cell exits thecongestion state, the cell-level parameter LowRrcConnRej-WaitTmr is reset to its original value.

Inter-RATredirection

l When the downlink power load of a cell enters the second-levelcongestion state or the uplink power load of a cell enters thecongestion state, the cell-level parameter ConnectFailRrcRedirS-witch is set to Allowed_To_Inter_RAT.

l When the downlink power load of a cell exits the second-levelcongestion state and the uplink power load of a cell exits thecongestion state, the cell-level parameter ConnectFailRrcRedirS-witch is reset to its original value.

Inter-RAT DRD l When the downlink power load of a cell enters the second-levelcongestion state or the uplink power load of a cell enters thecongestion state, the cell-level parameter InterRATDRDSwitch is setto ON.

l When the downlink power load of a cell exits the second-levelcongestion state and the uplink power load of a cell exits thecongestion state, the cell-level parameterInterRATDRDSwitch isreset to its original value.



7

Function Congestion Relief ActionCell HSUPA usernumberparameteroptimization

l When the uplink power load of a cell enters the congestion state, theMaxUpaUserNumDynAdjFactor parameter is set to 50. This reducesthe maximum number of HSUPA users in a cell.

l When the uplink power load of a cell exits the congestion state, theMaxUpaUserNumDynAdjFactor parameter is reset to its originalvalue. This increases the maximum number of HSUPA users in a cell..

Uplink initialaccess rate

l When the uplink power load of a cell enters the congestion state, thecell-level parameter UlBeTraffInitBitrate is set to D32. Thisdecreases the uplink initial access rate of R99 users that are processingPS BE services.

l When the uplink power load of a cell exits the congestion state, thecell-level parameter UlBeTraffInitBitrate is reset to its originalvalue. This increases the uplink initial access rate of R99 users thatare processing PS BE services.

Downlink initialaccess rate

l When the downlink power load of a cell enters the first-levelcongestion state, the cell-level parameterDlBeTraffInitBitrate is setto D32. This decreases the downlink initial access rate of R99 usersthat are processing PS BE services.

l When the downlink power load of a cell exits the first-levelcongestion state, the cell-level parameter DlBeTraffInitBitrate isreset to its original value. This increases the downlink initial accessrate of R99 users that are processing PS BE services.

CS RAB setupoptimization

When the uplink or downlink power load of a cell enters the normal state,the cell-level parameter CSRABCacOptSwitch is automatically set toON to enable the CS RAB setup optimization function.

CS servicespreempting PSBE serviceresources

When the uplink or downlink power load of a cell enters the normal state,the PREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH under thecell-level parameter PreemptEnhSwitch is automatically set to ON. Thisenables CS services to preempt resources occupied by PS services toaccess the cell.

Preemptionalgorithm

When the uplink or downlink power load of a cell enters the normal state,the cell-level parameter PreemptAlgoSwitch is automatically set toON to activate the preemption algorithm.

CS RRCpreemption

When the uplink or downlink power load of a cell enters the normal state,the PREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH under thecell-level parameter PreemptEnhSwitch is automatically set to ON.This enables RRC connection requests for CS services to preemptresources occupied by PS services.

High SPU CPUload preemption

When the uplink or downlink power load of a cell enters the normal state,the PREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWITCH underthe cell-level parameter PreemptEnhSwitch is automatically set to ON.This enables the preemption when the SPU CPU load is high.



8

Function Congestion Relief ActionP2D CSpreemption

When the uplink or downlink power load of a cell enters the normal state,the cell-level parameter CsP2DPreemptSwitch is automatically set toON. This enables CS services of a user to preempt resources occupiedby PS BE services during the transition from CELL_PCH or URA_PCHto CELL_DCH (P2D).

Increasingnumber of UEs onFACH to 60

When the number of users on the FACH in a cell enters the normal state,the FACH_60_USER_SWITCH under the cell-level parameterNBMFACHCTRLALGOSWITCH is automatically set to ON. Thisenables a maximum of 60 UEs to be carried on the FACH.

RLC transmissionsuspension afterUL 4A

l When the DTCH carried over the FACH in a cell enters the congestionstate, the PERFENH_TX_INTERRUPT_AFT_TRIG_SWITCHunder the parameter CORRMFACHCTRLALGOSWITCH isautomatically set to ON. This enables the RNC to suspend the RLCdata transmission for a certain period of time after reporting 4Ameasurement reports.

l When the DTCH carried over the FACH in a cell exits the congestionstate, the PERFENH_TX_INTERRUPT_AFT_TRIG_SWITCHunder the parameter CORRMFACHCTRLALGOSWITCH isautomatically reset to its original value.

RLC transmissionsuspension afterDL F2D

l When the DTCH carried over the FACH in a cell enters the congestionstate, the RNC_F2D_RLC_SUSPEND_SWITCH under theRRFACHCTRLALGOSWITCH parameter is automatically set toON. This enables the RNC to suspend the RLC data transmissionduring F2D state transitions.

l When the DTCH carried over the FACH in a cell exits the congestionstate, the RNC_F2D_RLC_SUSPEND_SWITCH under theRRFACHCTRLALGOSWITCH parameter is automatically reset toits original value.

P2D in FACHcongestion

When the number of users on the FACH enters the normal state, theP2D_SWITCH under the RRFACHCTRLALGOSWITCH parameteris automatically set to ON. This enables the RNC to switch the user fromthe CELL_PCH or URA_PCH state to the CELL_DCH state when theFACH is congested.

TVM-based P2D When the number of users on the FACH enters the light-load state, theRNC_TVM_BASED_P2D_SWITCH under theRRFACHCTRLALGOSWITCH parameter is automatically set to ON.This enables the RNC to trigger a P2D state transition for a user whenthe RNC receives from the user a CELL UPDATE message with theTraffic volume indicator IE set to TRUE or receives from the CN adynamic traffic volume measurement value that meets a specifiedthreshold.



9

Function Congestion Relief ActionF2P statetransition throughphysical channelreconfiguration

When the number of users on the FACH enters the light-load state, theCMP_F2P_PROCESS_OPTIMIZATION_SWITCH under theCORRMFACHCTRLALGOSWITCH parameter is automatically set toON. This enables the F2P state transition to be performed through thephysical channel reconfiguration procedure.

NOTE

When this feature is disabled or a function in the preceding table is deactivated, the parameters involvedin this feature or function are reset to their original values.



10

4 Related FeaturesPrerequisite Features

Inter-RAT redirection, inter-RAT DRD, and preemption-related functions are automaticallyenabled when the cell load meets certain requirements (as listed in Table 3-2) . These functionsdepend on the following features:l WRFD-02040003 Inter System Redirectl WRFD-02040002 Inter System Direct Retryl WRFD-010505 Queuing and Pre-Emption

Mutually Exclusive FeaturesNone

Impacted FeaturesNone

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 4 Related Features


11

5 Network ImpactSystem Capacity

Network configuration optimization cannot be performed in advance for unplanned events wherenetwork congestion often happens. With Automatic Congestion Handler, congestion reliefactions can be automatically performed when cells are congested. This improves the systemcapacity.This feature involves multiple algorithms and functions. The impact of each algorithm orfunction on the system capacity is as follows:l N300/T300 parameter optimization: This function reduces the number of RRC

CONNECTION REQUEST retransmissions in congestion scenarios and therefore reducesadditional resource consumption in the uplink. When there are sufficient services, thisaction also increases the uplink traffic volume.

l RRC connection release wait time parameter optimization: This function prolongs the timea user of low-priority has to wait before sending a second RRC CONNECTION REQUESTmessage and reduces additional resource consumption in the uplink in congestion scenarios.When there are sufficient services, this action also increases the uplink traffic volume.

l Cell HSUPA user number parameter optimization: This function reduces the maximumnumber of online HSUPA users in a cell in congestion scenarios. The uplink throughput islow in congestion scenarios and the power efficiency of R99 services is higher than that ofHSUPA services in low uplink throughput scenarios. Eventually, this action reduces theresource consumption in the uplink. When there are sufficient services, this action alsoincreases the total uplink traffic volume.

l Uplink or downlink initial access rate: This function decreases the initial access rate of R99users that are processing PS BE services and reduces the power consumption per user incongestion scenarios. When there are sufficient services, this action also increases thenumber of users on the DCH and improves the system capacity. However, this reduces theaverage throughput of a single user that is processing PS BE services.

l Functions under CS Preference, such as CS RAB setup optimization and CS servicespreempting PS BE service resources, ensure that CS services preferentially access thenetwork. This improves the CS Erlangs but reduces the PS traffic volume in congestionscenarios.

l Functions under FACH Congestion Control, such as RLC transmission suspension afterUL 4A, improve the utilization of FACH resources and therefore the system capacity.

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 5 Network Impact


12

The overall impact on system capacity is as follows:In cell congestion scenarios, congestion relief actions help reduce cell load and improve theefficiency of resource utilization. This feature also helps improve the cell capacity when thereare sufficient services.

Network PerformanceThe impact of each algorithm or function on the network performance is as follows:l N300/T300 parameter optimization: This function reduces the number of RRC

CONNECTION REQUEST retransmissions in congestion scenarios. This prolongs theresponse delay for users.

l RRC connection release wait time parameter optimization: This function prolongs the timea user of low-priority has to wait before sending a second RRC CONNECTION REQUESTmessage in congestion scenarios. This prolongs the response delay of these users.

l Cell HSUPA user number parameter optimization: This function reduces the maximumnumber of online HSUPA users in a cell in congestion scenarios. As a result, some HSUPAusers can be carried only on the DCH, affecting user experience.

l Inter-RAT redirection: This function enables users to be redirected to the GSM networkafter failing to access the UMTS network. This reduces the access delay for these users,improving user experience.

l Inter-RAT DRD: This function enables CS users to access the GSM network after failingto access the UMTS network in congestion scenarios. This reduces the access delay forthese users and slightly improves the setup success rate of CS services.

l Functions under CS Preference, such as CS RAB setup optimization and CS servicespreempting PS BE service resources, ensure that CS services preferentially access thenetwork. This improves the CS RAB setup success rate in congestion scenarios. However,the PS call drop rate slightly increases if the occurrences of CS or PS services preemptingresources occupied by PS services increase.

The overall impact on the network performance is as follows:If CS admission fails before this feature is enabled, the CS access success rate significantlyincreases after this feature is enabled. However, the PS call drop rate also increases when PS orCS preemption occurs.

NOTE

l After this feature is enabled, some of the preceding functions take effect simultaneously and thesefunctions mutually affect each other. Therefore, the impact of this feature on system capacity andnetwork performance cannot be quantified.

l After this feature is enabled, the RNC dynamically adjust parameters and therefore the CPU usage ofthe SPU subsystem slightly increases. The increase in the CPU usage is in direct proportion to thenumber of cells enabled with this feature on the SPU subsystem. When all the cells on the SPUsubsystem are enabled with this feature, the CPU usage of the SPU subsystem increases by less than3%.

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 5 Network Impact


13

6 Engineering Guidelines6.1 When to Use Automatic Congestion Handler

The Automatic Congestion Handler feature is recommended in the following scenarios:l The network configuration involved in this feature is not optimized.l Unplanned events happen. It is recommended that this feature always be enabled in this

scenario because network congestion often occurs and the congestion state is unpredictablein this scenario.

l A cell is congested. This feature helps relieve cell congestion and improves system capacity.For details about how to determine whether the network configuration needs to be optimizedand whether a cell is congested, see section 6.2 Required Information

6.2 Required InformationCollect the values of the VS.CellDCHUEs, VS.MeanULActualPowerLoad, VS.MeanRTWP,VS.MeanTCP.NonHS, VS.CellFACHUEs.MAX, and VS.CellFACHUEs counters during busyhours to evaluate the congestion states of different resources in a cell. When the counters meetthe following conditions, the corresponding resource in the cell is congested. It is recommendedthat this feature be enabled for a cell if any resource is congested.l The uplink power load meets the following conditions:

The value of the VS.CellDCHUEs counter is greater than 20. The value of the VS.MeanULActualPowerLoad counter is greater than 65%. That is,

the actual uplink load is greater than 5 dB. If the actual uplink load cannot be obtained,this feature uses the RTWP instead. In this case, it is required that the ROTcorresponding to the value of the VS.MeanRTWP counter be greater than 5 dB.

l For the downlink power load, the value of the VS.MeanTCP.NonHS counter meets thefollowing formula: 10[(VS.MeanTCP.NonHS-MaxTxPower/10)/10] > 60%.

l For the number of users on the FACH, the value of the VS.CellFACHUEs counter is greaterthan 25 or the value of the VS.CellFACHUEs.MAX counter is greater than or equal to 30.

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 6 Engineering Guidelines


14

Check the settings of related parameters and determine whether this feature is necessary basedon the congestion relief actions described in section 3.2.2 "Automatic Congestion ReliefActions."

Function Setting Notes MML CommandN300/T300parameteroptimization

If N300 is set to 1 before this featureis enabled, this function cannot takeeffect and it is recommended thatthis function be disabled.NOTE

When this feature is enabled, thisfunction is enabled by default.

l Preferentially run the LSTUCELLIDLEMODETIMERcommand to query the value ofN300 specified for a cell.

l If N300 is not specified for the cell,run the LSTUIDLEMODETIMER commandto query its value.

RRCconnectionrelease waittimeparameteroptimization

If LowRrcConnRejWaitTmr is setto 15 before this feature is enabled,this function cannot take effect andit is recommended that this functionbe disabled.NOTE


l Preferentially run the LSTUCELLSTATETIMER commandto query the value ofLowRrcConnRejWaitTmrspecified for a cell.

l If LowRrcConnRejWaitTmr is notspecified for the cell, run the LSTUSTATETIMER command toquery its value.

Inter-RATredirection

If ConnectFailRrcRedirSwitch isset to Allowed_To_Inter_RATbefore this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLDRD command to querythe value of ConnectFailRrcRe-dirSwitch specified for a cell.

l If ConnectFailRrcRedirSwitch isnot specified for the cell, run theLST UDRD command to query itsvalue.

Inter-RATDRD

If InterRATDRDSwitch orDR_INTER_RAT_DRD_SWITCH under DrSwitch is set to ONbefore this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLINTERRATDRcommand to query the value ofInterRATDRDSwitch specified fora cell.

l If InterRATDRDSwitch is notspecified for the cell, run the LSTUCORRMALGOSWITCHcommand to query the setting ofDR_INTER_RAT_DRD_SWITCH.



15

Function Setting Notes MML CommandCell HSUPAuser numberparameteroptimization

If MaxUpaUserNumDynAdjFac-tor is set to 50 before this feature isenabled, this function cannot takeeffect and it is recommended thatthis function be disabled.NOTE


Run the LST UCELLCAC commandto query the value ofMaxUpaUserNumDynAdjFactorspecified for a cell.

Uplinkinitial accessrate

If the value of UlBeTraffInitBi-trate is less than D32 before thisfeature is enabled, this functioncannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFRC command to querythe value of UlBeTraffInitBitratespecified for a cell.

l If UlBeTraffInitBitrate is notspecified for the cell, run the LSTUFRC command to query its value.

Downlinkinitial accessrate

If the value of DlBeTraffInitBi-trate is less than D32 before thisfeature is enabled, this functioncannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFRC command to querythe value of DlBeTraffInitBitratespecified for a cell.

l If DlBeTraffInitBitrate is notspecified for the cell, run the LSTUFRC command to query its value.

CS RABsetupoptimization

If CSRABCacOptSwitch is set toON before this feature is enabled,this function cannot take effect andit is recommended that this functionbe disabled.NOTE


Run the LSTUCELLALGOSWITCH command toquery the value of CSRABCacOptS-witch specified for a cell.

CS servicespreemptingPS BEserviceresources

IfPREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH is set to ONbefore this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLQUEUEPREEMPTcommand to query the value ofPREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH specifiedfor a cell.

l IfPREEMPT_ENH_CSRAB_PREEMPT_PS_SWITCH is notspecified for the cell, run the LSTUQUEUEPREEMPT command toquery its value.



16

Function Setting Notes MML CommandPreemptionalgorithm

If PreemptAlgoSwitch is set toON before this feature is enabled,this function cannot take effect andit is recommended that this functionbe disabled.NOTE


l Preferentially run the LSTUCELLQUEUEPREEMPTcommand to query the value ofPreemptAlgoSwitch specified for acell.

l If PreemptAlgoSwitch is notspecified for the cell, run the LSTUQUEUEPREEMPT command toquery its value.

CS RRCpreemption

IfPREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH is set to ONbefore this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLQUEUEPREEMPTcommand to query the value ofPREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH specifiedfor a cell.

l IfPREEMPT_ENH_CSRRC_PREEMPT_PS_SWITCH is notspecified for the cell, run the LSTUQUEUEPREEMPT command toquery its value.

High SPUCPU loadpreemption

IfPREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWITCH is set toON before this feature is enabled,this function cannot take effect andit is recommended that this functionbe disabled.NOTE


l Preferentially run the LSTUCELLQUEUEPREEMPTcommand to query the value ofPREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWITCH specifiedfor a cell.

l IfPREEMPT_ENH_CPU_HIGHLOAD_CTRL_SWITCH is notspecified for the cell, run the LSTUQUEUEPREEMPT command toquery its value.

P2D CSpreemption

If CsP2DPreemptSwitch is set toON before this feature is enabled,this function cannot take effect andit is recommended that this functionbe disabled.NOTE


l Preferentially run the LSTUCELLQUEUEPREEMPTcommand to query the value ofCsP2DPreemptSwitch specified fora cell.

l If CsP2DPreemptSwitch is notspecified for the cell, run the LSTUQUEUEPREEMPT command toquery its value.



17

Function Setting Notes MML CommandIncreasingnumber ofUEs onFACH to 60

If FACH_60_USER_SWITCH isset to ON before this feature isenabled, this function cannot takeeffect and it is recommended thatthis function be disabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofFACH_60_USER_SWITCHspecified for a cell.

l If FACH_60_USER_SWITCH isnot specified for the cell, run theLST UCACALGOSWITCHcommand to query its value.

RLCtransmissionsuspensionafter UL 4A

IfPERFENH_TX_INTERRUPT_AFT_TRIG_SWITCH is set to 1before this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofPERFENH_TX_INTERRUPT_AFT_TRIG_SWITCH specifiedfor a cell.

l IfPERFENH_TX_INTERRUPT_AFT_TRIG_SWITCH is notspecified for the cell, run the LSTUCORRMPARA command toquery its value.

RLCtransmissionsuspensionafter DLF2D

IfRNC_F2D_RLC_SUSPEND_SWITCH is set to 1 before this featureis enabled, this function cannot takeeffect and it is recommended thatthis function be disabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofRNC_F2D_RLC_SUSPEND_SWITCH specified for a cell.

l IfRNC_F2D_RLC_SUSPEND_SWITCH is not specified for the cell,run the LSTURRCTRLSWITCH command toquery its value.

D2I inFACHcongestion

IfPERFENH_FACH_CONG_D2IDLE_SWITCH is set to 1 beforethis feature is enabled, this functioncannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofPERFENH_FACH_CONG_D2IDLE_SWITCH specified for a cell.

l IfPERFENH_FACH_CONG_D2IDLE_SWITCH is not specified forthe cell, run the LSTUCORRMPARA command toquery its value.



18

Function Setting Notes MML CommandP2D inFACHcongestion

If P2D_SWITCH is set to 1 beforethis feature is enabled, this functioncannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofP2D_SWITCH specified for a cell.

l If P2D_SWITCH is not specifiedfor the cell, run the LSTURRCTRLSWITCH command toquery its value.

TVM-basedP2D

IfRNC_TVM_BASED_P2D_SWITCH is set to 1 before this feature isenabled, this function cannot takeeffect and it is recommended thatthis function be disabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofRNC_TVM_BASED_P2D_SWITCH specified for a cell.

l IfRNC_TVM_BASED_P2D_SWITCH is not specified for the cell, runthe LST URRCTRLSWITCHcommand to query its value.

F2P statetransitionthroughphysicalchannelreconfiguration

IfCMP_F2P_PROCESS_OPTIMIZATION_SWITCH is set to 1before this feature is enabled, thisfunction cannot take effect and it isrecommended that this function bedisabled.NOTE


l Preferentially run the LSTUCELLFACHCONGCTRLcommand to query the value ofCMP_F2P_PROCESS_OPTIMIZATION_SWITCH specified fora cell.

l IfCMP_F2P_PROCESS_OPTIMIZATION_SWITCH is notspecified for the cell, run the LSTUCORRMALGOSWITCHcommand to query its value.

For details about how to activate or deactivate a single function, see section 6.4.5 Activation

6.3 Network PlanningNone

6.4 Deployment



19

6.4.1 RequirementsHardware

None

LicenseFeature ID Feature Name License Control Item NE Sales

UnitWRFD-160253 Automatic

Congestion HandlerAutomatic CongestionHandler (Per Erl)

RNC Per Erl

Automatic CongestionHandler (per kbps)

RNC per Mbps

Other RequirementsInter-RAT redirection, inter-RAT DRD, and preemption-related functions are automaticallyenabled when the cell load meets certain requirements (as listed in Table 3-2) . These functionsdepend on the following features:l WRFD-02040003 Inter System Redirectl WRFD-02040002 Inter System Direct Retryl WRFD-010505 Queuing and Pre-Emption

6.4.2 Data PreparationParameterName

Parameter ID Description DataSource

AdaptiveAlgorithmSwitch

AdapAlgoSwitch:ADAP_CELL_CONGEST_SWITCH

TheADAP_CELL_CONGEST_SWITCH under this parametercontrols whether this feature isenabled.

Engineering design



20

ParameterName


AtomRuleID AtomRuleID l When the second-levelcongestion triggeringthreshold for the downlinknon-HSPA power load needs tobe adjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 1.

l When the second-levelcongestion release thresholdfor the downlink non-HSPApower load needs to beadjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 4.

l When the first-level congestiontriggering threshold for thedownlink non-HSPA powerload needs to be adjusted, runthe MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 7.

l When the first-level congestionrelease threshold for thedownlink non-HSPA powerload needs to be adjusted, runthe MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 8.

l When the normal statethreshold for the downlinknon-HSPA power load needs tobe adjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 15.

l When the congestiontriggering threshold for theactual uplink load needs to beadjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 2.

Engineering design



21

ParameterName


l When the congestion releasethreshold for the actual uplinkload needs to be adjusted, runthe MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 5.

l When the normal statethreshold for the actual uplinkload needs to be adjusted, runthe MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 11.

l When the congestiontriggering threshold for thenumber of users on the DCHneeds to be adjusted, run theMOD UIOPTATOMRULEcommand to set theAtomRuleID parameter to 3.

l When the congestion releasethreshold for the number ofusers on the DCH needs to beadjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 6.

l When the normal statethreshold for the number ofusers on the DCH needs to beadjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 12.

l When the normal statethreshold for the number ofusers on the FACH needs to beadjusted, run the MODUIOPTATOMRULEcommand to set theAtomRuleID parameter to 13.

l When the light-load statethreshold for the number ofusers on the FACH needs to beadjusted, run the MOD



22

ParameterName


UIOPTATOMRULEcommand to set theAtomRuleID parameter to 14.

ThresholdRangeValueOrThresholdEnumValue

ThresholdRangeValueOrThresholdEnumValue

The thresholds must meet thefollowing conditions:l The second-level congestion

triggering threshold for thedownlink non-HSPA powerload is greater than the second-level congestion releasethreshold for the downlinknon-HSPA power load.

l The first-level congestiontriggering threshold for thedownlink non-HSPA powerload is greater than the first-level congestion releasethreshold for the downlinknon-HSPA power load.

l The congestion triggeringthreshold for the actual uplinkload is greater than thecongestion release thresholdfor the actual uplink load.

l The congestion triggeringthreshold for the number ofusers on the DCH is greaterthan the congestion releasethreshold for the number ofusers on the DCH.

Engineering design

6.4.3 PrecautionsNone

6.4.4 Hardware AdjustmentNone

6.4.5 Activation



23

6.4.5.1 Using MML CommandsStep 1 (Optional) Configure thresholds for congestion decision conditions. For details about the

congestion decision conditions, see section 3.2.1 Decision Conditions for DifferentCongestion StatesConfigure the second-level congestion thresholds for the downlink non-HSPA power load.l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the

AtomRuleID parameter to 1 , MeasureObjType to CELL, MeasureObject toDL_NONH_PWR_STATUS, and set the ThresholdEnumValue parameter to adjust thesecond-level congestion triggering threshold for the downlink non-HSPA power load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 4 , MeasureObjType to CELL, MeasureObject toDL_NONH_PWR_STATUS, and set the ThresholdEnumValue parameter to adjust thesecond-level congestion release threshold for the downlink non-HSPA power load.Configure the first-level congestion thresholds for the downlink non-HSPA power load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 7 , MeasureObjType to CELL, MeasureObject toDL_NONH_PWR_STATUS, and set the ThresholdEnumValue parameter to adjust thefirst-level congestion triggering threshold for the downlink non-HSPA power load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 8 , MeasureObjType to CELL, MeasureObject toDL_NONH_PWR_STATUS, and set the ThresholdEnumValue parameter to adjust thefirst-level congestion release threshold for the downlink non-HSPA power load.

Configure the normal state threshold for the downlink non-HSPA power load.l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the

AtomRuleID parameter to 15 , MeasureObjType to CELL, MeasureObject toDL_NONH_PWR_STATUS, and set the ThresholdEnumValue parameter to adjust thenormal state threshold for the downlink non-HSPA power load.Configure the congestion thresholds for the uplink load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 2 , MeasureObjType to CELL, MeasureObject toUL_ACTUAL_LOAD, and set the ThresholdRangeValue parameter to adjust thecongestion triggering threshold for the actual uplink load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 5 , MeasureObjType to CELL, MeasureObject toUL_ACTUAL_LOAD, and set the ThresholdRangeValue parameter to adjust thecongestion release threshold for the actual uplink load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 3 , MeasureObjType to CELL, MeasureObject toDCH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the congestiontriggering threshold for the number of users on the DCH.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 6 , MeasureObjType to CELL, MeasureObject toDCH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the congestionrelease threshold for the number of users on the DCH.

Configure the normal state threshold for the uplink non-HSPA power load.



24

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 11,MeasureObjType to CELL, MeasureObject toUL_ACTUAL_LOAD, and set the ThresholdRangeValue parameter to adjust the normalstate threshold for the actual uplink load.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 12,MeasureObjType to CELL, MeasureObject toDCH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the normalstate threshold for the number of users on the DCH.

Configure the state thresholds for the number of users on the FACH.l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set the

AtomRuleID parameter to 13 , MeasureObjType to CELL, MeasureObject toFACH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the normalstate threshold for the number of users on the FACH.

l Run the RNC MML command MOD UIOPTATOMRULE. In this substep, set theAtomRuleID parameter to 14 , MeasureObjType to CELL, MeasureObject toFACH_USER_NUM, and set the ThresholdRangeValue parameter to adjust the light-loadstate threshold for the number of users on the FACH.

Step 2 (Optional) Activate or deactivate the functions involved in this feature based on the descriptionsin sections 3.2.1 Decision Conditions for Different Congestion States and 3.2.2 AutomaticCongestion Relief Actions.l Run the RNC MML command LST UIOPTRULE to query the RuleID of a specific

function.The following table lists the intelligent optimization function ID of each function.

Function Intelligent Optimization FunctionID

N300/T300 parameter optimization 1RRC connection release wait time parameteroptimization

2

Cell HSUPA user number parameteroptimization

3

Uplink initial access rate 5Downlink initial access rate 21Inter-RAT redirection 6Inter-RAT DRD 7CS RAB setup optimization 8Preemption algorithm 9CS RRC preemption 10CS services preempting PS BE service resources 11



25

Function Intelligent Optimization FunctionID

High SPU CPU load preemption 12P2D CS preemption 13Increasing number of UEs on FACH to 60 14P2D in FACH congestion 16RLC transmission suspension after DL F2D 17RLC transmission suspension after UL 4A 18TVM-based P2D 19F2P state transition through physical channelreconfiguration

20

Rules of a function can be queried based on the name or ID of the function. For example, theoutput of the following command shows that the RuleID of the N300/T300 parameteroptimization function is 501, 502, 503, and 504:LST UIOPTRULE: LstType=BY_ID, IOptiFunctionID=1Run the RNC MML command ACT UIOPTRULE or DEA UIOPTRULE to activate ordeactivate rules of a function. A function is deactivated when all the rules of the function aredeactivated. Pay attention to the following when activating or deactivating rules of a function:l For functions except the uplink initial access rate and downlink initial access rate, all the

rules of a function must be activated or deactivated simultaneously. You cannot activate ordeactivate a single rule of a function. For example, you need to activate rules 501, 502, 503,and 504 simultaneously to activate the N300/T300 parameter optimization function and youneed to deactivate rules 501, 502, 503, and 504 simultaneously to deactivate the N300/T300parameter optimization function.

l For the uplink initial access rate and downlink initial access rate functions, the rules areactivated as follows: For the uplink initial access rate function, you can activate rule 516, 520, or 522 to

automatically set the UlBeTraffInitBitrate parameter to D32, D16, or D8, respectively,when a cell is congested.

NOTE

Only one of rules 516, 520, and 522 can be activated. Otherwise, the uplink initial access rate functioncannot take effect. By default, rule 516 is activated and rules 520 and 522 are deactivated.

l For the downlink initial access rate function, you can activate rule 515, 519, or 521 toautomatically set the DlBeTraffInitBitrate parameter to D32, D64, or D16, respectively,when a cell is congested.NOTE

Only one of rules 515, 519, and 521 can be activated. Otherwise, the downlink initial access rate functioncannot take effect. By default, rule 515 is activated and rules 519 and 521 are deactivated.



26

NOTE

All the functions except CS services preempting PS BE service resources listed in the preceding table areactivated by default. You need to perform this step only when a function needs to be deactivated after thisfeature is enabled.

Step 3 Run the RNC MML command ADD UCELLALGOSWITCH or MODUCELLALGOSWITCH and select the ADAP_CELL_CONGEST_SWITCH check boxunder the AdapAlgoSwitch parameter.----End

6.4.5.2 MML Command Examples// (Optional) Configuring the second-level congestion thresholds for the downlink non-HSPA power loadMOD UIOPTATOMRULE: AtomRuleID=1, MeasureObjType=CELL, MeasureObject=DL_NONH_PWR_STATUS, ThresholdThresholdEnumValue=DL_HEAVY_STATEThreshold=DL_HEAVY_STATE; MOD UIOPTATOMRULE: AtomRuleID=4, MeasureObjType=CELL, MeasureObject=DL_NONH_PWR_STATUS, ThresholdThresholdEnumValue=DL_LOADED_STATEThreshold=DL_LOADED_STATE

// (Optional) Configuring the normal state threshold for the downlink non-HSPA power loadMOD UIOPTATOMRULE: AtomRuleID=15, MeasureObjType=CELL, MeasureObject=DL_NONH_PWR_STATUS, ThresholdEnumValue=DL_NORMAL_STATE;

// (Optional) Configuring the first-level congestion thresholds for the downlink non-HSPA power load MOD UIOPTATOMRULE: AtomRuleID=7, MeasureObjType=CELL, MeasureObject=DL_NONH_PWR_STATUS, ThresholdThresholdEnumValue=DL_LOADED_STATEThreshold=DL_LOADED_STATE

MOD UIOPTATOMRULE: AtomRuleID=8, MeasureObjType=CELL, MeasureObject=DL_NONH_PWR_STATUS, ThresholdThresholdEnumValue=DL_NORMAL_STATEThreshold=DL_NORMAL_STATE

// (Optional) Configuring the congestion thresholds for the uplink loadMOD UIOPTATOMRULE: AtomRuleID=2, MeasureObjType=CELL, MeasureObject=UL_ACTUAL_LOAD, ThresholdThresholdRangeValue=70Threshold=7;MOD UIOPTATOMRULE: AtomRuleID=5, MeasureObjType=CELL, MeasureObject=UL_ACTUAL_LOAD, ThresholdThresholdRangeValue=40Threshold=4; MOD UIOPTATOMRULE: AtomRuleID=6, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM, ThresholdThresholdRangeValue=25Threshold=25; MOD UIOPTATOMRULE: AtomRuleID=3, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM, ThresholdThresholdRangeValue=35Threshold=35;

// (Optional) Configuring the normal state threshold for the uplink non-HSPA power load MOD UIOPTATOMRULE: AtomRuleID=11, MeasureObjType=CELL, MeasureObject=UL_ACTUAL_LOAD, ThresholdRangeValue=40; MOD UIOPTATOMRULE: AtomRuleID=12, MeasureObjType=CELL, MeasureObject=DCH_USER_NUM, ThresholdRangeValue=25;

// (Optional) Configuring the state thresholds for the number of users on the FACHMOD UIOPTATOMRULE: AtomRuleID=13, MeasureObjType=CELL, MeasureObject=FACH_USER_NUM, ThresholdRangeValue=15;MOD UIOPTATOMRULE: AtomRuleID=14, MeasureObjType=CELL, MeasureObject=FACH_USER_NUM, ThresholdRangeValue=5;

//Turning on the Adaptive Algorithm Switch MOD UCELLALGOSWITCH: CellId=xxx, AdapAlgoSwitch=ADAP_CELL_CONGEST_SWITCH-1;



27

6.4.5.3 Using the CME(Applies to features not supported by batch modification)NOTE

When configuring the Automatic Congestion Handler feature on the CME, perform a single configurationfirst, and then perform a batch modification if required. Configure the parameters of a single object beforea batch modification. Perform a batch modification before logging out of the parameter setting interface.

Step 1 Configure a single object on the CME.Set parameters on the CME according to the operation sequence in Table 6-1. For instructionson how to perform the CME single configuration, see CME Single Configuration OperationGuide.

Step 2 (Optional) Modify objects in batches on the CME.To modify multiple objects (such as the RNC/NodeB/cell/carrier/external UMTS cell) inbatches, click on the CME to start the batch modification wizard. For instructions on howto perform a batch modification through the CME batch modification center, press F1 on thewizard interface to obtain online help.

Table 6-1 Configuring the parameter on the CMESN MO NE Parameter Name Parameter ID Configura

ble in CMEBatchModification Center

1 UCELLALGOSWITCH

RNC Adaptive AlgorithmSwitch

AdapAlgoSwitch

Yes

----End

6.4.6 Activation ObservationTo check whether this feature has been enabled, perform the following steps to query self-organizing network (SON) logs:

Step 1 On the U2000 client, choose SON > SON Log.Step 2 On the displayed SON Log tab page, click Query SON Log. Set Log Category to UMTS

Automatic Congestion Handler log and Event Name to Not Limited. In addition, specifyEvent Source Object and Time Period as required.

Step 3 Click Synchronize in the bottom right corner of the SON Log tab page.Step 4 Click Query. If there is a Cell-level Parameter Adjustment record in the specified time period,

this feature has taken effect.----EndAfter this feature is activated, operating information about this feature will be recorded in SONlogs.



28

6.4.7 Deactivation

6.4.7.1 Using MML CommandsRun the RNC MML command ADD UCELLALGOSWITCH or MODUCELLALGOSWITCH and clear the ADAP_CELL_CONGEST_SWITCH check boxunder the AdapAlgoSwitch parameter.

6.4.7.2 MML Command Examples//Disabling the Automatic Congestion Handler featureCellId=xxx, AdapAlgoSwitch=ADAP_CELL_CONGEST_SWITCH-0;

6.4.7.3 Using the CME

6.4.8 ReconfigurationNone

6.5 Performance MonitoringCheck the values of counters and KPIs in the following table to monitor gains provided by thisfeature.

Counter/KPI DescriptionVS.CellDCHUEs Number of UEs in CELL_DCH State for CellVS.MeanTCP.NonHS Mean Non-HSDPA Transmitted Carrier Power

for CellVS.MeanTCP Mean Transmitted Power of Carrier for CellVS.MeanULActualPowerLoad Mean Uplink Actual Cell LoadVS.MeanRTWP Mean Power of Totally Received Bandwidth for

CellVS.FACH.DTCH.CONG.TIME Congestion Duration of DTCH Carried over

FACHs for CellVS.CellFACHUEs Number of UEs in CELL_FACH State for CellVS.CellFACHUEs.MAX Maximum Count of UE in CELL_FACHVS.HSUPA.UE.Mean.Cell Average Number of HSUPA UEs in a CellVS.HSUPA.MeanChThroughput.Total-Bytes

Number of Total Bytes Received in Uplink ofHSUPA MAC-d Flow for Cell



29

Counter/KPI DescriptionVS.SRNCIubBytesPSR99Conv.RxVS.SRNCIubBytesPSR99Str.RxVS.SRNCIubBytesPSR99Int.RxVS.SRNCIubBytesPSR99Bkg.RxVS.CRNCIubBytesPSR99.CCH.Rx

Number of UL Bytes of PS R99 Services overIub for Cell

VS.HSDPA.MeanChThroughput.Total-Bytes

Number of Total Bytes Sent in Downlink ofHSDPA MAC-d Flow for Cell

VS.SRNCIubBytesPSR99Bkg.TxVS.SRNCIubBytesPSR99Conv.TxVS.SRNCIubBytesPSR99Int.TxVS.SRNCIubBytesPSR99Str.TxVS.CRNCIubBytesPSR99.CCH.Tx

Number of DL Bytes of PS R99 Services overIub for Cell

AMR RAB Setup Success Ratio KPINumber of users performing CS services(cell)

KPI

PS call drop rate KPI

l To evaluate the changes in the congestion state of a cell, compare the values of theVS.CellDCHUEs, VS.MeanTCP.NonHS, VS.MeanULActualPowerLoad,VS.MeanRTWP, and VS.CellFACHUEs counters before and after this feature is activated.

l When the function of Cell HSUPA user number parameter optimization is enabled in a cellwhere the uplink power load is congested, if the value of the VS.HSUPA.UE.Max.Cellcounter is greater than half the value of the MaxHsupaUserNum counter before the featureactivation, the value of the VS.HSUPA.UE.Mean.Cell counter decreases after the featureactivation.

l When CS Preference functions such as CS RAB setup optimization and CS servicespreempting PS BE service resources are enabled in a congested cell, if CS admission failsbefore this feature is activated, the AMR RAB setup success rate and number of CS usersincrease after this feature is activated. However, the PS call drop rate also increases whenPS or CS preemption occurs.

l When the maximum number of FACH users is greater than or equal to 30 before this featureis activated and the function of increasing number of UEs on FACH to 60 is enabled, thevalue of the VS.CellFACHUEs counter increases after the feature activation.

Changes in the cell load are as follows:l After this feature is activated, if the value of the VS.MeanRTWP counter does not decrease,

the total uplink PS traffic volume (the sum of uplink PS R99 traffic volume over the Iuband the HSUPA traffic volume) slightly increases. If the value of the VS.MeanTCP counter



30

does not decrease, the total downlink PS traffic volume (the sum of downlink PS R99 trafficvolume over the Iub and the HSDPA traffic volume) slightly increases.

l After this feature is activated, if the total uplink PS traffic volume does not increase, thevalue of the VS.MeanRTWP counter slightly decreases. If the total downlink PS trafficvolume does not increase, the value of the VS.MeanTCP counter slightly decreases.

6.6 Parameter OptimizationThe probability that this feature takes effect can be adjusted by adjusting the thresholds forcongestion decision conditions. For details about how to adjust these thresholds, see section6.4.5 Activation.

6.7 TroubleshootingNone



31

7 ParametersTable 7-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

AdapAlgoSwitch

BSC6900 ADDUCELLALGOSWITCHMODUCELLALGOSWITCH

None None Meaning:1.ADAP_CELL_CONGEST_SWITCH(AutomaticCongestionHandlerSwitch):Whether theautomaticcongestionHandlerfunction isenabled. Whenthis switch is setto on, theautomaticcongestionHandlerfunctionidentifies theoccurrence ofand relievescongestion. 2.INTELL_STATE_TRANS_ON_LOAD_SWITCH (Load-basedIntelligent StateTransitionSwitch):

WCDMA RANAutomatic Congestion Handler Feature ParameterDescription 7 Parameters


32



Whether theload-basedintelligent statetransitionfunction isenabled. Whenthis switch is setto on, the RNCswitches thestate of heavy-load UEs basedon the settings ofparameters forheavy-load statetransitions.GUI ValueRange:ADAP_CELL_CONGEST_SWITCH,INTELL_STATE_TRANS_ON_LOAD_SWITCHUnit:NoneActual ValueRange:ADAP_CELL_CONGEST_SWITCH,INTELL_STATE_TRANS_ON_LOAD_SWITCHDefaultValue:ADAP_CELL_CONGEST_SWITCH:0,INTELL_STATE_TRANS_ON_LOAD_SWITCH:0



33



AdapAlgoSwitch


None None Meaning:1.ADAP_CELL_CONGEST_SWITCH(AutomaticCongestionHandlerSwitch):Whether theautomaticcongestionHandlerfunction isenabled. Whenthis switch is setto on, theautomaticcongestionHandlerfunctionidentifies theoccurrence ofand relievescongestion. 2.INTELL_STATE_TRANS_ON_LOAD_SWITCH (Load-basedIntelligent StateTransitionSwitch):Whether theload-basedintelligent statetransitionfunction isenabled. Whenthis switch is setto on, the RNCswitches thestate of heavy-load UEs basedon the settings ofparameters forheavy-load statetransitions.



34



GUI ValueRange:ADAP_CELL_CONGEST_SWITCH,INTELL_STATE_TRANS_ON_LOAD_SWITCHUnit:NoneActual ValueRange:ADAP_CELL_CONGEST_SWITCH,INTELL_STATE_TRANS_ON_LOAD_SWITCHDefaultValue:ADAP_CELL_CONGEST_SWITCH:0,INTELL_STATE_TRANS_ON_LOAD_SWITCH:0

N300 BSC6900 ADDUCELLIDLEMODETIMERMODUCELLIDLEMODETIMER

WRFD-010101 3GPP R9Specifications

Meaning:Maximumretransmissionsof the RRCConnectionRequestmessageGUI ValueRange:0~7Unit:sActual ValueRange:0~7Default Value:3



35



N300 BSC6910 ADDUCELLIDLEMODETIMERMODUCELLIDLEMODETIMER

WRFD-010101 3GPP R9Specifications

Meaning:Maximumretransmissionsof the RRCConnectionRequestmessageGUI ValueRange:0~7Unit:sActual ValueRange:0~7Default Value:3



36



LowRrcConnRejWaitTmr

BSC6900 ADDUCELLSTATETIMERMODUCELLSTATETIMER

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand Release

Meaning:Waiting time carried inlow-priorityRRCConnectionRejectmessages. Thisparameterspecifies theminimum time aUE has to waitbefore sending asecond RRCConnectionRequestmessage. AnRRCConnectionRequestmessage isconsidered as ahigh-priorityone when themessage isinitiated in theCS domain andcarries the causevalue"OriginatingConversationalCall","TerminatingConversationalCall", or"EmergencyCall." All otherRRCConnectionRequestmessages arelow-priorityones.GUI ValueRange:0~15Unit:sActual ValueRange:0~15



37



Default Value:4



38



LowRrcConnRejWaitTmr

BSC6910 ADDUCELLSTATETIMERMODUCELLSTATETIMER

WRFD-010510 3.4/6.8/13.6/27.2Kbps RRCConnection andRadio AccessBearerEstablishmentand Release

Meaning:Waiting time carried inlow-priorityRRCConnectionRejectmessages. Thisparameterspecifies theminimum time aUE has to waitbefore sending asecond RRCConnectionRequestmessage. AnRRCConnectionRequestmessage isconsidered as ahigh-priorityone when themessage isinitiated in theCS domain andcarries the causevalue"OriginatingConversationalCall","TerminatingConversationalCall", or"EmergencyCall." All otherRRCConnectionRequestmessages arelow-priorityones.GUI ValueRange:0~15Unit:sActual ValueRange:0~15



39



Default Value:4ConnectFailRr-cRedirSwitch

BSC6900 ADDUCELLDRDMODUCELLDRD

WRFD-020120WRFD-02040003

Service Steeringand LoadSharing in RRCConnectionSetupInter SystemRedirect

Meaning:Whether to allow RRCredirection afteran RRCconnectionadmissionfailure. Whenthis switch is setto on, RRCredirection isallowed after anRRC connectionadmissionfailure. Whenthis switch is setto off, RRCredirection isprohibited afteran RRCconnectionadmissionfailure.GUI ValueRange:OFF,Only_To_Inter_Frequency,Allowed_To_Inter_RATUnit:NoneActual ValueRange:OFF,Only_To_Inter_Frequency,Allowed_To_Inter_RATDefaultValue:Only_To_Inter_Frequency



40



ConnectFailRr-cRedirSwitch

BSC6910 ADDUCELLDRDMODUCELLDRD

WRFD-020120WRFD-02040003

Service Steeringand LoadSharing in RRCConnectionSetupInter SystemRedirect

Meaning:Whether to allow RRCredirection afteran RRCconnectionadmissionfailure. Whenthis switch is setto on, RRCredirection isallowed after anRRC connectionadmissionfailure. Whenthis switch is setto off, RRCredirection isprohibited afteran RRCconnectionadmissionfailure.GUI ValueRange:OFF,Only_To_Inter_Frequency,Allowed_To_Inter_RATUnit:NoneActual ValueRange:OFF,Only_To_Inter_Frequency,Allowed_To_Inter_RATDefaultValue:Only_To_Inter_Frequency



41



InterRATDRD-Switch

BSC6900 ADDUCELLINTERRATDRMODUCELLINTERRATDR

None None Meaning:Whether to supportinter-RATDRD.When thisswitch is set toON, inter-RATDRD issupported. If aUE cannotaccess an intra-RAT cell, theUE can initiateaccess requeststo inter-RATcells. When thisswitch is set toOFF, inter-RATDRD is notsupported andUEs cannotinitiate accessrequests to inter-RAT cells.GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF



42



InterRATDRD-Switch

BSC6910 ADDUCELLINTERRATDRMODUCELLINTERRATDR

None None Meaning:Whether to supportinter-RATDRD.When thisswitch is set toON, inter-RATDRD issupported. If aUE cannotaccess an intra-RAT cell, theUE can initiateaccess requeststo inter-RATcells. When thisswitch is set toOFF, inter-RATDRD is notsupported andUEs cannotinitiate accessrequests to inter-RAT cells.GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF



43



MaxUpaUserNumDynAdjFactor

BSC6900 ADDUCELLCACMODUCELLCAC

WRFD-01061202WRFD-010670WRFD-020101WRFD-010639WRFD-01061211WRFD-010634

HSUPAAdmissionControl128 HSUPAUsers per CellAdmissionControl96 HSUPAUsers per Cell20 HSUPAUsers per Cell60 HSUPAUsers per Cell

Meaning:Factorfor dynamicallyadjusting themaximumnumber ofHSUPA users ina cell. The RNCdetermines thenumber ofHSUPA users ina cell beforeadmitting a newuser. If thenumber ofHSUPA usersadmitted to a cellis smaller thanthe rounded-down value ofthis parameter x"MaxHsupaUserNum", the RNCproceeds withthe admissiondecisionoperation.Otherwise, theRNC rejects theadmissionrequests of newHSUPA users.The value of thisparameter isautomaticallyadjusted whenthe AutomaticCongestionHandler (ACH)algorithm isenabled, that is,theADAP_CELL_CONGEST_SWITCH under the"AdapAlgoSwitch" parameter inthe "ADDUCELLALGOS



44



WITCH"command is setto on. Thisparameter is anadvancedparameter andmanualmodification ofthe parametervalue is notrecommended.If you need tomodify the valueof thisparameter,perform themodificationwith theassistance ofHuaweitechnicalsupport.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:100



45



MaxUpaUserNumDynAdjFactor

BSC6910 ADDUCELLCACMODUCELLCAC

WRFD-01061202WRFD-010670WRFD-020101WRFD-010639WRFD-01061211WRFD-010634

HSUPAAdmissionControl128 HSUPAUsers per CellAdmissionControl96 HSUPAUsers per Cell20 HSUPAUsers per Cell60 HSUPAUsers per Cell

Meaning:Factorfor dynamicallyadjusting themaximumnumber ofHSUPA users ina cell. The RNCdetermines thenumber ofHSUPA users ina cell beforeadmitting a newuser. If thenumber ofHSUPA usersadmitted to a cellis smaller thanthe rounded-down value ofthis parameter x"MaxHsupaUserNum", the RNCproceeds withthe admissiondecisionoperation.Otherwise, theRNC rejects theadmissionrequests of newHSUPA users.The value of thisparameter isautomaticallyadjusted whenthe AutomaticCongestionHandler (ACH)algorithm isenabled, that is,theADAP_CELL_CONGEST_SWITCH under the"AdapAlgoSwitch" parameter inthe "ADDUCELLALGOS



46



WITCH"command is setto on. Thisparameter is anadvancedparameter andmanualmodification ofthe parametervalue is notrecommended.If you need tomodify the valueof thisparameter,perform themodificationwith theassistance ofHuaweitechnicalsupport.GUI ValueRange:0~100Unit:%Actual ValueRange:0~100Default Value:100



47



UlBeTraffInitBitrate

BSC6900 ADDUCELLFRCMODUCELLFRC

WRFD-021101 DynamicChannelConfigurationControl (DCCC)

Meaning:Uplinkinitial accessrate for UEsprocessing PSbackground orinteractiveservices. Whenthe DCCCfunction takeseffect, the uplinkinitial accessrate is used if themaximumuplink rate ishigher than theuplink initialaccess rate.GUI ValueRange:D8, D16,D32, D64,D128, D144,D256, D384Unit:kbit/sActual ValueRange:8, 16, 32,64, 128, 144,256, 384DefaultValue:D64



48



UlBeTraffInitBitrate


WRFD-021101 DynamicChannelConfigurationControl (DCCC)

Meaning:Uplinkinitial accessrate for UEsprocessing PSbackground orinteractiveservices. Whenthe DCCCfunction takeseffect, the uplinkinitial accessrate is used if themaximumuplink rate ishigher than theuplink initialaccess rate.GUI ValueRange:D8, D16,D32, D64,D128, D144,D256, D384Unit:kbit/sActual ValueRange:8, 16, 32,64, 128, 144,256, 384DefaultValue:D64



49



DlBeTraffInitBitrate


WRFD-021101WRFD-010507

DynamicChannelConfigurationControl (DCCC)RateNegotiation atAdmissionControl

Meaning:Downlink initial accessrate for UEsprocessing PSbackground orinteractiveservices. Whenthe DCCCfunction takeseffect, thedownlink initialaccess rate isused if themaximumdownlink rate ishigher than thedownlink initialaccess rate.GUI ValueRange:D8, D16,D32, D64,D128, D144,D256, D384Unit:kbit/sActual ValueRange:8, 16, 32,64, 128, 144,256, 384DefaultValue:D64



50



DlBeTraffInitBitrate


WRFD-021101WRFD-010507

DynamicChannelConfigurationControl (DCCC)RateNegotiation atAdmissionControl

Meaning:Downlink initial accessrate for UEsprocessing PSbackground orinteractiveservices. Whenthe DCCCfunction takeseffect, thedownlink initialaccess rate isused if themaximumdownlink rate ishigher than thedownlink initialaccess rate.GUI ValueRange:D8, D16,D32, D64,D128, D144,D256, D384Unit:kbit/sActual ValueRange:8, 16, 32,64, 128, 144,256, 384DefaultValue:D64



51



CSRABCacOptSwitch


WRFD-020101 AdmissionControl

Meaning:Whether resourceallocation isoptimizedduring CS RABsetups. Whenthis parameter isset to ON, theRNC allocatespowerresources, coderesources,channel element(CE) resourcesduring CS RABsetups based onthe loose CACalgorithm. Thissetting increasesthe CS servicesetup successrate. When thisparameter is setto OFF, the RNCdoes not allocateresources duringCS RAB setupsbased on theloose CACalgorithm.GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:ON, OFFDefaultValue:OFF

WCDMA RANAutomatic Congest

automatic congestion handler(ran16.0_draft a)

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

thepurchase scope

usage scope

trade names

respective holders

technical description