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

Glossary term · Services

MCData group de-affiliation

Mission Critical Data Group De-affiliation

Services →

MCData group de-affiliation is a procedure by which an MCData user leaves or is removed from an MCData group, terminating group data delivery and ensuring users receive data only for groups they belong to.

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

Description

MCData group de-affiliation is a service-level procedure within the Mission Critical Data (MCData) service defined by 3GPP. MCData, specified in TS 23.282, provides mission-critical data communication capabilities such as short data messages, file distribution, and data streaming over LTE and 5G networks. Group de-affiliation is the counterpart to group affiliation: it removes a user's binding to a particular MCData group, meaning the user will no longer receive group communications (e.g., group messages or files) for that group and will not be considered an active member for group data delivery.

The procedure is executed via the MCData server, which is part of the broader Mission Critical Services (MCX) architecture. The MCData server maintains group membership and affiliation state. When a user de-affiliates, the MCData client sends a de-affiliation request to the server, which validates the request, updates the affiliation state, and notifies other relevant entities (such as the group management server or other group members) as needed. De-affiliation can be initiated by the user (voluntary) or by the server (e.g., due to policy, subscription changes, or administrative action).

Group de-affiliation is critical for resource management and privacy. By de-affiliating, a user stops consuming radio and network resources for group data that is no longer relevant. It also ensures that sensitive group data is not delivered to users who should no longer have access. In mission-critical environments, timely de-affiliation can be important when a responder leaves an incident or changes roles.

The procedure interacts with the group management framework (TS 23.783) which defines how groups are created, modified, and deleted. De-affiliation may be triggered implicitly when a group is disbanded or when a user's subscription changes. The MCData server must maintain consistency between affiliation state and group membership, and may enforce policies such as maximum number of affiliated groups per user.

From a protocol perspective, de-affiliation uses the MCData session control and group management protocols, typically SIP-based for session control and HTTP-based for group management. Security is provided by the underlying MCX security mechanisms (identity, authentication, authorization). The procedure is specified in 3GPP TS 23.282 and TS 23.783, and has remained stable across Releases 14 through 20, indicating a mature and well-understood function.

Purpose & Motivation

MCData group de-affiliation exists to provide controlled exit from group data communications. In mission-critical systems, users often belong to multiple groups (e.g., incident command, tactical teams, dispatch). Without a de-affiliation mechanism, users would continue to receive group data even after leaving a group, wasting resources and potentially causing confusion or security risks. The procedure solves this by explicitly removing the user from the group's active recipient list.

Historically, mission-critical data services evolved from voice-centric systems (MCPTT) where group affiliation was already defined. MCData extended this concept to data, requiring its own de-affiliation semantics because data groups may have different membership dynamics and delivery models (e.g., file distribution vs. short messages). The de-affiliation procedure ensures that group data delivery is efficient and respects user intent and policy.

Prior to standardized MCData, proprietary systems had ad-hoc ways to leave groups, leading to interoperability issues. 3GPP standardized de-affiliation to ensure consistent behavior across vendors and networks, enabling seamless group management in multi-vendor mission-critical deployments.

What changed in its specifications

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

Initial definition introduced with the MCData service. Specified the concept of group de-affiliation as the mechanism for a user to leave an MCData group, with procedures defined in TS 23.282 and group management in TS 23.783.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Definition carried over unchanged from Rel-14; no textual modification to the term's description.

Defining Specifications

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