SGM-S

SEAL Group Management Server

Management →
Introduced in Rel-16

SGM-S is the core network function for managing SEAL groups, handling their membership, configuration, and policy to enable efficient group-based communication and resource management.

Category
Management
Introduced
Rel-16
Where
Services
Specifications
1 specs
SGM-S Description Purpose Related Classification Detected Changes Specifications

Description

The SEAL Group Management Server (SGM-S) is a critical component within the 3GPP architecture for managing Service Access Layer (SEAL) groups. SEAL is a framework designed to provide efficient, group-based communication services, particularly relevant for IoT and V2X applications. The SGM-S acts as the central authority for these groups, residing within the core network. Its primary function is the creation, modification, deletion, and overall lifecycle management of SEAL groups. It maintains a database of group memberships, which can include UE (User Equipment) identifiers, and is responsible for distributing group configuration information to relevant network entities, such as the SEAL Group Management Client (SGM-C) in the UE or other network functions.

Architecturally, the SGM-S interacts with other core network functions via standardized interfaces defined in specifications like 24.544. It receives requests for group management operations, authenticates and authorizes these requests, and then executes the necessary actions. This includes provisioning group policies, which dictate how group communication should be handled—for example, defining QoS parameters, security contexts, or routing rules for group traffic. The SGM-S ensures consistency and synchronization of group state across the network, which is vital for services where multiple UEs must act in a coordinated manner based on their group affiliation.

From an operational perspective, the SGM-S works by processing management commands. When a new SEAL group is to be established, perhaps for a fleet of connected vehicles or a set of industrial sensors, an authorized entity (like an application server or network administrator) sends a request to the SGM-S. The server validates the request, creates the group record, assigns a unique Group ID, and defines the initial membership and policies. It then propagates this information. For ongoing management, the SGM-S handles member additions and removals, policy updates, and group dissolution. Its role is purely management and control; it does not directly handle the data traffic of the group members but provides the necessary control plane information so that other network functions (like the User Plane Function or access nodes) can correctly process the group's communication flows.

Purpose & Motivation

The SGM-S was created to address the need for scalable and efficient management of group-based services in mobile networks. Prior to its introduction, group communication (e.g., for IoT or public safety) often relied on ad-hoc methods or application-layer management, which lacked integration with the network's control plane. This resulted in inefficiencies, poor resource utilization, and difficulty in applying network-level policies like QoS or security uniformly to a group. The SEAL framework, including the SGM-S, was motivated by the growing demand for V2X (Vehicle-to-Everything) communication and massive IoT deployments, where thousands of devices need to be treated as a logical group for communication and management purposes.

Historically, managing groups of UEs required individual signaling to each member or relied on broadcast/multicast techniques without fine-grained control. The SGM-S provides a standardized, network-integrated solution. It solves the problem of centralized, authoritative group management, enabling the network to optimize resources by treating the group as a single entity for certain control procedures. This reduces signaling overhead and allows for the application of group-specific policies that are enforced by the network itself, leading to more reliable and performant group services. Its creation in Release 16 aligns with 3GPP's broader efforts to enhance support for advanced services like automotive and industrial IoT, where group dynamics are fundamental.

Classification

Part ofSEAL
Related approachesV2X

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 7 changes

In Release 16, the SGM-S function was enhanced with new SIP-based subscribe/notify procedures for group management and the ability to send an indication to the SGM-C when a group join is required. The release also introduced procedures for an Identity List notification, corrections to group creation, modification, and announcement procedures, and updates for configuring VAL group requests.

  • SIP based subscribe/notify procedures for SEAL group management TS 24.544CR0001
  • Adding IANA registration template for SEAL group document TS 24.544CR0005
  • Indication from SGM-S to SGM-C about group join required TS 24.544CR0003
  • Corrections to group creation procedure TS 24.544CR0009
  • Adding Identity List notification and corrections to group announcement procedure TS 24.544CR0010
  • Corrections to group modification procedure TS 24.544CR0011

+ 1 more changes

Rel-17 22 changes

In Release 17, the SGM-S function was enhanced with comprehensive support for the Constrained Application Protocol (CoAP), introducing new procedures for group creation, information query, membership management, configuration, and subscription/notification. This release also added specific capabilities for managing temporary groups and location-based group creation via CoAP, and enabled 5G Core Network capabilities for SEAL groups. Furthermore, it introduced a formal boot-up procedure and provided support for 5G-VN groups.

  • Group list fetch procedure TS 24.544CR0016
  • Client side of temporary groups procedure TS 24.544CR0021
  • Server side of temporary groups procedure TS 24.544CR0022
  • Addition of CoAP Group creation procedure TS 24.544CR0025
  • Addition of CoAP Group information query procedure TS 24.544CR0026
  • Addition of CoAP Group membership procedure TS 24.544CR0027

+ 16 more changes

Rel-18 1 change

In Release 18, the SEAL Group Management Server (SGM-S) introduced a new **group deletion procedure**. This addition provides a standardized method for removing VAL groups, complementing the existing group creation and management functionalities defined for the SGM-S and its interactions with the SGM-C and VAL servers.

Explore further

Broader topics and technologies where SGM-S plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.544 vj00 SEAL Group Management Protocol Rel-19