Description
Preconfigured Uplink Resource (PUR) is a mechanism defined in 3GPP Release 16 and later, primarily for LTE-M and NB-IoT technologies, which allows a UE to transmit uplink data on pre-allocated resources without initiating a random access channel (RACH) procedure. This is achieved by the network configuring the UE with specific time-frequency resources (e.g., periodic subframes or resource blocks) during an RRC Connected state, which persist even when the UE transitions to RRC Idle or Inactive states. The UE can use these resources to send data directly, bypassing the typical steps of random access preamble transmission, RAR reception, and scheduling request, thereby streamlining the transmission process.
Architecturally, PUR involves coordination between the UE and the eNodeB (for LTE-M/NB-IoT) or gNodeB (for NR-IoT). The configuration is established via RRC signaling, such as through an RRCConnectionSetup or RRCConnectionReconfiguration message, which includes parameters like PUR periodicity, time offset, frequency location, modulation and coding scheme (MCS), and power control settings. These resources are typically allocated in a contention-free manner, meaning they are dedicated to a specific UE, though contention-based variants may also be supported. The network maintains awareness of the PUR allocations and listens on the designated resources, enabling immediate decoding of incoming transmissions without prior scheduling grants.
How PUR works operationally: When a UE has data to send, it checks if a valid PUR configuration is active and if the current time aligns with the preconfigured resource occasion. If so, it transmits the data directly using the assigned resources, employing configured parameters for power and modulation. The network, upon successful reception, may respond with an acknowledgment or downlink data without requiring the UE to re-enter RRC Connected state fully. This reduces signaling overhead and latency, which is particularly beneficial for sporadic small data packets typical in IoT sensors. PUR configurations can be validated periodically through dedicated procedures to ensure synchronization, and they may be released or updated based on UE mobility or network conditions.
Purpose & Motivation
PUR was created to address the inefficiencies of traditional random access and scheduling request procedures for IoT devices, which often transmit small, infrequent data packets. In pre-Release 16 LTE-M and NB-IoT, each uplink transmission required a RACH procedure, involving multiple message exchanges that consumed significant energy and added latency. This was suboptimal for massive Machine-Type Communication (mMTC) use cases, such as smart meters or environmental sensors, where devices are battery-constrained and need to operate for years without recharging.
The motivation for PUR stems from the need to enhance power saving and reduce signaling overhead in IoT networks. By eliminating the RACH process for preconfigured transmissions, PUR minimizes the time the UE's radio is active, thereby extending battery life. It also reduces network congestion caused by frequent random access attempts from millions of devices, improving scalability for massive IoT deployments. This aligns with 3GPP's goals for 5G evolution, supporting ultra-lean design and efficient support for diverse IoT applications.
Historically, earlier solutions like Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX) helped with energy efficiency but did not optimize the transmission phase itself. PUR complements these by streamlining uplink communication. It addresses limitations of previous approaches where latency and power consumption were trade-offs; PUR enables low-latency transmissions without sacrificing energy efficiency, making it a key enabler for critical IoT services and industrial automation within the 5G framework.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the PUR (Preconfigured Uplink Resource) function was enhanced with specific technical clarifications and corrections. These included the introduction of a dedicated PUR RNTI for identification, refinements to the MAC layer procedures, and detailed validations for Timing Advance (TA). The release also corrected configuration parameters such as the `pur-ResponseWindowTimer` and defined the use of PUR in conjunction with the AS security context reactivation procedure during resume.
- Addition of PUR RNTI in E-UTRA related UE identities TS 36.300CR1297
- MAC corrections for PUR TS 36.321CR1503
- Clarification on TA validation for PUR TS 36.321CR1518
- MAC clarifications for PUR TS 36.321CR1524
- Correction to pur-ResponseWindowTimer and removal of pur-ResponseWindowSize TS 36.321CR1534
- TA timer corrections for PUR TS 36.331CR4448
+ 3 more changes
In Release 18, the PUR (Preconfigured Uplink Resource) function was updated with a correction to an MPDCCH parameter within the PUR-Configuration. This release also reinforced that the UE and ng-eNB may use the PUR feature as part of the procedure to store and reactivate the AS security context during suspend and resume, as defined alongside EDT.
- Correction on MPDCCH parameter in PUR-Config TS 36.331CR5087
Explore further
Broader topics and technologies where PUR plays a role.
Defining Specifications
3GPP specifications that define or reference PUR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 |
| TS 36.306 vj00 | E-UTRA UE Radio Access Capability Parameters | Rel-19 |
| TS 36.321 vj00 | E-UTRA MAC Protocol Specification | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 |