N-HC

Network Header Compressor

Radio Access Network
Introduced in Rel-5
An entity in the network, typically the RNC's PDCP layer, that performs header compression on downlink data packets. It reduces IP/UDP/RTP header overhead to conserve radio bandwidth and improve spectral efficiency for services like VoIP. This is crucial for optimizing limited air interface resources.

Description

The Network Header Compressor (N-HC) is a functional entity defined within the 3GPP UMTS Radio Access Network (UTRAN) architecture, specifically residing in the Radio Network Controller (RNC). Its primary implementation is within the Packet Data Convergence Protocol (PDCP) layer. The N-HC operates on the downlink path, meaning it processes data packets flowing from the core network towards the User Equipment (UE). Its core function is to apply robust header compression (ROHC) algorithms to IP-based traffic, such as VoIP (using RTP/UDP/IP) or interactive web traffic (TCP/IP). The compressor analyzes the packet headers, identifies static and dynamic fields, and replaces the full headers with much shorter context identifiers and compressed header information in subsequent packets. This process establishes and maintains a compression context both at the N-HC and its peer entity, the UE's header decompressor (U-HD). The context contains the static information and changing patterns of header fields, allowing the decompressor to reconstruct the original headers. The N-HC is responsible for context initialization, updating, and management, ensuring synchronization with the decompressor even in the presence of packet loss. By drastically reducing header size from 40-60 bytes for IPv4/v6 to a few bytes, the N-HC directly increases the payload capacity of each radio transport block, leading to more efficient use of the scarce and expensive radio spectrum. Its operation is transparent to higher layers and is configurable per radio bearer based on the QoS profile, allowing network operators to apply compression selectively to maximize gains for delay-sensitive, low-bandwidth applications.

Purpose & Motivation

The N-HC was introduced to address the significant inefficiency of transmitting full IP headers over the bandwidth-constrained and error-prone cellular radio interface. In early packet-switched mobile data services, the overhead from IP, UDP, and RTP headers could constitute 60-80% of the packet for small-payload services like Voice over IP (VoIP), making such services economically and technically unviable. The primary motivation was to enable efficient support of real-time, low-bit-rate services over UMTS networks, which was a key goal of 3GPP Release 5. Without header compression, the spectral efficiency for conversational services would be prohibitively low, wasting capacity and increasing latency. The N-HC, as part of the ROHC framework standardized in IETF and adopted by 3GPP, solved this by moving the complex compression logic to the stable network side (RNC), allowing for simpler decompression in the UE. This architectural choice balanced processing complexity and power consumption, ensuring the UE battery life was not overly impacted while achieving the necessary bandwidth savings to make services like video telephony and VoIP feasible over 3G networks.

Key Features

  • Located in the RNC's PDCP layer for downlink traffic compression
  • Implements Robust Header Compression (ROHC) profiles (e.g., for IP, UDP, RTP, ESP)
  • Establishes and manages compression contexts synchronized with the UE decompressor
  • Dynamically adapts compression state (e.g., Initialization, First Order, Second Order) based on link reliability
  • Configurable per radio bearer based on QoS requirements and traffic type
  • Provides robustness against packet loss and residual errors on the radio link

Evolution Across Releases

Rel-5 Initial

Introduced as part of the PDCP specification for UMTS. Defined the N-HC entity in the RNC to perform downlink header compression using the ROHC framework (RFC 3095). Supported initial ROHC profiles for uncompressed, RTP/UDP/IP, UDP/IP, and ESP/IP packets to enable efficient VoIP and real-time services.

Defining Specifications

SpecificationTitle
TS 25.323 3GPP TS 25.323