Académique Documents
Professionnel Documents
Culture Documents
Issue 01
Date 2009-03-30
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks
and trade names mentioned in this document are the property of their respective holders.
Notice
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 the warranty of any kind, express or implied.
Error! Unknown document property name.
Error! Unknown document property name. About This Document
Author
Prepared by Wu Xianbin Date 2008-10-26
Contents
13 Reference Documents................................................................................................................. 1
1 Change History
The change history provides information on the changes in different document versions.
01 (2009-03-30)
This is the document for the first commercial release of RAN11.0.
Compared with issue draft (2009-03-10) of RAN11.0, this issue incorporates the following
changes:
Draft (2009-03-10)
This is the second draft of the document for RAN11.0.
Compared with issue draft(2009-01-15) of RAN11.0, draft (2009-03-10) incorporates the
following changes:
Draft (2009-01-15)
This is the initial draft of the document for RAN11.0.
Compared with issue 03 (2008-12-30) of RAN10.0, draft (2009-01-15) incorporates the
following changes:
The WCDMA system is a self-interfering system. As the load of the system increases, the
interference rises. A relatively high interference can affect the coverage and QoS of
established services. Therefore, the capacity, coverage, and QoS of the WCDMA system are
mutually affected.
Through the control of key resources, such as power, downlink channelization codes, channel
elements (CEs), Iub transmission resources, which directly affect user experience, load
control aims to maximize the system capacity while ensuring coverage and QoS.
In addition, load control provides differentiated services for users with different priorities. For
example, when the system resources are insufficient, procedures such as direct admission,
preemption, redirection can be performed to ensure the successful access of emergency calls
to the network.
Intended Audience
This document is intended for:
System operators who need a general understanding of load control.
Personnel working on Huawei products or systems.
Impact
Impact on System Performance
This feature has no impact on system performance.
Impact on Other Features
This feature has no impact on other features.
- - - -
NOTE:
: not involved
: involved
UE = User Equipment, RNC = Radio Network Controller, MSC Server = Mobile Service Switching
Center Server, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway
GPRS Support Node, HLR = Home Location Register
The load control algorithms are applied to the 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)
In addition, functional load control algorithms vary depending on the load levels of the cell, as
shown in the following figure.
Figure 3-2 Load control algorithms used on different cell load levels
NodeB TX
power (noise)
The function of PUC is to balance traffic load between inter-frequency cells. The RNC
uses PUC to modify cell selection and reselection parameters, and broadcasts them
through system information. In this way, UEs are led to cells with a light load. The UEs
can be in idle mode, CELL_FACH state, CELL_PCH state, or URA_PCH state.
Intelligent Access Control (IAC)
The function of IAC is to increase the access success rate with the current QoS
guaranteed through rate negotiation, queuing, preemption, and Directed Retry Decision
(DRD).
Call Admission Control (CAC)
The function of CAC is to decide whether to accept resource requests from UEs, such as
access, reconfiguration, and handover requests, depending on the resource status of the
cell.
Intra-frequency Load Balancing (LDB)
The function of intra-frequency LDB is to balance the cell load between neighboring
intra-frequency cells to provide better resource usage.
Load Reshuffling (LDR)
The function of LDR is to reduce the cell load when the available resources for a cell
reach the specified alarm threshold. The purpose of LDR is to increase the access success
rate by taking the following actions:
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR voice service rate reduction
QoS renegotiation for uncontrollable real-time services
CS inter-RAT load handover
PS inter-RAT load handover
MBMS power reduction
Overload Control (OLC)
The function of OLC is to reduce the cell load rapidly when the cell is overloaded. The
purpose of OLC is to ensure the system stability and the QoS of most UEs in the
following ways:
Restricting the Transport Format (TF) of the BE service
Switching BE services to common channels
Adjusting the maximum transmit power of FACHs
Releasing some RABs
Dynamic power sharing among carriers
In dynamic power sharing among carriers, a carrier that carries the HSPA service can
dynamically use the idle power resource of another carrier, thus improving the power
usage and the cell HSPA service rate.
Each load control algorithm involves three factors: measuring, triggering, and controlling.
Valid measurement is a prerequisite for effective control.
The following table lists the resources that are considered by different load control algorithms.
CAC
IAC
PUC - - -
LDB - - -
LDR
OLC - -
NOTE
: not considered
: considered
User ERROR 1 1 1 1 1 2 2 2 2 2 3 3 3 3 3
Priority
ARP 15 is always the lowest priority and is not configurable. It corresponds to user priority 3 (copper).
If ARP is not received in messages from the Iu interface, the user priority is regarded as copper.
The levels of user priority are mainly used to provide different QoS for different users, for
example, setting different Guaranteed Bit Rate (GBR) values for BE services according to
different priority levels.
The GBR of BE services are configurable. According to the traffic class, priority level, and
carrier type (DCH or HSPA), the different values of GBR are configured through the SET
USERGBR command.
Changes in the mapping between ARP and user priority have an influence on the following
features:
High Speed Downlink Packet Access (HSDPA)
High Speed Uplink Packet Access (HSUPA)
Adaptive Multi Rate (AMR)
Adaptive Multi-Rate Wideband (AMR-WB)
Iub overbooking
Load control
ARP and THP are carried in the RAB ASSIGNMENT REQUEST message, and they are not
configurable on the RNC LMT.
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.
The load control algorithms, such as OLC and CAC, use load measurement values in the
uplink and the downlink. A common Load Measurement (LDM) algorithm is required to
control load measurement in the uplink and the downlink, which makes the algorithm
relatively independent.
The NodeB and the RNC perform measurements and filtering. The statistics obtained after the
measurements and filtering serve as the data input for the load control algorithms.
This chapter consists of the following sections:
Measurement Quantities and Procedure
Load Measurement Filtering
Auto-Adaptive Background Noise Algorithm
Received Scheduled E-DCH Power Share (RSEPS): power of the E-DCH scheduling
service
The NodeB measures the major measurement quantities and then obtains original
measurement values. After layer 3 filtering on the NodeB side, the NodeB reports the cell
measurement values to the RNC.
The RNC performs smooth filtering on the measurement values reported from the NodeB and
then obtains the measurement values, which further serve as data input for the load control
algorithms.
The Provided Bit Rate (PBR) measurement, however, does not use alpha filtering on the NodeB side.
The following figure shows the measurement model at the physical layer that is compliant
with 3GPP 25.302.
Parameters Parameters
A Layer 1 B Layer 3 C D
filtering filtering Measurement
evaluation
C
In Figure 4-5:
A is the sampling value of the measurement.
B is the measurement value after layer 1 filtering.
C is the measurement value after layer 3 filtering.
C' is another measurement value (if any) for measurement evaluation.
D is the reported measurement value after measurement evaluation on the conditions of
periodic measurement and event-triggered measurement.
Layer 1 filtering is not standardized by protocols and it depends on vendor equipment. Layer
3 filtering is standardized. The filtering effect is controlled by a higher layer. The alpha
filtering that applies to layer 3 filtering is calculated according to the following formula:
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, where k is specified by the UlBasicCommMeasFilterCoeff or
DlBasicCommMeasFilterCoeff parameter.
Delay susceptibilities of PUC, CAC, LDR, and OLC to common measurement are different.
The LDM algorithm must apply different smooth filter coefficients and measurement periods
to those algorithms; thus, they can get expected filtered values.
The following table lists the smooth window length parameters for setting different
algorithms.
Issue Error! Unknown Error! Unknown document property 3
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 4 Load Measurement Algorithm
GBP measurements have the same smooth window length in all related algorithms. The filter length for
GBP measurement is specified by the HsdpaNeedPwrFilterLen parameter.
RTWP ChoiceRprtUnitForUlBasicMeas
TenMsecForUlBasicMeas
RSEPS
MinForUlBasicMeas
TCP ChoiceRprtUnitForDlBasicMeas
Non-HSDPA power TenMsecForDlBasicMeas
MinForDlBasicMeas
GBP ChoiceRprtUnitForHsdpaPwrMeas
TenMsecForHsdpaPwrMeas
MinForHsdpaPwrMeas
On the RNC side, the length of the PBR smooth filter window is specified by the
HsdpaPrvidBitRateFilterLen / HsupaPrvidBitRateFilterLen parameter.
Yes
Yes No
Equivalent user quantity >
BGNEqUserNumThd?
No
|Mn Fn-1| <
Set the counter to 0 BgnAbnormalThd?
Yes
Increment the
Keep the current background
counter by one
noise unchanged and set the
initial value of the filter to the
current background noise
Calculate Fn
according to the
Alpha filter formula
Set the
counter to 0 No
Does the counter reach
the counting threshold?
Yes
No |Fn - BackgroundNoise|
< BgnAbnormalThd?
Yes
Yes
The Alpha filter formula is: Fn = (1 - ) x Fn-1 + x Mn (n1). For details about this formula, see
4.2.1 "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 through BGNAdjustTimeLen.
For the setting of RTWP reporting period, see 4.2.3 "Reporting Period."
In the case that BGNSwitch is set to ON, the procedure of auto-adaptive background noise
upgrade is as follows:
1. The RNC initializes the counter and filter that are used for auto-adaptive upgrade and
sets the initial value (F0) of the filter to BackgroundNoise.
2. The RNC receives the latest RTWP measurement value (Mn) from the physical layer.
3. The RNC determines whether the current time is within the effective period of the
algorithm, that is, whether the current time is later than BgnStartTime and earlier than
BgnEndTime. If the current time is within the effective period, the RNC performs the
next step. Otherwise, the RNC waits for the next RTWP measurement value.
4. The RNC determines whether the current Equivalent Number of Users (ENU) in the cell
is greater than the value of BGNEqUserNumThd:
If the current ENU is greater than this threshold value, the RNC infers that Mn
includes other noises in addition to the background noise, and therefore it does not
feed Mn to the filter. In addition, the RNC sets the counter to zero, keeps the current
background noise unchanged, sets the initial value of the filter to the current
background noise, and waits for the next RTWP measurement value.
If the current ENU in the cell is smaller than or equal to the threshold value, the RNC
feeds Mn to the filter and performs the next step.
5. The RNC determines whether |Mn Fn-1| is smaller than the value of BgnAbnormalThd.
If it is smaller than this threshold value, the RNC increments the counter by one,
calculates Fn according to the Alpha filter formula, and performs the next step.
Otherwise, the RNC waits for the next RTWP measurement value.
6. The RNC determines whether the counter reaches the counting threshold. If it reaches
the counting threshold, the RNC performs the next step. Otherwise, the RNC waits for
the next RTWP measurement value.
7. The RNC determines whether |Fn - BackgroundNoise| is smaller than the value of
BgnAbnormalThd. The purpose is to prevent burst interference and RTWP spike. If it
is smaller than the value of BgnAbnormalThd, the RNC performs the next step.
Otherwise, the RNC sets the counter to zero and waits for the next RTWP measurement
value.
8. The RNC determines whether |Fn - current background noise| is greater than the value of
BgnUpdateThd. The purpose is to prevent frequent background noise upgrades on the
Iub interface. If it is greater than the value of BgnUpdateThd, the RNC sets the current
background noise to Fn, sets the counter to zero, and waits for the next RTWP
measurement value. Otherwise, the RNC sets the counter to zero and waits for the next
RTWP measurement value.
In the WCDMA system, the mobility management of the UE in idle or connected mode is
implemented by cell selection and reselection. The Potential User Control (PUC) algorithm
controls the cell selection and cell reselection of the potential UE and prevents an idle UE
from camping on a heavily loaded cell.
The PUC algorithm is enabled only when the PUC subparameter of the NBMLdcAlgoSwitch
parameter is set to 1.
The RNC periodically monitors the downlink load of the cell.
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.
The states of cell load are heavy, normal, and light, as shown Figure 5-8.
Item Description
Implementation The variables related to cell selection and reselection are Qoffset1(s,n)
(load level offset), Qoffset2(s,n) (load level offset), and Sintersearch
(start threshold for inter-frequency cell reselection).
The NodeB periodically reports the transmit power of the cell, and the
PUC periodically triggers the following activities:
Assessing the cell load level based on the non-HSPA power and HS-
DSCH GBP
Setting Sintersearch, Qoffset1(s,n), and Qoffset2(s,n) based on the cell
load level
Updating the parameters in system information SIB3 and SIB11
Item Description
Adjustment Based on the characteristics of inter-frequency cell selection and
reselection, the UE makes the corresponding adjustments:
Sintersearch
- When this value is increased by the serving cell, the UE starts
inter-frequency cell reselection ahead of schedule.
- When this value is decreased by the serving cell, the UE delays
inter-frequency cell reselection.
Qoffset1(s,n): applies to R (reselection) rule with CPICH RSCP
- When this value is increased by the serving cell, the UE has a
lower probability of selecting a neighboring cell.
- When this value is decreased by the serving cell, the UE has a
higher probability of selecting a neighboring cell.
Qoffset2(s,n): applies to R (reselection) rule with CPICH Ec/I0
- When this value is increased by the serving cell, the UE has a
lower probability of selecting a neighboring cell.
- When this value is decreased by the serving cell, the UE has a
higher probability of selecting a neighboring cell.
Depending on the load status of the current cell, the cell reselection parameters are adjusted.
The setting of Sintersearch affects the current cell. Its value is related to the load of the
current cell. Table 5-5 describes the changes of Sintersearch.
The configuration of Qoffset1 and Qoffset2 affects the neighboring cells. Their values are
related to the load of the current cell and the load of the neighboring cells. Table 5-6 describes
the changes of Qoffset1 and Qoffset2.
Table 5-6 Changes of Qoffset1 and Qoffset2 according to the load state
The prerequisite for the changes of the preceding parameters is that these parameters take their default
values.
The access of a service to the network consists of setup of an RRC connection and a RAB.
The Intelligent Access Control (IAC) algorithm is used to improve the access success rate.
This chapter consists of the following sections:
IAC Overview
IAC During RRC Connection Setup
Rate Negotiation
RAB DRD
Preemption
Queuing
Low-Rate Access of the PS BE Service
IAC for Emergency Calls
RAB processing
Lead UE to
RAB setup request the inter-RAT cell
Yes Is there any No
inter-frequency cell
not tried? Succeeds
Fails Fails
Inter-RAT
DRD
Inter-frequency Rate Admission Fails or not supported
DRD algorithm negotiation algorithm
Target cell Succeeds
Preemption
Service steering selected Code
PS domain:
DRD maximum rate admission Fails or not supported
Succeeds
Power Succeeds
Load balancing PS and CS Queuing
DRD admission
domains:
Fails or not supported
initial rate Credit
admission Succeeds Low-rate
PS domain: access
GBR of PS Iub resource Fails or not supported
RT service admission
Target Rate HSPA user Service request
Negotiation number admission Succeeds accepted
Service request
denied
As shown in Figure 6-9, 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 first performs RRC redirection for
service steering:
If the RNC decides UE access from the current cell, it then makes a resource-based
admission decision through the CAC algorithm. If the resource-based admission fails,
the RNC performs DRD and redirection.
The resources include power resource, code resource, Iub resource, credit resource, and number
of HSPA users.
If the RNC decides 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.
During the RAB processing, the RNC performs the following steps:
1. Performs inter-frequency DRD to select a suitable cell for service steering or load
balancing.
Issue Error! Unknown Error! Unknown document property 2
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 6 Intelligent Access Control Algorithm
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
Target Rate
Initial Rate
Negotiation
Frequency
Inter-RAT
Inter-
MBR
GBR
DCH
HSUPA -
HSDPA -
UE RNC
1. RRC CONNECTION REQUEST
No Is the switch of
RRC redirection for service
steering ON?
Yes
May the UE No
accesses the network from
the current cell?
Yes
No
Yes Is any candidate
cell available?
No
RRC redirection
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC uses the
RRC redirection algorithm for service steering to decide whether the UE may access the
network from the current cell:
If the UE needs to access the network from another cell according to the decision, the
RNC sends an RRC CONNECTION REJECT message to the UE. The message carries
the information about this cell.
If the UE attempts to access the network from the current cell according to the decision,
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. For details about CAC,
see 7 "Call Admission Control Algorithm."
If no RRC connection can be set up between the UE and the current cell, the RNC
attempts to set up an RRC connection through RRC DRD or RRC redirection.
During the RRC connection setup, the RNC implements service steering between inter-
frequency or inter-RAT cells according to the cause of RRC connection setup. In addition, the
RNC considers the load of the cell for access and the redirection factors to control the degree
of load balancing.
The procedure of RRC redirection for service steering is as follows:
1. The RNC obtains the information about the service requested by the UE and the
capability of the UE.
2. If the switch of RRC redirection for service steering is on, the RNC determines the
service type requested by the UE. If the switch is off or the RNC fails to determine the
service type, the RNC handles the RRC connection setup request of the UE in the current
cell.
3. If the RNC succeeds in determining the service type requested by the UE and the switch
of RRC direction for service steering (RedirSwitch) is set to
ONLY_TO_INTER_FREQUENCY or ONLY_TO_INTER_RAT, the RNC performs
the next step. Otherwise, the RNC handles the RRC connection setup request of the UE
in the current cell.
4. Based on the cell load and the redirection factors, the RNC decides whether to perform
RRC redirection for service steering.
If the cell is normal, the RNC generates a random number between 0 and 1 and
compares it with the corresponding unconditional redirection factor
(RedirFactorOfNorm). If the random number is smaller than this factor, the RNC
performs the next step. Otherwise, the RNC handles the RRC connection setup
request of the UE in the current cell.
If the cell is in the basic congestion or overload state, the RNC generates a random
number between 0 and 1 and compares it with the corresponding LDR-triggered
redirection factor (RedirFactorOfLDR). If the random number is smaller than this
factor, the RNC performs the next step. Otherwise, the RNC handles the RRC
connection setup request of the UE in the current cell.
5. Based on the setting of RedirSwitch, the RNC takes the corresponding actions:
If RedirSwitch is set to ONLY_TO_INTER_FREQUENCY, the RNC sends an
RRC CONNECTION REJECT message to the UE, redirecting the UE to the
destination frequency carried in the message.
The frequency information carried in the message can be set through the parameters RedirBandInd,
ReDirUARFCNUplinkInd, ReDirUARFCNUplink, and ReDirUARFCNDownlink.
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.
Issue Error! Unknown Error! Unknown document property 5
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 6 Intelligent Access Control Algorithm
Here:
ON ON In the uplink, the initial rate is the smaller one of the MBR
and 384 kbit/s.
In the downlink, the initial rate is dynamically set on the
basis of Ec/N0. For the specific method, see the description
following this table.
ON OFF In the uplink, the initial rate is the smaller one of the MBR
and the initial rate of the uplink BE service.
In the downlink, the initial rate is the smaller one of the MBR
and the initial rate of the downlink BE service.
OFF - MBR
The parameter corresponding to the DCCC switch is DCCC_SWITCH.
The parameter corresponding to the PS BE initial rate dynamic configuration switch is
PS_BE_INIT_RATE_DYNAMIC_CFG_SWITCH.
As described in the table, when the two switches are ON, the initial rate is dynamically set on
the basis of Ec/N0 in the downlink. The specific method is as follows:
When receiving an RRC connection setup request, the RNC starts the timer
EcN0EffectTime.
Before the timer expires, the RNC dynamically sets the initial rate based on the P-
CPICH Ec/N0 carried in the RRC CONNECTION REQUEST message:
If the cell Ec/N0 is above the Ec/N0 threshold (EcN0Ths), the RNC sets the actual
initial rate to the smaller one of the MBR and 384 kbit/s.
If the cell Ec/N0 is below or at the Ec/N0 threshold (EcN0Ths) or the RRC
CONNECTION REQUEST message does not carry the information about Ec/N0, the
RNC sets the actual initial rate to the smaller one of the MBR and the initial rate of
the downlink BE service (DlBeTraffInitBitrate).
If the DCCC function is enabled and PS_RAB_Downsizing_Switch 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.
3. If all admission attempts of inter-RAT DRD fail, the RNC selects a suitable cell to
perform preemption and queuing (for selection of the target cell for preemption or
queuing, see Preemption).
For details about preemption and queuing, see Preemption and Queuing, respectively.
"Inter-frequency DRD for service steering" is called "DRD for service steering" for short in this section.
Cell Service Service Priority Service Priority of Service Priority Service Priority
Priority of R99 RT Service R99 NRT Service of HSPA Service of Other Service
Group
Identity
A 1 2 1 1 0
B 2 1 2 0 0
As shown in Figure 6-11, cell B has a higher service priority of the R99 RT service than cell A.
If the UE requests an RT service in cell A, preferably the RNC selects cell B for the UE to
access.
A 1
B 2
Cell B
Cell A
RT service
If the requested service is a combination of multiple services, the RAB with the highest priority is used
when a cell is selected for RAB processing. In addition, the target cell must support all these services.
This section describes the procedure of DRD for service steering when DRD for load balancing is
disabled.
The frequency of the candidate cell is within the band supported by the UE.
The quality of the candidate cell meets the requirements of inter-frequency DRD. For
details, see 6.2 "IAC During RRC Connection Setup."
The candidate cell supports the requested service.
2. The RNC selects a target cell from the candidate cells in order of service priority for UE
access.
If there is more than one cell with the same service priority,
When the cell, in which the UE requests the service, is one of the candidate cells with
the same service priority, preferably, the RNC selects this cell for admission decision.
Otherwise, the RNC randomly selects a cell as the target cell.
3. The CAC algorithm makes an admission decision based on the status of the target cell.
If the admission attempt is successful, the RNC accepts the service request.
If the admission attempt fails, the RNC removes the cell from the candidate cells and
then checks whether all candidate cells are tried.
If there are any cells where no admission decision has been made, the algorithm goes
back to step 2.
If admission decisions have been made in all the candidate cells, then:
a.If the service request is an HSPA one, the HSPA request falls back to a DCH one.
Then, the algorithm goes back to step 1 to make an admission decision based on R99
service priorities.
b.If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
"Inter-frequency DRD for load balancing" is called "DRD for load balancing" for short in this section.
This section describes the procedure of DRD for load balancing when DRD for service steering is
disabled.
The following two algorithms are available for power-based load balancing. If power-based
DRD for load balancing is enabled, one of them can be used. The algorithm used is specified
by the LdbDRDchoice parameter.
Algorithm 1: DRD for load balancing is performed according to the cell measurement
values about the DL non-HSDPA power and DL HS-DSCH GBP.
For DCH service, the RNC sets up the service on a carrier with a light load of non-
HSPA power to achieve load balancing among the cells at the different frequencies.
For HSDPA service, the RNC sets up the service on a carrier with a light load of HS-
DSCH GPB to achieve load balancing among the cells at different frequencies.
Algorithm 2: DRD for load balancing is performed according to the DCH ENU and
HSDPA user number.
For DCH service, the RNC sets up the service on a carrier with a light load of DCH
ENU to achieve load balancing among the cells on different frequencies.
For HSDPA service, the RNC sets up the service on a carrier with a light load of
HSDPA user to achieve load balancing among the cells on different frequencies.
As shown in Figure 6-13:
Cell B has a lighter load of non-HSDPA power than cell A. If the UE requests a DCH
service in cell A, preferably, the RNC selects cell B for the UE to access.
Cell A has a lighter load of HS-DSCH GBP than cell B. If the UE requests an HSDPA
service in cell B, preferably, the RNC selects cell A for the UE to access.
Cell B
Cell A
Load
Figure 6-14 shows the procedure of power-based DRD for load balancing.
Receive a
service request
No
Does power of a No
neighboring cell meet DRD
condition 2?
HSPA falls
Yes
back to DCH
No Are there multiple
such cells available?
Yes
Select the cell meeting Select the cell with the Select the
the DRD conditions as lightest power load as current cell as
the target cell the target cell the target cell
Yes No
Here:
Thdnon H is specified by LdbDRDLoadRemainThdDCH.
Thd H is specified by LdbDRDLoadRemainThdHSDPA.
If... Then...
Condition 1 is met The service tries admission to the current cell. Go to step 5.
Condition 1 is not met Go to step 4.
Thd total , nbcell PGBP ,nbcell Thd total ,cutcell PGBP ,cutcell Thd H ,loadoffset
Thd total , cutcell Pload , cutcell Thd total , nbcell Pload , nbcell Thd total ,loadoffset
For a DCH service
Thd AMR , nbcell Pnon H , nbcell Thd AMR , cutcell Pnon H , cutcell Thd D ,loadoffset
Thd total , cutcell Pload , cutcell Thd total , nbcell Pload , nbcell Thd total ,loadoffset
If algorithm 2 is used, condition 2 is as follows:
For an HSDPA service
Thd H ue , nbcell PH ue ,nbcell / Thd H ue ,nbcell Thd H ue,cutcell PH ue,cutcell / Thd H ue,cutcell
Thd H ,loadoffset
Thd AMR , nbcell PD enu , nbcell Thd AMR , cutcell PD enu , cutcell Thd D ,loadoffset
Issue Error! Unknown Error! Unknown document property 15
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 6 Intelligent Access Control Algorithm
If the admission attempt fails, the RNC checks whether admission decisions have been
made in all candidate inter-frequency neighboring cells.
If there is any cell where no admission decision is made, the algorithm goes back to
step 2.
If admission decisions have been made in all the candidate cells:
a.When the service request is an HSPA one, the HSPA request falls back to a DCH
one. Then, the algorithm goes back to step 1 to make an admission decision based on
R99 service priorities.
b.When the service request is a DCH one, the RNC initiates an inter-RAT DRD.
Start
Yes
No
No
Yes
Select the cell with
the lightest code load
from the cells with the
Select the same service priority
Select the cell with the lightest code
current cell as as the target cell
load as the target cell
the target cell
If the minimum SF supported by the cell with the lightest code load is the same as
that supported by the current cell, and the difference between the code resource
occupancies of the two is larger than or equal to the value of
DeltaCodeOccupiedRate, the RNC selects the cell with the lightest code load as the
target cell. Otherwise, the RNC selects the current cell as the target cell.
If the minimum SF supported by the cell with the lightest code load is smaller than
the minimum SF supported by the current cell, the RNC selects the cell with the
lightest code load as the target cell.
"Inter-frequency DRD for service steering" is called "DRD for service steering" for short in this section.
"Inter-frequency DRD for load balancing" is called "DRD for load balancing" for short in this section.
When both DRD for service steering and DRD for load balancing are enabled, the general
principles of inter-frequency DRD are as follows:
DRD for service steering takes precedence over DRD for load balancing, that is,
preferably considers service priorities.
To services of the same service priority, load balancing applies.
For example, Universal Terrestrial Radio Access Network (UTRAN) f1, UTRAN f2, UTRAN
f3, and UTRAN f4 in Figure 6-16 are inter-frequency cells with the same coverage. The
service priorities of real-time R99 services in these cells are listed in the following table.
UTRAN f1 3
UTRAN f2 2
UTRAN f3 1
UTRAN f4 1
According to the principles of inter-frequency DRD, the RAB DRD of a real-time R99 service
will select UTRAN f3 to make a CAC decision, as shown in Figure 6-16.
Receive a
service request
Determine a target
cell in order
No Yes
CAC No Yes No
Are all cells Is the request Initiate an
successful? tried? an HSPA one? inter-RAT DRD
Yes
Initiate a blind
handover
If both DRD for load balancing and DRD for service steering are enabled:
1. The RNC determines the candidate cells to which blind handovers can be
performed. A candidate cell must meet the following conditions:
The candidate cell supports the requested service.
The frequency of the candidate cell is within the band supported by the UE.
The quality of the candidate cell meets the requirements of inter-frequency DRD.
2. The RNC selects a target cell from the candidate cells for UE access.
Based on the relation between DRD for service steering and DRD for load
balancing:
The RNC preferably selects the cell with the highest service priority.
If there are multiple cells with the highest service priority, load balancing applies
to these cells. In this case, the RNC follows the same DRD logic as described in
Inter-Frequency DRD for Load Balancing.
3. The CAC algorithm makes an admission decision based on the resource status of
the cell.
If the admission attempt is successful, the RNC initiates an inter-frequency blind
handover to the cell.
If the admission attempt fails, the RNC removes the cell from the candidate cells
and then checks whether all candidate cells are tried.
a. If there is any candidate cell not tried, the algorithm goes back to step 2 to try
this cell.
b. If all candidate cells haven been tried, then:
If the service request is an HSPA one, the HSPA request falls back to a DCH
one. Then, the algorithm goes back to step 1 to retry admission based on
R99 service priorities.
If the service request is a DCH one, the RNC initiates an inter-RAT DRD.
For details about the CAC procedure, see 7 "Call Admission Control Algorithm."
For details about inter-RAT DRD, see 6.4.5 "Inter-RAT DRD."
Here:
The RAN11.0 does not support inter-RAT DRD for RABs of combined services.
The RAN11.0 does not support inter-RAT DRD for R99 PS services.
The RAN11.0 does not support inter-RAT DRD for HSPA services.
6.5 Preemption
By forcibly releasing the resources of lower-priority users, the preemption algorithm increases
the access success rate of higher-priority users.
After cell resourcebased admission fails, the RNC performs preemption if the following
conditions are met:
The RNC receives a RAB ASSIGNMENT REQUEST message indicating that
preemption is supported.
The preemption algorithm switch (PreemptAlgoSwitch) is set to ON.
Preemption is applicable to the following scenarios:
Setup or modification of a service
Hard handover or SRNS relocation
UE state transition from CELL_FACH to CELL_DCH
For preemption, the RNC selects a suitable cell according to the settings of the DRD
algorithms. Table 6-8 describes the selection of the target cell for preemption or queuing.
Table 6-9 describes the preemption for different types of service on different resources.
To enable resource-triggered preemption for MBMS services, the MBMS preemption algorithm switch
(MbmsPreemptAlgoSwitch) must be set to ON.
For details about preemption of MBMS services, see the MBMS Parameter Description.
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 the power reason, the preempted objects can be R99 users, R99 +
HSDPA combined users, or HSDPA RABs.
For the preemption triggered for the Iub bandwidth reason, the preempted objects can only be RABs.
For the preemption triggered for the code or Iub resource reason, only one user can be preempted.
For the preemption triggered for the power or credit resource reason, more than one user can be
preempted.
2. The RNC releases the resources occupied by the candidate users or RABs.
3. The requested service directly uses the released resources to access the network without
admission decision.
6.6 Queuing
When the queuing algorithm is enabled through QueueAlgoSwitch parameter and the RNC
receives a RAB ASSIGNMENT REQUEST message, indicating that the queuing function is
supported, the RNC triggers queuing actions if preemption fails.
The queuing algorithm is triggered by the heartbeat timer that equals 500 ms. Each time the
timer expires, the RNC selects the service that meets the requirement to make an admission
attempt.
The queuing algorithm takes the following actions:
The queuing algorithm checks whether the queue is full, that is, whether the number of
service requests in the queue exceeds the queue length, which equals 5.
The queuing algorithm decides whether to put the request into the queue, as described in
Table 6-10.
Not full Stamps this request with the request time (T_request).
Puts this request into the queue.
Starts the heartbeat timer if it is not started.
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 for a power-based admission attempt.
If the attempt is successful, the heartbeat timer is restarted for the next processing.
If the attempt fails, the queuing algorithm proceeds as follows:
Puts the service request back into the queue with the request time (T_request)
unchanged for the next attempt.
Selects the request with the longest queuing time from the rest and makes another
attempt until a request is accepted or all requests are rejected.
After a service request is rejected, the low-rate access actions in different scenarios are as
follows:
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 7 "Call Admission Control
Algorithm."
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 when the timer expires, the service is released, and the connection is also
released for a single service.
If no data is transmitted during a period after the access, the UE state changes to another state.
For details about state transition, see the Rate Control Parameter Description.
RAB process
To guarantee a successful admission of an emergency call, 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 algorithm is enabled or not.
In the case of hard resourcebased 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 that can be
preempted is specified by the EmcPreeRefVulnSwitch parameter.
If EmcPreeRefVulnSwitch is set to ON, all non-emergency users that 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
ordinary services. For details, see 6.5 "Preemption."
As the access decision procedure of IAC, Call Admission Control (CAC) is used to determine
whether the system resources are sufficient to accept a new user's access request or not. If the
system resources are sufficient, the access request is accepted; otherwise, the access request is
rejected.
This chapter consists of the following sections:
CAC Overview
CAC Based on Code Resource
CAC Based on Power Resource
CAC Based on NodeB Credit Resource
CAC Based on Iub Resource
CAC Based on the Number of HSPA Users
Admission request
Code-based No
admission successful?
Yes
Power-based No
admission successful?
Yes
No
NodeB credit-based
admission successful?
Yes
No
Iub resource-based
admission successful?
Yes
Admission based on No
the number of HSPA users
successful?
Yes
When NBMUlCacAlgoSelSwitch is set to ALGORITHM_OFF and the uplink OLC algorithm switch
(UL_UU_OLC) is enabled, the following cases occur if the cell is in the OLC state triggered by the
RTWP:
If the Control RTWP Anti-interfence algorithm switch (RsvdBit1) is enabled, the system checks
whether the uplink equivalent user load proportion of the cell is lower than 40%. If it is lower than
40%, the access request is accepted. Otherwise, the original algorithm procesure reamins unchanged.
If the Control RTWP Anti-interfence algorithm switch is disabled, the RNC rejects the access
request.
Request initiation
Uplink call
admission decision
No
Admitted?
Yes
Downlink call
admission desicion
No
Admitted?
Yes
The procedure of uplink powerbased admission decision for R99 cells is as follows:
1. The RNC obtains the uplink RTWP of the cell and uses the formula
to calculate the current uplink load factor UL, where PN is the received uplink
background noise.
2. The RNC calculates the uplink load increment UL based on the service request.
3. The RNC uses the following formula to predict the uplink load factor:
UL,predicted = UL + UL + ULcch
In the formula, ULcch is specified by UlCCHLoadFactor.
The measure taken by CAC is determined by the actual bearer type and whether the
scheduling mode is used.
Admission of HSUPA Scheduling Services and HSUPA Non-Scheduling Services
Since the HSUPA scheduling algorithm consumes additional uplink power resources, the
power load of the HSUPA cell is always relatively high. Therefore, the CAC algorithm
combines the PBR-based decision with the load-based decision to reduce the number of
potential erroneous rejections.
PBR-based decision is used to check whether the QoS requirement of existing users is
fulfilled. The QoS is measured on the basis of the Provided Bit Rate (PBR) of the users.
If the QoS requirement is fulfilled, new users are allowed to access the network.
As shown in the previous figure, the Scheduling Priority Indicator (SPI) of a new
HSUPA user is SPINew user.
When the admission of HSUPA scheduling services is implemented, the following
formulas apply:
1.
2.
3.
4.
5.
Here:
ThdL is the low priority HSUPA user PBR threshold
(HsupaLowPriorityUserPBRThd).
ThdE is the equal priority HSUPA user PBR threshold
(HsupaEqualPriorityUserPBRThd).
ThdGE is the high priority HSUPA user PBR threshold
(HsupaHighPriorityUserPBRThd).
HS-DPCCH is the UlHsDpcchRsvdFactor parameter.
thd is the cell UL admission threshold of a specific type of service. The threshold
may be UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR,
UlNonCtrlThdForOther, or UlNonCtrlThdForHo.
The RNC admits the HSUPA scheduling services in either of the following cases:
Formula 1, 2, or 3 is fulfilled.
Formula 4 is fulfilled.
For HSUPA non-scheduling services, the RNC admits the HSUPA non-scheduling
services in either of the following cases:
Formula 1, 2, or 3 is fulfilled.
Formulas 4 and 5 are fulfilled.
If the HSUPA scheduling services or non-scheduling services are rejected according to
the previous conditions, the RNC checks whether the Control RTWP Anti-interfence
algorithm switch (RsvdBit1) is enabled. If it is enabled, the RNC checks whether the
uplink equivalent user load proportion of the cell is lower than 40%. If it is lower than
40%, the RNC accepts the access request. Otherwise, the RNC rejects the access request.
Here:
is the cell UL admission threshold for a specific type of service. The threshold
may be UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR,
UlNonCtrlThdForOther, or UlNonCtrlThdForHo.
If formulas 1 and 2 are fulfilled, the RNC admits DCH services. If they are not fulfilled,
the RNC checks whether the Control RTWP Anti-interfence algorithm switch (RsvdBit1)
is enabled. If it is enabled, the RNC checks whether the uplink equivalent user load
proportion of the cell is lower than 40%. If it is lower than 40%, the RNC accepts the
access request. Otherwise, the RNC rejects the access request.
The power increment estimation for HSDPA RAB PDL is made on the basis of GBR,
Ec/N0, non-orthogonal factor, and so on.
Downlink Radio Admission Decision for DCH RAB
When the admission of the DCH RAB is implemented, the following formulas apply:
1.
2.
3.
Here:
is the maximum available power for HSPA. Its value is associated with the
HSDPA power allocation mode. For details, see the HSDPA Parameter Description.
The RNC admits the DCH RAB in either of the following situations:
Formulas 1 and 2 are fulfilled.
Formulas 1 and 3 are fulfilled.
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set to 0.
Downlink Radio Admission Decision for HSDPA RAB
When the admission of the HSDPA RAB is implemented, the following formulas apply:
1.
2.
3.
4.
5.
Here:
is the maximum available power for HSPA. Its value is associated with the
HSDPA power allocation mode. For details, see the HSDPA Parameter Description.
is the current downlink TCP.
If PS conversational services are carried on HSPA, the services can be treated as streaming services
during admission control.
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set to 0.
If the PBR measurement is deactivated, the decision formulas that involve PBR are regarded as
dissatisfied.
For the first HSDPA service accessing the cell, the decision formulas that involve PBR are regarded
as unsatisfied.
Downlink Radio Admission Decision for HSUPA Control Channels
The power of downlink control channels (E-AGCH/E-RGCH/E-HICH) is determined by
DlHSUPARsvdFactor. Therefore, the power-based admission for these channels is not
needed.
Downlink PowerBased Admission Decision for MBMS
For details, see the MBMS Parameter Description.
Service ENU
1. The RNC obtains the total ENU of all existing users ENUtotal = all_exist_userENUi.
2. The RNC gets the ENU of the new incoming user ENUnew.
3. The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU load, where
ENUmax is the configured maximum ENU (UlTotalEqUserNum or
DlTotalEqUserNum).
4. By comparing the forecasted ENU load with the corresponding threshold, the RNC
decides whether to accept the access request. The threshold may be one of the following
thresholds:
UL/DL threshold of conversational AMR service
UL/DL threshold of conversational non-AMR service
UL/DL threshold of other services
UL/DL access threshold for handover
The admission thresholds for different types of service are different. The following table lists
the parameters used to set admission thresholds for different types of service:
For example, the admission of a new AMR service in the uplink based on algorithm 2 will be
successful if the following condition is fulfilled:
(ENUtotal + ENUnew)/ENUmax UlNonCtrlThdForAMR
Before the admission of the uplink ENU resource, if the uplink OLC algorithm switch
(UL_UU_OLC) is enabled, and the cell is in the OLC state triggered by the RTWP.
-If the Control RTWP Anti-interfence algorithm switch (RsvdBit1) is enabled, the system
checks whether the uplink equivalent user load proportion of the cell is lower than 40%. If it is
lower than 40%, the RNC accepts the access request. Otherwise, the RNC performs an admission
decision on the uplink ENU resource.
-If the Control RTWP Anti-interfence algorithm switch is disabled, the RNC rejects the access
request.
If the cell is in the overload congestion state in the uplink, the RNC rejects any new RAB.
The ENU of MBMS downlink control channels (MICH and MCCH) is reserved. Therefore, the
power-based admission for these channels is not needed.
The ENU of HSUPA downlink control channels (E-AGCH, E-RGCH, and E-HICH) is reserved by
DlHSUPARsvdFactor. Therefore, the power-based admission for these channels is not required.
For the HSUPA service, if the HsupaCeScheduleSwitch is on, the RNC uses the GBR to
calculate the SF; if this switch is off, the RNC uses the MBR to calculate the SF. Then, the
RNC searches Table 7-13 for the number of consumed CEs.
UL 3.4 256 1 2
13.6 64 1 2
8 64 1 2
16 64 1 2
32 32 1.5 3
64 16 3 6
128 8 5 10
144 8 5 10
256 4 10 20
384 4 10 20
DL 3.4 256 1 1
13.6 128 1 1
8 128 1 1
16 128 1 1
32 64 1 1
64 32 2 2
128 16 4 4
144 16 4 4
256 8 8 8
384 8 8 8
UL 8 64 1 2
UL 16 64 1 2
UL 32 32 1 2
UL 64 32 1 2
UL 128 16 2 4
UL 144 16 2 4
UL 256 8 4 8
UL 384 4 8 16
UL 608 4 8 16
UL 1450 2SF4 16 32
UL 2048 2SF2 32 64
UL 2890 2SF2 32 64
UL 5760 2SF2+2SF4 48 96
As listed in Table 7-12 and Table 7-13, for each data rate and service, the number of UL credits is
equal to the number of UL CEs multiplied by 2. This is because the RESOURCE STATUS
INDICATION message over the Iub interface supports only integers. For example, a UL 32 kbit/s PS
service consumes 1.5 CEs. Then, the number of corresponding UL credits consumed is 3, an integer,
which can be carried in the RESOURCE STATUS INDICATION message.
There is no capacity consumption law for HS-DSCH in 3GPP TS 25.433, so certain credits are
reserved for HSDPA RAB, and credit admission for HSDPA is not needed.
The CE capabilities at the levels of local cell, local cell group, and NodeB are reported to the RNC
through the NBAP_AUDIT_RSP message over the Iub interface.
- The CE capability of local cell level indicates the maximum capability in terms of hardware that
can be used in the local cell.
- The CE capability of local cell group level indicates the capability obtained after the license and
hardware are taken into consideration.
- The CE capability of NodeB level indicates the number of CEs allowed to use as specified in the
license.
If the UL CC and DL CC are separate, the credit resourcebased admission is implemented in the
UL and DL, respectively.
If the UL CC and DL CC are not separate, the credit resourcebased admission is implemented
based on the total CC.
Intra-frequency Load Balancing (LDB) is performed to adjust the coverage areas of cells
according to the measured values of cell load. Currently, the intra-frequency LDB algorithm is
applicable only to the downlink.
LDB between intra-frequency cells is implemented by adjusting the transmit power of the
Primary Common Pilot Channel (P-CPICH) according to the downlink load of the associated
cells. When the load of a cell increases, the cell reduces its coverage to lighten its load. When
the load of a cell decreases, the cell extends its coverage so that some traffic is off-loaded
from its neighboring cells to it.
When the intra-frequency LDB algorithm is active, that is, when
INTRA_FREQUENCY_LDB is set to 1, the RNC checks the load of cells periodically and
adjusts the transmit power of the P-CPICH in the associated cells based on the cell load.
Figure 8-25 shows the procedure of intra-frequency LDB.
Yes Yes
Yes Yes
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.
This chapter consists of the following sections:
Basic Congestion Triggering
LDR Procedure
LDR Actions
UL/DL load
LDR trigger
threshold
LDR release
threshold
Time
If the congestion of all resources is triggered in a cell, the congestion is relieved in order of
resource priority for load reshuffling as configured through the SET LDCALGOPARA
command.
Assume that the parameters are set as follows:
The first priority for load reshuffling (LdrFirstPri) is set to IUBLDR.
The second priority for load reshuffling (LdrSecondPri) is set to CREDITLDR.
The third priority for load reshuffling (LdrThirdPri) is set to CODELDR.
Whether the users of gold priority are selected by LDR actions is specified by the
GoldUserLoadControlSwitch parameter.
When the cell is in the basic congestion state, the RNC takes one of the following actions in
each period (specified by the LdrPeriodTimerLen parameter) until the congestion is relieved:
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
Inter-RAT load handover in the PS domain, which involves the following actions:
Inter-RAT Should Be Load Handover in the PS Domain
Inter-RAT Should Not Be Load Handover in the PS Domain
Iu QoS renegotiation
MBMS power reduction
Figure 9-27 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 on Iu interface, and MBMS power reduction.
The sequence of LDR actions can be changed through the ADD CELLLDR command, and
the waiting timer for LDR period is specified by the LdrPeriodTimerLen parameter through
the SET LDCPERIOD command.
Inter-frequency Yes
Successful?
load handover
No
Code Yes
Successful?
reshuffling Wait for the
No
expiration of the timer
BE rate Yes
Successful?
reduction
No
Keep the
Inter-RAT
action Yes
handover Successful? Mark
sequence in CS domain
No "current action
unchanged
Inter-RAT = successful
and take the Yes
handover Successful? action"
current action
in PS domain
firstly No
AMR rate Yes
Successful?
reduction
No
QoS
Yes
renegotiation Successful?
on Iu interface No
MBMS power Yes
Successful?
reduction
No
As shown in Figure 9-27, 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:
Issue Error! Unknown Error! Unknown document property 5
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 9 Load Reshuffling Algorithm
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 rest may be deduced by analogy. For details about LDR actions, see 9.3 "LDR Actions."
Table 9-15 describes the LDR actions intended for different resources.
BE Rate Reduction
Code Reshuffling
Handover in CS
Inter-Frequency
Handover in PS
Load Handover
Renegotiation
MBMS Power
AMR Rate
Inter-RAT
Inter-RAT
Reduction
Reduction
Domain
Domain
Iu QoS
Power UL DCH
HSUPA
DL DCH *
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
BE Rate Reduction
Code Reshuffling
Inter-Frequency
Handover in CS
Handover in PS
Load Handover
Renegotiation
MBMS Power
AMR Rate
Inter-RAT
Inter-RAT
Reduction
Reduction
Domain
Domain
Iu QoS
FACH
(MBMS)
If the downlink powerbased 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 Table 9-15.
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 to the relief of CE resource congestion.
If the basic congestion of uplink power in an HSPA cell occurs, scheduled HSUPA users cannot be
selected by LDR actions.
The parameter CodeCongSelInterFreqHoInd can be set so that the inter-frequency handover can
relieve the basic congestion caused by code resource.
When the inter-frequency load handover is made to reduce the cell load, only an inter-frequency
neighboring cell that supports blind handover can be a target cell of the inter-frequency load
handover.
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 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 Parameter Description.
The algorithm checks whether the load margin of the target cell is higher than both
UlInterFreqHoCellLoadSpaceThd and DlInterFreqHoCellLoadSpaceThd and
whether the load of the target cell is normal.
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 one 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 is selected as the
blind handover target cell.
The load margin refers to the difference between the load of the target cell and the basic congestion
triggering threshold of the target cell, but not the difference between the load of the target cell and the
load of the current cell.
3. The algorithm selects the UEs to be handed over according to the setting of
NbmLdcBHOUeSelSwitch:
If NbmLdcBHOUeSelSwitch is set to NBM_LDC_MATCH_UE_ONLY, the
algorithm performs the following steps:
a. Selects the UEs whose service types are supported by the target cell as candidate
UEs.
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 NbmLdcBHOUeSelSwitch is set to NBM_LDC_MATCH_UE_FIRST, the
algorithm performs the following steps:
a. Selects the UEs whose service types are supported by the target cell as candidate
UEs.
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 whose service types are not supported by the target cells as
candidate UEs.
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 NbmLdcBHOUeSelSwitch is set to NBM_LDC_ALL_UE, the algorithm performs
the following steps:
a. From the current cell, selects the UEs whose rates are not higher than the handover
bandwidth thresholds, and then sorts them by 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 lowest
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 algorithm takes handover actions according
to the status of the UE and the measurement of the signal quality.
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.
The QoS renegotiation algorithm for uncontrollable real-time services is set by the
DRA_IU_QOS_RENEG_SWITCH subparameter of the DraSwitch parameter. The QoS
renegotiation can be performed only when the DRA_IU_QOS_RENEG_SWITCH is on.
The load can be reduced by adjusting the rates of real-time services through QoS
renegotiation. In 3GPP R5, the RNC initiates the RAB renegotiation procedure through the
RAB MODIFY REQUEST message on the Iu interface.
Upon reception of the RAB MODIFY REQUEST message, the Core Network (CN) sends the
RAB ASSIGNMENT REQUEST message to the RNC for RAB parameter reconfiguration.
Based on this function, the RNC can adjust the rate of real-time services to reduce the load of
the current cell.
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.
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.
5. If the RNC cannot find an appropriate service for the QoS renegotiation, the action fails.
The algorithm takes the next action.
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.
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 Parameter Description.
After the UE access is allowed, the power consumed by a single link is adjusted by the single
link power control algorithm. The power varies with all kinds of factors such as the mobility
of the UE and the changes in the environment. In some situations, the total power load of the
cell can be higher than the target load. To ensure the system stability, Overload Control (OLC)
must be performed.
This chapter consists of the following sections:
OLC Triggering
General OLC Procedure
OLC Actions
For details about overload congestion caused by Iub bandwidth and details about user release, see the
Transmission Resource Management Parameter Description.
OLC can be enabled through the UL_UU_OLC and DL_UU_OLC subparameters of the
NBMLdcAlgoSwitch parameter.
Figure 10-29 shows the triggering and release of cell power overload.
UL/DL load
Overload released
Cell in overload
OLC trigger
threshold
OLC release
threshold
time
If the current UL/DL load of an R99 cell is higher than or equal to the UlOlcTrigThd or
DlOlcTrigThd for 1,000 ms, the cell is in the overload state and the related overload
handling action is taken. If the current UL/DL load of the R99 cell is lower than the
UlOlcRelThd or DlOlcRelThd for 1,000 ms, the cell comes back to the normal state.
The overload triggering and release mechanisms for UL HSPA cells are the same as
those for R99 cells.
Whether a DL HSPA cell is overloaded is estimated according to the sum of the non-
HSPA power and the GBP.
In addition to periodic measurement, event-triggered measurement is applicable to OLC.
If OLC_EVENTMEAS is set to 1, the RNC sends the NodeB a request for event E
measurement based on power resource. In the associated request message, the reporting
criterion is specified, including UlOlcTrigHyst / DlOlcTrigHyst, UlOlcTrigThd /
DlOlcTrigThd, and UlOlcRelThd / DlOlcRelThd. 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.
Yes No
Current OLC state = congested?
Performing Yes
Successful?
TF control
No
Keep the
action Switching BE Yes Wait
services to CCH
Successful?
sequence Mark for the
No "current expiration
unchanged
and take action = of the
Adjusting Max Yes
the current Successful? success- OLC
FACH TX power
action first No ful action" period
timer
Releasing Yes
Successful?
some RABs
No
If the number of times that TF control is performed exceeds DlOlcFTFRstrctTimes and the system is
still overloaded, the OLC takes the next action to switch BE services to common channels.
2. If the TF control fails, 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.
Issue Error! Unknown Error! Unknown document property 3
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 10 Overload Control Algorithm
3. If the switching fails, 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.
4. If the adjustment fails, the OLC takes the fourth action to release some RABs.
For details about OLC actions, see 10.3 "OLC Actions."
MAC restricts the TFC selection by calculating the maximum TB number with the
formula:
TFmax(N+1) = TFmax(N) x RateRecoverCoeff
Here:
TFmax(0) is the maximum TB number of the BE service before congestion relief
indication is received.
TFmax(N+1) is the maximum TB number during the period from (T1 +
RateRecoverTimerLen x N) to (T1 + (RateRecoverTimerLen x (N + 1)), where T1
is the time when the MAC receives the congestion relief indication message.
RateRecoverCoeff is specified by the RecoverCoef parameter.
Figure 10-31 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.
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.
The time between point A and point B is specified by the RateRstrctTimerLen parameter.
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.
Issue Error! Unknown Error! Unknown document property 5
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 10 Overload Control Algorithm
For the TF control in the uplink, the OLC algorithm operates as follows:
1. Based on the integrated priority, the algorithm sorts the DCH RABs in descending order.
2. The algorithm selects the RABs with the lowest integrated priorities and with the rates
higher than UlDcccRateThd. The number of selected RABs is specified by the
UlOlcFTFRstrctRabNum parameter.
3. The RNC sends the TRANSPORT FORMAT COMBINATION CONTROL message to
the UE that accesses the specified service. This message contains the following IEs:
Transport Format Combination Set Identity: defines the available TFC that the UE
can select, that is, the restricted TFC sub-set. It is always the two TFCs corresponding
to the lowest data rate.
TFC Control Duration: defines the period in multiples of 10 ms frames for which the
restricted TFC sub-set is to be applied. It is set to a random value from the range of
10 ms to 5120 ms, so as to avoid data rate upsizing at the same time.
After the TFC control duration is due, the UE can apply any TFC of TFCS before the
TF control.
4. Each time, the RNC selects a certain number of RABs, which is specified by
UlOlcFTFRstrctRabNum, for TF control. The UE of each selected RAB will receive
the TRANSPORT FORMAT COMBINATION CONTROL message. The number of
times that TF control is performed is specified by UlOlcFTFRstrctTimes.
5. If the RNC cannot find an appropriate service, the OLC performs the next action.
The previous power adjustment is applicable to only the FACH carrying common services rather
than MBMS services.
During an OLC period, the OLC can adjust the power of only one FACH. If multiple FACHs meet
the conditions, the OLC adjusts them one by one in different OLC periods.
For the release of some RABs in the uplink, if the Control RTWP Anti-interfence algorithm switch
(RsvdBit1) 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.
11.1 Introduction
Along with the wide use of the WCDMA system, more and more hot areas use multi-carrier
power amplifiers. When traffic cannot be evenly distributed to different carriers, the requests
for DL power resources are unbalanced. In this case, dynamic power sharing among carriers
can be used to balance the requests between the carriers and increase the throughput.
In dynamic power sharing among carriers, a carrier that carries the HSPA service can
dynamically use the idle power resource of another carrier, thus improving the power usage
and the cell HSPA service rate.
RAN11.0 supports power sharing between two carriers, namely an R99 carrier and an HSDPA
carrier. The following section takes an R99 cell and an HSDPA cell as an example. In this case,
the HSDPA cell can determine the available power according to the power usage of the R99
cell.
Based on simulation results, the capacity of the HSDPA cell is increased by 5% to 6% in the
case of power sharing between two carriers.
Rmax-share denotes the maximum ratio of the idle power that can be shared to the transmit
power of the source cell. It is specified by the MAXSHRTO parameter.
Rmax-share denotes the maximum ratio of the idle power reserved for the source cell to the
transmit power of the source cell. It is specified by the SHMGN parameter.
The target cell assigns power to its HSDPA users based on the sum of the maximum power
configured for the target cell and the maximum power that can be shared by the source cell
with the target cell.
12.1 Description
Table 12-16 Load control parameter description
Parameter ID Description
BGNSwitch When the parameter is 'OFF', the auto-adaptive background noise update algorithm
is switched off. Otherwise, the algorithm is switched on.
BackgroundNoise If [Auto-Adaptive Background Noise Update Switch] is set to OFF, it is used to set
background noise of the cell. If [Auto-Adaptive Background Noise Update Switch]
is set to ON, new background noise is restricted by this parameter and
[PARA]BgnAbnormalThd[/PARA]. For detailed information of this parameter,
refer to the 3GPP TS 25.133.
BgnAbnormalThd This parameter is applied when [PARA]BGNSwitch[/PARA] is set to ON. (1) If
the difference of measured background noise without filtered and the current
background noise is larger than the RTWP threshold, the background noise will not
be updated. (2) If the difference of new background noise and the configured value
is larger than the RTWP threshold, the background noise will not be updated.
BGNAdjustTimeLen Only when the measured background noise's duration reaches this parameter, the
output of the auto-adaptive background noise 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.
BgnEndTime This parameter, along with the [Algorithm start time], is used to limit the validation
time of the background noise automatic updata algorithm.
BgnStartTime This parameter, along with the [Algorithm stop time], is used to limit the validation
time of the background noise automatic updata algorithm.
BgnUpdateThd The difference of RTWP that trigger the update of background noise. If the
difference is larger than the threshold, the background will be updated.
NBMCacAlgoSwitch The above values of the algorithms represent the following information:
CRD_ADCTRL: Control NodeB Credit admission control algorithm
Only when IUB_CONG_CAC_SWITCH which is set by the SET
CACALGOSWITCH command and this switch are on,the NodeB Credit admission
control algorithm is valid.
Issue Error! Unknown Error! Unknown document property 1
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
HSDPA_UU_ADCTRL: Control HSDPA UU Load admission control algorithm
HSDPA_GBP_MEAS: Control HSDPA HS-DSCH Required Power measurement
HSDPA_PBR_MEAS: Control HSDPA HS-DSCH Provided Bit Rate
measurement
HSUPA_UU_ADCTRL: Control HSUPA UU Load admission control algorithm
MBMS_UU_ADCTRL: Control MBMS UU Load admission control algorithm
DOFFC: Default DPCH offset configuration algorithm
HSUPA_PBR_MEAS: Control HSUPA Provided Bit Rate measurement
HSUPA_EDCH_RSEPS_MEAS: Control HSUPA Provided Received Scheduled
EDCH Power Share measurement.
EMC_UU_ADCTRL: Control power admission for emergency user
FACH_UU_ADCTRL: Control admission for user over FACH channels
If CRD_ADCTRL,HSDPA_UU_ADCTRL,HSDPA_GBP_MEAS,
HSDPA_PBR_MEAS, HSUPA_UU_ADCTRL, MBMS_UU_ADCTRL, DOFFC,
HSUPA_PBR_MEAS ,HSUPA_EDCH_RSEPS_MEAS, EMC_UU_ADCTRL
and FACH_UU_ADCTRL are selected, the corresponding algorithms will be
enabled; otherwise, disabled.
NBMLdcAlgoSwitch The algorithms with the above values represent are as follow:
INTRA_FREQUENCY_LDB: Intra-frequency load balance algorithm. It is also
named cell breathing algorithm.Based on the cell load, this algorithm changes the
pilot power of the cell to control the load between intra-frequency cells.
PUC: Potential user control algorithm. Based on the cell load, this algorithm
changes the selection/reselection parameters of a cell to lead the UE to a lighter
loaded cell.
UL_UU_OLC: UL UU overload congestion control algorithm. When the cell is
overloaded in UL, this algorithm reduces the cell load in UL by quick TF
restriction or UE release.
DL_UU_OLC: DL UU overload congestion control algorithm. When the cell is
overloaded in DL, this algorithm reduces the cell load in DL by quick TF
restriction or UE release.
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 inter-RAT handover, and PS inter-RAT handover.
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 inter-RAT handover, and PS inter-RAT handover.
OLC_EVENTMEAS: Control OLC event measurement. This algorithm starts the
OLC event measurement.
CELL_CODE_LDR: 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.
CELL_CREDIT_LDR:Credit reshuffling algorithm. When the cell credit is heavily
loaded, this algorithm reduces the credit load of the cell by using BE service rate
reduction, uncontrollable real-time service QoS renegotiation, CS inter-RAT
handover, and PS inter-RAT handover.
If INTRA_FREQUENCY_LDB, PUC, ULOLC, DLOLC, ULLDR, UDLLDR,
OLC_EVENTMEAS, CELL_CODE_LDR and CELL_CREDIT_LDR are
selected, the corresponding algorithms will be enabled; otherwise, disabled.
CellLdrSfResThd 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
Issue Error! Unknown Error! Unknown document property 2
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
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.
CellOverrunThd If the cell downlink load exceeds this threshold, the algorithm will decrease the
pilot transmit power of the cell so as to increase the whole system's capacity. This
parameter is based on network planning. When the cell breathing algorithm is
activated, if the value is too small, the physical coverage of the cell is limited so as
to avoid cell capacity waste. If the value is too great, the physical coverage is
expanded and interference over other cells is increased.
CellUnderrunThd If the cell downlink load is lower than this threshold, the algorithm will increase
the pilot transmit power of the cell so as to share load of other cells. This parameter
is based on network planning. When the cell breathing algorithm is activated, if the
value is too small, the physical coverage of the cell is limited so as to avoid cell
capacity waste. If the value is too great, the physical coverage is expanded and
interference over other cells is increased.
HsdpaCMPermissionInd CM permission indicator on HSDPA. If this parameter value is TRUE, CM is
permitted on HSDPA and HSDPA can be activated with CM activated. If this
parameter value is FALSE, H2D is needed before CM activated when HSDPA
exists and HSDPA cannot exist when CM is activated.
This switch is compatible with the old HSDPA terminals that might exist in the
network because these terminals do not support the activated compressed mode on
the HSDPA service.
HsupaCMPermissionInd CM permission indicator on HSUPA.
If this parameter value is Permit, CM is permitted on HSUPA and HSUPA can be
activated with CM activation. If this parameter value is Limited, H2D is needed
before CM activation when HSUPA exists and HSUPA cannot exist when CM is
activated; when the indicator is BasedonUECap, you can infer that the RNC
determines whether to configure and activate the compressed mode on the E-DCH
and whether to establish an E-DCH in the compressed mode.
This switch is compatible with the HSUPA terminals that might exist in the
network because these terminals do not support the activated compressed mode in
the E-DCH channel.
CodeBalancingDrdSwit This parameter specifies whether the code balancing DRD algorithm will be
ch applied.
- ON: The code balancing DRD algorithm will be applied.
- OFF: The code balancing DRD algorithm will not be applied.
CodeCongSelInterFreq This switch is valid only when the inter-frequency handover switch is enabled.
HoInd TRUE means that inter-frequency handover is selected in code resource
congestion. FALSE means that inter-frequency handover is not selected in code
resource congestion. This parameter should be set based on network resource
usage. In the case of multi-frequency coverage, if code resources present a
bottleneck, such as indoor environment, the parameter is recommended to be set to
TRUE. When the value is TRUE, users can be selected for inter-frequency
handover during code resource congestion, which can easily release code
congestion and use multi-frequency resources. However, the risk of inter-frequency
blink handover increases.
CodeBalancingDrdCode This parameter specifies one of the triggering conditions of code balancing DRD.
Issue Error! Unknown Error! Unknown document property 3
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
RateThd (The other condition is the minimum spreading factor.) This condition refers to that
the code occupancy in the best cell is not lower than the value of this parameter.
DeltaCodeOccupiedRate This parameter specifies the threshold of code occupancy offset between the
current cell and the target cell when code balancing DRD is applied. Only when the
cell code occupancy offset reaches this threshold can a neighboring cell be selected
to be a candidate cell for DRD.
MinForDlBasicMeas DL basic common measurement report cycle. For detailed information of this
parameter, refer to 3GPP TS 25.433.
DlBeTraffInitBitrate DL BE traffic Initial bit rate. When DCCC function is enabled, the downlink initial
bit rate will be set to this value if the downlink max bit rate is higher than the initial
bit rate.
DlCCHLoadRsrvCoeff Different admission policies are used for dedicated channel and common channel
users. For common channel users, resources instead of separate power admission
decision are reserved. For dedicated channel users, according to the current load
factor and the characteristics of the new call, the CAC algorithm predicts the new
TX power with the assumption of admitting the new call, then plus with the
premeditated common channel DL load factor to get the predicted DL load factor.
Then, compare it with the DL admission threshold. If the value is not higher than
the threshold, the call is admitted; otherwise, rejected.
DlCSInterRatShouldBe Number of users selected in a DL LDR CS domain inter-RAT SHOULDBE load
HOUeNum handover. The target subscribers of this parameter are the CS domain subscribers.
Because the CS domain subscribers are session subscribers in general and they
have little impact on load, you can set this parameter to a comparatively high
value.
DlCSInterRatShouldNot Number of users selected in a DL LDR CS domain inter-RAT SHOULDNOTBE
HOUeNum load handover. The target subscribers of this parameter are the CS domain
subscribers. Because the CS domain subscribers are session subscribers in general
and they have little impact on load, you can set this parameter to a comparatively
high value.
DlHOThd The percentage of the handover service admission threshold to the 100% downlink
load. It is applicable to algorithm 1 and algorithm 2. The parameter is used for
controlling the handover admission. That is, when a service is handing over to a
cell, the RNC evalutates the measurement value of the downlink load after the
service is accessed. If the DL load of a cell is higher than this threshold after the
access, this service will be rejected. If the DL load of a cell will not be higher than
this threshold, this service will be admitted.
The DL load factor thresholds include parameters of [DL threshold of Conv
non_AMR service], [DL handover access threshold] and [DL threshold of other
services]. The four parameters can be used to limit the proportion between the non-
handover service, handover user and other services in a specific cell, and to
guarantee the access priority of the handover service. This parameter is related to
the cell radius and cell maximum TX power. If the value is too high, the system
load after admission may be over large, which impacts system stability and leads to
system congestion. If the value is too low, the possibility of user rejects may
increase, resulting in waste in idle resources.
DlHoCeCodeResvSf Some cell resources can be reserved for handover UEs to guarantee handover
success rate and improve access priority of handover services. This parameter
Parameter ID Description
defines the quantity of downlink code and CE resources reserved for handover.
DlInterFreqHoCellLoad The inter-frequency neighboring cell could be selected as the destination of load
SpaceThd 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.
DlInterFreqHoBWThd 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.
DlHSUPARsvdFactor Reserved DL power factor for HSUPA user.
DlLdrCreditSfResThd Reserved SF threshold in downlink credit LDR. The downlink credit LDR could be
triggered only when the SF factor corresponding to the downlink reserved credit is
higher than the uplink or downlink credit SF reserved threshold. The lower the
parameter value is, the easier the credit enters the congestion status, the easier the
LDR action is triggered, and the easier the user experience is affected. A lower
code resource LDR trigger threshold, however, causes a higher admission success
rate because the resource is reserved. The parameter should be set based on the
operator's requirement.
DlLdrRelThd If the ratio of DL load of the cell to the downlink capacity is lower than this
threshold, the DL load reshuffling function of the cell is stopped. 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 ping-pong effect of
the preliminary congestion state may occur. 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. The carrier shall make a trade-off between these
factors.
DlLdrTrigThd If the ratio of DL load of the cell to the downlink capacity is not lower than this
threshold, the 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 ping-pong effect of
the preliminary congestion state may occur. 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. The carrier shall make a trade-off between these
factors.
DlLdrPsRTQosRenegRa Number of RABs selected in a DL LDR uncontrolled real-time traffic QoS
bNum renegotiation. The target subscribers of this parameter are the PS domain real-time
subscribers. The setting of this parameter is analogous to the setting of BE service
Issue Error! Unknown Error! Unknown document property 5
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
rate reduction subscriber number. Because the number of subscribers performing
QoS renegotiation may be smaller than the value of this parameter, for example,
the candidate subscribers selected for downlink LDR do not meet the QoS
renegotiation conditions, you must leave some margin when setting this parameter
to ensure the success of load reshuffling.
DlLdrAMRRateReducti The mechanism of the LDR is that an action is performed in each [LDR period]
onRabNum and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs selected in executing
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.
DlLdrBERateReduction Number of RABs selected in a DL LDR BE traffic rate reduction. In the actual
RabNum 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.
LdbDRDLoadRemainT This parameter specifies the downlink load threshold to trigger load balancing
hdDCH DRD for services carried on DCH. The load balancing DRD will probably be
triggered only when the downlink cell remanent non H power or remanent R99
equivalent user number is less than this threshold.
LdbDRDLoadRemainT This parameter specifies the downlink load threshold to trigger load balancing
hdHSDPA DRD for services carried on HS-DSCH. The load balancing DRD will probably be
triggered only when the downlink cell remanent HSDPA guarantee power or
remanent HSDPA user number is less than this threshold.
DlOlcFTFRstrctRabNu DL fast TF restriction refers to a situation where, when the cell is overloaded and
m congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell downlink load.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs selected in executing
downlink OLC fast restriction.
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. In the
actual system, UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum can be set
on the basis of the actual circumstances. If the high-rate subscribers occupy a high
proportion, set UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum to
comparatively low values. If the high-rate subscribers occupy a low proportion, set
UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum to comparatively high
values. 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.
DlOlcFTFRstrctTimes DL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
Issue Error! Unknown Error! Unknown document property 6
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
the cell downlink load.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of downlink OLC fast TF restriction
performed in entering/exiting the OLC status.
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. The lower the parameters are, the more likely the users
are released, resulting in negative effect on the system performance. If the
parameters are excessively high, the overload status is released slowly.
DlOlcRelThd If the ratio of DL load of the cell to the downlink capacity is lower than this
threshold, the DL overload and congestion control function of the cell is stopped.
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.
DlOlcTraffRelRabNum User release is an extreme method in reducing the cell load and recovering the
system when the cell is overloaded and congested.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs released in executing
downlink OLC service release.
For the users of a single service, the releasing of RABs means the complete
releasing of the users. The releasing of RABs causes call drops, so
UlOlcFTFRstrctTimes or DlOlcFTFRstrctTimes should be set to a low value.
Higher values of the parameter get the cell load to decrease more obviously, but the
QoS will be affected.
DlOlcTrigThd If the ratio of DL load of the cell to the downlink capacity is not lower than this
threshold, the 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.
DlPSInterRatShouldBe Number of users selected in a DL LDR PS domain inter-RAT SHOULDBE load
HOUeNum handover. The target subscribers of this parameter are the PS domain subscribers.
In the actual system, this parameter can be set on the basis of the actual
Parameter ID Description
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.
DlPSInterRatShouldNot Number of users selected in a DL LDR PS domain inter-RAT SHOULDNOTBE
HOUeNum load handover. The target subscribers of this parameter are the PS domain
subscribers. 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.
RateRecoverTimerLen DL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell downlink load. This parameter defines the downlink data rate recover timer
length in fast TF restriction. RateRstrctTimerLen and RateRecoverTimerLen 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. The higher
RateRecoverTimerLen is, the more slowly the BE service rate recovers, while the
lower probability that the overload is triggered again in a short period. The lower
RateRecoverTimerLen is, the more quickly the BE service rate is recovered, but
more overloads occur.
RateRstrctCoef DL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell downlink load. This parameter defines the downlink data rate restrict
coefficient in fast TF restrict The smaller this parameter is, the larger the TF
restrict effect. The lower the parameter is, the more severe the rate is restricted. An
excessive low parameter value, however, may affect the BE transmission delay. A
high parameter value means loose restriction, which may be ineffective in
alleviating the overload.
RateRstrctTimerLen DL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell downlink load. This parameter defines the time length of the downlink
OLC fast TF restriction. RateRstrctTimerLen and RateRecoverTimerLen 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. The higher
RateRstrctTimerLen is, the more slowly the BE service rate decreases. The lower
RateRstrctTimerLen is, the harder it is to receive the overload release instruction.
Recovercoef DL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the downlink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
Parameter ID Description
the cell downlink load. This parameter defines the downlink OLC fast TF rate
recovery coefficient. The greater this parameter is, the larger the TF restrict effect.
DlConvAMRThd The percentage of the conversational AMR service threshold to the 100% downlink
load. It is applicable to algorithm 1 and algorithm 2.
DlConvNonAMRThd The percentage of the conversational non-AMR service threshold to the 100%
downlink load. It is applicable to algorithm 1 and algorithm 2. The parameter is
used for controlling the non-AMR service admission. That is, when a non-AMR
service is accessing, the RNC evalutates the measurement value of the downlink
load after the service is accessed. If the DL load of a cell is higher than this
threshold after the access of a non-AMR speech service, this service will be
rejected. If the DL load of a cell will not be higher than this threshold, this service
will be admitted.
DlOtherThd The percentage of other service thresholds to the 100% downlink load. The
services refer to other admissions except the conversational AMR service,
conversational non-AMR service, and handover scenarios. It is applicable to
algorithm 1 and algorithm 2. The parameter is used for controlling other service
admissions. That is, when a service is accessing, the RNC evalutates the
measurement value of the downlink load after the service is accessed. If the DL
load of a cell is higher than this threshold after the access of a service, this service
will be rejected. If the DL load of a cell will not be higher than this threshold, this
service will be admitted.
The DL load factor thresholds include parameters of [DL threshold of Conv
non_AMR service], [DL handover access threshold] and [DL threshold of other
services]. The four parameters can be used to limit the proportion between the
conversational service, handover user and other services in a specific cell, and to
guarantee the access priority of other services. If the value is too high the system
load after admission may be over large, which impacts system stability and leads to
system congestion. If the value is too low, the possibility of user rejects may
increase, resulting in waste in idle resources and the failure to achieving network
planning target.
DlTotalEqUserNum When the algorithm 2 is used, this parameter defines the total equivalent user
number corresponding to the 100% downlink load. he parameter should be related
to the admission threshold and actual condition of the network. If the value is too
high, the system load after admission may be over large, which impacts system
stability and leads to system congestion. If the value is too low, the possibility of
user rejects may increase, resulting in waste in idle resources.
DlCellTotalThd Admission threshold of the total cell downlink power. If the value is too high, too
many users will be admitted. However, the throughput of a single user is easy to be
limited. If the value is too low, cell capacity will be wasted.
DlDcccRateThd 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.
NBMDlCacAlgoSelSwit The algorithms with the above values represent are as follow:
ch ALGORITHM_OFF: Disable downlink call admission control algorithm.
ALGORITHM_FIRST: The load factor prediction algorithm will be used in
downlink CAC.
ALGORITHM_SECOND: The equivalent user number algorithm will be used in
Issue Error! Unknown Error! Unknown document property 9
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
downlink CAC.
ALGORITHM_THIRD: The loose call admission control algorithm will be used in
downlink CAC.
DRDEcN0Threshhold This parameter is used as the DRD Ec/No threshold of whether to perform the
blind handover.
This parameter is used as the DRD Ec/No threshold of whether to perform the
blind handover. When choosing a DRD candidate cell, if the Ec/No value of the
current cell is greater than the threshold of inter-RAT/inter-frequency neighboring
cell, the DRD is permitted.
HsupaEqualPriorityUser Threshold of all the HSUPA user PBR whose schedule priority is the same as that
PBRThd of users to be admitted. If this value is too high, the possibility of rejecting HSUPA
schedule services increases, which impacts access success rate. If the value is too
low, too many HSUPA schedule users may be admitted, which impacts the
admitted users and results in overload and system congestion.
BGNEqUserNumThd When the number of uplink equivalent users is not larger than this parameter, the
RTWP could be regarded as background noise. 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.
LdrFirstPri 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.
LdrFourthPri 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
fourth 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.
GoldUserLoadControlS Indicates whether gold users involve in the switch of congestion control.
witch 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.
HsupaHighPriorityUser Threshold of all the HSUPA user PBR whose schedule priority is higher than that
PBRThd of users to be admitted. If this value is too high, the possibility of rejecting HSUPA
schedule services increases, which impacts access success rate. If the value is too
low, too many HSUPA schedule users may be admitted, which impacts the
admitted users and results in overload and system congestionRecommended.
HsdpaBePBRThd Average throughput admission threshold of the HSDPA best effort traffic. If the
sum of PBR of all the accessed HSDPA BE users is lower than the average
throughput admission threshold of the HSDPA BE service multiplied by the sum of
Parameter ID Description
GBR of all the accessed HSDPA BE users, it indicates that the QoS of the accessed
users cannot be satisfied and new HSDPA BE services are not allowed. Otherwise,
the QoS can be satisfied and new HSDPA BE services are allowed. If the value is
too high, admission requirement of the HSDPA BE service is strict, which
improves the service quality of the HSDPA BE service but also may lead to
HSDPA capacity waste. If the value is too low, admission requirement of the
HSDPA BE service is loose, which allows more BE services but QoS of the
HSDPA BE service cannot be guaranteed.
HsdpaStrmPBRThd Average throughput admission threshold of the HSDPA streaming service. If the
sum of PBR of all the accessed streaming users is lower than the average
throughput admission threshold of the HSDPA streaming service multiplied by the
sum of GBR of all the accessed streaming users, it indicates that the QoS of the
accessed users cannot be satisfied and new HSDPA streaming services are not
allowed. Otherwise, the QoS can be satisfied and new HSDPA streaming services
are allowed. If the value is too high, admission requirement of the HSDPA
streaming service is strict, which improves the service quality of the HSDPA
streaming service but also may lead to HSDPA capacity waste. If the value is too
low, admission requirement of the HSDPA streaming service is loose, which
allows more HSDPA streaming services but QoS of the HSDPA streaming service
cannot be guaranteed.
CarrierTypePriorInd Decide which carrier is prior when ARP and TrafficClass are both identical.
HsupaInitialRate HSUPA BE traffic Initial bit rate. When DCCC algorithm switch and HSUPA
DCCC algorithm switch are enabled, the uplink initial bit rate will be set to this
value if the uplink max bit rate is higher than the initial bit rate.
PriorityReference Reference used to determine which priority is arranged first in the priority
sequence.
If the ARP is preferably used, the priority sequence is gold > silver > copper. If the
ARPs are all the same, the TrafficClass is used and the priority sequence is
conversational > streaming > interactive > background.
If the TrafficClass is preferably used, the priority sequence is conversational >
streaming > interactive > background. If the TrafficClass factors are all the same,
the ARP factor is used and the priority sequence is gold > silver > copper.
LdrCodeUsedSpaceThd 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 inter-frequency blind
handover occurs, and the easier it is to guarantee the stability of the target cell.
LdrCodePriUseInd 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. It is
good for the code resource dynamic sharing, which is a function used for the
HSDPA service.
LdrPeriodTimerLen 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
Issue Error! Unknown Error! Unknown document property 11
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
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.
The LDR algorithm aims to slowly reduce the cell load and control the load below
the admission threshold, each LDR action takes a period (for example the inter-
RAT load handover needs a delay of about 5 s if the compressed mode is needed),
and there is a delay for the LDM module responds to the load decreasing (the delay
is about 3 s when the L3 filter coefficient is set to 6), so the parameter value should
be higher than 8s.
LdbDRDchoice This parameter specifies which choice the load balancing DRD algorithm will be
applied.
- Power: Power(Downlink none-HSDPA power is used for services carried on
DCH, and downlink HSDPA guarantee power is used for services carried on HS-
DSCH)will be applied to the load balancing DRD algorithm.
- UserNumber: User number(Downlink R99 equivalent user number is used for
services carried on DCH, and downlink HSDPA user number is used for services
carried on HS-DSCH)will be applied to the the load balancing DRD algorithm.
LdbDRDOffsetDCH This parameter specifies the threshold of remanent load offset between the current
cell and the target cell when load balancing DRD is applied for DCH users. Only
when the remanent load offset reaches this threshold can a neighboring cell be
selected as a candidate DRD cell for DCH users.(If Load balance DRD choice is
Power, additional condition should also be statisfied, that is total power remain
difference between the current cell and target cell should be less than Load Balance
DRD Total Power Protect Threshold; if Load balance DRD choice is UserNumber,
additional condition is not needed.)
LdbDRDOffsetHSDPA This parameter specifies the threshold of remanent load offset between the current
cell and the target cell when load balancing DRD is applied for HSDPA users.
Only when the remanent load offset reaches this threshold can a neighboring cell
be selected as a candidate DRD cell for HSDPA users.(If Load balance DRD
choice is Power, additional condition should also be statisfied, that is total power
remain difference between the current cell and target cell should be less than Load
Balance DRD Total Power Protect Threshold; if Load balance DRD choice is
UserNumber, additional condition is not needed.)
LdbDRDSwitchDCH This parameter specifies whether the load balancing DRD algorithm will be
applied for services carried on DCH.
- ON: The load balancing DRD algorithm will be applied.(If cell-level DRD
parameters are configured, the status of cell level Load balance DRD switch for
DCH should also be considered.)
- OFF: The load balancing DRD algorithm will not be applied.
LdbDRDSwitchHSDPA This parameter specifies whether the load balancing DRD algorithm will be
applied for services carried on HS-DSCH.
- ON: The load balancing DRD algorithm will be applied.(If cell-level DRD
parameters are configured, the status of cell level Load balance DRD switch for
HSDPA should also be considered.)
- OFF: The load balancing DRD algorithm will not be applied.
LdbDRDTotalPwrProTh This parameter specifies the threshold of the downlink remanent total power
d difference between the current cell and the target cell when load balancing DRD is
applied and the load balancing DRD choice is Power. Only when the downlink
Issue Error! Unknown Error! Unknown document property 12
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
remanent total power difference is less than this threshold can a neighboring cell be
selected as a candidate DRD cell.
SpucHyst Hysteresis used to determine the cell load level. It is denoted by the ratio of NodeB
TX power to the maximum TX power. It is used to avoid the unnecessary ping-
pong effect of a cell between two load levels due to tiny load change. For detailed
information of this parameter, refer to 3GPP TS 25.304.
SpucHeavy It is used to decide whether the cell load level is "Heavy" or not. It is denoted by
the ratio of NodeB TX power to the maximum TX power.
If the load of a cell is equal to or higher than this threshold, the load level of this
cell is heavy.
If the load level of a cell is heavy, the PUC algorithm will configure
selection/reselection parameters for this cell to lead the UE camping on this cell to
reselect another inter-frequency neighboring cell with light load.
SpucLight It is used to decide whether the cell load level is "Light" or not. It is denoted by the
ratio of NodeB TX power to the maximum TX power.
If the load of a cell is equal to or lower than this threshold, the load level of this
cell is light.
If the load level of a cell is light, the PUC algorithm will configure
selection/reselection parameters for this cell to lead the UE to reselect this cell
rather than the previous inter-frequency neighboring cell with heavy load.
HsupaLowPriorityUserP Threshold of all the HSUPA user PBR whose schedule priority is lower than that
BRThd of users to be admitted. If this value is too high, the possibility of rejecting HSUPA
schedule services increases, which impacts access success rate. If the value is too
low, too many HSUPA schedule users may be admitted, which impacts the
admitted users and results in overload and system congestion.
MaxQueueTimeLen Maximum queue time of users. When a user initiates a call, it joins the queue due
to cell resource insufficiency. This parameter defines the maximum length of time
required for queuing of a user. If cell resources are still insufficient after expiration,
access fails.
MaxUserNumCodeAdj 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.
MaxHsdpaUserNum Maximum number of users supported by the HSDPA channel. The user in this
parameter refers to the user with services on the HSDPA channel, regardless of the
number of RABs carried on the HSDPA channel. Maximum HSDPA user number
cannot exceed the HSDPA capability of the NodeB product, In practice, the value
can be set based on the cell type and the richness of the available HSDPA power
and code resources. If the value is too low, the cell HSDPA capacity may be
reduces, leading to waste in HSDPA resources. If the value is too high, HSDPA
services may be congested.
MaxHsupaUserNum Maximum number of users supported by the HSUPA channel.The user in this
parameter refers to the user with services on the HSUPA channel, regardless of the
number of RABs carried on the HSUPA channel. Maximum HSUPA user number
cannot exceed the HSUPA capacity.
Parameter ID Description
MbmsDecPowerRabThd When the priority of the RAB of MBMS services exceeds this threshold,
reconfigure the MBMS power to the minimum power. The lower the parameter
value is, the bigger the scope for selecting the MBMS services is, the more cell
load is decreased, the more effect there is on the MBMS service. At the same time,
the cell overload is significantly decreased while the impact on the MBMS services
becomes bigger. The higher the parameter value is, the smaller the scope for
selecting the MBMS services is, the less cell load is decreased, the more effect
there is on the MBMS services, and the quality of services with high priority,
however, can be guaranteed. The MBMS service at each rate is set on the basis of
two power levels. The power set for an MBMS service is determined according to
cell load during the service access. In addition, the FACH power of the MBMS
service must be decreased as required in the duration of cell congestion. Some
services with high priority, for example the disaster pre-alert, however, do not need
the coverage shrink caused by cell load. In such a case, you can adjust the service
priority threshold to protect the services with high priority against the impact of the
service access failure and the load control algorithm.
MbmsPreemptAlgoSwit Indicating whether MBMS is supported.
ch
MbmsOlcRelNum MBMS service release is an extreme method in reducing the cell load and
recovering the system when the cell is overloaded and congested.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of MBMS services released in
executing downlink OLC service release.
MinPCPICHPower Minimum TX power of the PCPICH in a cell. This parameter should be set based
on the actual system environment such as cell coverage (radius) and geographical
environment. If MinPCPICHPower is excessively small, the cell coverage is
affected. Ensure that MinPCPICHPower is set under the condition of a proper
proportion of soft handover area, or under the condition that no coverage hole
exists.
CodeBalancingDrdMinS This parameter specifies one of the triggering conditions of code balancing DRD.
FThd (The other condition is the code occupancy.) This condition refers to that the
minimum spreading factor of the best cell is not smaller than the value of this
parameter.
NodeBLdcAlgoSwitch IUB_LDR (Iub congestion control algorithm): 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.
NODEB_CREDIT_LDR (NodeB level credit congestion control algorithm): When
the NodeB level credit load is heavy, users are assembled in priority order among
all the NodeBs and some users are selected for LDR action in order to reduce the
NodeB level credit load.
LCG_CREDIT_LDR (Cell group level credit congestion control algorithm): When
the cell group level credit load is heavy, users are assembled in priority order
among all the NodeBs and some users are selected for LDR action in order to
reduce the cell group level credit load. IUB_OLC (Iub Overload congestion control
algorithm): When the NodeB Iub load is Overload, users are assembled in priority
order among all the NodeBs and some users are selected for Olc action in order to
reduce the NodeB Iub load.
Issue Error! Unknown Error! Unknown document property 14
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
To enable some of the algorithms above, select them. Otherwise, they are disabled.
NodeBHsdpaMaxUserN Maximum number of HSDPA users of the NodeB. If the HSDPA user access is
um rejected by the NodeB, you can infer that the HSDPA licenses are insufficient.
New HSDPA licenses are required.
NodeBHsupaMaxUserN Maximum number of HSUPA users of the NodeB. If the HSUPA user access is
um rejected by the NodeB, you can infer that the HSUPA licenses are insufficient.
New HSUPA licenses are required.
OlcPeriodTimerLen 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. For
example, when the layer 3 filter coefficient is 6, the hysteresis for which the load
measurement responds to the step-function signals is about 2.8s, namely that the
system can trace the load control effect about 3 s later after each load control. In
this case, the OLC period timer length cannot be smaller than 3s.
OlcPeriodTimerLen along with ULOLCFTFRstrctUserNum,
DLOLCFTFRstrctUserNum, ULOLCFTFRSTRCTTimes,
DLOLCFTFRSTRCTTimes, ULOLCTraffRelUserNum, and
DLOLCTraffRelUserNum determine the time it takes to release the
uplink/downlink overload. 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.
PCPICHPowerPace Pilot power adjustment step increased or decreased in each increase of the cell
breathing algorithm or decrease of cell pilot. If the value is too great, the cell pilot
may change fiercely, which is easy to lead to user call drops. If the value is too
small, the cell pilot may change smoothly. However, the response speed of the cell
breathing algorithm is decreased, impacting the algorithm performance. For
detailed information of this parameter, refer to 3GPP TS 25.433.
PreemptAlgoSwitch Indicating whether preemption is supported.
PreemptRefArpSwitch Indicating whether ARP-based preemption between TCs is supported. This switch
only has impact on the TC-based priorities. When the priority is based on the TC
and the switch is enabled, for the following two situations, the preempting service
should have a higher priority and ARP priority than the preempted service does:
1.The preempting service is the streaming service and the preempted service is the
interactive or background service. 2. The preempting service is the interactive
service and the preempted service is the background service.
EmcPreeRefVulnSwitch When the switch is enabled, users of emergency call can preempt all the users of
non emergency call. When the switch is disabled, users of emergency call can only
preempt users of non emergency call with the preempted attributes.
OffQoffset1Light Offset of Qoffset1 when neighboring cell load is lighter than that of the center cell
(Note: Qoffset1 is used as a priority to decide which cell will be selected in cell
selection or reselection) For detailed information of this parameter, refer to 3GPP
TS 25.304.
OffQoffset1Heavy Offset of Qoffset1 when neighboring cell load is heavier than that of the center cell
(Note: Qoffset1 is used as a priority to decide which cell will be selected in cell
selection or reselection) For detailed information of this parameter, refer to 3GPP
Parameter ID Description
TS 25.304.
OffQoffset2Light Offset of Qoffset2 when neighboring cell load is lighter than that of the center cell
(Note: Qoffset2 is used as a priority to decide which cell will be selected in cell
selection or reselection) For detailed information of this parameter, refer to 3GPP
TS 25.304.
OffQoffset2Heavy Offset of Qoffset2 when neighboring cell load is heavier than that of the center cell
(Note: Qoffset2 is used as a priority to decide which cell will be selected in cell
selection or reselection) For detailed information of this parameter, refer to 3GPP
TS 25.304.
QueueAlgoSwitch Indicating whether queue is supported. When a user initiates a call, if cell resources
are insufficient and the user is queue supportive, the RNC tries to arrange this user
to join the queue to increase access success ratio.
LdrSecondPri 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
second 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.
SeqOfUserRel This parameter indicates whether the MBMS service is released first or user first
when the overload occurs.
ServiceDiffDrdSwitch This parameter specifies whether the service differential DRD algorithm will be
applied.
- ON: The service differential DRD algorithm will be applied.(If cell-level DRD
parameters are configured, the status of cell level Service differential drd switch
should also be considered.)
- OFF: The service differential DRD algorithm will not be applied.
SpgId This parameter identifies a group of cells that have specific capabilities for four
service types: R99 real-time services, R99 non-real-time services, HSPA services,
and other services.
OffSinterLight Offset of Sintersearch when center cell load level is "Light" (Note: Sintersearch is
used to decide whether to start the inter-frequency cell reselection). For detailed
information of this parameter, refer to 3GPP TS 25.304.
OffSinterHeavy Offset of Sintersearch when center cell load level is "Heavy" (Note: Sintersearch is
used to decide whether to start the inter-frequency cell reselection). For detailed
information of this parameter, refer to 3GPP TS 25.304.
LdrThirdPri 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
third 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.
ChoiceRprtUnitForDlBa If you set this parameter to TEN_MSEC, use [DL basic meas rprt cycle,Unit:10ms]
sicMeas to specify the measurement report period. If you set this parameter to MIN, use
Parameter ID Description
[DL basic meas rprt cycle,Unit:min] to specify measurement report period. For
detailed information of this parameter, refer to 3GPP TS 25.433.
ChoiceRprtUnitForUlBa Value range: TEN_MSEC, MIN
sicMeas Physical value range: 10 milliseconds, 1 minute
Content: If you set this parameter to TEN_MSEC, use [UL basic meas rprt
cycle,Unit:10ms] to specify the measurement report period. If you set this
parameter to MIN, use [UL basic meas rprt cycle,Unit:min] to specify
measurement report period. For detailed information of this parameter, refer to
3GPP TS 25.433.
Recommended value: TEN_MSEC
TransCchUserNum Transfer Common Channel User number
Value range: 0~10
Content: When the system is overloaded and congested, users on the DCH can be
reconfigured to the CCH in order to reduce the cell load and recover the system.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
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.
MinForUlBasicMeas UL basic common measurement report cycle. For detailed information of this
parameter, refer to 3GPP TS 25.433.
UlBeTraffInitBitrate UL BE traffic Initial bit rate. When DCCC function is enabled, the uplink initial bit
rate will be set to this value if the uplink max bit rate is higher than the initial bit
rate.The larger this parameter to be set, the sooner max bit rate to be reached, but
the bit rate is more likely to be declined when system congested, so it makes no
sense to set this parameter too high. Contrarily,the smaller the parameter to be set,
the more easily the BE traffic to be accessed at required bit rate. But over small
setting will take longer to adjust to needed bit rate.
UlCCHLoadFactor The admission control decision is only for dedicated channels. For common
channels, some resources instead of a special admission procedure are reserved.
In the UL, according to the current load factor and the characteristics of the new
call, the UL CAC algorithm predicts the new traffic channels load factor with the
assumption of admitting the new call, then plus with the premeditated common
channel UL load factor to get the predicted UL load factor. Then, compare it with
the UL admission threshold. If the value is not higher than the threshold, the call is
admitted; otherwise, rejected. If the value is too high, power resources are wasted,
which impacts system capacity. If the value is too low, resources can be fully used
and coverage may be impacted in case of insufficient resources.
UlCSInterRatShouldBe Number of users selected in a UL LDR CS domain inter-RAT SHOULDBE load
HOUeNum handover. The target subscribers of this parameter are the CS domain subscribers.
Because the CS domain subscribers are session subscribers in general and they
have little impact on load, you can set this parameter to a comparatively high
value.
UlCSInterRatShouldNot Number of users selected in a UL LDR CS domain inter-RAT SHOULDNOTBE
HOUeNum load handover. The target subscribers of this parameter are the CS domain
Issue Error! Unknown Error! Unknown document property 17
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
subscribers. Because the CS domain subscribers are session subscribers in general
and they have little impact on load, you can set this parameter to a comparatively
high value.
UlNonCtrlThdForHo The percentage of the handover service admission threshold to the 100% uplink
load. It is applicable to algorithm 1 and algorithm 2. The parameter is used for
controlling the handover admission. That is, when a service is handing over to a
cell, the RNC evalutates the measurement value of the uplink load after the service
is accessed. If the UL load of a cell is higher than this threshold after the access,
this service will be rejected. If the UL load of a cell will not be higher than this
threshold, this service will be admitted.
The UL load factor thresholds include parameters of [UL threshold of Conv
non_AMR service], [UL handover access threshold] and [UL threshold of other
services]. The four parameters can be used to limit the proportion between the non-
handover service, handover user and other services in a specific cell, and to
guarantee the access priority of the handover service. This parameter is to
guarantee the access priority of the handover service. If the value is too high the
system load after admission may be over large, which impacts system stability and
leads to system congestion. If the value is too low, the possibility of user rejects
may increase, resulting in waste in idle resources.
UlHoCeResvSf Uplink Credit Reserved by Spread Factor for HandOver. SFOFF means that none
of them are reserved for handover.
UlInterFreqHoCellLoad The inter-frequency neighboring cell could be selected as the destination of load
SpaceThd 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.
UlInterFreqHoBWThd 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.
UlHsDpcchRsvdFactor If the HS-DPCCH carries ACK/NACK, the system will not perform CAC. If the
HS-DPCCH carries CQI, the system will perform CAC. This parameter refers to
the resources reserved for the uplink HS-DPCCH carrying ACK/NACK. The
corresponding threshold is the uplink limit capacity multiplied by this parameter. If
the value is too high, the possibility of wrong rejection to uplink admissions
increases, leading to waste in uplink resources. If the value is too low, the uplink
resources is insufficient. However, because the possibility of putburst load by
ACK/NACK and its impact are relatively low, the value can be set to a low level,
representing the loose admission rule.
UlLdrCreditSfResThd Reserved SF threshold in uplink credit LDR. The uplink credit LDR could be
triggered only when the SF factor corresponding to the uplink reserved credit is
higher than the uplink or downlink credit SF reserved threshold. The lower the
parameter value is, the easier the credit enters the congestion status, the easier the
LDR action is triggered, and the easier the user experience is affected. A lower
code resource LDR trigger threshold, however, causes a higher admission success
Issue Error! Unknown Error! Unknown document property 18
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
rate because the resource is reserved. The parameter should be set based on the
operator's requirement.
UlLdrRelThd If the ratio of UL load of the cell to the uplink capacity is lower than this threshold,
the UL load reshuffling function of the cell is stopped. 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 ping-pong effect of the
preliminary congestion state may occur. 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. The carrier shall make a trade-off between these
factors.
UlLdrTrigThd If the ratio of UL load of the cell to the uplink capacity is not lower than this
threshold, the UL 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 ping-pong effect of
the preliminary congestion state may occur. 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. The carrier shall make a trade-off between these
factors.
UlLdrPsRTQosRenegRa Number of RABs selected in a UL LDR uncontrolled real-time traffic QoS
bNum renegotiation. The target subscribers of this parameter are the PS domain real-time
subscribers. The setting of this parameter is analogous to the setting of BE service
rate reduction subscriber number. Because the number of subscribers performing
QoS renegotiation may be smaller than the value of this parameter, for example,
the candidate subscribers selected for downlink LDR do not meet the QoS
renegotiation conditions, you must leave some margin when setting this parameter
to ensure the success of load reshuffling.
UlLdrAMRRateReducti The mechanism of the LDR is that an action is performed in each [LDR period]
onRabNum and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs selected in executing uplink
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.
UlLdrBERateReduction Number of RABs selected in a UL LDR BE traffic rate reduction. In the actual
RabNum 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.
UlOlcFTFRstrctRabNu UL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the uplink TF can be adjusted to restrict the number of blocks
Issue Error! Unknown Error! Unknown document property 19
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
m transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell uplink load.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs selected in executing uplink
OLC fast restriction.
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. In the
actual system, UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum can be set
on the basis of the actual circumstances. If the high-rate subscribers occupy a high
proportion, set UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum to
comparatively low values. If the high-rate subscribers occupy a low proportion, set
UlOlcFTFRstrctRabNum and DlOlcFTFRstrctRabNum to comparatively high
values.
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.
UlOlcFTFRstrctTimes UL fast TF restriction refers to a situation where, when the cell is overloaded and
congested, the uplink TF can be adjusted to restrict the number of blocks
transported in each TTI at the MAC layer and the rate of user data, thus reducing
the cell uplink load.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of uplink OLC fast TF restriction
performed in entering/exiting the OLC status.
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.
The lower the parameters are, the more likely the users are released, resulting in
negative effect on the system performance. If the parameters are excessively high,
the overload status is released slowly.
UlOlcRelThd If the ratio of UL load of the cell to the uplink capacity is lower than this threshold,
the UL overload and congestion control function of the cell is stopped. 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.
UlOlcTraffRelRabNum User release is an extreme method in reducing the cell load and recovering the
system when the cell is overloaded and congested.
The mechanism of the OLC is that an action is performed in each [OLC period]
and some services are selected based on the action rules to perform this action.
This parameter defines the maximum number of RABs released in executing
Issue Error! Unknown Error! Unknown document property 20
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
uplink OLC service release.
For the users of a single service, the releasing of RABs means the complete
releasing of the users. The releasing of RABs causes call drops, so
UlOlcFTFRstrctTimes or DlOlcFTFRstrctTimes should be set to a low value.
Higher values of the parameter get the cell load to decrease more obviously, but the
QoS will be affected.
UlOlcTrigThd If the ratio of UL load of the cell to the uplink capacity is not lower than this
threshold, the UL 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.
UlPSInterRatShouldBe Number of users selected in a UL LDR PS domain inter-RAT SHOULDBE load
HOUeNum handover. The target subscribers of this parameter are the PS domain subscribers.
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.
UlPSInterRatShouldNot Number of users selected in a UL LDR PS domain inter-RAT SHOULDNOTBE
HOUeNum load handover. The target subscribers of this parameter are the PS domain
subscribers. 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.
UlNonCtrlThdForAMR The percentage of the conversational AMR service threshold to the 100% uplink
load.
UlNonCtrlThdForNonA The percentage of the conversational non-AMR service threshold to the 100%
MR uplink load.
UlNonCtrlThdForOther The percentage of other service thresholds to the 100% uplink load.
UlTotalEqUserNum When the algorithm 2 is used, this parameter defines the total equivalent user
numbers corresponding to the 100% uplink load. The parameter should be related
to the admission threshold and actual condition of the network. If the value is too
high, the system load after admission may be over large, which impacts system
stability and leads to system congestion. If the value is too low, the possibility of
user rejects may increase, resulting in waste in idle resources.
UlCellTotalThd Admission threshold of total cell uplink power. This parameter is related to the
target load of the uplink schedule.
Parameter ID Description
UlDcccRateThd 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.
NBMUlCacAlgoSelSwit The algorithms with the above values represent are as follow:
ch ALGORITHM_OFF: Disable uplink call admission control algorithm.
ALGORITHM_FIRST: The load factor prediction algorithm will be used in uplink
CAC.
ALGORITHM_SECOND: The equivalent user number algorithm will be used in
uplink CAC.
ALGORITHM_THIRD: The loose call admission control algorithm will be used in
uplink CAC.
RedirSwitch This parameter specifies whether the RRC redirection algorithm is valid for the
specified service. The algorithm is valid only when the RRC redirection switch is
enabled and when this parameter is set to ONLY_TO_INTER_FREQUENCY or
ONLY_TO_INTER_RAT. Value OFF indicates that RRC redirection is not
allowed. Value ONLY_TO_INTER_FREQUENCY indicates that only the RRC
redirection to an inter-frequency neighboring cell is allowed. Value
ONLY_TO_INTER_RAT indicates that only the RRC redirection to an inter-RAT
neighboring cell is allowed.
RedirFactorOfNorm When the load of the serving cell is within the normal range, a UE may be
redirected to another cell according to the traffic type. This parameter specifies the
possibility of redirecting the UE to another cell. When this parameter is set to 0, the
RRC redirection is not performed if the load of the serving cell is within the normal
range.
RedirFactorOfLDR When the UL load state or DL load state of the serving cell is LDR or OLC, a UE
may be redirected to another cell according to the traffic type. This parameter
specifies the possibility of redirecting the UE to another cell. When this parameter
is set to 0, the RRC redirection is not performed if the load state on the serving cell
is LDR or OLC. LDR indicates basic congestion. OLC indicates overload
congestion.
RedirBandInd This parameter specifies the target frequency band in the redirection procedure.
ReDirUARFCNUplinkI This parameter specifies whether the UL frequency of the target cell of redirection
nd needs to be configured.
- TRUE: The UL frequency needs to be configured.
- FALSE: The UL frequency does not need to be configured. It is configured
automatically according to the relationship between UL and DL frequencies.
ReDirUARFCNUplink This parameter specifies the target uplink UARFCN of a cell for RRC redirection.
Depending on the band indication, the value range as shown below:
Band1:
Common frequencies: [9612-9888]
Special frequencies: none
Band2:
Common frequencies: [9262-9538]
Special frequencies: {12, 37, 62, 87, 112, 137, 162, 187, 212, 237, 262, 287}
Band3:
Common frequencies: [937-1288]
Special frequencies: none
Issue Error! Unknown Error! Unknown document property 22
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
Band4:
Common frequencies: [1312-1513]
Special frequencies: {1662, 1687, 1712, 1737, 1762, 1787, 1812, 1837, 1862}
Band5:
Common frequencies: [4132-4233]
Special frequencies: {782, 787, 807, 812, 837, 862}
Band6:
Common frequencies: [4162-4188]
Special frequencies: {812, 837}
Band7:
Common frequencies: [2012-2338]
Special frequencies: {2362, 2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662, 2687}
Band8:
Common frequencies: [2712-2863]
Special frequencies: none
Band9:
Common frequencies: [8762-8912]
Special frequencies: none
BandIndNotUsed:
[0-16383]
Assume that the target uplink UARFCN for RRC redirection is unspecified, the
band indication is Band1, Band2, Band3, Band4, Band5, Band6, Band7, Band8, or
Band9, and the target downlink UARFCN for RRC redirection is valid. Then, the
default target uplink UARFCN for RRC redirection is as follows:
- If the DL frequency belongs to common frequencies, then
Band1: Uplink UARFCN = Downlink UARFCN - 950
Band2: Uplink UARFCN = Downlink UARFCN - 400
Band3: Uplink UARFCN = Downlink UARFCN - 225
Band4: Uplink UARFCN = Downlink UARFCN - 225
Band5: Uplink UARFCN = Downlink UARFCN - 225
Band6: Uplink UARFCN = Downlink UARFCN - 225
Band7: Uplink UARFCN = Downlink UARFCN - 225
Band8: Uplink UARFCN = Downlink UARFCN - 225
Band9: Uplink UARFCN = Downlink UARFCN - 475
- If the DL frequency belongs to special frequencies, then
Band2: Uplink UARFCN = Downlink UARFCN - 400
Band4: Uplink UARFCN = Downlink UARFCN - 225
Band5: Uplink UARFCN = Downlink UARFCN - 225
Band6: Uplink UARFCN = Downlink UARFCN - 225
Band7: Uplink UARFCN = Downlink UARFCN - 225
ReDirUARFCNDownli This parameter specifies the target downlink UARFCN of a cell for RRC
nk redirection.
EcN0EffectTime This parameter specifies the time duration when the reported Ec/N0 is valid. The
reported Ec/N0 is valid for the period (starting from the time when the RRC
connection request is initiated) specified by this parameter. Check whether the
reported Ec/N0 is valid before comparing it with EcN0Ths.
EcN0Ths This parameter specifies the threshold for determining the signal quality in a cell. If
the reported Ec/N0 exceeds the value of this parameter, you can infer that the
signal quality in the cell is good and a high code rate can be set for initial access.
Parameter ID Description
ZeroRateUpFailToRelTi For the PS BE service at a rate of 0 kbit/s, this parameter is used for the rate
merLen upsizing for DCCC triggered by event 4A. Unsuccessful rate upsizing indicates
that the resources are insufficient in the cell. The service may run at a rate of 0
kbit/s for a long time. If the timer is started, the 0 kbit/s service of the UE is
released after the timer expires. If the length is set to 0, the timer is not started.
FACHPwrReduceValue This parameter defines the reduce value in reducing FACH power Action.
DrSwitch Direct retry switch.
1) DR_RRC_DRD_SWITCH(DRD switch for RRC connection): When the switch
is on, DRD and redirection is performed for RRC connection if retry is required.
2) DR_RAB_SING_DRD_SWITCH(DRD switch for single RAB): When the
switch is on, DRD is performed for single service if retry is required.
3) DR_RAB_COMB_DRD_SWITCH(DRD switch for combine RAB): When the
switch is on, DRD is performed for combined services if retry is required.
DraSwitch Dynamic resource allocation switch.
1) DRA_AQM_SWITCH: When the switch is on, the active queue management
algorithm is used for the RNC.
2) DRA_BE_EDCH_TTI_RECFG_SWITCH: When the switch is on, the TTI
could be reconfigured to HSUPA traffic dynamically between 2ms and 10ms.
3) DRA_BE_RATE_DOWN_BF_HO_SWITCH: When the switch is on, the
bandwidth for BE services is reduced before soft handover. It is recommended that
the DCCC switch be on when this switch is on.
4) DRA_DCCC_SWITCH: When the switch is on, the dynamic channel
reconfiguration control algorithm is used for the RNC.
5) DRA_HSDPA_DL_FLOW_CONTROL_SWITCH: When the switch is on,
power control is enabled for HSDPA services in AM mode.
6) DRA_HSDPA_STATE_TRANS_SWITCH: When the switch is on, the status of
the UE RRC that carrying HSDPA services can be changed to CELL_FACH at the
RNC. If a PS BE service is carried over the HS-DSCH, the switch
PS_BE_STATE_TRANS_SWITCH should be on simultaneously. If a PS real-time
service is carried over the HS-DSCH, the switch
PS_NON_BE_STATE_TRANS_SWITCH should be on simultaneously.
7) DRA_HSUPA_DCCC_SWITCH: When the switch is on, the DCCC algorithm
is used for HSUPA. The DCCC switch must be also on before this switch takes
effect.
8) DRA_HSUPA_STATE_TRANS_SWITCH: When the switch is on, the status of
the UE RRC that carrying HSUPA services can be changed to CELL_FACH at the
RNC. If a PS BE service is carried over the E-DCH, the switch
PS_BE_STATE_TRANS_SWITCH should be on simultaneously. If a PS real-time
service is carried over the E-DCH, the switch
PS_NON_BE_STATE_TRANS_SWITCH should be on simultaneously.
9) DRA_IU_QOS_RENEG_SWITCH: When the switch is on and the Iu QoS
RENEQ license is activated, the RNC supports renegotiation of the maximum rate
if the QoS of real-time services is not ensured according to the cell status.
10) DRA_PS_BE_STATE_TRANS_SWITCH: When the switch is on, UE RRC
status transition (CELL_FACH/CELL_PCH/URA_PCH) is allowed at the RNC.
11) DRA_PS_NON_BE_STATE_TRANS_SWITCH: When the switch is on, the
status of the UE RRC that carrying real-time services can be changed to
CELL_FACH at the RNC.
12) DRA_R99_DL_FLOW_CONTROL_SWITCH: Under a poor radio
environment, the QoS of high speed services drops considerably and the TX power
is overly high. In this case, the RNC can set restrictions on certain transmission
Issue Error! Unknown Error! Unknown document property 24
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
formats based on the transmission quality, thus lowering traffic speed and TX
power. When the switch is on, the Iub overbooking function is enabled.
13) DRA_THROUGHPUT_DCCC_SWITCH: When the switch is on, the DCCC
based on traffic statistics is supported over the DCH.
NbmLdcBHOUeSelSwit The algorithms with the above values represent are as follow:
ch NBM_LDC_ALL_UE: When BHO select user occus, no need to consider whether
target cell support Ue. NBM_LDC_MATCH_UE_ONLY: When BHO select user
occus, only consider Ues supported by target cell.
NBM_LDC_MATCH_UE_FIRST: When BHO select user occus, first consider
Ues supported by target cell.
PsSwitch PS rate negotiation switch.
1) PS_BE_EXTRA_LOW_RATE_ACCESS_SWITCH: When the switch is on,
access at a rate of 0 kbit/s or on the FACH is determined according to the current
connection state of the RRC if the PS BE admission and the later preemption and
queuing fail.
2) PS_BE_INIT_RATE_DYNAMIC_CFG_SWITCH: When the switch is on, the
initial rate of the service should be dynamically configured according to the value
of Ec/No reported by the UE when the PS BE service is established.
3) PS_BE_IU_QOS_NEG_SWITCH: When the switch is on, the Iu QoS
Negotiation function is applied to the PS BE service if Alternative RAB Parameter
Values IE is present in the RANAP RAB ASSIGNMENT REQUEST or
RELOCATION REQUEST message.
4) PS_RAB_DOWNSIZING_SWITCH: When the switch is on and the RAB
downsizing license is activated, the initial speed is determined on the basis of cell
resources. Downsizing is implemented for BE services.
5) PS_RSC_FEEDBK_RABSETUP_CACFAIL_SWITCH: When the switch is on,
the SF feedback function is supported. If the SF is provided in feedback
information after the application for the cell SF is rejected, access at a lower speed
is performed on the basis of the returned SF.
6) PS_STREAM_IU_QOS_NEG_SWITCH: When the switch is on, the Iu QoS
Negotiation function is applied to the PS STREAM service if Alternative RAB
Parameter Values IE is present in the RANAP RAB ASSIGNMENT REQUEST or
RELOCATION REQUEST message.
7) PS_BE_STRICT_IU_QOS_NEG_SWITCH: When the switch is on, the strict Iu
QoS Negotiation function is applied to the PS BE service,RNC select Iu max bit
rate based on UE capacity,cell capacity,max bitrate and alternative RAB parameter
values in RANAP RAB ASSIGNMENT REQUEST or RELOCATION REQUEST
message. When the switch is not on, the loose Iu QoS Negotiation function is
applied to the PS BE service,RNC select Iu max bit rate based on UE capacity,max
bitrate and alternative RAB parameter values in RANAP RAB ASSIGNMENT
REQUEST or RELOCATION REQUEST message,not consider cell capacity,this
can avoid Iu QoS Renegotiation between different cell.The switch is valid when
PS_BE_IU_QOS_NEG_SWITCH is set to ON.
RlMaxDlPwr This parameter should fulfill the coverage requirement of the network planning,
and the value is relative to [PCPICH transmit power]. If the parameter is
excessively high, downlink interference may occur. If the parameter is excessively
low, the downlink power control may be affected. For detailed information of this
parameter, refer to 3GPP TS 25.433.
UlBasicCommMeasFilte Value range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15, D17, D19
rCoeff Physical value range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19
Parameter ID Description
Content: L3 filtering coefficient. The larger the value of this parameter, the
stronger the smoothing effect and the higher the anti-slow-fading capability, but
the lower the signal change tracing capability. For detailed information of this
parameter, refer to 3GPP TS 25.433.
Recommended value: D6
DlBasicCommMeasFilte L3 filtering coefficient. The larger the value of this parameter, the stronger the
rCoeff smoothing effect and the higher the anti-slow-fading capability, but the lower the
signal change tracing capability. For detailed information of this parameter, refer to
3GPP TS 25.433.
PucAvgFilterLen Length of smoothing filter window of potential user control (PUC).
UlCacAvgFilterLen Length of smoothing filter window of uplink CAC.
DlCacAvgFilterLen Length of smoothing filter window of downlink CAC.
LdbAvgFilterLen Length of smoothing filter window of intra-frequency load balancing (LDB).
UlLdrAvgFilterLen Length of smoothing filter window of uplink LDR.
DlLdrAvgFilterLen Length of smoothing filter window of downlink LDR.
UlOlcAvgFilterLen Length of smoothing filter window of uplink OLC.
DlOlcAvgFilterLen Length of smoothing filter window of downlink OLC.
HsdpaNeedPwrFilterLe Length of smoothing filter window of HSDPA power requirement.
n
ChoiceRprtUnitForHsdp If you set this parameter to TEN_MSEC, use [HSDPA need pwr meas
aPwrMeas cycle,Unit:10ms] to specify the measurement report period. If you set this
parameter to MIN, use [HSDPA need pwr meas cycle,Unit:min] to specify
measurement report period. For detailed information of this parameter, refer to
3GPP TS 25.433.
TenMsecForHsdpaPwr HSDPA power requirement measurement report period For detailed information of
Meas this parameter, refer to 3GPP TS 25.433.
MinForHsdpaPwrMeas HSDPA power requirement measurement report period For detailed information of
this parameter, refer to 3GPP TS 25.433.
ChoiceRprtUnitForHsdp If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
aRateMeas cycle,Unit:10ms] to specify the measurement report period. If you set this
parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify
measurement report period. For detailed information of this parameter, refer to
3GPP TS 25.433.
TenMsecForHsdpaPrvid This parameter specifies the HSDPA bit rate measurement report period. For
RateMeas detailed information of this parameter, refer to 3GPP TS 25.433.
MinForHsdpaPrvidRate This parameter specifies the HSDPA bit rate measurement report period. For
Meas detailed information of this parameter, refer to 3GPP TS 25.433.
ChoiceRprtUnitForHsup If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
aRateMeas cycle,Unit:10ms] to specify the measurement report period. If you set this
parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify
measurement report period. For detailed information of this parameter, refer to
Issue Error! Unknown Error! Unknown document property 26
document property name. name.
(Error! Unknown document
property name.)
Error! Unknown document property name.
Error! Unknown document property name. 12 Load Control Parameters
Parameter ID Description
3GPP TS 25.433.
TenMsecForHsupaPrvid This parameter specifies the HSUPA bit rate measurement report period. For
RateMeas detailed information of this parameter, refer to 3GPP TS 25.433.
MinForHsupaPrvidRate This parameter specifies the HSUPA bit rate measurement report period. For
Meas detailed information of this parameter, refer to 3GPP TS 25.433.
HsdpaPrvidBitRateFilter Length of smoothing filter window of HSDPA bit rate.
Len
HsupaPrvidBitRateFilter Length of smoothing filter window of HSUPA bit rate.
Len
DRMaxGSMNum This parameter specifies the maximum number of inter-RAT RAB directed retries.
It decides the size of the candidate set for inter-RAT DRD. The value 0 indicates
that inter-RAT RAB DRD is not applicable. This parameter can be cell-oriented.
RsvdPara1 The algorithms with the above values represent are as follow:
RsvdBit1: Control RTWP Anti-interfence algorithm
RsvdBit2RsvdBit16: Reserved Switch
If RsvdBit1 is selected, the corresponding algorithm is enabled; otherwise, the
algorithm is disabled.
UlOlcTrigHyst UL OLC trigger hysteresis.
SLOCELL It refers to Source LocalCell ID.
DLOCELL It refers to Destination LocalCell ID.
MAXSHRTO Max Sharing Power Ratio.
SHMGN Sharing Power Margin.
The Default Value column is valid for only the optional parameters.
The "-" symbol indicates no default value.
13 Reference Documents