Description
The MCPTT Private Emergency Alert (MPEA) is a specialized service component defined within the 3GPP Mission Critical Services suite, specifically for the MCPTT application. Unlike a regular group emergency alert, which is broadcast to all members of a talkgroup, a Private Emergency Alert is a targeted, point-to-point or point-to-multipoint urgent communication. The architecture for MPEA leverages the underlying MCPTT service framework, which includes an MCPTT client on the user device, an MCPTT application server, and utilizes 3GPP IP Multimedia Subsystem (IMS) core for session control and authentication. The alert is initiated by an authorized MCPTT user through their client, which sends a specific SIP MESSAGE request or utilizes dedicated emergency procedures to the MCPTT server.
The MCPTT server, upon receiving the MPEA request, validates the originator's authorization and processes the alert. It then routes the alert to the intended recipient(s) based on a private user identity or a private group identity. The signaling ensures the alert is delivered with the highest priority, pre-empting other traffic if necessary. Key protocol specifications are covered in 24.379 (MCPTT call control), while the conformance testing aspects are detailed in 36.579 and 37.579. The recipient's MCPTT client, upon receipt, must provide an unambiguous and intrusive indication—such as a distinct sound, persistent visual notification, and vibration—to ensure immediate attention, even if the device is in silent mode or engaged in another call.
How it works involves a defined message structure containing the alert type, originator identity, timestamp, and optional location information. The server may also log the alert for audit trails. The service ensures privacy by restricting the alert content and recipient list from being disclosed to unauthorized parties. Its role in the network is to provide a secure, reliable, and immediate channel for life-critical notifications within professional organizations like police, fire brigades, and industrial teams, where standard group communication may not be appropriate for sensitive emergencies.
Purpose & Motivation
MPEA was introduced in 3GPP Release 13 as part of the broader standardization of Mission Critical Services over LTE (and later 5G). Prior to its standardization, professional mobile radio (PMR) systems like TETRA or P25 had proprietary emergency features, but interoperability and broadband integration were limited. The motivation for MPEA stemmed from the operational needs of public safety agencies, where there are scenarios requiring a discreet, high-priority alert to a specific commander or a specialized team without causing panic or revealing tactical information to a wider group.
It addresses the limitation of a blanket group emergency call, which, while effective for general alerts, is not suitable for situations like covert operations, personal duress, or notifying a specific medic about a casualty. MPEA solves this by providing a targeted, private, yet high-priority communication path within the standardized MCPTT framework. Its creation was driven by user requirements from public safety organizations globally, ensuring that LTE/5G-based critical communications could match or exceed the functional capabilities of legacy narrowband systems, thereby facilitating the transition to broadband PPDR (Public Protection and Disaster Relief) networks.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (187 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the MCPTT Private Emergency Alert (MPEA) function was introduced, establishing the "MCPTT private emergency alert state" as the client's internal perspective of such an alert targeted to a specific user. This release also defined new procedures for managing the alert's lifecycle, including mechanisms for a user to "enter-exit emergency alert area" and criteria for "MCPTT Emergency location triggering." Additionally, the release specified the distinct states for "in-progress emergency private call" and the handling of private call procedures during such emergencies.
- Remotely initiated private call client procedures TS 24.379CR0356
- Remotely initiated private call server procedures TS 24.379CR0357
- Managing functional alias – MCPTT server serving the user TS 24.379CR0390
- Managing functional alias – MCPTT server owning the functional alias TS 24.379CR0391
- Enter-Exit emergency alert area TS 24.379CR0411
- Corrections to mcpttinfo.xsd TS 24.379CR0383
+ 4 more changes
In Release 16, the MCPTT Private Emergency Alert (MPEA) function was enhanced to support the use of functional aliases within emergency alerts, allowing for more flexible identification of users. Furthermore, procedures were introduced for the MCPTT server to automatically trigger an emergency group call following an emergency alert, streamlining the response process. The release also included mechanisms for the server to maintain a list of group members who did not acknowledge an emergency group call request, improving alert accountability.
- Restricting incoming private communications - call control TS 24.379CR0481
- Using functional alias in private calls – client procedures TS 24.379CR0482
- Using functional alias in private calls – server procedures TS 24.379CR0483
- Triggering an emergency group call after an emergency alert automatically TS 24.379CR0485
- List of MCPTT group members who did not acknowledge the group call request TS 24.379CR0486
- Support of functional aliases in emergency alerts TS 24.379CR0500
+ 14 more changes
In Release 17, the MCPTT Private Emergency Alert (MPEA) function was enhanced through new interconnect procedures, enabling emergency alerts to be initiated and managed across different MCPTT systems. This specifically involved defining the "Interconnect - MCPTT Emergency alert procedures" to standardize how alerts are originated and controlled between a Primary and a Partner MCPTT system. These updates ensured that the MCPTT private emergency alert state could be properly coordinated in interconnected deployments.
- Add altitude, timestamp to MCPTT location XML schema TS 24.379CR0625
- Call transfer for MCPTT private call, call control part TS 24.379CR0673
- Add accuracy to MCPTT location XML schema TS 24.379CR0698
- Call forwarding for MCPTT private call, call control part TS 24.379CR0709
- Interconnect - MCPTT Gateway Server functional entity TS 24.379CR0720
- Interconnect - MCPTT Pre-arranged group originating participating procedures TS 24.379CR0721
+ 56 more changes
In Release 18, the MCPTT Private Emergency Alert (MPEA) function was enhanced to support initiating alerts to clients performing late affiliation and to define procedures for ad-hoc group emergency alerts. These additions ensure emergency alerts can reach users who affiliate to a group after an incident begins and can be initiated within dynamically created ad-hoc group sessions. The release also specified the internal client state management for MCPTT private emergency alerts targeted to an individual MCPTT user.
- MCPTT Chat group join to group regroup TS 24.379CR0855
- Addition of 5G MBS inter-RAT information in MCPTT signalling TS 24.379CR0873
- MC GW UE functions in MCPTT TS 24.379CR0901
- General adhoc group call procedures in single system - Protoc impl for MCPTT TS 24.379CR0902
- Add the description of 5MBS in MCPTT TS 24.379CR0899
- Support MCPTT over 5G ProSe TS 24.379CR0905
+ 65 more changes
In Release 19, the MCPTT Private Emergency Alert (MPEA) function was enhanced by modifying the criteria for determining participants during an ongoing ad hoc group emergency alert. These changes included adding specific criteria to the SIP message containing participant lists sent to authorized users and providing additional information for ad hoc group emergency alert cancellation. Furthermore, corrections and clarifications were made to the controlling MCPTT server operations for users not authorized to receive MCPTT ad hoc group emergency alert participant information.
- Modify list of participants by changing the criteria during an ongoing MCPTT ad hoc group call TS 24.379CR1004
- Adhoc group emergency alert add criteria to the SIP message containing the participant lists sent to the authorised users TS 24.379CR1014
- MCPTT adhoc group call to migrated user TS 24.379CR1015
- Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert TS 24.379CR1018
- Adhoc group call release by an authorized user (MCPTT) TS 24.379CR1022
- FRMCS_Ph5 Adding reason to leave a session in MCPTT TS 24.379CR1029
+ 18 more changes
Explore further
Broader topics and technologies where MPEA plays a role.
Defining Specifications
3GPP specifications that define or reference MPEA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.379 vj50 | Mission Critical Push To Talk (MCPTT) call control | Rel-19 |
| TS 36.579 | 3GPP TR 36.579 | Rel-13 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |