Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Physical Layer

HARQ information

Hybrid Automatic Repeat Request Information

Physical Layer →

HARQ information is a set of control parameters (NDI, TB size, HARQ process ID, RV) accompanying a transport block to enable hybrid ARQ by indicating new data, retransmission combining, and the HARQ process.

Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
HARQ information Description Purpose What changed Neighbours Specifications

Description

HARQ information is the collection of control parameters that the MAC layer uses to operate the Hybrid Automatic Repeat Request (HARQ) protocol for a given transport block (TB). It is defined in 3GPP TS 36.321 (LTE) and TS 38.321 (NR) and is exchanged between the scheduler and the HARQ entity. Rather than being a single field, HARQ information is a structured set of parameters whose composition depends on the direction (downlink or uplink) and the type of transport channel (DL-SCH, UL-SCH, SL-SCH, SL-DCH).

For DL-SCH and UL-SCH transmissions, HARQ information always includes the New Data Indicator (NDI) and the Transport Block size. The NDI is a single-bit toggle that tells the receiver whether the received TB is a new transmission or a retransmission of a previously received TB; the UE compares the NDI to the value stored for the same HARQ process and, if it has been toggled, flushes the soft buffer and treats the data as new. The TB size is needed so the receiver knows how many bits to decode and how to interpret the soft buffer contents.

For DL-SCH transmissions, and for asynchronous UL HARQ and autonomous UL HARQ, the HARQ information additionally includes the HARQ process ID. The process ID identifies which of the parallel HARQ processes the transmission belongs to, allowing the receiver to associate the TB with the correct soft buffer and to combine retransmissions correctly. In asynchronous HARQ the retransmission timing is not fixed, so the explicit process ID is essential. The exception is NB-IoT UEs configured with a single HARQ process, where the process ID is redundant and therefore not signalled. For UL-SCH transmission, the HARQ information also includes the Redundancy Version (RV), which indicates which set of parity bits is transmitted in the current redundancy version and thus controls the incremental redundancy combining at the receiver.

When spatial multiplexing is used on DL-SCH, up to two transport blocks may be transmitted in the same subframe or slot. In that case the HARQ information comprises a set of NDI and TB size for each transport block, so that each codeword is tracked independently. For sidelink, HARQ information for SL-SCH and SL-DCH transmissions consists of TB size only, reflecting the simpler sidelink HARQ design where the NDI and process ID are not carried in the same way.

HARQ information is not transmitted as a single explicit field on the air interface; instead, it is derived by the UE from the DCI (downlink control information) or from higher-layer configuration. For example, the NDI and RV are carried in the DCI format, the HARQ process ID is either signalled in the DCI or derived from timing, and the TB size is computed from the MCS and resource allocation signalled in the DCI. The MAC layer assembles these parameters into the HARQ information set and passes it to the HARQ entity, which uses it to decide whether to perform soft combining, to flush the buffer, or to deliver the TB to the upper layers. This abstraction allows the HARQ operation to be described independently of the physical-layer signalling details.

Purpose & Motivation

HARQ information exists to make Hybrid ARQ work reliably and efficiently. HARQ combines forward error correction (FEC) with automatic repeat request (ARQ): the transmitter sends redundancy versions of a transport block, and the receiver soft-combines them across retransmissions. For this to work, the receiver must know several things: whether the current transmission is new or a retransmission (NDI), how large the TB is (TB size), which parallel HARQ process it belongs to (HARQ process ID), and which redundancy version is being sent (RV). Without this information, the receiver could not decide whether to flush its soft buffer, how to combine the received bits, or where to store them.

Before HARQ was standardised in LTE, earlier systems such as HSDPA already used HARQ, but the parameterisation was less flexible. The LTE design introduced multiple parallel HARQ processes (up to 8 in FDD) to keep the link busy while waiting for acknowledgements, which made the explicit HARQ process ID necessary for asynchronous operation. The NDI was introduced to allow implicit signalling of new data without a separate flag, and the RV allowed incremental redundancy to improve decoding gain on retransmissions.

Over time the definition was refined to cover new use cases: Rel-12 added sidelink HARQ information (TB size only), Rel-13 added asynchronous UL HARQ and the NB-IoT exception, and Rel-15 added autonomous UL HARQ for NR. These refinements reflect the growing diversity of 3GPP systems while keeping the core concept stable: a compact, well-defined set of parameters that lets the receiver operate HARQ correctly.

What changed in its specifications

The latest release-to-release comparison of specifications that define HARQ information. Each summary describes the whole specification, not only this term.

TS 36.321Rel-18 → Rel-19

Rel-19 adds to TS 36.321 a contention-based Msg3 early data transmission (CB-Msg3-EDT) procedure, along with new definitions and abbreviations. This is the only feature overview provided, so no other additions can be named.

Full comparison in TS 36.321 →
TS 38.321Rel-18 → Rel-19

Rel-19 adds sub-band full duplex handling to the NR Random Access procedure. It covers new second-PRACH-occasion RO type selection, power settings, Msg1 repetition, and RSRP threshold settings.

Full comparison in TS 38.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.

Rel-8 Initial

Initial definition: HARQ information consists of NDI and TB size; for DL-SCH it also includes HARQ process ID; for UL-SCH it also includes RV; with spatial multiplexing it comprises a set of NDI and TB size per transport block.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Wording changed: the definition was restructured to introduce 'HARQ information for DL-SCH or for UL-SCH transmissions' as the opening clause and to add a new sentence covering sidelink: 'HARQ information for SL-SCH and SL-DCH transmissions consists of TB size only.'

Wording changed: the HARQ process ID clause was extended to cover 'asynchronous UL HARQ' and an NB-IoT exception was added ('except for UEs in NB-IoT for which this information is not present').

Wording changed: the NB-IoT exception was refined to 'UEs in NB-IoT configured with a single HARQ process', clarifying that the process ID is omitted only when a single HARQ process is configured.

Wording changed: 'autonomous UL HARQ' was added alongside asynchronous UL HARQ as a case where the HARQ process ID is included.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-15.

Defining Specifications

3GPP specifications that define or reference HARQ information, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 36.321 vj30 E-UTRA MAC Protocol Specification Rel-19 read
TS 38.321 vj40 NR MAC Protocol Specification Rel-19 read