ZTE UMTS DRBC Algorithm Feature Guide

DRBC Algorithm
WCDMA RAN
Feature Guide
DRBC Algorithm Feature Guide
Version Date Author Approved By Remarks
V4.5 2010-10-15 Jiang Ying Wang Zhigang
© 2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains propriet ary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I

TABLE OF CONTENTS
1 Function Attribute ............................................................................................... 1
2 Introduction ......................................................................................................... 1
2.1 Function Introduction ............................................................................................ 1
2.1.1 Initial Channel Allocation ...................................................................................... 3
2.1.2 Channel Switching ................................................................................................ 4
2.2 DRBC .................................................................................................................... 5
2.3 Dynamic Channel Type Transfer for HSDPA Service.......................................... 7
2.4 Dynamic Channel Type Transfer for HSUPA Service.......................................... 8
2.5 RAB Negotiation & Re-negotiation ....................................................................... 9
3 Technical Description....................................................................................... 10
3.1 DRBC .................................................................................................................. 10
3.1.1 Introduction to Service Types ............................................................................. 10
3.1.2 Initial Channel Allocation .................................................................................... 10
3.1.3 Channel Switching .............................................................................................. 16
3.1.4 Related Measurement......................................................................................... 31
3.2 HSDPA Dynamic Channel Adjustment............................................................... 39
3.2.1 Signaling Channel Allocation .............................................................................. 39
3.2.2 Initial Service Channel Allocation ....................................................................... 39
3.3 HSUPA Dynamic Channel Adjustment............................................................... 49
3.3.1 Signaling Channel Allocation .............................................................................. 49
3.3.2 Initial Service Channel Allocation ....................................................................... 50
3.4 HSPA+ Dynamic Channel Adjustment ............................................................... 63
3.4.1 Dual-Carrier related Dynamic Channel Adjustment ........................................... 63
3.4.2 Fast Dormancy.................................................................................................... 64
3.5 Other Description ................................................................................................ 65
3.5.1 Traffic Sub-class rate matching .......................................................................... 65
3.5.2 RNC adjust MaxBitRate according to configuration ........................................... 67
3.5.3 Be compatible with the IPHONE which is not implement according to
encryption protocol ............................................................................................. 68
3.5.4 The MaxBR of HSDPA on Iur interface .............................................................. 69
4 Configuration of Parameters ........................................................................... 69

4.1 DRBC Related Parameters................................................................................. 69
4.1.1 Parameter List..................................................................................................... 69
4.1.2 Parameter Configuration..................................................................................... 71
4.2 HSDPA Dynamic Channel Adjustment Related Parameters ............................. 92
4.2.1 Parameter List..................................................................................................... 92
4.3 HSUPA Dynamic Channel Adjustment Related Parameters ............................. 95
4.3.1 Parameter List..................................................................................................... 95
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II

4.4 HSPA+ Dynamic Channel Adjustment Rarameters ........................................... 97

4.4.1 Parameter List..................................................................................................... 97
4.5 UE Traffic Volume Measurement Related Parameters ...................................... 99
4.5.1 Parameter List..................................................................................................... 99
4.5.2 Parameter Configuration................................................................................... 101
5 Counter And Alarm ......................................................................................... 116

5.1 Counter List ....................................................................................................... 116
5.2 Alarm List .......................................................................................................... 119
6 Glossary ........................................................................................................... 119
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. III
FIGURES
Figure 2-1 State Transitions .................................................................................................... 2

Figure 3-1 R99 Channel Switching ........................................................................................ 16
Figure 3-2 Event Triggering of Traffic Measurement ............................................................ 32
Figure 3-3 Rate Adjustment Triggered by Traffic .................................................................. 34
Figure 3-4 TxP Measurement Rationale ............................................................................... 37
Figure 3-5 HSDPA Channel Switching .................................................................................. 42
Figure 3-6 Event 1E in Channel Quality Measurement......................................................... 47
Figure 3-7 Event 1F in Channel Quality Measurement ......................................................... 48
Figure 3-8 HSUPA Channel Switching .................................................................................. 55
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. IV

1 Function Attribute
System version: [RNC V3.09, OMMR V3. 09, Node B V4.09, OMMB V4. 09]
Attribute: [Optional]
Relat ed NEs:
UE NodeB RNC MSCS MGW SGSN GGSN HLR
√ √ √ - - - - -
Note:
*-: Non-related NE:
*√: Related NE
Dependency: [None]
Exclusion: [None]
Remarks: [None]
2 Introduction
2.1 Function Introduction

The dynamic radio bearer c ontrol (DRB C) is to allocate res ources reasonably during the
system operation according to subscriber requirements and system resource utilization
to make full use of the bandwidth.
According to the state of DRB C switch DrbcSwch, it is to open or close service channel
switching dynamically. If the DRB C switch DrbcS wch is set to ON, then consider the
other switchs‟ state, which means the other functions should on the premise that DRBC
switch DrbcSwc h is set to ON. If the DRB C switch DrbcS wch is set to OFF, after initial
service channel allocation, the service will not switch channel before the end of service.
(Not e: Signaling channel allocation and switching are not under the control of this DRBC
switch DrbcSwc h.)
WCDMA PS services can be borne on CELL_DCH or CELL_FACH. Based on the

realtime t raffic, transmission power of radio links, and cell load, the bandwidth and
bearer channel for PS services may change dynamically.
The DRB C module can dynamically adjust the bearer c hannel and realtime rate of PS
and CS services, ensuring the full utilization of radio resources, system stability, and
service QoS.
The DRBC policies include:
ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1

 Initial Channel Allocation
During channel setup, the DRBC allocates proper channel and rate for the service
according to service requirements and system status. Including:
 Signaling Channel Allocation
 Initial Service Channel Allocation
 Conc urrent Service Channel Allocation
 Channel Switching
The DRB C selects appropriate transport channels according to the actual rate of PS
services. If the PS rate changes, the channel type also changes. The system monitors
the actual rate of PS services. If the actual data flow is smaller than the allocated
bandwidth, the system decreases the configured bandwidt h to save resources. When
the actual data flow is close to the allocated bandwidth, the system increases the
configured bandwidth to prevent the service from being affected.
During the session, the DRB C adjusts the service bandwidth and hands over channels
in realtime according to various measurements. The conversation service uses DL
DCH/UL DCH, streaming services use CE LL_DCH, and interactive and background
services use CELL_FA CH and CE LL_DCH. (Note: This FD does not include VoIP
related content, so the parameter VoIPChQS wc h does not use.)The figure of state
transitions currently supported by system is as follows:
Figure 2-1 State Transitions
Connected Mode
CELL_DCH
DL DCH/ UL DCH -> DL DCH/UL DCH
（UL/DL Decrease or Increase Rate（
DL HS-DSCH/ UL DCH <-> DL DCH/UL DCH

DL HS-DSCH/ UL E-DCH <-> DL DCH/ UL
DCH
Idle Mode
DL FACH/ UL RACH
CELL_FACH PCH
URA_PCH
 CELL_DCH service uses channels of the following types: DL HS-DSCH/UL E -DCH,

DL HS -DS CH/UL DCH, and DL DCH/UL DCH. Network side will determine different
channel types for services based on different NodeBs, support capabilities of UE,

and service features. Switching could be performed between different channel

types. And the rates of DL DCH and UL DCH can be adjusted dynamically.
 CELL_FACH service can use DL FA CH/ UL RA CH.
 Except not supporting to switch from URA _PCH to CELL_DCH directly, the
channels in URA_PCH, CELL_FA CH, and CE LL_DCH states can be switched
among each other.
2.1.1 Initial Channel Allocation
When a subscriber requests a service setup, the system chooses the transport channel
by the service type and rate allocat ed by the RAB sent by the CN.
 The DL DCH/ UL DCH is chosen for CS real -time services.
 I/B service in PS domain selects channels: DL HS-DSCH/UL E-DCH, DL HS-

DSCH/UL DCH, DL DCH/ UL DCH, DL FACH/UL RACH, and then selects proper
channel from the above channel set based on MaxBR, the capabilities of t he cell
and UE.
 C/S servic e in PS domain selects channels in t he following priority order: DL HS-

DSCH/UL E-DCH -> DL HS-DSCH/UL DCH -> DL DCH/UL DCH, and then selects
the proper channel from the above set based on capabilities of the cell and UE.
Relationships of supported channel types based on capabilities of the UE and cell are as
follows:
R99 cells HSDPA cell s HSUPA cell s
DL DCH/ UL DCH, DL DCH/ UL DCH, DL DL DCH/ UL DCH, DL
R99 UE DL FACH/UL FACH/UL RA CH, FACH/UL RA CH,
RACH, URA _PCH URA _PCH URA _PCH
DL HS-DSCH/UL DL HS-DSCH/UL DCH,
DL DCH/ UL DCH,
DCH, DL DCH/ UL DL DCH/ UL DCH, DL
HSDPA UE DL FACH/UL
RACH, URA _PCH DCH, DL FA CH/UL FACH/UL RA CH,
RACH, URA _PCH URA _PCH
DL HS-DSCH/UL E-DCH,
DL HS-DSCH/UL
DL DCH/ UL DCH, DL HS-DSCH/UL DCH,
DCH, DL DCH/ UL
HSUPA UE DL FACH/UL DL DCH/ UL DCH, DL
RACH, URA _PCH DCH, DL FA CH/UL
FACH/UL RA CH,
RACH, URA _PCH
URA _PCH
Determination of channel rate: For streaming, interactive, or background PS services,

the Initial rate is used for service admission and bandwidth allocation. The initial rate
function allocates adapted bandwidt h to guarant ee the user feeling, and then adjust with
traffic volume fluctuation. If Initial rate access was failed, it will try to reaccess DCH with
low-rate start.

The slow-rate start policy configures the radio paramet ers that meet the lowest QoS
requirements during the service setup. The subsequent dynamic adjustment of
bandwidth is increased according to the actual traffic requirements. The DRBC adjusts
the service bandwidth between the guaranteed bit rate and maximum bit rate to meet
the QoS requirements.
2.1.2 Channel Switching
The data demand changes when a subscriber is using a service. Therefore, it is required
to adjust the demand of the subscriber in time to satisfy the subscriber; or release the
unneeded resources of the subscriber to offer to other subscribers, ensuring the
effective utilization of resources.
During the session, the dynamic channel switching is to adjust the service bandwidth
and hands over channels in real time according to various meas urements. The system
supports the following handovers of different versions:
R99 version:
 CELL_DCH (DL DCH/ UL DCH) -> CELL_DCH (DL DCH/ UL DCH)
 DL DCH -> DL DCH (rate increase)
 DL DCH -> DL DCH (rate decrease)
 UL DCH -> UL DCH (rate increase)
 UL DCH -> UL DCH (rate decrease)
 CELL_DCH (DL DCH/ UL DCH) <-> CE LL_FACH (DL FACH/UL RA CH)
 CELL_DCH (DL DCH/ UL DCH) -> URA _PCH
 CELL_FACH (DL FA CH/ UL RA CH) <-> URA_P CH
 CELL_DCH (DL DCH/ UL DCH) -> IDLE
 CELL_FACH (DL FA CH/ UL RA CH) -> IDLE
 URA _PCH -> IDLE
Newly added channel switching in HSDPA version which supports the entire channel
switching in R99 version:
 CELL_DCH(DL HS-DS CH/UL DCH) <-> CELL_FACH (DL FA CH/ UL RA CH)
 CELL_DCH(DL HS-DS CH) <-> DL DCH

 CELL_DCH(DL HS-DS CH/UL DCH) -> URA _PCH
 CELL_DCH(DL HS-DS CH/UL DCH) -> IDLE
Newly added channel switching in HSUPA version which supports the entire channel
switching in R99 and HS DPA versions:
 CELL_DCH (DL HS -DS CH/ UL E-DCH) <-> CELL_FACH (DL FA CH/ UL RA CH)
 CELL_DCH (DL HS -DS CH/ UL E-DCH) <-> CELL_DCH (DL DCH/ UL DCH)
 CELL_DCH (DL HS -DS CH/ UL E-DCH) <-> CELL_DCH (DL HS -DS CH/ UL DCH)
 CELL_DCH ( DL HS-DSCH/UL E-DCH) -> URA_P CH
 CELL_DCH (DL HS -DS CH/ UL E-DCH) -> IDLE
2.2 DRBC
In R99 version, DL DCH/ UL DCH and DL FACH/UL RA CH can carry the PS services of
WCDMA. The real-time t raffic and transmission power of radio links, cell load, channel
occupancy, bandwidth, and bearer channel types of PS services may change
dynamically. DRBC calculation realizes the function of dynamic adjustment, mak es full
use of system radio resources, ensuring system stability and servic e QoS.
The data rat es of streaming, interactive, and background services can be changed.
Generally, the rate of streaming services will be guaranteed in a higher priority than
interactive and background services.
The traffic is the main parameter which DRB C measures. Other related parameters
includes UE internal TxP measurement, NodeB dedicated TCP measurement, and pilot
channel quality measurement.
The basic policy of DRB C calculation is:
 The service feature should be in consistency with the final bearer channel. For
example, real -time services are c arried by DL DCH/UL DCH; low-rate interactive or
background services are carried by DL FACH/UL RA CH; while high-rate interactive
or background services are carried by DL DCH/UL DCH in R99 cells.
 The bandwidt h of DCH should be exact the required bandwidth of services. When a
service requires less bandwidth, the bandwidth assigned to the service should be
adjusted correspondingly. The remaining bandwidth can be used by other
subscribers.
 When the bandwidth of DCH increases, the real -time transmission power of radio
links and cell load should be taken into consideration to ensure the stability of the
calculation and suppress the fluctuation.

The optimized dynamic configuration of radio bandwidth is realized based on policies

such as DRB C, admission control, load control, and c ongestion cont rol. For more details
of admission c ontrol, see ZTE UMTS A dmission Cont rol Feature Guide; for load control,
see ZTE UMTS Overload Control Feature Guide; for congestion control, see ZTE UMTS
Congestion Control Feature Guide.
R99 DRBC calculation can be divided into initial c hannel allocation calculation and
channel switching calculation.
1 Initial Channel Allocation Calculation
When a subscriber requests to establish a RAB, the transport channel (DL FACH/UL
RACH, DL DCH/UL DCH) will be selected based on the UE capability, service type, and
rate.
2 Channel Switching Calculation
 The handovers from dedicated channels to common channels are bas ed on the
comparis on between the capacity measurements of uplink and downlink
transmitting buffer areas and the thresholds. If the measurements are lower than
the threshold, and the rate threshold of common channels is higher than the
required rate, the services will be handed over from CELL_DCH state to
CELL_FACH state. If there is no traffic for long, services will be handed over from
CELL_FACH state to URA_P CH or IDLE state. The handovers from dedicated
channels to common channels also may be triggered by load control. If the
downlink load of the cell exceeds the overload threshold, the services will be
handed over from dedicated CE LL_DCH state to common CELL_FA CH state.
 The handovers from common channels to dedicated channels are bas ed on the
comparis on between the capacity measurements of UE uplink and downlink
transmitting buffer areas and the thres holds. If uplink or downlink measurements
are higher t han t he threshold, the servic es will be handed over from common
channels to dedicated channels.
 The dynamic adjustment SF (DASF) calculation for dedicated channels: to satisfy

the increasing demand of resourc es for subscribers, or release the unneeded
resources to offer to other subscribers, it is required to adjust the occupied
dedicated res ources in time.
 If the traffic measurement exceeds the preset thres hold, and both dedicat ed
transmission power and cell load do not exceed the preset thresholds, the
transmit rate will be increased. For details, see DL DCH -> DL DCH rate
increase” and “UL DCH -> UL DCH rate increase”. If the traffic measurement
is lower than preset threshold, the transmit rate will be decreased. For details,
see DL DCH -> DL DCH rate decrease” and “UL DCH -> UL DCH rate
decrease”.

 The changes of downlink dedicated transmission power or uplink transmission

power will also trigger the DASF. The uplink and downlink trigger the uplink
and downlink DASF adjustments separately and independently. When there
are services sent by the Uu interfac e, the system will trigger DASF with the
maximum transmission power allowed by OMC configuration. If t he
transmission power exceeds the preset high threshold, the network will
decrease the data rate till the transmission power is lower than t he preset low
threshold. By this, PS service subscribers obtain relatively high dat a rate when
the NodeB is close, and obtain lower data rat e when the NodeB is remote.
Thus, the coverage of PS services is expanded, the call drop rate during
handovers from high-rate services to low-rat e servic es is decreased. For
details, see “DL DCH -> DL DCH rate dec rease” and “UL DCH -> UL DCH
rate decreas e”.
2.3 Dynamic Channel Type Transfer for HSDPA

Serv ice
HSDPA DRB C calculation can be divided into initial channel allocat ion calculation and
1. Initial Channel Allocation Calculation
RACH, DL DCH/UL DCH, DL HS-DS CH/ UL DCH) will be selected based on the UE
capability, channel quality, service type, and rate.
2. Channel Switching Calculation
Dynamic channel switching is part of DRBC. See R99 for the whole solution. Herein we
just introduce the related contents with HS DPA. Just like R99, many factors can trigger
channel switching, including changes of traffic/throughput, RAB management, UE
mobility, load balance, and load control.
 Traffic-based channel switching
The channel resources will be adjusted dynamically based on the subscribers‟ demand
for actual service data capacity to save the network res ources. When subscribers need
a very high data rate of the actual uplink and downlink I/B servic es, the state switching
from CELL_FA CH to CELL_DCH (DL HS-DSCH/UL DCH) will be triggered. When
subscribers need a very low data rate of the actual uplink and downlink I/B services, the
state switching from CELL_DCH (DL HS-DSCH/UL DCH) to CELL_FACH will be
triggered. When there is no data rate demand, the state switching from CELL_DCH (DL
HS-DSCH/UL DCH) or CELL_FA CH to URA_PCH or IDLE will be triggered. For details,
see HSDPA channel switching.
 Channel switching based on load control

When a cell is overloaded, the services can be switched from dedicat ed channel DL HS-
DSCH/UL DCH to common channel DL FA CH/UL RA CH to reduce t he system load,
ensuring the stability of system. For details, see “CE LL_DCH -> CE LL_FACH Channel
Switching Triggered by Load” in HSDPA.
 Channel switching based on downlink channel quality
When a UE uses DL HS -DS CH/UL DCH, and moves to the margin of the cell to trigger
the 1F event, the current channel quality is relatively poor and the DL HS -DSCH -> DL
DCH channel switching will be triggered. For details, see “Switching from HS -DS CH to
DCH triggered by channel quality”.
 Mobility-bas ed channel switching
When UEs move, if the capabilities of source cell are different from that of the target cell,
the channel switching will be triggered to ensure the mobility of subscribers. For
example, the sourc e cell supports HS DPA servic es while t arget cell does not support -
that is, no other cell admits HS-DSCH services - channel realloc ation from HS-DSCH to
DCH will be performed. For details, see “HS-DS CH <-> DCH Switching triggered by
mobility”.
2.4 Dynamic Channel Type Transfer for HSUPA

Serv ice
HSUPA DRB C calculation can be divided into initial channel allocation calculation and
1. Initial Channel Allocation Calculation
RACH, DL DCH/UL DCH, DL HS-DSCH/UL DCH, DL HS-DSCH/UL E-DCH) will be
selected based on the UE capability, channel quality, service type, and rate.
2. Channel Switching Calculation
Dynamic channel switching is part of DRBC. See R99 for the whole solution. Herein we
just give some HS UPA-related introduction. Just like R99 and HSDPA, many factors can
trigger channel switching, including changes of traffic/throughput, channel quality, and
UE mobility.
 Traffic-based channel switching
The channel resources will be adjusted dynamically based on the subscribers‟ demand
for actual service data capacity to save the network resources. When subscriber need a
very high data rate of the actual I/B services, the state transition from CELL_FACH to
CELL_DCH (DL HS-DSCH/UL E-DCH) will be triggered. When subscribers need a very
low data rate of the actual uplink and downlink I/B services, the state transition from

CELL_DCH (DL HS-DS CH/ UL E-DCH) to CE LL_FACH will be triggered. When there is
no data rate demand, the state transition from CELL_DCH (HS-DSCH/E-DCH) or
CELL_FACH to URA_P CH or IDLE will be triggered. For details, see HSUPA channel
switching.
 Channel switching based on load control
When a cell is overloaded, the services can be switched from dedicat ed channel DL HS-
DSCH/UL E-DCH to common channel DL FA CH/ UL RACH to reduce the system load,
ensuring the stability of system. For details, see “CE LL_DCH -> CE LL_FACH Channel
Switching Triggered by Load” in HSUPA.
 Channel switching based on downlink channel quality
Just like HS DPA, when a UE uses HS -DS CH/E-DCH, and moves to the margin of the
cell to trigger the 1F event, the current channel quality is relatively poor and the HS-
DSCH/E-DCH -> DCH/DCH channel switching will be triggered. For det ails, see
“Channel switching from DL HS-DSCH/UL E-DCH -> DL DCH/ UL DCH triggered by
channel quality”.
 Mobility - based channel switching
When the UE moves, if the capabilities of source cell are different from that of the target
cell, the channel switching will be triggered to ensure the mobility of subscribers. For
example, the sourc e cell supports HS UPA servic es while t arget cell does not support -
that is, no ot her cell in the active set admits E-DCH services - the hard handover of HS-
DSCH and channel reallocation from E-DCH to DCH will be performed. For details, see
“DL HS-DS CH/ UL E-DCH <-> DL DCH/UL DCH or DL HS-DS CH/ UL DCH channel
switching triggered by mobility”.
2.5 RAB Negotiation & Re-negotiation

When RAB setup or relocation, it can execute QoS negotiation, also when the calling
process, it can execute QoS negotiation. RNC get alternative GB R information through
RAB ASSIGNME NT REQUES Tor RELOCA TION RE QUES T from CN, and take this as
the GBR level of this RAB. There are two situations of RAB QoS negotiation /
renegotiation: GBR increas e and GBR decrease.
GBR increase is triggered by event 4A of traffic measurement reports: the traffic

measurement reports of uplink DCH is from UE; the traffic measurement reports of
downlink DCH, downlink HS -DS CH and uplink E-DCH is from user plane. The traffic
measurement adopts the traffic measurement control of DRB C, such as 4A threshold,
trigger time and pending time.
GBR decrease is triggered by cell common overload. When common overload appears,
the executions will be performed as follow: Decreasing the service rate of R99
subscribers, forcedly handing over to inter-frequency or inter-RA T neighboring cell,

deleting the radio link of any soft handover, decreasing GBR, forcedly releasing the
service. For more details of overload, see ZTE UMTS Overload Control Feature Guide)
For more details of RAB QoS negotiation / renegotiation, see ZTE UMTS Services and
Radio Access Bearers Feature Guide)
3 Technical Description
3.1 DRBC
3.1.1 Introduction to Service Types
Because different types of services have different feat ures, the services have different
requirements for the occupied channel resources during channel allocation. Currently,
the services can be categorized into four types: Conversation, Interactive, Background,
and Streaming.
The conversation and streaming services are real-time services, and interactive and
background services are not real-time services.
3.1.2 Initial Channel Allocation
3.1.2.1 Signaling Channel Allocation
The OMC provides various parameter options so that the signaling rate c an be flexibly
configured by the paramet er InitRrcOnDc h at different rates on different channels in the
case of RRC connection establishment.
 The RNC sets the initial signaling to forcibly use DCH/DCH at 3.4k
When a UE sends a connection setup request to RNC, the RNC configures the
bidirectional 3.4 kbit/s DCH for the UE to bear signaling.
 The RNC sets the initial signaling to us e common channel forcibly
When a UE sends a c onnection setup request to RNC, the RNC configures the uplink
RACH or downlink FACH channel for the UE to bear signaling.

 The RNC sets the initial signaling to choose channel automatically, and setting
DCH/DCH at 3.4k, when dedicated channel is used
When a UE sends a connection setup request to RNC, the RNC automatically select the
dedicated channel (3. 4 kbit/s) or common channel based on the reason for connection
setup: if services are initiated immediately after the setup of RRC connection, RNC will
select DCH channel and configures bidirectional 3.4 kbit/s bear signaling; if there is only
LA update, instead of setting up services, that should be completed after RRC
connection, RNC will select common channel to bear signaling.
dedicated channel (13.6 kbit/s) or common channel based on the reason for connection
select DCH channel and configures bidirectional 13.6 kbit/s bear signaling; if there is
only LA update, instead of setting up services, that should be complet ed after RRC
connection, RNC will select common channel to bear signaling.
dedicated channel (27.2 kbit/s) or common channel based on the reason for connection
select DCH channel and reconfigures bidirectional 27.2 kbit/s bear signaling; if there is
only LA update, instead of setting up services, that should be complet ed after RRC
connection, RNC will reconfigure common channel to bear signaling.
When the RNC sets the initial signaling to c hoose channel automatically, the signaling
will be set on DL DCH/UL DCH bearer in preference if the signaling is set due to the
following reasons: Originating Conversational Call, Originating Streaming Call,
Originating Interactive Call, Originating Background Call, Originating Subscribed traffic
Call, Terminating Conversational Call, Terminating Streaming Call, Terminating
Interactive Call, Terminating Background Call, Emergency Call, Inter-RAT cell change
order, Call re-establishment, and MBMS ptp RB request; if the signaling is set due to
other reasons, it will be set on DL FA CH/ UL RA CH bearer.
High-rate (13.6 kbit/s,27.2kbps ) signaling bearer only exits in a separate signaling

process, and will be restored to ordinary rat e (3.4 kbit/s) after the service is set up. High-
rate signaling can effectively speed up the signaling interaction during the UE call setup
and lower the call delay, but it occupies more radio resources than ordinary rate

signaling bearer. Using common channel for signaling bearer does not occupy the
dedicated resources. Considering that the separat e signaling process is short, and the
radio connection is released or services are set up after the signaling interaction, the
configuration of high rate signaling is recommended.
3.1.2.2 Initial Service Channel Allocation
For a RAB request of a service, the RNC chooses the initial channel for the service by
the servic e features (RAB parameters ). Selection principles:
 The conversation and streaming servic es use DL DCH/UL DCH.
 The interactive and background services can use DL DCH/UL DCH and DL
FACH/ UL RA CH.
Whether the DL DCH/UL DCH or DL FACH/UL RA CH is used for interactive and

background services depends on the values of MaxBR in RAB allocation and Rfach and
Rrac h. If DL MaxBR is greater than or equal to Rfach, or UL MaxB R is great er than or
equal to Rrach, the DL DCH/UL DCH is chosen in preference. Otherwise, the DL
FACH/ UL RACH is chosen in preference. If FACH/RA CH is rejected to access, the RNC
will reselect the DL DCH/UL DCH to access.
CS 64k service access:
New CS 64k service setup
Check the state of switch Cs64S witch in the cell: if it is closed, CS 64k servic e is not
allowed to access; otherwise CS 64k service is allowed.
For the UE in macro diversity, if any of cells is not allowed to access CS 64k service, it is
not allowed.
CS 64k service already setup
In the scene of hand over cross Iur interface, check the state of switch AdjCs64S witch in
the target cell. If this information cannot acquire, it will consider that CS 64k service is
allowed to access. If the target cell doesn‟t allow CS 64k service access and it supports
CS 64k service falling back to AMR service, then CS 64k service will fall back to AMR
service, otherwise CS 64k service will not fallback to AMR service.
In the scene of hand over non-cross Iur interface, check the state of switch Cs64S witch
in the target cell. If the t arget cell doesn‟t allow CS 64k service access and it supports
CS 64k service falling back to AMR service, then CS 64k service will fall back to AMR
service, otherwise CS 64k service will not fall back to AMR service.
The initial access rate of DL DCH/ UL DCH of PS services is determined in the following
way:

If the DRB C switch DrbcS wch is set to OFF, the DCH initial rate is the minimum DRBC
rate (max (highest rate level of DBRC, GBR), MaxBR). The uplink and downlink DRBC
rate levels are configured by UlRateAdjLev[ MA X_NUM_RA TE _ADJUS T] and
DlRateAdjLev[MA X_NUM_RA TE_A DJUS T] separat ely.
If the DRB C switch DrbcSwch is ON,the DCH initial rate is [UL initial rate, DL initial rate],
if one or two direction(s) of DCH failed in accessing, UL and DL DCH try to access with
minimum rates of DCH at the same time.
DCH initial rate according to Non-realtime and Realtime are defined in following:
1. [Uplink initial rate]of Non-RealTime DCH is min( max(InitialRateUl, GBR), MBR, the
minimum NrtMaxUlRateDch_new of all connection cells).
Thereinto the definition of NrtMaxUlRateDch_new is as following:
 On the scene of the access cell is under the Serving-

RNC:NrtMaxUlRateDch_new = Nrt MaxUlRateDch
 If the access cell is the neighbor cell of cell under the S erving-
RNC:NrtMaxUlRateDch_new = NrtMax UlRateDchD
 And if Serving-RNC is unable to know NrtMax UlRateDchD,then

NrtMax UlRateDchD=384kbps.
2. [Uplink initial rate] of RealTime DCH channel is min( max(InitialRateUl, GBR), MBR,
the minimum RtMaxUlRateDch_new of all connection cells).
Thereinto the definition of RtMaxUlRat eDch_new is as following:

RNC:RtMax UlRateDch_new = RtMaxUlRateDch
RNC:RtMax UlRateDch_new = RrtMaxUlRateDchD
 And if Serving-RNC is unable to know RtMax UlRateDchD,then

RtMaxUlRateDchD=384kbps.
3. [Downlink initial rate] of Non-RealTime DCH channel is min( max (InitialRateDl,

GBR), MBR, the minimum NrtMaxDlRateDch_new of all connection cells).
Thereinto the definition of NrtMaxDlRateDch_new is as following:

RNC:NrtMaxDlRateDch_new =NrtMaxDlRateDch
RNC:NrtMaxDlRateDch_new = NrtMax DlRateDchD

 And if Serving-RNC is unable to know NrtMax DlRateDchD,then

NrtMax DlRateDchD=384kbps.
4. [Downlink initial rate]of RealTime DCH channel is min( max(InitialRat eDl, GBR),
MBR, the minimum RtMaxUlRateDch_new of all connection cells).
Thereinto the definition of RtMaxDlRat eDch_new is as following:

RNC:RtMax DlRateDch_new =RtMaxDlRateDch
RNC:RtMax DlRateDch_new = RtMaxDlRateDchD
 And if Serving-RNC is unable to know RtMax DlRateDchD,then

RtMaxDlRateDchD=384kbps.
5. When occupied DCH on initial setup,the Traffic should assigned with minimum
rate,which as the same as the rate transfer from HS-DSCH to DCH
6. If GBR of Uplink Traffic exceed Rt MaxUlRateDch,uplink Traffic access denial,so as

RtMaxDlRateDch for downlink.
Whatever the state of DRB C, If the GB R of a traffic exceed 384k, and be restriced on
DCH, it should be denial
If [ Initial rate]access failed,try to access with minimum rate:
1. Uplink minimum rate of Non-RealTime DCH channel is min( max(lowest level of

UlRateAdjLev [MAX_NUM_RATE_A DJUST], GBR), MBR, the minimum
NrtMax UlRateDch_new of all connection cells).
2. Uplink minimum rate of RealTime DCH channel is min( max(lowest level of

UlRateAdjLev [MAX_NUM_RATE_A DJUST], GBR), MBR, the minimum
RtMaxUlRateDch_new of all connection cells).
3. Downlink minimum rate of Non-RealTime DCH channel is min( max(lowest level of

DlRateAdjLev [MAX_NUM_RATE_A DJUST], GBR), MBR, the minimum
NrtMax DlRateDch_new of all connection cells).
4. Downlink minimum rate of RealTime DCH channel is min( max(lowest level of

DlRateAdjLev [MAX_NUM_RATE_A DJUST], GBR), MBR, the minimum
RtMaxUlRateDch_new of all connection cells).
Where, the GB R of streaming services is the GBR of RAB allocation; the GBR of I/B
services is 0; the MaxBR is the maximum bit rate of RAB allocation by Iu interface.
Nrt MaxUlRateDch indicates the maximum bit rate on UL DCH allowed in serving cell for an
NRT PS domain RAB. Nrt MaxDlRateDch indicates the maximum bit rate on DL DCH allowed
in serving cell for an NRT PS domain RAB. Rt MaxUlRateDch indicates the maximum bit rate on

UL DCH allowed in serving cell for an RT PS domain RAB. Rt MaxDlRateDch indicates the
maximum bit rate on DL DCH allowed in serving cell for an RT PS domain RAB.
DCH rate level can be configured by parameters, with the uplink and downlink rate
configured separately. The parameter UlRateAdjLevNum indicates the number of rate
levels in uplink DCH channel; the parameter UlRateA djLev[ MAX_NUM_RATE_ADJ UST]
indicates the specific rat e levels which can be chosen by uplink DCH channel; the
parameter DlRateA djLevNum indicates the number of rate levels in downlink DCH
channel; the parameter DlRateA djLev[ MAX_NUM_RATE_ADJ UST] indicates the
specific rate levels which can be chosen by the downlink DCH channel. The lowest rate
level is the minimum rat e level.
3.1.2.3 Concurrent Service Channel Allocation
The concurrent service means the setup of new service when a UE already has an
online call service.
 If a subscriber is in the CELL_DCH state, the new service is also set up on the
DCH channel. The initial rate of t he new servic e is determined by the same method
as that for a single service.
 If t he subscriber is in the CELL_FA CH state, the system judges whether to perform

state transitions according to the new service type.
 If the new servic e should be set up on the DL DCH/UL DCH channel

according to the channel allocation principles as for a single service, the UE
should switch from CELL_FACH state to CELL_DCH state, that is, all the
online services will be switched to DCH channel. The initial rate of the new
service is determined by the same method as that for a single service.
 If the new service is set up on the DL FA CH/UL RACH channel according to

the channel allocation principles as for a single service, the UE keeps in t he
CELL_FACH state, without impact on the online services.
For concurrent CS and PS (S/I/B) services:
 IF the DRB C switch DrbcS wch is set to OFF, the DCH rate of PS (S/I/B) services is
the minimum DRB C rate (max (highest rate level of DRB C, GBR), MaxBR). The
uplink and downlink DRBC rate levels are configured by
UlRateAdjLev[MA X_NUM_RA TE_A DJUS T] and
 If the DRB C switch DrbcSwch is ON, the DCH rate of PS (S/I/B) services is the
initial DRBC rate.(see 3.1.2.2). Rate increase is allowed based on rate increase
principles (see UL DCH -> UL DCH (rate increase) and DL DCH -> DL DCH (rate
increase)). The uplink and downlink DRB C rate levels are configured by

UlRateAdjLev[MA X_NUM_RA TE_A DJUS T] and

Where, the GB R of streaming services is the GBR of RAB allocation; the GBR of I/B
services is 0; the MaxBR is the maximum bit rate of RAB allocation by Iu interface.
The channel switching and dynamic resource adjustments are performed only when the
DRB C switch (DrbcSwc h) is ON.
During t he session, the dynamic channel s witching for the R99 system is to adjust the
service bandwidth and hand over channels in real-time according to the measurements
of traffic, cell load, DL DTCP, and UL UE Txp. The figure below shows the R99 channel
switching that the system currently supports according to the R99 protocol.
Figure 3-1 R99 Channel Switching

Reconfig SF
1. UL/DL Traffic Volume
Based
2. DL D-TCP Based
3. UL TxP Based Transition of DCH/DCH -> FACH/RACH
4. Cell’s RTWP 1. UL&DL Traffic Volume Based
5. Cell’s TCP 2. Support CELL_FACH
Transition of FACH/RACH -> DCH/DCH

CELL_DCH 1. UL/DL Traffic Volume Based
2. Cell’s RTWP & Cell’s TCP
FACH/RACH
DCH/DCH
CELL_FACH
Transition of FACH/RACH -> PCH

Transition of DCH/DCH -> PCH 1. UL&DL Traffic Volume Based
1. UL&DL Traffic Volume Based 2. Support PCH
2. Support PCH
Transition of PCH -> FACH/RACH
1. UL/DL Traffic Volume based
PCH
Idle Transition of FACH/RACH -> IDLE
URA_PCH 1. UL&DL Traffic Volume Based
Transition of PCH->IDLE Transition of DCH/DCH ->IDLE

1. DL&UL Traffic Volume Based 1. UL&DL Traffic Volume Based
Below we will introduce the switching principles for types of channel switching shown in
the above figure.
3.1.3.1 DL DCH -> DL DCH (Rate Increase)
Rate increase triggered by downlink traffic
The DCH to DCH rate inc rease is based on t he traffic measurement report (E vent 4A)
from the user plane and determined by the dedicated transmission power of the
subscriber and cell load.

The 4A event is defined as the traffic measurement larger than an absolute threshold.
See 3.1.4.1”Traffic Measurement” for its detailed definition.
The E vent A is defined as that the Node B downlink dedicat ed transmission power (D-
TCP) is greater than an absolute threshold. The E vent B is defined as that the Node B
downlink dedicated transmission power (D-TCP) s smaller than an absolut e threshold.
See 3.1.4.3”NodeB Dedicated TCP Measurement” for detailed definitions.
The downlink DCH rate increase is triggered in the case of the following conditions:
 The DCH rate adjustment triggered by traffic switch DchAdjRateS wch is open.
 The system receives consecutive DchE4aThd traffic measurement reports (E vent

4A) from the user plane. (Note: if the system receives a traffic measurement report
(E vent 4B) from the user plane when the receiving times are smaller than the
threshold, the corresponding counter is cleared)
 The system receives consecutive DtcpE bThd measurement reports (E vent B) of

NodeB D-TCP, that is, the UE is in B state. (Note: if the system receives a traffic
measurement report (E vent A) of NodeB when the receiving time is smaller than
the threshold, the corresponding counter is cleared.)
 The downlink load of the cell is not overloaded (the downlink load is determined by
TCP. For det ails of overload threshold, see ZTE UMTS Overload Control Feature
Guide)
For non-macro diversity, in the case of DCH rate increase:
the target rate of NRT DCH is min (next rate level greater than the current rate in the
DRB C downlink rate levels DlRat eAdjLev[ MAX_NUM_RATE_A DJUST],
Nrt MaxDlRateDch, DL MaxBR). The MaxBR is the maximum bit rate during RAB
allocation.
the target rate of RT DCH is min (next rate level greater than the current rate in the
DRB C downlink rate levels DlRat eAdjLev[ MAX_NUM_RATE_A DJUST],
RtMaxDlRateDch, DL MaxB R).
Parameters explaination:see 3.1.2. 2
For macro diversity, in the case of DCH rate increase:
the target rate of Nrt Downlink DCH rate is min (next rate level greater than the current
rate in DRB C downlink rate levels DlRateA djLev[ MAX_NUM_RATE_ADJ UST], DL
MaxB R, the minimum NrtMaxDlRat eDch_new of all connection cells, MaxRateMD). The
MaxRateMD is the maximum rate threshold allowed for DCH when t he UE is in macro
diversity.
the target rate of Rt Downlink DCH rate is min (next rate level greater than the cur rent
rate in DRB C downlink rate levels DlRateA djLev[ MAX_NUM_RATE_ADJ UST], DL

MaxB R, the minimum RtMaxDlRateDch_new of all connection cells,MaxRateMD). The

diversity.
The MaxRateMD is the maximum rate threshold allowed for DCH when t he UE is in
macro diversity.
In case of the concurrence of C (CS) services and PS (S/I/B) services, the additional
principles of rate increase of PS services are as follows:
 Determine the maximum rate threshold of NRT PS (I/B) services by distinguish the
rates of C (CS) services themselves
 If the rate of C (CS ) services is less than or equal to CRateThrd, the sum of
rates of concurrent PS services of NRT can not exceed PsRateLmt LowC
 If the rate of C (CS ) services exceeds CRateThrd, the sum of rates of

concurrent PS services of NRT can not exceed PsRateLmt HighC
 The rate of streaming services is not restricted by the above rate threshold.
3.1.3.2 DL DCH -> DL DCH (Rate Decrease)
The DCH rate is decreased in order to:
 Release some of the bandwidths of the subscriber to other subscribers to improve

the bandwidth utilization ratio when the required bandwidth for data transmission of
the subscriber is decreased.
 Lower the bandwidth of the subscriber and transmission power to ensure the QoS
for the subscriber when the downlink transmission power of the subscriber is too
high.
 Lower the bandwidth of the subscriber and the system load t o ens ure t he system
stability when the cell load is too high.
Therefore, the downlink DCH rate decrease can be triggered by the following factors:
 Rate decrease triggered by downlink traffic
 Rate decrease triggered by Node B downlink dedicated transmission power
 Rate decrease triggered by cell downlink load
 Rate decrease triggered by downlink resource congestion

 Rate decrease triggered by mobility
 Rate decrease triggered by DCH rate limitation in cell
Any of the above factors can trigger the rat e decrease.
1. Rate decrease triggered by downlink traffic
The DCH to DCH switching for downlink rat e decreas e is based on the traffic
measurement report (E vent 4B) on the user plane.
The E vent 4B is defined as that the value of t raffic measurement is smaller than an
absolute threshold. See 3.1. 4.1”Traffic Measurement” for its detailed definition.
The DL rate decrease is triggered in the case of the following conditions:
 The system receives consecutive DchE4bThd traffic measurement reports (E vent

4B) from the user plane. (Note: if the system receives a traffic measurement report
(E vent 4A) from the user plane when the receiving times are sm aller than the
threshold, the corresponding counter is cleared.)
 None-realtime I/B services: [current uplink rate of the UE is greater than or equal to
the rat e threshold Rrach for RACH switching] or [downlink target rate is greater
than or equal to the rate threshold Rfach for FACH switching] (if the system switch
FachSwch for CELL_FA CH switching is closed, the above condition is not taken
into consideration); real -time S services: current rate exceeds the GBR of RAB
allocation
In the case of rate increase of DCH, the target rate is calculated by the formula: max
(next rate level smaller than the current rate in DRB C downlink rate levels
DlRateAdjLev[MAX _NUM_RATE_A DJUST], GB R). The GB R of interactive and
background services is 0, and t he GB R of streaming se rvices is the GB R of RAB
allocation.
2. Rate decrease triggered by Node B downlink dedicated transmission power
The DCH to DCH switching for downlink rate decrease can be triggered by the Node B
downlink dedicated transmission power (E vent A).
The E vent A is defined as that the NodeB downlink dedicated transmission power (D-
TCP) is greater than an absolute threshold. The E vent B s defined as that the NodeB
downlink dedicated transmission power (D-TCP ) is smaller than an absolute threshold.
See 3.1.4.3”NodeB Dedicated TCP Measurement” for detailed definitions.
The DCH rate decrease is triggered in the case of the following conditions:
 The DCH rate adjustment triggered by D-TCP switch DlPwrDasf is open.

 The system receives consecutive DtcpE aThd measurement reports (E vent A) of

Node B D-TCP, that is, the UE is in A state. (Note: if the system receives a traffic
measurement report (E vent B) by Node B when the recei ving times are smaller
than the threshold, the corresponding counter is cleared.)
 Non-realtime I/B services: current rate is greater than minimum rate in DCH (lowest
rate level configured by DlRateAdjLev[ MA X_NUM_RA TE _ADJUS T] ); real -time S
services: current rat e is greater than the GBR of RAB allocation
background services is 0, and the GBR of streaming service is the GBR in RAB
allocation.
3. Rate decrease triggered by cell downlink load
The DCH to DCH switching for DCH downlink rate decrease can be triggered by the
downlink load control of the cell.
 The current cell load exceeds the overload threshold; (the downlink load is
determined by TCP. For details of overload threshold, see ZTE UMTS Overload
Cont rol Feature Guide)
rate level configured by DlRateAdjLev[MA X_NUM_RA TE _ADJUS T] ); realtime S
background services is 0, and the GBR of streaming services is the GBR in RAB
allocation.
For more details of load control, see ZTE UMTS Overload Control Feat ure Guide.
1. Rate decrease triggered by downlink resource congestion
The DCH to DCH switching for DCH downlink rate decrease can be triggered by the
downlink res ourc e congestion of the cell.
 The downlink CE resources, code reso urces or power are congested.

rate level configured by DlRateAdjLev[MA X_NUM_RA TE _ADJUS T] ); realtime S
background services is 0, and the GBR of streaming services is the GBR in RAB
allocation.
For more details of congestion control, see ZTE UMTS Congestion Control Feat ure
Guide.
1. Rate decrease triggered by mobility
The UE performs hard handover from one R99 cell to another due to mobility, if the
subscriber downlink admission at the current rate fails in the target cell, the system uses
the minimum DRB C rate to admit the user again. The minimum rate is min (max (lowest
level of DRBC downlink rate levels DlRateAdjLev[ MAX_NUM_RATE _ADJUS T], DL
GBR), DL MaxBR).
For more details of mobility, see ZTE UMTS handover Control Feature Guide.
1. Rate decrease triggered by DCH rate limitation in cell
Take the 6000ms as period, checking periodically whether there exist NRT or RT
services which exceed DCH rat e limitation NrtMaxDlRateDch or Rt MaxDlRat eDch. If so,
choose 5 users to decrease rate, and the NRT traffic target rate is Nrt MaxDlRateDch
and NRT traffic target rate is Rt MaxDlRat eDch
3.1.3.3 UL DCH -> UL DCH (Rate Increase)
1. Rate increase triggered by uplink traffic.
The DCH to DCH switching for uplink rate increas e is based on the traffic measurement
report (E vent 4A) by the UE and determined by the cell's dedicated transmission power
and cell load.
The 4A event is defined as the traffic measurement larger than an absolute threshold.
See 3.1.4.1”Traffic Measurement” for its detailed definition.
The uplink DCH rate increase is triggered in the case of the following conditions:

4A) from the UE. (Note: if the system receives a traffic measurement report (E vent

4B) from the UE when the receiving times are smaller than the threshold, the
corresponding counter is cleared)
 If the system receives the measurement reports (E vent 6B2) triggered by UE

transmission power, that is, UE uplink transmission power is in 6B state (Note: for
details, see 3.1.4.2”UE internal TxP Meas urement ”)
 The uplink load of t he cell is not overloaded (Note: the uplink load is determined by
RTWP. For details, see ZTE UMTS Overload Control Feature Guide)
For non-macro diversity, in the case of DCH rate increase:
the target rate of NRT DCH is min (next rate level greater than the current rate in the
DRB C uplink rate levels UlRateA djLev[ MAX_NUM_RATE _ADJ UST], Nrt MaxUlRateDch,
UL MaxBR). The MaxBR is the maximum bit rate during RAB allocation.
the target rate of RT DCH is min (next rate level greater than the current rate in the
DRB C downlink rate levels UlRat eAdjLev[ MAX_NUM_RATE_A DJUST],
RtMaxDlRateDch, UL MaxB R).
For macro diversity, in the case of DCH rate increase:
the target rate of Nrt Uplink DCH rate is min (next rate level greater than the current
rate in DRB C uplink rate levels UlRat eAdjLev[ MAX_NUM_RATE_A DJUST], UL MaxB R,
the minimum NrtMaxUlRateDch_new of all connection cells,MaxRateMD). The
diversity.
the target rate of Rt Downlink DCH rate is min (next rate level greater than the current
rate in DRBC Uplink rate levels UlRateAdjLev[ MAX_NUM_RATE _ADJ UST], UL MaxB R,
the minimum RtMaxUlRateDch_new of all connection cells,MaxRateMD). The
diversity.
macro diversity.
In case of the concurrence of C (CS) services and PS (S/I/B) services, the additional
principles of PS service rate inc rease are as follows:
 Determine the maximum rate threshold of NRT PS (I/B) services by distinguish the
rates of C (CS) services themselves.
 If the rate of C (CS ) services is less than or equal to CRateThrd, the sum of
rates of concurrent PS services of NRT can not exceed PsRateLmt LowC

 If the rate of C (CS ) services exceeds CRateThrd, the sum of rates of

concurrent PS services of NRT can not exceed PsRateLmt HighC
 The rate of streaming services is not restricted by the above rate threshold.
3.1.3.4 UL DCH -> UL DCH (Rate Decrease)
The DCH rate is decreased in order to:
 Release some of the bandwidths of the subscriber to other subscribers to improve

the bandwidth utilization ratio when the required bandwidth for data transmission of
the subscriber is decreased.
 Lower the bandwidth of the subscriber and transmission power to ensure the QoS
for the subscriber when the uplink transmission power of the subscriber is too high.
 Lower the bandwidth of the subscriber and the system load t o ens ure t he system
stability when the cell load is too high.
Therefore, the uplink DCH rate decrease can be triggered by various factors, such as:
 Rate decrease triggered by uplink traffic
 Rate decrease triggered by UE uplink dedicated transmission power
 Rate decrease triggered by cell uplink load
 Rate decrease triggered by uplink resource congestion.
 Rate decrease triggered by mobility
 Rate decrease triggered by DCH rate limitation in cell
Any of the above factors can trigger the rat e decrease.
1. Rate decrease triggered by uplink traffic
The DCH to DCH switching for uplink rat e decrease is based on the t raffic measurement
report (E vent 4B ) from the user plane.
The E vent 4B is defined as that the value of t raffic measurement is smaller than an
absolute threshold. See 3.1. 4.1”Traffic Measurement” for its detailed definition.
 If the system receives consecutive DchE 4bThd traffic measurement reports (E vent
4B) of the UE. (Note: if the system receives a t raffic measurement report (E vent 4A )

by the UE when the receiving times are smaller than the threshold, the
corresponding counter is cleared)
 None-realtime I/B services: [current uplink rate of the UE is greater than or equal to
the rat e threshold Rrach for RACH switching] or [downlink target rate is greater
than or equal to the rate threshold Rfach for FACH switching] (if the system switch
FachS wch for CELL_FA CH switching is closed, the above condition is not taken
into consideration); real -time S services: current rate exceeds the GBR of RAB
allocation
The target rate of DCH rate decrease is max (next rate level smaller than the current
rate in DRB C uplink rate levels UlRateAdjLev[MAX _NUM_RATE_A DJUST], GBR). The
GBR of interactive and background servic es is 0, and the GBR of streaming services is
the GBR in RAB allocation.
2. Rate decrease triggered by UE uplink dedicated transmission power
The DCH to DCH switching for uplink rate decrease can be triggered by the UE uplink
dedicated transmission power (E vent 6A1). When the UE is far away from the base
station and its transmission power reac hes the maximum, the UL DCH rate can be
decreased to lower the UE transmission power to avoid interference with other
subscribers. When the UE comes close to the base station, the traffic can trigger the UL
DCH rat e increase.
The E vent 6A1 is defined as that the UE dedicated transmission power exceeds an
absolute threshold, namely, the UE is in high power status. For specific configurations of
threshold, see 3.1.4.2”UE internal TxP Measurement.”
 The DCH rate adjustment triggered by UE dedicated transmission power switch

UlP wrDasf is open.
 Receive the measurement reports (E vent 6A1) triggered by UE transmission power,

that is, the UE transmission power is in 6A state.
rate level configured by UlRateAdjLev[ MAX_NUM_RATE _ADJUST] ); real-time S
services: current rat e is greater than the GBR in RAB allocation
3. Rate decrease triggered by cell uplink load

The DCH to DCH switching for DCH uplink rate decrease can be triggered by the uplink
load cont rol of the cell.
 The current uplink cell load exceeds the overload threshold; (the uplink load is
determined by RTWP. For details of overload threshold, see ZTE UMTS Overload
Cont rol Feature Guide)
4. Rate decrease triggered by uplink resource congestion
The DCH to DCH switching for DCH uplink rate decrease can be triggered by the uplink
resource congestion of the cell.
 The CE uplink resources or power are congested.
For more details of congestion control, see ZTE UMTS Congestion Control Feat ure
Guide.
1. Rate decrease triggered by mobility
When the UE performs hard handover from one R99 cell to another due to mobility, if
the subscriber uplink admission at the current rate fails in a target cell, the system uses
the minimum DRBC rate to admit the subscriber again. The minimum rate is min (max
(lowest level of DRBC uplink rate levels UlRateA djLev[ MAX_NUM_RA TE_ADJ UST], UL
GBR), UL MaxBR).

2. Rate decrease triggered by DCH rate limitation in cell
Take the 6000ms as period, checking periodically whether there exist NRT or RT
services which exceed DCH rat e limitation NrtMaxDlRateDch or Rt MaxDlRat eDch. If so,
choose 5 users to decrease rate, and the NRT traffic target rate is Nrt MaxDlRateDch
and NRT traffic target rate is Rt MaxDlRat eDch
3.1.3.5 CELL_DCH(DL DCH/ UL DCH) <-> CELL_FACH(DL FACH/UL RACH)
1. CELL_DCH <-> CELL_FA CH channel switching triggered by traffic
i CELL_DCH (DL DCH/ UL DCH ) -> CE LL_FACH (DL FACH/UL RA CH)
When the UE is in the CELL_DCH (DL DCH/ UL DCH) state, the switching from
CELL_DCH (DL DCH/UL DCH) to CELL_FA CH (DL FACH/UL RACH) can be
triggered by the traffic measurement report (E vent 4B ) from the user plane and UE.
The E vent 4B is defined as that the value of traffic measurement is smaller t han an
absolute threshold. For details, see 3.1.4.1”Traffic Measurement.”
The switching from CE LL_DCH (DL DCH/ UL DCH) to CELL_FACH (DL FA CH/ UL
RACH) is triggered in the case of the following conditions:
 The system switch FachS wch for CE LL_FACH switching is open.
 The services are interactive or background services.
 The system receives consecutive ToFtimesThr traffic measurement reports

(E vent 4B) from the user plane and UE,and switch is triggered by downlink
report.(Note: if the system receives a traffic measurement report (E vent 4A)
from the user plane or UE when the receiving times are smaller than the
threshold, the calculator is clear.)
 The downlink target rate of t he UE is smaller t han t he maximum downlink rate

threshold Rfach, and the current uplink rate is smaller than the maximum
uplink rate threshold Rrach (Note: if the rate is at the lowest rate level
configured by UlRateAdjLev[ MAX_NUM_RATE _ADJ UST] and
DlRateAdjLev[MAX _NUM_RATE_A DJUST], the above condition is not taken
into consideration.)
 When in macro diversity state, all the best radio link belongs to S-RNC;
otherwise the DL DCH/UL DCH rate is to be decreased.
If the concurrent services exist, it is required that all the services should meet the
condition for switching to CE LL_FACH.
If the condition for CE LL_FACH switching is met, but the CELL_FA CH fails the
admission, and current uplink or downlink rate is greater than the minimum rate that

UL DCH or DL DCH can bear, namely, the lowest rate level configured by
UlRateAdjLev[MAX _NUM_RATE_A DJUST] and
DlRateAdjLev[MAX _NUM_RATE_A DJUST], UL DCH or DL DCH rate decreas e is
selected.
ii CELL_FACH (DL FA CH/ UL RA CH) -> CE LL_DCH (DL DCH/ UL DCH)
When the UE is in the CELL_FA CH (DL FA CH/ UL RACH) state, the switching from
CELL_FACH (DL FACH/UL RA CH) to CELL_DCH (DL DCH/UL DCH) can be
triggered by the traffic measurement report (E vent 4A ) from the user plane or UE.
The switching from CE LL_FACH (DL FA CH/ UL RA CH) to CE LL_DCH is triggered

in the case of the following conditions:
 The system receives consecutive FachE 4aThd measurement reports of E vent

4A about traffic from the us er plane or UE.
 The cell is not overloaded (Note: the uplink load is determined by RTWP,
while the downlink load is determined by TCP. For overload threshold, see
ZTE UMTS Overload Control Feature Guide)
The rate of DL DCH/ UL DCH is the initial rate of DRB C after the CE LL_DCH
switching, which is [UL initial rate,DL initial rate] (see 3.1.2. 2) The GBR of
interactive and background services is 0.
2. CELL_DCH to CELL_FA CH channel switching triggered by load
The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FA CH can be triggered by
the cell load.
The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FA CH (DL FACH/UL
 The downlink cell load exceeds the overload threshold (Note: the downlink
load is determined by TCP. For of overload threshold, see ZTE UMTS
Overload Control Feature Guide)
3.1.3.6 CELL_DCH (DL DCH/UL DCH ) -> URA_PCH
When the UE uses the CELL_DCH(DL DCH/ UL DCH) for service bearer, the switching
from CELL_DCH (DL DCH/UL DCH) to URA_P CH can be triggered by the traffic
measurement report (E vent 4B0) from the user plane and UE.
The E vent 4B0 is defined as that the value of traffic measurement value is 0. See
3.1.4.1”Traffic Measurement” for its detailed definition.

The switching from CELL_DCH (DL DCH/UL DCH) to URA_P CH is triggered in the case
of the following conditions:
 The system switch PchSwch for URA _PCH switchingis open.
 The services are interactive or background services.
 The system rec eives consecutive DToPchThd traffic measurement reports with
measurement value of 0 from the user plane and UE (Note: if the system receives a
report with measurement value of non -zero value when the receiving times are
smaller than the threshold, the corresponding counter is cleared)
 When in macro diversity status, all the best radio links belong to S-RNC.
If t he concurrent services exist, it is required that all the services should meet the
condition for switching to URA_P CH.
If the concurrence of CS and PS servic es or multiple PS services occurs, and both the
uplink and downlink traffic measurement values of a PS I/B service are 0, and t hen the
system receives consecutive DToPchThd traffic measurement reports of E vent 4B0 from
the user plane and UE, the rate of the PS service is decreased to 0 kbit/s/0 kbit/s, and
keep in CE LL_DCH state without switching.
3.1.3.7 CELL_FACH (DL FACH/UL RACH) <-> URA_PCH
1. CELL_FACH (DL FA CH/ UL RA CH) -> URA_P CH
When the UE uses the CELL_FA CH to bear the interactive and background services,
the switching from CELL_FA CH to URA_P CH can be triggered by the traffic
measurement report (E vent 4B0) from the user plane and UE.
The switching from CE LL_FACH to URA _PCH is triggered in the c ase of the following
conditions:
 The system switch PchSwch for URA _PCH switching is open.
 The system receives consecutive FToPchThd traffic measurement reports with

measurement value of 0 by user plane and UE (Note: if the system receives a
report with measurement value of non -zero value when the receiving times are
2. URA _PCH -> CELL_FA CH (DL FACH/UL RACH)
When the UE in URA_PCH state originates the cell update mes sage due to uplink or
downlink data transmission requirements or for new service setup, the system allocates

the channel by the UE service type before the UE is handed over to P CH by the process
of initial service channel allocation. This applies to interactive and background services.
3.1.3.8 CELL_DCH (DL DCH/UL DCH ) -> IDLE
When the UE uses the CELL_DCH for service bearer, the switching from CELL_DCH to
IDLE is triggered in the case of the following conditions:
 The services are interactive or background services .
The system receives consecutive DToIdleThd traffic measurement reports with

measurement value of 0 from the user plane and UE. (Note: If the system receives the
measurement reports with traffic measurement value of non -zero value when the
receiving times are smaller than the threshold, the corresponding counter is cleared.)
condition for switching to IDLE.
When the channel is switched t o IDLE, the occupied radio resources are released and
the UE returns to the standby status.
3.1.3.9 CELL_FACH (DL FACH/UL RACH) -> IDLE
When the UE uses the CELL_FA CH to bear the interactive and background services,
the switching from CELL_FA CH to IDLE is triggered in the case of the following
conditions:
The system receives consecutive FToIdleThd traffic measurement reports with

measurement value of 0 from the user plane and UE. (Note: If the system receives the
measurement reports with traffic measurement value of non -zero value when the
receiving times are smaller than the threshold, the corresponding counter is cleared.)
conditions for switching to IDLE.
When the channel is switched t o IDLE, the occupied radio resources are released and
3.1.3.10 URA_PCH -> IDLE
When the time that the UE resides in the PCH status exceeds the threshold
PchHoldTimeThr, the UE is handed over to the IDLE status and the RRC connection is
released.

3.1.3.11 Bit rate Adaptation in one step
Bit rate adaptation in one step is based on the situation when UL DCH and DL DCH of a
RB re-configure succession in a short time. A Timer being set to certain that the
previous reconfigure direction could wait until the subsequent direction reconfigure being
triggered. Then UL DCH and DL DCH doing the reconfiguration in one step. This fuction
saves the delay of Uu.
Bit rate Adaptation in one step is apply to channel configuration triggered by traffic.
Other trigger elements will do reconfigure directly. In case of timer time out, doing the
reconfiguration of one direction directly.
With UL&DL DRB C switch opening, the correlated situations as following:
 UL DCH -> UL DCH(rate inc reas e)based on traffic
If UL DCH satisfied rate increase conditions in advance,start timer UpUdRecfgTimer
If before UpUdRecfgTimer time out, DL DCH satisfied rate increase triggered by

traffic,DRBC increase UL and DL DCH rate in one reconfigure process ,if it is failed, try
DL rate increase,if it is fail again or UpUdRecfgTimer time out, then trying UL rate
increase.
If before UpUdRecfgTimer time out, DL DCH satisfied rate decrease triggered by

traffic,DRBC inc rease UL DCH rate while in the same reconfiguration decrease the DL
DCH rate,if it is failed, try DL rate decrease;Ot herwise,DRB C proc ess UL DCH rate
increase, when time out.
If before UpUdRecfgTimer time out,UL DCH is not satisfied rate inceas e conditions
anymore, stop the UpUdRecfgTimer, and do not reconfigure UL DCH.
 DL DCH -> DL DCH(rate inc reas e)based on traffic
If DL DCH satisfied rate increase conditions in advance,start timer UpUdRecfgTimer
If before UpUdRecfgTimer time out, UL DCH satisfied rate increase triggered by traffic,
DRB C increase UL and DL DCH rate in one reconfigure process ,if it is failed, try DL rate
increase,if it is fail again, try to increase UL DCH rate, Ot herwise,DRB C process DL
DCH rat e increase,when time out.
If before UpUdRecfgTimer time out, DL DCH satisfied rate decrease triggered by

traffic,DRBC decrease UL DCH rate while in the same reconfiguration increase the DL
DCH rat e,if it is fail or UpUdRecfgTimer time out, then trying UL rate decrease.
If before UpUdRecfgTimer time out,DL DCH is not satisfied rate inceas e conditions
anymore, stop the UpUdRecfgTimer, and do not reconfigure DL DCH.
 UL DCH -> UL DCH(rate decrease)based on traffic

If UL DCH satisfied rate decrease conditions in advance,start timer DnUdRecfgTimer
If before DnUdRecfgTimer time out, DL DCH satisfied rate decrease triggered by traffic,
DRB C decrease UL and DL DCH rate in one reconfigure process,if it is failed or
UpUdRecfgTimer time out, then trying UL rate decrease.
If before DnUdRecfgTimer time out, DL DCH satisfied rate increase triggered by

traffic,DRBC decrease UL DCH rate while in the same reconfiguration increase the DL
DCH rat e,if it is failed or DnUdRecfgTimer time out, then trying UL DCH rate decrease.
If before DnUdRecfgTimer time out,UL DCH is not satisfied rate decease conditions
anymore, stop the UpUdRecfgTimer, and do not reconfigure UL DCH.
 DL DCH -> DL DCH(rate decrease)based on traffic
If DL DCH satisfied rate decrease conditions in advance,start timer DnUdRecfgTimer
If before DnUdRecfgTimer time out, UL DCH satisfied rate decrease triggered by

traffic,DRBC decrease UL and DL DCH rate in one reconfigure process,if it is failed or
DnUdRecfgTimer time out, then trying DL rate decrease.
If before DnUdRecfgTimer time out, UL DCH satisfied rate increase triggered by

traffic,DRBC inc rease UL DCH rate while in the same reconfiguration decrease the DL
DCH rat e,if it is failed or DnUdRecfgTimer time out, then trying DL DCH rate decrease.
If before DnUdRecfgTimer time out,DL DCH is not satisfied rate decease conditions
anymore, stop the DnUdRecfgTimer, and do not reconfigure DL DCH.
3.1.4 Related Measurement
3.1.4.1 Traffic Measurement
The traffic meas urement includes the BO measurements of UTRA N and UE service
buffer capacities, which are respectively meas ured from the user plane and UE.
RLC mode of Traffic measurement report is decided by MeasRptTrMod. If AM mode is

selected, RNC will require UE ret ransmit error or discontinue SDU. If UM mode is
selected, retransmission is not available. The quantity of traffic measurement is
controlled by MeasQuantity; MeasQuantity could be 1:RLC buffer payload, 2:A verage
RLC buffer payload 3:Variance of RLC buffer payload. In traffic measurement control
message, whether report the RLC BO is indicated by RptRlcBufInd, average RLC BO is
indicated by RptRlcAveInd and varianc e of RLC BO is indicated by RptRlcVarI nd..
For services using AM RLC mode to transmit data, the BO value of a RB is the sum of
RLC queue-to-s end, retransmission queue, and data in logical channel. The user plane
uses the average of BO sample values collected in AverageTime to trigger the event.
The UE uses BO sample values collected in 20 ms to trigger the event. Measurement

report of RNC accept periodic report or event report is decided by UeTrfRptMed, In

traffic measurement control message, Periodical Reporting / Event Trigger Reporting
Mode IE take the value of RptCrt.
Relat ed events with traffic measurement include:
 E vent 4A: the event is triggered when the traffic measurement value exceeds an
absolute threshold and this condition lasts for a certain period
(TrigTime[ MAX_UE_TRV_MEAS_EVE NT]). Delay timer
PendingTime[MAX _UE _TRV _MEAS_EVENT] is set to prevent triggering frequently
the event.
 E vent 4B: the event is triggered when the traffic measurement value is smaller than
an absolute threshold and this condition lasts for a certain period
(TrigTime[ MAX_UE_TRV_MEAS_EVE NT]). Delay timer
PendingTime[MAX _UE _TRV _MEAS_EVENT] is set to prevent triggering frequently
the event.
 E vent 4B0: the event is triggered when the traffic measurement value is 0 and this
condition lasts for a certain period (TrigTime[MAX _UE _TRV _MEAS_EVENT] ). 4B0
event is an exceptional case in 4B events, its delay timer
PendingTime[MAX _UE _TRV _MEAS_EVENT] is the same as that of 4B event.
Where, the absolute thresholds for different channels acquire different parameters,
which is as below. TrigTime[ MAX_UE_TRV_MEAS_EVE NT] is the interval between the
time when the event is observed and the time when the event is reported.
PendingTime[MAX _UE _TRV _MEAS_EVENT] is the screening period during which the
event which has occurred is prevent ed from reoccurring. The followin g figure shows the
report of 4A event based on the principles of trigger time and pending time.
Figure 3-2 E vent Triggering of Traffic Measurement
Traffic Volume
Thr_4A
Pending
Pending
Trigger Time Trigger
Time Trigger
Time Time Time
Report 4A Report 4A Report 4A
The time of trigger channel switching is calculated as below:
Time = Counter Threshold * TiggerTime + (Counter Threshold - 1)*PendingTime

The absolute t hreshold (such as parameter RptThres[MAX _UE _TRV _MEAS_EVENT] )

is configured as follows:
 The smaller the threshold value of 4A event is, the quicker the system responses to
the service demand of the UE, and the sooner the bandwidth increase is triggered,
so as to allocate more radio res ources. And vice versa.
 The bigger the threshold value of 4B event is, the quicker the system responses to
the service demand of the UE, and the sooner the occupied bandwidt h is
decreased. And vice versa.
The parameters TrigTime[MA X_UE _TRV_MEAS_EVENT] and PendingTime[MA X

_UE_TRV_MEAS_EVENT] are configured as follows:
 The smaller the value of TrigTime[MA X_UE_TRV_MEAS_EVENT] for 4A event is,

the quicker the control plane receives the reports and increases the bandwidth
when the traffic measurement meets the threshold for triggering the event 4A.
Therefore, the demand of service rate of UE is reflected in a better w ay. And vice
versa. However, if the parameter is configured with a very low value, the system
will response t o the service demand which fluctuates in a very short moment,
resulting in unnecessary bandwidth inc reas e.
 The smaller the value of PendingTime[MA X_UE_TRV_MEAS _EVENT] for 4A

event is, the quicker the control plane receives consecutively the reports and
increases the bandwidth when the traffic measurement meets the threshold for
triggering the event 4A. Therefore, the demand of service rate of UE is reflected in
a better way. And vice versa. However, if the paramet er is configured with a very
low value, reporting event 4A will resulting in considerable bandwidth occupation.
 The smaller the value of TrigTime[MA X_UE_TRV_MEAS_EVENT] for 4B event is,

the quicker the control plane receives consecutively the reports and decreases the
bandwidth when the traffic measurement meets the threshold for triggering the
event 4B. Therefore, the demand of service rate of UE is reflected in a better way.
And vice versa. If the parameter is configured with a very low value, the system will
response to the service demand which fluctuat es in a very short moment, resulting
in unnecessary bandwidth decrease.
 The smaller the value of PendingTime[MA X_UE_TRV_MEAS_EVE NT] of 4B event

is, the quicker the cont rol plane receives consec utively the reports and decreas es
the bandwidth when the traffic measurement meets the threshold for triggering the
event 4B. Therefore, the demand of service rate of UE is reflected in a better way.
And vice versa. However, if the parameter is configured with a very low value,
reporting event 4B will res ulting in considerable bandwidth occupation. Therefore,
the feeling of subscriber and bandwidth utilization should be taken into
consideration before configuration.
The rate increase process is triggered when the control plane or UE receives the
consecutive reports of event 4A and the 4A_counter >= 4A _threshold; while the rate

decrease process is triggered when the control plane or UE rec eives the consecuti ve
reports of event 4B and the 4B_counter > =4B_threshold. Where, 4A_threshold and
4B_threshold are configured with different OMC parameters based on different types of
channel switching. The figure below shows the rate adjustment process (no event
counter configured):
Figure 3-3 Rate Adjustment Triggered by Traffic
pending-time-after- Reporting event

trigger 4A
time-to-trigger Increasing Rate
Reporting event
4B
Thr_4A Decreasing Rate
Thr_4B time-to-trigger
pending-time-after-
Report Report trigger
4A 4B
The traffic measurement uses the parameter MeasE vtNum to define its number (2 at
present) of events. The two events are the event 4A and event 4B corresponding to
parameter MeaE vtId[MAX _UE _TRV _MEAS_EVENT] which are valid only for event
reporting.
Parameter TxI nterCfgPre[MAX _UE _TRV _MEAS_EVENT] decide whether forbid RA CH

data after measurement report., and the forbidden time is decided by
TxInterruption[ MAX_UE_TRV_MEAS _EVENT].
Measure parameter acquisition method: when the traffic parameter is obtained, obtain
the corresponding configuration number UeTrvMCfgNo from the UE traffic measurement
configuration of the cell based on the cell identity Cid and measurement target (uplink
DCH traffic measurement DrbcDchUeE vt, downlink DCH traffic measurement
DrbcDchUp, RACH traffic meas urement DrbcRachUeEvt, and FACH traffic
measurement DrbcFachUp), and then follow the following path to obtain corresponding
traffic meas urement parameter bas ed on the configuration number: RNC NE -> RNC
Radio Resource Management -> Modify Advanced Parameter -> UE Traffic Volume
Measurement Configuration:
 If t he uplink channel for service bearer is the DCH, the traffic is meas ured on the
UE side, and the related paramet er which is adopt ed to measure the t raffic is the
corresponding parameter of UE Traffic Volume E vent Measurement Configuration
Number for DCH.

 The 4A /4B threshold of every uplink DCH rate level adopts the parameters
under this configuration number. Such as, 8kbps uses the value of
Rpt Thres0[MA X_UE_TRV_MEAS _EVENT], 16k bps uses the value of
Rpt Thres3[MA X_UE_TRV_MEAS _EVENT], 128kbps uses the value of
Rpt Thres6[MA X_UE_TRV_MEAS _EVENT].
 The values of TrigTime[MA X_UE _TRV _MEAS_EVENT] and

PendingTime[MA X_UE _TRV _MEAS_EVENT] of event 4A and 4B of uplink
DCH are the values under corresponding configuration number.
 If the downlink channel for service bearer is the DCH, the traffic is measured on the
user plane side, and the related parameter which is adopted to measure the traffic
is the corresponding parameter of UP Traffic Volume Measurement Configuration
Number for DCH.
 The 4A /4B threshold of every downlink DCH rat e level adopts the parameters
under this configuration number. Such as, 8kbps uses the value of
Rpt Thres6[MA X_UE_TRV_MEAS _EVENT].

PendingTime[MA X_UE _TRV _MEAS_EVENT] of event 4A and 4B of downlink
DCH are the values under corresponding configuration number.
 If the uplink channel for service bearer is the RACH, the traffic is measured on the
UE side, and the related paramet er which is adopt ed to measure the t raffic is the
corresponding parameter of UE Traffic Volume E vent Measurement Configuration
Number for RA CH.
 The reporting thresholds of event 4A and 4B on the RA CH is determined by

the parameter RptThres[MA X_UE_TRV_MEAS_EVENT] under this
configuration number. (Note: there is no related policy for the event 4B
threshold for RA CH.)

PendingTime[MA X_UE _TRV _MEAS_EVENT] of event 4A and 4B of RACH
are the values under corresponding configuration number.

 If the downlink channel for service bearer is the FACH, the traffic is measured on
the user plane side, and the related parameter which is adopted to measure the
traffic is the corresponding parameter of UP Traffic Volume Measurement
Configuration Number for FACH.
 The reporting thresholds of event 4A and 4B on the FACH is determined by

the parameter RptThres[MA X_UE_TRV_MEAS_EVENT] under this
configuration number. (Note: there is no related policy for the event 4B
threshold for FA CH.)
 The values of TrigTime[ MAX_UE _TRV _MEAS_EVENT] and

PendingTime[MAX _UE _TRV _MEAS_EVENT] of event 4A and 4B of FACH
are the values under corresponding configuration number.
 If t he channel for servic e bearer is the uplink DCH, the traffic is meas ured on the
UE side, and if the related paramet er which is adopted to measure the traffic is the
corresponding parameter of UE Traffic Volume Period Measurement Configuration
Number for DCH:
 The times limitition of periodical report is determined by PrdRptAmount

accorording to UeTrvMCfgNote (0 for DCH)
 Time interval for preiod reports is deternimed by PrdRptInterval accorording

to UeTrvMCf gNote (0 for DCH)
 If the channel for service bearer is the RACH, the traffic is measured on the UE
side, and if the related parameter which is adopted to measure the traffic is the
corresponding parameter of UE Traffic Volume Period Measurement Configuration
Number for RA CH.
 The times limitition for periodical report is determined by PrdRptAmount

accorording to UeTrvMCfgNote (3 for RA CH)
 Time interval for preiod reports is deternimed by PrdRptInterval accorording

to UeTrvMCf gNote (3 for RACH)
 Note:Measurement parameter to transport channel corresponce by Measobj .
3.1.4.2 UE internal TxP Measurement
The UE internal measurement mainly measures the UE transmission power (TxP) by

event report, with the reporting threshold of the percent of the maximum UE TxP. It
defines the 6A and 6B statuses, whose relationships with corresponding events 6A1,
6B1, 6A2, and 6B2 are as follows:

Figure 3-4 TxP Measurement Rationale
Tx Power
Trigger
Time
Thr_6A1 Trigger
Thr_6B1 Time
Trigger
Time
Thr_6A2
Trigger
Time
Thr_6B2
Report Report Report Report

6A 6B 6B 6A
Two sets of measurement paramet ers are configured:
 E vent 6A1, E vent 6B 1: when the UE TxP measurement value is greater than a
certain absolute threshold and this condition lasts for a moment (100 ms), the
E vent 6A 1 is triggered; when the UE TxP measurement value is smaller than a
E vent 6B1 is triggered. The UE is in a high power status (6A status), RNC would
decrease rate periodically with period of 2ms. when the event 6A1 is report ed, and
the uplink rate can be decreased; the UE is not in a high power status (non-
adjustment status) when the event 6B1 is report ed, and the decreasing of uplink
rate is stopped. The thres hold defined for E vent 6B1 can be used as the cut-off
threshold for uplink rate decrease.
 E vent 6A2, E vent 6B 2: when the UE TxP measurement value is greater than a
E vent 6A 2 is triggered; when the UE TxP measurement value is smaller than a
E vent 6B 2 is triggered. It is used to check whether the UE TxP is in a low level. The
UE is in a low power status (6B status) when the event 6B2 is reported, and the
uplink rat e can be inc reased; the UE is not in a low power status (non-adjustment
status) when the event 6A2 is reported, and the inc reasing of uplink rate is stopped.
The higher the value of event 6A1 is, the harder uplink DCH rate decrease can be
triggered based on power, that is, the UE TxP will be higher with more power
consumption and interference with other subscribers. If the power consumption and
interference with ot her subscribers are not taken into consideration, the event 6A1 can
be configured with a high value; the lower the value of event 6A1 is, the easier the uplink
DCH rate dec rease can be triggered by the power, and then the feeling of the subscriber
is affected. If the value of event 6B1 is very small, the UE rate will be continuously
decreased and the feeling of the subscriber is affected. If the value of event 6B1 is very
high, the high power status may not be removed effectively. Based on the above factors,
the values of events 6A1 and 6B1 are [100%, 85%]. The higher the threshold of event

6B2 is, the easier the report ed power can stay in 6B status, so as to retrigger the rate
increase by the traffic. However, a certain margin should be configured between the
thresholds of event 6A1 and event 6B2, otherwise, there may be a situation: after the
rate is dec reased based on event 6A1, the rat e increase is triggered by the traffic
demand; the lower the threshold of event 6B2 is, the harder the reported power can stay
in 6B status, that is, it is harder to trigger the rate decrease by traffic. Thus, the feeling of
the subscriber is affected. Based on the above factors, the values of events 6A2 and
6B2 are [80%, 60%].
If PS services exist, and uplink DRB C DrbcS wch is open with the UE in the CELL_DCH
state, the measurement is triggered. If the condition is not met, the UE TxP
measurement is closed.
3.1.4.3 NodeB Dedicated TCP Measurement
If the NodeB dedicated TCP is related with the UE, single UE uplink TxP (the TxP on
given carrier, given scramble, and given channelization code) is measured by the NodeB.
It acts as a factor for triggering bandwidth decrease as well as a restriction for bandwidth
increase. If the NodeB dedicated TCP measurement which is used to trigger DRBC rate
adjustment is report ed periodically, the period is 1000 ms.
For events based on the D-TCP measurement reports of NodeB, their thresholds are
configured to be the percent of DP CH downlink maximum transmission power which is
related with service type. The D-TCP measurement of NodeB defines the events A and
B.
Two sets of measurement paramet ers are configured:
 E vent A: when t he NodeB D-TCP measurement value is greater than a specific

absolute threshold, event A is triggered. E vent A is used to trigger the downlink rate
decrease. When an event A is reported, the downlink transmission power of UE is
considered to be in a high power status.
 E vent B: when the NodeB D-TCP measurement value is smaller than a specific
absolute threshold, event B is triggered. The event B is used to check whether the
downlink transmission power is in a low status. When an event B is report ed, the
downlink transmission power of UE is considered to be in a low power status. The
downlink rat e increase can be triggered by traffic.
The higher the value of event A is, the harder the downlink DCH rate decreas e can be
triggered by the power, that is, the power of single UE is higher. If the system power
restriction is not taken into consideration, the event can be c onfigured with a high value;
the lower the value of event A is, the easier the downlink DCH rate decrease can be
triggered by the power, and then the feeling of the subscriber is affected.
The higher the threshold of event B is, the easier the reported power can stay in B status.
However, a certain margin should be configured between the thres holds of event A and

event B, otherwise, there may be a situation: after the rate is decreased based on event
6A1, the rat e increase is triggered by the traffic demand; the lower the threshold of event
B is, the harder the reported power can stay in B status, that is, it is harder to trigger the
rate increase by traffic. Thus, the feeling of the subscriber is affected.
Based on the above factors, the values of events A and B are [90%, 80%].
If PS services exist, and downlink DRBC DrbcSwch is open with the UE in the
CELL_DCH state, the measurement is triggered. If the condition is not met, the NodeB
dedicated TCP measurement is closed.
3.2 HSDPA Dynamic Channel Adjustment
3.2.1 Signaling Channel Allocation
The signaling channel allocation process upon the RRC connection setup is the same as
the R99 policy.
For the setup of RAB allocation service, the signaling channel is selected by the
following principles:
 The low-speed bearer signaling DL DCH/UL DCH is selected if there is DL DCH/ UL

DCH bearer service.
 If all the servic es are on the DL HS-DSCH/UL DCH: If both t he cell and UE support
F-DP CH, and Liscence FDpchS uptInd is support, then the signaling is on the DL
HS-DSCH/UL DCH; otherwise, the signaling is mapped to DCH/DCH low rate
signaling.
3.2.2 Initial Service Channel Allocation
the service features (RAB parameters). For t he HS-DSCH in the HS UPA cells, the
selectable channel types as follows:
 Conversation servic es use DL DCH/UL DCH channels.
 Streaming services can use DL HS -DS CH/UL DCH and DL DCH/UL DCH channels.
 Interactive and background s ervices can use DL HS-DS CH/ UL DCH, DL DCH/ UL
DCH, and DL FA CH/ UL RA CH channels.

Channel allocation of the HSDPA UE in the R99 is the same as that for R99 initial
service.
1. For the UE supporting only HS-DS CH in the HSDPA cell:
2. CS 64k service
3. The principles for CS 64k service is the same as R99, pleas e check “3.1.2.2 Initial
Service Channel Allocation”.
4. The principles for selecting channels for streaming services are as follows:
If the condition of [channel quality as non-1F event] is met, select the DL HS-DSCH/UL
DCH with priority. If selecting the DL HS -DS CH/UL DCH is failed (for example, downlink
HS-DSCH is failed to admit), select the DL DCH/ UL DCH.
Otherwise, streaming services use DL DCH/ UL DCH.
The E vent 1F is defined as that the measurement value Ec/N o is smaller than an
absolute threshold. See 3.2.4.1”Pilot Channel Quality Measurement” for the detailed
definition.
1. The principles for selecting the channel type for int eractive and background
services are as follows:
If dlMaxBR >= Rfach or ulMaxBR >= Rrach, select the CELL_DCH.
Otherwise, select the DL FACH/UL RA CH with priority. If the DL FACH/UL RACH is

failed to admit, select the CELL_DCH.
When the CE LL_DCH is selected:
If the condition of [channel quality as non-1F event] is met, select the DL HS-DSCH/UL
DCH with priority. If selecting the DL HS -DS CH/UL DCH is failed (for example, downlink
HS-DSCH is failed to admit), select the DL DCH/ UL DCH.
Otherwise, interactive and background services use DL DCH/UL DCH.
For the UE selecting DL HS-DSCH/UL DCH, the way to determine the initial rate for PS
(S/I/B) service on the UL DCH is the same as that for R99. The rate of the DL HS -DS CH
is controlled by the NodeB in real time, out of the control of the RNC. For the UE
selecting the DL DCH/UL DCH, the way to determine the initial rates for DL DCH and UL
DCH are the same as that for R99.
online call service. All concurrent PS services use the same channel as bearer.

Channel allocation for the UE supporting only HS-DS CH in the HSDPA cell is as follows:
Concurrent
Channel Type
Service Types
If any of I/B services meet the condition of [dlMaxBR >= Rfach or
ulMaxBR >= Rrach] and the channel quality is non-1F event, select
the DL HS-DS CH/ UL DCH wit h pri ority. If selecting the DL HS -
DSCH/UL DCH is failed (for ex ample, downlink HS-DS CH is failed
to admit), select the DL DCH/ UL DCH.
I/B+I/B If all the I/B services meet the condition of [dlMaxBR < Rfach and
ulMaxBR < Rrach], select DL FACH/ UL RA CH with priority. If the
selecting is failed, and the channel quality is non-1F event, select
DL HS-DSCH/UL DCH. If selecting DL HS-DSCH/UL DCH is failed
(for example, downlink HS-DSCH is failed to admit), select DL
DCH/UL DCH.
CS services select the DL DCH/UL DCH.
If the UE meets the [downlink concurrent capabilities of the DP CH
and HS-DSCH for CS services] and channel quality is non-1F
event, select the DL HS-DSCH/UL DCH with priority for PS (I/B or
I/B+CS or
S) services. If selecting the DL HS-DS CH/UL DCH is failed (for
S+CS or
I/B+S+CS example, downlink HS-DS CH is failed to admit), select the DL
DCH/UL DCH.
If the UE does not meet downlink concurrent capabilities of the
DPCH and HS-DS CH for CS services, select the DL DCH/UL DCH
for PS (I/B or S) services.
If the condition of [channel quality as non-1F event] is met, select
the DL HS-DS CH/ UL DCH wit h priority. If selecting the DL HS -
I/B+S or S+S
(S/I/B) service on the UL DCH is the same as that for R99. The rate of the DL HS -DS CH
is controlled by the NodeB in real time, out of the control of the RNC. For the UE
selecting the DL DCH/UL DCH, the way to determine the initial rates for DL DCH and UL
DCH are the same as that for R99.
Channel allocation for UE supporting only HS-DSCH in the R99 cell is the same as that
for R99 concurrent service.
During the session, the dynamic channel s witching in the HS DPA system is to adjust the
service bandwidth and hand over channels in real time according to the measurements
of traffic and channel quality. The figure below shows the channel switching that the
system currently supports according to HSDPA protocols.

Figure 3-5 HSDPA Channel Switching
Transition of DCH/DCH -> FACH/RACH

Transition DL DCH -> DL HS-DSCH Reconfig SF
1. UL&DL Traffic Volume Based
1. DL Traffic Volume Based 1. UL/DL Traffic Volume
2. Support CELL_FACH
2. Channel Quality Measure Based Based
(Option) 2. DL D-TCP Based
Transition of HS-DSCH/DCH -> FACH/RACH
3. UE &Cell Capability 3. UL TxP Based
4. Cell’s RTWP
Transition DL HS-DSCH -> DL DCH 5. Cell’s TCP
1. Channel Quality Measure Based
Transition of FACH/RACH -> DCH/DCH
(Option)
1. UL/DL Traffic Volume Based
CELL_DCH RACH/FAC
H
HS-DSCH/DCH Transition of FACH/RACH -> HS-DSCH/DCH
DCH/DCH 1. UL/DL Traffic Volume Based
CELL_FACH 2. UE &Cell Capability
Transition of DCH/DCH -> PCH
2. Support PCH
Transition of FACH/RACH -> PCH
Transition of HS-DSCH/DCH -> PCH
2. Support PCH
2. Support PCH
Transition of PCH -> FACH/RACH
PCH 1. UL/DL Traffic Volume Based
Idle
URA_PCH
Transition of FACH/RACH -> IDLE
1. UL&DL Traffic volume Based
Transition of DCH/DCH -> IDLE
Transition of PCH->IDLE
Transition of HS-DSCH/DCH -> IDLE
1. DL&UL Traffic Volume Based
3.2.3.1 CELL_DCH(DL HS-DSCH/UL DCH) <-> CELL_FACH
1. CELL_DCH <-> CELL_FA CH switching triggered by traffic
i. CELL_DCH (DL HS -DS CH/ UL DCH) -> CE LL_FACH
When the UE is in the CELL_DCH status, the switching from CELL_DCH (DL HS-
DSCH/UL DCH) to CE LL_FACH can be triggered by the traffic measurement report
(E vent 4B) from the user plane and UE.
The switching from CE LL_DCH (DL HS -DS CH/UL DCH) to CELL_FA CH is

triggered in the case of the following conditions:
 The services are interacti ve or background services.

(E vent 4B) from the user plane, and consecutive ToFtimesThr traffic
measurement reports (E vent 4B ) from the UE,and switch is triggered by
downlink report. (Not e: if the system receives a traffic measurement report
(E vent 4A) from the user plane or UE when the receiving times are smaller
than the threshold, the corresponding counter is clear.)
 When the current uplink rate is smaller than the maximum uplink rate
threshold Rrach for RA CH (Note: if the current uplink rate is smaller than or
equal to the rate of minimum rate level for DCH, the RACH rate threshold
judgment is not required)

If the condition for CE LL_FACH switching is met, but the CELL_FA CH fails the
admission, and the current uplink rate is great er than the minimum rate that UL
DCH can bear, namely, the lowest rate level configured by UlRateA djLev
[MAX_NUM_RA TE_ADJ UST], UL DCH rate decrease is selected.
ii. CELL_FACH -> CE LL_DCH (DL HS-DSCH/UL DCH)
When the UE is in the CELL_FA CH status, the switching from CELL_FA CH to

CELL_DCH (DL HS-DS CH/ UL DCH) can be triggered by the traffic measurement
report (E vent 4A ) from the user plane or UE.
The switching from CE LL_FACH to CELL_DCH (DL HS-DS CH/UL DCH) is

 The system receives consecutive FachE4aThd traffic measurement reports

(E vent 4A) from t he user plane or UE. (Note: if the system receives a traffic
measurement report (E vent 4B) from the user plane or UE when the rec eiving
times are smaller than the threshold, the corresponding counter is cleared.)
 Both the terminal and system support HS -DS CH.
 The cell load is not overloaded. (Note: see the ZTE UMTS Overload Cont rol
Feature Guide for the overload threshold)
 The rate of UL DCH in the CELL_DCH (DL HS-DS CH/ UL DCH) s witching is
the[UL Initial rate] for DRBC, see 3.1. 2.2.
2. CELL_DCH to CELL_FA CH switching triggered by load
the cell load.
The switching from CELL_DCH (DL HS -DS CH/UL DCH) to CE LL_FACH (DL FACH/UL
 The cell downlink load exceeds the overload threshold. (Note: see the ZTE
UMTS Overload Control Feature Guide for the overload thres hold.)
3.2.3.2 CELL_DCH (DL HS-DSCH) <-> DL DCH
1. Switching from DCH to HS -DS CH triggered by traffic

When the subscriber uses the DL DCH/UL DCH, the switching from DL DCH to DL HS-
DSCH can be triggered by the measurement report (E vent 4A) from the user plane to
increase the system capacity.
definition.
The switching from DL DCH to DL HS-DS CH is triggered in the case of the following
conditions:

4A) from the user plane. (Note: if the system receives a traffic measurement report
(E vent 4B) from the user plane when the receiving times are smaller than the
 The channel quality does not report 1F event.
 Both the terminal and system support HS -DS CH.
Note: HS -DS CH cannot switch to DCH based on traffic volume measurement.
Special cases of concurrent services during channel switching:
 If all the concurrent services are PS services and one servic e triggers the s witching
from DL DCH to DL HS-DSCH, the DL DCH of all services is switched to DL HS-
DSCH.
 If there is CS service in the conc urrent services and t he UE is capable of the DL

DCH and DL HS -DS CH concurrency (maximum rate on the DP CH is report ed by
the UE), the DL DCH of only PS services is switched to DL HS-DSCH; otherwis e,
the switching is not implemented.
If t he service is on the DCH, the event 4A triggered by the user plane meets the
condition for rate increase in the DL DCH -> DL HS-DSCH switching, but the DL HS-
DSCH fails the admission or the DL HS -DS CH is not supported, select DL DCH rate
increase, and the uplink remains on the DCH. In the case of DL DCH rate increase, the
other conditions of DL DCH rate increase must be satisfied (see DL DCH -> DL DCH
(rate increas e)).
When the UE is in non-macro diversity, determine the target rat e for DL DCH rate
increase as follows:
Uplink rate increasing see 3.1.2.6,while downlink rate inc reasing see 3.1.2. 4
When the UE is in macro diversity, determine the target rate for DL DCH as follows:
Uplink rate increasing see 3.1.2.6,while downlink rate inc reasing see 3.1.2. 4

macro diversity.
2. Switching from HS-DSCH to DCH triggered by channel quality
When a s ubscriber is using the DL HS-DS CH/ UL DCH, the DL HS -DS CH s witching to
DL DCH can be triggered by channel quality measurement (E vent 1F triggered by pilot
signal). This is because that the subscriber remaining on HS-DSCH will worsen the QoS
and lower the system capacity when the bit rate requirements of streaming services
carried on HS-DSCH are not satisfied and the channel quality deteriorates.
definition.
The switching from DL HS -DS CH to DL DCH is triggered in the case of the following
conditions:
 Channel quality measurement switches for the current PS service (IBChQS wc h,

SChQS wch) are open (Note: when PS S and I/B service are concurrent, if any of
IBChQS wc h and SChQS wch is open, these switches are considered open).
 The channel quality triggers E vent 1F.
Handling principle of concurrent services in c hannel s witching: if the concurrent services

are PS services, the DL HS -DS CH for all the services are switched to DL DCH.
During the fallback from DL HS-DS CH to DL DCH, the rate is the DRBC initial rate, see
3.1.2.2
3. HS-DSCH <-> DCH Switching triggered by mobility
During the PS services carried on downlink HS-DSCH, when the UE hands over from an
HSDPA cell to R99 cell for mobility but the t arget cell does not support the HS-DSCH,
the downlink channel will switch from HS-DS CH to DCH. The rate is the DRB C initial
rate, see 3.1.2.2
During the PS servic es carried on DL DCH/UL DCH, the UE may roam from a R99 cell
to HSDPA cell by hard handover for mobility. If the t arget cell and UE support the
HSDPA, the switching from DL DCH to DL HS -DS CH occurs along with the handover.
3.2.3.3 CELL_DCH (DL HS-DSCH/UL DCH) -> URA_PCH
When the UE uses the CELL_DCH (DL HS -DS CH/ UL DCH) for service bearer, the
switching from CELL_DCH (DL HS-DS CH/UL DCH) to URA_P CH can be triggered by
the traffic measurement report (E vent 4B0) from the user plane or UE.

The E vent 4B0 is defined as that the value of traffic measurement val ue is 0. See
The switching from CELL_DCH (DL HS-DSCH/UL DCH) to URA_P CH is triggered in the
case of the following conditions:
measurement value of 0 from the user plane and UE (Note: if the system receives a
report with measurement value of non-zero value when the receiving times are
3.2.3.4 CELL_DCH(DL HS-DSCH/UL DCH) -> IDLE
When the UE uses the CELL_DCH (DL HS -DS CH/ UL DCH) for service bearer, the
switching from CELL_DCH (DL HS -DS CH/ UL DCH) t o IDLE is triggered in the case of
the following conditions:
 The system receives consecutive DToIdleThd traffic measurement reports with

measurement value of 0 from the user plane and UE. (Note: If t he system rec eives
the measurement reports with traffic measurement value of non -zero value when
the rec eiving times are smaller t han the threshold, the c orresponding counter is
cleared.)
When the c hannel is changed to IDLE, the occupied radio resources are released and
3.2.4.1 Pilot Channel Quality Measurement
The channel quality meas urement is for the switching from HS -DS CH to DCH. The
E vent 1E and E vent 1F are used in the measurement.

The channel quality measurement CQ is performed on the P-CP ICH. If the UE supports
HS-DSCH, the measurement is initiated.
1E definition: when the pilot signaling quality is greater than an absolute threshold
(ThreshUsedFreq[MAX _INTRA_MEAS_EVE NT]) and this condition lasts for a moment
(TrigTime[ MAX_INTRA _MEAS_EVENT]), event 1E is triggered.
1F definition: when the pilot signaling quality is worse than an absolute threshold
(ThreshUsedFreq[MAX _INTRA_MEAS_EVE NT]) and this condition lasts for a moment
(TrigTime[ MAX_INTRA _MEAS_EVENT]), event 1F is triggered.
For more details of the parameter ThreshUsedFreq[MA X_INTRA_MEAS_EVE NT] and

TrigTime[MA X_INTRA_MEAS_EVE NT], see ZTE UMTS Handover Control Feat ure
Guide.
The figure below shows the rationale of E vent 1E:
Figure 3-6 E vent 1E in Channel Quality Measurement
Measurement
Quantity
P CPICH 1
P CPICH 2
Absolute
threshold
P CPICH 3
Trigger Time
Report 1E
The figure below shows the rationale of E vent 1F:

Figure 3-7 E vent 1F in Channel Quality Measurement

Measureme
nt
Quantity
P CPICH 1
Trigger
P CPICH 2 Time
Absolute
threshold
P CPICH 3
Report 1F
The traffic measurement on HS -DS CH indicat es the BO meas urement of UTRAN

service buffer capacity measured by the user plane.
For services bear on HS-DSCH, data is transmitted using AM RLC mode. The statistical
strategy for a specific BO of RB is: the AM RLC takes the RLC sent, to be sent currently,
retransmission data in the last 20 ms as the BO in the current 20 ms. The UE uses BO
sample values collected to trigger the event.
Measure parameter acquisition method: For a service on the DL HS-DS CH/UL DCH,
see traffic measurement on the R99 for acquisition of traffic parameters on the UL DCH.
Acquisition of traffic parameters on the DL HS-DSCH: when traffic parameters are
acquired, obtain the corresponding configuration number UeTrvMCfgNo from the UE
traffic volume measurement configuration relationship according to the cell identity Cid
and measurement purpos e (downlink HS-DS CH traffic measurement DrbcSHsUp for
streaming service, and downlink HS_DSCH traffic measurement DrbcIBHsUp for
interactive and background services ). Then according to the configuration number,
obtain the corresponding traffic volume meas urement parameters in RNC NE -> RNC
Radio Resource Management -> Modify Advanced Parameter -> UE Traffic Volume
Measurement Configuration:
 If the downlink channel for the service is the HS-DS CH, traffic volume
measurement is performed on the user plane and related parameters used in the
traffic volume measurements are parameters corres ponding to the UP Traffic
Volume Measurement Configuration Number for Streaming Class on HS -DS CH
and UP Traffic Volume Measurement Configuration Number for Interactive and
Background Class on HS-DS CH.

 In HS-DS CH, the reporting thresholds for events 4A and 4B for I/B and S
services are determined by the paramet er
RptThres[ MAX_UE_TRV_MEAS_EVENT] under this configuration number.
 TrigTime [MAX_UE_TRV_MEAS _EVENT] and PendingTime

[MAX_UE_TRV_MEAS_EVE NT] values for events 4A and 4B for I/B and S
services on the HS -DS CH are corresponding to those under this configuration
number.
3.3 HSUPA Dynamic Channel Adjustment
3.3.1 Signaling Channel Allocation
The signaling channel allocation process upon the RRC connection setup is the same as
the R99 policy.
For the setup of RAB alloc ation service, the signaling channel switching complies with
the following principles:
 The low-speed bearer signaling DL DCH/UL DCH is selected if there is DL DCH/ UL

DCH bearer service.
 If all the services are on the DL HS-DSCH/UL DCH: If both the system and UE
support F-DP CH, and Liscence FdpchS uptInd is support,then the signaling is on
the DL HS -DS CH/ UL DCH; otherwise, the signaling is mapped to DCH/DCH low
rate signaling.
 If all the services are on the DL HS -DS CH/ UL E-DCH:
a)If Liscence FourEChAllowed is supported, switch on SrbOnE dchS wch,
 If UE and cell both supported F-DP CH, and License FDpchSuptInd is set to be
supported，signaling bear on HS-DSCH/E-DCH.
 Otherwise signaling bear on DCH/E-DCH
b)If Liscence FourEChAllowed isn‟t supported, switch off SrbOnEdchS wc h, signaling bear
on DCH/ DCH

3.3.2 Initial Service Channel Allocation
the service features (RAB parameters). For the HS UPA UE in the HS UPA cell s, select
the following channel types as follows:
 Conversation servic es use DL DCH/UL DCH.
 Streaming services can use DL HS-DSCH/UL E-DCH, DL HS-DSCH/UL DCH, and

DL DCH/UL DCH.
 Interactive and background services can use DL HS-DS CH/UL E-DCH, DL HS-
DSCH/UL DCH, DL DCH/ UL DCH, and DL FACH/UL RA CH.
For the UE, supporting HSUPA, in HS UPA cell:
1. CS 64k service
The principles for CS 64k service is the same as R99, please check “3.1. 2.2 Initial
Service Channel Allocation”.
2. The principles for selecting channels for streaming services are as follows:
If the condition of [channel quality as non event 1F] is met, select the DL HS-DSCH/UL
E-DCH wit h priority. If selecting the DL HS-DSCH/UL E-DCH is failed (for example,
uplink E-DCH is failed t o admit), select the DL HS -DS CH/ UL DCH. If selecting the DL
HS-DSCH/UL DCH is failed (for example, downlink HS-DSCH is failed to admit), select
the DL DCH/UL DCH.
Otherwise, streaming services use the DL DCH/ UL DCH.
3. The principles for selecting the channel type for int eractive and background
services are as follows:
If dlMaxBR >= Rfach or ulMaxBR >= Rrach, select the CELL_DCH.
Otherwise, select the DL FACH/UL RA CH with priority. If the DL FACH/UL RACH is

failed to admit, select the CELL_DCH.
When the CE LL_DCH is selected:
If the condition of [channel quality as non event 1F] is met, select the DL HS-DSCH/UL
E-DCH. If selecting the DL HS-DSCH/UL E-DCH is failed (for example, uplink E-DCH is
failed to admit), select the DL HS -DS CH/UL DCH. If selecting the DL HS-DSCH/UL DCH
is failed (for example, downlink HS-DS CH is failed to admit), select the DL DCH/UL DCH.

Otherwise, interactive and background services select the DL DCH/ UL DCH.
(S/I/B) service on the UL DCH is the same as that for R99. The real time rate of the DL
HS-DSCH and UL E-DCH are controlled by the NodeB in real time, out of the control of
the RNC.
Configure principal of E-DCH max bit rate, which is the max bit rate for schedule and
non-schedule data from Node B:
If E-DCH traffic is Non-Realtime, The max bit rate configured in Node B is

min(NrtMax RateE Dch_new in avery cell of E-DCH activity set, MaxB R,MaxRateEdch)
Thereinto the definition of NrtMaxRateE Dch_new is as following:

RNC:NrtMaxRateEDch_new = NrtMaxRateEDch
RNC:NrtMaxRateEDch_new = NrtMaxRateEDchD
 And if S erving-RNC is unable to know Nrt MaxRateE DchD,then

Nrt MaxRateE DchD= 5.76Mbps.
RT Traffic is min(RtMax RateE Dch_new in avery cell of E-DCH activity set,

MaxB R, MaxRateEdch)
Thereinto the definition of RtMaxRateEDc h_new is as following:

RNC:RttMaxRateE Dch_new = RtMaxRateE Dch
RNC:RtMax RateE Dch_new = RtMaxRateEDchD
 And if Serving-RNC is unable to know Rt MaxRateE DchD,then

RtMaxRateEDchD=5.76Mbps.
Configuration explainations: Nrt MaxRateE Dch is the rate restriction of NRT Traffic on
E-DCH, RtMaxRateEDch is the rate restriction of RT Traffic on E-DCH .
Nrt MaxRateE DchD is cells in S RNC configure in DBS for cells in DRNC, which is also
the NRT Traffic rate restrictions. RtMaxRateE DchD is cells in SRNC configure in DBS
for cells in DRNC, which is also the RT Traffic rate restrictions. MaxRat eEdch is
calculated by former platform,for E-DCH max rate configuration.
The principal of acquiring the restriction rat e of E-DCH concurrent service:

>> Concurrent servic e are RT and NRT:the max bit rate of the concurrent servic e is the
bigger of RT and NRT restriction rates. That is because E-DCH not process distinguish
RAB. it is calculated min SF and max SF.then calculate the rate restriction.
>> Concurrent of more than one GB R service: Comparing the biggest GBR with
restriction rat e RtMaxRateEDc h.
>> When adding RL to cells which belong to DRNC, if current rate is bigger than rate
restriction of new cell, access denial.
>> If Uplink traffic GBR exceed Rt MaxRateE Dch,Access denial.
For the UE selecting the DL DCH/ UL DCH, the way to determine the initial rate for PS
(S/I/B) service on the DL DCH and UL DCH is the same as that for R99.
Note: The UL E-DCH and DL HS -DS CH need be bound for use in service channel
allocation, that is, there is no combination of DL DCH/UL E-DCH.
Configuration Principle of E-TTI:
1. If either UE or activity cell do not support of 2ms E-DCH TTI, and if initial RB setup
on E-DCH, The traffic will use 10ms E-DCH TTI on condition of 10ms TTI could
satisfy GBR requirement.
2. If both UE and activity cell support 2ms E-DCH TTI, and initial RB setup on E-DCH:
iii If E -DCH TTI of new service is 10ms (whatever it is C class or not) : check
whet her the configured E-TTI could satisfy GB R requirment, If satisfied, use
configured E-TTI.
iv If E-DCH TTI of new service is 2ms, and its class is not conversation:
 If 10ms E-TTI could satisfy GBR requirement, use 10ms E-DCH TTI and turn
on user plane meas urement for E-TTI transfer ; otherwise
 Check whether 2ms E-DCH TTI satisfy GB R requirement, If satisfy, use 2ms
E-DCH TTI.
online call service. All concurrent PS services use the same channel as bearer.
Channel allocation for the UE supporting HSUPA in the HSUPA is as follows:

Concurrent
Channel type
Service Types

If any of I/B services meets the condition of lMaxB R >= Rfach or

ulMaxBR >= Rrach, and channel quality is a non event 1F, select
the DL HS-DS CH/ UL E-DCH with priority. If selecting the DL HS-
DSCH/UL E-DCH is failed (for example, uplink E-DCH is failed to
admit), select the DL HS -DS CH/ UL DCH. If selecting the DL HS -
I/B+I/B If all the I/B services meet the condition of dlMaxBR < Rfach and
ulMaxBR < Rrach, select the DL FACH/UL RACH with priority; if
selecting is failed, channel quality is a non event 1F. Select the DL
HS-DSCH/UL E-DCH. If selecting the DL HS-DS CH/UL E-DCH is
failed (for example, the uplink E-DCH is failed to admit), select the
DL HS-DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH is
failed (for example, the downlink HS-DSCH is failed to admit),
select the DL DCH/UL DCH.
CS services select the DL DCH/UL DCH.
If the UE meets the uplink concurrent capabilities of the DP CH
and E-DCH, downlink concurrent capabilities of the DP CH and
HS-DSCH for CS services and channel quality is a non event 1F,
select the DL HS-DSCH/UL E-DCH with priority for PS (I/B or S)
services. If selecting the DL HS-DSCH/UL E-DCH is failed (for
example, uplink E-DCH is failed to admit), select the DL HS -
DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH is failed
(for example, downlink HS-DSCH is failed to admit), select the DL
I/B+CS or S+CS DCH/UL DCH.
or I/B+S+CS If the UE meets the downlink concurrent capabilities of the DP CH
and HS-DSCH for CS services but does not meet uplink
concurrent capabilities of the DPCH and E-DCH for CS servic es
and channel quality is a non event 1F, select the DL HS-DSCH/UL
DCH with priority for PS (I/B or S) services. If selecting the DL HS -
If the UE does not meet downlink concurrent capabilities of the
DPCH and HS-DS CH for CS services, select the DL DCH/UL DCH
for PS (I/B or S) services.
If channel quality is a non event 1F, select the DL HS-DSCH/UL E-
DCH. If selecting the DL HS-DSCH/UL E-DCH is failed (for
example, uplink E-DCH is failed to admit), select the DL HS -
I/B+S or S+S
DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH is failed
(for example, downlink HS-DSCH is failed to admit), select the DL
DCH/UL DCH.
(S/I/B) service on the UL DCH is the same as that for R99. The real time rate of the DL
HS-DSCH and UL E-DCH are controlled by the NodeB in real time, out of the control of
the RNC. For the UE selecting the DL DCH/ UL DCH, the way to determine the initial rate
for PS (S/I/B) servic e on the DL DCH and UL DCH is the same as that for R99.
Channel allocation of the HSUPA UE in the R99 is the same as that for R99 concurrent
service.
Channel alloc ation of the HS UPA UE in t he HSDPA is the same as that for HS DPA
concurrent service.

Conc urrent services on E-DCH:
New service is concurrent service:
If the new service is conversation:Check whether the configurate E-DCH TTI satisfy
GBR requirements,if satisfied,use configured E-DCH TTI; If the Measurement of TTI
transfer is Switch on,stop it.
If the new service is non conversation (whatever configured E-DCH TTI is 2ms or 10ms)
i. If present TTI 2ms could satisfy GBR requirement, use 2ms E-DCH TTI.
ii. If present TTI 10ms could satisfy GB R requirement, use 10ms E -DCH TTI,
otherwise check whether 2ms could satisfy, if satisfied, use 2ms E -DCH TTI
and switch off TTI trans fer measurement if it switch on.
Delet e concurrent service on E-DCH:
If present E-DCH TTI is 10ms, and TTI transfer measurement is switch off, keep on
using 10ms TTI.
If present E-DCH TTI is 2ms, and transfer measurement is switch off :
i. If the left services are all non conversation after delete, and the configured E-
DCH TTI is 10ms : If 10ms TTI c ould satisfy GB R requirementm use E-DCH
TTI of 10ms, otherwise use 2ms.
ii. If the left services are all non conversation after delete, and at least one
configured E -DCH TTI is 2ms : If 10ms TTI could satisfy GB R requirementm
use E-DCH TTI of 10ms, otherwise use 2ms.
iii. If the left services contain conversation aft er delete, if configured E-DCH TTI
of conversation service could satisfy GBR, use the configured TTI.
If present measurement is switch on :
i. If the left services contain service wit h configured TTI of 2ms after delete,
keep on current TTI, and keep the TTI reansfer measurement switch
on ;Otherwise
ii. If 10ms TTI could satisfy GB R requrement, use 10ms TTI and switch off t he
TTI transfer measurement ; Otherwise use 2ms TTI and s witch off
measurement.
During the session, the dynamic channel s witching in the HS UPA system is to adjust the
service bandwidth and hand over channels in real time mainly according to the

measurements of traffic and channel quality. The figure below shows the channel
switching that the system currently supports according to HS UPA protocols.
Figure 3-8 HSUPA Channel Switching
Transition DCH/DCH -> HS-DSCH/E-DCH

2. Channel Quality Measure Based (Option)
3. UE &Cell Capability Transition of DCH/DCH -> FACH/RACH
4. Compressed Mode is not started 1. UL&DL Traffic Volume Based
Reconfig SF 2. Support CELL_FACH
1. UL/DL Traffic Volume
Transition DCH/DCH -> HS-DSCH/DCH Based
1. UL/DL Traffic Volume Based Transition of HS-DSCH/DCH -> FACH/RACH
2. DL D-TCP Based 1. UL&DL Traffic Volume Based
2. Channel Quality Measure Based (Option) 3. UL TxP Based
3. UE &Cell Capability 2. Support CELL_FACH
4. Cell’s RTWP
5. Cell’s TCP Transition of HS-DSCH/E-DCH -> FACH/RACH
Transition HS-DSCH/E-DCH -> DCH/DCH
1. Channel Quality Measure Based (Option) 1. UL&DL Traffic Volume Based
Transition HS-DSCH/DCH -> DCH/DCH
1. Channel Quality Measure Based (Option) Transition of FACH/RACH -> DCH/DCH
Transition HS-DSCH/DCH -> HS-DSCH/E-DCH CELL_DCH RACH/FAC 2. Cell’s RTWP & Cell’s TCP
1. UL Traffic Volume Based H
2. UE &Cell Capability Transition of FACH/RACH -> HS-DSCH/DCH
3. If HSUPA associate compressed mode 1. UL/DL Traffic Volume Based
DCH/DCH 2. UE &Cell capability
method is set to “Serial”, the compressed mode
HS-DSCH /E-DCH CELL_FACH
is not started or 3. Cell’s RTWP & Cell’s TCP
HS-DSCH/DCH
Transition of FACH/RACH -> HS-DSCH/E-DCH
Transition of DCH/DCH -> PCH 2. UE &Cell capability
1. UL&DL Traffic Volume based 3. Cell’s RTWP & Cell’s TCP
2. Support PCH
Transition of HS-DSCH/DCH -> PCH Transition of FACH/RACH -> PCH

1. UL&DL Traffic Volume based 1. UL&DL Traffic Volume Based
2. Support PCH PCH 2. Support PCH
Idle
Transition of HS-DSCH/E-DCH -> PCH URA_PCH Transition of PCH -> FACH/RACH
1. UL&DL Traffic Volume Based 1. UL/DL Traffic Volume Based
2. Support PCH Transition of DCH/DCH ->IDLE
Transition of HS-DSCH/DCH -> IDLE Transition of FACH/RACH -> IDLE

1. UL&DL Traffic Volume Based 1. UL&DL Traffic Volume Based
Transition of PCH->IDLE
1. DL&UL Traffic Volume Transition of HS-DSCH/E-DCH -> IDLE
Based 1. UL&DL Traffic Volume Based
3.3.3.1 CELL_DCH (DL HS-DSCH/UL E-DCH) <-> CELL_FACH
1. CELL_DCH <-> CELL_FA CH switching triggered by traffic
i. CELL_DCH(DL HS-DS CH/UL E-DCH) -> CELL_FA CH
When the UE is in the CELL_DCH status, the switching from CELL_DCH (DL HS-
DSCH/UL E-DCH) to CELL_FA CH can be triggered by the traffic measurement
report (E vent 4B ) by the user plane.
The switching CELL_DCH (DL HS-DSCH/UL E-DCH) to CE LL_FACH is triggered

in the case of the following conditions:

(E vent 4B) on the HS -DS CH from the user plane as well as consecutive
ToFtimesThr traffic meas urement reports (E vent 4B) on t he E -DCH from t he
user plane. (Note: if the system receives a traffic meas urement report (E vent
4A) from t he user plane when t he receiving times are smaller t han t he

ii. CELL_FACH -> CE LL_DCH(DL HS -DS CH/ UL E-DCH)
When the UE is in the CELL_FA CH status, the switching from CELL_FA CH to

CELL_DCH (DL HS-DS CH/ UL DCH) can be triggered by the traffic measurement
report (E vent 4A ) from the user plane or UE.
The switching from CELL_FA CH t o CELL_DCH (DL HS-DS CH/ UL E-DCH) is

 The system receives consecutive FachE4aThd traffic measurement reports

(E vent 4A) from t he user plane or UE. (Note: if the system receives a traffic
measurement report (E vent 4B) from the user plane or UE when the rec eiving
times are smaller than the threshold, the corresponding counter is cleared.)
 Both the UE and system support HS -DS CH and E -DCH.
 The cell load is not overloaded. (Note: see the ZTE UMTS Overload Cont rol
Feature Guide for the overload threshold)
2. CELL_DCH to CELL_FA CH switching triggered by load
the cell load.
The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FA CH (DL FACH/UL
 The cell downlink load exceeds the overload threshold. (Note: see the ZTE UMTS
Overload Control Feature Guide for the overload threshold.)
3.3.3.2 CELL_DCH (DL HS-DSCH/UL E-DCH) <-> CELL_DCH (DL DCH/UL DCH)
1. Switching from DL DCH/UL DCH to DL HS-DS CH/ UL E-DCH triggered by traffic
When the subscriber uses the DL DCH/ UL DCH channel, the switching from DL DCH/UL
DCH to DL HS -DS CH/ UL E-DCH can be triggered by the measurement report (E vent 4A)
from the user plane or UE to increase the system capacity.
definition.

The switching from DL DCH/ UL DCH to DL HS-DSCH/UL E-DCH is triggered in the case

4A) on the downlink DCH or uplink DCH independently from the user plane or UE.
(Not e: if the system receives a traffic measurement report (E vent 4B) on the
downlink DCH or uplink DCH independently from the user plane or UE when the
receiving times are smaller than the threshold, the corresponding count er is
cleared.)
 The channel quality does not report 1F event.
 Both the UE and system support HS -DS CH and E -DCH.
 If HsupaCmAssoMode is configured as „Serial‟, the compressed mode is not started; if

HsupaCmAssoMode is configured as” Parallel ”, this requirement can be ignored.
(Not e: The parameter HsupaCmAssoMode indicates the HSUPA associate compressed
mode method, for more details see ZTE UMTS handover Control Feature Guide.)
Note: DL HS -DS CH/UL E -DCH cannot switch to DL DCH/ UL DCH based on traffic
volume measurement.
The concurrent services during channel switching are processed by the following
principl es:
 If all the c oncurrent services are PS services and one service triggers the switching from
DL DCH/UL DCH to DL HS -DS CH/ UL E -DCH, the DL DCH/ UL DCH of all servic es
is switched to DL HS -DS CH/ UL E-DCH.
 If there is conversation servic e in the concurrent services and the UE is capable of

the DL DCH/ UL DCH and DL HS-DSCH/UL E-DCH concurrency, the DL DCH/ UL
DCH of only PS services is switched to DL HS-DSCH/UL E-DCH; otherwis e, the
switching is not implemented.
Note:
When the downlink DP CH and HS -PDS CH coexist, the maximum rate on the DPCH is
reported by the UE. When the uplink DPCH and E-DP DCH coexist, the maximum rate
on the DP CH is 64 kbit/s.
If t he service is on the DL DCH/UL DCH, the UE triggers event 4A and meets conditions
for DL DCH/UL DCH -> DL HS -DS CH/UL E -DCH switching, but the DL HS -DS CH or UL
E-DCH fails to admit or the DL HS-DS CH or UL E-DCH is not supported, select UL DCH
rate increase. In the case of UL DCH rate increase, the other conditions of R99 UL DCH
rate increase must be satisfied (see UL DCH -> UL DCH) rate inc reas e)).
When the UE is in non-macro diversity, determine the target rat e for UL DC H rate
increase as follows:

see 3.1.3.3
When the UE is in macro diversity, determine the target rat e for UL DCH rate inc rease
as follows:
see 3.1.3.3
The MaxRateMD is the maximum rate threshold allowed for DCH rate inc rease when the
UE is in macro diversity.
If the service is on the DL DCH/UL DCH, the user plane triggers downlink event 4A and
meets conditions for DL DCH -> DL HS -DS CH switching, but the DL HS-DSCH fails to
admit or the DL HS-DS CH is not supported, select DL DCH rate inc reas e, and the uplink
is still on the DCH. In the case of DL DCH rate increase, the other conditions of DL DCH
rate increase must be satisfied. The way to determine the target rate for DL rate
increase is the same as that for HSDPA rate increase.
If the service is on the DL DCH/UL DCH, the UE triggers downlink event 4A and meets
conditions for DCH -> DL HS -DS CH switching, the DL HS-DSCH admits successfully,
but the UL E-DCH fails to admit or the E-DCH is not support ed, the downlink will be
switched to the HS -DS CH and the uplink is still on the DCH.
2. Switching from DL HS -DS CH/ UL E-DCH -> DL DCH/UL DCH triggered by channel
quality
When a subscriber is using the DL HS-DS CH/ UL E-DCH, the DL HS-DSCH/UL E-DCH
switching to DL DCH/ UL DCH can be triggered by channel quality measurement (E vent
1F triggered by pilot signal). This is because that the subscriber remaining on HS -DS CH
will wors en the QoS and lower the system capacity when the bit rate requirements of
streaming services carried on HS -DS CH are not satisfied and the channel quality
deteriorates.
definition.
The switching from DL HS-DS CH/ UL E-DCH to DL DCH/UL DCH is triggered in the case
 Channel quality measurement switches for the current PS service (IBChQS wc h,

SChQS wch) are open (Note: when PS S and I/B service are concurrent, if any of
IBChQS wc h and SChQS wch is open, these switches are considered open).
 The channel quality triggers E vent 1F.
Handling principle of concurrent services in channel s witching: switch all services on the
DL HS -DS CH/UL E-DCH to the DL DCH/UL DCH.

During the DL HS-DSCH/UL E-DCH -> DL DCH/UL DCH switching, the rate is the
DRB C initial rat e, see 3.1.2.2
3. Switching from DL HS-DSCH/UL E -DCH to DL DCH/UL DCH triggered by mobility
During the PS services carried on DL HS-DSCH/UL E-DCH, when t he HSUPA UE

hands over from an HS UPA cell to R99 cell for mobility but the target cell does not
support the HS-DSCH and E-DCH, the service channel will switch from DL HS-
DSCH/UL E-DCH to DL DCH/UL DCH. The rate is the DRBC initial rate, see 3.1.2.2

hands over from an HS UPA cell to HSDPA cell for mobility and the target cell supports
HS-DSCH but does not support the E-DCH, the service channel will switch from UL E-
DCH to UL DCH. The rate is the DRBC initial rate, see 3.1.2. 2
3.3.3.3 CELL_DCH (DL HS-DSCH/UL DCH) <-> CELL_DCH (DL HS-DSCH/UL E-DCH)
1. Switching from DL HS -DS CH/UL DCH to DL HS-DS CH/ UL E-DCH triggered by

traffic
When using the DL HS-DS CH/UL DCH, the UE can be switched from the DL HS-
DSCH/UL DCH to the DL HS-DSCH/UL E-DCH based on traffic volume measurement
reports (E vent 4A) from the UE so as to improve the peak rate of the UE.
The switching from DL HS-DS CH/ UL E-DCH to DL DCH/UL DCH is triggered in the case

4A) on the DCH from the UE. (Note: if the system receives a traffic measurement
report (E vent 4B) from the DCH when the receiving times are smaller than the
threshold, the corresponding counter is cleared)
 Both the system and the UE support the HSUPA
 If HsupaCmAssoMode is configured as „Serial‟, the compressed mode is not started; if

HsupaCmAssoMode is configured as” Parallel ”, this requirement can be ignored.
(Not e: The parameter HsupaCmAssoMode indicates the HSUPA associate compressed
mode method, for more details see ZTE UMTS handover Control Feature Guide.)
If the service is on the DL HS-DSCH/UL DCH, the UE triggers event 4A and meets
conditions for DL HS-DSCH/UL DCH -> DL HS-DSCH/UL E-DCH switching, but the UL
E-DCH fails to admit or the UL E-DCH is not supported, select UL DCH rate increase. In
the case of UL DCH rate increase, the other conditions of R99 UL DCH rate increase
must be satisfied (see UL DCH -> UL DCH (rat e increase)).

The way to determine the target rat e for UL DCH rate increase is the same as that in DL
DCH/UL DCH -> DL HS -DS CH/ UL E-DCH switching.
Note: DL HS-DS CH/ UL E-DCH cannot switch to DL HS-DSCH/UL DCH based on traffic
volume measurement.
2. DL HS -DS CH/UL E-DCH <-> DL HS-DS CH/ UL DCH switching triggered by mobility

hands over from an HS UPA cell to HSDPA cell for mobility and the target cell supports
HS-DSCH but does not support the E-DCH, the service channel will switch from UL E-
DCH to UL DCH. The rate is the DRBC initial rate, see 3.1.2. 2
During the PS services carried on DL HS-DSCH/UL DCH, when the HSUPA UE hands
over from an HSDPA cell to HSUPA cell for mobility and the target cell supports HS -
DSCH and E-DCH, the service channel will switch from UL DCH to UL E-DCH; the
downlink remains on the HS -DS CH.
3.3.3.4 CELL_DCH (DL HS-DSCH/UL E-DCH) -> URA_PCH
When the UE uses the CELL_DCH (DL HS -DS CH/UL E-DCH) for servic e bearer, the
switching from CE LL_DCH (DL HS-DSCH/UL E-DCH) to URA_P CH can be triggered by
the traffic measurement report (E vent 4B0) by the user plane.
The E vent 4B0 is defined as that the value of traffic measurement value is 0. See
The switching from CE LL_DCH (DL HS-DSCH/UL E-DCH) to URA_P CH is triggered in

the case of the following conditions:
measurement value of 0 on the HS-DSCH and E -DCH from the user plane (Note: if
the system receives a report with measurement value of non -zero value when the
receiving times are smaller than the threshold, the corresponding counter is cleared)

3.3.3.5 CELL_DCH (DL HS-DSCH/UL E-DCH) -> IDLE
When the UE uses the CELL_DCH (DL HS -DS CH/UL E-DCH) for servic e bearer, the
switching from CELL_DCH (DL HS-DS CH/ UL E-DCH) to IDLE is triggered in the case of
the following conditions:
 The system receives consecutive DToIdleThd traffic measurement reports with

measurement value of 0 on the HS -DS CH or E-DCH by the user plane. (Note: If the
system receives the measurement reports with traffic measurement value of non-
zero value before the receiving times is smaller than the threshold, the
corresponding counter is cleared.)
When the c hannel is changed to IDLE, the occupied radio resources are released and
3.3.3.6 E-DCH( 2ms E-TTI)<->E-DCH(10ms E-TTI)
1. E-DCH( 2ms E-TTI) -> E-DCH(10ms E-TTI)
If UL channel of user is E-DCH, It is possible that base on throughput measurement

report(4B) to trigger 2ms E-TTI transfer to 10ms E-TTI.
Once the condition bellow satisfied, it will trigger E-DCH (2ms E-TTI) trans fer to E-
DCH(_10ms E-TTI)
 The system receives consecutive ETtiEbThd throughput measurement reports

(E vent 4B) from the user plane, E-TTI transfer to 10ms. No action with 4A report.
(Not e: if the system receives a throughput measurement report (E vent 4A) from the
user plane, the corresponding counter is cleared. )
2. E-DCH( 10ms E-TTI) -> E-DCH(2ms E-TTI)
If UL channel of user is E-DCH, It is possible that base on throughput measurement

report(4A) to trigger 10ms E-TTI trans fer to 2ms E-TTI.
Once the condition bellow is satisfied, it will trigger E-DCH (10ms E-TTI) transfer to E-
DCH(2ms E-TTI)
 The system receives consecutive ETtiEbThd throughput measurement reports

(E vent 4A) from the user plane, E-TTI trans fer to 2ms. No action with 4B report.
(Not e: if the system receives a throughput measurement report (E vent 4B) from the
user plane, the corresponding counter is cleared. )

 Licence Tti2msSuptInd is support
 If UE and activity cell both support 2ms.
The throughput measurement mentioned above is illustrated in 3.3.4.2 Throughput

measurement for PS service TTI transfer.
Traffic measurement on the E-DCH is to measure the uplink throughput of the E-DCH on
the FP layer through the user plane.
For a service on the E-DCH, calculate its data volume within 100 ms and convert it to a
rate. Slide the window for 20 ms, and then calculate its data volume for 100 ms and
convert it to a rate once again.
Measure parameter acquisition met hod: For a service on the DL HS -DSCH/UL E-DCH,
see traffic measurement on the HSDPA for acquisition of traffic parameters on the DL
HS-DSCH. Acquisition of traffic parameters on the UL E-DCH: when t raffic parameters
are acquired, get the corres ponding configuration number UeTrvMCf gNo from the UE
traffic volume measurement configuration relationship according to the cell identity Cid
and measurement purpose (E-DCH uplink traffic measurement DrbcEDchUpThpt). Then
according to the configuration number, get the corres ponding traffic volume
measurement in RNC NE -> RNC Radio Resource Management -> Modify Advanced
Parameter -> UE Traffic Volume Measurement Configuration:
 If the uplink channel for the service is the E-DCH, traffic volume measurement is
made on the user plane and related parameters used in the traffic volume
measurements are parameters corresponding to the UP Throughput E vent
Measurement Configuration Number for E-DCH.
 On the E-DCH, the reporting thresholds for events 4A and 4B for I/B and S
services are determined by the paramet er
RptThres[ MAX_UE_TRV_MEAS_EVENT] under this configuration number.
 TrigTime [MAX_UE_TRV_MEAS _EVENT] and PendingTime

[MAX_UE_TRV_MEAS_EVE NT] values for events 4A and 4B on the E-DCH
are corresponding to those under this configuration number.
3.3.4.2 Throughput Measurement for PS service TTI transfer
For UL channel of user is E-DCH, the measurement of trans fer 2ms E-TTI and 10ms E-
TTI. Throughput measurment is independent of traffic measurement.

There is a s witch EttiTraffVolS wch(S witch of E-TTI S witching Triggered by User Plane
Throughput Measurement) to control this feature. As EttiTraffVolS wch open,for a service
on the DL HS-DSCH/UL E-DCH, acquisition of traffic parameters on the UL E-DCH for
E-TTI s witching: Get the corresponding configuration number UeTrvMCfgNo from the
UE traffic volume measurement configuration relationship according to the cell identity
Cid and measurement purpose (E-DCH E-TTI switching traffic measurement
ETtiUpThpt). Then according to the configuration number, get the corresponding traffic
volume measurement in RNC NE -> RNC Radio Resource Management -> Modify
Advanced Parameter -> UE Traffic Volume Measurement Configuration: ThoughThres
[MAX_UE_TRV_MEAS_EVE NT] define the rat e thresholds of 10ms to 2ms and 2ms to
10ms respectively. TrigTim and PendingTime is available in report regulation as traffic
measurement. The average time of time window for measurement quantity is set by
AverageTime. 4A and 4B event thresholds of E -DCH are ETtiEaThd(For times
threshold trigger E-TTI from 10ms to 2ms)and ETtiEbThd(For times threshold trigger E-
TTI from 2ms to 10ms),use as same as times threshold of traffic measurement.
The stop and start of throughput measurement
As EttiTraffVolSwch is set to be open,
 UE build E-DCH, and supported 2ms TTI
 All the cells of active set are support 2ms TTI.
 No C class traffic on E-DCH,
 At least one traffic E-tti configure is 2ms
If 10ms TTI could satisfy GBR require, Open the throughput measurement. At other
scenes it will not open the meas urement (close the measurement once opened)
 Note: The throughput is the combination of macro diversity throughput.
3.4 HSPA+ Dynamic Channel Adjustment
3.4.1 Dual-Carrier related Dynamic Channel Adjustment
Exceptional implement for Dual-Cell in initial service channel allocation:
 For UE which select DL HS-DSCH,if it capability and cell both support Dual-
Carriers HS-DSCH,the Dual -Carriers should be allocated to UE.
 DC-HS capability of neighbour cell from diffrent RNC and its secondary carrier
information should be obtained from adjucent cell list in RNC, whic h is

IurDc HsdsSuptInd and SndS vrCelI D; DC-HS capability of adjucent cell and
secondary carrier information over Iur interface could be acquire form IE in Iur
interface.
For concurrent service on Dual-Carrier
 If pure PS services concurrent，that all PS services bear on Dual-carrier.
 If CS service concurrent with PS service, that the judgment of PS service use Dual-
carrier or not is as the same as the judgment of single traffic in initial service
allocation. If Dual-carrier is used,CS service bears on the primary carrier.
3.4.1.3 Channel Switching
In case of switching to HS-DSCH from ot her channel, if UE capability and the cell both
support Dual-Cell, This UE should be allocated with Dual-Carriers.
HS-DSCH serving cell change will trigger trans fer bet ween Dual-Cell HS -DS CH and
Single cell HS-DS CH：
 If HS -DS CH target cell support dual-carrier，and also satisfy the condition bear on
dual-carrier，dual-c arrier would be allocated.
 If HS -DS CH t arget cell does not support dual-carrier, single cell would be allocated
to bear HS-DSCH.
3.4.2 Fast Dormancy
R8 and after version Smart phone have ability to request activated PS domain（without
CS domain） data session end by sending message“Signalling Connection Release
Indication ” (SCRI) ， which include IE “ Signalling Connection Release Indication
Caus e”has value“UE requested PS data session end”，When RNC receive this
message，it would switch the UE to URA_PCH or IDLE ，and reduce unnec essary
buttery consumption. There is a parameter ”T323S wch” to control whether configure
T323 in SIB 1. Without receive T323, UE would not sending SCRI with cause to”UE
requested PS dat a session end”
3.4.2.1 SCRI trigger Channel Switching to URA_PCH

The conditions of channel switching from CELL_DCH or CELL_FACH to URA_PCH
triggered by UE SCRI are as following：
 PchSwch is “on”

 Receive message “signaling connection release indication”which include IE

“signaling connection release indication cause”has value of“UE requested
PS data session end”
If conditions above are satisfied, trigger channel switch to URA_PCH.
3.4.2.2 SCRI trigger Channel Switching to IDLE

The conditions of channel switching from CELL_DCH or CELL_FACH to IDLE
triggered by UE SCRI are as following：
 PchSwch is “off”
 Receive message “signaling connection release indication”which include IE

“signaling connection release indication cause”has value of“UE requested
PS data session end”
If conditions above are satisfied, trigger channel s witch to IDLE, and release the
occupied radio resource.
3.5 Other Description
3.5.1 Traffic Sub-class rate matching
CN send necessary Qos information to RNC by RAB assignment message. In Qos

information, it defined max bit rate etc. traffic relat ed rat e information. Under the user
rate control of RNC, besides the rate demand of CN, it is also controlled by UE capability
limitation and real traffic situation. The whole process is rate matching.
Rate matching includes two procedures:
A: scissor Iu assignment rate:
A1: For HSPA: MaxBR1= min(max rate of Iu interface (If there is MBR negotiation, it is
the max rate after negotiation), max rate according to UE capability );
A2:For DCH: MaxBR1= max {max rate of Iu int erface (If there is MBR negotiation, it is
the max rate after negotiation), 384kbps}
B:Fuzzy match from MaxBR1 to nearest sub-class in sub-class list (Match to the nearest
greater or equal rate of sub-class), according to the matched sub -class number, it is
possible to achieve the parameters configuration for this traffic. Among them, the
parameter MaxBitRate is MaxBR2.

C:RNC controlled the max bit rate of this traffic is min(rate after rate matching, which is
MaxBR2, max rate of Iu interfac e (If there is MBR negotiation, it is the max rate after
negotiation))
3.5.1.1 HSDPA UE capability and the mapping rate of supported MaxBR
The max rat e restriction list according to UE capability is as following:

Max bit rate supported by UE
UE capability
capability
UE HS-DSCH Physical Layer category 1 and
1.2Mbps
2
UE HS-DSCH Physical Layer category 3, 4
1.8Mbps
and 12
UE HS-DSCH Physical Layer category 5 and
3.65Mbps
6
UE HS-DSCH Physical Layer category7 and
7.2Mbps
8
UE HS-DSCH Physical Layer category9 10.1Mbps
UE HS-DSCH Physical Layer category10 14Mbps
UE HS-DSCH Physical Layer category11 900kbps
Whether
supported Max bit rate supported by UE
UEcapability
64QAM by capability
Node B
not support 10.1Mbps(Match to category9,see
UE HS-DSCH Physical 64QAM note)
Layer Category 13
Support 64QAM 17.6Mbps
not support 14Mbps(Match to category10,see
Layer Category 14
UE HS-DSCH Physical not support 10.1Mbps(Match to category9,see
Layer Category 15 64QAM note)
UE HS-DSCH Physical not support 14Mbps(Match to category10,see
Layer Category 16 64QAM note)
not support 10.1Mbps(Match to category9,see
Layer Category 17
not support 14Mbps(Match to category10,see
Layer Category 18
Note: Configure pattern of HA RQ Info in Uu interface
If RNC adjust UE category downward according t o Node B capability,The Rate

restriction is the restriction after adjustment.

3.5.1.2 HSUPA UE capability and the mapping rate of supported MaxBR

Support for 10 and 2
E-DCH category Max bit rate supported
ms TTI EDCH
Category 1 10 ms TTI only 711kbps
10 ms TTI 1.448 Mbps
Category 2
2 ms TTI 1.448 Mbps
Category 3 10 ms TTI only 1.448 Mbps
10 ms TTI 2.048Mbps
Category 4
2 ms TTI 2.886 Mbps
Category 5 10 ms TTI only 2.048Mbps
10 ms TTI 2.048Mbps
Category 6
2 ms TTI 5.76 Mbps
10 ms TTI 2.048Mbps
2 ms TTI(UE not
5.76 Mbp
Category 7 configure 16QAM)
2 ms TTI(UE
11.52Mbps
configure 16QAM)
Note:Scissor by UE capability is cut max bit rate according to UE category and

modulation etc. at the same time.
3.5.2 RNC adjust MaxBitRate according to configuration
RNC could adjust MBR assigned by CN by controlled switch. The cont rolled switch
(Uplink:UlCt rlMBRS witch, Downlink:DlCtrlMB RS witch) are provided with four modes of
adjustments as following:
0 Closed, means No adjustment
1 Replaced Mode, means controlled MBR substitute of CN assigned MBR
2 Minimum Mode, means the minimum of controlled MB R and CN assigned MBR;
3 Maximum Mode, means the maximum of controlled MBR and CN assigned MBR;
RNC controlled MB R decided by Uplink UlControledMB R and Downlink

DlControledMB R.
Use the MBR after RNC adjustment to substitute CN assigned MBR.
Adjustment formular for MBR:
 Set UlMbrA fterA dj to be UL MBR after adjustment:
If UL Controlled MBR Switch is 0:Closed,UlMbrA fterAdj = CN assigned UL MBR

If UL Controlled MBR Switch is 1:Replaced Mode,UlMbrA fterAdj= UlControledMB R
If UL Cont rolled MBR Switch is 2:Minimum Mode, UlMbrAfterAdj =min{Assigned UL

MB R,UlCont roledMBR }
If UL Controlled MB R Switch is 3:Maximum Mode, UlMbrA fterAdj =max{Assigned

UL MBR, UlControledMBR }
 Set DLMbrAfterAdj to be DL MB R after adjustment:
If DL Controlled MBR Switch is 0:Closed,DLMbrA fterAdj = CN assigned DL MB R
If DL Controlled MBR Switch is 1:Replaced Mode,DLMbrA fterAdj=DlControledMB R
If DL Cont rolled MBR S witch is 2:Minimum Mode,DLMbrAfterAdj =min{Assigned DL

MB R,DlCont roledMBR}
If DL Controlled MBR Switch is 3:Maximum Mode, DLMbrA fterA dj =max{Assigned

DL MBR, DlControledMBR}
Remarks:
1. RNC adjusts CN assigned MBR is not related to MBR after RAB negotiation and
renegotiation.
2. In the case of macro diversity, UlControledMB R/ DlControledMBR is from best cell

when service setup up.
3.5.3 Be compatible with the IPHONE which is not implement according to

encryption protocol
When some version of IPHONE setup up Conversation, if they bear RRC on

CELL_FACH, and on the process of switching to CELL_DCH on RAB , their implements
are not according to enc ryption prot ocol, in that case, they will suffer bubble noise
caused by losing alignment of CFN. In order to be compatible with this kind of IPHONE,
ZTE set a switch CsRrcOnFachInd to control RRC not bear on CE LL_FACH by
guarantee UE not attempt to access CELL_FA CH aft er failed on CELL_DCH on RRC.
After RRC failed to bear on DCH low rate ，If it is CS traffic ，whether access to
FACH/ RACH would judge by Cs RrcOnFachInd.(CS traffic is defined by Establish cause,
which is Originating Conversational Call or Terminating Conversational Call). If
CsRrcOnFac hInd is off, RRC of non emergency CS would not bear on FA CH/ RACH.
Emergency CS call would not restrict by this switch.

3.5.4 The MaxBR of HSDPA on Iur interface

Iur interface does not inform MaxBR of HSDPA traffic to DRNC. ZTE base on the value
of Iur interface IE” TrCH Sourc e Statistics Descriptor” to decide MaxBR of HSDPA, and
set a parameter MaxDHsRate to cont rol the MaxBR of HSDPA traffic.
 If the value of IE “TrCH S ource Statistics Descriptor is “S peech“，t hen MaxBR

=38.8k
 If the value of IE“TrCH Source Statistics Descriptor“ is“RRC“，then MaxB R =3.4k
 If the value of IE “TrCH Source Statistics Descriptor“ is“Unknown“,or even this IE is
absent, then MaxBR is decided by IE“traffic class“
 If t he value of IE“Traffic class“ is “streaming“, “interactive“ or “background“，

then calculate MaxBR=max {MaxDHsRate1 ， GB R} ； thereinto
MaxDHs Rate1=min{MaxDHsRate，MaxBR of HS-DS CH supported by UE }
 If the value of IE“Traffic class“ is “conversation“，then MaxBR=38. 8k
Note:MaxB R of HS-DSCH supported by UE is the max bitrate supported by UE

category.
4 Configuration of Parameters
4.1 DRBC Related Parameters
4.1.1 Parameter List
4.1.1.1 Configuration information of dynamic radio bearer control

Abbreviated name Parameter name
DrbcS wch DRB C Method Switch
Downlink Maximum Rat e Thres hold of I/B Service on
Rfach
CELL_FA CH
Uplink Maximum Rate Threshold of I/B Service on
Rrac h
RACH
FachSwch Switch of Transferring to CELL_FACH
Switch for DCH Rate Adjustment Based on Traffic
DchAdjRateS wch
Volume Measurement
Switch for UL DCH Rate A djustment Based on UE
UlPwrDasf
Transmission Power
DlPwrDasf Switch for DL DCH Rate A djustment Based on D -TCP
E vent 4A Counter Thres hold for CELL_ FACH to
FachE4aThd
CELL_DCH Shared by Uplink and Downlink

E vent 4A Counter Thres hold for Inc reasing Rate on

DchE4aThd
DCH or DCH->HSPA
E vent 4B Counter Threshold for Decreasing Rate on
DchE4bThd
DCH
PchHoldTimeThr Time Threshold for CELL_PCH or URA _PCH to Idle
E vent A Counter Threshold for Decreasing Rat e on DL
DtcpEaThd
DCH Based on D-TCP
E vent B Counter Threshold for Restriction Inc reasing
DtcpEbThd
Rate on DL DCH Based on D-TCP
PchSwch Switch of URA_P CH/CELL_P CH Support
E vent 4B Counter Threshold for CELL_DCH to PCH
DToPchThd
Shared by Uplink and Downlink
E vent 4B Counter Threshold for CELL_FA CH to PCH
FToPchThd
E vent 4B Counter Threshold for CELL_DCH to Idle
DToIdleThd
E vent 4B Counter Threshold for CELL_FA CH to Idle
FToIdleThd
C Traffic Rate Threshold Us ed for Determining NRT PS
CRateThrd
Rate Upper Limit
NRT PS Traffic Rate Upper Limit When Low Rate C
PSRateLmtLowC
Traffic+ PS Traffic
NRT PS Traffic Rate Upper Limit When High Rat e C
PSRateLmtHighC
Traffic+ PS Traffic
Wait Timer for Adjusting Uplink and Downlink
UpUdRec fgTimer
Reconfiguration by One Step Upward
Wait Timer for Adjusting Uplink and Downlink
DnUdRec fgTimer
Reconfiguration by One Step Downward
This parameter indicates the initial rate of UL DCH
InitialRateUl
admission.
This parameter indicates the initial rate of DL DCH
InitialRateDl
admission.
UeTrfRptMed, UE Traffic Volume Measurement Report Method
4.1.1.2 RNC configuration information

Ty pe of Transport Channel for Initial RRC Con nection
InitRrcOnDch
Setup
Switch of non Emergency CS Service Access to
CsRrcOnFac hInd
CELL_FA CH On RRC
4.1.1.3 QoS configuration related priority and rate level information

UlRateAdjLevNum Uplink Rate Adjustment Level Number

UlRateAdjLev[MA X_NUM_RATE_A DJUS T] Uplink Rate Adjustment Level

Downlink Rate Adjustment Level
DlRateAdjLevNum
Number
DlRateAdjLev[MA X_NUM_RATE_A DJUS T] Downlink Rate Adjustment Level
4.1.1.4 Service Cell Information

Maximum Allowable Rate on DCH to be Increased to
MaxRateMD
When UE is in Macro Diversity(kbps)
Cs64S witch Switch of CS 64kbps Establishment
Maximum Bit Rate on UL DCH for NRT PS RAB in
NrtMax UlRateDch
Serving Cell
Maximum Bit Rate on DL DCH for NRT PS RAB in
NrtMax DlRateDch
Serving Cell
Maximum Bit Rate on UL DCH for RT PS RAB in
RtMaxUlRateDch
Serving Cell
Maximum Bit Rate on DL DCH for RT PS RAB in
RtMaxDlRateDch
Serving Cell
UlCtrlMB RS witch UL Controled MBR S witch
DlCtrlMB RS witch DL Controled MBR S witch
UlControledMBR UL Controled MBR
DlControledMBR DL Controled MBR
4.1.1.5 External Utran Cell Information

Switch of CS 64kbps Establishment for External
AdjCs64S witch
UTRA N Cell
Maximum Bit Rate on UL DCH for NRT PS RAB in
NrtMax UlRateDchD
External UTRA N Cell
Maximum Bit Rate on DL DCH for NRT PS RAB in
NrtMax DlRateDchD
Maximum Bit Rate on UL DCH for RT PS RAB in
RtMaxUlRateDchD
Maximum Bit Rate on DL DCH for RT PS RAB in
RtMaxDlRateDchD
4.1.2 Parameter Configuration
4.1.2.1 DRBC Method Switch
 OMC Path

Path: View->Configuration Management-> RNC NE-> RNC Radio Res ource

Management-> Modify Advanced Parameter-> UE Traffic Volume Measurement -> UE
Traffic Volume Measurement Configuration Index
 Parameter Configuration
This parameter is a switch, indicating whether dynamic radio bearer control algorithm is
used for uplink and downlink. There are four options:
 0: UL Closed & DL Closed
 1: UL Closed & DL Open
 2: UL Open & DL Closed
 3: UL Open & DL Open
This parameter controls whether to use dynamic radio bearer control for uplink and
downlink. Its default value is 3: UL Open & DL Open.
4.1.2.2 Downlink Maximum Rate Threshold of I/B Service on CELL_FACH
 OMC Path

Management-> Modify Advanced Parameter->Dynamic Radio B earer Control
Information-> Downlink Maximum Rate Threshold of I/B Service on CELL_FA CH (kbps)
This parameter indicates the downlink maximum bit rate threshold for PS servic e being
established on CE LL_FACH. I/B service is set up initially or is switched from DCH to
FACH, if downlink maximum bit rate or downlink target bit rate is lower than the
threshold indicated by this parameter and the uplink maximum bit rate or uplink target bit
rate is lower than the uplink maximum bit rate threshold of the PS servic e on the Rach.
The larger this parameter, the easier I/B service is set up or is switched to the fach/rach.
Its default value is 8kbit/s.
4.1.2.3 Uplink Maximum Rate Threshold of I/B Service on RACH
 OMC Path

Information-> Uplink Maximum Rate Threshold of I/B Service on RA CH (kbps)

This parameter indicates the uplink maximum bit rate threshold for PS service being
established on CE LL_FACH. I/B service is set up initially or is switched from DCH to
RACH, if uplink maximum bit rate or uplink target bit rate is lower than the threshol d
indicated by this parameter and the downlink maximum bit rate or downlink target bit
rate is lower t han t he downlink maximum bit rate threshold of the PS service on the
FACH.
The larger this parameter, the easier I/B service is set up or is migrated to t he fach/rach.
Its default value is 8kbit/s.
4.1.2.4 Switch of Transferring to CELL_FACH
 OMC Path
Path: View -> Configuration Management -> RNC NE -> RNC Radio Res ource
Management -> Modify Advanced Parameter -> Dynamic Radio B earer Control
Information -> Switch of Transferring to CE LL_FACH
This parameter is a switch of other channels transferring to the Fach. When this
parameter is closed, it is not allowed to transfer from other channels to the Fach. When
this parameter is open, it is allowed to transfer from other channels to the Fach.
Whatever this parameter is closed or open, it is essential to transfer to the FACH first
before to dedicated channels from the PCH.
Its default value is open.
4.1.2.5 Switch for DCH Rate Adjustment Based on Traffic Volume Measurement
 OMC Path
Information -> Switch for DCH Rate Adjustment Based on Traffic Volume Measurement
This parameter is a switch of adjustment of rate on the DCH. When this parameter is
closed, it is not allowed to adjust the rate for PS service on the DCH. When this
parameter is open, it is allowed to adjust the rate for PS service on the DCH.

4.1.2.6 Switch for UL DCH Rate Adjustment Based on UE Transmission Power
 OMC Path

Information-> Switch for UL DCH Rate A djustment Based on UE Transmission Power
This parameter is the rate adjustment switch on the DCH. The switch is triggered based
on the UE transmitting power. When the parameter is OFF, the rate of PS servic e on the
DCH will not be adjusted when the UE transmitting power is too high. When the
parameter is ON, the rate of PS service on the DCH will be adjusted when the UE
transmitting power is too high.
Its default value is off.
4.1.2.7 Switch for DL DCH Rate Adjustment Based on D-TCP
 OMC Path
Path:View->Configuration Management->RNC NE-> RNC Radio Resource Management-

> Modify Advanced Parameter-> Dynamic Radio Bearer Control Information-> Switch for
DL DCH Rat e Adjustment Based on D-TCP
This parameter is the rate adjustment switch on the DCH. The switch is triggered based
on the D-TCP. When the parameter is OFF, the rat e of PS service on the DCH will not
be adjusted when the D-TCP is too high. When the parameter is ON, the rate of PS
service on the DCH will be adjusted when the D-TCP is too high.
Its default value is off.
4.1.2.8 Event 4A Counter Threshold for CELL_FACH to CELL_DCH Shared by

Uplink and Downlink
 OMC Path
Information -> E vent 4A Counter Threshold for CE LL_FACH to CELL_DCH S hared by
Uplink and Downlink

This parameter indicates the event 4A counter threshold for FACH->DCH/ HS-DSCH or
RACH -> DCH/EDCH. For the UE on the CELL_FA CH, if the times of the measured
RLC buffer payload of the uplink or downlink being larger than the 4A threshold exceed
the threshold indicated by this parameter, the UE will be t rans ferred from the FA CH to
the DCH/ HS-DSCH or from the RA CH to the DCH/EDCH. And when event 4A counter
on either the downlink or uplink reaches the threshold, channel transfer occurs.
The larger this parameter is, the harder the UE will be transferred from FACH-> DCH/HS-
DSCH or RACH-> DCH/EDCH, and vice versa.
Its default value is 1.
4.1.2.9 Event 4A Counter Threshold for Increasing Rate on DCH or DCH -> HSPA
 OMC Path
Information -> E vent 4A Counter Threshold for Increasing Rate on DCH or DCH ->
HSPA
This parameter indic ates the event 4A counter threshold for increasing rate on DCH or
transferring from the DCH to the HSPA. For the UE using the DCH in both directions, if
the times of the measured RLC buffer payload of the uplink or downlink being larger
than the 4A threshold exceed the threshold indicated by this parameter, UE‟s data rate
on DCH will be increased or UE will be transferred from DCH to HSPA.
The larger this parameter is, the more slowly the UE's data rate on DCH will be
increased or UE will be transferred from DCH to HSPA. Vice versa.
4.1.2.10 Event 4B Counter Threshold for Decreasing Rate on DCH
 OMC Path
Information -> E vent 4B Counter Threshold for Decreasing Rate on DCH
This parameter indicates the event 4B count er threshold for decreasing rate on DCH.
For the UE using the DCH in both directions, if the times of the measured RLC buffer

payload of the uplink and downlink being less than the 4B threshold exceed the
threshold indicat ed by this parameter, UE‟s data rate on DCH will be decreased.
The larger this parameter is, the harder UE's data rate on DCH will be decreased. Vice
versa.
4.1.2.11 Time Threshold for CELL_PCH or URA_PCH to Idle
 OMC Path
Information -> Time Threshold for CELL_PCH or URA_PCH to Idle(s )
This parameter indicates the time threshold of UE stay ing in CELL_PCH or URA_P CH
for the judgment of trans ferring from CELL_P CH or URA_P CH to idle. If the time of UE
having stayed in URA_P CH exceeds the threshold indicat ed by this paramet er, the UE
will be transferred from URA_PCH to Idle.
The larger this parameter is, the longer the UE will stayed in URA_P CH and the harder
the UE will be trans ferred from PCH to IDLE. Vice versa.
Its default value is 30s.
4.1.2.12 Event A Counter Threshold for Decreasing Rate on DL DCH Based on D-

TCP
 OMC Path
Information -> E vent A Counter Threshold for Decreasing Rate on DL DCH Based on D-
TCP
This parameter indicates the event A counter threshold of consecutive DTCP reports for
DTCP -DRB C. If event A counter of DTCP reports reach the threshold indicated by this
parameter, UE„s rate on downlink DCH will be decreased.
The larger this parameter is, the harder UE‟s rate on downlink DCH will be decreased.
Vice versa.

4.1.2.13 Event B Counter Threshold for Restriction Increasing Rate on DL DCH

Based on D-TCP
 OMC Path
Information -> Event B Counter Threshold for Restriction Increasing Rate on DL DCH
Based on D-TCP
This parameter indicates the event B counter threshold of consecutive DTCP reports for
DTCP -DRB C. If event B counter of dedicated TCP reports reach the threshold indicated
by this parameter, UE leaves A status and turns to B status. Moreover, only traffic
volume report under B status can trigger increasing rate on DCH.
The larger this parameter is, the harder the UE leaves event A status and turns to B
status. Vice versa. When NodeB has not left A status and turned to B status, 4A event
cannot increase the rate of the UE on the uplink or downlink.
4.1.2.14 Switch of URA_PCH/CELL_PCH Support
 OMC Path
Information -> Switch of URA _PCH/CE LL_P CH Support
This parameter indicates whether transferring to URA_P CH/ CELL_P CH is supported or

not. If the value is „Only Support URA_P CH‟, the UE is allowed to t rans fer to the P CH
when there is no data to transmit. If the value is „Not Support URA_PCH/CE LL_PCH‟,
UE is not allowed to transfer to the PCH when there is no data to transmit.
Its default value is 0: Not support URA _PCH/CELL_P CH.
4.1.2.15 Event 4B Counter Threshold for CELL_DCH to PCH Shared by Uplink and
Downlink
 OMC Path


Information-> E vent 4B Counter Threshold for CELL_DCH to PCH Shared by Uplink and
Downlink
This parameter indicat es the threshold of the 4B event triggering times for DCH -> PCH
transition. For a user whose both uplink and downlink locate on the DCH, if the RLC
buffer loads of the uplink and downlink are 0, and the consecutive reporting times reach
this threshold, the DCH -> PCH state transition is triggered.
The higher the parameter value is, the harder the DCH -> PCH transition of the UE is
triggered, and vice versa.
4.1.2.16 Event 4B Counter Threshold for CELL_FACH to PCH Shared by Uplink and
Downlink
 OMC Path

Information-> E vent 4B Counter Threshold for CELL_FA CH to PCH Shared by Uplink
and Downlink
This parameter indicates the threshold of the 4B event triggering times for CELL_FA CH
-> PCH transition. For a user whos e both uplink and downlink locate on the CELL_FA CH,
if the RLC buffer loads of the uplink and downlink are 0, and the consecutive reporting
times reach this threshold, the CE LL_FACH -> PCH state transition is triggered.
The higher the parameter value is, the harder the CELL_FA CH -> PCH transition of the
UE is triggered, and vice versa.
4.1.2.17 Event 4B Counter Threshold for CELL_DCH to Idle Shared by Uplink and
Downlink
 OMC Path


Information-> E vent 4B Counter Threshold for CELL_DCH to Idle Shared by Uplink and
Downlink
This parameter indicat es the threshold of the 4B event triggering times for CELL_DCH -
> Idle transition. For a user whose both uplink and downlink locate on the DCH, if the
RLC buffer loads of the uplink and downlink are 0, and the consecutive reporting times
reach this threshold, the DCH -> Idle state transition is triggered.
The higher the paramet er value is, the harder the DCH -> Idle transition of the UE is
triggered, and vice versa.
4.1.2.18 Event 4B Counter Threshold for CELL_FACH to Idle Shared by Uplink and
Downlink
 OMC Path

Information-> E vent 4B Counter Thres hold for CELL_FA CH to Idle Shared by Uplink and
Downlink
This parameter indicates the threshold of the 4B event triggering times for CELL_FA CH
-> Idle transition. For a user whose both uplink and downlink locate on the CE LL_FACH,
if the RLC buffer loads of the uplink and downlink are 0, and the consecutive reporting
times reach this threshold, the CE LL_FACH -> Idle state transition is triggered.
The higher the parameter value is, the harder the CELL_FA CH -> Idle transition of the
UE is triggered, and vice versa.
4.1.2.19 C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit
 OMC Path

Information-> C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit

This parameter defines the threshold for judging the rat e level of CS service. If a CS
service rat e is higher than this threshold, the service is a High Rate C, or else a Low
Rate C.
The higher the parameter value is, the smaller the possibility of the High Rate C is, and
vice versa.
Its default value is 32kbps.
4.1.2.20 NRT PS Traffic Rate Upper Limit When Low Rate C Traffic+ PS Traffic
 OMC Path

Information-> NRT PS Traffic Rate Upper Limit When Low Rate C Traffic+ PS Traffic
This parameter defines the higher rat e threshold of PS I/B services that are concurrent
with Low Rate C.
The higher the parameter value is, the higher the highest rate of the concurrent PS I/B
services are, and vice versa.
4.1.2.21 NRT PS Traffic Rate Upper Limit When High Rate C Traffic+ PS Traffic
 OMC Path

Information-> NRT PS Traffic Rate Upper Limit When High Rate C Traffic+ PS Traffic
This parameter defines the higher rat e threshold of PS I/B services that are concurrent
with High Rate C.
The higher the parameter value is, the higher the highest rate of the concurrent PS I/B
services are, and vice versa.

4.1.2.22 Type of Transport Channel for Initial RRC Connection Setup
 OMC Path
path ： View->Configuration Management->RNC NE-> RNC Radio Res ource

Management->Basic Information-> Ty pe of Transport Channel for Initial RRC
Connection S etup
This parameter indicat es the type of transport channel of signaling when initial RRC
connection setup. There are five options:
0. The RNC sets the initial signaling to forcibly use DCH/DCH at 3.4k
2. The RNC sets the initial signaling to use common channel forcibly
3. The RNC sets the initial signaling to choose channel automatically, and setting
Its default value is The RNC sets the initial signaling to forcibly use DCH/DCH at 13.6k
4.1.2.23 Uplink Rate Adjustment Level Number
 OMC Path
Path: View->Configuration Management->RNC NE ->Qos Configuration-> Priority and

Rate Segment of Qos Advanced Parameter->check and modify…-> Uplink Rate
Adjustment Level Number
This parameter indicat es the number of uplink rate adjustment levels used by the DRB C.
It regulates the number of uplink rate adjustment levels for ser vices on the DCH.
Its default value is 3. The maximum value is 6.

4.1.2.24 Uplink Rate Adjustment Level
 OMC Path

Rate Segment of Qos Advanced Parameter ->check and modify…-> Uplink Rate
Adjustment Level
This parameter indicates the uplink rate adjustment levels used by DRB C. The uplink
rate adjustment can be adjusted on these levels only.
For Uplink Rat e Adjustment Level Number, the default value is 3, and the default values
of uplink rate adjustment levels are 16 kbit/s, 64 kbit/s, and 384 kbit/s.
4.1.2.25 Downlink Rate Adjustment Level Number
 OMC Path

Rate Segment of Qos Advanced Parameter->check and modify…-> Downlink Rate
Adjustment Level Number
This parameter indicates the number of downlink rate adjustment levels used by the
DRB C. It regulat es the number of down rat e adjustment levels for servic es on the DCH.
Its default value is 4. The maximum value is 6.
4.1.2.26 Downlink Rate Adjustment Level
 OMC Path

Rate Segment of Qos Advanced Parameter->check and modify…-> Downlink Rate
Adjustment Level
This parameter indicates the downlink rate adjustment levels used by DRBC. The
downlink rat e adjustment range can be adjusted on these levels only.
For Downlink Rat e Adjustment Level Number, the default value is 4, and the default
values of downlink rate adjustment levels are 8 kbit/s, 64 kbit/s, 128 kbit/s, and 384
kbit/s.

4.1.2.27 Maximum Allowable Rate on DCH to be Increased to When UE is in Macro

Diversity(kbps)
 OMC Path
Path ： View->Configuration Management->RNC NE->RNC Radio Res ource

Management-> UtranCell-> UtranCellX->Modify Advanced Parameter->UtranCell-
>Maximum Allowable Rate on DCH to be Increased to When UE is in Macro
Diversity(kbps)
This parameter indicates the maximum rat e threshold allowed for the DCH when the UE
is in macro diversity. When the UE is in macro diversity, its rate on the DCH cannot
exceed the thres hold. When the UE is in macro diversity and its current rate is larger
than this parameter, rate adjustment is not affected by this parameter. The larger this
parameter is, the higher the UE 's rate can be adjusted to on the DCH. Vice versa.
Its default value is 384 kbit/s.
4.1.2.28 Switch of CS 64kbps Establishment
 OMC Path

Management-> UtranCell-> UtranCellX->Cell Setup Parameters-> Switch of CS 64kbps
Establishment
This parameter defines whether a cell supports CS64K s ervices. When the par ameter is
ON, the cell supports CS64K services; when the paramet er is OFF, the cell does not
support CS64K services. Its default value is open.
4.1.2.29 Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell
 OMC Path

Management-> UtranCell-> UtranCellX->Modify Advanced Parameter->UtranCell->
Maximum Bit Rate on UL DCH for NRT PS RAB(kbps)

This parameter defines the uplink rate higher threshold of NRT PS services in a cell. The
higher the parameter value is, the higher the uplink rate higher threshold of users on the
DCH in the cell is, and vice versa.
4.1.2.30 Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell
 OMC Path
Path: View->Configuration Managem ent-> RNC NE-> RNC Radio Res ource
Management-> UtranCell-> UtranCellX->Modify Advanced Parameter->UtranCell->
Maximum Bit Rate on DL DCH for NRT PS RAB(kbps)
This parameter defines the downlink rate higher threshold of NRT PS services i n a cell.
The higher the paramet er value is, the higher the downlink rate higher threshold of users
on the DCH in the cell is, and vice vers a.
4.1.2.31 Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
 OMC Path

>External Utran Cell-> External Utran CellX-> Modify Advanced Parameter-> Maximum
Bit Rate on UL DCH for NRT PS RAB in External UTRA N Cell
 Parameters Configuration
This parameter indicates the maximum bit rate on UL DCH allowed in External UTRAN
Cell for an NRT PS domain RAB.
The default value is384kbps.
4.1.2.32 Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
 OMC Path

Bit Rate on UL DCH for NRT PS RAB in External UTRA N Cell

This parameter indicates the maximum bit rate on UL DCH allowed in External UTRAN
cell for an NRT PS domain RAB.
4.1.2.33 Maximum Bit Rate on DL DCH for NRT PS RAB in External UTRAN Cell
 OMC Path

Bit Rate on DL DCH for NRT PS RAB in External UTRA N Cell
This parameter indicates the maximum bit rate on DL DCH allowed in External UTRAN
Cell for an NRT PS domain RAB.
4.1.2.34 Maximum Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell
 OMC Path

Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell
This parameter indicates the maximum bit rate on DL DCH allowed in External UTRAN
cell for an RT PS domain RAB.
4.1.2.35 Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell
 OMC Path

>UtranCell->UtranCellX->Modify Advanced Parameter-> UtranCell-> Maximum Bit Rate
on UL DCH for RT PS RAB in Serving Cell

This parameter defines the uplink rate higher threshold of RT PS services in a cell. The
4.1.2.36 Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell
 OMC Path

on DL DCH for RT PS RAB in Serving Cell
This parameter defines the uplink rate higher threshold of RT PS services in a cell. The
4.1.2.37 Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell
 OMC Path

on E-DCH for NRT PS RAB in Serving Cell
This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
NRT PS domain RAB.
The default value is 5760kbps.
4.1.2.38 Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell
 OMC Path

>UtranCell->UtranCellX->Modify Advanced Parameter->ExternalUtranCell-> Maximum
Bit Rate on E-DCH for RT PS RAB in Serving Cell

This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
RT PS domain RAB.
4.1.2.39 Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
 OMC Path

Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
This parameter indicat es the maximum bit rate on E-DCH allowed in External UTRAN
cell for an NRT PS domain RAB.
4.1.2.40 Maximum Bit Rate on E-DCH for RT PS RAB in External UTRAN Cell
 OMC Path

Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
This parameter indicat es the maximum bit rate on E-DCH allowed in External UTRAN
cell for an RT PS domain RAB.
4.1.2.41 Switch of CS 64kbps Establishment for External UTRAN Cell
 OMC Path

Management->External Utran Cell-> External Utran CellX->Global Else-> Switch of CS
64kbps Establishment for External UTRAN Cell

This paramet er defines whet her a RNC cell adjacent to IUR supports CS 64K services.
When the parameter is OPEN, the adjacent RNC cell supports CS64K services; when
the paramet er is CLOSED, the cell does not support CS64K services.
4.1.2.42 Quality Measurement Switch for VoIP/CS Voice
 OMC Path

> Modify Advanced P arameter-> Dynamic Radio Bearer Control Information ->Qualiy
Measurement Switch for VoIP/CS Voice
 Parameter configuration
This parameter defines traffic quality mesurement switch for VoIP/CS Voice.
The default value is opened
4.1.2.43 Max CS Delay
 OMC Path

Information->Max CS Del ay
This parameter is the max buffer delay for CS voice.
The default value is 60(ms)
4.1.2.44 Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One
Step Upward
 OMC Path

Information->Wait Timer for A djusting Uplink and Downlink Rec onfiguration by One Step
Upward

This parameter defines the timer used for waiting UL and DL upward reconfiguration in
one step.
The default value is 30 (100ms)
4.1.2.45 Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One
Step Downward
 OMC Path

Information->Wait Timer for A djusting Uplink and Downlink Rec onfiguration by O ne Step
Downward
This parameter defines the timer us ed for waiting UL and DL downward reconfiguration
in one step.
The default value is 30 (100ms)
4.1.2.46 Initial Rate of UL DCH
 OMC Path

Information-> Initial Rate of UL DCH(kbps)
This parameter defines the Uplink initial rate of DCH setup traffic.
The default vaule is 64kbps
4.1.2.47 Initial Rate of DL DCH
 OMC Path

Information-> Initial Rate of DL DCH(kbps)

This parameter defines the Uplink initial rate of DCH setup traffic.
The default vaule is 64kbps
4.1.2.48 UE Traffic Volume Measurement Report Method
 OMC Path

> Modify Advanc ed Paramet er-> Dynamic Radio Bearer Control Information-> UE Traffic
Volume Measurement Report Method
This parameter indicates the report method of the UE t raffic volume measurement.
Periodic report or event report.
Its default value is event report.
4.1.2.49 UL Controled MBR Switch
 OMCR

>UtranCell->UtranCellX->Modify Advanc ed Parameter->Modify Advanced Parametr-
>UtranCell->UL Controled MB R Switch
This parameters specifies the switch for the UL Cont roled MBR function.
Its default value is closed.
4.1.2.50 DL Controled MBR Switch
 OMCR

>UtranCell->DL Controled MB R Switch
This parameters specifies the switch for DL Controled MBR function.

Its default value is closed.
4.1.2.51 UL Controled MBR
 OMCR

>UtranCell->UL Controled MB R
This parameter specifies the MBR value in the DL controlled MB R function.
Its default value is 5760000bps.
4.1.2.52 DL Controled MBR
 OMCR

> UtranCell->UtranCellX->Modify Advanc ed Parameter->Modify Advanced Parametr-
>UtranCell->DL Controled MB R
This parameter specifies the MBR value in the DL controlled MB R function.
Its default value is 21096000bps.
4.1.2.53 Switch of non Emergency CS Service Access to CELL_FACH On RRC
 OMCR

Management-> Modify Advanced Parameter-> Dynamic Radio Bearer Control
Information
This parameter indicates whether non emergency CS service access to CELL_FACH on RRC
process. If this switch is ”Off”, It means non emergency CS service will not access to FACH/RACH
or HS-DSCH/RACH on RRC process .

4.2 HSDPA Dynamic Channel Adjustment Related

Parameters

E vent 4B Counter Thres hold for CELL_DCH to
ToFtimes Thr
CELL_FACH
HS/D-> D/D or HS/E->D/ D Based on Quality Measurement
IBChQS wch
Switch for I/B Traffic
HS/D-> D/D or HS/E->D/ D Based on Quality Measurement
SChQS wch
Switch for S Traffic
Delay Time Threshold of D/D-> HS/D or HS/E after HS/D or
DToHs Delay Thr
HS/E ->D/D Triggering by Channel Quality
FdpchSuptInd F-DP CH Support Indicator
MaxDHs Rate Maximum Bit Rate of HS DPA Across Iur Interface
4.2.2.1 Event 4B Counter Threshold for CELL_DCH to CELL_FACH
 OMC Path

> Modify Advanced Parameter->Dynamic Radio Bearer Control Information -> E vent 4B
Counter Threshold for CELL_DCH to CE LL_FACH
For the UE which is using DELL_DCH, if the measurement of the occupied of the uplink
and downlink sending buffers. This parameter indicates the event 4B counter threshold
for CELL_DCH to CELL_FACH. For the UE using CELL_DCH, if the times of the
measured RLC buffer payload of the downlink being smaller than the event 4B‟s
threshold on uplink and the downlink exceed the threshold indicated by this parameter,
the UE will be transferred from CELL_DCH to CE LL_FACH. For I/B traffic class, attempt
accessing CELL_DCH after failure of accessing CELL_FA CH,For S traffic class, attempt
accessing CELL_DCH directly.
The larger this paramet er is, the harder the UE will be transferred from CELL_DCH to
CELL_FACH. Vice versa.

4.2.2.2 HS/D->D/D or HS/E->D/D Based on Quality Measurement Switch for I/B

Traffic
 OMC Path
Information -> HS/D->D/ D or HS/E->D/D Based on Quality Meas urement Switch for I/B
Traffic
This parameter indic ates whether downlink service trans ferring from HS -DSCH to DCH
for I/B services based on Quality Measurement is supported. This transferring is started
by 1F events according to channel quality.
When this parameter is set to open, downlink service transferring from HS -DSCH to
DCH is supported for I/B services by 1F events. When this parameter is set to Closed,
downlink service trans ferring from HS-DSCH to DCH is not supported for I/B services by
1F events.
Its default value is 0: Closed.
4.2.2.3 HS/D->D/D or HS/E->D/D Based on Quality Measurement Switch for S

Traffic
 OMC Path
Information -> HS/D-> D/D or HS/E-> D/D Based on Quality Measurement Switch for S
Traffic
This parameter indic ates whether downlink service trans ferring from HS -DSCH to DCH
for stream services based on Quality Measurement is supported. This transferring is
started by 1F events according to channel quality.
When this parameter is set to Open, downlink service t rans ferring from HS -DS CH to
DCH is supported for stream servic es by 1F events. When this paramet er is set to
Closed, downlink service transferring from HS-DS CH to DCH is not supported for stream
services by 1F events.
Its default value is 1: Open.

4.2.2.4 Delay Time Threshold of D/D->HS/D or HS/E after HS/D or HS/E->D/D

Triggering by Channel Quality
 OMC Path

> Modify Advanc ed Paramet er-> Dynamic Radio Bearer Control Information-> Delay Time
Thres holde of D/ D -> HS/D or HS/E after HS/D or HS/E -> D/ D Triggering by Channel
Quality
This parameter define as the delay of DCH/DCH switch to HS-DSCH/ DCH or HS-
DSCH/E-DCH, which is after HS-DS CH/ DCH or HS-DS CH/E-DCH switch to DCH/DCH
trigger by channel quality
The default value is 10s
4.2.2.5 F-DPCH Support Indicator
 OMCR
View-> Configuration Management->RNC NE-> RNC Radio Resource Management-

>Utran Cell->Utran Cell XXX-> Cell Setup Parameters->Cell F-DPCH Support Indic ator
This parameter indicates whether cell support F-DP CH.
4.2.2.6 Maximum Bit Rate of HSDPA Across Iur Interface

 OMCR

Management-> Modify Advanced Parameter-> Dynamic Radio Bearer Control
Information
This parameter indicates the maximum bit rate of HS-DS CH across Iur
interface.

4.3 HSUPA Dynamic Channel Adjustment Related

Parameters

SrbOnEdchSwc h Switch of supporting SRB on E-DCH
E vent 4B Counter Thres hold for HSPA Using DTX/DRX t o
DxHsBo0E 4b
PCH Shared by Uplink and Downlink
Switch of E-TTI Switching Triggered by User Plane Throughput
EttiTraffVolS wch
Measurement
E vent 4A Counter Thres hold for E-TTI Switching from 10ms to
ETtiEaThd
2ms
E vent 4B Counter Threshold for E-TTI S witching from 2ms to
ETtiEbThd
10ms
FourEchAllowed Four E-DP DCHs Allowed Indicator
4.3.2.1 Switch of supporting SRB on E-DCH
 OMC Path

Information-> Switch of supporting SRB on E -DCH
This parameter defines whether the uplink signaling servic e is established on the E -DCH.
When the parameter is OPEN, and both the cell and UE capability support the R6
protocol, the uplink signaling service is established on the E -DCH; when the parameter
is CLOSE D, both the cell and UE capability support the R6 protocol, and the UE uses
the code word of 2SF2 + 2SF4, the uplink signaling service is established on the E-DCH,
or else the uplink signaling service is established on the DCH.
The default value is closed

4.3.2.2 Event 4B Counter Threshold for HSPA Using DTX/DRX to PCH Shared by
Uplink and Downlink
 OMC Path

Information->E vent 4B Counter Threshold for HS-DSCH/E-DCH Using DTX/DRX to
PCH Shared by Uplink and Downlink
This parameter indicates the event 4B counter threshold for HSPA using DTX/DRX to
PCH shared by uplink and downlink. For the UE using the DTX/DRX, if the times of the
measured RLC buffer payload of the uplink and downlink being zero exceed the
threshold indicat ed by this parameter, UE will be trans ferre d from HSPA to PCH.
The default value is 10
4.3.2.3 Switch of E-TTI Switching Triggered by User Plane Throughput

Measurement
 OMC Path

> Modify Advanced Parameter->Dynamic Radio Bearer Control Information-> Switch of
E-TTI S witching Triggered by User Plane Throughput Measurement
This parameter indicates the switch of E-TTI switching triggered by user plane
throughput measurement. If this parameter is set to “Open”, the function of E-TTI
switching triggered by user plane throughput measurement is valid, otherwise invalid.
The default value is closed.
4.3.2.4 Event 4A Counter Threshold for E-TTI Switching from 10ms to 2ms
 OMC Path

> Modify Advanced Parameter->Dynamic Radio Bearer Control Information -> E vent 4A
Counter Threshold for E-TTI Switching from 10ms to 2ms

This parameter indicates the event 4A counter threshold for switching E-TTI from 10ms
to 2ms. For the UE using E-DCH, if the times of the measured us er plane E -DCH
throughput being larger than the 4A threshold exceed the threshold indicated by this
parameter and 2ms E-TTI is used, UE‟s E-TTI will be switched to 2ms.
The default value is 2 times.
4.3.2.5 Event 4B Counter Threshold for E-TTI Switching from 2ms to 10ms
 OMC Path

> Modify Advanced Parameter->Dynamic Radio Bearer Control Information -> E vent 4B
Counter Threshold for E-TTI Switching from 2ms to 10ms
This parameter indicates the event 4A counter threshold for switching E -TTI from 10ms
to 2ms. For the UE using E-DCH, if the times of the measured us er plane E -DCH
throughput being larger than the 4A threshold exceed the threshold indicated by this
parameter and 2ms E-TTI is used, UE‟s E-TTI will be switched to 2ms.
The default value is 2 times.
4.3.2.6 Four E-DPDCHs Allowed Indicator
 OMC Path
View-> Configuration Management->RNC NE-> RNC Radio Resource Management-

>RNC Configuration Supplement Parameters->Four E-DPDCHs Allowed Indicator
This parameter control whether use 2SF2+2SF4, in which case signal bear on E -DCH,
The value “1“ means capable to us e 2SF2+2SF4 and the value “0“ means not allowed to
use.
4.4 HSPA+ Dynamic Channel Adjustment

Rarameters


T323S wch Switch of T323 broadcasting

UE sending message ”signaling connection release
T323
indication”（with cause）in this interval
4.4.1.1 External Utran Cell Information

IurDcHsdsSuptInd Dual-Cell HS-DS CH Support Indication
SndS vrCelID Possible Secondary Serving Cell ID
4.4.2.1 T323Swch
 OMC Path

Management-> Modify Advanced Parameter-> UE Times and Constants Information
This parameter indicates whether the fast Dormancy is active. When fast dormancy
switch is “On”, RNC send T323 to UE by SIB1 and UTRA N mobility information. UE is
capable switch into dormancy.
4.4.2.2 T323
 OMC Path

Management-> Modify Advanced Parameter-> UE Times and Constants Information
This parameter indicates the interval of reporting signaling connection release indication
（with cause）.
4.4.2.3 Dual-Cell HS-DSCH Support Indication
 OMC Path

Management-> RNC Configuration Supplement Parameters->Dual-Cell HS -DS CH
Support Indication.

This parameter indicate whether Dual -Cell HS -DS CH is support ed for the neighbor cell
over Iur.
Its default value is not support.
4.4.2.4 Possible Secondary Serving Cell ID
 OMC Path

Management-> External UTRAN Cell-> External UTRAN Cell XXX ->Global Else-
>Possible Secondary Serving Cell ID
This paramet er describes the Possible Secondary Serving Cell ID for the neighbor c ell
over Iur.
4.5 UE Traffic Volume Measurement Related

Parameters
4.5.1.1 UE traffic volume measurement relationship

UE Traffic Volume Measurement
UeTrvMCfgNo
Configuration Index
E vent Number of UE Traffic Volume
MeasE vt Num
Measurement
UE Traffic Volume Measurement
MeaE vt Id[MA X_UE_TRV_MEAS_EVE NT]
E vent Identity
Traffic Volume Thres hold of E vent
Rpt Thres[MA X_UE_TRV _MEAS_EVENT]
4A/4B for Non-DCH Channel
Rpt Thres0[MA X_UE_TRV_MEAS_EVE NT]
4A/4B for DCH of 8 kbps


TrigTime[MA X_UE _TRV_MEAS_EVENT] Time to Trigger
PendingTime[MA X_UE_TRV_MEAS_EVENT] Pending Time after Trigger
Throughput Threshold of E vent
ThoughThres [MA X_UE_TRV_MEAS_EVENT]
4A/4B for E-DCH
Time Interval for Taking an A verage
AverageTime
or a Variance
MeasRptTrMod Measurement Report Transfer Mode
MeasQuantity Measurement Quantity
RptRlcBufInd RLC Buffer Payload for Each RB
Average of RLC Buffer Payload for
RptRlcA veInd
Each RB
Variance of RLC Buffer Payload for
RptRlcVarInd
Each RB
RptCrt Report Criteria
Tx Interruption Aft er Trigger
Tx InterCfgP re[MA X_UE_TRV_MEAS_EVENT]
Configuration Tag
Tx Interruption[MA X_UE_TRV_MEAS_EVE NT] Tx Interruption Aft er Trigger
UE Traffic Volume Period
Drbc DchUePrd Measurement Configuration Number
for DCH
UE Traffic Volume Period
Drbc RachUeP rd Measurement Configuration Number
for RACH
Measobj Transport Channel Type
Amount of Reporting in Period
PrdRptAmount
Report Criterial
Reporting Interval in Period Report
PrdRptInterval
Criteria
Function of Configuration
NoteUeTrvMCf
Parameters
4.5.1.2 UE traffic volume measurement relationship in cells

UE Traffic Volume E vent Measurement
Drbc DchUeE vt
Configuration Number for DCH
UP Traffic Volume Measurement Configuration
Drbc DchUp
Number for DCH
UE Traffic Volume E vent Measurement
Drbc RachUeE vt
Configuration Number for RA CH
DrbcFachUp
Number for FACH

DrbcS HsUp
Number for Streaming Class on HS-DSCH
Drbc IBHs Up Number for Interactive and Background Class
on HS -DS CH
UP Throughput E vent Meas urement
DrbcE DchUpThpt
Configuration Number for E-DCH
E-DCH UP Throughput Measurement
ETtiUpThpt
Configuration Number for E-TTI Switching
4.5.2.1 UE Traffic Volume Measurement Configuration Index
 OMC Path
Management -> Modify Advanced Parameter -> UE Traffic Volume Measurement
Configuration-> UE Traffic Volume Measurement Configuration Index
This parameter indicates the UE uplink or downlink traffic volume measurement

configuration index for PS service. There are several different sets of configured values
for uplink or downlink traffic volume measurements according to channel type or
measurement methods (period or event).
This parameter ranges from 0 to 9.
4.5.2.2 Event Number of UE Traffic Volume Measurement
 OMC Path
Configuration -> E vent Number of UE Traffic Volume Measurement
This parameter indicates event number of UE traffic volume measurement. Traffic

volume measurement events are classified to events 4A and 4B. Therefore, the
measurement event number is always 2.
4.5.2.3 UE Traffic Volume Measurement Event Identity
 OMC Path
Configuration -> UE Traffic Volume Measurement E vent Identity
This parameter indicates the event identity of the traffic volume measurement performed by UE.
Since there are two kinds of measurement events in each traffic volume measurement,
measurement event entities are 4a and 4b.
4.5.2.4 Traffic Volume Threshold of Event 4A/4B for Non-DCH Channel
 OMC Path
Management -> Modify Advanced Parameter -> UE Traffic Volumn Measurement
Configuration -> Traffic Volume Threshold of Event 4 A/4B for Non-DCH Channel
This parameter gives the specific value of reporting threshold for different measurement
volume of events 4A and 4B (in bytes).
If the traffic volume measurement value is greater than the threshold of event 4A, a
report of event 4A will be triggered; if t he traffic volume measurement value is smaller
than the threshold of event 4B, a report of event 4B will be triggered.
4.5.2.5 Traffic Volume Threshold of Event 4A/4B for DCH of 8 kbps
 OMC Path

Management->Modify Advanced Parameter->UE Traffic Volumn Measurement
Configuration-> Traffic Volume Threshold of Event 4A/4B for DCH of 8 kbps(bytes)
This parameter gives a specific value (in bytes) of the absolute thres hold measurement
based on the different measurements of 4A and 4B events for 8 Kbps traffic.
If t he traffic measurement value is higher than the 4A event threshold, the 4A event is
triggered; if the measurement value is lower than the 4B event threshold, the 4B event is
triggered.
 OMC Path

Configuration-> Traffic Volume Threshold of Event 4A/4B for DCH of 16 kbps(bytes)
triggered.
 OMC Path

Configuration-> Traffic Volume Tthreshold of Event 4 A/4B for DCH of 32 kbps
triggered.
 OMC Path

triggered.
 OMC Path

triggered.
 OMC Path

Configuration-> Traffic Volume Tthreshold of Event 4 A /4B for DCH of 256 kbps
triggered.
 OMC Path

This parameter gives a specific value (in bytes) of the absolute thres hold measur ement
triggered.
4.5.2.12 Time to Trigger
 OMC Path
Configuration -> Time to Trigger
This paramet er indicates the time difference between having detected the event
generation and reporting the event. Only when the event generation is detected and still
meets all requirements of event triggering after Time to trigger, the event can be
triggered and report ed.
The larger the value is, the stricter the judgment is for the event to be triggered. The
parameter should be set according to the actual requirements. Sometimes, if it is set too
large, customer satisfaction will be decreased.
4.5.2.13 Pending Time after Trigger
 OMC Path
Configuration -> Pending Time A fter Trigger
This parameter indicates the pending time after trigger. The UE is then forbidden to send
new measurement reports triggered by the same event during this time period.
The larger this parameter is, the smaller times the s ame event is triggered in a c ertain
period. Vice versa.
4.5.2.14 UE Traffic Volume Event Measurement Configuration Number for DCH
 OMC Path
Management -> Utran Cell -> Utran Cell XXX -> Modify Advanced P arameter -> UE
Traffic Volume Measurement
This parameter indicates the UE uplink traffic volume meas urement event configuration
number for DCH in the cell. According to this configuration number, you can a
corresponding set of traffic volume measurement parameters in RNC radio parameters.

Management-> Utran Cell-> Utran Cell XXX->Modify Advanced P arameter-> UE Traffic
Volume Measurement Configuration Information In A Cell–〉UE Traffic Volume E vent
Measurement Configration Number for DCH
4.5.2.15 UP Traffic Volume Measurement Configuration Number for DCH
 OMC Path
This parameter indicat es the downlink UP traffic volume meas urement event
configuration number for DCH in the cell. According to this configuration number, you
can a corresponding set of traffic volume measurement paramet ers in RNC radio
parameters.

Volume Measurement Configuration Information In A Cell– 〉 UP Traffic Volume
Measurement Configration Number for DCH
4.5.2.16 UE Traffic Volume Event Measurement Configuration Number for RACH
 OMC Path
This paramet er indicates the UE traffic volume measurement event configuration

number for RACH in the cell. According to t his configuration number, you c an a

Volume Measurement Configuration Information In A Cell–〉UE Traffic Volume E vent
Measurement Configration Number for RACH
4.5.2.17 UP Traffic Volume Measurement Configuration Number for FACH
 OMC Path
This paramet er indicates the UP traffic volume measurement event configuration

number for FACH in the cell. According to this configuration number, you can a

Measurement Configration Number for FACH
4.5.2.18 UP Traffic Volume Measurement Configuration Number for Streaming

Class on HS-DSCH
 OMC Path

number for streaming service on the HS in the cell. According t o this configuration
number, you can a corresponding set of traffic volume meas urement parameters in RNC
radio parameters.

Measurement Configration Number for Streaming Class on HS-DS CH
4.5.2.19 UP Traffic Volume Measurement Configuration Number for Interactive and

Background Class on HS-DSCH
 OMC Path

number for I/B service on the HS in t he cell. According to this configuration number, you
can a corresponding set of traffic volume measurement paramet ers in RNC radio
parameters.

Measurement Configration Number for Int eractive and Background Class on HS -DSCH
4.5.2.20 UP Throughput Event Measurement Configuration Number for E-DCH
 OMC Path
This parameter indic ates the UP throughput measurement event configurat ion number
for the E DCH in the cell. According to this configuration number, you can a

Measurement Configration Number for E-DCH
4.5.2.21 E-DCH UP Throughput Measurement Configuration Number for E-TTI

Switching
 OMC Path

>Utran Cell->Utran Cell XXX->Modify Advanced P arameter-> UE Traffic Volume
Measurement
Parameter Configuration
This parameter indicates the user plane throughput measurement configuration number
for E-DCH, used for E-TTI Switching. According to this configuration number, you can a
4.5.2.22 Throughput Threshold of Event 4A/4B for E-DCH
 OMC Path

>Modify Advanced Parameter->UE Traffic Volumn Measurement Configuration ->
Throughput Threshold of E vent 4A/4B for E-DCH(kbps)
This parameter indicates the reporting thres hold of event 4A and 4B for throughput
measurement on E -DCH. If the throughput becomes larger than the threshold of event
4A, a report of A event will be triggered; and if the throughput becomes smaller than the
threshold of event 4B, a report of 4B event will be triggered.Where
MA X_UE_TRV_MEAS _EVENT is the maximum number of UE throughput measurement
event, which equals to 2.
The default value is [1500,700]kbps,
4.5.2.23 Time Interval for Taking an Average or a Variance
 OMC Path

>Modify Advanc ed Parameter-> UE Traffic Volumn Measurement Configuration-> Time
Interval for Taking an A verage or a Variance(ms)
This parameter indicates whether the report of RLC bufferr payload for each radio bear
is requested or not.
The default value is 100ms.
4.5.2.24 Measurement Report Transfer Mode
 OMC Path
Path:View->Configuration Management->RNC NE-> RNC Radio Resource M anagement-

Measurement Report Trans fer Mode
This parameter indicates the RLC mode of the traffic volume measurement report. If the
value is AM RLC, RNC can request UE for retransmission after receiving the error SDU
label (not continuous). If the value is UM RLC, the retransmission is not required.
Usually, report the results of the important measurements in AM mode and thos e less
important in UM mode (to reduce the traffic volume of the measurement report and
increase the system capacity).
The default value is AM RLC
4.5.2.25 Measurement Quantity
 OMC Path

Measurement Quantity
This parameter indicates the measurement quantity of t he traffic volume measurement

that UE performs. Selected from[1: RLC buffer payload2: A verage RLC buffer payload3:
Variance of RLC buffer payload]
The default value isRLC buffer payload
4.5.2.26 RLC Buffer Payload for Each RB
 OMC Path

>Modify Advanced P arameter-> UE Traffic Volumn Measurement Configuration-> RLC
Buffer Payload for Each RB
This parameter indicates whether the report of RLC buffer payload for each radio bear is
requested or not.
The default value is true
4.5.2.27 Average of RLC Buffer Payload for Each RB
 OMC Path

A verage of RLC Buffer Payload for Eac h RB
This parameter indicates whether the report of A verage of RLC buffer payload for each
radio bear is requested or not.
The default value is False
4.5.2.28 Variance of RLC Buffer Payload for Each RB
 OMC Path

>Modify Advanced Parameter->UE Traffic Volumn Measurement Configuration->
Variance of RLC Buffer Payload for Each RB
This parameter indicates whether the report of Variance of RLC buffer payload for each
radio bear is requested or not.
The default value is False
4.5.2.29 Report Criteria
 OMC Path

>Modify Advanced Parameter-> UE Traffic Volumn Measurement Configuration -> Report
Criteria
This parameter indicates the report r ules of the traffic volume measurement. Select
from [1: Event Reporting Criteria,2: Periodical Reporting Criteria]
The default value is
0 (UE Traffic Volume Period Measurement Configuration Number for DCH): Periodical
Reporting Criteria
1 (UE Traffic Volume E vent Measurement Configuration Number for DCH): E vent
Reporting Criteria
2 (UP Traffic Volume Measurement Configuration Number for DCH): E vent Reporting
Criteria
3 (UE Traffic Volume Period Measurement Configuration Number for RA CH): Periodical
Reporting Criteria
4 (UE Traffic Volume E vent Measurement Configuration Number for RACH): E vent
Reporting Criteria
5 (UP Traffic Volume Measurement Configuration Number for FA CH): E vent Reporting
Criteria
6 (UP Traffic Volume Measurement Configuration Number for Streaming Class on HS-
DSCH): E vent Reporting Criteria
7 (UP Traffic Volume Meas urement Configuration Number for Interactive and
Background Class on HS-DS CH): E vent Reporting Criteria
9 (UP Traffic Volume Meas urement Configuration Number for E-DCH): E vent Reporting
Criteria
10 (E-DCH UP Throughput Measurement Configuration Number for E -TTI S witching):

E vent Reporting Crit eria
4.5.2.30 Tx Interruption After Trigger Configuration Tag
 OMC Path

>Modify Advanced Paramet er-> UE Traffic Volumn Measurement Configuration-> Tx
Interruption A fter Trigger Configuration Tag
This parameter indicates whether Tx interruption after trigger is configured or not.Where

MA X_UE_TRV_MEAS _EVENT is the maximum numbe r of UE traffic volume
measurement event, which equals to 2.
The default value for event [4a 4b] is [False, False]
4.5.2.31 Tx Interruption After Trigger
 OMC Path

>Modify Advanced Paramet er-> UE Traffic Volumn Measurement Configuration-> Tx
Interruption A fter Trigger(ms)
 Paramet er Configuration
This parameter indicates whether Tx interruption after trigger is configured or not.
Where MA X_UE_TRV _MEAS_EVENT is the maximum number of UE traffic volume

measurement event, which equals to 2.
The default value for event [4a 4b] is [250, 250]ms
4.5.2.32 UE Traffic Volume Period Measurement Configuration Number for DCH
 OMC Path

>Modify A dvanced Paramet er-> UE Traffic Volumn Meas urement Configuration-> UE
Traffic Volume Period Measurement Configuration Number for DCH
This parameter indicates the UE traffic volume periodic measurement configuration

number for DCH, used for indexing a set of parameters configured for UE traffic volume
periodic measurement for DCH.

Volume Measurement Configuration Information In A Cell –>UE Traffic Volume Period
Measurement Configuration Number for DCH
4.5.2.33 UE Traffic Volume Period Measurement Configuration Number for RACH
 OMC Path

>Modify A dvanced Paramet er-> UE Traffic Volumn Meas urement Configuration-> UE
Traffic Volume Period Measurement Configuration Number for RA CH
 Paramet er Configuration
This parameter indicates the UE traffic volume periodic measurement configuration

number for RACH, used for indexing a set of parameters configured for UE traffic
volume periodic measurement for RA CH.

Volume Measurement Configuration Information In A Cell –>UE Traffic Volume Period
Measurement Configuration Number for RA CH
4.5.2.34 Transport Channel Type
 OMC Path

Trans port Channel Type
This parameter indicates which type of transport channel this set of traffc volume
measurement paramet ers apply for.
0:DCH
1:DCH
2:DCH
3:RACH
4:RACH
5:FACH
6:HS-DSCH
7:HS-DSCH
9:E-DCH
10:E-DCH
4.5.2.35 Amount of Reporting in Period Report Criteria
 OMC Path

>Modify Advanc ed Parameter-> UE Traffic Volumn Measurement Configuration ->
Amount of Reporting in Period Report Criterial
This parameter indicates the amount of reporting for periodic reporting mode.
0 (UE Traffic Volume Period Measurement Configuration Number for DCH): Infinity
3 (UE Traffic Volume Period Measurement Configuration Number for RA CH): Infinity
4.5.2.36 Reporting Interval in Period Report Criteria
 OMC Path

Reporting Interval in Period Report Criterial(ms)
This parameter indicates the reporting interval for periodic reporting mode.
0 (UE Traffic Volume Period Measurement Configuration Number for DCH): 4000ms
3 (UE Traffic Volume Period Measurement Configuration Number for RA CH): 8000m s
4.5.2.37 Function of Configuration Parameters
 OMC Path

Function of Configuration Paramet ers
This paramet er indicates the purpose and functions of the set of traffic volume
measurement configuration parameters.
0: UE Traffic Volume Period Measurement Configuration Number for DCH
1: UE Traffic Volume E vent Measurement Configuration Number for DCH
2: UP Traffic Volume Measurement Configuration Number for DCH
3: UE Traffic Volume Period Measurement Configuration Number for RA CH
4: UE Traffic Volume E vent Measurement Configuration Number for RACH
5: UP Traffic Volume Measurement Configuration Number for FACH
6: UP Traffic Volume Measurement Configuration Number for Streaming Class on HS -

DSCH
7: UP Traffic Volume Measurement Confi guration Number for Interactive and

Background Class on HS-DS CH
9: UP Traffic Volume Measurement Configuration Number for E-DCH
10: E-DCH UP Throughput Measurement Configuration Number for E-TTI S witching
5 Counter And Alarm
5.1 Counter List

Counter No. Counter Description
C310404201 Number of attempted DCH Uplink DRBC
C310406296 Number of attempted DCH Uplink DRBC(rise rate)
C310406297 Number of attempted DCH Uplink DRBC(reduce rate)
C310404202 Number of successed DCH Uplink DRB C
C310406298 Number of successed DCH Uplink DRB C(rise rat e)
C310406299 Number of successed DCH Uplink DRB C(reduce rate)
C310404203 Number of attempted DCH Downlink DRBC
C310406300 Number of attempted DCH Downlink DRBC(rise rate)
C310406301 Number of attempted DCH Downlink DRBC(reduce rate)
C310404204 Number of successed DCH Downlink DRB C
C310406302 Number of successed DCH Downlink DRB C(rise rat e)
C310406303 Number of successed DCH Downlink DRB C(reduce rate)

C310404205 Number of Success DCH Uplink DRBC,rise rate to 16k
C310404211 Number of Success DCH Uplink DRBC,drop rate to 8k
C310404217 Number of Success DCH Downlink DRBC,ris e rate to 32k
C310404222 Number of Success DCH Downlink DRBC,drop rate to 8k
Number of int ra frequency Transport Channel Changing
C310414096
attempt, HS-DSCH to DCH
C310414097
attempt, DCH to HS-DSCH
C310414098
attempt, FACH to DCH
C310414099
attempt, DCH to FACH
C310414100
attempt, FACH to PCH
C310414101
attempt, PCH to FA CH
C310414102
attempt, HS-DSCH to FACH
C310414103
attempt, FACH to HS-DSCH
C310414104
attempt, E-DCH to DCH
C310414105
attempt, DCH to E-DCH

C310414106
attempt, E-DCH to RA CH
C310414107
attempt, RACH to E-DCH
Number of int ra frequency Transport Channel successful
C310414108
Changing attempt, HS-DS CH to DCH
C310414109
Changing attempt, DCH to HS-DSCH
C310414110
Changing attempt, FACH to DCH
C310414111
Changing attempt, DCH to FACH
C310414112
Changing attempt, FACH to PCH
C310414113
Changing attempt, PCH to FACH
C310414114
Changing attempt, HS-DS CH to FA CH
C310414115
Changing attempt, FACH to HS -DS CH
C310414116
Changing attempt, E-DCH to DCH
C310414117
Changing attempt, DCH to E-DCH
C310414118
Changing attempt, E-DCH to RA CH
C310414119
Changing attempt, RACH to E-DCH
C311855755 Number of HSUPA 2ms E TTI attempted change to 10ms ETTI
C311855756 Number of HSUPA 2ms E TTI successful change to 10ms ETTI
C311855757 Number of HSUPA 10ms ETTI attempted change to 2ms ETTI
C311855758 Number of HSUPA 10ms ETTI successful change to 2ms ETTI
Number of attempted Decreasing Rate on Uplink DCH,
C310405729
Triggered by UE TxP
Number of attempted Decreasing Rate on Uplink DCH,
C310405730
Triggered by Traffic Volume
Number of attempted Decreasing Rate on Downlink DCH,
C310405731
Triggered by D-TCP
Number of attempted Decreasing Rate on Downlink DCH,
C310405732
Number of success Decreasing Rate on Uplink DCH, Triggered
C310405733
by UE TxP
Number of success Decreasing Rate on Uplink DCH, Triggered
C310405734
by Traffic Volume
Number of success Decreasing Rate on Downlink DCH,
C310405735
Triggered by D-TCP
Number of success Decreasing Rate on Downlink DCH,

C310405736
Number of Users of Uplink and Downlink Reconfiguration by
C310405737
one step
5.2 Alarm List

This feat ure has no related alarm.
6 Glossary
B Background
BO Buffer Occupancy
C Conversation
CPC Continuous Packet Connectivity
CN Core Network
DCCH Dedic ated Control Channel
DCH Dedic ated Channel
DL Downlink
DRB C Dynamic Radio Bearer Cont rol
DTCH Dedic ated Traffic Channel
E-DCH Enhanced uplink DCH
FACH Forward Access Channel
F-DP CH Fractional DPCH
GBR Guarant eed Bit Rat e
HS-S CCH High Speed Shared Control Channel
HS-DSCH High Speed Downlink Shared Channel
I Interactive
IMS IP Multimedia Subsystem
MAC Media Access Control
MaxBR Maximum Bit Rate
MBMS Multimedia B roadcast Multicast Service
MCCH MBMS point-to-multipoint Control Channel
MTCH MBMS point-to-multipoint Traffic Channel
MSCH MBMS point-to-multipoint Scheduling Channel
PCH Paging Channel
PDP Packet Data Protocol
P-T-M Point-to-Multipoint
P-T-P Point-to-P oint
QoS Quality of Servic e
RAB Radio access bearer
RACH Random Access Channel
RB Radio Bearer
RL Radio Link
RLC Radio Link Control
RNC Radio Network Controller
ROHC Robust Header Compression
RRC Radio Resource Control
RTCP Real time Control Protocol
S Streaming
S-CCPCH Secondary Common Control Physical Channel
SF Spreading Factor
SIP Session Initiation Protoc ol
TTI Transmission Time Int erval
TF Trans port Format
TFCS Trans port Format Combination Set
TxP Transmission Power
UE User Equipment
UL Uplink
UM Unacknowledged Mode
UTRA N Universal Terrestrial Radio Access Network
VOIP Voice over IP

ZTE UMTS DRBC Algorithm Feature Guide

Uploaded by

Document Information

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

ZTE UMTS DRBC Algorithm Feature Guide

Uploaded by

Copyright:

Available Formats

DRBC Algorithm

DRBC Algorithm Feature Guide

Version Date Author Approved By Remarks

V4.5 2010-10-15 Jiang Ying Wang Zhigang

© 2010 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I

1 Function Attribute ............................................................................................... 1

4 Configuration of Parameters ........................................................................... 69

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II

4.4 HSPA+ Dynamic Channel Adjustment Rarameters ........................................... 97

5 Counter And Alarm ......................................................................................... 116

6 Glossary ........................................................................................................... 119

Figure 2-1 State Transitions .................................................................................................... 2

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. IV

2.1 Function Introduction

WCDMA PS services can be borne on CELL_DCH or CELL_FACH. Based on the

The DRBC policies include:

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1

 Initial Channel Allocation

 Signaling Channel Allocation

 Initial Service Channel Allocation

 Conc urrent Service Channel Allocation

Figure 2-1 State Transitions

DL HS-DSCH/ UL DCH <-> DL DCH/UL DCH

 CELL_DCH service uses channels of the following types: DL HS-DSCH/UL E -DCH,

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 2

and service features. Switching could be performed between different channel

 CELL_FACH service can use DL FA CH/ UL RA CH.

2.1.1 Initial Channel Allocation

 The DL DCH/ UL DCH is chosen for CS real -time services.

 I/B service in PS domain selects channels: DL HS-DSCH/UL E-DCH, DL HS-

 C/S servic e in PS domain selects channels in t he following priority order: DL HS-

Determination of channel rate: For streaming, interactive, or background PS services,

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 3

2.1.2 Channel Switching

 CELL_DCH (DL DCH/ UL DCH) -> CELL_DCH (DL DCH/ UL DCH)

 DL DCH -> DL DCH (rate increase)

 DL DCH -> DL DCH (rate decrease)

 UL DCH -> UL DCH (rate increase)

 UL DCH -> UL DCH (rate decrease)

 CELL_DCH (DL DCH/ UL DCH) <-> CE LL_FACH (DL FACH/UL RA CH)

 CELL_DCH (DL DCH/ UL DCH) -> URA _PCH

 CELL_FACH (DL FA CH/ UL RA CH) <-> URA_P CH

 CELL_DCH (DL DCH/ UL DCH) -> IDLE

 CELL_FACH (DL FA CH/ UL RA CH) -> IDLE

 URA _PCH -> IDLE

 CELL_DCH(DL HS-DS CH/UL DCH) <-> CELL_FACH (DL FA CH/ UL RA CH)

 CELL_DCH(DL HS-DS CH) <-> DL DCH

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 4

 CELL_DCH(DL HS-DS CH/UL DCH) -> URA _PCH

 CELL_DCH(DL HS-DS CH/UL DCH) -> IDLE

 CELL_DCH ( DL HS-DSCH/UL E-DCH) -> URA_P CH

 CELL_DCH (DL HS -DS CH/ UL E-DCH) -> IDLE

The basic policy of DRB C calculation is:

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 5

The optimized dynamic configuration of radio bandwidth is realized based on policies

1 Initial Channel Allocation Calculation

2 Channel Switching Calculation

 The dynamic adjustment SF (DASF) calculation for dedicated channels: to satisfy

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 6

 The changes of downlink dedicated transmission power or uplink transmission

2.3 Dynamic Channel Type Transfer for HSDPA

1. Initial Channel Allocation Calculation

2. Channel Switching Calculation