Choosing the Right IoT Protocol: CoAP/LWM2M vs MQTT Explained

CoAP/LWM2M Protocol

CoAP (Constrained Application Protocol) runs over UDP and adopts a RESTful style similar to HTTP, using a minimal 4‑byte packet header. It follows a request/response model with methods identified by a Code field and supports four message types: CON (confirmable), NON (non‑confirmable), ACK (acknowledgement), and RST (reset).

Key header fields include:

VER : 2‑bit version number.

T : 2‑bit message type (CON, NON, ACK, RST).

TKL : 4‑bit token length.

Code : 8‑bit request method or response code.

Message ID : 16‑bit identifier for matching ACKs and retransmissions.

Token : optional identifier linking request and response.

Options : variable‑length fields similar to HTTP headers.

Payload : optional data carried in the message body.

LWM2M (Lightweight M2M) builds on CoAP, defining three logical entities—Server, Client, and Bootstrap Server—and four core interfaces: Bootstrap, Device Discovery & Registration, Device Management & Service Enablement, and Information Reporting.

It introduces a hierarchical object model: objects (collections of resources), instances (specific objects), and resources (individual data points). Standard objects are numbered 0‑7 (e.g., object 5 for firmware). Custom objects and resources can be defined as needed.

MQTT Protocol

MQTT (Message Queuing Telemetry Transport) operates over TCP and uses a publish/subscribe model with a broker mediating communication. Clients subscribe to topics and publish messages; the broker forwards messages to all subscribed clients.

Key MQTT message types:

CONNECT : client initiates a connection, providing credentials and optional last‑will message.

SUBSCRIBE : client requests to receive messages for specific topics.

PUBLISH : client sends a message to a topic, optionally retained for future subscribers.

MQTT defines three Quality of Service (QoS) levels:

QoS 0 : at most once delivery, possible loss.

QoS 1 : at least once delivery, possible duplicates.

QoS 2 : exactly once delivery, highest reliability.

Higher QoS improves reliability but increases network and device overhead.

Summary

CoAP/LWM2M uses UDP, is connection‑less, and follows a request/response model suitable for point‑to‑point communication with minimal overhead, making it ideal for highly constrained devices. MQTT uses TCP, maintains persistent connections, and follows a publish/subscribe model that easily supports many‑to‑many scenarios, offering flexible payload formats but requiring more resources.

Both protocols have distinct strengths; the optimal choice depends on the specific device capabilities and application requirements.