Don't get lost in the IoT Protocol jungle!

Learn the difference between the various IoT protocols

Protocol Adapters

Navigate IoT protocols like a pro!

When developing an IoT solution there a plenty of options among each layer, which sometimes can be overwhelming to choose from. Don’t worry, we support a lot of different protocols out of the box.

IPv4, Non-IP
Network layer
The physical network your device connects to.
We support NB-IoT, LTE-M and LoRaWAN
Internet layer
Specify how routers transmit data packets between source and destination.
We support IP and Non-IP
Transport layer
Focuses on end-to-end communication.
We support TCP and UDP
Application layer
Interface between what the IoT device is doing and data handoff to the network.
We support CoAP, Neul, LWM2M, MQTT

IP or not to IP? that is the question

For NB-IoT, it is advised to use non-IP based data transfer wherever feasible as it further minimizes the volume of data delivered over the air interface (since IP overhead is saved). The core network then uses IP to relay the device data to the application. Data can only be delivered to one IP address (server), improving the device’s security by lowering the chance of fraud.

Lean more about Non-IP NO IP


Transport Layer
Transportation Layer Protocols

Make your NET WORK for you

The selected protocol has a major impact on your battery life and reliability of message delivery.


Transmission Control Protocol

A connection oriented protocol that specifies the format of data and confirmation information communicated between devices. The protocol is divided into three stages: connection formation, data transport, and connection closure.

Reliable communication due to message acknowledgement
Message loss unlikely
Heavyweight protocol due to high protocol overhead
Not the most battery-efficient protocol


User Datagram Protocol

UDP is a simple datagram-based transport layer protocol. It offers unreliable, non-connection-oriented data messaging.

Fast transmission speed
Lightweight protocol - saves battery and minimizes payload sizes
Best protocol when packet loss during data transmission is acceptable
No guaranteed transmission of data (no acknowledgement)
No message sequencing or flow control
Application Layer

Making bad decisions is part of life

but they don't need to be

Let is us help you to find the perfect application layer protocol for your IoT solution. And the best thing: we support all of them. So if your change your mind latter, that’s no problem.


Constrained Application Protocol

Transportation Layer: UDP

CoAP is a message-based protocol (client-server) and was designed to enable communications between constrained IoT devices. It is very similar to HTTP protocol. However, CoAP is in binary format, which is more compact than HTTP.

Lightweight and low power consumption
Reliable (re-)transmission
Supports asynchronous communication
Messages: confirmable or non-confirmable
Due to packet size, messages are rarely lost
Increased processing time due to acknowledging each message delivery
Not the best choice for devices with constrained environment


Message Queue Telemetry Transport

Transportation Layer: TCP

Operates in a publish/subscribe mode and differentiates the client that transmits the message (publisher) from the client who receives the message (subscriber). The publisher does not need to contact the subscriber directly. One-to-many communication to publishers and subscribers at the same time is possible.

Runs with low-power CPUs and RAM
Effective for minimizing data loss
Update requests are unnecessary, which reduces traffic and processing
Different quality of service levels: single handshake to acknowledgement demand
Not battery-efficient due to communication method


Lightweight M2M

Transportation Layer: UDP, Non-IP, TCP

LWM2M was created as a standard (based on CoAP) to decrease power and data consumption for low-power devices with limited computing power and bandwidth. It is not just intended for messaging but also incorporates device management features. LwM2M employs a defined data model for information transmission between device and platform that is unrelated to the device manufacturer.

Very low power consumption
Low bandwith usage
Standardized resource structure
Standardized device management processes
Complex implementation for simple use cases