LTE EPC Technical Overview

NokiaEDU
Section 1
Introduction
Module 1
EPC Overview
TMO21026W_V6.0-SG-EN-LR16.1-Edition 1
Nokia LTE Evolved Packet Core (EPC)
Technical Overview
© Nokia 2016
About this course
Welcome
Nokia LTE Evolved Packet Core (EPC) Technical Bienvenue
Overview.
欢迎
The primary audience for this course is the
operation and maintenance personnel who maintain
Bienvenidos
and troubleshoot the Evolved Packet Core (EPC) in ‫ﻣرﺣﺑﺎ‬
a Long Term Evolution (LTE) network. Willkommen
Benvenuti
Bem-vindo
Добро
пожаловать
Welkom
Course Outline
This course consists of the following Modules.

 Module 1. EPC Overview
 Module 2. EPC interfaces Protocols and Messages
 Module 3. Mobility Management Procedures
 Module 4. EPC OAM
 Appendix A – LTE acronyms and abbreviations
 Appendix B – LTE documentation
Prerequisite information
You should have completed the following course prior to taking this
course:
 Nokia LTE Solution Overview (TMO21054 )
Successful completion of this course requires basic knowledge of the

following:
 LTE architecture and terminology, including Evolved Packet Core (EPC)
and eUTRAN
 3GPP standards organization and where to find detailed information if
needed
 IP telephony, including IP addressing schemes and Ethernet connectivity
 Telecommunications-grade equipment
Course Controls
See Read voice- Search Glossary

outline over script feature Attachments
Audio time Play or Next page Minimize

min:sec Pause Previous page panels
Volume control Page number and Course

and mute total pages status
Module objectives
Upon completion of this module, you should be able to:
 Describe the primary objectives of Long Term Evolution (LTE)

 Describe the architecture of the Evolved Packet System (EPS)
 Identify the Evolved Packet Core (EPC) network elements
 Describe the primary functions of the EPC network elements
Table of Contents
1 LTE Evolved Packet System (EPS) 5

2 EPC network elements 13
3 Related components 27
4 Network sharing 33
5 Documentation 36
1 LTE Evolved Packet System (EPS)
LTE (Long Term Evolution)
 Next generation evolution for both WCDMA and CDMA operators.

 Developed by 3GPP (3rd generation Partnership Project)
 IP-based mobile core (central) network (ePC)
ePC
All-IP channel (Evolved Packet PDN
Core) Internet, etc.
 End-to-end IP mobile service delivery architecture

 VoIP instead of circuit switched network
EPS (Evolved Packet System) overview
 Evolved Universal Terrestrial Radio Network (eUTRAN)

 Evolved Packet Core (ePC)
 End-to-end IP
End-to-End IP
eUTRAN ePC
MME HSS
eNodeB
SGW PGW
-
PDN
UE PCRF
User and control

Control only
Nokia LTE Solution EPS components
 eUTRAN
 9412 eNodeB Cube, 9926 eNodeB with RRH
 ePC (Evolved Packet Core)
EPS
 9471 WMM MME (Mobility Management Entity)
 7750 MG – SGW (Serving Gateway) (Evolved Packet System)
 7750 MG – PGW (PDN Gateway)
 5780 DSC – PCRF (Policy Charging Rules Function)
eUTRAN ePC
9471 WMM MME 8650 SDM - HSS
9412 eNodeB
7750 MG - PGW
7750 MG -SGW
PDN
5780 DSC - PCRF

User
Control
Nokia LTE Solution OAM&P components
 OAM&P application
 5620 SAM (Service Aware Manager) - ePC
5620 SAM
eUTRAN ePC
9471 MME 8650 SDM - HSS
9412 eNodeB
7750 MG 7750 MG
-SGW - PGW
PDN
5780 DSC -
PCRF
User
Control
OAM&P
Gray indicates future interface
Nokia IMS (IP Multi-Media Subsystems)
 IMS applications
 8650 SDM – HSS
IMS
5620 SAM
eUTRAN ePC
8650 SDM - HSS
9471 MME
9412 eNodeB
7750 MG
7750 MG - PGW
-SGW
PDN
5780 DSC -
9453 PCRF
XMS
User
Control
OAM&P
Gray indicates future interface
Terminology
 User equipment (UE) – wireless devices that connect to the eUTRAN
 Session – In 3G networks, known as “call flow” or “data flow”; UE interaction
with the network
 Service Request – When the UE initiates a data call (starts a session) of any kind
 User plane (data plane) – Portion of a channel or protocol that carries user data
packets
 Control plane (application control or network control) – Portion of a channel or
protocol that carries signaling and control data
Blue dashed –
control data eUTRAN ePC
only 9471 MME 8650 SDM - HSS
9412 eNodeB
7750 7750
MG - MG - PDN
SGW PGW
UE
5780 DSC
- PCRF
Red solid – user User and control
and control data Control only

Data Flow Overview
 UE
 Sends initial attach requests to eNodeB
 Registers with the network to request services
 eNodeB
 Handles the scheduling of uplink and downlink data
 Connects the UE to the ePC
 MME
 Tracks, pages, and authenticates UEs
8650 SDM - HSS

MME
eNodeB
SGW PGW
PDN
PCRF
User
Control
Data Flow Overview, continued
 SGW
 Serves as the local mobility anchor for UE
 Performs IP routing and forwarding functions
 Maintains data paths between eNodeBs and the PGW
 PGW
 Provides UE with an IP address
 Terminates the SGi interface towards the PDN (packet data network)
 Provides Flow Based Charging under control of the PCRF
 PCRF
 Provides policy information to the SGW and PGW for establishing default bearer and
service-specific bearers
8650 SDM - HSS
MME
eNodeB
SGW PGW
PDN
PCRF
User
Control
2 EPC Network Elements
2 ePC Network Elements
ePC characteristics
 Provides mobile core functionality previously provided through circuit-
switched and packet-switched domains
 Packet-only (IP) architecture (first 3GPP system without a circuit switch
domain)
 Communication services are provided over IMS
 Very low end-to-end latency
ePC key functionality
 Manage mobility (an all IP mobile core network)
 Track users
 Routing of traffic
 Providing QoS and QoE connectivity to all network services
eUTRAN ePC
MME HSS
eNodeB
SGW PGW
PDN
UE PCRF
User and control

Control only
Services (voice,
User ePC Internet, email, etc.)
ePC network element functions
 9471 WMM MME – provides mobility and session control management,
and authenticates UEs
 7750 MG – SGW – routes and forwards user packets
 7750 MG – PGW – connects the user to external packet data networks
 5780 DSC – PCRF – supports service data flow and policy enforcement
 5620 SAM – OAM&P – manages all elements on the ePC
5620 SAM
ePC
MME
eUTRAN HSS
eNodeB
OFDM
SC-FDMA SGW PGW

PDN
UE PCRF
9453
XMS User and control
Control only
OAM&P
ePC control plane and data plane separation
 ePC separates control and data (user) planes for network simplification
 MME provides control plane functions and is optimized for signaling.
 SGW provides data plane functions and is optimized to provide bearer
services.
 The MME and SGW can be independently scaled or in different
geographic locations.
ePC HSS
MME
eUTRAN
S6a
eNodeB
S1-MME S11
OFDM
SGW PGW
SC-
FDMA S1-U S5/S8 SGi PD
N
PCRF
Gx
User and control
Control only
The control plane is the portion of a channel or protocol that carries signaling and control data.
The user plane provides bearer functions and carries user data packets.
9471 MME functionality
 Communicates with the eNodeB - exchanges information with the

eNodeB to control and set up a call
 Authenticates users
5620 SAM
MME HSS
Exchanges control
eNodeB procedures
7750 MG
(SGW)
UE authenticated….
Control only
OAM&P
Authenticates UEs
9471 MME functions
 Assigns temporary IDs to UEs

 Bearer management functions
 Tracks and pages UEs
 PGW and SGW selection - selects the SGW at initial UE attach and
intra-LTE handover
5620 SAM
ePC
MME
eUTRAN HSS
eNodeB
OFDM
SC-FDMA SGW PGW

PDN
UE PCRF
9453
Control only
OAM&P
UE authentication
 9471 MME authenticates UEs

 Check’s the user’s identity and confirms that the user has subscribed to
the requested services
 UE authentication process
 Check user’s identity and services at HSS (HSS stores user’s profile)
 MME sends authorization request to HSS
 HSS responds with authentication and security keys (if user and
services are valid)
 UE gets reject message and is purged from MME if not valid user or
services
WMM Hardware (ATCA)
HP c7000 BladeSystem Chassis
S S S S S
Type Slot B B B B B
5 6 7 8 9
Service 1 to 5 1 2 3 4 5 6 7 8
Blades (SB) 9 to 13 Chassis 2

S S S S S
Spare 6 to 8 B B B B B
5 6 7 8 9
14 to 16 9 10 11 12 13 14 15 16
O M M S S S S S
Type Slot A P I B B B B B
M H F 0 1 2 3 4
OAM 1 and 9 1 2 3 4 5 6 7 8
MPH 2 and 10 O M M S Chassis 1

S S S S
MIF 3 and 11 A P I B B B B B
M H F 0 1 2 3 4
Service 4 to 8 9 10 11 12 13 14 15 16
Blades (SB) 12 to 16
Front
SGW functionality
 Serves as the local mobility anchor for UE –
 Terminates the packet data network interface towards the eUTRAN (UE).
 Manages user-plane mobility –
 Performs IP routing and forwarding functions.
 Maintains data paths between eNodeBs and the PGW.
MME
eNodeB
7750 MG 7750 MG (PGW)

(SGW)
IP routing – maintains data

paths between eNodeBs
and the PGW
PCRF
Mobility anchor
User and control

Control only
PGW Functionality
 Provides the UE with an IP address

 Provides flow based charging under control of the PCRF
 Uplink and Downlink service level charging (e.g. based on SDFs defined by the
PCRF, or based on deep packet inspection defined by local policy)
 Serves as enforcement point for policy decisions coming from the PCRF
 Connects user to PDN (packet data network, or IP network)
 Serves as the cross-technology mobility anchor
 Supports mobility between 3GPP access and non-3GPP access, and between
different non-3GPP accesses
 Per-user based packet filtering (by e.g. deep packet inspection)
eNodeB Connects user
to PDN
7750 MG PDN
7750 MG
(SGW)
(PGW)
PCRF
User and control
Provides UE with an IP Control only
address…
155.555.0.555
7750 MG Chassis (Front)
 Nokia SGW and PGW are based

on the 7750 SR-12
 Leverages service router
technology
 Full set of IPv4/IPv6 routing
capabilities
 7750 SR-12 has 12 slots
 10 IOM (Input/Output Module)
slots or MG-ISM cards
 2 CPM (Control Processor Module)
slots (control card function, fabric
switching)
7750 SR-12 example configuration

PCRF functionality
 Policy management entity that provides dynamic control of QoS (quality

of service) and charging policies for service data flows (SDFs)
 Decides how SDFs should be treated by the PGW
 On UE attachment:
1. PCRF receives request for policies for the default bearer
2. Retrieves user profile from SPR and executes rule-set for decision for policy
and charging
3. Responds to SGW with PCC (policy control/charging - PCC) rule
eNodeB
SGW PGW
3. PCC rules:
SDF, QoS,
Charging rules
2. IMSI, subscription
profiles 1. IMSI, UEIP@,
location, RAT,
CAN type…
PCRF
User and control
SPR Control only
2 EPC Network Elements
PCRF: Hardware
PCRF
 Hardware
 5780 Dynamic Service Controller - DSC PCRF
 Standard ATCA platform - Fully redundant (configured horizontally)
 HP c7000 BladeSystem
 SUN X4170 M2 – Fully redundant 1+1
5620 SAM
GMLC/E-SMLC: Mobile
 Management (Configuration and OAM) Location services
 Local GUI and CLI CBC: Cell Broadcast center
MBMS: Multimedia Broadcast/
 5620 Service Aware Manger (SAM) Multicast service
eUTRAN Interworking
(2G/3G HOs)
IP/EBH Network
IMS
MME PCRF (VoIP) PSTN
EPC
UEs
eNodeB Internet
(e-mail, HSS
video,
SGW PGW new apps)
Note: 5780 DSC Training:

TOS36061 5780 DSC (Dynamic Session Controller) 3GPP PCRF Overview
TOS36062 5780 DSC (Dynamic Session Controller) Operation and Maintenance
3 Related Components
3 Related components
Functions: HSS – Home Subscriber Server
HSS is a master user database that supports the NEs that handle network
connections. It contains subscription related information (user profiles).
 Functions
 Authentication of the UE
 Tracking area for mobility
 PGW session information
 Subscriber data
5620 SAM
ePC
MME
eUTRAN HSS
eNodeB
OFDM
SC-FDMA SGW PGW

PDN
UE PCRF
9453
Control only
OAM&P
@@SECTION · @@MODULE · 33 COPYRIGHT © Nokia 2014. ALL RIGHTS RESERVED.

@@SECTIONTITLE · @@MODULETITLE
@@PRODUCT · @@COURSENAME
HSS: Hardware
HSS
 Hardware
 Nokia 8650 Subscriber Data Manager (SDM)
 Standard ATCA platform (14 blade chassis)
 Mated pair configuration (active/standby) for small configuration
 Distributed for large configuration
 Management
 Local GUI and CLI
 8950 SAM (provisioning) HSS1
EPC
UE Authentication information HSS2
Request (UE identity = x)
MME HSS3
DRA
UE id=X HSS4
Functions: SAM – Service Aware Manger
 ePC Element management
 Enhanced Service assurance
 Provisioning (configuration management)
 Operations support system (OSS) integration
5620 SAM
ePC
MME
eUTRAN HSS
eNodeB
OFDM
SC-FDMA SGW PGW

PDN
UE PCRF
9453
Control only
OAM&P
5620 SAM: Hardware
 SAM
 Hardware
 5620 Service Aware Manager (SAM)
 Server: network management processing engine, which is written in Java and runs on the Sun
Solaris or Microsoft Windows platforms
 Database: customized Oracle relational database that provides persistent storage for the
network data (Usually runs on same platform as Server)
 Clients: OSS applications or Java-based 5620 SAM GUIs (Run on Sun Solaris, Microsoft Windows
or Red Hat Linux platforms)
 Configurations GMLC/E-SMLC: Mobile
 Distributed: Sun Solaris and Window OS Location services
5620 SAM CBC: Cell Broadcast center
 Collocated: Window OS
MBMS: Multimedia Broadcast/
Multicast service
eUTRAN
Interworking
IP/EBH Network
(2G/3G HOs)
MME PCRF
EPC IMS
(VoIP) PSTN
UEs
eNodeB Internet
(e-mail,
video,
SGW PGW new apps)
Hardware platforms vary depending on number of managed elements and concurrent clients.
Component software versions
Components of the LTE solution have separate timelines for their

software upgrades. This table identifies, for LTE solution LR14.1, the
software version of each component.
Component SW release
9471 WMM MME WM10.0
7750 SR SGW R8.0
7750 SR PGW R8.0
5780 DSC PCRF R8.0
8650 SDM R5
8950 AAA (Nokia AAA) R10
5620 SAM R14 Rx
4 Network Sharing
4 Network Sharing
Radio and core Network sharing: MOCN/GWCN
3GPP defines two architectures (GWCN and MOCN) to support network sharing. In
both architectures the radio access network is shared.
 MOCN: Multi-Operator Core Network. Only the radio access network is shared.
 GWCN: Gateway Core Network. The core network (CN) elements, such as MSCs, SGSNs
and MMEs, are also shared.
Multi-Operator Core Network (MOCN) Gateway Core Network (GWCN)
CN CN CN
CN CN CN Operator Operator Operator
Operator Operator Operator A B C
A B C
S1
Shared Shared Shared
Shared RAN MME/ MME/ MME/
Operator X eNB SGW/PGW SGW/PGW SGW/PGW
S1
eNB eNB eNB
Shared RAN
Operator X
4 Network Sharing
Core Network sharing: GWCN variant
The Nokia LTE network also supports a variant of GWCN.

 Gateway Core Network (GWCN) variant: the radio access network is not shared. The
MME and possibly the SGW/PGW are shared
Gateway Core Network (GWCN) variant

CN CN CN
Operator Operator Operator
A B C
Shared Shared Shared

MME/ MME/ MME/
SGW/PGW SGW/PGW SGW/PGW
S1
eNB eNB eNB

Operator Operator Operator
A B C
5 Documentation
5 Documentation
EPC Documentation
A list of the documentation for the following EPC network elements
and EPC-related components can be found in Appendix B of the course
materials.
 9471 MME
 7750 SR (SGW & PGW)
 5780 DSC (PCRF)
 8650 SDM (HSS)
 8650 AAA (Nokia AAA)
 5620 SAM
Module summary
This module covered:

The purpose and description of 3GPP LTE
The Evolved Packet System (EPS)
 evolved Universal Terrestrial Radio Access Network (eUTRAN)
 Evolved Packet Core (EPC)
The functions and hardware of the EPC
 9471 WMM Mobility Management Entity (MME)
 7750 SR Serving Gateway (SGW)
 7750 SR PDN Gateway (PGW)
 5780 DSC Policy and Charging Rules Function (PCRF)
Related components
 8650 SDM Home Subscriber Server (HSS)
 8650 Authentication, Authorization and Accounting (AAA) server (Nokia AAA)
 5620 Service Aware Manager (SAM)
Network Sharing
 Radio and core Network sharing: MOCN/GWCN
 Core Network sharing: GWCN variant
EPC-related documentation
End of module
EPC Overview
NokiaEDU
Section 1
Introduction
Module 2
EPC interfaces Protocols and Messages
Technical Overview
© Nokia 2016
Module objectives
 Identify and describe transport protocols

 Identify the EPC network element interfaces
 Identify the protocols used between EPC network elements
 Identify the messages sent between EPC network elements
Table of Contents
1 Transport protocol overview 7

2 Interfaces, protocols, and messages 19
3 Interworking related interfaces 45
1 Transport protocol overview
1 Transport Protocol overview
Transport layers
The Transport Layer (OSI Model, Layer 4) provides transparent transfer of

data between end users.
 Responsible for
 Providing reliable data transfer services to upper layers
 Controlling reliability of a link (Flow control)
 Fragmenting and reassembling messages (called datagrams or segments)
 Error control and recovery Application
Presentation
Session
Transport
Network
Data Link
Physical
OSI Model
Note: OSI (Open System Interconnection) Model – http://en.wikipedia.org/wiki/OSI_model

EPC interface protocol
Transport protocols
 UDP – User Datagram Protocol (RFC 768)
 TCP – Transmission Control Protocol (RFC 793)
 SCTP – Stream Control Transmission Protocol (RFC 2960)
3GPP specific protocols (EPC Interfaces)
 NAS – Non-Access Stratum Protocol (3GPP TS 24.301)
 S1AP – S1 Application Protocol (3GPP TS 36.413)
 GTP – GPRS (General Packet Radio Service) Tunneling Protocol (3GPP TS
29.060)
 Diameter – (3GPP TS 29.272)
Mobility management protocol
 PMIPv6 – Proxy Mobile Internet Protocol (RFC 5213)
Note: Protocols – RFC #s: http://rfc-editor.org/rfcsearch.html

3GPP TS: http://www.3gpp.org/specification-numbering
Transport protocols
The application’s network requirements drive whether to use UDP, TCP,

or SCTP.
Feature Name UDP TCP SCTP Examples of usage:
Connection oriented N Y Y
 UDP is used for internet telephony
Reliable transport N Y Y  TCP is used where reliability of
Unreliable transport Y N Y
transport is required
Preserve message boundary Y N Y  SCTP is used for control plane
Ordered delivery N Y Y
messages
Unordered delivery Y N Y
Data checksum Y Y Y Protocol RFC #
Checksum size (bits) 16 16 32
Path MTU N Y Y
UDP 768
Congestion control N Y Y TCP 793
Multiple streams N N Y SCTP 2960
Multi-homing support N N Y
Bundling/Nagle N Y Y
For detailed information on transport protocols refer to Internet Engineering Task Force (IETF)
specific Request for Comments (RFC) number: http://rfc-editor.org/rfcsearch.html
NAS – Non-Access Stratum
NAS protocol is used between User Equipment (UE) and the MME. It is
described in 3GPP Technical Specification 24.301.
 Primary Functions
 EPS Mobility Management (EMM):
 User location (tracking) and identity confidentiality
 Provide connection management services to Session Management (SM) sub layer
 EPS Session Management (ESM)
 User plane bearer:
· Activation
· Modification and
· Deactivation
 NAS Security
 Authentication/
authorization
 Keying distribution
General message organization for a Security protected NAS message
Note: 3GPP TS: http://www.3gpp.org/ftp/Specs/html-info/24-series.htm

S1AP - S1 Application Protocol
S1AP protocol is used between the eNodeB and the MME. It is described in
3GPP Technical Specification 36.413.
 Primary functions
 Provide signaling service between eNB and EPC
 Non UE-associated services
· S1 interface management
· RAN information management
· RAN configuration transfer
 UE-associated services
· E-UTRAN Radio Access Bearer (E-RAB) management
· UE context management
· S1-based Handover
· Paging
· Location reporting

GTP – GPRS Tunneling Protocol
GPRS Tunneling Protocol (GTP) is:
 A group of IP-based communication protocols used to carry General Packet
Radio Service (GPRS). The GTP protocol is layered on top of UDP. The uplink
and downlink service flows are sent via the tunnel.
 Used between SGW and PGW, SGW and MME, and SGW and eNodeB, as well as
between pooled MMEs. In interworking solutions, GTP is used between MME and
SGSN; between PGW and SGSN, and PGW and HSGW; and between SGW and
SGSN, and SGW and RNC.
 Described in 3GPP Technical Specification 29.274, 29.281 & 32.295.
Primary Functions
 GTP-C (control plane: TS 29.274)
 Path management
 Tunnel management
 Mobility management
 GTP-U (user plane: TS 29.281)
 Carry encapsulated T-PDUs and signaling messages between a given pair of
GTP-U Tunnel endpoints
 T-PDU – Transport-Protocol Data Unit
 GTP-U endpoints – eNodeB-to-SGW/SGW-to-PGW
 GTP1 (TS 32.295)
 Carries charging data from the Charging Data Function (CDF) of the GSM or
UMTS network to the Charging Gateway Function (CGF)
Diameter protocol
Diameter is a networking protocol used for authentication, authorization
and accounting (AAA), and is a successor to RADIUS.
Diameter controls communication between the authenticator and any
network element requesting authentication.
 Signaling between MME and HSS (TS 29.272)
 Insert/Delete subscriber data
 Authentication information retrieval
 Signaling between PGW and the PCRF (TS 29.212)
 Gx Application
 Credit Control Request /Answer
 Re-Auth Request (RAR)/ Re-Auth Answer (RAA)
 Signaling between PGW and AAA server (TS 23.402)
 Mobility authentication
 Update PGW address request

Proxy Mobile IPv6 (PMIPv6)
Proxy Mobile IPv6 protocol is intended for providing network-based IP
mobility management support to a mobile node, without requiring the
participation of the mobile node in any IP mobility related signaling.
The mobility entities in the network will track the mobile node's
movements and will initiate the mobility signaling and set up the required
routing state.
 Primary Function
 Signaling between PGW and HSGW (TS 23.402)
PROPERTIES
On passing, 'Finish' button: Goes to Next Slide
On failing, 'Finish' button: Goes to Next Slide
Allow user to leave quiz: After user has completed quiz
User may view slides after quiz: At any time
Show in menu as: Multiple items

2 Interfaces, protocols, and messages
Interfaces per network solution
Regardless of LTE solution, the components of the EPC are the same, as
are most of the interfaces.
However, each interworking solution includes one or more additional
interfaces between EPC network elements and network elements located
in the existing 2G and 3G networks.
 Solutions
 LTE only
 LTE with CDMA interworking
 LTE with UMTS interworking
Additional interfaces are involved in roaming situations. Theses interfaces are

also identified and described in this section.
LTE only solution
eUTRAN EPC
8650 SDM -
9471 MME HSS/EIR
9412 eNodeB S10
S6a/S13
OFDMA
S1-MME S11
7750 SR-SGW 7750 SR-PGW
SC-FDMA
S1-U S5 SGi
PDN
X2
5780 DSC-PCRF
Gx
Sh/LDAP
9412
eNodeB
User
Control
S1-MME
S1-U
EPC interfaces: MME
MME Interface Network elements Solution
S1-MME eNodeB - MME All Solutions

S6a/S13 MME – HSS All Solutions
S10 MME – MME All Solutions
S11 MME - SGW All Solutions
Gn/S3 MME – SGSN LTE w/UMTS
Sm MME – MBMS GW All Solutions
SLs MME – E-SMLC All Solutions
SLg MME – GMLC All Solutions
SBc MME – CBC All Solutions
M3 MME – eNB (MCE) All Solutions
SGs/Sv MME – 3G-MSC/VLR LTE w/UMTS
Red = User
Blue = Control
*Interface that carries both user and control plane data.
EPC interfaces: SGW
SGW Interface Network elements Solution

S1-u eNodeB – SGW All solutions
S5/S8* SGW – PGW All Solutions
S4* SGW – SGSN LTE w/UMTS
S12 SGW - RNC LTE w/UMTS
Red = User
Blue = Control
EPC interfaces: PGW and PCRF
PGW Interface Network elements Solution

SGi PGW - PDN All Solutions
S6b PGW - AAA LTE w/UMTS, LTE
w/CDMA
Gx PGW - PCRF All Solutions
S2a* PGW – HSGW LTE w/CDMA
Gn/Gp* PGW – SGSN LTE w/UMTS
PCRF Interface Network elements Solution

Gxa PCRF – HSGW LTE w/CDMA Red = User
Sh/LDAP PCRF - HSS All Solutions Blue = Control
S9 PCRF-PCRF All Solutions

LTE Uu (UE to eNB) and S1-MME (eNB-MME)
Both the LTE Uu and S1-MME interfaces carry the Non-Access Stratum
(NAS) messages between the UE and the MME. NAS messages pass through
the eNodeB unchanged.
All messages between eNB and MME use S1-AP. NAS messages are
encapsulated in S1-AP messages on the S1-MME interface.
 Protocol
 NAS
 NAS Messages:
 AUTHENTICATION REQUEST/RESPONSE UEs
/REJECT/FAILURE eNB MME
 SECURITY MODE COMMAND/COMPLETE/REJECT
LTE Uu S1-MME
 ATTACH REQUEST/ACCEPT/COMPLETE/REJECT
NAS NAS
 SESSION MANAGEMENT CONFIGURATION REQUEST
/ACCEPT/REJECT RRC RRC S1-AP S1-AP
 BEARER RESOURCE ALLOCATION REQUEST PDCP PDCP
SCTP SCTP
/REJECT RLC
RLC
 PDN CONNECTIVITY REQUEST/ACCEPT/REJECT IP IP
MAC MAC
 DETACH REQUEST/ACCEPT L2 L2
PHY PHY
 BEARER RESOURCE RELEASE REQUEST/REJECT L1 L1
Note: Not all NAS messages are listed. Refer to 3GPP TS 24.301 for complete list and descriptions.
S1-MME (eNodeB-MME)
Interface for the control plane protocol between eNodeB and MME. Used
to exchange information to control and set up the call.
In the S1-MME interface, SCTP stream 0 is for the eNB-MME signaling.
Stream 1 is for the UE-to-MME signaling (i.e. NAS)
 Protocols
 S1-AP (application layer)
 SCTP - Stream Control Transmission Protocol
eNB
 S1-AP messages
 S1 SETUP REQUEST/ RESPONSE/FAILURE
 INITIAL CONTEXT SETUP REQUEST/RESPONSE/FAILURE
 UE CONTEXT MODIFICATION REQUEST/RESPONSE
 UE CONTEXT RELEASE REQUEST/COMMAND/COMPLETE S1-MME MME
 E-RAB (eUTRAN-Radio Access Bearer) SETUP
REQUEST/RESPONSE S1-AP S1-AP
 E-RAB MODIFY REQUEST/RESPONSE SCTP SCTP
 E-RAB RELEASE COMMAND/RESPONSE IP IP
 eNB CONFIGURATION UPDATE ACKNOWLEDGE/FAILURE
 MME CONFIGURATION UPDATE ACKNOWLEDGE/FAILURE L2 L2
 RESET/RESET ACKNOWLEDGE L1 L1
Note: Not all S1-AP messages are listed. Refer to 3GPP TS 36.413 for complete list and descriptions.
S6a (MME-HSS)
Interface between MME and HSS or DRA that enables the transfer of
location information and subscriber related data used for authenticating,
authorizing and changing user access in the evolved system.
 Protocols
 Diameter
 SCTP
 Messages (Diameter)
 UPDATE LOCATION REQUEST/ANSWER
 CANCEL LOCATION REQUEST/ANSWER
MME S6a HSS or DRA
 AUTHENTICATION INFORMATION
REQUEST/ANSWER Diameter Diameter
 INSERT SUBSCRIBER DATA REQUEST/ANSWER SCTP SCTP

 DELETE SUBSCRIBER DATA REQUEST/ANSWER IP IP
 PURGE UE REQUEST/ANSWER L2 L2
 RESET REQUEST/ANSWER L1 L1
 NOTIFY REQUEST/ANSWER
S13 over S6a (MME-EIR)
Implements the connection from MME to the Equipment Identity Register

(EIR). The EIR enables the identity check of user equipment (as opposed
to the subscriber) between the MME and the EIR.
This interface is used to verify the status of the equipment in the event
of loss or theft.
When the EIR is integrated into the HSS, the S13 function is implemented
on the S6a interface, which uses the same protocol stack.
 Protocols
 Diameter
 SCTP
 Messages (Diameter) S13
MME S6a HSS/EIR
 ME-IDENTITY-CHECK-REQUEST (ECR) Diameter Diameter
 ME-IDENTITY-CHECK-ANSWER (ECA)
SCTP/TCP SCTP/TCP
IP IP
L2 L2
L1 L1
S10 (MME-MMEs)
S10 is the control plane protocol interface between MMEs. It is used to
move the UE context from one MME to another in case of MME relocation.
 Protocols
 GTP-C
 UDP
 Messages
 IDENTIFICATION REQUEST/RESPONSE
 CONTEXT REQUEST/RESPONSE/ACKNOWLEDGE
 FORWARD RELOCATION REQUEST/RESPONSE
 FORWARD RELOCATION COMPLETE MME S10 MME
NOTIFICATION/ACKNOWLEDGE GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
The relocation of a MME may be required during intra-eUTRAN mobility procedures such as Tracking
Area Update (TAU) in IDLE mode with MME relocation, and S1 Handover with MME relocation.
S11 and S5: Control plane (Path Management)
The interfaces between MME and SGW (S11) and SGW and PGW (S5)
provide control of bearer establishment, modification, release, and
suspension. Path Management messages are sent between all GTP-C
entities.
 Protocols
 GTP-C (GPRS Tunneling Protocol-Control plane)
 UDP (User Datagram Protocol)
 Messages (GTP-C Path Management)
 ECHO REQUEST/RESPONSE
 VERSION NOT SUPPORTED INDICATION
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1
S11 and S5: Control plane (MME - SGW – PGW)
GTP-C tunnel management messages sent between the MME, SGW and
PGW (S11 and S5)
 Messages (GTP-C tunnel management)
 CREATE SESSION REQUEST/RESPONSE
 CREATE BEARER REQUEST/RESPONSE
 BEARER RESOURCE COMMAND
 BEARER RESOURCE FAILURE INDICATION
 MODIFY BEARER REQUEST/RESPONSE
 DELETE SESSION REQUEST/RESPONSE
 DELETE BEARER REQUEST/RESPONSE
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1
S11 and S5: Control plane (Various Messages)
A list of some of the other GTP-C messages sent between the MME, SGW
and/or PGW.
 Messages (GTP-C)
 DOWNLINK DATA NOTIFICATION/NOTIFICATION ACKNOWLEDGE
 DOWNLINK DATA FAILURE INDICATION
 UPDATE USER PLANE REQUEST/RESPONSE
 MODIFY BEARER COMMAND
 MODIFY BEARER FAILURE INDICATION
 UPDATE BEARER REQUEST/RESPONSE
 DELETE BEARER COMMAND
 DELETE BEARER FAILURE INDICATION
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1
M3/Sm (MCE-MME-MBMS GW)
The M3 interface supports communication the Multicast Control Entity
(MCE) in the eNodeB nodes and the 9471 MME.
 MME transmits session control messages toward the MCEs using the M3
interface.
M3 includes the following protocols:
 M3-AP
 SCTP over IPv4 or IPv6 for transport
 Single-homing or Multi-homing is supported
eNB/MCE
M3 Sm (GTP-C)
MME MBMS GW
M3-AP M3-AP
SCTP SCTP
IP IP
L2 L2
L1 L1
SLs (MME-E-SMLC)
The SLs interface supports GMLC SLh
communication between the 9471 MME
and the EPC Serving Mobile Location
SLg
Center (E-SMLC ) to obtain a UE's eNB
position. MME
S1-MME S6a
 Supports of Emergency Location Services
(LCS).
SLs
HSS
SLs includes the following protocols:
 LCS-AP E-SMLC
LCS-AP messages LCS-AP
SLs
LCS-AP
 LCS-AP Location Request message SCTP SCTP
 LCS-AP Location Response message IP IP
 LCS-AP Location Abort Request message L2 L2
 LCS-AP Connection Oriented Information message
L1 L1
 LCS-AP Connectionless Information message
E-SMLC
 LCS-AP Reset Request message MME
 LCS-AP Reset Acknowledge message

SLg (MME-GMLC)
The SLg interface supports GMLC SLh

and the Gateway Mobile Location Center (GMLC). SLg
eNB
 Transports positioning requests and
MME
responses for Location Services (LCS) S1-MME S6a
between GMLC and MME.
SLg includes the following protocols: SLs
HSS
 Diameter EPC LCS Protocol (ELP)

E-SMLC
ELP messages Diameter (ELP)
SLg
Diameter (ELP)
 Provide Location Request (PLR) SCTP SCTP
 Provide Location Answer (PLA) IP IP
 Location Report Request (LRR) L2 L2
 Location Report Answer (LRA) L1 L1
MME GMLC
SBc (CBC- MME)
The SBc interface supports eNB
communication between the 9471

S1-MME SBc
MME and the Cell Broadcast Center
(CBC). MME
CBC
 Transports messages associated with
Warning Message Delivery function.
SBc includes the following protocols:
 SBc-AP
 Single-homing or Multi-homing between MME and CBC is supported
 Multiple SCTP streams are supported
SBc
Warning Message Transmission messages SBc-AP SBc-AP
 WRITE-REPLACE WARNING REQUEST SCTP SCTP

IP IP
 WRITE-REPLACE WARNING RESPONSE
L2 L2
 STOP WARNING REQUEST
L1 L1
 STOP WARNING RESPONSE
MME CBC
S1-U (eNodeB – SGW) and S5 (SGW – PGW): User plane
User plane reference points between the eNodeB, SGW and PGW for the
per-bearer user plane tunneling.
 Protocols
 GTP-U – GPRS Tunneling Protocol-User plane
 Messages
eNB
 ERROR INDICATION
 SUPPORTED EXTENSION
HEADERS NOTIFICATION HSS
S1-U SGW S5 PGW
 G-PDU
GTP-U GTP-U GTP-U
 END MARKER
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1
Note: S1-U also used for inter-eNB path switching during hand over.
S5 is used for SGW relocation due to UE mobility and if the SGW needs to connect to a non-
collocated PGW for the required PDN connectivity.
SGi (PGW - PDN)
Interface between PGW and the Packet Data Network.
IP packets pass from the UE to the PGW and then over the SGi to the PDN
entity.
 Protocol
 IP
 IP Message
 IP PACKET
HSS
PDN
UEs SGW PGW
eNodeB
S1u S5 SGi
IP IP
Gx (PGW - PCRF)
Interface between PGW and the Policy and Charging Rule Function (PCRF).
It provides transfer of Policy and Charging Control (PCC) rules between
the PCRF to the Policy and Charging Enforcement Function (PCEF) in the
PGW.
 Protocol
 Diameter
 Messages
 Gx APPLICATION PCEF
 CREDIT CONTROL REQUEST/ANSWER
 RE-AUTHORIZATION REQUEST/ANSWER PGW
Gx
PCRF
Gx*
Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1
* The Gx reference point resides between the PCRF and the PCEF (3GPP TS 23.203)
located in the PGW. Gx protocol is described in 3GPP TS 23.402.
Sh (PCRF – HSS)
Sh is the reference point for PCRF* to obtain subscriber information from
an HSS that supports the Diameter protocol.
 Protocol
 Diameter
 Messages
 USER DATA REQUEST/ANSWER
 PROFILE UPDATE REQUEST/ANSWER
 SUBSCRIBE NOTIFICATION REQUEST/ANSWER
 PUSH NOTIFICATION REQUEST/ANSWER
PCRF Sh HSS
Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1
* Relevant PCRF subscriber information from the HSS is cached locally at the 5780 DSC
for rapid access.
LDAP (PCRF – HSS)
LDAP (Lightweight Directory Access Protocol) is the reference point for
PCRF* to obtain subscriber information from an HSS that supports LDAP.
 Protocol
 LDAP
 Messages
 BIND REQUEST/ RESPONSE
 UNBIND REQUEST
 SEARCH REQUEST
 SEARCH RESULT ENTRY / DONE / REFERENCE
PCRF LDAP HSS
 MODIFY REQUEST / RESPONSE
 ADD REQUEST / RESPONSE LDAP LDAP
 DEL REQUEST /RESPONSE TCP TCP
 MODIFY DN REQUEST / RESPONSE IP IP
 COMPARE REQUEST / RESPONSE L2 L2

 ABANDON REQUEST L1 L1
 EXTENDED REQUEST/ RESPONSE
for rapid access.
PROPERTIES

3 Interworking related interfaces
LTE with CDMA interworking solution
AAA
DNS
IMS PDN
LTE MME EPC S6b
HSS/EIR
eUTRAN SWx
S6a/S13
eNodeB S10
S1-MME S11
OFDMA
S102
SGW PGW MGW
SC- S101
FDMA S1-U S5/S8 SGi
PDN
PSTN
Gx
PCRF Sh/LDAP
CDMA eHRPD
eBTS eRNC User
Gxa Control
HSGW S103
Gray indicates future
interface in Nokia
network
S2a
3G1X MSC
LTE with UMTS interworking solution
3G-MSC/VLR GMSC
NodeB
UMTS/
GSM RNC or
BSC SGSN GGSN
Gn/Gp AAA
DNS Gn/Gp
S4 IMS PDN
LTE MME SGs/Sv EPC S6b
HSS/EIR
eUTRAN Gn/S3 SWx
S6a/S13
eNodeB S10
S1-MME S11
OFDMA
SGW PGW MGW

SC- S12
FDMA S1-U S5/S8 SGi
PDN PSTN
Gx
Gx
PCRF Sh/LDAP
User
Control
Note: the WMM supports a Combo Mode where MME and SGSN can be supported on the same Chassis
MME
WMM Gn
SGSN
Interworking related interfaces
LTE with CDMA
Interface Network elements
S6b PGW - AAA

S2a* PGW – HSGW
Gxa PCRF - HSGW
LTE with UMTS
S6b PGW - AAA

Gn/S3 MME – SGSN
Gn/Gp* PGW - SGSN
SGs/Sv MME – 3G-MSC/VLR
S4* SGW - SGSN *The Gn/Gp interface carries both user
S12 SGW - RNC and control plane data.
S6b (PGW - AAA)
Interface between PGW and the Authentication, Authorization and
Accounting (AAA) server proxy for mobility authentication, if needed.
May also be used to retrieve and request storage of mobility
parameters; and, to retrieve a static QoS profile for a UE for Non-3GPP
access if dynamic PCC is not supported.
 Protocol
 Diameter
 Messages
 UPDATE PDN GW ADDRESS REQUEST/ ACKNOWLEDGE
 DETACH INDICATION/ ACKNOWLEDGE
PGW S6b AAA

Diameter Diameter
SCTP/TCP SCTP/TCP
IP IP
L2 L2
L1 L1
S2a (PGW – HSGW): User plane
Interface that provides the user plane and related control and mobility
support between Trusted Non-3GPP IP access and the PGW.
 Protocol
 PMIPv6
 Messages
 ECHO REQUEST / RESPONSE
 PROXY BINDING UPDATE /ACKNOWLEDGEMENT
 BINDING REVOCATION INDICATION / ACKNOWLEDGEMENT
A10/A11 S2a
eHRPD HSGW PGW
eRNC HSS
IP PMIPv6 PMIPv6
IP IP IP
L2 L2 L2 L2
L1 L1 L1 L1
S2a (PGW – HSGW): Control plane
The figure below illustrates the S2a control plane.
 Protocol
 PMIPv6
 GRE
 Messages
 PROXY BINDING UPDATE REQUEST
 PROXY BINDING ACKNOWLEDGEMENT
 BINDING REVOCATION INDICATION /ACKNOWLEDGEMENT
A10/A11 S2a
eHRPD HSGW PGW
eRNC
PMIPv6 PMIPv6
IP IP
L2 L2 L2 L2
L1 L1 L1 L1
Gxa (PCRF – HSGW)
Interface that provides transfer of QoS policy information from the PCRF
to the Trusted Non-3GPP accesses.
 Protocol
 Diameter
 Messages
 CC-Request (CCR) Command
 CC-Answer (CCA) Command
 Re-Auth-Request (RAR) Command
 Re-Auth-Answer (RAA) Command
PCRF Gxa HSGW

Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1
Gn (MME – SGSN)
Interface for the control plane between the MME and the Pre-Release 8
SGSN. Gn allows the MME to affect handover between LTE and
UMTS/GERAN.
 Protocols
 GTP-C
 UDP
 Messages
 Path Management Messages
 Tunnel Management Messages
 Location Management Messages
 Mobility Management Message
Gn SGSN
MME
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
S3 (MME – SGSN)
Interface for the control plane between the MME and the Release 8 or
later SGSN. Gn allows the MME to affect handover between LTE and
UMTS/GERAN.
 Protocols
 GTP-C
 UDP
 Messages
 DETACH NOTIFICATION/ ACKNOWLEDGE
 CS PAGING INDICATION
 ALERT MME NOTIFICATION / ACKNOWLEDGE
 UE ACTIVITY NOTIFICATION / ACKNOWLEDGE
S3 SGSN
MME
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
Gn/Gp (PGW – SGSN) (1 of 3)
Interface between the PGW and Gn/Gp SGSN (2G-SGSN or 3G-SGSN).
GTP (GTP-C, GTP-U and GTP1) is defined for the Gn interface, i.e. the
interface between GSNs within a PLMN, and for the Gp interface between
GSNs in different PLMNs.
 Protocol
 GTP-C
 Messages
SGSN
 Mobility Management Message PGW Gn/Gp
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
Note: Specific GTP-C messages are not listed. Refer to 3GPP TS 29.060 for a full list & descriptions.
In the user plane, GTP uses a tunnelling mechanism (GTP-U) to provide a
service for carrying user data packets.
 Protocol
 GTP-U
 Messages
 SUPPORTED EXTENSION HEADERS NOTIFICATION
 G-PDU
PGW Gn/Gp SGSN
GTP-U GTP-U
UDP UDP
IP IP
L2 L2
L1 L1
GTP1 is used to transfer charging data from the Charging Data Function to
the Charging Gateway Function.
 Protocol
 GTP1
 Messages
 ECHO REQUEST/REPSONSE
 VERSION NOT SUPPORTED
 NODE ALIVE REQUEST/REPSONSE
 REDIRECTION REQUEST/REPSONSE
 DATA RECORD TRANSFER REQUEST/REPSONSE
PGW Gn/Gp SGSN

GTP1 GTP1
UDP UDP
IP IP
L2 L2
L1 L1
SGs (MME – 3G-MSC/VLR)
Interface between the MME and the Visitor Location Register (VLR) used for the mobility
management and paging procedures between EPS and CS domain (with CS Fall back
capability). SGs is also used for the delivery of mobile originating and mobile terminating
SMS over EUTRAN in case SMSIP is not used.
 Protocols
 Diameter
 SCTP/TCP
 Messages
 SGsAP-LOCATION-UPDATE-REQUEST/ACCEPT /REJECT
 SGsAP-TMSI-REALLOCATION-COMPLETE
SGs MSC Server
 SGsAP-PAGING-REQUEST/ REJECT MME
 SGsAP-SERVICE-REQUEST Diameter Diameter
 SGsAP-UE-UNREACHABLE SCTP/TCP SCTP/TCP
 SGsAP-UPLINK-UNITDATA
IP IP
 SGsAP-DOWNLINK-UNITDATA
L2 L2
 SGsAP-RELEASE-REQUEST
 SGsAP-EPS-DETACH-INDICATION/ ACK L1 L1
 SGsAP-ALERT-REQUEST/ ACK/ REJECT
 SGsAP-UE-ACTIVITY-INDICATION SGs used for CSFB (Circuit
switch Fall Back)
 SGsAP-MM-INFORMATION-REQUEST
 SGsAP-RESET-INDICATION
 SGsAP-RESET-ACK
 SGsAP-STATUS
SV (MME – 3G-MSC/VLR)
Sv is a reference point between the MSC/VLR
and the 9471 MME:
 Allows MME to interact with the MSC to handover
IMS-anchored voice sessions from LTE to UMTS.
 Supports SRVCC, which provides IMS continuity
when the UE is a single radio.
Sv includes the following protocols:
SV MSC Server
 GTPv2-C MME
 Tunnels signaling messages between MME and MSC Diameter Diameter
 UDP/IPv4 or IPv6 SCTP/TCP SCTP/TCP
 Transfers signaling messages IP IP
Sv Messages L2 L2
 SRVCC PS to CS Request L1 L1
 SRVCC PS to CS Response
 SRVCC PS to CS Complete Notification SV used for SRVCC (Single Radio
 SRVCC PS to CS Complete Acknowledge Voive Call Continuity)
 SRVCC PS to CS Cancel Notification
 SRVCC PS to CS Cancel Acknowledge
S4 (SGW – SGSN): User plane
Interface that provides related control and mobility support between
GPRS Core and the 3GPP Anchor function of SGW. In addition, if Direct
Tunnel is not established, S4 provides the user plane tunneling.
S4 is based on the Gn reference point as defined between SGSN and
GGSN.
 Protocol
 GTP-U
 UDP
 Messages
 END MARKER SGW
S4 SGSN
 G-PDU GTP-U GTP-U
UDP UDP
IP IP
L2 L2
L1 L1
S4 (SGW – SGSN): Control plane
GGSN.
 Protocol
 GTP-C
 UDP
 Messages
 CREATE FORWARDING TUNNEL REQUEST / RESPONSE
 CREATE INDIRECT DATA FORWARDING
TUNNEL REQUEST/ RESPONSE
 DELETE INDIRECT DATA FORWARDING S4 SGSN
SGW
 RELEASE ACCESS BEARERS REQUEST / RESPONSE GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
S12 (SGW – RNC)
Interface between UTRAN and SGW for user plane tunneling when Direct
Tunnel is established. It is based on the Iu-u/Gn-u reference point using
the GTP-U protocol as defined between SGSN and UTRAN or respectively
between SGSN and GGSN.
Usage of S12 is an operator configuration option.
 Protocol
 GTP-U
 UDP
 Messages
 ERROR INDICATION S12
SGW RNC
GTP-U GTP-U
 END MARKER
 G-PDU UDP UDP
IP IP
L2 L2
L1 L1
Roaming-related interfaces
S8* SGW – PGW

S9 V-PCRF – H-PCRF
S8 (SGW – PGW): User Plane
The inter-PLMN interface that provides the user and control plane
between the SGW in the VPLMN and the PGW in the HPLMN.
S8 is the inter-PLMN variant of S5.
 Protocol
 GTP-U
 UDP
 Messages
HEADERS NOTIFICATION
 G-PDU
 END MARKER
S8
SGW PGW
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1
S8 (SGW – PGW): Control Plane
 Protocol
 GTP-C
 UDP
 Messages
 DELETE SESSION REQUEST/RESPONSE S8
 DELETE BEARER REQUEST/RESPONSE SGW PGW
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1
S9 (V-PCRF – H-PCRF)
Interface that provides transfer of QoS policy and charging control

information between the Visited PCRF and the Home PCRF in order to
support local breakout function.
S9 is used in roaming scenarios involving an VPLMN and a HPLMN.
Two main roaming scenarios:
 Visited Access (“local breakout”): PCEF is located in the VPLMN, and the UE obtains
access to the PDN from the VPLMN.
 Home Routed Access: PCEF is located in the HPLMN, and the UE obtains access to the
PDN from the HPLMN.
Protocol
 Diameter S9
H-PCRF V-PCRF
 SCTP Diameter Diameter
Messages SCTP SCTP
 CC-Request (CCR) Command IP IP
 CC-Answer (CCA) Command L2 L2
 Re-Auth-Request (RAR) Command L1 L1
PROPERTIES

Module summary
This module covered:

Transport layer definitions and descriptions
Transport layer protocols used in EPC interface packets
 Common protocols
 Mobility protocols
Interfaces between network elements
Protocols used for each interface
Messages sent between network elements, via the interfaces
 LTE only
 LTE with CDMA interworking
 LTE with UMTS interworking
End of module
EPC interfaces, Protocols, and Messages
NokiaEDU
Section 1
Introduction
Module 3
Mobility Management Procedures
Technical Overview
© Nokia 2016
Module objectives
 Identify the main mobility management procedures for the Evolved Packet
System (EPS)
 Describe the actions that take place within each main LTE call flow
Table of Contents
1 Introduction 7
2 Attach procedure 11
3 S1 Release procedure 16
4 Tracking Area Update (TAU) procedure 19
5 Service Request procedures 24
6 Detach procedures 34
7 Intra-eUTRAN Handover procedures 39
8 LTE-CDMA Interworking / CSFB 56
9 LTE-WCDMA (UTRAN/GERAN) interworking/CSFB 63
10 Multiple PDN Connections procedure 72
1 Introduction
1 Introduction
Mobility management procedures
The diagram below reviews the interfaces used in LTE/UTRAN-GERAN (WCDMA)/eHRPD-RAN (CDMA).
1 Introduction
End-to-End scenario
1 Introduction
Mobility management procedures
The following are mobility management procedures for the Evolved
Packet System (EPS is the eUTRAN and EPC network)
 Attach Procedure
 S1 Release Procedure
 Tracking Area Update Procedure
 Service Request Procedures
 UE-Initiated
 Network-triggered
 Detach Procedures
 UE-Initiated
 MME-Initiated
 HSS-Initiated
 Intra-eUTRAN Handover Procedures
 X2-Based
 S1-Based
 LTE - CDMA Interworking / Circuit switch Fall Back
 LTE WCDMA (UMTS/GSM) Interworking / Circuit switch Fall Back
 Multiple PDN connections
For specific details and messages for mobility management procedures,
see the 3GPP TS 23.401.
2 Attach Procedure
2 Attach procedure
Attach procedure
 To receive service from the network, the UE must be authenticated,

and its location in the network must be identified. This is referred to as
network attachment.
 During the Attach procedure default bearers are assigned, along with
allocation of the IP address to the UE.
2 Attach procedure
Attach procedure (1 of 3)
PDN
1 Power on
UE eNB MME SGW PGW HSS PCRF

2
Radio Resource
Connection
(RRC) set up.
3
RRC Connection
Complete [NAS 4
Attach Request] NAS Attach
Request
5
Identity Request 6
/Response Auth-Info-
Request 7
Auth-Info-
8
Request Ack
9 NAS: Auth-
NAS: Auth- Request
Request
10 Required
11 Conditional
NAS: Auth-
NAS: Auth- Data
Response
Response
2 Attach procedure
PDN

12
13 NAS: Security
NAS: Security Mode
Mode
Command
Command
14
NAS: Security 15
Mode NAS: Security
Mode
Complete 16
Complete
Update Location Request/Answer
17
Create Session 18
Request Create Session 19
Request CC-Request /CC-Answer
20
21 Create Session
Create Session
22 Response Required
Initial Context Response Conditional
Setup Data
2 Attach procedure
PDN
PDN

23
RRC Connection
Reconfiguration
For detailed 3GPP call flow specifications, see 3GPP TS 23.401
24
http://www.3gpp.org/ftp/Specs/html-info/23401.htm
RRC Connection
Reconfiguration
25
Complete
Initial Context
26 Setup Response
Attach Complete 27
Attach Complete
First Uplink
Data
28
Modify Bearer
Request
29
Modify Bearer Required
Response Conditional
First Downlink
Data
Data
3 S1 Release Procedure
3 S1 Release procedure
S1 Release procedure
● This procedure releases a UE’s radio bearers, S1 bearers, and
signaling resources from the eNodeB.
● Procedure results in
 UE state in MME set to ECM-IDLE
 All UE related context information deleted in eNodeB
● S1 Release is
 eNodeB-initiated with cause
(e.g., O&M intervention, unspecified failure, user inactivity, UE-generated
signaling connection release, etc)
 MME-initiated with cause
(e.g., authentication failure, detach, etc.)
3 S1 Release procedure
S1 Release procedure
PDN
PDN
1
S1 UE Context
Release Request
2
Modify Bearer
Request
3
Modify Bearer
4 Response
S1 UE Context
Release
5 Command
RRC
Connection
Release
6
S1 UE Context Required
Release
Conditional
Complete
Data
4 Tracking Area Update (TAU) procedure
4 Tracking Area Update (TAU) Procedure
Tracking Area Update procedure
● The Tracking Area Update (TAU) is

 Used to
 Periodically notify the network of the availability of the UE
 Inform the MME when the UE tracking area has changed
 Always initiated by the UE
 In Idle or Connected Mode
● TAU Triggers
 The UE detects entering a tracking area not in the list of tracking areas
 The periodic tracking area update timer expires
 The RRC connection was released with release cause “load balancing
TAU required”
 A change of the UE Core Network Capability information of the UE
● During the tracking area update procedure, the MME may initiate an
authentication procedure and set up security mode.
in idle mode W/out SGW & MME changes (1 of 2)
PDN
1
Radio
Resource
Connection
(RRC) set up 2 3
S1 Initial UE If integrity check fails or new auth
message is needed, then Authentication is
mandatory.
4 HSS returns AKA vector
5 Authentication
Auth Request Request
6
Auth Response
7
Auth Response
8
NAS Security
9 Mode Command
NAS Security message Required
Mode Command
Conditional
& Complete Data
messages
in idle mode w/out SGW & MME changes (2 of 2)
PDN

10
NAS: Security
Mode Complete
11
12 DL NAS Transport
DL Info Transfer (TAU Accept)
(TAU Accept)
13 14
TAU Complete S1 Uplink NAS
Transport
(TAU Complete)
15
S1 UE Context
16 Release
Command
RRC
connection Required
release 17 Conditional
eNodeB confirms Data
S1 release
Tracking Area Update, with MME or SGW change
Additional steps are performed if there is a change of MME or SGW
MME Change:
● For a UE in ECM-IDLE state
 eNodeB determines that the current MME is not associated with the eNodeB
 eNodeB selects a new MME
 Forwards a TAU Request to the new MME
● For a UE in ECM-CONNECTED state
 Handover procedure applies
 TAU procedure occurs at the end of the handover procedure
SGW Change:
● The MME (new or unchanged)
 Determines the SGW needs to be relocated
 Selects the new SGW
 Sends a Create Session Request to the new SGW
 The new SGW sends a Modify Bearer Request to PGW
 Deletes the session with the old SGW
For details and specific messages associated with the different TAU procedures refer to the
3GPP TS 23.401.
5 Service Request procedure
5 Service Request Procedure
Service Request procedures
● The purpose of the Service Request procedure is to:

 Transfer the EPS Mobility Management (EMM) mode of the UE from
ECM-IDLE to ECM-CONNECTED
 Reestablish the radio and S1 bearers
● A service request is always initiated by the UE
● A service request is triggered…
By the… When…
UE UE has pending data to send and no radio bearer is established
Network Downlink signaling is pending and the UE is in ECM-IDLE
ECM-CONNECTED: When a signaling connection exists between the UE and the MME. The
signaling connection is made up of two parts: an RRC connection and an S1-MME connection.
ECM-IDLE: When no NAS signaling connection exists between the UE and the network. In
ECM-IDLE state, a UE performs cell selection/reselection.
UE-initiated Service Request procedure(1 of 2)
PDN

1
RRC Connection
Request
2
RRC Connection
Setup
3
RRC Connection
Setup Complete
4
NAS Attach
Service Request
Required
Conditional
Data
UE-initiated Service Request procedure(2 of 2)
PDN
UE eNB 5 MME SGW PGW HSS PCRF

Initial Context
6 Setup
RRC Connection
Reconfiguration
7
RRC Connection
Reconfiguration
Complete 8
Initial context
setup response
UE can begin
sending UL
Traffic 9
Modify Bearer
Request
10
Modify Bearer Required
Response
Conditional
SGW can send DL Traffic to UE Data
Before UE-initiated Service Request
eUTRAN EPC
HSS/EIR
MME
S6a/S13
S10
eNodeB
S11
SGW PGW
S1-MME
S5 SGi
PDN
PCRF Gx
Sh/LDAP
User
Control
After UE-initiated Service Request
eUTRAN EPC
HSS/EIR
MME
S6a/S13
S10
eNodeB
S11
OFDMA
SGW PGW
S1-MME
SC-FDMA S5 SGi
PDN
PCRF Gx
Sh/LDAP
User
Control
Network-triggered Service Request procedure
PDN

Incoming user
data is received
from network
1
Incoming user
data
2
Downlink Data
Notification &
Acknowledge
3
Paging
4
Paging
Required
Conditional
UE-Initiated Service request
Data
Before Network-triggered Service Request
eUTRAN EPC
HSS/EIR
MME
S6a/S13
S10
eNodeB
S11
SGW PGW
S1-MME
S5 SGi
PDN
PCRF Gx
Sh/LDAP
User
Control
After Network-triggered Service Request
eUTRAN EPC
HSS/EIR
MME
S6a/S13
S10
eNodeB
S11
OFDMA
SGW PGW
S1-MME
SC-FDMA S5 SGi
PDN
PCRF Gx
Sh/LDAP
User
Control
PROPERTIES

6 Detach procedures
6 Detach Procedure
Detach procedures
● Detach procedures allow
 The UE to inform the network that it no longer wants access to the EPS
 The network to inform the UE that it no longer has access to the EPS
● Initiated by
 UE
 MME
 HSS
● As a result of a Detach procedure

 EPS bearers are deleted
 UE signaling connection with the eNodeB and MME for that UE is released
(using the S1 Release procedure)
 IP address on the UE is released
● The UE detach is either
 Explicit – The network or the UE explicitly requests detach, and signal
with each other.
 Implicit - The network detaches the UE, without notifying the UE.
6 Detach Procedure
UE-Initiated Detach procedure
PDN
UE eNB MME SGW PGW PCRF

1
Detach request 2
Detach request
3
Delete session 4
request Delete session
5
request
CC Request/CC
6 Answer
7 Delete session
Delete session response
8 response
9 Detach accept
Detach accept
10
S1 UE Context
Release
11 Command
RRC Connection
12 Required
Release S1 UE Context Conditional
Release
Data
Complete
6 Detach Procedure
MME-Initiated Detach procedure
PDN
UE eNB 1 MME SGW PGW PCRF

2 Detach request
Detach request
3
Delete session 4
5
request
CC Request/CC
6 Answer
7 Delete session
8
response
Detach accept 9
Detach accept
10
S1 UE Context
Release
11 Command
RRC Connection
12 Required
Release
Data
Complete
6 Detach Procedure
HSS-Initiated Detach procedure
PDN

1
2 Cancel Location
3 Detach request
Detach request 4
Delete session 5
6
request
CC Request/CC
7 Answer
8 Delete session
9
response
Detach accept 10
Detach accept
11
12 Cancel Location
S1 UE Context Ack
Release
13 Command
RRC Connection
14 Required
Release Data
Complete
7 Intra-eUTRAN Handover procedures
7 Intra-eUTRAN Handover Procedures
Intra-eUTRAN Handover procedures
● Intra-eUTRAN Handover procedures involve the handover of the UE

from a source eNodeB to a target eNodeB
 This module’s examples are based on the availability of a single MME and
a single SGW
● Packet forwarding can take place from the source eNodeB to the
target eNodeB in two ways:
 X2-based handover (Directly)
 S1-based handover (Indirectly), when X2-based handover cannot be used
In scenarios where pooling is supported, there are variations in the X2-based

handover procedure based on the MME’s determination that the SGW is
relocated. Refer to 3GPP TS 23.401.
X2-based Handover (1 of 3)
PDN
Source Target
UE eNB eNB MME SGW PGW
UL and DL payload data
Decision to
perform
X2-based HO
1
Handover
Request
Admission
2
control
3
Handover Request
4 Acknowledge
RRC Connection
Reconfiguration
Source eNB
detach; sync to 5
target eNB Required
Buffered and in-
transit packets Conditional
6
delivered Source Data
to Target (X2)
PDN
Source Target
7
SN Status
transfer
Direct forwarding
of DL data
8
RRC Connection
Reconfiguration
Complete
DL forwarded data
UL payload data
9
Path Switch
Request 10
Required
User Plane Conditional
Update Request Data
PDN
Source Target
Switch DL
11
data path
End marker packets sent
DL payload data
12
Update User
Plane Response
End marker
13
Path Switch
Request
14 Acknowledge
UE Context
15 Release
TAU initiated
when Required
conditions Conditional
apply Data
Before X2-based Handover
eUTRAN EPC
MME HSS/EIR
Source
S6a/S13
eNodeB S10
OFDMA
S1-MME S11
SGW PGW
SC-FDMA
S1-U S5 SGi
PDN
X2
PCRF
Gx
Sh/LDAP
Target
eNodeB
User
Control
S1-MME
During X2-based Handover
eUTRAN EPC
9471 MME HSS/EIR
Source
S6a/S13
eNodeB S10
S1-MME S11
SGW PGW
S1-U S5 SGi
PDN
Down
X2 Link
PCRF
Gx
OFDMA
Down Sh/LDAP
Link
SC-FDMA
Target
eNodeB
User
Control
S1-MME
S1-U
Up
Link
After X2-based Handover
eUTRAN EPC
9471 MME HSS/EIR
Source
S6a/S13
eNodeB S10
S1-MME S11
SGW PGW
S1-U S5 SGi
PDN
X2
PCRF
Gx
OFDMA
Sh/LDAP
SC-FDMA
Target
eNodeB
User
Control
S1-MME
S1-U
S1-based Handover, no relocation of EPC NEs (1 of 3)
PDN
Source Target
UL and DL payload data
Decision to
perform
S1-based HO
1
Handover
Required
message 2
Handover Request
3 Admission
control
4
Handover Request
5
Acknowledge
Create Indirect
Data Forwarding
6 Tunnel Request &
Response
Handover
7 Command Required
Conditional
RRC Connection
Data
Reconfiguration
PDN
Source Target
Detach from
8
Source eNB
Buffered and in-
9 transit packets
delivered Source
to Target (S1-U)
10
eNB status
transfer
11
MME status
transfer
Indirect forwarding
of DL data
12 DL forwarded Required
RRC Connection data Conditional
Reconfiguration
Data
Complete
DL forwarded data
UL payload data
PDN
Source Target
13
Handover Notify
message 14
Modify Bearer
Request
Switch DL
15
data Path
End marker
packets sent
16
Modify Bearer
Response
DL payload
data
TAU initiated
when 17 18
conditions
apply UE Context Release 19 Required
Command/Complete Conditional
Delete Session
Request/ Data
Response
Before S1-based Handover (no relocation of EPC NEs)
eUTRAN EPC
9471 MME HSS/EIR
Source
S6a/S13
eNodeB S10
OFDMA
S1-MME S11
SGW PGW
SC-FDMA
S1-U S5 SGi
PDN
X2
PCRF
Gx
Sh/LDAP
Target
eNodeB
User
Control
S1-MME
During S1-based Handover (no relocation of EPC NEs)
eUTRAN EPC
9471 MME HSS/EIR
Source
S6a/S13
eNodeB S10
OFDMA
S1-MME S11
SGW PGW
SC-FDMA
S1-U S5 SGi
PDN
X2
PCRF
Gx
Sh/LDAP
Target
eNodeB
User
Control
S1-MME
S1-U
After S1-based Handover (no relocation of EPC NEs)
eUTRAN EPC
9471 MME HSS/EIR
Source
S6a/S13
eNodeB S10
S1-MME S11
SGW PGW
S1-U S5 SGi
PDN
X2
PCRF
Gx
OFDMA
Sh/LDAP
SC-FDMA
Target
eNodeB
User
Control
S1-MME
S1-U
S1-based Handover, with SGW relocation (1 of 3)
PDN
UE Source Target MME Source Target

eNB eNB SGW SGW PGW
Decision to perform
S1-based HO
1
Handover Required message 2
Create Session
3 Req. / Resp.
Handover Req.
4 Admission
control
Handover Req.
5 6
Acknowledge
Create Indirect Data
Forwarding Tunnel Req/ Resp
7
Create Indirect Data
9 Handover Command 8 Forwarding Tunnel Req/ Resp
RRC Connection
Reconfiguration
Required
UE detaches from Source eNB, & attaches to Conditional
10
Target eNB. Buffered and in-transit packets
Data
are delivered from Source eNB to Target eNB.
PDN

eNB eNB SGW SGW PGW
11 eNB status transfer
MME status 12
transfer
Indirect forwarding of downlink data
13 Indirect forwarding of downlink data
RRC Connection
Reconfiguration Complete
DL forwarded data
UL payload data
14 Handover Notify 15
Modify Bearer Request
16
Modify Bearer
17
Request / Response
Modify Bearer Response
Downlink data
18 TAU initiated when conditions apply

PDN

eNB eNB SGW SGW PGW
19 Delete Session
Request
UE Context Release
20
Command
21 UE Context Release
Complete
Delete Session
22
Response
23 Delete Indirect Data Forwarding Request
Delete Indirect Data Forwarding Response 24
25 Delete Indirect Data Forwarding Request
Delete Indirect Data Forwarding Response 26
Required
Conditional
Data
8 LTE-CDMA Interworking/CSFB
8 LTE-CDMA Interworking / CSFB
LTE-eHRPD/1x mobility procedures
Data mobility
Non-optimized Handover (HO)
 LTE to eHRPD active mode HO
 LTE to eHRPD idle mode HO
 eHRPD to LTE idle mode HO
 “Enhanced” Non-optimized HO allows limited context to be retained in the HSGW and the UE
Voice mobility
Dual transceiver (DTR) handset
 Uses circuit-switched network for voice and short message service (SMS)
 Uses LTE for data connections
 UE is dual registered, listens to both page channels over the air
Data mobility: eHRPD to LTE idle mode handover (1 of 3) +
User plane path before HO to LTE

User plane path after HO to LTE S6a/S13
HSS/
EIR
Sh SWx
MME S10
VoIP Services
Rx (CSCFs, E-CSCF,
PCRF TAS,SMS AS,MRF,
MGCF/MGW)
S11
S1-MME Gx SGi
LTE Gxa
eNB SGW PGW 3GPP

S1u S5 AAA
LTE-eHRPD
Dual S2a
Mode UE E-UTRAN
eHRPD PGW acts STa
as the mobility
anchor.
A10/A11
eBTS eRNC HSGW
eHRPD eHRPD-RAN 3GPP2

(e-AN)
MSC
UE eNodeB e-AN HSGW MME SGW PGW HSS PCRF
UE discovers LTE access system

and decides to handover to LTE.
1 RRC UL Information Transfer (attach type=HO)

S1 Initial UE Message (NAS Attach request)
2
Access and User Authentication
IP Address of eHRPD PGW Location Update and Subscriber Data Retrieval from HSS
Create Session Request
3
Create Session Request

4
CC Request
5
CC Answer
6
Create Session Response
7
Create Session Response
8
Radio and Access Bearer Establishment
Modify Bearer Request
9
Modify Bearer Response

10
UE eNodeB e-AN HSGW MME SGW PGW HSS PCRF
PDN Initiated eHRPD

resource release
PMIP-Binding Revocation Indication

11
PMIP-Binding Revocation Acknowledgement

12
A11 – Registration Update

13
A11 – Registration Acknowledge

14
A11 – Registration Request (lifetime = 0)

15
A11 – Registration Reply

16
The HSGW may clear all UE session context or the HSGW may start the UE
Context Maintenance timer to retain limited context for a period of time. UE
Context Maintenance Timer is provisionable at HSGW.
Voice mobility: CSFB / CS MT Call with LTE suspension (2 of 2) +
MME sends UE Context

Release command to eNodeB.
UE moves to 1xRTT.
7 6 UE context sub-state = SGW suspended.
MME
LTE
UE CONTEXT 5 Suspend DL Notification.
RELEASE 3
Request Resume notification, resume bearers, clear SGW
UE sends TAU to MME UE CONTEXT 9
suspended sub-state.
to resume LTE 4 MODIFICATION S11
service. Request
S1-MME
8 eNB SGW PGW
S1u S5
Extended Service
Request to MME. S2a
2 E-UTRAN
DTR UE
1
UE connected in A10/A11
eUTRAN receives a eBTS eRNC HSGW
page for an
incoming CS voice
call.
eHRPD
eHRPD-RAN 3GPP2
(e-AN)
MSC
9 LTE-WCDMA (UTRAN/GERAN) Interworking/CSFB
9 LTE-WCDMA (UTRAN/GERAN) interworking/CSFB
UMTS/GSM and LTE interworking options
 Mobility in idle mode

 Cell reselections
 Allows idle UE to reselect 2G, 3G, or LTE cell using “cell ranking” and “RAT
prioritization” measurements
 Mobility in active mode
 Cell reselections when UE is in GPRS packet transfer mode
 Cell redirections
 Pushes UE to, or from, LTE coverage
 PS handovers
 Handover packet switched services (with legacy core in Pre-Release 8 or
Release 8) when the UE is in active mode
 Voice call continuity
 Supports voice service continuity between 2G/3G and LTE
 Circuit Switched Fallback (CSFB) - Push UE to 2G/3G layer for CS services
 Single Radio Voice Call Continuity (SRVCC): voice call continuity from IMS voice
over packet-switched to circuit-switched (CS) voice
LTE-UMTS/GSM architecture
BTS BSC
(GERAN) (GERAN)
NodeB RNC Iu ps (UTRAN) Gn (pre-R8)

(UTRAN) (UTRAN) SGSN Gp (R8) GGSN
Gb (GERAN)
UTRAN/ Iu cs (UTRAN) S4 (S8) Gr
GERAN A (GERAN) (Indirect tuneling)
3GPP Gn (pre-R8) HSS/
MSC/VLR EIR
S3 (R8) Gn/Gp (pre-R8)
S6a/S13
S12 (R8) Sv Operator’s IP
SGs services
(Direct tuneling) (VoIP, IMS, etc)
S10
Rx
NAS MME PCRF
S1-MME
eNB
S11 SGi
E-UTRAN S1-U
S5 (MME home PGW)
SGW PGW
3GPP S8 (roaming UE PGW)
LTE-to-UMTS PS handovers with pre-Release 8 SGSN +
User plane path before and after HO
UTRAN
NB RNC
Iub SGSN
Iu-ps Pre-Rel. 8
HSS
GnS6a
(signaling)
Rx
MME PCRF Application
Function
S10
S1-mme S11
Gx
Gn (user)
E-UTRAN
S1u S5/S8 SGi
Data Services
eNB SGW PGW/GGSN (e.g., VPN, FTP)
Control plane
User plane
LTE-to-UMTS PS handovers with Release 8 SGSN and S3/S4 interfaces +
User plane path before and after HO

SGW acts as the local mobility anchor.
UTRAN
NB RNC
Iub SGSN
Iu-ps Rel. 8
HSS
• Data session S6a
handover S3
coordination
via the S3
Rx
S4 MME S10 PCRF Application
Function
S1-mme S11
Gx
E-UTRAN
S1u S5/S8 SGi
Data Services
eNB SGW PGW (e.g., VPN, FTP)
Control plane
User plane
IRAT Packet Switch Handover from eUTRAN to UTRAN (1 of 2)
UE eNodeB RNC MME SGSN SGW PGW
UE in ECM-
CONNECTED
state with
traffic 1
flowing in
both uplink eNodeB sends Handover
and downlink Required message to the MME
directions
2
MME initiates
resource allocation
3
SGSN makes resource
allocation request
4
RNC allocates
resources
5
SGSN returns the Forward Relocation
Response message to MME
MME sends PSHO command to the eNodeB

IRAT Packet Switch Handover from eUTRAN to UTRAN (2 of 2)
eNodeB RNC MME SGSN SGW PGW

UE
eNodeB requests the UE handover
UE detaches from the

eNodeB
8
eNodeB requests the handover to the
target UTRAN
Relocation complete message.
10
Relocation complete message.
11
Relocation complete acknowledgment.
User traffic is flowing in both uplink and downlink directions

Circuit-Switch Fall-back (CSFB)
Circuit Switch Fall Back over SGs
 For voice and other Circuit Switch domain services (SMS)
 Reuse of Circuit Switch infrastructure (3GPP TS 23.272)
 Use of GERAN or UTRAN to connect to the Circuit Switch domain
 Only available in case E-UTRAN coverage is overlapped by either GERAN coverage or
UTRAN coverage (voice service)
UE additional functions
 Supporting access to E-UTRAN/EPC as well as access to the CS domain over GERAN
and/or UTRAN
 Supporting combined procedures for EPS/IMSI attach, update and detach
MME additional functions
 Deriving a VLR number and LAI from the GUTI received from the UE or from a
default LAI
 Maintaining of SGs association towards MSC/VLR for EPS/IMSI attached UE
 Initiating IMSI detach at EPS detach
 Initiating specific paging procedure
 Supporting SMS procedures
CSFB – mobile terminating call in idle mode
UE eNodeB MME MSC/VLR GMSC
2 1
MME receives Paging Message sent to GMSC gets an IAM message from the
Request from MSC MSC/VLR network that a voice call is incoming
3
MME sends Paging
message to each
eNodeB
4
eNodeB pages UE
5
UE responds with
Extended Service
Request
6
MME sends a
request message
7
MME sends message
to eNodeB to move
UE to UTRAN
8
UE responds to the
eNodeB. IRAT mobility begins at this point.
10 Multiple PDN Connection procedures
10 Multiple PDN Connections procedure
Multiple PDN Connections procedure
● UE can support multiple applications and each application is

identified by individual Access Point Name (APN).
● UE can support multiple PDNs at the same time.
● To establish connectivity with a PDN when the UE is already
connected to one or more PDNs, the UE provides the requested APN
for the PGW selection function.
● One PGW can support multiple APNs or applications based on the
PGW address provisioned in HSS.
In scenarios where multiple PGWs are supported, UE supports multiple IP

addresses as each PGW allocates IP addresses on a per APN basis.
Multiple PDN Connections (1 of 2)
PDN PDN
New Existing
UE eNB MME SGW PGW HSS PCRF PGW
1
PDN
Connectivity
2
Request
Create Session 3
Request Create Session
Request 4
CC-Request /
5 CC-Answer
6 Create Session
7 Create Session Response
E-RAB Set-up Response
(w/Activate
Default EPS
8
Bearer Context
RRC Request)
Connection
Reconfiguration
Complete Required
9 Conditional
E-RAB Set-up Data
Response
Multiple PDN Connections (2 of 2)
PDN PDN
New Existing
UE eNB MME SGW PGW HSS PCRF PGW

10
UL Information
11
Transfer
UL NAS
Transport
Uplink Data
12
Modify Bearer
Request
13
Modify Bearer
Response
Downlink Data
14
Notify
Request Required
15 Conditional
Notify Answer Data
(Result)
End-to-End scenario revisited
One Saturday morning Ted gets up early to take a 10-mile bike ride
into the city and meet friends for coffee and a late-morning screening
of a new action movie. Before he heads out, Ted powers up his LTE
mobile device (4G UE), checks email, and puts the UE in his pocket.
Ted heads out and pedals towards the city. He leaves early, before his
family is awake at his house, to have time to stop by the lake and
enjoy the sun rise. By the lake, Ted enters a park. He parks his bike,
sits on a bench and sends a text message to his wife to say good
morning.
Ted heads out again towards the city. When he gets to the coffee shop
Ted is alerted to an incoming message; it’s his wife responding to his
earlier text message. After exchanging messages with his wife he
enters the coffee shop, orders coffee and a bagel, and sits with his
friends.
Before they all go to the theater Ted checks his e-mail and
views the film’s trailer via his wireless carrier’s video-on-
demand service. Inside the theater, Ted turns off his UE.
PROPERTIES

Module summary
This module presented the following common mobility management

procedures for the Evolved Packet System (EPS)
 Attach Procedure
 When the UE is authenticated, and its location in the network is identified
 S1 Release Procedure
 Release of a UE’s radio bearers, S1 bearers, and signaling resources from the eNodeB.
 Tracking Area Update Procedure
 Notifies the network of the availability of the UE
 Update the registration of the actual tracking area of the UE in the network
 Service Request Procedures
 Transfers the EMM mode of the UE/MME from ECM-IDLE to ECM-CONNECTED
 UE-initiated
 Network triggered
Module summary [Cont.]
 Detach Procedures
 The UE informs the network that it no longer wants access to the EPS
 The network informs the UE that it no longer has access to the EPS
 Intra-eUTRAN Handover Procedures
 The handover of the UE from a source eNodeB to a target eNodeB
 X2-based
 S1-based
 Without SGW relocation

 With SGW relocation
 IRAT HO and CSFB
 Multiple PDN connections
 UE support for multiple PDNs at the same time
End of module
Mobility Management Procedures
NokiaEDU
Section 1
Introduction
Module 4
EPC OAM
Technical Overview
© Nokia 2016
Module objectives
 Identify the EPC’s OAM interfaces

 Identify the interfaces used to facilitate EPC OAM functions
 Describe how to access the various OAM interfaces
 Describe the EPC management capabilities
 Configuration management
 Fault management
 Performance management
 Describe how network elements are discovered
 Describe how to access the Command Line Interface
Table of Contents
1 OAM Interfaces 7
2 EPC OAM Graphical User Interfaces (GUIs) 13
3 Management Capabilities 33
4 Configuration Management 38
5 Fault Management 44
6 Performance Management 51
7 Discovery Manager (5620 SAM) 57
8 Command Line Interface (CLI) 64
1 OAM Interfaces
1 OAM Interfaces
EPC OAM
● Nokia’s LTE solution provides an OAM infrastructure that supports

FCAPS:
 Fault Management – preventive and corrective maintenance
 Configuration Management – adding new components, customizing
 Accounting Management – subscriber billing
 Performance Management – efficiency of network elements
 Security Management – protecting the network
● OAM infrastructure covers internal OAM required to support each
LTE network element (NE) and its interfaces to the other LTE
network elements
1 OAM Interfaces
OAM Platform Interfaces
LIG X3
5620 SAM S6b 8950
STa AAA
EPC
X2/X3 X2 SWx IMS PDN
9471 8650 SDM –
MME 8950 SAM
S6a/S13 HSS/EIR Sh
S11
9412 Cx
S10
eNodeB VitalQIP 1300 XMC
DNS/ENUM
S101 7750 SR – 7750 SR –
S1-MME 7510
SGW PGW 5900 MGW Cx
MRF
LTE S1-U SGi
UE PDN PSTN
S5/S8
X2
9412 5020
eNodeB 5780 DSC – MGC-8
PCRF (MGCF)
Gx
1310
S1-MME Sh/LDAP OMC-P
5440
PCC S1-U 5450 5420
Gxa Rx+ ISC CTS
DNS/Mr
922X eHRPD
eBTS Isc
9271 8620 Rf/Ga Rf
eRNC SurePay
HSGW Rf/Gz User
A10/A11’ S103 Gy/Ro Rf Control
eHRPD S2A
OA&M
UE
8615 IeCCF Legal Intercept
Gray indicates
future interface
9253 9256
OMC-RAN OMP
1 OAM Interfaces
Northbound interfaces
NMS
Fault Configuration Accounting Performance Security
Management Management Management Management Management
JMS
SOAP-XML
5620 SAM
FM:
SNMPv2c
SNMPv3
FM: SNMPv3
CM: NETCONF/XML
9471 9412
PM: sftp XML
MME 5780 DSC eNodeB
7750 SR 7750 SR (PCRF)
(SGW) (PGW)
1 OAM Interfaces
5620 SAM Interfaces
OSS Application
Alarms/ Provisioning, inventory
Events set/get requests
JMS XML/ SOAP/ HTTP(S)
SNMP sets/ gets

EJB
CLI or SSH1/2
JMS FTP/ SCP

LTE
GUI Client SNMP traps Managed
JDBC/ TCP Network
Netconf
db
2 EPC OAM Graphical User Interfaces (GUIs)
EPC OAM GUIs
● Graphical User Interfaces used to access EPC equipment for OAM

functions include
 5620 SAM
 9471 WMM MI-Agent GUI
 8950 ID GUI (for 9471 WMM MME)
 5780 DSC PCRF GUI
5620 Service Aware Manager (SAM)
● The components of the EPC, and associated interfaces, along with the
IP transport, are monitored and administered via the 5620 SAM.
● The 5620 SAM
 Offers extensive use of open standards, such as:
 SOAP (Simple Object Access Protocol)
 XML (Extensible Markup Language)
 Java
 Enables network management at the
service and customer levels
 Provides fault management and
troubleshooting tools
LTE and transport components managed by the 5620 SAM
IP management of LTE network
Mobile
EPC 5620 SAM
PCRF
MME
eNodeB
PGW Cross-layer (domain)

coordination and
SGW management
Transport
7705 SAR 7705 SAR

7450 ESS
7710 SR
9500 MPR 9500 MPR 7710 SR
7210 SAS 7210 SAS 7750 SR

7750 SR
Mobile Backhaul IP/MPLS Aggregation Network Mobile Backbone
IP/MPLS
5620 SAM Graphical User Interface
● 5620 SAM Graphical User Interface runs on Client machines
● Used to provide FCAPS

Launch the 5620 SAM GUI
1. Click the 5620 SAM Client

App icon
2. Enter the Login Name

and Password
3. Click the Login button

Components of the 5620 SAM GUI
Menu bar
Tool bar
Navigation
tree labels
Working
pane
Dynamic
alarm list
Task bar
Status bar
5620 SAM GUI Workspace Customization Overview +
Menu bar Customize
Tool bar
Navigation Topology
tree labels icon labels
Window
layout
5620 SAM
GUI Client
Apply customized GUI workspaces created according to roles and responsibilities

Launch the MI-Agent GUI from 5620 SAM
To start the 9471 WMM MME MI-

Agent from the 5620 SAM:
Perform one of the following:
a. Right-click on the 9471 MME icon on
the physical topology map, choose
NE Sessions
b. Right-click on the 9471 MME NE in
the equipment tree, and choose
 NE Sessions, or
 Properties
2. Select Launch MI GUI
3. Enter the 9471 MME MI GUI login
and password
4. Click Connect
Note: For more information about configuring and using the MI-Agent, refer to the TMO21025,
9471 WMM MME OAM&P course.
Log in to the MI-Agent from a maintenance terminal
1. At a maintenance terminal, open an Internet Explorer® (IE) browser
and enter one of the two addresses:
 https://<MI Service floating IP address>:8443
 http://<MI Service floating IP address>:9090 (or http://<URL>:9090)
2. Click Web Start Client
3. In the login window, enter login and password.
4. Click Connect
All active pop-up blockers must be turned off in Internet Explorer.

NETCONF protocol and 9471 WMM MME provisioning
The NETCONF protocol (introduced in LE4.0) provides a mechanism to
install, manipulate, and delete the configuration of the 9471 WMM
MME applications from the 5620 SAM.
The local MME Provisioning GUI has been discontinued in LM5.0.
Network Configuration Protocol (NETCONF) is an IETF network

management protocol that provides mechanisms to install,
manipulate, and delete the configuration of network devices.
A NETCONF Request is sent from the 5620 SAM to the 9471 MME. The
5620 SAM receives a NETCONF Response from the MME.
5620 SAM
SNMPv3
ftp NETCONF
EML ssh
• For more NETCONF details, refer to the
NEL 5620 SAM EPC User Guide.
9471 MME • For MME configuration management details,
refer to 5620 SAM LTE Parameter
Reference
WMM Provisioning GUI from SAM
To access an WMM instance:
1. Select the MME in the Equipment Manager
2. From the main menu, select Manage > Mobile Core > WMM instances.
3. Select WMM then click properties.
Mobile/LTE Management
Equipment Management
MME form
NOTE: Prior to WM7.0.0, the WMM instance was called the "MME instance."
8950 ID® Identity GUI
● The 8950 ID GUI manages CLI and GUI user accounts across all diskful
and diskless blades.
● Administrator tasks include:
 Create, modify, or delete user accounts
 Lock or unlock user accounts
 Modify pre-login banner text and message of the day
● Users can perform the following tasks for their own accounts:
 Change password
 View account settings and permissions
 Upload SSH public keys
Note: If 8950 ID Identity GUI becomes inaccessible:

• The CLI can be used for the emergency access
• Passwords can be changed from the MI-Agent GUI or the CLI
Log into the 8950 ID GUI
1. At a maintenance terminal, open an IE browser and enter one of the

two addresses :
 https://<MI Service floating IP address>:8443
 http://<MI Service floating IP address>:80
2. In the login window, enter user ID and password
5780 DSC PCRF GUI
 The 5780 DSC provides a web-based GUI that simplifies the
configuration and management of the PCRF rules to meet specific
network requirements.
 This includes the creation and management of the following the PCRF
rule elements:
 Rules
 Rule tables
 Rule sets
 Rule definitions
 QoS rule definitions
 Charging rule definitions
 Internal SPR subscribers
 The 5780 DSC web-based GUI can also be used to
 list and track AF, IP CAN, and Gateway control sessions
 manage 5780 DSC equipment
For an overview of the specific features and functions that can be performed using the 5780 DSC
GUI refer to the 5780 DSC User Guide.
Launch the 5780 DSC GUI from 5620 SAM
To start the 5780 DSC GUI from the 5620 SAM:
1. Perform one of the following:
a. Right-click on the 5780 icon on the
physical topology map, choose NE
Sessions
b. Right-click on the 5780 DSC NE in the
equipment tree, choose NE Sessions
c. Open the Network Element (Edit) form
by right-clicking on the 5780 DSC NE in
the physical topology map or equipment
tree, and choose Properties.
2. Select Launch 5780 DSC Client
3. In the login window, enter the user
name and password
Log into the 5780 DSC PCRF GUI
1. At a maintenance terminal, open an Internet Explorer® browser and
enter: http://<5780 DSC IP address>/dsc/ui
2. In the login window, enter user name and password
3. Click on the Login button
3 Management Capabilities
EPC Element Management
 Using the 5620 SAM, most EPC devices can be
 Created
 Configured
 Managed
 The following table identifies the 5620 SAM management functions
for each of the Nokia LTE EPC network elements.
Equip- State Fault Config- Perfor- Discovery &

ment Uration Mance mediation
9471 MME      
7750 SGW      
7750 PGW      
5780 DSC    
PCRF
5620 SAM also provides management functions for eNodeB.

For more information, refer to the 5620 SAM LTE RAN User Guide.
7750 SR (SGW or PGW) support by 5620 SAM
 The 5620 SAM supports the discovery and management of the 7750 SR,
which can be configured as an SGW or PGW in the EPC.
 The 5620 SAM is used to configure, view and manage the following:
 chassis and shelf
 card slots, cards, and MDAs
 ISA-MG groups
 mobility regions
 one SGW or PGW instance per 7750 MG
 control bearer reference points, such as S1-u, S11, S5/S8, GA, and Gx
 gateway interface and application functions
 Policies and profiles
 status, statistics, and state management of faults associated with bearer
paths and peers
 alarms and fault management
 performance management data
9471 WMM MME support by 5620 SAM
 The 5620 SAM supports discovery and management of the 9471 WMM
MME chassis.
 The 9471 WMM MME device parameters can be configured via the 5620
SAM GUI, or the MI-Agent GUI that run on the 9471 WMM MME.
 Use the 5620 SAM to view the following:
 card slots and cards, including OAM, MME Interface Function, MME
Application Function, shelf management, and hub cards
 MME Interface Function and MME Application Function hosts and services
 card redundancy
 performance management data and statistics
More information on 9471 MME
Training TMO21024 – EPC 9471 MME Technical Overview
TMO21025 – EPC 9471 MME OAM&P
Documentation 9YZ-06010-0001-DEZZA - 9471 MME Technical Description manual
5780 DSC PCRF support by 5620 SAM
 The 5620 SAM supports the discovery and management of the 5780
DSC.
 The 5780 DSC GUI can be started from the 5620 SAM.
 Use the 5620 SAM to view
 card slots ad cards
 card redundancy
 geo-redundant nodes
Configuration management for the 5780 DSC is performed from the 5780 DSC GUI
that runs on the 5780 DSC platforms.
4 Configuration Management
7750 SR SGW & PGW Configuration
 The Nokia 7750 SR

 Can be configured as an SGW or PGW
 Supports an MG-ISM (Mobile Gateway – Integrated Services Module) card that
provides SGW and PGW functionality
 The MG-ISM card is an integrated card with no removable physical MDA cards
 When an MG-ISM card is configured, an MG-ISM daughter card with a
virtual port is also logically modeled and automatically configured.
 Entities to configure for an SGW and PGW include:
 Card slots and cards
 Daughter
. cards
 Physical Ports
 Physical links
 ISA-MG groups
 ISA-AA groups
For the detailed steps of the configuration procedures, refer to the 5620 SAM LTE EPC User Guide.
9471 WMM MME configuration
Configuration management
Provisioning commands are sent to the 9471
WMM MME using the NETCONF protocol.
5620 SAM users can:
 Set up communication and management policies
for the MME.
 View and modify MME application parameters. 5620
 Examples: Paging policy, MME pools, interfaces SAM
SNMPv3
 Perform bulk provisioning. Examples: NETCONF Web-enabled
User Interface,
 MME pool growth SCP/FTP/sFTP CLI
SSH, https
 Tracking areas
 Critical Performance Indicators (CPIs) 9471 WMM MME
 Diameter profile
OAM Server
 Emergency number list
 Perform load re-balancing by redistributing the
UEs between MMEs or within an MME
9471 WMM MME configuration management by MI-Agent
● Configuration management functions provided by the MI-Agent include

 Hardware discovery, audit, state management
 Software management: backup, restore, software update
 Provision northbound interface to EMS (5620 SAM)
 Manage growth and degrowth
 Provision interfaces
5780 DSC PCRF configuration
 Configuration management for the 5780 DSC is performed by the 5780

DSC GUI that runs on the 5780 DSC platforms.
 The following is a list of tasks that are associated with configuring and
managing 5780 DSC policies
 Create / Modify a PCRF rule definition
 Create / Modify a PCRF rule table and rules
 Modify a rule set
 Create / Modify a PCRF QoS rule definition
 Create / Modify a PCRF charging rule definition
 The following is a list of tasks that are associated with configuring an
SPR Subscriber
 Create and configure an SPR Subscriber
 Change the configuration settings for an SPR Subscriber
SPR Subscribers are the individual end-users of network services. Each Subscriber is configured with a
user ID and a category. Subscribers can also be configured with one or more subscription IDs and APNs.
These parameters are used by the 5780 DSC as matching conditions to apply a specific rule to the
Subscriber account.
5 Fault Management
5 Fault Management
EPC fault management
 The 5620 SAM converts SNMP traps from network elements and 5620
SAM events into alarms that are associated with the
 Managed equipment
 Configured services
 Policies
 The alarm-based fault management system provides the following
 Correlation of alarms with equipment- and service-affecting faults
 Updates to the managed-object operational status in near-real-time
 Alarm policy control that allows a network administrator to specify how to
process alarms, and how to create and store the alarm logs
 Point-and-click alarm management using the 5620 SAM GUI dynamic alarm
list and object properties forms
 Ability to log the actions taken to correct the associated fault by adding
notes to the alarm
 Alarm history for performing trend analysis
5 Fault Management
7750 SGW & PGW fault management
 The 5620 SAM supports LTE-specific traps that are generated by the MG-ISM
card on the SGW and PGW
 Alarm status of the SGW and PGW are represented in the 5620 SAM
 Equipment tree, and
 Network topology map
 SGW and PGW alarms are limited to status alarms for the gateway instances.
 There are also status-related notifications for the EPS peers, which are
propagated to the EPS paths.
Term Definition & example

EPS peers Neighboring nodes that are endpoints to an EPS path
Ex: SGW & PGW, as they are each an endpoint to the S5 path
EPS paths A point-to-point connection between LTE nodes that is used for bearer
control
Ex: S5 interface between SGW & PGW
For a description of the alarms that the 5620 SAM can raise, refer to the 5620 SAM LTE User Guide,
Appendix A.
5 Fault Management
9471 WMM MME fault management
● The MI-Agent is the primary means of fault detection and isolation for
the 9471 WMM MME.
● The 9471 MME raises an alarm and sends to the 5620 SAM a trap
containing all the alarm details.
● The 5620 SAM raises a corresponding alarm and displays the data in the
5620 SAM alarm subsystem.
● Properties of the 9471 WMM MME alarm can be viewed by clicking on
the alarm in the 5620 SAM Alarm Window.
● Data about the specified alarm can be viewed in the Alarm Info
Window.
● Most 9471 WMM MME alarms are designed to automatically clear.
Note: Known 9471 MME alarms are prefixed in the 5620 SAM with “Mme” so they can be distinguished
from 5620 SAM-generated alarms.
5 Fault Management
5780 DSC PCRF fault management
 The 5780 DSC provides alarms and triggers from an equipment
perspective, as well as a process and operational threshold
perspective.
Equipment alarms:
The ATCA platform provides alarms related to the status changes in the hardware
equipment.
Service alarms:
Alarms associated with the status and conditions associated with any of the
services (OAM, DPA or PCRF processing modules) are reported.
Performance threshold alarms:
For each of the performance counters, a provisioned threshold is specified. If the
threshold is crossed, the 5780 DSC sends a trap to each IP address that is
provisioned for the 5620 SAM to notify the 5620 SAM about the occurrence of an
event.
6 Performance Management
Performance Management
● The performance management (PM) process is used to schedule,
retrieve and analyze statistical data for equipment, services, and
network elements to:
 Monitor effectiveness of the system
 Correct problems
 Assist in planning, provisioning, and maintenance
● Statistical data is collected in the form of performance measurements
and can be forwarded to an upstream system for analysis.
● When a threshold is surpassed, data is analyzed at the network
elements to determine if an alarm should be raised (or cleared).
7750 SGW & PGW performance management
● Performance management counters are collected from the SGW and
PGW for
 MG-ISM card
 EPS peers
 The 5620 SAM records SGW and PGW counters as 7750-MG statistics
● Collected statistics are viewed on the 5620 SAM’s Statistics tab on the
Properties form
For more information about performance management can be found in the 5620 SAM Statistics
Management Guide document.
9471 MME performance management
The 9471 MME collects performance management (PM) counters as part of
its routine operation.
PM counters are collected and stored in 3GPP-compliant XML files, which
are created and stored in the 9471 WMM MME HDD.
If the PMFileEvent flag is set, the 9471 WMM MME PM files can also be
retrieved via 5620 SAM .
The PM raw data is stored on SAM server under:
/opt/5620sam/lte/stats/<date>/mme/<IP address of the mme>
The XML file format is compliant with 3GPP TS 32.435 for performance management counter (PMC) file
contents. The XML file naming conventions are compliant with 3GPP TS 32.401 v5.5.0, Annex B.1.2.
5780 DSC PCRF performance management
 All operational and performance statistics generated by the 5780 DSC
are available through SNMP polling.
 The following list shows some of the operational and performance
statistics that are available.
 Equipment
 Interface/processing blade (per interface)
 Bearer event
 Rule event
 QoS event
For the detailed list of operational and performance statistics refer to the 5780 DSC Dynamic
Services Controller User Guide.
7 Discovery Manager (5620 SAM)
5620 SAM Discovery Manager
Adds discovered device

properties into the 5620 SAM
database
5620 SAM
DB
EPC
For more information about Discovery Management refer to the 5620 SAM User Guide.
Mediation policies and SNMP MIBs
Mediation:
● A 5620 SAM mediation policy defines the interval at which the 5620 SAM
polls NEs for SNMP management information base (MIB) configuration
changes.
 Use the Mediation and MIB Entry Policy forms to view the information in an
SNMP MIB.
 Use the 5620 SAM client GUI to list the contents of the device MIBs that the
current 5620 SAM system supports.
SNMP management:
● An SNMP manager controls and monitors the activities of network hosts
that use SNMP.
 get operation is used to obtain a value from an SNMP agent
 set operation is used to store a value in the agent
For more information and procedures for mediation and SNMP management refer to the Device
Discovery chapter in the 5620 SAM User Guide.
Discovery rules
● Use Discovery Manager to
 Create one or more discovery rules
 Choose a discovery rule
 Scan the network as specified by the rule
Rule elements
● Discovery rules contain rule elements.
● Rule elements specify which devices or subnets are to be included or
excluded from the discovery process.
● A discovery rule can contain more than one rule element.
 Example: one rule element can be configured to discover a subnet, and
another rule element can be configured to exclude specific IP addresses
from the subnet.
8 Command Line Interface (CLI)
Command Line Interface - CLI
● CLI commands can be used to access, configure and manage network
elements.
 Access to specific CLI commands is controlled by permissions/roles set by the
system administrator
 9471 WMM MME CLI commands
 Common commands are located in the 9YZ-05481-0002-REZZA, 9471 WMM MME
OA&M document.
 Examples:
 calltrc_cli: Invoked on the MME OAM Server to perform various call trace operations. The
supported operations are: start, stop, and query.
 pmSchedCli: Provides administration capabilities for the 9471 MME performance
measurements. It starts a shell where the user can schedule the required measurements.
 7750 SR-MG CLI commands
 Common commands are located in the “7750 SR OS Basic System Configuration
Guide”; Chapter: CLI Usage
 Examples:
 clear: Clears statistics for a specified entity or clears and resets the entity.
 display-config: Displays the system’s running configuration.
Note: The software name for the 7750 SR PGW and SGW will be “SR-OS-MG”. Separate user guides
are in development and will be available for GA. These guides will contain Media Gateway
specific CLI commands.
CLI access
● CLI commands can be used to access, configure and manage network
elements. CLI can be accessed from:
 5620 SAM Maintenance Terminal
 GUI access to Telnet session
 Maintenance Terminal (MT)
 On-site (serial port connection used for installation and debugging)
 Remote site (office laptop of desk top PC via Telnet or SSH-Secure SHell)
EPC
MT 5620 SAM
MME
MLS SGW
Service
MT Providers
LAN
PGW
MLS
Remote Sites
PCRF
On site
CLI Access – 5620 SAM
 Double-click the shortcut icon to log into the 5620 SAM GUI.
 Right click the 9471 MME that you want to access in the Equipment Manager
and select:
• NE Sessions > Telnet Session or SSH session
 Log in using the appropriate MME user login and password.
There are two WMM Shells:

1. Shell CLI
2. WMM-CLI
(type “wmm-cli” from Shell CLI
2
Note: Shell CLI capabilities will
be removed in a future release
CLI access – On-site
Maintenance Terminal (Laptop) on-site:
 Serial port connection used for installation and
debugging
 Plug into DB-9 cable between Laptop and NE*
CP port
 9471 MME Hub or Blade connector USB
(If Hub connection is used, Linux Red Hat with the port
ipmitool must be installed on the maintenance terminal
and CLI is accessed from MI GUI.)
 7750 SR CPM connecter
 If port is configured correctly prompt is
displayed
 Enter CLI commands to perform operations
CP port
 Documentation
 9471 Mobility Manager Entity Operation, Administration
and Maintenance (9YZ-05481-0002-REZZA)
- Procedure 2.3: Access CLI from the MI GUI
- Procedure 2.7: Access blade through a serial connection (CLI)
 7750 SR Installation Guide
- Installing the SF/CPM
- Establishing Router Connections
- Console Connection 9471 MME 7750 SR
Hub Blade CPM
*Note: Port must be initially configured on Laptop. Refer to documentation.
CLI access – Remote
● Maintenance Terminal remote site:
 LAN access
 MT must have access to secure LAN from remote site
 In most situations IPSec access to LAN will be required
 Start Telnet or SSH session
 IP address or DNS Name required
 Enter Login/Username and Password
 Perform CLI command operations
 9471 MME access will be via the Hub, Linux Red Hat with the ipmitool must be installed on
the maintenance terminal
 Documentation
 9471 WMM Mobility Manager Entity Operation, Administration
and Maintenance (9YZ-05481-0002-REZZA)
 Procedure 2-5: Access and terminate a hub SOL session
 Procedure 2-6: Access and terminate a blade SOL session
 7750 SR Installation Guide
- Installing the SF/CPM
- Establishing Router Connections
- Console Connection
Module summary
●This module presented the following EPC OAM topics

 OAM interfaces for the EPC
 GUI interfaces used to access each EPC network element
 EPC management capabilities, including
 Configuration management
 Fault management
 Performance management
 How network elements are discovered
 How to access Command Line Interfaces of EPC network elements
End of module
EPC OAM
Appendix A
LTE acronyms and abbreviations
TMO21026_V6.0-SG-EN-LR16.1-Edition 1
Copyright © 2016 Nokia. All rights reserved.
Page A:1
Numbers
1X CDMA2000 1X
1X RNC 1X Radio Network Controller
2G 2nd Generation (GSM, TDMA, IS95A)
3G 3rd Generation (CDMA2000, UMTS)
3GPP Third Generation Partnership Project
3GPP2 Third Generation Partnership Project 2
4G 4th Generation
A
AAA Authentication, Authorization, and Accounting
AAT Average Aggregate Throughput
ACK Acknowledgement
ACL Access Control List
ACLR Adjacent Channel Leakage Ratio
ADMF Administrative Function
AF Assured Forwarding
AF Application Function
AGW Access Gateway
aIMS Advances to IP Multimedia Services
AKA Authentication and Key Agreement
AM Acknowledge Mode
AMBR Aggregate Maximum Bit Rate
AM Access Manager
AM Accounting Management
AMC Advanced Mezzanine Card
AN Access Network
AN Access Node
ANDSF Access Network Discovery and Selection Function
ANR Automatic Neighbor Relationship
Page A:2
AP Application Processor
AP Application Protocol
APB Active Phone Book
APN Access Point Name
AR Access Router
AR Aggregation Router
ARP Allocation and Retention Priority
ARQ Automatic Repeat Request
AS Access Stratum
AS Application Server
ASN.1 Abstract Syntax Notation 1
ASN-GW Access Service Network Gateway
AT Access Terminal
ATCA Advanced Telecommunications Computing Architecture
ATCA-LCP Advanced Telecommunications Computing Architecture –
Liquid Cooling Package
AVP Attribute Value Pair
AWS Advanced Wireless Services
B
BCCH Broadcast Control Channel
BCH Broadcast Channel
BE Best Effort
BHCA Busy Hour Call Attempts
BHL Back Haul
BM Bearer Manager
BM-SC Broadcast-Multicast Service Center
B-PCF 1X RNC Blade PCF
BRC Baseband Resources Controller
BS (BTS) Base Station
BSR Base Station Router
BSC Base Station Controller
BTS (BS) Base Transceiver Station
Page A:3
C
CAC Call Admission Control
CALEA Communications Assistance for Law Enforcement Act
CAZAC Constant Amplitude Zero Auto-Correlation
CB Controller Board
CBC Cell Broadcasting Center
CC Content of Communication
CC Cumulative Counter
CCCH Common Control Channel
CCM Common Chassis Management
CDMA Code Division Multiple Access
CER Capabilities Exchange Request (Diameter Setup)
CFC Call Final Class
CFCQ Call Final Class Qualifier
C/I Carrier-to-Interference Power Ratio
CIM Circuit Interface Module
CLI Command Line Interface
CM Configuration Management
CMAS Commercial Mobile Alert System
CMC Connection Mobility Control
CMIP Client Mobile IP
CN Core Network
CNFG Configuration
CORBA Common Object Request Broker Architecture
CP Cyclic Prefix
C-plane Control Plane
CPRI Common Public Radio Interface
CPU Central Processing Unit
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
C-RNTI Cell RNTI
CS Circuit Switched
CSFB Circuit Switch Fall back
Page A:4
CTM-HSSPC Controller Turbo Mode - High Speed Serial Protocol
Controller (Xilinx IP)
CU Controller Unit
D
d2U Digital 2 Unit
d4U Digital 4 Unit
DCCH Dedicated Control Channel
DCI Downlink Control Information
DER Discrete Event Registration
DF Delivery Function
DHCP Dynamic Host Configuration Protocol
DL Downlink
DL-SCH Downlink Shared channel
DO CDMA Data Only
DNS Domain Name Server
DPH Data Protocol Handler
DPI Deep Packet Inspection
DRA Diameter Proxy Agent
DRA&PS Dynamic Resource Allocation & Packet Scheduling
DRB Data Radio Bearer carrying user plane data
DRX Discontinuous Reception
DS1 Digital Signal level 1 (1.544 Mbit/s)
DSC Dynamic Service Controller
DSCH Downlink Shared Channel
DSCP Differentiated Services Code Point
DTCH Dedicated Traffic Channel
DTR Dual Transceiver
DTX Discontinuous Transmission
DWR Device Watchdog Request (heartbeat)
E
E1 Standard European PCM link (2.048 Mbit/s)
eAT Evolved Access Terminal
Page A:5
EBI EPS Bearer ID
eBTS Enhanced Base Transceiver Station
ECM EPS Connection Management
E-DCH Enhanced Dedicated Channel
EDGE Enhanced Data rates for GSM Evolution
EF Expedited Forwarding
eHRPD Evolved High Rate Packet Data
EIR Equipment Identity Register
ELP ECP Location Services Protocol
EML Element Management Level
EMM EPS Mobility Management
EMS Element Management System
eNodeB (eNB) Evolved NodeB
EPC Evolved Packet Core
ePDSN Evolved Packet Data Serving Node
EPS Evolved Packet System
eRNC Evolved Radio Network Controller
ESD Electrostatic Discharge
ESM Evolved Session Management
E-SMLC EPS Serving Mobile Location Center
eUTRAN Evolved Universal Terrestrial Radio Access Network
EVDO Evolution-Data Optimized or Evolution-Data Only
F
FA Foreign Agent
FBC Flow Based Charging
FCAPS Fault, Configuration, Accounting, Performance, and Security
FDD Frequency Division Duplex
FDM Frequency Division Multiplexing
FFS For Future Study
FM Fault Management
FRS Feature Requirements Specification
FRU Field Replaceable Unit
FQDN Fully Qualified Domain Name
Page A:6
FS Frame Selection
FTP File Transfer Protocol
G
GBR Guaranteed Bit Rate
GERAN GSM EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GMLC Gateway Mobile Location Center
GNSS Global Navigation Satellite System
GPRS General Packet Radio Service
GRE Generic Routing Encapsulation
GSM Global System for Mobile
GTP GPRS Tunneling Protocol
GTP-C GPRS Tunneling Protocol - Control
GTP-U GPRS Tunneling Protocol - User
GUI Graphical User Interface
GUMMEI Globally Unique MME Identifier
GUTI Globally Unique Temporary Identity
H
HA Home Agent
HARQ Hybrid ARQ
HO Handover
H-PCRF Home PCRF
H-PLMN Home PLMN
HRPD High Rate Packet Data
HSDPA High Speed Downlink Packet Access
HSGW HRPD Serving Gateway
HSPD High Speed Packet Data
HSPP High Speed Packet Processor
HSRP Hot Standby Router Protocol
HSS Home Subscriber Server
HSSL High Speed Serial Link
Page A:7
HSSPC High Speed Serial Protocol Controller
HW Hardware
I
ICIC Inter-Cell Interference Coordination
IE Information element
IETF Internet Engineering Task Force
IM Instant Messaging
IMEI International Mobile Equipment Identifier
IMS IP Multimedia Subsystems
IMSI International Mobile Station Identifier
IP Internet Protocol
IPBH Internet Protocol Back Haul
IPM IP Manager
IPMI Intelligent Platform Management Interface
IPSec Internet Protocol Security
I-RAT Inter-Radio Access Technology
IRI Intercept Related Information
ITU International Telecommunication Union
J
JMS Java Message Service
K
KPI Key Performance Indicator
L
L1 Layer 1
L2 Layer 2
L3 Layer 3
LA Location Area
LAI Location Area Identity
Page A:8
LB Load Balancing
LVI LVI Application Function
LBI Linked EPS Bearer Identity
LBO Local Break Out
LBS Location Based Service
LCID Logical Channel Identifier
LCP Linux Control Platform
LCR Low Chip Rate
LCS LoCation Services
LDAC Load Distribution and Access Control
LEA Law Enforcement Agency
LED Light-emitting Diode
LEMF Law Enforcement Monitoring Function
LI Lawful Interception
LIF LVI Interface Function
LMA Local Mobility Anchor
LMT Local Maintenance Terminal
LPP LTE Positioning Protocol
LR Location Request
LRF Location Retrieval Function
LSN Local Secure Network
LTE Long Term Evolution
LVI LTE Voice Interworking
M
MAC Medium Access Control
MAF MME Application Function
MAG Mobility Access Gateway
MBMS Multimedia Broadcast Multicast Service
Mbps Megabits per second
MBR Maximum Bit Rate
MCC Mobile Country Code
MCCH Multicast Control Channel
MCE Multicast Control Entity
Page A:9
MCM Media Conversion Module
MCS Modulation and Coding Scheme
MEI Mobile Equipment Identifier
META Mobile Evolution Transport Architecture
MGW Media Gateway
MI Management Interface
MIB Management Information Base
MIF MME Interface Function
MIMO Multiple Input Multiple Output
MIP Mobile Internet Protocol
MLS Multi-Layer Switch
MM Mobility Management
MME Mobility Management Entity
MMEC MME Code
MMEGI MME Group Id
MMEI MME Identifier
MNC Mobile Network Code
MO Mobile Origination
MO Managed Object
MPLS Multi-Protocol Label Switching
MSC Mobile Switching Center
MSIN Mobile Subscriber Identification Number
MT Mobile Termination
MTCH MBMS Traffic Channel
MTU Maximum Transmission Unit
MU Modem Unit
N
NACK Non-Acknowledgement
NAPTR Name Authority Pointer
NAS Non-Access Stratum
NBI Northbound Interface
NE Network Element (AGW or ENB)
NEL Network Element Level
Page A:10
NEM Network Element Manager
NML Network Management Level
NMS Network Management System
NSA National Security Agreement
NTP Network Time Protocol
O
OA&M (OAM) Operations, Administration, and Maintenance
OCAN Offline Configuration of Access Networks
OCS Online Charging System
OFCS Offline Charging System
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OMC Operations Management Centre
OMC-RAN Operations and Maintenance Center – Radio Access Network
OMP Operations and Management Platform
OOS Out of Service
OS Operating System
OSS Operations Support System
P
PA Power Amplifier
PAPR Peak-to-Average Power Ratio
PBCH Physical Broadcast Channel
PBR Prioritized Bit Rate
PCC Policy and Charging Control/Policy Control and Charging
PCCH Paging Control Channel
PCEF Policy and Charging Enforcement Function
PCFICH Physical Control Format Indicator Channel
PCI Physical Cell Identifier
PCMD Per Call Measurement Data
PCRF Policy and Charging Rules Function
PDCCH Physical Downlink Control Channel
Page A:11
PDCP Packet Data Context Protocol
PDN Packet Data Network
PDP Packet Data Protocol
PDSN Packet Data Serving Node
PDU Packet Data Unit
PEF Policy Enforcement Function
PEM Power Entry Module
PGW (P-GW) Packet Gateway (Packet Data Network Gateway)
PHICH Physical Hybrid ARQ Indicator Channel
PHY Physical layer
PIM Packet Interface Module
PLMN Public Land Mobile Network
PM Performance Management
PM Performance Measurements
PMC Performance Measurement Counter
PMIP Proxy Mobile IP
PO Processor Occupancy
PPP Point to Point Protocol
PRB Physical Resource Block
PS Packet Switched
PSAP Public Safety Answering Point
PSC Packet Scheduling
PSTN Public Switched Telephone Network
PTM-MC Point-to-Multipoint, Multi-Cell
PTM-SC Point-to-Multipoint, Single-Cell
Q
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QRM Quality and Reliability Measurements
Page A:12
R
RA Routing Area
RAC Radio Admission Control
RACH Random Access Channel
RA-RNTI Random Access RNTI
RAN Radio Access Network
RAT Radio Access Technology
RAU Routing Area Update
RB Radio Bearer
RBAC Role-Based Access Control
RBC Radio Bearer Control
RBP Rack Back Plane
RCC Reliable Cluster Computing
ReM Redundancy Manager
RF Radio Frequency
RFC Request For Comments
RLC Radio Link Control
RMT Remote Maintenance Terminal
RNC Radio Network Controller
RNL Radio Network Layer
RNTI Radio Network Temporary Identifier
R-OCM Reverse - Optical Control Module
ROHC Robust Header Compression
RQMS Reliability and Quality Measurements for
Telecommunications Systems
RRC Radio Resource Control
RRH Remote Radio Head
RRM Radio Resource Management
RTM Rear Transmission Module
RTT Radio Transmission Technology
RU Resource Unit
RUC Rack User Commissioning
RX Receive
Page A:13
S
S1-MME S1 for the control plane
S1-U S1 for the user plane
SACK SCTP Acknowledgement
SAE System Architecture Evolution
SAM Service Aware Manager
SAP Service Access Point
SAR Service Aggregation Router
SC-FDMA Single Carrier - Frequency Division Multiple Access
SCH Synchronization Channel
SCM System Control Module
SCP Secure Copy
SCTP Stream Control Transmission Protocol
SDF Service Data Flow
SDM Subscriber DB Manager
SDMA Spatial Division Multiple Access
SDU Service Data Unit
SFM Switch Fabric Module
SFN Single Frequency Network
sFTP Secure File Transfer Protocol
SGSN Serving GPRS Support Node
SGW (S-GW) Serving Gateway
SGW Signaling Gateway
ShMC Shelf Management Controller
SIP Session Initiation Protocol
SLOAM Slave Operation and Administration
SM Security Management
SM Session Management
SMC Security Mode Command
SMS Short Message Service
S-NAPTR Straightforward Name Authority Pointer
SNMP Simple Network Management Protocol
SNS Shared Network Services
Page A:14
SOAP Simple Object Access Protocol
SOL Serial Over LAN
SON Self-Organizing Network
SPR Subscription Profile Repository
SR Service Router
SRNS Serving Radio Network Subsystem
SRS Sounding Reference Signal
SRV DNS Service Record
SRVCC Single Radio Voice Call Continuity
SSH Secure Shell
S-TMSI S-Temporary Mobile Subscriber Identity
SU Scheduling Unit
SU Software Update
SW Software
T
TA Tracking Area
TAC Tracking Area Code
TAI Tracking Area Identity
TAS Telephony Application Server
TAU Tracking Area Update
TB Transport Block
TCP Transmission Control Protocol
TDD Time Division Duplex
TEID Tunnel Endpoint Identifier
TFT Traffic Flow Template
TIPC Transparent Inter Process Communication
TM Transparent Mode
TMN Telecommunication Management Network
TMSI Temporary Mobile Station Identity
TNL Transport Network Layer
TRDU Transmit Receive Duplex Unit
TTI Transmission Time Interval
TX Transmit
Page A:15
U
UDP User Datagram Protocol
UE User Equipment
UL Uplink
ULBO Uplink Buffer Occupancy
ULR Update Locate Request
UM Un-acknowledge Mode
UMB Ultra Mobile Broadband
UMTS Universal Mobile Telecommunications System
UPA User plane Application
U-plane User plane
USIM Universal Subscriber Identity Module
UTC Coordinated Universal Time
UTRAN Universal Terrestrial Radio Access Network
V
VCC Voice Call Continuity
VLAN Virtual Local Area Network
VLR Visitor Location Register
VoIMS Voice over IMS
VoIP Voice over IP
V-PCRF Visited PCRF
V-PLMN Visited PLMN
VRB Virtual Resource Block
VRRP Virtual Router Redundancy Protocol
W
WAP Wireless Access Protocol
W-CDMA Wideband Code Division Multiple Access
WiMAX Worldwide Interoperability for Microwave Access
Page A:16
X
X2-C X2-Control plane
X2-U X2-User plane
xCCM-U Extended Core Controller Module Unit
xCEM-U Extended Channel Element Module Unit
XML Extensible Markup Language
XMS Extended Management System
Page A:17
Page A:18
NokiaEDU
Section 1
Introduction
Module 6
Appendix B
Technical Overview
© Nokia 2016
1·1·1 COPYRIGHT © Nokia 2016. ALL RIGHTS RESERVED.
Technical Overview · Appendix B
Nokia LTE Evolved Packet Core (EPC) · Technical Overview
Blank page

References: Wireless Mobility Manager (WMM)
•9471 WMM 10.0

 Documentation
 9YZ-06832-0001-DEZZA: 9471 WMM Technical Description
 Provides reference information on software and hardware architecture, cabling, logical
functions and description of the high-level user interface
 9YZ-06832-0002-REZZA: 9471 WMM ATCA OA&M
9YZ-06832-0027-REZZA: HP 7000C OA&M
 Describes the concepts and procedures needed to perform OA&M on the MME
 9YZ-06832-0005-RKZZA : 9471 WMM Alarm Dictionary
 Provides information on interpreting MME alarms
 9YZ-06832-0006-RKZZA: 9471 WMM Observation Counters
 Describes the observation gauges and counters for the MME
 9YZ-06832-0008-RJZZA: 9471 WMM Site Preparation
 Describes and provides information on MME site preparation
Note: OLCS Website (Secure site requires Login and Password):

https://support.Nokia.com/portal/productIndex.do?range=9000-9999

References: Serving Gateway (SGW) & PDN Gateway (PGW)
•SGW & PGW: 7750 SR
 Documentation
 Basic System Configuration Guide
 Describes basic system configurations and operations
 System Management Guide
 Describes system security and access configurations as well as event logging and accounting logs
 Interface Configuration Guide
 Describes card, Media Dependent Adapter (MDA), and port provisioning
 Routing Protocols Guide
 Provides an overview of routing concepts and provides configuration examples for RIP, OSPF, IS-
IS, Multicast, BGP, Multicast, BGP, and route policies
 OS MPLS Guide
 Describes how to configure Multiprotocol Label Switching (MPLS) and Label Distribution Protocol
(LDP)
 Services Guide
 Describes how to configure service parameters such as service distribution points (SDPs),
customer information, and user services
 OAM and Diagnostic Guide
 Describes how to configure features such as service mirroring and Operations, Administration
and Management (OAM) tools
 Quality of Service Guide
 Describes how to configure Quality of Service (QoS) policy management
Note: For 7750 SR SGW/PGW specific information Release SR-OS-MG 5.0 R5 or later.
For 7750 SR common information Release SR-OS 11.0 R4 or later.
(Visit OLCS Website)

References: Policy and Charging Rules Function (PCRF)
•PCRF: 5780 DSC (PCRF)
 Documentation
 5780 DSC Release Description
 General information about the platform, product, compatibility requirements, network element compatibility of
the release, features and functions of the 5780 DSC
 5780 DSC User Guide
 An overall description of the 5780 DSC, including the core services and features, as well as the key benefits of
using the product, as well as how to access, configure and manage the 5780 DSC.
 5780 DSC Installation and Upgrade Guide
 Describes 5780 DSC software requirements and installation prerequisites, how to install the 5780 DSC for the
first time, and how to configure geo-redundant deployments.
 5780 DSC Policy Management Use Cases
 Use cases that demonstrate how the 5780 DSC provides flexible policy control and charging rules to address the
requirements of service providers.
 5780 DSC Integration Guide
 Information about 3GPP Gx, Gxx, and Rx and Sy Diameter interfaces supported by the 5780 DSC; and, 5780 DSC
compliance with the 3GPP PCC-related Release 7, 8, and 9 specifications
 5780 DSC Planning Guide
 Information required for, planning a successful deployment of the 5780 DSC including deployment scenarios, geo-
redundant configurations platform requirements & sizing considerations, etc..
 5780 DSC API Reference Manual
 Provides simplified APIs for the 5780 DSC to configure subscribers, provide types of billing identifiers, configure
metering limits, and specify QoS requirements for a flow.


References: Home Subscriber Server (HSS)
•HSS: 8650 SDM

 Documentation
 SDM HSS Mated Pair Management
 Describes mated pair configuration concepts and management and the HSS interface
 SDM HSS Management
 Explains how to manage the HSS from the 8650 SDM
 SDM HSS Spontaneous Messages
 Describes the spontaneous messages returned by the 8650 SDM concerning signaling software
with log type application errors
 SDM HSS Distributed Configuration Management
 Describes 8650 SDM configuration concepts and management and the HSS interface
 SDM HSS Alarms Dictionary
 Describes all the alarms raised by the 8650 SDM HSS
 SDM HSS Observation Counters Dictionary
 Describes the observation gauges and counters of the 8650 SDM HSS


References: Service Aware Manager (SAM)
•SAM: 5620 SAM
 Documentation
 5620 SAM LTE ePC User Guide
 Describes how to discover, configure, and manage ePC devices using the 5620 SAM
 5620 SAM LTE Parameter Reference
 Describes 9471 MME parameters related MME application provisioning.
 5620 SAM User Guide
 Provides task based workflows and user documentation on using the GUI, auto-discovery and administration,
configuration (NEs, QoS, services), performing fault management, collecting accounting and performance statics
 5620 SAM Statistics Management Guide
 Provides information collecting and viewing accounting and performance statistics
 5620 SAM Troubleshooting Guide
 Provides task based workflows to collect data to troubleshoot and resolve network and network management
issues
 5620 SAM System Architecture Guide
 Describes the system structure, software components, and interfaces
 5620 SAM Routine Maintenance Procedures Guide
 Provides procedures for generating baseline information and performing daily, weekly and monthly maintenance
activities
 5620 SAM Planning Guide
 Provides details on deployment, supported operating systems, hardware platforms, redundancy architecture,
network bandwidth req., scaling guidelines, etc.
Note: 5620 SAM Release 11.0 R5 or later.

OLCS Website (Secure site requires Login and Password):

End of module
Appendix B

NokiaEDU
Section 1
Introduction
Module 7
Appendix C
Technical Overview
© Nokia 2016
Technical Overview · EPC Interfaces, Protocols and Messages
NAS – Non-Access Stratum protocol
NAS protocol is used between User Equipment (UE) and the MME. It is
described in 3GPP Technical Specification 24.301.
 EPS Mobility Management (EMM):
 User location (tracking) and identity confidentiality
 Provide connection management services to Session Management (SM) sub layer
 EPS Session Management (ESM)
 User plane bearer:
· Activation
· Modification and
· Deactivation
 NAS Security
 Authentication/
authorization
 Keying distribution
General message organization for a Security protected NAS message

S1AP - S1 Application Protocol
S1AP protocol is used between the eNodeB and the MME. It is described in
3GPP Technical Specification 36.413.
 Primary functions
 Provide signaling service between eNB and EPC
 Non UE-associated services
· S1 interface management
· RAN information management
· RAN configuration transfer
 UE-associated services
· E-UTRAN Radio Access Bearer (E-RAB) management
· UE context management
· S1-based Handover
· Paging
· Location reporting

EPC interface protocols
Transport protocols
 UDP – User Datagram Protocol (RFC 768)
 TCP – Transmission Control Protocol (RFC 793)
 SCTP – Stream Control Transmission Protocol (RFC 2960)
3GPP specific protocols (EPC Interfaces)
 NAS – Non-Access Stratum Protocol (3GPP TS 24.301)
 S1AP – S1 Application Protocol (3GPP TS 36.413)
 GTP – GPRS (General Packet Radio Service) Tunneling Protocol (3GPP TS
29.060)
 Diameter – (3GPP TS 29.272)
Mobility management protocol
 PMIPv6 – Proxy Mobile Internet Protocol (RFC 5213)


GTP – GPRS Tunneling Protocol
GPRS Tunneling Protocol (GTP) is:
 A group of IP-based communication protocols used to carry General Packet
Radio Service (GPRS). The GTP protocol is layered on top of UDP. The uplink
and downlink service flows are sent via the tunnel.
 Used between SGW and PGW, SGW and MME, and SGW and eNodeB, as well as
between pooled MMEs. In interworking solutions, GTP is used between MME and
SGSN; between PGW and SGSN, and PGW and HSGW; and between SGW and
SGSN, and SGW and RNC.
 Described in 3GPP Technical Specification 29.274, 29.281 & 32.295.
Primary Functions
 GTP-C (control plane: TS 29.274)
 Path management
 Tunnel management
 Mobility management
 GTP-U (user plane: TS 29.281)
 Carry encapsulated T-PDUs and signalling messages between a given pair of
GTP-U Tunnel endpoints
 T-PDU – Transport-Protocol Data Unit
 GTP-U endpoints – eNodeB-to-SGW/SGW-to-PGW
 GTP1 (TS 32.295)
 Carries charging data from the Charging Data Function (CDF) of the GSM or
UMTS network to the Charging Gateway Function (CGF)

Diameter protocol
Diameter is a networking protocol used for authentication, authorization
and accounting (AAA), and is a successor to RADIUS.
Diameter controls communication between the authenticator and any
network element requesting authentication.
 Signaling between MME and HSS (TS 29.272)
 Insert/Delete subscriber data
 Authentication information retrieval
 Signaling between PGW and the PCRF (TS 29.212)
 Gx Application
 Credit Control Request /Answer
 Re-Auth Request (RAR)/ Re-Auth Answer (RAA)
 Signaling between PGW and AAA server (TS 23.402)
 Mobility authentication
 Update PGW address request


Proxy Mobile IPv6 (PMIPv6)
Proxy Mobile IPv6 protocol is intended for providing network-based IP
mobility management support to a mobile node, without requiring the
participation of the mobile node in any IP mobility related signaling.
The mobility entities in the network will track the mobile node's
movements and will initiate the mobility signaling and set up the required
routing state.
 Primary Function
 Signaling between PGW and HSGW (TS 23.402)


Interfaces per network solution
Regardless of LTE solution, the components of the EPC are the same, as
are most of the interfaces.
However, each interworking solution includes one or more additional
interfaces between EPC network elements and network elements located
in the existing 2G and 3G networks.
 Solutions
 LTE only
 LTE with CDMA interworking
 LTE with UMTS interworking
Additional interfaces are involved in roaming situations. Theses interfaces are

also identified and described in this section.

LTE only solution
eUTRAN EPC
8650 SDM -
9471 MME HSS/EIR
9412 eNodeB S10
S6a/S13
OFDMA
S1-MME S11
7750 SR-SGW 7750 SR-PGW
SC-FDMA
S1-U S5 SGi
PDN
X2
5780 DSC-PCRF
Gx
Sh/LDAP
9412
eNodeB
User
Control
S1-MME
S1-U
1 · 1 · 10 COPYRIGHT © Nokia 2016. ALL RIGHTS RESERVED.

EPC interfaces: MME
MME
Interface Network elements Solution
S1-MME eNodeB - MME All Solutions
S6a/S13 MME – HSS All Solutions
S10 MME – MME All Solutions
Gn/S3 MME – SGSN LTE w/UMTS
Sm MME – MBMS GW All Solutions
SLs MME – E-SMLC All Solutions
SLg MME – GMLC All Solutions
SBc MME – CBC All Solutions
M3 MME – eNB (MCE) All Solutions
SGs/Sv MME – 3G-MSC/VLR LTE w/UMTS
Red = User
Blue = Control

EPC interfaces: SGW
SGW
S1-u eNodeB – SGW All solutions
S4* SGW – SGSN LTE w/UMTS
S12 SGW - RNC LTE w/UMTS
Red = User
*Interface that carries both user and control plane data. Blue = Control

EPC interfaces: PGW
PGW
SGi PGW - PDN All Solutions
S6b PGW - AAA LTE w/UMTS,
LTE w/CDMA
S2a* PGW – HSGW LTE w/CDMA
Gn/Gp* PGW – SGSN LTE w/UMTS
Red = User
*Interface that carries both user and control plane data. Blue = Control

EPC interfaces: PCRF
PCRF
Gxa PCRF – HSGW LTE w/CDMA
Sh/LDAP PCRF - HSS All Solutions
S9 PCRF-PCRF All Solutions
Red = User
Blue = Control

LTE Uu (UE to eNB) and S1-MME (eNB-MME)
Both the LTE Uu and S1-MME interfaces carry the Non-Access Stratum
(NAS) messages between the UE and the MME. NAS messages pass through
the eNodeB unchanged.
All messages between eNB and MME use S1-AP. NAS messages are
encapsulated in S1-AP messages on the S1-MME interface.
 Protocol
 NAS
 NAS Messages:
 AUTHENTICATION REQUEST/RESPONSE UEs
/REJECT/FAILURE eNB MME
 SECURITY MODE COMMAND/COMPLETE/REJECT
LTE Uu S1-MME
 ATTACH REQUEST/ACCEPT/COMPLETE/REJECT
NAS NAS
 SESSION MANAGEMENT CONFIGURATION REQUEST
/ACCEPT/REJECT RRC RRC S1-AP S1-AP
 BEARER RESOURCE ALLOCATION REQUEST PDCP PDCP
SCTP SCTP
/REJECT RLC
RLC
 PDN CONNECTIVITY REQUEST/ACCEPT/REJECT IP IP
MAC MAC
 DETACH REQUEST/ACCEPT L2 L2
PHY PHY
 BEARER RESOURCE RELEASE REQUEST/REJECT L1 L1
Note: Not all NAS messages are listed. Refer to 3GPP TS 24.301 for complete list and descriptions.

S1-MME (eNodeB-MME)
Interface for the control plane protocol between eNodeB and MME. Used
to exchange information to control and set up the call.
In the S1-MME interface, SCTP stream 0 is for the eNB-MME signaling.
Stream 1 is for the UE-to-MME signaling (i.e. NAS)
 Protocols
 S1-AP (application layer)
 SCTP - Stream Control Transmission Protocol
eNB
 S1-AP messages
 S1 SETUP REQUEST/ RESPONSE/FAILURE
 INITIAL CONTEXT SETUP REQUEST/RESPONSE/FAILURE
 UE CONTEXT MODIFICATION REQUEST/RESPONSE
 UE CONTEXT RELEASE REQUEST/COMMAND/COMPLETE S1-MME MME
 E-RAB (eUTRAN-Radio Access Bearer) SETUP
REQUEST/RESPONSE S1-AP S1-AP
 E-RAB MODIFY REQUEST/RESPONSE SCTP SCTP
 E-RAB RELEASE COMMAND/RESPONSE IP IP
 eNB CONFIGURATION UPDATE ACKNOWLEDGE/FAILURE
 MME CONFIGURATION UPDATE ACKNOWLEDGE/FAILURE L2 L2
 RESET/RESET ACKNOWLEDGE L1 L1
Note: Not all S1-AP messages are listed. Refer to 3GPP TS 36.413 for complete list and descriptions.

S6a (MME-HSS)
Interface between MME and HSS or DRA that enables the transfer of
location information and subscriber related data used for authenticating,
authorizing and changing user access in the evolved system.
 Protocols
 Diameter
 SCTP
 Messages (Diameter)
 UPDATE LOCATION REQUEST/ANSWER
 CANCEL LOCATION REQUEST/ANSWER
MME S6a HSS or DRA
 AUTHENTICATION INFORMATION
REQUEST/ANSWER Diameter Diameter
 INSERT SUBSCRIBER DATA REQUEST/ANSWER SCTP SCTP

 DELETE SUBSCRIBER DATA REQUEST/ANSWER IP IP
 PURGE UE REQUEST/ANSWER L2 L2
 RESET REQUEST/ANSWER L1 L1
 NOTIFY REQUEST/ANSWER

S13 over S6a (MME-EIR)
Implements the connection from MME to the Equipment Identity Register

(EIR). The EIR enables the identity check of user equipment (as opposed
to the subscriber) between the MME and the EIR.
This interface is used to verify the status of the equipment in the event
of loss or theft.
When the EIR is integrated into the HSS, the S13 function is implemented
on the S6a interface, which uses the same protocol stack.
 Protocols
 Diameter
 SCTP
 Messages (Diameter) S13
MME S6a HSS/EIR
 ME-IDENTITY-CHECK-REQUEST (ECR)
Diameter Diameter
 ME-IDENTITY-CHECK-ANSWER (ECA)
SCTP/TCP SCTP/TCP
IP IP
L2 L2
L1 L1

S10 (MME-MMEs)
S10 is the control plane protocol interface between MMEs. It is used to
move the UE context from one MME to another in case of MME relocation.
 Protocols
 GTP-C
 UDP
 Messages
 IDENTIFICATION REQUEST/RESPONSE
 CONTEXT REQUEST/RESPONSE/ACKNOWLEDGE
 FORWARD RELOCATION REQUEST/RESPONSE
 FORWARD RELOCATION COMPLETE MME S10 MME
NOTIFICATION/ACKNOWLEDGE GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
The relocation of a MME may be required during intra-eUTRAN mobility procedures such as Tracking
Area Update (TAU) in IDLE mode with MME relocation, and S1 Handover with MME relocation.

S11 and S5: Control plane (Path Management)
The interfaces between MME and SGW (S11) and SGW and PGW (S5)
provide control of bearer establishment, modification, release, and
suspension. Path Management messages are sent between all GTP-C
entities.
 Protocols
 GTP-C (GPRS Tunneling Protocol-Control plane)
 Messages (GTP-C Path Management)
 VERSION NOT SUPPORTED INDICATION
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1

S11 and S5: Control plane (MME - SGW – PGW)
GTP-C tunnel management messages sent between the MME, SGW and
PGW (S11 and S5)
 Messages (GTP-C tunnel management)
 DELETE SESSION REQUEST/RESPONSE
 DELETE BEARER REQUEST/RESPONSE
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1

S11 and S5: Control plane (Various Messages)
A list of some of the other GTP-C messages sent between the MME, SGW
and/or PGW.
 Messages (GTP-C)
 DOWNLINK DATA NOTIFICATION/NOTIFICATION ACKNOWLEDGE
 DOWNLINK DATA FAILURE INDICATION
 UPDATE USER PLANE REQUEST/RESPONSE
 MODIFY BEARER COMMAND
 MODIFY BEARER FAILURE INDICATION
 UPDATE BEARER REQUEST/RESPONSE
 DELETE BEARER COMMAND
 DELETE BEARER FAILURE INDICATION
MME S11 HSS

SGW S5 PGW
GTP-C GTP-C GTP-C
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1

M3/Sm (MCE-MME-MBMS GW)
The M3 interface supports communication the Multicast Control Entity
(MCE) in the eNodeB nodes and the 9471 MME.
 MME transmits session control messages toward the MCEs using the M3
interface.
M3 includes the following protocols:
 M3-AP
eNB/MCE
M3 Sm (GTP-C)
MME MBMS GW
M3-AP M3-AP
SCTP SCTP
IP IP
L2 L2
L1 L1

SLs (MME-E-SMLC)
The SLs interface supports GMLC SLh
and the EPC Serving Mobile Location
SLg
Center (E-SMLC ) to obtain a UE's eNB
position. MME
S1-MME S6a
 Supports of Emergency Location Services
(LCS).
SLs
HSS
SLs includes the following protocols:
 LCS-AP E-SMLC
LCS-AP messages LCS-AP
SLs
LCS-AP
 LCS-AP Location Request message SCTP SCTP
 LCS-AP Location Response message IP IP
 LCS-AP Location Abort Request message L2 L2
 LCS-AP Connection Oriented Information message
L1 L1
 LCS-AP Connectionless Information message
E-SMLC
 LCS-AP Reset Request message MME
 LCS-AP Reset Acknowledge message

SLg (MME-GMLC)
The SLg interface supports GMLC SLh

and the Gateway Mobile Location Center (GMLC). SLg
eNB
 Transports positioning requests and
MME
responses for Location Services (LCS) S1-MME S6a
between GMLC and MME.
SLg includes the following protocols: SLs
HSS
 Diameter EPC LCS Protocol (ELP)

E-SMLC
ELP messages Diameter (ELP)
SLg
Diameter (ELP)
 Provide Location Request (PLR) SCTP SCTP
 Provide Location Answer (PLA) IP IP
 Location Report Request (LRR) L2 L2
 Location Report Answer (LRA) L1 L1
MME GMLC

SBc (CBC- MME)
The SBc interface supports eNB
communication between the 9471

S1-MME SBc
MME and the Cell Broadcast Center
(CBC). MME
CBC
 Transports messages associated with
Warning Message Delivery function.
SBc includes the following protocols:
 SBc-AP
 Single-homing or Multi-homing between MME and CBC is supported
 Multiple SCTP streams are supported
SBc
Warning Message Transmission messages SBc-AP SBc-AP
 WRITE-REPLACE WARNING REQUEST SCTP SCTP

IP IP
 WRITE-REPLACE WARNING RESPONSE
L2 L2
 STOP WARNING REQUEST
L1 L1
 STOP WARNING RESPONSE
MME CBC

S1-U (eNodeB – SGW) and S5 (SGW – PGW): User plane
User plane reference points between the eNodeB, SGW and PGW for the
per-bearer user plane tunneling.
 Protocols
 GTP-U – GPRS Tunneling Protocol-User plane
 Messages
eNB
HEADERS NOTIFICATION HSS
S1-U SGW S5 PGW
 G-PDU
GTP-U GTP-U GTP-U
 END MARKER
UDP UDP UDP
IP IP IP
L2 L2 L2
L1 L1 L1
Note: S1-U also used for inter-eNB path switching during hand over.
S5 is used for SGW relocation due to UE mobility and if the SGW needs to connect to a non-
collocated PGW for the required PDN connectivity.

SGi (PGW - PDN)
Interface between PGW and the Packet Data Network.
IP packets pass from the UE to the PGW and then over the SGi to the PDN
entity.
 Protocol
 IP
 IP Message
 IP PACKET
HSS
PDN
UEs SGW PGW
eNodeB
S1u S5 SGi
IP IP

Gx (PGW - PCRF)
Interface between PGW and the Policy and Charging Rule Function (PCRF).
It provides transfer of Policy and Charging Control (PCC) rules between
the PCRF to the Policy and Charging Enforcement Function (PCEF) in the
PGW.
 Protocol
 Diameter
 Messages
 Gx APPLICATION PCEF
 CREDIT CONTROL REQUEST/ANSWER
 RE-AUTHORIZATION REQUEST/ANSWER PGW
Gx
PCRF
Gx*
Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1
* The Gx reference point resides between the PCRF and the PCEF (3GPP TS 23.203)
located in the PGW. Gx protocol is described in 3GPP TS 23.402.

Sh (PCRF – HSS)
Sh is the reference point for PCRF* to obtain subscriber information from
an HSS that supports the Diameter protocol.
 Protocol
 Diameter
 Messages
 USER DATA REQUEST/ANSWER
 PROFILE UPDATE REQUEST/ANSWER
 SUBSCRIBE NOTIFICATION REQUEST/ANSWER
 PUSH NOTIFICATION REQUEST/ANSWER
PCRF Sh HSS
Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1
for rapid access.

LDAP (PCRF – HSS)
LDAP (Lightweight Directory Access Protocol) is the reference point for
PCRF* to obtain subscriber information from an HSS that supports LDAP.
 Protocol
 LDAP
 Messages
 BIND REQUEST/ RESPONSE
 UNBIND REQUEST
 SEARCH REQUEST
 SEARCH RESULT ENTRY / DONE / REFERENCE
PCRF LDAP HSS
 MODIFY REQUEST / RESPONSE
 ADD REQUEST / RESPONSE LDAP LDAP
 DEL REQUEST /RESPONSE TCP TCP
 MODIFY DN REQUEST / RESPONSE IP IP
 COMPARE REQUEST / RESPONSE L2 L2

 ABANDON REQUEST L1 L1
 EXTENDED REQUEST/ RESPONSE
for rapid access.


LTE with CDMA interworking solution
AAA
DNS
IMS PDN
LTE MME EPC S6b
HSS/EIR
eUTRAN SWx
S6a/S13
eNodeB S10
S1-MME S11
OFDMA
S102
SGW PGW MGW
SC- S101
FDMA S1-U S5/S8 SGi
PDN
PSTN
Gx
PCRF Sh/LDAP
CDMA eHRPD
eBTS eRNC User
Gxa Control
HSGW S103
Gray indicates future
interface in Nokia
network
S2a
3G1X MSC

LTE with UMTS interworking solution
3G-MSC/VLR GMSC
NodeB
UMTS/
GSM RNC or
BSC SGSN GGSN
Gn/Gp AAA
DNS Gn/Gp
S4 IMS PDN
LTE MME SGs/Sv EPC S6b
HSS/EIR
eUTRAN Gn/S3 SWx
S6a/S13
eNodeB S10
S1-MME S11
OFDMA
SGW PGW MGW

SC- S12
FDMA S1-U S5/S8 SGi
PDN PSTN
Gx
Gx
PCRF Sh/LDAP
User
Control

Interworking related interfaces
LTE with CDMA
S6b PGW - AAA
S2a* PGW – HSGW
Gxa PCRF - HSGW
LTE with UMTS

S6b PGW - AAA
Gn/S3 MME – SGSN
Gn/Gp* PGW - SGSN
SGs/Sv MME – 3G-MSC/VLR
S4* SGW - SGSN
S12 SGW - RNC *The Gn/Gp interface carries both user
and control plane data.

S6b (PGW - AAA)
Interface between PGW and the Authentication, Authorization and
Accounting (AAA) server proxy for mobility authentication, if needed.
May also be used to retrieve and request storage of mobility
parameters; and, to retrieve a static QoS profile for a UE for Non-3GPP
access if dynamic PCC is not supported.
 Protocol
 Diameter
 Messages
 UPDATE PDN GW ADDRESS REQUEST/ ACKNOWLEDGE
 DETACH INDICATION/ ACKNOWLEDGE
PGW S6b AAA

Diameter Diameter
SCTP/TCP SCTP/TCP
IP IP
L2 L2
L1 L1

S2a (PGW – HSGW): User plane
Interface that provides the user plane and related control and mobility
support between Trusted Non-3GPP IP access and the PGW.
 Protocol
 PMIPv6
 Messages
 PROXY BINDING UPDATE /ACKNOWLEDGEMENT
 BINDING REVOCATION INDICATION / ACKNOWLEDGEMENT
A10/A11 S2a
eHRPD HSGW PGW
eRNC HSS
IP PMIPv6 PMIPv6
IP IP IP
L2 L2 L2 L2
L1 L1 L1 L1

S2a (PGW – HSGW): Control plane
The figure below illustrates the S2a control plane.
 Protocol
 PMIPv6
 GRE
 Messages
 PROXY BINDING UPDATE REQUEST
 PROXY BINDING ACKNOWLEDGEMENT
 BINDING REVOCATION INDICATION /ACKNOWLEDGEMENT
A10/A11 S2a
eHRPD HSGW PGW
eRNC
PMIPv6 PMIPv6
IP IP
L2 L2 L2 L2
L1 L1 L1 L1

Gxa (PCRF – HSGW)
Interface that provides transfer of QoS policy information from the PCRF
to the Trusted Non-3GPP accesses.
 Protocol
 Diameter
 Messages
 CC-Request (CCR) Command
 CC-Answer (CCA) Command
 Re-Auth-Request (RAR) Command
PCRF Gxa HSGW

Diameter Diameter
TCP TCP
IP IP
L2 L2
L1 L1

Gn (MME – SGSN)
Interface for the control plane between the MME and the Pre-Release 8
SGSN. Gn allows the MME to affect handover between LTE and
UMTS/GERAN.
 Protocols
 GTP-C
 UDP
 Messages
 Mobility Management Message
Gn SGSN
MME
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1

S3 (MME – SGSN)
Interface for the control plane between the MME and the Release 8 or
later SGSN. Gn allows the MME to affect handover between LTE and
UMTS/GERAN.
 Protocols
 GTP-C
 UDP
 Messages
 DETACH NOTIFICATION/ ACKNOWLEDGE
 CS PAGING INDICATION
 ALERT MME NOTIFICATION / ACKNOWLEDGE
 UE ACTIVITY NOTIFICATION / ACKNOWLEDGE
S3 SGSN
MME
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1

Interface between the PGW and Gn/Gp SGSN (2G-SGSN or 3G-SGSN).
GTP (GTP-C, GTP-U and GTP1) is defined for the Gn interface, i.e. the
interface between GSNs within a PLMN, and for the Gp interface between
GSNs in different PLMNs.
 Protocol
 GTP-C
 Messages
SGSN
 Mobility Management Message PGW Gn/Gp
GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1
Note: Specific GTP-C messages are not listed. Refer to 3GPP TS 29.060 for a full list & descriptions.

In the user plane, GTP uses a tunnelling mechanism (GTP-U) to provide a
service for carrying user data packets.
 Protocol
 GTP-U
 Messages
 G-PDU
PGW Gn/Gp SGSN
GTP-U GTP-U
UDP UDP
IP IP
L2 L2
L1 L1

GTP1 is used to transfer charging data from the Charging Data Function to
the Charging Gateway Function.
 Protocol
 GTP1
 Messages
 ECHO REQUEST/REPSONSE
 VERSION NOT SUPPORTED
 NODE ALIVE REQUEST/REPSONSE
 REDIRECTION REQUEST/REPSONSE
 DATA RECORD TRANSFER REQUEST/REPSONSE
PGW Gn/Gp SGSN

GTP1 GTP1
UDP UDP
IP IP
L2 L2
L1 L1

SGs (MME – 3G-MSC/VLR)
Interface between the MME and the Visitor Location Register (VLR) used for the mobility
management and paging procedures between EPS and CS domain (with CS Fall Back
capability). SGs is also used for the delivery of mobile originating and mobile terminating
SMS over EUTRAN in case SMSIP is not used.
 Protocols
 Diameter
 SCTP/TCP
 Messages
 SGsAP-LOCATION-UPDATE-REQUEST/ACCEPT /REJECT
 SGsAP-TMSI-REALLOCATION-COMPLETE
SGs MSC Server
 SGsAP-PAGING-REQUEST/ REJECT MME
 SGsAP-SERVICE-REQUEST Diameter Diameter
 SGsAP-UE-UNREACHABLE SCTP/TCP SCTP/TCP
 SGsAP-UPLINK-UNITDATA
IP IP
 SGsAP-DOWNLINK-UNITDATA
L2 L2
 SGsAP-RELEASE-REQUEST
 SGsAP-EPS-DETACH-INDICATION/ ACK L1 L1
 SGsAP-ALERT-REQUEST/ ACK/ REJECT
 SGsAP-UE-ACTIVITY-INDICATION SGs used for CSFB (Circuit
Switch Fall Back)
 SGsAP-MM-INFORMATION-REQUEST
 SGsAP-RESET-INDICATION
 SGsAP-RESET-ACK
 SGsAP-STATUS
SV (MME – 3G-MSC/VLR)
Sv is a reference point between the MSC/VLR
and the 9471 MME:
 Allows MME to interact with the MSC to handover
IMS-anchored voice sessions from LTE to UMTS.
 Supports SRVCC, which provides IMS continuity
when the UE is a single radio.
Sv includes the following protocols:
SV MSC Server
 GTPv2-C MME
 Tunnels signaling messages between MME and MSC Diameter Diameter
 UDP/IPv4 or IPv6 SCTP/TCP SCTP/TCP
 Transfers signaling messages IP IP
Sv Messages L2 L2
 SRVCC PS to CS Request L1 L1
 SRVCC PS to CS Response
 SRVCC PS to CS Complete Notification SV used for SRVCC (Single Radio
 SRVCC PS to CS Complete Acknowledge Voive Call Continuity)
 SRVCC PS to CS Cancel Notification
 SRVCC PS to CS Cancel Acknowledge

S4 (SGW – SGSN): User plane
GGSN.
 Protocol
 GTP-U
 UDP
 Messages
 END MARKER SGW
S4 SGSN
UDP UDP
IP IP
L2 L2
L1 L1

S4 (SGW – SGSN): Control plane
GGSN.
 Protocol
 GTP-C
 UDP
 Messages
 CREATE FORWARDING TUNNEL REQUEST / RESPONSE
 CREATE INDIRECT DATA FORWARDING
 DELETE INDIRECT DATA FORWARDING S4 SGSN
SGW
 RELEASE ACCESS BEARERS REQUEST / RESPONSE GTP-C GTP-C
UDP UDP
IP IP
L2 L2
L1 L1

S12 (SGW – RNC)
Interface between UTRAN and SGW for user plane tunneling when Direct
Tunnel is established. It is based on the Iu-u/Gn-u reference point using
the GTP-U protocol as defined between SGSN and UTRAN or respectively
between SGSN and GGSN.
Usage of S12 is an operator configuration option.
 Protocol
 GTP-U
 UDP
 Messages
 END MARKER SGW
S12 RNC
UDP UDP
IP IP
L2 L2
L1 L1

Roaming-related interfaces
Interface Network
elements
S8* SGW – PGW
S9 V-PCRF – H-PCRF

S8 (SGW – PGW ): User Plane
 Protocol
 GTP-U
 UDP
 Messages
HEADERS NOTIFICATION
 G-PDU
 END MARKER
S8
SGW PGW
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1

S8 (SGW – PGW ): Control Plane
 Protocol
 GTP-C
 UDP
 Messages
 DELETE SESSION REQUEST/RESPONSE S8
 DELETE BEARER REQUEST/RESPONSE SGW PGW
GTP GTP
UDP UDP
IP IP
L2 L2
L1 L1

S9 (V-PCRF – H-PCRF )
Interface that provides transfer of QoS policy and charging control

information between the Visited PCRF and the Home PCRF in order to
support local breakout function.
S9 is used in roaming scenarios involving an VPLMN and a HPLMN.
Two main roaming scenarios:
 Visited Access (“local breakout”): PCEF is located in the VPLMN, and the UE obtains
access to the PDN from the VPLMN.
 Home Routed Access: PCEF is located in the HPLMN, and the UE obtains access to the
PDN from the HPLMN.
Protocol
 Diameter S9
H-PCRF V-PCRF
 SCTP Diameter Diameter
Messages SCTP SCTP
 CC-Request (CCR) Command IP IP
 CC-Answer (CCA) Command L2 L2
 Re-Auth-Request (RAR) Command L1 L1

End of appendix
EPC interfaces Protocols and Messages


LTE EPC Technical Overview

Uploaded by

Copyright:

Available Formats

LTE EPC Technical Overview

Uploaded by

Document Information

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

LTE EPC Technical Overview

Uploaded by

Copyright:

Available Formats

NokiaEDU

This course consists of the following Modules.

Successful completion of this course requires basic knowledge of the

See Read voice- Search Glossary

Audio time Play or Next page Minimize

Volume control Page number and Course

Upon completion of this module, you should be able to:

 Describe the primary objectives of Long Term Evolution (LTE)

1 LTE Evolved Packet System (EPS) 5

 Next generation evolution for both WCDMA and CDMA operators.

 End-to-end IP mobile service delivery architecture

EPS (Evolved Packet System) overview

 Evolved Universal Terrestrial Radio Network (eUTRAN)

User and control

5780 DSC - PCRF

and control data Control only

8650 SDM - HSS

User and control

SC-FDMA SGW PGW

 Communicates with the eNodeB - exchanges information with the

 Assigns temporary IDs to UEs

SC-FDMA SGW PGW

 9471 MME authenticates UEs

Blades (SB) 9 to 13 Chassis 2

MPH 2 and 10 O M M S Chassis 1

7750 MG 7750 MG (PGW)

IP routing – maintains data

User and control

 Provides the UE with an IP address

 Nokia SGW and PGW are based

7750 SR-12 example configuration

 Policy management entity that provides dynamic control of QoS (quality

Note: 5780 DSC Training:

SC-FDMA SGW PGW

@@SECTION · @@MODULE · 33 COPYRIGHT © Nokia 2014. ALL RIGHTS RESERVED.

SC-FDMA SGW PGW

Components of the LTE solution have separate timelines for their

eNB eNB eNB

The Nokia LTE network also supports a variant of GWCN.

Gateway Core Network (GWCN) variant

Shared Shared Shared

eNB eNB eNB

This module covered:

Upon completion of this module, you should be able to:

 Identify and describe transport protocols

1 Transport protocol overview 7

The Transport Layer (OSI Model, Layer 4) provides transparent transfer of

Note: OSI (Open System Interconnection) Model – http://en.wikipedia.org/wiki/OSI_model

Note: Protocols – RFC #s: http://rfc-editor.org/rfcsearch.html

The application’s network requirements drive whether to use UDP, TCP,

General message organization for a Security protected NAS message

Note: 3GPP TS: http://www.3gpp.org/ftp/Specs/html-info/24-series.htm

Note: 3GPP TS: http://www.3gpp.org/ftp/Specs/html-info/36-series.htm

Note: Protocols – RFC #s: http://rfc-editor.org/rfcsearch.html

On passing, 'Finish' button: Goes to Next Slide

On failing, 'Finish' button: Goes to Next Slide

Allow user to leave quiz: After user has completed quiz

User may view slides after quiz: At any time

Show in menu as: Multiple items

Additional interfaces are involved in roaming situations. Theses interfaces are