Description
MC service group de-affiliation is the inverse of affiliation within the Mission Critical Services (MCX) framework. In MCX, a user expresses communication interest in a group by affiliating to it; de-affiliation removes that interest. Once de-affiliated, the user is no longer considered an active recipient of group call traffic for that group, and the controlling MC service server stops delivering media to that user for the affected group(s).
The procedure is managed by the Group Management Server (GMS) and the participating MC service server, as specified in 3GPP TS 23.280 and TS 23.783. De-affiliation can be initiated explicitly by the user (via the MC service client), triggered automatically by the server (for example, on session termination, inactivity, or policy enforcement), or as a consequence of administrative actions. The server updates the affiliation state and may notify the user and other functional entities accordingly.
De-affiliation is important for resource efficiency: group calls may involve large groups, and keeping every member affiliated at all times would consume radio and core network resources unnecessarily. By allowing users to de-affiliate from groups they are not actively monitoring, the network can avoid delivering unwanted media and can release unicast or multicast resources. It also supports policy and security controls, such as removing a user's interest when authorization changes.
Operationally, de-affiliation interacts with group call delivery: a de-affiliated user will not receive group call media unless they re-affiliate. The mechanism is symmetric with affiliation and is part of the broader group management procedures that include group creation, membership management, and affiliation state tracking. It is essential for maintaining accurate group state and for scaling MCX deployments to many groups and users.
Purpose & Motivation
MC service group de-affiliation exists to let users and the network manage which groups a user is actively interested in receiving. Without a de-affiliation mechanism, users would remain affiliated indefinitely, causing the network to deliver group traffic to users who no longer wish to monitor a group, wasting radio resources and device battery.
It also provides a control point for policy enforcement and administrative management: operators and administrators can remove a user's interest in a group when authorization changes or when the user leaves an organization. This supports accurate group state and efficient scaling of MCX services across many groups.
The mechanism complements affiliation, forming a complete lifecycle for group interest management that is fundamental to the group communication model standardized in 3GPP MCX specifications.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC service group de-affiliation. Each summary describes the whole specification, not only this term.
Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference MC service group de-affiliation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |