ZTE UMTS DRBC Algorithm Feature Guide V6!1!201204

DRBC
Guide
Algorithm
WCDMA RAN
Feature
DRBC Algorithm Feature Guide

Version
Date
Author
Reviewer
Notes
(1) Add parameter DchSig68Swch in
chapter 3.1.2.1;
(2) Add parameter DlPsRateLmtLowC,
UlPsRateLmtLowC, DlPsRateLmtHighC,
UlPsRateLmtHighC in chapter 3.1.3.1 and
3.1.3.3;
V6.0
2011-6-16
Wang
(3) Add chapter 3.5 Enhanced FACH
ChengWei
Dynamic Channel Adjustment.

(4) Add chapter 3.7.6 Switching timers
based on UE capabilities;
(5) Update some parameters OMCR path.
(6) Add the related description for CResPara4
in chapter 3.7.3 IUB transmission bandwidth
limitation strategy.
The following section and related parameters
added:
3.7.7
Wang
V6.1
2012-2-28
ChengWei,
Sha Xiubin
CS Experience Improvement
for Concurrence Service with CS+PS

Jiang Qingsong
3.7.8
UE
PCH
Compatibility
Strategy
3.7.9
DRBC F/P->D Performance
Optimization
3.7.10
CELL_PCH Supporting
2012 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary 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
TABLE OF CONTENTS
1
Function Attribute ................................................................................................. 5
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Introduction............................................................................................................ 5
Function Introduction ............................................................................................... 5
Dynamic Channel Type Transfer for R99 Service................................................... 7
Dynamic Channel Type Transfer for HSDPA Service............................................. 9
Dynamic Channel Type Transfer for HSUPA Service........................................... 10
RAB Negotiation & Re-negotiation ........................................................................ 11
27.2Kbps High Speed Signaling RB...................................................................... 12
Fast Dormancy....................................................................................................... 12
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.5.3
3.6
Technical Description ......................................................................................... 12

Dynamic Channel Type Transfer for R99 Service................................................. 12
Introduction to Service Types ................................................................................ 12
Initial Channel Allocation ....................................................................................... 13
Channel Switching ................................................................................................. 19
Related Measurement............................................................................................ 38
Dynamic Channel Type Transfer for HSDPA Service........................................... 47
Signaling Channel Allocation ................................................................................. 47
Initial Service Channel Allocation .......................................................................... 48
Dynamic Channel Type Transfer for HSUPA Service........................................... 59
Signaling Channel Allocation ................................................................................. 59
Dual-Carrier related Dynamic Channel Adjustment .............................................. 74
Concurrent Service Channel Allocation................................................................. 74
Enhanced FACH Dynamic Channel Adjustment ................................................... 75
DL Enhanced FACH Dynamic Channel Adjustment ............................................. 75
UL Enhanced FACH Dynamic Channel Adjustment ............................................. 78
Traffic Measurement .............................................................................................. 80
Fast Dormancy....................................................................................................... 81
3.6.1
3.6.2
3.7
3.7.1
3.7.2
3.7.3
3.7.4
3.7.5
3.7.6
3.7.7
3.7.8
3.7.9
3.7.10
R8 Fast Dormancy ................................................................................................. 81

Pre-R7 Fast Dormancy Suppressing..................................................................... 82
Other Description ................................................................................................... 84
Traffic Sub-class rate matching ............................................................................. 84
MBR Controlling in RNC ........................................................................................ 87
IUB transmission bandwidth limitation strategy..................................................... 88
Be compatible with the IPHONE which is not implement according to encryption
protocol................................................................................................................... 88
The MaxBR of HSDPA on Iur interface ................................................................. 89
Switching Timers Based on UE Capabilities ......................................................... 89
CS Experience Improvement for Concurrence Service with CS+PS ................... 91
UE PCH Compatibility Strategy ............................................................................. 92
DRBC F/P->D Performance Optimization ............................................................. 92
CELL_PCH Supporting .......................................................................................... 93
4
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.3
4.3.1
4.3.2
4.4
4.4.1
4.4.2
4.5
4.5.1
4.5.2
4.6
4.6.1
4.7
4.7.1
Configuration of Parameters.............................................................................. 94
DRBC Related Parameters.................................................................................... 94
Parameter List........................................................................................................ 94
Parameter Configuration........................................................................................ 98
HSDPA Dynamic Channel Adjustment Related Parameters .............................. 126
Parameter List...................................................................................................... 126
Parameter Configuration...................................................................................... 126
HSUPA Dynamic Channel Adjustment Related Parameters .............................. 130
Parameter List...................................................................................................... 130
HSPA+ Dynamic Channel Adjustment Parameters ............................................ 134
Parameter List...................................................................................................... 134
UE Traffic Volume Measurement Related Parameters ....................................... 135
Parameter List...................................................................................................... 135
UE Internal TxP Measurem ent Related Parameters ................................... 156
Parameter List...................................................................................................... 156
Node B Dedicated TCP Measurem ent Related Param eters ...................... 161
Parameter List...................................................................................................... 161
5
5.1
5.2
Counter And Alarm ............................................................................................ 163

Counter List .......................................................................................................... 163
Alarm List ............................................................................................................. 168
Glossary ............................................................................................................. 168
FIGURES
Figure 2-1 State Transitions .................................................................................................... 6
Figure 3-1 R99 Channel Switching ....................................................................................... 19
Figure 3-2 Event Triggering of Traffic Measurement ............................................................ 39
Figure 3-3 Rate Adjustment Triggered by Traffic.................................................................. 41
Figure 3-4 HSDPA Channel Switching ................................................................................. 51
Figure 3-5 Event 1E in Channel Quality Measurement ........................................................ 57
Figure 3-6 Event 1F in Channel Quality Measurement ........................................................ 57
Figure 3-7 HSUPA Channel Switching ................................................................................. 64
Function Attribute
System version: [RNC V3.11. 10/V4.11.10, OMMR V3.11.10/V4.11. 10, Node B V4.11.10,
OMMB V4.11.10]
Attribute: [Optional]
Relat ed NEs:
UE
NodeB
RNC
MSCS
-
MGW
-
SGSN
-
GGSN
-
HLR
-
Note:
*-: Non-related NE:
*: Relat ed NE
Dependency: [None]
Exclusion: [None]
Remarks: [None]
Introduction
2.1
Function Introduction
The dy namic radio bearer control (DRB C) is to allocate resources reasonably according
to subscriber requirements and system resource utilization to make full use of the
bandwidth. ZTE RAN DRB C policies mainly include the following functions:
Initial Channel Allocation
During channel setup, the DRBC allocates proper channel and rate for the service
according to service requirements and system resourc e utilization status. Including:
Signaling Channel Alloc ation
Initial Service Channel Allocation
Conc urrent Service Channel Allocation
Initial Access Rate Allocation for DCH
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 rat e of PS services. If the actual data flow is smaller than the allocat ed
bandwidth, the system decreases the configured bandwidth 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 DRBC adjusts the service bandwidth and channel switching in
real-time according to various measurements. The conversation servic e uses DL
DCH/UL DCH, streaming services use CELL_DCH, and interactive and background
services us e CE LL_FACH or CELL_DCH. 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
Notes:
CELL_DCH service uses channels of the following types: DL HS -DSCH/UL E-DCH,

DL HS-DSCH/UL DCH, and DL DCH/UL DCH. RAN will det ermine different channel
types for services based on different support capabilities of NodeB and UE, and
service feat ures. Switching could be performed between different channel types.
And the rates of DL DCH and UL DCH can be adjusted dynamically.
CELL_FA CH service can use DL FA CH/ UL RACH.
Except that it does not support the switching from URA _PCH to CELL_DCH di rectly,
the channels in URA _PCH, CELL_FA CH, and CELL_DCH states can be switched
among each other.
2.2
Dynamic Channel Type Transfer for R99 Service

R99 DRB C dynamically adjusts the bearer channel and real-time rate of PS services. It
ensures full utilization of radio resources, system stability, and service QoS .
During channel setup, the DRB C allocates radio channel and initial rate to the
service according to service requirements and system resource utilization status.
CS service and Streaming s ervice can use DCH as bearer. The DCH channel
parameters are set according to necessary GBR.
Interactive servic e and Background Servic e may use FACH/RA CH or DCH.
For PS services that use DCH as bearer, its initial access rate can b e set
according to configuration.
Dynamical DCH rat e adjustment.
DCH rate configuration should be consistent with actual traffic rate. When
actual traffic volume drops, DCH rate should be decreased accordingly.
Released resource can be used by other us ers. DCH rate can be increased
when actual traffic volume gets high so as to avoid affecting user experience .
The traffic volume is evaluated in uplink and downlink separately. That is,
uplink traffic volume decides uplink DCH bandwidth while downlink bandwidt h
depends on downlink traffic volume. In reality, it is common that the DCH
bandwidth should be adjusted simultaneously in uplink and downlink. In this
case, ZTE RAN adjusts the DCH bandwidth in uplink and downlink via a single
signalling procedure so that the signalling message on Uu is reduced.
DCH rate downgrade is an alternative method to decrease the system load

when overload or congestion occurs.
If the transmission power exceeds the preset high threshold, the network and
UE will decrease the data rate till the transmission power is lower than the
preset low threshold. By this method, PS servic e subscribers obtain relatively
high data rate when Node B is close, and obtain lower data rate when the
Node B is remote. Thus, the coverage of PS services is expanded. The c all
drop rate of high-rat e servic es during handovers is also decreased.
When UE performs a 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 will downgrade its DCH rate before retrying handover.
Channel switching:
If the practical rate of PS Interactive S ervice or PS Background S ervice below

the traffic volume threshold or if overload occurs in the cell, RAB can switch to
FACH/RACH from DCH and UE then ent ers the CE LL FACH state.
If t he practical rate exceeds the traffic volume threshold of FACH/RA CH, RAB
will switch to DCH and UE then enter the CE LL DCH state.
If the practical rate is zero, radio resource can be released temporarily. UE of

Cell FA CH state or Cell DCH state can be switched to URA PCH state to save
UEs battery power. If it is configured not to use PCH state, RRC can be
released immediately.
When the UE in URA_P CH state originates the cell update message due t o
uplink or downlink data transmission requirements or for new service setup,
the system allocates the channel by the UE servic e type before the UE is
handed over to PCH by the process of initial service channel allocation.
If a UE has resided in URA PCH state for period, the RRC will be released.
ZTE RAN system supports DRBC feature combined with other RRM policy including
Admission Control, Overload Control and Congestion Control. Priorities of users and
services are considered to implement dynamic optimization configuration of radio
bandwidth.
2.3
Dynamic Channel Type Transfer for HSDPA Service

After introducing HSDPA, ZTE RA N system is able to select bearer channel among
Hs-DS CH, DCH or FA CH for the service and configure radio parameters correspondingly,
according to service requirement and system resource utilization status.
ZTE RAN equipments support dy namic channel switching bet ween different channels in
order to satisfy services requirement and system resourc e in the following factor state:
Save system resourc e by adjusting channel type dynamically according to I/B
real-time traffic volume:
When downlink traffic volume is too large, trigger the channel switching from
FACH or DCH to HS-DSCH
When downlink traffic volume is too small, trigger the channel switching from
HS-DSCH to FACH
When there is no downlink traffic volume, trigger the channel switching from
HS-DSCH to PCH or idle
Reduce the system load by adjusting channel type according to cell load.
When cell load is too high, the user can switch from HS-DSCH to FACH to reduce
the system load and maintain the system stability.
Ensure service quality by adjusting channel type according to channel quality.
When UE in HS-DSCH channel moving to cell edge to trigger 1F event, it shows the
channel quality is bad, and then trigger the channel switching from HS -DS CH to
DCH.
Ensure the service continuity by adjusting channel type according to the target cell
for handover.
If the capability of source cell and target cell is different during hand over, the
channel switching between HS-DSCH and DCH will be triggered to guarantee the
service continuity.
Downlink channel switching accompanies uplink channel switching: When downlink
channel is FACH, uplink channel is RACH; when downlink channel is HS -DSCH, uplink
channel can be DCH or E-DCH.
2.4
Dynamic Channel Type Transfer for HSUPA Service

After introducing HSUPA, ZTE RA N system is able to select bearer channel among
E-DCH, DCH or RACH for the service and configure radio paramet ers corres pondingly,
according to service requirement and system resource utilization status.
In order to accommodate requirements of service and practical status of system
resources, ZTE RAN system supports the following functions during channel switching:
Dynamically adjust channel type to s ave system resource according to the practical
traffic volume of I/B services:
If the traffic volume is high, the channel switching from RA CH or DCH to

E-DCH will be triggered
If the traffic volume is low, the channel switching from E -DCH t o RA CH will be
triggered
If no traffic volume, the channel switching from E-DCH to PCH or Idle will be
triggered
Adjust channel type to decrease the system load according to cell load
When the cell uplink is overloaded, the user can be switched to common RACH
from dedicated E-DCH to decrease the system load and guarantee the system
stabilized.
Adjust channel type to guarantee the service quality according to channel quality
If a UE on E-DCH channel moves to the edge of the cell and triggers 1F eve nt, it
10
indicates that the quality of current channel is bad and the channel switching from
E-DCH to DCH will be triggered.
Adjust channel type to guarantee mobile service continuity according to the
capability of target cell
If the capability of source cell and target cell is different during handover, the
channel switching between E-DCH and DCH will be triggered to guarantee the
service continuity.
Uplink channel switching accompanies downlink channel switching: If uplink channel is
RACH, downlink channel is FACH. If uplink channel is E-DCH, generally, downlink
channel is HS-DS CH.
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 can get alternative GBR information
through RAB ASSIGNMENT REQUES Tor RE LOCATION REQUES T from CN, and take
this as the GB R 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 volume measurement reports: the traffic
measurement reports of uplink DCH is from UE; the traffic measurement reports of
downlink DCH, downlink HS-DSCH and uplink E-DCH is from user plane. The traffic
measurement adopts the traffic measurem ent control of DRB C, such as 4A threshold,
trigger time and pending time.
GBR decrease is triggered by cell common overload. When c ommon overload appears,
the executions will be performed as follow: Decreasing the service rate of R99
subscribers, forcedly handing over to inter-frequency or inter-RAT neighboring cell,
deleting the radio link of any soft handover, decreasing GBR, forc edly 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 Servic es and
Radio Access Bearers Feature Guide )
11
2.6
27.2Kbps High Speed Signaling RB

This feature enables the system to use the 27.2 kbps Signaling Radio Bearer (S RB)
when it establishes the RRC connection, and recovers the 3.4Kbps SRB after RAB is
established. If 27.2k SRB is set to apply on OMC, ZTE RA N will employ 27. 2kbps SRB to
speed up t rans ferring the NAS signaling messages (including location update message,
authentication message, and call setup message) bet ween the UE and the CN.
Compared with 13.6kbps SRB, the 27.2 kbps SRB can reduce the call setup time delay
and shorten the SMS service reception. For detail of 27.2 kbps SRB ,please see the
chapter 3.1.2.1Signaling Channel Allocation.
2.7
Fast Dormancy
This feature includes two functions: R8 Fast dormancy and Pre -R7 Fast dormancy
suppressing. R8 Fast dormancy function can extend UE battery usage and improve user
experience. Pre-R7 Fast dormancy suppressing function can reduce the control plane
signaling load for smart phone on the premise that guarant eeing user experience. For
the detail, please see the chapter 3. 5 Fast dormancy.
Technical Description
3.1
Dynamic Channel Type Transfer for R99 Service
3.1.1
Introduction to Service Types

Because different types of servic es have different features, the services have different
requirements for the occupied channel res ources during channel allocation. Currently,
the services can be categorized into four types: Conversation, Int eractive, Background,
and Streaming.
The conversation and streaming services are real-time services, and interactive and
background services are not real-time services.
12
3.1.2
Initial Channel Allocation
3.1.2.1
Signaling Channel Allocation

The OMC provides various parameter options so that the signaling rat e can be flexibly
configured by the parameter InitRrcOnDch at different rates on different channels in the
case of RRC connection establishment.
When the parameter InitRrcOnDch is set to0 ,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.
When the parameter I nitRrcOnDch is set to1 ,the RNC sets the initial signaling to
use common channel forcibly
uplink RA CH or downlink FACH channel for the UE to bear signaling.
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 immediat ely 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 updat e, instead of setting up s ervices, that should
be complet ed after RRC connection, RNC will select common channel to bear
signaling.
13
channel is used
select the dedicat ed channel (13.6 kbit/s) or common channel bas ed on the reason
connection, RNC will select DCH channel and configures bidirectional 13.6 kbit/s
bear signaling; if there is only LA updat e, instead of setting up services, that should
be complet ed after RRC connection, RNC will select common channel to bear
signaling.
channel is used
select the dedicat ed channel (27.2 kbit/s) or common channel bas ed on the reason
connection, RNC will select DCH channel and reconfigures bidirectional 27. 2 kbit/s
bear signaling; if there is only LA updat e, instead of setting up services, that should
be completed after RRC connection, RNC will reconfigure common channel to bear
signaling.
forcibly use HSPA.
When a UE sends a connection setup request to RNC, if both the UE and the cell
support F-DPCH, both CresPara7 and RncFdpchSupInd are 1,(or both the UE
and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd are 1 ),
and both
the UE and the cell support E-DCH,, and SrbOnEdc hS wch is on, and the
14
channel quality measurement is not 1F event, the RNC configures the HSPA for the
UE to bear signaling.
choose channel automatically, and HSPA is prior, when Cell_DCH state is used
select the Cell_DCH state channel or Cell_FA CH state channel based on the
reason for connection setup ,and HSPA is prior, when Cell_DCH state is used.
When the RNC sets the initial signaling to c hoose c hannel automatically, the signaling
will be s et on Cell_DCH state bearer in preference if the signaling is set due to t he
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 Cell_FA CH state bearer.
High-rate (13.6 kbit/s,27.2kbps) signaling bearer only exits in a separat e signaling
process, and will be restored to ordinary rate (3.4 kbit/s) after the service is set up.
High-rate signaling can effectively speed up the signaling int eraction 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 separate 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.
Note: During RRC connection setup when signaling is carried on DCH , or when RAB has been
setup and signaling is carried on DPCH alone , and if signaling is setup with DCH low rate:
If DchSig68S wc h is on, it will substitute 3.4kbps signaling with 6.8 kbps signaling; Otherwise, If
DchSig68S wch is off, 3.4kbps signaling is used.
3.1.2.2

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:
15
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 FA CH/ UL RACH 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 MaxBR is greater than or
equal to Rrach, the DL DCH/UL DCH is chosen in preference. Otherwis e, the DL
FACH/UL RA CH is chosen in preference. If FACH/RA CH is rejected to access, the RNC
will reselect the DL DCH/UL DCH to access.
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 the new service is determined by the same method as
that for a single service.
If the subscriber is in the CE LL_FACH state, the system judges whether to perform
state transitions according to the new service type.
If the new service should be set up on the DL DCH/ UL DCH channel according
to the channel alloc ation 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 FACH/UL RA CH channel according to

the channel allocation principles as for a single service, the UE keeps in the
CELL_FA CH 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 DRBC rate (max (highest rate level of DRB C, GBR), MaxBR). The
16
uplink
and
downlink
DRB C
rate
levels
are
configured
UlRateAdjLev[MAX _NUM_RATE_A DJUST]
by
and
DlRateAdjLev[MAX _NUM_RATE_A DJUST] separately.

If the DRB C switch DrbcSwch is ON, the DCH rate of PS (S/I/B) services is the
minimum DRB C rate of DCH (see 3.1.2.5). 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
and
DlRateAdjLev[MAX _NUM_RATE_A DJUST] separately.

Where, the GBR of streaming servic es 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.
3.1.2.4
The Access Strategy of CS64K Service

According to some special scenarios where CS64K service is not expected to
access/handover in a cell, parameters Cs64k Switch and AdjCs64S witch are used to
control
whether cells support CS64k service in SRNC and DRNC, respectively. When
CS64k service is restricted in a cell, ingoing and handover of CS64k service are
forbidden.
Initial access scene: if the switch Cs64S witch in the cell is off ,CS 64k service is not
allowed to access; otherwise CS 64k service is allowed. For the UE in macro
diversity, if any cell of the active set is not allowed to access CS 64k service, it is not
allowed.
Handover scene: When handover happens in intra-RNC cells and CS64k service is
covered, if Cs64k Switch in target cell is off and UE supports CS64k falling back to
AMR12. 2k, then CS64k falls back to AMR12.2k and UE performs the related
disposal about handover, otherwise UE doesnt perform any disposal. When
handover happens in inter-RNC cells and CS 64k service is covered, if
AdjCs64k S witch in target cell is off and UE supports CS64k falling back to
AMR12. 2k, then CS64k falls back to AMR12.2k and UE performs the related
disposal about handover, otherwise UE doesnt perform any disposal. If the
configuration in DRNC cell and SRNC cell is not given, the cell is defaulted to
17
support CS64k.
3.1.2.5
DCH Initial Access Rate for PS Service

The initial access rate of DL DCH/ UL DCH of PS services is determined in t he following
way:
If t he DRB C switch DrbcS wch is set to OFF, the DCH initial rate is min(max (t he highest
rate level of DB RC, GBR), MaxBR). The uplink and downlink DRB C rate levels are
configured
by
UlRateA djLev[ MAX_NUM_RATE_A DJUST]
and
DlRateAdjLev[MAX _NUM_RATE_A DJUST] separately,the MaxBR is the maximum bit

rate of RAB alloc ation by Iu interfac e.
If the DRB C switch DrbcS wch is ON, the DCH initial rate is min(max (Initial Access Rate
for DCH, GBR), MaxBR, DCH Limited Rate). Here, the uplink and downlink Initial
Access Rate for DCH is configured by parameter InitialRat eUl and InitialRateDl
separately, If the admission decision for the DCH initial rate is failed, UL and DL DCH will
try to access with the minimum DRBC rate of DCH at the same time, which is defined as
min( max(the lowest rate level of DB RC, GBR), MaxBR, DCH Limited Rate).
Here, for the DCH Limited Rate:
In the case of intra-RNC, parameters RtMaxUlRateDch / RtMaxDlRateDch (for RT
service) and NrtMaxUlRateDch / Nrt MaxDlRateDch (for NRT service) are used to limited
the DCH maximum rate of uplink and downlink respectively.
In the case of inter-RNC, parameters Rt MaxUlRateDc hD / RtMaxDlRateDchD (for RT
service) and Nrt MaxUlRateDchD / Nrt MaxDlRateDchD (for NRT service) are used to
limited the DCH maximum rate of uplink and downlink res pectively. If the relat ed
parameters are not configured in the neighboring cells, the restriction decision does not
effect.
In the case of macro diversity, the DCH Limited Rate is set to the minimum limited rate
value of all the cells in the active set.
18
3.1.3
Channel Switching
The channel switching and dynamic resource adjustments are performed only when t he
DRB C switch (DrbcSwc h) is ON.
During the session, the dynamic channel switching for t he 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 protoc ol.
Figure 3-1
R99 Channel Switching

Reconfig SF
1. UL/DL Traffic Volume
Based
2. DL D-TCP Based
3. UL TxP Based
4. Cells RTWP
5. Cells TCP
Transition of DCH/DCH -> FACH/RACH

1. UL&DL Traffic Volume Based
2. Support CELL_FACH
CELL_DCH
DCH/DCH
FACH/RACH
Transition of FACH/RACH -> DCH/DCH

1. UL/DL Traffic Volume Based
2. Cells RTWP & Cells TCP
CELL_FACH
Transition of FACH/RACH -> PCH
2. Support PCH
Transition of DCH/DCH -> PCH

2. Support PCH
Transition of PCH -> FACH/RACH

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

Transition of DCH/DCH ->IDLE

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 increase is based on the traffic measurement report (E vent 4A)
from the user plane and determined by the dedicated transmission power of t he
subscriber and cell load.
The 4A event is defined as the t raffic measurement larger than an absolute threshold.
See 3.1.4.1Traffic Measurement for its detailed definition.
19
The E vent A is defined as that the Node B downlink dedicated transmission power
(D-TCP ) is greater than an abs olute threshold. The E vent B is defined as that t he Node B
downlink dedicat ed transmission power (D-TCP) s smaller t han an abs olute threshold.
See 3.1.4.3Node B Dedicat ed 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 wc h is on.
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 DtcpEbThd measurement reports (E vent B) of
NodeB D-TCP, that is, the UE is in B state. (Note: if the system receives a
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 details of overload t hres hold, 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], DCH Limited
Rate, DL MaxB R). The MaxBR is the maximum bit rat e 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], DCH Limited
Rate, DL MaxB R).
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 DRBC downlink rate levels DlRateA djLev[ MAX_NUM_RATE_ADJ UST], DL
MaxB R, DCH Limited Rate, MaxRateMD).
20
The target rate of RT Downlink DCH rate is min (next rate level greater than the c urrent
rate in DRBC downlink rate levels DlRateA djLev[ MAX_NUM_RATE_ADJ UST], DL
MaxB R, the minimum
DCH Limited Rate, MaxRateMD).
Here, for t he DCH Limited Rate explanation, please see 3.1.2.5; The MaxRat eMD is
the maximum rate thres hold allowed for DCH when the UE is in macro diversity.
In addition, 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
downlink rat es of concurrent PS services of NRT can not exceed
DlPsRateLmtLowC
If the rate of C (CS) services exceeds CRateThrd, the sum of downlink rates of
concurrent PS services of NRT can not exceed DlPsRateLmtHighC
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 transmiss ion of
the subscriber is decreased.
Lower the bandwidth of the subscriber and transmission power to ensure the QoS
for the s ubscriber when the downlink transmission power of the subscriber is too
high.
Lower the bandwidth of the subscriber and the system load to ensure the system
stability when the cell load is too high.
Therefore, the downlink DCH rate decrease can be triggered by the following factors:
21
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 trigge r the rat e decrease.
1.
Rate decrease triggered by downlink traffic
The DCH to DCH switching for downlink rate decrease 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.1Traffic Measurement for its detailed definition.
The DL rate decrease 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 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 smaller than the
None-real-time I/B services: [current uplink rate of the UE is greater than or equal to
the rate threshold Rrach for RA CH switching] or [downlink target rat e is greater than
or equal to the rate threshold Rfach for FA CH 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 GB R of RAB
allocation
In the case of rate increas e of DCH, the target rate is calculated by the formula: max
(next rat e level smaller than the c urrent rate in DRBC downlink rate levels
22
DlRateAdjLev[MAX _NUM_RATE_A DJUST],
GBR).
The
GBR
of int eractive and
background services is 0, and the GB R of streaming services is the GBR of RAB

allocation.
2.
Rate decrease triggered by Node B downlink dedicated transmission power
The DCH to DCH switching for downlink rate decreas e 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 t ransmission 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.3Node B Dedicat ed 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 DlP wrDasf is on.
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 rec eives a
measurement report (E vent B) by Node B when the receiving times are smaller than
the threshold, the corresponding counter is cleared.)
Non-real-time I/B services: current rate is greater than minimum rate in DCH (lowest
rate level configured by DlRateAdjLev[ MAX_NUM_RATE _ADJUST] ); real-time S
services: current rat e is greater than the GBR of RAB allocation
GBR).
The
GBR
of int eractive and
background services is 0, and the GBR of streaming servic e 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.
23
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 confi gured by DlRateAdjLev[ MA X_NUM_RATE _ADJUS T] ); real-time S
GBR).
The
GBR
of int eractive and
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 Feature Guide.
4.
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 resources or power are congested.
rate level configured by DlRateAdjLev[ MA X_NUM_RATE _ADJUS T] ); real-time S
GBR).
The
GBR
of int eractive and
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 Feature
Guide.
5.
24
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 DRBC rate t o admit the user again. The minimum rate is min (max (lowest
level of DRBC downlink rate levels DlRateAdjLev[ MAX_NUM_RATE _ADJ UST], DL
GBR), DL MaxBR).
For more details of mobility, see ZTE UMTS handover Control Feature Guide .
6.
Take the 6000ms as period, checking periodically whether there exist NRT or RT
services which exceed DCH rate limitation Nrt MaxDlRateDch or Rt MaxDlRateDch. If so,
choose no more than 5 users to decrease rat e, and the NRT traffic target rate is
Nrt MaxDlRateDch and NRT traffic target rate is Rt MaxDlRateDc h
3.1.3.3
UL DCH -> UL DCH (Rate Increase)

1.
Rate increase triggered by uplink traffic.
The DCH to DCH s witching for uplink rate increase is based on the traffic measurement
report (E vent 4A) by the UE and determined by the cell's dedicated transmissi on power
and cell load.
The 4A event is defined as the t raffic measurement larger than an absolute threshold.
See 3.1.4.1Traffic Measurement for its detailed definition.
The uplink DCH rate increase is triggered in the case of the following conditions:
4A) from the UE. (Not e: 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 6B) triggered by UE

transmission power, that is, UE uplink transmission power is in 6B state (Note: for
details, see 3.1.4.2UE internal TxP Meas urement )
25
The uplink load of the cell is not overloaded (Note: the uplink load is d etermined 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 t han the current rate in t he
DRB C uplink rate levels UlRateAdjLev[ MAX_NUM_RATE _ADJUST], DCH Limit ed
Rate, UL MaxB R). The MaxBR is the maximum bit rat e 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], DCH Limited
Rate, 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 DRBC uplink rate levels UlRateAdjLev[ MAX_NUM_RATE _ADJ UST], UL MaxBR,
the target rate of Rt Downlink DCH rate is min (next rate level greater than the current
rate in DRB C Uplink rat e levels UlRateAdjLev[ MAX_NUM_RATE _ADJ UST], UL MaxBR,
Here, for t he DCH Limited Rate explanation, please see 3.1.2.5; The MaxRat eMD is
the maximum rate thres hold allowed for DCH when the UE is in macro diversity.
In addition, in case of the concurrence of C (CS) services and PS (S/I/B) services, the
additional principles of PS service rate increase 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
uplink
rates
of
concurrent
PS
services
of
NRT
can
not
exceed
UlPsRateLmtLowC
If the rate of C (CS) services exceeds CRateThrd, the sum of uplink rates of
concurrent PS services of NRT can not exceed UlPsRateLmtHighC
26
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 to ensure the 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.
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 traffic measurement
report (E vent 4B ) from the user plane.
absolute threshold. See 3.1. 4.1Traffic Measurement for its detailed definition.
27
If the system receives consecutive DchE 4bThd traffic measurement reports (Event
4B) of the UE. (Note: if the system receives a traffic meas urement report (E vent 4A)
by the UE when the rec eiving times are smaller than the threshold, the
corresponding counter is cleared)
None-real-time I/B services: [current uplink rate of the UE is greater than or equal to
the rate threshold Rrach for RA CH switching] or [downlink target rat e is greater than
or equal to the rate threshold Rfach for FA CH 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 GB R of RAB
allocation
The target rate of DCH rate decrease is max (next rate level smaller than the c urrent rate
in DRBC uplink rate levels UlRateA djLev[ MAX_NUM_RATE_A DJUST], GBR). The GB R
of interactive and background services is 0, and the GB R 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 6A). When the UE is far away from the base station
and its transmission power reaches the maximum, the UL DCH rate can be decreased to
lower the UE transmission power to avoid interferenc e with other subscribers. When t he
UE comes close to the base station, the traffic can trigger the UL DCH rate increase.
The E vent 6A is defined as that the UE dedicat ed transmission power exceeds an
absolute threshold, namely, the UE is in high power status. For specific configurations of
threshold, see 3.1.4.2UE internal TxP Measurement.
The DCH rate adjustment triggered by UE dedicated transmission power switch
UlP wrDasf
is on.
28
Receive the measurement reports (E vent 6A) 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
The target rate of DCH rate decrease is max (next rate level smaller than the cur rent rate
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)
The target rate of DCH rate decrease is max (next rate level smaller than the current rate
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.
29
The CE uplink resources or power are congested.

The target rate of DCH rate decrease is max (next rate level smaller than the current rate
For more details of congestion control, see ZTE UMTS Congestion Control Feature
Guide.
5.
When the UE performs hard handover from one R99 cell to anot her 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 rat e i s min (max
(lowest level of DRBC uplink rate levels UlRateA djLev[ MAX_NUM_RATE_A DJUST], UL
GBR), UL MaxBR).
6.
Take the 6000ms as period, checking periodically whether there exist NRT or RT
services which exceed DCH rate limitation Nrt MaxDlRateDch or Rt MaxDlRateDch. If so,
choose no more than 5 users to decrease rat e, and the NRT traffic target rate is
Nrt MaxDlRateDch and NRT traffic target rate is Rt MaxDlRateDc h
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 RACH)

When the UE is in the CELL_DCH (DL DCH/UL DCH) state, the switching from
30
CELL_DCH (DL DCH/UL DCH) to CELL_FACH (DL FACH/UL RACH) can be

triggered by the traffic meas urement report (E vent 4B) from the user plane and UE.
absolute threshold. For details, see 3.1.4.1Traffic Measurement .
The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FACH (DL FACH/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 the UE is smaller than the maximum downlink rat e
threshold Rfach, and the current uplink rate is smaller than the maximum
uplink rat e 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_FA CH.
If the condition for CELL_FACH switching is met, but the the admission for
CELL_FA CH fails, 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
and
DlRateAdjLev[MAX _NUM_RATE_A DJUST], UL DCH or DL DCH rate decrease is

selected.
31
ii
CELL_FA CH (DL FA CH/ UL RACH) -> CELL_DCH (DL DCH/ UL DCH)
When the UE is in the CE LL_FACH (DL FA CH/UL RACH) state, the s witching from
CELL_FA CH (DL FACH/UL RA CH) to CELL_DCH (DL DCH/ UL DCH) can be
triggered by the traffic meas urement report (E vent 4A) from the user plane or UE.
The switching from CE LL_FACH (DL FACH/ UL RACH) to CELL_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 user 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 rat e of DRB C after the CELL_DCH
switching, which is [UL initial rate, DL initial rate] (see 3.1.2.2) The GB R of
interactive and background services is 0.
2.
CELL_DCH to CELL_FA CH channel switching triggered by load
The switching from CE LL_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_FACH (DL FA CH/UL RA CH)
is triggered in the case of the followin g conditions:
The downlink cell load exceeds the overload threshold (Note: the downlink
load is determined by TCP. For the 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 _PCH can be triggered by the traffic
32
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.1Traffic Measurement for its detailed definition.
The switching from CE LL_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 system receives 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 the concurrent services exist, it is requi red that all the services should meet the
condition for switching to URA_P CH.
If the concurrenc e of CS and PS services or multiple PS services occurs, and both the
uplink and downlink traffic measurement values of a PS I/B service are 0, and then the
system receives consecutive DToPchThd traffic measurement reports of E vent 4B 0 from
the user plane and UE: if GResPara4 is set to 0:support PS (0 kbps/0 kbps), the rate of
the PS service is decreased to 0 kbps /0 kbps, and keep in CELL_DCH state without
switching; if GResPara4 is set to 1:not support PS (0 kbps/0 kbps ), the rate of t he PS
service is decreased to the minimum DRB C rate.
3.1.3.7
CELL_FACH (DL FACH/UL RACH) <-> URA_PCH

1.
CELL_FA CH (DL FA CH/ UL RACH) -> URA _PCH
When the UE uses the CELL_FA CH to bear the int eractive and background servic es, the
switching from CELL_FA CH to URA _PCH can be triggered by the traffic measurement
report (E vent 4B 0) from the user plane and UE.
The switching from CELL_FACH to URA_P CH is triggered in the cas e of the following
33
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_FACH (DL FACH/UL RA CH)
When the UE in URA_P CH state originates the cell update message due to uplink or
downlink data transmission requirements or for new service s etup, the system allocates
the channel by the UE service type before the UE is handed over to PCH 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 us es the CE LL_DCH for service bearer, the switching from CELL_DCH to
IDLE is triggered in the case of the following conditions:
The system receives cons ecutive DToI dleThd 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 to IDLE, the occupied radio resources are releas ed and
the UE returns to the standby status.
34
3.1.3.9
CELL_FACH (DL FACH/UL RACH) -> IDLE

When the UE uses the CELL_FA CH to bear the int eractive and background servic es, 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 to IDLE, the occupied radio resources are releas ed 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
Uplink and downlink reconfiguration in one step

Uplink and downlink reconfiguration in one step is used for the scene when UL DCH and
DL DCH of the same RBs rate reconfiguration happens in succession during a short time.
This function can reduce the signaling messages on Uu interface. .
Uplink and downlink reconfiguration in one step is only applied to the channel
reconfiguration triggered by traffic volume measurement. The channel reconfiguration
triggered by other factors will be performed directly.
When DrbcS wch is UL&DL both on, the uplink and downlink reconfiguration in one step
scenes are as following:
UL DCH -> UL DCH(rate inc reas e)based on traffic volume
If UL DCH satisfies the rat e increase conditions in advance, start the timer
35
UpUdRecfgTimer
If before the timer UpUdRecfgTimer expires, DL DCH also satisfies the rate increase
conditions triggered by traffic volume, the uplink and downlinks rate increase
reconfiguration in one step is tried, if the admission decision is failed, try DL rate increase,
if it fails again , then go on to try UL rate inc rease.
If before the timer UpUdRecfgTimer expires, DL DCH s atisfies the rate decrease
conditions triggered by traffic volume, the uplinks rate increase and downlink s rate
decrease reconfiguration in one step is tried, if the admission decision for uplinks rate
increase is failed, then go on to perform DL rate decrease rec onfiguration.
If before the timer UpUdRecfgTimer expires, UL DCH does not satisfy the rate increase
conditions anymore, stop the UpUdRecfgTimer, and do not reconfigure UL DCH.
If the timer UpUdRecfgTimer expires, only UL rate increase reconfiguration is tried .
DL DCH -> DL DCH(rate inc reas e)based on traffic volume
If DL DCH satisfies the rat e increase conditions in advance, start the timer
UpUdRecfgTimer
If before the timer UpUdRecfgTimer expires, UL DCH also satisfies the rate increase
conditions triggered by traffic volume, the uplink and downlinks rate increase
reconfiguration in one step is tried, if the admission decision is failed, try DL rate increase,
if it is failed again, then go on to try UL rate increase.
If before the timer UpUdRecfgTimer expires, UL DCH s atisfies the rate decrease
conditions triggered by traffic volume, the uplinks rate decrease and downlink s rate
increase reconfiguration in one step is tried, if the admis sion decision for DL rate
increase is failed, then go on to perform UL rate decrease rec onfiguration.
If before the timer UpUdRecfgTimer expires, DL DCH does not satisfy the rate increase
conditions anymore, stop the UpUdRecfgTimer, and do not reconfigure DL DCH.
If the timer UpUdRecfgTimer expires, only DL rate increase reconfiguration is tried .
UL DCH -> UL DCH(rate decrease)based on traffic volume
36
If UL DCH satisfies the rate decrease conditions in advance, start the timer
DnUdRecfgTimer
If before the timer DnUdRecfgTimer expires, DL DCH also satisfies the rate decrease
triggered by traffic volume, the uplink and downlinks rate decrease reconfiguration in
one step is performed,.
If before the timer DnUdRecfgTimer expires, DL DCH satisfies the rate increase
triggered by traffic volume, the uplinks rate decrease and downlink s rate increase
reconfiguration in one step is tried, if the admission decision for DL rate increase is failed,
then go on to perform UL rat e decrease reconfiguration..
If before the timer DnUdRecfgTimer expires, UL DCH does not satisfy the rate decease
conditions anymore, stop the UpUdRecfgTimer, and do not reconfigure UL DCH.
If the timer DnUdRecfgTimer expires, only UL rat e decrease reconfiguration is
performed.
DL DCH -> DL DCH(rate decrease)based on traffic volume
If DL DCH satisfies the rate decrease conditions in advance, start the timer
DnUdRecfgTimer
If before the timer DnUdRecfgTimer expires, UL DCH also satisfies the rate decrease
conditions triggered by traffic volume, the uplink and downlinks rate decrease
reconfiguration in one step is performed,
If before the timer DnUdRecfgTimer expires, UL DCH satisfies the rate increase
conditions triggered by traffic volume, the uplinks rate increase and downlink s rate
decrease reconfiguration in one step is tried, if the admission decision for UL rate
increase is failed, then go on to perform DL DCH rate dec rease reconfiguration .
If before the timer DnUdRecfgTimer expires, DL DCH does not satisfy the rate decease
conditions anymore, stop the DnUdRecfgTimer, and do not reconfigure DL DCH.
If the timer DnUdRecfgTimer expires, only DL rat e decrease reconfiguration is
performed.
37
3.1.4
Related Measurement
3.1.4.1
Traffic Measurement
The traffic measurement includes the BO measurements of UTRAN and UE service
buffer capacities, which are respectively measured 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 S DU. If UM mode is
selected, ret ransmission 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 meas urement cont rol
message, whet her report the RLC BO is indicated by RptRlcBufInd, average RLC BO is
indicated by RptRlcAveInd and variance of RLC BO is indicated by RptRlcVarInd..
For services using AM RLC mode to transmit data, the BO value of a RB is the sum of
RLC queue-to-send, 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. In traffic
measurement control message, Periodical Reporting / E vent Trigger Reporting Mode IE
take the value of Rpt Crt.
Relat ed events with traffic measurement include:
E vent 4A: the event is triggered when the traffic measurement value exceeds an
absolute
t hreshold
and
this
condition
lasts
(TrigTime[ MAX_UE_TRV _MEAS_EVENT] ).
for
certain
Delay
period
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
(TrigTime[ MAX_UE_TRV _MEAS_EVENT] ).
lasts
for
Delay
certain
period
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
38
condition lasts for a certain period (TrigTime[ MAX _UE_TRV_MEAS _EVENT]). 4B 0

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 _EVENT] 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 t he

event which has occurred is prevent ed from reoccurring. The following figure s hows 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
Trigger
Time
Pending
Pending
Time Trigger
Time Trigger
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 threshold (such as parameter RptThres[ MAX_UE_TRV_MEAS_EVE NT] )
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. An d 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 bandwidth is decreased.
And vice versa.
39
The
parameters
TrigTime[MA X_UE_TRV_MEAS_EVE NT]
and
PendingTime[MA X
_UE_TRV_MEAS_EVE NT] 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 rec eives 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, the system will
response to the service demand which fluctuates in a ve ry short moment, resulting
in unnecessary bandwidth increase.
The smaller the value of PendingTime[MA X_UE_TRV_MEAS_EVE NT] for 4A event
is, the quicker the control plane receives consecutively the reports and increases
the bandwidt h 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 parameter 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 triggerin g 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 wit h a very low value, the system will
response to the service demand which fluctuates in a very short moment, resultin g
in unnecessary bandwidth decrease.
The smaller the value of P endingTime[MA X_UE _TRV_MEAS _EVENT] of 4B event
is, the quicker the control plane receives consecutively the reports and decreases
the bandwidt h 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 resulting 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
40
consecutive reports of event 4A and the 4A_counter >= 4A_threshold; while the rate
decrease process is triggered when the control plane or UE receives the consecutive
reports of event 4B and the 4B_count er > =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

Reporting event
4A
Increasing Rate
Reporting event
4B
Decreasing Rate
pending-time-aftertrigger
time-to-trigger
Thr_4A
time-to-trigger
Thr_4B
Report
4A
Report
4B
pending-time-aftertrigger
The traffic measurement uses the paramet er MeasEvtNum 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 TxInterCf gPre[ MAX_UE_TRV_MEAS _EVENT] decide whether forbid RACH
data
aft er
measurement
report.,
and
the
forbidden
time
is
decided
by
TxInterruption[ MAX_UE_TRV_MEAS _EVENT].

Measure paramet er acquisition method: when the traffic paramet er 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
DrbcDchUp,
RACH
traffic
DrbcDchUeE vt,
measurement
downlink
DCH
DrbcRachUeEvt,
traffic
and
measurement
FACH
traffic
measurement DrbcFachUp), and then follow the following path to obtain corresponding
traffic measurement parameter based on the configuration number: RNC NE -> RNC
41
Radio Res ourc e Management -> Modify Advanced Parameter -> UE Traffic Volume
Measurement Configuration:
If the uplink channel for service bearer is the DCH, 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 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_EVE NT],
16kbps
uses
the
value
of
32kbps
uses
the
value
of
64kbps
uses
the
value
of
128kbps
uses
the value of
256kbps
uses
the value of
384kbps
uses
the value of
Rpt Thres6[MA X_UE_TRV_MEAS_EVE NT].
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 if 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 rate level adopts the parameters
under this configuration number. Such as, 8kbps uses the value of
16kbps
uses
the
value
of
32kbps
uses
the
value
of
64kbps
uses
the
value
of
128kbps
uses
the value of
256kbps
uses
the value of
384kbps
uses
the value of
Rpt Thres6[MA X_UE_TRV_MEAS_EVE NT].
42
The
values
of
and
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 if the related paramet er which is adopted to meas ure t he traffic is the
corresponding parameter of UE Traffic Volume E vent Measurement Configu ration
Number for RA CH:
The reporting thres holds of event 4A and 4B on the RA CH is determined by

the
parameter
Rpt Thres[MA X_UE_TRV_MEAS_EVE NT]
under
this
configuration number.(Note: there is no relat ed policy for the event 4B

threshold for RA CH.)
The
values
of
and
PendingTime[MA X_UE_TRV_MEAS_EVENT] of event 4A and 4B of RA CH

are the values under corresponding configuration number.
If the downlink channel for servic e bearer is the FA CH, the traffic is measured on
the user plane side, and if 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 Rpt Thres[MA X_UE _TRV_MEAS_EVENT] under this configuration
number. (Note: there is no relat ed policy for the event 4B threshold for FACH.)
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 the channel for service bearer is the uplink DCH, 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 DCH:
The times limitition of periodical report is determined by PrdRptAmount
accorording to UeTrvMCfgNote (0 for DCH)
43
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 paramet er 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)
3.1.4.2
Note:Measurement
parameter to transport channel corresponce by Measob j .
UE internal TxP Measurement

The UE internal measurement mainly measures the UE transmission power (TxP) by
event report,
Before obtaining UE internal measurement parameters, first find the UE Internal
Measurement Configuration Index (UeInt MCfgNo) from UE internal measurement
relationship (UeInt ) configuration items, based on the Cid and the measurement purpose
(PsEvtMeasTP1) ; then find a relevant set of paramet ers from UE internal measurement
relationship (UeInt ) configuration items, based on the UE Internal Measurement
Configuration Index (UeInt MCf gNo).
Note: Each UeInt MCfgNo corresponds to one measurement purpose, indicated with t he
parameter UeInt MCfgNote.
There are two kinds of event, Event 6A and E vent 6B:
E vent 6A:when the UE TxP measurement value is greater than a certain absolute
threshold
and
this
condition
lasts
for
moment
(TrigTime[ MAX_UE_INTE R_MEAS _EVENT] ), the E vent 6A is triggered;

E vent 6B: when the UE TxP measurement value is smaller than a certain absolute
44
threshold
and
this
condition
lasts
for
moment
(TrigTime[ MAX_UE_INTE R_MEAS _EVENT]), the E vent 6B is triggered.

The threshold parameter of E vent 6A and E vent 6B (TxPowerThres )is a delta val ue
relative to min(UE maximum t ransmitted power, uplink DP CH maximum transmission
power).
Here, MA X_UE _INTE R_MEAS_EVE NT is configured by MeasE vtNum .
The higher the value of event 6A 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 other subscribers are not taken int o consideration, the event 6A can be
configured with a high value; the lower the value of event 6A is, the easier the uplink
DCH rate decrease can be triggered by the power, and then the user experience is
affected.
The higher the threshold of event 6B is, the easier the reported power can stay in 6B
status, so as to retrigger the rat e increase by the traffic. However, a certain margin
should be configured bet ween the thresholds of event 6A and event 6B, otherwise, there
may be a situation: aft er the rate is decreased based on event 6A, the rat e increase is
triggered by the traffic demand; the lower the threshold of event 6B is, the harder the
reported power can stay in 6B status, that is, it is harder to trigger the rate increase by
traffic volume, and then the user ex perience is affected.
The correspondence bet ween other parameters that need to be filled in UE internal
measurement control message and OMCR configuration is described as follows:
Measurement report transmission mode
(Meas RptTrMod(UeInt ))
Filter coefficient
(FilterCoeff(UeInt))
Measurement quantity
(MeasQuantity(UeInt ))
Report Criteria
(Rpt Crt(UeInt))
UE Transmitted Power
(Rpt TxP wrInd)
UE internal event identity
(MeaE vtId(UeInt ))
If PS servic es exist, and uplink DRBC DrbcS wch is on ,and UlP wrDasf is on, and all
services use uplink DCH as bearer, the measurement is triggered., after e very uplink rate
45
adjustment, RNC will send measurement control message for UE TxP to UE again.
If the
condition is not met, the UE TxP measurement is switched off.
3.1.4.3
Node B Dedicated TCP Measurement

The Node B dedic ated TCP is related with the UE, it indicates the downlink transmission
power for the UE (the TCP on given carrier, given scramble, and given channelization
code) is measured by the Node B. It acts as a factor for triggering bandwidth dec reas e as
well as a restriction for bandwidth increase. The Node B dedicated TCP measurement
which is used to trigger DRB C rate adjustment is reported periodically, the period is
configured by RptPrd, because of the periodical report, the Event A/B is decided by RNC.
Two sets of measurement parameters are configured:
E vent A: when the NodeB D-TCP measurement value is greater than a specific
absolute threshold (EvtAbTcpThrd[3] when Nb DMCfgNot e is 2), event A is triggered.
E vent A is used to trigger the downlink rate dec rease. 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 (EvtAbTcpThrd[3] when NbDMCfgNote is 3), 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 rate increase can be triggered
by traffic.
Here, EvtAbTcpThrd[3] is a delta value relative to DP CH downlink maximum
transmission power which is related with service type. And EvtAbTcpThrds value of
different DCH rate level can be configured differently based on the paramet er
DlRateLevel[2], the detailed description as the following:
Rate Level
The first rate
level
The
second
rate level
The corresponding rate range of PS
The corresponding
servi ces
thre shold of Event A/B
R<= DlRateLevel[0]
EvtAbTcpThrd[0]
DlRateLevel[0]<R<= DlRateLevel[1]
EvtAbTcpThrd[1]
46
The third rate

level
R>DlRateLevel[1]
EvtAbTcpThrd[2]
Here, R is the current DRBC rate level of PS service.

The higher the value of event A is, the harder the downlink DCH rate decrease 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 configured with a high value;
the lower the value of event A is, the easier the downlink DCH rat e decrease can be
triggered by the power, and then the user experience 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 bet ween the thresholds of event A and
event B, otherwise, there may be a situation: after the rate is decreased based on event
A, the rate 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 tri gger the
rate increase by traffic. Thus, the user experience is affected.
If PS services exist, and downlink DRBC DrbcS wch is on, and DlP wrDasf is on, and no
less than one PS service uses downlink DCH as bearer , , the measurement is triggered.
If the condition is not met, the Node B dedicat ed TCP measurement is switched off .
3.2
Dynamic Channel Type Transfer for HSDPA Service
3.2.1

The signaling channel allocation process upon the RRC connection setup is the same as
the R99 policy.
For the setup of RAB allocation servic e, 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 services are on the DL HS-DSCH/UL DCH: if both the UE and the cell
47
and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd are 1 ),
then the signaling is on the DL HS -DS CH/ UL DCH; otherwis e, the signaling is
mapped to DCH/DCH low rate signaling.
3.2.2
3.2.2.1

the service features (RAB parameters). For the HS-DS CH in the HSUPA cells, the
selectable channel types as follows:
Conversation servic es use DL DCH/ UL DCH channels.
Streaming services can use DL HS-DSCH/UL DCH and DL DCH/UL DCH channels.
Interactive and background servic es can use DL HS -DS CH/ UL DCH, DL DCH/UL
DCH, and DL FACH/UL RACH channels.
Channel allocation of the HSDPA UE in the R99 is the same as that for R99 initial
service.
3.
For the UE supporting HS-DSCH in the HSDPA cell:
The principles for CS 64k service is the same as R99, see 3.1.2.4 The Access
Strategy of CS 64k Service.
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-DSCH/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.
48
The E vent 1F is defined as that the measurement value Ec/No is smaller than an
absolute threshold. See 3.2.4.1Pilot Channel Quality Measurement for the detailed
definition.
The principles for selecting the channel type for interactive and background services
are as follows:
If dlMaxBR >= Rfach or ulMaxBR >= Rrach, select the CELL_DCH.
Otherwise, select the DL FACH/ UL RACH with priority. If the DL FACH/UL RA CH 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-DSCH/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 -DSCH
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.
3.2.2.2

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
Service Types
Channel Type
If any of I/B services meet the condition of [dlMaxB R >= Rfach or
I/B+I/B
ulMaxBR >= Rrach] and the channel quality is non-1F event, select
the DL HS-DSCH/UL DCH with priority. If selecting the DL
HS-DSCH/UL DCH is failed (for example, downlink HS-DSCH is
49
failed to admit), select the DL DCH/UL DCH.

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-DS CH/UL DCH. If selecting DL HS-DSCH/UL DCH is failed
(for example, downlink HS -DS CH 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 -DS CH for CS services] and channel quality is non-1F
I/B+CS
or
S+CS
or
I/B+S+CS
event, select the DL HS-DS CH/ UL DCH with priority for PS (I/B or
S) services. If selecting the DL HS-DS CH/ UL DCH is failed (for
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-DSCH 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
I/B+S or S+S
the DL HS-DSCH/UL DCH with priority. If selecting the DL

(S/I/B) service on the UL DCH is the same as that for R99. The rate of the DL HS -DSCH
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.
3.2.3
Channel Switching
During the session, the dynamic channel switching in the HSDPA 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.
50
Figure 3-4
HSDPA Channel Switching

Reconfig SF
Based
2. DL D-TCP Based
3. UL TxP Based
4. Cells RTWP
5. Cells TCP
Transition DL DCH -> DL HS-DSCH

1. DL Traffic Volume Based
2. Channel Quality Measure Based
(Option)
3. UE &Cell Capability
Transition DL HS-DSCH -> DL DCH
1. Channel Quality Measure Based
(Option)
Transition of HS-DSCH/DCH -> FACH/RACH

CELL_DCH
RACH/FAC
H
HS-DSCH/DCH
DCH/DCH
CELL_FACH

Transition of FACH/RACH -> HS-DSCH/DCH

2. Support PCH

2. Support PCH
Transition of HS-DSCH/DCH -> PCH

2. Support PCH
PCH
Idle
URA_PCH
Transition of DCH/DCH -> IDLE

1. DL&UL Traffic Volume Based
3.2.3.1


1. UL&DL Traffic volume Based
Transition of HS-DSCH/DCH -> IDLE

CELL_DCH(DL HS-DSCH/UL DCH) <-> CELL_FACH

1.
CELL_DCH <-> CELL_FA CH switching triggered by traffic

i.
CELL_DCH (DL HS-DSCH/UL DCH) -> CE LL_FA CH
When the UE is in the CE LL_DCH status, the switching from CELL_DCH (DL
HS-DSCH/UL DCH) to CELL_FACH can be triggered by the traffic measurement
report (E vent 4B ) from the user plane and UE.
The switching from CELL_DCH (DL HS-DSCH/UL DCH) to CELL_FACH is
triggered in the case of the following conditions:

(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. (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 corresponding counter is clear. )
51
When the current uplink rate is smaller than the maximum uplink rate threshold
Rrac h for RACH (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 concurrent services exist, it is required that all the services should m eet the
If the condition for CELL_FACH switching is met, but the CELL_FA CH fails the
admission, and the current uplink rat e is great er than the minimum rate that UL
DCH can bear, namely, the lowest rate level configured by UlRateAdjLev
[MAX_NUM_RATE_ADJ UST], UL DCH rate decrease is selected.
ii.
CELL_FA CH -> CELL_DCH (DL HS-DSCH/UL DCH)
When the UE is in the CELL_FA CH status, the switching from CE LL_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_FACH to CELL_DCH (DL HS-DSCH/UL DCH) is
The system receives consecutive FachE4aThd traffic measurement reports

(E vent 4A) from the user plane or UE. (Note: if the system receives a traffic
measurement report (E vent 4B) from the user plane or UE when the receiving
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 Control
Feature Guide for the overload threshold)
The rate of UL DCH in the CELL_DCH (DL HS -DS CH/UL DCH) switching is
the[UL Initial rate] for DRB C, see 3.1.2.2 .
2.
CELL_DCH to CELL_FA CH switching triggered by load
the cell load.
52
The switching from CE LL_DCH (DL HS -DS CH/UL DCH) to CELL_FACH (DL FACH/UL
RACH) is triggered in the case of the following conditions:
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 service triggers the switching
from DL DCH to DL HS-DSCH, the DL DCH of all services is switched to DL
HS-DSCH.
53
If t here is CS service in the concurrent services and the UE is capable of the DL

DCH and DL HS -DS CH c oncurrency (maximum rate on the DP CH is reported by
the UE), the DL DCH of only PS services is switched to DL HS -DS CH; otherwise,
the switching is not implemented.
If the service is on the DCH, the event 4A triggered by the user plane meets the condition
for rate inc rease in the DL DCH -> DL HS-DSCH switching, but the DL HS -DS CH fails
the admission or the DL HS-DSCH is not supported, select DL DCH rate inc rease, 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 increase)).
2.
Switching from HS-DSCH to DCH triggered by channel quality
When a subscriber is using the DL HS-DS CH/ UL DCH, the DL HS-DSCH switching 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 t he 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-DSCH to DL DCH is triggered in the case of the following
conditions:
Channel quality measurement switches for the current PS service (IB ChQS wch,
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 switching: if the concurrent services
are PS services, the DL HS-DSCH for all the services are switched to DL DCH.
During the fallback from DL HS-DSCH to DL DCH, the rate is the DCH initial rate, see
3.1.2.5
54
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 target cell does not support the HS -DS CH, the
downlink channel will switch from HS-DSCH to DCH. The rate is the DCH initial rate , see
3.1.2.5
During the PS services carried on DL DCH/ UL DCH, the UE may roam from a R99 cell to
HSDPA cell by hard handover for mobility. If the target cell and UE support the HSDPA,
the switching from DL DCH to DL HS-DSCH occurs along with the handover.
3.2.3.3
CELL_DCH (DL HS-DSCH/UL DCH) -> URA_PCH

When the UE uses the CE LL_DCH (DL HS -DS CH/ UL DCH) for service bearer, the
switching from CE LL_DCH (DL HS -DS CH/UL DCH) t o URA_P CH can be triggered by
the traffic measurement report (E vent 4B0) from the user plane or UE.
The switching from CE LL_DCH (DL HS-DS CH/ UL DCH) to URA_P CH is triggered in the
case of the following conditions:
The system switch PchSwch for URA _PCH switching is on.
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
55
3.2.3.4
CELL_DCH(DL HS-DSCH/UL DCH) -> IDLE

When the UE uses the CE LL_DCH (DL HS -DS CH/ UL DCH) for service bearer, the
switching from CELL_DCH (DL HS -DS CH/ UL 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 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 cou nter is
cleared.)
When the channel is changed to IDLE, the occupied radio resources are released and
3.2.4
Related Measurement
3.2.4.1
Pilot Channel Quality Measurement

The channel quality measurement is for the switching from HS -DS CH to DCH. The E vent
1E and E vent 1F are us ed in the measurement.
The channel quality measurement CQ is performed on the P -CPICH. If the UE supports
HS-DSCH, the measurement is initiated.
1E definition: when the pilot signaling quality is great er than an absolute threshold
(ThreshUsedFreq[MAX _INTRA_MEAS_EVE NT]) and t his 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 absolut e threshold
(ThreshUsedFreq[MAX _INTRA_MEAS_EVE NT]) and t his condition lasts for a moment
(TrigTime[ MAX_INTRA_MEAS _EVENT]), event 1F is triggered.
56
For more details of the parameter ThreshUsedFreq[MA X_INTRA _MEAS_EVENT] and

TrigTime[MA X_INTRA_MEAS_EVE NT], see ZTE UMTS Handover Control Feature
Guide.
The figure below shows the rationale of E vent 1E:
Figure 3-5
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-6
E vent 1F in Channel Quality Measurement
Measureme
nt
Quantity
P CPICH 1
P CPICH 2
Absolute
threshold
Trigger
Time
P CPICH 3
Report 1F
57
3.2.4.2
Traffic Measurement
The traffic volume measurement quantity on HS-DSCH is the average RLC buffer
payload, which is 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 paramet er acquisition method: For a service on the DL HS -DS CH/UL DCH, see
traffic measurement on the R99 for ac quisition of traffic paramet ers on t he UL DCH.
Acquisition of traffic parameters on the DL HS-DS CH: 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 purpose (downlink HS-DSCH traffic meas urement 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 measurement 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-DSCH, traffic volume measurement
is performed on the user plane and related paramet ers used in the t raffic volume
measurements
are parameters
corresponding to the
UP
Traffic
Volume
Measurement Configuration Number for Stre aming Class on HS-DS CH and UP

Traffic Volume Measurement Configuration Number for Interactive and Background
Class on HS -DS CH.
In HS-DSCH, the reporting t hres holds for events 4A and 4B for I/B and S
services
are
determined
by
the
parameter
RptThres[ MAX_UE_TRV _MEAS_EVENT] under this configuration number.
TrigTime
[MAX_UE_TRV _MEAS_EVENT]
and
PendingTime
[MAX_UE_TRV_MEAS_EVENT] 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.
58
3.3
Dynamic Channel Type Transfer for HSUPA Service
3.3.1

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 UE and the cell
and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd are
1 ),then t he 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-DSCH/UL E-DCH:
a)If Liscence FourEChAllowed is supported, switch on SrbOnE dchS wch,
if both the UE and the cell support F-DPCH, bot h CresPara7 and RncFdpchSupInd are
1,(or both the UE and the cell support E-FDPCH, both RncE fdpc hSupInd and
EfdpchSupInd are 1 ),signaling bear on HS -DS CH/E-DCH.

Otherwise signaling bear on DCH/E-DCH
b)If Liscenc e FourEChAllowed isnt supported, switch off SrbOnEdchS wc h, signaling bear
on DCH/ DCH
3.3.2
3.3.2.1

59
the service features (RAB parameters ). For the HS UPA UE in the HS UPA cells, 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-DSCH/UL E-DCH, DL
HS-DSCH/UL DCH, DL DCH/ UL DCH, and DL FA CH/ UL RACH.
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 see 3.1.2.4 The Access
Strategy of CS 64k Service.
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 with priority. If selecting the DL HS-DS CH/ 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-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 interactive and background services
are as follows:
If dlMaxBR >= Rfach or ulMaxBR >= Rrach, select the CELL_DCH.

Otherwise, select the DL FACH/ UL RACH with priority. If the DL FACH/UL RA CH 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
60
failed to admit ), select the DL HS-DSCH/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.
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-DSCH need be bound for use in service channel
allocation, that is, there is no combination of DL DCH/ UL E-DCH.
3.3.2.2

call service. All concurrent PS services use the same channel as bearer.
Channel allocation for the UE supporting HSUPA in the HS UPA is as follows:
Concurrent
Service Types
Channel type
If any of I/B services meets the condition of lMaxBR >= Rfach or
ulMaxBR >= Rrach, and channel quality is a non event 1F, 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
to admit), select the DL HS-DSCH/UL DCH. If selecting the DL
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 ex ample, the uplink E-DCH is failed to admit), select the
DL HS-DSCH/UL DCH. If selecting the DL HS-DS CH/UL DCH is
failed (for example, the downlink HS-DSCH is failed to admit),
61
select the DL DCH/UL DCH.

CS services select the DL DCH/UL DCH.
If the UE meets the uplink concurrent capabilities of the DPCH and
E-DCH, downlink concurrent capabilities of the DPCH and
HS-DSCH for CS services and channel quality is a non event 1F,
select the DL HS-DS CH/ 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 t o admit ), select the DL
HS-DSCH/UL DCH. If selecting the DL HS -DS CH/ UL DCH is failed
(for example, downlink HS-DS CH 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 DPCH

and HS -DS CH for CS services but does not meet uplink concurrent
capabilities of the DP CH and E-DCH for CS services 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-DSCH/UL
DCH is failed (for 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 t he
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-DS CH/UL E-DCH is failed (for
I/B+S or S+S
example, uplink E-DCH is failed t o admit ), select the DL

HS-DSCH/UL DCH. If selecting the DL HS -DS CH/ UL DCH is failed
(for example, downlink HS-DS CH 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 allocation of the HS UPA UE in the HS DPA is the same as that for HS DPA
concurrent service.
62
3.3.2.3
Configuration Principle of E-TTI

Configuration Principle of E-TTI:
1
When UE or any one cell of the active set only supports 10ms TTI, or the
Tti2msSuptInd of any one cell of the active set is off, then 10ms TTI is used.
Only when UE and all the cells of the active set support 2ms TTI, and the
Tti2msSuptInd of all the cells of the active set is on, then 2ms TTI can be allowed to
be used, the detail is in the following :

3
If EttiTraffVolSwch is on, and there is no CS traffic, and at least one traffic is

configured 2ms TTI, and if 10ms TTI can satisfy GBR require, 10ms TTI is used, and
the throughput measurement is switched on; Otherwise, if 10ms TTI cant satisfy
GBR require, 2ms TTI
is used, and the throughput meas urement isnt switched on.
For other scenes, if t here is no less than one traffic configured 2ms TTI, 2ms T TI is
used, otherwise, 10ms TTI is used, and t he throughput measurement isnt switched
on.
3.3.3
Channel Switching
During the session, the dynamic channel switching in the HSUPA 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.
63
Figure 3-7
HSUPA Channel Switching
Transition DCH/DCH -> HS-DSCH/E-DCH

2. Channel Quality Measure Based (Option)
4. Compressed Mode is not started

Reconfig SF
Based
2. DL D-TCP Based
3. UL TxP Based
4. Cells RTWP
5. Cells TCP
Transition DCH/DCH -> HS-DSCH/DCH

Transition HS-DSCH/E-DCH -> DCH/DCH
Transition of HS-DSCH/DCH -> FACH/RACH

Transition of HS-DSCH/E-DCH -> FACH/RACH
Transition HS-DSCH/DCH -> DCH/DCH

CELL_DCH
Transition HS-DSCH/DCH -> HS-DSCH/E-DCH
1. UL Traffic Volume Based
3. If HSUPA associate compressed mode
method is set to Serial, the compressed mode
HS-DSCH /E-DCH
is not started
or
HS-DSCH/DCH
RACH/FAC
H
DCH/DCH
CELL_FACH
Transition of HS-DSCH/E-DCH -> PCH

2. Support PCH
PCH
URA_PCH
Transition of FACH/RACH -> HS-DSCH/DCH

2. UE &Cell capability
Transition of FACH/RACH -> HS-DSCH/E-DCH
2. UE &Cell capability

1. UL&DL Traffic Volume based
2. Support PCH
Transition of HS-DSCH/DCH -> PCH
1. UL&DL Traffic Volume based
2. Support PCH

Idle
Transition of DCH/DCH ->IDLE
Transition of HS-DSCH/DCH -> IDLE
1. DL&UL Traffic Volume
Based
3.3.3.1

2. Support PCH

Transition of HS-DSCH/E-DCH -> IDLE

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_FACH
When the UE is in the CE LL_DCH status, the switching from CELL_DCH (DL
HS-DSCH/UL E-DCH) to CE LL_FA CH can be triggered by the traffic measurement
report (E vent 4B ) by the user plane.
The switching CE LL_DCH (DL HS-DSCH/UL E-DCH) to CELL_FACH is triggered in

(E vent 4B) on the HS-DSCH from the user plane as well as consecutive
ToFtimesThr t raffic measurement reports (E vent 4B) on the E-DCH 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 smaller than the
64

ii.
CELL_FA CH -> CELL_DCH(DL HS-DS CH/ UL E-DCH)
When the UE is in the CELL_FA CH status, the switching from CE LL_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 to CELL_DCH (DL HS -DS CH/ UL E-DCH) is
The system receives consecutive FachE4aThd traffic measurement reports

(E vent 4A) from the user plane or UE. (Note: if the system receives a traffic
measurement report (E vent 4B) from the user plane or UE when the receiving
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 Control
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_FACH (DL FA CH/UL RA CH)
is triggered in the case of the following conditions:
The cell downlink load exceeds the overload threshold. (Note: see the ZTE UMTS
Overload Control Feature Guide for the overload threshold.)
65
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-DSCH/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 counter 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 s witching are processed by the follo wing
principl es:
If all the c oncurrent services are PS services and one service trigg ers the switching from
DL DCH/UL DCH to DL HS -DS CH/UL E -DCH, the DL DCH/UL DCH of all services
66
is switched to DL HS-DSCH/UL E-DCH.

If there is conversation service in the concurrent servic es and the UE is capable of
the DL DCH/ UL DCH and DL HS-DS CH/ UL E-DCH concurrency, the DL DCH/UL
DCH of only PS services is switched to DL HS-DS CH/ UL E-DCH; otherwise, the
switching is not implemented.
Note:
When the downlink DPCH and HS -PDS CH coexist, the maximum rat e on the DPCH is
reported by the UE. When the uplink DPCH and E-DPDCH coexist, the maximum rate on
the DPCH is 64 kbit/s.
If the service is on t he 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 cas e of UL DCH rate increase, the ot her conditions of R99 UL DCH
rate increase must be satisfied (see UL DCH -> UL DCH) rate inc reas e)).
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-DSCH switching, but the DL HS-DS CH fails to
admit or the DL HS -DS CH is not supported, select DL DCH rate increase, 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 R99 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-DSCH switching, the DL HS-DSCH admits successfully, but
the UL E-DCH fails to admit or the E-DCH is not supported, the downlink will be switched
to the HS-DSCH 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 -DSCH
will worsen the QoS and lower the system capacity when the bit rate requirements of
67
streaming services carried on HS -DS CH are not satisfied and the channel quality
deteriorates.
definition.
The switching from DL HS-DSCH/UL E-DCH to DL DCH/ UL DCH is triggered in the case
Channel quality measurement switches for the current PS service (IB ChQS wch,
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 switching: switch all services on the
DL HS-DSCH/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 DCH
initial rate, see 3.1.2. 5
3.
Switching from DL HS-DS CH/ UL E-DCH to DL DCH/UL DCH triggered by mobility
During the PS services carried on DL HS-DS CH/ UL E-DCH, when the HS UPA UE hands
over from an HSUPA c ell 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 DCH initial rate, see 3.1.2.5
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 DCH initial rate, see 3.1.2.5
For more details of mobility, see ZTE UMTS handover Control Feature Guide.
68
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-DSCH/UL DCH, the UE c an be switche d from the DL

HS-DSCH/UL DCH to the DL HS -DS CH/ 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 t he DCH when the receiving times are smaller than the
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-DS CH/ UL DCH, the UE triggers event 4A and meets
conditions for DL HS -DS CH/UL DCH -> DL HS -DS CH/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 increas e, the ot her conditions of R99 UL DCH rate increase
must be satisfied (see UL DCH -> UL DCH (rat e increase)).
The way to determine the target rate 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-DSCH/UL E-DCH cannot switch to DL HS-DSCH/ UL DCH based on traffic
volume measurement.
2.
DL HS-DSCH/UL E-DCH <-> DL HS-DSCH/UL DCH switching triggered by mobility
69
over from an HS UPA cell to HSDPA cell for mobility and the tar get 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 DCH initial rate, see 3.1.2.5
During the PS services carried on DL HS -DS CH/ UL DCH, when the HS UPA UE hands
over from an HS DPA 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.
For more details of mobility, see ZTE UMTS handover Control Feature Guide.
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 service bearer, the
switching from CELL_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 switching from CELL_DCH (DL HS -DS CH/ UL E-DCH) to URA_P CH is triggered in
The system switch PchSwch for URA _PCH switching is open.
measurement value of 0 on the HS-DSCH and E-DCH from the user plane (Not e: 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)
If the concurrent services exist, it is required that all the services should me et the
70
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 service 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 channel 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 t rigger E -DCH (2ms E-TTI) t rans fer to
E-DCH(_10ms E-TTI)
The switch EttiTraffVolSwch is on.
The system receives consecutive ETtiEbThd throughput meas urement reports
(E vent 4B) from the user plane, E-TTI s witches to 10ms. (Not e: if the system
receives a throughput measurement report (E vent 4A) from the user plane, the
2
E-DCH( 10ms E-TTI) -> E-DCH(2ms E-TTI)
71
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) t rans fer to
E-DCH(2ms E-TTI)
The switch EttiTraffVolSwch is on.
The system receives consecutive ETtiEaThd throughput meas urement reports
(E vent 4A) from the user plane, E-TTI switches to 2ms. (Note: if the system receives
a throughput measurement report (E vent
4B) from the user plane, the

License Tti2msSuptInd is support
If UE and all the cells of the active set support 2ms TTI.
The throughput measurement mentioned above is illustrated in 3.3.4.2 Throughput
measurement for PS service TTI trans fer.
3.3.4
Related Measurement
3.3.4.1
Traffic Measurement
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. Slide the window
for 20 ms, and then calculate its data volume for 100 ms again.
Measure parameter acquisition method: For a service on the DL HS -DS CH/ 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 traffic parameters
are acquired, get the corresponding 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 corresponding traffic
volume
measurement in RNC NE -> RNC Radio Res ourc e Management -> Modify Advanc ed
72
Parameter -> UE Traffic Volume Measurement Configuration:

If the uplink channel for the service is the E-DCH, traffic volume meas urement is
made on the user plane and related parameters used in the traffic volume
measurements are parameters corres ponding 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
parameter
RptThres[ MAX_UE_TRV _MEAS_EVENT] under this configuration number.
TrigTime
[MAX_UE_TRV _MEAS_EVENT]
and
PendingTime
[MAX_UE_TRV_MEAS_EVENT] 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 is used for the switching bet ween
2ms E-TTI and 10ms E-TTI. Throughput measurment is independent of traffic
measurement.
There is a switch EttiTraffVolSwch(S witch of E-TTI Switching Triggered by User Plane
Throughput Measurement) to control this feat ure. As EttiTraffVolSwch on,for a service on
the DL HS-DS CH/UL E-DCH, acquisition of traffic parameters on the UL E-DCH for E-TTI
switching: 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 Res ourc e Management -> Modify Advanc ed
Parameter
->
UE
Traffic
Volume
Measurement
Configuration:
ThoughThres
[MAX_UE_TRV_MEAS_EVENT] defines the rat e thres holds of 10ms to 2ms and 2ms to
10ms respectively. TrigTime 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.
73
The stop and start of throughput measurement

As EttiTraffVolSwch is set to be on,
UE uses E-DCH as bearer, and supports 2ms TTI
All the cells of active set support 2ms TTI.
No C class traffic on E-DCH,
At least one traffic is configured 2ms TTI.
If 10ms TTI could satisfy GBR require, Open the t hroughput 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 t hroughput.
3.4
Dual-Carrier related Dynamic Channel Adjustment
3.4.1

The initial service channel allocation for dual- carrier is in the following:
When the downlink channel allocation result is HS-DS CH,
and bot h the UE and
the cell support dual -carrier, then the dual -carrier should be allocated to the UE.
Dual-carrier capability of the neighbouring cell from DRNC and its secondary carrier
information can be obtained from the parameters IurDcHsdsSuptInd and SndSvrCelI D
in the adjacent cell list in SRNC; Dual-carrier capability of adjacent cell and
secondary carrier information over Iur interface can also be acquired from the
related IE on Iur interface.
3.4.2

The concurrent service channel allocation for dual- carrier is similar to the initial service
channel allocation in 3.4. 1.1, that is, as long as the downlink channel allocation res ult is
HS-DSCH, and both the UE and the cell support dual-carrier, then the dual-c arrier should
be allocat ed to the UE.
74
For CS+PS, if CS service is established on DCH, and PS servic e is established on

dual-carrier, then CS service us es the primary carrier as bearer.
3.4.3
Channel Switching
If it is from other channel switching to HS-DS CH, and if both the UE and the cell support
dual-carrier, then the dual -carrier should be allocated to the UE.
And the HS-DSCH serving cell change may also trigger the channel switching bet ween
dual-carrier HS-DSCH and single-carrier HS-DS CH:
If t he HS-DSCH target cell supports dual-carrier, and it also satisfies the condition
for using the dual -carrier,then the dual-carrier will be allocated.
If t he HS-DS CH target cell does not support dual-carrier, then the single-c arrier will
be allocat ed.
3.5
Enhanced FACH Dynamic Channel Adjustment
3.5.1
DL Enhanced FACH Dynamic Channel Adjustment
3.5.1.1

During RRC signaling bearer selection, if RRC signaling selects CELL_FACH bearer,
and, If system SIB5 broadcasts HS-DSCH common system information, UE capability IE
HS-P DSCH in CE LL_FA CH in RRC connection request is true. That is, both cell and
UE support downlink enhanced FACH. In this case, DL HS-DSCH/UL RA CH channel
bearer is selected. Otherwise, select DL FACH/UL RA CH channel bearer.
3.5.1.2

Introducing DL enhanced FACH imposes no impacts to select CELL_DCH or
CELL_FA CH for services initial channel. If the initial channel selection is borne in
CELL_FA CH, and, If both cell and UE support DL Enhanced FA CH, DL HS -DSCH/UL
RACH is selected; otherwise, select DL FACH/UL RA CH channel bearer .
75
3.5.1.3
Channel Switching
The switching policy of DL enhanced FACH channel is shown below.
The switching policy of CELL_DCH and URA_P CH switching to CELL_FACH
(HS-DS CH/ RACH) is the same as that of CELL_DCH and URA_P CH to
CELL_FA CH (FACH/RA CH). That is, if the switching condition to CELL_FACH is
satisfied and both cell and UE support DL Enhanced FA CH, DL uses HS -DS CH to
replace FACH.
The switching policy of CELL_FA CH(HS-DSCH/RA CH) to CELL_DCH is the same
as that of CE LL_FACH(FACH/RA CH) to CELL_DCH.
The switching policy of CELL_FA CH(HS-DSCH/RA CH) DL non-E nhanced UE DR X
bearer to PCH and IDLE is the same as that of FACH/ RACH, keeping unchanged. If
DL uses Enhanced UE DRX, it resides on CELL_FA CH for longer time because
Enhanced UE DRX features power saving. Those CE LL_FA CH adopting Enhanced
UE DRX and not adopting Enhanced UE DRX should be differentiated to switch to
PCH or Idle.
1.
Traffic triggered CELL_FACH(DL HS-DS CH/ UL RACH) -> URA _PCH
Satisfying all conditions below to trigger CELL_FACH (HS -DS CH/ RACH) switching to
URA _PCH:
The switch PchSwch for system switching to URA_P CH is turned on.
For scenarios not using Enhanced UE DRX:
The system receives cons ecutive FToPchThd traffic measurement reports with
measurement value of 0 by user plane and UE (Not e: if the system receives a report with
measurement value of non-zero value when the receiving times are smaller than the
For scenarios using Enhanced UE DRX:
The system continuously receives user plane traffic measurement value 0 for
DxHsBo0E 4bThd times, UE traffic measurement value 0 for FToPchThd times; (Note: if
the system receives a report with measurement value of non-z ero value when t he
76
receiving times are smaller than the threshold, the corresponding counter is cleared)
2.

3.
Traffic triggered CELL_FACH(DL HS-DS CH/ UL RACH) -> IDLE
Satisfying all conditions below to trigger CELL_FACH (HS -DS CH/ RACH) switching to
IDLE:
The switch PchSwch for system switching to URA_P CH is turned off.
measurement value of 0 by user plane and UE (Not e: if the system receives a report with
measurement value of non-zero value when the receiving times are smaller than the
The system continuously receives user plane traffic measurement value 0 for
DxHsBo0E 4bThd times, and UE traffic measurement value 0 for FToIdleThd times. (Note:
Note: if the system receives a report with measurement value of non-zero value when
the receiving times are smaller than the threshold, the corres ponding counter is cleared)
4.
Mobility triggered CELL_FA CH intra -mode channel switching
Due t o the mobility, during UE adopts CELL_FA CH channel to bear I/B PS services, if
Enhanced FACH supports inter-cell moving at different capabilities, the target cell and
UEs support ability in DL Enhanced FACH should be complied with to re-allocate
channels:
If bot h target cell and UE support DL E nhanced FA CH, DLHS-DSCH/UL RACH channel
bearer is selected; otherwise, DL FACH/UL RACH is selected.
77
3.5.2
UL Enhanced FACH Dynamic Channel Adjustment
3.5.2.1

During RRC signaling bearer selection, if CE LL_FACH bearer is selected:
If system SIB5 broadcasts Common E-DCH system information, UE capability IE
Support of common E-DCH in RRC connection request is true. That is, both cell
and UE support uplink enhanced FACH. In this case, DL HS -DSCH/UL E-DCH
channel bearer is selected.
If both cell and UE support downlink enhanc ed FA CH, while not supporting uplink
enhanced FACH, DL HS -DS CH/ UL RACH channel bearer is selected.
Otherwise, DL FA CH/ UL RACH channel bearer is selected.
3.5.2.2

Introducing UL enhanced FACH imposes no impacts to select CELL_DCH or
CELL_FA CH for services initial channel. If the initial channel selection is borne in
CELL_FA CH, and,
If both cell and UE support common E-DCH, select DL HS-DSCH/UL E-DCH
channel bearer.
If both cell and UE support DL E-FACH, while not supporting Common E-DCH,
select DL HS-DS CH/UL RA CH channel bearer.
Otherwise, select DL FACH/UL RA CH channel bearer.
3.5.2.3
Channel Switching
The switching policy of UL enhanced FACH channel is shown below.
The switching policy of CELL_DCH and URA_P CH switching to CELL_FACH
(HS-DS CH/E-DCH) is the same as that of CELL_DCH and URA_P CH to
CELL_FA CH (FACH/RA CH). That is, if the switching condition to CELL_FACH is
satisfied and both cell and UE support common E-DCH, UL uses E-DCH to replace
78
RACH.
The switching policy of CELL_FA CH(HS-DSCH/E-DCH) to CELL_DCH is the same
as that of CE LL_FACH(FACH/RA CH) to CELL_DCH.
The switching policy of CELL_FA CH(HS-DSCH/ E-DCH) non-E nhanced UE DR X
bearer switching to P CH and IDLE is the same as that of FACH/RA CH to P CH and
IDLE, keeping unchanged. If DL uses Enhanced UE DRX, it resides on
CELL_FA CH for longer time because Enhanc ed UE DRX features power saving.
Those CELL_FA CH adopting E nhanced UE DRX and not adopting E nhanced UE
DRX should be differentiated to switch to PCH or Idle.
1.
Traffic triggered CELL_FACH(DL HS-DS CH/ UL E-DCH) -> URA_P CH
Satisfying all conditions below to trigger CELL_FA CH (HS-DSCH/E-DCH) switching to

URA _PCH:
The switch PchSwch for system switching to URA_P CH is turned o n.
The system receives cons ecutive FToPchThd traffic measurement reports with
measurement value of 0 by user plane of HS-DSCH and E-DCH channels in
CELL_FA CH (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 count er
is cleared)
The system receives consecutive DxHsBo0E 4bThd traffic measurement reports with
is cleared)
2.
Traffic triggered CELL_FACH(DL HS-DS CH/ UL E-DCH) -> IDLE
79
Satisfying all conditions below to trigger CELL_FA CH (HS-DSCH/E-DCH) switching to

IDLE:
The switch PchSwch for system switching to URA_P CH is turned off.
CELL_FA CH(Note: if the system receives a report with measurement value of non-zero
is cleared)
The system receives consecutive DxHsBo0E 4bThd traffic measurement reports with
is cleared)
3.
Mobility triggered CELL_FA CH intra -mode channel switching
Due t o the mobility, during UE adopts CELL_FA CH channel to bear I/B PS services, if
Enhanced FACH supports inter-cell moving at different capabilities, the target cell and
UEs support ability in Enhanced FACH should be complied with to re-allocate channels:
If both target cell and UE support Common E-DCH, DLHS -DS CH/UL E-DCH channel
bearer is selected; otherwise, if both target cell and UE support DL Enhanced FA CH,
while not supporting Common E-DCH, then select DL HS-DSCH/UL RA CH channel
bearer; otherwise, select DL FACH/UL RA CH channel bearer.
3.5.3
Traffic Measurement
The traffic measurement on CELL_FA CH (HS-DSCH/E-DCH) is the same as that of
80
CELL_DCH (HS -DS CH/E-DCH). For details, please refer to 3.2. 4.2 and 3.3.4.1.
How to get measurement parameters: first to get the configuration No. UeTrvMCfgNo
from cells UE traffic measurement configuration relationship according to Cid and
measurement target (CELL_FA CH DL HS-DS CH traffic measurement DrbcCFachHsUp,
CELL_FA CH UL E-DCH t raffic measurement DrbcCFachE DchUp); then to obtain t he
corresponding traffic measurement parameters in RNC NE-> RNC Radio Resource
Management->Modify
Advanced
Parameter-> UE
Traffic
Volume
Measurement
Configuration according to the configuration No.
3.6
Fast Dormancy
3.6.1
R8 Fast Dormancy
3GPP Release 8 introduces a simple UE signaling to indicate the state of UE for the
network. A new UE "Signaling Connection Release Indication Cause" indicat es that the
UE has decided to stop an activated PS data transmission. On receiving the IE, UTRA N
can decide to trigger an RRC state handover to URA_P CH or IDLE to save battery
consumption. The net work can control the using of this function by configuring and
sending a timer in SIB1 which regulates that this function is forbidden within a period of
T323.There is a paramet er T323S wch to control whether configure T323 in S IB1.
Without receive T323, UE would not sending SCRI with cause UE requested PS data
session end.
Note:
1.
The UE shall be inhibited from sending t he SCRI message with t he IE "Signalling

Connection Release Indication Cause" set to "UE Requested PS Data session end"
whilst timer T323 is running.
2.
According to 3GPP 25.331, when timer T323 expires, if it still meets the condition for
reporting SCRI message, the UE will trigger the transmission of a S CRI message
again. But some tests confirm that some UEs will not report SCRI message again
when timer T323 expires.
81
3.6.1.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 indicationwhich include
IEsignaling connection release indication causehas value ofUE requested PS
data session end
If conditions above are satisfied, trigger channel switch to URA_PCH.
3.6.1.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 indicationwhich include
IEsignaling connection release indication causehas value ofUE requested PS
data session end
If conditions above are satisfied, trigger channel switch to IDLE, and releas e the
occupied radio resource.
3.6.2
Pre-R7 Fast Dormancy Suppressing

In order to save the battery consumption, for some smart phones whos e versions are
3GPP Releas e 7 or before Release 7, once the data transmission is end, they will send
the message Signalling Connection Release Indication (S CRI ), and make the RA N
release the Iu signaling and RB connection. This process is called Pre -R7 Fast
Dormancy. When there are data packages need to be transmitted again, it will
re-establish the RRC connection, and re-establish RB/RAB. This frequent data
transmission will cause frequent net work connection and release, and produce many
signaling messages, and so its
easy to cause signaling storm phenomenon.
82
To solve the problem, this function based on the heart beat strategy of the user plane,
can avoid UE sending the message SCRI, and avoid the frequent signaling connection
and release.
3.6.2.1
Heart Beat Strategy of the User Plane

In order to avoid the UE whos e version is 3GPP Release 7 or before Release 7 sending
the message Signalling Connection Release Indication , and avoid the frequent
signaling connection and release., the heart beat strategy is performed for the UE that
can meet the following conditions:
1.
The bit value of the parameter HeartBeat UeVer that the UEs version is
corresponding to is 1;
2.
PS service is present, and no CS service.
3.
RLC is acknowledged mode.
4.
If parameter GResPara8 is1: true, the conditionThe IE RRC Connection Set up

Complete. UE radio access capability .Device type is not present or its value is not
doesNotBenefitFromBattery ConsumptionOptimisatio n should be also satisfied; If
GResPara8 is0: false, then its no need to judge the reportedDevice type
condition.
When the conditions above are satisfied, and there is no data interaction between CN
and RNC for the UE, the RNC user plane will do heart beat detection to t he UE with t he
period HeartBeatFreq, and during the heart beat detection time, the heart beat data is not
included in the traffic volume measurement result of the user plane. When there are data
package int eractions between CN and RNC for the UE again, the heart beat detection is
stopped. So, based on the heart beat detection, it can avoid UE sending the message
SCRI, and avoid the frequent signaling connection and release.
3.6.2.2
Channel Switching Strategy of the Control Plane

Because of the heart beat detection to UE, UE will send acknowledge data packages
after it receives the heart beat data, this may cause that RNC cant make correctly
judgment of the event 4B0 for uplink traffic volume measurement, and it will cause that
83
the channel switching to PCH or Idle state based on the traffic volume measurement
cant be performed. In order to solve the problem, add a new parameter OnlyDnOnHB, to
control whether the channel switching to PCH or Idle state only bases on the downlink
traffic volume measurement report for the UE that is performed heart beat detection.
For the UE that is performed heart beat detection, if the parameter OnlyDnOnHB is 1,
the channel switching to PCH or Idle state only needs to base on the downlink traffic
volume measurement report; Otherwise, if the parameter OnlyDnOnHB is 0,the channel
switching to PCH or Idle state needs to base on both the downlink and uplink traffic
volume measurement report.
Note: Tests confirm that UE doesnt send uplink data packages after it rec eives the heart
beat data, and the channel switching to P CH or Idle state based on the downlink and
uplink traffic volume measurement can be normally performed, so the paramet er
OnlyDnOnHB can be set to 0:Off.
3.7
Other Description
3.7.1
Traffic Sub-class rate matching

CN send necessary Qos information to RNC by RAB assignment message. In Qos
information, it defines the related traffic information, for example the maximal bit rate. For
the user rat e control of RNC, besides the rate demand of CN, it is also controll ed by UE
capability limitation and real traffic situation. The whole process is rate matching.
Rate matching includes the following procedures:
1.
Iu assignment rate matching according to UE capability:
For HSPA: MaxBR1= min(max rate of Iu int erface (If there is MBR negotiation, it is the
max rate after negotiation), max rate according to UE capability);
For DCH: MaxBR1= max {max rate of Iu interface (If there is MBR negotiation, it is the
max rate after negotiation), 384kbps}
2.
Fuzzy match from MaxBR1 t o the nearest sub-service in sub- service list (Match to
84
the sub- service whose rate is nearest and not smaller than MaxBR1),and then
according to the matched s ub-s ervice number, it can get the paramet er
configuration for this traffic. Among them, the parameter MaxBitRate is MaxBR2.
3.
RNC controlled the max bit rate of this traffic is min(MaxB R2, max rate of Iu
interface (If there is MBR negotiation, it is the max rate aft er negotiation)).
3.7.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 -DS CH P hysical Layer c ategory 1 and

2
UE HS-DS CH Physical Lay er category 3, 4
and 12
UE HS -DS CH P hysical Layer c ategory 5 and
6
UE HS-DS CH Physical Layer category7 and
8
1.2Mbps
1.8Mbps
3.65Mbps
7.2Mbps
UE HS-DSCH Physical Layer category9
10.1Mbps
14Mbps
900kbps
Whether
UEcapability
supported
Max bit rate supported by UE
64QAM by
capability
Node B
not
UE
HS-DSCH
Physical
support
10.1Mbps(Match
64QAM
note)
Support 64QAM
17.6Mbps
not
14Mbps(Match
to
category9,see
Layer Category 13
UE
HS-DSCH
Physical
support
64QAM
note)
Support 64QAM
21.096Mbps
not
10.1Mbps(Match
to
category10,see
Layer Category 14
UE
HS-DSCH
Physical
Layer Category 15
64QAM
UE
not
HS-DSCH
Physical
support
to
category9,see
note)
support
14Mbps(Match
to
category10,see
85
Layer Category 16
64QAM
not
UE
HS-DSCH
Physical
note)
support
10.1Mbps(Match
64QAM
note)
Support 64QAM
17.6Mbps
not
14Mbps(Match
to
category9,see
Layer Category 17
UE
HS-DSCH
Physical
support
64QAM
note)
Support 64QAM
21.096Mbps
to
category10,see
Layer Category 18
Note: Configuration pattern of HA RQ Info in Uu interface

If RNC adjusts UE category downward according to Node B capability, the rate restriction
is the restriction after adjustment.
3.7.1.2
HSUPA UE capability and the mapping rate of supported MaxBR

E-DCH category
Category 1
Support for 10 and 2

ms TTI EDCH
Max bit rate supported
10 ms TTI only
711kbps
10 ms TTI
1.448 Mbps
2 ms TTI
1.448 Mbps
10 ms TTI only
1.448 Mbps
10 ms TTI
2.048Mbps
2 ms TTI
2.886 Mbps
10 ms TTI only
2.048Mbps
10 ms TTI
2.048Mbps
2 ms TTI
5.76 Mbps
10 ms TTI
2.048Mbps
Category 2
Category 3
Category 4
Category 5
Category 6
2
Category 7
ms
TTI(UE
not
configure 16QAM)
2
ms
TTI(UE
configure 16QAM)
5.76 Mbps
11.52Mbps
Note: Rat e matching according to UE capability considers the factor UE category,

modulation, etc.
86
3.7.2
MBR Controlling in RNC

This feature relates four cell-level parameters: UlCtrlMB RSwitch, UlControledMBR,
DlCtrlMB RS witch, DlControledMB R.
For Uplink MBR operated in RNC:
If the value of UlCtrlMBRS witch is 0: Off, then the Uplink MBR operated in RNC
MBR subscribed in CN
If the value of UlCtrlMB RS witch is 1: Replaced Mode , then the Uplink MB R operated in
RNC
= UlControledMB R
If the value of UlCt rlMBRS witch is 2: Minimum Mode , then the Uplink MBR operated in
RNC
= min{ MBR subscribed in CN, UlControledMB R }
If the value of UlCtrlMBRS witch is 3: Ma ximum Mode , then the Uplink MB R operated in
RNC
= max{ MBR subscribed in CN,UlControledMB R }
For Downlink MBR operated in RNC:

If the value of DlCtrlMB RS witch is 0: Off , then the Downlink MBR operated in RNC
MBR subscribed in CN
If the value of DlCtrlMBRS witch is 1: Replaced Mode , then the Downlink MBR operat ed
in RNC
= DlControledMB R
If the value of DlCtrlMBRS witch is 2: Minimum Mode , then the Downlink MBR operated in
RNC
= min{ MBR subscribed in CN, DlControledMB R }
If the value of DlCtrlMB RS witch is 3: Ma ximum Mode , then the Downlink MBR operat ed
in RNC
= max{ MBR subscribed in CN, DlControledMB R }
Notes:
1.
This feature is only used to modify the MB R in RNC, not related to RAB negotiation
or RAB re-negotiation.
2.
For
macro-diversity
and
mobility
state,
the
value
of
UlCtrlMB RS witch,
DlCtrlMB RS witch, UlControledMB R, DlControledMB R get the parameter values for
87
the best cell when RAB Setup, not changing with best cell updating.
3.7.3
IUB transmission bandwidth limitation strategy

When constructing a net work, there may be lack of Iub transmission resource. An access
of a high-rate UE may lead to numbers of other users inaccessibility to the network. In
order to avoid the case that some individual high -rate UE affect the communication
quality in large scale, it is necessary to limit the maximum rate of these UE in the cell.
For signaling: CResPara4 is used to limit the maximum bit rate for signaling in cell. When there
is lack of Iub transmission resource, i t can improve the successful ratio of RRC connection.
For service:
In
the
case
of
intra-RNC,
for
DCH
users,
parameters
RtMaxUlRateDch
RtMaxDlRateDch (for RT service) and Nrt MaxUlRateDch / Nrt MaxDlRateDch (for NRT
service) are used to limited the DCH maximum rat e of uplink and downlink respectively.
For E DCH users, the E -DCH users maximum rates are limited by the parameters
RtMaxrat eEdch (for RT service) and Nrt MaxRateEdch (for NRT service).
In the case of inter-RNC,
for DCH users,
paramet ers
Rt MaxUlRateDchD /
RtMaxDlRateDchD (for RT service) and NrtMaxUlRateDchD / NrtMaxDlRateDchD (for

NRT service) are used to limited the DCH maximum rate of uplink and downlink
respectively. For E DCH users, the E-DCH users maximum rat es are limit ed by
parameters RtMaxRat eEdchD (for RT service) and Nrt MaxRateEdchD (for NRT service).
If the related parameters are not configured in the neighboring cells, the restriction
decision does not effect.
In the case of macro diversity, the limited rat e is set to the minimum limited rate value of
all the cells in the active set.
3.7.4
Be compatible with the IPHONE which is not implement according to

encryption protocol
When some versions of IPHONE trigger conversation services, if the RRC connection is
established on CE LL_FACH, and on the process of switching to CELL_DCH during RAB
process, their implements are not according to encry ption protocol, in that case, they will
88
suffer bubble noise caused by losing alignment of CFN. In order to be compatible with
this kind of IP HONE, ZTE set a switch Cs RrcOnFachS wc h to control RRC not to be
established on CELL_FA CH to guarantee UE not attempt to access CELL_FA CH aft er
the admission decision for RRC on CELL_DCH failed.
After the admission decision for RRC on CELL_DCH failed,if it is CS service,whether
access to FACH/RA CH is decided by Cs RrcOnFachS wc h.(CS service is defined by
Establish cause, which is Originating Convers ational Call or Terminating Conversational
Call). If CsRrcOnFachS wch is off, RRC of CS service which is not emergency call cant
be established on FACH/RA CH. Emergency call is not restricted by this switch.
3.7.5
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 Source Statistics Descriptor to decide MaxBR of HSDPA, and set
a parameter MaxDHsRate to control the MaxBR of HS DPA traffic.
If the value of IETrCH Source Statistics Descriptor is Speech,then MaxBR =38.8k
If the value of IETrCH Source Statistics Descriptor isRRC ,then MaxBR =3.4k
If the value of IETrCH Source Statistics Descriptor isUnknown,or even this IE is
absent, then MaxBR is decided by IEtraffic class
If
the
value
of
background,then
IE Traffic
calculate
class
is
streaming,
interactive
or
MaxB R=max{MaxDHsRate1,GBR};thereint o
MaxDHs Rate1=min{MaxDHsRate,MaxBR of HS-DS CH supported by UE }
If the value of IETraffic class is conversation ,then MaxBR=38.8k
Note:MaxB R of HS-DSCH supported by UE is the max bitrate supported by

UE category.
3.7.6
Switching Timers Based on UE Capabilities

If UE carries IEDevice type in RRC Connection S etup Complete message, and takes
doesNotBenefitFromBattery ConsumptionOptimisation as its value, it concludes that UE
is insensitive to battery consumption. The UE to report the IE Device type is generally
data card user, who features frequent background data transmission, resulting in
89
frequent channel switching. In order to resolve such problems, if traffic measurement

event 4B0 triggers channel switching to PCH or idle, add DeltaNumE4B0Thd times
based on required event 4B0 report times.
The following traffic measurement-based channel switching are involved:
CELL_DCH(DL DCH/ UL DCH ) -> URA_P CH
CELL_DCH(DL DCH/ UL DCH ) -> IDLE
CELL_DCH(DL HS-DS CH/ UL DCH) -> URA _PCH
CELL_DCH(DL HS-DS CH/ UL DCH) -> IDLE
CELL_DCH
(DL HS -DS CH/UL E-DCH)-> URA _PCH
CELL_DCH (DL HS-DSCH/UL E-DCH)-> IDLE

CELL_FA CH(DL FA CH/UL RA CH) -> URA_P CH
CELL_FA CH(DL FA CH/UL RA CH) -> IDLE
CELL_FA CH(DL HS-DSCH /UL RA CH) -> URA_P CH
CELL_FA CH(DL HS-DSCH /UL RA CH) -> IDLE
CELL_FA CH(DL HS-DSCH/UL E-DCH) -> URA _PCH
CELL_FA CH(DL HS-DSCH/UL E-DCH) -> IDLE
Note:
1.
For channel switching above mentioned, if the report whose traffic measurement is
not 0 is received before reaching the threshold times, the count er should be cleared
to 0.
2.
The other conditions required for channel switching keep unchanged.
3.
In test, some mobile phones also report IE Device type .
90
3.7.7
CS Experience Improvement for Concurrence Service with CS+PS

For improving CS Experience improvement of Concurrence Service with CS+PS,
CsPlusPsSwch is used:
(1) If CsPlusPsSwch is set to1:on:
If CS setup before PS, then PS is setup on DCH with the minimal DRBC rate of
DCH.
If PS setup before CS, then PS will downgrade to DCH with the minimal DRBC
rate of DCH.
Before the CS releasing, the PS will not be re-configured to HS-DSCH based on

traffic volume measurement. After the CS released, the PS can be re-configured
to HS-DSCH based on traffic volume measurement.
(2) If CsPlusPsSwch is set to0:off, this feature is not active. The formal DRBC
strategy is performed.
Notes:
If CsPlusPsSwch is set to1:on, PS is setup on DCH or downgrade to DCH, PS

data rate can be adjusted based on traffic volume measurement with the
condition that the total PS data rate is lower than or equal to DlPsRateLmtLowC,
UlPsRateLmtLowC, DlPsRateLmtHighC and UlPsRateLmtHighC. Thats, If
CsPlusPsSwch is set to1:on, PS is setup on DCH or downgrade to DCH, all
the strategy keeps the same except that the PS cannot be re-configured to
HS-DSCH based on traffic volume measurement..
For PS downgrade triggered by new service RB setup:
For UE with R6 or later release, if R6MulRabRcfgMeth is set to 0:RB Setup

Method, the new service RB setup and PS reconfiguration from HS to DCH
will be performed simultaneously. If R6MulRabRcfgMeth is set to 1:RB
Reconfiguration Method, the PS reconfiguration from HS to DCH will be
performed before the new service RB setup.
For UE with release before R6, the PS reconfiguration from HS to DCH will
be performed before the new service RB setup always
91
The PS downgrade to DCH triggered by CS setup before PS, only the scene of CS
setup, RAB modify and CS hard handover is taken into account (CS over HSPA is
not
3.7.8
taken into account also)
UE PCH Compatibility Strategy

For some UE with release of R99 and R4, PCH compatibility is not well. So for the UE
with release of R99 and R4, the state transfer to PCH is controlled by the switch
GResPara13.
If GResPara13 is set to 0, the state transfer to PCH (URA_PCH or CELL_PCH) will not
performed for UE with release of R99 and R4, which will transfer to idle directly(the same
as PchSwch set to 0:off). If GResPara13 is set to 0, the state transfer to PCH
(URA_PCH or CELL_PCH) can be performed.
3.7.9
DRBC F/P->D Performance Optimization

To solve CPU overload, procedure optimization is done from PCH or FACH to
CELL_DCH state (in which case, the channel re-selection will not done wholly). The
strategy is following:
For UE in URA_PCH/CELL_PCH state, when cell update triggered by Uplink data
transmitting, or downlink data transmitted, or new service setup, URA_PCH/CELL_PCH
state to CELL_DCH state will be triggered. For UE in CELL_FACH state, CELL_FACH
state to CELL_DCH state will be triggered by traffic volume measurement (Event 4A).
During which, the last CELL_DCH channel will be tried firstly in which cell capability and
traffic type mapping will be taken into account; if ok, the last CELL_DCH channel will be
used; else, the channel type selection will be done. (Notes: if the cell back to CELL_DCH
state is the same as the cell before leaving the CELL_DCH state, the last CELL_DCH
channel will be tried directly. no cell capability and traffic type mapping will be done.)
Notes:
1
The aim of this strategy is to reduce the DRBC channel allocation and cell
selection procedure. But the last channel setting needs to be kept when leaving
CELL_DCH state.
Traffic type preference PrefTrafType matching: if the Traffic type
is included in
the value of PrefTrafType, the Traffic type preference will be satisfied in this cell.
92
Cell capability matching:
If the last channel setting is HS/E, the cell should be with the HS/E
capability(HspaSptMeth is R6+R5 or R6+R5+R99, the capability in Audit
Response is supported, and hsdStat/hseStat is active) and the cell capability(E-TTI,
SF of E-DCH, HARQ of E-DCH) is larger than or equal to the last channel setting
requirement.
If the last channel setting is HS/D, the cell should be with the HS/D capability
(HspaSptMeth is
R5/R5+R99/R6+R5/R6+R5+R99, the
capability
in
Audit
Response is supported, and hsdStat is active).

If the last channel setting is D/D, the cell should be with the D/D capability
(HspaSptMeth is R99/R5+R99 /R6+R5+R99).
For HS/E and HS/D: if singling RB is setup on HS-DSCH, the cell should support
F-DPCH or E-FDPCH.
For CELL_FACH state, the last channel setting should be deleted when receiving
RAB setup, RAB Modify, or RAB Release.
3.7.10
CELL_PCH Supporting
One of CELL_PCH or URA_PCH feature can be selected by switch PchSwch
(GResPara49 is used in UR11.10 Release temporarily, PchSwch is used in
UR11.20Release normally).
With CELL_PCH supporting, the state transfer to PCH is the same as URA_PCH
supporting, the difference only is: when decision to transfer state to PCH,
CELL_PCH or URA_PCH need to be selected based on the parameter
PchSwch(GResPara49): If PchSwch GResPara49 is set to 1:Only Support
URA_PCH: then transfer to URA_PCH; If PchSwchGResPara49is set to 2:Only
Support CELL_PCH, then transfer to CELL_PCH.
Notes:
(1) The state transfer from CELL_PCH to other state is the same as the state
transfer from URA_PCH to other state.
(2) The state transfer between CELL_PCH and URA_PCH is not supported.
93
(3) When receiving Cell_update or URA_update message in PCH state, the stay
timer in PCH state will not reset.
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
DrbcS wch
Rfach
Rrac h
FachSwch
DchAdjRateS wch
UlPwrDasf
DlPwrDasf
FachE4aThd
DchE4aThd
DchE4bThd
PchHoldTimeThr
DtcpEaThd
Parameter name
DRB C Method Switch
Downlink Maximum Rate Thres hold of I/B Service on
CELL_FA CH
Uplink Maximum Rat e Threshold of I/B Service on
RACH
Switch of Transferring to CELL_FACH
Switch for DCH Rate Adjustment Based on Traffic
Volume Measurement
Switch for UL DCH Rate A djustment Based on UE
Transmission Power
Switch for DL DCH Rate A djustment Based on D -TCP
E vent 4A Counter Threshold for CELL_FA CH to
CELL_DCH Shared by Uplink and Downlink
E vent 4A Counter Threshold for Increasing Rate on
DCH or DCH->HSPA
E vent 4B Counter Threshold for Decreasing Rate on
DCH
Time Threshold for CELL_PCH or URA _PCH to Idle
E vent A Counter Threshold for PS on DL DCH or DL
AMR Dec reasing Rate on D-TCP
94
E vent
DtcpEbThd
Counter
Threshold
for
Restriction
PS
Increasing Rat e on DL DCH or Triggering DL AMR

Increasing Rate Bas ed on D-TCP
PchSwch
DToPchThd
FToPchThd
DToIdleThd
FToIdleThd
CRateThrd
DlPsRateLmtLowC
UlPsRateLmtLowC
DlPsRateLmtHighC
UlPsRateLmtHighC
UpUdRec fgTimer
DnUdRec fgTimer
InitialRateUl
InitialRateDl
Switch of URA_P CH/CELL_P CH Support

E vent 4B Counter Threshold for CELL_DCH to P CH
Shared by Uplink and Downlink
E vent 4B Counter Threshold for CELL_FA CH without
DRX to Idle Shared by Uplink and Downlink
E vent 4B Counter Threshold for CELL_DCH to Idle
Shared by Uplink and Downlink
E vent 4B Counter Threshold for CELL_FA CH without
DRX to Idle Shared by Uplink and Downlink
C Traffic Rat e Threshold Used for Det ermining NRT PS
Rate Upper Limit
NRT PS Traffic Downlink Rate Upper Limit When High
Rate C Traffic+ PS Traffic
NRT PS Traffic Uplink Rate Upper Limit When Low Rate
C Traffic+ PS Traffic
NRT PS Traffic Downlink Rate Upper Limit When High
NRT PS Traffic Uplink Rate Upper Limit When High
Wait
Timer
for
Adjusting
Uplink
Wait
Timer
for
Adjusting
Uplink
and
Downlink
This parameter indic ates the initial rate of UL DCH

admission.
This parameter indic ates the initial rate of DL DCH
admission.
The Target of UE Version for HeartBeat
HeartBeatFreq
Heart Beat Period
Downlink
Reconfiguration by One Step Downward
HeartBeat UeVer
OnlyDnOnHB
and
Reconfiguration by One Step Upward
The Switch Indicates whether Only Judge the Downlink

Traffic
on Heart
Beat
for Channel
Switching to
95
PCH/ IDLE
Increment Times of E vent 4B0 for UE Which is not
DeltaNumE4B 0Thd
sensitive for Battery
Consumption Trans ferred to
URA _PCH or Idle state

DchSig68Swch
4.1.1.2
Switch of 6.8kbps Signaling Using on DCH
RNC configuration information

Abbreviated name
InitRrcOnDch
CsRrcOnFac hSwch
4.1.1.3
Parameter name
Ty pe of Transport Channel for Initial RRC Connection
Setup
Switch of Non Emergency CS S ervice Access to
CELL_FA CH On RRC
RNC configuration supplement information

Abbreviated name
4.1.1.4
GResPara4
Global Reserved Parameter 4
GResPara8
GResPara13
GResPara49
Logical RNC Configuration Information Associated With PLMN

Abbreviated name
CsPlusPsSwch
R6MulRabRcfgMeth
4.1.1.5
Parameter name
Parameter name
Switch of PS Sevice Channel Allocation for Concurrent
CS+PS
Online-already Service Reconfiguration Met hod for UE of
Release 6 and after Release 6 When Multi-RAB
QoS configuration related priority and rate level information

Abbreviated name
Parameter name
UlRateAdjLevNum
Uplink Rate Adjustment Level Number
UlRateAdjLev[MA X_NUM_RATE_A DJUS T]
Uplink Rate Adjustment Level
DlRateAdjLevNum
Downlink
Rate
Adjustment
Level
96
Number
DlRateAdjLev[MA X_NUM_RATE_A DJUS T]
4.1.1.6
Service Cell Information

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

Abbreviated name
AdjCs64S witch
NrtMax UlRateDchD
NrtMax DlRateDchD
RtMaxUlRateDchD
RtMaxDlRateDchD
Parameter name
Switch of CS 64kbps Establishment for External UTRAN
Cell
Maximum Bit Rat e on UL DCH for NRT PS RAB in
External UTRA N Cell
Maximum Bit Rat e on DL DCH for NRT PS RAB in
Maximum Bit Rat e on UL DCH for RT PS RAB in
Maximum Bit Rat e on DL DCH for RT PS RAB in
97
4.1.2
Parameter Configuration
4.1.2.1
DRBC Method Switch

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> Logical RNC Associated With PLMN Configuration Information ->Logical

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> DRB C Method Switch

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 whet her 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
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> Downlink Maximum Rate Threshold of I/B Service on CE LL_FACH

This parameter indicates the downlink maximum bit rate threshold for PS service being
98
established on CELL_FA CH. 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 service on the Rach.
The larger this parameter, the easier I/B service is set up or is switched to the fach/rach.
4.1.2.3
Uplink Maximum Rate Threshold of I/B Service on RACH

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> Logical RNC Associated With PLMN Configuration Information->Logical

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> Uplink Maximum Rate Threshold of I/B Service on RA CH

This parameter indic ates the uplink maximum bit rate threshold for PS service bei ng
established on CELL_FA CH. 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 threshold
indicated by this parameter and the downlink maximum bit rate or downlink target bit rate
is lower than the downlink maximum bit rate thres hold of the PS service on the FACH.
The larger this parameter, the easier I/B service is set up or is migrated to the fach/rach.
4.1.2.4
Switch of Transferring to CELL_FACH

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->Switch of Trans ferring to CELL_FACH

This parameter is a switch of other channels trans ferring to the Fach. When this
99
parameter is closed, it is not allowed to transfer from other channels to the Fach. When
this parameter is open, it is allowed to trans fer from other channels to the Fach.
Whatever this parameter is closed or open, it is essential to t rans fer to the FA CH first
before to dedicated channels from the PCH.
4.1.2.5
Switch for DCH Rate Adjustment Based on Traffic Volume Measurement

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->Switch for DCH Rate Adjustment Based on Traffic Volume Meas urement
This paramet er 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 servic e on the DCH.
4.1.2.6
Switch for UL DCH Rate Adjustment Based on UE Transmission Power

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
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 bas ed
on the UE transmitting power. When the parameter is OFF, the rate of PS service 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.
100
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

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->Switch for DL DCH Rate A djustment Based on D -TCP

This parameter is the rate adjustment switch on the DCH. The switch is triggered bas ed
on the D-TCP. When the parameter is OFF, the rate 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.
4.1.2.8
Event 4A Counter Threshold for CELL_FACH to CELL_DCH Shared by

Uplink and Downlink
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4A Counter Threshold for CELL_FA CH to CE LL_DCH Shared by

Uplink and Downlink
This parameter indicates the event 4A counter threshold for FACH-> DCH/HS -DS CH 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 t o the
DCH/HS -DS CH or from the RA CH to the DCH/EDCH. And when event 4A counter on
either the downlink or uplink reaches the thres hold, channel trans fer occurs.
The larger this
parameter is,
the harder the UE
will
be trans ferred from
FACH->DCH/HS-DS CH or RA CH->DCH/E DCH, and vice versa.
101
4.1.2.9
Event 4A Counter Threshold for Increasing Rate on DCH or DCH -> HSPA
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4A Counter Thres hold for Inc reasing Rate on DCH or DCH-> HSPA
This parameter indicates 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, UEs data rate on
DCH will be increased or UE will be trans ferred from DCH to HSPA.
The larger this parameter is, the more slowly the UE's data rate on DCH will be increas ed
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
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for Decreasing Rate on DCH

This parameter indicat es the event 4B counter threshold for dec reasing 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
indicated by this paramet er, UEs 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.
102
4.1.2.11
Time Threshold for CELL_PCH or URA_PCH to Idle

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> Time Threshold for CELL_PCH or URA _PCH to Idle

This parameter indicates the time threshold of UE staying in CELL_PCH or URA_PCH
for the judgment of transferring from CE LL_P CH or URA _PCH to idle. If the time of UE
having stayed in URA_P CH exceeds the threshold indicat ed by this parameter, the UE
will be transferred from URA_PCH to Idle.
The larger this parameter is, the longer the UE will stayed in URA_PCH and the harder
the UE will be trans ferred from PCH to IDLE. Vice versa.
4.1.2.12
Event A Counter Threshold for PS on DL DCH or DL AMR Decreasing Rate

on D-TCP
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent A Counter Threshold for PS on DL DCH or DL AMR Decreasing Rate

on D-TCP
This parameter indicates the event A c ounter threshold of consecutive DTCP reports for
DTCP -DRB C. If event A counter of DTCP reports reach the thres hold indicated by this
parameter, UEs rate on downlink DCH will be decreased.
The larger this parameter is, the harder UEs rate on downlink DCH will be decreased.
Vice versa.
103
4.1.2.13
Event B Counter Threshold for Restriction PS Increasing Rate on DL DCH

or Triggering DL AMR Increasing Rate Based on D-TCP
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent B Counter Threshold for Restriction PS Inc reasing Rate on DL DCH
or Triggering DL AMR Increasing Rate Based on D -TCP
This parameter indicates the event B counter threshold of c onsecutive DTCP reports for
DTCP -DRB C. If event B counter of dedicated TCP reports reach the threshold indicat ed
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 paramet er is, the harder the UE leaves eve nt 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 downlink.
4.1.2.14
Switch of URA_PCH/CELL_PCH Support

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->Switch of URA_P CH/CELL_P CH Support

This parameter indic ates whether transferring to URA _PCH/ CELL_P CH is supported or
not. If the value is Only Support URA_P CH, the UE is allowed to trans fer to the PCH
when there is no data to transmit. If the value is Not Support URA_P CH/CELL_P CH,
UE is not allowed to transfer to the PCH when there is no data to transmit.
104
4.1.2.15
Event 4B Counter Threshold for CELL_DCH to PCH Shared by Uplink and

Downlink
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> Logical RNC Associated With PLMN Co nfiguration Information->Logical

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for CE LL_DCH to P CH Shared by Uplink and

Downlink
This paramet er indicates 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 c onsecutive reporting times reach
this threshold, the DCH -> PCH state transition is triggered.
The higher the parameter value is, the harder the DCH -> P CH transition of the UE is
triggered, and vice versa.
4.1.2.16
Event 4B Counter Threshold for CELL_FACH without DRX to Idle Shared

by Uplink and Downlink
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for CELL_FA CH without DRX to Idle Shared
This paramet er indicates the threshold of the 4B event triggering times for CE LL_FACH
-> PCH transition. For a user whose bot h 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.
105
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
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Count er Threshold for CE LL_DCH to Idle Shared by Uplink and
Downlink
This parameter indicates the threshold of the 4B event triggering times for CE LL_ DCH ->
Idle transition. For a us er whose both uplink and downlink locate on the DCH, if the RLC
buffer loads of the uplink and downlink are 0, and the c onsecutive reporting times reach
this threshold, the DCH -> Idle state transition is triggered.
The higher the parameter 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 without DRX to Idle Shared

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for CELL_FA CH without DRX to Idle Shared
106
This paramet er indicates the threshold of the 4B event triggering times for CE LL_FACH
-> Idle transition. For a user whose 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 -> 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.
Its default val ue is 2.
4.1.2.19
C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit
This parameter defines the threshold for judging the rate 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 paramet er value is, the smaller the possibility of the High Rate C is, and
vice versa.
4.1.2.20
NRT PS Traffic Downlink Rate Upper Limit When High Rate C Traffic+ PS
Traffic
OMCR
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter-> Dynamic
Radio
Bearer
Cont rol
Information-> NRT PS Traffic Downli nk Rate Upper Limit When High Rate C Traffic+ PS
Traffic
107
This parameter indicates the I/B PS downlink rate upper limit when Multi -RABs are
conversational (CS or PS) + streaming/interactive/background PS and the rate of the
conversational service is high, in which case, the sum of the downlink rates of all the I/B
PS servic es cannot exceed this threshold. Whether the rate of the conversational service
is considered as low or high is determined according to C Traffic Rate Threshold Used
for Determining NRT PS Rate Upper Limit .
4.1.2.21
NRT PS Traffic Uplink Rate Upper Limit When High Rate C Traffic+ PS
Traffic
OMCR
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter-> Dynamic
Radio
Bearer
Cont rol
Information-> NRT PS Traffic Uplink Rate Upper Limit When High Rate C Traffic+ PS
Traffic
This parameter indicates the I/B PS uplink rate upper limit when Multi-RABs are
conversational service is high, in which case, the sum of the uplink rates of all the I/B PS
services cannot exceed this thres hold. Whether the rat e of the conversational service is
considered as low or high is determined according to C Traffic Rate Threshold Used for
Determining NRT PS Rate Upper Limit.
4.1.2.22
NRT PS Traffic Downlink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic
OMCR
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter-> Dynamic
Radio
Bearer
Cont rol
Information-> NRT PS Traffic Downlink Rate Upper Limit When Low Rate C Traffic+ PS
108
Traffic
This parameter indicates the I/B PS downlink rate upper limit when Multi -RABs are
conversational service is low, in which case, the sum of the downlink rates of all the I/B
PS servic es cannot exceed this threshold. Whether the rate of the conversational service
is considered as low or high is determined according to C Traffic Rate Threshold Used
for Determining NRT PS Rate Upper Limit .
4.1.2.23
NRT PS Traffic Uplink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic
OMCR
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter-> Dynamic
Radio
Bearer
Cont rol
Information-> NRT PS Traffic Uplink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic
This parameter indicates the I/B PS uplink rate upper limit when Multi -RABs are
conversational service is low, in which case, the sum of the uplink rates of all the I/B PS
services cannot exceed this thres hold. Whether the rat e of the conversational servic e is
considered as low or high is determined according to C Traffic Rate Threshold Used for
Determining NRT PS Rate Upper Limit.
4.1.2.24
Type of Transport Channel for Initial RRC Connection Setup

OMC Path
path:
View->Configuration
Management-> RNC
NE-> RNC
Radio
Resource
109
Management-> RNC Configuration-> Ty pe of Trans port
Channel
for Initial
RRC
Connection S etup
This parameter indicates the type of transport channel of signaling when initial RRC
connection setup.
4.1.2.25
Uplink Rate Adjustment Level Number

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Qos Relevanc e Configuration-> Qos Configuration-> Qos Configuration

XXX-> Uplink Rate Adjustment Level Number
This parameter indicates the number of uplink rate adjustment levels used by the DRBC.
It regulates the number of uplink rate adjustment levels for services on the DCH.
4.1.2.26
Uplink Rate Adjustment Level

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

XXX-> Uplink Rate Adjustment Level
This parameter indicat es the uplink rate adjustment levels used by DRB C. The uplink
rate adjustment can be adjusted on these levels only.
4.1.2.27
Downlink Rate Adjustment Level Number

OMC Path
110
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

XXX-> 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.
4.1.2.28
Downlink Rate Adjustment Level

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

XXX-> Downlink Rate Adjustment Level
This parameter indicates the downlink rate adjustment levels used by DRB C. The
downlink rat e adjustment range can be adjusted on these levels only.
4.1.2.29
Maximum Allowable Rate on DCH to be Increased to When UE is in Macro

Diversity(kbps)
OMC Path
Path:View-> Configuration
Management-> RNC
Management-> UtranCell-> UtranCellX->Modify
NE->RNC
Radio
Resource
Advanc ed
Parameter->UtranCell->Maximum Allowable Rate on DCH to be Increased to When UE

is in Macro Diversity(kbps)
This parameter indic ates the maximum rate t hreshold 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 threshold. When the UE is in macro diversity and its current rate is larger
than this parameter, rat e adjustment is not affected by this parameter. The larger this
111
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.30
Switch of CS 64kbps Establishment

OMC Path
Management-> RNC
NE->RNC
Radio
Resource
Management-> UtranCell-> UtranCellX->Cell Setup P arameters-> Switch of CS 64kbps

Establishment
This parameter defines whether a cell supports CS 64K services. When the parameter is
ON, the cell supports CS64K services; when the parameter is OFF, the cell does not
support CS64K services. Its default value is open.
4.1.2.31
Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Advanc ed
Radio
Resource
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 paramet er value is, the higher the uplink rat e higher threshold of users on the
DCH in the cell is, and vice versa.
Its default value is 384kbps.
4.1.2.32
Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell

OMC Path
112
Path:
View->Configuration
Management-> RNC
NE ->RNC
Advanc ed
Radio
Resource
Maximum Bit Rate on DL DCH for NRT PS RAB(kbps)

This parameter defines the downlink rate higher threshold of NRT PS s ervices in a cell.
The higher the parameter 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.33
Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
OMC Path
Management->External
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran CellX->
Radio
Modify
Resource
Advanc ed
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 UTRA N
Cell for an NRT PS domain RAB.
The default value is384kbps.
4.1.2.34
Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
OMC Path
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran CellX->
Radio
Modify
Resource
Advanc ed
Parameter-> Maximum 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 UTRA N
113
cell for an NRT PS domain RAB.

4.1.2.35
Maximum Bit Rate on DL DCH for NRT PS RAB in External UTRAN Cell
OMC Path
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran CellX->
Radio
Modify
Resource
Advanc ed
Parameter-> Maximum 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 UTRA N
Cell for an NRT PS domain RAB.
4.1.2.36
Maximum Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell

OMC Path
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran CellX->
Radio
Modify
Resource
Advanc ed
Parameter-> Maximum Bit Rate on DL DCH for RT PS RAB in External UTRA N Cell
This parameter indicates the maximum bit rate on DL DCH allowed in External UTRA N
cell for an RT PS domain RAB.
4.1.2.37
Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell

OMC Path
114
Management-> RNC
NE->RNC
Advanc ed
Radio
Resource
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.38
Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell

OMC Path
Management-> RNC
NE->RNC
Advanc ed
Radio
Resource
Maximum Bit Rate 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.39
Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell

OMC Path
Management-> RNC
NE->RNC
Advanc ed
Radio
Resource
Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell

115
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.40
Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell

OMC Path
Management-> RNC
NE->RNC
Radio
Resource
Advanc ed
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.41
Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
OMC Path
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran CellX->
Radio
Modify
Resource
Advanc ed
Parameter-> Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRA N Cell
This parameter indicates the maximum bit rate on E-DCH allowed in External UTRA N
cell for an NRT PS domain RAB.
116
4.1.2.42
Maximum Bit Rate on E-DCH for RT PS RAB in External UTRAN Cell

OMC Path
Management-> RNC
Ut ran
Cell ->
External
NE->RNC
Utran
Radio
CellX->
Modify
Resource
Advanc ed
Parameter-> Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRA N Cell
This parameter indicates the maximum bit rate on E-DCH allowed in External UTRA N
cell for an RT PS domain RAB.
4.1.2.43
Switch of CS 64kbps Establishment for External UTRAN Cell

OMC Path
Management-> RNC
NE->RNC
Radio
Resource
Management->External Ut ran Cell -> External Ut ran CellX-> Global Else-> Switch of CS
64kbps Establishment for External UTRA N Cell
This parameter defines whether a RNC cell adjacent to IUR supports CS64K services.
When the paramet er is OPE N, the adjacent RNC cell supports CS64K services; when
the parameter is CLOSE D, the cell does not suppo rt CS64K services.
Its default value is open.
4.1.2.44
Max CS Delay
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Modify Advanced Parameter-> RNC Radio Resource Management->Max

CS Delay
117
Parameter configuration
This parameter is the max buffer delay for CS voic e.
4.1.2.45
Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step
Upward
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Modify Advanced Parameter->RNC Radio Resourc e Management->Wait

Timer for Adjusting Uplink and Downlink Reconfiguration by One Step Upward
This parameter defines the timer used for waiting UL and DL upward reconfiguration in
one step.
4.1.2.46
Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step
Downward
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Modify Advanced Parameter->RNC Radio Resourc e Management->Wait

Timer for Adjusting Uplink and Downlink Reconfiguration by One Step Downward
This parameter defines the timer used for waiting UL and DL downward reconfiguration
in one step.
4.1.2.47
Initial Rate of UL DCH

OMC Path
118
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> Initial Rate of UL DCH

This parameter defines the Uplink initial rate of DCH setup traffic.
4.1.2.48
Initial Rate of DL DCH

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> Initial Rate of DL DCH

This parameter defines the Uplink initial rate of DCH setup traffic.
4.1.2.49
UL Controlled MBR Switch

OMCR
Management-> RNC
NE->RNC
Radio
Resource
Management-> UtranCell-> UtranCellX->Modify Advanced Parameter->Modify Advanc ed

Parametr-> UtranCell-> UL Controlled MBR S witch
This parameters specifies the switch for the UL Controlled MBR function.
119
4.1.2.50
DL Controlled MBR Switch

OMCR
Management-> RNC
NE->RNC
Radio
Resource

Parametr-> UtranCell-> DL Controlled MBR S witch
This parameters specifies the switch for DL Controlled MBR function.
4.1.2.51
UL Controlled MBR
OMCR
Management-> RNC
NE->RNC
Radio
Resource

Parametr-> UtranCell-> UL Controlled MBR
This parameter specifies the MB R value in the DL controlled MB R function.
4.1.2.52
DL Controlled MBR
OMCR
Management-> RNC
NE->RNC
Radio
Resource
Management-> Ut ranCell->UtranCellX->Modify Advanced Parameter->Modify Advanced

Parametr-> UtranCell-> DL Controlled MBR
This parameter specifies the MB R value in the DL controlled MB R function.
4.1.2.53
Cell Reserved Parameter 4

OMCR
120
Path
View->Configuration
Management->RNC
NE->RNC
Radio
Resource
Management-> Ut ranCell->UtranCellX->Modify Advanced Parameter->Modify Advanced

Parametr-> UtranCell-> CResPara4
This parameter indicates the maximum bit rate allowed in cell for signaling.
4.1.2.54
Switch of non Emergency CS Service Access to CELL_FACH On RRC
OMCR
Management->
Modify
Management-> RNC
Advanced Parameter->
NE->RNC
Dynamic
Radio
Resource
Radio Bearer
Cont rol
Information
This parameter indicates whet her non emergency CS service access to CELL_FA CH on
RRC process. If this switch is Off, It means non emergency CS service will not access
to FACH/ RACH or HS-DSCH/RA CH on RRC process.
4.1.2.55
The Target of UE Version for HeartBeat

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Modify Advanced P arameter->RNC Radio Resource Management-> The

Target of UE Version for Heart Beat
This parameter indic ates the UE version for heart beat detection. In order to avoid UE
(before R8 )sending Signaling Connection Release Indication (SCRI )and release
signaling connection, RNC will do heart beat detection when no data transmission with
CN, UE will not send SCRI when receive data. The bit of this parameter indicates
whet her execute heart beat detection on the UE version.
121
4.1.2.56
Heart Beat Period

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanc ed
NE ->RNC
Parameter->RNC
Radio
Radio
Resource
Resource
Management-> Heart Beat Period

This parameter indicates the period of UE heart beat.
4.1.2.57
The Switch Indicates whether Only Judge the Downlink Traffic on Heart
Beat for Channel Switching to PCH/IDLE
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management->Modify Advanced P arameter->RNC Radio Resource Management-> The

Switch Indic ates whet her Only Judge the Downlink Traffic on Heart Beat for Channel
Switching to PCH/IDLE
This parameter indicates whether the channel s witching to P CH or Idle state only bases on
the downlink traffic volume measurement report for the UE that is performed heart beat
detection.
4.1.2.58
Golbal Reserved Parameter 4

OMCR
Path:
View->Configuration
Management-> Logical
XXX->Modify
RNC
Advanc ed
Management-> RNC
Associated
With
Parameter->RNC
NE ->RNC
PLMN
Radio
Configuration
Configuration
Resource
Information
Supplement
Information->Global Reserved Parameter 4

This parameter indicates whether the RNC support PS 0kbps/0kbps .
122
4.1.2.59
Golbal Reserved Parameter 8

OMCR
Path:
View->Configuration
XXX->Modify
RNC
Management-> RNC
Associated
Advanc ed
With
NE ->RNC
PLMN
Parameter->RNC
Radio
Configuration
Resource
Information
Configuration
Supplement
Information->Global Reserved Parameter 8

This parameter indic ates whether to judge the IE Device type in the message RRC
Connection S etup Complete, when judge the conditions should be satisfied for UE
which is performed heart beat detection.
4.1.2.60
Increment Times of Event 4B0 for UE Which is not sensitive for Battery
Consumption Transferred to URA_PCH or Idle state
OMCR
Path:
View-> Configuration
Management->RNC
NE-> RNC
Radio
Resource

RNC
XXX->Modify
Advanced
P arameter-> Dynamic
Radio
Bearer
Controll
Information-> Increment Times of Event 4B0 for UE Which is Not Sensitive for Battery
Cons umption Transferred to URA_P CH or Idle State
This parameter indicates the increment times of event 4B0 for UE which is not sensitive
for battery consumption is transferred to URA_P CH or Idle state based on the traffic
volume measurement, relative to other UEs. For this kind of UE, the
value of this
parameter is larger, the transition for the UE to URA _PCH or Idle is more difficult.
4.1.2.61
Switch of 6.8kbps Signaling Using on DCH

OMCR
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
123
RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->Switch of 6.8kbps Signaling Using on DCH

This parameter indicates whether substitute 3.4kbps signaling by 6.8 kbps signaling
during RRC connection setup when signaling is carried on DCH or when RB has been
setup and signaling is carried on DPCH alone.
4.1.2.62
Gl obal Reserved Parameter 13
Path:
OMCR
View->Configuration
Management->RNC
NE->RNC
Radio
Resource
Management->Logical RNC Associated With PLMN Configuration Info rmation XXX->Modify

Advanced
Parameter->RNC
Configuration
Supplement
Informat ion->Global
Reserved
Parameter 13
This parameter indicates whether the UE with release R99 o r R4 can transfer to PCH state.
4.1.2.63
Gl obal Reserved Parameter 49
Path:
OMCR
View->Configuration
Management->RNC
NE->RNC
Radio
Resource

Advanced
Parameter->RNC
Configuration
Supplement
Informat ion->Global
Reserved
Parameter 49
This parameter indicates whether URA_PCH/CELL_ PCH is activated.
4.1.2.64
Switch of PS Sevice Channel Allocati on for Concurrent CS+PS
OMCR
124
Path:
View->Configuration
Management->RNC
NE->RNC
Radio
Resource

Advanced Parameter->RNC Configurat ion Related to PLM N->Switch of PS Sevice Channel
Allocation for Concurrent CS+PS
This parameter is used to control PS sevice channel allocation for concurrent CS+PS . If the
parameter is on, for CS service first and then PS service triggered scene,allocate DCH/DCH for
the PS service; For PS service first and then CS service triggered scene,and if PS is on HS,
perform the HS to DCH reguration.Otherwise, allocate HS-DSCH/EDCH, HS-DSCH/ DCH or
DCH/ DCH for
4.1.2.65
PS service according to UE capability.
Online-already Service Reconfiguration Method for UE of Release 6 and after Release 6

When Mul ti-RAB
Path:
OMCR
View->Configuration
Management->RNC
NE->RNC
Radio
Resource

Advanced
Parameter->RNC
Configuration
Related
to
PLM N->On line-already
Service
Reconfiguration Method for UE of Release 6 and after Release 6 When Multi -RA B
This parameter is used to control online-already service reconfiguration method for UE of

Release 6 and after Release 6 when mult i-RA B. For the scene that it needs to reconfigure the
already online service at the same time when the setup of new service, if
the paramter is set to
"0" ,it means it takes RB Setup method,and then both the online-already service reconfiguration
and new service setup by the RADIO BEARER SETUP message in one step;if the paramter is
set to "1" ,it means it takes RB Reconfiguration method, it first performs the online-already
service reconfiguration by RADIO BEARER RECONFIGURATION message, and then
performs new service setup by RADIO BEARER SETUP message.
125
4.2
HSDPA Dynamic Channel Adjustment Related

Parameters
4.2.1
Parameter List
4.2.1.1

Abbreviated name
ToFtimes Thr
IBChQS wch
SChQS wch
DToHs Delay Thr
Parameter name
E vent
4B
Count er
Threshold
for
CE LL_DCH
to
CELL_FA CH
HS/D-> D/D or HS/E-> D/D Based on Quality Measurement
Switch for I/B Traffic
HS/D-> D/D or HS/E-> D/D Based on Quality Measurement
Switch for S Traffic
Delay Time Threshold of D/D-> HS/D or HS/E after HS/D or
HS/E ->D/D Triggering by Channel Quality
CRESPARA7
MaxDHs Rate
Maximum Bit Rate of HS DPA Across Iur Interface
RncFdpchSupInd
RNC F-DPCH Support Indicator
EfdpchSupInd
Cell Enhanced F-DPCH Support Indicator
RncEfdpchSupInd
RNC Enhanced F-DPCH Support Indic ator
4.2.2
4.2.2.1
Event 4B Counter Threshold for CELL_DCH to CELL_FACH

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for Cell_Dch to Cell_FA CH

126
For the UE which is using DELL_DCH, if the measurement of t he 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 tim es of the
measured RLC buffer payload of the downlink being smaller than the event 4Bs
threshold on uplink and the downlink exceed the threshold indicated by this paramet er,
the UE will be trans ferred from CELL_DCH to CELL_FA CH. For I/B traffic class, att empt
accessing CELL_DCH after failure of accessing CELL_FA CH ,For S traffic class, attempt
accessing CELL_DCH directly.
The larger this parameter is, the harder the UE will be transferred from CELL_DCH to
CELL_FA CH. 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
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> HS/D-> D/D or HS/E->D/D Based on Quality Measurement Switch for I/B
Traffic
This parameter indicates whether downlink service transferring from HS -DSCH to DCH
for I/B servic es based on Quality Measurement is supported. This transferring is started
by 1F events according to channel quality.
When this paramet er is set to open, downlink service transferring from HS -DS CH to DCH
is support ed for I/B services by 1F events. When this paramet er is set to Closed,
downlink service transferring from HS -DS CH to DCH is not supported for I/B services by
1F events.
127
4.2.2.3
HS/D->D/D or HS/E->D/D Based on Quality Measurement Switch for S

Traffic
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information-> HS/D-> D/D or HS/E-> D/D Based on Quality Measurement Switch for S
Traffic
This parameter indicates whether downlink service transferring from HS-DSCH to DCH
for stream s ervices 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 stream services by 1F events. When this paramet er is set to
Closed, downlink servic e transferring from HS-DS CH to DCH is not supported for stream
services by 1F events.
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
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanc ed
NE ->RNC
Parameter->RNC
Radio
Radio
Resource
Resource
Management-> Delay Time Threshold 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, whic h is after HS -DS CH/DCH or HS-DSCH/E-DCH switch to
DCH/DCH trigger by channel quality
128
The default value is 10s
4.2.2.5

OMCR
Path
View->Configuration Management->RNC NE->RNC Radio Resource
Management->
UtranCell->UtranCellX->Modify
Advanced
Parameter->Modify
Advanced Parametr->UtranCell-> CResPara7

This parameter indicates whether cell support F-DPCH.
4.2.2.6
Maximum Bit Rate of HSDPA Across Iur Interface

OMCR
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanc ed
NE ->RNC
Parameter->RNC
Radio
Radio
Resource
Resource
Management->Maximum Bit Rate of HS DPA Across Iur Interface

This parameter indicates the maximum bit rate of HS -DS CH across Iur interfac e.
4.2.2.7
RNC F-DPCH Support Indicator

OMCR
Path:
Management-> RNC
NE->RNC
Radio
Resource
Management-> HSPA Configuration->RNC F-DPCH Support indicator

This parameter indicates whether RNC support F-DPCH.
4.2.2.8
Cell Enhanced F-DPCH Support Indicator

OMCR
129
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> Utran Cell->Utran Cell XXX->Cell Setup Parameters-> Cell Enhanc ed

F-DP CH Support Indicator
This parameter indicates whether cell support enhanced F-DP CH.
4.2.2.9
RNC Enhanced F-DPCH Support Indicator

OMCR
Path:
Management-> RNC
NE->RNC
Radio
Resource
Management-> HSPA Configuration->RNC Enhanced F -DP CH S upport indicat or

This parameter indicates whether RNC support enhanced F-DP CH.
4.3
HSUPA Dynamic Channel Adjustment Related

Parameters
4.3.1
Parameter List
4.3.1.1

Abbreviated name
SrbOnEdchSwc h
Parameter name
Switch of supporting SRB on E-DCH
E vent 4B Counter Threshold for HSPA Using DTX/ DRX or
DxHsBo0E 4bThd
CELL_FA CH using DRX to PCH or IDLE Shared by Uplink and

Downlink
EttiTraffVolSwch
ETtiEaThd
ETtiEbThd
Switch of E-TTI Switching Triggered by User Plane Throughput

Measurement
E vent 4A Counter Threshold for E-TTI Switching from 10ms to
2ms
E vent 4B Counter Threshold for E-TTI S witching from 2ms to
130
10ms
FourEchAllowed
Four E-DP DCHs Allowed Indicator
4.3.2
4.3.2.1
Switch of supporting SRB on E-DCH

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC XXX->DRBC Controlling Configuration Information->Switch of supporting SRB on
E-DCH
This parameter defines whether the uplink signaling service 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 s ervice is established on the E -DCH, or
else the uplink signaling service is established on the DCH.
4.3.2.2
Event 4B Counter Threshold for HSPA Using DTX/DRX or CELL_FACH

using DRX to PCH or IDLE Shared by Uplink and Downlink
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for HSPA Using DTX/DRX or CE LL_FACH

using DRX t o PCH or IDLE Shared by Uplink and Downlink
This parameter indicates the event 4B counter threshold for HSPA using DTX/DRX or
131
CELL_FA CH using DRX to PCH or IDLE shared by uplink and downlink. For the HSPA
UE using the DTX/ DRX and CELL_FA CH using Enhanc ed UE DRX, if the times of the
measured RLC buffer payload of t he uplink and downlink being zero exceed t he
threshold indicated by this parameter, UE will be transferred from HSPA or CE LL_FACH
to PCH or IDLE.
4.3.2.3
Switch of E-TTI Switching Triggered by User Plane Throughput

Measurement
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Information->Switch of E-TTI Switching Triggered by
Radio
Bearer
User Plane
Cont roll
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.
4.3.2.4
Event 4A Counter Threshold for E-TTI Switching from 10ms to 2ms

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4A Counter Thres hold for E-TTI Switching from 10ms to 2ms
This parameter indic ates 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 user plane E-DCH
throughput being larger than the 4A threshold exceed the threshold indicated by this
132
parameter and 2ms E-TTI is used, UEs E-TTI will be switched to 2ms.
4.3.2.5
Event 4B Counter Threshold for E-TTI Switching from 2ms to 10ms

OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource

RNC
XXX->Modify
Advanced
Parameter->Dynamic
Radio
Bearer
Cont roll
Information->E vent 4B Counter Threshold for E-TTI S witching from 2ms to 10ms
This parameter indic ates 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 user plane E-DCH
throughput being larger than the 4A threshold exceed the threshold indicated by this
parameter and 2ms E-TTI is used, UEs E-TTI will be switched to 2ms.
4.3.2.6
Four E-DPDCHs Allowed Indicator

OMC Path
Path:
View->Configuration
RNC
Management-> RNC
Associated
With
NE ->RNC
PLMN
Radio
Configuration
Resource
Information
XXX-> RNC Configuration Supplement Information->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 use 2SF2+ 2SF4 and the value 0 means not allowed to
use.
133
4.4
HSPA+ Dynamic Channel Adjustment Parameters
4.4.1
Parameter List
Abbreviated name
Parameter name
T323S wch
Switch of T323 broadcasting

UE sending message signaling c onnection release
T323
4.4.1.1
indication (with cause )in this interval
External Utran Cell Information

IurDcHsdsSuptInd
Dual-Cell HS-DS CH Support Indication
SndS vrCelID
Possible Secondary Serving Cell ID
4.4.2
4.4.2.1
T323Swch
OMC Path
Management-> RNC
NE->RNC
Radio
Resource
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-> RNC
NE->RNC
Radio
Resource
Management-> Modify Advanced Parameter-> UE Times and Constants Information

134
This parameter indicates the interval of reporting signaling connection release indication
(with cause ).
4.4.2.3
Possible Secondary Serving Cell ID

OMC Path
Management->
External
Management-> RNC
UTRAN
Cell->
NE->RNC
External
UTRA N
Radio
Cell
Resource
XXX
->Global
Else->Possible Secondary Serving Cell ID

This parameter describes the Possible Secondary Serving Cell ID for the neighbor cell
over Iur.
4.5
UE Traffic Volume Measurement Related

Parameters
4.5.1
Parameter List
4.5.1.1
UE traffic volume measurement relationship

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

TrigTime[MA X_UE _TRV_MEAS_EVENT]
Time to Trigger
PendingTime[MA X_UE_TRV_MEAS_EVENT]
Pending Time after Trigger
ThoughThres [MA X_UE_TRV_MEAS_EVENT]
AverageTime
Throughput
Threshold
of
E vent
4A/4B for E-DCH

Time Interval for Taking an A verage
or a Variance
MeasRptTrMod
Measurement Report Transfer Mode
MeasQuantity
Measurement Quantity
RptRlcBufInd
RLC Buffer Payload for Each RB
RptRlcA veInd
RptRlcVarInd
RptCrt
Tx InterCfgP re[MA X_UE_TRV_MEAS_EVENT]
Tx Interruption[MA X_UE_TRV_MEAS_EVE NT]
Average of RLC Buffer P ayload for

Each RB
Variance of RLC Buffer Payload for
Each RB
Report Criteria
Tx
After
Trigger
Configuration Tag
Tx Interruption Aft er Trigger
UE
Drbc DchUePrd
Interruption
Traffic
Volume
P eriod
Measurement Configuration Number

for DCH
UE
Drbc RachUeP rd
Traffic
Volume
P eriod
Measurement Configuration Number

for RACH
Measobj
Transport Channel Type
PrdRptAmount
Amount
of
Reporting in P eriod
136
Report Criterial
Reporting Interval in Period Report
PrdRptInterval
Criteria
Function
UeTrvMCfgNote
4.5.1.2
of
Configuration
Parameters
UE traffic volume measurement relationship in cells

Abbreviated name
Drbc DchUeE vt
Drbc DchUp
Drbc RachUeE vt
DrbcFachUp
DrbcS HsUp
Parameter name
UE
Traffic
Volume
E vent
Measurement
Configuration Number for DCH

UP Traffic Volume Measurement Configuration
Number for DCH
UE
Traffic
Volume
E vent
Measurement
Configuration Number for RA CH

Number for FACH
Number for Streaming Class on HS-DSCH
Drbc IBHs Up
Number for Int eractive and Background Class

on HS -DS CH
DrbcE DchUpThpt
ETtiUpThpt
Drbc CFachHsUp
Drbc CFachE DchUp
UP Traffic Volume Measurement Configration

Number for E-DCH
E-DCH
UP
Throughput
Measurement
Configuration Number for E-TTI Switching

Number for HS-DS CH in CELL_FA CH
Number for E-DCH in CELL_FACH
4.5.2
4.5.2.1
UE Traffic Volume Measurement Configuration Index

OMC Path
137
Path: View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Modify Advanced Parameter -> UE Traffic Volume Measurement
Configuration-> UE Traffic Volume Meas urement 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.
138
Since there are two kinds of measurement e vents 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 4A/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 t he traffic volume measurement value is greater than t he threshold of event 4A, a
report of event 4A will be triggered; if the t raffic volume measurement value is smaller
than the threshold of event 4B, a report of event 4B will be tri ggered.
4.5.2.5
Traffic Volume Threshold of Event 4A/4B for DCH of 8 kbps

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Traffic Volume Threshold of Event 4 A/4B for DCH of 8 kbps(bytes)

This parameter gives a specific value (in bytes) of the absolute threshold measurement
based on the different meas urements of 4A and 4B events for 8 Kbps traffic.
If t he traffic measurement value is higher t han 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.
139
4.5.2.6

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Traffic Volume Threshold of Event 4 A/4B for DCH of 16 kbps(bytes)

triggered.
4.5.2.7

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurem ent
Configuration-> Traffic Volume Tthreshold of Event 4A/4B for DCH of 32 kbps

triggered.
4.5.2.8

OMC Path
140
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement

triggered.
4.5.2.9

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement
triggered.
4.5.2.10

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Traffic Volume Tthreshold of Event 4A /4B for DCH of 256 kbps
141
triggered.
4.5.2.11

OMC Path
Path:
View->Configuration
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE ->RNC
Traffic
Radio
Volumn
Resource
Measurement
This parameter gives a specific value (in bytes) of the absolut e threshold measurement
triggered; if the measurement value is lower than the 4B event thr eshold, the 4B event is
triggered.
4.5.2.12
Time to Trigger
OMC Path
Configuration -> Time to Trigger
Parameter Confi guration
This parameter indicates the time difference bet ween having detected the event
generation and reporting the event. Only when the event generation is detected and still
142
meets all requirements of event triggering aft er Time to trigger, the event can be triggered
and reported.
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
4.5.2.13
will be decreased.
Pending Time after Trigger

OMC Path
Configuration -> Pending Time After 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 same event is triggered in a certain
period. Vice vers a.
4.5.2.14
UE Traffic Volume Event Measurement Configuration Number for DCH

OMC Path
Management -> Utran Cell -> Utran Cell XXX -> Modify Advanced Parameter -> 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-> RNC
NE->RNC
Radio
Resource
143
Management-> Utran Cell->Ut ran Cell XXX->Modify Advanced Parameter-> 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
Management-> RNC
NE->RNC
Radio
Resource

Volume Measurement Configuration Information In A Cell>UP Traffic Volume
Measurement Configration Number for DCH
This parameter indicates the downlink UP traffic
volume measurement 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.
4.5.2.16
UE Traffic Volume Event Measurement Configuration Number for RACH

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

Volume Measurement Configuration Information In A Cell> UE Traffic Volume E vent
Measurement Configration Number for RACH
This parameter indic ates the UE traffic volume measurement event configuration number
for RACH in the cell. According to this configuration number, you can a corresponding set
of traffic volume measurement parameters in RNC radio parameters.
144
4.5.2.17
UP Traffic Volume Measurement Configuration Number for FACH

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

Measurement Configration Number for FACH
This parameter indicates the UP traffic volume measurement event configuration number
for FACH in the cell. According to this configuration number, you can a corresponding set
of traffic volume measurement parameters in RNC radio parameters.
4.5.2.18
UP Traffic Volume Measurement Configuration Number for Streaming

Class on HS-DSCH
OMC Path
Management-> RNC
NE->RNC
Radio
Resource

Measurement Configration Number for Streaming Class on HS -DS CH
This parameter indicates the UP traffic volume meas urement event configuration number
for streaming service on the HS in the cell. According to this configuration number, you
can a corresponding set of traffic volume measurement parameters in RNC radio
parameters.
145
4.5.2.19
UP Traffic Volume Measurement Configuration Number for Interactive and

Background Class on HS-DSCH
OMC Path
Management-> RNC
NE->RNC
Radio
Resource

Volume Measurement Configuration
Information In A Cell>UP Traffic Volume
Measurement Configration Number for Int eractive and Background Class on HS -DSCH
This parameter indicates the UP traffic volume measurement event configuration number
for I/B service on the HS in the cell. According to this configuration number, you can a
4.5.2.20
UP Traffic Volume Measurement Configration Number for E-DCH

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

Measurement Configration Number for E-DCH
This parameter indicates the UP throughput measurement event configuration number
for the E DCH in the cell. According to this configuration number, you can a
4.5.2.21
E-DCH UP Throughput Measurement Configuration Number for E-TTI

Switching
OMC Path
Management-> RNC
NE->RNC
Radio
Resource
146
Volume Measurement
This parameter indicates the user plane throughput measurement configuration number
for E-DCH, used for E-TTI S witching. According to this configuration number, you can a
4.5.2.22
UP Traffic Volume Measurement Configuration Number for HS-DSCH in

CELL_FACH
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> UltranCell-> UltranCellXXX->Modify Advanced Parameter->UE Traffic

Volume Measurement Configuration Information In A Cell-> UP Traffic Volume
Measurement Configuration Number for HS -DS CH in CELL_FACH
This parameter indicates the us er plane traffic volume measurement configuration
number for HS-DSCH in CELL_FA CH, used for indexing a set of paramet ers configured
for user plane traffic volume event measurement for HS-DSCH in CELL_FACH.
4.5.2.23
UP Traffic Volume Measurement Configuration Number for E-DCH in

CELL_FACH
OMC Path
Path:
View->Configuration
Management-> RNC
NE ->RNC
Radio
Resource
Management-> UltranCell-> UltranCellXXX->Modify Advanced Parameter->UE Traffic

Volume Measurement Configuration Information In A Cell-> UP Traffic Volume
Measurement Configuration Number for E-DCH in CE LL_FA CH
This parameter indicates the us er plane traffic volume measurement configuration
number for E-DCH in CELL_FACH, used for indexing a set of parameters configured for
user plane traffic volume event measurement for E-DCH in CE LL_FACH.
147
4.5.2.24
Throughput Threshold of Event 4A/4B for E-DCH

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Throughput Threshold of E vent 4A/4B for E-DCH(k bps)

This parameter indicates the reporting threshold 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 t han t he
threshold
of
event
4B,
report
of
4B
event
will
be
triggered.Where
MA X_UE_TRV_MEAS_EVE NT is the maximum number of UE throughput measurement

event, which equals to 2.
The default value is [1500,700]kbps,
4.5.2.25
Time Interval for Taking an Average or a Variance

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
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.26

OMC Path
148
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Measurement Report Transfer Mode

This parameter indicates the RLC mode of the traffic volume measurement report. If t he
value is AM RLC, RNC can request UE for ret ransmission aft er 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 those less important in
UM mode (to reduce the traffic volume of the measur ement report and increase t he
system capacity).
The default value is AM RLC
4.5.2.27
Measurement Quantity
OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Measurement Quantity

This parameter indicat es the measurement quantity of the 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 is RLC buffer payload
4.5.2.28
RLC Buffer Payload for Each RB

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> RLC Buffer Payload for Each RB
149
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.29
Average of RLC Buffer Payload for Each RB

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volume
Resource
Measurement
Configuration-> A verage of RLC Buffer Payload for Eac h RB

This parameter indicates whet her the report of A verage of RLC buffer payload for eac h
radio bear is requested or not.
The default value is False
4.5.2.30
Variance of RLC Buffer Payload for Each RB

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Variance of RLC Buffer Payload for Eac h 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
150
4.5.2.31
Report Criteria
OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
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 RACH): Periodical
Reporting Criteria
4 (UE Traffic Volume E vent Measurement Configuration Number for RA CH): E vent
Reporting Criteria
5 (UP Traffic Volume Measurement Configuration Number for FACH): 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 Measurement 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): Event Reporting
151
Criteria
10 (E-DCH UP Throughput Measurement Configuration Number for E-TTI Switching):
E vent Reporting Crit eria
4.5.2.32
Tx Interruption After Trigger Configuration Tag

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Tx Interruption Aft er Trigger Configuration Tag

This parameter indicates whether Tx interruption after trigger is configured or not.Where
MA X_UE_TRV_MEAS_EVE NT is
the maximum
number o f UE
traffic
volume
measurement event, which equals to 2.

The default value for event [4a 4b] is [False, False]
4.5.2.33
Tx Interruption After Trigger

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Tx Interruption Aft er Trigger(ms)

This parameter indicates whether Tx interruption aft er trigger is configured or not.
Where MA X_UE_TRV_MEAS_EVE NT 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
152
4.5.2.34
UE Traffic Volume Period Measurement Configuration Number for DCH

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
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 t raffic volume
periodic measurement for DCH.
The default value is 0
Management-> RNC
NE->RNC
Radio
Resource

Volume Measurement Configuration Information In A Cell> UE Traffic Volume P eriod
Measurement Configuration Number for DCH
4.5.2.35
UE Traffic Volume Period Measurement Configuration Number for RACH

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> UE Traffic Volume Period Measurement Configuration Number for

RACH
This parameter indicates the UE traffic volume periodic measurement configuration
number for RA CH, used for indexing a set of paramet ers configured for UE traffic volume
periodic measurement for RACH.
The default value is 3
Management-> RNC
NE->RNC
Radio
Resource
153

Volume Measurement Configuration Information In A Cell> UE Traffic Volume P eriod
Measurement Configuration Number for RA CH
4.5.2.36
Transport Channel Type

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter-> UE
NE->RNC
Traffic
Radio
Volumn
Resource
Measurement
Configuration-> Transport Channel Type

This parameter indicates which type of transport channel this set of traffc volume
measurement parameters 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
154
4.5.2.37
Amount of Reporting in Period Report Criteria

OMC Path
Management->Modify
Management-> RNC
NE->RNC
UE
Traffic
Radio
Resource
Volumn Measurement
Configuration -> Amount of Reporting in Period Report Crit erial

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.38
Reporting Interval in Period Report Criteria

OMC Path
Management->Modify
Management-> RNC
NE->RNC
UE
Traffic
Radio
Resource
Volumn Measurement
Configuration -> 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): 8000ms
4.5.2.39
Function of Configuration Parameters

OMC Path
155
Management->Modify
Management-> RNC
NE->RNC
UE
Traffic
Radio
Resource
Volumn Measurement
Configuration -> Function of Configuration Paramet ers

This parameter indicates the purpose and functions of the set of traffic volume
measurement configuration paramet ers.
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 RACH
4: UE Traffic Volume E vent Measurement Configuration Number for RA CH
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 Configuration Number for Interactive and
Background Class on HS-DS CH
9: UPTraffic Volume Measurement Configuration Number for E-DCH
10: E-DCH UP Throughput Measurement Configuration Number for E-TTI Switching
4.6
UE Internal TxP Measurement Related Parameters
4.6.1
Parameter List
UE Internal Measurement Relationship
156
Abbreviated name
UE
UeIntMCfgNo
Internal
Measurement
Configuration Index
Function
UeIntMCfgNote
of
Configuration
Parameters
Measurement
MeasRptTrMod
Report
Trans fer
Mode
FilterCoeff
Filter coefficient
UE
MeasQuantity
Internal
Measurement
Quantity
UE Transmitted Power Report
Rpt TxPwrInd
Indicator
RptCrt
Report Criteria
Maximum E vent Number of UE
MeasE vt Num
Internal Measurement
MeaE vt Id[MA X_UE_INTER_MEAS_EVENT]
UE Internal Measurement E vent

Identity
TrigTime[MA X_UE _INTE R_MEAS_EVE NT]
Time to Trigger
TxPowerThres[MA X_UE _INTE R_MEAS_EVE NT]
UE Transmitted Power Threshold

UE
PsEvtMeas TP1
4.6.1.1
Parameter name
Transmitted Power E vent
Report ConfigurationIndex for PS
UE Internal Measurement Configuration Index

OMC Path
Management-> RNC
NE->RNC
Radio
Resource
Management->Modify Advanced Parameter-> UE Int ernal Measurement Configuration

-> UE Internal Measurement Configuration Index
This parameter indicates the UE internal measurement configuration index, which is used to index
different parameter configuration sets for UE internal measurement, because there are s everal
different sets of measurement values for the same set of parameters according to specific
measurement purpose, measurement quantity, etc.
157
4.6.1.2

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> Function of Configuration Paramet ers
This parameter indicates the function of configuration parameters corresponding to the UE internal
measurement configuration index.
4.6.1.3

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> Measurement Report Transfer Mode
This parameter indicates the RLC mode of the UE internal measurement report.
4.6.1.4
Filter coefficient
OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> Filter coefficient
This parameter indicates the filtering factor that UE performs the L3 filtering on the measurement
results of the internal measurement.
4.6.1.5
UE Internal Measurement Quantity

OMC Path
158
Management-> RNC
NE->RNC
Radio
Resource

-> UE Internal Measurement Quantity
This parameter indicates the measurement quantity of the UE internal measu rement.
4.6.1.6
UE Transmitted Power Report Indicator

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> UE Transmitted Power Report Indicat or
This parameter indicates whether the UE transmitted power report is requested or not.
4.6.1.7
Report Criteria
OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> Report Criteria
This parameter indicates the report criteria for UE internal measurement report.
4.6.1.8
Maximum Event Number of UE Internal Measurement

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> Maximum E vent Number of UE Internal Measurement
159
This parameter indicates the maximum event number of UE internal measurement.
4.6.1.9
UE Internal Measurement Event Identity

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> UE Internal Measurement E vent Identity
This parameter indicates the UE int ernal meas urement event identity
4.6.1.10
Time to Trigger
OMC Path
Management-> RNC
NE->RNC
Radio
Resource

->Time to Trigger
This parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
4.6.1.11
UE Transmitted Power Threshold

OMC Path
Management-> RNC
NE->RNC
Radio
Resource

-> UE Transmitted Power Threshold
This parameter indicates the UE transmitted power threshold in event 6a/6b.
160
4.6.1.12
UE Transmitted Power Event Report ConfigurationIndex for PS

OMC Path
Management-> RNC
NE->RNC
Radio
Resource
Management-> UtranCell-> UtranCellxxxx->Modify Advanced P arameter-> UE Internal

Measurement Configuration -> UE Transmitted Power E vent Report ConfigurationIndex
1 for PS
This parameter indicates the UE transmitted power event report configuration index for
PS.
4.7
Node B Dedicated TCP Measurement Related

Parameters
4.7.1
Parameter List
Node B Dedicated Measurement Relationship
Abbreviated name
Parameter name
NbDMCfgNote
Function of Configuration Paramet ers

Downlink Rate Level Threshold used
DlRateLevel[2]
for D-TCP Meas urement in DASF -PS

Measurement Threshold of E vent A/B
E vtAbTcpThrd[3]
for Transmitted Code Power
RptPrd
4.7.1.1
Report Periodicity Value

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter->
NE->RNC
Nodeb
Radio
Dedic ated
Resource
Measurement
Configuration -> Function of Configuration Paramet ers

161
This parameter indicates the function, purpose etc. of the dedicat ed measurement
parameters indicated by the configuration index.
4.7.1.2
Downlink Rate Level Threshold used for D-TCP Measurement in DASF-PS

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter->
NE->RNC
Nodeb
Radio
Dedic ated
Resource
Measurement
Configuration -> Downlink Rat e Level Threshold used for D -TCP Measurement in
DASF-PS
This parameter indicates the downlink rate level threshold, In D-TCP based PS DRBC,
the thresholds of D-TCP measurement event A/B are got based on the rate level of the
service.
4.7.1.3
Measurement Threshold of Event A/B for Transmitted Code Power

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter->
NE->RNC
Nodeb
Radio
Dedic ated
Resource
Measurement
Configuration -> Measurement Thres hold of E vent A/B for Transmitted Code Power
This parameter indicates the power offset of the DP CH maximum DL power, which
defines which threshold that shall trigger event A, B for transmitted carrier power
measurement.
4.7.1.4
Report Periodicity Value

OMC Path
Management->Modify
Management-> RNC
Advanced
Parameter->
NE->RNC
Nodeb
Radio
Dedic ated
Resource
Measurement
Configuration-> Report Periodicity Value
162
This parameter indicates the frequency of measurement report transmitted by Node B.
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
C310404206
C310404207
C310404208
C310404209
C310404210
C310404211
Number of Success DCH Uplink DRBC,drop rate to 8k
C310404212
C310404213
C310404214
163
C310404215
C310404216
C310404217
Number of Success DCH Downlink DRBC,ris e rate to 32k
C310404218
C310404219
C310404220
C310404221
C310404222
Number of Success DCH Downlink DRBC,drop rate to 8k
C310404223
C310404224
C310404225
C310404226
C310414096
C310414097
C310414098
C310414099
C310414100
C310414101
C310414102
C310414103
C310414104
C310414105
C310414106
C310414107
Number of intra frequency Transport Channel Changing

attempt, HS-DSCH to DCH
attempt, DCH to HS-DSCH
attempt, FACH to DCH
attempt, DCH to FACH
attempt, FACH
to PCH

attempt, PCH to FA CH
attempt, HS-DSCH to FACH
Number of intra
frequency Transport Channel Changing
attempt, FACH to HS-DSCH

attempt, E-DCH to DCH
attempt, DCH to E-DCH
attempt, E-DCH to RA CH
164
attempt, RACH to E-DCH

C310414108
C310414109
C310414110
C310414111
C310414112
C310414113
C310414114
C310414115
C310414116
C310414117
C310414118
C310414119
Number of intra frequency Transport Channel successful

Changing attempt, HS-DS CH to DCH
Changing attempt, DCH to HS-DSCH
Changing attempt, FACH to DCH
Changing attempt, DCH to FACH
Changing attempt, FACH
to PCH

Changing attempt, PCH to FACH
Changing attempt, HS-DS CH to FA CH
Changing attempt, FACH to HS -DS CH
Changing attempt, E-DCH to DCH
Changing attempt, DCH to E-DCH
Changing attempt, E-DCH to RA CH
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
C310405729
C310405730
C310405731
C310405732
Number of attempted Decreasing Rate on Uplink DCH,

Triggered by UE TxP
Number of attempted Decreasing Rate on Uplink DCH,
Triggered by Traffic Volume
Number of attempted Decreasing Rate on Downlink DCH,
Triggered by D-TCP
Number of attempted Decreasing Rate on Downlink DCH,
165

C310405733
C310405734
C310405735
C310405736
C310405737
C310416901
C310416902
C310416903
C310416904
C310416905
C310416906
C310416907
C310416908
C310414130
C310414131
C310414132
C310414133
C310414134
Number of success Decreasing Rat e on Uplink DCH, Triggered

by UE TxP
Number of success Decreasing Rat e on Uplink DCH, Triggered
by Traffic Volume
Number of success Decreasing Rate on Downlink DCH,
Triggered by D-TCP
Number of success Decreasing Rate on Downlink DCH,
Number of Users of Uplink and Downlink Reconfiguration by
one step
Changing attempt, DCH
to PCH

Changing attempt, PCH to DCH
Changing attempt, HS-DS CH
to PCH

Changing attempt, PCH to HS-DS CH
to PCH

Changing attempt, PCH to DCH
Changing attempt, HS-DS CH
to PCH

Changing attempt, PCH to HS-DS CH
Number of inter frequency Transport Channel Changing
attempt, HS-DSCH to DCH
attempt, DCH to HS-DSCH
attempt, FACH to DCH
attempt, DCH to FACH
166
attempt, FACH
C310414135
C310414136
C310414137
C310414138
C310414139
C310414140
C310414141
C310416909
C310416910
C310416911
C310416912
C310414142
C310414143
C310414144
C310414145
C310414146
C310414147
C310414148
to PCH

attempt, PCH to FA CH
attempt, HS-DSCH to FACH
attempt, FACH to HS-DSCH
attempt, E-DCH to DCH
attempt, DCH to E-DCH
attempt, E-DCH to RA CH
attempt, RACH to E-DCH
attempt, DCH
to PCH

attempt, PCH to DCH
attempt, HS-DSCH
to PCH

attempt, PCH to HS -DS CH
Number of inter frequency Transport Channel successful
Changing attempt, HS-DS CH to DCH
Changing attempt, DCH to HS-DSCH
Changing attempt, FACH to DCH
Changing attempt, DCH to FACH
Changing attempt, FACH
to PCH

Changing attempt, PCH to FACH
167
Changing attempt, HS-DS CH to FA CH

C310414149
C310414150
C310414151
C310414152
C310414153
C310416913
5.2

Changing attempt, FACH to HS -DS CH
Changing attempt, E-DCH to DCH
Changing attempt, DCH to E-DCH
Changing attempt, E-DCH to RA CH
Changing attempt, RACH to E-DCH
Number of inter frequency Transport
Channel successful
to PCH
Alarm List
This feat ure has no related alarm.
Glossary
B
Background
BO
Buffer Occupancy
Conversation
CPC
CN
Continuous Packet Connectivity

Core Network
DCCH
Dedic ated Control Channel
DCH
Dedic ated Channel
DL
DRB C
Downlink
Dynamic Radio Bearer Cont rol
168
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
Interactive
IMS
IP Multimedia Subsystem
MAC
Media Access Cont rol
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
169
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
S-CCPCH
Streaming
Secondary Common Control Physical Channel
SF
Spreading Factor
SIP
Session Initiation Protoc ol
TTI
Transmission Time Interval
TF
Transport Format
TFCS
Transport 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
170

ZTE UMTS DRBC Algorithm Feature Guide V6!1!201204

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ZTE UMTS DRBC Algorithm Feature Guide V6!1!201204

Enviado por

Direitos autorais:

Formatos disponíveis

DRBC

DRBC Algorithm Feature Guide

DRBC Algorithm Feature Guide

(3) Add chapter 3.5 Enhanced FACH

Dynamic Channel Adjustment.

for Concurrence Service with CS+PS

DRBC F/P->D Performance

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

Function Attribute ................................................................................................. 5

Technical Description ......................................................................................... 12

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

R8 Fast Dormancy ................................................................................................. 81

Counter And Alarm ............................................................................................ 163

Glossary ............................................................................................................. 168

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

Signaling Channel Alloc ation

Initial Service Channel Allocation

Conc urrent Service Channel Allocation

Initial Access Rate Allocation for DCH

DL DCH/ UL DCH -> DL DCH/UL DCH

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

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

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

Dynamic Channel Type Transfer for R99 Service

Interactive servic e and Background Servic e may use FACH/RA CH or DCH.

Dynamical DCH rat e adjustment.

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

DCH rate downgrade is an alternative method to decrease the system load

If the practical rate of PS Interactive S ervice or PS Background S ervice below

If the practical rate is zero, radio resource can be released temporarily. UE of

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

Dynamic Channel Type Transfer for HSDPA Service

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

Dynamic Channel Type Transfer for HSUPA Service

If the traffic volume is high, the channel switching from RA CH or DCH to

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

RAB Negotiation & Re-negotiation

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

27.2Kbps High Speed Signaling RB

Dynamic Channel Type Transfer for R99 Service

Introduction to Service Types

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

Initial Channel Allocation

Signaling Channel Allocation

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide

ZTE Confidential Proprietary

DRBC Algorithm Feature Guide