Evolved EPC For LTE by Cisco 1

Evolved Packet Core for LTE Networks
BRKSPG-2022
Follow us on Twitter for real time updates of the event:

@ciscoliveeurope, #CLEUR
Housekeeping
 We value your feedback- don't forget to complete your online session

evaluations after each session & the Overall Conference Evaluation
which will be available online from Thursday
 Visit the World of Solutions and Meet the Engineer
 Visit the Cisco Store to purchase your recommended readings
 Please switch off your mobile phones
 After the event don’t forget to visit Cisco Live Virtual:
www.ciscolivevirtual.com
 Follow us on Twitter for real time updates of the event:
@ciscoliveeurope, #CLEUR
BRKSPG-2022 © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
Agend
Evolved
a Packet Core
 Mobile Network Evolution
- From 2G to 3G
 LTE/EPC introduction
 LTE/EPC Interfaces and Basic Procedures
- LTE/EPC Architecture and Interfaces
- Basic call flows (attach, intra-LTE mobility)
- Bearers, PDN connections and QoS
- Security
 Delivering voice with LTE/EPC
From 2G to 3G R8
Improving the mobile data services
Home Location Service Control
In the beginning…. Register (HLR) Point (SCP)
 There was wireless ISDN (aka GSM)
Base Station Mobile Switching Center +

Mobile Base Transceiver Controller Visitor Location Register
System (BTS) (BSC) (MSC/VLR)
Station
 Voice oriented architecture

 Re-define fixed wireline services (e.g. SS and IN)
 SMS is a signalling transport rather than a data service
 Network transport based on TDM
… data was circuit switched
 One burst every TDMA frame was sufficient to transport a speech
frame with source rate of 13 kbit/s
 GSM Phase 2 (circa 1996) added Circuit Switched Data support
offering 9.6 kbit/s service
 High Speed CSD consisted in aggregating multiple timeslot for a
single user but resource intensive
Modem Interworking Function
(IWF)
Modified V.110
3.1 kHz audio

or
V110 64k UDI
BSC MSC
.. and eventually packet data with General Packet Radio
System was bolted on
MSC/VLR Gateway MSC

BSC
BTS
IP
Packet Control Gateway GPRS

Serving GPRS Support Node
Unit (PCU)
Support Node (GGSN)
(SGSN)
IP IP
Relay
SNDCP SNDCP GTP GTP
LLC Relay LLC UDP UDP
RLC RLC BSSGP BSSGP IP IP
MAC Relay MAC Nw Services Nw Services L2 L2
GSM GSM
RadioBRKSPG-2022 64 kbps 64 kbps L1bis L1bis L1 L1
Radio © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
Home Based GGSN Roaming
Visited PLMN Home PLMN
GRX
BSC SGSN
BTS GGSN
 GPRS Roaming Exchange (GRX)

 GRX Services (as per GSMA IR.34)
DNS routing (for APN translation)
IP transport including routing & QoS
Security
 In future release, GRX is enhanced to become IPX (IP exchange) and
supports application proxy capabilities (e.g. for SIP), charging, etc.
3GPP UMTS System
 First step towards an all IP network
 New radio designed to accommodate greater packet throughput
(up to 2Mbits/s initially… In reality, can support up to 384 kbit/s)
 Core network remains largely unchanged from 2.5G
 Migration to ATM for Radio Access Transport
3G MSC
 More control into the RNC
PSTN
ATM/AAL
2
ATM/AAL
5
Node B 3G RNC IP
3G SGSN GGSN
3G Packet Architecture
Iu-ps Gn/Gp
NodeB Radio Network 3G SGSN GGSN

Controller (RNC)
IP IP
PDCP PDCP GTP-U GTP-U GTP-U GTP-U

RLC RLC UDP UDP UDP UDP
MAC Frame
MAC IP IP IP IP
Protocol
AAL2 AAL2 AAL5 AAL5 L2 L2
WCDMA WCDMA ATM ATM ATM L1 L1
ATM
Radio Radio
3GPP R4 Voice Services
HLR
MSC-s MSC-s
Iu-cs
IP
MGW MGW
INAP
MAP
Nb-UP
TCAP

RTP
Still Voice over CS bearer on the radio ac cess, data bearer not suitable (latency, overhea d)
 Option to transport Voice over IP in the C ore (see TS 23.205) SCCP

Introduction of SS7oIP transport
M3UA
BICC or SIP-T
H.248

Iu-UP UDP
AAL2 IP
ATM L1/2
SCTP
3GPP R5 to R7: Addressing the Bottlenecks
HSPA+: Distribute RNC
Data plane to NodeHBSDPA Removes Drift RNC and
adds intelligence to the Node B
Iu-ps Gn
Drift RNC
Node B Serving RNC 3G SGSN GGSN
IP Direct Tunnel allows IP

SGSN to remove itself
PDCP from data plane PDCP GTP-U GTP-U GTP-U GTP-U
RLC RLC UDP UDP UDP UDP
MAC MAC
Frame Frame
IP IP IP IP
FP
MAC-HS MAC-HS Protocol FP Protocol
AAL2/ATM AAL2 AAL2 AAL2/ATM ALA2L5/ATM AAL5/ATM L2 L2
WCDMA L1 L1 L1 L1 L1 L1 L1
WCDMA L1
3G architrecture summary
 Highlighting the growing importance of IP transport
3G MSC-S HLR/HSS
SGW PSTN
IP RAN
w/ ATM PW
or Native 3G MGW
Core IP
IP 3G RNC
Node B 3G SGSN GGSN
Introducing LTE
The 3GPP All-IP architecture
What is the LTE/SAE?
 Evolved Packet System (EPS) is the technology direction for

3GPP based networks
 Long Term Evolution (LTE) is the next generation 3GPP
radio
access network
- Evolved UMTS Terrestrial Radio Access Network (E-UTRAN)
 System Architecture Evolution (SAE) is the 3GPP next generation

standard for mobile networks providing:
- Increased Bandwidth
- End-to-End IP
- Simplified Architecture
- Support for multiple radio access technologies
 Evolved Packet Core (EPC) is the next generation 3GPP packet

core
Consists of (3) main components (MME, SGW, and PGW)
The LTE Revolution
 Radio Side (Evolved UTRAN - EUTRAN)

- Improvements in spectral efficiency, user throughput, latency
- Simplification of the radio network
- Efficient support of packet based services: Multicast, VoIP, etc.
 Network Side (Evolved Packet Core - EPC)

- Improvement in latency, capacity, throughput, idle to active transitions
- Simplification of the core network
- Optimization for IP traffic and services
- Simplified support and handover to non-3GPP access technologies
LTE/EPC Key Attributes
 Higher Bandwidth (>100 kbps per user on average) and improved latency
- Transmission and transition delays <10 & 100ms resp. in unloaded conditions
 Service independent and data-only architecture

- Strict data QoS mechanism with no voice dedicated bearer identifictaion
 Always-on model
- All registered users have a default bearer established used for signalling
 IP addressing
- IPv6 by default with dual stack sessions (IPv4v6)
 Support of alternative access technologies

- 3GPP and non-3GPP architecture, including possible wireline access
 Local breakout
- Part of the traffic may be routed directly in the visited network
3GPP Mobile Network
Evolution
GERAN CS Network
UTRAN
IP Services
Evolved
E-UTRAN / Internet
Packet Core
(LTE)
(EPC)
Non-3GPP
Access
EPS = Evolved
Packet System
LTE (Long Term
Evolution) is the 3GPP
WI that defined the E-
Evolved Packet System
Architecture
RNC SGSN GGSN
NodeB PDN/
Internet
RNC
MME
eNodeB PGW
PDN/
Internet
SGW
From hierarchical architecture to flat IP topology

Open to centralized or distributed deployments
RNC functions distributed between the eNB and the
EPC
LTE/EPC Key
Components
Next Mobility
PDN
Generation interconnect
Cell Site Control Destination
Node Network
Mobility
Anchor
UMTS, LTE/SAE Architecture:
Comparison
 SGSN  MME + Serving GW
- In the LTE architecture the SGSN functionality is split into MME & Serving GW
MME = Control Plane of SGSN
Serving GW = Data Plane of SGSN
 GGSN  PDN GW
- The PDN GW has similar
function as the GGSN
IP Anchor
Policy Enforcement
Accounting/Charging
Deep Packet Inspection
UMTS, LTE/SAE Architecture:
Comparison
LI OCS CGF
PCRF Gi AAA
HSS/HLR ADMF/DF HSS
Ro Ga
Gi X1,x2,x3 S6b SGi
S6a
Gx
Gx
GGSN GGSN P-GW

Gr Gr
Gxc Gx
Gn/Gp Gn/Gp S5/S8
S11
Gn/Gp SGSN S10
Gn/Gp
SGSN MME S-GW
GTP-U
IuPs IuPs
S1-U
S1-MME
RNC
RNC
Iub Iub
Iub Iub
nodeB nodeB
nodeB nodeB
eNB eNB
UMTS UMTS
(Direct Tunnel) LTE-SAE
Key 3G <-> LTE terminology differences
3G LTE
Primary PDP Context Default Bearer
Secondary PDP Context Dedicated Bearer
Routing Area Tracking Area
P-TIMSI (Packet- GUTI (Globally Unique Temp ID)
Temporary includes GUMMEI)
IMSI)
Attach + Default Bearer Act

Attach
Initial Content Setup Request
RAB Assignment
Request (Primary)
Bearer Setup Request
RAB Assignment
Request (Secondary)
EPC Protocol Stacks – Signalling Plane
MME
S1-MME
UE
eNodeB PDN-GW
S-GW
Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC)
NAS NAS
S1-MME
RRC RRC S1-AP S1-AP
PDCP PDCP SCTP 36.413 SCTP
RLC RLC IP IP
MAC MAC L2 L2
OFDMA OFDMA L1 L1
EPC Protocol Stacks – Data Plane
MME
S1-U S5/S8
UE
eNodeB PDN-GW
S-GW
IP (user) IP (user)
S1-U S5/S8
PDCP PDCP GTP-U GTP-U GTP-U PMIP PMIP GTP-U
36.414 29.274
RLC RLC UDP UDP UDP GRE UDP GRE
IP IP IP (GTP) IP
MAC MAC
L2 L2 L2 - L2
OFDMA OFDMA L1 L1 L1 29.275 L1
(PMIPv6)
EPC Protocol Stacks – X2 interface
MME
X2
UE
eNodeB PDN-GW
S-GW
X2-AP X2-AP GTP-U GTP-U

SCTP SCTP UDP UDP
X2-C X2-U
IP IP IP IP
L2 L2 L2 L2
36.423 36.424
L1 L1 L1 L1
EPC Roaming
Home Gateway Model
Rx
Gx
Operator’s
hPDN-GW IP
S6a
Services
Home Network (e.g. video,
IMS)
Visited Network S8
MME
eNodeB vS-GW
UE
EPC Roaming
Visited Gateway Model aka Local Breakout
S6a S9
Home Network
Visited Network
MME Gx Rx
Operator’s
IP
Services
eNodeB vS-GW vPDN-GW
UE (e.g. video,
IMS)
LTE/EPC Interfaces and Basic
Procedures
LTE Initial TS 23.401 Ch. 5.3.2.1 (for GTP S5)
Attach or TS 23.402 Ch. 5.2 (for PMIP S5)
All
UE
MME
PGW
eNB
DNS
SGW elements
selects
selects
used
retrieves
sends
forwards
may
assignsto
retrieve
PLMN
Create
MME
(SGW,
resolve
IP
subscription
Create
address(es)
and
and
PCC
Session
MME,
APNSession
eNodeB
sets
and
and
eNB)
up
information
Request
QoS
and
aid
Request
and
are
rules
binds
insets
to
up
and/or
SGW
bearer
connection
selecting
to
for
updated
PGW
radio
default
toauthenticates
toto
set
resources
and
PGW/SGW
the
bearer
set
ifupnone
PCC/QoS/billing
now
up
default
from
default
traffic
established
UE bearer
PCRF
can
with
bearer
flow
HSS
rules
(GTP
previously
S5 case) S6a
HSS PCRF
MME
S1-MME Gx
S11 DNS
LTE-Uu
S5/S8
S1-U
SGW PGW SGi
PDN
UE
eNB
 eNodeB combines some RNC functionality with LTE radio

 MME (Mobility Management Entity) controls network selection, attach and
mobility
- HSS for subscriber authentication
 SGW (Serving GateWay) provides local mobility anchor, inter PLMN
roaming, accounting
 PGW (Packet Data Network GateWay) provides IP anchor, QoS and
charging enforcement
 PCRF for PCC and QoS rules, service authorization
 In case of PMIP access, the SGW interacts with PCRF and PGW
with AAA
EPS
Bearers Example for S5 GTP
UE eNB SGW PGW PDN/

SGi Internet
S1 S5
Default Bearer: network initiated during the Attach
Dedicated Bearer: network initiated when needed
1 PDN
Conne
ction
 An EPS bearer uniquely identifies traffic flows that receive a common

QoS treatment between a UE and a PDN GW (GTP) or SGW
(PMIP)
 Default bearer is assigned during attach and provides always‐on IP
connectivity
- Internet‐like default connectivity for QoS‐agnostic needs (browser, email, etc.)
 Dedicated bearer is assigned only when needed to provide guaranteed

bit rate QoS control
APN “corp.com”
Multiple PDNs PDN Type IPv4
Connectivity Corporate
Network
UE eNB SGW
PGW APN “internet”

PDN Type IPv4v6
Internet
PGW
IMS
Default Bearer
Dedicated Bearer APN “IMS”
PDN Type IPv6
 Each PDN connection has one default bearer
- possibly one or more dedicated bearers
 All bearers of the same PDN Connection use the same IP address(es)
- IPv4, IPv6, or IPv4v6 (dual-stack)
 Multiple PDN connections may be served by one or more PGW nodes

- The UE can be attached to a single SGW at any point in time
Dedicated Bearer
Activation
 The PGW may activate a dedicated bearer, possibly after
indications from UE or PCRF
 The UE can only ask for the amount of resources, the network
decides whether an existing bearer is modified or a new one
is established.
UE eNodeB MME Serving GW PDN GW PCRF
1. IP-CAN Sessi on
(A)
Modification
2. Create Bearer Re quest
3. Create Bearer Request

4. Bearer Setup Request/
Session Management Request
5. RRC Connection Reconfiguration
6. RRC Connection Reconfiguration Complete
7. Bearer Setup Response

8. Direct Transfer
9. Session Management
Response
10. Create 11. Create Bearer Res ponse
Bearer
12. IP-CAN Sessi on
Respo Modification
nse (B)
Setting up additional PDN
connection MME S/PGW
UE
eNB
PDN Connectivity Request (APN,…)
Create Session Request
Bearer Setup Req. Create Session REsponse
(def bearer)
PDN Connectivity Accept
RRC
Bearer Setup
Resp
PDN Connectivity Complete
Modify Bearer
 The UE initate the request indicating the APN for the PDN connection
 Multiple APNs/PDNs must be managed by the UE and the applications
Quality of Service in the
EPS
• QoS parameters per EPS‐bearer
- QoS Class Identifier (QCI)
Scalar value used for scheduling/RRM decisions
- Allocation and Retention Priority (ARP)
Used to accept/modify/drop bearers in case of resource limitation
- Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) only for
dedicated bearers
• QoS paramers per group of EPS‐bearers
- Aggregate Maximum Bit Rate (AMBR)
Only for non‐GBR bearers, APN-AMBR and UE-AMBR
• Static mapping to/from 3GPP QoS partially standardized

- QCI ranges  Traffic Classes TS 23.401 Annex E
EPS Security
HSS
S6a EPS AKA via S6a
(Auth
Vectors)
Challenge and keys
exchange
MME
E- UTRAN Mutual Authentication

NAS Integrity/Ciphering
RRC Integrity and ciphering eNB
U-Plane Ciphering
UE
 USIM required for LTE

 Different set of keys used for ciphering, derived from the same
original K stored in the USIM/HSS
IP address(es)
LTE Mobility Management allocated to the UE
Attach Signaling connection

release
Power
On ECM-IDLE ECM-CONNECTED ECM-IDLE
RRC_IDLE RRC_CONNECTED RRC_IDLE
Signaling connection
Detach establishment
EMM-DEREGISTERED E
M
UE position unknown UE position known at eNB level M-
UE position known at TA level
R
No Context allocated Network controlled HO Cell reselection, paging
E
 EPS Mobility Management (EMM) defines the relation betweenGI UE and MME
ST
resulting from mobility
E
R
 EPS Connectivity Management (ECM) is related to the signaling connection
between UE and MME E
D
 RRC state is related to the connection established between UE and E‐
UTRAN
EPS Connectivity
TS 36.331 TS 36.413
UE RRC Connection
eNB
S1 Connection MME
ECM Connection
 UE and E‐UTRAN enter RRC‐CONNECTED state when the signaling

connection is established between UE and E‐UTRAN
 UE and MME enter ECM‐CONNECTED state when the signaling connection is
established between UE and MME
 Discontinuous Reception/Transmission (DRX/DTX) on the radio can influence
the time the UE is in Connected/Idle mode
- E.g. maintain the UE in Connected mode with DRX cycle as long as the paging
interval to save battery when the user is not transferring data
Tracking Area Update vs. Paging
Incoming data MME

Paging TAI list 2
Paging
Paging
Paging
Paging
Paging
Enter Idle
Mode
Enter
Connected
Mode
TAI list 1
Short TA List: more TAU, less Paging

Long TA list: less TAU, more Paging
TAU Procedure
HSS
Context Resp
Old New No UE context
Context
MME Request.
availablle
MME
TAU Request
TAI list 1 TAI list 2 TAU Accept
eNB
eNB
TAI not in
TAI list
 The TAU may require a relocation of the MME (as in the picture)
and/or also of the SGW
 The new MME identifies the old MME from the MME Id included
in the GUTI (Global Unique Temp. Id) sent in the Request
X2 Based
Handover
Update Bearer
MME SGW
Path Switch Req.
HO Request
HO Request
Ack.
eNB HO Command Data forwarding eNB
HO
Measurement Confirm
Reports
 Data forwarding over X2 interface only during the handover

 Fully eNB controlled, the EPC network is notified at the end
 Better performance than S1 based handover, but requires additional
connectivity in the RAN
MME RMC = Relative MME Capacity
Pooling
MME-1 MME-2 MME-3
RMC=1 RMC=2 RMC=3
MME Pool: area served by

one or more MME within E-UTRAN
which a UE may be served
without need to change eNB
the serving MME. eNB eNB eNB eNB
UE
 Load Balancing: the MME sends a weight factor (RMC) to be
used by the eNB for MME selection
 Load re-balancing: procedures for node offload (O&M
operation)
 MME relocation required for load re-balancing or for mobility
across different MME pool areas
EPC Node
Selection
 Process of Discovering/Choosing PGW, SGW, MME:
- Initial Attach (PGW and SGW)
- Additional PDN Connection (PGW)
TS 23.401
- Relocation/Handover (SGW, MME)
 The MME shall select:

- a PGW that provides the connectivity for a given APN
- a SGW to serve UE’s location
- a new MME to serve the target location (in case of relocation)
 Dynamic discovery via DNS NAPTR

- APN-FQDN for PGW TS 23.003,
internet.apn.epc.mnc123.mcc456.3gppnetwork.org TS 29.003
- TAI-FQDN for SGW and MME
tac-lb12.tac-hb34.tac.epc.mnc123.mcc456.3gppnetwork.org
 Selection based on multiple criteria
- Co-location, static DNS indications
Policy session TS 29.214
Control PCRF
Rx
request
Event &
AF
Access
Info Gxc Event & Notifications
Access Rules
QoS Info Gx TS 29.212
UE eNB SGW rules PGW

S5
EPS bearer with PMIP S5 PMIP tunnel (no QoS) Off-path PCC
EPS bearer with GTP S5

On-path PCC
 GTP S5  Gx for enforcement in the PGW

- PCEF (Policy and Charging Enforcement) in the PGW
 PMIP S5  Gxc for enforcement in the SGW

- No QoS information in PMIP
Voice over LTE Strategies
Voice & SMS Services
Providing Legacy Services in an LTE Network
 The EPS architecture (3GPP Rel 8) is

the first 3GPP all-IP architecture
 Voice and SMS are still the cash cows
for mobile operators
• Migration is critical
• User experience must be preserved
 CSFB is the interim solution
recommended by NGMN
 IMS is the target solution for
Telephony and Multimedia
Services
 OneVoice IMS profile
‘simplifies’ implementation
for VoLTE
 NGMN and OneVoice
initiatives reduce risk of
Circuit Switched Fallback (23.272)
Delivery of SMS to EPC Attached Subscriber
1
Incoming SMS
UTRAN / IuCS / A
MSC
GERAN
SGs
2
SMS is delivered via SGs interface
S6a
MME HSS
S1-MME S11
S1-U
Serving/
CSFB UE E-UTRAN
PDN
GW
 During EPC attach, CSFB UE’s are also attached over SGs to MSC
 MME maintains mapping of TA to LA to determine appropriate MSC to
establish SGs association with
 SMS can be delivered/sent without FallBack to legacy radio (SGs
interface includes SMS payload capability)
Circuit Switched Fallback (23.272)
Delivery of Terminating Voice Session to EPC Attached Subscriber
1
Incoming Call – delivered to VMSC which
has SGs association for this subscriber
4 UE Responds to paging –
incoming call terminated via
standard 2G/3G
procedures IuCS / A
CSFB UE UTRAN / MSC
GERAN
SGs
2
UE is paged via the SGs interface
3 S6a
UE retunes to 2G/3G RAT on MME HSS
receipt of page
S1-MME S11
S1-U
Serving/
CSFB UE E-UTRAN
PDN
GW
 SGs interface is used to inform UE of incoming call

 SGs Paging triggers UE to retune to 2G or 3G legacy network
 Page Response sent via the legacy radio network
 Call terminates to UE ‘normally’
Voice over IMS
Mobile Origination
1 IMS (HPLMN)
Subscriber has already registered
into IMS following EPC attach
UTRAN / IuCS / A MSC Server SCC AS TAS IP-SM-GW

GERAN (SR-VCC)
IuPS / Gb Sv Mg ISC
Cx I/S-CSCF MGCF
SGSN S3 S6a
MME HSS Mw
(SR-VCC)
P-CSCF
S11
S1-MME SGi
(Gm from UE)
S1-U Serving/
E-UTRAN
SR2- PDN GW
VUCECOUrEigi
nates Call
 To enable mid-call mobility, S-CSCF anchors call at SCC AS

 TAS provides end-user services (e.g. IR.92)
 MGCF provides breakout to PSTN or other CS networks
Voice over IMS
UE roams during active call – SR-VCC mobility
IMS (HPLMN)
3
SCC AS performs
bearer management
2
IuCS / A and tears down original
NewUcTaRl Al MSC Server SCC AS IP-SM-GW
SR-VCC UE leg
(SR-VCC)
eNg/
TAS
estaGblEisRhIuPS
A / Gb Sv Mg ISC
eNd
Cx I/S-CSCF MGCF
1 S3 S6a
UE retunes to 2G/3G SGSN MME HSS Mw
RAT during active call (SR-VCC)
P-CSCF
S11
S1-MME SGi
(Gm from UE)
S1-U Serving/
SR-VCC UE E-UTRAN
PDN GW
 SCC AS performs leg management – hides mobility events from other

IMS application servers
 SR-VCC only works in one direction – LTE -> 2G/3G
 Requires upgrades on legacy MSC infrastructure
CSFB – Deployment Challenges
 Some of the major challenges/difficulties facing CSFB rollout are:
 Legacy network dependencies
 Continued legacy network spend/investment
 Fallback latency / post-dial delay
 Ongoing operational complexity (TA/LA mapping)
CSFB – MSC/VLR Selection
As defined in 23.272
TA LA MSC/VLR TA LA MSC/VLR
TA1 LA1 MSC/VLR1 TA1 LA1 MSC/VLR1
TA2 LA1 MSC/VLR1 TA2 LA1 MSC/VLR1
MME TA3 LA2 MSC/VLR2 MME TA3 LA2 MSC/VLR2
Mapping
Error Area
TA TA TA TA TA TA
1 2 3 1 2 3
LA1 LA2 LA1 LA2
MSC/ MSC/ MSC/ MSC/
VLR1 VLR2 VLR1 VLR2
Roaming Retry
TS 23.272/23.018
 The Roaming Retry (complex) procedure is applied for mobile terminated

calls where the MSC, to which the UE sends the LAU, is different from the
MSC that sent the paging message to the UE.
1. IAM 12. IAM 10. RCH (Resume Call Handling)

4. IAM GMSC
GMSC
11. SRI
2. SRI 5. SGs Page
VMSC VMSC MME
MME
3. PRN
HLR HLR
9. Cancel Location
8. UL 12. PRN
6. Page
VMSC VMSC
7. Location Update 13. Call Establishment
Scenario Leading to Roaming Roaming Retry Invocation

Retry Requirement
TA to LA Mapping
Implementation Challenges
 Most network operates deploying LTE already have both 2G and

3G networks
 Mapping process has to take into account
 When UE falling back, is it likely to go to 2G or 3G overlapping cells?
 Where cell boundaries between 4G and 2G (or 3G) do not perfectly align, which
is provisioned?
 As cells ‘breathe’, boundaries become less predictable
 4G networks will be growing rapidly in near-term – requires constant
‘tweaking’
of provisioning tables
 One major tier-1 EMEA operator has already
concluded that it is not difficult to maintain
4G
accurate TA to LA mappings... ...it is, in their
view, impossible ? TA’
s
 Therefore, Roaming Retry invocation will be 3G
more common than expected even though LA’s
considerable effort may be expended
maintaining tables 2G
LA’s
Dependencies for CSFB
As Specified by TS 23.272
 UE
 UE must support CSFB procedures as defined with TS 23.272
 MME
 Must support SGs interface
 Must support MSC/VLR selection procedures
 MSC
 Must support SGs interface (legacy MSC’s will require addition of IP
interface cards)
 Should support Roaming Retry procedure to minimise call drops
 HLR
 Should support Roaming Retry procedure to minimise call drops
Cisco CSFB Product Strategy
 Cisco has developed a CSFB product strategy that addresses:
 Inefficient operational deployment model – operators not forced to upgrade
legacy MSC and HLR platforms
 Investment legacy Capex spend – no investment required on legacy MSC
or HLRs
 Complicated MME provisioning procedure – requires only static TA-LA
mappings
 The Cisco solution places no dependencies on existing network elements (CS or
EPC)
 Supports both SMS (originate/terminate) and Voice (CSFB)
 Roaming Retry procedural support not required
CSFB IWF – Architectural Fit
Um GERAN/ A/Iu
MSC/VLR MAP
UTRAN
UE HLR
MAP
LTE-Uu S1-MME SGs
E-UTRAN MME CSFB IWF
S6a MAP
HSS SMSC
 CSFB IWF supports only SGs and MAP interfaces

 Appears as a ‘thin’ MSC/VLR – is allocated a pseudo LA
 Does not touch the bearer traffic within legacy network
EPC Attach / Location Update Procedure
3G 4G
Core HLR HSS Core 1. UE Registers in LTE
MAP
2. Serving MME registers with HSS
4
2
3. Serving MME informs registered VLR
(CSFB IWF)
CSFB SGs
MSC MME
IWF
3 4. CSFB IWF registers as serving MSC with
HLR
1
RNC E-UTRAN
3G/4G
Device
3G 4G UE
4G
Access Access
Mobile Originated SMS
3G 4G
Core HLR HSS Core 1. UE initiates SMS
2. MME sends SMS to serving MSC (CSFB

SMSC
MAP IWF)
3
3. CSFB IWF sends SMS to SMSC
CSFB SGs › CSFB IWF performs SMS MO service
MSC IWF MME logic
2
› CSFB IWF performs SMS MO billing
› CSFB IWF performs LI if required
BSC/RNC E-UTRAN
3G/4G
Device
3G 4G UE
4G
Access Access
Mobile Termination SMS
3G 4G
Core HLR HSS Core 1. Incoming SMS to SMSC
2 2. SMSC queries HLR to determine routing
MAP
SMSC
1 3 3. SMSC sends SMS to serving MSC (CSFB
IWF)
CSFB SGs
MSC IWF MME 4. CSFB IWF sends SMS to MME
4
› CSFB IWF performs SMS MT service logic
› CSFB IWF performs SMS MT billing
› CSFB IWF performs LI if required
5. MME sends SMS to UE
RNC E-UTRAN
3G/4G
Device
3G 4G UE
4G
Access Access
Mobile Origination
3G 4G
Core HLR HSS Core 1. UE leaves LTE and re-tunes to
MAP
GSM/UMTS
2 3
2. UE Location Updates on GSM/UMTS
3. HLR sends Cancel Subscriber to CSFB
CSFB SGs IWF
MSC IWF MME
› CSFB IWF Removes subscriber from
VLR
4. UE initiates
4 call
RNC E-UTRAN
Note: MO Procedure utilised for Call Originations,

3G/4G
3G Device
USSD and also for SS
3G Device 4G modifications
4G UE
Access Access
Mobile Terminated Call
Signalling times and delays example
500 ms additional delay
to avoid race Inserts MSRN from
conditions VMSC into original PRN
Response
This delay may vary 13. MAP PRN Resp
depending on RAN T0+2880ms
conditions 12. SRI ACK T0+2869
HLR 9. SRI
T0+2767ms
3. MAP PRN
T0
2. MAP SRI
8. MAP CL
T0+2222ms 4. SGs Page
14. MAP SRI Ack
IWF T0+7ms MME
10. MAP PRN
1. IAM 11. MAP PRN Resp

GMSC
7. MAP UL 5. Page
15. IAM 6. LU
VMSC
16. Page
Note: only key messages are shown for simplicity (e.g. not all acknowledgments are shown)
Benefits of CSFB IWF
 Solution enables deployment of SMS over SGs and CSFB through a

centralised gateway
 Does not require SGs software licensing (or IP hardware upgrades) on
any network MSCs
 Operators no longer locked in to a existing vendors (current MSC
suppliers) for CSFB solution
 Reduced operational rollout costs and complexity
 Common platform for other Cisco CSP services – ensures investment
protection moving forward into IMS
 Requires no specific TA to LA mapping changes on MME (i.e. MME is
provisioned as if it is connecting to standard SGs interface)
 Does not require or utilize Roaming Retry
 Signalling only solution, no bearer impact
VoLTE (IMS) – Deployment Challenges
 Some of the major challenges/difficulties facing VoLTE rollout are:
 Service parity/consistency
 Network complexity
 Back office (re)integration
 Legacy network dependencies (SR-VCC)
 Call routing and optimisation
Single Radio Voice Call Continuity
 SR-VCC
 Voice call anchored in IMS over PS (e.g. LTE) access
 UE moves to area of CS access only
 UE is capable of transmitting/receiving on only one of those access
networks at a given time.
 Mobility handled at two levels
 Radio
 S1, Sv and MAP-E signaling
 Application
 SIP / SDP
 Requires Service Centralization and Continuity Application Server (SCC AS)
 From SCC AS perspective, seen as a PS to CS access transfer
Additional
Resources
- www.3gpp.org
- http://www.thespectool.com/v2/index.php
Relevant 3GPP Specifications:
• TS 36.300 E-UTRA and E-UTRAN Overall description; Stage 2
• TS 36.331 E-UTRA; Radio Resource Control (RRC); Protocol
specification
 TS 23.401 GPRS enhancements for E-UTRAN access (EPC)
 TS 23.402 Architecture enhancements for non-3GPP access
• TS 24-301: Non-Access-Stratum (NAS) protocol for EPS;
Stage 3
• TS 29.272: EPS; MME and SGSN related interfaces based on
Diameter protocol
• TS 33.401 3GPP SAE; Security architecture
Recommended Reading
Please visit the Cisco Store for suitable reading.

Please complete your Session Survey
We value your feedback
 Don't forget to complete your online session evaluations after each session.
Complete 4 session evaluations & the Overall Conference Evaluation
(available from Thursday) to receive your Cisco Live T-shirt
 Surveys can be found on the Attendee Website at

www.ciscolivelondon.com/onsite which can also be accessed through the screens
at the Communication Stations
 Or use the Cisco Live Mobile App to complete the

surveys from your phone, download the app at
www.ciscolivelondon.com/connect/mobile/app.html
1. Scan the QR code
(Go to http://tinyurl.com/qrmelist for QR code reader
software, alternatively type in the access URL above)
2. Download the app or access the mobile site
3. Log in to complete and submit the evaluations
http://m.cisco.com/mat/cleu12/
Thank you.

Evolved EPC For LTE by Cisco 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Evolved EPC For LTE by Cisco 1

Uploaded by

Copyright:

Available Formats

Evolved Packet Core for LTE Networks

Follow us on Twitter for real time updates of the event:

 We value your feedback- don't forget to complete your online session

 Delivering voice with LTE/EPC

Base Station Mobile Switching Center +

 Voice oriented architecture

3.1 kHz audio

MSC/VLR Gateway MSC

Packet Control Gateway GPRS

Visited PLMN Home PLMN

 GPRS Roaming Exchange (GRX)

NodeB Radio Network 3G SGSN GGSN

PDCP PDCP GTP-U GTP-U GTP-U GTP-U

 Option to transport Voice over IP in the C ore (see TS 23.205) SCCP

IP Direct Tunnel allows IP

 Highlighting the growing importance of IP transport

Node B 3G SGSN GGSN

 Evolved Packet System (EPS) is the technology direction for

 System Architecture Evolution (SAE) is the 3GPP next generation

 Evolved Packet Core (EPC) is the next generation 3GPP packet

 Radio Side (Evolved UTRAN - EUTRAN)

 Network Side (Evolved Packet Core - EPC)

 Service independent and data-only architecture

 Support of alternative access technologies

From hierarchical architecture to flat IP topology

GGSN GGSN P-GW

Gn/Gp Gn/Gp S5/S8

Attach + Default Bearer Act

Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC)

Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC)

Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC)

X2-AP X2-AP GTP-U GTP-U

 eNodeB combines some RNC functionality with LTE radio

UE eNB SGW PGW PDN/

 An EPS bearer uniquely identifies traffic flows that receive a common

 Dedicated bearer is assigned only when needed to provide guaranteed

PGW APN “internet”

 Multiple PDN connections may be served by one or more PGW nodes

2. Create Bearer Re quest

3. Create Bearer Request

5. RRC Connection Reconfiguration

6. RRC Connection Reconfiguration Complete

7. Bearer Setup Response

• Static mapping to/from 3GPP QoS partially standardized

E- UTRAN Mutual Authentication

 USIM required for LTE

Attach Signaling connection

 UE and E‐UTRAN enter RRC‐CONNECTED state when the signaling

Incoming data MME

Short TA List: more TAU, less Paging

Path Switch Req.

 Data forwarding over X2 interface only during the handover

RMC=1 RMC=2 RMC=3

MME Pool: area served by

 The MME shall select:

 Dynamic discovery via DNS NAPTR

UE eNB SGW rules PGW

EPS bearer with GTP S5

 GTP S5  Gx for enforcement in the PGW

 PMIP S5  Gxc for enforcement in the SGW

 The EPS architecture (3GPP Rel 8) is

 SGs interface is used to inform UE of incoming call

UTRAN / IuCS / A MSC Server SCC AS TAS IP-SM-GW