Description
An MCPTT group is the core logical entity in Mission Critical Push To Talk (MCPTT) service that defines a set of users who can communicate with one another using group calls. The group is defined independently of the underlying transport or network type, meaning the same group identity and membership can be used over LTE, 5G, Wi-Fi, or fixed access, and across different MCPTT service providers. This abstraction is essential for mission-critical users such as public safety officers, who must be able to reach their team regardless of which network they are currently attached to.
Architecturally, the MCPTT group is managed by the MCPTT server, which is part of the Mission Critical Services (MCX) architecture defined in 3GPP TS 23.379. The group identity is a globally unique identifier (MCPTT Group ID) that is used in session establishment, floor control, and authorization decisions. Group membership and configuration data are stored in the group management server (GMS) and are provisioned via the MCPTT user profile. The group identity is carried in SIP signalling (TS 24.481) as part of the group call request, and the MCPTT server uses it to determine which users should be invited to the call and which QoS treatment applies.
Group communication in MCPTT uses a centralized floor control mechanism. When a user requests the floor, the MCPTT server arbitrates among all affiliated group members and grants the floor to one user at a time (or multiple users in a configured mode). The group identity is the key used to bind the floor control queue, the media distribution tree, and the policy and charging rules. Because the group is defined independently of transport, the MCPTT server can use unicast or multicast delivery, and can interwork with legacy Land Mobile Radio (LMR) systems through gateways.
The group also plays a central role in affiliation management. A user must affiliate with a group before they can receive group calls; affiliation is the mechanism by which the MCPTT server knows which users are currently reachable and interested in the group. This is covered by the companion terms MCPTT group affiliation and MCPTT group de-affiliation. The group definition itself includes attributes such as group priority, allowed call types (e.g., emergency, imminent peril), and maximum number of simultaneous talkers.
In the broader 3GPP ecosystem, the MCPTT group concept has been extended to other mission-critical services such as MCVideo and MCData, where analogous group definitions exist. The group is also a key input to the 5G Mission Critical Services architecture, where network slicing and QoS flows can be tailored per group. The definition has remained stable since Rel-13, reflecting the maturity of the group model and its importance as a stable anchor for interoperability across releases and vendors.
Purpose & Motivation
The MCPTT group exists to provide a stable, network-independent identity for a set of users who need to communicate as a team. Before MCPTT, mission-critical group communication was typically provided by proprietary Land Mobile Radio systems, where group membership was tied to a specific radio network and could not easily span technologies or operators. The MCPTT group abstracts the team away from the transport, enabling seamless operation across LTE, 5G, and non-3GPP access, and allowing a single group identity to be used for authorization, floor control, and policy enforcement.
The group concept also solves the problem of scalable group management. Instead of configuring each user-to-user relationship, administrators define groups once and assign users to them. This simplifies provisioning, supports dynamic reorganization of teams, and enables features such as group priority and emergency group calls. The independence from transport means that the same group can be used when users are on different networks, which is critical for multi-agency responses and for users who roam between networks.
Finally, the MCPTT group provides a foundation for interoperability with legacy systems. Through gateways, an MCPTT group can be mapped to an LMR talkgroup, allowing a phased migration from LMR to LTE/5G while preserving the operational concept of a talkgroup. This motivation drove the initial Rel-13 definition and continues to guide extensions in later releases.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCPTT group. 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 →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 (6 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MCPTT group, 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.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 |
| TS 24.481 vj30 | MCS Group Management Protocol | Rel-19 read |