1.LTE QoS From E2E Solution Perspective

35pt

: R153 G0 B0

:

FrutigerNext LT Medium

: Arial

32pt : R153 G0 B0

黑体

22pt) :18pt

黑色

:

FrutigerNext LT Regular

: Arial

20pt):18pt

黑色细黑体

HUAWEI TECHNOLOGIES CO., LTD.

1

LTE QoS from E2E solution pespective

Derek CuiVF LTE MIC(UK)

HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 2

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


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

• MBB QoS implementation target

› 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

• LTE QoS implementation principle

› Share the MBB QoS implementation target

› Keep LTE QoS compatible with other MBB technologies


General MBB network model (HSPA combined with LTE)

and QoS enabling principle

•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)

IP Backhaul

Multi-mode

UE

1

2

3

LTE eRAN

IP Backbone transmission

UMTS PS core

EPCLTE eRAN

UMTS RANUMTS RAN

LTE eRAN


Outline







General LTE-EPC network architecture

S1-MME

S1-U

S11

E-UTRAN

MME

S-GW

S5

HSS/HLR

PDN-GW

SGi

Gx

LTE handset

PCRF

Rx

Internet / intranet /

Operators in-house & 3rd

Party AS

AF

S6a


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


Basic concept: LTE-EPC QoS parameters- QCI

QCIResource

TypePriority

Packet Delay

Budget (UE / P-GW)

Packet Error

Loss RateExample of Services

1

GBR

2 100ms 10-2 Conversational Voice

2 4 150ms 10-3 Conversational Video (live streaming)

3 3 50ms 10-3 Real Time Gaming

4 5 300ms 10-6 Non-conversational Video (buffered streaming)

5

Non-GBR

1 100ms 10-6 IMS Signalling

6 6 300ms 10-6

Video (Buffered Streaming);

TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing,

progressive video, etc.)

7 100ms 10-3

Voice,

Video (Live Streaming),

Interactive Gaming

7

8

300ms 10-6

Video (Buffered Streaming);

TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing,

progressive video, etc.)

9 Best effort8

9


Basic concept: EPS bearer

Radio S5/S8S 1 SGi

P -GWS - GW PeerEntity

UE eNB

EPS Bearer

Radio Bearer S1 Bearer

End-to-end service

External Bearer

InternetE-UTRAN EPC

S5/S8 Bearer

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

EPS dedicated bearer: Bearer with specific characteristic that is setup when needed (Application triggered)

Can be GBR or non-GBR


Basic concept: Service data flow

SDF 1

SDF 2

SDF 3

PCC Rule 1

TFT Packet Filter 1

TFT Packet Filter 2

TFT Packet Filter 3

TFT Packet Filter 4

TFT Packet Filter 5

TFT Packet Filter 6

PCC Rule 2

PCC Rule 3

Bearer Level QoS

Bearer

Authorized QoS 1

Authorized QoS 2

Authorized QoS 3

SDF: Service data flow TFT: Traffic flow template


Basic concept: PCC architecture

Gy

Gx

Offline Charging System

PCEF

Gx x

BBERF

(OFCS)P-GW

Offline Charging System (OFCS)

Subscription Profile

Repository

(SPR)

Sp Policy and Charging

Rules Function

(PCRF)

Rx

AF

Online C harging System (OCS)

Service Data Flow Based

Credit Control

CAMELSCP

Gz


The initial QoS parameters set at HSS

Page 12

IMSI 1

APN(Default)

APN1

APNn

APN QoS Template

QoSTPL1: QCI, ARP, APN-

AMBR


AMBR


AMBR

QoSTPLn: QCI, ARP, APN-

AMBR

UE-AMBR

UE-AMBR

UE-AMBR

IMSI 2

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


Default bearer establishment during UE attach with

QoS transferred

Page 13

S1-MME

S1-U

S11

E-UTRAN

MME

S-GW

S5

HSS/HLR

PDN-GWSGi

Gx

PCRF

Rx

AF

S6a

UE attach initiationTo get subscribed QoS profile

Send back the subscribed QoS profile

QoS decided by PCRFand back to PGW

UE attach complete

Session create with QoS decision request)

Session create response with QoS

parametersQoS parameters signaled to eNB

QoS parameters

mapped to radio and

signaled to UE

•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.


Network-initiated dedicated bearer establishment with

QoS transferred

Page 14

S1-MME

S1-U

S11

E-UTRAN

MME

S-GW

S5

HSS/HLR

PDN-GWSGi

Gx

PCRF

Rx

AF

S6a

Service level signaling over default bearer

QoS requestQCI, 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 responseCreate bearer response

IP CAN session

modification

response

Request response


Network-initiated bearer establishment from PCC

perspective

P-GW (incl. PCEF)

(Home or Visited**) Policy Server

(PCRF)

SPR (Subscribers Profile Repository)

“if-then” policy rules

e.g. LDAP database Application Server

(e.g. video streaming,

IMS P-CSCF, etc.)

One EPS bearer

(same QCI)

QoS/Charging/Appli/User

profile provisioning

• 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)

Application

IP bearer service

eUTRAN bearer service

UE

Appli. Client/Service Request

Application session setup

Session info, User info (IP@, port), Appl.

info (appl. type, IP@, port, BW), etc. Rx

Gx

(e.g. LDAP) Sp

S-GW (incl. BBERF***)

• 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)

Gxc*

Service Data Flow

• IP flows filtering, traffic

shaping based on PCRF info

• Resources usage reporting

to PCRF

QoS rules but no

charging rules!

HISILICON SEMICONDUCTORHUAWEI TECHNOLOGIES CO., LTD. Page 16 Page 16

QoS parameters maintained along LTE-EPC network

elements

HSS

QCI ARP GBR MBR APN-AMBR UE-AMBR

P-GW

eNodeB

UE

√ √ √ √

√ √ √ √ √

√ √ √ √ √

√ √√ √


Summary for LTE QoS implementation

• LTE-EPC has specialized QoS parameters

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

• Bearer is the basic unit applying LTE-EPC parameters

› 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

• 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


Outline







Use case scenario assumption

eRAN LTE

RAN 3G/HSPAEPC

UGW

USN

Rx

eNB

MME

SGW

NodeB

SGSN

HSS

PGW

SGi

PCRF

RNC

User category Bandwidth

Priority at high

load

Premium•10 Mb/s in EPS

•5 Mb/s in HSPA High

Normal•5 Mb/s in EPS

•2 Mb/s in HSPA Low

•Cell-cite and backhaul sharing for RAN

and eRAN


User differentiation planning with extended-QCI

Type Bearer typeQCI valueService exampleNone-

differentiated

traffic

GBR 1 Conversational Voice

2 Conversational Video

3 Real Time Gaming

4 Streaming (non-conv. video)

IMS signaling None-GBR 5 IMS & voice-related signalling (Premium & Normal)

Normal user’s

data traffic

6 Gaming, other low delay (normal)

7 Interactive, e.g. WWW (normal)

8 Bulk data, e.g. ftp (normal)

9 Background, e.g. exceeded vol. limit (normal)

Premium user’s

data traffic

131 Gaming, other low delay (premium)

132 Interactive, e.g. WWW (premium)

133 Bulk data, e.g. ftp (premium)

134 Background, e.g. exceeded vol. limit (premium)

•Extended-QCI range: 128~254

•In this case, the roaming user from other operator will be set to normal user by default.


UGW

USN

1. The UE attach to the network and MME retrieves static QoS parameters from HLR and sends to PGW

2. PGW request Authorization and Control from PCRF for the specific user

3. 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

4. PCEF responds with the actual authorized default bearer QoS parameters that will be effectuated on the user plane

E-UTRAN

UE

PGW (PCEF)Default Bearer establishment

Default bearer establishment completed

SGW

MME

1

2

4

PCRF

HSSSPR

Policy controller

User are categorized in

subscriber groups

(e.g., Premium and normal) • PCRF perform rule action and

sets bearer QoS (QCI, ARP, APN-

AMBR..) depending on user

category (Premium and normal)

• PCRF can also set Service

enforcement and charging rules

dependent on user category

• PCRF receives usage reporting

and sets user Fair Usage quota

thresholds

3•Admission and scheduling is

performed using QCI, ARP

•Bandwidth is enforced by UE-AMBR

HSS sets default QoS

(QCI, ARP, AMBR)

User differentiation achieved during LTE UE attach


Keep user differentiation consistent during UL handover

Map LTE QoS parameters to UMTS QoS parameters


UMTS-LTE QoS mapping executed at MME or SGSN

Page 23

Type LTE QoS parameters UMTS QoS parametersQCI Bit rate UMTS Traffic Class Bit rate

None-

differentiated

traffic

1 GBR, MBR Conversational GBR, MBR

2 Conversational

3 Conversational

4 Streaming

IMS signaling 5 APN-AMBR=128kbps Interactive MBR=128kbps

Normal user’s

data traffic

6 APN-AMBR=10Mbps Interactive MBR=5Mbps

7 Interactive

8 Interactive

9 Background

Premium user’s

data traffic

131 APN-AMBR=5Mbps Interactive MBR=2Mbps

132 Interactive

133 Interactive

134 Background

•Parameters mapping between LTE-EPS and UMTS QoS is defined in 3GPP TS23.401


eRAN LTE

RAN 3G/HSPA

UGW

Rx

eNB

MME

SGW

NodeB

SGSN HSS

PGW

SGi

PCRF

RNC

EPCUSN

UGW

User differentiation enforcement with UL interworking

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

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

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

GGSN


Outline







UMTS/LTE transmission mapping with user differentiation

Type QCI valueUMTS Traffic Class DSCP mapping recommendation3GPP-defined GBR

QCIs

1 Conversational EF(101110)

2 Conversational AF31(011010)


4 Streaming AF31(011010)

3GPP-defined non-GBR

QCIs for IMS signaling

5 Interactive EF(101110)


QCIs for normal user’s

data traffic

6 Interactive AF22(010100)



9 Background BE(000000)

Operator-defined QCIs

for premium user’s data

traffic




134 Background AF13(001110)

SCTP (Signaling) n/a n/a EF(101110)

OM (MML) n/a n/a EF(101110)

OM(FTP) n/a n/a AF13(001110)

PTP(IP Clock) n/a n/a EF(101110)


DSCP Mapped to transmission queues for LTE backhaul

Type QCI DSCP mapping 3GPP-defined GBR QCIs 1 EF(101110)

2 AF31(011010)3 AF41(100010)4 AF31(011010)


QCI for IMS signaling

5 EF(101110)


QCIs for normal user

6 AF22(010100) 7 AF22(010100)

8 AF12(001110)9 BE(000000)

Operator-defined QCIs

for premium user

131 AF21(010010)132 AF21(010010)133 AF11(001010)134 AF13(001110)

SCTP (Signaling) n/a EF(101110)

OM (MML) n/a EF(101110)

OM(FTP) n/a AF13(001110)

PTP(IP Clock) n/a EF(101110)

Queue 1

Queue 3

Queue 8

Queue 2

EF(101110)

AF41(100010)

AF31(011010)

Queue 4

Queue 5

Queue 6

Queue 7

AF21(010010)

AF22(010100)

AF11(001010)

AF12(001100)

AF13(001110) +

BE(000000)

eNodeB/SGWPQ+WRR

Logical port


DSCP Mapped to transmission queues for UMTS backhaul

Type Pre-R8 Class DSCP mappingNone-

differentiate

d traffic

Conversational EF(101110)

Conversational AF31(011010)

Conversational AF41(100010)

Streaming AF31(011010)

IMS signaling Interactive EF(101110)

Normal

user’s data

traffic

Interactive AF22(010110)



Background BE(000000)

Premium

user’s data

traffic




Background AF13(001110)

OM (MML) n/a EF(101110)

OM(FTP) n/a AF13(001110)

PTP(IP Clock) n/a EF(101110)

Queue 1

Queue 3

Logical port

Queue 2

EF(101110)

AF41(100010)

AF31(011010)

Queue 4

Queue 5

Queue 6

AF21(010010)+

AF22(010110)

AF11(001010)+AF12(001110)+AF13(001110)

BE(000000)

NodeB/RNC PQ+WRR


UL co-site transmission(up link sceanrio1)

NodeB

eNodeB

Cell site Transport

Cell site

Backhaul

RNC

SGW

TransportNE

•Up link LP bandwidth:

25/50Mbps(Min/Max)

•VLAN ID:40

•IP PM enabled

•Up link LP bandwidth: 10/20Mbps(Min/Max)

•VLAN ID:20

•IP PM /FP PM enabled

•VLAN ID: 40

•VLAN bundled with tunnel

•Bandwidth of tunnel: 25/50Mbps(CIR/PIR)

•VLAN ID: 20

•VLAN bundled with tunnel

•Bandwidth of tunnel: 10/20Mbps(CIR/PIR)

IP PM/FP PM

IP PM

•WFQ scheduling with weight

ratio: 10:25 Central office


UL co-site transmission(up link sceanrio2)

No

de

B

Cell site Transport

Cell site

Backhaul

RNC

SGW

TransportNE

IP PM/FP PM

IP PM

Central office

LP1

LP2

•WRR scheduling

eN

ode

B

•Up link LP1 bandwidth:

10/20Mbps(Min/Max)


•Up link LP2 bandwidth:

25/50Mbps(Min/Max)

•IP PM enabled

IP PM/FP PM

IP PM/FP PM


UL co-site transmission(down link)

NodeB

eNodeB

Cell site Transport

Cell site

Backhaul

RNC

SGW

TransportNE

•Down link bandwidth:

50/100Mbps(Min/Max)

•Down link traffic identified by eNodeB

address (Destination address)

•IP PM enabled

•Down link bandwidth:

20/40Mbps(Min/Max)

•Downlink traffic identified by NodeB IP

address (Destination address)


•Destination IP address bundled with a path

•Bandwidth of path: 50/100Mbps(CIR/PIR)

•Destination IP address bundled with a path

•Bandwidth of path: 20/40Mbps(CIR/PIR)

IP PM/FP PM

IP PM

•WFQ scheduling with

weight ratio: 20:50

Central office


Do you want every 3GPP differentiation information be

mapped to IP layer?

For discussion only

•With enough identifiers reflected at

transmission, fairness and

differentiation at transmission will be

totally handled by HQoS -capable

transmission network instead of 3GPP

nodes.

Type QCI value

Pre-R8 Class DSCP mapping

None-

differentiat

ed traffic

1 Conversational EF(101110)



4 Streaming AF31(011010)

IMS

signaling

5 Interactive EF(101110)

Normal

user’s data

traffic




9 Background BE(000000)

Premium

user’s data

traffic




134 Background AF13(001110)

Outer VLAN20 Outer

VLAN40

Inner VLAN100

Inner VLAN200

RAT differentiation

User differentiation


Outline







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 Huawei’s 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.


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, APN-

AMBR, 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.

• Do we need transport have a per-user-based QoS assurance capability?

› It means a 3GPP user-identifier will have a counterpart tag at transmission.

• How can we evaluate transport capacity expansion requirement based on network

performance monitoring at RAN/eRAN side (in pure IP environment)?

Page 35



Service request procedure

MME Serving GW PDN GW

2. NAS: Service Request

1. NAS: Service Request

7. S1-AP: Initial Context Setup Complete

3. Authentication/Security

HSS

4. S1-AP: Initial Context Setup Request

5. Radio Bearer Establishment

6. Uplink Data

8. Modify Bearer Request

12. Modify Bearer Response

UE eNodeB

11. Modify Bearer Response

PCRF

(A)

10. PCEF Initiated IP-CAN Session Modification

9. Modify Bearer Request

To synchronize the accepted EPS

bearers between UE and network

•eNodeB and UE decide which EPS bearers should be accepted

•Both UE initiated and network initiated service request are available.


Standardized Mapping between EPS and pre Rel-8 QoS

parameters

Pre Rel-8 parameter Rel-8 parameter Mapping Rule

PDP/Bearer PDP Context（NSAPI） EPS Bearer（Bearer ID） 1:1

QoS parameters GBR（Conversational/Streaming） GBR (GBR Bearer) 1:1

MBR（Conversational/Streaming） MBR (GBR Bearer) 1:1

MBR（Interactive/Background） APN-AMBR 1:1

N/A UE-AMBR N/A

TC, THP, Signalling Indication, Source Statistics

Descriptor

QCI See next page

Transfer Delay PDB 1) R8Pre-R8: Transfer Delay=PDB

and SDU Error Ratio=PELR

2) Pre-R8R8:Ignore Transfer Delay

and SUD Error Ratio

SDU Error Ratio PELR

ARP-Priority (1~3) ARP- Priority (1~15) R8(1~15) Pre-R8( 1~3)

N/A ARP- Pre-emption

capability/vulnerability

N/A

Source: 3GPP TS23.401


QCI Traffic Class Traffic Handling Priority Signalling

Indication

Source Statistics

Descriptor

Transfer

Delay

1 Conversational N/A N/A Speech 100 ms

2 Conversational N/A N/A Unknown 150 ms

3 Conversational N/A N/A Unknown 80 ms

4 Streaming N/A N/A Unknown 300 ms

5 Interactive 1 Yes N/A 100 ms

6 Interactive 1 No N/A 300 ms



9 Background N/A N/A N/A 300 ms

Standardized Mapping between EPS and pre Rel-8 QoS

parameters (Cont.)


Use case 2: User starts Internet VOIP serviceDPI/SPI detected services, Control

Page 40

UGW

PGW (PCEF)SGW

1

PCRF

SPR

Policy controller

2

Charging node

3

4

User performs attach

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

2

3

4


Third party application

Use case 2: User starts Internet VOIP serviceDetected services, enforcement

Page 41

Media servers (User plane)

EPS

Backbone

network

Service flows

…

Control

Ingress

Egress

Service detection

(SPI or DPI)

HTTP

Streaming WAP

StreamingStreaming

WAP

…

HTTP

Charging

GatingPolicy match

Remark Policing/

shaping

Bearer control

Web Proxy

Redirect

Captive Portal

…

HTTP:URL

Streaming

WAP

•Service gating

•BW limit

UGW

PCRF


Use case 3: Promoted VoD service Service detection using interface to Policy Controller

Page 42

VOD service

VoD

Application server

(e.g., http based)

Media servers (User plane)

EPS

Backbone

network

Gx

Session requirements

• Media server IP adresses

• Bandwidth requirements

• Charging indicator

Policy rules

• IP Filters

• QoS parameters (QCI, Bandwidth)

• Charging info

GBR bearer (Streaming)

• Scheduling priority

• GBR bandwidth

UGW

PCRF


VoD

service

UGW

Page 43

Use case 3: Promoted VoD service Service detection using interface to Policy Controller

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 characteristic 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

E-UTRAN

UE

PGW (PCEF)

Default Bearer

SGW

MME

3

PCRF

SPR

Policy controller

• 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

Internet

Dedicated bearer

establishment

4

5

•PCRF activates rule in PGW at e.g., default

bearer establishment or due to other event

2

1


Use case 4: Congestion in Radio link

E-UTRAN

UE

PGWSGW

MME

Bearers

Internet 190.32.11.80:80

VoD 190.32.11.80:9201

Voice 190.32.11.80:25/101

MP3 downloading 192.135.10.5:8080

GBR

Non-GBR

0

20

40

60

80

100

120

1 3 5 7 9 11 13 15 17 19 21

Reso

urce

Blo

ck u

sage

TimeGBR admission level

• New GBR request will be rejected

or accepted depending on ARP

GBR

Non-GBR

Congestion

• eNB will not be able to schedule all

traffic

QCI =4,

ARP =10

GBR= 2Mb/s

QCI =2,

ARP =10

GBR=100 Kb/s

QCI =9

(non-GBR)

(ARP=10)

UE-AMBR= 2 Mb/s

Scheduling

order


IP PM Monitoring Solution for Backhaul Congestion

Status


PCRF

Policy updateTraffic usage info report

Tariff Plan：Normal userQuota size ：5GbPolicy rule:

•80% warning notification •90% Throttle access speed •Exhausted：Set max speed

(AMBR) to 384 Kb/s

Notification

SMSC Your traffic quota is ***. The data speed will be reduced to X b/s when quota is depleted

Fair usage policy implementation for user differentiation

PGW

UE A

UE B


User category differentiation enforcement and charging

Page 47

Service

Flows

BillingPCRF

RG = 004; Rate = 0.20$/K bytes


RG = 003; Rate = 0.50 $/K bytes


Internet 190.32.11.80:80

Mobile TV 190.32.11.80:9201

E-mail 190.32.11.80:25/101

MP3 downloading 192.135.10.5:8080

Service ID = 104; RG = 004




Documents

1.LTE QoS From E2E Solution Perspective