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

Glossary term · IoT

IOPS-enabled UE

Isolated Operation for Public Safety enabled User Equipment

IoT →

IOPS-enabled UE is a user equipment configured to operate in Isolated Operation for Public Safety mode, enabling direct device-to-device and local network communication for mission-critical services when wide-area network coverage is unavailable.

Introduced
Rel-13
Where
Security
Specifications
3 specs
IOPS-enabled UE Description Purpose What changed Neighbours Specifications

Description

An IOPS-enabled UE (Isolated Operation for Public Safety enabled User Equipment) is a user equipment that is configured to use networks operating in IOPS mode. IOPS, defined in 3GPP Release 13, enables public safety users to maintain communication services when the network infrastructure is unavailable or isolated, such as during disasters or in remote areas. This capability is critical for mission-critical push-to-talk (MCPTT) and other public safety applications.

The IOPS-enabled UE operates in two primary modes: normal mode when connected to a fully operational network, and IOPS mode when the network is isolated or unavailable. In IOPS mode, the UE can communicate directly with other IOPS-enabled UEs using Proximity Services (ProSe) device-to-device communication, or it can connect to an isolated E-UTRAN node (eNodeB) that is operating without backhaul connectivity to the core network. The UE supports the necessary protocols and procedures to discover and communicate with other devices in proximity, as well as to maintain session continuity when transitioning between normal and IOPS modes.

Key technical aspects include the support for isolated E-UTRAN operation, where the eNodeB can function autonomously to provide local services. The IOPS-enabled UE must support the necessary security procedures, including authentication and authorization for IOPS mode, as specified in TS 33.401 and TS 33.897. The UE also supports the discovery of IOPS-capable networks and the selection of appropriate IOPS mode based on configuration and network availability. The UE may be pre-configured with IOPS settings or receive them from the network via NAS signaling.

The architecture for IOPS involves the UE, the isolated E-UTRAN, and optionally a local gateway or ProSe function. When the network is isolated, the eNodeB may connect to a local EPC (Evolved Packet Core) or operate in a standalone mode with limited functionality. The IOPS-enabled UE can establish communication with other UEs within the isolated network, and if the isolated network has connectivity to the central EPC, it can also communicate with UEs in the wider network. The UE supports the necessary bearer management, mobility, and session management procedures to enable seamless service continuity.

IOPS-enabled UEs are essential for public safety organizations such as police, fire, and emergency medical services. They ensure that first responders can communicate even when the commercial network is down or congested. The feature is part of the broader 3GPP efforts to enhance mission-critical communications, which also include MCPTT, MCVideo, and MCData. The IOPS capability is specified in 3GPP TS 23.401 for EPS, TS 33.401 for security, and TS 33.897 for study on IOPS security. The term has been stable since its introduction in Release 13, with no changes to its definition in subsequent releases up to Release 19.

Purpose & Motivation

The IOPS-enabled UE exists to address the critical need for public safety communication during network outages or in areas without coverage. Traditional cellular networks rely on centralized core network elements, which can become unavailable due to natural disasters, power failures, or backhaul disruptions. In such scenarios, first responders require reliable communication to coordinate rescue efforts and ensure their own safety. The IOPS feature, introduced in 3GPP Release 13, enables UEs to operate in an isolated mode, either by communicating directly with each other via ProSe or by connecting to an isolated E-UTRAN node that provides local services.

Before IOPS, public safety users had to rely on separate dedicated networks (e.g., TETRA or P25) that were expensive to deploy and maintain, and often lacked broadband capabilities. IOPS leverages commercial LTE technology to provide broadband public safety services, while adding the resilience needed for isolated operation. The IOPS-enabled UE is a key enabler of this capability, as it must support the additional procedures for isolated operation, including discovery, security, and session management. This allows public safety agencies to use a single device for both normal and emergency operations, reducing costs and improving interoperability.

The motivation for IOPS also includes the need for rapid deployment in temporary situations, such as large events or remote incidents, where network infrastructure may be temporarily unavailable or insufficient. By allowing UEs to form an isolated network, IOPS ensures that communication can be established quickly without relying on pre-existing infrastructure. This is particularly important for mission-critical services where even brief communication loss can have severe consequences.

What changed in its specifications

The latest release-to-release comparison of specifications that define IOPS-enabled UE. 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 introduction of IOPS-enabled UE in 3GPP specifications. Defined as a UE configured to use networks operating in IOPS mode, enabling isolated operation for public safety. The architecture and procedures for IOPS were specified in TS 23.401, with security aspects in TS 33.401 and TS 33.897.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

The definition of IOPS-enabled UE carried over unchanged from Release 13. No modifications to the term were made in this release.

Defining Specifications

3GPP specifications that define or reference IOPS-enabled UE, 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 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.897 vd10 Security for Isolated E-UTRAN Operation (IOPS) Rel-13 read