Description
MCData emergency communication is a specific mode of the Mission Critical Data (MCData) service, defined in TS 23.282, that applies when a user is in an emergency situation. It is defined as an MC service emergency group communication or an MC service emergency private communication within the MCData service. In other words, it is the MCData realization of the generic MC emergency communication concept, covering both group-based and one-to-one data communications initiated under emergency conditions.
Emergency communication in the MC framework is a distinct operational state. When an MC user declares an emergency, the MC service system elevates the user's communications to emergency priority, granting them preferential treatment in the network and in the MC service infrastructure. For MCData, this means that emergency group data sessions and emergency private data communications receive higher priority, can pre-empt other traffic, and are handled with the reliability and availability guarantees appropriate to life-critical operations. The emergency state is signaled through the MC service protocols and is recognized by the MCData server and the underlying 3GPP network.
The MCData emergency communication builds on the general MCData communication procedures. An emergency group communication involves an MCData group whose members participate in a data session under emergency conditions, while an emergency private communication is a one-to-one data exchange between two MC users in emergency mode. The MCData client initiates the emergency communication, and the MCData server manages the session, including participant authorization, priority handling, and delivery. The emergency state may be associated with the user's emergency indication, which is propagated to the relevant MC service entities.
From an architectural perspective, MCData emergency communication relies on the same functional entities as normal MCData communication: the MCData client on the UE, the MCData server, the group management server, the configuration management server, and the identity management server. The difference lies in the policies and priority treatment applied. The configuration management server provisions the emergency-related parameters, and the MCData server enforces emergency priority during session establishment and data delivery. The underlying 3GPP network provides the QoS treatment, including priority and pre-emption, that supports the emergency communication.
Emergency communication is a fundamental requirement for public safety and critical communications. The MCData emergency communication ensures that data services—such as sharing incident information, distributing alerts, or exchanging critical files—remain available and prioritized when users are in emergency situations, complementing the emergency voice and video services in the overall MC service system.
Purpose & Motivation
MCData emergency communication exists to guarantee that mission critical data services remain available and prioritized when users face emergency situations. In public safety operations, the ability to exchange data—incident details, maps, alerts, and instructions—can be as important as voice communication. Without a dedicated emergency mode, data traffic could be delayed or dropped during congestion, precisely when it is most needed.
The concept addresses the limitations of treating all data communications equally. Standard MCData communications are already prioritized relative to commercial traffic, but emergency communications require an even higher level of treatment: they must be able to pre-empt other sessions, receive the highest QoS, and be handled with special procedures by the MC service infrastructure. The 3GPP MC framework introduced emergency communication as a first-class concept, and MCData emergency communication extends it to the data service.
Introduced in Rel-16, MCData emergency communication reflects the maturation of the MCData service, which began in Rel-14 with basic data communications. As MCData deployments grew, the need for standardized emergency data handling became clear, and the emergency group and private communication modes were defined to ensure interoperability and consistent priority treatment across vendors and networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCData emergency communication. Each summary describes the whole specification, not only this term.
Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.
Full comparison in TS 23.282 →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.
Defining Specifications
3GPP specifications that define or reference MCData emergency communication, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.282 vk31 | Mission Critical Data Architecture | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |