OWO117090 WCDMA RAN15 Load Congestion Control Algorithm and Parameters ISSUE1.00

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)
Confidential Information of Huawei. No Spreading Without Permission
Each cell has its own set of load control functions that are responsible for monitoring and
controlling the resources of the cell. The load control functions monitor the load condition
of the cell through load measurement, make the admission decision for services through
intelligent access control and call admission control, and relieve congestion in a cell.
Load control functions in different UE access phases
Before UE access: Potential User Control (PUC)
During UE access: Intelligent Access Control (IAC) and Call Admission Control (CAC)
After UE access: Inter-Frequency Load Balancing Based on Configurable Load

Threshold(CLB), intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and
Overload Control (OLC)
LCC (Load Congestion Control) consist of LDR (Load Reshuffling) and OLC (Over Load
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 reduce cell load quickly, keep system stability and
the service of high priority users.
WCDMA Admission Control Algorithm and Parameters
In CN HLR, operator can set ARP (Allocation Retention Priority ). During service setup, CN
sends ARP to RNC. Based on the mapping relation (configured in RNC), RNC can identify
the users priority, namely gold, silver or copper one.
User priorities are adopted to provide differentiated services for users. For ease of
application, the RNC maps the 15 levels of Allocation/Retention Priority (ARP) that is
carried in the RAB ASSIGNMENT REQUEST message from the core network (CN) onto three
user priorities, that is, gold (high priority), silver (medium priority), and copper (low priority).
The relation between user priority and ARP can be set through SET UUSERPRIORITY
command.
If ARP is not received in messages from the Iu interface, the user priority is regarded as
copper.
The values of RAB integrated priority are set according to the integrated priority configuration
reference parameter (PriorityReference):
If PriorityReference is set to ARP, the integrated priority abides by the following rules:
ARP: ARP1 > ARP2 > ARP3 > ... > ARP14 >ARP15
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 > THP15
Services of the same ARP, traffic class and THP (only for interactive services): HSPA
or DCH service preferred depending on CarrierTypePriorInd.
If PriorityReference is set to Traffic Class, the integrated priority abides by the following
rules:
Traffic classes: conversational > streaming > interactive > background
Services of the same traffic class: priority based on ARP, that is, ARP1 > ARP2 >
ARP3 > ... > ARP14 > ARP15
Only for the interactive service of the same ARP : priority based on Traffic Handling
Priority (THP) that is carried in the RAB ASSIGNMENT REQUEST message, that is,
THP1 > THP2 > THP3 > ... > THP14 > THP15
Services of the same traffic class, ARP and THP (only for interactive services): High
Speed Packet Access (HSPA) or Dedicated Channel (DCH) service preferred
depending on CarrierTypePriorInd.
This example shows the RAB integrated priority calculation in 2 different conditions.
A user may have multiple RABs, and the RABs may have different priorities. In this case, the
highest priority is taken as the priority of this user. Such a priority is called user integrated
priority. User integrated priority is used in user-specific load control. For example, the
selection of R99 users during preemption, the selection of users during inter-frequency
load handover for LDR, and the selection of users during switching of BE services to
common channels are performed according to the user integrated priority.
When the usage of cell resource exceeds the basic congestion triggering threshold, the cell
enters the basic congestion state. In this case, Load Reshuffling (LDR) is required to reduce
the cell load and increase the access success rate.
The basic congestion of a cell can be caused by power resource, code resource, Iub
resource, or NodeB credit resource. For power resource, the RNC performs periodic
measurement and checks whether the cells are congested. For code, Iub, and NodeB credit
resources, the RNC checks whether the cells are congested when resource usage changes.
If the congestion of all resources is triggered in a cell, the basic congestion triggered by
different resource will be relieved in order of resource priority for load reshuffling as
configured through the SET ULDCALGOPARA command.
Congestion control based on power resource can be enabled through the DL_UU_LDR
and UL_UU_LDR subparameters of the NBMLdcAlgoSwitch parameter.
The above figure shows the triggering and relieving of basic congestion:
if the UL/DL load of the cell is higher than or equal to the UL/DL LDR trigger
threshold (UlLdrTrigThd or DlLdrTrigThd) for a hysteresis time, the cell is in the
basic congestion state, and the related load reshuffling actions.
If the current UL/DL load of the cell is lower than the UL/DL LDR relief threshold
(UlLdrRelThd or DlLdrRelThd) for a hysteresis time, the cell changes to the
normal state and the related load reshuffling actions are stopped.
If a DC-HSDPA cell group is in the basic congestion state, the related LDR actions are
performed in each cell separately.
The DL LDR trigger threshold of a DC-HSDPA cell group equals the sum of the DL
LDR trigger thresholds of the two cells in this group.
The DL LDR relief threshold of a DC-HSDPA cell group equals the sum of the DL
LDR relief thresholds of the two cells in this group.
In a DC-HSUPA cell, LDR triggering and execution happen in the two cells respectively.
For the downlink, the hysteresis time is specified by the DlLdTrnsHysTime parameter; for
the uplink, the hysteresis time is 600ms.
Power Resource:
Load level > LDR trigger threshold
Iub Bandwidth:
Available Iub bandwidth < predefined threshold
NBMLdcAlgoSwitch-UL_UU_LDR/DL_UU_LDR
UL_UU_LDR: UL UU load reshuffling algorithm. When the cell is heavily loaded in

UL, this algorithm reduces the cell load in UL by using inter-frequency load
handover, BE service rate reduction, uncontrollable real-time service QoS
renegotiation, CS should be inter-RAT, PS should be inter-RAT handover, CS should
not be inter-RAT handover, PS should not be inter-RAT handover and AMR service
rate reduction.
DL_UU_LDR: DL UU load reshuffling algorithm. When the cell is heavily loaded in
DL, this algorithm reduces the cell load in DL by using inter-frequency load
handover, BE service rate reduction, uncontrollable real-time service QoS
renegotiation, CS should be inter-RAT, PS should be inter-RAT handover, CS should
not be inter-RAT handover, PS should not be inter-RAT handover, AMR service rate
reduction and MBMS service power decrease.
Value range: OFF, ON

Physical value range: 0, 1
Set this parameter through ADD UCELLALGOSWITCH/ MOD UCELLALGOSWITCH.
UlLdrTrigThd/DlLdrTrigThd
Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is not
lower than this threshold, the UL/DL load reshuffling function of the cell is
triggered. After the basic congestion state of the cell load is released, the system
no longer implements the LDR action. Because the load fluctuates, the difference
between the LDR release threshold and trigger threshold should be higher than
10%. The lower the LDR trigger and release thresholds are, the easier the system
enters the preliminary congestion status, the harder it is released from this status,
the easier the LDR action is triggered, and the more likely the users are affected.
But, the admission success rate becomes higher since the resources are preserved.
Value range: 0~100
Physical value range: 0~1; step: 0.01
Physical unit: %
Set these parameters through ADD UCELLLDM/ MOD UCELLLDM.
UlLdrRelThd/DlLdrRelThd
Content: If the ratio of UL/DL load of the cell to the uplink capacity is lower than
this threshold, the UL/DL load reshuffling function of the cell is stopped.
Value range: 0~100
Physical unit: %
NBMLdcAlgoSwitch-CELL_CODE_LDR
Content: Code reshuffling algorithm. When the cell CODE is heavily loaded, this
algorithm reduces the cell CODE load by using BE service rate reduction and code
tree reshuffling.
CellLdrSfResThd
Content: Cell SF reserved threshold. The code load reshuffling could be triggered
only when the minimum available SF of a cell is higher than this threshold. The
lower the code resource LDR trigger threshold is, the easier the downlink code
resource enters the initial congestion status, the easier the LDR action is triggered,
and the easier the subscriber perception is affected. But a lower code resource LDR
trigger threshold causes a higher admission success rate because the resource is
reserved.
Value range: SF4(SF4), SF8(SF8), SF16(SF16), SF32(SF32), SF64(SF64),
SF128(SF128), SF256(SF256)
Physical value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256
Set this parameter through ADD UCELLLDR/ MOD UCELLLDR.
NodeBLdcAlgoSwitch-IUB_LDR
Content: When the NodeB Iub load is heavy, users are assembled in priority order
among all the NodeBs and some users are selected for LDR action (such as BE
service rate reduction) in order to reduce the NodeB Iub load.
Set this parameter through ADD UNODEBALGOPARA / MOD UNODEBALGOPARA.
The switches of NodeB credit LDR:

Algorithm
Load Control Algorithm Switch
LDC Algorithm Switch
Type A
LC_CREDIT_LDR_SWITCH
CELL_CREDIT_LDR
Type B
LCG_CREDIT_LDR_SWITCH
LCG_CREDIT_LDR
Type C
NODEB_CREDIT_LDR_SWITCH
NODEB_CREDIT_LDR
The threshold of NodeB credit LDR:
Type A: If the cell UL/DL current remaining SF (mapped to credit resource) is higher
than UlLdrCreditSfResThd or DlLdrCreditSfResThd (set through the ADD

UCELLLDR command), credit congestion at cell level is triggered and related load
reshuffling actions are taken in the current cell.
Type B and C: If the cell group or NodeB UL/DL current remaining credit resource is
lower than the credit resource corresponding to the SF specified by
UlLdrCreditSfResThd or DlLdrCreditSfResThd (set by running the ADD
UNODEBLDR command), credit congestion at the cell group or NodeB level is
triggered and related load reshuffling actions will be taken.
The basic congestion of type A will not trigger load-based inter-frequency
handovers while the basic congestion of type B or C will trigger such actions.
Type A: CELL_CREDIT_LDR
Type A: UlLdrCreditSfResThd/DlLdrCreditSfResThd
Set these parameters through ADD UCELLLDR/ MOD UCELLLDR.
Type B/C: LCG_CREDIT_LDR/NODEB_CREDIT_LDR
Set these parameters through ADD UNODEBALGOPARA/ MOD

UNODEBALGOPARA.
Type B/C: UlLdrCreditSfResThd/DlLdrCreditSfResThd
Set these parameters through ADD UNODEBLDR/ MOD UNODEBLDR.
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 ULDCALGOPARA
command
LdrFirstPri/LdrSecondPri/LdrThirdPri/LdrFourthPri
Content: If congestion is triggered by multiple resources such as credit and code at

the same time, the congestion of resources specified in this parameter is processed
with the first priority. IUBLDR refers to processing of LDR action trigged by Iub
bandwidth. CREDITLDR refers to processing of LDR action trigged by credit.
CODELDR refers to processing of LDR action trigged by code. UULDR refers to
processing of LDR action trigged by Uu.
Value range: IUBLDR(Iub load reshuffling), CODELDR(Code load reshuffling),
UULDR(Uu load reshuffling), CREDITLDR(Credit load reshuffling)
Physical value range: IUBLDR, CODELDR, UULDR, CREDITLDR
Set these parameters through SET ULDCALGOPARA.
The sequence of LDR actions can be changed by running the MOD UCELLLDR/MOD
UNODEBLDR command.
As shown in the above figure, when the system is congested, the inter-frequency load
handover is initiated first.
If the handover succeeds, the algorithm continues to check whether the system is
congested. If the system is still congested, the inter-frequency load handover is
initiated again.
If the handover fails, code reshuffling is performed:
If the code reshuffling succeeds, the algorithm continues to check whether

the system is congested. If the system is still congested, the code
reshuffling is initiated again.
If the code reshuffling fails, the next action, that is, BE rate reduction, is
taken.
The remaining actions to be performed may be deduced by analogy
LDR Actions Intended for Different Resources
When the basic congestion is triggered by different resources, the congestion can be
relieved in a order set by running the SET ULDCALGOPARA command.
LDR Actions
DC-HSUPA
Power
DCH
DL
HSDPA
DC-HSDPA
UL
DL
DCH
HSUPA
Code
DL
UL
Credit
DL
DCH
HSDPA
DC-HSDPA
DC-HSUPA
Iub
Code
Reshuffling
HSUPA
AMR Rate
Reduction
UL
Inter-RAT
Handover in
PS Domain
Channel
Inter-RAT
Handover in
CS Domain
DCH
UL/DL
BE Rate
Reduction
InterFrequency
Load
Handover
Resource
DCH
HSUPA
DC-HSUPA
DCH
HSDPA
DCH
HSDPA
If the uplink power-based admission uses the power resource algorithm, the load-based
inter-frequency handover for HSUPA user cannot be performed, as indicated by the symbol
"*" in the preceding table.
If the downlink/uplink power-based admission uses the ENU algorithm, the basic
congestion can also be caused by the ENU. In this situation, LDR actions do not involve
AMR rate reduction, as indicated by the symbol "*" in the preceding table.
LdrPeriodTimerLen
Content: Identifying the period of the LDR execution. When basic congestion
occurs, execution of LDR can dynamically reduce the cell load. The lower the
parameter value is, the more frequently the LDR action is executed, which
decreases the load quickly. If the parameter value is excessively low, an LDR action
may overlap the previous one before the previous result is displayed in LDM. The
higher the parameter value is, the more likely this problem can be prevented. If the
parameter value is excessively high, the LDR action may be executed rarely, failing
to lower the load timely.
Value range: 1~86400
Physical value range: 1~86400; step: 1
Physical unit: s
Set this parameter through SET ULDCPERIOD.
GoldUserLoadControlSwitch
Content: Indicates whether gold users involve in the switch of congestion control.
According to the policy set for gold users by operators, if service quality of gold
users should be guaranteed even in resource congestion, the switch should be
disabled. If the switch is enabled, LDR such as rate reduction and handover also
occurs on gold users even in cell resource congestion, which impacts user service
quality. If the switch is disabled, no action is performed on gold users.
Set this parameter through ADD UCELLLDR/ MOD UCELLLDR.
DlLdrFirstAction to DlLdrTenthAction
Content: Downlink LDR actions.
Value range: NoAct(no action), InterFreqLDHO(inter-freq load handover),

BERateRed(BE traff rate reduction), QoSRenego(uncontrolled real-time traff Qos renegotiation), CSInterRatShouldBeLDHO(CS domain inter-rat should be load
handover), PSInterRatShouldBeLDHO(PS domain inter-rat should be load handover),
AMRRateRed(AMR traff rate reduction), CodeAdj(Code adjust),
CSInterRatShouldNotLDHO(CS domain inter-rat should not be load handover),
PSInterRatShouldNotLDHO(PS domain inter-rat should not be load handover)
UlLdrFirstAction to UlLdrEighthAction
Content: Uplink LDR actions.
Value range: NoAct(no action), InterFreqLDHO(inter-freq load handover),

BERateRed(BE traff rate reduction), QoSRenego(uncontrolled real-time traff Qos renegotiation), CSInterRatShouldBeLDHO(CS domain inter-rat should be load
handover), PSInterRatShouldBeLDHO(PS domain inter-rat should be load handover),
AMRRateRed(AMR traff rate reduction), CSInterRatShouldNotLDHO(CS domain
inter-rat should not be load handover), PSInterRatShouldNotLDHO(PS domain interrat should not be load handover)
If the UE is in the soft handover state, load-based inter-frequency handover can be
performed only when the HO_ALGO_LDR_ALLOW_SHO_SWITCH sub-parameter of the

HoSwitch parameter is set to 1.
Inter-frequency load handover can be performed only when the

HO_ALGO_LDR_ALLOW_SHO_SWITCH subparameter of the HoSwitch parameter is set
to 1.
The inter-frequency load handover can be performed based on blind handover or

measurement, which can be decided by the parameter InterFreqLDHOMethodSelection.
InterFreqLDHOMethodSelection
Meaning: This parameter specifies load handover method. When network is

composed of same frequency band, Blind Handover method is
suggested .Otherwise, Measure handover is suggested .
GUI Value Range: BLINDHO(BLINDHO), MEASUREHO(MEASUREHO)
Actual Value Range: BLINDHO, MEASUREHO
Unit: None
Default Value: BLINDHO
Set these parameters through ADD UCELLLDR/ MOD UCELLLDR
1. The algorithm checks whether cells for inter-frequency blind handover are available. If
available, the algorithm goes to the next step. Otherwise, the action fails, and the
algorithm takes the next action.
Whether the neighboring cells support blind handover is specified by the

parameter BlindHoFlag.
2. The RNC selects the UEs that meet the following requirements. Then, RNC sorts the UEs
by integrated user priority and selects the UE of the lowest integrated user priority to
perform the next step. If there are no candidate users, the action fails, and the algorithm
takes the next action.
The service types of UEs are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC.
The user rate of UEs is smaller than or equal to the handover bandwidth threshold.
The handover bandwidth thresholds of uplink and downlink are respectively
specified by the UlInterFreqHoBWThd and DlInterFreqHoBWThd parameters.
If the basic congestion is caused by the credit resource, only UEs processing PS
services are selected as candidate UEs.
1. The RNC selects the UE whose service types are not restricted for LDR handover by
parameter InterFreqLdHoForbidenTC, and then sorts the selected UEs according to

their integrated priority and performs load-based inter-frequency handover based on
measurement on the UE with the lowest integrated priority.
If the basic congestion is caused by the credit resource, only UEs processing PS
services are selected as candidate UEs. This is the same as in cases of blind
handovers.
2. The RNC selects the candidate cells that meet the following conditions:
The cell is an inter-frequency neighboring cell of the current cell and is controlled
by the same RNC.
The frequency of the cell is within the band supported by the UE.
The cell meets the following conditions on load margin:
a. If the basic congestion is caused by power resource:

If the cell does not support DC-HSDPA, the algorithm checks whether
the UL/DL load margin of the target cell is higher than
UlInterFreqHoCellLoadSpaceThd /
DlInterFreqHoCellLoadSpaceThd and whether the load of the
target cell is normal.
InterFreqLdHoForbidenTC
Parameter name: Forbidden Traffic Class for inter-freq HO

Meaning: This parameter specifies the forbidden traffic classes when perform interfrequency handover, in order to prevent disarranging of the layers.
GUI Value Range: R99_CONVERSATIONAL, R99_STREAMING, R99_BE,
HSDPA_CONVERSATIONAL, HSDPA_STREAMING, HSDPA_BE,
HSPA_CONVERSATIONAL, HSPA_STREAMING, HSPA_BE
Actual Value Range: R99_CONVERSATIONAL, R99_STREAMING, R99_BE,
HSDPA_CONVERSATIONAL, HSDPA_STREAMING, HSDPA_BE,
HSPA_CONVERSATIONAL, HSPA_STREAMING, HSPA_BE
Unit: None
Default Value: None
Recommended Value: None
Set these parameters through ADD UCELLLDR/ MOD UCELLLDR
NbmLdcUeSelSwitch
Meaning: The algorithms with the above values represent are as follow:
NBM_LDC_ALL_UE: When inter-freq handover select user occurs, no need

to consider whether target cell support UE.
NBM_LDC_MATCH_UE_ONLY: When inter-freq handover select user occurs,

only consider UEs supported by target cell.
NBM_LDC_MATCH_UE_FIRST: When inter-freq handover select user occurs,

first consider UEs supported by target cell.
GUI Value Range: NBM_LDC_ALL_UE(Select all users),

NBM_LDC_MATCH_UE_ONLY(Select users match target cell support only),
NBM_LDC_MATCH_UE_FIRST(Select users match target cell support first)
Actual Value Range: NBM_LDC_ALL_UE, NBM_LDC_MATCH_UE_ONLY,

NBM_LDC_MATCH_UE_FIRST
Unit: None
Default Value: None
Recommended Value: NBM_LDC_MATCH_UE_ONLY
Set these parameters through ADD UCELLALGOSWITCH/ MOD

UCELLALGOSWITCH.
UlInterFreqHoCellLoadSpaceThd/DlInterFreqHoCellLoadSpaceThd
Content: The inter-frequency neighboring cell could be selected as the destination

of load handover only when its load remaining space is larger than this threshold.
The lower the parameter is, the easier it is to find a qualified target cell for the
blind handover. Excessively small value of the parameter, however makes the
target cell easily enter the congestion status. The higher the parameter is, the more
difficult it is for the inter-frequency blind handover occurs.
Value range: 0~100
Physical unit: %
LdrCodeUsedSpaceThd
Content: Code resource usage difference threshold. Inter-frequency handover is

triggered when the difference of the resource usage of the current cell and that of
the target cell is greater than this threshold. The smaller this parameter value, the
easier it is to find the qualified target cell for blind handover. Excessively small
values of the parameter, however makes the target cell easily enters the congestion
status. The higher the parameter value, the more difficult it is for the interfrequency blind handover occurs, and the easier it is to guarantee the stability of
the target cell.
Value range: 0~100
Physical unit: %
UlInterFreqHoBWThd/DlInterFreqHoBWThd
Content: The UE can be selected to process load handover only when its
bandwidth is less than this threshold. The higher the parameter is, the higher the
service rate of the user in handover is, and the more obviously the cell load is
decreased. However, high value of the parameter gives rise to the fluctuation and
congestion of the target cell load. The lower the parameter is, the smaller
amplitude of the load decreases as a result of the inter-frequency load handover,
and the easier it is to maintain the stability of the target cell load.
Physical unit: bit/s
DrdOrLdrFlag
Content: Flag of a cell on which the DRD(Direct Retry Decision) measurement or

LDR(Load Reshuffling) measurement is performed. If this parameter is set to TRUE,
the cell can be considered as the measurement object in the DRD measurement
algorithm or LDR measurement algorithm. If this parameter is set to FALSE, the cell
is invalid.
Value range: FALSE(Do not send), TRUE(Send)
Set these parameters through ADD UINTERFREQNCELL / MOD UINTERFREQNCELL
UESpdOptSwitch
Content: Whether the RNC considers the UE speed when initiating a measurementbased inter-frequency handover. If this parameter is set to ON, high-speed UEs will
not be handed over to a micro cell. If this parameter is set to OFF, the RNC does
not consider the UE speed when initiating a measurement-based inter-frequency
handover.
Set these parameters through ADD UCELLMCLDR / MOD UCELLMCLDR
PrdReportInterval
Content: The interval between two reports is the configured value.

Value range: D250, D500, D1000, D2000, D3000, D4000, D6000, D8000, D12000,
D16000, D20000, D24000, D28000, D32000, D64000
Physical unit: ms
Set these parameters through ADD UCELLMCLDR / MOD UCELLMCLDR.
TargetFreqThdRscp/TargetFreqThdEcN0
Content: Estimate the signal quality of the periodic reports. The inter-frequency
handover is triggered only when the signal quality of the target cell is higher than
this parameter. Note: The threshold can be reached only when RSCP and EcNo of
the target cell are above the RSCP and EcNo that are set in the command.
Value range: -115~-25,-24~0
Physical unit: dBm,dB
Set these parameters through ADD UCELLMCLDR / MOD UCELLMCLDR.
The BE rate reduction function is controlled by the DCCC algorithm switch. BE rate reduction can
only be performed when the DCCC algorithm is enabled, which means the DRA_DCCC_SWITCH
subparameter of the DraSwitch parameter is set to 1.
Different from the TF restriction to the OLC function, the BE rate reduction is implemented by
bandwidth reconfiguration. The bandwidth reconfiguration requires signaling interaction on the Uu
interface. This procedure is relatively long.
In the same environment, different rates have different downlink transmit powers. The higher the
rate, the greater the downlink transmit power. Therefore, the load can be reduced by bandwidth
reconfiguration.
For HSUPA services, the consumption of CEs is based on the bit rate. The higher the rate, the more
the consumption of CEs. Therefore, the consumption of CEs can be reduced by bandwidth
reconfiguration.
The LDR algorithm operates as follows:
Based on the integrated priority, the algorithm sorts the RABs in descending order.
The algorithm selects the RABs with the lowest integrated priorities and with the current
rate higher than the GBR specified through the SET UUSERGBR command for related to the
BE services. If the integrated priorities of some RABs are identical, the RAB with the highest
rate is selected. The number of selected RABs is specified by the
UlLdrBERateReductionRabNum or DlLdrBERateReductionRabNum parameter.
If services can be selected, the action is successful. If services cannot be selected, the action
fails. The algorithm takes the next action.
The reconfiguration is completed as indicated by the RADIO BEARER RECONFIGURATION
message on the Uu interface and through the synchronized radio link reconfiguration
procedure on the Iub interface.
UlLdrBERateReductionRabNum/DlLdrBERateReductionRabNum
Content: Number of RABs selected in a UL/DL LDR BE traffic rate reduction. In the
actual system, this parameter can be set on the basis of the actual circumstances. If
the high-rate subscribers occupy a high proportion, set the parameter to a
comparatively low value. If the high-rate subscribers occupy a low proportion, set
the parameter to a comparatively high value. Because the basic congestion control
algorithm is designed to slowly decrease cell load, you need to set this parameter
to a comparatively low value.
Value range: 1~10
Inter-RAT handover in the CS/PS domain involves the following actions:
Inter-RAT Should Be Load Handover in the CS/PS domain:
1. Based on the integrated priority, the algorithm sorts the UEs with the "service handover"
IE set to "handover to GSM should be performed" in the CS domain in descending order.
2. The algorithm selects the UEs with the lowest integrated priorities. The number of
selected UEs is specified by the UlCSInterRatShouldBeHOUeNum or
DlCSInterRatShouldBeHOUeNum parameter.
3. For the selected UEs, the LDR module sends the load handover command to the interRAT handover module, requesting the inter-RAT handover module to hand over the UEs to
the 2G system.
4. The handover module decides to trigger the inter-RAT handover, depending on the
capability of the UE to support the compressed mode.
5. If a UE that satisfies the handover criteria is not found, the algorithm takes the next
action.
Inter-RAT Should Not Be Load Handover in the CS/PS domain:
The algorithm for this action is the same as that for the action "Inter-RAT Should Be Load
Handover in the CS Domain". The difference is that this action only involves CS users with
the "service handover" IE set to "handover to GSM should not be performed".
The number of selected UEs is specified by the UlCSInterRatShouldNotHOUeNum or

DlCSInterRatShouldNotHOUeNum parameter.
This action can only be performed when the AMRC algorithm is enabled, which means the
CS_AMRC_SWITCH subparameter of the parameter CsSwitch parameter is set to 1, Set these
parameters through SET UCORRMALGOSWITCH.
In the WCDMA system, voice services work in eight AMR modes. Each mode has its own rate.
Therefore, mode control is functionally equivalent to rate control.
In the downlink, the LDR algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the RABs in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities and with the rates
higher than the GBR for AMR services (conversational). The number of selected RABs is
specified by the DlLdrAMRRateReductionRabNum parameter. If the RNC cannot find an
appropriate RAB for the AMR rate reduction, the action fails. The algorithm takes the next
action.
3. The RNC sends the Rate Control request message through the Iu interface to the CN to
adjust the AMR rate to the GBR.
In the uplink, the LDR algorithm operates as follows:
2. The algorithm selects the RABs with the lowest integrated priorities and with the rates
higher than the GBR for AMR services (conversational). The number of selected RABs is
determined by the UlLdrAMRRateReductionRabNum parameter. If the RNC cannot find
an appropriate RAB for the AMR rate reduction, the action fails. The algorithm takes the
next action.
3. The RNC sends the TFC CONTROL command to the UE to adjust the AMR rate to the
GBR.
UlLdrAMRRateReductionRabNum/DlLdrAMRRateReductionRabNum
Content: This parameter defines the maximum number of RABs selected in

executing uplink/downlink LDR-AMR voice service rate reduction. If the parameter
value is too high, the LDR action may fluctuate greatly and over control may occur
(the state of basic congestion turns into another extreme--underload). If the
parameter value is too low, the LDR action has a slow response and the effect is
not apparent, affecting the LDR performance.
Value range: 1~10
The code reshuffling algorithm operates as follows:
Initializes SF_Cur to CellLdrSfResThd.
Traverses all the subtrees with this SF_Cur at the root node except the subtrees
occupied by common channels and HSDPA channels, and takes the subtrees in
which the number of users is not larger than the value of MaxUserNumCodeAdj as
candidates for code reshuffling.
If such candidates are available, the algorithm goes to step 3.
If no such candidate is available, subtree selection fails. This procedure ends.
Selects a subtree from the candidates according to the setting of LdrCodePriUseInd.

If this parameter is set to TRUE, the algorithm selects the subtree with the largest
code number from the candidates.
If this parameter is set to FALSE, the algorithm selects the subtree with the smallest
number of users from the candidates. In the case that multiple subtrees have the
same number of users, the algorithm selects the subtree with the largest code
number.
Treats each user in the subtree as a new user and allocates code resources to each
user.
Initiates the reconfiguration procedure for each user in the subtree and
reconfigures the channelization codes of the users to the newly allocated code
resources. 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.
The above figure shows an example of code reshuffling. In this example, CellLdrSfResThd is
set to SF8, and MaxUserNumCodeAdj is set to 1.
CellLdrSfResThd
Content: Cell SF reserved threshold. The code load reshuffling could be triggered
only when the minimum available SF of a cell is higher than this threshold. The
lower the code resource LDR trigger threshold is, the easier the downlink code
resource enters the initial congestion status, the easier the LDR action is triggered,
and the easier the subscriber perception is affected. But a lower code resource LDR
trigger threshold causes a higher admission success rate because the resource is
reserved.
Value range: SF4(SF4), SF8(SF8), SF16(SF16), SF32(SF32), SF64(SF64),

SF128(SF128), SF256(SF256)
Physical value range:SF4, SF8, SF16, SF32, SF64, SF128, SF256
MaxUserNumCodeAdj
Content: This parameter specifies the number of users selected in code reshuffling.
Code reshuffling can be triggered only when the number of users on a code is no
greater than the threshold. Code reshuffling has a big impact on the QoS. In
addition, the reshuffled subscribers occupy two code resources during code
reshuffling. Thus, the parameter should be set to a comparatively low value.
Value range: 1~3
LdrCodePriUseInd
Content: FALSE means not considering the code priority during the code
reshuffling. TRUE means considering the code priority during the code reshuffling.
If the parameter is TRUE, the codes with high priority are reserved during the code
reshuffling.
Value range: FALSE, TRUE

Physical value range: FALSE, TRUE
Only the power resource and Iub bandwidth may result in the overload congestion state.
Hard resources such as the ENU and credit resource do not cause overload congestion.
After the UE access is allowed, the power consumed by a single link is adjusted by the
single link power control function. 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.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the
NBMLdcAlgoSwitch parameter.
As shown in the figure, if the UL/DL load of the cell is higher than or equal to the
UlOlcTrigThd or DlOlcTrigThd for a hysteresis time, the cell is in the overload state, and
the related overload handling action is taken. If the current UL/DL load of the cell is lower
than the UlOlcRelThd or DlOlcRelThd for a hysteresis time, the overload state of the cell
is released and the related overload handling is stopped.
The UL or DL OLC trigger threshold of a DC-HSDPA cell group equals the sum of the UL or
DL OLC trigger thresholds of the two cells in this group. The UL or DL OLC relief threshold
of a DC-HSDPA cell group equals the sum of the UL or DL OLC relief thresholds of the two
cells in this group. If a DC-HSDPA cell group is overloaded, the related overload handling is
performed in each cell separately.
In a DC-HSUPA cell, OLC triggering and execution happen in the two cells respectively
Power Resource:
Load level > OLC trigger threshold
Iub Bandwidth:
Available Iub bandwidth < predefined threshold
UlOlcTrigThd/DlOlcTrigThd
Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is not
lower than this threshold, the UL/DL overload and congestion control function of
the cell is triggered. The lower the OLC trigger threshold is, the easier the system is
in the overload status. An excessively low value of the OLC trigger threshold is very
detrimental to the system performance. The lower the OLC release threshold is, the
harder the system releases the overload. The value of the OLC release threshold
should not be much lower than or close to the OLC trigger threshold, or the system
state may have a ping-pong effect. The recommended difference between the OLC
release threshold and the OLC trigger threshold is higher than 10%. 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.
Value range: 0~100
Physical unit: %
UlOlcRelThd/DlOlcRelThd
Content: If the ratio of UL/DL load of the cell to the uplink/downlink capacity is
lower than this threshold, the UL/DL overload and congestion control function of
the cell is stopped.
Value range: 0~100
Physical unit: %
When the cell is overloaded, the RNC takes one of the following actions in each period specified by
the OlcPeriodTimerLen parameter 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
As shown in the previous figure, the OLC procedure is as follows:
1. The OLC takes the first action to perform TF control.
If the TF control succeeds, the OLC checks whether the system is overloaded. If
yes, the OLC performs TF control again.
If the TF control fails, go to 2.
2. The OLC takes the second action to switch BE services to common channels.
If the switching succeeds, the OLC checks whether the system is overloaded. If yes,
the OLC switches BE services to common channels again.
If the switching fails, go to 3.
3. The OLC takes the third action to adjust the maximum FACH transmit power.
If the adjustment succeeds, the OLC checks whether the system is overloaded. If
yes, the OLC adjusts the power again.
If the adjustment fails, the OLC takes the fourth action to release some RABs.
OlcPeriodTimerLen
Content: :Identifying the period of the OLC execution. When overload occurs,
execution of OLC can dynamically reduce the cell load. When setting the parameter,
consider the hysteresis for which the load monitoring responds to the load change.
If the OLC period is excessively long, the system may respond very slowly to
overload. If the OLC period is excessively short, unnecessary adjustment may occur
before the previous OLC action has taken effect, and therefore the system
performance is affected.
Value range:100~86400000
Physical unit: ms
Set this parameter through SET ULDCPERIOD.
For the TF control in the downlink, the OLC algorithm operates as follows:
2. The algorithm selects the following RABs:
DCH RABs with the bit rates higher than DlDcccRateThd for BE services.
RABs with the lowest integrated priorities.
The number of RABs selected is smaller than or equal to DlOlcFTFRstrctRabNum.

If the RNC cannot find an appropriate service for the TF control, the OLC takes the next
action
3. The RNC sends the TF control indication message to the MAC. Each MAC of the selected
RABs will receive one TF control indication message and will restrict the TFC (transport
format combination ) selection of the BE services to reduce the data rate step by step.
The MAC restricts the TFC selection according to the following formula:
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.
The above figure shows an example of TF control. In this example, the MAC performs TF
control of a downlink 384 kbit/s service, and RateRstrctCoef is set to 0.68. And the time
between point A and point B is specified by the RateRstrctTimerLen parameter.
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 for fast TF restriction.
MAC restricts the TFC selection during the period 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
Compare 8.16 with the TFS. Then, the maximum TB number is 8.
At point B, the MAC performs further TFC restriction by calculating maximum TB

number as follows:
TFmax(2) = TFmax(1) x Ratelimitcoeff = 8 x 0.68 = 5.44
Compare 5.44 with the TFS. Then, the maximum TB number is 4.
At point C and point D, similar process is followed.
DlDcccRateThd
Content: For a BE service that has a low maximum rate, the DCCC algorithm is not
obviously effective yet it increases algorithm processing. Thus, the traffic-based
DCCC algorithm is applied to BE services whose maximum DL rate is greater than
the threshold.
Value range: D8, D16, D32, D64, D128, D144, D256, D384
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384; step: 1
Physical unit: Kbit/s
Set this parameter through SET UDCCC.
DlOlcFTFRstrctRabNum
Content: Selection of RABs of the OLC is based on the service priorities and ARP
values and bearing priority indication. The RAB of low priority is under control. The
higher the parameters are, the more users are involved in fast TF restriction under
the same conditions, the quicker the cell load decreases, and the more user QoS is
affected.
Value range: 1~10
Set this parameter through ADD UCELLOLC/ MOD UCELLOLC.
DlOlcFTFRstrctTimes
Content: After the overload is triggered, the RNC immediately executes OLC by first
executing 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 relieve the overload. If the
number of overloads exceeds the OLC action threshold, the previous operation has
no obvious effect on alleviating the overload and the system has to release users to
solve the overload problem.
Value range: 0~100
RateRstrctTimerLen/RateRecoverTimerLen
Content: These parameters define the downlink data rate restrict/recover timer
length in fast TF restriction. Both of them are effective only to the downlink. The
uplink fast TF restriction is performed by the UE. For the uplink fast TF restriction,
the RNC only delivers a new TFCS and randomly selects a comparatively bigger
time length in the signaling value scope. The UE automatically release the TF
restriction once the time expires.
Physical unit: ms
Set these parameters through ADD UCELLOLC/ MOD UCELLOLC.
RateRstrctCoef/RecoverCoef
Content: These parameters define the downlink OLC fast TF rate restrict/recovery
coefficient. Both of them are effective only to the downlink.
Value range: 1~99/100~200
Physical value range: 0.01~0.99/1~2; step:0.01
Physical unit: %
UlDcccRateThd
Content: For a BE service that has a low maximum rate, the DCCC algorithm is not
obviously effective yet it increases algorithm processing. Thus, the traffic-based
DCCC algorithm is applied to BE services whose maximum UL rate is greater than
the threshold.
Value range: D8, D16, D32, D64, D128, D144, D256, D384
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384; step: 1
Physical unit: Kbit/s
Set this parameter through SET UDCCC.
UlOlcFTFRstrctRabNum
Content: Selection of RABs of the OLC is based on the service priorities and ARP
values and bearing priority indication. The RAB of low priority is under control. The
higher the parameters are, the more users are involved in fast TF restriction under
the same conditions, the quicker the cell load decreases, and the more user QoS is
affected.
Value range: 1~10
UlOlcFTFRstrctTimes
Content: After the overload is triggered, the RNC immediately executes OLC by first
executing 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 relieve the overload. If the
number of overloads exceeds the OLC action threshold, the previous operation has
no obvious effect on alleviating the overload and the system has to release users to
solve the overload problem.
Value range: 0~100
Whether the selected UEs can be switched to common channels depends on the setting of
DRA_PS_BE_STATE_TRANS_SWITCH, DRA_HSDPA_STATE_TRANS_SWITCH, or
DRA_HSUPA_STATE_TRANS_SWITCH in the parameter DraSwitch.
For switching BE services to common channels, the OLC algorithm operates as follows:
Based on the integrated priority, the algorithm sorts all the UEs in the PS domain in
descending order.
The algorithm selects the UEs with the lowest integrated priorities. The number of
selected UEs is specified by TransCchUserNum. If the selection fails, the OLC takes
the next action.
The OLC switches the selected UEs to common channels.
This function is disabled when the TransCchUserNum parameter is set to 0.
TransCchUserNum
Content: When the system is overloaded and congested, users on the DCH or HSPA
can be reconfigured to the CCH in order to reduce the cell load and recover the
system. This parameter defines the maximum number of users selected in
executing reconfiguration to the CCH. If the parameter value is too high, the OLC
action may fluctuate greatly and over control may occur (the state of overload and
congestion turns into another extreme--underload). If the parameter value is too
low, the OLC action has a slow response and the effect is not apparent, affecting
the OLC performance.
Value range: 0~10
Set this parameters through ADD UCELLOLC/ MOD UCELLOLC.
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 above formula.
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.
MaxFachPower
Content: The offset between the FACH transmit power and PCPICH transmit power
in a cell. If MaxFachPower is excessively low, the UE at the cell verge fails to
receive correctly the services and signaling borne over the FACH, resulting in the
influence on the downlink common channel coverage and the cell coverage. If
MaxFachPower is excessively high, other channels are interfered, the downlink
power resources are occupied, and consequently the cell capacity is influenced.
Value range: -350~150
Physical value range: -35~15; step: 0.1
Physical unit: dB
Set this parameter through ADD UFACH.
FACHPwrReduceValue
Content: This parameter defines the reduce value in reducing FACH power Action.
Value range: 0~30
Physical unit: dB
If the Control RTWP Anti-interference algorithm switch (NBMCacAlgoSwitch:
RTWP_RESIST_DISTURB) is enabled, the RNC checks whether the uplink equivalent user
load proportion of the cell is lower than 40% before performing this operation. If it is
lower than 40%, the RNC does not perform this operation.
For the release of some RABs in the uplink, the OLC algorithm operates as follows:
Based on the integrated priority, the algorithm sorts all RABs including HSUPA and
DCH services in descending order.
The algorithm selects the RABs with the lowest integrated priorities. If the
integrated priorities of some RABs are identical, it selects the RAB with a higher
rate (that is, the current rate for DCH RAB or the GBR for HSUPA RAB) in the uplink.
The number of selected RABs is specified by UlOlcTraffRelRabNum.
The selected RABs are released directly.
For the release of some RABs in the downlink, the OLC algorithm operates as follows:
Based on the integrated priority, the algorithm sorts all RABs in descending order.
The algorithm selects the RABs with the lowest integrated priorities. If the
integrated priorities of some RABs are identical, it selects the RAB with a higher
rate (that is, the current rate for DCH RAB or the GBR for HSDPA RAB) in the
downlink. The number of selected RABs is specified by DlOlcTraffRelRabNum.
The selected RABs are directly released.
UlOlcTraffRelRabNum/DlOlcTraffRelRabNum
Content: These parameters define the maximum number of RABs released in

executing uplink/downlink OLC service release.
Value range: 0~10

OWO117090 WCDMA RAN15 Load Congestion Control Algorithm and Parameters ISSUE1.00

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OWO117090 WCDMA RAN15 Load Congestion Control Algorithm and Parameters ISSUE1.00

Hochgeladen von

Copyright:

Verfügbare Formate

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Load control functions in different UE access phases

Before UE access: Potential User Control (PUC)

After UE access: Inter-Frequency Load Balancing Based on Configurable Load

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA Admission Control Algorithm and Parameters

Confidential Information of Huawei. No Spreading Without Permission

WCDMA Admission Control Algorithm and Parameters

Confidential Information of Huawei. No Spreading Without Permission

WCDMA Admission Control Algorithm and Parameters

Traffic classes: conversational > streaming > interactive > background

Confidential Information of Huawei. No Spreading Without Permission

WCDMA Admission Control Algorithm and Parameters

Confidential Information of Huawei. No Spreading Without Permission

WCDMA Admission Control Algorithm and Parameters

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

and UL_UU_LDR subparameters of the NBMLdcAlgoSwitch parameter.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Load level > LDR trigger threshold

Available Iub bandwidth < predefined threshold

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

UL_UU_LDR: UL UU load reshuffling algorithm. When the cell is heavily loaded in

Value range: OFF, ON

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Value range: 0~100

Physical value range: 0~1; step: 0.01

Set these parameters through ADD UCELLLDM/ MOD UCELLLDM.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Load Congestion Control Algorithm and Parameters (LCC)

Value range: 0~100

Physical value range: 0~1; step: 0.01

Set these parameters through ADD UCELLLDM/ MOD UCELLLDM.