No abstract

The Internet of Things (IoT) promotes the communication among heterogeneous entities, from small sensors to Cloud systems. However, this is realized using a wide range of communication media and data protocols, usually incompatible with each other. Thus, IoT systems tend to grow as homogeneous isolated platforms, which hardly interact. To achieve a higher degree of interoperability among disparate IoT platforms, we propose a language-based approach for communication technology integration. We build on the Jolie programming language, which allows programmers to easily make the same logic work over disparate communication stacks in a declarative, dynamic way. Jolie currently supports the main technologies from Service-Oriented Computing, such as TCP/IP, Bluetooth, and RMI at transport level, and HTTP and SOAP at application level. As technical result, we integrate in Jolie the two most adopted protocols for IoT communication, i.e., CoAP and MQTT. In this paper, we report our experience and we present high-level concepts valuable both for the general implementation of interoperable systems and for the development of other language-based solutions.

The Internet of Things (IoT) advocates for multi-layered platformsfrom edge devices to Cloud nodeswhere each layer adopts its own communication standards (media and data formats). While this freedom is optimal for in-layer communication, it puzzles cross-layer integration due to incompatibilities among standards. Also enforcing a unique communication stack within the same IoT platform is not a solution, as it leads to the current phenomenon of IoT islands, where disparate platforms hardly interact with each other. In this paper we tackle the problem of IoT cross-layer and cross-platform integration following a language-based approach. We build on the Jolie programming language, which provides uniform linguistic abstractions to exploit heterogeneous communication stacks, allowing the programmer to specify in a declarative way the desired stack, and to easily change it, even at runtime. Jolie currently supports the main technologies from Service-Oriented Computing, such as TCP/IP, Bluetooth, and RMI at transport level, and HTTP and SOAP at application level. We integrate in Jolie the two most adopted protocols for IoT communication, i.e., CoAP and MQTT. We report our experience on a case study on Cloud-based home automation, and we present high-level concepts valuable both for the general implementation of interoperable systems and for the development of other language-based solutions. 1 Introduction The Internet of Things (IoT) advocates for multi-layered software platforms, each adopting its own media protocols and data formats [1, 2, 3]. The problem of integrating layers of the same IoT platform, as well as dierent IoT vertical solutions, involves many levels of the communication stack, spanning from linklayer communication technologies, such as ZigBee and WiFi, to application-layer protocols like HTTP, CoAP [4, 5], and MQTT [6, 7], reaching the topmost layers of data-format integration [8]. Technology-wise, architects of IoT platforms can choose between two approaches at odds. The rst approach favors optimal in-layer communications, i.e., choosing media protocols and data formats best suited for the interactions happening among homogeneous elements, e.g., edge devices (connectionless protocols and binary data formats [3]), mid-tier controllers (gateways and aggre

This poster illustrates how we redesigned the CS1 course for Math undergraduates to be held online but reflecting the face-to-face (F2F) experience as much as possible. We describe the course structure and the strategies we implemented to maintain the benefits of a synchronous experience. We present the positive and negative aspects that emerged from the students' opinion analysis. We highlight what worked, what did not, and what can be improved to strengthen the perception of a F2F experience and mitigate the "presence paradox" we found: although students are enthusiastic about the online format, most would still prefer a F2F course.