Description
The Primary MCPTT System is a foundational concept in 3GPP's Mission Critical Push To Talk (MCPTT) architecture, defined primarily in TS 22.179 and TS 23.779. It represents the MCPTT system that holds and manages the MCPTT User Profile for a given MCPTT User. In simple terms, it is the user's 'home' MCPTT system. Every MCPTT user is associated with exactly one Primary MCPTT System, which acts as the authoritative source for that user's service configuration, identity, and authorization data. This system is responsible for provisioning the user's MCPTT ID, group memberships, role assignments, and other service parameters that determine what the user is allowed to do within the MCPTT service.
The architecture of MCPTT is built around a set of functional entities that can be distributed across multiple systems. The Primary MCPTT System typically contains the MCPTT User Database, which stores the MCPTT User Profile. When a user registers with the MCPTT service, the Primary MCPTT System authenticates the user and provides the necessary profile information to the serving MCPTT system. This separation of home and serving environments is analogous to the home network concept in cellular networks, enabling users to roam across different MCPTT systems while maintaining a consistent service experience. The Primary MCPTT System may also host the MCPTT Key Management Server (KMS) for security functions, although this can be deployed separately.
Operationally, the Primary MCPTT System interacts with other MCPTT systems through standardized reference points. For example, the MCPTT-1 reference point connects the MCPTT client to the MCPTT server, while MCPTT-3 connects MCPTT servers for inter-system communication. When a user is registered on a different MCPTT system (the serving system), that system retrieves the user's profile from the Primary MCPTT System to enforce policies and provide services. This allows for a flexible deployment where organizations can have their own MCPTT systems while users can access services from various locations or networks.
The Primary MCPTT System also plays a critical role in group communication. Group configurations, including group identities and membership lists, are typically managed in the Primary MCPTT System of the group's administrator or the group's home system. This ensures that group calls can be set up consistently regardless of where individual users are currently registered. The system supports both on-network and off-network operation, and the Primary MCPTT System concept applies primarily to on-network scenarios where connectivity to the home system is available.
In summary, the Primary MCPTT System is the authoritative MCPTT system for a user, providing the user profile and enabling service continuity across different serving systems. It is essential for managing user identities, authorizations, and group configurations in a scalable and secure manner, forming the backbone of mission-critical push-to-talk services over LTE and 5G networks.
Purpose & Motivation
The Primary MCPTT System concept was created to solve the problem of managing user identities and service profiles in a multi-system, multi-operator MCPTT environment. In traditional push-to-talk systems, user data was often tied to a specific network or device, making roaming and interoperability difficult. 3GPP introduced the Primary MCPTT System to provide a clear home for each user's profile, enabling consistent service delivery regardless of the user's current location or serving network. This mirrors the home network model in cellular communications, where the Home Subscriber Server (HSS) stores subscription data and the serving network retrieves it as needed.
By centralizing the MCPTT User Profile in the Primary MCPTT System, 3GPP ensures that security policies, group memberships, and service authorizations are managed from a single authoritative source. This simplifies administration for organizations and enables features like user roaming between MCPTT systems, which is crucial for public safety and mission-critical users who may operate across jurisdictional boundaries. It also facilitates interoperability between different MCPTT vendors and operators, as the standardized interfaces allow the serving system to query the primary system for user data.
Furthermore, the Primary MCPTT System supports the separation of concerns between home and serving environments, allowing operators to deploy MCPTT services flexibly. For example, a public safety agency can host its own Primary MCPTT System while its users roam onto a commercial operator's MCPTT system during large-scale incidents. This architecture was motivated by the need for resilience, scalability, and interoperability in mission-critical communications, addressing the limitations of proprietary PTT solutions that lacked standardized roaming and profile management.
What changed in its specifications
The latest release-to-release comparison of specifications that define Primary 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: 'MCPTT system where the MCPTT User Profile of an MCPTT User is defined.' This established the concept of a home MCPTT system for user profile management, forming the basis for roaming and inter-system interoperability in mission-critical push-to-talk services.
Defining Specifications
3GPP specifications that define or reference Primary 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 |
| TS 33.880 vf10 | Security Study for Enhanced Mission Critical Services | Rel-15 read |