Don't get lost in the IoT Protocol jungle!
Learn the difference between the various IoT protocols
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.
ApplicationCoAP, Neul, MQTT, LWM2M
NetworkNB-IoT, LTE-M, LoRaWAN
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.
126.96.36.199 188.8.131.52 184.108.40.206 NO IP
NO IP 220.127.116.11 18.104.22.168 22.214.171.124
126.96.36.199 NO IP 188.8.131.52 184.108.40.206
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.
User Datagram Protocol
UDP is a simple datagram-based transport layer protocol. It offers unreliable, non-connection-oriented data messaging.
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.
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.
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.
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.