Description
The MCData client is the on-device software component that implements the client side of the Mission Critical Data (MCData) service as specified in TS 23.282. It is defined as an instance of an MC service client that provides the client application function for the MCData service. In the 3GPP MC architecture, the MC service client is the generic concept covering all mission critical client applications; the MCData client is the specialization of that concept for data-centric communications.
The MCData client runs on the user equipment (UE) and communicates with the MCData server in the MC service infrastructure over the network. It provides the user-facing and protocol-facing functions needed to originate, receive, and manage MCData communications. These include short data messages, file distribution (both one-to-one and one-to-many), and data streaming, as well as the associated procedures for session establishment, participant management, and delivery handling. The client also handles the MCData-specific aspects of group data communication, emergency data communication, and private (one-to-one) data communication.
Architecturally, the MCData client interacts with several functional entities. It communicates with the MCData server for the core data service functions, with the group management server for group membership information, with the configuration management server for its service configuration and user profile, and with the identity management server for authentication and authorization. The client also relies on the underlying 3GPP network (EPS or 5GS) for connectivity, QoS, and security. The MCData client is typically co-located with other MC service clients (e.g., MCPTT and MCVideo clients) on the same UE, sharing the MC user identity and common service enablers.
The client is responsible for enforcing the user's authorization and configuration. It receives its configuration from the configuration management server, including which MCData functions are enabled, group definitions, and communication policies. It uses this configuration to determine whether a requested action (such as initiating a group data session or sending a file) is permitted. The MCData client also participates in the security procedures of the MC service system, including authentication and the protection of MCData traffic.
In operation, the MCData client initiates and terminates MCData sessions, manages the transmission and reception of messages and files, and reports status and delivery information. It supports functional aliases and handles the mapping between the MC user identity and the communication endpoints. Through its interaction with the MCData server, the client enables reliable, prioritized data delivery that meets the stringent requirements of mission critical operations, including low latency, high availability, and support for emergency communications.
Purpose & Motivation
The MCData client exists to bring mission critical data services to end users on broadband devices. Traditional mission critical communications focused on voice (push-to-talk), but modern public safety and critical infrastructure operations increasingly depend on data: sharing situational awareness information, distributing files such as maps and images, sending short messages, and streaming telemetry. The MCData client provides the standardized client-side functionality that makes these services interoperable across vendors and networks.
Before MCData, mission critical data exchange was often implemented with proprietary or non-standard applications that could not interoperate, could not be prioritized consistently by the network, and lacked the security and authorization guarantees required for critical operations. The 3GPP MCData service, and the MCData client that implements it, addressed these limitations by defining standardized protocols, data formats, and procedures on top of the 3GPP network.
The client concept also enables a clean separation between the user's identity and authorization (the MC user) and the application software that delivers the service. This separation allows a single user to run multiple MC service clients, supports device replacement and multi-device scenarios, and lets the network enforce consistent policies across all mission critical services. The MCData client is therefore a key building block for integrating data communications into the mission critical communications ecosystem.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCData client. Each summary describes the whole specification, not only this term.
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 RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MCData client, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |