Load Control 2

Security Level: Confidentia
Load Control Strategys

for UMTS Network
UMTS Solution Test Department
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
V2.0V1.0
88)
Huawei confidential
Contents
Perface
Load Control Algorithm Overview
Auto-Adaptive Background Noise Algorithm
Potential User Control Algorithm
Call Admission Control Algorithm
Intelligent Access Control Algorithm
Load Reshuffling Algorithm
Overload Control Algorithm
Dynamic Cell Shutdown Algorithm
Huawei Confidential
Page 3
Contents
Perface
Load Control Introduction
Load Control algorithms in different UE access phases
Load Control algorithms used on different cell load levels
Priorities Involved in Load Control
Huawei Confidential
Page 4
Load Control Introduction

Why we use load control algorithms?
The WCDMA system is a self-interfering system. As the load of the system increases, the
interference rises. A relatively high interference can affect the coverage and QoS of established
services. Therefore, the capacity, coverage, and QoS of the WCDMA system are mutually affected.
The destination of load control algotirhms

Through the control of key resources, such as power, downlink channelization codes, channel
elements (CEs), Iub transmission resources, which directly affect user experience, load control
aims to maximize the system capacity while ensuring coverage and QoS.
Differentiated services under load control algorithms

load control provides differentiated services for users with different priorities. For example,
when the system resources are insufficient, procedures such as direct admission, preemption,
redirection can be performed to ensure the successful access of emergency calls to the network.
Huawei Confidential
Page 5
Load Control algorithms in different UE access phases

Depending on the actual phase of UE access, different load control algorithms are
used, as shown in the following figure.
Before UE access: PUC
During UE access: CACIAC
After UE access: LDBLDROLC
PUC = Potential User Control

IAC = Intelligence Admission Control
CAC = Call admission control
LDB = Load Control Balancing

LDR = Load Resuffling
OLC = Overload Control
Huawei Confidential
Page 6
Load control algorithms used on different cell load levels

NodeB TX
power (noise)
Icons for different load levels
Cell load (number of subscribers)
Start OLC: check and relieve overload

congestion in cells
Start IAC: increase the access rate in cells with
heavy load by some actions while ensuring the QoS
Start PUC: enable UEs in idle mode to camp on cells with light load
Start LDR: check and relieve basic congestion in cells
Dynamically shut down or open up cells during the
effective period of the dynamic cell shutdown algorithm
Huawei Confidential
Page 7
Resources used by different load control algorithms

Resources
Load Control
Algorithm
Power
Code
NodeB Credits
Iub Bandwidth
CAC
IAC
PUC
LDB
LDR
OLC
Dynamic cell
shutdown
NOTE
: not considered
: considered
This table lists the resources that are considered by different load control
algorithms.
Huawei Confidential
Page 8
Priorities Involved in Load Control

The priorities involved in load control are user priority, Radio Access Bearer (RAB)
integrated priority, and user integrated priority.

User Priority
RAB Integrated Priority
User Integrated Priority
Huawei Confidential
Page 9
User Priority
There are three levels of user priority (1, 2, and 3), which are denoted as gold (high
priority), silver (middle priority) and copper (low priority) users. The relation between user
priority and Allocation Retention Priority (ARP) can be set through OM command; the
typical relation is shown in the following table.
ARP
10
11
12
13
14
15
User
Priority
ERROR
Note:
ARP 15 is always the lowest priority and is not configurable. It corresponds to user priority 3 (copper).
If ARP is not received in messages from the Iu interface, the user priority is regarded as copper.
The levels of user priority are mainly used to provide different QoS for different users, for example, setting
different Guaranteed Bit Rate (GBR) values for BE services according to different priority levels.Changes in
the mapping between ARP and user priority have an influence on the following features:
High Speed Uplink/Downlink Packet Access (HSUPA /HSDPA)
Adaptive Multi Rate (AMR/ AMR-WB)
Iub overbooking
Load control
Huawei Confidential
Page 10
RAB Integrated Priority

The values of RAB integrated priority are set according to the integrated priority
configuration reference parameter:
If the integrated priority configuration reference parameter is set to Traffic Class, the integrated
priority abides by the following rules:
Traffic classes: conversational -> streaming -> interactive -> background =>
Services of the same class: priority based on Allocation/Retention Priority (ARP) values, that is, ARP1 ->
ARP2 -> ARP3 -> ... -> ARP14 =>
Only for the interactive service of the same ARP value: priority based on Traffic Handling Priority (THP),
that is, THP1 -> THP2 -> THP3 -> ... -> THP14 =>
Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH service
preferred depending on the carrier type priority indicator parameter.
If the integrated priority configuration reference parameter is set to ARP, the integrated priority
abides by the following rules:
ARP: ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>
Services of the same ARP: priority based on traffic classes, that is, conversational -> streaming ->
interactive -> background =>
Only for the interactive service of the same ARP value: priority based on Traffic Handling Priority (THP),
that is, THP1 -> THP2 -> THP3 -> ... -> THP14 =>
Services of the same ARP, traffic class and THP (only for interactive services): HSPA or DCH service
preferred depending on the carrier type priority indicator parameter.
Huawei Confidential
Page 11
User Integrated Priority

For multiple-RAB users, the integrated priority of the user is based on the service of the
highest priority. User integrated priority is used in user-specific load control.
Huawei Confidential
Page 12
Contents
Perface



Huawei Confidential
Page 13

Uplink background noise is sensitive to environmental conditions. Therefore, the
LDM algorithm incorporates an auto-adaptive update algorithm to restrict the background
noise within a specified range:
If the temperature in the equipment room is constant, the background noise changes
slightly. In this case, the background noise requires no more adjustment after initial
correction.
If the temperature in the equipment room varies with the ambient temperature, the
background noise changes greatly. In this case, the background noise requires autoadaptive upgrade.
Huawei Confidential
Page 14
Contents
Perface
Potential User Control Overview
Potential User Control Triggering
Potential User Control Procedure
Huawei Confidential
Page 15
Potential User Control Overview

PUC algorithm is used to balance downlink traffic load between interfrequency cells.
This algorithm can be used for the UE which is in these state:
Idle mode
CELL_FACH
This algorithm
can used intra
RNC
CELL_PCH
URA_PCH state
Light
F2
Potential UE cell selection

or reselection
F1
Heavy
Huawei Confidential
Page 16
Potential User Control Triggering

when the load is higher
than this threshold, it
will be consider heavy
Between the heavy

threshold and light
threshold, that means
the cell state is normal.
when the load is lower

than this threshold, it
will be considered light
NOTE: PUC takes effect only in downlink.
Huawei Confidential
Page 17
Potential User Control Procedure

Depending on the load status of the current cell and neighboring cell, the cell reselection
parameters are adjustedwhich are contained in SIB3 and SIB11.In this way, potential
user in heavy load cell reselects to the light load cell.
Note: The PUC algorithm consider the load of neighboring cell, if it is in heavy state, the
adjusting will not happened.
Huawei Confidential
Page 18
Contents
Perface
Call Admission Control Overview
CAC Based on power resource
CAC Based on Code Resource
CAC Based on CE Resource
CAC Based on Iub transmission Resource
CAC Based on Number of HSPA Users
Huawei Confidential
Page 19
Call Admission Control Overview

Call Admission Control (CAC) is used to determine whether the system
resources are sufficient to accept a new user's access request. If the system
resources are sufficient, the access request is accepted; otherwise, the access
request is rejected.
The admission decision is based on the following resources:
Cell code resource
Cell power resource
NodeB credits resource
Iub transmission bandwidth resource
Number of HSDPA users (only for HSDPA services)
Number of HSUPA users (only for HSUPA services)
Note:
A call can be admitted only when all of these resources are available.
For CAC based on all the resources, uplink and downlink are independently.
Huawei Confidential
Page 20
CAC based on power resource

For power resource admission, it can based on three kinds of algorithms to suit different
application scenarios.
Algorithm 1:
Power resource admission decision based on power or interference.
Depending on the current cell load (uplink load factor and downlink transmitted carrier power)
and the access request, the RNC determines whether the cell load will exceed the threshold or not
upon admitting a new call. If yes, the RNC rejects the request. If not, the RNC accepts the
request.
Algorithm 2:
Power resource admission decision based on the number of equivalent users.
Depending on the current number of equivalent users and the access request, the RNC determines
whether the number of equivalent users will exceed the threshold or not upon admitting a new
call. If yes, the RNC rejects the request. If not, the RNC accepts the request.
Algorithm 3:
The same as the Algorithm 1, the only difference is the estimated load increment always set to 0.
Note: For power resource, regardless of which the power algorithm is used, the RRC admission threshold
is always the cell OLC threshold.
Huawei Confidential
Page 21
UL Power Admission based on algorithm 1&3for R99 cell

The procedure for uplink power admission decision for R99 cells as follows:
The RNC obtains the uplink RTWP of the cell and uses the formula:
For HUSPA cells, the

DCH UL power
admission formula is
different from R99
cells.
to calculate the current uplink load factor UL, where PN is the received uplink Background
noise.The RNC calculates the uplink load increment UL based on the service request.
For algorithm 3, UL is fixed to zero, this is the only difference between algorithm 1 and algorithm 3.
The RNC uses the following formula to predict the uplink load factor:
In the formula, ULcch is the value of the UL common channel load factor, which defines the factor
of UL common channel resources reserved.
By comparing the predicted uplink load factor UL, predicted with the corresponding threshold of
different service,the RNC decides whether to accept the access request or not.
The threshold relationship of different services is set as follows
Huawei Confidential
Page 22
Different threshold for different service

Baseline values for thresholds
Threshold
High
Threashold name
Uplink
Downlink
Overload trigger threshold
95
95
Total power threshold
83
90
AMR&non-AMR
Handover access threshold
80
85
Other services
AMR access threshold
75
80
Non-AMR access threshold
75
80
Other services access threshold
60
75
Load reshuffling trigger threshold
55
70
OLC
Total power
handover
LDR
Low
Cell power load
The thresholds and coresponding algorithms are used for resource management and keep system stability.
Meanwhile,different threshold expresses different serivce priority. When the power resource is
insufficiency, the effect of these thresholds wiill be emerge: the higher the threshold is , the easier to
access the network.
Note:
For the RRC connection request for the reason of emergency call,detach or registration, direct admission is used.
For the RRC connection request for other reasons, UL/DL OLC Trigger threshold is used for admission.
For the serivce RB setup request admission,coresponding thresholds in the table will be used.
For the service handover in admission, handover access threshold will be used.
For the service upsize reconfiguration admisson, the load reshuffling trigger threshold will be used.
Huawei Confidential
Page 23
UL Power Admission based on algorithm 1&3
for HSPA cell
The power admission for HSUPA cell. If the RSEPS measurement is deactivated, the
admission algorithm automatically changes into algorithm 2.
Type A: All UEs for which cell is the serving EDCH cell, the uplink load generated by the type A of
E-DCH scheduling services is defined by
UL,EDCH,s
Type B: all UEs for which this cell is not the serving
E-DCH cell,the uplink load generated by the type B
of E-DCH scheduling services is defined by
UL,EDCH,f ,which is fixed to zero

The uplink uncontrollable load is defined as follows:
UL,non-ctrl =UL- UL,EDCH,s- UL,EDCH,f

This result will be used to adminssion control.
Since the HSUPA scheduling algorithm consumes additional uplink power resources, the
power load of the WCDMA system is always relatively high. Therefore, the CAC algorithm
combines the PBR-based decision with the load-based decision to reduce the number of
potential erroneous rejections.
Huawei Confidential
Page 24
The PBR admission decision for HSUPA service

The PBR-based decision is used to check whether the QoS requirement of existing users
is fulfilled. The QoS is measured on the basis of the Provided Bit Rate (PBR) of the
users. If the QoS requirement is fulfilled, new users are allowed to access the network.
As shown in the previous figure, the Scheduling Priority Indicator (SPI) of a new HSUPA user
is SPINew user.
Huawei Confidential
Page 25
The PBR admission decision for HSUPA service

Decision:
The RNC admits the HSUPA

scheduling services in either of the
following cases:
For HSUPA non-scheduling

services, the RNC admits the
HSUPA non-scheduling services
in either of the following cases:
Where
Formula 1, 2, or 3 is fulfilled.
Formula 4 is fulfilled.
Formula 1, 2, or 3 is fulfilled.
Formulas 4 and 5 are fulfilled.
Note:
For HSUPA serivce, either PBR or power
resource admission descision is passed, the
serivce access will be allowed.
If the PBR measurement is deactivated, the
decision formulas that involve PBR are
regarded as unsatisfied.
Huawei Confidential
Page 26
UL Radio Admission Decision for DCH RAB (for HSPA cell)

For HSUPA cells, the DCH service admission decision in uplink is different from R99
cells.
Uncontrollable interference must be kept within a certain range. The purpose is to ensure the
stability of the system and to prevent non-scheduling services and DCH services from seizing the
resources of HSUPA services. In this regard, the CAC algorithm combines the uncontrollable part
based decision and the total loadbased decision.
When the admission of DCH services is implemented, the following formulas apply:
Where:
The RNC admits DCH services if formulas 1 and 2 are fulfilled.
Huawei Confidential
Page 27
DL Power Admission based on power algorithm 1&3 (for R99 cell)

The procedure for uplink power admission decision for R99 cells as follows:
The RNC obtains the cell downlink TCP and calculates the downlink load factor DL by dividing
the maximum downlink transmit power Pmax by this TCP.
For HSDPA cells, the
DCH DL power
admission formula is
different from R99 cells.
The RNC calculates the downlink load increment DL based on the service request and the current
load.
The RNC uses the following formula to predict the downlink load factor:
In the formula, DL_cch is the value of DL common channel load reserved coefficient, which defines
the factor of DL common channel resources reserved.
By comparing the downlink load factor DL,predicted with the corresponding threshold, the RNC
decides whether to accept the access request or not.
Note: The downlink threshold for different service see the uplink part.
Huawei Confidential
Page 28
DL PowerAdmission based on Algorithm 1&3
(for HSPA Cells)
Power Increment Estimation for DCH RAB
The power increment estimation for the DCH RAB in the HSPA cell is similar to the DCH RAB
in the R99 cell.
Power Increment Estimation for HSDPA RAB
The power increment estimation for HSDPA RAB PDL is made on the basis of GBR, Ec/N0,
non-orthogonal factor, and so on.
For algorithm 3, PDL is fixed to zero, this is the only difference between algorithm 1 and algorithm 3.
The detailed information
NEXT PAGE
Huawei Confidential
Page 29
DL Radio Admission Decision for DCH RAB (for HSPA cell)

When the admission of the DCH RAB is implemented in the HSDPA cells, the following
formulas apply:
Where:
Decision:
The RNC admits the DCH RAB in
either of the following situations:
Note:
If the GBP measurement is deactivated, the GBP
involved in the decision formulas is set to 0.
Huawei Confidential
Page 30
Downlink Radio Admission Decision for HSDPA RAB

Decision:
The RNC admits the HSDPA

streaming RAB in any of the following
situations:
The RNC admits the HSDPA BE RAB

in any of the following situations:
Where
Note:
If the GBP measurement is deactivated, the GBP

involved in the decision formulas is set to 0.
If the PBR measurement is deactivated, the

decision formulas that involve PBR are regarded
as dissatisfied.
For the first HSDPA service accessing the cell, the

decision formulas that involve PBR are regarded
as unsatisfied.
Huawei Confidential
Page 31
Power admission decision based on algorithm 2

Definition
The 12.2 kbit/s AMR traffic is used to calculate the Equivalent Number of Users (ENU) of all other
services. The 12.2 kbit/s AMR traffic's ENU is assumed to be 1.
Admission procedure
The RNC obtains the total ENU of all existing users ENUtotal = all_exist_userENUi.
The RNC gets the ENU of the new incoming user ENUnew.
The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU load, where ENUmax is the
configured maximum ENU.
By comparing the forecasted ENU load with the corresponding threshold, the RNC decides whether to accept
the access request.
Different threshold parameters is set

for different types of service
For example, the admission of a new AMR
service in the uplink based on algorithm 2
will be successful if the following formula is
fulfilled:
(ENUtotal + ENUnew)/ENUmax UL threshold
of Conv AMR service
Service Type
Admission Threshold
UL DCH/HSUPA
UL threshold of Conv AMR service

UL threshold of Conv non_AMR service
UL threshold of other services
UL Handover access threshold
DL DCH
DL threshold of Conv AMR service

DL threshold of Conv non_AMR service
DL threshold of other services
DL Handover access threshold
HSDPA
DL total power threshold
Huawei Confidential
Page 32
Typical Equivalent Number of Users

Typical equivalent number of users (with activity factor to be 100%)
Service
ENU
Uplink for DCH
Downlink for DCH
HSDPA
HSUPA
3.4 kbit/s SIG
0.44
0.42
0.28
1.76
13.6 kbit/s SIG
1.11
1.11
0.74
1.89
3.4 + 12.2 kbit/s
1.44
1.42
3.4 + 8 kbit/s (PS)
1.35
1.04
0.78
2.26
3.4 + 16 kbit/s (PS)
1.62
1.25
1.11
2.37
3.4 + 32 kbit/s (PS)
2.15
2.19
1.70
2.60
3.4 + 64 kbit/s (PS)
3.45
3.25
2.79
3.14
3.4 + 128 kbit/s (PS)
5.78
5.93
4.92
4.67
3.4 + 144 kbit/s (PS)
6.41
6.61
5.46
4.87
3.4 + 256 kbit/s (PS)
10.18
10.49
9.36
6.61
3.4 + 384 kbit/s (PS)
14.27
15.52
14.17
9.36
In the upon table, for a 3.4+n kbit/s service of HSDPA or HSUPA
???
3.4 kbit/s is the rate of the signaling carried on the DCH.

n kbit/s is the GBR of the BE service, and the MBR of the RT service.
When calculate ENUs in RNC, the formula will be used: ENUi*AFi.

ENUi is the total equivalent number of different user priority users, as show in upon table;
AFi is the active factor for different user priority users;
Huawei Confidential
Page 33
CAC Based on Code Resource
When a new service attempts to access the network, code resource admission is mandatory.
Code resource admission is implemented as follows:
For RRC connection setup requests, the code resource admission is successful if the current
remaining code resource is enough for the RRC connection.
For handover services, the code resource admission is successful if the current remaining code
resource is enough for the service.
For other R99 services, the RNC has to ensure that the remaining code does not exceed the
configurable OM threshold (Dl HandOver Credit and Code Reserved SF) after admission of the new
service.
For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore, the
code resource admission is not needed.
For R99 PS BE serivce upsizing reconfiguration, the Cell LDR SF reserved threshold will be used.
Note: The spread factor code consume law and admission algorithm are similar to Node B credit resource,
coresponding content see CAC based on Node B Credit part.
Huawei Confidential
Page 34
CAC based on Node B Credit

Definition
CE stands for Node B credit on the RNC side and for Channel Element on the NodeB side. It
is used to measure the channel demodulation capability of the NodeBs.
How to calculate the CE resource

The resource of one equivalent 12.2 kbit/s AMR voice service, including 3.4 kbit/s signaling on the
Dedicated Control Channel (DCCH), consumed in baseband is defined as one CE.
one 12.2 kbit/s AMR voice service consumes one uplink CE and one downlink CE.If there is only
3.4 kbit/s signaling on the DCCH but no voice channel, one CE is consumed.
Channel elements provide either uplink or downlink capacity for services. There are two kinds of
CE.
Huawei Confidential
Page 35
CAC based on Node B credit resource

When a new service tries to access the network, the credit resource admission is
implemented as follows:
For an RRC connection setup request, the credit resource admission is successful if the
current remaining credit resources of the local cell, local cell group (if any), and NodeB are
sufficient for the RRC connection.
For a handover service, the credit resource admission is successful if the current remaining
credit resources of the local cell, local cell group (if any), and NodeB are sufficient for the service.
For other services, the RNC has to ensure that the remaining credit of the local cell, local
cell group (if any), and NodeB does not exceed the configurable OM thresholds ( Ul HandOver Credit
Reserved SF/Dl HandOver Credit and Code Reserved SF) after admission of the new services.
For R99 PS BE serivce upsizing configuration, the LDR reserved threshold will be used.
Notes:
The credit resource admission is implemented in the uplink and downlink respectively.
For detailed information about local cell, local cell group, and capacity consumption law, refers to the
3GPP TS 25.433.
Huawei Confidential
Page 36
SF&CE DCH consume law

Stage
Uplink
Rate
Downlink
(kbit/s)
SF
Number of CEs
Consumed
Corresponding
Credits Consumed
SF
Number of CEs
Consumed
Corresponding
Credits Consumed
3.4
256
256
13.6
64
128
64
128
16
64
128
32
32
1.5
64
64
16
32
128
10
16
144
10
16
256
10
20
384
10
20
AMR
4.75
128
128
AMR
12.2
64
128
RRC
RAB
Note: For each rate and service, the number of UL credits is equal to the number of UL CEs multiplied by 2.
Huawei Confidential
Page 37
SF&CE HSUPA consume law

Uplink
Rate (kbit/s)
SF
Number of CEs Consumed
Corresponding Credits Consumed
64
16
64
32
32
1.5
64
32
1.5
128
16
144
16
256
10
384
10
20
608
10
20
1450
2SF4
16
32
2048
2SF3
32
64
2890
2SF2
32
64
5760
2SF2+2SF4
48
96
Note: There is no capacity consumption law for HS-DSCH in 3GPP TS 25.433, so certain credits
are reserved for HSDPA RAB, and credit admission for HSDPA channel is not needed.
Huawei Confidential
Page 38
CAC Based on Iub transmission Resource
When a new service accesses the network, Iub interface resource admission is mandatory.
For the transmission admission control in Iub interface, as shown in the Figure, bottom-up MultiLevel Admission Control Policy is used.
A user accessing the network from a path should go through the admission of the path,
resource group, and physical port in turn. The user that passes all the admission can be
successfully admitted by the transport layer.
Physical link users consist of R99 users and HSPA users.

For R99 users, the UL and DL control admission together.
For HSPA users, the UL and DL control admission separately.
For BE service Iub

admisssion ,the GBR
rate is used.
First the UL controls admission. If the UL admission for HSPA users is approved, the DL
controls admission and if the UL admission for HSPA users is rejected, the DL does not
control admission.
Huawei Confidential
Page 39
Bandwidth Reserved for Services

The RNC calculates the reserved bandwidth based on the activity factor and performs
admission control based on the reserved bandwidth. Different services use different policies.
RT services, including conversational and streaming services, are admitted at the Maximum
Bit Rate (MBR).
Reserved bandwidth for admission of an RT service = MBR * Activity factor, where the activity factor needs to be
set for each type of service.
NRT services, including interactive and background services, are admitted at the GBR.
Reserved bandwidth for admission of an NRT service = GBR * Activity factor
SRB services can be admitted at the GBR or 3.4 kbit/s.

Admission at 3.4 kbit/s: The bandwidth is fixed at 3.4 kbit/s. This admission mode is applicable to R99, HSDPA,
and HSUPA services.
Admission at the GBR: For R99 services, if the bandwidth of a transport channel varies between 3.4 kbit/s and 13.6
kbit/s, resource allocation and resource admission do not need to be performed again.
Reserved bandwidth for admission of SRB = 3.4k * Activity factor
In terms of common channels, EFACH services are admitted at the GBR, and other
common channel services are admitted at the MBR.
Reserved bandwidth for admission of EFACH = GBR * Activity factor

Reserved bandwidth for admission of other common channel = MBR * Activity factor
Note: The activity factor can be set for different services relatively. The forward and backward activity factors can
congured independently!
Huawei Confidential
Page 40
IUB bandwidth admission desicion

For a new user, the following requirements apply:
Total bandwidth allocated to the users on the path + required bandwidth for the new user < total bandwidth
configured for the path bandwidth reserved for handover.
Total bandwidth allocated to the users on the physical link + required bandwidth for the new user < total
bandwidth of the physical link bandwidth reserved for handover.
For a handover user, the following requirements apply:
Total bandwidth allocated to the users on the path + required bandwidth for the handover user < total bandwidth
configured for the path.
Total bandwidth allocated to the users on the physical link + required bandwidth for the handover user < total
bandwidth of the physical link.
For a rate upsizing user, the following requirements apply:
Total bandwidth allocated to the users on the path + required bandwidth for the rate upsizing user < total
bandwidth configured for the path congestion threshold.
Total bandwidth allocated to the users on the physical link + required bandwidth for the rate upsizing user < total
bandwidth of the physical link congestion threshold.
Threshold
High
The forward and backward bandwidth

thresholds are set respectively. Also,
different level bandwidth threshold can be
set separately.
Total bandwidth
Handover resovered bandwidth
Congestion bandwidth
Congestion clear bandwith
Low
Path/resource group/phycial port
Huawei Confidential
Page 41
IUB bandwidth admission procedure
Primary and secondary paths are used in admission control. According to the mapping between traffic
types and transmission resources, the RNC first selects the primary path for admission. If the
admission on the primary path fails, then the admission on the secondary path is performed.
The user tries to be admitted to available bandwidth 1 of the primary path, as shown in the Figure. The
procedure is as following:
If the admission on the primary path is successful, the user is carried on the primary path.
If the admission on the primary path fails, the user tries to be admitted to available bandwidth 2 of the secondary
path.
If the admission on the secondary path is successful, the user is carried on the secondary path. If not, the
bandwidth admission request of the user is rejected.
Admission decision for a new user :

For a new user
admission,
bandwidth for
handover users
is reseved
Available bandwidth 1 = total bandwidth of the primary path - used bandwidth - handover reserved bandwidth
Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth - handover reserved bandwidth
Huawei Confidential
Page 42
IUB bandwidth admission procedure

Admission procedure for a handover user
For handover users
admission,
allocation of the
bandwidth is 100%!
Available bandwidth 1 = total bandwidth of the primary path - used bandwidth

Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth
Admission procedure for a rate upsizing user

For rate upsizing
users admission,
congestion reserved
bandwidth is reserved
Available bandwidth 1 = total bandwidth of the primary path - used bandwidth - congestion reserved bandwidth
Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth - congestion reserved bandwidth
Note: Therefor, the serivce priority is: handover users > new users> rate upsizing users
Huawei Confidential
Page 43
CAC Based on the Number of HSPA Users

CAC of HSDPA Users
When a new HSDPA service attempts to access the network, the algorithm admits the
service if the following conditions are met:
The number of HSDPA users in the cell does not exceed the maximum value specified by
MaxHsdpaUserNum.
The number of HSDPA users in the NodeB does not exceed the maximum value specified by
NodeB HsdpaMaxUserNum.
Otherwise, the algorithm rejects the service request.
CAC of HSUPA Users

When a new HSUPA service attempts to access the network, the algorithm admits the
service if the following conditions are met:
The number of the HSUPA users in the cell does not exceed the maximum value specified by
MaxHsupaUserNum.
The number of the HSUPA users in the NodeB does not exceed the maximum value specified by
NodeB HsupaMaxUserNum.
Otherwise, the algorithm rejects the service request.
Huawei Confidential
Page 44
Contents
Perface
Intelligence Access Control Overview
IAC During RRC Setup Stage
IAC During RAB Setup Stage
IAC for Emergency Calls
Huawei Confidential
Page 45
Intelligence Access Control Algorithm

IAC algorithm is used to increase the access success ratio with the current
QoS guaranteed through Rate Negotiation, Directed Retry Decision(DRD),
Preemption, Queuing and BE service Low-Rate Access.
RRC IAC
RAB Rate
Negotiation
RAB Directed
Retry Decision
RAB
preemption
Huawei Confidential
RAB
queuing
Page 46
Low-Rate
Access
Intelligence Access Control Overview

RRC connection processing
Access from another cell
RRC
connection
request
Servicebased RRC
redirection
Access from
current cell
Admission
algorithm
Fails
DRD
Succeeds
Fails
Lead UE to
another cell
Redirection
Succeeds
RAB processing
RAB setup request
Yes
No
Is there any
cell not tried?
Fails
Fails
Succeeds
DRD
algorithm
Service
steering DRD
Load balancing
DRD
Target cell
selected
Rate
negotiation
Admission
algorithm
PS domain:
maximum rate
Power
admission
PS and CS
domains:
initial rate
Succeeds
Code admission
Fails or not supported

Succeeds
Queuing
Low-rate
access
Succeeds
Iub resource
admission
PS domain:
GBR of PS
RT service
Credit admission
Target Rate
Negotiation
HSPA user
number admission
Preemption
Huawei Confidential
Succeeds
Service request
accepted
Service request
denied
Page 47
IAC procedure supported by different services

Service
Type
LowRate
Access
Rate Negotiation
Preempti
on
MB
R
Nego
tiatio
n
GBR
Nego
tiatio
n
Initial
Rate
Negotiat
ion
Target
Rate
Negotia
tion
Queuin
g
DRD
InterFreque
ncy
Inte
rRA
T
DCH
HSUPA
HSDPA
Note: MBR stands for maximum bit rate

Huawei Confidential
Page 48
IAC During RRC Setup Stage

RRC
Redirection
for Service
Steering
In the RRC connection setup stage, there are

three actions for intelligence access control
algorithm:
During the RRC connection setup, the
RNC implements service steering
between inter-frequency or inter-RAT
cells according to the cause of RRC
connection setup.
IAC during
RRC
Setup
RRC
Redirection
After DRD
Failure
RRC Direct
Retry
Decision
If the RRC CAC fails, RNC selects

inter-frequency, but intra-band blind
neighboring cells to do RRC DRD;
If RRC DRD fails, select interfreq/inter-RAT blind neighboring cells
to do redirection action;
For emergency call, different strategy is used for the RRC setup IAC !
Huawei Confidential
Page 49
RRC Redirection for Service Steering

During the RRC connection setup, the RNC implements service steering between interfrequency or inter-RAT cells according to the cause of RRC connection setup. The procedure
of RRC redirection for service steering is as follows:
If the switch of RRC direction for service steering (RedirSwitch) is set to

ONLY_TO_INTER_FREQUENCY or ONLY_TO_INTER_RAT, based on the cell load and the
redirection factors, RNC decides whether to perform RRC redirection for service
steering acconding to the cause of the service requested by UE and the capability of
UE. If the switch is off or the RNC fails to determine the service type, the RNC
handles the RRC connection setup request of the UE in the current cell.
Based on the setting of Redirection Switch, the RNC takes the corresponding actions:
If RedirSwitch is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an RRC

CONNECTION REJECT message to the UE, redirecting the UE to the destination
frequency carried in the message. .
If RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION

REJECT message to the UE. The message carries the information about inter-RAT
neighboring cells.
Huawei Confidential
Page 50
RRC Redirection for load balancing

In addition, the RNC considers the load of the cell for access and the redirection factors
to control the degree of load balancing.
If the cell is normal, the RNC generates a random number between 0 and 1 and
compares it with the corresponding unconditional redirection factor. If the random
number is smaller than this factor, the RNC performs the redirection action
according to the setting of Redirection Switch . Otherwise, the RNC handles the
RRC connection setup request of the UE in the current cell.
If the cell is in the basic congestion or overload state, the RNC generates a random
number between 0 and 1 and compares it with the corresponding LDR-triggered
redirection factor. If the random number is smaller than this factor, the RNC
performs the redirection action according to the setting of Redirection Switch .
Otherwise, the RNC handles the RRC connection setup request of the UE in the
current cell.
Note: The RRC redirection action needs inter-frequency or inter-RAT blind neighboring cells. If
this condision dont meet, the RRC redirection will not happened.
Huawei Confidential
Page 51
RRC DRD after CAC failure

If the RRC setup is CAC failure as the resource insufficient, and the RRC DRD
switch is open, the following procedure will be implemented:
The RNC selects intra-band inter-frequency neighboring cells of the current
cell. These neighboring cells are suitable for blind handovers.
The RNC generates a list of candidate DRD-supportive inter-frequency cells
according to the singal quality.
The RNC selects a target cell from the candidate cells for UE access. If the
candidate cell list contains more than one cell, the UE tries a cell randomly.
If the admission is successful, the RNC initiates an RRC DRD procedure.
If the admission to a cell fails, the UE tries admission to another cell in the
candidate cell list. If all the admission attempts fail, the RNC makes an RRC
redirection decision.
If the candidate cell list does not contain any cell, the RRC DRD fails. The
RNC performs the next step, that is, RRC redirection.
Note: If the RRC DRD switch is closed, the RRC redirection action based on RRC CAC
failure will be performed.
Huawei Confidential
Page 52
RRC Redirection After DRD Failure

The RNC performs the following steps when the RRC DRD swtich is off for the RRC DRD
procedure fails:
The RNC selects all intra-band inter-frequency neighboring cells of the current cell as the candidate
cells.
The RNC selects a cell from candidate cells. The candidate cells are the cells selected in step 1 but
exclude the cells that have carried out inter-frequency RRC DRD attempts.
If more than one candidate cell is available, the RNC selects a cell randomly and redirects the UE to
the cell.
If no candidate cell is available,
If the switch of RRC redirection after DRD failure is set to Only_To_Inter_Frequency, the RRC connection
setup fails.
If the switch of RRC redirection after DRD failure is set to Allowed_To_Inter_RAT, then:
If a neighboring GSM cell is configured, the RNC redirects the UE to that GSM cell.
If no neighboring GSM cell is configured, the RRC connection setup fails
Note: If the RRC recirection switch is OFF, then the RRC Connection procedure stage fails.
Huawei Confidential
Page 53
IAC During RAB Setup Stage

During the RAB setup stage, several IAC actions will be attempted orderly to
increase the access success radio:
RAB Rate Negotiation
RAB Direct Retry Decision(DRD)
RAB Preemption
RAB Queuing
RAB Low-Rate Access for BE service
RAB IAC actions work as following:
RAB Rate
Negotiation
RAB Direct
Retry
Decision
RAB
Preemption
RAB
Queuing
Low-Rate
Access
Service access success
Huawei Confidential
Page 54
Service Access
Failure
RAB Rate Negotiation

Maximum rate negotiation
When setting up, modifying, or admitting a PS service, and the 'Alternative RAB Parameter Values' of IE is present in the
RANAP RAB ASSIGNMENT REQUEST or the RELOCATION REQUEST message, the RNC and the CN negotiate the rate
according to the UE capability to obtain the maximum expected rate while ensuring a proper QoS.
GBR rate negotiation

During the setup, modification, or handover of real-time PS services, if the RAB assignment message includes multiple
alternative guaranteed bit rates, the RNC selects the smallest one as the negotiated guaranteed rate and responds to the CN.
Initial rate negotiation

For a non-real-time service in the PS domain, the RNC selects an initial rate to allocate bandwidth for the service before
the cell resource request.The negotiation is based on the cell load information, which includes:
Uplink and downlink radio bearer status of the cell
Minimum spreading factor supported
HSPA capability
Target rate negotiation

For a non-real-time service in the PS domain, if cell resource admission fails, the RNC chooses a target rate to allocate
bandwidth for the service based on cell resource in following cases:
Service setup
Soft handover
DCCC rate upsizing
Huawei Confidential
Page 55
RAB DRD for service steering

After receiving a Radio Access Network Application Part (RANAP) message RAB
ASSIGNMENT REQUEST, the RNC initiates an RAB DRD procedure to select a suitable cell for
RAB processing according to the cell service property.
Service priority group

HSPA cell
R99 cell
Before DRD
Service priority of R99 RT service

Service priority of R99 NRT service
Service priority of HSDPA service

Service priority of HSUPA service
Service priority of Other service
HSPA cell
HSPA cell
The SPG(service priority

group) is used to set different
priorities for different types of
service. Huawei can support 8
SPGs on RNC. For each
SPG,there are 0~7 priorities
for each type of serivce, 7 is
the highest and 0 is the
lowest,which means that the
SPG can not support the
specific type of service.
R99 cell
R99 cell
During DRD
After DRD
Note: The SPG can configure for each cell. In this way, different cell can support different service.
This network strategy is used to the scenarios which some old equipments cant support HSPA function.
Huawei Confidential
Page 56
Load balance direct retry

If the UE requests a service setup or channel reconfiguration in an area covered by multiple frequencies,
the RNC sets up the service on a carrier with a light load to achieve load balancing among the cells on the
different frequencies.
If there is no load balance algorithm, the
load of multiple frequencies performed as
the illustration. one cell has many
HSDPA users, and another cell has many
R99 users.The downlink resource usage
of the cell cant reach the maximum.
Cell B
Cell A HSPA+R99
Cell A
Cell B HSPA+R99
load
Load of HS-DSCH require power(GBP)
Load of Non-HSDPA power
If we use the load balance algorithm,the

HSDPA users and R99 users in different
cells are averaged. The downlink resource
usage of the cell can reach the maximum.
Cell B
Cell A
Cell A HSPA+R99
Cell B HSPA+R99
load
Load of HS-DSCH require power(GBP)
Load of Non-HSDPA power
Note: Huawei recommend that opening the load balance direct retry function in live network When
there have multiple frequencies cover the same area.
Huawei Confidential
Page 57
Detailed information for load balance DRD algorithm

Algorithm 1
The load balancing DRD is performed according to the cell measurement values about the DL non-HSDPA
power and DL HS-DSCH required power.
For DCH service, the RNC sets up the service on a carrier with a light load of non-HSDPA power to achieve load
balancing among the cells on the different frequencies.
For HSDPA service, the RNC sets up the service on a carrier with a light load of HS-DSCH required power to
achieve load balancing among the cells on different frequencies.
Algorithm 2
The load balancing DRD is performed according to the DCH Equivalent Number of Users (ENU) and
HSDPA user number.
For DCH service, the RNC sets up the service on a carrier with a light load of DCH ENU to achieve load balancing
among the cells on different frequencies.
For HSDPA service, the RNC sets up the service on a carrier with a light load of HSDPA user to achieve load
balancing among the cells on different frequencies.
The effect of the algorithm as shown in the previous page:
Cell B has a lighter load of non-HSDPA power than Cell A. If the UE requests a DCH service in Cell A, preferably,
the RNC selects Cell B for the UE to access.
Cell A has the lighter load of HS-DSCH required power than Cell B .If the UE requests an HSDPA service in Cell B,
preferably, the RNC selects Cell A for the UE to access.
Note:
The calculation of the DCH Equivalent Number of Users is the same as rules of call admission control part.
Huawei Confidential
Page 58
Inter-Frequency DRD due to CAC failure

The precondition is that it is covered by multiple frequencies when the UE
requests a service in an area.The RNC selects a suitable cell in candidate cell. The
CAC algorithm makes an admission decision based on the resource status of the cell.
If the admission attempt is successful, the RNC initiates an inter-frequency blind
handover to the cell.
If the admission attempt fails, the RNC removes the cell from the candidate cells and
then checks whether all candidate cells are tried.
If there is any candidate cell not tried, the algorithm goes back to try this cell.
If all candidate cells haven been tried, then:
If the service request is an HSPA one, the HSPA request falls back to a DCH one. Then, the
algorithm goes back to step 1 to retry admission based on R99 service priorities.
If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
Note: If there is no inter-frequency neighboring cells exist or the inter-frequency handover

procedure is failure for all the attempts, the inter-RAT DRD may be happened.
Huawei Confidential
Page 59
Inter-RAT DRD due to CAC failure

When all admission attempts for inter-frequency DRD during RAB processing fail, the
RNC determines whether to initiate an inter-RAT DRD.
The inter-RAT DRD procedure is as follows:
If the current cell is configured with any neighboring GSM cell suitable for blind handover,
and the RNC performs this action.
The RNC generates a list of candidate DRD-supportive inter-RAT cells that fulfill the
singal quality requirement.
The service request then tries admission to a target GSM cell in order of blind handover
priority.
Note: If there is no suitable handover cells exist or the inter-RAT handover procedure is failure
for all the attempts, the service request undergoes preemption and queuing.
Huawei Confidential
Page 60
RAB preemption
Why we use preemption function
Preemption guarantees the success in the access of a higher-priority user by forcibly
releasing the resources of a lower-priority user. We support the preemption scenarios in
following cases:
Setup or modification of a service
Hard handover or SRNS relocation
UE state transits from CELL_FACH to CELL_DCH
Preemption preconditions
RNC performs preemption if the following conditions are met:
New serivce have the preemption capacity
The destination service can be preempted
User priority are satisfied.
1
USER
High
K
USER
USER
VIP USER
USERS
USER
Low
User Integration priority
Huawei Confidential
END
Page 61
Preemption of different service on different resources

Service
Resource
R99 service
HSDPA service
HSUPA service
Service That can Be Preempted

R99
HSUPA
HSDPA
R99 + HSPA Combined
Code
Power
CE
Iub bandwidth
Code
Power
CE
Iub bandwidth
Number of users
Code
Power
CE
Iub bandwidth
Number of users
Note: The preemption function is controlled by corresponding algorithm switch on the RNC.
Huawei Confidential
Page 62
RAB Queuing
After the admission of a service fails, the service request is put into a specific queue
to increase the access success radio. Admission attempts for the service request are made
periodically during a defined period of time.
When timer expires, select the
request with the highest
integrate priority for an attempt
of resource allocation.
NEW
USER
1
USER
USER
Heartbeat
timer
3
USER
USERS
N
USER
END
Queue
Note:
RNC performs queuing when the service has the queue capacity.
The Preemption and queuing capacity is difined in RANAP RAB ASSIGNMENT
REQEST message on the IU interface.
Huawei Confidential
Page 63
Detailed information for RAB Queuing

When a new queuing request is received, the queuing algorithm will do some decision:
If the queue is not full, then the queqing algorithm will put this request into the quque and start the
heartbeat timer if it is not started.
If the queue is full, then the queuing algorithm check out whether there are have requests whose
intergate priorities are lower than that of new request
If yes, then preemption occurs in the queue,that is lower request are took out and
rejected,New request are put into the queuing.
If no,then the queing algorithm rejects the new request directly.
After the heartbeat timer(500ms) expires, the queuing algorithm proceeds as follows:
Rejects the request which the actual waiting time of is longer than the value of the Max queuing
time length parameter.
Selects the request with the highest integrate priority for an attempt of resource allocation.
If the attempt is successful, the heartbeat timer is restarted for the next processing upon
expiry of this timer.
If the attempt fails, the queuing algorithm puts the service request back into the queue with
the time stamp unchanged for the next attempt.
Huawei Confidential
Page 64
Low-Rate Access of the PS BE Service

If a preemption or queuing failure, the PS BE service can access the target cell at a low
rate to increase the access success rate. Low-rate access means access from the DCH at 0
kbit/s, FACH, or enhanced FACH (E-FACH).
Low-rate access is used in the following scenarios:
RAB setup
Hard handover or relocation
After an appropriate access action is determined, the service attempts to access the
network
If the action of access from the DCH at 0 kbit/s is determined, the service attempts to access
the network at 0 kbit/s for traffic and at the normal rate for signaling.
If the action of access from the FACH/E-FACH is determined, the service attempts to access
the network from the FACH/E-FACH.
If the access attempt fails, this service is rejected.

For the service that accesses the network at 0 kbit/s, the rate up timer is started after the
service rate fails to increase for the first time. If the rate fails to increase even when the timer
expires, the service is released, and the connection is also released for a single service.
Huawei Confidential
Page 65
Low-rate access actions in different scenarios

Scenario
RAB setup
Combined
services
Scenario Description
FACH/E_FACH
DCH at 0 kbit/s
The RRC connection is set up on the FACH or E-FACH.
The RRC connection is set up on the DCH.
The RRC connection is set up on the HSPA channel.
Hard handover or relocation is performed for the CS+PS

combined services.
(Note 1)
Hard handover or relocation is performed for the PS+PS

combined services.
The CS service is set up, and a new PS service is to be set up.
The existing PS service is set up on the FACH/E-FACH, and a

new PS service is to be set up.
The existing PS service is set up on the DCH, and a new PS

service is to be set up.
The existing PS service is set up on the HSPA channel, and a

new PS service is to be set up.
(Note 2)
The PS service is set up, and a new CS service is to be set up.
Note:
Note 1: In this scenario, only the PS service can be admitted at 0 kbit/s.

Note 2: In this scenario, the new PS service can be admitted at 0 kbit/s, and the existing service are not affected.
Huawei Confidential
Page 66
IAC for Emergency Calls (RRC setup stage)

To guarantee successful access of emergency calls, the RNC takes special measures for
emergency calls.
Resource admission in RRC setup stage
For power resource, the emergency call is admitted regardless of whether the CAC algorithm is
enabled or not..
For hard resources (that is, code, Iub, CE), preemption will always happened due to admission
failure.
RRC connection
setup request
Admission
algorithm
Fails
Succeeds
Fails
Preemption
Succeeds
Fails
DRD
Redirection
Succeeds
RAB process
Note: To guarantee a successful admission of an emergency call, the RNC does not
perform RRC redirection for service steering.
Huawei Confidential
Page 67
IAC for Emergency Calls (RAB setup stage)

Resource admission in RAB setup stage
For power resource, when the admission switch for emergency call is enabled, power-based
admission fails if the system is in the overload congestion state. Otherwise, the admission
succeeds.
For hard resources (that is, code, Iub, and CE), the resource-based admission is successful if the
current remaining resources are sufficient for the request. Otherwise, the admission fails.
Preemption procedure
The emergency calls that trigger preemption have the highest priority, the preempted users have
the lowest priority.
preemption is performed regardless of whether the preempt algorithm is enabled or not.
The range of users that can be preempted is specified by the specific switch, that is whether the
emergecy call can preempt the users which have preemption-prohibited attribute.
Note: The emergency calls can only preempt the non-emergency users.
Huawei Confidential
Page 68
Contents
Perface
Load Reshuffling Algorithm Overview
Load reshuffling triggering
Load reshuffling actions

Huawei Confidential
Page 69
Load Reshuffling Algorithm Overview

When the usage of cell resource exceeds the basic congestion triggering threshold, the
cell enters the basic congestion state. In this case, LDR is required to reduce the cell load
and increase the access success ratio.
Four resources can trigger the basic congestion of the cell:
power resource,
code resource,
Iub resource,
NodeB credit resource.
Load reshuffling algorithm procedure has three stages, that is:
Basic Congestion Triggering
LDR Procedure
LDR Actions
Tiggering style
For power resource, the RNC performs periodic measurement and checks whether the
cells are congested.
For code, Iub, and NodeB credit resources, event-triggered congestion applies, that is,
the RNC checks whether the cells are congested when resource usage changes.
Huawei Confidential
Page 70
LDR Triggering for power resource

For an R99 cell:
If the current UL/DL load of the R99 cell is higher than or equal to the basic congestion trigger
threshold in UL/DL for 1000ms, the cell works in the basic congestion state.
If the current UL/DL load of the R99 cell is lower than the UL/DL LDR Release threshold for
1000ms, the cell returns to the normal state.
For an HSPA cell:

In the uplink, the object to be compared with the associated threshold for decision is the
uncontrollable load.
In the downlink, the object to be compared with the associated threshold for decision is the sum
of the non-HSDPA power and the Power Requirement for GBR (GBP).
Huawei Confidential
Page 71
LDR Thresholds for power resource

When the cell enters the basic
congestion state, the maximum
target rate is GBR for BE RAB.The
rate upsizing exceed GBR is
forbidden!
Threshold
High
OLC
Total power
LDR state
Handover access
AMR&non-AMR
Other services
LDR trigger
LDR release
Normal state
Threshold Name
Uplink
Downlink
Overload trigger threshold
95
95
Overload release threshold
85
85
Total power threshold
83
90
Handover access threshold
80
85
AMR access threshold
75
80
Non-AMR access threshold
75
80
Other services access threshold
60
75
Load reshuffling trigger threshold
55
70
Load reshuffling release threshold
45
60
Low
Cell power load
They are baseline values of

coresponding threshold in huawei
RNC.These valuses are not
recommended modified in live
network, but can be modified in the
testbed to help testing easier when
verify the load control algorithms.
Huawei Confidential
Page 72
LDR Triggering for Code Resource

Congestion control algorithm based on code resource can be enabled through the
specific parameter on RNC Local Maintenance Terminal.
If the SF corresponding to the current remaining code of the cell is larger than Cell
LDR SF reserved threshold, code congestion is triggered.
When the code resource congestion triggered, that means the spread code resource
is insufficient, and the access success raido maybe lower than the normal state.
Note: Only the downlink spread code may be insufficient and triggerr the code resource load
reshuffling, the code in uplink always sufficient and never trigger the LDR state.
Huawei Confidential
Page 73
LDR Triggering for Node B Credit Resource

The basic congestion for NodeB credit is of the following types:
Type A: Basic congestion at local cell level
If the cell UL/DL current remaining SF (mapped to credit resource) is higher than UL LDR
Credit SF reserved threshold/DL LDR Credit SF reserved threshold, credit congestion at cell
level is triggered.
Type B: Basic congestion at local cell group level (if any)

The same as the basic congestion at Node B level.
Type C: Basic congestion at NodeB level

If the cell group or NodeB UL/DL current remaining SF (mapped to credit resource ) is higher
than UL LDR Credit SF reserved threshold/DL LDR Credit SF reserved threshold, credit
congestion at cell group or NodeB level is triggered.
Note: When RNC performs Load reshuffling actions for the CE reource, the range of UEs to be
sorted by priority is different from other resources, all the UEs in the normal-state cells that belong to the
cell group or NodeB will be sorted based on the integrated priority.
Huawei Confidential
Page 74
LDR Triggering for Iub Bandwidth Resource

Congestion detection can be triggered in any of the following conditions:
Bandwidth adjustment because of resource allocation, modification, or release
Change in the configured bandwidth or the congestion threshold
Fault in the physical link
Assume that the forward parameters of a port for congestion detection are
defined as follows:
Configured bandwidth: AVE
Forward congestion threshold: CON
Forward congestion clear threshold: CLEAR (Note that CLEAR is greater than CON.)
Used bandwidth: USED
Then, the mechanism of congestion detection on the port is as follows:

Congestion occurs on the port when CON + USED AVE.
Congestion disappears from the port when CLEAR + USED < AVE.
Huawei Confidential
Page 75
LDR Triggering for Iub Bandwidth Resource

The congestion detection for a path or a resource group is similar to that for a port.
Generally, congestion thresholds need to be set for only ports or resource groups. If
different types of AAL2 paths or IP paths require different congestion thresholds, the
associated parameters need to be set for the paths as required.
If ATM LPs or IP LPs are configured, congestion control is also applicable to the LPs.
The congestion detection mechanism for the LPs is the same as that for resource
groups.
Huawei Confidential
Page 76
Load Reshuffling Actions

Inter-frequency load handover
Occasion: When the cell is in basic congestion state, the RNC

takes one of the following actions in each period until the congestion
is resolved
Code reshuffling
Actions: As the illustration, the sequence of the LDR actions is
Uncontrolable realtime
Qos renegotiation
AMR rate reduction
Inter-system load handover
in the CS domain
Load Resuffling Actions
BE service rate reduction
Inter-system load handover

in the PS domain
MBMS power reduction
fixed to Inter-freq load handover, code reshuffling, BE rate reduction,

Uncontrolable realtime Qos renegotiation, AMR rate reduction,
Inter-system handover in CS domain, Inter-system handover in PS
domain, and MBMS power reduction.
Order: The sequence of the LDR actions can be changed through

the ADD CELLLDR command, and the waiting timer for LDR
period is defined by the LDR period timer length parameter through
the SET LDCPERIOD command.
Procedure: As showed in the illustration, if the inter-frequency

handover action succeeds, the determination of whether the system
is congested continues. If the system is still congested, the interfrequency load handover is initiated again.
If the handover fails, code reshuffling is performed:
If the code reshuffling succeeds, the determination of whether the
system is congested continues. If the system is still congested, the
code reshuffling is initiated first.
If the code reshuffling fails, the next action, that is, BE rate
reduction, is taken.
Huawei Confidential
Page 77
LDR actions performed for different resources

LDR Actions
Resource
UL/
DL
Channel
DCH
HSUPA
DCH
HSDPA
UL
Power
DL
InterInter-RAT Inter-RAT
Iu QoS
MBMS
Frequency BE Rate
AMR Rate
Code
Handover in Handover in
Renegotiatio
Power
Load
Reduction
Reduction
Reshuffling
CS Domain PS Domain
n
Reduction
Handover
FACH
(MBMS)
DCH
UL
DCH
DL
HSDPA
HSUPA
Iub
FACH
(MBMS)
Huawei Confidential
Page 78
LDR actions performed for different resources

LDR Actions
Resource
UL/
DL
Channel
InterFrequency
Load
Handover
Inter-RAT
Inter-RAT
Iu QoS
MBMS
BE Rate
AMR Rate
Code
Handover in Handover in
Renegotiatio
Power
Reduction
Reduction
Reshuffling
CS Domain PS Domain
n
Reduction
DCH
code
DL
HSDPA
FACH
(MBMS)
DCH
HSUPA
DCH
UL
credit
DL
HSDPA
FACH
(MBMS)
Note: Whether the gold users perform the LDR actions is controled by specific switch on RNC
Loal Maintenance Terminal.
Huawei Confidential
Page 79
Action 1: Inter-Frequency Load Handover

The neighbouring cell must be the inter-frequency blind
handover celland the measured
signal quality can meet
Target Cell condition

After actions performed, all of the resources in the target
cell do not trigger basic
congestion
All the conditons must

be satified, then the
action will be
performed
For the selected UE, its UL/DL current bandwidth has to be

less than the UL/DL HO maximum
bandwidth
Service condition
Inter-Frequency
Load Handover
action performed
The LDR algorithm selects one UE to perform the actions

according to the user integrate
priority.
Power resource LDR
Code resource LDR
The UL/DL HO load space threshold for the target cell
must be satified
The minimum SF of target cell mustnt greater then the

current cell
The difference of code occupy rate must meet the

InterFreq HO code used ratio
space threshold
Huawei Confidential
If the conditions are not

meet or the action fails, the
algorithm will go to next
action desicion
Page 80
Action 2: BE Rate Reduction

In the same environment, different rates consume different resource. The higher the rate is, the more
resource will be needed. Therefore, the load can be reduced by bandwidth reconfiguration. The BE rate
reduction action is based on DCCC algorithm. When admission control of Power/NodeB Credit is disabled,
it is not recommended that the BE Rate Reduction be configured as an LDR action in order to avoid pingpong effect.
For HSUPA service, this action is
just used for CE resource LDR, and
the rate variety depends on HSUPA
UpLink rate adjust set parameter
Rate downsizing
If the selected RAB is a DCH RAB, only
3-rate downsizing applies.
If the current rate is MBR, the rate is
downsized to Uplink mid bit rate threshold.
If the current rate is higher than GBR but
lower than MBR, the rate is downsized to
GBR.
The reconfiguration is completed

as indicated by the RB
RECONFIGURATION message
on the Uu interface and through
the RL RECONFIGURATION
message on the Iub interface.
Rate recovery
In the LDR state, the rate upsizing
target rate is GBR.
After basic congestion is cleared, the
rate upsizing target rate is MBR rate.
If the rate upsizing will trigger the
basic congestion,the action should not
be happened.
Baise principle
User selection based on the
integrate priority, the lowest RAB
will be processed first .
The number of RABs to select is
determined by the UL/DL LDR-BE
rate reduction RAB number
parameter .
Service
condition
BE Rate Reduction action of

basic congestion algorithm
This action is used for DCH

RAB and HSUPA
RAB .Only BE service will
be considered.
The selected RAB bit rate
must greater than GBR.
Note: If the conditions are not meet or action fail, the algorithm will go to next action decision.
Huawei Confidential
Page 81
Action 3Uncontrolled Real-Time QoS Renegotiation

Based on this action, the RNC can adjust the rate of real-time services to reduce the
load of the current cell.
Renegotiation
Procedure
The target rate is the GBR rate which is indicated on

Iu interface when the serivce setup.
The RNC initiates the RAB renegotiation procedure

through the RAB MODIFICATION REQUEST
message on the Iu interface.
The Core Network sends the RAB ASSIGNMENT

REQUEST message to the RNC for RAB parameter
reconfiguration.
Baise Principle
User selection based on the

integrate priority, the lowest
RAB will be processed first .
The number of RABs to
select is determined by the
UL/DL LDR un-ctrl RT Qos
re-nego RAB num parameter .
Uncontrolled RealTime QoS

Renegotiation
This action is not recommended

to be configured when there are
no steaming traffic calss
subscribed in live network.
Service
Pondition
This action is just used for

DCH RAB.
Only the real-time services in
the PS domain will be
considered. For example, the
streaming service.
Note: If the conditions are not meet or actions fails, the algorithm will go to next action decision.
Huawei Confidential
Page 82
Action 4: Inter-RAT Handover in the CS Domain
According to the different service-handover IE in the RAB ASSIGNMENT REQ message on

the IU interface,this action is divided into two types:
Environment
condition
Inter-RAT Should Be Load Handover in the CS Domain

Inter-RAT Should Not Be Load Handover in the CS Domain
The two actions have completely similar parameters and procedures, therefore, we just introduce
the Inter-RAT Should Be Load Handover in the CS Domain action here as an example.
The CS inter-rat handover algorithm switch and the CS interrat handover algorithm parameter
are both enabled.
The GSM neighbouring cells are configured properly.
The algorithm selects RAB to perform this action according to
Basic
principle
will be selected first.

integrate priority. the lowest RAB
The number of UEs which are selected is controled by the UL/DL
CS should be ho user number
parameter.
Inter-RAT
Handover in the
CS Domain
performed
The UE can support inter-RAT compress mode.
Service
condition
The AMR DCH service in the CS domain, which the
service-handover IE is set to "handover

to GSM should be
performed" in RAB ASSIGNMENT REQ message.
Note: If the conditions are not meet or actions fails, the algorithm will go to next action decision.
Huawei Confidential
Page 83
Action 5: Inter-RAT Handover in the PS Domain
The action procedure of Inter-RAT Handover in the PS Domain is similar to that of InterRAT Handover in the CS Domain.
Huawei Confidential
Page 84
Actions 6: AMR Rate Reduction

In the WCDMA system, voice services work in eight AMR modes. Each mode has its own rate.
Therefore, mode control is functionally equal to rate control.
The LDR algorithm operates in the downlink as follows:
In the downlink direction
Based on the integrate priority, the LDR sorts the RABs in descending order. RABs with AMR
services (conversational) and with the bit rate higher than the GBR are selected. The number of
RABs to select is determined by the DL LDR-AMR rate reduction RAB number parameter.
The RNC sends the Rate Control request message through the IuUP to the CN to adjust the
AMR rate to the GBR.
If the RNC cannot find an appropriate RAB for the AMR rate reduction, the action fails. The
LDR takes the next action.
In the Uplink direction

The only difference from downlink is on the step 2: The RNC sends the TFC CONTROL command to
the UE to adjust the AMR rate to the GBR..
Note: This action is just suitable for CS AMR service which is canrried on the DCH.
Huawei Confidential
Page 85
Action 7Code Reshuffling

Principle
When the cell is in basic congestion for shortage of code resources, sufficient code resources can be
reserved for subsequent service access through code reshuffling. Code subtree adjustment refers to the
switching of users from one code subtree to another. It is used for code tree defragmentation, so as to free
smaller codes first.
The algorithm operates as follows:
Step 1 : Initialize the SF_Cur of the root node of subtrees to Cell LDR SF reserved threshold.
Step 2 : Traverse all the subtrees with this SF_Cur at the root node. Leaving the subtrees
occupied by common channels and HSDPA channels out of account, take the subtrees in which
the number of users is not larger than the value of the Max user number of code adjust parameter
as candidates for code reshuffling.
Step 3: Select a subtree from the candidates to perform the action
Step 4: Treat each user in the subtree as a new user and allocate code resources to each user.
Step 5: Initiate the reconfiguration procedure for each user in the subtree and reconfigure the
channel codes of the users to the newly allocated code resources.
Note: If no such candidate is available in step 2, subtree selection fails. This procedure ends.
Huawei Confidential
Page 86
Code Reshuffling Procedure

In the Step 3 in previous page, subtree select principle according to the setting
of the LDR code priority indicator parameter:
If this parameter is set to TRUE, select the subtree with the largest code number from the
candidates.
If this parameter is set to FALSE, select the subtree with the smallest number of users from
the candidates. In the case that multiple subtrees have the same number of users, select the
subtree with the largest code number.
The following figures show an example of code reshuffling. In this example, Cell
LDR SF reserved threshold is set to SF8 and Max user number of code adjust is
set to 1.
The reconfiguration procedure on the UU interface is implemented through the

PHYSICAL CHANNEL RECONFIGURATION message and that on the Iub
interface through the RL RECONFIGURATION message.
Huawei Confidential
Page 87
Action 8: MBMS Power Reduction

The downlink power load can be reduced by lowering power on MBMS traffic
channels.
The algorithm operates as follows:
Based on the integrated priority, the algorithm sorts the RABs in descending order.
The algorithm selects a RAB with the lowest integrated priority and with the
current power higher than the minimum transmit power of the corresponding
MTCH. That is, it selects a RAB of which the ARP value is higher than
MbmsDecPowerRabThd.
The algorithm triggers a reconfiguration procedure to set the power to the

minimum transmit power of the FACH onto which the MTCH is mapped.
The reconfiguration procedure on the Iub interface is implemented through the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST
message.
Huawei Confidential
Page 88
Contents
Perface



Overload Control Algorithm Overview
Triggering and release of cell power overload
General OLC Procedure for power resource
Overload Detection for Transmission resource
Overload Handling for Transmission resource
Huawei Confidential
Page 89
Overload Control Algorithm Overview

After the UE access is allowed, the power consumed by a single link is adjusted by the
single link power control algorithm. The power varies with all kinds of factors such as the
mobility of the UE and the changes in the environment. In some situations, the total power load
of the cell can be higher than the target load. To ensure the system stability, Overload Control
(OLC) must be performed.
Two kinds of resources can trigger OLC:
Power
Iub bandwidth
Overload control algorithm procedure has three stages, that is:
Overload Congestion Triggering
Over load Control Procedure
Over load Control Actions
Tiggering style
For power resource, the RNC performs periodic measurement and checks whether the cells are congested.
For Iub resources, event-triggered congestion applies, that is, the RNC checks whether the cells are
congested when resource usage changes.
Note: Only power resources and Iub resource can result in overload congestion. Other resources such as the equivalent
number of users, code resource, and credit resources do not cause overload congestion.
Huawei Confidential
Page 90
Triggering and release of cell power overload

UL/DL load
Cell in overload
Overload released
OLC trigger
threshold
OLC release
threshold
time
RNC periodic check
State transition hysteresis threshold
If the current UL/DL load of an R99 cell is higher than or equal to the UL OLC trigger threshold
or DL OLC trigger threshold for 1,000 ms, the cell is in the overload state and the related
overload handling action is taken. If the current UL/DL load of the R99 cell is lower than the UL
OLC release threshold or DL release threshold for 1,000 ms, the cell comes back to the normal
state.
The overload triggering and release mechanisms for UL HSPA cells are the same as those for R99
cells.
Whether a DL HSPA cell is overloaded is estimated according to the sum of the non-HSPA power
and the GBP.
Huawei Confidential
Page 91
General OLC Procedure for power resource

When the cell power resource is overloaded, the RNC takes one of the following actions in each
load control period until the congestion is relieved: performing TF Control of BE Services,
switching BE Services to Common Channels, adjusting the Maximum FACH TX Power, releasing
Some RABs.
Action 1
TF Control of
BE Services
If the action
succeeds, the OLC
algorithm checks
whether the system is
overloaded. If yes, the
OLC performs TF
control again.
If this action fails or
the action performed
time exceeds the
specific threshold,
then takes next action.
Action 2
Action 3
Switching BE
Services to
Common Channels
If the action
succeeds, the OLC
algorithm checks
whether the system
is overloaded. If
yes, the OLC
switches BE
services to common
channels again.
If this action fails,
then takes next
action.
Action 4
Adjusting the
Maximum FACH
TX Power
Releasing
Some RABs
If the action
succeeds, the OLC
algorithm checks
whether the system
is overloaded. If
yes, the OLC
adjusts the power
again.
If this action fails,
then takes next
action.
Huawei Confidential
Page 92
The OLC
algorithm takes this
action to release
some RABs
If this action falis,
then takes whole
procedure again,
that is perform the
action 1 ...
Action 1: Fast TF Control

The principle of this action is the same as the BE rate reduction action of load resuffling algorithm. Lower
bit rate will consume less power resource. The different is that BE rate reduction action need more time to do the
message interactive on the UU interface, and the Fast TF control action of overload control algorithm neednt.
Service selective:
The RABs with the lowest integrate priority will be selected.
The RABs with the DCH BE services whose bit rates are higher than Downlink bit rate threshold for DCCC parameter
Control principle
The RNC sends the TF control indication message to the MAC layer. Each MAC of selected RABs will receive one TF
control indication message and will restrict the TFC selection of the BE services to reduce the data rate step by step.
TF Control procedure <in the downlink direction>

MAC restricts the TFC selection in a way like that the maximum TB number is calculated with the
formula(for one RAB):
TFmax(N+1) = TFmax(N) x Ratelimitcoeff
Here:
TFmax(0) is the maximum TB number of the BE service before the service is selected for TF control.
TFmax(N+1) is the maximum TB number during the period from (T0 + RateRstrctTimerLen x N) to (T0 +
RateRstrctTimerLen x (N + 1)), where T0 is the time when the MAC receives the TF control indication message.
Ratelimitcoeff is specified by the RateRstrctCoef parameter on the RNC Local Maintenance Terminal.
If the RNC cannot find an appropriate service for the TF control or the number of times that TF control is
performed exceeds specific times, the action fails. The OLC takes the next action.
Huawei Confidential
Page 93
Fast TF Control recovered Procedure

If the congestion is released, the RNC sends the congestion release indication to the
MAC. At the same time, the rate recovery timer is started. When this timer is expired, the
MAC increases the data rate step by step.
MAC restricts the TFC selection by calculating the maximum TB number with the
formula:
TFmax(N+1) = TFmax(N) x RateRecoverCoeff
Here:
TFmax(0) is the maximum TB number of the BE service before congestion relief indication is received.
TFmax(N+1) is the maximum TB number during the period from (T1 + RateRecoverTimerLen x N) to
(T1 + (RateRecoverTimerLen x (N + 1)), where T1 is the time when the MAC receives the congestion
relief indication message.
RateRecoverCoeff is specified by the RecoverCoef parameter.
Huawei Confidential
Page 94
An example for TF Control on the downlink
Before point A, the cell is not in OLC state. The downlink data transfer rate is 384 kbit/s, the
corresponding TF is 12 x 336, and TFS is {12 x 336, 8 x 336, 4 x 336, 2 x 336, 1 x 336, 0 x 336}.
At point A, the cell enters OLC state. The RNC selects this RAB to do fast TF restriction. MAC
restricts the TFC selection during time between point A and point B by calculating the maximum
TB number as follows:
TFmax(1) = TFmax(0) x Ratelimitcoeff = 12 x 0.68 = 8.16
Match 8.16 and the TFS. Therefore, the maximum TB number is 8.
Huawei Confidential
Page 95
OLC Algorithm for TF Control in the Uplink

When uplink power overload congestion is triggered, for a UE with the DCH service, the RNC
sends a TRANSPORT FORMAT COMBINATION CONTROL message to the UE to restrict the TFC of
the UE, according to the 3GPP TS25.331.
The RNC sends the TRANSPORT FORMAT COMBINATION CONTROL message to the UE that
accesses the specified service. This message contains the following IEs:
Transport Format Combination Set Identity: defines the available TFC that the UE can select,
that is, the restricted TFC sub-set. It is always the two TFCs corresponding to the lowest data
rate.
TFC Control Duration: defines the period in multiples of 10 ms frames for which the restricted
TFC sub-set is to be applied. It is set to a random value from the range of 10 ms to 5120 ms, so
as to avoid data rate upsizing at the same time.
After the TFC control duration is due, the UE can apply any TFC of TFCS before the TF control.
Huawei Confidential
Page 96
Action 2: Switching BE Services to Common Channel

The OLC algorithm for switching BE services to common channel operates as
follows:
Based on the user integrate priority, the OLC sorts all UEs that only have PS
services including HSPA and DCH services (except UEs having also a streaming
bearer) in descending order.
The top N UEs are selected. The number of selected UEs is equal to Transfer
Common Channel user number. If UEs cannot be selected, the action fails. The OLC
performs the next action.
The selected UEs are switched to common channel.
Note:
The state transition from FACH to DCH is prohibited when the cell is in the overload congestion state.
After the overload state is relived, the state transition from FACH to DCH will happened due the traffic volume.
Huawei Confidential
Page 97
Action 3: Adjusting the Maximum FACH TX Power

The procedure for adjusting the maximum FACH transmit power is as follows:
Set the maximum FACH transmit power to the target maximum transmit power. The target
maximum transmit power is calculated according to the following formula:
Here:
Ptarget is the target maximum transmit power.
Pmax is the maximum FACH transmit power (MaxFachPower).
Delta is the FACH power reduction step (FACHPwrReduceValue).
If the congestion is relieved after the power adjustment, the system starts the FACH power
recovery timer, which is set to 5s. When the timer expires, the maximum FACH transmit power
is increased to the original maximum FACH transmit power if the system is always in the
normal state before the timer expires.
Note: During an OLC period, the OLC can adjust the power of only one FACH. If multiple FACHs meet the
conditions, the OLC adjusts them one by one in different OLC periods.
Huawei Confidential
Page 98
Action 4: Release of Some RABs

OLC Algorithm for the Release of Some RABs in the Uplink
Based on the integrate priority, the OLC sorts all RABs including HSUPA and DCH services in
descending order.
The top RABs selected. If the integrate priorities of some RABs are identical, the RAB with
higher rate (current rate for DCH RAB and GBR for HSUPA RAB) in the uplink is selected. The
number of selected RABs is equal to UL OLC traff release RAB number.
The selected RABs are released directly.
OLC Algorithm for the Release of Some RABs in the Downlink
Based on the integrate priority, the OLC sorts all non-MBMS RABs in descending order.
The top-priority RABs are selected. If the integrate priorities of some RABs are identical, the
RAB with higher rate (current rate for DCH RAB and GBR for HSUPA RAB) in the downlink is
selected. The number of selected RABs is equal to DL OLC traff release RAB number.
The selected RABs are directly released.
If all non-MBMS RABs are released but congestion persists in the downlink, MBMS RABs are
selected.
CAUTIONThe higher the value of UL OLC traff release RAB number/ DL OLC traff release RAB
number is, the more obviously the cell load decreases at the cost of negatively affecting user experience.
Huawei Confidential
Page 99
Overload Detection for Transmission resource

Overload can be triggered in any of the following conditions:
In ATM IMA networking scenario, an IMA group contains multiple E1s, among which
some E1s are broken whereas others work properly.
In ADSL networking scenario, the available ADSL bandwidth deteriorates abruptly, for
example, from 8 Mbit/s to 1 Mbit/s.
When some links in a link aggregation group are faulty, the available bandwidth of the
group decreases.
When some links in an IP MLPPP group are faulty, the available bandwidth of the group
decreases.
Similar to congestion detection, overload detection is applicable to paths, resources

group, and ports.
For example: Assume the available bandwidth at a port as AVE and the used
bandwidth at the port as USED. Then, overload occurs when USED > AVE.
Huawei Confidential
Page 100
Overload Handling for Transmission resource

Handling on the Iub Interface
After the RNC receives an overload message, the RNC triggers Overload Control (OLC)
actions. OLC triggers release of resources used by users in order of comprehensive priority.
Handling on Other Interfaces
The congestion on the Iur interface can trigger Serving Radio Network Subsystem (SRNS)
relocation.
During Iu signaling flow control, if congestion is detected on the signaling link towards
the signaling point, the congested state is reported to the RANAP subsystem of the RNC. Then,
the RANAP subsystem discards user messages in the following sequence: short message
service > CS and PS call > registration.
Huawei Confidential
Page 101
Contents
Perface
Dynamic Cell Shutdown Algorithm Overview
Conditions for Dynamic Cell Shutdown
Conditions for Opening Up a Cell
Huawei Confidential
Page 102
Dynamic Cell Shutdown Algorithm Overview

Why we use this algorithm ?
During a certain period of time, the traffic density or traffic volume in a cell may be relatively low. In
this case, the dynamic cell shutdown algorithm hands over some UEs from this cell to other interfrequency same-coverage neighboring cells, when certain load conditions are met. Then, the algorithm
shuts down this cell to reduce the power consumption.
Before shutdown
Cell A
Cell B
After shutdown
Cell A
Cell B
UEs in cell A are

handed over to cell B
Huawei Confidential
Page 103
Conditions for Dynamic Cell Shutdown
cell A and cell B are inter-frequency same-coverage neighboring cells between which blind
handover can be performed. The algorithm checks whether the cell meets the following conditions:
The number of total UEsHSDPA UEsHSUPA UEs are all below corresponding threshold.
The load margin of a neighboring cell is above the threshold NCellLdrRemainThd.
No MBMS services, CBS services, or UEs on common channels exist in this cell.
If all these conditions are met, The algorithm starts a handover-waiting timer T1 (30s) and hands
over the UEs from this cell to neighboring cells.
If no UE exists and the load of neighboring cells is normal when T1 expires, the RNC identifies
this cell as an unusable cell and sends a cell shutdown indication to the NodeB. The NodeB shuts
down this cell.
Load or
UE quantity
Handover is triggered
and T1 is started.
When cell B enters the LDR

state, cell A is opened up
and T2 is started.
When T2 expires, the

next cycle of dynamic
cell shutdown is started.
LDR trigger
threshold
T2
T1
Start time of
dynamic cell
shutdown
time
Periodic check
by the RNC
When T1 expires, cell A is shut
down if handover is complete.
Huawei Confidential
Load status of cell B

Load status of cell A
Page 104
Conditions for Opening Up a Cell

After the cell is shut down, the RNC determines at intervals whether to open up the
cell. The RNC opens up the cell that is shut down when any of the following conditions is
met:
In the sector to which the shutdown cell belongs, there is a cell of which the load is in the
LDR state.
The effective period of dynamic cell shutdown expires.
A neighboring cell fails to admit a service because of resource insufficiency.

The shutdown cell is an HSPA cell, and a neighboring R99 cell admits a high-rate UE.
Huawei Confidential
Page 105
Reference Documents
Load Control Algorithms Reference Documents lists the reference documents related
to the feature.
3GPP TS 25.133: Requirements for Support of Radio Resource Management (FDD)
3GPP TS 25.215: Physical layer - Measurements (FDD)
3GPP TS 25.304: UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode
3GPP TS 25.321: Medium Access Control (MAC) protocol specification
3GPP TS 25.331: Radio Resource Control (RRC)
3GPP TS 25.413: UTRAN Iu Interface RANAP Signaling
Huawei Confidential
Page 106
Thank you
www.huawei.com

Load Control 2

Загружено:

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

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

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

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

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

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

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

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

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

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

Load Control 2

Загружено:

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

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

Security Level: Confidentia

Load Control Strategys

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Load Control Algorithm Overview

Load Control Introduction

Load Control algorithms in different UE access phases

Load Control algorithms used on different cell load levels

Priorities Involved in Load Control

Auto-Adaptive Background Noise Algorithm

Potential User Control Algorithm

Call Admission Control Algorithm

Intelligent Access Control Algorithm

Load Reshuffling Algorithm

Overload Control Algorithm

Dynamic Cell Shutdown Algorithm

HUAWEI TECHNOLOGIES CO., LTD.

Load Control Introduction

The destination of load control algotirhms

Differentiated services under load control algorithms

HUAWEI TECHNOLOGIES CO., LTD.

Load Control algorithms in different UE access phases

used, as shown in the following figure.

Before UE access: PUC

During UE access: CACIAC

After UE access: LDBLDROLC

PUC = Potential User Control

HUAWEI TECHNOLOGIES CO., LTD.

LDB = Load Control Balancing

Load control algorithms used on different cell load levels

Cell load (number of subscribers)

Start OLC: check and relieve overload

HUAWEI TECHNOLOGIES CO., LTD.

Resources used by different load control algorithms

HUAWEI TECHNOLOGIES CO., LTD.

Priorities Involved in Load Control

integrated priority, and user integrated priority.

HUAWEI TECHNOLOGIES CO., LTD.

High Speed Uplink/Downlink Packet Access (HSUPA /HSDPA)

Adaptive Multi Rate (AMR/ AMR-WB)

HUAWEI TECHNOLOGIES CO., LTD.

RAB Integrated Priority

HUAWEI TECHNOLOGIES CO., LTD.

User Integrated Priority

HUAWEI TECHNOLOGIES CO., LTD.

Auto-Adaptive Background Noise Algorithm

Call Admission Control Algorithm

Load Reshuffling Algorithm

Dynamic Cell Shutdown Algorithm

HUAWEI TECHNOLOGIES CO., LTD.

Auto-Adaptive Background Noise Algorithm

HUAWEI TECHNOLOGIES CO., LTD.

Load Control Algorithm Overview

Auto-Adaptive Background Noise Algorithm

Potential User Control Algorithm

Potential User Control Overview

Potential User Control Triggering

Potential User Control Procedure

Call Admission Control Algorithm

Intelligent Access Control Algorithm

Load Reshuffling Algorithm

Overload Control Algorithm

Dynamic Cell Shutdown Algorithm

HUAWEI TECHNOLOGIES CO., LTD.