Documente Academic
Documente Profesional
Documente Cultură
Load Control
Feature Parameter Description
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may
not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all
statements, information, and recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
7 Load Reshuffling.......................................................................................................................7-1
7.1 Basic Congestion Triggering ......................................................................................................... 7-1
7.1.1 Power Resource ................................................................................................................... 7-1
7.1.2 Code Resource..................................................................................................................... 7-2
7.1.3 Iub Resource ........................................................................................................................ 7-2
7.1.4 NodeB Credit Resource ....................................................................................................... 7-2
7.2 LDR Procedure.............................................................................................................................. 7-3
7.3 LDR Actions................................................................................................................................... 7-6
7.3.1 Inter-Frequency Load Handover .......................................................................................... 7-6
7.3.2 BE Rate Reduction ............................................................................................................... 7-9
7.3.3 QoS Renegotiation for Uncontrollable Real-Time Services ................................................. 7-9
7.3.4 Inter-RAT Handover in the CS Domain .............................................................................. 7-10
7.3.5 Inter-RAT Handover in the PS Domain .............................................................................. 7-10
7.3.6 AMR Rate Reduction ...........................................................................................................7-11
7.3.7 Code Reshuffling ................................................................................................................ 7-12
7.3.8 MBMS Power Reduction .................................................................................................... 7-13
7.3.9 UL and DL LDR Action Combination of a UE ..................................................................... 7-13
8 Overload Control.......................................................................................................................8-1
8.1 Overload Triggering ....................................................................................................................... 8-1
8.2 General OLC Procedure ............................................................................................................... 8-2
8.3 OLC Actions .................................................................................................................................. 8-3
8.3.1 Performing TF Control of BE Services ................................................................................. 8-3
8.3.2 Switching BE Services to Common Channels ..................................................................... 8-5
8.3.3 Adjusting the Maximum FACH TX Power ............................................................................. 8-5
8.3.4 Releasing Some RABs ......................................................................................................... 8-5
9 Parameters .................................................................................................................................9-1
10 Counters .................................................................................................................................10-1
11 Glossary ..................................................................................................................................11-1
12 Reference Documents .........................................................................................................12-1
1 Introduction
1.1 Scope
This document describes the features related to the load control. It also describes the related
parameters.
Document Issues
The document issues are as follows:
01 (2011-04-30)
Draft B (2011-03-30)
Draft A (2010-12-30)
01 (2011-04-30)
This is the document for the first commercial release of RAN13.0.
Compared with issue Draft B (2011-03-30) of RAN13.0, this issue has no change.
Draft B (2011-03-30)
This is the draft of the document for RAN13.0.
Compared with Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.
Draft A (2010-12-30)
This is the draft of the document for RAN13.0.
Compared with issue 02 (2010-12-20) of RAN12.0, the uplink load balancing algorithm is added and the
description is optimized.
The load control functions are applied to different UE access phases as follows:
Before UE access: Potential User Control (PUC)
During UE access: Intelligent Access Control (IAC) and Call Admission Control (CAC)
After UE access: intra-frequency Load Balancing (LDB), Load Reshuffling (LDR), and Overload
Control (OLC)
The following sections will provide detailed information about the load control functions performed in the
different UE access phases.
NOTE
- : not considered
√: considered
If ARP is not received in messages from the Iu interface, the user priority is regarded as copper.
3 Load Measurement
This chapter describes the WRFD-020102 Load Measurement Feature.
The load control functions, such as OLC and CAC, use load measurement values in the uplink and the
downlink. A common Load Measurement (LDM) function is used to control load measurement in the
uplink and the downlink separately.
Load measurement is implemented by the NodeB. The filtering of measurement quantities is
implemented by the NodeB and the RNC.
In Figure 3-2:
A is the sampling value of the measurement.
B is the measurement value after layer 1 filtering.
Here:
Fn is the new post-filtering measurement value.
Fn-1 is the last post-filtering measurement value.
Mn is the new measurement value from the physical layer.
α = (1/2)k/2, k is the measure filter coefficient which is specified by the following parameters.
− For
load control algorithms (excluding OLC), k is specified by the UlBasicCommMeasFilterCoeff or
DlBasicCommMeasFilterCoeff parameter.
− For OLC algorithm, k is specified by the UlOlcMeasFilterCoeff or DlOlcMeasFilterCoeff parameter.
LDM must apply different smooth window length and measurement periods to PUC, CAC, LDR, and
OLC to obtain appropriate filtered values.
The following table lists the smooth window length parameters for setting different functions.
GBP measurements have the same smooth window length in all related functions. The filter length for GBP measurement
is specified by the HsdpaNeedPwrFilterLen parameter.
The length of the PBR smooth filter window is specified by the HsdpaPrvidBitRateFilterLen /
HsupaPrvidBitRateFilterLen parameter.
The Alpha filter formula is: Fn = (1 - α) x Fn-1 + α x Mn (n≥1). For details about this formula, see section 3.3.1 "Layer 3
Filtering on the NodeB Side."
Counting threshold = (Duration of background noise)/(RTWP reporting period). The duration of background noise is
used in auto-adaptive upgrade decision and is set by the BGNAdjustTimeLen parameter. For the setting of RTWP
reporting period, see section 3.2 "Reporting Period."
The PUC function is enabled only when the PUC subparameter of the NBMLdcAlgoSwitch parameter
is set to 1.
For a cell not supporting DC-HSDPA, the RNC periodically monitors the downlink load of the cell.
If the cell load is higher than the upper threshold (SpucHeavy) plus the load level division hysteresis
(SpucHyst), the cell load is considered heavy.
If the cell load is lower than the lower threshold (SpucLight) minus SpucHyst, the cell load is
considered light.
For a cell supporting DC-HSDPA, the RNC concurrently monitors the load state of each single cell and
load state of the cell group.
The checking of load state of a single cell is the same as that of a cell not supporting DC-HSDPA.
The checking of load state of the cell group is as follows:
− If
the load of the two cells is higher than their upper thresholds (SpucHeavy) plus their load level
division hysteresis (SpucHyst), the load of the cell group is considered heavy.
− If
the load of the two cells is lower than their lower thresholds (SpucLight) minus their load level
division hysteresis (SpucHyst), the load of the cell group is considered light.
The load state of a cell supporting DC-HSDPA is determined based on the following table.
Load of Single Cell Load of Cell Group Load of Cell Supporting DC-HSDPA
Heavy Heavy, normal, or light Heavy
Heavy, normal, or light Heavy Heavy
Normal Normal, or light Normal
Normal, or light Normal Normal
Light Light Light
The states of a cell load are heavy, normal, and light, as shown in Figure 4-2.
Figure 4-2 Cell load states
Depending on the load status of the serving cell, the cell reselection variable Sintersearch is adjusted up
or down or kept unchanged. Changes to the variable Sintersearch are made as shown in Table 4-2.
Table 4-2 Changes made to Sintersearch according to the load state
Load State of the S'intersearch Change to Sintersearch
Serving Cell
Light S'intersearch = Sintersearch + OffSinterLight
Normal S'intersearch = Sintersearch →
Heavy S'intersearch = Sintersearch + OffSinterHeavy
The configurations of Qoffset1 and Qoffset2 are related to the load of the serving cell and the load of the
neighboring cells. Changes to Qoffset1 and Qoffset2 are made as shown in Table 4-3.
Table 4-3 Changes made to Qoffset1 and Qoffset2 according to the load state
Load State of Load State Q'offset1 Change Q'offset2 Change
the of the to to
Neighboring Serving Qoffset1 Qoffset2
Cells Cell
Light Light Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Light Normal Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Light Heavy Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Light + OffQoffset2Light
Normal Light Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Normal Normal Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
Normal Heavy Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ OffQoffset1Light + OffQoffset2Light
Heavy Light Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ +
OffQoffset1Heavy OffQoffset2Heavy
Heavy Normal Q'offset1 = Qoffset1 Q'offset2 = Qoffset2
+ +
OffQoffset1Heavy OffQoffset2Heavy
Heavy Heavy Q'offset1 = Qoffset1 → Q'offset2 = Qoffset2 →
The prerequisite for changing the preceding parameters is that these parameters should be in their default values.
As shown in Figure 5-1, the procedure of service access includes the procedures for RRC connection
setup and RAB setup. The successful setup of the RRC connection is one of the prerequisites for the
RAB setup.
During the RRC connection processing, the RNC performs the following steps.
1. RRC redirection based on distance (only for UE-originating AMR services). For details, see section
5.2.2 "RRC Redirection based on Distance". If the RNC decides to obtain UE access from another
cell, it sends an RRC connection reject message to the UE; otherwise, the RNC performs the next
step.
2. RRC redirection for service steering. For details, see section 5.2.3 "RRC Redirection for Service
Steering."
− If
the RNC decides to obtain UE access from the current cell, it then makes a resource-based
admission decision. If the resource-based admission fails, the RNC performs directed retry decision
(DRD) and redirection.
− If
the RNC decides to obtain UE access from another cell, it then sends an RRC connection reject
message to the UE. The message carries the information about the cell and instructs the UE to set up
an RRC connection to the cell.
For details, see section 5.2 "IAC During RRC Connection Setup."
During the RAB connection processing, the RNC performs the following steps:
1. Performs inter-frequency DRD to select a suitable cell for service steering or load balancing. For
details about DRD, see the Directed Retry Decision Feature Parameter Description
2. Performs rate negotiation according to the service requested by the UE. For details, see section 5.4
"Rate Negotiation at Admission Control."
3. Makes cell resource-based admission decision. If the admission is successful, UE access is granted.
Otherwise, the RNC performs the next step. For details about admission decision, see the Call
Admission Control Feature Parameter Description.
4. Selects a suitable cell, according to the inter-frequency DRD, from the cells where no admission
attempt has been made, and then performs step 5. If all the attempts fail, the RNC performs the next
step.
5. Selects a suitable cell according to the inter-RAT DRD. If the inter-RAT admission is successful, UE
access is granted in the inter-RAT cell. If the inter-RAT DRD fails or is not supported, the RNC
performs the next step.
6. Makes a preemption attempt. For details about preemption, see section 5.6 "Preemption." If the
preemption is successful, UE access is granted. If the preemption fails or is not supported, the RNC
performs the next step.
7. Makes a queuing attempt. For details about queuing, see section 5.7 "Queuing." If the queuing is
successful, UE access is granted. If the queuing fails or is not supported, the RNC performs the next
step.
8. Performs low-rate access. For details about low-rate access, see section 5.8 "Low-Rate Access of
the PS BE Service." If the low-rate access is admitted, UE access is granted. If the low-rate access is
unsuccessful, the RNC performs the next step.
9. Rejects UE access.
After the admission attempts of an HSPA service request fail in all candidate cells, the service falls back to the DCH. Then,
the service reattempts to access the network.
Negotiation
Negotiation
Negotiation
Negotiation
Target Rate
Initial Rate
Frequency
Inter-RAT
Inter-
MBR
GBR
DCH √ √ √ √ √ √ √ √ √
HSUPA - √ √ √ √ √ √ √ -
HSDPA - √ √ - - √ √ √ -
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC performs the RRC
redirection based on distance (only for UE-originating AMR services). For details, see section 5.2.2
"RRC Redirection based on Distance". If the RNC decides to obtain UE access from another cell, it
sends an RRC connection reject message to the UE; otherwise, the RNC performs the next step.
Then, the RNC uses the RRC redirection algorithm for service steering to decide whether the UE can
access the network from the current cell:
If the UE can access the network from the current cell according to the decision result, the RNC uses
the CAC algorithm to decide whether an RRC connection can be set up between the UE and the
current cell.
− If
the RRC connection can be set up between the UE and the current cell, the RNC sends an RRC
CONNECTION SETUP message to the UE.
− If
the RRC connection cannot be set up between the UE and the current cell, the RNC attempts to
select a cell for RRC connection setup through RRC DRD. If the RRC DRD fails, RRC redirection will
be performed.
If the UE needs to access the network from another cell according to the decision result, the RNC
sends an RRC CONNECTION REJECT message to the UE. The message carries the information
about this cell.
DrSwitch: DR_RRC_DRD_SWITCH is the general switch of the following four algorithms:
RRC Redirection based on Distance
RRC Redirection for Service Steering
RRC DRD
RRC Redirection After DRD Failure
Before enabling the four algorithms, turn on the DrSwitch: DR_RRC_DRD_SWITCH.
smaller than the parameter, the RNC performs the next step. Otherwise, the RNC does not perform
RRC redirection based on distance, and handles the RRC connection setup request of the UE in the
current cell.
− If
the cell is in the basic congestion state or is overloaded, the RNC generates a random value
ranging from 0 to 1 and compares the value with the RedirFactorOfLDR parameter. If the random
value is equal to or smaller than the parameter, the RNC performs the next step. Otherwise, the RNC
does not perform RRC redirection based on distance, and handles the RRC connection setup
request of the UE in the current cell.
4. The RNC sends the UE an RRC CONNECTION REJECT message containing information on the
neighboring GSM cells of the current cell.
If the current cell does not have any neighboring GSM cell, the UE spontaneously selects a proper cell to access.
− If
RedirSwitch is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an RRC CONNECTION
REJECT message to the UE, redirecting the UE to the target frequency carried in the message.
The frequency information carried in the message can be set by running the SET UREDIRECTION command.
If the RedirBandInd parameter is set to DependOnNCell, only intra-band inter-frequency neighboring cell can be
selected as target frequency.
− If
RedirSwitch is set to ONLY_TO_INTER_RAT, the RNC sends an RRC CONNECTION REJECT
message to the UE. The message carries the information about inter-RAT neighboring cells.
PS R99 and PS HSPA services for UEs of the REL-5 version cannot be identified by the RNC because these UEs do
not carry the Domain indicator, Call type, or UE capability indication IEs in the RRC CONNECTION REQUEST
message.
In order to reduce the waiting time of the peer UE and ensure that the terminated call can be admitted as soon as
possible, the RRC redirection based on service steering is not applicable to the terminated call.
contained in the IE "RAB Parameters" of the RAB ASSIGNMENT REQUEST message is used. In
addition, the subsequent RAB ASSIGNMENT RESPONSE message does not contain the GBR.
If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST
message is set to "value range", the sole GBR contained in the IE "Alternative Guaranteed Bit Rates"
is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains the GBR.
If the IE "Type of Alternative Guaranteed Bit Rate Information" in the RAB ASSIGNMENT REQUEST
message is set to "Discrete values", the largest GBR contained in the IE "Alternative Guaranteed Bit
Rates" is used. In addition, the subsequent RAB ASSIGNMENT RESPONSE message contains the
GBR.
If the subparameter PS_STREAM_IU_QOS_NEG_SWITCH of the parameter PsSwitch is set to 0, the
GBR negotiation will be not performed. In such a case, the GBR contained in the IE "RAB Parameters" in
the RAB ASSIGNMENT REQUEST message is used.
For details about GBR negotiation, see 3GPP 25.413.
If the DCCC function is enabled and PS_RAB_Downsizing_Switch subparameter of the PsSwitch parameter is set to 1,
the RNC can decrease the rate through the RAB rate decrease function when the admission based on the initial rate fails.
− If
the DRA_HSUPA_DCCC_SWITCH subparameter of the DraSwitch parameter is set to 0, the
actual initial access rate is the MBR.
For the HSDPA service, the initial admission rate and the initial access are both GBR.
5.6 Preemption
Common Preemption
This section describes the pre-emption algorithm in the WRFD-010505 Queuing and Pre-Emption
feature.
By forcibly releasing the resources of lower-priority users, the preemption (pre-emption) function
increases the access success rate of higher-priority users.
After cell/cell group resource-based admission fails, the RNC performs preemption if the following
conditions are met:
The RNC receives an RAB ASSIGNMENT REQUEST message indicating that preemption is
supported.
In the RAB ASSIGNMENT REQUEST message sent by the CN, the Pre-emption Capability IE specifies whether a service
can trigger preemption and the Pre-emption Vulnerability IE specifies whether a service can be preempted. Service
priorities and the Pre-emption Capability and Pre-emption Vulnerability IEs determine whether to perform preemption.
The preemption algorithm switch (PreemptAlgoSwitch) is set to ON.
Preemption is applicable to the following scenarios:
Setup or modification of a service
The preemption algorithm checks whether the resources released by preempted UEs or RABs are sufficient for setting
up new RABs. It does not consider the remaining resources in the cell, because they may be used by other UEs during
the preemption.
For the preemption triggered for power, the preempted objects can be R99 users, R99 + HSPA combined users, or
HSPA RABs.
For the preemption triggered for the Iub bandwidth, the preempted objects can only be RABs.
For the preemption triggered for the credit resource, more than one user or RAB can be preempted.
For the preemption triggered for the code, only one user can be preempted.
3. The RNC releases the resources occupied by the candidate users or RABs.
4. The requested service directly uses the released resources to access the network without admission
decision.
For details about preemption of MBMS services, see the MBMS Feature Parameter Description.
Forced Preemption
Common preemption requires that RABs have been set up or are being set up for preempting users and
that preempting users have higher priorities than preemptable users. Therefore, CS services cannot
trigger preemption in the RRC connection setup phase. Even in the RAB-related phases, CS services
may fail to preempt PS services because of insufficient priorities. When PS traffic volume is high and
radio resources are insufficient, the success rate for CS service setup may decrease. To solve this
problem, forced preemption is introduced. This function ensures preferred access of AMR services and a
high success rate for AMR service setup.
In forced preemption, only CS conversational services can trigger preemption and only PS BE services can be
preempted.
This function is determined by the RsvdPara1 parameter. This parameter consists of two subparameters:
RSVDBIT4 and RSVDBIT5.
The following table describes how these two subparameters determine preemption.
In the RRC connection setup phase, if an RRC setup request is from the CS domain and the cause of RRC setup is
Originating Conversational Call or Terminating Conversational Call, the RNC regards the corresponding service as CS
conversational service.
In the case of unconditional preemption, the RNC does not compare the priority of CS conversational
services with that of PS BE services. In addition, it does not consider the Pre-emption Capability or
Pre-emption Vulnerability IE delivered by the CN. In this case, PS BE services can be preempted by any
CS conversational services and only PS BE services can be preempted. Preempted PS BE services are
ranked by priority and PS BE services with the lowest priority are preempted.
5.7 Queuing
This section describes the queuing algorithm in the WRFD-010505 Queuing and Pre-Emption feature.
For PS services, after preemption fails, the RNC performs queuing if the following conditions are met:
The RNC receives an RAB ASSIGNMENT REQUEST message indicating that queuing is supported.
The UE requesting DC-HSDPA services will be queued in the selected primary cell.
Full Checks whether the integrated priority of any existing request is lower than that of
the new request
If yes, then the queuing algorithm:
- Checks the queuing time of each request. The algorithm removes the request
with the longest queuing time from the queue
- Stamps the new request with the request time (T_request) and then puts it into
the queue
- Starts the heartbeat timer if it is not started
If no, then the queuing algorithm rejects the new request directly
After the heartbeat timer expires, the queuing algorithm performs resource-based admission attempts as
follows:
Rejects the request if the queuing time of the request(Telapsed) is longer than the maximum queuing
time (MaxQueueTimeLen). Here, Telapsed is equal to the current time minus the request time
(T_request).
Selects the request with the highest integrated priority for a resource-based admission attempt.
If more than one service has the highest integrated priority, the RNC selects the request with the
longest queuing time.
If the attempt is successful, the heartbeat timer is restarted for the next processing.
If the attempt fails, the queuing algorithm proceeds as follows:
− Putsthe service request back into the queue with the request time (T_request) unchanged for the next
attempt.
− Selectsthe request with the longest queuing time from the rest and makes another attempt until a
request is accepted or all requests are rejected.
After an appropriate access action is determined, the service attempts to access the network.
If the action of access from the DCH at 0 kbit/s is determined, the service attempts to access the
network at 0 kbit/s for traffic and at the normal rate for signaling. For details about the methods of
resource-based admission decision, see the Call Admission Control Feature Parameter Description.
If the action of access from the FACH/E-FACH is determined, the service attempts to access the
network from the FACH/E-FACH.
If the attempt fails, this service is rejected.
For the service that accesses the network at 0 kbit/s, the ZeroRateUpFailToRelTimerLen timer is
started after the service rate fails to increase for the first time. If the rate fails to increase even after the
timer expires, the service is released, and the connection is also released for a single service.
If no data is transmitted for some time after the access, the UE state changes to another state. For
details about state transition, see the State Transition Feature Parameter Description.
The RNC does not perform RRC redirection for service steering.
In the case of power-based admission, the emergency call is admitted regardless of whether the CAC
function is enabled or not.
In the case of hard resource-based admission, the emergency call is admitted if the current remaining
resources are sufficient for RRC connection setup. If the admission fails, preemption is performed
regardless of whether the preemption is enabled or not. The emergency call that triggers preemption has
the highest priority. The range of users who can be preempted is specified by the
EmcPreeRefVulnSwitch parameter.
If EmcPreeRefVulnSwitch is set to ON, all non-emergency users who have accessed the network
can be preempted, regardless of the preemption-prohibited attribute of the users.
If EmcPreeRefVulnSwitch is set to OFF, only the non-emergency users with preemption-allowed
attribute can be preempted.
The principles for selection of specific users to be preempted are the same as those for common
services. For details, see section 5.6 "Preemption."
As shown in Figure 6-2, the RNC performs the following actions in each ULB period (specified by the
IntraFreqULBPeriodTimerLen parameter):
1. The RNC obtains RTWP from the NodeB and then performs smooth filtering on the RTWP value. The
smooth filtering window is specified by the ULBAvgFilterLen parameter.
2. The RNC evaluates the uplink load of the current cell based on the filtered RTWP value.
− If
the filtered RTWP value is between RTWPHeavyThd and RTWPLightThd, the RNC considers the
load of the current cell to be normal. In this case, the RNC does not adjust the pilot power in this
period.
− If
the filtered RTWP value is more than or equal to RTWPHeavyThd, the RNC considers the load of
the current cell to be heavy. In this case, the RNC performs step 3.
− If
the filtered RTWP value is less than or equal to RTWPLightThd, the RNC considers the load of the
current cell to be light. In this case, the RNC performs step 4.
3. The RNC compares the current pilot power and MinPCPICHPower. If the current pilot power is more
than MinPCPICHPower, the RNC decreases the current pilot power by one step (specified by the
PCPICHPowerPace parameter). Otherwise, the RNC does not adjust the pilot power in this period.
4. The RNC compares the current pilot power and MaxPCPICHPower. If the current pilot power is less
than MaxPCPICHPower, the RNC increases the current pilot power by one step (specified by the
PCPICHPowerPace parameter). Otherwise, the RNC does not adjust the pilot power in this period.
7 Load Reshuffling
This chapter describes the WRFD-020106 Load Reshuffling feature.
When the usage of cell resource exceeds the basic congestion trigger 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 following figure shows the triggering and relieving of basic congestion.
Figure 7-1 Triggering and relieving of basic congestion
As shown in Figure 7-1, 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, as listed in Table 7-2, are taken. 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.
For the downlink, the hysteresis time is specified by the DlLdTrnsHysTime parameter; for the uplink, the hysteresis time
is 600ms.
The UL or DL LDR trigger threshold of a DC-HSDPA cell group equals the sum of the UL or DL LDR
trigger thresholds of the two cells in this group. The UL or DL LDR relief threshold of a DC-HSDPA cell
group equals the sum of the UL/DL LDR relief thresholds of the two cells in this group. If a DC-HSDPA
cell group is in the basic congestion state, the related LDR actions are performed in each cell separately.
The uplink load of an HSUPA cell is calculated based on the uncontrollable load of the cell. The downlink
load of an HSDPA cell is calculated based on the load of non-HSPA power and GBP in the cell.
The following table lists the LDR switches that need to be set to 1 for different algorithm types.
Table 7-1 LDR switches to be set to 1
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
For R99 cells, only DCH UEs are selected by LDR actions.
The GoldUserLoadControlSwitch parameter specifies whether the users of gold priority are selected by LDR actions.
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR rate reduction
Inter-RAT load handover in the CS domain, which involves the following actions:
− Inter-RAT Should Be Load Handover in the CS Domain
− Inter-RAT Should Not Be Load Handover in the CS Domain
The difference between the "Inter-RAT Should Be Load Handover In the CS/PS Domain" and "Inter-RAT Should Not Be
Load Handover In the CS/PS Domain" actions lies in the selection of users. The former only involves CS/PS users with
the "service handover" IE in RAB ASSIGNMENT REQUEST set to "handover to GSM should be performed", while the
latter only involves CS/PS users with the "service handover" IE set to "handover to GSM should not be performed". For
details about the "service handover" IE, see the Handover Feature Parameter Description.
Inter-RAT load handover in the PS domain, which involves the following actions:
− Inter-RAT Should Be Load Handover in the PS Domain
− Inter-RAT Should Not Be Load Handover in the PS Domain
QoS Renegotiation for Uncontrollable Real-Time Services
MBMS power reduction
The LDR actions concerning DC-HSDPA are inter-frequency load handover and inter-RAT handover in
PS domain.
The sequence of LDR actions can be changed by running the ADD UCELLLDR / ADD UNODEBLDR
command.
The following figure illustrates the detailed LDR procedure. In this example, the sequence of LDR
actions is fixed to inter-frequency load handover, code reshuffling, BE rate reduction, inter-RAT handover
in CS domain, inter-RAT handover in PS domain, AMR rate reduction, QoS Renegotiation for
Uncontrollable Real-Time Services, and MBMS power reduction.
As shown in the preceding 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:
− Ifthe 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. For details about LDR actions, see
section 7.3 "LDR Actions."
The LDR actions that are triggered by basic congestion caused by different resources are different.
Table 7-2 describes the LDR actions intended for different resources.
When the basic congestion is triggered by different resources, the congestion can be relieved in an order
set by running the SET ULDCALGOPARA command.
Inter-RAT Handover in
Inter-Frequency Load
Real-Time Services
BE Rate Reduction
Code Reshuffling
Uncontrollable
CS Domain
PS Domain
Power UL DCH √ Handover √ √ √ √ √
HSUPA √ √ √
DL DCH √ √ √ √ √* √
HSDPA √ √ √
DC-HSDPA √ √
FACH √*
(MBMS)
Iub UL DCH √ √ √ √
HSUPA √ √
DL DCH √ √ √ √
HSDPA √ √
FACH
(MBMS)
Code - -
DL DCH √ √ √
HSDPA
FACH
(MBMS)
Credit UL DCH √ √ √ √
HSUPA √ √ √
DL DCH √ √ √ √
HSDPA
FACH
(MBMS)
The Inter-RAT Handover in CS Domain action can be performed for the HSDPA services only when
the HsdpaCMPermissionInd parameter is set to TRUE.
If the downlink 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 or MBMS power
reduction, as indicated by the symbol "*" in the preceding table.
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 CE consumption, which is calculated on the basis of the Maximum Bit Rate
(MBR), can be reduced through rate downsizing. Therefore, the BE service rate downsizing for
HSUPA is applicable only for reducing CE resource congestion.
For LDR triggered by Iub resource, RNC selects UEs in the congested path or port.
The load margin refers to the difference between the load of the target cell and the basic congestion triggering threshold of
the target cell.
If the margin is not higher than the threshold, the action fails, and the algorithm takes the next action.
If there is more than one cell meeting the requirements, the first cell in the list of the neighbor cells is
selected as the blind handover target cell.
− If the basic congestion is caused by code resource:
Whether there are blind handover target cells meeting the requirements is decided by the following
conditions:
a. The minimum SF of the target cell is not greater than that of the current cell.
b. The difference of code usage between the current cell and the target cell is greater than
LdrCodeUsedSpaceThd.
c. The state of target cell is normal.
If there is no such cell, this action fails and the algorithm takes the next action. If there is more than
one cell meeting the requirements, the first cell in the list of the neighbor cells is selected as the blind
handover target cell.
3. The algorithm selects the UEs to be handed over according to the setting of
InterFreqLdHoForbidenTC and NbmLdcUeSelSwitch:
− IfNbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the algorithm performs the
following steps:
a. Selects the UEs that meet the following conditions as candidate UEs.
The service types of UEs are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC.
The service types of UEs are supported by the target cell.
b. Sorts the candidate UEs whose rates are not higher than the handover bandwidth thresholds,
based on the integrated priority.
c. Selects the UE with the lowest integrated priority for handover.
− IfNbmLdcUeSelSwitch is set to NBM_LDC_MATCH_UE_FIRST, the algorithm performs the
following steps:
a. Selects the UEs that meet the following conditions as candidate UEs.
The service types of UEs are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC.
The service types of UEs are supported by the target cell.
b. Sorts the candidate UEs whose rates are not higher than the handover bandwidth thresholds,
based on the integrated priority.
c. Selects the UE with the lowest integrated priority for handover.
If the rates of all the candidate UEs are higher than the handover bandwidth thresholds, the
algorithm performs the following steps:
a. Selects the UEs that meet the following conditions as candidate UEs.
The service types of UEs are not restricted for LDR handover by parameter
InterFreqLdHoForbidenTC.
The service types of UEs are not supported by the target cell.
b. Sorts the UEs whose rates are not higher than the handover bandwidth threshold, based on the
integrated priority.
c. Selects the UE with the lowest integrated priority for handover.
− If NbmLdcUeSelSwitch is set to NBM_LDC_ALL_UE, the algorithm performs the following steps:
a. From the current cell, selects the UEs whose service types are not restricted for LDR handover by
InterFreqLdHoForbidenTC parameter.
b. Sorts the UEs whose rates are not higher than the handover bandwidth thresholds, based on the
integrated priority.
b. Selects the UE with the lowest integrated priority for handover.
If multiple UEs have the same lowest integrated priority, the algorithm selects the one with the highest rate for handover.
The UL and DL handover bandwidth thresholds are specified by UlInterFreqHoBWThd and DlInterFreqHoBWThd
respectively. Both the thresholds are considered in the selection of the target UE.
4. After selecting the target cell and the UE, the RNC makes blind handover decision. For details, see
the Handover Feature Parameter Description.
6. The RNC selects the cell with the highest priority from the candidate target cells to perform
inter-frequency hard handover.
− If the handover succeeds, the LDR action is complete.
− If
the handover fails, the RNC tries accessing the cell with the second highest priority to perform
inter-frequency hard handover until the handover succeeds or it has tried accessing all the candidate
target cells.
If the compressed mode is required for the UE to perform inter-frequency measurement, the RNC starts the
inter-frequency measurement timer (specified by the InterFreqMeasTime parameter) as soon as the measurement
control message is issued. If inter-frequency handover remains unsuccessful until the timer expires, the RNC stops the
inter-frequency measurement and cancels the compressed mode.
When admission control of Power/NodeB Credit is disabled, it is not recommended that the BE Rate Reduction be
configured as an LDR action in order to avoid ping-pong effect.
BE rate reduction can only be performed when the DRA_DCCC_SWITCH subparameter of the
DraSwitch parameter is set to 1.
The LDR algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the BE RABs in descending order.
2. The algorithm selects the BE RABs that meet the following condition:
− The
current rate of the BE RAB is higher than the GBR specified by running the SET USERGBR
command.
− The BE RAB has the lower integrated priorities.
The number of selected RABs is specified by the UlLdrBERateReductionRabNum or
DlLdrBERateReductionRabNum parameter.
If the integrated priorities of some RABs are identical, the RAB with the highest rate is selected.
3. If services can be selected, the action is successful. If services cannot be selected, the action fails.
The algorithm takes the next action.
4. The bandwidth of the selected services is reduced to the specified rate. For details about the rate
reduction procedure, see the DCCC Feature Parameter Description.
5. The reconfiguration is complete as indicated by the RADIO BEARER RECONFIGURATION
message on the Uu interface and through the synchronized radio link reconfiguration procedure on
the Iub interface.
The RNC will request a new MBR and GBR that are the lowest ones among the alternative
configurations in the RAB ASSIGNMENT message from the CN. However, the CN can decide how to
react to the request upon reception of the RAB MODIFY REQUEST message.
The LDR algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the RABs for real-time services in the PS domain
in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities for QoS renegotiation. The
number of selected RABs is specified by the UlLdrPsRTQosRenegRabNum or
DlLdrPsRTQosRenegRabNum parameter. If the RNC cannot find an appropriate service for the
QoS renegotiation, the action fails. The algorithm takes the next action.
3. The algorithm performs QoS renegotiation for the selected services. The GBR during the service
setup is the minimum rate of the service after the QoS renegotiation.
4. The RNC initiates the RAB MODIFY REQUEST message to the CN for the QoS renegotiation. Upon
reception of the RAB MODIFY REQUEST message, the CN sends the RAB ASSIGNMENT
REQUEST message to the RNC for RAB parameter reconfiguration.
HSPA services can be selected only when HsdpaCMPermissionInd is set to TRUE and HsupaCMPermissionInd is not
set to Limited.
For details about the two parameters, see the Handover Feature Parameter Description.
8 Overload Control
This chapter describes the WRFD-020107 Overload Control feature.
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 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.
For details about overload congestion caused by Iub bandwidth, see the Transmission Resource Management Feature
Parameter Description.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the
NBMLdcAlgoSwitch parameter.
The following figure shows the triggering and release of cell power overload.
Figure 8-1 Triggering and release of cell power overload
As shown in Figure 8-1, 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.
For the downlink, the hysteresis time is specified by the parameter DlLdTrnsHysTime; for the uplink, the hysteresis time
is 600ms.
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.
The uplink load of an HSUPA cell is calculated based on the uncontrollable load of the cell. The downlink
load of an HSDPA cell is calculated based on the load of non-HSPA power and GBP in the cell.
In addition to periodic measurement, event-triggered measurement is applicable to OLC.
If the subparameter OLC_EVENTMEAS of the parameter NBMLdcAlgoSwitch is set to 1, the RNC
sends the NodeB a request for event measurement based on power resource. In the associated request
message, the reporting criterion is specified, including the hysteresis time, the related OLC thresholds.
Then the NodeB checks the current power load in real time according to this criterion and reports the
status to the RNC periodically if the conditions of reporting are met.
Limited by 3GPP, the NodeB cannot check the total load of the non-HSDPA power and the GBP. Therefore, the
recommended setting of OLC_EVENTMEAS is 0 for HSDPA cells.
− 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.
4. If the number of times that TF control is performed exceeds DlOlcFTFRstrctTimes, the action fails.
The OLC takes the next action.
5. If the congestion is relieved, the RNC sends the congestion relief indication to the MAC. At the same
time, the rate recovery timer (RateRecoverTimerLen) is started. When this timer expires, the MAC
increases the data rate step by step.
MAC recovers the TFC selection by calculating the maximum TB number according to the following
formula:
TFmax(N+1) = TFmax(N) x RateRecoverCoeff
Here:
− TFmax(0) is the maximum TB number of the BE service before congestion relief indication is
received.
− TFmax(N+1) is the maximum TB number during the period from (T1 + RateRecoverTimerLen x N)
to (T1 + (RateRecoverTimerLen x (N + 1)), where T1 is the time when the MAC receives the
congestion relief indication message.
− RateRecoverCoeff is specified by the RecoverCoef parameter.
The preceding power adjustment is applicable to only the FACH carrying common services rather than MBMS services.
2. 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.
3. The selected RABs are released directly.
This function is disabled when the UlOlcTraffRelRabNum, DlOlcTraffRelRabNum, and MbmsOlcRelNum parameters
are set to 0.
The higher the value of UlOlcTraffRelRabNum or DlOlcTraffRelRabNum, the more the cell load decreases, which will
affect the users experience negatively.
9 Parameters
Table 9-1 Parameter description
Parameter ID NE MML Command Description
AMRQosPerform BSC6900 SET Meaning: When the parameter is set to YES, the
UQOSACT(Optional) QoS control algorithm is used for AMR services.
When the parameter is set to NO, the QoS
control algorithm is not used for AMR
services.The QoS actions of AMR services
include rate downsizing, inter frequency
handover and inter rat handover.
GUI Value Range: NO, YES
Actual Value Range: NO, YES
Default Value: NO
BGNAdjustTimeLe BSC6900 ADD Meaning: Only when the measured background
n UCELLCAC(Optional) noise's duration reaches this parameter, the
MOD output of the auto-adaptive background noise
UCELLCAC(Optional) update filter could be regarded as effect
background noise, and the current value is
replaced with the new one. At the same time,
the auto-adaptive status should be restarted;
otherwise, the output could not be regarded as
the effective background noise.
GUI Value Range: 1~6000
Actual Value Range: 1~6000
Default Value: 120
BGNEqUserNumT BSC6900 ADD Meaning: When the number of uplink equivalent
hd UCELLCAC(Optional) users is not larger than this parameter, the
MOD RTWP could be regarded as background noise.
UCELLCAC(Optional) Therefore, the measured RTWP could be input
to the auto-adaptive background noise update
filter; otherwise, the RTWP could not be
regarded as background noise, and should not
be input to the filter, and at the same time, the
auto-adaptive status should be reset.
GUI Value Range: 0~10
Actual Value Range: 0~10
Default Value: 0
BGNSwitch BSC6900 ADD Meaning: When the parameter is 'OFF', the
UCELLCAC(Optional) auto-adaptive background noise update
MOD algorithm is switched off. Otherwise, the
UCELLCAC(Optional) algorithm is switched on.
GUI Value Range: OFF, ON
Actual Value Range: OFF, ON
Default Value: ON
BackgroundNoise BSC6900 ADD Meaning: If [Auto-Adaptive Background Noise
10 Counters
Table 10-1 Counter description
Counter Counter Name Counter Feature ID Feature Name
ID Description
67180549 VS.HHO.AttInterCellLB.S Number of WRFD-020103 Inter Frequency Load
ingleRL Outgoing Balance
Inter-Frequency
Hard Handover
Attempts Due to
Load Balancing for
Cell (Single RL)
67180550 VS.HHO.SuccInterCellLB Number of WRFD-020103 Inter Frequency Load
.SingleRL Successful Balance
Outgoing
Inter-Frequency
Hard Handovers
Due to Load
Balancing for Cell
(Single RL)
67183900 VS.HHO.AttInterFreqOut Number of WRFD-020302 Inter Frequency Hard
Outgoing WRFD-020304 Handover Based on
Inter-Frequency Coverage
Hard Handover WRFD-020106
Inter Frequency Hard
Attempts for Cell Handover Based on DL QoS
Load Reshuffling
67183901 VS.HHO.SuccInterFreqO Number of WRFD-020302 Inter Frequency Hard
ut Successful WRFD-020304 Handover Based on
Outgoing Coverage
Inter-Frequency WRFD-020106
Inter Frequency Hard
Hard Handovers for Handover Based on DL QoS
Cell
Load Reshuffling
67189852 VS.LCC.OLC.UL.Num Number of UL WRFD-020107 Overload Control
Overload
Congestions for
Cell
67189853 VS.LCC.OLC.DL.Num Number of DL WRFD-020107 Overload Control
Overload
Congestions for
Cell
67189856 VS.PUC.High.Offset.Updt Number of Qoffset WRFD-020105 Potential User Control
Updates Due to
Heavy Load for Cell
67189857 VS.PUC.Light.Offset.Upd Number of Qoffset WRFD-020105 Potential User Control
t Updates Due to
Light Load for Cell
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
12 Reference Documents
[1] 3GPP TS 25.133: Requirements for Support of Radio Resource Management (FDD)
[2] 3GPP TS 25.215: Physical layer - Measurements (FDD)
[3] 3GPP TS 25.321: Medium Access Control (MAC) protocol specification
[4] 3GPP TS 25.331: Radio Resource Control (RRC)
[5] 3GPP TS 25.413: UTRAN Iu Interface RANAP Signaling
[6] DCCC Feature Parameter Description
[7] AMR Feature Parameter Description
[8] MBMS Feature Parameter Description
[9] HSDPA Feature Parameter Description
[10] HSUPA Feature Parameter Description
[11] Transmission Resource Management Feature Parameter Description
[12] Handover Feature Parameter Description