Description
The MCPTT client is defined in 3GPP TS 23.379 (Functional architecture and information flows for Mission Critical Push To Talk) and referenced in TS 23.783 (MC services architecture). It is the UE-side application entity that implements the client half of the MCPTT service. An MCPTT client is an instance of the generic MC service client, specialized to provide the client application function for push-to-talk: it initiates and receives group and private calls, manages talker arbitration, handles media encoding and decoding, and communicates with the MCPTT server using standardized protocols.
The MCPTT architecture separates client and server functions. The MCPTT client resides on the MCPTT UE and interacts with the MCPTT server in the network. Between them, the client uses SIP for session control (call setup, modification, and teardown) and RTP/RTCP for media transport and control. The client also interacts with supporting functions: it obtains identity and authentication through the identity management framework, retrieves service configuration from the configuration management server, and uses group management information to know which groups it may call. The client is responsible for presenting the push-to-talk user experience, including floor control indications, participant lists, and emergency call handling.
A key function of the MCPTT client is floor control. In a push-to-talk system, only one participant speaks at a time, and the client must request the floor from the floor control server, receive grants and revocations, and reflect the floor state to the user. The client also handles the media burst, buffering and transmitting voice when the floor is granted. For group calls, the client participates in the group session established via the MCPTT server, receiving media from the media distribution function and sending its own media when it holds the floor.
The client also supports a range of MCPTT features beyond basic calls: emergency calls and imminent peril calls with priority handling, private calls between individual users, chat groups, location reporting, and media storage. It interacts with the MC service client common functions that are shared across MCPTT, MCVideo, and MCData, which is why the definition describes it as an instance of an MC service client rather than a standalone application. This common-client architecture allows a single UE application framework to host multiple MC service clients.
In operation, the MCPTT client registers with the MCPTT service, authenticates the user, downloads configuration, and then can initiate or receive calls. It maintains awareness of the user's affiliation with groups, which determines whether the client is invited to group calls. Because MCPTT is designed for mission-critical use, the client must support priority and pre-emption, resilience mechanisms such as server failover, and offline or isolated operation where feasible. The client is thus a substantial application entity, not merely a thin media endpoint, and its standardized behavior is essential for interoperability between vendors in public safety networks.
Purpose & Motivation
The MCPTT client exists to standardize the UE-side behavior of mission-critical push-to-talk, enabling interoperable PTT services across vendors and networks. Before MCPTT, push-to-talk was implemented through proprietary technologies, most notably narrowband land mobile radio systems and vendor-specific cellular PTT solutions. These were closed ecosystems: a device from one vendor could not interoperate with infrastructure from another, and integration with broadband data services was limited.
3GPP Release 13 introduced MCPTT as the first mission-critical service over LTE, and Release 14 refined the architecture and aligned it with the broader MC services framework. The MCPTT client is the component that makes the standardized service usable on the device: by defining its functions, protocols, and interactions with the server, 3GPP ensures that any compliant client can work with any compliant server. This is the foundation of multi-vendor mission-critical broadband, allowing agencies to mix devices and infrastructure and to migrate from narrowband to LTE and 5G.
The client concept also supports the separation of service logic from the underlying radio access, so that MCPTT can operate over LTE, 5G, and future access technologies, and can be combined with MCVideo and MCData in a unified MC service client framework.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCPTT client. Each summary describes the whole specification, not only this term.
Rel-19 adds clauses for ad hoc group call release, leave and criteria modification. It also covers emergency private call and floor remote triggers, floor revoke, and extended ad hoc group call setup.
Full comparison in TS 23.379 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MCPTT client, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |