It gives seven named layers so engineers can discuss responsibilities clearly, even when real protocols blur boundaries.
OSI vs TCP/IP Layer Mapping Workbench
Compare the OSI reference model with practical TCP/IP layering while tracing how IoT data is encapsulated.
animation
networking
osi
tcpip
encapsulation
iot-protocol-stack
Learner-ready OSI and TCP/IP layer mapping workbench with scenario presets, animated encapsulation stages, protocol placement diagnostics, quick reference cards, source links, and desktop/mobile visual checks.
Interactive animation
OSI vs TCP/IP Layer Mapping Workbench
Use the scenarios and controls to watch IoT data move down a network stack. The animation shows where each protocol fits, what the packet becomes at each stage, and why the OSI and TCP/IP models are useful but not perfectly identical.
Current scenario
HTTPS dashboard request
Active layer focus
Application data
Mapping confidence
Clean mapping
Teaching view
4-layer TCP/IP
Application, Transport, Internet, and Link/Network Access layers are enough for most real troubleshooting.
Each lower layer adds delivery information for its own scope.
TLS, QUIC, 6LoWPAN, and gateways need careful placement rather than memorized layer labels.
Guided workbench
Trace one IoT exchange through both models
Application data starts in the user-facing protocol. OSI splits application, presentation, and session ideas; TCP/IP usually groups them as Application.
OSI reference model
7 layers
7
Application
User-facing network services and application protocols.
HTTP
6
Presentation
Data format, compression, serialization, and often security discussion.
TLS record protection
5
Session
Dialog control and session continuity as a conceptual responsibility.
HTTP connection reuse
4
Transport
End-to-end process delivery, ports, reliability, ordering, or datagrams.
TCP segment
3
Network
Logical addressing and routing across networks.
IPv6 packet
2
Data Link
Local delivery, MAC addressing, framing, and link access.
Wi-Fi frame
1
Physical
Bits as radio symbols, optical pulses, or electrical signals.
Radio symbols
Many-to-one mapping
OSI layers 7, 6, and 5 usually map to the TCP/IP Application layer.
A model is not a packet capture.
Use the layers to reason about scope and responsibility, then inspect real headers when debugging.
TCP/IP Internet model
4 layers
A
Application
Application protocols and data representations used by the program.
HTTP + TLS
T
Transport
TCP, UDP, or transport-like services used between host processes.
TCP port 443
I
Internet
IP addressing, forwarding, ICMP, and routing between networks.
IPv6 route
L
Link / Network Access
Local network interface, MAC, and physical media details.
Wi-Fi
Protocol data unit
Payload is being prepared by the application layer
Data
JSON payload
Message body before network delivery headers are added.
Segment / datagram
TCP segment
Transport ports and reliability or datagram behavior.
Packet
IPv6 packet
Source/destination IP addresses and routing scope.
Frame / signal
Wi-Fi frame
Local link delivery plus physical transmission.
Clean teaching map: HTTP over TLS over TCP over IP.
This is the simplest case for learners: application data is protected above TCP, TCP provides ordered byte-stream delivery, IP routes packets, and the link carries frames locally.
Quick Reference: How To Read The Two Models
Useful for discussing app protocol, data format, encryption, and dialog concepts. TCP/IP usually groups these as Application.
TCP gives an ordered byte stream; UDP gives datagrams. QUIC uses UDP but implements transport and security behavior above it.
IP addressing and routing happen here. IPv6, IPv4, ICMP, and routing decisions belong in this scope.
Local delivery and signal transmission: Ethernet, Wi-Fi, IEEE 802.15.4, BLE, LoRa PHY, or another local medium.
A BLE sensor can speak GATT locally while the gateway publishes MQTT over TCP/IP upstream. That is not one continuous TCP/IP session.
Ask: is the issue local radio/link, IP routing, transport session, security negotiation, or application semantics?
Guided Task: Use This In Three Minutes
Watch the token move from Application to Transport to Internet to Link. Confirm that each lower layer adds delivery context.
Notice UDP datagrams, IPv6, 6LoWPAN adaptation, and the small MTU warning when payloads get too large.
Use the diagnosis panel to explain why modern stacks sometimes blur or cross the simple model boundaries.
Deeper Notes: Technical Boundaries And Source Links
Header sizes shown here are teaching estimates, not packet-capture truth. Real overhead depends on options, compression, link framing, retransmissions, security records, and implementation choices. The important lesson is the responsibility of each layer and the scope of each header.
ISO/IEC 7498-1:1994 OSI Basic Reference Model
ISO catalogue entry for the OSI Basic Model, explicitly a reference model rather than an implementation specification.
RFC 1122: Requirements for Internet Hosts
Primary Internet host layering reference: link, internet, transport, and application responsibilities.
RFC 8200: IPv6 Specification
Defines IPv6 packet format and Internet layer behavior.
RFC 9293: Transmission Control Protocol
Current TCP specification for reliable ordered byte-stream delivery.
RFC 768: User Datagram Protocol
Defines UDP datagram service and header structure.
RFC 8446: TLS 1.3
Application security protocol often shown near the OSI presentation concept.
RFC 9000: QUIC
Shows why QUIC mapping needs care: QUIC runs over UDP while providing transport and security functions.