Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

UDC

Uplink Data Compression

Radio Access Network →

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.

Introduced
Rel-9
Where
Core Network › Evolved Packet Core
Specifications
25 specs
Also in
Radio Access Network, Services, User Equipment
UDC Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define UDC. Each summary describes the whole specification, not only this term.

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 23.280Rel-18 → Rel-19

Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.

Full comparison in TS 23.280 →

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
  • 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
  • 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
  • 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

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 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.335 vj00 User Data Convergence (UDC) Procedures Rel-19 read
TS 23.845 va00 UDC Evolution Study Rel-10 read
TS 23.862 vc00 Interworking Solutions for Mobile Operators & Data Apps Rel-12 read
TS 29.212 vk00 Diameter-Based PCC Reference Points Rel-20 read
TS 29.213 vj30 PCC Procedures and Flows Rel-19 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.215 vj00 S9 Reference Point Stage 3 Specification Rel-19 read
TR 29.935 vj00 HSS Reference Data Model for Ud Interface Rel-19 read
TS 32.181 vj00 User Data Convergence Management Framework Rel-19 read
TS 32.182 vj00 UDC Common Baseline Information Model (CBIM) Rel-19 read
TR 32.901 vj00 UDC Application Data Models Study Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 36.323 vj00 PDCP Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.754 vf10 Study on Uplink Data Compression in LTE Rel-15 read
TS 37.483 vj40 E1 Application Protocol (E1AP) Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.306 vj40 NR UE Radio Access Capability Parameters Rel-19 read
TS 38.323 vj10 PDCP Protocol Specification Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19 read