WCDMA RAN Planning and Optimization - Book3 - 2 - Features and Algorithms

WCDMA Load Control
www.huawei.com
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.
The WCDMA system is a self interference system. As the load of the WCDMA system
increases, the interference rises. A relatively high interference may affect the coverage
and Quality of Service (QoS) of established services. Therefore, capacity, coverage and
QoS of the WCDMA system are mutually affected. The purpose of load control is to
maximize the system capacity while ensuring coverage and QoS.
Objectives
z
Upon completion of this course, you will be able to:
Know load control principles
Know load control realization methods in WCDMA system
Know load control parameters in WCDMA system
Contents
1. Load Control Overview
2. Load Control Algorithms
Contents
1.1 Load Control Algorithms Overview
1.2 Load Measurement
1.3 Priorities Involved in Load Control
Load Definition
z
Load: the occupancy of capacity
Two kinds of capacity in WCDMA system
Hard capacity
Cell DL OVSF Code
NodeB Transport resource
NodeB processing capability (NodeB credit)
Soft capacity
Cell Power (UL and DL)
WCDMA network load can be defined by 4 factors:

1,Power ,include DL transmitting power of cell and increased UL interference (RTWP).
2,DL OVSF code of a cell
3,DL and UL NodeB processing capability which is defined by NodeB credit.
4,Iub transmission bandwidth of a NodeB
The power resource is related to the mobility, distribution of the UE and also effected by
the radio conditions. Therefore, for a fixed power resource, the numbers of service can
be supported is not a fix result. We believe the UL and DL power resources are soft.
The Objectives of Load Control

z
Keeping system stable
Maximizing system capacity while ensuring coverage and

QoS
Realize different priorities for different service and different

user
WCDMA network load can be defined by 4 factors:

1,Power ,include DL transmitting power of cell and increased UL interference (RTWP).
2,DL OVSF code of a cell
3,DL and UL NodeB processing capability which is defined by NodeB credit.
4,Iub transmission bandwidth of a NodeB
The power resource is related to the mobility, distribution of the UE and also effected
by the radio conditions. Therefore, for a fixed power resource, the numbers of service
can be supported is not a fix result. We believe the UL and DL power resources are
soft.
Load Control Algorithms

z
The load control algorithms are applied to the different

UE access phases as follows:
PUC: Potential User Control
CAC: Call Admission Control
IAC: Intelligent Admission Control
LDB : Intra-frequency Load Balancing
LDR: Load Reshuffling
OLC: Overload Control
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)

Load control algorithm in the WCDMA system
The load control algorithms are built into the RNC. The input of load control comes
from the RNC and measurement information of the NodeB.
RNC can calculate hard resource load, that is OVSF ,NodeB credit, Iub occupancy.
The soft load need the NodeB reporting.
Contents
Soft Load Measurement

The major measurement objects of the load measurement
Uplink Received Total Wideband Power (RTWP)
UL Load
Received scheduled Enhanced Dedicated Channel (E-DCH)

power share (RSEPS)
E-DCH Provided Bit Rate
TCP
Non-HSPA TCP
DL Load
HSDPA PBR
HSDPA GBP
The soft load control algorithms 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.
The NodeB and the RNC perform measurements and filtering in accordance with the
parameter settings. The statistics obtained after the measurements and filtering serve
as the data input for the load control algorithms.
The major measurement objects of the LDM are as follows:
Uplink Received Total Wideband Power (RTWP)
Received scheduled Enhanced Dedicated Channel (E-DCH) power share (RSEPS)
E-DCH Provided Bit Rate
Downlink Transmitted Carrier Power (TCP)
TCP of all codes not used for High Speed Physical Downlink Shared Channel (HSPDSCH), High Speed Shared Control Channel (Non-HSPA TCP)
Provided Bit Rate on HS-DSCH (PBR)
HS-DSCH required power also called Guaranteed Bit Rate (GBR) required power
(GBP)
Load Measurement procedure
Smooth Window Filtering on the RNC Side

N 1
P ( n) =
n i
i =0
N : the size of the smooth window
Pn : the reported measurement value
Based on the measurement parameters set on the NodeB Local Maintenance Terminal
(LMT), 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.
Based on the measurement parameters set on the RNC LMT, 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.
Filtering on the NodeB Side
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 ,which is the reported measurement
value
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 interval at which the NodeB reports each measurement quantity to the RNC is
configured by the Time unit and Report cycle on RNC LMT: SET LDM
The report interval = Time unit * Report cycle
By default, Time unit for all measurement are set to 10ms ;Report cycle for
RTWP is 100, that is 1s; Report cycle for TCP and Non HSPA TCP is 20 ,that is
200ms ;Report cycle for HSDPA GBP is 10, that is 100 ms; Report cycle for
HSDPA PBR is 10, that is 100 ms
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, LDBLDR, and OLC to common measurement

are different. The LDM algorithm must apply different smooth filter coefficients and
measurement periods to those algorithms , on RNC LMT, we can set the smooth
window length for different algorithms by SET LDM:
The following table lists the parameters :
Parameter Name
Parameter ID
Value
Range
default
Value
PUC moving average

filter length
PucAvgFilterLen
1 to 32
32
LDB moving average

filter length
LdbAvgFilterLen
1 to 32
32
UL LDR moving average

filter length
UlLdrAvgFilterLen
1 to 32
25
DL LDR moving average

filter length
DlLdrAvgFilterLen
1 to 32
25
UL CAC moving average

filter length
UlCACAvgFilterLen
1 to 32
DL CAC moving average

filter length
DlCACAvgFilterLen
1 to 32
UL OLC moving average

filter length
UlOLCAvgFilterLen
1 to 32
25
DL OLC moving average

filter length
DlOLCAvgFilterLen
1 to 32
25
Smooth window for GBP for all related algorithms are the same and the default setting is 1
Contents
Priority
z
The service of user with low priority will be affected by the

load control algorithms first
Three kinds of priorities
User Priority
RAB Integrate Priority
User Integrate Priority
User Priority: mainly applying to provide different QoS for different users. Eg., setting
different GBR according to the user priority for BE service. No consideration about the
service.
RAB Integrate Priority: Priority of a service, related to the service type, and the user
priority of the user.
User Integrate Priority: Only used for multi-RAB user ,it is a temporary priority of an
ongoing-service user.
User Priority
z
There are three levels of user priority
gold (high), silver (middle) and copper (low) user
User priority
Gold
Silver
Copper
Uplink
128kbps 64kbps 32kbps
Downlink
128kbps 64kbps 32kbps
gold
user
Pay $100
for 3G
services
In CN HLR, we can set ARP (Allocation Retention Priority ), during service setup, CN
sends ARP to RNC .Based on the mapping relation( configured in RNC), RNC can
identify the user is a gold, silver or copper one.
The user priority affect GBR of BE service in RAN, Iub transmission management and so
on.
User Priority
z
The mapping relation between user priority and ARP

(Allocation/Retention Priority) is configured in RNC by SET
USERPRIORITY
The default relation is:
ARP
User
Priority
Gold
Silver
10 11
12 13
14
Copper
The user priority mapping can be configured in RNC by SET USERPRIORITY

ARP 15 is always the lowest priority and it cannot be configured. It corresponds to
copper.
If ARP is not received in messages from the Iu interface, the user priority is regarded as
copper.
15
RAB Integrate Priority

z
RAB Integrate Priority is mainly used in load control

algorithms
RAB Integrate Priority are set according to :
ARP
Traffic Class
THPfor interactive service only
HSPA or DCH
RAB Integrate Priority is mainly used in load control algorithms.

The values of RAB Integrate Priority are set according to the Integrate Priority
Configured Reference parameter as follows:
If Integrate Priority Configured Reference is set to Traffic Class, the integrate 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, defined in CN , sent to RNC during service setup), that is,
THP1 -> THP2 -> THP3 -> ... -> THP14 =>
Services of the same ARP, class and THP (only for interactive services): High
Speed Packet Access (HSPA) or Dedicated Channel (DCH) service preferred
depending on the value of the Indicator of Carrier Type Priority parameter.
If Integrate Priority Configured Reference is set to ARP, the integrate priority abides by
the following rules:
ARP1 -> ARP2 -> ARP3 -> ... -> ARP14 =>
Traffic classes: 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, class and THP (only for interactive services): HSPA
or DCH service preferred depending on the value of the Indicator of Carrier
Type Priority parameter.
Integrate Priority Configured Reference and Indicator of Carrier Type
Priority are set by SET USERPRIORITY .
By default
Integrate Priority Configured Reference is set to ARP
Indicator of Carrier Type Priority is set to NONE, that means HSDPA and DCH
services have the same priority.
ARP and THP are carried in the RAB ASSIGNMENT REQUEST message, and they are
not configurable on the RNC LMT.
Example for RAB Integrate Priority

Based on ARP, HSDPA priority is higher
Service ARP Traffic Class
ID
Services attribution in the cell
Service ARP
ID
Traffic Class
Bear
type
Interactive
HSDPA
Bear
type
Interactive
DCH
Conversational
DCH
Background
DCH
Interactive
DCH
Interactive
HSDPA
Conversational
DCH
Background
DCH
Based on Traffic Class, HSDPA priority is higher

Service
ID
Traffic Class
ARP
Bear
type
Conversational
DCH
Interactive
HSDPA
Interactive
DCH
Background
DCH
This example shows the RAB Integrate Priority calculation in 2 different conditions
User Integrate Priority

z
When the user has one RAB, User integrate priority is the
same as the RAB integrate priority
For multiple RAB users, the integrate priority of the user is

based on the service of the highest priority
When the user has one RAB, User integrate priority is the same as the service of the
RAB integrate priority;
For multiple RAB users, the integrate priority of the user is based on the service of the
highest priority.
User integrate 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 BE services to CCH are
performed according to the user integrate priority.
Key parameters of Priority

z
Integrate Priority Configured Reference
Parameter ID: PRIORITYREFERENCE
The default value of this parameter is ARP
Indicator of Carrier Type Priority
Parameter ID: CARRIERTYPEPRIORIND
The default value of this parameter is NONE
Integrate Priority Configured Reference

Parameter ID: PRIORITYREFERENCE
Value range: ARP, Traffic Class
Content: This parameter is used to set the criterion by which the priority is first sorted.
The default value of this parameter is ARP
Set this parameter through SET USERPRIORITY
Indicator of Carrier Type Priority
Parameter ID: CARRIERTYPEPRIORIND
Value range: NONE, DCH, HSPA
Content: This parameter is used to decide which carrier (DCH or HSPA) takes
precedence when ARP and Traffic Class are identical. When this parameter is set to
NONE, the bearing priority of services on the DCH is the same as that of HSPA
services.
The default value of this parameter is NONE,
Set this parameter through SET USERPRIORITY
Contents
2.1 PUC (Potential User Control)
2.2 LDB (Intra-Frequency Load Balancing)
2.3 CAC (Call Admission Control)
2.4 IAC (Intelligent Admission Control)
2.5 LDR (Load Reshuffling)
2.6 OLC (Overload Control)
PUC Principles
z
The Potential User Control (PUC) algorithm controls the

Inter-frequency cell reselection of the potential UE, and
prevents UE from camping on a heavily loaded cell.
Potential UE :
IDLE Mode UE
CELL-FACH UECELL-PCH UEURA-PCH UE
The function of PUC is to balance traffic load among inter-frequency cells. By modifying
cell selection and reselection parameters and broadcasting them through system
information, PUC leads UEs to cell with light load. The UE may be in idle mode,
Cell_FACH state, Cell _PCH state, URA_PCH state
PUC Load Judgment
Cell load for PUC is of three states: heavy, normal, and light
The RNC periodically monitors the downlink load of the cell and compares the
measurement results with the configured thresholds Load level division threshold 1 and
Load level division threshold 2, that is, load level division upper and lower thresholds.
If the cell load is higher than the load level division upper threshold plus the Load level
division hysteresis, the cell load is considered heavy.
If the cell load is lower than the load level division lower threshold minus the Load level
division hysteresis, the cell load is considered light.
Otherwise the cell load is considered normal
PUC Procedure
Threshold
Every 200ms
Cell TCP
Heavy?
Light?
Normal?
RNC
cell reselection
parameters
System information
NodeB
UE
Every 30 minutes
The parameters related to cell selection and cell reselection are Qoffset1(s,n) (load level
offset), Qoffset2(s,n) (load level offset), and Sintersearch (start threshold for interfrequency cell reselection).
The NodeB periodically reports the total TCP of the cell, and the PUC periodically triggers
the following activities:
Assessing the cell load level based on the total TCP
Configuring Sintersearch, Qoffset1(s,n), and Qoffset2(s,n) based on the cell load level
PUC can Modify inter-frequency cell reselection parameters based on the load:
1. Sintersearch :
when the load of a cell is Heavy, PUC will increase Sintersearch
when the load of a cell is Light, PUC will decrease Sintersearch
2. QOffset:
when the load of current cell is Heavy and neighbor is Non heavy, PUC will decrease
QOffset
when the load of current cell is Non heavy and neighbor is Heavy, PUC will increase
QOffset
Updating the parameters of system information SIB3 and SIB11
Load of Current Cell
Sintersearch
Light
S'intersearch = Sintersearch + Sintersearch offset 1
Normal
S'intersearch = Sintersearch
Heavy
S'intersearch = Sintersearch + Sintersearch offset 2
: indicates that the parameter value remains unchanged.

: indicates that the parameter value increases.
: indicates that the parameter value decreases.
Change of
Sintersearch
PUC Principles
Light load
Freq1
Modify
System Info
SIB3,11
1.Hard to trigger reselection

2.Easy to camp on the cell
Increase the POTENTIAL load
Normal load
Stay
System Info
SIB3,11
Heavy load
Freq2 1.Easy to trigger reselection
2.Easy to select light load

Inter-freq neighbor Cell
Modify
Decrease the POTENTIAL load
System Info
SIB3,11
Idle state
CCH state
Based on the characteristics of inter-frequency cell selection and reselection.

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.
Key parameters PUC

z
Cell LDC algorithm switch
Parameter ID: NBMLDCALGOSWITCH PUC
The default value of this parameter is Off
Load level division threshold 1 (Heavy)
Parameter ID: SPUCHEAVY
The default value of this parameter is 70(70%)
Load level division threshold 2 (Light)
Parameter ID: SPUCLIGHT

Parameter ID: NBMLDCALGOSWITCH PUC
Value range: OFF, ON
Content: This parameter is used to enable or disable the PUC algorithm..
The default value of this parameter is OFF
Set this parameter through ADD CELLALGOSWITCH / MOD CELLALGOSWITCH
Load level division threshold 1 (Heavy)

Parameter ID: SPUCHEAVY
Value range: 0 to 100
Content: This parameter is one of the thresholds used to assess cell load level and to
decide whether the cell load level is heavy or not.
The default value of this parameter is 70%,
Set this parameter through ADD CELLPUC / MOD CELLPUC
Load level division threshold 2 (Light)
Parameter ID: SPUCLIGHT
Content: This parameter is one of the thresholds used to assess cell load level and to
decide whether the cell load level is heavy or not.
Key parameters PUC

z
Load level division hysteresis
Parameter ID: SPUCHYST
The default value of this parameter is 5 (5%)
PUC period timer length
Parameter ID: PUCPERIODTIMERLEN
The default value of this parameter is 1800(s)
Load level division hysteresis

Parameter ID: SPUCHYST
Content: This parameter specifies the hysteresis used during cell load level
assessment to avoid unnecessary ping-pong effect of a cell between two load levels
due to a little load change.
The default value of this parameter is 5 (5%)
PUC period timer length
Parameter ID: PUCPERIODTIMERLEN
Value range: 6 to 86400 s
Content: This parameter specifies the period of potential user control. The higher the
parameter is set, the longer the period to trigger the PUC is.
The default value of this parameter is 1800(s)
Set this parameter through SET LDCPERIOD
Key parameters PUC

z
Sintersearch offset 1
Parameter ID: OFFSINTERLIGHT
The default value of this parameter is 2 (-4dB)
Parameter ID: OFFSINTERHEAVY
The default value of this parameter is 2 (4dB)
Parameter ID: OFFSINTERLIGHT
Value range: 10 to 10 ,step:2dB
Content: This parameter defines the offset of Sintersearch when the center cell load
level is "Light". It is strongly recommended that this parameter be set to a value not
higher than 0. The default value of this parameter is 2 (-4dB)
Parameter ID: OFFSINTERHEAVY
Content: This parameter defines the offset of Sintersearch when the center cell load
level is "Heavy". It is strongly recommended that this parameter be set to a value not
lower than 0. The default value of this parameter is 2 (4dB)
Key parameters PUC

z
Qoffset1 offset 1
Parameter ID: OFFQOFFSET1LIGHT
Qoffset1 offset 2
Parameter ID: OFFQOFFSET1HEAVY
Qoffset1 offset 1
Content: This parameter defines the offset of Qoffset1RSCP when the current
cell has heavy load and the neighboring cell has light or normal load. To enable the
UE to select a neighboring cell with relatively light load, it is strongly recommended
that this parameter be set to a value not higher than 0.
The default value of this parameter is -4 (-8dB)
Set this parameter through ADD CELLPUC/MOD CELLPUC
Qoffset1 offset 2
Content: This parameter defines the offset of Qoffset1RSCP when the load of a
neighboring cell is heavier than that of the center cell. To enable the UE to select a
neighboring cell with relatively light load, it is strongly recommended that this
parameter be set to a value not lower than 0.
Key parameters PUC

z
Qoffset2 offset 1
Qoffset2 offset 2
Qoffset1 offset 1
Content: This parameter defines the offset of Qoffset1RSCP when the current cell
has heavy load and the neighboring cell has light or normal load. To enable the UE to
select a neighboring cell with relatively light load, it is strongly recommended that this
parameter be set to a value not higher than 0.
The default value of this parameter is -4 (-8dB)
Qoffset1 offset 2
Content: This parameter defines the offset of Qoffset2EcNo when the load of a
neighboring cell is heavier than that of the center cell. To enable the UE to select a
neighboring cell with relatively light load, it is strongly recommended that this
parameter be set to a value not lower than 0.
Contents
Intra-Frequency Load Balancing

z
Intra-frequency Load Balancing (LDB) is performed to adjust

the coverage areas of cells by modifying PCPICH power
LDB affect UEs in all states
Intra-frequency Load Balancing (LDB) is performed to adjust the coverage areas of

cells according to the measured values of cell downlink power load. 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.
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.
Reduction of the pilot power will make the UEs at the edge of the cell 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.
LDB Procedure
Threshold
Cell TCP
Heavy?
Handover or
Light?
Cell Reselection
Normal?
RNC
Modify cell PCPICH

power
Updated PCPICH
POWER
NodeB
UE
The NodeB periodically reports the total TCP of the cell, and the LDB periodically triggers
the following activities:
Assessing the cell load level based on the total TCP
If the downlink load of a cell is higher than the value of the Cell overload threshold, it is
an indication that the cell is heavily loaded. In this case, the transmit power of the PCPICH needs to be reduced by a step, which is defined by the Pilot power adjustment
step parameter. However, if the current transmit power is equal to the value of the Min
transmit power of PCPICH parameter, no adjustment is performed.
If the downlink load of a cell is lower than the value of the Cell underload threshold, it is
an indication that the cell has sufficient remaining capacity for more load. In this case, the
transmit power of the P-CPICH increases by a step, which is defined by the Pilot power
adjustment step parameter, to help to lighten the load of neighboring cells. However, if
the current transmit power is equal to the value of the Max transmit power of PCPICH
parameter, no adjustment is performed.
Key parameters LDB

z
Parameter ID: NBMLdcAlgoSwitch LDB
The default value of this parameter is Off
Intra-frequency LDB period timer length
Parameter ID: IntraFreqLdbPeriodTimerLen
The default value of this parameter is 1800 (s)

Parameter ID: NBMLdcAlgoSwitch LDB
Content: This parameter is used to enable or disable the LDB algorithm..
Intra-frequency LDB period timer length
Parameter ID: IntraFreqLdbPeriodTimerLen
Content: This parameter specifies the length of the intra-frequency LDB period.
The default value of this parameter is 1800 (s)
Key parameters LDB

z
Cell overload threshold (Heavy)
Parameter ID: CellOverrunThd
Cell underload threshold (Light)
Parameter ID: CellUnderrunThd
Cell overload threshold

Parameter ID: CellOverrunThd
Content: If the downlink load of a cell exceeds this threshold, the algorithm can
decrease the pilot transmit power of the cell so as to extend the capacity of the whole
system.
Set this parameter through ADD CELLLDB / MOD CELLLDB
Cell underload threshold
Parameter ID: CellUnderrunThd
Content: If the downlink load of a cell is lower than this threshold, the algorithm can
increase the pilot transmit power of the cell so as to share the load of other cells.
Key parameters LDB

z
Pilot power adjustment step
Parameter ID: PCPICHPowerPace
The default value of this parameter is 2 (0.2dB)
Max transmit power of PCPICH
Parameter ID: MaxPCPICHPower
The default value of this parameter is 346 (34.6dBm)
Pilot power adjustment step

Parameter ID: PCPICHPowerPace
Value range: 0 to 10 , Step 0.1dB
Content: This parameter defines the step for the adjustment to the pilot power.
The default value of this parameter is 2, 0.2dB
Max transmit power of PCPICH
Parameter ID: MaxPCPICHPower
Value range: 100 to 500 ,Step 0.1dB
Content: This parameter defines the maximum transmit power of the P-CPICH in a cell.
This parameter has to be set according to the actual system environment, that is, for
example, cell coverage (radius) and geographical environment. If the maximum transmit
power of the P-CPICH is set too low, the cell coverage decreases. When a certain
proportion of soft handover area is ensured, any more increase in the pilot power
achieves no improvement on the performance of the downlink coverage.
Set this parameter through ADD PCPICH / MOD PCPICHPWR
Key parameters LDB

Min transmit power of PCPICH
Parameter ID: MinPCPICHPower
Min transmit power of PCPICH

Parameter ID: MinPCPICHPower
Value range: -100 to 500
Content: This parameter defines the minimum transmit power of the P-CPICH in a cell.
This parameter has to be set according to the actual system environment, that is, for
example, (radius) and geographical environment. If the minimum transmit power of the
P-CPICH is set too low, the cell coverage will be affected. The parameter has to be set
under the condition that a certain proportion of soft handover area is ensured or the
occurrence of coverage hole can be prevented.
Set this parameter through ADD PCPICH / MOD PCPICHPWR
Contents
Why we need CAC?

z
WCDMA is an interference limited system, after a new call is

admitted, the system load will be increased
If a cell is high loaded, a new call will cause ongoing user

dropped
We must keep the coverage planned by the Radio Network

Planning
CAC is needed under such scenarios:

1. RRC connection setup request
2. RAB setup and Bandwidth increasing
3. Handover
4. RB reconfiguration
Flow chart of CAC
The admission decision is based on:
Cell available code resource: managed in RNC
Cell available power resource, that is DL/UL load : measured in NodeB
NodeB resource state, that is, NodeB credits : managed in RNC
Available Iub transport layer resource, that is, Iub transmission bandwidth:
managed in RNC
HSPA user number (only for HSPA service)
Algorithm Switch of CAC

Admission control Switches can be set on RNC LMT:
z
Power CAC
Uplink CAC algorithm switch
Downlink CAC algorithm switch
NodeB Credit CAC
CAC algorithm switch : CacSwitch
Cell CAC algorithm switch: CRD_ADCTRL
HSDPA user number CAC
CAC algorithm switch :HSDPA_UU_ADCTRL
HSUPA user number CAC
CAC algorithm switch: HSUPA_UU_ADCTRL
Except the mandatory code and Iub resource admission control, the admission control based
on power and NodeB credit ,HSDPA User Number can be disabled through the LMT command:
Power CAC can be switched off by ADD CELLALGOSWITCH / MOD CELLALGOSWITCH
Uplink CAC algorithm switch (NBMULCACALGOSELSWITCH ) specifies the algorithm used
for power admission in the uplink.
Downlink CAC algorithm switch (NBMDLCACALGOSELSWITCH) specifies the algorithm
used for power admission in the downlink.
NodeB Credit CAC can be switched off by SET CACALGOSWITCH or ADD
CELLALGOSWITCH / MOD CELLALGOSWITCH
CAC algorithm switch (CacSwitch) specifies the NodeB level credit CAC algorithm
Cell CAC algorithm switch (CRD_ADCTRL) specifies the Cell level credit CAC algorithm
HSDPA user number CAC switched off by ADD CELLALGOSWITCH / MOD
CELLALGOSWITCH
HSDPA_UU_ADCTRL specifies whether to enable or disable the HSDPA admission control
algorithm.
HSUPA user number CAC switched off by ADD CELLALGOSWITCH / MOD
CELLALGOSWITCH
HSUPA_UU_ADCTRL specifies whether to enable or disable the HSUPA admission control
algorithm
CAC Based on Code Resource

z
Code Resource CAC functions in:
RRC connection setup
Handover
R99 services RAB setup
Note: RRC connection setup and Handover have higher priority
When a new service attempts to access the network, code resource admission is
mandatory.
1. For RRC connection setup requests, the code resource admission is successful if the
current remaining code resource is enough for the RRC connection.
2. For handover services, the code resource admission is successful if the current
remaining code resource is enough for the service.
3. For other R99 services, the RNC has to ensure that the remaining code does not
exceed the configurable threshold after admission of the new service.
4. For HSDPA services, the reserved codes are shared by all HSDPA services. Therefore,
the code resource admission is not needed.
So the RRC connection setup and Handover has higher priority to access a cell
CAC Based on Power Resource

z
UL and DL Power Resource CAC functions in:
R99 cell
R99 RAB setup
Handover
HSPA cell
RRC connection
R99 RAB setup
HSPA RAB setup
Handover
Note: RRC connection setup and Handover have higher priority

The UL CAC and DL CAC are independent .

The basic principle of Power CAC is: RNC predict the cell power load after the access. If
the load will be higher than a threshold, the admission is failed.
So, by setting different threshold for different access, we can realize different priorities.
Power CAC Algorithms

z
Algorithm 1: based on UL/DL load measurement and load

prediction (RTWP and TCP)
Algorithm 2: based on Equivalent Number of User (ENU)
Algorithm 3: loose call admission control algorithm
Huawei provide 3 Power CAC Algorithms

Algorithm 1: power resource admission decision based on power or interference.
Depending on the current cell load (uplink load factor and downlink transmitted carrier power)
and the access request, the RNC determines whether the cell load will exceed the threshold
upon admitting a new call. If yes, the RNC rejects the request. If not, the RNC accepts the
request.
Algorithm 2: power resource admission decision based on the number of equivalent
users.Based on Huawei testing and experience, The 12.2 kbit/s AMR traffic is used to
calculate the Equivalent Number of Users (ENU) of all other services in UL and DL. The
12.2 kbit/s AMR traffic's ENU is assumed to be 1. Depending on the current number of
equivalent users and the access request in UL and DL, the RNC determines whether the
number of equivalent users will exceed the threshold upon admitting a new call. If yes, the
RNC rejects the request. If not, the RNC accepts the request.
Algorithm 3: power resource admission decision based on power or interference, but with
the estimated load increment always set to 0.Depending on the current cell load (uplink load
factor and downlink TCP) and the access request, 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.
Basic principle of Uplink CAC Algorithm 1

Admission request
UL = 1
Get current RTWP, and calculate the

current load factor
Get the traffic characteristic, and

estimate the increment of load factor
UL _ predicted = UL + + CCH
Calculate the predicted load factor
Smaller than
the threshold?
admitted
PN
RTWP
rejected
End of UL CAC
Pn is uplink receive background noise.

The procedure for uplink power resource decision is as follows:
1. The RNC obtains the uplink RTWP of the cell, and calculate the current uplink load
factor.
2. The RNC calculates the uplink load increment UL based on the service request.
3. The RNC uses the formula UL,predicted=UL + UL to forecast the uplink load
factor.
4. By comparing the forecasted uplink load factor UL,predicted with the corresponding
threshold ,the RNC decides whether to accept the access request or not.
Basic principle of Downlink CAC Algorithm1
The procedure for downlink power resource decision is as follows:

1. The RNC obtains the cell downlink TCP, and calculates the downlink load factor by
multiplying the maximum downlink transmit power by this TCP.
2. The RNC calculates the downlink load increment P based on the service request and
the current load.
3. The RNC forecasts the downlink load factor.
4. By comparing the downlink load factor with the corresponding threshold (DL threshold
of Conv AMR service, DL threshold of Conv non_AMR service, DL threshold of other
services, DL Handover access threshold), the RNC decides whether to accept the
access request or not.
Basic principle of CAC Algorithm 2

Admission request
ENU
Get current total ENU

Get the traffic characteristic, and
estimate the increment of ENU
Smaller than
the threshold?
admitted
ENU
i =1
ENU new
ENU total ( N + 1) = ENU total ( N ) + ENU new
Calculate the predicted ENU
total
(N ) =
ENULoad = ENU total ( N + 1) / ENU max
rejected
End of UL/DL CAC

The procedure for ENU resource decision is as follows:

1. The RNC obtains the total ENU of all exist users ENUtotal.
2. The RNC get the ENU of the new incoming user ENUnew.
3. The RNC forecast the ENU load.
4. By comparing the forecasted ENU load with the corresponding threshold (the same
threshold as power resource), the RNC decides whether to accept the access request
or not.
The ENUmax can be set by LMT, the ENUnew and ENUi is determined by Huawei
algorithm, there is an example in next slide.
Power CAC for RRC connection Setup

z
For the RRC connection request is, tolerance principles are

applied :
Emergency call, Detach , Registration
Direct Admission
RRC connection request for other reasons
UL/ DL OLC Trigger threshold Admission
To ensure that the RRC connection request is not denied by mistake, tolerance principles
are applied.
The admission decision is made for the following reasons of the RRC connection request:
1. For the RRC connection request for the reasons of emergency call, detach or
registration, direct admission is used ,that is no limitation.
2. For the RRC connection request for other reasons, UL/DL OLC Trigger
threshold is used for admission. By default, the OLC trigger threshold is
relatively high (DL/UL 95%), which make the RRC connections are easily set
up.
UL Power CAC for R99 Cell (Algorithm1)

z
For R99 DCH RAB Setup, The RNC uses the following formula
to predict the uplink load factor :
UL _ predicted = UL + UL + UL CCH
Where the
PN
RTWP
By comparing the predicted uplink load factor UL,predicted with the
UL = 1
corresponding threshold ,the RNC decides whether to accept the

access request or not
The threshold for Conv AMR service , Conv non_AMR service , Other R99 services ,
Handover are set independently, which provide different priorities.
Normally, Other R99 services < Conv non_AMR service services < Conv AMR
service < Handover
The uplink load increment UL is determined by :
1. The Eb/No of the new incoming call
2. The uplink load increment is proportional to the value of Eb/No.
3. UL neighbor interference factor
4. Active Factor of the new incoming call
DL Power CAC for R99 Cell (Algorithm1)

z
For R99 DCH RAB Setup, The RNC uses the following formula to
predict the downlink load factor :
DL _ predicted = DL + DL + DL CCH
Where the
DL =
TCP
Pmax
DL =
DL
Pmax
By comparing the predicted downlink load factor DL,predicted with

the corresponding threshold ,the RNC decides whether to accept
the access request or not
The threshold for Conv AMR service , Conv non_AMR service , Other R99 services ,
Handover are set independently, which provide different priorities.
Normally, Other R99 services < Conv non_AMR service services < Conv AMR service <
Handover
The downlink load increment DL is determined by :
1. The Eb/No of the new incoming call
2. Non-orthogonality factor
3. Current transmission carrier power
4. Active Factor of the new incoming call
UL Power CAC for HSPA Cell (Algorithm1)

z
The power increment of an HSUPA service is related to Ec/No,

GBR requirement, neighboring interference factor, active factor of
the service. The formula of UL power CAC for HSUPA is similar to
that for R99
After RSEPS measurement is introduced, the UL RTWP is divided

into two parts:
Controllable part
The UL interference generated by E-DCH scheduling services belong to

the controllable part
Uncontrollable part
RSEPS: Received scheduled E-DCH power share

z
E-DCH scheduling service consists of following two types:
TypeA: all UEs for which this cell is the serving E-DCH cell
The uplink load generated by TypeA E-DCH scheduling service is defined as follows:
UL EDCH , S =
RSEPS
RTWP
TypeB: all UEs for which this cell is
NOT the serving EDCH-cell
The uplink load generated by
TypeB E-DCH scheduling service

is defined by UL,EDCH,f,
which is fixed to zero
The Uplink uncontrollable load
Is defined as follows:
UL , non ctrl = UL UL , EDCH , s UL , EDCH , f


z
UL Power CAC for HSUPA Scheduling Services and HSUPA Non-Scheduling Services
RNC admits HSUPA scheduling service in either of the following cases
Formula 1,2 or 3 is fulfilled
Formula 4 is fulfilled
RNC admits HSUPA Non-scheduling service in either of the following cases
Formula 1,2 or 3 is fulfilled
Formula 4 and 5 are fulfilled
ThdL is the Low priority HSUPA user PBR threshold of the current cell
ThdE is the Equal priority HSUPA user PBR threshold of the current cell
ThdGE is the High priority HSUPA user PBR threshold of the current cell
HS-DPCCH is the value of the UL HS-DPCCH reserve factor parameter, which defines the factor of
UL HS-DPCCH resource reserved
thd is the cell UL admission threshold for specific type of service, that is UL threshold of Conv
AMR service, UL threshold of Conv non_AMR service, UL threshold of other services or UL
handover access service threshold

z
UL Power CAC for R99 service in HSPA cell
Uncontollable interference must be kept within a given

range. The purpose is to ensure the stability of system and
to prevent non-scheduling services and DCH services
from seizing the resources of HSUPA services
UL , non ctrl + UL + UL , cch + HS DPCCH < thd

UL + UL + UL., cch + HS DPCCH < thd total
RNC admits R99 services if formula 1 and 2 are fulfilled
thd-total is the UL total power threshold of the current cell

thd is the cell UL admission threshold for specific type of service, that is UL threshold of Conv
AMR service, UL threshold of Conv non_AMR service, UL threshold of other services or UL
handover access service threshold
DL Power CAC for HSPA Cell (Algorithm1)

z
DL Power incremental estimation for DCH RAB in HSPA

cell is similar to the DCH RAB in R99 cell
DL Power incremental estimation for HSDPA RAB PDL is

made based on GBR, Ec/No, Non-orthogonality factor

z
DL power CAC for R99 service in HSPA cell
RNC admits R99 service (i.e. DCH RAB) in either of the

following situations:
Pnon-hspa is the current non-HSDPA power

Pcch-res is the power reserved for the common channel
Pmax is the cell maximum transmit power
Thdnon-hspa-cac is the cell DL admission threshold for different types of service, that is DL
threshold for Conv AMR service, DL threshold for Conv non-AMR service, DL threshold for
other service or DL handover access threshold
Ptotal is the current downlink transmitted carrier power
Thdtotal-cac is the threshold of cell DL total power. It is defined by the DL total power threshold
parameter
GBP is power requirement for GBR
Phsupa-res is the power reserved for HSUPA downlink control channels (E-AGCH/E-RGCH/E-HICH)
Pmax-hspa is the maximum available power for HSPA. Its value is associated with the HSDPA
power allocation mode.

z
DL power CAC for HSDPA RAB in HSPA cell
RNC admits the HSDPA streaming service in any of the following situations:
Formulas 3 and 4 are fulfilled
RNC admits the HSDPA BE service in any of the following situations:
PBRstrm is the provided bit rate of all existing streaming services

Thdhsdap-str is the admission threshold for streaming PBR decision. It is defined by the Hsdpa
streaming PBR threshold parameter
PBRbe is the provided bit rate of all existing BE services
Thdhsdap-be is the admission threshold for BE PBR decision. It is defined by the Hsdpa best effort
PBR threshold parameter
GBR is the power requirement for GBR
Phsupa-res is the power reserved for HSUPA downlink control channels (E-AGCH/E-RGCH/E-HICH)
Pmax-hspa is the maximum available power for HSPA. Its value is associated with the HSDPA
power allocation mode.
Ptotal is the current downlink transmitted carrier power
Pmax is the cell maximum transmitted power
Thdtotal-cac is the threshold of cell DL total power, which is defined by the DL total power
threshold parameter
Pcch-res is the power reserved for the common channels
Pnon-hspa is the current non-HSDPA power

z
DL power CAC for HSUPA control channels in HSPA cell
The power of downlink control channels (E-AGCH/E-RGCH/EHICH) are reserved by DL HSUPA reserved factor. Therefore,
the power admission for these channels is NOT needed
Power CAC for Algorithm2

z
For R99 and HSDPA RAB, The RNC uses the following formula
to predict the uplink load factor :
(ENUtotal + ENUnew) / ENUmax
By comparing the forecasted ENU load with the corresponding

threshold ,the RNC decides whether to accept the access request
or not
ENUtotal is the total ENU of all existing users.

ENUnew is ENU of the new incoming user .
ENUmax is the configured maximum ENU (UL total equivalent user number or DL total
nonhsdpa equivalent user number) .
The threshold for Algorithm2 are the same with Algorithm1,for Conv AMR service ,
Conv non_AMR service , Other R99 services , Handover , HSDPA are set independently:
Service Type
Admission Threshold
UL DCH/HSUPA
UL threshold of Conv AMR service

UL threshold of Conv non_AMR service
UL threshold of other services
UL Handover access threshold
DL DCH
DL threshold of Conv AMR service

DL threshold of Conv non_AMR service
DL threshold of other services
DL Handover access threshold
HSDPA
DL total power threshold
Typically ENU (equivalent number of users) for different services (with activity factor to be
100%)
Service Type
Admission Threshold
UL DCH/HSUPA

DL DCH

HSDPA
Key parameters
z
Parameter ID: UlNonCtrlThdForAMR
The default value of this parameter is 75%
Parameter ID: UlNonCtrlThdForNonAMR

Parameter ID: UlNonCtrlThdForAMR
Value range: 0 to 100 %
Content: The uplink threshold for the AMR conversational service is used for the uplink
admission of AMR conversational service users. The threshold is shared by algorithm 1,
algorithm 2 and algorithm 3.
Set this parameter through ADD CELLCAC / MOD CELLCAC
Parameter ID: UlNonCtrlThdForNonAMR
Content: The downlink threshold for the AMR conversational service is used for the
downlink admission of AMR conversational service users. The threshold is shared by
algorithm 1, algorithm 2 and algorithm 3.
Key parameters
z
Parameter ID: UlNonCtrlThdForOther
Parameter ID: UlNonCtrlThdForHo

Parameter ID: UlNonCtrlThdForOther
Content: This parameter is the uplink threshold for services other than the
conversational service. It is used for uplink admission of other services. The threshold is
shared by algorithm 1, algorithm 2 and algorithm 3.
Parameter ID: UlNonCtrlThdForHo
Content: The uplink handover threshold is used for uplink admission of handover users.
The parameter is useful only to uplink inter-frequency handovers. Do not make the
admission decision in the uplink soft handover. The threshold is shared by algorithm 1,
algorithm 2 and algorithm 3.
Key parameters
z
Parameter ID: DLCONVAMRTHD
Parameter ID: DLCONVNAMRTHD

Parameter ID: DLCONVAMRTHD
Content: The downlink threshold for the AMR conversational service is used for the
downlink admission of AMR conversational service users. The threshold is shared by
algorithm 1, algorithm 2 and algorithm 3.
Parameter ID: DLCONVNAMRTHD
Content: The downlink threshold for the non-AMR conversational service is used for the
downlink admission of non-AMR conversational service users. The threshold is shared
by algorithm 1, algorithm 2 and algorithm 3.
Key parameters
z
Parameter ID: DLOTHERTHD
Parameter ID: DLHOTHD

Parameter ID: DLOTHERTHD
Content: This parameter is the downlink threshold for services other than the
conversational service. It is used for downlink admission of users of other services. The
threshold is shared by algorithm 1, algorithm 2 and algorithm 3.
Set this parameter through ADD CELLCAC/MOD CELLCAC
Parameter ID: DLHOTHD
Content: The downlink handover threshold is used for downlink admission of handover
users. The threshold is shared by algorithm 1, algorithm 2 and algorithm 3.
Key parameters
z
Parameter ID: DLCELLTOTALTHD
Hsdpa streaming PBR threshold
Parameter ID: HSDPASTRMPBRTHD
Hsdpa best effort PBR threshold
Parameter ID: HSDPABEPBRTHD

Parameter ID: DLCELLTOTALTHD
Content: This parameter specifies the total downlink power threshold of the cell.
Parameter ID: HSDPASTRMPBRTHD
Content: This parameter specifies the average throughput admission threshold of the
HSDPA streaming traffic.
Parameter ID: : HSDPABEPBRTHD
Content: This parameter specifies the average throughput admission threshold of the
HSDPA best effort traffic.
Key parameters
z
UL total equivalent user number
Parameter ID: ULTOTALEQUSERNUM
The default value of this parameter is 80
DL total equivalent user number
Parameter ID: DLTOTALEQUSERNUM
UL total equivalent user number

Parameter ID: ULTOTALEQUSERNUM
Content: When algorithm 2 is used, this parameter defines the total equivalent number
of users corresponding to the 100% uplink load.
DL total equivalent user number
Parameter ID: DLTOTALEQUSERNUM
Content: When algorithm 2 is used, this parameter defines the total equivalent number
of users corresponding to the 100% downlink load.
CAC Based on NodeB Credit Resource

z
When a new service accesses the network, NodeB credit

resource admission is optional
The principles of NodeB credit admission control are similar

to those of power resource admission control, that is, to
check in the local cell whether the remaining credit can
support the requesting services
CE stands for NodeB credit on RNC side and for Channel Element on NodeB side. It is
used to measure the channel demodulation capability of the NodeBs
The resource of one 12.2kbps voice service, including 3.4kbps signaling on the DCCH,
consumed in baseband is defined as one CE. If there is 3.4kbps signaling on the DCCH,
but no voice channel, one CE is consumed.The credit resource are divided into several
resource pools. Each resource pool is shared by a local cell.
According to the common and dedicated channels capacity consumption laws, as well as
the addition, removal, and reconfiguration of the 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 of the local cell group (and local cell , if any)
based on the spreading factor.
the UL Capacity Credit and DL Capacity Credit are separate, so the CAC is performed in
the UL and DL, respectively.

z
For DCH service, MBR is used to calculate the NodeB

Credit based on spreading factor :
The total NodeB Credit Resource of a local cell is depend on

the configuration.
Direction
Spreading
Factor
Corresponding Credits Consumed
DL
256
UL
256
DL
128
UL
64
DL
128
UL
64
DL
32
UL
16
DL
64
UL
32
DL
32
UL
16
DL
16
UL
10
DL
UL
20
Typical Traffic Class
3.4 kbit/s SRB
13.6 kbit/s SRB
12.2 kbit/s AMR
64 kbit/s VP
32 kbps PS
64 kbit/s PS
128 kbit/s PS
384 kbit/s PS

z
For HSUPA service, the rate used to calculate the

spreading factor is MBR

z
When a new service tries to access the network, the credit

resource admission CAC functions in :
Handover service
The other services
For an RRC connection setup request, the credit resource admission is successful if the current
remaining credit resource is sufficient for the RRC connection.
For a handover service, the credit resource admission is successful if the current remaining credit
resource is sufficient for the service.
For other services, the RNC has to ensure that the remaining credit does not exceed the
configurable thresholds after admission of the new services.
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.
UL Capacity Credit and DL Capacity Credit are separate, the credit resource admission is
implemented in the UL and DL, respectively.
Key parameters
z
Ul HandOver Credit Reserved SF
Parameter ID: UlHoCeResvSf
The default value of this parameter is SF16
Dl HandOver Credit and Code Reserved SF
Parameter ID: DlHoCeCodeResvSf
Ul HandOver Credit Reserved SF

Parameter ID: UlHoCeResvSf
Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFF
Content: The spreading factor specified by this parameter is used to define the uplink
credit resource reserved for handover services.
SFOFF means that none of resources are reserved for handover services. If the
remaining uplink resource cannot fulfill the requirement for the reserved resource after
the admission of a new service, the service is rejected.
Dl HandOver Credit and Code Reserved SF
Parameter ID: DlHoCeCodeResvSf
Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256, SFOFF
Content: The spreading factor specified by this parameter is used to define the downlink
credit and channelized code resources reserved for handover services.
SFOFF means that none of the resources is reserved for handover. If the remaining
downlink resource cannot fulfill the requirement for the reserved resource after the
access of a new service, the service is rejected.
CAC Based on Iub Interface Resource

z
The CAC of the Iub transmission resources is similar
Admission Control is used to determine whether the Iub

resources are enough to accept a new access request
It functions in:
RRC connection setup and Services RAB setup
Handover
A user accessing the network from a path should go through the admission of the path,
resource group, and physical port in turn. The user that passes all the admission can be
successfully admitted by the transport layer.
Path means AAL2 PATH, IP PATH
The physical ports correspond to IMA, UNI, FRAATM, NCOPT, ETHER, PPP, and MLPPP.
The priority of the 2 types of access follows : Handover >RRC connection setup and
Services RAB setup

z
Iub Overbooking
The Iub overbooking feature considers the statistic multiplexing

of service activities and multiple users
Admit more users, increases the resource utilization on the Iub

interface.
The Iub overbooking feature considers the statistic multiplexing of service activities and
multiple users. Through the admission of more users, Iub overbooking increases the
resource utilization on the Iub interface.
If the RNC allocates the maximum bandwidth to the subscriber when a service is
established, a large proportion of the Iub transmission bandwidth is unused. For example,
downloading a 50 KB page takes only about one second, but reading this page needs
dozens of seconds. Thus, over 90% of the Iub transmission bandwidth is not used.
To save the Iub transmission bandwidth for operator use, Huawei provides the Iub
overbooking function, which applies an admission control mechanism to access the
service.

z
Iub Overbooking
CS voice services
Service rate:12.2 kbit/s
SID
PS interactive and background services
Download time
Reading time
The UMTS supports four traffic classes: conversational, streaming, interactive, and
background.
The transmission rate varies with the traffic class as follows:
For Circuit Switched (CS) conversational services, the channel transmits voice signals at
a certain rate (for example, 12.2 kbit/s) during a conversation and only transmits Silence
Descriptors (SIDs) at intervals when there is no conversation.
For Packet Switched (PS) interactive and background services, such as web browsing,
there is data transmitted during data downloading. After a web page has been
downloaded, and when the user is reading the page, however, there is very little data to
transfer.

z
Iub Overbooking
CS voice services
PS interactive and background services
Activity Factor
GBR
MML
SET DEFAULTFACTORTABLE
SET USERGBR
SET CORRMALGOSWITCH (IUB_OVERBOOKING_SWITCH)
ADD AAL2PATH
ADD IPPATH
Use SET DEFAULTFACTORTABLE to set a default of Activity Factor table for all the
services.
Use SET USERGBR to set GBR for BE services
Use SET CORRMALGOSWITCH (IUB_OVERBOOKING_SWITCH) to define the switch
of Iub overbooking
CAC Based on Number of HSPA Users

z
HSPA user number can be limited in:
Cell level
maximum number of HSPA users in a cell
NodeB level
Maximum number of HSPA users in all the cells configured in

one NodeB
When the HSDPA_UU_ADCTRL is on, the HSDPA services have to undergo HSDPA
user number admission decision.
When a new HSDPA service attempts to access the network, it is admitted if the number
of HSDPA users in the cell and that in the NodeB do not exceed the associated
thresholds
When the HSUPA_UU_ADCTRL is on, the HSUPA services have to undergo HSUPA
user number admission decision.
When a new HSUPA service attempts to access the network, it is admitted if the number
of HSUPA users in the cell and that in the NodeB do not exceed the associated
thresholds
Key parameters
z
HSDPA_UU_ADCTRL
Maximum HSDPA user number
Parameter ID: MaxHSDSCHUserNum
HSDPA_UU_ADCTRL
Parameter ID: HSDPA_UU_ADCTRL
Parameter ID: HSUPA_UU_ADCTRL
Maximum HSUPA user number
Parameter ID: MaxHsupaUserNum
Maximum HSDPA user number

Parameter ID: MaxHSDSCHUserNum
Content: This parameter specifies the maximum number of HSDPA users in a cell.
HSDPA_UU_ADCTRL
Value range: 0 ,1
Content: This parameter specifies whether to enable or disable the HSDPA admission control algorithm.
Set this parameter through ADD CELLALGOSWITCH / LST CELLALGOSWITCH/MOD
CELLALGOSWITCH
HSUPA_UU_ADCTRL
Value range: 0 ,1
Content: This parameter specifies whether to enable or disable the HSDPA admission control algorithm.
Set this parameter through ADD CELLALGOSWITCH / LST CELLALGOSWITCH/MOD
CELLALGOSWITCH
Maximum HSUPA user number
Parameter ID: MaxHsupaUserNum
Content: This parameter specifies the maximum number of HSDPA users in a cell.
Content: This parameter specifies the maximum number of HSUPA users in a cell.
Set this parameter through ADD CELLCAC / LST CELLCAC / MOD CELLCAC
Contents
Why we need IAC?

z
The disadvantage of CAC
For PS NRT (Non-Real Time) services, CAC is not flexible
No consideration about the priority of different users
No consideration about Directed Retry after CAC rejection
Intelligent means the algorithm can increase admission

successful rate
CAC limits the setup of RRC and RAB . When the cell is overloaded , the CAC will cause
access failure.
In order to improve the access success rate the Intelligent Access Control (IAC) algorithm is
used to improve the access success rate. The IAC procedure includes rate negotiation,
Call Admission Control (CAC), preemption, queuing, and Directed Retry Decision (DRD).
IAC Overview
z
The access procedure (include the IAC)
As shown in the Figure, the procedure for the UE access includes the procedures for RRC
connection setup and RAB setup. The success in the RRC connection setup is one of the
prerequisites for the RAB setup.
During the RRC connection processing, if resource admission fails, DRD and redirection apply.
During the RAB processing, the RNC performs the following steps:
Performs RAB DRD to select a suitable cell to access, for service steering or load balancing.
Performs rate negotiation according to the service requested by the UE.
Performs cell resource admission decision. If the admission is passed, UE access is granted.
Otherwise, the RNC performs the next step.
Selects a suitable cell, according to the RAB DRD algorithm, from the cells where no admission
attempt has been made, and then goes to rate negotiation and cell resource admission again. If
all DRD admission attempts to the cells fail, go to 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, queuing.
Makes a queuing attempt. If the queuing is successful, UE access is granted. If the queuing fails
or is not supported, the RNC Rejects UE access.
IAC - RRC Connection Processing
When a new service accesses the network, an RRC connection must be set up first. If the
RRC connection request is denied, DRD is performed. If DRD also fails, RRC
redirection is performed to direct the UE to an inter-frequency or inter-RAT cell
through cell reselection.
After the RNC receives the RRC CONNECTION REQUEST message, the CAC algorithm
decides whether an RRC connection can be set up between the UE and the current
cell.
If the RRC connection can be set up between the UE and the current cell, the RNC sends
an RRC CONNECTION SETUP message to the UE. If the RRC connection cannot
be set up between the UE and the current cell, the RNC takes the following
actions:
RRC DRD :
If the DRD_SWITCH is set to 0, the RRC DRD fails, and RRC redirection is performed.
Else, the RNC performs the following steps:
1. The RNC selects inter-frequency neighboring cells of the current cell. These
neighboring cells are suitable for blind handovers.
2. 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:
(CPICH_Ec/No)RACH > DRD_Ec/No nbcell
where
(CPICH_Ec/No)RACH is the cached CPICH Ec/N0 value included in the RACH
measurement report.
DRD_Ec/No nbcell is the DRD Ec/N0 Threshold set for the inter-frequency
neighboring cell.
3. 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.
1. If the admission is successful, the RNC initiates an RRC DRD procedure.
2. 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.
4. If the candidate cell list does not contain any cell, the RRC DRD fails. The RNC performs the next
step, that is, RRC redirection.
5. RRC redirection, the RNC performs the following steps:
1. The RNC selects all inter-frequency cells of the local cell.
2. The RNC selects candidate cells. That is, exclude the cells to which inter-frequency RRC
DRD attempts have been made from the cells selected in the previous step.
3. If more than one candidate cell is available, the RNC selects a cell randomly and redirects
the UE to the cell.
Key parameters
z
RRC redirect switch
Parameter ID: RrcRedictSwitch
The default value of this parameter is

Only_To_Inter_Frequency
DRD Ec/N0 threshold
Parameter ID: DRDEcN0Threshhold
The default value of this parameter is -18-9 dB
RRC redirect switch

Parameter ID: RrcRedictSwitch
Value range: OFF, Only_To_Inter_Frequency, Allowed_To_Inter_RAT
Content: This parameter specifies the RRC redirection strategy.
The default value of this parameter is Only_To_Inter_Frequency
Set this parameter through SET DRD
DRD Ec/N0 threshold
Parameter ID: DRDEcN0Threshhold
Content: If the measured Ec/N0 value of the neighbor cell is less than this
parameter, this neighboring cell cannot be selected to be the candidate DRD
cell.
The default value of this parameter is -18-9 dB
Set this parameter through ADD INTERFREQNCELL
IAC PS Rate Negotiation

z
PS Service Rate Negotiation Includes:
Maximum expected rate negotiation
Initial rate negotiation
Target rate negotiation
Rate negotiation includes the maximum expected rate negotiation, initial rate negotiation, and target rate negotiation.
When setting up, modifying, or admitting a PS service (conversational, streaming, interactive, or background service)
the RNC and the CN negotiate the rate according to the UE capability to obtain the maximum expected rate while
ensuring a proper QoS.
For a non-real-time service in the PS domain, the RNC selects an initial rate to allocate bandwidth for the service
when Setup or UE state transits from CELL_FACH to CELL_DCH based on cell code and credit resource
The Initial rate selection is affected by 2 algorithm switches: RAB Downsizing Switch, DCCC Switch
For DCH
For HSUPA
For a non-real-time service in the PS domain, if cell resource admission fails, the RNC chooses a target rate to
allocate bandwidth for the service based on cell resource in Service setup or Soft handover
Key parameters
z
RAB_Downsizing_Switch
Parameter ID: RAB_DOWNSIZING_SWITCH
The default value of this parameter is 1 (on)
UL/DL BE traffic Initial bit rate
Parameter ID:
ULBETRAFFINITBITRATE / DLBETRAFFINITBITRATE
The default value of this parameter is D64 64k
RAB_Downsizing_Switch
Parameter ID: RAB_DOWNSIZING_SWITCH
Value range: (0,1)
Content: This parameter specifies whether to support the RAB downsizing function.
The default value of this parameter is 1 (on)
When this parameter is set to 1, the RAB downsizing function is applied to
determine the initial bit rate based on cell resources (code and credit). .
Set this parameter through SET CORRMALGOSWITCH
UL/DL BE traffic Initial bit rate
Parameter ID: ULBETRAFFINITBITRATE / DLBETRAFFINITBITRATE
Value range: D8, D16, D32, D64, D128, D144, D256, D384, D768, D1024, D1536,
D1800, D2048 k
Content: This parameter defines the uplink initial access rate of background and
interactive services in the PS domain.
The default value of this parameter is D64 64k
Set this parameter through SET FRC
IAC RAB Directed Retry Decision

z
RAB Directed Retry Decision (DRD) is used to select a

suitable cell for the UE to try an access
Inter-frequency DRD
Service Steering
Load Balancing
Inter-RAT DRD
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. For inter-frequency DRD, the service steering and load balancing algorithms are
available.
After receiving a RANAP RAB ASSIGNMENT REQUEST, the RNC initiates an RAB
DRD procedure to select a suitable cell for RAB processing during access control.
The RNC performs inter-frequency DRD firstly. If all admission attempts of interfrequency DRD fail, the RNC performs an inter-RAT DRD. If all admission attempts of
inter-RAT DRD fail, the RNC selects a suitable cell to perform preemption and
queuing .
Relation Between Service Steering DRD and Load Balancing DRD
When both service steering DRD and load balancing DRD are enabled, the general
principles of inter-frequency DRD are as follows:
Service steering DRD takes precedence over load balancing DRD. That is,
preferably take service priorities into consideration.
To services of the same service priority, load balancing applies.
IAC RAB Directed Retry Decision

RAB Directed Retry Switchs
Scenario
Switch
Description
DRD switch
DRD_SWITCH
This is the primary DRD algorithm switch. The

secondary DRD switches are valid only when
this switch is on.
Combined
services
COMB_SERV_DRD_SWITCH
DRD is applicable to combined services only

when this switch is on.
HSDPA service
HSDPA_DRD_SWITCH
DRD is applicable to HSDPA services only

HSUPA service
HSUPA_DRD_SWITCH
DRD is applicable to HSUPA services only

RAB modification
RAB_MODIFY_DRD_SWITCH
DRD is applicable to RAB modification only

DCCC
RAB_DCCC_DRD_SWITCH
DRD is applicable to traffic-volume-based

DCCC procedure or UE state transition, only
RAB setup
RAB_SETUP_DRD_SWITCH
DRD is applicable to RAB setup only when this

switch is on.
DRD algorithm switch

Parameter ID: DRDSWITCH
The default value of this parameter is off
IAC Inter-frequency DRD

z
Inter-Frequency DRD for Service Steering
DRD for Service Steering is based on Service priorities of

cells ,include:
R99 RT services priority
R99 NRT services priority
HSPA services priority
Other services priority
Called Service priority group
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.
Cell service 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 service priorities in each cell is called Service priority group , which is identified by
the Service priority group Identity 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 check the service type firstly ,
then, selects a cell with a high priority for the service, that is, a cell that has a small
value of service priority.

z
Inter-Frequency DRD for Service Steering

Service
priority group
Identity
Service priority
Service priority
Service priority
service
service
service
An example
priority group
of R99 RT of service
of R99 NRT
of HSPA
Service
priority of
other service
Cell A and cell B are of different frequencies.

Assume that the service priority groups given in the table are defined on an RNC, 2
groups of service priorities are defined.
Then ,Cell A is configured with service priority group 1. Cell B is configured with service
priority group 2
If UE requests a R99 RT service in cell A ,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.

z
Inter-Frequency DRD procedure for Service Steering
The procedure for the service steering DRD is as follows:

1The RNC determines candidate cells to which blind handovers can be performed and sorts the
candidate cells into a descending order according to service priority.
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 Ec/No requirements of inter-frequency DRD (DRD
Ec/N0 Threshold )
The candidate cell supports the requested service.
2The RNC selects a target cell from the candidate cells in order of service priority for UE access.
3The 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
choose next candidate cell.
4If admission decisions have been made in all the candidate cells
For HSPA access, 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.
For DCH access, the RNC initiates an inter-RAT DRD.
Key parameters
z
Service differential drd switch
Parameter ID: ServiceDiffDrdSwitch
Service priority group Identity
Parameter ID: PriorityServiceForR99RT
Service differential drd switch

Parameter ID: ServiceDiffDrdSwitch
Value range: ON, OFF
Content: This parameter specifies whether to enable the service steering DRD algorithm
The default value of this parameter is OFF.
Set this parameter through ADD CELLDRD
Service priority of R99 RT service
Parameter ID: SpgId
Value range: 1 to 8
Content: This parameter uniquely identifies a group of service priorities that map to cells
and indicate the support of each cell for the following service types: R99 RT service,
R99 NRT service, HSPA service, and other services.
Set this parameter through ADD SPG
Key parameters
z
Service priority of R99 NRT service
PriorityServiceForR99NRT
Service priority of HSPA service
Parameter ID: SpgId
PriorityServiceForHSPA
Service priority of Other service
PriorityServiceForExtRab

Parameter ID: PriorityServiceForR99RT
Value range: 0 to 7
Content: This parameter specifies the support of the cells with a specific Service priority
group Identity for R99 RT services.
The value 0 means that these cells do not support R99 RT services.
For the values 1 through 7, the service priority is inversely proportional to the value, that is,
the value 7 indicates the lowest service priority, whereas the value 1 indicates the highest.
Service priority of R99 NRT service

Parameter ID: PriorityServiceForR99NRT
Value range: 0 to 7
group Identity for R99 NRT services.
The value 0 means that these cells do not support R99 NRT services.
Service priority of HSPA service
Parameter ID: PriorityServiceForHSPA
Value range: 0 to 7
group Identity for HSPA services.
The value 0 means that these cells do not support HSPA services.
Service priority of Other service
Parameter ID: PriorityServiceForExtRab
Value range: 0 to 7
group Identity for Other services .
The value 0 means that these cells do not support Other service .

z
Inter-Frequency DRD for Load Balance
The resources triggering DRD for Load Balance include:
DL Power
OVSF code
Any of these 2 resources can trigger inter-frequency DRD for

Load Balance
Load balancing considers two resources: power, and code.

If both are activated, power-based load balancing DRD takes precedence over codebased load balancing DRD.
Code-based load balancing DRD is applicable to only R99 services because HSDPA
services use reserved codes.

z
Inter-Frequency DRD procedure for DL Power Load Balance
The procedure for the service steering DRD is as follows:

1The RNC determines candidate cells to which blind handovers can be performed and sorts
the candidate cells into a descending order according to service priority.
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 Ec/No requirements of inter-frequency
DRD (DRD Ec/N0 Threshold )
The candidate cell supports the requested service.
2The RNC determines whether the DL radio load of the current cell is lower than the power
threshold for load balancing DRD (condition 1 )
power threshold for load balancing DRD is CAC parameter.
If the DL load of the current cell is lower than the threshold, the service tries admission to
the current cell.
If the DL load of the current cell is equal to or higher than the threshold, the RNC checks
the candidate cells to try to find out a target cell for UE access.
RNC will check if there is a candidate cell will meet the following condition (condition 2 ) :
Ptotal_thd,nbcell is DL total power threshold for the inter-frequency neighboring cell.

Pload,nbcell is total power load of the inter-frequency neighboring cell. For a R99 cell, it is
the Downlink Transmitted Carrier Power of the cell, and for an HSPA cell, it is the nonHSDPA power and GBP.
Ptotal_thd,cutcell is DL total power threshold for the current cell.
Pload,cutcell is the total downlink load of the current cell.
Ploadoffset is the Power balancing drd offset of the current cell.
Then, the RNC selects the target cell as follows:

If there is only one inter-frequency neighboring cell that meets the load balancing DRD
conditions, the RNC selects this cell as the target cell.
If there are multiple such cells, the RNC selects the cell with the lightest load as the
target cell.
If there is no such cell, the RNC selects the current cell as the target cell.
3The 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 choose next candidate cell.
4If admission decisions have been made in all the candidate cells
For HSPA access, 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.
For DCH access, the RNC initiates an inter-RAT DRD.
Key parameters
z
Power balance DRD switch on DCH
Parameter ID: LdbDrdSwitchDCH
Power balance DRD switch on HSDPA
Parameter ID: LdbDrdSwitchHSDPA
Max transmit power of cell
Parameter ID: MaxTxPower
The default value of this parameter is 430 (43dBm)
Dl power balancing drd power threshold for DCH
Parameter ID: LdbDRDOffsetDCH
Dl power balancing drd power threshold for HSDPA
Parameter ID: LdbDRDOffsetHSDPA
Power balancing drd switch

Parameter ID: PowerBalancingDrdSwitch
Content: This parameter specifies whether to enable the power-based load
balancing DRD algorithm .
Set this parameter through SET DRD / ADD CELLDRD
Max transmit power of cell
Parameter ID: MaxTxPower
Value range: 0 to 500 , step:0.1dBm
Content: This parameter specifies the sum of the maximum transmit power of
all the downlink channels in a cell.
The default value of this parameter is 430 (43dBm).
Set this parameter through MOD CELL
Power balancing drd offset
Parameter ID: LoadBalanceDRDOffset
Value range: 0% to 100%
Content: This parameter specifies the load offset threshold of the current cell
and the inter-frequency cell when power balancing drd algorithm is applied.
Only when the cell load offset reaches this threshold, the inter-frequency cell
can be selected to be the target drd cell.

z
Inter-Frequency DRD procedure for Code Load Balance
The procedure of load balancing DRD based on code resource is similar to that based on power
resource.
1The RNC determines whether the minimum remaining spreading factor of the current cell is
smaller than Minimum SF threshold for code balancing drd.
If the minimum SF is smaller than Minimum SF threshold for code balancing drd, the
RNC tries the admission of the service request to the current cell.
If the minimum SF is not smaller than Minimum SF threshold for code balancing drd,
the RNC performs the next step .
2The RNC determines whether the code load of the current cell is lower than Code occupied
rate threshold for code balancing drd. .
If the code load is lower than Code occupied rate threshold for code balancing drd,
the service tries the admission to the current cell.
If the code load is not lower than Code occupied rate threshold for code balancing
drd, the RNC selects the cell with the lightest code load or the current cell as the target
cell.
3The RNC selects the cell as follows:
If the difference between the code resource occupancies of the cell and the current cell
is larger than the value of Delta code occupied rate , 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.
Key parameters
z
Code balancing drd switch
Parameter ID: CodeBalancingDrdSwitch
Minimum SF threshold for code balancing drd
Parameter ID: CodeBalancingDrdMinSFThd
Code balancing drd switch

Parameter ID: CodeBalancingDrdSwitch
Content: This parameter specifies whether to enable the code-based load
balancing DRD algorithm.
Minimum SF threshold for code balancing drd
Parameter ID: CodeBalancingDrdMinSFThd
Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256
Content: If the downlink minimum SF of the best cell is below this threshold,
the code-based load balancing DRD is not triggered.
The default value of this parameter is SF8 .
Key parameters
z
Code occupied rate threshold for code balancing drd
Parameter ID: CodeBalancingDrdCodeRateThd
Delta code occupied rate
Parameter ID: DeltaCodeOccupiedRate
Code occupied rate threshold for code balancing drd

Parameter ID: CodeBalancingDrdCodeRateThd
Content: This parameter specifies the code occupancy threshold of the current cell for
code-based load balancing DRD.Only when the code occupancy of the best cell
reaches this threshold can code-based load balancing DRD be triggered.
The default value of this parameter is 13%.
Delta code occupied rate
Parameter ID: DeltaCodeOccupiedRate
Content: This parameter specifies the code occupied rate offset threshold of the
current cell and the inter-frequency cell when code balancing drd algorithm is applied.
Only when the code occupied rate offset reaches this threshold, the inter-frequency
cell can be selected to be the target drd cell.
The default value of this parameter is 7% .
Set this parameter through SET DRD
IAC Inter-RAT DRD

z
Inter-RAT DRD
Inter-RAT DRD is available for AMR service only in RAN 10:
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 the Service Handover Indicator is set to HO_TO_GSM_SHOULD_BE_PERFORM,
the RNC performs next step. Otherwise, the service request undergoes preemption and
queuing.
2,The RNC generates a list of candidate DRD-supportive inter-RAT cells that fulfill the Ec/No
threshold.
3,The service request then tries admission to a target GSM cell in order of blind handover
priority.
4,If all admission attempts fail or the number of inter-RAT directed retries exceeds the value
of Max inter-RAT direct retry number, the service request undergoes preemption and
queuing.
Key parameters
z
Max inter-RAT direct retry number
Parameter ID: DRMaxGSMNum
Max inter-RAT direct retry number

Parameter ID: DRMaxGSMNum
Value range: 0 to 5
Content: This parameter defines the maximum number of inter-RAT directed
retries for an RAB. The value 0 means that inter-RAT DRD is not allowed.
Set this parameter through ADD CELLDRD
IAC Preemption and Queuing

z
After cell admission fails, the RNC performs preemption

and Queuing
Precondition of Preemption and Queuing

According to CN setting, Preemption and Queuing is supported
Target cell of Preemption and Queuing

Based on DRD
Preemption and Queuing guarantees the success in the access of a higher-priority user
by forcibly releasing the resources of a lower-priority user.
After cell resource admission fails, the RNC performs Preemption and Queuing if the
following conditions are met:
The RNC receives an RAB ASSIGNMENT REQUEST message indicating that
Preemption and Queuing is supported.
By default, Preemption and Queuing setting in CN may be:
USER
LEVEL
Preemption
capability
Preemptable
Queuing
High
Able
Not allowed
allowed
Medium
Able
allowed
allowed
Low
Not able
allowed
Not
allowed
Preemption and Queuing is applicable to the following cases:

Setup or modification of a service
Hard handover or SRNS relocation
UE state transits from CELL_FACH to CELL_DCH
The RNC selects a suitable cell according to the settings of the DRD algorithms.
IAC Preemption
z
Preemption on different resources

Service
Resource
Service That can Be Preempted

R99 Service
R99 service
HSDPA
service
HSDPA Service
R99 + HSPA Combined Service
Code
Power
CE
Iub bandwidth
Code
Power
CE
Iub bandwidth
Number of
users
The preemption procedure is as follows:

1The preemption algorithm determines which radio link sets can be preempted. The
algorithm proceeds as follows:
Chooses SRNC users first. If no user under the SRNC is available, the
algorithm chooses users under the DRNC.
Sorts the pre-emptable users by user integrate priority, or sorts the preemptable RABs by RAB integrate priority.
Determines candidate users or RABs.
Only the users or RABs with priorities lower than the RAB to be
established are selected.
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 chooses the user or RAB that can release
the most resources.
2The RNC releases the resources occupied by the candidate users or RABs.
3The requested service directly uses the released resources to access the network
without admission decision.
Key parameters
z
Preempt algorithm switch
Parameter ID: PREEMPTALGOSWITCH
Preempt algorithm switch

Parameter ID: PREEMPTALGOSWITCH
Content: This parameter specifies whether to support the preemption function.
Set this parameter through SET QUEUEPREEMPT
IAC Queuing
z
After Preemption rejection, UE can wait in queue, then

admission attempts for the service are made periodically till
Tmax expires.
Admission attempts are made based on Queuing priority:

Pqueue = Tmax Telapsed
Tmax is the maximum time in the queue, default value is 5s
Telapsed is the time has queued
After the cell resource decision fails, the RNC performs queuing if the RNC receives an RAB
ASSIGNMENT REQUEST message indicating the queuing function is supported
The queuing algorithm checks whether the queue is full, that is, whether the number of service
requests in the queue exceeds the queue length that is defined by the Queue length
The queuing algorithm is triggered by the heartbeat timer, which is set through the Poll timer
length .
If the queue is not full:
Stamps this request with the current time.
Puts this request into the queue.
If the queue is full:
Checks whether there are requests whose integrate priorities are lower than that of
the priority of the new request. If there is, delete the low priority request, put the new
service in the queue. (Otherwise, the queuing algorithm rejects the new request
directly.)
Stamps the new request with the current time and then puts it into the queue.
After the heartbeat timer (Poll timer length) expires, the queuing algorithm proceeds as follows:
Selects the request with the highest integrate priority for an attempt of resource
allocation .
If the attempt fails, the queuing algorithm proceeds as follows:
Puts the service request back into the queue with the time stamp
unchanged for the next attempt.
Chooses the request with the greatest weight from the rest and makes
another attempt until a request is accepted or all requests are rejected.
Key parameters
z
Queue algorithm switch
Parameter ID: QUEUEALGOSWITCH
Queue length
Parameter ID: QUEUELEN
Queue algorithm switch

Parameter ID: QUEUEALGOSWITCH
Content: This parameter specifies whether to support the queuing function.
Queue length
Parameter ID: QUEUELEN
Content: This parameter defines the length of a queue.
Key parameters
z
Poll timer length
Parameter ID: POLLTIMERLEN
The default value of this parameter is 50 (500ms)
Max queuing time length
Parameter ID: MAXQUEUETIMELEN
Poll timer length

Parameter ID: POLLTIMERLEN
Value range: 1 to 6000 , step: 10ms
Content: This parameter defines the length of the heartbeat timer. Each time the timer
expires, the RNC chooses the service that meets the requirement to make an
admission attempt .
The default value of this parameter is 50 (500ms)
Max queuing time length
Parameter ID: MAXQUEUETIMELEN
Value range: 1 to 60s
Content: This parameter defines the maximum time that the service request can be in
the queue.
The default value of this parameter is 5s
Contents
Load%
LCC (Load Congestion Control)

100%
Overload state: OLC will be
section A
THOLC
used
1
section B
THLDR
Basic congestion state: LDR

will be used
section C
Normal state: Permit entry
Times
LCC (Load Congestion Control) consist of LDR (Load Reshuffling) and OLC (Over Load
Control).
In basic congestion state, LDR will be used to optimize resource distribution, the main
rules is not to affect the feeling of users as possible as we can.
In overload state, OLC will be used to release overload state quickly, keep system stability
and the service of high priority users.
Load Reshuffling
z
Reasons
When the cell is in basic congestion state, new coming calls

could be easily rejected by system
Purpose
Optimizing cell resource distribution
Decreasing load level, increasing admission successful rate
When the usage of cell resource exceeds the basic congestion triggering threshold, the
cell enters the basic congestion state. In this case, LDR is required to reduce the cell load
and increase the access success rate.
Load Reshuffling
z
Triggering of LDR
Power resources
Code resource
Iub resources
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, event-triggered congestion
applies, that is, the RNC checks whether the cells are congested when resource usage
changes.
Load Reshuffling
z
LDR Actions:
Inter-frequency load handover
Code reshuffling
BE service rate reduction
AMR rate reduction
Inter-RAT load handover in the CS domain
Inter-RAT load handover in the PS domain
Real time service Iu QoS renegotiation
MBMS power reduction
When the cell is in basic congestion state, the RNC takes one of the actions in each
period until the congestion is resolved
Load Reshuffling Actions triggered by different resources
If the downlink power admission uses the equivalent user number algorithm, basic congestion can also be
triggered by the equivalent number of users. In this situation, LDR actions do not involve AMR rate
reduction or MBMS power reduction, as indicated by the symbol "*" in above table
Congestion of different resource may trigger different actions.
For example, Credit congestion do not trigger Inter-Frequency Load Handover, AMR Rate
Reduction, and Code Reshuffling
When congestion of all resources is triggered, the action to be taken is based on the resource priority
configuration.
Key parameters
z
Parameter ID: NBMLDCALGOSWITCH
UL_UU_LDR
DL_UU_LDR
CELL_CODE_LDR
NodeB LDC algorithm switch
Parameter ID: NodeBLdcAlgoSwitch
IUB_LDR
NODEB_CREDIT_LDR

Content: If ULLDR, DLLDR, CELL_CODE_LDR are selected, the corresponding
algorithms are enabled. .
NodeB LDC algorithm switch
Parameter ID: NodeBLdcAlgoSwitch
Content: If IUB_LDR, NODEB_CREDIT_LDR, are selected, the corresponding
algorithms will be enabled; otherwise, disabled. .
Set this parameter through ADD NODEBALGOPARA / MOD NODEBALGOPARA /
SET LDCALGOPARA
Key parameters
z
UL (RTWP) LDR trigger threshold
Parameter ID: ULLDRTRIGTHD
UL (RTWP) LDR release threshold
Parameter ID: ULLDRRELTHD
UL LDR trigger threshold

Parameter ID: ULLDRTRIGTHD
Value range: 0 to 100 , %
Content: If the UL load of the cell is not lower than this threshold, the UL load
reshuffling function of the cell is triggered.
Set this parameter through ADD CELLLDM/MOD CELLLDM
UL LDR release threshold
Parameter ID: ULLDRRELTHD
Content: If the UL load of the cell is lower than this threshold, the UL load reshuffling
function of the cell is stopped.
Set this parameter through ADD CELLLDM / MOD CELLLDM
Key parameters
z
DL (TX POWER) LDR trigger threshold
Parameter ID: DLLDRTRIGTHD
DL (TX POWER) LDR release threshold
Parameter ID: DLLDRRELTHD
DL LDR trigger threshold

Parameter ID: DLLDRTRIGTHD
Content: If the DL load of the cell is not lower than this threshold, the DL load
reshuffling function of the cell is triggered.
DL LDR release threshold
Parameter ID: DLLDRRELTHD
Content: If the DL load of the cell is lower than this threshold, the DL load reshuffling
function of the cell is stopped.
Key parameters
z
Cell LDR SF reserved threshold
Parameter ID: CELLLDRSFRESTHD
Ul LDR Credit SF reserved threshold
Parameter ID: ULLDRCREDITSFRESTHD
Dl LDR Credit SF reserved threshold
Parameter ID: DLLDRCREDITSFRESTHD
Cell LDR SF reserved threshold

Parameter ID: CELLLDRSFRESTHD
Value range: SF4, SF8, SF16, SF32, SF64, SF128, SF256
Content: If the SF corresponding to the current remaining code of the cell is higher than
the threshold defined by this parameter, code congestion is triggered and the related
handling actions are taken.
Set this parameter through ADD CELLLDR / MOD CELLLDR
Ul LDR Credit SF reserved threshold
Parameter ID: ULLDRCREDITSFRESTHD
Content: If the SF corresponding to the current UL remaining credit resource is higher
than the threshold defined by this parameter, the UL credit LDR can be performed and
the related handling actions are taken.
Set this parameter through ADD NODEBLDR/MOD NODEBLDR
Dl LDR Credit SF reserved threshold
Parameter ID: DLLDRCREDITSFRESTHD
Content: If the value of SF corresponding to the current DL remaining credit resource is
higher than the threshold defined by this parameter, the DL credit LDR can be
performed and the related handling actions are taken.
Set this parameter through ADD NODEBLDR/MOD NODEBLDR
Key parameters
z
The First / Second/ Third/ Fourth priority for load reshuffling
Parameter ID:
LdrFirstPri
LdrSecondPri
LdrThirdPri
LdrFourthPri
The default configuration is :
IUBLDR > CREDITLDR > CODELDR > UULDR
The First / Second/ Third/ Fourth priority for load reshuffling

Parameter ID: LdrFirstPri / LdrSecondPri / LdrThirdPri / LdrFourthPri
Value range: IUBLDR(Iub load reshuffling), CREDITLDR(Credit load reshuffling),
CODELDR (Code load reshuffling), UULDR (Uu load reshuffling)
Content: These parameters specify the triggering resource order when congestion of all
resources are triggered.
The default configuration is IUBLDR > CREDITLDR > CODELDR > UULDR
Set this parameter through SET LDCALGOPARA
LDR procedure
Turn on LDR algorithm switch
Mark "current LDR state = uncongested"

Start LDM congestion indication report
Mark "current action
= first LDR action"
Clear "selected" mark of all UE LDR actions

Congestion
state indication
Wait for congestion indication
Current LDR state = congested?
Inter-freq
load handover
Succeed?
N
Code
reshuffling
Succeed?
N
BE rate
reduction
Succeed?
N
Sequence of
actions can be
configured
(current action
is taken firstly)
Inter-system
handover
in CS domain
Inter-system
handover
in PS domain
Succeed?
N
Succeed?
Mark
"current action
= successful
action"
AMR rate
reduction
Succeed?
N
QoS renogiation
on Iu interface
Succeed?
N
Y
MBMS power
reduction
Succeed?
N
No related action can be found

Mark "current action
= first LDR action"
Wait time
for LDR
action duration
Key parameters
z
LDR period timer length
Parameter ID: LDRPERIODTIMERLE
The default value of this parameter is 10 s
Gold User Load Control Switch
Parameter ID: GoldUserLoadControlSwitch
LDR period timer length

Parameter ID: LDRPERIODTIMERLE
Value range: 0 to 86400 s
Content: This parameter specifies the period of load reshuffling .
The default value of this parameter is 10 s
Gold User Load Control Switch
Parameter ID: GoldUserLoadControlSwitch
Content: This parameter specifies whether LDR actions are applicable to users of gold
priority.
Key parameters
z
DL LDR first / second / third / fourth / fifth / sixth / seventh /

eighth / ninth / tenth action
Parameter ID:
DlLdrFirstAction / DlLdrSecondAction / DlLdrThirdAction /

DlLdrFourthAction / DlLdrFifthAction / DlLdrSixthAction /
DlLdrSeventhAction / DlLdrEighthAction / DlLdrNinthAction /
DlLdrTenthAction
The default configuration is :
1st:CODEADJ , 2nd: INTERFREQLDHO , 3rd: BERATERED
DL LDR first / second / third / fourth / fifth / sixth / seventh / eighth / ninth / tenth action
Parameter ID: DlLdrFirstAction / DlLdrSecondAction / DlLdrThirdAction /
DlLdrFourthAction / DlLdrFifthAction / DlLdrSixthAction / DlLdrSeventhAction /
DlLdrEighthAction / DlLdrNinthAction / DlLdrTenthAction
Value range: NOACT (NO ACTION), INTERFREQLDHO (INTER-FREQ LOAD
HANDOVER), BERATERED (BE TRAFF RATE REDUCTION), QOSRENEGO
(UNCONTROLLED REAL-TIME TRAFF QOS RE-NEGOTIATION),
CSINTERRATSHOULDBELDHO (CS DOMAIN INTER-RAT SHOULD BE LOAD
HANDOVER), PSINTERRATSHOULDBELDHO (PS DOMAIN INTER-RAT SHOULD
BE LOAD HANDOVER), AMRRATERED (AMR TRAFF RATE REDUCTION),
MBMSDECPOWER(MBMS DESCEND POWER), CODEADJ(CODE ADJUST),
CSINTERRATSHOULDNOTLDHO (CS DOMAIN INTER-RAT SHOULD NOT BE
LOAD HANDOVER), PSINTERRATSHOULDNOTLDHO (PS DOMAIN INTER-RAT
SHOULD NOT BE LOAD HANDOVER).
Content: These parameters specify the LDR action order.
The default configuration is 1st:CODEADJ , 2nd: INTERFREQLDHO , 3rd:
BERATERED ,
Set this parameter through ADD CELLLDR / MOD CELLLDR / ADD NODEBLDR /
MOD NODEBLDR
LDR Actions
z
Inter-frequency load handover
Target users
Based on user integrate priority

Current bandwidth for DCH or GBR bandwidth for HSPA has to be less
than the UL/DL Inter-freq cell load handover maximum bandwidth
parameter
Target cells
Load difference between current load and the basic congestion trigger
threshold of target cell is larger than UL/DL Inter-freq cell load handover
load space threshold
It is implemented as follows:
1. The LDR check whether the existing cell has a target cell of inter-frequency blind handover. If there is no
such a target cell, the action fails, and the LDR performs the next action.
2. The principles of selecting inter-freq handover target cell are different as a result of the different resources
which trigger the basic congestion.
1. If the basic congestion is triggered by the power resource:
The LDR checks whether the load difference between the current load and the basic congestion triggering
threshold of each target cell for blink handover is larger than the UL/DL Inter-freq cell load handover load
space threshold (both the uplink and downlink conditions must be fulfilled). The other resources (code
resource, Iub bandwidth, and NodeB credit resource) in the target cell do not trigger basic congestion.
If the difference is not larger than the threshold, the action fails, and the LDR takes the next action.
If there are more than one cell meeting the requirements, the first one is selected as the blind handover
target cell.
2. If the basic congestion is triggered by the code resource:
Weather there are blind handover target cells meeting the requirements is decided by the following
conditions:
The minimum SF of the target cell is not greater than that of current cell.
The difference of code occupy rate between current cell and the target cell is greater than InterFreq HO
code used ratio space threshold.
The state of target cell is normal.
If there is no such cell, this action fails and the LDR performs the next action. If there are more than one cell
meeting the requirements, the first cell is selected as the blind handover target cell.
3. If the LDR finds out a target cell that meets the specified blind handover conditions, the LDR selects one UE
to make an inter-frequency blind handover, depending on the UEs ARP and occupied bandwidth. For the
selected UE other than a gold user, its UL/DL current bandwidth for DCH, GBR bandwidth for HSPA, shall be
less than and have the least difference from the UL/DL Inter-freq cell load handover maximum bandwidth
parameter (Both the uplink and downlink condition must be fulfilled). If the LDR cannot find such a UE, the
action fails. The LDR performs the next action.
Key parameters
z
UL/DL Inter-freq cell load handover load space threshold
Parameter ID: UL/DLINTERFREQHOCELLLOADSPACETHD
InterFreq HO code used ratio space threshold
Parameter ID: LdrCodeUsedSpaceThd
UL/DL Inter-freq cell load handover maximum bandwidth
Parameter ID: UL/DLINTERFREQHOBWTHD
UL/DL Inter-freq cell load handover load space threshold

Parameter ID: UL/DLINTERFREQHOCELLLOADSPACETHD
Content: The target cell can be a cell for inter-frequency blind handover only when the
UL/DL load space is higher than the threshold.
The UL/DL load space is the difference between the UL/DL basic congestion triggering
threshold and the current UL/DL load of a target cell for blind handover. .
InterFreq HO code used ratio space threshold
Parameter ID: LdrCodeUsedSpaceThd
Value range: 0% to 100% (0~1) ,step:1%
Content: The target cell can be used for inter-frequency blind handover only when the
DL Code used ratio space is higher than the threshold. The DL Code used ratio space
is the difference of code used ratio between the source cell and the target cell.
Set this parameter through ADD CELLLDR / LST CELLLDR / MOD CELLLDR
UL/DL Inter-freq cell load handover maximum bandwidth
Parameter ID: UL/DLINTERFREQHOBWTHD
Value range: 0 to 400000 bps
Content: During the inter-frequency load handover, the UE is selected as the target of
inter-frequency load handover from the UE set where the bandwidth is less than this
threshold.
LDR Actions
z
BE Rate Reduction
Target RABs
Based on RAB integrate priority
The data rate of BE service is larger than GBR
Number of RABs to be selected is configurable
BE rate reduction is implemented by reconfiguring the bandwidth. Bandwidth

reconfiguration requires signaling interaction on the Uu interface.
The LDR algorithm is implemented as follows:
1. Based on the integrate priority, the LDR sorts the RABs into a descending order. The
top RABs related to the BE services (whose current rate is higher than its GBR
configured by SET USERGBR command) are selected. If the integrate priorities of
some RABs are identical, the RAB with the highest rate is selected. The number of
RABs to select is determined by the UL/DL LDR-BE rate reduction RAB number
parameter.
2. The bandwidth of the selected services is reduced to the specified rate.
3. If services can be selected, the action is successful. If services cannot be selected, the
action fails. The LDR takes the next action.
4. The reconfiguration is completed as indicated by the RB RECONFIGURATION
message on the Uu interface and through the RL RECONFIGURATION message on
the Iub interface.
5. The BE rate reduction algorithm is controlled by the DCCC algorithm switch. BE rate
reduction can be performed only when the DCCC algorithm is enabled.
Key parameters
z
UL /DL LDR-BE rate reduction RAB number
Parameter ID: UL/DLLDRBERATEREDUCTIONRABNUM
UL /DL LDR-BE rate reduction RAB number

Parameter ID: UL/DLLDRBERATEREDUCTIONRABNUM
Content: These parameters specify the number of RABs to select in a UL/DL LDR BE
rate reduction.
If the number of RABs that fulfil the criteria for BE rate reduction is smaller than the
value of this parameter, then all the RABs that fulfil the criteria are selected.
LDR Actions
z
Uncontrolled Real-time service QoS Renegotiation
Target RABs
Real-time services in the PS domain
The load is reduced by adjusting the rate of the real-time services through uncontrolled realtime OoS renegotiation.
Upon receipt of the message, the CN sends the RAB ASSIGNMENT REQUEST message
to the RNC for RAB parameter reconfiguration. Based on this function, the RNC can
adjust the rate of real-time services to reduce the load.
1. Based on the integrate priority, the LDR sorts the real-time services in the PS domain in
descending order. The top services are selected for QoS renegotiation.
2. The LDR performs QoS renegotiation for the selected services. The GBR during
service setup is the rate of the service after QoS renegotiation.
3. The RNC initiates the RAB Modification Request message to the CN for QoS
renegotiation.
4. If the RNC cannot find a proper service for QoS renegotiation, the action fails. The LDR
performs the next action.
Key parameters
z
UL / DL LDR un-ctrl RT Qos re-nego RAB num
Parameter ID: UL/DLLDRPSRTQOSRENEGRABNUM
UL / DL LDR un-ctrl RT Qos re-nego RAB num

Parameter ID: UL/DLLDRPSRTQOSRENEGRABNUM
Content: These parameters specify the number of RABs to select in a UL/DL LDR
uncontrolled real-time QoS renegotiation.
If the number of RABs that fulfil the criteria for uncontrolled real-time QoS renegotiation
is smaller than the value of this parameter, then all the RABs that fulfil the criteria are
selected.
LDR Actions
z
Inter-system Handover In the CS/PS Domain
Target user
Based on the user integrate priority
Handover Indicator
Handover to GSM should be performed
"handover to GSM should not be performed"
GSM cell
WCDMA cell
The 2G and 3G systems have different cell sizes and coverage modes. Therefore, blind
handover across systems is not taken into account.
The LDR is implemented in the downlink (e.g.) as follows:
1. Based on the integrate priority, the LDR sorts the UEs in descending order. The top
CS/PS services are selected.
2. For the selected UEs, the LDR sends the load handover command to the inter-system
handover module to ask the UEs to hand over to the 2G system.
3. The handover module decides to trigger inter-system handover, depending on the
capability of the UE and the capability of the algorithm switch to support the
compression mode.
4. This action is successful if any load handover UE is found. Otherwise, this action fails.
Key parameters
z
UL / DL CS should be ho user number
Parameter ID: UL/DLCSINTERRATSHOULDBEHOUENUM
UL / DL CS should not be ho user number
Parameter ID: UL/DLCSINTERRATSHOULDNOTBEHOUENUM
UL / DL CS should be ho user number

Parameter ID: UL/DLCSINTERRATSHOULDBEHOUENUM
Content: These parameters specify the number of users to select in a UL/DL Inter-RAT
Should Be Load Handover in the CS Domain.
If the number of users that fulfil the criteria for Inter-RAT Should Be Load Handover in the
CS Domain is smaller than the value of this parameter, then all the users that fulfil the
criteria are selected.
UL / DL CS should not be ho user number
Parameter ID: UL/DLCSINTERRATSHOULDNOTBEHOUENUM
Should Not Be Load Handover in the CS Domain.
If the number of users that fulfil the criteria for Inter-RAT Should Not Be Load Handover
in the CS Domain is smaller than the value of this parameter, then all the users that fulfil
the criteria are selected.
Key parameters
z
UL / DL PS should be ho user number
Parameter ID: UL/DLPSINTERRATSHOULDBEHOUENUM
UL / DL PS should not be ho user number
Parameter ID: UL/DLPSINTERRATSHOULDNOTBEHOUENUM
UL / DL PS should be ho user number

Parameter ID: UL/DLPSINTERRATSHOULDBEHOUENUM
Should Be Load Handover in the PS Domain.
If the number of users that fulfil the criteria for Inter-RAT Should Be Load Handover in
the PS Domain is smaller than the value of this parameter, then all the users that fulfil
UL / DL PS should not be ho user number
Parameter ID: UL/DLPSINTERRATSHOULDNOTBEHOUENUM
Should Not Be Load Handover in the PS Domain.
If the number of users that fulfil the criteria for Inter-RAT Should Not Be Load Handover
in the PS Domain is smaller than the value of this parameter, then all the users that fulfil
LDR Actions
z
AMR Rate Reduction
Target user
AMR services and with the bit rate higher than the GBR
In the WCDMA system, voice services work in eight AMR modes. Each mode has its own
rate. Therefore, mode control is functionally equal to rate control.
1. Based on the integrate priority, the LDR sorts the RABs in the descending order. The top
UEs accessing the AMR services (conversational) and with the bit rate higher than the
GBR are selected.
2. In uplink, the RNC sends the Rate Control request message through the Iu-UP to the
CN to adjust the AMR rate to the GBR.
3. In downlink, The RNC sends the TFC CONTROL command to the UE to adjust the AMR
rate to the assured rate.
4. If the RNC cannot find a proper service for AMR rate reduction, the action fails. The LDR
performs the next action.
Key parameters
z
UL/DL LDR-AMR rate reduction RAB number
Parameter ID: UL/DLLDRAMRRATEREDUCTIONRABNUM
UL/DL LDR-AMR rate reduction RAB number

Parameter ID: UL/DLLDRAMRRATEREDUCTIONRABNUM
Content: These parameters specify the number of RABs to select in a UL/DL LDR AMR
rate reduction.
If the number of RABs that fulfil the criteria for AMR rate reduction is smaller than the
value of this parameter, then all the RABs that fulfil the criteria are selected.
LDR Actions
Code Reshuffling
Reallocate code resources for candidate user
Code Adjustment
The algorithm operates as follows:

1,Initialize the SF_Cur of the root node of subtrees to Cell LDR SF reserved threshold.
2,Traverse all the subtrees with this SF_Cur at the root node. Leaving the subtrees
occupied by common channels and HSDPA channels out of account, take the
subtrees in which the number of users is not larger than the value of the Max user
number of code adjust parameter as candidates for code reshuffling.
3,Select a subtree from the candidates according to the setting of the LDR code priority
indicator parameter.
z
If this parameter is set to TRUE, select the subtree with the largest code
number from the candidates.
If this parameter is set to FALSE, select the subtree with the smallest
number of users from the candidates. In the case that multiple subtrees have
the same number of users, select the subtree with the largest code number.
4,Treat each user in the subtree as a new user and allocate code resources to each user.
5,Initiate the reconfiguration procedure for each user in the subtree and reconfigure the
channel codes of the users to the newly allocated code resources.
The reconfiguration procedure on the air interface is implemented through the PHYSICAL
CHANNEL RECONFIGURATION message and that on the Iub interface through the
RL RECONFIGURATION message.
Key parameters
z
Max user number of code adjust
Parameter ID: MAXUSERNUMCODEADJ
LDR code priority indicator
Parameter ID: LdrCodePriUseInd
The default value of this parameter is TRUE
Max user number of code adjust

Parameter ID: MAXUSERNUMCODEADJ
Value range: 1 to 3
Content: This parameter specifies the maximum number of users that can be selected
whenever code reshuffling is performed.
LDR code priority indicator
Parameter ID: LdrCodePriUseInd
Value range: True, False
Content: This parameter specifies whether to select preferentially the subtree with a
relatively large code number during subtree selection.
LDR Actions
z
MBMS Power Reduction
Purpose
The downlink power load can be reduced by lowering power on

MBMS traffic channels

1. Select all RABs with low priorities.
2. The RNC initiates the reconfiguration procedure and resets the transmit power of
MTCH (FACH) to the minimum value. The transmit power corresponds to the MBMS
service.
3. The reconfiguration procedure on the Iub interface is implemented through the
COMMON TRANSPORT CHANNEL RECONFIGURATION REQUEST message.
Contents
Over Load Control

z
Reasons
In overload state, system is not stable
Purpose
Ensuring the system stability and making the system back to

the normal state as soon as possible
Triggering of Over Load
Power resource
After the UE access is granted, the power consumed by a single link is adjusted by the
single link power control algorithm. The power varies with the mobility of the UE and the
changes in the environment and the source rate. In some situations, the total power load of
the cell may be higher than the target load. To ensure system stability, overload congestion
must be handled.
Over Load Control

z
Over Load triggering
If the current UL/DL load of an R99 cell is not lower than the UL/DL OLC Trigger
threshold for some hysteresis (defined by the DL State Trans Hysteresis threshold in
DL; not configurable in UL), the cell works in overload congestion state and the related
overload handling action is taken. If the current UL/DL load of the R99 cell is lower than the
UL/DL OLC Release threshold for some hysteresis (defined by the DL State Trans
Hysteresis threshold in DL; not configurable in UL), the cell comes back to the normal
state.
The HSPA cell has the same uplink decision criterion as the R99 cell. The load in the
downlink, however, is the sum of load of the non-HSPA power (transmitted carrier power of
all codes not used for HS-PDSCH or HS-SCCH transmission) and the GBP..
Key parameters
z
UL_UU_OLC, DL_UU_OLC
UL/DL OLC trigger threshold
Parameter ID: UL/DLOLCTRIGTHD
UL/DL OLC release threshold
Parameter ID: UL/DLOLCRELTHD

Content: This parameter specifies the switch of UL/DL OLC.
UL_UU_OLC: UL overload control algorithm
DL_UU_OLC: DL overload control algorithm
UL/DL OLC trigger threshold
Parameter ID: UL/DLOLCTRIGTHD
Content: If the UL load of the cell is not lower than the value of the UL OLC trigger
threshold, the UL overload congestion control of the cell is activated.
If the DL load of the cell is not lower than the value of the DL OLC trigger threshold,
the DL overload congestion control of the cell is activated.
UL/DL OLC release threshold
Parameter ID: UL/DLOLCRELTHD
Content: If the UL load of the cell is lower than the value of the UL OLC release
threshold, the UL overload congestion control of the cell is deactivated.
If the DL load of the cell is lower than the value of the DL OLC release threshold, the
DL overload congestion control of the cell is deactivated.
The general OLC procedure covers the following actions: TF control of BE services, channel
switching of BE services, and release of RABs. The RNC takes periodical actions if overload
congestion is detected.
When the cell is overloaded, the RNC takes one of the following actions in each period (defined by
the OLC period timer length parameter, e.g.3s) until the congestion is resolved:
1. TF control of BE service (only for DCH BE service)
2. Switching BE services to common channel
3. Choosing and releasing the RABs (for HSPA or DCH service)
If the first action fails or the first action is completed but the cell is still in congestion, then the
second action is taken.
Key parameters
z
OLC period timer length
Parameter ID: OLCPERIODTIMERLEN
The default value of this parameter is 3000 (ms)
OLC period timer length

Parameter ID: OLCPERIODTIMERLEN
Content: This parameter specifies the period of overload control.
OLC Action
z
TF Control
Target user
The RABs with the DCH BE services
Execution
The RNC sends the TF control indication message to the MAC.
MAC restricts the TFC selection :

TFmax(N+1) = TFmax(N) x Ratelimitcoeff
Based on the RAB integrate priority, the OLC sorts the RABs into a descending order.The
following RABs are selected:
1. The RABs with the DCH BE services
2. The RABs with the lowest integrate priority.
3. The number of RABs selected is DL/UL OLC fast TF restrict RAB number.
The RNC sends the TF control indication message to the MAC. Each MAC of 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.
MAC restricts the TFC selection in a way like that the maximum TB number is calculated
with the formula:
TFmax(N+1) = TFmax(N) x Ratelimitcoeff
Ratelimitcoeff is a configurable parameter (DL OLC fast TF restrict data rate restrict
coefficient).
If the RNC cannot find an appropriate service for the TF control or the time for performing
the TF control exceed the DL OLC fast TF restrict times parameter, the action fails.
The OLC performs the next action.
If the congestion is released, the RNC sends the congestion release indication to the MAC.
At the same time, the rate recovery timer (whose length is defined by DL OLC fast TF
restrict data rate recover timer length) is started. When this timer is expired, the
MAC increases the data rate step by step.
MAC recovers the TFC selection by calculating the maximum TB number with the formula:
TFmax(N+1) = TFmax(N) x RateRecoverCoeff
RateRecoverCoeff is a configurable parameter (DL TF rate recover coefficient)
OLC Action
z
TF Control example
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}.336 is the TB size, 320 payload + 16 MAC head
At point A, the cell enters OLC state. The RNC selects this RAB to do fast TF restriction.
MAC restricts the TFC selection during time 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
Match 8.16 and the TFS. Therefore, the maximum TB number is 8.
At point B, MAC performs further TFC restriction by calculating maximum TB number as
follows:
TFmax(2) = TFmax(1) x Ratelimitcoeff = 8 x 0.68 = 5.44
Match 5.44 and the TFS. Then, the maximum TB number is 4.
At point C and point D, similar process is followed.
Key parameters
z
UL/DL OLC fast TF restrict RAB number
Parameter ID: UL/DLOLCFTFRSTRCTRABNUM
UL/DL OLC fast TF restrict times
Parameter ID: UL/DLOLCFTFRSTRCTTIMES
UL/DL OLC fast TF restrict RAB number

Parameter ID: UL/DLOLCFTFRSTRCTRABNUM
Content: These parameters specify the maximum number of RABs selected in a fast
TF restriction of UL/DL OLC.
If the number of RABs that fulfil the criteria for TF control is smaller than the value of
this parameter, then all the RABs that fulfil the criteria are selected.
Set this parameter through ADD CELLOLC / MOD CELLOLC
UL/DL OLC fast TF restrict times
Parameter ID: UL/DLOLCFTFRSTRCTTIMES
Content: These parameters specify the times of UL/DL OLC fast TF restrictions that
are executed.
Key parameters
z
DL TF rate restrict coefficient
Parameter ID: RateRstrctCoef
DL TF rate restrict timer length
Parameter ID: RateRstrctTimerLen
DL TF rate restrict coefficient

Parameter ID: RateRstrctCoef
Content: This parameter specifies the data rate restriction coefficient in the fast TF
restriction. The smaller the parameter is, the more effective the TF restriction is. After
receiving the TF control indication, the MAC obtains the maximum TF format with the
formula TFmax' = TFmax x Ratelimitcoeff .
The default value of this parameter is 68 %
DL TF rate restrict timer length
Parameter ID: RateRstrctTimerLen
Value range: 1 to 65535 ms
Content: This parameter specifies the length of the data rate restriction timer in the fast
TF restriction. The smaller the value of this parameter is, the more effective the TF
restriction is.
The default value of this parameter is 3000 ms
Key parameters
z
DL TF rate recover timer length
Parameter ID: RateRecoverTimerLen
DL TF rate recover coefficient
Parameter ID: RecoverCoef
The default value of this parameter is 130 %
DL TF rate recover timer length

Parameter ID: RateRecoverTimerLen
Value range: 1 to 65535 ms
Content: This parameter specifies the length of the data rate recovery timer. The
smaller the value of this parameter is, the faster the BE traffic rate increases after the
congestion is resolved.
The default value of this parameter is 5000 ms
DL TF rate recover coefficient
Parameter ID: RecoverCoef
Content: This parameter specifies the data rate recovery coefficient in the fast TF
restriction. The larger the parameter is, the larger the TF recover effect. After receiving
congestion release indication, the MAC obtains the maximum TF format with the
formula TFmax' = TFmax x RateRecovercoeff.
OLC Action
z
Switching BE Services to Common Channel
Target user
Based on the user integrate priority
The users with the DCH or HSDPA BE services in PS
Execution
The RNC sends RB Reconfiguration message to UE
UE make a response by RB Reconfiguration Complete
The OLC algorithm for switching BE services to common channel operates as follows:
Based on the user integrate priority, the OLC sorts all UEs that only have PS services
including HSPA and DCH services (except UEs having also a streaming bearer) into a
descending order.
The top N UEs are selected. The number of selected UEs is equal to Transfer Common
Channel user number. If UEs cannot be selected, the action fails. The OLC performs the
next action.
The selected UEs are switched to common channel.
Key parameters
z
Transfer Common Channel User number
Parameter ID: TransCchUserNum
Transfer Common Channel User number

Parameter ID: TransCchUserNum
Content: This parameter specifies the transfer common channel user number
Set this parameter through ADD CELLOLC / LST CELLOLC / MOD CELLOLC
OLC Action
z
Release of Some RABs
Target user
Based on the RAB integrate priority
DCH services RAB
Execution
The RNC sends IU Release Request message to CN
The RNC sends RRC Connection Release message to UE
OLC Algorithm for the Release of Some RABs in the Uplink:

The OLC algorithm for the release of some RABs in the uplink operates as follows:
Based on the integrate priority, the OLC sorts all RABs including HSUPA and DCH services
into a descending order.
The top RABs selected. If the integrate priorities of some RABs are identical, the RAB with
higher rate (current rate for DCH RAB and GBR for HSUPA RAB) in the uplink is
selected. The number of selected RABs is equal to UL OLC traff release RAB number.
The selected RABs are released directly.
OLC Algorithm for the Release of Some RABs in the Downlink
The OLC algorithm for the release of some RABs in the downlink operates as follows:
Based on the integrate priority, the OLC sorts all RABs into a descending order.
The top-priority RABs are selected. If the integrate priorities of some RABs are identical,
the RAB with higher rate (current rate) The number of selected RABs is equal to DL
OLC traff release RAB number.
The selected RABs are directly released.
Key parameters
z
UL/DL OLC traff release RAB number
Parameter ID: UL/DLOLCTRAFFRELRABNUM
UL/DL OLC traff release RAB number

Parameter ID: UL/DLOLCTRAFFRELRABNUM
Content: Either parameter specifies the number of RABs released in a UL or DL OLC
release action.
If the number of RABs that fulfil the criteria for release is smaller than the value of this
parameter, then all the RABs that fulfil the criteria are selected.
Summary
PUC (Potential User Control)
LDB (Intra-Frequency Load Balancing)
CAC (Call Admission Control)
IAC (Intelligent Admission Control)
LDR (Load Reshuffling)
OLC (Overload Control)
Thank You
www.huawei.com
HSDPA RRM and

Parameters
www.huawei.com
Contents
1. HSDPA Channel Type Mapping
2. HSDPA Code Resource Management
3. HSDPA Power Management
4. HSDPA Mobility Management
5. HSDPA Channel Switching
6. HSDPA Mac-hs Scheduling Algorithm
7. HSDPA TFRC Selection
8. HSDPA Flow control
Page1
Mapping signaling and traffic

onto HSDPA
z
UMTS network could provide multi-services such as CS service, PS service and

signaling
In most case, CS service with high requirement of transmission quality will be

mapped onto DCH
PS service such as PS conversational service i.e. VOIP, streaming service, BE

service and signaling ) could be mapped onto HS-DSCH
The following figure show mapping between service and bearer
Page2

onto HSDPA
z
PS conversational services may be mapped onto the DCH, HS-DSCH, or EDCH

If Voip channel type = DCH
If Voip channel type = HSDPA
Both uplink and downlink are mapped onto DCH
Uplink is beared on DCH, downlink mapped onto HS-DSCH
If Voip channel type = HSPA
Uplink is beared on E-DCH, downlink mapped onto HS-DSCH
For Ps conversational service

VoipChlType --- UL_DCH / DL_DCH, UL_DCH / DL_HS-PDSCH, UL_EDCH / DL_HSP-DSCH
MML: SET FRCCHLTYPEPARA
Page3
VoIP stands for Voice over IP, a PS conversational service. It uses IP data
packets to encapsulate voice data and transports them on the IP network
to implement the conversational services.

onto HSDPA
z
During the setup of an RRC connection, the single SRB can be carried
on the CCH, DCH, HS-DSCH, or E-DCH
If the selected channel type is FACH, the SRB is carried on the CCH in
both the uplink and the downlink
If the selected channel type is DCH, then
In the downlink, if Srb channel type RRC effect flag is set to TRUE and Srb
channel type is set to HSDPA or HSPA, the SRB is carried on the HS-DSCH;
otherwise, on the DCH
In the uplink, if Srb channel type RRC effect flag is set to TRUE and Srb
channel type is set to HSPA, the SRB is carried on the E-DCH; otherwise, on
the DCH
Page4

onto HSDPA
z
SRB may be mapped onto the DCH, HS-DSCH, or E-DCH, RACH/FACH
zIf
SRB channel type = DCH
If SRB channel type = HSDPA
Both uplink and downlink are mapped onto DCH

Uplink is mapped on DCH, downlink mapped onto HS-DSCH
If SRB channel type = HSPA
Uplink is mapped on E-DCH, downlink mapped onto HS-DSCH
Bearer types for SRB
Bandwidth allocation
SrbChlType --- UL_DCH / DL_DCH, UL_DCH /
MML: SET
DL_HS-PDSCH, UL_EDCH / DL_HS-PDSCH
FRCCHLTYPEPARA
SigChType --- FACH ,DCH-3.4kbps-signaling, DCH-
MML: SET RRCESTCAUSE
13.6kbps-signaling, DCH-27.2kbps-signaling
With SRB over HSPA, call setup delay is reduced, moreover compared with
SRB over DCH , code resource is saved
Page5

onto HSDPA
z
During the setup of an RRC connection, the single SRB can be carried on the CCH,
DCH, HS-DSCH, or E-DCH

z
If the selected channel type is FACH, the SRB is carried on the CCH in both the uplink
and the downlink

z
If the selected channel type is DCH, then
In the downlink, if Srb channel type RRC effect flag is set to TRUE and Srb
channel type is set to HSDPA or HSPA, the SRB is carried on the HS-DSCH;
otherwise, on the DCH
In the uplink, if Srb channel type RRC effect flag is set to TRUE and Srb
channel type is set to HSPA, the SRB is carried on the E-DCH; otherwise, on the
DCH
Bearer types for SRB
SrbChlTypeRrcEffectFlag --- TURE,
MML: SET
FALSE
FRCCHLTYPEPARA
Page6
Mapping signaling and traffic onto

HSDPA
z
PS streaming services can be mapped onto the DCH, HS-DSCH, or
E-DCH
The cell supports HSDPA
PS_STREAMING_ON_HSDPA_SWITCH is selected
If the maximum DL service rate is higher than or equal to DL streaming traffic
threshold on HSDPA
then PS streaming service is carried on the HS-DSCH. Otherwise, it is carried on
the DCH
Bit rate threshold
for streaming
DlStrThsOnHsdpa --- 8, 16, 32, 64, 128, 144, 256, 384kbps
MML: SET FRCCHLTYPEPARA
UlStrThsOnHsupa --- 8, 16, 32, 64, 128, 144, 256, 384kbps
over HSPA
Algorithm switch
for streaming
PS_STREAMING_ON_HSDPA_SWITCH --- Enable , Disable

PS_STREAMING_ON_E_DCH_SWITCH --- Enable , Disable
MML: SET
CORRMALGOSWITCH
over HSPA
Page7
PS streaming services can be mapped onto the DCH, HS-DSCH, or E-DCH
If the maximum UL service rate is higher than or equal to UL streaming

traffic threshold on HSUPA
The cell supports HSUPA
PS_STREAMING_ON_E_DCH_SWITCH is selected
then the service is carried on the E-DCH. Otherwise, the service is carried on the
DCH

onto HSDPA
z
The IMS signaling can be mapped on the DCH, HS-DSCH, or E-DCH
If IMS channel type = DCH
If IMS channel type = HSDPA
Both uplink and downlink are mapped on DCH

Uplink is mapped on DCH, downlink mapped on HS-DSCH
If IMS channel type = HSPA
Uplink is mapped onto E-DCH, downlink mapped on HS-DSCH
Bearer types for IMS
ImsChlType --- UL_DCH / DL_DCH, UL_DCH /
MML: SET
signaling
DL_HS-PDSCH, UL_EDCH / DL_HS-PDSCH
FRCCHLTYPEPARA
Page8
IMS signaling (SIP SDP) is an PS RAB to UTRAN, and only setup on DCH and use the
fixed configuration before RAN10.0
SIP / SDP characteristics based on Huawei research
- The traffic in the SIP/SDP setup phase is about 70Kbits and the setup time is generally
less than 3s, therefore, mean bit rate is 23.3Kbps
-
Very low traffic exists on SIP / SDP after connection establishment

UTRAN
UTRAN
UE
PS
PS
IMS
IMS
Domain
Domain
Domain
Session control Signaling (SIP / SDP)

Media ( RTP)
Real Time Media Control (RTCP)
It is more suitable for HSPA to bear IMS Signaling
UTRAN
UTRAN
UE
UE

onto HSDPA
z
PS interactive and background services (i.e. BE service) can be mapped onto
the CCH, DCH, HS-DSCH, or E-DCH
Low-rate PS services have relatively small amount of data. Therefore,
such PS services can be carried on the CCH to save radio resources
If the maximum DL service rate is lower than DL BE traffic DCH decision threshold,
the maximum UL service rate is lower than UL BE traffic DCH decision threshold,
and the RRC connection is set up on the CCH, then the service is carried on the CCH.
Otherwise, further decision need to be made as follows:
If the maximum DL service rate is higher than or equal to DL BE traffic threshold on

HSDPA, then the service is carried on the HS-DSCH. Otherwise, the service is
carried on the DCH
If the maximum UL service rate is higher than or equal to UL BE traffic threshold on

HSUPA, then the service is carried on the E-DCH. Otherwise, the service is carried
on the DCH
Page9

onto HSDPA
Bit rate
threshold for BE
DL BE traffic DCH decision threshold --- 8, 16kbps

UL BE traffic DCH decision threshold --- 8, 16kbps
MML: SET
FRCCHLTYPEPARA
service over
HSPA
DL BE traffic threshold on HSDPA --- 8, 16, 32, 64, 128,

144, 256, 384, 768, 1024, 1536, 1800, 2048, 3648, 7200,
10100, 14400kbps
UL BE traffic threshold on HSUPA --- 8, 16, 32, 64, 128,
144, 256, 384, 608, 1450, 2048,2890, 5760kbps
Page10
Contents
Page11
HSDPA Code Resource Allocation

z
The codes of the HS-PDSCH can be allocated in three ways:
Static HSDPA code allocation
In static allocation, the RNC reserves codes for the HS-PDSCH
The DPCH, HS-SCCH, and common channels use the remaining codes
RNC-controlled dynamic allocation
In RNC-controlled dynamic allocation, the RNC adjusts the reserved HSPDSCH codes according to the real-time usage status of the codes
NodeB-controlled dynamic allocation
NodeB-controlled dynamic allocation allows the NodeB to use the HSPDSCH codes allocated by the RNC
The NodeB can dynamically allocate the idle codes of the current cell to
the HS-PDSCH
Page12
The channelization codes are constant resources consisting of the following three
parts:
channelization codes for HS-PDSCH
channelization codes for Common channels and HS-SCCH
channelization codes for DPCH
The resources are reserved for the common channels and the HS-SCCH. The
parameter of the codes reserved for the HS-SCCH can be configured on the RNC LMT.

Static HSDPA Code Allocation
Static HS-PDSCH code
allocation
Spreading factor =16
Allocate continuously
Static HS-SCCH code allocation
Spreading factor =128
Allocate with common channel
Code Resource
Allocation
Code Number for HS-SCCH --- 1~15
MML: ADD CELLHSDPA
Allocate Code Mode --- Manual, Automatic
Parameters
PS_STREAMING_ON_HSDPA_SWITCH --- 1~15
Page13

RNC-controlled dynamic allocation
In the RNC-controlled dynamic allocation, the RNC adjusts the reserved
HS-PDSCH codes according to the real-time usage status of the codes
Min. number of codes, defined by the code min number for HS-PDSCH
parameter, are reserved for HS-PDSCH in a cell
Code Resource
Code Min Number for HS-PDSCH --- 1~15
MML: ADD CELLHSDPA
Allocation
Parameters
Code Max Number for HS-PDSCH--- 1~15
Page14

z
When R99 code consumption is reduced, RNC increases the codes

reserved for HSDPA if following conditions are met
the shared code neighboring to the codes reserved for HS-PDSCH is idle
At least another free code that reserved for R99 handover users. This idle
code SF is equal or less than cell LDR SF reserved threshold
* the solid dots represent the occupied codes and the circles represent the idle codes
Page15

When the re-allocation of R99 code resource is trigger by some voice calls
coming
RNC re-allocates one shared code from HS-PDSCH to R99 if the rest idle
code SF is greater than Cell LDR SF reserved threshold
* the solid dots represent the occupied codes and the circles represent the idle codes
Code Resource
Cell LDR SF reserved threshold --- SF8, SF16,
Allocation Parameters
SF32, SF64, SF128, SF256
MML: ADD CELLLDR
Page16

z
NodeB-controlled dynamic allocation allows the NodeB to use the HSPDSCH codes that are allocated by the RNC. The NodeB can dynamically
allocate the idle codes of the current cell to the HS-PDSCH channel
The NodeB periodically detects the SF16 codes apart from the RNCallocated HS-PDSCH codes every 2 ms. If the codes or sub-codes are
allocated by the RNC to the DCH or common channels, they are identified
as occupied. Otherwise, they are identified as unoccupied. Therefore, the
HS-PDSCH codes available for the HS-PDSCH channel include the codes
allocated by the RNC and those consecutive and unoccupied SF16 codes
Page17

z
For example, if the RNC allocates five codes to the NodeB, that is, No.11
to 15 SF16 codes are allocated to the HS-PDSCH. Suppose in a 2 ms TTI,

No. 0 to 5 SF16 codes are allocated to the DCH and common channels. No.
0 to 5 SF16 codes are occupied. Therefore, in the current TTI, the HSPDSCH can use No. 6 to 15 SF16 codes
If the DCH codes allocated by the RNC are temporarily occupied by the
HS-PDSCH during the setup of radio links, the NBAP message returned to
the RNC indicates that the radio link is set up successfully. From the next 2
ms TTI, the HS-PDSCH no longer uses these codes until they are released
from the DCH
Code Resource
Dynamic codes switch--- OPEN, CLOSE
MML: SET
MACHSPARA
Page18
Contents
Page19
HSDPA Power Allocation

z
HS-PDSCH and HS-SCCH shared power with R99 channels
The downlink power consists of the following parts
Power for common channel
Power for DPCH
Power for DL HSDPA channel, such as HS-PDSCH, HS-SCCH
A configurable margin is used to keep the system in stable status
Power Resource
The Offset of HSPA Total Power --- [-5dB~0dB]
MML: ADD CELLHSDPA
Power Margin --- [0~100%]
MML: SET MACHSPARA
Max Power per H user --- [1%~100%]
Page20
The cell total transmit power is the constant resources. The DL power consists of the
following three parts:
Power of the HSPA DL physical channel (HS-PDSCH, HS-SCCH, E-AGCH, ERGCH and E-HICH)
Common channel power
DPCH power
Power margin for DCH

power control
Total Power
Allowed power for HSDPA
Time
Higher power
utility
efficiency
DPCH
Power for CCH
Time
HSDPA Power Control

z
HS-DPCCH Power Control
Power Offset of ACK, NACK and CQI (Non SHO & SHO)
There is no separate power control for HS-DPCCH but setting several power offsets
between HS-DPCCH and UL associated DPCCH, namely ACK, NACK, CQI
Page21
The CQI feedback in the uplink is determined by the following parameters:

z
CQI_Repetition_Factor
CQI_Power_Offset
CQI_feedback_cycle
CQI_feedback_cycle refers to the cycle of UE providing CQI feedback. In each cycle, the
CQI is repeatedly sent within the CQI_Repetition_Factor consecutive subframes
which is equal to 1 frame
In each subframe, the CQI transmission power is equal to the associated UL DPCCH
power plus the CQI power offset
The NACK/ACK feedback in the uplink is determined by the following parameters:
z
ACK-NACK_Repetition_Factor
ACK/NACK_poweroffset
HS-DPCCH_Preamble_Transmission_Indication
At the end of about 19,200 chips (i.e.5ms) after the UE receives HS-PDSCH subframes in
the downlink, the UE provides HARQ NACK or ACK feedback in the uplink within
ACK-NACK_Repetition_Factor consecutive HS-DPCCH subframes.
The transmit power of the UE is equal to the associated UL DPCCH transmit power plus
the ACK_Poweroffset or NACK_Poweroffset, for NACK or ACK feedback
respectively
Several power offsets are set between the HS-DPCCH and the associated UL DPCCH.
When ACK/NACK and CQI are carried on the HS-DPCCH, their power offsets, that is,
ACK, NACK, and CQI, are set in one HS-DPCCH TTI
The transmit power of the HS-DPCCH is calculated with the following formula:
where
PUL DPCCH is the transmit power of the associated UL DPCCH
For the first slot of a TTI, HS-DPCCH means ACK when the UE responds with ACK or
means NACK when the UE responds with NACK.
For the second and third slots of a TTI, HS-DPCCH means CQI.
HSDPA Power Control

z
HS-DPCCH Power Control
In soft handover area, the UL combining gain reduces the necessary transmission
power of UL DPCCH. While HS-DPCCH does not has the UL combining gain, to
maintain the receiving quality of the HS-DPCCH, higher power offset is needed. Thus,
when UE enters or leaves the soft handover area, the power offset for ACK/NACK and
CQI may have a change correspondingly
Parameters for
ACK power offset
Parameters for
NACK power
offset
Parameters for
CQI power offset
ACK poweroffset1 / ACK poweroffset2 / ACK poweroffset3 --- 5/15,

6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15
ACK poweroffset1 multi-RLS / ACK poweroffset2 multi-RLS / ACK
poweroffset3 multi-RLS --- 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15,
24/15, 30/15
NACK poweroffset1 / ACK poweroffset2 / ACK poweroffset3 --- 5/15,
6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15, 30/15
NACK poweroffset1 multi-RLS / ACK poweroffset2 multi-RLS / ACK
poweroffset3 multi-RLS --- 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15,
24/15, 30/15
CQI Power Offset --- 5/15, 6/15, 8/15, 9/15, 12/15, 15/15, 19/15, 24/15,
30/15
CQI Power Offset multi-RLS --- 5/15, 6/15, 8/15, 9/15, 12/15, 15/15,
19/15, 24/15, 30/15
Page23
MML:ADD
CELLHSDPCCH
HSDPA Power Control

HS-SCCH Power Control
Fixed Power
Set fixed power for each HS-SCCH by O&M
Simple to configuration, but low utilization of the power
Based on CQI
If the HS-SCCH Power Control Method parameter is set to CQI, the NodeB adjust
the transmission power of HS-SCCH, depending on the following information
CQI reported by UE
DTX detected by NodeB
Target frame error rate ( FER ) of HS-SCCH
HS-SCCCH power
HS-SCCH Power Control Method --- FIXED, CQI
control parameters
HS-SCCH Power --- -10 dB to 10 dB
MML: SET MACHSPARA
HS-SCCH FER --- 1~999 1
Page24
The process of power control adjustment within an adjustment period is as follows:

1NodeB acquires the PHS-SCCH,init, PHS-SCCH,min and PHS-SCCH,max
according to the reported CQI
1PHS-SCCH,init is the initial HS-SCCH transmit power, which is an offset relative
to the P-CPICH transmit power
2PHS-SCCH,min is the minimum HS-SCCH transmit power, which is an offset
relative to the P-CPICH transmit power. PHS-SCCH,min is set to -10 dB
3PHS-SCCH,max is the maximum HS-SCCH transmit power, which is an offset
relative to the P-CPICH transmit power
2NodeB calculates the HS-SCCH power for the Nth scheduling period by using the
following formula:
PHS-SCCH(n) = FUNC(PHS-SCCH(n-1), CQI(n-1), CQI(n), NDTX, Cpc, FERT, Sbase,
Smax,u)
where:
Cpc is the HS-SCCH power adjustment period, indicating the number of transmitted
HS-SCCH frames. After the period, the power adjustment is performed at once. Cpc
is set to 3 TTI.
Sbase is the step of power adjustment within an HS-SCCH power adjustment period.
Sbase is set to 0.02 dB.
Smax,u is the maximum allowed power step-up within a power adjustment period.
Smax,u is set to 0.5 dB.
NDTX is the number of DTXs.
FERT represents HS-SCCH FER and can be set on the NodeB LMT
3NodeB limits the HS-SCCH power for the Nth schedule time by PHS-SCCH,min
and PHS-SCCH,min . That is, limit the HS-SCCH power in the range [PHSSCCH,min , PHS-SCCH,min]
HSDPA Power Control

z
HS-PDSCH Power Control
Power is allocated in NodeB, Mac-hs allocates HS-PDSCH power for different

HSDPA users with scheduling algorithm
When configured by static HSDPA power allocation algorithm, the total power
of HS-PDSCH and HS-SCCH shall not exceed the maximum transmission
power
When configuredby dynamic HSDPA power allocation algorithm, the maximum

transmission power is the remaining power excluding R99 power and power
margin
Page26
HSDPA Power Control

z
The initial transmit power of the downlink F-DPCH, PF-DPCH,Initial is calculated with
the following formula:
To prevent waste of downlink power while adding a new radio link to the active
set, a power adjustment for the new radio link is used. Based on the calculation
used for calculating the initial transmit power of the F-DPCH, the power of the
new radio link is decreased by a power offset, which is 15 dB. This parameter is
only available when the branch parameter
DOWNLINK_POWER_BALANCE_SWITCH is set to ON
Page27
where:
z
PCPICH is the P-CPICH transmit power in a cell. It is defined by the PCPICH transmit
power parameter
(Ec/No)CPICH is the ratio of received energy per chip to noise spectral density of
CPICH received by the UE
is the orthogonality factor in the downlink. Orthogonal codes are employed in the
downlink to separate the physical channels, and without any multi-path propagation,
the orthogonality remains when the NodeB signal is received by the UE. If there is
sufficient delay spread in the radio channel, part of the NodeB signals will be regarded
as multiple access interference by the UE. The orthogonality of 0 corresponds to
perfectly orthogonal users. In the Huawei implementation, is set to 0.
Ptotal is the downlink transmitted carrier power measured at the NodeB. This power is
reported to the RNC.
(Ec/N0)F-DPCH is the Ec/No required for the TPC symbol error rate of the F-DPCH
stipulated by the protocol, that is, a symbol error rate of 4%. This Ec/No is set to -17 dB.
HSDPA Power Control

Downlink open loop power control on F-DPCH
The maximum and minimum values of the transmit power range of
downlink F-DPCH is calculated with the following formulas:.
Maximum transmit power value = PCPICH + FDPCH maximum reference

power + F-DPCH Power Offset
Minimum transmit power value = PCPICH + FDPCH minimum reference

power + F-DPCH Power Offset
F-DPCH initial
FDPCH maximum reference power --- -35dB ~ 15dB
MML: SET FDPCHRLPWR
transmission power
parameters
FDPCH minimum reference power --- -35dB ~ 15dB

Soft handover initial power offset --- 0dB ~ 25dB
Page28
Contents
Page29
HSDPA Mobility Management

z
HSDPA connection
One HSDPA user has up to one HSDPA connection with network at

the same time
HSDPA connection HO means HO caused by moving
DPCH connection
DPCH connection has same function as R99 HO, Containing SHO,

HHO and inter-RAT HO
Both HSDPA connection and DPCH connection HO are based on UE

measurement report and other information, and they are controlled by
UTRAN side
Page30
Intra-frequency Handover of HSDPA

Cell 1(HSDPA)
Cell 2(HSDPA)
before handover
Cell 1(HSDPA)
Cell 2(HSDPA)
after handover
The 1D event is triggered by

cell 2
Cell 1(HSDPA)
Cell 2(R99)
before handover
Cell 1(HSDPA)
Cell 2(R99)
after handover
Soft handover
The 1B (remove) is triggered
by HSDPA cell
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
after handover
Soft handover
HSDPA cell is added into active set
The 1D event is triggered by HSDPA
cell
Page31
Cell 2(R99)
Intra-frequency Handover of
HSDPA
Parameter
The timer length of D2H Intra-handover --- 0s ~ 999s
MML: SET HOCOMM
Page32
Handover Between a Cell Supporting the

F-DPCH and a Cell Not Supporting the F-DPCH
If all the cells in the active set support the F-DPCH after the active set is updated
and the SRB is carried on the DCH, the SRBD2HHoTimer starts. After this timer
expires, the RNC decides whether to switch the SRB to the HS-DSCH
z
Parameter
The timer length of Srb Over Hspa Retry

Delay[100ms] --- 0s ~ 60s
MML: SET HOCOMM
After the UE is handed over to an HSDPA cell from an R99 cell, the D2HRetryTimer
starts. After this timer expires, the RNC decides whether to switch the SRB to the HSDSCH and whether to set up the F-DPCH. D2HRetryTimer is set through The timer
length of D2H Inter-freq handover and The timer length of D2H Intra-freq
handover
z
Page33
Inter-frequency Handover of HSDPA

z
Inter-frequency handover can be triggered on the basis of coverage, load,
and Hierarchical Cell Structure (HCS).

The introduction of HSDPA does not affect the triggering conditions and
decisions of these types of inter-frequency handover

Scenario
Description
Scenario 1
Inter-Frequency Handover from an HSDPA Cell to an R99 Cell

The UE moves from an HSDPA cell to a non-HSDPA cell.
Event 2B is triggered
Scenario 2
Inter-Frequency Handover from an R99 Cell to an HSDPA Cell

The UE moves from a non-HSDPA cell to an HSDPA cell.
Scenario 3
Inter-Frequency Handover Between HSDPA Cells

The UE moves from one HSDPA cell to another HSDPA cell.
Page34

Cell 1(HSDPA)
Cell 2(HSDPA)
before handover
Cell 1(HSDPA)
Cell 2(HSDPA)
after handover
Inter-frequency handover
2B is triggered by HSDPA
cell (cell2)
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
Cell 2(R99)
Cell 1(HSDPA)
before handover
before handover
after handover
after handover
The 2B event is triggered by
HSDPA cell
2B is triggered by R99 cell
Page35
Cell 2(R99)

Parameter
The timer length of D2H Inter-handover--- 0s ~ 999s
MML: SET HOCOMM
Page36
Inter-RAT Handover of HSDPA

z
z
The introduction of HSDPA does not affect the inter-RAT handover algorithms.
The switch CM permission ind on HSDPA decides whether the Compressed
Mode (CM) can be used on HSDPA. For detailed information about the switch,
see Inter-Frequency Handover of HSDPA
When the UE handover to a cell supporting the F-DPCH from another system
and a UL or DL event 4A is reported, the RNC decides whether to change the
bearing mode of TRB and SRB.
If the TPC command is carried on the F-DPCH between the UE and the
UTRAN, the SRB and the TRB are carried on the HS-DSCH. If a cell not
supporting the F-DPCH is added to the active set, all the F-DPCHs are
deleted. In addition, new DPCHs between the UE and all the cells in the
active set are set up to carry the SRB and TPC commands. In this case, the
TRB is still carried on the HS-DSCH.
Page37
Contents
Page38
HSDPA Channel Switching

With introducing HSDPA technology, the UE has one more RRC
state CELL_DCH (with HS-DSCH)

CELL_DCH
CELL_PCH
CELL_FACH
CELL_DCH
(with HS-DSCH)
UE State Transition
Channel Switching
Cell-DCH ( with HS-DSCH ) Cell-DCH
HS-DSCH DCH
Cell-DCH ( with HS-DSCH ) Cell-FACH
HS-DSCH FACH
Page39
Channel Switching between HS-DSCH and DCH
Channel Switch from HS-DSCH to DCH

Mobility
Channel Switch from DCH to HS-DSCH

Mobility
Timer (H Retry Timer)
Traffic Volume
~ The UE is rejected by the admission control algorithm when it attempts to
access an HSDPA cell. If the activity of the UE that performs data services
increases and the RNC receives an event 4A report, the RAN tries to hand
over the UE from the DCH to the HS-DSCH
Channel switching from DCH to HS-DSCH needs to implement the process of
HSDPA directed retry
Page40

Parameters
HSDPA_ State_ Trans _Switch --- Enable , Disable
MML: SET CORRMALGOSWITCH
PS _ BE _ State_ Trans _Switch --- Enable , Disable

PS _Non_ BE _ State_ Trans _Switch --- Enable ,
Disable
H Retry Timer Length --- 0 ( disable ), 1180s
MML:SET COIFTIMER
Page41

z
Channel Switching between HS-DSCH and FACH
Since the HSDPA UE occupies the DPCH, the RAN will switch the
transport channel from HS-DSCH to FACH to reduce occupation of
the DPCH when the following conditions are met
The HS-DSCH carries the BE service for the UE
There is a few data flow of any of the services for a certain length of time
By contrary, if data service activity increased, for example, when the

RNC receives a 4A event measuring report ,state transfer is triggered
for Cell-FACH to Cell-DCH ( with HS-DSCH )
Page42

Parameters
BE HS-DSCH to FACH Transition Timer --- 1s~65535s
MML:SET UESTATETRANS
BE HS-DSCH to FACH 4B threshold --- 8163264

12825651210242k3k4k6k8k12k
16k24k32k48k64k96k128k192k256k
384k512k768kbytes
BE HS-DSCH To FACH 4b Time To Trigger --- 0, 10,
20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000ms
BE HS-DSCH To FACH 4b Pending Time After
Trigger --- 250, 500, 1000, 2000, 4000, 8000, 16000ms
Realtime Traff DCH Or HSPA To FACH Transition
Timer --- 1s~65535s
Realtime Traff DCH Or HSPA To FACH 4b Threshold -- 816326412825651210242k3k4k
6k8k12k16k24k32k48k64k96k
128k192k256k384k512k768kbytes
Realtime Traff DCH Or HSPA To FACH 4b Time To
trigger --- 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240,
320, 640, 1280, 2560, 5000ms
Realtime Traff DCH Or HSPA To FACH 4b Pending
Time --- 250, 500, 1000, 2000, 4000, 8000, 16000 ms
Page43
Contents
Page44
HSDPA Qos Management

z
QoS Requirements of Different Services
IMS / SRB
Voice over IP (Conversational Service)
Streaming Service
BE Service
QoS Parameters Mapped onto the MAC-hs Layer of the NodeB
MAC-hs Discard timer
Scheduling Priority Indicator (SPI)
Guaranteed Bit Rate (GBR)
Page45
IMS/SRB: Signaling has a high requirement for transmission delay. If the requirement
cannot be met, the service may be affected. For example, an SRB delay may lead to a
handover delay. The average rate of signaling is lower than 20 kbit/s.
VoIP: The VoIP service is highly delay sensitive. The end-to-end delay of a voice frame
should be shorter than 250 ms. The tolerant frame error rate is about 1%. The average
rate of the VoIP service with the header compressed is about 20 kbit/s.
Streaming: The streams at the receiver end should be continuous. Compared with VoIP,
the streaming service has a relatively low delay sensitivity, because a buffer that can
avoid jitter for several seconds is configured at the receiver end. When the rate of the
streaming service is equal to or higher than the GBR, the QoS can be guaranteed.
BE (background and interactive): The data rate at the service source end can reach a high
value, for example, several Mbit/s during a burst. The BE service has a low
requirement for transmission delay but has a high requirement for reliable transmission.
MAC-hs Discard timer: An MAC-d PDU in an MAC-hs queue is discarded if the waiting
time exceeds the length of this discard timer. This timer is set on the RNC side. It is an
optional IE on the Iub interface. For the VoIP service, the timer is set to 100 ms. For
the BE and streaming services, the timer may not be set. For an MAC-hs queue
configured with the discard timer, the scheduler should send out the MAC-d PDUs
before expiry of the timer.
Scheduling Priority Indicator (SPI): This parameter specifies the scheduling priority of
an MAC-hs queue. The priority is derived from the Traffic Class, Traffic Handling
Priority, and User Priority that are mapped onto this queue.
Guaranteed Bit Rate (GBR): It is configured on an MAC-hs queue basis. For the
streaming service, the GBR specifies the rate that can meet the requirement of the
user for viewing and the GBR of a queue is determined by the NAS. For the BE service,
the GBR specifies the required minimum rate for the service of the users in the RAN.
The GBR of a BE service user is set through the SET USERGBR command on the
RNC side. The setting is based on the user priority, namely, gold user, silver user, or
copper user.
Services with different QoS requirements require different QoS guarantee policies. For
example, the VoIP service has a high requirement for delay. To limit the delay caused
by flow control or scheduling within a proper range, the algorithm grants the VoIP
queue a priority to occupy resources first. The streaming service has a high
requirement for GBR. Therefore, the scheduling and flow control algorithms guarantee
that the average rate of the service is not lower than the GBR during Iub traffic
distribution and Uu resources allocation. The BE service has a high requirement for
reliability, which can be achieved through more retransmissions on the Uu interface.

z
Scheduling Priority Indicator (SPI) is the relative priority of the HS-DSCH

FP data frame and the SDUs included
The SPI is set according to the following factors
Traffic Class (TC)
Traffic Handling Priority (THP) of the interactive service
User Priority
The SPI is set on the RNC LMT and sent to the NodeB through NBAP
signaling
Page47
User priority
ARP
10
11
12
1
3
14
15
User
priority
Error
The case for mapping of traffic class, user priority, and THP to SPI
Traffic Class
Traffic Class
User
Priority
THP
SPI
Interactive
SRB
signaling
No ARP
None
15
IMS signaling
No ARP
None
14
Conversation
al (VoIP)
None
13
None
13
None
13
None
12
None
11
None
11
Streaming
User
Priority
Background
THP
SPI
10
3 to 15
3 to 15
3 to 15
None
None
None
The case for algorithm configuration based on SPI
SPI
Max
Retrans
mission
Count
EPF Schedule
Algorithm Switch
Flow Control
Algorithm Switch
Weight of
SPI
15
DS_PQ_SCHEDULE
FLOW_CONTRL_FREE
100%
14
DS_PQ_SCHEDULE
FLOW_CONTRL_FREE
100%
13
DS_URGENT_SCHEDULE
FLOW_CONTRL_FREE
100%
12
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
100%
11
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
90%
10
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
100%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
100%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
100%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
90%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
90%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
90%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
80%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
80%
TS_SCHEDULE
FLOW_CONTRL_DYNAMIC
80%

Parameters
MAC-hs Discard timer [ ms ]--- 20, 40, 60, 80, 100,

120, 140, 160, 180, 200, 250, 300, 400, 500, 750, 1000,
1250, 1500, 1750, 2000, 2500, 3000, 3500, 4000, 4500,
5000, 7500 ms
MML: ADD TYPRABHSPA
Scheduling Priority Indicator (SPI) --- 0~15
MML: SET SCHEDULEPRIOMAP
Traffic Class --- CONVERSATIONAL, STREAMING,

INTERACTIVE, BACKGROUND, IMS, SRB
User Priority --- Gold, Silver, Copper
Traffic Handling Priority (THP) --- 1~15
Weight of SPI (%) --- 1% ~ 100%
MML: SET MACHSSPIPARA
Page49
MAC-hs Discard timer specifies the maximum waiting time for sending a MAC-d PDU
after it is put in the MAC-hs queue. The MAC-d PDU is discarded when the timer
expires.
SPI indicates the scheduling priority of the service of the user. The value 15 indicates the
highest priority and the value 0 indicates the lowest priority.
User priority is set according to the ARP
THP is valid only when the traffic class is interactive. The value 1 indicates the highest
priority, 14 indicates the lowest priority, and 15 indicates no priority
Weight of SPI is used in the scheduling algorithm to select a queue to send data. To
implement differentiated services, it can adjust the proportions of the rates obtained by
the users with different SPIs in the same channel conditions. When Scheduling
Method is set to EPF, this parameter is valid in the scheduling algorithm. When Flow
Control Switch is set to SIMPLE_FLOW_CTRL or AUTO_ADJUST_FLOW_CTRL,
this parameter is valid in the flow control algorithm.
HSDPA Scheduling Algorithm

z
Huawei RAN10 product supports 4 scheduling algorithms:
Max C/I
RR (Round Robin)
PF (Proportional Fair)
EPF (Enhanced Proportional Fair)
Page50
When the HS-DSCH carries only the BE service, the PF scheduling algorithm can make a
tradeoff between user equity and cell throughput. When the HS-DSCH carries more
types of services, such as VoIP, streaming, SRB, and IMS, the HSDPA scheduling
algorithm needs to guarantee the QoS. The reason is that such services have high
requirements for delay or GBR. Based on the PF, the EPF algorithm is designed to
guarantee the QoS of these services as follows.

Scheduling
Algorithm
Factor considered in
algorithm
MAX C/I
CQI
To select users according to the CQI value in descending order. The radio
channel quality is the only factor considered in this algorithm and therefore the
fairness among users cannot be guaranteed.
RR
Waiting time of data

buffered in the
MAC-hs priority
queue
To select users according to the waiting time of data buffered in the MAC-hs
priority queue in descending order. The waiting time is the only factor
considered in this algorithm and therefore the fairness among users can be
guaranteed but the cell capacity degrades because the channel quality is not
taken into account.
PF
CQI,
Average data rate of
the MAC-hs priority
queue
To select users according to the value of R/r in descending order, where R is

the maximum data rate corresponding to the CQI, and r is the average data
rate of the MAC-hs priority queue.
The PF scheduler uses the variation in the radio channel qualities of
individual users (for example, multi-user diversity) and provides the user with
an average throughput proportional to its average CQI. This algorithm is a
tradeoff between cell capacity and fairness among users.
EPF
Queue types i.e.

QOS requirement of
different services
DS_PQ_SCHEDULE: SRB/IMS scheduling policy. The SRB and IMS queues are
scheduled before the VoIP, streaming and BE queues. DS means delay sensitive. PQ
means priority queue.
DS_URGENT_SCHEDULE: VoIP scheduling policy. The VoIP queues are
scheduled before the streaming and BE queues but after the SRB and IMS queues.
TS_SCHEDULE: streaming/BE scheduling policy. The streaming and BE queues
are scheduled after the SRB, IMS, and VoIP queues. Among the streaming and BE
queues, the resources for GBR are allocated first. The remaining resources are
allocated as required by golden, silver, and copper users. TS means throughput
sensitive
Scheduling Principle
Page51
When the HS-DSCH carries only the BE service, the PF scheduling algorithm can make a
tradeoff between user equity and cell throughput. When the HS-DSCH carries more
types of services, such as VoIP, streaming, SRB, and IMS, the HSDPA scheduling
algorithm needs to guarantee the QoS. The reason is that such services have high
requirements for delay or GBR. Based on the PF, the EPF algorithm is designed to
guarantee the QoS of the multiple services

z
EPF ( Enhanced Proportional Fair )
The types of queues are considered
Qos guarantee for delay-sensitive service (delay) and throughputsensitive service (GBR)
Configurable for SPI
Schedulin
g
Algorithm
EPF
Factor
considered in
algorithm
Queue types i.e.
QOS requirement
of different
services
Scheduling Principle
DS_PQ_SCHEDULE: SRB/IMS scheduling policy. The SRB and
IMS queues are scheduled before the VoIP, streaming and BE
queues. DS means delay sensitive. PQ means priority queue.
DS_URGENT_SCHEDULE: VoIP scheduling policy. The VoIP
queues are scheduled before the streaming and BE queues but after
the SRB and IMS queues.
TS_SCHEDULE: streaming/BE scheduling policy. The streaming
and BE queues are scheduled after the SRB, IMS, and VoIP queues.
Among the streaming and BE queues, the resources for GBR are
allocated first. The remaining resources are allocated as required by
golden, silver, and copper users. TS means throughput sensitive
Page52
When the HS-DSCH carries more types of services, such as VoIP, streaming, SRB, and
IMS signaling, the HSDPA scheduling algorithm needs to guarantee the QoS. The
reason is that such services have high requirements for delay or GBR. Based on the
PF, the EPF algorithm is designed to guarantee the QoS of the following services:
z
SRB and IMS have high requirements for service connection delay and handover delay.
In addition, the average traffic volume and the consumption of the Uu interface are low.
Therefore, the algorithm always selects the MAC-hs queues of SRB and IMS first.
The VoIP service is highly delay sensitive. The maximum delay of MAC-d PDUs in a
queue is specified by the discard timer of the MAC-hs queue. The scheduler needs to
send out the MAC-d PDUs before the discard timer expires. The discard timer is
usually shorter than 100 ms. Therefore, the scheduler has little chance of considering
the channel quality. The scheduler always selects VoIP services after scheduling SRB
and IMS services. Among MAC-hs queues of VoIP, the selection is based on both
delay and channel quality.
The streaming service is usually the CBR (Constant Bit Rate) streaming service. If the
rate of this service is not lower than the GBR, the user can obtain good experience.
Therefore, the scheduler needs to guarantee the GBR. When the average rate of the
streaming service is lower than the GBR, the queues of the streaming service are
selected first after SRB, IMS, and VoIP. Among the MAC-hs queues of the streaming
service, the selection is based on PF.
The BE service is allocated with the remaining resource after the resource
requirements of the SRB, IMS, VoIP, and streaming services are met. Among the
MAC-hs queues of the BE service, the selection is based on PF. In addition, the
resource allocation complies with the following rules.
Firstly, the GBR should be guaranteed first.

Secondly, the algorithm considers the requirement for user differentiation. For all
the users in the cell, the scheduler intends to allocate the radio resource in
proportion to their Weight of SPI, which is based on user priorities, eg. gold,
silver and copper.
For example, assuming that radio resource is the bottleneck, gold , silver
and copper users of same channel quality are using FTP service
simultaneously, then the Uu throughputs of gold, silver and copper users
are in proportion to the ratio of their SPI weights.
For another example, assuming that the silver user is using HTTP service,
the gold and copper user are using FTP service, and the silver user are
reading the HTTP page, then the gold and copper users share the radio
resource, and the Uu throughput of the gold and copper users are in
proportion to the ratio of their SPI weight.
Page54

Parameters
Scheduling Method --- EPF (Enhanced PF), PF (PF),

RR (Round Robin), MAXCI (Max C/I )
MML: SET MACHSPARA
EPF Schedule Algorithm Switch --DS_PQ_SCHEDULE, DS_URGENT_SCHEDULE,

TS_SCHEDULE
MML: SET MACHSSPIPARA
Page55
EPF Schedule Algorithm Switch is valid only when Scheduling Method is set to EPF
Contents
Page56
HSDPA TFRC Selection

z
Transport Format Resource Combination (TFRC) selection determines

the transport block size, modulation type, HS-PDSCH codes, and HSPDSCH transmission power
The UEs estimate and send CQI to the UTRAN to aid the TFRC selection
The CQI indicates the number of bits that can be transmitted to the UE
through certain HS-PDSCH power, a certain modulation method (QPSK
or 16QAM), and a certain number of HS-PDSCH codes with an initial
transmission BLER of 10%
Page57

z
TFRC selection is performed according to the following factors
Available power of the HS-PDSCH
Available codes of the HS-PDSCH
CQI from the UE
UE capability
Page58

z
If there is sufficient amount of data cached in the MAC-hs queue

(TBSmax < Queue length), the data is scheduled for the UE as much as
possible in the maximum format of TFRC, that is, TBS = TBSmax
If there is insufficient amount of data cached in the queue (TBSmax >
Queue length), the Uu resources necessary for the UE are allocated on
the basis of the amount of data in the queue
Select the TFRC (power, code, and modulation mode) by searching the CQIMax TBS mapping table and taking the amount of data cached in the queue
into consideration
The search is based on the priority defined by the Resource Allocate Method
parameter, that is, code preferable or power preferable
Page59

z
TFRC Selection Process
Macro cells usually have a

poor radio environment
with limited power
resource. The downlink
power resource of a cell is
used up when the downlink
code resource is enough
Indoor pico cells usually

have a good radio
environment with
limited code resource.
The downlink code
resource of a cell is
used up when the power
resource is enough
Page60

z
Example of TFRC selection process
Page61

z
After TFRC is determined, the matched CQI of TBS in the CQIMaxTBS mapping table is determined. This CQI is expressed as
CQIused. Then, the transmit power of the HS-PDSCHs is
calculated as follows:
POWERHS-PDSCH = PCPICH + (CQIadjusted - CQIused)
Parameters
Resource Allocate Method --- code priority,

power priority
MML: SET MACHSPARA
MAX POWER PER HS-USER --- 1% to 100%
Page62
Within one TTI, the HS-PDSCH power and HS-SCCH power allocated to one UE cannot
exceed the value of the MAX POWER PER HS-USER parameter.
The HSDPA cell load is limited by the The Offset of HSPA Total Power parameter.
z
= Max(-6, Min(13, PCellMAX - PCPICH - MPOconstant))
PCell-MAX - PCPICH = maximum transmit power of the cell - CPICH transmit

power
MPOconstant represents HS-PDSCH MPO Constant and can be set on the RNC
LMT (MML: ADD CELLHSDPA)
Contents
Page63
Overview of NodeB HSDPA Flow

Control
z
HSDPA Flow control is a process used to control HSDPA data flow from RNC
MAC-d to NodeB MAC-hs according to Iub bandwidth and air interface bandwidth
After HSDPA is introduced, users rate on air and on Iub is not consistent. It is
necessary to adjust rate on Iub according to its rate on air
The signaling of HSDPA flow control process is implemented through the capacity
request and capacity allocation. The NodeB allocates the capacity for each
MAC-hs queue, and the RNC limits the downlink rate of each MAC-hs queue
according to the allocated capacity
capacity means how much data RNC can send to NodeB in an interval
Page64
Signaling of HSDPA Flow Control

z
Capacity Request includes following IEs
CmCH-PI : Scheduling priority Indicator ( SPI ) of the queue
Uesr buffer size: Occupancy status of RLC buffer
Page65
The RNC sends Capacity Request to the NodeB, when some RLC PDUs are
accumulated in RLC buffer or CREDITS (i.e. some control messages in the latest
Capacity Allocation) are expired
The RNC also sends Capacity Request if No RLC PDU but allocated capacity is greater
than zero, indicating the NodeB can stop Capacity Allocation
Signaling of HSDPA Flow Control

z
The NodeB sends the HS-DSCH Capacity Allocation message to the

RNC in response to a HS-DSCH Capacity Request
Capacity Allocation includes following IEs
Maximum MAC-d PDU Length: maximum PDU size among the MAC-d PDU
sizes configured in the NBAP messages
HS-DSCH Credits : total quantity of Mac-d PDU that CRNC can send during
HS-DSCH interval
HS-DSCH interval : time interval during which the HS-DSCH credits granted in
Capacity Allocation can be used
HS-DSCH Repetition : number of subsequent intervals during which the HSDSCH Credits IE granted in the HS-DSCH CAPACITY ALLOCATION control
frame can be used and the value 0 means that there is no limit to the repetition
period
Page66
Capacity Allocation Policy

z
Generally, the NodeB allocating the capacity to a MAC-hs queue

considers the data rate on the Uu interface and Iub available bandwidth
For different service (i.e. QoS requirements), the NodeB uses different
flow control policies
Flow control free policy for SRB, IMS signaling or VOIP
Dynamic flow control policy (for streaming service or BE service)
Flow control free Policy
After the HS-DSCH bearer is set up, the NodeB sends a capacity allocation
message to the RNC, indicating that the DL traffic of the new MAC-hs queue is
not limited and the RNC MAC-d can send data as much as required
The allocation keeps unchanged for the service
The policy of no flow control policy is applied only to VoIP, IMS, and SRB, for
these services are delay sensitive and have a relative low rate
Page67
For VOIP, the flow control free Policy is applied to the Mac-hs queue due to
It is highly delay sensitive. Therefore VOIP service is mapped onto bearers with high
priorities to guarantee the high requirement for delay. The bearer priority of VOIP on
the Iub interface is higher than that of non-real-time service. The scheduling priority of
VOIP queue on Uu interface is also higher than that of non-real-time service queue.
Average rate of VOIP is low. The rate is about 20kbps. The probability of congestion
incurred by VOIP on the Uu interface and Iub interface is low
The IMS signaling / SRB has a low average rate. It is also highly delay sensitive. So flow
control free is also applied to them.

z
Dynamic flow control
Dynamic flow control is mainly applied to MAC-hs queues of

BE service, for theses services are not delay sensitive, the rate
varies in a wide range, and will reach a high rate during a burst
Dynamic flow control is also applied to MAC-hs queues of

streaming service, for streaming service has a relative high
rate and may result in congestion on Uu
Page68

Dynamic flow control
Dynamic flow control process with adaptive Iub bandwidth is as
follows:
The congestion status of the transport network is reflected to NodeB through DRT and
FSN. The NodeB adaptively adjusts the Iub bandwidth available for HSDPA based on
the congestion detection
Depending on the available bandwidth and rate on air interface, the NodeB allocates
bandwidth to HSDPA users and performs traffic shaping (Iub shaping) to avoid
congestion and packet loss over the Iub interface
The RNC limits the flow of HS-DSCH data frames for each MAC-hs queue according
to the HS-DSCH capacity allocation
Parameters
Flow Control Algorithm Switch --FLOW_CONTRL_FREE, FLOW_CONTRL_DYNAMIC
We can configure the Flow Control Algorithm according to SPI.

Default configuration for Flow Control Algorithm
MML: SET
MACHSSPIPARA
Page69
HSDPA Flow Control

z
Dynamic flow control consists of the following modules:
Adaptive capacity allocation
NodeB adaptively allocates capacity to an MAC-hs queue based on its rate on air
interface
Capacity means how much data RNC can send to NodeB in an interval
Congestion control on Iub
The total flow of all the MAC-hs queues should not exceed the available Iub
bandwidth to avoid congestion on Iub
NodeB provides the following functions to avoid Iub congestion:
Adaptive adjustment of Iub bandwidth
~ NodeB periodically detects Iub congestion and adaptively adjusts the available Iub
bandwidth according to the Iub state
Iub shaping
~ Iub shaping is used to allocate Iub bandwidth to every MAC-hs queue based on the
available Iub bandwidth and ensure the total flow of the queues does not exceed the
available Iub bandwidth. Thus, congestion control is achieved on the Iub interface, which
increases the bandwidth usage and avoids overload
Page70
HSDPA Dynamic Flow Control

z
Dynamic flow control policy is configured through the Flow control switch.
Parameters
Flow Control Switch--- SIMPLE_FLOW_CTRL,

AUTO_ADJUST_FLOW_CTRL,
NO_FLOW_CONTROL
MML: SET
HSDPAFLOWCTRLPARA
If the switch is set to AUTO_ADJUST_FLOW_CTRL, the NodeB performs
adaptive capacity allocation, Iub shaping and adaptive adjustment of Iub

bandwidth
When the Iub resource is the bottleneck, the algorithm performs capacity
allocation based on the bit rate on the Uu interface and the Iub shaping of
dynamic flow control queues.
When the congestion on the Iub interface is invisible for the NodeB, the
algorithm performs capacity allocation based on the bit rate on the Uu

interface
Page71
HSDPA Dynamic Flow Control

z
If the switch is set to NO_FLOW_CONTROL, the NodeB performs

adaptive capacity allocation, and does not perform Iub shaping
and adaptive adjustment of Iub bandwidth
If the switch is set to SIMPLE_FLOW_CTRL, the NodeB performs

adaptive capacity allocation and Iub shaping, and does not
perform adaptive adjustment of Iub bandwidth
Some Iub bandwidth should be reserved for HSDPA users. This

setting is used mainly for testing the algorithm during the design
phase
Page72
HSDPA Flow Control

z
MAC-hs / MAC-d flow control
The flow control keeps the queue occupancy in a reasonable

level in order to reduce data transmission delay, L2 layer signal
delay, and discarding as the result of priority queue congestion
or reset during handover
In this sense, the functionality is called capacity allocation

adaptive to Uu interface bit rate, where capacity allocation for
each priority queue is based on the Uu interface bit rate and
the buffer occupancy level
Page73
HSDPA Flow Control

z
MAC-hs / MAC-d flow control when Iub interface resource is

not congested
If there is not enough data in the queue, large bandwidth is

allocated
If there is enough data in the queue, the bandwidth that is

close to the rate on the Uu interface is allocated
If there is too much data in the queue, small bandwidth or no

bandwidth is allocated
Page74
If the resource on the Uu interface is the bottleneck, or the total traffic volume within the
NodeB (i.e. Mac-hs queue) is low, or the congestion on the Iub interface is managed
by the RNC back pressure algorithm, then the algorithm allocates the capacity based
only on the rate of each queue on the Uu interface. The MAC-hs performs flow control
for each priority queue periodically.
Whether there is enough data in the queue is judged by the time length of the priority
queue. Time length is defined as the ratio of the length of the queue to the air interface
bit rate of the queue. In this way, the average delay of MAC-d PDU at the MAC-hs
layer is limited within a hundred milliseconds.
HSDPA Flow Control

z
Adaptive adjustment of Iub bandwidth available for HSDPA
Adaptive adjustment of Iub bandwidth available for HSDPA is a

part of the mechanism to control the congestion on Iub.
Adaptive adjustment of Iub bandwidth available for HSDPA

comprises the following process
detection of Iub congestion
adjustment of Iub bandwidth available
Page75
HSDPA Flow Control

z
Detection of Iub congestion
This Iub congestion detection algorithm

periodically measures the transmission delay and
frame loss
Assuming that for each MAC-d flow the HS-DSCH

data frame must be delivered to the MAC-hs layer
in FSN sequence, Iub frame loss is counted and
the frame loss ratio at the Iub level in a specific
time window is calculated
The HS-DSCH data frame transmission delay is

the interval from the time when HS-DSCH data
frame generated in the RNC (identified as DRT) to
the time when the frame arrives at the NodeB
MAC-hs layer
Page76
Frame Sequence Number: used to detect frame loss over the Iub interface.
DRT: Delay Reference Time, used to detect transmission delay over the Iub interface
HSDPA Flow Control

z
Detection of Iub congestion
Periodically the Iub congestion status is differentiated into three
levels:
Congestion due to delay means that the delay buildup is larger than the
Time Delay Threshold
Congestion due to frame loss that means the frame loss ratio is larger than
the Discard Rate Threshold. Otherwise frame loss may be caused by an
Iub bit error
Congestion released means that there is no congestion due to delay and

no congestion due to frame loss
Parameters
Discard Rate Threshold --- 0~100%
MML: SET
Time Delay Threshold --- 0~500ms
HSDPAFLOWCTRLPARA
Page77
The other two thresholds related to Iub congestion detection are described as follows:
Discard Rate Threshold: is used to determine whether the Iub interface is congested
because of frame loss. Generally, frame losses due to bit error are less than those due
to congestion. By default, the threshold is set to 5%. It can be adjusted on the basis of
transport network quality. The HS-DSCH frame error rate on the Iub interface within
300 ms can be a reference. If the threshold is too high, the congestion on the Iub
interface cannot be relieved in time. If the threshold is too low, the Iub interface will be
regarded as congested in the case of frame loss due to bit error. Thus, the Iub
bandwidth cannot be fully utilized.
Time Delay Threshold: is used to determine whether the Iub interface is congested
because of delay buildup. By default, this threshold is set to 20 ms. It can be adjusted
on the basis of the delay jitter allowed on the transport network. Generally, the
threshold is set to the allowed delay jitter plus several ms. If the threshold is too high,
the transmission on the Iub interface will be much delayed when the Iub interface is the
bottleneck. If the threshold is too low, the Iub interface will be regarded as congested
by mistake. Thus, the transmission resource cannot be fully utilized.
HSDPA Flow Control

z
Adjustment of Iub bandwidth available
The algorithm actively adjusts the Iub bandwidth based on the congestion
detection
If the Iub is in the congestion due to delay, the Iub bandwidth available for HSDPA is
decreased by a step in direct proportion to the delay buildup
If the Iub is in the due to frame loss, the Iub bandwidth available for HSDPA is
decreased by a big step regardless of the delay buildup
If the Iub is in the congestion released, the Iub bandwidth available for HSDPA is
increased by a smaller step, applying the Policy of increasing slowly, yet decreasing
fast
In a time window of tens of seconds, if consecutive "congestion released" is

detected, the Iub resource is identified as not the bottleneck. In this case, the
MAC-hs/MAC-d flow control does not take the Iub bandwidth available for
HSDPA as the limitation of capacity allocation
Page78
Contents
Page79
Thank you
www.huawei.com
WCDMA Dynamic
Channel
Configuration Control
(DCCC)
www.huawei.com
340
Objectives
z
Upon completion of this course, you will be able to:
Briefly explain DCCC benefit
Describe how the DCCC algorithm works
Page1
341
Contents
1. DCCC Overview
2. Rate Reallocation Based on Traffic Volume
3. Rate Reallocation Based on Throughput
4. Rate Reallocation Based on Link Quality
5. UE State Transition Algorithm
6. Always Online
Page2
342
DCCC Description
z
DCCC: Dynamic Channel Configuration Control
DCCC, as one the most important RAN feature, will allocate

dynamic resource according to the service request
Meanwhile, DCCC is an effective method to increase the radio

resource utilization efficiency.
Page3
343
Contents
1. DCCC Overview
6. Always Online
Page4
344
Contents
2.1 Traffic Volume Measurement and Event Reporting
2.2 Rate Reallocation Based on Traffic Volume
2.3 Signaling Procedure
Page5
345
Traffic Volume Measurement

z
In the uplink, the UE measures Dedicated Traffic Channel

(DTCH), (that is, buffer occupancy of RLC entities), to
obtain the uplink traffic volume.
In the downlink, the RNC measures the DTCH, (that is,

buffer occupancy of RLC entities), to obtain the downlink
traffic volume.
Page6
Rate reallocation herein is based on the traffic volume measurement. After comparing the
measurement results with associated thresholds, the RNC can trigger rate reallocation.
The traffic volume measurements defined in 3GPP TS 25.331 are applicable only to the uplink.
Regarding the downlink traffic volume measurements and associated rate reallocation, the
design and implementation are Huawei specific.
346
Event
z
Event 4a
Traffic volume is above a threshold -> High active
Event 4b
Traffic volumes is below a threshold -> Low active
Page7
347
Event Reporting
z
Traffic volume measurement triggering can be associated

with both the time-to-trigger and the pending time after
trigger
Time-to-trigger is used to get time domain hysteresis, that is,

the condition must be fulfilled during the time-to-trigger period
before a report is sent.
Pending time after trigger is used to limit consecutive reports

when one traffic volume measurement report has already been
sent.
Page8
348
Event Reporting
z
Event 4a triggered by an increase in the transport channel

traffic volume
In the uplink:
Page9
When the traffic volume is higher than the value of Traffic Measurement Event 4A
threshold for a period of time defined by Time to trigger 4A, the UE reports an event
4a. No more events 4a are reported during the time defined by Pending time after
trigger 4A.
In the downlink:
When the traffic volume is higher than the value of Traffic Measurement Event 4A
threshold for a period of time defined by Time to trigger 4A, the RNC reports
internally an event 4a. No more events 4a are reported during the time defined by
Pending time after trigger 4A.
349
Event Reporting
z
Event 4b triggered by a decrease in the transport channel

traffic volume
In the uplink:
Page10
When the traffic volume is lower than the value of Traffic Measurement Event 4B
threshold for a period of time defined by Time to trigger 4B, the UE reports an event
4b. No more events 4b are reported during the time defined by Pending time after
trigger 4B.
In the downlink:
When the traffic volume is lower than the value of Traffic Measurement Event 4B
threshold for a period of time defined by Time to trigger 4B, the RNC reports
internally an event 4b. No more events 4b are reported during the time defined by
Pending time after trigger 4B.
350
Parameters
z
All the preceding parameters associated with events 4a and

4b are configurable in each direction, that is, either uplink or
downlink.
DIRECTION
Parameter name: Direction
Recommended value: None
The Direction parameter has to be set before the setting of the event-related parameters.
Page11
If Direction is set to UPLINK, all the event-related parameters take effect in the uplink.
If Direction is set to DOWNLINK, all the event-related parameters take effect in the
downlink.
DIRECTION
Parameter name: Direction
Value range: DOWNLINK, UPLINK
Physical value range: DOWNLINK, UPLINK
Unit: None
Content: This parameter defines the Traffic Volume Measurement (TVM) direction.
DOWNLINK: Conduct downlink TVM.
UPLINK: Conduct uplink TVM.
Recommended value: None.
Set this parameter through ADD TYPRABDCCCMC
351
Parameters
z
EVENT4ATHD
Parameter name: Traffic Measurement Event 4A threshold
Recommended value: D1024, namely 1024Byte
EVENT4BTHD
Parameter name: Traffic Measurement Event 4B threshold
Recommended value: D128(rate < 128k),D256(rate >= 128k)
EVENT4ATHD
Page12
Parameter name: Traffic Measurement Event 4A threshold

Value range: D16, D32, D64, D128, D256, D512, D1024, D2k, D3k, D4k, D6k, D8k,
D12k, D16k, D24k, D32k, D48k, D64k, D96k, D128k, D192k, D256k, D384k, D512k,
D768k
Physical value range: 16, 32, 64, 128, 256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k, 16k, 24k,
32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k .
Unit: byte
Content: This parameter defines the threshold to trigger event 4a, that is, the upper
threshold of traffic volume.
Recommended value: D1024 .
EVENT4BTHD
Parameter name: Traffic Measurement Event 4B threshold

Value range: D8, D16, D32, D64, D128, D256, D512, D1024, D2k, D3k, D4k, D6k, D8k,
D12k, D16k, D24k, D32k, D48k, D64k, D96k, D128k, D192k, D256k, D384k, D512k
Physical value range: 8, 16, 32, 64, 128, 256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k, 16k,
24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k .
Unit: byte
Content: This parameter defines the threshold to trigger event 4b, that is, the lower
threshold of traffic volume.
Recommended value: D128(rate < 128k),D256(rate >= 128k) .
352
Parameters
z
TIMETOTRIGGER4A
Parameter name: Time to trigger 4A
Recommended value: D240, namely 240ms
TIMETOTRIGGER4B
Parameter name: Time to trigger 4B
TIMETOTRIGGER4A
Page13
Parameter name: Time to trigger 4A

Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,
D640, D1280, D2560, D5000
Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 .
Unit: ms
Content: The time-to-trigger for event 4a is used to prevent frequent triggering caused
by small fluctuations of the traffic.
Recommended value: D240.
TIMETOTRIGGER4B
Parameter name: Time to trigger 4B

Value range: D0, D10, D20, D40, D60, D80, D100, D120, D160, D200, D240, D320,
D640, D1280, D2560, D5000
Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280,
2560, 5000 .
Unit: ms
Content: The time-to-trigger for event 4b is used to prevent frequent triggering caused
by small fluctuations of the traffic.
353
Parameters
z
PENDINGTIME4A
Parameter name: Pending time after trigger 4A
PENDINGTIME4B
Parameter name: Pending time after trigger 4B
PENDINGTIME4A
Parameter name: Pending time after trigger 4A
Value range: D250, D500, D1000, D2000, D4000, D8000, D16000
Physical value range: 250, 500, 1000, 2000, 4000, 8000, 16000 .
Unit: ms
Page14
Content: The pending time period after trigger for event 4a is associated with a timer
started after the event measurement report is triggered.
PENDINGTIME4B
Parameter name: Pending time after trigger 4B
Unit: ms
Content: The pending time period after trigger for event 4b is associated with a timer
started after the event measurement report is triggered.
354
Contents
Page15
355
Rate Reallocation Strategy

z
In Huawei implementation, two strategies are available for

rate reallocation based on traffic volume.
RATE_UP_AND_DOWN_ON_DCH
RATE_UP_ONLY_ON_DCH
DCCCSTG
Parameter name: DCCC strategy
Recommended value: RATE_UP_AND_DOWN_ON_DCH
Page16
The RATE_UP_AND_DOWN_ON_DCH strategy means that the rate can be either downsized
or upsized. When the system resources in the network are insufficient, the
RATE_UP_AND_DOWN_ON_DCH strategy is recommended.
The RATE_UP_ONLY_ON_DCH strategy means that the rate can only be upsized. When the
network resources are sufficient, the RATE_UP_ONLY_ON_DCH strategy is recommended.
DCCCSTG
Parameter name: DCCC strategy
Value range: RATE_UP_AND_DOWN_ON_DCH, RATE_UP_ONLY_ON_DCH
Physical value range: 0, 1 .
Content: This parameter defines the strategy of adjusting the data rate of PS BE
services when the UE is in CELL_DCH state.
RATE_UP_AND_DOWN_ON_DCH: Data rate upsizing and rate downsizing

are allowed.
RATE_UP_ONLY_ON_DCH: Only data rate upsizing is allowed. It means that
the state of UE transits from CELL_DCH to CELL_FACH when the 4b event is
reported.
Recommended value: RATE_UP_AND_DOWN_ON_DCH .
Set this parameter through SET DCCC.
356
UL Rate Reallocation Based on Traffic Volume

z
Principles of RATE_UP_AND_DOWN_ON_DCH
Rate downsizing is performed if the RNC receives a report of

event 4b about the uplink traffic volume.
Rate upsizing is performed if the RNC receives a report of

event 4a about the uplink traffic volume.
Page17
The lowest value that the rate can be downsized to is the value of Uplink bit rate threshold
for DCCC. The highest value that the rate can be upsized to is MBR, which is Min{ the
requested maximum bit rate assigned by the CN, the maximum rate supported by UE
capabilities}.
357
UL Rate Reallocation Based on Traffic Volume

z
Principles of RATE_UP_ONLY_ON_DCH
Rate downsizing is prohibited. If a UE is in low activity, the

state of the UE is directly transitted to CELL_FACH if the UE
state transition algorithm is enabled.

Page18
The lowest value that the rate can be downsized to is the value of Uplink bit rate threshold
for DCCC. The highest value that the rate can be upsized to is MBR, which is MIN{the
requested maximum bit rate assigned by the CN, the maximum rate supported by UE
capabilities}.
358
UL Rate Increase
z
When Uplink Rate increase adjust level is 2_Rates, the

rate is upsized directly to the MBR from the Uplink bit rate
threshold for DCCC.
Page19
359
UL Rate Increase
z
When Uplink Rate increase adjust level is 3_Rates, In the

process of upsizing :
If the current rate is lower than the value of Uplink bit rate threshold
for DCCC, the data rate is upsized to the value of Uplink bit rate
threshold for DCCC.
If the current rate equals the value of Uplink bit rate threshold for
DCCC, the data rate is upsized to the value of Uplink mid bit rate
threshold and then to the MBR.
If the current rate is lower than MBR and higher than the value of
Uplink bit rate threshold for DCCC, the rate is upsized to MBR
when upsizing is triggered.
Page20
If the value of Uplink mid bit rate threshold is lower than that of Uplink bit rate threshold
for DCCC, the rate is directly upsized to the MBR, which is the same as the processing
applicable when Uplink Rate increase adjust level is 2_Rates.
360
UL Rate Decrease
z
When Uplink Rate decrease adjust level is 2_Rates, the

data rate is downsized directly to the value of Uplink bit
rate threshold for DCCC
Page21
When Uplink Rate decrease adjust level is 2_Rates, the data rate is downsized directly to
the value of Uplink bit rate threshold for DCCC
361
UL Rate Decrease
z
When Uplink Rate decrease adjust level is 3_Rates, the

data rate is downsized to the value of Uplink mid bit rate
threshold if the current rate is the MBR, and then to the
value of Uplink bit rate threshold for DCCC. If the current
rate is lower than MBR and higher than Uplink bit rate
threshold for DCCC, the rate is downsized to Uplink bit
rate threshold for DCCC when downsizing is triggered.
Page22
362
UL Parameters
z
ULRATEUPADJLEVEL
Parameter name: Uplink Rate increase adjust level
Recommended value: 3_Rates
ULRATEDNADJLEVEL
Parameter name: Uplink Rate decrease adjust level
ULRATEUPADJLEVEL
Parameter name: Uplink Rate increase adjust level
Value range: 2_Rates, 3_Rates
Page23
Content: This parameter defines whether to use 2-rate or 3-rate increase adjustment in
the uplink.
Recommended value: 3_Rates .
Set this parameter through SET DCCC
ULRATEDNADJLEVEL
Parameter name: Uplink Rate decrease adjust level
Content: This parameter defines whether to use 2-rate or 3-rate decrease adjustment
in the uplink. .
363
UL Parameters
z
ULDCCCRATETHD
Parameter name: Uplink bit rate threshold for DCCC
Recommended value: D64, namely 64kbps
ULMIDRATECALC
Parameter name: Uplink mid bite rate calculate method
Recommended value: HAND_APPOINT
ULDCCCRATETHD
Parameter name: Uplink bit rate threshold for DCCC
Value range: D8, D16, D32, D64, D128, D144, D256, D384
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384 .
Unit: kbit/s.
Page24
Content: The larger the parameter value is, the less the algorithm of rate reallocation
based on the traffic volume gains. If the parameter value is too low, however, it may
affect the adverse data transfer.
ULMIDRATECALC
Parameter name: Uplink mid bite rate calculate method
Value range: AUTO_CALC, HAND_APPOINT
Physical value range: None .
Content: This parameter is used to decide the uplink middle bite rate calculation
method that applies when Uplink Rate increase adjust level or Uplink Rate
decrease adjust level is 3_Rates. If Uplink mid bite rate calculate method is set to
AUTO_CALC, the value of Uplink mid bit rate threshold is automatically calculated
by the system. The value of Uplink mid bit rate threshold is equal to the RB rate
closest to the highest rate divided by two. .
Recommended value: HAND_APPOINT.
364
UL Parameters
z
ULMIDRATETHD
Parameter name: Uplink mid bit rate threshold
Page25
ULMIDRATECALC
Unit: kbit/s
Content: This parameter defines the uplink middle rate threshold used when Uplink
Rate increase adjust level or Uplink Rate decrease adjust level is 3_Rates and
Uplink mid bite rate calculate method is HAND_APPOINT.
Recommended value: None .
365
DL Rate Reallocation Based on Traffic Volume

z
Principles of RATE_UP_AND_DOWN_ON_DCH
Rate downsizing is performed if the RNC receives a report of

event 4b about the downlink traffic volume.
Rate upsizing is performed if an event 4a about the downlink

traffic volume is triggered.
Page26
The lowest value that the rate can be downsized to is the value of Downlink bit rate
threshold for DCCC. The highest value that the rate can be upsized to is MBR.
366
DL Rate Reallocation Based on Traffic Volume

z
Principles of RATE_UP_ONLY_ON_DCH
Rate downsizing is prohibited. If a UE is in low activity, the

state of the UE is directly transitted to CELL_FACH if the UE
state transition algorithm is enabled.

Page27
The highest value that the rate can be upsized to is MBR.
367
DL Rate Increase
z
When Downlink Rate increase adjust level is 2_Rates,

the rate is upsized directly to the highest value from the
value of Downlink bit rate threshold for DCCC.
Page28
368
DL Rate Increase
z
When Downlink Rate increase adjust level is 3_Rates,

the rate is upsized to the Downlink mid bit rate threshold
if the current rate is the Downlink bit rate threshold for
DCCC, and then to the highest.
Page29
If the value of Uplink mid bit rate threshold is lower than that of Uplink bit rate threshold
for DCCC, the rate is directly upsized to the MBR, which is the same as the processing
applicable when Uplink Rate increase adjust level is 2_Rates.
369
DL Rate Decrease
z
When Downlink Rate decrease adjust level is 2_Rates,

the rate is downsized directly to the value of Downlink bit
rate threshold for DCCC from the MBR
Page30
370
DL Rate Decrease
z
When Downlink Rate decrease adjust level is 3_Rates,

the rate is downsized to the value of Downlink mid bit rate
threshold if the current rate is the MBR, and then to the
value of Downlink bit rate threshold for DCCC. If the
current rate is lower than MBR and higher than Uplink bit
rate threshold for DCCC, the rate is downsized to Uplink
bit rate threshold for DCCC when downsizing is triggered.
Page31
371
DL Parameters
z
DLRATEUPADJLEVEL
Parameter name: Downlink Rate increase adjust level
DLRATEDNADJLEVEL
Parameter name: Downlink Rate decrease adjust level
DLRATEUPADJLEVEL
Parameter name: Downlink Rate increase adjust level
Page32
Content: This parameter defines whether to use 2-rate or 3-rate adjustment in the
downlink when increasing the rate.
DLRATEDNADJLEVEL
Parameter name: Downlink Rate decrease adjust level
Content: This parameter defines whether to use 2-rate or 3-rate adjustment in the
downlink when decreasing the rate..
372
DL Parameters
z
DLDCCCRATETHD
Parameter name: Donwlink bit rate threshold for DCCC
Recommended value: D64, namely 64kbps
DLMIDRATECALC
Parameter name: Downlink mid bite rate calculate method
Recommended value: AUTO_CALC
DLDCCCRATETHD
Parameter name: Downlink bit rate threshold for DCCC
Value range: D8, D16, D32, D64, D128, D144, D256, D384
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384 .
Unit: kbit/s.
Page33
Content: The higher the parameter value is, the less the traffic volume based rate
reallocation algorithm gains. If the parameter value is too low, however, it may affect
the adverse data transfer.
DLMIDRATECALC
Parameter name: Downlink mid bite rate calculate method
Value range: AUTO_CALC, HAND_APPOINT
Physical value range: None .
Content: This parameter is used to decide the downlink middle bite rate calculation
method that applies when Downlink Rate increase adjust level or Downlink Rate
decrease adjust level is 3_Rates. If Downlink mid bite rate calculate method is set
to AUTO_CALC, the value of Downlink mid bit rate threshold is automatically
calculated by the system. The value of Downlink mid bit rate threshold is equal to
the RB rate closest to the highest rate divided by two.
Recommended value: AUTO_CALC.
373
DL Parameters
z
DLMIDRATETHD
Parameter name: Dwnlink mid bit rate threshold
Page34
ULMIDRATECALC
Unit: kbit/s
Content: This parameter defines the downlink middle rate threshold used when
Downlink Rate increase adjust level or Downlink Rate decrease adjust level is
3_Rates and Downlink mid bit rate calculate method is HAND_APPOINT.
Recommended value: None .
374
Contents
Page35
375
Signaling Procedure of UL Rate Reallocation

z
Signaling procedure of UL rate downsizing based on traffic

volume
Page36
376
Signaling Procedure of UL Rate Reallocation

z
Signaling procedure of UL rate upsizing based on traffic

volume
Page37
377
Signaling Procedure of DL Rate Reallocation

z
Signaling procedure of DL rate downsizing based on traffic

volume
Page38
378
Signaling Procedure of DL Rate Reallocation

z
Signaling procedure of DL rate upsizing based on traffic

volume
Page39
379
Contents
1. DCCC Overview
6. Always Online
Page40
380
Contents
3.1 Throughput Measurement and Event Reporting
3.2 Rate Reallocation Action Based on Throughput
Page41
381
Throughput Measurement
z
In each measurement period (E-DCH Throu Meas Period

for E-DCH service, DCH Throu Meas Period for DCH
service), the MAC-d takes statistics of the data volume
properly received by this RB. The result is then divided by
the measurement period to obtain the throughput value.
Page42
E-DCH and DCH BE services rate reallocation is based on the throughput measurement
results. After comparing the measurement results with associated thresholds, the RNC can
trigger rate reallocation.
382
Event
z
Event 4a
Throughput is above a threshold -> High active
Event 4b
Throughput is below a threshold -> Low active
Page43
For throughput-based rate reallocation on the E-DCH, both events 4a and 4b apply, that is,
both rate upsizing and downsizing are applicable for both uplink and downlink.
For throughput-based rate reallocation on the DCH, only event 4b applies, that is, only rate
downsizing is applicable.
383
Event Reporting
z
Mechanism of throughput measurement and reporting of

events 4a and 4b
Page44
During each measurement period (E-DCH Throu Meas Period, DCH Throu Meas Period),
throughput measurement on this RB is performed to obtain the throughput of this period,
defined as AvgThroughput.
If the AvgThroughput is higher than the 4a threshold for Ttrig_4a consecutive times
(Period Amount to trigger 4A on EDCH) and the Tpend_4a timer whose length is
defined through Period Amount after trigger 4A on EDCH is not started, event 4a is
reported and the Tpend_4a timer is started.
If the AvgThroughput is lower than the 4b threshold for Ttrig_4b consecutive times
(Period Amount to trigger 4B on EDCH or Period Amount to trigger 4B on DCH)
and the Tpend_4b timer whose length is defined through Period Amount after trigger
4B on EDCH or Period Amount after trigger 4B on DCH is not started, event 4b is
reported and the Tpend_4b timer is started.
384
Event Threshold
z
In the aspect of DCCC for HSUPA
The 4a threshold is the throughput threshold associated with

the current HSUPA adjustment rate, that is, TRt.
TRt = Rt * threshold rate ratiot
The 4b threshold is the throughput threshold associated with

the previous rate, that is, TRt1.
TRt1 = Rt1 * threshold rate ratiot1
Page45
If the current HSUPA adjustment rate is the minimum rate, the 4b rate threshold is the
threshold rate of E-DCH to FACH state transition (E-DCH to FACH 4b Threshold).
Where:
Rt is the current rate in the rate adjustment set
Rt-1 is the previous rate in the rate adjustment set.
Threshold rate ratiot and Threshold rate ratiot-1 are defined by the parameter percent
of ratio for nKbps (n = 8, 16, 32, 64, 128, 144, 256, 384).
385
Event Threshold
z
In the aspect of DCCC for DCH services,
The 4b threshold is calculated as follows:
TRt1 = Rt1 * threshold rate ratiot1
Page46
Where:
Rt-1 is the previous rate in the rate adjustment set.

Threshold rate ratiot-1 is defined by the parameter percent of ratio for nKbps (n = 8,
16, 32, 64, 128, 144, 256, 384).
386
Parameters
z
E2FTHROUMEASPERIOD
Parameter name: E-DCH Throu Meas Period
Recommended value: 30, namely 300s
EDCHTIMETOTRIGGER4A
Parameter name: Period Amount to trigger 4A on EDCH
Recommended value: 2
Page47
E2FTHROUMEASPERIOD
Parameter name: E-DCH Throu Meas Period
Physical value range: 10 ms to 100s.
Unit: ms
Content: This parameter defines how often the E-DCH throughput is measured.
Recommended value: 30.
Set this parameter through SET UESTATETRANS
EDCHTIMETOTRIGGER4A
Parameter name: Period Amount to trigger 4A on EDCH
Physical value range: 0 to 1023 .
Content: This parameter defines during how many consecutive time periods the
throughput exceeds the 4a threshold. After the throughput exceeds the threshold for
the time defined by this parameter, event 4a is reported.
387
Parameters
z
EDCHPENDINGTIME4A
Parameter name: Period Amount after trigger 4A on EDCH
EDCHTIMETOTRIGGER4B
Parameter name: Period Amount to trigger 4B on EDCH
EDCHPENDINGTIME4A
Parameter name: Period Amount after trigger 4A on EDCH
Physical value range: 0 to 1023
Page48
Content: This parameter defines the number of consecutive measurement periods for
not reporting event 4a after reporting of an event 4a.
EDCHTIMETOTRIGGER4B
Parameter name: Period Amount to trigger 4B on EDCH
throughput exceeds the 4b threshold. After the throughput exceeds the threshold for
the time defined by this parameter, event 4b is reported.
388
Parameters
z
EDCHPENDINGTIME4B
Parameter name: Period Amount after trigger 4B on EDCH
EDCHRATEADJUSTSET
Parameter name: HSUPA Uplink rate adjust set
EDCHPENDINGTIME4B
Parameter name: Period Amount after trigger 4B on EDCH
Page49
not reporting event 4b after reporting of an event 4b.
EDCHRATEADJUSTSET
Parameter name: HSUPA UpLink rate adjust set

Value range: Rate_8Kbps, Rate_16Kbps, Rate_32Kbps, Rate_64Kbps, Rate_128Kbps,
Rate_144Kbps, Rate_256Kbps, Rate_384Kbps, Rate_608Kbps, Rate_1450Kbps,
Rate_2048Kbps, Rate_2890Kbps, Rate_5760Kbps
Physical value range: 8 kbit/s, 16 kbit/s, 32 kbit/s, 64 kbit/s, 128 kbit/s, 144 kbit/s, 256
kbit/s, 384 kbit/s, 608 kbit/s, 1450 kbit/s, 2048 kbit/s, 2890 kbit/s, 5760 kbit/s .
Content: This parameter defines the rates contained in the HSUPA adjustment rate set.
Recommended value: None.
Set this parameter through SET EDCHRATEADJUSTSET
389
Parameters
z
RATIOFORRATE8,
RATIOFORRATE16,
RATIOFORRATE32,
RATIOFORRATE64,
RATIOFORRATE128,
RATIOFORRATE144,
RATIOFORRATE256,
RATIOFORRATE384,
RATIOFORRATE608,
RATIOFORRATE1450,
RATIOFORRATE2048,
RATIOFORRATE2890,
RATIOFORRATE5760
Parameter name: percent of ratio for nKbps
Recommended value: 90/90/90/90/80/80/80/75/75/75/75/70/70
Page50
RATIOFORRATE8, RATIOFORRATE16, RATIOFORRATE32, RATIOFORRATE64,

RATIOFORRATE5760
Parameter name: percent of ratio for 8Kbps, percent of ratio for 16Kbps, percent of
ratio for 32Kbps, percent of ratio for 64Kbps, percent of ratio for 128Kbps, percent of
ratio for 144Kbps, percent of ratio for 256Kbps, percent of ratio for 384Kbps, percent of
ratio for 608Kbps, percent of ratio for 1450Kbps, percent of ratio for 2048Kbps, percent
of ratio for 2890Kbps, percent of ratio for 5760Kbps
Step: 1%
Content: These parameters define the threshold bit rate ratios of all the bit rates
supported on the RAN side.
Recommended value: 90/90/90/90/80/80/80/75/75/75/75/70/70 .
Set this parameter through SET EDCHTHDRATERATIO
390
Parameters
z
DCHTHROUMEASPERIOD
Parameter name: DCH Throu Meas Period
Recommended value: 100, namely 1000ms
DCHTHROUTIMETOTRIGGER4B
Parameter name: Period Amount to trigger 4B on DCH
Page51
DCHTHROUMEASPERIOD
Parameter name: DCH Throu Meas Period
Physical value range: 0 to 100s
Unit: 10ms
Content: This parameter defines how often the DCH throughout is measured.
DCHTHROUTIMETOTRIGGER4B
Parameter name: Period Amount to trigger 4B on DCH
throughput exceeds the 4b threshold. After the throughput exceeds the threshold for
the time defined by this parameter, event 4b is reported. .
391
Parameters
z
DCHTHROUPENDINGTIME4B
Parameter name: Period Amount after trigger 4B on DCH
RATIOFORRATE8,
RATIOFORRATE16,
RATIOFORRATE32,
RATIOFORRATE64,
RATIOFORRATE128, RATIOFORRATE144,
RATIOFORRATE256, RATIOFORRATE384
Parameter name: percent of ratio for nKbps
DCHTHROUPENDINGTIME4B
Parameter name: Period Amount after trigger 4B on DCH
Page52
not reporting event 4b after reporting of an event 4b.

RATIOFORRATE128, RATIOFORRATE144, RATIOFORRATE256, RATIOFORRATE384
Parameter name: percent of ratio for 8Kbps, percent of ratio for 16Kbps, percent
of ratio for 32Kbps, percent of ratio for 64Kbps, percent of ratio for 128Kbps,
percent of ratio for 144Kbps, percent of ratio for 256Kbps, percent of ratio for
384Kbps
Step: 1%
Content: These parameters define the threshold bit rate ratios of all the bit rates
supported on the RAN side.
Set this parameter through SET DCHTHDRATERATIO
392
Contents
Page53
393
Rate Reallocation Strategy

z
Two strategies are available for EDCH in Huawei

implementation.
RATE_UP_AND_DOWN
RATE_UP_ONLY
For DCH, only rate downsizing is applicable.
Page54
394
Rate Reallocation on EDCH

z
The strategy is set through the HSUPA DCCC strategy

parameter.
HSUPADCCCSTG
Parameter name: HSUPA DCCC strategy
Recommended value: RATE_UP_AND_DOWN_ON_EDCH
Page55
The information about setting these parameters is as follows:
The RATE_UP_AND_DOWN_ON_EDCH strategy means that the rate can be both downsized
and upsized. If the system resources in the network are insufficient, the
RATE_UP_AND_DOWN_ON_EDCH strategy is recommended.
The RATE_UP_ONLY_ON_EDCH strategy means that the rate can only be upsized. When
the network resources are sufficient, the RATE_UP_ONLY_ON_EDCH strategy is
recommended.
HSUPADCCCSTG
Parameter name: HSUPA DCCC strategy
Value range: RATE_UP_AND_DOWN_ON_EDCH, RATE_UP_ONLY_ON_EDCH
Physical value range: 0, 1
Unit: 10ms
Content: This parameter defines whether to use the

RATE_UP_AND_DOWN_ON_EDCH or RATE_UP_ONLY_ON_EDCH strategy.
Recommended value: RATE_UP_AND_DOWN_ON_EDCH .
395

z
Principles of RATE_UP_AND_DOWN_ON_EDCH
After event 4a is reported, the bit rate is adjusted by one level

upwards. If the current rate is the maximum bit rate, no action is
required.
After event 4b is reported, the reported throughput is compared with

the threshold rate that is associated with the HSUPA adjustment rate.
The RB is reconfigured to the HSUPA adjustment bit rate, which is
associated with the minimum threshold rate of throughput that is
higher than the reported throughput.
Page56
396

z
Principles of RATE_UP_ONLY_ON_EDCH
After event 4a is reported, the rate is adjusted by one level

upwards. If the current rate is the maximum rate, no action is
required.
After event 4b is reported, no rate downsizing is done.

However state transition can be done according to rules
specified in 5. UE State Transition Algorithm.
Page57
397
Rate Downsizing on DCH

z
After event 4b is reported, the reported throughput is

compared with the threshold rate that is associated with the
rate adjustment set. The RB is reconfigured to the rate in
the rate adjustment set, which is associated with the
minimum threshold rate of throughput that is greater than
the reported throughput.
The above procedure is for both uplink and downlink.
Page58
398
Contents
Page59
399
Signaling Procedure of Rate Reallocation

z
Signaling procedure of rate upsizing based on throughput
Page60
400
Signaling Procedure of Rate Reallocation

z
Signaling procedure of rate downsizing based on throughput
Page61
The DCH rate reallocation based on throughput is implemented through the signaling over the
Uu and Iub interfaces. Only downsizing is applicable to the DCH rate reallocation based on
throughput.
401
Contents
1. DCCC Overview
6. Always Online
Page62
402
Contents
4.1 Uplink Quality Measurement and Event Reporting
4.2 Downlink Quality Measurement and Event Reporting
4.3 Rate Reallocation Action Based on Uplink Quality
4.4 Rate Reallocation Action Based on Downlink Quality
Page63
Uplink Quality Measurement and Event Reporting describes the uplink quality evaluation
factors and corresponding events.
403
Uplink Quality Measurement

z
There are two measurement quantities related to the uplink

quality:
Uplink transmit power
Uplink BLER
Page64
The measurement of uplink transmit power through UU interface from UE. When the uplink
transmit power reaches the maximum power, it indicates that the radio link may be unstable.
The measurement of uplink BLER can be implemented in RNC. When uplink BLER is high, it
also indicates that the radio link may be unstable.
404
Event 6A and 6B
z
In the uplink, the measurement of UE transmit power can

trigger event 6A or event 6B.
6A (6A1/6A2): The UE TX power is larger than the UE Tx

power threshold for a period of time
6B (6B1/6B2): The UE TX power is lower than the UE Tx

power threshold for a period of time
Page65
405
Parameters
ULTHD6A1
Parameter name : UL 6A1 event relative threshold
Recommended value : 2dB
ULBETRIGTIME6A1
Parameter name : BE Trigger Time 6A1
Recommended value : D640
ULTHD6A1
Value range: 0~82 .
Physical value range: 0 to 82; Step: 1 (dB).
Page66
Content: This parameter defines the measurement reporting threshold at which

the event 6A1 is triggered.
Recommended value : 2
Set this parameter through ADD TYPRABQUALITYMEAS
ULBETRIGTIME6A1
Parameter name : BE trigger time 6A1

D320, D640, D1280, D2560, D5000 .
Physical value range: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640,
1280, 2560, 5000; Unit: ms .
Content: This parameter defines the duration during which the UE transmitted
power always meets the 6A1 measurement condition before the event 6A1 is
triggered. The trigger time is used to avoid any sudden change of the
measured value in measurement reporting.
Set this parameter through SET QUALITYMEAS, ADD CELLQUALITYMEAS
406
Parameters
ULTHD6B1
Parameter name : UL 6B1 event relative threshold
ULBETRIGTIME6B1
Parameter name : BE Trigger Time 6B1
ULTHD6B1
Value range: 0~82 .
Page67

the event 6B1 is triggered.
ULBETRIGTIME6B1
Parameter name : BE trigger time 6B1

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000; Unit: ms .
power always meets the 6B1 measurement condition before the event 6B1 is
407
Parameters
ULTHD6A2
ULBETRIGTIME6A2
Parameter name : BE Trigger Time 6A2
ULTHD6A2
Value range: 1~83 .
Page68

the event 6A2 is triggered.
ULBETRIGTIME6A2
Parameter name : BE trigger time 6A2

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000; Unit: ms .
power always meets the 6A2 measurement condition before the event 6A2 is
408
Parameters
ULTHD6B2
ULBETRIGTIME6B2
Parameter name : BE Trigger Time 6B2
ULTHD6B2
Value range: 0~82 .
Page69

the event 6B2 is triggered.
ULBETRIGTIME6B2
Parameter name : BE trigger time 6B2

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000; Unit: ms .
power always meets the 6B2 measurement condition before the event 6B2 is
409
Event 6D
z
If the transmit power of the UE is equal to the maximum

transmit power of the UE for a period of time (the time is
defined by the hysteresis), the UE reports event 6D.
6D: The UE TX power is equal to the maximum allowed UE TX

power for a period of time
Page70
For BE services, the hysteresis is defined by the Be trigger time 6D parameter.
410
Parameters
ULBETRIGTIME6D
Parameter name : BE Trigger Time 6D
Recommended value : D240, namely 240ms
Page71
ULBETRIGTIME6D
Parameter name : BE trigger time 6D

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000; Unit: ms .
Content: This parameter defines the duration during which the measured UE
transmitted power always meets the 6D measurement condition before the
event 6D is triggered. The trigger time is used to avoid any sudden change of
the measured value in measurement reporting.
411
Event 5A
z
The uplink BLER reflects the uplink quality. The change in

the BLER is indicated by event 5A.
5A: The number of error blocks during the sliding window is

greater than or equal to a predefined number
Page72
For a specific service parameter index, set the following parameters related to event 5A:
Statistic Block Number for 5A Event: the length of the sliding window in which the
number of error blocks is counted
Event 5A Threshold: the number of error blocks in a sliding window, which
determines whether to trigger an event 5A or not
Interval Block Number: After an event 5A is triggered, no more event 5A is triggered
before a number of blocks (the number is defined by this parameter) are received.
412
Event 5A
z
Event 5A Mechanism
Page73
Each time a block is received, the number of error blocks within the sliding window is
compared with the Event 5A Threshold parameter. If the number of error blocks is equal to or
greater than the value of the parameter, an event 5A is triggered. When event 5A is triggered,
a pending counter is started to prevent further triggering of the event before a certain number
of transport blocks which is specified by Interval Block Number are received.
The whole process is based on the sliding window mechanism. This window slides with the
arrival of each block. Each time a block is received, the decision on whether to trigger event 5A
is made. The number of error blocks is still counted when the pending timer after trigger timer
works. However, no event 5A is triggered even if the triggering conditions are met.
413
Parameters
STABLKNUM5A
Parameter name : Statistic Block Number for 5A Event
THD5A
Parameter name : Event 5A Threshold
STABLKNUM5A
Parameter name : Statistic Block Number for 5A Event
Value range: 1 to 512 .
Physical value range: 1 to 512.
Page74
Content: This parameter defines the length of the sliding window in which the
number of error blocks is counted.
THD5A
Parameter name : Event 5A Threshold
Content: This parameter defines the threshold of the number of error blocks
within a sliding window. If the number of error blocks is equal to or greater than
the parameter value, an event 5A is triggered.
414
Parameters
HANGBLOCKNUM5A
Parameter name : Interval Block Number Value
Page75
HANGBLOCKNUM5A
Parameter name : Interval Block Number Value
Physical value range: 1 to 512.
Content: This parameter defines the length of the pending timer after trigger
timer, which is started after an event 5A is triggered. .
Recommended value : 512.
415
Contents
Page76
416
Downlink Quality Measurement

z
There are two measurement quantities related to the

downlink quality,
Transmitted Code Power (TCP)
RLC PDU retransmission rate.
Page77
The measurement of TCP is implemented on the NodeB side. When the transmit power of the
DPDCH is higher than the threshold of event Ea, it indicates that the radio link may be unstable.
The RLC PDU retransmission rate is optional. It is controlled by the Srnc Downlink RLC QOS
Action Trigger Indicator of Traffic BE parameter.
417
Event E
z
Event E has two measurement thresholds, that is, threshold

1, and threshold 2.
Event Ea means that the transmit power rises higher than

measurement threshold 1, and NodeB send TCP meas. report
Event Eb means that the transmit power falls below

measurement threshold 2, and NodeB stop sending TCP meas.
Report
Threshold 1 and 2 are calculated by the following formula:
Absolute threshold = max mum DL power relative threshold + PO3

Page78
Where:
PO3 is the relative transmit power offset between pilot fields of the DPCCH and
DPDCHs.
The relative threshold is configured through the parameter Event Ea relative
threshold, and Event Eb relative threshold
Maximum DL power is defined through the RL Max DL TX power parameter that is
specific for the DPDCHs.
418
Event E
z
Event E reporting mechanism
Page79
When the transmit power of the pilot fields of the DPCCH remains above the measurement
threshold 1 for a time period longer than T1 (the trigger time of event E which is set to 640 ms
for BE service), event Ea is triggered. The NodeB periodically reports the measurement results
of the transmit power to the RNC.
When the transmit power of the pilot fields of the DPCCH remains below the measurement
threshold 2 for a time period longer than T1 (the trigger time of event E which is set to 640 ms
for BE service), event Eb is triggered. The NodeB stops reporting the measurement results of
the transmit power.
419
Parameters
EVENTEATHD
Parameter name : Event Ea relative threshold
Recommended value : 2, namely 1dB
EVENTEBTHD
EVENTEATHD
Physical value range: 0 to 55.5, Step: 0.5
Unit: dB
Page80
Content: Together with the maximum transmit power, this parameter defines
the event Ea threshold of the DL DPCCH power.
EVENTEBTHD
Parameter name : Event Eb relative threshold
Physical value range: 0 to 55.5, Step: 0.5
Unit: dB
Content: Together with the maximum transmit power, this parameter defines
the event Eb threshold of the DL DPCCH power. It is recommended that the
value of Event Eb relative threshold be the same as that of Event Ea
relative threshold. .
420
Parameters
DLBETRIGTIMEE
Parameter name : Be trigger time of Event E
Recommended value : 64, namely 640ms
CHOICERPTUNITFORBEE
Parameter name : Be Reporting period unit for event E
Recommended value : TEN_MSEC
DLBETRIGTIMEE
Parameter name : Be trigger time of Event E
Physical value range: 10 to 60000 , Step: 10
Unit: ms
Page81
Content: This parameter defines the time allowance when the measured power
is higher than the threshold, so as to avoid the misreporting due to sudden
fluctuation.
CHOICERPTUNITFORBEE
Parameter name : Be Reporting period unit for event E
Value range: TEN_MSEC, MIN .
Physical value range: None
Unit: dB
Content: The DL transmitted code power (if any) is reported periodically after
the event Ea is reported. The reporting period unit can be min or 10 ms.
421
Parameters
TENMSECFORBEE
Parameter name : Be Event E reporting period in 10ms
MINFORBEE
Parameter name : Be Event E reporting period in min
Recommended value : None
TENMSECFORBEE
Parameter name : Be Event E reporting period in 10ms
Physical value range: 10 to 60000 , Step: 10
Unit: ms
Page82
Content: This parameter is valid when the Reporting period unit for event E
parameter is set to TEN_MSEC. The DL transmitted code power (if any) is
reported periodically after the event Ea is reported.
MINFORBEE
Parameter name : Be Event E reporting period in min
Unit: ms
Content: This parameter is valid when the Reporting period unit for event E
parameter is set to MIN. The DL transmitted code power (if any) is reported
periodically after the event E is reported. This parameter specifies the reporting
period.
422
Parameters
RLMAXDLPWR
Parameter name : RL Max DL TX power
Page83
RLMAXDLPWR
Parameter name : RL Max DL TX power
Value range: -350 to 150
Physical value range: -35 to 15, Step: 0.1
Unit: dB
Content: This parameter defines the maximum downlink transmit power of

radio link. This parameter has to meet the coverage requirement of the
network planning, and the value is relative to the PCPICH transmit power
parameter that is set through the MOD CELL command.
Set this parameter through ADD CELLRLPWR
423
Event A
z
Event A: RLC retransmission value is above threshold for a

period
RLC retransmission rate :
Page84
The RLC PDU retransmission rate is calculated according to the ACK and NACK feedback
information. The RLC PDU retransmission rate is optional. It is controlled by the Srnc
Downlink RLC QOS Action Trigger Indicator of Traffic BE parameter (through the SET
QOSACT command).
Each time a retransmission event A is triggered, RLC retransmission rate calculation needs to
be suspended for a period of time (that is, re-TX monitor period x Event A pending time
after trigger), during which RLC retransmission rate is not calculated. When RLC
retransmission rate event report A is received, the downlink bandwidth can be downsized if an
event Ea has already been reported.
424
Parameters
EVENTATHRED
Parameter name : Event A threshold
Recommended value : 160, namely 16%
TIMETOTRIGGERA
Parameter name : Event A time to trigger
EVENTATHRED
Parameter name : Event A threshold
Physical value range: 0% to 100%, Step: 0.1%
Page85
Content: This parameter defines the threshold of event A, which indicates that
a high ratio of PDUs are retransmitted.
Set this parameter through ADD TYPRABRLC
TIMETOTRIGGERA
Parameter name : Event A time to trigger
Content: This parameter defines the time period of reporting event A before
event A is triggered.
425
Parameters
PENDINGTIMEA
Parameter name : Event A pending time after trigger
MONITERPRD
Parameter name : re-TX monitor period
PENDINGTIMEA
Parameter name : Event A pending time after trigger
Page86
Content: This parameter defines the number of time periods which are the
pending time after event A is triggered.
MONITERPRD
Parameter name : re-TX monitor period
Unit: ms
Content: This parameter defines the period of monitoring PDU retransmission.
426
Event F
z
Event F is used to check whether the current transmit power

allows rate upsizing.
Event F has two measurement thresholds, threshold 1, and

threshold 2.
Event Fa means that the transmit power falls below threshold 1.
Event Fb means that the transmit power rises above threshold 2.
The threshold is calculated according to the following formula:
where:
Page87
P is the power difference between current rate and target rate which is calculated in
RNC through the parameters acquired by the simulation and field test results.
Pmargin is the event F reporting power margin (Event F reporting power margin).
Event Ea relative threshold is used to protect triggering event report Ea after
upsizing.
Pmax is the maximum DL power of target rate, that is, the maximum configured power
of the target rate.
PO3 is the relative transmit power offset between pilot fields of the DPCCH and
DPDCHs.
Though these parameters can be changed by using the MML commands on the LMT, it is
strongly recommended that no change be made to them.
427
Event F
z
Event F reporting mechanism
Page88
When the transmit power of the pilot fields of the DPCCH remains below the measurement
threshold 1 for a time period longer than T1 (the trigger time of event F which is set to 640 ms
for BE service), event Fa is triggered. Then the NodeB periodically reports the measurement
results of the transmit power to the RNC.
When the transmit power of the pilot fields of the DPCCH remains above the measurement
threshold 2 for a time period longer than T1 (the trigger time of event F which is set to 640 ms
for BE service), event Fb is triggered. The NodeB then stops reporting the measurement
results of the transmit power.
428
Parameters
PWRMARGIN
Parameter name : Event F reporting power margin
DLBETRIGTIMEF
Parameter name : Be trigger time of Event F
PWRMARGIN
Parameter name : Event F reporting power margin
Physical value range: 0 to 10, Step: 0.1
Unit: dB
Page89
Content: This parameter defines the power margin applied when event F is
reported.
Set this parameter through SET DCCC, ADD CELLDCCC
DLBETRIGTIMEF
Parameter name : Be trigger time of Event F
Unit: ms
Content: This parameter defines the time allowance when the measured power
is lower than the threshold, so as to avoid the misreporting due to sudden
fluctuation.
Set this parameter through SET QUALITYMEAS , ADD CELLQUALITYMEAS
429
Parameters
CHOICERPTUNITFORBEF
Parameter name : Be Reporting period unit for event F
TENMSECFORBEF
Parameter name : Be Event F reporting period in 10ms
CHOICERPTUNITFORBEF
Parameter name : Be Reporting period unit for event F
Value range: TEN_MSEC, MIN .
Page90
Content: The DL transmitted code power (if any) is reported periodically after
the event Fa is reported. The reporting period unit can be min or 10 ms.
TENMSECFORBEF
Parameter name : Be Event F reporting period in 10ms
Unit: ms
Content: This parameter is valid when the Be Reporting period unit for
event F parameter is set to TEN_MSEC. The DL transmitted code power (if
any) is reported periodically after the event Fa is reported.
430
Parameters
MINFORBEF
Parameter name : Be Event F reporting period in min
Page91
MINFORBEF
Parameter name : Be Event F reporting period in min
Unit: min
Content: This parameter is valid when the Be Reporting period unit for
event F parameter is set to MIN. The DL transmitted code power (if any) is
reported periodically after the event F is reported.
431
Contents
Page92
432
Rate Downsizing
z
For rate downsizing based on uplink quality, only the 3-rate

downsizing applies.
If the current rate is MBR, the rate is downsized to the value of

Uplink mid bit rate threshold.
If the current rate is higher than Uplink full coverage bit rate
and lower than MBR, the rate is downsized to the value of
Uplink full coverage bit rate.
Page93
The Uplink mid bit rate threshold parameter is the same as that described in Rate
Reallocation Based on Traffic Volume.
The Uplink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic
volume in the uplink. When Uplink Rate decrease adjust level is 2_Rates, the middle bit rate
for the rate reallocation based on uplink quality is equal to the RB rate closest to the highest
rate divided by two. The bit rate is calculated in the RNC.
433
Rate Downsizing
z
Rate downsizing based on uplink quality in the case of 3rate adjustment
Page94
434
Parameters
ULFULLCVRRATE
Parameter name : Uplink full coverage bit rate
Recommended value : D64, namely 64kbit/s
Page95
ULFULLCVRRATE
Parameter name : Uplink full coverage bit rate
Value range: D8, D16, D32, D64, D128, D144, D256, D384 .
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Content: This parameter defines the highest uplink rate that can reach its QoS
requirement throughout the whole cell.
Set this parameter through SET DCCC, ADD CELLDCCC.
435
Rate Upsizing
z
Rate upsizing process based on uplink quality
Page96
436
Rate Upsizing
z
If the RNC receives an event 6B2 but no event 6A2, rate

upsizing based on traffic-volume-related event 4a is allowed.
If the RNC receives an event 6A2, rate upsizing based on

traffic-volume-related event 4a is not allowed. If the RNC
receives an event 6B1, rate downsizing is stopped and rate
upsizing is still prohibited.
Page97
437
Contents
Page98
438
Rate Downsizing
z
For rate downsizing based on downlink quality, only the 3rate downsizing applies.
If the current rate is MBR, the rate is downsized to the value of

Downlink mid bit rate threshold.
If the current rate is higher than Downlink full coverage bit

rate and lower than MBR, the rate is downsized to the value of
Downlink full coverage bit rate.
Page99
The Downlink mid bit rate threshold parameter is the same as that described in Rate
Reallocation Based on Traffic Volume.
The Downlink mid bit rate threshold is the middle bit rate threshold for adjustment of the
traffic volume in the downlink. When Downlink Rate adjust level is 2_Rates, the middle bit
rate for the rate reallocation based on downlink quality is equal to the RB rate closest to the
highest rate divided by two. The bit rate is calculated in the RNC.
439
Rate Downsizing
z
Rate downsizing based on downlink quality in the case of 3rate adjustment
Page100
440
Parameters
DLFULLCVRRATE
Parameter name : Downlink full coverage bit rate
Recommended value : D64, namely 64kbit/s
Page101
DLFULLCVRRATE
Parameter name : Downlink full coverage bit rate
Value range: D8, D16, D32, D64, D128, D144, D256, D384 .
Physical value range: 8, 16, 32, 64, 128, 144, 256, 384
Unit: kbit/s
Content: This parameter defines the highest downlink rate that can reach its
QoS requirement throughout the whole cell.
Set this parameter through SET DCCC, ADD CELLDCCC.
441
Rate Upsizing
z
Rate upsizing process based on downlink quality
Page102
The rate upsizing process requires checking whether the current DL channel power is ample.
Rate upsizing is allowed only when the DL channel power is ample. The above figure shows
the process of rate upsizing based on downlink quality.
442
Rate Upsizing
z
If event Fa is reported, it indicates that the DL channel

power is ample. Rate upsizing is then performed if event 4a
is reported.
If event Fb is reported, it indicates that the DL channel

power is not ample. Then rate upsizing is prohibited.
Page103
443
Contents
Page104
444
Signaling Procedure of Rate Downsizing

z
Signaling procedure of rate downsizing based on downlink

quality
Page105
For detailed information about the signaling procedure of rate upsizing, see Signaling
Procedure of Rate Reallocation Based on Traffic Volume.
445
Contents
1. DCCC Overview
6. Always Online
Page106
446
UE State Transition
z
UE state transition and status of the RRC connection
Page107
The above figure shows the RRC states in UTRA RRC connected mode, including transitions
between UTRA RRC connected mode and GSM connected mode for CS domain services and
transitions between UTRA RRC connected mode and GSM/GPRS packet modes for PS
domain services. It also shows the transitions between idle mode and UTRA RRC connected
mode, and the transitions within UTRA RRC connected mode. Only the state transitions within
the UTRAN connected mode is described herein.
The principles of UE state transition are as follows:
The state of the UE transits from CELL_DCH to CELL_FACH or from CELL_FACH to

CELL_PCH/URA_PCH if the activity of UE decreases.
The state of the UE transits from CELL_PCH/URA_PCH to CELL_FACH or from
CELL_FACH to CELL_DCH if the activity of UE increases.
447
Contents
5.1 UE State Transition From CELL_DCH to CELL_FACH
5.2 UE State Transition From CELL_FACH to CELL_PCH
5.3 UE State Transition From CELL_PCH to URA_PCH
5.4 UE State Transition From CELL_PCH or URA_PCH to CELL_FACH
5.5 UE State Transition From CELL_FACH to CELL_DCH
Page108
448
From CELL_DCH to CELL_FACH

z
UE state transition from CELL_DCH to CELL_FACH
Page109
When the RNC receives the 4b event report, the CELL_DCH to CELL_FACH transition timer
and the uplink and downlink 4b counters are started on the RNC side. If both uplink and
downlink 4b counters of traffic volume event 4b report are greater than or equal to a
CELL_DCH to CELL_FACH transition threshold before the timer expires, the UE state transits
from CELL_DCH to CELL_FACH when the timer expires.
449

z
The CELL_DCH to CELL_FACH transition threshold is the

rounded-down value of the following formula:
CELL_DCH to CELL_FACH transition threshold = [CELL_DCH

to CELL_FACH transition time / (time to trigger + pending time
after trigger) * state transition traffic redundancy coefficient]
where:
Page110
CELL_DCH to CELL_FACH transition time, time to trigger, and pending time after
trigger are set through the parameters listed in the following table.
State transition traffic redundancy coefficient is used to avoid detecting UE in lowactivity state incorrectly due to the loss of measurement reports. The value of this
coefficient is set to 80%.
Parameters used for UE state transition from CELL_DCH to CELL_FACH
450

z
UE state transition is not applicable in the following cases:
For BE services on the DCH:
If PS_BE_STATE_TRANS_SWITCH is set to OFF, or other

services which cannot perform state transition are configured for
the UE, no state transition is performed on the UE.
Page111
Instead, if both uplink and downlink 4b counters of traffic volume event 4b report are greater
than or equal to a CELL_DCH to CELL_FACH transition threshold when the CELL_DCH to
CELL_FACH transition timer expires, the UE is reconfigured to the low-activity rate that is
defined through the Low activity bit rate threshold parameter.
However, if the value of Low activity bit rate threshold is greater than or equal to that of
Uplink/Downlink bit rate threshold for DCCC, the reconfiguration to Low activity bit rate
threshold is prohibited.
451

z
For BE services on the HS-DSCH or E-DCH,
If PS_BE_STATE_TRANS_SWITCH or
HSDPA_STATE_TRANS_SWITCH/HSUPA_STATE_TRANS_S
WITCH is set to OFF, or other services which cannot perform state
transition are configured for the UE, the UE does not undergo
state transition.
Page112
452

z
For real-time PS services,
If PS_NON_BE_STATE_TRANS_SWITCH is set to OFF, or other

services which cannot perform state transition are configured for
the UE, the UE does not undergo state transition.
Page113
453
Parameters
PS_BE_STATE_TRANS_SWITCH
Parameter name : PS_BE_STATE_TRANS_SWITCH
Recommended value : 0, namely OFF
PS_NON_BE_STATE_TRANS_SWITCH
Parameter name : PS_NON_BE_STATE_TRANS_SWITCH
PS_BE_STATE_TRANS_SWITCH
Parameter name : PS_BE_STATE_TRANS_SWITCH
Value range: Enum (0,1) .
Physical value range: Enum (0,1)
Page114
Content: If this parameter is set to 1, UE RRC state transitions

(CELL_FACH/CELL_PCH/URA_PCH) for services are allowed in the RNC. .
PS_NON_BE_STATE_TRANS_SWITCH
Parameter name : PS_NON_BE_STATE_TRANS_SWITCH
Content: If this parameter is set to 1, UE RRC state transitions to CELL_FACH

for real-time services are allowed in the RNC.
454
Parameters
HSDPA_STATE_TRANS_SWITCH
Parameter name : HSDPA_STATE_TRANS_SWITCH
HSUPA_STATE_TRANS_SWITCH
Parameter name : HSUPA_STATE_TRANS_SWITCH
HSDPA_STATE_TRANS_SWITCH
Parameter name : HSDPA_STATE_TRANS_SWITCH
Page115
Content: When it is checked, UE RRC state transitions to CELL_FACH for the

DCCC algorithm of HSDPA services are allowed in the RNC. When the RAB
on HS-DSCH is BE service, the PS_BE_STATE_TRANS_SWITCH is checked
simultaneously, and when the RAB on HS-DSCH is PS real-time traffic, the
PS_NON_BE_STATE_TRANS_SWITCH is checked simultaneously.
HSUPA_STATE_TRANS_SWITCH
Parameter name : HSUPA_STATE_TRANS_SWITCH
Content: When it is checked, UE RRC state transitions to CELL_FACH for the

DCCC algorithm of HSUPA services are allowed in the RNC. When the RAB
on E-DCH is BE service, the PS_BE_STATE_TRANS_SWITCH is checked
simultaneously, and when the RAB on E-DCH is PS real-time traffic, the
PS_NON_BE_STATE_TRANS_SWITCH is checked simultaneously.
455
Parameters (BE DCH)

z
DTOFSTATETRANSTIMER
Parameter name : BE DCH to FACH transition timer
Recommended value : 5, namely 5s
D2F2PTVMTHD
Parameter name : BE DCH to F/RACH or F/RACH to PCH 4b

threshold
Recommended value : D64 , namely 64byte
Page116
DTOFSTATETRANSTIMER
Parameter name : BE DCH to FACH transition timer
Unit: s
Content: This parameter is used to detect the stability of a UE in low activity in

CELL_DCH state. Configuration of the parameter is based on the BE service
model on DCH.

D2F2PTVMTHD
Parameter name : BE DCH to F/RACH or F/RACH to PCH 4b threshold
Value range: D8, D16, D32, D64, D128, D256, D512, D1024, D2k, D3k, D4k,
D384k, D512k, D768k .
Physical value range: 8, 16, 32, 64, 128, 256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k,
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
Content: This threshold is used to check whether a UE is in low-activity state. If

the UE is in CELL_DCH state, the BE DCH to FACH transition timer
increases every time the UE reports event 4b. If the UE is in CELL_FACH
state, the BE DCH to FACH transition timer increases every time the UE
reports event 4b when the traffic volume is 0.
456
Parameters (BE DCH)

D2FTVMTIMETOTRIG
Parameter name : BE DCH to F/RACH 4b time to trigger
D2FTVMPTAT
Parameter name : BE DCH to F/RACH 4b Pending Time after

trigger
D2FTVMTIMETOTRIG
Page117
Parameter name : BE DCH to F/RACH 4b time to trigger

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000
Unit: ms
Content: When the traffic volume is lower than BE DCH to F/RACH or
F/RACH to PCH 4b threshold for a period of time defined by this parameter,
the UE reports event 4b. This parameter is used to avoid triggering
unnecessary events caused by unstable traffic volumes.
D2FTVMPTAT
Parameter name : BE DCH to F/RACH 4b Pending Time after trigger
Value range: D250, D500, D1000, D2000, D4000, D8000, D16000 .
Physical value range: 250, 500, 1000, 2000, 4000, 8000, 16000
Unit: ms
Content: This parameter defines the time interval of reporting event 4b. This
parameter is used to avoid too frequent event 4b reports.
457
Parameters (BE HS-DSCH)

BEH2FSTATETRANSTIMER
Parameter name : BE HS-DSCH to FACH transition timer
Recommended value : 180 , namely 180s
BEH2FTVMTHD
Parameter name : BE HS-DSCH to FACH 4b threshold
BEH2FSTATETRANSTIMER
Parameter name : BE HS-DSCH to FACH transition timer
Unit: s
Page118
Content: This parameter is used to detect the stability of a UE in low activity in

CELL_DCH (with HS-DSCH) state. Configuration of the parameter is based on
the BE service model on HS-DSCH.
BEH2FTVMTHD
Parameter name : BE HS-DSCH to FACH 4b threshold

D384k, D512k, D768k .
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
Content: This threshold is used to check whether a UE is in low-activity state. If
the traffic volume is lower than this threshold for a certain period, event 4b is
reported when the UE in CELL_DCH (with HS-DSCH) state.
458
Parameters (BE HS-DSCH)

BEH2FTVMTIMETOTRIG
Parameter name : BE HS-DSCH to FACH 4b time to trigger
BEH2FTVMPTAT
Parameter name : BE HS-DSCH to FACH 4b Pending Time

after trigger
BEH2FTVMTIMETOTRIG
Page119
Parameter name : BE HS-DSCH to FACH 4b time to trigger

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000
Unit: ms
Content: When the traffic volume is lower than the lower threshold for a period
of time defined by this parameter, the UE reports event 4b. This parameter is
used to avoid triggering unnecessary events caused by unstable traffic
volumes.
BEH2FTVMPTAT
Parameter name : BE HS-DSCH to FACH 4b Pending Time after trigger
Unit: ms
459
Parameters (Realtime Traff DCH)

RTDH2FSTATETRANSTIMER
Parameter name : Realtime Traff DCH or HSPA to FACH

transition timer
RTDH2FTVMTHD
Parameter name : Realtime Traff DCH or HSPA to FACH 4b

threshold
RTDH2FSTATETRANSTIMER
Parameter name : Realtime Traff DCH or HSPA to FACH transition timer
Unit: s
Page120
Content: This timer is used to check whether a real-time service UE in

CELL_DCH state is in stable low-activity state. Configuration of the parameter
is based on the RT service model.
RTDH2FTVMTHD
Parameter name : Realtime Traff DCH or HSPA to FACH 4b threshold

D384k, D512k, D768k .
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
Content: This threshold is used to check whether a UE is in low-activity state.
The CELL_DCH to CELL_FACH transition timer increases 1 every time the UE
in CELL_DCH state reports event 4b.
460

RTDH2FTVMTIMETOTRIG
Parameter name: Realtime Traff DCH or HSPA to FACH 4b

time to trigger
RTDH2FTVMPTAT
Parameter name: Realtime Traff DCH or HSPA to FACH 4b

pending time
RTDH2FTVMTIMETOTRIG
Page121
Parameter name : Realtime Traff DCH or HSPA to FACH 4b time to trigger

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000
Unit: ms
volumes.
RTDH2FTVMPTAT
Parameter name : Realtime Traff DCH or HSPA to FACH 4b pending time
Unit: ms
461
Parameters (E-DCH)
E2FTHROUMEASPERIOD
Parameter name : E-DCH Throu Meas Period
E2FSTATETRANSTIMER
Parameter name : E-DCH to FACH State Transformation Timer
E2FTHROUMEASPERIOD
Parameter name : E-DCH Throu Meas Period
Physical value range: 10 ms to 100s
Unit: 10ms
Page122
Content: This parameter defines the period of throughput measurement. An

extremely low value of this parameter leads to great fluctuation of the obtained
throughput, which results in unexpected reporting of events 4a and 4b.
E2FSTATETRANSTIMER
Parameter name : E-DCH to FACH State Transformation Timer
Unit: s
Content: This timer is used to check whether a UE in CELL_DCH state with EDCH bearer is in stable low-activity state.
462
Parameters (E-DCH)
E2FTHROUTHD
Parameter name : E-DCH to FACH 4b Threshold
Recommended value : 8, namely 8byte
E2FTHROUTIMETOTRIG
Parameter name: E-DCH to FACH 4b Period Amount To

Trigger
E2FTHROUTHD
Parameter name : E-DCH to FACH 4b Threshold
Unit: kbit/s
Page123
Content: This parameter determines whether the UE is in low-activity state. For

the UE on the E-DCH, the counter for checking low activity increases by 1
each time the 4b throughput event is reported.
E2FTHROUTIMETOTRIG
Parameter name : E-DCH to FACH 4b Period Amount To Trigger
Content: If the throughput is lower than E-DCH to FACH 4b Threshold for the
times defined by this parameter, the UE reports event 4b. This parameter is
used to avoid unnecessary triggering of throughput events caused by unstable
throughput.
463

E2FTHROUPTAT
Parameter name: E-DCH to FACH 4b Pending Period Amount

After Trigger
LITTLERATETHD
Parameter name: Low activity bit rate threshold
Recommended value: 64, namely 64kbit/s
E2FTHROUPTAT
Parameter name : E-DCH to FACH 4b Pending Period Amount After Trigger
Page124
Content: This parameter defines the time interval for a second event 4b report
after the first event 4b report. This parameter is used to avoid frequent event
4b reports.
LITTLERATETHD
Parameter name : Low activity bit rate threshold
Value range: D0, D8, D16, D32, D64, D128, D144, D256, D384 .
Physical value range: 0, 8, 16, 32 ,64, 128, 144, 256, 384
Unit: kbit/s
Content: When a UE fails to transit from CELL_DCH to CELL_FACH state

because the switch of state transition algorithm is off or multiple services are
configured for the UE, the UE is reconfigured to the value of Low activity bit
rate threshold, which is configured on the LMT.
464
Contents
Page125
465
From CELL_FACH to CELL_PCH

z
This UE state transition occurs when only the BE service of

the PS domain exists.
The procedure of UE state transition from CELL_FACH to

CELL_PCH is similar to that of UE state transition from
CELL_DCH to CELL_FACH.
Page126
When the RNC receives the 4b report in which the traffic volume is zero, the CELL_FACH to
CELL_PCH transition timer and the uplink and downlink 4b counters are started on the RNC
side. If both uplink and downlink 4b counters of traffic volume event 4b report are greater than
or equal to a CELL_FACH to CELL_PCH transition threshold before the timer expires, the UE
state transits from CELL_FACH to CELL_PCH when the timer expires.
466
From CELL_FACH to CELL_PCH

z
The CELL_FACH to CELL_PCH transition threshold is the

rounded-down value of the following formula:
CELL_FACH to CELL_PCH transition threshold =

[CELL_FACH to CELL_PCH transition time / (time to trigger +
pending time after trigger) * State transition traffic redundancy
coefficient]
Page127
This table lists the parameters used to calculate the threshold for UE state transition from
CELL_FACH to CELL_PCH.
467
Parameters
FTOPSTATETRANSTIMER
Parameter name : BE FACH to PCH transition timer
F2PTVMTIMETOTRIG
Parameter name: BE FACH to PCH 4b time to trigger
FTOPSTATETRANSTIMER
Parameter name : BE FACH to PCH transition timer
Unit: s
Page128
Content: This timer is used to check whether the UE in CELL_FACH state is in

stable low-activity state. Therefore, zero traffic event is used to determine the
need for transition from FACH to PCH.
F2PTVMTIMETOTRIG
Parameter name : BE FACH to PCH 4b time to trigger

D320, D640, D1280, D2560, D5000 .
1280, 2560, 5000
Unit: ms
volumes.
468
Parameters
F2PTVMPTAT
Parameter name : BE FACH to PCH 4b Pending Time after

trigger
Page129
F2PTVMPTAT
Parameter name : BE FACH to PCH 4b Pending Time after trigger
Unit: ms
469
Contents
Page130
470
From CELL_PCH to URA_PCH

z
This UE state transition occurs when only the BE service of the

PS domain exists.
Before the state transition, the state of the UE is CELL_PCH.

During the cell reselection, the UE sends the CELL UPDATE
messages. The RNC starts a timer and counts the number of
CELL UPDATE messages with the cause value of cell reselection.
When the timer expires, the number of CELL UPDATE messages
may exceed the threshold . In this case, the RNC initiates the
state transition when the UE sends the CELL UPDATE message
again.
Page131
The state transition from CELL_PCH to URA_PCH involves the transient state CELL_FACH, in
which some necessary signaling interaction is performed.
471
Parameters
CELLRESELECTTIMER
Parameter name : Cell reselection timer
CELLRESELECTCOUNTER
Parameter name: Cell reselection counter
CELLRESELECTTIMER
Parameter name : Cell reselection timer
Unit: s
Page132
Content: This parameter is used to check whether a UE is in the state of

frequent cell reselections.
CELLRESELECTCOUNTER
Parameter name : Cell reselection counter
Content: For a UE in CELL_PCH state, if the number of cell reselections

exceeds this parameter within the period defined by Cell reselection timer, it
is determined that the UE is in the state of frequent cell reselections.
472
Contents
Page133
473
From CELL_PCH or URA_PCH to CELL_FACH

z
The state of the UE transits to CELL_FACH when the UE is

paged by UTRAN, or the UE needs to exchange messages
with the network.
Page134
474
Contents
Page135
475
From CELL_FACH to CELL_DCH

z
The state of the UE transits to CELL_DCH when the

UTRAN receives a report which indicates that the UL or DL
traffic volume exceeds a 4a threshold.
Page136
Parameters used for UE state transition from CELL_FACH to CELL_DCH
476
Parameters (BE F/RACH to DCH)

z
FTODTVMTHD
Parameter name : BE F/RACH to DCH 4a threshold
Recommended value : D1024, namely 1024byte
FTODTVMTIMETOTRIG
Parameter name: BE F/RACH to DCH 4a time to trigger
Page137
FTODTVMTHD
Parameter name : BE F/RACH to DCH 4a threshold
Value range: D16, D32, D64, D128, D256, D512, D1024, D2k, D3k, D4k, D6k,
D8k, D12k, D16k, D24k, D32k, D48k, D64k, D96k, D128k, D192k, D256k,
D384k, D512k, D768k .
Physical value range: 16, 32, 64, 128, 256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k,
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
Content: Upper threshold for triggering the traffic volume event 4a for state
transition from FACH to DCH. If the value of this parameter is too high,
congestion may happen over the common channel.

FTODTVMTIMETOTRIG
Parameter name : BE F/RACH to DCH 4a time to trigger
D320, D640, D1280, D2560, D5000
1280, 2560, 5000
Unit: ms
Content: This parameter defines the time-to-trigger for event 4a, that is, the
transition from FACH to DCH. This parameter is used to avoid unnecessary
reports caused by unstable traffic volumes.
477
Parameters (BE FACH to HS-DSCH)

z
BEFTOHTVMTHD
Parameter name : BE FACH to HS-DSCH 4a threshold
BEFTOHTVMTIMETOTRIG
Parameter name: BE FACH to HS-DSCH 4a time to trigger
Page138
BEFTOHTVMTHD
Parameter name : BE FACH to HS-DSCH 4a threshold
D384k, D512k, D768k .
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
transition from FACH to DCH (with HS-DSCH). If the value of this parameter is
too high, congestion may happen over the common channel.

BEFTOHTVMTIMETOTRIG
Parameter name : BE FACH to HS-DSCH 4a time to trigger
D320, D640, D1280, D2560, D5000
1280, 2560, 5000
Unit: ms
transition from FACH to DCH (with HS-DSCH). This parameter is used to
avoid unnecessary reports caused by unstable traffic volumes.
478
Parameters (Realtime Traff FACH to DCH

or HSPA)
z
RTFTODHTVMTHD
Parameter name : Realtime Traff FACH to DCH or HSPA 4a

threshold
RTFTODHTVMTIMETOTRIG
Parameter name: Realtime Traff FACH to DCH or HSPA 4a

time to trigger
Page139
RTFTODHTVMTHD
Parameter name : Realtime Traff FACH to DCH or HSPA 4a threshold
D384k, D512k, D768k .
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
transition from FACH to DCH. If the value of this parameter is too high,
congestion may happen over the common channel..

RTFTODHTVMTIMETOTRIG
Parameter name : Realtime Traff FACH to DCH or HSPA 4a time to trigger
D320, D640, D1280, D2560, D5000
1280, 2560, 5000
Unit: ms
transition from FACH to DCH. This parameter is used to avoid unnecessary
reports caused by unstable traffic volumes.
479
Parameters (FACH to E-DCH)

z
FTOETVMTHD
Parameter name : FACH to E-DCH 4a Threshold
FTOETVMTIMETOTRIG
Parameter name: FACH to E-DCH 4a Time To Trigger
Page140
FTOETVMTHD
Parameter name : FACH to E-DCH 4a Threshold
D384k, D512k, D768k .
16k, 24k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k
Unit: byte
Content: This parameter determines the upper threshold of traffic volume for
event 4a triggering the transition from FACH to E-DCH.

FTOETVMTIMETOTRIG
Parameter name : FACH to E-DCH 4a Time To Trigger
D320, D640, D1280, D2560, D5000
1280, 2560, 5000
Unit: ms
transition from FACH to E-DCH. This parameter is used to avoid unnecessary
reports caused by fluctuation of traffic volumes.
480
Contents
1. DCCC Overview
6. Always Online
Page141
481
Always Online
z
If there is no data transmission for a PS service of a UE, the

connection for the service is released, but the CN reserves
the Packet Data Protocol (PDP) context of the PS service
for the UE.
When the UE reinitiates the service of this PDP context, it

does not have to apply for the PDP context again. Therefore,
the PS UE is always online.
Page142
When the RNC detects that there is no data transmission for a PS service, the RNC sends a
request to the CN for release of the service. The CN initiates the release procedure, and
requests the RNC to release the corresponding radio resources. However, the CN reserves
the PDP context for the PS UE. When the UE reinitiates the service of this PDP context, it
does not have to apply for the PDP context again. Therefore, the PS UE is always online.
482
Always Online
z
For each PS RAB, two PDCP timers are available. They are
T1 and T2.
T1 and T2 are RNC-oriented; they can be set differently for

the conversational service, streaming service, interactive
service, background service, and IMS signaling.
Page143
In RAN10.0, T1 and T2 are both set to 20 s for all the above services.
483
Process Description
z
For each PS RAB, two PDCP

timers are available. They are T1
and T2
T1 and T2 are RNC-oriented;

they can be set differently for the
conversational service, streaming
service, interactive service,
background service, and IMS
signaling.
Page144
When the PDCP entity of a service is set up, timer T1 is started.
When timer T1 expires and the PDCP entity still detects no data packet either in UL or DL, the
PDCP entity sends the request to the RRC layer for the service release and timer T2 is started.
If the CN does not initiate the service release, and the PDCP still detects no UL or DL data
packet when timer T2 expires, the PDCP entity sends the request again to the RRC layer for
the service release.
If there is only one RAB for the UE in the PS domain, the RNC sends an IU RELEASE
REQUEST message to the CN.
If there is more than one RAB for the UE in the PS domain, the RNC sends an RAB
RELEASE REQUEST message to the CN.
The release cause carried in both messages is "User Inactivity".
When the CN receives the message, it initiates the release procedure.
484
Parameters
z
PSINACTTMRFORCON
PROTECTTMRFORCON
Parameter name: Conversational service T2
PSINACTTMRFORSTR
Parameter name : Conversational service T1
Parameter name: Streaming service T1
PROTECTTMRFORSTR
Parameter name: Streaming service T2
Page145
485
Parameters
z
PSINACTTMRFORINT
PROTECTTMRFORINT
Parameter name: Interactive service T2
PSINACTTMRFORBAC
Parameter name : Interactive service T1
Parameter name: Background service T1
PROTECTTMRFORBAC
Parameter name: Background service T2
Page146
486
Parameters
PSINACTTMRFORIMSSIG
Parameter name: IMS signal T1
PROTECTTMRFORIMSSIG
Parameter name: IMS signal T2
Recommended value for all the above 10 parameters:
20, namely 20s
Description for all the above parameters (T1 and T2):
T1:
Unit: s
Page147
Content: When the T1 timer expires and there is still no data transmission for
the UE in the PS interactive service, the PDCP entity sends a request to the
RRC layer for release of the service.
Set this parameter through SET PSINACTTIMER
Unit: s
T2:
Content: When the T1 timer expires, the PDCP entity sends a request to the
RRC layer for release of the interactive service and the T2 timer is started. If
the service is not released when the T2 timer expires, the PDCP entity sends
again the request to the RRC layer for release of the service.
Set this parameter through SET PSINACTTIMER
487
Summary
z
In this course, we have discussed DCCC Algorithm:
Rate Reallocation Based on Traffic Volume
Rate Reallocation Based on Throughput
Rate Reallocation Based on Link Quality
UE State Transition Algorithm
Always Online
Page148
488
Thank you
www.huawei.com
489

WCDMA RAN Planning and Optimization - Book3 - 2 - Features and Algorithms

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

WCDMA RAN Planning and Optimization - Book3 - 2 - Features and Algorithms

Загружено:

Авторское право:

Доступные форматы

WCDMA Load Control

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

Upon completion of this course, you will be able to:

Know load control principles

Know load control realization methods in WCDMA system

Know load control parameters in WCDMA system

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

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

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

Load: the occupancy of capacity

Two kinds of capacity in WCDMA system

Cell DL OVSF Code

NodeB Transport resource

NodeB processing capability (NodeB credit)

Cell Power (UL and DL)

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

WCDMA network load can be defined by 4 factors:

The Objectives of Load Control

Keeping system stable

Maximizing system capacity while ensuring coverage and

Realize different priorities for different service and different

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

WCDMA network load can be defined by 4 factors:

Load Control Algorithms

The load control algorithms are applied to the different

PUC: Potential User Control

CAC: Call Admission Control

IAC: Intelligent Admission Control

LDB : Intra-frequency Load Balancing

LDR: Load Reshuffling

OLC: Overload Control

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

Load Control Algorithms

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

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

Soft Load Measurement

Received scheduled Enhanced Dedicated Channel (E-DCH)

Downlink Transmitted Carrier Power (TCP)

Provided Bit Rate on HS-DSCH (PBR)

Load Measurement procedure

Smooth Window Filtering on the RNC Side

N : the size of the smooth window

Pn : the reported measurement value

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

A is the sampling value of the measurement.

Delay susceptibilities of PUC, CAC, LDBLDR, and OLC to common measurement

PUC moving average

LDB moving average

UL LDR moving average

DL LDR moving average

UL CAC moving average

DL CAC moving average

UL OLC moving average

DL OLC moving average

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

The service of user with low priority will be affected by the

Three kinds of priorities

RAB Integrate Priority

User Integrate Priority

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

There are three levels of user priority

gold (high), silver (middle) and copper (low) user

128kbps 64kbps 32kbps