End-to-End QoS Architecture

E-UTRAN EPC Internet

UE eNB S-GW P-GW Peer

Entity

End-to-end Service

EPS Bearer External Bearer

E-RAB S5/S8 Bearer

Radio Bearer S1 Bearer

Radio QoSRadio
Control S1 QoSS1
Control S5 QoS
S5/S8Control SGiGi
QoS Control
 Rate control  QCI based packet  QCI based packet  DSCP marking(UL)
(GBR/MBR/AMBR) classification classification
 PDB and priority based  QCI/DSCP/COS  QCI/DSCP/COS
scheduling mapping & marking mapping & marking
 PELR based  Backhaul BW mgmt.  DL Gating(PGW)
Retransmission  UL Traffic shaping  DL APN-AMBR(PGW)
Standard & Operator Specific QCI
Samsung eNB supports the standardized QoS class identifiers(QCIs) and operator-
defined QoS classes
Resource
QCI Priority PDB PELR Example Services
Type

1 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video (Live Streaming)

3 GBR 3 50 ms 10-3 Real Time Gaming

4 5 300 ms 10-6 Non-Conversational Video (Buffered Streaming)

5 1 100 ms 10-6 IMS Signalling

Video (Buffered Streaming), TCP-based (e.g., www, e-

6 6 300 ms 10-6
mail, chat, ftp, p2p file sharing, progressive video, etc.)
Non-GBR
7 7 100 ms 10-3 Voice, Video (Live Streaming), Interactive Gaming

8 8 Video (Buffered Streaming), TCP-based (e.g., www, e-

300 ms 10-6
9 9 mail, chat, ftp, p2p file sharing, progressive video, etc.)

128 ~254 … … … Operator-defined specific classes (TS24.301)

QCI: QoS Class Identifier PDB: Packet Delay Budget b/w UE and PGW Ref: 3GPP TS 23.203
PELR: Packet Error Loss Rate GBR: Guaranteed Bit Rate
Operator Specific QCI
Samsung eNB supports max. 127 operator-specific QCIs in
addition to 9 standardized QCIs.
Operator can define QoS characteristics of the extended QCIs
• Resource Type : GBR or Non-GBR
• Priority : 1 – 16
• PDB : 0(50ms) -9(500ms)
Radio scheduler considers those parameters when it allocates
radio resources.
 QoS Parameters and Bearers
PDN Connection 1 (IP-CAN Session 1)

UE Resource Type QoS Parameters QoS Parameters of SDF

Dedicated Bearer GBR MBR

for connect with PDN 1 GBR QCI ARP (UL/DL) (UL/DL) MBR (UL/DL) GBR (UL/DL) SDF 5

Dedicated Bearer MBR (UL/DL) SDF 4

UE IP 1 for connect with PDN 1 Non-GBR QCI ARP PDN 1
APN-AMBR MBR (UL/DL) SDF 3
Default Bearer (UL/DL) MBR (UL/DL) SDF 2
for connect with PDN 1 Non-GBR QCI ARP
MBR (UL/DL) SDF 1
UE-AMBR
(UL/DL)
Default Bearer
for connect with PDN 2 Non-GBR QCI ARP MBR (UL/DL) SDF 1
APN-AMBR
Dedicated Bearer (UL/DL) MBR (UL/DL) SDF 2
UE IP 2 for connect with PDN 2 Non-GBR QCI ARP PDN 2
MBR (UL/DL) SDF 3
Dedicated Bearer GBR MBR MBR (UL/DL) GBR (UL/DL) SDF 4
for connect with PDN 2 GBR QCI ARP (UL/DL) (UL/DL) MBR (UL/DL) GBR (UL/DL) SDF 5

PDN Connection 2 (IP-CAN Session 2)

Samsung LTE QoS Features
• For GBR services, the radio scheduler of eNB considers
the bit rate requirements and QoS characteristics (resource
QoS Aware Scheduling type, priority, PDB, PLER) of bearers for resource
allocation.

• The CAC algorithm admits new GBR bearers only when

QoS Based CAC the required level of bit rate and QoS can be satisfied.

• Samsung eNB can predict the network congestion by

monitoring the amount of buffered data. When the
Congestion Prevention congestion is expected, the congestion prevention
algorithm is enabled to avoid it.
• UL traffic shaping

• Samsung eNB supports DSCP and COS marking and ECN

Backhaul QoS field in order to help intermediate nodes in the backhaul
network fulfill QoS requirements of operator.
• Traffic Segregation and bandwidth control based on traffic
type or QCI

User Differentiated QoS • Samsung eNB provides subscriber differentiation in terms

of throughput for non-GBR bearers. Subscribers are
classified into Gold/Silver/Bronze groups and they can
achieve differentiated throughput in proportion to the weight
factor that operator pre-dfined.
QoS Aware Scheduling Rules

1) Resource Allocation for

Resource Allocation QCI#5 Bearer (IMS signaling)
For QCI#5 Bearers  Strict prioritization based on
Priority standardized QCI priority
based
Scheduling
2) Resource Allocation for
Resource Allocation
GBR Bearers
For GBR Bearers  Strict prioritization based on
standardized QCI priority
 QCI #1 ~ #4

Weight 3) Resource Allocation for

Resource Allocation
based
For Non-GBR Bearers
Non-GBR Bearers
Scheduling
 Proportional resource allocation
based on weight configured by
operator
QoS Based CAC (1/2)
Capacity based CAC for GBR and Non-GBR Bearer Requests
QoS based CAC for GBR Bearer Requests

RRC connection E-RAB

establishment establishment

MaxUeENB
Capacity based CAC MaxRbCELL
MaxUeCELL

PRB usage of the cell,

Backhaul bandwidth resource,
Requested bearer Info. (GBR,
QoS based CAC
priority)

Accept or Deny Preemption if denied Preemption

 QoS Based CAC (2/2)
• Scheduler measures radio resource utilization and reports it to the Call admission
control entity

• QoS CAC Policy 1: The CAC admits a new GBR Bearer, if the new service can
achieve the guaranteed bit rate requirement based on the radio resource
utilization of other GBR services and the backhaul resource utilization.
Introducing a new GBR bearer must not degrade the QoS level of existing GBR
bearer services.

• QoS CAC Policy 2: Non-GBR bearers are always allowed as long as the total
number of bearers per UE and per Cell does not exceed the maximum limit
respectively.

• In order to sustain a certain level of QoS for Non-GBR services, operator can limit
the maximum number of users allowed per cell, can let CAC automatically reject
new calls when congestion occurs.
Traffic Congestion Control
Load Balancing
Load balancing between LTE carriers or between cells

Offload to other RAT

Offload to 3G or WiFi network

UL Traffic Shaping
Backhaul bandwidth configured not to exceed bottleneck bandwidth in
the backhaul network between eNB and EPC

UL Congestion Prevention
Uplink flow control between eNB and UE
Traffic Shaping and Congestion Prevention
UL Backhaul Congestion Prevention
Operator can limit the backhaul bandwidth in order to avoid congest
ion in a bottleneck link in the backhaul network.
eNB constrains uplink transmission rate not to exceed the pre-
configured backhaul bandwidth usage.

Rate Control
UL Buffer Traffic
Scheduler Monitor Shaping

Q1
Q2
Q3
UE Q4
RLC Packet
PDCP Classification Q5
UE
Q6
N/W
Q7 Scheduler

eNB Q8
 ECN Field Copy

Server

Inner IP Payload
ECN field copy (ECN = ‘01’/’10’)

SAE-GW
Outer IP Inner IP
UDP GTP Payload
(ECN = ‘01’/’10’) (ECN = ‘01’/’10’)

SW/RT

Outer IP Inner IP
UDP GTP Payload
(ECN = ’11’) (ECN = ‘01’/’10’)

eNB
Inner IP
ECN field copy (ECN = ’11’)
Payload

UE
Congestion information
delivered to application server
Call Congestion Control
Maximum # of UE Capacity limitation
Operator can configure the maximum number of UEs that eNB or a cell
can accommodate in order to guarantee a certain level of user
experience such as throughput or response time.

Dynamic Access Barring

When CPU is overloaded, eNB dynamically change the ac-barring
parameters so that call attempts of some Ues can be delayed

Cell Barring
UEs are not allowed to access the cell. The cell can be used only for
limited purpose, e.g. testing.
eNB Overload Control: Dynamic Access Barring
Automatic adjustment of access barring control
parameters to resolve overload situation of eNB
processor
In normal state eNB monitors the eNB Processor (CPU)
load status of CPU processor Load Monitoring
(main B’d) periodically.

When overloaded situation, eNB CPU Overload

State Changed? No
performs eNB Overload Control
function, i.e. automatic
Yes
configuration for access barring
control parameters per overload Adjustment of
level (Minor/Major/Critical). AC-Barring Information
eNB Overload Control: Dynamic Access Barring
Configuration of access barring control parameters per overload level of eNB CPU
processor
When the main board's CPU processor is overloaded, cell barring function is automatically activated and new
incoming calls are limited by the CAC algorithm.(SIB Type2)

eNB Overloaded
Generated Random Number
> Ac-BarringFactor

Delayed Access
Generated Random Number
< Ac-BarringFactor

Access barring control parameters Overload level of eNB CPU processor

(SIB type2) Critical Major Minor Normal
ac-BarringForEmergency Barred Not barred Not barred Not barred
ac-BarringFactor 0% allowed 90% allowed 95% allowed -
ac-BarringForMO-Signalling
ac-BarringTime 128s 32s 16s -
ac-BarringFactor 0% allowed 70% allowed 80% allowed -
ac-BarringForMO-Data
ac-BarringTime 128s 32s 16s -
QCI Design Proposal (1/3)
Resource QoS Weight for
QCI Priority Example Service Subscribers
Type Characteristics Resource Alloc.

1 GBR 2 100ms, 10-2 N/A Conversational voice All users

2 GBR 4 150ms, 10-3 N/A Conversational video All users

3 GBR 3 50ms, 10-3 N/A Real time gaming All users

4 GBR 5 300ms, 10-6 N/A Non-conversational viedo All users

5 Non-GBR 1 100ms, 10-6 N/A IMS signaling All users

6 6 3 Gold

128 Non-GBR 10 300ms, 10-6 2 Video (Buffered streaming) Silver

129 11 1 Bronze(default)

7 7 5 Gold
Voice,
130 Non-GBR 12 100ms, 10-3 4 Video(Live streaming) Silver
Interactive gaming
131 13 3 Bronze(default)

8 8 3 Gold

132 Non-GBR 14 300ms, 10-6 2 Reserved Silver

133 15 1 Bronze(default)

9 9 3 Gold
TCP-based(www, email,
134 Non-GBR 16 300ms, 10-6 2 Silver
chat, ftp, p2p)
135 17 1 Bronze(default)
QCI Design Proposal (2/3)
No user differentiation for QCI#5 (IMS Signaling)
 QCI#5 is dedicated to IMS signaling messages. The amount of the
messages is supposed to be quite small.
 Reducing call setup time for every users.
Bit rate differentiation for Non-GBR bearers
 Introduction of “weight factor”, configurable by operator
 Non-GBR bearers can be differentiated in terms of the amount of resource
allocation, which is a new feature that is not defined in the standard

User differentiation within one standard QCI

 An operator-defined QCI can share QoS characteristics(resource type,
PDB, PLER) with a standardized QCI except priority.
 Total 15 differentiated Non-GBR QCIs supported, including standardized
Non-GBR QCIs(#6~#9)
 A UE shall be either Gold or Silver or Bronze user. A UE is not allowed to
open both Gold bearer and Silver bearer.
QCI Design Proposal (3/3)
Use of “Weight” factor
 If the operator does not want this feature, the weight factor should be all
set to “1”
 The weight factor always applied to NGBR bearers, but it takes effect only
in case of resource limitation. When there are enough resources, each
bearers would be able to transmit all of its own data.

Service differentiation with different QCI

 Standard feature
 A dedicated bearer with specific QCI can be established for a service
offered by an identified server or a service that PGW can identity its IP
flow.
EPS QoS Parameter Decision(1/3)
Default EPS Bearer Setup (Non-GBR)

HSS PCRF

③ Subs. EPS QoS I ⑥ Authorized EPS

② Request for ⑤ Request for QoS Info.
nfo.
Subscriber. Info. QoS Param. • QCI, ARP
• QCI, ARP
• QCI, ARP • APN-AMBR
• UE-AMBR
• APN-AMBR • Src & Dst IP
• APN-AMBR

UE eNB MME S-GW P-GW

① PDN Connectivity Req. ④ Create Session Req.

(APN, No QoS Paramete (QCI, ARP, APN-AMBR)
r)
⑦ Create Session Res.
(QCI, ARP, APN-AMBR)

UE-AMBR 계산

⑧ Initial Ctx Setup Req.

(QCI, ARP, UE-AMBR)

⑧ Activate Default EPS Bearer Ctx Req.

(QCI, APN-AMBR)
EPS QoS Parameter Decision(2/3)
Dedicated EPS Bearer Setup Initiated by UE
PCRF

④ Authorized EPS
③ Request for QoS Info.
QoS Param. • QCI, ARP
• QCI • GBR/MBR
• GBR/MBR • Src & Dst IP

UE eNB MME S-GW P-GW

① Bearer Resource Allocation Req. ② Bearer Resource Command

(QCI,GBR/MBR, LBI ) (QCI, GBR/MBR, LBI )

⑤ Create Bearer Req.

(QCI, GBR/MBR, ARP, LBI)

⑥ E-RAB Setup Req.

(QCI, ARP, UE-AMBR)

⑦ Activate Dedicated EPS Bearer Ctx. Req.

(QCI, GBR/MBR, APN-AMBR)

⑧ Activate Dedicated EPS Bearer Ctx. Accept.

LBI:Linked Bearer ID
ARP: Allocation & Retention Priority
Ref: 3GPP 24.301
EPS QoS Parameter Decision(3/3)
Dedicated EPS Bearer Setup Initiated by PCRF ② IP Filter & BW Info.
Rx
PCRF P-CSCF

③ EPS QoS Info.

• QCI, ARP
• GBR/MBR
• Src & Dst IP

UE eNB MME S-GW P-GW

① INVITE message [???] Interne

t
④ Create Bearer Req.
(QCI, GBR/MBR, ARP, LBI)

⑤ E-RAB Setup Req.

(QCI, ARP, UE-AMBR)

⑥ Activate Dedicated EPS Bearer Ctx. Req.

(QCI, APN-AMBR)

LBI:Linked Bearer ID
ARP: Allocation & Retention Priority
CSCF: Call Session Control Function
QCI to DSCP Mapping Rule (Example)

QCI DSCP Value Traffic Type Remarks

S1/X2 signaling ( including SCTP heart-beat), GTP echo, GTP error

- 24 (CS3) Signaling
indication
- 24 (CS3) Management SNMP messages (Alarm, Status, Command Request/Response)
- 26 (AF31) OAM Traffic FTP, Logs (CSL, Trace), ICMP (between LSM and eNBs)
- 48 (CS6) Network control IP control (DHCP), NTP (LSM and eNBs)
1 46 (EF) QCI-1 User Data Conversational Voice (RTP) (CDMA Voice)
2 34 (AF41) QCI-2 User Data Conversational Video (Live Streaming)
3 36(AF42) QCI-3 User Data Real Time Gaming

4 38(AF43) QCI-4 User Data Non-Conversational Video (Buffered Streaming)

5 24(CS3) QCI-5 User Data IMS Signalling

Video (Buffered Streaming)

6 16(CS2) QCI-6 User Data
TCP-based (e.g., www, e-mail, chat, ftp, p2p)

Voice, Interactive Gaming

7 18(AF21) QCI-7 User Data Video (Live Streaming)

Video (Buffered Streaming)

8 20(AF22) QCI-8 User Data
TCP-based (e.g., www, e-mail, chat, ftp, p2p)

Video (Buffered Streaming)

9 22(AF23) QCI-9 User Data
TCP-based (e.g., www, e-mail, chat, ftp, p2p)

0 (CS0) Remaining Traffic Best Effort