SDDM-S

SEAL Data Delivery Management Server

Services →
Introduced in Rel-18

SDDM-S is the server within the SEAL Data Delivery Management framework that publishes data sets, manages and authorizes client subscriptions, stores publication data, and triggers delivery to authorized subscribers.

Category
Services
Introduced
Rel-18
Where
Services
Specifications
2 specs
SDDM-S Description Purpose Related Classification Detected Changes Specifications

Description

The SEAL Data Delivery Management Server (SDDM-S) is the server-side counterpart to the SDDM-C within the 3GPP SDDM framework. It embodies the role of a data producer or publisher. An SDDM-S is typically a network function or service enabler that generates or possesses data of value to other entities, such as location information, sensor readings, group status, or configuration updates. Its core function is to make this data available for subscription, manage the lifecycle of those subscriptions, and orchestrate the delivery of data to all authorized subscribing clients.

Architecturally, the SDDM-S hosts one or more data sets, each identifiable by a unique resource address. It exposes a service-based interface (e.g., Nsddm_DataPublication) that allows it to receive publication requests, either from its own internal logic or from an associated application. When new data is published, the SDDM-S processes it against its active subscription list. For each subscription, it evaluates if the new data matches the subscriber's filters and if the subscriber is authorized to receive it. Based on the subscription's delivery mode, the SDDM-S then either pushes a notification (or the data itself) to the subscriber's callback address or makes the data available for the subscriber to pull.

The SDDM-S works in close coordination with other SDDM management functions for tasks like subscription authorization, which may involve querying a unified data repository (UDR) for user profiles. It maintains subscription state, including subscriber identities, callback URLs, filter criteria, and expiration times. A key operational aspect is its ability to handle a large number of concurrent subscriptions efficiently and scale data publication events. Its role in the network is to be the authoritative source and distributor for specific data domains, providing a standardized, secure, and reliable point of access for client applications, thereby enabling the creation of rich, data-driven network services.

Purpose & Motivation

The SDDM-S was created to standardize the role of a data publisher in the 3GPP service layer. Historically, network functions that produced data (e.g., a location server, a presence server) exposed their data through vendor-specific interfaces, making it difficult for clients to integrate with multiple sources. The SDDM-S provides a common model for data exposure, subscription management, and delivery triggering.

It solves the problem of inconsistent data publishing mechanisms across different service enablers. By adhering to the SDDM-S specification, any data-producing function can seamlessly integrate into the broader SEAL data delivery ecosystem, instantly making its data discoverable and subscribable by any SDDM-C client. This promotes reuse and interoperability. The motivation stems from the need to treat data as a managed network resource, with controlled access, audit trails, and policy enforcement, rather than as an ad-hoc service feature.

Furthermore, the SDDM-S centralizes the logic for subscription management and delivery decisions. This offloads complexity from the client applications and from the core data-producing logic of the service enabler itself. It enables features like fan-out (one publication to many subscribers) and conditional delivery based on network policies or subscriber attributes, which are essential for efficient large-scale service deployments in areas like connected cars or massive IoT.

Classification

Part ofSDDM
Related approachesSDDM-C

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 1 change

In Release 17, the SDDM-S (SEAL Data Delivery Management Server) function was newly introduced as part of the SEAL (Service Enabler Architecture Layer) framework to enable data delivery management for vertical applications. This introduction is detailed in the new protocol specification TS 24.543, which defines the procedures and interfaces for the Data Delivery Management service. The SDDM-S function works in conjunction with other SEAL management servers, such as those for Configuration, Group, and Location Management, to provide a comprehensive service enabler layer.

  • SEAL terms in 24.538 aligned with 24.546 TS 24.538CR0021
Rel-18 16 changes

In Release 18, the SDDM-S (SEAL Data Delivery Management Server) function was enhanced to support bulk operations for constrained UEs, including procedures for bulk registration, de-registration, and configuration requests via the MSGin5G-6 interface. It also introduced new message delivery capabilities between different MSGin5G Servers and updated the general message delivery procedures, including specific flows for constrained devices. Furthermore, the release added formal CDDL specifications for key SDDM-S and SDDM-C APIs related to regular and URLLC transmission connections.

  • Add message delivery between different MSGin5G Servers TS 24.538CR0032
  • add new SEAL GMS capabilities TS 24.538CR0033
  • The behaviors of MSGin5G Server receiving bulk Registration Request TS 24.538CR0041
  • The behaviors of MSGin5G Server receiving bulk De-registration Request TS 24.538CR0051
  • update of clause 6.4.1.2.1 general procedure at MSGin5G Server TS 24.538CR0059
  • update of MSGin5G messages procedure at MSGin5G Server TS 24.538CR0060

+ 10 more changes

Rel-19 10 changes

In Release 19, the SDDM-S (SEAL Data Delivery Management Server) was enhanced with the new **Sdd_URLCCTransmissionConnection API** to support URLCC transmissions. The release also brought updates to the existing **Sdd_RegularTransmissionConnection API**, introduced refinements for **SDDM XR transmission connections**, and updated the **SEALDD server relocation procedure**. Additionally, the specifications for these APIs, including their CDDL and media types, were defined or corrected.

  • MSGin5G deferred delivery TS 24.538CR0136
  • Clarify the interaction between the SEAL Clients on constrained UEs and unconstrained UE TS 24.538CR0146
  • Clarify the behavior of the MSGin5G Server for deferred message TS 24.538CR0145
  • Introduction of Sdd_URLCCTransmissionConnection API provided by the SDDM-S TS 24.543CR0017
  • CDDL specification and Media types for the Sdd_URLCCTransmissionConnection API provided by the SDDM-S TS 24.543CR0032
  • Updates to the Sdd_RegularTransmissionConnection API provided by the SDDM-S TS 24.543CR0033

+ 4 more changes

Explore further

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

Defining Specifications

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

SpecificationTitleRelease
TS 24.538 vj30 MSGin5G Service Protocol Specification Rel-19
TS 24.543 vj50 SEAL Data Delivery Management Protocol Rel-19