Load Control Huawei

RAN
Load Control Parameter Description
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.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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.
About This Document

Author
Prepared by
Wu Xianbin
Date
2008-10-26
Edited by
Cheng Xiaoli
Date
2008-12-09
Reviewed by
Zeng Yongmei
Date
2008-12-10
Translated
by
Wang Xiaofen
Date
2008-12-20
Tested by
Zhang Shasha
Date
2009-01-10
Approved by
Duan Zhongyi
Date
2009-03-30
RAN
Contents
Contents
1 Change History.............................................................................3
2 Load Control Introduction..............................................................3
3 Load Control Algorithm Overview...................................................3
3.1 Load Control Workflow.....................................................................................................................................3
3.2 Algorithm Introduction......................................................................................................................................3
3.3 Priorities Involved in Load Control...................................................................................................................3
3.3.1 User Priority.............................................................................................................................................3
3.3.2 RAB Integrated Priority............................................................................................................................3
3.3.3 User Integrated Priority............................................................................................................................3
4 Load Measurement Algorithm........................................................3

4.1 Measurement Quantities and Procedure............................................................................................................3
4.1.1 Major Measurement Quantities................................................................................................................3
4.1.2 LDM Procedure........................................................................................................................................3
4.2 Load Measurement Filtering..............................................................................................................................3
4.2.1 Filtering on the NodeB Side.....................................................................................................................3
4.2.2 Smooth Window Filtering on the RNC Side............................................................................................3
4.2.3 Reporting Period.......................................................................................................................................3
4.2.4 Provided Bit Rate......................................................................................................................................3
4.3 Auto-Adaptive Background Noise Algorithm...................................................................................................3
5 Potential User Control Algorithm...................................................3

6 Intelligent Access Control Algorithm..............................................3
6.1 IAC Overview....................................................................................................................................................3
6.2 IAC During RRC Connection Setup..................................................................................................................3
6.2.1 RRC Redirection for Service Steering......................................................................................................3
6.2.2 RRC DRD.................................................................................................................................................3
6.2.3 RRC Redirection After DRD Failure........................................................................................................3
6.3 Rate Negotiation................................................................................................................................................3
6.3.1 PS MBR Negotiation................................................................................................................................3
6.3.2 PS GBR Negotiation.................................................................................................................................3
6.3.3 Initial Rate Negotiation............................................................................................................................3
Issue 01 (2009-03-30)
Huawei Proprietary and Confidential

Copyright Huawei
Technologies Co., Ltd
RAN
Contents
6.3.4 Target Rate Negotiation............................................................................................................................3

6.4 RAB DRD..........................................................................................................................................................3
6.4.1 RAB DRD Overview................................................................................................................................3
6.4.2 Inter-Frequency DRD for Service Steering..............................................................................................3
6.4.3 Inter-Frequency DRD for Load Balancing...............................................................................................3
6.4.4 Inter-Frequency DRD...............................................................................................................................3
6.4.5 Inter-RAT DRD........................................................................................................................................3
6.5 Preemption.........................................................................................................................................................3
6.6 Queuing..............................................................................................................................................................3
6.7 Low-Rate Access of the PS BE Service.............................................................................................................3
6.8 IAC for Emergency Calls...................................................................................................................................3
6.8.1 RRC Connection Setup Process of Emergency Calls...............................................................................3
6.8.2 RAB Process of Emergency Calls............................................................................................................3
7 Call Admission Control Algorithm...................................................3

7.1 CAC Overview..................................................................................................................................................3
7.2 CAC Based on Code Resource..........................................................................................................................3
7.3 CAC Based on Power Resource........................................................................................................................3
7.3.1 Overview..................................................................................................................................................3
7.3.2 Admission Decision for RRC Connection Setup Request........................................................................3
7.3.3 Power-Based Admission Algorithm 1......................................................................................................3
7.4 CAC Based on NodeB Credit Resource............................................................................................................3
7.4.1 NodeB Credit............................................................................................................................................3
7.4.2 Procedure of Admission Decision Based on NodeB Credit.....................................................................3
7.5 CAC Based on Iub Resource.............................................................................................................................3
7.6 CAC Based on the Number of HSPA Users......................................................................................................3
7.6.1 CAC of HSDPA Users..............................................................................................................................3
7.6.2 CAC of HSUPA Users..............................................................................................................................3
8 Intra-Frequency Load Balancing Algorithm.....................................3

9 Load Reshuffling Algorithm............................................................3
9.1 Basic Congestion Triggering.............................................................................................................................3
9.1.1 Power Resource........................................................................................................................................3
9.1.2 Code Resource..........................................................................................................................................3
9.1.3 Iub Resource.............................................................................................................................................3
9.1.4 NodeB Credit Resource............................................................................................................................3
9.2 LDR Procedure..................................................................................................................................................3
9.3 LDR Actions......................................................................................................................................................3
9.3.1 Inter-Frequency Load Handover..............................................................................................................3
9.3.2 BE Rate Reduction...................................................................................................................................3
9.3.3 QoS Renegotiation for Uncontrollable Real-Time Services....................................................................3
Issue 01 (2009-03-30)

Copyright Huawei
RAN
Contents
9.3.4 Inter-RAT Handover in the CS Domain...................................................................................................3

9.3.5 Inter-RAT Handover in the PS Domain....................................................................................................3
9.3.6 AMR Rate Reduction................................................................................................................................3
9.3.7 Code Reshuffling......................................................................................................................................3
9.3.8 MBMS Power Reduction..........................................................................................................................3
9.3.9 UL and DL LDR Action Combination of a UE........................................................................................3
10 Overload Control Algorithm.........................................................3

10.1 OLC Triggering................................................................................................................................................3
10.2 General OLC Procedure...................................................................................................................................3
10.3 OLC Actions....................................................................................................................................................3
10.3.1 Performing TF Control of BE Services..................................................................................................3
10.3.2 Switching BE Services to Common Channels.......................................................................................3
10.3.3 Adjusting the Maximum FACH TX Power............................................................................................3
10.3.4 Releasing Some RABs............................................................................................................................3
11 Dynamic Power Sharing Among Carriers.......................................3

11.1 Introduction......................................................................................................................................................3
11.2 Power Sharing Mode........................................................................................................................................3
12 Load Control Parameters.............................................................3

12.1 Description.......................................................................................................................................................3
12.2 Values and Ranges...........................................................................................................................................3
13 Reference Documents.................................................................3
Issue 01 (2009-03-30)

Copyright Huawei
RAN
1 Change History
Change History
The change history provides information on the changes in different document versions.
Document and Product Versions

Document Version
RAN Version
01 (2009-03-30)
11.0
Draft (2009-03-10)
11.0
Draft (2009-01-15)
11.0
This document is based on the BSC6810 and 3900 series NodeBs.

The available time of each feature is subject to the RAN product roadmap.
There are two types of changes, which are defined as follows:
Feature change: refers to the change in the load control feature.
Editorial change: refers to the change in the information that was inappropriately
described or the addition of the information that was not described in the earlier version.
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:
Change
Type
Change Description
Parameter Change
Feature change
The description of Control RTWP

Anti-interfence algorithm is added.
For details, see 7.3"CAC Based on
Power Resource" and 10.3"OLC
Actions."
The added parameter is as

follows: RsvdPara1.
Issue 01 (2009-03-30)

Copyright Huawei
RAN
1 Change History
Change
Type
Change Description
Parameter Change
Editorial change
None.
None.
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:
Change
Type
Change Description
Parameter Change
Feature change
None.
None.
Editorial
change
The description of dynamic

cell shutdown algorithm is
moved to Green BTS
Description.
The corresponding parameters as

follows are move to Green BTS
Description:
StartTime1
EndTime1
StartTime2
EndTime2
StartTime3
EndTime3
DynShutdownSwitch
TotalUserNumThd
HsdpaUserNumThd
HsupaUserNumThd
NCellLdrRemainThd
DynCellShutdownProtectTimerlen
DynCellOpenJudgeTimerlen
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:
Issue 01 (2009-03-30)

Copyright Huawei
RAN
1 Change History
Change
Type
Change Description
Parameter Change
Feature change
Some parameters are added to

section 4.1"Measurement
Quantities and Procedure."
The added parameters are as follows:
The description of RRC

redirection for service steering
is added. For details, see
1"RRC Redirection for Service
Steering."
The description of initial rate

negotiation for BE services is
optimized. For details, see
6.3.3"Initial Rate
Negotiation."
Issue 01 (2009-03-30)
UlBasicCommMeasFilterCoeff
DlBasicCommMeasFilterCoeff
PucAvgFilterLen
UlCacAvgFilterLen
DlCacAvgFilterLen
LdbAvgFilterLen
UlLdrAvgFilterLen
DlLdrAvgFilterLen
UlOlcAvgFilterLen
DlOlcAvgFilterLen
HsdpaNeedPwrFilterLen
ChoiceRprtUnitForHsdpaPwrMeas
TenMsecForHsdpaPwrMeas
MinForHsdpaPwrMeas
ChoiceRprtUnitForHsdpaRateMeas
TenMsecForHsdpaPrvidRateMeas
MinForHsdpaPrvidRateMeas
ChoiceRprtUnitForHsupaRateMeas
TenMsecForHsupaPrvidRateMeas
MinForHsupaPrvidRateMeas
HsdpaPrvidBitRateFilterLen
HsupaPrvidBitRateFilterLen
RedirSwitch
RedirFactorOfNorm
RedirFactorOfLDR
RedirBandIn
ReDirUARFCNUplinkInd
ReDirUARFCNUplink
ReDirUARFCNDownlink
EcN0EffectTime
EcN0Ths

Copyright Huawei
RAN
Change
Type
1 Change History
Change Description
Parameter Change
The description of low-rate

access is added. For details,
see 6.1"IAC Overview" and
6.7"Low-Rate Access of the
PS BE Service."
The description of an OLC

action, that is, the adjustment
of maximum FACH transmit
power, is added. For details,
see 10.3.3"Adjusting the
Maximum FACH TX Power."
The added parameter is as follows:

cell shutdown algorithm is
added.

power sharing among carriers
is added. For details, see
11"Dynamic Power Sharing
Among Carriers."
Editorial
change
The title of the document is

changed from Load Control
Description to Load Control
Parameter Description.
PSBELowRateAccessSwitch
ZeroRateUpFailToRelTimerLen
FACHPwrReduceValue
StartTime1
EndTime1
StartTime2
EndTime2
StartTime3
EndTime3
DynShutdownSwitch
TotalUserNumThd
HsdpaUserNumThd
HsupaUserNumThd
NCellLdrRemainThd
DynCellShutdownProtectTimerlen
DynCellOpenJudgeTimerlen
SLOCELL
DLOCELL
MAXSHRTO
SHMGN
None.
Parameter names are replaced

with parameter IDs.
Issue 01 (2009-03-30)

Copyright Huawei
RAN
9 Load Reshuffling Algorithm
Load Control Introduction
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 on System Performance
Impact
This feature has no impact on system performance.
Impact on Other Features

This feature has no impact on other features.
Network Elements Involved

Table 2.1.1.I.1.1.1.1 lists the Network Elements (NEs) involved in load control.
Issue 01 (2009-03-30)

Copyright Huawei
RAN
9 Load Reshuffling Algorithm
Table 2.1.1.I.1.1.1.1 NEs involved in load control

U
E
Node
B
RN
C
MSC Server
MGW
SGSN
GGSN
HLR
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
Issue 01 (2009-03-30)

Copyright Huawei
Load Control Algorithm

Overview
This chapter consists of the following sections:
Load Control Workflow
Algorithm Introduction
Priorities Involved in Load Control
3.1 Load Control Workflow

Depending on the actual phase of UE access, different load control algorithms are used, as
shown in the following figure.
Figure 3.1.1.I.1.1.1 Load Control algorithms in different UE access phases
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.1.1.I.1.1.2 Load control algorithms used on different cell load levels
3.2 Algorithm Introduction

The load control algorithms are built into the RNC.The input of load control comes from the
measurement information of the NodeB.
Figure 3.2.1.I.1.1.1 Load control algorithm in the WCDMA system
Load control has the following algorithms:
Potential User Control (PUC)
The function of PUC is to balance traffic load between inter-frequency cells. The RNC
uses PUC to modify cell selection and reselection parameters, and broadcasts them
through system information. In this way, UEs are led to cells with a light load. The 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.
Table 3.2.1.I.1.1.1.1 Resources used by different load control algorithms

Resources
Power
Code
NodeB
Credits
Iub
Bandwid
th
CAC
IAC
PUC
LDB
LDR
OLC
Dynamic power sharing among

carriers
NOTE
: not considered
: considered
3.3 Priorities Involved in Load Control

The priorities involved in load control are user priority, Radio Access Bearer (RAB)
integrated priority, and user integrated priority.
3.3.1 User Priority

There are three levels of user priority (1, 2, and 3), which are denoted as gold (high priority),
silver (middle priority) and copper (low priority) users. The relation between user priority and
Allocation Retention Priority (ARP) can be set through SET USERPRIORITY command;
the typical relation is shown in the following table.
Table 3.3.1.I.1.1.1.1 Typical relation between user priority and ARP
ARP
1
0
11
1
2
1
3
1
4
15
User
Priori
ty
ERRO
R
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
3.3.2 RAB Integrated Priority

RAB integrated priority is mainly used in load control algorithms.
The values of RAB integrated priority are set according to the integrated priority
configuration reference parameter (PriorityReference):
If the integrated priority configuration reference parameter is set to Traffic Class, the
integrated priority abides by the following rules:
Traffic classes: conversational -> streaming -> interactive -> background =>
Services of the same class: priority based on Allocation/Retention Priority (ARP)

values, that is, ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>
Only for the interactive service of the same ARP value: priority based on Traffic
Handling Priority (THP), that is, THP1 -> THP2 -> THP3 -> ... -> THP14 =>
Services of the same ARP, traffic class and THP (only for interactive services): High
Speed Packet Access (HSPA) or Dedicated Channel (DCH) service preferred
depending on the carrier type priority indicator parameter (CarrierTypePriorInd).
If the integrated priority configuration reference parameter is set to ARP, the integrated
priority abides by the following rules:
ARP: ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>
Services of the same ARP: priority based on traffic classes, that is, conversational ->
streaming -> interactive -> background =>
Only for the interactive service of the same ARP value: priority based on Traffic
Handling Priority (THP), that is, THP1 -> THP2 -> THP3 -> ... -> THP14 =>
Services of the same ARP, traffic class and THP (only for interactive services): HSPA
or DCH service preferred depending on the carrier type priority indicator parameter.
ARP and THP are carried in the RAB ASSIGNMENT REQUEST message, and they are not
configurable on the RNC LMT.
3.3.3 User Integrated Priority

For multiple-RAB users, the integrated priority of the user is based on the service of the
highest priority. User integrated priority is used in user-specific load control. For example, the
selection of R99 users during preemption, the selection of users during inter-frequency load
handover for LDR, and the selection of users during switching of BE services to common
channels are performed according to the user integrated priority.
Load Measurement Algorithm
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.
Measurement Quantities and Procedure
Load Measurement Filtering
Auto-Adaptive Background Noise Algorithm
4.1 Measurement Quantities and Procedure

4.1.1 Major Measurement Quantities
The major measurement quantities of the LDM are as follows:
Uplink Received Total Wideband Power (RTWP)
Downlink Transmitted Carrier Power (TCP)
Non-HSPA power: TCP excluding the power used for transmission on HS-PDSCH, HSSCCH, E-AGCH, E-RGCH, and E-HICH
Here:
HS-PDSCH: High Speed Physical Downlink Shared Channel
HS-SCCH: High Speed Shared Control Channel
E-AGCH: Enhanced Dedicated Channel (E-DCH) Absolute Grant Channel
E-RGCH: E-DCH Relative Grant Channel
E-HICH: E-DCH HARQ Acknowledgement Indicator Channel
Provided Bit Rate (PBR) on HS-DSCH
PBR on E-DCH
Power Requirement for GBR (GBP) on HS-DSCH: minimum power required to ensure
the GBR on HS-DSCH
Received Scheduled E-DCH Power Share (RSEPS): power of the E-DCH scheduling
service
4.1.2 LDM Procedure

The following figure shows the LDM procedure.
Figure 4.1.2.I.1.1.1 LDM procedure
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.
4.2 Load Measurement Filtering

4.2.1 Filtering on the NodeB Side
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.
Figure 4.2.1.I.1.1.1 Measurement model at the physical layer
In Figure 4.2.1.I.1.1.1:
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.
4.2.2 Smooth Window Filtering on the RNC Side

After the RNC receives the measurement report, it filters the measurement value with the
smooth window.
Assuming that the reported measurement value is Qn and that the size of the smooth window
is N, the filtered measurement value is
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.
Algorithm
Smooth Window Length Parameter
PUC
PucAvgFilterLen
CAC
UlCacAvgFilterLen
DlCacAvgFilterLen
LDB
LdbAvgFilterLen
LDR
UlLdrAvgFilterLen
DlLdrAvgFilterLen
OLC
UlOlcAvgFilterLen
DlOlcAvgFilterLen
GBP measurements have the same smooth window length in all related algorithms. The filter length for
GBP measurement is specified by the HsdpaNeedPwrFilterLen parameter.
4.2.3 Reporting Period

The NodeB periodically reports each measurement quantity to the RNC. The following table
lists the reporting period parameters for setting different measurement quantities.
Measurement
Reporting Period Parameter
RTWP
ChoiceRprtUnitForUlBasicMeas
RSEPS
TenMsecForUlBasicMeas
TCP
Non-HSDPA power
MinForUlBasicMeas
ChoiceRprtUnitForDlBasicMeas
TenMsecForDlBasicMeas
MinForDlBasicMeas
GBP
ChoiceRprtUnitForHsdpaPwrMeas
TenMsecForHsdpaPwrMeas
MinForHsdpaPwrMeas
4.2.4 Provided Bit Rate

The Provided Bit Rate (PBR) measurement quantity is also reported by the NodeB to the
RNC. Different from other power measurement quantities, PBR does not undergo alpha
filtering on the NodeB side.
For details about PBR, see the 3GPP 25.321.
The following table lists the PBR reporting period parameters.
Measurement
Reporting Period Parameter
HS-DSCH PBR
ChoiceRprtUnitForHsdpaRateMeas
TenMsecForHsdpaPrvidRateMeas
MinForHsdpaPrvidRateMeas
E-DCH PBR
ChoiceRprtUnitForHsupaRateMeas
TenMsecForHsupaPrvidRateMeas
MinForHsupaPrvidRateMeas
On the RNC side, the length of the PBR smooth filter window is specified by the
HsdpaPrvidBitRateFilterLen / HsupaPrvidBitRateFilterLen parameter.
4.3 Auto-Adaptive Background Noise Algorithm

Uplink (UL) background noise is sensitive to environmental conditions. Therefore, the LDM
algorithm incorporates an auto-adaptive update algorithm to restrict the background noise
within a specified range, as described here:
If the temperature in the equipment room is constant, the background noise changes
slightly. In this case, the background noise requires no more adjustment after initial
correction.
If the temperature in the equipment room varies with the ambient temperature, the
background noise changes greatly. In this case, the background noise requires autoadaptive upgrade.
Figure 4.3.1.I.1.1.1 shows the procedure of auto-adaptive background noise upgrade, which is
enabled by the BGNSwitch parameter.
BGNSwitch is set to ON by default.
Figure 4.3.1.I.1.1.1 Procedure of auto-adaptive background noise upgrade
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 M n
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 |F n - 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 |F n - 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.
Potential User Control

Algorithm
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 only valid for inter-frequency cells.
Figure 5.1.1.I.1.1.1 shows the PUC procedure.

Figure 5.1.1.I.1.1.1 PUC procedure
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.1.1.I.1.1.2.
Figure 5.1.1.I.1.1.2 Cell load states
PUC takes effect only in downlink.
Based on the cell load, the PUC works as follows:
If the cell load becomes heavy, the PUC modifies cell selection and reselection
parameters and broadcasts them through system information. In this way, the PUC leads
UEs to the neighboring cells with light load.
If the cell load becomes normal, the PUC uses the cell selection and reselection
parameters configured on the RNC LMT.
If the cell load becomes light, the PUC modifies cell selection and reselection parameters
and broadcasts them through system information. In this way, the PUC leads UEs to this
cell.
Table 5.1.1.I.1.1.2.1 describes PUC-related variables and their impacts on UEs.
Table 5.1.1.I.1.1.2.1 PUC-related variables and their impacts on UEs

Item
Description
Implementatio
n
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 HSDSCH 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
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.1.1.I.1.1.2.2 describes the changes of Sintersearch.
Table 5.1.1.I.1.1.2.2 Changes of Sintersearch according to the load state
Load State of
the Current
Cell
Sintersearch
Change of
Sintersearch
Light
S'intersearch = Sintersearch + OffSinterLight
Normal
S'intersearch = Sintersearch
Heavy
S'intersearch = Sintersearch +
OffSinterHeavy
Load State of
the Current
Cell
Sintersearch
Change of
Sintersearch
: indicates that the parameter value remains unchanged.

: indicates that the parameter value increases.
: indicates that the parameter value decreases.
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.1.1.I.1.1.2.3 describes the changes of Qoffset1 and Qoffset2.
Table 5.1.1.I.1.1.2.3 Changes of Qoffset1 and Qoffset2 according to the load state
Load State
of the
Neighboring
Cells
Load
State of
the
Current
Cell
Q'offset1
Change
of
Q'offset
1
Q'offset2
Change
of
Q'offset
2
Light
Light
Q'offset1 = Qoffset1
Light
Normal
Light
Heavy
+ OffQoffset1Light
+ OffQoffset2Light
Normal
Light
Normal
Normal
Normal
Heavy
+ OffQoffset1Light
+ OffQoffset2Light
Heavy
Light
+ OffQoffset1Heavy
+ OffQoffset2Heavy
Heavy
Normal
+ OffQoffset1Heavy
+ OffQoffset2Heavy
Heavy
Heavy
The prerequisite for the changes of the preceding parameters is that these parameters take their default
values.
Intelligent Access Control

Algorithm
The access of a service to the network consists of setup of an RRC connection and a RAB.
The Intelligent Access Control (IAC) algorithm is used to improve the access success rate.
IAC Overview
IAC During RRC Connection Setup
Rate Negotiation
RAB DRD
Preemption
Queuing
Low-Rate Access of the PS BE Service
IAC for Emergency Calls
6.1 IAC Overview

Figure 6.1.1.I.1.1.1 shows a typical procedure of service access control.
Figure 6.1.1.I.1.1.1 Service access control procedure
As shown in Figure 6.1.1.I.1.1.1, the procedure of service access includes the procedures for
RRC connection setup and RAB setup. The successful setup of the RRC connection is one of
the prerequisites for the RAB setup.
During the RRC connection processing, the RNC 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:
Performs inter-frequency DRD to select a suitable cell for service steering or load
balancing.
Performs rate negotiation according to the service requested by the UE.
Makes cell resourcebased admission decision. If the admission is successful, UE access

is granted. Otherwise, the RNC performs the next step.
Selects a suitable cell, according to the inter-frequency DRD algorithm, from the cells
where no admission attempt has been made, and then goes to 2. If the attempt fails, the
RNC performs the next step.
selects a suitable cell, according to the inter-RAT DRD algorithm. If the inter-RAT
access is successful, UE access in the inter-RAT cell. If the inter-RAT DRD fails or is not
supported, the RNC performs the next step.
Makes a preemption attempt. If the preemption is successful, UE access is granted. If the

preemption fails or is not supported, the RNC performs the next step.
Makes a queuing attempt. If the queuing is successful, UE access is granted. If the

queuing fails or is not supported, the RNC performs the next step.
Performs low-rate access. If the low-rate access is successful, UE access is granted. If

the low-rate access is unsuccessful, the RNC performs the next step.
Rejects UE access.
After the admission attempts of an HSPA service request fail in all candidate cells, the service falls
back to the DCH. Then, the service reattempts to access the network.
Queui
ng
DRD
Target Rate
Negotiation
InterFrequency
Inter-RAT
LowRate
Access
Rate Negotiation
GBR
Negotiation
Preempti
on
Initial Rate
Negotiation
Servic
e Type
MBR
Negotiation
Table 6.1.1.I.1.1.1.1 IAC procedure supported by services
DCH
HSUPA
HSDPA
In the previous table, MBR stands for maximum bit rate.

For details about CAC, see 7"Call Admission Control Algorithm."
6.2 IAC During RRC Connection Setup

Before a new service is admitted to the network, an RRC connection must be set up.
During the RRC connection setup, the RRC redirection for service steering algorithm is used
for service steering and load sharing between inter-frequency or inter-RAT cells.
When the resources of a cell for UE access are insufficient, the RNC instructs the UE to an
inter-frequency or inter-RAT cell through DRD or redirection to increase the access rate.
Figure 6.2.1.I.1.1.1 RRC connection setup procedure
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.
1 RRC Redirection for Service Steering

This algorithm is not applicable to combined services.
The switch of RRC redirection for service steering can be set through the DR_ RRC_DRD_SWITCH
subparameter of the DrSwitch parameter.
During the RRC connection setup, the RNC implements service steering between interfrequency 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:
2.
The RNC obtains the information about the service requested by the UE and the
capability of the UE.
3.
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.
4.
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.
5.
Based on the cell load and the redirection factors, the RNC decides whether to perform
RRC redirection for service steering.
6.
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.
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.
6.2.2 RRC DRD

If the DR_ RRC_DRD_SWITCH subparameter of the DrSwitch parameter is set to 0, the
RNC performs RRC redirection without performing RRC DRD. Otherwise, the RNC
performs the following steps:
1
The RNC selects intra-band inter-frequency neighboring cells of the current cell. These
neighboring cells are suitable for blind handovers.
1.
The RNC generates a list of candidate DRD-supportive inter-frequency cells. The quality
of the candidate cell meets the requirements of inter-frequency DRD:
Here:
is the cached CPICH Ec/N0 value included in the RACH
measurement report.
2.
3.
is the DRD threshold (DRDEcN0Threshhold).
The RNC selects a target cell from the candidate cells for UE access. If the candidate cell
list contains more than one cell, the UE tries a cell randomly.
If the admission is successful, the RNC initiates an RRC DRD procedure.
If the admission to a cell fails, the UE tries admission to another cell in the candidate
cell list. If all the admission attempts fail, the RNC makes an RRC redirection
decision.
If the candidate cell list does not contain any cell, the RRC DRD fails. The RNC
performs the next step, that is, RRC redirection.
6.2.3 RRC Redirection After DRD Failure

When the RRC DRD fails, the associated RRC connection fails to be set up if the DR_
RRC_DRD_SWITCH subparameter of the DrSwitch parameter is set to 0 or if the switch of
RRC redirection after DRD failure (ConnectFailRrcRedirSwitch) is set to OFF. Otherwise,
the RNC performs the following steps when the RRC DRD fails:
1
The RNC selects all intra-band inter-frequency cells of the local cell.
1.
The RNC selects candidate cells. The candidate cells are the cells selected in step 1 but
exclude the cells that have carried out inter-frequency RRC DRD attempts.
2.
If more than one candidate cell is available, the RNC selects a cell randomly and
redirects the UE to the cell.
3.
If no candidate cell is available,
If the switch of RRC redirection after DRD failure is set to

Only_To_Inter_Frequency, the RRC connection setup fails.
If the switch of RRC redirection after DRD failure is set to Allowed_To_Inter_RAT,

then:
a.If a neighboring GSM cell is configured, the RNC redirects the UE to that GSM
cell.
b.If no neighboring GSM cell is configured, the RRC connection setup fails.
6.3 Rate Negotiation

Rate negotiation includes MBR negotiation, GBR negotiation, initial rate negotiation, and
target rate negotiation.
For details about AMR and AMR-WB speech services in the CS domain, see the Rate Control
Parameter Description.
6.3.1 PS MBR Negotiation

If the IE "Alternative RAB Parameter Values" is present in the RANAP RAB ASSIGNMENT
REQUEST or the RELOCATION REQUEST message when a PS service is set up,
reconfigured, or admitted, then the RNC and the CN negotiate the rate according to the UE
capability to obtain the MBR while ensuring a proper QoS.
For the PS streaming service, when PS_STREAM_IU_QOS_NEG_SWITCH is set to

1, the Iu QoS negotiation function is enabled for MBR negotiation.
For the PS BE service:
When both PS_BE_IU_QOS_NEG_SWITCH and

PS_BE_STRICT_IU_QOS_NEG_SWITCH are set to 1, the Iu QoS negotiation
function is enabled, and the RNC determines the MBR of Iu QoS negotiation based
on the information about UE capability, cell capability and other settings..
When PS_BE_IU_QOS_NEG_SWITCH is set to 1 and

PS_BE_STRICT_IU_QOS_NEG_SWITCH is set to 0, the Iu QoS negotiation
function is enabled, and the RNC determines the MBR of Iu QoS negotiation based
on the maximum rate supported by the UE rather than the cell capability and other
settings.
6.3.2 PS GBR Negotiation

During the setup, reconfiguration, or handover of a real-time PS service, if the RAB
assignment message carries multiple alternative GBRs and
PS_STREAM_IU_QOS_NEG_SWITCH is set to 1, the RNC selects the minimum rate as
the GBR of this RAB and sends it to the CN. If the IE "Type of Alternative Guaranteed Bit
Rate Information" in the message is set to unspecified, the GBR is set to 8 kbit/s.
6.3.3 Initial Rate Negotiation

For a non-real-time service in the PS domain, the RNC selects an initial rate to allocate
bandwidth for the service before the admission request based on cell resources in the
following cases:
A service is set up.
The UE state changes from CELL_FACH to CELL_DCH.
The negotiation is based on the cell load information, which includes:
Uplink and downlink radio bearer status of the cell
Minimum spreading factor (SF) supported
HSPA capability
Initial Rate Definition for DCH Services

For DCH services, the initial rate is defined as follows:
DCCC
Switc
h
PS BE
Initial Rate
Dynamic
Configurati
on Switch
Actual Initial Rate
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 PCPICH 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.
Initial Rate Definition for HSUPA Services

For the HSUPA service, the initial rate is defined as follows:
If HSUPA_DCCC_SWITCH is set to 1, the actual initial rate is the initial rate of the
HSUPA BE service (HsupaInitialRate).
If the HSUPA DCCC function is disabled, the actual initial rate is the MBR.
6.3.4 Target Rate Negotiation

For a non-real-time service in the PS domain, if cell resourcebased admission fails, the RNC
selects a target rate to allocate bandwidth for the service based on cell resource in following
cases:
Service setup
Soft handover
DCCC rate upsizing
If the cell has sufficient code and CE resources, the RNC sets the candidate target rate to the
one that matches the cell resource surplus. Then, the RNC sets the target rate to the greater
one of the candidate target rate and the GBR.
In the case of soft handover, the actual target rate is the candidate target rate set by the RNC.
In the case of DCCC rate upsizing, if the rate upsizing fails, the target rate is the greater one
of the candidate target rate and the pre-upsizing DCCC rate.
6.4 RAB DRD

RAB DRD is used to select a suitable cell for the UE to try an access.
For a single service, RAB DRD can be enabled by the DR_RAB_SING_DRD_SWITCH
subparameter of the DrSwitch parameter.
For combined services, RAB DRD can be enabled by the
DR_RAB_COMB_DRD_SWITCH subparameter of the DrSwitch parameter.
6.4.1 RAB DRD Overview

Through the RAB DRD procedure, the RNC selects a suitable cell for RAB processing during
access control. RAB DRD is of two types: inter-frequency DRD and inter-RAT DRD. Interfrequency DRD is further classified into inter-frequency DRD for service steering and interfrequency DRD for load balancing.
After receiving a Radio Access Network Application Part (RANAP) message RAB
ASSIGNMENT REQUEST, the RNC initiates a RAB DRD procedure to select a suitable cell
for RAB processing during access control.
The basic procedure of RAB DRD is as follows:
1
The RNC performs inter-frequency DRD. According to the purposes of directed retry,
Inter-frequency DRD is of the following types:
Inter-frequency DRD for service steering

For details, see Inter-Frequency DRD for Service Steering.
Inter-frequency DRD for load balancing

For details, see Inter-Frequency DRD for Load Balancing.
1.
If all admission attempts of inter-frequency DRD fail, the RNC performs an inter-RAT
DRD.
For details about inter-RAT DRD, see Inter-RAT DRD.
2.
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.
6.4.2 Inter-Frequency DRD for Service Steering

If the UE requests a service in an area covered by multiple frequencies, the RNC selects the
cell with the highest service priority for UE access, based on the service type of RAB and the
definitions of service priorities in the cells.
The availability of DRD for service steering is specified by the ServiceDiffDrdSwitch
parameter.
"Inter-frequency DRD for service steering" is called "DRD for service steering" for short in this section.
Cell Service Priorities Introduction

Cell service priorities refer to the priorities of cells under the same coverage accepting
specific service types. These priorities help achieve traffic absorption in a hierarchical way.
The priorities of specific service types in cells are configurable. If a cell does not support a
service type, the priority of this service type is set to 0 in this cell. The group of service
priorities in each cell is specified by the service priority group identity (SpgId) parameter.
Service priority groups are configured on the LMT. In each group, priorities of R99 RT
services, R99 NRT services, HSPA services, and other services are defined.
When selecting a target cell for RAB processing, the RNC selects a cell with a high priority,
that is, a cell that has a small value of service priority.
Assume that the service priority groups given in the following table are defined on an RNC.
Cel
l
Service
Priority
Group
Identity
Service
Priority of
R99 RT
Service
Service
Priority of R99
NRT Service
Service
Priority of
HSPA Service
Service
Priority of
Other Service
As shown in Figure 6.4.2.I.1.1.1, 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.
Figure 6.4.2.I.1.1.1 Example of DRD for service steering
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.
Procedure of DRD for Service Steering

This section describes the procedure of DRD for service steering when DRD for load balancing is
disabled.
Figure 6.4.2.I.1.1.1 Procedure of DRD for service steering
The procedure of DRD for service steering is as follows:

1
The RNC determines the candidate cells to which blind handovers can be performed and
sorts the candidate cells in descending order according to service priority.
A candidate cell must meet the following conditions:
2.
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.
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.
6.4.3 Inter-Frequency DRD for Load Balancing

If the UE requests a service setup or channel reconfiguration in an area covered by multiple
frequencies, the RNC sets up the service on a carrier with a light load to achieve load
balancing among the cells on the different frequencies.
"Inter-frequency DRD for load balancing" is called "DRD for load balancing" for short in this section.
Overview of DRD for Load Balancing

Load balancing considers two resources, power, and code.
The availability of DRD for load balancing is specified by the associated parameters as
follows:
The availability of power-based DRD for load balancing for DCH service is specified by
the LdbDRDSwitchDCH parameter.
The availability of power-based DRD for load balancing for HSDPA service is specified
by the LdbDRDSwitchHSDPA parameter.
The availability of code-based DRD for load balancing is specified by the

CodeBalancingDrdSwitch parameter.
In practice, it is recommended that only either a power-based DRD for load balancing or a
code-based DRD for load balancing is activated. If both are activated, power-based DRD for
load balancing takes precedence over code-based DRD for load balancing.
Code-based DRD for load balancing is applicable to only R99 services because HSDPA
services use reserved codes.
Power-Based DRD for Load Balancing

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 nonHSPA 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 HSDSCH 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.4.3.I.1.1.1:
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.
Figure 6.4.3.I.1.1.1 Power-based DRD for load balancing
Figure 6.4.3.I.1.1.2 shows the procedure of power-based DRD for load balancing.
Figure 6.4.3.I.1.1.2 Procedure of power-based DRD for load balancing
The procedure of power-based DRD for load balancing is as follows:

1
The RNC determines the candidate cells to which blind handovers can be performed.
A candidate cell must meet the following conditions:
The frequency of the candidate cell is within the band supported by the UE.
The quality of the candidate cell meets the requirements of inter-frequency DRD.
If the current cell is such a candidate cell, the RNC goes to step 3. Otherwise, the RNC
selects a cell with the lightest load from the candidate cells as the target cell and then
goes to step 2.
The RNC determines whether the DL radio load of the current cell is lower than the
threshold of power-based DRD for load balancing (condition 1). Based on the bearer
type (DCH or HSDPA) of the requested service, the RNC selects an appropriate
condition.
For algorithm 1, condition 1 is as follows:

a. For DCH bearer
Thd
Pnon H ,cutcell Thd non H
AMR , cutcell
b. For HSDPA bearer
Thd
total , cutcell
PGBP ,cutcell Thd H
For algorithm 2, condition 1 is as follows:

a. For DCH bearer
Thd
AMR , cutcell
PD ENU ,cutcell Thd non H
b. For HSDPA bearer
Thd
H ue ,cutcell
PH ue ,cutcell / Thd H ue ,cutcell Thd H
Here:
Thd non H
Thd H
is specified by LdbDRDLoadRemainThdDCH.
is specified by LdbDRDLoadRemainThdHSDPA.
If...
Then...
Condition 1 is met
The service tries admission to the current cell. Go to step 3.
Condition 1 is not met
Go to step 2.
2.
The RNC selects a target cell for UE access.

The RNC determines whether any inter-frequency neighboring cell meets the following
condition (condition 2): Based on the bearer type (DCH or HSDPA) of the requested
service, the RNC selects an appropriate condition as follow:
If algorithm 1 is used, condition 2 is as follows:
For an HSDPA service
Thd
Thd
PGBP ,nbcell Thdtotal ,cutcell PGBP ,cutcell Thd H ,loadoffset
total , cutcell
Pload ,cutcell Thd total , nbcell Pload ,nbcell Thd total ,loadoffset
For a DCH service
Thd
Thd
total , nbcell
AMR , nbcell
total , cutcell
Pnon H , nbcell Thd AMR , cutcell Pnon H ,cutcell Thd D , loadoffset
Pload ,cutcell Thd total , nbcell Pload ,nbcell Thd total ,loadoffset
If algorithm 2 is used, condition 2 is as follows:
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
For a DCH service
Thd
AMR , nbcell
PD enu , nbcell Thd AMR , cutcell PD enu ,cutcell Thd D , loadoffset
The related variables are described as follows:

Current
cell
Inter-frequency
Neighboring
Cell
Description
Thdtotal ,cutcell
Thdtotal , nbcell
DL total power threshold

(DlCellTotalThd)
PGBP ,cutcell
PGBP , nbcell
HS-DSCH GBP
Total power load, which is the sum of the
non-HSDPA power and the GBP
Pnon H , cutcell
Pnon H , nbcell
Non-HSDPA power load
Thd AMR , cutcell
Thd AMR ,nbcell
DL threshold of conversational AMR

service (DlConvAMRThd)
Thd H ue, cutcell
Thd H ue, nbcell
Maximum number of HSDPA users

(MaxHsdpaUserNum)
PH ue , cutcell
PH ue , nbcell
Total number of HSDPA users
PD enu , cutcell
PD enu ,nbcell
DCH ENU load
Thd H ,loadoffset
Load balancing DRD offset for HSDPA

(LdbDRDOffsetHSDPA)
Thd D ,loadoffset
Load balancing DRD offset for DCH

(LdbDRDOffsetDCH)
Thd total ,loadoffset
Load balancing DRD total power protect

threshold (LdbDRDTotalPwrProThd)
Then, the RNC selects the target cell as follows:
If there is only one inter-frequency neighboring cell that meets the conditions of DRD
for load balancing, the RNC selects this cell as the target cell. If there are multiple such
cells:
For a DCH service

a.If algorithm 1 is used, the RNC selects the cell with the lightest non-HSDPA load as
the target cell.
b.If algorithm 2 is used, the RNC selects the cell with the lightest load of DCH ENU
as the target cell.

a.If algorithm 1 is used, the RNC selects the cell with the lightest load of HS-DSCH
required power as the target cell.
b.If algorithm 2 is used, the RNC selects the cell with the lightest load of HSDPA
user as the target cell.
If there is no such cell, the RNC selects the current 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 admits the service request.
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.
Code-Based DRD for Load Balancing

The procedure of DRD for load balancing based on code resource is similar to that based on
power resource.
Figure 6.4.3.I.1.1.1 shows the procedure for selecting a target cell based on code resource.
Figure 6.4.3.I.1.1.1 Procedure of code-based DRD for load balancing
The procedure is as follows:

1
The RNC determines whether the minimum remaining SF of the current cell is smaller
than
the
minimum
SF
threshold
of
DRD
for
code
balancing
(CodeBalancingDrdMinSFThd).
If the minimum SF is smaller than this threshold, the RNC tries the admission of the
service request to the current cell.
If the minimum SF is not smaller than this threshold, the RNC goes to the next step.
2.
The RNC determines whether the code load of the current cell is lower than the code
occupation
rate
threshold
of
DRD
for
code
balancing
(CodeBalancingDrdCodeRateThd).
If the code load is lower than this threshold, the service tries the admission to the current
cell.
If the code load is higher than or equal to this threshold, the RNC selects the cell with the
lightest load or the current cell as the target cell. The RNC selects the cell as follows:
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.
6.4.4 Inter-Frequency DRD

Relation Between DRD for Service Steering and DRD for Load
Balancing
"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.4.4.I.1.1.1 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.
Cell
Value of Service Priority of R99 Real-Time Service
UTRAN f1
UTRAN f2
UTRAN f3
UTRAN f4
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.4.4.I.1.1.1.
Figure 6.4.4.I.1.1.1 Example of inter-frequency DRD
Inter-Frequency DRD Procedure

If the UE requests a service in an area covered by multiple frequencies, the RNC selects a
suitable cell for access based on the service priority in each candidate cell and the service
type. In addition, during cell selection, the RNC checks whether DRD for service steering and
DRD for load balancing are enabled. Figure 6.4.4.I.1.1.1 shows the procedure.
Figure 6.4.4.I.1.1.1 Inter-frequency DRD procedure
The procedure of inter-frequency DRD is as follows:
If DRD for service steering is enabled but DRD for load balancing is disabled, as shown
in A in Figure 6.4.4.I.1.1.1, the inter-frequency DRD procedure is the procedure of DRD
for service steering. For details, see Inter-Frequency DRD for Service Steering.
If DRD for load balancing is enabled but DRD for service steering is disabled, as shown
in B in Figure 6.4.4.I.1.1.1, the inter-frequency DRD procedure is the procedure of DRD
for load balancing. For details, see Inter-Frequency DRD for Load Balancing.
If both DRD for load balancing and DRD for service steering are disabled:
1
The UE attempts to access the current cell when its service priority is not 0. If the
service priority of the current cell is 0, the UE attempts to access another candidate
cell whose service priority is not 0.
2.
The CAC algorithm makes an admission decision based on the cell status.
If the admission attempt is successful, the RNC admits the service
request.
If the admission attempt fails, the UE attempts to access another
candidate cell randomly.
3.
If any request for access to a candidate cell is rejected, 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.
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 frequency of the candidate cell is within the band supported by the
UE.
The quality of the candidate cell meets the requirements of interfrequency DRD.
4.
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.
5.
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 interfrequency 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."
6.4.5 Inter-RAT DRD

When all admission attempts for inter-frequency DRD during RAB processing fail, the RNC
determines whether to initiate an inter-RAT DRD.
Figure 6.4.5.I.1.1.1 shows the inter-RAT DRD procedure.
Figure 6.4.5.I.1.1.1 Inter-RAT DRD procedure
The inter-RAT DRD procedure is as follows:

1
If the current cell is configured with any neighboring GSM cell suitable for blind
handover, and if the "service handover" IE that is contained in the RAB assignment
signaling assigned by the CN is set to "handover to GSM should be performed", then the
RNC performs step 2. Otherwise, the service request undergoes preemption and queuing.
2.
The RNC generates a list of candidate DRD-supportive inter-RAT cells that fulfill the
following requirement:
Here:
is the cached CPICH Ec/N0 value included in the RACH
measurement report.
is the DRD threshold (DRDEcN0Threshhold).
If the candidate cell list does not include any cell, the service request undergoes
preemption and queuing.
3.
The RNC selects target GSM cells for the service request according to the blind
handover priority.
4.
If all admission attempts fail or the number of inter-RAT handover retries exceeds the
value of DRMaxGSMNum, the service request undergoes preemption and queuing.
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.5.1.I.1.1.1.1 describes the selection of the target cell for preemption or
queuing.
Table 6.5.1.I.1.1.1.1 Selection of the target cell for preemption or queuing
DRD
Switch
for
Servic
e
Steeri
ng
PowerBased DRD
Switch for
Load
Balancing
CodeBased
DRD
Switch for
Load
Balancing
Target Cell for Preemption or

Queuing
ON
ON
ON
The cell with the lightest load among the

cells with the highest service priority.
OFF
OFF
The cell with the highest service priority.

If there are multiple such candidate cells,
the target cell is selected as follows:
If the current cell is one of the candidate
cells, the current cell is selected as the
target cell.
Otherwise, a neighboring cell that
supports blind-handover is selected
randomly from the candidate cells.
OFF
ON
ON
The cell that supports the service and has

the lightest load. If there are multiple such
candidate cells, the target cell is selected
DRD
Switch
for
Servic
e
Steeri
ng
PowerBased DRD
Switch for
Load
Balancing
CodeBased
DRD
Switch for
Load
Balancing
Target Cell for Preemption or

Queuing
as follows:
If the current cell is one of the candidate
cells, the current cell is selected as the
target cell.
Otherwise, a neighboring cell that
supports blind-handover is selected
randomly from the candidate cells.
OFF
OFF
Preferably the current cell. If the current

cell does not support the service, a cell is
selected randomly from the cells that
support this service.
Table 6.5.1.I.1.1.1.2 describes the preemption for different types of service on different
resources.
Table 6.5.1.I.1.1.1.2 Preemption of different types of service on different resources
Service
R99
service
HSDPA
service
HSUPA
service
Resourc
e
Service That Can Be Preempted

R99
Servic
e
HSUPA
Service
HSDPA
Service
R99+HSPA
Combined
Services
Code
Power
CE
Iub
bandwidth
Code
Power
CE
Iub
bandwidth
Code
Power
CE
Service
Resourc
e
Service That Can Be Preempted

R99
Servic
e
HSUPA
Service
HSDPA
Service
R99+HSPA
Combined
Services
Iub
bandwidth
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 procedure is as follows:

1
The preemption algorithm determines the radio link sets to be preempted:

a. Selects SRNC users first. If no user under the SRNC is available, the algorithm selects
users under the DRNC.
b. Sorts the preemptable users by user integrated priority, or sorts the preemptable RABs
by RAB integrated priority.
c. Determines candidate users or RABs.
Only the users or RABs with priorities lower than the RAB to be established are
selected. If PriorityReference is set to Traffic Class and PreemptRefArpSwitch is set
to ON, only the ones with lower priority than the RAB to be established are selected.
This applies to RABs of streaming or BE services.
d. Selects as many users or RABs as necessary in order to match the resource needed by
the RAB to be established. When the priorities of two users or RABs are the same, the
algorithm selects the user or RAB that can release the most resources.
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.6.1.I.1.1.1.1.
Table 6.6.1.I.1.1.1.1 Putting the new request into the queue

If the
queue
is...
Not full
Full
Then the queuing algorithm...
Stamps this request with the request time (T_request).
Puts this request into the queue.
Starts the heartbeat timer if it is not started.
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.
6.7 Low-Rate Access of the PS BE Service

If the PS_BE_EXTRA_LOW_RATE_ACCESS_SWITCH subparameter of the PsSwitch
parameter is set to 1, the PS BE service can access the target cell at a low rate in the case of a
preemption or queuing failure to increase the access success rate. Low-rate access means
access from the DCH at 0 kbit/s, FACH, or enhanced FACH (E-FACH).
Low-rate access is used in the following scenarios:
RAB setup
Hard handover or relocation
After a service request is rejected, the low-rate access actions in different scenarios are as
follows:
Scenar
io
Scenario Description
FACH/E_FAC
H
DCH at 0
kbit/s
RAB
setup
The RRC connection is set up on the

FACH or E-FACH.

DCH.

HSPA channel.
Hard handover or relocation is

performed for the CS+PS combined
services.
(Note 1)
Hard handover or relocation is

performed for the PS+PS combined
services.
The CS service is set up, and a new

PS service is to be set up.
The existing PS service is set up on

the FACH/E-FACH, and a new PS
service is to be set up.

the DCH, and a new PS service is to
be set up.

the HSPA channel, and a new PS
service is to be set up.
(Note 2)
The PS service is set up, and a new

CS service is to be set up.
Combine
d services
Note 1: In this scenario, only the PS service can be admitted at 0 kbit/s.
Note 2: In this scenario, the new PS service can be admitted at 0 kbit/s, and the existing service are not
affected.
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.
6.8 IAC for Emergency Calls

To guarantee successful access of emergency calls, the RNC takes special measures for
emergency calls.
6.8.1 RRC Connection Setup Process of Emergency

Calls
Compared with the RRC connection setup process of ordinary services, the RRC connection
setup process of emergency calls incorporates the preemption due to hard resourcebased
admission failure. Hard resources include code, Iub, and CE resources. Figure 6.8.1.I.1.1.1
shows the RRC connection setup process of an emergency call.
Figure 6.8.1.I.1.1.1 RRC connection setup process of an emergency call
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."
6.8.2 RAB Process of Emergency Calls

Compared with the RAB process of ordinary services, the RAB process of emergency calls
incorporates special processing of resource-based admission and preemption.
RAB Admission of Emergency Calls

In case of power resources:
If the CAC algorithm is enabled, regardless of which algorithm is selected, the admission
decision-making is as follows:
When the EMC_UU_ADCTRL subparameter of the NBMCacAlgoSwitch

parameter is set to 1, power-based admission fails if the system is in the overload
congestion state. Otherwise, the admission succeeds.
When this subparameter is set to 0, the emergency calls are directly admitted.
If the CAC algorithm switch is off, the emergency calls are directly admitted.
For hard resources (that is, code, Iub, and CE), the resource-based admission is successful if
the current remaining resources are sufficient for the request.
Preemption of Emergency Calls

If cell resourcebased admission fails, preemption is performed regardless of whether the
preempt algorithm is enabled or not. The emergency calls that trigger preemption have 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."
Call Admission Control

Algorithm
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.
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
7.1 CAC Overview

The CAC algorithm consists of CAC based on code resource, CAC based on power resource,
CAC based on NodeB credit resource, CAC based on Iub resource, and CAC based on the
number of HSPA users.
A CAC procedure involves admission decision for RRC connection setup request and RAB
admission decision.
Figure 7.1.1.I.1.1.1 shows the basic procedure of resource-based admission decision.
Figure 7.1.1.I.1.1.1 Basic procedure of resource-based admission decision
The admission decision is based on:
Available cell code resource
Available cell power resource
NodeB resource state, that is, NodeB credits, which are used to measure the channel
demodulation capability of NodeBs
Available Iub transport layer resource, that is, Iub transmission bandwidth
Number of HSDPA users (only for HSDPA services)
Number of HSUPA users (only for HSUPA services)
A call can be admitted only when all of these resources are available.
Except the mandatory code and Iub resourcebased admission control, the admission control
based on any other resource can be disabled through the ADD CELLALGOSWITCH
command.
Some CAC algorithm switches are set by the NBMCacAlgoSwitch parameter.
Power-based admission decision switches are set by the NBMUlCacAlgoSelSwitch and
NBMDlCacAlgoSelSwitch parameters.
7.2 CAC Based on Code Resource

When a new service attempts to access the network, code resourcebased admission is
mandatory.
Code resourcebased admission is implemented as follows:
For RRC connection setup requests, the code resourcebased admission is successful if
the current remaining code resource is sufficient for RRC connection setup.
For handover services, the code resourcebased admission is successful if the current
remaining code resource is sufficient for the service.
For other R99 services, the RNC has to ensure that the remaining code does not exceed
the DlHoCeCodeResvSf parameter after admission of the new service.
For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore, the
code resourcebased admission is not required.
For details about HSDPA code allocation, see the HSDPA Parameter Description.
7.3 CAC Based on Power Resource

7.3.1 Overview
Power-based admission decision involves admission decision for RRC connection setup
request as well as RAB admission decision based on algorithms 1, 2, or 3.
The algorithm switches are set by the NBMUlCacAlgoSelSwitch or
NBMDlCacAlgoSelSwitch algorithm.
To enable the power-based admission control for HSDPA/HSUPA, the HSDPA_UU_ADCTRL or
HSUPA_UU_ADCTRL subparameter must also be set to 1.
Algorithm 1 (ALGORITHM_FIRST): admission decision based on predicted load

increment upon admission of a new service
Based on the current cell load (indicated by the uplink load factor and downlink TCP)
and the predicted load increment due to admission of the new service, the RNC
determines whether the cell load will exceed the threshold upon admitting the new
service. If yes, the RNC rejects the access request. If not, the RNC accepts the access
request.
Algorithm 2 (ALGORITHM_SECOND): admission decision based on the ENU

Depending on the current ENU and the access request, the RNC determines whether the
ENU will exceed the threshold upon admitting a new service. If yes, the RNC rejects the
request. If not, the RNC accepts the request.
Algorithm 3 (ALGORITHM_THIRD): admission decision based on no load increment

upon admission of a new service
This algorithm assumes that load increment upon admission of a new service is 0. Based
on the current cell load (indicated by the uplink load factor and downlink TCP), the RNC
determines whether the cell load will exceed the threshold upon admitting the new
service. If yes, the RNC rejects the access request. If not, the RNC accepts the access
request.
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.
Figure 7.3.1.I.1.1.1 shows the basic procedure of power-based admission decision.

Figure 7.3.1.I.1.1.1 Basic procedure of power-based admission decision
The basic principles of power-based admission decision are as follows:
Four basic load thresholds are used for power-based admission decision. They are:
UL/DL access threshold for handover (UlNonCtrlThdForHo or DlHOThd)
UL/DL threshold of conversational AMR service (UlNonCtrlThdForAMR or

DlConvAMRThd)
UL/DL threshold of conversational non-AMR service (UlNonCtrlThdForNonAMR

or DlConvNonAMRThd)
UL/DL threshold of other services (UlNonCtrlThdForOther or DlOtherThd)
With these thresholds, the RNC defines the proportion of speech service to other services
while ensuring handover preference.
Admission control involves uplink admission control and downlink admission control.
The corresponding admission control switches NBMUlCacAlgoSelSwitch and
NBMDlCacAlgoSelSwitch are independent of each other.
For an intra-frequency handover request, only downlink admission decision is needed.
For a non-intra-frequency handover request, both uplink and downlink decisions are
needed if both uplink CAC and downlink CAC are enabled.
If there is a rate downsizing request, the RNC accepts it directly.

For a rate upsizing request, the RNC makes the decision, as shown in Figure
7.3.1.I.1.1.1.
For a rejected RRC connection setup request, the RNC performs DRD or redirection.
For a rejected service request, the RNC performs preemption or queuing according to the
actual situation.
7.3.2 Admission Decision for RRC Connection Setup

Request
To ensure that the RRC connection setup request is not denied by mistake, tolerance
principles are applied.
The admission decision for RRC connection setup request is as follows:
When power-based admission is based on power or interference (algorithm 1 and

algorithm 3):
For the RRC connection setup request for the reason of emergency call, detach or
registration, direct admission is used.
For the RRC connection setup request for other reasons, the UL or DL OLC trigger
threshold (UlOlcTrigThd or DlOlcTrigThd) is used for admission.
For details about UL and DL OLC trigger thresholds, see 10.1"OLC Triggering."
When power-based admission is based on the ENU (algorithm 2):
For the RRC connection setup request for the reason of emergency call, detach or
registration, direct admission is used.
For the RRC connection setup request for other reasons, the admission decision is
made as follows:
a. When UL_UU_OLC or DL_UU_OLC is set to 1, RRC connection setup request
is rejected when the cell is in the overload congestion state. If the cell is not in the
overload state, the UL or DL OLC trigger threshold is used for power-based
admission.
b. When UL_UU_OLC or DL_UU_OLC is set to 0, the UL or DL OLC trigger
threshold is used for power-based admission.
7.3.3 Power-Based Admission Algorithm 1

Power-based admission decision based on algorithm 1 consists of uplink powerbased
admission decision and downlink power-based admission decision procedures.
Uplink PowerBased Admission Decision for R99 Cells Based on

Algorithm 1
Figure 7.3.3.I.1.1.1 shows the procedure of uplink powerbased admission decision for R99
cells.
Figure 7.3.3.I.1.1.1 Uplink powerbased admission decision for R99 cells
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 uplink load increment UL is determined by the following factors:
Eb/N0 of the new incoming call, which has a positive correlation with the uplink load increment
UL neighbor interference factor, which has a positive correlation with the uplink load increment
Active Factor (AF) of the new incoming call, which has a positive correlation with the uplink load
increment, and varies with the traffic class, user priority level, and carrier type (DCH or HSPA)
4.
By comparing the predicted uplink load factor UL,predicted with the corresponding threshold
(UlNonCtrlThdForHo, UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, or
UlNonCtrlThdForOther), the RNC decides whether to accept the access request. If the
access request is accepted, the RNC processes the access request. If the access request is
rejected, the RNC performs the next step.
5.
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.
Uplink PowerBased Admission Decision for HSPA Cells Based on

Algorithm 1
The power increment of an HSUPA service is related to the following factors:
Ec/N0 of the GBR of the service
Neighboring interference factor
AF of the service
The formula is similar to that for R99. After the RSEPS measurement is introduced, the UL
RTWP is divided into two parts: controllable part and uncontrollable part. The controllable
part is generated by the E-DCH scheduling service, and others belong to the uncontrollable
part. Figure 7.3.3.I.1.1.1 shows the uncontrollable part of the UL RTWP.
Figure 7.3.3.I.1.1.1 Uncontrollable part of the UL RTWP
The E-DCH scheduling service involves the following types of UEs:
Type A: UEs of this type are in the serving E-DCH cell.
Type B: UEs of this type are not in the serving E-DCH cell.
The methods of calculating the uplink load vary according to user type.
For type A, the uplink load generated by the E-DCH scheduling service is calculated as
follows:
UL , EDCH , S
RSEPS
RTWP
For type B, the uplink load generated by the E-DCH scheduling service is calculated
through
, which is set to 0.
The uplink uncontrollable load is calculated as follows:
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.
The IMS signaling service over HSUPA can be directly admitted.
For the first HSUPA service accessing the cell, the decision formulas that involve PBR are regarded
as unsatisfied.
If the PBR measurement is deactivated, the decision formulas that involve PBR are regarded as
unsatisfied.
If the RSEPS measurement is deactivated, the admission algorithm automatically changes into
algorithm 2.
For details about the scheduling mode of services on HSUPA, see the Radio Bearer Parameter
Description.
Admission of DCH Services

Uncontrollable interference must be kept within a certain range. The purpose is to ensure
the stability of the system and to prevent non-scheduling services and DCH services
from seizing the resources of HSUPA services. In this regard, the CAC algorithm
combines the uncontrollable partbased decision and the total loadbased decision.
When the admission of DCH services is implemented, the following formulas apply:
Here:
is the UL total power threshold of the current cell (UlCellTotalThd).
is the cell UL admission threshold for a specific type of service. The threshold
thd
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.
Downlink PowerBased Admission Decision for R99 Cells Based on

Algorithm 1
Figure 7.3.3.I.1.1.1 shows the procedure of downlink powerbased admission decision.
Figure 7.3.3.I.1.1.1 Downlink powerbased admission decision procedure
The procedure of downlink powerbased admission decision is as follows:

1
The RNC obtains the cell downlink TCP and calculates the downlink load factor DL by
dividing the maximum downlink transmit power Pmax by this TCP.
2.
The RNC calculates the downlink load increment DL based on the service request and
the current load.
3.
The RNC uses the following formula to predict the downlink load factor:
DL,predicted = DL + DL + DLcch
In the formula, DLcch is the percentage of reserved DL common channel load
(DlCCHLoadRsrvCoeff).
4.
By comparing the downlink load factor DL,predicted with the corresponding threshold
(DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, and DlHOThd), the RNC
decides whether to accept the access request.
The downlink load increment DL is determined by the following factors:
Eb/N0 of the incoming new call, which has a positive correlation with the downlink load increment
Non-orthogonal factor, which has a positive correlation with the downlink load increment
Current TCP, which has a negative correlation with the downlink load increment
Active Factor (AF) of the incoming new call, which has a positive correlation with the downlink
load increment
Downlink PowerBased Admission Decision for HSPA Cells Based on

Algorithm 1
Power Increment Estimation for DCH RAB

The power increment estimation for the DCH RAB in the HSPA cell is similar to the
DCH RAB in the R99 cell.
Power Increment Estimation for HSDPA RAB

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 current non-HSPA power.
is the power reserved for the common channel.
is the maximum transmit power of the cell.

is the cell DL admission threshold for a specific type of service.
The threshold may be DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, and

DlHOThd.
is the current downlink TCP.

is the threshold of the total DL power of the cell (DlCellTotalThd).
is the minimum power required to ensure the GBR.
is the power reserved for HSUPA downlink control channels (E-AGCH/ERGCH/E-HICH).
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:
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 provided bit rate of all existing streaming services.

is the admission threshold for streaming PBR decision
(HsdpaStrmPBRThd).
is the provided bit rate of all existing BE services.

is the admission threshold for BE PBR decision (HsdpaBePBRThd).
is the minimum power required to ensure the GBR.
is the power reserved for HSUPA downlink control channels (E-AGCH/ERGCH/E-HICH).
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.
is the maximum transmit power of the cell.
is the threshold of total DL power of the cell, which is specified by the

DlCellTotalThd parameter.
is the power reserved for the common channel.

is the current non-HSPA power.
The RNC admits the HSDPA streaming RAB in any of the following situations:
The RNC admits the HSDPA BE RAB in any of the following situations:
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.

When the uplink CAC algorithm or the downlink CAC algorithm uses algorithm 2, the
admission of uplink/downlink power resources uses the algorithm depending on the ENU.
Equivalent Number of Users

The 12.2 kbit/s AMR traffic is defined as one ENU, which stands for Equivalent Number of
Users. Thus, the 12.2 kbit/s AMR traffic can be used to calculate the ENU of all other
services. The calculation is related to the following factors:
Cell type, such as urban or suburban
Traffic domain, CS or PS
Coding type, turbo code or 1/2 1/3 convolutional code
Traffic QoS, that is, Block Error Rate (BLER)
Table 7.3.4.I.1.1.1.1 describes the typical ENU of some services.

Table 7.3.4.I.1.1.1.1 Typical ENU (with activity factor to be 100%)
Service
ENU
Uplink for
DCH
Downlink for
DCH
HSDP
A
HSUP
A
3.4 kbit/s SIG
0.44
0.42
0.28
1.76
13.6 kbit/s SIG
1.11
1.11
0.74
1.89
3.4+12.2 kbit/s
1.44
1.42
3.4+8 kbit/s (PS)
1.35
1.04
0.78
2.26
Service
ENU
Uplink for
DCH
Downlink for
DCH
HSDP
A
HSUP
A
3.4+16 kbit/s (PS)
1.62
1.25
1.11
2.37
3.4+32 kbit/s (PS)
2.15
2.19
1.70
2.60
3.4+64 kbit/s (PS)
3.45
3.25
2.79
3.14
3.4+128 kbit/s (PS)
5.78
5.93
4.92
4.67
3.4+144 kbit/s (PS)
6.41
6.61
5.46
4.87
3.4+256 kbit/s (PS)
10.18
10.49
9.36
6.61
3.4+384 kbit/s (PS)
14.27
15.52
14.17
9.36
In Table 7.3.4.I.1.1.1.1, for a 3.4+n kbit/s service of HSDPA or HSUPA,
3.4 kbit/s is the rate of the signaling carried on the DCH.
n kbit/s is the GBR of the service.
Procedure of ENU Resource Decision for Uplink/Downlink

The procedure of ENU resource decision for uplink/downlink is as follows:
1
The RNC obtains the total ENU of all existing users ENUtotal = all_exist_userENUi.
1.
The RNC gets the ENU of the new incoming user ENUnew.
2.
The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU load, where
ENUmax
is
the
configured
maximum
ENU
(UlTotalEqUserNum
or
DlTotalEqUserNum).
3.
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:
Service
Type
Admission Threshold
UL
DCH/HSUPA
UL threshold of conversational AMR service

(UlNonCtrlThdForAMR)
UL threshold of conversational non-AMR service
(UlNonCtrlThdForNonAMR)
UL threshold of other services (UlNonCtrlThdForOther)
UL access threshold for handover (UlNonCtrlThdForHo)
DL DCH
DL threshold of conversational AMR service (DlConvAMRThd)

DL threshold of conversational non-AMR service
(DlConvNonAMRThd)
DL threshold of other services (DlOtherThd)
DL access threshold for handover (DlHOThd)
HSDPA
DL total power threshold (DlCellTotalThd)
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.

Algorithm 3 is similar to algorithm 1. The difference is that the estimated load increment in
algorithm 3 is always set to 0.
In accordance with the current cell load (uplink load factor and downlink TCP), the RNC
determines whether the cell load will exceed the threshold, with the estimated load increment
set to 0. If yes, the RNC rejects the request. If not, the RNC accepts the request.
7.4 CAC Based on NodeB Credit Resource

When a new service accesses the network, NodeB credit resourcebased admission is
optional.
7.4.1 NodeB Credit

CE is used to measure the channel demodulation capability of the NodeBs. On the RNC side,
it is referred to the NodeB credit. On the NodeB side, it is the channel element.
The resource of one equivalent 12.2 kbit/s AMR voice service, including 3.4 kbit/s signaling
on the Dedicated Control Channel (DCCH), is defined as one CE. If there is only 3.4 kbit/s
signaling on the DCCH, one CE is consumed. Channel elements provide either uplink or
downlink capacity for services. There are two kinds of CE. One is uplink CE supporting
uplink services, and the other is downlink CE supporting downlink services. Therefore, one
12.2 kbit/s AMR voice service consumes one uplink CE and one downlink CE.
The principles of NodeB creditadmission control are similar to those of power-based
admission control, that is, to check in the local cell, local cell group (if any), and NodeB
whether the remaining credit can support the requesting services.
For details about local cell, local cell group, and capacity consumption law, refer to the 3GPP
TS 25.433.
According to the capacity consumption laws of common and dedicated channels, the
Controlling RNC (CRNC) debits the amount of the credit resource consumed from or credits
the amount to the Capacity Credit (CC) of the local cell (or local cell group, if any) based on
the SF. The specific scenarios are the addition, removal, and reconfiguration of the common
and dedicated channels.
If the UL CC and the DL CC are separate, they are maintained separately in the local cell
or local cell group.
If the UL CC and DL CC are not separate, only the global CC is maintained in the local
cell or local cell group.
The consumption laws of CEs and the relation between CE and credit are listed in Table
7.4.1.I.1.1.1.1 and Table 7.4.1.I.1.1.1.2.
For the DCH service, the RNC uses the MBR to calculate the SF and searches Table
7.4.1.I.1.1.1.1 for the number of consumed CEs.
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.4.1.I.1.1.1.2 for the number of consumed CEs.
Table 7.4.1.I.1.1.1.1 Consumption of credits related to SF for the DCH service
Directi
on
Rate
(kbit/s)
SF
Number of CEs
Consumed
Corresponding
Credits Consumed
UL
3.4
25
6
13.6
64
64
16
64
32
32
1.5
64
16
128
10
Directi
on
DL
Rate
(kbit/s)
SF
Number of CEs
Consumed
Corresponding
Credits Consumed
144
10
256
10
20
384
10
20
3.4
25
6
13.6
12
8
12
8
16
12
8
32
64
64
32
128
16
144
16
256
384
Table 7.4.1.I.1.1.1.2 Consumption of credits related to SF for HSUPA services

Directi
on
Rate
(kbit/s)
SF
Number of
CEs
Consumed
Corresponding
Credits
Consumed
UL
64
UL
16
64
UL
32
32
UL
64
32
UL
128
16
UL
144
16
UL
256
UL
384
16
UL
608
16
UL
1450
2SF4
16
32
Directi
on
Rate
(kbit/s)
SF
Number of
CEs
Consumed
Corresponding
Credits
Consumed
UL
2048
2SF2
32
64
UL
2890
2SF2
32
64
UL
5760
2SF2+2SF4
48
96
As listed in Table 7.4.1.I.1.1.1.1 and Table 7.4.1.I.1.1.1.2, 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.
7.4.2 Procedure of Admission Decision Based on

NodeB Credit
When a new service tries to access the network, the admission decision based on NodeB
credit is implemented as follows:
For an RRC connection setup request, the credit resourcebased admission is successful
if the current remaining credit resources of the local cell, local cell group (if any), and
NodeB are sufficient for RRC connection setup.
For a handover service, the credit resourcebased admission is successful if the current
remaining credit resources of the local cell, local cell group (if any), and NodeB are
sufficient for the service.
For other services, the RNC has to ensure that the remaining credit of the local cell, local
cell group (if any), and NodeB does not exceed the value of UlHoCeResvSf (for the
uplink) or DlHoCeCodeResvSf (for the downlink) after admission of the new services.
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.
7.5 CAC Based on Iub Resource

When a new service accesses the network, Iub resourceadmission is mandatory.
For details about resource-based admission at the Iub transport layer, see the Transmission
Resource Management Parameter Description.
7.6 CAC Based on the Number of HSPA Users

7.6.1 CAC of HSDPA Users
When HSDPA_UU_ADCTRL is set to 1, the HSDPA services have to undergo admission
decision based on the number of HSDPA users.
When a new HSDPA service attempts to access the network, the algorithm admits the service
if the following conditions are met:
The number of HSDPA users in the cell does not exceed the maximum value specified by
MaxHsdpaUserNum.
The number of HSDPA users in the NodeB does not exceed the maximum value
specified by NodeBHsdpaMaxUserNum.
Otherwise, the algorithm rejects the service request.
7.6.2 CAC of HSUPA Users

When HSUPA_UU_ADCTRL is set to 1, the HSUPA services have to undergo admission
decision based on the number of HSUPA users.
When a new HSUPA service attempts to access the network, the algorithm admits the service
if the following conditions are met:
The number of the HSUPA users in the cell does not exceed the maximum value
specified by MaxHsupaUserNum.
The number of the HSUPA users in the NodeB does not exceed the maximum value
specified by NodeBHsupaMaxUserNum.
Otherwise, the algorithm rejects the service request.
Intra-Frequency Load
Balancing Algorithm
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.1.1.I.1.1.1 shows the procedure of intra-frequency LDB.
Figure 8.1.1.I.1.1.1 Procedure of intra-frequency LDB
The intra-frequency LDB is described as follows:
If the downlink load of a cell is higher than the cell overload threshold
(CellOverrunThd), it is an indication that the cell is heavily overloaded. In this case, the
transmit power of the P-CPICH needs to be reduced step by step. The step is specified by
the PCPICHPowerPace parameter.
If the current transmit power is equal to the minimum transmit power of P-CPICH
(MinPCPICHPower), the current transmit power is not adjusted.
Because of the reduction in the pilot power, the UEs at the edge of the cell can be handed
over to neighboring cells, especially to those with a relatively light load and with
relatively high pilot power. After that, the downlink load of the cell is lightened
accordingly.
If the downlink load of a cell is lower than the cell underload threshold
(CellUnderrunThd), it is an indication that the cell has sufficient remaining capacity for
more load. In this case, the transmit power of the P-CPICH can be increased step by step
to help lighten the load of neighboring cells. The step is specified by the
PCPICHPowerPace parameter.
If the current transmit power is equal to the maximum transmit power of P-CPICH
(MaxPCPICHPower), the current transmit power is not adjusted.
Load Reshuffling Algorithm
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.
Basic Congestion Triggering
LDR Procedure
LDR Actions
9.1 Basic Congestion Triggering

The basic congestion of a cell can be caused by power resource, code resource, Iub resource,
or NodeB credit resource.
For power resource, the RNC performs periodic measurement and checks whether the cells
are congested. For code, Iub, and NodeB credit resources, the RNC checks whether the cells
are congested when resource usage changes.
9.1.1 Power Resource

Congestion control based on power resource can be enabled through the DL_UU_LDR and
UL_UU_LDR subparameters of the NBMLdcAlgoSwitch parameter.
If the parameter NBMUlCacAlgoSelSwitch / NBMDlCacAlgoSelSwitch is set to
ALGORITHM_SECOND , the load reffuffling algorithm will trigger basic congestion based on
Equivalent Number of Users (ENU). For details about NBMUlCacAlgoSelSwitch /
NBMDlCacAlgoSelSwitch, see 7.3"CAC Based on Power Resource."
Figure 9.1.1.I.1.1.1 shows the triggering and relieving of basic congestion.
Figure 9.1.1.I.1.1.1 Triggering and relieving of basic congestion
For an R99 cell:
If the current UL/DL load of the R99 cell is higher than or equal to the UL/DL LDR
trigger threshold (UlLdrTrigThd or DlLdrTrigThd) for 1,000 ms, the cell is in the
basic congestion state, and the related load reshuffling actions, as listed in Table
9.2.1.I.1.1.1.1, are taken.
If the current UL/DL load of the R99 cell is lower than the UL/DL LDR relief threshold
(UlLdrRelThd or DlLdrRelThd) for 1,000 ms, the cell enters the normal state again.
For an HSPA cell:
In the uplink, the basic congestion decision is based on the comparison between the UL
LDR trigger threshold (UlLdrTrigThd) and the uncontrollable load of the cell.
In the downlink, the basic congestion decision is based on the comparison between the
DL LDR trigger threshold (DlLdrTrigThd) and the sum of the non-HSPA power and the
GBP.
9.1.2 Code Resource

Congestion control based on code resource can be enabled through the CELL_CODE_LDR
subparameter of the NBMLdcAlgoSwitch parameter.
If the SF corresponding to the current remaining code of the cell is larger than the value of
CellLdrSfResThd, code congestion is triggered and the related load reshuffling actions, as
listed in Table 9.2.1.I.1.1.1.1, are taken.
9.1.3 Iub Resource

Congestion control based on Iub resource can be enabled through the IUB_LDR
subparameter of the NodeBLdcAlgoSwitch parameter in the ADD NODEBALGOPARA or
MOD NODEBALGOPARA command.
Iub congestion control in both the uplink and downlink is NodeB-oriented.. In the case of Iub
congestion, LDR actions are applied to congestion resolution. Iub congestion detection is
implemented in a separate processing module. For details about the decision on Iub
congestion detection, see the Transmission Resource Management Parameter Description.
For the basic congestion caused by Iub resource, all UEs under the NodeB are the objects of
related LDR actions.
9.1.4 NodeB Credit Resource

The basic congestion caused by NodeB credit resource is of the following types:
Type A: Basic congestion at local cell level

If the cell UL/DL current remaining SF (mapped to credit resource) is higher than
UlLdrCreditSfResThd or DlLdrCreditSfResThd (set through the ADD CELLLDR
command), credit congestion at cell level is triggered and related load reshuffling actions
are taken in the current cell.
Type B: Basic congestion at local cell group level (if any)
Type C: Basic congestion at NodeB level

If the cell group or NodeB UL/DL current remaining SF (mapped to credit resource ) is
higher than UlLdrCreditSfResThd or DlLdrCreditSfResThd (set through the ADD
NODEBLDR command), credit congestion at cell group or NodeB level is triggered and
related load reshuffling actions are taken. The range of LDR actions is the same as the
first type, but the range of UEs to be sorted by priority is different. All the UEs in the
normal cells that belong to the cell group or NodeB will be sorted.
Table 9.1.4.I.1.1.1.1 lists the LDR switches that need to be set to 1 for different algorithm
types.
Table 9.1.4.I.1.1.1.1 LDR switches to be set to 1
Algorithm

Switch
LDC Algorithm
Switch
Type A
LC_CREDIT_LDR_SWITCH
CELL_CREDIT_LDR
Type B
LCG_CREDIT_LDR_SWITCH
LCG_CREDIT_LDR
Type C
NODEB_CREDIT_LDR_SWITCH
NODEB_CREDIT_LDR
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.
The fourth priority for load reshuffling (LdrFourthPri) is set to UULDR.
Then, the basic congestion is relieved in the following sequence:
LDR based on Iub resource
LDR based on credit resource
LDR based on code resource
LDR based on power resource
The information of cell status can be checked through the DSP CELLCHK command.
9.2 LDR Procedure

The RNC periodically takes actions if the basic congestion is detected.
The following procedures apply to HSPA cells and R99 cells. For R99 cells, only DCH UEs
are selected by LDR actions.
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.2.1.I.1.1.1 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.
Figure 9.2.1.I.1.1.1 LDR procedure
As shown in Figure 9.2.1.I.1.1.1, when the system is congested, the inter-frequency load
handover is initiated first.
If the handover succeeds, the algorithm continues to check whether the system is
congested. If the system is still congested, the inter-frequency load handover is initiated
again.
If the handover fails, code reshuffling is performed:
If the code reshuffling succeeds, the algorithm continues to check whether the system
is congested. If the system is still congested, the code reshuffling is initiated again.
If the code reshuffling fails, the next action, that is, BE rate reduction, is taken.
The rest may be deduced by analogy. For details about LDR actions, see 9.3"LDR Actions."
Table 9.2.1.I.1.1.1.1 describes the LDR actions intended for different resources.
HSUPA
DCH
HSDPA
Load Handover
DL
FACH
(MBMS)
Iub
UL
DCH
HSUPA
DL
DCH
HSDPA
FACH
(MBMS)
Code
DL
DCH
HSDPA
FACH
(MBMS)
Credit
UL
DL
DCH
HSUPA
DCH
HSDPA
FACH
(MBMS)
MBMS Power
Reduction
DCH
Code
Reshuffling
UL
Iu QoS
Renegotiation
Power
AMR Rate
Reduction
LDR Actions
PS Domain Inter-RAT
Handover in
Channel
BE Rate
Reduction
UL/DL
InterFrequency
Resour
ce
CS Domain Inter-RAT
Handover in
Table 9.2.1.I.1.1.1.1 LDR actions intended for different resources
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.2.1.I.1.1.1.1.
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 "InterRAT 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.
9.3 LDR Actions

LDR actions include inter-frequency load handover, BE rate reduction, QoS renegotiation for
uncontrollable real-time services, inter-RAT handover in the CS domain, inter-RAT handover
in the PS domain, AMR rate reduction, code reshuffling, and MBMS power reduction.
9.3.1 Inter-Frequency Load Handover

The inter-frequency load handover algorithm is restricted by the inter frequency hard
handover algorithm switch. Inter-frequency load handover can be performed only when the
inter frequency hard handover algorithm is enabled.
The LDR algorithm performs the following steps:
1.
The algorithm checks whether cells for inter-frequency blind handover are available. If
available, the algorithm goes to the next step. Otherwise, the action fails, and the
algorithm takes the next action.
2.
The algorithm selects the target cell according to the type of resource that causes the
basic congestion:
If the basic congestion is caused by power resource:

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.
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.
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.
9.3.2 BE Rate Reduction

The BE rate reduction algorithm is controlled by the DCCC algorithm switch. BE rate
reduction can only be performed when the DCCC algorithm is enabled.
Different from the TF restriction to the OLC algorithm, the BE rate reduction is implemented
by bandwidth reconfiguration. The bandwidth reconfiguration requires signaling interaction
on the Uu interface. This procedure is relatively long.
In the same environment, different rates have different downlink transmit powers. The higher
the rate, the greater the downlink transmit power. Therefore, the load can be reduced by
bandwidth reconfiguration.
For HSUPA services, the consumption of CEs is based on the bit rate. The higher the rate, the
more the consumption of CEs. Therefore, the consumption of CEs can be reduced by
bandwidth reconfiguration.
The LDR algorithm operates as follows:
1
Based on the integrated priority, the algorithm sorts the RABs in descending order.
The algorithm selects the RABs with the lowest integrated priorities and with the current
rate higher than the GBR specified through the SET USERGBR command for related to
the BE services. If the integrated priorities of some RABs are identical, the RAB with
the highest rate is selected. The number of selected RABs is specified by the
UlLdrBERateReductionRabNum or DlLdrBERateReductionRabNum parameter.
If services can be selected, the action is successful. If services cannot be selected, the
action fails. The algorithm takes the next action.
1.
The bandwidth of the selected services is reduced to the specified rate. For details about
the rate reduction procedure, see the Rate Control Parameter Description.
2.
The reconfiguration is completed as indicated by the RADIO BEARER

RECONFIGURATION message on the Uu interface and through the synchronized radio
link reconfiguration procedure on the Iub interface.
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.
9.3.3 QoS Renegotiation for Uncontrollable Real-Time

Services
Uncontrollable real-time services refer to PS streaming services.
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.
Based on the integrated priority, the algorithm sorts the RABs for real-time services in
the PS domain in descending order.
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.
1.
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.
2.
The RNC initiates the RAB MODIFY REQUEST message to the CN for the QoS
renegotiation.
3.
If the RNC cannot find an appropriate service for the QoS renegotiation, the action fails.
The algorithm takes the next action.
9.3.4 Inter-RAT Handover in the CS Domain

The action is restricted by the CS inter-RAT handover algorithm switch. This action can only
be performed when the CS inter-RAT handover algorithm is enabled.
The size and coverage mode of a 2G cell are different from those of a 3G cell. Therefore,
inter-RAT blind handover is not considered.
Inter-RAT handover in the CS domain involves the following actions:
Inter-RAT Should Be Load Handover in the CS Domain

1.
Based on the integrated priority, the algorithm sorts the UEs with the "service handover"
IE set to "handover to GSM should be performed" in the CS domain in descending order.
2.
The algorithm selects the UEs with the lowest integrated priorities. The number of
selected UEs is specified by the UlCSInterRatShouldBeHOUeNum or
DlCSInterRatShouldBeHOUeNum parameter.
3.
For the selected UEs, the LDR module sends the load handover command to the interRAT handover module to ask the UEs to be handed over to the 2G system.
4.
The handover module decides to trigger the inter-RAT handover, depending on the
capability of the UE to support the compressed mode.
5.
If a UE that satisfies the handover criteria is not found, the algorithm takes the next
action.
Inter-RAT Should Not Be Load Handover in the CS Domain

The algorithm for this action is the same as that for the action "Inter-RAT Should Be
Load Handover in the CS Domain". The difference is that this action only involves CS
users with the "service handover" IE set to "handover to GSM should not be performed".
The number of selected UEs is specified by the UlCSInterRatShouldNotHOUeNum or
DlCSInterRatShouldNotHOUeNum parameter.
9.3.5 Inter-RAT Handover in the PS Domain

The action is restricted by the PS inter-RAT handover algorithm switch. This action can only
be performed when the PS inter-RAT handover algorithm is enabled.
Inter-RAT handover in the PS domain involves the following actions:
Inter-RAT Should Be Load Handover in the PS Domain
The algorithm for this action is the same as that for the action "Inter-RAT Should Be
Load Handover in the CS Domain". The difference is that this action involves only PS
users with the "service handover" IE set to "handover to GSM should be performed".
The number of controlled UEs is determined by the UlPSInterRatShouldBeHOUeNum
or DlPSInterRatShouldBeHOUeNum parameter.
Inter-RAT Should Not Be Load Handover in the PS Domain

The algorithm for this action is the same as that for the action "Inter-RAT Should Not Be
Load Handover in the CS Domain". The difference is that this action involves only PS
users with the "service handover" IE set to "handover to GSM should not be performed".
The number of controlled UEs is specified by the UlPSInterRatShouldNotHOUeNum
or DlPSInterRatShouldNotHOUeNum 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.
9.3.6 AMR Rate Reduction

The action is restricted by the AMRC algorithm switch. This action can only be performed
when the AMRC algorithm is enabled.
In the WCDMA system, voice services work in eight AMR modes. Each mode has its own
rate. Therefore, mode control is functionally equivalent to rate control.
LDR Algorithm for AMR Rate Control in the Downlink

The LDR algorithm operates in the downlink as follows:
1.
2.
The algorithm selects the RABs with the lowest integrated priorities and with the rates
higher than the GBR for AMR services (conversational). The number of selected RABs
is specified by the DlLdrAMRRateReductionRabNum parameter.
3.
The RNC sends the Rate Control request message through the Iu interface to the CN to
adjust the AMR rate to the GBR.
4.
If the RNC cannot find an appropriate RAB for the AMR rate reduction, the action fails.
LDR Algorithm for AMR Rate Control in the Uplink

In the uplink, the LDR algorithm operates as follows:
1.
2.
higher than the GBR for AMR services (conversational). The number of selected RABs
is determined by the UlLdrAMRRateReductionRabNum parameter.
3.
The RNC sends the TFC CONTROL command to the UE to adjust the AMR rate to the
GBR.
4.
If the RNC cannot find an appropriate RAB for the AMR rate reduction, the action fails.
9.3.7 Code Reshuffling

When the cell is in the basic congestion state caused by code resource, code reshuffling can be
performed to reserve sufficient code resources for subsequent services. Code subtree
adjustment refers to the switching of users from one code subtree to another. It is used for
code tree defragmentation, so as to release smaller codes first.
The algorithm operates as follows:
1
Initializes SF_Cur to CellLdrSfResThd.
1.
Traverses all the subtrees with this SF_Cur at the root node except the subtrees occupied
by common channels and HSDPA channels, and takes the subtrees in which the number
of users is not larger than the value of MaxUserNumCodeAdj as candidates for code
reshuffling.
2.
If such candidates are available, the algorithm goes to step 2.
If no such candidate is available, subtree selection fails. This procedure ends.
Selects a subtree from the candidates according to the setting of LdrCodePriUseInd.
If this parameter is set to TRUE, the algorithm selects the subtree with the largest
code number from the candidates.
If this parameter is set to FALSE, the algorithm selects the subtree with the smallest
number of users from the candidates. In the case that multiple subtrees have the same
number of users, the algorithm selects the subtree with the largest code number.
3.
Treats each user in the subtree as a new user and allocates code resources to each user.
4.
Initiates the reconfiguration procedure for each user in the subtree and reconfigures the
channelization codes of the users to the newly allocated code resources.
The reconfiguration procedure on the UU interface is implemented through the
PHYSICAL CHANNEL RECONFIGURATION message and that on the Iub interface
through the RL RECONFIGURATION message.
Figure 9.3.7.I.1.4.1 shows an example of code reshuffling. In this example,

CellLdrSfResThd is set to SF8, and MaxUserNumCodeAdj is set to 1.
Figure 9.3.7.I.1.4.1 Code reshuffling
9.3.8 MBMS Power Reduction

The downlink power load can be reduced by lowering power on MBMS traffic channels.
The algorithm operates as follows:

1.
2.
The algorithm selects a RAB with the lowest integrated priority and with the current
power higher than the minimum transmit power of the corresponding MTCH. That is, it
selects a RAB of which the ARP value is higher than MbmsDecPowerRabThd.
3.
The algorithm triggers a reconfiguration procedure to set the power to the minimum
transmit power of the FACH onto which the MTCH is mapped.
The reconfiguration procedure on the Iub interface is implemented through the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message.
9.3.9 UL and DL LDR Action Combination of a UE

LDR actions in the uplink and the downlink are independent. Sometimes, the actions in both
directions are applied to the same UE. In this situation, the actions are combined as follows:
If the actions in the two directions are identical, the actions are combined. For example,
if BE rate reduction actions in both the uplink and the downlink need to be applied to the
same UE, then only a single RADIO BEARER RECONFIGURATION message is sent
out.
If the actions in the two directions are different and if one direction requires interfrequency handover, the UE undergoes the inter-frequency handover. The other action is
not taken.
If the actions in the two directions are different and if one direction requires the interRAT handover, the UE undergoes the inter-RAT handover. The other action is not taken.
If the action in one direction requires inter-frequency handover, and the action in the
other direction requires inter-RAT handover, the UE undergoes the UL LDR action. The
DL LDR action is not taken.
10
Overload Control
Algorithm
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.
OLC Triggering
General OLC Procedure
OLC Actions
10.1 OLC Triggering

Only the power resource, interference, and Iub bandwidth may result in the overload
congestion state. Hard resources such as the ENU and credit resources do not cause overload
congestion.
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.1.1.I.1.1.1 shows the triggering and release of cell power overload.
Figure 10.1.1.I.1.1.1 Triggering and release of cell power overload
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 nonHSPA 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.
10.2 General OLC Procedure

When the cell is overloaded, the RNC takes one of the following actions in each period
specified by the OlcPeriodTimerLen parameter until the congestion is relieved:
Performing TF Control of BE Services
Switching BE Services to Common Channels
Adjusting the Maximum FACH TX Power
Releasing Some RABs
Figure 10.2.1.I.1.1.1 shows the OLC procedure.

Figure 10.2.1.I.1.1.1 OLC procedure
As shown in Figure 10.2.1.I.1.1.1, the OLC procedure is as follows:

1
When the system is overloaded, the OLC takes the first action to perform TF control. If
the TF control succeeds, the OLC checks whether the system is overloaded. If yes, the
OLC performs TF control again.
If the 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.
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."

when the cell is in the overload congestion state:
The state transition from FACH to DCH is prohibited
whether the admission for users over FACH channels is permitted can be set through
FACH_UU_ADCTRL subparameter of NBMCacAlgoSwitch parameter.
10.3 OLC Actions

The OLC actions of restricting the TF of the BE service, switching BE services to common
channels, and choosing and releasing RABs are supported in the current version.
10.3.1 Performing TF Control of BE Services

OLC Algorithm for TF Control in the Downlink
For the TF control in the downlink, the OLC algorithm operates as follows:
1.
2.
The algorithm selects the following RABs:
DCH RABs with the bit rates higher than DlDcccRateThd for BE services. For
details about the parameter, see the Rate Control Parameter Description.
RABs with the lowest integrated priorities.
The number of RABs selected is smaller than or equal to DlOlcFTFRstrctRabNum.

3.
The RNC sends the TF control indication message to the MAC. Each MAC of the
selected RABs will receive one TF control indication message and will restrict the TFC
selection of the BE services to reduce the data rate step by step.
The MAC restricts the TFC selection according to the following formula:
TFmax(N+1) = TFmax(N) x Ratelimitcoeff
Here:
TFmax(0) is the maximum TB number of the BE service before the service is selected
for TF control.
TFmax(N+1) is the maximum TB number during the period from (T0 +

RateRstrctTimerLen x N) to (T0 + RateRstrctTimerLen x (N + 1)), where T0 is
the time when the MAC receives the TF control indication message.
Ratelimitcoeff is specified by the RateRstrctCoef parameter.
4.
If the RNC cannot find an appropriate service for the TF control or the number of times
that TF control is performed exceeds DlOlcFTFRstrctTimes, the action fails. The OLC
takes the next action.
5.
If the congestion is relieved, the RNC sends the congestion relief indication to the MAC.
At the same time, the rate recovery timer (RateRecoverTimerLen) is started. When this
timer expires, the MAC increases the data rate step by step.
MAC 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.3.1.I.1.5.1 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.
Figure 10.3.1.I.1.5.1 Example of TF control
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.
OLC Algorithm for TF Control in the Uplink

For a UE with the DCH service, the RNC sends a TRANSPORT FORMAT COMBINATION
CONTROL message to the UE to restrict the TFC of the UE, according to the 3GPP
TS25.331. Figure 10.3.1.I.1.1.1 shows the message flow, in which the UE does not have any
response if the procedure can be performed successfully.
Figure 10.3.1.I.1.1.1 TFC control on the Uu interface
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.
higher than UlDcccRateThd. The number of selected RABs is specified by the
UlOlcFTFRstrctRabNum parameter.
2.
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.
3.
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.
4.
If the RNC cannot find an appropriate service, the OLC performs the next action.
10.3.2 Switching BE Services to Common Channels

For switching BE services to common channels, the OLC algorithm operates as follows:
1
Based on the integrated priority, the algorithm sorts all the UEs in the PS domain in
descending order.
The algorithm selects the UEs with the lowest integrated priorities. The number of
selected UEs is specified by TransCchUserNum. If the selection fails, the OLC takes
the next action.
The OLC switches the selected UEs to common channels.
This function is disabled when the TransCchUserNum parameter is set to 0.
For the switching of uplink BE services to common channels, 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.
Whether the selected UEs can be switched to common channels depends on the setting of
PS_BE_STATE_TRANS_SWITCH, HSDPA_STATE_TRANS_SWITCH, or
HSUPA_STATE_TRANS_SWITCH.
10.3.3 Adjusting the Maximum FACH TX Power

The procedure for adjusting the maximum FACH transmit power is as follows:
1.
Set the maximum FACH transmit power to the target maximum transmit power. The
target maximum transmit power is calculated according to the following formula:
Pt arg et Pmax Delta
2.
Pt arg et
Pmax
Delta
is the target maximum transmit power.
is the maximum FACH transmit power (MaxFachPower).

is the FACH power reduction step (FACHPwrReduceValue).
If the congestion is relieved after the power adjustment, the system starts the FACH
power recovery timer, which is set to 5s. When the timer expires, the maximum FACH
transmit power is increased to the original maximum FACH transmit power if the system
is always in the normal state before the timer expires.
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.
10.3.4 Releasing Some RABs

OLC Algorithm for the Release of Some RABs in the Uplink
For the release of some RABs in the uplink, the OLC algorithm operates as follows:
1.
Based on the integrated priority, the algorithm sorts all RABs including HSUPA and
DCH services in descending order.
2.
The algorithm selects the RABs with the lowest integrated priorities. If the integrated
priorities of some RABs are identical, it selects the RAB with a higher rate (that is, the
current rate for DCH RAB or the GBR for HSUPA RAB) in the uplink. The number of
selected RABs is specified by UlOlcTraffRelRabNum.
3.
The selected RABs are released directly.

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.
OLC Algorithm for the Release of Some RABs in the Downlink

For the release of some RABs in the downlink, the OLC algorithm operates as follows:
If the SeqOfUserRel parameter is set to USER_REL, then:
1.
Based on the integrated priority, the algorithm sorts all non-MBMS RABs in descending
order.
2.
The algorithm selects the RABs with the lowest integrated priorities. If the integrated
priorities of some RABs are identical, it selects the RAB with a higher rate (that is, the
current rate for DCH RAB or the GBR for HSDPA RAB) in the downlink. The number
of selected RABs is specified by DlOlcTraffRelRabNum.
3.
The selected RABs are directly released.
4.
If all non-MBMS RABs are released but congestion persists in the downlink, MBMS
RABs are selected.
If the SeqOfUserRel parameter is set to MBMS_REL, then:
5.
Based on the ARP, the algorithm sorts all MBMS RABs in descending order.
6.
The algorithm selects the RABs with the lowest integrated priorities. The number of
selected RABs is specified by MbmsOlcRelNum.
7.
The selected RABs are directly released.
8.
If all MBMS RABs are released but congestion persists in the downlink, non-MBMS
RABs are selected.
The higher the value of UlOlcTraffRelRabNum or DlOlcTraffRelRabNum is, the more

obviously the cell load decreases at the cost of negatively affecting user experience.
This function is disabled when all the UlOlcTraffRelRabNum, DlOlcTraffRelRabNum, and
MbmsOlcRelNum parameters are set to 0.
11
Dynamic Power Sharing

Among Carriers
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.
11.2 Power Sharing Mode

Assume that the NodeB is configured with a power sharing group through the ADD PAGRP
command. In addition, assume that the source cell is an R99 cell, which is specified by the
SLOCELL parameter. The target cell is an HSDPA cell, which is specified by the
DLOCELL parameter. Then, the algorithm periodically calculates the maximum power that
can be shared by the source cell with the target cell according to the following formula:
Psource-share = Max{0,{Min(Pmax Pcurrent, Pmax x Rmax-share) Pmax x Rshare-margin}}
Psource-share denotes the maximum power that can be shared by the source cell with the
target cell.
Pmax denotes the maximum power configured for the source cell. It is specified by the
RlMaxDlPwr parameter.
Pcurrent denotes the power currently used by the source cell.
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
Load Control Parameters
12.1 Description
Table 12.1.1.I.1.1.1.1 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
Parameter ID
Description
control algorithm is valid.
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
Parameter ID
Description
the minimum available SF of a cell is higher than this threshold. The lower the
code resource LDR trigger threshold is, the easier the downlink code resource
enters the initial congestion status, the easier the LDR action is triggered, and the
easier the subscriber perception is affected. But a lower code resource LDR trigger
threshold causes a higher admission success rate because the resource is reserved.
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
ch
This parameter specifies whether the code balancing DRD algorithm will be
applied.
- ON: The code balancing DRD algorithm will be applied.
- OFF: The code balancing DRD algorithm will not be applied.
CodeCongSelInterFreq
HoInd
This switch is valid only when the inter-frequency handover switch is enabled.
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.
Parameter ID
Description
CodeBalancingDrdCode
RateThd
This parameter specifies one of the triggering conditions of code balancing DRD.
(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
HOUeNum
Number of users selected in a DL LDR CS domain inter-RAT SHOULDBE 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.
DlCSInterRatShouldNot
HOUeNum
Number of users selected in a DL LDR CS domain inter-RAT SHOULDNOTBE

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 nonhandover 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
Parameter ID
Description
success rate and improve access priority of handover services. This parameter
defines the quantity of downlink code and CE resources reserved for handover.
DlInterFreqHoCellLoad
SpaceThd
The inter-frequency neighboring cell could be selected as the destination of load

handover only when its load remaining space is larger than this threshold. The
lower the parameter is, the easier it is to find a qualified target cell for the blind
handover. Excessively small value of the parameter, however makes the target cell
easily enter the congestion status. The higher the parameter is, the more difficult it
is for the inter-frequency blind handover occurs.
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
factors.
DlLdrPsRTQosRenegRa
bNum
Number of RABs selected in a DL LDR uncontrolled real-time traffic QoS

renegotiation. The target subscribers of this parameter are the PS domain real-time
Parameter ID
Description
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.
DlLdrAMRRateReducti
onRabNum
The mechanism of the LDR is that an action is performed in each [LDR 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 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
RabNum
Number of RABs selected in a DL LDR BE traffic rate reduction. In the actual

system, this parameter can be set on the basis of the actual circumstances. If the
high-rate subscribers occupy a high proportion, set the parameter to a
comparatively low value. If the high-rate subscribers occupy a low proportion, set
the parameter to a comparatively high value. Because the basic congestion control
algorithm is designed to slowly decrease cell load, you need to set this parameter to
a comparatively low value.
LdbDRDLoadRemainT
hdDCH
This parameter specifies the downlink load threshold to trigger load balancing
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
hdHSDPA
This parameter specifies the downlink load threshold to trigger load balancing
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
m
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.
The mechanism of the OLC is that an action is performed in each [OLC period]
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
Parameter ID
Description
the cell downlink load.
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.
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.
DlPSInterRatShouldBe
HOUeNum
Number of users selected in a DL LDR PS domain inter-RAT SHOULDBE load

handover. The target subscribers of this parameter are the PS domain subscribers.
Parameter ID
Description
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.
DlPSInterRatShouldNot
HOUeNum
Number of users selected in a DL LDR PS domain inter-RAT SHOULDNOTBE

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
RateRecoverTimerLen
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
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
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
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.
NBMDlCacAlgoSelSwi
tch

ALGORITHM_OFF: Disable downlink call admission control algorithm.
ALGORITHM_FIRST: The load factor prediction algorithm will be used in
downlink CAC.
Parameter ID
Description
ALGORITHM_SECOND: The equivalent user number algorithm will be used in
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
PBRThd
Threshold of all the HSUPA user PBR whose schedule priority is the same as that
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
fourth priority.
GoldUserLoadControlS
witch
Indicates whether gold users involve in the switch of congestion control. According
to the policy set for gold users by operators, if service quality of gold users should
be guaranteed even in resource congestion, the switch should be disabled. If the
switch is enabled, LDR such as rate reduction and handover also occurs on gold
users even in cell resource congestion, which impacts user service quality. If the
switch is disabled, no action is performed on gold users.
HsupaHighPriorityUser
PBRThd
Threshold of all the HSUPA user PBR whose schedule priority is higher than that
of users to be admitted. If this value is too high, the possibility of rejecting HSUPA
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
Parameter ID
Description
throughput admission threshold of the HSDPA BE service multiplied by the sum of
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
Parameter ID
Description
quickly. If the parameter value is excessively low, an LDR action may overlap the
previous one before the previous result is displayed in LDM. The higher the
parameter value is, the more likely this problem can be prevented. If the parameter
value is excessively high, the LDR action may be executed rarely, failing to lower
the load timely.
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 interRAT 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 HSDSCH)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
d
This parameter specifies the threshold of the downlink remanent total power
difference between the current cell and the target cell when load balancing DRD is
Parameter ID
Description
applied and the load balancing DRD choice is Power. Only when the downlink
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 pingpong 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
BRThd
Threshold of all the HSUPA user PBR whose schedule priority is lower than that of
users to be admitted. If this value is too high, the possibility of rejecting HSUPA
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
ch
Indicating whether MBMS is supported.
MbmsOlcRelNum
MBMS service release is an extreme method in reducing the cell load and
recovering the system when the cell is overloaded and congested.
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
FThd
This parameter specifies one of the triggering conditions of code balancing DRD.
(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.
Parameter ID
Description
To enable some of the algorithms above, select them. Otherwise, they are disabled.
NodeBHsdpaMaxUserN
um
Maximum number of HSDPA users of the NodeB. If the HSDPA user access is
rejected by the NodeB, you can infer that the HSDPA licenses are insufficient. New
HSDPA licenses are required.
NodeBHsupaMaxUserN
um
Maximum number of HSUPA users of the NodeB. If the HSUPA user access is
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
Parameter ID
Description
TS 25.304.
OffQoffset2Light
Offset of Qoffset2 when neighboring cell load is lighter than that of the center cell
TS 25.304.
OffQoffset2Heavy
Offset of Qoffset2 when neighboring cell load is heavier than that of the center cell
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
second priority.
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
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
LdrThirdPri
third priority.
ChoiceRprtUnitForDlBa
sicMeas
If you set this parameter to TEN_MSEC, use [DL basic meas rprt cycle,Unit:10ms]
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
ChoiceRprtUnitForUlBa
sicMeas
Value range: TEN_MSEC, MIN

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.
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

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
HOUeNum
Number of users selected in a UL LDR CS domain inter-RAT SHOULDBE 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.
UlCSInterRatShouldNot
HOUeNum
Number of users selected in a UL LDR CS domain inter-RAT SHOULDNOTBE

load handover. The target subscribers of this parameter are the CS domain
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 nonhandover 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
SpaceThd
The inter-frequency neighboring cell could be selected as the destination of load

handover only when its load remaining space is larger than this threshold. The
lower the parameter is, the easier it is to find a qualified target cell for the blind
handover. Excessively small value of the parameter, however makes the target cell
easily enter the congestion status. The higher the parameter is, the more difficult it
is for the inter-frequency blind handover occurs.
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
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
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
factors.
UlLdrPsRTQosRenegRa
bNum
Number of RABs selected in a UL LDR uncontrolled real-time traffic QoS

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
onRabNum
The mechanism of the LDR is that an action is performed in each [LDR period]
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
RabNum
Number of RABs selected in a UL LDR BE traffic rate reduction. In the actual

system, this parameter can be set on the basis of the actual circumstances. If the
high-rate subscribers occupy a high proportion, set the parameter to a
comparatively low value. If the high-rate subscribers occupy a low proportion, set
the parameter to a comparatively high value. Because the basic congestion control
algorithm is designed to slowly decrease cell load, you need to set this parameter to
a comparatively low value.
UlOlcFTFRstrctRabNu
m
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
Parameter ID
Description
the cell uplink load.
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
the cell uplink load.
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.
This parameter defines the maximum number of RABs released in executing
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.
UlPSInterRatShouldBe
HOUeNum
Number of users selected in a UL LDR PS domain inter-RAT SHOULDBE 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
UlPSInterRatShouldNot
HOUeNum
Number of users selected in a UL LDR PS domain inter-RAT SHOULDNOTBE

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
UlNonCtrlThdForAMR
The percentage of the conversational AMR service threshold to the 100% uplink
load.
UlNonCtrlThdForNonA
MR
The percentage of the conversational non-AMR service threshold to the 100%

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.
UlDcccRateThd
For a BE service that has a low maximum rate, the DCCC algorithm is not
Parameter ID
Description
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.
NBMUlCacAlgoSelSwi
tch

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
nd
This parameter specifies whether the UL frequency of the target cell of redirection
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:
Special frequencies: {12, 37, 62, 87, 112, 137, 162, 187, 212, 237, 262, 287}
Band3:
Band4:
Parameter ID
Description
Special frequencies: {1662, 1687, 1712, 1737, 1762, 1787, 1812, 1837, 1862}
Band5:
Special frequencies: {782, 787, 807, 812, 837, 862}
Band6:
Special frequencies: {812, 837}
Band7:
Special frequencies: {2362, 2387, 2412, 2437, 2462, 2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662, 2687}
Band8:
Band9:
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
- If the DL frequency belongs to special frequencies, then
ReDirUARFCNDownli
nk
This parameter specifies the target downlink UARFCN of a cell for RRC
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.
ZeroRateUpFailToRelTi
For the PS BE service at a rate of 0 kbit/s, this parameter is used for the rate
Parameter ID
Description
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
formats based on the transmission quality, thus lowering traffic speed and TX
Parameter ID
Description
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
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
UlBasicCommMeasFilte
rCoeff
Value range: D0, D1, D2, D3, D4, D5, D6, D7, D8, D9, D11, D13, D15, D17, D19
Physical value range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19
Content: L3 filtering coefficient. The larger the value of this parameter, the
Parameter ID
Description
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
Recommended value: D6
DlBasicCommMeasFilte
rCoeff
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.
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
n
Length of smoothing filter window of HSDPA power requirement.
ChoiceRprtUnitForHsdp
aPwrMeas
If you set this parameter to TEN_MSEC, use [HSDPA need pwr meas
parameter to MIN, use [HSDPA need pwr meas cycle,Unit:min] to specify
3GPP TS 25.433.
TenMsecForHsdpaPwr
Meas
HSDPA power requirement measurement report period For detailed information of

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
aRateMeas
If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify
3GPP TS 25.433.
TenMsecForHsdpaPrvid
RateMeas
This parameter specifies the HSDPA bit rate measurement report period. For
MinForHsdpaPrvidRate
Meas
This parameter specifies the HSDPA bit rate measurement report period. For
ChoiceRprtUnitForHsup
aRateMeas
If you set this parameter to TEN_MSEC, use [HSDPA bit rate meas
parameter to MIN, use [HSDPA bit rate meas cycle,Unit:min] to specify
3GPP TS 25.433.
Parameter ID
Description
TenMsecForHsupaPrvid
RateMeas
This parameter specifies the HSUPA bit rate measurement report period. For
MinForHsupaPrvidRate
Meas
This parameter specifies the HSUPA bit rate measurement report period. For
HsdpaPrvidBitRateFilter
Len
Length of smoothing filter window of HSDPA bit rate.
HsupaPrvidBitRateFilter
Len
Length of smoothing filter window of HSUPA bit rate.
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
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.
12.2 Values and Ranges

Table 12.2.1.I.1.1.1.1 Load control parameter values and parameter ranges
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
BGNSwitch
ON
OFF, ON
OFF, ON
None
ADD
CELLCAC(Optional)
RNC
Background
Noise
61
0621
112 to 50, step:

0.1
dBm
ADD
CELLCAC(Optional)
RNC
BgnAbnor
malThd
100
1400
0.140, step: 0.1
dB
ADD
CELLCAC(Optional)
RNC
BGNAdjust
TimeLen
120
16000
16000
ADD
CELLCAC(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
BgnEndTim
e
hour, min, sec
hour{023},
min{059},
sec{059}
None
ADD
CELLCAC(Mandatory)
RNC
BgnStartTi
me
hour, min, sec
hour{023},
min{059},
sec{059}
None
ADD
CELLCAC(Mandatory)
RNC
BgnUpdate
Thd
1100
0.110, step: 0.1
dBm
ADD
CELLCAC(Optional)
RNC
NBMCacAl
goSwitch
CRD_ADCTRL,
HSDPA_UU_A
DCTRL,
HSUPA_UU_A
DCTRL,
MBMS_UU_AD
CTRL,
HSDPA_GBP_
MEAS,
HSDPA_PBR_
MEAS, DOFFC,
HSUPA_PBR_
MEAS,
HSUPA_EDCH_
RSEPS_MEAS,
EMC_UU_ADC
TRL,
FACH_UU_AD
CTRL
CRD_ADCTRL,
HSDPA_UU_AD
CTRL,
HSUPA_UU_AD
CTRL,MBMS_U
U_ADCTRL,
HSDPA_GBP_M
EAS,HSDPA_PB
R_MEAS,
DOFFC,HSUPA_
PBR_MEAS,HSU
PA_EDCH_RSEP
S_MEAS,
EMC_UU_ADCT
RL,FACH_UU_A
DCTRL
None
ADD
CELLALGOSWITCH(
Optional)
RNC
NBMLdcAl
goSwitch
INTRA_FREQU
ENCY_LDB,
PUC,
UL_UU_LDR,
DL_UU_LDR,
UL_UU_OLC,
DL_UU_OLC,
OLC_EVENTM
EAS,
CELL_CODE_L
DR,
CELL_CREDIT
_LDR
INTRA_FREQUE
NCY_LDB,
PUC,UL_UU_LD
R,
DL_UU_LDR,UL
_UU_OLC,
DL_UU_OLC,OL
C_EVENTMEAS
,
CELL_CODE_L
DR,CELL_CRED
IT_LDR
None
ADD
CELLALGOSWITCH(
Optional)
RNC
CellLdrSfR
esThd
SF8
SF4(SF4),
SF8(SF8),
SF16(SF16),
SF32(SF32),
SF64(SF64),
SF128(SF128),
SF256(SF256)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256
None
ADD
CELLLDR(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
CellOverru
nThd
90
0100
01, step: 0.01
perce
nt
ADD
CELLLDB(Optional)
RNC
CellUnderr
unThd
30
0100
01, step: 0.01
perce
nt
ADD
CELLLDB(Optional)
RNC
HsdpaCMP
ermissionIn
d
FALSE(Forbidde
n),
TRUE(Permit)
FALSE, TRUE
None
SET CMCF(Optional)
RNC
HsupaCMP
ermissionIn
d
Limited, Permit,
BasedOnUECap(
Based On UE
Capability)
For each switch of

this parameter, the
value can be ON,
OFF.
None
SET CMCF(Optional)
RNC
CodeBalanc
ingDrdSwit
ch
-(SET
DRD)
ON, OFF
ON, OFF
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
OFF(AD
D
CELLDR
D)
CodeCongS
elInterFreq
HoInd
FALSE
FALSE(FALSE),
TRUE(TRUE)
FALSE, TRUE
None
ADD
CELLLDR(Optional)
RNC
CodeBalanc
ingDrdCod
eRateThd
-(SET
DRD)
13(ADD
CELLDR
D)
0100
0100
perce
nt
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
DeltaCode
OccupiedRa
te
0100
0100
perce
nt
SET DRD(Optional)
RNC
MinForDlB
asicMeas
160
160
min
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
DlBeTraffI
nitBitrate
D8, D16, D32,

D64, D128,
D144, D256,
D384
8, 16, 32, 64, 128,

144, 256, 384
kbit/s
SET FRC(Optional)
RNC
DlCCHLoa
dRsrvCoeff
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlCSInterR
atShouldBe
HOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
DlCSInterR
atShouldNo
tHOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
DlHOThd
85
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlHoCeCo
deResvSf
SF32
SF4(SF4),
SF8(SF8),
SF16(SF16),
SF32(SF32),
SF64(SF64),
SF128(SF128),
SF256(SF256),
SFOFF(SFOFF)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256,
SFOFF
None
ADD
CELLCAC(Optional)
RNC
DlInterFreq
HoCellLoad
SpaceThd
20
0100
01, step: 0.01
perce
nt
ADD
CELLLDR(Optional)
RNC
DlInterFreq
HoBWThd
200000
0400000
0400000
bit/s
ADD
CELLLDR(Optional)
RNC
DlHSUPAR
svdFactor
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlLdrCredi
tSfResThd
SF8
SF4(SF4),
SF8(SF8),
SF16(SF16),
SF32(SF32),
SF64(SF64),
SF128(SF128),
SF256(SF256)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
DlLdrRelT
hd
60
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
DlLdrTrigT
hd
70
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
DlLdrPsRT
QosRenegR
abNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
DlLdrAMR
RateReducti
onRabNum
110
110
None
ADD
CELLLDR(Optional)
RNC
DlLdrBERa
teReduction
RabNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
LdbDRDLo
adRemainT
hdDCH
-(SET
DRD)
35(ADD
CELLDR
D)
0100
0100
perce
nt
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
LdbDRDLo
adRemainT
hdHSDPA
-(SET
DRD)
0100
0100
perce
nt
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
100(AD
D
CELLDR
D)
DlOlcFTFR
strctRabNu
m
110
110
None
ADD
CELLOLC(Optional)
RNC
DlOlcFTFR
strctTimes
0100
0100
None
ADD
CELLOLC(Optional)
RNC
DlOlcRelTh
d
85
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
DlOlcTraff
RelRabNu
m
010
010
None
ADD
CELLOLC(Optional)
RNC
DlOlcTrigT
hd
95
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
DlPSInterR
atShouldBe
HOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
DlPSInterR
atShouldNo
tHOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
RateRecove
rTimerLen
5000
165535
165535
ms
ADD
CELLOLC(Optional)
RNC
RateRstrctC
oef
68
199
0.010.99, step:
0.01
perce
nt
ADD
CELLOLC(Optional)
RNC
RateRstrctT
imerLen
3000
165535
165535
ms
ADD
CELLOLC(Optional)
RNC
Recovercoe
f
130
100200
12, step: 0.01
perce
nt
ADD
CELLOLC(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
DlConvAM
RThd
80
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlConvNon
AMRThd
80
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlOtherThd
75
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlTotalEqU
serNum
80
1200
1200
None
ADD
CELLCAC(Optional)
RNC
DlCellTotal
Thd
90
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
DlDcccRate
Thd
D8, D16, D32,

D64, D128,
D144, D256,
D384
8, 16, 32, 64, 128,

144, 256, 384
kbit/s
SET DCCC(Optional)
RNC
NBMDlCac
AlgoSelSwi
tch
ALGORITHM_
OFF,
ALGORITHM_
FIRST,
ALGORITHM_
SECOND,
ALGORITHM_
THIRD
ALGORITHM_O
FF,
ALGORITHM_FI
RST,
ALGORITHM_S
ECOND,
ALGORITHM_T
HIRD
None
ADD
CELLALGOSWITCH(
Mandatory)
RNC
DRDEcN0
Threshhold
-18
24 to 0
12 to 0, step: 0.5
dB
ADD
GSMNCELL(Optional)
ADD
INTERFREQNCELL(O
ptional)
RNC
HsupaEqual
PriorityUse
rPBRThd
100
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
BGNEqUse
rNumThd
010
010
None
ADD
CELLCAC(Optional)
RNC
LdrFirstPri
IUBLDR(Iub
load reshuffling),
CODELDR(Cod
e load
reshuffling),
UULDR(Uu
load reshuffling),
CREDITLDR(Cr
edit load
reshuffling)
IUBLDR,CODEL
DR,UULDR,CRE
DITLDR
None
SET
LDCALGOPARA(Opti
onal)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
LdrFourthP
ri
IUBLDR(Iub
load reshuffling),
CODELDR(Cod
e load
reshuffling),
UULDR(Uu
load reshuffling),
CREDITLDR(Cr
edit load
reshuffling)
IUBLDR,CODEL
DR,UULDR,CRE
DITLDR
None
SET
LDCALGOPARA(Opti
onal)
RNC
GoldUserL
oadControl
Switch
OFF
OFF(OFF),
ON(ON)
OFF, ON
None
ADD
CELLLDR(Optional)
RNC
HsupaHigh
PriorityUse
rPBRThd
100
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
HsdpaBePB
RThd
30
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
HsdpaStrm
PBRThd
70
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
CarrierType
PriorInd
NONE, DCH,
HSPA
NONE,DCH,HSP
A
None
SET
USERPRIORITY(Optio
nal)
RNC
HsupaInitial
Rate
D8, D16, D32,

D64, D128,
D144, D256,
D384, D608,
D1440, D2048,
D2880, D5740
8, 16, 32, 64, 128,

144, 256, 384,
608, 1440, 2048,
2880, 5740
kbit/s
SET FRC(Optional)
RNC
PriorityRef
erence
ARP,
TrafficClass
ARP, TrafficClass
None
SET
USERPRIORITY(Optio
nal)
RNC
LdrCodeUs
edSpaceThd
13
0100
01, step: 0.01
perce
nt
ADD
CELLLDR(Optional)
RNC
LdrCodePri
UseInd
FALSE
FALSE(FALSE),
TRUE(TRUE)
FALSE, TRUE
None
ADD
CELLLDR(Optional)
RNC
LdrPeriodTi
merLen
186400
186400
SET
LDCPERIOD(Optional)
SET
SATLDCPERIOD(Opti
onal)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
LdbDRDch
oice
-(SET
DRD)
UserNumber,
Power
Power,
UserNumber
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
UserNum
ber(ADD
CELLDR
D)
LdbDRDOf
fsetDCH
0100
0100
perce
nt
SET DRD(Optional)
RNC
LdbDRDOf
fsetHSDPA
0100
0100
perce
nt
SET DRD(Optional)
RNC
LdbDRDS
witchDCH
-(SET
DRD)
ON, OFF
ON, OFF
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
ON, OFF
ON, OFF
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
OFF(AD
D
CELLDR
D)
LdbDRDS
witchHSDP
A
-(SET
DRD)
OFF(AD
D
CELLDR
D)
LdbDRDTo
talPwrProT
hd
0100
0100
perce
nt
SET DRD(Optional)
RNC
SpucHyst
0100
01, step: 0.01
perce
nt
ADD
CELLPUC(Optional)
RNC
SpucHeavy
70
0100
01, step: 0.01
perce
nt
ADD
CELLPUC(Optional)
RNC
SpucLight
45
0100
01, step: 0.01
perce
nt
ADD
CELLPUC(Optional)
RNC
HsupaLow
PriorityUse
rPBRThd
100
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
MaxQueue
TimeLen
160
160
SET
QUEUEPREEMPT(Opt
ional)
RNC
MaxUserNu
mCodeAdj
13
13
None
ADD
CELLLDR(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
MaxHsdpa
UserNum
64
0100
0100
None
ADD
CELLCAC(Optional)
RNC
MaxHsupa
UserNum
20
0100
0100
None
ADD
CELLCAC(Optional)
RNC
MbmsDecP
owerRabTh
d
115
115
None
ADD
CELLLDR(Optional)
RNC
MbmsPree
mptAlgoSw
itch
OFF, ON
OFF, ON
None
SET
QUEUEPREEMPT(Opt
ional)
RNC
MbmsOlcR
elNum
08
08
None
ADD
CELLOLC(Optional)
RNC
MinPCPIC
HPower
313
100 to 500
10 to 50, step:
0.1
dBm
ADD
PCPICH(Optional)
RNC
CodeBalanc
ingDrdMin
SFThd
-(SET
DRD)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
SF8(AD
D
CELLDR
D)
NodeBLdc
AlgoSwitch
IUB_LDR,
NODEB_CREDI
T_LDR,
LCG_CREDIT_
LDR, IUB_OLC
IUB_LDR,
NODEB_CREDI
T_LDR,
LCG_CREDIT_L
DR, IUB_OLC
None
ADD
NODEBALGOPARA(O
ptional)
RNC
NodeBHsd
paMaxUser
Num
3840
03840
03840
None
ADD
NODEBALGOPARA(O
ptional)
RNC
NodeBHsu
paMaxUser
Num
3840
03840
03840
None
ADD
NODEBALGOPARA(O
ptional)
RNC
OlcPeriodTi
merLen
10086400000
10086400000
ms
SET
LDCPERIOD(Optional)
SET
SATLDCPERIOD(Opti
onal)
RNC
PCPICHPo
werPace
0100
010, step: 0.1
dB
ADD
CELLLDB(Optional)
RNC
PreemptAlg
oSwitch
OFF, ON
OFF, ON
None
SET
QUEUEPREEMPT(Opt
ional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
PreemptRef
ArpSwitch
OFF, ON
OFF, ON
None
SET
QUEUEPREEMPT(Opt
ional)
RNC
EmcPreeRe
fVulnSwitc
h
OFF, ON
OFF, ON
None
SET
QUEUEPREEMPT(Opt
ional)
RNC
OffQoffset1
Light
20 to 20
20 to 20
dB
ADD
CELLPUC(Optional)
RNC
OffQoffset1
Heavy
20 to 20
20 to 20
dB
ADD
CELLPUC(Optional)
RNC
OffQoffset2
Light
20 to 20
20 to 20
dB
ADD
CELLPUC(Optional)
RNC
OffQoffset2
Heavy
20 to 20
20 to 20
dB
ADD
CELLPUC(Optional)
RNC
QueueAlgo
Switch
OFF, ON
OFF, ON
None
SET
QUEUEPREEMPT(Opt
ional)
RNC
LdrSecond
Pri
IUBLDR(Iub
load reshuffling),
CODELDR(Cod
e load
reshuffling),
UULDR(Uu
load reshuffling),
CREDITLDR(Cr
edit load
reshuffling)
IUBLDR,CODEL
DR,UULDR,CRE
DITLDR
None
SET
LDCALGOPARA(Opti
onal)
RNC
SeqOfUser
Rel
MBMS
service
MBMS_REL(M
BMS service),
USER_REL(UE)
MBMS_REL,
USER_REL
None
ADD
CELLOLC(Optional)
RNC
ServiceDiff
DrdSwitch
-(SET
DRD)
ON, OFF
ON, OFF
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
18
18
None
ADD SPG(Mandatory)
ADD
CELLSETUP(Mandator
y)
ADD
QUICKCELLSETUP(M
andatory)
RNC
OFF(AD
D
CELLDR
D)
SpgId
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
OffSinterLi
ght
-2
10 to 10
20 to 20, step: 2
dB
ADD
CELLPUC(Optional)
RNC
OffSinterHe
avy
10 to 10
20 to 20, step: 2
dB
ADD
CELLPUC(Optional)
RNC
LdrThirdPri
IUBLDR(Iub
load reshuffling),
CODELDR(Cod
e load
reshuffling),
UULDR(Uu
load reshuffling),
CREDITLDR(Cr
edit load
reshuffling)
IUBLDR,
CODELDR,
UULDR,
CREDITLDR
None
SET
LDCALGOPARA(Opti
onal)
RNC
ChoiceRprt
UnitForDlB
asicMeas
TEN_MSEC,
MIN
TEN_MSEC,
MIN
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
ChoiceRprt
UnitForUlB
asicMeas
TEN_MSEC,
MIN
TEN_MSEC,
MIN
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
TransCchU
serNum
010
010
None
ADD
CELLOLC(Optional)
RNC
MinForUlB
asicMeas
160
160
min
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
UlBeTraffI
nitBitrate
D8, D16, D32,

D64, D128,
D144, D256,
D384
8, 16, 32, 64, 128,

144, 256, 384
kbit/s
SET FRC(Optional)
RNC
UlCCHLoa
dFactor
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
UlCSInterR
atShouldBe
HOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlCSInterR
atShouldNo
tHOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlNonCtrlT
hdForHo
80
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
UlHoCeRes
vSf
SF16
SF4(SF4),
SF8(SF8),
SF16(SF16),
SF32(SF32),
SF64(SF64),
SF128(SF128),
SF256(SF256),
SFOFF(SFOFF)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256,
SFOFF
None
ADD
CELLCAC(Optional)
RNC
UlInterFreq
HoCellLoad
SpaceThd
20
0100
01, step: 0.01
perce
nt
ADD
CELLLDR(Optional)
RNC
UlInterFreq
HoBWThd
200000
0400000
0400000
bit/s
ADD
CELLLDR(Optional)
RNC
UlHsDpcch
RsvdFactor
0100
01, step: 0.01
perce
nt
ADD
CELLCAC(Optional)
RNC
UlLdrCredi
tSfResThd
SF8
SF4(SF4),
SF8(SF8),
SF16(SF16),
SF32(SF32),
SF64(SF64),
SF128(SF128),
SF256(SF256)
SF4, SF8, SF16,

SF32, SF64,
SF128, SF256
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlLdrRelT
hd
45
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
UlLdrTrigT
hd
55
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
UlLdrPsRT
QosRenegR
abNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlLdrAMR
RateReducti
onRabNum
110
110
None
ADD
CELLLDR(Optional)
RNC
UlLdrBERa
teReduction
RabNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlOlcFTFR
strctRabNu
m
110
110
None
ADD
CELLOLC(Optional)
RNC
UlOlcFTFR
strctTimes
0100
0100
None
ADD
CELLOLC(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
UlOlcRelTh
d
85
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
UlOlcTraff
RelRabNu
m
010
010
None
ADD
CELLOLC(Optional)
RNC
UlOlcTrigT
hd
95
0100
01, step: 0.01
perce
nt
ADD
CELLLDM(Optional)
RNC
UlPSInterR
atShouldBe
HOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlPSInterR
atShouldNo
tHOUeNum
110
110
None
ADD
CELLLDR(Optional)
ADD
NODEBLDR(Optional)
RNC
UlNonCtrlT
hdForAMR
75
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
UlNonCtrlT
hdForNonA
MR
75
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
UlNonCtrlT
hdForOther
60
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
UlTotalEqU
serNum
80
1200
1200
None
ADD
CELLCAC(Optional)
RNC
UlCellTotal
Thd
83
0100
01, step: 0.01
None
ADD
CELLCAC(Optional)
RNC
UlDcccRate
Thd
D8, D16, D32,

D64, D128,
D144, D256,
D384
8, 16, 32, 64, 128,

144, 256, 384
kbit/s
SET DCCC(Optional)
RNC
NBMUlCac
AlgoSelSwi
tch
ALGORITHM_
OFF,
ALGORITHM_
FIRST,
ALGORITHM_
SECOND,
ALGORITHM_
THIRD
ALGORITHM_O
FF,
ALGORITHM_FI
RST,
ALGORITHM_S
ECOND,
ALGORITHM_T
HIRD
None
ADD
CELLALGOSWITCH(
Mandatory)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
RedirSwitc
h
OFF,
ONLY_TO_INT
ER_FREQUEN
CY,
ONLY_TO_INT
ER_RAT
OFF,
ONLY_TO_INTE
R_FREQUENCY,
ONLY_TO_INTE
R_RAT
None
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
RedirFactor
OfNorm
0100
0100
perce
nt
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
RedirFactor
OfLDR
0100
0100
perce
nt
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
RedirBandI
nd
-(ADD
CELLRE
DIRECT
ION,SET
REDIRE
CTION,S
ET DRD)
Band1, Band2,
Band3, Band4,
Band5, Band6,
Band7, Band8,
Band9,
DependOnNCell
,
BandIndNotUse
d
Band1, Band2,
Band3, Band4,
Band5, Band6,
Band7, Band8,
Band9,
DependOnNCell,
BandIndNotUsed
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
TRUE, FALSE
TRUE, FALSE
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
DependO
nNCell(
ADD
CELLDR
D)
ReDirUAR
FCNUplink
Ind
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
ReDirUAR
FCNUplink
016383
016383
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
ReDirUAR
FCNDownl
ink
016383
016383
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
SET
REDIRECTION(Option
al)
ADD
CELLREDIRECTION(
Optional)
RNC
EcN0Effect
Time
-(SET
FRC)
065535
065535
ms
SET FRC(Optional)
ADD
CELLFRC(Optional)
RNC
30000(A
DD
CELLFR
C)
EcN0Ths
-(SET
FRC)
41(ADD
CELLFR
C)
049
24.5 to 0
dB
SET FRC(Optional)
ADD
CELLFRC(Optional)
RNC
ZeroRateUp
FailToRelTi
merLen
065535
065535
SET
COIFTIMER(Optional)
RNC
FACHPwrR
educeValue
030
03, step: 0.1
dB
ADD
CELLOLC(Optional)
RNC
DrSwitch
DR_RRC_DRD
_SWITCH,
DR_RAB_SING
_DRD_SWITCH
,
DR_RAB_COM
B_DRD_SWITC
H
DR_RRC_DRD_
SWITCH,
DR_RAB_SING_
DRD_SWITCH,
DR_RAB_COMB
_DRD_SWITCH
None
SET
CORRMALGOSWITC
H(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
DraSwitch
DRA_AQM_SW
ITCH,
DRA_BE_EDC
H_TTI_RECFG
_SWITCH,
DRA_BE_RATE
_DOWN_BF_H
O_SWITCH,
DRA_DCCC_S
WITCH,
DRA_HSDPA_
DL_FLOW_CO
NTROL_SWITC
H,
DRA_HSDPA_S
TATE_TRANS_
SWITCH,
DRA_HSUPA_
DCCC_SWITC
H,
DRA_HSUPA_S
TATE_TRANS_
SWITCH,
DRA_IU_QOS_
RENEG_SWITC
H,
DRA_PS_BE_S
TATE_TRANS_
SWITCH,
DRA_PS_NON_
BE_STATE_TR
ANS_SWITCH,
DRA_R99_DL_
FLOW_CONTR
OL_SWITCH,
DRA_THROUG
HPUT_DCCC_S
WITCH
DRA_AQM_SWI
TCH,
DRA_BE_EDCH
_TTI_RECFG_S
WITCH,
DRA_BE_RATE_
DOWN_BF_HO_
SWITCH,
DRA_DCCC_SW
ITCH,
DRA_HSDPA_D
L_FLOW_CONT
ROL_SWITCH,
DRA_HSDPA_ST
ATE_TRANS_S
WITCH,
DRA_HSUPA_D
CCC_SWITCH,
DRA_HSUPA_ST
ATE_TRANS_S
WITCH,
DRA_IU_QOS_R
ENEG_SWITCH,
DRA_PS_BE_ST
ATE_TRANS_S
WITCH,
DRA_PS_NON_
BE_STATE_TRA
NS_SWITCH,
DRA_R99_DL_F
LOW_CONTRO
L_SWITCH,
DRA_THROUG
HPUT_DCCC_S
WITCH
None
SET
CORRMALGOSWITC
H(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
NbmLdcBH
OUeSelSwi
tch
NBM_L
DC_MA
TCH_UE
_ONLY
NBM_LDC_AL
L_UE(Select all
users),
NBM_LDC_MA
TCH_UE_ONL
Y(Select users
mactch target
cell support
only),
NBM_LDC_MA
TCH_UE_FIRS
T(Select users
mactch target
cell support first)
NBM_LDC_ALL
_UE,
NBM_LDC_MAT
CH_UE_ONLY,
NBM_LDC_MAT
CH_UE_FIRST
None
ADD
CELLALGOSWITCH(
Optional)
RNC
PsSwitch
PS_BE_EXTRA
_LOW_RATE_
ACCESS_SWIT
CH,
PS_BE_INIT_R
ATE_DYNAMI
C_CFG_SWITC
H,
PS_BE_IU_QOS
_NEG_SWITCH
,
PS_RAB_DOW
NSIZING_SWIT
CH,
PS_RSC_FEED
BK_RABSETU
P_CACFAIL_S
WITCH,
PS_STREAM_I
U_QOS_NEG_S
WITCH,
PS_BE_STRICT
_IU_QOS_NEG
_SWITCH
PS_BE_EXTRA_
LOW_RATE_AC
CESS_SWITCH,
PS_BE_INIT_RA
TE_DYNAMIC_
CFG_SWITCH,
PS_BE_IU_QOS_
NEG_SWITCH,
PS_RAB_DOWN
SIZING_SWITC
H,
PS_RSC_FEEDB
K_RABSETUP_
CACFAIL_SWIT
CH,
PS_STREAM_IU
_QOS_NEG_SWI
TCH,
PS_BE_STRICT_
IU_QOS_NEG_S
WITCH
None
SET
CORRMALGOSWITC
H(Optional)
RNC
RlMaxDlP
wr
350 to 150
35 to 15, step:
0.1
dB
ADD
CELLRLPWR(Mandato
ry)
RNC
UlBasicCo
mmMeasFil
terCoeff
D0, D1, D2, D3,

D4, D5, D6, D7,
D8, D9, D11,
D13, D15, D17,
D19
D0, D1, D2, D3,

D4, D5, D6, D7,
D8, D9, D11,
D13, D15, D17,
D19
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
DlBasicCo
mmMeasFil
terCoeff
D0, D1, D2, D3,

D4, D5, D6, D7,
D8, D9, D11,
D13, D15, D17,
D19
D0, D1, D2, D3,

D4, D5, D6, D7,
D8, D9, D11,
D13, D15, D17,
D19
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
PucAvgFilt
erLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
UlCacAvgF
ilterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
DlCacAvgF
ilterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
LdbAvgFilt
erLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
UlLdrAvgFi
lterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
DlLdrAvgFi
lterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
UlOlcAvgFi
lterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
DlOlcAvgFi
lterLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
HsdpaNeed
PwrFilterLe
n
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
ChoiceRprt
UnitForHsd
paPwrMeas
TEN_MSEC,
MIN
TEN_MSEC,
MIN
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
TenMsecFo
rHsdpaPwr
Meas
16000
1060000, step:
10
ms
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
MinForHsd
paPwrMeas
160
160
min
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
ChoiceRprt
UnitForHsd
paRateMeas
TEN_MSEC,
MIN
TEN_MSEC,
MIN
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
TenMsecFo
rHsdpaPrvi
dRateMeas
16000
1060000, step:
10
ms
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
MinForHsd
paPrvidRate
Meas
160
160
min
SET LDM(Mandatory)
SET
SATLDM(Mandatory)
RNC
ChoiceRprt
UnitForHsu
paRateMeas
TEN_MSEC,
MIN
TEN_MSEC,
MIN
None
SET LDM(Optional)
RNC
TenMsecFo
rHsupaPrvi
dRateMeas
16000
1060000, step:
10
ms
SET LDM(Mandatory)
RNC
MinForHsu
paPrvidRate
Meas
160
160
min
SET LDM(Mandatory)
RNC
HsdpaPrvid
BitRateFilte
rLen
132
132
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
HsupaPrvid
BitRateFilte
rLen
132
132
None
SET LDM(Optional)
RNC
DRMaxGS
MNum
-(SET
DRD)
2(ADD
CELLDR
D)
05
05
None
SET DRD(Optional)
ADD
CELLDRD(Optional)
RNC
UlOlcTrigH
yst
16000
1060000, step:
10
None
SET LDM(Optional)
SET
SATLDM(Optional)
RNC
Paramet
er ID
Defaul
t
Value
GUI Value
Range
Actual Value
Range
Unit
MML Command
NE
RsvdPara1
RsvdBit1(Reserv
ed Switch 1),
RsvdBit2(Reserv
ed Switch 2),
RsvdBit3(Reserv
ed Switch 3),
RsvdBit4(Reserv
ed Switch 4),
RsvdBit5(Reserv
ed Switch 5),
RsvdBit6(Reserv
ed Switch 6),
RsvdBit7(Reserv
ed Switch 7),
RsvdBit8(Reserv
ed Switch 8),
RsvdBit9(Reserv
ed Switch 9),
RsvdBit10(Reser
ved Switch 10),
RsvdBit11(Reser
ved Switch 11),
RsvdBit12(Reser
ved Switch 12),
RsvdBit13(Reser
ved Switch 13),
RsvdBit14(Reser
ved Switch 14),
RsvdBit15(Reser
ved Switch 15),
RsvdBit16(Reser
ved Switch 16)
RsvdBit1,
RsvdBit2,
RsvdBit3,
RsvdBit4,
RsvdBit5,
RsvdBit6,
RsvdBit7,
RsvdBit8,
RsvdBit9,
RsvdBit10,
RsvdBit11,
RsvdBit12,
RsvdBit13,
RsvdBit14,
RsvdBit15,
RsvdBit16
None
ADD
CELLALGOSWITCH(
Optional)
RNC
SLOCELL
026843545
026843545
None
ADD
PAGRP(Mandatory)
Node
B
DLOCELL
026843545
026843545
None
ADD
PAGRP(Mandatory)
Node
B
MAXSHRT
O
50
180
180
ADD PAGRP(Optional)
Node
B
SHMGN
10
180
180
ADD PAGRP(Optional)
Node
B
The Default Value column is valid for only the optional parameters.
The "-" symbol indicates no default value.
13
Reference Documents
The following lists the reference documents related to the feature:

1.
3GPP TS 25.133: Requirements for Support of Radio Resource Management (FDD)
2.
3GPP TS 25.215: Physical layer - Measurements (FDD)
3.
3GPP TS 25.304: UE Procedures in Idle Mode and Procedures for Cell Reselection in
Connected Mode
4.
3GPP TS 25.321: Medium Access Control (MAC) protocol specification
5.
3GPP TS 25.331: Radio Resource Control (RRC)
6.
3GPP TS 25.413: UTRAN Iu Interface RANAP Signaling
7.
Basic Feature Description of Huawei UMTS RAN11.0 V1.5
8.
Optional Feature Description of Huawei UMTS RAN11.0 V1.5
9.
Rate Control Parameter Description
10. MBMS Parameter Description

11. HSDPA Parameter Description
12. HSUPA Parameter Description
13. Radio Bearer Parameter Description
14. Transmission Resource Management Parameter Description
15. Handover Parameter Description
16. Green BTS Description

Load Control Huawei

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Load Control Huawei

Caricato da

Copyright:

Formati disponibili

RAN

Load Control Parameter Description

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

About This Document

4 Load Measurement Algorithm........................................................3

5 Potential User Control Algorithm...................................................3

Huawei Proprietary and Confidential

6.3.4 Target Rate Negotiation............................................................................................................................3

7 Call Admission Control Algorithm...................................................3

8 Intra-Frequency Load Balancing Algorithm.....................................3

Huawei Proprietary and Confidential

9.3.4 Inter-RAT Handover in the CS Domain...................................................................................................3

10 Overload Control Algorithm.........................................................3

11 Dynamic Power Sharing Among Carriers.......................................3

12 Load Control Parameters.............................................................3

Huawei Proprietary and Confidential

Document and Product Versions

This document is based on the BSC6810 and 3900 series NodeBs.

Feature change: refers to the change in the load control feature.

The description of Control RTWP

The added parameter is as

Huawei Proprietary and Confidential

The description of dynamic

The corresponding parameters as

Huawei Proprietary and Confidential

Some parameters are added to

The added parameters are as follows:

The description of RRC

The description of initial rate

The added parameters are as follows:

The added parameters are as follows:

Huawei Proprietary and Confidential

The description of low-rate

The added parameters are as follows:

The description of an OLC

The added parameter is as follows:

The description of dynamic

The added parameters are as follows:

The description of dynamic

The title of the document is

The added parameters are as follows:

Parameter names are replaced

Huawei Proprietary and Confidential

9 Load Reshuffling Algorithm

Load Control Introduction

System operators who need a general understanding of load control.

Personnel working on Huawei products or systems.

Impact on System Performance

Impact on Other Features

Network Elements Involved

Huawei Proprietary and Confidential

9 Load Reshuffling Algorithm

Table 2.1.1.I.1.1.1.1 NEs involved in load control

Huawei Proprietary and Confidential

Load Control Algorithm

This chapter consists of the following sections:

Load Control Workflow

Priorities Involved in Load Control

3.1 Load Control Workflow

Before UE access: Potential User Control (PUC)