Description
An IOPS-capable eNB is an LTE base station that supports Isolated E-UTRAN Operation for Public Safety (IOPS). IOPS is a 3GPP feature introduced in Rel-13 to enable public safety users (e.g., police, fire, ambulance) to maintain communication when the backhaul link between the radio access network and the core network is unavailable, such as during a disaster, power outage, or remote deployment. The IOPS-capable eNB is equipped with a local core network function, known as the Local EPC, which provides essential EPC services (e.g., MME, S-GW, P-GW, HSS) in a compact form factor. When the eNB detects loss of backhaul to the macro EPC, it can transition to IOPS mode and serve IOPS-enabled UEs in its coverage area using the Local EPC.
The architecture of IOPS involves several key components. The IOPS-capable eNB must support the S1 interface to both the macro EPC and the Local EPC, and it must be able to detect backhaul failure and trigger a switchover. The Local EPC is typically co-located with the eNB or connected via a local link, and it may be pre-provisioned with subscription data for IOPS-enabled UEs. The UEs must also be IOPS-enabled, meaning they support the necessary procedures to attach to the Local EPC and use local IP services. The IOPS mode operation is transparent to the UEs to some extent, but they may need to perform a re-attach or PDN connection establishment towards the Local EPC.
When in IOPS mode, the eNB provides local IP connectivity, allowing UEs to communicate with each other and with local application servers (e.g., dispatch servers) without traversing the macro EPC. This is crucial for push-to-talk (PTT) and group communication services used by public safety. The eNB may also support public safety services such as Mission Critical Push To Talk (MCPTT) via local application functions. The Local EPC may have limited functionality compared to the macro EPC, but it includes the essential functions for authentication, authorization, and bearer management to support voice and data.
The IOPS feature is specified in 3GPP TS 23.401 (GPRS enhancements for E-UTRAN access) and TS 23.797 (Study on architecture enhancements to support isolated E-UTRAN operation for public safety). Security aspects are covered in TS 33.401 and TS 33.897. The IOPS-capable eNB must ensure that security is maintained even when operating in isolated mode, using pre-shared keys or local credentials. The feature also includes procedures for transitioning back to normal mode when backhaul is restored, including synchronizing state with the macro EPC.
IOPS is particularly relevant for rural and remote areas where backhaul may be unreliable, as well as for temporary deployments (e.g., emergency response). The eNB may be mobile (e.g., mounted on a vehicle) and powered by batteries or generators. The IOPS-capable eNB must be able to operate in a standalone manner, possibly with reduced capacity, and must prioritize public safety users. The feature has evolved over releases, with refinements to the architecture and procedures, but the core definition has remained stable since Rel-13.
Purpose & Motivation
The IOPS-capable eNB exists to address a critical gap in public safety communications: the reliance on backhaul connectivity to the core network. In conventional LTE networks, if the backhaul between the eNB and the EPC is severed (e.g., due to a natural disaster, fiber cut, or power outage), the eNB becomes unusable, and first responders lose communication exactly when they need it most. Previous solutions involved deploying standalone systems or using different technologies (e.g., TETRA), but these lacked the broadband capabilities of LTE. IOPS was created to allow LTE eNBs to continue providing services in isolation by embedding core network functionality locally.
The motivation was to ensure mission-critical voice and data services remain available during emergencies. Public safety users require reliable, secure, and group-oriented communication. IOPS enables local IP connectivity and public safety services (e.g., MCPTT) via a Local EPC, allowing users to communicate with each other and with local command centers. This is particularly important for incident area networks where temporary coverage is needed. The feature also supports the concept of a deployable system that can be rapidly set up in the field.
Historically, IOPS was introduced in Rel-13 as part of 3GPP's broader efforts to enhance public safety communications, which also included MCPTT and GCSE. The feature builds on the existing EPC architecture but adds the concept of a Local EPC and procedures for isolated operation. It addresses the limitations of previous approaches that either required full core network connectivity or used proprietary solutions. By standardizing IOPS, 3GPP ensures interoperability and enables a wide ecosystem of devices and infrastructure.
What changed in its specifications
The latest release-to-release comparison of specifications that define IOPS-capable eNB. 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 IOPS-capable eNB, 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 |