Description
PUR-RNTI (Preconfigured Uplink Resource Radio Network Temporary Identifier) is a specific type of RNTI introduced in 3GPP Release 16 for use with PUR-enabled UEs in LTE-M and NB-IoT systems. An RNTI is a temporary identifier assigned by the network to uniquely address a UE over the radio interface, and PUR-RNTI serves this purpose for operations related to Preconfigured Uplink Resources. When a UE is configured with PUR, the network may assign a PUR-RNTI to that UE, which is used to scramble and address downlink control information (DCI) on the Physical Downlink Control Channel (PDCCH) or messages on the Physical Downlink Shared Channel (PDSCH) specifically for PUR-related communications.
Architecturally, PUR-RNTI operates within the MAC and physical layers of the radio protocol stack. Upon PUR configuration via RRC signaling, the network can allocate a PUR-RNTI value, which is communicated to the UE as part of the configuration parameters. This identifier is typically used in scenarios where the UE transmits uplink data using its preconfigured resources, and the network needs to send a response, such as an acknowledgment (ACK/NACK) for the received data or a downlink data transmission. The UE monitors the PDCCH for DCI formats scrambled with its PUR-RNTI, allowing it to efficiently receive downlink signals without requiring additional identification procedures.
How it works in practice: When a UE performs a PUR-based uplink transmission, the network decodes the data and may generate a response. To deliver this response, the network uses the PUR-RNTI to address the UE directly. For example, if the network sends an ACK via a DCI format on PDCCH, it scrambles the cyclic redundancy check (CRC) of the DCI with the PUR-RNTI. The UE, knowing its assigned PUR-RNTI, descrambles the CRC and, if it matches, processes the DCI to obtain the acknowledgment or scheduling information. This avoids the need for broader identifiers like C-RNTI in connected state or P-RNTI for paging, streamlining the process and reducing control channel overhead. PUR-RNTI is designed to be UE-specific but may be reused or updated based on network policies, and it plays a key role in maintaining low-latency and energy-efficient communication for IoT devices.
Purpose & Motivation
PUR-RNTI was created to support the efficient downlink signaling required by the Preconfigured Uplink Resource (PUR) feature in IoT networks. Without a dedicated identifier, the network would have to rely on existing RNTIs like C-RNTI or P-RNTI for responses to PUR transmissions, which could incur additional signaling or state management overhead. PUR-RNTI provides a targeted mechanism for addressing UEs in idle or inactive states that are using PUR, enabling quick and resource-efficient acknowledgments or data delivery.
The motivation for introducing PUR-RNTI stems from the need to minimize control channel usage and UE power consumption in massive IoT deployments. In traditional LTE, downlink responses to uplink transmissions often require the UE to be in RRC Connected state with a C-RNTI, necessitating state transitions that consume energy and time. By using PUR-RNTI, the network can send downlink signals directly to a UE configured with PUR, even if the UE is in RRC Idle or Inactive, reducing the need for frequent state changes and associated signaling procedures.
This addresses limitations of previous approaches where IoT devices had to undergo full random access and connection setup for bidirectional communication, negating some benefits of PUR. PUR-RNTI enhances the overall PUR architecture by enabling a lightweight downlink path, supporting features like early data transmission and efficient small data communication. It aligns with 3GPP's evolution towards lean and scalable IoT solutions, ensuring that both uplink and downlink aspects are optimized for low-power, low-latency applications in 5G and beyond.
Key Features
- Unique identifier for PUR-enabled UEs
- Used to scramble downlink control information (DCI)
- Enables efficient acknowledgments for PUR transmissions
- Reduces control channel overhead
- Supports UE addressing in idle/inactive states
- Integrates with LTE-M and NB-IoT PUR procedures
Evolution Across Releases
Defining Specifications
| Specification | Title |
|---|---|
| TS 36.300 | 3GPP TR 36.300 |