Combination of IoT framework with liquid software

Abstract

To mass-deploy and manage IoT applications, an IoT framework was developed by TUT. The capabilities of this framework have been expanded to include liquid functionalities. To limit the extra work an IoT programmer has to add to their IoT applications, the liquid functionalities were added to the application non-specific code rather than the application specific code. To limit power consumption, a polling technique was introduced to check for changes in the state of the applications. To limit the data communication, two ways were created to communicate state changes between applications. One uses a peer-to-peer topology to communicate and the other a master-slave topology. Synchronization collisions are also solved using timestamps.

A network of four IoT devices was used to test the speed of the liquid functionalities as well as the amount of communication between the devices when synchronized. It was found that cloning takes marginally longer than migrating or forking, that liquid transfer speeds are greatly influenced by the presence of a resources folder and that communication between devices works as predicted. To limit power consumption when initiating a liquid transfer, a new way to initiate a liquid transfer has been discussed. It migrates the power to the RR rather than the IoT device. Data communication can be limited by saving all synchronized applications on the device instead of using a syncID.