Rate Control Description (2008!05!30)

RAN
Rate Control Description

Issue 01
Date 2008-05-30

Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Proprietary and Confidential

RAN
Rate Control Description Contents

Issue 01 (2008-05-30) Huawei Proprietary and Confidential
i
Contents
1 Rate Control Change History...................................................................................................1-1
2 Rate Control Introduction ........................................................................................................2-1
3 AMRC/AMRC-WB Algorithms...............................................................................................3-1
3.1 Initial Access Rate of AMRC/AMRC-WB....................................................................................................3-2
3.1.1 Initial Access Rate of AMRC...............................................................................................................3-2
3.1.2 Initial Access Rate of AMRC-WB.......................................................................................................3-3
3.2 AMRC/AMRC-WB Algorithm Based on Uplink Stability ...........................................................................3-5
3.2.1 UL Measurement and Event Reporting................................................................................................3-5
3.2.2 UL AMRC/AMRC-WB Action............................................................................................................3-8
3.2.3 UL AMRC/AMRC-WB Signaling Procedure....................................................................................3-10
3.3 AMRC/AMRC-WB Algorithm Based on Downlink Stability .................................................................... 3-11
3.3.1 DL Measurement and Event Reporting.............................................................................................. 3-11
3.3.2 DL AMRC/AMRC-WB Algorithm....................................................................................................3-13
3.3.3 DL AMRC/AMRC-WB Signaling Procedure....................................................................................3-15
3.4 AMRC/AMRC-WB Algorithm Based on Basic Congestion.......................................................................3-16
3.4.1 UL AMR/AMR-WB Rate Downsizing Based on UL Basic Congestion ...........................................3-16
3.4.2 DL AMR/AMR-WB Rate Downsizing Based on DL Basic Congestion ...........................................3-17
3.4.3 Signaling Procedure of AMR/AMR-WB Rate Downsizing...............................................................3-17
3.4.4 Relation Between Congestion and Rate Upsizing..............................................................................3-18
3.5 AMRC/AMRC-WB Algorithm for TFO/TrFO ...........................................................................................3-18
3.5.1 Background Information of TFO/TrFO .............................................................................................3-18
3.5.2 Support for TFO/TrFO.......................................................................................................................3-19
3.5.3 AMRC/AMRC-WB Algorithm for TFO/TrFO..................................................................................3-19
4 DCCC Algorithm........................................................................................................................4-1
4.1 Rate Reallocation Based on Traffic Volume..................................................................................................4-1
4.1.1 Traffic Volume Measurement and Event Reporting.............................................................................4-1
4.1.2 UL Rate Reallocation Based on Traffic Volume ..................................................................................4-4
4.1.3 DL Rate Reallocation Based on Traffic Volume ..................................................................................4-8
4.1.4 Signaling Procedure of Rate Reallocation Based on Traffic Volume................................................. 4-11
4.2 Rate Reallocation Based on Throughput .....................................................................................................4-14
4.2.1 Throughput Measurement and Event Reporting ................................................................................4-14
4.2.2 Rate Reallocation Action Based on Throughput ................................................................................4-16

Contents
RAN

ii Huawei Proprietary and Confidential
Issue 01 (2008-05-30)
4.2.3 Signaling Procedure of Rate Reallocation Based on Throughput ......................................................4-17
4.3 Rate Reallocation Based on Link Quality ...................................................................................................4-19
4.3.1 Uplink Quality Measurement and Event Reporting...........................................................................4-19
4.3.2 Downlink Quality Measurement and Event Reporting......................................................................4-20
4.3.3 Rate Reallocation Action Based on Uplink Quality...........................................................................4-25
4.3.4 Rate Reallocation Action Based on Downlink Quality......................................................................4-26
4.3.5 Signaling Procedure of Rate Reallocation Based on Downlink Quality............................................4-28
4.4 BE Rate Downsizing and Recovery Based on Basic Congestion................................................................4-29
4.4.1 UL BE Rate Downsizing and Recovery Based on UL Basic Congestion..........................................4-29
4.4.2 DL BE Rate Downsizing and Recovery Based on DL Basic Congestion..........................................4-31
4.4.3 Signaling Procedure of Rate Downsizing ..........................................................................................4-32
4.4.4 Rate Upsizing Failure and Penalty.....................................................................................................4-33
4.5 UE State Transition Algorithm....................................................................................................................4-35
4.5.1 UE State Transition From CELL_DCH to CELL_FACH..................................................................4-36
4.5.2 UE State Transition From CELL_FACH to CELL_PCH...................................................................4-38
4.5.3 UE State Transition From CELL_PCH to URA_PCH.......................................................................4-39
4.5.4 UE State Transition From CELL_PCH or URA_PCH to CELL_FACH...........................................4-39
4.5.5 UE State Transition From CELL_FACH to CELL_DCH..................................................................4-39
4.6 Always Online.............................................................................................................................................4-40
5 Link Stability Control Algorithms .........................................................................................5-1
5.1 Link Stability Control Algorithms for AMR/AMR-WB Speech Services.....................................................5-1
5.1.1 Uplink Link Stability Control Algorithm.............................................................................................5-1
5.1.2 Downlink Link Stability Control Algorithm........................................................................................5-2
5.2 Link Stability Control Algorithms for VP Services.......................................................................................5-3
5.3 Link Stability Control Algorithms for BE Services.......................................................................................5-4
6 Rate Control Reference Documents .......................................................................................6-1

RAN
Rate Control Description 1 Rate Control Change History

1-1
1 Rate Control Change History
Rate Control Change History provides information on the changes between different
document versions.
Document and s
T nt and p t versions
Product Version
able 1-1 Docume roduc
Document Version RAN Version RNC Version NodeB Version
01 (2008-05-30) 10.0 V200R010C01B051 V100R010C01B049
V200R010C01B040
Draft (2008-03-20) 10.0 V200R010C01B050 V100R010C01B045

There are two types of changes, which are defined as follows:
Feature change: refers to the change in the Rate Control feature of a specific produc

t
version.

Editorial change: refers to the change in the information that has already been included,
previous version.
01(2008-05-30)
This is the document for the first commercial release of RAN10.0.
Compared with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-30) of RAN10.0
incorporates the changes described in the following table.
or the addition of the information that was not provided in the

RAN

1-2 Huawei Proprietary and Confidential
Issue 01 (2008-05-30)
Change
Type
Change Description Parameter Change
Feature
change
None. The parameters that are changed to
be non-configurable are listed as
follows:

Amr trigger time 6A1

Amr trigger time 6A2

Amr trigger time 6B1

Amr trigger time 6B2

Amr trigger time 6D

Wait Timer for Uplink Rate
Adjustment of Traffic AMR

Adjustment of Traffic WAMR

DL Measurement Reporting
Period

Pending time after trigger 4A

Pending time after trigger 4B

E-DCH Throu Meas Period

DCH Throu Meas Period

Period Amount to trigger 4A on
EDCH

Period Amount after trigger 4A
on EDCH

Period Amount to trigger 4B on
EDCH

Period Amount after trigger 4B on
EDCH

Percent Of Ratio For 128Kbps













DCH

RAN

1-3
Change Change Description Parameter Change
Type

Period Amount after trigger 4B
after DCH

UL measurement filter coefficient

DL measurement filter coefficient

Be trigger time 6A1

Be trigger time 6A2

Be trigger time 6B1

Be trigger time 6B2

Be trigger time 6D

Be trigger time of Event E

Be Reporting period unit for event
E

Be Event E reporting period in
10ms / min

re-TX monitor period

re-TX measure filter coef

Event A time to trigger

Event A pending time after trigger

Event F reporting power margin

Be trigger time of Event F

F

Be Event F reporting period in
10ms / min

DCCC rate up fail time threshold

DCCC rate up fail monitor time
length

DCCC rate up fail penalty time
length

Conversational service T2

Streaming service T2

Interactive service T2

Background service T2

IMS signal T2

Amr trigger time of Event E

Amr Event E Reporting Period In
10ms

Vp trigger time 6A1

Vp trigger time 6B1

Vp trigger time 6D

Vp trigger time of Event E

RAN

Issue 01 (2008-05-30)
Change Change Description Parameter Change
Type

Vp Event E reporting period in
10ms

Adjustment of Traffic BE

State trans traff redund coef
The Link Stability Control Algorithm
for BE Services is updated.
The UE State Transition From
CELL_FACH to CELL_DCH is
updated.
None
Editorial
change
General documentation change:

The Rate Control Parameters is
removed because of the creation of
RAN10.0 parameter Reference.

The structure is optimized.
None

Draft (2008-03-20)
This is a draft of the document for the first commercial release of RAN10.0.
Compared with issue 03 (2008-01-20) of RAN 6.1, this issue incorporates the changes
described in the following table.
Change Type Change Description Parameter Change
Feature change The AMRC/AMRC-WB
algorithms are updated and the
link stability control algorithm
of AMR/AMR-WB speech
services is added, see 5.1 Link
Stability Control Algorithms
for AMR/AMR-WB Speech
Services.
The added parameters are listed as
follows:

First Uplink QOS Enhancement
Action for Traffic BE

Second Uplink QOS Enhancement

Third Uplink QOS Enhancement

First Downlink QOS Enhancement

Second Downlink QOS
Enhancement Action for Traffic
BE

Third Downlink QOS
Enhancement Action for Traffic
BE

Uplink QOS Action Trigger
Indicator of Traffic BE

Srnc Downlink RLC QOS Action

RAN

1-5
Trigger Indicator of Traffic BE

Adjustment of Traffic AMR

InterFreq Handover Switch based
on Uplink Traffic AMR

InterRat Handover Switch based

on Uplink Traffic WAMR


on Downlink Traffic AMR


on Downlink Traffic WAMR


on Uplink Traffic VP

on Downlink Traffic VP

Measurement of 6A1 Switch

Measurement of 5A Switch

Measurement of 6D Switch
Throughput-based rate
reallocation on the DCH is
added and only rate
downsizing is applicable. For
detailed information, see 4.2
Rate Reallocation Based on
Throughput.
follows:

DCH Throu Meas Period

DCH

Period Amount after trigger 4B on
DCH

percent of ratio for 8Kbps to
384Kbps

RAN

Issue 01 (2008-05-30)
Rate reallocation based on
uplink quality is added. For
detailed information, see 4.3
Rate Reallocation Based on
Link Quality.
follows:

UL measurement filter coefficient

Be trigger time 6A1

Be trigger time 6A2

Be trigger time 6B1

Be trigger time 6B2

Be trigger time 6D

Statistic Block Number for 5A
Event

Event 5A Threshold

Interval Block Number Value

Srnc Downlink RLC QOS Action
Trigger Indicator of Traffic BE

DL measurement filter coefficient

Event Ea relative threshold

Event Eb relative threshold

Be trigger time of Event E

E

10ms

min

RL Max DL TX power

Event A threshold

Event A time to trigger

Event A pending time after trigger

re-TX monitor period

re-TX measure filter coef

Uplink full coverage bit rate

Downlink full coverage bit rate
The link stability control
algorithm has been added in
Rate Control. For detailed
information, see 5 Link
Stability Control Algorithm.
follows:



Freq Handover Switch based on
Uplink Traffic WAMR


RAN

1-7

Amr trigger time of Event E

Amr Reporting Period Unit For
Event E

10ms

Min





Vp trigger time 6A1

Vp trigger time 6B1

Vp trigger time 6D

on Uplink Traffic VP

Vp trigger time of Event E

Vp Reporting Period Unit For
Event E

Vp Event E Reporting Period In
10ms

Vp Event E Reporting Period In
Min

on Downlink Traffic VP
The DCCC, AMRC, and
AMRC-WB features have
been merged into one feature
Rate Control.
None Editorial
change
"Relation Between Congestion
and Rate Upsizing" is updated
and renamed as "Rate
Upsizing Failure and Penalty".
For detailed information, see
4.4.4 Rate Upsizing Failure
and Penalty.
None

RAN

Issue 01 (2008-05-30)
Implementation information
has been moved to a separate
document. For information on
how to implement rate control,
see Configuring Rate Control
in RAN Feature
Configuration Guide.
None

RAN
Rate Control Description 2 Rate Control Introduction

2-1
2 Rate Control Introduction
Rate control triggers rate upsizing, rate downsizing, and handover for different services
according to the consumption of resources.
Ra control in the Wideband Code Division Multiple Access (WCDMA) system has two
: rate control over Adaptive Multi Rate (AMR) services and rate control over Best Effort
services. Rate control herein is described in terms of the following algorithms:
Adaptive Multi-Rate Control (AMRC) / AMRC-WB algorith
te
types
(BE)

ms: They are implemented
d,

by the

Link stability control algorithm: It is implemented by the RNC. It triggers rate
downsizing, inter-frequency handover, and inter-RAT handover to guarantee the stability
of links and QoS of services. The rate downsizing of this algorithm is the power-based
Impact
AMR erformance
an process.
n be used to choose a proper AMR/AMR-WB
s way,
DCC

he Uu and Iub
ith the user profile
by the RNC. They dynamically adjust the transport format based on the cell load, link
power, and Iub resource utilization, so as to achieve the balance between the system loa
link stability, Iub resources, and link QoS. The UL AMRC/AMRC-WB algorithm and
the DL AMRC/AMRC-WB algorithm work independently.

Dynamic Channel Configuration Control (DCCC) algorithm: It is implemented
RNC. It controls the rate of BE services according to the traffic volume, throughput,
radio link quality, or congestion state. The UL DCCC algorithm and the DL DCCC
algorithm work independently.
rate downsizing in AMRC/AMRC-WB and DCCC.
C/AMRC-WB Impact on System P

The AMRC/AMRC-WB algorithm can be used to steer the UL permitted highest
AMR/AMR-WB speech codec mode down according to the UE transmit power. In this
way, the UL coverage is expanded.

The AMRC/AMRC-WB algorithm can be used to steer the permitted highest
AMR/AMR-WB speech codec mode down according to DPDCH transmit power or UE
transmit power. In this way, the system capacity is increased in terms of the maximum
number of UEs that the system c

The AMRC/AMRC-WB algorithm ca
speech codec mode according to the quality of the transmission environment. In thi
the speech quality is ensured.
C Impact on System Performance
Every time rate adjustment occurs, there is interactive signaling on t
interfaces. The impact on the system performance has relations w

2 Rate Control Introduction
RAN

Issue 01 (2008-05-30)
mode and the user traffic mode. In general, there is little impact of DCCC on the system
Link S Performance

Link stability control algorithm has no impact on system performance.
t on Other Features
Network Elem
T - the rk ts (NEs d in trol
Table 2- Es involv in rate control
performance.
tability Control Algorithm Impact on System
Rate Control Impac

Rate control has no impact on other features.
ents Involved
able 2 1describes Netwo Elemen ) involve rate con .
1 N ed
UE NodeB RNC MSC MGW SGSN GGSN HLR
Server

NOT

: involved
UE = User Equipment, RNC = Radio Network Controller, MSC = Mobile Service Switching Center,
MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support
Node, HLR = Home Location Register
E:
: not involved

RAN
Rate Control Description 3 AMRC/AMRC-WB Algorithms

3-1
3 AMRC/AMRC-WB Algorithms
T describes Key ed in the AMRC/AMRC-WB feature.
T n
able 3-1 terms involv
able 3-1 Key terms i volved in the AMRC/AMRC-WB feature
Term Definition
Guaranteed bit
(GBR)
rate The GBR is the minimum bit rate for the RNC to adjust. It is
contained in the RAB assignment message that the CN sends to the
RNC.
The supported
AMR speech codec
mode set
The set consists of all the AMR speech codec modes that can be used
for the service transport. The set is decided by the RNC according
the mode set specified by the RAB assignment.

to
The controllable The set consists of the AMR speech codec modes that are contained
in the supported AMR speech codec mode set and are equal to or AMR speech codec
mode set larger than the GBR. The modes in this set can be selected by the
AMRC/AMRC-WB algorithm.
For example:
The supported AMR speech codec mode set is {NO DATA, SID, 4.75 kbit/s, 7.95 kbit/s,
12.2 kbit/s}.
Then, the controllable AMR speech codec mode set is {4.75 kbit/s, 7.95 kbit/s, 12.2 kbit/s},
if the GBR is 4.75 kbit/s.

This chapter describes two important algorithms: AMRC and AMRC-WB, the following lists
c
k Stability

AMRC/AMRC-WB Algorithm Based on Downlink Stability

AMRC/AMRC-WB Algorithm Based on Basic Congestion

AMRC/AMRC-WB Algorithm for TFO/TrFO
the ontents of this chapter.

Initial Access Rate of AMRC/AMRC-WB

AMRC/AMRC-WB Algorithm Based on Uplin

RAN

Issue 01 (2008-05-30)
3.1 Initial Access Rate of AMRC/AMRC-WB
3.1.1 Initial Access Rate of AMRC
Initial Access Rate of AMRC provides the definition of initial access rate, values of initial
access rate and controllable mode set in different situations.
Definition of Initial Access Rate

For uplink, the initial access rate is not only the maximum permitted bit rate at the start
of the communication phase, but also the maximum bit rate that the UL AMRC
algorithm can select, that is, the maximum bit rate in the uplink controllable AMR
speech codec mode set (controllable mode set for short) and uplink supported AMR
speech codec mode set (supported mode set for short).

For downlink, the initial access rate is the maximum permitted bit rate at the start of the
communication phase.
Value of Initial Access Rate
AMRC Algorithm Enabled
When the AMRC algorithm is enabled,

If the cell load is in basic congestion, the initial access rate is the GBR in the RAB
parameters.

If the cell load is normal, commonly, the initial access rate is the maximum rate that is in
the RAB assignment message sent from the CN and meets both the following conditions:
Higher than or equal to the GBR in the RAB assignment message sent from the CN
Lower than or equal to the UE-priority-oriented maximum rate that is set on the RNC
LMT
For detailed information about how to enable the AMRC algorithm, see the Rate Control

The UE-priority-oriented maximum rate refers to the Max mode of narrowband AMRC for golden
users, Max mode of narrowband AMRC for silver users, and Max mode of narrowband AMRC for
copper users parameters. For detailed information about the definitions and description of the user
priority, see Priorities Involved in Load Control.
If the UE-priority-oriented maximum rate is lower than the GBR in the RAB assignment message, then
the initial access rate is the GBR.
This note applies to all the initial access rates mentioned thereafter.
AMRC Algorithm Disabled
When the AMRC algorithm is disabled, the initial access rate is the maximum rate that is in
the RAB assignment message sent from the CN and meets both the following conditions:


LMT
In this case, all the AMR rates in the controllable mode set, a subset of the set in the RAB
assignment message, are no lower than GBR and no higher than the UE-priority-oriented
maximum rate configured on the RNC LMT.

RAN

3-3
Controllable Mode Set
Only when AMRC algorithm is enabled, the controllable mode set is valid.

For links in the uplink,
If the initial access rate is the GBR in the RAB assignment message, the uplink
controllable mode set contains only one rate, that is, {GBR in the RAB assignment
message}.
If the initial access rate is higher than the GBR in the RAB assignment message, the
uplink controllable mode set is {GBR in the RAB assignment message, initial access
rate}.

For links in the downlink,
In the case of Iu UP version 2, the downlink controllable mode set contains all the
rates that are included in the RAB assignment message and higher than or equal to
the GBR.
In the case of Iu UP version 1 and code-resource-saving algorithm disabled, assume
that the maximum rate that is in the RAB assignment message sent from the CN and
meets both of the following conditions is expressed as Rmax:
a. Higher than or equal to the GBR in the RAB assignment message sent from the
CN
b. Lower than or equal to the UE-priority-oriented maximum rate that is set on the
RNC LMT
Then, if Rmax is higher than the GBR, the downlink controllable mode set is {GBR in
the RAB assignment message, Rmax}. Otherwise, the downlink controllable mode set
contains only one rate, that is {GBR in the RAB assignment message}.

In the case of Iu UP version 1 and code-resource-saving algorithm enabled,
If the initial access rate is the GBR in the RAB assignment message, the downlink
message}.
downlink controllable mode set is {GBR in the RAB assignment message, initial
access rate}.

The DL code-resource-saving algorithm is available for the RNC. This algorithm allows a single speech
service which has a DL maximum rate of 7.95 kbit/s or lower to use 256 as the Spreading Factor (SF)
for the downlink. When the DL code-resource-saving algorithm is disabled, SF128 is used for the
downlink.
3.1.2 Initial Access Rate of AMRC-WB
This provides the definition of initial access rate, values of initial access rate and controllable
mode set in different situations.
Definition of Initial Access Rate

For uplink, the initial access rate is not only the maximum permitted bit rate at the start
of the communication phase, but also the maximum bit rate that the UL AMRC-WB
algorithm can select, that is, the maximum bit rate in the uplink controllable AMR-WB
speech codec mode set (controllable mode set for short) and uplink supported AMR-WB
speech codec mode set (supported mode set for short).

RAN

Issue 01 (2008-05-30)

For downlink, the initial access rate is the maximum permitted bit rate at the start of the
communication phase.
Value of Initial Access Rate
AMRC-WB Algorithm Enabled
When the AMRC-WB algorithm is enabled,

If the cell load is in basic congestion, the initial access rate is the GBR in the RAB
parameters.

If the cell load is normal, the initial access rate is the maximum rate that is in the RAB
assignment message sent from the CN and meets both the following conditions:
LMT
For detailed information about how to enable the AMRC-WB algorithm, see the Rate Control

The UE-priority-oriented maximum rate refers to the Max mode of wideband AMRC for golden users,
Max mode of wideband AMRC for silver users, and Max mode of wideband AMRC for copper
users parameters. For detailed information about the definitions and description of the user priority, see
Priorities Involved in Load Control in Load Control.
If the UE-priority-oriented maximum rate is lower than the GBR in the RAB assignment message, then
the initial access rate is the GBR.
This note applies to all the initial access rates mentioned thereafter.
AMRC-WB Algorithm Disabled
When the AMRC-WB algorithm is disabled, the initial access rate is the maximum rate that is
in the RAB assignment message sent from the CN and meets both the following conditions:


LMT
Controllable Mode Set
Only when AMRC-WB algorithm is enabled, the controllable mode set is valid.

For links in the uplink,
If the initial access rate is the GBR in the RAB assignment message, the uplink
message}.
uplink controllable mode set is {GBR in the RAB assignment message, initial access
rate}.

For links in the downlink,
In the case of Iu UP version 2, the downlink controllable mode set contains all the
rates that are included in the RAB assignment message and higher than or equal to
the GBR.

RAN

3-5
In the case of Iu UP version 1, assume that the maximum rate that is in the RAB
assignment message sent from the CN and meets both of the following conditions is
expressed as Rmax:
Higher than or equal to the GBR in the RAB assignment message sent from the
CN
Lower than or equal to the UE-priority-oriented maximum rate that is set on the
RNC LMT
Then, if Rmax is higher than the GBR, the downlink controllable mode set is {GBR in
the RAB assignment message, Rmax}. Otherwise, the downlink controllable mode set
contains only one rate, which is {GBR in the RAB assignment message}.
3.2 AMRC/AMRC-WB Algorithm Based on Uplink
Stability
The UL AMRC algorithm steers the UL permitted highest AMR speech codec mode up or
down according to the UE transmit (TX) power.
3.2.1 UL Measurement and Event Reporting
Measurement results serve as the basis of AMRC/AMRC-WB. By comparing the
measurement results with associated thresholds, the UE reports events. Then, the RNC takes
associated AMRC/AMRC-WB actions.
UL Measurement
In the uplink, the measurement quantity is the transmit power of the UE.
UL Events and Thresholds
UL AMRC/AMRC-WB events consist of 6A1, 6A2, 6B1, 6B2 and 6D.
Events 6A1, 6A2, 6B1, and 6B2
Events 6A1, 6B1, 6A2, and 6B2 have their respective thresholds. The thresholds 6A1, 6B1,
6A2, and 6B2 in Figure 3-1 are specific for measurement events 6A1, 6B1, 6A2, and 6B2
respectively.

RAN

Issue 01 (2008-05-30)
Figure 3-1 UL events and thresholds

The Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 in Figure 3-1 refer to the following
relative values respectively:

The relative value between the TX power threshold 6A1 and the Max UL TX power of
conversational service

The relative value between the TX power threshold 6B1 and the Max UL TX power of

The relative value between the TX power threshold 6A2 and the Max UL TX power of

The relative value between the TX power threshold 6B2 and the Max UL TX power of
Therefore, Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 are relative measurement
thresholds.
A set of relative measurement thresholds for all AMR/AMR-WB services are configured. The
set includes the following parameters:

Uplink 6A1 event relative threshold

Uplink 6B1 event relative threshold

Uplink 6A2 event relative threshold

Uplink 6B2 event relative threshold
The measurement thresholds, that is, the absolute measurement thresholds, are calculated on
the basis of the following formula:

Measurement threshold 6A1 = Max UL TX power of conversational service Uplink
6A1 event relative threshold

Measurement threshold 6B1 = Max UL TX power of conversational service Uplink
6B1 event relative threshold

Measurement threshold 6A2 = Max UL TX power of conversational service Uplink
6A2 event relative threshold

RAN

3-7

Measurement threshold 6B2 = Max UL TX power of conversational service Uplink
6B2 event relative threshold
Event 6D
The threshold of event 6D is the maximum UE Tx power, which can not be set on the RNC
LMT.
Figure 3-2 Event 6D and thresholds

Event Reporting
After establishing an AMR/AMR-WB speech service, the UTRAN sends the UE a
MEASUREMENT CONTROL message to configure

the TX power threshold of 6A1, 6B1, 6A2, 6B2, and 6D.

the trigger time of 6A1, 6B1, 6A2, 6B2, and 6D.
For AMR/AMR-WB service, the trigger time of 6A1, 6B1, 6A2 and 6B2 is set to 320 ms,
and the trigger time of 6D is set to 640 ms.
Then, the UE measures the TX power in real time, filters the measurement results, and makes
decisions as follows:

If the UE TX power has been higher than TX power threshold 6A1 for a period longer
than the trigger time of 6A1 and the TRIGGERED_6A1_EVENT variable is FALSE,
event 6A1 is triggered and the TRIGGERED_6A1_EVENT variable is set to TRUE.

If the TRIGGERED_6A1_EVENT variable is TRUE and the UE TX power is lower than
TX power threshold 6A1, the TRIGGERED_6A1_EVENT variable is set to FALSE.

If the UE TX power has been lower than TX power threshold 6B1 for a period longer
than the trigger time of 6B1 and the TRIGGERED_6B1_EVENT variable is FALSE,
event 6B1 is triggered and the TRIGGERED_6B1_EVENT variable is set to TRUE.

If the TRIGGERED_6B1_EVENT variable is TRUE and the UE TX power is higher than
TX power threshold 6B1, the TRIGGERED_6B1_EVENT variable is set to FALSE.

If the UE TX power has been lower than TX power threshold 6B2 for a period longer
than the trigger time of 6B2 and the TRIGGERED_6B2_EVENT variable is FALSE,
event 6B2 is triggered and the TRIGGERED_6B2_EVENT variable is set to TRUE.

RAN

Issue 01 (2008-05-30)

If the TRIGGERED_6B2_EVENT variable is TRUE and the UE TX power is higher than
TX power threshold 6B2, the TRIGGERED_6B2_EVENT variable is set to FALSE.

If the UE TX power has been higher than TX power threshold 6A2 for a period longer
than the trigger time of 6A2 and the TRIGGERED_6A2_EVENT variable is FALSE,
event 6A2 is triggered and the TRIGGERED_6A2_EVENT variable is set to TRUE.

If the TRIGGERED_6A2_EVENT variable is TRUE and the UE TX power is lower than
TX power threshold 6A2, the TRIGGERED_6A2_EVENT variable is set to FALSE.

If the UE Tx power equals the maximum UE TX power for the trigger time of 6D and
the variable TRIGGERED_6D_EVENT is set to FALSE, event 6D is triggered and the
variable TRIGGERED_6D_EVENT to TRUE.

If the variable TRIGGERED_6D_EVENT is set to TRUE and if the UE Tx power is less
than the maximum UE TX power, set the variable TRIGGERED_6D_EVENT to
FALSE.

For detailed information about the TRIGGERED_6A1_EVENT, TRIGGERED_6A2_EVENT,
TRIGGERED_6B1_EVENT, TRIGGERED_6B2_EVENT and TRIGGERED_6D_EVENT variables, see
the 3GPP TS 25.331.
Each time a measurement event is triggered, the UE sends the measurement report to the
UTRAN (as shown in Figure 3-1) and the UL AMRC/AMRC-WB algorithm makes a
corresponding adjustment according to the reported measurement event. For detailed
information about the signaling procedure, see 3.2.3 UL AMRC/AMRC-WB Signaling
Procedure.
3.2.2 UL AMRC/AMRC-WB Action
Based on the event reports from the UE, the UL AMRC/AMRC-WB algorithm takes
associated AMRC/AMRC-WB actions.
Principles of the UL AMRC/AMRC-WB Algorithm
The principles of the UL AMRC/AMRC-WB algorithm are as follows:

To steer the UL permitted highest AMR/AMR-WB speech codec mode up, the following
requirements must be satisfied:
The UE TX power is below a certain threshold.
The UL load resource is not in congestion state.

To steer the UL permitted highest AMR/AMR-WB speech codec mode down, the UE TX
power must be higher than a certain threshold.
The UL AMRC/AMRC-WB algorithm steers the UL permitted highest AMR/AMR-WB
speech codec mode up or down in the controllable mode set by only one level each time.
Details of the UL AMRC/AMRC-WB Algorithm
The UL AMRC/AMRC-WB algorithm adjusts the UL permitted highest AMR/AMR-WB
speech codec mode as follows:

When an event 6A1 or 6D is received, the UL AMRC/AMRC-WB algorithm decreases
the UL permitted highest AMR/AMR-WB speech codec mode by one level and starts the
UL AMRC/AMRC-WB timer whose length is 3000ms. If the rate before the decrease is
GBR or rate decrease fails, handover can be performed. For details, refer to 5.1 Link
Stability Control Algorithms for AMR/AMR-WB Speech Services.

RAN

3-9
If the event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires,
the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the
UL AMRC/AMRC-WB timer and ends the adjustment.
If no event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires
and if the current rate is higher than GBR, the adjustment is not complete. The UL
AMRC/AMRC-WB algorithm decreases the UL permitted highest AMR/AMR-WB
speech codec mode by one more level and restarts the UL AMRC/AMRC-WB timer.
If the rate before the decrease is GBR, handover can be performed. For details or rate
decrease fails, refer to 5.1 Link Stability Control Algorithms for AMR/AMR-WB
Speech Services.

When an event 6B2 is received and UL load resource is not in congestion state, the UL
AMRC/AMRC-WB algorithm increases the UL permitted highest AMR/AMR-WB
speech codec mode by one level and starts the UL AMRC/AMRC-WB timer whose
length is 3000ms. If the rate before the increase is the maximum one in the controllable
mode set, no increase will be performed, and the UL AMRC/AMRC-WB timer does not
start.
If the event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires,
the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the
UL AMRC/AMRC-WB timer and ends the adjustment.
If no event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires
and if UL load resource is still not in congestion state, the adjustment is not complete.
The UL AMRC/AMRC-WB algorithm increases the UL permitted highest
AMR/AMR-WB speech codec mode by one more level and restarts the UL
AMRC/AMRC-WB timer. If the rate before the increase is the maximum one in the
controllable mode set, no increase will be performed, and the UL AMRC/AMRC-WB
timer does not restart.

In current version, there are two rates in the controllable mode set at most.
Table 3-2 UL AMRC/AMRC-WB algorithm
Event Permitted Highest AMR/AMR-WB
Speech Codec Mode
UL AMRC/AMRC-WB
Timer
6A1 Started
6B1 Stopped
6A2 Stopped
6B2 Started
: depicts decrease in the permitted highest AMR/AMR-WB speech codec mode.
: depicts increase in the permitted highest AMR/AMR-WB speech codec mode.
: depicts no change on the current permitted highest AMR/AMR-WB speech codec
mode.
If event 6B1 is reported when the permitted highest AMR/AMR-WB speech codec mode is
, then no adjustment related to event 6B1 is made.
If event 6A2 is reported when the permitted highest AMR/AMR-WB speech codec mode is
, then no adjustment related to event 6A2 is made.

RAN

Issue 01 (2008-05-30)

If the event 6A2 or 6B1 is received when the UL AMRC/AMRC-WB timer is not started, the
AMRC/AMRC-WB algorithm regards it as a normal variation of UE TX power and does not make any
adjustment.
3.2.3 UL AMRC/AMRC-WB Signaling Procedure
This describes UL AMRC/AMRC-WB signaling procedures.
As shown in Figure 3-3, the UTRAN sends the information to the UE through a
MEASUREMENT CONTROL message

the TX power threshold of 6A1, 6B1, 6A2, 6B2, and 6D.

the trigger time of 6A1, 6B1, 6A2, 6B2, and 6D.
Figure 3-3 Signaling procedure of measurement control

As shown in Figure 3-4, the UE reports events 6A1, 6B1, 6A2, 6B2 or 6D by sending a
MEASUREMENT REPORT message.
Figure 3-4 Signaling procedure of measurement reporting

As shown in Figure 3-5, the RNC adjusts the UL permitted highest AMR/AMR-WB speech
codec mode by sending a TRANSPORT FORMAT COMBINATION CONTROL message
and adjusts the UL bandwidth by sending a QAAL2 MODIFY message.

RAN

3-11
Figure 3-5 Signaling procedure of UL AMR/AMR-WB speech codec mode adjustment

3.3 AMRC/AMRC-WB Algorithm Based on Downlink
Stability
The DL AMRC algorithm steers the DL permitted highest AMR speech codec mode up or
down according to the DPDCH transmit (TX) power.
3.3.1 DL Measurement and Event Reporting
Measurement results serve as the basis of AMRC/AMRC-WB. By comparing the
measurement results with associated thresholds, the RNC triggers AMRC/AMRC-WB
actions.
DL Measurement
In the downlink, the measurement quantity is the DPDCH transmit (TX) power.
DL Events and Thresholds
DL AMRC/AMRC-WB events consist of E1, E2, F1, and F2.
The thresholds E1, E2, F1, and F2 in Figure 3-6 are specific for measurement events E1, E2,
F1, and F2 respectively.

RAN

Issue 01 (2008-05-30)
Figure 3-6 DL Events and Thresholds

In Figure 3-6:

For event E1, the average TX power on the DPDCH is higher than the TX power
threshold E1.

For event E2, the average TX power on the DPDCH is lower than the TX power
threshold E2.

For event F1, the average TX power on the DPDCH is lower than the TX power
threshold F1.

For event F2, the average TX power on the DPDCH is higher than the TX power
threshold F2.
The Delta_E1, Delta_E2, Delta_F1, and Delta_F2 in Figure 3-6 refer to the following relative
values respectively:

The relative value between the TX power threshold E1 and the RL Max DL TX power

The relative value between the TX power threshold E2 and the RL Max DL TX power

The relative value between the TX power threshold F1 and the RL Max DL TX power

The relative value between the TX power threshold F2 and the RL Max DL TX power
Therefore, Delta_E1, Delta_E2, Delta_F1, and Delta_F2 are relative measurement thresholds.
A set of relative measurement thresholds for all AMR/AMR-WB services are configured. The
set includes the following parameters:

DL E1 event relative threshold

DL E2 event relative threshold

DL F1 event relative threshold

DL F2 event relative threshold

RAN

3-13
The measurement thresholds, that is, the absolute measurement thresholds, are calculated on
the basis of the following formula:

Measurement threshold E1 = RL Max DL TX power DL E1 event relative threshold

Measurement threshold E2 = RL Max DL TX power DL E2 event relative threshold

Measurement threshold F1 = RL Max DL TX power DL F1 event relative threshold

Measurement threshold F2 = RL Max DL TX power DL F2 event relative threshold
Event Reporting
After establishing a service, the UTRAN sends a request to the NodeB for periodical
measurements of DL Transmitted Code Power (TCP) in the pilot field of DPCCH, and NodeB
sends the TCP measurement reports to the RNC every 480 ms.
The RNC processes the measurement report as follows:
1. The RNC converts DL TCP in the pilot field of DPCCH to the average TX power of the
DPDCH.
2. The RNC compares the average DPDCH TX power with the measurement thresholds E1,
E2, F1 and F2 to determine the type of event.
3.3.2 DL AMRC/AMRC-WB Algorithm
The DL AMRC/AMRC-WB algorithm steers the DL permitted highest AMR/AMR-WB
speech codec mode up or down according to the DPDCH transmit (TX) power.
Principles of the DL AMRC/AMRC-WB Algorithm
The principles of the DL AMRC/AMRC-WB algorithm are as follows:

To steer the DL permitted highest AMR/AMR-WB speech codec mode up, the following
requirements must be satisfied:
The DPDCH TX power is below a certain threshold.
The DL load resource is not in congestion state.

To steer the DL permitted highest AMR/AMR-WB speech codec mode down, the
DPDCH TX power must be higher than a certain threshold.
The DL AMRC/AMRC-WB algorithm steers the DL permitted highest AMR/AMR-WB
speech codec mode up or down in the controllable mode set by only one level each time.
Details of the DL AMRC/AMRC-WB Algorithm
The DL AMRC/AMRC-WB algorithm adjusts the DL permitted highest AMR speech codec
mode as follows:

When the average DPDCH power is higher than the threshold E1, the DL
AMRC/AMRC-WB algorithm decreases the DL permitted highest AMR/AMR-WB
speech codec mode by one level and sets the AMRC/AMRC-WB status to Rate-Down. If
the rate before the decrease is GBR or rate decrease fails, handover can be performed.
For detailed information, see 5.1 Link Stability Control Algorithms for AMR/AMR-WB
Speech Services.

When the average DPDCH power is lower than the threshold F1 and the DL load is not
in congestion state, the DL AMRC/AMRC-WB algorithm increases the DL permitted
highest AMR/AMR-WB speech codec mode by one level and sets the

RAN

Issue 01 (2008-05-30)
AMRC/AMRC-WB status to Rate-Up. If the rate before the increase is the maximum
one in the controllable mode set, no increase will be performed.

When the average DPDCH power is between the thresholds E2 and F2, the current DL
AMR/AMR-WB speech rate is appropriate. The DL AMRC/AMRC-WB algorithm
makes no adjustment and sets the AMRC/AMRC-WB status to Normal.

When the average DPDCH power is lower than or equal to the threshold E1 and higher
than the threshold E2, the DL AMRC/AMRC-WB algorithm makes adjustments
according to the AMRC/AMRC-WB status.
If the AMRC/AMRC-WB status is Rate-Down, the DL AMRC/AMRC-WB
algorithm decreases the DL permitted highest AMR/AMR-WB speech codec mode
by one level. If the rate before the decrease is GBR or rate decrease fails, handover
can be performed. For detailed information, see 5.1 Link Stability Control Algorithms
for AMR/AMR-WB Speech Services.
If the AMRC/AMRC-WB status is Normal or Rate-Up, the DL AMRC/AMRC-WB
algorithm makes no adjustment.

When the average DPDCH power is lower than the threshold F2 and higher than or equal
to the threshold F1, the DL AMRC/AMRC-WB algorithm makes adjustments according
to the AMRC/AMRC-WB status and DL load status.
If the AMRC/AMRC-WB status is Rate-Up and the DL load is not in congestion state,
the DL AMRC/AMRC-WB algorithm increases the DL permitted highest
AMR/AMR-WB speech codec mode by one more level. If the rate before the
increase is the maximum one in the controllable mode set, no increase will be
performed.
If the AMRC/AMRC-WB status is Normal or Rate-Down, the DL
AMRC/AMRC-WB algorithm makes no adjustment.
Table 3-3 Change of DL permitted highest AMR/AMR-WB speech codec mode
DPDCH
Power
Mode Change when
AMRC/AMRC-WB
Status is Normal
Mode Change when
AMRC/AMRC-WB
Status is Rate_Down
Mode Change when
AMRC/AMRC-WB
Status is Rate_Up
DPDCH
power > the
TX power
threshold
E1

The TX
power
threshold
E2 <
DPDCH
power the
TX power
threshold
E1

RAN

3-15
DPDCH Mode Change when Mode Change when Mode Change when
Power AMRC/AMRC-WB
Status is Normal
AMRC/AMRC-WB AMRC/AMRC-WB
Status is Rate_Down Status is Rate_Up
The TX
power
threshold F2
DPDCH
power the
TX power
threshold
E2

The TX
power
threshold F1
DPDCH
power < the
TX power
threshold F2

DPDCH
power < the
TX power
threshold F1

: depicts the decrease in the permitted highest AMR/AMR-WB speech codec mode.
: depicts the increase in the permitted highest AMR/AMR-WB speech codec mode.
: depicts no change on the current permitted highest AMR/AMR-WB speech codec
mode.

3.3.3 DL AMRC/AMRC-WB Signaling Procedure
This describes DL AMRC/AMRC-WB signaling procedures.
As shown in Figure 3-7, the RNC sets periodical measurement reporting by sending a
DEDICATED MEASUREMENT INITIATION REQUEST message to the NodeB.
Figure 3-7 Signaling procedure of dedicated measurement

As shown in Figure 3-8, the NodeB reports the measurement results by sending a
DEDICATED MEASUREMENT REPORT message.

RAN

Issue 01 (2008-05-30)
Figure 3-8 Signaling procedure of dedicated measurement reporting

As shown in Figure 3-9, the RNC adjusts the DL rate by sending an IUUP RATE CONTROL
REQUEST message.
Figure 3-9 Signaling procedure of DL rate adjustment

3.4 AMRC/AMRC-WB Algorithm Based on Basic
Congestion
AMRC/AMRC-WB Algorithm Based on Basic Congestion is one of the actions implemented
by Load Reshuffling (LDR).

When the cell enters the basic congestion state, the LDR algorithm triggers the
corresponding actions to reduce the cell load. For detailed information, see Load
Reshuffling in load control.

When the cell exits the basic congestion state, the LDR algorithm will no longer do any
action to the UEs in the cell. The rate of the service will be increased according to
AMRC/AMRC-WB algorithm based on link stability.
3.4.1 UL AMR/AMR-WB Rate Downsizing Based on UL Basic
Congestion
When a cell enters the basic congestion state in the uplink and AMR/AMR-WB rate
downsizing is triggered, the uplink permitted maximum AMR/AMR-WB speech codec rate
will be reduced to the GBR in the uplink controllable mode set.

RAN

3-17
3.4.2 DL AMR/AMR-WB Rate Downsizing Based on DL Basic
Congestion
When a cell enters the basic congestion state in the downlink and AMR/AMR-WB rate
downsizing is triggered, the downlink permitted maximum AMR/AMR-WB speech codec
rate will be reduced to the GBR in the downlink controllable mode set.
3.4.3 Signaling Procedure of AMR/AMR-WB Rate Downsizing
AMR/AMR-WB Rate Downsizing based on basic congestion uses the signaling interaction on
the Uu and Iu interface to adjust the permitted maximum AMR/AMR-WB speech codec
mode.
This describes the Signaling Procedure of UL AMR/AMR-WB Rate Downsizing .
As shown in the following figure, the RNC downsizes the UL permitted highest
AMR/AMR-WB speech codec mode by sending a TRANSPORT FORMAT COMBINATION
CONTROL message and downsizes the UL bandwidth by sending a QAAL2 MODIFY
message.
Figure 3-10 Signaling procedure of UL AMR/AMR-WB rate downsizing based on UL basic
congestion

This describes the Signaling Procedure of DL AMR/AMR-WB Rate Downsizing.
As shown in the following figure, the RNC downsizes the DL permitted highest
AMR/AMR-WB speech codec mode by sending an IUUP RATE CONTROL REQUEST
message.
Figure 3-11 Signaling procedure of DL AMR/AMR-WB rate downsizing based on DL basic
congestion

RAN

Issue 01 (2008-05-30)
3.4.4 Relation Between Congestion and Rate Upsizing
During the congestion period, the RNC does not upsize the service rate.
3.5 AMRC/AMRC-WB Algorithm for TFO/TrFO
This describes the AMRC/AMRC-WB algorithm for TFO/TrFO from the following aspects:
background information of TFO/TrFO, support for TFO/TrFO, and AMRC/AMRC-WB
algorithm for TFO/TrFO.
3.5.1 Background Information of TFO/TrFO
Tandem Free Operation (TFO) is intended to avoid the traditional double speech
encoding/decoding in MS to MS (GSM), MS to UE (GSM/3G), or UE to UE (3G) call
configurations. In the following paragraphs, the term "MS" is used for MS and UE, and the
term "UE" is used only if a 3G terminal is explicitly addressed.
In a normal UE-UE call configuration, the speech signals are:
1. Encoded in the originating UE
2. Sent over the Uu interface
3. Converted to A-law or -law ITU-T Recommendation G.711 in the local transcoder
4. Carried over the fixed network
5. Transcoded again in the distant transcoder
6. Sent over the distant Uu interface
7. Decoded in the terminating UE
See Figure 3-12. In this configuration, the two speech codecs (coder/decoder pairs) are in
tandem operation. The key inconvenience of a tandem configuration is the speech quality
degradation introduced by the double transcoding. This degradation is usually more
noticeable when the speech codecs are operating at low rates.
Figure 3-12 Typical speech codec tandem operation

When the originating and terminating connections are using the same speech codec, it is
possible to transmit transparently the speech frames received from the originating UE to the
terminating UE without activating the transcoding functions in the originating and terminating
networks. In this configuration, TFO or Transcoder Free Operation (TrFO) is ongoing.

RAN

3-19
For detailed information about TFO and TrFO, see 3GPP TS 28.062.
3.5.2 Support for TFO/TrFO
To enable the RNC to use the AMRC/AMRC-WB algorithm for TFO/TrFO, the following
conditions must be met:

The AMRC/AMRC-WB algorithm is enabled.

The supported Iu UP version assigned by the CN includes version 2.
When both the UE and the network supporting the UE-UE calls use the same codec type
and codec mode set, the transcoding functions may be omitted to improve the speech
quality and the CN will assign Iu UP version 2.

The IUUP_V2_SPT_SWITCH under the Channel class algorithm switch parameter is
on.
3.5.3 AMRC/AMRC-WB Algorithm for TFO/TrFO
The rules of the AMRC/AMRC-WB algorithm for the TFO/TrFO are as follows:

The UL permitted highest AMR/AMR-WB speech codec mode can be steered down on
the local RNC according to 3.2.2 UL AMRC/AMRC-WB Action.

The UL permitted highest AMR/AMR-WB speech codec mode may be steered up on the
local RNC according to 3.2.2 UL AMRC/AMRC-WB Action. Ensure that the UL highest
mode after the adjustment is lower than or equal to the DL highest mode requested by
the peer RNC most recently.

Compared with 3.2.2 UL AMRC/AMRC-WB Action, the adjustment of the UL permitted
highest AMR/AMR-WB speech codec mode can be triggered by the peer RNC. The
rules for the local RNC to respond to the mode requests from the peer RNC are as
follows:
If... Then...
The current UL highest codec mode is
higher than the highest codec mode
requested by the peer RNC.
The local RNC sends the TRANSPORT
FORMAT COMBINATION CONTROL
message to the UE to steer the permitted
highest AMR/AMR-WB speech codec mode
down to the mode that is lower than and
nearest to the highest AMR/AMR-WB speech
codec mode requested by the peer RNC in the
UL controllable mode set.

RAN

Issue 01 (2008-05-30)
If... Then...
The following conditions are fulfilled at
the same time:

lower than the highest codec mode

The highest codec mode requested by
the peer RNC is not in the UL
controllable mode set.

In the UL controllable mode set, there
is an AMR/AMR-WB speech codec
mode that is lower than and nearest to
the highest AMR/AMR-WB speech
codec mode requested by the peer RNC
and that is higher than the current UL
highest AMR/AMR-WB speech codec
mode.

The UL load resource is not in
congestion state.
highest AMR/AMR-WB speech codec mode
up to the mode that is lower than and nearest to
the highest AMR/AMR-WB speech codec
mode requested by the peer RNC in the UL
controllable mode set.
The following conditions are fulfilled at
the same time:

lower than the highest codec mode

The highest codec mode requested by
the peer RNC is in the UL controllable
mode set.

The UL load resource is not in
congestion state.
highest AMR/AMR-WB speech codec up to
the highest codec mode requested by the peer
RNC.

In the downlink, the permitted highest AMR/AMR-WB speech codec mode can be
adjusted according to 3.3.1 DL Measurement and Event Reporting. If the mode needs to
be adjusted, the local RNC sends the mode adjustment command to the peer RNC. Based
on its own AMRC/AMRC-WB algorithm, the peer RNC will further decide whether to
perform the mode adjustment.

RAN
Rate Control Description 4 DCCC Algorithm

4-1
4 DCCC Algorithm

The DCCC_SWITCH is used for internal testing. Do not set the DCCC_SWITCH to OFF
th in e commercial network.
The following lists the contents of this chapter:

Rate Reallocation Based on Traffic Volume

Rate Reallocation Based on Throughput
n Based on Link Quality

BE Rate Downsizing and Recovery Based on Basic Congestion

UE State Transition Algorithm
4.1 Rate Reallocation Based on Traffic Volume
on for BE
4.1.1 Traffic Volume Measurement and Event Reporting
is based on the traffic volume measurement. After comparing the
Traffic Volum
cated Traffic Channel (DTCH), (that is, buffer occupancy
tities), to obtain the uplink traffic volume.
In th es), to
obta

Rate Reallocatio

Always Online
This section describes the uplink rate reallocation and downlink rate reallocati
services.
Rate reallocation herein
measurement results with associated thresholds, the RNC can trigger rate reallocation.
e Measurement
In the uplink, the UE measures Dedi
of RLC en
e downlink, the RNC measures the DTCH (that is, buffer occupancy of RLC entiti
in the downlink traffic volume.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)

The traffic volume measurements defined in 3GPP TS 25.331 are applicable only to the uplink.
uawei specific.
Event 4a and E
Time
pen time_after_trigger_4b
r,
refer mechanisms" in 3GPP TS 25.331.
gger is used to get time domain hysteresis, that is, the condition must be
h

vents 4a are reported during the pending_time_after_trigger_4a.
t
In th

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 pending time
pending_time_after_trigger_4b.
Regarding the downlink traffic volume measurements and associated rate reallocation, the design and
implementation are H
vent 4b
Traffic volume threshold of event 4a is defined by the Traffic Measurement Event 4A
threshold parameter.
Traffic volume threshold of event 4b is defined by the Traffic Measurement Event 4B
threshold parameter.
Traffic volume measurement triggering can be associated with both the time-to-trigger (
to trigger 4A and Time to trigger 4B) and the pending time after trigger
ding_time_after_trigger_4a which is set to 4,000 ms and pending_
which is set to 4,000 ms. For the definitions of time-to-trigger and pending time after trigge
to section 14.4.3 "Traffic volume reporting

Time-to-tri
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.
In t e uplink:
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 e

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 even
4b. No more events 4b are reported during the pending_time_after_trigger_4b.
e 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
pending_time_after_trigger_4a.

RAN

4-3
Figure 4-1 Event 4a triggered by an increase in the transport channel traffic volume

Figure 4-2 Event 4b triggered by a decrease in the transport channel traffic volume

In the uplink, the absolute threshold, time-to-trigger of event 4a,
pending_time_after_trigger_4a and those of event 4b are sent by UTRAN through the
MEASUREMENT CONTROL message.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-3 Measurement control

The UE reports the uplink event 4a and event 4b by sending the MEASUREMENT REPORT
message.
Figure 4-4 Measurement report

In the downlink, there are also MEASUREMENT CONTROL message, which carries the
absolute threshold, time-to-trigger of event 4a, time-to-trigger of event 4b,
pending_time_after_trigger_4a, pending_time_after_trigger_4b, and MEASUREMENT
REPORT message, which carries event 4a and event 4b. The difference to those in the uplink
is that they are internal messages in the RNC.
All the preceding parameters associated with events 4a and 4b (Traffic Measurement Event
4A/4B threshold and Time to trigger 4A/4B) are configurable in each direction, that is,
either uplink or downlink.
The Direction parameter has to be set before the setting of the preceding event-related
parameters.

If Direction is set to UPLINK, all the preceding event-related parameters take effect in
the uplink.

If Direction is set to DOWNLINK, all the preceding event-related parameters take effect
in the downlink.
After the parameters are set, the rate reallocation based on traffic volume works in either
direction separately.
4.1.2 UL Rate Reallocation Based on Traffic Volume
In Huawei implementation, two strategies are available for uplink rate reallocation based on
traffic volume. One is RATE_UP_AND_DOWN_ON_DCH and the other is
RATE_UP_ONLY_ON_DCH.
The strategy is set through the DCCC strategy parameter.

RAN

4-5

The RATE_UP_AND_DOWN_ON_DCH strategy means that the rate can be either
downsized or upsized.

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.

The UL DCCC algorithm is unavailable for the BE services whose applied uplink maximum rate is
lower than or equal to the Uplink bit rate threshold for DCCC because DCCC can otherwise bring
processing burden for these BE services.
The prerequisite of UL rate reallocation based on traffic volume described herein is as follows:
- The UL channel power is ample if the rate reallocation based on uplink quality algorithm is
enabled (see 4.3 Rate Reallocation Based on Link Quality).
- The cell is not in the basic congestion state in the uplink (see 4.4.1 UL BE Rate Downsizing and
Recovery Based on UL Basic Congestion). If the cell is in the basic congestion state in the uplink,
only the service whose bit rate is lower than GBR can upsize bit rate to GBR.
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.

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.

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.
In the process of upsizing, if the current rate is lower than the value of Uplink bit rate
threshold for DCCC, the rate is upsized to the value of Uplink bit rate threshold for
DCCC. If the current rate is higher than or equal to the value of Uplink bit rate
threshold for DCCC but lower than MBR, the rate is upsized directly to the MBR.

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 the value of Uplink bit rate threshold for DCCC, the data rate is
downsized to the value of Uplink bit rate threshold for DCCC when downsizing is
triggered.
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.
If the value of Uplink mid bit rate threshold is lower than that of Uplink bit rate
threshold for DCCC, the processing is the same as it is when Uplink Rate increase
adjust level or Uplink Rate decrease adjust level is 2_Rates.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-5 Rate reallocation when both Uplink Rate decrease adjust level and Uplink Rate
increase adjust level are 2_Rates

Figure 4-6 Rate reallocation when both Uplink Rate decrease adjust level and Uplink Rate
increase adjust level are 3_Rates

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
transited to CELL_FACH when the UE state transition algorithm is enabled.

RAN

4-7

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

The highest value that the rate can be upsized to is MBR.

When Uplink Rate increase adjust level is 2_Rates, if the current rate is lower than
Uplink bit rate threshold for DCCC, the rate is upsized to Uplink bit rate threshold
for DCCC. If the current rate is higher than or equal to Uplink bit rate threshold for
DCCC but lower than MBR, the rate is upsized directly to the MBR

When Uplink Rate increase adjust level is 3_Rates:
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 is 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
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.
Figure 4-7 Rate reallocation when Uplink Rate increase adjust level is 2_Rates

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-8 Rate reallocation when Uplink Rate increase adjust level is 3_Rates

4.1.3 DL Rate Reallocation Based on Traffic Volume
In Huawei implementation, two strategies are available for downlink rate reallocation based
on traffic volume. One is RATE_UP_AND_DOWN_ON_DCH and the other is
RATE_UP_ONLY_ON_DCH.

The DL DCCC algorithm is unavailable for the BE services whose applied downlink maximum rate
is lower than or equal to the Downlink bit rate threshold for DCCC because DCCC can otherwise
bring processing burden for these BE services.
The prerequisites of DL rate reallocation based on traffic volume described herein are as follows:
- The DL channel power is ample if the rate reallocation based on downlink quality algorithm is
enabled (event F is reported, see 4.3.2 Downlink Quality Measurement and Event Reporting).
- The cell is not in the basic congestion state in the downlink (see 4.4.2 DL BE Rate Downsizing and
Recovery Based on DL Basic Congestion).
If the cell is in the basic congestion state in the downlink, only the service whose bit rate is lower
than GBR can upsize bit rate to GBR.
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.

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.

When Downlink Rate decrease adjust level is 2_Rates, the rate is downsized directly to
the value of Downlink bit rate threshold for DCCC, or the rate is upsized directly to
the MBR from the value of Downlink bit rate threshold for DCCC.
In the process of upsizing, if the current rate is lower than Downlink bit rate threshold
for DCCC, the rate is upsized to the value of Downlink bit rate threshold for DCCC.

RAN

4-9
If the current rate is higher than or equal to the value of Downlink bit rate threshold for
DCCC but lower than MBR, the rate is upsized directly to the MBR

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 Downlink bit rate threshold for DCCC, the rate is downsized to the
value of Downlink bit rate threshold for DCCC when downsizing is triggered.
In the process of upsizing:
If the current rate is lower than Downlink bit rate threshold for DCCC, the data
rate is upsized to the value of Downlink bit rate threshold for DCCC.
If the current rate equals the value of Downlink bit rate threshold for DCCC, the
data rate is upsized to the value of Downlink mid bit rate threshold and then to the
MBR.
If the current rate is lower than MBR and higher than Downlink bit rate threshold
for DCCC, the rate is upsized to MBR when upsizing is triggered.
If the value of Downlink mid bit rate threshold is lower than that of Downlink bit rate
threshold for DCCC, the processing is the same as it is when Downlink Rate increase
adjust level or Downlink Rate decrease adjust level is 2_Rates.
Figure 4-9 Rate reallocation when both Downlink Rate decrease adjust level and Downlink
Rate increase adjust level are 2_Rates

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-10 Rate reallocation when both Downlink Rate decrease adjust level and Downlink
Rate increase adjust level are 3_Rates

Principles of RATE_UP_ONLY_ON_DCH

Rate downsizing is not performed. If a UE is in low activity, the state of the UE is
directly transited to CELL_FACH when the UE state transition algorithm is enabled.

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

The highest value that the rate can be upsized to is MBR.

When Downlink Rate increase adjust level is 2_Rates, if the current rate is lower than
Downlink bit rate threshold for DCCC, the rate is upsized to the value of Downlink
bit rate threshold for DCCC. If the current rate is higher than or equal to Downlink bit
rate threshold for DCCC but lower than MBR, the rate is upsized directly to the MBR

When Downlink Rate increase adjust level is 3_Rates:
If the current rate is lower than the value of Downlink bit rate threshold for DCCC,
the data rate is upsized to the value of Downlink bit rate threshold for DCCC.
If the current rate is the value of Downlink bit rate threshold for DCCC, the data
rate is upsized to the value of Downlink mid bit rate threshold and then to the
MBR.
If the current rate is lower than MBR and higher than the value of Downlink bit rate
If the value of Downlink mid bit rate threshold is lower than that of Downlink bit rate
threshold for DCCC, the rate is directly upsized to the highest rate, which is the same
as the processing applicable when Downlink Rate increase adjust level or Downlink
Rate decrease adjust level is set to 2_Rates.

RAN

4-11
Figure 4-11 Rate reallocation when Downlink Rate increase adjust level is 3_Rates

Figure 4-12 Rate reallocation when Downlink Rate increase adjust level is 2_Rates

4.1.4 Signaling Procedure of Rate Reallocation Based on Traffic
Volume
This section describes how the rate reallocation based on traffic volume is implemented
through the signaling over the Uu and Iub interfaces.
Signaling Procedure of UL Rate Reallocation
Figure 4-13 and 0 show the signaling procedures of UL rate reallocation based on the traffic
volume.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-13 Signaling procedure of UL rate downsizing based on traffic volume

Figure 4-14 Signaling procedure of UL rate upsizing based on traffic volume

Signaling Procedure of DL Rate Reallocation
Figure 4-15 and Figure 4-16 show the signaling procedures of DL rate reallocation based on
the traffic volume.

RAN

4-13
Figure 4-15 Signaling procedure of DL rate downsizing based on traffic volume

Figure 4-16 Signaling procedure of DL rate upsizing based on traffic volume

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
4.2 Rate Reallocation Based on Throughput
This section describes how the DCCC of BE services is implemented through rate
reallocation based on the throughput.
4.2.1 Throughput Measurement and Event Reporting
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.
Throughput Measurement
In each measurement period, 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.

For E-DCH service, the throughput measurement period is set to 300 ms.
For DCH service, the throughput measurement period is set to 1,000 ms.
Event 4a and Event 4b

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.
Mechanism
Figure 4-17 shows the mechanism of throughput measurement and reporting of events 4a and
4b.
Figure 4-17 Mechanism of throughput measurement and reporting of events 4a and 4b

The mechanism of reporting throughput-related events 4a and 4b is as follows:
A specified group of adjustment rate and the associated throughput threshold has to be
configured:
{(R
1
, TR
1
), ... (R
i
, TR
i
), ... (R
N
, TR
N
)}

RAN

4-15
Where:

For E-DCH services,
The first figure in each pair of parentheses is the HSUPA adjustment rate which is set
through the HSUPA UpLink rate adjust set parameter.
The second figure is the associated throughput threshold of this HSUPA adjustment
rate.
TR
i
= R
i
x threshold rate ratio
The threshold rate ratio is set as the following table.
The R
N
is the highest rate in the set defined by the HSUPA UpLink rate adjust set
parameter.
Assume that the maximum bit rate of a service assigned through an RAB
ASSIGNMENT REQUEST message is MaxRate. Then, MaxRateThreshold = MaxRate
MaxRate
.
If R
t
MaxRate R
t+1
(1 t N1), the HSUPA adjustment rate and associated
throughput threshold set is: {(R
1
, TR
1
), ..., (R
i
, TR
i
), ..., (R
t
, TR
t
)}.
If MaxRate R
N
, the HSUPA adjustment rate and associated throughput threshold set
is: {(R
1
, TR
1
), ..., (R
i
, TR
i
), ..., (R
N
, TR
N
)}.
Rate Threshold Rate Ratio
8Kbps 90%
16Kbps 90%
32Kbps 90%
64Kbps 90%
128Kbps 80%
144Kbps 80%
256Kbps 80%
384Kbps 75%
608Kbps 75%
1450Kbps 75%
2048Kbps 75%
2890Kbps 70%
5760Kbps 70%

For DCH services, the rate adjustment set is {rate threshold for DCCC, middle rate,
maximum rate} permanently.
The rate threshold for DCCC is defined by the Uplink/Downlink bit rate threshold
for DCCC parameter.
The middle rate is defined by the Uplink/Downlink mid bite rate calculate method
and Uplink/Downlink mid bit rate threshold parameters. For detailed information,
see 4.1.2 UL Rate Reallocation Based on Traffic Volume and 4.1.3 DL Rate
Reallocation Based on Traffic Volume.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
The maximum rate is the MBR.
During each measurement 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 two consecutive time periods
and the Tpend_4a timer, which is set to 16 consecutive time periods after event 4a is
triggered, is not started, event 4a is reported and the Tpend_4a timer is started.

If the AvgThroughput is lower than the 4b threshold for two consecutive time periods
and the Tpend_4b timer, which is set to 16 consecutive time periods after event 4a is
triggered, is not started, event 4b is reported and the Tpend_4b timer is started.

For E-DCH service, the throughput measurement period is set to 300 ms.
For DCH service, the throughput measurement period is set to 1,000 ms.
Thresholds
In the aspect of DCCC for HSUPA,

The 4a threshold is the throughput threshold associated with the current HSUPA
adjustment rate, that is, TR
t
.
TR
t
= R
t
t

The 4b threshold is the throughput threshold associated with the previous rate, that is,
TR
t1
.
TR
t1
= R
t1
t1
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).
In the aspect of DCCC for DCH services, the 4b threshold is calculated as follows:
TR
t-1
= R
t-1
t-1
where:

R
t-1
is the previous rate in the rate adjustment set.

Threshold rate ratio
t-1
is equal to 90%.
4.2.2 Rate Reallocation Action Based on Throughput
Two strategies are available for E-DCH in Huawei implementation. One is
RATE_UP_AND_DOWN, and the other is RATE_UP_ONLY. For DCH, only rate
downsizing is applicable.
Rate Reallocation on E-DCH
The strategy is set through the HSUPA DCCC strategy parameter. 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.
Principles of RATE_UP_AND_DOWN_ON_EDCH

RAN

4-17

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.
The process is as follows:
Assume that R
t
is the current configured rate. If AvgThroughput > R
t
x threshold rate
ratio
t
for two consecutive measurement periods and the Tpend_4a timer after trigger 4a
is not started, event 4a is triggered, and R
t
is upsized to R
t+1
if R
t
is not the maximum
rate.

After event 4b is reported, the reported throughput is compared with the threshold rates
that are associated with the HSUPA adjustment rates, to find out the threshold rates
which are higher than the reported throughput. Then, the RB is reconfigured to the
HSUPA adjustment bit rate, which is associated with the minimum threshold rate among
those which are higher than the reported throughput.
Assume that R
t
is the current configured rate. If AvgThroughput < R
t1
x threshold rate
ratio
t1
for two consecutive measurement periods and the Tpend_4b timer after trigger 4b
is not started, then event 4b is triggered. If the measured average throughput is between
TR
i1
and TR
i
, the current configured rate is downsized to a proper rate R
i
. Figure 4-18
shows the relation.
Figure 4-18 Average throughput between TR and TR
i1 i

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 4.5 UE State Transition Algorithm.
Rate Downsizing on DCH
After event 4b is reported, the reported throughput is compared with the threshold rates that
are associated with the HSUPA adjustment rates, to find out the threshold rates which are
higher than the reported throughput. Then, the RB is reconfigured to the HSUPA adjustment
bit rate, which is associated with the minimum threshold rate among those which are higher
than the reported throughput. For detailed information, see Figure 4-18.
The above procedure is for both uplink and downlink.
4.2.3 Signaling Procedure of Rate Reallocation Based on
Throughput
This section describes how the rate reallocation based on throughput is implemented through
the signaling over the Uu and Iub interfaces.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-19 and Figure 4-20 show the signaling procedures of rate reallocation based on
throughput.
Figure 4-19 Signaling procedure of rate upsizing based on throughput

Figure 4-20 Signaling procedure of rate downsizing based on throughput

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.

RAN

4-19
4.3 Rate Reallocation Based on Link Quality
This section describes how to make rate reallocation for BE services according to the link
quality.
4.3.1 Uplink Quality Measurement and Event Reporting
This section describes the uplink quality evaluation factors and corresponding events.
Uplink Quality Measurement
There are two measurement quantities related to the uplink quality, uplink transmit power of
the UE and uplink BLER.

The measurements 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.
Higher Layer Filtering
Before the measurement results of uplink transmitted power are reported, higher layer
filtering has to be performed at the UE.
The basic principle is the same as Higher Layer Filtering in the downlink, while the difference
is that the filter coefficient in the uplink is 19.

For the detailed information about Higher Layer Filtering in the downlink, see 4.3.2 Downlink Quality
Measurement and Event Reporting
Event 6A and 6B
In the uplink, the measurement of UE transmit power can trigger event 6A or event 6B.

If the transmit power of the UE is above a certain threshold for a period of time, event
6A is triggered.
Event 6A involves two thresholds: 6A1 and 6A2. For detailed information, see 3.2.1 UL
Measurement and Event Reporting. In RAN10.0, the trigger time of event 6A1 is set to
640 ms, and the trigger time of event 6A2 is set to 1,280 ms.

If the transmit power of the UE is below a certain threshold for a period of time, event
6B is triggered.
Event 6B involves two thresholds: 6B1 and 6B2. For detailed information, see 3.2.1 UL
Measurement and Event Reporting. In RAN10.0, the trigger time of event 6B1 is set to
2,560 ms, and the trigger time of event 6B2 is set to 1,280 ms.
Event 6D
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.
For BE services the hysteresis is set to 240 ms.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Event 5A
The uplink BLER reflects the uplink quality. The change in the BLER is indicated by event
5A.
The RNC defines a sliding window of a certain length. If the number of error blocks during
the sliding window is greater than or equal to a predefined number, event 5A is triggered.
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.
Figure 4-21 shows the triggering and reporting mechanism of event 5A.
Figure 4-21 Event 5A mechanism

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.
4.3.2 Downlink Quality Measurement and Event Reporting
This section describes the downlink quality evaluation factors and corresponding events.
Downlink Quality Measurement
There are two measurement quantities related to the downlink quality, Transmitted Code
Power (TCP), and RLC PDU retransmission rate.

RAN

4-21

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.
Higher Layer Filtering
Before the measurement results for TCP are reported, they need to undergo higher layer
filtering at the NodeB.
The DL code TX power meas filter coef parameter indicates how the filtering of
measurement values is performed. The RNC sends this parameter to the NodeB through the
DEDICATED MEASUREMENT INITION REQUEST message.
The averaging is calculated according to the following formula:

where:

is the updated filtered measurement result.

is the previous filtered measurement result.

is the latest received measurement result of DL transmitted code power from
physical layer measurements. The unit used for M
n
is the same as that for F
n
.

, where k is defined by the DL code TX power meas filter coef parameter.
To initialize the averaging filter, F
0
is set to M
1
when the first measurement result from the
physical layer measurement is received.
Event E
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.

Event Eb means that the transmit power falls below measurement threshold 2.
For different services, there are different Ea and Eb thresholds. For the sake of simplicity of
parameters, a set of relative thresholds (Event Ea relative threshold and Event Eb relative
threshold) is defined for all BE services, and absolute Ea and Eb thresholds are calculated by
the following formula:

Where:

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 maximum DL power is configured through RL Max DL TX power that
is specific to the DPDCHs.

Maximum DL power is defined through the RL Max DL TX power parameter that is
specific for the DPDCHs.
Figure 4-22 shows the reporting mechanism of event E.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-22 Event E reporting mechanism

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.
Before event E measurement event evaluation and reporting, DL code TX power meas filter
coef is used to perform higher layer filtering.
Event A
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).
RLC retransmission rate is reported to layer 3 by layer 2. Figure 4-23 shows the RLC
retransmission rate.

RAN

4-23
Figure 4-23 RLC retransmission rate

The RLC retransmission process is as follows:
1. Set up a statistic window according to the period of monitoring PDU retransmission
which is set to 1,000 ms, during which RLC retransmission rate is calculated.
2. Filter the RLC retransmission rate by the filter coefficient for RLC retransmission
measurement which is set to 1. The filter coefficient for RLC retransmission
measurement is similar to the parameter DL code TX power meas filter coef, except
that here M
n
is the latest RLC retransmission rate.
For detailed information about DL code TX power meas filter coef, see Higher Layer
Filtering.
3. Check whether the RLC retransmission rate is above the Event A threshold. If it is
above the threshold for a period of time (the period of monitoring PDU retransmission x
2), RLC retransmission event A is triggered and the RLC retransmission rate is reported.
RLC retransmission event A is defined as Huawei specific and it is not a 3GPP standard
event.
Each time a retransmission event A is triggered, RLC retransmission rate calculation needs to
be suspended for a period of time (the period of monitoring PDU retransmission x 1), 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.
Event F
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 measurement thresholds are various for different current rates and upsizing target rates
which are triggered by event 4a reports. For the sake of simplicity, measurement threshold 1

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
equals the measurement threshold 2 in programming, and the threshold is calculated
according to the following formula:

where:

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.

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.

is the event F reporting power margin which is set to 1 dB.

Event Ea relative threshold is used to protect triggering event report Ea after upsizing.

is the maximum DL power of target rate, that is, the maximum configured power of
the target rate.

is the relative transmit power offset between pilot fields of the DPCCH and
DPDCHs.
Figure 4-24 shows the reporting mechanism of event F.
Figure 4-24 Event F reporting mechanism

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.
Before event F measurement event evaluation and reporting, DL code TX power meas filter
coef is used.

RAN

4-25

The event F threshold cannot be higher than the Ea threshold. Otherwise, this threshold is set to Ea
threshold.
4.3.3 Rate Rea
rforms rate
s are met.
r
trol
.
Rate Downsiz
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
llocation Action Based on Uplink Quality
After events indicating unsatisfactory uplink quality are reported, the RNC pe
downsizing. The RNC restores the service rate when the associated condition
In RAN10.0, rate downsizing is one of the actions of the link stability control algorithm fo
BE services. The RNC takes the action described herein only when the link stability con
algorithm triggers the rate downsizing. For detailed information about the link stability
control algorithm for BE services, see 5.3 Link Stability Control Algorithms for BE Services
ing
For 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.

The Uplink mid bit rate threshold parameter is the same as that described in 4.1 Rate Reallocation
Traffic Volume. Based on
k quality is equal to the RB rate closest to the highest rate divided by two.
Figu
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 uplin
The bit rate is calculated in the RNC.
re 4-25 Rate downsizing based on uplink quality in the case of 3-rate adjustment

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Rate Upsizing
Figure 4-26 shows the process of rate upsizing based on uplink quality.
Figure 4-26 Rate upsizing process based on uplink quality

If the RNC receives an event 6B2 but no event 6A2, rate upsizing based on
affic-volume-related event 4a is allowed.
-related event 4a is
ed and rate upsizing
is still prohibited.
upsizing process, see 4.1.2 UL

performs rate
et.
gorithm for
ility control
tability
for BE Services.
Rate Downsiz
es.

If the current rate is MBR, the rate is downsized to the value of Downlink mid bit rate
link full coverage bit rate and lower than MBR,
the rate is downsized to the value of Downlink full coverage bit rate.
tr
If the RNC receives an event 6A2, rate upsizing based on traffic-volume
not allowed. If the RNC receives an event 6B1, rate downsizing is stopp
For detailed information about event 4a reporting and the rate
Rate Reallocation Based on Traffic Volume.
4.3.4 Rate Reallocation Action Based on Downlink Quality
After events indicating unsatisfactory downlink quality are reported, the RNC
downsizing. The RNC restores the service rate when the associated conditions are m
In RAN10.0, rate downsizing is one of the actions of the link stability control al
BE services. The RNC takes the action described herein only when the link stab
algorithm triggers the rate downsizing. For detailed information about the link s
control algorithm for BE services, see 5.3 Link Stability Control Algorithms
ing
For rate downsizing based on downlink quality, only the 3-rate downsizing appli
threshold.

If the current rate is higher than Down

RAN

4-27

The Downlink mid bit rate threshold parameter is the same as that described in 4.1 Rate
the traffic
ate for the

The Downlink mid bit rate threshold is the middle bit rate threshold for adjustment of
volume in the downlink. When Downlink Rate adjust level is 2_Rates, the middle bit r
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.
Figure 4-27 Rate downsizing based on downlink quality in the case of 3-rate adjustment

The rate upsizing process requires checking whether the current DL channel power is
Rate upsizing is allowed only when the DL channel power is ample. Figure 4-28
process of rate upsizing based on downlink quality.
Rate Upsizing
ample.
shows the

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
igure 4-28 Rate upsizing process based on downlink quality F

If event Fa is reported, it indicates that the DL channel power is ample. Rate upsi
performed if event 4a is reported.
If event Fb is reported, it indicates that the DL channel power is not ample. Th
zing is then
ate upsizing
is prohibited.
ailed information about event 4a reporting and the rate upsizing process, see 4.1.3 DL
4.3.5 Signal
Downlink Q
erfaces.
ows the signaling procedure of rate downsizing based on the downlink quality.
en r
For det
Rate Reallocation Based on Traffic Volume.
ing Procedure of Rate Reallocation Based on
uality
This section describes how the rate reallocation based on downlink quality is implemented
through the signaling over the Uu and Iub int
Signaling Procedure of Rate Downsizing
Figure 4-29 sh

RAN

4-29
Figure 4-29 Signaling procedure of rate downsizing based on downlink quality

Signaling Procedure of Rate Upsizing
For detailed information about the signaling procedure of rate upsizing, see 4.1.4 Signaling
Procedure of Rate Reallocation Based on Traffic Volume.
4.4 BE Rate Downsizing and Recovery Based on Basic
Congestion
BE rate downsizing is one of the actions implemented by Load Reshuffling (LDR), which
uses the signaling interaction on the Uu interface to reconfigure the bandwidth.
When the cell enters the basic congestion state, the LDR algorithm triggers the corresponding
actions to reduce the cell load. For detailed information, see Load Reshuffling in Load
Control.
When the cell enters the basic congestion state, the maximum target rate is GBR for BE RAB.
When the cell exits the basic congestion state, the LDR algorithm no longer does any action
to the UEs in the cell. The rate of the service is upsized or downsized according to other
DCCC algorithms.
4.4.1 UL BE Rate Downsizing and Recovery Based on UL Basic
Congestion
When a cell enters the basic congestion state in the uplink and BE rate downsizing is triggered,
the bandwidth of the selected RABs is reduced to the target bit rate. For DCH RAB and
HSUPA RAB, the target rates of the rate downsizing are different.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)

If the selected RAB is a DCH RAB, only 3-rate downsizing applies.
If the current rate is MBR, the rate is downsized to Uplink mid bit rate threshold.
If the current rate is higher than GBR but lower than MBR, the rate is downsized to
GBR.

The Uplink mid bit rate threshold parameter is the same as that described in 4.1 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 is
equal to the RB rate closest to the highest rate divided by two. The bit rate is calculated in the RNC.

If the selected RAB is an HSUPA RAB, the target rate is determined according to the
configured HSUPA adjustment rate in order (For detailed information about the HSUPA
UpLink rate adjust set parameter, see 4.2.1 Throughput Measurement and Event
Reporting). The target rate has to be greater than or equal to GBR.
Figure 4-30 shows an example of UL BE rate downsizing and upsizing (DCH RAB). In this
example, the Uplink Rate decrease adjust level parameter is set to 3_Rates, rate downsizing
is triggered by UL basic congestion, and rate upsizing is triggered when basic congestion is
removed. In addition, the current UL rate can be the initial rate, middle rate, or maximum bit
rate.

When the current UL rate is the maximum bit rate, the current rate is downsized to the middle rate if a
UL basic congestion report is received, and the rate is then downsized to the GBR if a second UL basic
congestion report is received.
Figure 4-30 UL BE rate downsizing and upsizing based on UL basic congestion (2)

RAN

4-31
4.4.2 DL BE Rate Downsizing and Recovery Based on DL Basic
Congestion
When a cell enters the basic congestion state in the downlink and BE rate downsizing is
triggered, the bandwidth of the selected RABs is reduced.
The bit rate of the selected services is downsized to the associated GBR. (The user GBRs can
be set through the SET USERGBR command.)
Only 3-rate downsizing applies.

If the current rate is MBR, the rate is downsized to Downlink mid bit rate threshold.

If the current rate is higher than GBR and lower than MBR, the rate is downsized to
GBR.

The Downlink mid bit rate threshold parameter is the same as that described in 4.1 Rate
The Downlink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic
volume in the downlink. When Downlink Rate decrease adjust level is 2_Rates, the middle bit rate
is equal to the RB rate closest to the highest rate divided by two. The bit rate is calculated in the
RNC.
Figure 4-31 shows an example of DL BE rate downsizing and upsizing. In this example, rate
downsizing is triggered by DL basic congestion, and rate upsizing is triggered when basic
congestion is removed. In addition, the current DL rate can be the initial rate, middle rate, or
maximum bit rate.

When the current DL rate is the maximum bit rate, the current rate is downsized to the middle rate if a
DL basic congestion report is received, and the rate is then downsized to the GBR if a second DL basic
congestion report is received.
Figure 4-31 DL BE rate downsizing and upsizing based on DL basic congestion (2)

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
4.4.3 Signaling Procedure of Rate Downsizing
This section describes how BE rate reallocation based on basic congestion uses the Uu and
Iub signaling to reconfigure the bandwidth.
UL Signaling Procedure
Figure 4-32 shows the signaling procedure of UL rate downsizing based on the UL cell basic
congestion.
Figure 4-32 Signaling procedure of UL rate downsizing based on UL basic congestion

DL Signaling Procedure
Figure 4-33 shows the signaling procedure of DL rate downsizing based on the DL cell basic
congestion.

RAN

4-33
Figure 4-33 Signaling procedure of DL rate downsizing based on DL basic congestion

4.4.4 Rate Upsizing Failure and Penalty
Rate upsizing may fail due to different reasons, such as lack of Iub resources or cell resources,
NodeB exception or UE exception, and so on. When rate upsizing failure happens frequently,
rate upsizing attempts have to be prohibited for a period of time.
At the RNC, the following three factors are used to control the rate upsizing when rate
upsizing failure happens:

the threshold of number of rate upsizing failures which is set to 4

the length of the DCCC rate upsizing failure monitoring timer which is set to 60 s

the length of the DCCC rate upsizing failure penalty timer which is set to 30 s
Figure 4-34 shows the penalty on rate upsizing failure in case of 2_Rates adjustment.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Figure 4-34 Rate upsizing failure penalty in case of 2_Rates adjustment

In Figure 4-34, the symbols denote as follows:

1-8: 4A measurement reports from UE

S1: cell in the normal state

S2: cell in the congestion state

S3: cell state recovered
The procedure of rate upsizing failure penalty is as follows:
1. The DCCC rate upsizing failure monitoring timer whose length is 60 s, is started at the
first failure of the rate upsizing procedure, and the upsizing failure counter is increased
each time rate upsizing fails.
2. The rate upsizing failure counter determines whether to start the DCCC rate upsizing
failure penalty timer.
If the number of rate upsizing failures equals or exceeds the threshold of rate upsizing
failure times which is set to 4, the DCCC rate upsizing failure penalty timer which
length is 30s is started. No rate upsizing attempt is allowed before this penalty timer
expires.
When the DCCC rate upsizing failure monitoring timer expires, if the number of rate
upsizing failures is less than the threshold of rate upsizing failure times which is set
to 4, go to 1.
3. After the DCCC rate upsizing failure penalty timer expires, rate upsizing attempts are
allowed. When a rate upsizing attempt happens, go to 1 if the cell is in the congestion
state.

RAN

4-35

The upsizing failure counter always works, instead of being valid only during the DCCC rate
upsizing failure monitoring time. The DCCC rate upsizing failure monitoring timers for uplink and
downlink, which have the same length, work independently.
If the number of rate upsizing failures equals or exceeds the threshold of rate upsizing failure times,
the DCCC rate upsizing failure penalty timer is started, and the DCCC rate up fail monitor timer is
stopped.
When the cell is in basic congestion state, the services, whose bit rate is lower than GBR, are
allowed to upsize rates. The success of the rate upsizing, however, depends on the related resources
being sufficient.
4.5 UE State Transition Algorithm
After the RRC connection is set up, the RNC observes UE activity and uses the UE state
transition algorithm to transit the UE state.
Figure 4-35 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. Figure 4-35 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.
Figure 4-35 UE state transition and status of the RRC connection

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.
At the RNC, the following parameters are available to control the function of UE state
transition:

PS_BE_STATE_TRANS_SWITCH

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)

PS_NON_BE_STATE_TRANS_SWITCH

HSDPA_STATE_TRANS_SWITCH

HSUPA_STATE_TRANS_SWITCH
If the above state transition switches are set to on, and:

The DCCC_SWITCH is on and DCCC strategy is
RATE_UP_AND_DOWN_ON_DCH, the UE state transition algorithm starts to work if
the uplink and downlink bit rate equals or falls below the Uplink/Downlink bit rate
threshold for DCCC.

The DCCC_SWITCH is on and DCCC strategy is RATE_UP_ONLY_ON_DCH, the
UE state transition algorithm always works.

The DCCC_SWITCH is off, the UE state transition algorithm always works.
The following types of UE state transition are described:

UE State Transition From CELL_DCH to CELL_FACH

UE State Transition From CELL_FACH to CELL_PCH

UE State Transition From CELL_PCH to URA_PCH

UE State Transition From CELL_PCH or URA_PCH to CELL_FACH

UE State Transition From CELL_FACH to CELL_DCH

For UE state transition, if the corresponding parameters for the PS' user inactive detecting timer in the
SET PSINACTTIMER command are set too small, the RRC connection is released before state
transition.
4.5.1 UE State Transition From CELL_DCH to CELL_FACH
Figure 4-36 shows the principles of UE state transition from CELL_DCH to CELL_FACH.
Figure 4-36 UE state transition from CELL_DCH to CELL_FACH

RAN

4-37
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.
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) x state transition traffic redundancy
coefficient]
Where:

CELL_DCH to CELL_FACH transition time, time to trigger, and pending time after
trigger are set through the parameters listed in Table 4-1.

State transition traffic redundancy coefficient is used to avoid detecting UE in
low-activity state incorrectly due to the loss of measurement reports. The value of this
coefficient is set to 80%.
Table 4-1 Parameters used for UE state transition from CELL_DCH to CELL_FACH
Service
Type
CELL_DCH to
CELL_FACH
Transition Time
4b Event
Threshold
Time to Trigger Pending Time After
Trigger
BE service
on the DCH
BE DCH to FACH
transition timer
BE DCH to
F/RACH or
F/RACH to PCH
4b threshold
BE DCH to
F/RACH 4b time to
trigger
BE DCH to F/RACH
4b Pending Time after
trigger
BE service
on the
HS-DSCH
BE HS-DSCH to
FACH transition
timer
BE HS-DSCH to
FACH 4b threshold
BE HS-DSCH to
FACH 4b time to
trigger
BE HS-DSCH to
FACH 4b Pending
Time after trigger
Real-time
PS service
Realtime Traff
DCH or HSPA to
FACH transition
timer
Realtime Traff
DCH or HSPA to
FACH 4b threshold
Realtime Traff
DCH or HSPA to
FACH 4b time to
trigger
Realtime Traff DCH or
HSPA to FACH 4b
pending time
BE service
on the
E-DCH
E-DCH to FACH
State
Transformation
Timer
E-DCH to FACH
4b Threshold
E-DCH to FACH
4b Period Amount
To Trigger x 300
ms
E-DCH to FACH 4b
Pending Period
Amount After Trigger x
300 ms

The state transition from E-DCH to FACH is similar to the state transition from CELL-DCH
to CELL-FACH. The difference is that the measurement quantity of the 4b event is the

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
throughput value. The throughput measurement period is set to 300 ms. the threshold
configuration value of the associated event 4b is also the throughput value which is indicated
by the E-DCH to FACH 4b Threshold parameter.
UE state transition, however, 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. 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.

For BE services on the HS-DSCH or E-DCH,
If PS_BE_STATE_TRANS_SWITCH or
HSDPA_STATE_TRANS_SWITCH/HSUPA_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.

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.

For the BE services on the uplink DCH and downlink HS-DSCH, configure time to trigger, pending
time after trigger, and 4b threshold respectively for the uplink and downlink.
For the BE and real-time services on the uplink and downlink DCH, configure time to trigger,
pending time after trigger, and 4b threshold by using the same parameters for both the uplink and
downlink.
For the real-time services on the uplink DCH and downlink HS-DSCH, configure time to trigger,
pending time after trigger, and 4b threshold by using the same parameters for both the uplink and
downlink.
For the BE and real-time services on the uplink E-DCH and downlink DCH or HS-DSCH, configure
time to trigger, pending time after trigger, and 4b threshold respectively for the uplink and downlink.
4.5.2 UE State Transition From CELL_FACH to CELL_PCH
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.
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.
The CELL_FACH to CELL_PCH transition threshold is the rounded-down value of the
following formula:

RAN

4-39
CELL_FACH to CELL_PCH transition threshold = [CELL_FACH to CELL_PCH transition
time / (time to trigger + pending time after trigger) x State transition traffic redundancy
coefficient]
Table 4-2 lists the parameters used to calculate the threshold for UE state transition from
CELL_FACH to CELL_PCH.
Table 4-2 Parameters used for UE state transition from CELL_FACH to CELL_PCH
Service
Type
CELL_FACH to
CELL_PCH
Transition Timer
4b Event
Threshold
Time to
Trigger
Pending Time
After Trigger
BE service
of the PS
domain
BE FACH to PCH
transition timer
BE DCH to
F/RACH or
F/RACH to PCH
4b threshold
BE FACH
to PCH 4b
time to
trigger
BE FACH to
PCH 4b
Pending Time
after trigger

4.5.3 UE State Transition From CELL_PCH to URA_PCH
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 (Cell reselection 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
(Cell reselection counter). In this case, the RNC initiates the state transition when the UE
sends the CELL UPDATE message again.

The state transition from CELL_PCH to URA_PCH involves the transient state CELL_FACH, in which
some necessary signaling interaction is performed.
4.5.4 UE State Transition From CELL_PCH or URA_PCH to
CELL_FACH
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.
4.5.5 UE State Transition From CELL_FACH to CELL_DCH
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. The 4a threshold
parameters are list in Table 4-3.

4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
Table 4-3 Parameters used for UE state transition from CELL_FACH to CELL_DCH
Service
Type
4a Event
Threshold
Target Rate
BE service on
the DCH
BE F/RACH to
DCH 4a
threshold

For the uplink, the target rate equals the smaller one
of MBR and Uplink bit rate threshold for DCCC

For the downlink, the target rate equals the smaller
one of MBR and Downlink bit rate threshold for
DCCC
BE service on
the
HS-DSCH
BE FACH to
HS-DSCH 4a
threshold

For the uplink:
- The target rate equals the smaller one of MBR and
Uplink bit rate threshold for DCCC for the
transition from FACH to DCH (with HS-DSCH)
- The target rate equals the minimum value among the
configured HSUPA UpLink rate adjust set for the
transition from FACH to UPA (with HS-DSCH)

For the downlink, the target rate equals the MBR
Real-time PS
service
Realtime Traff
FACH to DCH
or HSPA 4a
threshold
MBR
BE service on
the E-DCH
FACH to
E-DCH 4a
Threshold

For the uplink:
- The target rate equals the minimum value among the
configured HSUPA Uplink rate adjust set when
HSUPA_DCCC_SWITCH is set to ON
- The target rate equals the MBR when
HSUPA_DCCC_SWITCH is set to OFF

For the downlink:
- The target rate equals the smaller one of MBR and
Downlink bit rate threshold for DCCC when the
downlink channel is DCH
- The target rate equals the MBR when the downlink
channel is HS-DSCH

4.6 Always Online
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 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.

RAN

4-41
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. In RAN10.0,
T1 and T2 are both set to 20 s for all the above services.
Figure 4-37 shows the PDCP release process.
Figure 4-37 PDCP release process


4 DCCC Algorithm
RAN

Issue 01 (2008-05-30)
1. When the PDCP entity of a service is set up, timer T1 is started.
2. 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.
3. 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".
4. When the CN receives the message, it initiates the release procedure.
The CN reserves the PDP context of the service and the UE does not have to apply for the
PDP context again when it reinitiates the service.

The service release request sent from the PDCP entity may not be processed in time. That is because the
associated processor in the RNC is busy.

RAN
Rate Control Description 5 Link Stability Control Algorithms

5-1
5 Link Stability Control Algorithms
Tt following lists the contents of this chapter: he

Link Stability Control Algorithms for AMR/AMR-WB Speech Services

Link Stability Control Algorithms for VP Services
5.1 Link S
Speech Se
The link stability control algorithm for AMR/AMR-WB speech services is used to trigger rate
shold,
te
over, and inter-RAT handover. They are controlled by
individual switches but are performed in a fixed sequence of rate downsizing, inter-frequency
speech services, the rate
orithm as described in 3.2.2
ion.
5.1.1 Uplink
Measurement Events and Reports
detailed information about the descriptions and parameters of the related measurement
en
Related Actions

h
M
AM
sed on Uplink Traffic AMR/WAMR is set to
YES, inter-frequency handover is performed.

Link Stability Control Algorithms for BE Services
tability Control Algorithms for AMR/AMR-WB
rvices
downsizing, inter-frequency handover, or inter-RAT handover when the uplink transmit power
of the UE or downlink transmitted code power of the NodeB exceeds the associated thre
so as to guarantee the stability of links.
The actions of the link stability control algorithm for AMR/AMR-WB speech services are ra
downsizing, inter-frequency hand
handover, and then inter-RAT handover. For AMR/AMR-WB
downsizing refers to the link-quality-based rate downsizing alg
UL AMRC/AMRC-WB Act
Link Stability Control Algorithm
For
ev ts, see 3.2.1 UL Measurement and Event Reporting.
W en rate downsizing is configured, that is, when link-quality-based
A RC/AMRC-WB algorithm is enabled, if a 6A1 or 6D report is received or the UL
RC timer (described in 3.2.2 UL AMRC/AMRC-WB Action) is expired, and if the
current rate is GBR, then
If InterFreq Handover Switch ba

RAN

Issue 01 (2008-05-30)
If InterRat Handover Switch based on Uplink Traffic AMR/WAMR is set to YES
inter-RAT handover is performed.
If both switches are set to YES, the inter-frequen
,
cy and inter-RAT measurement are
about the inter-frequency, inter-RAT handovers and combined
er Inter-RAT
Hand

AM 6A1 or 6D report is received, then
erformed.
,
cy and inter-RAT measurement are
about the inter-frequency, inter-RAT handovers and combined
dover and Inter-RAT
y Control Algorithm
Measurement Eve

nts E1 and E2.
ed

d
detailed information about the descriptions and parameters of the related
started at the same time, and then the RNC decides to perform which type of
handover based on the first report from the UE.
For detailed information
int -frequency and inter-RAT handover, see Inter-Frequency Handover and
over respectively.
When rate downsizing is not configured, that is, when link-quality-based
RC/AMRC-WB algorithm is not enabled, if a
If InterFreq Handover Switch based on Uplink Traffic AMR/WAMR is set to
YES, inter-frequency handover is p
If InterRat Handover Switch based on Uplink Traffic AMR/WAMR is set to YES
inter-RAT handover is performed.
If both switches are set to YES, the inter-frequen
started at the same time, and then the RNC decides to perform which type of
handover based on the first report from the UE.
For detailed information
inter-frequency and inter-RAT handover, see Inter-Frequency Han
Handover respectively.
5.1.2 Downlink Link Stabilit
nts and Reports
When rate downsizing is configured, that is, when link-quality-based
AMRC/AMRC-WB algorithm is enabled, the measurement events are eve
For detailed information about the descriptions and parameters of the relat
measurement events, see 3.3.1 DL Measurement and Event Reporting.
AMRC/AMRC-WB algorithm is not enabled, the measurement events are events Ea an
Eb. For
measurement events, see 4.3.2 Downlink Quality Measurement and Event Reporting.

For AMR service, the trigger time of event E is set to 640 ms, and the reporting period of event E is set
to 4,800 ms.
Related Actions

he average
the E2 threshold
t
AM reshold, then

ed.
to
performed.
If both the switches are set to YES, the combined inter-frequency and inter-RAT
handover is performed.
When rate downsizing is configured (that is, when link-quality-based
AMRC/AMRC-WB algorithm is enabled) and the current rate is GBR, if t
DPDCH transmit power is lower than the E1 threshold and higher than
bu the AMR/AMR-WB status is "Rate-Down" (described in 3.3.2 DL
RC/AMRC-WB Algorithm) or higher than the E1 th
If InterFreq Handover Switch based on Downlink Traffic AMR/WAMR is set to
YES, inter-frequency handover is perform
If InterRat Handover Switch based on Downlink Traffic AMR/WAMR is set
YES, inter-RAT handover is

RAN

5-3
For detailed information about the inter-frequency, inter-RAT handovers and combined
inter-frequency and inter-RAT handover, see Inter-Frequency Handover and Inter-RAT

AMRC/AMRC-WB algorithm is not enabled, if an event Ea report is received, then
If InterFreq Handover Switch based on Downlink Traffic AMR/WAMR is set to
YES, inter-frequency handover is performed.
If InterRat Handover Switch based on Downlink Traffic AMR/WAMR is set to
YES, inter-RAT handover is performed.
If both the switches are set to YES, the combined inter-frequency and inter-RAT
handover is performed.
For detailed information about the inter-frequency, inter-RAT handovers and combined
inter-frequency and inter-RAT handover, see Inter-Frequency Handover and Inter-RAT
5.2 Link Stability Control Algorithms for VP Services
The link stability control algorithm for Video Phone (VP) services is used to trigger
inter-frequency handover when the uplink transmit power of the UE or downlink transmitted
code power of the NodeB exceeds the associated threshold, so as to guarantee the stability of
links.
5.2.1 Uplink Link Stability Control Algorithm
The uplink link stability control algorithm for VP services is related to events 6A1, 6B1, and
6D. For detailed information about the descriptions and threshold parameters of the related
measurement events, see 3.2.1 UL Measurement and Event Reporting.

For VP service, the trigger time of event 6A1 and 6B1 are both set to 640 ms, and the trigger time of
event 6D is set to 240 ms.
Related Actions
When link stability control algorithm for VP services is enabled for uplink (InterFreq
Handover Switch based on Uplink Traffic VP is set to YES), Inter-frequency handover is
performed if an event 6A1 or 6D report is received. For detailed information about the
handover action, see Inter-Frequency Handover.
5.2.2 Downlink Link Stability Control Algorithm
The downlink link stability control algorithm for VP services is related to event Ea and Eb.
For detailed information about the descriptions and threshold parameters of the related
measurement events, see 4.3.2 Downlink Quality Measurement and Event Reporting.

RAN

Issue 01 (2008-05-30)

For VP service, the trigger time of event E is set to 640 ms, and the reporting period of event E is set to
4,800 ms.
Related Actions
When link stability control algorithm for VP services is enabled for downlink (InterFreq
Handover Switch based on Downlink Traffic VP is set to YES), Inter-frequency handover
is performed if an Ea report is received. For details of the handover action, see
Inter-Frequency Handover.
5.3 Link Stability Control Algorithms for BE Services
The link stability control algorithm for Best Effort (BE) services is used to trigger rate
downsizing, inter-frequency handover, or inter-RAT handover so as to guarantee the stability
of links when the uplink or downlink link quality deteriorates, which is indicated by the high
uplink/downlink transmitted power or the high BLER (for uplink)/high RLC retransmission
rate (for downlink).
5.3.1 Uplink Link Stability Control Algorithm
For the uplink link stability control algorithm for BE services, the RNC uses events 6A, 6B,
6D, and 5A. For detailed information, see 4.3.1 Uplink Quality Measurement and Event
Reporting.
Triggering Condition

When Measurement of 6D Switch is ON, event 6D can directly trigger uplink link
stability control action.

When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and
Measurement of 6A1 Switch is ON, event 6A1 can trigger uplink link stability control
action.

When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and
Measurement of 5A Switch is ON, event 5A can trigger uplink link stability control
action.

When Uplink QOS Action Trigger Indicator of Traffic BE is COMBINE, the
combination of event 6A1 and event 5A can trigger uplink link stability control action.
Related Actions
The related procedure is shown in the following figure.

RAN

5-5
Figure 5-1 The related procedure of uplink link stability control algorithm

RAN

Issue 01 (2008-05-30)
Note 1:
The sequence of the link stability control actions is determined by the settings of the
following parameters:

First Uplink QOS Enhancement Action for Traffic BE

Second Uplink QOS Enhancement Action for Traffic BE

Third Uplink QOS Enhancement Action for Traffic BE
Note 2:
A, B, and C in the figure denote the actions as follows:

A denotes rate downsizing.

B denotes inter-frequency handover.

C denotes inter-RAT handover.
Note 3:
The action in the dashed frame can be ignored in a link stability control procedure, if the
last procedure has contained the rate downsizing action and the current rate is above
Uplink Full Coverage Bit Rate.
Note 4:
The timer waiting for uplink rate adjustment of traffic BE is 3,000 ms.

After the uplink link stability control algorithm is triggered, the RNC takes actions on the BE
service in the sequence defined on the LMT. The RNC takes a second action when the
previous action fails. The sequence of the actions is as follows:
1. The action defined by the First Uplink QOS Enhancement Action for Traffic BE
parameter
2. The action defined by the Second Uplink QOS Enhancement Action for Traffic BE
parameter
3. The action defined by the Third Uplink QOS Enhancement Action for Traffic BE
parameter
For detailed information about the rate downsizing action, see 4.3.3 Rate Reallocation Action
Based on Uplink Quality.
For detailed information about the handover actions, see Inter-Frequency Handover and
Inter-RAT Handover.
5.3.2 Downlink Link Stability Control Algorithm
For the downlink link stability control algorithm for BE services, the RNC uses events Ea, Eb,
Fa, Fb, and A. For detailed information, see 4.3.2 Downlink Quality Measurement and Event
Reporting.

RAN

5-7
Triggering Condition
When determining the downlink link stability control, the following two aspects are taken into
account:

One is the current transmit power.
When the transmit power of the downlink channel reaches the maximum power, it is an
indication that the radio link is unstable. The following condition must be fulfilled: The
transmit power of downlink channel exceeds the Ea event threshold (Event Ea relative
threshold).

The other is RLC PDU retransmission rate in AM RLC mode.
When the Srnc Downlink RLC QOS Action Trigger Indicator of Traffic BE is set to
YES, the downlink link stability control algorithm is determined only if the RLC
retransmission rate exceeds the retransmission threshold (Event A threshold).
When the Srnc Downlink RLC QOS Action Trigger Indicator of Traffic BE is set to
NO, related actions are triggered so long as the current transmit power fulfils the criteria.
Related Actions
The related procedure is shown in Figure 5-2.

RAN

Issue 01 (2008-05-30)
Figure 5-2 The related procedure of downlink link stability control algorithm

Note 1:
The sequence of the link stability control actions is determined by the settings of the
following parameters:

First Downlink QOS Enhancement Action for Traffic BE

Second Downlink QOS Enhancement Action for Traffic BE

Third Downlink QOS Enhancement Action for Traffic BE

RAN

5-9
Note 2:
A, B, and C in the figure denote the actions as follows:

A denotes rate downsizing.

B denotes inter-frequency handover.

C denotes inter-RAT handover.
Note 3:
The action in the dashed frame can be ignored in a link stability control procedure, if the
last procedure has contained the rate downsizing action and the current rate is above
Downlink Full Coverage Bit Rate.

After the downlink link stability control algorithm is triggered, the RNC takes actions on the
BE service in the sequence defined on the LMT. The RNC takes a second action when the
previous action fails. The sequence of the actions is as follows:
1. The action defined by the First Downlink QOS Enhancement Action for Traffic BE
parameter
2. The action defined by the Second Downlink QOS Enhancement Action for Traffic
BE parameter
3. The action defined by the Third Downlink QOS Enhancement Action for Traffic BE
parameter
For detailed information about the rate downsizing action, see 4.3.4 Rate Reallocation Action
Based on Downlink Quality.
For detailed information about the handover actions, see Inter-Frequency Handover and
Inter-RAT Handover.

RAN
Rate Control Description 6 Rate Control Reference Documents

6-1
6 Rate Control Reference Documents
Ra Control Reference Documents lists the reference documents te related to the feature.

protocols

eech codec speech processing functions; Adaptive Multi-Rate -
Wideband (AMR-WB) speech codec; Frame structure

3GPP TS 28.062: Inband Tandem Free Operation (TFO) of speech codecs; Service
description; Stage 3

3GPP TS 25.331: Radio Resource Control (RRC)

3GPP TS 25.413: UTRAN Iu interface RANAP signalling
3GPP TS 25.415: UTRAN Iu interface user plane

3GPP TS 25.433: UTRAN Iub interface NBAP signalling
3GPP TS 26.101: Mandatory speech codec speech processing functions; Adaptive
Multi-Rate (AMR) speech codec frame structure
3GPP TS 26.201: Sp

Rate Control Description (2008!05!30)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rate Control Description (2008!05!30)

Uploaded by

Copyright:

Available Formats

RAN

Rate Control Description

or the addition of the information that was not provided in the

You might also like