IoT Protocol Selection Guide

Build a defensible shortlist of connectivity and application protocols from IoT requirements

Interactive protocol selection workbench that separates radio/connectivity choices from application-layer messaging choices

Protocol Selection Connectivity First Interactive Guide

IoT Protocol Selection Workbench

Build a shortlist from requirements instead of memorizing a single protocol table. The selector separates the connectivity layer from the application messaging layer so MQTT is not confused with a radio link.

LoRaWAN Top connectivity option

92 / 100 Fit score for current requirements

CoAP / LwM2M Application-layer fit

Duty-cycle check Main validation warning

Protocol Selection Decision Path

What

Protocol selection maps requirements to a shortlist of communication choices, then validates the shortlist with real constraints.

Why

A protocol that is excellent for long battery life may be poor for low latency, high data rate, or direct cloud access.

Try First

Switch from Soil sensors to Snapshot cameras. Notice how the result moves from low-power wide-area to high-throughput local IP.

Notice

MQTT, CoAP, and HTTP are application choices. They still need a connectivity path such as cellular, Wi-Fi, Ethernet, or a gateway.

Scenario

Preset Soil sensors Smart meters Asset trackers Building sensors Wearable beacon Snapshot cameras

Requirements

Coverage area Nearby personal device Room or building Campus or site Farm or city zone Nationwide cellular area Power budget Coin cell or years Battery months Rechargeable days/weeks Mains or large battery Data need Tiny telemetry under 10 Kbps Low data under 250 Kbps Medium data up to 2 Mbps High data above 2 Mbps Latency tolerance Minutes are acceptable Seconds are acceptable Sub-second response Near real-time Network shape Local gateway is acceptable Direct cellular network Local mesh network Phone or nearby hub Existing IP network Wired infrastructure Mobility Fixed devices Occasionally moving Mobile assets

This selector creates a first shortlist. Final engineering also checks regional rules, payload limits, security, gateway density, carrier plans, interference, certification, and total cost.

Decision flow

Soil sensors: long range, very low power, tiny telemetry, relaxed latency, gateway acceptable.

Step 1: Coverage

Requirement path

Shortlist ranking

ConnectivityLoRaWAN: long range, low power, gateway based

ApplicationCoAP / LwM2M for constrained telemetry and device management

Best evidenceCoverage and power requirements dominate this selection.

Watch outCheck duty cycle, payload size, downlink expectations, and gateway coverage.

LoRaWAN Best when tiny messages need long range and very low battery drain through a gateway.

NB-IoT A credible alternative when cellular coverage and operator service are available.

CoAP / LwM2M Use for constrained request/response telemetry and managed device operations.

Current explanation

Start with coverage and power before choosing the messaging layer. Connectivity decides whether bits can reach a network. MQTT, CoAP, and HTTP decide how application messages behave after a link exists.

1. Coverage

Short, building, campus, wide-area, and nationwide needs remove different choices.

2. Power

Coin-cell devices prefer low duty cycle links; mains-powered devices can use richer networks.

3. Data

Camera-sized payloads and tiny telemetry belong to very different protocol families.

4. Latency

Relaxed telemetry can wait; control loops and live media need fast response.

5. Topology

A gateway, phone, mesh, cellular network, or existing IP network changes the answer.

6. Validate

Use the shortlist for testing, cost estimates, security design, and coverage planning.

Learning Support

Minimum Background

A connectivity protocol moves bits over a physical network. An application protocol structures messages after the device has a path.

Mental Model

Pick the road first, then the parcel format. LoRaWAN, Wi-Fi, BLE, and cellular are roads. MQTT and CoAP are parcel rules.

Design Meaning

The best answer is a defensible shortlist, not a magic winner. Real deployments must validate coverage, cost, security, and operations.

Quick Reference

LoRaWAN

Long range and very low power for small, infrequent messages. Watch duty cycle, payload limits, gateways, and downlink limits.

NB-IoT / LTE-M

Cellular IoT for wide coverage. NB-IoT suits static low data; LTE-M is better for mobility and lower latency.

Wi-Fi / Ethernet

High throughput and low latency where power and infrastructure are available. Good for cameras, gateways, and local IP systems.

BLE

Very low power for nearby phones, hubs, tags, wearables, and commissioning. Range and always-on cloud access need a gateway.

Zigbee / Thread

Low-power local mesh for buildings. Thread uses IPv6 and is common in Matter-style smart building designs.

MQTT / CoAP / HTTP

Application protocols, not radio links. MQTT is broker-based over TCP. CoAP is lightweight REST over UDP. HTTP is simple but heavier.

Guided Practice

Coverage Stress

Set coverage to nationwide. Local mesh and BLE should fall, while cellular options rise.

Power Stress

Move from coin-cell to mains. Wi-Fi and Ethernet become more realistic because energy is less constrained.

Data Stress

Raise data need to high. LoRaWAN and Zigbee become poor fits even if range or power looked attractive.

Latency Stress

Choose near real-time. Relaxed LPWAN choices lose ground because response time matters.

Layer Check

When the top application recommendation changes, ask whether it runs on the chosen connectivity path.

Validation Check

Use the top two connectivity choices for field tests, pricing, security design, and maintenance planning.

Bandwidth Calculator Estimate average, peak, and daily data before choosing protocol families. Protocol Comparison Simulator Compare shortlist candidates side-by-side after this first pass. Protocol Overhead Calculator Check how headers and framing affect small IoT messages.