Description
System Architecture Evolution (SAE) is the standardized core network architecture developed by 3GPP for the Long-Term Evolution (LTE) radio access network, collectively known as the Evolved Packet System (EPS). It represents a fundamental shift from the circuit-switched and packet-switched dual-domain architecture of 2G/3G networks to a simplified, all-IP, flat architecture designed for high-speed packet data. The primary goal was to reduce latency, increase data throughput, and simplify network operations to support the explosive growth of mobile broadband services.
The architecture is centered around the Evolved Packet Core (EPC), which consists of several key logical nodes interconnected via standardized interfaces. The core components include the Mobility Management Entity (MME) for control-plane signaling, the Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) for user-plane data routing and policy enforcement, and the Home Subscriber Server (HSS) as the central subscriber database. The S-GW acts as the local mobility anchor during handovers between eNodeBs, while the P-GW provides the interface to external packet data networks (like the internet) and enforces Quality of Service (QoS) policies based on subscriber profiles.
SAE works by separating the control plane (signaling) from the user plane (data bearer), allowing for independent scaling and optimization. When a User Equipment (UE) attaches to the network, the MME authenticates the subscriber via the HSS and establishes a default bearer with specific QoS characteristics through the S-GW and P-GW. This bearer provides 'always-on' IP connectivity. Dedicated bearers with different QoS levels can be established on-demand for specific services like voice over LTE (VoLTE). The architecture supports seamless mobility between 3GPP and non-3GPP access networks (like Wi-Fi) via trusted or untrusted access gateways.
Its role in the network is pivotal as the service delivery and mobility management hub. It provides the framework for policy control and charging (PCC) via the Policy and Charging Rules Function (PCRF), enabling operators to offer tiered services. SAE's design principles of network simplification, all-IP transport, and support for multiple radio access technologies directly enabled the high-performance, low-latency experience of 4G LTE and laid the architectural groundwork that was later evolved into the 5G Core (5GC) with the introduction of service-based architecture and network slicing.
Purpose & Motivation
SAE was created to address the limitations of the pre-4G core network architectures, which were ill-suited for the anticipated massive growth in mobile data traffic. Previous 3GPP architectures, like the GPRS Core Network, were complex, with separate network elements for circuit-switched voice and packet-switched data, leading to inefficient resource utilization and higher latency. The rise of smartphones and bandwidth-hungry applications demanded a network that could deliver data faster, with lower latency, and at a lower cost per bit.
The primary motivation was to design a future-proof, simplified core network that could seamlessly support high-speed packet data from the new OFDMA-based LTE radio interface. Key problems it solved included architectural complexity, latency bottlenecks from multiple network hops, and the inability to efficiently support 'always-on' connectivity and advanced QoS mechanisms for diverse services. By moving to a flat, all-IP architecture with control and user plane separation, SAE drastically reduced the number of network nodes involved in data transmission, minimized latency, and simplified network management and deployment for operators.
Historically, SAE's development in 3GPP Release 8 was part of a parallel project with the LTE radio access network. It was driven by the need for a core network that could match the performance leap of the new radio technology and support the eventual migration of voice services to IP (VoLTE). It also aimed to provide a unified core for heterogeneous access, including legacy 3GPP (2G/3G) and non-3GPP networks, paving the way for true network convergence. This evolution was critical for operators to transition their networks to support the mobile broadband era efficiently.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-17.
In Release 17, the SAE architecture was enhanced to introduce support for User Plane IP for EPC connected architectures using NR PDCP, as indicated by the CR titles. This update facilitates Evolved Packet Core communications within packet-optimized systems supporting multiple radio access technologies. Additionally, the release addressed PDN connection release procedures for standalone P-GW interworking scenarios.
- V2X application layer architecture enhancement TS 23.286CR0022
- PDN connection release in case of standalone P-GW for interworking TS 24.301CR3580
- Introducing support of UP IP for EPC connected architectures using NR PDCP TS 36.300CR1353
- Introducing support of UP IP for EPC connected architectures using NR PDCP TS 36.331CR4763
In Release 18, the SAE (System Architecture Evolution) function was enhanced to introduce support for V2X application layer architecture in edge deployments. This extends the capabilities of the Evolved Packet Core framework to facilitate new, lower-latency communications for V2X services at the network edge. The update leverages the packet-optimized, multi-RAT foundation of the Evolved Packet System to enable these advanced application layer deployments.
- V2X application layer architecture support for edge deployments TS 23.286CR0072
Explore further
Broader topics and technologies where SAE plays a role.
Defining Specifications
3GPP specifications that define or reference SAE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.286 vj00 | V2X Application Enabler Architecture | Rel-19 |
| TS 23.795 vg10 | V2X Application Architecture Study | Rel-16 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 |
| TR 26.985 vj00 | Media Handling for Advanced V2X Services | Rel-19 |
| TR 29.909 vj00 | Diameter Usage Guidelines for 3GPP | Rel-19 |
| TS 32.582 vj00 | HNB Management Information Model for Type 1 Interface | Rel-19 |
| TS 32.584 vj00 | HNB OAM&P XML Definitions for Type 1 Interface | Rel-19 |
| TS 32.592 vj00 | HeNB OAM&P Information Model | Rel-19 |
| TS 32.594 vj00 | Data definitions for HeNB to HeMS Type 1 interface | Rel-19 |
| TS 32.821 v1900 | SON OAM Architecture for Home NodeB | Rel-9 |
| TS 33.821 v900 | LTE/SAE Security Threat Analysis and Countermeasures | Rel-9 |
| TS 33.822 v1800 | Security Architecture for Inter-Access Mobility | Rel-8 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 36.938 v900 | E-UTRAN to 3GPP2/Mobile WiMAX Mobility | Rel-9 |