Description
Ethernet Header Compression (EHC) is a protocol defined by 3GPP to efficiently transmit Ethernet frames over cellular radio access networks (RAN), specifically for NR (New Radio) and LTE. It operates by compressing the often-redundant fields within Ethernet frame headers before transmission over the Uu air interface between the User Equipment (UE) and the gNB (in 5G) or eNB (in LTE). The protocol is typically implemented in the Packet Data Convergence Protocol (PDCP) layer, which is responsible for header compression and ciphering. EHC works by establishing a context between the compressor (sender) and decompressor (receiver) for each data flow. This context contains static information about the Ethernet header fields, such as source and destination MAC addresses, VLAN tags, and EtherType. After an initial full header is sent to establish the context, subsequent packets transmit only a compressed header containing dynamic fields (like sequence numbers) and changes to static fields, significantly reducing the per-packet overhead.
The architecture involves EHC entities in both the UE and the base station (gNB/eNB). Compression and decompression are performed at the PDCP layer. The network configures EHC parameters via RRC (Radio Resource Control) signaling, specifying profiles and contexts. EHC supports multiple profiles to handle different Ethernet frame types, including those with and without VLAN tags. It uses robust header compression (ROHC) principles adapted for Ethernet, employing feedback mechanisms to ensure reliable context synchronization between compressor and decompressor, even in lossy radio conditions.
EHC's role is critical in the 5G system architecture for supporting Ethernet-based services that require low latency and high reliability, such as those defined for the 5G LAN-type service, industrial automation, and fronthaul/backhaul integration. By reducing header size, it decreases transmission time and increases effective data throughput, which is vital for meeting the stringent requirements of Ultra-Reliable Low-Latency Communication (URLLC) and enhanced Mobile Broadband (eMBB) use cases. It enables the 5G system to natively transport layer 2 Ethernet frames, facilitating integration with existing Ethernet-based industrial networks and supporting network slicing for isolated service segments.
Purpose & Motivation
EHC was introduced to address the inefficiency of transmitting standard Ethernet frames, which have a minimum header size of 14 bytes (plus optional VLAN tags), over the bandwidth-constrained and latency-sensitive air interface in 4G and 5G networks. Prior to EHC, transporting Ethernet traffic over cellular required tunneling protocols like GTP-U, which added further overhead, or transmitting uncompressed headers, wasting valuable radio resources. This was particularly problematic for new 5G use cases like industrial IoT, vehicle-to-everything (V2X), and mobile fronthaul, where many small, frequent Ethernet packets (e.g., for sensor data or control signals) are generated, making header overhead a significant portion of the total transmission.
The creation of EHC was motivated by the need to optimize radio resource utilization for Ethernet-based services, which are foundational in many vertical industries. 3GPP Release 16, which introduced enhanced support for vertical LAN services and time-sensitive networking, identified Ethernet transport as a key requirement. EHC directly supports these capabilities by minimizing air interface overhead, thereby improving spectral efficiency, reducing latency, and increasing capacity for Ethernet flows. It solves the problem of efficiently integrating layer 2 Ethernet networks with 3GPP cellular systems, enabling 5G to act as a seamless Ethernet bridge for industrial and enterprise applications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (84 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the EHC (Ethernet Header Compression) function was not newly introduced; the provided grounding context and list of Change Requests for PDCP in Release 15 contain no mention of EHC. The documented PDCP enhancements for this release instead include the introduction of PDCP duplication, support for ROHC with PDCP duplication and for V2X and Mission Critical services, and various corrections and clarifications to the PDCP specification and structure.
- Introduction of PDCP duplication TS 38.323CR0009
- RoHC support for Mission Critical services over MBMS TS 36.300CR1116
- Correction on the feature downlink SDAP header TS 36.306CR1711
- Inclusion of Maximum Number of PDCP SDUs per TTI for DL Categories 22-26 TS 36.306CR1736
- Deliver stored PDCP SDUs for UM DRB at PDCP re-establishment TS 36.323CR0241
- CR on supporting of the ROHC for PDCP duplication TS 36.323CR0243
+ 22 more changes
In Release 16, the new Ethernet Header Compression (EHC) function was introduced for the LTE PDCP layer to efficiently compress Ethernet frame headers. This addition specifically enhanced the user plane protocol stack for data bearers configured to carry Ethernet traffic. The specification also included necessary corrections for PDCP operation when EHC was configured alongside features like out-of-order delivery.
- Introducing EHC in LTE PDCP TS 36.323CR0278
- E2E delay measurement for Qos monitoring for URLLC TS 38.463CR0481
- Support of Ethernet Header Compression TS 38.463CR0478
- Allowing PDCP version change without handover TS 36.306CR1754
- LTE PDCP corrections for NR IIOT TS 36.323CR0286
- Correction for PDCP status report TS 36.323CR0287
+ 20 more changes
In Release 17, the EHC (Ethernet Header Compression) function was enhanced with specific corrections and clarifications to its operation. These included a dedicated Change Request for EHC decompression procedures and another for corrections on EHC parameters. This work refined the existing EHC mechanism within the PDCP layer to improve its reliability and specification accuracy.
- Introducing support of UP IP for EPC connected architectures using NR PDCP TS 36.300CR1353
- Introduction of Rel-17 IIoT/URLLC to TS 38.300 TS 38.300CR0416
- Introducing support of UP IP for EPC connected architectures using NR PDCP TS 38.323CR0085
- Correction on PDCP Control PDU for UDC feedback TS 36.323CR0304
- Extended PDCP Discard Timer over E1 interface TS 37.483CR0002
- Correction on PDCP for SL relay TS 38.323CR0093
+ 12 more changes
In Release 18, the EHC (Ethernet Header Compression) function itself is not mentioned in the provided Change Request titles or grounding context. The listed CRs for Release 18 focus on other PDCP enhancements, including corrections and new support for PDCP Sequence Number Gap reporting, alongside various corrections for URLLC, RedCap, and PDCP duplication procedures.
- Introduction of Timing Resiliency and URLLC enhancements TS 38.300CR0730
- Introduction of NR sidelink PDCP duplication in TS 38.323 TS 38.323CR0126
- Support of PDCP SN Gap Report TS 37.483CR0135
- Correction on UAI for URLLC TS 38.300CR0793
- Correction to PDCP duplication description for L2 MP using SL relay or N3C indirect path TS 38.300CR0989
- PDCP SN gap reporting TS 38.323CR0139
+ 4 more changes
In Release 19, the new EHC (Ethernet Header Compression) function introduced specific enhancements for XR (Extended Reality) traffic within the PDCP layer. These enhancements were detailed alongside necessary corrections to the XR PDCP specifications to ensure proper implementation. The updates focused on optimizing the PDCP protocol's handling of XR data flows to improve efficiency.
Explore further
Broader topics and technologies where EHC plays a role.
Defining Specifications
3GPP specifications that define or reference EHC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.306 vj00 | E-UTRA UE Radio Access Capability Parameters | Rel-19 |
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 |
| TS 37.483 vj10 | E1 Application Protocol (E1AP) | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.323 vj00 | Packet Data Convergence Protocol (PDCP) | Rel-19 |
| TS 38.463 vj00 | E1 Application Protocol (E1AP) | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |