Automatic Congestion Handler Feature

member of
Feature Automatic
Congestion
Handler Feature
1
DESCRIPTION
This feature monitors load-related measurement quantities for a cell in real time. If a measurement
quantity or a set of measurement quantities meets certain requirements, the RNC determines that
the cell is congested and performs corresponding congestion relief actions, which can be
implemented by activating existing congestion relief algorithms or adjusting the settings of existing
network configuration parameters.
When the automatic congestion control switch (ADAP_CELL_CONGEST_SWITCH under the
AdapAlgoSwitch parameter) is set to on, the RNC determines the congestion state of a cell based on
measurement quantities such as;
1. downlink non-HSPA power load,
2. actual uplink load, and
3. number of users on the DCH.
After determining the congestion state, the RNC performs corresponding congestion relief actions to
improve the cell performance
DESCRIPTION (2)
The RNC determines the load state of a cell based on the following
measurement objects:
Downlink power load of a cell: This measurement object includes the downlink non-HSPA power load..
Uplink power load of a cell: This measurement object includes the actual uplink load, uplink rise over thermal
(RoT) or received total wideband power (RTWP) and number of users on the DCH.
DTCH carried over the FACH: The state of the DTCH carried over the FACH determines whether the FACH of a
cell is congested.
Number of users on the FACH: This is determined based on the number of users in the CELL_FACH state.
The RNC performs Automatic Congestion Relief Actions after determining the
load state of a cell.
Some functions under CS Preference and FACH Congestion Control have no
negative impact on the network when the cell is not congested. Therefore,
these functions are enabled by default when the
ADAP_CELL_CONGEST_SWITCH under the AdapAlgoSwitch parameter is set to
ON and corresponding conditions are met. Once enabled, these functions will
not be disabled.
Number of users on the DCH

Decision conditions for each measurement object
Congestion state
Normal state
When the number of users on the DCH is greater than or equal to the congestion triggering threshold, the number of users
on the DCH enters the congestion state.
The congestion triggering and release thresholds for the number of users on the DCH are 35 and 25, respectively.
When the number of users on the DCH is greater than or equal to the normal state threshold for the number of users on
the DCH, the number of users on the DCH enters the normal state.
The default value of the normal state threshold for the number of users on the DCH is 25.
Light-load state
When the number of users on the DCH is greater than or equal to the light-load state triggering threshold, the number of
users on the DCH enters the light-load state.
The light-load state triggering and release thresholds for the number of users on the DCH are 20 and 10, respectively
Downlink power load of a cell

Decision conditions for each measurement object
Second-level congestion state
First-level congestion state
When the downlink non-HSPA power load is greater than or equal to the second-level congestion triggering
threshold for the downlink non-HSPA power load, the downlink power load of the cell enters the second-level
congestion state.
The second-level congestion triggering threshold for the downlink non-HSPA power load is greater than the
second-level congestion release threshold for the downlink non-HSPA power load.
When the downlink non-HSPA power load is greater than or equal to the first-level congestion triggering
threshold for the downlink non-HSPA power load, the downlink power load of the cell enters the first-level
congestion state.
The first-level congestion triggering threshold for the downlink non-HSPA power load is greater than the
first-level congestion release threshold for the downlink non-HSPA power load.
Normal state
When the downlink non-HSPA power load is greater than or equal to the normal state threshold for the
downlink non-HSPA power load, the downlink power load of the cell enters the normal state.
The default value of the normal state threshold for the downlink non-HSPA power load is
DL_NORMAL_STATE.
Uplink power load of a cell
Congestion state (actual uplink load)
Congestion state (RoT)
When the uplink RoT is greater than or equal to the congestion triggering threshold for the uplink RoT and the number of users on the
DCH is greater than or equal to the congestion triggering threshold for the number of users on the DCH, the uplink power load of the
cell (RoT) enters the congestion state.
Congestion state (RTWP)
When the actual uplink load is greater than or equal to the congestion triggering threshold for the actual uplink load and the number
of users on the DCH is greater than or equal to the congestion triggering threshold for the number of users on the DCH, the uplink
power load of the cell (actual uplink load) enters the congestion state.
When the uplink RTWP is greater than or equal to the congestion triggering threshold for the uplink RTWP and the number of users on
the DCH is greater than or equal to the congestion triggering threshold for the number of users on the DCH, the uplink power load of
the cell (RTWP) enters the congestion state.
Normal state
When the actual uplink load is greater than or equal to the normal state threshold for the actual uplink load and the number of users
on the DCH is greater than or equal to the normal state threshold for the number of users on the DCH, the uplink power load of the
6
cell enters the normal state.
DTCH Congestion & FACH user
FACH Congestion Control includes the following functions: RLC transmission

suspension after UL 4A, RLC transmission suspension after DL F2D, P2D in
FACH congestion, TVM-based P2D, and F2P state transition through physical
channel reconfiguration.
Automatic Congestion Handler function ID of

each action
Current intelligent optimization function setting as per their ID

Manually adjusted parameter
When this feature is disabled or a function
in the preceding table is deactivated, the
parameters involved in this feature or
function are reset to their original values. If
values of parameters related to this feature
are manually adjusted after this feature is
enabled, the adjusted values will be
overwritten because these values will be
automatically adjusted later. Therefore, do
not manually adjust related parameters
after this feature is enabled.
Activate or deactivate a function

Run the RNC MML command ACT
UIOPTRULE or DEA UIOPTRULE to
activate or deactivate rules of a function. A
function is deactivated when all the rules of
the function are deactivated. Pay attention
to the following when activating or
deactivating rules of a function:
All the rules of a function must be activated
or deactivated simultaneously. You cannot
activate or deactivate 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 you need to
deactivate rules 501, 502, 503, and 504
simultaneously to deactivate the
N300/T300 parameter optimization
function.
SON Log
10
Sample case of RuleID 544
RLC transmission suspension after DL F2D

When the DTCH carried over the FACH in a cell enters the congestion state, the
RNC_F2D_RLC_SUSPEND_SWITCH under the RRFACHCTRLALGOSWITCH
parameter is automatically set to ON. This enables the RNC to suspend the RLC
data transmission during F2D state transitions.
11
Sample of ACH
Sample of 3G2IP_SUMEDANGKOTA for
ACH
Microsoft Excel
Worksheet
Actions of ACH
Microsoft Excel
Worksheet
12
Conclusion
After the initial implementation when all the rules enabled as default, it was
noticed that certain rules degrade the user experience.
Rules: 509/527/528/531/532/550/551/569/571/573/574/575.
Only in Special events, such as festivals, parades, or major demonstrations,

often which result in unpredictable network congestion depending on crowd
levels and community participation, it is suggested to implement Automatic
Congestion Handler since network configuration optimization cannot be
performed in advance, congestion relief can be performed automatically in
these scenarios with the help of Automatic Congestion Handler .
13
Thank You
Decision Conditions for Different Congestion States
15
Automatic Congestion Relief Actions
16
Automatic Congestion Relief Actions (2)
17

Automatic Congestion Handler Feature

Uploaded by

Copyright:

Available Formats

Automatic Congestion Handler Feature

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Automatic Congestion Handler Feature

Uploaded by

Copyright:

Available Formats

member of

Number of users on the DCH

Downlink power load of a cell

Second-level congestion state

First-level congestion state

Uplink power load of a cell

Congestion state (actual uplink load)

Congestion state (RoT)

Congestion state (RTWP)

DTCH Congestion & FACH user

FACH Congestion Control includes the following functions: RLC transmission

Automatic Congestion Handler function ID of

Current intelligent optimization function setting as per their ID

Activate or deactivate a function

Sample case of RuleID 544

RLC transmission suspension after DL F2D

Only in Special events, such as festivals, parades, or major demonstrations,

Decision Conditions for Different Congestion States

Automatic Congestion Relief Actions

Automatic Congestion Relief Actions (2)

You might also like