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

Glossary term · Services

MCData group affiliation

Mission Critical Data Service Group Affiliation

Services →

MCData group affiliation is an MC service group affiliation representing a user's dynamic registration of interest in a specific MCData group, which determines which group members receive group communications and is distinct from static group membership.

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

Description

MCData group affiliation is the dynamic state that links an MCData user to an MCData group for the purpose of receiving group communications. It is defined in 3GPP TS 23.282 as an MC service group affiliation for MCData. While group membership is a provisioning attribute — a user is configured as a member of a group by the administrator — affiliation is a runtime state that the user (or the user's client, on the user's behalf) activates when the user wants to participate in the group's communications. Only affiliated members are considered recipients of MCData group communications.

The affiliation procedure is carried out between the MCData client and the MCData server. The client sends an affiliation request identifying the group (by MCData group ID) and the desired affiliation state (affiliated or de-affiliated). The MCData server authenticates the user, verifies that the user is a member of the group and is authorized to affiliate, and then updates the group's affiliation state. The server may also consult policy configured for the group, such as limits on the number of affiliated users or restrictions based on the user's location or role. Once affiliated, the user becomes a candidate recipient for group communications addressed to that group.

Affiliation is fundamental to how group communications are delivered. When a group communication is initiated, the MCData server resolves the group's affiliated membership and distributes the data only to those members. This conserves radio resources and server processing capacity, and it ensures that users who are off duty or otherwise not interested in the group do not receive unwanted traffic. Affiliation state is maintained by the MCData server and can be queried by authorized entities, for example to display group presence information to users or to support dispatcher functions.

Affiliation interacts with the user's registration state and with the underlying network. A user must typically be registered with the MC service before affiliating to groups, and affiliation may be automatically restored after re-registration depending on the client's configuration and the group's policies. The MCData server tracks affiliation per user and per group, and the affiliation state is part of the group's overall state that the server manages. Affiliation changes can be triggered by the user explicitly, by policy (e.g., automatic affiliation to a default group on login), or by the administrator through the group management interface.

In the broader MC services architecture, group affiliation is a common concept shared across MCPTT, MCVideo, and MCData. This consistency allows a single user to manage affiliations across multiple mission-critical services with a uniform operational model. For MCData specifically, affiliation determines eligibility for short data messages, file distribution, and other group-addressed data services, and it is a prerequisite for the MCData server to include the user in the distribution tree of a group communication.

Purpose & Motivation

MCData group affiliation exists to separate the static organizational structure of groups from the dynamic, real-time participation of users. In mission-critical operations, group membership is relatively stable — a firefighter belongs to a brigade — but participation varies continuously as personnel come on duty, go off duty, move between incidents, or change roles. Affiliation provides the mechanism to reflect this dynamic participation without requiring administrators to constantly modify group membership.

The concept also solves a resource-efficiency problem. If every group communication were delivered to every member regardless of whether they were on duty, the network would carry large amounts of unwanted traffic, and users would be overwhelmed by irrelevant messages. Affiliation ensures that only users who have declared interest in a group receive its communications, reducing radio load and improving the user experience.

Finally, affiliation supports policy enforcement and operational awareness. Administrators and dispatchers can see which users are affiliated to which groups, which is valuable for situational awareness. Policies can restrict affiliation based on role, location, or capacity, giving organizations fine-grained control over who can participate in which communications. This combination of dynamic participation, resource efficiency, and policy control motivated the inclusion of affiliation as a first-class concept in the MC services architecture.

What changed in its specifications

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

Group affiliation was introduced as part of the MCData service, defined as an MC service group affiliation for MCData. Procedures for affiliation and de-affiliation between the MCData client and MCData server were specified in TS 23.282.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

The definition text carried over unchanged from Rel-14; the term continued to denote an MC service group affiliation for MCData.

Defining Specifications

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