Description
Device to Reader (D2R) is a novel communication paradigm standardized in 3GPP Release 19, primarily documented across specifications like 33.369 (security), 38.191/194/291/300/391 (NR aspects), and 38.769/870 (IoT enhancements). It defines a direct link between an IoT device (often a simple, battery-constrained sensor or tag) and a Reader node. The Reader is a specialized network entity, distinct from a conventional gNB, optimized for aggregating data from a potentially massive number of nearby devices. Architecturally, D2R operates within the broader NR (New Radio) and RedCap (Reduced Capability) frameworks, but it introduces a new point-to-multipoint topology where the Reader acts as a centralized data collector.
The D2R link is designed for uplink-centric, sporadic, and small data transmissions. The device (D2R Device) initiates communication by sending its data directly to the Reader using defined physical channels and procedures. The Reader, which has enhanced reception capabilities compared to a standard device, manages the access of multiple devices, potentially using contention-based or grant-free access schemes to minimize signaling overhead and device energy consumption. Key components include the D2R Device (with simplified protocol stack), the D2R Reader (with aggregation and possibly relay functions), and the supporting network functions for authentication, security, and data forwarding defined in core network specs.
From a protocol perspective, D2R involves modifications to the NR physical layer (waveforms, reference signals), MAC layer for efficient random access and scheduling, and RRC for limited configuration. Security mechanisms are tailored for lightweight device authentication and data integrity between the device and Reader. The Reader typically has a backhaul connection (e.g., to 5GC) to forward the collected data. D2R's role is to enable ultra-efficient, scalable, and localized data harvesting for applications like industrial sensor networks, smart agriculture, and environmental monitoring, where devices are simple and data destinations are well-defined collectors rather than arbitrary endpoints.
Purpose & Motivation
D2R was created to address the specific challenges of massive-scale, low-complexity IoT deployments that were not optimally served by existing 3GPP cellular paradigms like LTE-M or NB-IoT. While these technologies excel at providing wide-area coverage, they still require devices to establish full cellular links with base stations, involving significant control signaling and device complexity for scenarios where data only needs to reach a nearby aggregation point. The limitations of previous approaches included unnecessary power consumption for cell search, synchronization, and mobility management in static sensor fields, and network congestion from many devices connecting to macro cells.
The historical context is the growing need for 'sensor-to-cloud' or 'thing-to-gateway' communication in Industry 4.0 and smart city applications. D2R is motivated by the desire to create a 3GPP-standardized, efficient alternative to proprietary short-range technologies (like RFID readers) that offers better integration with 5G core networks, improved security, and guaranteed QoS. It solves the problem of connecting billions of ultra-simple, cost- and energy-constrained devices by minimizing protocol complexity and enabling very localized, high-density communication cells managed by Readers, thus offloading traffic from the macro RAN and core network.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the D2R (Device to Reader) function was newly introduced to enable secure Ambient IoT (AIoT) services, specifically defining security procedures for inventory and command use cases. It specifies mechanisms for network-layer authentication between the AIoT device and the 5G core, including the generation of a pseudo-random number (RAND_AIOT_d) and the calculation of a response (RES_AIOT) for authentication. Furthermore, it mandates integrity protection for command messages and supports confidentiality protection using defined ciphering algorithms for secure D2R communication.
- Running CR to 38300 for Multi-USIM devices support TS 38.300CR0422
In Release 18, the new D2R (Device to Reader) function for Ambient IoT introduced specific security procedures for device authentication and protected command communication. This included defining an authentication procedure where the device generates a response to a network paging challenge and establishes keys for securing NAS messages with the AIOTF. The release also specified requirements for confidentiality and integrity protection of these command messages, using algorithms like 128-NEA2 and 128-NIA2.
- Introduction of In-Device Co-existence (IDC) enhancements for NR TS 38.300CR0680
In Release 19, the D2R (Device to Reader) function saw specific technical refinements, including a correction to the D2R test configuration and a detailed definition of the D2R transmission time determination procedure within the specifications. These updates provided clearer implementation guidelines for the security and timing of the D2R message, which carries the AIoT NAS message containing authentication responses like RES_AIOT and RAND_AIOT_d from the AIoT device to the NG-RAN.
- CR to TR 38.870 for an alternate TRP test procedure for XR devices TS 38.870CR0019
- CR for TS 38.191, Correction on A-IoT Device Symbol TS 38.191CR0001
- CR for TS 38.191, Correction on A-IoT Device Output RF spectrum emissions TS 38.191CR0002
- Corrections for device RF requirements TS 38.191CR0006
- CR on 38.191 for A-IoT device testing TS 38.191CR0003
- Correction for D2R test configuration TS 38.191CR0011
+ 1 more changes
In Release 20, the D2R (Device to Reader) function was enhanced for Ambient IoT active devices in outdoor NR scenarios, introducing new security procedures and message flows. Key additions include a defined authentication procedure where the device generates a response (RES_AIOT) to a network paging challenge and sends it within an AIOT NAS message via D2R. Furthermore, the release specified command protection for AIoT NAS messages, mandating integrity protection and supporting confidentiality with algorithms like 128-NEA2 and 128-NIA2.
Explore further
Broader topics and technologies where D2R plays a role.
Defining Specifications
3GPP specifications that define or reference D2R, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.369 vj00 | Security for AIoT in Isolated Private 5G Networks | Rel-19 |
| TS 38.191 vj00 | NR Ambient IoT RF Characteristics | Rel-19 |
| TS 38.194 vj00 | Ambient IoT Base Station RF Spec | Rel-19 |
| TS 38.291 vj20 | Ambient IoT Physical Layer Specification | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.391 vj00 | NR; Ambient IoT MAC Protocol Spec | Rel-19 |
| TS 38.769 vk00 | Ambient IoT Solutions in NR | Rel-20 |
| TS 38.870 vj20 | Enhanced OTA Test Methods for NR FR1 TRP/TRS | Rel-19 |