Description
The MCData group is the foundational grouping construct within the Mission Critical Data (MCData) service defined by 3GPP. MCData itself is one of the Mission Critical services built on the Mission Critical Push To Talk (MCPTT) architectural framework, standardized from Release 14 onwards in TS 23.282 (functional architecture and information flows) and TS 23.783 (MCData media plane). An MCData group is an MC service group that has been configured specifically for MCData service, meaning that its membership, policies, and communication characteristics are provisioned to support data-oriented communications rather than (or in addition to) voice.
Architecturally, the MCData group is managed by the MCData server, which is a functional entity within the MC service layer. The group is defined in the group management documents held by the group management server (GMS) and referenced by the MCData server when authorizing and routing group communications. Each group has an identifier (MCData group ID), a set of members with associated roles and permissions, and a configuration that determines which MCData services (short data, file distribution, etc.) the group may use. The group configuration also defines the maximum data size, the allowed media types, and the security policies applicable to communications within the group.
The group is central to how MCData communications are addressed and delivered. When a user initiates an MCData group communication, the MCData client sends the request to the MCData server, which resolves the group identity, checks the initiating user's affiliation and authorization, and then distributes the data to all affiliated members of the group. Group membership and affiliation are distinct concepts: membership is a provisioning attribute (who belongs to the group), while affiliation is a dynamic state (who is currently registered and interested in receiving group communications). Only affiliated members receive group communications, which conserves radio and network resources.
MCData groups support both pre-arranged and chat-style group communications. In a pre-arranged group, the group and its membership are provisioned in advance by the administrator, and communications can be initiated immediately by any authorized member. Chat groups allow dynamic creation and membership management, with the group existing for the duration of the communication session. The MCData server enforces the group's policies, including talker/transmitter arbitration for short data and file distribution, ensuring that only authorized users transmit and that data is delivered reliably to all recipients.
The group also interacts with the underlying 3GPP network through the MC service layer's interfaces to the EPS/5GS. Group communications may use unicast bearers per recipient or, where supported, multicast delivery via MBMS (in EPS) or 5G multicast/broadcast services (in 5GS) to efficiently distribute data to many group members in the same area. This makes the MCData group not only a service-layer concept but also a driver of efficient radio resource usage for group data delivery.
Purpose & Motivation
The MCData group exists to provide a managed, policy-controlled way to distribute data among a defined set of mission-critical users. Public safety and mission-critical organizations (police, fire, ambulance, utilities) need to send short messages, files, and structured data to teams rather than to individuals. Without a group construct, each transmission would require enumerating recipients, applying per-recipient authorization, and managing delivery state individually — an approach that does not scale and cannot enforce organizational policy.
The group abstraction solves this by decoupling the logical recipient set from the individual users. Administrators provision groups that mirror operational structures (e.g., a fire brigade, a tactical team), and the MCData server enforces membership, affiliation, and transmission rights. This mirrors the group concept already proven in MCPTT voice services, providing consistency across mission-critical services and allowing organizations to manage voice and data communications with the same operational model.
The group also enables efficient use of network resources. Because only affiliated members receive group communications, and because the architecture supports multicast/broadcast delivery, the MCData group allows a single transmission to reach many users without multiplying the load on the radio access network. This was a key motivation for building MCData on the MCPTT architectural framework rather than defining an ad hoc messaging service.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCData group. 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 (3 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MCData group, 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 |