Header Error Control

Description

Header Error Control (HEC) is a fundamental error detection mechanism used in the data link layer and transport protocols within 3GPP systems, particularly in the Iub/Iur/Iu interfaces for UMTS and the framing of certain channels. It is a form of Cyclic Redundancy Check (CRC) calculated over the header fields of a protocol data unit (PDU). The primary function is to detect errors that may have occurred during transmission over the physical medium, specifically within the header information which is critical for proper packet processing, routing, and multiplexing. The transmitter calculates the HEC value based on the header bits and appends it to the PDU. The receiver independently recalculates the HEC from the received header and compares it to the received HEC value; a mismatch indicates a header error.

In technical implementation, such as in the Frame Protocol (FP) for the Iub interface (specified in 25.427), the HEC is typically an 8-bit field. The generator polynomial used for the CRC calculation is standardized to ensure interoperability. The HEC covers all fields in the FP header, which includes information like Connection Frame Number (CFN), Transport Format Indicator, and power control bits. When a receiver detects a HEC failure, the standard procedure is to discard the entire frame. This is because an erroneous header could lead to misdelivery of user data, incorrect timing, or faulty power control commands, which could be more detrimental than losing the frame. In some implementations or configurations, forward error correction (FEC) at a lower layer combined with HEC may allow for limited error correction, but the primary design is for detection.

The role of HEC is distinct from, yet complementary to, error detection/correction performed on the user data payload (e.g., by the RLC layer). Headers require a very high degree of integrity because a single bit error can cause the entire PDU to be misrouted or misinterpreted. By providing a dedicated, lightweight check on the header, HEC allows for rapid and reliable validation of control information before significant processing resources are expended on the potentially corrupted payload. This contributes to the overall robustness and efficiency of the transport network in the Radio Access Network (RAN).

Purpose & Motivation

HEC was introduced to address the problem of undetected errors in protocol headers, which are catastrophic for communication reliability. Physical transmission links, especially wireless backhaul connections, are susceptible to noise, interference, and fading, which can cause bit flips. Without error detection, a corrupted header could lead to a frame being delivered to the wrong user, applied with incorrect timing, or trigger erroneous control actions (like wrong power adjustments), degrading network performance and stability.

The motivation for a dedicated header check, as opposed to relying solely on payload CRCs or higher-layer checks, is efficiency and specificity. Headers are processed by every network node and are essential for frame delineation and routing. A lightweight CRC on the header allows intermediate nodes or the receiving endpoint to quickly verify header integrity and discard corrupted frames early in the processing chain, saving resources and preventing error propagation. This is particularly important for real-time control data in the RAN, where latency and reliability are critical. HEC solves the limitation of lower-layer FEC, which may not guarantee a perfectly error-free header, by adding an additional, targeted layer of protection for the most critical part of the protocol data unit.

Key Features

• Cyclic Redundancy Check (CRC) calculated over protocol header bits
• Typically an 8-bit field in framing protocols (e.g., Frame Protocol)
• Enables detection of bit errors introduced during transmission
• Triggers discarding of frames with corrupted headers to prevent processing errors
• Standardized generator polynomial for interoperability
• Complements payload error detection/correction mechanisms

Evolution Across Releases

Defining Specifications