3G Load Management

3G LOAD MANAGEMENT
Jan 2012
Behrouz Lotfipour
Over load and high load
definition
1
Huawei Algorithms to
Control the load
2
Special Event
Management
3
Topics
OVERLOAD AND HIGH
LOAD DEFINITION
DL Power Utilization
UL Load
CE Utilization
NodeB Limitation
IuB Utilization
Code Utilization

Call setup procedure
C VS.RRC.Rej.Redir.Service
E VS.RRC.Rej.Redir.InterRat,VS.RRC.Rej.Redir.IntraRat,VS.RRC.Rej.ULCE.Cong,VS.RRC.
Rej.DLCE.Cong
G VS.RRC.Rej.RL.Fail,VS.RRC.Rej.DLCE.Cong,VS.RRC.Rej.ULCE.Cong
H VS.RRC.Rej.TNL.Fail
K VS.RRC.FailConnEstab.NoReply
L VS.RRC.Rej.Sum,VS.RRC.FailConnEstab.Cong
Call setup procedure
VS.RRC.Rej.ULPower.Cong Number of RRC Connection Rejects for Cell (UL Power
Congestion)
V900R012
VS.RRC.Rej.DLPower.Cong Number of RRC Connection Rejects for Cell (DL Power
Congestion)
V900R012
VS.RRC.Rej.ULCE.Cong Number of RRC Connection Rejects for Cell (UL CE Resource
Congestion)
Earlier than
V900R011
VS.RRC.Rej.DLCE.Cong Number of RRC Connection Rejects for Cell (DL CE Resource
Congestion)
Earlier than
V900R011
VS.RRC.Rej.Code.Cong Number of RRC Connection Rejects for Cell (Code Resource
Congestion)
Earlier than
V900R011
VS.RRC.Rej.RL.Fail Number of RRC Connection Rejects Due to Radio Link Setup
Failure for Cell
Earlier than
V900R011
VS.RRC.Rej.TNL.Fail Number of RRC Connection Rejects for Cell (Transmission Setup
Failure on Iub Interface )
Earlier than
V900R011
VS.RRC.Rej.ULIUBBand.Cong Number of RRC Connection Rejects for Cell (UL Iub Bandwidth
Congestion)
Earlier than
V900R011
VS.RRC.Rej.DLIUBBand.Cong Number of RRC Connection Rejects for Cell (DL Iub Bandwidth
Congestion)
Earlier than
V900R011
VS.RRC.Rej.Redir.InterRat Number of RRC Connection Rejects during redirection between
inter-RAT cells for cell
Earlier than
V900R011
VS.RRC.Rej.Redir.IntraRat Number of RRC Connection Rejects during redirection between
inter-frequency cells for cell
Earlier than
V900R011
HUAWEI ALGORITHMS TO
CONTROL CELL LOAD
Huawei Algorithms to control the load
1. Before UE access: Potential User Control (PUC)
2. During UE access:
2.1. Intelligent Access Control (IAC)
2.2. Call Admission Control (CAC)
3. After UE access:
3.1. intra-frequency Load Balancing (LDB),
3.2. Load Reshuffling (LDR),
3.3. Overload Control (OLC)
1
Potential User Control (PUC)
1. Potential User Control (PUC)
The function of PUC is to balance traffic load between inter-frequency cells. The
RNC uses PUC to modify cell selection and reselection parameters, and broadcasts
them through system information. In this way, UEs are led to cells with a light load.
The User can be in idle mode, CELL_FACH state, CELL_PCH state, or URA_PCH state.

The PUC algorithm is enabled only when the PUC subparameter of the
NBMLdcAlgoSwitch parameter is set to 1.

The RNC periodically monitors the downlink load of the cell and compares the
measurement results with the upper threshold and lower threshold for load level
division, that is, SpucHeavy and SpucLight.

If the cell load is higher than the upper threshold plus the load level division
hysteresis (SpucHyst), the cell load is considered heavy.
If the cell load is lower than the lower threshold minus the load level division
hysteresis,the cell load is considered light.
2.1
Intelligent Access Control (IAC)
The function of IAC is to increase the access success rate with the current QoS
guaranteed through rate negotiation, queuing, pre emption, and Directed Retry
Decision (DRD).

The access of a service to the network consists of setup of an RRC connection and a
RAB. The Intelligent Access Control (IAC) algorithm is used to improve the access
success rate.

IAC Overview
IAC During RRC Connection Setup
Rate Negotiation
RAB DRD
Pre emption
Queuing
Low-Rate Access of the PS BE Service
IAC for Emergency Calls
Intelligent Access Control (IAC) IAC Overview

IAC procedure supported by services
Intelligent Access Control (IAC) IAC During RRC Connection Setup

Intelligent Access Control (IAC) Rate Negotiation
Intelligent Access Control (IAC) RRC DRD
If the UE fails to access the current cell, the RNC performs RRC DRD. The purpose is to
instruct the UE to set up an RRC connection in an inter-frequency neighbouring cell with
better signal quality.
The RNC performs the following steps:
1. The RNC selects the intra-band inter-frequency neighbouring cells of the current cell.
These neighbouring cells are suitable for blind handovers. Whether the neighbouring cells
support blind handover is specified by the parameter BlindHoFlag.
2. The RNC generates a list of candidate DRD-supportive inter-frequency cells according to
the following condition:
(CPICH_EcNo)RACH > DRD_EcNOnbcell
Here:
(CPICH_EcNo)RACH is the cached CPICH Ec/N0 value included in the RACH measurement
report. Note that this value is of the current cell.
DRD_EcNOnbcell is the DRD threshold (DRDEcN0Threshhold) of the neighbouring cell.
3. The RNC selects a target cell from the candidate cells for UE access. If the candidate cell
list is empty, the RRC DRD fails. The RNC performs RRC redirection. If the candidate cell list
contains more than one cell, the UE tries a cell randomly.
If the admission is successful, the RNC continues the RRC connection setup procedure.
If the admission to a cell fails, the UE tries admission to another cell in the candidate cell
list until an
admission is successful or all admission attempts fail.
If all the admission attempts fail, the RNC makes an RRC redirection decision.
Intelligent Access Control (IAC) RRC Redirection
ConnectFailRrcRedirSwitch=1

1. The RNC selects all intra-band inter-frequency cells of the local cell.
2. The RNC selects 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.
3. If more than one candidate cell is available, the RNC selects a cell randomly and
redirects the UE to the cell.
4. 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:
a. If a neighbouring GSM cell is configured, the RNC redirects the UE to that GSM
cell.
b. If no neighbouring GSM cell is configured, the RRC connection setup fails.
Intelligent Access Control (IAC) Pre emption
Common Pre emption
Forced Pre emption

Common preemption requires that RABs have been set up or are being set up for pre
empting users and that pre empting users have higher priorities than pre emptable
users. Therefore, CS services cannot trigger pre emption in the RRC connection setup
phase. Even in the RAB-related phases, CS servicesmay fail to preempt PS services
because of insufficient priorities. When PS traffic volume is high and
radio resources are insufficient, the success rate for CS service setup may decrease. To
address this problem, forced preemption is introduced. This function ensures
preferred access of AMR services and a high success rate for AMR service setup.
In forced preemption, only CS conversational services can trigger preemption and only
PS BE services can be preempted.
This function is determined by the RsvdPara1 parameter. This parameter consists of
two subparameters:

RSVDBIT4 and RSVDBIT5.

Intelligent Access Control (IAC) Queuing
Intelligent Access Control (IAC) RAB DRD

Inter-Frequency DRD for Service Steering
ServiceDiffDrdSwitch=1


The procedure of DRD for service steering is as follows:

1. The RNC determines the candidate cells to which blind handovers /Measured DRD
can be performed and sorts the candidate cells in descending order according to
service priority.
A candidate cell must meet the following conditions:
The frequency of the candidate cell is within the band supported by the UE.
The quality of the candidate cell meets the requirements of inter-frequency DRD. For
details, see 6.2 "IAC During RRC Connection Setup."
The candidate cell supports the requested service.



2. The RNC selects a target cell from the candidate cells in order of service priority for UE
access.
If there is more than one cell with the same service priority,
When the cell, in which the UE requests the service, is one of the candidate cells with
the same service priority, preferably, the RNC selects this cell for admission decision.
Otherwise, the RNC randomly selects a cell as the target cell.
3. The CAC algorithm makes an admission decision based on the status of the target cell.
If the admission attempt is successful, the RNC accepts the service request.
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 are any cells where no admission decision has been made, the algorithm goes
back to step 2.
If admission decisions have been made in all the candidate cells, then:
a. 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 make an admission decision based on
R99 service priorities.
b. If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
Call Admission Control (CAC)
The function of CAC is to decide
whether to accept resource requests
from UEs, such as
access, reconfiguration, and
handover requests, depending on
the resource status of the
cell.
The admission decision is based on:
Available cell code resource
Available cell power resource
NodeB resource state, that is, NodeB credits, which are used to
measure the channel
demodulation capability of NodeBs
Available Iub transport layer resource, that is, Iub transmission
bandwidth
Number of HSDPA users (only for HSDPA services)
Number of HSUPA users (only for HSUPA services)
cell code resource
When a new service attempts to access the network, code resourcebased
admission is mandatory.

Code resourcebased admission is implemented as follows:

For RRC connection setup requests, the code resourcebased admission is
successful if
the current remaining code resource is sufficient for RRC connection setup.
For handover services, the code resourcebased admission is successful if the
current
remaining code resource is sufficient for the service.
For other R99 services, the RNC has to ensure that the remaining code does not
exceed
the DlHoCeCodeResvSf parameter after admission of the new service.
For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore,
the code resourcebased admission is not required.
Call Admission Control (CAC) cell power resource
2.2
Call Admission Control (CAC) Overview

Avalable cell code ressource
Available cell power resource
NodeB credits, which are used to measure the
channel demodulation capability of NodeBs
Available Iub transmission bandwidth
Number of HSDPA users (only for HSDPA services)
Number of HSUPA users (only for HSUPA services)

Admission Decision for RRC Connection Setup Request
Power-Based Admission for RAB Setup

Call Admission Control (CAC) cell power resource RRC
For the RRC connection setup request due to an emergency call, detach, or
registration, direct admission is used.
For the RRC connection setup request for other reasons, the admission decision for
RRC connection setup request is as follows:

When power-based admission is based on power (algorithm 1 and algorithm 3),
the UL or DL OLC trigger threshold (UlOlcTrigThd or DlOlcTrigThd) is used for
admission.
When power-based admission is based on the ENU (algorithm 2), the admission
decision is made as follows:
When UL_UU_OLC or DL_UU_OLC is set to 1, RRC connection setup request is
rejected when the cell is in the overload state. If the cell is not in the overload
state, the UL or DL OLC trigger threshold is used for power-based admission.
When UL_UU_OLC or DL_UU_OLC is set to 0, the UL or DL OLC trigger
threshold is used for power-based admission.

Algorithm 1 (ALGORITHM_FIRST): admission decision based on predicted load
increment upon admission of a new service
Based on the current cell load (indicated by the uplink load factor and downlink TCP)
and the predicted load increment due to admission of the new service, the RNC
determines whether the cell load will exceed the threshold upon admitting the new
service. If yes, the RNC rejects the access request. If not, the RNC accepts the access
request.
Algorithm 2 (ALGORITHM_SECOND): admission decision based on the ENU
Depending on the current ENU and the access request, the RNC determines whether the
ENU will exceed the threshold upon admitting a new service. If yes, the RNC rejects the
request. If not, the RNC accepts the request.
Algorithm 3 (ALGORITHM_THIRD): admission decision based on no load increment
upon admission of a new service
This algorithm assumes that load increment upon admission of a new service is 0. Based
on the current cell load (indicated by the uplink load factor and downlink TCP), the RNC
determines whether the cell load will exceed the threshold upon admitting the new
service. If yes, the RNC rejects the access request. If not, the RNC accepts the access
request.
Common Channel Power
R99 PS+R99 CS +HS +HO
R99 CS+HS + HO
HO +HS HS (depend on HS power margin setting)
Reserved +HS (depend on HS power margin setting)
DlConvAMRThd
DlOtherThd
DlHOThd
DlCellTotalThd
cell power resource RAB
cell power resource: ENU table
The 12.2 kbit/s AMR traffic is defined as one ENU, which stands for Equivalent
Number of Users. Thus, the 12.2 kbit/s AMR traffic can be used to calculate the
ENU of all other services.
NodeB resource/
Call Admission Control (CAC) NodeB resource
Call Admission Control (CAC) NodeB resource
NodeB resource/
User Number
CAC Based on the Number of HSPA Users
CAC of HSDPA Users
When HSDPA_UU_ADCTRL is set to 1, the HSDPA services have to undergo admission
decision based on the number 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 NodeBHsdpaMaxUserNum.
Otherwise, the algorithm rejects the service request.
CAC of HSUPA Users
When HSUPA_UU_ADCTRL is set to 1, the HSUPA services have to undergo admission
decision based on the number of HSUPA users.
When a new HSUPA service attempts to access the network, the algorithm admits the
service if the following conditions are met:
1- The number of the HSUPA users in the cell does not exceed the maximum value
specified by MaxHsupaUserNum.
2- The number of the HSUPA users in the NodeB does not exceed the maximum value
specified by NodeBHsupaMaxUserNum
3.1
Intra-frequency Load Balancing (LDB)
The function of intra-frequency LDB is to balance the cell load between
neighbouring intra-frequency cells to provide better resource usage.

Intra-frequency Load Balancing (LDB) is performed to adjust the coverage areas of
cells according to the measured values of cell load. Currently, the intra-frequency
LDB algorithm is applicable only to the downlink.
LDB between intra-frequency cells is implemented by adjusting the transmit power
of the Primary Common Pilot Channel (P-CPICH) according to the downlink load of
the associated cells. When the load of a cell increases, the cell reduces its coverage
to lighten its load.
When the load of a cell decreases, the cell extends its coverage so that some traffic
is off-loaded from its neighbouring cells to it.

When the intra-frequency LDB algorithm is active, that is, when
INTRA_FREQUENCY_LDB is set to 1, the RNC checks the load of cells periodically
and
adjusts the transmit power of the P-CPICH in the associated cells based on the cell
load.
The intra-frequency LDB is described as follows:

If the downlink load of a cell is higher than the cell overload threshold
(CellOverrunThd), it is an indication that the cell is heavily overloaded. In this case, the
transmit power of the P-CPICH needs to be reduced step by step. The step is specified by
the PCPICHPowerPace parameter.
If the current transmit power is equal to the minimum transmit power of P-CPICH
(MinPCPICHPower), the current transmit power is not adjusted.
Because of the reduction in the pilot power, the UEs at the edge of the cell can be handed
over to neighboring cells, especially to those with a relatively light load and with
relatively high pilot power. After that, the downlink load of the cell is lightened
accordingly.
If the downlink load of a cell is lower than the cell underload threshold
(CellUnderrunThd), it is an indication that the cell has sufficient remaining capacity for
more load. In this case, the transmit power of the P-CPICH can be increased step by step
to help lighten the load of neighboring cells. The step is specified by the
PCPICHPowerPace parameter.
If the current transmit power is equal to the maximum transmit power of P-CPICH
(MaxPCPICHPower), the current transmit power is not adjusted.
3.2
Load Reshuffling (LDR)
The function of LDR is to reduce the cell load when the available resources for a cell
reach the specified alarm threshold.

1- Basic Congestion Triggering
2- LDR Procedure
3- LDR Actions

The purpose of LDR is to increase the access success rate by taking the following
actions:
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR voice service rate reduction
QoS renegotiation for uncontrollable real-time services
CS inter-RAT load handover
PS inter-RAT load handover
MBMS power reduction
Load Reshuffling (LDR) Basic Congestion Triggering

1- Power Resource
2- Code Resource
3- Iub Resource
4- NodeB Credit Resource

The function of LDR is to reduce the cell load when the available resources for a cell
reach the specified alarm threshold.

1- Basic Congestion Triggering
2- LDR Procedure
3- LDR Actions

The purpose of LDR is to increase the access success rate by taking the following
actions:
Code reshuffling
AMR voice service rate reduction
QoS renegotiation for uncontrollable real-time services
CS inter-RAT load handover
PS inter-RAT load handover

Power Resource

Congestion control based on power resource can be enabled through the
DL_UU_LDR and UL_UU_LDR subparameters of the NBMLdcAlgoSwitch
parameter.

Power Resource

Congestion control based on power resource can be enabled through the
DL_UU_LDR and UL_UU_LDR subparameters of the NBMLdcAlgoSwitch
parameter.

In the uplink, the basic congestion decision is based on the comparison
between the UL LDR trigger threshold (UlLdrTrigThd) and the uncontrollable
load of the cell.
In the downlink, the basic congestion decision is based on the comparison
between the DL LDR trigger threshold (DlLdrTrigThd) and the sum of the non-
HSPA power and the GBP

Code Resource

Congestion control based on code resource can be enabled through the
CELL_CODE_LDR subparameter of the NBMLdcAlgoSwitch parameter.

If the SF corresponding to the current remaining code of the cell is larger than
the value of CellLdrSfResThd, code congestion is triggered and the related load
reshuffling actions are taken.

IUB Resource

Congestion control based on Iub resource can be enabled through the IUB_LDR
subparameter of the NodeBLdcAlgoSwitch parameter in the ADD
NODEBALGOPARA or MOD NODEBALGOPARA command.

Iub congestion control in both the uplink and downlink is NodeB-oriented.. In
the case of Iub congestion, LDR actions are applied to congestion resolution. Iub
congestion detection is implemented in a separate processing module.

For details about the decision on Iub congestion detection, see the Transmission
Resource Management Parameter Description.

For the basic congestion caused by Iub resource, all UEs under the NodeB are
the objects of related LDR actions.

NodeB Credit Resource

The basic congestion caused by NodeB credit resource 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 UlLdrCreditSfResThd or
DlLdrCreditSfResThd (set through the ADD CELLLDR command), credit
congestion at cell level is triggered and related load reshuffling actions
are taken in the current cell.
Type B: Basic congestion at local cell group level (if any)
Type C: Basic congestion at NodeB level If the cell group or NodeB UL/DL
current remaining SF (mapped to credit resource ) ishigher than
UlLdrCreditSfResThd or DlLdrCreditSfResThd (set through the ADD NODEBLDR
command), credit congestion at cell group or NodeB level is triggered
andrelated load reshuffling actions are taken. The range of LDR actions is the
same as thefirst type, but the range of UEs to be sorted by priority is different.
All the UEs in thenormal cells that belong to the cell group or NodeB will be
sorted.

All Resource

If the congestion of all resources is triggered in a cell, the congestion is relieved
in order of resource priority for load reshuffling as configured through the SET
LDCALGOPARA command.
Assume that the parameters are set as follows:
1- The first priority for load reshuffling (LdrFirstPri) is set to IUBLDR.
2-The second priority for load reshuffling (LdrSecondPri) is set to CREDITLDR.
3-The third priority for load reshuffling (LdrThirdPri) is set to CODELDR.
4- The fourth priority for load reshuffling (LdrFourthPri) is set to UULDR.

Then, the basic congestion is relieved in the following sequence:
1- LDR based on Iub resource
2- LDR based on credit resource
3- LDR based on code resource
4- LDR based on power resource

The information of cell status can be checked through the DSP CELLCHK
command.

Load Reshuffling (LDR) LDR Procedures

When the cell is in the basic congestion state, the RNC takes one of the following
actions in each period (specified by the LdrPeriodTimerLen parameter) until the
congestion is relieved:
Code reshuffling
AMR rate reduction
Inter-RAT load handover in the CS domain, which involves the following actions:
Inter-RAT Should Be Load Handover in the CS Domain
Inter-RAT Should Not Be Load Handover in the CS Domain
Inter-RAT load handover in the PS domain, which involves the following actions:
Inter-RAT Should Be Load Handover in the PS Domain
Inter-RAT Should Not Be Load Handover in the PS Domain
Iu QoS renegotiation

The sequence of LDR actions can be changed through the ADD CELLLDR command,
andthe waiting timer for LDR period is specified by the LdrPeriodTimerLen
parameter throughthe SET LDCPERIOD command.


3.3
Overload Control (OLC)
The function of OLC is to reduce the cell load rapidly when the cell is overloaded.
The
purpose of OLC is to ensure the system stability and the QoS of most UEs in the
following ways:
Restricting the Transport Format (TF) of the BE service
Switching BE services to common channels
Adjusting the maximum transmit power of FACHs
Releasing some RABs
Dynamic power sharing among carriers
In dynamic power sharing among carriers, a carrier that carries the HSPA service can
dynamically use the idle power resource of another carrier, thus improving the
power
usage and the cell HSPA service rate.
Resources used by different load control algorithms
THANKS

3G Load Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3G Load Management

Uploaded by

Copyright:

Available Formats

3G LOAD MANAGEMENT

You might also like