Evolved Packet Core CCT PDF

Contents
1 Network Architecture
2 Procedures in EPC
3 Quality of Service
4 Voice Service
5 SMS Service
6 Key Features in LTE/SAE
Page 1
1.1 SAE Network Architecture
1.2 Interfaces and Protocols
1.3 Roaming Architecture
1.4 Interworking with other networks
Page 2
2G/3G to LTE/SAE Architecture
PGW
SGW
MME PCRF
Terminals LTE Network SAE/EPC Network
• Flat and all-IP Network Architecture

• Reduced Complexity
• Seamless Mobility
• Separation of Control Plane (MME) and User Plane (SGW) with open interface S11
Page 3
LTE/SAE Architecture - 2
• End-users profile (MSISDN, APNs…)
•Negotiates QoS requirement with application
•Authorizes QoS request against user subscription data
•Receives network events
•Decides policy rules to be applied (filters, QoS
parameters QCI, MBR, GBR, ARP)
GERAN SGSN
UTRAN HSS/HLR PCRF •Application

•NAS signaling with UE (+security) S3 •Mobility anchor for •Signalling (PCRF
•Tracking Area list management S12 S6a and terminal)
inter-eNB handover
•PGW and SGW selection •Lawful Interception
•Authentication S4 •Packet Routeing and
•Bearer control forwarding
•Handover coordination with SGW, AS
other MME or SGSNs (IRAT) Gx Rx
• Lawful Interception of signalling
traffic. MME
S1-MME S11
S5/S8
SGi Internet / intranet /
Operators in-house
E-UTRAN S1-U & 3rd Party AS
Terminal S-GW PDN-GW
(LTE/UMTS/GSM
•Radio resources allocation

•Application (incl. signaling) •Scheduling,
•UL filtering of traffic flow to bearer •Admission Control
•APN-AMBR policing •UL filtering, •IP address allocation
•Mobility support •interference control (ICIC) •EPS bearer control
•Idle mode reselection •Handover •DPI
•Handover measurements •Idle mode cell reselection priorities •Lawful Interception
•QoS mapping (S1 Bearer/backhaul QoS)
Page 5
1.4 Interworking with GERAN/UTRAN
Page 6
User Plane Control Plane
LTE-Uu Interface
•Transfer of upper layer PDUs

•Error correction through ARQ (CRC check
provided by the physical layer)
•Segmentation •Header compression and decompression for user
•Concatenation of SDUs for the same radio plane data.
bearer •Ciphering and deciphering for user plane and
•In-sequence delivery of upper layer PDUs control plane data.
except at HO. •Integrity protection and verification for control plane
•Duplicate Detection data.
•Protocol error detection and recovery •Handover support functions.
•SDU discard •Discard for user plane data due timeout.
• Reset
The AS protocols on E-UTRAN-Uu (RRC, PDCP, RLC, MAC and the physical LTE layer) implements the Radio
Resource Management and supports the NAS protocols by transporting the NAS messages across the E-UTRAN-Uu
interface.
Page 7
Interface S1 It carries signaling
messages between
eNodeB and MME
S1-MME
MME
S1-U
E-UTRUAN SGW
It carries user traffic

between eNodeB and
SGW
S1 interface connects the EUTRAN to the EPC. S1 is split into control plane, called S1-
MME, and a user plane, called S1-U.
Page 8
S1-MME Interface •One logical S1AP connection per UE.

•Multiple UEs supported via a single
SCTP association.
NAS NAS
Relay
RRC S1-AP
RRC S1-AP
PDCP PDCP SCTP SCTP
RLC RLC IP IP
MAC MAC L2 L2
L1 L1 L1 L1
LTE-Uu S1-MME
UE eNodeB MME
•Set up, modification and release of E-RABS.
•Establishment of an initial S1 UE context
•Paging and S1 management functions. Provides reliable transport.
•NAS signaling transport functions between UE • it’s rate adaptative and message-
and MME. oriented.
•Status transfer functionality • Multi-streaming function
•Trace of active UE’s, and location reporting.
• Multi homing
•Mobility functions for UE to enable inter and
intra RAT HO.
S1MME is responsible for EPS bearer setup and release procedures, handover signaling,
paging, NAS Signaling transport and UE context management.
Page 9
S10 and S11 Interfaces

The main function is to transfer
the contexts for individual
terminals attached to EPC and
thus sent on a per UE basis.
Keeps the control and user plane

procedures in sync for a terminal durng
the period that the terminal is seen
active/attached in the EPS.
Page 10
Interfaces S5/S8 (Control Plane)

There are two protocol options to be used in S5/S8 interface: GTP or PMIPv6
PMIPv6 PMIPv6
IPv4/IPv6 IPv4/IPv6
L2 L2
L1 L1
Serving GW PDN GW
S5 or S8
S5/S8 over GTP S5/S8 over PMIPv6

•Provides the functionality associated with •Provides tunneling management between
creation/deletion/modification/change of the Serving Gateway and PDN Gateway.
bearers for individual user connected to EPS.
Page 11
S6a and Gx Interfaces

Diameter Diameter
SCTP/TCP SCTP/TCP
IP IP
L2 L2
L1 L1
S6a
MME HSS
Interface Functionality: Interface Functionality:

•Exchange location information
•Authorize a user to access the EPS • Gx enables the
•Exchange authentication information
transfer/modification/removal of
•Download and handle changes in the subscriber data stored in the
server PCC rules from the PCRF to
•Upload the PGW identity and APN being used for a specific PDN PCEF function within the PGW.
connection.
•Download the PGW identity and APN pairs being stored in HSS for
already ongoing PDN connection.
Page 12
Interface S13
Interface Functionality:
The S13 and S13’ interfaces between the MME and the EIR and between the SGSN and the EIR
respectively are used to check the status of the UE (e.g. if it has been reported stolen). The MME or
SGSN checks the ME Identity by sending the Equipment Identity to an EIR and analyzing the
response.
Page 13
Interfaces S1-U,SGi and S5/S8 (User Plane)

One or more GTP
tunnels per user
Note that both IPv4 and IPv6 are supported on the transport layer of IP
Application
IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U
GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
LTE-Uu S1-U S5/S8 SGi

• GTPU carry encapsulated payload and signalling a
UE nodes.
messages between eNodeB Serving GW PDN GW
•Provides non-guaranted data delivery.
•S1-U is the user plane interface between EUTRAN and SGW, carrying user traffic in a GTP-U tunnel.
•SGi is the reference point between the PDN GW and the packet data network. PDN may be an
operator external public or private packet data network or an intra operator packet data network, e.g.
for provision of IMS services. This reference point corresponds to Gi for 3GPP accesses.
Page 14
1.5 SAE Key Feature on Handover
Page 15
Home Routed
VPLMN HPLMN
Gb SGSN HSS PCRF
GERAN
Iu
S3 S4
S6a Rx diameter
Gx message
S12
UTRAN
S11
S8a
S1-MME MME SGi
Operator’s
S1-U IP Service
E-UTRUAN S-GW PDN-GW
In this Scenario, the PCEF (PGW) is located in, and controlled by, home operator.
The PCEF connects to the H-PCRF via Gx and online charging can be performed
via Gy to the OCS in a similar way as for non-roaming scenarios.
Page 16
Local Breakout with Home Service
H-PCRF makes decision after
VPLMN HPLMN received the visited AF
SGSN HSS H-PCRF requirement from V-PCRF
Gb
Rx
Operator’s
GERAN
IP Service
Iu
S4
S3
S9
S6a
V-PCRF
S12
UTRAN
S11
Gx
S1-MME MME S5
SGi Visited
Operator’s PDN
S1-U
Control of allowed services and the authorization of resources are always handled
by the H-PCRF.
Page 17
Local Breakout with Visited Service
H-PCRF makes decision after
received the visited AF requirement
VPLMN HPLMN from V-PCRF
HSS H-PCRF
SGSN
Gb
GERAN
Iu S4
S3
S9
S6a
V-PCRF
S12
UTRAN Rx
S11
Gx
MME S5
S1-MME
SGi
Visited Operator’s
PDN
S1-U
Control of allowed services and the authorization of resources are always handled
by the H-PCRF.
Page 18
S9 Interface
Interface Functionality
• S9 transfer policy decisions from HPLMN to VPLMN and transport the events that may occur in the
VPLMN to HPLMN.
• Can be also used to transfer session information in specific roaming scenarios.
• in LBO, S9 also carries service session information from V-PCRF to H-PCRF.
Page 19
Page 20
Interworking between LTE/SAE and GERAN/UTRAN
Page 21
Solution 1- Pre-Rel 8 UMTS/GPRS Interworking
BTS BSC/PCU
GSM BSS SGSN
Gn GGSN Gi
NodeB RNC Gn/Gp Internet
UMTS RAN Gi/SGi
Legacy PS
SAE/LTE
MME
S11
P-GW
eNodeB
E-UTRAN
S-GW
In this Scenario:
- MME translates the security context of EPC into the legacy PS format (R8 QoS profile into R99/R97 QoS
profile) and just acts as a SGSN to interconnect with legacy PS core.
- PGW also support GGSN function and can act as the common anchoring point for the UE wherever the it
is in EPC or in the legacy PS core.
Page 22
Inter-working with legacy PS by Gn/Gp
BTS BSC/PCU
GSM BSS SGSN
Gn GGSN Gi
Gn
NodeB RNC Internet
UMTS RAN Gi/SGi
Legacy PS
SAE/LTE
MME
S11
P-GW
eNodeB
E-UTRAN
S-GW
How can SGSN select the GGSN or PDN-GW based on the type of subscribers (2G/3G or 2G/3G/LTE)?
Three solutions:
 Access Restriction Data (ARD) and/or MS Network Capability based
 APN-based
 IMSI range
Page 23
Note:
Requirements on Legacy to Handle Mobility
GGSN / PGW Selection Description Requirements / Impact on legacy
Solution
ARD and/or • SGSN makes use of Access Restriction Data (ARD) • SGSN upgrade to support a new GGSN/PDN-GW selection
MS Network Capability and/or MS Network Capability to select the PDN- method
GW/GGSN • DNS reconfiguration
• HLR reconfiguration
APN-Based • Configure new APNs in LTE network • New APNs have to be configured in HLR, DNS and LTE MS
• LTE subscriber uses the new APN
IMSI range • LTE users have a separate IMSI segment • LTE users have a separate segment
• SGSN makes use of IMSI segment to select the • DNS reconfiguration
GGSN/PDN-GW
Page 24
Solution 2 - Rel 8 UMTS/GPRS Interworking
Enhacement to support:
1. SGW, PGW selection
2. MME selection
BTS BSC/PCU
GSM BSS SGSN
S3 S4
NodeB RNC SGi Internet
UMTS RAN
Legacy PS S11
SAE/LTE MME S-GW P-GW

S1-MME
eNodeB
S1-U
E-UTRAN
The EPC core interconnect with legacy 2G/3G PS core by S3/S4 interface. In this solution, the existing
SGSN should be upgraded to become S4 SGSN and the existing GGSN should be upgraded to
become SAE GW. The SGW becomes the common anchoring point between LTE and 2G/3G. In this
case, the legacy PS core can enjoy some enhancement of R8, such as the label QoS profile, the idle
signaling reduction etc.
Page 25
Gn/Gp and S3/S4 Comparation
Benefits Limitations
SGSN shall be able to select

No impact on the GGSN or GGSN/PGW
Gn/Gp legacy or roaming based on the type of
networks subscribers.
Solution
Legacy SGSN and GGSN

Optimization of the
should be upgraded to S4
S3/S4 signalling load for all SGSN and SAE GW.
terminal in iddle mode.
Solution (ISR)
ISR: Idle Mode Signaling Reduction
Page 26
S3
S4
• S3 transfer the information related to handover/relocation between 2G/3G and LTE.

• The S4 interface supports signaling and provides procedures to enable user plane tunnel between
SGSN and SGW, in case 3G has not enable direct tunnel for user plane traffic from RNC to SGW.
Page 27
S16 and S12
Interface Functionality:
• S12 is a reference point between
• S16 main function is to transfer the context for UTRAN and Serving GW for user
individual terminals attached to EPC network plane tunneling when Direct Tunnel is
established
Page 28
Interworking between LTE/SAE and Trusted non-3GPP
Page 29
Solution for Trusted non-3GPP Networks
* 3GPP AAA Server
We will took CDMA network as an example of trusted non-3GPP networks. It includes

the emergence of eHRPD network, depicted by the darker entities.
Page 30
Control Plane – PMIPv6
S2a Interface
User Plane – PMIPv6
Note: PMIPv6 or MIPv4-FA can be used on S2a.
• S2a provides user plane tunneling and tunnel management between the trusted non-3GPP access and
the PDN GW.
• It also provides mobility support for mobility within the trusted non-3GPP access and between different
accesses.
Page 31
Control Plane – MIPv4
S2a Interface
User Plane –MIPv4
• S2a provides user plane tunneling and tunnel management between the trusted non-3GPP access and
the PDN GW.
• It also provides mobility support for mobility within the trusted non-3GPP access and between different
accesses.
Page 32
S6b Interface
• It informs the 3GPP AAA server/proxy about current PGW identity and APN being used for a given UE, or that a certain PDN GW
and APN pair is no longer used.
• Retrieves specific subscription-related parameters such as a subscribed QoS profile for non-3GPP accesses.
(if uses DSMIPv6 to attach the UE to EPC):

• Authenticate and authorize the UE and indicate to the PGW that a PGW re-allocation shall be performed.
• It is used to transport a session termination indication from the 3GPP AAA server/proxy to the PDN GW, to trigger a termination of
a PDN connection.
(if uses MIPv4 to attach UE to EPC):

•S6b is also used to authenticate and authorize the Mobile IPv4 Registration Request message that was sent by the UE.
Page 33
STa Interface
• Authentication and Authorization for non-3GPP IP Access.
• Transport of subscription data (i.e QoS profile)
• Transport mobility parameters needed for S2a and related to S2C.
• Transport information about IP mobility Mode Selection. This includes information about mobility
features supported by non-3GPP Access and selected mobility mechanism used by 3GPP AA
server/proxy.
Page 34
SWx Interface
• AAA server registration
• Upload PDN GW identity and APN
• PDN GW identity and APN download
• AAA-initiated de-registration
• HSS-initiated de-registration
Page 35
Gxa Interface
• The main purpose is to support QoS rules and event handling for PCC.
• Gxc applies when BBERF is located in the SGW and Gxa when BBERF is located in an
AGW (HSGW).
Page 36
Control Plane
User Plane
• S101 enables interactions between EPS and HRPD access to allow for pre-registration and handover
signaling with the target system.
• The S103 interface from the Serving GW to the HSGW in the CDMA HRPD network. This interface
provides support for forwarding of downlink data during handover from LTE to HRPD
Page 37
Interworking between LTE/SAE and Untrusted non-3GPP
Page 38
Solution for Non-Trusted non-3GPP networks
* 3GPP AAA Server
A new logical node called the ePDG (evolved Packet Data Gateway) allows interconnection (but not
inter-access mobility) of untrusted non 3GPP access (i.e. WLAN) to 3GPP network.
Page 39
Control Plane
Interface Swu
User Plane
• Swu interface supports procedures for establishment/disconection/modification of and e2e tunnel
between UE-ePDG.
• The tunnel between UE and ePDG is an IPsec tunnel. The UE and ePDG use IKEv2 to establish the
IPSec security association (SA) for the tunnel.
Page 40
Interface SWm
Interface Functionality Interface Functionality

• Authentication and Authorization for non-3GPP IP
Access.
• Transport of subscription data (i.e QoS profile) • SWn tunnels user data packets between
• Transport mobility parameters needed for S2a and untrusted IP access networks and the ePDG.
Interface
related to S2C. Functionality
• Transport information about IP mobility Mode Selection.
This includes information about mobility features
supported by ePDG and selected mobility mechanism
used.
• Transport session termination indications and request
from 3GPP AAA to ePDG.
Page 41
Interface SWx
• Authentication and Authorization for non-3GPP IP Access.
• Transport of subscription
Interface data (i.e QoS profile)
Functionality
• Transport mobility parameters, that is PMIPv6 or IPv4 is used to connect UE to EPC.
•Transport information about IP mobility Mode Selection. This includes information about mobility
features supported by non-3GPP Access and selected mobility mechanism used by 3GPP AA
server/proxy.
• Transport session termination indications and request from 3GPP AAA to ePDG.
Page 42
Interface Swa
• Swa is used for 3GPP-based access authentication/authorization with an untrusted non-
3GPP access.
• Also support reporting of accounting information generated by access network.
Page 43
Control Plane
S2b Interface
User Plane
• S2b provides user plane tunneling and tunnel management between ePDG and the PDN GW.
Page 44
Gxb Interface
Gxb
ePDG
• The main purpose is to support QoS rules and event handling for PCC.
Page 45
Trusted/Untrusted non-3GPP networks with S2c
Page 46
Interface S2c S2c over trusted non-3GPP access
S2c over untrusted non-3GPP access
• The S2c interface provides the user plane with related control and mobility support between UE and
the PDN GW. This interface is implemented over trusted and/or untrusted non-3GPP Access and/or
3GPP access.
Page 47
Contents
2 Procedures in EPC
4 Voice Service
5 SMS Service
Page 48
2 Procedures in EPC
1.1 Key Concepts
1.2 Attach and Detach Procedure
1.3 Tracking Area Update
1.4 Handover Procedure
Page 49
Default and Dedicated Bearers
The “bearer” is a central element of the EPS QoS concept. It provides a logical
transport channel between the UE and the PDN for transporting IP traffic and a
set of QoS parameters (i.e. bit rates, delay and bit error rate, etc)
MME
E-UTRUAN PDN-GW
S-GW
Operator’s
IP Service
Default Bearer Dedicated Bearers
 The first EPS bearer that is activated  Additional EPS Bearers that may be
when PDN connection is established. activated for a PDN connection.
 It remains established during the  Used for new QoS requirements
lifetime of the PDN connection. It can be activated/desactivated by
 It assigns basic conectivity (IP, demand.
QoS).  Share IP address with Default Bearer.
Page 50
UE Identifiers Globally Unique Temporary Identifier
HSS
GUMMEI: Global Unique MME Identifier

M-TMSI: MME Temporary Subscriber Identity
MCC: Mobile Country Code
MME MNC: Mobile Network Code

GUTI –Registered-MME
MMEI: MME Identifier within the network
MMEGI: MME group ID
MMEC: MME Code
E-UTRAN
S-GW P-GW
IP Address-Registered-PGW
Page 51
Tracking Area
Tracking
Area List 1
TA1
TA1
TA6
TA2
TA2
TA4
TA3
Tracking
TA3
TA6 Area List 2
• Traking Area is a set of contiguous cells. Several Tracking Areas are combined into one TA
list in which UE’s movement will not trigger Tracking Area Update procedure.
• All TAs of TA list are managed by the same MME.
• The UE also performs TA Update when the periodic TA Update timer expires.
Page 52
Mobility Scenario: Idle and Connected Mode
Handover decision and cell priorities based on
criterias such as:
 Target cell/system capabilities

Candidate cells
 Coverage
WCDMA LTE  Load in own and target system
HSPA
 UE type or behavior (broadband , mobile phone,
Load information cell selection statistics, speed)
 Services in use by user (QCI: non-GBR, GBR,
multiple bearers)
UE LTE
Load balancing
X2 supports load information sharing in LTE
 RAT target radio link load
Handover decision
 Node load (GBR, non-GBR)
•Source eNB/RNC selects target cell  Transport link load
Idle mode cell selection Load information used in handover decision and
• eNB sets priorities in neighbour cell list to set cell selection priority in broadcasted
• UE selects target cell Neighbor cell/RAT lists
Benefits
Improved probability for successful handover
Page 53
Mobility Management: Idle Mode
UE periodically updates its
MME current location to MME,
at TA level.
UE State
S-GW PGW
SDF PDN
eNodeB
RRC-Iddle Mode
What is idle mode? What are the benefits?
• An UE is considering in idle mode when • Conserves resources in UTRAN and still

there is no NAS signaling connection between maintain the contact with UE (paging)
UE and network; on timely basis;
• eNB has no information of UE, no RRC • Conserves battery power in UE.
connection, no S1 connection;
• At least one PDN connection exist.
Page 54
2 Procedures in LTE/SAE
1.1 Key Concepts
1.4 Cell Selection and Cell Reselection
1.5 Handover
Page 55
Network Attach Procedure
Page 56
Network Attach Procedure
E-UTRAN HSS
UE MME S-GW P-GW
Network Discovery, access system selection

Step 0. and RRC connection
Step 1.
Initial Attach
MME selection & S1 Bearer Setup
Step 2.
Authentication and Secutiry
SGW & PGW selection
Step 3.
Default EPS Bearer Setup
Step 4.
IP Address Allocation
Page 57
1. Initial Attach
E-UTRAN
UE MME
0. Signalling Radio Bearer
1A Attach Request
1C. Initial UE Message
1B. MME Selection 1D. Downlink NAS Transport
1E. S1-MME Bearer
1A.The initial attach process begins with an Attach Request from UE, including the UE identity,its network capabilities and
the resources it wants.
1B. The eNB selects a MME for the UE. eNB may eb connected to multiple MMEs (for redundancy and network sharing) and
the MMEs may be grouped into pools.
1C. The eNB forwards the Attach Request to the selected MME over the S1 interface in an initial UE message.
1D. The MME processes the request and responds with a NAS message within a Downlink NAS Transport Message.
1E. At this point the S1-MME signalling bearer is in place
Page 58
2. Authentication and Security
UE MME HSS
2A Authentication Information Request
2D. Store KASME &

XRES
2C. Auth. Information Response
2E. Auth. Request 2F. Generate KASME, AUTN & RES using 2B. Generate KASME, AUTN &
K & RAND and compares if XRES using K & RAND
AUTNUE=AUTNMME
2G. Auth.
Response 2H. Compare RES=XRES
SGW and PGW Selection

2I. AS and NAS Secutiry Procedure
2A. MME retrieves UE’s security information from the HSS using an Authentication Information Request Message.
2B. The HSS maps the IMSI to a Subscriber Authentication Key (K) and generates : XRES, KASME and AUTN.
2C. XRES and KASME are sent to MME into the Authentication Information Response message.
2D. These parameters are stored into the MME for later used.
2E. The MME sends K, AUTN and RAND to UE into the Authentication Request message.
2F. The UE generates KASME, AUTN and RES and compares AUTN value generated with the AUTN received form MME to decide if the network has
been authenticated successfully.
2G. UE responds with an Authentication Response Message including the RES value.
2H. The MME compares RES with XRES. If the values match, then the UE has been successfully authenticated
2I. AS and NAS encryption and integrity checking can be established.
Page 59
3. Default EPS Bearer Setup - 1
MME S-GW P-GW
IP Address Allocation
3A. Create Session Request
3B. Create Session Request
3C. Create Session Response
3D. Create Session Response
Default S11 GTP-C Tunnel Default S5/S8 GTP-C Tunnel
Default EPS S5/S8 Bearer
2A. MME retrieves UE’s security information from the HSS using an Authentication Information Request Message.
2B. The HSS maps the IMSI to a Subscriber Authentication Key (K) and generates : XRES, KASME and AUTN.
2C. XRES and KASME are sent to MME into the Authentication Information Response message.
2D. These parameters are stored into the MME for later used.
2E. The MME sends K, AUTN and RAND to UE into the Authentication Request message.
2F. The UE generates KASME, AUTN and RES and compares AUTN value generated with the AUTN received form MME to decide if the network has
been authenticated sucessfully.
Page 60
E-UTRAN MME
UE
Signalling Radio Bearer S1-MME Bearer
3E. Initial Context Setup Request
3F. RRC Connection Reconfiguration •New GUTI

•TAI list
IP address •Default Bearer
3G. RRC Connection Reconfiguration Complete Context information
•IP address assigned
3H. Initial Context Setup Response
Default EPS Radio Bearer
3E. MME send an Attach Accept Message. The attach accept is sent in an Initial Context Setup Request Message.
Which instructs the eNB to create the necessary radio and S1 bearers. A default bearer is always established.
3F. The eNB configures its radio resources for the default bearer, and fowards the radio bearer parameters to the UE in an
RRC connection Reconfiguration message. This message also carries the Attach Accept Message from he MME
informing the UE of this IP address.
3G. The UE acknowledges the radio bearer reconfiguration with an RRC Connection Reconfiguration Complete message.
3H. The eNB informs MME of the sucessful setup of the default radio bearer with an Initial Context Setup Response
Message.
Page 61
E-UTRAN
UE MME S-GW P-GW
EPS Radio Bearer S1 MME Bearer Default S11 GTC Tunnel Default S5/S8 GTP-C tunnel
3K. Modify
Default S5/S8 EPS Bearer
3I. Attach 3J. Attach Bearer Request
Complete Complete
3K. Modify Bearer
Response
Default S1-U EPS Access Bearer
Default S1-U EPS Bearer
3I. The UE finishes the process by sending an Attach Complete Message to eNB, indicating the successful completion of the
network attach.
3J. UE begins using NAS security mechanisms (encryption and Integrity checking). eNB forwards this message to MME and
provides information about its end of the default S1-U bearer.
3K. The MME sends the bearer configuration to SGW to finish establishing the S1-U bearer.
3L. SGW acknowledges the successful completion of the bearer with a Modify Bearer Response message. And the UE is
finally ready to being using its IP address to send packets into the network.
Page 62
Network Detach Procedure
Page 63
Network Detach Procedure
Page 64
UE Initiated Detach Procedure
E-UTRAN HSS
UE MME S-GW P-GW
1. Detach Request
2. Delete Bearer Request
3. Delete Bearer Response
3. Dettach Accept
4. Signalling Connection Release
1. UE sends a Detach Request to MME because it’s turned off.

2. The MME instruts the SGW and PGW to delete any bearers for the UE and the PCEF in the PGW
informs CRF that the bearers are being removed.
3. The MME may confirm the detach with Detach Accept message and remove the signalling connection.
Page 65
Selection Functions
Page 66
MME Selection
MME selection Functionality allocates an available MME for serving an UE

GUMMEI
• Selection is based mainly on network topology, determining the
MME that serves the UEs location.
• When the MME/SGSN selects a target MME, the selection
+
Load Status of MME
functions performs a simple load balancing between the possible within a Pool
target MME. When an eNodeB selects an MME, the selection
shall achieve load balancing.
• Each MME has a Weight Factor. It is typically set according to
S1-AP
the capacity of an MME node relative to other MME nodes.
eNodeB
 The MME selection function was designed to be efficient from the UE movement point of view and
have been developed to reduce MME change when serving within certain operation boundaries.
Page 67
SGW and PGW Selection
HSS
MME
Selection criteria for PGW

subscription data:
1. Update Location Request
• List of APNs
• Default APNs
• PDN type of each APN 2. Update Location Answer
• QoS requirements
• IP address
• Services supported
MME PGW S-GW

1 2
PGW selection First SGW selection next
1. MME updates the HSS with the current location of the UE using an Update Location Request message.
2. HSS responds back with an Update Location Answer message, and includes the UE’s subscription information. This
information lists the UE’s registered APN configurations.
Then the MME maps each APN to a PGW and then chooses an appropiate SGW based on UE location and mobility
mechanisms supported (GTP vs PMIP)
Page 68
SGW Selection
MME selection Functionality allocates an available SGW for serving an UE
• Selection is based mainly on network topology.

• When the SGW IP address returned from the DNS server
include Weigh Factors, the MME should use it if load balancing is TA I
required.
• SGW may need to support both protocols for a single UE
connected to different PDNs.
 The MME selection function in the MME is used to ensure that all TA in the TA List belong to the
same SGW service Area.
Page 69
PCRF Selection
• It shall allow that entities contacting the PCRF may be able to provide
different sets of information about the UE and PDN connections. For
example
- The AF has information about UE IP address and PDN but may not
have user identity information
- The PDN GW has information about user identity (UE NAI), the APN
and the UE IP address(es) for a certain PDN connection
Page 70
1.1 Key Concepts
Page 71
Tracking Area Update
Whenever the UE selects a
cell with a different TAI than
its previous serving cell, it has
entered a new Tracking Area,
and informs the network.
If the 2 cells has the same

TAI, then the update is not
required.
Detect a new TAI different

from old TAI If an idle UE needs to be
paged, the page request will
be sent to all cells within the
Tracking Update Procedure UE’s last known Tracking
Area.
Page 72
TA Update Procedure
eNodeB RNC/BSC MME Old MME/ old S4 S-GW PGW PCRF HSS
UE SGSN
1. Tracking Area Update Request

3. Deactivate
Context Request bearers not
2. Context Response
active in UE
Authentication Security
2. Context Acknowledge
Update Bearer Request

3. Update Bearer Response
Update Location Request
Cancel Location
4. Cancel Location Ack
Update Location Ack
Iu Release Command
5. Iu Release Complete
TA Update Accept
6. TA Update Complete
Triggers for TA update

• UE detects it has entered a new TA that is not in the list of TAIs that UE registered with the network.
• The periodic TA update timer has expired.
Page 73
1.1 Key Concepts
Page 74
Basic Handover
If we consider radio access and packet core network level handover, the following
possible handover combinations can be found:
Optimized HO E-UTRAN to/from

HRPD *
Intra EUTRAN Non Optimized HO trusted non 3GPP

Within eNBs to/from GERAN/UTRAN/EUTRAN **
Non-
3GPP
Inter EUTRAN Handover Handover
Toward other nodes for 3GPP
access Non Optimized HO untrusted non 3GPP
to/from GERAN/UTRAN/EUTRAN **
Inter RAT
Different Radio Technologies
* For GTP and PMIP.

** With GTP/PMIP on 3GPP access and PMIP/MIPv4FA/DSMIPv6 on non-3GPP access
*** With GTP/PMIP on 3GPP access and PMIP/DSMIPv6 on non-3GPP access
Page 75
Handover for 3GPP access
Page 76
Intra EUTRAN HO Inter EUTRAN HO Inter RAT HO
1. eNB makes the handover

decision based on UE’s
measurements.
2. The target eNB performs the

admission control dependent
on the QoS information.
3. Both source eNB and target eNB

may need to buffer data so source
eNB establishes uplink and
downlink data forwarding path for
user plane traffic towards target
eNodeB.
4. During the execution phase, the

source eNB forwards any data
received from the downlink path
from SGW towards target eNB.
5. Target eNB informs MME to

switch path and MME then also
informs SGW to switch the user
plane path for the downlink data
traffic and informs source eNB via
an end marker about the end of
data transfer.
Also called X2 handover (no changes in CN)
Page 77
Inter EUTRAN and MME HO
1. The S-MME uses GTP signaling to communicate the handover signaling to the T-MME and vice versa.
2. S-MME detects that the target cell requested for handover belongs to another MME and initiates the GTP FORWARD
RELOCATION REQ message to the T-MME.
3. The T-MME creates the S1 logical connection toward the T-eNB and sends the S1 HANDOVER REQ on it.
4. The T-eNB prepares the requested resources and responds with a HANDOVER REQ ACK to the T-MME.
5. The T-MME sends a GTP FORWARD RELOCATION RESP to the S-MME, to notify the resource reservation at the T-
eNB and DL data packets are forwarded from the S-eNB to T-eNB via the SGW during the handover.
6. Once the T-eNB detects the UE in its area, it notifies the T-MME. And also notifies the completion of the handover to the
S-MME with a GTP FORWARD RELOCATION COMPLETE NOTIFY message.
7. The S-MME proceeds with clearing the S1 logical connection and the associated bearer resources.
Page 78
Inter EUTRAN, MME and SGW HO
1. After receiving the GTP: FORWARD RELOCATION REQ from the S-MME, the T-MME detects the SGW change and initiates the
bearer creation toward the target SGW (T-SGW) using a GTP: CREATE SESSION REQ message.
2. After the creation of the requested bearers, the T-SGW responds back to the MME with a GTP: CREATE SESSION RESPONSE
message.
3. From this point onward, the message flow is very similar to that in the previous section except for the following differences:
• While processing the S1 HANDOVER NOTIFY message from the T-eNB, the T-MME updates the T-eNB endpoint
information to the T-SGW using GTP: MODIFY BEARER REQ.
• After updating the T-eNB information in the bearers (successfully set up during the handover), the T-SGW responds with
a GTP: MODIFY BEARER RESPONSE message to the T-MME.
4. After successful completion of the handover, the S-MME takes care of releasing bearer resources with the S-SGW for this UE by
initiating the GTP: DELETE SESSION procedure.
Page 79
1. Preparation Phase
EUTRAN to UTRAN HO
1. Once the inter-RAT handover is decided at the S-eNB based on the measurement report procedure, it prepares and sends a HANDOVER
REQUIRED message to the S-MME.
2. The S-MME retrieves the target SGSN details from the database based on the information in the message and sends a GTP-C: FORAWRD
RELOCATION REQUEST to the T-SGSN.
3. The T-SGSN detects the change of SGW and creates the bearer resources in the T-SGW by initiating the GTP: CREATE SESSION procedure.
Once the resources are reserved at the T-SGW, it responds to the T-SGSN with a GTP: CREATE SESSION RESPONSE message.
4. The T-SGSN now reserves the resources at the T-RNC by sending a RANAP: RELOCATION REQUEST message to it.
5. The T-RNC reserves the radio resources and responds to the T-SGSN with a RANAP: RELOCATION REQUEST ACK message. The T-SGSN
creates the indirect data forwarding tunnels in the T-SGW for the DL packets transfer from the S-SGW to T-SGW during the handover.
6. After the Indirect Data forwarding tunnel creation, the T-SGSN responds with a GTP: FORWARD RELOCATION RESPONSE message to the S-
MME.
7. The S-MME has to create the indirect data forwarding tunnels as the resources are reserved successfully in the target network to forward the DL
packets to the target network.
Page 80
2. Execution Phase
EUTRAN to UTRAN HO
1. The S-MME sends the HANDOVER COMMAND message to the S-eNB with the target to source transparent container.
2. The S-eNB prepares and sends the MOBILITY FROM EUTRA COMMAND message to prepare the UE for the handover toward the target network.
3. After accessing the target UMTS cell, the UE sends a HO TO UTRAN COMPLETE message to the T-RNC signaling the successful handover.
4. The S-eNB forwards the DL data packets toward the T-SGW via the S-SGW during the handover. This step can happen any time after it receives the S1AP
HANDOVER COMMAND message from the S-MME. This step is executed in case a direct forwarding path is not available with the T-RNC, otherwise it will
forward the DL data packets to the T-RNC directly. Both the options are shown above in Figure 6.
5. Once the T-RNC detects the UE in its area, it notifies the T-SGSN about the completion of the handover by sending a RANAP: RELOCATION COMPLETE
message.
6. The T-eNB reserves the radio resources and responds to the T-MME with a S1AP: HANDOVER REQUEST ACK message.
7. The T-MME creates the indirect data forwarding tunnels in the T-SGW for the DL packets transfer from the S-SGW to the T-SGW during the handover if there is
no direct forwarding path available from source to target.
8. After the Indirect Data forwarding tunnel creation, the T-MME responds with a GTP: FORWARD RELOCATION RESPONSE message to the S-SGSN.
9. The S-SGSN has to create the indirect data forwarding tunnels, as the resources are reserved successfully in the target network to forward the DL packets to the
target network. With this, the preparation phase is complete.
Page 81
1. Preparation Phase
UTRAN to EUTRAN HO
1. The S-MME sends the HANDOVER COMMAND message to the S-eNB with the target to source transparent container.
2. The S-eNB prepares and sends the MOBILITY FROM EUTRA COMMAND message to prepare the UE for the handover toward the target network.
3. After accessing the target UMTS cell, the UE sends a HO TO UTRAN COMPLETE message to the T-RNC signaling the successful handover.
4. The S-eNB forwards the DL data packets toward the T-SGW via the S-SGW during the handover. This step can happen any time after it receives the S1AP
HANDOVER COMMAND message from the S-MME. This step is executed in case a direct forwarding path is not available with the T-RNC, otherwise it will
forward the DL data packets to the T-RNC directly. Both the options are shown above in Figure 6.
5. Once the T-RNC detects the UE in its area, it notifies the T-SGSN about the completion of the handover by sending a RANAP: RELOCATION COMPLETE
message.
6. The T-eNB reserves the radio resources and responds to the T-MME with a S1AP: HANDOVER REQUEST ACK message.
7. The T-MME creates the indirect data forwarding tunnels in the T-SGW for the DL packets transfer from the S-SGW to the T-SGW during the handover if there is
no direct forwarding path available from source to target.
8. After the Indirect Data forwarding tunnel creation, the T-MME responds with a GTP: FORWARD RELOCATION RESPONSE message to the S-SGSN.
9. The S-SGSN has to create the indirect data forwarding tunnels, as the resources are reserved successfully in the target network to forward the DL packets to the
target network. With this, the preparation phase is complete.
Page 82
2. Execution Phase
EUTRAN to UTRAN HO
1. The S-SGSN sends the RANAP RELOCATION COMMAND message to the S-RNC with the target to source transparent container (it has the
reserved resource information at the target).
2. The S-RNC prepares and sends the HO FROM UTRAN COMMAND message to prepare the UE for the handover toward the target network.
3. After accessing the T-eNB, the UE sends an RRC CONNECTION RECONFIGURATION COMPLETE message to the T-eNB signaling the
successful handover.
4. The S-RNC forwards the DL data packets toward the T-SGW via the S-SGW during the handover. This step can happen any time after it receives
the RANAP RELOCATION COMMAND message from the S-SGSN. This step is executed in case a direct forwarding path is not available with the
T-eNB, otherwise it will forward the DL data packets to the T-eNB directly. Both the options are shown above in Figure 8.
5. Once the T-eNB detects the UE in its area, it notifies the T-MME about the completion of the handover by sending an S1AP: HANDOVER NOTIFY
message.
6. The T-MME notifies the completion of handover to the S-SGSN by sending a GTP: FORWARD RELOCATION COMPLETE NOTIFICATION ACK
message. The S-SGSN acknowledges this message and proceeds with the release of the resources associated with this UE at the S-SGW and S-
RNC.
7. The T-MME modifies the E-RAB resources at the T-SGW by initiating the GTP MODIFY BEARER procedure.
8. The T-SGW notifies the bearer parameters with the PGW by initiating the GTP MODIFY BEARER procedure.
Page 83
Non 3GPP Access Handover
Page 84
Intra EUTRAN HO Inter EUTRAN HO
HO from a Trusted
Non 3GPP Access
to EUTRAN
Page 85
Roaming
Trusted Scenarios
Non- HSS/
3GPP MME/ Serving PDN GW AAA vPCRF hPCRF
UE 3GPP IP AAA
Access SGSN GW Proxy
Access
1. PMIPv6/
GTP tunnel
2. UE discovers
Trusted Non-3GPP
Access and initiates
HO
3. Access 3. Authentication and Authorization (PDN GW)

Authentication
4. L3 Attach Trigger
Handover
5. Gateway Control Session Establishment Procedure from 3GPP
6. Proxy Binding Update
to trusted
7. PCEF-Initiated IP-CAN Session
Modification Procedure
non-3GPP
8. Proxy Binding Ack (IP Addr)
9. L3 Attach Completion
10. PMIPv6 tunnel
11. UE-initiated Connectivity to Additional PDN
12. 3GPP EPS Bearer Release 12. 3GPP EPS Bearer Release
Page 86
Roaming
Trusted Scenarios
Non- HSS/
3GPP MME/ Serving PDN GW AAA vPCRF hPCRF
UE 3GPP IP AAA
Access SGSN GW Proxy
Access
1. PMIPv6/
GTP tunnel
2. UE discovers
Trusted Non-3GPP
Access and initiates
HO
3. Access 3. Authentication and Authorization (PDN GW)

Authentication
4. L3 Attach Trigger
Handover
5. Gateway Control Session Establishment Procedure from 3GPP
6. Proxy Binding Update
to trusted
7. PCEF-Initiated IP-CAN Session
Modification Procedure
non-3GPP
8. Proxy Binding Ack (IP Addr)
9. L3 Attach Completion
10. PMIPv6 tunnel
11. UE-initiated Connectivity to Additional PDN
12. 3GPP EPS Bearer Release 12. 3GPP EPS Bearer Release
Page 87
Handover from
3GPP to
untrusted non-
3GPP
Page 88
Contents
2 Procedures in EPC
4 Voice Service
5 SMS Service
Page 89
1.1 QoS Parameters
1.2 QoS Enforcement
1.3 Bearer and QoS Parameters
1.4 Interoperability with GERAN/UTRAN
Page 90
QoS parameters in EPS
Quality of Service
Allocation and
Guaranted Bit Rate QoS Class Identifier
Retention Priority
GBR ARP QCI
• Nine Scalar value used as a

Non-GBR GBR • Is the priority of bearer reference to control bearer
establishment/modification level packet forwarding
request. treatment.
• There are all • A bearer is referred to as a • The service flows with • The service flows with
the bearers GBR bearer if dedicated
different ARP should use different QCI should use
that share the network resources related
different bearers. different bearers.
network to a GBR value that is
resources associated with the EPS
bearer are permanently
allocated (e.g. by an
UE-AMBR admission control function
in the eNodeB) at bearer
establishment/modification
APN-AMBR
Page 91
QoS Classes in EPS
Source: TS 23.203
Packet Delay
Resource Packet Loss
QCI Priority Budget Example Services
Type Rate (PLR)
(PDB)
1 2 100 ms 10-2 Conversational Voice
2 4 150 ms 10-3 Conversational Video (Live Streaming)

GBR
3 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 Signaling
6 6 300 ms 10-6 Video (Buffered Streaming) TCP-based
7 7 100 ms 10-3 Voice, Video (Live Streaming)

Non-GBR Interactive Gaming
8 8 300 ms 10-6 Video (Buffered Streaming)

TCP-based (e.g., www, e-mail, chat, ftp, p2p,
9 9 file sharing, progressive video, etc.)
Page 92
1.1 QoS Parameters
1.2 QoS Enforcement
Page 93
QoS Enforcement
•Negotiates QoS requirement with application
•Authorizes QoS request against user subscription data
•Receives network events
•Decides policy rules to be applied (filters, QoS
parameters QCI, MBR, GBR, ARP)
GERAN SGSN
UTRAN HSS/HLR PCRF •Application

•NAS signaling with UE (e.g., QoS S3 •Signalling (PCRF
request) S12 S6a and terminal)
•Authentication •Mobility anchor
•Bearer control S4 •QoS mapping (S1
•Handover coordination with SGW, bearer/backhaul QoS
other MME or SGSNs (IRAT) AS
•QoS mapping (Gn/Gp interworking) Gx Rx
•SGW/PGW selection
MME
S1-MME S11
S5
SGi Internet / intranet /
Operators in-house
E-UTRAN S1-U & 3rd Party AS
Terminal S-GW PDN-GW
(LTE/UMTS/GSM
•Radio resources allocation

•Application (incl. signaling) •Scheduling, •IP address allocation
•UL filtering of traffic flow to bearer •Admission Control •EPS bearer control
•APN-AMBR policing •UL filtering, •DL filtering of traffic flow to bearer
•Mobility support •interference control (ICIC) •Traffic shaping/policing (e.g., APN-AMBR)
•Idle mode reselection •Handover •Charging
•Handover measurements •Idle mode cell reselection priorities •DPI
•QoS mapping (S1 Bearer/backhaul QoS) •QoS mapping to SGi Qos support (e.g., DiffServ
Page 94
End to End QoS
 A radio bearer transports the packets of an EPS bearer between a UE and a eNB. There is a one-to-one
mapping between an EPS bearer and a radio bearer.
 An S1 bearer transports the packets of an EPS bearer between an eNB and a SGW.
 An eNB stores a one-to-one mapping between a radio bearer and an S1 to create the binding between a
radio bearer and an S1 bearer in both the uplink and downlink,
AF AF
Client PCRF Client
Application Signalling
Application Application
End to end Service
Bearer Policy
QoS enabled
handling EPS bearer Enforcement Ext. QoS mechanism IP stack
(PCEF)
Radio Bearer Radio Bearer
Backhaul Backbone
control RB control Transport
S1 Bearer S5/S8 Bearer Transport
Serving PDN Application
Network Network
UE eNB GW GW Server
Radio S1 S5 SGi
EPS network External network to application

Bearer level QoS mechanism Other QoS mechanism
(e.g. DiffServ on Ethernet, MPLS...)
Page 95
1.1 QoS Parameters
1.2 QoS Enforcement
Page 96
Dedicated Bearer Activation
The bearers can be dynamically established, modified
or removed depending on the needs of applications
being used by the UE.
In E-UTRAN, the dedicated bearer procedures are

always initiated by the network. The UE may send a
request for certain resources (QCI, bit rates, packet filters)
to the network and this request can result in bearer
operations being initiated by the network.
In GERAN/UTRAN, the PDP context procedures are

initiated by the network or by the UE.
Page 97
Dedicated Bearer Activation - Network
Initiated (DPI) PCRF
3
MME
E-UTRAN
2 4 AF
S-GW
1
P-GW
Default Bearer (or earlier established dedicated bearer)
UE 5
Network Initiated Dedicated Bearer
1. The UE invoke a new service (e.g. Skype).

2. The P-GW DPI detects that a new service is invoked against external server. The P-GW triggers the
PCRF
3. PCRF decides services parameters and authorizes the QoS requirement against subscription.
4. PCRF sends QoS parameters (QCI, MBR, GBR, ARP, UL and DL traffic flow filters) to PCEF in PGW
5. The PCEF decides to establish a new dedicated bearer to the UE and applies the QoS parameters.
All nodes in the chain applies the forwarding policy given by the QCI
Page 98
Dedicated Bearer Activation - Network
Initiated (Application Server)
PCRF
3
MME 2
E-UTRAN
4
S-GW
P-GW
1
Default Bearer (or earlier established dedicated bearer)
UE
5
1. The UE invoke a new service (e.g., starts MMtel video conferencing during IMS voice call).
2. The application Server signals new QoS requirements to PCRF (through Rx)
3. PCRF coordinates and authorizes the QoS requirement against subscription.
5. The PCEF decides to establish a new dedicated bearer to the UE and applies the QoS parameters
Page 99
Dedicated Bearer Activation - UE resource
Request, Modification and Release
PCRF
3
MME
E-UTRAN
2 4 AF
S-GW
Default Bearer P-GW

1
UE initiated Request bearer resource modification
UE
5
1. The UE sends a request for bearer resource modification using signaling.

2. The P-GW sends the requested QoS parameters to the PCRF (or applies local policy)
3. PCRF decides services parameters and authorizes the QoS requirement against subscription.
5. The PCEF decides to establish a new dedicated bearer to the UE and applies the QoS parameters
Page 100
Contents
2 Procedures in EPC
4 Voice Service
5 SMS Service
Page 101
4 Voice Solution in SAE
1.1 CSFB-Circuit Switching Fallback
1.2 VoLGA
1.3 SRVCC- Single Radio Voice Call Continuity

1.4 Voice over IMS
1.5 Conclusion
Page 102
Options for Voice in LTE
Non SIP UE CS Fallback 0
DP2 VoLGA 1
How to provide
voice service?
DP1
SRVCC 2
Dual Mode Terminals
IMS 3
New SIP Infrastructure
Page 103
CS Fall Back Solution
GSM/UMTS LTE
coverage hotspot
In the overlaid Core network requirement:

coverage of LTE  Reuse traditional GSM / UMTS
and GSM/UMTS… Core (Sw upgrade);
 No additional equipment;
Principle Benefit
 GSM/UMTS has the highest priority to provide
 Voice service can be deployed
voice service for multi-mode UE;
quickly and minimize new
 If CSFB voice service initiated, two options for
investment.
the ongoing LTE data service:
 Service handed over to GSM/UMTS network  Guarantee users’ data service
(DTM supported by GU network); quality when handover occurs.
 Service suspended in LTE network until voice
call is over (DTM not supported);
Page 104
Voice Call in CSFB
Initiate voice call

MSC/VLR
NodeB RNC
Inter-system change
HSS/HLR
2G/3G SGs
LTE
SGsAP SGsAP
MME SCTP SCTP
IP IP
Paging L2 L2
L1 L1
eNodeB SAE-GW MME SGs MSC Server
SGs AP: SGs Application Part
 CSFB needs RAN/LTE cover simultaneously

 Possible to handover the ongoing data session to 2G/3G PS if the target cell support PS/CS
simultaneous sessions
 CSFB and IMS-based service shall be able to co-exist in the same network (Roaming in)
Page 105
Flow Chart of MO in CSFB
Voice call established

MSC/VLR
Fallback to GSM/UMTS
BTS/NodeB BSC/RNC
HSS/HLR
2G/3G SGs
LTE Service Request

Signaling
MME
Service Bearer
eNodeB
SAE-GW
MO CSFB procedure:
1. Voice service request is activated from UE;
2. MME indicates UE fall back to G/U network for voice service via eNodeB, UE sends
service request to GERAN/UTRAN; in the mean time, MME informs G/U CS Core to
prepare resource;
3. When resource in G/U network is allocated, UE falls back to GERAN/UTRAN for voice
service
Page 106
Flow Chart of MT CSFB
Voice call established
MSC/VLR
Fallback to GSM/UMTS
BTS/NodeB BSC/RNC
HSS/HLR
2G/3G SGs
LTE Paging
CS paging Service Request
MME
Signaling
Service Bearer
eNodeB
SAE-GW
MT CSFB procedure:
1. GSM/UMTS MSC initiates CS paging to the called party (LTE UE), voice service is
requested by LTE UE;
2. MME indicates UE fall back to GERAN/UTRAN for voice service via eNodeB, UE sends
service request to GERAN/UTRAN; in the mean time, MME informs GSM/UMTS CS
Core to prepare resource;
3. When resource in GSM/UMTS network is allocated, UE falls back to GERAN/UTRAN
for voice service;
Page 107
CSFB- Pros and Cons
Advantages
 Full re-use of Stable and Proven CS Core

Mechanisms such as Roaming,
Iu-ps Interconnection and Handovers etc.
UTRAN
SGSN
 No major impact on IT OSS/BSS,
Gs Provisioning, Billing Systems
Gb
Iu-cs
MSC  Only Minor Upgrade on MSC, SGSN and
GERAN CSFB Enabled MME required.
CSFB UE S3
SGs  Co-existence with IMS with minor
requirement on UE for domain selection
functions (R9)
S1-MME
E-UTRAN MME
CSFB Enabled CSFB Enabled
Disadvantages
 Possible Poor Service Experience with delay between  Superior Spectral efficiency of
answering the call and the actual speech path setup. VoPS is not utilized to lower costs
 Data Applications running over the LTE may get  Only voice centric services as
disrupted during CS Call, as no simultaneous CS and compared to IMS Multimedia
LTE access would be supported by UE.
Page 108
Contents
1.2 VoLGA

1.4 Voice over IMS
1.5 Conclusion
Page 109
VoLGA Solution
GSM/UMTS LTE
coverage hotspot
In the overlaid Core network requirement:

coverage of LTE  Doesn’t require any update
and GSM/UMTS… on existing network.
 VoLGA Access Network
Controller
Principle Benefit
• To connect the already existing MSCs to the • No need to deploy the IMS, but
LTE network via a gateway. VANC must be introduced.
• Utilize the Sv interface [TS23.216], realize the • No impact to legacy MSC
function of voice handover to 2G/3G CS core. • Flexible to deliver CS services
• Voice is carried as VoIP over the radio links.
Page 110
VoLGA Solution
Iu-CS/A SGSN
MSC/VLR
Voice
Iu-PS/Gb Network
GERAN/UTRAN S3 Iu-CS/A
MME VANC PCRF

Rx
Sv
SGi
S1-MME S11 Gx
IP Network
S1-U
E-UTRUAN
S5 SGi
S-GW PDN-GW
 Requires dual mode UEs with have both a GSM/UMTS and LTE radio interface.
 New VANC network element.
 For SAE, VANC looks like any other IP based external node. And for CS network it looks like a
BSC/RNC.
Page 111
VoLGA Pros and Cons
VoLGA – Voice over LTE via Generic Access
Advantages
Iu-ps
UTRAN  Full re-use of Stable and Proven CS
SGSN Core Mechanisms.
Gs
Gb  No major impact on IT OSS/BSS,
Iu-cs MSC
Provisioning, Billing Systems
GERAN
 Less impact on EPC.
LTE GAN UE A/Iu
Sv’  LTE high data rates are always
available, even during voice calls.
E-UTRAN EPC VANC

VoLGA Access Network
Controller
Disadvantages
 Only Voice Services in CS Core and

 Not a 3GPP standard. (like CSFB and MMTel). Opposed requires continued investment in CS Core
in 3GPP by AT&T, Vodafone, Verizon, DoCoMO, KDDI etc.
 Provides VoLTE but has limitations on
 VANC investment is not future proof, and costly impact global roaming and interoperability.
on UE for IMS evolution. GANC Node CAPEX issue.
 Limited selection of handsets.
Page 112
1.2 VoLGA

1.4 Voice over IMS
1.5 Conclusion
Page 113
SRVCC Solution
GSM/UMTS LTE
coverage hotspot
When UE moving
from LTE coverage
to GSM/UMTS with
voice service… Core network requirement:
 IMS deployed
 Enhanced MSC deployed;
Principle Benefit
 IMS supports voice and data service of LTE  LTE network can support both voice
subscribers; and data services with IMS solution
 PS handover for LTE VoIP to UMTS VoIP;
 Future oriented convergent solution
 SRVCC for LTE VoIP to GSM/UMTS CS calls if G/U
network doesn’t support VoIP
 SRVCC happens when voice handover from LTE to
RAN after the voice service has begun.
Page 114
Voice Call in SRVCC Bearer before handover
Bearer after handover
MSC SIP signaling
MAP E
Iu-cs
EMSC 3GPP
NodeB RNC IMS
SGSN
Handover
Sv
VCC AS
MME
SRVCC UE eNodeB
SAE-GW
 SRVCC needs a VCC AS and the MSC should be upgraded to EMSC

 Interface Sv between MSC Server and MME is used to support the processing SRVCC. Sv is
based on GTPv2, which is to transfer handover signaling.
Page 115
Flow Chart of SRVCC
Bearer before handover
Bearer after handover
Target MSC SRVCC Signaling
BSC/RNC SIP signaling
MAP E
Iu-cs
Inter-RAT Handover
3GPP
BTS/NodeB IMS
EMSC with SRVCC
SGSN
Sv
VCC AS *
MME
SRVCC UE eNodeB
SAE-GW * VCC AS: Voice Call Continuity Application Server
Voice handover procedure:

1. Voice service is beared by LTE. E-UTRAN indicates MME for SRVCC.
2. MME transfers the data request signal to SGSN and voice request signal to EMSC.
3. Data and voice service requests are sent to BSC/RNC and data/voice resources are
prepared for taking over UE’s service. BSC/RNC sends the response signal from
EMSC/SGSN to MME/eNodeB;
4. UE handover from LTE coverage to GSM/UMTS coverage, voice service continuity
guaranteed. After handover succeeded, the occupied resource in LTE will be released.
Page 116
SRVCC Pros and Cons
MSC
Advantages
MAP E
Iu-cs
EMSC 3GPP  Better service capability
NodeB RNC IMS
SGSN  FMC support in the future
Handover
Sv
 Dominant solution in 3GPP
VCC AS
MME  VCC is an existing method, which
has been improved for Single Radio
SRVCC UE eNodeB
SAE-GW
 Facilitate evolution to IMS in
future.
Disadvantages
 Only the handover from SAE/LTE to legacy is
 IMS network need to be deployed beforehand supported.
 MSC should be upgraded to support SRVCC handover.  It requires dual mode terminals with SRVCC
capability.
Page 117
1.2 VoLGA

1.4 Voice over IMS
1.5 Conclusion
Page 118
Voice with IMS
Principle
 Deployment of IMS core

 The IMS concept is based around the
Session Initiation Protocol (SIP).
 Data retains LTE’s bandwith
during voice calls.
 Traditional services are implemented
over the packet network
Benefit
 IMS provides VoIP using a fully

packet switched network.
 Only method that is all-IP.
• Rich Communication Suite for
enhanced service experience
Note: SRVCC facilitates the session transfer of voice component from LTE to the CS domain.
Page 119
S-CSCF: Serving-Call Session Control Function
IMS Architecture P-CSCF：Proxy-Call Session Control Function

I-CSCF：Interrogating-Call Session Control Function
CSCF (Call Session Control Function)

 The core element with the same position as softswitch and
MSC Application
 S-CSCF performs routing and triggers services
 P-CSCF validates and forwards requests
 I-CSCF interworks with other IMS networks ISC (SIP)
 In a small network, S-CSCF, P-CSCF, and I-CSCF are PSTN
Cx/Dx(Diameter)
commonly integrated into one physical element. Mg (SIP)
HSS (Home Subscriber Server)
 Stores all subscriber and service-related data HSS P/I/S-CSCF MGCF PLMN
 The same as the HLR in the existing mobile network Gq(Diameter) Mr (SIP)
MRS (Media Resource Server)
 Plays announcements and collects digits H.323
MGW
PDF Core MRS
PDF (Policy Decision Function)
 Manages QoS policies
MGCF (Media Gateway Control Function)

 Provides conversion between SIP and SUP signaling GGSN AC
 Interworks with the existing signaling network
BAS PDSN
MGW (Media Gateway) GSM/WCDMA WiMAX/
WiFi
 Provides the conversion between the IP bearer and the xDSL/LAN CDMA
TDM bearer
 Interworks with the existing bearer network
Page 120
iFC contains the address of AS to which the subscriber has subscribed services.
IMS Call Flow

HSS B
Caller Part Calle Part
AS A
Fisrt entry AS B
point of a call
HSS A signalling
S-CSCF A
I-CSCF B S-CSCF B
I-CSCF A
DNS/ENUM P-CSCF B
P-CSCF A It is the only portal for

all subscribers to
access IMS dpmain
IP Media
Procedure:
1. The caller AS forwards the call to SCSCF_A and it analyzes the Callee ID (IP or phone number) and request the DNS for the IP address of the
ICSCF_B.
2. ICSCF_B then forwards the message to the HSS_B to authenticate the callee. If the callee is a valid subscriber and has already successfully
registered, the HSS returns the address of the SCSCF_B to the ICSCF_B. Then, the ICSCF_B forwards the call to the SCSCF_B.
3. UE sends a call request message to the P-CSCF_A and it forwards the message to the S-CSCF_A. S-CSCF_A triggers the call to the specified
AS and it processes the call based on the service subscription and registration information of caller.
4. When the call reaches SCSCF_B, it triggers the service to the AS_B according to the iFC subscribed by the callee.
5. Then the AS processes the call and the SCSCF_B forwards the call to the callee via the P-CSCF at the callee side.
Page 121
IMS User Initial Call to PSTN/PLMN User
IMS Caller Part PSTN Callee Part
HSS A
S-CSCF A BGCF
MGCF PSTN
IAM
I-CSCF A
Media Control
ENUM
P-CSCF A
UMG
Procedure:
1. When the call is sent to S-CSCF A, it query the DNS/ENUM (because the caller number doesn’t belong
to IMS domain).
2. S-CSCF A forwards the call to the BGCF and it forwards the call to the corresponding MGCF.
3. The MGCF forwards the call to the PSTN/PLMN in traditional signalling mode (that is SS7 or BICC).
Page 122
PSTN/PLMN User Initial Call to IMS User
IMS Caller Part PSTN Callee Part
HSS A I-CSCF A
S-CSCF A
MGCF PSTN/PLMN
IAM
Media Control
P-CSCF A
UMG
Procedure:
1. The SS7 signaling message is transmitted from the PSTN to the MGCF and it converts
the SS/ signaling message to SIP message.
2. Then, the MGCF forwards this message to the ICSCF.
3. The subsequent process is the same as the process at the callee side in Intra-IMS call.
Page 123
IMS Pros and Cons
Advantages
 Preserves LTE’s bandwith during voice

calls while minimizing call setup delay.
 Assures global interoperability and

roaming
 Provides the largest possible ecosystem

which affects such matters as handset
supply and multivendor interworking
 Provides an all-IP network for operational

savings and HD voice
 Enables full blending of voice with

advanced services beyond GSMA RCS.
Disadvantages  Convergence via ICS
 Investment in new equipments.

 Complexity of the system.
 Only the packet domain to circuit domain transition.
 Limited LTE coverage if only hot spots at initial phase.
Page 124
1.2 VoLGA

1.4 Voice over IMS
1.5 Conclusion
Page 125
Comparison of Three Voice solutions
CSFB SRVCC VoLGA
Complete standardization at the end of Complete standardization at Defined in VolGA, Stage 2 is
Technology 2008 the end of 2008 completed 2009Q1.
Maturity
Without IMS deployment. With IMS deployment. Without IMS deployment.

LTE network doesn’t provide VoIP LTE network provides VoIP LTE network provides VoIP
service. service. service with additional VANC
Application
Note: Take advantage of legacy equipment.
Scenario
networks voice ability. Notes: Take advantage of
legacy networks voice ability.
Low High Medium

Legacy network needs a little IMS should be deployed. Add VANC equipment.
Solution modification. Legacy network and LTE Convert the VoIP to CS.
Complexity LTE network identify the voice service network are both connect to
and fall back to CS domain. IMS.
Connection time is 2 or 3 seconds Handover interrupt latency is Less impact on performance.

Performance longer than voice call of legacy network higher
such as GSM/UMTS
Low High Medium
Terminal UMTS/LTE overlap Dual-mode terminal should Dual-mode terminal should
Requirement support VoIP and related IMS support VoIP and related
signaling. VANC signaling.
Page 126
Contents
2 Procedures in EPC
4 Voice Service
5 SMS Service
Page 127
SMS over LTE Architecture
MMTel/SCC AS Messaging AS
Solution
• There are two IM

options: SMS over SMSC
SGs (using CSFB) ISC ISC
CSCF IP-SM-GW
or SMS over IP
Sh
solution (using IMS) Sh/J
E/Gd SMS-IWMSC
Cx
• IP-SM-GW Rx
PCRF HSS/HLR
C/D
functionality will be SGi
mainly responsible
S7
for IM/SMS S6a SGs
S/P-GW
interworking
• Fully compliant with

S4
3GPP (TS23.204) S11 MME SGSN MGW
and OMA standards S3
S1-U
• Standard interfaces
S1-MME
with other
components or E-UTRAN PC Client with UTRAN GERAN
datacard
networks CS Handset
Page 128
5 SMS over LTE
1.1 SMS o SGS
1.2 SMS o IMS
Page 129
SMSoSGs: Independent SMS-IWF to reduce impact
on CN
SMS-SC
SMS-GMSC/IWMSC
Newly introduced SMS-
IWF, to handle all
SMSoSGs for LTE users
Benefits of independent
SMS-IW/F:
Existing MSC  Prevent impact on
existing MSCs (Upgrade
D SGs MME
D to support SMS over SGs,
Existing MSCs SMS-IWF VLR capacity impacts)
do not need to
HLR  SMS-IWF is basically a
be upgraded to
support A/Iu
simplified MSC-S which
SMSoSGs doesn’t need to have
BSC/RNC complete voice call
related features – its
capacity can be
dimensioned mainly for
Registration & SMS
support
eNodeB BTS/NodeB
Page 130
5 SMS over LTE
1.1 SMS o SGS
1.2 SMS o IMS
Page 131
Call Flow – Registration
MSC SMS-
IWMSC
GERAN
SMSC
SGSN
UTRAN E/Gd
C/D
HSS/HL IP-SM-GW
MAP_ATM
R
UE Sh/J
4
S3 S4
SIP REGISTER
MME 2
Cx 3
ISC
1 PCRF
S1-MME
CSCF
S-GW P-GW S7 Rx
E-UTRAN
S1-U S11 SGi
• 1) IMS user registration. SIP REGISTER

• 2) 3rd party registration sent to IP-SM-GW
• 3) IP-SM-GW subscribes to Registration Info package
• 4) IP-SM-GW registers the user’s MSISDN in the HLR using
MAP_ANY_TIME_MODIFICATION
Page 132
End to End Call Flow – Transport Level
Interworking SMS Originating Procedure
MSC SMS-IWMSC
GERAN 4.MO-FSM(MAP)
SMSC
3.MO-FSM(MAP)
SGSN
UTRAN E/Gd
C/D
Called party
HSS/HLR IP-SM-GW IM
UE Sh/J
S3 S4
MME
Cx 2. Message (SIP)
ISC
S1-MME
CSCF
1. Message (SIP)
CSCF
S-GW P-GW S7 Rx
E-UTRAN
S1-U S11 SGi
Page 133
End to End Call Flow – Transport Level
Interworking SMS Terminating Procedure
MSC SMSC
1. MT_SMS
GERAN
4. SRI_SM_Rsp
SGSN
2 . SRI_SM E/Gd
UTRAN C/D 5a . MT_FSM
HSS/HLR IP-SM-GW
UE Sh/J
S3 S4
3 . SRI_SM
MME
Cx
ISC
S1-MME
CSCF
6a.Message (SIP)
CSCF
S-GW P-GW S7 Rx
E-UTRAN
S1-U S11 SGi
Page 134
Contents
2 Procedures in EPC
4 Voice Service
5 SMS Service
Page 135
1.1 Network Management Functions
1.2 Key Mobility Functions
Page 136
Network Management Functions
• Load balancing MME-MME

• Load re-balancing between MMEs
• MME control overload
Load Balancing Between MMEs
UE eNB MME1 MME2
1. S1 Setup Request
1. S1 Setup Request
2. S1 Setup Response（Weight Factor）
2. S1 Setup Response（Weight Factor）
3. eNB stores each

MME’s Weight Factor
in the MME pool
4. Attach Request
5. eNB selectes MME

based on the Weight
Factor
6. Attach Request
Each MME has a Weight Factor. The Weight Factor is typically set according to the
capacity of an MME node relative to other MME nodes. The Weight Factor is sent from
the MME to the eNodeB via S1-AP messages. The eNB selects the MME according to the
MME’s Weight factor.
Page 138
Load Re-balancing between MMEs
UE eNB MME1 MME2
1. S1 Release Command
2. RRC Release
3. S1 Release Complete
4. TAU Request
 The MME initiates the S1 Release procedure with release cause "load balancing TAU
required"
 The S1 and RRC connections are released and the UE initiates a TAU and indicates to
the eNB that the RRC establishment is for load balancing reasons
 The eNB selects other MME according to this indication
Page 139
MME control of overload
eNB MME1
1. Overload Start
2. eNB stops the service for

this MME, except for
Emergency Service
3. Overload Stop
4. eNB recoveries the

server for this MME.
 When the MME overloads, MME can send Overload Start message to the selected eNB(s).
The MME can request the eNodeB to reject RRC connection requests that are for non-
emergency services
When the MME has recovered and wishes to increase its load, the MME sends OVERLOAD
STOP messages to the eNodeB(s). The eNB recoveries to send message to this MME
Page 140
4 Miscellaneous Features
Page 141
1. Data forwarding
Source MME Target MME
Source eNB Target eNB Source SGW Target SGW
or SGSN or SGSN
1. Forward Relocation Request
2. Create Bearer Request

3. Create Bearer Response
4. Forward Relocation Response

5. Create Bearer Request
6. Create Bearer Response
7. Handover Command
8. Only for Direct Data

Forwarding
8. Only for Indirect Data Forwarding
Two data forwarding ways

• Direct forwarding, i.e. data forwarding can take place either directly from the source
eNB to the target eNB
• Indirect forwarding, i.e. data forwarding takes place indirectly from the source eNB
to the target eNB via the source and target Serving GWs (or if the Serving GW is
not relocated, only the single Serving GW)
Page 142
1.3 Others
Page 143
Earthquake and Tsunami Warning
System (ETWS)
A warning is received by the Cell Broadcast

Centre (CBC) from, say, a government agency
monitoring seismic activity and predicting
earthquakes.
Since all terminals in the network must be reachable

for this warning, the MMEs must convey the warning
to all terminals that happen to be in idle mode, and
whose location is only known with the accuracy of a
Tracking Area which may or may not contain lots of
base stations and radio cells.
Page 144
Access Network Discovery and
Selection Function (ANDSF)
 The ANDSF shall be able to provide the following information:
• Inter-system mobility policy
• Access network discovery information

3GPP IP Access or S14
 ANDSF Discovery : DHCP/DNS
Trusted/Untrusted ANDSF
UE
 Either the UE can request the information or the ANDSF can Non-3GPP IP
initiate the data transfer to the UE. Access
• S14 is a reference point is between UE and ANDSF for direct queries via pull.
• It enables dynamic provision of information to the UE for access NW discovery and selection
procedures related to non-3GPP and 3GPP accesses.
• Push and/or combination of Pull-Push may be supported as well.
• S14 is based on Open Mobile Alliance (OMA) Device Management (DM).
Page 145
Idle mode Signaling Reduction (ISR)
It is a feature that allows the UE to move between LTE and 2G/3G without performing
Tracking Area (TA) or Routing Area (RA) Update.
If the UE first registers on GERAN/UTRAN and then SGSN and the MME have a control connection with the SGW
moves into an LTE cell, the UE will initiate a TA update and the MME and SGSN are both registered in HSS.
procedure. In the TA update procedure, the SGSN, MME The UE stores P-TMSI,RA, GUTI and TA(s) and session
and Serving GW will communicate their capabilities to management (bearer) contexts that are common. SGSN and
support ISR, and MME will indicate to the UE that ISR is MME store each other’s address when ISR is activated.
activated in the TAU accept message.
Page 146
ISR - Paging
1. Downlink data arrives from PGW.

2. SGW send a downlink data notification for both MME and SGSN.
3. The MME will then initiate paging in the TA, where the UE is registered, and the SGSN will initiate paging in the RA,
where the UE is registered.
4. UE receives the paging message, it will perform a service request procedure on the RAT it is currently camping on.
5. When the Serving GW receives this request to establish the downlink data connection, it will also inform the SGSN or
MME to stop paging on the other RAT.
Page 147
Page 148
Glossary
• MME Pool Area

An area within which a UE may be served without need to change the serving MME. An MME
Pool Area is served by one or more MMEs ("pool of MMEs") in parallel. MME Pool Areas are a
collection of complete Tracking Areas
• Serving GW Service Area

An area within which a UE may be served without need to change the Serving GW. A Serving
GW Service Area is served by one or more Serving GWs in parallel. Serving GW Service Areas
are a collection of complete Tracking Areas.
• PDN Connection
The association between a UE represented by one IPv4 address and/or one IPv6 prefix/address,
and a PDN represented by an APN.
• Default Bearer
The EPS bearer which is first established for a new PDN connection and remains established
throughout the lifetime of the PDN connection
• Default APN
A Default APN is defined as the APN which is marked as default in the subscription data and
used during the Attach procedure for PDN connection.
Page 149
Interfaces in Detail -1
S1: Used for EUTRAN access
S1-U: The S1-U interface provides a per bearer user plane tunneling between the Evolved UTRAN and
Serving GW. It contains support for path switching during handover between eNodeBs. S1-U is
based on the GTP-U protocol that is also used for Iu user plane in the Rel-7 architecture.
S1-MME: The S1-MME interface provides the control plane protocol between the Evolved UTRAN and
MME.
S2: Used for non-3GPP access
S2a: Trusted non-3GPP access
S2b: Un-trusted non-3GPPaccess
S2c: used for DSMIPv6 bootstrapping and DSMIPv6 de-registration via 3GPP access
S3: Interface between SGSN and MME. The S3 interface enables user and bearer information exchange
for inter 3GPP access network mobility in idle and/or active state. It is based on the GTP
protocol and the Gn interface as defined between SGSNs.
S4: The S4 interface provides the user plane with related control and mobility support between
GPRS Core and the 3GPP Anchor function of Serving GW and is based on the GTP protocol
and the Gn reference point as defined between SGSN and GGSN.
S5: The S5 interface provides user plane tunneling and tunnel management between Serving
GW and PDN GW local. It is used for Serving GW relocation due to UE mobility, and if the
Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.
There are two variants of the S5 interface, one based on the GTP protocol and one IETF variant
based on Proxy Mobile IPv6 (PMIP).
S6: Interface between HSS and AAA
Page 150
S7: The S7 interface provides transfer of (QoS) policy and charging rules from PCRF to Policy
and Charging Enforcement Function (PCEF) in the PDN GW. The interface is based on the Gx
interface.
S8: SGW and PDNGW remote
S8a: The S8a interface is the roaming interface in case of roaming with home routed traffic (see
section 5.1.5.5). It provides user plane with related control between the Serving GW in the
VPLMN and the PDN GW in the HPLMN. It is based on the GTP protocol and the Gp interface as
defined between SGSN and GGSN. S8a is a variant of S5 for the roaming (inter-PLMN) case.
There is also an IETF variant of called S8b that is based on Proxy Mobile IPv6 (PMIP).
S9: Interface between HPCRF and VPCRF which supports Local Breakout.
S10: The S10 interface between MMEs provides MME relocation and MME to MME information transfer.
S11: The S11 interface is the interface between MME and Serving GW.
S12: Direct Tunnel
SGi: it is the interface between the PDN GW and the packet data network.
Packet data network may be an operator external public or private packet data network or an intra
operator packet data network, e.g. for provision of IMS services. This interface corresponds to Gi
and Wi interfaces and support any 3GPP or non-3GPP access.
Rx+: The Rx interface is the interface between the AF and the PCRF. It is unclear at this point if
there will be any significant modifications to current Rx interface to motivate calling it Rx+.
Page 151
To support non-3GPP accesses the EPS also included the following interfaces:
S2a: The S2a interface provides the user plane with related control and mobility support between
trusted non 3GPP IP access and the PDN Gateway. S2a is based on Proxy Mobile IPv6 (PMIP)
and to support accesses that do not support PMIP also Mobile IPv4.
S2b: The S2b interface provides the user plane with related control and mobility support between
ePDG and the PDN Gateway. S2b is based on the Proxy Mobile IPv6 (PMIP).
S2c: The S2c interface provides the user plane with related control and mobility support between UE
and the PDN Gateway. It is implemented over trusted and/or untrusted non-3GPP Access and/or
3GPP access and it is based on the DS-MIPv6 protocol.
S6c: The S6c interface is the interface between PDN Gateway in HPLMN and 3GPP AAA server for
mobility related authentication if needed.
S6d: The S6d interface is the interface between Serving Gateway in VPLMN and 3GPP AAA Proxy
for mobility related authentication if needed. This is a variant of S6c for the roaming (inter-PLMN)
case.
S9: The S9 interface is the interface between hPCRF and vPCRF used in roaming cases for
enforcement in the VPLMN of dynamic control polices from the HPLMN.
Wa*, Wd*, Wm*, Wn*, Wx*: These interfaces are defined in 3GPP TS 23.234 and specify
interworking between 3GPP systems and WLAN. It is unclear at this point if there will be any
significant modifications to the current interfaces.
Ta*: The Ta* interface connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy
and transports access authentication, authorization and charging-related information in a secure
manner.
Page 152
Technical Specifications
3GPP Specifications
3GPP TS 22.168 Earthquake and Tsunami Warning System (ETWS) requirements

3GPP TS 22.278 Service requirements for the Evolved Packet System (EPS)
3GPP TS 23.203 Policy and charging control architecture
3GPP TS 23.216 Single Radio Voice Call Continuity (SRVCC)
3GPP TS 23.272 Circuit Switched (CS) fallback in Evolved Packet System (EPS)
3GPP TR 23.882 3GPP system architecture evolution (SAE)
3GPP TS 24.302 Access to the Evolved Packet Core (EPC) via non-3GPP access networks
3GPP TS 24.312 Access Network Discovery and Selection Function (ANDSF) Management Object
(MO)
3GPP TS 25.913 Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)
3GPP TS 29.213 Policy and charging control signaling flows and Quality of Service (QoS) parameter
mapping
3GPP TS 29.276 Optimized Handover Procedures and Protocols between EUTRAN Access and
cdma2000 HRPD Access
3GPP TS 33.401 3GPP System Architecture Evolution (SAE) Security architecture
3GPP2 Specifications
3GPP2 X.S0042-0 Voice Call Continuity between IMS and Circuit Switched System
Page 153

Evolved Packet Core CCT PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Evolved Packet Core CCT PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Contents

6 Key Features in LTE/SAE

1.1 SAE Network Architecture

1.2 Interfaces and Protocols

1.3 Roaming Architecture

1.4 Interworking with other networks

Terminals LTE Network SAE/EPC Network

• Flat and all-IP Network Architecture

UTRAN HSS/HLR PCRF •Application

•Radio resources allocation

1.1 SAE Network Architecture

1.2 Interfaces and Protocols

1.3 Roaming Architecture

1.4 Interworking with GERAN/UTRAN

•Transfer of upper layer PDUs

It carries user traffic

S1-MME Interface •One logical S1AP connection per UE.

S10 and S11 Interfaces

Keeps the control and user plane

Interfaces S5/S8 (Control Plane)

S5/S8 over GTP S5/S8 over PMIPv6

S6a and Gx Interfaces

Interface Functionality: Interface Functionality:

Interfaces S1-U,SGi and S5/S8 (User Plane)

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

LTE-Uu S1-U S5/S8 SGi

1.1 SAE Network Architecture

1.2 Interfaces and Protocols

1.3 Roaming Architecture

1.4 Interworking with other networks

1.5 SAE Key Feature on Handover

E-UTRUAN S-GW PDN-GW

E-UTRUAN S-GW PDN-GW

E-UTRUAN S-GW PDN-GW

1.1 SAE Network Architecture

1.2 Interfaces and Protocols

1.3 Roaming Architecture

1.4 Interworking with other networks

SAE/LTE MME S-GW P-GW

SGSN shall be able to select

Legacy SGSN and GGSN

ISR: Idle Mode Signaling Reduction

• S3 transfer the information related to handover/relocation between 2G/3G and LTE.

* 3GPP AAA Server

We will took CDMA network as an example of trusted non-3GPP networks. It includes

User Plane – PMIPv6

Note: PMIPv6 or MIPv4-FA can be used on S2a.

User Plane –MIPv4

(if uses DSMIPv6 to attach the UE to EPC):

(if uses MIPv4 to attach UE to EPC):

* 3GPP AAA Server

Interface Functionality Interface Functionality

S2c over untrusted non-3GPP access

6 Key Features in LTE/SAE

1.1 Key Concepts

1.2 Attach and Detach Procedure

1.3 Tracking Area Update

1.4 Handover Procedure

Default Bearer Dedicated Bearers

GUMMEI: Global Unique MME Identifier

MME MNC: Mobile Network Code

 Target cell/system capabilities

What is idle mode? What are the benefits?