Description
The Group Management Client (GMC) is a functional component residing within the User Equipment (UE) that is responsible for managing the UE's participation in group-based services. It acts as the endpoint for group management procedures defined by the network, specifically interacting with the Group Management Server (GMS) or ProSe Function for Proximity Services. The GMC's primary role is to handle group membership lifecycle events, including registration, deregistration, and updates. It receives and processes group configuration data and policies from the network, such as group identifiers, security keys, and service parameters, which are essential for the UE to participate in group communications like Mission Critical Push-to-Talk (MCPTT) or ProSe Direct Discovery and Communication.
Architecturally, the GMC is a logical entity often implemented as part of the UE's application layer or service layer stack, particularly for services standardized in 3GPP. It interfaces with lower-layer protocols and other client functions within the UE to apply received group policies. For instance, upon receiving a group membership authorization, the GMC may configure the UE's radio and session management layers to prioritize traffic for that group or establish necessary bearers. It also manages local storage of group-related data, ensuring the UE can operate correctly even when temporarily out of network coverage, by utilizing pre-configured policies and keys.
The GMC works in conjunction with core network functions like the GMS in the Home Subscriber Server (HSS) or a dedicated application server. The process typically begins with the GMC initiating a registration request for a specific group service. The network authenticates the UE and authorizes the group membership, after which the GMC receives a configuration package. This package includes critical information such as the Group Management Key (GMK) for security, group identifiers, and service-specific parameters. The GMC is then responsible for enforcing these parameters, monitoring for updates from the network, and handling events like group membership revocation. Its operation is crucial for scalable group services, as it offloads continuous management from the network by enabling UEs to manage local group states based on initial network directives.
Purpose & Motivation
The GMC was introduced to address the growing need for efficient and scalable group communication services in 3GPP networks, particularly with the rise of Mission Critical Services (MCS) and Proximity Services (ProSe) in Release 13. Prior approaches often relied on point-to-point or broadcast mechanisms that were inefficient for dynamic groups, lacking dedicated management entities in the UE to handle group-specific policies and security. This made service provisioning complex and limited the scalability of group applications like public safety communications or IoT group messaging.
The creation of the GMC standardizes the client-side behavior for group management, ensuring interoperability across different UE implementations and network vendors. It solves the problem of decentralized and inconsistent group policy enforcement by providing a defined functional entity within the UE that can reliably receive, store, and apply network-provided group configurations. This is especially important for services requiring secure, low-latency group interactions, where UEs must quickly adapt to group changes without constant network signaling.
Historically, group management was often handled ad-hoc within specific applications, leading to fragmentation. The GMC, as part of the 3GPP architecture, provides a unified framework. It enables network operators to efficiently manage large groups (e.g., first responder teams) by delegating management tasks to the client, reducing signaling load on the core network. This client-centric approach supports advanced features like off-network operation in ProSe, where UEs in proximity can communicate directly using group policies managed by the GMC.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the Group Management Client (GMC) function introduced support for "Group Configuration Multi-Talker" and included a correction for Group ID usage during group creation. Specifically, the GMC procedures were defined to enable the creation of a group document by sending an XML document via an HTTP PUT request with a Request-URI set to an XCAP URI using a group creation XUI configuration parameter.
In Release 16, the Group Management Client (GMC) was enhanced to support additional commencement modes for group calls. This required the GMC to manage updates to the group document in the Group Management Server (GMS) using XCAP procedures. The update specifically involved the GMC creating or modifying the XML group document according to the specified application usage to enable these new call commencement modes.
- Update group document to support additional commencement modes for group calls TS 24.481CR0039
In Release 17, the GMC function was enhanced with new group subscription service elements and the ability to mark a group for preconfigured-group-use-only within the group document. Furthermore, the group configuration update procedure was extended to support disabling functional alias (FA) de-affiliation for a group.
In Release 18, the GMC function was updated to support Mission Critical Services over 5G ProSe (Proximity-services) and Prose direct communication. The release also introduced clarifications for handling multiple GKTPs (Group Key Transport Parameters) within a group document and provided corrections to the associated XSD (XML Schema Definition).
Explore further
Broader topics and technologies where GMC plays a role.
Defining Specifications
3GPP specifications that define or reference GMC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.481 vj20 | Mission Critical Services (MCS) group management | Rel-19 |