GMS

Group Management Server

Services →
Introduced in Rel-13 Also in: Security

GMS is a core network function that manages group communication services by handling group membership, configuration, and service authorization.

Category
Services
Introduced
Rel-13
Where
Services › IMS
Also touches
1 segments
Specifications
16 specs
GMS Description Purpose Related Classification Detected Changes Specifications

Description

The Group Management Server (GMS) is a critical functional entity within the 3GPP architecture for Mission Critical Services (MCS), standardized as part of the Mission Critical Push-to-Talk (MCPTT) framework. It operates within the service layer, separate from the underlying IP Multimedia Subsystem (IMS) or Evolved Packet Core (EPC)/5G Core (5GC), and is responsible for the centralized management of groups. A group is a fundamental construct in MCPTT, defining a set of users authorized to communicate with each other. The GMS maintains a persistent database of all groups, their members, and associated attributes such as group identity, priority levels, floor control policies, and geographic scopes.

Architecturally, the GMS interfaces with several other MCPTT functions. It communicates with the MCPTT Application Server (AS) to provide group configuration data necessary for establishing and controlling group sessions. It also interfaces with the Key Management Server (KMS) for security key distribution specific to groups and with the Configuration Server for provisioning. The GMS exposes northbound interfaces (e.g., Mcx interface) for external management by authorized administrators or systems, allowing for the creation, modification, and deletion of groups and memberships. Its operation is defined to be highly reliable and available, as it is essential for emergency and mission-critical operations.

From a procedural standpoint, the GMS is involved whenever a user initiates or joins a group call. The MCPTT client or AS queries the GMS to validate the user's membership and retrieve the group's operational parameters. The GMS also manages dynamic group affiliations, where users can join or leave groups on-the-fly based on their role or situation. It supports complex group hierarchies, including sub-groups and talk groups, and can enforce policies based on user priority, pre-emption rights, and emergency states. In essence, the GMS acts as the authoritative source of truth for group definitions, ensuring that communication is organized, secure, and adheres to the predefined operational rules of the mission-critical service.

Purpose & Motivation

The GMS was created to address the specific and stringent requirements of professional and public safety communication, which rely heavily on instant, reliable, and organized group communication. Traditional cellular services like voice calls or SMS were designed for one-to-one communication and lack the structured group management, priority handling, and security needed for coordinated team responses in emergencies. Before its standardization, proprietary systems like Terrestrial Trunked Radio (TETRA) offered group features but were isolated, expensive, and not integrated with broadband cellular networks.

The introduction of the GMS within 3GPP's Mission Critical Services framework allows public safety agencies to leverage commercial 3GPP networks (4G LTE and 5G) for critical communications. It solves the problem of scalable, secure, and manageable group communication over IP networks. By centralizing group management, it eliminates the need for each application server or client to maintain its own inconsistent group lists, ensuring uniformity and security across the entire service footprint. Its creation was motivated by global initiatives, such as those led by the First Responder Network Authority (FirstNet) and the European Telecommunications Standards Institute (ETSI), to develop standardized, interoperable, and future-proof critical communication solutions.

Classification

Part ofMCPTT

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the Group Management Server (GMS) was introduced as a new functional entity for Mission Critical (MC) services to manage pre-defined groups. It provides group and call policy information to UEs and interacts with clients and other servers via new reference points like CSC-2 and CSC-10. The release also specified procedures for GMS selection during group regroup operations.

  • GMS selection during group regroup TS 23.280CR0107
Rel-16 1 change

In Release 16, the Group Management Server (GMS) was enhanced to manage affiliation status information for group members. This new capability, as indicated by the Change Request, specifically applies to pre-arranged groups, where affiliated members are invited when group communication is set up. This allows the GMS to track and utilize a member's affiliation status as part of group management operations.

  • Proposal for affiliation status information in group management server TS 23.280CR0165
Rel-17 1 change

In Release 17, the GMS (Group Management Server) was enhanced to support dynamic data associated with a group. This introduces new configuration capabilities over the CSC-2 reference point, allowing both the group management client and the server to configure this dynamic group-related data.

  • Dynamic data associated with a group at GMS TS 23.280CR0260
Rel-19 1 change

In Release 19, the GMS function introduced a new standardized reference point, REC-5, between the Group Management Server and the recording server. This interface allows the recording server to obtain information related to target groups for recordings, including group-related key material. This addition formally integrates the GMS into the recording service architecture for mission-critical communications.

  • Add reference point between GMS and recording server TS 23.280CR0656

Explore further

Broader topics and technologies where GMS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.280 vk10 Common Architecture for Mission Critical Services Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.781 vf00 Study on MC services migration & interconnection Rel-15
TS 23.782 vf00 Interworking between LTE MC and non-LTE MC systems Rel-15
TS 23.784 vg00 Discreet Listening for Mission Critical Services Rel-16
TS 24.380 vj10 MCPTT Media Plane Control Protocol Rel-19
TS 24.481 vj20 Mission Critical Services (MCS) group management Rel-19
TS 24.483 vj20 Mission Critical Services Management Object Rel-19
TS 24.581 vj00 MCVideo Media Plane Control Protocol Specification Rel-19
TS 29.380 vj00 MCPTT-LMR Interworking Media Plane Control Rel-19
TS 29.582 vj00 MCData Interworking with LMR Systems Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.179 vdc0 MCPTT Security Architecture and Procedures Rel-13
TS 33.180 vk00 Security of Mission Critical (MC) Service Rel-20
TS 33.879 vd10 MCPTT Security Study Rel-13
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.