Overload Control Feature Guide

Overload Control Feature
Guide
WCDMA RAN
Overload Control Feature Guide

Version Date Author Reviewer Revision History
1. Modified the description of DC-HSDPA

overload control;
2. Modified and added some parameters,
and added the related description;
Wang 3. Deleted the parameter NodeBSafeThr
V7.0 2012-4-12 Xiang Zhijian
Shaojiang and the related description.
4. Modified the GBR increase restriction
after the HS GBR is decreased due to the
GBR resource consumption limiting
function.
1. Deleted the description in section 3.3.1.
For the HSUPA uplink effective load,
please refer to ZTE UMTS Admission
V8.0 2012-12-21 HeChao Xiang Zhijian Control Feature Guide.
2. Added the switch of forbidding AMR
downgrade in section 3.1.3.1
“Downgrading”.
Wang
V8.5 2013-12-21 Xiang Zhijian Added Feature ID
shaojiang
© 2013 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attributes.............................................................................................. 5
2 Overview ............................................................................................................ 5
2.1 ZWF21-04-002 Overload Control ......................................................................... 6
2.2 ZWF23-04-002 Overload Control for HSDPA Service .......................................... 7
2.3 ZWF25-04-002 Overload Control for HSUPA Service .......................................... 8
3 Technical Descriptions ..................................................................................... 8

3.1 R99 Overload Control .......................................................................................... 8
3.1.1 R99 Overload Control Flow .................................................................................. 9
3.1.2 R99 Overload Control States ............................................................................. 10
3.1.3 Load Decrease Methods for R99 Overload Control ............................................ 13
3.1.4 Load Decrease Methods for R99 Common Overload ......................................... 18
3.1.5 Load Decrease Methods for R99 Serious Overload ........................................... 19
3.1.6 Related Measurement of R99 Algorithm ............................................................ 20
3.2 HSDPA Overload Control................................................................................... 21
3.2.1 HSDPA Overload Control Flow .......................................................................... 22
3.2.2 Decision Methods for Conversion between HSDPA Overload Control States .... 23
3.2.3 Load Decrease Methods for HSDPA Overload Control ...................................... 25
3.2.4 HSDPA Load Decrease Flow ............................................................................. 29
3.2.5 Dual-Cell HSDPA Overload Control ................................................................... 31
3.2.6 Related Measurement of HSDPA Algorithm ....................................................... 32
3.3 HSUPA Overload Control................................................................................... 32
3.3.1 HSUPA Uplink Effective Load ............................................................................ 33
3.3.2 HSUPA Overload Control Flow .......................................................................... 33
3.3.3 Decision Methods for Conversion between HSUPA Overload Control States .... 34
3.3.4 Load Decrease Methods for HSUPA Overload Control ...................................... 37
3.3.5 Load Decrease Methods for HUSPA Common Overload ................................... 38
3.3.6 Load Decrease Methods for HSUPA Serious Overload ..................................... 39
3.3.7 Related Measurement of HSUPA Algorithm ....................................................... 39
3.4 MBMS Overload Control .................................................................................... 40
3.5 GBR Resource Consumption Limit .................................................................... 40
3.5.1 HSDPA GBR Resource Consumption Limit Algorithm ....................................... 41
3.5.2 Related Measurement ........................................................................................ 42
4 Parameters and Configurations ..................................................................... 42

4.1 Common Parameters ......................................................................................... 42
4.1.1 Common Parameter List .................................................................................... 42
4.1.2 Common Parameter Configurations ................................................................... 43

4.2 R99 Overload Control Parameters ..................................................................... 50

4.2.1 R99 Overload Control Parameter List ................................................................ 50
4.2.2 Configuration of R99 Overload Control Parameters ........................................... 51
4.3 HSDPA Overload Control Parameters ............................................................... 55
4.3.1 HSDPA Overload Control Parameter List ........................................................... 55
4.3.2 Configuration of HSDPA Overload Control Parameters ..................................... 55
4.4 HSUPA Overload Control Parameters ............................................................... 57
4.4.1 HSUPA Overload Control Parameter List ........................................................... 57
4.4.2 Configuration of HSUPA Overload Control Parameters ..................................... 57
4.5 MBMS Overload Control Parameters ................................................................. 59
4.6 GBR Resource Consumption Limiting Parameters............................................. 59
4.6.1 GBR Resource Consumption Limiting Parameter List ........................................ 59
4.6.2 Configuration of GBR Resource Consumption Limiting Parameters ................... 59
5 Counters and Alarms ...................................................................................... 62

5.1 Counter List ....................................................................................................... 62
5.2 Alarm List ........................................................................................................... 64
6 Glossary ........................................................................................................... 64

FIGURES
Figure 3-1 R99 overload control flowchart..........................................................................10

Figure 3-2 R99 overload control threshold .........................................................................11
Figure 3-3 Conversion between R99 overload control states .............................................12
Figure 3-4 R99 common overload control flowchart ...........................................................19
Figure 3-5 R99 serious overload control flowchart .............................................................20
Figure 3-6 Overload control flowchart for the HSDPA cells ................................................23
Figure 3-7 Conversion between HSDPA overload control states .......................................24
Figure 3-8 HSDPA overload control flowchart ....................................................................31
Figure 3-9 HSUPA overload control flowchart ....................................................................34
Figure 3-10 Classification of HSUPA overload control states .............................................35
Figure 3-11 Conversion between HSUPA overload control states .....................................36

1 Feature Attributes
System version: [RNC V3.12.10/V4.12.10, Node B V4.12.10, OMMR V12.12.41, and
OMMB V12.12.40]
Attribute: [Mandatory + Optional]
Involved NEs:
UE Node B RNC MSCS MGW SGSN GGSN HLR
√ √ √ - - - - -
Note:
*-: Not involved
*√: Involved
Dependency: [None]
Mutual exclusion: [None]
Note: [None]
2 Overview
The overload control is performed to control the load on individual cells. It takes
appropriate measures to make the system recover as soon as possible from the overload
to maintain system stability. Here overload means that the uplink/downlink load on a cell
exceeds the overload threshold set during network planning. In such a case, the system
is unstable, with its capacity close to the limit. Appropriate measures are required to
decrease the system load. Overload includes serious overload and common overload.
Serious overload means the load is close to the limit and requires prompt recovery.
By functional systems, the overload control can be classified into the following types:
 R99 overload control
 HSDPA overload control
 HSUPA overload control

 MBMS overload control
By severity of overload, the overload control can be classified into the following two
types:
 Common overload control
 Serious overload control
By direction, uplink and downlink, the overload control can be classified into the following
two types:
 Uplink overload control
 Downlink overload control
2.1 ZWF21-04-002 Overload Control
The Node B sends RTWP and TCP messages to the RNC periodically in the common
measurement report. The RNC compares the overload threshold with RTWP and TCP.
The RNC implements overload control if RTWP or TCP exceeds the threshold. Here, the
uplink overload threshold is an absolute value (dBm). It is equal to the sum of
background noise (dBm) and the relative value of uplink overload control threshold (dB).
There are two types of overload: serious overload and common overload. The RNC
system takes actions according to the overload type. Serious overload means that the
payload approaches the limit of system capacity. At the moment, the RNC system must
adjust its payload to a normal level. Therefore, the system can forcedly drop calls to
reduce the payload of a cell until the payload deceases to a value below the threshold of
common overload. In the case of common overload, the system can take the following
measures to reduce the system payload to a normal level:
 Decreasing the service rate of R99 subscribers
 Forcedly deleting the UE soft handover radio link of the overloaded cell (the link is
for downlink connection and is not for the best cell)

 Forcedly handing over subscribers to an inter-frequency cell or an inter-RAT cell

(the target cell has the same coverage as the overloaded cell or contains the
overloaded cell)
 Forcedly transferring the interactive subscribers or background subscribers to the

CELL_FACH status
 Decreasing GBR of C/S traffic through the GBR renegotiation
 Forcedly dropping calls
When overload occurs, the system selects services or UEs through the overload control
priority and then takes the above actions for these services. In this way, the system can
maintain the stability for services of high-priority subscribers. .
2.2 ZWF23-04-002 Overload Control for HSDPA Service
The overload control of the HSDPA is based on the transmit power of a cell. The
overload control function is triggered when the downlink power reaches a certain value
(which is configurable through the OMCR). During the implementation of overload control,
the HSDPA reduces the payload of a cell according to the difference of subscribers. The
HSDPA takes the following measures:
 Forcedly deleting the UE soft handover radio link from the overloaded cell (including
DCH subscribers and HS-DSCH subscribers)
 Forcedly handing over DCH and HSDPA subscribers to an inter-frequency cell or

an inter-RAT cell (the target cell has the same coverage as the overloaded cell or
contains the overloaded cell)
 Forcedly transferring the interactive subscribers or background subscribers to the

CELL_FACH status
 Forcedly dropping calls of low-priority services (DCH and HSDPA)

2.3 ZWF25-04-002 Overload Control for HSUPA Service
When overload occurs in the E-DCH cell, the system can take the following measures of
overload control:
 Forcedly handing over DCH and HSUPA subscribers to an inter-frequency cell or

an inter-RAT cell (the target cell has the same coverage as the overloaded cell or
contains the overloaded cell)
 Forcedly dropping low-priority services (DCH and HSDPA)
3 Technical Descriptions
3.1 R99 Overload Control
For R99 cells, the Node B periodically sends common measurement reports to the RNC,
and updates their uplink load RTWP and downlink load TCP. RNC compares the RTWP
and TCP with the overload control threshold. If the RTWP or TCP exceeds the threshold,
it means the occurrence of overload and the overload control process is performed.
Overload includes serious overload and common overload.
Serious overload means the load is close to the limit and requires prompt recovery. In
such a case, the following load reduction measures should be taken to decrease the
system load to a normal level as soon as possible.
 Forcing call drop until the load is recovered below the common overload threshold.
For common overload, the following load reduction measures are available to decrease
the system load to a normal level as soon as possible.

 Forcedly handing over to inter-frequency or inter-RAT neighboring cell
 Deleting the radio link of any soft handover UE from the overloaded cell
 Transferring services of I/B subscribers to the RACH/FACH channels
 Decreasing GBR (GBR renegotiation)
 Forcedly releasing the service
3.1.1 R99 Overload Control Flow
The figure below shows the overall R99 overload control flowchart. The overload control
is classified into serious overload control and common overload control depending on
different overload states. The overload control is triggered by the common measurement
reports from the Node B.
Upon the receipt of a common measurement report from the Node B, the system decides
the state of overload control with the methods described in section 3.1.2, and performs
an appropriate process depending on the decision result. If the status is common
overload, the common overload control is performed; if the status is serious overload, the
serious overload control is carried out.
The overload control in any status is performed in the directions of uplink and downlink
respectively.

Figure 3-1 R99 overload control flowchart
Common Measurement
Report
Load status
judgment
The status of The status of The status of common

normal load serious overload overload
To perform serious To perform common

Return
overload control overload control
3.1.2 R99 Overload Control States
3.1.2.1 Classification of R99 Overload Control States
There are three thresholds available to set for the overload control. They are serious
overload threshold, common overload threshold, and threshold for releasing from
overload state. Relations among the three thresholds are: serious overload threshold
(uplink: UlSeriousOverLdThr, downlink: DlSeriousOverLdThr) > common overload
threshold (uplink: UlOverLdThr, downlink: DlOverLdThr) > threshold for releasing from
overload state (uplink: UlRecoverLdThr, downlink: DlRecoverLdThr). See Figure 3-2.
The overload thresholds are set in the directions of uplink and downlink respectively.

Figure 3-2 R99 overload control threshold
The Load of Cell

The Threshold of Serious Overload
(uplink: UlSeriousOverLd,
downlink: DlSeriousOverLd)
The Threshold of Common Overload

(uplink: UlOverLd, downlink:DlOverLd)
The Threshold for Releasing from

Overload State
(uplink: UlAlrmLd, downlink: DlAlrmLd)
Depending on the load on a cell, overload control is performed in one of the three states:
normal load, common overload, and serious overload.
Note: These uplink and downlink overload thresholds and other overload control
parameters are configured based on the cell load scene (UUtranCellFDD.loadScene).
Where, UUtranCellFDD.loadScene = 0 indicates the cell is a normal load cell, and
UUtranCellFDD.loadScene = 1 indicates the cell is a high load cell.
3.1.2.2 Conversion between R99 Overload Control States
With the change of load on a cell, the three states of overload control are
inter-convertible in a relationship as shown in Figure 3-3.

Figure 3-3 Conversion between R99 overload control states
1. Load over the threshold of common overload

(uplink: UlOverLd, downlink: DlOverLd)
2. Load below the threshold for

normal common
releasing from overload state
load overload
3. Load over the threshold of serious overload

(uplink: UlSeriousOverLd, 6. Load below the threshold of serious overload
downlink: DlSeriousOverLd) (uplink: UlSeriousOverLd, downlink: DlSeriousOverLd)，
But over the threshold for releasing from overload state
5. Load over the threshold of serious

4. Load below the threshold for overload
releasing from overload state (uplink: UlSeriousOverLd,
(uplink: UlAlrmLd, downlink: DlAlrmLd) downlink: DlSeriousOverLd)
serious
overload
Note: When a cell is set up, the cell load is normal.
1. In the status of normal load, when the load is found over the common overload
threshold but below the serious overload threshold, the cell enters the status of
common overload.
2. In the status of common overload, when overload control helps decrease the load
below the threshold for releasing from overload state, the cell returns to the normal
state.
3. In the status of normal load, when the load is found over the serious overload
threshold, the cell enters the status of serious overload.
4. In the status of serious overload, when the overload control helps decrease the load
state.

5. In the status of common overload, when the load is found over the serious overload
6. In the status of serious overload, when the overload control helps decrease the load
below the serious overload threshold but above the threshold for releasing from
overload state (including over the common overload threshold), the cell enters the
status of common overload.
7. These mutual conversions between overload control states are implemented in the
directions of uplink and downlink respectively.
3.1.3 Load Decrease Methods for R99 Overload Control
The load decrease measures available with overload control include decrease of service
rate, forced handover to an inter-frequency cell or a 2G cell under the same coverage,
forced deletion of the radio link of the UE in the macro diversity state from the overloaded
cell (the forced deletion of a macro diversity link is also referred to as a mode of forced
handover), transfer of interactive and background services to the RACH/FACH channel,
decreasing GBR (GBR renegotiation) and forced drop of service. The following outlines
these load decrease methods:
 Downgrading
 Forced handover
 Forced transfer of DCH to FACH (only for downlink overload control)
 Call drop (service disconnection)
The priorities of the methods in descending order: downgrading -> forced handover ->
forced transfer to RACH/FACH -> decreasing GBR (GBR renegotiation) ->call drop
These overload control methods are performed in the directions of uplink and downlink
respectively. That whether an overload control method is enabled can be configured in
the background.

3.1.3.1 Downgrading
Downgrading includes AMR service downgrading and PS service downgrading. The

AMR downgrading must fall within the dynamic AMR rate range supported by the RNC
and UE. For information on AMR speed grading, refer to the ZTE UMTS AMR Feature
Guide. Note that the AMR service in iur interface cannot be downgraded, and when the
AMR service downgrading forbidden switch is on (GresPara47:bit6 = 1), the AMR service
cannot be downgraded. For a subscriber with concurrent DCH service in addition to the
AMR service, downgrading is applicable only to the PS service rather than the AMR
service except for concurrence of additional HS service. The stream services of the PS
domain can be decreased to the Maximum (the lowest level of DRBC, Guarantee Bit
Rate). I/B service has no Guarantee Bit Rate (GBR). Its rate can be decreased to the
lowest level of DRBC. For details on specifying the lowest level of DRBC, refer to the
ZTE UMTS DRBC Algorithm Feature Guide.
The rate of a service can be decreased by multiple levels at a time. The rate can be
graded according to the rate levels of DRBC. The maximum number of rate levels
(UlMaxDecStg in the uplink and DlMaxDecStg in the downlink) that can be decreased at
a time is configurable through the system.
When decreasing service rate, the system selects the subscribers for which the service
rate should be decreased: First, sort all the services according to the overload control
priorities in descending order, and decrease speed for the subscribers with the lowest
priority. The system does not select a service that is already at the lowest rate. The
overload control priority adopts the settings of application priority. It is mapped based on
basic priority, bearer type, and real-time rate of a service. Since the overload control
priority is associated with the current service rate, it is necessary to remap the overload
control priority according to the new rate after the service rate is decreased. The Traffic
Rate in the table indicates the current allocated rate for the DCH, the GBR for the S traffic
of HSPA, the MBR for C traffic of HSPA, and the NBR for I/B traffic of HSPA. For NBR
(Nominal Bit Rate), refer to the ZTE UMTS QoS Feature Guide.
For details on the rules of mapping between the overload control priority and basic
priority, bearer type and service real-time rate, refer to ZTE UMTS QoS Feature Guide.

The parameter MaxNumUeOfDecRat controls the number of subscribers whose line

rates can be decreased in the uplink and downlink at a time.
The overload control can trigger the downgrading rather than the rate increase. The cell
load state serves as a constraint on the service rate increase. That is, if the current cell
load is abnormal, the rate increase is forbidden.
3.1.3.2 Forced Handover
Forced handover is to hand over the subscribers of a cell to an inter-frequency cell or a

2G cell (the target cell has the same coverage as the overloaded cell or contains the
overloaded cell), or forcedly delete macro diversity links.
If it is required to hand over a call to an inter-frequency cell or 2G cell, the overloaded cell
must be configured with an adjacent cell of different frequency with the same coverage or
a 2G cell with the same coverage, and the capability of the UE and service attributes
satisfy the requirements of inter-frequency handover or inter-RAT handover. For details,
refer to the ZTE UMTS Handover Control Feature Guide. Measurement is not applied to
the forced handover of overload control, which is known as a kind of blind handover.
Forced deletion of macro diversity link is to delete a radio link of the UE working in macro
diversity status in the overloaded cell. If the UE is in the best cell, it cannot be deleted. If
the deleted link is not in the best cell, the link deletion does not seriously affect the
service quality for the subscribers. The link deletion is applied only to downlink overload
because the uplink interference is common to all cells. If the channel quality turns poorer
due to link deletion, greater interference may occur.
To perform forced handover, the system sorts all the subscribers by overload control
priority, and then processes the subscriber with the lowest priority as needed. The
overload control priority of a subscriber is determined by the service with the highest
overload control priority among all his services.
priority, bearer type and service real-time rate, refer to the ZTE UMTS QoS Feature
Guide.

The maximum number of subscribers allowed in a forced uplink handover is controlled by

the parameter UlMaxForHoNum; the maximum number of subscribers allowed in a
forced downlink handover and the maximum number of downlink radio links that can be
deleted each time are controlled by the parameter DlMaxForHoNum.
3.1.3.3 Forced Transfer to FACH
Forced transfer to FACH means to decrease the system load by migrating interactive and
background subscribers to RACH/FACH channels in the case of downlink overload. (Do
not perform this operation unless all the services of the subscriber are of the I/B
category.)
To perform forced transfer to FACH, the system should sort all interactive and
background subscribers by overload control priority first, and then start with the
subscriber with the lowest priority as needed. Because the operation of forced transfer to
FACH is for a subscriber, when the subscriber has multiple RABs, and the RABs have
different overload control priorities, RNC should select the highest overload control
priority among all the services of the subscriber.
Guide. The maximum number of subscribers allowed in a transfer is controlled by the
parameter NFach.
3.1.3.4 GBR Decrease
When a cell is in the status of common overload, the QoS negotiation/renegotiation

(QosNegRenegSwi) is set to enable the QoS renegotiation, and shielding GBR reduction
(DecGbrSw) is switched on through the system, GBR decrease targets at services with
the current GBR higher than their lowest level of negotiation GBR and decreases GBR to
their lowest level negotiation GBR at a time.
When performing GBR decrease, the system sorts all the services according to the
overload control priorities in descending order, and decreases GBR of the subscriber
with the lowest priority. It is necessary to remap the overload control priority with the new
GBR after the HSPA S GBR is decreased. The maximum number of services of GBR

decrease that can be performed at a time is configured by the parameter

(MaxGbrDecNum) through the system.
Note:
1 The GBR exists in the C and S service only.
2 The overload control priority is mapped from the BP, rate, and bearer type, where
the rate is MBR for HSPA C traffic, GBR for HSPA S traffic, and the current allocated
rate for the R99 traffic. It is necessary to remap the overload control priority for the
HSPA S traffic with the new GBR after the GBR is decreased, but there is no need
for the R99 traffic.
3 For details of the GBR negotiation and the parameters QosNegRenegSwi,

DecGbrSw, and MaxGbrDecNum involved, refer to the ZTE UMTS Services and
Radio Access Bearers Feature Guide.
3.1.3.5 Call Drop
Forced service drop is a measure taken to release the RAB with low overload control
priority when the methods mentioned above are invalid or do not achieve the desired
results.
Call drop triggered by overload control mechanism is performed for RABs. When there
are multiple RABs for a subscriber, it is unnecessary to process the priorities.
To perform call drop, the system should sort all the subscribers by overload control
priority first, and then start with the subscriber with the lowest priority as needed.
Guide.
The maximum number of subscribers allowed in a forced uplink call drop is controlled by
the parameter UlMaxDrpUsrNum; the maximum number of subscribers allowed in a
forced downlink call drop is controlled by the parameter DlMaxDrpUsrNum.

3.1.4 Load Decrease Methods for R99 Common Overload
When the system load rises over the common overload threshold, the system enters the
status of common overload. It is necessary to take appropriate load decrease measures.
The load decrease action continues until the system load drops below the threshold for
releasing from overload state.
The load decrease for the common overload goes through the following steps:
1. If the downgrading switch (UlLdCtrlDecRateSw for the uplink and

DlLdCtrlDecRateSw for the downlink) is on, and the cell contains services with high
rates, sort the service according to the priorities of these services in ascending
order, and then decrease the rates of the services. For details on downgrading,
refer to “3.1.3.1 Downgrading".
2. If the forced handover switch (UlLdCtrlForceHoSw for the uplink and

DlLdCtrlForceHoSw for the downlink) is on, and the cell contains subscribers
supporting forced handover, sort the subscribers according to the priorities in
ascending order, and then perform the forced handover for these subscribers. For
details on forced handover, refer to "3.1.3.2 Forced Handover".
3. For downlink overload control, if the switch of forced transfer from DCH to FACH
(SwitchToFachSw) is on, and the cell contained DCH subscribers supporting
transfer to the FACH, sort the subscribers according to the priorities in ascending
order, and then transfer these subscribers to the FACH channel. For details on
CELL_FACH method, refer to "3.1.3.3 Forced Transfer to FACH".
4. If the QoS negotiation/renegotiation (QosNegRenegSwi) is set to enable the QoS

renegotiation, shielding GBR reduction (DecGbrSw) is switched on, and the
services with GBR higher than the minimum negotiation GBR exist, the system
sorts all the services according to the overload control priorities in descending order
and decreases GBR of the subscriber with the lowest priority. For details on GBR
decrease method, refer to "3.1.3.4 GBR Decrease ". For the parameter DecGbrSw,
refer to the ZTE UMTS Services and Radio Access Bearers Feature Guide.
5. If the forced call drop switch (UlLdCtrlDropSw for the uplink, and DlLdCtrlDropSw
for the downlink) is on, and the cell contains some subscribers available for forced

call drop, the system selects certain number of subscribers for call drop by priority in
an ascending sequence. For more details, refer to "3.1.3.5 Call Drop".
The figure below shows the common overload control flowchart.
Figure 3-4 R99 common overload control flowchart
Find the methods of load

decreasing is supported by
each UE in the cell
The switch of downgrading is on Yes Downgra

(UlDecRateSw=1 for uplink; DlDecRateSw=1
de
for downlink) ?
No
The switch of forced handover is on Yes Forced
(UlForceHandoffSw=1 for uplink;
Handover
DlForceHandoffSw=1 for downlink) ?
No
The downlink overload control and the switch Transfer

Yes DCH to
of transferring DCH to FACH of I/B traffic is FACH of
on (SwitchToFach=1 ) ? I/B traffic
No
Yes Decreasing
The switch of shielding GBR reduction is on
GBR of
(DecGbrSw=1 ) ? C/S traffic
No
The switch of forced call drop is Yes Forced
on(UlDropSw=1 for uplink; DlDropSw=1 for
Call Drop
downlink) ?
No
End
3.1.5 Load Decrease Methods for R99 Serious Overload
When the system load rises over the serious overload threshold, the system enters the
status of serious overload. For quick decrease of cell load, the system should force
service drop to release the calls of some subscribers in the cell. That is to perform the
forced service drop in the common overload control process which is described in
section “3.1.3.4 Call Drop”. When the system load recovers below the serious overload
threshold, the system enters the status of common overload, and performs the

downgrading and forced handover for the common overload.
The figure below shows the serious overload control flowchart:
Figure 3-5 R99 serious overload control flowchart
Start
Forced Call Drop
Load is below the threshold of the serious

overload(uplink: UlSeriousOverLd,
No downlink: DlSeriousOverLd) ?
Yes
Load is below the threshold of load
Decreasing load with the method
recovery (uplink: UlAlrmLd, downlink: of common overload
DlAlrmLd)?
No
Yes
End
3.1.6 Related Measurement of R99 Algorithm
3.1.6.1 Node B Common Measurement
The Node B common measurement information required for R99 overload control
includes:
 Received Total Wideband Power (RTWP)
 Transmitted Carried Power (TCP)
The Node B reports the measurement results to the RNC periodically. Overload control
judges whether the overload control trigger condition is satisfied. If yes, the overload
control process is started. For Node B common measurement, refer to the ZTE UMTS

Node B Management Feature Guide.
3.2 HSDPA Overload Control
As the overload control is performed in the uplink and downlink separately, and HSDPA
involves downlink alone, this section only describes the policies for downlink overload
control in the cells supporting the HSDPA.
In a cell supporting HSDPA, the overload control policies are performed in two
conditions:
1. NoHsPower >= R99 common overload threshold (DlOverLdThr), or NoHsPower >=

R99 serious overload threshold (DlSeriousOverLdThr), where NoHsPower is the
Transmitted Carrier Power Of All Codes Not Used For HSTransmission in the
common measurement report:
In the case of NoHsPower >= R99 common overload threshold (DlOverLdThr),

enable HS load decrease or R99 load decrease according to the setting of the
parameter AglLdDec. If the algorithm of load decreasing (AglLdDec) is set to R99
load decrease algorithm, start the R99 load decrease for the DCH services (the
downgrading action targets at the services carried over the DPCH channel; forced
handover targets at the subscribers of the DPCH physical channel; call drop targets
at the services over the DCH channel). The load decrease policy is similar to that
described in "3.1.3 Load Decrease Methods for R99 ". If the algorithm of load
decrease (AglLdDec) is set to HS load decrease algorithm, the load decrease
action targets at the DCH and HS-DSCH subscribers. The load decrease actions
and priorities based on subscriber selection policies are the same as those
described in "3.2.3 Load Decrease Methods for HSDPA Overload Control".
In the case of NoHsPower >= R99 serious overload threshold

(DlSeriousOverLdThr), the call drop action targets at the DCH service at first. If
there is no DCH subscriber, the call drop action targets at the HS service. The
methods to decease the load are the same as those adopted for R99 serious
overload.

 HsRe quiredPower
sp i
2. When there are HS subscribers and NoHsPower + >=
HS overload threshold, where HsRequiredPower is the HS-DSCH Required Power
in the common measurement report, the system starts the load decrease policies
described in 3.2.3.
If the conditions specified in (1) and (2) are satisfied simultaneously, the system
implements the load decrease policies of (1).
3.2.1 HSDPA Overload Control Flow
Figure 3-6 shows the overload control flowchart of the HSDPA cell. The overload control
includes R99 common overload control, R99 serious overload control, and HS overload
control. The overload control is triggered by common measurement reports from the
Node B. In the case of R99 common overload control, the AglLdDec switch may trigger
different load decrease actions. The load decrease actions also target at different object
set.
For a cell supporting the HSDPA, this section only describes the downlink overload
control. The uplink overload control is the same as that for the R99 cells. Therefore, the
uplink overload control is omitted here.

Figure 3-6 Overload control flowchart for the HSDPA cells
Common
measurement
report of node B
Load status
judgment
Normal R99 common R99 serious HS

load overload overload overload
AglLdDec indicate No Reduce load of

Reduce load of
Back R99 reducing R99 serious
HS overload
load? overload
Yes
Reduce Load of
R99 overload
3.2.2 Decision Methods for Conversion between HSDPA Overload Control

States
3.2.2.1 Classification of HSDPA Overload Control States
For a cell supporting the HSDPA, two thresholds are set for the HS overload control (the
R99 thresholds are omitted here):
 HS-DSCH common overload threshold (HsdschOverLdThr)
 Threshold for Releasing from HS-DSCH Overload (HsdschRecoverThr)
HsdschOverLdThrHsdschRecoverThrA has four states according to the comparison

between the current load and each threshold: normal load, R99 common overload, R99
serious overload, and HS overload.

3.2.2.2 Conversion between HSDPA Overload Control States
With the change of load on a cell, the four states of overload described in figure 3-7 are
inter-convertible in a relationship as shown below, where the status of R99 overload
includes R99 common overload and R99 serious overload:
Figure 3-7 Conversion between HSDPA overload control states
NoHsPower+HsRequiredPower below the threshold for releasing

from hs overload(HsdsRecoverThr) and NoHsPower below
the threshold of R99 common overload(DlOverLd)
NoHsPower+HsRequiredPower over the threshold of
hs overload(HsdsOverLdThr) and NoHsPower below
the threshold of R99 common overload(DlOverLd)
Hs overload
Normal load NoHsPower over the threshold of
R99 common Overload(DlOverLd) or
serious overload(DlSeriousOverLd)
NoHsPower+HsRequiredPower over the threshold

of hs overload(HsdsOverLdThr) and NoHsPower
belowthe threshold the threshold for releasing
from R99 overload(DlAlrmLd)
NoHsPower+HsRequiredPower below the threshold

for releasing from hs overload(HsdsRecoverThr)
R99 overload
and NoHsPower below the threshold for releasing
from R99 overload(DlAlrmLd)
NoHsPower over the threshold of R99
common overload(DlOverLd)
or serious overload(DlSeriousOverLd)
Process description: When a cell is set up, the cell load is normal.
1. In the normal state, when NoHsPower is found below the R99 common overload
sp i
threshold, and NoHsPower+ exceeds the HS overload
threshold, the cell enters the status of HS overload.
2. In the status of HS overload, when NoHsPower is found below the R99 common
sp i
overload threshold, and NoHsPower+ decreases below
the threshold for releasing from HS overload, the cell returns to the normal state.

3. In the normal state, when NoHsPower is found over the R99 common overload
threshold but below the R99 serious overload threshold, the cell enters the status of
R99 common overload.
4. In the normal state, when NoHsPower is found over the R99 serious overload
threshold, the cell enters the status of R99 serious overload.
5. In the status of R99 common overload, when NoHsPower is found over the R99
serious overload threshold, the cell enters the status of R99 serious overload.
6. In the status of R99 serious overload, when NoHsPower is found down below the
R99 serious overload threshold but above the threshold for releasing from R99
overload (including over the R99 common overload threshold), the cell enters the
status of R99 common overload.
7. In the status of R99 common or serious overload, when NoHsPower is found down
below the threshold for releasing from R99 overload, and NoHsPower+
sp i is below the threshold for releasing from HS overload,
the cell returns to the normal state.
8. In the status of R99 common or serious overload, when NoHspower is found down
below the threshold for releasing from R99 overload, and NoHsPower+
sp i is over the HS overload threshold, the cell enters the
status of HS overload.
3.2.3 Load Decrease Methods for HSDPA Overload Control
The R99 overload and the HS overload exist in cells supporting HSDPA. In the case of
R99 common overload, there are two load decrease methods, R99 load decrease
method and HSDPA load decrease method. The R99 load decrease method is described
in section 3.1.4, so there is no need to describe it again.
This chapter focuses on the status of HS overload and load decrease actions. The HS
load decrease can be performed with the following methods:
 Downgrading

 Forced handover
 Forced transfer to FACH
 Call drop
The priorities of the above five load decrease methods can be sorted as downgrading ->
forced handover -> forced transfer to FACH -> decreasing GBR (GBR renegotiation) ->
call drop.
You can configure switches to control the use of the above overload control methods. For
details on the switch parameters, refer to 3.2.4. The following contents only describe the
differences between the above methods and the methods applied in R99 cells.
3.2.3.1 Downgrading
Since the RNC cannot control the rate of HSDPA services, the downgrading for the HS
load decrease actually means to decrease the rate of DCH services as well, and the
downgrading method is the same as that for the R99 cells.
Forced handover is to hand over the subscribers of a cell to an inter-frequency cell or a

2G cell (the target cell has the same coverage as the overloaded cell or contains the
overloaded cell), or forcedly delete macro diversity links.
Forced handover to an inter-frequency cell or a 2G cell under the same coverage is only
applied to the subscribers with DCH services and the subscribers with streaming class
services on the HS-DSCH in the cell. The deletion of macro diversity link is based on a
DPCH channel. If the cell is the serving cell of the UE HS-DSCH or the best cell of DCH
channel, the link cannot be deleted even though the DPCH channel is in the macro
diversity status. If the cell is not a serving cell of UE HS-DSCH, the associated DPCH
channel can be deleted.

When forcedly handing over services to an inter-frequency cell with the same coverage,
the system first sorts the DCH subscribers or the subscribers of the stream services
carried over the HS-DSCH channel according to overload control priorities, and then
performs the forced handover for the subscriber with the lowest priority. When there are
multiple concurrent services, the system selects the service with the highest overload
control priority among all the services of the subscriber.
The method for selecting the UE on the HS for link deletion: first make sure the UE is in
the macro diversity state and the cell is not its HS-DSCH serving cell, and then make
selection by the application priority of the overload control on the DCH in an ascending
sequence (note: if there is only signaling on the DCH, the rate used by the subscriber to
determine its application priority should be set to the signaling rate, and other parameters
should follow the RAB parameters on the HS-DSCH. If there are multiple RABs, the one
with the highest overload control should be followed). If there are concurrent services on
the DCH, the overload control priority should be determined by the service with the
highest priority.
The overload control priority is obtained by mapping the basic priority (BP), bearer type,
and subscribers’ real-time rate. For stream services carried over the HS-DSCH channel,
the real-time rate of the stream service is GBR; for HSPA C traffic, the real-time rate is
MBR; for I/B service, the real-time rate is NBR for I/B traffic of HSPA. For the NBR
(Nominal Bit Rate), refer to the ZTE UMTS QoS Feature Guide.
DlMaxForHoNum (the maximum number of subscribers involved in a forced handover or

the maximum number of links deleted at a time) is the same as the parameter adopted by
R99 downlink overload control and can be configured at the OMC.
3.2.3.3 Forced Transfer to FACH
Forced transfer to FACH means transfer of interactive and background RABs to the
FACH channel. This action is applied to all the services in the cell. As the associated
channel of the HS-DSCH subscribers also occupies certain power, if this action is not
performed on the HS-DSCH service, the last resort for the subscriber will be service drop
when the cell has only HS-DSCH service and is overloaded.

To perform forced transfer to FACH, the system should first sort all interactive and
background subscribers by overload control priority, and then start with the subscriber
with the lowest priority as needed. The overload control priority of a subscriber is
determined by the service with the highest overload control priority among all the
services.
For details on the factors related to overload control priorities and mapping methods,
refer to the ZTE UMTS QoS Feature Guide. For I/B traffic, the real-time rate is NBR for
I/B traffic of HSPA. For the NBR (Nominal Bit Rate), refer to the ZTE UMTS QoS Feature
Guide.
The maximum number of subscribers in a forced transfer (NFach) is the same as the
parameter used in R99 overload control, and can be configured through the system.
The method of GBR decrease in HSPA is same as that in R99, referring to 3.1.3.4. Note
that it is necessary to remap the overload control priority with the new GBR after the
HSPA S GBR is decreased.
3.2.3.5 Call Drop
Forced service drop means to choose and release some RABs. The objects for release
are all the subscribers’ RABs in the cell, for the associated channel DPCH of the
HS-DSCH subscribers also occupies certain power.
Call drop triggered by overload control mechanism is based on RABs. When there are
multiple RABs in a subscriber, it is unnecessary to process the priorities.
To perform call drop, the system should first sort all the subscribers by overload control
priority, and then start with the subscriber with the lowest priority as needed.
Overload control priority is mapped by the basic priority (BP), bearer type, and
subscribers’ real-time rate. For stream services carried over the HS-DSCH channel, the
real-time rate of the stream service is GBR; for HSPA C traffic, the real-time rate is MBR;
for I/B service, the real-time bit rate is NBR for I/B traffic of HSPA. For the NBR (Nominal
Bit Rate), refer to the ZTE UMTS QoS Feature Guide.

The maximum number of subscribers in a call drop event (DlMaxDrpUsrNum) is the

same as the parameter used in R99 overload control, and can be configured through the
system.
3.2.4 HSDPA Load Decrease Flow
When the system load rises over the HS overload threshold, the system enters the status
of HS overload, making it necessary to take appropriate load decrease measures. The
load decrease action continues until the system load drops below the threshold for
releasing from HS overload. The load decrease methods for HS overload involve the R99
load decrease and HS load decrease. This section describes the selection and execution
of HS load decrease only.
The load decrease for the HS overload goes through the following steps:
1. If the downgrading switch (DlLdCtrlDecRateSw) is on and the cell contains services

with high rates, sort the services according to the priorities in ascending order and
then decrease the rates of the services. For details on downgrading, refer to
"3.2.3.1 Downgrading".
2. If the forced handover switch (DlLdCtrlForceHoSw) is on, when the cell is the best
cell of DCH channel or the serving cell of HS-DSCH channel of the UE (the UE has
a single radio link or macro-diversity radio links), if there were inter-frequency cells
or a 2G cell has the same coverage or contains the overloaded cell, sort the UEs
according to the priorities in ascending order, and then perform the forced handover
for these UEs. When the cell is neither the best cell of DCH channel nor the serving
cell of HS-DSCH channel of the UE (the UE is only in macro-diversity condition),
sort the UEs according to the priorities in ascending order, and then delete macro
diversity links for these UEs. For details on forced handover and deleting
macro-diversity radio link, refer to "3.2.3.2 Forced Handover".
3. If the switch of forced transfer from DCH to FACH (SwitchToFachSw) is on and the
cell contains the DCH subscribers supporting transfer to the FACH, sort the
subscribers according to the priorities in ascending order, and then transfer these
subscribers to the FACH channel. For details on transfer to CELL_FACH method,
refer to "3.2.3.3 Forced Transfer to FACH".


sorts all the services according to the overload control priorities in descending order,
and decreases GBR of the subscriber with the lowest priority. For details on GBR
decrease method, refer to "3.2.3.4 GBR Decrease ". For the parameter DecGbrSw,
refer to the ZTE UMTS Services and Radio Access Bearers Feature Guide.
5. If the forced call drop switch (DlLdCtrlDropSw) is on and the cell contains the
subscribers supporting forced handover, sort the subscribers according to the
priorities in ascending order, and then perform the forced handover for these
subscribers. For details on call drop, refer to "3.2.3.5 Call Drop".
The figure below shows the HS overload control flowchart:

Figure 3-8 HSDPA overload control flowchart
Strat
Switch for Downgrade

Yes
is on
(DlDecRateSw=1)?
Exist traffic Yes
can be Downgrade
No downgrade?
No
Switch for Forced
Handover or Deleting RL Yes
of Macro Diversity is on
(DlForceHandoffSw=1) ?
The cell is the best cell of NO Deleting RL of
DCH channel or the Macro Diversity
serving cell of HS-DSCH (UE in macro-
channel of the UE? diversity)
Yes
No there were inter- Forced Handover
frequency cells or 2G Yes (UE has single RL
cells have the same
coverage or contains or macro-diversity
the overloaded cell? RLs)
No
Switch for Transfer DCH Yes

to FACH of I/B traffic is on
(SwitchToFach=1)? Transfer DCH to
Can be Yes
converted to FACH of I/B
No FACH? traffic
No
Switch for shielding GBR Yes
reduction is on
(DecGbrSw=1)? QoS renegotiation switch is
Yes
open? And exist C/S services Decreasing GBR
No can be renegotiationed to of C/S traffic
lower GBR level?
No
Switch for Call Drop

Yes
is on Call Drop
(DlDropSw=1)?
No
End
3.2.5 Dual-Cell HSDPA Overload Control
As the single cell HSDPA overload control, the priorities of the overload control methods
for the dual-cell HSDPA is in descending order: downgrading -> forced handover ->
forced transfer to RACH/FACH -> decreasing GBR (GBR renegotiation) -> call drop. But

if the overload cell is the secondary frequency cell of the selected UE, the overload
method will be changed to remove the secondary frequency.
3.2.6 Related Measurement of HSDPA Algorithm
The Node B common measurement information required for HSDPA overload control
includes:
 HS-DSCH Required Power (HsRequiredPower)
 Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH
transmission (NoHsPower)
control process is started. For the Node B common measurement, refer to the ZTE
UMTS Node B Management Feature Guide.
3.3 HSUPA Overload Control
In the cell supporting E-DCH, the Node B can effectively control the fluctuation of the
uplink RTWP. Therefore, the overload threshold of the E-DCH cell is higher than the
uplink overload threshold configured for a common R99 cell. The database does not add
new thresholds and still uses the original common overload threshold and serious
overload threshold of the DCH.
In addition to the normal overload control mechanism of the RNC, Node B also controls
the load of the UE in the non-service link of the E-DCH through the scheduling
mechanism of the HSUPA. The RNC can also set up a physically-shared channel to the
Node B and configure the parameter NServToTotalPwr which is the percentage of the
E-DCH received power of the non-service link over the total E-DCH received power. The
percentage of the received power over the total received power of the E-DCH is
NServToTotalPwr. Node B keeps NServToTotalPwr to control the scheduling of the

E-DCH so that the percentage of the power of the E-DCH subscriber in the non-service
link of the cell over the power of all E-DCH subscribers does not exceed
NServToTotalPwr. To achieve this purpose, Node B sends DOWN message (power
decrease authorization) to the UE in the non-service link.
As the measurement information of the RSEPS was introduced, the uplink load state of
HSUPA cell is judged based on the uplink effective load.
3.3.1 HSUPA Uplink Effective Load
In order to forecast the uplink interference and judge the uplink load state, it is necessary
to know the uplink effective load, which is the part of the load that Node B cannot control.
For the method to calculate the uplink effective load of HSUPA cell and the relative
parameters, please refer to the ZTE UMTS Admission Control Feature Guide.
3.3.2 HSUPA Overload Control Flow
The figure below shows the overall overload control flowchart. The overload control is
classified into serious overload control and common overload control depending on
different overload states. The overload control is triggered by the common measurement
reports from the Node B.
Upon the receipt of a common measurement report from the Node B, the system decides
the status of overload control with the methods described in section 3.3.3, and performs
an appropriate process depending on the decision result. In the status of common
overload, the common overload control is performed; in the status of serious overload,
the serious overload control is performed.
The overload control described in this section is specific to the uplink direction.

Figure 3-9 HSUPA overload control flowchart
Common Measurement
Report
To make a
decision
for status
The status of The status of The status of common

normal load serious overload overload
To perform serious To perform common

Return
overload control overload control
3.3.3 Decision Methods for Conversion between HSUPA Overload Control

States
3.3.3.1 Classification of HSUPA Overload Control States
There are three thresholds available to set for the HSUPA overload control. They are
serious overload threshold (UlSeriousOverLdThr*), common overload threshold
(UlOverLdThr*), and threshold for releasing from overload state (UlRecoverLdThr*). The
recommendatory relationship between these three thresholds and the maximum target
RTWP (MaxRTWP*) is: UlSeriousOverLdThr* > UlOverLdThr* > MaxRTWP* >
UlRecoverLdThr*, as shown in the following diagram, where the relationship is specific to
the uplink direction. Thereinto, UlSeriousOverLdThr*(dBm)=cell background
noise(dBm)+ UlSeriousOverLdThr(dB); UlOverLdThr*(dBm)= cell background
noise(dBm)+ UlOverLdThr(dB); UlRecoverLdThr*(dBm) = cell background noise(dBm)+
UlRecoverLdThr(dB); MaxRTWP*(dBm)= cell background noise(dBm)+ MaxRTWP(dB).
For the method to get cell background noise, refer to the ZTE UMTS Admission Control
Feature Guide.

The E-DCH cells adopt the common overload threshold and serious overload threshold
configured for the original DCH. The serious overload threshold is configured the same
as the DCH, while the common overload threshold in the E-DCH cells is configured
higher than that in the DCH cells.
Figure 3-10 Classification of HSUPA overload control states
The Uplink Load

The Threshold of Serious
Overload(UlSeriousOverLd*)
The Threshold of Common

Overload(UlOverLd*)
Maximum Target RTWP(MaxRTWP*)

Forbid to use in the period of releasing from
overload state
The Threshold for Releasing from

Overload State(UlAlrmLd*)
Depending on the load on a cell, overload control is performed in three states: normal
load, common overload, and serious overload.
3.3.3.2 Conversion between HSUPA Overload Control States
With the change of load on a cell, the three states of overload control are
inter-convertible in a relationship as shown below:

Figure 3-11 Conversion between HSUPA overload control states
1. Load over the threshold of common overload

(UlOverLd*)
2. Load below the threshold for

normal common
releasing from overload state
load overload
(UlAlrmLd*)
3. Load over the threshold of serious 6. Load below the threshold of serious
overload (UlSeriousOverLd*) overload(UlSeriousOverLd*),
but over the threshold for releasing from
overload state (UlAlrmLd*)
4. Load below the threshold for 5. Load over the threshold of serious
releasing from overload state overload (UlSeriousOverLd*)
(UlAlrmLd*)
serious
overload
Note: When a cell is set up, the cell load is normal.
1. In the normal state, when the load is found over the common overload threshold but
below the serious overload threshold, the cell enters the status of common
overload.
2. In the status of common overload, when overload control helps decrease the load
state.
3. In the normal state, when the load is found over the serious overload threshold, the
cell enters the status of serious overload.
4. In the status of serious overload, when overload control helps decrease the load
state.
5. In the status of common overload, when the load is found over the serious overload

6. In the status of serious overload, when overload control helps decrease the load
below the serious overload threshold but above the threshold for releasing from
overload state ((including over the common overload threshold), the cell enters the
status of common overload.
7. These mutual conversions between overload control states are implemented in the
direction of uplink.
3.3.4 Load Decrease Methods for HSUPA Overload Control
In the overload state, the Node B has decreased the rate of non-GBR services on the
E-DCH down to a very low level and the rate of GBR services on the E-DCH down to the
guaranteed bit rate (GBR) through scheduling. That is, it is impossible now for the Node
B to decrease the uplink load further through scheduling, and the load can be decreased
only by the RNC through overload control.
The RNC can take the overload control measures as follows:
 Downgrading
 Forced handover
 Call drop
The priorities of the above four methods can be sorted as downgrading -> forced
handover-> decreasing GBR (GBR renegotiation) ->forced call drop.
3.3.4.1 Downgrading
Downgrading is only applied to the DCH services, including PS service and CS service,
in the same way as that for the R99 cells.
Forced handover is to forcedly hand over DCH subscribers to an inter-frequency

adjacent cell or a 2G cell (the target cell has the same coverage as the overloaded cell or

contains the overloaded cell). Forced handover targets at all subscribers of the specified
cell, including DCH and E-DCH subscribers. Performing forced handover selects target
subscriber according to the overload control priority. The overload control priority is
mapped from the BP, real-time rate, and bearer type. The real-time rate is GBR for the
HSUPA S traffic, MBR for the HSUPA C traffic, NBR for the HSUPA I/B traffic, and the
current allocated rate for the DCH traffic. For the mapping rules between overload control
priority and BP, Bearer type and real-time rate, and NBR (Nominal Bit Rate) of the I/B
traffic, refer to the ZTE UMTS QoS Feature Guide.
If the subscriber selected for handover is an E-DCH subscriber, the system selects an
E-DCH cell with the same coverage; if the handover fails or the mentioned cell does not
exist, the handover process accompanies the transfer from the E-DCH to the DCH.
The method of GBR decrease in HSPA is the same as that in R99, referring to 3.1.3.4.
Note that it is necessary to remap the overload control priority with the new GBR after the
HSPA S GBR is decreased.
3.3.4.4 Call Drop
Forced call drop is applied to all the subscribers selected according to the overload
control priority (3.3.4.2) in the overloaded cell. The subscriber might be either a DCH
subscriber or an E-DCH subscriber. The specific steps are the same as those for the R99
cells.
3.3.5 Load Decrease Methods for HUSPA Common Overload
When the system load rises over the common overload threshold, the system enters the
status of common overload. It is necessary to take appropriate load decrease measures.
The load decrease action continues until the system load drops below the threshold for
releasing from overload state.
The load decrease for the common overload goes through the following steps:

1. If the uplink DCH downgrading switch (UlLdCtrlDecRateSw) is on and there are

DCH services to be decreased in the uplink, the system implements the uplink DCH
downgrading flow. For more details, refer to "3.3.4.1 Downgrading".
2. If the uplink forced handover switch (UlLdCtrlForceHoSw) is on and there is an

inter-channel cell with the same coverage, the system implements forced handover.
For more details, refer to "3.3.4.2 Forced Handover".

sorts all the services according to the overload control priorities in descending order,
and decreases GBR of the subscriber with the lowest priority. For details on the
GBR decrease method, refer to "3.3.4.3 GBR Decrease ". For the parameter
DecGbrSw, refer to the ZTE UMTS Services and Radio Access Bearers Feature
Guide.
4. If the uplink forced call drop switch (UlLdCtrlDropSw) is on, the system implements
the forced call drop. This method is the same as that for the R99, and the DCH and
E-DCH subscribers are considered. For more details, refer to "3.3.4.4 Call Drop”.
3.3.6 Load Decrease Methods for HSUPA Serious Overload
When the system load rises over the serious overload threshold, the system enters the
status of serious overload. For quick decrease of cell load, the system should perform
forced service drop to release the calls of some subscribers in the cell. That is to perform
the forced service drop in the common overload control process. When the system load
recovers below the serious overload threshold, the system enters the status of common
overload and performs the common overload control.
3.3.7 Related Measurement of HSUPA Algorithm
The Node B common measurement information required for HSUPA overload control
includes:

 E-DCH Provided Bit Rate
In this common measurement information, we can get the current rate for different SPI of
the scheduling E-DCH services.
 Received scheduled E-DCH power share
This common measurement information contains the RSEPS and RTWP*. In this
information we can get the RTWP of current cell and the RTWP produced by scheduling
E-DCH services.
control process is started. For the Node B common measurement, refer to the ZTE
UMTS Node B Management Feature Guide.
3.4 MBMS Overload Control
For details on the technical description on MBMS overload control, refer to the MBMS
Technical Attribute Description.
3.5 GBR Resource Consumption Limit
Because GBR services need to guarantee the GBR, when the radio condition is poor, it
will consume too many resources of the cell. As the solution, ZTE RNC can limit the GBR
resource consumption.
For R99 and HSUPA services, the maximum power of DCH and E-DCH channel is
configured to limit the DCH and E-DCH transmit power. In this way, the GBR resource
consumption can be limited.
For HSDPA services, the HS-DSCH Required Power Per UE Weight (Expressed in
percentage of the value provided in the HS-DSCH Required Power Value IE) can be
adopted to limit the GBR resource consumption in the common measurement report.

3.5.1 HSDPA GBR Resource Consumption Limit Algorithm
When the switch for limiting the HSDPA GBR resource consumption (HsGBRLimitSwi) is
on, the following method can be used to limit the HSDPA GBR resource consumption.
When the required power of HSDPA GBR service is bigger than a threshold
(RequiredPower> RequiredPowerlimit), if the GBR of this service can be decreased by
the method of GBR renegotiation, the GBR of this service would be decreased, and if the
GBR of this service cannot be decreased, the service would be forced drop. For the
description of the GBR decrease, please refer to section 3.1.3.4 of this paper and the
ZTE UMTS Services and Radio Access Bearers Feature Guide.
Therein,
1 The required power of HSDPA GBR service is got form the HS-DSCH Required
Power Per UE Weight (Expressed in percentage of the value provided in the
HS-DSCH Required Power Value IE) in the common measurement report, and it
needs to be converted to an absolute value (unit: dBm).
2 RequiredPowerlimit(dBm) is the upper limit for HS-DSCH required power. Firstly, get
the required power offset (dB) relative to P-CPICH power from the array
UEHsReqPwrUplim[MAX_NUM_HS_GBR] according to the GBR grade of the
service, and then add the P-CPICH power (dBm). The result is RequiredPowerlimit
(dBm). Here, UEHsReqPwrUplim[MAX_NUM_HS_GBR] is UE HS-DSCH required
power upper limit for limiting the HSDPA GBR resource consumption according to
each GBR grade. Its elements and the GBR levels of HSDPA services
(HsGBRLev[MAX_NUM_HS_GBR]) have a one-to-one correspondence relationship.
The number of HSDPA GBR levels is HsGBRLevNum.
Note:
1 If the UE has concurrent HS GBR services, and the services have the same SPI, we
get the sum of the GBRs of each HSDPA GBR service with THE same SPI in one
UE, and then get the required power threshold according to this GBR sum result.
2 If the UE has concurrent services, but each service has a different SPI, we get the
required power thresholds and compare with the required power of the services
respectively. (HS-DSCH Required Power in the common measurement report is the

total required power for all services with the same SPI in the cell, while the
HS-DSCH Required Power Per UE Weight is the required power for services with
the same SPI in the same UE).
3 The HS-DSCH required power limit can make GBR decreased, and the event 4A
can make GBR increased. In order to avoid the ping-pong between GBR increase
and decrease, after the GBR is decreased by HS-DSCH required power limit, the
GBR of this service cannot be increased within 2 minutes. For the description of the
GBR increased, please refer to the ZTE UMTS Services and Radio Access Bearers
Feature Guide.
4 The parameters used in the HSDPA GBR resource consumption limit function are
obtained in the following ways: Firstly, obtain the HSDPA GBR resource
consumption limit profile (refUGbrResLimitProfile) used in the cell from the
configuration items of UCHspa. Next, obtain the MO instance of the sub-object
UGbrResLimit under the MO instance positioned in the object UGbrResLimitProfile
according to the refUGbrResLimitProfile. In these instances of the sub-object
UGbrResLimit, the related parameter configuration can be obtained.
3.5.2 Related Measurement
HS-DSCH Required Power Per UE Weight (Expressed in percentage of the value

provided in the HS-DSCH Required Power Value IE)
4 Parameters and Configurations
4.1 Common Parameters
4.1.1 Common Parameter List

Abbreviated name Parameter name
Maximum Number of UE Decreasing Rate When
MaxNumUeOfDecRat
Congestion
AglLdDec Algorithm of Load Decreasing

UlLdCtrlDecRateSw Uplink Switch for Shielding Rate Reduction
UlLdCtrlForceHoSw Uplink Switch for Shielding Forced Handover
UlLdCtrlDropSw Uplink Switch for Shielding Forced Drop
Maximum Number of Degraded Uplink Load Steps Every

UlMaxDecStg
Time
Maximum Number of Uplink Forced Handover Users Every

UlMaxForHoNum
Time
UlMaxDrpUsrNum Maximum Number of Uplink Forced Drop Users Every Time
DlLdCtrlDecRateSw Downlink Switch for Shielding Rate Reduction
DlLdCtrlForceHoSw Downlink Switch for Shielding Forced Handover
DlLdCtrlDropSw Downlink Switch for Shielding Forced Drop
Maximum Number of Degraded Downlink Load Steps Every

DlMaxDecStg
Time
Maximum Number of Downlink Forced Handover or Deleted

DlMaxForHoNum
Radio Links Users Every Time
Maximum Number of Downlink Forced Drop Users Every

DlMaxDrpUsrNum
Time
UUtranCellFDD.loadSc
Cell Load Scene
ene
4.1.2 Common Parameter Configurations
4.1.2.1 Maximum Number of UE Decreasing Rate When Congestion
 OMC Path
View -> GUI: Managed Element -> UMTS Logical Function Configuration -> UTRAN Cell
-> Load Control Information -> Maximum Number of UE Decreasing Rate When
Congestion
 Parameter configuration
The parameter is set for the load decrease triggered due to congestion. The system
decides the number of uplink/downlink DCH subscribers according to the current
congestion level.

If the system increases the value of the parameter for load decrease, the number of DCH
subscribers ready for downgrading increases accordingly, and released resources also
increase; if the system reduces the value of the parameter, the number of DCH
subscribers ready for downgrading decreases accordingly, and released resources
decreases also.
4.1.2.2 Algorithm of Load Decreasing
 OMC Path
-> Load Control Information -> Algorithm of load Decreasing
This parameter indicates the method of load decrease for common overload. When R99
common overload takes place in a cell supporting HS, the HS load decrease or the R99
load decrease will be selected.
For the R99 load decrease configuration and the R99 common overload control method,
refer to 3.1.4. For the HS load decrease configuration for all the subscribers of a cell,
including R99 and HS subscribers, refer to 3.2.4.
4.1.2.3 Uplink Switch for Shielding Rate Reduction
 OMC Path
-> Load Control Information -> Uplink Switch for Shielding Rate Reduction
This parameter indicates that whether the uplink downgrading switch is on. This
parameter is set only for the load decrease in the uplink.
If the parameter is set to be disabled, the system does not reduce rate in the uplink when
the uplink load reaches the overload threshold; if the parameter is set to be enabled, the
system reduces rate in the uplink when the uplink load reaches the overload threshold.

4.1.2.4 Uplink Switch for Shielding Forced Handover
 OMC Path
-> Load Control Information -> Uplink Switch for Shielding Forced Handover
This parameter indicates that whether the switch of the forced handover of the uplink
overload control is on. This parameter is valid only when the uplink is overloaded and it is
necessary to decrease the load.
If the parameter is set to be disabled, the system does not perform forced handover
when the uplink load reaches the overload threshold; if the parameter is set to be
enabled, the system performs forced handover for load decrease when the uplink load
reaches the overload threshold.
4.1.2.5 Uplink Switch for Shielding Forced Drop
 OMC Path
-> Load Control Information -> Uplink Switch for Shielding Forced Drop
This parameter indicates that whether the switch of the forced call drop of the uplink
overload control is on. This parameter is valid only when the uplink is overloaded.
If the parameter is set to be disabled, the system does not perform forced call drop when
the uplink load reaches the overload threshold; if the parameter is set to be enabled, the
system performs forced call drop for load decrease when the uplink load reaches the
overload threshold.
4.1.2.6 Maximum Number of Degraded Uplink Load Steps Every Time
 OMC Path

-> Load Control Information -> Maximum Number of Degraded Uplink Load Steps Every
Time
This parameter specifies the maximum number of DRBC rate steps that can be
decreased at a time in implementing the load decrease in the uplink. You can configure
the parameter in reference to the configuration of DRBC uplink rate steps.
Provided that the number of uplink DRBC rate grades is set to 2 grades [64 384], the
current bit rate is 384kbit/s and the parameter is set to 1. If the uplink rate is decreased
by 1 step, the rate is decreased to 64kbit/s. Provided that the number of uplink DRBC
rate grades is set to 3 grades [64 128 384], the current bit rate is 384kbit/s, and the
parameter is set to 1. If the uplink rate is decreased by 1 step, the rate is decreased to
128kbit/s. if the parameter is set to 2, the rate is decreased by 2 steps to 64kbit/s.
4.1.2.7 Maximum Number of Uplink Forced Handover Users Every Time
 OMC Path
View -> GUI: Managed Element -> UMTS Logical Function Configuration -> UTRAN
Cell -> Load Control Information -> Maximum Number of Uplink Forced Handover
Users Every Time
This parameter specifies the maximum number of subscribers that can be switched in
each forced handover operation when the uplink is overloaded.
To switch more subscribers in the uplink forced handover, increase the parameter; to
switch fewer subscribers in the uplink forced handover, decrease the parameter.
4.1.2.8 Maximum Number of Uplink Forced Drop Users Every Time
 OMC Path

-> Load Control Information -> Maximum Number of Uplink Forced Drop Users Every
Time
This parameter specifies the maximums number of subscribers supported in each forced
call drop operation when the uplink is overloaded.
To drop calls of more subscribers in implementing the uplink forced call drop, increase
the value of the parameter; to drop calls of fewer subscribers in implementing the uplink
forced call drop, decrease the value of the parameter.
4.1.2.9 Downlink Switch for Shielding Rate Reduction
 OMC Path
-> Load Control Information -> Downlink Switch for Shielding Rate Reduction
This parameter indicates that whether the downlink downgrading switch is on. This
parameter is set only for downgrading the load decrease in the downlink.
If the parameter is set to be disabled, the system does not reduce the rate in the downlink
when the downlink rate reaches the overload threshold; if the parameter is set to be
enabled, the system reduces the rate in the downlink when the downlink load reaches
the overload threshold.
4.1.2.10 Downlink Switch for Shielding Forced Handover
 OMC Path
-> Load Control Information-> Downlink Switch for Shielding Forced Handover

This parameter indicates that whether the switch of the forced handover of the downlink
overload control is on. This parameter is valid only when the downlink is overloaded and
it is necessary to decrease the load.
If the parameter is set to be disabled, the system does not perform forced handover
when the downlink load reaches the overload threshold; if the parameter is set to be
enabled, the system performs forced handover for load decrease when the downlink load
reaches the overload threshold.
4.1.2.11 Downlink Switch for Shielding Forced Drop
 OMC Path
-> Load Control Information -> Downlink Switch for Shielding Forced Drop
This parameter indicates that whether the switch of the forced call drop of the downlink
load control is on. This parameter is valid only when the downlink is overloaded and it is
necessary to decrease the load.
If the parameter is set to be disabled, the system does not perform forced call drop when
the downlink load reaches the overload threshold; if the parameter is set to be enabled,
the system performs forced call drop for load decrease when the downlink load reaches
the overload threshold.
4.1.2.12 Maximum Number of Degraded Downlink Load Steps Every Time
 OMC Path
-> Load Control Information -> Maximum Number of Degraded Downlink Load Steps
Every Time

This parameter specifies the maximum number of degraded downlink load steps at a
time in implementing the load decrease in the downlink. You can configure the parameter
in reference to the configuration of DRBC downlink rate grades.
Provided that the number of downlink DRBC rate grades is set to 4 [8 64 128 384], and
the current bit rate is 384kbit/s. If the parameter is set to 1 step, the downlink rate is
decreased by 1 grade to 128kbit/s. If the parameter is set to 2 steps, the rate is
decreased by 2 steps to 64kbit/s. If the parameter is set to 3 steps, the rate is decreased
by 3 steps to 8kbit/s.
4.1.2.13 Maximum Number of Downlink Forced Handover Users or Deleted Radio

Links Every Time
 OMC Path
View -> GUI: Managed Element -> UMTS Logical Function Configuration -> UTRAN
Cell -> Load Control Information -> Maximum Number of Downlink Forced Handover
Users or Deleted Radio Links Every Time
This parameter specifies the maximum number of subscribers in each forced handover
operation and the maximum number of radio links can be deleted each time when the
downlink is overloaded.
To increase the number of subscribers in downlink forced handover, increase the value
of the parameter; to decrease the number of subscribers in downlink forced handover,
decrease the value of the parameter.
4.1.2.14 Maximum Number of Downlink Forced Drop Users Every Time
 OMC Path
-> Load Control Information -> Maximum Number of Downlink Forced Drop Users Every
Time

This parameter specifies the maximums number of subscribers in each forced call drop
operation when the downlink is overloaded.
To increase the number of subscribers that can be disconnected in implementing the

downlink forced call drop, increase the value of the parameter; to decrease the number
of subscribers that can be disconnected in implementing the downlink forced call drop,
decrease the value of the parameter.
4.1.2.15 Cell Load Scene
 OMC Path
View -> GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell ->
Cell Load Scene
This parameter indicates that whether the cell is a high load cell. It should be configured
according to the load condition of the cell.
If the cell is always in high load condition, set this parameter to "1: High Load Cell";
otherwise, the parameter should be "0: Normal Load Cell".
4.2 R99 Overload Control Parameters
4.2.1 R99 Overload Control Parameter List

UlSeriousOverLdThr Uplink Serious Overload Threshold(dB)
UlOverLdThr Uplink Common Overload Threshold(dB)
UlRecoverLdThr Threshold for Releasing from Uplink Overload(dB)
DlSeriousOverLdThr Downlink Serious Overload Threshold(%)
DlOverLdThr Downlink Common Overload Threshold (%)
DlRecoverLdThr Threshold for Releasing from Downlink Overload(%)

Switch of Interactive Class/Background Class RAB->FACH

SwitchToFachSw
for Overload
Maximum Users of Interactive Class/Background Class

NFach
RAB->FACH for Overload
GresPara47 Golbal Reserved Parameter 47
4.2.2 Configuration of R99 Overload Control Parameters
4.2.2.1 Uplink Serious Overload Threshold (dB)
 OMC Path
-> Load Control Information -> Uplink Serious Overload Threshold (dB)
This parameter indicates the threshold of the uplink serious overload.
If the value of the uplink load of the current cell exceeds this parameter, the system is in
the status of serious overload and it is needed to take measures to decrease the load.
If the value of the parameter increases, it is relatively difficult to trigger uplink serious
overload; if the value of the parameter decreases, it is relatively easy to trigger uplink
serious overload.
4.2.2.2 Uplink Common Overload Threshold (dB)
 OMC Path
-> Load Control Information -> Uplink Common Overload Threshold (dB)
This parameter indicates the threshold of the uplink common overload.

If the value of the uplink load of the current cell exceeds this parameter, the system is in
the status of common overload and it is needed to take measures to decrease the load.
If the value of the parameter increases, it is relatively difficult to trigger uplink common
overload; if the value of the parameter decreases, it is relatively easy to trigger uplink
common overload.
4.2.2.3 Threshold for Releasing from Uplink Overload (dB)
 OMC Path
-> Load Control Information -> Threshold for Releasing from Uplink Overload (dB)
This parameter indicates the threshold for releasing from uplink overload state.
If the value of the uplink load of the current cell is lower than this parameter, the system
is not overloaded and the load decrease measures can be stopped. If the value of the
parameter increases, it is relatively easy to reach the threshold for releasing from uplink
overload state; if the value of the parameter decreases, it is relatively hard to reach the
threshold for releasing from uplink overload state.
4.2.2.4 Downlink Serious Overload Threshold(%)
 OMC Path
-> Load Control Information -> Downlink Serious Overload Threshold (%)
This parameter indicates the downlink serious overload threshold.
If the value of the downlink load of the current cell exceeds this parameter, the system is
in the status of serious overload and it is needed to take measures to decrease the load.
If the value of the parameter decreases, it is relatively easy to trigger downlink serious

overload. If the value of the parameter increases, it is relatively hard to trigger downlink
serious overload.
4.2.2.5 Downlink Common Overload Threshold (%)
 OMC Path
-> Load Control Information -> Downlink Common Overload Threshold (%)
This parameter indicates the downlink common overload threshold.
If the value of the downlink load of the current cell exceeds this parameter, the system is
in the status of common overload and it is needed to take measures to decrease the
downlink load immediately. If the value of the parameter increases, it is relatively difficult
to trigger downlink common overload; if the value of the parameter decreases, it is
relatively easy to trigger downlink common overload.
4.2.2.6 Threshold for Releasing from Downlink Overload (%)
 OMC Path
-> Load Control Information -> Threshold for Releasing from Downlink Overload (%)
This parameter indicates the threshold for releasing from downlink overload state.
If the value of the downlink load of the current cell is lower than this parameter, the
system is not overloaded and the load decrease measures can be stopped. If the value
of the parameter increases, it is relatively easy to reach the threshold for releasing from
downlink overload state; if the value of the parameter decreases, it is relatively hard to
reach threshold for releasing from downlink overload state.

4.2.2.7 Switch of Interactive Class/Background Class RAB->FACH for Overload
 OMC Path
-> Load Control Information -> Switch of Interactive Class/Background Class
This parameter is the switch of transferring the interactive/background RABs to the

FACH when the cell is overloaded.
If the parameter is set to be off, the system does not transfer the interactive/background
DCH/HSDPA subscribers to the FACH forcedly when the cell is overloaded; if the
parameter is set to be on, the system transfers the interactive/background DCH/HSDPA
subscribers to the FACH forcedly when the cell is overloaded.
4.2.2.8 Maximum Users of Interactive Class/Background Class RAB->FACH for

Overload
 OMC Path
-> Load Control Information -> Maximum Users of Interactive Class/Background Class
This parameter specifies the maximum number of interactive/background subscribers

that can be transferred to the FACH when the cell is overloaded. To increase the number
of interactive/background subscribers that can be transferred to the FACH at a time when
the cell is overloaded, increase the value of the parameter; to decrease the number of
interactive/background subscribers that can be transferred to the FACH at a time when
the cell is overloaded, decrease the value of the parameter.

4.2.2.9 Global Reserved Parameter 47
 OMCR Path
View -> GUI: Managed Element ->UMTS Logical Function Configuration
The bit6 of this parameter indicates the switch of forbidding AMR downgrade.
When the switch of forbidding AMR downgrade is on (GresPara47:bit6 = 1), the AMR
downgrade command triggered by congestion control is not performed until the switch is
off (GresPara47:bit6 = 0).
4.3 HSDPA Overload Control Parameters
4.3.1 HSDPA Overload Control Parameter List

HsdschOverLdThr Common Overload Threshold for HS-DSCH (%)
HsdschRecoverThr Threshold for Releasing from HS-DSCH Overload (%)
Switch of Interactive Class/Background Class RAB->FACH for

SwitchToFachSw
Overload
Maximum Users of Interactive Class/Background Class

NFach
4.3.2 Configuration of HSDPA Overload Control Parameters
4.3.2.1 Common Overload Threshold for HS-DSCH (%)
 OMC Path
-> Load Control Information -> Common Overload Threshold for HS-DSCH (%)

When HSDPA exists, if the downlink load of the current cell (namely TCP not used for
HS-PDSCH or HS-SCCH plus HS-DSCH Required Power) exceeds the value of the
parameter, the system is in the status of common overload and common overload
decrease is performed. If the value of the parameter increases, it is relatively difficult to
trigger downlink HS-DSCH common overload; if the value of the parameter decreases, it
is relatively easy to trigger downlink HS-DSCH common overload.
4.3.2.2 Threshold for Releasing from HS-DSCH Overload (%)
 OMC Path
-> Load Control Information-> Threshold for Releasing from HS-DSCH Overload (%)
When HSDPA exists, if the downlink load of the current cell (namely TCP not used for
HS-PDSCH or HS-SCCH plus HS-DSCH Required Power) is lower than the value of the
parameter, the system is not in the status of common overload and common load
decrease can be stopped. If the value of the parameter increases, it is relatively easy to
reach the threshold for releasing from HS overload state; if the value of the parameter
decreases, it is relatively hard to reach the threshold for releasing from HS overload
state.
4.3.2.3 Switch of Interactive Class/Background Class RAB->FACH for Overload
 OMC Path
-> Load Control Information-> Switch of Interactive Class/Background Class
This parameter is the switch of transferring the interactive/background RABs to the

FACH when the cell is overloaded. If the parameter is set to be off, the system does not
transfer the interactive/background DCH/HSDPA subscribers to the FACH forcedly when

the cell is overloaded; if the parameter is set to be on, the system transfers the
interactive/background DCH/HSDPA subscribers to the FACH forcedly when the cell is
overloaded.
4.3.2.4 Maximum Users of Interactive Class/Background Class RAB->FACH for

Overload
 OMC Path
-> Load Control Information -> Maximum Users of Interactive Class/Background Class
This parameter specifies the maximum number of interactive/background subscribers

that can be transferred to FACH when the cell is overloaded. To increase the number of
interactive/background subscribers that can be transferred to FACH at a time when the
cell is overloaded, increase the value of the parameter; to decrease the number of
interactive/background subscribers that can be transferred to FACH at a time when the
cell is overloaded, decrease the value of the parameter.
4.4 HSUPA Overload Control Parameters
4.4.1 HSUPA Overload Control Parameter List

NServToTotalPwr Target Non-serving E-DCH to Total E-DCH Power Ratio (%)
MaxRTWP Maximum Target Received Total Wideband Power(dB)
4.4.2 Configuration of HSUPA Overload Control Parameters
4.4.2.1 Target Non-serving E-DCH to Total E-DCH Power Ratio (%)
 OMC Path

-> Hspa Configuration In A Cell -> Target Non-serving E-DCH to Total E-DCH Power
Ratio (%)
If the value of the parameter is increased, the system sends power decrease
authorization messages to the UE in a non-service link only when the percentage of the
E-DCH received power in a non-service link of a cell over the total received power of the
E-DCH is relatively high, and it is very hard to trigger the mechanism of sending relative
grant to the UE in a non-service link.
If the value of the parameter is decreased, the system sends power decrease
authorization messages to the UE in a non-service link only when the percentage of the
E-DCH received power in a non-service link of a cell over the total received power of the
E-DCH is relatively low, and it is very easy to trigger the mechanism of sending relative
grant to the UE in a non-service link.
4.4.2.2 Maximum Target Received Total Wideband Power (dB)
 OMC Path
-> Hspa Configuration In A Cell -> Maximum Target Received Total Wideband Power
(db)
The parameter specifies the maximum target uplink interference for a certain cell, and is
an offset relative to the uplink interference when there is no load in the cell. The
parameter can also be considered as the maximum RTWP of Node B. If the value of the
parameter increases, the RTWP of Node B increases accordingly; if the value of the
parameter decreases, the RTWP of the Node B decreases accordingly.

4.5 MBMS Overload Control Parameters
For details on the parameter description of MBMS overload control, refer to the MBMS
Feature Guide.
4.6 GBR Resource Consumption Limiting Parameters
4.6.1 GBR Resource Consumption Limiting Parameter List

Used Limiting HSDPA GBR Resource Consumption
refUGbrResLimitProfile
Profile
Switch for Limiting HSDPA GBR Resource

HsGBRLimitSwi
Consumption
Guaranteed Bit Rate Level Number of HSDPA

HsGBRLevNum Services for Limiting HSDPA GBR Resource
Consumption
HsGBRLev[MAX_NUM_HS_GB Guaranteed Bit Rate Levels of HSDPA Services for

R] Limiting HSDPA GBR Resource Consumption
UEHsReqPwrUplim[MAX_NUM UE HS-DSCH Required Power Upper Limit for

_HS_GBR] Limiting HSDPA GBR Resource Consumption
4.6.2 Configuration of GBR Resource Consumption Limiting Parameters
4.6.2.1 Used Limiting HSDPA GBR Resource Consumption Profile
 OMC Path
-> Hspa Configuration In A Cell -> Used Limiting HSDPA GBR Resource Consumption
Profile
This parameter indicates the HSDPA GBR resource consumption limiting parameter
configuration profile (UGbrResLimitProfile) of the cell in use.

4.6.2.2 Switch for Limiting HSDPA GBR Resource Consumption
 OMC Path
View -> GUI: Managed Element -> UMTS Logical Function Configuration -> Service
Configuration -> Hspa Configuration -> Switch for Limiting HSDPA GBR Resource
Consumption
Switch for Limiting HSDPA GBR Resource Consumption.
Considering the cell capacity, if there is a need to limit the resource consumption of
HSDPA GBR service, the switch should be turned on.
Considering the quality of HSDPA GBR services, the switch should be turned off.
4.6.2.3 Guaranteed Bit Rate Level Number of HSDPA Services for Limiting HSDPA
GBR Resource Consumption
 OMC Path
Configuration -> Measurement Configuration -> Limiting HSDPA GBR Resource
Consumption Profile -> Limiting HSDPA GBR Resource Consumption Configuration ->
Guaranteed Bit Rate Level Number of HSDPA Services for Limiting HSDPA GBR
Resource Consumption
This parameter is set to define Guaranteed Bit Rate Level Number of HSDPA Services
for Limiting HSDPA GBR Resource Consumption.
The number of HSDPA GBR levels is based on the requirement of different HSDPA GBR
resource consumption limit for different HSDPA GBR services. Small number of levels
cannot meet the requirement, but a large number of levels are not necessary.
The greater the value of this parameter is, the larger the number of HSDPA GBR levels
is.

The smaller the value of this parameter is, the smaller the number of HSDPA GBR levels
is.
4.6.2.4 Guaranteed Bit Rate Levels of HSDPA Services for Limiting HSDPA GBR
 OMC Path
Consumption Profile -> Limiting HSDPA GBR Resource Consumption Configuration ->
Guaranteed Bit Rate Level Number of HSDPA Services for Limiting HSDPA GBR
Those parameters are set to define Guaranteed Bit Rate Levels of HSDPA Services for
Limiting HSDPA GBR Resource Consumption.
To set the GBR levels, it is needed to consider the requirement of different HSDPA GBR
resource consumption limit for different HSDPA GBR services, and the services with
similar GBR resource consumption should be allocated into the same GBR level. The
GBR levels are sorted as HsGBRLev[0] < HsGBRLev[1] < HsGBRLev[2] <…<
HsGBRLev[HsGBRLevNum-1]. Usually, the higher the GBR level is, the higher the
HS-DSCH Required Power Per UE Weight threshold (UEHsReqPwrUplim[]) is.
4.6.2.5 UE HS-DSCH Required Power Upper Limit for Limiting HSDPA GBR
 OMC Path
Consumption Profile->Limiting HSDPA GBR Resource Consumption Configuration ->
UE HS-DSCH Required Power Upper Limit for Limiting HSDPA GBR Resource
Consumption

This parameter is set to define UE HS-DSCH Required Power Upper Limit for Limiting
HSDPA GBR Resource Consumption.
It is needed to consider the requirement of different HSDPA GBR resource consumption

limit for different HSDPA GBR services.
The services with similar GBR resource consumption should be allocated into the same
GBR level. And the GBR levels are sorted as HsGBRLev[0] < HsGBRLev[1] <
HsGBRLev[2] <…< HsGBRLev[HsGBRLevNum-1]. Usually, the higher the GBR level
is, the higher the HS-DSCH Required Power Per UE Weight threshold
(UEHsReqPwrUplim[]) is. So usually UEHsReqPwrUplim[0] <= UEHsReqPwrUplim[1] <=
UEHsReqPwrUplim[2] <=…<= UEHsReqPwrUplim[HsGBRLevNum-1].
5 Counters and Alarms
5.1 Counter List

Counter No. Description
C310524810 Number of call drop by load control, Conversation class
C310524811 Number of call drop by load control, Interactive class
C310524812 Number of call drop by load control, Background class
C310524813 Number of call drop by load control, Streaming class
C310524814 Number of rate decreased by load control, Conversation
C310524815 Number of rate decreased by load control, Interactive class
C310524816 Number of rate decreased by load control, Background class
C310524817 Number of rate decreased by load control, Streaming class
C310525625 Number of forced handover by load control, Conversation class
C310525626 Number of forced handover by load control, Interactive class
C310525627 Number of forced handover by load control, Background class
C310525628 Number of forced handover by load control, Streaming class
C310525629 Number of delete RL by load control
C310525633 Number of services be forced convert to FACH by overload control, I


traffic
Number of services be forced convert to FACH by overload control, B

C310525634
traffic
C310525635 Number of services GBR decreased by overload control
Number of cell downlink load state change from normal to R99

C310525636
common overload
Number of cell downlink load state change from normal to R99

C310525637
serious overload
Number of cell downlink load state change from R99 common

C310525638
overload to R99 serious overload
Number of cell downlink load state change from R99 serious overload
C310525639
to R99 common overload

C310525640
overload to normal
C310525641
to normal
Number of cell uplink load state change from normal to R99 common
C310525642
overload
Number of cell uplink load state change from normal to R99 serious
C310525643
overload
Number of cell uplink load state change from R99 common overload
C310525644
to R99 serious overload
Number of cell uplink load state change from R99 serious overload to
C310525645
R99 common overload
Number of cell uplink load state change from R99 common overload
C310525646
to normal
Number of cell uplink load state change from R99 serious overload to
C310525647
normal
Number of cell downlink load state change from normal to HSDPA

C310525648
overload

C310525649
overload to HSDPA overload
C310525650
to HSDPA overload
C310525651 Number of cell downlink load state change from HSDPA overload to


R99 common overload
Number of cell downlink load state change from HSDPA overload to

C310525652
R99 serious overload
Number of cell downlink load state change from HSDPA overload to

C310525653
normal
C310525654 Total time of R99 downlink common overload
C310525655 Total time of R99 downlink serious overload
C310525656 Maximum time of R99 downlink common overload
C310525657 Maximum time of R99 downlink serious overload
C310525658 Total time of R99 uplink common overload
C310525659 Total time of R99 uplink serious overload
C310525660 Maximum time of R99 uplink common overload
C310525661 Maximum time of R99 uplink serious overload
C310525662 Total time of downlink HSDPA common overload
C310525663 Maximum time of downlink HSDPA common overload
5.2 Alarm List
This feature has no relative alarm.
6 Glossary
C
CAC Call Admission Control
DCH Dedicated Channel
DL Downlink (Forward link)
DPCCH Dedicated Physical Control Channel

DPCH Dedicated Physical Channel
DPDCH Dedicated Physical Data Channel
E-AGCH E-DCH Absolute Grant Channel
E-RGCH E-DCH Relative Grant Channel
E-HICH E-DCH Hybrid ARQ Indicator Channel
FACH Forward Access Channel
HS-DPCCH High Speed Dedicated Physical Control Channel
HS-DSCH High Speed Downlink Shared Channel
HS-PDSCH High Speed Physical Downlink Shared Channel
HS-SCCH High Speed Shared Control Channel
HSDPA High Speed Downlink Packet Access
HSUPA High Speed Uplink Packet Access
I/B Interactive/Background
LC Load Control
MBMS Multimedia Broadcast Multicast Service

RACH Random Access Channel
RNC Radio Network Controller
RTWP Received Total Wide Band Power
SIR Signal to Interference Ratio
TCP Transmitted Carrier Power
UE User Equipment
WCDMA Wideband Code Division Multiple Access

Overload Control Feature Guide

Uploaded by

Document Information

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

Overload Control Feature Guide

Uploaded by

Copyright:

Available Formats

Overload Control Feature

Overload Control Feature Guide

1. Modified the description of DC-HSDPA

© 2013 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

3 Technical Descriptions ..................................................................................... 8

4 Parameters and Configurations ..................................................................... 42

ZTE Confidential Proprietary 2

4.2 R99 Overload Control Parameters ..................................................................... 50

5 Counters and Alarms ...................................................................................... 62

ZTE Confidential Proprietary 3

Figure 3-1 R99 overload control flowchart..........................................................................10

ZTE Confidential Proprietary 4

Attribute: [Mandatory + Optional]

Mutual exclusion: [None]

 R99 overload control

 HSDPA overload control

 HSUPA overload control

ZTE Confidential Proprietary 5

 MBMS overload control

 Common overload control

 Serious overload control

 Uplink overload control

 Downlink overload control

2.1 ZWF21-04-002 Overload Control

 Decreasing the service rate of R99 subscribers

ZTE Confidential Proprietary 6

 Forcedly handing over subscribers to an inter-frequency cell or an inter-RAT cell

 Forcedly transferring the interactive subscribers or background subscribers to the

 Decreasing GBR of C/S traffic through the GBR renegotiation

 Forcedly dropping calls

2.2 ZWF23-04-002 Overload Control for HSDPA Service

 Decreasing the service rate of R99 subscribers

 Forcedly handing over DCH and HSDPA subscribers to an inter-frequency cell or

 Forcedly transferring the interactive subscribers or background subscribers to the

 Decreasing GBR of C/S traffic through the GBR renegotiation

 Forcedly dropping calls of low-priority services (DCH and HSDPA)

ZTE Confidential Proprietary 7

2.3 ZWF25-04-002 Overload Control for HSUPA Service

 Decreasing the service rate of R99 subscribers

 Forcedly handing over DCH and HSUPA subscribers to an inter-frequency cell or

 Decreasing GBR of C/S traffic through the GBR renegotiation

 Forcedly dropping low-priority services (DCH and HSDPA)

3.1 R99 Overload Control

 Decreasing the service rate of R99 subscribers

ZTE Confidential Proprietary 8

 Forcedly handing over to inter-frequency or inter-RAT neighboring cell

 Transferring services of I/B subscribers to the RACH/FACH channels

 Decreasing GBR (GBR renegotiation)

 Forcedly releasing the service

3.1.1 R99 Overload Control Flow

ZTE Confidential Proprietary 9

Figure 3-1 R99 overload control flowchart

The status of The status of The status of common

To perform serious To perform common

3.1.2 R99 Overload Control States

3.1.2.1 Classification of R99 Overload Control States

ZTE Confidential Proprietary 10

Figure 3-2 R99 overload control threshold

The Load of Cell

The Threshold of Common Overload

The Threshold for Releasing from

3.1.2.2 Conversion between R99 Overload Control States

ZTE Confidential Proprietary 11