Core Networking · Study deck

IoT Protocol Layers and Selection

A protocol is an agreed set of rules for an exchange.

Packet Pete is your guide for this deck.

fundprotocolslayered
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Explain: At each boundary, write the job: move bits, share the local link, name the sender and receiver, carry the message, protect it, route it to a service, and show the final result.
  • Explain: A reference model earns its keep by naming duties a packet trace cannot show. Figure: The ITU view keeps the model compact keeps that list to four layers and two columns.
  • Explain: Devices sense or act, the network carries what they produce, service support stores and processes it and offers it through APIs, and applications turn it into something a person uses.
Layer-aware review asks what each boundary adds, removes, preserves, or translates.
Layer-aware review asks what each boundary adds, removes, preserves, or translates.
iotclass.org

Major section

Start With the Job of Each Protocol · Overview: Protocols Work as a Stack

Saying that the device is connected hides which rule or hand-off failed.

  • At each boundary, write the job: move bits, share the local link, name the sender and receiver, carry the message, protect it, route it to a service, and show the final result.
  • A gateway is a boundary device that may join unlike links or change message form.

Key terms

Reachability
Reachability is not trust, and delivery is not correct meaning.

Why it matters

That separation prevents vague decisions such as "use MQTT" or "use LoRaWAN" from hiding missing work.

A protocol stack is a set of layer agreements, not a single product choice.
A protocol stack is a set of layer agreements, not a single product choice.
iotclass.org

Major section

Practitioner: Select the Stack from Constraints

Protocol selection should start with the system behavior, not a favorite protocol name.

  • A practitioner asks what the device must send, how often, how far, under what power budget, through which gateway or service, and with what failure behavior.
  • The narrow column beside them is the part teams skip.
  • Choosing a verbose web stack because it is familiar.
  • Assuming a dashboard click means the device changed state.

Key terms

Assuming a dashboard click
Assuming a dashboard click means the device changed state.

Why it matters

Choosing a verbose web stack because it is familiar.

Choose each layer for a reason and record the handoff between layers.
Choose each layer for a reason and record the handoff between layers.
iotclass.org

Major section

Under the Hood: Boundaries Create Failure Modes

The hard part of a protocol stack is often not the protocol syntax.

  • Under the hood, every layer adds context and cost.
  • Headers, acknowledgements, retransmissions, security wrappers, and gateway buffers are useful when they serve the requirement; they are waste when they hide responsibility or exceed the link budget.
  • Each layer adds or removes facts around the data.
  • A gateway may end one set of rules and start another when it changes a protocol.
Layer-aware review asks what each boundary adds, removes, preserves, or translates.
Layer-aware review asks what each boundary adds, removes, preserves, or translates.
iotclass.org

Major section

Under the Hood: Boundaries Create Failure Modes (continued)

The layer names show where to look; they do not name an owner.

  • At each handoff, record what came in, what went out, what was checked, what state was kept, and which fault reached the next layer.
  • The message looks delivered, but command meaning, duplicate handling, or freshness is unclear.
  • Reliability assumptions break when paths are lossy, sleepy, buffered, or translated.
  • Address mapping, compression, fragmentation, or retries hide where packets are actually dropped.
Choose each layer for a reason and record the handoff between layers.
Choose each layer for a reason and record the handoff between layers.
iotclass.org

Major section

Under the Hood: Boundaries Create Failure Modes (continued)

Address plan, adaptation context, frame fit, link acknowledgement, retry count, and channel evidence.

  • Translation changes identity, time, quality, credentials, or failure visibility.
  • Common pitfall: A protocol family name is not a deployed contract.
  • Protocol Stack Review ChecklistBegin with the physical event, payload, receiver, and action the stack supports.
Reference-model boundary record across device, connectivity, edge, data, and application responsibilities
Reference-model boundary record across device, connectivity, edge, data, and application responsibilities
iotclass.org

Major section

Worked End-to-End Stack Trace: Connected Tilt Maze

It decapsulates the Internet message all the way to its control application, validates freshness and limits, then creates a new local-link message for the Arduino.

  • A fast command round trip does not prove low video latency, and smooth video does not prove that a stale motor command will be rejected.
  • The command crosses the stack more than once because the Raspberry Pi is both an Internet endpoint and a local gateway.

Why it matters

The command crosses the stack more than once because the Raspberry Pi is both an Internet endpoint and a local gateway.

iotclass.org

Major section

IoT Reference Models

A layer picture helps only when each hand-off has an owner and evidence.

  • OSI means Open Systems Interconnection, a model that separates network communication jobs.
  • TCP means a connected byte stream that tracks order and loss.
  • Telemetry means measurements and status sent from remote devices for review.
  • This runway does not choose products or prove the full system.

Why it matters

The expanded model is useful here because it prevents connectivity, processing, storage, applications, and operational work from being hidden inside one platform box.

The ITU view keeps the model compact: devices generate or act on physical-world data, networks carry it, service support prepares it, and applications use it. Management and security cut across the stack.
The ITU view keeps the model compact: devices generate or act on physical-world data, networks carry it, service support prepares it, and applications use it. Management and security cut across the stack.
iotclass.org

Major section

IoT Reference Models (continued)

Break a hand-off, delay it, repeat it, restart one part, and keep the local safe response available.

  • The deeper sections compare network models with IoT responsibility models and show how device, service, security, management, and human action fit together.
  • An IoT reference model is not a poster to memorize.
  • That shape is the argument.
Seven-level IoT reference model from physical devices to collaboration and processes
Seven-level IoT reference model from physical devices to collaboration and processes
iotclass.org

Major section

IoT Reference Models (continued)

That sequence turns a flexible deployment—where one gateway may implement several roles—into explicit contracts.

  • Each layer should explain a responsibility, an owner, and the evidence needed to know the system is still doing its job.
  • The two vertical bars beside them are what makes this model different.
  • An IoT reference model is not a product stack.
A protocol stack is a set of layer agreements, not a single product choice.
A protocol stack is a set of layer agreements, not a single product choice.
iotclass.org

Major section

IoT Reference Models (continued)

A reference model earns its keep by naming duties a packet trace cannot show. Figure: The ITU view keeps the model compact keeps that list to four layers and two columns.

  • Devices sense or act, the network carries what they produce, service support stores and processes it and offers it through APIs, and applications turn it into something a person uses.
  • A design can pass every connectivity test and still have nobody named as the owner of updates or credentials.
  • The ordered map connects technology selection to the deployment decision the message supports and exposes which failure boundaries still lack proof.
The ITU view keeps the model compact: devices generate or act on physical-world data, networks carry it, service support prepares it, and applications use it. Management and security cut across the stack.
The ITU view keeps the model compact: devices generate or act on physical-world data, networks carry it, service support prepares it, and applications use it. Management and security cut across the stack.
iotclass.org

Major section

Summary · Key Takeaway

IoT communication is a stack of agreements, not one protocol name.

  • Application, transport, network/adaptation, link, and physical layers each carry a different responsibility.
  • Protocol selection should start from payload meaning, freshness, delivery behavior, range, power, gateway handoff, and operational ownership.
  • Header overhead, retransmissions, security wrappers, and fragmentation are design costs that should be visible in the decision record.
End-to-end protocol sequence for an Internet-connected tilt maze from tablet orientation through Raspberry Pi and Arduino control to return video.
End-to-end protocol sequence for an Internet-connected tilt maze from tablet orientation through Raspberry Pi and Arduino control to return video.
iotclass.org

Deck summary

Key takeaways

Saying that the device is connected hides which rule or hand-off failed.

  • Protocol selection should start with the system behavior, not a favorite protocol name.
  • The hard part of a protocol stack is often not the protocol syntax.
  • The layer names show where to look; they do not name an owner.
  • Address plan, adaptation context, frame fit, link acknowledgement, retry count, and channel evidence.
iotclass.org

Retrieval practice

Recall check 1 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q1A team says, "We chose MQTT, so the network architecture is solved." What is the best response?

AMQTT replaces the need to choose transport, addressing, link behavior, gateways, or operations.
BAll IoT systems should use the same protocol stack after a broker is available.
CMQTT helps app messaging; transport, addressing, link, security, gateways, and operations still need evidence.
DLayering matters only in textbook diagrams, not deployed IoT systems with gateways.
Show answer

Answer: C A stack choice is credible when the team names application meaning, transport behavior, addressing, link limits, security, gateway handoff, and layer evidence.

iotclass.org

Retrieval practice

Recall check 2 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q2A battery sensor sends a small reading only occasionally through a local gateway. Which protocol-selection habit is strongest?

ASelect a familiar web stack before checking the sensor and gateway constraints.
BIgnore gateway handoff because protocol translation cannot change meaning.
CSelect peak bandwidth because maximum link capacity is the decisive fit for the planned readings.
DStart with device constraints and verify the gateway handoff contract.
Show answer

Answer: D Constrained IoT stack selection should be driven by evidence about payload, freshness, link behavior, gateway handoff, and operations.

iotclass.org

Retrieval practice

Recall check 3 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q3A gateway receives constrained-device messages on one side and publishes them to a cloud broker on the other. Which review record is most important?

AA cloud broker connection record with gateway publish topics and endpoint settings.
BA radio link qualification record showing the gateway receives representative field messages.
CA dashboard trace showing the published device values after gateway translation.
DA boundary record for identity, time, payload, buffering, stale data, credentials, and monitoring.
Show answer

Answer: D Protocol-stack correctness depends on evidence at the boundaries where layers or gateways add, remove, or translate context.

iotclass.org

Retrieval practice

Recall check 4 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q4Why do IoT teams use IoT reference models in addition to OSI or TCP/IP?

ABecause they add a deployment-responsibility map around networking mechanics.
BBecause IoT reference models replace packet, port, address, and routing analysis in architecture reviews.
CBecause they provide a common firmware module layout for device implementations.
DBecause dashboards are the only architecture layer needing ownership, security, and evidence.
Show answer

Answer: A OSI and TCP/IP are still useful, but IoT reference models add the functional responsibilities that sit around the communication path.

iotclass.org

Retrieval practice

Recall check 5 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q5A building gateway receives meter readings, rejects malformed payloads, summarizes normal readings locally, and sends alarms immediately to an operations service. What is the most useful reference-model review action?

APlace the gateway only in the physical device layer because it sits near sensors.
BSkip the edge-processing review because summaries are smaller than raw readings.
CTreat the application dashboard as proof that all lower layers are correct.
DMap the gateway across connectivity, edge processing, data services, and operations evidence
Show answer

Answer: D A single product can span several model areas.

iotclass.org

Retrieval practice

Recall check 6 of 6

Packet Pete says: answer from memory, then check your reasoning.

Q6A review document labels an IoT service-support layer as equivalent to the OSI session layer because both use the word service. What is the best correction?

AMap every IoT reference layer one-to-one to an OSI layer with the same name.
BRemove OSI and TCP/IP from review because newer IoT models replace them.
CMove all service-support work into dashboards to keep lower layers simple.
DCompare the layers' functions and boundaries; similar names do not imply equivalence.
Show answer

Answer: D Similar words across models can hide different meanings.

iotclass.org

Print reference

Answers 1 of 2

Answer key.

  1. C · A stack choice is credible when the team names application meaning, transport behavior, addressing, link limits, security, gateway handoff, and layer evidence.
  2. D · Constrained IoT stack selection should be driven by evidence about payload, freshness, link behavior, gateway handoff, and operations.
  3. D · Protocol-stack correctness depends on evidence at the boundaries where layers or gateways add, remove, or translate context.
  4. A · OSI and TCP/IP are still useful, but IoT reference models add the functional responsibilities that sit around the communication path.
iotclass.org

Print reference

Answers 2 of 2

Answer key.

  1. D · A single product can span several model areas.
  2. D · Similar words across models can hide different meanings.
iotclass.org