Q72 - ZTE UMTS QoS Feature Description - ZTE

QoS
UMTS RAN
Feature Description
QoS Feature Description
2017 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 of the document is
subjected to change without notice.
ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. I

TABLE OF CONTENTS
1 Function Attribute..................................................................................................... 1
2 Overview.................................................................................................................... 1
2.1 Overview of the Functions.......................................................................................... 1
2.1.1 ZWF21-05-002 RAB QoS Parameters Mapping.........................................................2
2.1.2 ZWF21-05-003 Differentiated Service........................................................................2
2.1.3 ZWF23-05-001 QoS Mapping for HSDPA Service.....................................................3
2.1.4 ZWF25-05-001 QoS Mapping for HSUPA Service.....................................................3
3 Introduction to Technologies..................................................................................3
3.1 Functions Description................................................................................................. 3
3.1.1 Functions of Priorities................................................................................................. 3
3.1.2 Types of Priorities....................................................................................................... 4
3.1.3 Configuration Scheme of Priorities.............................................................................4
3.1.4 Configuration of Logical Channel Priority...................................................................6
3.1.5 BP Configuration......................................................................................................... 7
3.1.6 SP Configuration......................................................................................................... 8
3.1.7 AP Configuration....................................................................................................... 10
3.1.8 The Application of QoS Parameters of Iu Interface.................................................14
4 Radio QoS differentiated Strategy.........................................................................15

4.1 QoS Differentiation of Admission Control.................................................................15
4.2 QoS Differentiation of Congestion Control...............................................................16
4.2.1 Application of QoS Application in Resource Occupation..........................................16
4.2.2 Application of QoS in Forced release.......................................................................16
4.2.3 Application of QoS in Rate Decrease.......................................................................17
4.2.4 Application of QoS in Admission Scheduling............................................................19
4.3 QoS Differentiation of Load Control..........................................................................19
4.4 QoS Differentiation of HSDPA service......................................................................20
4.5 QoS Differentiation of HSUPA service......................................................................20
5 Configuration of Parameters..................................................................................21
5.1 Parameter List.......................................................................................................... 21
5.1.1 Information about Priority and Rate Segments.........................................................21
5.1.2 BP Configuration....................................................................................................... 21
5.1.3 SP Configuration....................................................................................................... 21
5.2 Parameter Configuration.......................................................................................... 22
5.2.1 Information about Priority and Rate Segments.........................................................22
5.2.2 BP Configuration....................................................................................................... 27
5.2.3 SP Configuration....................................................................................................... 29
6 Counter And Alarm.................................................................................................. 34

6.1 Counter List.............................................................................................................. 34
6.2 Alarm List.................................................................................................................. 35
7 Glossary.................................................................................................................... 35
ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. II

Figures and Tables

Figure 1 Priority Mapping Scheme.......................................................................................... 5
Table 1 Logical Channel Priority Mapping.................................................................................6

Table 2 BasicPrio Mapping Example......................................................................................... 8
Table 3 Mapping Relationship Table between the ARP Mapping and ARP Segment
(ARPSeg)...................................................................................................................... 8
Table 4 SchPrio Mapping Example........................................................................................... 9
Table 5 AppPri Mapping Example (Congestion Control Priority) - AppPriIndex = 1................11
Table 6 Mapping Relationship Between BP and BPSeg..........................................................12
Table 7 Mapping Relationship Between Rate and RateSeg (downlink)...................................12
Table 8 Mapping Relationship Between Rate and RateSeg(uplink)........................................12
Table 9 AppPri Mapping Example (Load Control Priority).......................................................13
ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. III
1 Function Attribute
Attribute: Mandatory
Related NEs:
UE NodeB RNC MSCS MGW SGSN GGSN HLR
- - -
Note:
*-: Non-related NE
*: Related NE
Dependency: [None]
Exclusion: [None]
Remarks: [None].
2 Overview
2.1 Overview 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 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 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 with high experience requirements will be handled in
preference. For real-time applications of services, each network element handles
related data as 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:
ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 1

Improve the benefits of operation cost: The QoS mechanism offers effective measures
for network operators to optimize network resources, so the operators are able to satisfy
the requirements of more end users with minimum network resources.
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 different service features
and users requirements, thus realizing different user experiences.
2.1.1 ZWF21-05-002 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 ZWF21-05-003 Differentiated Service

According to traffic class (Traffic Class and THP) and ARP, ZTE defines the BPBasic
Priority, SP(Scheduling Priority), and AP(Application Priority) for intra-RNC radio
resource management, which is not involving the transmission between the NEs.
The priority is just a reference for the inter-UE resource allocation when the radio
resources are insufficient and the congestion is about to happen. Sufficient radio
resources ensure each subscriber with enough radio resources.
The BP reflects the priorities of users and services, 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 obtained 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 the BP, bearer type
and rate of real-time, 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 BP mapping table, you can see the trends of

operation strategy of the user and service priorities. While through the adjustment of AP
mapping table, you can adjust the amount of system resources occupied by high-priority
users and services.
2.1.3 ZWF23-05-001 QoS Mapping for HSDPA Service

RNC maps RAB QoS parameters from CN to the basic priority used in the UTRAN. And
RNC maps basic priority to Scheduling Priority IndicatorSPIfor HSDPA service
2.1.4 ZWF25-05-001 QoS Mapping for HSUPA Service

RNC maps RAB QoS parameters from CN to the basic priority used in the UTRAN. And
RNC maps basic priority to Scheduling Priority IndicatorSPIfor HSUPA service.
3 Introduction to Technologies
3.1 Functions Description
3.1.1 Functions of Priorities

For subscribers connected to the cell, RNC allocates the radio resources based on the
priorities. The configuration of ARP depends on the following factors: ARP assigned by
core network in the service establishment phase, traffic class, THP of I services, radio
channel type, and real-time rate of the subscriber.
The bit rate that the 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 resourcesNode B
HSPA subscriber resources(Node B)
For the radio network, not only the QoS requirements of services should be ensured as
much 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
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.
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 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 introduces 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 interfaces, and
the user-defined priorities used in the RRM algorithm of 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 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/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:
Logical channel priority
BP
SP
AP
3.1.3 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 parameters 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.
(Note: C indicates conversation services, S indicates streaming services, I indicates

interactive services, and B indicates background services.)
Figure 1 Priority Mapping Scheme
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 SPI 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 descriptions.
Priority Function Scenarios
Basic Admission (1) When RAB is admitted, RNC obtains admission
Priority(BP) Control threshold based on BP.
HSDPA Packet (2) For HSDPA, when resources for HSDPA are
Scheduling shared by multiple users, RAN (Node B) will allocate
HSUPA Packet the code and power resources to different HSDPA
Scheduling mobiles according to SPI which is equal to BP.
(3) For HSUPA, when resources for HSUPA are
shared by multiple users, RAN (Node B) will allocate
the grant to different HSUPA mobiles according to

SPI which is equal to BP.

SP of Congestion (1) When forced release is performed because of
RNC(SP) Control 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 Congestion When downgrading is performed because of resource
Priority(AP) Control congestion, RNC will select users to perform
OverLoad downgrading based on AP.
Control When overload happens, RNC will select users to
decrease load based on AP.
For more details about the application of the priorities in radio resource management,
see chapter 4.
3.1.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. 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 user plane of RNC and UE, that is, it is a
considerable factor when the user 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 (SIP) 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.And SIP RAB is interactive RAB
assigned by CN, so Logical Channel Priority of SIP is equal to Logical Channel Priority
of interactive.
Table 1 Logical Channel Priority Mapping
Traffic Class SRB1 SRB2 SRB3 SRB4 C S I B

MLP 1 2 3 4 5 6 7 8
3.1.5 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.

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 network, 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 beyond 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 ARP is segmented by setting the
segment number (ARPSegNum) and segment thresholds (ARPThresh) in OMCR to
determine the segment intervals. The THP is also segmented by segment number
(ARPSegNum) and segment thresholds (THPThresh) to determine the segment
intervals. In addition, THP is valid only for I services. Therefore, it is reflected by the
TrafficClass (Basic 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 (SIP) 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 the
priorities of SIP and other services, the TrafficClass is also added with a SIP value.
Thus, the SIP 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 Voice 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 indicates 'speech ' in 25.413.
2 C_Video is attained according to traffic class IE which indicates 'conversational'

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

Signalling Indication IE which indicates 'signalling ' in 25.413.
After the service assignment, the RNC maps to the BP based on Traffic Class, ARP, and
THP in the following way:
4 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.
5 For a subscriber using I/B services, 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. Obtain the TrafficClass -
Basic Priority based on the THP segment where the service resides.

6 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 2 BasicPrio Mapping Example
TrafficClass
ARP( ARP SIP C_Voi C_Vid S I (THP) B
RAB) Seg ce eo 1~5 6~10 11~1
5
2 1 15 14 14 10 9 8 7 7
7 2 15 13 13 10 6 5 4 4
11 3 15 12 12 10 3 2 1 0
Take the procedure from RAB assignment to obtaining the BP as an example, reference
the parameters pre-configured by OMC and the mapping table.
Obtain the parameter values pre-configured by OMC at first.
The configurations of ARPSegNum and ARPThresh which are used for ARP
segmentation are: ARPSegNum = 3, ARPThresh = [5, 10]. Based on the configurations
of ARPSegNum and ARPThresh, the mapping relationship between ARP and ARP
segment is as follows:
Table 3 Mapping Relationship Table between the ARP Mapping and ARP Segment (ARPSeg)
ARP 1-5 6 - 10 11 - 15
ARPSeg 1 2 3
Suppose a subscriber whose ARP is 2 initiates a request for establishing B services, the
RNC obtains the BP in the following way:
Because the ARP is 2, the ARP segment is 1 (ARPSeg = 1) according to the Table 3 .
Then, according to the ARPSeg and Traffic Class (B) in the Table 2 , the BP of the RAB
is 7.
3.1.6 SP Configuration
When the resource congestion occurs and the 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:
7 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.

8 Obtain the BP of the RAB according to the method introduced in 3.2.5 BP

Configurations.
9 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 4 SchPrio Mapping Example
SchPriIndex
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
Let's use an example to explain the mapping process specifically based on the Table 4
SchPrio 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:
10 SchPrilndex obtained from the Utran Cell is 1.
11 The BP is 7 according to the method introduced in 3.2.5 BP Configurations.

12 The SP of the UE is 8 according to the Table 4 based on the bearer type E-

DCH/HS-DSCH allocated by the RNC.
The SP is used to schedule the call 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 subscribers with low SP are scheduled later; while the
forced released 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 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, so 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 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.
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 DlRateAdjLev , the uplink RateSeg is detemined by
UlRateAdjLevNum and UlRateAdjLev . 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 control priority respectively.
3.1.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
BPSeg, BearerType, and RateSeg, 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:
13 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.

14 Obtain the BP of RAB according to the method introduced in 3.2.5 BP

Configurations, and then map the BasicPrio to the BPseg.
15 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 based 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 DlNormBitRate is used for downlink
and UlNormBitRate is used for uplink. The AP varies by the rate.
16 According to the AppPriIndex, BPseg, RateSeg, direction and BearerType,

congestion control priority is obtained from the AP mapping table pre-configured by
OMC.
Table 5 AppPri Mapping Example (Congestion Control Priority) - AppPriIndex = 1
AppPriIndex
1
BearerType
DCH HSPA MBMS
Direction RateSeg
BPSeg
1 2 3 4 5 1 2 3 4 5 1 2 3 4
1 4 5 6 7 8 5 6 7 8 9 11 12 13 14
2 3 4 5 6 7 4 5 6 7 8 11 12 13 14
1(downlink) 3 2 3 4 5 6 3 4 5 6 7 11 12 13 14
4 1 2 3 4 5 2 3 4 5 6 10 11 12 13
5 0 1 2 3 4 1 2 3 4 5 10 11 12 13
1 3 4 5 6 7 4 5 6 7 8 - - - -
2 2 3 4 5 6 3 4 5 6 7 - - - -
0uplink
3 1 2 3 4 5 2 3 4 5 6 - - - -
4 0 1 2 3 4 1 2 3 4 5 - - - -
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 BPThresh used for BP segmentation are:

BPSegNum = 5, BPThresh = [3, 6, 9, 11]. Based on the BPSegNum and BPThresh, the
mapping relationship between BP and BPSeg is as follows:

Table 6 Mapping Relationship Between BP and BPSeg
BP 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
BPSeg 1 2 3 4 5
The configurations of DlRateAdjLevNum and DlRateAdjLev used for rate segmentation

are: DlRateAdjLevNum = 4, DlRateAdjLev = [8, 64, 128, 384] kbit/s. According to the
two parameters, the mapping relationship between the rate and RateSeg is as follows:
Table 7 Mapping Relationship Between Rate and RateSeg (downlink)
Rate (DL) 8 8~64 64~128 128~384 >384

RateSeg 1 2 3 4 5
The configurations of UlRateAdjLevNum and UlRateAdjLev used for rate segmentation

are: UlRateAdjLevNum = 3, UlRateAdjLev = [16, 64, 384] kbit/s. According to the two
parameters, the mapping relationship between the rate and RateSeg is as follows:
Table 8 Mapping Relationship Between Rate and RateSeg(uplink)
RateUL 16 16~64 64~384 >384

RateSeg 1 2 3 4
After the RAB assignment, the AP to which the RAB maps is obtained in the follow way:
17 CgtCtlPriIndex obtained from the Utran Cell is 1.
18 The BP is 7 according to the method introduced in 3.2.5 BP Configurations.
19 According to Table 6 , the BP is in the No. 3 BP segment.
20 The current service downlink bit rate is 128 kbit/s which is in the No.4 RateSeg
according to Table 7 . The current service uplink bit rate is 128 kbit/s which is in the
No.3 RateSeg according to Table 7 .
21 Based on the CgtCtlPriIndex=1, BPseg = 3, RateSeg = 4, direction=1 and

BearerType = DCH, you can find the corresponding downlink congestion control
priority is 3 according to the pre-configured Table 5 . Based on the
CgtCtlPriIndex=1, BPseg = 3, RateSeg = 3, direction=0,and BearerType = DCH,
you can find the corresponding uplink congestion control priority is 3 according to
the pre-configured Table 5
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 RateSeg, including 16 levels (0 - 15, with the 15 the
highest level, 0 the lowest).
RNC maps to the load control priority based on the above factors in the following way:
22 Obtain the load control AP index number used in the service cell from the
LdCtlPriIndex in the Utran Cell, and then find the AppPriIndex with the same value
as LdCtlPriIndex from the AP.
23 Obtain the BP of RAB according to the method introduced in 3.2.5 BP

Configurations, and then map the BasicPrio to the BPseg.
24 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 based 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 DlNormBitRate is used for downlink
and UlNormBitRate is used for uplink.. The AP varies by the rate.
25 According to the AppPriIndex, BPseg, RateSeg, direction and BearerType, find the
load control priority from the AP mapping table pre-configured by OMC.
Table 9 AppPri Mapping Example (Load Control Priority)
AppPriIndex
1
BearerType
DCH HSPA MBMS
Direction RateSeg
BPSeg
1 2 3 4 5 1 2 3 4 5 1 2 3 4
1 4 5 6 7 8 5 6 7 8 9 11 12 13 14
2 3 4 5 6 7 4 5 6 7 8 11 12 13 14
1(downlink) 3 2 3 4 5 6 3 4 5 6 7 11 12 13 14
4 1 2 3 4 5 2 3 4 5 6 10 11 12 13
5 0 1 2 3 4 1 2 3 4 5 10 11 12 13
1 3 4 5 6 7 4 5 6 7 8 - - - -
2 2 3 4 5 6 3 4 5 6 7 - - - -
0uplink
3 1 2 3 4 5 2 3 4 5 6 - - - -
4 0 1 2 3 4 1 2 3 4 5 - - - -
Because the load control priority and congestion control 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 based ton their APs. When a subscriber is selected,

the subscriber can execute: rate decrease, forced handover, migration to FACH, and
release.
3.1.8 The Application of QoS Parameters of Iu Interface

The QoS Parameters of Iu interface include:
Traffic Class It is used to establish bearer and the mapping of basic priority(Please
refer to section 3.1.5
Maximum Bit RateMBRMaximum Bit Rate determines the maximum bit rate for
R99 services (Refer to ZTE UMTS DRBC Algorithm Feature Description) and is used in
the process of HSDPA flow control (Please refer to ZTE UMTS HSDPA Packet
Scheduling Feature Description) and used to determine the SF for the physical channel
of HSUPA(Please refer to ZTE UMTS HSUPA Introduction Feature Description ) .
Guaranteed Bit Rate(GBR)Guaranteed Bit Rate is available for conversional traffic

class and streaming class services. GBR is used in dynamic radio bearer control
(Please refer to ZTE UMTS DRBC Algorithm Feature Description) HSDPA packet
scheduling (Please refer to ZTE UMTS HSDPA Packet Scheduling Feature Description)
and HSUPA packet scheduling (Please refer to ZTE UMTS HSUPA Packet Scheduling
Feature Description).
Transfer 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:
Priority LevelThis parameter indicates the priority of UE and is used in

basic priority mapping.
Pre-emption CapabilityThis parameter indicates the RAB attribute to pre-

empt other RABs. Please refer to ZTE UMTS Congestion Control Feature
Description.
Pre-emption VulnerabilityThe parameter indicates the RAB attribute to be

pre-empted by another RAB. Please refer to ZTE UMTS Congestion
Control Feature Description.
Queuing AllowedThe parameter indicates the RAB attributes of queueing.

Please refer to ZTE UMTS Congestion Control Feature Description.
4 Radio QoS differentiated Strategy

Since QoS differentiation of user priorities, the R99, and the HSDPA 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 thresholds can be set in admission control based on BP and
different transmission channels.
Operator can 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, Operator can admit users with higher priority and
refuse those with lower priorities, so as to avoid impact on service quality of higher-
priority 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 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, see ZTE UMTS Admission Control Feature Description.
BasicPrio DchDlAcThresh
7 95%
2 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 preserving resource for higher-
property 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 user to
be admitted easier or harder than HSPA user. 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 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 re-
admission.
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 without the preemption
capability and can be released by other RABs forcibly. Basic principle of forced release:
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 services with lower
priorities whose resources can 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 the user originating the forced release has multiple RABs, the system needs to
combine the preemption capabilities for the originator: 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 originator will occupies resources occupied by the
user.
If the user 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 released only when they are
allowed to be released forced (PVI is pre-emptable).
Resource occupation of HSPA services: 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 the
forced release strategies, see ZTE UMTS Congestion Control Feature Description.
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 (SP 3 higher,
SP 5 lower)
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 UE1 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 UE1 is the lowest, UE is the first to be released forcibly.
4.2.3 Application of QoS in Rate Decrease

When resources are in congestion (for example, new users fail to access the network),
the system can trigger rate decrease of online user to reserve resources for new
services or users.
DCH rate adjustment triggered by the RNC:
Congestion causes triggering rate to decrease: DPCH code resources, CE congestion,

power congestion, RTWP congestion, that is, the system will trigger rate increase in
case of these resource congestions.
Selection of users whose rate is to be decreased: arrange the congestion control APs of
RABs of users in a descending order, and decrease the rate starting with the service
with the lowest control AP. That is, 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, ignore relative priority between the
new access user and the user whose rate to be decreased or whether the new access
user has preemption capability, ensuring the completion rate of the user.
When a rate increase request of an online service triggers rate decrease of other online
services, to ensure equality between users and avoid ping-pong adjustment between
the user requesting rate increase and the user whose rate is to be decreased, take into
account the following two factors 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: uplink NBR is controlled by the
OMC parameter of UlNormBitRate and the downlink NBR 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 resources are congested, the system can distribute
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 between APs. And AP reflects ARP. Therefore,
ARP differentiation is reflected in the preceding strategy.
rate decrease strategies for congestion, see ZTE UMTS Congestion Control Feature
Description.
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 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 rule, the AP of UE1 is the lowest but its real-time rate does not
reach its MinBR, so the system will 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 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 SPI difference in scheduling resources. For detailed controlled
strategies, see ZTE UMTS HSDPA Feature Description.
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 with queuing capability, when his service admission is rejected, the
system can place 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 will also place the service in a queue
triggering rate decrease 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
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
Description.

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. 2
UE2 Y 7
UE3 Y 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 CELL_FACH, forced call
drop, etc.
During the process of load reduction, the system does not select the method used for
selecting users to reduce the load simply according to 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 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, ARP as well as QoS differentiation between the R99 and
the HSPA are reflected in the load control.
load control strategies, see ZTE UMTS Overload Control Feature Description.
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 2
UE2 7
The first load reduction strategy in 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, 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 forced handover, select the user to be

forcibly handed over as in rate decrease 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 service

Scheduling Priority IndicatorSPIis considered in HSDPA packet scheduling strategy.
The higher the SPI of the service is, the more opportunity and resources (code and
power) are scheduled by Node B.SPI is mapped from basic priority(BP)which reflects
the differentiation between HSDPA services.
For details of the HSDPA packet scheduling strategy, please refer to ZTE UMTS HSDPA
Packet Scheduling Feature Description.
4.5 QoS Differentiation of HSUPA service

Scheduling Priority IndicatorSPIis 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 HSDPA packet scheduling strategy, please refer to ZTE UMTS HSUPA
Packet Scheduling Feature Description.
5 Configuration of Parameters
5.1 Parameter List
5.1.1 Information about Priority and Rate Segments

Abbreviated name Parameter name
ARPSegNum ARP Segment Number
ARPThresh ARP Segment Threshold
THPSegNum THP Segment Number
THPThresh THP Segment Threshold
BPSegNum Basic Priority Segment Number
BPThresh Basic Priority Segment Threshold
UlNormBitRate Uplink Nominal Bit Rate
DlNormBitRate 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

ARPSeg ARP Segment
TrafficClass Traffic Class
BasicPrio Basic Priority
SchPriIndex(Utran Cell) Scheduling Priority Index
SchPriIndex(Scheduling Priority) Scheduling Priority Index
BasicPrio Basic Priority
BearerType Radio Bearer Type
SchPrio Scheduling Priority
LdCtlPriIndex Application Priority Index - Load Control
CgtCtlPriIndex Application Priority Index - Congestion Control
AppPriIndex Application Priority Index
BPSeg Basic Priority Segment
BearerType Radio Bearer Type
Service Direction Used in Application Priority
Direction
Mapping
RateSeg Rate Segment
AppPri Application Priority
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 Resource Tree > OMC -> UTRAN Subnetwork304 -> RNC
Managed Element$304 -> RNC Config Set1 (Choose the used config set) -> QoS
Configuration304 -> Priority and Rate Segment Related QoS Configuration
Parameter Configuration
Related 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 ARPs are different, their BPs after mapping are the same if their
ARPs are in the same ARP segment.
Parameter description:
This parameter indicates the number of segments of ARP. The larger the number of
segments is, the more precise the BP mapping operation is. However, the mapping
relationship will be more complex.
Recommendation: This parameter will affect the sequent priority mappings greatly.
5.2.1.2 ARP Segment Threshold
OMC Path
Path: View -> Configuration Resource Tree -> OMC -> UTRAN Subnetwork304 -> RNC
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 ARPs are different, their BPs after mapping are the same if their
ARPs are in the same ARP segment.
This parameter indicates the ARP segment threshold. For example, the parameter
value 1 - 5 indicates the all the ARPs with the value 1 to 5 belong to a same ARP
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
Configuration304 -> Priority and Rate Segment Related QoS Configuration.
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 services, even if their THP are different, their BPs
after mapping are the same if their THPs are in the same THP segment.
This parameter indicates the number of segments of THP. The larger the number of
segments is, the more precise the BP mapping operation is. However, the mapping
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 services, even if their THP are different, their BPs
after mapping are the same if their THPs are in the same THP segment.
This parameter 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, BearerType, 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.
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
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, BearerType, 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 parameter indicates the BP segment 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 indicates 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 RateSegs are the same.
Note: None
Recommendation: This parameter will affect the sequent priority mappings to some
extent.
5.2.1.7 Uplink Nominal Bit Rate
OMC Path

The purpose of the NBR configured for I/B services is: The UE admits the service with
NBR; NBR acts as the lowest rate for rate decrease for packet scheduling and load-
reduction in congestion. Generally speaking, the NBR of a subscriber with high priority
is high.
This parameter is used to configure the uplink NBRs 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; NBR acts as the lowest rate for rate decrease for packet scheduling and load-
reduction in congestion. Generally speaking, the NBR of a subscriber with high priority
is high.
This parameter is used to configure the downlink NBRs of interactive and background
services for each BPs.
Note: This parameter is valid only for the downlink rates of I/B services.
5.2.1.9 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 DBRC rate adjustment levels. It
defines the number of rates which can be selected by downlink DCH services.
Generally speaking, the smaller the parameter 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.10 Downlink Rate Adjustment Level
OMC Path
Adjust the PS services by level when the PS services are established on DCH.
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.1 ARP Segment
OMC Path
Configuration304 -> Basic Priority Configuration Information Advanced Parameter.
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
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.1 Scheduling Priority Index(Utran Cell)
OMC Path
Managed Element$304 -> RNC Config Set1 (Choose the used config set) -> RNC
Radio Resource Management Utran Cell UtranCellxx Modify Advanced
Parameter Utran Cell
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 separately 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

Configuration304 -> 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 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 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
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.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 Utran Cell, then find the AppPriIndex 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
Parameter Utran Cell
Obtain the congestion control AP index number used in the service cell from the
CgtCtlPriIndex in the Utran Cell, then find the AppPriIndex with the same value as
CgtCtlPriIndex from the AP, so as to find the corresponding congestion control 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
Configuration304 -> Application Priority Configuration Information Advanced Parameter.

The AP is mapped from the BPSeg, BearerType, and RateSeg. Each set 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
The AP is mapped from the BPSeg, BearerType, and RateSeg.
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
This parameter is used to set the rate segment in AP mapping.
Note: None
5.2.4.7 Application Priority
OMC Path
This parameter is used to set the AP value which is mapped from a specific BPSeg,
BearerType, and RateSeg in AP mapping.
Note: None

6 Counter And Alarm
6.1 Counter List

This feature has no related counter.
6.2 Alarm List

This feature has no related alarm.
7 Glossary
3GPP 3rd Generation Partnership Project
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
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

Q72 - ZTE UMTS QoS Feature Description - ZTE

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Q72 - ZTE UMTS QoS Feature Description - ZTE

Загружено:

Авторское право:

Доступные форматы

QoS

QoS Feature Description

2017 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. I

4 Radio QoS differentiated Strategy.........................................................................15

6 Counter And Alarm.................................................................................................. 34

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. II

Figures and Tables

Table 1 Logical Channel Priority Mapping.................................................................................6

2.1 Overview of the Functions

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

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 1

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

2.1.1 ZWF21-05-002 RAB QoS Parameters Mapping

2.1.2 ZWF21-05-003 Differentiated Service

The SP and AP are obtained based on the BP.

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 2

2.1.3 ZWF23-05-001 QoS Mapping for HSDPA Service

2.1.4 ZWF25-05-001 QoS Mapping for HSUPA Service

3.1 Functions Description

3.1.1 Functions of Priorities

HSPA subscriber resources(Node B)

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 3

3.1.2 Types of Priorities

Logical channel priority

3.1.3 Configuration Scheme of Priorities

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 4

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

Figure 1 Priority Mapping Scheme

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 5

SPI which is equal to BP.

3.1.4 Configuration of Logical Channel Priority

Table 1 Logical Channel Priority Mapping

Traffic Class SRB1 SRB2 SRB3 SRB4 C S I B

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 6

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

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

3 SIP is attained according to traffic class IE which indicates 'interactive' and

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 7

Table 2 BasicPrio Mapping Example

Obtain the parameter values pre-configured by OMC at first.

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 8

8 Obtain the BP of the RAB according to the method introduced in 3.2.5 BP

Table 4 SchPrio Mapping Example

The ARP assigned by RAB in service establishment is 2;

The UE requests B services.

The RNC allocates services for HSPA.

10 SchPrilndex obtained from the Utran Cell is 1.

11 The BP is 7 according to the method introduced in 3.2.5 BP Configurations.

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 9

12 The SP of the UE is 8 according to the Table 4 based on the bearer type E-

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

3.1.7.1 Congestion Control Priority

ZTE Confidential Proprietary 2008 ZTE Corporation. All rights reserved. 10

14 Obtain the BP of RAB according to the method introduced in 3.2.5 BP

16 According to the AppPriIndex, BPseg, RateSeg, direction and BearerType,

Table 5 AppPri Mapping Example (Congestion Control Priority) - AppPriIndex = 1

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: