What Is a PDU in Networking?
In networking, PDU stands for Protocol Data Unit. It is the structured block of information that a protocol sends across a network link. Every layer of the OSI model or TCP/IP stack creates its own PDU, adding control information before passing the data down to the next lower layer. The term captures a simple but important idea: network communication is a layered process, and each layer packages data differently.
More from this site
Keep reading the latest coverage
Understanding PDU meaning in networking helps engineers trace how a message travels from an application on one device to an application on another. It also makes troubleshooting more systematic, because each layer has a distinct header format and a recognizable name for its unit.
How PDUs Map to OSI Layers
The OSI model defines seven layers, and each layer encapsulates the PDU from the layer above before adding its own header and, sometimes, trailer. The table below shows the common names and what each layer contributes.
| OSI Layer | PDU Name | Typical Contents |
|---|---|---|
| Application (7) | Data / Message | User payload, application protocols such as HTTP or DNS |
| Presentation (6) | Data | Encryption, compression, translation |
| Session (5) | Data | Session management, synchronization |
| Transport (4) | Segment (TCP) / Datagram (UDP) | Port numbers, sequence numbers, error control |
| Network (3) | Packet | Source and destination IP addresses, TTL |
| Data Link (2) | Frame | MAC addresses, error detection (FCS) |
| Physical (1) | Bits / Signal | Electrical, optical, or radio encoding |
At the physical layer, the PDU becomes a stream of bits transmitted over the medium. The Data Link layer groups those bits into frames, the Network layer wraps them into packets, and so on upward. The term PDU is often used generically when the exact layer does not matter, but precise conversations usually name the specific unit.
PDU Encapsulation and Decapsulation
Encapsulation is the process of adding a header (and sometimes a trailer) to the PDU received from the upper layer. A router performs decapsulation when it receives a frame, strips the Data Link header, inspects the packet header, and re-encapsulates the packet in a new frame for the next hop. On the receiving side, the reverse happens: each layer removes its corresponding header and passes the inner PDU up to the next layer until the original application data reaches the destination.
This nested packaging is why PDU meaning in networking is more than a label. It describes where in the stack a device is reading or writing headers, which determines what addressing and error-checking fields are visible at that point.
Common PDU Types and Their Roles
While the OSI model gives the canonical mapping, practical networking often focuses on a handful of PDUs:
- Segment: Used by TCP for reliable, ordered delivery. Includes port numbers and sequence control.
- Datagram: Used by UDP when reliability is handled by the application or is not needed.
- Packet: The unit routed across networks, identified by IP addresses.
- Frame: The unit switched on a local network segment, identified by MAC addresses.
- Bits: The physical representation of the PDU on copper, fiber, or wireless media.
Each type carries the information needed for its layer's job. A switch, for example, makes forwarding decisions based on the frame's destination MAC address and does not inspect the packet inside unless it is a Layer 3 switch.
PDU Size, MTU, and Fragmentation
Every PDU has a maximum size tied to the underlying link. The Maximum Transmission Unit (MTU) defines the largest packet a link can carry without fragmentation. When a packet exceeds the MTU of a downstream link, routers may fragment it into smaller packets, each becoming its own PDU at the Network layer. Reassembly happens at the destination, which adds overhead and latency. Path MTU Discovery helps avoid unnecessary fragmentation by discovering the smallest MTU along the route.
Why PDU Awareness Matters for Network Engineers
Knowing PDU meaning in networking lets engineers read captures and logs with precision. Wireshark displays each PDU with its protocol name and relevant headers. By expanding a frame, then a packet, then a segment, an engineer can see exactly where a problem occurs: a malformed frame suggests a physical or Data Link issue, while a packet with a bad checksum points to a routing or configuration error.
PDU awareness also supports capacity planning. Understanding how much overhead each layer adds helps estimate real throughput and buffer requirements on switches, routers, and endpoints.