QOS Reserved User

Reserved User QoS
Guarantee
Feature Guide
Reserved User QoS Guarantee

Version Date Author Reviewer Notes
Cai
V1.00 2015/5/20 Ke Yazhu First edition
Yaofang
© 2015 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 ............................................................................................... 6
2 Overview ............................................................................................................ 6
2.1 Feature Introduction ............................................................................................. 6
2.2 License Control .................................................................................................... 7
2.3 Correlation with Other Features ........................................................................... 7
3 Technical Description ....................................................................................... 8

3.1 Identify Reserved Users ....................................................................................... 8
3.1.1 Identify Reversed Users on SRNC ....................................................................... 9
3.1.2 Identify Reversed Users on DRNC ....................................................................... 9
3.2 Notify Node B of Reserved UEs ......................................................................... 10
3.3 Obtain QoS Parameters for Reserved Users ..................................................... 10
3.3.1 QoS Parameters for Reserved Users on SRNC ................................................. 10
3.3.2 QoS Parameters for Reserved Users on DRNC ................................................. 12
3.4 Limit Rate of Non-Reserved Users ..................................................................... 13
3.5 Indicate Node B to Suppress Loads in a Serving Cell and Intra-frequency
Neighbors .......................................................................................................... 14
3.6 Admission Control Strategy for Reserved Users ................................................ 15
3.6.1 Loose Admission Control Strategy for Reserved Users ...................................... 15
3.6.2 Admission Control Strategy for Non-Reserved Users when Reserved Users
Exist ................................................................................................................... 15
3.7 Congestion Strategy .......................................................................................... 17
3.8 Handover Control Policy for Reserved Users ..................................................... 18
3.8.1 Intra-frequency Handover Parameters for Reserved Users ................................ 18
3.8.2 Relocate a Reserved user to DRNC................................................................... 18
3.9 DRBC Strategy for Reserved Users ................................................................... 18
3.9.1 Signaling Channel Allocation for Reserved Users .............................................. 18
3.9.2 Channel Transition for Reserved Users ............................................................. 19
3.9.3 E-TTI Policy for Reserved Users ........................................................................ 20
3.10 Power Control for Reserved Users ..................................................................... 22
3.11 Code Resource Allocation.................................................................................. 27
3.12 Reserved Frequency.......................................................................................... 28
3.12.1 Load Balance ..................................................................................................... 28
3.12.2 Admission Control Strategy ................................................................................ 33
3.12.3 Congestion Strategy .......................................................................................... 35
3.13 Paging ............................................................................................................... 37
3.14 Overbooking ...................................................................................................... 37
3.14.1 Overbooking Priority for Reserved Users ........................................................... 38

3.14.2 Expanding PDCP Downlink Buffer for Reserved Users ...................................... 38

3.14.3 Downlink Reserved Bandwidth for Reserved UE's I/B Traffic ............................. 39
3.15 TCP Optimization for Reserved Users ............................................................... 39
3.16 Fast L1 Synchronization for Reserved Users ..................................................... 39
3.17 CPC Strategy ..................................................................................................... 40
3.18 MR Collection Strategy ...................................................................................... 40
3.19 Forced Release of SRBs Carried on DL DCH/UL E-DCH .................................. 41
3.20 Reservation of User Plane Resource ................................................................. 41
3.20.1 Reservation of User Plane Resource for high-version UEs ................................ 41
3.20.2 Reservation of User Plane Resource for Reserved Users .................................. 42
4 Parameters....................................................................................................... 42
4.1 Parameters Related to Identify Reserved Users ................................................ 42
4.2 Parameters Related to Notify Node B of Reserved Users .................................. 44
4.3 Parameters Related to Obtain QoS Parameters for Reserved Users ................. 45
4.4 Parameters Related to Limit Rate of Non-Reserved Users ................................ 47
4.5 Parameters Related to Indicate Node B to Suppress Loads in a Serving Cell and
Neighboring Cells............................................................................................... 48
4.6 Parameters Related to Admission Control for Reserved Users .......................... 49
4.7 Parameters Related to Congestion Control ........................................................ 50
4.8 Parameters Related to Handover Control Policy for Reserved Users ................. 51
4.9 Parameters Related to DRBC Strategy for Reserved Users ............................... 52
4.10 Parameters Related to Power Control Strategy for Reserved Users .................. 55
4.11 Parameters Related to Reserved Frequency ..................................................... 87
4.12 Parameters Related to Paging ........................................................................... 91
4.13 Parameters Related to Overbooking .................................................................. 91
4.14 Parameters Related to TCP Optimization for Reserved Users ........................... 95
4.15 Parameters Related to Fast L1 Synchronization ................................................ 95
4.16 Parameters Related to CPC Strategy................................................................. 96
4.17 Parameters Related to MR Collection Strategy .................................................. 96
4.18 Parameters Related to Forced Release of SRBs Carried on DL DCH/UL E-DCH97
4.19 Parameters Related to Reservation of User Plane Resource ............................. 98
5 Related Counters and Alarms ........................................................................ 99
6 Engineering Guide .......................................................................................... 99

6.1 Application Scenario .......................................................................................... 99
6.2 Feature Activation Procedure ........................................................................... 100
6.3 Feature Validation Procedure........................................................................... 100
6.4 Feature Deactivation Procedure....................................................................... 100
6.5 Network Impact ................................................................................................ 100

7 Abbreviation .................................................................................................. 101
8 Reference Document..................................................................................... 102

FIGURES
Figure 3-1 Illustration of A Reserved User Matching .............................................................. 9
TABLES
Table 4-1 Identifying Reserved Users Parameter List ...........................................................42

Table 4-2 Notify Node B of Reserved Users Parameter List .................................................44
Table 4-3 Parameters Related to Obtain QoS Parameters for Reserved users Parameter List
.............................................................................................................................................45
Table 4-4 Limit Rate of Non-Reserved Users Parameter List ...............................................47
Table 4-5 Indicate Node B to Suppress Loads in a Serving Cell and Neighboring Cells
Parameter List ......................................................................................................................48
Table 4-6 Admission Control for Reserved Users Parameter List .........................................49
Table 4-7 Congestion Control Parameter List .......................................................................50
Table 4-8 Handover Control Policy for Reserved Users Parameter List ................................51
Table 4-9 DRBC Strategy for Reserved Users Parameter List..............................................52
Table 4-10 Power Control Strategy for Reserved Users Parameter List ...............................55
Table 4-11 Reserved Frequency Parameter List ..................................................................87
Table 4-12 Paging Parameter List ........................................................................................91
Table 4-13 Overbooking Parameter List ...............................................................................91
Table 4-14 TCP Optimization for Reserved Users Parameter List ........................................95
Table 4-15 Fast L1 Synchronization Parameter List .............................................................95
Table 4-16 CPC Parameter List ............................................................................................96
Table 4-17 MR Collection Strategy Parameter List ...............................................................96
Table 4-18 Forced Release of SRBs Carried on DL DCH/UL E-DCH Parameter List ...........97
Table 4-19 Reservation of User Plane Resource Parameter List ..........................................98
Table 6-1 Feature Validation Procedure .............................................................................100

1 Feature Attribute
RNC version: [ZXWR RNC V3.14.10.14/ZXUR 9000 V4.14.10.14]
Node B version: [ZXSDR V4.14.10]
Attribute: [Internal feature]
Involved NEs:
NE Name Related or Not Special Requirements
UE - None
Node B √ None
RNC √ None
iTC - None
MSC - None
MGW - None
SGSN - None
GGSN - None
HLR - None
√”: involved
“-”: not involved
2 Overview
2.1 Feature Introduction
To improve their service setup success rate, some specific users are defined as reserved
users, who can forcibly release other users, queue, and avoid being forcibly released by
other users.
The service priority (including the basic priority, application priority, HSPA scheduling
priority, and congestion scheduling priority) parameters of reserved users can be

configured independently of those of common users so that reserved users have higher
service priorities than common users do, and thus user experience is improved
Power control parameters can also be independently configured to allocate more power
to reserved users. For example, when the system calculates the initial transmit power on
the downlink dedicated channel, an offset value is added for reserved users to adjust the
initial power. Furthermore, the power control parameters, including the uplink initial SIR,
maximum SIR, minimum SIR, and target BLER can also be independently configured to
improve the service experience of reserved users.
2.2 License Control
This feature is not controlled by the license, and thus no authorization through NetNumen
is needed to enable the feature.
2.3 Correlation with Other Features
1. Required Features
ZWF21-04-001 Admission Control
ZWF21-04-002 Overload Control
ZWF21-04-004 Dynamic Radio Bearer Control
ZWF21-04-006 Code Resource Allocation
ZWF21-04-009 Power Control
ZWF21-04-010 Congestion Control
ZWF21-04-011 Load Balance
ZWF21-05-002 RAB QoS Parameter Mapping
ZWF22-01-006 Overbooking on Iub/Iur

ZWF23-01-A HSDPA Introduction Package
ZWF25-01-A HSUPA Introduction Package
ZWF26-01-A CPC Package
2. Mutually Exclusive Features
None
3. Affected Features
None
3 Technical Description
Because the reserved users are preferred on the resource allocation, there is an adverse
effect on the service experience of non-reserved users, mainly on admission control,
congestion control and load balance.
This feature involves the QoS, admission control, DRBC, power control, and overbooking
on Iub/Iur strategies. The details are described as below.
3.1 Identify Reserved Users
The reserved user identification function is enabled or disabled by the

URsvdUeGlobalPara.RsvdUeLstSwitch parameter.
If this parameter is set to “1: On”, the system needs to identify reserved users. Otherwise,
the system does not identify reserved users.
The reserved user identification strategy based on the IMSI is described as follows:
The IMSI carried by the Common ID message on the Iu interface or an RRC connection
request or the IMSI deduced from a TMSI or a P-TMSI is compared with the reserved
user information stored in the network to determine whether the UE is a reserved user.
Figure 3-1 shows the reserved user matching procedure.

Figure 3-1 Illustration of A Reserved User Matching
RRC Req:
IMSI/TMSI/P-TMSI
Common ID:
IMSI
Whether the UE is a
URsvdUeImsiList: reserved user or not
ImsiDgt
ImsiDgtNum
ImsiActiveInd
There is a slight difference in identifying reversed users on the SRNC and on the DRNC.
The details are described as below.
3.1.1 Identify Reversed Users on SRNC
The IMSI carried by a Common ID message on the Iu interface or an RRC connection

request (or the IMSI deduced from a TMSI or a P-TMSI) is compared with the reserved
user list (URsvdUeImsiList.imsiDgt) stored in the network to determine whether the IMSI
is in the list. As long as the high URsvdUeImsiList.imsiDgtNum (a number) bits are
matched, the UE is identified as a reserved user.
If a UE IMSI is in the reserved user list (URsvdUeImsiList) stored in the network and
URsvdUeImsiList.imsiActiveInd is set to “1: Active”, the UE is a reserved user. Otherwise,
the UE is a common user.
Note:
 Each record in the reserved user list refers to a UE (IMSI completely matched) or
UEs of the same type (some high IMSI digits matched).
 The reserved user list can contain up to 100 reserved users.
3.1.2 Identify Reversed Users on DRNC
Because the RNCs connected via the Iur interface may be provided by different vendors,
a parameter (UIurLink.RncFeatSwitchBit23) is set to determine whether a DRNC needs
to identify reserved users.

 If UIurLink.RncFeatSwitchBit23 is set to “1: Carrying Reserved User Indication over

Iur dedicated link”, the DRNC determines whether the corresponding UE is a
reserved user according to the IMSI transmitted over the Iur interface. The UE IMSI
is obtained from the IMSI carried by the RADIO LINK SETUP REQUEST/ RADIO
LINK ADDITION REQUEST message. The reserved user identification method
based on IMSI is the same as that described for SRNC. If the IMSI cannot be
obtained, the corresponding UE is treated as a common UE.
 Otherwise, the DRNC does not identify reserved users, and all users are treated as
common UEs.
3.2 Notify Node B of Reserved UEs
Once a reserved UE sets up a service in the cell, the RNC notifies the Node B through
RADIO LINK SETUP REQUEST/RADIO LINK RECONFIGURATION PREPARE to
perform some special processing, such as allocating high priority to reserved UEs, and
controlling the load of common users to guarantee the QoS of the reserved UEs.
For a radio link over Iur, whether to send the reserved UE indication to the Node B on
DRNC is also controlled by UIurLink.RncFeatSwitchBit23. If
UIurLink.RncFeatSwitchBit23 is set to “1: Carrying Reserved User Indication over Iur
dedicated link”, the information will be sent; otherwise, the information will not be sent.
3.3 Obtain QoS Parameters for Reserved Users
3.3.1 QoS Parameters for Reserved Users on SRNC
Reserved users can forcibly release other users, queue, and avoid being forcibly
released by other users.
To distinguish the QoS priorities of different reserved users, the QoS parameters can be
configured independently for each reserved user. Because CS services and PS services
have different resource usage priorities (for example, CS services have higher priority

than PS services do), the QoS parameters can also be configured independently for CS
services and PS services.
When a reserved user accesses the network, its QoS priority is obtained as follows.
Note:
 About the CS and PS service mentioned in the following section, it is identified for a
service on the SRNC through CN Domain Identity carried by the DIRECT
TRANSFER message, and identified for a service on DRNC through Traffic Class or
TrCH Source Statistics Descriptor carried by the RADIO LINK SETUP
REQUEST/RADIO LINK ADDITION REQUEST message over Iur.
 For the usage of the basic priority, HSPA scheduling priority, congestion scheduling
priority, and application priority described below, refer to ZTE UMTS QoS Feature
Guide.
 The SRB is always assigned with the highest priority, so there is no need to
distinguish reserved users and common users.
3.3.1.1 Obtain QoS Parameters for a CS Reserved Service on SRNC
If a reserved user establishes a CS service, the system matches the UE IMSI with a
record in URsvdUeImsiList, and obtains the QoS priority parameters based on the
following strategies:
 The basic priority (BasicPrio) of the CS service is obtained from

URsvdUeImsiList.CsBasicPrio.
 The HSPA scheduling priority (SPI) of the CS service is obtained from

URsvdUeImsiList.CsHspaSchPrio.
 The congestion scheduling priority (SchPrio) of the CS service is obtained from

URsvdUeImsiList.CsCgtSchPrio.
 The application priority (AppPri) of the CS service is obtained from

URsvdUeImsiList.CsAppPri.

If there are several records matched (exceptional configuration), take the first one
matched.
3.3.1.2 Obtain QoS Parameters for a PS Reserved Service on SRNC
If a reserved user establishes a PS service, the system matches the UE IMSI with a
record in URsvdUeImsiList, and obtains the QoS priority parameters based on the
following strategies:
 The basic priority (BasicPrio) of the PS service is obtained from

URsvdUeImsiList.PsBasicPrio.
 The HSPA scheduling priority (SPI) of the PS service is obtained from

URsvdUeImsiList.PsHspaSchPrio.
 The congestion scheduling priority (SchPrio) of the PS service is obtained from

URsvdUeImsiList.PsCgtSchPrio.
 The application priority (AppPri) of the PS service is obtained from

URsvdUeImsiList.PsAppPri.
Note:
If there are several records matched (abnormal configuration), take the first one
matched.
3.3.2 QoS Parameters for Reserved Users on DRNC
 The HSPA SPI priority of a reserved user in a DRNC
About the HSPA SPI for a reserved user in DRNC, the SPI carried on the Iur
interface is obtained just as that for a common user.
 The other priorities of a reserved user in a DRNC
About other self-defined priorities on the RNC, including the basic priority,
congestion scheduling priority, and application priority, the QoS priority is obtained
from the record of the reserved user list, which matches the UE IMSI. For the

obtaining method, refer to 3.3.1 QoS Parameters for Reserved Users on SRNC.
The IMSI is taken from that carried by RL Setup/RL Add message over Iur.
3.4 Limit Rate of Non-Reserved Users
If there is a reserved user in a cell or its intra-frequency neighboring cell, a method of

limiting rate of non-reserved users is performed to reserve resources for a reserved user.
If a reserved user in CELL_DCH state exists in the cell, a non-reserved PS user is not
allowed to upgrade the data rate (including all scenes for upward data rate, upgrading
rate triggered by RAB modify procedure is not allowed as well). The rejection reason of
upward PS rate is recoded externally as other causes (not counted in related counters),
and recorded internally as PS rate limited due to reserved users.
If a reserved user in CELL_DCH state exists in an intra-frequency neighboring cell, when

URsvdUeGlobalPara.rsvdUeEstNtfSwitch is set to “1: On”, its intra-frequency
neighboring cells are notified to suppress the load, that is the non-reserved PS users in
the cell are not allowed to upgrade data rates when there is a reserved user in its
neighboring cell (including all scenes for upward data rates, upgrading rate triggered by
RAB modify procedure is not allowed as well). The rejection reason for the upward PS
rate is recoded externally as other causes (not counted in related counters), and
recorded internally as PS rate limited due to reserved users.
If there is no reserved user in an intra-frequency neighboring cell, its neighboring cells

are notified to stop suppressing the load.
The selection of intra-frequency neighboring cells is the same as that described in 3.5
Indicate Node B to Suppress Loads in a Serving Cell and Intra-frequency Neighbors. It is
controlled by URsvdUeGlobalPara.rsvdUeEstNtfSwitch and
URsvdUeGlobalPara.rsvdUeNtfNbrPrio.

3.5 Indicate Node B to Suppress Loads in a Serving

Cell and Intra-frequency Neighbors
In order to allocate more resources to reserved users when reserved users exist in the
cell, and also to prepare the resources for intra-frequency soft handover, the Node Bs
controlling the serving cell and the neighboring cells with high measured priorities can be
notified to suppress the load, the details are described as follows.
When reserved users are in the cell and URsvdUeGlobalPara.RsvdUeEstNtfSwitch is set

to “On”, the Node Bs controlling the relevant cells are notified over Iub to suppress the
load of the common UEs. Here the relevant cells include: 1) the intra-frequency
neighboring cells for handover whose measured priorities are higher than or equal to
URsvdUeGlobalPara.RsvdUeNtfNbrPrio. 2) The current serving cell. For a dual cell pair,
the intra-frequency neighboring cells of the primary cell and the secondary one are all
notified.
When either of the following conditions is met, the Node Bs controlling the relevant cells
are notified to stop suppressing the common users and resume the normal process:
 There are no reserved users in this cell or the intra-frequency neighboring cells for
handover with measurement priorities higher or equal to
URsvdUeGlobalPara.RsvdUeNtfNbrPrio.
 URsvdUeGlobalPara.rsvdUeEstNtfSwitch is changed from On to Off.
The actions taken by Node Bs to suppress the load include reducing transmitted power
and decreasing the scheduling rate for HSPA.
Notes:
Only the neighboring cells in the local RNC are informed (the neighboring cells across
the Iur are not notified).
The measured priority of a neighboring cell is denoted with UUtranRelation.MeasPrio.

3.6 Admission Control Strategy for Reserved Users
With a purpose that a reserved user is not restricted by the resources in a cell and can
access the network at any time, there are some special strategies of admission control
for reserved users. Besides, the number of non-reserved users is also controlled to
reduce the resource consumption.
3.6.1 Loose Admission Control Strategy for Reserved Users
There is no resource admission control for a reserved user, meaning that a reserved user
is allowed to directly access to the network as follows.
 No admission control of soft resources: a reserved user is accepted in soft resource

judgment.
 No HSDPA, E-DCH or RRC connection number-based admission control
A reserved user is not limited by the maximum number of users on a HS-DSCH, on

an E-DCH or RRC connection.
 No CE-based admission control: A reserved user is accepted in CE resource

judgment.
 No admission control when blocked users with high service priority are involved
A blocked user with higher service priority will not affect the access of a reserved
user.
 No admission control of code occupation ratio
As long as the free code resources can be allocated to a reserved user, it is

accepted in code resource judgment.
3.6.2 Admission Control Strategy for Non-Reserved Users when Reserved

Users Exist
Once a reserved user in CELL_DCH state exists in the cell, the following UE
number-based admission control will be executed for non-reserved users:

 If the number of non-reserved PS users in CELL_DCH state exceeds

UUtranCellFDD.psNumThrd2 in the cell after a non-reserved user sets up a PS
service in a cell successfully, the setup of non-reserved PS service in CELL_DCH
state will be rejected by admission control. The rejection reason is recoded
externally as other causes of admission rejection (not counted in related counters),
and recorded internally as the number of PS services limited due to reserved users.
 If the number of non-reserved CS users exceeds UUtranCellFDD.csNumThrd2 in

the cell after a non-reserved user sets up a CS service in a cell successfully, the
setup of non-reserved CS service in CELL_DCH state will be rejected by admission
control. The rejection reason is recoded externally as other causes of admission
rejection (not counted in related counters), and recorded internally as the number
of CS services limited due to reserved users.
Once no reserved user in CELL_DCH state exists in the current cell and a reserved UE
in CELL_DCH state exists in the intra-frequency neighboring cells, the following UE
number-based admission control will be executed for non-reserved users:
 If the number of non-reserved PS users in CELL_DCH state exceeds

UCelInfoFDD.nbrPsNumThrd in the cell after a non-reserved user sets up a PS
service in the current cell successfully, the setup of non-reserved PS service in
CELL_DCH state will be rejected by admission control. The rejection reason is
recoded externally as other causes of admission rejection (not counted in related
counters), and recorded internally as the number of PS services limited due to
reserved users.
 If the number of non-reserved CS users exceeds UCelInfoFDD.nbrCsNumThrd in

the cell after a non-reserved user sets up a CS service in a cell successfully, the
setup of non-reserved CS service will be rejected by admission control. The
rejection reason is recoded externally as other causes of admission rejection (not
counted in related counters), and recorded internally as the number of CS services
limited due to reserved users.
Once no reserved user in CELL_DCH state exists in the current cell or in the
intra-frequency neighboring cells, the admission control of non-reserved user is not
affected.

Note:
When the feature of a reserved frequency is introduced, less non-reserved users are
allowed on the reserved frequency, indicating that there is a difference about the
thresholds for non-reserved users in a reserved frequency. For details, refer to 3.12.2
Admission Control Strategy.
3.7 Congestion Strategy
In order not to seriously affect the performance of reserved users by non-reserved users,
the number of non-reserved users is controlled. When a reserved user initiates a service,
a congestion control is triggered to reduce the affection to the reserved user if there are
excess non-reserved users online.
When there is a reserved user in the cell:
 If URsvdUeGlobalPara.dropForRsvdUeSwch is set to “1: On”, the non-reserved PS

services of the non-reserved users, the number of who exceeds
UUtranCellFDD.psNumThrd2, are released according to their scheduling priority
from low to high. And then downgrade all the non-reserved users’ rate to the lowest
DRBC level.
 If URsvdUeGlobalPara.dropForRsvdUeSwch is set to “0: Off”, downgrade all the

non-reserved users’ rate to the lowest DRBC level.
When there is no reserved user in the cell but there is a reserved user in the
intra-frequency neighboring cell, the actions are the same as there is a reserved user in
the cell, the difference is that the threshold for non-reserved is obtained from
UCelInfoFDD.nbrPsNumThrd.
Note:
When the function of a reserved frequency is introduced, the less non-reserved users are
set in the reserved frequency, meaning that the threshold for allowed non-reserved
differs and a forced handover can be performed for the non-reserved users exceeding
the threshold. For details, refer to 3.12.3 Congestion Strategy.

3.8 Handover Control Policy for Reserved Users
3.8.1 Intra-frequency Handover Parameters for Reserved Users
The intra-frequency handover parameters can be configured independently for reserved

users to control a better handover opportunity and also not to affect other common users.
Those parameters for the reserved uses are indexed by
UUtranCellFDD.ref2UIntraMeasProfile.
3.8.2 Relocate a Reserved user to DRNC
There is a service interruption during UE relocation to a DRNC, and thus the service
experience is affected. To provide better service quality over Iur, reserved users should
be seldomly relocated.
 If the URsvdUeGlobalPara.rsvdUeLstSwitch is “1: On”, when a reserved user needs

to be relocated to the DRNC, the timer URsvdUeImsiList.rsvCsReDelayTimer for
CS services or URsvdUeImsiList.rsvPsReDelayTimer for PS services starts
respectively depending on the service type. The relocation is triggered after the
timer expires.
 When the CS and PS services are concurrent, the timer for CS services
URsvdUeImsiList.rsvCsReDelayTimer is used for the reserved user.
 The other handover strategy over Iur interface for a reserved user is the same as
that for a common user.
3.9 DRBC Strategy for Reserved Users
3.9.1 Signaling Channel Allocation for Reserved Users
3.9.1.1 RRC Phase
For a reserved user, the RRC can be set up through the DCH/DCH 27.2 kbps signaling
to accelerate the connection setup procedure.

 If URsvdUeGlobalPara.RsvdUeRrcSrb272Swch is set to “0: Off”, reserved users

are not processed specially by the DRBC algorithm.
 If URsvdUeGlobalPara.RsvdUeRrcSrb272Swch is set to “1: On”, the RRC

connection is set up through the DCH/DCH 27.2k signaling. If the DCH/DCH 27.2
kbps signaling admission fails, the DCH/DCH 3.4 kbps signaling is tried then. If the
DCH/DCH 3.4 kbps signaling also fails, the channels for CELL_FACH are used.
3.9.1.2 Service Phase
To accelerate the service setup, HS-DSCH or E-DCH can be allocated to carry SRBs.
However, on the edge of the coverage, a call drop is easy to occur or the ratio of
successful RAB establishment decreases when SRBs are carried on HS-DSCH/E-DCH.
Thus, a special strategy of signaling channel allocation for reserved users during RAB or
other service setup phase is introduced as follows.
 If URsvdUeGlobalPara.rsvdUeSrbCfgSwch takes “0: Off”, reserved users are not

processed specially by the DRBC algorithm.
 If URsvdUeGlobalPara.rsvdUeSrbCfgSwch takes “1: On”, DCH/DCH channels are

allocates directly for SRBs.
Note:
If SRBs are carried on DCH/DCH, 2xSF2+2xSF4 cannot be used for E-DCH (SRBs
carried on HS-DSCH/E-DCH is required) and then the peak rate is affected.
3.9.2 Channel Transition for Reserved Users
To avoid impact on throughput and experience of a reserved user during channel

transition, an independent strategy for reserved users can be used. Thus a reserved user
can be kept in CELL_DCH state until the service is released.
The channel transition policy for reserved users is as follows:
 If URsvdUeGlobalPara.rsvdUeStateChgSwch takes “0: Off”, the transition from

CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH/IDLE is not allowed for
reserved users.

 If URsvdUeGlobalPara.rsvdUeStateChgSwch takes “1: On”, the switching from

CELL_DCH to CELL_FACH/CELL_PCH/URA_PCH/IDLE is allowed for reserved
users, that is, reserved users are not processed specially by the channel switching
policy.
3.9.3 E-TTI Policy for Reserved Users
HSUPA 2ms TTI can increase transmission bit rate by decreasing transmission delay of
Uu Interface, but the shorter TTI reduces the interleave protection in time domain. As a
result, the transmission of 2ms TTI E-DCH requires higher Tx power and better channel
quality than 10ms TTI, otherwise its performance may be even inferior to that of 10 ms
E-DCH TTI. For details, refer to ZTE UMTS Adaptive HSUPA TTI Feature Guide.
So there are two options for E-TTI allocation for reserved users. It is selected
depending on the actual network condition. Besides, the transition between 2 ms and 10
ms is controlled independently for reserved users.
3.9.3.1 Initial E-TTI Allocation for Reserved Users
The initial E-TTI allocation for reserved users is shown below.
 When URsvdUeGlobalPara.rsvdUeEttiCfgMeth takes “0: Off”, reserved users are

not processed specially by the channel switching policy.
 When URsvdUeGlobalPara.rsvdUeEttiCfgMeth takes “1: E-TTI is allocated based

on CPICH Ec/No, and 2ms/10ms TTI transfer is allowed”, if the UE and the cell both
support 2 ms E-TTI, and CPICH Ec/No is great than
URsvdUeGlobalPara.rsvdUeEttiEcNoThd and there are no multiple radio links, 2
ms E-TTI is allocated to the service; Otherwise, 10ms E-TTI is allocated.
Note:
If CPICH Ec/No cannot be acquired, it deems that the CPICH Ec/No is less than
URsvdUeGlobalPara.rsvdUeEttiEcNoThd.

 When URsvdUeGlobalPara.rsvdUeEttiCfgMeth takes “2: 2ms E-TTI is fixed

allocated, and 2ms/10ms TTI transfer isn't allowed”, 2 ms E-TTI is fixedly allocated
to the service, and the transition between 2 ms and 10 ms TTI is prohibited.
3.9.3.2 E-TTI Transition for Reserved Users
If URsvdUeGlobalPara.rsvdUeEttiCfgMeth takes “1: E-TTI is allocated based on

CPICH Ec/No, and 2ms/10ms TTI transfer is allowed”, the transition between 2ms and
10ms TTI is allowed later. Here the transition is not controlled by
ULogicalRnc.EttiTraffVolSwch.
 Transition from 10 ms E-TTI to 2 ms E-TTI triggered by throughput for reserved

users
If the followings are all met, the transition from 10 ms to 2 ms E-TTI for a reserved
user is triggered.
 The user is identified as a reversed user and

URsvdUeGlobalPara.rsvdUeEttiCfgMeth is set to “1: E-TTI is allocated based
on CPICH Ec/No, and 2ms/10ms TTI transfer is allowed”.
 The UE and all the cells in an active set support 2 ms E-TTI.
 CPICH Ec/No is greater than URsvdUeGlobalPara.rsvdUeEttiEcNoThd.
 The number of consecutive traffic measurement reports of 4A reported by the

user plane reaches Udrbc.eTtiEaThd.
 Transition from 2 ms E-TTI to 10 ms E-TTI triggered by throughput for reserved

users
If the followings are all met, the transition from 2 ms to 10 ms E-TTI for a reserved
user is triggered.
 The user is identified as a reversed user and

URsvdUeGlobalPara.rsvdUeEttiCfgMeth is set to “1: E-TTI is allocated based
on CPICH Ec/No, and 2ms/10ms TTI transfer is allowed”.

 The number of consecutive traffic measurement reports of 4B reported by the

user plane reaches UDrbc.eTtiEbThd.
3.10 Power Control for Reserved Users
In order to allocate more resources for reserved users, some power control parameters
related to service are set independently for reserved users. The following power control
parameters are obtained from URsvdUserSrvPc which is distinguished by service type of
a reserved user. The service type of a reserved user is obtained from
URsvdUserSrvPc.srvType, and then the values are obtained like a common user. If the
required power parameters cannot be obtained from the list, the parameters for golden
common users are taken. For the details about power control algorithm see ZTE UMTS
Power Control Feature Guide, ZTE UMTS Power Control Algorithm Enhancement
Feature Guide and ZTE UMTS HSUPA Introduction Feature Guide.
When the system calculates the initial transmit power on the downlink dedicated channel,
compared with the power of a common user, an offset value (rsvdUserPwrOffset) is
added for a reserved user. So the DPCH initial transmit power of a reserved user is
calculated as follows:
 Eb   
 N   
 0  req  Ptx ,CPICH     min 

Ptx ,init     min  max L  k1 
 Ptx ,total 
PG  Ec cpich   
 1  k  10 k2 
 N 0  + PowerOffset
+ rsvdUserPwrOffset
Where, rsvdUserPwrOffset is obtained from URsvdUeGlobalPara.rsvdUserPwrOffset.

For the values of other parameters and the detailed calculation, refer to ZTE UMTS
Power Control Feature Guide.
The parameters of power control of DCH downlink dedicated channel for reserved users
are listed as follows. Refer to ZTE UMTS Power Control Feature Guide for details.
Power Control Parameter Name Control Parameter
DPCH Maximum DL Power URsvdUserSrvPc.maxDlDpchPwr
DPCH Minimum DL Power URsvdUserSrvPc.minDlDpchPwr

The parameters of power control of DCH uplink dedicated channel are listed as follows.
Refer to ZTE UMTS Power Control Feature Guide for details.
DPCCH Pilot Field Eb/N0 URsvdUserSrvPc.dpcchPilotEbN0
The parameters of uplink inner loop power control of R99 in normal mode for reserved
users are listed as follows. See ZTE UMTS Power Control Feature Guide for details.
Maximum Allowed Uplink DPCH
URsvdUserSrvPc.maxUlDpchPwr
Transmission Power
The parameters of CRC-based outer loop power control for reserved users are listed as
follows. Refer to ZTE UMTS Power Control Feature Guide for details.
Uplink Initial SIR Target URsvdUserSrvPc.uLInitSIR
Maximum Uplink SIR Target URsvdUserSrvPc.uLMaxSIR
Minimum Uplink SIR Target URsvdUserSrvPc.uLMinSIR

Uplink Outer Loop PC SIR Target URsvdUserSrvPc.swchAdaptiveStep
Adaptive Down Step Size Switch
Uplink SIR Target Down Step Size URsvdUserSrvPc.ulSirTargDnStep
Uplink SIR Target Up Step Size URsvdUserSrvPc.ulSirTargUpStep

Uplink SIR Target Maximum Down
URsvdUserSrvPc.maxSirTargDnStep
Step Size
Uplink SIR Target Maximum Up Step
URsvdUserSrvPc.maxSirTargUpStep
Size
Error Transport Block Number
URsvdUserSrvPc.errorThresh
Threshold
Tolerance BLER Period URsvdUserSrvPc.blerAccpPeriod
The parameters of QE-based outer loop power control for reserved users are listed as


Uplink Outer Loop PC QE Switch
URsvdUserSrvPc.ulOlPcQESwchSil
For Silent Mode
Physical Channel BER Target For
URsvdUserSrvPc.qePhyBerTarSil
Silent Mode
The Number Threshold of Physical
Channel BER Less Than or Equal URsvdUserSrvPc.qeCntThres
BER Target
The parameters of BLER Target based outer loop power control for reserved users are
listed as follows. Refer to ZTE UMTS Power Control Algorithm Enhancement Feature
Guide for details.
BLER Target URsvdUserSrvPc.blerTarget

Uplink SIR Target Up Step Size for
URsvdUserSrvPc.ulSirStep
R99
The parameters of NHR Based HSUPA outer loop power control for reserved users are
listed as follows. Refer to ZTE UMTS HSUPA Introduction Feature Guide for details.
E-DCH HARQ Power Offset FDD URsvdUserSrvPc.edchHarqPOFdd

Threshold of HARQ Failure URsvdUserSrvPc.thrHarqFailTti10
Indication Number to Adjust SIR
Target Upward (10ms E-TTI)
Threshold of HARQ Failure URsvdUserSrvPc.thrHarqFailTti2
Indication Number to Adjust SIR
Target Upward (2ms E-TTI)
Threshold of Sample Number to URsvdUserSrvPc.upThrSampNumTti10
Adjust SIR Target Upward (10ms
E-TTI)
Threshold of Sample Number to URsvdUserSrvPc.upThrSampNumTti2
Adjust SIR Target Upward (2ms
E-TTI)
NHR Threshold to Adjust SIR Target URsvdUserSrvPc.nhrThrUpTti10
Upward (10ms E-TTI)

NHR Threshold to Adjust SIR Target URsvdUserSrvPc.nhrThrUpTti2

Upward (2ms E-TTI)
Threshold of Sample Number to URsvdUserSrvPc.dwThrSampNumTti10
Adjust SIR Target Downward (10ms
E-TTI)
Threshold of Sample Number to URsvdUserSrvPc.dwThrSampNumTti2
Adjust SIR Target Downward (2ms
E-TTI)
NHR Threshold to Adjust SIR Target URsvdUserSrvPc.nhrThrDownTti10
Downward (10ms E-TTI)
NHR Threshold to Adjust SIR Target URsvdUserSrvPc.nhrThrDownTti2
Downward (2ms E-TTI)
Uplink Initial SIR Target (10ms TTI URsvdUserSrvPc.ulInitSIRTti10
HSUPA)
Uplink Initial SIR Target (2ms TTI URsvdUserSrvPc.ulInitSIRTti2
HSUPA)
Maximum Uplink SIR Target (10ms URsvdUserSrvPc.ulMaxSIRTti10
TTI HSUPA)
Maximum Uplink SIR Target (2ms URsvdUserSrvPc.ulMaxSIRTti2
TTI HSUPA)
Minimum Uplink SIR Target (10ms URsvdUserSrvPc.ulMinSIRTti10
TTI HSUPA)
Minimum Uplink SIR Target (2ms URsvdUserSrvPc.ulMinSIRTti2
TTI HSUPA)
The parameters of NHR Target based HSUPA outer loop power control for reserved
users are listed as follows. Refer to ZTE UMTS HSUPA Introduction Feature Guide for
details.
Target Number of HARQ URsvdUserSrvPc.targetRetranNum
Retransmission
Uplink SIR Target Up Step Size for URsvdUserSrvPc.ulSirStepTti10
HSUPA (10ms E-TTI)
Uplink SIR Target Up Step Size for URsvdUserSrvPc.ulSirStepTti2
HSUPA (2ms E-TTI)
The Target Rate of FP HARQ URsvdUserSrvPc.fpTargErrorTti10
Retransmission Number Over the
Target (10ms E-TTI)


The Target Rate of FP HARQ URsvdUserSrvPc.fpTargErrorTti2
Retransmission Number Over the
Target (2ms E-TTI)
The parameters of downlink outer loop power control for reserved users are listed as
BLER Target URsvdUserSrvPc.blerTarget
The parameters of period BER based outer loop power control for reserved users are
listed as follows. See ZTE UMTS Power Control Algorithm Enhancement Feature Guide
for details.
The BER Threshold of Increasing
SIR Target in the Periodic URsvdUserSrvPc.berTargetUpThres
BER-based OLPC Algorithm
The BER Threshold of Decreasing
SIR Target in the Periodic URsvdUserSrvPc.berTargetDnThres
BER-based OLPC Algorithm
The Number Threshold of Trigging
URsvdUserSrvPc.berCntThres
SIRtarget Adjustment
The parameters of SIR target rapid convergence power control for reserved users are
listed as follows. Refer to ZTE UMTS Power Control Algorithm Enhancement Feature
Guide for details.
SIR Target Rapid Convergence
URsvdUserSrvPc.sirRapidConvSwi
Switch
Additional SIR Target Down Step
URsvdUserSrvPc.addiSIRDownStep
Size
Minimum Uplink SIR Target URsvdUserSrvPc.ulMinSIR
Uplink Initial SIR Target URsvdUserSrvPc.uLInitSIR

Initial Value for BLER Based SIR

URsvdUserSrvPc.initBlerSIR
Target
Initial Value for Additional SIR Target URsvdUserSrvPc.initSirAdd
Maximum Uplink SIR Target URsvdUserSrvPc.uLMaxSIR
Minimum Uplink SIR Target (10ms
URsvdUserSrvPc.ulMinSIRTti10
TTI HSUPA)
Uplink Initial SIR Target (10ms TTI
URsvdUserSrvPc.ulInitSIRTti10
HSUPA)

URsvdUserSrvPc.initBlerSIRTti10
Target (10ms TTI HSUPA)
Initial Value for Additional SIR

URsvdUserSrvPc.initSirAddTti10
Maximum Uplink SIR Target (10ms

URsvdUserSrvPc.ulMaxSIRTti10
TTI HSUPA)
Minimum Uplink SIR Target (2ms

URsvdUserSrvPc.ulMinSIRTti2
TTI HSUPA)
Uplink Initial SIR Target (2ms TTI

URsvdUserSrvPc.ulInitSIRTti2
HSUPA)
URsvdUserSrvPc.initBlerSIRTti2
Initial Value for Additional SIR Target
URsvdUserSrvPc.initSirAddTti2
(2ms TTI HSUPA)
Maximum Uplink SIR Target (2ms
URsvdUserSrvPc.ulMaxSIRTti2
TTI HSUPA)
3.11 Code Resource Allocation
The RNC shall not re-assign the DPCH/F-DPCH code resources of reserved users in
order to ensure the service quality.
If the DPCH/F-DPCH code belongs to a reserved user during the channelization code
re-assignment for downlink DPCH/F-DPCH in an HSDPA-capable cell (described in ZTE
UMTS HSDPA Introduction Feature Guide), or during the dynamic adjustment of the
number of E-AGCH/E-RGCH/E-HICH (described in ZTE UMTS HSUPA Introduction

Feature Guide), the RNC will not re-assign the DPCH/F-DPCH code resources of
reserved users.
In the feature of DCH/HSDPA fairness of code resources, the code allocation for the
upward PS data rate on DCH for a reserved user is that the DCH service is given the
priority to use the code resources, which is not controlled by UCHspa.hsVsR99CdPriInd.
3.12 Reserved Frequency
If there are several frequencies deployed in the network, a reserved frequency can be
introduced to improve the experience of reserved users, meaning that the reserved users
are served on a specific frequency. The frequencies for CS services and PS services can
be set separately. They can be served on the same frequency or different.
The feature is controlled by URsvdUeGlobalPara.rsvSpecFreqSwch. The parameters for

setting frequency are as follows.
 Reserved specific downlink carrier central frequency for PS services is configured

by URsvdUeGlobalPara.rsvDlArfcnforPsInd.
 Reserved specific downlink carrier central frequency for CS services is configured

by URsvdUeGlobalPara.rsvDlArfcnforCsInd.
All the users are camped on a cell through cell selection and reselection. With a reserved
frequency introduced, UEs classified as reserved users or common users will be
distributed with different frequencies. Three main strategies are involved in the
distribution process, which are load balance, admission control and congestion control.
The details are described below.
3.12.1 Load Balance
In order to avoid the inefficient utilization of resource, non-reserved users are also
allowed to access to the reserved frequency. Thus there is an influence on the load
balance of non-reserved users when a reserved frequency is set.

The strategies of load balance for reserved users and common users are described
respectively below.
When URsvdUeGlobalPara.rsvSpecFreqSwch is set to “1: True” and a reserved

frequency is set:
 A reserved user will be balanced to the cell with an overlapping or containment

relationship on the reserved frequency, meaning that CS reserved users are
absorbed by CS reserved frequency, PS reserved users are absorbed by PS
reserved frequency. For the CS+PS concurrent users, the access frequency is
selected if the access frequency is a reserved one; otherwise, the CS reserved
frequency is selected.
 A common user will be balanced to the non-reserved frequency when the load in the
reserved frequency is high, or be balanced to the reserved frequency when the load
in the reserved frequency is low.
3.12.1.1 Load Balance for Reserved Users

frequency is set, if there is a reserved frequency among the source cell and its
neighboring cells with an overlap or containment relationship, then the load balance is
performed for the reserved users during RRC (if a reserved user can be identified), RAB
or call holding phrase, meaning that the reserved frequency absorbs reserved users
according to the service attribute.
Otherwise, the original balance based on load and service attribute is performed.
Note:
A CS reserved user balanced to a reserved frequency is not controlled by

UPlBal.csBalSwch.
3.12.1.2 Load Balance for Non-Reserved Users

frequency is set, the RNC will judge whether to remove a candidate cell during a balance

according to whether there is a reserved user in the candidate cell or in its neighboring
cell, or according to the number of non-reserved users in the candidate cell of a reserved
frequency. Other processing remains unchanged. The details of load balance for a
non-reserved user are described as follows.
 When a candidate cell is a cell on the reserved frequency (denoted as reserved cell
in brief)and there is a reserved user on it, the candidate cell will be removed during
the balance for a non-reserved user if one of the following conditions is met:
 For the CS service, the number of non-reserved CS users in the candidate cell
is greater than or equal to min(UCelInfoFDD.csNumThrd1,
UUtranCellFDD.csNumThrd2).
 For the PS service, the number of non-reserved PS users in the candidate cell
is greater than or equal to min(UCelInfoFDD.psNumThrd1,
UUtranCellFDD.psNumThrd2).
 For the CS+PS concurrent service, the number of non-reserved CS users on

the candidate cell is greater than or equal to min(UCelInfoFDD.csNumThrd1,
UUtranCellFDD.csNumThrd2), or the number of non-reserved PS users on the
candidate cell is greater than or equal to min(UCelInfoFDD.psNumThrd1,
UUtranCellFDD.psNumThrd2).
 When the candidate cell is a non-reserved cell and there is a reserved user in it, the
candidate cell will be removed during the balance for a non-reserved user if one of
the following conditions is met:
is greater than or equal to UUtranCellFDD.csNumThrd2.
is greater than or equal to UUtranCellFDD.psNumThrd2.
 For the CS+PS simultaneous service, the number of non-reserved CS users in

the candidate cell is greater than or equal to UUtranCellFDD.csNumThrd2, or
the number of non-reserved PS users in the candidate cell is greater than or
equal to UUtranCellFDD.psNumThrd2.

 When there is no reserved user in the candidate cell which is a reserved cell, and
there is a reserved user in the candidate cell’s neighbor, if
URsvdUeGlobalPara.rsvdUeEstNtfSwitch is set to “1: On” and the candidate cell’s
measured priority is higher than or equal to
URsvdUeGlobalPara.RsvdUeNtfNbrPrio, the candidate cell will be removed if one
of the following conditions is met:
 For the CS service, the number of non-reserved CS users on the candidate

cell is greater than or equal to min(UCelInfoFDD.csNumThrd1,
UCelInfoFDD.nbrCsNumThrd).
 For the PS service, the number of non-reserved PS users on the candidate

cell is greater than or equal to min(UCelInfoFDD.psNumThrd1,
UCelInfoFDD.nbrPsNumThrd).
 For the CS+PS simultaneous service, the number of non-reserved CS users

on the candidate cell is greater than or equal to
min(UCelInfoFDD.csNumThrd1, UCelInfoFDD.nbrCsNumThrd), or the number
of non-reserved PS users on the candidate cell is greater than or equal to
min(UCelInfoFDD.psNumThrd1, UCelInfoFDD.nbrPsNumThrd).
 When there is no reserved user in the candidate cell which is a non-reserved cell,
and there is a reserved user in the candidate cell’s neighbor, if
URsvdUeGlobalPara.rsvdUeEstNtfSwitch is set to “1: On” and the candidate cell’s
measured priority is higher than or equal to
URsvdUeGlobalPara.RsvdUeNtfNbrPrio, the candidate cell will be removed if one
of the following conditions is met:
 For the CS service, the number of non-reserved CS users on the candidate

cell is greater than or equal to UCelInfoFDD.nbrCsNumThrd.
 For the PS service, the number of non-reserved PS users on the candidate cell
is greater than or equal to UCelInfoFDD.nbrPsNumThrd.
 For the CS+PS concurrent service, the number of non-reserved CS users on

the candidate cell is greater than or equal to UCelInfoFDD.nbrCsNumThrd, or

the number of non-reserved PS users on the candidate cell is greater than or

equal to UCelInfoFDD.nbrPsNumThrd.
 When the candidate cell is a reserved cell, and there is no reserved user in the
candidate cell and its neighboring cell, the candidate cell will be removed if one of
the following conditions is met:
is greater than or equal to UCelInfoFDD.csNumThrd1.
is greater than or equal to UCelInfoFDD.psNumThrd1.
 For the CS+PS simultaneous service, the number of non-reserved CS users in

the candidate cell is greater than or equal to UCelInfoFDD.csNumThrd1, or the
number of non-reserved PS users in the candidate cell is greater than or equal
to UCelInfoFDD.psNumThrd1.
Note:
 When the candidate cell is a dual cell pair, the number of non-reserved users in
each cell of the dual cell pair should be judged. If either of the dual cell pair cannot
satisfy the user number condition mentioned above, the dual cell pair is removed
out of the candidate cell list. The candidate cells are then sorted according to the
original load balance and service balance algorithm.
 The strategies mentioned above can be applied to non-reserved users during the
RRC, RAB and call holding phase.
 If a reserved user with SRBs only can be identified, it is performed according to

3.12.1.1 Load Balance for Reserved Users. If a reserved user can not be identified,
it is performed as a non-reserved user. The service is classified as CS, PS or Other
as the description in 3.1 Inter-frequency Load Balance section in ZTE UMTS Load
Balance Feature Guide. Whether the balance for CS service of non-reserved users
is performed is controlled by UrsvdUeGlobalPara.rrcNonRsvCsStra, and whether
the balance for PS service of non-reserved users is performed is controlled by
UrsvdUeGlobalPara.rrcNonRsvPsStra. The other services are set up in the source
cell and no balance is performed.

 If the candidate cell list is null, the source cell is selected to access.
3.12.2 Admission Control Strategy
The admission control strategy for reserved users is irrelevant to the reserved frequency,
and it is the same as that in 3.6 Admission Control Strategy.
To avoid the inefficient resource utilization, some non-reserved users are allowed to
access to the reserved cell, that is there is an admission control based on the number of
non-reserved users in the reserved cell.
There are two scenarios depending on the existence of reserved users to improve the
resource utilization during admission control:
 The number of non-reserved users can be adapted to a small threshold when there
is a reserved user.
 The number of non-reserved users can be adapted to a large threshold when there
is no reserved user.
3.12.2.1 Admission Strategy for Non-Reserved Users when There Is a Reserved

User in the Reserved Frequency
When there is a reserved user in a reserved cell, the admission control for non-reserved
users based on the user number of non-reserved users is as follows:
 If the number of PS online non-reserved users in CELL_DCH state is greater than

min(UUtranCellFDD.psNumThrd2, UCelInfoFDD.psNumThrd1) after a new
incoming non-reserved user is accepted, the PS service of new incoming
non-reserved user in CELL_DCH is not allowed to access. The admission rejection
cause is displayed externally as other cause of admission control (not counted in
the performance counters), and displayed internally as PS limited due to reserved
users.
 If the number of CS online non-reserved users is greater than

min(UUtranCellFDD.csNumThrd2, UCelInfoFDD.csNumThrd1) after a new
incoming non-reserved CS user is accepted, the CS service of new incoming

non-reserved user is not allowed to access. The admission rejection cause is

displayed externally as other cause of admission control (not counted in the
performance counters), and displayed internally as CS limited due to reserved
users.
When there is no reserved user in a reserved cell, and there is a reserved user in its
intra-frequency neighbor, the admission control for non-reserved users based on the
user number of non-reserved users is as follows:

min(UCelInfoFDD.nbrPsNumThrd, UCelInfoFDD.psNumThrd1) after a new
incoming non-reserved user is accepted, the PS service of new incoming
non-reserved user in CELL_DCH is not allowed to access. The admission rejection
cause is displayed externally as other cause of admission control (not counted in
the performance counters), and displayed internally as PS limited due to reserved
users.

min(UCelInfoFDD.nbrCsNumThrd, UCelInfoFDD.csNumThrd1) after a new
incoming non-reserved CS user is accepted, the CS service of new incoming
non-reserved user is not allowed to access. The admission rejection cause is
displayed externally as other cause of admission control (not counted in the
performance counters), and displayed internally as CS limited due to reserved
users.
3.12.2.2 Admission Strategy for Non-Reserved Users when There Is no Reserved

When there is no reserved user in a reserved cell and its intra-frequency neighbor, the
admission control for non-reserved users based on the user number of non-reserved
users is as follows:

UCelInfoFDD.psNumThrd1 after a new incoming non-reserved user is accepted,
the PS service of new incoming non-reserved user in CELL_DCH is not allowed to
access. The admission rejection cause is displayed externally as other cause of

admission control (not counted in the performance counters), displayed internally as

PS limited due to reserved users.

UCelInfoFDD.csNumThrd1 after a new incoming non-reserved CS user is accepted,
the CS service of new incoming non-reserved user is not allowed to access. The
admission rejection cause is displayed externally as other cause of admission
control (not counted in the performance counters), and displayed internally as CS
limited due to reserved users.
3.12.3 Congestion Strategy
After the reserved frequency is introduced, in order to improve the experience of

reserved users and also not to waste the resource of reserved frequency, there are 2
scenarios depending on the existence of reserved users during congestion control:
 A small number of non-reserved users are allowed to access to the reserved

frequency when there is a reserved user.
 A slightly large number of non-reserved users are allowed to access to the reserved
frequency when there is no reserved user.
3.12.3.1 Congestion Strategy for Non-Reserved Users when There is a Reserved

The upper limit for CS non-reserved users is min(UCelInfoFDD.csNumThrd1,

UUtranCellFDD.csNumThrd2) in a reserved frequency and that for PS non-reserved
users is min(UCelInfoFDD.psNumThrd1, UUtranCellFDD.psNumThrd2). The congestion
control strategy is described as follows.
 When URsvdUeGlobalPara.rsvForcedHoSwch for forced handover is set to “1:

True”, the non-reserved users exceeding the upper limit will be forcibly handed over
to another cell or removed the radio link in macro diversity if the cell is not the best
cell or not the HSDPA serving cell, in the order of the scheduling priority from low to
high. And then downgrade all the non-reserved PS users’ rate to the lowest DRBC
level.

Note:
 The forced handover or the removing of radio link in macro diversity for CS
services and PS services is performed respectively.
 The maximum number in each forced handover or removing radio link is

controlled by ULdCtrl.dlMaxForHoNum.
 For the CS+PS concurrent service, the number of PS non-reserved user and
that of CS non-reserved user are counted respectively, and as long as one
upper limit is reached, the forced handover is performed.
 If no non-reserved user for forced handover is selected or

URsvdUeGlobalPara.rsvForcedHoSwch is set to “0: False”, the following strategy is
performed:
 If URsvdUeGlobalPara.dropForRsvdUeSwch controlling the forced drop of

services is set to “1: On”, the forced drop of services is performed in the order
of scheduling priority. The number of remaining non-reserved users is equal to
min(UCelInfoFDD.psNumThrd1, UUtranCellFDD.psNumThrd2) after one drop
for the exceeding non-reserved users. And then downgrade all the PS
non-reserved users’ rate to the lowest DRBC level.
 If URsvdUeGlobalPara.dropForRsvdUeSwch controlling the forced drop of

services is set to “0: Off”, downgrade all the PS non-reserved users’ rate to the
lowest DRBC level.
3.12.3.2 Congestion Strategy for Non-Reserved Users when There is No Reserved

When there is no reserved user in the cell and the cell is not in the suppression state
(that is there is no reserved user in the neighboring cell or the function of suppressing
neighbor cell load is set off), in order to reserve sufficient resources for the reserved
users, the same strategy of forced handover or forced release as that for the existence of
reserved user in a reserved frequency is performed (see 3.12.3.13.12.3.1 Congestion
Strategy for Non-Reserved Users when There is a Reserved User in the Reserved
Frequency), but rate downgrade is not performed. Another difference is that the

maximum number of non-reserved CS users in the reserved cell is

UCelInfoFDD.csNumThrd1 and the maximum number of non-reserved PS users in the
reserved cell is UCelInfoFDD.psNumThrd1.
When there is no reserved user in the cell and the cell is in the suppression state (that is
there is a reserved user in the neighboring cell and the function of suppressing neighbor
cell load is set on), the same congestion strategy as that for the existence of reserved
user in a reserved frequency is performed (see 3.12.3.13.12.3.1 Congestion Strategy for
Non-Reserved Users when There is a Reserved User in the Reserved Frequency). The
difference is that the maximum number of non-reserved CS users in the reserved cell is
min(UCelInfoFDD.csNumThrd1, UCelInfoFDD.nbrCsNumThrd) and the maximum
number of non-reserved PS users in the reserved cell is min(UCelInfoFDD.psNumThrd1,
UCelInfoFDD.nbrPsNumThrd).
3.13 Paging
The CS paging of reserved users has the highest priority. When the PCH of a cell is
congested, the CS paging of reserved users is preferentially transmitted over the air
interface.
The number of paging messages transmitted over the air interface for the CS service of
reserved users can be configured independently. This function is enabled or disabled by
the URnluCfg.RnluResPara23 parameter. The higher value this parameter is set to, the
larger the maximum number of times that the CS paging type 1 messages of reserved
users are transmitted on the air interface is allowed (the maximum value cannot exceed
six). If this parameter is set to 0, the maximum number of times that a CS paging
message of a reserved user is transmitted over the air interface is the same as that of
common users.
3.14 Overbooking
Overbooking is implemented in an RNC to control the throughput within the transmission

bandwidth limit and maximize the transmission resource utilization. Because the number
of downlink high-speed services is increasing and the bandwidth is constrained

especially on Iub/Iur, overbooking control is mainly used for the Iub/Iur interface. In an
Iub/Iur overbooking control strategy, the UE downlink throughput of PS
streaming/interactive/background service depends on the QoS, throughput requirement,
UE radio capability, and transmission bandwidth. For the detailed overbooking control
strategy, refer to the ZTE UMTS Overbooking on Iux Feature Guide.
3.14.1 Overbooking Priority for Reserved Users
For a reserved user, the throughput requirement weight of PS services on the HS-DSCH
can be adjusted and more Iub/Iub transmission resources can be allocated for the
service to guarantee downlink PS data transmission. This function is enabled or disabled
by the URsvdUeGlobalPara.RsvOverBookPriSwch parameter.
 If URsvdUeGlobalPara.RsvOverBookPriSwch is set to “0: Off”, the method to

allocate the transmission resources for reserved users is the same as that for
common users when their PS service requirements are the same.
 If URsvdUeGlobalPara.RsvOverBookPriSwch is set to “1: On”, the higher value the

URsvdUeGlobalPara.RsvOverBookPri parameter is set to, the more transmission
resources are allocated by the RNC for the PS services carried on the HS-DSCH of
reserved users when the Iub and Iur downlink transmission resources are
congested and the throughput requirements of reserved users and those of
common users are the same, the downlink service rate of reserved users is given
priority.
3.14.2 Expanding PDCP Downlink Buffer for Reserved Users
To guarantee the QoS, the RNC sets Iu downlink data buffer for each PS service, which
stores downlink service data received from the SGSN/GGSN but not sends to the UE.
For a reserved user, the Iu downlink PS data buffer can be expanded independently.
This function is enabled or disabled by the URsvdUeGlobalPara.RsvExpPdcpBufSwch.
 If URsvdUeGlobalPara.RsvExpPdcpBufSwch is set to “0: Off”, the same Iu downlink

buffer size can be allocated to reserved users and common users for service with
the same QoS requirements.

 If URsvdUeGlobalPara.RsvExpPdcpBufSwch is set to “1: On”, the Iu downlink PS

data buffer size of reserved users can be expanded through the
URsvdUeGlobalPara.RsvPdcpDlBufLmt parameter to improve the QoS of reserved
users.
3.14.3 Downlink Reserved Bandwidth for Reserved UE's I/B Traffic
For the PS I/B service of a reserved user, the downlink reserved rate can be configured
independently. This function is enabled or disabled by the
URsvdUeGlobalPara.rsvDlResBwd parameter. The higher value the
URsvdUeGlobalPara.rsvDlResBwd parameter is set to, the more downlink transmission
bandwidth is reserved for the PS service carried on the HS-DSCH of reserved users.
When the Iub/Iur transmission resources are insufficient, reserved users are allowed to
get more downlink throughput, and the QoS of reserved users may be improved.
3.15 TCP Optimization for Reserved Users
To achieve a better service quality, the RNC controls reserved users’ TCP optimization
by URsvdUeGlobalPara.vipTcpOptSwch. If the value of this parameter is 1, TCP
optimization is enabled for only reversed users; otherwise, it is not for only reserved
users. If URsvdUeGlobalPara.vipTcpOptSwch is 1, the reserved users are always
permitted to use TCP optimization regardless of the TCP optimization license and Cell
level TCP optimization switches are enabled or not. For details about TCP optimization,
refer to ZTE UMTS TCP Service Accelerator Feature Guide.
3.16 Fast L1 Synchronization for Reserved Users
To improve the access of reserved users, the fast L1 synchronization function for
reserved user is introduced. It is controlled by parameter
URsvdUeGlobalPara.rsvdFastL1SyncSwch. If the value is 1, reserved users can use fast
L1 synchronization. For details about fast L1 synchronization, refer to ZTE UMTS
Connection Management Feature Guide.

3.17 CPC Strategy
There is a delay for the burst data transmission due to the use of DTX/DRX. In order to
improve the experience for reserved users, the parameters are introduced to control
related CPC feature enabled or not for reserved users seperately.
The parameter URsvdUeGlobalPara.rsvdLessCfgSwch to control HS-SCCH LESS and

the parameter URsvdUeGlobalPara.rsvdDtxdrxCfgSwch to control DTX/DRX for
reserved users are introduced.
 When URsvdUeGlobalPara.rsvdLessCfgSwch is “0: Off”, reserved users do not use

HS-SCCH LESS, otherwise the judgment of HS-SCCH LESS usage for reserved
users is the same as that for common users.
 When URsvdUeGlobalPara.rsvdDtxdrxCfgSwch is ‘’0: Off’, reserved users do not

use DTX/DRX, otherwise the judgment of DTX/DRX usage for reserved users is the
same as that for common users.
3.18 MR Collection Strategy
Collecting numerous MR data will increase the load of the control plane and degrade the
system performance though it is helpful to know the network information and then to
perform the network optimization. Thus there is a MR collection strategy for reserved
users.
MR collection strategy of reversed users is controlled by

URsvdUeGlobalPara.MrBarSwch.
 If URsvdUeGlobalPara.MrBarSwch is set to “1: On”, MR collection for reserved

users is forbidden.
 If URsvdUeGlobalPara.MrBarSwch is set to “0: Off”, MR collection for reserved

users is allowed.

3.19 Forced Release of SRBs Carried on DL DCH/UL

E-DCH
If the SRBs are carried on DL DCH/UL E-DCH, some types of UEs may be abnormal. To
solve the compatibility issue, SRBs can be released by setting
URsvdUeGlobalPara.onlySrbRrcRelSwch.
 When it is set to “1: On”, if there are only SRBs remained and carried on DL
DCH/UL E-DCH, the RRC will be forced to release.
 When it is set to “0: Off”, there is no special actions for SRBs carried on DL DCH/UL
E-DCH.
Note:
If the SRBs are carried on DL DCH/UL E-DCH and no other service is carried, the SRBs
will be reconfigured to DCH/DCH for a common user.
3.20 Reservation of User Plane Resource
If there is a resource reservation of RUB (Radio User Plane Board) for high protocol UEs
or reserved users, the high performance services can be initiated with a high probability.
However, reservation may cause a waste. With this feature enabled, when there is an
access failure, the user will access to other boards to improve the success access ratio.
3.20.1 Reservation of User Plane Resource for high-version UEs
If URsvdUeGlobalPara.rubRsvdSwch is set to “1: Switch On, RUP Reserved for

high-version UE”, and UUtranCellFDD.rubRsvdCellInd is set to “1: True” and the UE
release is higher than or equal to URsvdUeGlobalPara.rubRsvdNeedUEVer, the UE will
access a reserved radio user plane board.

3.20.2 Reservation of User Plane Resource for Reserved Users
If URsvdUeGlobalPara.rubRsvdSwch is set to “2: Switch On, RUP Reserved for VIP

User”, and UUtranCellFDD.rubRsvdCellInd is set to“1: True”, a reserved user accesses a
reserved radio user plane board.
4 Parameters
4.1 Parameters Related to Identify Reserved Users
Table 4-1 Identifying Reserved Users Parameter List
Reco
Defaul
Managed Value mmen
Logic Name Parameter Description Unit t
Object Range ded
Value
Value
Parameter Function: This

parameter indicates
whether the Reserved user
identification function is
enabled or not.
In the ZTE network, a
specific IMSI can be added
to the Reserved User List,
URsvdUeGlobal Switch for
for which special QoS 0: Off
Para.rsvdUeLst Reserved User NA 0: Off 1: On
parameters (for example, 1: On
Switch Identification
priority parameters, and
power control parameters)
can be set. This parameter
is used to control whether
to active the Reserved
User identification
function.
IMSI Digits This parameter indicates

URsvdUeImsiLi
Number in the number of IMSI digits 1..15 NA NA NA
st.imsiDgtNum
Reserved User in a reserved user list for

Reco
Defaul
Managed Value mmen
Object Range ded
Value
Value
List for User user identification, which is
Identification used in conjunction with
the ImsiDgt[15] in the
URsvdUeImsiList to
determine whether an IMSI
is in the reserved user list.
In the ZTE network,
special QoS parameters
(for example, priority and
power control) can be set
for IMSI in the reserved
user list.
This parameter indicates

the IMSI high-bit digits in a
reserved user list for user
identification, which is
used in conjunction with
IMSI High-bit the ImsiDgtNum in the
Digits in URsvdUeImsiList to
URsvdUeImsiLi
Reserved User determine whether an IMSI 0..9 NA NA NA
st.imsiDgt
List for User is in the reserved user list.
Identification In the ZTE network,
special QoS parameters
(for example, priority and
power control) can be set
for IMSI in the reserved
user list.

IMSI Active the IMSI activation
0: Not
Indication for indication for IMSIs in the
URsvdUeImsiLi Active 0: Not 1:
IMSI in reserved user list. Only the NA
st.imsiActiveInd 1: Active Active
Reserved User users with active IMSI in
Active
List the reserved user list are
reserved users.
UIurLink.RncFe Whether This parameter indicates 0:Not 0:Not 1:Carr

NA
atSwitchBit23 Support whether to carry reserved Carryin Carryi ying

Reco
Defaul
Managed Value mmen
Object Range ded
Value
Value
Reserved User user indication over the Iur g ng Reser
Notify dedicated link. The Reserv Reser ved
Indication over reserved user identification ed ved User
Iur in DRNC is based on this User User Indicat
parameter. Indicati Indicat ion
on ion over
over over Iur
Iur Iur dedica
dedicat dedica ted link
ed link ted link
1:Carr
ying
Reserv
ed
User
Indicati
on
over
Iur
dedicat
ed link
4.2 Parameters Related to Notify Node B of Reserved

Users
Table 4-2 Notify Node B of Reserved Users Parameter List
Recom
Managed Logic Value Default
Parameter Description Unit mende
Object Name Range Value
d Value
Whether This parameter indicates 0:Not 0:Not 1:Carryi
UIurLink.R
Support whether to carry reserved Carrying Carryin ng
ncFeatSwi NA
Reserved user indication over the Iur Reserved g Reserv
tchBit23
User Notify dedicated link. The reserved User Reserv ed User

Recom
d Value
Indication user identification in DRNC Indication ed User Indicati
over Iur is based on this parameter. over Iur Indicati on over
dedicated on over Iur
link Iur dedicat
1:Carrying dedicat ed link
Reserved ed link
User
Indication
over Iur
dedicated
link
4.3 Parameters Related to Obtain QoS Parameters for

Reserved Users
Table 4-3 Parameters Related to Obtain QoS Parameters for Reserved users Parameter
List
Recom
d Value
Basic
Priority of
URsvdUeI This parameter indicates the
CS Domain
msiList.cs basic priority of CS Domain 0..15 NA 15 15
for User in
BasicPrio service for the Reserved User.
Reserved
User List
HSPA
URsvdUeI Scheduling This parameter indicates the
msiList.cs Priority of HSPA Scheduling priority of CS
0..15 NA 15 15
HspaSchP CS Domain Domain service for the
rio for User in Reserved User.
Reserved

Recom
d Value
User List
Congestion
Scheduling
Priority of
msiList.cs Congestion Scheduling priority
CS Domain 0..15 NA 15 15
CgtSchPri of CS Domain service for the
for User in
o Reserved User.
Reserved
User List
Application
Priority of This parameter indicates the
URsvdUeI
CS Domain application priority of CS
msiList.cs 0..15 NA 15 15
for User in Domain service for Reserved
AppPri
Reserved User.
User List
Basic
Priority of
URsvdUeI PS Domain This parameter indicates the
msiList.ps Service for basic priority of PS Domain 0..15 NA 15 15
BasicPrio User in Service for the Reserved User.
Reserved
User List
HSPA
Scheduling
URsvdUeI Priority of This parameter indicates the
msiList.ps PS Domain HSPA Scheduling priority of PS
0..15 NA 15 15
HspaSchP Service for Domain Service for the
rio User in Reserved User.
Reserved
User List
Congestion
Scheduling
URsvdUeI Priority of This parameter indicates the
msiList.ps PS Domain Congestion Scheduling priority
0..15 NA 15 15
CgtSchPri Service for of PS Domain Service for the
o User in Reserved User.
Reserved
User List
URsvdUeI Application This parameter indicates the 0..15 NA 15 15

Recom
d Value
msiList.ps Priority of application priority of PS
AppPri PS Domain Domain Service for the
Service for Reserved User.
User in
Reserved
User List
4.4 Parameters Related to Limit Rate of Non-Reserved

Users
Table 4-4 Limit Rate of Non-Reserved Users Parameter List
Recom
d Value
whether to notify neighboring
cells when reserved users exist
URsvdUe Notification in the cell. If the parameter is
GlobalPar Switch for set to "1: On", the neighboring
0:Off
a.rsvdUeE Reserved cells are notified to lower the NA 1:On 1:On
1:On
stNtfSwitc User load and guarantee the
h Existing performance of reserved users.
If the parameter is set to "Off",
the neighboring cells are not
notified.
This parameter indicates the
Lowest
lowest priority of neighboring
Priority of
cells to be notified when
URsvdUe Neighbor
reserved users exist in the cell.
GlobalPar Cell
The priority here means the 0~2 NA 2 2
a.rsvdUeN Notified of
Measurement Priority
tfNbrPrio Reserved
(MeasPrio) of neighboring
User
cells. Only the neighboring cell
Existing
whose Measurement Priority is

Recom
d Value
equal to or higher than the
priority will be notified.
4.5 Parameters Related to Indicate Node B to Suppress

Loads in a Serving Cell and Neighboring Cells
Table 4-5 Indicate Node B to Suppress Loads in a Serving Cell and Neighboring Cells
Parameter List
Recom
d Value
whether to notify neighboring
cells when reserved users exist
URsvdUe Notification in the cell. If the parameter is
GlobalPar Switch for set to "1: On", the neighboring
0: Off
a.rsvdUeE Reserved cells are notified to lower the NA 1: On 1: On
1: On
stNtfSwitc User load and guarantee the
h Existing performance of reserved users.
If the parameter is set to "Off",
the neighboring cells are not
notified.
lowest priority of neighboring
Lowest
cells to be notified when
Priority of
URsvdUe Neighbor
The priority here means the
GlobalPar Cell
Measurement Priority 0~2 NA 2 2
a.rsvdUeN Notified of
(MeasPrio) of neighboring
tfNbrPrio Reserved
cells. Only the neighboring cell
User
whose Measurement Priority is
Existing
equal to or higher than the
priority will be notified.

4.6 Parameters Related to Admission Control for

Reserved Users
Table 4-6 Admission Control for Reserved Users Parameter List
Recom
d Value
maximum number of
non-reserved CS users in
Non-Reserv
CELL_DCH when reserved
ed CS User
users exist in the current cell.
UUtranCel Number
When the number of
lFDD.csN Threshold 0..255 NA 10 10
non-reserved users exceeds
umThrd2 When
the threshold, the RNC will
Reserved
forbid non-reserved users to
User Exists
access the cell of reserved
carrier and balance the users
to non-reserved carriers.
maximum number of
non-reserved PS users in
Non-Reserv CELL_DCH when reserved
ed PS User users exist in the current cell.
UUtranCel Number When the number of
lFDD.psN Threshold non-reserved users exceeds 0..255 NA 10 10
umThrd2 When the threshold, the RNC will
Reserved forbid non-reserved users to
User Exists access the cell of reserved
to non-reserved carriers, or
trigger the R99 service.
UCelInfoF Non-Reserv This parameter indicates the
DD.nbrCs ed CS User maximum number of 0..255 NA 20 20
NumThrd Number non-reserved CS users when

Recom
d Value
Threshold the current cell is a reserved
for neighboring cell. If no reserved
Reserved user exists in the current cell,
Neighborin and the number of
g Cells non-reserved users exceeds
access the current cell.
maximum number of
Non-Reserv
non-reserved PS users when
ed PS User
the current cell is a reserved
Number
UCelInfoF neighboring cell. If no reserved
Threshold
DD.nbrPs user exists in the current cell, 0..255 NA 20 20
for
NumThrd and the number of
Reserved
Neighborin
g Cells
4.7 Parameters Related to Congestion Control
Table 4-7 Congestion Control Parameter List
Recom
d Value
User Drop
URsvdUe whether the forced call drop
Switch
GlobalPar will be triggered when the
Triggered 0:Off
a.dropFor number of online non-reserved NA 1:On 1:On
by 1:On
RsvdUeS PS users in CELL_DCH state
Reserved
wch is larger than the threshold and
User
UUtranCel Non-Reserv This parameter indicates the
0..255 NA 10 10
lFDD.psN ed PS User maximum number of

Recom
d Value
umThrd2 Number non-reserved PS users in
Threshold CELL_DCH when reserved
When users exist in the current cell.
Reserved When the number of
User Exists non-reserved users exceeds
to non-reserved carriers, or
trigger the R99 service.
maximum number of
Non-Reserv
non-reserved PS users when
ed PS User
the current cell is a reserved
Number
UCelInfoF neighboring cell. If no reserved
Threshold
DD.nbrPs user exists in the current cell, 0..255 NA 20 20
for
NumThrd and the number of
Reserved
Neighborin
g Cells
4.8 Parameters Related to Handover Control Policy for

Reserved Users
Table 4-8 Handover Control Policy for Reserved Users Parameter List
Recom
d Value
Intra-freque This parameter indicates the 0..6553

NA NA NA
UUtranCel ncy profile ID of a set of 5

Recom
d Value
lFDD.ref2 Measureme intra-frequency measurement
UIntraMea nt Profile parameters of reserved users.
sProfile Identity for Each cell obtains the
Reserved intra-frequency measurement
User parameters of reserved users
in accordance with the profile
ID.
Timer of
Relocation
Delay for
msiList.rsv length of the relocation delay 0..6553
CS Service 100ms 30 30
CsReDela timer for the CS service of 5 step 1
of
yTimer reserved users.
Reserved
User
Timer of
Relocation
Delay for
msiList.rsv length of the relocation delay 0..6553
PS Service 100ms 0 0
PsReDela timer for the PS service of 5 step 1
of
yTimer reserved users.
Reserved
User
4.9 Parameters Related to DRBC Strategy for Reserved

Users
Table 4-9 DRBC Strategy for Reserved Users Parameter List
Recom
d Value
URsvdUe Switch of
GlobalPar the DCH
DCH 27.2 kbps Rate whether 0: Off
a.rsvdUeR 27.2kbps NA 0: Off 1: On
to be used for reserved User’s 1: On
rcSrb272S Rate
initial RRC Connection Setup.
wch whether to

Recom
d Value
be Used for
Reserved
Users'
Initial RRC
Connection
Setup
Switch of
SRB This parameter indicates the
Transport SRB transport channel
URsvdUe
Channel configuration method for
GlobalPar 0:off
Configurati reserved users. If the value is NA 0: Off 1: On
a.rsvdUeS 1:on
on Method "On", SRB will be carried on
rbCfgSwc
for DCH during RAB period for
h
Reserved reserved users.
Users
URsvdUe Reserved
GlobalPar User State 0: Off
switch of reserved user state NA 0: Off 1: On
a.rsvdUeS Transfer 1: On
transition.
tateChgS Switch
wch
0:off
1:E-TTI
is 1:E-TTI
allocate is
d based allocate
on d based
HSUPA TTI
CPICH on
URsvdUe Configurati
This parameter indicates the Ec/No, CPICH
GlobalPar on Method
HSUPA E-TTI configuration and NA 0:off Ec/No,a
a.rsvdUeE for
method for reserved users. 2ms/10 nd
ttiCfgMeth Reserved
ms TTI 2ms/10
Users
transfer ms TTI
is transfer
allowed is
2:2ms allowed
E-TTI is
fixed

Recom
d Value
allocate
d, and
2ms/10
ms TTI
transfer
isn't
allowed
Threshold
of Ec/No This parameter indicates the
Requested threshold of Ec/No requested
URsvdUe
when for HSUPA 2ms TTI. When
GlobalPar
HSUPA rsvdUeEttiCfgMeth is "1", only (-24..0)
a.rsvdUeE dB -7 -7
2ms TTI is when the CPICH Ec/No that dB, step
ttiEcNoTh
Configured UE reported is more than the 0.5dB
d
for threshold, 2ms TTI can be
Reserved used for reserved User.
Users
event 4A counter threshold for
Event 4Aswitching E-TTI from 10 ms to
Counter 2 ms. For the UE using E-DCH,
Threshold if the times of the measured
UDrbc.etti
for E-TTI user plane E-DCH throughput 1..255 NA 2 2
EaThd
Switching is larger than the 4A threshold
from 10ms exceeding the threshold
to 2ms indicated by this parameter and
10 ms E-TTI is used, UE's
E-TTI will be switched to 2 ms.
event 4B counter threshold for
Event 4B
switching E-TTI from 2 ms to
Counter
10 ms. For the UE using
Threshold
UDrbc.etti E-DCH, if the times of the
for E-TTI 1..255 NA 2 2
EbThd measured user plane E-DCH
Switching
throughput is less than the 4B
from 2ms to
threshold exceeding the
10ms
threshold indicated by this
parameter and 10ms E-TTI is

Recom
d Value
used, UE's E-TTI will be
switched to 10 ms.
4.10 Parameters Related to Power Control Strategy for

Reserved Users
Table 4-10 Power Control Strategy for Reserved Users Parameter List
Recom
d Value
sub-service type by numbering
each sub-service. The
numbers 0...5 are used for
URsvdUs
Sub-service signaling services, and 6...250 0..6553
erSrvPc.sr NA 0..249 NA
Type are used for single services. 4
vType
Odd numbers are used to
configure downlink services,
while even numbers are used
to configure uplink services.
DL DPCH DL DPCH initial power offset
Initial of a reserved subscriber
Power compared to that of a
URsvdUe
Offset for normal subscriber. When (-50..50
GlobalPar
Reserved the initial downlink power of )dB, dB 0dB 0dB
a.rsvdUse
User a reserved subscriber is step
rPwrOffset
Relative to calculated, the power offset 0.1dB
Normal must be added to the initial
User downlink power of a normal
subscriber.


maximum transmission power
of the downlink DPCH for
reserved subscribers. When
downlink inner loop power
control is performed, new
transmit power must be smaller
than or equal to the configured
DPCH Maximum DL Power. If
Configu Configu
the newly calculated transmit
red red
power is larger than the
URsvdUs receptiv receptiv
DPCH configured DPCH Maximum DL(-35..15
erSrvPc.m ely ely
Maximum Power, set it to be equal to the )dB, dB
axDlDpch accordi accordi
DL Power configured DPCH Maximum DLstep
Pwr ng to ng to
Power. 0.1dB
service service
This parameter is a 3-tuple.
type type
The elements in this array are
used in different load levels.
The corresponding relations
between the elements and load
levels are as follows:
Element 1: low load.
Element 2: medium load.
Element 3: high load.


minimum transmission power
of the downlink DPCH for
downlink inner loop power
control is performed, new
transmit power must be larger
than or equal to the configured
DPCH Minimum DL Power. If
Configu Configu
the newly calculated transmit
red red
power is lower than the
DPCH configured DPCH Minimum DL (-35..15
erSrvPc.m ely ely
Minimum Power, set it to be equal to the )dB, dB
inDlDpchP accordi accordi
DL Power configured DPCH Minimum DLstep
wr ng to ng to
Power. 0.1dB
service service
type type

quality factor of the uplink
DPCCH pilot field for reserved
subscribers, which is used for
calculating the uplink DPCCH Configu Configu
power offset upon new call red red
URsvdUs access. receptiv receptiv
DPCCH (-30..+3
erSrvPc.d This parameter is a 3-tuple. ely ely
Pilot Field 0)dB, dB
pcchPilotE The elements in this array are accordi accordi
Eb/N0 step
bN0 used in different load levels. ng to ng to
0.1dB
The corresponding relations service service
between the elements and load type type


maximum DPCH uplink
transmit power allowed for
uplink inner loop power control
is performed, the transmit
power newly calculated by a Configu Configu
Maximum UE may be larger than this red red
URsvdUs Allowed parameter. In this case, the UE receptiv receptiv
(-50..33
erSrvPc.m Uplink can only use this parameter for ely ely
)dBm, dBm
axUlDpch DPCH transmitting signals. accordi accordi
step
Pwr Transmissi This parameter is a 3-tuple. ng to ng to
1dBm
on Power The elements in this array are service service
used in different load levels. type type
R99 service initial SIR target of
the uplink physical channel for
reserved subscribers. The SIR
target is the criterion of uplink
Configu Configu
inner loop power control. The
red red
value affects the convergence
receptiv receptiv
URsvdUs Uplink speed of power control. (-8.2..17
ely ely
erSrvPc.u Initial SIR This parameter is a 3-tuple. .3)dB, dB
accordi accordi
LInitSIR Target The elements in this array are step
ng to ng to
used in different load levels. 0.1dB
service service
type type


maximum uplink target SIR of
R99 service for reserved
subscribers, which is used to
restrict the range of the SIR Configu Configu
target in outer loop power red red
control. receptiv receptiv
URsvdUs Maximum (-8.2..17
This parameter is a 3-tuple. ely ely
erSrvPc.u Uplink SIR .3)dB, dB
The elements in this array are accordi accordi
LMaxSIR Target step
used in different load levels. ng to ng to
0.1dB
minimum uplink target SIR of
R99 service for reserved
subscribers, which is used to
restrict the range of the SIR Configu Configu
target in outer loop power red red
URsvdUs Minimum (-8.2..17
erSrvPc.u Uplink SIR .3)dB, dB
LMinSIR Target step
0.1dB

URsvdUs This parameter indicates

erSrvPc.s whether the adaptive
wchAdapti downward adjustment step for
veStep the SIR target is used in uplink
Uplink outer loop power control for
Outer Loop reserved subscribers.
PC SIR This parameter is a 3-tuple.
0:Off
Target The elements in this array are NA [0, 0, 0] [0, 0, 0]
1:On
Adaptive used in different load levels.
Down Step The corresponding relations
Size Switch between the elements and load
URsvdUs This parameter indicates the
erSrvPc.ul step for decreasing the SIR
SirTargDn target of uplink outer loop
Step power control for reserved
subscribers. To restore
communication quality as soon
as possible when the
communication environment
worsens and to lower the Configu Configu
communication quality slowly red red
Uplink SIR (to make it more reliable) when receptiv receptiv
(0.1..0.5
Target the environment improves, the ely ely
)dB, dB
Down Step increasing and decreasing accordi accordi
step
Size steps are set asymmetrically ng to ng to
0.1dB
and separately. service service
This parameter is a 3-tuple. type type


erSrvPc.ul step for increasing the SIR
SirTargUp target of uplink outer loop
Step power control for reserved
subscribers. To restore
communication quality as soon
as possible when the
communication environment
worsens and to lower the Configu Configu
communication quality slowly red red
(to make it more reliable) when receptiv receptiv
Uplink SIR (0.1..0.5
the environment improves, the ely ely
Target Up )dB, dB
increasing and decreasing accordi accordi
Step Size step
steps are set asymmetrically ng to ng to
0.1dB
and separately. service service
This parameter is a 3-tuple. type type
maximum step for decreasing
the SIR target of uplink outer
loop power control for reserved Configu Configu
subscribers. red red
Uplink SIR
URsvdUs This parameter is a 3-tuple. receptiv receptiv
Target
erSrvPc.m The elements in this array are (0.1..1)d ely ely
Maximum dB
axSirTarg used in different load levels. B, step accordi accordi
Down Step
DnStep The corresponding relations 0.1dB ng to ng to
Size
between the elements and load service service
levels are as follows: type type


maximum step size for
increasing the uplink SIR
Configu Configu
target.
red red
Uplink SIR This parameter is a 3-tuple.
Target The elements in this array are
erSrvPc.m (0.1..1)d ely ely
Maximum used in different load levels. dB
axSirTarg B, step accordi accordi
Up Step The corresponding relations
UpStep 0.1dB ng to ng to
Size between the elements and load
service service
type type
error transport block number
threshold in outer loop power
control that uses the threshold
algorithm for reserved
subscribers. If the number of
Configu Configu
error blocks exceeds the
red red
Error threshold within a period, the
receptiv receptiv
URsvdUs Transport RNC increases the SIR target
(1..50)T ely ely
erSrvPc.er Block immediately. TBs
Bs, step accordi accordi
rorThresh Number This parameter is a 3-tuple.
1TB ng to ng to
Threshold The elements in this array are
service service
type type


error block tolerance period in
outer loop power control that
uses the threshold algorithm
for reserved subscribers. If the
tolerance period does not
expire but the number of error
blocks is larger than the error
block threshold, the
Signal-to-Interference Ratio Configu Configu
(SIR) target is increased. If the red red
URsvdUs tolerance period expires and receptiv receptiv
Tolerance (1..6553
erSrvPc.bl the number of error blocks is ely ely
BLER 5)TBs, TBs
erAccpPer smaller than the error block accordi accordi
Period step
iod threshold, the SIR target is ng to ng to
1TB
decreased. Otherwise, the SIR service service
target is not adjusted. type type


whether Quality Estimation
(QE) based Uplink Outer Loop
Power Control (OLPC) is
enabled or disabled for
reserved subscribers within the
valid time window when the FP
Configu Configu
mode is silent. If BLER-based
red red
Uplink OLPC is invalid, the OLPC that
Outer Loop is based on the BER of a
erSrvPc.ul 0: off ely ely
PC QE transmission channel can be NA
OlPcQES 1: on accordi accordi
Switch For used.
wchSil ng to ng to
Silent Mode This parameter is a 3-tuple.
service service
type type


BER target for a physical
channel within the valid time
window when the FP mode is
silent. The BER target is used
in outer loop power control
based on QE. If QESelector is
set to Selected and a
transmission channel BER is
available, the transmission
channel BER is the base for
QE of uplink data frames. If no
transport channel BER is
Configu Configu
available for the selected DCH,
red red
Physical the physical channel BER is
Channel used for QE. If QESelector is
erSrvPc.q (0..100) ely ely
BER Target set to "Non-selected", the %
ePhyBerT %, step accordi accordi
For Silent physical channel BER is used
arSil 0.1% ng to ng to
Mode for QE of uplink data frames. If
service service
mixed services are used, the
type type
minimum value in
QePhyBerTarSil of each
service is combined, and
signaling is excluded.


threshold for the number of
times that the physical channel
BER is less than or equal to the
BER target in the QE-based
uplink outer loop power control
algorithm for reserved
The subscribers. If the number of
Configu Configu
Number times that the physical channel
red red
Threshold BER is less than or equal to the
receptiv receptiv
URsvdUs of Physical BER target is greater than or
ely ely
erSrvPc.q Channel equals to the threshold, the 1..20 NA
accordi accordi
eCntThres BER Less RNC decreases the SIR target
ng to ng to
Than or immediately.
service service
Equal BER This parameter is a 3-tuple.
type type
Target The elements in this array are


Block Error Ratio (BLER) target
for reserved subscribers, and is
the benchmark for outer loop
power control. In the case of a
service with multiple subflows,
this parameter is applicable to
the first subflow.
The signaling value is Log10
(transport channel BLER
quality target). That is, the
physical value P in TS 25.331
is Log10 (actual value); the
scalar value D in TS 25.331 is Configu Configu
P*10; value configured in the red red
database = D+63; actual value receptiv receptiv
URsvdUs
BLER configured on the UI is 10^P, ely ely
erSrvPc.bl 0..1 NA
Target and is listed in exponential accordi accordi
erTarget
form, refer to the table in value ng to ng to
range. service service
Calculation method: type type
BLEREVAL=1: 63;
BLER=10.^
( (BLEREVAL-63)/10);
S=[BLEREVAL; BLER]'


adjustment step size of the
uplink SIR target in the R99
algorithm based on the BLER
target.
Uplink SIR This parameter is a 3-tuple.
URsvdUs (0.0..5.0 [0.3, [0.3,
Target Up The elements in this array are
erSrvPc.ul )dB, dB 0.3, 0.3,
Step Size used in different load levels.
SirStep step 0.3]dB 0.3]dB
for R99 The corresponding relations
0.1dB
erSrvPc.e E-DCH HARQ power offset for
dchHarqP reserved subscribers in FDD
OFdd mode. It is used to calculate
the quantized gain factor βed
Configu Configu
of E-DPDCH. For the detailed
red red
descriptions, refer to
E-DCH receptiv receptiv
TS25.214.
HARQ ely ely
This parameter is a 3-tuple. 0..6 NA
Power accordi accordi
Offset FDD ng to ng to
service service
type type


erSrvPc.th threshold of the HARQ failure
rHarqFailT number for increasing the SIR
ti10 target for reserved subscribers
when E-TTI is 10 ms. If the
Threshold number of HARQ failures
of HARQ exceeds the threshold within Configu Configu
Failure the time window, the RNC red red
Indication increases the SIR target. It is receptiv receptiv
Number to applicable to the services ely ely
0..255 NA
Adjust SIR carried on the E-DCH. accordi accordi
Target This parameter is a 3-tuple. ng to ng to
Upward The elements in this array are service service
(10ms used in different load levels. type type
E-TTI) The corresponding relations
erSrvPc.th threshold of the HARQ failure
rHarqFailT number for increasing the SIR
ti2 target for reserved subscribers
when E-TTI is 2 ms. If the
number of HARQ failures
Threshold
exceeds the threshold within Configu Configu
of HARQ
the time window, the RNC red red
Failure
increases the SIR target. It is receptiv receptiv
Indication
applicable to the services ely ely
Number to 0..255 NA
carried on the E-DCH. accordi accordi
Adjust SIR
This parameter is a 3-tuple. ng to ng to
Target
The elements in this array are service service
Upward
(2ms E-TTI)


erSrvPc.u minimum sample number for
pThrSamp increasing the SIR target for
NumTti10 reserved subscribers when
E-TTI is 10 ms. The SIR target
cannot be increased unless the
sample number is larger than
Threshold or equal to the threshold. When Configu Configu
of Sample HARQ retransmission red red
Number to (including when the number of receptiv receptiv
Adjust SIR HARQ retransmissions is 0) or ely ely
0..255 NA
Target failure is recorded once, a accordi accordi
Upward sample is obtained. ng to ng to
(10ms This parameter is a 3-tuple. service service
E-TTI) The elements in this array are type type


erSrvPc.u minimum sample number for
pThrSamp increasing the SIR target for
NumTti2 reserved subscribers when
cannot be increased unless the
sample number is larger than
or equal to the threshold. When Configu Configu
Threshold
HARQ retransmission red red
of Sample
(including when the number of receptiv receptiv
Number to
HARQ retransmissions is 0) or ely ely
Adjust SIR 0..255 NA
failure is recorded once, a accordi accordi
Target
sample is obtained. ng to ng to
Upward
This parameter is a 3-tuple. service service
(2ms E-TTI)
The elements in this array are type type


erSrvPc.n Number of HARQ
hrThrUpTt Retransmissions (NHR)
i10 threshold for increasing the
SIR target for reserved
subscribers when E-TTI is 10
ms. If the NHR is larger than Configu Configu
NHR
the threshold, the RNC red red
Threshold
increases the SIR target. It is receptiv receptiv
to Adjust (0..15),
SIR Target step NA
Upward 0.01
(10ms
E-TTI)
hrThrUpTt Retransmissions (NHR)
i2 threshold for increasing the
ms. If the NHR is larger than Configu Configu
NHR the threshold, the RNC red red
Threshold increases the SIR target. It is receptiv receptiv
(0..15),
to Adjust applicable to the services ely ely
step NA
SIR Target carried on the E-DCH. accordi accordi
0.01
Upward This parameter is a 3-tuple. ng to ng to
(2ms E-TTI) The elements in this array are service service


erSrvPc.d minimum sample number for
wThrSam decreasing the SIR target for
pNumTti1 reserved subscribers when
0 E-TTI is 10 ms. The SIR target
cannot be decreased unless
the sample number is larger
Threshold than or equal to the threshold. Configu Configu
of Sample When HARQ retransmission red red
Number to (including when the number of receptiv receptiv
Adjust SIR HARQ retransmissions is 0) or ely ely
0..255 NA
Target failure is recorded once, a accordi accordi
Downward sample is obtained. ng to ng to
(10ms This parameter is a 3-tuple. service service
E-TTI) The elements in this array are type type


erSrvPc.d minimum sample number for
wThrSam decreasing the SIR target for
pNumTti2 reserved subscribers when
cannot be decreased unless
the sample number is larger
than or equal to the threshold. Configu Configu
Threshold
When HARQ retransmission red red
of Sample
(including when the number of receptiv receptiv
Number to
HARQ retransmissions is 0) or ely ely
Adjust SIR 0..255 NA
failure is recorded once, a accordi accordi
Target
sample is obtained. ng to ng to
Downward
(2ms E-TTI)


hrThrDow Retransmissions (NHR)
nTti10 threshold for decreasing the
ms. When the NHR is smaller Configu Configu
NHR
than the threshold, the RNC red red
Threshold
decreases the SIR target. It is receptiv receptiv
to Adjust (0..15),
SIR Target step NA
Downward 0.01
(10ms
E-TTI)
hrThrDow Retransmissions (NHR)
nTti2 threshold for decreasing the
ms. If the NHR is smaller than Configu Configu
NHR the threshold, the RNC red red
Threshold decreases the SIR target. It is receptiv receptiv
(0..15),
to Adjust applicable to the services ely ely
step NA
SIR Target carried on the E-DCH. accordi accordi
0.01
Downward This parameter is a 3-tuple. ng to ng to
(2ms E-TTI) The elements in this array are service service


erSrvPc.ul 10 ms TTI HSUPA service
InitSIRTti1 initial SIR target of the uplink
0 physical channel for reserved
subscribers. The SIR target is
the criterion of uplink inner loop Configu Configu
power control. The value red red
Uplink
affects the convergence speed receptiv receptiv
Initial SIR (-8.2..17
of power control. ely ely
Target .3)dB, dB
This parameter is a 3-tuple. accordi accordi
(10ms TTI step
The elements in this array are ng to ng to
HSUPA) 0.1dB
used in different load levels. service service
The corresponding relations type type
URsvdUs This parameter indicates the 2
erSrvPc.ul ms TTI HSUPA service initial
InitSIRTti2 SIR target of the uplink
physical channel for reserved
subscribers. The SIR target is
the criterion of uplink inner loop Configu Configu
power control. The value red red
Uplink
affects the convergence speed receptiv receptiv
Initial SIR (-8.2..17
of power control. ely ely
Target (2ms .3)dB, dB
This parameter is a 3-tuple. accordi accordi
TTI step
The elements in this array are ng to ng to
HSUPA) 0.1dB
used in different load levels. service service
The corresponding relations type type


erSrvPc.ul maximum uplink target SIR of
MaxSIRTti 10 ms TTI HSUPA service for
10 reserved subscribers, which is
used to restrict the range of the Configu Configu
SIR target in outer loop power red red
Maximum
Uplink SIR (-8.2..17
Target .3)dB, dB
(10ms TTI step
HSUPA) 0.1dB
erSrvPc.ul maximum uplink target SIR of 2
MaxSIRTti ms TTI HSUPA service for
Maximum
TTI step
HSUPA) 0.1dB


erSrvPc.ul minimum uplink target SIR of
MinSIRTti 10 ms TTI HSUPA service for
Minimum
Target .3)dB, dB
(10ms TTI step
HSUPA) 0.1dB
erSrvPc.ul minimum uplink target SIR of 2
MinSIRTti ms TTI HSUPA service for
Minimum
TTI step
HSUPA) 0.1dB


erSrvPc.ta target number of HARQ
rgetRetran retransmissions.
Num This parameter is a 3-tuple.
Target
Number of
HARQ (0..15) NA [0, 0, 0] [0, 0, 0]
Retransmis
sion
erSrvPc.ul uplink SIR target up step size
SirStepTti of 10 ms E-TTI HSUPA
10 services in the HSUPA OLPC
algorithm based on the
Uplink SIR Number of HARQ
Target Up Retransmission (NHR) target.
(0.0..5.0 [0.3, [0.3,
Step Size This parameter is a 3-tuple.
)dB, dB 0.3, 0.3,
for HSUPAThe elements in this array are
step 0.3]dB 0.3]dB
(10ms used in different load levels.
0.1dB
E-TTI) The corresponding relations


erSrvPc.ul uplink SIR target up step size
SirStepTti of 2 ms E-TTI HSUPA services
2 in the HSUPA OLPC algorithm
based on the Number of HARQ
Uplink SIR Retransmission (NHR) target.
Target Up This parameter is a 3-tuple. (0.0..5.0 [0.1, [0.1,
Step Size The elements in this array are )dB, dB 0.1, 0.1,
for HSUPAused in different load levels. step 0.1]dB 0.1]dB
(2ms E-TTI) The corresponding relations 0.1dB
erSrvPc.fp target rate of 10 ms TTI FP
TargError HARQ retransmission number
Tti10 over the FP HARQ
The Target
retransmission number target
Rate of FP
in the HSUPA OLPC algorithm
HARQ
based on the Number of HARQ
Retransmis
Retransmission (NHR) target. [1%, [1%,
sion (0..100)
This parameter is a 3-tuple. % 1%, 1%,
Number %, step
The elements in this array are 1%] 1%]
Over the 0.1%
Target
(10ms
E-TTI)


erSrvPc.fp target rate of 2 ms TTI FP
TargError HARQ retransmission number
Tti2 over the FP HARQ
The Target retransmission number target
Rate of FP in the HSUPA OLPC algorithm
HARQ based on the Number of HARQ
Retransmis Retransmission (NHR) target. [10%, [10%,
(0..100)
sion This parameter is a 3-tuple. % 10%, 10%,
%, step
Number The elements in this array are 10%] 10%]
0.1%
Over the used in different load levels.
Target (2ms The corresponding relations
E-TTI) between the elements and load


erSrvPc.bl Block Error Ratio (BLER) target
erTarget for reserved subscribers, and is
the benchmark for outer loop
power control. In the case of a
service with multiple subflows,
this parameter is applicable to
the first subflow.
The signaling value is Log10
(transport channel BLER
quality target). That is, the
physical value P in TS 25.331
is Log10 (actual value); the
scalar value D in TS 25.331 is Configu Configu
P*10; value configured in the red red
database = D+63; actual value receptiv receptiv
BLER configured on the UI is 10^P, ely ely
0..1 NA
Target and is listed in exponential accordi accordi
form, refer to the table in value ng to ng to
range. service service
Calculation method: type type
BLEREVAL=1: 63;
BLER=10.^
( (BLEREVAL-63)/10);
S=[BLEREVAL; BLER]'


BER threshold for increasing
SIR target in the periodic
BER-based OLPC algorithm.
When the periodic BER-based
The BER
OLPC is effective, if the
Threshold Configu Configu
consecutive berCntThres
of red red
BERs are greater than this
URsvdUs Increasing receptiv receptiv
threshold, the SIR target
erSrvPc.b SIR Target (0..100) ely ely
should be increased. %
erTargetU in the %, step accordi accordi
pThres Periodic 0.1% ng to ng to
BER-based service service
OLPC type type
Algorithm
BER threshold for decreasing
SIR target in the periodic
BER-based OLPC algorithm.
When the periodic BER-based
The BER
OLPC is effective, if the
Threshold Configu Configu
consecutive berCntThres
of red red
BERs are lower than this
URsvdUs Decreasing receptiv receptiv
threshold, the SIR target
erSrvPc.b SIR Target (0..100) ely ely
should be decreased. %
erTargetD in the %, step accordi accordi
nThres Periodic 0.1% ng to ng to
BER-based service service
OLPC type type
Algorithm


threshold of the number of
times for triggering SIR target
The
adjustments. In the periodic
URsvdUs Number
BER based OLPC, if the
erSrvPc.b Threshold
continuous BERs satisfy the 1..20 NA 1 1
erCntThre of Trigging
SIR target increase (or
s SIRtarget
decrease) requirement, and
Adjustment
the BER number reaches the
threshold, the SIR target can
be increased (or decreased).
OLPC algorithm switch for
SIR-target rapid convergence
for reserved subscribers. If the
function is enabled, the initial
Configu Configu
SIR target can be rapidly
red red
decreased to the SIR target
URsvdUs SIR Target receptiv receptiv
based on the BLER.
erSrvPc.si Rapid 0: Off; ely ely
This parameter is a 3-tuple. NA
rRapidCo Convergen 1: On accordi accordi
nvSwi ce Switch ng to ng to
service service
type type
Configu Configu
red red
URsvdUs Additional receptiv receptiv
downward adjustment step
erSrvPc.a SIR Target (0~2)Db ely ely
size of the additional SIR dB
ddiSIRDo Down Step , step accordi accordi
target in the SIR-target rapid
wnStep Size 0.1dB ng to ng to
convergence algorithm.
service service
type type


initial value of the BLER-based
SIR target of R99 services for
reserved subscribers in the
Configu Configu
red red
algorithm.
Initial Value receptiv receptiv
URsvdUs This parameter is a 3-tuple. (-8.2..17
for BLER ely ely
erSrvPc.in The elements in this array are .3)dB, dB
Based SIR accordi accordi
itBlerSIR used in different load levels. step
Target ng to ng to
The corresponding relations 0.1dB
service service
type type
initial value of the additional
SIR target of R99 services for
reserved subscribers in the
Configu Configu
red red
algorithm.
Initial Value receptiv receptiv
URsvdUs This parameter is a 3-tuple. (-8.2..17
for ely ely
erSrvPc.in The elements in this array are .3)dB, dB
Additional accordi accordi
itSirAdd used in different load levels. step
SIR Target ng to ng to
service service
type type
Configu Configu
SIR target of 10 ms TTI HSUPA
Initial Value red red
services for reserved
URsvdUs for BLER receptiv receptiv
subscribers in the SIR-target (-8.2..17
erSrvPc.in Based SIR ely ely
rapid convergence algorithm. .3)dB, dB
itBlerSIRT Target accordi accordi
This parameter is a 3-tuple. step
ti10 (10ms TTI ng to ng to
The elements in this array are 0.1dB
HSUPA) service service
type type


initial value of the additional
Configu Configu
subscribers in the SIR-target
rapid convergence algorithm.
URsvdUs for receptiv receptiv
This parameter is a 3-tuple. (-8.2..17
erSrvPc.in Additional ely ely
The elements in this array are .3)dB, dB
itSirAddTti SIR Target accordi accordi
used in different load levels. step
10 (10ms TTI ng to ng to
type type
Configu Configu
subscribers in the SIR-target
rapid convergence algorithm.
URsvdUs for BLER receptiv receptiv
This parameter is a 3-tuple. (-8.2..17
erSrvPc.in Based SIR ely ely
The elements in this array are .3)dB, dB
itBlerSIRT Target (2ms accordi accordi
used in different load levels. step
ti2 TTI ng to ng to
type type
This parameter indicates the Configu Configu
Initial Value
initial value of the additional red red
URsvdUs for
SIR target of 2 ms TTI HSUPA(-8.2..17 receptiv receptiv
erSrvPc.in Additional
services for reserved .3)dB, dB ely ely
itSirAddTti SIR Target
subscribers in the SIR-target step accordi accordi
2 (2ms TTI
rapid convergence algorithm. 0.1dB ng to ng to
HSUPA)


4.11 Parameters Related to Reserved Frequency
Table 4-11 Reserved Frequency Parameter List
Recom
Managed Value Default
Logic Name Parameter Description Unit mende
Object Range Value
d Value
When VipSpecFreqSwch is
true, the RNC will balance
Reserved
URsvdUe reserved users to reserved
Specific 0:
GlobalPar carrier frequency. 0:
Frequency False; NA 1: True
a.rsvSpec Non-reserved user will be False;
Strategy 1: True
FreqSwch balanced to Non-reserved
Switch
carrier frequency in the
case of high load.
CS Reserved
URsvdUe
Specific
GlobalPar The parameter indicates the
Downlink 0..1638
a.rsvDlArf downlink central frequency NA 0 NA
Carrier Central 3
cnforCsIn of CS reserved carrier.
Frequency
d
Indicator
PS Reserved
URsvdUe
Specific
GlobalPar The parameter indicates the
Downlink 0..1638
a.rsvDlArf downlink central frequency NA 0 NA
Carrier Central 3
cnforPsIn of PS reserved carrier.
Frequency
d
Indicator
Non-Reserved This parameter indicates
UCelInfoF
CS User the maximum number of
DD.csNu 0..255 NA 255 10
Number non-reserved CS users in
mThrd1
Threshold for CELL_DCH allowed for the

Recom
Object Range Value
d Value
Reserved reserved carrier in the
Carrier current cell. When the
number of non-reserved
users exceeds the
threshold, the RNC will
carrier and balance the
users to non-reserved
carriers.
the maximum number of
non-reserved CS users in
Non-Reserved
users exist in the current
CS User
cell. When the number of
UUtranCel Number
non-reserved users
lFDD.csN Threshold 0..255 NA 10 10
exceeds the threshold, the
umThrd2 When
RNC will forbid
Reserved User
non-reserved users to
Exists
carriers.
CELL_DCH allowed for the
Non-Reserved reserved carrier in the
PS User current cell. When the
UCelInfoF
Number number of non-reserved
DD.psNu 0..255 NA 255 10
Threshold for users exceeds the
mThrd1
Reserved threshold, the RNC will
Carrier forbid non-reserved users to
carriers.

Recom
Object Range Value
d Value
Non-Reserved users exist in the current
PS User cell. When the number of
UUtranCel Number non-reserved users
lFDD.psN Threshold exceeds the threshold, the 0..255 NA 10 10
umThrd2 When RNC will forbid
Reserved User non-reserved users to
Exists access the cell of reserved
carriers, or trigger the R99
service.
non-reserved CS users
Non-Reserved
when the current cell is a
CS User
reserved neighboring cell. If
UCelInfoF Number
no reserved user exists in
DD.nbrCs Threshold for 0..255 NA 20 20
the current cell, and the
NumThrd Reserved
number of non-reserved
Neighboring
users exceeds the
Cells
Non-Reserved non-reserved PS users
PS User when the current cell is a
UCelInfoF Number reserved neighboring cell. If
DD.nbrPs Threshold for no reserved user exists in 0..255 NA 20 20
NumThrd Reserved the current cell, and the
Neighboring number of non-reserved
Cells users exceeds the

Recom
Object Range Value
d Value
This parameter is the switch
of non-reserved CS user
Non-Reserved load balance strategy in
URsvdUe CS User RRC procedure. If the
0: Off
GlobalPar Strategy switch is turned on, the NA 0: Off 1: On
1: ON
a.rrcNonR Switch in RRC reserved user load balance
svCsStra Procedure strategy for non-reserved
CS users is performed in
RRC procedure.
This parameter is the switch
of non-reserved PS user
Non-Reserved load balance strategy in
URsvdUe
PS User RRC procedure. If the
GlobalPar 0: Off
Strategy switch is turned on, the NA 0: Off 1: On
a.rrcNonR 1: On
Switch in RRC reserved user load balance
svPsStra
Procedure strategy for non-reserved
PS users is performed in
RRC procedure.
whether the forced
handover policy is enabled
URsvdUe Reserved User for the reserved carrier
0:
GlobalPar Forced frequency. When the switch
False; NA 0: False 1: True
a.rsvForce Handover is turned on, the RNC will
1: True
dHoSwch Switch hand over non-reserved
users that exceed the
threshold to a non-reserved
carrier.
Maximum This parameter indicates
Number of the maximum number of
Downlink UEs selected for forced
ULdCtrl.dl Forced handover or the maximum
MaxForHo Handover number of radio links 1..50 NA 3 3
Num Users or selected for deletion each
Deleted Radio time when the downlink
Links Every forced handover or link
Time deletion function is

Recom
Object Range Value
d Value
performed for load
reduction.
whether the forced call drop
URsvdUe will be triggered when the
User Drop
GlobalPar number of online
Switch 0:Off
a.dropFor non-reserved PS users in NA 1:On 1:On
Triggered by 1:On
RsvdUeS CELL_DCH state is larger
Reserved User
wch than the threshold and
reserved users exist in the
cell.
4.12 Parameters Related to Paging
Table 4-12 Paging Parameter List
Recom
d Value
URnluCfg. This parameter indicates the

Reserved
RnluResP maximum number of times for 0..6553
Parameter N/A 0 0
ara23 a reserved user’s or a diamond 5
23
user's paging type1 in a cell.
4.13 Parameters Related to Overbooking
Table 4-13 Overbooking Parameter List
Recom
d Value
RsvOverB Switch of The Iub/Iur overbooking
ookPriSwc Overbookin function of the RNC limits the 0:Off
h g priority downlink traffic of all UE 1:On N/A 0:Off 1:On

Recom
d Value
value for services from an SRNC to a
reserved NodeB (or DRNS) to ensure
users that the downlink traffic is not
heavier than the traffic that the
downlink bandwidth of the
transport network can support.
During overbooking, the
downlink traffic of a UE's PS
streaming, interactive, and
background services are
affected by multiple factors
such as QoS, traffic
requirements, radio resource
capacity, and transport network
bandwidth.
If this switch is turned on, a
reserved subscriber can make
more requests for PS
background services and the
transport network bandwidth
for the reserved subscriber
during lub/lur transport network
congestion can be increased.
The Iub/Iur overbooking

function of the RNC limits the
downlink traffic of all UE
services from an SRNC to a
NodeB (or DRNS) to ensure
that the downlink traffic is not
heavier than the traffic that the
downlink bandwidth of the
transport network can support.
Overbookin During overbooking, the
URsvdUe g priority downlink traffic of a UE's PS
GlobalPar value for streaming, interactive, and 1.0..10.
a.RsvOver reserved background services are 0
BookPri users affected by multiple factors step:0.1 N/A 2.0 2.0

Recom
d Value
requirements, radio resource
capacity, and transport network
bandwidth.
overbooking priority value for a
reserved subscriber's PS
services borne on HS-DSCHs.
Through this parameter, the
reserved subscriber can make
more requests for PS
background services and the
transport network bandwidth
for the reserved subscriber can
be increased.
To ensure the QoS, an RNC

allocates an IU downlink data
buffer for each PS service to
store the downlink service data
Switch of that is received from the SGSN
expanding or GGSN but is not sent to the
URsvdUe PDCP UE.
GlobalPar downlink If this switch is turned on, the
a.RsvExp buffer for PDCP buffer for the downlink
PdcpBufS reserved data of reserved subscribers’ 0:Off
wch Users PS services can be extended. 1:On N/A 0:Off 1:On
To ensure the QoS, an RNC

allocates an IU downlink data
buffer for each PS service to
store the downlink service data
Upper Limit that is received from the SGSN 0-20000 300000 300000
byte
of PDCP or GGSN but is not sent to the 000 0 0
URsvdUe downlink UE.
GlobalPar buffer for This parameter sets the upper
a.RsvPdc reserved limit of the IU downlink data
pDlBufLmt Users buffer for every PS service of a

Recom
d Value
reserved subscriber.
URsvdUe The Iub/Iur overbooking

GlobalPar function controls the downlink
a.rsvDlRe throughput of all UEs of a Node
sBwd B and ensures that the
downlink throughput does not
exceed the downlink bandwidth
of the Iub/Iur transport network.
In Iub/Iur overbooking, the
downlink throughput of a UE's
PS streaming service,
Downlink
interactive service, and
Reserved
background service is
Bandwidth
influenced by multiple factors,
for 0..6553 kbps 200 200
Reserved 5
requirement, radio resource
UE's I/B
capacity, transport network
Traffic
bandwidth, and the application
priority adjustment coefficient.
downlink transport network
bandwidth reserved for PS
services of reserved users. The
reserved bandwidth allows
more transport resources to be
allocated to the reserved UEs
for QoS improvement.

4.14 Parameters Related to TCP Optimization for

Reserved Users
Table 4-14 TCP Optimization for Reserved Users Parameter List
Recom
d Value

whether to enable the TCP
optimization for reserved
subscribers. For reserved
0:TCP
subscribers, when the Uplink
Optimiz
ACK Duplicating Switch or the
TCP ation for 0:TCP 0:TCP
URsvdUe Downlink Local Retransmission
Optimizatio all users Optimiz Optimiz
GlobalPar Switch or the Uplink ACK
n for the 1:TCP N/A ation for ation for
a.vipTcpO Splitting Switch, or the Local
reserved Optimiz all all
ptSwch TCP Agent Optimization
user ation for users users
Switch needs to be turned on,
reserve
you can turn on this TCP
d users
optimization switch for
reserved subscribers or turn on
the RNC-level TCP
optimization switch.
4.15 Parameters Related to Fast L1 Synchronization
Table 4-15 Fast L1 Synchronization Parameter List
Recom
d Value
URsvdUe Switch of
GlobalPar Faster L1
whether the faster L1 DCH 0: Off
a.rsvdFast DCH NA 0: Off 1: On
synchronization function is 1: On
L1SyncSw synchroniza
enabled for Reserved users.
ch tion

Recom
d Value
function for
Reserved
User
4.16 Parameters Related to CPC Strategy
Table 4-16 CPC Parameter List
Recom
d Value
URsvdUeGl HS-SCCH
obalPara.rsv Less Switch
whether reserved 0: Off
dLessCfgSw for NA 0: Off 0: Off
subscribers can use the 1: On
ch Reserved
HS-SCCH Less.
User
URsvdUeGl DTX/DRX This parameter indicates
obalPara.rsv Switch for whether reserved 0: Off
NA 0: Off 0: Off
dDtxdrxCfgS Reserved subscribers can use the 1: On
wch User DTX/DRX.
4.17 Parameters Related to MR Collection Strategy
Table 4-17 MR Collection Strategy Parameter List
Recom
d Value
URsvdUe This parameter indicates the
Switch of
GlobalPar switch for forbidding reserved
Reserved
a.MrBarS users from MR collection. 0: Off
User NA 0: Off 0: Off
wch If the switch is turned on, 1: On
Forbidden
reserved users are forbidden
MR
from MR collection.

Recom
d Value
If the switch is turned off,
reserved users are not
forbidden from MR collection.
4.18 Parameters Related to Forced Release of SRBs

Carried on DL DCH/UL E-DCH
Table 4-18 Forced Release of SRBs Carried on DL DCH/UL E-DCH Parameter List
Recom
d Value
URsvdUe This parameter is a functional

GlobalPar switch that controls whether to
a.onlySrb release a reserved user's RRC
RrcRelSw Switch of when the user has only
ch Reserved remaining SRB on D/E..
User If the switch is turned on, the
Released RNC will release a reserved 0: Off
NA 0: Off 1: On
RRC when user' RRC when it has only 1: On
the Only remaining SRB on D/E.
Remaining If the switch is turned off, the
SRB on D/E RNC will not release a
reserved user' RRC when it
has only remaining SRB on
D/E.

4.19 Parameters Related to Reservation of User Plane

Resource
Table 4-19 Reservation of User Plane Resource Parameter List
Recom
d Value
0:Off
1:Switc
h
This parameter indicates On ,RU
whether to reserve RUB P
resources for a specific UE. Reserve
URsvdUe If this parameter is set to 1 d for
GlobalPar Reserved (switched on), RUB resources high-ver
NA 0 2
a.rubRsvd RUB Switch are reserved for a specific UE. sion UE
Swch If this parameter is set to 0 2:Switc
(switched off), all UEs must h
obtain RUB resources from the On,RUP
resource pool. Reserve
d for
VIP
User
0:No
Reserve
d RUB
URsvdUe earliest protocol version of UEs
UE Version 1:R3
GlobalPar that are allowed to use
for 2:R4
a.rubRsvd reserved RUB resources. NA 0 0
Reserved 3:R5
NeedUEV UEs with this version or later
RUB 4:R6
er versions are allowed to use
5:R7
reserved RUB resources.
6:R8
7:R9
URsvdUe Cells for
whether the cell has reserved
GlobalPar Reserved 0:False
RUB resources. NA 0 1
a.rubRsvd RUB 1:True
If this cell has reserved RUB
CellInd Indicator
resources, the specific UE in

Recom
d Value
the cell will be required to
access the reserved RUB
board that provides sufficient
resources for the UE and
prevents the access of the
other UEs.
If this cell has no reserved RUB
resources, the accesses of all
UEs camped in this cell are
allowed.
5 Related Counters and Alarms

This feature has no related counter and alarm.
6 Engineering Guide
6.1 Application Scenario
If some sites bear heavy loads but capacity expansion is not required yet, this feature
can be activated to guarantee high-priority users’ experience. The IMSIs of some
important users are added to the reserved user list, so the service requirements of these
users can be met when network loads are high and resources are insufficient.
If the operator wants to improve the high-priority users’ experience, this feature can be
activated. After the IMSIs of high-priority users are added to the reserved user list,
network resources are preferentially allocated to reserved users.

6.2 Feature Activation Procedure
6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item Enhanced RAN Functionality
Preconditio
1.
ns
Test Steps 1.
Anticipative
1.
Result
6.4 Feature Deactivation Procedure
6.5 Network Impact
1. Equipment performance
Advantages:
Because more transmission resources are allocated to reserved users when the Iub/Iur
transmission network is congested, downlink data transmission of reserved users can be
guaranteed, and the QoS of reserved users is improved. When there are many service
requirements from reserved users, the RNC allocates more user-plane memory
resources to reserved users to improve their QoS.
Disadvantages:
More transmission resources are allocated to reserved users, which may affect common
user admission, and transmission resources may be wasted if the service requirements
of reserved users are not sufficient. When there are many service requirements from
reserved users, the RNC allocates more user-plane memory resources to reserved users.

If the user-plane memory resources are insufficient, the QoS of common users may be
affected.
2. Network KPI
Advantages:
Because reserved users have higher priority, they can obtain more resources when
network loads are high and resources are insufficient. Activating this feature can
guarantee the QoS of reserved users.
In addition, this feature can be activated and set independently for each user, so some
specific users’ experience can be improved accordingly.
Disadvantage
The QoS of common users may be affected.
7 Abbreviation
Abbreviations Full Characteristics
BLER Block Error Rate
CPC Continuous Packet Connectivity
CS Circuit Switch
DCH Dedicated Channel
DRBC Dynamic Radio Bearer Control
DRX Discontinuous Reception
DTX Discontinuous Transmission
E-TTI E-DCH Transmission Time Interval
HSDPA High Speed Downlink Packet Access
HSUPA High Speed Uplink Packet Access
IMSI International Mobile Subscriber Identification Number
MR Measurement Report

P-TMIS Packet Temporary Mobile Subscriber Identity
PS Packet Switch
Qos Quality of Service
R99 Release 1999
RAB Radio Access Bearer
RRC Radio Resource Control
RUB RNC User Plane Board
SIR Signal to Interference Ratio
SPI Schedule Priority Indicator
TCP Transmission Control Protocol
TMSI Temporary Mobile Subscriber Identity
8 Reference Document
[1] ZTE UMTS Qos Feature Guide Feature Guide
[2] ZTE UMTS Admission Control Feature Guide
[3] ZTE UMTS Power Control Feature Guide
[4] ZTE UMTS Power Control Algorithm Enhancement Feature Guide
[5] ZTE UMTS Power Control Algorithm Enhancement Feature Guide
[6] ZTE UMTS HSUPA Introduction Feature Guide
[7] ZTE UMTS Overbooking on Iux Feature Guide
[8] ZTE UMTS TCP Service Accelerator Feature Guide
[9] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Radio Parameter
Reference

[10] ZXWR RNC (V3.14.10.14) Radio Network Controller Radio Parameter Reference
[11] ZXUR 9000 UMTS (V4.14.10.14) Radio Network Controller Performance Counter
Reference
[12] ZXWR RNC (V4.14.10.14) Radio Network Controller Radio Parameter Reference

QOS Reserved User

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

QOS Reserved User

Uploaded by

Copyright:

Available Formats

Reserved User QoS

Reserved User QoS Guarantee

© 2015 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 6

3 Technical Description ....................................................................................... 8

ZTE Confidential Proprietary 2

3.14.2 Expanding PDCP Downlink Buffer for Reserved Users ...................................... 38

5 Related Counters and Alarms ........................................................................ 99

6 Engineering Guide .......................................................................................... 99

ZTE Confidential Proprietary 3

7 Abbreviation .................................................................................................. 101

8 Reference Document..................................................................................... 102

ZTE Confidential Proprietary 4

Figure 3-1 Illustration of A Reserved User Matching .............................................................. 9

Table 4-1 Identifying Reserved Users Parameter List ...........................................................42

ZTE Confidential Proprietary 5

Node B version: [ZXSDR V4.14.10]

Attribute: [Internal feature]

NE Name Related or Not Special Requirements

2.1 Feature Introduction

ZTE Confidential Proprietary 6

2.2 License Control

2.3 Correlation with Other Features

ZWF21-04-001 Admission Control

ZWF21-04-002 Overload Control

ZWF21-04-004 Dynamic Radio Bearer Control

ZWF21-04-006 Code Resource Allocation

ZWF21-04-009 Power Control

ZWF21-04-010 Congestion Control

ZWF21-04-011 Load Balance

ZWF21-05-002 RAB QoS Parameter Mapping

ZWF22-01-006 Overbooking on Iub/Iur

ZTE Confidential Proprietary 7

ZWF23-01-A HSDPA Introduction Package

ZWF25-01-A HSUPA Introduction Package

ZWF26-01-A CPC Package

2. Mutually Exclusive Features

3.1 Identify Reserved Users

The reserved user identification function is enabled or disabled by the

ZTE Confidential Proprietary 8

Figure 3-1 Illustration of A Reserved User Matching

3.1.1 Identify Reversed Users on SRNC

The IMSI carried by a Common ID message on the Iu interface or an RRC connection

 The reserved user list can contain up to 100 reserved users.

3.1.2 Identify Reversed Users on DRNC

ZTE Confidential Proprietary 9

 If UIurLink.RncFeatSwitchBit23 is set to “1: Carrying Reserved User Indication over

3.2 Notify Node B of Reserved UEs

3.3 Obtain QoS Parameters for Reserved Users

3.3.1 QoS Parameters for Reserved Users on SRNC

ZTE Confidential Proprietary 10

3.3.1.1 Obtain QoS Parameters for a CS Reserved Service on SRNC

 The basic priority (BasicPrio) of the CS service is obtained from

 The HSPA scheduling priority (SPI) of the CS service is obtained from

 The congestion scheduling priority (SchPrio) of the CS service is obtained from

 The application priority (AppPri) of the CS service is obtained from

ZTE Confidential Proprietary 11

3.3.1.2 Obtain QoS Parameters for a PS Reserved Service on SRNC

 The basic priority (BasicPrio) of the PS service is obtained from

 The HSPA scheduling priority (SPI) of the PS service is obtained from

 The congestion scheduling priority (SchPrio) of the PS service is obtained from

 The application priority (AppPri) of the PS service is obtained from

3.3.2 QoS Parameters for Reserved Users on DRNC