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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (45 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Preconfigured Uplink Resource (PUR) function was not explicitly introduced or detailed within the provided grounding context or the associated list of Change Request titles. The context focuses on security context parameters like the uplink NAS COUNT for key derivation and procedures such as the NAS Security Mode Command, while the titles primarily address corrections and clarifications for other resource types like SPS, sidelink, and NPRACH. Therefore, based solely on the given materials, no specific technical details for a new PUR function in Release 15 can be described.
- E-UTRA - NR Cell Resource Coordination TS 36.300CR1122
- uplink NAS Count for Kasme derivation in idle mode mobility to EPS TS 33.501CR0616
- Corrections on resource coordination in stage-2 TS 36.300CR1190
- 36.300 CR on Correction of Physical Layer Resource to Cell Resource TS 36.300CR1211
- Clear SPS resources for Scell TS 36.321CR1428
- CR on PDCP duplication related operations in sidelink LCP procedure and resource reselection procedure TS 36.321CR1432
+ 14 more changes
In Release 16, the enhancements for Preconfigured Uplink Resource (PUR) included the introduction of a carrier-specific NRSRP threshold for NPRACH resource selection and the addition of a dedicated PUR RNTI to the set of E-UTRA related UE identities. The release also provided clarifications and corrections for key procedures, including TA validation, MAC operation, and the configuration of the `pur-ResponseWindowTimer`.
- Resource Level Authorization using Access Tokens TS 33.501CR0755
- Addition of PUR RNTI in E-UTRA related UE identities TS 36.300CR1297
- Introduction of carrier specific NRSRP thresholds for NPRACH resource selection TS 36.306CR1844
- MAC corrections for PUR TS 36.321CR1503
- Clarification on TA validation for PUR TS 36.321CR1518
- MAC clarifications for PUR TS 36.321CR1524
+ 10 more changes
In Release 17, the enhancements for Preconfigured Uplink Resource (PUR) included the introduction of uplink RRC segmentation capability to improve data transmission efficiency. Furthermore, corrections were made to ensure the correct uplink NAS COUNT value is used for the derivation of security keys, such as KgNB/KeNB, from a mapped 5G security context.
- Introduction of uplink RRC Segmentation capability TS 36.306CR1853
- Introduction of uplink RRC Segmentation capability TS 36.331CR4826
- RACH optimisation in EN-DC secondary cell TS 36.300CR1366
- Introduction of new attributes "Resource Coordination Only" in ANR TS 36.300CR1390
- Correct NAS uplink COUNT for KgNB/KeNB derivation TS 33.501CR1075
- Correct current uplink EPS NAS COUNT used at derivation of a mapped 5G security context TS 33.501CR1076
In Release 18, a correction was made to the MPDCCH parameter within the PUR-Config information element. This update ensures the accurate configuration of the MPDCCH, which is used for scheduling and control signaling, as part of the Preconfigured Uplink Resource (PUR) function's parameters.
- Correction on MPDCCH parameter in PUR-Config TS 36.331CR5087
In Release 19, the enhancements for Preconfigured Uplink Resource (PUR) focused on corrections for specific deployment scenarios. The updates included a correction to the Semi-Persistent Scheduling (SPS) and preallocated uplink grant procedures for Time Division Duplex (TDD) operation. Additionally, corrections were made to define the valid uplink subframes for IoT applications over Non-Terrestrial Networks (NTN) using TDD.
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 |