Description
A Disaster Condition is a concept introduced in 3GPP Release 17 to address the need for continued telecommunications services during large-scale emergencies. It is defined as the condition that a government decides whether it is applicable or not based on, e.g., a natural disaster or a man-made disaster. When this condition applies, users may have the opportunity to mitigate service interruptions and failures. This definition has evolved slightly in later releases, with Rel-18 and Rel-20 emphasizing that the government decides when to initiate and terminate the condition, and Rel-19 stating that service interruptions and failures will be mitigated.
The Disaster Condition triggers a set of network behaviors aimed at ensuring that users can still communicate. In a disaster, the home PLMN (Public Land Mobile Network) may be partially or fully unavailable. The Disaster Condition allows users to register with other PLMNs that are operational, even if they do not have a roaming agreement with the home PLMN. This is known as Disaster Inbound Roaming. The network elements, such as the AMF (Access and Mobility Management Function) in 5G or the MME (Mobility Management Entity) in 4G, are enhanced to support this functionality.
The 3GPP specifications 22.011 (Service accessibility), 22.261 (Service requirements for the 5G system), 22.831 (Study on disaster roaming), 23.401 (GPRS enhancements for E-UTRAN access), and 23.501 (System architecture for the 5G System) define the requirements and procedures. The Disaster Condition is typically declared by a government authority, which then notifies the mobile network operators. The operators may then activate disaster roaming, allowing inbound roamers to attach to their networks. The network may also prioritize emergency calls and public warning messages.
The Disaster Condition is a temporary state; once the government declares it terminated, the special procedures are deactivated. The network must handle the transition gracefully, ensuring that users return to normal service. The concept is part of a broader effort to enhance network resilience and emergency response, leveraging the flexibility of 5G and beyond.
In summary, the Disaster Condition is a regulatory and technical trigger that enables networks to provide service continuity during disasters, focusing on inbound roaming and service mitigation.
Purpose & Motivation
The Disaster Condition was created to address the critical need for telecommunications services during disasters, when normal network operations may be disrupted. Before its introduction, users whose home networks failed could not easily access services from other networks, even if those networks were operational, due to roaming restrictions and lack of standardized procedures. This led to communication blackouts precisely when they were most needed.
The Disaster Condition provides a standardized mechanism for governments to declare an emergency, which then allows mobile operators to open their networks to inbound roamers from affected networks. This ensures that users can make emergency calls, access public warnings, and communicate with loved ones. It solves the problem of network isolation during disasters by enabling cross-network access.
Additionally, the Disaster Condition helps coordinate the response among operators and government agencies, ensuring that resources are used efficiently. It builds on existing roaming and emergency frameworks but adds specific triggers and procedures for disaster scenarios. The concept is part of 3GPP's ongoing efforts to enhance public safety and network resilience.
What changed in its specifications
The latest release-to-release comparison of specifications that define Disaster Condition. Each summary describes the whole specification, not only this term.
Rel-19 adds an optional Operator Controlled Lower Selection-priority PLMN Selector list, stored in USIM or ME, used during PLMN selection.
Full comparison in TS 22.011 →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 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference Disaster Condition, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.011 vl00 | Service Access and Roaming Procedures | Rel-21 read |
| TS 22.261 vk81 | 5G Service and Operational Requirements | Rel-20 read |
| TR 22.831 vh10 | Minimization of Service Interruption Study | Rel-17 read |
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |