Glossary term · IoT

D2R

Device to Reader

IoT →

D2R is a 3GPP communication mode for IoT where a device transmits data directly to a specialized reader node, bypassing cellular base stations for efficient, low-power, localized data collection.

Introduced
Rel-19
Specifications
8 specs
Category
IoT
Introduced
Rel-19
Specifications
8 specs
D2R Description Purpose Related Classification Detected Changes Specifications

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

Part ofMTC

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-19 3 changes
  • Correction for D2R test configuration TS 38.191CR0011
  • (Ambient_IoT_Solutions)CR to TS38.191 for correcting D2R transmission Bandwidth TS 38.191CR0019
  • CR on D2R transmission time determination in TS 38.291 TS 38.291CR0003

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.

SpecificationTitleRelease
TS 33.369 vj30 Security and Privacy Aspects of AIoT Services in 5G System Rel-19
TS 38.191 vj30 Ambient IoT RF Characteristics Rel-19
TS 38.194 vj30 A-IoT BS and CW Node RF Requirements Rel-19
TS 38.291 vj30 Ambient IoT Physical Layer Rel-19
TS 38.300 vj30 NR and NG-RAN Overall Description Rel-19
TS 38.391 vj30 Medium Access Control (MAC) protocol of Ambient IoT Rel-19
TS 38.769 vk00 Ambient IoT Solutions in NR Rel-20
TS 38.870 vj50 Enhanced OTA Test Methods for NR TRP and TRS Rel-19