Resource design in federated sensor networks using RELOAD/CoAP overlay architectures

Rodrı́gues, L.; Guerreiro, Joel; Correia, N.

doi:10.1016/j.comcom.2021.07.019

Cited by 1 publication

(1 citation statement)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Then, following this CoAP-oriented approach, each sensor equipping a physical LoRaWAN end node will be represented as a virtual CoAP resource attached to its own vEN, thus allowing external CoAPenabled entities to virtually interact with the (physical) LoRaWAN end nodes. In detail, CoAP has been chosen thanks to its light traffic requirements (e.g., being based on UDP instead of TCP) and native support to service and resource discovery mechanisms [34]- [36] (even if requiring additional information descriptors [37]), as well as to increase the number of application protocols (e.g., the traditional HTTP and MQTT protocols [38]) able to cooperate with the LoRaWAN's AS. This enables communication heterogeneity in several IoT scenarios.…”

Section: Container-based Virtualization Architecturementioning

confidence: 99%

LoRa meets IP: a Container-based Architecture to Virtualize LoRaWAN End Nodes

Cilfone,

Davoli,

Ferrari

2024

IEEE Trans. on Mobile Comput.

View full text Add to dashboard Cite

In this work, a container-based architecture for the integration of Long Range Wide Area Network (LoRaWAN) end nodes-e.g., used to monitor industrial machines or mobile entities in specific environments-with Internet Protocol (IP)-based networks is proposed and its performance is investigated. To this end, we exploit the native service and resource discovery support of the Constrained Application Protocol (CoAP), as well as its light traffic requirements, owing to its use of User Datagram Protocol (UDP) rather than Transmission Control Protocol (TCP). This approach (i) adapts transparently (with no impact) to both private and public LoRaWAN networks, (ii) enables seamless interaction between LoRaWAN-based and CoAP-based nodes, through a logical "virtualization" of LoRaWAN nodes at server side, and (iii) enables routing among LoRaWAN end nodes, overcoming LoRaWAN's absence of inter-node communication and lack of compliance (at the end nodes' side) with IP. Two virtualization approaches are proposed: (i) virtualization of a single end node (represented as a CoAP server) per container and (ii) virtualization of multiple end nodes (as CoAP servers) per container. Finally, deployments of the proposed virtualization architectures, using both a laptop and an Internet of Things (IoT) device (e.g., a Raspberry Pi), are considered, highlighting how the best solution relies on the use of several containers, with more than one CoAP server per container.

show abstract

Section: Container-based Virtualization Architecturementioning

confidence: 99%