Description
The MC service ID is a generic, service-agnostic identifier defined in 3GPP TS 23.280 (Common functional architecture to support mission critical services) and referenced in TS 23.783 (Mission Critical (MC) services over 5G). It represents the user identity of a mission critical user within a specific MC service and is deliberately abstract so that the common MC architecture can be specified once and then specialized per service. In practice, wherever the common architecture documents refer to an 'MC service ID', the concrete realization is the MCPTT ID for Mission Critical Push-To-Talk, the MCVideo ID for Mission Critical Video, or the MCData ID for Mission Critical Data.
The identifier is a SIP URI, typically of the form 'sip:user@domain', which allows it to be used directly in SIP signalling between the MC service UE and the MC service server. Because it is a URI, it can be routed, resolved through DNS/IMS procedures, and authenticated using the same identity framework that underpins the MC service. The MC service ID is bound to the user's credentials and to the user profile stored in the MC service user database, and it is the key by which authorization, group membership, and affiliation are evaluated.
Architecturally, the MC service ID sits at the centre of the identity and authorization model. When a UE registers with an MC service, it authenticates and asserts its MC service ID; the MC service server then checks the associated user profile to determine which groups the user belongs to, which services they may invoke, and what priority they hold. Group identities (MC service group IDs) and functional aliases are separate identifiers, but all authorization decisions ultimately resolve back to the individual MC service ID.
The generic naming convention matters because it keeps the common functional architecture (TS 23.280) reusable across MCPTT, MCVideo, and MCData. A single set of procedures for registration, group management, and configuration management can be written against 'MC service ID', and the service-specific specifications (TS 23.379 for MCPTT, TS 23.281 for MCVideo, TS 23.282 for MCData) simply substitute the concrete identifier. This reduces duplication and ensures consistent security and identity handling across all mission critical services.
In the 5G context (TS 23.783), the MC service ID continues to serve the same role, but the underlying connectivity may be provided by 5G System capabilities such as network slicing and QoS flows rather than by legacy LTE/EPC bearers. The identity layer remains independent of the transport layer, which is a key design principle: the MC service ID identifies the user regardless of whether they are attached via LTE, 5G, or non-3GPP access.
Purpose & Motivation
The MC service ID exists to give mission critical services a single, consistent way to identify users across multiple service types. Before the common MC architecture was introduced in Release 14, MCPTT, MCVideo, and MCData were specified with their own identity notions, which risked divergence in authentication, authorization, and group management. By defining a generic 'MC service ID' in TS 23.280 and allowing it to be replaced by MCPTT ID, MCVideo ID, or MCData ID, 3GPP ensured that the common functional architecture could be reused and that a user's identity semantics remain uniform across services.
The identifier also solves an interoperability problem. Mission critical users often need to communicate across agencies and vendors; a standardized, URI-based identity that can be authenticated and routed through IMS-style procedures makes cross-domain communication feasible. It allows the network to apply authorization, priority, and QoS treatment based on a well-defined identity rather than on opaque, implementation-specific tokens.
Finally, the generic identity supports evolution. Because the common architecture refers to the abstract MC service ID, new MC services can be added in later releases without redefining the identity framework. The definition has remained essentially stable from Release 14 through Release 20, with only editorial refinement in Release 19, which is a sign that the underlying identity model has proven durable.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC service ID. 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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MC service ID, 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 |