Protocol Data Unit

Description

A Protocol Data Unit (PDU) is a standardized data block used for communication between peer entities within a layered protocol architecture, such as the OSI model or 3GPP protocol stacks. Each PDU is specific to a given layer (e.g., RRC, PDCP, RLC, MAC, NAS, GTP-U) and is composed of two main parts: the Protocol Control Information (PCI), which is the header added by the current layer containing instructions for the peer entity, and the Service Data Unit (SDU), which is the payload received from the layer above. For instance, an IP packet is the SDU for the PDCP layer, which adds its header to create a PDCP PDU. This PDU then becomes the SDU for the RLC layer, which in turn creates an RLC PDU, and so on down the stack.

In the 3GPP architecture, PDUs are central to every interface and procedure. On the radio interface (Uu), key PDUs include RRC PDUs for control signaling (e.g., RRCConnectionSetup), and user plane PDUs processed through the PDCP, RLC, and MAC layers. In the core network, NAS PDUs carry signaling between the UE and the AMF/SMF, while GTP-U PDUs tunnel user data between the gNB and UPF over the N3 interface. The processing of a PDU involves encapsulation at the transmitting side (adding headers/trailers) and decapsulation at the receiving side (stripping them off to retrieve the SDU for the higher layer). This layered processing ensures separation of concerns, modularity, and interoperability.

The role of the PDU is to provide a standardized container that ensures reliable, in-order, and secure delivery of information across the network. Different layers impart different characteristics to their PDUs. The RLC layer, for example, can segment or concatenate SDUs to fit radio resources, creating RLC PDUs. The MAC layer schedules MAC PDUs for transmission via transport blocks. In the core network, the PDU Session is a key concept representing an association for PDU connectivity service, where a PDU Session ID uniquely identifies the session, and user data flows as sequences of PDUs through established tunnels. Thus, the PDU is the atomic unit of data transfer that enables all 3GPP services, from voice calls to high-speed internet access.

Purpose & Motivation

The PDU concept exists to enable structured, layered communication in complex digital networks. Before standardized layered architectures, communication protocols were monolithic and inflexible, making them difficult to develop, debug, and evolve. The introduction of the PDU as part of layered models (like OSI and TCP/IP) solved the problem of managing complexity by dividing communication tasks into discrete layers, each with a specific function and a well-defined interface to adjacent layers. The PDU is the tangible object passed across these interfaces.

Historically, as telecommunications evolved from circuit-switched voice to packet-switched data, the need for a robust, multi-layered data unit became paramount. In 3GPP, starting from GSM and through UMTS, LTE, and now 5G, the PDU framework has provided consistency and backward compatibility. It addresses the limitation of having no common 'data currency' for different protocol functions. For example, the same IP packet (a network layer PDU) can be carried transparently through different radio access technologies (GERAN, UTRAN, E-UTRAN, NG-RAN) because each technology defines how to encapsulate it into its own link-layer PDUs (e.g., LLC PDUs, RLC PDUs).

Ultimately, the PDU is the foundational construct that allows for interoperability, efficient processing (e.g., header compression in PDCP), error correction (in RLC), and multiplexing (in MAC). It enables the network to treat different types of traffic (control vs. user plane) with appropriate reliability and priority. The evolution of PDU structures across releases (e.g., new PDCP headers for security, new RRC PDUs for 5G NR features) reflects the ongoing adaptation of the standards to new services and requirements, while maintaining the core principle of layered communication.

Key Features

• Consists of a Protocol Control Information (header) and a Service Data Unit (payload)
• Layer-specific; each protocol layer (RRC, PDCP, RLC, MAC, NAS) defines its own PDU structure
• Enables encapsulation and decapsulation in a layered protocol stack
• Can be subject to segmentation, concatenation, and reassembly by layers like RLC
• Carries both user data and control signaling information
• Identified uniquely within contexts like a bearer or a PDU Session

Evolution Across Releases

Defining Specifications