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

推荐订阅源

A
About on SuperTechFans
G
Google Developers Blog
L
LangChain Blog
aimingoo的专栏
aimingoo的专栏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
云风的 BLOG
云风的 BLOG
小众软件
小众软件
月光博客
月光博客
Recent Announcements
Recent Announcements
人人都是产品经理
人人都是产品经理
P
Proofpoint News Feed
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
雷峰网
雷峰网
The Cloudflare Blog
博客园_首页
美团技术团队
大猫的无限游戏
大猫的无限游戏
B
Blog
IT之家
IT之家
Jina AI
Jina AI
H
Hackread – Cybersecurity News, Data Breaches, AI and More
C
Check Point 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
Stop Memorizing the PDU names — Understand It Like Amazon...
TAKUMI SUGAT · 2026-04-23 · via DEV Community

Introduction

While studying for CompTIA Network+, I couldn't totally grasp the PDU names in the OSI model. I could memorize them, but I never understood why the names are what they are.

One day, while ordering some items on Amazon, it hit me — the ordering process maps perfectly to the OSI model. So I decided to write it down.


What is OSI model

The OSI model is a framework that divides network communication into 7 layers. Separating responsibilities by layer makes it easier to identify which layer is causing a problem.

Layer Name
7 Application
6 Presentation
5 Session
4 Transport
3 Network
2 Data Link
1 Physical

Note: This mnemonic goes from Layer 1 to 7 (bottom to top).
Physical → Data Link → Network → Transport → Session → Presentation → Applicaion


What is PDU

PDU (Protocol Data Unit) is the name given to data at each layer. Each time data passes through a layer, it gets a new name.

Layer PDU name
7–5 Data
4 Segment
3 Packet
2 Frame
1 Bit

We can memorize them:
" Do Some People Fear Birthdays?"

Data → Segment → Packet → Frame → Bit


What is Encapsulation and Decapsulation

-Encapsulation: The process of adding headers to data as it moves down the layers (sender side).
-Decapsulation: The process of removing headers from data as it moves up the layers (receiver side).

We can memorize them:

-En = put in an envelope → Top to Bottom (7-1), adding header when sending.
-De = take out of the envelope → Bottom to Top (1-7), removing header when receiving.


Understand the concept with Amazon ordering

This section is the main part of this article.
When I think about Amazon ordering process - from ordering items to delivering them, I could understand them easily.


Layer 7-5 (Data) - Items themselves

Data represents the items we ordered in Amazon.
T-shirts, gadgets, or other items stays in Amazon warehouse.
It is not wrapped yet.

Layer 4 (Segment) - Dividing and Numbering them

It can be difficult to deliver them, if the order consists of multiple items.
Therefore, we need to divide into small portion and numbering them 1,2,3…

Without numbers, it would be impossible to identify which piece is missing if they arrive out of order.

Layer 3 (Packet) - Putting in boxes and Labeling them

In this process, divided items are put into boxes and labeling each of them.
Labels show the destination address about receiver (IP address).
The multiple boxes come to do have same address labels.

The labels are useful to determine routes to deliver.

Layer 2 (Frame) - Adding relay labels about next delivering center to Boxes

The destination address (IP address) always stays the same, but the package doesn't travel directly to the final destination -it goes through multiple delivery centers along the way.

The actual delivering process is going through many delivering center in each locations until completing delivering, and relay labels, shows destination center, are replaced each time.
This label is the Frame (MAC Address).

-Destination address label (IP Address) = Final destination = stays same
-Relay label (MAC Address) = Next center destination = replaced whenever the items go through delivering center

Layer 1 (Bit) - Transporting

Actually, those boxes are transported physically by track.
Items go through cables or wireless as electrical or light signal (0,1) .
Ultimately, any data are exchanged to 0 and 1.


Conclusion

[Sending side: Encapsulation]
Items (Data)
↓ Dividing and numbering
Segments
↓ Labeling with destination address (IP Address)
Packets
↓ Labeling with next delivery center (MAC Address)
Frames
↓ Physical transport
Bits → Network

[Receiving side: Decapsulation]
Bits ← Network
↓ Removing relay labels at each delivery center
Frames → Packets → Segments
↓ Reassembling and unpacking
Items (Data)