Negation ACKnowledgement

Description

The Negation ACKnowledgement (NACK) is a fundamental feedback signal within Automatic Repeat reQuest (ARQ) and Hybrid ARQ (HARQ) mechanisms defined in 3GPP specifications for UMTS, LTE, and NR. It operates as part of the link-layer error control protocol, primarily in the Medium Access Control (MAC) and Physical (PHY) layers. When a receiver fails to correctly decode a transport block—due to factors like poor channel conditions, interference, or collision—it sends a NACK message back to the transmitter via a dedicated feedback channel (e.g., the Physical HARQ Indicator Channel (PHICH) in LTE or the Physical Uplink Control Channel (PUCCH)/Physical Downlink Control Channel (PDCCH) in NR). This negative acknowledgement explicitly informs the sender that the specific data unit identified by a sequence number or HARQ process ID requires retransmission.

The technical operation involves tight coupling with timers, sequence numbers, and soft buffer management. Upon receiving a NACK, the transmitter schedules a retransmission of the same or a redundant version (incremental redundancy) of the original data. In HARQ, particularly Chase Combining or Incremental Redundancy, the receiver combines the initially received (erroneous) packet with the retransmitted version before attempting decoding again, improving the probability of success. The NACK feedback is typically multiplexed with ACK signals and other control information, requiring efficient coding (e.g., 1-bit indicator per HARQ process) to minimize overhead. In scenarios with multiple component carriers or multiple input, multiple output (MIMO) layers, separate NACKs may be generated per carrier or codeword.

Its role is critical for achieving reliable packet data services, especially for delay-sensitive applications like voice over IP (VoIP) or real-time gaming, where TCP's end-to-end retransmission would be too slow. By providing fast, link-local retransmissions, NACK-based mechanisms maintain throughput and latency targets despite varying radio conditions. The design ensures that the radio link control (RLC) layer's acknowledged mode (AM) can rely on HARQ for most errors, reducing higher-layer retransmissions and improving overall system efficiency.

Purpose & Motivation

The NACK mechanism was introduced to address the inherent unreliability of wireless channels, where packet loss due to fading, interference, and noise is common. Prior to standardized HARQ in 3GPP, early cellular systems used simpler stop-and-wait ARQ or no link-layer retransmissions, leading to poor spectral efficiency and unreliable data services. The creation of NACK as part of HARQ in Release 5 (HSDPA) for UMTS was motivated by the need for higher data rates and lower latency for packet-switched services, enabling efficient retransmissions without excessive signaling delay.

It solves the problem of inefficient error recovery by allowing rapid, physical-layer-aware retransmissions that adapt to channel conditions. Without NACK, all error recovery would depend on higher-layer protocols like TCP, which introduce significant latency due to round-trip times and congestion control mechanisms, degrading user experience for interactive services. The NACK feedback enables the system to implement adaptive modulation and coding (AMC) more aggressively, as errors can be quickly corrected, thus pushing the operational point closer to the channel capacity limit.

Historically, its evolution through LTE and NR reflects the increasing demands for ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB). In NR, enhancements like codeblock-group-based HARQ and multi-shot feedback allow partial retransmissions and improved reliability for large transport blocks, making NACK an even more granular and efficient tool for maintaining quality of service in 5G and beyond.

Key Features

• Explicit negative feedback for failed packet decoding
• Integral part of Hybrid ARQ (HARQ) for fast retransmissions
• Uses dedicated physical control channels (e.g., PHICH, PUCCH) for transmission
• Supports multiple HARQ processes for continuous data flow
• Enables incremental redundancy and chase combining techniques
• Facilitates link adaptation and robust performance under varying radio conditions

Evolution Across Releases

Defining Specifications