UE attempts to register

with network
subscriber must be
authenticated,
equipment ID may be
validated

MME entirely
responsible with
support from HSS/EIR

Default bearer activation

MME initiates, PGW
responsible

PGW may get policy and

charging rules from
PCRF, may get
subscribers available
credit from OCS

User plane is established

S1-MME Interface S13 Interface EIR Emulation
eNodeB Emulation Diameter/SCTP
Mainly relay function Validate UE identity configurable responses
between UE and MME
using S1-AP/SCTP S6a Interface HSS Emulation
stack Diameter/SCTP
UE Emulation Provide authentication vectors
NAS signaling with Provide subscriber profile
security encrypt
Learn UE location
requests, decrypt
responses
S11 Interface SGW/PGW Emulation
Inform MME of user GTP-Cv2/UDP
and equipment
identities Simulate bearer activation relay bearers
attributes to MME with Create Session
Respond to Response: PDN type, IP address(es) (V4, V6, or
authentication both), ID, QoS profile, PCO, Charging ID, APN
challenge restriction and AMBR, SGW user address, SGW
Learn/retain current control/user TEIDs, PGW address/TEID
session and bearer Retain bearer information
identifiers
Learn eNodeB TEID from Modify Bearer Request

MMEs responsibilities are access control & session management control plane only
S11 Interface MME S5 Interface PGW
Emulation Emulation
Control plane: GTP-Cv2/UDP Control plane: GTP-Cv2/UDP
Initiate default bearer User plane: GTP-U/UDP
activation with Create Simulate bearer activation
Session Request, using pre- inform SGW of bearers
provisioned identities for attributes in Create Session
subscribers and equipment Response: PDN type, IP
Learn/retain bearer address(es) (V4, V6, or both),
attributes ID, QoS profile, and PCO,
S1-U Interface eNodeB Charging ID, APN restriction
and AMBR, PGW TEID
Emulation
User plane: GTP-U/UDP Retain bearer information

Establish GTP tunnel with

SGW

SGWs primary focus is the user plane packet routing and per-user/per-flow accounting
S5 Interface SGW Gx Interface PCRF
Emulation Emulation
Provide initial policy and
Initiate default
charging rules based on APN
bearer activation and PDN type
using pre- Gy Interface OCS Emulation
provisioned Maintain credit balance per
identities for subscriber/service and provide
subscribers and balance when requested
equipment Adjust balance per quota
(including RAN requests/usage reporting from
capabilities) PGW
SGi Interface
Learn/retain bearer
Interface between core network
attributes
and public PDN (in carriers
Establish GTP-U network interface would not be
tunnel with PGW exposed to PDN)
Receive subscriber uplink
traffic, generate response
traffic, initiate downlink traffic

PGWs primary focus is the user plane bearer activation; packet routing, inspection, and
screening; policy and rate enforcement; and service-level accounting
 UE attempts to access IMS service that requires a new data flow (e.g., streaming video)
AF notifies PCRF of UE request
PCRF pushes QoS policy decision to PGW, triggering PGW to initiate dedicated bearer activation
PGW may query OCS for quota if service requires pre-paid credit
Dedicated bearer request pushed downstream to eNodeB which establishes bearer and relays
the bearer information back upstream to PGW
S1-MME Interface
eNodeB Emulation S11 Interface SGW/PGW Emulation
Establish requested
If UE is idle, trigger Service Request process
bearer using ID
assigned by MME, Generate Create Dedicated Bearer Request with
associate with identifiers, QoS, Traffic Flow Template, and
referenced default Protocol Configuration Options (if configured)
bearer On successful response, learn bearer ID
Correctly respond
with a Bearer Setup
Response, indicating
whether requested
QoS could be
honored
Relay UEs SM
Response
UE Emulation
Formulate Session
Management
Response

MME assigns EPS Bearer Identity

S11 Interface MME Emulation
Establish bearer with requested S5 Interface PGW Emulation
QoS, associate with referenced
Generate Create Bearer Request
default bearer
with identifiers and pre-
Assign EPS Bearer Identity provisioned QoS, TFT, and PCO
Correctly respond with a Create Learn EPS Bearer Identity
Bearer Response
Generate server-initiated traffic
towards UE
S1-U Interface eNodeB Respond to traffic from UE
Emulation Measure data throughput
Respond to server-initiated
traffic
Measure data throughput

SGW relays request and response, routes downlink/uplink traffic

S5 Interface SGW Gx Interface PCRF
Emulation Emulation
Establish bearer with Push QoS policy to PGW
requested QoS, associate Gy Interface OCS
with referenced default
bearer
Emulation (conditional)
If subscriber is accessing a
Assign EPS Bearer Identity chargeable service, PGW
Correctly respond with a may check for credit
Create Bearer Response availability prior to
Generate UE-initiated traffic activation
Measure data throughput SGi Interface Application
Server Emulation
Respond to traffic from UE
Measure data throughput

PGW-initiated bearer activation triggered by PCRF, routes downlink/uplink traffic

 An inter-MME mobility
process without SGW
relocation
UE initiates procedure
when it moves to a
new tracking area
MME obtains
subscribers context
from old MME, may
request authentication
MME initiates bearer
modification
MME notifies HSS of
subscribers new
location
HSS notifies old MME
that subscriber has
relocated, old MME
releases resources
S1-MME Interface S11 Interface SGW/PGW
eNodeB Emulation Emulation
Simulate UE TAU Receive Modify Bearer Request
request with new Update subscribers location
location parameters
Respond with Modify Bearer Response
Respond to
authentication
procedure if
requested by MME (if
MME determines that
credentials are
invalid)
Receive TAU Accept
S1-U Interface
eNodeB Emulation
Receive forwarded
packets from old MME

MME establishes subscriber session, obtains session information from previous MME,
initiates bearer modification
S11 Interface S5 Interface PGW
MME Emulation Emulation
(assumes both MMEs are Receive Modify Bearer
emulated) Request (sent if PGW
requested User Location
Send Modify Bearer Request
Information IE during attach)
with subscribers new location
and new MME Update subscribers location
and RAT type, which may
Handle Modify Bearer
cause a shift in QoS policy
Response
Respond with Modify Bearer
Response

SGW updates subscribers MME, may notify PGW of the subscribers new location if dynamic
PCC is configured, routes downlink traffic to new MME
 Gx Interface PCRF
Emulation
S5 Interface Provide QoS profile for
SGW Emulation subscribers new RAT
type
Notify PGW of
subscribers new PGW may not wait for
location and Radio the PCRF response
Access Type with may continue and then
Modify Bearer initiate an Update Bearer
Request Request if warranted
Handle Modify
Gy Interface OCS
Bearer Response
Emulation
(conditional)
If subscriber is
accessing a chargeable
service, PGW may check
for rate/tariff differences
for new location

PGW may react to subscribers new location by notifying PCRF and OCS; new RAN may not
support existing QoS, may result in different rate for chargeable service
 The UE, MME, and HSS can initiate the detach procedure, UE-initiated detach is shown
UE requests a detach from the MME (NAS signaling) and eNodeB relays request, adding the cell location
MME initiates Delete Session Request which is forwarded upstream, with each node deleting the
subscribers bearers (SGW also releases UE context)
PGW may initiate session termination with the PCRF and, if subscriber was accessing a chargeable
service, delivers final charging report to OCS
AF may be notified by the PCRF that subscriber session has been terminated
PGW acknowledges the SGWs request with a Delete Session Response which is forwarded back to the
MME
MME may confirm the detach with the UE and then releases the S1 connection for the subscriber,
triggering the eNodeB to release the subscribers bearers
eNodeB releases the connection with the UE
S1-MME Interface
eNodeB Emulation S11 Interface SGW/PGW
Initiate Detach Emulation
Request with UEs Receive Delete Session Request
GUTI , Switch Off Delete subscribers bearers and context,
indication, and cell halt uplink/downlink user traffic
location towards MME
Respond with Delete Session Response
Release S1-AP
connection when
requested
S1-U Interface eNodeB
Emulation
Delete subscribers
bearers

MME releases subscribers bearers, initiates Delete Session Request towards SGW
S11 Interface S5 Interface PGW
MME Emulation Emulation
Initiate Delete Session Receive Delete Session Request
Request with UEs TEID Delete subscribers bearers , halt
towards the SGW uplink/downlink user traffic
Receive Delete Session Respond with Delete Session
Response Response

SGW releases subscribers bearers and context, relays Delete Session Request towards PGW
S5 Interface Gx Interface PCRF
SGW Emulation Emulation
Initiate Delete Receive session termination
request
Session Request
with UEs TEID Delete subscribers session
towards the PGW Acknowledge session
Receive Delete termination
Session
Gy Interface OCS
Response
Emulation
Receive and acknowledge
Credit Final Report

PGW releases subscribers bearers, notifies PCRF and OCS