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

Glossary term · Services

MEA

MCPTT Emergency Alert

Services →

MEA is a critical MCPTT feature that allows an authorized user to initiate a high-priority, network-wide emergency alert for rapid dissemination of information to all relevant personnel.

Introduced
Rel-13
Where
Services
Specifications
3 specs
MEA Description Purpose What changed Neighbours Detected Changes Specifications

Description

MCPTT Emergency Alert (MEA) is a specialized service defined within the 3GPP framework for Mission Critical Services (MCS), specifically under Mission Critical Push-To-Talk. It is a mechanism for initiating an emergency alert that is propagated with the highest priority across the MCPTT system. When a user triggers an MEA, it generates an alert notification that is distributed to a predefined group or to all users within a specific context, such as all members of an emergency response team or an entire organization. The alert carries metadata including the alert type, location of the initiating user, timestamp, and a unique identifier.

Architecturally, the MEA functionality involves several MCPTT system components. The MCPTT client on the user's device provides the interface to trigger the alert. Upon initiation, the client sends an MCPTT EMERGENCY ALERT request message to the MCPTT server over the MC services signaling path. The MCPTT server, which manages group communications and service logic, validates the request, applies any configured policies (e.g., verifying the user's authorization to send alerts), and then orchestrates the distribution. Distribution typically occurs via a combination of MCPTT group call establishment with emergency priority and/or via a separate alerting signaling channel to ensure receipt even if a call cannot be established. The server may also interact with other MC service entities like the MC Gateway for interconnection with other alerting systems.

How it works involves prioritized resource allocation. The network treats MEA signaling and associated media (like an alert tone or voice announcement) with pre-emptive priority. This means the network uses Quality of Service (QoS) mechanisms, such as allocating Guaranteed Bit Rate (GBR) bearers with a high Allocation and Retention Priority (ARP), to ensure the alert bypasses congestion. The alert is delivered to target users' devices, which then provide prominent indications—such as distinctive ringtones, screen pop-ups, and vibration—to capture immediate attention. The system also supports alert acknowledgment, allowing recipients to confirm receipt, and maintains logs for audit and post-incident analysis.

Purpose & Motivation

MEA was created to meet the stringent reliability and immediacy requirements of public safety and mission-critical organizations. It solves the problem of slow or unreliable emergency notification in traditional group communication systems. In high-stakes scenarios like natural disasters, terrorist incidents, or industrial accidents, the ability to instantly alert all relevant personnel can save lives and coordinate an effective response.

The motivation stems from the limitations of earlier professional mobile radio (PMR) systems and commercial cellular services, which lacked standardized, prioritized, and globally interoperable emergency alerting within a group communication context. 3GPP's work on Mission Critical Services over LTE (starting in Rel-13) aimed to provide broadband-enabled critical features. MEA is a direct response to user requirements from public safety agencies for a guaranteed, high-priority alert mechanism that works over commercial network infrastructure, providing a superior alternative to sirens, pagers, or non-prioritized SMS alerts.

What changed in its specifications

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

TS 24.379Rel-18 → Rel-19

Rel-19 adds participant-criteria handling for ad hoc group emergency alerts, a Reason header with cause 200 on session-leaving messages, and SIP 302 rejection for migrated MCPTT IDs. It also adds location-information conditions for INVITE and REFER requests, removes implicit floor grants from such requests, and changes prearranged group call and emergency alert authorisation rules.

Full comparison in TS 24.379 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 1 change
  • Interconnect - MCPTT Emergency alert procedures TS 24.379CR0756

Defining Specifications

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

SpecificationTitleRelease
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read
TS 36.579 3GPP TR 36.579 Rel-13 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read