惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

S
SegmentFault 最新的问题
J
Java Code Geeks
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
博客园 - 司徒正美
Hugging Face - Blog
Hugging Face - Blog
F
Fortinet All Blogs
aimingoo的专栏
aimingoo的专栏
B
Blog
A
About on SuperTechFans
有赞技术团队
有赞技术团队
月光博客
月光博客
Microsoft Azure Blog
Microsoft Azure Blog
阮一峰的网络日志
阮一峰的网络日志
腾讯CDC
美团技术团队
大猫的无限游戏
大猫的无限游戏
爱范儿
爱范儿
N
Netflix TechBlog - Medium
C
Check Point Blog
Recent Announcements
Recent Announcements
博客园 - Franky
博客园 - 叶小钗
T
Tailwind CSS Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
PDU Names Explained: Data, Segment, Packet, Frame & Bits
Roboticela · 2026-06-06 · via DEV Community
Cover image for PDU Names Explained: Data, Segment, Packet, Frame & Bits

Roboticela

In any networking exam or professional discussion, you will encounter the term PDU — Protocol Data Unit. A PDU is simply the specific name for a unit of data at each layer of the OSI Model. Getting these names right is essential — it's a common exam question and a critical part of professional communication.

The Five Essential PDU Names

While each of the seven OSI layers handles data, the upper three (Application, Presentation, Session) all simply call their data unit "Data". The distinctive names appear at Layers 4–1:

7-5 Data

Application, Presentation, and Session layers all use the generic term "Data" for their PDU. The data is user information plus application-specific headers and encoding.

4 Segment (TCP) / Datagram (UDP)

The Transport Layer breaks data into Segments (TCP) or Datagrams (UDP). Each contains a source/destination port, sequence number, and other transport headers.

3 Packet

The Network Layer wraps each segment in a Packet. The packet contains source and destination IP addresses — enabling routing across multiple networks.

2 Frame

The Data Link Layer encapsulates packets in Frames. Frames contain source and destination MAC addresses for local delivery and a Frame Check Sequence for error detection.

1 Bits

The Physical Layer converts frames into a stream of raw Bits — electrical signals, light pulses, or radio waves — transmitted over the physical medium.

Why PDU Names Matter

When a network engineer says "I'm seeing malformed frames," they instantly communicate that the problem is at Layer 2. When another says "I see packet loss," that's a Layer 3 issue. When someone reports "segments are being retransmitted excessively," that's TCP at Layer 4. PDU vocabulary is the shorthand of the networking profession.

The OSI Model Simulator explicitly labels each PDU at every layer of the simulation. After a few sessions, these names become deeply ingrained — appearing in your memory automatically when you need them.

"Knowing the right word at the right layer is not pedantry — it's professional efficiency. PDU vocabulary reduces ambiguity in every networking conversation."