WO - NAST3018 - E01 - 1 UMTS QoS Management 50P

UMTS QoS Management
ZTE University
Contents
 UMTS QoS Architecture

 QoS Policy of Radio Network Layer
 QoS Policy of Transport Network Layer
 QoS Application and Monitoring
Requirement of QoS Management
 Flat tariffs boosts the mobile broadband services by

astonishing speed
 New radio technology (HSPA/HSPA+/LTE)
can’t keep pace with the growth of mobile PS
services.
 QoS management strategy has to be deployed
to control the usage and protect capital
investment
 Too many service and too many access
technologies make the QoS management complex
and hard to control for operators
 Voice , Video call , Streaming, WWW, FTP , etc.
 R99 DCH, HSUPA, HSDPA, etc.
Requirements of developing Multi-Service, enhancing ARPU and

Competition
© ZTE Corporation. All rights reserved
Significance of QoS
 The objective of realizing guarantee mechanism of QoS
 Provide differentiated service resource and guaranteed quality,
realize different user experience for different characteristic of service
and requirement of user
 The benefit of realizing guarantee mechanism of QoS
 Increase operator's income of OPEX :mechanism of QoS can provide
efficient way for optimizing the resources of network for operator, it

enable operator using minimal resource of network to meet the
requirements of maximum users
 Acquire new gain-up point of income: mechanism of QoS can
provide more value-added service for operator, it make possible of

users using more complicated application (generally, these services
require higher QoS), offer better service for senior user, represent the
differentia of its network from other and realize individual service,
improve the loyalty of user by enhancing the satisfaction of senior
user

QoS Monitoring-UMTS KPI System
UMTS KPI
Coverage Accessability Retainability Service Integrity Mobility Delay/Latency
•Coverage •WCDMA •Call Drop •Voice Quality •Soft •Attach Setup Time
Ratio Availability Ratio (MOS) Handover
•PDP Context
(RSCP and (Voice, Success
•Attach Success •Video Phone Activation Time
EcIo) Video Ratio
Ratio (Synchronization
Phone) •Service Access Time
•Soft between voice •Hard
•Service Access
Handover •PDP and image ) Handover •End-to-end Access
Success Ratio
Ratio Context Success Time
(MO-Voice, Video •Service UL/DL
Drop Ratio Ratio
•Pilot Phone, SMS) BLER (Voice, •Packet Round Trip
Pollution •Date Video Phone) •Inter-RAT Time (Initial/
•End-to-end
Ratio Transfer Handover Continuous Ping)
Access Success •PS Mean
Drop Ratio Success
Ratio (MT-Voice, Throughput (RLC •Transfer Interruption
Ratio
Video Phone, – 64K / 128K / Time
SMS) 384K /HSPA)
•PDP Context
Activation Success
Ratio

UMTS QoS Reference Model
UMTS Bearer Service
QOS Negotiate
RNC SGSN GGSN PCRF
IP Bearer Internet/SP
IP Bearer Network
Network
Backbone Bearer Service Backbone Bearer Service
Radio Bearer Service IU/S1 Bearer Service External Bearer Service

QoS applied in Core network-Adjusting QoS
instantly
Service Bandwidth Control-Based on PCRF
Use case 1 ：
Restrict P2P service Method:
bandwidth by service PCRF send service
Bandwidth
access time bandwidth control
policy by service
type to GGSN, and
60%
P2P
GGSN implement
SPR/HSS Time P2P
service bandwidth
PCRF Other Services 90% control sent from
PCRF
ISAG
GGSN
Advantages:
GGSN Video Streaming
SGSN
SGSN •Reasonable use of
RNC operators'
resources.
Mobi TV •Ensure enough
network resource
for preferred
VOIP
Bandwidth
services and meet

Use case 2: subscriber
Ensure bandwidth for streaming experience
streaming
conversation media and conversational services
default

Mapping of QoS Parameter
UE maps application need to UMTS QoS Profile
Option 1>SGSN or MSC maps UMTS QoS Profile/ Subscriber’s QoS Profile from HLR to
RAB QoS
Option 2>PCRF maps the service information received into Authorized IP QoS parameters to
GGSN, then the GGSN maps these QoS parameters to UMTS QoS parameters.
(RAB assignment parameters)
RNC maps RAB QoS to RB QoS

(WCDMA L1/L2 parameters)
BTS manager Iub CAC Iu-CS CAC

reserves resource reserves Iu-PS IP Traffic
reserves
for RB resource for RB management
resource for RAB
 UE maps the service application attribute to the UMTS bearer attribute

 SGSN and MSC map the UMTS bearer attribute to RAB service attribute
 RNC maps RAB QoS parameters to RB service and Iu Bearer service
QoS Management for Multi-Services
•Network Initiated QoS QoS control based on PCC which
negotiation can transfer service QoS
•Secondary PDP activation requirement from application level
QoS information can be to bear level.
transferred to relative entity in
3GPP network
RNS PCRF
Cooperative office
Gx Rx P-CSCF
ATM Data conference
RNS Backbone IP Backbone
GGSN VOIP/Centrex
SGSN DiffServ
Video Conference
DiffServ

Contents

KEY QoS Attributes for RAN
CN transfers QoS attribute to RNC
 Traffic class
 Maximum Bit Rate
 Guaranteed Bit Rate ： class
 Traffic Handling Priority
 Allocation/Retention Priority
 Priority Level
 Pre-emption Capability
 Pre-emption Vulnerability
 Queuing Allowed
 Each application can map to one traffic class
 Radio network is limited by capability of radio interface, so QoS classes can
not complicatedly differentiated like fixed network
 Differentiation is mostly based on sensitivity to delay
QoS Differentiation
 User priority differentiation
 Priority differentiation among different users can be reflected by
Allocation/Retention Priority-> priority level ， for example, by setting
gold, silver, bronze priority, when system resource is congestion, the QoS of
higher priority user can be guaranteed by victimizing the QoS of lower
priority user.
 Also user priority include traffic handling priority which is valid for interactive
service, Pre-emption Capability, Pre-emption Vulnerability and Queuing
Allowed
 Service priority differentiation
 The relation of service priority is conversation> streaming >interactive
>background based on different service attribute

QoS Policy of Radio network Layer
DCH
FACH/RACH
OMC
HSDPA/E-DCH
Configuration Management
SP
TC MLP
ARP 1 BP
CmChPI
CA
THP LC CC PS FC
C
2
NBR
Bearer Type
(DCH/HSPA/MBMS)
3 CACP
Data Rate CCP/LCP
Radio Resources
Code Resources
DL Power Resources
UL Interference Resources
CE Resources
Other Resources(Maximum Allowable
Users)
By Doujw

Flexible Basic Priority Mapping Sample

Flexible Scheduling Priority Mapping Sample
SchPriIndex
RNC RNC 1
BasicPrio
Inner Interface BearerType
0(DCH) 1(HSPA) 2(MBMS)
0 0 1 2
1 1 2 3
2 2 3 4
3 3 4 5
4 4 5 6
BP 5 5
SP
6 7
6 6 7 8
Bearer Type
7 7 8 9
8 8 9 10
9 16 levels(0~15), 159 is the 10 11
10 highest level, 0 is the
10 lowest 11 12
11 level 10 11 12
12 11 12 13
13 12 13 14
14 13 14 15
15 14 15
SP Mapping Table
15

Flexible CCP/LCP Mapping Sample
RNC RNC
Inner Interface
16 levels(0~15), 15 is
BP the highest level, 0 is
Bearer Type CCP/ the lowest level
LCP
Data Rate
CCP/LCP Mapping Table
AppPriIndex
1
BearerType
0(DCH) 1(HSPA) 2(MBMS)
RateSeg
BPSeg
1 2 3 4 5 1 2 3 4 5 1 2 3 4 5
1 4 5 6 7 8 5 6 7 8 9 11 12 13 14 15
2 3 4 5 6 7 4 5 6 7 8 11 12 13 14 15
3 2 3 4 5 6 3 4 5 6 7 CCP/LCP
11 12 13Mapping
14 15
4 1 2 3 4 5 2 3 4 5 6 10 11
Table
12 13 14
5 0 1 2 3 4 1 2 3 4 5 10 11 12 13 14

Summary of Scenarios applied for BP, SP ,CCP
and LCP
Priority Function Scenarios
Basic Priority Admission Control (1) When RAB is admitted, RNC obtains admission
(BP) HSDPA Packet threshold based on BP.
Scheduling (2) For HSDPA, when resources for HSDPA are shared by
HSUPA Packet multiple users, RAN (Node B) will allocate the code and
Scheduling power resources to different HSDPA 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 RNC (SP) Congestion (1) When forced release is performed because of resource
Control congestion, RNC will select users to perform forced release
based on SP.
(2) When queuing 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 Control congestion, RNC will select users to perform downgrading
(CCP/LCP) OverLoad Control based on CCP.
When overload happens, RNC will select users to decrease
load based on LCP.
QoS Differentiation of Admission Control
The admit threshold is highest for
gold user and gold user is first to
UE with highest priority (eg. Admit Threshold is be scheduled in the queue, so
gold user is easy to be accessed
Gold user ) 90% in the network when load is high.
The admit threshold is between

gold user and bronze user for
silver user and silver user is to be
scheduled inferior to gold user in
UE with higer priority(eg. Admit Threshold is the queue, so the access
successful ratio for silver user is
Silver user) 80%
between gold user and bronze
user when load is high.
The admit threshold is lowest for

bronze user and bronze user is
last to be scheduled in the queue,
UE with low priortiy(eg. Admit Threshold is so bronze user is difficult to be
Bronze user) 70% accessed in the network when
load is high.
Operator can determine the degree of difficulty to be admitted for users/services

with different ARPs and by setting different admission thresholds for different
priorities (CACP- which is equal to BP.)

QoS Differentiation of Congestion Control
When resource is congestion,
bronze user may to be force
To force release low release by gold user to
The new access user which
priority user which guarantee gold user to access
may trigger pre-emption
may be pre-empted successfully.

the new access user and
To trigger online handover user may trigger
The new access user and online user to downgrade in
user
handover user order to improve access
to downgrade successful ratio.

To trigger online the throughput of gold user is
higher the throughput of silver
user which priority
The high priority user online user and the throughput of
is low to silver user is higher the
downgrade throughput of bronze user.
When resource is congestion , RNC will perform force release RAB which may be pre-
empted and trigger online user which priority (CCP) is low to downgrade, in order to
guarantee the QoS of higher priority users and improve the access successful ratio

QoS Differentiation of Load Control
Bronze user will be selected
to decrease cell load first
, so
UE with low priority
(eg. the QoS of bronze user will
Bronze user) not be guaranteed first.
Siler user will be selected to

UE with higher priority
(eg. decrease cell load secondly.
Overload Silver user)
happen
Gold user will be selected to

decrease cell load last, so the
UE with highest priority(eg. QoS of gold user will be
Gold user ) guaranteed first .
When cell is overload, RNC will select users whose LCP is lowest to decrease cell
load
QoS Differentiation of Packet Scheduling
The scheduling Gold user will attain highest
UE with highest priority (eg.
priority throughput.
Gold user )
indicator(SPI) is 6
Silver user will attain the

The scheduling
UE with higer priority(eg. throughput which is
priority between gold user and
Silver user)
indicator(SPI) is 4 bronze user.
UE with low priortiy(eg. The scheduling Bronze user will attain

Bronze user) priority lowest throughput.
indicator(SPI) is 2
Scheduling Priority Indicator （ SPI ） is considered in HSDPA/HSUPA 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/HSUPA
services
Application Example of QoS
CSL Network
SPI=6 SPI=4 SPI=4
(Interac (BackG (BackGr
tive) round) ound)
Users of other 3*DP
Operator Users operator Roam Users
purchased
A
7.2M 2.53M 1.89M 1.84M
3*UP
A
Gold Users Silver Users Bronze Users
1.9M 1.15M 723.3K 725.4K
3*64
QAM 5.52M 3.15M 3.68M
Voice Video
PS
Streaming(n
PS PS CSL Test Result
Interactive BackGround
ot used)
 There are multi-users and multi-traffic in

the example. The priority can be
configured in OMC in ZTE network and
these priority will be reflected in each
RRM algorithm, So complex QoS of
operator can be fulfilled.

Priority Configuration for CS Service
 In order to reflect QoS differentiation among the CS services

which have different priority, the priority information in HLR
needs to be configured in advance.
Emergency High priority Medium Lower

call UE (gold user) priority UE priority UE
(silver user) (bronze user)
Priority 1 2 7 11
Queuing Y Y Y Y
Pre-emption Y Y N N
Capability
Pre-emption N N Y Y
Vulnerability

Priority Configuration for PS Service
 In order to reflect QoS differentiation among the PS services which have different
priority, the priority information in HLR needs to be configured in advance.
Subscriber HLR HLR HLR SGSN SGSN SGSN Pre-emption Pre- Queui Usages
Priority Class APR Traffic THP APR Traffic THP Capability emption ng
Class Class Vulnerabli
ty
B-Gold 1 Backgrou - 2 BG - N Y Y High priority of

nd background traffic
B-Silver 2 Backgrou - 7 BG - N Y Y Medium priority of

B-Bronze 3 Backgrou - 11 BG - N Y Y Low priority of

I-Gold 1 Interactiv 1 2 I 1 N Y Y High priority of

e interactive traffic
I-Silver 2 Interactiv 2 7 I 2 N Y Y Medium priority of

I-Bronze 3 Interactiv 3 11 I 14 N Y Y Low priority of


Basic Priority Mapping Example
TrafficClass
5(Inter 6(Inter
3 （ bac 4(Inter
ARP ARP 0 （ voi 2 （ Stre active active 19 （ S
1(video) kgroun active
(RAB) Seg ce ） am ） 6～ 11 ～ IP ）
d） 1 ～ 5)
10) 15)
2 1 14 14 10 4 6 5 4 15
7 2 13 13 10 2 5 4 3 15
11 3 12 12 10 0 4 4 3 15

Scheduling Priority 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
CCP/LCP Mapping Example
AppPriIndex
1
D R BearerType
ir a
0 （ DCH ） 1(HSPA) 2(MBMS)
e t
c e BPSeg
ti S
o e 1 2 3 4 5 6 7 8 9 1 2 3 4 5 6 7 8 9 1 2 3 4 5 6 7 8 9
n g
1 1 1 1 1 1 1 1 1 1 1 1 1
1
4 5 6 7 8 9 0 1 2 5 6 7 8 9 0 1 2 3 7 8 9 0 1 2 3 4 5
1 1 1 1 1 1 1 1 1 1
2
3 4 5 6 7 8 9 0 1 4 5 6 7 8 9 0 1 2 6 7 8 9 0 1 2 3 4
D 1 1 1 1 1 1 1
3
L 2 3 4 5 6 7 8 9 0 3 4 5 6 7 8 9 0 1 5 6 7 8 9 0 1 2 3
1 1 1 1
4
1 2 3 4 5 6 7 8 9 2 3 4 5 6 7 8 9 0 4 5 6 7 8 9 0 1 2
1 1
5
0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 9 3 4 5 6 7 8 9 0 1
1 1 1 1 1
1
3 4 5 6 7 8 9 0 1 4 5 6 7 8 9 0 1 2 - - - - - - - - -
1 1 1
2
U 2 3 4 5 6 7 8 9 0 3 4 5 6 7 8 9 0 1 - - - - - - - - -
L
1
3
1 2 3 4 5 6 7 8 9 2 3 4 5 6 7 8 9 0 - - - - - - - - -
4 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 9 - - - - - - - - -

Contents

Flow Classification & Mapping to TNL: ATM
Mapping
User Plane
Control Management
Plane Plane
Common Channel
I/B
SRB,CS, I/B(HSPA)
Streaming(R’99/MBM (R’99/MBMS)
S)
RT NRT1 NRT2
CBR rt-VBR UBR+ nrt-VBR UBR
Mapping by default
Mapping optional

Flow Classification & Mapping to TNL: IP
Mapping
TC
User Basic priority Bearer Type

Plane THP C (1~15) (R99/HSPA/MBMS)
ARP
C
Control
Plane C DSCP
VLAN/pbits
Management
(COS)
Plane C
C Configurable Mapping
Flow Classification & Mapping to TNL: IP
Mapping IPDSCP COS
0~7 0
 ZTE support maximum 256 cases, the different NodeB
8~15 1
or RNC can adopt corresponding mapping strategies to
16~23 2
different cases 24~31 3
 The mapping from IPDSCP to COS is also configurable 32~39 4
40~47 5
48~55 6
56~63 7
Bearer Type
Basic DCH HSPA MBMS

Case
Priority
(0-255)
(1-15) VLANID IPDSCP VLANID IPDSCP VLANID IPDSCP
(1-4094) (0-63) (1-4094) (0-63) (1-4094) (0-63)
1 a x1 a2 x2 a3 x3
2 b y1 b2 y2 b3 y3
0
… … … … … … …
15 c z1 c2 z2 c3 z3
1 … … … … … … …
CAC & QoS - QoS requirements
 QoS requirements to normal transport recommend by ZTE:
Interface Packet Delay Packet Delay Jitter Packet Loss Rate

(one-way)
IP Iub/Iur <20 ms <7 ms <0.05 %
IP IuCS <10 ms <6 ms <0.05 %
IP IuPS <10 ms <6 ms <0.05 %

 QoS requirements to satellite transport recommend by ZTE:
Interface Packet Delay Packet Delay Packet Loss Rate

(one-way) Jitter
IP Iub/Iur <250 ms <100 ms <1 %
IP IuCS <250 ms <100 ms <1 %
IP IuPS <250 ms <100 ms <1 %

CAC & QoS - IP SLA Monitoring
 ZTE developed IP SLA monitoring feature :

 IP SLA monitoring functionality:

SLA monitoring

IP SLA based CAC Core Network

Network availability monitoring

Troubleshooting of network operation
 IP SLA monitoring methods: Node B RNC

Continuous UDP echo (more precise)

Continuous ICMP echo (compatible with any IP node)
RNC
 IP SLA monitoring results:
UDP echo

Round-trip delay ICMP echo

Delay jitter

Packet loss rate

Trigger alarm when a performance threshold is violated

Adjust CAC

CAC & QoS - Path & Path Group Concept
Path group
 Transport pool (path) defined by:
 a set of ATM VC PVC
path PVC
 one IMA group PVC
VP
PVC
 one ML-PPP group path PVC
PVC
 one destination IP with related NE
PVC
(relative with VLAN) path PVC VP
PVC
 Transport pool group (path group)
defined by: path
FE
 a set of paths GE
path
 Transport pool’s resource defined by:
Path
 uplink bandwidth group
 downlink bandwidth

CAC & QoS – Dynamic Adjustment of Pool
 Pool capacity can be adjusted automatically when:

 Physical link broken (e.g. partial E1 link broken in IMA)
 IP SLA monitoring, a threshold is reached (e.g. delay, delay
jitter, packet loss, etc.)
Reduced
Dynamic
PS RAB PS RAB
adjustment
PS RAB PS RAB
Pool capacity
CS RAB Pool capacity CS RAB
CS RAB CS RAB

CAC & QoS - CAC Rule
Traffic Bandwidth Reserved Interface Fixed/
Adjustable
Calculated bandwidth according to number
Common channel Iub Fixed
of PCH and FACH
Signaling Radio
6.4kbps/23kbps + Transport layer overhead Iub/Iur Fixed
Bearer
Adjustable
[Maximum Bit Rate] of RAB + Transport layer
Conversational Iub/Iur/IuCS (Activity
overhead
factor )
[Guaranteed Bit Rate] of RAB + Transport
Streaming Iub/Iur Fixed
layer overhead
Interactive Pseudo-GBR (configured) + Transport layer
Iub/Iur Adjustable
Background overhead
 Overbooking achieved by configuring pseudo-GBR which is less than

MBR of RAB
 Different Iub/Iur can be mapped to different CAC strategy
CAC & QoS – Congestion Avoidance illustration
C: 64kbps B: ~384kbps
Iu
Buffer User Plane scheduling
Congestion indication
RNC
Buffer Transport pool (path/path group)
Buffer
Buffer based shaping
Queue
Path
Iub
C: 64kbps B: ~384kbps
UE

CSL Network Introduction
HLR 1+1
Mutual
HLR1 HLR2
MSC MSC MSC MSC
Server1 Server2 Server3 Server4 GGSN1 GGSN2 GGSN3 GGSN4
VAS MSC Pool GGSN Pool
Core IP
Other
network SGSN Pool
MGW1 MGW2 MGW3 MGW4 SGSN1 SGSN2 SGSN3 SGSN4
Core IP
10 x iBSC 6 x RNC
RAN IP
>2100 sites
2&3G 2&3G 2&3G 2&3G

BTS BTS BTS BTS

CSL IP Network Topology
Switching Center #1 Switching Center #2
Leased dark fibre
1xHLR 2xMSCS 2xMGW 2xSGSN 2xGGSN 1xHLR 2xMSCS 2xMGW 2xSGSN 2xGGSN
6xiBSC 3xRNC 4xiBSC 3xRNC
Leased Ethernet
2&3G 2&3G
BTS BTS

Contents

QoS Monitoring and Guarantee
 Detect faults ASAP to guarantee the network quality

QoS Monitoring Solution
 Active Monitoring: Test Robot to implement the test procedure, result

report, and analysis automatically
 Test Computer + UE distributed, performance and post-processing
centralized. The Test computer to handle the data and submit.
 UE RF units distributed, UE Baseband units centralized. Test data
collected and post-processing centralized: Agilent Active Monitoring
System
 Passive Monitoring: O&M statistics and 3rd Protocol analyzer
 Performance Statistics deployed in NodeB, RNC, MSC, SGSN, GGSN,
HLR
 Protocol Analyzer deployed in Interfaces of Uu, Iub, Iur, Iu, such as
Ethereal, Tektronix, Nethawk, Agilent Passive Monitoring System,
CNT, ...

QoS Monitoring Deployment
Agilent Passive
Monitoring
Statistics
Statistics
Protocol
Analysis
Test Robot & Agilent Active

Monitoring System
Statistics Statistics
Statistics
Statistics Statistics
Statistics Protocol
Analysis
Ethereal
Ethereal

Test Robot
 Test robots implement the defined test procedures and report to

the server.
 Post-processing and report in the server

KPI
AMR12.2K
PPP Establiment duration
R6 Download Speed

Agilent Active Monitoring System
Deploy test probes and link the RF part to SIM Multiplexer by IP LAN,
can implement flexible test procedures and centralized processing.

Collection, Analysis, and Report

Agilent Passive Monitoring System
Deployed Interfaces
Link Type Participating Network Nodes
DNS GGSN <-> DNS Server
MAP MSC Server <-> HLR, MSC Server <-> MSC Server
Gb BSC <-> SGSN
Gi GGSN <-> Internet
Gn SGSN <-> GGSN
Gr SGSN <-> HLR
ISUP MSC Server <-> MSC Server
IuCS RNC <-> MSC Server
IuPS RNC <-> SGSN

Collection, Analysis, and Report

WO - NAST3018 - E01 - 1 UMTS QoS Management 50P

Uploaded by

Copyright:

Available Formats

You might also like

WO - NAST3018 - E01 - 1 UMTS QoS Management 50P

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WO - NAST3018 - E01 - 1 UMTS QoS Management 50P

Uploaded by

Copyright:

Available Formats

UMTS QoS Management

 UMTS QoS Architecture

 Flat tariffs boosts the mobile broadband services by

Requirements of developing Multi-Service, enhancing ARPU and

efficient way for optimizing the resources of network for operator, it

provide more value-added service for operator, it make possible of

© ZTE Corporation. All rights reserved

Coverage Accessability Retainability Service Integrity Mobility Delay/Latency

© ZTE Corporation. All rights reserved

UMTS Bearer Service

RNC SGSN GGSN PCRF

Backbone Bearer Service Backbone Bearer Service

Radio Bearer Service IU/S1 Bearer Service External Bearer Service

© ZTE Corporation. All rights reserved

services and meet

© ZTE Corporation. All rights reserved

RNC maps RAB QoS to RB QoS

BTS manager Iub CAC Iu-CS CAC

 UE maps the service application attribute to the UMTS bearer attribute

© ZTE Corporation. All rights reserved

 UMTS QoS Architecture

© ZTE Corporation. All rights reserved

Data Rate CCP/LCP

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

The admit threshold is between

The admit threshold is lowest for

Operator can determine the degree of difficulty to be admitted for users/services

© ZTE Corporation. All rights reserved

When resource is congestion,

When resource is congestion,

© ZTE Corporation. All rights reserved

Siler user will be selected to

Gold user will be selected to

Silver user will attain the

UE with low priortiy(eg. The scheduling Bronze user will attain

Scheduling Priority Indicator （ SPI ） is considered in HSDPA/HSUPA packet

 There are multi-users and multi-traffic in

© ZTE Corporation. All rights reserved

 In order to reflect QoS differentiation among the CS services

Emergency High priority Medium Lower

© ZTE Corporation. All rights reserved

B-Gold 1 Backgrou - 2 BG - N Y Y High priority of

B-Silver 2 Backgrou - 7 BG - N Y Y Medium priority of

B-Bronze 3 Backgrou - 11 BG - N Y Y Low priority of

I-Gold 1 Interactiv 1 2 I 1 N Y Y High priority of

I-Silver 2 Interactiv 2 7 I 2 N Y Y Medium priority of

I-Bronze 3 Interactiv 3 11 I 14 N Y Y Low priority of

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 UMTS QoS Architecture

CBR rt-VBR UBR+ nrt-VBR UBR

© ZTE Corporation. All rights reserved

User Basic priority Bearer Type

 The mapping from IPDSCP to COS is also configurable 32~39 4