Description
The MC service user profile is the data structure that binds an MC service user to the services, roles, and devices the user is permitted to use. Defined in TS 23.280 and reused in TS 23.783 for MC services over 5G, the profile is the authoritative source for service-layer authorization in the MC system. It is stored and managed by the MC service user database and delivered to the UE during configuration, typically via the identity management and configuration management functions of the MC common architecture.
The profile contains several categories of information. Identity-related data includes the MC service user identity (e.g., MC service ID) and any functional aliases. Service authorization data indicates which MC services (MCPTT, MCVideo, MCData) the user may employ. Role information specifies the roles the user may assume within each service — for example, whether the user may initiate group calls, act as a dispatcher, or participate in particular group types. Device binding information indicates from which MC service UEs the user may use the services, which is essential in shared-device environments. Additional profile elements may cover group membership references, security credentials and keys, and service-specific configuration such as priority levels.
Operationally, the profile is used at several points. During service authentication and authorization, the MC system checks the user's credentials and retrieves the profile to decide whether access is granted. During UE configuration, the profile is used to populate the UE with the user's settings, including group lists, service parameters, and security material. When a user changes device or role, the profile determines what the new configuration should be. The profile also supports on-demand configuration updates, allowing the MC system to push changes to the UE when the user's authorization changes.
The profile is tightly coupled to the MC service user concept: the user is the identity, and the profile is the set of attributes that make the identity actionable. Because the profile is centrally managed, operators can enforce consistent policy across services and devices, and can revoke or modify access without touching the device. This is particularly important for mission critical organizations, where roles and authorizations may change rapidly during incidents.
The definition of MC service user profile has remained unchanged from Rel-14 through Rel-20, indicating a stable and well-scoped data model. Its importance lies in enabling role-based, device-aware authorization and consistent configuration across the MC service ecosystem.
Purpose & Motivation
The MC service user profile exists to make the MC service user identity actionable. An identity alone does not specify what a user may do, in which role, or from which device; the profile provides those attributes in a standardized, centrally managed form. This was necessary because mission critical organizations need fine-grained control over authorization — for example, allowing a responder to use MCPTT from a shared vehicle-mounted UE but not from a personal device, or granting dispatcher privileges only during certain assignments.
Before the MC common architecture, such authorization data was typically embedded in proprietary systems, making multi-vendor interoperability and cross-organizational operations difficult. By standardizing the profile in TS 23.280, 3GPP enabled a common data model that can be provisioned, exchanged, and enforced across vendors and networks. The profile also supports the separation of user and device, which is essential for shared-device and shift-based operations.
The profile was introduced in Rel-14 together with the MC service user concept and has been reused unchanged since, reflecting the maturity of the data model and its adequacy for subsequent MC service enhancements.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC service user profile. 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 service user profile, 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 |