Mission Critical User Identity

Description

The Mission Critical User Identity (MC) is a fundamental identifier within the 3GPP-defined Mission Critical Services architecture. It is a globally unique identifier assigned to a user (e.g., a first responder) or a functional alias (e.g., 'Fire Engine 5') that is subscribed to mission-critical services. This identity is used across the entire service layer for authentication, authorization, service discovery, and session management. It is distinct from, but can be associated with, other network identities like IMSI or MSISDN, allowing mission-critical services to operate independently of the underlying access network technology (e.g., LTE, 5G).

The MC identity is a key component in the MC service framework defined in 3GPP TS 23.280 and related specifications. It is used by the Mission Critical Service client on the User Equipment (UE) to register with the MC service platform, which includes core functions like the Mission Critical Push To Talk (MCPTT) server. During registration and subsequent service requests, the MC identity is validated against the user's subscription profile stored in the Home Subscriber Server (HSS) or a dedicated Mission Critical Service database. This ensures that only authorized personnel can access critical communication groups, initiate emergency calls, or use other prioritized features.

Architecturally, the MC identity enables key service features. It supports individual and group communications, allowing users to be addressed directly or as part of a predefined talkgroup. The identity is also crucial for security, as it forms the basis for mutual authentication between the UE and the network using credentials stored on a UICC or in a soft credential system. Furthermore, it facilitates service continuity and mobility; as a user moves between cells or networks, the MC identity allows the MC service layer to maintain the user's active sessions and apply consistent policies, such as pre-emption and priority QoS, regardless of location.

In practice, the MC identity is often structured according to a specific naming convention, such as a Uniform Resource Name (URN) format defined in 3GPP TS 23.003 (e.g., 'urn:uuid:...' or a mission-critical-specific schema). This structured format allows for federation between different service providers or public safety organizations, enabling interoperability in large-scale incidents. The management of these identities, including their creation, assignment, and lifecycle, is typically handled by the mission-critical service operator's management system, which interfaces with the core network elements to provision subscription data.

Purpose & Motivation

The MC identity was created to address the specific needs of public safety and critical industry communications within commercial 3GPP networks. Traditional cellular identifiers like MSISDN (phone numbers) were designed for consumer services and lack the granularity, security, and functional requirements for mission-critical operations. There was a need for a dedicated identity that could support group-based communications, high-priority treatment, secure authentication, and interoperability across organizational and national boundaries.

Prior to its standardization, proprietary systems like TETRA or P25 used their own identity schemes, which hindered interoperability with modern IP-based LTE and 5G networks. The introduction of MC services in 3GPP Release 13 required a foundational identity mechanism that was independent of the underlying access technology, allowing mission-critical applications to be deployed over LTE and, later, 5G NR. This identity solves the problem of uniquely and securely identifying first responders and their functional roles within a standardized, scalable framework.

Furthermore, the MC identity enables the realization of key service requirements such as dynamic group management, emergency alerting, and inherent security. It provides the anchor point for applying mission-critical QoS policies, ensuring that communication sessions for authorized identities receive the necessary network resources and priority, even during network congestion. Its creation was motivated by the global push to replace or complement legacy land mobile radio (LMR) systems with broadband-based solutions, requiring a robust and standardized identity management system at the core of this transition.

Key Features

• Globally unique identifier for users and functional aliases
• Foundation for authentication and authorization in MC services
• Enables individual and group (talkgroup) communication addressing
• Supports service continuity and mobility across network areas
• Independent of underlying access network technology (LTE, 5G)
• Structured format (e.g., URN) for federation and interoperability

Evolution Across Releases

Defining Specifications