Evolved Packet System

Overview of EPS Requirements and Architectural overview

CONTENT
1. Evolution of Mobile Communications
2. Requirements to Evolved Packet System 3. Architectural overview

Evolution of mobile communications

Evolution of 2G and 3G mobile technologies

Evolution of mobile communications

Typical downlink throughput for 2G and 3G technologies

Typical downlink user data throughput of IS-41 systems

Evolution of mobile communications

System Architecture Evolution (SAE) is the name of the 3GPP standardization work item which is responsible for the evolution of the packet core network, more commonly referred to as EPC.
Evolved Packet System (EPS) covers the radio access, the core network and the terminals that comprise the overall mobile system. Also provides support for other high-speed RANs that are not based on 3GPP standards, for example, WLAN, WiMAX or fixed access.

Evolution of mobile communications

SAE building bridges between different networks
1. Support for non-3GPP access networks 2. Support handovers between 3GPP and non-3GPP accesses 3. Network-based mobility mechanisms were preferred 4. Common Security framework 5. Common User management and Authentication and Authorization framework 6. Common Policy and Charging support 7. Common framework for On and Off line Charging and Accounting 8. Provide Optimized handover to/from existing deployed Radio access and Packet Core networks: GPPs GERAN, UTRAN and HSPA and GPP2s HRPD networks 9. Common Evolved Packet Core for access to Common IMS and Applications and Service framework 10. Common operations and management of Terminals.
6

Evolution of mobile communications

Evolved Packet System is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple radio access technologies. The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and EUTRAN). The focus of the EPS work is on enhancement of Packet Switched technology to cope with rapid growth in IP traffic.

Evolution of mobile communications

The Evolved Packet System is characterised by:
Reduced latency Higher user data rates equating to broadband performance (peak packet data rates of 100 Mbps on the radio access bearer downlink to the UE and 50 Mbps on the uplink) Improved system capacity and coverage Lower operational costs

E-UTRAN latency requirements

Evolution of mobile communications

The objectives of the EPS are to: Provide higher data rates, lower latency, high level of security and enhanced QoS;

Support access system selection based on a combination of operator policies, user preference and access network conditions;
Realise improvements in basic system performance whilst maintaining the negotiated QoS across the whole system;

Provide capabilities for co-existence with legacy systems and migration to the EPS;
Support a variety of different access systems (existing and future), ensuring mobility and service continuity between these access systems.

Evolution of mobile communications

PSTN
SC

Internet
MM

3GPP Legacy System

Policy

Evolved Packet Core

AAA

...

Evolved Packet System

...

E-UTRA and E-UTRAN

...

Non 3GPP Access System

Heterogeneous access system mobility between 3GPP Legacy Systems or E-UTRAN and non 3GPP Access Systems including Fixed Access systems
10

Requirements to EPS
High-level requirements user and operational aspects
Enhanced performance e.g., low communication delay, low connection set-up time and high communication quality;

Efficiently support a variety of traffic models e.g. user-to-user, user-to-group and traffic models generated by ubiquitous services;
Always on The support for efficient mechanisms to support always-connected terminals is a key requirement for services like Presence, Instant Messaging and Push-ToTalk.
Terminal state transition requirements
11

Requirements to EPS
High-level requirements user and operational aspects
Support of service continuity between 3GPP access systems and also between 3GPP access systems and non 3GPP access systems whether the UE supports simultaneous radio transmission or not. Service Continuity: The uninterrupted user experience of a service that is using an active communication (e.g. an ongoing voice call) when a UE undergoes a radio access technology change or a CS/PS domain change without, as far as possible, the user noticing the change.

Service capability set shall include, as a minimum, support for the following categories of services : - Voice - Video - Messaging - Data file exchange

12

Requirements to EPS
Quality of Service
Network Access Service Access Service Retainability Service Integrity

Phases of service use from customer's point of view

Network Access: The network indication on the display of the mobile is a signal to the customer that he can use the service of this network operator (or any other means to indicate to the user that a network is available). Service Access: If the customer wants to use a service, the network operator should provide him as fast as possible access to the service. Service Integrity: This describes the Quality of Service during service use. Service Retainability: Service retainability describes the termination of services (in accordance with or against the will of the user).
13

Requirements to EPS
Quality of Service
There should be no perceptible deterioration of audio quality of a voice call during and following handover between dissimilar CS and PS access networks, and transitions between PS access networks supporting different IP protocol versions. There should be no loss of data, as a result of handovers between dissimilar fixed and mobile access systems, including those that support different versions of the IP protocol. The EPS network shall support a minimum of 8 levels of QoS in parallel. It shall be possible for the EPS to change QoS, when the terminal moves from one access system to a new access system and the new access system can not provide the same QoS as the old access system or the new access system can provide higher QoS.

14

Requirements to EPS
Support of Multicast and Broadcast Services
The EPS shall be able to support Multicast and Broadcast Services which shall be enhanced especially from some aspects, e.g. optimized service provisioning procedures, better performance compared to current MBMS system, and support of multiple access systems.

Support of Emergency Calls

The EPS shall support IMS emergency calls applicable to the PS domain

15

Requirements to EPS
Security requirements
The EPS shall provide a high level of security. Any possible lapse in security in one access technology shall not compromise security of other accesses. The EPS should provide protection against threats and attacks including those present in the Internet. The EPS shall support information authenticity between the terminal and Evolved Packet Systems. The EPS shall allow for a network to hide of internal network elements from the UE. Security policy shall be under the control of the home operator. Appropriate traffic protection measures should be provided by the EPS The EPS shall provide appropriate mechanisms to enable lawful intercept.
16

Architecture overview
Pure IP infrastructure supporting the logical nodes with functions needed for IP connectivity and routing between the entities, DNS functions supporting selection and discovery of different network elements, support for both IPv4 and IPv6 in the transport and application layer.

Architecture overview

17

Architecture overview
Basic IP connectivity over LTE access
Two main principles have been guiding the design of the architecture:

to optimize the handling of the user data traffic itself, through designing a flat architecture (as few nodes as possible are involved in processing the user data traffic).
to separate the handling of the control signaling from the user data traffic.

Basic EPS architecture for LTE

18

Architecture overview
Basic IP connectivity over LTE access
eNodeB (the LTE base station) includes all features needed to realize the actual wireless connections between user devices and the network.
Mobility Management Entity (MME) handles all LTE-related control plane signaling, including mobility and security functions for devices and terminals attaching over the LTE RAN.

The user data payload are handled by two logical nodes called the Serving Gateway (Serving GW) and the Packet Data Network Gateway (PDN GW).
HSS manages user data and related user management logic for users accessing over the LTE RAN.

Basic EPS architecture for LTE19

Architecture overview
Adding more advanced functionality for LTE access
The PCC (Policy and Charging Control) concept is designed to enable flow-based charging, including, for example, online credit control, as well as policy control, which includes support for service authorization and QoS management. PCRF contains policy control decision and flow-based charging control functionalities.

Adding policy and charging control to the basic EPC architecture

20

Architecture overview
Adding more advanced functionality for LTE access
Charging models supported by the EPS include: calling party pays charging based on assured QoS charging based on the transport charging based on an event charging based on content charging adjustment (e.g. based on subscription bands) alternate party charging. Charging mechanisms of the EPS provide: - Cost effective Control and Charging of IP Flows - Perform online charging - Support differentiated charging including zero rating of the bearer and event charging - Awareness of subscriber identity, time-of-day, roaming status, QoS, Service input etc.
21

Architecture overview
Adding more advanced functionality for LTE access
OFCS - Offline Charging System OCS - Online Charging System. Both logical entities interface the PDN GW (through the Gz and Gy interfaces respectively) and support various features related to charging of end users based on a number of different parameters such as time, volume, event, etc.

Adding policy and charging control to the basic EPC architecture

22

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
Before EPS, when the user has moved and wants to use the new access network, the network considers this as a completely new attach request. The device is normally given a new IP address from the network, which then may or may not cause problems for the applications in use in the device. Furthermore, there is normally a quite long service interruption between loss of coverage of network A and the establishment of IP connectivity to network B.

Inter-access mobility without session continuity 23

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
The EPC architecture allows for session continuity, that is that an IP connectivity session which is established over any of the allowed access networks (A or B) actually will survive movements between the different access networks due to loss of radio coverage. This is handled through retaining a stable IP anchor point in the network which allows for not having to change the IP address of the device at all. Applications and services will, in theory, then not be dependent on the access network that is in use or on any possible movements between these.

Inter-access mobility with session continuity 24

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
The interworking solution for LTE includes the SGSN attaching to GSM and WCDMA radio networks as today, but then includes the MME and the PDN GW acting as an SGSN and a GGSN respectively. The MME and PDN GW are in fact replicating the signalling needed for movements between networks GSM/GPRS and WCDMA/HSPA to also apply for mobility with LTE. Interworking between LTE and GSM/GPRS or WCDMA/HSPA25

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
SGSN distinguishes a terminal - that attaches over GSM/GPRS or WCDMA/HSPA but is not capable of moving to LTE - that in fact can connect to LTE but is currently attaching to GSM/GPRS or WCDMA/HSPA due to lack of LTE radio coverage. The latter terminal must always be using the PDN GW as the anchor point and never a GGSN since there is no logical connection between the LTE radio network and a GGSN.

SGSN selecting GW

26

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
The SGSN implements four new interfaces. S3, S4 and S16 rely on an updated version of the GTP protocol and are used instead of the different variants of the Gn interface. S6d - data related to GSM and/or WCDMA, not to LTE.

27

Interworking using GTPv2 interfaces

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
S4 - creates a common anchor point for LTE, GSM/GPRS and WCDMA/HSPA in the Serving GW.
S3 - signaling-only interface and supports inter-system mobility. S16 - mimics the MME S6a interface towards the HSS for retrieving subscriber data from the HSS.

28

Interworking using GTPv2 interfaces

Architecture overview
Interworking between LTE and GSM/GPRS or WCDMA/HSPA
S12 (optional for user traffic) - utilizes a direct connection between the RNC in the WCDMA radio network and the Serving GW. If S12 is used, the SGSN will only handle the control signaling for WCDMA/HSPA. The primary driver for this is that the network does not have to be scaled in terms of SGSN user capacity.
29

Direct tunnel support for WCDMA/HSPA

Architecture overview
Interworking between LTE and CDMA networks
Efficient and smooth handovers between the different technologies: Access authentication for a user attaching over an eHRPD network are based on AAA functionality (a software feature inside the HSS or stand-alone AAA equipment interfacing the HSS over the Diameter-based SWx interface).

Interworking between LTE and eHRPD networks

30

Architecture overview
Interworking between 3GPP access technologies and non-3GPP access technologies
Terminals IP address assignment, access to general IP services as well as network features like user subscription management, security, charging, policy control and VPN connections are independent of the access technology be it wireless or fixed.

Interworking between 3GPP access and non-3GPP access technologies

31

Architecture overview
Interworking between 3GPP access technologies and non-3GPP access technologies
There are two ways to distinguish between the available options: 1. Are Network-based or Client-based mobility mechanisms used? 2. Is it a connection to trusted or a non-trusted network?

Network-based means that there are functions in the access network that acts on behalf of the terminal, and provides mobility support. It simplifies the terminal client application, but instead requires that there is specific Mobile IP support in the network itself. Client-based approach works over any access network, as long as there is adequate support in the terminal itself. This function may be used totally transparent to the functionality in the access network.
32

Architecture overview
Interworking between 3GPP access technologies and non-3GPP access technologies
There are two ways to distinguish between the available options:
1. Are Network-based or Client-based mobility mechanisms used? 2. Is it a connection to trusted or a non-trusted network? An indicator on if the 3GPP operator (owning the PDN GW and the HSS) trust the security of the non-3GPP access network A typical trusted network may be an eHRPD network, while a nontrusted network may be, for example, usage of WLAN in a public caf and connecting to the PDN GW over the public Internet.

33

Architecture overview
Interworking between 3GPP access technologies and non-3GPP access technologies
ePDG (evolved Packet Data Gateway) is an evolution of the PDG that is specified in earlier versions of the 3GPP standards to allow interconnection (but not inter-access mobility) of WLAN access to a 3GPP network. Typically, the ePDG belongs to the mobile operator.

EPC architecture for non-3GPP accesses 34

Architecture overview
Interworking between 3GPP access technologies and non-3GPP access technologies
Encrypted tunnels are established between the user devices and the ePDG, to ensure that each device can communicate with the network in a secure way.

EPC architecture for non-3GPP accesses

35

Architecture overview
Support for voice services
Specific mechanisms to allow for voice services for users of the packet data services offered over the LTE access: IMS mechanisms realizing voice using the MultiMedia Telephony (MMTel) user device cant encounter the lost of LTE coverage.
stick to the old CS way of providing voice services. Users temporarily leave LTE to perform the voice calls over 2G/3G, and then return when the voice call is finished.

EPC architecture for voice support

36

Architecture overview
Support for voice services
Sv interface for IMS solution: -Single-Radio Voice Call Continuity (SRVCC).
SGs interface (no IMS) - Circuit-Switched Fallback (CSFB).

EPC architecture for voice support

37

Architecture overview
Miscellaneous features
ETWS ( Earthquake and Tsunami Warning System)
Warnings from Cell Broadcast Centre (CBC) MMEs must convey the warnings to all terminals that happen to be in idle mode, and whose location is only known with the accuracy of a Tracking Area.

Miscellaneous features in the EPC 38 architecture

Architecture overview
Miscellaneous features
Equipment Identifier Register (EIR)
ANDSF ( Access Network Discovery and Selection Function) - used to control how users and their devices prioritize between different access technologies if several non-3GPP access networks are available. It is a means to give the network operator the possibility to control how users attach to the network, based on a number of criteria. Miscellaneous features in the EPC architecture
39

Architecture overview

Overall EPS architecture

40