Arrow MQTT protocol Handling

Any protocol promise of Arrow has no exception for MQTT protocol. Arrow pairs knows how to process MQTT packets and transfer based on the rule set administrators build.

Devices that generates MQTT based data are known as Publishers. They require a message collector to send the generated data, later to be collected by subscribers who are basically data consumers. Data used for monitoring, telemetry, reporting, legal issues and so on. Collectors in MQTT environments are called Brokers. Arrow Guardian is able to work as an MQTT broker, to collect data for MQTT topics from each receivers. Arrow provides a certificate based secure MQTT connection to each publisher. The certificate is built in, device specific and can be downloaded from Guardian user interface. As long as the MQTT service is licensed and enabled, any publisher can send their topic specific messages to Arrow.

Guardian does store any messages, and sends out to its sister Postman, from the secure, one-way fiber connection. Transfer of the data is part of the reception flow, so information has not to be kept waiting for any process, thus limiting transfer latency to minimum.

Postman acts as MQTT Publisher toward outer world. Upon Postman receiving the messages, it again sends out the data to an upstream broker defined from the user interface. It is possible to define a different broker for each topic. Each mapping creates a new publisher for the selected topic. Broker parameters including upstream security certificates can be configured from Postman user interface.

Below is a descriptive illustration of how Arrow MQTT flow works: