U DEI 0604 ZTE UTMS Overload Control Feature Description V3.00 200903

Overload Control
WCDMA RAN
Feature Description
Overload Control Feature Description

Versio
n
Date
Author
Approved By
V2.5
2009-1-20
KeYaZhu
Cui Lili / Zheng

Dan
V3.0
2009-2-27
KeYaZhu
Cui Lili / Zheng

Dan
Remarks
2008 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 of the document is
subjected to change without notice.
ZTE Confidential Proprietary
TABLE OF CONTENTS
1
Functions and Attributes ...................................................................................... 1
2
2.1
2.1.1
2.1.2
2.1.3
Overview ................................................................................................................ 1
Overview of the Functions....................................................................................... 1
ZWF21-04-002 R99 Load Control Function ............................................................. 2
ZWF23-04-002 HSDPA Load Control ...................................................................... 2
ZWF25-04-002 HSUPA Load Control ...................................................................... 3
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.4
Technical Description ........................................................................................... 3

R99 Load Control .................................................................................................... 3
R99 Load Control Flow............................................................................................ 4
R99 Load Control States ......................................................................................... 5
Load Decrease Methods for R99 Load Control ........................................................ 6
Load Decrease Methods for R99 Common Overload............................................... 9
Load Decrease Method for R99 Serious Overload ................................................ 10
R99 Algorithm Related Measurement .................................................................... 11
HSDPA Load Control ............................................................................................ 11
HSDPA Load Control Flow .................................................................................... 12
Decision Methods for Conversion between HSDPA Load Control States ............... 13
Load Decrease Methods for HSDPA Load Control................................................. 15
HSDPA Load Decrease Flow................................................................................. 17
HSDPA Algorithm Related Measurement .............................................................. 19
HSUPA Load Control ............................................................................................ 19
HSUPA Load Control Flow .................................................................................... 19
Decision Methods for Conversion between HSUPA Load Control States ............... 20
Load Decrease Methods for HSUPA Load Control................................................. 22
Load Decrease Methods for HUSPA Common Overload ....................................... 23
Load Decrease Methods for HSUPA Serious Overload ......................................... 23
HSUPA Algorithm Related Measurement .............................................................. 24
MBMS Load Control .............................................................................................. 24
4
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.3
4.3.1
4.3.2
4.4
4.4.1
4.4.2
4.5
Configuration of Parameters............................................................................... 24
Common Parameters ............................................................................................ 24
Common Parameter List ....................................................................................... 24
Common Parameter Configuration ........................................................................ 25
R99 Load Control Parameters ............................................................................... 34
R99 Load Control Parameter List .......................................................................... 34
Configuration of R99 Load Control Parameters ..................................................... 35
HSDPA Load Control Parameters ......................................................................... 40
HSDPA Load Control Parameter List ..................................................................... 40
Configuration of HSDPA Load Control Parameters................................................ 40
HSUPA Load Control Parameters ......................................................................... 43
HSUPA Load Control Parameter List ..................................................................... 43
Configuration of HSUPA Load Control Parameters................................................ 43
MBMS Load Control Parameters ........................................................................... 44
5
5.1
5.1.1
5.1.2
5.1.3
5.1.4
Counter And Alarm .............................................................................................. 45

Counter List........................................................................................................... 45
Number of Call Drop by Load Control, Conversation Class.................................... 45
Number of Call Drop by Load Control, Interactive Class ........................................ 45
Number of Call Drop by Load Control, Background Class...................................... 45
Number of Call Drop by Load Control, Streaming Class ........................................ 45
II
5.1.5
5.1.6
5.1.7
5.1.8
5.1.9
5.1.10
5.1.11
5.2
Number of Rate Decreased by Load Control, Conversation Class ......................... 45

Number of Rate Decreased by Load Control, Interactive Class ............................. 45
Number of Rate Decreased by Load Control, Background Class ........................... 46
Number of Rate Decreased by Load Control, Streaming Class.............................. 46
Sum of Control Time of Load Control .................................................................... 46
Times of Load Control ........................................................................................... 46
Noise Floor of the System ..................................................................................... 46
Alarm List .............................................................................................................. 46
Glossary ............................................................................................................... 46
III
Figures and Tables

Figure 1
R99 load control flowchart ......................................................................................... 4
Figure 2
R99 load control threshold......................................................................................... 5
Figure 3
Conversion between R99 load control states ............................................................. 6
Figure 4
R99 common overload control flowchart ................................................................. 10
Figure 5
R99 serious overload control flowchart .................................................................... 11
Figure 6
Load control flowchart for the HSDPA cells ............................................................. 13
Figure 7
Conversion between HSDPA load control states ..................................................... 14
Figure 8
HSDPA overload control flowchart .......................................................................... 19
Figure 9
HSUPA load control flowchart ................................................................................. 20
Figure 10
Classification of HSUPA load control states ............................................................ 21
Figure 11
Conversion between HSUPA load control states ..................................................... 21
IV
Functions and Attributes

System version: [RNC V3.07.300, Node B V4.00.100, OMMR V3.17.300, OMMB
V4.00.100]
Attributes: basic functions + optional functions
NEs involved:
UE
Node B
RNC
MSCS
MGW
SGSN
GGSN
HLR
Note:
*-: NEs not involved
*: NEs involved:
Dependency: [None]
Mutual exclusive functions: [None]
Remarks: [None]
Overview
2.1
Overview of the Functions

The load control is performed to control the load on individual cells. It takes appropriate
measures to recover normal load as soon as possible and thus stabilizes the system
when overload occurs to the system. Here overload means the uplink/downlink load on
a cell exceeds the overload threshold set during network planning. In such a case, the
system is in an unstable state, with its capacity so 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 so close to the limit and
requires prompt recovery.
By functional systems, the load control can be classified into the following types:
R99 load control
HSDPA load control
HSUPA load control
MBMS load control
By severity of overload, the load control can be classified into the following two types:
Common overload control
Serious overload control
By direction of uplink/downlink, load control can be classified into the following two
types:
2.1.1
Uplink load control
Downlink load control
ZWF21-04-002 R99 Load Control Function

The Node B sends RTWP and TCP messages to the RNC periodically in the common
measurement report. The RNC compares the load threshold with RTWP and TCP. The
RNC implements load control if RTWP or TCP exceeds the threshold. Here, the uplink
load threshold is a absolute value(dBm), it is equal to the sum of background
noise(dBm) and the relative value of uplink load control threshold(dB).
There are two types of overload: serious overload and common overload. According to
the overload type, the RNC system should take actions accordingly. 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 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
Forcedly dropping calls
When overloading occurs, the system selects services or UEs through the overload
control priority and then takes above actions for these services. In this way, the system
can maintain the stability for services of high-priority subscribers. .
2.1.2
ZWF23-04-002 HSDPA Load Control

The load control of the HSDPA is based on the transmit power of a cell. The load
control function is triggered when the downlink power reaches a certain value (which is
configurable through the OMCR).During the implementation of load control, the HSDPA
reduces the payload of a cell according to the difference of subscribers. The HSDPA
takes the following measures:
2.1.3
Decreasing the service rate of R99 subscribers
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).
ZWF25-04-002 HSUPA Load Control

When overloading occurs in the E-DCH cell, the system can take the following load
control measures:
Decreasing the service rate of R99 subscribers
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)
Technical Description
3.1
R99 Load 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 load control threshold. If the RTWP or TCP exceeds the threshold, it
means occurrence of overload and the load control process is carried out. 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:
3.1.1
Decreasing the service rate of R99 subscribers;
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;
Forcedly releasing the service.
R99 Load Control Flow

The figure below shows the overall R99 load control flowchart. The load control is
classified into serious overload control and common overload control depending on
different overload states. The load control is triggered by 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 load control with the methods described in section 3.1.2, and
performs an appropriate process depending on the decision result. In the state of
common overload, the common overload control is carried out; in the sate of serious
overload, the serious overload control is carried out.
The overload control in all states is performed in the direction of uplink and downlink
respectively.
Figure 1
R99 load control flowchart
3.1.2
R99 Load Control States
3.1.2.1
Classification of R99 Load Control States

Load control has three thresholds, which are serious overload threshold, common
overload threshold, and overload recovery threshold. Relations among the three
thresholds are: serious overload threshold (uplink: UlSeriousOverLd, downlink:
DlSeriousOverLd) > common overload threshold (uplink: UlOverLd, downlink:
DlOverLd) > overload recovery threshold (uplink: UlAlrmLd, downlink: DlAlrmLd). See
Figure 2. The overload thresholds are set in the direction of uplink and downlink
respectively.
Figure 2
R99 load control threshold
Depending on the load on a cell, load control is performed in three states: normal state,
common overload state, and serious overload state.
3.1.2.2
Conversion between R99 Load Control States

With the change of load on a cell, the three states of load control are inter-convertible in
a relationship as shown in Figure 3.
Figure 3
Conversion between R99 load control states
Note: When a cell is set up, the cell load is in the normal state.
3.1.3
In the normal state, when the load is found over the common overload threshold
but below the serious overload threshold, the cell enters the common overload
state.
In the common overload state, when load control helps decrease the load below the
overload recovery threshold, the cell returns to the normal state.
In the normal state, when the load is found over the serious overload threshold, the
cell enters the serious overload state.
In the serious overload state, when load control helps decrease the load below the
In the common overload state, when the load is found over the serious overload
threshold, the cell enters the serious overload state.
serious overload threshold but above the common overload threshold, the cell
enters the common overload state.
These mutual conversions between load control states are implemented in the
direction of uplink and downlink respectively.
Load Decrease Methods for R99 Load Control

The load decrease measures available with load 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, and forced drop of service. The following outlines these load
decrease methods:
Downgrade
Forced handover
Forced transfer of DCH to FACH
Call drop (service disconnection)
The priorities of the methods in descending order: Downgrade -> forced handover ->
forced transfer to RACH/FACH -> call drop
These load control methods are performed in the direction of uplink and downlink
respectively. Whether a load control method is used can be configured in the
background.
3.1.3.1
Downgrade
Downgrade includes AMR service downgrade and PS service downgrade. The AMR
downgrade 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
Description. For a subscriber with concurrent DCH service in addition to AMR service,
downgrade is applicable only to the PS service rather than the AMR service except for
concurrence of additional HS services. The stream services of the PS domain can be
decreased to the Max(the lowest level of DRBC, Guarantee Bit Rate); the I/B service
has no Guarantee Bit Rate (GBR), with 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 Description.
The rate of a service can be decreased by many levels at a time. The rate can be
divided into many levels according to the rate levels of DRBC. The maximum rate
levels (UlDnMaxStg in the uplink and DlDnMaxStg in the downlink) that can be
decreased at a time is configurable at the daemon.
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 load control
priorities in descending order, decrease speed for the subscriber with the lowest priority.
The system does not select a service that is already at the lowest rate. The load control
priority adopts the settings of application priority and is based on basic priority, bearer
type, and real-time rate of a service. Since the load control priority is associated with
the current service rate, it is necessary to remap the load control priority against the
new rate after the service rate is decreased. The Traffic Rate in the table indicates the
current allocated rate for the DCH. It is the GBR for the S traffic of HSPA, and the
signaling rate for the I/B traffic of HSPA.
For details on the rules of mapping between the load control priority and basic priority,
bearer type, and service real-time rate, refer to ZTE UMTS QoS Feature Description.
The parameter MaxNumUeOfDecRat controls the number of subscribers whose line

rates can be decreased in the uplink and downlink at a time.
The load control can trigger the downgrade 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 for inter-frequency handover or inter-RAT handover.
For details, refer to the ZTE UMTS Handover Control Feature Description.
Measurement is not applied to the forced handover of load 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, the UE cannot
be deleted. If the deleted link is not in the best cell, the link deletion does not seriously
affect the service quality of 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 load control priority,
and then processes the subscriber with the lowest priority as needed. The load control
priority of a subscriber is determined by the service with the highest load control priority
among all his services.
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 is controlled by the parameter DlMaxForHoNum.
The maximum number of downlink radio links that can be deleted at a time is controlled
by the parameter DlMaxDelRlNum.
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 overload. (Do not
perform this operation unless all services of the subscriber are of the I/B category.)
To perform forced transfer to FACH, the system should first sort all interactive and
background subscribers by load control priority, 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 load
control priorities, RNC should select the highest load control priority among all the
services of the subscriber.
bearer type, and service real-time rate, refer to ZTE UMTS QoS Feature
Description.The maximum number of subscribers allowed in a transfer is controlled by
the parameter NFach.
3.1.3.4
Call Drop
Forced service drop is a measure taken to release the RAB with low load control priority
when the above-mentioned methods fail to produce any effect or expected effect.
Call drop triggered by load 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 load control
priority, and then start with the subscriber with the lowest priority as needed.
The maximum number of subscribers allowed in a forced uplink call drop is controlled
by the parameter UlMaxDrpUrNum; the maximum number of subscribers allowed in a
forced downlink call drop is controlled by the parameter DlMaxDrpUrNum.
3.1.4
Load Decrease Methods for R99 Common Overload

When the system load rises over the common overload threshold, the system enters the
common overload state. It is necessary to take appropriate load decrease measures.
The load decrease action continues until the system load drops below the overload
recovery threshold.
The load decrease for the common overload goes through the following steps:
1.
If the downgrade switch is on (the uplink downgrade switch is UlDecRateSw; the

downlink downgrade switch is DlDecRateSw) 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 downgrade, refer
to " ".
2.
If the forced handover switch is on (the uplink handover switch is

UlForceHandoffSw; the downlink handover switch is DlForceHandoffSw) 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.
If the switch of forced transfer from DCH to FACH (SwitchToFach) 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 forced call drop switch (UlDropSw for the uplink or DlDropSw for the downlink)
is open, and the cell contains some subscribers suitable 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.4 Call Drop".
The figure below shows the common overload control flowchart.
Find the methods of load decreasing

is supported by each UE in the cell
Switch for Downgrade is open(UlDecRateSw=1 for

uplink; DlDecRateSw=1 for downlink) ?
Yes
Downgrade
No
Switch for Forced Handover is open
(UlForceHandoffSw=1 for uplink;
DlForceHandoffSw=1 for downlink) ?
Yes
Forced
Handover
No
Yes
Transfer DCH
to FACH of
I/B traffic
Switch for Transfer DCH to FACH of I/B traffic is

open (SwitchToFach=1 ) ?
Yes
No
Switch for Forced Call Drop is open(UlDropSw=1 for
uplink; DlDropSw=1 forNo
downlink) ?
Forced Call
Drop
End
Figure 4
3.1.5
R99 common overload control flowchart
Load Decrease Method for R99 Serious Overload

When the system load rises over the serious overload threshold, the system enters the
serious overload state. 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 common overload
threshold, the system enters the common overload state, and performs the downgrade
and forced handover for the common overload.
The figure below shows the serious overload control flowchart:
10
Figure 5
R99 serious overload control flowchart
3.1.6
R99 Algorithm Related Measurement
3.1.6.1
Node B Common Measurement

The Node B common measurement information required for R99 load control includes:
Received Total Wide Band Power (RTWP)
Transmitted Carried Power (TCP)
Node B needs to report the measurement results to the RNC periodically. The Node B
reports RTWP and TCP at the interval of 2s. Load control judges whether the load
control trigger condition is satisfied. If yes, the load control process is started.
3.2
HSDPA Load Control

As the load control is performed in the uplink and downlink separately, and HSDPA
involves downlink alone, this section describes only the policies for downlink load
control in the cells supporting the HSDPA.
In a cell supporting HSDPA, the load control policies are performed in two conditions:
11
1.
NoHsPower>= R99 common overload threshold (DlOverLd), or NoHsPower>= R99

serious overload threshold (DlSeriousOverLd), 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 (DlOverLd), enable HS

load decrease or R99 load decrease according to the setting of 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 downgrade action targets at the
services carried over the DPCH channel; forced handover targets at subscribers of the
DPCH physical channel; call drop targets at services over the DCH channel). The load
decrease policy is similar to "3.1.3 Load Decrease Methods for R99 Load Control". If
the algorithm of load decreasing(AglLdDec) is set to HS load decrease algorithm, the
load decrease action targets at DCH and HS-DSCH subscribers. The load decrease
actions and priorities based subscribers selection policies are the same as those
described in "3.2.3 Load Decrease Methods for HSDPA Load Control".
In the case of NoHsPower>= R99 serious overload threshold (DlSeriousOverLd), the
call drop action targets at the DCH service at first. And than 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.
2.
When there are HS subscribers and NoHsPower +
Hs Re quiredPowe r >= HS
spi
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 Load Control Flow

Figure 6 shows the load control flowchart of the HSDPA cell. The load control statuses
include R99 common overload control, R99 serious overload control, and HS overload
control. The load 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 describes only the downlink load control.
The uplink load control is the same as that for the R99 cells. Hence, the uplink load
control is omitted here.
12
Figure 6
Load control flowchart for the HSDPA cells
3.2.2
Decision Methods for Conversion between HSDPA Load Control

States
3.2.2.1
Classification of HSDPA Load Control States

For a cell supporting the HSDPA, two thresholds are set for the HS load control (the
R99 thresholds are omitted here):
HS-DSCH common overload threshold (HsdsOverLdThr)
HS-DSCH overload recovery threshold (HsdsRecoverThr)
A comparison between the current load and each threshold can determine four states:
normal state, R99 common overload state, R99 serious overload state, and HS
overload state.
13
3.2.2.2
Conversion between HSDPA Load Control States

With the change of load on a cell, the four states of overload described in figure 6 are
inter-convertible in a relationship as shown below, where R99 overload states contains
R99 common overload state and R99 serious overload state:
Figure 7
Conversion between HSDPA load control states
Process description: When a cell is set up, the cell load is in the normal state.
1.
In the normal state, when NoHsPower is found below the R99 common overload
threshold and NoHsPower+
Hs Re quiredPowe r exceeds the HS overload
spi
threshold, the cell enters the HS overload state.

2.
In the HS overload state, when NoHsPower is found below the R99 overload
recovery threshold and NoHsPower+
Hs Re quiredPowe r decreases below the
spi
HS overload recovery threshold, the cell returns to the normal state.
14
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 R99
common overload state.
4.
In the normal state, when NoHsPower is found over the R99 serious overload
threshold, the cell enters the R99 serious overload state.
5.
In the R99 common overload state, when NoHsPower is found over the R99
serious overload threshold, the cell enters the R99 serious overload state.
6.
In the R99 serious overload state, when NoHsPower is found down below the R99
common overload threshold but above the R99 overload recovery threshold, the
cell enters the R99 common overload state.
7.
In the R99 common or serious overload state, when NoHsPower is found down
below
the
R99
overload
recovery
threshold
and
NoHsPower+
Hs Re quiredPowe r is below the HS overload recovery
spi
threshold, the cell returns to the normal state.

8.
In the R99 common or serious overload statewhen NoHspower is found over the
threshold of R99 overload recovery, and NoHsPower+
Hs Re quiredPowe r
spi
over the HS overload threshold, the cell enters the HS overload state.
3.2.3
Load Decrease Methods for HSDPA Load Control

R99 overload and HS overload occur in cells supporting HSDPA. In the case of R99
common overload, there are two load decrease methods correspond to the R99 load
decrease method and HSDPA load decrease method. The R99 load decrease method is
described in section 3.1.4, so it is not need to describe again.
This chapter focuses on HS overload status and load decrease actions. The HS load
decrease can be performed with the following methods:
Downgrade
Forced handover
Forced transfer to FACH
Call drop
The priorities of the above four load decrease methods can be sorted as downgrade ->
forced handover-> forced transfer to FACH ->call drop
You can configure switches to control the use of the above load control methods. For
details on the switch parameters, refer to 3.2.4. The following describes the differences
between above methods and the methods applied in R99 cells.
3.2.3.1
Downgrade
Since the RNC cannot control the rate of HSDPA services, the downgrade for the HS
load decrease actually means to decrease the rate of DCH services as well, and the
downgrade method is the same as that for the R99 cells.
15
3.2.3.2
Forced Handover
Forced handover is to hand over the subscribers 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
applied only 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 load control priorities, and then
performs the forced switchover for the subscriber with the lowest priority. When there
are multiple concurrent services, the system selects the service with the highest load
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 service cell, and then make
selection by the application priority of the load 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 load control should be followed). If there are concurrent
services on the DCH, the load control priority should be determined by the service with
the highest priority.
The load 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 the assured rate; for I/B service, the real-time rate
is 3.4 kbit/s signaling rate.
DlMaxForHoNum (the maximum number of subscribers involved in a forced handover)
and DlMaxDelRlNum (maximum number of links deleted at a time) are the same as the
parameters adopted by R99 downlink load control and can be configured at the daemon.
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 load control priority, and then start with the subscriber with
the lowest priority as needed. The load control priority of a subscriber is determined by
the service with the highest load control priority among all his services.
16
For details on the factors related to load control priorities and mapping methods, refer to
ZTE UMTS QoS Feature Description.
The maximum number of subscribers in a forced transfer (NFach) is the same as the
parameter used in R99 load control, and can be configured through the daemon.
3.2.3.4
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 HSDSCH subscribers also occupies certain power.
Call drop triggered by load 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 load control
priority, and then start with the subscriber with the lowest priority as needed.
Load control priority is mapped by basic priority (BP), bearer type, and subscribers realtime rate. For stream services carried over the HS-DSCH channel, the real-time rate of
the stream service is the assured rate; for I/B service, the real-time bit rate is 3.4 k bit
rate.
The maximum number of subscribers in a call drop event (DlMaxDrpUrNum) is the
same as the parameter used in R99 load control, and can be configured through the
daemon.
3.2.4
HSDPA Load Decrease Flow

When the system load rises over the HS overload threshold, the system enters the HS
overload state, making it necessary to take appropriate load decrease measures. The
load decrease action continues until the system load drops below the HS overload
recovery threshold. 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 downgrade switch is on (DlDecRateSw) 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 downgrade,
refer to " ".
2.
If the forced handover switch (DlForceHandoffSw) 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.2.3.2 Forced Handover".
3.
If the switch of deleting macro diversity link (DlForceHandoffSw) is on and the
cell contains macro diversity links, sort the subscribers according to the priorities in
ascending order and then delete macro diversity links for these subscribers. For details
on forced handover, refer to "3.2.3.2 Forced Handover".
17
4.
If the switch of forced transfer from DCH to FACH (SwitchToFach) 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 transfer to CELL_FACH method, refer
to "3.2.3.3 Forced Transfer to FACH".
5.
If the forced call drop switch (DlDropSw) 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 call drop, refer to "3.2.3.4 Call Drop".
The figure below shows the HS overload control flowchart:
Strat
Switch for Downgrade

is open
(DlDecRateSw=1)?
No
Yes
Exist traffic can
be downgrade?
Yes
Downgrade
No
Switch for Deleting RL of
Macro Diversity is open
(DlForceHandoffSw=1) ?
No
Yes
Exist RL can be
deleted?
Yes
Deleting RL of
Macro Diversity
No
Switch for Forced
Handover is open
(DlForceHandoffSw=1)
&& exist cell can be
handover to ?
No
Yes
Forced Handover
can be run?
Yes
Forced Handover
No
Switch for Transfer DCH

to FACH of I/B traffic is
open(SwitchToFach=1)?
No
Yes
Can be converted
to FACH?
Yes
Transfer DCH to
FACH of I/B
traffic
No
Switch for Call Drop

is open
(DlDropSw=1)?
No
Yes
Call Drop
End
18
Figure 8
HSDPA overload control flowchart
3.2.5
HSDPA Algorithm Related Measurement
3.2.5.1

The Node B common measurement information required for HSDPA load control
includes:
HS-DSCH Required Power(HsRequiredPower)
Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH
transmission(NoHsPower)
Node B reports the measurement results to the RNC at the interval of 2s. Load control
judges whether the load control trigger condition is satisfied. If yes, the load control
process is started.
3.3
HSUPA Load 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 load 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
receive power of the non-service link over the total E-DCH receive power. The
percentage of the receive power over the total receive power of the E-DCH is
NServToTotalPwr. Node B keeps NServToTotalPwr to control the scheduling of the EDCH so that the percentage of the power of the E-DCH subscriber in the non-service
link of the cell over the 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.
3.3.1
HSUPA Load Control Flow

The figure below shows the overall load control flowchart. The load control is classified
into serious overload control and common overload control depending on different
overload states. The load control is triggered by 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 load control with the methods described in section 3.3.2, and
19
performs an appropriate process depending on the decision result. In the state of

common overload, the common overload control is carried out; in the sate of serious
overload, the serious overload control is carried out.
The load control described in this section is specific to the uplink direction.
Figure 9
HSUPA load control flowchart
3.3.2
Decision Methods for Conversion between HSUPA Load Control

States
3.3.2.1
Classification of HSUPA Load Control States

The HSUPA load control has three thresholds, which are serious overload
threshold(UlSeriousOverLd*), common overload threshold(UlOverLd*), and overload
recovery threshold(UlAlrmLd*). The relationship between these three thresholds and the
maximum target RTWP(MaxRTWP*) is: UlSeriousOverLd* > UlOverLd* >
MaxRTWP* > UlAlrmLd*, as shown in the following diagram, where the relationship is
specific to the uplink direction. Where, UlSeriousOverLd*(dBm)=cell background
noise(dBm)+ UlSeriousOverLd(dB); UlOverLd*(dBm)= cell background noise(dBm)+
UlOverLd(dB); UlAlrmLd*(dBm) = cell background noise(dBm)+ UlAlrmLd(dB);
MaxRTWP*(dBm)= cell background noise(dBm)+ MaxRTWP(dB). How to get cell
background noise refer to ZTE UMTS Admission Control Feature Description.
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 that for the DCH, while the common overload threshold in the E-DCH cells is
configured higher than that in the DCH cells.
20
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 load recovering
The Threshold of Overload
Recovery(UlAlrmLd*)
Figure 10 Classification of HSUPA load control states
Depending on the load on a cell, load control is performed in three states: normal state,
common overload state, and serious overload state.
3.3.2.2
Conversion between HSUPA Load Control States

With the change of load on a cell, the three states of load control are inter-convertible in
a relationship as shown below:
Figure 11 Conversion between HSUPA load control states
21
Note: When a cell is set up, the cell load is in the normal state.
3.3.3
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 common overload
state.
2.
In the common overload state, when load control helps decrease the load below the
3.
In the normal state, when the load is found over the serious overload threshold, the
cell enters the serious overload state.
4.
5.
In the common overload state, when the load is found over the serious overload
threshold, the cell enters the serious overload state.
6.
serious overload threshold but above the common overload threshold, the cell
enters the common overload state.
7.
These mutual conversions between load control states are implemented in the
direction of uplink.
Load Decrease Methods for HSUPA Load Control

In the overload state, the Node B has decreased, through scheduling, the rate of nonGBR services on the E-DCH to zero and the rate of GBR services on the E-DCH down
to the guaranteed bit rate(GBR). 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 load control.
The RNC can take the load control measures as follows:
Downgrade
Forced handover
Call drop
The priorities of the above three downgrade methods can be sorted as downgrade ->
forced handover-> forced call drop
3.3.3.1
Downgrade
Downgrade is applied only to the DCH services, including PS service and CS service, in
the same way as for the R99 cells.
22
3.3.3.2
Forced Handover
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.
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.
3.3.3.3
Call Drop
Forced call drop is applied to all the subscribers in the overloaded cell, who might be
either DCH subscriber or E-DCH subscriber. The specific steps are the same as those
for the R99 cells.
3.3.4
Load Decrease Methods for HUSPA Common Overload

When the system load rises over the common overload threshold, the system enters the
common overload state. It is necessary to take appropriate load decrease measures.
The load decrease action continues until the system load drops below the overload
recovery threshold.
The load decrease for the common overload goes through the following steps:
3.3.5
1.
If the uplink DCH downgrade switch (UlDecRateSw) is on and there are DCH
services to be decreased in the uplink, the system implements the uplink DCH
downgrade flow. For more details, refer to "
".
2.
If the uplink forced handover switch (UlForceHandoffSw) is on and there is an interchannel cell with the same coverage), the system implements forced handover.
For more details, refer to "3.3.3.2 Forced Handover".
3.
If the uplink forced call drop switch (UlDropSw) is on, the system implements the
forced call drop. This method is the same as that for the R99, and the DCH and EDCH subscribers are considered.For more details, refer to "3.3.3.3 Call Drop".
Load Decrease Methods for HSUPA Serious Overload

When the system load rises over the serious overload threshold, the system enters the
serious overload state. For quick decrease of cell load, the system should delete the UE
with excessive SIR ERROR, and then 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 common
overload threshold, the system enters the common overload state and performs the
common overload control.
23
3.3.6
HSUPA Algorithm Related Measurement
3.3.6.1

The Node B common measurement information required for HSUPA load control
includes:
Received Total Wide Band Power (RTWP)
Node B reports the measurement results to the RNC at the interval of 2s. Load control
judges whether the load control trigger condition is satisfied. If yes, the load control
process is started.
3.4
MBMS Load Control

For details on the technical description on MBMS load control, refer to MBMS Technical
Attribute Description.
Configuration of Parameters
4.1
Common Parameters
4.1.1
Common Parameter List
24
Abbreviated name
Parameter name
MaxNumUeOfDecRat
Maximum Number of UE Decreasing Rate When

Congestion
AglLdDec
Algorithm of Load Decreasing
UlDecRateSw
Uplink Switch for Shielding Rate Reduction
UlForceHandoffSw
Uplink Switch for Shielding Forced Handover
UlDropSw
Uplink Switch for Shielding Forced Drop
UlDnMaxStg
Maximum Number of Degraded Uplink Load Steps

Every Time
UlMaxForHoNum
Maximum Number of Uplink Forced Handover Users

Every Time
UlMaxDrpUrNum
Maximum Number of Uplink Forced Drop Users Every

Time
DlDecRateSw
Downlink Switch for Shielding Rate Reduction
DlForceHandoffSw
Downlink Switch for Shielding Forced Handover
DlDropSw
Downlink Switch for Shielding Forced Drop
DlDnMaxStg
Maximum Number of Degraded Downlink Load Steps

Every Time
DlMaxDelRlNum
Maximum Number of Deleted Downlink Radio Links

Every Time
DlMaxForHoNum
Maximum Number of Downlink Forced Handover

Users Every Time
DlMaxDrpUrNum
Maximum Number of Downlink Forced Drop Users

Every Time
4.1.2
Common Parameter Configuration
4.1.2.1
Maximum Number of UE Decreasing Rate When Congestion
Parameter description
Parameter
name
Maximum Number of UE Decreasing Rate When Congestion
Abbreviated
name
MaxNumUeOfDecRat
Description
This parameter indicates the maximum number of services whose

rates will be decreased each time when congestion takes place.
Range and
Step
[1, 100]
Unit
N/A
Default Value
(note)
OMC Path
Path: View->Configuration Management->RNC NE->RNC Radio Resource

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Load
Control Relationship ->Maximum Number of UE Decreasing Rate When Congestion
Parameter configuration
The parameter is used when load decrease is 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 downgrade also increases accordingly, and released
resources also increase; if the system reduces the value of the parameter, the number
of DCH subscribers ready for downgrade also decreases accordingly, and released
resources decreases.
4.1.2.2
Parameter name
25
Abbreviated name
AglLdDec
Description
This parameter indicates the algorithm of load decreasing

during common overload for HSDPA cell. HS load decreasing
and R99 load decreasing can be selected.
Range and Step
0: R99 Load Decreasing Algorithm

1: HS Load Decreasing Algorithm
Unit
N/A
Default Value (note)
0: R99 Load Decreasing Algorithm
OMC Path

Control Relationship ->Algorithm of load Decreasing
This parameter describes a general method for reducing load for an overload cell.
When R99 common overload takes place in a cell supporting HS, the system selects an
HS load decrease action or an R99 load decrease action.
To take R99 load decrease action and adopt the R99 common load control method,
refer to 3.1.4; to configure HS load decrease action for all subscribers of a cell
(including R99 and HS subscribers), refer to 3.2.4.By default, the system adopts R99
load decrease action.
4.1.2.3
Parameter name
Abbreviated name
UlDecRateSw
Description
This parameter is a switch indicating whether it is open or

closed for decreasing rate when the cell is in the uplink
overload state.
Range and Step
0: Closed
1: Open
Unit
N/A
1: Open
OMC Path

Control Relationship ->Uplink Switch for Shielding Rate Reduction
26
This parameter indicates whether the uplink downgrade switch is on or off. This
parameter is used only when load decrease takes place in the uplink.
If the setting of the parameter is disabled, the system does not reduce rate in the uplink
when the uplink load reaches the overload threshold; if the setting of the parameter is
enabled, the system reduces rate in the uplink when the uplink load reaches the
overload threshold. By default, the settings are enabled.
4.1.2.4
Parameter name
Abbreviated name
UlForceHandoffSw
Description

closed for forcing handover when the cell is in the uplink
overload state.
0: Closed
Range and Step
1: Open
Unit
N/A
0: closed
OMC Path

Control Relationship -> Uplink Switch for Shielding Forced Handover
This parameter indicates whether the forced handover attribute of the uplink load
control function is on or off. This parameter is valid only when the uplink is overloaded
and it is necessary to decrease the load.
If the setting of the parameter is disabled, the system does not perform forced handover
enabled, the system performs forced handover for load decrease when the uplink load
reaches the overload threshold. By default, the settings are disabled.
4.1.2.5
Parameter name
Abbreviated name
UlDropSw
Description

closed for dropping call when the cell is in the uplink overload
state.
27
Range and Step
0: Closed
1: Open
Unit
N/A
1: Open
OMC Path

Control Relationship -> Uplink Switch for Shielding Forced Drop
This parameter indicates whether the forced call drop attribute of the uplink load control
function is on or off. This parameter is valid only when the uplink is overload.
If the setting of the parameter is disabled, the system does not perform forced call drop
enabled, the system performs forced call drop for load decrease when the uplink load
reaches the overload threshold. By default, the settings are enabled.
4.1.2.6
Maximum Number of Degraded Uplink Load Steps Every Time
Parameter name
Maximum Number of Degraded Uplink Load Steps Every

Time
Abbreviated name
UlDnMaxStg
Description
This parameter indicates the maximum number of DRBC

steps of decreasing data rate for the selected service each
time when uplink overload happens.
Range and Step
[1, 8]
Unit
N/A
OMC Path

Control Relationship ->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 during the implementation of the load decrease measures 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
28
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. By
default, the settings is 1 step
4.1.2.7
Maximum Number of Uplink Forced Handover Users Every Time
Parameter name
Maximum Number of Uplink Forced Handover Users Every

Time
Abbreviated name
UlMaxForHoNum
Description
This parameter indicates the maximum number of selected

UEs which are forced to be handed over each time when
uplink overload happens.
Range and Step
[1, 50]
Unit
N/A
OMC Path

Control Relationship -> 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 operation, increase the
setting of the parameter; to switch fewer subscribers in the uplink forced handover
operation, decrease the setting of the parameter. By default, the setting of the
parameter is 5.
4.1.2.8
Maximum Number of Uplink Forced Drop Users Every Time
Parameter name
Maximum Number of Uplink Forced Drop Users Every Time
Abbreviated name
UlMaxDrpUrNum
Description

UEs which are forced to be dropped each time when uplink
overload happens.
Range and Step
[1, 50]
Unit
N/A
29
OMC Path

Control Relationship -> 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 overload.
To drop calls of more subscribers in the implementation of uplink forced call drop
solution, increase the setting of the parameter; to drop calls of fewer subscribers in the
implementation of uplink forced call drop solution, decrease the setting of the
parameter. By default, the setting is 5.
4.1.2.9
Parameter name
Abbreviated name
DlDecRateSw
Description
This parameter is a switch which indicates whether it is open

or closed for decreasing data rate when the cell is in the
downlink overload state.
Range and Step
0: Closed
1: Open
Unit
N/A
1: Open
OMC Path

Control Relationship ->Downlink Switch for Shielding Rate Reduction
This parameter indicates whether the downlink downgrade switch is on or off. This
parameter is used only when downgrade takes place in the downlink.
If the setting of the parameter is disabled, the system does not reduce the rate in the
downlink when the downlink rate reaches the overload threshold; if the setting of the
parameter is enabled, the system reduces the rate in the downlink when the downlink
load reaches the overload threshold. By default, the settings are enabled.
4.1.2.10
30
Parameter name
Abbreviated name
DlForceHandoffSw
Description
This parameter is a switch which indicates whether is open or

closed for forcing handover when the cell is in the downlink
overload state.
0: Closed
Range and Step
1: Open
Unit
N/A
0: Closed
OMC Path

Control Relationship -> Downlink Switch for Shielding Forced Handover
This parameter indicates whether the forced handover attribute of the downlink load
control function is on or off. This parameter is valid only when the downlink is
overloaded and it is necessary to decrease the load.
If the setting of the parameter is disabled, the system does not perform forced handover
when the downlink load reaches the overload threshold; if the setting of the parameter
is enabled, the system performs forced handover for load decrease when the downlink
load reaches the overload threshold. By default, the settings are disabled.
4.1.2.11
Parameter name
Abbreviated name
DlDropSw
Description
This parameter is a switch which indicates whether is open or

closed for dropping calls when the cell is in the downlink
overload state.
Range and Step
0: Closed
1: Open
Unit
N/A
Default Value
(note)
1: Open
OMC Path

Control Relationship -> Downlink Switch for Shielding Forced Drop
31
This parameter indicates whether the forced call drop attribute of the downlink load
control function is on or off. This parameter is valid only when the downlink is
overloaded and it is necessary to decrease the load.
If the setting of the parameter is disabled, the system does not perform forced call drop
when the downlink load reaches the overload threshold; if the setting of the parameter
is enabled, the system performs forced call drop for load decrease when the downlink
load reaches the overload threshold. By default, the settings are enabled.
4.1.2.12
Maximum Number of Degraded Downlink Load Steps Every Time
Parameter name
Maximum Number of Degraded Downlink Load Steps Every

Time
Abbreviated name
DlDnMaxStg
Description
This parameter indicates the maximum number of DRBC

steps of decreasing data rate for the selected service each
time when downlink overload happens.
Range and Step
[1, 8]
Unit
N/A
OMC Path

Control Relationship -> Maximum Number of Degraded Downlink Load Steps Every
Time
This parameter specifies the maximum number of degraded downlink load steps at a
time during the implementation of the load decrease measures 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. By default, the setting is 1 step.
4.1.2.13
Maximum Number of Deleted Downlink Radio Links Every Time
Parameter name
32
Maximum Number of Deleted Downlink Radio Links Every

Time
Abbreviated name
DlMaxDelRlNum
Description

radio links to be deleted each time when downlink overload
happens.
Range and Step
[1, 50]
Unit
N/A
OMC Path

Control Relationship ->Maximum Number of Deleted Downlink Radio Links Every Time
This parameter specifies the maximum number of radio links that can be deleted in
each forced handover operation when the downlink is overload.
To increase the number of radio links that can be deleted in the downlink forced
handover operation, increase the setting of the parameter; to decrease the number of
radio links that can be deleted in the downlink forced handover operation, decrease the
setting of the parameter. By default, the setting is 1.
4.1.2.14
Maximum Number of Downlink Forced Handover Users Every Time
Parameter name
Maximum Number of Downlink Forced Handover Users Every

Time
Abbreviated name
DlMaxForHoNum
Description

UEs which are forced to be handed over each time when
downlink overload happens.
Range and Step
[1, 50]
Unit
N/A
OMC Path

Control Relationship -> Maximum Number of Downlink Forced Handover Users Every
Time
This parameter specifies the maximum number of subscribers in each forced handover
operation when the downlink is overload.
33
To increase the number of subscribers in downlink forced handover operation, increase

the setting of the parameter; to decrease the number of subscribers in downlink forced
handover operation, decrease the setting of the parameter. By default, the setting is 5.
4.1.2.15
Maximum Number of Downlink Forced Drop Users Every Time
Parameter name
Maximum Number of Downlink Forced Drop Users Every

Time
Abbreviated name
DlMaxDrpUrNum
Description

UEs which are forced to be dropped each time when
downlink overload happens.
Range and Step
[1, 50]
Unit
N/A
OMC Path

Control Relationship -> 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 overload.
To increase the number of subscribers that can be disconnected in the implementation
of downlink forced call drop solution, increase the setting of the parameter; to decrease
the number of subscribers that can be disconnected in the implementation of downlink
forced call drop solution, decrease the setting of the parameter. By default, the setting
is 5.
4.2
R99 Load Control Parameters
4.2.1
R99 Load Control Parameter List
34
Abbreviated name
Parameter name
UlSeriousOverLd
Uplink Serious Overload Upper Limit(dB)
UlOverLd
Uplink Overload Upper Limit(dB)
UlAlrmLd
Uplink Overload Recovering Lower Limit(dB)
DlSeriousOverLd
Downlink Serious Overload Upper Limit(%)
DlOverLd
Downlink Overload Upper Limit(%)
DlAlrmLd
Downlink Overload Recovering Lower Limit(%)
SwitchToFach
Switch of Interactive Class/Background Class RAB->FACH

for Overload
NFach
Maximum Users of Interactive Class/Background Class

RAB->FACH for Overload
4.2.2
Configuration of R99 Load Control Parameters
4.2.2.1
Parameter name
Abbreviated name
UlSeriousOverLd
Description
This parameter indicates the upper limit of the uplink serious

overload. The system is in the serious overload status if the
uplink RTWP exceeds this threshold, and measures of serious
overload will be taken to decrease the load immediately.
Range and Step
[0, 62]dB step 0.1 dB
Unit
dB
20dB
OMC Path

Control Relationship ->Uplink Serious Overload Upper Limit(dB)
If the value of the uplink RTWP of the current cell exceeds this parameter, it means
that the system is in serious overload status and must 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. By default, the setting is 62dB.
4.2.2.2
Parameter name
Abbreviated name
UlOverLd
Description
This parameter indicates the upper limit of the uplink

overload. The system is in the overload status if the uplink
RTWP exceeds this threshold, and measures of overload will
be taken to decrease the load immediately.
35
Range and Step
[0, 62]dB step 0.1 dB
Unit
dB
20dB
OMC Path

Control Relationship ->Uplink Overload Upper Limit(dB)
The value of the uplink RTWP of the current cell exceeds this parameter, it means that
the system is in common overload status and must take common overload decrease
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. By default, the setting is 61dB.
4.2.2.3
Parameter name
Abbreviated name
UlAlrmLd
Description
A cell leaves overload state when its RTWP reported by

Node B is lower than the threshold indicated by this
parameter for a period of time.
Range and Step
[0, 62]dB step 0.1 dB
Unit
dB
20dB
OMC Path

Control Relationship -> Uplink Overload Recovering lower Limit (dB)
This parameter indicates the lower limit of the uplink overload recovery.
If the value of the uplink RTWP of the current cell is lower than this parameter, it
means that the system is not in overload status and the load decrease measures can be
stopped. If the value of the parameter increases, it is relatively easy to reach uplink
overload recovery; if the value of the parameter decreases, it is relatively hard to reach
uplink overload recovery status. By default, the setting is 57dB.
36
4.2.2.4
Parameter name
Abbreviated name
DlSeriousOverLd
Description
This parameter indicates the upper limit of the downlink

serious overload. The system is in the serious overload status
if the download TCP exceeds this threshold and measures of
serious overload should be taken to decrease the downlink
load immediately.
Range and Step
[1, 100]% step 1%
Unit
100%
OMC Path

Control Relationship -> Downlink Serious overload Upper Limit(%)
This parameter indicates the downlink overload upper threshold.

The value of the downlink TCP of the current cell exceeds this parameter, it means that
the system is in serious overload status and must 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. By default, the setting is 100%.
4.2.2.5
Parameter name
Abbreviated name
DlOverLd
Description
This parameter indicates the upper limit of the downlink

overload. The system is in the overload status if the downlink
load exceeds this threshold and measures of overload should
be taken to decrease the downlink load immediately.
Range and Step
[1, 100]% step 1%
Unit
90%
OMC Path

Control Relationship ->Downlink Overload Upper Limit(%)
37
This parameter indicates the upper limit of the downlink overload.

If the value of the downlink TCP of the current cell exceeds this parameter, it means
that the system is in common overload status and must take common 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. By default, the
setting is 90%.
4.2.2.6
Parameter name
Abbreviated name
DlAlrmLd
Description
This parameter indicates the lower limit for the downlink

overload recovers. The system recovers from the overload
status if the downlink load decreases below the threshold. And
the measures of decreasing the downlink load should be
stopped.
Range and Step
[1, 100]% step 1%
Unit
60%
OMC Path

Control Relationship ->Downlink Overload Recovering Lower Limit(%)
This parameter indicates the lower threshold of downlink overload recovery.

If the value of the downlink TCP of the current cell is lower than this parameter, it
means that the system is not in overload status and the load decrease measures can be
stopped. If the value of the parameter increases, it is relatively easy to reach downlink
overload recovery status; if the value of the parameter decreases, it is relatively hard to
reach downlink overload recovery status. By default, the setting is 60%.
4.2.2.7
Switch of Interactive Class/Background Class RAB->FACH for Overload
38
Parameter name

for Overload
Abbreviated name
SwitchToFach

or closed for interactive or background RABs to be
transferred to FACH from DCH or HSDPA when the cell is in
the overload state.
Description
0: Closed
Range and Step
1: Open
Unit
N/A
0: Closed
OMC Path

Control Relationship ->Switch of Interactive Class / Background Class RAB->FACH for
Overload
This parameter is the switch of migrating interactive/background RABs to the FACH

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

Overload
Parameter name
Maximum Users of Interactive Class/Background Class

RAB->FACH for Overload
Abbreviated name
NFach
Description
This parameter indicates the maximum users of interactive

or background RABs to be transferred to FACH from DCH or
HSDPA when the cell is in the overload state.
Range and Step
[0, 255]
Unit
N/A
OMC Path

Control Relationship ->Maximum Users of Interactive Class/Background Class RAB>FACH for Overload
39
This parameter specifies the maximum number of interactive/background subscribers

that can be transferred to the FACH when the cell is in the overload state. To increase
the number of interactive/background subscribers that can be transferred to the FACH
at a time when the cell is in the overload state, increase the value of the parameter; to
decrease the number of interactive/background subscribers that can be transferred to
the FACH when the cell is in the overload state at a time, decrease the value of the
parameter.
4.3
HSDPA Load Control Parameters
4.3.1
HSDPA Load Control Parameter List

Abbreviated name
Parameter name
HsdsOverLdThr
Common Overload Threshold for HS-DSCH(%)
HsdsRecoverThr
Recover Threshold for HS-DSCH Overload(%)
SwitchToFach

for Overload
NFach
Maximum Users of Interactive Class/Background Class RAB>FACH for Overload
4.3.2
Configuration of HSDPA Load Control Parameters
4.3.2.1
Parameter name
Abbreviated name
HsdsOverLdThr
Description
This parameter indicates the common overload threshold of

the HS-DSCH. The system is in the overload status when the
sum of HS-DSCH Required Power and the transmitted carrier
power of all codes not used for HS-PDSCH, HS-SCCH, EAGCH, E-RGCH or E-HICH is over this threshold, and
measures should be taken to decrease the load.
Range and Step
[1, 100]% step 1%
Unit
97%
OMC Path

Control Relationship ->Common Overload Threshold for HS-DSCH(%)
40
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, it means that the systems is in common overload status and takes common
overload decrease measures. 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
Parameter name
Abbreviated name
HsdsRecoverThr
Description
This parameter indicates the HS-DSCH overload recovery

threshold. The system recovers from the HS overload status if
the downlink load decreases below the threshold and
measures of decreasing the HS overload should be stopped.
Range and Step
[1, 100]% step 1%
Unit
96%
OMC Path

Control Relationship ->Recover Threshold for 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, it means that the systems is not in common overload status and the
common load decrease measures can be stopped. If the value of the parameter
increases, it is relatively easy to reach downlink overload recovery status; if the value of
the parameter decreases, it is relatively hard to reach downlink overload recovery
status.
4.3.2.3
Switch of Interactive Class/Background Class RAB->FACH for Overload
Parameter name

for Overload
Abbreviated name
SwitchToFach
Description

or closed for interactive or background RABs to be
transferred to FACH from DCH or HSDPA when the cell is in
the overload state.
41
0: Closed
Range and Step
1: Open
Unit
N/A
0: Closed
OMC Path

Control Relationship ->Switch of Interactive Class / Background Class RAB->FACH for
Overload
This parameter is the switch of migrating interactive/background RABs to the FACH

when the cell is in the overload state. If the setting of the parameter is off, the system
does not transfer the interactive/background DCH/HSDPA subscribers to the FACH
forcedly when overloading occurs; if the setting of the parameter is on, the system
transfers the interactive/background DCH/HSDPA subscribers to the FACH forcedly
when overloading occurs.
4.3.2.4
Maximum Users of Interactive Class/Background Class RAB->FACH for

Overload
Parameter name
Maximum Users of Interactive Class/Background Class RAB>FACH for Overload
Abbreviated name
NFach
Description
This parameter indicates the maximum users of interactive or

background RABs to be transferred to FACH from DCH or
HSDPA when the cell is in the overload state.
Range and Step
[0, 255]
Unit
N/A
OMC Path

Control Relationship ->Maximum Users of Interactive Class / Background Class RAB>FACH for Overload
This parameter specifies the maximum number of interactive/background subscribers

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

when the cell is in the overload state at a time,, decrease the value of the parameter.
4.4
HSUPA Load Control Parameters
4.4.1
HSUPA Load Control Parameter List

Abbreviated name
Parameter name
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 Load Control Parameters
4.4.2.1
Parameter name
Abbreviated name
NServToTotalPwr
Description
This parameter indicates the threshold of non-serving E-DCH

to total E-DCH power ratio. HSUPA overload control
mechanism will be triggered when non-serving E-DCH to total
E-DCH power ratio exceeds this threshold.
Range and Step
(0..100)% step 1%
Unit
15%
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Hspa
Configuration information In A Cell-> Target Non-serving E-DCH to Total E-DCH Power
Ratio(%)
If the setting 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 EDCH receive power in a non-service link of a cell over the total receive power of the EDCH 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 setting 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 EDCH receive power in a non-service link of a cell over the total receive power of the EDCH is relatively low, and it is very easy to trigger the mechanism of sending relative
grant to the UE in a non-service link.
43
4.4.2.2
Parameter name
Abbreviated name
MaxRTWP
Description
This parameter indicates the maximum target UL interference

for a certain cell, including received wide band power from all
sources, which is an offset relative to the UL interference
when there is no load in the cell. This parameter is used by
the Node B scheduler. As a result of scheduling, the total
rising RTWP caused by the uplink services should not
exceed this target value.
Range and Step
(0.. 62)dB step 0.1
Unit
dB
20dB
OMC Path

Management->Utran Cell->Utran Cell XXX->Modify Advanced Parameter->Hspa
Configuration information 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 setting of
the parameter increases. the RTWP of Node B increases accordingly; if the setting of
the parameter decreases, the RTWP of the Node B decreases accordingly.
4.5
MBMS Load Control Parameters

For details on the parameter description of MBMS load control, refer to MBMS
Technical Attribute Description.
44
Counter And Alarm
5.1
Counter List
5.1.1
Number of Call Drop by Load Control, Conversation Class
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
Counter No.
C301420744
Counter Name
Number of call drop by load control, Conversation class
Unit
None
Number of Call Drop by Load Control, Interactive Class

Counter No.
C301420745
Counter Name
Number of call drop by load control, Interactive class
Unit
None
Number of Call Drop by Load Control, Background Class

Counter No.
C301420746
Counter Name
Number of call drop by load control, Background class
Unit
None
Number of Call Drop by Load Control, Streaming Class

Counter No.
C301420747
Counter Name
Number of call drop by load control, Streaming class
Unit
None
Number of Rate Decreased by Load Control, Conversation Class

Counter No.
C301420748
Counter Name
Number of rate decreased by load control, Conversation
Unit
None
Number of Rate Decreased by Load Control, Interactive Class

Counter No.
C301420749
Counter Name
Number of rate decreased by load control, Interactive
Unit
None
45
5.1.7
Number of Rate Decreased by Load Control, Background Class
5.1.8
Counter No.
C301420750
Counter Name
Number of rate decreased by load control, Background

class
Unit
None
Number of Rate Decreased by Load Control, Streaming Class
5.1.9
Counter No.
C301420751
Counter Name
Number of rate decreased by load control, Streaming

class
Unit
None
Sum of Control Time of Load Control
5.1.10
Counter No.
C301420752
Counter Name
Sum of control time of load control
Unit
Second
Times of Load Control
5.1.11
Counter No.
C301420753
Counter Name
Times of load control
Unit
Times
Noise Floor of the System
5.2
Counter No.
C301421336
Counter Name
Noise floor of the System
Unit
dBm
Alarm List
This feature has no relative alarm.
Glossary
C
CAC
46
Call Admission Control
D
DCH
Dedicated Channel
DL
Downlink (Forward link)
DPCCH
Dedicated Physical Control Channel
DPCH
Dedicated Physical Channel
DPDCH
Dedicated Physical Data Channel
E
E-AGCH
E-DCH Absolute Grant Channel
E-RGCH
E-DCH Relative Grant Channel
E-HICH
E-DCH Hybrid ARQ Indicator Channel
F
FACH
Forward Access Channel
H
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
I/B
Interactive/Background
L
LC
Load Control
47
M
MBMS
Multimedia Broadcast Multicast Service
R
RACH
Random Access Channel
RNC
Radio Network Controller
RTWP
Received Total Wide Band Power
S
SIR
Signal to Interference Ratio
T
TCP
Transmitted Carrier Power
U
UE
User Equipment
W
WCDMA
48
Wideband Code Division Multiple Access

U DEI 0604 ZTE UTMS Overload Control Feature Description V3.00 200903

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

U DEI 0604 ZTE UTMS Overload Control Feature Description V3.00 200903

Uploaded by

Copyright:

Available Formats

Overload Control

Overload Control Feature Description

Overload Control Feature Description

Cui Lili / Zheng

Cui Lili / Zheng

2008 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Overload Control Feature Description

Functions and Attributes ...................................................................................... 1

Technical Description ........................................................................................... 3

Counter And Alarm .............................................................................................. 45

2008 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

Overload Control Feature Description

Number of Rate Decreased by Load Control, Conversation Class ......................... 45

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Overload Control Feature Description

Figures and Tables

R99 load control flowchart ......................................................................................... 4

R99 load control threshold......................................................................................... 5

Conversion between R99 load control states ............................................................. 6

R99 common overload control flowchart ................................................................. 10

R99 serious overload control flowchart .................................................................... 11

Load control flowchart for the HSDPA cells ............................................................. 13

Conversion between HSDPA load control states ..................................................... 14

HSDPA overload control flowchart .......................................................................... 19

HSUPA load control flowchart ................................................................................. 20

Classification of HSUPA load control states ............................................................ 21

Conversion between HSUPA load control states ..................................................... 21

2008 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

Overload Control Feature Description

Functions and Attributes

Overview of the Functions

R99 load control

HSDPA load control

HSUPA load control

MBMS load control

ZTE Confidential Proprietary

2008 ZTE Corporation. All rights reserved.

Overload Control Feature Description

Common overload control

Serious overload control

Uplink load control

Downlink load control

ZWF21-04-002 R99 Load Control Function

Decreasing the service rate of R99 subscribers;

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

Forcedly transferring the interactive subscribers or background subscribers to the

Forcedly dropping calls

ZWF23-04-002 HSDPA Load Control

2008 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

Overload Control Feature Description

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

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

ZWF25-04-002 HSUPA Load Control

Decreasing the service rate of R99 subscribers

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

Forcedly dropping low-priority services (DCH and HSDPA)