Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

Macro EPC

Macro Evolved Packet Core

Core Network →

Macro EPC is the Evolved Packet Core that provides normal connectivity to core network functions for an eNodeB not operating in Isolated E-UTRAN Operation for Public Safety mode.

Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
4 specs
Also in
Security
Macro EPC Description Purpose What changed Neighbours Specifications

Description

The Macro EPC is a term used in 3GPP specifications to distinguish the regular, fully connected Evolved Packet Core (EPC) from the isolated EPC functionality used during Isolated E-UTRAN Operation for Public Safety (IOPS). In normal operation, an eNodeB connects to the Macro EPC, which provides the complete set of core network functions: Mobility Management Entity (MME) for signalling and mobility, Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) for user-plane routing, Home Subscriber Server (HSS) for subscription data, and Policy and Charging Rules Function (PCRF) for policy control. The Macro EPC is the default core network environment for LTE deployments and is defined in specifications such as TS 23.401 and TS 23.797.

When an eNodeB is in IOPS mode, it operates in an isolated fashion, often because backhaul to the core network is unavailable (for example, during a disaster or in remote areas). In that mode, the eNodeB may use a local EPC or isolated E-UTRAN functionality to maintain essential public safety services. The Macro EPC, by contrast, is the core network that serves the eNodeB when it is not in IOPS mode. This distinction is important for mobility, session management, and security procedures, because the anchor points and available services differ significantly between the two modes.

From an architectural standpoint, the Macro EPC provides the standard S1 interface connectivity to the E-UTRAN. The eNodeB establishes S1-MME and S1-U associations with the MME and S-GW respectively. The Macro EPC also enforces subscription-based QoS, charging, and policy control, and it supports interworking with other access networks such as 2G/3G and non-3GPP accesses. Security functions, including authentication and key agreement, are anchored in the Macro EPC via the MME and HSS, as described in TS 33.401. The term is also used in security and IOPS-related specifications (TS 33.897) to clarify which security procedures apply when the eNodeB is connected to the Macro EPC versus operating in isolated mode.

The Macro EPC concept matters because it provides a clear reference point for normal versus isolated operation. In public safety scenarios, the transition between Macro EPC connectivity and IOPS mode must be handled gracefully, with appropriate bearer and context management. The term helps specification writers and implementers distinguish the two operational states and ensures that procedures such as handover, paging, and bearer establishment are correctly scoped. It also supports testing and validation, as engineers can verify that an eNodeB behaves correctly when connected to the Macro EPC and when it falls back to isolated operation.

In later releases, the definition was refined to use the term eNodeB instead of eNB, reflecting a harmonization of terminology across 3GPP specifications. The Macro EPC remains a relevant concept for public safety LTE and for any scenario where isolated E-UTRAN operation is supported.

Purpose & Motivation

The Macro EPC term exists to clearly delineate the normal, fully connected core network from the isolated core network functionality used in IOPS. Public safety users require resilient communications even when backhaul to the core network is lost. IOPS allows an eNodeB to continue serving users in an isolated mode, but this mode has limited functionality and different security and mobility procedures. Without a clear term for the normal EPC, specifications would be ambiguous about which core network is being referenced in procedures and requirements.

Historically, the need arose with the development of LTE for public safety in Release 13. Earlier public safety systems, such as TETRA and P25, had their own isolated operation modes, but LTE introduced a packet-switched architecture where the core network plays a central role. The Macro EPC concept allowed 3GPP to define IOPS procedures as exceptions or alternatives to normal Macro EPC procedures, making the specifications easier to understand and implement.

The term also supports interoperability and roaming, as it clarifies that normal EPC services, including policy and charging, are available only when the eNodeB is connected to the Macro EPC. This distinction is essential for operators and public safety agencies to plan coverage and fallback strategies, and it remains a foundational concept in the 3GPP public safety framework.

What changed in its specifications

The latest release-to-release comparison of specifications that define Macro EPC. Each summary describes the whole specification, not only this term.

TS 23.401Rel-18 → Rel-19

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 →
TS 33.401Rel-18 → Rel-19

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.

Rel-13 Initial

Initial definition introduced: the EPC which serves an eNB when it is not in IOPS mode of operation. This established the distinction between normal Macro EPC connectivity and isolated IOPS operation for public safety.

Definition text carried over unchanged from Rel-13; no wording revision.

Definition text carried over unchanged from Rel-13; the term remained stable.

Wording changed from 'eNB' to 'eNodeB': the definition now reads 'the EPC which serves an eNodeB when it is not in IOPS mode of operation.' This was a terminology harmonization with no technical impact.

Definition text carried over unchanged from Rel-16; no further revision.

Definition text carried over unchanged from Rel-16; the term continued to be used as defined.

Definition text carried over unchanged from Rel-16; no change to the Macro EPC definition.

Definition text carried over unchanged from Rel-16; the term remains part of the glossary with the same meaning.

Defining Specifications

3GPP specifications that define or reference Macro EPC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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