INI
IoT Protocols - INI
IoT protocols are communication conventions for enabling data exchange between devices in Internet of Things environments. Centered around lightweight messaging protocols such as MQTT, CoAP, and AMQP, various protocols exist to meet different use cases and requirements, including XMPP, DDS, HTTP, and LwM2M. These protocols are designed to accommodate the characteristics of IoT devices, including bandwidth constraints, power consumption, latency, and reliability. They are widely utilized across diverse fields such as smart homes, industrial automation, smart cities, and healthcare.
IoT
protocol
MQTT
CoAP
AMQP
communication
M2M
smart devices
[item.mqtt]
code=01
slug=mqtt
name=MQTT
description=Lightweight publish-subscribe messaging protocol
architecture=Broker-based (Pub/Sub)
bestFor=["unreliable networks","remote monitoring","smart homes","industrial automation"]
fullName=Message Queuing Telemetry Transport
headerSize=2 bytes
powerConsumption=moderate
qosLevels=3
transportProtocol=TCP
[item.coap]
code=02
slug=coap
name=CoAP
description=Lightweight web transfer protocol for constrained devices
architecture=Client-Server (RESTful)
bestFor=["battery-powered devices","constrained networks","smart agriculture","LPWAN"]
fullName=Constrained Application Protocol
headerSize=4 bytes
powerConsumption=low
qosLevels=2
transportProtocol=UDP
[item.amqp]
code=03
slug=amqp
name=AMQP
description=Advanced message queuing protocol for enterprise
architecture=Broker-based (Multiple patterns)
bestFor=["enterprise integration","financial systems","healthcare","mission-critical applications"]
fullName=Advanced Message Queuing Protocol
headerSize=variable (larger)
powerConsumption=high
qosLevels=3
transportProtocol=TCP
[item.xmpp]
code=04
slug=xmpp
name=XMPP
description=XML-based real-time communication protocol
architecture=Distributed (Client-Server)
bestFor=["instant messaging","presence detection","chat applications","device management"]
fullName=Extensible Messaging and Presence Protocol
headerSize=variable (XML overhead)
powerConsumption=moderate
qosLevels=1
transportProtocol=TCP
[item.dds]
code=05
slug=dds
name=DDS
description=Middleware protocol for real-time data distribution
architecture=Brokerless (Pub/Sub)
bestFor=["industrial automation","robotics","defense systems","automotive","real-time systems"]
fullName=Data Distribution Service
headerSize=variable
powerConsumption=high
qosLevels=22
transportProtocol=UDP/TCP
[item.http-https]
code=06
slug=http-https
name=HTTP/HTTPS
description=Standard protocol for web communication
architecture=Client-Server (Request/Response)
bestFor=["web applications","device management portals","data visualization","RESTful APIs"]
fullName=HyperText Transfer Protocol / HTTP Secure
headerSize=800+ bytes
powerConsumption=high
qosLevels=1
transportProtocol=TCP
[item.lwm2m]
code=07
slug=lwm2m
name=LwM2M
description=Lightweight M2M device management protocol
architecture=Client-Server
bestFor=["device management","firmware updates","smart metering","asset tracking"]
fullName=Lightweight M2M
headerSize=4+ bytes
powerConsumption=low
qosLevels=2
transportProtocol=UDP (over CoAP)
[item.mqtt-sn]
code=08
slug=mqtt-sn
name=MQTT-SN
description=MQTT protocol for sensor networks
architecture=Broker-based (Pub/Sub)
bestFor=["sensor networks","non-IP networks","Zigbee","LoRaWAN","Bluetooth"]
fullName=MQTT for Sensor Networks
headerSize=2-5 bytes
powerConsumption=low
qosLevels=3
transportProtocol=UDP
[item.opc-ua]
code=09
slug=opc-ua
name=OPC UA
description=M2M communication protocol for industrial automation
architecture=Client-Server
bestFor=["industrial automation","process control","manufacturing","Industry 4.0"]
fullName=OPC Unified Architecture
headerSize=variable
powerConsumption=moderate
qosLevels=2
transportProtocol=TCP
[item.websocket]
code=10
slug=websocket
name=WebSocket
description=Web protocol enabling full-duplex communication
architecture=Client-Server (Full-duplex)
bestFor=["real-time streaming","chat applications","live dashboards","bidirectional communication"]
fullName=WebSocket Protocol
headerSize=2-14 bytes
powerConsumption=moderate
qosLevels=1
transportProtocol=TCP