Description
The Mission Critical Push to Talk Identity (MCPTT ID) is a core element within the 3GPP Mission Critical Services (MCS) architecture, specifically defined for the MCPTT service. It serves as a unique, persistent identifier assigned to an MCPTT user (e.g., a first responder) or an MCPTT group. This identity is used throughout the service layer for authentication, authorization, service provisioning, and routing of push-to-talk communications. The MCPTT ID is distinct from, but can be associated with, other 3GPP identifiers like IMSI or MSISDN, and it is managed within the MCPTT service's home network.
Architecturally, the MCPTT ID is utilized by several functional entities defined in 3GPP specifications. The MCPTT client, residing on the user equipment (UE), is configured with this identity. During registration, the MCPTT client presents the MCPTT ID to the MCPTT service platform, which includes components like the MCPTT Server, MCPTT Application Server, and key management entities. The identity is validated against subscription data stored in the Home Subscriber Server (HSS) or a dedicated MCPTT database. For group communications, MCPTT Group IDs are used to define talkgroups, and the MCPTT ID determines a user's membership and privileges within those groups (e.g., dispatcher, floor control rights).
How it works involves the identity being embedded in signaling messages (using protocols like SIP and HTTP) for all MCPTT procedures: registration, group affiliation, call initiation (floor request), and emergency calls. Security is paramount; the MCPTT ID is a key input for authentication and key agreement procedures, ensuring that only authorized users can access the service. It also enables features like identity-based priority and pre-emption, where a high-priority user's MCPTT ID can grant them immediate access to network resources during congestion. The identity remains consistent across sessions and is crucial for lawful interception and logging for public safety accountability.
Purpose & Motivation
MCPTT Identity was created to fulfill the stringent requirements of professional and public safety communications migrating from legacy Land Mobile Radio (LMR) systems like TETRA or P25 to 3GPP-based broadband networks (LTE, 5G). Legacy systems had their own proprietary identity and security models. A standardized, secure identity framework was necessary to enable interoperability between different vendors' MCPTT solutions and to allow public safety users to roam onto visited networks while maintaining their service profile and authorization.
The limitations of using generic cellular identifiers (like phone numbers) for mission-critical services were significant. These identifiers lacked the granularity for group management, did not inherently support service-specific authentication, and could not easily encode user roles or priorities. The MCPTT ID solves these problems by providing a service-layer identity specifically tailored for push-to-talk. It enables secure, authenticated access to the MCPTT service, supports dynamic group management, and forms the basis for advanced features like emergency alerting, inherent user priority, and secure end-to-end group communications. Its creation was motivated by the need for a reliable, standardized, and secure identity mechanism that is integral to making LTE/5G a viable replacement for traditional PMR networks.
Key Features
- Unique identifier for MCPTT users and groups within the 3GPP service framework
- Foundation for authentication and authorization in Mission Critical Push to Talk services
- Enables dynamic group affiliation and management for talkgroups
- Supports user priority and pre-emption mechanisms based on identity
- Essential for secure signaling and media encryption key derivation
- Facilitates roaming and interoperability between different MCPTT service providers
Evolution Across Releases
MCPTT Identity was initially defined as part of the first 3GPP specification set for Mission Critical Push to Talk services. The architecture established the MCPTT ID as a core service-layer identifier, detailing its structure, usage in registration, group call procedures, and its relationship with underlying 3GPP subscription identifiers for public safety over LTE.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.179 | 3GPP TS 22.179 |
| TS 22.280 | 3GPP TS 22.280 |
| TS 22.281 | 3GPP TS 22.281 |
| TS 22.879 | 3GPP TS 22.879 |
| TS 22.880 | 3GPP TS 22.880 |
| TS 23.179 | 3GPP TS 23.179 |
| TS 23.280 | 3GPP TS 23.280 |
| TS 23.283 | 3GPP TS 23.283 |
| TS 23.379 | 3GPP TS 23.379 |
| TS 23.479 | 3GPP TS 23.479 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.741 | 3GPP TS 23.741 |
| TS 23.780 | 3GPP TS 23.780 |
| TS 23.781 | 3GPP TS 23.781 |
| TS 23.782 | 3GPP TS 23.782 |
| TS 23.783 | 3GPP TS 23.783 |
| TS 23.790 | 3GPP TS 23.790 |
| TS 23.792 | 3GPP TS 23.792 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.379 | 3GPP TS 24.379 |
| TS 24.380 | 3GPP TS 24.380 |
| TS 24.481 | 3GPP TS 24.481 |
| TS 24.482 | 3GPP TS 24.482 |
| TS 24.483 | 3GPP TS 24.483 |
| TS 24.484 | 3GPP TS 24.484 |
| TS 24.883 | 3GPP TS 24.883 |
| TS 24.980 | 3GPP TS 24.980 |
| TS 26.179 | 3GPP TS 26.179 |
| TS 26.281 | 3GPP TS 26.281 |
| TS 26.346 | 3GPP TS 26.346 |
| TS 26.802 | 3GPP TS 26.802 |
| TS 26.880 | 3GPP TS 26.880 |
| TS 26.881 | 3GPP TS 26.881 |
| TS 26.928 | 3GPP TS 26.928 |
| TS 26.989 | 3GPP TS 26.989 |
| TS 29.165 | 3GPP TS 29.165 |
| TS 29.379 | 3GPP TS 29.379 |
| TS 29.380 | 3GPP TS 29.380 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 31.102 | 3GPP TR 31.102 |
| TS 31.103 | 3GPP TR 31.103 |
| TS 33.107 | 3GPP TR 33.107 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.126 | 3GPP TR 33.126 |
| TS 33.127 | 3GPP TR 33.127 |
| TS 33.128 | 3GPP TR 33.128 |
| TS 33.179 | 3GPP TR 33.179 |
| TS 33.180 | 3GPP TR 33.180 |
| TS 33.879 | 3GPP TR 33.879 |
| TS 33.880 | 3GPP TR 33.880 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.579 | 3GPP TR 36.579 |
| TS 37.579 | 3GPP TR 37.579 |
| TS 38.913 | 3GPP TR 38.913 |