Description
The Evolved Packet Core (EPC) is the foundational core network architecture for the 3GPP 4G LTE system, introduced as a clean-slate design to support high-speed, low-latency packet data services. It represents a significant departure from the circuit-switched cores of 2G/3G, adopting an all-IP, simplified, and flat architecture. The EPC's primary function is to manage data sessions, provide connectivity between User Equipment (UE) and external packet data networks (like the internet or IMS), and handle critical control-plane and user-plane operations for mobility and security.
Architecturally, the EPC comprises several key logical nodes interconnected via standardized interfaces. The central control-plane entity is the Mobility Management Entity (MME), responsible for signaling, bearer management, authentication, and mobility tracking. The Serving Gateway (S-GW) acts as the local mobility anchor, routing and forwarding user data packets and managing handovers between eNodeBs. The Packet Data Network Gateway (P-GW) is the point of exit and entry for traffic to external networks; it performs policy enforcement, charging, and IP address allocation. For subscriber data and authentication, the Home Subscriber Server (HSS) serves as the central database. The user-plane path is streamlined: data flows from the eNodeB through the S-GW to the P-GW, minimizing latency. The control plane uses the S1-MME interface to connect the eNodeB to the MME and the S11 interface between the MME and S-GW for session management.
How the EPC works involves a coordinated sequence of procedures. When a UE attaches to the network, it initiates a procedure with the MME, which authenticates the user via the HSS. Upon successful authentication, the MME establishes a default bearer by communicating with the S-GW and P-GW, which assigns an IP address to the UE. This bearer represents a virtual pipe with specific Quality of Service (QoS) characteristics. All subsequent user data travels through this bearer path. For mobility, as a UE moves, the MME orchestrates handovers, updating the S-GW's context to seamlessly reroute the data path. The EPC also supports dedicated bearers for services requiring specific QoS, like VoIP. Its role is absolutely central: it is the intelligent hub that enables seamless mobility, ensures security, enforces operator policies, and provides the gateway to the broader internet and service platforms, making LTE's high-performance data experience possible.
Purpose & Motivation
The Evolved Packet Core was created to address the limitations of previous 3GPP core networks, which were built around a dual-domain architecture with separate circuit-switched cores for voice and packet-switched cores for data. This separation was inefficient for the burgeoning demand for mobile broadband data and converged services. The primary motivation for EPC was to support the LTE radio access network's high data rates and low latency with a simplified, cost-effective, and scalable core that used Internet Protocol (IP) for all services, including voice (via VoLTE).
Historically, the work began in 3GPP Release 8, building upon earlier packet core concepts from GPRS and UMTS. The EPC solved key problems: it eliminated the network complexity and cost of maintaining parallel circuit and packet cores, reduced latency through a flatter architecture with fewer nodal hops, and provided a future-proof foundation for all-IP services. It was designed from the outset to handle massive growth in data traffic, sophisticated QoS for different applications, and seamless mobility not just within LTE but also to and from legacy 3GPP and non-3GPP networks (like WiFi). The creation of EPC was a strategic move to enable mobile operators to compete with fixed broadband providers and support the new era of smartphones and connected devices.
Key Features
- All-IP, flat architecture minimizing latency and network complexity
- Separation of control plane (MME) and user plane (S-GW, P-GW)
- Support for seamless mobility within LTE and to/from other 3GPP and non-3GPP access
- Policy and Charging Control (PCC) integration for dynamic QoS and charging
- Network-based mobility management using GTP protocol in the user plane
- Foundation for Voice over LTE (VoLTE) via interconnection with the IP Multimedia Subsystem (IMS)
Evolution Across Releases
The Evolved Packet Core was initially standardized in Release 8 as the core network for LTE. This foundational release defined the key architectural nodes—MME, S-GW, P-GW, HSS—and their interfaces (S1, S11, S5/S8, etc.). It established the all-IP, flat architecture principle, introduced the concept of EPS bearers for QoS, and defined procedures for initial attach, bearer management, and inter-eNodeB handover, setting the blueprint for 4G core networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.801 | 3GPP TS 22.801 |
| TS 23.041 | 3GPP TS 23.041 |
| TS 23.139 | 3GPP TS 23.139 |
| TS 23.179 | 3GPP TS 23.179 |
| TS 23.180 | 3GPP TS 23.180 |
| TS 23.261 | 3GPP TS 23.261 |
| TS 23.280 | 3GPP TS 23.280 |
| TS 23.281 | 3GPP TS 23.281 |
| TS 23.369 | 3GPP TS 23.369 |
| TS 23.379 | 3GPP TS 23.379 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.402 | 3GPP TS 23.402 |
| TS 23.434 | 3GPP TS 23.434 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.701 | 3GPP TS 23.701 |
| TS 23.758 | 3GPP TS 23.758 |
| TS 23.839 | 3GPP TS 23.839 |
| TS 23.857 | 3GPP TS 23.857 |
| TS 23.882 | 3GPP TS 23.882 |
| TS 23.894 | 3GPP TS 23.894 |
| TS 23.896 | 3GPP TS 23.896 |
| TS 24.139 | 3GPP TS 24.139 |
| TS 24.244 | 3GPP TS 24.244 |
| TS 24.301 | 3GPP TS 24.301 |
| TS 24.302 | 3GPP TS 24.302 |
| TS 24.303 | 3GPP TS 24.303 |
| TS 24.304 | 3GPP TS 24.304 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.801 | 3GPP TS 24.801 |
| TS 24.890 | 3GPP TS 24.890 |
| TS 24.980 | 3GPP TS 24.980 |
| TS 25.322 | 3GPP TS 25.322 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 26.501 | 3GPP TS 26.501 |
| TS 26.802 | 3GPP TS 26.802 |
| TS 26.924 | 3GPP TS 26.924 |
| TS 26.941 | 3GPP TS 26.941 |
| TS 28.627 | 3GPP TS 28.627 |
| TS 28.707 | 3GPP TS 28.707 |
| TS 28.708 | 3GPP TS 28.708 |
| TS 28.709 | 3GPP TS 28.709 |
| TS 28.802 | 3GPP TS 28.802 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 29.168 | 3GPP TS 29.168 |
| TS 29.172 | 3GPP TS 29.172 |
| TS 29.273 | 3GPP TS 29.273 |
| TS 29.274 | 3GPP TS 29.274 |
| TS 29.275 | 3GPP TS 29.275 |
| TS 29.279 | 3GPP TS 29.279 |
| TS 29.507 | 3GPP TS 29.507 |
| TS 29.513 | 3GPP TS 29.513 |
| TS 29.826 | 3GPP TS 29.826 |
| TS 29.866 | 3GPP TS 29.866 |
| TS 29.890 | 3GPP TS 29.890 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 31.121 | 3GPP TR 31.121 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.252 | 3GPP TR 32.252 |
| TS 32.295 | 3GPP TR 32.295 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.404 | 3GPP TR 32.404 |
| TS 32.426 | 3GPP TR 32.426 |
| TS 32.455 | 3GPP TR 32.455 |
| TS 32.521 | 3GPP TR 32.521 |
| TS 32.541 | 3GPP TR 32.541 |
| TS 32.593 | 3GPP TR 32.593 |
| TS 32.751 | 3GPP TR 32.751 |
| TS 32.752 | 3GPP TR 32.752 |
| TS 32.816 | 3GPP TR 32.816 |
| TS 32.820 | 3GPP TR 32.820 |
| TS 32.823 | 3GPP TR 32.823 |
| TS 32.826 | 3GPP TR 32.826 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.401 | 3GPP TR 33.401 |
| TS 33.402 | 3GPP TR 33.402 |
| TS 36.113 | 3GPP TR 36.113 |
| TS 36.124 | 3GPP TR 36.124 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.304 | 3GPP TR 36.304 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.401 | 3GPP TR 36.401 |
| TS 36.410 | 3GPP TR 36.410 |
| TS 36.413 | 3GPP TR 36.413 |
| TS 36.414 | 3GPP TR 36.414 |
| TS 36.423 | 3GPP TR 36.423 |
| TS 36.424 | 3GPP TR 36.424 |
| TS 36.440 | 3GPP TR 36.440 |
| TS 36.444 | 3GPP TR 36.444 |
| TS 36.445 | 3GPP TR 36.445 |
| TS 36.455 | 3GPP TR 36.455 |
| TS 36.456 | 3GPP TR 36.456 |
| TS 36.463 | 3GPP TR 36.463 |
| TS 36.876 | 3GPP TR 36.876 |
| TS 36.887 | 3GPP TR 36.887 |
| TS 36.927 | 3GPP TR 36.927 |
| TS 37.113 | 3GPP TR 37.113 |
| TS 37.483 | 3GPP TR 37.483 |
| TS 37.985 | 3GPP TR 37.985 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.413 | 3GPP TR 38.413 |
| TS 38.463 | 3GPP TR 38.463 |
| TS 38.473 | 3GPP TR 38.473 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.848 | 3GPP TR 38.848 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 43.129 | 3GPP TR 43.129 |