Description
The MCPTT Emergency Private Call (MEPC) is a specialized communication service defined within the 3GPP Mission Critical Services (MCS) framework, specifically under Mission Critical Push-To-Talk (MCPTT). It is a call type designed for urgent, confidential communication between an individual in distress (the emergency initiator) and a specific responder, typically a dispatcher or team leader, during a critical incident. Unlike a group emergency call, which broadcasts to a pre-defined group, the MEPC establishes a dedicated, one-to-one audio channel. The call is initiated with a high-priority emergency request that preempts other network resources and ongoing communications if necessary.
Architecturally, MEPC operates within the MCPTT application layer, which is hosted on User Equipment (UE) and in the network on MCPTT Application Servers. The key components involved are the MCPTT Client on the user's device, the MCPTT Server (which manages call control and media distribution), and the underlying 3GPP core network (EPC or 5GC) which provides the prioritized connectivity. When a user triggers an MEPC, the MCPTT Client sends a specific service request to the MCPTT Server. This request contains indicators marking it as an Emergency Private Call, including the identity of the target user (the intended recipient). The MCPTT Server authenticates the request, validates the user's authorization to make such a call, and then processes it with the highest priority.
The workflow involves several steps. First, the initiating client sends an MCPTT EMERGENCY private call request message to the server. The server then sends an incoming call notification to the target user's client. Upon acceptance, a dedicated media path is established between the two parties. Crucially, the 3GPP network's Quality of Service (QoS) mechanisms are invoked. The MCPTT Server interacts with the Policy and Charging Rules Function (PCRF in EPC) or Policy Control Function (PCF in 5GC) to ensure the call's media flows are assigned the highest QoS Class Identifier (QCI or 5QI), such as those reserved for mission critical voice. This guarantees minimal packet delay and loss. Furthermore, the call is private, meaning no other users can join or monitor it without authorization. The call remains active until explicitly ended by one of the parties, and the server logs the event for audit and incident review purposes, which is a key requirement for public safety communications.
Purpose & Motivation
MEPC was created to address a critical gap in traditional group-based emergency communications for first responders and mission-critical users. In high-stress operational scenarios, such as a police officer needing immediate backup or a firefighter reporting a trapped victim, broadcasting to an entire group may not be appropriate. It could cause unnecessary panic, clutter the shared channel, or compromise operational security. The purpose of MEPC is to provide a direct, immediate, and confidential line to a specific command authority or specialist who can provide precise instructions or dispatch targeted assistance without alerting others.
It solves the problem of communication overload and lack of discretion during emergencies. Before standardized MCPTT features like MEPC, professional radio systems often had limited call types—typically group calls and all-calls. An individual in need had to use the shared group channel, potentially blocking it for others and lacking privacy. MEPC introduces a structured, prioritized private channel that coexists with group communications. It ensures that the most urgent, individualized requests for help get through reliably, even when the network is congested, by leveraging the 3GPP's standardized priority and preemption mechanisms.
The development of MEPC was motivated by the global public safety community's requirements for LTE and 5G-based mission-critical services, as captured in projects like 3GPP's work on MCPTT starting in Release 13. It addresses the limitations of legacy Land Mobile Radio (LMR) systems and early VoIP push-to-talk services, which lacked sophisticated, standardized emergency call variants. By defining MEPC within the 3GPP suite, it ensures interoperability across different vendors' equipment and networks, which is paramount for joint operations between different agencies. It forms an essential component of the broader MCPTT service, fulfilling the requirement for flexible, reliable, and immediate voice communication in life-threatening situations.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (186 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 Emergency Private Call (MEPC) function was enhanced with new procedures for remotely initiated private calls, both from the client and server side. The release also introduced capabilities for managing functional aliases across different MCPTT servers and established specific triggering criteria for MCPTT emergency location. Furthermore, it provided corrections for handling private call procedures, including answer modes and off-network call type control.
- 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, key enhancements for the MEPC (MCPTT Emergency Private Call) function included the ability to use functional aliases in private calls, both in client and server procedures, and support for functional aliases in emergency alerts. Furthermore, the release introduced mechanisms for restricting incoming private communications and allowed emergency and imminent peril calls even when the maximum number of simultaneous sessions was reached.
- 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
+ 13 more changes
In Release 17, the MCPTT Emergency Private Call (MEPC) function was enhanced with new call control features, specifically adding support for call transfer and call forwarding for MCPTT private calls. Furthermore, significant work was done to enable interconnect procedures for MCPTT private calls between different systems, expanding emergency communications capabilities. The release also introduced more detailed location reporting by adding altitude, timestamp, and accuracy attributes to the MCPTT location XML schema.
- 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, key enhancements for MCPTT Emergency Private Call (MEPC) included new procedures for initiating emergency alerts within ad hoc group calls and support for emergency alerts to clients performing late affiliation. The release also introduced mechanisms for handling private calls to users that have migrated to a partner system, ensuring continuity during critical communications.
- 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 Emergency Private Call (MEPC) function was enhanced with specific procedures for emergency remote floor requests and refined criteria for participant determination during ongoing ad hoc group emergency alerts. The release also introduced the ability for an authorized user to release an ad hoc group call and added clarifications for private call transfer and forwarding operations. Furthermore, corrections and additional information were provided for the cancellation of ad hoc group emergency alerts and for handling user participation in group regroups.
- 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 MEPC plays a role.
Defining Specifications
3GPP specifications that define or reference MEPC, 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 |