Description
MC service group affiliation is a mechanism defined in 3GPP Mission Critical (MC) services (23.280, 23.783) that allows an MC service user to indicate their interest in one or more MC service groups. When a user affiliates to a group, the MC service server records this interest and ensures that the user receives group communications (e.g., group calls, group messages) for that group. Affiliation is essential for group communication because it determines the set of users that should be invited to or notified of group sessions.
The affiliation process typically involves the client sending an affiliation request to the MC service server (e.g., via SIP PUBLISH or HTTP) indicating the group(s) the user wants to affiliate with. The server authenticates and authorizes the request based on the user's profile and group policies, and then updates the affiliation status. The server may also notify other servers or the group management server about the affiliation. The user can affiliate to multiple groups simultaneously, and can also de-affiliate when they no longer wish to receive group communications.
Affiliation is closely tied to the group definition and the user's profile. The group may have policies that restrict affiliation (e.g., only users with a certain role can affiliate), and the user's profile may limit the number of groups they can affiliate with. The affiliation status is used by the server to determine the participants for a group call: when a group call is initiated, the server invites all affiliated users (or uses multicast/broadcast to reach them). Affiliation also affects the delivery of group messages and other group data.
The mechanism supports both explicit and implicit affiliation. Explicit affiliation occurs when the user actively requests to join a group. Implicit affiliation may occur when the user initiates a group call or sends a group message, which can automatically affiliate them to the group if allowed by policy. The server maintains the affiliation state and may expire affiliations after a configured time or when the user deregisters.
In the overall architecture, group affiliation is a key enabler for efficient group communication. It allows the network to know the potential recipients of group traffic without requiring the initiator to specify each recipient. It also enables the use of broadcast/multicast technologies (e.g., eMBMS) for group communication, as the network can target only the affiliated users in a given area. The affiliation mechanism is standardized to ensure interoperability between clients and servers from different vendors.
Purpose & Motivation
MC service group affiliation exists to manage the dynamic membership of users in MC service groups for communication purposes. In mission-critical operations, users may join or leave groups based on their current role or assignment. For example, a police officer may affiliate with a group when starting a shift and de-affiliate when off-duty. The affiliation mechanism allows the network to track this interest in real-time, ensuring that group communications are delivered only to those who need them, thus optimizing resource usage and avoiding unnecessary notifications.
Before standardized MC services, group membership was often static and managed through provisioning, which was inflexible for dynamic operations. The affiliation mechanism provides a standardized, dynamic way for users to express interest in groups, enabling more efficient group communication and better alignment with operational needs. It also supports the use of advanced delivery methods like multicast, as the network can determine the set of affiliated users for a group in a specific area.
The affiliation mechanism also enhances security and policy enforcement: the server can verify that a user is allowed to affiliate with a group before accepting the request, preventing unauthorized users from receiving sensitive group communications. It also allows the group management server to track group usage and adjust configurations accordingly.
What changed in its specifications
The latest release-to-release comparison of specifications that define MC service group 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 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 |