1.LTE QoS From E2E Solution Perspective

LTE QoS from E2E solution pespective
Derek Cui VF LTE MIC(UK)
HUAWEI TECHNOLOGIES CO., LTD.
Outline
Business driver and overview for LTE QoS General LTE-EPC QoS solution
User differentiation with UMTS/LTE interworking

Solution for mobile network implementation Solution for backhaul implementation
Summary and discussion
HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR
Page
Mobile broadband demands QoS implementation

MBB QoS implementation driver
Revenue originated from Internet traffic is limited in terms of per-bit-revenue Network capacity can never catch up with increase of IP traffic Valuable subscribers can not get additional network quality Internet service provider consuming huge network resource but pay little to operators Build up the basis for market segmentation Keep user experience generally good enough with always limited network resources Pave the way for innovative business model in future Share the MBB QoS implementation target Keep LTE QoS compatible with other MBB technologies
MBB QoS implementation target

LTE QoS implementation principle

Page
General MBB network model (HSPA combined with LTE) and QoS enabling principle
1
UMTS RAN UMTS RAN Multi-mode UE

2
UMTS PS core EPC IP Backbone transmission
LTE eRAN LTE eRAN LTE eRAN

3
IP Backhaul
1:How does the QoS be guaranteed from UE to core network at 3GPP network layer 1.1: How does the QoS parameters be decided 1.2: How does the QoS parameters be transferred between core, ran and UE 1.3: How does the QoS parameters be used at radio interface handling (to be covered in another presentation) 1.4. How does the QoS parameters be used at core network (out of the scope of this workshop) 2: How does the QoS be guaranteed during UMTS/LTE interworking 2.1: How does LTE QoS parameters be mapped to UMTS parameters 2.2. How does the QoS parameters be transferred during handover 3: How does the QoS be guaranteed during traffic conversion between 3GPPnetwork and transmission network 3.1: How does the 3GPP QoS parameters be mapped to IP transmission QoS parameters 3.2: How to mitigate the negative effect of transmission congestion during traffic conversion 3.3: How to manage transmission resource competition between UMTS and LTE 3.4: How does the transmission QoS parameters be used at transmission (out of the scope of this wokshop)
HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR Page 4
Outline

Page
General LTE-EPC network architecture
S6a HSS/HLR PCRF
MME AF S1-MME LTE handset S5 E-UTRAN S1-U S-GW PDN-GW SGi Internet / intranet / Operators in-house & 3rd Party AS S11
Gx
Rx
Page
Basic concept: QoS parameters- priority & bitrate

Characterstics and Priority
QCI, QoS Class Identifer Reference to a specific packet forwarding behaviour.
ARP, Allocation and Retention Priority The priority of a bearer used in contention situations e.g. at bearer establishments or for packet drop policy. Includes pre-emption capabillity and pre-emption vulnerability booleans
Bitrate enforcement
GBR, Guaranteed BitRate GBR bearer guaranteed bitrate
MBR, Maximum Bitrate Per bearer Maximum bitrate. Used in conjuction with GBR bearer. MBR set equal to GBR in 3GPP release 8 and 9. MBR can be set > GBR in R10.
UE-AMBR, UE Aggregated Maximum Bitrate The maximum total bitrate a UE can use (e.g., over multiple APNs) APN-AMBR, APN Aggregated Maximum Bitrate The maximum total bitrate a UE can use against an APN
HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR Page
Basic concept: LTE-EPC QoS parameters- QCI

QCI 1 2 3 4 5 6 GBR Resource Type Priority 2 4 3 5 1 6 Packet Delay Budget (UE / P-GW) 100ms 150ms 50ms 300ms 100ms 300ms Packet Error Loss Rate 10-2 10-3 10-3 10-6 10-6 10-6 Example of Services Conversational Voice Conversational Video (live streaming) Real Time Gaming Non-conversational Video (buffered streaming) IMS Signalling Video (Buffered Streaming); TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) Voice, Video (Live Streaming), Interactive Gaming Video (Buffered Streaming); TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) Best effort
100ms
10-3
Non-GBR
7 8 300ms 8 9
10-6
Page
Basic concept: EPS bearer

E-UTRAN UE eNB
S - GW
EPC
P -GW
Internet Entity
Peer
End-to-end service EPS Bearer

Radio Bearer Radio EPS default bearer:
The EPS default bearer (with a HSS pre-defined QoS) is setup at attach APN is selected and UE IP address is allocated (IP connectivity) Default bearer is non-GBR
External Bearer
S5/S8 Bearer S5/S8 SGi
S1
Bearer
S1
EPS dedicated bearer:

Bearer with specific characteristic that is setup when needed (Application triggered) Can be GBR or non-GBR
Page
Basic concept: Service data flow

Bearer TFT Packet Filter 1 TFT Packet Filter 2 TFT Packet Filter 3 PCC Rule 1 Authorized QoS 1
SDF 1
TFT Packet Filter 4 SDF 2 TFT Packet Filter 5 PCC Rule 2 Authorized QoS 2 Bearer Level QoS
TFT Packet Filter 6 SDF 3
PCC Rule 3
Authorized QoS 3
SDF: Service data flow

TFT: Traffic flow template

Page 10
Basic concept: PCC architecture

Subscription Profile Repository
AF
(SPR) Rx Online C Sp
Policy and Charging Rules Function
harging System (OCS) Service Data Flow Based Credit Control
CAMEL SCP
(PCRF)
Gx x
Gx
Gy PCEF Offline Offline Charging Charging System System (OFCS) (OFCS)
BBERF
P-GW
Gz
Page 11
The initial QoS parameters set at HSS

APN(Default) APN QoS Template
UE-AMBR
QoSTPL1: QCI, ARP, APNAMBR
QoSTPL2: QCI, ARP, APNAMBR IMSI 1 APN1 QoSTPL3: QCI, ARP, APNAMBR
UE-AMBR
IMSI 2
QoSTPLn: QCI, ARP, APNAMBR
APNn
UE-AMBR
QoS parameters set at HSS: QCI, ARP, APN-AMBR and UE-AMBR

Page 12
Page 12
Default bearer establishment during UE attach with QoS transferred

S6a HSS/HLR MME AF S11 S1-U S-GW To get subscribed QoS profile Send back the subscribed QoS profile Session create with QoS decision request) Session create response with QoS parameters QoS decided by PCRFand back to PGW S5 PDN-GW PCRF
S1-MME
E-UTRAN UE attach initiation
Gx
SGi
Rx
QoS parameters mapped to radio and signaled to UE
QoS parameters signaled to eNB
UE attach complete
Subscribed QoS profile is got from HSS MME can be regarded as the QoS parameters distribution center PCRF is the QoS decision-making point The EPS bearer entry point for service flow is also arranged in this process.
Page 13
Network-initiated dedicated bearer establishment with QoS transferred

S6a HSS/HLR MME PCRF
AF
S11 S5 S-GW PDN-GW Gx SGi Rx
S1-MME
E-UTRAN S1-U
Service level signaling over default bearer QoS request QCI, ARP, GBR, MBR and TFT
Create beaer request with QoS par.

QoS parameters signaled to eNB
QoS mapped to radio bearer and signaled to UE
Bearer setup response

Create bearer response
IP CAN session modification response Request response
Page 14
Page 14
Network-initiated bearer establishment from PCC perspective

QoS/Charging/Appli/User profile provisioning Application (e.g. LDAP) Sp
SPR (Subscribers Profile Repository) if-then policy rules e.g. LDAP database
IP bearer service
eUTRAN bearer service UE Appli. Client/Service Request
Application Server (e.g. video streaming, IMS P-CSCF, etc.)
Application session setup Session info, User info (IP@, port), Appl. info (appl. type, IP@, port, BW), etc.
(Home or Visited**) Policy Server (PCRF)
Rx
IP flows filtering, traffic shaping based on PCRF info Resources usage reporting to PCRF
QoS rules but no charging rules!
Gxc* Gx
To check Appl/Users profile and session info To get inputs from PCEF and BBERF (option) To select/apply pre-defined PCC rules (QoS & Charging) by session/user/application profile Bearer resources decision (QCI, MBR, AMBR, etc.) for UE/session (flow Id IP@ source/destination, etc. ) and charging rate to apply (one PCC rule per SDF) Service Data Flow Bearer binding**** IP filtering/ SDF detection for traffic shaping, gating based on PCRF info Resources usage reporting to PCRF On-line charging with OCS for pre-paid and credit management (Gy itf)
Page 15
One EPS bearer (same QCI)

S-GW (incl. BBERF***) P-GW (incl. PCEF)
QoS parameters maintained along LTE-EPC network elements

QCI HSS P-GW eNodeB UE ARP GBR MBR APN-AMBR UE-AMBR
Page 16
Page 16
Summary for LTE QoS implementation

LTE-EPC has specialized QoS parameters
QCI, ARP, GBR, MBR, UE-AMBR and APN-AMBR

Bearer can be classified into GBR bearer (applying QCI, ARP,GBR and MBR) and none-GBR-bearer (applying QCI, ARP,UE-AMBR and APN-AMBR) Default bearer is established during UE attach procedure, playing as none-GBR bearer; dedicated bearer is usually established from network side, playing as GBR or none-GBR bearer
Bearer is the basic unit applying LTE-EPC parameters
Service traffic, as client of bearer, use traffic flow template (e.g source/destination IP address, protocol number, port number) as entry point for bearer PCRF is the decision maker for QoS parameters, and MME plays like a coordinator during QoS parameters transferring
Page 17
Page 17
Outline

Page 18
Use case scenario assumption

Cell-cite and backhaul sharing for RAN and eRAN
User category
Premium Normal
Bandwidth
10 Mb/s in EPS 5 Mb/s in HSPA 5 Mb/s in EPS 2 Mb/s in HSPA
Priority at high load

High Low
RAN 3G/HSPA
RNC
EPC
USN
SGSN HSS Rx PCRF
NodeB
eRAN LTE
MME
UGW
SGW PGW
SGi
eNB
Page 19
User differentiation planning with extended-QCI

Type
Nonedifferentiated traffic
Bearer type QCI value Service example

GBR 1 2 3 4 5 6 7 8 9 131 132 133 134 Conversational Voice Conversational Video Real Time Gaming Streaming (non-conv. video) IMS & voice-related signalling (Premium & Normal) Gaming, other low delay (normal) Interactive, e.g. WWW (normal) Bulk data, e.g. ftp (normal) Background, e.g. exceeded vol. limit (normal)
Gaming, other low delay (premium) Interactive, e.g. WWW (premium) Bulk data, e.g. ftp (premium) Background, e.g. exceeded vol. limit (premium)
IMS signaling Normal users data traffic
None-GBR
Premium users data traffic
Extended-QCI range: 128~254 In this case, the roaming user from other operator will be set to normal user by default.
Page 20
User differentiation achieved during LTE UE attach

User are categorized in subscriber groups (e.g., Premium and normal) HSS sets default QoS (QCI, ARP, AMBR) Admission and scheduling is performed using QCI, ARP Bandwidth is enforced by UE-AMBR
Policy controller
PCRF
HSS USN
SPR
PCRF perform rule action and sets bearer QoS (QCI, ARP, APNAMBR..) depending on user category (Premium and normal)
2
UGW
E-UTRAN
PCRF can also set Service enforcement and charging rules dependent on user category PCRF receives usage reporting and sets user Fair Usage quota thresholds
MME
Default Bearer establishment

UE
1
SGW PGW (PCEF)
4
Default bearer establishment completed The UE attach to the network and MME retrieves static QoS parameters from HLR and sends to PGW PGW request Authorization and Control from PCRF for the specific user PCRF coordinates and authorizes the QoS requirement against subscription. The PCRF apply the user category by perform QoS action setting QCI, ARP and UE AMBR (UL/DL) and send it to PCEF PCEF responds with the actual authorized default bearer QoS parameters that will be effectuated on the user plane
1. 2. 3. 4.
Page 21
Keep user differentiation consistent during UL handover

Map LTE QoS parameters to UMTS QoS parameters
Page 22
UMTS-LTE QoS mapping executed at MME or SGSN

Parameters mapping between LTE-EPS and UMTS QoS is defined in 3GPP TS23.401
Type
Nonedifferentiated traffic
LTE
QoS parameters
Bit rate GBR, MBR
IMS signaling Normal users data traffic
QCI 1 2 3 4 5 6 7 8 9 131 132 133 134
UMTS QoS parameters UMTS Traffic Class

Conversational Conversational Conversational Streaming Interactive Interactive Interactive Interactive Background Interactive Interactive Interactive Background
Bit rate GBR, MBR
APN-AMBR=128kbps APN-AMBR=10Mbps
MBR=128kbps MBR=5Mbps
APN-AMBR=5Mbps
MBR=2Mbps
Page 23
Page 23
User differentiation enforcement with UL interworking

NodeB Performs airlink scheduling based on SPI Perform admission control based on ARP Premium user: MBR=5Mb/s, SPI= 9 Normal user: MBR=2Mb/s, SPI=5 MME Fetch subscriber QoS profile from HSS during attach Perform UMTS and LTE QoS parameters mapping during handover or cell re-selection Transfer QoS parameters from EPC to eRAN
RAN 3G/HSPA
RNC NodeB
SGSN
USN
HSS
EPC
PCRF Rx
GGSN MME
eRAN LTE
UGW
SGW
UGW
PGW
SGi
eNB
eNB Performs airlink scheduling based on QCI Performs Admission control at bearer establishment (ARP) Bandwidth is enforced by UE-AMBR
The eNB enforces the user category differentiation on the airlink: Premium user: APN-AMBR = 10Mb/s, QCI (Priority) = 131 Normal user: APN-AMBR = 5 Mb/s, QCI (Priority) = 6
UGW APN bandwidth shaping Detect services by DPI/Shallow packet inspection Performs usage reporting for session and per service Performs service bandwidth shaping/policing Mapping of EPS QoS (QCI) parameters to Gi transport IP layer
Page 24
Outline

Page 25
UMTS/LTE transmission mapping with user differentiation

Type
3GPP-defined GBR QCIs
QCI value UMTS Traffic Class

1 2 3 4 5 6 7 8 9 Conversational Conversational Conversational Streaming Interactive Interactive Interactive Interactive Background
DSCP mapping recommendation

EF(101110) AF31(011010) AF41(100010) AF31(011010) EF(101110) AF22(010100) AF22(010100) AF12(001100) BE(000000)
3GPP-defined non-GBR QCIs for IMS signaling 3GPP-defined non-GBR QCIs for normal users data traffic
Operator-defined QCIs for premium users data traffic

SCTP (Signaling) OM (MML) OM(FTP) PTP(IP Clock)
131 132 133 134

n/a n/a n/a n/a
Interactive Interactive Interactive Background

n/a n/a n/a n/a
AF21(010010) AF21(010010) AF11(001010) AF13(001110)

EF(101110) EF(101110) AF13(001110) EF(101110)
Page 26
DSCP Mapped to transmission queues for LTE backhaul

Type
3GPP-defined GBR QCIs
QCI
1 2 3 4
DSCP mapping
EF(101110) AF31(011010) AF41(100010) AF31(011010) EF(101110) AF22(010100) AF22(010100) AF12(001110) BE(000000) AF21(010010) AF21(010010) AF11(001010) AF13(001110) EF(101110) EF(101110) AF13(001110) EF(101110)
EF(101110) AF41(100010)
eNodeB/SGW
PQ+WRR
Logical port
Queue 1
3GPP-defined non-GBR QCI for IMS signaling 3GPP-defined non-GBR QCIs for normal user
5 6 7
Queue 2
AF31(011010)
Queue 3
AF21(010010)
Queue 4
8
9
AF22(010100)
Queue 5
Operator-defined QCIs for premium user
131 132 133 134
AF11(001010)
Queue 6
AF12(001100) AF13(001110) + BE(000000)
Queue 7
SCTP (Signaling) OM (MML) OM(FTP) PTP(IP Clock)
n/a n/a
Queue 8
n/a
n/a
Page 27
DSCP Mapped to transmission queues for UMTS backhaul

Type Pre-R8 Class DSCP mapping
EF(101110) AF31(011010) AF41(100010) AF31(011010) EF(101110) AF22(010110) AF22(010110) AF12(001110) BE(000000) AF21(010010) AF21(010010) AF11(001010) AF13(001110)
EF(101110)
NoneConversational differentiate Conversational d traffic Conversational Streaming IMS signaling Interactive Normal Interactive users data Interactive traffic Interactive Background Premium Interactive users data Interactive traffic Interactive Background
NodeB/RNC
Logical port
PQ+WRR
Queue 1
AF41(100010)
Queue 2
AF31(011010)
Queue 3
AF21(010010)+ AF22(010110) AF11(001010)+ AF12(001110)+ AF13(001110) BE(000000)
Queue 4
Queue 5
OM (MML) n/a OM(FTP) n/a PTP(IP Clock) n/a

EF(101110) AF13(001110) EF(101110)
Queue 6
Page 28
UL co-site transmission(up link sceanrio1)

Up link LP bandwidth: 10/20Mbps(Min/Max) VLAN ID:20 VLAN ID: 20 IP PM /FP PM enabled VLAN bundled with tunnel Bandwidth of tunnel: 10/20Mbps(CIR/PIR) WFQ scheduling with weight ratio: 10:25
Cell site
NodeB IP PM/FP PM
Central office RNC
eNodeB
IP PM
Cell site Transport
Backhaul
Transport NE
SGW
Up link LP bandwidth: 25/50Mbps(Min/Max) VLAN ID:40 IP PM enabled

VLAN ID: 40 VLAN bundled with tunnel Bandwidth of tunnel: 25/50Mbps(CIR/PIR)

Page 29
UL co-site transmission(up link sceanrio2)

Cell site WRR scheduling Up link LP1 bandwidth: 10/20Mbps(Min/Max) IP PM /FP PM enabled
LP1 eNodeB IP PM/FP PM Cell site Transport Node B IP PM/FP PM
Central office RNC

Backhaul
Transport NE
IP PM/FP PM
LP2
IP PM
SGW
Up link LP2 bandwidth: 25/50Mbps(Min/Max) IP PM enabled

UL co-site transmission(down link)

Destination IP address bundled with a path Bandwidth of path: 20/40Mbps(CIR/PIR) WFQ scheduling with weight ratio: 20:50 Cell site
NodeB Cell site Transport Backhaul Transport NE
Down link bandwidth: 20/40Mbps(Min/Max) Downlink traffic identified by NodeB IP address (Destination address) IP PM /FP PM enabled
Central office
IP PM/FP PM
RNC
IP PM
eNodeB
SGW
Destination IP address bundled with a path Bandwidth of path: 50/100Mbps(CIR/PIR)
Down link bandwidth: 50/100Mbps(Min/Max) Down link traffic identified by eNodeB address (Destination address) IP PM enabled
Page 31
For discussion only
Do you want every 3GPP differentiation information be mapped to IP layer?

Outer VLAN20 Outer VLAN40 RAT differentiation
Type
Nonedifferentiat ed traffic IMS signaling Normal users data traffic
QCI value
1 2 3
Pre-R8 Class
Conversational Conversational Conversational
DSCP mapping
EF(101110) AF31(011010) AF41(100010)
4 5 6 7 8 9 131 132 133 134
Streaming Interactive Interactive Interactive Interactive Background Interactive Interactive Interactive Background
AF31(011010) EF(101110) AF22(010110) AF22(010110) AF12(001110) BE(000000) AF21(010010) AF21(010010) AF11(001010) AF13(001110)
With enough identifiers reflected at transmission, fairness and differentiation at transmission will be totally handled by HQoS -capable transmission network instead of 3GPP nodes.
Inner VLAN100 User differentiation
Inner VLAN200
Page 32
Outline

Page 33
LTE-EPC QoS solution summary

1:How does the QoS be guaranteed for a single flow from UE to core network 1.1: How does the QoS parameters be decided PCRF is the QoS strategy decision maker for LTE-EPC. Pre-configured PCC rules (including QoS parameters)for specified flow is configured in it. 1.2: How does the QoS parameters be transferred between core, ran and UE MME is a key element helping QoS parameters be transferred over core, ran and UE. 2: How does the QoS be guaranteed during UMTS/LTE interworking 2.1: How does LTE QoS parameters be mapped to UMTS parameters Either MME or SGSN implements UMTS-LTE QoS parameters mapping during handover, which is a standardized mapping relation and handling procedure. 3: How does the QoS be guaranteed during traffic conversion between 3GPPnetwork and transmission network 3.1: How does the 3GPP QoS parameters be mapped to IP transmission QoS parameters IP DSCP mapping for UMS and LTE Qos parameters is implemented at each node. The mapping is configurable and the differentiation can be reflected over transmission. 3.2: How to mitigate the negative effect of transmission congestion during traffic conversion IP performance monitoring can be implemented for Huaweis solution. The traffic admitted over backhaul can be adjusted based on the backhaul congestion status detected by eRAN and core network. 3.3: How to manage transmission resource competition between UMTS and LTE The fairness algorithm implemented at base station or transmission NE can guarantee the fairness between UMTS and LTE traffic.
Page 34
Discussion: QoS topics to be explored

How can we make QoS effect visible to the customer?
Especially make premium user understand the value he/she possess is really superior over others
Do we need a tools to help operator quickly get correct QoS parameters(eg. GBR, MBR, APNAMBR, UE-AMBR, etc) and network configuration based on business, service and existed traffic model input. Can we establish a QoS monitoring system to evaluate the overall effect of differentiation
A corresponding trouble shooting system could also be needed. It means a 3GPP user-identifier will have a counterpart tag at transmission.
Do we need transport have a per-user-based QoS assurance capability?
How can we evaluate transport capacity expansion requirement based on network performance monitoring at RAN/eRAN side (in pure IP environment)?
Page 35
Page 35
Page 36
Service request procedure

UE eNodeB MME Serving GW PDN GW PCRF HSS 1. NAS: Service Request 2. NAS: Service Request 3. Authentication/Security 4. S1-AP: Initial Context Setup Request 5. Radio Bearer Establishment 6. Uplink Data 7. S1-AP: Initial Context Setup Complete 8. Modify Bearer Request 9. Modify Bearer Request (A)
10. PCEF Initiated IP-CAN Session Modification
To synchronize the accepted EPS bearers between UE and network
11. Modify Bearer Response 12. Modify Bearer Response
eNodeB and UE decide which EPS bearers should be accepted Both UE initiated and network initiated service request are available.
Page 37
Page 37
Standardized Mapping between EPS and pre Rel-8 QoS parameters

Pre Rel-8 parameter
PDP/Bearer QoS parameters PDP ContextNSAPI GBRConversational/Streaming MBRConversational/Streaming MBRInteractive/Background N/A TC, THP, Signalling Indication, Source Statistics Descriptor Transfer Delay SDU Error Ratio
Rel-8 parameter
EPS BearerBearer ID GBR (GBR Bearer) MBR (GBR Bearer) APN-AMBR UE-AMBR QCI PDB PELR 1:1 1:1 1:1 1:1 N/A
Mapping Rule
See next page 1) 2) R8Pre-R8: Transfer Delay=PDB and SDU Error Ratio=PELR Pre-R8R8:Ignore Transfer Delay and SUD Error Ratio
ARP-Priority (1~3) N/A
ARP- Priority (1~15) ARP- Pre-emption capability/vulnerability
R8(1~15) Pre-R8( 1~3) N/A
Source: 3GPP TS23.401

Page 38
Page 38
Standardized Mapping between EPS and pre Rel-8 QoS parameters (Cont.)
QCI 1 2 3 4 Traffic Class Conversational Conversational Conversational Streaming Traffic Handling Priority N/A N/A N/A N/A Signalling Indication N/A N/A N/A N/A Source Statistics Descriptor Speech Unknown Unknown Unknown Transfer Delay 100 ms 150 ms 80 ms 300 ms
5
6 7
Interactive
Interactive Interactive
1
1 2
Yes
No No
N/A
N/A N/A
100 ms
300 ms 100 ms
8
9
Interactive
Background
3
N/A
No
N/A
N/A
N/A
300 ms
300 ms
Page 39
Page 39
Use case 2: User starts Internet VOIP service

DPI/SPI detected services, Control
Policy controller
1
2
PCRF User performs attach
SPR
PCRF installs Service detection rules, charging rules and QoS rules in UGW (PGW) Service is detected by DPI engine when user starts the service. Different actions can be applied in the PGW such as BW limitation. In this use case CDRs are used for recording use of a specific service Charging data is generated performed per service (Rating Group)
1
UGW
2 4
Charging node
3
SGW PGW (PCEF)
Page 40
Page 40
Use case 2: User starts Internet VOIP service

Detected services, enforcement
Ingress
Service detection (SPI or DPI)
Service gating BW limit
Control
Policy match
HTTP:URL Streaming WAP
Service flows
Gating Policing/ shaping Charging
HTTP Streaming HTTP Streaming
Bearer control Remark

Web Proxy Redirect Captive Portal
Egress
WAP Streaming
WAP
PCRF
EPS
Third party application
Backbone network
UGW Media servers (User plane)
Page 41
Page 41
Use case 3: Promoted VoD service

Service detection using interface to Policy Controller
Session requirements Media server IP adresses Bandwidth requirements Charging indicator
EPS
Policy rules IP Filters QoS parameters (QCI, Bandwidth) Charging info
PCRF
VOD service
VoD Application server (e.g., http based)
Gx Backbone network
UGW Media servers (User plane)
GBR bearer (Streaming) Scheduling priority GBR bandwidth
Page 42
Page 42
Use case 3: Promoted VoD service

Service detection using interface to Policy Controller
Policy controller
PCRF activates rule in PGW at e.g., default bearer establishment or due to other event Admission control is performed at the bearer establishment (ARP) Streaming GBR bearers have scheduling precedence over non-GBR bearers (QCI) Bandwidth is enforced by UE-AMBR
PCRF
SPR
2 3
E-UTRAN
VoD service
MME
UGW
4
Internet
Default Bearer
1
UE
Dedicated bearer establishment
SGW
PGW (PCEF)
The UE attach to the network and the default bearer is established with default QoS 1. User selects a video from the Video library 2. The VoD service poses communication requirements to the PCRF through the Rx interface 3. PCRF checks against the subscriber policy register on what right the user have. The PCRF decide to order the requested char acteristic from the UGW (PGW, PCEF) 4. The UGW (PGW, PCEF) decides that a streaming GBR bearer is required and start the establishment of the dedicated bearer. 5. All involved user plane node performs admission control to decide if it can handle the bearer at the current load situation. The bearer is established and traffic is scheduled with high priority
Page 43
Page 43
Use case 4: Congestion in Radio link

MME
E-UTRAN
SGW
Non-GBR
PGW
UE
Congestion eNB will not be able to schedule all traffic
GBR
Resource Block usage
120 100 80 60 40 20 0
1 3 5 7 9 11 13 15 17 19 21
Bearers
Non-GBR
MP3 downloading
Internet
192.135.10.5:8080
QCI =9 (non-GBR) (ARP=10) UE-AMBR= 2 Mb/s QCI =4, ARP =10 GBR= 2Mb/s
190.32.11.80:80
GBR
VoD 190.32.11.80:9201
Voice 190.32.11.80:25/101
GBR admission level New GBR request will be rejected or accepted depending on ARP
Time
Scheduling order
QCI =2, ARP =10 GBR=100 Kb/s
Page 44
Page 44
IP PM Monitoring Solution for Backhaul Congestion Status
Page 45
Page 45
Fair usage policy implementation for user differentiation
Tariff PlanNormal user Quota size 5Gb Policy rule: 80% warning notification 90% Throttle access speed ExhaustedSet max speed (AMBR) to 384 Kb/s
SMSC
PCRF
Notificati on
Your traffic quota is ***. The data speed will be reduced to X b/s when quota is depleted
Traffic usage info report
Policy update
UE A
UE B
PGW
Page 46
User category differentiation enforcement and charging

PCRF
Service ID = 101; RG = 001 Service ID = 102; RG = 002 Service ID = 103; RG = 003 Service ID = 104; RG = 004 RG = 001; Rate = 0.51$/K bytes RG = 002; Rate = 0.10$/K bytes RG = 003; Rate = 0.50 $/K bytes RG = 004; Rate = 0.20$/K bytes
Billing
MP3 downloading Service Flows Internet
192.135.10.5:8080
190.32.11.80:80
Mobile TV 190.32.11.80:9201 E-mail 190.32.11.80:25/101
Page 47
Page 47

1.LTE QoS From E2E Solution Perspective

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1.LTE QoS From E2E Solution Perspective

Încărcat de

Drepturi de autor:

Formate disponibile

LTE QoS from E2E solution pespective

Derek Cui VF LTE MIC(UK)

HUAWEI TECHNOLOGIES CO., LTD.

User differentiation with UMTS/LTE interworking

Summary and discussion

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Mobile broadband demands QoS implementation

MBB QoS implementation target

LTE QoS implementation principle

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

UMTS RAN UMTS RAN Multi-mode UE

UMTS PS core EPC IP Backbone transmission

LTE eRAN LTE eRAN LTE eRAN

User differentiation with UMTS/LTE interworking

Summary and discussion

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

General LTE-EPC network architecture

S6a HSS/HLR PCRF

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Basic concept: QoS parameters- priority & bitrate

Basic concept: LTE-EPC QoS parameters- QCI

Basic concept: EPS bearer

End-to-end service EPS Bearer

EPS dedicated bearer:

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Basic concept: Service data flow

TFT Packet Filter 6 SDF 3

SDF: Service data flow

TFT: Traffic flow template

Basic concept: PCC architecture

harging System (OCS) Service Data Flow Based Credit Control

The initial QoS parameters set at HSS

QoSTPL1: QCI, ARP, APNAMBR

QoSTPLn: QCI, ARP, APNAMBR

QoS parameters set at HSS: QCI, ARP, APN-AMBR and UE-AMBR

Default bearer establishment during UE attach with QoS transferred

QoS parameters mapped to radio and signaled to UE

QoS parameters signaled to eNB

Network-initiated dedicated bearer establishment with QoS transferred

Create beaer request with QoS par.

QoS mapped to radio bearer and signaled to UE

Bearer setup response

IP CAN session modification response Request response

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Network-initiated bearer establishment from PCC perspective

Application Server (e.g. video streaming, IMS P-CSCF, etc.)

(Home or Visited**) Policy Server (PCRF)

QoS rules but no charging rules!

One EPS bearer (same QCI)

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

QoS parameters maintained along LTE-EPC network elements

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Summary for LTE QoS implementation

QCI, ARP, GBR, MBR, UE-AMBR and APN-AMBR

Bearer is the basic unit applying LTE-EPC parameters

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

User differentiation with UMTS/LTE interworking

Summary and discussion

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

Use case scenario assumption

Priority at high load

HUAWEI TECHNOLOGIES CO., LTD. HISILICON SEMICONDUCTOR

User differentiation planning with extended-QCI

Bearer type QCI value Service example