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

Glossary term · Services

IOPS

Isolated E-UTRAN Operations for Public Safety

Services →

IOPS is a 3GPP feature enabling LTE base stations to operate independently from the core network during emergencies, providing critical local communication for public safety personnel when the wider network is unavailable.

Introduced
Rel-13
Where
Services
Specifications
15 specs
Also in
Security, Core Network
IOPS Description Purpose What changed Neighbours Detected Changes Specifications

Description

Isolated E-UTRAN Operations for Public Safety (IOPS) is a specialized operational mode defined in 3GPP specifications that allows a cluster of LTE radio access network (E-UTRAN) nodes, specifically evolved NodeBs (eNBs), to provide local communication services without a connection to the Evolved Packet Core (EPC) or 5G Core (5GC). In this mode, the eNBs form a self-contained network, managing radio resources, mobility, and basic session management autonomously. The architecture for IOPS involves one eNB acting as an Anchor eNB, which assumes control plane functions typically handled by the core network, such as mobility management and bearer context storage. Other eNBs in the cluster operate as Assisting eNBs, connecting to the Anchor eNB via the X2 interface.

How IOPS works begins with a trigger, such as a loss of backhaul connection to the EPC or a manual command. Eligible eNBs (pre-configured for IOPS) enter the isolated state. The Anchor eNB establishes itself, often through a pre-defined priority mechanism, and begins broadcasting system information indicating IOPS operation. Public Safety User Equipment (PS UE), which is specially configured to support IOPS, can then attach to this isolated network. The Anchor eNB performs a localized version of attachment and authentication, potentially using pre-stored credentials or a local authentication server if available. It manages the radio bearers for voice, video, and data services within the limited geographical coverage of the eNB cluster.

Key components include the IOPS-capable eNB (with enhanced software), IOPS-capable PS UE, and potentially a local application server (e.g., for Group Communication System Enablers). The X2 interface between eNBs is crucial for supporting mobility (handovers) within the isolated cluster. The system supports essential public safety services like mission-critical push-to-talk (MCPTT), location services, and emergency alerting. All communication is confined to the local radio coverage area; there is no connectivity to the public internet or other external networks unless a gateway function is locally implemented.

IOPS's role is to provide a lifeline communication network when the infrastructure is compromised due to natural disasters, terrorist attacks, or technical failures. It ensures that first responders can continue to coordinate using high-speed LTE-based services even in the absence of network infrastructure. Specifications such as TS 23.401 (GPRS enhancements for E-UTRAN access) and TS 33.401 (3GPP system architecture security) define the procedures and security mechanisms for IOPS, including how to securely transition UEs into and out of the isolated mode and how to protect the local communications.

Purpose & Motivation

IOPS was created to address a critical vulnerability in early LTE networks for public safety: complete dependence on the core network and transport backhaul. Traditional cellular networks are centralized; if the core network sites or the links to them fail, the entire radio access network becomes inoperative. This is unacceptable for mission-critical public safety communications, where reliability is paramount during crises that often damage infrastructure. Prior to IOPS, public safety agencies relied on dedicated land mobile radio (LMR) systems for local resilience, but these lacked the high-speed data capabilities of LTE.

The motivation for standardizing IOPS within 3GPP was to enable LTE to become a true broadband replacement for legacy LMR systems, but without sacrificing resilience. It solves the problem of "single point of failure" inherent in the centralized EPC architecture. By allowing eNBs to operate autonomously, IOPS ensures that communication can be maintained among first responders at a disaster site even if the nearest core network node is destroyed or isolated. This capability was a key requirement from public safety organizations worldwide as they planned their transition to 3GPP-based broadband networks.

Historically, the feature was driven by requirements from entities like the First Responder Network Authority (FirstNet) in the USA and other national public safety bodies. Its development in Release 13 was part of a broader 3GPP effort on Mission Critical services. IOPS addresses the limitations of previous commercial cellular technology, which was designed for efficiency and scalability in stable conditions, not for survivability in extreme scenarios. It enables a hybrid model where public safety networks can benefit from wide-area commercial-grade LTE services normally, but seamlessly fall back to resilient, localized operation when needed, all on the same network infrastructure and devices.

What changed in its specifications

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

TS 22.261Rel-18 → Rel-19

Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.

Full comparison in TS 22.261 →
TS 22.281Rel-16 → Rel-17

Rel-17 brings only minor changes to TS 22.281: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 22.281 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change
  • Dedicated Bearers for Ethernet in EPC - IOPS / LIPA / SIPTO@LN aspects TS 23.401CR3508
Rel-19 7 changes
  • Updates to sections 10.6.1.4 and 10.7 to support generic IOPS TS 23.180CR0001
  • Updates to sections 10.5.1.3, 10.5.1.4, 10.5.3.1, and 10.5.3.3 to support generic IOPS TS 23.180CR0002
  • Updates to clauses 2 and 3 (References, Definitions, Abbreviations) to support access agnostic IOPS TS 23.180CR0010
  • Updates to clause 1 (Scope) to support access generic IOPS TS 23.180CR0011
  • Update the IOPS network deployment TS 23.180CR0012
  • Updates to clause 10.2.2.3 (IOPS discovery request) to support access generic IOPS TS 23.180CR0014

+ 1 more changes

Rel-20 1 change
  • Clarification about security for MC over IOPS TS 33.180CR0236

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk81 5G Service and Operational Requirements Rel-20 read
TS 22.281 vj00 Mission Critical Video (MCVideo) Service Requirements Rel-19 read
TS 22.282 vj00 Mission Critical Data Service Requirements Rel-19 read
TR 22.879 ve00 Mission Critical Video over LTE Feasibility Study Rel-14 read
TS 22.880 ve00 Mission Critical Data Communications Study Rel-14 read
TS 23.180 vj20 Mission Critical Services in IOPS Mode Rel-19 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.778 vg00 Mission Critical Services in Isolated E-UTRAN (IOPS) Rel-16 read
TS 23.797 vd00 Isolated E-UTRAN Operation for Public Safety (IOPS) Rel-13 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.700 3GPP TR 33.700 Rel-13 read
TS 33.897 vd10 Security for Isolated E-UTRAN Operation (IOPS) Rel-13 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read