Description
The Group Home MCPTT System is a foundational architectural concept in the 3GPP MCPTT specifications. In large mission-critical deployments, MCPTT services are not provided by a single monolithic system but by a federation of interconnected MCPTT systems, each potentially serving different organisations, regions or administrative domains. When a group is created, it must be defined somewhere: that 'somewhere' is its group home MCPTT system. The group home MCPTT system is therefore the authoritative owner of the group's definition, including its identity, membership and configuration.
The concept matters because group communication frequently spans system boundaries. A user served by one MCPTT system may need to communicate with a group whose home is a different MCPTT system. In such cases, the group home MCPTT system remains the reference point: it holds the group definition, and other systems interact with it to obtain group information and to support group calls. This separation between where a user is served and where a group is defined is essential for multi-agency and multi-vendor interoperability.
Architecturally, the group home MCPTT system contains the group management server that owns the group definition, as well as the MCPTT server that provides group services. When a group call involves users from multiple systems, the group home MCPTT system coordinates with the MCPTT servers of the participating systems. The related concept of the group host MCPTT server identifies the server within a system that provides centralised support for the group's services, and it is closely tied to the group home MCPTT system.
The group home MCPTT system also plays a role in group affiliation and group membership management. Because it is the authoritative source of the group definition, it determines which users are members and how the group is configured. Other systems rely on it for consistent group information, avoiding conflicting definitions across domains.
Introduced in Release 13, the term has been carried forward unchanged through Release 20. Its definition text has remained identical across all releases, reflecting the stability of the underlying architectural principle. The term appears in TS 23.179, TS 23.379, TS 23.781 and TS 23.783, which together cover MCPTT architecture, functional architecture, group management and group communication. For engineers designing multi-system MCPTT deployments, understanding the group home MCPTT system is essential for correctly placing group definitions and planning inter-system interfaces.
Purpose & Motivation
The Group Home MCPTT System exists to solve the problem of group ownership in a federated mission-critical environment. Mission-critical organisations rarely operate as a single homogeneous network; police, fire, ambulance and other agencies may each run their own MCPTT systems, yet they must communicate in shared groups. Without a clear notion of where a group is defined, group information could conflict across systems, and it would be unclear which system is authoritative.
By designating a group home MCPTT system for each group, the specifications provide a single source of truth. This enables consistent group management, unambiguous membership and reliable group communication across system boundaries. It also supports administrative autonomy: each organisation can define and manage its own groups within its own system while still participating in cross-system communication.
The concept was introduced in Release 13 alongside the first MCPTT architecture, when 3GPP recognised that mission-critical push-to-talk must support multi-domain deployments. It has remained unchanged through subsequent releases, demonstrating that the underlying design principle has proven robust as MCPTT has evolved.
What changed in its specifications
The latest release-to-release comparison of specifications that define Group home MCPTT system. 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
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Group home MCPTT system, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 read |
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TR 23.781 vf00 | Study on MC services migration & interconnection | Rel-15 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |