LTE Evolved Packet System Architecture

LTE basic nodes and interfaces LTE interworking options

LTE enables you to redefine the end-user experience Mobility Management Entity (MME) functions Home Subscriber Server (HSS) LTE with legacy 3GPP interworking (pre-Release 8)
• Non-Access Stratum (NAS) signaling (attachment, bearer setup/deletion) • Storage of subscriber data
with the most advanced packet-based solution in • NAS signaling security

• Signaling for mobility between 3GPP access networks (S3)

UE RAN CORE A P P L I C AT I O N S
• Enhanced Presence Service (EPS) QoS subscriber profile

• Roaming restrictions list •

•
•
HSS/HLR
Gr • • • •

• • • • • • • • • • • • • • • • • • • •
• Idle mode user equipment reachability • Accessible Access Point Names (APNs)

the industry. Continuing our 3G partnership into LTE,

•
•
•
• S6a
• Tracking Area list management • Address of current serving mobility management entity (MME) UTRAN/ lu-PS/Gb •
2G/3G Gn 2G/3G Gi

•
GERAN SGSN GGSN

•
• PDN gateway and serving gateway selection • Current Tracking Area (TA) of user equipment (UE)

•
IMS APPS

•
•
the Alcatel-Lucent end-to-end LTE solution provides:

•
• MME selection for handoffs with MME change • Authentication vectors and security keys per UE Gn Gn

•
eNB

•
•
• • •

•
S1-MME • •
•
• •
• Roaming - s6a to home subscriber server (HSS) • Alcatel-Lucent 8650 Subscriber Data Manager
•

•
•
• • • •
• • • • •
HSS
• •
Gn (IP/lu-PS)

•
• • • • •
• •

•
• •
•
• •
S10
•

•
•

•
•
• Authentication
•
• • •

• • • •

•
• •
• •

• • • •
• •
Rx
•

•
• •

• A comprehensive transformation to an IP
• •
•
S6a

•
• •
• •
PCRF
•
• Bearer management functions including dedicated bearer establishment

•
• •
•
• •

•
•
• •
EUTRAN MME

•
•
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •• •• •• •• • • • • • • • • • • • • • •

•
• Support for Earthquake and Tsunami Warning System (ETWS) message transmission S1-U S1-MME S11 PDN

• • •
LTE-Uu
X2
infrastructure with minimal risk

• • • • • • • • • • •
• Alcatel-Lucent 9471 MME MME S-GW P-GW/
• •
• •
• • S1-U S5 GGSN SGi
• •
• • Gx

•
S1-MME •
S11

•
•
• •

•
• •

•
• An open LTE ecosystem of devices, applications
• •

•
• •
Policy and charging rules function (PCRF)

•
TS 23.401, ANNEX D:
User Equipment (UE) functions

•
• •

•
• •
S1-U S5/S8 SGi PDN Utilizes new LTE elements to emulate legacy elements for interworking An LTE-capable device that also supports 2G/3G will access APNs
eNB • Interfaces with application functions such as the proxy-call session control function
and content providers
• Contains the Universal Subscriber Identity Module (USIM) which holds S-GW P-GW through the PDN gateway, which serves as the mobility anchor
(P-CSCF) or other policy enabled applications • Mobility management entity (MME) supports Gn/Gp interfaces
authentication information for the legacy third-generation partnership project (3GPP)
• Interfaces with the PDN gateway to convey policy decisions to it (TS 23.060) for the control plane (based on GTPv1)
• Supports services and applications
S5 • Decides how services shall be treated in the PDN gateway in accordance with
• PDN gateway needs to support Gn/Gp interfaces (TS 23.060) for the

• Smooth interworking with existing 2G/3G networks

• Monitors radios and conveys performance to the Evolved Node B (eNB) channel
a user subscriber policy control and user planes. PDN gateway also acts as a GGSN and common
quality indicator (CQI) anchor for evolved packet core (ePC) bearers and packet data protocol
• Alcatel-Lucent 5780 DSC
• Supports LTE uplink and downlink air interface (PDP) contexts.
and evolution to the next generation • Maps upstream traffic into traffic classes that are defined by upstream traffic
flow templates
LTE with legacy 3GPP interworking (Release 8)
Serving Gateway (S-GW)
• Local mobility anchor for inter-evolved Node B (eNB) handover
Evolved Node B (eNB) functions
•

For more information, visit:

•

Mobility anchor for inter-third-generation partnership project (3GPP) mobility

•
•
HSS/HLR
• S6d/Gr • • •

• • • • • • • • • • • • • • • • • • • • •
S16 • • •
• Radio resource management: radio bearer control, radio admission control, • Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) idle-mode downlink • • •

www.alcatel-lucent.com/LTEinfo
•

PDN Gateway (P-GW)

•
connection mobility control, uplink/downlink scheduling
•
•
•
S6a

• •
packet buffering and initiation of network triggered service request procedure •

•
GERAN/ lu-PS/Gb R8
•
Gn 2G/3G Gi

• • •
•
•
• IP header compression and ciphering of user data stream

•
••
PDN gateway

•
• Lawful intercept •
SGSN GGSN
• • •

or call your Alcatel-Lucent representative. UTRAN

•
•
• Mobility management entity (MME) selection

•
• Packet routing/forwarding • Per-user packet filtering S4

•
•
S3

•
• Forwarding uplink data to serving gateway

•
• Transport level packet marking (uplinking and downlinking) • Lawful intercept

•
•
S12

•
• Paging

•
• Accounting on user and Quality of Service (QoS) class identifier granularity • User equipment (UE) IP address allocation

•
•
• • • •
S11

• •
• Scheduling and transmission of broadcast information, originated from the mobility for inter-operator charging •
• Transport level packet marking for downlinking

• • •
EUTRAN MME• • •• • • • • • • • • • •

• ••
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
management entity (MME) or operations and maintenance (O&M) S1-MME

• • • • •
• Uplink and downlink charging per user equipment, packet data node (PDN), and • Uplink/downlink service level charging, gating, and rate enforcement PDN

• • •
• Measurement and measurement reporting configuration for mobility and scheduling • • •
••
S10
QoS class identifier (for roaming with home routed traffic) • Downlink rate enforcement based on aggregate maximum bit rate (AMBR) S-GW P-GW
• Scheduling and transmission of Earthquake and Tsunami Warning System (ETWS) • Alcatel-Lucent 7750 Service Router S1-U S5/S8 SGi
• Alcatel-Lucent 7750 Service Router

Voice and SMS interworking options

messages, originated from the MME

RELEASE 8 METHOD OF I NTERWORKI NG (TS 23.401, CLAUSE 5.5.2):

The release 8 method of inter-radio access technology (IRAT) interworking Advantages of R8 interworking
relies on using: • Offers a highly scalable solution that leverages new evolved
IMS - Industry-standard service architecture S1-mobility management entity (MME): used for signaling between the Evolved Node B X2: used to support intra-MME handoff with no packet loss S5: a signaling interface for establishing bearers between the serving gateway SGi: the interface into the IP PDN. This is where the IP visibility into the UE IP address(es) • New S3 and S4 interfaces, modeled on the S5 and S10 interfaces used for packet core (EPC) elements for a variety of 3GPP access options
(eNB) and the MME and the PDN gateway or between serving gateways, for serving gateway changes is exposed. S1 based handover, to support signaling and user plane requirements (HSPA+, other 2G/3G)
(GTPv2). It also supports the user plane for bearers (GTPv1). Note there is a PMIPv6
- A serving GPRS support node (SGSN) that uses the new interface is • Compatible with 3G direct tunnel approach (3G DT terminated
S11: used by the MME to control path switching and bearer establishment in the serving version of the S5.
UE EUTRAN EPC IMS S1-U: defines user plane between eNB and serving gateways S8: analogous to the S5 except that it is used in roaming scenarios. called an S3/S4 SGSN on a serving gateway)
gateway and PDN gateway
• A serving gateway as a mobility anchor for intra-3GPP mobility • Supports Idle Mode Signaling Reduction (ISR)
A PPLICATION S Gx: used by the PCRF to convey policy enforcement to the P-GW, and also used to
Voice Call Continuity Rx: used by application functions, such as the IMS P-CSCF, to convey policy data to - Mobility management entity (MME) <> SGSN handovers support call
S10: used by MMEs to support MME changes S6a: used by the MME to retrieve subscriber data from home subscriber server (HSS) retrieve traffic flow data.
eNB •
•
Telephony the PCRF. flows similar to the basic S1-based handover with MME change
• • •
• •
• •
• • •
Sh (also described in TS 23.401)
• •
• • S6a
• •
• •
• •
•
• •
•
Presence
• • • • • •
• • •
• •
• • •
Sp SMS/IM
• •
• •
• •
HSS
LTE with non-3GPP interworking (Release 8)
• • •
• • •
•

Gm • •
Voice Mail
•

Bearer architecture LTE policy control and charging

•
Cx
•
•

MME PCRF
•
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

• • •
•

• • • •
• •
•

• • • •
Rx • • • • • • • • • • • • • • • • • • • • • • • • • • S6a
S1-MME • • MME
•

• •
S1-MME

• • • • • • • •
•

•
•

S11 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

• • • • • • • • • • •
• •
•

•
• •

• • • •

• • • • • • • • • • • • • • • •
• • • • •
•

Gx
•

• • •
Session control S11
•

• • SWx
• •

• •
HSS/HLR
•

•
(CSCF)
•

•
• •

•
Sv S5
S1-U EUTRAN EPC PDN EUTRAN S-GW P-GW PDN
• •

Other NW
eNB S-GW P-GW SGi

• • • • • • • •
• •

PCRF S101
• • • • • • • • • • • • • • • • • •
• •

SGi S103 • • • • • • • • • •
UE eNB SGW PGW PEER S2a S6b

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• •

• • • •
ENTITY trusted
MGCF/ IP CORE S9 non-3GPP access AN • • • • • • • • • • • • •

BTS/NB MSC MGW End-to-end service (EHRPD)

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
(e.g. HSGW)
Rx STa
PSTN & Other • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Application
• • • • • • • • • • • • • • • • • • • • • • PCRF 3GPP/AAA

• • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • •
UTRAN/GERAN Networks Gxc (PMIPv6 S5 only) • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Function

• • • • • • • • • • • • • • • • • • • • • • • • •
Media untrusted S2b

• • • • • •
• • • •
Sp

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

• • • • •
EPS bearer External bearer Gxa Gxb SWm SWa
server non-3GPP access ePDG • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Gx (WLAN)
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

E-RAB S5/S8 bearer S5 SPR SGi

• • • • • •
EUTRAN S-GW PDN
• IMS architecture is described in TS 23.228 • IMS centralized services (ICS) (TS 23.292) and service centralization and P-GW
• • • • • • • • • • • • • • • • • • • • I NTERWORKI NG WI TH NON-3GPP ACCESS NETWORKS (TS 23.402):
continuity (SCC) (TS 23.237) enable IMS services for user equipment in

• • • •

• • • • • • • • • • • • • •
• IMS supports VoIP on EV-DO, HSPA+ and LTE Radio bearer S1 bearer • • • • • • • • • • • • • • • • • • • • • • • • • •
Fundamental goal: Achieve mobility with IP address preservation when Basics:
the circuit-switched domain

• • • • • • • • • •
• Single Radio Voice Call Continuity (SRVCC) IMS supports optimized • • • • • • • • • • • • • • • • • • • • • • • • •
user equipment selects a non-3GPP access
S2a • The PDN gateway is a mobility anchor for non-3GPP access and

• • • • • • • • • • • • • • • • • • •
handoff of calls between VoIP domains and wireless circuit domains Gz/Rf GyRo
S2b Access types supports PMIPv6 Local Mobility Anchor (LMA) functions
using the Voice Call Continuity (VCC) application server (TS 23.216) EHRPD
LTE-UU S1 S5-S8 SGi HSGW • Trusted non-3GPP access — WiMAX and high rate packet data (HRPD) • The serving gateway (in the case of PMIPv6 S5/S8) supports mobile
(trusted non-3GPP access) • • • • • • • • • • • • • • • • • • • • • • • • • •
GyRo operated by the same provider as LTE access gateway (MAG) functions

• • • •

•
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • OCS
Circuit-switched (CS) fall back EPS BEARER (36.300, CLAUSE 13.1): PCRF (TS 23.203): UE
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
- The operator has authenticated users for the access network • The Access Network (AN) - HRPD Serving Gateway (HSGW) or

• • • • • • • • • •
• • • • • • • • • • • • • • • • • • • • •

• • • • • •
• Evolved packet switch (EPS) bearer (36.300, clause 13.1): • Policy rule • • • • • • • • • • • • • • • • • • • •
- The operator has implemented sufficient safeguards to mitigate Evolved Packet Data Gateway (ePDG) - supports PMIPv6 (RFC 5123)

• • • • • •
• An EPS bearer is an end-to-end tunnel defined to a specific QoS - Applies a filter (TFT) to map SDFs to EPS bearers potential attacks • Other options such as client MIP, dual-stack MIP and others are
WLAN
UE EUTRAN EPC A P P L I C AT I O N S ePDG• • • • • •• •• •• •• •• •• •• •• •• •• •• •• •• •• •• •Gz/Rf
• • • • • • • • • • OfCS
• • • • • • • • • • • • • • • • • • • • • •
• Untrusted non-3GPP access — third-party WLAN access supported in TS 23.402
- A default bearer is defined at the user equipment initial attach; radio resources are - Provides charging instructions (untrusted non-3GPP access) • • • • • • • • • • •

removed if the user equipment goes idle (home or business) hot spot • S101 and S103 can optimize the handoff from LTE to HRPD with
• Extremely flexible model
- The operator requires separate authentication procedures no packet loss and quicker handoff completion
- A dedicated bearer is created using signaling for specific services - Dynamic policy control
APPS - Example: WLAN access from a third party (home or business) hot spot
eNB • •
• • • • The QoS model is built on the EPS bearer which has four parameters associated to it:
• • •
Sp - Policy push: User equipment <> application signaling determines which SDFs
• •
S10
•

Rx
•

LTE security
- QoS class identifier (QCI) is an integer which provides an index into a table providing to use and what policy rule to install using the PCRF on the PDN gateway
• • • •

•
• •
•
• • • •

•
HSS
• •
•

• • •
•

•
• •
• •
forwarding treatment for that bearer (in terms of latency and packet loss)
•

• •
• •
- Policy pull: The gateway detects an event which triggers notification to the PCRF
• •
• • • •
S6a
•
• •
•

PCRF - Allocation and retention priority (ARP) is used by the scheduler to provide preemption to download a policy rule
•
• • •
•

X2 MME priority in case of contention - Pre-defined policy rules

•
• • - Guaranteed Bit Rate (GBR): separately for both downlinks and uplinks.
• • • • • • • •

• • - Roaming support, other AN support I NTERFACE PURPOSE PROTOCOL REFERENCE

S1-MME • •
Note an EPS-bearer can be non-GBR EPS AKA EPS AKA
•

• •
S11 Gx
•

• • • Charging functions in PCRF

• •

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
•

• •
•

• •
- Aggregate Maximum Bit Rate (AMBR) specifies downlink and uplink bit rates for Gx Policy control Diameter/SCTP TS 29.212
•
• •

• •
•

• • - Charging correlation: binds uplink traffic (per SDF) to IMS signaling layer
•

• •
an aggregate EPS bearer NAS Integrity Protection
• •

• • • • •• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
•

INTERNET (useful for volume metering, for example) Gxa, Gxb and Gxc BBERF as defined in TS 23.402 Diameter/SCTP TS 29.212
• •

S1-U S5/S8 SGi • Service data flows (SDF) are specific packet flows identified by quintuple and associated • NAS Ciphering (Null, AES, Snow 3G)
eNB S-GW P-GW
• •

• Charging in PDN gateway and serving gateway (for roamers)

to a service requiring special treatment Rx Application function to PCRF Diameter/SCTP TS 29.214 MME • • • • • • • •
• •

- Per SDF statistics collection based on charging rules provided by the PCRF • • • • • RRC Signaling Integrity Protection (AES and Snow 3G) • • • • • • • S6a
• •

SGs or S101 (for CDMA) • SDFs are mapped into EPS bearers at the user equipment (for uplinks) and at the PDN
•
•
S9 Roaming interconnect for PCRF Diameter/SCTP TS 29.215 HSS
•

• • • • • • • • •
- Online charging through diameter credit control (Gz) • RRC Signaling Ciphering (Null, AES and Snow 3G)
•

PSTN & Other gateway (for downlinks) using a set of filter rules called traffic flow templates (TFT). S1-MME
•
•
•
BTS MSC • User Plane Ciphering (Null, AES, and Snow 3G)
•
Networks - Offline charging (Gy) Sp Retrieving per subscriber policy data Not specified Not defined in R8 •
•
•
S11
•
• Other PDN gateway functions
•
•
Gy/Ro On-line charging Diameter/SCTP TS 30.240 &TS 32.299
•
L1/L2 Signaling
•
- Gate control: allows or disallows SDF
•

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
- Flow policing Gz/Rf Off-line charging Diameter/SCTP TS 32.251 & TS 32.295 eNB S-GW
• CSFB is defined in TS 23.272 • The user equipment retunes and reconnects to the 2G/3G carrier and • • • • • • • • • • • • • •
User Plane User Plane
• Dual mode 2G/3G and LTE user equipment is registered in the 2G/3G accepts calls - Marking flows Ga Off-line charging GTP/UDP TS 32.299
circuit domain but is tuned and connected to the LTE/EPC network • LTE data session is either suspended or is handed to W-CDMA - Metering
• Voice calls come into the mobile switching center (MSC) (if applicable - not shown above) - Application awareness through DPI REFERENCES ARE: For backhaul security, follow the SeGW specification:
• The MSC alerts the user equipment of incoming voice calls through • SGs interface can also deliver SMS traffic to the user equipment when • Bearer binding and event reporting function (BBERF) • TS 33.401: SAE Security Architecture TS 33.210 / TS 33.310
the serving gateway interface, mobility management entity (MME) in LTE mode • TS 24.301: NAS Protocol
- Bearer binding is the generic procedure for associating a bearer in the access to a SDF
and LTE. Note the S101 is used in the event the MSC is 3GPP2 (CDMA) • TS 36.323: PDCP Specification
- TS 23.402 and 23.203 defines bearer binding and event reporting function (BBERF)
to support situations where a direct policy interface is needed.
www.alcatel-lucent.com
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
© 2009 Alcatel-Lucent. All rights reserved. RMK7526091004 (10)