DAI

Downlink Assignment Index

Physical Layer →
Introduced in Rel-8

DAI is a counter field in LTE and NR downlink control information that indicates the cumulative number of downlink assignments to help a UE detect missed grants and maintain accurate HARQ-ACK feedback.

Category
Physical Layer
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
6 specs
DAI Description Purpose Related Classification Detected Changes Specifications

Description

The Downlink Assignment Index (DAI) is a fundamental mechanism in 3GPP LTE and NR specifications that addresses the challenge of missed downlink control information detection in HARQ-ACK feedback procedures. In the physical layer control channel structure, DAI is embedded within Downlink Control Information (DCI) formats that schedule Physical Downlink Shared Channel (PDSCH) transmissions. This counter field specifically operates in scenarios requiring multi-subframe or multi-slot feedback, most notably in Time Division Duplex (TDD) configurations where multiple downlink assignments can be acknowledged in a single uplink subframe.

Architecturally, DAI functions within the UE's physical layer processing chain, specifically in the HARQ-ACK generation module. When a UE receives a DCI containing a DAI value, it interprets this as an indicator of how many downlink assignments have been transmitted up to that point within a specific bundling window. The UE maintains an internal counter that tracks received DAI values, allowing it to detect discrepancies that indicate missed DCIs. This detection capability is crucial because missed scheduling assignments would otherwise lead to incorrect HARQ-ACK feedback, potentially causing unnecessary retransmissions or protocol failures.

The technical implementation varies between LTE and NR, but follows similar principles. In LTE, DAI is typically 2 bits for TDD configurations, counting modulo-4 within the bundling window. In NR, the mechanism is more sophisticated with both counter-DAI and total-DAI fields in some DCI formats, providing enhanced reliability for multi-PDSCH scheduling scenarios. The UE's HARQ-ACK codebook construction directly depends on correctly interpreting DAI values to determine which HARQ-ACK bits to include and their proper ordering in the feedback payload.

DAI's role extends beyond simple error detection to enabling efficient spectrum utilization. By allowing accurate HARQ-ACK feedback even when some DCIs are missed, it prevents the radio link control (RLC) layer from triggering unnecessary retransmissions for correctly received data. This optimization is particularly valuable in TDD systems with asymmetric downlink/uplink ratios, where the feedback opportunity is limited relative to the number of potential downlink transmissions. The mechanism thus contributes directly to system throughput and latency performance in real network deployments.

Purpose & Motivation

DAI was introduced to solve a fundamental problem in HARQ-ACK feedback reliability: when a UE misses a downlink assignment (DCI), it cannot generate correct HARQ-ACK feedback for the corresponding PDSCH transmission. Before DAI implementation, missed DCIs would cause the UE to construct an incomplete HARQ-ACK codebook, leading to misalignment between the UE's feedback and the gNB's expectations. This misalignment could cause several issues: unnecessary retransmissions of correctly received data (wasting radio resources), failure to retransmit incorrectly received data (reducing reliability), and potential protocol timeouts or radio link failures.

The historical context for DAI's creation lies in the evolution from Frequency Division Duplex (FDD) to more complex Time Division Duplex (TDD) deployments in LTE. In FDD systems, HARQ-ACK timing is fixed and predictable, with each downlink transmission having a dedicated uplink feedback opportunity. However, TDD configurations with asymmetric downlink/uplink ratios (such as configuration 2 with more downlink than uplink subframes) required bundling multiple downlink HARQ-ACK responses into a single uplink subframe. This bundling created the possibility that a UE might miss some DCIs while receiving others, without any mechanism to detect these misses.

DAI addressed these limitations by providing explicit signaling that allows the UE to detect missing assignments and construct the HARQ-ACK codebook accordingly. The solution was particularly motivated by the need to support efficient TDD operation in LTE Release 8, where spectrum flexibility was a key requirement. By enabling reliable HARQ-ACK feedback in challenging radio conditions where control channel reception might be imperfect, DAI contributed to the overall robustness of the LTE system and paved the way for even more flexible scheduling mechanisms in subsequent NR specifications.

Classification

Part ofDCI
Related approachesHARQTDD

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 2 changes

In Release 16, the specification introduced clarifications and corrections for the Downlink Assignment Index (DAI) function. This included defining the DAI size determination for DCI formats 1_1 and 1_2 when operating with Carrier Aggregation (CA). Additionally, a correction was made regarding the value mapping for the 1-bit counter DAI field.

  • 38.212 CR on DAI size determination for DCI format 1_1/1-2 in CA TS 38.212CR0066
  • Correction on value of 1-bit counter DAI TS 38.213CR0243
Rel-17 1 change

In Release 17, a change was introduced to the Downlink Assignment Index (DAI) function regarding its counting procedure. This change specifically addresses the scenario when a DCI format uses the 'dci-enabler' field to indicate a value of 0. The update defines how the DAI is to be counted in this particular case.

  • CR on DAI counting for 'dci-enabler' in DCI indicating value 0 TS 38.213CR0390

Explore further

Broader topics and technologies where DAI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.131 vj00 Terminal Acoustic Performance Requirements Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.