ZTE UMTS QoS Feature Guide - V8.5 - 201312 PDF

QoS Feature Guide
WCDMA RAN
QoS Feature Guide
QoS Feature Guide

Version Date Author Reviewer Revision History
Updated the following parameter descriptions:

Section 5.2.1.2 DCH Uplink Nominal Bit Rate
V7.5 2012-9-25 Sha Xiubin Jiang Qingsong
Section 5.2.1.3 DCH Downlink Nominal Bit
Rate
Added For HSPA CS Domain Conversational
speech services, it indicates the MBR. For
HSPA PS Domain Conversational speech
services, it indicates the MBR in the stable
V8.0 2012-11-27 Sha Xiubin Song Qiong
state. For HSPA Conversational non-speech
services, it indicates the GBR; in the
description for data rate R value in Section
3.1.7 AP Configuration.
V8.5 2013-12-10 Zhang Min Song Qiong Added feature IDs.
2014 ZTE Corporation. All rights reserved.

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

QoS Feature Guide
TABLE OF CONTENTS
1 Feature Attributes.............................................................................................. 5
2 Overview ............................................................................................................ 5
2.1 ZWF21-05-002 RAB QoS Parameters Mapping ................................................... 6
2.2 ZWF21-05-003 Differentiated Service .................................................................. 6
2.3 ZWF23-05-001 QoS Mapping for HSDPA Service ............................................... 7
2.4 ZWF25-05-001 QoS Mapping for HSUPA Service ............................................... 8
3 Technical Descriptions ..................................................................................... 8

3.1 Functions of Priorities .......................................................................................... 8
3.2 Types of Priorities ................................................................................................ 9
3.3 Configuration Scheme of Priorities ..................................................................... 10
3.4 Configuration of Logical Channel Priority ........................................................... 12
3.5 BP Configuration ................................................................................................ 13
3.6 SP Configuration ................................................................................................ 15
3.7 AP Configuration ................................................................................................ 17
3.7.1 Congestion Control Priority ................................................................................ 18
3.7.2 Load Control Priority .......................................................................................... 21
3.8 The Application of QoS Parameters of Iu Interface ............................................ 23
3.9 MBR Controlling in RNC .................................................................................... 24
4 Radio QoS Differentiated Strategy ................................................................. 25

4.1 QoS Differentiation of Admission Control ........................................................... 25
4.2 QoS Differentiation of Congestion Control ......................................................... 26
4.2.1 Application of QoS Application in Resource Occupation .................................... 26
4.2.2 Application of QoS in Forced Release................................................................ 27
4.2.3 Application of QoS in Rate Decrease ................................................................. 29
4.2.4 Application of QoS in Admission Scheduling ...................................................... 30
4.3 QoS Differentiation of Load Control ................................................................... 31
4.4 QoS Differentiation of HSDPA service ............................................................... 33
4.5 QoS Differentiation of HSUPA service ............................................................... 33
5 Parameters and Configurations ..................................................................... 33

5.1 Parameter List ................................................................................................... 33
5.1.1 Information about Priority and Rate Segments ................................................... 33
5.1.2 BP Configuration ................................................................................................ 34
5.1.3 SP Configuration ................................................................................................ 34
5.1.4 AP Configuration ................................................................................................ 34
5.1.5 MBR Controlling in RNC .................................................................................... 35

QoS Feature Guide
5.2 Parameter Configurations .................................................................................. 35

5.2.1 Information about Priority and Rate Segments ................................................... 35
5.2.2 BP Configuration ................................................................................................ 38
5.2.3 SP Configuration ................................................................................................ 40
5.2.4 AP Configuration ................................................................................................ 43
5.2.5 MBR Controlling in RNC .................................................................................... 47
6 Counters And Alarms ...................................................................................... 48

6.1 Counter List ....................................................................................................... 48
6.2 Alarm List ........................................................................................................... 48
7 Glossary ........................................................................................................... 48

QoS Feature Guide
FIGURES
Figure 3-1 Priority Mapping Scheme ..................................................................................11
TABLES
Table 3-1 Logical Channel Priority Mapping .......................................................................13

Table 3-2 BasicPrio Mapping Example ..............................................................................15

QoS Feature Guide
1 Feature Attributes
System version: [RNC V3.12.10/V4.12.10, OMMR V12.12.41, Node B V4.12.10, OMMB
V12.12.40]
Attribute: [Mandatory]
Involved NEs:
UE NodeB RNC MSCS MGW SGSN GGSN HLR
- - -
Note:
*-: Not involved.
*: >Involved.
Dependency: [None]
Mutual exclusion: [None]
Note: [None].
2 Overview
Besides the more complicated technologies employed in the physical layer of the air
interface for higher spectrum utilization in 3G systems, the typical features of the
end-to-end (E2E) QoS structure are clearly defined in the UMTS. The UMTS system
takes a wide range of the existing and future multimedia services into account. To ensure
the QoS of these services, the UMTS system defines many QoS assurance measures.
Therefore, the system makes full use of its own technical strengths and provides
customers with differentiated services to enhance their satisfaction and increase the
operation income.
With the implementation of the E2E QoS mechanism, subscribers will be satisfied with
the services provided by the mobile network, and the UMTS operators can use resources
more efficiently to develop emerging mobile content services with high profits. The QoS
plays a very important role in utilizing radio resources of the UMTS system efficiently and
maximizing the profits of operators.

QoS Feature Guide
The implementation of QoS brings the following benefits for subscribers: The
differentiated user classes ensure that the high-level subscribers obtain better services
than the low-level subscribers. The differentiated applications of different services ensure
that the services with high experience requirements are processed in preference. For
real-time applications of services, each network element processes related data as soon
as possible. For non-real-time applications of services, the related data is processed
later.
The implementation of QoS brings the following benefits to network operators:
Benefits growth of operation cost: The QoS mechanism offers effective measures for
network operators to optimize network resources; therefore the operators are able to
satisfy the requirements of more end users with minimum network resources.
New income growth points: The QoS mechanism enables the network operators to offer
more value-added services and allows subscribers to use complex applications (usually
with relatively high QoS requirements). As a result, the preferential treatments are
offered to high-level subscribers to show the difference from other networks and to
realize the customization of services, and the users loyalty will be enhanced by
improving the satisfaction of subscribers.
In a word, the purpose of implementation of the QoS assurance mechanism is to offer

different service resources and quality assurance according to different service features
and users requirements, realizing different user experiences.
2.1 ZWF21-05-002 RAB QoS Parameters Mapping
The RNC maps the RAB QoS parameters from the CN to the priority used in the UTRAN,
and performs admission control, congestion control, overload control and packet
scheduling according to the priority mapped.
2.2 ZWF21-05-003 Differentiated Service
According to traffic class (Traffic Class and THP) and ARP, ZTE defines the BP (Basic
Priority), SP (Scheduling Priority), and AP (Application Priority) for intra-RNC radio

QoS Feature Guide
resource management, which does not involve the transmission between NEs.
A priority is a reference for inter-UE resource allocation when radio resources are
insufficient and congestion is about to happen. Sufficient radio resources ensure enough
radio resources available for each subscriber.
The BP reflects the priorities of users and services. A user or service with a higher priority
may obtain better services when equal radio resources are available.
The BP reflects the priorities of users and services rather than the occupation of
resources by users or services. The higher the data rate is, the more the occupied
resources are. In addition, the system should make a final strategic choice between the
priority and the occupation of system resources. As a result, the ZTE RRM module
designs an AP mapping table.
The SP and AP are obtained based on the BP.
The SP, based on the BP and bearer type, indicates comprehensive relationships
between priorities and bearer types. It is used for forced release and queue scheduling.
The AP mapping table, which is a three-dimension table based on the BP, bearer type
and real-time rate, indicates the strategic balance between the priority and resource
occupation, and embodies the best match between differentiated services and resource
efficiency. It is used for congestion control and load control.
The BP mapping table, SP mapping table and AP mapping table can be configured and
adjusted in the OMC. Different mapping data shows different trends of operation
strategies. Through the adjustment of the BP mapping table, you can see the trends of
operation strategies of the user and service priorities. In addition, through the adjustment
of the AP mapping table, you can also adjust the amount of system resources occupied
by high-priority users and services.
2.3 ZWF23-05-001 QoS Mapping for HSDPA Service
The RNC maps the RAB QoS parameters from the CN to the basic priority used in the
UTRAN and uses the basic priority as a Scheduling Priority Indicator (SPI) for HSDPA
services.

QoS Feature Guide
2.4 ZWF25-05-001 QoS Mapping for HSUPA Service
The RNC maps the RAB QoS parameters from the CN to the basic priority used in the
UTRAN and uses the basic priority as a Scheduling Priority Indicator (SPI) for HSUPA
services.
3 Technical Descriptions
3.1 Functions of Priorities
For subscribers connected to a cell, the RNC allocates the radio resources based on the
priorities. The configuration of ARP depends on the following factors: ARP assigned by
the core network in the service establishment phase, traffic class, THP of I services,
radio channel type, and real-time rate of subscribers.
The bit rate that a service is able to obtain depends on the radio channel which bears the
service. The radio channel consists of the following resources:
Uplink interference
Downlink power
HSDPA throughput
Code resources
CE resources (Node B)
Number of HSPA UEs (Node B)
For the radio network, not only should the QoS requirements of services be met as many
as possible, but also the capacity factors should be taken into account. To achieve a
good balance between them, the ZTE RNC allocates resources reasonably through
admission control, congestion control and load control.
Admission control is mainly used for determining whether to admit new service requests

QoS Feature Guide
based on the requested resources and the usage of the cells current resources when the
services request new system resources. As a result, it helps to avoid the system
overload after the access of new services, ensuring the stability of the system.
Meanwhile, services should be accesses as many as possible if there are sufficient
resources available to make full use of system resources and ensure the QoS of users.
Congestion control is designed for reallocating the system radio resources when the
system is congested and for executing a series of control measures to relieve congestion
according to the service attributes. As a result, it improves the call completion rate and
realizes proper utilization of system resources for services with different priorities.
Load control is used to control the load of each cell. It aims to adopt measures to get the
system load back to the normal as soon as possible to keep the system stable when the
system is overloaded.
The above functions allocate resources based on the priorities. The RRM priority is
obtained by the mapping of the ARP, traffic class, bearer type and real-time rate of
services. The following sections introduce the mapping methods of priorities.
3.2 Types of Priorities
In the UTRAN, the priorities that need to be configured are classifies into two categories:
the priorities defined in the messages of the Iub, Iur and Uu interfaces, and the
user-defined priorities used in the RRM algorithm of the RNC. All these priorities are
configured based on the QoS attributes of services. The QoS of services is mainly
defined by the CN. To be specific, the CN delivers the QoS by assigning messages by
the RAB to the RNC, including the ARP which embodies the subscription priority of users,
THP for interactive services, and Traffic Class. In addition, operators wish to differentiate
bearer priorities, in particular, the priorities among the DCH bearer services, the
HSDPA/HSUPA bearer services, and the MBMS bearer services.
When performing the control functions such as admission, congestion, and load, the
RNC maps the QoS parameters assigned by the CN mentioned above to the internal
priority of the RNC, and makes use of it. The priorities can be divided into the following
categories:

QoS Feature Guide
Logical channel priority
BP
SP
AP
3.3 Configuration Scheme of Priorities
The priority used by the RNC is acquired by the mapping of the QoS parameters in RAB
assignment by the CN. Input parameters are:
Traffic Class
THP
ARP
The RNC maps these parameters to the logical channel priority, BP, SP, and AP. For the
general mapping scheme, see the figure below.
(Note: C indicates conversation services, S indicates streaming services, I indicates

interactive services, and B indicates background services.)

QoS Feature Guide
Figure 3-1 Priority Mapping Scheme
Traffic Class
Traffic Handling MAC logical channel priority
priority(THP) SRB > C > S > I > B
(Service Type)
Allocation/Retention
Iub/Iur
Priority(ARP)
Allocation/Retention Priority
(User Type)
Iub/Iur
Frame Handling Priority
MCC
+ Basic Priority Scheduling Priority Indicator
MNC
Common Transport Channel Priority
Indicator
DCH/HSPA/MBMS
+ Queue Scheduling Priority
(Bearer Type)
Admission Priority
Direction (UL or DL) + Admission Threshold
Pre-emption Priority
Data Rate(R) + Overload/Congestion Priority
Note:
1. The Frame Handling Priority (FHP), Scheduling Priority Indicator, and Common
Transport Channel Priority Indicator on the lur/lub interface adopt the mapping
results of the BP directly. Therefore, for an RB, the FHP, SPI and BP are the same.
The FHP is the priority of a Node B. It indicates the priority of data scheduling and
resource allocation during resource congestion. The SPI is used for queue data
scheduling of HSPA. It is an important basis for packet scheduling and resource
allocation of a Node B.
2. MCC and MNC refer to the MCC and MNC of the Selected PLMN of a UE. If the
Selected PLMN is not available, the MCC and MNC of the using PLMN are obtained
as the MCC and MNC.
The following table is a summary of the scenarios applied to the basic priority (BP),

QoS Feature Guide
scheduling priority (SP), and application priority (AP). For details of the applications, refer
to the relative Feature Guides.
Priority Function Scenarios
(1) When the RAB is admitted, the RNC obtains the
admission threshold based on BP.
(2) For HSDPA, when resources for HSDPA are
shared by multiple users, the RAN (Node B)
Admission
allocates the code and power resources to different
Control
HSDPA mobiles according to the SPI which is equal
HSDPA Packet
to the BP.
Basic Priority Scheduling
(3) For HSUPA, when resources for HSUPA are
(BP) HSUPA Packet
shared by multiple users, the RAN (Node B)
Scheduling
allocates the grant to different HSUPA mobiles
FACH
according to the SPI which is equal to the BP.
Scheduling
(4) For FACH, SPI = 15 is used only for signaling,
for example, BCCH, CCCH and DCCH; SPI = 014
is used for DTCH (corresponding to the BP; if the
BP is over 14, set the SPI to 14).
(1) When forced release is performed because of

resource congestion, the RNC selects users to
perform forced release based on SP.
SP of RNC Congestion
(2) When queuing and service readmission are
(SP) Control
performed because of resource congestion, the
RNC selects users to perform admission based on
SP.
When DCH data rate downgrading is performed

Congestion
because of resource congestion, the RNC selects
Application Control
users to perform downgrading based on AP.
Priority (AP) Overload
When overload happens, the RNC selects users to
Control
decrease load based on AP.
For more details about the applications of the priorities in radio resource management,
see Chapter 4.
3.4 Configuration of Logical Channel Priority
The MAC logical channel priority is configured directly based on the Traffic Class, and
the MLP of SRB has the highest priority. SRB > C > S > I > B. The RNC is configured as

QoS Feature Guide
follows (1 indicates the highest priority).
MLP reflects priorities of different RBs for a UE. It is the basis of data scheduling. For
example, an RB with a higher priority is allocated with more bandwidth when the amount
of resources is fixed.
For a DCH, the MLP is configured to the user plane of the RNC and UEs, which is a
considerable factor when the user plane schedules the data. The Node B is invisible for
the MLP, because the protocol of logical channels is invisible for the Node B.
For the IMS system, a session initiation protocol (SIP) should be set up at first, which
means, for the RNC, the signaling in the application layer is still a service RB (Radio
Bearer). But it serves the real service RB which it accompanies. The SIP RAB is an
interactive RAB assigned by the CN, and therefore the Logical Channel Priority of SIP is
equal to that of the interactive listed in the table below.
Table 3-1 Logical Channel Priority Mapping
Traffic Class SRB1 SRB2 SRB3 SRB4 C S I B
MLP 3 1 2 4 5 6 7 8
3.5 BP Configuration
The BP can be mapped based on PLMN (the parameters is set depending on the object
vsDataUPlmnSpecFunction), and is mapped from the Traffic Class, ArpPL, THP Seg of I
services. It is divided into 16 levels (015, with 15 the highest level, 0 the lowest).
Because these elements mapping the BP are the same for uplink and downlink, the BP
does not differentiate uplink and downlink. The uplink BP and downlink BP are the same
for a call.
For multiple-RAB concurrence, each RAB has its own ArpPL/TC/THP. Therefore, the
RABs are mapped from the MOC mapping table based on their own ArpPL/TC/THP, and
are independent from each other.
In the 25.413, the valid value range of the ArpPL and THP (only valid for I services) is
from 1 to 15. 1 indicates the highest priority and 14 the lowest, while 15 means no priority.

QoS Feature Guide
The RNC considers 15 to be the lowest priority during processing (the RNC sets ArpPL
to 14 once the value of ArpPL from the CN is 0). When the RNC receives the ArpPL and
THP assigned by the core network, it maps the BP based on the Traffic Class, ArpPL,
and THP. Because the value range (15) of the ArpPL and THP plus the classes of Traffic
Class is far beyond the value range (15) of the BP, the values of THP are segmented.
The values in the same segment are considered to be the same, corresponding to the
same BP. The THP is segmented by segment thresholds (THPThresh) to determine the
segment intervals. In addition, the THP is valid only for I services. Therefore, it is
reflected by the TrafficClass (UBasPriMapping) field of the OMC in terms of the OMC
configuration field, which means the intra-ZTE Traffic Class extends the Traffic Class in
the protocol.
For the IMS system, a session initiation protocol (SIP) should be set up at first, which
means, for the RNC, the signaling in the application layer is still a service RB (Radio
Bearer). But it serves the real service RB which it accompanies. Therefore, to
differentiate the priorities of SIP and other services, the TrafficClass(UBasPriMapping)
is also added with a SIP value. Then, the SIP can be configured with a higher priority
than the services.
Considering that the Voice and Video can have different BPs, the C services can be
divided into Voice and Video services for mapping separately.
Note1: The RNC configures the BP of the SRB with the highest priority which is equal to
15 by default.
Note2: SIP, C_Voice and C_Video are defined by 3GPP, but they are not simply attained
by 3GPP's Traffic Class. ZTE treats an RAB as SIP, C_Voice and C_Video according to
the following from the Iu interface:
1 C_Voice is attained according to the traffic class IE which indicates 'conversational'

and the Source Statistics Descriptor IE which indicates 'speech ' in 25.413.
2 C_Video is attained according to the traffic class IE which indicates 'conversational'

and the Source Statistics Descriptor IE which indicates 'unknown' in 25.413.
3 SIP is attained according to the traffic class IE which indicates 'interactive' and the
Signalling Indication IE which indicates 'signalling' in 25.413.

QoS Feature Guide
After service assignment, the RNC maps to the BP based on Traffic Class, ARP, and
THP in the following way:
1 For a subscriber using I services, the RNC obtains the THP of the subscriber in RAB
assignment, and determines the THP segment where the service resides based on
the THP segment threshold value configured by the OMC. Then it obtains the
TrafficClass(BasPri) based on the THP segment where the service resides.
2 The RNC obtains the BasicPrio from the mapping of the BP table configured by the
OMC based on the ArpPL and TrafficClass (extended) where the service resides.
Table 3-2 BasicPrio Mapping Example
TrafficClass
I (THP)
ArpPL(RAB) SIP C_Voice C_Video S B
1~5 6~10 11~15
1~5 15 14 14 10 9 8 7 7
6~10 15 13 13 10 6 5 4 4
11~15 15 12 12 10 3 2 1 0
3.6 SP Configuration
If resource congestion occurs and the resource preemption is initiated, the scheduling
priority (SchPrio) of the RNC is used to select a UE to be preempted and a queuing UE
for rescheduling and admission.
SchPrio is mapped from the BasicPrio and BearerType. It can be divided into 16 levels
(015, with 15 the highest level, 0 the lowest). Compared with the BP, the SP takes one
more factor - bearer type - into consideration to differentiate the priorities of different
bearer types. If the BP or bearer type changes (for example, channel migration occurs),
the SP changes.
The RNC maps to the SP based on the BP and bearer type in the following way:
1 The RNC obtains the refUSchPriMappingProfile value used in the service cell from
the object UUtranCellFDD and then finds the profileId in the object

QoS Feature Guide
vsDataUSchPriMappingProfile with the same value as refUSchPriMappingProfile.
2 The RNC obtains the BP of the RAB according to the method introduced in Section
3.2.5 BP Configurations.
3 The RNC obtains the SP of the RAB according to the profileId, BP of the RAB, and
bearer type of the RAB allocated by the RNC based on the SP mapping table
configured by the OMC.
Table 3-3 SchPrio Mapping Example
profileId =1
BearerType
BasicPrio
DCH HSPA MBMS
0 0 1 2
1 1 2 3
2 2 3 4
3 3 4 5
4 4 5 6
5 5 6 7
6 6 7 8
7 7 8 9
8 8 9 10
9 9 10 11
10 10 11 12
11 10 11 12
12 11 12 13
13 12 13 14
14 13 14 15
15 14 15 15
The following example explains the mapping process specifically based on the 0SchPrio
Mapping Example.
Supposing a UE initiates a service request, the related parameters are as follows:

QoS Feature Guide
The ArpPL assigned by the RAB in service establishment is 2;
The UE requests B services.
The RNC allocates services for HSPA.
Then:
1. SchPrilndex (UtranCell) is 1.
2. The BP is 7 according to the method described in Section 3.1.5 BP

Configurations.
3. The SP of the UE is 8 according to the Table 3-3 based on the bearer type
E-DCH/HS-DSCH allocated by the RNC.
The SP is used to schedule a call queue and to select the subscriber to be released
during forced release. When queue scheduling starts, the subscribers with higher SPs
are scheduled first, and the subscribers with lower SPs are scheduled later. The forcedly
released subscribers are selected in the ascending order of priority.
The SP is used only within the RNC. It is different from the SPI which can be configured
to the Node B and can be used for the packet scheduling algorithm.
3.7 AP Configuration
The AP involves two application scenarios. It is used to select users in the case of
congestion, which is called congestion control priority. It is also used for reducing load
when the system is overloaded, which is called load control priority. The handling policy
of congestion differs from that of overload, and therefore the configurations of the
congestion control priority and load control priority are different from each other. They
share the configuration table of the AP, but the values may be different. They can be
indexed to different AP configurations according to the following index numbers in the
cell table. The AP index number for load control is controlled by the parameter
ref1UAppPriMappingProfile, while the AP index number for congestion control is
controlled by the parameter ref2UAppPriMappingProfile.

QoS Feature Guide
The AP is mapped from the BP, rate, and bearer type.
Because there are multiple service rates, the rate factor which is taken into account by
the AP has its rate class (RateClass). The current rate of a service should be mapped to
the RateClass before the AP mapping.
The following section describes the mapping rules of congestion control priority and load
control priority respectively.
3.7.1 Congestion Control Priority
The congestion control priority is used to select a subscriber for rate decrease and
schedule the DRBC queue in the congestion control process. It is mapped from the
BasicPrio, BearerType, and RateClass, including 16 levels (015, with 15 the highest
level, 0 the lowest).
The RNC maps to the congestion control priority based on the above factors in the
following way:
1 The RNC obtains the ref2UAppPriMappingProfile value used in the service cell from
UAppPriMappingProfile with the same value as ref2UAppPriMappingProfile and
intialAppPriUsingScene=1:Application Priority Configuration for Congestion
Control. Then the relevant Application priority records configuration set in the
UAppPriMapping sub-object is found.
2 The RNC obtains the BasicPrio of the RAB according to the method described in
Section 3.1.5 BP Configurations.
3 The RNC maps the downlink bit rate to the downlink rate class (RateClass) and
maps the uplink bit rate to the uplink bit class (RateClass). The bit rate is mapped to
the RateClass based on the bit rate (R) of the service. For DCH services, the bit rate
(R) indicates the currently allocated rate. For HSPA CS Domain Conversational
speech services, it indicates the MBR. For HSPA PS Domain Conversational
speech services, it indicates the MBR in the stable state. For HSPA Conversational
non-speech services, it indicates the GBR. For HSPA S services, it indicates the
GBR. For HSPA I/B services, it indicates the nominal bit rate which is controlled by

QoS Feature Guide
the OMC. HsNormBitRate is used for downlink and EdchNormBitRate is used for
uplink. The AP varies with the rate.
4 According to the AppPriIndex, BasicPrio, RateClass, Direction, and BearerType, the

congestion control priority is obtained from the AP mapping table pre-configured by
the OMC.
Table 3-4 AppPri Mapping Example (Congestion Control Priority) - profileId = 1
profileId =1
BearerType
0 1 2
Directi RateCl BasicPrio
on ass
0 4 7 0 4 7 0 4 7
10~ 12~ 10~ 12~ 10~ 12~
~ ~ ~ ~ ~ ~ ~ ~ ~
11 15 11 15 11 15
3 6 9 3 6 9 3 6 9
<=16
4 5 6 7 8 5 6 7 8 9 11 12 13 14 15
Kbps
(16,
64] 3 4 5 6 7 4 5 6 7 8 11 12 13 14 15
Kbps
(64,
1 128] 2 3 4 5 6 3 4 5 6 7 11 12 13 14 15
Kbps
(128,
384] 1 2 3 4 5 2 3 4 5 6 10 11 12 13 14
Kbps
>384K
0 1 2 3 4 1 2 3 4 5 10 11 12 13 14
bps
<=16K
4 5 6 7 8 5 6 7 8 9 - - - - 15
bps
(16,
64] 3 4 5 6 7 4 5 6 7 8 - - - - -
0
Kbps
(64,
128] 2 3 4 5 6 3 4 5 6 7 - - - - -
Kbps

QoS Feature Guide
profileId =1
(128,
1 2 3 4 5 2 3 4 5 6 - - - - -
384]
>384
0 1 2 3 4 1 2 3 4 5 - - - - -
Kbps
The following example explains the mapping rules for configuration personnel.
Supposing the related parameters of the requested service are as follows:
The ArpPL assigned by the RAB in service establishment is 2;
The UE requests B services.
The RNC allocates DCH/DCH for the service.
The services real-time rate is 128 kbit/s.
After RAB assignment, the AP to which the RAB maps is obtained in the follow way:
1. CgtCtlPriIndex obtained from the Utran Cell is 1.
2. The BasicPrio is 7 according to the method described in Section 3.1.5 BP

Configurations.
3. The current service downlink bit rate is 128 kbit/s, which is within the range of the
parameter RateClass 2 according to Table 3-4. The current service uplink bit rate is
128 kbit/s, which is within the range of the parameter RateClass 2 according to
Table 3-4.
4. Based on the CgtCtlPriIndex = 1, BasicPrio = 7, RateClass = 3, direction = 1, and

BearerType = DCH, you can find the corresponding downlink congestion control
priority is 4 according to the pre-configured value 0. Based on the CgtCtlPriIndex=1,
BasicPrio = 3, RateClass = 3, direction=0, and BearerType = DCH, you can find the
corresponding uplink congestion control priority is 4 according to the pre-configured
value 0.

QoS Feature Guide
By executing congestion control through the congestion control priority, the system is
able to effectively allocate radio resources to users based on their priorities, which
ensures higher-priority users to occupy more resources and obtain more bandwidth.
3.7.2 Load Control Priority
The load control priority is used to select target subscribers during load control. It is
mapped from the BasicPrio, BearerType, and RateClass, including 16 levels (015, with
15 the highest level, 0 the lowest).
The RNC maps to the load control priority based on the above factors in the following
way:
1 The RNC obtains the ref1UAppPriMappingProfile value used in the service cell from
UAppPriMappingProfile with the same value as ref1UAppPriMappingProfile and
intialAppPriUsingScene=0:Application Priority Configuration for Load Control.
Then the relevant Application priority records configuration set in the
UAppPriMapping sub-object is found.
2 The RNC obtains the BasicPrio of the RAB according to the method described in
Section 3.1.5 BP Configurations.
3 The RNC maps the downlink bit rate to the downlink rate class (RateClass) and
maps the uplink bit rate to the uplink bit class (RateClass). The bit rate is mapped to
the RateClass based on the currently rate (R) of the service. For DCH services, the
bit rate indicates the currently allocated rate. For HSPA CS Domain Conversational
speech services, it indicates the MBR. For HSPA PS Domain Conversational
speech services, it indicates the MBR in the stable state. For HSPA Conversational
non-speech services, it indicates the GBR. For HSPA S services, it indicates the
GBR. For HSPA I/B services, it indicates the nominal bit rate which is controlled by
the OMC. HsNormBitRate is used for downlink and EdchNormBitRate is used for
uplink. The AP varies with the rate.
4 According to the AppPriIndex, BasicPrio, RateClass, Direction and BearerType, the

load control priority is obtained from the AppPri mapping table pre-configured by the
OMC.

QoS Feature Guide
Table 3-5 AppPri Mapping Example (Load Control Priority)
profileId =2
BearerType
0 1 2
Directi RateCl BasicPrio
on ass
0 4 7 0 4 7 0 4 7
10~ 12~ 10~ 12~ 10~ 12~
~ ~ ~ ~ ~ ~ ~ ~ ~
11 15 11 15 11 15
3 6 9 3 6 9 3 6 9
<=16
4 5 6 7 8 5 6 7 8 9 11 12 13 14 15
Kbps
(16,
64] 3 4 5 6 7 4 5 6 7 8 11 12 13 14 15
Kbps
(64,
1 128] 2 3 4 5 6 3 4 5 6 7 11 12 13 14 15
Kbps
(128,
384] 1 2 3 4 5 2 3 4 5 6 10 11 12 13 14
Kbps
>384
0 1 2 3 4 1 2 3 4 5 10 11 12 13 14
Kbps
<=16
4 5 6 7 8 5 6 7 8 9 - - - - -
Kbps
(16,
64] 3 4 5 6 7 4 5 6 7 8 - - - - -
Kbps
(64,
0 128] 2 3 4 5 6 3 4 5 6 7 - - - - -
Kbps
(128,
384] 1 2 3 4 5 2 3 4 5 6 - - - - -
Kbps
>384
0 1 2 3 4 1 2 3 4 5 - - - - -
Kbps

QoS Feature Guide
Because the load control priority and congestion control priority share the same mapping
method, we do not explain with an example.
If load control is triggered due to overload, the subscribers whose load will be decreased
are selected based on their APs. When a subscriber is selected, the subscriber can
execute rate decrease, forced handover, migration to FACH, and release.
3.8 The Application of QoS Parameters of Iu Interface
The QoS parameters of the Iu interface include:
Traffic Class: It is used to establish bearer and the mapping of the basic priority (refer to
Section 3.1.5).
Maximum Bit Rate (MBR): This parameter determines the maximum bit rate for R99
services (refer to the ZTE UMTS DRBC Algorithm Feature Guide) and is used in the
process of HSDPA flow control (refer to ZTE UMTS HSDPA Packet Scheduling Feature
Guide) and used to determine the SF for the physical channel of HSUPA (refer to the
ZTE UMTS HSUPA Introduction Feature Guide) .
Guaranteed Bit Rate (GBR): This parameter is available for conversional traffic class
and streaming class services. The GBR is used in dynamic radio bearer control (refer to
the ZTE UMTS DRBC Algorithm Feature Guide), HSDPA packet scheduling (refer to the
ZTE UMTS HSDPA Packet Scheduling Feature Guide), and HSUPA packet scheduling
(refer to the ZTE UMTS HSUPA Packet Scheduling Feature Guide).
Transfer Delay: It is not used in the ZTE RNC.
Traffic Handling Priority: It is used for basic priority mapping; refer to Section 3.1.5.
SDU Error Ratio: It is not used in the ZTE RNC.
Residual Bit Error Ratio: It is not used in the ZTE RNC.
Allocation/Retention Priority: It includes four IEs:
Priority Level: This parameter indicates the priority of UEs and is used in basic
priority mapping.

QoS Feature Guide
Pre-emption Capability: This parameter indicates the RAB attributes to

pre-empt other RABs. Refer to the ZTE UMTS Congestion Control Feature
Guide.
Pre-emption Vulnerability: This parameter indicates the RAB attributes to be

pre-empted by another RAB. Refer to the ZTE UMTS Congestion Control
Feature Guide.
Queuing Allowed: This parameter indicates the RAB attributes of queuing.

Refer to the ZTE UMTS Congestion Control Feature Guide.
3.9 MBR Controlling in RNC
This feature relates to four cell-level parameters: UlCtrlMBRSwitch, UlControledMBR,

DlCtrlMBRSwitch, and DlControledMBR.
For Uplink MBR operated in the RNC:
If the value of UlCtrlMBRSwitch is 0: Off, the Uplink MBR operated in RNC = MBR
subscribed in CN.
If the value of UlCtrlMBRSwitch is 1: Replaced Mode , the Uplink MBR operated in

RNC = UlControledMBR.
If the value of UlCtrlMBRSwitch is 2: Minimum Mode , the Uplink MBR operated in

RNC = min{ MBR subscribed in CN, UlControledMBR }.
If the value of UlCtrlMBRSwitch is 3: Maximum Mode , the Uplink MBR operated in

RNC = max{ MBR subscribed in CN, UlControledMBR }.
For Downlink MBR operated in the RNC:
If the value of DlCtrlMBRSwitch is 0: Off, the Downlink MBR operated in RNC =

MBR subscribed in CN.
If the value of DlCtrlMBRSwitch is 1: Replaced Mode, the Downlink MBR operated

in RNC = DlControledMBR.

QoS Feature Guide
If the value of DlCtrlMBRSwitch is 2: Minimum Mode, the Downlink MBR operated in

RNC = min{ MBR subscribed in CN, DlControledMBR }.
If the value of DlCtrlMBRSwitch is 3: Maximum Mode, the Downlink MBR operated

in RNC = max{ MBR subscribed in CN, DlControledMBR }.
Notes
1. This feature is only used to modify the MBR in the RNC, not related to RAB
negotiation or RAB re-negotiation.
2. For macro-diversity and mobility state, the value of UlCtrlMBRSwitch,

DlCtrlMBRSwitch, UlControledMBR, and DlControledMBR get the parameter values
for the best cell when the RAB is setup without consideration of the changes in
update of the best cell.
4 Radio QoS Differentiated Strategy

QoS differentiation of user priorities, R99, and HSDPA are finally reflected by admission
control, congestion, and load control. The following sections describe how QoS
differentiation is reflected in RRM algorithms.
4.1 QoS Differentiation of Admission Control
Different admission thresholds can be set in admission control based on BP (values

015 refer to the BasicPrio and come from BP configuration; see Section 3.1.5 BP
Configuration in this document; value 16 is used only for Handover) and different
transmission channels, and can be set to different values for different operators
(MCC/MNC).
Operators determine the degree of difficulty to be admitted for users/services with

different ARPs by setting different admission thresholds for different priorities. For
example, when the load is heavy, an operator can admit users with higher priorities and
refuse those with lower priorities to avoid the impact on service quality of higher-priority
users due to lower-priority user admission.

QoS Feature Guide
Here are some examples.
Assume that 90% TCP resources are occupied in the current system. Two users are
requesting to be admitted. Ones BP is 7 (higher) and the others BP is 2 (lower). The
DCH downlink admission thresholds are set as follows:
For the details about application of DCH downlink admission threshold in admission
control strategy, refer to the ZTE UMTS Admission Control Feature Guide.
BasicPrio DchDlAcThresh
7 95%
2 85%
Because the current load of the system is 90% and the admission threshold for users
with the BP of 2 is 85%, the users cannot be admitted but the users with the BP priority of
7 can be admitted. This achieves the purpose of preserving resources for higher-priority
users.
In addition, you can also determine the degree of difficulty to be admitted for users on the
R99, HSDPA, and HSUPA by setting admission thresholds for different transmission
channels. For example, for users at the same BP, the operator can adjust the admission
threshold according to the use priorities of the DCH and HSPA to enable the R99 users
to be admitted easier or harder than HSPA users. This reflects differentiation between
the R99 and the HSPA.
4.2 QoS Differentiation of Congestion Control
If the system is congested, differentiation is reflected by scheduling strategies in case of

resource occupation or queuing user re-admission. The following sections describe how
to reflect QoS differentiation in scheduling in case of resource occupation or queuing
user re-admission.
4.2.1 Application of QoS Application in Resource Occupation
The resource occupation function is introduced to ensure that users with strong
preemption capability can be admitted quickly by occupying other resources that can be
released forcibly or be used by lower-priority users. This reflects service differentiation

QoS Feature Guide
between users.
Resource occupation strategies include forced release and rate decrease. The following
sections describe how to apply QoS to reflect differentiation in these strategies.
4.2.2 Application of QoS in Forced Release
For a service request during system congestion, the system releases an ongoing service
forcibly according to service priority and preemption capability. As specified in 3GPP
protocols, the preemption capability is determined by the CN in the Allocation/Retention
Priority Information Element (IE) in the RAB assignment message during service setup
or in the RL setup message during Iur handover. If the RAB assignment message or RL
setup message during Iur handover does not carry the Allocation/Retention Priority IE,
the RAB has the lowest priority without the preemption capability and can be released by
other RABs forcibly. Basic principles of forced release are: The services with preemption
capability and higher resource scheduling priorities (SPs) can release those with lower
SPs to obtain their required radio resources. During system congestion, the access of
services with preemption capability and higher priority triggers forced release. The
system searches and releases the services with lower priorities whose resources meet
the requirements of services with higher priorities, and then accesses the services with
higher priorities.
Resource occupation of multiple RABs: (Note: multiple RABs below include CS+PS and
PS+PS)
If a user originating the forced release has multiple RABs, the system needs to combine
the preemption capabilities for the originator. If one of the RABs has preemption
capability, the originator is considered as having the preemption capability. The system
uses the RAB with the highest priority as the SP to compare with the SP of the user to be
released forcibly. If the highest priority of the originator is higher than that of the user to
be released forcibly, the originator occupies resources occupied by the user.
If a user to be released forcibly has multiple RABs, the highest RAB SP is used as the SP
during forced release. Meanwhile, all RABs can be forcibly released only when they are
allowed to be released forcibly (PVI is pre-emptable).
Resource occupation of HSPA services: Forced release is carried out according to the

QoS Feature Guide
load types and congestion causes.
If the number of users on the HS or E-DCH is restricted, online HS or E-DCH users can
be forcibly released only.
If DPCH code resources are restricted, HS users are also considered as those to be
released forcibly (if the preceding forced release conditions are met).
If DPCH CE resources are restricted, E-DCH users are also considered as those to be
released forcibly (if the preceding forced release conditions are met).
As described above, selection of users to be released forcibly and priority judgment

between users originated forced release and users to be released forcibly are based on
the SP. Because SP is associated with BP and load types (DCH, HSPA) and BP reflects
ARP, differentiation between R99, HSPA and ARP can be reflected in these strategies.
Note: This document mainly describes application of priorities in QoS. For details of the
forced release strategies, refer to the ZTE UMTS Congestion Control Feature Guide.
Here are the examples:
Assume that there are three users in the network: UE1, UE2, and UE3. Now UE4 wants
to be admitted to the network. However, the network is now congested due to insufficient
radio resources.
The following table lists forced release attributes and SPs of these users:
Users PCI PVI SchPrio
UE1 N. Y 2
UE2 Y Y 5
UE3 Y N. 13
UE4 Y Y 7
From the table, the PCI of UE4 has preemption capability, and the PVIs of the online
users UE1 and UE2 are allowed to be released forcibly. In addition, priority levels of the
four users are arranged in a descending order: UE4, E2, and UE1. Therefore, UE4 with
the highest priority can access the network by forcibly releasing other users. Because the
priority of UE1 is the lowest, UE1 is the first to be released forcibly.

QoS Feature Guide
4.2.3 Application of QoS in Rate Decrease
When resources are congested (for example, new users fail to access the network), the
system can trigger rate decrease of online users to reserve resources for new services or
users.
DCH rate adjustment triggered by the RNC:
Congestion causes triggering rate decrease include DPCH code resources, CE

congestion, power congestion, and RTWP congestion, which means the system triggers
rate decrease in case of these resource congestions.
Selection of users whose rate is to be decreased: The congestion control APs of RABs of
users are arranged in a descending order. The rate of the service with the lowest control
AP is decreased, which means the rate is decreased according to RABs.
When resource congestion of a new access user (including handover users and
relocation users) in the cell triggers rate decrease, o ensure the completion rate of the
user, the relative priority between the new access user and the user whose rate to be
decreased, or whether the new access user has preemption capability, is ignore.
When a rate increase request of an online service triggers rate decrease of other online
services, to ensure equality between users and to avoid ping-pong adjustment between
the user requesting rate increase and the user whose rate is to be decreased, the
following two factors should be taken into account in the strategy of triggering rate
decrease of online services: comparison between current rate and NBR, and AP (based
on rate mapping of the user currently allocated). NBRs can be set separately based on
different priorities and its downlink and uplink can also be set separately. The uplink NBR
is controlled by the OMC parameter UlNormBitRate and the downlink NBR by the OMC
parameter DlNormBitRate. The service with a lower AP cannot trigger rate decrease of
the service with a higher AP, but the service with a higher AP can trigger rate decrease of
the service with a lower AP. Additionally, when resources are congested, the system
distributes bandwidth to the NBR according to BP. This ensures that users with higher
priorities share higher rate services, which reflects user differentiation.
According to the preceding rules, selection of users whose rate is to be decreased during
rate decrease is based on comparison between APs. And AP reflects ARP. Therefore,

QoS Feature Guide
ARP differentiation is reflected in the preceding strategies.
rate decrease strategies for congestion, refer to the ZTE UMTS Congestion Control
Feature Guide.
Assume that a new user UE4 requests access to the network that which is now
congested due to insufficient downlink power resources in the cell. There are three online
users: UE1, UE2, and UE3. The following table lists APs, real-time rates, and MinBRs of
the four users.
Users Real-time Rate (kbit/s) DlNormBitRate (kbit/s) AppPri
UE1 8 16 2
UE2 128 32 5
UE3 128 32 7
UE4 - 64 13
According to the above rules, the AP of UE1 is the lowest but its real-time rate does not
reach its MinBR, then the system does not select UE1 for rate decrease. Real-time rates
of UE2 and UE3 are higher than their MinBR and AP of UE2 is lower than that of UE3,
and the system selects UE2 to decrease its rate, and provides the disconnected
downlink power resources to UE4 for access.
HSPA rate control reflects differentiation, which is achieved by the SPI. The Node B
takes into accounts the SPI difference in scheduling resources. For detailed controlled
strategies, refer to the ZTE UMTS HSDPA Packet Scheduling Feature Guide
4.2.4 Application of QoS in Admission Scheduling
For a user who has preemption capability but fails to release forcibly, or a user with
queuing capability but without preemption capability, if the users service admission is
rejected, the system places the user/service in a queue waiting for resources for
re-access.
When the service is rejected during DRBC due to state migration, bandwidth
reapplication or redistribution, the system also places the service in a queue triggering

QoS Feature Guide
rate decrease of users with a lower priority.
For users who are put in the queue due to above-mentioned scenarios, they are
scheduled according to their APs to attempt network access or trigger rate decrease,
which means that those with higher priorities are selected to attempt network access or
trigger rate decrease in preference. This improves the successful completion rate to
reflect differentiation between different priorities.
In addition, because AP reflects load types (DCH and HSPA), differentiation between the
R99 and the HSPA is also reflected in the preceding strategies.
scheduling strategies for congestion, refer to the ZTE UMTS Congestion Control Feature
Guide.
Assume that three new call requests are congested. The following table lists the Queuing
Allowed capabilities and AP configurations of these requests (AP 13 indicates a higher
priority and AP 2 a lower priority).
Users Queuing Allowed SchPrio
UE1 N. 2
UE2 Y 7
UE3 Y 13
Because UE1 does not have queuing capability, it cannot be put in the queue. UE2 and
U3 wait in the queue. If it is found that no radio resource available for new users after a
measurement, UE3 with a higher priority is the first to access the network. If the current
radio resources are not available to both UEs at the same time, UE2 must wait for next
scheduling.
4.3 QoS Differentiation of Load Control
Purpose of load control: When the system is overloaded, it takes measures to restore the
system load to normal to ensure the stability of the system.

QoS Feature Guide
Load control reduces load in the following way: data rate decrease of PS/AMR services,
forced handover, forced IB service handover to the CELL_FACH, forced call drop, etc.
During load reduction, the system does not simply select the method used for selecting
users to reduce load according to the priority of ARP > traffic AP > load rate. Instead, it
uses the AP obtained from flexible mapping of the BP (reflecting ARP and traffic class),
load type, and load rate.. In this way, the system takes into full consideration the
business focuses of operators and the adjustment of operation strategies during different
periods. It simplifies the procedures as much as possible on the basis of usability and
completeness to ensure the operators to adjust the mapping of the QoS of traffic AP
flexibly and to satisfy the varying operation requirements in terms of time and space by
using APs for selection.
From the preceding strategies, the AP used in load control is associated with the BP, load
type, and rate. Therefore, ARP as well as QoS differentiation between the R99 and the
HSPA is reflected during load control.
load control strategies, refer to the ZTE UMTS Overload Control Feature Guide.
Assume that a cell is overloaded. There are two online users: UE1 and UE2. Their APs
are 2 and 7 respectively (AP 7 indicates a higher priority and AP 2 a lower priority).
Users AppPri
UE1 2
UE2 7
The first load reduction strategy in the RNC is rate decrease. The first step is to reduce
the rate of UE1 with a lower AP. If UE1 is already at its minimum rate, UE2 is selected to
decrease its rate. If UE2 is also already at its minimum rate, the further load reduction
measure is taken (forced handover). During forced handover, the same user as the one
selected for rate decrease is selected to be forcibly handed over. If the forced handover
fails, migration to the FACH and forced call drop are carried out.

QoS Feature Guide
4.4 QoS Differentiation of HSDPA service
The Scheduling Priority Indicator (SPI) is considered in HSDPA packet scheduling

strategy. The higher the SPI of the service is, the more opportunities and resources
(code and power) are scheduled by a Node B. The SPI is mapped from the basic priority
(BP), and can be set to different values for different operators (MCC/MNC), which
reflects the differentiation between HSDPA services.
For details of the HSDPA packet scheduling strategies, refer to the ZTE UMTS HSDPA
Packet Scheduling Feature Guide.
4.5 QoS Differentiation of HSUPA service
The Scheduling Priority Indicator (SPI) is considered in HSUPA packet scheduling

strategy. The higher the SPI of the service is, the more opportunities and resources are
scheduled by a Node B. The SPI is mapped from the basic priority (BP), and can be set
to different values for different operators (MCC/MNC), which reflects the differentiation
between HSUPA services.
For details of the HSUPA packet scheduling strategies, refer to the ZTE UMTS HSUPA
Packet Scheduling Feature Guide.
5 Parameters and Configurations
5.1 Parameter List
5.1.1 Information about Priority and Rate Segments

Abbreviated Name Parameter Name
THPThresh THP Segment Threshold
DlNormBitRate DCH Downlink Nominal Bit Rate
UlNormBitRate DCH Uplink Nominal Bit Rate
EdchNormBitRate E-DCH Uplink Nominal Bit Rate

QoS Feature Guide
HsNormBitRate HS-DSCH Downlink Nominal Bit Rate
5.1.2 BP Configuration
ArpPL ARP Priority Level
TrafficClass Traffic Class
BasicPrio Basic Priority
5.1.3 SP Configuration
Used Scheduling Priority Mapping Relationship

refUSchPriMappingProfile
Profile
profileId
Scheduling Priority Index
(vsDataUSchPriMappingProfile )
BearerType Radio Bearer Type
SchPrio Scheduling Priority
5.1.4 AP Configuration
Used Application Priority Mapping Relationship

ref1UAppPriMappingProfile
Profile (Load Control)
Used Application Priority Mapping Relationship

ref2UAppPriMappingProfile
Profile (Congestion Control)
profileId(UAppPriMappingProfile) Application Priority Index
BearerType Radio Bearer Type
Service Direction Used in Application Priority

Direction
Mapping
RateClass Rate Class
AppPri Application Priority
intialAppPriUsingScene Application Priority Configuration Scene

QoS Feature Guide
5.1.5 MBR Controlling in RNC

Abbreviated name Parameter name
UlCtrlMBRSwitch UL Controlled MBR Switch
UlControledMBR UL Controlled MBR
DlCtrlMBRSwitch DL Controlled MBR Switch
DlControledMBR DL Controlled MBR
5.2 Parameter Configurations
5.2.1 Information about Priority and Rate Segments
5.2.1.1 THP Segment Threshold
OMC Path
GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration.
Parameter Configuration
Related description:
The BP of an interactive service is mapped from both the THP segment and traffic class.
Therefore, before BP mapping, the THP should be divided into several segments. For
different interactive services, even if their THPs are different, their BPs are the same
after mapping if their THPs are in the same THP segment.
Parameter description:
This parameter indicates the THP segment threshold. For example, the parameter
values 15 indicate all the THPs with the values 1 to 5 belong to the same THP segment.
When the BP mapping is executed, the two interactive services (THP = 2 and THP = 3)
have the same BP.
Note: None

QoS Feature Guide
Recommendation: This parameter may affect the sequent priority mappings greatly.
5.2.1.2 DCH Uplink Nominal Bit Rate
OMC Path
GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->QOS Function->Qos Basic Configuration.
This parameter indicates the nominal bit rate for uplink interactive/background services
on DCH. It is mapped from the Basic Priority, and higher basic priority traffic has a higher
nominal bit rate. Online services should be sorted during DRBC scheduling. The services
with the current rate smaller than the NBR are put into the foremost set (set1), the
services with the current rate equal to the NBR are put into set2, and the services with
the current rate larger than the NBR are put into the last set (set3). Then the services in
each set are sorted according to their scheduling priorities (SP). The service ranking
foremost is scheduled first.
This parameter is used to configure the uplink NBRs of interactive and background
services for each BP.
Note: This parameter is valid only for the uplink rates of I/B services.
Recommendation: An appropriate value is set based on the specific conditions.
5.2.1.3 DCH Downlink Nominal Bit Rate
OMC Path


QoS Feature Guide
This parameter indicates the nominal bit rate for downlink interactive/background
services on DCH. It is mapped from the Basic Priority, and higher basic priority traffic has
a higher nominal bit rate. Online services should be sorted during DRBC scheduling. The
services with the current rate smaller than the NBR are put into the foremost set (set1),
the services with the current rate equal to the NBR are put into set2, and the services
with the current rate larger than the NBR are put into the last set (set3). Then the
services in each set are sorted according to their scheduling priorities (SP). The service
ranking foremost is scheduled first.
This parameter is used to configure the downlink NBRs of interactive and background
Note: This parameter is valid only for the downlink rates of I/B services.
5.2.1.4 E-DCH Uplink Nominal Bit Rate
OMC Path

This parameter indicates the nominal bit rate for interactive/background services on E-DCH. It is
mapped from the Basic Priority, and higher basic priority traffic has a higher nominal bit rate. In the
process of NodeB HSUPA quick scheduling, EdchNormBitRate is used as the minimum guarantee
bit rate.

QoS Feature Guide
This parameter is used to configure the uplink NBRs of interactive and background
Note: This parameter is valid only for the uplink rates of I/B services.
5.2.1.5 HS-DSCH Downlink Nominal Bit Rate
OMC Path

This parameter indicates the nominal bit rate for interactive/background services on HS-DSCH. It
is mapped from the Basic Priority, and higher basic priority traffic has a higher nominal bit rate. In
the process of NodeB HSDPA quick scheduling, HsNormBitRate is used as the minimum
guarantee bit rate.
This parameter is used to configure the downlink NBRs of interactive and background
Note: This parameter is valid only for the downlink rates of I/B services.
5.2.2 BP Configuration
5.2.2.1 ARP Priority Level
OMC Path
GUI: View -> Managed Element ->UMTS Logical Function Configuration->PLMN

QoS Feature Guide
Relating Configuration->Basic Priority Mapping Relationship.
The BP is mapped from both the ARP Priority Level and traffic class.
This parameter indicates the priority level of Allocation/Retention Priority (ARP).
5.2.2.2 Traffic Class
OMC Path

Configuration->Basic Priority Mapping Relationship.
The BP is mapped from both the ARP segment and traffic class.
This parameter indicates the traffic class for mapping.
Note: None
5.2.2.3 Basic Priority
OMC Path

QoS Feature Guide
Configuration->Basic Priority Mapping Relationship.
The BP is mapped from both the ARP segment and traffic class.
This parameter indicates the BP value mapping from a specific ARP segment value and
traffic class.
Note: None
Recommendation: This parameter is set based on the specific conditions.
5.2.3 SP Configuration
5.2.3.1 Used Scheduling Priority Mapping Relationship Profile
OMC Path
GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell.
The SP is mapped from the BP and BearerType. The BP is divided into 16 levels, and the
radio bearer has three types (DCH, HSPA, and MBMS). There are several different sets
of SP configurations. Different cells can use these sets separately according to their
unique index number.
This parameter is used to set the index number of SP global configuration.
Note: None

QoS Feature Guide
Recommendation: None
5.2.3.2 Scheduling Priority Index
OMC Path

Configuration->QOS Function->Scheduling Priority Mapping Relationship Profile.
The SP is mapped from the BP and BearerType. The BP is divided into 16 levels, and the
radio bearer has three types (DCH, HSPA, and MBMS). There are several different sets
of SP configurations. Different cells can use these sets separately according to their
unique index number.
This parameter is used to set the index number of SP global configuration.
Note: None
5.2.3.3 Basic Priority
OMC Path

The SP is mapped from the BP and BearerType and used for forced release and real
queue scheduling.

QoS Feature Guide
This parameter is used to set the BP value during SP mapping.
Note: None
5.2.3.4 Radio Bearer Type
OMC Path

queue scheduling.
This parameter indicates the radio bearer type during SP mapping.
Note: This parameter cannot be configured.
5.2.3.5 Scheduling Priority
OMC Path


QoS Feature Guide
queue scheduling.
This parameter is used to set the SP value which is mapped from a specific BP and
BearerType during SP mapping.
Note: None
5.2.4 AP Configuration
5.2.4.1 Used Application Priority Mapping Relationship Profile (Load Control)
OMC Path
This parameter indicates the DN (Distinguished Name) of the referenced application

priority profile. Load control priorities of different cells can be indexed to different
application priority profiles.
Note: None
5.2.4.2 Used Application Priority Mapping Relationship Profile (Congestion

Control)
OMC Path

QoS Feature Guide
This parameter indicates the Scheduling Priority configuration index. There are several
different sets of configuration of the Scheduling Priority configured at the RNC level and
different cells can use this parameter to index the different sets of the configuration
separately.
Note: None
5.2.4.3 Application Priority Index
OMC Path

Configuration->QOS Function->Application Priority Mapping Relationship
Profile->Application Priority Mapping Relationship.
This parameter indicates the Application Priority Mapping Relationship Profile Object ID.
Note: None
Recommendation: This parameter is configured according to the practical conditions.
5.2.4.4 Basic Priority Segment
OMC Path
GUI: View -> Managed Element ->UMTS Logical Function Configuration->Service


QoS Feature Guide
The AP is mapped from the BPSeg, BearerType, and RateSeg.
This parameter indicates the BP segment during AP mapping. For details, see Section
5.2.1.5.
Note: This parameter is used for indication only, and cannot be modified.
Note: This parameter is used with the radio bearer type in the following way: BearerType
+ BPSeg. For example, DCH1 indicates that the BearerType is DCH, and the BPSeg is
1.
5.2.4.5 Radio Bearer Type
OMC Path

This parameter indicates the radio bearer type during AP mapping.
Note: This parameter is used with the BP segment in the following way: BearerType +
BPSeg. For example, DCH1 indicates that the BearerType is DCH, and the BPSeg is 1.

QoS Feature Guide
5.2.4.6 Rate Class
OMC Path

This parameter indicates the rate class which is used to map basic priority of services.
Note: None
5.2.4.7 Application Priority
OMC Path
GUI: View -> Managed Element ->UMTS Logical Function Configuration->Service

This parameter is used to set the AP value which is mapped from a specific BPSeg,
BearerType, and RateSeg during AP mapping.
Note: None

QoS Feature Guide
5.2.4.8 Application Priority Configuration Scene
OMC Path
GUI: View ->Managed Element ->UMTS Logical Function Configuration->Service

Configuration->QOS Function->Application Priority Mapping Relationship Profile
This parameter is used to identify the Scene of the application priority. The value of 0 is
to identify that the application priority is used for the load control algorithm. The value of
0 is to identify that the application priority is used for the congestion control algorithm.
5.2.5 MBR Controlling in RNC
5.2.5.1 UL Controlled MBR Switch
OMC Path
GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN

Cell->Extended Info of UTRAN Cell.
Parameter Configuration description:
This parameter specifies the switch for the UL Controlled MBR function.
5.2.5.2 UL Controlled MBR
OMC Path

This parameter specifies the MBR value in the DL Controlled MBR function.

QoS Feature Guide
5.2.5.3 DL Controlled MBR Switch
OMC Path

This parameter specifies the switch for the DL Controlled MBR function.
5.2.5.4 DL Controlled MBR
OMC Path

Parameter configuration description:
This parameter specifies the MBR value in the DL Controlled MBR function.
6 Counters And Alarms
6.1 Counter List
This feature has no related counters.
6.2 Alarm List
This feature has no related alarms.
7 Glossary
3GPP 3rd Generation Partnership Project

QoS Feature Guide
AP Application Priority
ARP Allocation/Retention Priority
BP Basic Priority
DCH Dedicated Channel
HSDPA High Speed Downlink Packet Access
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
Kbps kilo-bits per second
MAC Media Access Control
NBR Nominal Bit Rate
QoS Quality of Service
RNC Radio Network Control

QoS Feature Guide
RRM Radio Resource Management
SP Scheduling Priority
TC Traffic Class
THP Traffic Handling Priority
UE User Equipment
UMTS Universal Mobile Telecommunication System
WCDMA Wideband Code Division Multiple Access

ZTE UMTS QoS Feature Guide - V8.5 - 201312 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS QoS Feature Guide - V8.5 - 201312 PDF

Uploaded by

Copyright:

Available Formats

QoS Feature Guide

QoS Feature Guide

Updated the following parameter descriptions:

V8.5 2013-12-10 Zhang Min Song Qiong Added feature IDs.

2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

3 Technical Descriptions ..................................................................................... 8

4 Radio QoS Differentiated Strategy ................................................................. 25

5 Parameters and Configurations ..................................................................... 33

ZTE Confidential Proprietary 2

5.2 Parameter Configurations .................................................................................. 35

6 Counters And Alarms ...................................................................................... 48

ZTE Confidential Proprietary 3

Figure 3-1 Priority Mapping Scheme ..................................................................................11

Table 3-1 Logical Channel Priority Mapping .......................................................................13

ZTE Confidential Proprietary 4

Mutual exclusion: [None]

ZTE Confidential Proprietary 5

The implementation of QoS brings the following benefits to network operators:

In a word, the purpose of implementation of the QoS assurance mechanism is to offer

2.1 ZWF21-05-002 RAB QoS Parameters Mapping

2.2 ZWF21-05-003 Differentiated Service

ZTE Confidential Proprietary 6

The SP and AP are obtained based on the BP.

2.3 ZWF23-05-001 QoS Mapping for HSDPA Service

ZTE Confidential Proprietary 7

2.4 ZWF25-05-001 QoS Mapping for HSUPA Service

3.1 Functions of Priorities

Number of HSPA UEs (Node B)

ZTE Confidential Proprietary 8

3.2 Types of Priorities

ZTE Confidential Proprietary 9

Logical channel priority

3.3 Configuration Scheme of Priorities

(Note: C indicates conversation services, S indicates streaming services, I indicates

ZTE Confidential Proprietary 10

Figure 3-1 Priority Mapping Scheme

Data Rate(R) + Overload/Congestion Priority

ZTE Confidential Proprietary 11

(1) When forced release is performed because of

When DCH data rate downgrading is performed

3.4 Configuration of Logical Channel Priority

ZTE Confidential Proprietary 12

follows (1 indicates the highest priority).

Table 3-1 Logical Channel Priority Mapping

Traffic Class SRB1 SRB2 SRB3 SRB4 C S I B

ZTE Confidential Proprietary 13

1 C_Voice is attained according to the traffic class IE which indicates 'conversational'

2 C_Video is attained according to the traffic class IE which indicates 'conversational'

ZTE Confidential Proprietary 14

Table 3-2 BasicPrio Mapping Example

ZTE Confidential Proprietary 15

vsDataUSchPriMappingProfile with the same value as refUSchPriMappingProfile.

Table 3-3 SchPrio Mapping Example

Supposing a UE initiates a service request, the related parameters are as follows:

ZTE Confidential Proprietary 16

The ArpPL assigned by the RAB in service establishment is 2;

The UE requests B services.

The RNC allocates services for HSPA.

2. The BP is 7 according to the method described in Section 3.1.5 BP

ZTE Confidential Proprietary 17

The AP is mapped from the BP, rate, and bearer type.

3.7.1 Congestion Control Priority