Description
A Local EPC (Local Evolved Packet Core) is an entity defined in 3GPP specifications (TS 23.401, TS 23.797, TS 33.401, TS 33.897) that provides core network functionality for eNodeBs operating in Isolated E-UTRAN Operation for Public Safety (IOPS) mode. In normal operation, eNodeBs connect to a macro EPC that provides mobility management, session management, and gateway functions. However, in public safety scenarios such as disasters or remote areas, the macro EPC may be unreachable. IOPS mode allows eNodeBs to continue providing communication services by using a Local EPC instead of the macro EPC.
The Local EPC is essentially a compact, deployable EPC that can be co-located with or near the eNodeBs. It includes the essential core network functions needed for basic connectivity: Mobility Management Entity (MME) functionality for tracking and paging, Serving Gateway (S-GW) and PDN Gateway (P-GW) functions for user-plane routing, and often a local Home Subscriber Server (HSS) or authentication proxy for subscriber authentication. The Local EPC may be implemented as a standalone physical entity or as a virtualized function running on edge infrastructure. It connects to the eNodeBs via the S1 interface, just like a macro EPC, but with a reduced feature set optimized for public safety use.
When eNodeBs enter IOPS mode, they establish S1 connections to the Local EPC. The Local EPC authenticates users (possibly using pre-provisioned credentials or a local HSS), establishes bearers, and manages mobility within the isolated cluster. It may also provide local breakout for IP traffic, allowing public safety users to communicate with each other and access local services even without connectivity to the macro network. The Local EPC can synchronize with the macro EPC when connectivity is restored, enabling seamless transition back to normal operation.
Security is a critical aspect, addressed in TS 33.401 and TS 33.897. The Local EPC must support authentication and key agreement procedures, possibly using a local authentication server, and must protect the S1 interface. Because the Local EPC may be deployed in physically insecure environments, additional security measures such as tamper resistance and secure boot are considered. The specifications define procedures for secure attachment and handover between IOPS and macro EPC modes.
The Local EPC concept was introduced in Release 13 and has evolved through Release 20. The definition changed slightly in Release 16, replacing 'eNBs' with 'eNodeBs' for consistency. The concept is part of the broader IOPS framework, which also includes isolated E-UTRAN operation, proximity services (ProSe), and group communication enablers. The Local EPC enables public safety agencies to deploy rapidly deployable networks that are self-contained yet interoperable with the macro network when available.
Purpose & Motivation
The Local EPC exists to ensure continuity of critical communications for public safety users when the macro EPC is unavailable. In disaster scenarios, the macro core network may be damaged or unreachable due to power outages, backhaul failures, or physical destruction. Without a core network, eNodeBs cannot authenticate users, establish bearers, or route traffic, leaving first responders without communication. The Local EPC solves this by providing a deployable, localized core network that can operate independently and support essential services.
The motivation is rooted in the requirements of public safety organizations, which need resilient, rapidly deployable communication systems. Traditional cellular networks are centralized and vulnerable to single points of failure. The IOPS work in 3GPP Release 13 aimed to address this by defining isolated operation modes. The Local EPC is a key enabler, allowing eNodeBs to switch from macro EPC to local EPC when the backhaul is lost, and to switch back when connectivity is restored.
Historically, public safety communications relied on dedicated technologies like TETRA or P25, which have limited data capabilities. The Local EPC leverages LTE technology to provide broadband data, video, and voice over a deployable core. It also supports interoperability with the macro network, so that users can roam between isolated and normal coverage. The concept has been refined over releases to improve security, mobility, and integration with 5G, ensuring that public safety users have robust, resilient communications in all scenarios.
What changed in its specifications
The latest release-to-release comparison of specifications that define Local EPC. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.
Full comparison in TS 33.401 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Local EPC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.797 vd00 | Isolated E-UTRAN Operation for Public Safety (IOPS) | Rel-13 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.897 vd10 | Security for Isolated E-UTRAN Operation | Rel-13 read |