Professional Documents
Culture Documents
www.huawei.com
The WCDMA system is a self interference system. As the load of the WCDMA
system increases, the interference rises. A relatively high interference may affect
the coverage and Quality of Service (QoS) of established services. Therefore,
capacity, coverage and QoS of the WCDMA system are mutually affected. The
purpose of load control is to maximize the system capacity while ensuring coverage
and QoS.
1
Objectives
Upon completion of this course, you will be able to:
Know the load control principles
2
Contents
1. Load Control Overview
3
Contents
1. Load Control Overview
4
Load Definition
Load: the occupancy of capacity
Soft capacity
Interference (UL)
Power (DL)
5
Uplink Load Definition
1 RTWP
Cell Load Factor: UL = 1 noise rise =
noise rise PN
6
Downlink Load Definition
The definition of DL load is very different from the definition of UL load, the
adjacent cell interference factor and the non-orthogonality factor in the downlink
are very difficult to measure and calculate, therefore, the DL cell load factor can
not be used to describe the DL cell load. Then, the transmission power is used to
describe DL load.
7
The Objectives of Load Control
Keeping system stable
Load control algorithm can be classified into three parts according to the different
working states of UE.
Before UE accesses, the PUC algorithms will function. RNC will monitor the cell
load periodically. If the current cell load exceeds a specific threshold, RNC will
modify the cell selection and re-selection parameters, in order that UE can select
the low-load cell easily when UE will initiate some services and work at CELL-DCH
state. This algorithm aims at UE which working at IDLE mode, CELL-FACH state,
CELL-PCH state or URA-PCH state in this cell.
During UE accesses, the CAC and IAC algorithms will function. RNC will judge
whether the new access is admissible.
After UE accesses, LDR and OLC algorithms will function. There are some
practical algorithms to decrease the cell load. When a cell is in basic congestion,
the RNC shall select some UEs for inter-frequency handover. When a cell is in
overload congestion, the RNC shall select some UEs to release if failing to release
the cell from overload congestion by BE service TF control.
8
Load Control Algorithms
NodeB transmit
power (noise)
Icons for different load levels
Cell load
CAC or IAC: to prevent new calls into cells with heavy load
No Load DRD starts: to enable rejected UEs to retry neighboring cells or GSM cells
control
PUC starts: to enable UEs in idle mode to camp on cells with light load
LDR starts: to check and release initial congestion in cells
In a cell, the higher the cell load, the higher the NodeB transmit power (noise).
In this diagram, different icons indicates different load levels. And for different load
levels, the different load control algorithm will function.
9
Load Measurement
The objectives of LDM (LoaD Measurement)
Measure the system load
For LDR and OLC algorithms, the LDM algorithm needs to decide whether the
system works in basic congestion or overload congestion mode and to notify related
algorithms for handling.
Delay susceptibilities of PUC, CAC, LDR, and OLC to common measurement are
different. When some or all the algorithms use the same common measurement,
the LDM must apply different smoothed filter coefficients in order to get rippling and
timely common measurement as required.
10
LDM procedure
P ( n) = i =0
Pn : the reported measurement value
N
11
Parameters for LDM (1)
CHOICERPRTUNITFORULBASICMEAS
/CHOICERPRTUNITFORDLBASICMEAS (Time unit for UL/DL
basic meas rprt cycle)
Value Range: TEN_MSEC, MIN
Set the following parameters through SET LDM, query it through LST LDM.
12
Parameters for LDM (2)
TENMSECFORULBASICMEAS/TENMSECFORDLBASICMEA
S (UL/DL basic meas rprt cycle, Unit:10ms)
Value Range: 1~6000
MINFORULBASICMEAS/MINFORDLBASICMEAS (UL/DL
basic meas rprt cycle, Unit: min)
Value Range: 1~60
Notes:
1. [LDR period timer length] and [OLC period timer length] which are configured in
the command SET LDCPERIOD must be twice greater than the UL basic common
measurement report cycle.
2. [Intra-frequency LDB period timer length], [PUC period timer length], [LDR period
timer length] and [OLC period timer length] which are configured in the command
SET LDCPERIOD must be twice greater than the DL basic common measurement
report cycle.
13
Parameters for LDM (3)
ULBASICCOMMMEASFILTERCOEFF /
DLBASICCOMMMEASFILTERCOEFF (UL/DL basic common
measure filter coeff)
Value Range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13,
D15, D17, D19
Recommended value: D6
ULBASICCOMMMEASFILTERCOEFF / DLBASICCOMMMEASFILTERCOEFF
(UL/DL basic common measure filter coeff)
This parameter specifies the L3 filtering coefficient of the measurement value on the
NodeB side. The greater this parameter is, the greater the smoothing effect and the
higher the anti slow fading capability, but the lower the signal change tracing
capability. The change of this parameter has an effect on PUC, CAC, LDR
algorithms.
14
Parameters for LDM (4)
The parameters for smoothing filter window
Recommend
Parameter Name Parameter ID Value Range
Value
PUC moving average filter length PucAvgFilterLen 132 32
UL LDR moving average filter length UlLdrAvgFilterLen 132 25
DL LDR moving average filter length DlLdrAvgFilterLen 132 25
UL CAC moving average filter length UlCACAvgFilterLen 132 3
DL CAC moving average filter length DlCACAvgFilterLen 132 3
UL OLC moving average filter length UlOLCAvgFilterLen 132 25
DL OLC moving average filter length DlOLCAvgFilterLen 132 25
These parameters specify the length of smoothing filter window of the report
measurement value on the RNC side. The greater these parameters are, the
greater the smoothing effect, but the lower the signal change tracing capability.
15
Parameters for HSDPA LDM (1)
CHOICERPRTUNITFORHSDPAPWRMEAS (Time unit of
HSDPA need pwr meas cycle)
Value Range: TEN_MSEC, MIN
16
Parameters for HSDPA LDM (2)
TENMSECFORHSDPAPWRMEAS (HSDPA need pwr meas
cycle,Unit:10ms)
Value Range: 1~6000
Recommended value: 10, namely 100ms
17
Parameters for HSDPA LDM (3)
MINFORHSDPAPWRMEAS (HSDPA need pwr meas cycle,
Unit: min)
Value Range: 1~60
Recommended value: none
18
Parameters for HSDPA LDM (4)
HSDPANEEDPWRFILTERLEN (HSDPA need power filter len)
Value Range: 1~32
Recommended value: 1
These parameters specify the length of the smoothing filter window of HSDPA
power and bit rate requirement.
19
Priority
The service of user with low priority will be affected by the
load control algorithms first
User Priority: mainly applying to provide different QoS for different users. Eg.,
setting different GBR according to the level of users for BE service.
User Integrate Priority: defining different ARP (Allocation/Retention Priority) to the
user with the same User Priority.
RAB Integrate Priority: considering ARP, traffic class, THP (Traffic Handling Priority)
synthetically.
20
User Priority
There are three levels of user priority (1, 2, and 3)
gold (high), silver (middle) and copper (low) user
In CN HLR, we can set this priority; CN send ARP and user priority to RNC
21
User Priority
The relationship between user priority and ARP is configurable
The typical relationship as follow:
ARP 1 2 3 4 5 6 7 8 9 10 11 12 13 14
User Priority 1 1 1 1 1 2 2 2 2 2 3 3 3 3
22
RAB Integrate Priority
The values of RAB Integrate Priority are set according to the
following parameters
PRIORITYREFERENCE (Integrated Priority Configured
Reference)
Value range: ARP, TrafficClass
Set the parameter through SET USERPRIORITY, and query it through LST
USERPRIORITY.
If the value of the parameter is set to Traffic Class, the integrate priority abides by
the following rules:
Classes of services: conversational -> streaming -> interactive -> background
Services of the same class: priority based on Allocation/Retention Priority (ARP)
values
Only for the interactive service of the same ARP value: priority based on THP
Services of the same class and priority: HSDPA or DCH service preferred on the
basis of the value of the Indicator of Carrier Type Priority parameter
If the value of the parameter is set to ARP, the integrate priority abides by the
following rules:
ARP1 -> ARP2 -> ARP3 -> ARP14
Same ARP value: conversational -> streaming -> interactive -> background
THP
Indicator of Carrier Type Priority parameter
23
Example for RAB Integrate Priority
Based on ARP, HSDPA priority is higher
Service ARP Traffic Class Bear
ID type
When the user just has one RAB, User integrate priority is the same as the service
of the RAB integrate priority;
For multiple RAB users, the integrate priority of the user is based on the service of
the highest priority.
24
User Integrate Priority
For multiple-RAB users, the integrate priority of the user is
based on the service of the highest priority. User integrate
priority is mainly used to select different users during
LDR/OLC.
25
Contents
1. Load Control Overview
26
Contents
1. Load Control Overview
27
PUC Principles
Light load 1.Hard to trigger reselection Normal load
Freq1 Modify 2.Easy to camp on the cell
Stay
System Info Increase the POTENTIAL load System Info
SIB3,11,12 SIB3,11,12
28
PUC Realization
PUC can modify inter-frequency cell reselection parameters
to control the user distribution between cells.
Sintersearch: when the load of a cell is Heavy, PUC will
increase this parameter; when the load of a cell is Light, PUC
will decrease this parameter.
According to the load level of a cell, system will adjust the cell-reselection
parameters in SIB3, 11 and 12:
1. Sintersearch:
When the UE detects that the quality of the service cell (CPICH Ec/N0 measured by
the UE) is lower than the sum of the minimum quality criterion of the service cell
(Qqualmin) plus this threshold, it will start the inter-frequency cell reselection
process.
If this parameters are too high, cell reselection will probably start frequently,
resulting in UE battery waste; If they are too low, cell reselection will probably start
difficultly.
2. QOffset1sn and QOffset2sn:
These parameters are offsets of CPICH measured values of neighboring cells.
QOffset1sn is used for the RSCP measurement and the neighboring cell
measurement value participates in cell reselection sequencing after this offset is
deducted from it. QOffset2sn is used for the Ec/No measurement and the
neighboring cell measurement value participates in cell reselection sequencing after
this offset is deducted from it.
The bigger these values are, the smaller the probability of selecting the neighboring
cell will be; the smaller these values are, the bigger the probability of selecting the
neighboring cell will be.
29
Parameters for PUC Algorithm Switch
NBMSWITCH (Cell algorithm switch)
Value Range:
PUC
Set PUC period timer through SET LDCPERIOD, query it through LST
LDCPERIOD.
Note: [PUC period timer length must be twice greater than the DL basic common
measurement report cycle (default value is 200ms).
30
Parameters for PUC (1)
SPUCHEAVY (Load level division threshold 1)
Value Range: 0 to 100%
Set the following parameters through ADD CELLPUC, query it through LST
CELLPUC, and modify it through MOD CELLPUC.
31
Parameters for PUC (2)
OFFSINTERLIGHT (Sintersearch offset 1)
Value Range: -10 to 10
32
Parameters for PUC (3)
OFFQOFFSET1LIGHT (Qoffset1 offset 1)
Value Range: -20 to 20
33
Parameters for PUC (4)
OFFQOFFSET1HEAVY (Qoffset1 offset 2)
Value Range: -20 to 20
34
Contents
1. Load Control Overview
35
Why we need CAC?
WCDMA is an interference limited system, after a new call is
admitted, the system load will be increased
36
Flow chart of CAC
37
CAC Code Resource Admission
For handover services
The current remaining code resource should be enough for the
service
For handover services, the code resource admission is successful if the current
remaining code resource is enough for the service.
For other R99 services, RNC shall ensure the remaining code does not exceed the
configurable O thresholds after admission of the new service.
For HSDPA services, the reserved codes are shared by all HSDPA services; so the
code resource admission is not needed. The RNC adjusts the reserved HS-PDSCH
codes according to the real-time usage status of the codes.
38
Parameters for Code Resource Admission
DLHOCECODERESVSF (DL HandOver Credit and Code
Reserved SF)
Value Range:0, 1, 2, 3, 4, 5, 6, 7
Set this parameter through ADD CELLCAC, query it through LST CELLCAC, and
modify it through MOD CELLCAC.
39
CAC Power Resource Admission
Algorithm 1: based on UL/DL load measurement and load
prediction (RTWP and TCP)
The algorithm is easy to implement, but it is affected by the
result of RTWP and TCP measurement
When RTWP and/or TCP measurement value are/is invalid/unavailable, the CAC
will change from algorithm 1 to 2 automatically.
When measurement are/is valid/available, the CAC will change back to algorithm 1
automatically.
In principle, a request will be admitted only when UL and DL are both admitted. But
if UL or DL CAC switch is closed, only one direction CAC also can be realized.
40
Uplink CAC Algorithm 1 - Load Prediction
Admission request
PN
Get current RTWP, and calculate the
current load factor
UL = 1
RTWP
Get the traffic characteristic, and
estimate the increment of load factor
Calculate the predicted load factor UL _ predicted = UL +
Smaller than
Y N
the threshold?
admitted rejected
End of UL CAC
41
Downlink CAC Algorithm 1 - Load Prediction
Admission request
Smaller than
Y N
the threshold?
admitted rejected
End of DL CAC
42
Uplink and Downlink CAC Algorithm 2 - ENU
Admission request
N
Get current total ENU ENU total (N ) = ENU i
i =1
Calculate the predicted ENU ENU total ( N + 1) = ENU total ( N ) + ENU new
Y
Smaller than
N
ENULoad = ENU total ( N + 1) / ENU max
the threshold?
admitted rejected
43
Typical equivalent number of users
Equivalent Number of User (ENU)
Service
For Already Existing Users For New Incoming Call
3.4 kbit/s SIG 0.2669 0.4569
13.6 kbit/s SIG 0.4531 1.2131
3.4 + 12.2 kbit/s 0.7662 1.3210
3.4 + 8 kbit/s (PS) 0.5106 0.6325
3.4 + 16 kbit/s (PS) 0.9215 1.0472
3.4 + 32 kbit/s (PS) 2.1319 2.2680
3.4 + 64 kbit/s (PS) 3.2479 3.4188
3.4 + 128 kbit/s (PS) 6.2219 6.4143
3.4 + 144 kbit/s (PS) 6.9731 7.1888
3.4 + 256 kbit/s (PS) 11.2941 11.5245
3.4 + 384 kbit/s (PS) 17.0178 17.1897
44
Parameters for Power Resource
Admission Algorithm Switch
NBMULCACALGOSELSWITCH (Uplink CAC algorithm
switch)
Value Range:
ALGORITHM_OFF, ALGORITHM_FIRST,
ALGORITHM_SECOND, and ALGORITHM_THIRD
45
Parameters for Load Prediction (1)
CELLENVTYPE (Cell environment type)
Value Range:
TU: typical urban district RA: rural area HT: hill terrain
Default value: TU
Set the following CAC parameters through ADD CELLCAC, query it through LST
CELLCAC, and modify it through MOD CELLCAC.
46
Parameters for Load Prediction (2)
ULINTERFACTOR (UL neighbor interference factor )
Value Range: 0 to 200
47
Parameters for Power Resource
Admission (1)
ULCCHLOADFACTOR (UL common channel load factor)
Value range: 0 to 100%
48
Parameters for Power Resource
Admission (2)
ULCONVAMRTHD (UL threshold of Conv AMR service)
Value range: 0 to 100%
The UL load factor thresholds include this parameter, [UL threshold of Conv AMR
service], [UL handover access threshold], and [UL threshold of other services]. The
four parameters can be used to limit the proportion between conversational service,
handover user and other services in a specific cell, and to guarantee the access
priority of conversational service.
49
Parameters for Power Resource
Admission (3)
ULOTHERTHD (UL threshold of other services)
Value range: 0 to 100%
50
Parameters for Power Resource
Admission (4)
DLCONVAMRTHD (DL threshold of Conv AMR service)
Value range: 0 to 100%
The DL load factor thresholds include this parameter, [DL threshold of Conv
non_AMR service], [DL handover access threshold], and [DL threshold of other
services]. The four parameters can be used to limit the proportion between
conversational service, handover user and other services in a specific cell, and to
guarantee the access priority of conversational AMR service.
51
Parameters for Power Resource
Admission (5)
DLOTHERTHD (DL threshold of other services)
Value range: 0 to 100%
52
Parameters for Power Resource
Admission (6)
ULTOTALEQUSERNUM (UL total equivalent user number)
Value range: 1 to 200
53
CAC Credit Resource Admission
Credit resource admission is similar with code resource
admission
For handover service, the credit resource admission is successful if the current
remaining credit resource is enough for the service.
For other R99 and HSUPA service, RNC shall ensure the remaining credit of the
local cell, local cell group (if any), NodeB does not exceed the configurable O&M
thresholds (Ul HandOver Credit Reserved SF/ Dl HandOver Credit and Code
Reserved SF) after admission of the new service.
For HSDPA service, no credit resource needed.
54
Parameters for Credit Resource
Admission (1)
DLHOCECODERESVSF (DL HandOver Credit and Code
Reserved SF)
Value Range:0, 1, 2, 3, 4, 5, 6, 7
Set this parameter through ADD CELLCAC, query it through LST CELLCAC, and
modify it through MOD CELLCAC.
55
Parameters for Credit Resource
Admission (2)
ULHOCERESVSF (Ul HandOver Credit Reserved SF)
Value Range:0, 1, 2, 3, 4, 5, 6, 7
Set this parameter through ADD CELLCAC, query it through LST CELLCAC, and
modify it through MOD CELLCAC.
56
Contents
1. Load Control Overview
57
Why we need IAC?
The disadvantage of CAC:
For PS NRT (Non-Real Time) services, CAC is not flexible
IAC can increase admission successful rate through the following methods:
1. The data rate of PS service is not fixed, so maybe the cell can admit the UE
after the data rate is decreased.
2. Since the service is non-real time, the users can wait a short time, then access
to the cell.
3. The user with high priority can preempt the resource of users with low priority.
4. If the load of neighboring cell is not Heavy, UE may be admitted to the
neighboring cell directly.
58
Flow chart of IAC
The IAC procedure includes rate negotiation, DRD, preemption and queuing.
59
IAC Rate negotiation
Iu QoS Negotiation: based
Maximum allowed bit rate on the UE capability
384kbps Physical layer capability
128kbps
RAB Downsizing: based on
Initial / Target data rate
64kbps system load
Channelization codes
32kbps
Iub transmission resources
Radio resources
60
IAC Direct Retry based on service
Data service can be retry to HSDPA cells for better QoS
Data
service
Frequency B
CELL A HSDPA
61
IAC Preemption
The user with high priority can preempt the resource of
users with low priority
High priority
Preempting resource
Low priority
62
IAC Queuing
After CAC rejection, UE can wait a moment and queue, then
try to admit again
63
IAC Directed Retry based on Load
Balance
Service will be set up to the cell with lightest load
The advantages
Keeping the load of the network balanced
Cell 1 Cell 1
Cell 2 Cell 2
RRC RAB
Connection
If the load of neighboring cell is lighter than current cell, UE may be admitted to the
neighboring cell directly.
The RAB DRD procedure is as follows:
1. The RNC determines the admission of the inter-frequency target cell for blind
handover.
2. If the admission is accepted, DRD procedure is performed for the inter-
frequency target cell for blind handover.
3. The RNC starts the RL setup procedure to complete the inter-frequency hard
handover.
4. The RNC starts the RB setup procedure to complete the inter-frequency hard
handover on the Uu interface and the service setup.
64
Parameters for IAC Algorithm Switch (1)
IU_QOS_NEG_SWITCH (Switcher for IU QoS Negotiation)
Value range: 0 (close), 1 (open)
Default value: 0
Default value: 1
65
Parameters for IAC Algorithm Switch (2)
PREEMPTALGOSWITCH (Preempt algorithm switch)
Value range: On, Off
66
Parameters for RAB Downsizing
ULBETRAFFINITBITRATE (Uplink initial access rates) &
DLBETRAFFINITBITRATE (Downlink initial access rates)
Value range: D8, D16, D32, D64, D128, D144, D256, D384,
D768, D1024, D1536, D2048
Physical Value range: 8, 16, 32, 64, 128, 144, 256, 384, 768,
1024, 1536, 2048, Unit: kbps
Set the parameter through SET FRC, and query it through LST FRC.
When the initial rate selection (RAB Downsizing) function is enabled, this value is
the uplink/downlink initial access rate when the BE service is set up. If this rate
access fails to satisfy the current load condition, then the actual initial access rate is
the negotiated rate based on this rate.
When the RAB Downsizing function is disabled, this parameter is the
uplink/downlink initial access rate when the BE service is set up.
The higher this parameter set, the shorter the time fro the BE service to reach the
maximum rate but the easier for adjustment downward through negotiation when
the system is congested, so it makes no sense to set it too high.
The smaller this parameter, the easier for the BE service to access as per this rate,
but, if it is set too low, it will take a longer time to adjust to the required rate when
there is a service requirement.
67
Parameters for Queuing (1)
QUEUELEN (Queue length)
Value range: 5 to 20
Recommended value: 10
Set the parameters through SET QUEUEPREEMPT, and query them through LST
QUEUEPREEMPT.
68
Parameters for Queuing (2)
MAXQUEUETIMELENx (Max queuing time length 1~12)
Value range: 1 to 60s
Set the parameters through SET QUEUEPREEMPT, and query them through LST
QUEUEPREEMPT.
69
Parameters for DRD (1)
DRMAXUMTSNUM (Max inter-frequency direct retry
number)
Value range: 0 to 5
Recommended value: 2
70
Parameters for DRD (2)
R99CSSEPIND (R99 CS separation indicator)
Value range: FALSE (no separation), TRUE (separation)
According to the cell type (R99 or R99+HSDPA), an HSDPA user accessing the
R99 cell can be DRDed to a R99+HSDPA cell. According to these two parameters,
a R99 user accessing the R99+HSDPA cell can be DRDed to a R99 cell.
71
Contents
1. Load Control Overview
72
LCC (Load Congestion Control)
Load%
100%
Overload state: OLC will be
section A
used
THOLC
1 2
section B
Basic congestion state: LDR
THLDR
will be used
section C
Normal state: Permit entry
Times
LCC (Load Congestion Control) consist of LDR (Load Reshuffling) and OLC
(OverLoad Control).
In basic congestion state, LDR will be used to optimize resource distribution, the
main rules is not to affect the feeling of users as possible as we can.
In overload state, OLC will be used to release overload state quickly, keep system
stability and the service of high priority users.
73
LDR (Load Reshuffling)
Reasons
When the cell is in basic congestion state, new coming calls
could be easily rejected by system
Purpose
Optimizing cell resource distribution
Triggering of LDR
Power resources, code resource, Iub resources or Iub
bandwidth, NodeB Credit resource
The resources that can trigger the basic congestion of the cell are:
Power resources
If the current UL/DL load of the R99 cell is not lower than UL/DL LDR Trigger
threshold (basic congestion control threshold in UL/DL), the cell works in basic
congestion state and the related load reshuffling actions are taken.
Code resource
If the current remaining code of the cell is higher than Cell SF reserve threshold,
code congestion is triggered and related load reshuffling actions are taken.
Iub resources or Iub bandwidth
Iub congestion control in both the uplink and downlink is NodeB-oriented. Load
trigger threshold and load release threshold are set for the uplink and the downlink
separately.
Iub congestion control is implemented in a separate process module, so its
functionality does not controlled by LDR switchers.
NodeB Credit resource
If the UL/DL current remaining credit resource is higher than Ul Credit SF reserved
threshold/ Dl Credit SF reserved threshold, credit congestion is triggered and
related load reshuffling actions are taken.
74
LDR procedure
Turn on LDR algorithm switch
N
Current LDR state = congested?
Inter-freq Y
Succeed?
load handover
N
Code Y
Succeed?
reshuffling
N
BE rate Y
Succeed?
reduction
N
Sequence of Inter-system
Y
actions can be handover Succeed? Mark
configured in CS domain Wait time
N "current action
(current action for LDR
Inter-system = successful
is taken firstly) Y action duration
handover Succeed? action"
in CS domain
N
AMR rate Y
Succeed?
reduction
N
QoS renogiation Y
on Iu interface
Succeed?
N
MBMS power Y
reduction
Succeed?
N
No related action can be found
Mark "current action = first LDR action"
75
Resource Power Iub Code Credit
UL/DL UL DL UL DL DL UL DL
Inter-Frequency
Load Handover
BE Rate
Reduction
Inter-system
Handover in CS
Domain
Inter-System
LDR Handover in PS
Actions Domain
AMR Rate
Reduction
Iu QoS
Negotiation
Code Reshuffling
MBMS Power
Reduction
76
LDR Actions - Inter-frequency Load
Handover
Target cells
Load difference between current load and the basic
congestion trigger threshold of target cell is larger than
UL/DL Inter-freq cell load handover load space threshold
Target users
Based on user priority and the current service rate
Result
The load of two cells is lower than the basic congestion
trigger threshold
The user with low priority hand over to the Light load cells
It is implemented as follows:
1. The LDR check whether the existing cell has a target cell of inter-frequency
blind handover. If there is no such a target cell, the action fails, and the LDR
performs the next action.
2. The LDR checks whether the load difference between the current load and the
basic congestion trigger threshold of each target cell for blink handover is larger
than UL/DL Inter-freq cell load handover load space threshold (Both uplink and
downlink condition must be all fulfilled). If the basic congestion trigger threshold
is not set, the admission threshold of the cell is used. If the difference is not
larger than the threshold, the action fails. The LDR performs the next action.
3. If the LDR finds out a target cell that meets the specified blind handover
conditions, the LDR selects one UE to make an inter-frequency blind handover,
depending on the UEs integrate priority and occupied bandwidth. The selected
UE has lower integrate priority and its bandwidth is less than and has the least
difference between the UL/DL Inter-freq cell load handover maximum
bandwidth parameter. If the LDR cannot find such a UE, the action fails. The
LDR performs the next action.
77
LDR Actions - BE Rate Reduction
Candidate RABs
The data rate of BE service is larger than GBR
Target RABs
Rank the candidate RABs by the integrate priority, the low
priority RABs reduce BE rate first
Result
Cell load is decreased under basic congestion trigger threshold
78
LDR Actions - Uncontrolled Real-time
QoS Renegotiation
Target RABs
Rank the candidate RABs by the integrate priority, the service
with lowest priority and current data rate higher than GBR will
be selected
Result
Cell load is decreased under basic congestion trigger threshold
The load is reduced by adjusting the rate of the real-time services through
uncontrolled real-time OoS renegotiation.
Upon receipt of the message, the CN sends the RAB ASSIGNMENT
REQUEST message to the RNC for RAB parameter reconfiguration. Based on
this function, the RNC can adjust the rate of real-time services to reduce the
load.
The LDR algorithm is implemented as follows:
1. Based on the integrate priority, the LDR sorts the real-time services in the PS
domain in descending order. The top services are selected for QoS
renegotiation.
2. The LDR performs QoS renegotiation for the selected services. The GBR
during service setup is the maximum rate of the service after QoS renegotiation.
3. The RNC initiates the RAB Modification Request message to the CN for QoS
renegotiation.
4. If the RNC cannot find a proper service for QoS renegotiation, the action fails.
The LDR performs the next action.
79
LDR Actions - Inter-system Handover
In the CS/PS Domain
Target user
Based on the integrate priority, sorting the UEs in descending
order. The top CS/PS services are selected
GSM cell
WCDMA cell
Result
Cell load is decreased under basic congestion trigger threshold
The 2G and 3G systems have different cell sizes and coverage modes.
Therefore, blind handover across systems is not taken into account.
The LDR is implemented in the downlink (e.g.) as follows:
1. Based on the integrate priority, the LDR sorts the UEs in descending order. The
top CS/PS services are selected.
2. For the selected UEs, the LDR sends the load handover command to the inter-
system handover module to ask the UEs to hand over to the 2G system.
3. The handover module decides to trigger inter-system handover, depending on
the capability of the UE and the capability of the algorithm switch to support the
compression mode.
4. This action is successful if any load handover UE is found. Otherwise, this
action fails.
80
LDR Actions - AMR Rate Reduction
Target user (downlink e.g.)
Candidate RABs: users accessing the AMR services
(conversational) and with the bit rate higher than the GBR
Result
Cell load is decreased under basic congestion trigger threshold
The AMR user with low priority is reduced to low voice rate
mode
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 is implemented as follows:
1. Based on the integrate priority, the LDR sorts the RABs in the descending
order. The top UEs accessing the AMR services (conversational) and with the
bit rate higher than the GBR are selected.
2. In downlink, the RNC sends the Rate Control request message through the Iu-
UP to the CN to adjust the AMR rate to the GBR.
3. In uplink, The RNC sends the TFC CONTROL command to the UE to adjust the
AMR rate to the assured rate.
4. If the RNC cannot find a proper service for AMR rate reduction, the action fails.
The LDR performs the next action.
81
LDR Actions - Code Reshuffling
Purpose
Cell load is decreased under basic congestion trigger threshold
SF=4
SF=8
SF=16 7
SF=32
3 C 5
SF=64
1 2 4 A 6 B
SF=128
When code resources are in basic congestion state, sufficient code resources
can be reserved for subsequent service access through code reshuffling.
The LDR algorithm is implemented as follows:
1. Select a subtree. Ensure that the number of users in the subtree is not higher
than Max user number of code adjust.
2. Treat each user in the subtree as a new user and allocate code resources to
each user.
3. Initiate the reconfiguration procedure for each user in the subtree and
reconfigure the channel codes of the users to the newly-allocated code
resources.
4. The reconfiguration procedure on the air interface is implemented through the
PHYSICAL CHANNEL RECONFIGURATION message and that on the Iub
interface through the RL RECONFIGURATION message.
82
LDR Actions - MBMS Power Reduction
Purpose
The downlink power load can be reduced by lowering power on
MBMS traffic channels
83
Parameters for LDR Algorithm Switch
NBMLdcAlgoSwitch (Cell algorithm switch)
Value Range:
ULLDR, DLLDR, CELL_CODE_LDR, CELL_CREDIT_LDR
Set LDR Algorithm Switch through ADD CELLALGOSWITCH, query it through LST
CELLALGOSWITCH, and modify it through MOD CELLALGOSWITCH.
84
Parameters for LDR Algorithm Priority
Priority for load reshuffling
Value Range:
IUBLDR(Iub load reshuffling), CREDITLDR(Credit load
reshuffling), CODELDR (Code load reshuffling), UULDR (Uu load
reshuffling)
Default status:
LdrFirstPri = IUBLDR
LdrSecondPri = CREDITLDR
LdrThirdPri = CODELDR
LdrFourthPri = UULDR
Set LDR Algorithm Switch through SET LDCALGOPARA, query it through LST
LDCALGOPARA, and modify it through MOD LDCALGOPARA.
85
Parameters for Triggering of Power
Resource (1)
ULLDRTRIGTHD (UL LDR trigger threshold)
Value range: 0 to 100%
Set the following parameters through ADD CELLLDM, query it through LST
CELLLDM, and modify it through MOD CELLLDM.
When uplink basic congestion status is triggered, the uplink LDR action will be
started. LDR control objective is to preserve space for admission to increase the
success rate. Therefore under the current policy, the LDR trigger threshold shall be
so set that the congestion is less than or close to the concerned admission
threshold index.
The smaller the LDR trigger threshold and release threshold, the easier the system
is in preliminary congestion status, the harder it is released from this status, the
easier the LDR action happens, and the more likely the users are affected. However,
since the resources are preserved, the admission success rate becomes higher.
The carrier shall make tradeoff between these factors.
The uplink LDR trigger thresholds must be greater than uplink LDR release
thresholds, and the recommended difference between the two thresholds is larger
than 10%, otherwise maybe the basic congestion state is Ping-Pong.
86
Parameters for Triggering of Power
Resource (2)
DLLDRTRIGTHD (DL LDR trigger threshold)
Value range: 0 to 100%
When downlink basic congestion status is triggered, the downlink LDR action will be
started. LDR control objective is to preserve space for admission to increase the
success rate. Therefore under the current policy, the LDR trigger threshold shall be
so set that the congestion is less than or close to the concerned admission
threshold index.
The smaller the LDR trigger threshold and release threshold, the easier the system
is in preliminary congestion status, the harder it is released from this status, the
easier the LDR action happens, and the more likely the users are affected. However,
since the resources are preserved, the admission success rate becomes higher.
The carrier shall make tradeoff between these factors.
The downlink LDR trigger thresholds must be greater than downlink LDR release
thresholds, and the recommended difference between the two thresholds is larger
than 10%, otherwise maybe the basic congestion state is Ping-Pong.
87
Parameters for Triggering of Code
Resource and Credit Resource
CELLLDRSFRESTHD (Cell LDR SF reserved threshold)
Value Range:0, 1, 2, 3, 4, 5, 6, 7
Set the following parameters through ADD CELLLDR, query it through LST
CELLLDR, and modify it through MOD CELLLDR.
88
Parameters for LDR Period
LDRPERIODTIMERLEN (LDR period timer length)
Value range: 1 to 86400 unit: second
Set this parameters through SET LDCPERIOD, query it through LST LDCPERIOD.
89
Parameters for LDR Action Sequence
UL (DL) LDRFIRSTACTION (UL/DL LDR First action) ~
Set the following parameters through ADD CELLLDR, query it through LST
CELLLDR, and modify it through MOD CELLLDR.
This set of parameters determines the action sequence for the uplink/downlink LDR.
NOACT: NO ACTION
INTERFREQLDHO: INTER-FREQ LOAD HANDOVER
BERATERED: BE TRAFF RATE REDUCTION
QOSRENEGO: UNCONTROLLED REAL-TIME TRAFF QOS RE-NEGOTIATION
CSINTERRATLDHO: CS DOMAIN INTER-RAT LOAD HANDOVER
PSINTERRATLDHO: PS DOMAIN INTER-RAT LOAD HANDOVER
AMRRATERED: AMR TRAFF RATE REDUCTION
90
Parameters for LDR Code Reshuffling
MAXUSERNUMCODEADJ (Max user number of code
adjust)
Value range: 1 to 3
Recommended value: 1
91
Parameters for LDR Inter-Frequency
Load Handover (1)
ULINTERFREQHOCELLLOADSPACETHD (UL Inter-freq
cell load handover load space threshold)
Value range: 0 to 100%
Inter-frequency load handover happens only when the current load space of the
target cell is higher than this parameter setting. This parameter value is relative to
target cell LDR threshold.
The smaller this parameter value is, the easier it is to find qualified target cell for
blind handover.
However, too low value easily makes the target cell enter congestion status. The
larger the value, the more difficult for the interfrequency blind handover to happen
and the easier to guarantee the stability of the target cell.
92
Parameters for LDR Inter-Frequency
Load Handover (2)
ULINTERFREQHOBWTHD (UL Inter-freq cell load
handover maximum bandwidth)
Value range: 0 to 400000bps
93
Parameters for LDR Other Actions
UL (DL) LDRBERATEREDUCTIONRABNUM,
UL (DL) LDRPSRTQOSRENEGRABNUM,
UL (DL) LDRCSINTERRATHOUSERNUM,
UL (DL) LDRPSINTERRATHOUSERNUM,
ULLDRAMRRATEREDUCTIONRABNUM
Value range: 1 to 10
Default value
UL (DL) LDRBERATEREDUCTIONRABNUM: 1
UL (DL) LDRPSRTQOSRENEGRABNUM: 1
UL (DL) LDRCSINTERRATHOUSERNUM: 3
UL (DL) LDRPSINTERRATHOUSERNUM: 1
UL (DL) LDRAMRRATEREDUCTIONRABNUM: 3
This set of parameters determines the action sequence for the uplink/downlink LDR.
UL (DL) LDRBERATEREDUCTIONRABNUM: UL/DL LDR-BE rate reduction RAB
number
UL (DL) LDRPSRTQOSRENEGRABNUM: UL/DL LDR un-ctrl RT Qos re-nego
RAB number
UL (DL) LDRCSINTERRATHOUSERNUM: UL/DL LDR CS inter-rat ho user
number
UL (DL) LDRPSINTERRATHOUSERNUM: UL/DL LDR PS inter-rat ho user number
UL (DL) LDRAMRRATEREDUCTIONRABNUM: UL/DL LDR-AMR rate reduction
RAB number
The larger these parameters are, the more obviously the current cells load is
reduced. Its cost is that user feelings are affected and that it gives rise to congestion
of the target cell. The smaller these parameters are, the smaller the amplitude of
the load adjusted by LDR. Its benefit is that the QoS is guaranteed and the target
cell load is stable.
94
Contents
1. Load Control Overview
95
OLC (Over Load Control)
Reasons
In overload state, system is not stable
Purpose
Ensuring the system stability and making the system back to
the normal state as soon as possible
Triggering of OLC
Power resources only
After the UE access is granted, the power consumed by a single link is adjusted by
the single link power control algorithm. The power varies with the mobility of the UE
and the changes in the environment and the source rate. In some situations, the
total power load of the cell may be higher than the target load. To ensure system
stability, overload congestion must be handled. The OLC includes:
Restricting the TF (Transmission Format) of the BE service
Choosing and releasing some UEs
Only power resources could result in overload congestion. Hard resources such as
equivalent user number, Iub bandwidth, and credit resources do not cause overload
congestion.
96
OLC Procedure
97
OLC Actions - TF Control
Target user
Rank the candidate users by the integrate priority, the low
priority user will be selected
Execution
Send the control message to UE (downlink: TF control
indication, uplink: Transport format combination control) to
restricts the TFC selection
98
OLC Actions - Release of Some UEs
Target user (downlink e.g.)
Rank the candidate users by the integrate priority, the low
priority user will be selected
Execution
Releasing the service of the selected user
99
Parameters for OLC Algorithm Switch
NBMSWITCH (Cell algorithm switch)
Value Range:
ULOLC, DLOLC
Set OLC Algorithm Switch through ADD CELLALGOSWITCH, query it through LST
CELLALGOSWITCH, and modify it through MOD CELLALGOSWITCH.
100
Parameters for Triggering of Overload (1)
ULOLCTRIGTHD (UL OLC trigger threshold)
Value range: 0 to 100%
Set these parameters through ADD CELLLDM, query it through LST CELLLDM,
and modify it through MOD CELLLDM.
The uplink OLC trigger threshold judges whether the system uplink is in overload
status. If the cell load is consecutively higher than the threshold for pre-determined
times, it means the system is in overload status for a long time. Under this
circumstance, if the cells OLC switch is open, the system will perform OLC
algorithm, including fast TF restriction or even user release.
The smaller the OLC trigger threshold is, the easier the system will be in overload
status. Since OLC will ultimately use extreme method like user release to lower the
load, too low value will be very detrimental to the system performance.
The smaller the OLC release threshold is, the harder for the system to release the
overload. Since the consequence of overload is not as severe as expected, it is
desirable to set the two parameters a bit higher given that the difference between
OLC trigger threshold and OLC release threshold is fixed.
The uplink OLC trigger thresholds must be greater than up OLC release thresholds,
and the recommended difference between the two thresholds is larger than 10%,
otherwise maybe the basic congestion state is Ping-Pong.
101
Parameters for Triggering of Overload (2)
DLOLCTRIGTHD (DL OLC trigger threshold)
Value range: 0 to 100%
Set these parameters through ADD CELLLDM, query it through LST CELLLDM,
and modify it through MOD CELLLDM.
The downlink OLC trigger threshold judges whether the system downlink is in
overload status. If the cell load is consecutively higher than the threshold for pre-
determined times, it means the system is in overload status for a long time. Under
this circumstance, if the cells OLC switch is open, the system will perform OLC
algorithm, including fast TF restriction or even user release.
The smaller the OLC trigger threshold is, the easier the system will be in overload
status. Since OLC will ultimately use extreme method like user release to lower the
load, too low value will be very detrimental to the system performance.
The smaller the OLC release threshold is, the harder for the system to release the
overload. Since the consequence of overload is not as severe as expected, it is
desirable to set the two parameters a bit higher given that the difference between
OLC trigger threshold and OLC release threshold is fixed.
The downlink OLC trigger thresholds must be greater than down OLC release
thresholds, and the recommended difference between the two thresholds is larger
than 10%, otherwise maybe the basic congestion state is Ping-Pong.
102
Parameters for OLC (1)
OLCPERIODTIMERLEN (OLC period timer length)
Value range: 100 to 86400000, unit: ms
Set this parameters through SET LDCPERIOD, query it through LST LDCPERIOD.
This parameter is the period of the OLC timer. When this period is up, OLC
executes once and then restarts automatically. The period of the timer is the period
of the OLC action. The uplink OLC and downlink OLC share the same timer.
If the OLC action period is set too long, the system may respond very slowly to
overload;
If the OLC action period is set too short, unnecessary adjustment may occur before
the previous OLC action has taken effect, thus affecting the system performance.
103
Parameters for OLC (2)
ULOLCFTFRSTRCTTIMES (UL OLC fast TF restrict times)
Value range: 0 to 100
Recommended value: 3
Recommended value: 3
Set the following parameters through ADD CELLOLC, query it through LST
CELLOLC, and modify it through MOD CELLOLC.
When uplink/downlink overload is triggered, the RNC will immediately execute OLC
action by first executing uplink/downlink fast TF restriction. The internal counter is
incremented by 1 with each execution. If the number of overloads does not exceed
the OLC action threshold, the system lowers the BE service rate by lowering TF to
try to relieve the overload. Exceeding OLC action threshold means that the previous
operation has no obvious effect on alleviating the overload and the system has to
release users to solve the overload problem.
The lower the parameter value, the more likely the users are released, resulting in
negative effect on the system performance. If the parameter value is set too high,
the overload status is released slowly.
104
Parameters for OLC (3)
ULOLCFTFRSTRCTRABNUM (UL OLC fast TF restrict
RAB number)
Value range: 1 to 100
Recommended value: 3
Recommended value: 3
The higher the parameter value, the more users involved in fast TF restriction under
identical conditions, the quicker the cell load decreases, and the more users QoS
affected.
105
Parameters for OLC (4)
RATERSTRCTCOEF (DL OLC fast TF restrict data rate
restrict coefficient)
Value range: 1 to 99%
OLC fast TF restriction rate coefficient means the degree of the rate restriction.
The smaller the parameter value, the more severe the rate is restricted. Too low
value may affect the BE transmission delay. Large value means loose restriction,
which may be ineffective in alleviating the overload.
106
Parameters for OLC (5)
RATERSTRCTTIMERLEN (DL OLC fast TF restrict data
rate restrict timer length)
Value range: 1 to 65535, unit: ms
107
Parameters for OLC (6)
ULOLCTRAFFRELRABNUM (UL OLC traff release RAB
number)
Value range: 0 to 10
Default value: 0
Default value: 0
The higher the parameter value, the more obvious the cell load decreases at the
cost of negatively affecting user feelings.
108
Thank You
www.huawei.com
109