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

Glossary term · Radio Access Network

IOPS network

Isolated Operation for Public Safety Network

Radio Access Network →

IOPS network is a self-contained public safety system of eNodeBs and a Local EPC that provides autonomous cellular service when the connection to the central core network is lost.

Introduced
Rel-13
Where
Core Network › Evolved Packet Core
Specifications
3 specs
IOPS network Description Purpose What changed Neighbours Specifications

Description

An IOPS network is a self-contained cellular network deployment that operates independently of the central core network when backhaul connectivity is lost. It is defined in 3GPP specifications such as TS 23.401, TS 23.798, and TR 33.897, and was first introduced in Rel-13 for LTE. The IOPS network comprises one or more eNodeBs (eNBs) that are configured to operate in IOPS mode, along with a Local Evolved Packet Core (Local EPC) that provides the core network functions locally. This architecture allows public safety users to continue communicating even when the central EPC is unreachable.

The IOPS network is typically deployed in scenarios where a permanent or temporary local coverage is needed, such as at incident scenes, remote areas, or during disasters. The eNodeBs in the IOPS network are connected to the Local EPC via standard interfaces (S1), and the Local EPC handles all the necessary control and user plane functions, including authentication, mobility management, session management, and policy enforcement. The Local EPC may be a compact, ruggedized version of the EPC, designed for field deployment.

When the backhaul link to the central EPC is available, the IOPS network can operate in a normal mode, connected to the central core. However, when the backhaul is lost, the network transitions to IOPS mode, where the Local EPC takes over and the eNodeBs continue to serve users without interruption. The transition is designed to be seamless, with minimal impact on ongoing sessions. The IOPS network may also support connectivity to other IOPS networks or to the central core via alternative backhaul (e.g., satellite) if available.

Key components of the IOPS network include the eNodeBs, the Local EPC (which may include MME, SGW, PGW, PCRF, and HSS functions), and the interfaces between them. The network also includes security functions to ensure that only authorized users can access the services, and to protect the integrity and confidentiality of communications. The IOPS network is designed to be interoperable with the central network, so that when backhaul is restored, user sessions and data can be synchronized.

The IOPS network is a critical enabler for mission critical communications, providing resilience and continuity for public safety operations. It is specified in 3GPP TS 23.401 (General Packet Radio Service enhancements for E-UTRAN), TS 23.798 (IOPS study), and TR 33.897 (security aspects). The concept has evolved over releases, with refinements to the architecture and procedures, but the core definition has remained consistent: an IOPS network consists of one or more eNodeBs operating in IOPS mode and connected to a Local EPC.

Purpose & Motivation

The IOPS network was created to provide a standardized solution for maintaining cellular communications when the backhaul connection between the radio access network and the central core network is lost. This is particularly important for public safety users, such as police, fire, and emergency medical services, who rely on their networks for critical communications. Without IOPS, a backhaul failure would result in a complete loss of service, which could have severe consequences during emergencies.

Prior to the introduction of IOPS in Rel-13, there was no standardized way to handle isolated operation in LTE networks. Some vendors offered proprietary solutions, but these lacked interoperability and could not guarantee a consistent level of service. The IOPS network concept was developed to fill this gap, providing a clear architecture and set of procedures for autonomous operation. It leverages the existing LTE/EPC architecture but allows for a local core network (Local EPC) to take over when the central core is unreachable.

The IOPS network solves the problem of service continuity by enabling a local, self-sufficient network that can serve users independently. It ensures that public safety personnel can continue to communicate, coordinate, and respond effectively even when the central infrastructure is damaged or unavailable. The concept has been refined over multiple releases, with enhancements for security, interoperability, and support for mission critical services. Today, the IOPS network is a foundational element of resilient public safety communications, and its principles are being extended to 5G and beyond.

What changed in its specifications

The latest release-to-release comparison of specifications that define IOPS network. 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 →

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 of the IOPS network. An IOPS network consists of one or more eNBs operating in IOPS mode and connected to a Local EPC. This release introduced the concept of isolated operation for public safety in LTE, allowing a local core network to serve eNodeBs when backhaul is lost.

The definition carried over unchanged from Rel-13. The term 'eNB' was still used, and the architecture remained the same. No significant changes to the IOPS network concept were made in this release.

The definition carried over unchanged from Rel-14. The term 'eNB' was still used, and the architecture remained the same. No significant changes to the IOPS network concept were made in this release.

The definition was updated to use the term 'eNodeB' instead of 'eNB'. The core meaning remained the same: an IOPS network consists of one or more eNodeBs operating in IOPS mode and connected to a Local EPC. This change reflects a terminology alignment in the specifications.

The definition carried over unchanged from Rel-16. The term 'eNodeB' was used, and the architecture remained the same. No significant changes to the IOPS network concept were made in this release.

The definition carried over unchanged from Rel-17. The term 'eNodeB' was used, and the architecture remained the same. No significant changes to the IOPS network concept were made in this release.

The definition carried over unchanged from Rel-18. The term 'eNodeB' was used, and the architecture remained the same. However, in this release, the IOPS network concept was extended to support mission critical services through the introduction of the IOPS MC system and IOPS mode of operation for MC services.

Defining Specifications

3GPP specifications that define or reference IOPS network, 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.798 vf00 IOPS with Limited Backhaul Enhancements Study Rel-15 read
TS 33.897 vd10 Security for Isolated E-UTRAN Operation (IOPS) Rel-13 read