ZTE UMTS QoS Feature Guide

Operator Logo
QoS
WCDMA RAN
Feature Guide
QoS Feature Guide
QoS Feature Guide

Version
V4.5
Date
2010-10-15
Author
Sha xiubin
Approved By
Jiang
Remarks
Qingsong
2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains propriet ary 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
QoS Feature Guide
TABLE OF CONTENTS
1
Function Attribute ............................................................................................... 1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
Overview .............................................................................................................. 1
Overview of the Functions .................................................................................... 1
RAB QoS Parameters Mapping............................................................................ 2
MBR Controlling in RNC ....................................................................................... 2
Differentiated Service............................................................................................ 2
QoS Mapping for HSDPA Service ........................................................................ 3
QoS Mapping for HSUPA Service ........................................................................ 3
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
Introduction to Technologies ............................................................................ 4

Functions Description ........................................................................................... 4
Functions of Priorities ........................................................................................... 4
Types of Priorities ................................................................................................. 5
Configuration Scheme of Priorities ....................................................................... 5
Configuration of Logical Channel Priority ............................................................. 7
BP Configuration ................................................................................................... 7
SP Configuration ................................................................................................. 10
AP Configuration ................................................................................................. 11
The Application of QoS Parameters of Iu Interface ......................................... 15
MBR Controlling in RNC ..................................................................................... 16
4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.3
4.4
4.5
Radio QoS differentiated Strategy.................................................................. 17

QoS Differentiation of Admission Control ........................................................... 17
QoS Differentiation of Congestion Control ......................................................... 18
Application of QoS Application in Resource Occupation ................................... 18
Application of QoS in Forced release ................................................................. 18
Application of QoS in Rate Decrease ................................................................. 20
Application of QoS in Admission Scheduling ..................................................... 21
QoS Differentiation of Load Control.................................................................... 22
QoS Differentiation of HSDPA service ............................................................... 23
QoS Differentiation of HSUPA service ............................................................... 23
5
5.1
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
Configuration of Parameters ........................................................................... 24

Parameter List..................................................................................................... 24
Information about Priority and Rate Segments .................................................. 24
BP Configuration ................................................................................................. 24
MBR Controlling in RNC related parameters ..................................................... 25
Parameter Configuration..................................................................................... 25
Information about Priority and Rate Segments .................................................. 25
BP Configuration ................................................................................................. 32
MBR Controlling in RNC related parameters ..................................................... 39
II
QoS Feature Guide
6
6.1
6.2
Counter And Alarm ........................................................................................... 41

Counter List ......................................................................................................... 41
Alarm List ............................................................................................................ 41
Glossary ............................................................................................................. 41
III
QoS Feature Guide
FIGURES
Figure 3-1 Priority Mapping Scheme ....................................................................................... 6
TABLES
Table 3-1 Logical Channel Priority Mapping ........................................................................... 7
Table 3-2 BasicPrio Mapping Example ................................................................................... 9
Table 3-3 Mapping Relationship Table between the ARP Mapping and ARP Segment
(ARPSeg) .................................................................................................................................... 9
Table 3-4 SchPrio Mapping Example .................................................................................... 10
Table 3-5 AppPri Mapping Example (Congestion Control Priority) - AppPriIndex = 1 ......... 12
Table 3-6
Mapping Relationship Between BP and BPSeg ................................................... 13
Table 3-7
Mapping Relationship Between Rate and RateSeg (downlink) ............................ 13
Table 3-8
Mapping Relationship Between Rate and RateSeg(uplink) ................................. 14
Table 3-9 AppPri Mapping Example (Load Control Priority) ................................................. 15
IV
QoS Feature Guide
Function Attribute
System version: [RNC V3.09, OMMR V3. 09, Node B V4.09, OMMB V4. 09]
Attribute: Mandatory
Relat ed NEs:
UE
-
NodeB
RNC
MSCS
MGW
-
SGSN
GGSN
-
HLR
Note:
*-: Non-related NE
*: Related NE
Dependency: [None]
Exclusion: [None]
Remarks: [None].
Overview
2.1
Overv iew of the Functions

Besides the more complicated technologies employed in the physical layer of the air
interface for higher spectrum utilization in 3G system, the typically features of end-to-end
(E2E) QoS structure is clearly defined by 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. Thus, the
system can make full use of its own technical strengths and provides customers with
differentiated services to enhance their satisfaction and increase the operation income.
Through implementation of t he E2E QoS mechanism, subscribers will be satisfied with
the servic es 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 profits of operators.
The implementation of QoS brings the following benefits for subscribers: the
differentiated user classes will ensure the high -level subscribers to obtain better service
than the low-level subscribers. The differentiated applications of different services
ensure that the services wit h high experience requirements will be handled in preference.
For real-time applications of services, each net work element handles related data as
QoS Feature Guide
soon as possible; while for non-real-time applications of services, the related data will be
handled later.
The implementation of QoS brings the following benefits to network operators:
Improve the benefits of operation c ost: The QoS mechanism offers effective measures
for net work operat ors to optimize network resources, so the operators are able t o satisfy
the requirements of more end users with minimum network resourc es.
Acquire new income growth points: The QoS mechanism enables the network operators
to offer more value-added services, which makes it possible for 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, so 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 diffe rent service features
and users requirements, thus realizing different user experiences.
2.1.1
RAB QoS Parameters Mapping

RNC maps RAB QoS parameters from CN to the priority used in the UTRAN. And
RNC performs admission control, congestion control, overload control and packet
scheduling according to the priority mapped.
2.1.2
MBR Controlling in RNC

This Feature is used to modify the MBR by RNC to satisfy the following scene
requirement:
To test a new feat ure which need higher MB R that the subscribed MB R can not
reach.e.g. to test DC HS DPA, the MBR of whic h can reach 42Mbps, but the MBR
from CN is less than 42Mbps, when this feature can be used to satisfy the
requirement
2.1.3
Operator may hope t he real data rate enjoyed by subscriber steady-going no matter
the cell load is high or not, this feature can be used to restrain the real data rate to
reach the subscribed MBR.
Differentiated Service
According t o traffic class (Traffic Class and THP ) and A RP, ZTE defines the BP(Basic
Priority), SP(Scheduling Priority), and AP(Application Priority) for intra-RNC radio
resource management, which is not involving the transmission between the NEs.
QoS Feature Guide
The priority is just a reference for the inter-UE resource allocation when the radio
resources are insufficient and the congestion is about t o happen. Sufficient radio
resources ensure each subscriber with enough radio resourc es.
The BP reflects the priorities of us ers and servic es, that is, the users and services with
higher priority will obtain better services when the radio resources are equivalent.
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 RRM module of ZTE
designs an AP mapping table.
The SP and AP are obt ained based on the BP.
The SP, which is 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 the three-dimension table based on t he BP, bearer type
and rate of real-time, indicates the strat egic balance between the priority and res ource
occupation, and embodies the best match between differentiated services and res ource
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 BP mapping table, you can see the trends of
operation strategy of the user and servic e priorities. While through the adjustment of AP
mapping table, you can adjust the amount of system resources occupied by high-priority
users and servic es.
2.1.4
QoS Mapping for HSDPA Service

RNC maps RAB QoS paramet ers from CN to t he basic priority used in the UTRA N. And
RNC maps basic priority to Scheduling Priority Indicator (SPI)for HSDPA service
2.1.5
QoS Mapping for HSUPA Service

RNC maps RAB QoS paramet ers from CN to t he basic priority used in the UTRA N. And
RNC maps basic priority to Scheduling Priority Indicator (SPI)for HSUPA service.
QoS Feature Guide
Introduction to Technologies
3.1
Functions Description
3.1.1
Functions of Priorities
For subscribers connected to the cell, RNC allocat es the radio resources based on the
priorities. The configuration of ARP depends on the following factors: ARP assigned by
core network in t he service establishment phase, traffic class, THP of I services, radio
channel type, and real -time rat e of the subscriber.
The bit rate that the service is able to obtain depends on the radio channel which bears
the servic e. The radio channel consists of the following resources:
Uplink interference
Downlink power
HSDPA throughput
Code res ources
CE resources(Node B)
HSPA subscriber resources(Node B)
For the radio net work, not only the QoS requirements of servic es should be ensured as
much as possible, but also the capacity factors should be taken into account. To achieve
a good balance bet ween 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
based on the requested resources and usage of 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, thus ensuring the stability of the system.
Meanwhile, services should be accesses as many as possible if the resources permit, so
as to make full use of system resources and ensure the QoS of users.
Congestion control is designed for reallocating the radio resources of system 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 reasonable utilization of system resources for services with
different priorities.
QoS Feature Guide
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 when the system is overloaded,
thus keeping the system stable.
The above functions allocat e 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 introduc es the mapping methods of priorities.
3.1.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 interfac es, and the userdefined priorities used in the RRM algorithm of RNC. All these priorities are configured
based on the QoS attributes of services. The QoS of servic es is mainly defined by the
CN. To be specific, the CN delivers the QoS through 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, the operators wish to differentiate
bearer priorities, in particular, the priorities between the DCH bearer services, the
HSDPA/HS UPA 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:
3.1.3
Logical channel priority
BP
SP
AP
Configuration Scheme of Priorities

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

interactive services, and B indicates background services.)
Figure 3-1
Priority Mapping Scheme
Traffic Class
Traffic Handling
priority(THP)
(Service Type)
MAC logical channel priority

SRB > C > S > I > B
Allocation/Retention
Priority(ARP)
(User Type)
Iub/Iur
Allocation/Retention Priority
Iub/Iur
Frame Handling Priority
Scheduling Priority Indicator
Common Transport Channel Priority Indicator
Basic Priority
DCH/HSPA/MBMS
(Bearer Type)
Scheduling Priority
Data Rate
Application Priortiy
Note:
Frame Handling Priority (FHP ), Scheduling Priority Indicator, and Common Transport
Channel Priority Indicator on the lur/lub interface adopt the mapping results of BP
directly, that is, the FHP, SPI and BP are the same for aRB. Where, the FHP is the
priority of Node B. It indicates the priority of data scheduling and resource allocation in
the resource congestion. The SP I is used for the queue data scheduling of HSPA. It is
an important basis for packet scheduling and resource allocation of Node B.
The following table is the summary of scenarios applied for basic priority(BP),
scheduling priority(SP) and application priority(AP). For details of the application, please
refer to the relative Feature Guides.
Priority
Basic
Priority(BP)
Function
Scenarios
Admission
Cont rol
HSDPA Packet
Scheduling
HSUPA Packet
Scheduling
(1) When RAB is admitted, RNC obtains admission

threshold bas ed on BP.
(2) For HS DPA, when resources for HSDPA are
shared by multiple users, RAN (Node B) will
allocate the code and power res ources to different
HSDPA mobiles according to SPI which is equal to
BP.
(3) For HS UPA, when resources for HSUPA are
shared by multiple users, RAN (Node B) will
allocate the grant to different HS UPA mobiles
according to SPI which is equal to BP.
QoS Feature Guide
SP of
RNC(SP )
Congestion
Cont rol
(1) When forced release is performed bec ause of

resource congestion, RNC will select users to
perform forced release based on SP.
(2) When queueing and service admission again
are performed because of resource congestion,
RNC will select users to perform admission based
on SP.
Application
Priority(AP)
Congestion
Cont rol
OverLoad
Cont rol
When downgrading is performed because of

resource congestion, RNC will select users to
perform downgrading based on AP.
When overload happens, RNC will select users to
decrease load based on AP.
For more details about the application of the priorities in radio res ource management,
see chapter 4.
3.1.4
Configuration of Logical Channel Priority

The MA C 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. RNC is configured as
follows (1 indicates the highest priority).
MLP reflects priorities of different RB for an UE. It is the basis of data scheduling. For
example, RB with high priority is allocated with more bandwidth when the resources are
fixed.
For DCH, the MLP is configured to us er plane of RNC and UE, that is, it is a
considerable factor when the us er plane schedules the data. Node B is invisible for the
MLP, because the protocol of logical channel is invisible for Node B.
For IMS system, a session initiation protocol (S IP) should be set up at first, that is, for
RNC, the signaling in the application layer is still a service RB (Radio Bearer). But it
serves the real servic e RB which it accompanies.And SIP RAB is interactive RAB
assigned by CN, so Logical Channel Priority of SIP is equal t o Logical Channel Priority
of interactive.
Table 3-1
Logical Channel Priority Mapping
Traffic Cla ss
MLP
3.1.5
SRB1
SRB2
SRB3
SRB4
BP Configuration
BP is mapped from the Traffic Class, ARP Seg, THP Seg of I services. It is divided into
16 levels (0 - 15, with the 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, that is, the uplink BP and downlink BP are the same for a call.
QoS Feature Guide
For multiple RAB concurrence, each RAB has their respective ARP/ TC/ THP. Therefore,
the RABs are mapped from the MOC mapping table based on their own ARP/ TC/ THP,
and are independent from each other.
In the 25. 413, the valid value range of the ARP and THP (only valid for I services) is
from 1 to 15. 1 indicates the highest priority and 14 the lowest, while 15 mean no priority.
The RNC considers 15 to be the lowest priority during processing.When the RNC
receives the ARP and THP assigned by the core net work, it maps the BP based on the
Traffic Class, ARP, and THP. Because the value range (15) of The ARP and THP plus
the classes of Traffic Class is far bey ond the value range (15) of BP, the values of the
ARP and THP are segmented. The values in the same segment are considered to be
the same, corresponding to the same BP. The A RP is segment ed by setting the
segment number (A RPSegNum ) and segment thres holds (ARPThresh) in OMCR to
determine the segment intervals. The THP is also segmented by segment number
(ARPSegNum) and segment thresholds (THPThresh) to det ermine the segment intervals.
In addition, THP is valid only for I services. Therefore, it is reflected by the TrafficCl ass
(Ba sic Priority) field of the OMC in terms of the OMC configuration field, that is, the
intra-ZTE Traffic Class extends the Traffic Class in the protocol.
For IMS system, a session initiation protocol (S IP) should be set up at first, that is, for
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 t he priorities
of S IP and other services, the TrafficClass is also added with a S IP value. Thus, the S IP
can be configured with a higher priority than the service.
Considering that the Voice and Video can have different BPs, the C services can be
divided into V oice and Video services for mapping separately.
Note1: 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 difined by 3GPP, but they are not only attained
by 3GPP's Traffic Class. ZTE treats a RAB as SIP, C_Voice and C_Video according to
the followings from Iu interface:
1
C_Voice is attained according to traffic class IE which indicates 'conversational'

and Source Statistics Descriptor IE which indicat es 'speec h ' in 25. 413.
C_Video is attained according to traffic class IE which indicates 'conversational'

and 'Source Statistics Descriptor IE which indicates 'unknown' in 25.413.
SIP is attained according to t raffic class IE which indicates 'interactive'

Signalling Indication IE which indicates 'signalling ' in 25.413.
and
After the service assignment, the RNC maps to the BP based on Traffic Class, ARP, and
THP in the following way:
QoS Feature Guide
Determine the ARP segment (ARPSeg) where the service resides based on the ARP
of the UE assigned by RAB and the ARP segment threshold value configured in
OMC.
For a subscriber using I servic es, obtain the THP of the subscriber in RAB
assignment, and determine the THP segment where the service resides based on
the THP segment threshold value configured by OMC. Obt ain the TrafficClass Basic Priority based on the THP segment where the service resides.
Obtain the BP (BasicPrio ) from the mapping of BP table configured by OMC based
on the ARP segment and TrafficClass (extended) where the service resides.
Table 3-2
BasicPrio Mapping Example

TrafficClass
ARP(RAB)
ARPSeg
SIP
C_Voice
C_Video
15
14
14
15
13
11
15
12
I (THP)
1~5
6~10
11~15
10
13
10
12
10
Take the proc edure from RAB assignment to obt aining the BP as an example, referenc e
the paramet ers pre-configured by OMC and the mapping table.
Obtain the paramet er values pre-configured by OMC at first.
The configurations of A RPSegNum and A RP Thresh which are used for A RP
segment ation are: ARPSegNum = 3, ARPThresh = [5, 10] . Based on the configurations
of ARPSegNum and ARP Thresh, the mapping relationship between ARP and ARP
segment is as follows:
Table 3-3 Mapping Relationship Table between the A RP Mapping and A RP Segment
(ARPSeg)
ARP
1-5
6 - 10
11 - 15
ARPSeg
Suppose a subscriber whose A RP is 2 initiates a request for establishing B servic es, the
RNC obt ains the BP in the following way:
Because the A RP is 2, the ARP segment is 1 (ARPS eg = 1) according to the 0. Then,
according to the ARPSeg and Traffic Class (B) in the 0, the BP of the RAB is 7.
QoS Feature Guide
3.1.6
SP Configuration
When the resource congestion occurs and t he resource preemption is initiated, the
scheduling priority of RNC - SP is used to select a UE to be preempted and a queuing
UE for rescheduling and admission.
SP (SchPrio) is mapped from the BasicPrio and BearerType. It can be divided into 16
levels (0 -15, with the 15 the highest level, 0 the lowest). Compared with BP, the SP
takes one more factor bearer type - into consideration to differentiate the priorities of
different bearer types. When 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
Obtain the SP index number used in the service cell from the SchPriIndex in the
Utran Cell, and then find another SchPriIndex with the same value from the SP.
Obtain the BP of the RAB according to the method introduced in 3.2.5 BP

Configurations.
Obtain the SP of the RAB according to the SchPriIndex, BP of the RAB, and bearer
type of the RAB allocated by the RNC based on the SP mapping table configured
by OMC.
Table 3-4
SchPrio Mapping Example
SchPriIndex
1
BasicPrio
BearerTy pe
DCH
HSPA
MBMS
10
10
11
10
10
11
12
11
10
11
12
12
11
12
13
13
12
13
14
10
QoS Feature Guide
SchPriIndex
14
13
14
15
15
14
15
15
Let's use an example to explain the mapping process specifically based on the 0SchPrio
Mapping Example.
Suppose an UE initiates a service request, and the related parameters are as follows:
The ARP assigned by RAB in service establishment is 2;
The UE requests B services.
The RNC allocates services for HSPA.
Then:
1
SchPrilndex obtained from the Utran Cell is 1.
The BP is 7 according to the method introduced in 3.2.5 BP Configurations.
The SP of t he UE is 8 according t o the 0based on t he bearer type E -DCH/HSDSCH allocated by the RNC.
The SP is used to schedule the c all queue and to select the subscriber to be released in
forced release. When the queue scheduling starts, the subscribers with high SP are
scheduled with priority, and the s ubscribers with low SP are scheduled later; while the
forced releas ed subscribers are selected in the order of a low-to-high priority.
The SP is used only in the RNC. It is different from the SPI which can be configured to
Node B and can be used for packet scheduling algorithm.
3.1.7
AP Configuration
The AP involves two application scenarios: It is used to select users in the case of
congestion , which is called congestion cont rol 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, so the configurations of the congestion
control priority and load control priority are different from each ot her. They share the
configuration t able of the AP, but the values may be different. They can be indexed to
different configurations of AP according to the following index numbers in the cell table:
the AP index number for load control is controlled by the parameter of LdCtlPriInde,
while the AP index number for congestion control is controlled by the parameter of
CgtCtlPriIndex.
The AP is mapped from the BP, rate, and bearer type.
11
QoS Feature Guide
However, if the 16 levels of BP are mapped to the AP respectively, there will be a lot of
values. Therefore, the BP should be segmented. BP segmentation determines the
BPSeg of BP by BPSegNum and BPThresh. Therefore, the BP should be mapped to BP
segment at first when the AP mapping is initiated, and multiple BP may be mapped to
one BP segment. Because there are multiple service rates, the rate factor which is taken
into account by the AP has its rate segment.. The downlink RateSeg is detemined by
DlRateAdjLevNum and DlRateA djLev , the uplink RateS eg is detemined by
UlRateAdjLevNum and UlRateA djLev . The current rate of a service should be mapped
to the rate segment before the AP mapping.
The following section will introduce the mapping rules of congestion control priority and
load cont rol priority respectively.
3.1.7.1
Congestion Control Priority

The congestion cont rol priority is used to select a subscriber for rate dec reas e and
schedule the DRBC queue in the congestion control process. It is mapped from the
BPSeg, BearerType, and RateS eg, including 16 levels (0 - 15, with the 15 the highest
level, 0 the lowest).
RNC maps to the congestion control priority based on the above factors in the following
way:
1
Obtain the congestion control AP index number used in the service cell from the
CgtCtlPriIndex in the Utran Cell, and then find the AppPriIndex with the same value
as CgtCtlPriIndex from the AP.
Obtain the BP of RAB according to the method introduc ed in 3.2. 5 BP

Configurations, and then map the BasicPrio to the BPseg.
Map the downlink bit rate to the downlink rate segment and map the uplink bit rate
to the uplink bit segment: Map the R to the RateSeg bas ed on the currently rate (R)
of the service. For DCH services, R indicates the currently allocated rate; For HSPA
S services, it indicates the GBR; For HSPA I/B services, it indicates the nominal bit
rate which is controlled by OMC, HsNormBitRat e is used for downlink and
EdchNormBitRate is used for uplink. The AP varies by the rate.
According to the AppPriIndex, BPseg, RateS eg, direction and BearerType,

congestion control priority is obtained from the AP mapping table pre-configured by
OMC.
Table 3-5
AppP ri Mapping Example (Congestion Control Priority) - AppPriIndex = 1
AppPriIndex
1
Direction
RateSeg
BearerTy pe
12
QoS Feature Guide
AppPriIndex
DCH
HSPA
MBMS
BPSeg
1
11
12
13
14
15
11
12
13
14
15
1(downlink) 3
11
12
13
14
15
10
11
12
13
14
10
11
12
13
14
0(uplink)
Lets use the following example to explain the mapping rules for configuration personnel.
Suppose the related parameters of the request service are as follows:
The ARP assigned by 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.
Suppose that OMC pre-configures the following parameters:
The configurations of BPSegNum and BP Thresh used for BP segmentation are:
BPSegNum = 5, BPThresh = [3, 6, 9, 11]. Based on the BPSegNum and BP Thresh, the
mapping relationship between BP and BPSeg is as follows:
Table 3-6
Mapping Relationship Between BP and BPSeg
BP
BPSeg
10
11
12
13
14
15
The configurations of DlRateAdjLevNum and DlRateAdjLev used for rate segmentation

are: DlRat eAdjLevNum = 4, DlRateA djLev = [8, 64, 128, 384] kbit/s. According to the two
parameters, the mapping relationship between the rate and RateSeg is as follows:
Table 3-7
Mapping Relationship Between Rate and RateS eg (downlink )
Rate (DL)
8~64
64~128
128~384
>384
RateSeg
13
QoS Feature Guide
The configurations of UlRateAdjLevNum and UlRateAdjLev used for rate segmentation

are: UlRateA djLevNum = 3, UlRateA djLev = [16, 64, 384] kbit/s. According to the two
parameters, the mapping relationship between the rate and RateSeg is as follows:
Table 3-8
Mapping Relationship Between Rate and RateS eg (uplink)

Rate(UL)
16
16~64
64~384
>384
RateSeg
After the RAB assignment, the AP to which the RAB maps is obtained in the follow way:
1
CgtCtlPriIndex obtained from the Utran Cell is 1.
The BP is 7 according to the method introduced in 3.2.5 BP Configurations.
According to 0, the BP is in the No. 3 BP segme nt.
The c urrent service downlink bit rat e is 128 kbit/s which is in t he No.4 Rat eSeg
according to 0. The current service uplink bit rate is 128 kbit/s which is in the No.3
RateSeg according to 0.
Based on the Cgt CtlPriIndex= 1, BPseg = 3, RateSeg = 4, direction=1 and

BearerType = DCH, you can find the corresponding downlink congestion control
priority is 3 according t o the pre-configured 0. Based on the Cgt CtlPriIndex= 1,
BPseg = 3, RateSeg = 3, direction=0,and BearerType = DCH, you can find the
corresponding uplink congestion c ontrol priority is 3 according to the pre-configured
0
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 high-priority users to occupy more resources and thus obtain larger bandwidth.
3.1.7.2
Load Control Priority

The load control priority is used to select target subscriber in load control. It is mapped
from the BPSeg, BearerType, and Rat eSeg, including 16 levels (0 - 15, with the 15 the
highest level, 0 the lowest).
RNC maps to the load cont rol priority based on the above factors in the following way:
1
Obtain the load control AP index number used in the service cell from the
LdCtlPriI ndex in the Utran Cell, and then find the AppPriIndex with the same value
as LdCtlPriIndex from the AP.
Obtain the BP of RAB according to the method introduced in 3.2.5 BP

Configurations, and then map the BasicPrio to the BPseg.
14
QoS Feature Guide
Map the downlink bit rat e to the downlink rat e segment and map t he uplink bit rate
to the uplink bit segment: Map the R to the RateSeg bas ed on the currently rate (R)
of the service. For DCH services, R indicates the currently allocated rate; for HSPA
S services, it indicates the GBR; while for HSPA I/B services, it indicates the
nominal bit rate which is controlled by OMC, HsNormBit Rateis used for downlink
and EdchNormBitRate is used for uplink.. The AP varies by the rate.
According to the AppPriIndex, BPseg, RateSeg, direction and BearerType, find the
load cont rol priority from the AP mapping table p re-configured by OMC.
Table 3-9
AppP ri Mapping Example (Load Control Priority)

AppPriIndex
1
BearerType
Direction
1(downlink)
0(uplink)
DCH
RateSeg
HSPA
MBMS
BPSeg
1
11
12
13
14
15
11
12
13
14
15
11
12
13
14
15
10
11
12
13
14
10
11
12
13
14
Because the load cont rol priority and congestion cont rol priority share the same mapping
method, herein we will not explain with example.
When the overload triggers the load control to decrease the load, the subscribers whose
load will be decreased are selected bas ed ton their APs. When a subscriber is selected,
the subscriber can execute: rate dec reas e, forced handover, migration to FA CH, and
release.
3.1.8
The Application of QoS Parameters of
Iu Interface
The QoS Parameters of Iu interfac e include:

Traffic Class: It is used to establish bearer and the mapping of
refer to section 3.1. 5 )
basic priority(Please
Maximum Bit Rate(MBR):Maximum Bit Rate determines the maximum bit rate for R99
services (Refer to ZTE UMTS DRB C Algorithm Feature Guide) and is used in the
15
QoS Feature Guide
process of HSDPA flow control (Please refer to ZTE UMTS HSDPA Pack et Scheduling
Feature Guide) and used to determine the SF for the physical channel of HSUPA (Please
refer to ZTE UMTS HS UPA Introduction Feat ure Guide ) .
Guarant eed Bit Rate(GBR):Guaranteed Bit Rate is available for conversional traffic class
and streaming class services. GBR is us ed in dynamic radio bearer cont rol (Please refer
to ZTE UMTS DRB C Algorithm Feature Guide) HS DPA packet scheduling (Please refer
to ZTE UMTS HSDPA Pack et Scheduling Feature Guide) and HSUPA packet
scheduling (Please refer to ZTE UMTS HS UPA Pack et Scheduling Feature Guide).
Trans fer Delay: It is not used in ZTE RNC.
Traffic Handling Priority: It is used for basic priority mapping, please refer to the
subclause 3.1.5.
SDU Error Ratio: It is not used in ZTE RNC.
Residual Bit Error Ratio: It is not used in ZTE RNC.
Allocation/Retention Priority: It includes 4 IEs:
3.1.9
Priority Level: This parameter indicates the priority of UE and is used in basic
priority mapping.
Pre-emption Capability:This parameter indicates the RAB attribute to pre-empt

other RABs. Please refer to ZTE UMTS Congestion Control Feature Guide.
Pre-emption Vulnerability:The parameter indicates the RAB attribute to be preempted by another RAB. Please refer to ZTE UMTS Congestion Cont rol
Feature Guide.
Queuing Allowed: The parameter indicates the RAB attributes of queueing.

Please refer to ZTE UMTS Congestion Control Feature Guide.
MBR Controlling in RNC

This feat ure relates four cell-level parameters: UlCtrlMB RS witch, UlControledMB R,
DlCtrlMB RS witch, DlControledMB R.
For Uplink MBR operated in RNC:
If the value of UlCt rlMBRS witch is 0: Off , then the Uplink MBR operated in RNC
MBR subscribed in CN
If the value of UlCtrlMB RS witch is 1: Replaced Mode , then the Uplink MBR
operated in RNC = UlControledMBR
If the value of UlCtrlMB RS witch is 2: Minimum Mode , then the Uplink MBR
operated in RNC = min{ MBR subscribed in CN, UlControledMBR }
16
QoS Feature Guide
If the value of UlCtrlMB RS witch is 3: Ma ximum Mode , then the Uplink MBR
operated in RNC = max{ MBR subscribed in CNUlControledMB R }
For Downlink MBR operated in RNC:
If t he value of DlCtrlMBRS witch is 0: Off , then the Downlink MBR operated in RNC
= MBR subscribed in CN
If t he value of DlCtrlMB RS witch is 1: Replaced Mode , then the Downlink MBR

operated in RNC = DlControledMBR
If the value of DlCtrlMB RS witch is 2: Minimum Mode , then the Downlink MBR
operated in RNC = min{ MBR subscribed in CN, DlControledMBR }
If the value of DlCtrlMB RS witch is 3: Ma ximum Mode , then the Downlink MBR
operated in RNC = max{ MBR subscribed in CN, DlControledMB R }
Notes
1.
This feature is only used to modify the MBR in RNC, not related to RAB negotiation
or RAB re-negotiation.
2.
For macro-diversity and mobility state, the value of UlCt rlMBRS witch,
DlCtrlMB RS witch, UlControledMB R, DlControledMB R get the parameter values for
the best cell when RAB Setup, not changing with best cell updating.
Radio QoS differentiated Strategy

Since QoS differentiation of user priorities, the R99, and the HS DPA are finally reflected
by admission control, congestion, and load control, the following will describe how QoS
differentiation is reflected in RRM algorithms.
4.1
QoS Differentiation of Admission Control

Different admission t hresholds can be set in admission control based on BP and
different transmission channels.
Operator can det ermine the degree of difficulty to be admitted for users/services with
different A RPs by setting different admission thresholds for different priorities. For
example, when the load is heavy, Operator can admit users with higher priority and
refuse those with lower priorities, so as to avoid impact on service quality of higherpriority users caused by lower-priority user admission.
Here are some examples.
Assume that 90% TCP resources are occupied in the current system. Two users are
requesting t o be admitted. Ones BP is 7 (higher) and the others BP is 2 (lower). The
DCH downlink admission thresholds are set as follows:
17
QoS Feature Guide
For the det ails about application of DCH downlink admission threshold in admission
control strategy, see ZTE UMTS Admission Control Feature Guide.
Basi cPrio
DchDlAcThre sh
95%
85%
Because the current load of the system is 90% and the admission threshold for users
with BP higher than 2 is 85%, the user cannot be admitted but the user with BP priority
of 7 can be admitted. This achieves the purpose of pres erving resource for higherproperty 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 transm ission
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 user to
be admitted easier or harder t han HSPA user. This reflects differentiation bet ween the
R99 and the HSPA.
4.2
QoS Differentiation of Congestion Control

If the system is congested, differentiation is reflected by scheduling strategies when
resource occupation or queuing user re-admission. The following will describe how to
reflect QoS differentiation in scheduling when resource occupation or queuing user readmission.
4.2.1
Application of QoS Application in Resource Occupation

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 are being used by lower-priority users. This reflects service differentiation
between users.
Resource occupation strategies include forced release and rate decrease. The following
will 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 can release 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 wit hout the preemption
capability and can be released by other RABs forcibly. Basic principle of forced release:
18
QoS Feature Guide
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 service with preemption capability and higher priority will
trigger forced release. The system searches and releases the servic es with lower
priorities whose resources can meet the requirements of services wit h higher priorities,
and then accesses the services wit h higher priorities.
Resource occupation of multiple RABs: (Note: multiple RABs below include CS+PS and
PS+PS)
If the user originating the forced release has multiple RABs, the system needs to
combine the preemption capabilities for the originat or: If one of the RAB has preemption
capability, the originator is considered as having the preemption capability; The system
will use the RAB with 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 originat or will occupies resources occupied by the user.
If t he us er to be released forcibly has multiple RABs, the highest RAB SP is used as the
SP in forced release. Meanwhile, all RABs can be forcibly releas ed only when they are
allowed to be released forced (PV I is pre -emptable).
Resource occupation of HSPA servic es: forced release is carried out according to the
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 condition is met).
If DPCH CE resources are restricted, E-DCH users are also considered as those to be
released forcibly (if the preceding forced release condition is 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. Since 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 t he
forced releas e strategies, see ZTE UMTS Congestion Control Feature Guide.
Here are the examples:
Assume that there are three users in the network: UE 1, UE 2, and UE 3. Now UE4 wants
to be admitted to the net work. However, the network is now congested due to insufficient
radio resources.
19
QoS Feature Guide
The following table lists forced release attributes and SPs of these users (SP 3 higher,
SP 5 lower)
Users
PCI
PVI
SchPrio
UE1
N.
UE2
UE3
N.
13
UE4
From the table, the P CI of UE4 has preemption capability, and the PVIs of UE 1 and UE2
in the online users are allowed to be released forcibly. In addition, priority levels of the
four users are arranged in a descending order: UE4, E2, UE1. Therefore, UE5 with the
highest priority can access the network by forcibly releasing other users. Because the
priority of UE 1 is the lowest, UE is the first to be released forcibly.
4.2.3
Application of QoS in Rate Decrease

When res ources are in congestion (for ex ample, new us ers fail to access the network),
the system can trigger rate decrease of online user to res erve resourc es for new
services or users.
DCH rat e adjustment triggered by the RNC:
Congestion c auses triggering rate to decrease: DP CH code resources, CE congestion,
power congestion, RTWP congestion, that is, the sy stem will trigger rate increase in
case of these resource congestions.
Selection of users whose rate is to be decreased: arrange t he congestion control APs of
RABs of users in a descending order, and decrease the rate starting wit h the service
with the lowest control AP. That is, rate is decreas ed according to RABs.
When resource congestion of a new access user (including handover us ers and
relocation users) in the cell triggers rate decrease, ignore relative priority between the
new access user and the user whose rate to be dec reased or whether the new access
user has preemption capability, ensuring the completion rate of the user.
When a rate increas e request of an online service triggers rate dec rease of other online
services, to ensure equality between users and avoid ping-pong adjustment bet ween the
user requesting rate increase and the user whos e rate is to be dec reased, take into
account the following two factors in the strategy of triggering rate decrease of online
services: comparison bet ween current rate and NB R, 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: uplink NB R is controlled by the
OMC parameter of UlNormBitRate and the downlink NB R by the OMC parameter of
DlNormBitRate. The service with lower AP cannot trigger rate decrease of the service
with higher AP, but the service with higher AP can trigger rate decrease of the service
with lower AP. Additionally, when res ources are congested, the system can distribute
20
QoS Feature Guide
bandwidth to NBR according to BP. This ensures that users with higher priority can
share higher rate services, which reflects user differentiation.
According to the preceding rules, selection of users whose rate is to be decreased in the
rate decrease is based on comparison bet ween APs. And AP reflects ARP. Therefore,
ARP differentiation is reflected in the preceding strategy.
Note: This document mainly describes application of priorities in QoS. For details of the
rate decrease strategies for congestion, see ZTE UMTS Congestion Control Feat ure
Guide.
Suppose that a new user UE4 requires access to the network, 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 MinB Rs of the
four users.
Users
Real-time Rate (kbit/ s)
DlNorm BitRate (kbit/ s)
AppPri
UE1
16
UE2
128
32
UE3
128
32
UE4
64
13
According to the above rule, the AP of UE 1 is the lowest but its real-time rate does not
reach its MinBR, so the system will not select UE1 for rat e decrease. Real -time rates of
UE2 and UE3 are higher than their MinBR and AP of UE2 is lower t han that of UE 3, and
the system will select UE2 to decrease its rate, and provide the disconnected downlink
power resources to UE4 for access.
HSPA rate control reflects differentiation, which is achieved by the SPI. Node B takes
into accounts the SP I difference in scheduling resources. For detailed controlled
strategies, see ZTE UMTS HS DPA Pack et Scheduling Feature Guide
.
4.2.4
Application of QoS in Admission Scheduling

For a user with preemption capability but failed to release forcibly or without preemption
capability but wit h queuing capability, when his service admission is rejected, the system
can place the us er/service in a queue waiting for resources for re-access.
When the service is rejected during DRB C due to state migration, bandwidth
reapplication or redistribution, the system will also plac e the service in a queue triggering
rate decreas e of users with lower priority.
For users in the queue due to these scenarios, schedule them according to their APs to
attempt access or trigger rate decrease, that is, select those with higher priority to
21
QoS Feature Guide
attempt access or trigger rate decrease with priority. This improves successful
completion rate, thus reflecting 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 strategy.
scheduling strategies for congestion, see ZTE UMTS Congestion Control Feature Guide.
Assume that three new call requests are congested. The following table lists the QA
capabilities and AP configurations of these requests (AP 13 higher, AP 2 lower).
Users
QA
SchPrio
UE1
N.
UE2
UE3
13
Because UE1 does not have queuing capability, it cannot be in the queue. UE2 and U3
can wait in the queue. When it is found no radio resource for new users through
measurement, UE3 with higher priority is the first to access the network. If the current
radio resources are not available to the both UEs at the same time, UE2 will have to wait
for next scheduling.
4.3
QoS Differentiation of Load Control

Purpose of load control: when the system is overloaded, it will take measures to restore
the system load to the normal condition, thus ensuring the stability of the system.
Load control have the following means of load reduction: data rate decrease of PS/AMR
service, forced handover, forced IB service handover to the CE LL_FACH, forced c all
drop, etc.
During the process of load reduction, the system does not select the method used for
selecting users to reduc e the load simply according to priority of A RP > 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 t he business emphases of operators in different periods and the
adjustment of operation strategies. It simplifies the procedures as much as possible on
the basis of ease of use and completeness, thus ensuring the operators to adjust the
mapping of the QoS of traffic AP flexibly and satisfying the varying operation
requirements in terms of time and space by using APs for selection.
From the preceding strategy, the AP used in the load control is associated with the BP,
load type, and rate. Therefore, A RP as well as QoS differentiation bet ween the R99 and
the HSPA are reflected in the load control.
22
QoS Feature Guide
load cont rol strategies, see ZTE UMTS Overload Control Feature Guide.
Suppose that the cell is overloaded. There are two online users: UE1 and UE2. Their
APs are 2 and 7 separately (AP 7 higher, AP 2 lower).
Users
AppPri
UE1
UE2
The first load reduction strategy in RNC is rate decrease. The first step is to reduce the
rate of UE 1 with a lower AP. If UE1 is already at its minimum rat e, select UE2 to
decrease its rate. If UE2 is also already at its minimum rate, carry out the next load
reduction means (forced handover). During the forc ed handover, select the user to be
forcibly handed over as in rat e dec reas e means. If forced handover is failed, carry out
migration to the FACH and forced call drop in likewise manner.
4.4
QoS Differentiation of HSDPA serv ice

Scheduling Priority Indicator(SP I)is considered in HSDPA packet scheduling strategy.
The higher t he SP I of the service is, the more opportunity and resources (code and
power) are scheduled by Node B.SPI is mapped from basic priority(BP)whic h reflects the
differentiation bet ween HS DPA services.
For details of the HSDPA packet scheduling strategy, please refer to ZTE UMTS HS DPA
Pack et Scheduling Feature Guide.
4.5
QoS Differentiation of HSUPA serv ice

Scheduling Priority Indicator(SP I)is considered in HSUPA packet scheduling strategy.
The higher the SPI of the service is, the more opportunity and resources are scheduled
by Node B. SPI is mapper from basic priority(BP)which reflects the differentiation
between HSUPA services.
For details of the HSUPA packet scheduling strategy, please refer to ZTE UMTS HS UPA
Pack et Scheduling Feature Guide.
23
QoS Feature Guide
Configuration of Parameters
5.1
Parameter List
5.1.1
Information about Priority and Rate Segments

Abbreviated name
5.1.2
Parameter name
ARPSegNum
ARP Segment Number
ARP Thresh
ARP Segment Threshold
THPSegNum
THP Segment Number
THP Thresh
THP Segment Threshold
BPSegNum
Basic Priority Segment Number
BPThresh
Basic Priority Segment Threshold
EdchNormBitRate
E-DCH Uplink Nominal Bit Rate
HsNormBitRate
HS-DSCH Downlink Nominal Bit Rate
DlRateAdjLevNum
Downlink Rate Adjustment Level Number
DlRateAdjLev
Downlink Rate Adjustment Level
UlRateAdjLevNum
Uplink Rate Adjustment Level Number
UlRateAdjLev
Uplink Rate Adjustment Level
BP Configuration
Abbreviated name
5.1.3
Parameter name
ARPSeg
ARP Segment
TrafficClass
Traffic Class
BasicPrio
Basic Priority
SP Configuration
Abbreviated name
5.1.4
Parameter name
SchPriIndex(Utran Cell)
Scheduling Priority Index
SchPriIndex(Scheduling Priority)
Scheduling Priority Index
BasicPrio
Basic Priority
BearerTy pe
Radio Bearer Ty pe
SchPrio
Scheduling Priority
AP Configuration
Abbreviated name
Parameter name
LdCtlPriIndex
Application Priority Index - Load Control
CgtCtlPriIndex
Application Priority Index - Congestion Control
AppPriIndex
Application Priority Index
24
QoS Feature Guide
5.1.5
BPSeg
Basic Priority Segment
BearerTy pe
Radio Bearer Ty pe
Direction
Service Direction Used in Application Priority

Mapping
RateSeg
Rate Segment
AppPri
Application Priority
MBR Controlling in RNC related parameters

Abbreviated name
Parameter name
UlCtrlMB RS witch
UL Controled MBR Switch
UlControledMBR
UL Controled MBR
DlCtrlMB RS witch
DL Controled MBR S witch
DlControledMBR
DL Controled MBR
5.2
Parameter Configuration
5.2.1
Information about Priority and Rate Segments
5.2.1.1
ARP Segment Number
OMC Path
Path: View -> Configuration Resourc e Tree > OMC -> UTRAN Subnet work XXX -> RNC
Managed Element XXX -> RNC Config Set XXX (Choose the us ed config set) -> QoS
ConfigurationXXX -> Priority and Rate Segment of QoS Advanced Parameter.
Relat ed description:
BP is mapped from both the ARP segment and traffic class. Therefore, before the BP
mapping, the ARP should be divided into several segments. For services of the same
type, even if their A RPs are different, their BPs after mapping are the same if their A RPs
are in the same ARP segment.
Parameter description:
This paramet er indicates the number of s egments of A RP. The larger the number of
segments is, the more precise the BP mapping operation is. However, the mapping
relationship will be more compl ex.
Recommendation: This parameter will affect the sequent priority mappings greatly.
25
QoS Feature Guide
5.2.1.2
ARP Segment Threshold
OMC Path
Path: View -> Configuration Resourc e Tree -> OMC -> UTRAN S ubnetwork XXX -> RNC
ConfigurationXXX -> Priority and Rate Segment Related of QoS Advanced Parameter.
BP is mapped from both the ARP segment and traffic class. Therefore, before the BP
mapping, the ARP should be divided into several segments. For services of the same
type, even if their A RPs are different, their BPs after mapping are the same if their A RPs
are in the same ARP segment.
This paramet er indicates the A RP segment threshold. For example, the parameter value
1 - 5 indicates the all the ARPs with t he value 1 to 5 belong to a same A RP segment.
When the BP mapping is executed, the ARP = 2 and ARP = 3 streaming services have
the same BP.
5.2.1.3
THP Segment Number
OMC Path
ConfigurationXXX -> Priority and Rate Segment of QoS Advanced Parameter.
The BP of an interactive service is mapped from both the THP segment and traffic class.
Therefore, before the BP mapping, the THP should be divided into several segments.
For different interactive s ervices, even if their THP are different, their BPs after mapping
are the same if their THPs are in the same THP segment.
This paramet er indicates the number of segments of THP. The larger t he number of
segments is, the more precise the BP mapping operation is. However, the mapping
relationship will be more complex.
26
QoS Feature Guide
5.2.1.4
THP Segment Threshold
OMC Path
The BP of an interactive service is mapped from both the THP segment and traffic class.
Therefore, before the BP mapping, the THP should be divided into several segments.
For different interactive s ervices, even if their THP are different, their BPs after mapping
are the same if their THPs are in the same THP segment.
This paramet er indicates the THP segment threshold. For example, the parameter value
1 - 5 indicates the all the THP with the value 1 to 5 belong to a same THP segment.
When the BP mapping is executed, the THP = 2 and THP = 3 interactiving services have
the same BP.
Note: None
5.2.1.5
Basic Priority Segment Number
OMC Path
The AP is mapped from three parameters - BPSeg, BearerTy pe, and RateSeg, therefore,
the BP segment should be divided before the AP mapping. For services with same
BearerType and RateSeg, even if their BPs are different, their APs after mapping are the
same if their BPs belong to the same BP segment.
27
QoS Feature Guide
Parameter description
This parameter indicates the number of segments of BP. The larger the number of
segments is, the more precise the mapping operation is. However, the mapping
relationship will be more complex.
Note: None
Recommendation: This parameter will affect the sequent priority mappings to some
extent.
5.2.1.6
Basic Priority Segment Threshold
OMC Path
The AP is mapped from three parameters - BPSeg, BearerTy pe, and RateSeg, therefore,
the BP segment should be divided before the AP mapping. For services with same
BearerType and RateSeg, even if their BPs are different, their APs after mapping are the
same if their BPs belong to the same BP segment.
This paramet er indicates the BP segm ent threshold. For example, the value 1, 5
indicates that the BPs with values from 1 to 5 belong to the same BP segment.
This parameter indic ates the BP segment threshold. For example, the parameter value 1
- 5 indicates the all the BPs with the values from 1 to 5 belong to the same BP segment.
When the AP mapping is executed, the BP = 2 and BP = 3 services map to the same AP
if their BearerTypes and RateS egs are the same.
Note: None
Recommendation: This parameter will affect the sequent priority mappings t o some
extent.
5.2.1.7
Uplink Nominal Bit Rate
OMC Path
28
QoS Feature Guide
The purpose of the NBR configured for I/B services is: The UE admits the service with
NBR; NB R acts as the lowest rate for rate decrease for packet scheduling and loadreduction in congestion. Generally speaking, the NB R of a subscriber with high priority is
high.
This parameter is used to configure the uplink NB Rs of interactive and background
services for each BPs.
Note: This parameter is valid only for the uplink rates of I/B services.
Recommendation: Set appropriate value based on the specific condition.
5.2.1.8
Downlink Nominal Bit Rate
OMC Path
The purpose of the NBR configured for I/B services is: The UE admits the service with
NBR; NB R acts as the lowest rate for rate decrease for packet scheduling and loadreduction in congestion. Generally speaking, the NB R of a subscriber with high priority is
high.
This parameter is used to configure the downlink NBRs of interacti ve and background
Note: This parameter is valid only for the downlink rates of I/B services.
29
QoS Feature Guide
5.2.1.9
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, higher basic priority traffic has higher nominal bit rate. In the
process of NodeB HSUPA quick scheduling, EdchNormBitRate is used as minmum guarantee bit
rate.
This parameter is used to configure the uplink NB Rs of interactive and background
Note: This parameter is valid only for the uplink rates of I/B services.
5.2.1.10
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, higher basic priority traffic has higher nominal bit rate. In the
process of NodeB HSDPA quick scheduling, HsNormBitRate is used as minmum guarantee bit
rate..
This parameter is used to configure the downlink NBRs of interactive and background
30
QoS Feature Guide
Note: This parameter is valid only for the downlink rates of I/B services.
5.2.1.11
Downlink Rate Adjustment Level Number
OMC Path
Adjust the PS services by level when the PS services are established on DCH.
This parameter indicates the number of downlink DB RC rate adjustment levels. It
defines the number of rates which can be selected by downlink DCH services. Generally
speaking, the smaller the paramet er value is, the greater the change of downlink DCH
rate is, and vice versa. The parameter will affect the subscribers using the services
greatly when the PS services are established on DCH.
Note: None
5.2.1.12
Downlink Rate Adjustment Level
OMC Path
Adjust the PS services by level when the PS services are established on DCH.
31
QoS Feature Guide
This parameter indicates the downlink rate adjustment levels used by DRBC. Generally
speaking, the downlink DCH rate adjustment range is limited by this parameter. But the
range may be not limited by this parameter in some special cases (for example, the
guaranteed rates of streaming services are not within the range of the parameter values).
The parameter will affect the subscribers using the services greatly when the PS
services are established on DCH.
Note: None
5.2.2
BP Configuration
5.2.2.1
ARP Segment
OMC Path
ConfigurationXXX -> Basic Priority Configuration Information Advanced Paramet er.
The BP is mapped from both the ARP segment and traffic class.
This parameter indicates the value of ARP segment for mapping.
Note: The ARP segment herein is configured in 4.2.2 and 4.2. 3.
5.2.2.2
Traffic Class
OMC Path
32
QoS Feature Guide
This parameter indicates the traffic class for mapping.
Note: None
5.2.2.3
Basic Priority
OMC Path
This parameter indicates the BP value mapping from specific ARP segment value and
traffic class.
Note: None
Recommendation: Set the parameter based on the specific condition.
5.2.3
SP Configuration
5.2.3.1
Scheduling Priority Index(Utran Cell)
OMC Path
Managed Element XXX -> RNC Config Set XXX (Choos e the used config set) -> RNC
Radio Resource Management -> Utran Cell -> UtranCellXXX -> Modify Advanced
Parameter -> Utran Cell.
33
QoS Feature Guide
SP is mapped from BP and BearerType. The BP is divided into 16 levels, and the radio
bearer has three types (DCH, HSPA, MBMS). There are several diffe rent sets of
configuration of the SP. Different cells can use these sets separat ely according to their
unique index number.
This parameter is used to set the index number of SP global configuration.
Note: None
Recommendation: None
5.2.3.2
Scheduling Priority Index (Scheduling Priority)
OMC Path
ConfigurationXXX -> Scheduling Priority Configuration Information Advanced Parameter.
SP is mapped from BP and BearerType. The BP is divided into 16 levels, and the radio
bearer has three types (DCH, HSPA, MBMS). There are several different sets of
configuration of the SP. Different cells can use these sets separat ely 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
34
QoS Feature Guide
The SP is mapped from the BP and BearerType and used to forced release and real
queue scheduling.
This parameter is used to set the BP value in SP mapping.
Note: None
5.2.3.4
Radio Bearer Type
OMC Path
queue scheduling.
This parameter indicates the radio bearer type in SP mapping.
Note: This parameter can not be configured.
5.2.3.5
Scheduling Priority
OMC Path
35
QoS Feature Guide
queue scheduling.
This parameter is used to set the SP value which is mapped from a specific BP and
BearerType in SP mapping.
Note: None
5.2.4
AP Configuration
5.2.4.1
Application Priority Index- Load Control
OMC Path
Parameter -> Utran Cell.
Obtain the load control AP index number used in the service cell from the LdCtlPriIndex
in the Ut ran Cell, then find the AppP riIndex with the same value as LdCtlPriIndex from
the AP, so as to find the corresponding load control priority.
This parameter is used to set the index number of the load control priority configuration
of the cell.
Note: None
5.2.4.2
Application Priority Index- Congestion Control
OMC Path
36
QoS Feature Guide
Parameter -> Utran Cell
Obtain the congestion control AP index number used in the servi ce cell from the
CgtCtlPriIndex in the Utran Cell, then find the AppP riIndex with the same value as
CgtCtlPriIndex from the AP, so as to find the corresponding congestion cont rol priority.
This parameter is used to set the index number of the congestion control priority
configuration of the cell.
Note: None
5.2.4.3
Application Priority Index
OMC Path
ConfigurationXXX -> Application Priority Advanced Parameter.
The AP is mapped from the BPSeg, BearerType, and RateS eg. Each s et of AP
relationship is identified by an unique index number, and different cells can use this
parameter to index the different sets of the configuration separately.
This parameter is used to set the index number of AP global configuration.
Note: None
Recommendation: Configure according to the practical condition.
5.2.4.4
Basic Priority Segment
OMC Path
37
QoS Feature Guide
The AP is mapped from the BPSeg, BearerType, and RateS eg.
This parameter indicates the BP segment in AP mapping. For details, see 4.2.1.5.
Note: This parameter is used for indication only, and can not 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 in AP mapping.
Note: This parameter is used with BP segment in the following way: BearerType +
BPSeg. For example, DCH1 indicates that the BearerType is DCH, and the BPSeg is 1.
5.2.4.6
Rate Segment
OMC Path
38
QoS Feature Guide
This parameter is used to set the rate segment in AP mapping.
Note: None
5.2.4.7
OMC Path
This parameter is used to set the AP value which is mapped from a specific BPSeg,
BearerType, and RateS eg in AP mapping.
Note: None
5.2.5
MBR Controlling in RNC related parameters
5.2.5.1
UL Controled MBR Switch
OMC Path
39
QoS Feature Guide
Path: View -> Configuration Resource Tree -> OMC -> UTRA N Subnetwork XXX -> RNC
Managed Element XXX -> RNC Config Set XXX (Choose the used config set ) -> RNC
Radio Resource Management -> Utran Cell -> Ut ranCellXXX -> Modify Advanced
Parameter Configuration description:
Specifies the switch for the UL Controled MBR function.
5.2.5.2
UL Controled MBR
OMC Path
Specifies the MBR value in the DL Controled MBR function.
5.2.5.3
DL Controled MBR Switch
OMC Path
Specifies the switch for the DL Controled MBR function.
5.2.5.4
DL Controled MBR
OMC Path
Specifies the MBR value in the DL Controlled MBR function.
40
QoS Feature Guide
Counter And Alarm
6.1
Counter List
This feat ure has no related counter.
6.2
Alarm List
This feat ure has no related alarm.
Glossary
3GPP
3rd Generation Part ners hip Project
A
AP
ARP
Allocation/Retention Priority
B
BP
Basic Priority
D
DCH
Dedic ated Channel
H
HSDPA
High Speed Downlink Packet Access
HSPA
High Speed Packet Access
HSUPA
High Speed Uplink Packet Access
K
Kbps
kilo-bits per second
M
MAC
Media Access Control
41
QoS Feature Guide
NBR
Nominal Bit Rate
Q
QoS
Quality of Servic e
R
RNC
Radio Network Control
RRM
Radio Resource Management
S
SP
Scheduling Priority
T
TC
Traffic Class
THP
Traffic Handling Priority
U
UE
User Equipment
UMTS
Universal Mobile Telecommunication System
W
WCDMA
Wideband Code Division Multiple Access
42

ZTE UMTS QoS Feature Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ZTE UMTS QoS Feature Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

Operator Logo

QoS Feature Guide

QoS Feature Guide

2010 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Function Attribute ............................................................................................... 1

Introduction to Technologies ............................................................................ 4

Radio QoS differentiated Strategy.................................................................. 17

Configuration of Parameters ........................................................................... 24

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Counter And Alarm ........................................................................................... 41

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Mapping Relationship Between BP and BPSeg ................................................... 13

Mapping Relationship Between Rate and RateSeg (downlink) ............................ 13

Mapping Relationship Between Rate and RateSeg(uplink) ................................. 14

Table 3-9 AppPri Mapping Example (Load Control Priority) ................................................. 15

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Overv iew of the Functions

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

RAB QoS Parameters Mapping

MBR Controlling in RNC

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

QoS Mapping for HSDPA Service

QoS Mapping for HSUPA Service

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Code res ources

HSPA subscriber resources(Node B)

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

Logical channel priority

Configuration Scheme of Priorities

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

(Not e: C indicates conversation services, S indicates streaming services, I indicates

Priority Mapping Scheme

MAC logical channel priority

ZTE Confidential Proprietary

(1) When RAB is admitted, RNC obtains admission

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

(1) When forced release is performed bec ause of

When downgrading is performed because of

Configuration of Logical Channel Priority

Logical Channel Priority Mapping

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

QoS Feature Guide

are difined by 3GPP, but they are not only attained