Description
MCVideo group affiliation is a core concept in the 3GPP Mission Critical Video (MCVideo) service, defined in TS 23.281 (functional architecture and information flows) and TS 23.783 (MCVideo media handling and codecs). MCVideo is one of the Mission Critical Services (MCX) family, alongside MCPTT (push-to-talk) and MCData, and is designed for public safety and critical-communications users who need to share real-time video in operational scenarios.
Affiliation is the mechanism by which a user (through their MCVideo client and identity) registers interest in a particular MCVideo group. When a user affiliates to a group, the MCVideo server records that the user is an active member of that group. This has two important consequences. First, the affiliated user becomes eligible to receive group video transmissions — for example, a live video stream initiated by another group member. Second, the affiliation state is used by the server for group management functions such as determining the set of recipients for a group call, computing group membership for floor control and media distribution, and supporting group regrouping and temporary group creation.
The affiliation procedure is carried out over the CSC (Common Services Core) functional architecture. The MCVideo client sends an affiliation request to the MCVideo server via the SIP-based signalling interface (using the CSC-3 interface toward the participating MCVideo function and onward to the controlling MCVideo function). The server validates the request against the user's service authorization and group configuration (stored in the group management server and the user database), and then updates the affiliation state. The server may respond with the current affiliation status and, in some cases, the aggregated list of affiliated members if the user is authorized to see it.
Affiliation is distinct from group membership. A user may be a configured member of a group (provisioned in the group management server) but not affiliated, in which case the user will not receive group communications until they affiliate. Conversely, affiliation can be dynamic: users can affiliate and de-affiliate during operation, for example when moving between operational roles or incident areas. The MCVideo server maintains affiliation state per user per group and uses it to drive media distribution decisions, so affiliation directly affects which users receive group video streams and therefore the bandwidth and resource consumption of the system.
In the overall MCVideo architecture, group affiliation interacts with the group management, identity management, and configuration management functions. It also underpins features such as late entry, where a user who affiliates after a group session has started can be brought into the ongoing session. Because MCVideo is intended for bandwidth-constrained and priority-managed environments, accurate affiliation state is essential for efficient use of network resources and for meeting the strict latency and reliability requirements of mission-critical communications.
Purpose & Motivation
MCVideo group affiliation exists to give the mission-critical video service a precise, dynamic notion of which users are currently participating in which groups. In public-safety operations, group membership is often broad and pre-provisioned, but only a subset of users is actively engaged at any moment. Affiliation lets the system track that active subset in real time, so that group video is delivered only to users who need it, conserving radio and backhaul resources in bandwidth-limited environments.
Before MCX services, group voice and video were typically handled by proprietary systems with static talkgroup configurations. 3GPP's MCVideo specifications introduced standardized, SIP-based affiliation procedures so that clients from different vendors and operators can interoperate, and so that affiliation state can be managed consistently across the Common Services Core. This standardization was motivated by the need for multi-vendor, multi-operator mission-critical deployments where users roam across networks and still need to join their operational groups.
Affiliation also solves the problem of authorization and policy enforcement. By requiring an explicit affiliation request that the server validates against service authorization and group configuration, the system ensures that only entitled users receive sensitive group video. It provides the hook for priority and QoS treatment, since affiliated users can be given the appropriate mission-critical QoS flows, and it enables operational features such as late entry and group regrouping that depend on knowing the current active membership.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCVideo group affiliation. Each summary describes the whole specification, not only this term.
Enhanced Mission Critical Architecture adds MCVideo procedures for ad hoc group call release, leave, and criteria modification, plus call handling during group regroup.
Full comparison in TS 23.281 →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.
MCVideo group affiliation was introduced with the initial MCVideo specifications in TS 23.281 and TS 23.783, establishing the SIP-based affiliation procedure within the Common Services Core architecture and defining affiliation as an MC service group affiliation for MCVideo.
Defining Specifications
3GPP specifications that define or reference MCVideo group affiliation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.281 vk51 | Mission Critical Video Service | Rel-20 read |
| TR 23.783 vi00 | Technical Report on Mission Critical Services over 5GS | Rel-18 read |