A Cost-Effective Method to Keep Availability of Many Cloud-Connected Devices

Abstract

In the case of a cloud-based remote control system that enables users to control cloud-connected devices from anywhere at any time, costs tend to increase in proportion to the number of devices. Most of the costs are derived from a message broker, a key component of the system that keeps connections from devices and relays messages between users and devices. In this paper, we analyze the costs of the message broker under a typical remote-control workload and reveal that keepalive communication costs account for a non-negligible percentage of the total. Then, we present a novel method to reduce the costs. By using the message broker as an echo back server for NAT timeout measurements initiated from devices, the method allows each device to extend the keep-alive interval adaptively by itself while keeping availability of devices and without customizing the existing message broker. The method also keeps extra resource consumption caused by the measurements under control. Finally, we evaluate our proposal on a public cloud and confirm its cost-effectiveness quantitatively.

La Búsqueda de Interacción Semántica en la Web de las Cosas: Una Revisión

“…Finalmente, las tecnologías utilizadas por los trabajos recientes para la implementación de la interacción semántica entre objetos se pueden resumir en: middlewares orientados a servicios de sensores [15], middlewares orientados a microservicios [16], arquitecturas orientadas a eventos [17], desarrollo de agentes inteligentes para objetos inteligentes [18] y basados en ontologías y mensajes en redes sociales [19].…”

Towards Efficient Integration of Blockchain for IoT Security: The Case Study of IoT Remote Access

“…With the embedded public key, IoT devices can initiate a secure session towards the endpoint right after it boots up and maintain the session with heartbeat packets. This method enables indirect access through the relay server [4]. Since the session is proactively launched by the IoT device located behind the NAT, access requests encapsulated in the response packets can freely pass through the NAT and firewall, which is dubbed as "piggybacking."…”