MCPTT Emergency Group Call

Description

MCPTT Emergency Group Call (MEGC) is the actual service invocation and session establishment procedure that utilizes an MCPTT Emergency Group (MEG). It represents the end-to-end process of initiating, authorizing, establishing, and maintaining a real-time, typically half-duplex voice, group communication session targeted at a specific MEG. The service is a cornerstone of the 3GPP Mission Critical Services suite. Architecturally, it involves the MCPTT client on the user's device, the MCPTT application server, and the underlying 3GPP access and core networks (E-UTRAN/EPC or NG-RAN/5GC).

The workflow begins when an authorized MCPTT user activates the emergency group call function, specifying the target MEG identifier. The MCPTT client sends a service request to the MCPTT application server over the established signaling connection (using protocols like SIP over IMS). This request is marked as an emergency request. The MCPTT server performs several critical checks: it authenticates the user, verifies their authorization to initiate a call to the requested MEG, and retrieves the current member list for that MEG. Upon validation, the server initiates the media session establishment. A key differentiator of MEGC is its interaction with the network's policy and charging control (PCC) framework. The MCPTT server communicates with the Policy Control Function (PCF) to request the establishment of a dedicated, prioritized bearer (in 4G) or QoS Flow (in 5G) for the media stream. This bearer is assigned a high-priority QoS Class Identifier (QCI) or 5QI, often with pre-emption capabilities, to ensure the call is not blocked by congestion.

Simultaneously, the server signals to the MCPTT clients of all MEG members (except the initiator), alerting them to the incoming emergency group call. These alerts are typically intrusive and may override other device activities. Once the media path is established via the network's user plane functions (UPF in 5G, PGW in 4G), a one-to-many media distribution tree is formed, with the initiator's audio stream replicated to all group members. The server manages the floor control for the call, granting the right to speak according to MCPTT rules, which for emergency calls may involve pre-emptive or prioritized floor granting. The call persists until explicitly terminated, providing a stable channel for crisis coordination.

Purpose & Motivation

MEGC was created to fulfill the stringent requirement for instantaneous, guaranteed, and group-wide communication during public safety and emergency response operations. While general MCPTT group calls provide efficient team communication, they may not have the absolute priority and resource guarantees required for life-or-death situations. MEGC addresses this gap by defining a specialized, highest-priority service class within MCPTT. The problem it solves is the potential failure or delay of a critical group call due to network congestion, contention with other services, or complex setup procedures.

Historically, first responders used push-to-talk on LMR systems, where an emergency group call often meant switching to a dedicated, pre-allocated "emergency" channel or using a channel-grabbing feature. The purpose of standardizing MEGC in 3GPP (starting in Release 13) was to replicate and improve upon this capability in broadband LTE and 5G networks. It addresses the limitations of best-effort IP communication by mandating network-enforced priority end-to-end, from the radio interface through the core to the application server. This ensures that emergency communications from authorized personnel can pre-empt other network traffic, a critical capability during major incidents where public networks become congested. Its creation was motivated by the need for a standardized, interoperable, and carrier-grade emergency group call feature that could be deployed globally on commercial networks, enabling seamless cooperation between different agencies and across geographical boundaries.