ZTE UMTS DRBC Algorithm Feature Guide - V8.5 - 201312

DRBC Algorithm Feature
Guide
WCDMA RAN
DRBC Algorithm Feature Guide

Version Date Author Reviewer Revision History
1. Updated 3.1.2.1 Signaling Channel

Allocation.
2. Updated 3.7.7 CS Experience
Improvement for Concurrence Service
with CS+PS.
3. Added 3.1.3.11 Channel Selection
Wang
V8.0 2012-12-12 Liu Min Policy for UE from PCH State to Other
Chengwei
State.
4. Added 3.7.12 Penalty Policy for UE that
cannot Camp on PCH State.
5. Added 3.7.13 Uplink Access Strategy
for Bad E-DCH Coverage.
6. Updated parameters OMCR paths.
1. Updated 3.6.1, R8 Fast Dormancy.

2. Updated 3.7.7 Voice Service
Optimization for Multi-RAB.
3. Added 3.7.8 UE PCH Compatibility
Strategy.
Zhang
V8.5 2013-10-26 Liu Min 4. Updated parameters OMCR paths.
Haiyan
5. Added the following parameters and
related descriptions: dedMeasType,
rptPrdUnit, rptType, nbDedMeasProfile,
profileId, nbDMCfgNo, and
measFilterCoeff.
2013 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 subject to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attributes.............................................................................................. 6
2 Overview ............................................................................................................ 6
2.1 ZWF21-04-004 Dynamic Radio Bearer Control .................................................... 8
2.2 ZWF23-04-004 Dynamic Channel Type Transfer for HSDPA Service ................ 10
2.3 ZWF25-04-005 Dynamic Channel Type Transfer for HSUPA Service ................ 11
2.4 ZWF21-01-020 27.2Kbps High-Speed Signaling RB .......................................... 12
2.5 ZWF21-01-027 Fast Dormancy .......................................................................... 12
2.6 ZWF21-05-016 Video Call Prohibited in Specific Area ....................................... 13
2.7 ZWF27-03-002 Application Awared DRBC Enhancement .................................. 13
2.8 ZWF21-05-026 Voice Service Optimization for Multi-RAB.................................. 13
2.9 ZWF21-04-014 Adaptive Radio Bearer .............................................................. 13
3 Technical Descriptions ................................................................................... 14

3.1 Dynamic Channel Type Transfer for R99 Service .............................................. 14
3.1.1 Introduction to Service Types ............................................................................. 14
3.1.2 Initial Channel Allocation .................................................................................... 14
3.1.3 Channel Switching ............................................................................................. 20
3.1.4 Related Measurement ........................................................................................ 39
3.2 Dynamic Channel Type Transfer for HSDPA Service ......................................... 51
3.2.1 Signaling Channel Allocation ............................................................................. 51
3.2.2 Initial Service Channel Allocation ....................................................................... 52
3.3 Dynamic Channel Type Transfer for HSUPA Service ......................................... 64
3.3.1 Signaling Channel Allocation ............................................................................. 64
3.4 Dual-Carrier Related Dynamic Channel Adjustment........................................... 80
3.4.2 Concurrent Service Channel Allocation .............................................................. 80
3.5 Enhanced FACH Dynamic Channel Adjustment ................................................ 81
3.5.1 DL Enhanced FACH Dynamic Channel Adjustment ........................................... 81
3.5.2 UL Enhanced FACH Dynamic Channel Adjustment ........................................... 84
3.5.3 Traffic Measurement .......................................................................................... 87
3.6 Fast Dormancy .................................................................................................. 87
3.6.1 R8 Fast Dormancy ............................................................................................. 87

3.6.2 Pre-R7 Fast Dormancy Suppressing .................................................................. 90

3.7 Other Description ............................................................................................... 92
3.7.1 Traffic Sub-class rate matching .......................................................................... 92
3.7.2 MBR Controlling in RNC .................................................................................... 95
3.7.3 Iub Transmission Bandwidth Limitation Strategy ................................................ 96
3.7.4 Be compatible with the IPHONE which does not meet encryption protocol ........ 97
3.7.5 MaxBR of HSDPA on Iur Interface ..................................................................... 97
3.7.6 Switching Timers Based on UE Capabilities....................................................... 98
3.7.7 Voice Service Optimization for Multi-RAB .......................................................... 99
3.7.8 UE PCH Compatibility Strategy ........................................................................ 101
3.7.9 DRBC F/P->D Performance Optimization ........................................................ 102
3.7.10 CELL_PCH Supporting .................................................................................... 103
3.7.11 Video Call Prohibited in Specific Area .............................................................. 103
3.7.12 Penalty Policy for UE that cannot Camp on PCH State .................................... 104
3.8 Uplink Access Strategy for Bad E-DCH Coverage ........................................... 104
3.8.1 Initial Channel Allocation Based on Channel Quality ........................................ 104
3.8.2 Switching from DL HS-DSCH/UL E-DCH to DL HS-DSCH /UL DCH Triggered
by UE Transmitted Power and Throughput Measurement ................................ 105
3.8.3 UE Transmitted Power Measurement for E-DCH to DCH................................. 105
3.8.4 Throughput Measurement for E-DCH to DCH .................................................. 106
3.9 Application Aware DRBC Enhancement .......................................................... 107
3.9.1 Analysis of DPI Service Feature....................................................................... 107
3.10 DRBC Strategy for QChat ................................................................................ 108
3.10.1 Initial Channel Allocation .................................................................................. 108
3.10.2 Channel Switch ................................................................................................ 109
3.10.3 Strategy for Qchat UE when its non-Qchat RB2 service has no traffic ............. 111
3.11 Whether to decide Event 1F when service is established on HSPA ................. 112
4 Parameters and Configurations ................................................................... 112

4.1 DRBC Related Parameters .............................................................................. 112
4.1.1 Parameter List ................................................................................................. 112
4.1.2 Parameter Configurations ................................................................................ 118
4.2 UE Traffic Volume Measurement Related Parameters ..................................... 161
4.2.1 UE Traffic Volume Event Measurement Configuration Object for RACH .......... 161
4.2.2 UE Traffic Volume Period Measurement Configuration Object for RACH ......... 167
4.2.3 UP Traffic Volume Event Measurement Configuration Object for FACH .......... 170
4.2.4 UE Traffic Volume Event Measurement Configuration Object for DCH ............ 175
4.2.5 UE Traffic Volume Period Measurement Configuration Object for DCH ........... 184
4.2.6 UP Traffic Volume Event Measurement Configuration Object ID for DCH ........ 187
4.2.7 UP Traffic Volume Measurement Configuration for Interactive and Background
Class on HS-DSCH Object .............................................................................. 196

4.2.8 UP Traffic Volume Measurement Configuration Number for Streaming Class on

HS-DSCH Object ............................................................................................. 201
4.2.9 UP Traffic Volume Measurement Configuration Object for E-DCH ................... 207
4.2.10 UP Throughput Event Measurement Configuration for E-TTI Switching Object 212
4.2.11 UP Traffic Volume Measurement Configuration for HS-DSCH in CELL_FACH
Object .............................................................................................................. 217
4.2.12 UP Traffic Volume Measurement Configuration for E-DCH in CELL_FACH
Object ID.......................................................................................................... 222
4.2.13 E-DCH Throughput Measurement Configuration Object for HS-DSCH/E-DCH to
HS-DSCH/DCH Switching................................................................................ 227
4.3 UE Internal TxP Measurement Related Parameters......................................... 233
4.3.1 UE Transmitted Power Event Measurement Configuration for PS Object ........ 233
4.3.2 UE Transmitted Power Event Report Object for Power Limitation Judgment.... 236
4.4 Node B Dedicated TCP Measurement Related Parameters ............................. 239
4.4.1 Parameter List ................................................................................................. 239
4.5 Dynamic Radio Bearer Control Information of DPI Service Object ................... 244
4.5.1 Parameter List ................................................................................................. 244
4.5.2 Parameter Configurations ................................................................................ 244
5 Counter List ................................................................................................... 244
6 Glossary ......................................................................................................... 250

FIGURES
Figure 2-1 State Transitions ................................................................................................ 7

Figure 3-1 R99 Channel Switching .......................................................................................20
Figure 3-2 Event Triggering of Traffic Measurement ..........................................................41
Figure 3-3 Rate Adjustment Triggered by Traffic ................................................................43
Figure 3-4 HSDPA Channel Switching ...............................................................................55
Figure 3-5 Event 1E in Channel Quality Measurement.......................................................61
Figure 3-6 Event 1F in Channel Quality Measurement .......................................................62
Figure 3-7 HSUPA Channel Switching ...............................................................................69
Figure 3-8 Channel switch with Pre-R7 fast dormancy .......................................................88
Figure 3-9 Channel switch with R8 fast dormancy .............................................................89

1 Feature Attributes
System version: [RNC V3.12.10/V4.12.10, Node B V4.12.10]
Attribute: [Mandatory + Optional]
Involved NEs:
UE Node B RNC MSCS MGW SGSN GGSN HLR
- - - - -
Note:
*-: Not involved.
*: Involved.
Dependency: [None]
Mutual exclusion: [None]
Note: [None]
2 Overview
Dynamic Radio Bearer Control (DRBC) is to allocate resources reasonably according to
subscribers requirements and the system resource utilization to make full use of the
radio bandwidth. ZTE RAN DRBC provides the following functions:
Initial Channel Allocation
During the channel setup, the DRBC allocates proper channels and rates for the services
according to service requirements and system resource utilization status, including:
Signaling Channel Allocation
Initial Service Channel Allocation
Concurrent Service Channel Allocation
Initial Access Rate Allocation for DCH

Channel Switching
The DRBC selects appropriate transport channels according to the actual rates of PS
services. If the PS rate changes, the channel type changes accordingly. The system
monitors the actual rate of PS services. If the actual data flow is smaller than the
allocated bandwidth, the system decreases the configured 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 service uses DL
DCH/UL DCH; the streaming service uses CELL_DCH, and the interactive and
background services use CELL_FACH or CELL_DCH. The state transition currently
supported by the system is shown in the following figure:
Figure 2-1 State Transitions
Connected Mode
CELL_DCH
DL DCH/ UL DCH -> DL DCH/UL DCH
UL/DL Decrease or Increase Rate
DL HS-DSCH/ UL DCH <-> DL DCH/UL DCH

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

E-DCH, DL HS-DSCH/UL DCH, and DL DCH/UL DCH. The RAN determines
different channel types for services based on different support capabilities of Node
B and UE, and service features. Channel switching could be performed between
different channel types. The rates of DL DCH and UL DCH can be adjusted
dynamically.

The CELL_FACH service can use DL FACH/UL RACH.
2.1 ZWF21-04-004 Dynamic Radio Bearer Control
The R99 DRBC 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 DRBC allocates radio channel and initial rate to the
service according to service requirements and system resource utilization status.
CS service and Streaming service can use DCH as a bearer. The DCH
channel parameters are set according to the required GBR.
Interactive service and Background Service may use FACH/RACH or DCH.
For PS services that use DCH as a bearer, its initial access rate can be set
according to configuration.
Dynamic DCH rate adjustment
DCH rate configuration should be consistent with the actual traffic rate. When
actual traffic volume drops, the DCH rate should be decreased accordingly.
Released resources can be used by other users. The DCH rate can be
increased when actual traffic volume gets high 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 bandwidth
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
signaling procedure so that the signaling messages on the Uu are 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 using this method, PS service subscribers obtain a
relatively higher data rate when UE is in the center of the cell, and obtain a
lower data rate when UE is in the cell edge. Thus, the coverage of PS services
is expanded. The call drop rate of high-rate services in the handover process
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 Service or PS Background Service falls

below the traffic volume threshold or if overload occurs in the cell, RAB will
switch to FACH/RACH from DCH, and the UE then enters the CELL FACH
state.
If the practical rate exceeds the traffic volume threshold of FACH/RACH, RAB
will switch to DCH, and the UE then enters the CELL DCH state.
If the practical rate is zero, radio resources can be released temporarily. The
UE in Cell FACH state or Cell DCH state can be switched to the URA PCH
state to save UEs battery power. If it is not configured in the PCH state, RRC
can be released.
When the UE in the URA_PCH state originates the cell update message due
to uplink or downlink data transmission requirements or for new service setup,
the system allocates the channels by the UE service type before the UE is
handed over to PCH in the process of initial service channel allocation.
If a UE has resided in the URA PCH state for period, the RRC will be released.
The ZTE RAN system supports the DRBC feature combined with other RRM policies
including Admission Control, Overload Control, and Congestion Control. Priorities of
users and services are considered to implement dynamic optimization configuration of
radio bandwidth.

2.2 ZWF23-04-004 Dynamic Channel Type Transfer for

HSDPA Service
After introducing HSDPA, the ZTE RAN system is able to select the bearer channel
among HS-DSCH, DCH or FACH for the service and configure radio parameters
according to service requirements and system resource utilization status.
ZTE RAN equipment supports dynamic channel switching between different channels in
order to satisfy service requirements and system resources in the following ways:
Save system resources by adjusting channel type dynamically according to I/B

real-time traffic volume:
When downlink traffic volume is too high, 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 system stability.
Ensure service quality by adjusting channel type according to channel quality.
When the UE in the HS-DSCH channel moves to the cell edge to trigger a 1F event,
it indicates that the channel quality is bad. The user can trigger the channel
switching from HS-DSCH to DCH.
Ensure the service continuity by adjusting channel type according to the target cell
for handover.
If the capability of the source cell and target cell is different in the handover process,
the channel switching between HS-DSCH and DCH will be triggered to guarantee

service continuity.
Downlink channel switching accompanies uplink channel switching: When the downlink
channel is FACH, the uplink channel is RACH; when the downlink channel is HS-DSCH,
the uplink channel can be DCH or E-DCH.
2.3 ZWF25-04-005 Dynamic Channel Type Transfer for

HSUPA Service
After introducing HSUPA, the ZTE RAN system is able to select the bearer channel
among E-DCH, DCH or RACH for the service and configure radio parameters according
to service requirements and system resource utilization status.
In order to accommodate the requirements of service and practical status of system

resources, the ZTE RAN system supports the following functions during channel
switching:
Dynamically adjust channel type to save system resources according to the

practical traffic volume of I/B services:
If the traffic volume is high, the channel switching from RACH or DCH to
E-DCH will be triggered.
If the traffic volume is low, the channel switching from E-DCH to RACH will be
triggered.
If there is 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 the 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 system stability.
Adjust channel type to guarantee the service quality according to channel quality
If a UE on E-DCH channel moves to the cell edge and triggers a 1F event, it

indicates that the quality of the 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 the target cell
If the capability of the source cell and target cell is different in the handover process,
the channel switching between E-DCH and DCH will be triggered to guarantee
service continuity.
The uplink channel switching accompanies the downlink channel switching: If the uplink
channel is RACH, the downlink channel is FACH. If the uplink channel is E-DCH,
generally, the downlink channel is HS-DSCH.
2.4 ZWF21-01-020 27.2Kbps High-Speed Signaling RB
This feature enables the system to use the 27.2 kbps Signaling Radio Bearer (SRB)
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 the OMC, ZTE RAN will employ 27.2kbps
SRB to speed up transferring the NAS signaling messages (including location update
message, authentication message, and call setup message) between 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 details of 27.2 kbps SRB, please refer to
3.1.2.1 Signaling Channel Allocation.
2.5 ZWF21-01-027 Fast Dormancy
This feature includes two functions: R8 Fast dormancy and Pre-R7 Fast dormancy
suppressing. The R8 Fast dormancy function can extend UE battery usage and reduce
the control plane signaling load. The Pre-R7 Fast dormancy suppressing function can
reduce the control plane signaling load for smart phones on the premises, which
guarantees user experience. For the details, please refer to 3.6 Fast dormancy.

2.6 ZWF21-05-016 Video Call Prohibited in Specific

Area
The UMTS network provides the video call service. In some areas with security
control or areas with privacy protected, the video call service is prohibited and it is
necessary to suspend the service in the network layer. This feature enables the
system to suspend the video call service for a specific cell.
2.7 ZWF27-03-002 Application Awared DRBC

Enhancement
ZTE RAN adopts this feature to optimize the radio resource usage and service
experience. After the DPI module recognizes the service type, ZTE RAN activates
different DRBC strategies for different services.
2.8 ZWF21-05-026 Voice Service Optimization for

Multi-RAB
This feature decreases the interference to voice service caused by the high bit-rate PS
service in Multi-RAB, and then reduces the voice quality degradation and improves the
service experience.
2.9 ZWF21-04-014 Adaptive Radio Bearer
Normally, to accelerate network access for a user, RAN uses the high-speed SRB, such
as 13.6kbps, to establish a signal radio bearer. However, comparing with the low-speed
SRB, the high-speed SRB consumes more downlink and uplink transmission power.
When a user is under poor coverage, the high-speed SRB establishment fails easily.
With the radio quality information in the first message of requesting access, ZTE RAN
uses the 3.4kbps SRB for users in weak coverage areas. For details, please refer to
3.1.2.1 Signaling Channel Allocation.

The high-speed AMR mode is used for voice calls to guarantee service experience of
users if the system resources are enough. However, in a poor coverage area, the
low-speed AMR mode does better in keeping the call stable. So, when the user is in a
weak coverage area, the low-speed AMR mode is used to establish the voice call. For
details, please refer to Classification of Dynamic AMR Adaptation in ZTE UMTS
AMR-NB & AMR-WB Feature Guide.
3 Technical Descriptions
3.1 Dynamic Channel Type Transfer for R99 Service
3.1.1 Introduction to Service Types
Because different types of services have different features, the services have different
requirements for the occupied channel resources during the channel allocation process.
Currently, the services can be categorized into four types: Conversation, Interactive,
Background, and Streaming.
The conversation and streaming services are real-time services, while interactive and
background services are not real-time services.
3.1.2 Initial Channel Allocation
3.1.2.1 Signaling Channel Allocation
The OMC provides various parameter options so that the signaling rate 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 to 0, the RNC sets the initial signaling to
forcibly use the DCH/DCH at 3.4kbit/s.

When a UE sends a connection setup request to the RNC, the RNC configures the
bidirectional DCH at 3.4 kbit/s for the UE to bear signaling.
forcibly use DCH/DCH at 13.6kbit/s.
bidirectional DCH at 13.6 kbit/s for the UE to bear signaling.
use common channel forcibly.
uplink RACH or downlink FACH channel for the UE to bear signaling.
choose the channel automatically, and sets DCH/DCH at 3.4kbit/s when the
dedicated channel is used.
When a UE sends a connection setup request to the RNC, the RNC automatically
selects the dedicated channel (3.4 kbit/s) or common channel based on the reason
for connection setup: if services are initiated immediately after the setup of the RRC
connection, the RNC will select DCH channel and configure bidirectional 3.4 kbit/s
bearer signaling; if there is only an LA update, instead of setting up services, which
should be completed after RRC connection, the RNC will select the common
channel to bear signaling.
choose channels automatically, and sets DCH/DCH at 13.6kbit/s, when the
dedicated channel is used
selects the dedicated channel (13.6 kbit/s) or common channel based on the
reason for connection setup: if services are initiated immediately after the setup of
the RRC connection, RNC will select DCH channel and configure bidirectional 13.6
kbit/s bear signaling; if there is only LA update, instead of setting up services, which
should be completed after RRC connection, RNC will select common channel to
bear signaling.

forcibly use DCH/DCH at 27.2kbit/s.
bidirectional 27.2 kbit/s DCH for the UE to bear signaling.
choose channel automatically, and sets DCH/DCH at 27.2kbit/s, when the
dedicated channel is used
When a UE sends a connection setup request to The RNC, the RNC automatically
selects the dedicated channel (27.2 kbit/s) or common channel based on the
reason for connection setup: if services are initiated immediately after the setup of
RRC connection, RNC will select DCH channel and reconfigure bidirectional 27.2
kbit/s bear signaling; if there is only LA update, instead of setting up services, which
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 the RNC, if both the UE and the
cell support F-DPCH, both FdpchSupInd and RncFdpchSupInd are 1, (or both
the UE and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd
are 1), both the UE and the cell support E-DCH, and SrbOnEdchSwch is on, and
the 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 the Cell_DCH state is used
selects the Cell_DCH state channel or Cell_FACH state channel based on the
reason for the connection setup, and HSPA is prior when Cell_DCH state is used.
When the RNC sets the initial signaling to choose channel automatically, the signaling
will be set on Cell_DCH state bearer in preference if the signaling is set due to the
following reasons: Originating Conversational Call, Originating Streaming Call,

Originating Interactive Call, Originating Background Call, Originating Subscribed Traffic

Call, Terminating Conversational Call, Terminating Streaming Call, Terminating
Interactive Call, Terminating Background Call, Emergency Call, Inter-RAT cell change
order, Call re-establishment, and MBMS ptp RB request; if the signaling is set due to
other reasons, it will be set on Cell_FACH state bearer.
The high-rate (13.6 kbit/s, 27.2 kbit/s) signaling bearer only exists in a separate signaling
process, and will be restored to the ordinary rate (3.4 kbit/s) after the service is set up.
The high-rate signaling can effectively speed up the signaling interaction during the UE
call setup and lower the call delay, but it occupies more radio resources than ordinary
rate signaling bearer. Using common channel for signaling, the 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,
ZTE recommends the configuration of high-rate signaling.
Note:
(1) 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 DchSig68Swch is on, it will substitute 3.4 kbit/s signaling with 6.8 kbit/s
signaling; otherwise, if DchSig68Swch is off, 3.4kbit/s signaling is used.
(2) If BadCovRrcSwch is 1:On, and if the poor coverage condition that the P-CPICH
Ec/N0 UE reported is no more than BadCovEcN0 or the P-CPICH RSCP UE reported is
no more than BadCovRscp is satisfied, the RRC connection will be setup with DCH 3.4
kbit/s rate; otherwise, the RRC connection will be setup in the above principle. That is,
the channel selection for the RRC connection is firstly decided by BadCovRrcSwch,
unless BadCovRrcSwch is off or BadCovRrcSwch is on but the above condition is not
satisfied, and then decided by InitRrcOnDch.
3.1.2.2 Initial Service Channel Allocation
For a RAB request of a service, the RNC chooses the initial channel for the service by
the service features (RAB parameters). The selection principles are:
The conversation and streaming services use DL DCH/UL DCH.

The interactive and background services can use DL DCH/UL DCH and DL
FACH/UL RACH.
Whether the DL DCH/UL DCH or DL FACH/UL RACH is used for interactive and
background services depends on the values of MaxBR in RAB allocation and Rfach and
Rrach. 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. Otherwise, the DL
FACH/UL RACH is chosen in preference. If FACH/RACH 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 a subscriber is in the CELL_FACH state, the system judges whether to perform

state transitions according to the new service type.
i. If the new service should be set up on the DL DCH/UL DCH channel according
to the channel allocation principles as for a single service, the UE should
switch from CELL_FACH state to CELL_DCH state, namely, 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.
ii. If the new service is set up on the DL FACH/UL RACH channel according to
the channel allocation principles as for a single service, the UE keeps working
in the CELL_FACH state, without impacting on the online services.
For concurrent CS and PS (S/I/B) services:
If the DRBC switch DrbcSwch is set to OFF, the DCH rate of the PS (S/I/B) services
is the minimum DRBC rate (max (highest rate level of DRBC, GBR), MaxBR). The
uplink and downlink DRBC rate levels are configured by

UlRateAdjLev[MAX_NUM_RATE_ADJUST] and
DlRateAdjLev[MAX_NUM_RATE_ADJUST] separately.
If the DRBC switch DrbcSwch is ON, the DCH rate of the PS (S/I/B) services is the
minimum DRBC rate of DCH (refer to 3.1.2.4 "DCH Initial Access Rate for PS
Service"). The rate increase is based on the rate increase principles (refer to UL
DCH -> UL DCH (rate increase) and DL DCH -> DL DCH (rate increase)). The
uplink and downlink DRBC rate levels are configured by
UlRateAdjLev[MAX_NUM_RATE_ADJUST] and
DlRateAdjLev[MAX_NUM_RATE_ADJUST] separately.
Where, the GBR of streaming services is the GBR of RAB allocation; the GBR of I/B
services is 0; the MaxBR is the maximum bit rate of RAB allocation by Iu interface.
3.1.2.4 DCH Initial Access Rate for PS Service
The initial access rate of DL DCH/UL DCH of PS services is determined in the following
way:
If the DRBC switch DrbcSwch is set to OFF, the DCH initial rate is min (max (the highest
rate level of DBRC, GBR), MaxBR). The uplink and downlink DRBC rate levels are
configured by UlRateAdjLev[MAX_NUM_RATE_ADJUST] and
DlRateAdjLev[MAX_NUM_RATE_ADJUST] separately, the MaxBR is the maximum bit
rate of RAB allocation by Iu interface.
If the DRBC switch DrbcSwch 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 InitialRateUl and InitialRateDl
separately. If the admission decision for the DCH initial rate fails, 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 DBRC, 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 / NrtMaxDlRateDch (for NRT service) are used to limit
the DCH maximum rate of uplink and downlink respectively.

In the case of inter-RNC, parameters RtMaxUlRateDchD / RtMaxDlRateDchD (for RT

service) and NrtMaxUlRateDchD / NrtMaxDlRateDchD (for NRT service) are used to limit
the DCH maximum rate of uplink and downlink respectively. If the related 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 DCH
Limited Rate value of all the cells in the active set.
3.1.3 Channel Switching
The channel switching and dynamic resource adjustments are performed only when the
DRBC switch (DrbcSwch) is ON.
During the session, the dynamic channel switching for the R99 system is to adjust the
service bandwidth and hand over channels in real-time according to the measurements
of traffic, cell load, DL DTCP, and UL UE Txp. The figure below shows the R99 channel
switching that the system currently supports in accordance with the R99 protocol.
Figure 3-1 R99 Channel Switching
Reconfig SF
1. UL/DL Traffic Volume
Based
2. DL D-TCP Based
3. UL TxP Based Transition of DCH/DCH -> FACH/RACH
4. Cells RTWP 1. UL&DL Traffic Volume Based
5. Cells TCP 2. Support CELL_FACH
Transition of FACH/RACH -> DCH/DCH

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

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

1. DL&UL Traffic Volume Based 1. UL&DL Traffic Volume Based
Below we will introduce the switching principles for types of channel switching shown in
the above figure.

3.1.3.1 DL DCH -> DL DCH (Rate Increase)
Rate increase is triggered by the downlink traffic.
The DCH to DCH rate increase is based on the traffic measurement report (Event 4A)
from the user plane and determined by the dedicated transmission power of the
subscriber and cell load.
The Event 4A is defined as the traffic measurement that is larger than an absolute
threshold. For detailed definition, refer to 3.1.4.1 Traffic Measurement.
The Event A is defined as that the Node B downlink dedicated transmission power
(D-TCP) is greater than an absolute threshold. The Event B is defined as that the Node B
downlink dedicated transmission power (D-TCP) is smaller than an absolute threshold.
For detailed definition, refer to 3.1.4.3 Node B Dedicated TCP Measurement.
The downlink DCH rate increase is triggered in the case of the following conditions:
The DCH rate adjustment triggered by traffic switch DchAdjRateSwch is ON.
The system receives consecutive DchE4aThd traffic measurement reports (Event

4A) from the user plane. (Note: if the system receives a traffic measurement report
(Event 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 (Event B) of

NodeB D-TCP, that is, the UE is in B state. (Note: if the system receives a
measurement report (Event 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 threshold, refer to 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 that is greater than the current rate in
the DRBC downlink rate levels DlRateAdjLev[MAX_NUM_RATE_ADJUST], DCH
Limited Rate, DL MaxBR). The MaxBR is the maximum bit rate during the RAB

allocation.
The target rate of RT DCH is min (next rate level that is greater than the current rate in
the DRBC downlink rate levels DlRateAdjLev[MAX_NUM_RATE_ADJUST], DCH
Limited Rate, DL MaxBR).
For macro diversity, in the case of DCH rate increase:
The target rate of NRT Downlink DCH rate is min (next rate level that is greater than the
current rate in DRBC downlink rate levels DlRateAdjLev[MAX_NUM_RATE_ADJUST],
DL MaxBR, DCH Limited Rate, and MaxRateMD).
The target rate of RT Downlink DCH rate is min (next rate level that is greater than the
current rate in DRBC downlink rate levels DlRateAdjLev[MAX_NUM_RATE_ADJUST],
DL MaxBR, the minimum DCH Limited Rate, and MaxRateMD).
Here, for the DCH Limited Rate explanation, please refer to 3.1.2.4 "DCH Initial Access
Rate for PS Service". The MaxRateMD is the maximum rate threshold allowed for DCH
when the UE is in macro diversity.
In addition, in the 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 distinguishing

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 rates of concurrent PS services of NRT cannot exceed DlPsRateLmtLowC
If the rate of C (CS) services exceeds CRateThrd, the sum of downlink rates of
concurrent PS services of NRT cannot 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:

1. Release some of the bandwidth of the subscriber to other subscribers to improve
the bandwidth utilization ratio when the required bandwidth for data transmission of
the subscriber is decreased.
2. Lower the bandwidth of the subscriber and transmission power to ensure the QoS
for the subscriber when the downlink transmission power of the subscriber is too
high.
3. 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:
1. Rate decrease triggered by downlink traffic
2. Rate decrease triggered by Node B downlink dedicated transmission power
3. Rate decrease triggered by cell downlink load
4. Rate decrease triggered by downlink resource congestion
5. Rate decrease triggered by mobility
6. Rate decrease triggered by DCH rate limitation in cell
Any of the above factors can trigger the rate decrease.
1. Rate decrease triggered by downlink traffic
The DCH to DCH switching for downlink rate decrease is based on the traffic
measurement report (Event 4B) on the user plane.
The Event 4B is defined as that the value of traffic measurement is smaller than an
absolute threshold. For detailed definition, refer to 3.1.4.1 Traffic Measurement.
The DL rate decrease is triggered in the case of the following conditions:
The DCH rate adjustment triggered by traffic switch DchAdjRateSwch is open.

The system receives consecutive DchE4bThd traffic measurement reports (Event

4B) from the user plane. (Note: if the system receives a traffic measurement report
(Event 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 RACH switching] or [downlink target rate is greater than
or equal to the rate threshold Rfach for FACH switching] (if the system switch
FachSwch for CELL_FACH switching is closed, the above condition is not taken
into consideration); real-time S services: current rate exceeds the GBR of RAB
allocation
In the case of rate increase of DCH, the target rate is calculated by the formula: max
(next rate level smaller than the current rate in DRBC downlink rate levels
DlRateAdjLev[MAX_NUM_RATE_ADJUST], GBR). The GBR of interactive and
background services is 0, and the GBR 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 decrease can be triggered by the Node B
downlink dedicated transmission power (Event A).
The Event A is defined as that the NodeB downlink dedicated transmission power
(D-TCP) is greater than an absolute threshold. The Event B s defined as that the NodeB
downlink dedicated transmission power (D-TCP) is smaller than an absolute threshold.
For detailed definition, refer to 3.1.4.3 Node B Dedicated TCP Measurement.
The DCH rate decrease is triggered in the case of the following conditions:
The DCH rate adjustment triggered by D-TCP switch DlPwrDasf is ON.
The system receives consecutive DtcpEaThd measurement reports (Event A) of

Node B D-TCP, that is, the UE is in A state. (Note: if the system receives a
measurement report (Event B) by Node B when the receiving times are smaller than
the threshold, the corresponding counter is cleared.)

Non-real-time I/B services: the current rate is greater than minimum rate in DCH
(the lowest rate level configured by DlRateAdjLev[MAX_NUM_RATE_ADJUST]);
real-time S services: the current rate is greater than the GBR of RAB allocation.
(next rate level that is smaller than the current rate in DRBC downlink rate levels
background services is 0, and the GBR of streaming service is the GBR in RAB
allocation.
3. Rate decrease triggered by cell downlink load
The DCH to DCH switching for DCH downlink rate decrease can be triggered by the
downlink load control of the cell.
The current cell load exceeds the overload threshold; (the downlink load is
determined by TCP. For details of overload threshold, refer to ZTE UMTS Overload
Control Feature Guide).
real-time S services: current rate is greater than the GBR of RAB allocation
background services is 0, and the GBR of streaming services is the GBR in RAB
allocation.
For more details about the load control, refer to 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 resource congestion of the cell.

The downlink CE resources, code resources or power are congested.
real-time S services: the current rate is greater than the GBR of RAB allocation.
background services is 0, and the GBR of streaming services is the GBR in RAB
allocation.
For more details about congestion control, refer to ZTE UMTS Congestion Control
Feature Guide.
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 to admit the user again. The minimum rate is min (max (the
lowest level of DRBC downlink rate levels DlRateAdjLev[MAX_NUM_RATE_ADJUST],
DL GBR), DL MaxBR).
For more details about mobility, refer to ZTE UMTS handover Control Feature Guide.
Take the 6000ms as period, and check periodically whether there exist NRT or RT
services which exceed DCH rate limitation NrtMaxDlRateDch or RtMaxDlRateDch. If so,
choose no more than 5 users to decrease rate, and the NRT traffic target rate is
NrtMaxDlRateDch and NRT traffic target rate is RtMaxDlRateDch.
3.1.3.3 UL DCH -> UL DCH (Rate Increase)
1. Rate increase triggered by uplink traffic

The DCH to DCH switching for uplink rate increase is based on the traffic measurement
report (Event 4A) by the UE and determined by the cell's dedicated transmission power
and cell load.
The Event 4A is defined as the traffic measurement that is larger than an absolute
threshold. For detailed definition, refer to 3.1.4.1 Traffic Measurement.
The uplink DCH rate increase is triggered in the case of the following conditions:

4A) from the UE. (Note: if the system receives a traffic measurement report (Event
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 (Event 6B) triggered by UE

transmission power, that is, UE uplink transmission power is in 6B state. (Note: for
details, refer to 3.1.4.2 UE internal TxP Measurement.)
The uplink load of the cell is not overloaded. (Note: the uplink load is determined by
RTWP. For details, refer to 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 that is greater than the current rate in
the DRBC uplink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST], DCH Limited
Rate, UL MaxBR). The MaxBR is the maximum bit rate during the RAB allocation.
The target rate of RT DCH is min (next rate level that is greater than the current rate in
the DRBC downlink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST], DCH
Limited Rate, UL MaxBR).
For macro diversity, in the case of DCH rate increase:
The target rate of NRT Uplink DCH rate is min (next rate level that is greater than the
current rate in DRBC uplink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST], UL
MaxBR, DCH Limited Rate, and MaxRateMD).

The target rate of RT Downlink DCH rate is min (next rate level that is greater than the
current rate in DRBC Uplink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST], UL
MaxBR, DCH Limited Rate, and MaxRateMD).
Here, for the DCH Limited Rate explanation, refer to 3.1.2.4 "DCH Initial Access Rate
for PS Service"; The MaxRateMD is the maximum rate threshold allowed for DCH when
the UE is in macro diversity.
In addition, in the 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 distinguishing

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 cannot exceed UlPsRateLmtLowC.
If the rate of C (CS) services exceeds CRateThrd, the sum of uplink rates of
concurrent PS services of NRT cannot exceed UlPsRateLmtHighC.
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:
1. Release some of the bandwidth of the subscriber to other subscribers to improve

the bandwidth utilization ratio when the required bandwidth for data transmission of
the subscriber is decreased.
2. 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.
3. 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:
1. Rate decrease triggered by uplink traffic

2. Rate decrease triggered by UE uplink dedicated transmission power
3. Rate decrease triggered by cell uplink load
4. Rate decrease triggered by uplink resource congestion.
Any of the above factors can trigger the rate decrease.
1. Rate decrease triggered by uplink traffic
The DCH to DCH switching for uplink rate decrease is based on the traffic measurement
report (Event 4B) from the user plane.
absolute threshold. For detailed definition, refer to 3.1.4.1 Traffic Measurement.
If the system receives consecutive DchE4bThd traffic measurement reports (Event

4B) of the UE. (Note: if the system receives a traffic measurement report (Event 4A)
by the UE when the receiving times are smaller than the threshold, the
None-real-time I/B services: [current uplink rate of the UE is greater than or equal to
the rate threshold Rrach for RACH switching] or [downlink target rate is greater than
or equal to the rate threshold Rfach for FACH switching] (if the system switch
FachSwch for CELL_FACH switching is closed, the above condition is not taken
into consideration); real-time S services: the current rate exceeds the GBR of RAB
allocation
The target rate of DCH rate decrease is max (next rate level that is smaller than the
current rate in DRBC uplink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST],
GBR). The GBR of interactive and background services is 0, and the GBR of streaming

services is the GBR in the 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 (Event 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 interference with other subscribers. When the
UE is close to the base station, the traffic can trigger the UL DCH rate increase.
The Event 6A is defined as that the UE dedicated transmission power exceeds an

absolute threshold, namely, the UE is in high power status. For specific configurations of
threshold, refer to 3.1.4.2 UE internal TxP Measurement.
The DCH rate adjustment triggered by UE dedicated transmission power switch

UlPwrDasf is ON.
Receive the measurement reports (Event 6A) triggered by UE transmission power,

that is, the UE transmission power is in 6A state.
(lowest rate level configured by UlRateAdjLev[MAX_NUM_RATE_ADJUST]);
real-time S services: the current rate is greater than the GBR in the RAB allocation
3. Rate decrease triggered by cell uplink load
The DCH to DCH switching for DCH uplink rate decrease can be triggered by the uplink
load control of the cell.

The current uplink cell load exceeds the overload threshold. The uplink load is
determined by RTWP. For details about overload threshold, refer to ZTE UMTS
Overload Control Feature Guide.
(the lowest rate level configured by UlRateAdjLev[MAX_NUM_RATE_ADJUST]);
real-time S services: the current rate is greater than the GBR in the RAB allocation.
4. Rate decrease triggered by uplink resource congestion
The DCH to DCH switching for DCH uplink rate decrease can be triggered by the uplink
resource congestion of the cell.
The CE uplink resources or power are congested.
(the lowest rate level configured by UlRateAdjLev[MAX_NUM_RATE_ADJUST]);
real-time S services: the current rate is greater than the GBR in the RAB allocation
For more details about congestion control, refer to ZTE UMTS Congestion Control
Feature Guide.
When the UE performs hard handover from one R99 cell to another due to mobility, if the
subscriber uplink admission at the current rate fails in a target cell, the system uses the

minimum DRBC rate to admit the subscriber again. The minimum rate is min (max (the
lowest level of DRBC uplink rate levels UlRateAdjLev[MAX_NUM_RATE_ADJUST], UL
GBR), UL MaxBR).
Take the 6000ms as period, and check periodically whether there exist NRT or RT
services which exceed DCH rate limitation NrtMaxDlRateDch or RtMaxDlRateDch. If so,
choose no more than 5 users to decrease rate, and the NRT traffic target rate is
NrtMaxDlRateDch and NRT traffic target rate is RtMaxDlRateDch.
3.1.3.5 CELL_DCH(DL DCH/ UL DCH) <-> CELL_FACH(DL FACH/UL RACH)
1. CELL_DCH <-> CELL_FACH channel switching triggered by traffic
i CELL_DCH (DL DCH/UL DCH ) -> CELL_FACH (DL FACH/UL RACH)
When the UE is in the CELL_DCH (DL DCH/UL DCH) state, the switching from
CELL_DCH (DL DCH/UL DCH) to CELL_FACH (DL FACH/UL RACH) can be
triggered by the traffic measurement report (Event 4B) from the user plane and UE.
absolute threshold. For details, refer to 3.1.4.1 Traffic 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 FachSwch for CELL_FACH switching is open.
The services are interactive or background services.
The system receives consecutive ToFtimesThr traffic measurement reports

(Event 4B) from the user plane and UE, and the switch is triggered by downlink
report. (Note: if the system receives a traffic measurement report (Event 4A)
from the user plane or UE when the receiving times are smaller than the
threshold, the calculator is cleared.)

The downlink target rate of the UE is smaller than the maximum downlink rate
threshold Rfach, and the current uplink rate is smaller than the maximum
uplink rate threshold Rrach (Note: if the rate is at the lowest rate level
DlRateAdjLev[MAX_NUM_RATE_ADJUST], 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 CELL_FACH.
If the condition for CELL_FACH switching is met, but the admission for
CELL_FACH fails, and the current uplink or downlink rate is greater than the
minimum rate that UL DCH or DL DCH can bear, namely, the lowest rate level
DlRateAdjLev[MAX_NUM_RATE_ADJUST], UL DCH or DL DCH rate decrease is
selected.
ii CELL_FACH (DL FACH/UL RACH) -> CELL_DCH (DL DCH/UL DCH)
When the UE is in the CELL_FACH (DL FACH/UL RACH) state, the switching from
CELL_FACH (DL FACH/UL RACH) to CELL_DCH (DL DCH/UL DCH) can be
triggered by the traffic measurement report (Event 4A) from the user plane or UE.
The switching from CELL_FACH (DL FACH/UL RACH) to CELL_DCH is triggered in

the case of the following conditions:
The system receives consecutive FachE4aThd measurement reports of Event

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 details about overload threshold,
refer to ZTE UMTS Overload Control Feature Guide.
The rate of DL DCH/UL DCH is the initial rate of DRBC after the CELL_DCH
switching, which is [UL initial rate, DL initial rate] (see 3.1.2.2 Initial Service

Channel Allocation) The GBR of interactive and background services is 0.
2. CELL_DCH to CELL_FACH channel switching triggered by load
The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FACH can be triggered by
the cell load.
The downlink cell load exceeds the overload threshold (Note: the downlink
load is determined by TCP.) For details about overload threshold, refer to ZTE
UMTS Overload Control Feature Guide.
3.1.3.6 CELL_DCH (DL DCH/UL DCH ) -> URA_PCH/ CELL_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 / CELL_PCH can be triggered by the
traffic measurement report (Event 4B0) from the user plane and UE.
The Event 4B0 is defined as that the value of traffic measurement value is 0. For detailed
definition, refer to 3.1.4.1 Traffic Measurement.
The switching from CELL_DCH (DL DCH/UL DCH) to URA_PCH/ CELL_PCH is

triggered in the case of the following conditions:
The system switch PchSwch for URA_PCH/ CELL_PCH switching is ON.
PchCellSwch is ON.
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.
condition for switching to URA_PCH/ CELL_PCH.
If the concurrence 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, then the
system receives consecutive DToPchThd traffic measurement reports of Event 4B0 from
the user plane and UE: If there are radio links in D-RNC, and the D-RNC does not
support PS (0 kbps/0 kbps), the rate of the PS service is decreased to the minimum
DRBC rate. Otherwise, the rate of the PS service decreases to 0 kbps/0 kbps, and keeps
working in the CELL_DCH state without switching. (Note: RncFeatSwitchBIT18 is used
to indicate whether the D-RNC supports PS (0 kbps/0 kbps) or not.)
3.1.3.7 CELL_FACH (DL FACH/UL RACH) -> URA_PCH/ CELL_PCH
When the UE uses the CELL_FACH to bear the interactive and background services, the
switching from CELL_FACH to URA_PCH/ CELL_PCH can be triggered by the traffic
measurement report (Event 4B0) from the user plane and UE.
The switching from CELL_FACH to URA_PCH/ CELL_PCH is triggered in the case of the
following conditions:
PchCellSwch is ON.
The system receives consecutive FToPchThd traffic measurement reports with

measurement value of 0 by user plane and UE. (Note: if the system receives a
3.1.3.8 CELL_DCH (DL DCH/UL DCH ) -> IDLE
When the UE uses the CELL_DCH for service bearer, the switching from CELL_DCH to

IDLE is triggered in the case of the following conditions:
The system receives consecutive DToIdleThd traffic measurement reports with

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

cleared.)
conditions for switching to IDLE.
When the channel is switched to IDLE, the occupied radio resources are released and
3.1.3.10 URA_PCH/ CELL_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 Channel Selection Policy for UE from PCH State to Other State
For UE in URA_PCH/CELL_PCH state when the cell is triggered by the uplink data
transmitting, or downlink data transmitted, or new service setup:
If the parameter GresPara48 bit8 is 0, URA_PCH/CELL_PCH state to CELL_DCH state

will be triggered;
If the parameter GresPara48 bit8 is 1, URA_PCH/CELL_PCH state to CELL_FACH

state will be triggered.
3.1.3.12 Uplink and downlink reconfiguration in one step
The 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.
The 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 DrbcSwch in UL&DL are both on, the uplink and downlink reconfiguration in one
step scenes are as following:
UL DCH -> UL DCH (rate increase) based on traffic volume
If UL DCH satisfies the rate increase conditions in advance, start the timer
UpUdRecfgTimer.
If, before the timer UpUdRecfgTimer expires, DL DCH also satisfies the rate increase
conditions triggered by traffic volume, try the uplink and downlink rate increase
reconfiguration in one step; if the admission decision fails, try the DL rate increase; if it
fails again, go on to perform UL rate increase.
If, before the timer UpUdRecfgTimer expires, DL DCH satisfies the rate decrease
conditions triggered by traffic volume, try the uplink and downlink rate decrease

reconfiguration in one step; if the admission decision for the uplink rate increase fails, go
on to perform DL rate decrease reconfiguration.
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, try the UL rate increase reconfiguration.
DL DCH -> DL DCH (rate increase) based on traffic volume
If DL DCH satisfies the rate 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, try the uplink and downlink rate increase
reconfiguration in one step; if the admission decision fails, try the DL rate increase; if it
fails again, go on to perform UL rate increase.
If, before the timer UpUdRecfgTimer expires, UL DCH satisfies the rate decrease
conditions triggered by traffic volume, try the uplink rate decrease and downlink s rate
increase reconfiguration in one step is tried, if the admission decision for DL rate
increase fails, then go on to perform UL rate decrease reconfiguration.
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, try DL rate increase reconfiguration.
UL DCH -> UL DCH (rate decrease) based on traffic volume
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, perform the uplink and downlink rate decrease
reconfiguration in one step.
If, before the timer DnUdRecfgTimer expires, DL DCH satisfies the rate increase
triggered by traffic volume, try the uplink rate decrease and downlink rate increase

reconfiguration in one step; if the admission decision for DL rate increase fails, go on to
perform UL rate 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, perform UL rate decrease reconfiguration.
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, perform the uplink and downlink rate decrease
reconfiguration in one step.
If, before the timer DnUdRecfgTimer expires, UL DCH satisfies the rate increase
conditions triggered by traffic volume, try the uplink rate increase and downlink rate
decrease reconfiguration in one step; if the admission decision for UL rate increase fails,
go on to perform DL DCH rate decrease 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, perform DL rate decrease reconfiguration.
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.
The RLC mode of Traffic measurement report is decided by MeasRptTrMod. If the AM

mode is selected, RNC will require UE retransmit error or discontinue SDU. If the UM
mode is selected, the retransmission will not be available. The quantity of traffic
measurement is controlled by MeasQuantity; MeasQuantity could be 1:RLC buffer

payload, 2:Average RLC buffer payload, 3:Variance of RLC buffer payload. In the traffic
measurement control message, whether to 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 the 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 the
traffic measurement control message, Periodical Reporting / Event Trigger Reporting
Mode IE take the value of RptCrt.
Related events with traffic measurement include:
Event 4A: the event is triggered when the traffic measurement value exceeds an
absolute threshold and this condition lasts for a certain period
(TrigTime[MAX_UE_TRV_MEAS_EVENT]). Delay timer
PendingTime[MAX_UE_TRV_MEAS_EVENT] is set to prevent the event from
being triggered frequently.
Event 4B: the event is triggered when the traffic measurement value is smaller than
an absolute threshold and this condition lasts for a certain period
(TrigTime[MAX_UE_TRV_MEAS_EVENT]). Delay timer
PendingTime[MAX_UE_TRV_MEAS_EVENT] is set to prevent the event from
being triggered frequently.
Event 4B0: the event is triggered when the traffic measurement value is 0 and this
condition lasts for a certain period (TrigTime[MAX_UE_TRV_MEAS_EVENT]).
Event 4B0 is an exceptional case in Event 4B, its delay timer
PendingTime[MAX_UE_TRV_MEAS_EVENT] is the same as that of Event 4B.
Where, the absolute thresholds for different channels acquire different parameters.
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 the
event which has occurred is prevented from reoccurring. The following figure shows the
report of Event 4A based on the principles of trigger time and pending time.

Figure 3-2 Event Triggering of Traffic Measurement
Traffic Volume
Thr_4A
Pending
Pending
Trigger Time Trigger
Time Trigger
Time Time Time
Report 4A Report 4A Report 4A
The time of trigger channel switching is calculated as follows:
Time = Counter Threshold* TiggerTime + (Counter Threshold - 1)*PendingTime
The absolute threshold (such as parameter RptThres[MAX_UE_TRV_MEAS_EVENT]) is

configured as follows:
1. The smaller the threshold value of Event 4A 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 resources; and vice versa.
2. The bigger the threshold value of Event 4B is, the quicker the system responses to
the service demand of the UE, and the sooner the occupied bandwidth is decreased;
and vice versa.
The parameters TrigTime[MAX_UE_TRV_MEAS_EVENT] and PendingTime[MAX

_UE_TRV_MEAS_EVENT] are configured as follows:
1. The smaller the value of TrigTime[MAX_UE_TRV_MEAS_EVENT] for Event 4A is,

the quicker the control plane receives the reports and increases the bandwidth
when the traffic measurement meets the threshold for triggering 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, the system will
respond to the service demand which fluctuates in a very short moment, resulting in
unnecessary bandwidth increase.

2. The smaller the value of PendingTime[MAX_UE_TRV_MEAS_EVENT] for Event

4A is, the quicker the control plane receives consecutively the reports and
increases the bandwidth when the traffic measurement meets the threshold for
triggering 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 result in a considerable bandwidth occupation.
3. The smaller the value of TrigTime[MAX_UE_TRV_MEAS_EVENT] for Event 4B is,

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

is, the quicker the control plane receives consecutively the reports and decreases
the bandwidth when the traffic measurement meets the threshold for triggering
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 result in a considerable bandwidth occupation. Therefore,
the feeling of subscriber and bandwidth utilization should be taken into
consideration before configuration.
The rate increase process is triggered when the control plane or UE receives the
consecutive reports of Event 4A and the 4A_counter >= 4A_threshold; while the rate
decrease process is triggered when the control plane or UE receives the consecutive
reports of Event 4B and the 4B_counter > =4B_threshold. Where, 4A_threshold and
4B_threshold are configured with different OMC parameters based on different types of
channel switching. The following figure shows the rate adjustment process (no event
counter configured).

Figure 3-3 Rate Adjustment Triggered by Traffic
pending-time-after- Reporting event

trigger 4A
time-to-trigger Increasing Rate
Reporting event
4B
Thr_4A Decreasing Rate
Thr_4B time-to-trigger
pending-time-after-
Report Report trigger
4A 4B
The traffic measurement uses the parameter MeasEvtNum to define its number (2 at
present) of events. The two events are Event 4A and Event 4B corresponding to
parameter MeaEvtId[MAX_UE_TRV_MEAS_EVENT] which are valid only for event
reporting.
Parameter TxInterCfgPre[MAX_UE_TRV_MEAS_EVENT] decides whether to forbid

RACH data after measurement report. The forbidden time is decided by
TxInterruption[MAX_UE_TRV_MEAS_EVENT].
Measure parameter acquisition method: Firstly obtain the Used UTrvMeasProfile

(refUTrvMeasProfile) of the cell from the management object UTRAN Cell Object
UUtranCellFDD, secondly obtain the corresponding Traffic Volume Measurement Profile
Object UTrvMeasProfilebased on the value of the parameter refUTrvMeasProfile, and
thirdly obtain the corresponding traffic measurement parameter based on the
measurement target from the sub-object of UTrvMeasProfile.
Here, Traffic Volume Measurement Profile Object UTrvMeasProfile includes the

following sub-objects:
URachEvtUeTrv (UE Traffic Volume Event Measurement Configuration Object for

RACH)
URachPrdUeTrv (UE Traffic Volume Period Measurement Configuration Object for

RACH)

UFachEvUpTrv (UP Traffic Volume Event Measurement Configuration Object for

FACH)
UDchEvUeTrv (UE Traffic Volume Event Measurement Configuration Object for

DCH)
UDchEvUpTrv (UP Traffic Volume Event Measurement Configuration Object for

DCH)
UDchPrdUeTrv (UE Traffic Volume Period Measurement Configuration Object for

DCH)
UDedSHsdschEvUpTrv (UP Traffic Volume Measurement Configuration Number

for Streaming Class on HS-DSCH Object)
UDedIBHsdschEvUpTrv (UP Traffic Volume Measurement Configuration for

Interactive and Background Class on HS-DSCH Object)
UComHsdschEvUpTrv (UP Traffic Volume Measurement Configuration for

HS-DSCH in CELL_FACH Object)
UETTIEdchEvUpTrv (UP Throughput Event Measurement Configuration for E-TTI

Switching Object)
UDedEdchEvUpTrv (UP Traffic Volume Measurement Configuration Object for

E-DCH)
UComEdchEvUpTrv (UP Traffic Volume Measurement Configuration Object for

E-DCH)
If the uplink channel for service bearer is the DCH, the traffic is measured on the UE side,
and if the measurement way which is adopted to measure the traffic is the event report,
the traffic volume measurement parameters are obtained from the sub-object
UDchEvUeTrv. The details are listed in the following table:
ueTrvMCfgNo UE Traffic Volume Measurement Configuration Index
averageTime Time Interval for Taking an Average or a Variance
MeaEvtId UE Traffic Volume Measurement Event Identity
MeasEvtNum Event Number of UE Traffic Volume Measurement

MeasQuantity Measurement Quantity
measRptTrMod Measurement Report Transfer Mode
pendingTime Pending Time After Trigger
rptRlcAveInd Average of RLC Buffer Payload for Each RB
rptRlcBufInd RLC Buffer Payload for Each RB
rptRlcVarInd Variance of RLC Buffer Payload for Each RB
rptThres0 Traffic Volume Threshold of Event 4A/4B for DCH(8kbps)
trigTime Time to Trigger
If the downlink channel for service bearer is the DCH, the traffic is measured on the user
plane side, the traffic volume measurement parameters are obtained from the sub-object
UDchEvUpTrv. The details are listed in the following table:

If the uplink channel for service bearer is the RACH, the traffic is measured on the UE
side, and if the measurement way which is adopted to measure the traffic is the event
report, the traffic volume measurement parameters are obtained from the sub-object
URachEvtUeTrv. The details are listed in the following table:
rptThres Traffic Volume Threshold of Event 4A/4B for RACH Channel
txInterCfgPre Tx Interruption After Trigger Configuration Tag
txInterruption Tx Interruption After Trigger
If the downlink channel for service bearer is the FACH, the traffic is measured on the
user plane side, the traffic volume measurement parameters are obtained from the
sub-object UFachEvUpTrv. The details are listed in the following table:

rptThres Traffic Volume Threshold of Event 4A/4B for FACH Channel
If the channel for service bearer is the uplink DCH, the traffic is measured on the UE side,
and if the measurement way which is adopted to measure the traffic is the period report,
the traffic volume measurement parameters are obtained from the sub-object
UDchPrdUeTrv. The details are listed in the following table:
prdRptAmount Amount of Reporting in Period Report Criteria
prdRptInterval Reporting Interval in Period Report Criteria
If the channel for service bearer is the RACH, the traffic is measured on the UE side, and
if the measurement way which is adopted to measure the traffic is the period report, the
traffic volume measurement parameters are obtained from the sub-object
URachPrdUeTrv. The details are listed in the following table:

3.1.4.2 UE internal TxP Measurement
The UE internal measurement measures the UE transmission power (TxP) by the event
report.
There are two kinds of event: Event 6A and Event 6B.
Event 6A: when the UE TxP measurement value is greater than a certain absolute
threshold and this condition lasts for a moment
(TrigTime[MAX_UE_INTER_MEAS_EVENT] ), the Event 6A is triggered.
Event 6B: when the UE TxP measurement value is smaller than a certain absolute
threshold and this condition lasts for a moment
(TrigTime[MAX_UE_INTER_MEAS_EVENT]), the Event 6B is triggered.
The threshold parameter of Event 6A and Event 6B (TxPowerThres ) is a delta value

relative to min (UE maximum transmitted power, uplink DPCH maximum transmission
power).
Here, MAX_UE_INTER_MEAS_EVENT is configured by MeasEvtNum.
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 into consideration, 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 rate increase by the traffic. However, a certain margin
should be configured between the thresholds of Event 6A and Event 6B; otherwise, there
may be a situation: after the rate is decreased based on Event 6A, the rate 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 experience is affected.
If PS services exist, and uplink DRBC DrbcSwch is on, and UlPwrDasf is on, and all

services use uplink DCH as bearer, the measurement is triggered. After every uplink rate
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.
Method to measure parameter acquisition: Firstly obtain Used UUeIntMeasProfile

(refUUeIntMeasProfile) of the cell from the management object UTRAN Cell
ObjectUUtranCellFDD, secondly obtain the corresponding UE Internal Measurement
Profile Object UueIntMeasProfile based on the value of the parameter
refUUeIntMeasProfile, and thirdly obtain the corresponding UE Internal Measurement
parameter based on the measurement target from the sub-object UPsEvtTPUeInt of
UUeIntMeasProfile:
UE Transmitted Power Event Measurement Configuration
UPsEvtTPUeInt
for PS Object ID
ueIntMCfgNo UE Internal Measurement Configuration Index
filterCoeff Filter Coefficient
measEvtNum Maximum Event Number of UE Internal Measurement
meaEvtId UE Internal Measurement Event Identity
txPowerThres UE Transmitted Power Threshold
3.1.4.3 Node B Dedicated TCP Measurement
The Node B dedicated 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 decrease as
well as a restriction for bandwidth increase. The Node B dedicated TCP measurement
which is used to trigger DRBC rate adjustment is reported periodically. The period is
configured by rptPrd, and the unit of the period is determined by rptPrdUnit.
The Node B dedicated measurement parameter configuration object instance used for
dynamic radio bearer control is obtained in the sub-object UNbDedMeas of the object
UNbDedMeasProfile.
The type of Node B dedicated measurement is indicated by the parameter dedMeasType,
and the report type of the measurement result is indicated by the parameter rptType.

Each set of Node B dedicated measurement parameters configuration has a number

indicated by the parameter nbDMCfgNo, and nbDMCfgNote indicates the function used
by the configuration. The Node B dedicated measurement filter coefficient is
measFilterCoeff.
Because of the periodical report, the Event A/B is decided by RNC.
Two sets of measurement parameters relating to Event A and Event B are configured:
Event A: when the NodeB D-TCP measurement value is greater than a specific
absolute threshold (EvtAbTcpThrd[3]), Event A is triggered. Event A is used to
trigger the downlink rate decrease. When Event A is reported, the downlink
transmission power of UE is considered to be in a high power status.
Event B: when the NodeB D-TCP measurement value is smaller than a specific
absolute threshold (EvtAbTcpThrd[3]), Event B is triggered. Event B is used to
check whether the downlink transmission power is in a low status. When Event B is
reported, 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 DPCH 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 parameter
DlRateLevel[2]. The details are described in the following table:
The corresponding rate range of PS The corresponding
Rate Level
services threshold of Event A/B
The first rate

R<= DlRateLevel[0] EvtAbTcpThrd[0]
level
The second
DlRateLevel[0]<R<= DlRateLevel[1] EvtAbTcpThrd[1]
rate level
The third rate

R>DlRateLevel[1] EvtAbTcpThrd[2]
level
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 rate 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 between 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 trigger the
rate increase by traffic. Thus, the user experience is affected.
If PS services exist, and downlink DRBC DrbcSwch is on, and DlPwrDasf 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 dedicated TCP measurement is switched off.
3.2 Dynamic Channel Type Transfer for HSDPA Service
3.2.1 Signaling Channel Allocation
The signaling channel allocation process upon the RRC connection setup is the same as
the R99 policy.
For the setup of RAB allocation service, the signaling channel is selected in the following
principles:
1. 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: both the UE and the cell
support F-DPCH, both FdpchSupInd and RncFdpchSupInd are 1, (or both the UE
and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd are 1),
then the signaling is on the DL HS-DSCH/UL DCH; otherwise, the signaling is
mapped to DCH/DCH low rate signaling.

3.2.2 Initial Service Channel Allocation
the service features (RAB parameters). For the HS-DSCH in the HSUPA cells, the
selectable channel types are as follows:
1. Conversation services use DL DCH/UL DCH channels.
2. Streaming services can use DL HS-DSCH/UL DCH and DL DCH/UL DCH

channels.
3. Interactive and background services can use DL HS-DSCH/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.
1. For the UE supporting HS-DSCH in the HSDPA cell:
The principles for CS 64k service is the same as R99, see 3.7.11 "Video Call
Prohibited in Specific Area".
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 fails (for example, downlink
HS-DSCH fails to admit), select the DL DCH/UL DCH.
Otherwise, streaming services use DL DCH/UL DCH.
The Event 1F is defined as that the measurement value Ec/No is smaller than an
absolute threshold. For detailed definition, refer to 3.2.4.1 Pilot Channel Quality
Measurement.
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 RACH fails to
admit, select the CELL_DCH.
When the CELL_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 fails (for example, the downlink
HS-DSCH fails to admit), select the DL DCH/UL DCH.
Otherwise, the 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, but 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.
call service. All concurrent PS services use the same channel as bearer.
Channel allocation for the UE supporting only HS-DSCH in the HSDPA cell is as follows:
Concurrent
Channel Type
Service Types
If any of I/B services meet the condition of [dlMaxBR >= Rfach or

ulMaxBR >= Rrach] and the channel quality is non-1F event, select
the DL HS-DSCH/UL DCH with priority. If selecting the DL
HS-DSCH/UL DCH fails (for example, downlink HS-DSCH fails to
admit), select the DL DCH/UL DCH.
I/B+I/B If all the I/B services meet the condition of [dlMaxBR < Rfach and
ulMaxBR < Rrach], select DL FACH/UL RACH with priority. If the
selection fails, and the channel quality is non-1F event, select DL
HS-DSCH/UL DCH. If selecting DL HS-DSCH/UL DCH fails (for
example, downlink HS-DSCH fails 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 DPCH
and HS-DSCH for CS services] and channel quality is non-1F
event, select the DL HS-DSCH/UL DCH with priority for PS (I/B or
I/B+CS or
S) services. If selecting the DL HS-DSCH/UL DCH fails (for
S+CS or
example, downlink HS-DSCH fails to admit), select the DL DCH/UL
I/B+S+CS
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

the DL HS-DSCH/UL DCH with priority. If selecting the DL
I/B+S or S+S
HS-DSCH/UL DCH fails (for example, downlink HS-DSCH fails to
admit), select the DL DCH/UL DCH.
(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.
During the session, the dynamic channel switching in the HSDPA system is to adjust the
of traffic and channel quality. The following figure shows the channel switching that the
system currently supports according to HSDPA protocols.

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

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


Event 4B from the user plane, and consecutive ToFtimesThr traffic
measurement reports Event 4B from the UE, and switch is triggered by
downlink report. (Note: if the system receives a traffic measurement report
Event 4A from the user plane or UE when the receiving times are smaller than
the threshold, the corresponding counter is cleared.)

The current uplink rate is smaller than the maximum uplink rate threshold
Rrach 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 condition for CELL_FACH switching is met, but the CELL_FACH fails to admit,
and the current uplink rate is greater than the minimum rate that UL DCH can bear,
namely, the lowest rate level configured by UlRateAdjLev
[MAX_NUM_RATE_ADJUST], UL DCH rate decrease is selected.
ii. CELL_FACH -> CELL_DCH (DL HS-DSCH/UL DCH)
When the UE is in the CELL_FACH status, the switching from CELL_FACH to

CELL_DCH (DL HS-DSCH/UL DCH) can be triggered by the traffic measurement
report (Event 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

Event 4A from the user plane or UE. (Note: if the system receives a traffic
measurement reports Event 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-DSCH.
The cell load is not overloaded. (Note: For details about the overload threshold,
refer to ZTE UMTS Overload Control Feature Guide.)
The rate of UL DCH in the CELL_DCH (DL HS-DSCH/UL DCH) switching is

the [UL Initial rate] for DRBC, refer to 3.1.2.2 Initial Service Channel
Allocation.
2. CELL_DCH to CELL_FACH switching triggered by the cell load

the cell load.
The switching from CELL_DCH (DL HS-DSCH/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: For details
about the overload threshold, refer to ZTE UMTS Overload Control Feature
Guide.)
3.2.3.2 CELL_DCH (DL HS-DSCH) <-> DL DCH
1. Switching from DCH to HS-DSCH 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 (Event 4A) from the user plane to
increase the system capacity.
Measurement.
The switching from DL DCH to DL HS-DSCH is triggered in the case of the following
conditions:

4A) from the user plane. (Note: if the system receives a traffic measurement report
(Event 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-DSCH.
Note: HS-DSCH 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.
If there is CS service in the concurrent services and the UE is capable of the DL

DCH and DL HS-DSCH concurrency (maximum rate on the DPCH is reported by
the UE), the DL DCH of only PS services is switched to DL HS-DSCH; otherwise,
the switching is not implemented.
If the service is on the DCH, Event 4A triggered by the user plane meets the condition for
rate increase in the DL DCH -> DL HS-DSCH switching, but the DL HS-DSCH fails to
admit or the DL HS-DSCH is not supported, select DL DCH rate increase, and the uplink
remains on the DCH. In the case of DL DCH rate increase, the other conditions of DL
DCH rate increase must be satisfied (refer to DL DCH -> DL DCH (rate increase)).
2. Switching from HS-DSCH to DCH triggered by channel quality
When a subscriber uses the DL HS-DSCH/UL DCH, the DL HS-DSCH switching to DL

DCH can be triggered by channel quality measurement (Event 1F triggered by pilot
signal). This is because that the subscriber remaining on HS-DSCH will worsen the QoS
and lower the system capacity when the bit rate requirements of streaming services
carried on HS-DSCH are not satisfied and the channel quality deteriorates.
Measurement.
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 (IBChQSwch,

SChQSwch) are open (Note: when PS S and I/B service are concurrent, if any of
IBChQSwch and SChQSwch is open, these switches are considered open).
1. The channel quality triggers Event 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.4 "DCH Initial Access Rate for PS Service".
2. 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-DSCH, the
downlink channel will switch from HS-DSCH to DCH. The rate is the DCH initial rate, see
3.1.2.4 "DCH Initial Access Rate for PS Service".
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/ CELL_PCH
When the UE uses the CELL_DCH (DL HS-DSCH/UL DCH) for service bearer, the
switching from CELL_DCH (DL HS-DSCH/UL DCH) to URA_PCH/ CELL_PCH can be
triggered by the traffic measurement report (Event 4B0) from the user plane or UE.
The switching from CELL_DCH (DL HS-DSCH/UL DCH) to URA_PCH is triggered in the
case of the following conditions:
PchCellSwch is ON.

measurement value of 0 from the user plane and UE (Note: if the system receives a

3.2.3.4 CELL_DCH(DL HS-DSCH/UL DCH) -> IDLE
When the UE uses the CELL_DCH (DL HS-DSCH/UL DCH) for service bearer, the
switching from CELL_DCH (DL HS-DSCH/UL DCH) to IDLE is triggered in the case of
the following conditions:

cleared.)
When the channel is changed to IDLE, the occupied radio resources are released and
3.2.4.1 Pilot Channel Quality Measurement
The channel quality measurement is for the switching from HS-DSCH to DCH. Event 1E
and Event 1F are used 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 greater than an absolute threshold
(ThreshUsedFreq[MAX_INTRA_MEAS_EVENT]) and this condition lasts for a moment
(TrigTime[MAX_INTRA_MEAS_EVENT]), Event 1E is triggered.

1F definition: when the pilot signaling quality is worse than an absolute threshold
(ThreshUsedFreq[MAX_INTRA_MEAS_EVENT]) and this condition lasts for a moment
(TrigTime[MAX_INTRA_MEAS_EVENT]), Event 1F is triggered.
For more details about the parameter ThreshUsedFreq[MAX_INTRA_MEAS_EVENT]

and TrigTime[MAX_INTRA_MEAS_EVENT], refer to ZTE UMTS Handover Control
Feature Guide.
The following figure shows the rationale of Event 1E:
Figure 3-5 Event 1E in Channel Quality Measurement
Measurement
Quantity
P CPICH 1
P CPICH 2
Absolute
threshold
P CPICH 3
Trigger Time
Report 1E
The following figure shows the rationale of Event 1F:

Figure 3-6 Event 1F in Channel Quality Measurement
Measureme
nt
Quantity
P CPICH 1
Trigger
P CPICH 2 Time
Absolute
threshold
P CPICH 3
Report 1F
The traffic 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 in the 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.

(refUTrvMeasProfile) of the cell from the management object UTRAN Cell
ObjectUUtranCellFDD, secondly obtain the corresponding Traffic Volume
Measurement Profile Object UTrvMeasProfilebased on the value of the parameter
refUTrvMeasProfile, and thirdly obtain the corresponding traffic measurement parameter
based on the measurement target from the sub-object of UTrvMeasProfile.
If the service on the HS-DSCH is I/B, the traffic volume measurement is performed on
the user plane, and related parameters used in the traffic volume measurements are
obtained from the sub-object UDedIBHsdschEvUpTrv. The details are listed in the
following table:
ueTrvMCfgNo UE Traffic Volume Measurement Configuration

Index
Time Interval for Taking an Average or a

averageTime Variance
Event Number of UE Traffic Volume

MeasEvtNum Measurement
Traffic Volume Threshold of Event 4A/4B for

Interactive and Background Class on HS-DSCH
rptThres Channel
If the service on the HS-DSCH is streaming, the traffic volume measurement is

performed on the user plane, and related parameters used in the traffic volume
measurements are obtained from the sub-object UDedSHsdschEvUpTrv. The details are
listed in the following table:
UE Traffic Volume Measurement Configuration
ueTrvMCfgNo Index

rptThres Streaming Class on HS-DSCH Channel

3.3 Dynamic Channel Type Transfer for HSUPA Service
3.3.1 Signaling Channel Allocation
The signaling channel allocation process upon the RRC connection setup is the same as
the R99 policy.
For the setup of RAB allocation service, the signaling channel switching complies with
the following principles:
1. The low-speed bearer signaling DL DCH/UL DCH is selected if there is DL DCH/UL

DCH bearer service.
2. If all the services are on the DL HS-DSCH/UL DCH: if both the UE and the cell
support F-DPCH, both FdpchSupInd and RncFdpchSupInd are 1, (or both the UE
and the cell support E-FDPCH, both RncEfdpchSupInd and EfdpchSupInd are 1),
then the signaling is on the DL HS-DSCH/UL DCH; otherwise, the signaling is
mapped to DCH/DCH low-rate signaling.
3. If all the services are on the DL HS-DSCH/UL E-DCH:
i. If FourEChAllowed is supported, and SrbOnEdchSwch is switched on,
If both the UE and the cell support F-DPCH, and both FdpchSupInd and
RncFdpchSupInd are 1, (or both the UE and the cell support E-FDPCH, both
RncEfdpchSupInd and EfdpchSupInd are 1), the signaling is on
HS-DSCH/E-DCH.
Otherwise, the signaling is on DCH/E-DCH.
ii. If FourEChAllowed is supported, and SrbOnEdchSwch is switched off,
When the calculated MinSF is equal to 2sf2+2sf4: if both the UE and the cell
support F-DPCH, both FdpchSupInd and RncFdpchSupInd are 1, (or both

the UE and the cell support E-FDPCH, both RncEfdpchSupInd and

EfdpchSupInd are 1), the signaling is on HS-DSCH/E-DCH; Otherwise, the
signaling is on DCH/E-DCH.
When the calculated MinSF is not equal to 2sf2+2sf4, the signaling is on DCH/
DCH.
iii. If FourEChAllowed is not supported, and the switching is on SrbOnEdchSwch,
If both the UE and the cell support F-DPCH, both FdpchSupInd and
RncFdpchSupInd are 1, (or both the UE and the cell support E-FDPCH, both
RncEfdpchSupInd and EfdpchSupInd are 1), the signaling is on
HS-DSCH/E-DCH.
Otherwise, the signaling is on DCH/E-DCH.
iv. If FourEChAllowed is not supported, and SrbOnEdchSwch is switched off, the

signaling is on DCH/DCH.
the service features (RAB parameters). For the HSUPA UE in the HSUPA cells, select
the following channel types:
1. Conversation services use DL DCH/UL DCH.
2. Streaming services can use DL HS-DSCH/UL E-DCH, DL HS-DSCH/UL DCH, and

DL DCH/UL DCH.
3. Interactive and background services can use DL HS-DSCH/UL E-DCH, DL

HS-DSCH/UL DCH, DL DCH/UL DCH, and DL FACH/UL RACH.
For the UE, supporting HSUPA, in HSUPA cell:
1. CS 64k service

The principle for CS 64k service is the same as R99. Refer to 3.7.11 "Video Call
Prohibited in Specific Area".
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-DSCH/UL E-DCH fails (for example, the
uplink E-DCH fails to admit), select the DL HS-DSCH/UL DCH. If selecting the DL
HS-DSCH/UL DCH fails (for example, the downlink HS-DSCH fails 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 RACH fails to
admit, select the CELL_DCH.
When the CELL_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 fails (for example, the uplink E-DCH
fails to admit), select the DL HS-DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH
fails (for example, the downlink HS-DSCH fails 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 should be bound for use in service channel

allocation, that is, there is no combination of DL DCH/UL E-DCH.
call service. All concurrent PS services use the same channel as bearer.
Channel allocation for the UE supporting HSUPA in the HSUPA is as follows:

Concurrent
Channel Type
Service Types
If any of I/B services meets the condition of lMaxBR >= Rfach or

ulMaxBR >= Rrach, and channel quality is a non event 1F, select
the DL HS-DSCH/UL E-DCH with priority. If selecting the DL
HS-DSCH/UL E-DCH fails (for example, the uplink E-DCH fails to
admit), select the DL HS-DSCH/UL DCH. If selecting the DL
HS-DSCH/UL DCH fails (for example, the downlink HS-DSCH fails
to admit), select the DL DCH/UL DCH.
I/B+I/B If all I/B services meet the condition of dlMaxBR < Rfach and
ulMaxBR < Rrach, select the DL FACH/UL RACH with priority; if
selecting fails, channel quality is a non event 1F. Select the DL
HS-DSCH/UL E-DCH. If selecting the DL HS-DSCH/UL E-DCH
fails (for example, the uplink E-DCH fails to admit), select the DL
HS-DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH fails (for
example, the downlink HS-DSCH fails to admit), select the DL
DCH/UL DCH.
CS services select the DL DCH/UL DCH.

If the UE meets the uplink concurrent capabilities of the DPCH and
E-DCH, the downlink concurrent capabilities of the DPCH and
HS-DSCH for CS services and channel quality is a non event 1F,
select the DL HS-DSCH/UL E-DCH with priority for PS (I/B or S)
services. If selecting the DL HS-DSCH/UL E-DCH fails (for
I/B+CS or S+CS example, the uplink E-DCH fails to admit), select the DL
or I/B+S+CS HS-DSCH/UL DCH. If selecting the DL HS-DSCH/UL DCH fails (for
example, the downlink HS-DSCH fails to admit), select the DL
DCH/UL DCH.
If the UE meets the downlink concurrent capabilities of the DPCH
and HS-DSCH for CS services but does not meet the uplink
concurrent capabilities of the DPCH 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 fails (for example, the downlink HS-DSCH fails
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 channel quality is a non event 1F, select the DL HS-DSCH/UL

E-DCH. If selecting the DL HS-DSCH/UL E-DCH fails (for example,
I/B+S or S+S the uplink E-DCH fails to admit), select the DL HS-DSCH/UL DCH.
If selecting the DL HS-DSCH/UL DCH fails (for example, the
downlink HS-DSCH fails 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) service 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 HSUPA UE in the HSDPA is the same as that for HSDPA
concurrent service.
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.
2 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 used.
3 If EttiTraffVolSwch is on, and there is no CS traffic, and at least one traffic is

configured with 2ms TTI; and if 10ms TTI can satisfy GBR requirement, 10ms TTI is
used, and the throughput measurement is switched on; otherwise, if 10ms TTI
cannot satisfy GBR requirement, 2ms TTI is used, and the throughput measurement

is not switched on.
4 For other scenes, if there is no less than one traffic configured 2ms TTI, 2ms TTI is
used; otherwise, 10ms TTI is used, and the throughput measurement is not
switched on.
During the session, the dynamic channel switching in the HSUPA system is to adjust the
of traffic and channel quality. The following figure shows the channel switching that the
system currently supports according to HSUPA protocols.
Figure 3-7 HSUPA Channel Switching
Transition DCH/DCH -> HS-DSCH/E-DCH

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

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

1. UL&DL Traffic Volume Based 1. UL&DL Traffic Volume Based
Transition of PCH->IDLE
1. DL&UL Traffic Volume Transition of HS-DSCH/E-DCH -> IDLE
Based 1. UL&DL Traffic Volume Based
3.3.3.1 CELL_DCH (DL HS-DSCH/UL E-DCH) <-> CELL_FACH
1. CELL_DCH <-> CELL_FACH switching triggered by traffic
i. CELL_DCH(DL HS-DSCH/UL E-DCH) -> CELL_FACH
When the UE is in the CELL_DCH status, the switching from CELL_DCH (DL
HS-DSCH/UL E-DCH) to CELL_FACH can be triggered by the traffic measurement

report (Event 4B) by the user plane.
The switching CELL_DCH (DL HS-DSCH/UL E-DCH) to CELL_FACH is triggered in

the case of the following conditions:

(Event 4B) on the HS-DSCH from the user plane as well as consecutive
ToFtimesThr traffic measurement reports (Event 4B) on the E-DCH from the
user plane. (Note: if the system receives a traffic measurement report (Event
4A) from the user plane when the receiving times are smaller than the
ii. CELL_FACH -> CELL_DCH(DL HS-DSCH/UL E-DCH)
When the UE is in the CELL_FACH status, the switching from CELL_FACH to

CELL_DCH (DL HS-DSCH/UL DCH) can be triggered by the traffic measurement
report (Event 4A) from the user plane or UE.
The switching from CELL_FACH to CELL_DCH (DL HS-DSCH/UL E-DCH) is

The system receives consecutive FachE4aThd traffic measurement reports

(Event 4A) from the user plane or UE. (Note: if the system receives a traffic
measurement report (Event 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-DSCH and E-DCH.
The cell load is not overloaded. (Note: For details about overload threshold,
refer to ZTE UMTS Overload Control Feature Guide.)
2. CELL_DCH to CELL_FACH switching triggered by load

the cell load.
3. The services are interactive or background services.
The cell downlink load exceeds the overload threshold. (Note: For details about
overload threshold, refer to ZTE UMTS Overload Control Feature Guide.)
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-DSCH/UL E-DCH can be triggered by the measurement report (Event 4A)
from the user plane or UE to increase the system capacity.
Measurement.
The switching from DL DCH/UL DCH to DL HS-DSCH/UL E-DCH is triggered in the case
of the following conditions:

4A) on the downlink DCH or uplink DCH independently from the user plane or UE.
(Note: if the system receives a traffic measurement report (Event 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 Event 1F.
Both the UE and system support HS-DSCH 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. (Note: The parameter HsupaCmAssoMode indicates the HSUPA associate
compressed mode method. For more details, refer to ZTE UMTS handover Control
Feature Guide.)
Note: DL HS-DSCH/UL E-DCH cannot switch to DL DCH/UL DCH based on traffic

volume measurement.
The concurrent services during channel switching are processed by the following
principles:
If all the concurrent services are PS services and one service triggers the switching
from DL DCH/UL DCH to DL HS-DSCH/UL E-DCH, the DL DCH/UL DCH of all
services is switched to DL HS-DSCH/UL E-DCH.
If there is conversation service in the concurrent services and the UE is capable of

implementing the DL DCH/UL DCH and DL HS-DSCH/UL E-DCH concurrency, the
DL DCH/UL DCH of PS services is switched to DL HS-DSCH/UL E-DCH; otherwise,
the switching is not implemented.
Note:
When the downlink DPCH and HS-PDSCH coexist, the maximum rate 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 the DL DCH/UL DCH, the UE triggers Event 4A and meets the
conditions for DL DCH/UL DCH -> DL HS-DSCH/UL E-DCH switching, but the DL
HS-DSCH or UL E-DCH fails to admit or the DL HS-DSCH or UL E-DCH is not supported,
select UL DCH rate increase. In the case of UL DCH rate increase, the other conditions
of R99 UL DCH rate increase must be satisfied (see UL DCH -> UL DCH (rate increase)).
If the service is on the DL DCH/UL DCH, the user plane triggers downlink Event 4A and
meets the conditions for DL DCH -> DL HS-DSCH switching, but the DL HS-DSCH fails
to admit or the DL HS-DSCH 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-DSCH/UL E-DCH -> DL DCH/UL DCH triggered by channel

quality
When a subscriber uses the DL HS-DSCH/UL E-DCH, the DL HS-DSCH/UL E-DCH

switching to DL DCH/UL DCH can be triggered by channel quality measurement (Event
1F triggered by pilot signal). This is because that the subscriber remaining on HS-DSCH
will worsen the QoS and lower the system capacity when the bit rate requirements of
streaming services carried on HS-DSCH are not satisfied and the channel quality
deteriorates.
Measurement.
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 (IBChQSwch,

SChQSwch) are open (Note: when PS S and I/B service are concurrent, if any of
IBChQSwch and SChQSwch is open, these switches are considered open).
The channel quality triggers Event 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.4 "DCH Initial Access Rate for PS Service".
3. Switching from DL HS-DSCH/UL E-DCH to DL DCH/UL DCH triggered by mobility
During the PS services carried on DL HS-DSCH/UL E-DCH, when the HSUPA UE hands

over from an HSUPA cell to R99 cell for mobility, but the target cell does not support the
HS-DSCH and E-DCH, the service channel will switch from DL HS-DSCH/UL E-DCH to
DL DCH/UL DCH. The rate is the DCH initial rate, see 3.1.2.4 "DCH Initial Access Rate
for PS Service".
over from an HSUPA 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.4 "DCH Initial Access Rate
for PS Service".
For more details about mobility, refer to ZTE UMTS Handover Control Feature Guide.
3.3.3.3 CELL_DCH (DL HS-DSCH/UL DCH) <-> CELL_DCH (DL HS-DSCH/UL

E-DCH)
1. Switching from DL HS-DSCH/UL DCH to DL HS-DSCH/UL E-DCH triggered by

traffic
When using the DL HS-DSCH/UL DCH, the UE can be switched from the DL
HS-DSCH/UL DCH to the DL HS-DSCH/UL E-DCH based on traffic volume
measurement reports (Event 4A) from the UE so as to improve the peak rate of the UE.
The switching from DL HS-DSCH/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 (Event 4B) from the 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. (Note: The parameter HsupaCmAssoMode indicates the HSUPA associate

compressed mode method. For more details, refer to ZTE UMTS Handover Control
Feature Guide.)
If the service is on the DL HS-DSCH/UL DCH, the UE triggers Event 4A and meets the
conditions for DL HS-DSCH/UL DCH -> DL HS-DSCH/UL E-DCH switching, but the UL
E-DCH fails to admit or the UL E-DCH is not supported, select UL DCH rate increase. In
the case of UL DCH rate increase, the other conditions of R99 UL DCH rate increase
must be satisfied (see UL DCH -> UL DCH (rate 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-DSCH/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
over from an HSUPA 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.4 "DCH Initial Access Rate
for PS Service".
During the PS services carried on DL HS-DSCH/UL DCH, when the HSUPA UE hands
over from an HSDPA cell to HSUPA cell for mobility and the target cell supports
HS-DSCH and E-DCH, the service channel will switch from UL DCH to UL E-DCH; the
downlink remains on the HS-DSCH.
For more details about mobility, refer to ZTE UMTS Handover Control Feature Guide.
3.3.3.4 CELL_DCH (DL HS-DSCH/UL E-DCH) -> URA_PCH/CELL_PCH
When the UE uses the CELL_DCH (DL HS-DSCH/UL E-DCH) for service bearer, the
switching from CELL_DCH (DL HS-DSCH/UL E-DCH) to URA_PCH can be triggered by
the traffic measurement report (Event 4B0) by the user plane.

The switching from CELL_DCH (DL HS-DSCH/UL E-DCH) to URA_PCH/CELL_PCH is

PchCellSwch is ON.

measurement value of 0 on the HS-DSCH and E-DCH from the user plane (Note: if
the system receives a report with measurement value of non-zero value when the
cleared.)
condition for switching to URA_PCH/CELL_PCH.
3.3.3.5 CELL_DCH (DL HS-DSCH/UL E-DCH) -> IDLE
When the UE uses the CELL_DCH (DL HS-DSCH/UL E-DCH) for service bearer, the
switching from CELL_DCH (DL HS-DSCH/UL E-DCH) to IDLE is triggered in the case of

measurement value of 0 on the HS-DSCH 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
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 to trigger 2ms E-TTI to transfer to 10ms

E-TTI, based on throughput measurement report (Event 4B).
Once the following condition is satisfied, it will trigger E-DCH (2ms E-TTI) to transfer to
E-DCH (10ms E-TTI).
The switch EttiTraffVolSwch is ON.
The system receives consecutive ETtiEbThd throughput measurement reports

(Event 4B) from the user plane. (Note: if the system receives a throughput
measurement report (Event 4A) from the user plane, the corresponding counter is
cleared.)
2 E-DCH(10ms E-TTI) -> E-DCH(2ms E-TTI)
If UL channel of user is E-DCH, It is possible to trigger 10ms E-TTI to transfer to 2ms

E-TTI, based on throughput measurement report (Event 4A).
Once the following condition is satisfied, it will trigger E-DCH (10ms E-TTI) to transfer to
E-DCH(2ms E-TTI).
The switch EttiTraffVolSwch is ON.
The system receives consecutive ETtiEaThd throughput measurement reports

(Event 4A) from the user plane. (Note: if the system receives a throughput
measurement report (Event 4B) from the user plane, the corresponding counter is
cleared.)
License Tti2msSuptInd is supported.
The 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 Transfer".

Traffic measurement on the E-DCH is to measure the uplink throughput of the E-DCH on
the FP layer through the user plane.
For a service on the E-DCH, calculate its data volume within 100 ms. Slide the window
for 20 ms, and then calculate its data volume for 100 ms again.
Method to measure parameter acquisition: Firstly obtain the Used UTrvMeasProfile

Measurement Profile Object UTrvMeasProfilebased on the value of the parameter
If the channel for service bearer is the E-DCH, the traffic volume measurement
parameters are obtained from the sub-object UDedEdchEvUpTrv. The details are listed
in the following table:
ueTrvMCfgNo Index

rptThres E-DCH Channel

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 between
2ms E-TTI and 10ms E-TTI. Throughput measurement is independent of traffic
measurement.
There is a switch EttiTraffVolSwch (Switch of E-TTI Switching Triggered by User Plane

Throughput Measurement) to control this feature.
The stop and start of throughput measurement:
As EttiTraffVolSwch is ON,
1. UE uses E-DCH as bearer, and supports 2ms TTI.
2. All the cells of active set support 2ms TTI.
3. No C class traffic is on E-DCH.
4. At least one traffic is configured with 2ms TTI.
If 10ms TTI could satisfy GBR requirement, open the throughput measurement. In other
scenes, it will not open the measurement (close the measurement once opened).
Note: The throughput is the combination of macro diversity throughputs.

Measurement Profile Object UTrvMeasProfile(UTrvMeasProfile)based on the value of
the parameter refUTrvMeasProfile, and thirdly obtain the corresponding traffic
measurement parameter based on the measurement target from the sub-object of
UTrvMeasProfile.
If the channel for service bearer is the E-DCH, when the E-DCH TTI is switched between
10ms and 2ms, the traffic volume measurement parameters are obtained from the
sub-object UETTIEdchEvUpTrv. The details are listed in the following table:
ueTrvMCfgNo Index

Throughput Measurement Threshold for E-TTI

ThoughThres Switching of Event 4A/4B for E-DCH Channel
3.4 Dual-Carrier Related Dynamic Channel Adjustment
The initial service channel allocation for dual- carrier is as follows:
When the downlink channel allocation result is HS-DSCH, both the UE and the cell
support dual-carrier, then the dual-carrier should be allocated to the UE.
Dual-carrier capability of the neighboring cell from DRNC and its secondary carrier
information can be obtained from the parameters IurDcHsdsSuptInd and
SndSvrCelID 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 Concurrent Service Channel Allocation
The concurrent service channel allocation for dual- carrier is similar to the initial service
channel allocation in 3.4.1 that is, as long as the downlink channel allocation result is
HS-DSCH, and both the UE and the cell support dual-carrier, then the dual-carrier should
be allocated to the UE.

For CS+PS, if CS service is established on DCH, and PS service is established on

dual-carrier, then CS service uses the primary carrier as bearer.
If it is from other channel switching to HS-DSCH, 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 between
dual-carrier HS-DSCH and single-carrier HS-DSCH:
1. If the 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.
2. If the HS-DSCH target cell does not support dual-carrier, then the single-carrier will
be allocated.
3.5 Enhanced FACH Dynamic Channel Adjustment
3.5.1 DL Enhanced FACH Dynamic Channel Adjustment
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-PDSCH in CELL_FACH in RRC connection request is true. That is, both cell and
UE support downlink enhanced FACH. In this case, DL HS-DSCH/UL RACH channel
bearer is selected. Otherwise, select DL FACH/UL RACH channel bearer.
Introducing DL enhanced FACH imposes no impacts to select CELL_DCH or

CELL_FACH for services initial channel. If the initial channel selection is borne in
CELL_FACH, and, if both cell and UE support DL Enhanced FACH, DL HS-DSCH/UL
RACH is selected; otherwise, select DL FACH/UL RACH channel bearer.

3.5.1.3 Channel Switching
The switching policies of DL enhanced FACH channel are:
1. The switching policy of CELL_DCH and PCH switching to CELL_FACH

(HS-DSCH/RACH) is the same as that of CELL_DCH and URA_PCH to
CELL_FACH (FACH/RACH). That is, if the switching condition to CELL_FACH is
satisfied and both cell and UE support DL Enhanced FACH, DL uses HS-DSCH to
replace FACH.
2. The switching policy of CELL_FACH(HS-DSCH/RACH) to CELL_DCH is the same

as that of CELL_FACH(FACH/RACH) to CELL_DCH.
3. The switching policy of CELL_FACH(HS-DSCH/RACH) DL non-Enhanced UE DRX

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_FACH for longer time because
Enhanced UE DRX features power saving. Those CELL_FACH adopting Enhanced
UE DRX and not adopting Enhanced UE DRX should be differentiated to switch to
PCH or Idle.
i. Traffic triggered CELL_FACH(DL HS-DSCH/UL RACH) -> PCH
Satisfying all conditions below to trigger CELL_FACH (HS-DSCH/ RACH)

switching to URA_PCH:
a) The switch PchSwch for system switching to PCH is turned on.
b) For scenarios not using Enhanced UE DRX:

measurement value of 0 by user plane and UE. (Note: if the system receives a
c) For scenarios using Enhanced UE DRX:
The system continuously receives user plane traffic measurement value 0 for
DxHsBo0E4bThd times, UE traffic measurement value 0 for FToPchThd times.
(Note: if the system receives a report with measurement value of non-zero

value when the receiving times are smaller than the threshold, the
d) If the concurrent services exist, it is required that all the services should
meet the condition for switching to PCH.
ii. Traffic triggered CELL_FACH(DL HS-DSCH/UL RACH) -> IDLE
Satisfying all conditions below to trigger CELL_FACH (HS-DSCH/ RACH)

switching to IDLE:
a) The switch PchSwch for system switching to URA_PCH is turned off.
b) For scenarios not using Enhanced UE DRX:
The system receives consecutive FToIdleThd 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 smaller than the threshold, the
c) For scenarios using Enhanced UE DRX:
The system continuously receives user plane traffic measurement value

0 for DxHsBo0E4bThd times, and UE traffic measurement value 0 for
FToIdleThd times. (Note: if the system receives a report with
measurement value of non-zero value when the receiving times are
d) If the concurrent services exist, it is required that all the services should
meet the condition for switching to IDLE.
iii. Mobility triggered CELL_FACH intra-mode channel switching
Due to the mobility, when UE adopts CELL_FACH 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 both target cell and UE support DL Enhanced FACH, DLHS-DSCH/UL

RACH channel bearer is selected; otherwise, DL FACH/UL RACH is selected.
3.5.2 UL Enhanced FACH Dynamic Channel Adjustment
During RRC signaling bearer selection, if CELL_FACH bearer is selected:
1. 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.
2. If both cell and UE support downlink enhanced FACH, while not supporting uplink
enhanced FACH, DL HS-DSCH/UL RACH channel bearer is selected.
3. Otherwise, DL FACH/UL RACH channel bearer is selected.
Introducing UL enhanced FACH imposes no impacts to select CELL_DCH or

CELL_FACH for services initial channel. If the initial channel selection is borne in
CELL_FACH, and,
1. If both cell and UE support common E-DCH, select DL HS-DSCH/UL E-DCH

channel bearer.
2. If both cell and UE support DL E-FACH, while not supporting Common E-DCH,
select DL HS-DSCH/UL RACH channel bearer.
3. Otherwise, select DL FACH/UL RACH 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 PCH switching to CELL_FACH

(HS-DSCH/E-DCH) is the same as that of CELL_DCH and URA_PCH to
CELL_FACH (FACH/RACH). 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
RACH.
The switching policy of CELL_FACH(HS-DSCH/E-DCH) to CELL_DCH is the same

as that of CELL_FACH(FACH/RACH) to CELL_DCH.
The switching policy of CELL_FACH(HS-DSCH/ E-DCH) non-Enhanced UE DRX

bearer switching to PCH and IDLE is the same as that of FACH/RACH to PCH and
IDLE, keeping unchanged. If DL uses Enhanced UE DRX, it resides on
CELL_FACH for longer time because Enhanced UE DRX features power saving.
Those CELL_FACH adopting Enhanced UE DRX and not adopting Enhanced UE
DRX should be differentiated to switch to PCH or Idle.
Traffic triggered CELL_FACH(DL HS-DSCH/UL E-DCH) -> PCH
Satisfying all conditions below to trigger CELL_FACH (HS-DSCH/E-DCH) switching to

URA_PCH:
The switch PchSwch for system switching toPCH is turned on.
For scenarios not using Enhanced UE DRX:

measurement value of 0 by user plane of HS-DSCH and E-DCH channels in
CELL_FACH (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.)
For scenarios using Enhanced UE DRX:
The system receives consecutive DxHsBo0E4bThd traffic measurement reports with


is cleared.)
condition for switching to PCH.
Traffic triggered CELL_FACH(DL HS-DSCH/UL E-DCH) -> IDLE
Satisfying all conditions below to trigger CELL_FACH (HS-DSCH/E-DCH) switching to

IDLE:
The switch PchSwch for system switching to PCH is turned off.
For scenarios not using Enhanced UE DRX:
The system receives consecutive FToIdleThd traffic measurement reports with

CELL_FACH. (Note: if the system receives a report with measurement value of non-zero
is cleared.)
For scenarios using Enhanced UE DRX:
The system receives consecutive DxHsBo0E4bThd traffic measurement reports with

is cleared.)
Mobility triggered CELL_FACH intra-mode channel switching
Due to the mobility, when UE adopts CELL_FACH 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-DSCH/UL E-DCH channel
bearer is selected; otherwise, if both target cell and UE support DL Enhanced FACH,
while not supporting Common E-DCH, then select DL HS-DSCH/UL RACH channel
bearer; otherwise, select DL FACH/UL RACH channel bearer.
3.5.3 Traffic Measurement
The traffic measurement on CELL_FACH (HS-DSCH/E-DCH) is the same as that of

CELL_DCH (HS-DSCH/E-DCH). For more details, refer to 3.2.4.2 Traffic Measurement
and 3.3.4.1 Traffic Measurement.

Object UTrvMeasProfile(UTrvMeasProfile) based on the value of the parameter
If the channel for service bearer is the CELL_FACH(HS-DSCH), the traffic volume
measurement parameters are obtained from the sub-object UComHsdschEvUpTrv.
If the channel for service bearer is the CELL_FACH(E-DCH), the traffic volume
measurement parameters are obtained from the sub-object UComEdchEvUpTrv.
3.6 Fast Dormancy
3.6.1 R8 Fast Dormancy
In order to save the battery consumption, for some smart phones whose versions are
3GPP Release 7 or Pre-Release 7, once the data transmission ends, they will send the
message Signaling Connection Release Indication (SCRI ), upon receiving the SCRI,
the network has no other choice than to release the Iu signaling and RB connection. This
process is called Pre-R7 Fast Dormancy. When there are data packages to be
transmitted again, they will re-establish the RRC connection, and re-establish RB/RAB.
This frequent data transmission will cause frequent network connection and release, and

produce many signaling messages, and it is easy to cause signaling storm phenomenon.
An example of the channel switch with Pre-R7 fast dormancy is shown in Figure 3-8.
Figure 3-8 Channel switch with Pre-R7 fast dormancy
Data Packet
CELL_DCH
CELL_FACH
URA_PCH
IDLE
SCRI causes UE SCRI causes UE SCRI causes UE

switch to Idle switch to Idle switch to Idle
To overcome this problem, 3GPP Release 8 introduces a simple UE signaling to indicate

the state of UE for the network. A new UE information element (IE) "Signaling
Connection Release Indication Cause" was added to the SCRI, and is used to indicate
that the UE has decided to stop an activated PS data transmission. When the UE wants
to release the PS session, it must first ask the network by the IE. On receiving the IE,
UTRAN can decide to trigger an RRC state handover to URA_PCH. This significantly
reduces the signaling load on the network.
The network can control the using of this function by configuring and sending a T323
timer in SIB1, and the UE shall be inhibited from sending the SCRI message with the IE
"Signaling Connection Release Indication Cause" set to "UE Requested PS Data
session end" whilst timer T323 is running. There is a parameter T323Swch to control
whether to configure T323 in SIB1. Without receiving T323, UE would not send SCRI
with cause UE requested PS data session end. An example of the channel switch with
R8 fast dormancy is shown in Figure 3-9.

Figure 3-9 Channel switch with R8 fast dormancy
Data Packet
CELL_DCH
CELL_FACH
T323 T323
URA_PCH
IDLE
R8 Fast Dormancy
4B causes UE switch 4B causes UE switch
causes UE switch to
to FACH to FACH
PCH
Note:
(1) The UE shall be inhibited from sending the SCRI message with the IE "Signaling
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 SCRI message
again. But some tests confirm that some UEs will not report SCRI message again
when timer T323 expires.
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 follows:
PchSwch is 1:Only Support URA_PCH.
PchCellSwch is on.
The value of the PCH switch that the UEs version corresponds to is 0. For details,
please refer to 3.7.8 UE PCH Compatibility Strategy.
The value of the parameter GResPara4 bit3/ bit4/bit5/bit6/bit7 that the UEs
version is corresponding to is 0.

Receive message signaling connection release indication which includes the IE

"signaling connection release indication cause with the value of UE requested PS
data session end.
If these conditions are satisfied, RNC will trigger channel switch to URA_PCH. If PCH is
off, UE will be switched to Idle.
Note: GResPara4 bit3/ bit4/bit5/bit6/bit7 is used to control the target RRC state of R8
Fast Dormancy for R99/R5/R6/R7/R8 UE separately.
3.6.1.2 SCRI Trigger Channel Switching to CELL_FACH
The conditions of channel switching from CELL_DCH to CELL_FACH triggered by UE

SCRI are as follows:
FachSwch is 1:On.
The value of the parameter GResPara4 bit3/ bit4/bit5/bit6/bit7 that the UEs
version is corresponding to is 1.
Receive message signaling connection release indication which includes the IE

"signaling connection release indication cause with the value of UE requested PS
data session end.
If these conditions are satisfied, RNC will trigger channel switch to CELL_FACH. If
CELL_FACH is off, UE will be switched to PCH; If PCH is off, UE will be switched to Idle.
Note: When T323Swch is on, it is recommended to turn on the PCH state.
3.6.2 Pre-R7 Fast Dormancy Suppressing
As described in 3.6.1 R8 Fast Dormancy, Pre-R7 Fast Dormancy causes frequent

network connection and release, produces many signaling messages, and easily causes
signaling storm phenomenon. Although 3GPP have added the R8 fast dormancy, it
cannot handle with the UE before Release 8.
For the situation, the function based on the heart beat strategy of the user plane is added.
It can avoid UE sending the message SCRI based on heartbeat detection, and avoid the

frequent signaling connection and release, so the function is also called Pre-R7 Fast
Dormancy Suppressing.
3.6.2.1 Heart Beat Strategy of the User Plane
In order to avoid the UE whose version is 3GPP Release 7 or Pre-Release 7 sending the
message Signaling Connection Release Indication, and avoid the frequent signaling
connection and release. The heart beat strategy is performed for the UE that can meet
1. The value of the parameter heartBeatUeVerR4/heartBeatUeVerR5/

heartBeatUeVerR6 / heartBeatUeVerR7/ heartBeatUeVerR8 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 DeviceTypeInd is "1: true, the condition "The IE" RRC Connection
Setup Complete. UE radio access capability Device type is not present or its value
is not doesNotBenefitFromBatteryConsumptionOptimisation should be also
satisfied. If DeviceTypeInd is "0: false, then there is no need to judge the reported
"Device 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 the UE with the
period HeartBeatFreq, the UE observes it have data to be received, and will not send
SCRI message. The heart beat data is not included in the traffic volume measurement
result of the user plane. When there are data package interactions 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. And when UE does not have data transmission for a long time, it
can be switched to PCH or Idle by 4B0 traffic volume measurement report.
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 cannot correctly make
judgment of the event 4B0 for uplink traffic volume measurement, and it will cause that
the channel switching to PCH or Idle state based on the traffic volume measurement
cannot be performed. In order to solve the problem, add a new parameter OnlyDnOnHB,
to control whether the channel switching to PCH or Idle state is based on the downlink
traffic volume measurement report for the UE with the heart beat detection performed.
For the UE with the heart beat detection performed, 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 does not send uplink data packages after it receives the heart beat
data, and the channel switching to PCH or Idle state based on the downlink and uplink
traffic volume measurement can be normally performed, so the parameter OnlyDnOnHB
can be set to 0:Off.
Pre-R7 Fast Dormancy Suppressing may have some negative impacts on network,
for example, it may raise the cell RTWP. So it is not recommended to turn on this
function generally.
3.7 Other Description
3.7.1 Traffic Sub-class rate matching
The CN sends necessary QoS information to the RNC by RAB assignment message. In
QoS information, it defines the related traffic information, for example, the maximal bit
rate. For the user rate control of RNC, besides the rate demand of CN, it is also
controlled by UE capability limitation and real traffic situation. The whole process is rate
matching.
The rate matching includes the following procedures:

1. Iu assignment rate matching according to UE capability
For HSPA: MaxBR1= min (max rate of Iu interface (If there is MBR negotiation, it is the
max rate after negotiation), max rate according to UE capability).
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 to the nearest sub-service in sub- service list (Match to
the sub- service whose rate is the nearest and not smaller than MaxBR1), and then
according to the matched sub-service number, it can get the parameter
configuration for this traffic. Among them, the parameter MaxBitRate is MaxBR2.
3. The max bit rate of this traffic controlled by the RNC is min (MaxBR2, max rate of Iu
interface. (If there is MBR negotiation, it is the max rate after negotiation.)
3.7.1.1 HSDPA UE Capability and the Mapping Rate of Supported MaxBR
The max rate restriction list according to UE capability is as follows:

Max bit rate supported by UE
UE capability
capability
UE HS-DSCH Physical Layer category 1 and

1.2Mbps
2
UE HS-DSCH Physical Layer category 3, 4

1.8Mbps
and 12

3.65Mbps
6

7.2Mbps
8
UE HS-DSCH Physical Layer category 9 10.1Mbps
UE HS-DSCH Physical Layer category 10 14Mbps
UE HS-DSCH Physical Layer category1 1 900kbps
Whether
supported Max bit rate supported by UE
UEcapability
64QAM by capability
Node B
UE HS-DSCH Physical Not support 10.1Mbps (Match to category 9, see

Layer Category 13 64QAM note)
Support 64QAM 17.6Mbps
Not support 14Mbps (Match to category 10, see

UE HS-DSCH Physical
64QAM note)
Layer Category 14
UE HS-DSCH Physical Not support 10.1Mbps (Match to category 9, see

UE HS-DSCH Physical Not support 14Mbps (Match to category 10, see

Not support 10.1Mbps(Match to category 9, see

UE HS-DSCH Physical
64QAM note)
Layer Category 17
Not support 14Mbps (Match to category 10, see

UE HS-DSCH Physical
64QAM note)
Layer Category 18
Note: Configuration pattern of HARQ 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 Support 10 and 2 ms TTI EDCH Max bit rate supported
Category 1 10 ms TTI only 711 kbps
10 ms TTI 1.448 Mbps

Category 2
2 ms TTI 1.448 Mbps
Category 3 10 ms TTI only 1.448 Mbps

Category 4
2 ms TTI 2.886 Mbps
Category 5 10 ms TTI only 2.048 Mbps

Category 6
2 ms TTI 5.76 Mbps

Category 7
2 ms TTI (UE not configure 16QAM) 5.76 Mbps

2 ms TTI (UE configure 16QAM) 11.52 Mbps
Note: Rate matching according to UE capability considers the factor UE category,

modulation, etc.
3.7.2 MBR Controlling in RNC
This feature relates four cell-level parameters: UlCtrlMBRSwitch, UlControledMBR,

DlCtrlMBRSwitch, and DlControledMBR.
For Uplink MBR operated in RNC:
If the value of UlCtrlMBRSwitch is 0: Off, then the Uplink MBR operated in RNC = MBR
subscribed in CN.
If the value of UlCtrlMBRSwitch is 1: Replaced Mode, then the Uplink MBR operated in
RNC = UlControledMBR.
If the value of UlCtrlMBRSwitch is 2: Minimum Mode, then the Uplink MBR operated in
RNC = min{ MBR subscribed in CN, UlControledMBR }.
If the value of UlCtrlMBRSwitch is 3: Maximum Mode, then the Uplink MBR operated in
RNC = max{ MBR subscribed in CN,UlControledMBR }.
For Downlink MBR operated in RNC:
If the value of DlCtrlMBRSwitch is 0: Off, then the Downlink MBR operated in RNC =
MBR subscribed in CN.
If the value of DlCtrlMBRSwitch is 1: Replaced Mode, then the Downlink MBR operated
in RNC = DlControledMBR.
If the value of DlCtrlMBRSwitch is 2: Minimum Mode, then the Downlink MBR operated in
RNC = min{ MBR subscribed in CN, DlControledMBR }.
If the value of DlCtrlMBRSwitch is 3: Maximum Mode, then the Downlink MBR operated
in RNC = max{ MBR subscribed in CN, DlControledMBR }.
Notes:

1. This feature is only used to modify the MBR in RNC, not related to RAB negotiation
or RAB re-negotiation.
2. For macro-diversity and mobility state, the values of UlCtrlMBRSwitch,

DlCtrlMBRSwitch, UlControledMBR, DlControledMBR get the parameter values for
the best cell when RAB sets up, not changing with best cell updating.
3.7.3 Iub Transmission Bandwidth Limitation Strategy
When constructing a network, 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 UEs affect the communication
quality in large scale, it is required to limit the maximum rate of these UEs 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, it 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 NrtMaxUlRateDch / NrtMaxDlRateDch (for NRT
service) are used to limit the DCH maximum rate of uplink and downlink respectively. For
EDCH users, the E-DCH users maximum rates are limited by the parameters
RtMaxrateEdch (for RT service) and NrtMaxRateEdch (for NRT service).
In the case of inter-RNC, for DCH users, parameters RtMaxUlRateDchD /

RtMaxDlRateDchD (for RT service) and NrtMaxUlRateDchD / NrtMaxDlRateDchD (for
NRT service) are used to limit the DCH maximum rate of uplink and downlink
respectively. For EDCH users, the E-DCH users maximum rates are limited by
parameters RtMaxRateEdchD (for RT service) and NrtMaxRateEdchD (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 rate 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 does not meet encryption
protocol
When some versions of IPHONE trigger conversation services, if the RRC connection is
established on CELL_FACH, and in the process of switching to CELL_DCH during the
RAB process, their implements are not in accordance with the encryption protocol. In that
case, they will suffer bubble noise resulted from losing alignment of CFN. In order to be
compatible with this kind of IPHONE, ZTE sets a switch CsRrcOnFachSwch to control
RRC not to be established on CELL_FACH to guarantee that UE does not attempt to
access CELL_FACH after 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 to
access to FACH/RACH is decided by CsRrcOnFachSwch. (CS service is defined by
Establish cause, which is Originating Conversational Call or Terminating Conversational
Call). If CsRrcOnFachSwch is off, RRC of CS service, which is not an emergency call,
cannot be established on FACH/RACH. An emergency call is not restricted by this
switch.
3.7.5 MaxBR of HSDPA on Iur Interface
Iur interface does not inform MaxBR of HSDPA traffic to DRNC. ZTE uses the value of Iur
interface IE TrCH Source Statistics Descriptor to decide MaxBR of HSDPA, and sets a
parameter MaxDHsRate to control the MaxBR of HSDPA traffic.
If the value of IE TrCH Source Statistics Descriptor is Speech, then MaxBR =

38.8k.
If the value of IE TrCH Source Statistics Descriptor is RRC, then MaxBR = 3.4k.
If the value of IE TrCH Source Statistics Descriptor is "Unknown, or even this IE is

absent, then MaxBR is decided by IE traffic class.
If the value of IE Traffic class is streaming, interactive or background, then

calculate MaxBR=max{MaxDHsRate1,GBR}; there into
MaxDHsRate1=min{MaxDHsRate, MaxBR of HS-DSCH supported by UE}
If the value of IE Traffic class is conversation, then MaxBR = 38.8k.
Note: MaxBR of HS-DSCH supported by UE is the max bit rate supported by UE

category.

3.7.6 Switching Timers Based on UE Capabilities
If the UE carries IE Device type in RRC Connection Setup Complete message, and
takes doesNotBenefitFromBatteryConsumptionOptimisation as its value, it concludes
that UE is insensitive to battery consumption. The UE that reports the IE Device type is
generally data-card user, who features frequent background data transmission, resulting
in 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 the required Event 4B0 report times.
The following traffic measurement-based channel switching is involved:
CELL_DCH (DL DCH/ UL DCH) -> URA_PCH
CELL_DCH (DL DCH/ UL DCH) -> IDLE
CELL_DCH (DL HS-DSCH/UL DCH) -> URA_PCH
CELL_DCH (DL HS-DSCH/UL DCH) -> IDLE
CELL_DCH (DL HS-DSCH/UL E-DCH)-> URA_PCH
CELL_DCH (DL HS-DSCH/UL E-DCH)-> IDLE
CELL_FACH (DL FACH/UL RACH) -> URA_PCH
CELL_FACH (DL FACH/UL RACH) -> IDLE
CELL_FACH (DL HS-DSCH /UL RACH) -> URA_PCH
CELL_FACH (DL HS-DSCH /UL RACH) -> IDLE
CELL_FACH (DL HS-DSCH/UL E-DCH) -> URA_PCH
CELL_FACH (DL HS-DSCH/UL E-DCH) -> IDLE
Note:
1. For the above-mentioned channel switching, if the report, whose traffic

measurement is not 0, is received before reaching the threshold times, the counter
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.
3.7.7 Voice Service Optimization for Multi-RAB
To improve CS Experience of concurrence service with CS+PS, CsPlusPsSwch is used.
CsPlusPsSwch is set to 1:on:
If CS is set up before PS, then PS is set up on DCH with the minimal DRBC rate of
DCH.
If PS is set up before CS, then PS is downgraded to DCH with the minimal DRBC
rate of DCH.
If CsPlusPsSwch is set to 0:off, this feature is not active. The formal DRBC
strategy is performed.
Notes:
In the above policy, after PS is set up on DCH or downgraded to DCH, if

GresPara50 is 0, PS data rate can be adjusted based on traffic volume
measurement; if GresPara50 is not 0, PS data rate cannot be adjusted based on
traffic volume measurement unless the timer exceeds GresPara50 (Unit: Second).
R5 UE is controlled by CsPlusPsR5UeSwch and CsPlusPsSwch at the same time,

only when both CsPlusPsR5UeSwch and CsPlusPsSwch are on, R5 UEPS service
is downgraded to DCH with the minimal DRBC rate of DCH.
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 Pre-R6 release, the PS reconfiguration from HS to DCH is

performed before the new service RB setup.
The PS downgrade to DCH is triggered by CS setup before PS, only the scene of CS
setup, RAB modify, and CS hard handover are taken into account (CS over HSPA is not
taken into account.)
For further improving CS Experience improvement of concurrence service with CS+PS,

another two features HS/E or HS/D>D/D triggered by traffic volume measurement
and PS Service Channel allocation policy for UE in the CELL_FACH/PCH State
Triggering CS Call are introduced. The details are as follows.
HS/E or HS/D>D/D triggered by traffic volume measurement
When PS service is set up on HS/E or HS/D, if CsPsSceHsToDSwch is on, the

switching from HS/E or HS/D> DL DCH/UL DCH is triggered in the case of the
following conditions:
(1) There is CS service, and CS service is set up on DCH.
(2) GresPara50 is 0, or GresPara50 is not 0, and the timer exceeds GresPara50.
(3) The system receives consecutive HsToDE4B0timeThr traffic measurement

reports with measurement value of 0 on the uplink and downlink (Note: if the
system receives a report with measurement value of non-zero value when the
cleared.)
Note:
(1) When CS service is setup successfully, GresPara50 timer is turned on.
(2) When PS service is switched to DL DCH/UL DCH, the initial DCH rate is
decided by CsPsSceDchRate.
(3) If both the switch of CsPsSceHsToDSwch and CsPlusPsSwch are on, it is

handled according to the policy of CsPlusPsSwch.

(4) In the above policy, after PS is switched to DCH, if DToHsDelaySwch is on,

PS data rate can be adjusted based on traffic volume measurement unless the
timer exceeds DToHsDelayThr. The DToHsDelayThr timer is turned on when
PS service is switched to DL DCH/UL DCH. If DToHsDelaySwch is off, PS
data rate can be adjusted based on traffic volume measurement, and it is not
required to judge the timer.
PS Service Channel allocation policy for UE in the CELL_FACH/PCH state

triggering CS call
When UE in the CELL_FACH/PCH state triggering CS call, if FchPchUeCsPsSwch is on,

PS service will be set up on DCH, and the initial DCH rate is decided by
CsPsSceDchRate; and after PS is set up on DCH, if GresPara50 is 0, PS data rate can
be adjusted based on traffic volume measurement; if GresPara50 is not 0, PS data rate
cannot be adjusted based on traffic volume measurement unless the timer exceeds
GresPara50 (Unit: Second). (When CS service is set up successfully, GresPara50 timer
is turned on.)
Note: If both the switch of FchPchUeCsPsSwch and CsPlusPsSwch are on, for the
above scene, it is handled according to the policy of CsPlusPsSwch.
3.7.8 UE PCH Compatibility Strategy
For some UEs, PCH compatibility is not well. So for the UE with PCH compatibility
problem, the state transfer to PCH is controlled by the switch.
If R99R4PchSwch is set to 0, the state transfer to PCH (URA_PCH or CELL_PCH) will

not be performed for UE with release of R99 and R4, which will transfer to idle directly
(the same as PchSwch set to 0:off). If R99R4PchSwch is set to 1, the state transfer to
PCH (URA_PCH or CELL_PCH) can be performed when PCH is on.
If GresPara52 bit0 is set to 0, the state transfer to PCH (URA_PCH or CELL_PCH) will
not be performed for UE with release of R5, which will transfer to idle directly (the same
as PchSwch set to 0:off). If GresPara52 bit0 is set to 1, the state transfer to PCH
(URA_PCH or CELL_PCH) can be performed when PCH is on.

If GResPara4 bit0/bit1/bit2 is set to 1, the state transfer to PCH (URA_PCH or

CELL_PCH) will not be performed for UE with release of R6/R7/R8, which will transfer to
idle directly (the same as PchSwch set to 0:off). If GResPara4 bit0/bit1/bit2 is set to 1,
the state transfer to PCH (URA_PCH or CELL_PCH) can be performed when PCH is on.
3.7.9 DRBC F/P->D Performance Optimization
To solve CPU overload, the procedure optimization is done from PCH or FACH to
CELL_DCH state (the channel re-selection will not be done wholly). The strategy is as
follows:
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).
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; the
channel type selection will be done. (Note: 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.)
Note:
The aim of this strategy is to reduce the DRBC channel allocation and cell selection
procedure. However, 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.
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 set up on HS-DSCH, the cell should support
F-DPCH or E-FDPCH.
3.7.10 CELL_PCH Supporting
One of CELL_PCH or URA_PCH feature can be selected by switch PchSwch.
With the support by CELL_PCH, the state transfer to PCH is the same as the support by
URA_PCH. The difference is: when the decision to transfer state to PCH, CELL_PCH or
URA_PCH needs to be selected based on the parameter PchSwch: If PchSwch is set to
1:Only Support URA_PCH, then it is required to transfer to URA_PCH; If PchSwch is
set to 2:Only Support CELL_PCH, then it is required to transfer to CELL_PCH.
Note:
The state transfer from CELL_PCH to other state is the same as the state transfer
from URA_PCH to other state.
The state transfer between CELL_PCH and URA_PCH is not supported.
3.7.11 Video Call Prohibited in Specific Area

According to some special scenarios where CS64K service is not expected to
access/handover in a cell, parameters Cs64kSwitch and AdjCs64Switch 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 prohibited.

Initial access scene: if the switch Cs64Switch 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 Cs64kSwitch 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 does not perform any
disposal. When handover happens in inter-RNC cells and CS64k service is
covered, if AdjCs64kSwitch 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 does not perform any disposal.
If the configuration in DRNC cell and SRNC cell is not given, the cell is
defaulted to support CS64k.
3.7.12 Penalty Policy for UE that cannot Camp on PCH State
If PunishUePchSwch is1:On, when UE is switched to PCH from other state, count the
time that UE is on PCH state. If UE is switched to other channel when the time is less
than 1 second, UE will not be allowed to switch to PCH state again during the call period,
in order to avoid the ping-pong between PCH and other state.
3.8 Uplink Access Strategy for Bad E-DCH Coverage
3.8.1 Initial Channel Allocation Based on Channel Quality
When both the cell and UE capability support E-DCH, and UE will be beard on Cell_DCH
state:
If EdchBadCovSwch is 1:On, and if the poor E-DCH coverage condition that the
P-CPICH Ec/N0 UE reported is no more than BadEdchCovEcNo or the P-CPICH RSCP
UE reported is no more than BadEdchCovRscp is satisfied, the uplink channel cannot
be allowed to bear on E-DCH, and HS-DSCH/DCH is selected.

3.8.2 Switching from DL HS-DSCH/UL E-DCH to DL HS-DSCH /UL DCH

Triggered by UE Transmitted Power and Throughput Measurement
The switching CELL_DCH (DL HS-DSCH/UL E-DCH) to CELL_DCH (DL HS-DSCH/UL

DCH) is triggered in the case of the following conditions:
The switch EdchToDch6ASwch is on.
The system receives event 6A report from UE.
The system receives consecutive EToD4BtimesThr throughput measurement

reports (Event 4B) on the E-DCH from the user plane a. (Note: If the system
receives a E-DCH throughput measurement report (Event 4A) from the user
plane, the corresponding counter is cleared.)
Note: After the switching from DL HS-DSCH/UL E-DCH to DL HS-DSCH /UL DCH
triggered by UE transmitted Power and throughput measurement, it does not allow the
UE to switch to DL HS-DSCH/UL E-DCH again unless it leaves Cell_DCH state and
reenter the Cell_DCH state.
3.8.3 UE Transmitted Power Measurement for E-DCH to DCH
To stop and start of the measurement:
If EdchToDch6ASwch is on, and services use uplink E-DCH as a bearer, the

measurement is triggered. If the condition is not met, the UE TxP measurement is
switched off.
Method to measure parameter acquisition: Firstly obtain the Used UUeIntMeasProfile

(refUUeIntMeasProfile) of the cell from the management object UTRAN Cell
ObjectUUtranCellFDD, secondly obtain the corresponding UE Internal Measurement
Profile Object UueIntMeasProfile (UUeIntMeasProfile) based on the value of the
parameter refUUeIntMeasProfile, and thirdly obtain the corresponding UE Internal
Measurement parameter based on the measurement target from the sub-object
UPwrLimTPUeInt of UUeIntMeasProfile:
UE Transmitted Power Event Report Object ID for Power
UPwrLimTPUeInt
Limitation Judgment

UE Transmitted Power Event Report Object ID for Power

UPwrLimTPUeInt
Limitation Judgment
3.8.4 Throughput Measurement for E-DCH to DCH
To stop and start of the measurement:
If EdchToDch6ASwch is on, and services use uplink E-DCH as a bearer, the

measurement is triggered. If the condition is not met, the throughput measurement is
switched off.

Object UTrvMeasProfile (UTrvMeasProfile) based on the value of the parameter
based on the measurement target from the sub-object UEdchtoDchUpTrv of
UTrvMeasProfile:
UTrvMeasProfile Traffic Volume Measurement Profile Object ID
E-DCH Throughput Measurement Configuration

Object ID for HS-DSCH/E-DCH to HS-DSCH/DCH
UEdchtoDchUpTrv Switching

ueTrvMCfgNo Index

UTrvMeasProfile Traffic Volume Measurement Profile Object ID
E-DCH Throughput Measurement Threshold of

Event 4A/4B for HS-DSCH/E-DCH to
ThoughThres HS-DSCH/DCH Switching
3.9 Application Aware DRBC Enhancement
3.9.1 Analysis of DPI Service Feature
3.9.1.1 Brief Introduction to DPI
Deep Packet Inspection (DPI) is a flow inspection and control technology based on
services identity of application layer. When IP packet, TCP or UDP data goes through the
DPI management system, it regroups the application layer information of OSI seven
layers by deeply inspecting IP packet payload, to get the whole application contents and
obtain the type of service.
When getting the service type, RAN is able to use different QoS policies for different
services, improving radio resources utilization on the basis of ensuring user experience.
3.9.1.2 Influence of Algorithm
When obtaining DRBC related parameters:
If parameters DpiSwitch and DpiDrbcSwch are enabled, DRBC related parameters are
obtained in terms of service type DPI identifies. That is, after DPI identifies service type:

firstly obtain the Dynamic Radio Bearer Control Information Profile Object UdrbcProfile
(UDrbcProfile, drbcStragyName) based on the value of refUDpiAppSrv and
refUDrbcProfile in UDpiDrbc, and then obtain the DRBC parameters related in
UDrbcProfile.
If parameters DpiSwitch or DpiDrbcSwch is disabled, or both of them are enabled but

DPI does not identify the service type, that is, the DRBC parameters not using DPI DRBC
scenario firstly obtain the Dynamic Radio Bearer Control Information Profile Object
UdrbcProfile (UDrbcProfile, drbcStragyName) based on the value of refUDrbcProfile in
ULogicalRnc, and then obtain the DRBC parameters related in UDrbcProfile.
During DRBC channel migration, for concurrent services, DRBC related parameters take
Drbc parameters indexed by the service in the highest basic priority (if DPI QoS is
enabled at the same time, the basic priority is the one after DPI BP mapping); if there are
several services in the highest priority, randomly select one.
3.10 DRBC Strategy for QChat
3.10.1 Initial Channel Allocation
3.10.1.1 Channel Allocation of Signaling
Channel allocation of Signaling adopts the original strategy after introducing Qchat. For
more details, refer to 3.1.2.1 Signaling Channel Allocation.
3.10.1.2 Channel Allocation of Service
3.10.1.2.1 Channel Allocation of Initial Service
For QChat:
If [channel quality is non-1F] is satisfied, the DL HS-DSCH/UL E-DCH is preferred; if

selecting DL HS-DSCH/UL E-DCH fails (such as UL E-DCH admission failure), select DL
HS-DSCH/UL DCH; if selecting DL HS-DSCH/UL DCH fails (such as DL HS-DSCH
admission failure), select DL DCH/UL DCH.

Otherwise, directly select DL DCH/UL DCH.
Note: When QChat is established on DCH, it is accessed at min DRBC rate. Because
QChat has GBR rate, the GBR in min DRBC rate formula takes the UlGBR and DlGBR
instead of taking 0 as I/B service directly.
3.10.1.2.2 Channel Allocation of Concurrent Service
When QChat is concurrent with other PS services, the channel configuration of other PS
services is in accordance with that of Qchat.
When QChat is concurrent with other CS services, the channel allocation strategy uses
that of the original CS+PS channels, keeping unchanged.
3.10.2 Channel Switch
For QChat UE, if there is no uplink and downlink data transmission during
Tqchatdormancy, UE is allowed to migrate from CELL_DCH state to other RRC state.
Maintennance of TQchatdormancy timer: When inspecting that Qchat RB has no uplink

and downlink data transmission, enable the timer; Once it has data transmitted, clear the
timer. (During the actual coding implementation, when receiving Event 4B0, enable
Tqchatdormancy; when receiving non 4B0 service measuring event, clear the timer.)
After introducing QChat service, the channel migration strategy of QChat is updated as
follows:
3.10.2.1 CELL_DCH -> CELL_FACH
For CELL_DCH -> CELL_FACH of QChat, the following decision is made on the basis of
introducing QChat: Migrating QChat service from CELL_DCH to CELL_FACH should
satisfy the following two conditions at the same time.
QChat has other concurrent services that satisfy the conditions to migrate to
CELL_FACH.
TQchatdormancy timer times out.

The following channel migrations are involved.
CELL_DCH (DL DCH/ UL DCH )-> CELL_FACH
CELL_DCH (DL HS-DSCH/ UL DCH )-> CELL_FACH
CELL_DCH (DL HS-DSCH/ UL E- DCH )-> CELL_FACH
Note:
For concurrent services, other services migrating from CELL_DCH to CELL_FACH

should satisfy the requirements introduced before Qchat. For more details, refer to
3.1.3.5 "CELL_DCH(DL DCH/ UL DCH) <-> CELL_FACH(DL FACH/UL RACH)",
3.2.3.1 "CELL_DCH(DL HS-DSCH/UL DCH) <-> CELL_FACH", 3.3.3.1
"CELL_DCH (DL HS-DSCH/UL E-DCH) <-> CELL_FACH".
When QChat has no concurrent services, it is required to directly decide whether to

migrate to URA_PCH.
3.10.2.2 CELL_FACH -> CELL_DCH
For Qchat UE in CELL_FACH state, once detecting Qchat has uplink and downlink data
transmitted, migrate it to CELL_DCH, if the cell is in non-overload state; channel
allocation strategy after going in CELL_DCH is the same as that when Qchat is
established.
3.10.2.3 CELL_DCH -> PCH
For CELL_DCH -> URA_PCH of QChat, the following decision is made on the basis of
introducing QChat: Migrating QChat service from CELL_DCH -> URA_PCH should
satisfy the following two conditions at the same time.
TQchatdormancy timer times out.
The following channel migrations are involved:
CELL_DCH (DL DCH/ UL DCH )-> PCH

CELL_DCH (DL HS-DSCH/ UL DCH )-> PCH
CELL_DCH (DL HS-DSCH/ UL E- DCH )-> PCH
Note: If there are concurrent services, all services should satisfy the conditions to migrate
to PCH at the same time. (For concurrent services, conditions that other services
migrating CELL_DCH to URA_PCH should satisfy are the same as that before
introducing Qchat. For more details, refer to 3.1.3.6 "CELL_DCH (DL DCH/UL DCH ) ->
URA_PCH/ CELL_PCH", 3.2.3.3 "CELL_DCH (DL HS-DSCH/UL DCH) -> URA_PCH/
CELL_PCH", 3.3.3.4 "CELL_DCH (DL HS-DSCH/UL E-DCH) ->
URA_PCH/CELL_PCH".
3.10.2.4 PCH -> CELL_DCH
For Qchat, when UE in PCH state initiates cell update (temporary CELL_FACH) because
there is uplink data transmitted, or downlink data transmitted (paging), or new service
establishment request, the system directly transfers UE to CELL_DCH.
3.10.2.5 Other States->Idle
Qchat UE does not migrate from other states (Cell_DCH, Cell_FACH and PCH) to Idle
except when it is actively released in principle. That is, Qchat UE is always online. But
the migration to Idle is allowed in the following scenarios:
If other conditions are satisfied to migrate to PCH, only the best link does not meet
the requirement because it lies in D side, Qchat UE is directly migrated to Idle.
Or, if migration to PCH fails because the switch PchSwch is turned off, on the basis
of satisfying the requirements of migrating to idle before introducing QChat, and
TQchatdormancy timer times out, perform the migration to Idle; when there are
concurrent services, all services should satisfy the requirements which are the
same as that before introducing QChat.
3.10.3 Strategy for Qchat UE when its non-Qchat RB2 service has no traffic
When parameter NonQchatPsRelInd is 1:True:

For Qchat UE in cell_ Dch or cell_ Fach state, if there is concurrent I/B service which is
not Qchat RB2, and the system receives consecutive NQchatRel4B0Times traffic
measurement reports with measurement value of 0 (4B0) for the concurrent non-Qchat
RB2 service, the concurrent non-Qchat RB2 service will be released.
3.11 Whether to decide Event 1F when service is

established on HSPA
When service is borne on HSPA channel, if Event1fHsInd selects 1: True, and the
current channel satisfies the condition of [channel quality is non 1F event], HSPA
channel is allowed to access. Otherwise, the access is prohibited. If Event1fHsInd
selects 0: False, it is not required to judge the current channel quality.
4 Parameters and Configurations
4.1 DRBC Related Parameters
4.1.1 Parameter List
Dynamic Radio Bearer Control Information Profile Object

Abbreviated Name Parameter Name
drbcStragyName Drbc Strategy Name
UDrbc Dynamic Radio Bearer Control Information Object ID
Event 4B Counter Threshold for HSPA Using

dxHsBo0E4bThd DTX/DRX or CELL_FACH using DRX to PCH or IDLE
Shared by Uplink and Downlink
Event 4A Counter Threshold for CELL_FACH to

fachE4aThd
CELL_DCH Shared by Uplink and Downlink
Event 4A Counter Threshold for Increasing Rate on

dchE4aThd
DCH or DCH->HSPA
Event 4B Counter Threshold for Decreasing Rate on

dchE4bThd
DCH

Event 4B Counter Threshold for CELL_DCH to PCH

dToPchThd
Event 4B Counter Threshold for CELL_FACH without

fToPchThd
DRX to PCH Shared by Uplink and Downlink
Event 4B Counter Threshold for CELL_DCH to Idle

dToIdleThd
Event 4B Counter Threshold for CELL_FACH without

fToIdleThd
DRX to Idle Shared by Uplink and Downlink
pchHoldTimeThr Time Threshold for CELL_PCH or URA_PCH to Idle
Event 4B Counter Threshold for Cell_Dch to

dToFachThd
Cell_FACH
Event 4A Counter Threshold for E-TTI Switching from

ettiEaThd
10ms to 2ms
Event 4B Counter Threshold for E-TTI Switching from

ettiEbThd
2ms to 10ms
Event A Counter Threshold for PS on DL DCH or DL

dtcpEaThd
AMR Decreasing Rate on D-TCP
Event B Counter Threshold for Restriction PS

dtcpEbThd Increasing Rate on DL DCH or Triggering DL AMR
Increasing Rate Based on D-TCP
fachSwch Switch of Transferring to CELL_FACH
pchSwch Switch of URA_PCH/CELL_PCH Support
Increment Times of Event 4B0 for UE Which is Not

deltaNumE4B0Thd Sensitive for Battery Consumption Transferred to
URA_PCH or Idle State
RNC Configuration Object

Type of Transport Channel for Initial RRC Connection

InitRrcOnDch
Setup
Switch of Non Emergency CS Service Access to

CsRrcOnFachSwch
CELL_FACH On RRC
heartBeatUeVerR4 The Target of UE Version for Heart Beat(R4)

HeartBeatFreq Heart Beat Period
The Switch Indicates whether Only Judge the Downlink

OnlyDnOnHB
Traffic on Heart Beat for Channel Switching to PCH/IDLE
Wait Timer for Adjusting Uplink and Downlink

UpUdRecfgTimer
Reconfiguration by One Step Upward
Wait Timer for Adjusting Uplink and Downlink

DnUdRecfgTimer
Reconfiguration by One Step Downward
Delay Time Threshold of D/D->HS/D or HS/E after HS/D or

DToHsDelayThr
HS/E ->D/D Triggering by Channel Quality
r99R4PchSwch Switch of URA_PCH for UE of Release 99 and Release 4
UE's Device Type Condition Whether to be Judged

deviceTypeInd
Indicator when Heart Beat Detection
E-DCH Throughput Measurement Event 4B Counter

Threshold for the HS-DSCH/E-DCH to HS-DSCH/DCH
EToD4BtimesThr Switching
GresPara48 Global Reserved Parameter 48
GresPara52 Global Reserved Parameter 52
Logic RNC Configuration Object

ulRateAdjLevNum Uplink Rate Adjustment Level Number
ulRateAdjLev Uplink Rate Adjustment Level
dlRateAdjLevNum Downlink Rate Adjustment Level Number
dlRateAdjLev Downlink Rate Adjustment Level
refUDrbcProfile Used UDrbcProfile
amrOverHspaSwch Switch of CS voice over HSPA
drbcSwch DRBC Method Switch
ettiTraffVolSwch Switch of E-TTI Switching Triggered by User Plane

Throughput Measurement
dlPwrDasf Switch for DL DCH Rate Adjustment Based on D-TCP

ulPwrDasf Switch for UL DCH Rate Adjustment Based on UE

Transmission Power
rfach Downlink Maximum Rate Threshold of I/B Service on

CELL_FACH
rrach Uplink Maximum Rate Threshold of I/B Service on RACH
dchAdjRateSwch Switch for DCH Rate Adjustment Based on Traffic Volume

Measurement
iBChQSwch HS/D->D/D or HS/E->D/D Based on Quality Measurement

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

Switch for S Traffic
cRateThrd C Traffic Rate Threshold Used for Determining NRT PS Rate

Upper Limit
ulPsRateLmtLowC NRT PS Traffic Uplink Rate Upper Limit When Low Rate C
Traffic+ PS Traffic
dlPsRateLmtLowC NRT PS Traffic Downlink Rate Upper Limit When Low Rate C
Traffic+ PS Traffic
ulPsRateLmtHighC NRT PS Traffic Uplink Rate Upper Limit When High Rate C
Traffic+ PS Traffic
dlPsRateLmtHighC NRT PS Traffic Downlink Rate Upper Limit When High Rate C
Traffic+ PS Traffic
srbOnEdchSwch Switch of supporting SRB on E-DCH
cChQSwch Quality Measurement Switch for VoIP/ CS Voice
initialRateUl Initial Rate of UL DCH
initialRateDl Initial Rate of DL DCH
dchSig68Swch Switch of 6.8kbps Signaling Using on DCH
csPlusPsSwch Switch of PS Service Channel Allocation for Concurrent

CS+PS
r6MulRabRcfgMeth Online-already Service Reconfiguration Method for UE of

Release 6 and after Release 6 When Multi-RAB
dpiDrbcSwch Switch of Dynamic Radio Bearer Control Based on DPI
nonQchatPsRelInd Non QChat RB2 Whether to be Released Indicator When It is

no Traffic Volume
nQchatRel4B0Times Event 4B0 Counter Threshold for the Release of Qchat UE's
Non-Qchat-RB2 PS Service(Shared by Uplink and Downlink)
fourEChAllowedInd Four E-DPDCHs Allowed Indicator
punishUePchSwch Switch of whether to Punish the UE that cant Camp on PCH

state
UTRAN Cell Object

Maximum Allowable Rate on DCH to be Increased to

MaxRateMD
When UE is in Macro Diversity(kbps)
Cs64Switch Switch of CS 64kbps Establishment
Maximum Bit Rate on UL DCH for NRT PS RAB in

NrtMaxUlRateDch
Serving Cell
Maximum Bit Rate on DL DCH for NRT PS RAB in

NrtMaxDlRateDch
Serving Cell
Maximum Bit Rate on UL DCH for RT PS RAB in

RtMaxUlRateDch
Serving Cell
Maximum Bit Rate on DL DCH for RT PS RAB in

RtMaxDlRateDch
Serving Cell
UlCtrlMBRSwitch UL Controlled MBR Switch
DlCtrlMBRSwitch DL Controlled MBR Switch
UlControledMBR UL Controlled MBR
DlControledMBR DL Controlled MBR
CResPara4 Cell Reserved Parameter 4
FdpchSuptInd Cell F-DPCH Support Indicator
EfdpchSupInd Cell Enhanced F-DPCH Support Indicator
refUTrvMeasProfile referenced UTrvMeasProfile
refUUeIntMeasProfile referenced UUeIntMeasProfile
PchCellSwch Cell Level PCH Switch
Switch of the Uplink Channel Allocation Strategy For

badEdchCovSwch Bad Coverage
badEdchCovEcNo P-CPICH Ec/No Threshold for Bad E-DCH Coverage

badEdchCovRscp P-CPICH RSCP Threshold for Bad E-DCH Coverage
Switch of the HS-DSCH/E-DCH to HS-DSCH/DCH

Channel Switching Triggered by UE Transmitted
edchToDch6ASwch Power and Throughput
P-CPICH Ec/No Threshold to Decrease AMR Initial

badCovEcNo Access Rate
badCovRscp Bad Coverage P-CPICH RSCP Threshold
External UTRAN Cell Object

Switch of CS 64kbps Establishment for External UTRAN

AdjCs64Switch
Cell
Maximum Bit Rate on UL DCH for NRT PS RAB in External

NrtMaxUlRateDchD
UTRAN Cell
Maximum Bit Rate on DL DCH for NRT PS RAB in External

NrtMaxDlRateDchD
UTRAN Cell
Maximum Bit Rate on UL DCH for RT PS RAB in External

RtMaxUlRateDchD
UTRAN Cell
Maximum Bit Rate on DL DCH for RT PS RAB in External

RtMaxDlRateDchD
UTRAN Cell
IurDcHsdsSuptInd Dual-Cell HS-DSCH Support Indication
SndSvrCelID Possible Secondary Serving Cell ID
Hspa Configuration Object

Indicator for Whether to Judge Event 1F Condition

event1fHsInd
When the Service is Setup on HSPA
HsdpaIurMBR Maximum Bit Rate of HSDPA Across Iur Interface
RncFdpchSupInd RNC F-DPCH Support Indicator
RncEfdpchSupInd RNC Enhanced F-DPCH Support Indicator
QChat Service Configuration Object

tQchatdormancy QChat Dormancy Timer
nonQchatPsRelInd Indicator for Whether to Release Qchat UE's

Non-Qchat-RB2 PS service When It is no Traffic
Volume

tQchatdormancy QChat Dormancy Timer
NQchatRel4B0Times Event 4B0 Counter Threshold for the Release of Qchat

UE's Non-Qchat-RB2 PS Service, shared by Uplink and
Downlink
UE Timers and Constants Information Object

T323Swch Switch of T323 broadcasting
Waiting Time of UE Sending message

T323 SIGNALING CONNECTION RELEASE
INDICATION (with Cause) (T323)
Application Service Type Configuration Object

ulGBR Uplink Guaranteed Bit Rate
dlGBR Downlink Guaranteed Bit Rate
4.1.2 Parameter Configurations
4.1.2.1 Drbc Strategy Name
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->Global Information

Configuration ->Dynamic Radio Bearer Control Information Profile
Parameter configuration
This parameter indicates the Drbc Strategy Name.
4.1.2.2 Used UDrbcProfile
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration

This parameter indicates the used UDrbcProfile.
4.1.2.3 DRBC Method Switch
OMC path

This parameter is a switch, indicating whether dynamic radio bearer control algorithm is
used for uplink and downlink. There are four options:
0: UL Closed & DL Closed
1: UL Closed & DL Open
2: UL Open & DL Closed
3: UL Open & DL Open
This parameter controls whether to use dynamic radio bearer control for uplink and
downlink. Its default value is 3: UL Open & DL Open.
4.1.2.4 Downlink Maximum Rate Threshold of I/B Service on CELL_FACH
OMC path

This parameter indicates the downlink maximum bit rate threshold for PS service being
established on CELL_FACH. I/B service is set up initially, or is switched from DCH to
FACH, if downlink maximum bit rate or downlink target bit rate is lower than the threshold
indicated by this parameter and the uplink maximum bit rate or uplink target bit rate is
lower than the uplink maximum bit rate threshold of the PS service on the Rach.

The larger this parameter is, the easier I/B service is set up or is switched to the
Fach/Rach.
4.1.2.5 Uplink Maximum Rate Threshold of I/B Service on RACH
OMC path

This parameter indicates the uplink maximum bit rate threshold for PS service being
established on CELL_FACH. I/B service is set up initially or is switched from DCH to
RACH, if uplink maximum bit rate or uplink target bit rate is lower than the threshold
indicated by this parameter and the downlink maximum bit rate or downlink target bit rate
is lower than the downlink maximum bit rate threshold of the PS service on the FACH.
The larger this parameter is, the easier I/B service is set up or is migrated to the
Fach/Rach.
4.1.2.6 Switch of Transferring to CELL_FACH
OMC path

Configuration ->Dynamic Radio Bearer Control Information Profile->Dynamic Radio
Bearer Control Information
This parameter is a switch of other channels transferring to the Fach. When this
parameter is closed, it is not allowed to transfer from other channels to the Fach. When
this parameter is open, it is allowed to transfer from other channels to the Fach.

4.1.2.7 Switch for DCH Rate Adjustment Based on Traffic Volume Measurement
OMC path

This parameter is a switch of adjustment of rate on the DCH. When this parameter is
closed, it is not allowed to adjust the rate for PS service on the DCH. When this
parameter is open, it is allowed to adjust the rate for PS service on the DCH.
4.1.2.8 Switch for UL DCH Rate Adjustment Based on UE Transmission Power
OMC path

This parameter is the rate adjustment switch on the DCH. The switch is triggered based
on the UE transmitting power. When the parameter is OFF, the rate of PS 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.
4.1.2.9 Switch for DL DCH Rate Adjustment Based on D-TCP
OMC path

This parameter is the rate adjustment switch on the DCH. The switch is triggered based

on the D-TCP. When the parameter is OFF, the 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.10 Event 4A Counter Threshold for CELL_FACH to CELL_DCH Shared by

Uplink and Downlink
OMC path

This parameter indicates the Event 4A counter threshold for FACH->DCH/HS-DSCH or

RACH -> DCH/EDCH. For the UE on the CELL_FACH, 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 transferred from the FACH to the
DCH/HS-DSCH or from the RACH to the DCH/EDCH. And when Event 4A counter on
either the downlink or uplink reaches the threshold, a channel transfer occurs.
The larger this parameter is, the harder the UE will be transferred from
FACH->DCH/HS-DSCH or RACH->DCH/EDCH, and vice versa.
4.1.2.11 Event 4A Counter Threshold for Increasing Rate on DCH or DCH -> HSPA
OMC path

This parameter indicates 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 transferred from DCH to HSPA.
The larger this parameter is, the more slowly the UE's data rate on DCH will be increased
or UE will be transferred from DCH to HSPA, and vice versa.
4.1.2.12 Event 4B Counter Threshold for Decreasing Rate on DCH
OMC path

This parameter indicates Event 4B counter threshold for decreasing rate on DCH. For
the UE using the DCH in both directions, if the times of the measured RLC buffer payload
of the uplink and downlink being less than the 4B threshold exceed the threshold
indicated by this parameter, UEs data rate on DCH will be decreased.
The larger this parameter is, the harder UE's data rate on DCH will be decreased, and
vice versa.
4.1.2.13 Time Threshold for CELL_PCH or URA_PCH to Idle
OMC path

This parameter indicates the time threshold of UE staying in CELL_PCH or URA_PCH

for the judgment of transferring from CELL_PCH or URA_PCH to idle. If the time of UE
having stayed in URA_PCH exceeds the threshold indicated by this parameter, the UE

will be transferred from URA_PCH to Idle.
The larger this parameter is, the longer the UE will stay in URA_PCH, and the harder the
UE will be transferred from PCH to IDLE, and vice versa.
4.1.2.14 Event A Counter Threshold for PS on DL DCH or DL AMR Decreasing Rate

on D-TCP
OMC path

This parameter indicates Event A counter threshold of consecutive DTCP reports for
DTCP-DRBC. If Event A counter of DTCP reports reach the threshold indicated by this
parameter, UEs rate on downlink DCH will be decreased.
The larger this parameter is, the harder the UEs rate on downlink DCH will be decreased,
and vice versa.
4.1.2.15 Event B Counter Threshold for Restriction PS Increasing Rate on DL DCH

or Triggering DL AMR Increasing Rate Based on D-TCP
OMC path

This parameter indicates Event B counter threshold of consecutive DTCP reports for
DTCP-DRBC. If Event B counter of dedicated TCP reports reach the threshold indicated
by this parameter, UE leaves A status and turns to B status. Moreover, only traffic volume
report under B status can trigger increasing rate on DCH.

The larger this parameter is, the harder the UE leaves Event A status and turns to B
status, and vice versa. When NodeB has not left A status and turned to B status, Event
4A cannot increase the rate of the UE on the downlink.
4.1.2.16 Switch of URA_PCH/CELL_PCH Support
OMC path

This parameter indicates whether transferring to URA_PCH/ CELL_PCH is supported or

not.
4.1.2.17 Event 4B Counter Threshold for CELL_DCH to PCH Shared by Uplink and
Downlink
OMC path

This parameter indicates the threshold of Event 4B triggering times for DCH -> PCH
transition. For a user whose both uplink and downlink locate on the DCH, if the RLC
buffer loads of the uplink and downlink are 0, and the consecutive reporting times reach
this threshold, the DCH -> PCH state transition is triggered.
The higher the parameter value is, the harder the DCH -> PCH transition of the UE is
triggered, and vice versa.

4.1.2.18 Event 4B Counter Threshold for CELL_FACH without DRX to Idle Shared
by Uplink and Downlink
OMC path

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

This parameter indicates the threshold of Event 4B triggering times for CELL_DCH ->
Idle transition. For a user whose both uplink and downlink locate on the DCH, if the RLC
buffer loads of the uplink and downlink are 0, and the consecutive reporting times reach
this threshold, the DCH -> Idle state transition is triggered.
The higher the parameter value is, the harder the DCH -> Idle transition of the UE is
triggered, and vice versa.

4.1.2.20 Event 4B Counter Threshold for CELL_FACH without DRX to Idle Shared
by Uplink and Downlink
OMC path

This parameter indicates the threshold of Event 4B triggering times for CELL_FACH ->
Idle transition. For a user whose both uplink and downlink locate on the CELL_FACH, if
the RLC buffer loads of the uplink and downlink are 0, and the consecutive reporting
times reach this threshold, the CELL_FACH -> Idle state transition is triggered.
The higher the parameter value is, the harder the CELL_FACH -> Idle transition of the
UE is triggered, and vice versa.
Its default value is 2.
4.1.2.21 C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit
OMC path

This parameter defines the threshold for judging the rate level of CS service. If a CS
service rate is higher than this threshold, the service is high-rate C, or else low-rate C.
The higher the parameter value is, the smaller the possibility of the high-rate C is, and
vice versa.

4.1.2.22 NRT PS Traffic Downlink Rate Upper Limit When High Rate C Traffic+ PS
Traffic
OMCR path

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 services 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 High Rate C Traffic+ PS
Traffic
OMCR path

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 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.24 NRT PS Traffic Downlink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic
OMCR path

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 services 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.25 NRT PS Traffic Uplink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic
OMCR path

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 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.26 Type of Transport Channel for Initial RRC Connection Setup
OMC path

PGUI: Managed Element ->UMTS Logical Function Configuration
This parameter indicates the type of transport channel of signaling when initial RRC
connection sets up.
4.1.2.27 Uplink Rate Adjustment Level Number
OMC path

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.28 Uplink Rate Adjustment Level
OMC path

This parameter indicates the uplink rate adjustment levels used by DRBC. The uplink
rate adjustment can be adjusted on these levels only.
4.1.2.29 Downlink Rate Adjustment Level Number
OMC path


This parameter indicates the number of downlink rate adjustment levels used by the
DRBC. It regulates the number of down rate adjustment levels for services on the DCH.
4.1.2.30 Downlink Rate Adjustment Level
OMC path

This parameter indicates the downlink rate adjustment levels used by DRBC. The
downlink rate adjustment range can be adjusted on these levels only.
4.1.2.31 Maximum Allowable Rate on DCH to be Increased to When UE is in Macro

Diversity (kbps)
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell
This parameter indicates the maximum rate threshold allowed for the DCH when the UE
is in macro diversity. When the UE is in macro diversity, its rate on the DCH cannot
exceed the threshold. When the UE is in macro diversity and its current rate is larger
than this parameter, rate adjustment is not affected by this parameter. The larger this
parameter is, the higher the UE's rate can be adjusted to on the DCH, and vice versa.
Its default value is 384 kbps.
4.1.2.32 Switch of CS 64kbps Establishment
OMC path

This parameter defines whether a cell supports CS64K 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.33 Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell
OMC path
This parameter defines the uplink rate, the higher threshold of NRT PS services in a cell.
The higher the parameter value is, the higher the uplink rate, and the higher threshold of
users on the DCH in the cell is, and vice versa.
Its default value is 384kbps.
4.1.2.34 Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell
OMC path
This parameter defines the downlink rate, the higher threshold of NRT PS services in a
cell. The higher the parameter value is, the higher the downlink rate, and the higher
threshold of users on the DCH in the cell is, and vice versa.

4.1.2.35 Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->External Resource

Configuration->External RNC Function->External UTRAN Cell
Parameters configuration
This parameter indicates the maximum bit rate on UL DCH allowed in External UTRAN
Cell for an NRT PS domain RAB.
The default value is 384kbps.
4.1.2.36 Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell
OMC path

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

This parameter indicates the maximum bit rate on DL DCH allowed in External UTRAN
Cell for an NRT PS domain RAB.

4.1.2.38 Maximum Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell
OMC path

This parameter indicates the maximum bit rate on DL DCH allowed in External UTRAN
cell for an RT PS domain RAB.
4.1.2.39 Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell
OMC path
This parameter defines the uplink rate, the higher threshold of RT PS services in a cell.
4.1.2.40 Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell
OMC path
This parameter defines the uplink rate, the higher threshold of RT PS services in a cell.

4.1.2.41 Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell
OMC path
This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
NRT PS domain RAB.
4.1.2.42 Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell
OMC path
This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an
RT PS domain RAB.
4.1.2.43 Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell
OMC path


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

This parameter indicates the maximum bit rate on E-DCH allowed in External UTRAN
cell for an RT PS domain RAB.
4.1.2.45 Switch of CS 64kbps Establishment for External UTRAN Cell
OMC path

This parameter defines whether a RNC cell adjacent to IUR supports CS64K services.
When the parameter is OPEN, the adjacent RNC cell supports CS64K services; when
the parameter is CLOSED, the cell does not support CS64K services.
Its default value is OPEN.
4.1.2.46 Max CS Delay
OMC path

GUI: Managed Element ->UMTS Logical Function Configuration
This parameter is the max buffer delay for CS voice.
4.1.2.47 Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step
Upward
OMC path
This parameter defines the timer used for waiting UL and DL upward reconfiguration in
one step.
4.1.2.48 Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step
Downward
OMC path
This parameter defines the timer used for waiting UL and DL downward reconfiguration
in one step.
4.1.2.49 Initial Rate of UL DCH
OMC path


This parameter defines the Uplink initial rate of DCH setup traffic.
4.1.2.50 Initial Rate of DL DCH
OMC path

This parameter defines the Uplink initial rate of DCH setup traffic.
4.1.2.51 UL Controlled MBR Switch
OMCR path
GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN

Cell->Extended Info of UTRAN Cell
This parameter specifies the switch for the UL Controlled MBR function.
4.1.2.52 DL Controlled MBR Switch
OMCR path

This parameter specifies the switch for DL Controlled MBR function.
4.1.2.53 UL Controlled MBR
OMCR path


This parameter specifies the MBR value in the DL controlled MBR function.
4.1.2.54 DL Controlled MBR
OMCR path

This parameter specifies the MBR value in the DL controlled MBR function.
4.1.2.55 Cell Reserved Parameter 4
OMCR path

This parameter indicates the maximum bit rate allowed in cell for signaling.
4.1.2.56 Switch of non Emergency CS Service Access to CELL_FACH On RRC
OMCR path
This parameter indicates whether non emergency CS service access to CELL_FACH on

RRC process. If this switch is Off, it means non emergency CS service will not access

to FACH/RACH or HS-DSCH/RACH on RRC process.
4.1.2.57 Target of UE Version for Heart Beat (R4)
OMCR path
This parameter indicates the UE of Release 4 Version whether to be performed heart

beat detection.
4.1.2.58 The Target of UE Version for Heart Beat(R5)
OMCR path

beat detection.
OMCR path

beat detection.
OMCR path


beat detection.
OMCR path

beat detection.
4.1.2.62 Heart Beat Period
OMC path
This parameter indicates the period of UE heart beat.
4.1.2.63 The Switch Indicates whether Only Judge the Downlink Traffic on Heart
Beat for Channel Switching to PCH/IDLE
OMC path

This parameter indicates 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.
4.1.2.64 UE's Device Type Condition Whether to be Judged Indicator when Heart
Beat Detection
OMCR path
This parameter indicates whether to judge the IE Device type in the message RRC
Connection Setup Complete, when judge the conditions should be satisfied for UE
which is performed heart beat detection.
4.1.2.65 Global Reserved Parameter 48
OMCR path
GUI: Managed Element ->UMTS Logical Function Configuration->Global Reserved

Parameter 48
Global Reserved Parameter 48 bit8: This parameter indicates the Channel Selection
Strategy of UEs Switching from PCH to Other Channel.
0: Prefer to Cell_DCH;
1: Prefer to Cell_FACH.
OMCR path

Parameter 4

bit0: 0/1:Switch of URA_PCH/CELL_PCH for UE of Release 6. 0: Allowed; 1: Not

Allowed.
bit1: 0/1: Switch of URA_PCH/CELL_PCH for UE of Release 7. 0: Allowed; 1: Not

Allowed.
BIT2: 0/1: Switch of URA_PCH/CELL_PCH for UE of Release 8 and After Release 8. 0:

Allowed; 1:Not Allowed.
bit3: 0/1: The Target RRC State of Fast Dormancy(R99/R4). 0: prior to

URA_PCH/CELL_PCH, 1: prior to CELL_FACH.
bit4: 0/1: The Target RRC State of Fast Dormancy(R5). 0: prior to

URA_PCH/CELL_PCH, 1: prior to CELL_FACH.
bit5: The Target RRC State of Fast Dormancy(R6). 0: prior to URA_PCH/CELL_PCH,

1: prior to CELL_FACH.
Bit6: The Target RRC State of Fast Dormancy(R7). 0: prior to URA_PCH/CELL_PCH,

1: prior to CELL_FACH.
bit7:The Target RRC State of Fast Dormancy(R8). 0: prior to URA_PCH/CELL_PCH, 1:

prior to CELL_FACH.
OMCR path

Parameter 52
Global Reserved Parameter 52 bit0: If GresPara52 bit0 is set to 0, the state transfer to
PCH (URA_PCH or CELL_PCH) will not be performed for UE with release of R5,. If
GresPara52 bit0 is set to 1, the state transfer to PCH (URA_PCH or CELL_PCH) can
be performed when PCH is on.

0: Not allow R5 UE to PCH;
1: Allow R5 UE to PCH.
4.1.2.68 Switch of the RRC Connection Access Strategy For Bad Coverage
OMCR path
GUI: Managed Element ->UMTS Logical Function Configuration->Extended Info of

RNC->Switch of the RRC Connection Access
This parameter indicates the switch of the RRC connection access strategy for bad
coverage. If the parameter is "On", RRC connection will be setup on DCH with the rate of
3.4Kbps for bad coverage.
4.1.2.69 Increment Times of Event 4B0 for UE Which is not sensitive for Battery
Consumption Transferred to URA_PCH or Idle state
OMCR path

Configuration->Dynamic Radio Bearer Control Information Profile->Dynamic Radio
This parameter indicates the increment times of event 4B0 for UE which is not sensitive
for battery consumption is transferred to URA_PCH 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.70 Switch of 6.8kbps Signaling Using on DCH
OMCR path


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.71 Switch of URA_PCH for UE of Release 99 and Release 4
OMCR path
This parameter indicates whether the UE with release R99 or R4 can transfer to PCH
state.
4.1.2.72 Switch of PS Service Channel Allocation for Concurrent CS+PS
OMCR path

This parameter is used to control PS service 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 regulation. Otherwise, allocate
HS-DSCH/EDCH, HS-DSCH/DCH or DCH/DCH for PS service according to UE
capability.

4.1.2.73 Online-already Service Reconfiguration Method for UE of Release 6 and

after Release 6 When Multi-RAB
OMCR path

This parameter is used to control online-already service reconfiguration method for UE of

Release 6 and after Release 6 when multi-RAB. For the scene that it needs to
reconfigure the already online service at the same time when the setup of new service, if
the parameter 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 parameter 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.
4.1.2.74 Event 4B Counter Threshold for CELL_DCH to CELL_FACH
OMC path

Bearer Control
For the UE which is using DELL_DCH, if the measurement of the occupied of the uplink
and downlink sending buffers. This parameter indicates the event 4B counter threshold
for CELL_DCH to CELL_FACH. For the UE using CELL_DCH, if the times of the
measured RLC buffer payload of the downlink being smaller than the event 4Bs
threshold on uplink and the downlink exceed the threshold indicated by this parameter,
the UE will be transferred from CELL_DCH to CELL_FACH. For I/B traffic class, attempt

accessing CELL_DCH after failure of accessing CELL_FACH, 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_FACH, and vice versa.
4.1.2.75 HS/D->D/D or HS/E->D/D Based on Quality Measurement Switch for I/B

Traffic
OMC path

This parameter indicates whether downlink service transferring from HS-DSCH to DCH
for I/B services based on Quality Measurement is supported. This transferring is started
by 1F events according to channel quality.
When this parameter is set to open, downlink service transferring from HS-DSCH to DCH
is supported for I/B services by 1F events. When this parameter is set to Closed,
downlink service transferring from HS-DSCH to DCH is not supported for I/B services by
1F events.
4.1.2.76 HS/D->D/D or HS/E->D/D Based on Quality Measurement Switch for S

Traffic
OMC path

This parameter indicates whether downlink service transferring from HS-DSCH to DCH
for stream services based on Quality Measurement is supported. This transferring is
started by 1F events according to channel quality.

When this parameter is set to Open, downlink service transferring from HS-DSCH to
DCH is supported for stream services by 1F events. When this parameter is set to
Closed, downlink service transferring from HS-DSCH to DCH is not supported for stream
services by 1F events.
4.1.2.77 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
This parameter is defined as the delay of DCH/DCH switch to HS-DSCH/DCH or

HS-DSCH/E-DCH after being triggered by the channel quality.
The default value is 10s
4.1.2.78 Cell F-DPCH Support Indicator
OMCR path
This parameter indicates whether the cell supports F-DPCH.
4.1.2.79 RNC F-DPCH Support Indicator
OMCR path
GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->Hspa Configuration

This parameter indicates whether the RNC supports F-DPCH.
4.1.2.80 Cell Enhanced F-DPCH Support Indicator
path
This parameter indicates whether the cell supports enhanced F-DPCH.
4.1.2.81 Referenced UTrvMeasProfile
path
This parameter is the DN (Distinguish Name) of UTrvMeasProfile.
4.1.2.82 Referenced UUeIntMeasProfile
path
This parameter is the DN (Distinguish Name) of UUeIntMeasProfile.
4.1.2.83 RNC Enhanced F-DPCH Support Indicator
OMCR path


This parameter indicates whether the RNC supports enhanced F-DPCH.
4.1.2.84 Maximum Bit Rate of HSDPA Across Iur Interface
OMCR path

This parameter indicates the maximum bit rate of HS-DSCH across Iur interface.
4.1.2.85 Switch of supporting SRB on E-DCH
OMC path

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
CLOSED, both the cell and UE capability support the R6 protocol, and the UE uses the
code word of 2SF2 + 2SF4, the uplink signaling service is established on the E-DCH, or
else the uplink signaling service is established on the DCH.
4.1.2.86 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


Bearer Control
This parameter indicates Event 4B counter threshold for HSPA using DTX/DRX or
CELL_FACH using DRX to PCH or IDLE shared by uplink and downlink. For the HSPA
UE using the DTX/DRX and CELL_FACH using Enhanced UE DRX, if the times of the
measured RLC buffer payload of the uplink and downlink being zero exceed the
threshold indicated by this parameter, UE will be transferred from HSPA or CELL_FACH
to PCH or IDLE.
4.1.2.87 Switch of E-TTI Switching Triggered by User Plane Throughput

Measurement
OMC path

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.1.2.88 Event 4A Counter Threshold for E-TTI Switching from 10ms to 2ms
OMC path

Bearer Control
This parameter indicates 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.1.2.89 Event 4B Counter Threshold for E-TTI Switching from 2ms to 10ms
OMC path

Bearer Control
This parameter indicates 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.1.2.90 Four E-DPDCHs Allowed Indicator
OMC path

This parameter controls whether to use 2SF2+2SF4, in which the signaling must bear on
the E-DCH. The value 1 means it can use 2SF2+2SF4, and the value 0 means it
cannot use 2SF2+2SF4.
4.1.2.91 Switch to Punish the UE that Cannot Camp on PCH State
OMCR path

Configuration->Logic RNC Configuration->Switch of whether to punish the UE that
cannot camp on PCH state

This parameter indicates whether to punish the UE that cannot camp on PCH state.
4.1.2.92 Switch of HS-DSCH/E-DCH or HS-DSCH/ DCH to DCH/DCH, Used for

CS+PS Scene
OMCR

Configuration->Logic RNC Configuration -> Switch of HS-DSCH/E-DCH or HS-DSCH/
DCH to DCH/DCH, Used for CS+PS Scene
This parameter indicates the switch of HS-DSCH/E-DCH or HS-DSCH/ DCH to

DCH/DCH, used for CS+PS Scene. For CS+PS Scene, if this parameter is set to ON, the
PS service will be switched from HS to DCH when it has no data.
4.1.2.93 Event 4B0 Counter Threshold for HS-DSCH to DCH, Used for CS+PS Scene
OMCR path

Configuration->Logic RNC Configuration -> Event 4B0 Counter Threshold for HS-DSCH
to DCH, Used for CS+PS Scene
This parameter indicates Event 4B0 counter threshold for HS-DSCH to DCH, used for
CS+PS scene.
4.1.2.94 The DCH Rate of PS Reconfigured, Used for CS+PS Scene
OMCR path

Configuration->Logic RNC Configuration -> The DCH Rate of PS Reconfigured, Used for
CS+PS Scene

This parameter indicates the DCH rate of PS reconfigured, used for CS+PS scene.
4.1.2.95 Switch of the PS Service Channel allocation, Used for UE in the

CELL_FACH/PCH State Triggering CS Call
OMCR path

Configuration->Logic RNC Configuration -> Switch of the PS Service Channel allocation,
Used for UE in the CELL_FACH/PCH State Triggering CS Call
This parameter indicates the switch of the PS service channel allocation, used for UE in
the CELL_FACH state triggering CS Call. If the parameter is ON, when the UE in the
CELL_FACH state triggers CS Call, the PS service will be beard on DCH with the rate of
CsPsSceDchRate.
4.1.2.96 Switch of D/D->HS/D or HS/E after HS/D or HS/E ->D/D
OMCR path

Configuration->Logic RNC Configuration -> Switch of D/D->HS/D or HS/E after HS/D or
HS/E ->D/D
This parameter indicates that after switching from HS-DSCH/DCH or HS-DSCH/E-DCH

to DCH/DCH triggered by traffic volume, whether the switching from DCH/DCH to
HS-DSCH/DCH or HS-DSCH/E-DCH is allowed. If it is ON, only timer DToHsDelayThr
expires, the switching from DCH/DCH to HS-DSCH/DCH or HS-DSCH/E-DCH can be
allowed.
4.1.2.97 Switch of T323 Broadcasting
OMC path


Configuration->UE Timers and Constants Information
This parameter indicates whether the fast Dormancy is active. When the fast dormancy
switch is ON, the RNC sends T323 to UE by SIB1 and UTRAN mobility information. UE
can switch into dormancy.
4.1.2.98 Waiting Time of UE Sending message SIGNALING CONNECTION RELEASE

INDICATION (with Cause) (T323)
OMC path

Configuration->UE Timers and Constants Information
This parameter indicates the interval of UE reporting signaling connection release

indication (with cause).
4.1.2.99 Possible Secondary Serving Cell ID
OMC path

This parameter describes the Possible Secondary Serving Cell ID for the neighbor cell
over Iur.
4.1.2.100 Switch of Dynamic Radio Bearer Control based on DPI
OMCR path


This parameter is a switch, which indicates whether the dynamic radio bearer control
algorithm based on DPI is supported.
4.1.2.101 QChat Dormancy Timer
OMCR path

Configuration->QChat Service Configuration
This parameter defines the data inactivity timer for QChat. QChat UE can be switched
from Cell_DCH to other RRC state only when the TQchatdormancy expires.
4.1.2.102 Indicator for Whether to Release Qchat UE's Non-Qchat-RB2 PS Service

When It has no Traffic Volume
OMCR path

This parameter indicates whether to release Qchat UE's non-Qchat-RB2 PS service

when non-Qchat-RB2 PS service has no traffic volume.
4.1.2.103 Event 4B0 Counter Threshold for the Release of Qchat UE's
Non-Qchat-RB2 PS Service, Shared by Uplink and Downlink
OMCR path


This parameter indicates Event 4B0 counter threshold for the release of Qchat UE's
non-Qchat-RB2 PS service for, when non-Qchat-RB2 PS service has no traffic volume.
4.1.2.104 Uplink Guaranteed Bit Rate
OMCR path

Configuration->Application Service Type Configuration
This parameter indicates the Uplink Guaranteed Bit Rate.
4.1.2.105 Downlink Guaranteed Bit Rate
OMCR path

Configuration->Application Service Type Configuration
This parameter indicates the Downlink Guaranteed Bit Rate.
4.1.2.106 Indicator for Whether to Judge Event 1F Condition When the Service is Set
up on HSPA
OMCR path


This parameter indicates whether to judge Event 1F condition when the service is set up
on HSPA.
4.1.2.107 Cell Level PCH Switch
OMCR path

Cell->Extended Info of UTRAN Cell->Cell Level PCH Switch
This parameter is a switch to indicate whether transferring to URA_PCH/CELL_PCH is

supported or not in the cell. If the value is ON, the UE is allowed to transfer to
URA_PCH/CELL_PCH when there is no data to transmit in the cell. If the value is OFF,
UE is not allowed to transfer to URA_PCH/CELL_PCH when there is no data to transmit
in the cell.
4.1.2.108 Switch of the Uplink Channel Allocation Strategy for Bad Coverage
OMCR path

Cell->Extended Info of UTRAN Cell->Switch of the Uplink Channel Allocation Strategy for
Bad Coverage
This parameter indicates the switch of the uplink channel allocation strategy for bad
coverage. If the parameter is ON, when the PS service is set up on cell_DCH state, its
uplink will be set up on DCH but not E-DCH.
4.1.2.109 P-CPICH Ec/No Threshold for Bad E-DCH Coverage
OMCR path


Cell->Extended Info of UTRAN Cell-> P-CPICH Ec/No Threshold for Bad E-DCH
Coverage
This parameter indicates the P-CPICH Ec/No threshold for bad E-DCH coverage.
4.1.2.110 P-CPICH RSCP Threshold for Bad E-DCH Coverage
OMCR path

Cell->Extended Info of UTRAN Cell-> P-CPICH RSCP Threshold for Bad E-DCH
Coverage
This parameter indicates the P-CPICH RSCP threshold for bad E-DCH coverage.
4.1.2.111 Switch of the HS-DSCH/E-DCH to HS-DSCH/DCH Channel Switching Triggered by

UE Transmitted Power and Throughput
OMCR path

Cell->Extended Info of UTRAN Cell->Switch of the HS-DSCH/E-DCH to HS-DSCH/DCH
Channel Switching Triggered by UE Transmitted Power and Throughput
This parameter indicates the switch of the HS-DSCH/E-DCH to HS-DSCH/DCH channel

switching triggered by UE transmitted power and throughput. If the parameter is ON,
when the system receives consecutive EToD4BtimesThr throughput measurement
reports (Event 4B) on the E-DCH from the user plane, and Event 6A is reported by UE,
the UE will be switched from HS-DSCH/E-DCH to HS-DSCH/DCH.

4.1.2.112 E-DCH Throughput Measurement Event 4B Counter Threshold for the

HS-DSCH/E-DCH to HS-DSCH/DCH Switching
OMCR path
GUI: Managed Element ->UMTS Logical Function Configuration->Extended Info of

RNC->E-DCH Throughput Measurement Event 4B Counter Threshold for the
This parameter indicates E-DCH Throughput Measurement Event 4B Counter Threshold

for the HS-DSCH/E-DCH to HS-DSCH/DCH Channel Switching. When the system
receives consecutive EToD4BtimesThr throughput measurement reports (Event 4B) on
the E-DCH from the user plane, and Event 6A is reported by UE, the UE will be switched
from HS-DSCH/E-DCH to HS-DSCH/DCH.
4.1.2.113 Bad Coverage P-CPICH Ec/N0 Threshold
OMCR path

Cell->Extended Info of UTRAN Cell->Bad Coverage P-CPICH Ec/N0 Threshold
This parameter decides whether UE is in bad coverage area according to the reported
CPICH Ec/No value.
4.1.2.114 Bad Coverage P-CPICH RSCP Threshold
OMCR path

Cell->Extended Info of UTRAN Cell->Bad Coverage P-CPICH RSCP Threshold
This parameter decides whether UE is in bad coverage area according to the reported
CPICH RSCP value.

4.2 UE Traffic Volume Measurement Related

Parameters
4.2.1 UE Traffic Volume Event Measurement Configuration Object for

RACH
4.2.1.1 Parameter List

MeaEvtId[MAX_UE_TRV_M
EAS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE_TRV
_MEAS_EVENT] Pending Time After Trigger
rptThres[MAX_UE_TRV_ME Traffic Volume Threshold of Event 4A/4B for RACH

AS_EVENT] Channel
trigTime[MAX_UE_TRV_ME
AS_EVENT] Time to Trigger
txInterCfgPre[MAX_UE_TRV
_MEAS_EVENT] Tx Interruption After Trigger Configuration Tag
txInterruption[MAX_UE_TRV
_MEAS_EVENT] Tx Interruption After Trigger

4.2.1.2 Parameter Configuration
4.2.1.2.1 UE Traffic Volume Measurement Configuration Index
OMC path

Configuration->Measurement Configuration->Traffic Volume Measurement Profile->UE
Traffic Volume Event Measurement Configuration for RACH
This parameter indicates the UE traffic volume measurement configuration index.
4.2.1.2.2 Event Number of UE Traffic Volume Measurement
OMC path

This parameter indicates the 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.2.1.2.3 UE Traffic Volume Measurement Event Identity
OMC path


This parameter indicates the event identity of the traffic volume measurement performed
by UE. Since there are two kinds of measurement events in each traffic volume
measurement, measurement event entities are 4A and 4B.
4.2.1.2.4 Traffic Volume Threshold of Event 4A/4B for RACH Channel
OMC path

This parameter indicates the reporting threshold of Events 4A and 4B for traffic volume
measurement on RACH channel. If the traffic volume becomes larger than the threshold
of Event 4A, a report of Event 4A will be triggered; and if the traffic volume becomes
smaller than the threshold of Event 4B, a report of Event 4B will be triggered.
4.2.1.2.5 Time to Trigger
OMC path

This parameter indicates the time difference between having detected the event
generation and reporting the event. Only when the event generation is detected and still
meets all requirements of event triggering after Time to trigger, the event can be
triggered and reported.
4.2.1.2.6 Pending Time after Trigger
OMC path


This parameter indicates the pending time after the trigger. The UE is then prohibited to
send new measurement reports triggered by the same event during this time period.
4.2.1.2.7 Time Interval for Taking an Average or a Variance
OMCR path

This parameter indicates the time interval for taking an average or a variance, which is
only valid when the measurement quantity is Average RLC buffer payload or Variance
of RLC buffer payload.
4.2.1.2.8 Measurement Report Transfer Mode
OMCR path

This parameter indicates the RLC mode of the traffic volume measurement report. If the
value is AM RLC, RNC can request UE for retransmission after receiving the error SDU
label (not continuous). If the value is UM RLC, the retransmission is not required.

4.2.1.2.9 Measurement Quantity
OMCR path

This parameter indicates the measurement quantity of the traffic volume measurement
that UE performs.
4.2.1.2.10 RLC Buffer Payload for Each RB
OMCR path

This parameter indicates whether the report of RLC buffer payload for each radio bear is
requested or not.
4.2.1.2.11 Average of RLC Buffer Payload for Each RB
OMCR path

This parameter indicates whether the report of average of RLC buffer payload for each
radio bear is requested or not.

4.2.1.2.12 Variance of RLC Buffer Payload for Each RB
OMCR path

This parameter indicates whether the report of variance of RLC buffer payload for each
4.2.1.2.13 Tx Interruption After Trigger Configuration Tag
OMCR path

This parameter indicates whether Tx interruption after the trigger is configured or not.
Where, MAX_UE_TRV_MEAS_EVENT is the maximum number of UE traffic volume

measurement event, which equals to 2.
4.2.1.2.14 Tx Interruption After Trigger
OMCR path


This parameter indicates the time of prohibiting transmitting data on RACH. Only when
traffic volume measurement is on RACH, can this parameter be configured and its
configuration is optional. If the transport channel to be measured is DCH, this parameter
does not need to be configured.

4.2.2 UE Traffic Volume Period Measurement Configuration Object for

RACH

OMCR path

Traffic Volume Period Measurement Configuration for RACH

OMCR path

OMCR path

that UE performs.
OMCR path


requested or not.
OMCR path

OMCR path

4.2.2.2.7 Amount of Reporting in Period Report Criteria
OMCR path


This parameter indicates the amount of reporting for periodic reporting mode.
4.2.2.2.8 Reporting Interval in Period Report Criteria
OMCR path

This parameter indicates the reporting interval for periodic reporting mode.
4.2.3 UP Traffic Volume Event Measurement Configuration Object for

FACH

MeaEvtId[MAX_UE_T
RV_MEAS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE
_TRV_MEAS_EVENT] Pending Time After Trigger

rptThres[MAX_UE_TR
Traffic Volume Threshold of Event 4A/4B for FACH Channel
V_MEAS_EVENT]
trigTime[MAX_UE_TR
V_MEAS_EVENT] Time to Trigger
4.2.3.2 Parameter Configurations
OMC path

Configuration->Measurement Configuration->Traffic Volume Measurement Profile->UP
Traffic Volume Event Measurement Configuration for FACH
OMC path

This parameter indicates event number of UE traffic volume measurement. Traffic

OMC path


4.2.3.2.4 Traffic Volume Threshold of Event 4A/4B for FACH Channel
OMC path

measurement on FACH channel. If the traffic volume becomes larger than the threshold
OMC path


OMC path

OMCR path

OMCR path


label (not continuous). If the value is UM RLC, the retransmission is not required
OMCR path

that UE performs.
OMCR path

requested or not.
OMCR path


OMCR path

4.2.4 UE Traffic Volume Event Measurement Configuration Object for DCH

ueTrvMCfgNo Index
MeaEvtId[MAX_UE_TRV_ME
AS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE_TRV_
MEAS_EVENT] Pending Time After Trigger

rptThres0[MAX_UE_TRV_ME Traffic Volume Threshold of Event 4A/4B for

AS_EVENT] DCH(8kbps)






trigTime[MAX_UE_TRV_MEA
S_EVENT] Time to Trigger
OMC path

Traffic Volume Event Measurement Configuration for DCH

OMC path


OMC path

4.2.4.2.4 Traffic Volume Threshold of Event 4A/4B for DCH (8 kbps)
OMCR path


measurement on DCH whose rate is 8kbps. If the traffic volume becomes larger than the
threshold of Event 4A, a report of Event 4A will be triggered; and if the traffic volume
becomes smaller than the threshold of Event 4B, a report of Event 4B will be triggered.

OMCR path

measurement on DCH whose rate is 16kbps. If the traffic volume becomes larger than
the threshold of Event 4A, a report of Event 4A will be triggered; and if the traffic volume
becomes smaller than the threshold of event 4B, a report of 4B event will be triggered.
Where MAX_UE_TRV_MEAS_EVENT is the maximum number of UE traffic volume

OMCR path



OMCR path


OMCR path



OMCR path


OMCR path



OMC path

OMC path

OMCR path


OMCR path

OMCR path

that UE performs.
OMCR path


requested or not.
OMCR path

OMCR path


4.2.5 UE Traffic Volume Period Measurement Configuration Object for

DCH
OMC path

Traffic Volume Period Measurement Configuration for DCH
OMCR path


OMCR path

OMCR path

that UE performs.
OMCR path


requested or not.
OMCR path

OMCR path

4.2.5.2.8 Amount of Reporting in Period Report Criteria
OMCR path


This parameter indicates the amount of reporting for periodic reporting mode.
4.2.5.2.9 Reporting Interval in Period Report Criteria
OMCR path

This parameter indicates the reporting interval for periodic reporting mode.
4.2.6 UP Traffic Volume Event Measurement Configuration Object ID for

DCH

MeaEvtId[MAX_UE_TRV_
MEAS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE_TR
V_MEAS_EVENT] Pending Time After Trigger

rptThres0[MAX_UE_TRV_ Traffic Volume Threshold of Event 4A/4B for

MEAS_EVENT] DCH(8kbps)






trigTime[MAX_UE_TRV_M
EAS_EVENT] Time to Trigger
OMC path

OMC path



OMC path

OMCR path

measurement on DCH whose rate is 8kbps. If the traffic volume becomes larger than the
threshold of Event 4A, a report of Event 4A will be triggered; and if the traffic volume


OMCR path


OMCR path



OMCR path


OMCR path



OMCR path


OMCR path



OMC path

OMC path

This parameter indicates the pending time after trigger. The UE is then prohibited to send
new measurement reports triggered by the same event during this time period.
OMCR path


OMCR path

This parameter indicates the RLC mode for UE measurement reporting.
If the value of this parameter is "Acknowledged Mode RLC" (AM mode), when an
RNC receives an SDU with a wrong SDU label (discontinuous), the RNC can
request the UE to retransmit the SDU.
If the value is Unacknowledged Mode RLC (UM mode), the retransmission is not
required.
In general, the AM mode is used to report important measurement results. For less
important measurement results, the UM mode should be used to reduce the traffic
volume of the measurement reports and improve system capacity.
OMCR path


that UE performs.
OMCR path

requested or not.
OMCR path

OMCR path


4.2.7 UP Traffic Volume Measurement Configuration for Interactive and

Background Class on HS-DSCH Object

ueTrvMCfgNo Index

rptThres[MAX_UE_TRV_MEA Interactive and Background Class on HS-DSCH
S_EVENT] Channel
OMC path


Traffic Volume Measurement Configuration for Interactive and Background Class on
HS-DSCH
OMC path

HS-DSCH

OMC path

HS-DSCH

4.2.7.2.4 Traffic Volume Threshold of Event 4A/4B for Interactive and Background Class on
HS-DSCH Channel
OMC path

HS-DSCH
measurement for Interactive and Background Class on HS-DSCH Channel. If the traffic
volume becomes larger than the threshold of Event 4A, a report of Event 4A will be
triggered; and if the traffic volume becomes smaller than the threshold of Event 4B, a
report of Event 4B will be triggered.
OMC path

HS-DSCH
OMC path


HS-DSCH
OMCR path

HS-DSCH
OMCR path

HS-DSCH

OMCR path

HS-DSCH
that UE performs.
OMCR path

HS-DSCH
requested or not.
OMCR path


HS-DSCH
OMCR path

HS-DSCH
4.2.8 UP Traffic Volume Measurement Configuration Number for

Streaming Class on HS-DSCH Object

ueTrvMCfgNo Index
MeaEvtId[MAX_UE_TRV_MEA
S_EVENT] UE Traffic Volume Measurement Event Identity

pendingTime[MAX_UE_TRV_M
EAS_EVENT] Pending Time After Trigger
rptThres[MAX_UE_TRV_MEAS Traffic Volume Threshold of Event 4A/4B for

_EVENT] Streaming Class on HS-DSCH Channel
trigTime[MAX_UE_TRV_MEAS_
EVENT] Time to Trigger
OMC path

Traffic Volume Measurement Configuration Number for Streaming Class on HS-DSCH
OMC path



OMC path

4.2.8.2.4 Traffic Volume Threshold of Event 4A/4B for Streaming Class on HS-DSCH
Channel
OMC path

measurement for Streaming Class on HS-DSCH Channel. If the traffic volume becomes
larger than the threshold of Event 4A, a report of Event 4A will be triggered; and if the
traffic volume becomes smaller than the threshold of Event 4B, a report of Event 4B will
be triggered.

OMC path

OMC path

OMCR path


OMCR path

OMCR path

that UE performs.
OMCR path


requested or not.
OMCR path

OMCR path


4.2.9 UP Traffic Volume Measurement Configuration Object for E-DCH
MeaEvtId[MAX_UE_TR
V_MEAS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE_
TRV_MEAS_EVENT] Pending Time After Trigger
rptThres[MAX_UE_TRV Traffic Volume Threshold of Event 4A/4B for E-DCH

_MEAS_EVENT] Channel
trigTime[MAX_UE_TRV
_MEAS_EVENT] Time to Trigger
OMC path

Traffic Volume Measurement Configuration for E-DCH

OMC path


OMC path

4.2.9.2.4 Traffic Volume Threshold of Event 4A/4B for E-DCH Channel
OMC path


measurement on E-DCH Channel. If the traffic volume becomes larger than the threshold
OMC path

OMC path

OMCR path


OMCR path

OMCR path

that UE performs.

OMCR path

requested or not.
OMCR path

OMCR path


4.2.10 UP Throughput Event Measurement Configuration for E-TTI

Switching Object
MeaEvtId[MAX_UE_TR
pendingTime[MAX_UE_
trigTime[MAX_UE_TRV
Throughput Measurement Threshold for E-TTI Switching

ThoughThres of Event 4A/4B for E-DCH Channel
OMC path

Throughput Event Measurement Configuration for E-TTI Switching

OMC path


OMC path

4.2.10.2.4 Throughput Measurement Threshold for E-TTI Switching of Event 4A/4B for E-DCH
Channel
OMC path


This parameter indicates the reporting threshold of Events 4A and 4B for throughput
measurement on E-DCH. If the throughput becomes larger than the threshold of Event
4A, a report of Event 4A will be triggered; and if the throughput becomes smaller than the
threshold of Event 4B, a report of Event 4B will be triggered.
OMC path

OMC path

OMCR path


OMCR path

OMCR path

that UE performs.

OMCR path

requested or not.
OMCR path

OMCR path


4.2.11 UP Traffic Volume Measurement Configuration for HS-DSCH in

CELL_FACH Object
MeaEvtId[MAX_UE_TRV
_MEAS_EVENT] UE Traffic Volume Measurement Event Identity
pendingTime[MAX_UE_T
RV_MEAS_EVENT] Pending Time After Trigger
rptThres[MAX_UE_TRV_ Traffic Volume Threshold of Event 4A/4B for HS-DSCH

MEAS_EVENT] Channel in CELL_FACH
trigTime[MAX_UE_TRV_
MEAS_EVENT] Time to Trigger
OMC path

Traffic Volume Measurement Configuration for HS-DSCH in CELL_FACH

OMC path


OMC path

4.2.11.2.4 Traffic Volume Threshold of Event 4A/4B for HS-DSCH Channel in CELL_FACH
OMC path


measurement on HS-DSCH Channel in CELL_FACH. If the traffic volume becomes
larger than the threshold of Event 4A, a report of Event 4A will be triggered; and if the
traffic volume becomes smaller than the threshold of Event 4B, a report of Event 4B will
be triggered.
OMC path

OMC path


OMCR path

OMCR path

OMCR path


that UE performs.
OMCR path

requested or not.
OMCR path

OMCR path


4.2.12 UP Traffic Volume Measurement Configuration for E-DCH in

CELL_FACH Object ID

ueTrvMCfgNo Index
rptThres[MAX_UE_TRV_MEA Traffic Volume Threshold of Event 4A/4B for E-DCH

S_EVENT] Channel in CELL_FACH
OMC path


Traffic Volume Measurement Configuration for E-DCH in CELL_FACH
OMC path


OMC path


4.2.12.2.4 Traffic Volume Threshold of Event 4A/4B for E-DCH Channel in CELL_FACH
OMC path

measurement on E-DCH Channel in CELL_FACH. If the traffic volume becomes larger
than the threshold of Event 4A, a report of Event 4A will be triggered; and if the traffic
volume becomes smaller than the threshold of Event 4B, a report of Event 4B will be
triggered.
OMC path

OMC path


OMCR

OMCR path

OMCR path


that UE performs.
OMCR path

requested or not.
OMCR path

OMCR path


4.2.13 E-DCH Throughput Measurement Configuration Object for

MeaEvtId[MAX_UE_TR
pendingTime[MAX_UE_
trigTime[MAX_UE_TRV
E-DCH Throughput Measurement Threshold of Event

ThoughThres 4A/4B for HS-DSCH/E-DCH to HS-DSCH/DCH Switching

4.2.13.2.1 UP Throughput Event Measurement Configuration for E-TTI Switching Object ID
OMC path

Configuration->Measurement Configuration->Traffic Volume Measurement Profile->
E-DCH Throughput Measurement Configuration Object for HS-DSCH/E-DCH to
HS-DSCH/DCH Switching
This parameter indicates the UP Throughput Event Measurement Configuration for E-TTI
Switching Object ID.
OMC path

OMC path



OMC path

4.2.13.2.5 E-DCH Throughput Measurement Threshold of Event 4A/4B for HS-DSCH/E-DCH to

OMC path

This parameter indicates the reporting threshold of Events 4A and 4B for throughput
measurement on E-DCH. If the throughput becomes larger than the threshold of Event
4A, a report of Event 4A will be triggered; and if the throughput becomes smaller than the
threshold of Event 4B, a report of Event 4B will be triggered.

OMC path

OMC path

OMCR path


OMCR path

OMCR path

that UE performs.

OMCR path

requested or not.
OMCR path

OMCR path


4.3 UE Internal TxP Measurement Related Parameters
4.3.1 UE Transmitted Power Event Measurement Configuration for PS

Object
4.3.1.2.1 UE Internal Measurement Configuration Index
OMC path

Configuration->Measurement Configuration->UE Internal Measurement Profile->UE
Transmitted Power Event Measurement Configuration for PS
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 several different sets of measurement values for the same set of
parameters according to specific measurement purpose, and measurement quantity.
OMC path

This parameter indicates the RLC mode of the UE internal measurement report.
4.3.1.2.3 Filter coefficient
OMC path

This parameter indicates the filtering factor that UE performs the L3 filtering on the
measurement results of the internal measurement.
4.3.1.2.4 Maximum Event Number of UE Internal Measurement
OMC path


This parameter indicates the maximum event number of UE internal measurement.
4.3.1.2.5 UE Internal Measurement Event Identity
OMC path

This parameter indicates the UE internal measurement event identity
OMC path

This parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
4.3.1.2.7 UE Transmitted Power Threshold
OMC path

This parameter indicates the UE transmitted power threshold in Event 6A/6B.

4.3.2 UE Transmitted Power Event Report Object for Power Limitation

Judgment
4.3.2.2.1 UE Internal Measurement Configuration Index
OMC path

Configuration->Measurement Configuration->UE Internal Measurement Profile-> UE
Transmitted Power Event Report Object for Power Limitation Judgment
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 several different sets of measurement values for the same set of
parameters according to specific measurement purpose, and measurement quantity.
OMC path


This parameter indicates the RLC mode of the UE internal measurement report.
4.3.2.2.3 Filter coefficient
OMC path

This parameter indicates the filtering factor that UE performs the L3 filtering on the
measurement results of the internal measurement.
4.3.2.2.4 Maximum Event Number of UE Internal Measurement
OMC path

This parameter indicates the maximum event number of UE internal measurement.
4.3.2.2.5 UE Internal Measurement Event Identity
OMC path


This parameter indicates the UE internal measurement event identity.
OMC path

Configuration->Measurement Configuration->UE Internal Measurement Profile->E
This parameter indicates the period of time during which the event condition has to be
satisfied before sending a measurement report.
4.3.2.2.7 UE Transmitted Power Threshold
OMC path

Configuration->Measurement Configuration->UE Internal Measurement Profile->E
This parameter indicates the UE transmitted power threshold in Event 6A/6B.

4.4 Node B Dedicated TCP Measurement Related

Parameters
Node B Dedicated Measurement Relationship

NbDMCfgNote Function of Configuration Parameters
Downlink Rate Level Threshold used for D-TCP

DlRateLevel[2]
Measurement in DASF-PS
Measurement Threshold of Event A/B for Transmitted

EvtAbTcpThrd[3]
Code Power
rptPrd Report Periodicity Value
dedMeasType Dedicated Measurement Type
rptPrdUnit Choice Report Periodicity Scale
rptType Report Characteristics
NodeB Dedicated Measurement Configuration Object

UNbDedMeasProfile
ID
profileId Profile ID
nbDMCfgNo NbDed Measure Configuration No
measFilterCoeff Measurement Filter Coefficient
4.4.1.1 Function of Configuration Parameters
OMC path

Configuration->Measurement Configuration->NodeB Dedicated Measurement
Profile->NodeB Dedicated Measurement Configuration
This parameter indicates the function and purpose of the dedicated measurement
parameters indicated by the configuration index.

4.4.1.2 Downlink Rate Level Threshold used for D-TCP Measurement in DASF-PS
OMC path

This parameter indicates the downlink rate level threshold. In D-TCP based PS DRBC,
the thresholds of D-TCP measurement Event A/B are not based on the rate level of the
service.
4.4.1.3 Measurement Threshold of Event A/B for Transmitted Code Power
OMC path

This parameter indicates the power offset of the DPCH maximum DL power, which
defines which threshold that shall trigger Event A, B for transmitted carrier power
measurement.
4.4.1.4 Report Periodicity Value
OMC path


This parameter indicates the frequency of measurement report transmitted by Node B.
4.4.1.5 Dedicated Measurement Type
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration-> Service

This parameter indicates the type of dedicated measurement to be executed by

Node B.
Configuration Rule: Dedicated measurement type should be chosen according to

the usage of the dedicated measurement.
4.4.1.6 Choice Report Periodicity Scale
OMC path

This parameter indicates the time unit of measurement report transmitted by Node
B.
Configuration Rule: According to the measurement period which is determined

according to the contribution to the system load and the timeliness of the
measurement report.
4.4.1.7 Report Characteristics
OMC path


This parameter indicates the report characteristics of measurement results, which

can be on demand, periodic or by triggering all kinds of events.
Configuration Rule: according to the measurement type and event of the dedicated
measurement.
4.4.1.8 NodeB Dedicated Measurement Configuration Object ID
OMC path

This parameter indicates the object ID of Node B dedicated measurement

configuration.
4.4.1.9 NodeB Dedicated Measurement Profile Object ID
OMC path

Profile
This parameter indicates the Profile ID for the NodeB dedicated measurement. Each
profile corresponds to one setting of Node B dedicated measurement.

4.4.1.10 NbDed Measure Configuration No
OMC path

This parameter indicates the NodeB Measurement Configuration Number.
4.4.1.11 Measurement Filter Coefficient
OMC path

This parameter indicates the L3 filter coefficient.
The involved factor for setting this parameter: smoothness and real-time effect of
measurement report value.
Influence of this parameter: the less the value is, the less fluctuant the
measurement report value will be; the larger the value is, the more real-time the
measurement report value will be.
Suggestion for adjusting this parameter: not suggested.

4.5 Dynamic Radio Bearer Control Information of DPI

Service Object

refUDpiAppSrv Used UDpiAppSrv
refUDrbcProfile Used UDrbcProfile
4.5.2 Parameter Configurations
4.5.2.1 Used UDpiAppSrv
OMC path

Configuration->Dynamic Radio Bearer Control Information of DPI Service
This parameter indicates the Used UDpiAppSrv.
4.5.2.2 Used UDrbcProfile
OMC path

Configuration->Dynamic Radio Bearer Control Information of DPI Service
This parameter indicates the Used UDrbcProfile.
5 Counter List
Counter No. 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 DRBC
C310406298 Number of successed DCH Uplink DRBC(rise rate)
C310406299 Number of successed DCH Uplink DRBC(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 DRBC
C310406302 Number of successed DCH Downlink DRBC(rise rate)
C310406303 Number of successed DCH Downlink DRBC(reduce rate)
C310404205 Number of Success DCH Uplink DRBC,rise rate to 16k
C310404211 Number of Success DCH Uplink DRBC,drop rate to 8k
C310404217 Number of Success DCH Downlink DRBC,rise rate to 32k
C310404222 Number of Success DCH Downlink DRBC,drop rate to 8k

Number of intra frequency Transport Channel Changing

C310414096
attempt, HS-DSCH to DCH

C310414097
attempt, DCH to HS-DSCH

C310414098
attempt, FACH to DCH

C310414099
attempt, DCH to FACH

C310414100
attempt, FACH to PCH

C310414101
attempt, PCH to FACH

C310414102
attempt, HS-DSCH to FACH

C310414103
attempt, FACH to HS-DSCH

C310414104
attempt, E-DCH to DCH

C310414105
attempt, DCH to E-DCH

C310414106
attempt, E-DCH to RACH

C310414107
attempt, RACH to E-DCH
Number of intra frequency Transport Channel successful

C310414108
Changing attempt, HS-DSCH to DCH

C310414109
Changing attempt, DCH to HS-DSCH

C310414110
Changing attempt, FACH to DCH

C310414111
Changing attempt, DCH to FACH

C310414112
Changing attempt, FACH to PCH


C310414113
Changing attempt, PCH to FACH

C310414114
Changing attempt, HS-DSCH to FACH

C310414115
Changing attempt, FACH to HS-DSCH

C310414116
Changing attempt, E-DCH to DCH

C310414117
Changing attempt, DCH to E-DCH

C310414118
Changing attempt, E-DCH to RACH

C310414119
Changing attempt, RACH to E-DCH
Number of HSUPA 2ms ETTI attempted change to 10ms

C311855755
ETTI
Number of HSUPA 2ms ETTI successful change to 10ms

C311855756
ETTI
Number of HSUPA 10ms ETTI attempted change to 2ms

C311855757
ETTI
Number of HSUPA 10ms ETTI successful change to 2ms

C311855758
ETTI
Number of attempted Decreasing Rate on Uplink DCH,

C310405729
Triggered by UE TxP
Number of attempted Decreasing Rate on Uplink DCH,

C310405730
Triggered by Traffic Volume
Number of attempted Decreasing Rate on Downlink DCH,

C310405731
Triggered by D-TCP
Number of attempted Decreasing Rate on Downlink DCH,

C310405732
Number of success Decreasing Rate on Uplink DCH,

C310405733
Triggered by UE TxP
Number of success Decreasing Rate on Uplink DCH,

C310405734
Number of success Decreasing Rate on Downlink DCH,

C310405735
Triggered by D-TCP

Number of success Decreasing Rate on Downlink DCH,

C310405736
Number of Users of Uplink and Downlink Reconfiguration by

C310405737
one step

C310416901
Changing attempt, DCH to PCH

C310416902
Changing attempt, PCH to DCH

C310416903
Changing attempt, HS-DSCH to PCH

C310416904
Changing attempt, PCH to HS-DSCH

C310416905

C310416906
Changing attempt, PCH to DCH

C310416907
Changing attempt, HS-DSCH to PCH

C310416908
Changing attempt, PCH to HS-DSCH
Number of inter frequency Transport Channel Changing

C310414130
attempt, HS-DSCH to DCH

C310414131
attempt, DCH to HS-DSCH

C310414132
attempt, FACH to DCH

C310414133
attempt, DCH to FACH

C310414134
attempt, FACH to PCH

C310414135
attempt, PCH to FACH

C310414136
attempt, HS-DSCH to FACH

C310414137
attempt, FACH to HS-DSCH


C310414138
attempt, E-DCH to DCH

C310414139
attempt, DCH to E-DCH

C310414140
attempt, E-DCH to RACH

C310414141
attempt, RACH to E-DCH

C310416909
attempt, DCH to PCH

C310416910
attempt, PCH to DCH

C310416911
attempt, HS-DSCH to PCH

C310416912
attempt, PCH to HS-DSCH
Number of inter frequency Transport Channel successful

C310414142
Changing attempt, HS-DSCH to DCH

C310414143
Changing attempt, DCH to HS-DSCH

C310414144
Changing attempt, FACH to DCH

C310414145
Changing attempt, DCH to FACH

C310414146
Changing attempt, FACH to PCH

C310414147
Changing attempt, PCH to FACH

C310414148
Changing attempt, HS-DSCH to FACH

C310414149
Changing attempt, FACH to HS-DSCH

C310414150
Changing attempt, E-DCH to DCH

C310414151
Changing attempt, DCH to E-DCH


C310414152
Changing attempt, E-DCH to RACH

C310414153
Changing attempt, RACH to E-DCH

C310416913
6 Glossary
B
B Background
BO Buffer Occupancy
C Conversation
CPC Continuous Packet Connectivity
CN Core Network
DCCH Dedicated Control Channel
DCH Dedicated Channel
DL Downlink
DRBC Dynamic Radio Bearer Control
DTCH Dedicated Traffic Channel
E-DCH Enhanced uplink DCH

FACH Forward Access Channel
F-DPCH Fractional DPCH
GBR Guaranteed Bit Rate
HS-SCCH High Speed Shared Control Channel
HS-DSCH High Speed Downlink Shared Channel
I Interactive
IMS IP Multimedia Subsystem
MAC Media Access Control
MaxBR Maximum Bit Rate
MBMS Multimedia Broadcast 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-Point
QoS Quality of Service
RAB Radio access bearer
RACH Random Access Channel
RB Radio Bearer
RL Radio Link
RLC Radio Link Control
RNC Radio Network Controller
ROHC Robust Header Compression
RRC Radio Resource Control
RTCP Real time Control Protocol
S Streaming
S-CCPCH Secondary Common Control Physical Channel
SF Spreading Factor
SIP Session Initiation Protocol
TTI Transmission Time Interval

TF Transport Format
TFCS Transport Format Combination Set
TxP Transmission Power
UE User Equipment
UL Uplink
UM Unacknowledged Mode
UTRAN Universal Terrestrial Radio Access Network
VOIP Voice over IP

ZTE UMTS DRBC Algorithm Feature Guide - V8.5 - 201312

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS DRBC Algorithm Feature Guide - V8.5 - 201312

Uploaded by

Copyright:

Available Formats

DRBC Algorithm Feature

DRBC Algorithm Feature Guide

1. Updated 3.1.2.1 Signaling Channel

1. Updated 3.6.1, R8 Fast Dormancy.

2013 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

3 Technical Descriptions ................................................................................... 14

ZTE Confidential Proprietary 2

3.6.2 Pre-R7 Fast Dormancy Suppressing .................................................................. 90

4 Parameters and Configurations ................................................................... 112

ZTE Confidential Proprietary 3

4.2.8 UP Traffic Volume Measurement Configuration Number for Streaming Class on

5 Counter List ................................................................................................... 244

6 Glossary ......................................................................................................... 250

ZTE Confidential Proprietary 4

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

ZTE Confidential Proprietary 5

Attribute: [Mandatory + Optional]

Mutual exclusion: [None]

Initial Channel Allocation

Signaling Channel Allocation

Initial Service Channel Allocation

Concurrent Service Channel Allocation

Initial Access Rate Allocation for DCH

ZTE Confidential Proprietary 6

Figure 2-1 State Transitions

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

The CELL_DCH service uses the following types of channels: DL HS-DSCH/UL

ZTE Confidential Proprietary 7

The CELL_FACH service can use DL FACH/UL RACH.

2.1 ZWF21-04-004 Dynamic Radio Bearer Control

Interactive service and Background Service may use FACH/RACH or DCH.

Dynamic DCH rate adjustment

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

ZTE Confidential Proprietary 8

If the practical rate of PS Interactive Service or PS Background Service falls

ZTE Confidential Proprietary 9

2.2 ZWF23-04-004 Dynamic Channel Type Transfer for

Save system resources by adjusting channel type dynamically according to I/B

Ensure service quality by adjusting channel type according to channel quality.

ZTE Confidential Proprietary 10

2.3 ZWF25-04-005 Dynamic Channel Type Transfer for

In order to accommodate the requirements of service and practical status of system

Dynamically adjust channel type to save system resources according to the

If a UE on E-DCH channel moves to the cell edge and triggers a 1F event, it

ZTE Confidential Proprietary 11

Adjust channel type to guarantee mobile service continuity according to the

2.4 ZWF21-01-020 27.2Kbps High-Speed Signaling RB

2.5 ZWF21-01-027 Fast Dormancy

ZTE Confidential Proprietary 12

2.6 ZWF21-05-016 Video Call Prohibited in Specific

2.7 ZWF27-03-002 Application Awared DRBC

2.8 ZWF21-05-026 Voice Service Optimization for

2.9 ZWF21-04-014 Adaptive Radio Bearer

ZTE Confidential Proprietary 13

3.1 Dynamic Channel Type Transfer for R99 Service

3.1.1 Introduction to Service Types

3.1.2 Initial Channel Allocation

3.1.2.1 Signaling Channel Allocation

ZTE Confidential Proprietary 14

ZTE Confidential Proprietary 15

ZTE Confidential Proprietary 16

Originating Interactive Call, Originating Background Call, Originating Subscribed Traffic