UDC

Uplink Data Compression

Radio Access Network →
Introduced in Rel-9 Also in: Radio Access Network, Services, User Equipment

UDC is a radio interface feature that compresses user data in the uplink before transmission to reduce data volume, conserve radio resources, lower UE power consumption, and improve spectral efficiency.

Category
Radio Access Network
Introduced
Rel-9
Where
Core Network › Evolved Packet Core
Also touches
3 segments
Specifications
25 specs
UDC Description Purpose Related Classification Detected Changes Specifications

Description

Uplink Data Compression (UDC) is a performance-enhancing feature in 3GPP LTE and 5G NR that operates at the Packet Data Convergence Protocol (PDCP) layer. Its primary function is to apply lossless compression algorithms to user plane data packets in the uplink direction (from User Equipment to the base station) before they are ciphered and transmitted over the radio interface. The process involves the UE compressing IP packets (including headers and payload) and the receiving network node (eNodeB/gNB) decompressing them. The compression context is established and synchronized between the UE and the network during radio bearer setup or reconfiguration.

Architecturally, UDC is integrated into the PDCP entity for a specific data radio bearer. When configured by the network via RRC signaling, the UE's PDCP layer applies a compression algorithm (e.g., based on Robust Header Compression (ROHC) principles or dedicated UDC algorithms) to the incoming IP packets from higher layers. The compressed packet, along with necessary control information, is then processed through standard PDCP functions like ciphering and adding a PDCP header before being passed to the RLC layer. The gNB performs the inverse operation. The feature requires robust error recovery mechanisms to handle packet loss without causing de-synchronization of the compression context.

UDC plays a crucial role in optimizing radio resource utilization. By reducing the size of uplink transmissions, it decreases the amount of physical layer resources (time/frequency blocks) required, which directly translates to improved cell capacity and user throughput. It is especially effective for applications with repetitive data patterns, such as messaging, IoT sensor reports, or certain web protocols. The feature is managed by the RAN and can be dynamically controlled per UE and per bearer based on network policy and observed traffic characteristics.

Purpose & Motivation

UDC was created to address the growing asymmetry in cellular data traffic and the specific challenges of uplink transmission. While downlink capacity saw significant improvements with advanced techniques, uplink efficiency remained a bottleneck, constrained by UE transmit power and available bandwidth. Transmitting raw, repetitive data (like protocol headers) consumes valuable radio resources and UE battery life unnecessarily.

The technology solves this by applying lossless compression at the source (the UE), directly reducing the payload size before it consumes radio interface resources. This is particularly important for latency-tolerant IoT devices, which often send small, periodic reports, and for scenarios with limited uplink coverage. By improving spectral efficiency, UDC allows networks to serve more users with the same bandwidth or to deliver the same user experience with lower resource allocation, leading to cost savings and enhanced performance. Its introduction in LTE-Advanced (Rel-9) was part of a broader effort to optimize all aspects of the radio interface for efficient data handling.

Classification

Part ofPDCP
Related approachesROHC

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 8 changes

In Release 15, the Uplink Data Compression (UDC) function was newly introduced with a DEFLATE-based compression solution. This introduction included specifications for the UDC data format, clarifying that the UDC Header is part of the Data Field, and provided corrections and clarifications for UDC-only PDUs and configuration.

  • Introduction of DEFLATE based UDC Solution TS 36.300CR1090
  • Introduction of DEFLATE based UDC Solution TS 36.306CR1543
  • Introduction of DEFLATE based UDC Solution TS 36.323CR0217
  • Introduction of DEFLATE based UDC Solution TS 36.331CR3211
  • Correction to description for UDC-only PDU TS 36.323CR0238
  • Correction on UDC data format TS 36.323CR0266

+ 2 more changes

Rel-16 2 changes

In Release 16, the UDC (User Data Convergence) function was enhanced to handle specific RRC connection re-establishment scenarios. The updates introduced procedures for the reconfiguration of UDC parameters, specifically for the buffer size, following an RRC connection re-establishment. This ensured that the UDC's data handling remained correctly aligned with the connection state after this critical recovery procedure.

  • UDC reconfiguration for RRC connection re-establishment case TS 36.331CR4221
  • BufferSize reconfiguration for UDC after RRC connection re-establishment TS 36.331CR4551
Rel-17 11 changes

In Release 17, the new support for Uplink Data Compression (UDC) in NR was introduced, with subsequent corrections made to its implementation in the PDCP control PDU for feedback, the CP-UP split architecture, and specific parameters over the E1 interface and in E1AP messaging. Further corrections addressed UE behavior in the RRC resume procedure and NR UDC details in the RRC specification (38.331). These updates refined the integration of the UDC function, which is part of the broader User Data Convergence concept for simplifying network topology and managing user data.

  • Introduction of the support for UDC in NR TS 38.300CR0415
  • Introduction of the support for UDC in NR TS 38.323CR0087
  • Introduction of the support for UDC in NR TS 38.331CR2927
  • Correction on PDCP Control PDU for UDC feedback TS 36.323CR0304
  • Correction of UDC in CP-UP Split architecture TS 37.483CR0001
  • Correction to UDC Parameters in E1AP TS 37.483CR0064

+ 5 more changes

Explore further

Broader topics and technologies where UDC plays a role.

Defining Specifications

3GPP specifications that define or reference UDC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 22.985 vj00 3GPP User Data Convergence (UDC) concept Rel-19
TS 23.203 vj20 Policy and charging control architecture Rel-19
TS 23.280 vk10 Common Architecture for Mission Critical Services Rel-20
TS 23.335 vj00 User Data Convergence (UDC) Procedures Rel-19
TS 23.845 va00 UDC Evolution Study Rel-10
TS 23.862 vc00 Interworking Solutions for Mobile Operators & Data Apps Rel-12
TS 29.212 vj00 Gx/Gxx/Sd/St Diameter Protocol Rel-19
TS 29.213 vj20 PCC Signalling Flows and QoS Mapping Rel-19
TS 29.214 vj20 Policy and Charging Control over Rx Rel-19
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19
TR 29.935 vj00 HSS Reference Data Model for Ud Interface Rel-19
TS 32.181 vj00 User Data Convergence Management Framework Rel-19
TS 32.182 vj00 UDC Common Baseline Information Model (CBIM) Rel-19
TR 32.901 vj00 UDC Application Data Models Study Rel-19
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 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 36.754 vf10 Study on Uplink Data Compression in LTE Rel-15
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.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.