Description
The MCPTT system is the overarching architectural concept defined by 3GPP for Mission Critical Push To Talk (MCPTT) services. It encompasses all the applications, services, and enabling capabilities required to provide push-to-talk communication with mission-critical quality, availability, and security. The system is built on the 3GPP IP Multimedia Subsystem (IMS) and leverages the Evolved Packet Core (EPC) or 5G Core (5GC) for connectivity, but it adds a dedicated set of functional entities to handle group communication, floor control, and priority handling.
At its core, the MCPTT system comprises several key functional entities. The MCPTT Server is the central application server that manages MCPTT sessions, group calls, and floor control. It interacts with the Group Management Server (GMS) for group definitions, the Identity Management Server (IdMS) for authentication and authorization, the Key Management Server (KMS) for security, and the Configuration Management Server (CMS) for user and group configuration. The MCPTT Client resides on the MCPTT UE and provides the user interface and protocol handling for push-to-talk operations. The system also includes the EPS/5GS as the underlying network, providing bearers with appropriate QoS (e.g., Mission Critical services use QCI 65/66 or 5QI 65/66/67/69/70) and priority mechanisms such as Access Class Barring and Pre-emption.
The MCPTT system supports both on-network and off-network operation. On-network operation uses the cellular infrastructure, while off-network (direct mode) allows UEs to communicate directly using ProSe (Proximity Services) when network coverage is unavailable. The system also defines a migration path between these modes. The architecture is designed for high availability, with redundancy and failover mechanisms for critical servers.
Floor control is a fundamental mechanism in MCPTT: only one user can speak at a time in a group call. The MCPTT Server implements a floor control protocol (based on RTCP or HTTP) to arbitrate requests, grant the floor, and manage queuing. The system also supports functional aliases, which allow users to be identified by aliases (e.g., "Police Officer 1") rather than IMPUs, and location reporting for dispatcher use.
The MCPTT system is defined in 3GPP TS 22.179 (service requirements), TS 23.179 (architecture), and TS 23.781 (functional architecture and information flows). It is part of the broader Mission Critical Services (MCX) framework, which also includes MCVideo and MCData. The system is designed to interoperate with legacy Land Mobile Radio (LMR) systems through interworking functions, enabling a smooth transition for public safety organizations.
Purpose & Motivation
The MCPTT system was created to provide a standardized, cellular-based alternative to proprietary Land Mobile Radio (LMR) systems used by public safety and mission-critical organizations. LMR systems (such as TETRA, P25, or DMR) are typically narrowband, expensive to deploy, and offer limited data capabilities. They also lack the economies of scale and innovation of commercial cellular networks. 3GPP recognized the need for a mission-critical push-to-talk service that could leverage LTE and later 5G networks, providing wide-area coverage, broadband data, and interoperability with commercial devices.
The MCPTT system solves several problems: it enables push-to-talk communication with guaranteed priority and pre-emption, ensuring that emergency responders can communicate even during network congestion. It provides group communication with floor control, location reporting, and dispatcher functions, all essential for coordinated operations. It also supports off-network direct communication for situations where infrastructure is unavailable. The system is designed to meet the stringent requirements of mission-critical users, including high availability, security, and quality of service.
Historically, mission-critical communication was dominated by LMR technologies, which are still widely used. The MCPTT system represents a shift towards broadband mission-critical services, allowing integration of voice, video, and data. It was first specified in Release 13 and has evolved with subsequent releases to add features like MCVideo and MCData, forming a comprehensive MCX ecosystem.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCPTT system. Each summary describes the whole specification, not only this term.
Rel-17 added Mission Critical Push-to-talk Phase 3 to TS 22.179, covering general overview, Figure 6.15.3.1.1, and requirements. It also changed three other related items in the same release.
Full comparison in TS 22.179 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced the MCPTT system as the collection of applications, services, and enabling capabilities required to provide Mission Critical Push To Talk for a Mission Critical Organization. This release established the foundational architecture and service requirements.
Defining Specifications
3GPP specifications that define or reference MCPTT system, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.179 vl00 | MCPTT Service Requirements | Rel-21 read |
| TS 23.779 vd00 | MCPTT over LTE Stage 2 Study | Rel-13 read |
| TR 23.781 vf00 | Study on MC services migration & interconnection | Rel-15 read |