Client helps IoT communications
Embedded devices joining the IoT exchange data with other devices using a network can communicate using wired or wireless connections, anywhere, at any time, using Segger’s message queuing telemetry transport (MQTT) client.
The lightweight communication protocol is suited for constrained environments such as IoT and M2M contexts. It fit onto resource-constrained embedded processors, says the company.
All devices (clients) designed to communicate with each other address the same broker. The broker preserves messages it receives by the sending (publisher) devices and forwards them to one or more receiver (subscriber) devices.
Messages are sent from the publisher to the broker using a topic. When the broker receives a published message, it forwards it to all subscribers as a broadcast. A subscription to a topic defines the messages that the subscribing MQTT client receives from the broker. The company’s client implementation of the MQTT protocol implements version 3.1.1 of the OASIS (Organization for the Advancement of Structured Information Standards) and talks to any compliant MQTT broker.
MQTT runs over TCP/IP and can operate on top of embOS/IP and any other IP stack using sockets.
To establish secure communication between publisher and broker and subscriber, the Transport Layer Security can be implemented by using the company’s emSSL.
The MQTT client is written in C and portable to run on sensor nodes, tablets, or PCs. A trial is available for download.