Group Document

Description

In 3GPP mission-critical services, a Group Document is a critical data structure stored and managed by the Group Management Server (GMS). It contains all the information necessary to define a communication group, including the group identity, the list of members, their roles and priorities, and various policies that govern group communication. The Group Document is specified in 3GPP TS 24.481, which defines the group management protocols for MCPTT, MCVideo, and MCData services. The term 'Group Document' is used in specifications such as TS 24.281 (MCPTT), TS 24.282 (MCData), and TS 24.379 (MCVideo) to refer to this data structure.

The Group Document serves as the authoritative source for group configuration. When a group communication session is established, the GMS provides the relevant Group Document information to the participating entities, such as the Group Communication Service Enabler Application Server (GCS AS) and the group members' clients. This ensures that all parties have a consistent view of the group's membership and policies. The Group Document includes attributes such as the group's display name, the maximum number of members, the media types allowed (e.g., voice, video, data), and the priority level of the group.

For preconfigured groups, the Group Document is created and maintained in the GMS by the Group Controller or an administrator. For dynamic groups, such as those created on-the-fly during an incident, the Group Document is generated when the group is created. In the case of a regroup, which is a temporary group formed by combining members from existing groups, the Group Document is derived from the preconfigured group's document but restricted to the users or groups included in the regroup. The MCVideo server (or MCPTT server) stores this restricted view at the time of regroup creation.

The Group Document also plays a role in security and authorization. It defines which users are allowed to participate in the group and what actions they can perform, such as initiating a group call or sending data. The GMS enforces these policies by checking the Group Document before allowing a user to join or perform actions. This prevents unauthorized access and ensures that group communication adheres to organizational policies.

In terms of implementation, the Group Document is typically represented as an XML document or a similar structured format. The GMS provides interfaces for creating, reading, updating, and deleting Group Documents, as defined in TS 24.481. These interfaces are used by Group Controllers and other authorized entities to manage groups. The Group Document is also used by the GMS to synchronize group information across multiple servers in a distributed deployment, ensuring consistency and high availability.

Purpose & Motivation

The Group Document exists to provide a standardized, structured representation of a communication group's configuration and membership. Without a formal definition, group management would be ad-hoc and vendor-specific, leading to interoperability issues and inconsistent behavior across different network elements. The Group Document ensures that all entities involved in group communication have a common understanding of the group's parameters.

The need for Group Documents became particularly acute with the introduction of mission-critical services in 3GPP Release 13 and beyond. These services require strict control over group membership and policies to meet the demands of public safety and other mission-critical users. For example, a group document can specify that only certain users have the right to initiate emergency calls, or that the group has a higher priority than others. This level of control is essential for ensuring that critical communications are not disrupted by non-critical traffic.

Furthermore, the Group Document enables dynamic group management. In rapidly changing scenarios, such as a major incident, groups may need to be created or modified quickly. The Group Document provides a flexible and extensible way to define groups, allowing Group Controllers to adapt to evolving needs. The concept of regroup, where a temporary group is formed from existing groups, is also facilitated by the Group Document, which defines how the regroup inherits properties from the preconfigured group. Overall, the Group Document is a cornerstone of 3GPP's group communication framework, providing the necessary structure and control for mission-critical group services.