DRBC Zte PDF

Dynamic Radio Bearer
Control
Feature Guide
Dynamic Radio Bearer Control

Version Date Author Reviewer Notes
Zhang
V1.00 2014/08/13 Ma Yongchao First edition
Haiyan
© 2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 7
2 Overview ............................................................................................................ 7
2.1 Feature Introduction ............................................................................................. 7
2.1.1 ZWF21-04-004 Dynamic Radio Bearer Control .................................................... 9
2.1.2 ZWF21-05-016 Video Call Prohibited in Specific Area ....................................... 12
2.2 License Control .................................................................................................. 12
2.3 Correlation With Other Features ........................................................................ 12
3 Technical Description ..................................................................................... 13

3.1 ZWF21-04-004 Dynamic Radio Bearer Control .................................................. 13
3.1.1 Introduction to Service Types ............................................................................. 13
3.1.2 Initial Channel Allocation .................................................................................... 13
3.1.3 Channel Switching ............................................................................................. 20
3.1.4 Related Measurement ........................................................................................ 42
3.1.5 Method of Obtaining DRBC Parameters ............................................................ 54
3.2 ZWF21-05-016 Video Call Prohibited in Specific Area ....................................... 54
3.3 Other Descriptions ............................................................................................. 56
3.3.1 Rate Matching for Sub-Services......................................................................... 56
3.3.2 MBR Controlling in the RNC .............................................................................. 56
3.3.3 Compatibility Strategy for the iPhones not Compliant With Encryption Protocols 56
3.3.4 Special Handling for the UEs Insensitive to Power Consumption ....................... 57
3.3.5 UE PCH Compatibility Strategies ....................................................................... 58
3.3.6 DRBC F/P->D Performance Optimization .......................................................... 59
3.3.7 Penalty Policy for the UEs That Cannot Stay in PCH State ................................ 59
3.3.8 The Controlling Strategy of Whether to Release the Traffic Measurement
Control Sent to the UE before When Transition to PCH ..................................... 60
3.3.9 PCH is Forbidden Based on the Number of UEs ................................................ 60
4 Parameters....................................................................................................... 61
4.1 ZWF21-04-004 Parameters Related to DRBC ................................................... 61
4.1.1 Dynamic Radio Bearer Control Information ........................................................ 61
4.1.2 Dynamic Radio Bearer Control Information Profile ............................................. 67
4.1.3 UMTS Logical Function Configuration ................................................................ 67
4.1.4 Logic RNC Configuration ................................................................................... 72
4.1.5 UTRAN Cell ....................................................................................................... 80
4.1.6 External UTRAN Cell ......................................................................................... 83
4.1.7 Iur Link ............................................................................................................... 84
4.1.8 Parameters Related to the Traffic Volume Measurement ................................... 84

4.1.9 Parameters Related to the Internal Measurement ............................................ 120

4.1.10 Parameters Related to the Dedicated Measurement ........................................ 123
4.2 ZWF21-05-016 Video Call Prohibited in Specific Area ..................................... 139
5 Related Counters and Alarms ...................................................................... 140

5.1 Related Counters ............................................................................................. 140
5.2 Related Alarms ................................................................................................ 143
6 Engineering Guide ........................................................................................ 143

6.1 Application Scenario ........................................................................................ 143
6.1.1 ZWF21-04-004 Dynamic Radio Bearer Control ................................................ 143
6.1.2 ZWF21-05-016 Video Call Prohibited in Specific Area ..................................... 144
6.2 Feature Activation Procedure ........................................................................... 144
6.3 Feature Validation Procedure .......................................................................... 169
6.4 Feature Deactivation Procedure....................................................................... 170
6.5 Impact on the Network ..................................................................................... 171
7 Abbreviation .................................................................................................. 172
8 Reference Document..................................................................................... 174

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

Figure 3-1 R99 Channel Switching.....................................................................................21
Figure 3-2 Event Triggering of Traffic Measurement ..........................................................49
Figure 3-3 Rate Adjustment Triggered by Traffic ................................................................50
Figure 6-1 Parameter Configuration 1 ..............................................................................145
Figure 6-10 Parameter Configuration 10 ..........................................................................158
Figure 6-19 Parameters configuration interface 19 ..........................................................166
Figure 6-20 Parameters configuration interface 20 ..........................................................167

TABLES
Table 2-1 License Control List ...........................................................................................12

Table 4-1 Parameter List (Dynamic Radio Bearer Control Information) ..............................61
Table 4-2 Parameter List (Dynamic Radio Bearer Control Information Profile) ...................67
Table 4-3 Parameter List (UMTS Logical Function Configuration)......................................67
Table 4-4 Parameter List (UMTS Logical Function Configuration)......................................72
Table 4-5 Parameter List (UTRAN Cell) .............................................................................80
Table 4-6 Parameter List (UTRAN Cell) .............................................................................83
Table 4-7 Parameter List (Iur Link).....................................................................................84
Table 4-8 Parameter List (Iur Link).....................................................................................84
Table 4-9 Parameters List (Parameters Related to the UE Event Traffic Measurement on the
DCH) ....................................................................................................................................85
Table 4-10 Parameters List (Parameters Related to the User Plane Event Traffic
Measurement on the DCH) ...................................................................................................92
Table 4-11 Parameters List (Parameters Related to the UE Periodic Traffic Measurement on
the DCH) ............................................................................................................................100
Table 4-12 Parameters List (Parameters Related to the User Plane Traffic Measurement on
the FACH) ..........................................................................................................................103
Table 4-13 Parameters List (Parameters Related to the UE Traffic Measurement on the
RACH) ................................................................................................................................108
Table 4-14 Parameters List (Parameters Related to the UE Periodic Traffic Measurement on
the RACH) ..........................................................................................................................113
Table 4-15 Parameters List (Parameters Related to the UE Event Traffic Measurement on
the PCH) ............................................................................................................................116
Table 4-16 Parameters List (Parameters Related to the UE Event Traffic Measurement on
the PCH) ............................................................................................................................119
Table 4-17 Parameter List (Parameters Related to the Internal Measurement) ................120
Table 4-18 Parameter List (Parameters Related to the Dedicated Measurement) ............123
Table 4-19 Parameter List (Parameters Related to the Video Call Prohibited in Specific Area)
...........................................................................................................................................139
Table 5-1 Counter List .....................................................................................................140

Table 6-1 Feature Validation Procedure...........................................................................169

Table 6-2 Feature Validation Procedure...........................................................................169
Table 6-3 RNC Parameter List 2 ......................................................................................170
Table 6-4 RNC Parameter List 2 ......................................................................................170

1 Feature Attribute
RNC version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
Node B version: [ZXSDRV4.13.10.20]
Attribute: [Mandatory]
Involved NE:
NE Name Related or Not Special Requirement
UE √ -
Node B √ -
RNC √ -
iTC - -
MSC - -
MGW - -
SGSN - -
GGSN - -
HLR - -
“√”: involved
“-”: not involved
2 Overview
2.1 Feature Introduction
Dynamic Radio Bearer Control (DRBC) is a process to allocate resources properly during
system operation according to the requirements of subscribers, UE types, and available
system resources to fully use the bandwidth. This document introduces the DRBC
function of the ZTE RAN for the R99 PS services. For the rate control strategies of the
NB-AMR and WB-AMR, refer to the ZTE UMTS NB-AMR Rate Control Feature Guide
and ZTE UMTS WB-AMR Rate Control Feature Guide. For the DRBC function for
HSDPA, HSUPA, DC-HSDPA, DC-HSUPA, and 4C-HSDPA services, refer to the ZTE

UMTS HSDPA Introduction Feature Guide, ZTE UMTS HSUPA Introduction Feature
Guide, ZTE UMTS DC-HSDPA Feature Guide, ZTE UMTS DC-HSUPA Feature Guide,
and ZTE UMTS 4C-HSDPA Feature Guide respectively.
The R99 DRBC function mainly includes the following aspects:
 Initial Channel Allocation
During an initial channel setup process, DRBC allocates proper channels and rates for
the services according to the service requirements and system resource utilization,
including:
 Signaling Channel Allocation
 Initial Service Channel Allocation
 Initial Access Rate Allocation for DCH
 Concurrent Service Channel Allocation
 Channel Switching
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 traffic is lower than the
allocated bandwidth, the system decreases the configured bandwidth to save resources.
When the actual data traffic is close to the allocated bandwidth, the system increases the
configured bandwidth to prevent the services from being affected.
During a session, DRBC adjusts the service bandwidth and channel switching in real
time according to various measurements. The conversational services use DL DCH/UL
DCH, the streaming services use 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
Note:
 A service in CELL_DCH state 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 NodeBs and UEs, and service features. Channel switching can be
performed between different channel types. The rates of DL DCHs and UL DCHs
can be adjusted dynamically. This document only focuses on R99 DRBC. For the
description of the transition between the HS-DSCH and DL DCH, the UL DCH and
E-DCH, refer to the ZTE UMTS HSDPA Introduction Feature Guide and ZTE UMTS
HSUPA Introduction Feature Guide respectively.
 The CELL_FACH service uses DL FACH/UL RACH.
 The PCH state includes the CELL_PCH and URA_PCH states, and which one is
used depends on the value of UDrbc.pchSwch.
2.1.1 ZWF21-04-004 Dynamic Radio Bearer Control
The R99 DRBC function of the ZTE RAN dynamically adjusts the bearer channel types
and the rates of PS services in real time. It ensures full utilization of radio resources,
system stability, and service QoS.

 During a channel setup process, DRBC allocates appropriate radio channel and
initial rate to the service according to service requirements and system resource
utilization.
 The conversational service and streaming service use DCHs as bearers. The
parameters of the DCH channel are set according to the required GBR.
 The interactive service and background service use FACHs/RACHs or DCHs.
 For a PS service that uses a DCH as a bearer, the initial access rate is set
according to the configuration in the OMCR.
 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 is high to avoid affecting user experience.
 Traffic volume is evaluated in the uplink and downlink separately. That is,
uplink traffic volume determines 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 the uplink and downlink.
In this case, the ZTE RAN adjusts the DCH bandwidth in the uplink and
downlink through a single signaling procedure so that the signaling messages
on the Uu interface 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
the UE decrease the data rate till the transmission power is lower than the
preset low threshold. By using this method, a PS service subscriber obtains a
relatively higher data rate when a UE is in the center of a cell, and obtains a
lower data rate when the UE is on the edge of the cell. Thus, the coverage of
PS services is expanded. The call drop rate of high-rate services in the
handover process is also decreased.

 When a UE performs a hard handover from one R99 cell to another due to
mobility, the system downgrades its DCH rate before reattempting handover if
the downlink admission of the UE at the current rate fails in the target cell.
 Channel switching
 If the practical rate of the PS interactive service or PS background service falls

below the traffic volume threshold or if overload occurs in a cell, the RAB
switches to FACH/RACH from DCH, and the UE then transits to the CELL
FACH state.
 If the practical rate exceeds the traffic volume threshold of FACH/RACH, the
RAB switches to DCH, and the UE then transits to 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 or the CELL_PCH state to save the battery power of the UE. If the PCH
state is not configured on the EMS, the RRC connection can be directly
released.
 When the UE in URA_PCH state or CELL_PCH state originates a cell update

message due to uplink or downlink data transmission or due to a new service
setup request, the system gives priority to CELL_DCH or CELL_FACH
according to the value of the bit8 (0 or 1) of URncFunction.gresPara48 and the
value of ULogicalRnc.pchToOtherTVISw.
 If the duration when a UE is in URA PCH or CELL_PCH state exceeds a

preset threshold, the RRC is 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 for radio bandwidth.

2.1.2 ZWF21-05-016 Video Call Prohibited in Specific Area
The UMTS network provides the video call service. In some areas, for example, security
control zones or privacy-sensitive areas, the video call service is prohibited and must be
disabled in the network layer. This feature allows the system to disable the video call
service for specific cells.
2.2 License Control
Table 2-1 License Control List
License Configured
Feature ID Feature Name Unit
Control Item NE
ZWF21-04-004 Dynamic Radio

- - -
Bearer Control
ZWF21-05-016 Video Call Prohibited

- - -
in Specific Area
2.3 Correlation With Other Features
1. Required Features
None
2. Mutually Exclusive Features
None
3. Affected Features
None

3 Technical Description
3.1 ZWF21-04-004 Dynamic Radio Bearer Control
3.1.1 Introduction to Service Types
Different types of services have various features, and therefore the services have
different requirements for the occupied channel resources during the channel allocation
process. Currently, services can be categorized into four types: Conversational,
Interactive, Background, and Streaming.
The conversational and streaming services are real-time, while interactive and
background services are not real-time.
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 URncFunction.initRrcOnDch at different rates on different
channels for RRC connection establishment.
 If the parameter URncFunction.initRrcOnDch is set to “0: Forced to CELL_DCH and

Using DCH/DCH Low Rate Signalling”, the RNC sets the initial signaling to forcibly
use the DCH/DCH at 3.4 kbit/s.
When a UE sends an RRC connection setup request message to the RNC, the
RNC configures the bidirectional DCH 3.4 kbit/s for the signaling.

Using DCH/DCH with 13.6k Signalling”, the RNC sets the initial signaling to forcibly

 If the parameter URncFunction.initRrcOnDch is set to “2: Forced to FACH”, the

RNC sets the initial signaling to use the common channel forcibly.
RNC configures the uplink RACH or downlink FACH channel for the UE to bear
signaling.
 If the parameter URncFunction.initRrcOnDch is set to “3: Not Forced, Using

DCH/DCH with DCH/DCH Low Rate Signalling on Cell_DCH State”, the RNC sets
the initial signaling to choose channels automatically, and sets the DCH/DCH at 3.4
kbit/s when the dedicated channel is used.
RNC automatically selects the dedicated channel (3.4 kbit/s) or common channel
based on the cause for connection setup: If a service is initiated immediately after
the setup of the RRC connection, the RNC selects the 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 the RRC connection, the RNC
selects the common channel to bear signaling.

DCH/DCH with 13.6k Signalling on Cell_DCH State”, the RNC sets the initial
signaling to choose channels automatically, and sets the DCH/DCH at 13.6 kbit/s
when the dedicated channel is used.
RNC automatically selects the dedicated channel (13.6 kbit/s) or common channel
based on the cause for connection setup. If services are initiated immediately after
the setup of the RRC connection, the RNC selects the DCH channel and configures
bidirectional 13.6 kbit/s bear signaling. If there is only an LA update, instead of
setting up services, which should be completed after the RRC connection, the RNC
selects the common channel to bear signaling.

Using DCH/DCH with 27.2k Signalling”, the RNC sets the initial signaling to forcibly


DCH/DCH with 27.2k Signalling on Cell_DCH State”, the RNC sets the initial
signaling to choose channels automatically, and sets the 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 cause
for connection setup. If services are initiated immediately after the setup of the RRC
connection, the RNC selects the DCH channel and reconfigures bidirectional 27.2
kbit/s bear signaling. If there is only an LA update, instead of setting up services,
which should be completed after the RRC connection, the RNC reconfigures the
common channel to bear signaling.
 If the parameter URncFunction.initRrcOnDch is set to “7: Forced to HSPA”, the

RNC sets the initial signaling to forcibly use HSPA. For the detailed strategy of SRB
over HSDPA, refer to the section Signaling Channel Allocation in the Phase of RRC
in the ZTE UMTS F-DPCH & SRB over HSDPA Feature Guide and the section
Signaling Channel Allocation in the Phase of RRC in the ZTE UMTS Enhanced
F-DPCH Feature Guide.
 If the parameter URncFunction.initRrcOnDch is set to “8: Not Forced,Using HSPA

Signalling on CELL_DCH state”, the RNC sets the initial signaling to choose
channels automatically, and priority is given to HSPA when the Cell_DCH state is
used.
RNC automatically selects the channel in Cell_DCH state or Cell_FACH state
based on the cause for connection setup, and priority is given to HSPA when the
Cell_DCH state is used.
When the RNC sets the initial signaling to choose channels automatically, the signaling is
set on the bearer in Cell_DCH state preferentially if the signaling is set due to the
following causes: 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 causes, it is set on the bearer in Cell_FACH state.
The high-rate (13.6 kbit/s and 27.2 kbit/s) signaling bearer only exists in a separate
signaling process, and is 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
setup of a UE call and lower the call delay, but it occupies more radio resources than the
ordinary rate signaling bearer. Using the common channel for signaling, the bearer does
not occupy the dedicated resources. Considering that the separate signaling process
occupies the resources for a short time, 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 the setup of an RRC connection when the signaling is carried on a DCH, or
when the RAB has been set up and the signaling is carried on a DPCH alone, and if
a signaling process is set up at a DCH low rate (DCH 3.4 kbit/s): DCH 6.8 kbit/s
signaling replaces 3.4 kbit/s signaling if ULogicalRnc.dchSig68Swch is set to On;
otherwise, DCH 3.4 kbit/s signaling is used if ULogicalRnc.dchSig68Swch is set to
Off.
2. To avoid the transport resource limitation on the Iub interface, the parameter
UCelInfoFDD.CellSigMaxBR is used to limit the maximum rate for the signaling in a
cell, that is, when the signaling is on the DCH, the rate for the signaling should be
the smaller one of the two rates obtained with the previous method and from
UCelInfoFDD.CellSigMaxBR respectively. When UCelInfoFDD.CellSigMaxBR is set
to “4: CELL_FACH Forced”, the RRC is set up on the CELL_FACH despite the
value of URncFunction.initRrcOnDch. In this case, the success rate of the RRC
establishment can be increased when the transport resources of the Iub interface
are insufficient.

3.1.2.1.1 For CELL_DCH Admission Failure During the RRC Establishment Stage of the PS
Service Add a Switch to Control Whether the UE is Attempted on the FACH
For the RRC stage, if the establishment cause is PS service (see the note), if UE is
denied by the CELL_DCH, whether it is attempted on the CELL_FACH should consider
the value of the switch (bit0 of UCelInfoFDD.CresPara7): only when the switch takes the
value of “0: Second Admission on FACH is allowed‟, can it attempts on the FACH for the
second time, otherwise not.
Note: It is regarded as PS service cause when the establishment cause in the RRC
connection request is one of the following: Originating Streaming Call, Originating
Interactive Call, Originating Background Call, Terminating Streaming Call, Terminating
Interactive Call, Terminating Background Call, Originating High Priority Signalling,
Terminating High Priority Signalling, Inter-RAT Cell Change Order, Originating
Subscribed Traffic Call, Call re-establishmen.
3.1.2.2 Initial Service Channel Allocation
For an RAB request of a service, the RNC chooses the initial channel for the service by
the service features (RAB parameters). The selection principles are as follows:
 The conversational and streaming services use DL DCHs/UL DCHs.
 The interactive and background services can use DL DCHs/UL DCHs and DL
FACHs/UL RACHs. Whether a DL DCH/UL DCH or DL FACH/UL RACH is to be
used depends on whether an SRB is established on the DCH or FACH:
 If an SRB is on a DCH, the service cannot be established on an FACH. If the

admission to the DCH fails, the service and signaling are set up on an FACH.
 If an SRB is on an FACH, it is necessary to compare MaxBR in the RAB

Assignment message with ULogicalRnc.rfach and ULogicalRnc.rrach. If DL
MaxBR is equal to or greater than ULogicalRnc.rfach or if UL MaxBR is equal
to or greater than ULogicalRnc.rrach, priority is given to the DL DCH/UL DCH.
Otherwise, priority is given to the DL FACH/UL RACH. If the FACH/RACH is
rejected for access, the RNC reselects the DL DCH/UL DCH.

3.1.2.3 Initial DCH Access Rate for PS Services
The initial access rate of DL DCHs/UL DCHs for PS services is determined in the
following way:
 If the DRBC switch ULogicalRnc.drbcSwch is set to Off, the initial DCH rate is the
result of min(max(the highest rate level of DBRC, GBR), MaxBR). Where, the
highest rate level of DBRC for the uplink and downlink are obtained from
UlDrbcRateLevel and DlDrbcRateLevel separately. The definitions of
UlDrbcRateLevel and DlDrbcRateLevel are described in the note below. For how to
obtain MaxBR, refer to Section 3.3.1 Rate Matching for Sub-Services in this
document.
 If the DRBC switch ULogicalRnc.drbcSwch is set to On, the initial DCH rate is the
result of min(max(“Initial Access Rate for DCH”, GBR), MaxBR, “DCH Limited
Rate”). Where, “Initial Access Rate for DCH” for the uplink and downlink is
configured by the parameter ULogicalRnc.initialRateUl and
ULogicalRnc.initialRateDl separately. If the admission decision for the initial DCH
rate fails, the UL and DL DCHs attempt to access at the minimum DRBC rate of the
DCH at the same time. The minimum DRBC rate of the DCH is defined as the result
of min(max(the lowest rate level of DBRC, GBR), MaxBR, “DCH Limited Rate”). For
how to obtain MaxBR, refer to Section 3.3.1 Rate Matching for Sub-Services in this
document.
Note:
1. The definition of the DCH Limited Rate is as follows:
For the case of intra-RNC, the parameters

UCelInfoFDD.rtMaxUlRateDch/UCelInfoFDD.rtMaxDlRateDch (for RT services) and
UUtranCellFDD.nrtMaxUlRateDch/UUtranCellFDD.nrtMaxDlRateDch (for NRT services)
are used to limit the maximum rate of the uplink and downlink DCHs respectively.
For the case of inter-RNC, the parameters

UExternalUtranCellFDD.rtMaxUlRateDchD/UExternalUtranCellFDD.rtMaxDlRateDchD
(for RT services) and
UExternalUtranCellFDD.nrtMaxUlRateDchD/UExternalUtranCellFDD.nrtMaxDlRateDch

D (for NRT services) are used to limit the maximum rate of the uplink and downlink DCHs
respectively. If the neighboring cells belonging to the DRNC are not configured in the
SRNC, the restriction decision does not take effect.
For macro diversity, the “DCH Limited Rate” is set to the minimum value of "DCH Limited
Rate" for all the cells in the active set.
2. The definition of the rate levels of DBRC is as follows:
ULRateLevelNum defines the number of DRBC uplink rate adjustment levels, which is
controlled by ULogicalRnc.ulRateAdjLevNum.
UlDrbcRateLevel is the adjustment levels of the uplink DRBC rate. It is an array with the
number of rate levels set by ULRateLevelNum. It is obtained from
ULogicalRnc.ulRateAdjLev.
DLRateLevelNum defines the number of DRBC downlink rate adjustment levels, which is
controlled by ULogicalRnc.dlRateAdjLevNum.
DlDrbcRateLevel is the adjustment levels of the downlink DRBC rate. It is an array with
the number of rate levels set by DLRateLevelNum. It is obtained from
ULogicalRnc.dlRateAdjLev.
3.1.2.4 Concurrent Service Channel Allocation
The concurrent service means the setup of a new service when a UE already has an
online call service.
 If a UE is in 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 UE is in CELL_FACH state, the system determines whether to perform state

transitions according to the new service type:
 If the new service should be set up on the DL DCH/UL DCH channels

according to the channel allocation principles as for a single service, the UE
transits from the CELL_FACH state to the CELL_DCH state, that is, all the

online services are switched to the DCH channel. The initial rate of the new
service is determined by the same method as that for a single service.
 If the new service is set up on the DL FACH/UL RACH channels according to

the channel allocation principles as for a single service, the UE remains in
CELL_FACH state, without impacting on the online services.
For concurrent CS and PS (S/I/B) services:
 If the DRBC switch ULogicalRnc.drbcSwch is set to Off, the DCH rate of the PS
(S/I/B) service is the result of min(max(the highest rate level of DRBC, GBR),
MaxBR). The highest rate levels of DRBC for the uplink and downlink are obtained
from UlDrbcRateLevel and DlDrbcRateLevel. UlDrbcRateLevel and
DlDrbcRateLevel are defined in the previous section.
 If the DRBC switch ULogicalRnc.drbcSwch is set to On, the DCH rate of the PS
(S/I/B) service is the minimum DRBC rate of the DCH (refer to Section 3.1.2.3 Initial
DCH Access Rate for PS Services). The rate increase is based on the rate increase
principles (refer to Section 3.1.3.3 UL DCH -> UL DCH (Rate Increase) and
Section 3.1.3.1 DL DCH -> DL DCH (Rate Increase)).
Where, the GBR of a streaming service is the GBR obtained after RAB assignment and
the GBR of an I/B service is 0. For how to obtain MaxBR, refer to Section 3.3.1 Rate
Matching for Sub-Services in this document.
3.1.3 Channel Switching
Channel switching and dynamic resources adjustment are performed only when the
DRBC switch (ULogicalRnc.drbcSwch) is set to On.
During a session, the dynamic channel switching for an R99 system is to adjust the
service bandwidth and to 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 R99
protocols.

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

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

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

1. DL&UL Traffic Volume Based 1. UL&DL Traffic Volume Based
The following sections describe the switching principles for the types of channel
switching shown in this figure.
3.1.3.1 DL DCH -> DL DCH (Rate Increase)
1. Rate increase triggered by downlink traffic
Downlink DCH-to-DCH rate increase is based on the traffic measurement reports (Event
4A) from the user plane and determined by the dedicated transmission power of UEs and
cell load.
Event 4A is defined as an event when the traffic measurement is larger than an absolute
threshold. For the detailed definition, refer to Section 3.1.4.1 Traffic Volume
Measurement.
Event A is defined as an event when the Node B downlink dedicated transmission power
(D-TCP) is greater than an absolute threshold. For the detailed definition, refer to Section
3.1.4.3 Node B Dedicated TCP Measurement.
Event B is defined as an event when the Node B downlink dedicated transmission power
(D-TCP) is smaller than an absolute threshold. For the detailed definition, refer to Section

A Downlink DCH rate increase process is triggered when all the following conditions are
satisfied at the same time:
 The DCH rate adjustment triggered by the traffic switch

ULogicalRnc.dchAdjRateSwch is set to On.
 The system consecutively receives the traffic measurement reports (Event 4A) from
the user plane for UDrbc.dchE4aThd times.
Note: If the system receives a traffic measurement report (Event 4B) from the user
plane when the number of receptions is smaller than the threshold, the
corresponding counter is cleared.
 The system consecutively receives the measurement reports (Event B) of the Node
B D-TCP for UDrbc.dtcpEbThd times, that is, the UE is in B status.
Note: If the system receives a measurement report (Event A) from the Node B when
the number of receptions is smaller than the threshold, the corresponding counter is
cleared.
 The downlink load of the cell is not overloaded.

Note: The downlink load is determined by the TCP. For details of the overload
threshold, refer to the ZTE UMTS Overload Control Feature Guide.
During DCH rate increase for non-macro diversity, the target rate of the downlink DCH is
the result of min(next rate level that is greater than the current rate level specified by
DlDrbcRateLevel, “DCH Limited Rate”, DL MaxBR).
During DCH rate increase for macro diversity, the target rate of the downlink DCH is the
result of min(next rate level that is greater than the current rate level specified by
DlDrbcRateLevel, DL MaxBR, “DCH Limited Rate”, MaxRateMD).
Where,
1. For the definition of “DCH Limited Rate”, refer to Section 3.1.2.3 Initial DCH Access
Rate for PS Services.
2. For the definitions of UlDrbcRateLevel and DlDrbcRateLevel, refer to Section

3.1.2.3 Initial DCH Access Rate for PS Services.
3. MaxRateMD is the maximum rate threshold allowed for DCH rate increase when

the UE is in macro diversity state. It is obtained from UUtranCellFDD.maxRateMD.
For the concurrence of C (CS) services and PS (S/I/B) services, the additional principles
for rate increase of PS services are as follows:
 The maximum rate threshold of NRT PS (I/B) services is determined by

distinguishing the rates of C (CS) services.
 If the rate of a C (CS) service is less than or equal to ULogicalRnc.cRateThrd, the

sum of downlink rates of concurrent NRT PS services cannot exceed
ULogicalRnc.dlPsRateLmtLowC.
 If the rate of a C (CS) service exceeds ULogicalRnc.cRateThrd, the sum of

downlink rates of concurrent NRT PS services cannot exceed
ULogicalRnc.dlPsRateLmtHighC.
 The rates of streaming services are not restricted by these rate thresholds.
3.1.3.2 DL DCH -> DL DCH (Rate Decrease)
The DCH rate is decreased in order to:
1. Release some bandwidth of a UE and allocate the released bandwidth to other UEs
to improve the bandwidth utilization when the required bandwidth for data
transmission of the UE is decreased.
2. Lower the bandwidth of a UE and the transmission power to ensure the QoS for the
UE when the downlink transmission power of the UE is too high.
3. Lower the bandwidth of UEs and the system load to ensure the system stability
when the cell load is too high.
Therefore, the downlink DCH rate decrease can be classified into the following types:
 Rate decrease triggered by downlink traffic
 Rate decrease triggered by Node B downlink dedicated transmission power
 Rate decrease triggered by cell downlink load

 Rate decrease triggered by downlink resource congestion
 Rate decrease triggered by mobility
Any of these factors can trigger a rate decrease process.
1. Rate decrease triggered by downlink traffic
The DCH-to-DCH switching for downlink rate decrease is based on the traffic
measurement reports (Event 4B) on the user plane.
Event 4B is defined as an event when the traffic measurement is less than an absolute
Measurement.
A DL rate decrease process is triggered when all the following conditions are satisfied at
the same time:

 The system consecutively receives the traffic measurement reports (Event 4B) from
the user plane for UDrbc.dchE4bThd times.
Note: If the system receives an Event 4A traffic measurement report from the user
plane when the number of receptions is smaller than the threshold, the
corresponding counter is cleared.
 For non-real-time I/B services, the current uplink rate of a UE is greater than or
equal to the rate threshold ULogicalRnc.rrach for RACH switching or the downlink
target rate is greater than or equal to the rate threshold ULogicalRnc.rfach for FACH
switching. If the system switch UDrbc.fachSwch for CELL_FACH switching is set to
Off, this condition should not be taken into consideration. For real-time S services,
the current rate exceeds the GBR obtained after RAB assignment.
During DCH rate decrease, the target rate is the result of max(next rate level that is
smaller than the current rate level specified by DlDrbcRateLevel, GBR). The GBR of an
interactive or background service is 0, and the GBR of a streaming service is the GBR

obtained after RAB assignment. For the definition of DlDrbcRateLevel, refer to Section
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).
Event A is defined as an event when the Node B downlink dedicated transmission power
(D-TCP) is greater than an absolute threshold. For the detailed definition, refer to Section
A DCH rate decrease process is triggered when all the following conditions are satisfied
at the same time:
 The DCH rate adjustment triggered by the D-TCP switch ULogicalRnc.dlPwrDasf is

set to On.
 The system consecutively receives the measurement reports (Event A) of the Node
B D-TCP for UDrbc.dtcpEaThd times, that is, the UE is in A status.
Note: If the system receives a measurement report (Event B) from Node B when the
number of receptions is smaller than the threshold, the corresponding counter is
cleared.
 For non-real-time I/B services, the current rate is greater than the minimum rate
level specified by DlDrbcRateLevel. For real-time S services, the current rate is
greater than the GBR obtained after RAB assignment.
During DCH rate increase, the target rate is the result of max(next rate level that is
obtained after RAB assignment.
3. Rate decrease triggered by cell downlink load
Refer to Section 3.1.3 Load Decrease Methods for R99 Common Overload in the ZTE
UMTS Overload Control Feature Guide.
4. Rate decrease triggered by downlink resource congestion

Refer to Section 3.1.3 DCH Downgrade in the ZTE UMTS Congestion Control Feature
Guide.
The DCH-to-DCH switching for DCH downlink rate decrease can be triggered by the
downlink resource congestion of a cell.
at the same time:
 The downlink CE resources, code resources or power are congested.
 For non-real-time I/B services, the current rate is greater than the minimum rate on
the DCH (the lowest rate level specified by DlDrbcRateLevel). For real-time S
services, the current rate is greater than the GBR obtained after RAB assignment.
During DCH rate increase, the target rate is the result of max(next rate level that is
obtained after RAB assignment. For more details about congestion control, refer to the
ZTE UMTS Congestion Control Feature Guide.
5. Rate decrease triggered by mobility
A UE performs a hard handover from one R99 cell to another due to mobility. If the
downlink admission for the UE to the target cell fails at the current rate, the system uses
the minimum DRBC rate to admit the user again. The minimum rate is the result of
min(max(the lowest level specified by DlDrbcRateLevel, DL GBR), DL MaxBR).
For more details about mobility, refer to the ZTE UMTS handover Control Feature Guide.
For the definition of DlDrbcRateLevel, refer to Section 3.1.2.3 Initial DCH Access Rate for
PS Services.
3.1.3.3 UL DCH -> UL DCH (Rate Increase)
Uplink DCH-to-DCH rate increase is based on the traffic measurement reports (Event 4A)
from UEs and determined by the transmission power of the UEs and cell load.

Event 4A is defined as an event when the traffic measurement is larger than an absolute
Measurement.
An uplink DCH rate increase process is triggered when all the following conditions are

 The system consecutively receives the traffic measurement reports (Event 4A) from
a UE for UDrbc.dchE4aThd times.
Note: If the system receives a traffic measurement report (Event 4B) from the UE
when the number of receptions is smaller than the threshold, the corresponding
counter is cleared.
 The system receives the measurement reports (Event 6B) triggered by the
transmission power of the UE, that is, the uplink transmission power of the UE is in
6B status.
Note: For details, refer to Section 3.1.4.2 Internal UE TxP Measurement.
 The uplink load of the cell is not overloaded.

Note: The uplink load is determined by the RTWP. For details of the definition of the
uplink load, refer to the ZTE UMTS Overload Control Feature Guide.
During DCH rate increase for non-macro diversity, the target rate of the DCH is the result
of min(next rate level that is greater than the current rate level specified by
UlDrbcRateLevel, “DCH Limited Rate”, UL MaxBR).
During DCH rate increase for macro diversity, the target rate of the NRT uplink DCH is
the result of min(next rate level that is greater than the current rate level specified by
UlDrbcRateLevel, UL MaxBR, “DCH Limited Rate”, MaxRateMD).
Where,
1. For the definition of “DCH Limited Rate”, refer to Section 3.1.2.3 Initial DCH Access
2. For the definition of UlDrbcRateLevel, refer to Section 3.1.2.3 Initial DCH Access

3. MaxRateMD is the maximum rate threshold allowed for DCH rate increase when
the UE is in macro diversity state. It is obtained from UUtranCellFDD.maxRateMD.
4. For how to obtain MaxBR, refer to Section 3.3.1 Rate Matching for Sub-Services in
this document.
For the concurrence of C (CS) services and PS (S/I/B) services, the additional principles
for rate increase of PS service are as follows:
 The maximum rate threshold of NRT PS (I/B) services is determined by

distinguishing the rates of C (CS) services.
 If the rate of a C (CS) service is less than or equal to ULogicalRnc.cRateThrd, the

sum of uplink rates of concurrent NRT PS services cannot exceed
ULogicalRnc.ulPsRateLmtLowC.
 If the rate of a C (CS) service exceeds ULogicalRnc.cRateThrd, the sum of uplink

rates of concurrent NRT PS services cannot exceed
ULogicalRnc.ulPsRateLmtHighC.
 The rates of streaming services are not restricted by these rate thresholds.
3.1.3.4 UL DCH -> UL DCH (Rate Decrease)
The DCH rate is decreased in order to:
1. Release some bandwidth of a UE and allocate the released bandwidth to other UEs
to improve the bandwidth utilization when the required bandwidth for data
transmission of the UE is decreased.
2. Lower the bandwidth of a UE and transmission power to ensure the QoS for the UE
when the uplink transmission power of the UE is too high.
3. Lower the bandwidth of UEs and the system load to ensure the system stability
when the cell load is too high.
Therefore, the uplink DCH rate decrease can be classified into the following types:

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 these factors can trigger a rate decrease process.
1. Rate decrease triggered by uplink traffic
The DCH-to-DCH switching for uplink rate decrease is based on the traffic measurement
reports (Event 4B) from UEs.
Event 4B is defined as an event when the traffic measurement is less than an absolute
Measurement.
at the same time:

 The system consecutively receives the traffic measurement reports (Event 4B) of a
UE for UDrbc.dchE4bThd times.
Note: If the system receives a traffic measurement report (Event 4A) from the UE
when the number of receptions is smaller than the threshold, the corresponding
counter is cleared.
 For non-real-time I/B services, the current uplink rate of a UE is greater than or
equal to the rate threshold ULogicalRnc.rrach for RACH switching or the downlink
target rate is greater than or equal to the rate threshold ULogicalRnc.rfach for FACH
switching. If the system switch UDrbc.fachSwch for CELL_FACH switching is set to
Off, this condition should not be taken into consideration. For real-time S services,
the current rate exceeds the GBR obtained after RAB assignment.

smaller than the current rate level specified by UlDrbcRateLevel, GBR). The GBR of an
obtained after RAB assignment. For the definition of UlDrbcRateLevel, refer to Section
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). If a 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 transmission power of the UE to avoid interference with other UEs. If the UE is
close to the base station, the traffic volume can trigger a UL DCH rate increase process.
Event 6A is defined as an event when the UE dedicated transmission power exceeds an

absolute threshold, that is, the UE is in high power status. For the configuration of the
threshold, refer to Section 3.1.4.2 Internal UE TxP Measurement.
at the same time:
 The DCH rate adjustment triggered by the UE dedicated transmission power switch
ULogicalRnc.ulPwrDasf is set to On.
 The measurement reports (Event 6A) triggered by the UE transmission power is

received, that is, the UE transmission power is in 6A status.
 For non-real-time I/B services, the current rate is greater than the minimum rate on
the DCH (the lowest rate level specified by UlDrbcRateLevel). For real-time S
services, the current rate is greater than the GBR obtained after RAB assignment.
smaller than the current rate specified by UlDrbcRateLevel, GBR). The GBR of an
obtained after RAB assignment.
3. Rate decrease triggered by cell uplink load

Refer to Section 3.1.3 Load Decrease Methods for R99 Common Overload in the ZTE
UMTS Overload Control Feature Guide.
4. Rate decrease triggered by uplink resource congestion
Refer to Section 3.1.3 DCH Downgrade in the ZTE UMTS Congestion Control Feature
Guide.
A UE performs a hard handover from one R99 cell to another due to mobility. If the uplink
admission of the UE 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 the result of
min(max(the lowest level specified by UlDrbcRateLevel, UL GBR), UL MaxBR).
For more details about mobility, refer to the ZTE UMTS handover Control Feature Guide.
For the definition of UlDrbcRateLevel, refer to Section 3.1.2.3 Initial DCH Access Rate for
PS Services.
3.1.3.5 CELL_DCH(DL DCH/UL DCH) <-> CELL_FACH(DL FACH/UL RACH)
There are two kinds of triggers for the switching between CELL_DCH and CELL_FACH:
traffic volume and load.
1. CELL_DCH <-> CELL_FACH channel switching triggered by traffic volume
i. CELL_DCH (DL DCH/UL DCH) -> CELL_FACH (DL FACH/UL RACH)
When a UE is in 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 reports (Event 4B) from the user plane and the
UE.
Event 4B is defined as an event when the traffic measurement is less than an

absolute threshold. For the detailed definition, refer to Section 3.1.4.1 Traffic
Volume Measurement.

The switching from CELL_DCH (DL DCH/UL DCH) to CELL_FACH (DL FACH/UL
RACH) is triggered when all the following conditions are satisfied at the same time:
 The system switch UDrbc.fachSwch for CELL_FACH switching is set to On.
 The service type is interactive or background.
 The system consecutively receives the traffic measurement reports (Event 4B)
from the user plane and the UE for UDrbc.dToFachThd times, and the switch
is triggered by downlink reports.
Note: If the system receives a traffic measurement report (Event 4A) from the
user plane or the UE when the number of receptions is smaller than the
threshold, the corresponding counter is cleared.
 The downlink target rate of the UE is smaller than the maximum downlink rate
threshold ULogicalRnc.rfach, and the current uplink rate is smaller than the
maximum uplink rate threshold ULogicalRnc.rrach.
Note: If the rate is at the lowest rate level specified by UlDrbcRateLevel and
DlDrbcRateLevel, this condition is not taken into consideration.
 For the UE in macro diversity state, the best radio link is on the S-RNC side;
otherwise, the DL DCH/UL DCH rate is to be decreased.
If concurrent services exist, all the services should meet the conditions for switching
to CELL_FACH.
If the conditions for CELL_FACH switching are met, but the admission to
CELL_FACH fails, and the current uplink or downlink rate is greater than the
minimum rate that UL DCHs or DL DCHs can bear (the lowest rate level specified
by UlDrbcRateLevel and DlDrbcRateLevel), the UL DCH or DL DCH rate decrease
is selected.
For the definitions of UlDrbcRateLevel and DlDrbcRateLevel, refer to Section

ii. CELL_FACH (DL FACH/UL RACH) -> CELL_DCH (DL DCH/UL DCH)
When a UE is in 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 reports (Event 4A) from the user plane or the
UE.
The switching from CELL_FACH (DL FACH/UL RACH) to CELL_DCH is triggered

when all the following conditions are satisfied at the same time:
 The system consecutively receives the traffic measurement reports of Event

4A from the user plane or the UE for UDrbc.fachE4aThd times.
 The cell is not overloaded.

Note: The uplink load is determined by the RTWP, while the downlink load is
determined by the TCP. For details about the overload threshold, refer to the
ZTE UMTS Overload Control Feature Guide.
The rate of the DL DCH/UL DCH is the initial rate of DRBC after switching to
CELL_DCH, which is [UL initial rate, DL initial rate] (refer to Section 3.1.2.2 Initial
Service Channel Allocation)
2. CELL_DCH -> CELL_FACH channel switching triggered by load
Refer to Section 3.1.3.3 Forced Transfer to FACH in the ZTE UMTS Overload Control
Feature Guide.
3.1.3.6 CELL_DCH(DL DCH/UL DCH) -> URA_PCH/CELL_PCH
When a UE uses the CELL_DCH (DL DCH/UL DCH) as a service bearer, the switching
from CELL_DCH (DL DCH/UL DCH) to URA_PCH/CELL_PCH can be triggered by the
traffic measurement reports (Event 4B0) from the user plane and the UE.
Event 4B0 is defined as an event when the traffic measurement value is 0. For the
detailed definition, refer to Section 3.1.4.1 Traffic Volume Measurement.
The switching from CELL_DCH (DL DCH/UL DCH) to URA_PCH/CELL_PCH is

triggered when all the following conditions are satisfied at the same time:
 The system switch UDrbc.pchSwch for URA_PCH/CELL_PCH switching is set to “1:

Only Support URA_PCH” or “2: Only Support CELL_PCH”.

 UCelInfoFDD.pchCellSwch is set to On.
 The service type is interactive or background.
 The system consecutively receives the traffic measurement reports with the
measurement values of 0 from the user plane and the UE forUDrbc.dToPchThd
times.
Note: If the system receives a report with a non-zero measurement value when the
cleared.
 For the UE in macro diversity state, the best radio link is on the S-RNC side.
If concurrent services exist, all the services should meet the conditions 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, the channel
transition strategy is as follows:
When the system consecutively receives the traffic measurement reports of Event 4B0
from the user plane and the UE for UDrbc.dToPchThd times:
1. If there are no radio links in the D-RNC, the rate of the PS service decreases to 0
kbps/0 kbps.
2. If there are radio links in the D-RNC, the strategy depends on whether the D-RNC
supports PS (0 kbps/0 kbps) (determined by UIurLink.rncFeatSwitchBIT18): if this
parameter is set to “0: 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.
Note: For the strategy of forbidding the transition to the PCH based on the CPU load,
refer to the ZTE UMTS Processor Overload Control Feature Guide.
3.1.3.7 CELL_FACH (DL FACH/UL RACH) -> URA_PCH/CELL_PCH
When a 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 reports (Event 4B0) from the user plane and the UE.
The switching from CELL_FACH to URA_PCH/CELL_PCH is triggered when all the

following conditions are satisfied at the same time:
 The system switch UDrbc.pchSwch for URA_PCH/CELL_PCH switching is set to

“ 1: Only Support URA_PCH” or “2: Only Support CELL_PCH”.
 UCelInfoFDD.pchCellSwch is set to On.
measurement values of 0 from the user plane and the UE for UDrbc.fToPchThd
times.
Note: If the system receives a report with a non-zero measurement value when the
cleared.
URA_PCH/CELL_PCH.
3.1.3.8 CELL_DCH (DL DCH/UL DCH) -> IDLE
When a UE uses the CELL_DCH as a service bearer, the switching from CELL_DCH to
IDLE is triggered when all the following conditions are satisfied at the same time:
 The service type is interactive or background.
measurement values of 0 from the user plane and the UE for UDrbc.dToIdleThd
times.
Note: If the system receives the measurement reports with non-zero traffic
measurement values when the number of receptions is smaller than the threshold,
the corresponding counter is cleared.
IDLE.

3.1.3.9 CELL_FACH (DL FACH/UL RACH) -> IDLE
When a UE uses the CELL_FACH to bear the interactive and background services, the
switching from CELL_FACH to IDLE is triggered when all the following conditions are
measurement values of 0 from the user plane and the UE for UDrbc.fToIdleThd
times.
Note: If the system receives the measurement reports with non-zero traffic
measurement values when the number of receptions is smaller than the threshold,
the corresponding counter is cleared.
IDLE.
3.1.3.10 URA_PCH/CELL_PCH -> IDLE
When the duration for which a UE stays in PCH state exceeds the threshold
UDrbc.pchHoldTimeThr, the UE transmits to IDLE state and the RRC connection is
released.
3.1.3.11 Handling Strategies When the Conditions of Switching to Different States

are Satisfied at the Same Time and Notes for the Switching to PCH/IDLE
1. [Switching to IDLE], [Switching to PCH], [Switching to FACH] and [DCH rate

decrease] are four independent functions controlled by different parameters and
have no coupling relations with each other. If more than one conditions for triggering
these four functions are satisfied at the same time, the handling priority is [Switching
to IDLE], [ Switching to PCH], [ Switching to FACH], and [DCH rate decrease] in
turn.
2. If the PCH switch of the system is set to On but the switching to PCH is not
supported (for example, the best link is not in the SRNC), the handling principle is
the same as that for the switching to IDLE.
3. If a UE is in PCH state and then leaves this state because a CS service is

established (determined by the IE “establishment Cause” in a CELL UPDATE

message), the timestamp when the UE leaves the PCH state is recorded if there is
no PS 0 kbps/0 kbps. Within the result of min(the moment of CS RAB assignment –
the timestamp when the UE leaves the PCH state, 5 seconds) from this timestamp
on, the channel transition and rate adjustment for the PS service based on the
traffic volume is not executed to avoid unnecessary reconfiguration caused by
channel transition.
3.1.3.12 Channel Selection Policies for UEs from the PCH State to Other States
3.1.3.12.1 Switching from the PCH State Triggered by the RNC Side
Receiving data from the downlink direction, the user plane determines whether to send
the data to the UE in PCH state. The user plane sends the 4A event to the control plane
and triggers the control plane to send a paging message to the UE. At the same time, the
timer URnluCfg.Pch4APendingTime is started by the user plane. If the UE is still in PCH
state after the timer expires, the 4A event needs to be sent again to trigger the control
plane to send the paging message to the UE.
3.1.3.12.2 Strategies for Selecting Channels by Priority
When a UE in PCH state sends a CELL UPDATE message because there is data to be
transmitted in the uplink or in the downlink, or there is a new service establishment
request:
1. For the UE of R5 and earlier:
 If bit8 of URncFunction.gresPara48 is set to “0: preferred to Cell_DCH”, the

UE is switched to the CELL_DCH state.
 If bit8 of URncFunction.gresPara48 is set to “1: preferred to Cell_FACH”, the

UE is switched to the CELL_FACH state.
2. For the UE of R6 and later:
After the UE is switched to the PCH state, if the RNC receives the CELL UPDATE
message with the cause of “uplink data transmission”:
i. If the switch ULogicalRnc.pchToOtherTVISw is set to On:

 If the CELL UPDATE message carries an IE “Traffic volume indicator” of which

the value is True, the RNC switches the UE to the CELL_DCH state, selects
the channel configuration of the CELL_DCH before the UE is switched to the
URA_PCH/CELL_PCH state preferentially, and matches the configuration with
the capability of the camping cell. If the matching succeeds, the corresponding
resources are allocated directly. If the matching or the admission fails, the
channel is allocated according to the strategies described in Section 3.1.2
Initial Channel Allocation.
 If the CELL UPDATE message carries an IE “Traffic volume indicator” of which

the value is False, or if the CELL UPDATE message does not carry an IE
“Traffic volume indicator”, the RNC switches the UE to the CELL_FACH state.
If the admission to CELL_FACH fails, the switching to CELL_DCH is
attempted (the initial service establishment procedure is used).
ii. If the switch ULogicalRnc.pchToOtherTVISw is set to Off:
 The RNC does not determine the TVI conditions but determines whether to
switch the UE to the FACH or the DCH according to bit8 of
URncFunction.gresPara48, which is the same as that of the UEs of R5 and
earlier.
Note:
i. The previous strategies are only applicable for PS services. For CS services,
the UE is directly allocated with the channel configuration used in CELL_DCH
state before it was switched to URA_PCH/CELL_PCH.
Where, the judgment whether it is a CS or PS service depends on the IE

“Establishment Cause” in the CELL UPDATE message as follows:
 It is regarded as a PS service if there is no “Establishment Cause” IE in the

CELL UPDATE message or if the IE “Establishment Cause” in the CELL
UPDATE message takes one of the following values:
interRAT_CellChangeOrder, originatingStreamingCall,
originatingInteractiveCall, originatingBackgroundCall,
originatingSubscribedTrafficCall, terminatingStreamingCall,

terminatingInteractiveCall, terminatingBackgroundCall,
originatingHighPrioritySignalling, terminatingHighPrioritySignalling,
originatingLowPrioritySignalling, terminatingLowPrioritySignalling,
callRe_establishment, nterRAT_CellReselection, and detach.
 Otherwise, it is regarded as a CS service.
3.1.3.12.3 Traffic Volume Measurement Used for Selecting Channels by Priority
If the switch ULogicalRnc.pchToOtherTVISw is set to On, the control plane of the RNC
sends the traffic volume measurement used for the PCH state to the UE. In the
measurement control message, the following conditions should be satisfied:
"measurement identity" = 4, "Traffic volume event identity" = "4a", and "Measurement
validity" = "all states except CELL_DCH".
The measurement should be terminated when the UE leaves the PCH state.
The MO UPchEvUeTrv is used. For how to obtain the measurement parameters, refer to
Section 3.1.4.1.1 Method of Obtaining Measurement Parameters in this document.
3.1.3.13 Uplink and Downlink Reconfiguration in One Step
The uplink and downlink reconfiguration in one step is used when the rate
reconfiguration of the same RB on the UL DCH and DL DCH occurs in succession during
a short time. This function can reduce the signaling overhead on Uu interfaces.
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 is performed directly.
When ULogicalRnc.drbcSwch is set to On for both the uplink and downlink, the
scenarios of the uplink and downlink reconfiguration in one step are as follows:
 UL DCH -> UL DCH (rate increase) based on traffic volume
If the UL DCH satisfies the rate increase conditions in advance, the timer
URncFunction.upUdRecfgTimer is started.

Before the timer expires, if the DL DCH also satisfies the rate increase conditions
triggered by traffic volume, the uplink and downlink rate increase reconfiguration in one
step is performed. If the admission decision fails, a DL rate increase process is
performed. If the admission decision fails again, a UL rate increase process is
performed.
Before the timer expires, if the DL DCH also satisfies the rate decrease conditions
triggered by traffic volume, the uplink and downlink rate decrease reconfiguration in one
step is performed. If the admission decision for the uplink rate increase fails, the DL rate
decrease reconfiguration is performed.
Before the timer expires, if the UL DCH does not satisfy the rate increase conditions
anymore, the timer is stopped and the UL DCH is not reconfigured.
If the timer expires, the UL rate increase reconfiguration is performed.
 DL DCH -> DL DCH (rate increase) based on traffic volume
If the DL DCH satisfies the rate increase conditions in advance, the timer
URncFunction.upUdRecfgTimer is started.
Before the timer expires, if the UL DCH also satisfies the rate increase conditions
triggered by traffic volume, the uplink and downlink rate increase reconfiguration in one
step is performed. If the admission decision fails, a DL rate increase process is
performed. If the admission decision fails again, a UL rate increase process is
performed.
Before the timer expires, if the UL DCH also satisfies the rate decrease conditions
triggered by traffic volume, the uplink rate decrease and downlink rate increase
reconfiguration in one step is performed. If the admission decision for the DL rate
increase fails, the UL rate decrease reconfiguration is performed.
Before the timer expires, if the DL DCH does not satisfy the rate increase conditions
anymore, the timer is stopped and the DL DCH is not reconfigured.
If the timer expires, the DL rate increase reconfiguration is performed.
 UL DCH -> UL DCH (rate decrease) based on traffic volume

If the UL DCH satisfies the rate decrease conditions in advance, the timer
URncFunction.dnUdRecfgTimer is started.
Before the timer expires, if the DL DCH also satisfies the rate decrease conditions
step is performed.
Before the timer expires, if the DL DCH also satisfies the rate increase conditions
triggered by traffic volume, the uplink rate decrease and downlink rate increase
reconfiguration in one step is performed. If the admission decision for the DL rate
increase fails, the UL rate decrease reconfiguration is performed.
Before the timer expires, if the UL DCH does not satisfy the rate decease conditions
anymore, the timer is stopped and the UL DCH is not reconfigured.
If the timer expires, the UL rate decrease reconfiguration is performed.
 DL DCH -> DL DCH (rate decrease) based on traffic volume
If the DL DCH satisfies the rate decrease conditions in advance, the timer
URncFunction.dnUdRecfgTimer is started.
Before the timer expires, if the UL DCH also satisfies the rate decrease conditions
step is performed.
Before the timer expires, if the UL DCH also satisfies the rate increase conditions
triggered by traffic volume, the uplink rate increase and downlink rate decrease
reconfiguration in one step is performed. If the admission decision for the UL rate
increase fails, the DL DCH rate decrease reconfiguration is performed.
Before the timer expires, if the DL DCH does not satisfy the rate decease conditions
anymore, the timer is stopped and the DL DCH is not reconfigured.
If the timer expires, the DL rate decrease reconfiguration is performed.

3.1.4 Related Measurement
3.1.4.1 Traffic Volume Measurement
Traffic measurement includes the BO measurements for UTRAN and UE service buffer
capacities, which are respectively measured from the user plane and the UE. The
parameter obtaining methods and the basic principles are described separately in the
following sections.
3.1.4.1.1 Method of Obtaining Measurement Parameters
The traffic volume measurement profile UtrvMeasProfile is obtained by matching

UUtranCellFDD.refUTrvMeasProfile with UTrvMeasProfile.profileId, and then the
measurement parameters for a certain measurement purpose are obtained from the child
objects of this profile.
Where, the traffic volume measurement profile UtrvMeasProfile includes the following
child objects:
 UrachEvtUeTrv (UE Traffic Volume Event Measurement Configuration for RACH)
 UrachPrdUeTrv (UE Traffic Volume Period Measurement Configuration for RACH)
 UfachEvUpTrv (UP Traffic Volume Event Measurement Configuration for FACH)
 UDchEvUeTrv (UE Traffic Volume Event Measurement Configuration for DCH)
 UDchEvUpTrv (UP Traffic Volume Event Measurement Configuration for DCH)
 UDchPrdUeTrv (UE Traffic Volume Period Measurement Configuration for DCH)
 UPchEvUeTrv (UE Traffic Volume Event Measurement Configuration for PCH)
If the uplink channel for a service is carried on a DCH, the measurement is executed by
the UE. In addition, if traffic volume is measured based on events, the following
measurement parameters are obtained from the MO UDchEvUeTrv:
UE Traffic Volume Measurement
UDchEvUeTrv.ueTrvMCfgNo
Configuration Index


UDchEvUeTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode UDchEvUeTrv.measRptTrMod
Measurement Quantity UDchEvUeTrv.measQuantity
Time Interval for Taking an Average or a

UDchEvUeTrv.averageTime
Variance
RLC Buffer Payload for Each RB UDchEvUeTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each RB UDchEvUeTrv.rptRlcAveInd
Variance of RLC Buffer Payload for Each RB UDchEvUeTrv.rptRlcVarInd
Event Number of UE Traffic Volume

UDchEvUeTrv.measEvtNum
Measurement
UE Traffic Volume Measurement Event

UDchEvUeTrv.meaEvtId
Identity
Traffic Volume Threshold of Event 4A/4B for
UDchEvUeTrv.rptThres0
DCH (8kbps)
DCH (16kbps)
DCH (32kbps)
DCH (64kbps)
DCH (128kbps)
DCH (256kbps)
DCH (384kbps)
Time to Trigger UDchEvUeTrv.trigTime
Pending Time After Trigger UDchEvUeTrv.pendingTime
If the downlink channel for a service is carried on a DCH, the measurement is executed
by the user plane, and the following measurement parameters are obtained from the MO
UDchEvUpTrv:
UDchEvUpTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode UDchEvUpTrv.measRptTrMod


UDchEvUpTrv.ueTrvMCfgNo
Configuration Index
Measurement Quantity UDchEvUpTrv.measQuantity

UDchEvUpTrv.averageTime
Variance
RLC Buffer Payload for Each RB UDchEvUpTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each RB UDchEvUpTrv.rptRlcAveInd
Variance of RLC Buffer Payload for Each RB UDchEvUpTrv.rptRlcVarInd

UDchEvUpTrv.measEvtNum
Measurement

UDchEvUpTrv.meaEvtId
Identity
UDchEvUpTrv.rptThres0
DCH (8kbps)
DCH (16kbps)
DCH (32kbps)
DCH (64kbps)
DCH (128kbps)
DCH (256kbps)
DCH (384kbps)
Time to Trigger UDchEvUpTrv.trigTime
Pending Time After Trigger UDchEvUpTrv.pendingTime
If the uplink channel for a service is carried on an RACH, the measurement is executed
by the UE. In addition, if traffic volume is measured based on events, the following
measurement parameters are obtained from the MO URachEvtUeTrv:
URachEvtUeTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode URachEvtUeTrv.measRptTrMod
Measurement Quantity URachEvtUeTrv.measQuantity


URachEvtUeTrv.ueTrvMCfgNo
Configuration Index
URachEvtUeTrv.averageTime
Variance
RLC Buffer Payload for Each RB URachEvtUeTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each

URachEvtUeTrv.rptRlcAveInd
RB
Variance of RLC Buffer Payload for

URachEvtUeTrv.rptRlcVarInd
Each RB

URachEvtUeTrv.measEvtNum
Measurement

URachEvtUeTrv.meaEvtId
Identity
Traffic Volume Threshold of Event

URachEvtUeTrv.rptThres
4A/4B for RACH Channel
Time to Trigger URachEvtUeTrv.trigTime
Pending Time After Trigger URachEvtUeTrv.pendingTime
Tx Interruption After Trigger

URachEvtUeTrv.txInterCfgPre
Configuration Tag
Tx Interruption After Trigger URachEvtUeTrv.txInterruption
If the downlink channel for a service is carried on an FACH, the measurement is

executed by the user plane, and the following measurement parameters are obtained
from the MO UFachEvUpTrv:
UFachEvUpTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode UFachEvUpTrv.measRptTrMod
Measurement Quantity UFachEvUpTrv.measQuantity

UFachEvUpTrv.averageTime
Variance
RLC Buffer Payload for Each RB UFachEvUpTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each RB UFachEvUpTrv.rptRlcAveInd
Variance of RLC Buffer Payload for Each RB UFachEvUpTrv.rptRlcVarInd
Event Number of UE Traffic Volume UFachEvUpTrv.measEvtNum


UFachEvUpTrv.ueTrvMCfgNo
Configuration Index
Measurement

UFachEvUpTrv.meaEvtId
Identity

UFachEvUpTrv.rptThres
FACH Channel
Time to Trigger UFachEvUpTrv.trigTime
Pending Time After Trigger UFachEvUpTrv.pendingTime
If the channel for a service is carried on an uplink DCH, the measurement is executed by
the UE. In addition, if traffic volume is measured based on periods, the following
measurement parameters are obtained from the MO UDchPrdUeTrv:
UDchPrdUeTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode UDchPrdUeTrv.measRptTrMod
Measurement Quantity UDchPrdUeTrv.measQuantity

UDchPrdUeTrv.averageTime
Variance
RLC Buffer Payload for Each RB UDchPrdUeTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each RB UDchPrdUeTrv.rptRlcAveInd
Variance of RLC Buffer Payload for Each RB UDchPrdUeTrv.rptRlcVarInd
Amount of Reporting in Period Report

UDchPrdUeTrv.prdRptAmount
Criteria
Reporting Interval in Period Report Criteria UDchPrdUeTrv.prdRptInterval
If the channel for a service is carried on an RACH, the measurement is executed by the
UE. In addition, if traffic volume is measured based on periods, the following
measurement parameters are obtained from the MO URachPrdUeTrv:
URachPrdUeTrv.ueTrvMCfgNo
Configuration Index
Measurement Report Transfer Mode URachPrdUeTrv.measRptTrMod
Measurement Quantity URachPrdUeTrv.measQuantity


URachPrdUeTrv.ueTrvMCfgNo
Configuration Index
URachPrdUeTrv.averageTime
Variance
RLC Buffer Payload for Each RB URachPrdUeTrv.rptRlcBufInd
Average of RLC Buffer Payload for Each

URachPrdUeTrv.rptRlcAveInd
RB
Variance of RLC Buffer Payload for Each

URachPrdUeTrv.rptRlcVarInd
RB
Amount of Reporting in Period Report

URachPrdUeTrv.prdRptAmount
Criteria
Reporting Interval in Period Report Criteria URachPrdUeTrv.prdRptInterval
If the user plane of the RNC sends the traffic volume measurement control used for the
PCH state to a UE, the following measurement parameters are obtained from the MO
UPchEvUeTrv:
Time Interval for Taking an Average or a Variance UPchEvUeTrv.averageTime
UE Traffic Volume Measurement Event Identity UPchEvUeTrv.MeaEvtId

UPchEvUeTrv.measEvtNum
Measurement
Measurement Quantity UPchEvUeTrv.measQuantity
Measurement Report Transfer Mode UPchEvUeTrv.measRptTrMod
Traffic Volume Threshold of Event 4A/4B for UE

UPchEvUeTrv.rptThres
on PCH State
UE Traffic Volume Measurement Configuration

UPchEvUeTrv.ueTrvMCfgNo
Index
3.1.4.1.2 Basic Principle of Traffic Volume Measurement
Note: The parameters used in this section are obtained by the method described in the
previous section.
Traffic measurement includes the BO measurements for UTRAN and UE service buffer
capacities, which are respectively measured from the user plane and the UE.

If the AM mode is selected as the RLC mode for traffic measurement reporting, the RNC
requires the UE to retransmit the SDUs if erroneous (discontinuous) SDUs are received.
If the UM mode is selected, the retransmission is not available.
For the services using the AM RLC mode to transmit data, the BO value of an RB is the
sum of the data in the RLC queue-to-send queue and retransmission queue, and the
data in the logical channel. For the services using the UM RLC mode to transmit data,
the BO value of an RB is the sum of the data in the RLC queue-to-send queue and the
data in the logical channel. For the measurement executed in the user plane, the user
plane takes the average of BO sample values collected in 20 ms to trigger an event. For
the measurement executed in an UE, the UE evaluates the conditions for triggering
the event during each TTI at least.
 For RLC buffer payload: The BO value is that of an RB.
 For Average RLC buffer payload: The BO value is the average of the BO values of
an RB.
 For Variance of RLC buffer payload: The BO value is the variance of the BO values
of an RB.
The related events of traffic volume measurement include:
 Event 4A: The event is triggered when the traffic measurement value is greater than
an absolute threshold for a certain period of time (Trigger Time). The delay timer
"Pending Time" 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 for a certain period of time (Trigger Time). The delay timer
"Pending Time" is set to prevent the event from being triggered frequently.
 Event 4B0: The event is triggered when the traffic measurement value remains 0 for
a certain period of time (Trigger Time). Event 4B0 is an exceptional case of Event
4B, and its delay timer "Pending Time" is the same as that of Event 4B.
The application principles of Trigger Time and Pending Time in the measurement events
are shown in the following figure. The example is based on Event 4A.

Figure 3-2 Event Triggering of Traffic Measurement
Traffic Volume
Thr_4A
Pending Pending
Trigger Time Time
Time
Report 4A Report 4A Report 4A
The time for triggering channel switching is calculated as follows:
Time = TiggerTime + (Counter Threshold – 1) × PendingTime
The absolute thresholds of Event 4A and Event 4B are configured as follows:
1. The smaller the threshold value of Event 4A is, the quicker the system responses to
the service demand of the UEs, and the sooner the bandwidth increase is triggered;
therefore more radio resources can be allocated, and vice versa.
2. The bigger the threshold value of Event 4B is, the quicker the system responses to
the service demand of the UEs, and the sooner the occupied bandwidth is
decreased, and vice versa.
The parameters Trigger Time and Pending Time are configured as follows:
1. The smaller the value of Trigger Time for Event 4A is, the quicker the control plane
receives the reports and increases the bandwidth when the traffic measurement
reaches the threshold for triggering Event 4A. Therefore, the demand for the service
rates of UEs is reflected in a better way, and vice versa. However, if the parameter
is configured to a very low value, the system responds to the service demand that
fluctuates in a very short moment, resulting in unnecessary bandwidth increase.
2. The smaller the value of Pending Time for Event 4A is, the quicker the control plane
consecutively receives the reports and increases the bandwidth when the traffic
measurement reaches the threshold for triggering Event 4A. Therefore, the demand
for the service rates of UEs is reflected in a better way, and vice versa. However, if

the parameter is configured to a very low value, the reporting of Event 4A may result
in considerable bandwidth usage.
3. The smaller the value of Trigger Time for Event 4B is, the quicker the control plane
consecutively receives the reports and decreases the bandwidth when the traffic
measurement reaches the threshold for triggering Event 4B. Therefore, the demand
the parameter is configured to a very low value, the system responds to the service
demand that fluctuates in a very short moment, resulting in unnecessary bandwidth
decrease.
4. The smaller the value of Pending Time of Event 4B is, the quicker the control plane
consecutively receives the reports and decreases the bandwidth when the traffic
measurement reaches the threshold for triggering Event 4B. Therefore, the demand
the parameter is configured to a very low value, the reporting of Event 4B may result
in considerable bandwidth usage. Therefore, the perception of subscribers and
bandwidth utilization should be taken into consideration before configuration.
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
3.1.4.2 Internal UE TxP Measurement
The internal UE measurement measures the transmission power (TxP) of UEs by event
reporting.

3.1.4.2.1 Method of Obtaining Measurement Parameters
The internal UE measurement profile UUeIntMeasProfile is obtained by matching

UUtranCellFDD. refUUeIntMeasProfile with UueIntMeasProfile.profileId, and then the
measurement parameters are obtained from the child object UPsEvtTPUeInt.
UE Internal Measurement Configuration
UPsEvtTPUeInt.ueIntMCfgNo
Index
Measurement Report Transfer Mode UPsEvtTPUeInt.measRptTrMod
Filter Coefficient UPsEvtTPUeInt.filterCoeff
Maximum Event Number of UE Internal

UPsEvtTPUeInt.measEvtNum
Measurement
UE Internal Measurement Event Identity UPsEvtTPUeInt.meaEvtId
Time to Trigger UPsEvtTPUeInt.trigTime
UE Transmitted Power Threshold UPsEvtTPUeInt.txPowerThres
3.1.4.2.2 Basic Principle of UE Transmission Measurement
There are two kinds of events: Event 6A and Event 6B.
Event 6A: The event is triggered when the UE TxP measurement value is greater than an
absolute threshold for a certain period of time (Trigger Time).
Event 6B: The event is triggered when the UE TxP measurement value is smaller than
an absolute threshold for a certain period of time (Trigger Time).
The threshold parameter for Event 6A and Event 6B (Txpower_Threshold) is a delta

value relative to the value of min(maximum UE TxP, maximum uplink DPCH TxP).
The higher the value of Event 6A is, the less likely the uplink DCH rate decrease is
triggered based on power, that is, the UE TxP is higher with more power consumption
and more interference with other UEs. If the power consumption and interference with
other UEs are not taken into consideration, Event 6A can be configured to a high value.
The lower the value of Event 6A is, the more likely the uplink DCH rate decrease is
triggered based on power. In this case, the user experience is affected.
The higher the threshold of Event 6B is, the more likely the power in 6B status is reported,
and therefore the rate increase can be retriggered based on traffic. However, a certain

margin should be configured between the thresholds of Event 6A and Event 6B;
otherwise, the rate increase is triggered based on traffic demand after the rate is
decreased based on Event 6A. The lower the threshold of Event 6B is, the less likely the
power in 6B status is reported, which means that it is less likely to trigger the rate
increase based on traffic volume. In this case, the user experience is affected.
The measurement is triggered if the following conditions are satisfied at the same time: A
PS service exists, the DRBC switch ULogicalRnc.drbcSwch is set to On in the uplink,
ULogicalRnc.ulPwrDasf is set to On, and all services use uplink DCHs as bearers. After
each uplink rate adjustment, the RNC sends a measurement control message for the UE
TxP to the UE again. If these conditions are not met, the UE TxP measurement is
switched off.
3.1.4.3 Node B Dedicated TCP Measurement
The Node B dedicated TCP is related with a UE and indicates that the downlink
transmission power for the UE (the TCP on a given carrier, a given scramble, and a given
channelization code) is measured by the Node B. It acts as a factor for triggering
bandwidth decrease and as a restriction on bandwidth increase. The Node B dedicated
TCP measurement that is used to trigger DRBC rate adjustment is reported periodically.
The method for obtaining the measurement parameters of the periodical Node B
dedicated TCP measurement is as follows: The following parameters are obtained from
the record of UNbDedMeas.nbDMCfgNote with the value of “0: Period Report
Parameters for TCP in Power Balance”.
Dedicated Measurement Type UNbDedMeas.dedMeasType
Measurement Filter Coefficient UNbDedMeas.measFilterCoeff
Report Characteristics UNbDedMeas.rptType
Choice Report Periodicity Scale UNbDedMeas.rptPrdUnit
Report Period UNbDedMeas.rptPrd
Two sets of measurement parameters relating to Event A and Event B are configured:
 Event A: The event is triggered when the Node B D-TCP measurement value is
greater than a specific absolute threshold (Threshold_A). Event A is used to trigger
downlink rate decrease. When Event A is reported, the downlink transmission

power of the UE is considered to be high. Where, Threshold_A is obtained from

UNbDedMeas.EvtAbTcpThrd corresponding to the record of
UNbDedMeas.NbDMCfgNote with the value of “2: Event A Report Parameters for
TCP in DASF-PS”.
 Event B: The event is triggered when the Node B D-TCP measurement value is
smaller than a specific absolute threshold (Threshold_B). Event B is used to check
whether the downlink transmission power is low. When Event B is reported, the
downlink transmission power of the UE is considered to be low. The downlink rate
increase can be triggered by traffic. Where, Threshold_A is obtained from
UNbDedMeas.EvtAbTcpThrd corresponding to the record of
UNbDedMeas.NbDMCfgNote with the value of “3: Event B Report Parameters for
TCP in DASF-PS”.
Where, UNbDedMeas.EvtAbTcpThrd is a delta value relative to the maximum DPCH

downlink transmission power which is related to service types. The values of different
DCH rate levels can be configured based on the parameter UNbDedMeas.DlRateLevel.
The details are listed in the following table:
Corresponding Rate Range of PS Corresponding
Rate Level
Services Threshold of Event A/B
The first rate UNbDedMeas.EvtAbTcp

R<= UNbDedMeas.DlRateLevel[0]
level Thrd[0]
The second UNbDedMeas.DlRateLevel[0]<R<= UNbDedMeas.EvtAbTcp

rate level UNbDedMeas.DlRateLevel[1] Thrd[1]
The third rate UNbDedMeas.EvtAbTcp

R> UNbDedMeas.DlRateLevel[1]
level Thrd[2]
Where, R is the current DRBC rate level of the PS service.
The rules for configuring the threshold of the Event A and Event B are as follows:
The higher the value of Event A is, the less likely the downlink DCH rate decrease is
triggered based on power, that is, the power of a single UE is higher. If the restriction on
the system power is not taken into consideration, the event can be configured with a high
value. The lower the value of Event A is, the more likely the downlink DCH rate decrease
is triggered based on power. In this case, the user experience is affected.

The higher the threshold of Event B is, the more likely the power in B status is reported.
However, a certain margin should be configured between the thresholds of Event A and
Event B; otherwise, the rate increase is triggered based on traffic demand after the rate
is decreased based on Event A. The lower the threshold of Event B is, the less likely the
power in B status is reported, which means that it is less likely to trigger the rate increase
based on traffic. In this case, the user experience is affected.
The measurement is triggered if the following conditions are satisfied at the same time: A
PS service exists, the DRBC switch ULogicalRnc.drbcSwch is set to On in the downlink,
ULogicalRnc.dlPwrDasf is set to On, and all services use downlink DCHs as bearers. If
these conditions are not met, the Node B dedicated TCP measurement is switched off.
3.1.5 Method of Obtaining DRBC Parameters
ULogicalRnc.refUDrbcProfile is obtained from the MO ULogicalRnc based on the PLMN

that the UE belongs to. The DRBC configuration information is obtained according to the
following method:
 The dynamic radio bearer control information profile UDrbcProfile is obtained by

matching ULogicalRnc.refUDrbcProfile with UDrbcProfile.profileId, and then the
DRBC parameters are obtained from the child object UDrbc.
Besides, UDrbcProfile.drbcStragyName is introduced to know which function

UDrbcProfile is used for and the special characteristics of the corresponding parameter
because UDrbcProfile includes both the records of the child objects for DPI DRBC and
non-DPI DRBC. This parameter is only used to display the strategy usage of the DRBC
parameters corresponding to the profile on the OMCR.
3.2 ZWF21-05-016 Video Call Prohibited in Specific

Area
In some special scenarios where the access/handover of the CS64K service is not
expected to be supported in a cell, the parameters UUtranCellFDD.Cs64Switch and
UExternalUtranCellFDD.AdjCs64Switch are used to control whether a cell supports the

CS64k service in the SRNC and DRNC respectively. If the CS64K service is restricted in
a cell, the access and handover of the CS64K service are prohibited.
The initial access and handover scenarios are described as follows:
1. Initial access
If the switch UUtranCellFDD.cs64Switch of a cell is set to Off, the CS64K service is

not allowed to be accessed; otherwise, the access of the CS64K service is allowed.
For the UE in macro diversity state, if any cell in the active set is not allowed to
access the CS64K service, the access of the CS64K service to other cells is not
allowed.
2. The CS64K service has been established.
i. If the CS64K service has been established and if the source cell supports
CS64K but the target cell does not supports CS64K due to mobility:
 For a handover in intra-RNC cells and the UE with the CS64K service, if
UUtranCellFDD.cs64Switch in the target cell is set to Off and the UE supports
CS64K falling back to AMR12.2K, the CS64K service falls back to the
AMR12.2K service and then the UE performs the related handover; otherwise
the UE does not perform the fallback and handover.
 For a handover in inter-RNC cells and the UE with the CS64K service, if
UExternalUtranCellFDD.adjCs64Switch in the target cell is set to Off and the
UE supports CS64K falling back to AMR12.2K, the CS64K service falls back to
the AMR12.2K service and then the UE performs the related handover;
otherwise the UE does not perform the fallback and handover. If a neighboring
cell belonging to the DRNC is not configured in the SRNC, the neighboring cell
supports CS64K by default.
ii. A call is reestablished because the link is interrupted due to bad radio quality:
If the target cell does not support CS 64K, the CS64K service is prohibited; if
the UE supports CS64K falling back to AMR12.2K, the CS64K service falls
back to the AMR12.2K service and the new measurement control is
re-delivered; otherwise the fallback does not occur.

3.3 Other Descriptions
3.3.1 Rate Matching for Sub-Services
The CN sends necessary QoS information to the RNC by an RAB assignment message.
The QoS information defines the related traffic information, for example, the maximum bit
rate. The RNC controls the user rate according to the rate requirement of the CN, UE
capability, and real traffic establishment. The whole process is called rate matching.
Rate matching includes the following procedures (the uplink and downlink perform the
procedures separately according to the same principle):
1. Iu assignment rate matching according to UE capability
For a DCH: MaxBR1 = max{max rate of the Iu interface (max rate after negotiation if
there is an MBR negotiation), 384 kbps}.
2. The rate is fuzzy matched from MaxBR1 to the nearest sub-service in the sub-
service list (matched to the sub-service of which the rate is the closest to and not
smaller than MaxBR1), and the parameter configurations for this service are
obtained according to the matched sub-service number. Where, the parameter
MaxBitRate is used as MaxBR2.
3. The max bit rate of this service controlled by the RNC is the value of min(MaxBR2,
max rate of the Iu interface (max rate after negotiation if there is an MBR
negotiation)).
3.3.2 MBR Controlling in the RNC
Refer to the description in the ZTE UMTS QOS Guarantee Feature Guide.
3.3.3 Compatibility Strategy for the iPhones not Compliant With

Encryption Protocols
When the iPhones of some versions trigger conversational services, the bubble noise
may occur due to losing alignment of the CFN if the RRC connection is established on
CELL_FACH and the UEs transit to CELL_DCH in a way that is not compliant with

encryption protocols during the RAB process. To be compatible with this kind of iPhones,
ZTE sets a switch URncFunction.csRrcOnFachSwch to control the RRC not to be
established on CELL_FACH to ensure that the UE does not attempt to access
CELL_FACH after the admission decision for RRC on CELL_DCH fails.
After the admission decision for RRC on CELL_DCH fails, whether to access
FACH/RACH is determined by URncFunction.csRrcOnFachSwch if the cause indicated
in the RRC connection request is a non-emergency call with a CS service. If
URncFunction.csRrcOnFachSwch is set to Off, the RRC connection for a
non-emergency call with a CS service cannot be established on FACH/RACH.
3.3.4 Special Handling for the UEs Insensitive to Power Consumption
For the UEs not sensitive to power consumption, for example, data card users,
background data transmission occurs frequently, resulting in frequent channel switching.
Therefore, the IE “Device type” is added to an RRC Connection Setup Complete
message for the network to identify their requirements and take special measures.
The method for the network to identify that a UE is not sensitive to power consumption is
as follows: If the UE carries the IE “Device type” with the value of
“doesNotBenefitFromBatteryConsumptionOptimisation” in an RRC Connection Setup
Complete message, it is considered that the UE is insensitive to power consumption.
For this kind of UEs, the ZTE RNC has the following strategy: If traffic measurement
(Event 4B0) triggers channel switching to the PCH or the idle state,
UDrbc.deltaNumE4B0Thd times are added to the required number of times to report
Event 4B0.
Note:
1. For the previous channel switching, if the report with a non-zero traffic
measurement is received before the threshold times is reached, the counter is
cleared.
2. Other conditions required for channel switching remain unchanged.
3. Tests show that some mobile phones also report the IE “Device type”.

3.3.5 UE PCH Compatibility Strategies
Some UEs supporting early protocol versions are not perfectly compatible with PCH. To
fix the PCH compatibility problem, the ZTE RNC introduces UE-based protocol versions
and uses independent control strategy to control the state transition to PCH.
1. For R99 and R4 UEs:
If URncFunction.R99R4PchSwch is set to “0: Not Allowed”, the state transition to the

PCH state (URA_PCH or CELL_PCH) is not performed, and the state transition to the
idle state can be performed when the conditions for switching to the idle state are
satisfied.
If URncFunction.R99R4PchSwch is set to “1: Allowed”, the state transition to PCH

(URA_PCH or CELL_PCH) can be performed when the conditions for switching to the
PCH state are satisfied.
2. For R5 UEs:
If bit0 of URncFunction.gresPara52 is set to 0, the state transition to PCH (URA_PCH or

CELL_PCH) is not performed, and the state transition to the idle state can be performed
when the conditions for switching to the idle state are satisfied.
If bit0 of URncFunction.gresPara52 is set to 1, the state transition to PCH (URA_PCH or

CELL_PCH) can be performed when the conditions for switching to the PCH state are
satisfied.
3. For R6/R7/R8 UEs:
If the bit0, bit1, and bit2 of URncFunction.gResPara4 are set to 1, the state transition to
PCH (URA_PCH or CELL_PCH) is not performed and the state transition to the idle state
can be performed when the conditions for switching to the idle state are satisfied. If the
bit0, bit1, and bit2 of URncFunction.gResPara4 are set to 0, the state transition to PCH
(URA_PCH or CELL_PCH) can be performed when the conditions for switching to the
PCH state are satisfied.
Where, bit0, bit1, and bit2 correspond to the R6, R7, and R8 UEs respectively.

3.3.6 DRBC F/P->D Performance Optimization
To solve the problem of CPU overload, the optimization procedure for the channel
transition from CELL_PCH/URA_PCH or CELL_FACH to CELL_DCH state is performed
without complete channel re-selection. The strategy is as follows:
For a UE in URA_PCH/CELL_PCH state, if the UE sends a cell update message

because of uplink data transmission, or downlink data transmission, or a new service
establishment request, or switching from the CELL_FACH state to the CELL_DCH state
triggered based on traffic measurement (Event 4A), priority is given to the channel
configuration for the CELL_DCH state used before the URA_PCH/CELL_PCH or
CELL_FACH state. The channel configuration is matched with the capability of the
current cell based on the traffic type preference (UUtranCellFDD.csTrafPrefInd and
UUtranCellFDD.r99PsTrafPrefInd) and the support of the cell for the configuration.
If the matching process succeeds, the channel configuration for the CELL_DCH state is
used. If the matching process or the admission fails, the channel is allocated according to
the strategies described in Section 3.1.2 Initial Channel Allocation.
Note:
 The aim of this strategy is to reduce the handling time for the DRBC channel
transition of URA_PCH -> CELL_DCH and CELL_FACH -> CELL_DCH and for the
cell selection procedure. However, the last channel configuration needs to be kept
when the UE leaves the CELL_DCH state.
 Traffic type preference matching: If the traffic type is included in the value of
UUtranCellFDD.csTrafPrefInd or UUtranCellFDD.r99PsTrafPrefInd, the traffic type
preference is matched in this cell.
3.3.7 Penalty Policy for the UEs That Cannot Stay in PCH State
After the function of the PCH state is enabled, it is found that some UEs fail to stay in
PCH state stably in the actual network, that is, when a UE transmits to PCH state, it
requests data transmission soon. In this case, the transition between the PCH state and
the CELL_FACH/CELL_DCH state occurs frequently. To solve this problem, the ZTE

RNC introduces the penalty policy. With this policy, if a UE fails to stay in PCH state, it is
forbidden to transmit to the PCH state.
This function is controlled by ULogicalRnc.punishUePchSwch.
The method to identify a UE that cannot stay in PCH state is as follows: If the UE stays in
PCH state for less than one second, it is considered that the UE fails to stay in PCH
state.
For the UE that is considered to fail to stay in PCH state, if

ULogicalRnc.punishUePchSwch is set to “1: On”, the UE is not allowed to transmit to the
PCH state again during the call period to avoid ping-pong between PCH and other
states.
3.3.8 The Controlling Strategy of Whether to Release the Traffic

Measurement Control Sent to the UE before When Transition to PCH
Use bit1 of URncFunction.gRESPARA52 to control whether to release the traffic

measurement control sent to the UE before when transition to PCH
 If bit 1 of URncFunction.gRESPARA52 takes value of “Release the traffic volume

measurement before switching to PCH”, if the RNC has sent traffic measurement
control to the UE before, it needs to release the traffic measurement control before
it executes transitioning to CELL_PCH/URA_PCH; if it fails to transition to
CELL_PCH/URA_PCH and returns to original channel, it needs to send new traffic
measurement control to the UE.
 If bit1 of URncFunction.gRESPARA52 is “Not release the traffic volume

measurement before switching to PCH”, the RNC needs not to release the traffic
measurement control before it executes transitioning to CELL_PCH/URA_PCH
even it has sent traffic measurement control to the UE before.
3.3.9 PCH is Forbidden Based on the Number of UEs
To avoid the high usage of the internal CPU resources of the RNC due to a large number
of UEs transiting to the PCH state, the following limitations are set for the RNC:

If the actual number of DMP UEs is beyond the product of the number of online UEs on
the physical board of the logical DMP processor and URncInfo.PchBarredUsrThd, all the
UEs in the DMP are forbidden to transmit to the PCH state.
Where, the number of online UEs is 6000 for V3, 22500 for V4 USP, and 32500 for V4
USP2A.
4 Parameters
4.1 ZWF21-04-004 Parameters Related to DRBC
4.1.1 Dynamic Radio Bearer Control Information
Table 4-1 Parameter List (Dynamic Radio Bearer Control Information)
Recom
Parameter Value Default mende
GUI Name Parameter Description Unit
Name Range Value d
Value
This parameter indicates

the event 4A counter
threshold for increasing
rate on DCH or
DCH->HSPA. For the UE
Event 4A
using DCH in both
Counter
directions, if the times of
Threshold for
UDrbc.dch the measured RLC buffer
Increasing 1..255 N/A
E4aThd payload of the uplink or
Rate on DCH
downlink is larger than the
or
4A threshold exceed the
DCH->HSPA
threshold indicated by this
parameter, UE's data rate
on DCH will be increased
or UE will be transferred
from DCH to HSPA. 2 2
UDrbc.dch Event 4B This parameter indicates 1..255 N/A 2 2

Recom
Name Range Value d
Value
E4bThd Counter the event 4B counter
Threshold for threshold for decreasing
Decreasing rate on DCH. For the UE
Rate on DCH used DCH in both
directions, if the times of
the measured RLC buffer
payload of the uplink or
downlink is less than the
4B threshold exceed the
parameter, UE's data rate
on DCH will be decreased.
Event A This parameter indicates

Counter the reported times of
Threshold for threshold of DTCP
PS on DL measurement event A. If
UDrbc.dtcp
DCH or DL the times of the event A 1..255 N/A 2 2
EaThd
AMR that only uses TCP is
Decreasing larger than this threshold,
Rate Based the speed of downlink PS
on D-TCP or AMR will be reduced.

the event B counter
Event B
threshold of consecutive
Counter
DTCP reports. If the times
Threshold for
of dedicated transmitted
Restriction PS
code power is less than
Increasing
the event B threshold
UDrbc.dtcp Rate on DL
exceed the threshold 1..255 N/A 2 2
EbThd DCH or
indicated by this
Triggering DL
parameter, it will trigger the
AMR
downlink AMR increasing
Increasing
rate or allow PS services
Rate Based
to increase rate on DL
on D-TCP
DCH based on traffic
volume report.

Recom
Name Range Value d
Value

the event 4B counter
threshold for CELL_DCH
to idle state shared by
uplink and downlink when
Event 4B
PCH is not supported by
Counter
UE or UTRAN. For the UE
Threshold for
UDrbc.dTo in CELL_DCH state, if the
CELL_DCH to 1..65535 N/A 3 3
IdleThd measured RLC buffer
Idle Shared by
payload of the uplink and
Uplink and
downlink is zero, and the
Downlink
triggering times of the
event 4B reaches this
threshold, UE will be
transferred from
CELL_DCH to idle state.

to PCH shared by uplink
Event 4B
and downlink. For the UE
Counter
in CELL_DCH state, if the
Threshold for
UDrbc.dTo measured RLC buffer
CELL_DCH to 1..65535 N/A 3 3
PchThd payload of the uplink and
PCH Shared
by Uplink and
Downlink
transferred from
CELL_DCH to PCH.
Event 4A This parameter indicates

Counter the event 4A counter
UDrbc.fach Threshold for threshold for
1..65535 N/A 1 1
E4aThd CELL_FACH CELL_FACH->CELL_DCH
to CELL_DCH . For the UE in
Shared by CELL_FACH state, if the

Recom
Name Range Value d
Value
Uplink and measured RLC buffer
Downlink payload of the uplink or
downlink exceeds the
event 4A threshold, and
the triggering times
reaches this threshold, UE
will be transferred from
CELL_FACH->CELL_DCH
.

Switch of
whether the other
UDrbc.fach Transferring 0: Off
channels can be N/A 0 0
Swch to 1: On
transferred to
CELL_FACH
CELL_FACH.

threshold for CELL_FACH
without enhanced UE DRX
to idle state shared by
Event 4B uplink and downlink when
Counter PCH is not supported. For
Threshold for the UE in CELL_FACH
UDrbc.fToI CELL_FACH state, if the UE or system
1..65535 N/A 2 2
dleThd without DRX does not support the PCH,
to Idle Shared the measured RLC buffer
by Uplink and payload of the uplink and
Downlink downlink is zero, and the
transferred from
CELL_FACH to idle state.
Event 4B This parameter indicates

UDrbc.fTo Counter the event 4B counter
1..65535 N/A 1 1
PchThd Threshold for threshold for CELL_FACH
CELL_FACH without Enhanced UE DRX

Recom
Name Range Value d
Value
without DRX to PCH shared by uplink
to PCH and downlink. For the UE
Shared by in CELL_FACH state, if the
Uplink and measured RLC buffer
Downlink payload of the uplink and
transferred from
CELL_FACH to PCH.

the time threshold of UE
staying in CELL_PCH or
URA_PCH for the
judgment of transferring
Time from CELL_PCH or
UDrbc.pch Threshold for URA_PCH to idle.
(1..65535
HoldTimeT CELL_PCH or If the time of UE having s 30 30
)s, step
hr URA_PCH to stayed in CELL_PCH or
1s
Idle URA_PCH exceeds the
parameter, UE will be
transferred from
CELL_PCH or URA_PCH
to Idle.
This parameter indicates 0: Not

whether Support
URA_PCH/CELL_PCH is 1: Only
Switch of supported or not. Support
UDrbc.pch URA_PCH/C Supported: The traffic can URA_PC
N/A 0 0
Swch ELL_PCH be carried on PCH channel H
Support when there is no data. 2: Only
Not supported: The traffic Support
cannot be carried on PCH CELL_P
channel when there is no CH

Recom
Name Range Value d
Value
data.

to CELL_FACH. For the
UE using CELL_DCH, if
the times of the measured
RLC buffer payload of the
downlink and the uplink is
Event 4B smaller than their event
Counter 4B‟s threshold separately,
UDrbc.dTo
Threshold for which exceeds the 1..65535 N/A 1 1
FachThd
Cell_Dch to threshold indicated by this
Cell_FACH parameter, the UE will be
transferred from
CELL_DCH to
CELL_FACH. For the
streaming service, it is
forbidden to be
transitioned to
CELL_FACH, i.e. this
parameter is invalid.

the offset times of event
Increment
4B0 for UE which is not
Times of
sensitive for battery
Event 4B0 for
consumption is transferred
UE Which is
to URA_PCH/CELL_PCH
UDrbc.delt not sensitive
or idle state based on the
aNumE4B for Battery 0..65535 N/A 0 0
traffic volume
0Thd Consumption
measurement. It is relative
Transferred to
to other UEs. For this kind
URA_PCH/C
of UE, the value of this
ELL_PCH or
parameter is larger, the
Idle state
transition for the UE to
URA_PCH or idle is more

Recom
Name Range Value d
Value
difficult.
4.1.2 Dynamic Radio Bearer Control Information Profile
Table 4-2 Parameter List (Dynamic Radio Bearer Control Information Profile)
Recom
Name Range Value d
Value
Drbc Strategy This parameter indicates

UDrbcProfi Configuration the DRBC strategy 0..255 N/A
le.profileId Index configuration index. 0 0
DRBC DRBC
Strateg Strateg
Drbc Strategy This parameter indicates
UDrbcProfi - N/A y for y for
Name the DRBC strategy name.
le.drbcStra not DPI not DPI
gyName Scene Scene
4.1.3 UMTS Logical Function Configuration
Table 4-3 Parameter List (UMTS Logical Function Configuration)
Recom
Name Range Value d
Value
bit0: Switch of bit0:0:Allo

bit0:0:A
URA_PCH/CELL_PCH for wed;1:No
llowed;
UE of Release 6. t Allowed.
URncFunct Global bit1:0:A
bit: Switch of bit1:0:Allo
ion.GRES Reserved N/A llowed;
URA_PCH/CELL_PCH for wed;1:No
PARA4 Parameter 4 BIT2:0:
UE of Release 7. t Allowed.
Allowed
BIT2: Switch of BIT2:0:All
.
URA_PCH/CELL_PCH for owed;1:N

Recom
Name Range Value d
Value
UE of Release 8 and After ot
Release 8. Allowed.
Wait Timer for This parameter indicates

Adjusting when uplink or downlink
Uplink and meets the requirements for 0..65535,
URncFunct
Downlink rate adjustment (reduce) step 1;
ion.dnUdR 100ms 30 30
Reconfigurati first, it is the waiting timer Unit:
ecfgTimer
on by One for waiting the opposite 100ms
Step direction reconfiguration by
Downward one step.

Wait Timer for
when uplink or downlink
Adjusting
meets the requirements for 0..65535,
URncFunct Uplink and
rate adjustment (increase), step 1;
ion.upUdR Downlink 100ms 30 30
the wait timer for waiting Unit:
ecfgTimer Reconfigurati
the opposite direction 100ms
on by One
reconfiguration by one
Step Upward
step.

whether non-emergency
CS service access to
Switch of Non
CELL_FACH on RRC
URncFunct Emergency
process is supported. If
ion.csRrcO CS Service 0: Off
this switch is "Off": RRC N/A 1: On 1: On
nFachSwc Access to 1: On
connection of the
h CELL_FACH
non-emergency CS
On RRC
service cannot be created
on FACH/RACH or
HS-DSCH/RACH.
0: Forced Forced Forced

Type of
This parameter indicates to to to
Transport
URncFunct the type of transport CELL_D CELL_ CELL_
Channel for
ion.initRrc channel and signaling rate CH and N/A DCH DCH
Initial RRC
OnDch for initial RRC connection Using and and
Connection
setup. DCH/DC Using Using
Setup
HLow DCH/D DCH/D

Recom
Name Range Value d
Value
Rate CH with CH with
Signalling 13.6k 13.6k
1: Forced Signalli Signalli
to ng ng
CELL_D
CH and
Using
DCH/DC
H with
13.6k
Signalling
2: Forced
to FACH
3: Not
Forced,
Using
DCH/DC
H with
DCH/DC
H Low
Rate
Signalling
on
Cell_DC
H State
4: Not
Forced,
Using
DCH/DC
H with
13.6k
Signalling
on
Cell_DC
H State
5: Forced
to

Recom
Name Range Value d
Value
CELL_D
CH and
Using
DCH/DC
H with
27.2k
Signalling
6: Not
Forced,
Using
DCH/DC
H with
27.2k
Signalling
on
Cell_DC
H State
7: Forced
to HSPA
8: Not
Forced,
Using
HSPA
Signalling
on
CELL_D
CH state

whether the switch to
Switch of URA_PCH/CELL_PCH is
URA_PCH/C allowed for the UE of
URncFunct 0:Not
ELL_PCH for Release 99 and Release 0: Not 0: Not
ion.r99R4P Allowed N/A
UE of Release 4."0" means the switching Allowed Allowed
chSwch 1:Allowed
99 and to URA_PCH/CELL_PCH
Release 4 is not allowed for the UE of
Release 99 and
Release,and "1" means to

Recom
Name Range Value d
Value
be allowed.
bit8:
0:preferre
Bit8 of the parameter
d to
function: Indicator for the 0:prefer 0:prefer
URncFunct Global Cell_DC
Channel Selection red to red to
ion.gRESP Reserved H N/A
Strategy of UE‟s Switching Cell_D Cell_D
ARA48 Parameter 48 1:preferre
from PCH to Other CH CH
d to
Channel.
Cell_FAC
H.
bit0:
0:Not
allow R5 0:Not 0:Not
URncFunct Global Bit0 of the parameter
UE to allow allow
ion.gRESP Reserved function: Whether to Allow N/A
PCH R5 UE R5 UE
ARA52 Parameter 52 R5 UE to PCH.
1:Allow to PCH to PCH
R5 UE to
PCH
bit1
0:
Release
the traffic
0: 0:
volume
Releas Releas
measure
e the e the
bit1=0/1:Release the traffic ment
traffic traffic
volume measurement before
URncFunct Global volume volume
before switching to PCH/ switching
ion.gRESP Reserved N/A measur measur
Note release the traffic to PCH
ARA52 Parameter 52 ement ement
volume measurement 1: Note
before before
before switching to PCH release switchi switchi
the traffic ng to ng to
volume PCH PCH
measure
ment
before
switching

Recom
Name Range Value d
Value
to PCH

the relative threshold of the
number of PCH users who
are barred from the PCH.
When the number of users
URncInfo. PCH Barred
on the control-plane board
PchBarred User Relative % 70 70
exceeds the product of the (0..100)%
UsrThd Threshold
system performance index
and the relative threshold,
all users on the
control-plane board are
barred from the PCH.
4.1.4 Logic RNC Configuration
Table 4-4 Parameter List (UMTS Logical Function Configuration)
Recom
Name Range Value d
Value
Used
DRBC DRBC
Dynamic
ULogicalR This parameter indicates Strateg Strateg
Radio Bearer
nc.refUDrb the Drbc strategy used by - N/A y for y for
Control
cProfile Non-DPI scene. not DPI not DPI
Information
Scene Scene
Profile
If the conversational class

C Traffic Rate
services (PS or CS) and
Threshold (1..384)
ULogicalR the
Used for kbps,
nc.cRateT Streaming/Interactive/Back kbps 32 32
Determining step 1
hrd ground class PS services
NRT PS Rate kbps
erupt simultaneously, and
Upper Limit
use DCH/DCH+DCH/DCH

Recom
Name Range Value d
Value
channel. This parameter is
used to determine the rate
threshold of the
conversational class
service of the rate
upper-limit of the I/B PS
services.
If the rate of the
conversational class
service is smaller than the
threshold, rate upper-limit
of the I/B PS service uses
DlPsRateLmtLowC/UlPsR
ateLmtLowC. If the rate of
the conversational class
service is larger than the
threshold, the rate
upper-limit of the I/B PS
service uses
DlPsRateLmtHighC/UlPsR
ateLmtHighC.

whether DCH rate
Switch for adjustment based on traffic
DCH Rate volume measurement is
ULogicalR
Adjustment supported. 0: Off
nc.dchAdj N/A 1: On 1: On
Based on If this switch is "Off", it is 1: On
RateSwch
Traffic Volume invalid for DCH rate
Measurement adjustment based on traffic
volume measurement.
Otherwise, it is valid.

Switch for DL
whether DL DCH rate
ULogicalR DCH Rate
adjustment for PS services 0: Off
nc.dlPwrD Adjustment N/A 1: On 1: On
based on D-TCP 1: On
asf Based on
measurement is
D-TCP
supported. If this switch is

Recom
Name Range Value d
Value
"Off", it is invalid for DCH
rate adjustment based on
D-TCP measurement;
otherwise, valid.
0: Switch
Off in UL
& Switch
Off in DL
1: Switch
3: 3:
This parameter is a switch Off in UL
Switch Switch
which indicates whether & Switch
ULogicalR On in On in
DRBC Method the dynamic radio bearer On in DL
nc.drbcSw N/A UL & UL &
Switch control algorithm is 2: Switch
ch Switch Switch
supported for the uplink On in UL
On in On in
and downlink services. & Switch
DL DL
Off in DL
3: Switch
On in UL
& Switch
On in DL
(8, 16,
ULogicalR 32, 64,
Initial Rate of the DL initial access rate
nc.initialRa 128, 144, kbps
DL DCH when DCH creating
teDl 256, 384)
services.
kbps 64 64
(8, 16,
ULogicalR 32, 64,
Initial Rate of the UL initial access rate
nc.initialRa 128, 144, kbps
UL DCH when DCH creating
teUl 256, 384)
services.
kbps 16 16
NRT PS This parameter indicates

(8, 16,
Traffic the I/B PS downlink rate
ULogicalR 32, 64,
Downlink Rate upper limit when
nc.dlPsRat 128, 144, kbps 64 64
Upper Limit Multi-RABs are
eLmtHighC 256, 384)
When High conversational (CS or
kbps
Rate C PS) +

Recom
Name Range Value d
Value
Traffic+ PS streaming/interactive/back
Traffic ground 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
in accordance with "C
Traffic Rate Threshold
Used for Determining NRT
PS Rate Upper Limit".

the I/B PS uplink rate
upper limit when
Multi-RABs are
conversational (CS or
PS) +
streaming/interactive/back
NRT PS ground PS and the rate of
Traffic Uplink the conversational service (8, 16,
ULogicalR Rate Upper is high, in which case, the 32, 64,
nc.ulPsRat Limit When sum of the uplink rates of 128, 144, kbps 64 64
eLmtHighC High Rate C all the I/B PS services 256, 384)
Traffic+ PS cannot exceed this kbps
Traffic threshold. Whether the

Recom
Name Range Value d
Value

the I/B PS downlink rate
upper limit when
Multi-RABs are
PS) +
NRT PS
ground PS and the rate of
Traffic
the conversational service (8, 16,
Downlink Rate
ULogicalR is low, in which case, the 32, 64,
Upper Limit
nc.dlPsRat sum of the downlink rates 128, 144, kbps 128 128
When Low
eLmtLowC of all the I/B PS services 256, 384)
Rate C
cannot exceed this kbps
Traffic+ PS
Traffic

the I/B PS uplink rate
upper limit when
Multi-RABs are
NRT PS
PS) +
Traffic Uplink (8, 16,
ULogicalR Rate Upper 32, 64,
ground PS and the rate of
nc.ulPsRat Limit When 128, 144, kbps 128 128
the conversational service
eLmtLowC Low Rate C 256, 384)
is low, in which case, the
Traffic+ PS kbps
sum of the uplink rates of
Traffic
all the I/B PS services
cannot exceed this

Recom
Name Range Value d
Value

the downlink maximum
rate threshold for I/B
service established on
CELL_FACH. When
Downlink
interactive/background
Maximum
service is set up initially, if (0..65535
ULogicalR Rate
the downlink maximum bit ) kbps, kbps 8 8
nc.rfach Threshold of
rate is lower than the step 1
I/B Service on
threshold, allocate FACH kbps
CELL_FACH
for the service. Otherwise,
allocate HS-DSCH/EDCH,
HS-DSCH/DCH or
DCH/DCH in accordance
with UE capability.

the uplink maximum rate
threshold for I/B service
established on
CELL_FACH. When
Uplink
interactive/background
Maximum
service is set up initially, if (0..65535
ULogicalR Rate
the uplink maximum bit ) kbps, kbps 8 8
nc.rrach Threshold of
rate is lower than the step 1
I/B Service on
threshold, allocate FACH kbps
RACH
for the service. Otherwise,
allocate HS-DSCH/EDCH,
HS-DSCH/DCH or
DCH/DCH in accordance
with UE capability.
ULogicalR Switch for UL This parameter indicates 0: Off N/A 1: On 1: On

Recom
Name Range Value d
Value
nc.ulPwrD DCH Rate whether UL DCH rate 1: On
asf Adjustment adjustment for PS services
Based on UE based on UE transmission
Transmission power is supported. If this
Power switch is "Off", it is invalid
for DCH rate adjustment
based on UE transmission
power.Otherwise, it is
valid.

ULogicalR the adjustment levels of
(8, 16,
nc.dlRateA the downlink DRBC rate. [8, 64, [8, 64,
Downlink Rate 32, 64,
djLev[MAX The downlink rate 128, 128,
Adjustment 128, 144, kbps
_NUM_RA adjustment range is limited 384] 384]
Level 256, 384)
TE_ADJU by this parameter. kbps kbps
kbps
ST] MAX_NUM_RATE_ADJU
ST=6.
1..MAX_
This parameter indicates NUM_RA
the number of DRBC TE_ADJ
ULogicalR Downlink Rate
downlink rate adjustment UST,
nc.dlRateA Adjustment N/A 4 4
levels, meaning the MAX_NU
djLevNum Level Number
number of available M_RATE
downlink DCH rate levels. _ADJUS
T=6

ULogicalR the adjustment levels of
(8, 16,
nc.ulRateA the uplink DRBC rate. The
Uplink Rate 32, 64, [16, 64, [16, 64,
djLev[MAX Uplink rate adjustment
Adjustment 128, 144, kbps 384] 384]
_NUM_RA range is limited by this
Level 256, 384) kbps kbps
TE_ADJU parameter.
kbps
ST] MAX_NUM_RATE_ADJU
ST=6.
ULogicalR Uplink Rate .This parameter indicates 1..MAX_

nc.ulRateA Adjustment the number of DRBC NUM_RA N/A 3 3
djLevNum Level Number uplink rate adjustment TE_ADJ

Recom
Name Range Value d
Value
levels, meaning the UST,
number of available uplink MAX_NU
DCH rate levels. M_RATE
_ADJUS
T=6

whether to replace 3.4
kbps signaling with 6.8
Switch of
ULogicalR kbps signaling during RRC
6.8kbps 0: Off
nc.dchSig6 connection setup when N/A 0: Off 0: Off
Signalling 1: On
8Swch signaling is carried on
Using on DCH
DCH or when RB has been
created when signaling is
carried on DPCH alone.

whether to punish the UE
that can‟t camp on PCH
state.If PunishUePchSwch
is"1:on", when UE is
Switch of switched to PCH from
ULogicalR whether to other state, count the time
0:off
nc.Punish Punish the UE that UE is on PCH state. If
N/A 1 1
UePchSwc that can't UE is switched to other
1:on
h Camp on PCH channel when the time is
state less than 1 second, UE will
be not allowed to switch to
PCH state again during the
call period to avoid the
ping-pong between PCH
and other state.
Switch of the This parameter controls

ULogicalR Channel whether the channel
nc. Selection selection strategy is 0:Off
N/A 0 1
PchToOthe Strategy determined by the traffic 1:On
rTVISw whether to be volume indicator IE when a
decided by UE transits from PCH to

Recom
Name Range Value d
Value
Traffic volume another channel.
indicator IE of
UE's
Switching
from PCH to
Other
Channel
4.1.5 UTRAN Cell
Table 4-5 Parameter List (UTRAN Cell)
Recom
Name Range Value d
Value
Maximum
Allowable
This parameter indicates (8, 16,
Rate on DCH
UUtranCell the maximum rate 32, 64,
to be 384 384
FDD.MaxR threshold that DCH can be 128, 144, kbps
Increased to kbps kbps
ateMD increased to when UE is in 256, 384)
When UE is in
the macro diversity. kbps
Macro
Diversity

Maximum Bit (8, 16,
the maximum bit rate of a
UCelInfoF Rate on DL 32, 64,
real-time PS domain RAB 384 384
DD.RtMax DCH for RT 128, 144, kbps
in the serving cell that can kbps kbps
DlRateDch PS RAB in 256, 384)
be allowed on the DL
Serving Cell kbps
DCH.
UUtranCell Used Traffic

This parameter is the DN
FDD.refUT Volume
(Distinguish Name) of - N/A - -
rvMeasPro Measurement
UTrvMeasProfile.
file Profile
UCelInfoF Cell Level This parameter is a switch 0:Off N/A 0: Off 0: Off

Recom
Name Range Value d
Value
DD.PchCel PCH Switch to indicate whether 1:On
lSwch URA_PCH/CELL_PCH is
supported or not in the cell.
On: UE is allowed to
transfer to PCH when
there is no data to transmit
in the cell.
Off: UE is not allowed to
transfer to PCH when
there is no data to transmit
in the cell.

Maximum Bit (8, 16,
the maximum bit rate of a
UCelInfoF Rate on UL 32, 64,
non-real-time PS domain 384 384
DD.RtMax DCH for RT 128, 144, kbps
RAB in the serving cell that kbps kbps
UlRateDch PS RAB in 256, 384)
can be allowed on the UL
Serving Cell kbps
DCH.

Maximum Bit (8, 16,
UUtranCell the maximum bit rate of a
Rate on UL 32, 64,
FDD.NrtMa non-real-time PS domain 384 384
DCH for NRT 128, 144, kbps
xUlRateDc RAB in the serving cell that kbps kbps
PS RAB in 256, 384)
h can be allowed on the UL
Serving Cell kbps
DCH.

Maximum Bit (8, 16,
UUtranCell the maximum bit rate of a
Rate on DL 32, 64,
FDD.NrtMa non-real-time PS domain 384 384
DCH for NRT 128, 144, kbps
xDlRateDc RAB in the serving cell that kbps kbps
PS RAB in 256, 384)
h can be allowed on the DL
Serving Cell kbps
DCH.
0:CS No
UUtranCell CS Traffic This parameter indicates
Preferred
FDD.csTra Preferred CS traffic is preferred in N/A 1 1
1:CS
fPrefInd Indicator the cell.
Preferred
UUtranCell R99 PS This parameter indicates 0:R99 PS

FDD.r99Ps Traffic R99 PS traffic is preferred No N/A 1 1
TrafPrefInd Preferred in the cell. Preferred

Recom
Name Range Value d
Value
Indicator 1:R99 PS
Preferred
0: 27.2
kbps
1: 13.6
kbps
Maximum Bit
UCelInfoF This parameter indicates 2: 6.8 0: 0:
Rate allowed
DD.CellSig the maximum signaling bit kbps N/A 27.2 27.2
for Signalling
MaxBR rate allowed in a cell. 3: 3.4 kbps kbps
in Cell
kbps
4:CELL_
FACH
Forced
UUtranCell Used UE
This parameter is the DN
FDD.refUU Internal 0..65535,
(Distinguish Name) of N/A 0 0
eIntMeasP Measurement step 1
UUeIntMeasProfile.
rofile Profile
0:
Second
This parameter is used to Admissio
control whether the UE is n on
attempted on the FACH is
UCelInfoF Bit0 of Cell CELL_FACH when it is allowed;
DD.CresPa Reserved denied by CELL_DCH 1: N/A 0 1
ra7 Parameter 7 during the RRC connection Second
establishment stage, and Admissio
the establishment cause is n on
PS service. FACH is
not
allowed

4.1.6 External UTRAN Cell
Table 4-6 Parameter List (UTRAN Cell)
Recom
Name Range Value d
Value
Maximum Bit
UExternal This parameter indicates (8, 16,
Rate on DL
UtranCellF the maximum bit rate on 32, 64,
DCH for NRT 384 384
DD.nrtMax DL DCH allowed in 128, 144, kbps
PS RAB in kbps kbps
DlRateDch External UTRAN cell for an 256, 384)
External
D NRT PS domain RAB. kbps
UTRAN Cell
Maximum Bit
UExternal This parameter indicates (8, 16,
Rate on UL
UtranCellF the maximum bit rate on 32, 64,
DCH for NRT 384 384
DD.nrtMax UL DCH allowed in 128, 144, kbps
PS RAB in kbps kbps
UlRateDch External UTRAN cell for an 256, 384)
External
D NRT PS domain RAB. kbps
UTRAN Cell
Maximum Bit
UExternal Rate on DL
the maximum bit rate on 32, 64,
UtranCellF DCH for RT 384 384
DL DCH allowed in 128, 144, kbps
DD.rtMaxD PS RAB in kbps kbps
External UTRAN Cell for 256, 384)
lRateDchD External
an RT PS domain RAB. kbps
UTRAN Cell
Maximum Bit
UExternal Rate on UL
the maximum bit rate on 32, 64,
UtranCellF DCH for RT 384 384
UL DCH allowed in 128, 144, kbps
DD.rtMaxU PS RAB in kbps kbps
External UTRAN Cell for 256, 384)
lRateDchD External
an RT PS domain RAB. kbps
UTRAN Cell

4.1.7 Iur Link
Table 4-7 Parameter List (Iur Link)
Recom
Name Range Value d
Value
0:Not
Support
This parameter indicates PS(0 1: 1:
UIurLink.R
Whether the adjacent RNC feature kbps /0 Support Support
NCFEATS
Support PS switch,0 means not kbps) N/A PS(0 PS(0
WITCHBIT
(0kbps/0kbps) support PS(0 kbps /0 kbps) 1:Support kbps /0 kbps /0
18
and 1 means support. PS(0 kbps) kbps)
kbps /0
kbps)
4.1.8 Parameters Related to the Traffic Volume Measurement
4.1.8.1 Traffic Volume Measurement Profile
Table 4-8 Parameter List (Iur Link)
Recom
Parameter Parameter Default mende
GUI Name Value Range Unit
Name Description Value d
Value
This parameter
UTrvMeas
indicates traffic
Profile.profi profileId Profile Id 0..9 N/A 0
volume measurement
leId
profile identity

4.1.8.2 Parameters Related to the UE Event Traffic Measurement on the DCH
Table 4-9 Parameters List (Parameters Related to the UE Event Traffic Measurement
on the DCH)
Recom
Name Range Value d
Value

the average time window
(20,
Time Interval for the measurement,
UDchEvUe 40, ..,
for Taking an which is only valid when
Trv.averag 260)ms, ms 100ms 100ms
Average or a the measurement quantity
eTime step
Variance is Average RLC buffer
20ms
payload or Variance of
RLC buffer payload.

the event identity of the
traffic volume
measurement performed
UE Traffic
UDchEvUe by UE.
Volume
Trv.MeaEv (4a, 4b) N/A [4a, 4b] [4a, 4b]
Measurement
tId MAX_UE_TRV_MEAS_EV
Event Identity
ENT is the maximum
number of UE traffic
volume measurement
event, which equals to 2.
1..MAX_
UE_TRV
_MEAS_
Event Number
UDchEvUe This parameter indicates EVENT
of UE Traffic
Trv.measE event number of UE traffic where N/A 2 2
Volume
vtNum volume measurement. MAX_UE
Measurement
_TRV_M
EAS_EV
ENT=2
UDchEvUe This parameter indicates 1: RLC

Measurement
Trv.measQ the measurement object of buffer N/A RLC RLC
Quantity
uantity the traffic volume payload, buffer buffer

Recom
Name Range Value d
Value
measurement that UE 2: payload payload
performs.For the Average
definitions of RLC buffer RLC
payload, Average RLC buffer
buffer payload, and payload
Variance of RLC buffer 3:
payload, please refer to Variance
the 3GPP TS25.321 of RLC
protocol. buffer
payload

the RLC mode that is used
by the traffic volume
measurement report. If the
AM mode is used, when
RNC receives the SDU
0:
with wrong SDU labels (not
Acknowle
continuous), it can ask the
dged
UE to transmit the SDU
Measurement Mode Acknow Acknow
UDchEvUe again. If the UM mode is
Report RLC ledged ledged
Trv.measR used, the retransmission is N/A
Transfer 1: Mode Mode
ptTrMod not needed. In general, the
Mode Unackno RLC RLC
important measurements
wledged
must use the AM mode to
Mode
report the measurement
RLC
result. Otherwise, only the
UM mode is available
(reduce the data traffic for
the measurement report
and improve the system
capacity).
This parameter indicates (250,

the pending time after 500,
UDchEvUe [2000, [2000,
Pending Time triggered. This timer is 1000,
Trv.pendin ms 4000]m 4000]m
After Trigger started in the UE when a 2000,
gTime s s
measurement report has 4000,
been triggered by a given 8000,

Recom
Name Range Value d
Value
event. The UE is then 16000)
forbidden to send new ms
measurement reports
triggered by the same
event during this time
period, instead the UE
waits until the timer
expires.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
measurement event, which
equals to 2.

Average of
UDchEvUe whether the Average of
RLC Buffer 0: False 0: 0:
Trv.rptRlcA RLC Buffer Payload is N/A
Payload for 1: True False False
veInd reported in the traffic
Each RB
volume measurement.

UDchEvUe RLC Buffer whether RLC Buffer
0: False
Trv.rptRlcB Payload for Payload is reported in the N/A 1: True 1: True
1: True
ufInd Each RB traffic volume
measurement.

Variance of
UDchEvUe whether Variance of RLC
Trv.rptRlcV Buffer Payload is reported N/A
arInd in the traffic volume
Each RB
measurement.

the reporting threshold of 32, 64,
Traffic Volume
event 4A and 4B for traffic 128, 256,
UDchEvUe Threshold of
volume measurement on 512, [64, 8] [64, 8]
Trv.rptThre Event 4A/4B bytes
DCH whose rate is 8 kbps. 1024, 2K, bytes bytes
s0 for DCH
If the traffic volume 3K, 4K,
(8kbps)
becomes larger than the 6K, 8K,
threshold of event 4A, a 12K, 16K,

Recom
Name Range Value d
Value
report of 4A event will be 24K, 32K,
triggered; and if the traffic 48K ,
volume becomes smaller 64K, 96K,
than the threshold of event 128K,
4B, a report of 4B event 192K,
will be triggered. 256K,
MAX_UE_TRV_MEAS_EV 384K,
ENT is the maximum 512K,
number of UE traffic 768K)
volume measurement bytes

(8, 16,
the reporting threshold of
32, 64,
event 4A and 4B for traffic
128, 256,
volume measurement on
512,
DCH whose rate is 16
1024, 2K,
kbps If the traffic volume
3K, 4K,
becomes larger than the
6K, 8K,
Traffic Volume threshold of event 4A, a
12K, 16K,
UDchEvUe Threshold of report of 4A event will be
24K, 32K, [128, 8] [128, 8]
Trv.rptThre Event 4A/4B triggered; and if the traffic bytes
48K , bytes bytes
s1 for DCH volume becomes smaller
64K, 96K,
(16kbps) than the threshold of event
128K,
4B, a report of 4B event
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

Traffic Volume the reporting threshold of 32, 64,
UDchEvUe Threshold of event 4A and 4B for traffic 128, 256,
[256, 8] [256, 8]
Trv.rptThre Event 4A/4B volume measurement on 512, bytes
bytes bytes
s2 for DCH DCH whose rate is 32 1024, 2K,
(32kbps) kbps. If the traffic volume 3K, 4K,

Recom
Name Range Value d
Value

(8, 16,
32, 64,
128, 256,
512,
1024, 2K,
kbps. If the traffic volume
3K, 4K,
6K, 8K,
12K, 16K,
UDchEvUe Threshold of report of 4A event will be [512, [512,
24K, 32K,
Trv.rptThre Event 4A/4B triggered; and if the traffic bytes 32] 32]
48K ,
s3 for DCH volume becomes smaller bytes bytes
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

Traffic Volume
UDchEvUe Threshold of
event 4A and 4B for traffic 128, 256, [1k, 32] [1k, 32]
volume measurement on 512, bytes bytes
s4 for DCH
DCH whose rate is 128 1024, 2K,
(128kbps)
kbps. If the traffic volume 3K, 4K,

Recom
Name Range Value d
Value

(8, 16,
32, 64,
128, 256,
512,
1024, 2K,
3K, 4K,
6K, 8K,
12K, 16K,
UDchEvUe Threshold of report of 4A event will be
24K, 32K, [2k, 64] [2k, 64]
Trv.rptThre Event 4A/4B triggered; and if the traffic bytes
48K , bytes bytes
s5 for DCH volume becomes smaller
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

Traffic Volume
UDchEvUe the reporting threshold of 32, 64, [8k, [8k,
Threshold of
Trv.rptThre event 4A and 4B for traffic 128, 256, bytes 128] 128]
Event 4A/4B
s6 volume measurement on 512, bytes bytes
for DCH

Recom
Name Range Value d
Value
(384kbps) kbps. If the traffic volume 3K, 4K,

the time difference from
the event being detected to
the event being reported.
Only when the event is
detected and still meets all
requirements of event
(0, 10,
triggering within the
20, 40,
triggering duration, the
60, 80,
event can be triggered and
100, 120,
UDchEvUe reported. [320, [320,
Time to 160, 200,
Trv.trigTim The larger which equals to, ms 2560]m 2560]m
Trigger 240, 320,
e the stricter the judgment is s s
640,
for the event to be
1280,
triggered. The parameter
2560,
must be set in accordance
5000) ms
with the actual
requirements. If it is too
large, the quality of calls
may be influenced.
MAX_UE_TRV_MEAS_EV
ENT is the maximum

Recom
Name Range Value d
Value
volume measurement

the configuration index of
the UE traffic volume
measurement. There are
UE Traffic different sets of
UDchEvUe Volume measurement
Trv.ueTrv Measurement configuration values in 0..65535 N/A
MCfgNo Configuration accordance with different
Index measurement purposes
and measurement
volumes. This parameter
can be used to index
different configurations. 0 0
4.1.8.3 Parameters Related to the User Plane Event Traffic Measurement on the
DCH
Table 4-10 Parameters List (Parameters Related to the User Plane Event Traffic
Measurement on the DCH)
Recom
Name Range Value d
Value

(20,
UDchEvUp 40, ..,
eTime step
20ms
RLC buffer payload.
UDchEvUp UE Traffic This parameter indicates (4a, 4b) N/A [4a, 4b] [4a, 4b]

Recom
Name Range Value d
Value
Trv.MeaEv Volume the event identity of the
tId Measurement traffic volume
Event Identity measurement performed
by UE.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
volume measurement
1..MAX_
UE_TRV
_MEAS_
Event Number
UDchEvUp This parameter indicates EVENT
of UE Traffic
Trv.measE event number of UE traffic where N/A 2 2
Volume
vtNum volume measurement. MAX_UE
Measurement
_TRV_M
EAS_EV
ENT=2
1: RLC
buffer
the measurement object of
payload,
the traffic volume
2:
measurement that RNC
Average
user plane performs.For Averag Averag
UDchEvUp RLC
Measurement the definitions of RLC e RLC e RLC
Trv.measQ buffer N/A
Quantity buffer payload, Average buffer buffer
uantity payload
RLC buffer payload, and payload payload
3:
Variance of RLC buffer
Variance
payload, please refer to
of RLC
the 3GPP TS25.321
buffer
protocol.
payload
Measurement This parameter indicates 0: Acknow Acknow

UDchEvUp
Report the RLC mode that is used Acknowle ledged ledged
Trv.measR N/A
Transfer by the traffic volume dged Mode Mode
ptTrMod
Mode measurement report. If the Mode RLC RLC

Recom
Name Range Value d
Value
AM mode is used, when RLC
RNC receives the SDU 1:
with wrong SDU labels (not Unackno
continuous), it can ask the wledged
UE to transmit the SDU Mode
again. If the UM mode is RLC
used, the retransmission is
not needed. In general, the
capacity).

the pending time after
trigger. This timer is
started in the UE when a
measurement report has
been triggered by a given
(250,
event. The UE is then
500,
forbidden to send new
1000,
UDchEvUp measurement reports [2000, [2000,
Pending Time 2000,
Trv.pendin triggered by the same ms 4000]m 4000]m
After Trigger 4000,
gTime event during this time s s
8000,
16000)
ms
expires.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
equals to 2.

Recom
Name Range Value d
Value

Average of
UDchEvUp whether the Average of
RLC Buffer 0: False
Trv.rptRlcA RLC Buffer Payload is N/A 1: True 1: True
Payload for 1: True
veInd reported in the traffic
Each RB
volume measurement.

UDchEvUp RLC Buffer whether RLC Buffer
0: False
Trv.rptRlcB Payload for Payload is reported in the N/A 1: True 1: True
1: True
ufInd Each RB traffic volume
measurement.

Variance of
UDchEvUp whether Variance of RLC
Trv.rptRlcV Buffer Payload is reported N/A
arInd in the traffic volume
Each RB
measurement.

(8, 16,
32, 64,
128, 256,
512,
DCH whose rate is 8 kbps.
1024, 2K,
If the traffic volume
3K, 4K,
6K, 8K,
12K, 16K,
UDchEvUp Threshold of report of 4A event will be [128, [128,
24K, 32K,
48K ,
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes
UDchEvUp Traffic Volume This parameter indicates (8, 16, [128, 8] [128, 8]
bytes
Trv.rptThre Threshold of the reporting threshold of 32, 64, bytes bytes

Recom
Name Range Value d
Value
s1 Event 4A/4B event 4A and 4B for traffic 128, 256,
for DCH volume measurement on 512,
(16kbps) DCH whose rate is 16 1024, 2K,
kbps If the traffic volume 3K, 4K,

(8, 16,
32, 64,
128, 256,
512,
1024, 2K,
3K, 4K,
6K, 8K,
12K, 16K,
24K, 32K,
48K ,
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

Recom
Name Range Value d
Value

(8, 16,
32, 64,
128, 256,
512,
1024, 2K,
3K, 4K,
6K, 8K,
12K, 16K,
24K, 32K,
48K ,
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

volume measurement on 512,
Traffic Volume
UDchEvUp Threshold of
report of 4A event will be 24K, 32K, [2k, 64] [2k, 64]
triggered; and if the traffic 48K , bytes bytes
s4 for DCH
(128kbps)

Recom
Name Range Value d
Value

(8, 16,
32, 64,
128, 256,
512,
1024, 2K,
3K, 4K,
6K, 8K,
12K, 16K,
UDchEvUp Threshold of report of 4A event will be [2k, [2k,
24K, 32K,
48K ,
64K, 96K,
128K,
192K,
will be triggered.
256K,
MAX_UE_TRV_MEAS_EV
384K,
ENT is the maximum
512K,
768K)
volume measurement
bytes

Traffic Volume becomes larger than the 6K, 8K,
UDchEvUp Threshold of threshold of event 4A, a 12K, 16K, [8k, [8k,
Trv.rptThre Event 4A/4B report of 4A event will be 24K, 32K, bytes 128] 128]
s6 for DCH triggered; and if the traffic 48K , bytes bytes
(384kbps) volume becomes smaller 64K, 96K,

Recom
Name Range Value d
Value

(0, 10,
20, 40,
60, 80,
reported.
100, 120,
UDchEvUp The larger which equals to, [320, [320,
Time to 160, 200,
Trv.trigTim the stricter the judgment is ms 2560]m 2560]m
Trigger 240, 320,
e for the event to be s s
640,
1280,
2560,
with the actual
5000) ms
may be influenced.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
volume measurement

UE Traffic
UDchEvUp Volume
different sets of
Trv.ueTrv Measurement 0..65535 N/A
measurement
MCfgNo Configuration
configuration values in
Index
accordance with different
measurement purposes
and measurement 0 0

Recom
Name Range Value d
Value
different configurations.
4.1.8.4 Parameters Related to the UE Periodic Traffic Measurement on the DCH
Table 4-11 Parameters List (Parameters Related to the UE Periodic Traffic

Measurement on the DCH)
Recom
Name Range Value d
Value

(20,
UDchPrdU 40, ..,
eTrv.avera 260)ms, ms 20ms 20ms
geTime step
20ms
RLC buffer payload.
1: RLC
buffer
payload,
the traffic volume
2:
measurement that UE
Average
performs.For the
UDchPrdU RLC
Measurement definitions of RLC buffer RLC RLC
eTrv.meas buffer N/A
Quantity payload, Average RLC buffer buffer
Quantity payload
buffer payload, and payload payload
3:
Variance
of RLC
the 3GPP TS25.321
buffer
protocol.
payload
UDchPrdU Measurement This parameter indicates 0: N/A AcknowAcknow

Recom
Name Range Value d
Value
eTrv.meas Report the RLC mode that is used Acknowle ledged ledged
RptTrMod Transfer by the traffic volume dged Mode Mode
capacity).
Amount of 1, 2, 4, 8,
UDchPrdU This parameter indicates
Reporting in 16, 32,
eTrv.prdRp the times for reporting N/A Infinity Infinity
Period Report 64,
tAmount periodic reports.
Criteria Infinity
(250,
500,
1000,
2000,
3000,
Reporting
UDchPrdU This parameter indicates 4000,
Interval in 4000m 4000m
eTrv.prdRp the UE reporting interval in 6000, ms
Period Report s s
tInterval periodic reporting mode. 8000,
Criteria
12000,
16000,
20000,
24000,
28000,

Recom
Name Range Value d
Value
32000,
64000)m
s

Average of
UDchPrdU whether the Average of
eTrv.rptRlc RLC Buffer Payload is N/A
AveInd reported in the traffic
Each RB
volume measurement.

UDchPrdU RLC Buffer whether RLC Buffer
0: False
eTrv.rptRlc Payload for Payload is reported in the N/A 1: True 1: True
1: True
BufInd Each RB traffic volume
measurement.

Variance of
UDchPrdU whether Variance of RLC
eTrv.rptRlc Buffer Payload is reported N/A
VarInd in the traffic volume
Each RB
measurement.

UDchPrdU Volume measurement
eTrv.ueTrv Measurement configuration values in 0..65535 N/A 0 0
MCfgNo Configuration accordance with different
and measurement

4.1.8.5 Parameters Related to the User Plane Traffic Measurement on the FACH
Table 4-12 Parameters List (Parameters Related to the User Plane Traffic
Measurement on the FACH)
Recom
Name Range Value d
Value

trigger. This timer is
been triggered by a given
(250,
event. The UE is then
500,
forbidden to send new
1000,
UFachEvU measurement reports [4000, [4000,
Pending Time 2000,
pTrv.pendi triggered by the same ms 1000] 1000]
After Trigger 4000,
ngTime event during this time ms ms
8000,
16000)
ms
expires.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
equals to 2.

Average of
UFachEvU whether the Average of
RLC Buffer 0: False
pTrv.rptRlc RLC Buffer Payload is N/A 1: True 1: True
Payload for 1: True
AveInd reported in the traffic
Each RB
volume measurement.

UFachEvU RLC Buffer whether RLC Buffer
0: False
pTrv.rptRlc Payload for Payload is reported in the N/A 1: True 1: True
1: True
BufInd Each RB traffic volume
measurement.
UFachEvU Variance of This parameter indicates 0: False 0: 0:

N/A
pTrv.rptRlc RLC Buffer whether Variance of RLC 1: True False False

Recom
Name Range Value d
Value
VarInd Payload for Buffer Payload is reported
Each RB in the traffic volume
measurement.

FACH channel. If the traffic 1024, 2K,
volume becomes larger 3K, 4K,
than the threshold of event 6K, 8K,
Traffic Volume
4A, a report of 4A event 12K, 16K,
UFachEvU Threshold of
will be triggered; and if the 24K, 32K, [256, 8] [256, 8]
pTrv.rptThr Event 4A/4B bytes
traffic volume becomes 48K , bytes bytes
es for FACH
smaller than the threshold 64K, 96K,
Channel
of event 4B, a report of 4B 128K,
event will be triggered. 192K,
number of UE traffic 512K,
volume measurement 768K)
event, which equals to 2. bytes

the time difference
between having detected
the event generation and (0, 10,
reporting the event. Only 20, 40,
when the event generation 60, 80,
is detected and still meets 100, 120,
UFachEvU [80, [80,
Time to all requirements of event 160, 200,
pTrv.trigTi ms 2560]m 2560]m
Trigger triggering after Time to 240, 320,
me s s
trigger, the event can be 640,
triggered and reported. 1280,
The larger which equals to, 2560,
the stricter the judgment is 5000) ms
for the event to be
should be set in

Recom
Name Range Value d
Value
accordance with the actual
requirements. Sometimes,
if it is set too large, the
quality of calls may
decrease.
Where
MAX_UE_TRV_MEAS_EV
ENT is the maximum
volume measurement
reported.
The larger which equals to,
the stricter the judgment is
for the event to be
with the actual
may be influenced.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
volume measurement
UFachEvU UE Traffic This parameter indicates 0..65535 N/A 0 0

Recom
Name Range Value d
Value
pTrv.ueTrv Volume the configuration index of
MCfgNo Measurement the UE traffic volume
Configuration measurement. There are
Index different sets of
measurement
and measurement

(20,
UFachEvU 40, ..,
pTrv.avera 260)ms, ms 100ms 100ms
geTime step
20ms
RLC buffer payload.

traffic volume
UE Traffic
UFachEvU by UE.
Volume
pTrv.meaE (4a, 4b) N/A [4a, 4b] [4a, 4b]
Measurement
vtId MAX_UE_TRV_MEAS_EV
Event Identity
ENT is the maximum
volume measurement
1..MAX_
Event Number This parameter indicates
UFachEvU UE_TRV
of UE Traffic event number of UE traffic
pTrv.meas _MEAS_ N/A 2 2
Volume volume measurement in
EvtNum EVENT
Measurement RNC user plane.
where

Recom
Name Range Value d
Value
MAX_UE
_TRV_M
EAS_EV
ENT=2
1: RLC
buffer
payload,
the traffic volume
2:
measurement that RNC
Average
user plane performs.For Averag Averag
UFachEvU RLC
Measurement the definitions of RLC e RLC e RLC
pTrv.meas buffer N/A
Quantity buffer payload, Average buffer buffer
Quantity payload
RLC buffer payload, and payload payload
3:
Variance
of RLC
the 3GPP TS25.321
buffer
protocol.
payload

with wrong SDU labels (not Acknowle
continuous), it can ask the dged
Measurement UE to transmit the SDU Mode Acknow Acknow
UFachEvU
Report again. If the UM mode is RLC ledged ledged
pTrv.meas N/A
Transfer used, the retransmission is 1: Mode Mode
RptTrMod
Mode not needed. In general, the Unackno RLC RLC
important measurements wledged
must use the AM mode to Mode
report the measurement RLC

Recom
Name Range Value d
Value
capacity).
4.1.8.6 Parameters Related to the UE Traffic Measurement on the RACH
Table 4-13 Parameters List (Parameters Related to the UE Traffic Measurement on the
RACH)
Recom
Name Range Value d
Value

(20,
URachEvt 40, ..,
UeTrv.aver 260)ms, ms 100 100
ageTime step
20ms
RLC buffer payload.

traffic volume
UE Traffic
URachEvt by UE.
Volume
UeTrv.Mea (4a, 4b) N/A [4a, 4b] [4a, 4b]
Measurement
EvtId MAX_UE_TRV_MEAS_EV
Event Identity
ENT is the maximum
volume measurement
1..MAX_
Event Number
URachEvt This parameter indicates UE_TRV
of UE Traffic
UeTrv.mea event number of UE traffic _MEAS_ N/A 2 2
Volume
sEvtNum volume measurement. EVENT
Measurement
where

Recom
Name Range Value d
Value
MAX_UE
_TRV_M
EAS_EV
ENT=2
1: RLC
buffer
payload,
the traffic volume
2:
measurement that UE
Average
performs.For the
URachEvt RLC
Measurement definitions of RLC buffer RLC RLC
UeTrv.mea buffer N/A
Quantity payload, Average RLC buffer buffer
sQuantity payload
buffer payload, and payload payload
3:
Variance
of RLC
the 3GPP TS25.321
buffer
protocol.
payload

with wrong SDU labels (not Acknowle
continuous), it can ask the dged
Measurement UE to transmit the SDU Mode Acknow Acknow
URachEvt
Report again. If the UM mode is RLC ledged ledged
UeTrv.mea N/A
Transfer used, the retransmission is 1: Mode Mode
sRptTrMod
Mode not needed. In general, the Unackno RLC RLC
important measurements wledged
must use the AM mode to Mode
report the measurement RLC

Recom
Name Range Value d
Value
capacity).

triggered. This timer is
been triggered by a given (250,
event. The UE is forbidden 500,
to send new measurement 1000,
URachEvt
Pending Time reports triggered by the 2000, [4000, [4000,
UeTrv.pen ms
After Trigger same event during this 4000, 1000] 1000]
dingTime
time period, instead the UE 8000, ms ms
waits until the timer 16000)
expires. ms
MAX_UE_TRV_MEAS_EV
ENT is the maximum
equals to 2.

Average of
URachEvt whether the Average of
UeTrv.rptR RLC Buffer Payload is N/A
lcAveInd reported in the traffic
Each RB
volume measurement.

URachEvt RLC Buffer whether RLC Buffer
0: False
UeTrv.rptR Payload for Payload is reported in the N/A 1: True 1: True
1: True
lcBufInd Each RB traffic volume
measurement.

Variance of
URachEvt whether Variance of RLC
UeTrv.rptR Buffer Payload is reported N/A
lcVarInd in the traffic volume
Each RB
measurement.
URachEvt Traffic Volume This parameter indicates (8, 16, [256, 8] [256, 8]
bytes
UeTrv.rptT Threshold of the reporting threshold of 32, 64, bytes bytes

Recom
Name Range Value d
Value
hres Event 4A/4B event 4A and 4B for traffic 128, 256,
for RACH volume measurement on 512,
Channel RACH channel. If the 1024, 2K,
traffic volume becomes 3K, 4K,
larger than the threshold of 6K, 8K,
event 4A, a report of 4A 12K, 16K,
event will be triggered; and 24K, 32K,
if the traffic volume 48K ,
becomes smaller than the 64K, 96K,
threshold of event 4B, a 128K,
report of 4B event will be 192K,
triggered. 256K,

detected and still meets all (0, 10,
requirements of event 20, 40,
triggering within the 60, 80,
triggering duration, the 100, 120,
URachEvt [80, [80,
Time to event can be triggered and 160, 200,
UeTrv.trigT ms 2560]m 2560]m
Trigger reported. The larger which 240, 320,
ime s s
equals to, the stricter the 640,
judgment is for the event to 1280,
be triggered. The 2560,
parameter must be set in 5000) ms
accordance with the actual
may be influenced.
MAX_UE_TRV_MEAS_EV

Recom
Name Range Value d
Value
ENT is the maximum
volume measurement
This parameter indicates The The

whether Tx interruption default default
after trigger is configured value value
Tx Interruption
URachEvt or not. for for
After Trigger 0: False
UeTrv.txInt MAX_UE_TRV_MEAS_EV N/A event event
Configuration 1: True
erCfgPre ENT is the maximum [4a 4b] [4a 4b]
Tag
number of UE traffic is is
volume measurement [False, [False,
event, which equals to 2. False] False]

the time of prohibiting
transmitting data on
RACH. Only when traffic
volume measurement is on
RACH, and the
The The
corresponding (250,
default default
TxInterCfgPre is "1:True" , 500,
value value
this parameter can be 1000,
URachEvt for for
Tx Interruption configured and its 2000,
UeTrv.txInt ms event event
After Trigger configuration is optional. If 4000,
erruption [4a 4b] [4a 4b]
the transport channel to be 8000,
is is
measured is DCH, this 16000)
[250, [250,
parameter doesn't need to ms
250]ms 250]ms
be configured.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
volume measurement
URachEvt UE Traffic This parameter indicates

0..65535 N/A 0 0
UeTrv.ueTr Volume the configuration index of

Recom
Name Range Value d
Value
vMCfgNo Measurement the UE traffic volume
Configuration measurement. There are
Index different sets of
measurement
and measurement
4.1.8.7 Parameters Related to the UE Periodic Traffic Measurement on the RACH
Table 4-14 Parameters List (Parameters Related to the UE Periodic Traffic

Measurement on the RACH)
Recom
Name Range Value d
Value
1: RLC
buffer
payload,
the traffic volume
2:
measurement that UE
Average
performs.For the
URachPrd RLC RLC RLC
Measurement definitions of RLC buffer
UeTrv.mea buffer N/A buffer buffer
Quantity payload, Average RLC
sQuantity payload payload payload
buffer payload, and
3:
Variance
of RLC
the 3GPP TS25.321
buffer
protocol.
payload
URachPrd Measurement This parameter indicates 0: Acknow Acknow

N/A
UeTrv.mea Report the RLC mode that is used Acknowle ledged ledged

Recom
Name Range Value d
Value
sRptTrMod Transfer by the traffic volume dged Mode Mode
capacity).
Amount of 1, 2, 4, 8,
URachPrd This parameter indicates
Reporting in 16, 32,
UeTrv.prd the times for reporting N/A Infinity Infinity
Period Report 64,
RptAmount periodic reports.
Criteria Infinity
(250,
500,
1000,
2000,
3000,
Reporting 4000,
URachPrd This parameter indicates
Interval in 6000, 8000m 8000m
UeTrv.prd the UE reporting interval in ms
Period Report 8000, s s
RptInterval periodic reporting mode.
Criteria 12000,
16000,
20000,
24000,
28000,
32000,

Recom
Name Range Value d
Value
64000)m
s

Average of
URachPrd whether the Average of
UeTrv.rptR RLC Buffer Payload is N/A
lcAveInd reported in the traffic
Each RB
volume measurement.

URachPrd RLC Buffer whether RLC Buffer
0: False
UeTrv.rptR Payload for Payload is reported in the N/A 1: True 1: True
1: True
lcBufInd Each RB traffic volume
measurement.

Variance of
URachPrd whether Variance of RLC
UeTrv.rptR Buffer Payload is reported N/A
lcVarInd in the traffic volume
Each RB
measurement.

URachPrd Volume measurement
UeTrv.ueTr Measurement configuration values in 0..65535 N/A 0 0
vMCfgNo Configuration accordance with different
and measurement

(20,
Time Interval the average time window
URachPrd 40, ..,
for Taking an for the measurement,
UeTrv.aver 260)ms, ms 20ms 20ms
Average or a which is only valid when
ageTime step
Variance the measurement quantity
20ms
is Average RLC buffer

Recom
Name Range Value d
Value
RLC buffer payload.
4.1.8.8 Parameters Related to the UE Event Traffic Measurement on the PCH
on the PCH)
Recom
Name Range Value d
Value

the time interval for taking
(20,
Time Interval an average or a variance,
UPchEvUe 40, ..,
eTime step
Variance is „Average RLC buffer
20ms
payload‟ or „Variance of
RLC buffer payload‟.

traffic volume
UE Traffic
UPchEvUe by UE.
Volume
Trv.MeaEv Where (4a, 4b) N/A [4a] [4a]
Measurement
tId MAX_UE_TRV_MEAS_EV
Event Identity
ENT is the maximum
volume measurement
Event Number 1..MAX_

UPchEvUe This parameter indicates
of UE Traffic UE_TRV
Trv.measE event number of UE traffic N/A 1 1
Volume _MEAS_
vtNum volume measurement.
Measurement EVENT

Recom
Name Range Value d
Value
where
MAX_UE
_TRV_M
EAS_EV
ENT=2
1: RLC
buffer
payload,
2:
This parameter indicates Average
UPchEvUe the measurement quantity RLC RLC RLC
Measurement
Trv.measQ of the traffic volume buffer N/A buffer buffer
Quantity
uantity measurement that UE payload payload payload
performs. 3:
Variance
of RLC
buffer
payload

the RLC mode of the traffic
volume measurement
report. If the value is AM
RLC, RNC can request UE 0:
for retransmission after Acknowle
receiving the error SDU dged
Measurement label (not continuous). If Mode Acknow Acknow
UPchEvUe
Report the value is UM RLC, the RLC ledged ledged
Trv.measR N/A
Transfer retransmission is not 1: Mode Mode
ptTrMod
Mode required. Usually, report Unackno RLC RLC
the results of the important wledged
measurements in AM Mode
mode and those less RLC
important in UM mode (to
reduce the traffic volume of
and increase the system

Recom
Name Range Value d
Value
capacity).

event 4A and 4B for traffic (8, 16,
volume measurement for 32, 64,
Interactive and 128, 256,
Background Class on 512,
HS-DSCH Channel. If the 1024, 2K,
traffic volume becomes 3K, 4K,
larger than the threshold of 6K, 8K,
Traffic Volume
event 4A, a report of 4A 12K, 16K,
UPchEvUe Threshold of
event will be triggered; and 24K, 32K, [256] [256]
if the traffic volume 48K , bytes bytes
s for UE on
becomes smaller than the 64K, 96K,
PCH State
threshold of event 4B, a 128K,
report of 4B event will be 192K,
triggered. 256K,
Where 384K,
ENT is the maximum 768K)
number of UE traffic bytes
volume measurement

measurement
configuration index which
is used to index different
UE Traffic
parameter configuration
UPchEvUe Volume
sets for traffic volume
Trv.ueTrv Measurement 0..65535 N/A 0 0
MCfgNo Configuration
several different sets of
Index
configured values for the
same set of parameters
according to specific
measurement purpose,
measurement quantity and

Recom
Name Range Value d
Value
so on.

(20,
ULogicalR 40, ..,
nc.PchToO 260)ms, ms 100ms 100ms
therTVISw step
20ms

Pending Time the pending time after
URnluCfg. After 4A for EVENT 4A triggered by the
100..600 4200m 4200m
Pch4APen CELL_PCH user plan for CELL_PCH ms
00 s s
dingTime UE/URA_PC and URA_PCH UE, during
H UE which EVENT 4A shall not
be triggered again.
4.1.8.9 Parameters Related to the UE Event Traffic Measurement on the PCH
on the PCH)
Recom
Name Range Value d
Value

(20,
UPchEvUe 40, ..,
eTime step
20ms

4.1.9 Parameters Related to the Internal Measurement
Table 4-17 Parameter List (Parameters Related to the Internal Measurement)
Recom
Name Range Value d
Value
This parameter is used for

indexing the configuration
UE Internal
UPsEvtTP of the first set of
Measurement 0..65535,
UeInt.ueInt parameters of UE N/A
Configuration step 1
MCfgNo transmitted power event
Index
report for packet domain
service. 0 0

the RLC mode for the UE
internal measurement
report. If AM mode is used,
when the RNC receives an
SDU with a wrong SDU
label (discontinuous), the 0:
RNC can request the UE Acknowle
to retransmit the SDU. If dged
Measurement UM mode is used, the Mode Acknow Acknow
UPsEvtTP
Report retransmission is not RLC ledged ledged
UeInt.mea N/A
Transfer required. In general, 1: Mode Mode
sRptTrMod
Mode important measurement Unackno RLC RLC
results are reported in AM wledged
mode, and other Mode
measurement results are RLC
reported in UM mode (this
can reduce the traffic
volume caused by
measurement reports and
increase the system
capacity).
UPsEvtTP This parameter indicates (0, 1, 2,

Filter
UeInt.filter the filter coefficient used 3, 4, 5, 6, N/A 3 3
Coefficient
Coeff by the UE to perform L3 7, 8, 9,

Recom
Name Range Value d
Value
filtering on internal 11, 13,
measurement results. 15, 17,
For the UE, L1 performs 19)
the measurement based
on the fixed measurement
period (Multiple points may
be measured in a
measurement period. L1
uses the filtering method
that is freely decided by
the UE to filter
measurement results), L1
reports the filtered
measurement results to L3
periodically, and then L3
filters the measurement
results and the
measurement results
previously stored. The
filtering method is defined
by the protocol:
Fn= (1-a) * Fn-1 + a * Mn
Fn is the updated filtered
measurement result.
Fn-1 is the last filtered
measurement result.
Mn is the latest received
measurement result.
a = (1/2)^ (k/2), where k is
the filter coefficient.
Note that, if k is set to 0, L3
filtering is not performed.
Maximum
UPsEvtTP This parameter indicates
Event Number 1..7, step
UeInt.mea the number of UE internal N/A 2 2
of UE Internal 1
sEvtNum measurement events.
Measurement

Recom
Name Range Value d
Value

the UE internal
measurement event
identity including 6A, 6B,
6F, and 6G.
6A: The UE Tx power
becomes larger than an
absolute threshold;
6B: The UE Tx power
UPsEvtTP UE Internal becomes less than an
[6a, 6b,
UeInt.mea Measurement absolute threshold; N/A [6a, 6b] [6a, 6b]
6f, 6g]
EvtId Event Identity 6F: The UE Rx-Tx time
difference for a RL
included in the active set
becomes larger than an
absolute threshold
6G: The UE Rx-Tx time
difference for a RL
included in the active set
becomes less than an
absolute threshold
(0, 10,
20, 40,
60, 80,
100, 120,
UPsEvtTP the period of time during
Time to 160, 200, [1280, [1280,
UeInt.trigTi which the event criteria is ms
Trigger 240, 320, 1280] 1280]
me satisfied before sending a
640,
measurement report.
1280,
2560,
5000)ms
UE
UPsEvtTP This parameter indicates (-50,
Transmitted
UeInt.txPo the UE transmitted power 0)dB, dB [-1, -2] [-1, -2]
Power
werThres threshold in event 6a/6b. step 1dB
Threshold
UUeIntMea Profile Id ID of UE internal 0..9, step N/A 0 0

Recom
Name Range Value d
Value
sProfile.pro measurement Profile 1
fileId
4.1.10 Parameters Related to the Dedicated Measurement
Table 4-18 Parameter List (Parameters Related to the Dedicated Measurement)
Recomme
Parameter Parameter Value Default
GUI Name Unit nded
Name Description Range Value
Value
Period Period
Report Report
Parameters Parameter
for TCP in s for TCP
Power in Power
Balance: Balance:
Transmitted Transmitte
Code Power d Code
Period Power
Report Period
1: SIR Error Parameters Report
This parameter
2: for TCP in Parameter
UNbDedM Dedicated indicates the type of
Transmitted AMR or s for TCP
eas.dedMe Measurement dedicated N/A
Code Power DASF-PS or in AMR or
asType Type measurement to be
5: Round Handover DASF-PS
executed by Node B
Trip Time Control: or
Transmitted Handover
Code Power Control:
Event A Transmitte
Report d Code
Parameters Power
for TCP in Event A
DASF-PS: Report
Transmitted Parameter
Code Power s for TCP
Event B in

Recomme
GUI Name Unit nded
Value
Report DASF-PS:
Parameters Transmitte
for TCP in d Code
DASF-PS: Power
Transmitted Event B
Code Power Report
Period Parameter
Report s for TCP
Parameters in
for RTT in DASF-PS:
LCS: Round Transmitte
Trip Time d Code
Event E Power
Report Period
Parameters Report
for SIR Error Parameter
in Outer s for RTT
Loop Power in LCS:
Control: SIR Round
Error Trip Time
Event F Event E
Report Report
for SIR Error s for SIR
in Outer Error in
Loop Power Outer
Control: SIR Loop
Error Power
Event A Control:
Report SIR Error
Parameters Event F
for TCP in Report
AMR: Parameter
Transmitted s for SIR
Code Power Error in
Event B Outer
Report Loop
Parameters Power

Recomme
GUI Name Unit nded
Value
for TCP in Control:
AMR: SIR Error
Transmitted Event A
Code Power Report
Event A Parameter
Report s for TCP
Parameters in AMR:
for TCP in Transmitte
Handover d Code
Control: Power
Transmitted Event B
Code Power Report
Event B Parameter
Report s for TCP
Parameters in AMR:
for TCP in Transmitte
Handover d Code
Control: Power
Transmitted Event A
Code Power Report
Parameter
s for TCP
in
Handover
Control:
Transmitte
d Code
Power
Event B
Report
Parameter
s for TCP
in
Handover
Control:
Transmitte
d Code
Power

Recomme
GUI Name Unit nded
Value
1. Event A 1. Event A
Report Report
1 for TCP in s 1 for
DASF-PS: TCP in
100ms DASF-PS:
2. Event B 100ms
For event A/B/E/F, Report 2. Event B
this parameter is Parameters Report
measurement 1 for TCP in Parameter
hysteresis time and DASF-PS: s 1 for
the measurement 100ms TCP in
hysteresis time 3. Event E DASF-PS:
provides the Report 100ms
duration during Parameters 3. Event E
which a reporting for SIR Error Report
Measurement criterion has to be in Outer Parameter
Change fulfilled for the Loop Power s for SIR
UNbDedM
Time/Measure Measurement (10..60000) Control: Error in
eas.evtAbc ms
ment Reporting procedure ms, step 200ms Outer
defTime
Hysteresis to be triggered. 10ms 4. Event F Loop
Time For event C/D, this Report Power
parameter is change Parameters Control:
time. and the for SIR Error 200ms
change time is the in Outer 4. Event F
time the Loop Power Report
measurement entity Control: Parameter
shall rise on (in ms), 200ms s for SIR
in order to trigger a 5. Event A Error in
measurement Report Outer
report. Parameters Loop
for TCP in Power
AMR: Control:
100ms 200ms
6. Event B 5. Event A
Report Report

Recomme
GUI Name Unit nded
Value
AMR: in AMR:
100ms 100ms
7. Event A 6. Event B
Report Report
Handover in AMR:
Control: 100ms
100ms 7. Event A
8. Event B Report
Report Parameter
Parameters s for TCP
for TCP in in
Handover Handover
Control: Control:
100ms 100ms
9. Other 8. Event B
measureme Report
nts: - Parameter
s for TCP
in
Handover
Control:
100ms
9. Other
measurem
ents: -
This parameter 1. Event E 1. Event E

indicates the Report Report
threshold 2 used for Parameters Parameter
triggering event E, F for SIR Error s for SIR
Measurement
UNbDedM for SIR Error in Outer Error in
Threshold 2 of
eas.evtEfSi measurement. And (-31..31)dB, dB Loop Power Outer
Event E/F for
rEThrd2 EvtEfSirEThrd1 step 0.5dB Control: 1dB Loop
SIR Error
indicates the 2. Event F Power
threshold 1 used for Report Control:
triggering event E, F Parameters 1dB
for SIR Error for SIR Error 2. Event F

Recomme
GUI Name Unit nded
Value
measurement. in Outer Report
EvtEfSirEThrd1 and Loop Power Parameter
EvtEfSirEThrd2 are Control: s for SIR
used together to -1dB Error in
determine SIR error 3. Other Outer
event state of the measureme Loop
radio link as the nts: - Power
following: E1 state: Control:
SIRerror > -1dB
EvtEfSirEThrd1 3. Other
corresponding to E measurem
event, or when RL is ents: -
in E1 state and
SIRerror >=
EvtEfSirEThrd2
corresponding to E
event; E2 state:
SIRerror <
EvtEfSirEThrd2
corresponding to E
event; F1 state:
SIRerror <
EvtEfSirEThrd1
corresponding to F
event or RL is in F1
state and SIRerror
<= EvtEfSirEThrd2
corresponding to F
event; F2 state:
SIRerror >EvtEfSirE
Thrd2
corresponding to F
event.
This parameter
(0, 1, 2, 3, 4,
UNbDedM Measurement indicates how All All
5, 6, 7, 8, 9,
eas.measF Filter filtering of the N/A measureme measurem
11, 13, 15,
ilterCoeff Coefficient measurement nts: 2 ents: 2
17, 19)
values shall be

Recomme
GUI Name Unit nded
Value
performed before
measurement event
evaluation and
reporting.
The averaging shall
be performed
according to the
following formula.
F(n) =(1-a)* F(n-1)
+ a*M(n)
The variables in the
formula are defined
as follows:
F(n) is the updated
filtered
measurement result
F(n-1) is the old
filtered
measurement result
Mn is the latest
received
measurement result
from physical layer
measurements
a = (1/2)^ (k/2) ,
where k is the
Measurement Filter
Coefficient. If k=1
there‟s no filtering)
In order to initialise
the averaging filter,
F(0) is set to M(1)
when the first
measurement result
from the physical
layer measurement
is received.
UNbDedM Function of This parameter 0: Period N/A 0: Period 0: Period

Recomme
GUI Name Unit nded
Value
eas.nbDM Configuration indicates the Report Report Report
CfgNote Parameters function, purpose Parameters Parameters Parameter
etc. of the dedicated for TCP in for TCP in s for TCP
measurement Power Power in Power
parameters Balance Balance Balance
indicated by the 1: Period 1: Period 1: Period
configuration index. Report Report Report
Parameters Parameters Parameter
for TCP in for TCP in s for TCP
AMR or AMR or in AMR or
DASF-PS or DASF-PS or DASF-PS
Handover Handover or
Control Control Handover
2: Event A 2: Event A Control
Report Report 2: Event A
Parameters Parameters Report
for TCP in for TCP in Parameter
DASF-PS DASF-PS s for TCP
3: Event B 3: Event B in
Report Report DASF-PS
Parameters Parameters 3: Event B
for TCP in for TCP in Report
DASF-PS DASF-PS Parameter
4: Period 4: Period s for TCP
Report Report in
Parameters Parameters DASF-PS
for RTT in for RTT in 4: Period
LCS LCS Report
5: Event E 5: Event E Parameter
Report Report s for RTT
Parameters Parameters in LCS
for SIR Error for SIR Error 5: Event E
in Outer in Outer Report
Loop Power Loop Power Parameter
Control Control s for SIR
6: Event F 6: Event F Error in
Report Report Outer
Parameters Parameters Loop

Recomme
GUI Name Unit nded
Value
for SIR Error for SIR Error Power
in Outer in Outer Control
Loop Power Loop Power 6: Event F
Control Control Report
7: Event A 7: Event A Parameter
Report Report s for SIR
Parameters Parameters Error in
for TCP in 2 for TCP in Outer
AMR AMR Loop
8: Event B 8: Event B Power
Report Report Control
Parameters Parameters 7: Event A
for TCP in 2 for TCP in Report
AMR AMR Parameter
9: Event A 9: Event A s 2 for
Report Report TCP in
Parameters Parameters AMR
for TCP in for TCP in 8: Event B
Handover Handover Report
Control Control Parameter
10: Event B 10: Event B s 2 for
Report Report TCP in
Parameters Parameters AMR
for TCP in for TCP in 9: Event A
Handover Handover Report
Control Control Parameter
s for TCP
in
Handover
Control
10: Event
B Report
Parameter
s for TCP
in
Handover
Control
UNbDedM Report Period This parameter RptPrdUnit ms Period Period

Recomme
GUI Name Unit nded
Value
eas.rptPrd indicates the =1: Report Report
frequency of (10..60000) Parameters Parameter
measurement report ms, step for TCP in s for TCP
transmitted by Node 10ms AMR or in AMR or
B. RptPrdUnit DASF-PS or DASF-PS
=2: Handover or
(1..60)min Control : Handover
step min 1000ms; Control :
Other 1000ms;
measureme Other
nts: 4000ms measurem
ents:
4000ms
This parameter
indicates the report
UNbDedM Choice Report
period unit applied 1: ms
eas.rptPrd Periodicity N/A ms ms
by Node B for 2: min
Unit Scale
measurement result
reporting.
Period Period
Report Report
Power in Power
This parameter 1: On Balance: Balance:
indicates the report Demand Periodic Periodic
characteristics of 2: Periodic Period Period
UNbDedM Report measurement 3: Event A Report Report
eas.rptTyp Characteristic results, which can 4: Event B N/A Parameters Parameter
e s be on demand, 5: Event C for TCP in s for TCP
periodic or by 6: Event D AMR or in AMR or
triggering all kinds 7: Event E DASF-PS or DASF-PS
of: events. 8: Event F Handover or
Control: Handover
Periodic Control:
Event A Periodic
Report Event A
Parameters Report

Recomme
GUI Name Unit nded
Value
for TCP in Parameter
AMR or s for TCP
DASF-PS: in AMR or
Event A DASF-PS:
Event B Event A
Report Event B
Parameters Report
for TCP in Parameter
AMR or s for TCP
DASF-PS: in AMR or
Event B DASF-PS:
Period Event B
Report Period
Parameters Report
for RTT in Parameter
LCS: s for RTT
Periodic in LCS:
Event E Periodic
Report Event E
Parameters Report
for SIR Error Parameter
in Outer s for SIR
Loop Power Error in
Control: Outer
Event E Loop
Event F Power
Report Control:
Parameters Event E
for SIR Error Event F
in Outer Report
Loop Power Parameter
Control: s for SIR
Event F Error in
Event A Outer
Report Loop
Parameters Power
for TCP in Control:
AMR: Event Event F

Recomme
GUI Name Unit nded
Value
A Event A
Event B Report
Report Parameter
for TCP in in AMR:
AMR: Event Event A
B Event B
Event A Report
Report Parameter
for TCP in in AMR:
Handover Event B
Control: Event A
Event A Report
Event B Parameter
Report s for TCP
Parameters in
for TCP in Handover
Handover Control:
Control: Event A
Event B Event B
Report
Parameter
s for TCP
in
Handover
Control:
Event B
This parameter 1. Event E 1. Event E

indicates the Report Report
threshold 1 used for Parameters Parameter
Measurement triggering event E, F for SIR Error s for SIR
UNbDedM
Threshold 1 of for SIR Error in Outer Error in
eas.evtEfSi (-31..31)dB, dB
Event E/F for measurement. And Loop Power Outer
rEThrd1 step 0.5dB
SIR Error EvtEfSirEThrd2 Control: 4dB Loop
indicates the 2. Event F Power
threshold 2 used for Report Control:
triggering event E, F Parameters 4dB

Recomme
GUI Name Unit nded
Value
for SIR Error for SIR Error 2. Event F
measurement. in Outer Report
EvtEfSirEThrd1 and Loop Power Parameter
EvtEfSirEThrd2 are Control: s for SIR
used together to -4dB Error in
determine SIR error 3. Other Outer
event state of the measureme Loop
radio link as the nts: - Power
following: E1 state: Control:
SIRerror > -4dB
EvtEfSirEThrd1 3. Other
corresponding to E measurem
event, or when RL is ents: -
in E1 state and
SIRerror >=
EvtEfSirEThrd2
corresponding to E
event; E2 state:
SIRerror <
EvtEfSirEThrd2
corresponding to E
event; F1 state:
SIRerror <
EvtEfSirEThrd1
corresponding to F
event or RL is in F1
state and SIRerror
<= EvtEfSirEThrd2
corresponding to F
event; F2 state:
SIRerror >EvtEfSirE
Thrd2
corresponding to F
event.
Downlink Rate This parameter NbDMCfgN NbDMCfg

UNbDedM (1..65535)
Level indicates the ote =2 or 3 Note =2 or
eas.dlRate kbps, step 1 kbp
Threshold downlink rate level (Event A/B 3 (Event
Level kbps s
used for threshold, In D-TCP Report A/B

Recomme
GUI Name Unit nded
Value
D-TCP based PS DRBC, Parameters Report
Measurement the thresholds of for TCP in Parameter
in DASF-PS D-TCP DASF-PS): s for TCP
measurement event [64, 128] in
A/B are got based kbps DASF-PS)
on the rate level of Other : [64, 128]
the service. measureme kbps
nts: need Other
not be measurem
configured. ents: need
not be
configured
.
This parameter 1. 1.
indicates the power NbDMCfgN NbDMCfg
offset of the DPCH ote =2 Note =2
maximum DL (Event A (Event A
power, which Report Report
defines which Parameters Parameter
threshold that shall for TCP in s for TCP
trigger event A, B for DASF-PS): in
transmitted carrier [-0.4dB DASF-PS)
power -0.4dB : [-0.4dB
Measurement measurement. -0.4dB]; -0.4dB
UNbDedM Threshold of In PS DRBC, this 2. -0.4dB];
(-50..0)dB,
eas.evtAbT Event A/B for threshold is related dB NbDMCfgN 2.
step 0.1dB
cpThrd Transmitted to the service rate ote =3 NbDMCfg
Code Power as following: (Event B Note =3
Rate Level PS Report (Event B
Service Rate (R) Parameters Report
Threshold of Event for TCP in Parameter
A/B DASF-PS): s for TCP
Level 1 R<= [-1.6dB in
DlRateLevel[0] -1.6dB DASF-PS)
EvtAbTcpThrd [0] -1.6dB]; : [-1.6dB
Level 2 3. -1.6dB
DlRateLevel[0]<R<= NbDMCfgN -1.6dB];
DlRateLevel[1] ote =7 3.

Recomme
GUI Name Unit nded
Value
EvtAbTcpThrd [1] (Event A NbDMCfg
Level 3 Report Note =7
R>DlRateLevel[1] Parameters (Event A
EvtAbTcpThrd [2] for TCP in Report
Other case, the AMR): Parameter
threshold and [-0.4dB - -]; s for TCP
service rate 4. in AMR):
independent, and NbDMCfgN [-0.4dB -
the threshold is ote =8 -];
EvtAbTcpThrd [0]. (Event B 4.
Report NbDMCfg
Parameters Note =8
for TCP in (Event B
AMR): Report
[-1.6dB - -]; Parameter
5. s for TCP
NbDMCfgN in AMR):
ote =9 [-1.6dB -
(Event A -];
Report 5.
Parameters NbDMCfg
for TCP in Note =9
Handover (Event A
Control): Report
[-0.4dB - -]; Parameter
6. s for TCP
NbDMCfgN in
ote =10 Handover
(Event B Control):
Report [-0.4dB -
Parameters -];
for TCP in 6.
Handover NbDMCfg
Control): Note =10
[-1.6dB - -]; (Event B
7. Other Report
measureme Parameter
nts: need s for TCP

Recomme
GUI Name Unit nded
Value
not be in
configured. Handover
Control):
[-1.6dB -
-];
7. Other
measurem
ents: need
not be
configured
.
NbDed This parameter

UNbDedM
Measure indicates the NbDed
eas.nbDM 0..65535 N/A NA NA
Configuration Measure
CfgNo
No Configuration No.
This parameter
indicates the Profile
Id for the NodeB
dedicated
UNbDedM
measurement. Each
easProfile. Profile Id 0..9 N/A
profile corresponds
profileId
one setting of
NodeB dedicated
measurement
parameters. 0 0

4.2 ZWF21-05-016 Video Call Prohibited in Specific

Area
Table 4-19 Parameter List (Parameters Related to the Video Call Prohibited in Specific
Area)
Recom
Name Range Value d
Value

whether the external cell
Switch of CS
allows the accessing of
64kbps
traffic of CS 64kbps. If this 0: Off
Establishment N/A 1: On 1: On
UExternal switch is "Off", the traffic 1: On
for External
UtranCellF cannot be accessed. If this
UTRAN Cell
DD.adjCs6 switch is "On", the traffic
4Switch can be accessed.

whether the CS64 kbps
service accessing in the
cell is allowed or not.
Switch of CS
If this switch is "Off", the 0: Off
64kbps N/A 1: On 1: On
traffic of CS 64 kbps is not 1: On
Establishment
allowed.
UUtranCell If this switch is "On", the
FDD.Cs64 traffic of CS 64 kbps is
Switch allowed.

5 Related Counters and Alarms
5.1 Related Counters
Table 5-1 Counter List
Counter ID Name
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

C310414098
attempt, FACH to DCH

C310414099
attempt, DCH to FACH

C310414100
attempt, FACH to PCH

C310414101
attempt, PCH to FACH
Number of intra frequency Transport Channel successful

C310414110
Changing attempt, FACH to DCH

C310414111
Changing attempt, DCH to FACH

C310414112
Changing attempt, FACH to PCH

C310414113
Changing attempt, PCH to FACH
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

C310405737
by one step

C310416901
attempt, DCH to PCH

C310416902
attempt, PCH to DCH

C310416905
Changing attempt, DCH to PCH

C310416906
Changing attempt, PCH to DCH
Number of inter frequency Transport Channel Changing

C310414132
attempt, FACH to DCH

C310414133
attempt, DCH to FACH

C310414134
attempt, FACH to PCH

C310414135
attempt, PCH to FACH

C310416909
attempt, DCH to PCH

C310416910
attempt, PCH to DCH
Number of inter frequency Transport Channel successful

C310416914
Changing attempt, PCH to DCH

C310414144
Changing attempt, FACH to DCH

C310414145
Changing attempt, DCH to FACH


C310414146
Changing attempt, FACH to PCH

C310414147
Changing attempt, PCH to FACH

C310416913
Changing attempt, DCH to PCH
5.2 Related Alarms
This feature has no related alarm.
6 Engineering Guide
6.1 Application Scenario
Application scenario for this feature:
 During a channel setup process, DRBC allocates appropriate radio channel and
initial rate to the service according to service requirements and system resource
utilization status.
 Dynamic DCH rate adjustment: DCH rate configuration is adjusted for the
consistency with the actual traffic rate. If the cell load is too high or the system
resources are congested, the DCH rate can be decreased to decrease the system
load. If the transmission power of the radio link is too high, the DCH rate can be
lowered to decrease excessive consumption of the system capacity and reduce the
risk of call drops caused by handover of high rate services. If the system resources

for a hard handover to the target cell are limited when the same DCH rate is
provided, the rate can be decreased before the handover.
 Channel switching: If the actual rate of the PS interactive service or PS background

service falls below the traffic volume threshold or if overload occurs in the cell, the
UE transmits from the CELL_DCH to the CELL_FACH state. If there is no actual
traffic volume rate for a long period, the UE can transmit to the URA_PCH or
CELL_PCH or IDLE state to save the battery power and resources. If the UE in
URA_PCH state or CELL_PCH state sends a cell update message due to uplink
data transmission, or downlink data transmission, or a new service establishment
request, the UE transmits to the CELL_DCH or CELL_FACH state. If a UE has
stayed in URA PCH state or CELL_PCH state over a period greater than a
threshold, the UE transmits to the IDLE state.
The DRBC feature provides positive gain for increasing the system throughput and other
basic KPIs. It is a mandatory feature and should be enabled once the system is running.
In some areas, for example, security control zones or privacy-sensitive areas, the video
call service is prohibited and must be disabled in the network layer. This feature allows
the system to disable the video call service for specific cells.
6.2 Feature Activation Procedure
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
In the configuration resource tree, select Modify Area -> Managed Element -> UMTS
Logical Function Configuration -> Global Information Configuration, double click

Dynamic Radio Bearer Control Information Profile, and configure Drbc Strategy
Configuration Index and Drbc Strategy Name, see Figure 6-1.
Figure 6-1 Parameter Configuration 1
Logical Function Configuration -> Global Information Configuration, double click
Dynamic Radio Bearer Control Information Profile -> Dynamic Radio Bearer
Control Information, and configure Event 4A Counter Threshold for CELL_FACH to
CELL_DCH Shared by Uplink and Downlink, Event 4A Counter Threshold for
Increasing Rate on DCH or DCH->HSPA, Event 4B Counter Threshold for
Decreasing Rate on DCH, Event 4B Counter Threshold for CELL_DCH to PCH
Shared by Uplink and Downlink, Event 4B Counter Threshold for CELL_FACH
without DRX to Idle Shared by Uplink and Downlink, Event 4B Counter Threshold
for CELL_DCH to Idle Shared by Uplink and Downlink, Event 4B Counter
Threshold for CELL_FACH without DRX to PCH Shared by Uplink and Downlink,
Time Threshold for CELL_PCH or URA_PCH to Idle, Event 4B Counter Threshold
for Cell_Dch to Cell_FACH, Event A Counter Threshold for PS on DL DCH or DL
AMR Decreasing Rate Based on D-TCP, Event B Counter Threshold for Restriction
PS Increasing Rate on DL DCH or Triggering DL AMR Increasing Rate Based on
D-TCP, Switch of Transferring to CELL_FACH, Switch of URA_PCH/CELL_PCH
Support, and Increment Times of Event 4B0 for UE Which is not sensitive for
Battery Consumption Transferred to URA_PCH/CELL_PCH or Idle state, see Figure
6-2.

In the configuration resource tree, select Modify Area -> Managed Element, double
click UMTS Logical Function Configuration, and configure Global Reserved
Parameter 4, Global Reserved Parameter 48, Global Reserved Parameter 52, Wait
Timer for Adjusting Uplink and Downlink Reconfiguration by One Step Downward,
Wait Timer for Adjusting Uplink and Downlink Reconfiguration by One Step
Upward, Switch of Non Emergency CS Service Access to CELL_FACH On RRC,
Type of Transport Channel for Initial RRC Connection Setup, and Switch of
URA_PCH/CELL_PCH for UE of Release 99 and Release 4, see Figure 6-3.


Logical Function Configuration -> PLMN Relating Configuration, double click Logic
RNC Configuration, and configure Used Dynamic Radio Bearer Control Information
Profile, C Traffic Rate Threshold Used for Determining NRT PS Rate Upper Limit
and NRT PS Traffic Downlink Rate Upper Limit When High Rate C Traffic+ PS
Traffic, NRT PS Traffic Uplink Rate Upper Limit When High Rate C Traffic+ PS
Traffic, NRT PS Traffic Downlink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic, NRT PS Traffic Uplink Rate Upper Limit When Low Rate C Traffic+ PS
Traffic, Initial Rate of DL DCH, Initial Rate of UL DCH, Switch of 6.8kbps Signalling

Using on DCH, Uplink Rate Adjustment Level Number, Uplink Rate Adjustment
Level, Downlink Rate Adjustment Level Number, Downlink Rate Adjustment Level,
DRBC Method Switch, Switch for DL DCH Rate Adjustment Based on D-TCP,
Switch for UL DCH Rate Adjustment Based on UE Transmission Power, Downlink
Maximum Rate Threshold of I/B Service on CELL_FACH, Uplink Maximum Rate
Threshold of I/B Service on RACH, Switch for DCH Rate Adjustment Based on
Traffic Volume Measurement, Switch of whether to Punish the UE that can't Camp
on PCH state, and Switch of the Channel Selection Strategy whether to be decided
by Traffic volume indicator IE of UE's Switching from PCH to Other Channel, see
Figure 6-4.


Logical Function Configuration, double click UTRAN Cell, and configure Maximum
Allowable Rate on DCH to be Increased to When UE is in Macro Diversity,
Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell, Maximum Bit Rate
on DL DCH for NRT PS RAB in Serving Cell, Switch of CS64 kbps Establishment,
Used Traffic Volume Measurement Profile, Used UE Internal Measurement Profile,

CS Traffic Preferred Indicator, and R99 PS Traffic Preferred Indicator, see Figure
6-5.

Logical Function Configuration -> UTRAN Cell, double click Extended Info of
UTRAN Cell, and configure Cell Level PCH Switch, Maximum Bit Rate on UL DCH for
RT PS RAB in Serving Cell, Maximum Bit Rate on DL DCH for RT PS RAB in
Serving Cell, and Maximum Bit Rate allowed for Signalling in Cell, see Figure 6-6.


Logical Function Configuration -> External Resource Configuration -> External
RNC Function, double click External UTRAN Cell, and configure Maximum Bit Rate
on DL DCH for NRT PS RAB in External UTRAN Cell, Maximum Bit Rate on UL DCH
for NRT PS RAB in External UTRAN Cell, Maximum Bit Rate on DL DCH for RT PS
RAB in External UTRAN Cell, Maximum Bit Rate on UL DCH for RT PS RAB in
External UTRAN Cell, and Switch of CS 64kbps Establishment for External UTRAN
Cell, see Figure 6-7.

Logical Function Configuration -> Link Configuration, double click Iur Link, and
configure Whether Support PS (0kbps/0kbps), see Figure 6-8.

Logical Function Configuration -> Service Configuration -> Measurement
Configuration, double click Traffic Volume Measurement Profile, and configure
Profile Id, see Figure 6-9.

Configuration -> Traffic Volume Measurement Profile, double click UE Traffic
Volume Event Measurement Configuration for RACH, and configure Measurement
Report Transfer Mode, Measurement Quantity, Time Interval for Taking an Average
or a Variance, RLC Buffer Payload for Each RB, Average of RLC Buffer Payload for
Each RB, Variance of RLC Buffer Payload for Each RB, Event Number of UE Traffic
Volume Measurement, UE Traffic Volume Measurement Event Identity, Traffic
Volume Threshold of Event 4A/4B for RACH Channel, Time to Trigger, Pending
Time After Trigger, Tx Interruption After Trigger Configuration Tag, and Tx
Interruption After Trigger, see Figure 6-10.
Volume Period Measurement Configuration for RACH, and configure UE Traffic
Volume Period Measurement Configuration Object ID for RACH, Measurement

Each RB, Variance of RLC Buffer Payload for Each RB, Amount of Reporting in
Period Report Criteria, and Reporting Interval in Period Report Criteria, see Figure
6-11.
Configuration -> Traffic Volume Measurement Profile, double click UP Traffic
Volume Event Measurement Configuration for FACH, and configure Measurement
Volume Threshold of Event 4A/4B for FACH Channel, Time to Trigger, and Pending
Time After Trigger, see Figure 6-12.

Volume Event Measurement Configuration for DCH, and configure Measurement
Volume Threshold of Event 4A/4B for DCH (8kbps), Traffic Volume Threshold of
Event 4A/4B for DCH (16kbps), Traffic Volume Threshold of Event 4A/4B for DCH
(32kbps), Traffic Volume Threshold of Event 4A/4B for DCH (64kbps), Traffic
Volume Threshold of Event 4A/4B for DCH (128 kbps), Traffic Volume Threshold of
(384kbps), Time to Trigger, and Pending Time After Trigger, see Figure 6-13.

Configuration -> Traffic Volume Measurement Profile, double click UP Traffic
Volume Event Measurement Configuration for DCH, and configure Measurement

Volume Threshold of Event 4A/4B for DCH (8kbps), Traffic Volume Threshold of
(32kbps), Traffic Volume Threshold of Event 4A/4B for DCH (64kbps), Traffic
Volume Threshold of Event 4A/4B for DCH (128 kbps), Traffic Volume Threshold of
(384kbps), Time to Trigger, and Pending Time After Trigger, see Figure 6-14.

Volume Period Measurement Configuration for DCH, and configure Measurement
Each RB, Variance of RLC Buffer Payload for Each RB, Amount of Reporting in
Period Report Criteria, and Reporting Interval in Period Report Criteria, see Figure
6-15.

Volume Event Measurement Configuration for PCH, and configure Time Interval for
Taking an Average or a Variance, UE Traffic Volume Measurement Event Identity,
Event Number of UE Traffic Volume Measurement, Measurement Report Transfer
Mode, Measurement Quantity, and Traffic Volume Threshold of Event 4A/4B for UE
on PCH State, see Figure 6-16.

Configuration -> UE Internal Measurement Profile, double click UE Transmitted
Power Event Measurement Configuration for PS, and configure Measurement
Report Transfer Mode, Filter Coefficient, Maximum Event Number of UE Internal
Measurement, UE Internal Measurement Event Identity, Time to Trigger, and UE
Transmitted Power Threshold, see Figure 6-17.
Configuration -> NodeB Dedicated Measurement Profile, double click NodeB
Dedicated Measurement Configuration, and configure Function of Configuration
Parameters, Dedicated Measurement Type, Measurement Filter Coefficient, Report
Characteristics, Measurement Threshold 1 of Event E/F for SIR Error, Downlink
Rate Level Threshold used for D-TCP Measurement in DASF-PS, Measurement
Threshold of Event A/B for Transmitted Code Power, Measurement Threshold 2 of
Event E/F for SIR Error, Measurement Change Time /Measurement Hysteresis Time,
Choice Report Periodicity Scale, and Report Period, see Figure 6-18.

Logical Function Configuration -> Link Configuration, double click Radio Network
Layer User Plane Global Parameters, and configure Pending Time After 4A for
CELL_PCH UE/URA_PCH UE, see Figure 6-19
Figure 6-19 Parameters configuration interface 19
Logical Function Configuration -> UTRAN Cell, double click Extended Info Of

UTRAN Cell] interface and set the parameter, and configure Bit0 of Cell Reserved
Parameter 7, see Figure 6-20
Figure 6-20 Parameters configuration interface 20
This procedure describes how to locate the parameters related to this feature in the GUI.
The parameter values on the screenshots in the procedure are for reference only. Refer
to Chapter 4 for the recommended values of the related parameters.
Logical Function Configuration, double click UTRAN Cell, and configure Switch of
CS64 kbps Establishment, see Figure 6-21.

Logical Function Configuration -> External Resource Configuration -> External
RNC Function, double click External UTRAN Cell, and configure Switch of CS 64kbps
Establishment for External UTRAN Cell, see Figure 6-22.

6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item Dynamic Radio Bearer Control
1. The WCDMA system is ready.

2. Cell1 supports HSUPA, HSDPA, and DCH.
Prerequisit
3. UE1 camps on Cell1 in Idle mode.
e
4. UE1 supports R99 and subscribes to the interactive or background
service, MBR = UL 2 Mbps/DL 2 Mbps.
1. UE1 activates a PS service on the DCH/DCH.

2. Keep pinging small packets. The channel state of UE1 changes
from CELL_DCH to CELL_FACH after a while.
3. Ping 32 bytes of packets in CELL_FACH state and last for 30
Steps
seconds.
4. Start FTP download and trigger UE1 to switch from CELL_FACH to
CELL_DCH after a while.
5. Release the PDP.
1. UE1 performs the channel switching procedure successfully
Expected between the CELL_DCH and CELL_FACH states.

Result 2. Pinging and FTP download are proper in CELL_FACH and
CELL_DCH state.
Table 6-2 Feature Validation Procedure
Test Item Video Call Prohibited in Specific Area

Test Item Video Call Prohibited in Specific Area
1. The WCDMA system is ready.
Prerequisit 2. Cell1 supports HSUPA, HSDPA, and DCH.

e 3. UE1 and UE 2 camp on Cell1 in Idle mode.
4. The video call function is activated in Cell1.
1. UE1 makes a video call to UE2 in Cell1. The service is established

successfully.
2. Release the video call.
Steps
3. Deactivate the video call function prohibited in Cell1.
4. UE1 makes a video call to UE2 in Cell1. The service fails to be
established.
Expected 1. When the function is disabled, video calls are allowed in Cell1.
Result 2. When the function is enabled, video calls are forbidden in Cell1.
6.4 Feature Deactivation Procedure
Table 6-3 RNC Parameter List 2
Managed Object.Logical Deactivation

GUI Name Default Value
Name Value
3: Switch On in 0: Switch Off in

DRBC Method
ULogicalRnc.drbcSwch UL & Switch On UL & Switch Off
Switch
in DL in DL
For the description and configuration of these parameters, refer to Section 6.2.
Table 6-4 RNC Parameter List 2
Default Deactivation
Managed Object.Logical Name GUI Name
Value Value

Default Deactivation
Managed Object.Logical Name GUI Name
Value Value
Switch of
UUtranCellFDD.Cs64Switch CS64 kbps 1: On 0: Off
Establishment
For the description and configuration of these parameters, refer to Section 6.2.
6.5 Impact on the Network
1. Impact on Equipment Performance
None
2. Impact on Network KPIs
Advantages of this feature:
 During a channel setup process, DRBC allocates appropriate radio channels and
initial rates for the service according to the service requirements and system
resource utilization.
 Dynamic DCH rate adjustment: DCH rate configuration is adjusted for the
consistency with the actual traffic rate. If the cell load is too high or the system
resources are congested, the DCH rate can be decreased to decrease the system
load. If the transmission power of the radio link is too high, the DCH rate can be
lowered to decrease excessive consumption of the system capacity and reduce the
risk of call drops caused by handover of high rate services. If the system resources
for a hard handover to the target cell are limited when the same DCH rate is
provided, the rate can be decreased before the handover.

 Channel switching: A UE can transit to an appropriate state based on the actual

traffic volume requirement. Therefore, the radio resources of the UEs that have no
traffic volume requirement can be released. The released resources can be used by
other UEs that have traffic volume requirement to increase the system capability.
When a UE has traffic volume requirement, it transits to an appropriate state
matching its requirement quickly. In this way, the user experience can be improved.
The DRBC feature provides positive gain for increasing the system throughput and other
basic KPIs.
Disadvantages of this feature:
None
1. Impact on Equipment Performance
None
2. Impact on Network KPIs
Advantages of this feature:
In some areas, for example, security control zones or privacy-sensitive areas, the video
call service must be disabled to satisfy the specific requirements of operators.
Disadvantages of this feature:
None
7 Abbreviation
Abbreviation Full Name
AM Acknowledged Mode
BO Buffer Occupation
CE Channel Element
CS Circuit Switched

DCH Dedicated Channel
DL Downlink
DPCH Dedicated Physical Channel
DRBC Dynamic Radio Bearer Control
DTCP Dedicated Transmit Code Power
E-DCH Enhanced Dedicated Transport Channel
EFDPCH Enhanced Fractional Dedicated Physical Channel
FACH Forward Access Channel
F-DPCH Fractional Dedicated Physical Channel
GBR Guaranteed Bit Rate
HSDPA High Speed Downlink Packet Access
HS-DSCH High-Speed Downlink Shared Channel
HSPA High-Speed Packet Access
HSUPA High Speed Uplink Packet Access
MaxBR Maximum Bit Rate
MO Managed Object
NRT Non-realtime
PCH Paging Channel
PS Packet Switched
QoS Quality of Service
RAB Radio Access Bearer
RACH Random Access Channel
RAN Radio Access Network
RB Radio Bearer
RLC Radio Link Control
RNC Radio Network Controller
RRM Radio Resource Management
RTWP Received Total Wideband Power
SDU Service Data Unit
TCP Transmission Control Protocol
UM Unacknowledged Mode
UMTS Universal Mobile Telecommunication System

WCDMA Wideband Code Division Multiple Access
8 Reference Document
[1]ZTE UMTS NB-AMR Rate Control Feature Guide
[2]ZTE UMTS WB-AMR Rate Control Feature Guide
[3]ZTE UMTS HSDPA Introduction Feature Guide
[4]ZTE UMTS HSUPA Introduction Feature Guide
[5]ZTE UMTS DC-HSDPA Feature Guide
[6]ZTE UMTS DC-HSUPA Feature Guide
[7]ZTE UMTS 4C-HSDPA Feature Guide
[8]ZTE UMTS F-DPCH & SRB over HSDPA Feature Guide
[9]ZTE UMTS Enhanced F-DPCH Feature Guide
[10]ZTE UMTS Overload Control Feature Guide
[11]ZTE UMTS Congestion Control Feature Guide
[12]ZTE UMTS Handover Control Feature Guide
[13]ZTE UMTS Processor Overload Control Feature Guide
[14]ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Parameter Reference
[15]ZXWR RNC (V3.13.10.15) Radio Network Controller Performance Counter

Reference
[16]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Parameter

Reference
[17]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Performance Counter

Reference

DRBC Zte PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DRBC Zte PDF

Transféré par

Droits d'auteur :

Formats disponibles

Dynamic Radio Bearer

Dynamic Radio Bearer Control

© 2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 7

3 Technical Description ..................................................................................... 13

ZTE Confidential Proprietary 2

4.1.9 Parameters Related to the Internal Measurement ............................................ 120

5 Related Counters and Alarms ...................................................................... 140

6 Engineering Guide ........................................................................................ 143

7 Abbreviation .................................................................................................. 172

8 Reference Document..................................................................................... 174

ZTE Confidential Proprietary 3

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

ZTE Confidential Proprietary 4

Table 2-1 License Control List ...........................................................................................12

ZTE Confidential Proprietary 5

Table 6-1 Feature Validation Procedure...........................................................................169

ZTE Confidential Proprietary 6

Node B version: [ZXSDRV4.13.10.20]

2.1 Feature Introduction

ZTE Confidential Proprietary 7

The R99 DRBC function mainly includes the following aspects:

 Initial Channel Allocation

 Signaling Channel Allocation

 Initial Service Channel Allocation

 Initial Access Rate Allocation for DCH

 Concurrent Service Channel Allocation

DRBC selects appropriate transport channels according to the actual rates of PS

ZTE Confidential Proprietary 8

Figure 2-1 State Transitions

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

 A service in CELL_DCH state uses the following types of channels: DL

 The CELL_FACH service uses DL FACH/UL RACH.

2.1.1 ZWF21-04-004 Dynamic Radio Bearer Control

ZTE Confidential Proprietary 9

 The interactive service and background service use FACHs/RACHs or DCHs.

 Dynamic DCH rate adjustment

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

ZTE Confidential Proprietary 10

 If the practical rate of the PS interactive service or PS background service falls

 When the UE in URA_PCH state or CELL_PCH state originates a cell update

 If the duration when a UE is in URA PCH or CELL_PCH state exceeds a

ZTE Confidential Proprietary 11

2.1.2 ZWF21-05-016 Video Call Prohibited in Specific Area

2.2 License Control

Table 2-1 License Control List

ZWF21-04-004 Dynamic Radio

ZWF21-05-016 Video Call Prohibited

2.3 Correlation With Other Features

2. Mutually Exclusive Features

ZTE Confidential Proprietary 12

3.1 ZWF21-04-004 Dynamic Radio Bearer Control

3.1.1 Introduction to Service Types

3.1.2 Initial Channel Allocation

3.1.2.1 Signaling Channel Allocation

 If the parameter URncFunction.initRrcOnDch is set to “0: Forced to CELL_DCH and

 If the parameter URncFunction.initRrcOnDch is set to “1: Forced to CELL_DCH and

ZTE Confidential Proprietary 13

 If the parameter URncFunction.initRrcOnDch is set to “2: Forced to FACH”, the

 If the parameter URncFunction.initRrcOnDch is set to “3: Not Forced, Using

 If the parameter URncFunction.initRrcOnDch is set to “4: Not Forced, Using

 If the parameter URncFunction.initRrcOnDch is set to “5: Forced to CELL_DCH and