Reliable Data Service

Description

Reliable Data Service (RDS) is a service layer capability standardized by 3GPP to meet stringent reliability requirements for data transmission, especially for mission-critical and industrial Internet of Things (IoT) communications. It operates above the transport layer, providing an assurance that application data is delivered successfully from a source to a target destination. The service is designed to function over various underlying transport protocols, including both IP-based and non-IP data delivery (NIDD) mechanisms, making it adaptable to diverse IoT device capabilities and network architectures.

Architecturally, RDS is implemented within the 3GPP Core Network, specifically involving the Service Capability Exposure Function (SCEF) for Non-IP Data Delivery (NIDD) and the User Plane Function (UPF) for IP-based delivery. The service introduces the concept of a Reliable Data Server (RDS), which acts as an endpoint for the reliable service. For NIDD, the SCEF interfaces with the RDS server, while for IP, the UPF may apply specific packet handling. The service utilizes mechanisms such as end-to-end acknowledgments, retransmissions, and potentially packet duplication over multiple paths to achieve its reliability targets, which can be configured per service request.

The service works by establishing a reliable data session context between the requesting entity (e.g., an Application Server (AS) or a User Equipment (UE)) and the RDS server. The requesting entity specifies the required reliability level and other service parameters. During data transfer, the RDS mechanisms monitor delivery success. If an acknowledgment is not received within a specified time, retransmissions are triggered. The service also manages session state, including buffering of data if the UE is unreachable, and provides delivery reports back to the originator. Its role is crucial for applications where data loss is unacceptable, such as remote control of industrial machinery, smart grid protection commands, or vital health telemetry, ensuring the 5G system can support Ultra-Reliable Low-Latency Communication (URLLC) service commitments.

Purpose & Motivation

RDS was created to address the gap in standardized, network-assisted reliable data delivery for critical machine-type communication (MTC) and IoT services. Prior to its introduction, applications requiring high reliability had to implement complex, proprietary end-to-end protocols on top of the best-effort IP service provided by mobile networks. This was inefficient, increased device complexity and power consumption, and could not leverage network intelligence for optimization.

The motivation stemmed from the industry's push towards Industrial IoT (IIoT) and automation, where control commands and sensor data must be delivered with near-perfect certainty. 3GPP's work on Cellular IoT (CIoT) and Critical Communications identified reliability as a key service requirement that the network itself should natively support. RDS provides a standardized, network-agnostic interface for applications to request and obtain guaranteed data delivery, simplifying application development and enabling consistent service quality across different operator networks and device types. It is a key enabler for 5G's vertical industry ambitions, providing a foundational service for URLLC use cases.

Key Features

• Configurable end-to-end reliability levels for data transfer
• Support for both IP and Non-IP Data Delivery (NIDD) transport
• Mechanisms for delivery acknowledgments and retransmissions
• Session management with state maintenance for unreachable devices
• Delivery reporting and status notification to the service requester
• Integration with Core Network functions like SCEF and UPF

Evolution Across Releases

Defining Specifications