Acknowledgement

Description

ACK (Acknowledgement) is a fundamental control signal within 3GPP's Hybrid Automatic Repeat Request (HARQ) framework, operating primarily at the physical layer. In the context of downlink transmission, when a User Equipment (UE) successfully decodes a Transport Block (TB) received via the Physical Downlink Shared Channel (PDSCH), it transmits an ACK on the Physical Uplink Control Channel (PUCCH) or, in some configurations, the Physical Uplink Shared Channel (PUSCH). This signal informs the gNB (in 5G) or eNB (in LTE) that the data was received correctly, allowing the transmitter to proceed with the next scheduled data packet. The timing relationship between the PDSCH reception and the corresponding ACK/NACK transmission is strictly defined by the HARQ timeline, which varies based on the numerology and duplex mode (FDD or TDD).

The generation of an ACK involves multiple layers. At the Medium Access Control (MAC) layer, successful cyclic redundancy check (CRC) verification of the decoded TB triggers the generation of a positive acknowledgement. This MAC-layer indication is then passed to the physical layer, which formats it for transmission. In scenarios involving multiple codewords (e.g., using MIMO), multiple ACK bits may be generated and bundled or multiplexed. The physical layer maps these ACK bits to specific resource elements within a PUCCH format (e.g., Format 1, 2, 3, or 4 in LTE; various formats in NR) or embeds them within uplink shared channel data. The chosen format depends on factors like the number of simultaneous ACK/NACK bits, simultaneous CSI reporting, and whether simultaneous PUCCH and PUSCH transmission is configured.

The role of ACK extends beyond simple confirmation; it is integral to the stop-and-wait nature of HARQ processes. Each HARQ process maintains a buffer and a state. Upon receiving an ACK, the process can flush its buffer for that specific TB and make the process available for new data. The network schedules transmissions based on ACK/NACK feedback, directly impacting throughput and latency. In advanced implementations like LTE-Advanced and 5G NR, features such as spatial bundling (for multiple component carriers in Carrier Aggregation) and enhanced feedback with more bits (to support increased number of TBs or codeblocks) have been introduced. The reliability of the ACK signal itself is paramount, as a missed or falsely interpreted ACK can lead to unnecessary retransmissions or packet loss, degrading system performance. Therefore, the physical channel carrying the ACK is designed with sufficient robustness, often using techniques like sequence selection or resource coding.

In the broader system architecture, ACK feedback is a key component of the link adaptation loop. While Channel Quality Indicator (CQI) reports provide long-term channel state information, the pattern of ACKs and NACKs provides immediate feedback on the success of the chosen Modulation and Coding Scheme (MCS). A persistent stream of NACKs may prompt the scheduler to choose a more robust MCS. Furthermore, in multi-user MIMO (MU-MIMO) scenarios, accurate ACK/NACK feedback is critical for managing interference between layers intended for different users. The efficient design of ACK signaling, including its overhead, latency, and reliability, is therefore a critical consideration in the air interface design of all 3GPP systems from LTE onwards.

Purpose & Motivation

The primary purpose of the ACK signal is to enable reliable data transmission over inherently unreliable and time-varying wireless radio channels. Before the widespread adoption of HARQ with ACK/NACK feedback in 3GPP systems (fully realized in LTE), error control relied more heavily on forward error correction (FEC) and higher-layer ARQ protocols like the Radio Link Control (RLC) Acknowledged Mode. While effective, these approaches had limitations: FEC alone requires excessive redundancy for poor channel conditions, wasting bandwidth, while RLC ARQ introduces significant latency due to its operation at a higher protocol layer with larger round-trip times.

HARQ, with its ACK/NACK mechanism at the physical/MAC layer, was introduced to solve these problems. It provides rapid feedback on a per-transmission-time-interval (TTI) basis, allowing for much faster retransmissions (on the order of milliseconds). This tight integration of FEC (through turbo or LDPC codes) and ARQ (through the ACK/NACK loop) creates a powerful adaptive system. The ACK specifically informs the transmitter of success, allowing it to stop retransmitting a given packet and efficiently utilize radio resources for new data or other users. This directly increases spectral efficiency and user throughput while reducing latency for packet data services, which was a core requirement for the 3GPP Long Term Evolution (LTE) project targeting a high-performance, all-IP packet-switched network.

Furthermore, the ACK mechanism enables more advanced features. It is the foundational feedback that makes incremental redundancy (IR) HARQ—where retransmissions send different coded bits—effective. The knowledge that a previous transmission was not acknowledged (implicitly via a NACK or lack of feedback) allows the receiver to combine soft bits from multiple transmission attempts, significantly improving decoding success in fading channels. Thus, the ACK is not merely a confirmation signal but a critical enabler for the sophisticated, adaptive, and efficient link-level protocols that define modern cellular data systems.

Key Features

• Positive feedback signal within the HARQ protocol confirming successful packet decoding
• Transmitted on uplink control channels (PUCCH) or shared channels (PUSCH) with strict timing alignment
• Enables efficient stop-and-wait HARQ operation, freeing transmitter buffers for new data
• Integral part of the link adaptation loop, influencing future MCS selection
• Supports bundling and multiplexing for multi-codeword MIMO and Carrier Aggregation scenarios
• Physical transmission designed for high reliability to prevent feedback error propagation

Evolution Across Releases

Defining Specifications