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.
Key Features
- Hosts and publishes identifiable data sets for client subscription
- Manages the lifecycle of client subscriptions (creation, modification, deletion)
- Authorizes subscription requests against network policies and user profiles
- Triggers data delivery to subscribers upon new data publication
- Supports configurable data filtering for subscriptions
- Exposes standardized service-based interfaces for publication and subscription management
Evolution Across Releases
Introduced the SDDM-S as the foundational server entity. Defined its procedures for accepting data publications, managing subscription resources, and initiating data delivery to clients. Established the required service-based interfaces (e.g., Nsddm_DataPublication, Nsddm_SubscriptionManagement) that the server must implement.
Defining Specifications
| Specification | Title |
|---|---|
| TS 24.538 | 3GPP TS 24.538 |
| TS 24.543 | 3GPP TS 24.543 |