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

Glossary term · Identifier

MCData ID

Mission Critical Data Identity

Identifier →

MCData ID is a unique identifier for an MCData user or service instance within the MCData service, used for authentication, authorization, and routing of mission-critical data communications.

Introduced
Rel-14
Where
Services › IMS
Specifications
2 specs
MCData ID Description Purpose What changed Neighbours Detected Changes Specifications

Description

The MCData ID is a fundamental identifier in the Mission Critical Data (MCData) service, defined in 3GPP TS 23.282. It represents an instance of an MC service ID specifically within the MCData service context. An MC service ID is a generic identity used across all mission-critical services (MCPTT, MCVideo, MCData) to identify users, functional aliases, or service accounts. The MCData ID is the concrete instantiation of that identity for data communications, ensuring that data sessions, group memberships, and message routing are correctly associated with the right user or entity.

In the MCData architecture, the MCData ID is used by the MCData client, server, and other functional entities to authenticate and authorize access to MCData services. It is typically a SIP URI or a Tel URI, following the MCX identity framework. The ID is provisioned in the user's MCData client and stored in the MCData server's user database. When a user initiates a data session or sends a group message, the MCData ID is included in signaling to identify the originator and to apply policies (e.g., whether the user is allowed to send to a particular group).

The MCData ID also plays a role in group management: group members are identified by their MCData IDs, and affiliation/de-affiliation operations reference these IDs. The ID must be unique within the MCData service domain and may be mapped to other identifiers (e.g., IMPI, MSISDN) for interworking with the underlying 3GPP network.

Security is tightly coupled with the MCData ID: authentication of the user during MCData service authorization binds the ID to credentials, preventing impersonation. The ID is also used in charging and accounting records, enabling operators to track usage per user.

Because the MCData ID is an instance of the MC service ID, it inherits properties such as support for functional aliases (e.g., a dispatcher ID that represents a role rather than a person). This flexibility is essential in mission-critical environments where roles may be shared or reassigned. The definition of MCData ID has remained stable since Rel-14, reflecting its foundational nature.

Purpose & Motivation

The MCData ID exists to provide a unambiguous, standardized way to identify entities within the MCData service. In mission-critical communications, knowing exactly who sent a message or who is a member of a group is vital for accountability, security, and correct routing. Without a standardized ID, interoperability between vendors and networks would be impossible, and policy enforcement (e.g., who can send data to whom) would be error-prone.

The MCData ID solves the problem of identity fragmentation by building on the generic MC service ID framework. It allows a single user identity to be used across MCPTT, MCVideo, and MCData, simplifying provisioning and user experience. It also enables the use of functional aliases, which is important when a user acts in a role (e.g., incident commander) rather than as an individual.

Historically, proprietary mission-critical data systems used various identifiers (e.g., IP addresses, usernames), leading to integration challenges. 3GPP standardized the MCData ID to ensure consistent identity semantics, security binding, and routing across all MCData implementations.

What changed in its specifications

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

TS 23.282Rel-18 → Rel-19

Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.

Full comparison in TS 23.282 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-18 1 change
  • Correct MCData ID usage in information flow table TS 23.282CR0313

Defining Specifications

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

SpecificationTitleRelease
TS 23.282 vk31 Mission Critical Data Architecture Rel-20 read
TR 23.783 vi00 Technical Report on Mission Critical Services over 5GS Rel-18 read