GMD

Group Message Delivery

Services →
Introduced in Rel-15

GMD is a service capability that enables efficient delivery of messages to a group of users or devices by using group addressing to optimize network resources.

Category
Services
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
1 specs
GMD Description Purpose Related Classification Detected Changes Specifications

Description

Group Message Delivery (GMD) is a network service capability that facilitates the efficient dissemination of messages to a defined group of recipients, such as User Equipments (UEs) or IoT devices. Unlike individual message delivery, which requires separate transactions per recipient, GMD leverages group addressing to minimize signaling overhead and optimize resource utilization across the core network and radio access network. It is typically implemented within the Service Capability Exposure Function (SCEF) or Application Server architectures, interacting with core network functions like the HSS for group membership resolution and the MME/SGSN for delivery triggering. The service handles both mobile-terminated and application-triggered messages, ensuring reliable delivery to group members regardless of their attachment status through mechanisms like deferred delivery.

Architecturally, GMD operates by defining a group identifier that represents the target set of recipients. When an application or network function initiates a group message, the GMD capability resolves this group identifier into a list of individual subscriber identifiers (e.g., IMSIs or MSISDNs) by querying group membership repositories. It then orchestrates the delivery process, which may involve interfacing with the Short Message Service Center (SMSC) for SMS-based delivery or using IP-based mechanisms like HTTP/2 for data messages. For IoT scenarios, GMD often integrates with the SCEF to provide network APIs for application servers, allowing them to request group message delivery without needing direct access to core network interfaces.

The workflow involves several key components: the GMD service itself, group management databases, and delivery gateways. Upon receiving a delivery request, the GMD service authenticates the requesting entity and validates the group authorization. It then determines the optimal delivery method based on message type, recipient capabilities, and network conditions. For example, for non-real-time IoT device updates, it may use background delivery with network triggering to wake up devices in power-saving mode. The service also implements delivery reports and error handling, providing feedback to the originator about the success or failure of the message delivery to group members. This ensures accountability and allows for retry mechanisms in case of temporary failures.

Purpose & Motivation

GMD was introduced to address the inefficiencies of mass message delivery in cellular networks, particularly with the exponential growth of IoT and machine-type communications in Release 15. Traditional message delivery methods, such as individual SMS or IP packets per recipient, generated excessive signaling traffic and core network load when scaling to thousands or millions of devices, leading to congestion and degraded performance for other services. This was a critical limitation for use cases like firmware updates for IoT devices, emergency alert broadcasting, or command-and-control messages for mission-critical teams.

The creation of GMD provides a standardized, network-optimized mechanism for group-oriented messaging. It solves the problem of scalable message dissemination by introducing group addressing, which allows a single message transaction from the application layer to be efficiently fanned out to multiple recipients by the network. This reduces latency, signaling overhead, and resource consumption compared to sequential unicast deliveries. It also enables new service models where applications do not need to manage individual device addresses, simplifying application logic.

Historically, group messaging was often implemented at the application layer without network awareness, leading to suboptimal radio and core network utilization. GMD, as a network capability, allows operators to control and optimize the delivery process. It supports features like delivery time optimization, priority handling, and integration with network triggering services for IoT devices in idle mode. This is especially important for 5G and massive IoT deployments, where efficient group communication is essential for managing large device fleets in smart cities, industrial automation, and public warning systems.

Classification

Part ofSMS
Related approachesMTC

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 9 changes

In Release 15, the GMD function was enhanced with corrections to its delivery procedures via the MB2, xMB, and MBMS interfaces, and its APIs received successful code corrections. The release also introduced the capability for an additional external group ID to indicate the number of UEs in an area and addressed specific issues such as a missing UE ID in GMD acknowledgements. Furthermore, support was added for partial group modification, allowing the SCS/AS to cancel or add specific UEs within an active group via an HTTP PATCH request.

  • Remove the monitoring configuration for a group TS 29.122CR0011
  • Correct group NIDD procedure TS 29.122CR0039
  • Correct GMD via MB2 TS 29.122CR0065
  • Correct GMD via xMB TS 29.122CR0066
  • Additional external group ID for number of UE in an area TS 29.122CR0083
  • Correct GMD via MBMS TS 29.122CR0089

+ 3 more changes

Rel-16 6 changes

In Release 16, the GMD function was enhanced to allow the cancellation or addition of specific UEs within an active monitoring group via an HTTP PATCH request, a feature referred to as "Partial_group_modification". Furthermore, support was explicitly defined for using an External Group Identifier in configuration requests to target a group of UEs for monitoring events. The release also clarified procedures for handling failure responses from the SCEF northbound APIs.

  • Notification of Downlink data delivery status and availability after DDN failure notification for multiple Afs TS 29.122CR0156
  • Add External Group Id TS 29.122CR0157
  • URI of the SCEF northbound APIs TS 29.122CR0249
  • Removal of open issue on external Group Id for ResourceManagementOfBdt API TS 29.122CR0256
  • Correct SCEF aggregation TS 29.122CR0208
  • Failure response for SCEF northbound APIs TS 29.122CR0307
Rel-17 3 changes

In Release 17, the GMD function was updated to support redirection for pure 4G SCEF northbound APIs and included resource URI corrections for the GMD via MBMS APIs. Additionally, specific resource corrections were made for the SCEF Northbound APIs to ensure proper configuration and interaction procedures.

  • Support redirection for pure 4G SCEF northbound APIs TS 29.122CR0406
  • Resource URI correction in the GMD via MBMS APIs TS 29.122CR0480
  • Resource corrections for SCEF Northbound APIs TS 29.122CR0415
Rel-18 2 changes

In Release 18, the Group Message Delivery (GMD) function was enhanced to support a **Group Member List Change event**, allowing the SCS/AS to subscribe to notifications when the membership of a targeted group changes. Furthermore, the update procedure was refined by **removing the multiModalId from the update message** and updating the associated terminology. These changes provided more dynamic group management and streamlined the protocol for group-based monitoring configurations.

  • Support of Group Member List Change event TS 29.122CR0659
  • Remove the multiModalId in the update message and update the terminology TS 29.122CR0785
Rel-19 1 change

In Release 19, the GMD function was enhanced to enable the provisioning of the "MPS for Messaging Indication" parameter via the SCEF. This allows the SCS/AS to configure this specific indication for a group of UEs using the defined External Group Identifier and the SCEF's existing interaction with the HSS via the S6t interface.

  • MPS for Messaging Indication parameter provisioning via SCEF TS 29.122CR0880

Explore further

Broader topics and technologies where GMD plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.122 vj40 T8 Reference Point for Northbound APIs Rel-19