Description
The Inactive Process is a concept defined in 3GPP specifications 25.319 and 25.321 for the UMTS Terrestrial Radio Access Network (UTRAN). It refers to a Hybrid Automatic Repeat Request (HARQ) process for which Scheduling Grants are not applicable, meaning that scheduled data cannot be sent on that process. In the uplink of HSPA (High Speed Packet Access), the UE maintains multiple parallel HARQ processes to enable continuous transmission while acknowledgements are pending. However, not all processes are allowed to transmit at any given time; the network controls the UE's transmission through Scheduling Grants, which assign resources. A process that has no valid grant is considered inactive and must not transmit new data.
The concept is tightly coupled with the uplink scheduling mechanism in HSPA. The NodeB scheduler issues grants that map to specific HARQ processes, and the UE is only permitted to send data on processes that have been granted resources. Inactive processes remain idle until a grant is received. This mechanism allows the network to manage interference and allocate resources efficiently among multiple users. The UE maintains a state for each HARQ process, and the transition between active and inactive states is governed by the reception of grants and the HARQ feedback (ACK/NACK).
In the MAC layer, the UE's HARQ entity manages the processes. When a grant is received, the corresponding process becomes active and can transmit a transport block. After transmission, the process awaits feedback; if a NACK is received, retransmission is required, but the process may still be considered active if the grant remains valid. The inactive state is explicitly defined to prevent transmission without authorization, which could cause collisions and degrade network performance. The specifications 25.321 (MAC protocol) and 25.319 (RRC protocol) detail the procedures for grant handling and process activation.
The Inactive Process concept is fundamental to the distributed scheduling architecture of HSPA, where the NodeB makes fast scheduling decisions. It enables the network to control the UE's transmission on a per-TTI basis, ensuring that only authorized processes transmit. This is particularly important in the uplink, where multiple UEs share the same frequency and interference must be carefully managed. By marking processes as inactive, the network can effectively mute certain transmissions without explicit signaling, relying on the absence of grants.
Over the releases, the definition has remained unchanged, indicating the stability of the concept. However, the surrounding procedures have evolved with features like Enhanced Uplink (HSUPA) and dual-cell operation, where multiple carriers and processes are managed. The inactive process concept continues to be relevant in these enhancements, ensuring that scheduling grants are respected across all configured carriers and processes.
Purpose & Motivation
The Inactive Process concept exists to enforce network-controlled uplink transmission in HSPA. Without it, UEs could transmit autonomously, leading to excessive interference and inefficient resource utilization. By defining processes as inactive when no grant applies, the network retains tight control over when and how UEs access the shared uplink channel. This is essential for maintaining QoS and fairness among users.
Historically, before HSPA, uplink transmission in UMTS was based on dedicated channels with fixed allocations, which were inefficient for bursty traffic. HSPA introduced shared channels and fast scheduling, requiring a mechanism to dynamically assign resources. The HARQ process with grant-based activation provided a way to combine fast retransmissions with flexible scheduling. The inactive process concept emerged as part of this evolution, allowing the NodeB to quickly activate or deactivate processes based on load and channel conditions.
The concept also addresses the need for reliable data transfer. HARQ processes that are inactive do not transmit, avoiding unnecessary retransmissions and conserving UE battery power. It simplifies the UE implementation by clearly defining when a process can send data, reducing ambiguity in scheduling. Overall, the inactive process is a building block of the HSPA uplink scheduling framework, enabling efficient and controlled utilization of radio resources.
What changed in its specifications
The latest release-to-release comparison of specifications that define Inactive Process. Each summary describes the whole specification, not only this term.
Added two E-DCH interference mitigation sub-features: radio links without DPCH/F-DPCH and serving E-DCH cell decoupling. Also added Implicit Grant handling for Secondary Serving E-DCH cells.
Full comparison in TS 25.319 →Rel-16 brings only minor changes to TS 25.321: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 25.321 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced in 3GPP Rel-8 specifications 25.319 and 25.321. The concept was established as part of HSPA uplink enhancements, defining an inactive process as a HARQ process for which Scheduling Grants are not applicable, thereby preventing scheduled data transmission.
Defining Specifications
3GPP specifications that define or reference Inactive Process, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 25.319 vj00 | Enhanced Uplink for UTRA FDD/TDD | Rel-19 read |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 read |