MCPTT Emergency Private Call

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.

Key Features

• One-to-one private voice call initiated with emergency priority
• Preempts network resources and lower-priority communications using QoS mechanisms (high-priority 5QI/QCI)
• Requires authorization; only authorized MCPTT users can initiate or receive an MEPC
• Targeted call setup to a specific user identity (e.g., dispatcher ID)
• Integral logging and recording for audit trails and post-incident analysis
• Works within the overarching MCPTT service architecture, interfacing with MCPTT Server and 3GPP core policy functions

Evolution Across Releases

Defining Specifications