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

Glossary term · Identifier

Group identity

Group Identity (MCVideo/MCPTT)

Identifier →

Group identity is a unique identifier for a group of users in mission-critical push-to-talk or video services, enabling one sender to reach many recipients through a single address.

Introduced
Rel-13
Where
Services › IMS
Specifications
3 specs
Group identity Description Purpose What changed Neighbours Detected Changes Specifications

Description

In 3GPP mission-critical services, a Group Identity (GID) is a key identifier used to address a collection of users as a single entity. It is defined in the MCPTT and MCVideo specifications (e.g., 24.281 for MCPTT, 24.282 for MCVideo, and 24.379 for MCVideo). The group identity can be either a permanent group identity (statically provisioned) or a temporary group identity (dynamically allocated, e.g., for a temporary group session). The group identity is used in the signalling protocols to establish and manage group calls, and it is also used for authorization and policy enforcement.

The group identity is typically a URI (Uniform Resource Identifier) or a numeric identifier that is unique within the mission-critical service domain. It is stored in the user's subscription and is used by the group management server (GMS) to manage group memberships. When a user initiates a group call, the group identity is included in the session establishment request, allowing the network to route the call to all group members. The group identity also plays a role in floor control, as it helps identify the group context for the media plane.

The concept of group identity was introduced in Release 13 as part of the first MCPTT specifications. Initially, the definition referred specifically to MCPTT group identity, but in Release 14 it was generalized to cover MCVideo as well, reflecting the expansion of mission-critical services beyond voice. The group identity is a fundamental building block for group communication, enabling efficient use of network resources and providing a scalable way to manage large groups of users.

In terms of architecture, the group identity is used by the MCPTT/MCVideo server (also known as the group call server) to identify the group and its members. The server interacts with the group management server to retrieve the group membership and with the policy and charging rules function (PCRF) for QoS authorization. The group identity is also used in the user profile (in the UDR) to indicate which groups a user belongs to. This allows the network to apply the appropriate QoS and security policies for group communication.

The group identity is a critical identifier for mission-critical services, as it enables the core functionality of group communication. Without a group identity, it would be impossible to efficiently address a group of users and manage their communication. The group identity also supports features such as late entry, pre-emptive priority, and emergency group calls, which are essential for public safety and other mission-critical users.

Purpose & Motivation

The Group Identity exists to provide a scalable and efficient way to address multiple users in mission-critical communication. In traditional cellular networks, each user is addressed individually, which is inefficient for group communication where a single message needs to reach many recipients. The Group Identity solves this by allowing a single identifier to represent a group, reducing signalling overhead and enabling the network to manage group sessions efficiently.

Historically, mission-critical communication was handled by dedicated narrowband systems like TETRA or P25, which had their own group identity concepts. 3GPP introduced the Group Identity in Release 13 as part of the MCPTT specifications to bring group communication to LTE. This evolution reflects the ongoing convergence of voice and video in mission-critical communications.

The Group Identity also enables advanced features such as group-based prioritization, where groups can be assigned priority levels for resource allocation during congestion. It also supports location-based group communication, where groups can be formed based on geographic areas. Overall, the Group Identity is a cornerstone of the 3GPP mission-critical architecture, providing the foundation for group-centric services.

What changed in its specifications

The latest release-to-release comparison of specifications that define Group identity. Each summary describes the whole specification, not only this term.

TS 24.281Rel-17 → Rel-18

Added MBS session management and XML schema types. Added MCVideo emergency and imminent peril adhoc group call procedures. Added MCVideo gateway UE function for non-3GPP access. Added 5G ProSe support to MCVideo. Added migration service authorization for MCVideo clients.

Full comparison in TS 24.281 →
TS 24.282Rel-17 → Rel-18

MCData location reporting, MCData adhoc group communications, 5G MBS Phase 2 procedures, gateway UE support, and ProSe term mappings are key Rel-18 additions.

Full comparison in TS 24.282 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-16 1 change
  • Support for MCData emergency alert and communications MCC note: This CR introduces the abbreviation IMPU; MCC has added this in the list of abbreviations, choosing the most appropriate of the five variations appearing in other 3GPP Specs. Similarly, MCC has provided the expansions of abbreviations UUID and URN introduced, but not defined by, this CR. The newly introduced term "Group identity" has a circular definition. In clause D.1.3,, "can" has been changed to "may" in newly introduced bullet points 11 c), 11 c) i), and 11 e). TS 24.282CR0126

Defining Specifications

3GPP specifications that define or reference Group identity, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.282 vk10 MCData Signalling Control Protocols Rel-20 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read