Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Partner MCPTT System

Partner Mission Critical Push-to-Talk System

Services →

Partner MCPTT System is an allied MCPTT system that provides push-to-talk service to a user based on the MCPTT User Profile defined in that user's Primary MCPTT System, enabling cross-system PTT for public safety and critical communications.

Introduced
Rel-13
Where
Services
Specifications
3 specs
Partner MCPTT System Description Purpose What changed Neighbours Specifications

Description

The Partner MCPTT System is the MCPTT-specific instantiation of the allied system concept in 3GPP mission critical services. Defined in TS 23.779 (the MCPTT architecture specification) and referenced in TS 22.179 (service requirements) and TS 33.880 (security), it describes an MCPTT system that serves an MCPTT User whose home subscription and profile reside in a different, Primary MCPTT System. The relationship between the two systems is governed by an inter-system agreement that establishes trust, security associations, and operational procedures.

MCPTT is a push-to-talk service built on LTE and 5G networks, providing group and individual voice communication with floor control, priority handling, and mission-critical quality. The architecture comprises an MCPTT server (handling call control, group management, and floor control), an MCPTT client on the user equipment, a group management server, an identity management server, a key management server, and supporting functions such as the participating and controlling MCPTT functions. When a user roams into the domain of a Partner MCPTT System, the Partner system's MCPTT server handles the call control and floor control for that user, but it does so using the user's MCPTT User Profile obtained from the Primary MCPTT System.

The MCPTT User Profile is the authoritative record of the user's service authorization: which groups the user belongs to, what priority the user has, which services (e.g., private calls, group calls, emergency calls) are permitted, and what security credentials apply. By anchoring this profile in the Primary system, the architecture ensures that a user's rights and group affiliations are consistent no matter which system serves them. The Partner MCPTT System acts as a service delivery point, while the Primary system remains the source of truth for identity and authorization.

Cross-system operation involves several coordinated procedures. The Partner system must authenticate the user, which typically involves interaction with the Primary system's identity management function. It must retrieve the user's profile and group configuration, which may involve the group management server of the Primary system. For group calls that span users served by different systems, the MCPTT servers of the involved systems must interconnect so that floor control and media distribution work across the group. Security is handled through key management procedures defined in TS 33.880, ensuring that media and signaling are protected end-to-end across system boundaries.

The Partner MCPTT System concept is fundamental to public safety operations. Agencies frequently conduct joint operations where responders from multiple organizations need to communicate in shared talkgroups. Each agency may operate its own MCPTT system, yet the allied system model allows their users to participate in cross-agency groups with consistent authorization and priority. The definition has remained unchanged from Rel-13 through Rel-20, indicating a stable architectural foundation that has successfully supported the evolution of MCPTT from its initial specification into a mature, widely deployed technology.

Purpose & Motivation

Public safety and critical communications are inherently multi-organizational. Police, fire, emergency medical, and civil defense agencies each have their own command structures, subscriptions, and operational policies, but they must communicate seamlessly during joint incidents. The Partner MCPTT System concept exists to allow one agency's MCPTT system to serve another agency's users without duplicating subscriptions or compromising the authority of the home system over its users' profiles.

Before standardized inter-system MCPTT, cross-agency communication relied on patching disparate radio systems together, shared talkgroups configured manually, or proprietary gateways. These approaches were fragile, difficult to secure, and could not enforce consistent priority and authorization across organizations. They also created administrative duplication: a user needing service in multiple systems would require multiple subscriptions, leading to inconsistency and operational overhead.

The Partner MCPTT System model solves these problems by establishing a trust relationship between allied systems and anchoring user authorization in a single Primary MCPTT System. This gives agencies the benefits of federation — shared talkgroups, cross-agency calls, mutual aid — while retaining local control over their own users. It provides the architectural basis for security (through defined key management), for priority and preemption consistency, and for charging across organizational boundaries. The model's longevity from Rel-13 to Rel-20 reflects its success in meeting the demanding requirements of mission critical communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define Partner MCPTT System. Each summary describes the whole specification, not only this term.

TS 22.179Rel-16 → Rel-17

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.

Rel-13 Initial

Initial definition introduced in TS 23.779: an allied MCPTT system that provides MCPTT services to an MCPTT User based on the MCPTT User Profile defined in that user's Primary MCPTT System. Established the inter-system architecture for cross-agency MCPTT.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Defining Specifications

3GPP specifications that define or reference Partner MCPTT System, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.179 vl00 MCPTT Service Requirements Rel-21 read
TS 23.779 vd00 MCPTT over LTE Stage 2 Study Rel-13 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read