Description
Redundancy Version (RV) is a fundamental parameter in Hybrid Automatic Repeat Request (HARQ) processes used in 3GPP wireless technologies like UMTS, LTE, and 5G NR. It specifies which part of a turbo-encoded or LDPC-encoded codeword is selected for transmission during a given HARQ attempt, allowing for incremental redundancy (IR) strategies that enhance decoding success. When data is initially encoded for transmission, it generates a set of systematic bits (the original data) and parity bits (error-correcting redundancy). RV controls the starting point and pattern within this encoded sequence that is actually transmitted, with different RVs corresponding to different subsets of bits, such as primarily systematic bits in one transmission and additional parity bits in retransmissions.
In operation, the transmitter selects an RV index (e.g., 0, 1, 2, 3 in LTE) for each HARQ transmission, which dictates the bit selection according to a predefined circular buffer model. The receiver combines soft bits from multiple transmissions, leveraging the complementary information from different RVs to progressively build a more complete version of the codeword. This combining occurs in the HARQ soft buffer, where log-likelihood ratios (LLRs) are accumulated, improving the probability of successful decoding with each retransmission. Key components include the HARQ entity, which manages RV selection, and the rate matching function, which applies the RV to generate the transmit sequence.
RV plays a critical role in adapting to varying channel conditions and optimizing spectral efficiency. By transmitting different redundancy versions, the system can achieve a form of time diversity and coding gain without requiring additional bandwidth. In LTE, four RVs are typically defined, while 5G NR extends this with more flexible RV configurations to support diverse use cases, including ultra-reliable low-latency communication (URLLC). The choice of RV sequence can be predefined or dynamically adjusted based on channel state information, impacting performance metrics like block error rate (BLER) and throughput. Overall, RV is essential for robust data delivery in mobile networks, enabling efficient error recovery and enhancing link adaptation.
Purpose & Motivation
RV was introduced to improve the efficiency of error correction in wireless communications, where traditional ARQ methods simply retransmitted the same data, wasting bandwidth and offering limited gains in poor channel conditions. Early systems like GSM used basic retransmissions, but as data rates increased with 3G UMTS, there was a need for more sophisticated techniques to combat errors without excessive redundancy. HARQ with incremental redundancy, enabled by RV, addressed this by allowing retransmissions to send different encoded bits, providing additional coding gain when combined at the receiver.
First standardized in 3GPP Release 5 for HSDPA in UMTS, RV was motivated by the demand for higher throughput and reliability in packet-switched services. It solves the problem of inefficient retransmissions by enabling the receiver to accumulate information across attempts, effectively creating a stronger error-correcting code over time. This approach reduces the need for excessive initial redundancy, optimizing spectral efficiency and supporting the evolution towards high-speed mobile broadband in LTE and 5G, where adaptive modulation and coding are paramount.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, the RV (Remote Vehicle) function was newly introduced to support V2V (Vehicle-to-Vehicle) safety applications like FCW (Forward Collision Warning) and CLW (Control Loss Warning). The RV is defined as a vehicle that periodically broadcasts its kinematic state and, for specific events, can broadcast self-determined information like control loss, in-lane status, and time-to-collision using the V2V Service.
- Version for Release 15 TS 26.267
In Release 16, the standardization of the Redundancy Version (RV) function was explicitly extended to support new V2X safety applications like Forward Collision Warning (FCW) and Control Loss Warning (CLW). This enabled the RV to periodically broadcast its kinematic state and, for CLW, to additionally broadcast self-determined control loss events. These enhancements integrated the RV's role into defined service flows for collision avoidance within the V2V service.
- Update to Rel-16 version (MCC) TS 26.267
In Release 17, the update for the Redundancy Version (RV) function was primarily an administrative version alignment to reflect the completion of the Release 17 work item. The change involved updating the normative references within the specification to point to the finalized Release 17 versions of all referenced 3GPP documents, ensuring consistency across the standard. No new technical procedures or capabilities specific to the RV's role in V2V services, such as in-lane determination or event broadcasting, were introduced in this particular maintenance update.
- Update to Rel-17 version (MCC) TS 26.267
In Release 18, the primary update for the RV (Redundancy Version) function was to update the specification to its finalized Rel-18 version, as indicated by the Change Request. This administrative update ensured the document references and provisions were aligned with the completed release, without introducing new technical procedures or capabilities specific to the RV's role in V2V services like Forward Collision Warning or Control Loss Warning.
- Update to Rel-18 version (MCC) TS 26.267
In Release 19, the update for the "RV" (Remote Vehicle) function specifically enhanced the Forward Collision Warning (FCW) and Control Loss Warning (CLW) applications within the V2V Service. The modifications refined the service flows where the RV periodically broadcasts its dynamic state, including location, speed, acceleration, and an optional estimated trajectory, and now explicitly performs in-lane and time-to-collision determinations for inclusion in these messages. These updates standardized the RV's role in both generating event-driven warnings for control loss and enabling the Host Vehicle (HV) to assess collision risk more effectively.
- Update to Rel-19 version (MCC) TS 26.267
Explore further
Broader topics and technologies where RV plays a role.
Defining Specifications
3GPP specifications that define or reference RV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.885 ve00 | LTE support for V2X services | Rel-14 |
| TS 25.212 vj00 | UTRA FDD Layer 1 Multiplexing & Channel Coding | Rel-19 |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 |
| TS 25.705 vd00 | UMTS Small Data Transmission Enhancements Study | Rel-13 |
| TS 25.766 vd10 | Network-Assisted Interference Cancellation for UMTS | Rel-13 |
| TS 26.267 vj00 | eCall In-band Modem Specification | Rel-19 |
| TS 38.104 vj20 | NR Base Station RF Requirements | Rel-19 |
| TS 38.141 vj20 | NR Base Station RF Conformance Testing Part 1 | Rel-19 |
| TR 38.845 vh00 | NR Positioning Use Cases Study | Rel-17 |