36  Layered Models Resources

In 60 Seconds

This resource chapter provides supplementary learning materials for layered network models, including subnet calculators, OUI lookup tools, protocol analyzers, video tutorials on the OSI and TCP/IP stacks, and AI-generated visual galleries for different learning styles.

36.1 Learning Objectives

By the end of this chapter, you will be able to:

  • Apply reference tools: Use subnet calculators, OUI lookups, and protocol analyzers to solve real networking problems
  • Analyze supplementary videos: Extract key concepts from OSI/TCP-IP tutorials and apply them to IoT scenarios
  • Select visual references: Identify AI-generated diagrams that best clarify specific layered model concepts
  • Evaluate next steps: Differentiate advanced topics building on layered models and construct a personal study path

36.2 Prerequisites

Required Chapters:

Estimated Time: 10 minutes (browsing resources)

How to use this chapter:

  1. Videos: Watch during focused study time (30-60 min sessions)
  2. Interactive tools: Bookmark for reference during practical work
  3. Visual galleries: Review when preparing for exams or refreshing concepts

Learning tip: Different resources suit different learning styles. If you learn better from videos, start there. If you prefer hands-on practice, jump to the interactive tools.

“There are so many ways to learn about network layers!” said Sammy the Sensor excitedly. “Videos, tools, quizzes – where do I start?”

“Everyone learns differently,” Max the Microcontroller explained. “If you like watching and listening, check out the video tutorials first. They walk you through how OSI and TCP/IP work with real traffic examples. If you are more hands-on, jump straight to the subnet calculators and protocol analyzers.”

Lila the LED suggested, “Try the interactive tools when you are actually working on a project. Bookmark the OUI lookup tool – you can paste in any device’s MAC address and find out who manufactured it. It is like detective work for IoT devices!”

“And do not forget the quizzes,” added Bella the Battery. “After watching videos or playing with tools, test yourself to see what stuck. The best strategy is to mix it up – watch a video, then try a tool, then take a quiz. Your brain remembers things better when you learn them in different ways!”

36.3 Cross-Hub Connections

Explore Related Learning Resources
  • Knowledge Gaps Hub: Common misconceptions about OSI layers, encapsulation overhead, and IPv4 vs IPv6
  • Quizzes Hub: Test your understanding with networking fundamentals quizzes covering layer mapping and addressing
  • Simulations Hub: Interactive network topology visualizer demonstrating protocol stacking in action
  • Videos Hub: Visual walkthroughs of encapsulation, ARP operation, and IPv6 addressing

Why This Matters: Understanding layered models is the foundation for all networking knowledge. The hubs provide alternative learning modalities to reinforce these critical concepts through visual, interactive, and self-assessment approaches.

36.4 Video Resources

OSI and TCP/IP in Practice (Part 1)
OSI and TCP/IP in Practice (Part 1)
From Lesson 4 — layering concepts with real traffic examples.
OSI and TCP/IP in Practice (Part 2)
OSI and TCP/IP in Practice (Part 2)
From Lesson 4 — protocols across layers and encapsulation.

36.4.1 Additional Video Tutorials

36.5 Interactive Tools

Bookmark These Tools

Subnet Calculators:

Address Lookups:

Hands-On Practice Environments:

Quick Knowledge Check: Protocol Selection

36.7 Additional Visual References

Side-by-side comparison of OSI 7-layer and TCP/IP 4-layer models showing how OSI layers map to TCP/IP layers, with Application, Presentation, and Session combining into TCP/IP Application layer

OSI TCP/IP Comparison

Understanding how OSI and TCP/IP models relate helps bridge theoretical networking knowledge with practical protocol implementation.

TCP/IP 4-layer stack showing Application layer protocols, Transport layer with TCP and UDP, Internet layer with IP, and Network Access layer with various link technologies

TCP/IP Stack

The TCP/IP model provides the practical framework used in real-world networks, organizing protocols into four functional layers.

OSI model adapted for IoT showing how each layer applies to Internet of Things devices, with emphasis on constrained device considerations at each layer

OSI Model IoT

The OSI model applied to IoT highlights unique considerations for constrained devices, particularly at the lower layers where power efficiency and bandwidth limitations matter most.

36.8 Match the Concepts

36.9 Order the Steps

36.10 Key Takeaways

The complete layered models review has covered:

  • Standards and protocols enable global interoperability across diverse systems
  • OSI model (7 layers) is theoretical framework; TCP/IP (4 layers) is practical implementation
  • Layering enables abstraction, modularity, and independent development
  • Encapsulation adds headers at each layer; decapsulation removes them
  • IoT reference models address unique IoT challenges (edge processing, scale, resource constraints)
  • MAC addresses (48-bit) identify hardware at Layer 2 (local delivery)
  • IP addresses (32-bit IPv4, 128-bit IPv6) enable Layer 3 routing
  • Subnet masks divide IP addresses into network and host portions
  • IPv6 provides abundant addresses for IoT’s billions of devices
  • ARP maps IP addresses to MAC addresses for local frame delivery

36.11 Worked Example: Protocol Efficiency for Battery-Powered Sensors

Scenario: You need to choose between HTTP/JSON and CoAP/CBOR for a battery-powered soil moisture sensor. Compare the protocol efficiency.

Given:

  • Payload: Temperature (23.5 C), humidity (65%), battery (3.7 V)
  • Transmission frequency: Every 10 minutes (144 transmissions per day)
  • Battery capacity: 2,000 mAh at 3.7 V
  • Radio power: 100 mW during transmission
  • Data rate: 160 bits/s (20 bytes/s) – typical for LPWAN

Option 1: HTTP POST with JSON over TCP/IP

POST /sensors/data HTTP/1.1
Host: api.example.com
Content-Type: application/json
Content-Length: 58

{"temp":23.5,"humidity":65,"battery":3.7,"id":"sensor01"}
  • Application payload: 58 bytes (JSON)
  • HTTP headers: ~180 bytes
  • TCP header: 20 bytes
  • IP header: 20 bytes
  • Total: 278 bytes per transmission

Option 2: CoAP with CBOR over UDP/IP

CoAP POST coap://api.example.com/sensors/data
CBOR: A4 64 74 65 6D 70 FA 41 BC 00 00 ... (binary)
  • Application payload: 24 bytes (CBOR binary)
  • CoAP header: 4 bytes
  • UDP header: 8 bytes
  • IP header: 20 bytes
  • Total: 56 bytes per transmission

Efficiency Calculation:

Metric HTTP/JSON CoAP/CBOR Improvement
Bytes per transmission 278 56 5x smaller
Transmissions per day 144 144 Same
Daily data transmitted 40,032 bytes 8,064 bytes 5x reduction
Time per transmission (at 20 bytes/s) 13.9 s 2.8 s 5x faster
Energy per transmission (100 mW x time) 1.39 J 0.28 J 5x less energy
Energy per day (x 144 transmissions) 200.2 J (55.6 mWh) 40.3 J (11.2 mWh) 5x less energy
Battery life (7,400 mWh capacity) ~133 days ~661 days 5x longer

Key Insight: Protocol overhead directly impacts battery life. CoAP/CBOR’s 5x efficiency improvement translates to nearly 2 years of battery life versus about 4 months with HTTP/JSON – a critical difference for deployed IoT sensors.

Decision: Use CoAP/CBOR for battery-powered sensors. Use HTTP/JSON only when mains-powered or when web compatibility is mandatory.

For a battery-powered sensor transmitting every 10 minutes with a 2,000 mAh battery at 3.7 V:

HTTP/JSON Energy Calculation: $ = 278, $ $ = = 13.9, $ $ = 100, , = 1{,}390, = 1.39, $ $ = 1.39, = 200.2, = 55.6, $ $ = 2{,}000, , = 7{,}400, $ $ = , $

CoAP/CBOR Energy Calculation: $ = 56, $ $ = = 2.8, $ $ = 100, , = 280, = 0.28, $ $ = 0.28, = 40.3, = 11.2, $ $ = , (,) $

The 5x reduction in bytes transmitted directly translates to a 5x increase in battery life – from about 4 months to nearly 2 years – making CoAP/CBOR the clear choice for battery-constrained IoT deployments.

Try It: Protocol Efficiency Calculator

Adjust the parameters below to see how protocol choice affects battery life for your IoT sensor deployment.

Common Pitfalls

Reading RFC documents or textbook chapters passively does not consolidate understanding. Fix: after reading each resource, write a one-paragraph summary in your own words and identify one concept that was unclear.

Tutorials simplify concepts to make them approachable, sometimes at the cost of accuracy. Fix: supplement tutorials with at least one primary source (RFC or IEEE standard) for each protocol you study.

Returning to resources you have already read without knowing it wastes limited study time. Fix: maintain a simple log of resources reviewed with the date and a brief note about the main concept learned.

36.12 What’s Next

The layered model and addressing foundations covered in this chapter connect directly to the following topics. Work through them in order or jump to the area most relevant to your current project.

Topic Chapter Description
OSI and TCP/IP Comparison Layered Models Comparison Side-by-side analysis of the OSI 7-layer and TCP/IP 4-layer models with IoT protocol mapping
Encapsulation and PDUs Encapsulation and Protocol Data Units How headers are added at each layer and how PDU naming (segment, packet, frame) follows the stack
Routing Fundamentals Routing Fundamentals How Layer 3 routers use routing tables and algorithms to forward datagrams across IoT networks
Transport Layer Protocols Transport Fundamentals TCP reliability versus UDP efficiency: selecting the right transport for constrained IoT devices
Wired Communication Wired Communication Protocols UART, SPI, and I2C protocols at the Data Link and Physical layers for sensor-to-microcontroller links
LoRaWAN Architecture LoRaWAN Overview How LoRa physical layer, LoRaWAN MAC layer, and network server implement the layered model for LPWAN