MobileComm Professionals, Inc.

Your Partner for Wireless Engineering Solutions

Data Session Setup
 3

Agenda

Initial Attach

Default EPS Bearer Setup

S1 Release

QoS Management
 4

Initial Attach Procedures

SPR
HSS

UE ID Acquisition

Authentication

NAS Security Setup

Location Update

EPS Session Establishment

 5

IMSI Acquisition

RRC Connection Request

RRC Connection Setup

RRC Connection

RRC Connected RRC Connected

Attach Request
RRC Connection Setup Complete
Initial UE Message

S1 Signaling Connection

ECM Connection

ECM-Connected ECM-Connected

EMM-Connected EMM-Connected

MME Acquire IMSI

 6

Authentication

Procedure for Authentication

 7

NAS Security Setup

Procedure for NAS Security Setup

 8

Location Update

Procedure for Location Update

 9

EPS Session Establishment

SPR
HSS

Assign EPS Bearer ID

P-GW selection by HSS or MME Create Session Request

Create Session Request

Create S5 Receive S5
TEID(DL) TEID(DL)
UE IP Address Allocation

Indication of IP-CAN Session establishment (CCR)

Profile Request
Profile Response
Policy Decision

Ack of IP-CAN Session establishment (CCA)

Create Session Response

Receive S5 Create S5
TEID(DL) TEID(UL)
SS P-GW TEID will be used for Create Session Response
TAU in case of S-GW relocation

MME Shall Set the UE AMBR to the sum of APN-AMBR of all

Create S1 TEID(UL)
active APNs upto the value of the Subscribed UE AMBR
 EPS Session Establishment
10

SPR
HSS

MME Generates Various Parameters

Attach Accept

Initial Context Setup Request

Receive S1 TEID(UL)
eNB generates AS Keys
Security Mode Command

UE generates AS Keys

Security Mode Command

Ciphering and Integrity Setup Complete for

RRC Message and Bearer
RRC Connection Reconfiguration

Receive DRB ID Create DRB ID

Initial Context Setup response

Attach Complete
Modify Bearer Request

Modify Bearer Response

 11

SAE Bearer QoS Awareness

One of the major requirements for EUTRAN and EPC to fulfill is that every SAE bearer must be QoS aware.
All data transmitted within a SAE bearer will get the same QoS handling (scheduling, prioritization, discarding probability,
etc.).
Different applications (for example take a packet video streaming service and a ftp download) have different QoS setting and
cannot share the same SAE bearer.
Other applications with similar traffic characteristics will be able to be placed inside the same SAE bearer provided that the
bandwidth of the bearer is scaled accordingly .
Due to this fact, the standard will allow a UE to have several SAE bearers, each one with a different QoS setting.
 12

Bearer
There are two types of Bearer, i.e. Dedicated bearer and Default bearer.

There is at-least one default bearer established when UE is attached to LTE network while dedicated bearer is
always established when there is need to provide QoS to specific service (like VoIP, video etc).
 13

SAE Bearer Usage Example

PDN
Gateway

IMAP server
(IP:A, UDP Port:a)

E-MAIL Default EPS Bearer (N-GBR)

SIP UA

SIP server
VoIP (IP:B, UDP Port:b)
Codec

PDN

UL Packet Filter: DL Packet Filter:

(UL TFT) (DL TFT)
IP Dest Add.=C IP Source Add.=C
Dedicated EPS Bearer (GBR)
UDP Dest. Port =c UDP Source Port =c
Protocol = UDP/RTP Protocol = UDP/RTP VoIP User Agent
(IP:C, UDP Port:c)
 SAE Bearer Usage Example 14

PDN
Gateway

IMAP server
(IP:A, UDP Port:a)

E-MAIL Default EPS Bearer (N-GBR)

SIP UA

SIP server
VoIP (IP:B, UDP Port:b)
Codec

PDN

UL Packet Filter: DL Packet Filter:

(UL TFT) (DL TFT)
IP Dest Add.=C IP Source Add.=C
Dedicated EPS Bearer (GBR)
UDP Dest. Port =c UDP Source Port =c
Protocol = UDP/RTP Protocol = UDP/RTP VoIP User Agent
(IP:C, UDP Port:c)
EPS Bearer Service & NAS Signalling Connection
15

MME S/P-GW

UE

EPS Bearer Service (S1-UP)

Data Radio
Bearer

Traffic
Radio Channel Transport Bearer (GTP)
Link
RRC Signalling
Channel S1 Signalling Bearer

Signalling Radio
Bearer
NAS Signalling Connection
 16

EPS Bearer Service

Peer
Entity
UE eNB

End to End

EPS Bearer External Bearer

E - RAB S5/S8 Bearer

Radio Bearer S1 Bearer

Radio S1 S5/S8 Gi
 17

Default Bearer

UE Packet eNB
Filter

IP1
Data Radio
S1 Bearer S5/S8 Bearer
Bearer

Packet
Filter

Bearer 1 Default
 Default Bearers
18

The initial Default EPS Bearer is created as part of the LTE Attach procedure.

UE is allocated an IP address.

QoS is based on the QCI and associated parameters.

Additional Default EPS Bearers may be created when simultaneous access to

services available via multiple Access Point Names (APN) is needed.

Trigger of an additional Default EPS Bearer is initiated by UE.

Default EPS Bearers are always non-GBR.

 Dedicated Bearer
19

UE eNB Packet
Packet Filter Bearer1
Filter Default

IP1 Data Radio Bearer S1 Bearer S5/S8 Bearer

Data Radio Bearer S1 Bearer S5/S8 Bearer

Bearer2
Dedicated
 Dedicated Bearer
20

Dedicated EPS Bearers (non-GBR or GBR) are created for QoS differentiation
purposes.

The IP address allocated for the default bearer is used for the dedicated
EPS bearers within the same PDN connection.
Utilization of default or dedicated EPS bearers is based on a TFT.
Dedicated EPS Bearers are created by network.
 21

E-UTRAN Initial Attach

UE eNB MME SGW PGW HSS

1. Random Access
procedure

RRCConnectionSetupCompl
2 ete
(EMM:Attach Request, ESM:PDN Connectivity Request)

IntialUEMessage
3
(EMM:Attach Request, ESM:PDN Connectivity Request)

4 ME Identity check procedure ME identity check procedure EIR

Authentication / Security Authentication / Security

5 Location updating

6 CreateSessionRequest
7.Session
creation
CreateSessionRensponse
8
 22

E-UTRAN Initial Attach

UE eNB MME SGW PGW HSS

InitialContextSetupRequ
9 est
(EMM:Attach Accept, ESM:Activate Default EPS Bearer Context Request )
RRCConnectionReconfiguration
10
(EMM:Attach Accept, ESM:Activate Default EPS Bearer Context Request )
RRCConnectionReconfigurationCompl
11 ete
InitialContextSetupResponse
12
ULInformationTransfer
13
(EMM:Attach Complete, ESM:Activate Default EPS Bearer Context Complete)
UplinkNASTransport
14
(EMM:Attach Complete, ESM:Activate Default EPS Bearer Context Complete)
First Uplink Data
15 ModifyBearerRequest
16 Modify Bearer Response

First Downlink
Data

Signalling For Attach and Default Bearer Establishment Procedure

 Dedicated Bearer Activation (1/2)
23

MME PCRF

PCC
Create Dedicated Bearer Decision
Create Dedicated Bearer Request (QoS Policy)
Request
(PDN GW IP/TEID2, QoS param. )
RRC_Idle+ ECM_Idle (SGW-S1 IP/TEID2, QoS param.)

Paging Paging

(S-TMSI) (S-TMSI, TA/TA-list, )

Service Request

(GUTI/S-TMSI, TAI.service type = paging response) Network Triggered

Initial Context Setup Req. Service Request
RB Establishment Req. (SGW-S1 IP/TEID1, EPS Bearer ID,QoS) Procedure

RB Establishment Rsp. Initial Context Setup Rsp.

(eNB-S1 IP/TEID1, Update Bearer Request Note: procedure

EPS Bearer ID, ..)
(eNB-S1 IP/TEID1) initiated by the Network
Update Bearer Response

RRC_Connected + ECM_Connected
Reference to specs.: TS 23.401 section 5.4.1
 Dedicated Bearer Activation (2/2)
24

Session Mgmt. Response

(NAS message, EPS Bearer ID)

Create Dedicated Bearer

Response

(eNB IP/TEID2, EPS Bearer

ID, QoS, ) Create Dedicated Bearer
Response

(SGW-S5 IP/TEID2, EPS

Bearer ID, QoS, ) PCC
Provision
Note: procedure Ack
initiated by the Network

Reference to specs.: TS 23.401 section 5.4.1

 GUTI (Globally Unique Temporary UE Identity)
25

GUTI

GUMMEI M-TMSI

MMC MNC MMEI

MMEGI MMEC

The GUTI has two main components:

GUMMEI: uniquely identifies the MME which allocated the GUTI

M-TMSI: uniquely identifies the UE within the MME that allocated the GUTI
 EPS Mobility Management States
26

The EMM states describe the Mobility Management States from the NAS Procedures

Attach

EMM EMM
De-Registered Registered

Detach
 EPS Connection Management State
27

For a UE in ECM-CONNECTED state, a signaling connection exists between the UE and the
MME

UE E-UTRAN MME

RRC Connection
establishment RRC
RRC Idle
RRC Connection release Connected

S1 Connection establishment
ECM
ECM Idle
Connected
S1 Connection release
 EMM & ECM Transitions
28

Power On

Release due to
Registration (Attach) Inactivity
Allocate C-RNTI, S_TMSI Release RRC connection
Allocate IP addresses Release C-RNTI
Authentication Configure DRX for paging
Establish security context

EMM_Deregistered EMM_Registered EMM_Registered

ECM_Connected ECM_Idle

Deregistration (Detach) New Traffic

Change PLMN
Establish RRC Connection
Release C-RNTI, S-TMSI Allocate C-RNTI
Release IP addresses

Timeout of Periodic TA
Update

Release S-TMSI
Release IP addresses
 EMM and ECM States Summary
29

EMM_De-Registered
Network Context: no context exists
Allocated IDs: IMSI
UE Position: unknown to network
UE Radio Activity: none

EMM_Registered , ECM_Connected
Network Context: all info for ongoing transmission / reception
Allocated IDs: IMSI, S-TMSI per TAI C-RNTI
UE Position: known on cell level
Mobility: NW controlled handover
UE Radio Activity: DL w/o DRX UL w/o DTX

EMM_Registered, ECM_Idle
Network Context: security keys enable fast transition to ECM_CONNECTED
Allocated IDs: IMSI, S-TMSI per TAI
UE Position: known on TA level (TA list)
Mobility: cell reselection
UE Radio Activity: DL DRX for paging no UL
 30

S1 Release Procedure
This procedure is used to release the logical S1-AP signalling connection (over S1-MME) and all S1 bearers (in S1-U)
for a UE.
The procedure will move the UE from ECM-CONNECTED to ECM-IDLE in both the UE and MME, and all UE related
context information is deleted in the eNB.
The initiation of S1 Release procedure is either:
eNB-initiated with cause e.g. O&M Intervention, Unspecified Failure, User Inactivity, Repeated RRC signalling
Integrity Check Failure, Release due to UE generated signalling connection release, etc.
MME-initiated with cause e.g. authentication failure, detach, etc.
 31

S1 Release Signalling

UE eNB MME SGW PGW HSS

ECM_CONNECTED ECM_CONNECTED

UEContextReleaseRequest Only in eNB initiated S1 Release

1
2 ReleaseAccessBearerRequest

3 ReleaseAccessBearerResponse

UEContext
4 ReleaseCommand
RRCConnectionRelease
5
UEContext ReleaseComplete
6
ECM_IDLE ECM_IDLE
 SAE Bearer QoS Awareness
32

All data transmitted within a SAE bearer will get the same QoS handling (scheduling,
prioritization, discarding probability, etc.).
Different applications (for example packet video streaming service and FTP download)
have different QoS setting and cannot share the same SAE bearer
Other applications with similar traffic characteristics will be able to be placed inside the
same SAE bearer provided that the bandwidth of the bearer is scaled accordingly .
Due to this fact, the standard will allow a UE to have several SAE bearers, each one with a
different QoS setting.

HTTP
Radio QoS Bearers Mobility Tunnels

Streaming

UE eNB
VoIP, PTT
Mapping of mobility Packet Filtering and
tunnels to radio bearers classification
 SAE Bearer QoS Attributes
33

QoS parameters:
Guaranteed Bit Rate (GBR)
Non-Guaranteed Bit Rate (N-GBR)
Maximum Bit Rate (MBR)
Allocation/Retention Priority (ARP)
For all bearers together for one terminal, following QoS parameter is available:
Aggregate Maximum Bit Rate (AMBR)
eNB
UE

S1-U S5 Sgi
cell PDN

End-to-End Service

External Bearer
SAE Bearer Service (EPS Bearer) Service
 E2E QoS Architecture
34

Dynamic PCC rule:

GBR,QCI,ARP ,UL
and PCC filters
Sp
SPR
E-UTRAN EPC
Gx INTERNET
UE eNodeB S-GW P-GW Peer entity
Default bearer(Non GBR) QCI=5
IMS signaling
Dedicated bearer(GBR) QCI 1
Voice Media

Dedicated bearer (GBR) QCI 2

Video Media
EPS bearer
Packet Packet
filters(uplink) E-RAB S5/S8 Bearer filters(Downlink)

Radio bearer S1 Bearer

Radio S1 S5/S8 Gi
 35

3GPP definition for QoS

LTE Network QoS is implemented between UE and PDN Gateway and is applied to a set of bearers. 'Bearer' is basically
a virtual concept and is a set of network configuration to provide special treatment to set of traffic e.g. VoIP packets
are prioritized by network compared to web browser traffic.
In LTE, QoS is applied on Radio bearer, S1 bearer and S5/S8 bearer, collectively called as EPS bearer as shown in figure
below
 36

QoS Class Identifier (QCI)

 37

Policy Control and Charging (PCC)

Policy Management

Operator control over network usage

Control the level of service provided and charge accordingly

Superior performance for the customers that pay for it

Enforce limits or restrictions based on customer subscription

Dynamic service level adjustment enhances QoE

Offer attractive options to gain market share

Restrict content based on subscription or local laws

 38

Policy and Charging Control (PCC) Architecture

Subscription AF
profile
Repository(SPR) Online
Sp charging
Rx
system (OCS)

Policy and Charging Rules

Function (PCRF)

Gxx Gx

PCEF Gy
BBERF
Offline charging
Gz system (OFCS)
Gateway
 39

PCC Network Elements

PCRF (Policy & Charging Rules Function)
PCRF is the central node in the policy and charging control architecture; it keeps a DB of PCC rules in SPR and
supports flow-based charging and policy (QoS)

Interworks with other network elements via the Diameter protocol

SPR (Subscription Profiles Repository)
DB of PCC rules; can be co-located with HSS or PCRF
A PCC rule consists of traffic filters to map Service Data Flows (SDF) to EPS Bearers,
QoS and charging related parameters

PCEF (Policy & Charging Enforcement Function)

The enforcement part of the policy architecture
Main functions include DPI, traffic shaping, etc.
Typically co-located with a PDN-GW

BBERF (Bearer Binding and Event Reporting Function)

Bearer Binding and Event Reporting Function
Use PCC rules to map SDFs to EPS bearers; logical function of PDN-GW
 40

HAPPY LEARNING

MobileComm Professionals, Inc.

www.mcpsinc.com