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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (183 CRs across 6 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 Server (GMS) function was enhanced with new procedures for MC server-initiated group de-affiliation, both within the home system and from groups in a partner MC system. It introduced support for interconnection groups, allowing the configuration of groups that include members from partner systems, and defined the role of an MC gateway server for topology hiding in such interconnections. Additionally, new capabilities were added for group regrouping operations, application group paging, and enhanced group call setup.
- Introduction of MC server initiated group de-affiliation procedure TS 23.280CR0026
- Enhancement on group regrouping with an MC system TS 23.280CR0052
- MC server initiated group de-affiliation from group(s) in partner system TS 23.280CR0053
- Resource Management in CFA TS 23.280CR0059
- Group configuration for interconnection TS 23.280CR0074
- Service type for group regroup TS 23.280CR0076
+ 36 more changes
In Release 16, the Group Management Server (GMS) introduced capabilities for automatic group affiliation and de-affiliation based on a user's location or functional alias, and enhanced group regroup procedures with clarifications for rules and broadcast group regroup. It also added support for notifying group status over MBMS and for managing implicit functional aliases, while introducing new commencement modes for group calls and mechanisms to limit emergency group calls per functional alias. Furthermore, improvements were made to group creation requests, temporary group formation notifications, and the management of server URIs for media storage and location management.
- Regroup group configuration TS 23.280CR0171
- Broadcast group regroup TS 23.280CR0174
- Group status notification over MBMS TS 23.280CR0178
- Implicit functional alias management TS 23.280CR0188
- Update group document to support additional commencement modes for group calls TS 24.481CR0039
- MO for limiting the number of emergency group calls for a specific functional alias TS 24.483CR0058
+ 14 more changes
In Release 17, the Group Management Server (GMS) saw enhancements for managing functional aliases, including the provisioning of activated functional alias information and the list of functional aliases used by affiliated group members. It also introduced new management object configurations for functional alias association with groups and for limiting the number of MCData emergency groups per functional alias. Furthermore, the release added capabilities for temporary group teardown within an MC system and provided clarifications on preconfigured group usage.
- Providing activated functional alias information to the group controlling server TS 23.280CR0207
- Providing the list of functional aliases used by affiliated group members TS 23.280CR0208
- Dynamic data associated with a group at GMS TS 23.280CR0260
- Clarification on user subscription, group policy and functional alias policy TS 23.280CR0258
- Request for network resources at session establishment from the MC service server TS 23.280CR0278
- Server side procedures for unicast media Stop and Resume TS 24.380CR0292
+ 31 more changes
In Release 18, the GMS function was enhanced with new capabilities for ad hoc group emergency alerts, including procedures for initiating alerts between multiple MC systems, managing the participants list, and allowing subsequent MCVideo and MCData communications after an alert. It also introduced support for preconfigured regrouping for MCPTT and a procedure for group de-affiliation for a specific UE. Furthermore, updates were made to manage migration during ongoing group communication and to support service de-authorization initiated by an MC service server.
- MCGWUE 3GPP access network related location information management TS 23.280CR0300
- Migration during an ongoing group communication TS 23.280CR0315
- Partner MC service server stores necessary information for communication redirection TS 23.280CR0355
- Introduction of the ad hoc group emergency alert TS 23.280CR0356
- Migration service de-authorization procedure initiated by MC service server TS 23.280CR0363
- Preconfigured regrouping support for MCPTT TS 23.280CR0366
+ 31 more changes
In Release 19, the Group Management Server (GMS) function was enhanced with new capabilities for dynamic group management during emergency alerts and active sessions, including the ability to modify participant criteria for ongoing ad hoc group emergency alerts within single or multiple MC systems and to perform regroup group member updates during an MCX session. It also introduced formalized administrative and recording interfaces, such as the interface between the MC service server and the Recording Server, and new procedures for the Administrative Configuration Management Server (ACMS) to handle user migration, group configuration, and interconnection group IDs. Furthermore, new information elements were added for ad hoc group emergency alerts, and specific target group configuration for recording was defined.
- Modify list of participants by changing the criteria during an ongoing ad hoc group emergency alert (single MC system) TS 23.280CR0413
- Changing the criteria during an ongoing ad hoc group emergency alert (multiple MC systems) TS 23.280CR0432
- Add the regroup group member update during MCX session TS 23.280CR0441
- Distribute criteria of an ad hoc group emergency alert request to authorised users TS 23.280CR0464
- ACM Group configuration management TS 23.280CR0466
- ACM providing interconnection MC service group ID TS 23.280CR0506
+ 34 more changes
In Release 20, the GMS function was enhanced to formally incorporate ad hoc groups into its preconfigured regroup procedures, allowing these temporary groups to be used as sources for regrouping operations. Furthermore, the generic migration procedure for ongoing group communications was extended to include the MCData service. These updates were accompanied by clarifications and corrections to location management and MC service group ID handling.
- Adding MCData to generic procedure for migration during an ongoing group communication TS 23.280CR0658
- Preconfigured ad hoc group regroup procedure TS 23.280CR0705
- Updating preconfigured regroup IE to include ad hoc groups TS 23.280CR0706
- Updating general clause of preconfigured regroup to include ad hoc group regroup TS 23.280CR0707
- Revised CSC-15: Incorporating Additional LMS and MC Service Server Interactions TS 23.280CR0671
- Corrections to location management TS 23.280CR0699
+ 1 more changes
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.
| Specification | Title | Release |
|---|---|---|
| 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 |