Description
Limited backhaul capability is a concept within Isolated E-UTRAN Operation for Public Safety (IOPS), defined in 3GPP TS 22.346 (Isolated E-UTRAN Operation for Public Safety) and referenced in TS 22.897 (Study on Isolated E-UTRAN Operation for Public Safety). IOPS addresses scenarios where a radio access network must continue to serve public safety users even when its connection to the core network (EPC) is degraded or absent — for example during a disaster, in remote areas, or when backhaul links fail.
IOPS distinguishes between two situations: operation with no backhaul capability to the EPC, and operation with limited backhaul capability to the EPC. In the no-backhaul case, the isolated E-UTRAN operates autonomously, typically with a local core or with functionality moved into the eNodeB, serving public safety UEs locally. In the limited-backhaul case, a narrow or unreliable link to the EPC remains available. Over this link, only the signalling of public safety UEs can be reliably communicated to the EPC. In addition, users may have the possibility to transmit a limited amount of user data, but with no guarantee of service.
The rationale is that signalling (e.g., for authentication, authorization, session management, and public safety service control) is essential and relatively low-bandwidth, so it can be prioritized over a constrained backhaul. User-plane traffic, by contrast, may be throttled, best-effort, or largely confined to local breakout within the isolated E-UTRAN. The network therefore needs mechanisms to prioritize public safety signalling, to decide which traffic is allowed over the limited link, and to manage the transition between normal, limited-backhaul, and no-backhaul operation.
Architecturally, IOPS with limited backhaul involves the isolated E-UTRAN (one or more eNodeBs) maintaining a control-plane connection to the EPC while handling most user-plane traffic locally or restricting it. Public safety UEs are identified and given priority treatment. The system must handle the case where the backhaul degrades further (transition to no backhaul) or recovers (return to normal operation), including the handling of contexts and sessions established during isolation.
The feature is part of the broader public safety portfolio alongside MCPTT and other MCX services, and it complements them by ensuring that the radio access and core connectivity survive adverse conditions. The definition has remained unchanged from Rel-13 through Rel-19, indicating a stable requirement that continues to be relevant as public safety networks evolve toward 5G, where similar isolation concepts are being studied for NG-RAN.
Purpose & Motivation
Limited backhaul capability exists to address the reality that public safety networks must remain operational when infrastructure is damaged or incomplete. During disasters, backhaul links (fibre, microwave, satellite) can be severed or degraded, yet first responders still need reliable communication. IOPS was created to specify how an E-UTRAN can continue serving public safety users in such conditions.
The limited-backhaul case is the middle ground between full connectivity and complete isolation. It recognizes that even a constrained link can carry essential signalling, allowing the EPC to remain aware of public safety UEs and to support authentication, authorization and service control, while user data may be severely restricted. This prioritization of signalling over user data ensures that the most critical control functions survive, and that the network can gracefully degrade rather than fail completely.
Introduced in Rel-13 as part of the initial IOPS work, the requirement has been carried forward unchanged through Rel-19. It provides a foundation for later work on isolated operation in 5G and for resilience features in mission-critical networks, where graceful degradation and priority for public safety traffic remain central design goals.
What changed in its specifications
The latest release-to-release comparison of specifications that define Limited backhaul capability. Each summary describes the whole specification, not only this term.
Rel-16 brings only minor changes to TS 22.346: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 22.346 →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.
Introduced within the IOPS requirements in TS 22.346 and the study in TS 22.897: isolated E-UTRAN may operate with no backhaul or with limited backhaul to the EPC, where only public safety UE signalling is reliably carried and limited user data may be sent without service guarantees.
Defining Specifications
3GPP specifications that define or reference Limited backhaul capability, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.346 vj00 | Isolated E-UTRAN Operation for Public Safety | Rel-19 read |
| TS 22.897 vd00 | Isolated E-UTRAN Operation for Public Safety | Rel-13 read |