The toolchain has a management layer in the cloud that is used to manage sensors’ configuration (e.g. sampling frequency). Hence, with some simple operations, the user can decide which sensor has to return its measures and at which frequency. This, in terms of time, is really efficient because the user does not have to “manually” add this information in the configuration files of each sensor and neither re-program the microcontroller to get the actual data.
The tool at the backend manages these operations, reducing the time requested for a single operation. This backend system is based on HTTPS protocol, allowing to easily communicate with each sensor that has subscribed to a specific topic where the messages arrive. The connection between the gateway and backend can also be based on MQTT. In doing so, it can communicate with many sensors at the same time, instead of sending one message to each one of them individually. Hence reducing the response time of the system. In fact, without this tool,the user would need to program the microcontroller to read the data from a specific sensor. Moreover, the user would need to manually set-up the communication interface between the data provider and consumer, which is being automatically orchestrated now. This manual process, taking into account all of the sensors individually, would be time-consuming and possibly frustrating.