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

Glossary term · Services

MCData user

Mission Critical Data User

Services →

MCData user is a mission-critical service user authorized for the MCData services suite via an MCData UE, identifying the subscriber identity that can access mission-critical data applications such as file distribution, messaging, and chat within an MC system.

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

Description

The MCData user is a conceptual entity defined in 3GPP TS 23.282 (Mission Critical Data services) and referenced in TS 23.783 (Mission Critical services architecture). It represents the human or organizational subscriber who has been granted authorization to use the Mission Critical Data (MCData) services suite through an MCData-capable User Equipment. The MCData user is distinct from the MCData UE: the user is the identity and authorization subject, while the UE is the physical device through which the user accesses services. A single MCData user may be associated with one or more MCData UEs, and authorization is managed by the MCData server infrastructure.

Architecturally, the MCData user sits within the broader MC services framework. The MC system comprises an MC service client on the UE, an MC service server (the MCData server) in the network, and supporting functions such as the identity management server, the group management server, and the configuration management server. The MCData user is provisioned with a user profile that defines which MCData services (short data messaging, file distribution, conversational data, etc.) the user may invoke, which groups the user belongs to, and what data size limits apply. Authorization is enforced at the MCData server when the user's client requests service.

The MCData user identity is typically derived from the 3GPP identity framework, using an MC service ID that maps to credentials held in the identity management server. When an MCData UE registers, the MCData server authenticates the user and retrieves the user's service configuration. This configuration determines the functional capabilities available to the user, such as whether the user can initiate standalone or conversational data exchanges, and whether the user is permitted to send data to groups or only to individuals.

In operation, the MCData user is the subject of all MCData transactions. When the user sends a short data message or distributes a file, the MCData server authorizes the request against the user's profile, applies any applicable policies, and routes the data to the target recipients. The server also maintains state about the user's affiliation with groups, which determines whether the user receives group-addressed data. Because MCData is designed for mission-critical environments (public safety, utilities, transport), the authorization model is strict: only explicitly authorized MCData users can access the suite, and the authorization can be revoked or modified dynamically by the administrator.

The term is deliberately defined in terms of authorization rather than mere capability, emphasizing that mission-critical data access is a controlled privilege. This aligns MCData with the other MC services (MCPTT, MCVideo) which use the same user/UE distinction, enabling a consistent identity and authorization architecture across the MC services suite.

Purpose & Motivation

The MCData user concept exists to separate the authorization subject from the device in mission-critical data services. In public safety and critical communications, access to data services must be tightly controlled: not every device or subscriber may distribute files or send messages within an incident response organization. By defining an MCData user as an authorized MC service user, 3GPP provides a clear anchor for authentication, authorization, and policy enforcement.

Historically, mission-critical communications were voice-centric (MCPTT), and data capabilities were bolted on through proprietary or non-standard solutions. The introduction of MCData in Release 14 created a standardized data suite, and with it the need for a standardized notion of who is entitled to use it. The MCData user fills that gap, enabling administrators to provision users, assign them to groups, and control their data privileges independently of the devices they carry.

The concept also supports operational realities such as shared devices, device replacement, and multi-device usage, where the user identity must persist across UEs. This makes the MCData user a foundational building block for interoperable, multi-vendor mission-critical broadband systems.

What changed in its specifications

The latest release-to-release comparison of specifications that define MCData user. 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 (6 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 2 changes
  • MCData user profile migration information TS 23.282CR0130
  • Correct misalignment on MCData user usage TS 23.282CR0123
Rel-17 2 changes
  • Point-to-Point IP connectivitity using functional alias to address the target MCData user TS 23.282CR0162
  • Distribution of file residing in MCData message store account of the MCData user TS 23.282CR0253
Rel-18 1 change
  • MCData user profile configuration parameters for location information TS 23.282CR0303
Rel-19 1 change
  • Target MCData user configuration for recording TS 23.282CR0367

Defining Specifications

3GPP specifications that define or reference MCData user, 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