Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MC service user

Mission Critical Service User

Services →

MC service user is an authorized user who can use an MC service UE to participate in one or more mission critical services and serves as the identity anchor for authorization, roles, and service access in MC systems.

Introduced
Rel-14
Where
Services › IMS
Specifications
2 specs
MC service user Description Purpose What changed Neighbours Detected Changes Specifications

Description

The MC service user is the fundamental identity concept in the 3GPP Mission Critical (MC) services framework defined in TS 23.280 (Common functional architecture) and TS 23.783 (MC services over 5G). It represents an authorized human or organizational identity that is permitted to consume one or more mission critical services — such as MCPTT (Mission Critical Push-To-Talk), MCVideo, or MCData — through an MC service UE. The user is distinct from the UE: a single MC service user may be associated with multiple UEs, and a single UE may be used by different users, with the binding between user identity and device controlled through configuration and authorization.

Architecturally, the MC service user is managed by the MC service user database and the identity management function within the MC system. When a UE attaches and attempts to use an MC service, the MC service performs authorization and authentication procedures that verify the user's identity and check the user's profile. The profile determines which services the user may employ, in which roles (e.g., authorized to initiate group calls, dispatcher role, first responder role), and from which UEs. The user identity is typically expressed as an MC service ID, which is used in signaling, group membership, and policy decisions.

The MC service user concept underpins several key mechanisms. First, group management: users are members of MC service groups, and their membership and role determine call participation rights. Second, functional alias and role management: users can be assigned functional aliases (e.g., 'Incident Commander') that map to their user identity for dispatching and communication. Third, location and presence: user-level presence and location reporting are tied to the user identity, not merely the device. Fourth, security: user authentication and authorization are enforced at the service layer, complementing the underlying 3GPP network security.

In operation, the lifecycle of an MC service user includes provisioning (creating the user and profile in the MC system), authentication and authorization at service access, on-demand configuration of the UE with the user's profile, and de-provisioning. The MC service user may be authorized for multiple MC services simultaneously, and the MC system enforces per-service and per-role permissions. The user identity is also used for charging and for audit and logging of mission critical communications.

The definition of MC service user has remained stable from Rel-14 through Rel-20, reflecting the maturity of the concept. Its importance lies in separating the human/organizational identity from the device, enabling flexible device sharing, role-based authorization, and consistent policy enforcement across MCPTT, MCVideo, and MCData services.

Purpose & Motivation

Mission critical communications require strict control over who may participate, in what role, and from which device. Before the MC services architecture, push-to-talk and related systems were largely proprietary, with user identity and authorization handled in vendor-specific ways. The MC service user concept was created to provide a standardized, service-layer identity that is independent of the underlying 3GPP subscription and of the physical device, enabling interoperability across vendors and networks.

By separating user identity from UE identity, the concept solves practical operational problems: responders may share devices across shifts, may use multiple devices, and may need temporary role assignments during incidents. It also enables centralized provisioning and policy enforcement, so that a single authoritative profile governs access to MCPTT, MCVideo, and MCData consistently.

The concept was introduced in Rel-14 as part of the first release of the MC services common architecture (TS 23.280), motivated by the need for a common framework across the different MC service enablers rather than service-specific identity models. It has since been reused unchanged, demonstrating that the abstraction was correctly scoped from the outset.

What changed in its specifications

The latest release-to-release comparison of specifications that define MC service user. Each summary describes the whole specification, not only this term.

TS 23.280Rel-18 → Rel-19

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

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-18 4 changes
  • Private call towards a migrated MC service user TS 23.280CR0353
  • Updating the MC service user ID list within preconfigured user regroup TS 23.280CR0364
  • Addition of functional alias that corresponds to the location information requesting MC service user TS 23.280CR0339
  • Resolving the target KMS URI for a migrated MC service user TS 23.280CR0361
Rel-19 3 changes
  • ACM updating MC service user profiles assigned from partner MC system TS 23.280CR0509
  • Ad hoc group call procedure towards a migrated MC service user TS 23.280CR0579
  • Requesting specific location information of MC service user on-demand or periodic TS 23.280CR0609
Rel-20 1 change
  • Provide User Info ID during MC service user authentication procedure TS 23.280CR0708

Defining Specifications

3GPP specifications that define or reference MC service user, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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