Description
The MC user is the foundational identity concept in the 3GPP Mission Critical (MC) services framework defined in TS 23.280. It represents a human being (or an entity acting on behalf of a human) who has been provisioned and authorized to consume one or more mission critical services, such as MCPTT (Mission Critical Push-To-Talk), MCVideo, or MCData. Every MC user is uniquely identified by an MC ID, which is a globally unique identifier used across the MC service ecosystem to bind the user to their service profile, authorization state, and configuration data.
The MC user concept sits at the top of the MC service identity hierarchy. An MC user may be associated with one or more MC service clients (e.g., an MCPTT client, an MCVideo client, an MCData client) running on one or more user equipment devices. The MC user is distinct from the MC service client: the user is the identity and authorization subject, while the client is the software instance that performs the client application functions. This separation allows a single user to operate multiple clients and devices while maintaining a consistent identity and service profile across the MC system.
Authorization of an MC user is performed by the MC service infrastructure, typically through the configuration management server and the identity management server. The user's profile defines which MC services they are entitled to, which groups they belong to, their role and priority levels, and their security credentials. Before any MC service can be obtained, the MC user must be authenticated and authorized; only after successful authorization does the user obtain access to the mission critical services for which they are provisioned. This authorization step is critical in mission critical environments where access control directly affects operational safety.
The MC user is also the subject of key management operations, including group membership management, affiliation, and functional alias assignment. In group communication scenarios, the MC user's membership in MC groups determines which group calls and group data sessions they can participate in. The MC user's priority and pre-emption attributes, derived from their profile, influence how the network treats their traffic during congestion or emergency conditions.
In the broader 3GPP architecture, the MC user interacts with the MC service system through the UE and the MC service client. The MC service system (comprising servers such as the MCPTT server, MCData server, group management server, and configuration management server) uses the MC ID to look up the user's profile and enforce authorization decisions. The MC user concept therefore provides the consistent, secure identity layer that ties together authentication, authorization, service delivery, and group management across all mission critical services.
Purpose & Motivation
The MC user concept exists to provide a single, authoritative identity and authorization anchor for mission critical services. In public safety and critical communications, it is essential to know exactly who is using the service, what they are entitled to, and under what conditions. Without a well-defined user identity separate from devices and clients, it would be impossible to enforce access control, manage group membership, or apply priority treatment consistently across MCPTT, MCVideo, and MCData.
Historically, mission critical communications were delivered over dedicated narrowband systems such as TETRA and P25, where subscriber identity was tightly bound to the radio terminal and managed by the network operator. The move to LTE and 5G broadband MC services required a new identity model that could operate over IP, support multiple clients per user, and integrate with standard 3GPP authentication. The MC user, identified by the MC ID and authorized through the MC service infrastructure, was created to fill this gap.
The concept also solves the problem of cross-service consistency. A single first responder may need push-to-talk, video, and data services simultaneously; the MC user ensures that one identity and one authorization profile govern all of them, simplifying provisioning and reducing the risk of inconsistent access rights. This design directly supports the reliability and security requirements of mission critical operations.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC user. Each summary describes the whole specification, not only this term.
Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →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 MC user, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |