Description
The Packet Data Convergence Protocol (PDCP) is a crucial sublayer of the radio protocol stack in 3GPP access technologies, including UMTS (UTRAN), LTE (E-UTRAN), and NR (NG-RAN). It is defined for both the User Plane (UP) and Control Plane (CP). Architecturally, PDCP entities are located in the User Equipment (UE) and in the network node (NodeB/eNodeB/gNB), one per Radio Bearer. Its primary functions are convergence, meaning it adapts higher-layer protocols (typically IP) for efficient transmission over the specific radio interface.
For the User Plane, PDCP performs Robust Header Compression (ROHC) to significantly reduce the size of IP packet headers (e.g., IPv4, IPv6, UDP, RTP), which are large relative to payload for many applications, thereby saving precious air interface bandwidth. It also provides security through ciphering (encryption) of the user data payload to ensure confidentiality. Furthermore, for LTE and NR, PDCP ensures in-sequence delivery and duplicate detection of data packets during handover procedures. It manages the PDCP Sequence Number (SN) and buffers packets to allow lossless handover when the underlying RLC layer is operating in Acknowledged Mode (AM).
For the Control Plane, specifically for RRC and NAS messages, PDCP provides integrity protection and ciphering. Integrity protection guarantees that control messages have not been tampered with during transmission. PDCP performs these security functions using keys derived by the NAS and AS security procedures. The protocol operates by receiving Service Data Units (SDUs) from the higher layers (IP or RRC), attaching a PDCP header containing the sequence number, performing the configured operations (compression, ciphering), and then passing the resulting Protocol Data Unit (PDU) to the RLC layer below. During reception, the process is reversed. Its role is fundamental to achieving efficient, secure, and reliable data delivery in modern cellular networks.
Purpose & Motivation
PDCP was introduced to address the inefficiencies and security shortcomings of transmitting Internet Protocol (IP) packets directly over the radio link in 3G UMTS. In early 3G releases, the protocol stack lacked a dedicated convergence layer, making IP packet transmission over the air resource-intensive due to large, repetitive headers. This was particularly problematic for voice-over-IP (VoIP) and interactive gaming where small payloads are dwarfed by IP/UDP/RTP headers.
The protocol solves several key problems. First, header compression (initially introduced in Rel-4) dramatically improves spectral efficiency and reduces latency for IP-based services. Second, it centralizes ciphering for user data at a layer above RLC, simplifying security architecture and enabling ciphering even when RLC is in Transparent Mode. Third, with the move to a flatter, all-IP architecture in LTE, PDCP's role expanded to include in-order delivery and duplicate removal, which are essential for maintaining data integrity during handovers between eNodeBs, especially for delay-sensitive services. Its creation was motivated by the need to optimize the radio interface for the explosive growth of IP traffic, ensure robust security, and support seamless mobility in increasingly heterogeneous network environments.
Key Features
- Robust Header Compression (ROHC) for IP, UDP, RTP, and ESP headers
- Ciphering (encryption) for user plane data and control plane messages
- Integrity protection for control plane (RRC) data
- In-sequence delivery and duplicate detection during handover
- PDCP Sequence Number management for lossless handover support
- Support for data and control plane, and multiple radio bearers
Evolution Across Releases
Initial introduction of PDCP for UMTS (UTRAN). Defined basic functions: header compression using RFC 2507 and later RFC 3095 (ROHC), and transfer of user data. Ciphering was not initially part of PDCP in UTRAN; it was performed at the RLC/MAC layers.
Major overhaul and redefinition for LTE (E-UTRAN). PDCP was significantly enhanced to become the sole layer for user plane ciphering and integrity protection. Introduced PDCP Sequence Numbers, in-order delivery, duplicate detection, and retransmission during handover for lossless mobility. Became a critical component of the flat IP architecture.
Introduction of PDCP for 5G NR (NG-RAN). Added support for the new 5G QoS framework, reflective QoS, and additional integrity protection algorithms. Enhanced duplication and reliability features for Ultra-Reliable Low Latency Communication (URLLC) services. Introduced the concept of PDCP duplication for packet redundancy over multiple paths.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.725 | 3GPP TS 23.725 |
| TS 25.301 | 3GPP TS 25.301 |
| TS 25.323 | 3GPP TS 25.323 |
| TS 25.324 | 3GPP TS 25.324 |
| TS 25.331 | 3GPP TS 25.331 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.912 | 3GPP TS 25.912 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 26.114 | 3GPP TS 26.114 |
| TS 26.926 | 3GPP TS 26.926 |
| TS 26.935 | 3GPP TS 26.935 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 27.060 | 3GPP TS 27.060 |
| TS 28.837 | 3GPP TS 28.837 |
| TS 29.061 | 3GPP TS 29.061 |
| TS 33.401 | 3GPP TR 33.401 |
| TS 33.821 | 3GPP TR 33.821 |
| TS 33.825 | 3GPP TR 33.825 |
| TS 33.835 | 3GPP TR 33.835 |
| TS 33.836 | 3GPP TR 33.836 |
| TS 33.843 | 3GPP TR 33.843 |
| TS 33.938 | 3GPP TR 33.938 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.306 | 3GPP TR 36.306 |
| TS 36.323 | 3GPP TR 36.323 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.360 | 3GPP TR 36.360 |
| TS 36.361 | 3GPP TR 36.361 |
| TS 36.413 | 3GPP TR 36.413 |
| TS 36.423 | 3GPP TR 36.423 |
| TS 36.424 | 3GPP TR 36.424 |
| TS 36.463 | 3GPP TR 36.463 |
| TS 36.938 | 3GPP TR 36.938 |
| TS 37.320 | 3GPP TR 37.320 |
| TS 37.901 | 3GPP TR 37.901 |
| TS 38.306 | 3GPP TR 38.306 |
| TS 38.323 | 3GPP TR 38.323 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.415 | 3GPP TR 38.415 |
| TS 38.424 | 3GPP TR 38.424 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 44.060 | 3GPP TR 44.060 |
| TS 44.160 | 3GPP TR 44.160 |