Description
MCData Emergency Alert (MDEA) is a standardized service within the 3GPP Mission Critical Services (MCX) suite, specifically under the Mission Critical Data (MCData) umbrella defined from Release 16. It provides mechanisms for authorized personnel (e.g., incident commanders, public safety agencies) to originate and disseminate time-sensitive emergency alerts to a defined population of MCData users or groups. The service is architected to guarantee delivery even in congested or degraded network conditions, leveraging the quality of service (QoS) and priority mechanisms of the underlying LTE or 5G network.
The MDEA functionality is realized through a set of logical functions and reference points as specified in TS 24.282 (MCData stage 3) and TS 37.579 (conformance testing). Key components include the MDEA Client, which resides on the user equipment (UE), and the MDEA Server, typically part of the MCData system infrastructure. The alert origination process involves an authorized user composing an alert message, which can include text, pre-defined templates, geographic target areas, severity levels, and acknowledgment requirements. This request is sent via the MCData service layer to the MDEA Server, which then manages the distribution.
The server employs group management and distribution functions to identify the target recipients based on the alert's criteria, such as group membership, location, or role. It then initiates the delivery using reliable transport protocols with explicit priorities. Alerts are pushed to client devices, triggering prominent visual and auditory notifications to ensure immediate user attention. The architecture supports end-to-end encryption for security and includes mechanisms for delivery status reporting and user acknowledgment, allowing the originator to track the alert's reach and effectiveness. This end-to-end process is integrated with the core MCData architecture, sharing common elements like identity management, group management, and security, ensuring a cohesive mission-critical ecosystem.
Purpose & Motivation
MDEA was created to address a critical gap in public safety communications: the need for a standardized, network-based, mass alerting capability for mission-critical users. Prior to its standardization, emergency alerts were often delivered via disparate systems like sirens, television broadcasts, or proprietary radio paging, which lacked targeting precision, delivery confirmation, and integration with modern data services used by first responders. The development of MDEA within the 3GPP MCX framework was motivated by the global push to leverage commercial LTE/5G networks for public safety, requiring feature parity with traditional land mobile radio (LMR) systems.
The technology solves the problem of rapidly communicating urgent situational awareness (e.g., hazardous material spills, active shooter locations, evacuation orders) to a dynamic set of responders in the field. Its creation was driven by lessons from major disasters where communication breakdowns hampered response efforts. MDEA provides a digital, IP-based alerting system that can be integrated with other MCX services like mission-critical push-to-talk (MCPTT) and mission-critical video (MCVideo), creating a unified command and control platform.
Furthermore, MDEA leverages the inherent advantages of 3GPP networks, such as wide geographic coverage, high bandwidth for rich alerts, and sophisticated device ecosystems. It addresses limitations of previous approaches by offering granular targeting (by group, location, or role), mandatory priority treatment over network resources, and guaranteed delivery receipts. This ensures that critical information reaches the right personnel reliably and promptly, enhancing operational coordination and responder safety during emergencies.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (157 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the MDEA (MCData Emergency Alert) function was introduced as a notification from an MCData client to the MCData service to signal a user's emergency condition. The release included foundational protocol work, such as clarifications for encoding MCData signalling and payload content, corrections to SDS Session procedures, and fixes for encoding Information Elements in MONP messages. This established the core signalling control for the emergency alert state and its associated procedures within the MCData architecture.
- Clarification of encoding of MCData signalling content and MCData payload content TS 24.282CR0063
- Completed IANA registrations for MCData TS 24.282CR0048
- Fix issues with encoding of IEs in MONP messages for MCData TS 24.282CR0050
- Rel-14 completed IANA registrations for MCData TS 24.282CR0062
- Removing IP Address from media-level section in SDP body for MCData Standalone SDS using media plan, SDS Session and FD using media plane TS 24.282CR0065
- Corrections in MCData SDS Session TS 24.282CR0070
In Release 16, the MDEA (MCData Emergency Alert) function was introduced as a new capability, allowing an MCData client to send a notification of an emergency condition to the MCData service. This release specified comprehensive procedures for sending, canceling, and handling these alerts both on-network and, for the first time, in off-network scenarios. It also defined the necessary supporting client and server procedures, including the handling of alerts at participating and controlling servers, and integrated this new emergency alerting function with existing MCData communication features.
- Emergency Alerts for MCData – General sections TS 24.282CR0066
- Emergency Alerts for MCData – sending origination request, on-network TS 24.282CR0067
- Emergency Alerts for MCData – cancelation, on-network TS 24.282CR0068
- Add Location procedures for MCData TS 24.282CR0072
- PF side procedures – Initiating MCData communication using pre-established session TS 24.282CR0085
- Add signalling plane capability to support transmission / reception via MBMS in MCData TS 24.282CR0092
+ 31 more changes
In Release 17, key enhancements for MCData Emergency Alert (MDEA) included the introduction of procedures for on-network private communication emergency, applicable even to pre-established sessions, and the addition of client-side handling for emergency alert area notifications. The release also defined specific states for emergency and imminent peril communications, while adding altitude and accuracy details to the MCData location information schema to improve situational awareness.
- Add preconfigured regroup to MCData TS 24.282CR0182
- Add altitude, timestamp to MCData location TS 24.282CR0187
- On-network grp emrgcy and imm peril comms – Updt to emrgcy alert TS 24.282CR0211
- Emergency alert area notification handling at client side for MCData TS 24.282CR0212
- Limiting the number of MCData emergency group participations per FA TS 24.282CR0219
- Add Application metadata container - MCData TS 24.282CR0200
+ 43 more changes
In Release 18, the MDEA (MCData Emergency Alert) function was enhanced to specifically support emergency alerts for MCData clients that affiliate to a group after that group has already moved to an emergency alert state. This ensures late-joining clients are properly notified of the ongoing emergency condition. The release also included updates for location information requests and triggers involving MCData UEs, which can support emergency alerting scenarios.
- MCData Standalone SDS over signalling control plane to group regroup TS 24.282CR0340
- Use of 5G MBS transmission in MCData signalling plane TS 24.282CR0350
- Addition of 5G MBS inter-RAT information in MCData signalling TS 24.282CR0349
- Decoupling of signalling and media plane for MCData IP Connectivity TS 24.282CR0353
- Add the description of 5MBS in MCData TS 24.282CR0354
- Support MCData over 5G ProSe TS 24.282CR0360
+ 42 more changes
In Release 19, the MDEA (MCData Emergency Alert) function was enhanced by modifying the criteria for determining participants during an ongoing ad hoc group emergency alert. Specifically, the SIP message containing the participant lists sent to authorized users was updated to add criteria for the alert. These changes were accompanied by general corrections and clarifications to the ad hoc group emergency alert procedures.
- Adding application data to MCData IPcon TS 24.282CR0426
- Modify list of participants by changing the criteria during an ongoing MCData ad hoc group data communication TS 24.282CR0447
- Adhoc group emergency alert add criteria to the SIP message containing the participant lists sent to the authorised users TS 24.282CR0450
- MCData adhoc group call to migrated user TS 24.282CR0448
- Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert TS 24.282CR0456
- FRMCS_Ph5 Adding reason to leave a session in MCData TS 24.282CR0461
+ 11 more changes
Explore further
Broader topics and technologies where MDEA plays a role.
Defining Specifications
3GPP specifications that define or reference MDEA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.282 vj50 | MCData Signalling Control Protocols | Rel-19 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |