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

Glossary term · Services

MCData group communication

Mission Critical Data Service Group Communication

Services →

MCData group communication is a one-to-many communication using an MCData service that delivers data from one sender to all affiliated members of an MCData group, serving as the primary mechanism for group-addressed data distribution in mission-critical operations.

Introduced
Rel-14
Where
Services › IMS
Specifications
2 specs
MCData group communication Description Purpose What changed Neighbours Specifications

Description

MCData group communication is a one-to-many communication using an MCData service, as defined in 3GPP TS 23.282. It is the mechanism by which a single sender distributes data — short data messages, files, or other structured payloads — to all affiliated members of an MCData group. The communication is mediated by the MCData server, which resolves the group, authorizes the sender, and distributes the data to the group's affiliated membership. The media plane aspects, including the transport of the data payload and the handling of large files, are specified in TS 23.783.

The communication begins when an MCData client sends a request to the MCData server to transmit data to a group. The request identifies the group and carries or references the data payload. The MCData server authenticates the sender, verifies that the sender is a member of the group and is authorized to transmit (for example, that the sender holds the transmission right for the group), and checks the data against the group's policy — including maximum data size and allowed media types. If the request is authorized, the server distributes the data to all affiliated members of the group. For short data, the payload may be carried in the signalling or in a dedicated media plane message; for larger files, the media plane handles the transfer, potentially using the file distribution procedures defined in TS 23.783.

Group communication differs from one-to-one MCData communication in its addressing and delivery semantics. In a one-to-one communication, the recipient is a single user; in a group communication, the recipient set is the group's affiliated membership, which may change dynamically during the life of the communication. The MCData server maintains the distribution state and ensures that all affiliated members receive the data reliably. Delivery may use unicast bearers to each recipient or, where supported, multicast/broadcast delivery via MBMS in EPS or 5G multicast/broadcast services in 5GS, which is particularly valuable when many group members are in the same cell or area.

Transmission arbitration is an important aspect of group communication. For services where only one sender may transmit at a time (such as short data with a transmission right), the MCData server arbitrates requests from multiple group members, granting the right to one and queuing or rejecting others according to policy. This prevents collisions and ensures orderly communication within the group. The server also handles the case where the sender's data must be delivered to members who affiliate after the transmission begins, depending on the group's configuration and the nature of the data.

Group communication integrates with the broader MC services architecture. It uses the same group management, identity management, and security frameworks as MCPTT and MCVideo, and it can be combined with those services — for example, a user might send a short data message to a group while a voice group call is in progress. The communication is also subject to the mission-critical security model, including authentication, authorization, and confidentiality protection of the data in transit.

Purpose & Motivation

MCData group communication exists to provide an efficient, policy-controlled mechanism for distributing data to teams. Mission-critical operations frequently require sending the same information — an incident report, a photograph, a map, a status update — to an entire team. Sending such data individually to each member would be inefficient, error-prone, and impossible to manage at scale, especially when team composition changes dynamically.

The one-to-many model solves this by letting a sender address the group rather than enumerating recipients. The MCData server handles the fan-out, applying authorization and policy once and delivering to all affiliated members. This reduces the sender's workload, ensures consistency of the information across the team, and allows the organization to control who can send to which groups.

The communication also enables efficient use of network resources. By combining the group abstraction with multicast/broadcast delivery where available, a single transmission can reach many users without multiplying the load on the radio access network. This was a key motivation for defining MCData group communication within the MCPTT-derived architecture, which already provided the group management and delivery infrastructure needed for scalable mission-critical group services.

What changed in its specifications

The latest release-to-release comparison of specifications that define MCData group communication. 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

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-14 Initial

MCData group communication was introduced as a one-to-many communication using an MCData service. The functional architecture and information flows were specified in TS 23.282, with media plane procedures for short data and file distribution in TS 23.783.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

The definition text carried over unchanged from Rel-14; the term continued to denote a one-to-many communication using an MCData service.

Defining Specifications

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