ZTE UMTS Overload Control Feature Guide U9.2

Operator Logo
Overload Control
WCDMA RAN
Feature Guide

Overload Control Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. I

Version Date Author Approved By Remarks
V4.0 2010-06-18
Wang
Shaoji ang
Cui Lili / Zheng Dan Not open to the Thi rd Party

2010 ZTE Corporation. All rights reserved.
ZTE CONFIDENTIAL: This document contai ns propriet ary 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 2010 ZTE Corporation. All rights reserved. II

TABLE OF CONTENTS
1 Functions and Attributes ....................................................................................1
2 Overview .............................................................................................................1
2.1 Overview of the Functions.....................................................................................1
2.1.1 Load Control Function ..........................................................................................2
2.1.2 HSDPA Load Control ............................................................................................2
2.1.3 HSUPA Load Control ............................................................................................3
3 Technical Description .........................................................................................3
3.1 R99 Load Control .................................................................................................3
3.1.1 R99 Load Control Flow .........................................................................................4
3.1.2 R99 Load Control States.......................................................................................5
3.1.3 Load Decrease Methods for R99 Load Cont rol .......................................................7
3.1.4 Load Decrease Methods for R99 Common Overl oad ............................................10
3.1.5 Load Decrease Method for R99 Seri ous Overl oad .............................................11
3.1.6 R99 Algorithm Rel ated Measurement ..................................................................12
3.2 HSDPA Load Control ..........................................................................................12
3.2.1 HSDPA Load Control Flow..................................................................................13
3.2.2 Decision Met hods for Conversion between HSDPA Load Control States ................14
3.2.3 Load Decrease Methods for HSDPA Load Control ................................................16
3.2.4 HSDPA Load Decrease Flow ..............................................................................18
3.2.5 Dual -Cell HSDPA Overl oad Control .....................................................................20
3.2.6 HSDPA Algorithm Related Measurement .............................................................21
3.3 HSUPA Load Control ..........................................................................................21
3.3.1 HSUPA Uplink Effecti ve Load .............................................................................22
3.3.2 HSUPA Load Control Flow..................................................................................23
3.3.3 Decision Met hods for Conversion between HSUPA Load Control States................24
3.3.4 Load Decrease Methods for HSUPA Load Control ................................................25
3.3.5 Load Decrease Methods for HUSPA Common Overload.......................................27
3.3.6 Load Decrease Methods for HSUPA Serious Overload .........................................27
3.3.7 HSUPA Algorithm Related Measurement .............................................................27
3.4 MBMS Load Control ...........................................................................................28
3.5 GBR Resource Consumption Limiting..................................................................28
3.5.1 HSDPA GBR Resource Consumption Prevention .................................................28
3.5.2 Relat ed Measurement ........................................................................................29
4 Configuration of Parameters.............................................................................29
4.1 Common Parameters .........................................................................................29
4.1.1 Common Parameter List .....................................................................................29
4.1.2 Common Parameter Configuration ......................................................................30
4.2 R99 Load Control Parameters .............................................................................35
4.2.1 R99 Load Control Parameter List ........................................................................35
4.2.2 Confi guration of R99 Load Control Parameters ....................................................36
4.3 HSDPA Load Control Paramet ers .......................................................................39
4.3.1 HSDPA Load Control Paramet er List ...................................................................39
4.3.2 Confi guration of HSDPA Load Cont rol Parameters ...............................................39
4.4 HSUPA Load Control Paramet ers .......................................................................40
4.4.1 HSUPA Load Control Paramet er List ...................................................................40
4.4.2 Confi guration of HSUPA Load Cont rol Parameters ...............................................41
4.5 MBMS Load Control Parameters .........................................................................41
4.6 GBR Resource Consumption Limiting Parameters................................................42
4.6.1 GBR Resource Consumption Limiting Paramters List ...........................................42


ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. III

4.6.2 Confi guration of GBR Resource Consumption Limiting Parameters .......................42
5 Counter And Alarm ...........................................................................................44
5.1 Counter List .......................................................................................................44
5.2 Alarm List ..........................................................................................................44
6 Glossary ...........................................................................................................44


ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. IV

FIGURES
Figure 1 R99 l oad control flowchart ......................................................................................4
Figure 2 R99 l oad control threshol d ......................................................................................5
Figure 3 Conversion between R99 load control states............................................................6
Figure 4 R99 common overload cont rol fl owchart ................................................................11
Figure 5 R99 serious overload control fl owchart ..................................................................11
Figure 6 Load control flowchart for the HSDPA cells ............................................................13
Figure 7 Conversion between HSDPA load cont rol states ....................................................15
Figure 8 HSDPA overload control flowchart .........................................................................19
Figure 9 HSUPA load control flowchart ...............................................................................23
Figure 10 Classification of HSUPA load control states ...........................................................24
Figure 11 Conversion between HSUPA load cont rol states ....................................................24


ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 1

1 Functions and Attributes
System version: [RNC V3.09, Node B V4.09, OMMR V3.09, and OMMB V4.09]
Attributes: basic functions + optional functions
NEs invol ved:
UE Node B RNC MSCS MGW SGSN GGSN HLR
- - - - -
Note:
*-: NEs not invol ved
*: NEs invol ved:
Dependency: [None]
Mutual exclusi ve functions: [None]
Remarks: [None]
2 Overview
2.1 Overview of the Functions
The load control is performed to control the load on indi vi dual 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 overl oad means the uplink/downlink load on a
cell exceeds the overload threshol d set during network pl anni ng. In such a case, the
system is in an unstable state, with its capacity so close to the limit. Appropriate
measures are requi red to decrease the system load. Overl oad i ncludes serious overl oad
and common overl oad. Seri ous overload means the load is so close to the limit and
requires prompt recovery.
By functional systems, the load control can be classifi ed into the foll owi ng types:
- R99 l oad control
- HSDPA load control
- HSUPA load control
- MBMS load control
By severity of overload, the load control can be classified into the foll owi ng two types:
- Common overload control
- Serious overload control



By direction of uplink/downli nk, load control can be classifi ed i nto the foll owi ng two types:
- Uplink load control
- Downlink load control
2.1.1 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 threshol d with RTWP and TCP. The
RNC impl ements load control i f RTWP or TCP exceeds the threshold. Here, the upli nk
load threshol d is a absolute val ue(dBm), it is equal to the sum of background
noise(dBm) and the relati ve value of uplink load control threshold(dB).
There are two types of overload: seri ous overl oad and common overl oad. According to
the overload type, the RNC system should take actions accordingly. Serious overl oad
means that the payload approaches the limit of system capacity. At the moment, the
RNC system must adj ust its payload to a normal level. Therefore, the system can
forcedly drop calls to reduce payl oad of a cell until the payload deceases to a value
below the threshol d of common overl oad. In the case of common overl oad, the system
can take the followi ng 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 downli nk connection and is not for the best cell)
- Forcedly handing over subscribers to an int er-frequency cell or an i nter-RAT cell
(the target cell has the same coverage as the overloaded cell or cont ains the
overloaded cell)
- Forcedly transferri ng the int eracti ve subscribers or background subscribers to the
CELL_FACH status
- Decreasing GBR of C/S traffic through the GBR renegotiation
- Forcedly dropping calls
When overl oading occurs, the system selects services or UEs through the overl oad
control pri ority and then takes above actions for these services. In this way, the system
can maintai n the stability for services of high-priority subscribers. .
2.1.2 HSDPA Load Control
The load cont rol of the HSDPA is based on the transmit power of a cell. The l oad control
function is triggered when the downli nk power reaches a certain value (which is
confi gurabl e through the OMCR). Duri ng the impl ementation of load control, the HSDPA
reduces the payload of a cell according to the difference of subscribers. The HSDPA
takes the following measures:



- Decreasing the service rate of R99 subscribers
- Forcedly deleting the UE soft handover radi o link from the overl oaded cell (includi ng
DCH subscribers and HS-DSCH subscri bers)
- 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 overl oaded cell or
contains the overloaded cell)
- Forcedly transferri ng the int eracti ve subscribers or background subscribers to the
CELL_FACH status
- Decreasing GBR of C/S traffic through the GBR renegotiation.
- Forcedly dropping calls of low-priority services (DCH and HSDPA).
2.1.3 HSUPA Load Control
When overl oadi ng 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 overl oaded cell or
contains the overloaded cell)
- Decreasing GBR of C/S traffic through the GBR renegotiation.
- Forcedly dropping low-priority services (DCH and HSDPA)
3 Technical Description
3.1 R99 Load Control
For R99 cells, the Node B periodically sends common measurement reports to the RNC,
and updates thei r uplink load RTWP and downlink load TCP. RNC compares the RTWP
and TCP with the l oad control threshol d. If the RTWP or TCP exceeds the threshold, it
means occurrence of overload and the load control process is carried out. Overl oad
includes seri ous overl oad and common overload.
Serious overl oad means the l oad is close to the limit and requi res prompt recovery. In
such a case, the foll owi ng 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 thr eshold.



For common overl oad, the following load reduction measures are available to decrease
the system load to a normal level as soon as possible:
- Decreasing the service rate of R99 subscribers;
- Forcedly handing over to inter-frequency or inter-RAT nei ghbori ng cell;
- Deleti ng the radi o link of any soft handover UE from the overl oaded cell;
- Transferring services of I/B subscribers to the RACH/FACH channels;
- Decreasing GBR (GBR renegotiati on)
- Forcedly releasing the service.
3.1.1 R99 Load Control Flow
The figure bel ow shows the overall R99 load control flowchart. The l oad control is
classified into seri ous overload cont rol and common overload control depending on
different overl oad states. The l oad control is triggered by common measurement reports
from the Node B.
Upon the recei pt 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 cont rol is carri ed out; in the sate of serious
overload, the seri ous overl oad control is carri ed out.
The overload control in all states is performed in the di rection of uplink and downli nk
respecti vely.
Figure 1 R99 load control flowchart



Common Measurement
Report
To make a
decision
for status
The status of
serious overload
The status of
normal load
The status of common
overload
To perform serious
overload control
Return
To perform common
overload control

3.1.2 R99 Load Control States
3.1.2.1 Classification of R99 Load Control States
Load control has three thresholds, which are seri ous overload threshol d, common
overload threshol d, and overl oad recovery threshol d. Relations among the three
threshol ds are: serious overl oad threshol d (upli nk: UlSeriousOverLd, downlink:
DlSeri ousOverLd) > common overload threshol d (upli nk: UlOverLd, downlink:
DlOverLd) > overl oad recovery threshol d (uplink: UlAl rmLd, downlink: DlAl rmLd). See
Figure 2. The overl oad thresholds are set in the direction of uplink and downli nk
respecti vely.
Figure 2 R99 load control threshold
The Threshold of Serious Overload
(uplink: UlSeriousOverLd,
downlink: DlSeriousOverLd)
The Threshold of Overload Recovery
(uplink: UlAlrmLd, downlink: DlAlrmLd)
The Threshold of Common Overload
(uplink: UlOverLd, downlink:DlOverLd)
The Load of Cell



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 int er-converti ble in
a relationship as shown in Fi gure 3.
Figure 3 Conversion between R99 load control states
normal
load
common
overload
serious
overload
4. Load below the threshold of load recovery
3. Load over the threshold of serious overload
(uplink: UlSeriousOverLd, downlink: DlSeriousOverLd)
6. Load below the threshold of serious overload
But over threshold of common overload
(uplink: UlOverLd, downlink: DlOverLd)
5. Load over the threshold of serious overload
1. Load over the threshold of common overload
(uplink: UlOverLd, downlink: DlOverLd)
2. Load below the threshold of load recovery

Note: When a cell is set up, the cell load is in the normal state.
1 In the normal state, when the load is found over the common overload threshol d but
below the seri ous overl oad threshold, the cell ent ers the common overl oad state.
2 In the common overl oad state, when load cont rol helps decrease the load below the
overload recovery threshol d, the cell returns to the normal state.
3 In the normal state, when the load is found over the serious overload threshol d, the
cell enters the seri ous overl oad state.
4 In the seri ous overl oad state, when load control helps decrease the load bel ow the
5 In the common overload state, when the load is found over the serious overload
threshol d, the cell enters the serious overload state.
serious overl oad threshol d but above the common overl oad threshol d, the cell
enters the common overload state.



7 These mutual conversions between load control states are implemented in the
direction of uplink and downli nk respecti vely.
3.1.3 Load Decrease Methods for R99 Load Control
The load decrease measures availabl e with l oad control include decrease of service rate,
forced handover to an i nter-frequency cell or a 2G cell under the same coverage, forced
deletion of the radio link of the UE in the macro di versity state from the overloaded cell
(the forced deleti on of a macro di versity link is also referred to as a mode of forced
handover), transfer of interacti ve and background services to the RACH/FACH channel,
decreasing GBR (GBR renegotiation) and forced drop of service. The following outlines
these load decrease met hods:
- Downgrade
- Forced handover
- Forced transfer of DCH to FACH
- Call drop (service disconnection)
The priorities of the methods in descendi ng order: Downgrade -> forced handover ->
forced transfer to RACH/FACH -> decreasing GBR (GBR renegotiation) ->call drop
These load control met hods are performed in the di rection of upli nk and downli nk
respecti vely. Whether a load control method is used can be confi gured in the
background.
3.1.3.1 Downgrade
Downgrade includes AMR service downgrade and PS service downgrade. The AMR
downgrade must fall within t he dynamic AMR rate range supported by the RNC and UE.
For information on AMR speed grading, refer to the ZTE UMTS AMR Feature Gui de. For
a subscriber wit h concurrent DCH service in additi on to AMR service, downgrade is
applicable only to the PS service rather t han the AMR service except for concurrence of
additional HS services. The stream services of the PS domai n can be decreased to the
Max(the l owest 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 specifyi ng the lowest level of DRBC, refer to the ZTE UMTS DRBC Algorithm Feat ure
Guide.
The rate of a service can be decreased by many levels at a time. The rate can be
di vided i nto many levels according to the rate levels of DRBC. The maximum rate l evels
(Ul DnMaxStg i n the uplink and DlDnMaxStg i n the downli nk) 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 shoul d be decreased: First, sort all the services according to the load control
priorities in descendi ng 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 pri ority and is based on basic priority, bearer
type, and real -time rate of a service. Since the l oad 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 i ndicates the
current allocated rate for the DCH. It is the GBR for the S traffic of HSPA, and the NBR
for the I/B traffic of HSPA. NBR (Nominal Bit Rate) refers to ZTE UMTS QoS Feature
Guide.
For details on the rul es of mapping bet ween the load control pri ority and basic priority,
bearer type, and service real -time rate, refer to ZTE UMTS QoS Feature Guide.
The parameter MaxNumUeOf DecRat controls the number of subscribers whose line
rates can be decreased i n the upli nk 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 rat e 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 overl oaded cell or contai ns the
overloaded cell), or forcedly del ete macro di versity links.
If it is requi red to hand over a call to an inter-frequency cell or 2G cell, the overl oaded
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 requi rements for i nter -frequency handover or inter-RAT handover.
For details, refer to the ZTE UMTS Handover Control Feature Gui de. Measurement is
not applied to the forced handover of load control, which is known as a kind of blind
handover.
Forced deletion of macro di versity link is to delete a radio link of the UE working in
macro di versity status in the overl oaded cell. If the UE is in the best cell, the UE cannot
be del eted. If the deleted link is not in the best cell, the link deletion does not seri ously
affect the service quality of the subscribers. The link deletion is applied only to downli nk
overload, because the upli nk 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 subscri bers by load control priority,
and then processes the subscriber with the lowest pri ority as needed. The l oad control
priority of a subscriber is determi ned by the service with the highest load control pri ority
among all his services.
The maximum number of subscribers allowed in a forced upli nk handover is controlled
by the parameter Ul MaxForHoNum; the maximum number of subscribers allowed in a
forced downli nk handover and the maximum number of downlink radi o links that can be
deleted each time are controlled by the parameter Dl MaxForHoNum.



3.1.3.3 Forced Transfer to FACH
Forced transfer to FACH means to decrease the system load by migrating interacti ve
and background subscribers to RACH/FACH channels in the case of overload. (Do not
perform this operation unl ess all services of the subscriber are of the I/B category.)
To perform forced transfer to FACH, the system should first sort all interacti ve and
background subscribers by l oad control pri ority, 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 di fferent load
control pri orities, 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 Guide. The
maximum number of subscribers allowed in a t ransfer is controll ed by the parameter
NFach.
3.1.3.4 GBR Decrease
When the cell is in the overl oad state, the switch for QoS
negotiation/renegotiation(QosNegRenegSwi ) is QoS renegotiati on open and the switch
for shielding GBR reduction(DecGbrSw) is open, configured at the daemon, GBR
decrease targets at services wit h current GBR hi gher than their lowest level of
negotiation GBR and then decrease GBR to their lowest level negotiation GBR at a time.
When performing GBR decrease, the system sorts all t he services accordi ng to the l oad
control pri orities in descendi ng order, decrease GBR of the subscriber with the lowest
priority. It is necessary to remap t he load control priority use new GBR after the HSPA S
GBR is decreased. The maximum number of services that can be performed GBR
decrease at a time (MaxDecGbrNum) is configured at the daemon.
Note:
1 The GBR exists in the C/S services only.
2 The l oad 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 t he current all ocated
rate for the R99 traffic. It is necessary to remap the load control pri ority for the
HSPA S traffic use the new GBR after the GBR is decreased, but no need for the
R99 traffic
3 For details of the GBR negotiation and the parameters QosNegRenegSwi,
DecGbrSw, and MaxDecGbrNum invol ved, refer to 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 load control pri ority
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 all owed in a forced uplink call drop is controlled by
the parameter Ul MaxDrpUrNum; the maximum number of subscribers allowed in a
forced downlink call drop is controlled by the parameter Dl MaxDrpUrNum.
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 appropriat e load decrease measures.
The load decrease action continues until the system load drops below the overl oad
recovery threshol d.
The load decrease for the common overload goes through the foll owi ng steps:
1 If the downgrade switch is on (the upli nk downgrade switch is UlDecRateSw; the
downlink downgrade switch is DlDecRat eSw) and the cell contai ns services with
high rates, sort the service according to the pri orities of these services in ascendi ng
order and then decrease the rates of the services. For det ails on downgrade, refer
to " 3.1.3.1 Downgrade".
2 If the forced handover switch is on (the upli nk 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 switch for QoS negotiation/renegotiation(QosNegRenegSwi) is QoS
renegotiation open , the switch for shiel ding GBR reduction(DecGbrSw)is open
and services wit h GBR higher than the mi nimum negotiation GBR exists, the
system sorts all the services according to the load control prioriti es in descending
order, decrease GBR of the subscriber with the lowest priority. For details on GBR
decrease method, refer to "3.1. 3.4 GBR Decrease ". Parameter DecGbrSw refers to
ZTE UMTS Services and Radio Access Bearers Feature Gui de.
5 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 pri ority in an
ascending sequence. For more det ails, refer to "3.1.3.5 Call Drop".
The fi gure below shows the common overload control fl owchart.



Figure 4 R99 common overload control flowchart
Findthemethodsofload
decreasingissupportedby
eachUEinthecell
Downgra
de
Forced
Handove
r
Transfer
DCHto
FACHof
I/Btraffic
Forced
Call
Drop
SwitchforDowngradeis
open(UlDecRateSw=1foruplink;
DlDecRateSw=1fordownlink)?
End
SwitchforForcedHandoverisopen
(UlForceHandoffSw=1foruplink;
DlForceHandoffSw=1fordownlink)?
SwitchforTransferDCHtoFACHofI/B
trafficisopen(SwitchToFach=1)?
SwitchforForcedCallDropis
open(UlDropSw=1foruplink;DlDropSw=1
fordownlink)?
No
Yes
No
No
Yes
Yes
Yes
No
SwitchforshieldingGBRreductionis
open(DecGbrSw=1)?
Decreasin
gGBRof
C/Straffic
Yes
No

3.1.5 Load Decrease Method for R99 Serious Overload
When the system load rises over the serious overload threshol d, the system enters the
serious overl oad state. For quick decrease of cell load, the system should force service
drop to release the calls of some subscri bers i n the cell. That is to perform the forced
service drop in the common overl oad control process which is described in section
3.1.3.4 Call Drop. When the system load recovers below the common overl oad
threshol d, the system enters the common overload state, and performs the downgrade
and forced handover for the common overl oad.
The fi gure below shows the serious overload control fl owchart:
Figure 5 R99 serious overload control flowchart



End
Start
Forced Call Drop
Load is below the threshold of the serious
overload(uplink: UlSeriousOverLd,
downlink: DlSeriousOverLd) ? No
Yes
Load is below the threshold of load
recovery (uplink: UlAlrmLd, downlink:
DlAlrmLd)?
Yes
No
Dereasing load with the method
of common overload

3.1.6 R99 Algorithm Related Measurement
3.1.6.1 Node B Common Measurement
The Node B common measurement informati on requi red for R99 load control includes:
- Recei ved 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 upli nk and downlink separately, and HSDPA
invol ves downlink al one, this section describes only the policies for downli nk load control
in the cells supporting the HSDPA.
In a cell supporti ng HSDPA, the load control policies are performed in two conditions:
1 NoHsPower>= R99 common overload threshold (DlOverLd), or NoHsPower>= R99
serious overload threshol d (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 (Dl OverLd), enabl e HS
load decrease or R99 load decrease accordi ng to the setti ng of parameter Agl LdDec. If
the algorithm of load decreasing (Agl LdDec) is set to R99 l oad decrease al gorithm, start
the R99 l oad 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 al gorit hm, the load
decrease action targets at DCH and HS-DSCH subscribers. The load decrease actions
and pri orities 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 overl oad threshol d (DlSeri ousOverLd), 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 +
spi
r quiredPowe HsRe >= HS
overload threshol d, where HsRequi redPower 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 overl oad control, R99 serious overload control, and HS overl oad
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 supporti ng 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 upli nk load
control is omitted here.
Figure 6 Load control flowchart for the HSDPA cells



Common
measurement
report of node B
AglLdDec indicate
R99 reducing
load?
Load status
judgment
Normal
load
R99 common
overload
R99 serious
overload
HS
overload
Back
Reduce load of
R99 serious
overload
Reduce load of
HS overload
Reduce Load of
R99 overload
No
Yes

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
threshol ds are omitted here):
- HS-DSCH common overl oad threshold (HsdsOverLdThr)
- HS-DSCH overl oad recovery threshold (HsdsRecoverThr)
A comparison between t he current load and each threshold can determi ne four states:
normal state, R99 common overload state, R99 seri ous overload state, and HS overl oad
state.
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 fi gure 6 are
inter-converti ble in a rel ationshi p as shown below, where R99 overl oad states contai ns
R99 common overload state and R99 seri ous overl oad state:



Figure 7 Conversion between HSDPA load control states

Normal load
Hs overload
NoHsPower+HsRequiredPower over the threshold of
hs overload(HsdsOverLdThr) and NoHsPower below
the threshold of R99 common overload(DlOverLd)
NoHsPower+HsRequiredPower below the threshold of hs overload recovery(HsdsRecoverThr)
and NoHsPower below the threshold of R99 overload recovery(DlAlrmLd)
R99 overload
NoHsPower over the threshold of
R99 common Overload(DlOverLd) or
serious overload(DlSeriousOverLd)
NoHsPower+HsRequiredPower below the threshold of
hs overload recovery(HsdsRecoverThr) and NoHsPower
below the threshold of R99 overload recovery(DlAlrmLd)
NoHsPower+HsRequiredPower over the threshold
of hs overload(HsdsOverLdThr) and NoHsPower over
the threshold of R99 overload recovery(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 in the normal state.
1 In the normal state, when NoHsPower is found below the R99 common overload
threshol d and NoHsPower+

spi
r quiredPowe HsRe exceeds the HS overload
threshol d, the cell enters the HS overl oad state.
2 In the HS overl oad state, when NoHsPower is found below the R99 overload
recovery threshold and NoHsPower+

spi
r quiredPowe HsRe decreases bel ow
the HS overl oad recovery threshold, the cell returns to the normal state.
3 In the normal state, when NoHsPower is found over the R99 common overload
threshol d but below the R99 seri ous overload threshold, the cell enters the R99
common overload state.
4 In the normal state, when NoHsPower is found over the R99 serious overload
threshol d, the cell enters the R99 serious overl oad state.
5 In the R99 common overl oad state, when NoHsPower is found over the R99 serious
overload threshol d, the cell enters the R99 serious overload state.
6 In the R99 seri ous overl oad state, when NoHsPower is found down below the R99
common overload threshol d but above the R99 overload recovery threshold, the cell
enters the R99 common overload state.



7 In the R99 common or serious overl oad state, when NoHsPower is found down
below the R99 overl oad recovery threshold and
NoHsPower+
spi
r quiredPowe HsRe is below the HS overload recovery threshol d,
the cell returns to the normal state.
8 In the R99 common or serious overl oad state, when NoHspower is found over the
threshol d of R99 overl oad recovery, and NoHsPower+
spi
r quiredPowe HsRe
over the HS overload threshold, the cell enters the HS overload state.
3.2.3 Load Decrease Methods for HSDPA Load Control
R99 overl oad and HS overl oad occur in cells supporting HSDPA. In the case of R99
common overload, there are two load decrease methods correspond to the R99 l oad
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 wit h the following methods:
- Downgrade
- Forced handover
- Forced transfer to FACH
- Call drop
The priorities of the above fi ve load decrease methods can be sort ed as downgrade ->
forced handover-> forced transfer to FACH -> Decreasing GBR (GBR renegotiati on) ->
call drop
You can confi gure 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 appli ed 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.
Forced handover is to hand over t he subscri bers a cell to an i nter -frequency cell or a 2G
cell (the target cell has the same coverage as the overloaded cell or contains the
overloaded cell), or forcedly del ete macro di versity links.



Forced handover to an i nter-frequency cell or a 2G cell under the same coverage is
appli ed 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 di versity 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 delet ed even though the DPCH channel is in the macro
di versity status. If the cell is not a serving cell of UE HS-DSCH, the associated DPCH
channel can be delet ed.
When forcedly handing over services to an inter-frequency cell with the same coverage,
the system first sorts the DCH subscri bers 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 wit h the lowest priority. When there are
multiple concurrent services, the system selects the service wit h the highest load control
priority among all the services of the subscriber.
The method for selecting t he UE on the HS for li nk del etion: first make sure the UE is in
the macro di versity state and the cell is not its HS-DSCH serving cell, and then make
selection by the application priority of the load control on the DCH in an ascending
sequence (note: i f there is only signaling on the DCH, the rate used by the subscriber to
determine its application priority shoul d be set to the signaling rate, and other
parameters should foll ow the RAB parameters on the HS-DSCH. If there are multiple
RABs, the one with the highest load control should be foll owed). If there are concurrent
services on the DCH, the load control pri ority should be determined by the service with
the highest priority.
The load control priority is obtained by mappi ng the basic priority (BP), bearer type, and
subscribers real-time rate. For stream services carri ed over the HS-DSCH channel, the
real -time rate of t he stream service is the assured rat e; for I/B service, the real -time rate
is NBR for the I/B traffic of HSPA. NBR (Nominal Bit Rate) refers to ZTE UMTS QoS
Feature Gui de.
Dl MaxForHoNum (t he maximum number of subscribers invol ved i n a forced handover or
the maximum number of links deleted at a time) is the same as the parameter adopted
by R99 downlink load control and can be confi gured at the OMC.
3.2.3.3 Forced Transfer to FACH
Forced transfer to FACH means transfer of interacti ve 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 l ast 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 al l interacti ve and
background subscribers by l oad control pri ority, and then start with the subscriber with
the lowest priority as needed. The load cont rol pri ority of a subscriber is determi ned by
the service with the hi ghest load control pri ority among al l his services.
For details on the factors rel ated to l oad control priorities and mapping met hods, refer to
ZTE UMTS QoS Feature Guide. For I/B traffic, the real -time rate is NBR for I/B traffic of
HSPA. NBR (Nomi nal Bit Rate) refers to ZTE UMTS QoS Feature Gui de.
The maximum number of subscribers in a forced transfer ( NFach) is the same as the
parameter used i n R99 load control, and can be configured through the daemon.



The method of GBR decrease i n HSPA is same as that in R99, referring to 3.1.3. 4. Note
that it is necessary to remap the load control pri ority use 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 t he associated channel DPCH of the HS-
DSCH subscribers also occupi es 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 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 bit rat e is NBR for I/B
traffic of HSPA. NBR (Nomi nal Bit Rate) refers to ZTE UMTS QoS Feature Gui de.
The maximum number of subscribers in a call drop event ( Dl MaxDrpUrNum) is the same
as the parameter used i n 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 overl oad 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 bel ow the HS overl oad
recovery threshold. The load decrease methods for HS overload invol ve the R99 load
decrease and HS load decrease. This section descri bes 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 (DlDecRateSw) is opened 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 " 3.2.3.1 Downgrade".
2 If the forced handover switch (DlForceHandoffSw) is opened, when the cell is the
best cell of DCH channel or the serving cell of HS-DSCH channel of the UE (the UE
has single radio link or macro-di versity radio links), if there were inter-frequency
cells or a 2G cells has the same coverage or contains the overl oaded cell, then sort
the UEs accordi ng to the pri orities in ascending order and then perform the forced
handover for these UEs. And when the cell is neither the best cell of DCH channel
nor the servi ng cell of HS-DSCH channel of the UE (t he UE is only in macro-
di versity condition), then sort the UEs accordi ng to the priorities in ascending order
and then delete macro di versity links for these UEs. For details on forced handover
and delete macro-di versity radi o link, refer to "3.2.3.2 Forced Handover".



3 If the switch of forced transfer from DCH to FACH (SwitchToFach) is opened and
the cell contained DCH subscribers supporting transfer to the FACH, sort the
subscribers according to the priorities in ascendi ng 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 opened and the cell contai ns
subscribers supporting forced handover, sort the subscribers according t o the
priorities in ascendi ng order and then perform the forced handover for these
subscribers. For details on call drop, refer to "3.2.3.5 Call Drop".
The fi gure below shows the HS overl oad control flowchart:
Figure 8 HSDPA overload control flowchart



Strat
End
SwitchforDowngrade
isopen
(DlDecRateSw=1)?
Existtraffic
canbe
downgrade?
Downgrade
SwitchforForced
HandoverorDeletingRL
ofMacroDiversityis
open
(DlForceHandoffSw=1)?
Thecellisthebestcellof
DCHchannelorthe
servingcellofHS-DSCH
channeloftheUE?
therewereinter-
frequencycellsor2G
cellshavethesame
coverageorcontains
theoverloadedcell?
SwitchforTransferDCH
toFACHofI/Btrafficis
open(SwitchToFach=1)?
Canbe
convertedto
FACH?
SwitchforCall
Dropisopen
(DlDropSw=1)?
DeletingRLof
MacroDiversity
(UEinmacro-
diversity)
ForcedHandover
(UEhassingle
RLormacro-
diversityRLs)
TransferDCHto
FACHofI/B
traffic
CallDrop
Yes
No
Yes
No
Yes
NO
No
No
Yes
Yes
No
Yes
Yes
No
No
Yes
No
SwitchforshieldingGBR
reductionis
open(DecGbrSw=1)?
QoSrenegotiationswitchis
open?AndexistC/Sservices
canberenegotiationedto
lowerGBRlevel?
Yes
Yes
DecreasingGBR
ofC/Straffic
No

3.2.5 Dual-Cell HSDPA Overload Control
For Dual-Cell HSDPA overl oad control, the algorithm of downgrade, forced transfer to
CELL_FACH and GBR decrease are consistent with which for single frequency HSDPA
cell.



For Dual -Cell HSDPA, the method to select the user to be forced handover is also same
as that for single frequency HSDPA cell. But if the overl oad cell is the secondary
frequency cell of the UE selected to handover, it only needs to remove the secondary
frequency of this UE.
For Dual-Cell HSDPA, the method to select the user to be forced call drop is also the
same as that for single frequency HSDPA cell. But the selection range contains all the
single frequency UEs and the Dual -Cell HSDPA UEs whose HS-DSCH Requi red Power
is not zero.
3.2.6 HSDPA Algorithm Related Measurement
The Node B common measurement information requi red for HSDPA load control
includes:
- HS-DSCH Requi red Power(HsRequiredPower)
- Transmitted carri er 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 effecti vely control the fluctuation of the
uplink RTWP. Therefore, the overl oad threshold of the E-DCH cell is higher than the
uplink overload threshol d configured for a common R99 cell. The database does not add
new thresholds and still uses the origi nal common overl oad threshold and serious
overload threshol d 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
confi gure the parameter NServToTotalPwr, which is the percentage of the E-DCH
recei ve power of the non-service link over the total E-DCH recei ve power. The
percentage of the recei ve power over the tot al recei ve power of the E-DCH is
NServToTotalPwr. Node B keeps NServToTotalPwr to control the scheduli ng of t he E-
DCH so that the percentage of the power of the E-DCH subscri ber in the non-service
link of the cell over the the power of all E-DCH subscribers does not exceed
NServToTotalPwr. To achi eve this purpose, Node B sends DOWN message (power
decrease aut horizati on) 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 upli nk effecti ve load.



3.3.1 HSUPA Uplink Effective Load
In order to forecast the upli nk interference and j udge the uplink load state, we must
know the uplink effecti ve l oad, which is the part load that Node B can not control. The
uplink effecti ve load can be expressed in the formul a as foll owi ng:
Uplink effecti ve load = the load produced by uplink DCH + the load produced by non-
scheduling E-DCH services + the load produced by non-serving E-DCH services + the load
produced by neighboring cell interference + the load produced by the GBR throughput of
scheduling E-DCH GBR services.
Order:
a=10^((RSEPS)/10);
I
total
=10^((RTWP*)/10)[mW];
Then,
Uplink effecti ve load = I
total
(1-a) + the load produced by the GBR throughput of scheduling E-
DCH GBR services.
Where,
i. I
total
(1-a) = background noise + the load produced by uplink DCH + the load produced by
non-serving E-DCH services + the load produced by neighboring cell interference
(contains the load produced by non-scheduling E-DCH services). It can be get from the
RTWP and RSEPS common measurement report.
ii. The load produced by the GBR throughput of scheduling E-DCH GBR services can be
get from the uplink interference forecast formula as following:
I( ) I
1
L
total
C
dBm
q
A =

Where,
I
total
is get from common measurement report (RTWP*);
= 1 - N
0
/ I
total

N
0
is uplink background and recei ver noise. If the background noise adjustment
switch (BckNoiseAdjSwh) is closed, N
0
can be get from the parameter
OriBckNoise. And i f the background noise adjustment switch
(BckNoiseAdjSwh) is opened, N
0
can be get from the uplink background noise
automatic measurement result, refer to the section 3.1.1.3 Automatic
Measurement of Uplink Background Noise of ZTE UMTS Admission Control
Feature Gui de.
Load forecast factor |
.
|
\
|
+ =
W
R
i C
L
|
o ) 1 ( , W=3.84e6[bit/s];
o is the uplink activation gain of the services, determined by the parameter Alfa;



i
is the uplink interference factor of adjacent cells to current cell (Ul InterFactor).
=10
^((Eb/N0 )/10 )

Eb/N0 is the uplink quality factor. As all scheduling E-DCH services are unifi ed
scheduled by NodeB, several users share the system resource, so the Eb/ N0 of
scheduling E-DCH is get from the parameter (SEdchEbN0), and it is same to
different services.(The Eb/N0 is same for non-scheduling E-DCH and DCH. )
R is the sum of the GBR rat e of the online scheduling E-DCH services.
The method to calcul ate the upli nk effecti ve l oad of HSUPA cell and relati ve parameters
please refer to ZTE UMTS Admission Control Feature Guide.
3.3.2 HSUPA Load Control Flow
The fi gure 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 cont rol is triggered by common measurement reports from the
Node B.
Upon the recei pt 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.3, and
performs an appropriate process depending on the decision result. In the state of
common overload, the common overload cont rol is carri ed out; in the sate of serious
overload, the seri ous overl oad control is carri ed out.
The load control described in this section is specific to the uplink direction.
Figure 9 HSUPA load control flowchart
Common Measurement
Report
To make a
decision
for status
The status of
serious overload
The status of
normal load
The status of common
overload
To perform serious
overload control
Return
To perform common
overload control



3.3.3 Decision Methods for Conversion between HSUPA Load Control
States
3.3.3.1 Classification of HSUPA Load Control States
The HSUPA load control has three threshol ds, which are seri ous overl oad
threshol d(UlSeriousOverLd*), common overl oad threshold(Ul OverLd*), and overl oad
recovery threshold(UlAl rmLd*). The relati onship bet ween these three threshol ds and the
maximum target RTWP(MaxRTWP*) is: UlSeriousOverLd* > UlOverLd* > MaxRTWP* >
UlAlrmLd*, as shown in the foll owi ng diagram, where the relationship is speci fic to the
uplink di rection. Where, UlSeri ousOverLd*(dBm)=cell background noise(dBm)+
UlSeri ousOverLd(dB); UlOverLd*(dBm)= cell background noise(dBm)+ UlOverLd(dB);
UlAlrmLd*(dBm) = cell background noise(dBm)+ UlAl rmLd(dB); MaxRTWP*(dBm)= cell
background noise(dBm)+ MaxRTWP(dB). How to get cell background noise refer to ZTE
UMTS Admission Control Feat ure Guide.
The E-DCH cells adopt the common overload threshol d and serious overload threshold
confi gured for the ori ginal DCH. The serious overload threshol d is configured the same
as that for the DCH, whil e the common overload threshol d in the E-DCH cells is
confi gured hi gher than that in the DCH cells.
Figure 10 Classification of HSUPA load control states
The Threshold of Serious
Overload(UlSeriousOverLd*)
The Threshold of Overload
Recovery(UlAlrmLd*)
The Threshold of Common
Overload(UlOverLd*)
The Uplink Load
Maximum Target RTWP(MaxRTWP*)
Forbid to use in the period of load recovering

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.3.2 Conversion between HSUPA Load Control States
With the change of load on a cell, the three states of load control are int er-converti ble in
a relationship as shown below:
Figure 11 Conversion between HSUPA load control states



normal
load
common
overload
serious
overload
4. Load below the threshold of
overload recovery(UlAlrmLd*)
3. Load over the threshold of
serious overload(UlSeriousOverLd*)
6. Load below the threshold of serious
Overload(UlSeriousOverLd*) But over the threshold of
common overload(UlOverLd*)
serious overload(UlSeriousOverLd*)
common overload(UlOverLd*)
2. Load below the threshold of
overload recovery(UlAlrmLd*)

Note: When a cell is set up, the cell load is in the normal state.
1 In the normal state, when the load is found over the common overload threshol d but
below the seri ous overl oad threshold, the cell ent ers the common overl oad state.
2 In the common overl oad state, when load cont rol helps decrease the load below the
3 In the normal state, when the load is found over the serious overload threshol d, the
cell enters the seri ous overl oad state.
5 In the common overload state, when the load is found over the serious overload
threshol d, the cell enters the serious overload state.
serious overl oad 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.
3.3.4 Load Decrease Methods for HSUPA Load Control
In the overload state, the Node B has decreased, through scheduli ng, the rate of non-
GBR services on the E-DCH extremely low nearly 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 pri orities of the above three downgrade met hods can be sorted as downgrade ->
forced handover-> decreasing GBR (GBR renegotiation) ->forced call drop
3.3.4.1 Downgrade
Downgrade is appli ed only to the DCH services, including PS service and CS service, in
the same way as 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 overl oaded cell). Forced handover targets at all subscribers of the
specified cell, including DCH and E-DCH subscri bers. Performi ng forced handover
selects target subscriber according to l oad control priority, which is mapped from the BP,
real -time rat e, and bearer type. The real-time rate is GBR for HSUPA S traffic, and the
current allocated rate for the DCH traffic. The mapping rules between load control
priority and BP, Bearer type and real -time rate and NBR (Nomi nal Bit Rate) refer to ZTE
UMTS QoS Feature Gui de.
If the subscriber selected for handover is an E-DCH subscri ber, the system selects an E-
DCH cell with the same coverage; i f the handover fails or the mentioned cell does not
exist, the handover process accompani es the transfer from the E-DCH to the DCH.
The method of GBR decrease i n HSPA is same as that in R99, referring to 3.1.3. 4. Note
that it is necessary to remap the load control pri ority use 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 load control
priority (3.3.4.2) 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.5 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 appropriat e load decrease measures.
The load decrease action continues until the system load drops below the overl oad
recovery threshol d.
The load decrease for the common overload goes through the foll owi ng steps:
1 If the upli nk DCH downgrade switch ( Ul DecRateSw) is on and there are DCH
services to be decreased in the uplink, the system implements the uplink DCH
downgrade fl ow. For more details, refer to " 3.3.4.1 Downgrade".
2 If t he uplink forced handover switch (UlForceHandoffSw) 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".
4 If the uplink forced call drop switch (Ul DropSw) 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 threshol d, the system enters the
serious overload state. For quick decrease of cell load, the system shoul d delete the UE
with excessi ve SIR ERROR, and then perform forced service drop to rel ease 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 overl oad
threshol d, the system enters the common overload state and performs the common
overload cont rol.
3.3.7 HSUPA Algorithm Related Measurement
The Node B common measurement information requi red for HSUPA load control
includes:
- E-DCH Provi ded Bit Rate
In this common measurement information, we can get the current rate for different SPI of
the scheduli ng E-DCH services.
- Recei ved schedul ed E-DCH power share



This common measurement information contai ns the RSEPS and RTWP*, in this
informati on we can get the RTWP of current cell and RTWP produced by scheduling E-
DCH services.
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.
3.5 GBR Resource Consumption Limiting
Because GBR services need to guarantee the GBR, so when the radio condition is bad,
it will consume t oo much resource of the cell. In order t o resol ve this problem, ZTE RNC
can limit the GBR resource consumption.
For R99 and HSUPA services, configure maximum power of DCH and E-DCH channel
to limit the DCH and E-DCH transmit power, in t his way, the GBR resource consumption
can be limited.
And for HSDPA services, the method to limit the GBR resource consumption is based
on 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.
3.5.1 HSDPA GBR Resource Consumption Prevention
When the switch for limiting HSDPA GBR resource consumption (HsGBRLimitSwi ) is
opened, the foll owi ng method can be used to limit the HSDPA GBR resource
consumption.
When the required power of HSDPA GBR service is bigger then a threshold
(RequiredPower> RequiredPowerlimit), i f the GBR of t his service can be decreased by
the method of GBR renegotiation, the GBR of this service woul d be decreased, and if
the GBR of this service can not be decreased, the service woul d be forced drop. The
description of the GBR decrease please refer to the section 3.1.3.4 of this paper, and
also refer to ZTE UMTS Services and Radio Access Bearers Feature Guide.
Where,
1 The required power of HSDPA GBR service is get form HS-DSCH Required Power
Per UE Weight(Expressed in percentage of the value provided in the HS-DSCH
Required Power Value IE)in common measurement report, and it need t o be
converted to an absolute value (unit: dBm).
2 RequiredPowerlimit(dBm) is the upper limit for HS-DSCH required power. Fi rstly,
get the required power offset(dB) rel ati ve 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 HSDPA GBR resource
consumption accordi ng to each GBR grades. its elements and the GBR levels of
HSDPA services (HsGBRLev[ MAX_NUM_HS_GBR]) have a one to one
relationship. The number of HSDPA GBR levels is HsGBRLevNum. We can get a
index by reading the cell limiting HSDPA GBR resource consumption
index(CHsGBRResLmtIdx) in the cell, and then get the correspondi ng
index(HsGBRResLimitId) in the GBR resource consumption limiting parameters
table, in this way, we get the val ue of the
UEHsReqPwrUplim[ MAX_NUM_HS_GBR], HsGBRLev[ MAX_NUM_HS_GBR] and
HsGBRLevNum.
Note:
1 If the UE has multi-services, and the services have same SPI, we get the sum of the
GBRs of each HSDPA GBR service with same SPI in one UE, and then get the
required power threshol d accordi ng to this GBR sum result.
2 If the UE has multi-services, but the service have different SPI, we get the required
power thresholds and compare with required power of the services respecti vely.
(HS-DSCH Required Power in the common measurement report is the total
required power for all services with same SPI in the cell, while the HS-DSCH
Required Power Per UE Weight is the required power for services with same
SPI in the same UE) .
3 The HS-DSCH requi red power limiting can make GBR decreased, and the event 4A
can make GBR increased, in order to avoi ding the ping-pong bet ween GBR
increase and decrease, after the GBR be decreased by HS-DSCH required power
limiting, if the serving RL of the service is not change, the GBR of this service can
not be increased. The description of the GBR increased please refer to ZTE UMTS
Services and Radi o Access Bearers Feat ure Guide.
3.5.2 Related Measurement
- HS-DSCH Requi red Power Per UE Weight(Expressed in percentage of the val ue
provided in the HS-DSCH Required Power Val ue IE)
4 Configuration of Parameters
4.1 Common Parameters
4.1.1 Common Parameter List
Abbreviated name Parameter name
MaxNumUeOfDecRat
Maximum Number of UE Decreasing Rate When
Congestion
AglLdDec Algorithm of Load Decreasing
UlDecRateSw Uplink Switch for Shi eldi ng Rate Reduction
UlForceHandoffSw Uplink Switch for Shi eldi ng Forced Handover



UlDropSw Uplink Switch for Shi eldi ng 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 Shi eldi ng Rate Reduction
DlForceHandoffSw Downlink Switch for Shi eldi ng Forced Handover
DlDropSw Downlink Switch for Shi eldi ng Forced Drop
DlDnMaxStg
Maximum Number of Degraded Downlink Load Steps
Every Time
DlMaxForHoNum
Maximum Number of Downlink Forced Handover or
Delet ed Radi o Links 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
- OMC Path
Path: View->Confi guration Management->RNC NE->RNC Radio Resource
Management->Utran Cell->Utran Cell XXX->Modi fy Advanced Parameter->Load Control
Relati onship ->Maximum Number of UE Decreasing Rate When Congestion
- Parameter confi guration
The parameter is used when load decrease is triggered due to congestion. The system
decides the number of uplink/downli nk DCH subscribers according to the current
congestion level.
If the system increases the val ue of the paramet er for l oad 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 Algorithm of Load Decreasing
- OMC Path
Relati onship ->Algorit hm 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 l oad 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 Uplink Switch for Shielding Rate Reduction
- OMC Path
Relati onship ->Upli nk Switch for Shieldi ng Rate Reduction
This parameter indicat es 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 upli nk load reaches the overload t hreshold; i f the setting of the parameter is
enabled, the system reduces rate in the uplink when the uplink load reaches the
overload threshol d. By default, the settings are enabl ed.
4.1.2.4 Uplink Switch for Shielding Forced Handover
- OMC Path
Relati onship -> Uplink Switch for Shi eldi ng Forced Handover
This parameter indicates whether the forced handover attribute of the upli nk load control
function is on or off. This parameter is valid only when the upli nk is overloaded and it is
necessary to decrease the l oad.
If t he setting of the paramet er is disabled, the system does not perform forced handover
enabled, the system performs forced handover for l oad decrease when the upli nk load
reaches the overl oad threshold. By default, the settings are disabl ed.
4.1.2.5 Uplink Switch for Shielding Forced Drop
- OMC Path



Relati onship -> Uplink Switch for Shi eldi ng Forced Drop
This parameter indicat es whether the forced call drop attribute of the upli nk 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 overl oad threshold. By default, the settings are enabled.
4.1.2.6 Maximum Number of Degraded Uplink Load Steps Every Time
- OMC Path
Relati onship ->Maximum Number of Degraded Upli nk Load Steps Every Time
This parameter speci fies 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 i n reference to the confi guration of DRBC
uplink rat e steps.
Provi ded that the number of upli nk DRBC rat e 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. Provi ded t hat the number of upli nk 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
- OMC Path
Relati onship -> Maximum Number of Uplink Forced Handover Users Every Time
This parameter specifi es 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 upli nk forced handover operation, increase the setting
of the paramet er; to switch fewer subscribers in the uplink forced handover operation,
decrease the setting of the parameter. By default, the setting of the paramet er is 5.
4.1.2.8 Maximum Number of Uplink Forced Drop Users Every Time
- OMC Path
Relati onship -> Maximum Number of Uplink Forced Drop Users Every Time
This parameter specifi es the maximums number of subscribers supported in each forced
call drop operation when the uplink is overl oad.
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 subscri bers in the
implementation of uplink forced call drop soluti on, decrease the setting of the parameter.
By default, the setting is 5.
4.1.2.9 Downlink Switch for Shielding Rate Reduction
- OMC Path
Relati onship ->Downli nk Switch for Shiel ding Rate Reduction
This parameter indicates whether the downlink downgrade switch is on or off. This
parameter is used only when downgrade takes place i n the downli nk.
If the setting of the paramet er is disabled, the system does not reduce the rate in the
downlink when the downlink rate reaches the overload threshol d; if the setting of the
parameter is enabled, the system reduces the rate in the downli nk when the downli nk
load reaches the overl oad threshold. By default, the settings are enabled.
4.1.2.10 Downlink Switch for Shielding Forced Handover
- OMC Path
Relati onship -> Downli nk Switch for Shi eldi ng Forced Handover



This parameter indicates whether the forced handover attribute of the downlink load
control function is on or off. This parameter is vali d only when the downlink is
overloaded and it is necessary to decrease the load.
If t he setting of the paramet er is disabled, the system does not perform f orced handover
when the downlink load reaches the overload threshol d; if the setting of the parameter is
enabled, the system performs forced handover for load decrease when the downli nk
load reaches the overl oad threshold. By default, the settings are disabled.
4.1.2.11 Downlink Switch for Shielding Forced Drop
- OMC Path
Relati onship -> Downli nk Switch for Shi eldi ng Forced Drop
This parameter indicates whether the forced call drop attri bute of the downlink load
control function is on or off. This parameter is vali d 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 threshol d; if the setting of the parameter is
enabled, the system performs forced call drop for l oad decrease when the downli nk load
reaches the overl oad threshold. By default, the settings are enabled.
4.1.2.12 Maximum Number of Degraded Downlink Load Steps Every Time
- OMC Path
Relati onship -> Maximum Number of Degraded Downlink Load Steps Every Time
This parameter specifi es the maximum number of degraded downlink load steps at a
time during t he implementation of the l oad decrease measures in the downli nk. You can
confi gure the parameter in reference to the configurati on of DRBC downlink rat e grades.
Provi ded that the number of downlink DRBC rat e 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 Downlink Forced Handover Users Every Time
- OMC Path



Relati onship -> Maximum Number of Downlink Forced Handover Users Every Time
This parameter specifi es the maximum number of subscribers in each forced handover
operation and the maximum number of radi o links can be deleted each time when the
downlink is overload.
To increase the number of subscribers in downli nk forced handover operation, increase
the setting of the parameter; to decrease the number of subscribers in downli nk forced
handover operati on, decrease the setting of the parameter. By default, the setting is 5.
4.1.2.14 Maximum Number of Downlink Forced Drop Users Every Time
- OMC Path
Relati onship -> Maximum Number of Downlink Forced Drop Users Every Time
This parameter specifi es the maximums number of subscribers in each forced call
drop operation when the downli nk is overl oad.
To increase the number of subscribers that can be disconnected in the impl ementation
of downli nk forced call drop solution, increase the setting of the parameter; to decrease
the number of subscribers that can be disconnected in t he impl ementation of downli nk
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
UlSeri ousOverLd Uplink Serious Overload Upper Limit(dB)
UlOverLd Uplink Overload Upper Limit(dB)
UlAlrmLd Uplink Overload Recoveri ng Lower Limit(dB)
DlSeri ousOverLd Downlink Serious Overload Upper Limit(%)
DlOverLd Downlink Overload Upper Limit(%)
DlAlrmLd Downlink Overload Recoveri ng Lower Limit(%)
SwitchToFach
Switch of Interacti ve Class/Background Class RAB->FACH
for Overl oad
NFach
Maximum Users of Interacti ve Class/Background Class
RAB->FACH for Overl oad



4.2.2 Configuration of R99 Load Control Parameters
4.2.2.1 Uplink Serious Overload Upper Limit(dB)
- OMC Path
Relati onship ->Upli nk Serious Overload Upper Limit (dB)
If the val ue of the uplink RTWP of the current cell exceeds this parameter, it means that
the system is in serious overl oad status and must take measures to decrease the load.
If the value of the parameter increases, it is relati vely difficult to trigger uplink serious
overload; if the value of the paramet er decreases, it is relatively easy to trigger upli nk
serious overload. By default, the setting is 62dB.
4.2.2.2 Uplink Overload Upper Limit(dB)
- OMC Path
Relati onship ->Upli nk Overload Upper Limit (dB)
The value of the uplink RTWP of the current cell exceeds this paramet er, it means that
the system is in common overload status and must take common overl oad decrease
measures to decrease the load.
If the value of the parameter increases, it is relati vely di fficult to trigger upli nk common
overload; if the value of the paramet er decreases, it is relatively easy to trigger upli nk
common overload. By default, the setting is 61dB.
4.2.2.3 Uplink Overload Recovering Lower Limit(dB)
- OMC Path
Relati onship -> Uplink Overload Recoveri ng lower Limit (dB)
This parameter indicates the lower limit of the uplink overload recovery.



If the val ue of t he uplink RTWP of the current cell is lower than this parameter, it means
that the system is not in overload status and the l oad decrease measures can be
stopped. If the value of the parameter i ncreases, it is relati vely easy to reach upli nk
overload recovery; if the val ue of the parameter decreases, it is relati vely hard to reach
uplink overload recovery status. By default, the setting is 57dB.
4.2.2.4 Downlink Serious Overload Upper Limit(%)
- OMC Path
Relati onship -> Downli nk Serious overload Upper Limit(%)
This parameter indicates the downlink overload upper threshold.
The val ue of the downlink TCP of the current cell exceeds this parameter, it means that
the system is in serious overl oad status and must take measures to decrease the load. If
the val ue of the paramet er decreases, it is relatively easy to trigger downlink serious
overload. If the val ue of the parameter increases, it is relati vely hard to trigger downli nk
serious overload. By default, the setting is 100%.
4.2.2.5 Downlink Overload Upper Limit(%)
- OMC Path
Relati onship ->Downli nk Overload Upper Li mit(%)
This parameter indicates the upper limit of the downli nk 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 tri gger downlink common overl oad; if the val ue of t he paramet er decreases, it
is relati vely easy to trigger downlink common overl oad. By default, the setting is 90%.
4.2.2.6 Downlink Overload Recovering Lower Limit(%)
- OMC Path
Relati onship ->Downli nk 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 l oad decrease measures can be
stopped. If t he value of the parameter increases, it is relati vely easy to reach downli nk
overload recovery status; if the value of the parameter decreases, it is relati vely 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
- OMC Path
Relati onship ->Switch of Interacti ve Class / Background Cl ass RAB->FACH for Overload
This parameter is the switch of migrating interacti ve/background RABs to the FACH
when the cell is in the overl oad state.
If the setting of the parameter is off, the system does not transfer the
interacti ve/background DCH/HSDPA subscribers to the FACH forcedly when overload; if
the setting of the parameter is on, the system transfers the interacti ve/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
- OMC Path
Relati onship ->Maximum Users of Interacti ve Cl ass/Background Class RAB->FACH for
Overload
This parameter specifi es the maximum number of interacti ve/background subscribers
that can be transferred to the FACH when the cell is in the overload state. To increase
the number of int eracti ve/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 interacti ve/background subscri bers 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
HsdsOverLdThr Common Overload Threshol d for HS-DSCH(%)
HsdsRecoverThr Recover Threshold for HS-DSCH Overload(%)
SwitchToFach
Switch of Interacti ve Class/Background Class RAB->FACH
for Overl oad
NFach
Maximum Users of Interacti ve Class/Background Class RAB-
>FACH for Overl oad
4.3.2 Configuration of HSDPA Load Control Parameters
4.3.2.1 Common Overload Threshold for HS-DSCH(%)
- OMC Path
Relati onship ->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 val ue of the
parameter, it means that the systems is in common overl oad 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 overl oad.
4.3.2.2 Recover Threshold for HS-DSCH Overload(%)
- OMC Path
Relati onship ->Recover Threshold for HS-DSCH Overl oad (%)
When HSDPA exists, if the downlink load of the current cell (namely TCP not used for
HS-PDSCH or HS-SCCH pl us HS-DSCH Required Power) is lower than the value of the
parameter, it means that the systems is not in common overl oad status and the common
load decrease measures can be stopped. If the value of the paramet er i ncreases, it is
relati vely easy to reach downli nk overload recovery status; if the val ue of the parameter
decreases, it is relatively hard to reach downli nk overload recovery status.



4.3.2.3 Switch of Interactive Class/Background Class RAB->FACH for Overload
- OMC Path
Relati onship ->Switch of Interacti ve Class / Background Cl ass RAB->FACH for Overload
This parameter is the switch of migrating interacti ve/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 interacti ve/background DCH/HSDPA subscribers to the FACH
forcedly when overloadi ng occurs; if the setting of the parameter is on, the system
transfers the interacti ve/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
- OMC Path
Relati onship ->Maximum Users of Interacti ve Class / Background Cl ass RAB->FACH for
Overload
This parameter specifi es the maximum number of interacti ve/background subscribers
that can be transferred to FACH when the cell is in the overl oad state. To increase the
number of interacti ve/background subscri bers that can be transferred to FACH at a time
when the cell is in the overl oad state, increase the value of the parameter; to decrease
the number of interacti ve/background subscribers that can be transferred to FACH when
the cell is in the overload state at a time,, decrease the val ue of the parameter.
4.4 HSUPA Load Control Parameters
4.4.1 HSUPA Load Control Parameter List
NServToTotalPwr Target Non-serving E-DCH to Total E-DCH Power Ratio(%)
MaxRTWP Maximum Target Recei ved Total Wideband Power(dB)



4.4.2 Configuration of HSUPA Load Control Parameters
4.4.2.1 Target Non-serving E-DCH to Total E-DCH Power Ratio(%)
- OMC Path
Management->Utran Cell->Utran Cell XXX->Modify Advanced Paramet er->Hspa
Confi guration information In A Cell-> Target Non-servi ng E-DCH to Tot al E-DCH Power
Ratio(%)
If t he 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 E-
DCH recei ve power in a non-service link of a cell over the total recei ve power of the E-
DCH is rel ati vely high, and it is very hard to trigger the mechanism of sending rel ati ve
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 E-
DCH recei ve power in a non-service link of a cell over the total recei ve power of the E-
DCH is relati vely low, and it is very easy to trigger the mechanism of sendi ng rel ati ve
grant to the UE in a non-service link.
4.4.2.2 Maximum Target Received Total Wideband Power(dB)
- OMC Path
Management->Utran Cell->Utran Cell XXX->Modify Advanced Paramet er->Hspa
Confi guration i nformation In A Cell ->Maximum Target Recei ved Total Wideband
Power(db)
The parameter speci fies the maximum target uplink i nterference for a certai n cell, and is
an offset relati ve 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 paramet er 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.



4.6 GBR Resource Consumption Limiting Parameters
4.6.1 GBR Resource Consumption Limiting Paramters List
HsGBRResLimit Idx
Limiting HSDPA GBR Resource Consumption
Index
CHsGBRResLmt Idx
Cell Limiting HSDPA GBR Resource Consumption
Index
HsGBRLimitSwi
Switch for Limiting HSDPA GBR Resource
Consumption
HsGBRLevNum
Guarant eed Bit Rat e Level Number of HSDPA
Services for Limiting HSDPA GBR Resource
Consumption
HsGBRLev[ MAX_NUM_HS
_GBR]
Guarant eed Bit Rat e Levels of HSDPA Services
for Limiting HSDPA GBR Resource Consumption
UEHsReqPwrUplim[MAX_
NUM_HS_GBR]
UE HS-DSCH Required Power Upper Limit for
4.6.2 Configuration of GBR Resource Consumption Limiting Parameters
4.6.2.1 Limiting HSDPA GBR Resource Consumption Index
- OMC Path
Path:View->Configuration Management->RNC NE->RNC Radio Resource
Management-> Limiting HSDPA GBR Resource Consumption Information->
Limiting HSDPA GBR Resource Consumption Index
Limiting HSDPA GBR Resource Consumption Index
4.6.2.2 Cell Limiting HSDPA GBR Resource Consumption Index
- OMC Path
Management-> Utran Cell->Utran Cell XXX->Modify Advanced Parameter-
>Hspa Configuration information In A Cell-> Cell Limiting HSDPA GBR
Resource Consumption Index
Cell Limiting HSDPA GBR Resource Consumption Index
4.6.2.3 Switch for Limiting HSDPA GBR Resource Consumption
- OMC Path
Management->HSPA Configuration Information-> Switch for Limiting HSDPA
GBR Resource Consumption
Switch for Limiting HSDPA GBR Resource Consumption



4.6.2.4 Guaranteed Bit Rate Level Number of HSDPA Services for Limiting HSDPA
- OMC Path
Guaranteed Bit Rate Level Number of HSDPA Services for Limiting HSDPA
This parameter is used to define Guaranteed Bit Rate Level Number of HSDPA
Services for Limiting HSDPA GBR Resource Consumption
4.6.2.5 Guaranteed Bit Rate Levels of HSDPA Services for Limiting HSDPA GBR
Resource Consumption
- OMC Path
Guaranteed Bit Rate Levels of HSDPA Services for Limiting HSDPA GBR
Resource Consumption(bps)
Those parameters is used to define Guaranteed Bit Rate Levels of HSDPA
Services for Limiting HSDPA GBR Resource Consumption
4.6.2.6 UE HS-DSCH Required Power Upper Limit for Limiting HSDPA GBR Resource
Consumption
- OMC Path
Management-> Limiting HSDPA GBR Resource Consumption Information-> UE
HS-DSCH Required Power Upper Limit for Limiting HSDPA GBR Resource
Consumption (dB)
This parameter is used to define UE HS-DSCH Required Power Upper Limit for



5 Counter And Alarm
5.1 Counter List
5.2 Alarm List
This feat ure has no relati ve alarm.
6 Glossary
C
CAC Call Admission Cont rol
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 Absol ute Grant Channel
E-RGCH E-DCH Relati ve Grant Channel
E-HICH E-DCH Hybrid ARQ Indicat or Channel
F
Counter No. Description
C310524810 Number of call drop by load control,Conversation class
C310524811 Number of call drop by load control,Interacti ve 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, Interacti ve class
C310524816 Number of rate decreased by load control,Background class
C310524817 Number of rate decreased by load control,St reaming class



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 Upli nk Packet Access
I
I/B Interacti ve/Background
L
LC Load Control
M
MBMS Multimedia Broadcast Multicast Service
R
RACH Random Access Channel
RNC Radi o Network Controll er
RTWP Recei ved Total Wide Band Power
S
SIR Signal to Interference Ratio
T
TCP Transmitted Carrier Power
U
UE User Equipment
W
WCDMA Wideband Code Di vision Multipl e Access

ZTE UMTS Overload Control Feature Guide U9.2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE UMTS Overload Control Feature Guide U9.2

Загружено:

Авторское право:

Доступные форматы

Operator Logo

Вам также может понравиться