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

Glossary term · Services

MCData imminent peril communication

Mission Critical Data Imminent Peril Communication

Services →

MCData imminent peril communication is a high-priority MCData group communication used in imminent peril situations that grants priority access and resource allocation to ensure mission-critical data delivery when lives are at risk.

Introduced
Rel-16
Where
Services › IMS
Specifications
2 specs
MCData imminent peril communication Description Purpose What changed Neighbours Specifications

Description

MCData imminent peril communication is a special type of group communication within the Mission Critical Data (MCData) service, introduced in 3GPP Release 16. It is designed for situations where there is an imminent threat to life or property, and data communication must be prioritized over other traffic. The concept mirrors the imminent peril communication defined for MCPTT voice, extending it to data services such as short messages, file transfers, and streaming.

In the MCData architecture, an imminent peril communication is initiated by an authorized user (e.g., a first responder) when they perceive an imminent danger. The MCData server, upon receiving the request, grants the communication elevated priority. This priority is enforced across the network: the underlying 3GPP network (LTE/5G) allocates radio resources with higher priority (e.g., via QoS Class Identifier or 5QI with priority scheduling), and the MCData server ensures that the data is delivered even under congestion. The communication is typically a group communication, meaning it is sent to a predefined group of recipients who are affiliated with the group.

The procedure involves several steps: the user's MCData client sends an imminent peril request to the MCData server, including the target group ID and an indication of the peril. The server authenticates and authorizes the user (checking that the user has the right to invoke imminent peril), then sets up the communication with the appropriate priority. The server may also notify a dispatcher or other authorized entities. The data is then transmitted with priority handling, and the recipients are informed of the imminent peril status.

Imminent peril communication is distinct from normal group communication in its priority treatment and authorization requirements. It may also have different charging or logging rules. The feature is critical for public safety and mission-critical users, as it ensures that vital data (e.g., a photo of a hazard, a file with evacuation plans) gets through even when the network is congested.

The definition of MCData imminent peril communication has remained unchanged since its introduction in Rel-16, indicating a stable specification. It is specified in TS 23.282 and TS 23.783, and relies on the underlying MCX priority and QoS mechanisms.

Purpose & Motivation

MCData imminent peril communication exists to guarantee that mission-critical data can be delivered with the highest priority when human life is at stake. In emergency situations, networks can become congested with traffic from many users. Without a priority mechanism, critical data from first responders might be delayed or lost. This feature solves that by allowing authorized users to flag a communication as imminent peril, which triggers priority handling throughout the network.

The concept was introduced in Rel-16 as an extension of the imminent peril communication already available for MCPTT voice. As MCData services matured, it became clear that data (e.g., images, files, location data) is equally important in emergencies. The feature builds on the MCX priority framework and the underlying 3GPP QoS mechanisms to provide end-to-end priority.

Prior to standardization, priority handling for data was inconsistent across vendors. 3GPP standardized imminent peril communication for MCData to ensure interoperable, predictable behavior, enabling first responders to rely on data services in the most critical moments.

What changed in its specifications

The latest release-to-release comparison of specifications that define MCData imminent peril communication. Each summary describes the whole specification, not only this term.

TS 23.282Rel-18 → Rel-19

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.

Rel-16 Initial

Initial definition introduced. Specified MCData imminent peril communication as an MC service imminent peril group communication within the MCData service, with procedures in TS 23.282 and TS 23.783.

Definition carried over unchanged from Rel-16; no textual modification to the term's description.

Definition carried over unchanged from Rel-16; no textual modification to the term's description.

Definition carried over unchanged from Rel-16; no textual modification to the term's description.

Definition carried over unchanged from Rel-16; no textual modification to the term's description.

Defining Specifications

3GPP specifications that define or reference MCData imminent peril communication, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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