System Architecture Evolution


System Architecture Evolution is the core network architecture of 3GPP's LTE wireless communication standard.
SAE is the evolution of the GPRS Core Network, with some differences:
The SAE has a flat, all-IP architecture with separation of control plane and user plane traffic.
The main component of the SAE architecture is the Evolved Packet Core, also known as SAE Core. The EPC will serve as the equivalent of GPRS networks.

Evolved Packet Core (EPC)

The subcomponents of the EPC are:

MME (Mobility Management Entity)

The MME is the key control-node for the LTE access-network. It is responsible for idle mode User Equipment paging and tagging procedure including retransmissions. It is involved in the bearer activation/deactivation process and is also responsible for choosing the Serving Gateway for a UE at the initial attach and at time of intra-LTE handover involving Core Network node relocation. It is responsible for authenticating the user. The Non Access Stratum signaling terminates at the MME and it is also responsible for generation and allocation of temporary identities to UEs. It checks the authorization of the UE to camp on the service provider's Public Land Mobile Network and enforces UE roaming restrictions. The MME is the termination point in the network for ciphering/integrity protection for NAS signaling and handles the security key management. Lawful interception of signaling is also supported by the MME. The MME also provides the control plane function for mobility between LTE and 2G/3G access networks with the S3 interface terminating at the MME from the SGSN. The MME also terminates the S6a interface towards the HSS for roaming UEs.

SGW (Serving Gateway)

The Serving Gateway routes and forwards user data packets, while also acting as the mobility anchor for the user plane during inter-eNodeB handovers and as the anchor for mobility between LTE and other 3GPP technologies. For idle state User Equipment, the Serving Gateway terminates the downlink data path and triggers paging when downlink data arrives for the User Equipment. It manages and stores UE contexts, e.g. parameters of the IP bearer service, network internal routing information. It also performs replication of the user traffic in case of lawful interception.

PGW (Packet Data Network Gateway)

The Packet Data Network Gateway provides connectivity from the User Equipment to external packet data networks by being its the point of exit and entry of traffic. A piece of User Equipment may have simultaneous connectivity with more than one Packet Data Network Gateway for accessing multiple packet data networks. The PDN Gateway performs policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening. Another key role of the Packet Data Network Gateway is to act as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2.

HSS (Home Subscriber Server)

The Home Subscriber Server is a central database that contains user-related and subscription-related information. The functions of the HSS include functionalities such as mobility management, call and session establishment support, user authentication and access authorization. The HSS is based on pre-Rel-4 Home Location Register and Authentication Center.

ANDSF (Access Network Discovery and Selection Function)

The ANDSF provides information to the UE about connectivity to 3GPP and non-3GPP access networks. The purpose of the ANDSF is to assist the UE to discover the access networks in their vicinity and to provide rules to prioritize and manage connections to these networks.

ePDG (Evolved Packet Data Gateway)

The main function of the ePDG is to secure the data transmission with a UE connected to the EPC over untrusted non-3GPP access, e.g. VoWi-Fi. For this purpose, the ePDG acts as a termination node of IPsec tunnels established with the UE.

Non Access Stratum (NAS) protocols

The Non-Access Stratum protocols form the highest stratum of the control plane between the user equipment and MME. NAS protocols support the mobility of the UE and the session management procedures to establish and maintain IP connectivity between the UE and a PDN GW. They define the rules for a mapping between parameters during inter-system mobility with 3G networks or non-3GPP access networks. They also provide the NAS security by integrity protection and ciphering of NAS signaling messages. EPS provides the subscriber with a "ready-to-use" IP connectivity and an "always-on" experience by linking between mobility management and session management procedures during the UE attach procedure.
Complete NAS transactions consist of specific sequences of elementary procedures with EPS Mobility Management and EPS Session Management protocols.

EMM (EPS Mobility Management)

The EPS Mobility Management protocol provides procedures for the control of mobility when the User Equipment uses the Evolved UMTS Terrestrial Radio Access Network. It also provides control of security for the NAS protocols.
EMM involves different types of procedures such as:
The UE and the network execute the attach procedure, the default EPS bearer context activation procedure in parallel. During the EPS attach procedure the network activates a default EPS bearer context. The EPS session management messages for the default EPS bearer context activation are transmitted in an information element in the EPS mobility management messages. The UE and network complete the combined default EPS bearer context activation procedure and the attach procedure before the dedicated EPS bearer context activation procedure is completed. The success of the attach procedure is dependent on the success of the default EPS bearer context activation procedure. If the attach procedure fails, then the ESM session management procedures also fails.

ESM (EPS Session Management)

The EPS Session Management protocol provides procedures for the handling of EPS bearer contexts. Together with the bearer control provided by the Access Stratum, it provides the control of user plane bearers. The transmission of ESM messages is suspended during EMM procedures except for the attach procedure.
EPS Bearer:
Each EPS bearer context represents an EPS bearer between the UE and a PDN. EPS bearer contexts can remain activated even if the radio and S1 bearers constituting the corresponding EPS bearers between UE and MME are temporarily released. An EPS bearer context can be either a default bearer context or a dedicated bearer context. A default EPS bearer context is activated when the UE requests a connection to a PDN. The first default EPS bearer context, is activated during the EPS attach procedure. Additionally, the network can activate one or several dedicated EPS bearer contexts in parallel.
Generally, ESM procedures can be performed only if an EMM context has been established between the UE and the MME, and the secure exchange of NAS messages has been initiated by the MME by use of the EMM procedures. Once the UE is successfully attached, the UE can request the MME to set up connections to additional PDNs. For each additional connection, the MME activates a separate default EPS bearer context. A default EPS bearer context remains activated throughout the lifetime of the connection to the PDN.
Types of ESM procedures:
ESM involves different types of procedures such as:
The MME maintains EMM context and EPS bearer context information for UEs in the ECM-IDLE, ECM CONNECTED and EMM-DEREGISTERED states.

EPC protocol stack

MME (Mobility Management Entity) protocols

The MME protocol stack consists of:
  1. S1-MME stack to support S1-MME interface with eNodeB
  2. S11 stack to support S11 interface with Serving Gateway
MME supports the S1 interface with eNodeB. The integrated S1 MME interface stack consists of IP, SCTP, S1AP.
MME supports S11 interface with Serving Gateway. The integrated S11 interface stack consists of IP, UDP, eGTP-C.

SGW (Serving Gateway) protocols

The SGW consists of
  1. S11 control plane stack to support S11 interface with MME
  2. S5/S8 control and data plane stacks to support S5/S8 interface with PGW
  3. S1 data plane stack to support S1 user plane interface with eNodeB
  4. S4 data plane stack to support S4 user plane interface between RNC of UMTS and SGW of eNodeB
  5. Sxa: since 3GPP Rel.14, the Sx interface and the associated PFCP protocol was added to the PGW, allowing for the Control User Plane Separation between PGW-C and PGW-U.
SGW supports S11 interface with MME and S5/S8 interface with PGW. The integrated control plane stack for these interfaces consists of IP, UDP, eGTP-C.
SGW supports the S1-U interface with eNodeB and S5/S8 data plane interface with PGW. The integrated data plane stack for these interfaces consists of IP, UDP, eGTP-U.

PGW (Packet Data Network Gateway) protocols

Main interfaces supported by the P-GW are:
  1. S5/S8: this interface is defined between S-GW and P-GW. It is named S5 when the S-GW and the P-GW are located in the same network and S8 when the S-GW is located in the visited network and the P-GW in the home network. eGTP-C and GTP-U protocols are used in the S5/S8 interface.
  2. Gz: this interface is used by the P-GW to communicate with the Offline Charging System, mainly to send the Charging Data Records of the post-paid users via FTP.
  3. Gy: this interface is used by the P-GW to communicate with the Online Charging System. The P-GW informs the charging system about pre-paid users payload in real time. Diameter protocol is used in the Gy interface.
  4. Gx: this interface is used by the P-GW to communicate with the Policy and Charging Rules Function in order to handle Policy and Charging Rules rules. These rules contain charging related information as well as Quality of Service parameters that will be used in the bearer establishment. Diameter protocol is used in the Gx interface.
  5. SGi: this interface is defined between the P-GW and external networks, for example, Internet access, corporate access, etc.
  6. Sxb: since 3GPP Rel.14, the Sx interface and the associated PFCP protocol was added to the PGW, allowing for the Control User Plane Separation between PGW-C and PGW-U.

    Support of voice services and SMS

The EPC is a packet-only core network. It does not have a circuit-switched domain, which is traditionally used for phone calls and SMS.

Support for Voice services in EPC

3GPP specified two solutions for voice:
3GPP specified three solutions for SMS:
CSFB and SMS over SGs are seen as interim solutions, the long term being IMS.

Multiple access networks

The UE can connect to the EPC using several access technologies. These access technologies are composed of:
It is up to the network operator to decide whether a non-3GPP access technology is trusted or untrusted.
It is worth noting that these trusted/untrusted categories do not apply to 3GPP accesses.

3GPP releases

The 3GPP delivers standards in parallel releases, which compose consistent sets of specifications and features.
VersionReleasedInfo
Release 72007 Q4Feasibility study on All-IP Network
Release 82008 Q4First release of EPC. SAE specification: high level functions, support of LTE and other 3GPP accesses, support of non-3GPP accesses, inter-system mobility, Single Radio Voice Call Continuity, CS fallback. Earthquake and Tsunami Warning System. Support of Home Node B / Home eNode B.
Release 92009 Q4LCS control plane for EPS. Support of IMS emergency calls over GPRS and EPS. Enhancements to Home Node B / Home eNode B. Public Warning System.
Release 102011 Q1Network improvements for machine-type communications. Various offload mechanisms.
Release 112012 Q3Further improvements for machine-type communications. Simulation of USSD in IMS. QoS control based on subscriber spending limits. Further improvements to LIPA and SIPTO. Single Radio Video Call Continuity. Single Radio Voice Call Continuity from UTRAN/GERAN to HSPA/E-UTRAN. Support of interworking with Broadband Forum accesses.
Release 122015 Q1Enhanced Small Cells operation, Carrier Aggregation, MIMO, MTC - UE Cat 0 introduced, D2D communication, eMBMS enhancements.
Release 132016 Q1Introduced LTE-U / LTE-LAA, LTE-M, Elevation beamforming / Full Dimension MIMO, Indoor positioning, LTE-M Cat 1.4 MHz & Cat 200 kHz