Nothing Special   »   [go: up one dir, main page]

You seem to have javascript disabled. Please note that many of the page functionalities won't work as expected without javascript enabled.
 
 
Sign in to use this feature.

Years

Between: -

Subjects

remove_circle_outline
remove_circle_outline
remove_circle_outline
remove_circle_outline

Journals

Article Types

Countries / Regions

Search Results (10)

Search Parameters:
Keywords = AMQP

Order results
Result details
Results per page
Select all
Export citation of selected articles as:
18 pages, 3011 KiB  
Article
Performance Evaluation and Cyberattack Mitigation in a Blockchain-Enabled Peer-to-Peer Energy Trading Framework
by Nihar Ranjan Pradhan, Akhilendra Pratap Singh, S. V. Sudha, K Hemanth Kumar Reddy and Diptendu Sinha Roy
Sensors 2023, 23(2), 670; https://doi.org/10.3390/s23020670 - 6 Jan 2023
Cited by 6 | Viewed by 2396
Abstract
With the electric power grid experiencing a rapid shift to the smart grid paradigm over a deregulated energy market, Internet of Things (IoT)-based solutions are gaining prominence, and innovative peer-to-peer (P2P) energy trading at a micro level is being deployed. Such advancement, however, [...] Read more.
With the electric power grid experiencing a rapid shift to the smart grid paradigm over a deregulated energy market, Internet of Things (IoT)-based solutions are gaining prominence, and innovative peer-to-peer (P2P) energy trading at a micro level is being deployed. Such advancement, however, leaves traditional security models vulnerable and paves the path for blockchain, a distributed ledger technology (DLT), with its decentralized, open, and transparency characteristics as a viable alternative. However, due to deregulation in energy trading markets, most of the prototype resilience regarding cybersecurity attack, performance and scalability of transaction broadcasting, and its direct impact on overall performances and attacks are required to be supported, which becomes a performance bottleneck with existing blockchain solutions such as Hyperledger, Ethereum, and so on. In this paper, we design a novel permissioned Corda framework for P2P energy trading peers that not only mitigates a new class of cyberattacks, i.e., delay trading (or discard), but also disseminates the transactions in a optimized propagation time, resulting in a fair transaction distribution. Sharing transactions in a permissioned R3 Corda blockchain framework is handled by the Advanced Message Queuing Protocol (AMQP) and transport layer security (TLS). The unique contribution of this paper lies in the use of an optimized CPU and JVM heap memory scenario analysis with P2P metric in addition to a far more realistic multihosted testbed for the performance analysis. The average latencies measured are 22 ms and 51 ms for sending and receiving messages. We compare the throughput by varying different types of flow such as energy request, request + pay, transfer, multiple notary, sender, receiver, and single notary. In the proposed framework, request is an energy asset that is based on payment state and contract in the P2P energy trading module, so in request flow, only one node with no notary appears on the vault of the node.Energy request + pay flow interaction deals with two nodes, such as producer and consumer, to deal with request and transfer of asset ownership with the help of a notary. Request + repeated pay flow request, on node A and repeatedly transfers a fraction of energy asset state to another node, B, through a notary. Full article
(This article belongs to the Special Issue Security, Privacy and Attack in Next Generation Networks)
Show Figures

Figure 1

Figure 1
<p>Issues in the traditional energy trading system.</p>
Full article ">Figure 2
<p>Proposed framework for P2P energy trading.</p>
Full article ">Figure 3
<p>Energy request, transfer, and payment flow sequence in the proposed P2P energy trading framework with participant signatures.</p>
Full article ">Figure 4
<p>Transaction explorer.</p>
Full article ">Figure 5
<p>Vault query explorer.</p>
Full article ">Figure 6
<p>CPU and JVM heap memory usage at time t1 = 15 min.</p>
Full article ">Figure 7
<p>CPU and JVM heap memory usage at time t2 = 60 min.</p>
Full article ">Figure 8
<p>Overhaul CPU performance.</p>
Full article ">Figure 9
<p>Receive and send latency histogram.</p>
Full article ">Figure 10
<p>Send and receive message rate.</p>
Full article ">
21 pages, 821 KiB  
Article
Assertive, Selective, Scalable IoT-Based Warning System
by Ion-Dorinel Filip, Cristian-Mihai Iliescu and Florin Pop
Sensors 2022, 22(3), 1015; https://doi.org/10.3390/s22031015 - 28 Jan 2022
Cited by 5 | Viewed by 3093
Abstract
With the evolution of technology, developed systems have become more complex and faster. Thirty years ago, there were no protocols or databases dedicated to developing and implementing IoT projects. We currently have protocols such as MQTT, AMQP, CoAP, and databases such as InfluxDB. [...] Read more.
With the evolution of technology, developed systems have become more complex and faster. Thirty years ago, there were no protocols or databases dedicated to developing and implementing IoT projects. We currently have protocols such as MQTT, AMQP, CoAP, and databases such as InfluxDB. They are built to support a multitude of data from an IoT system and scale very well with the system. This paper presents the design and implementation of an IoT alert system that uses MQTT and InfluxDB to collect and store data. We design a scalable system to display assertive alerts on a Raspberry Pi. Each user can select a subset of alerts in our system using a web interface. We present a bibliographic study of SoTA, the proposed architecture, the challenges posed by such a system, a set of tests for the performance and feasibility of the solution, and a set of conclusions and ideas for further developments. Full article
(This article belongs to the Collection Intelligent Security Sensors in Cloud Computing)
Show Figures

Figure 1

Figure 1
<p>MQTT general components schema and workflows.</p>
Full article ">Figure 2
<p>An overview of the architecture with the main blocks and interaction between them.</p>
Full article ">Figure 3
<p>A representation of data flow between the BMP180 sensor and InfluxDB.</p>
Full article ">Figure 4
<p>A representation of message handshake between the RPI and the server in the scope of authenticating the RPI.</p>
Full article ">Figure 5
<p>The message flow for alerts.</p>
Full article ">Figure 6
<p>This schema represents the process of updating the settings for a device.</p>
Full article ">Figure 7
<p>RPI configuration JSON message.</p>
Full article ">Figure 8
<p>Representation in Grafana of the average temperature/hour in a year for a device.</p>
Full article ">Figure 9
<p>UML diagram of the SQL database.</p>
Full article ">Figure 10
<p>Elapsed time loading data for every 15 min for 1 year. Batch size 3500.</p>
Full article ">Figure 11
<p>Elapsed time loading data for every 15 min for 1 year using equally spaced vs realistic spaced timestamps.</p>
Full article ">Figure 12
<p>Storage space used by data generated for fixed time intervals vs data generated for random time intervals.</p>
Full article ">Figure 13
<p>Side to side comparison of the average request response time per iteration of each case.</p>
Full article ">
19 pages, 7987 KiB  
Article
Data Distribution Service Converter Based on the Open Platform Communications Unified Architecture Publish–Subscribe Protocol
by Woongbin Sim, ByungKwen Song, Junho Shin and Taehun Kim
Electronics 2021, 10(20), 2524; https://doi.org/10.3390/electronics10202524 - 16 Oct 2021
Cited by 8 | Viewed by 3501
Abstract
The open platform communications unified architecture (OPC UA) is a major industry-standard middleware based on the request–reply pattern, and the data distribution service (DDS) is an industry standard in the publish–subscribe form. The OPC UA cannot replace fieldbuses at the control and field [...] Read more.
The open platform communications unified architecture (OPC UA) is a major industry-standard middleware based on the request–reply pattern, and the data distribution service (DDS) is an industry standard in the publish–subscribe form. The OPC UA cannot replace fieldbuses at the control and field levels. To facilitate real-time connectionless operation, the OPC Foundation added the publish–subscribe model—a new specification that supports broker functions, such as message queuing telemetry transport (MQTT), and advanced message queuing protocol (AMQP)—to the OPC UA Part 14 standard. This paper proposes a protocol converter for incorporation into the application layer of the DDS subscriber to facilitate interoperability among publisher–subscriber pairs. The proposed converter comprises a DDS gateway and bridge. The former exists inside the MQTT and AMQP brokers, which convert OPC UA publisher data into DDS messages prior to passing them on to the DDS subscriber. The DDS bridge passes the messages received from the DDS gateway to the OPC UA subscriber in the corresponding DDS application layer. The results reported in existing studies, and those obtained using the proposed converter, allow all devices supporting the OPC UA and OPC UA PubSub standards to realize DDS publish–subscribe interoperability. Full article
(This article belongs to the Section Computer Science & Engineering)
Show Figures

Figure 1

Figure 1
<p>The open platform communications unified architecture (OPC UA) protocol stack. MQTT, message queuing telemetry transport; AMQP, advanced message queuing protocol; TSN, time-sensitive network.</p>
Full article ">Figure 2
<p>OPC UA PubSub communication model [<a href="#B3-electronics-10-02524" class="html-bibr">3</a>].</p>
Full article ">Figure 3
<p>OPC UA PubSub broker communication model.</p>
Full article ">Figure 4
<p>Correlation between DDS domain participants and topics.</p>
Full article ">Figure 5
<p>Overall system architecture of the OPC UA protocol converter.</p>
Full article ">Figure 6
<p>A-Open62541 PubSub UML diagram.</p>
Full article ">Figure 7
<p>Communication model of OPC UA publisher and subscriber.</p>
Full article ">Figure 8
<p>A-Open62541 PubSub protocol stack and API.</p>
Full article ">Figure 9
<p>Overall software architecture of DDS gateway.</p>
Full article ">Figure 10
<p>Example of DDS gateway IDL mapping process.</p>
Full article ">Figure 11
<p>DDS bridge APIs.</p>
Full article ">Figure 12
<p>Testbed configuration used for proof of concept.</p>
Full article ">Figure 13
<p>Testbed configuration for the performance analysis.</p>
Full article ">Figure 14
<p>Monitoring screen between the OPC UA publisher and DDS gateway (AMQP).</p>
Full article ">Figure 15
<p>Monitoring screen between the DDS gateway and OPC UA subscriber (AMQP).</p>
Full article ">Figure 16
<p>OPC UA PubSub and OpenDDS latencies without converter.</p>
Full article ">Figure 17
<p>Comparison of latencies with and without the MQTT-based converter.</p>
Full article ">Figure 18
<p>Comparison of latencies with and without the AMQP-based converter.</p>
Full article ">
27 pages, 840 KiB  
Article
Internet of Things (IoT) Platform for Multi-Topic Messaging
by Mahmoud Hussein, Ahmed I. Galal, Emad Abd-Elrahman and Mohamed Zorkany
Energies 2020, 13(13), 3346; https://doi.org/10.3390/en13133346 - 30 Jun 2020
Cited by 9 | Viewed by 2981
Abstract
IoT-based applications operate in a client–server architecture, which requires a specific communication protocol. This protocol is used to establish the client–server communication model, allowing all clients of the system to perform specific tasks through internet communications. Many data communication protocols for the Internet [...] Read more.
IoT-based applications operate in a client–server architecture, which requires a specific communication protocol. This protocol is used to establish the client–server communication model, allowing all clients of the system to perform specific tasks through internet communications. Many data communication protocols for the Internet of Things are used by IoT platforms, including message queuing telemetry transport (MQTT), advanced message queuing protocol (AMQP), MQTT for sensor networks (MQTT-SN), data distribution service (DDS), constrained application protocol (CoAP), and simple object access protocol (SOAP). These protocols only support single-topic messaging. Thus, in this work, an IoT message protocol that supports multi-topic messaging is proposed. This protocol will add a simple “brain” for IoT platforms in order to realize an intelligent IoT architecture. Moreover, it will enhance the traffic throughput by reducing the overheads of messages and the delay of multi-topic messaging. Most current IoT applications depend on real-time systems. Therefore, an RTOS (real-time operating system) as a famous OS (operating system) is used for the embedded systems to provide the constraints of real-time features, as required by these real-time systems. Using RTOS for IoT applications adds important features to the system, including reliability. Many of the undertaken research works into IoT platforms have only focused on specific applications; they did not deal with the real-time constraints under a real-time system umbrella. In this work, the design of the multi-topic IoT protocol and platform is implemented for real-time systems and also for general-purpose applications; this platform depends on the proposed multi-topic communication protocol, which is implemented here to show its functionality and effectiveness over similar protocols. Full article
(This article belongs to the Special Issue IoT and Sensor Networks in Industry and Society)
Show Figures

Graphical abstract

Graphical abstract
Full article ">Figure 1
<p>Architecture of the Internet of Things (IoT) network.</p>
Full article ">Figure 2
<p>Publish/subscribe architecture based on single-topic messaging.</p>
Full article ">Figure 3
<p>Multi-messages technique using batching; for example, pulsar.apache.</p>
Full article ">Figure 4
<p>Proposed message with the three-topics technique.</p>
Full article ">Figure 5
<p>Architecture of the proposed multi-topic IoT protocol.</p>
Full article ">Figure 6
<p>Sequence diagram for a sensor node. ACK: acknowledgement message.</p>
Full article ">Figure 7
<p>Sequence diagram for an actuator node.</p>
Full article ">Figure 8
<p>Sequence diagram of a normal node.</p>
Full article ">Figure 9
<p>Sequence diagram of a monitor node.</p>
Full article ">Figure 10
<p>Sequence diagram for node to node communication.</p>
Full article ">Figure 11
<p>Identification frame structure.</p>
Full article ">Figure 12
<p>Acknowledgment frame structure.</p>
Full article ">Figure 13
<p>Registration frame structure.</p>
Full article ">Figure 14
<p>Data frame structure.</p>
Full article ">Figure 15
<p>Real-time operating system (RTOS) architecture.</p>
Full article ">Figure 16
<p>System tasks.</p>
Full article ">Figure 17
<p>Task state diagram.</p>
Full article ">Figure 18
<p>Block diagram of the proposed embedded IoT client.</p>
Full article ">Figure 19
<p>Sensor node flowchart.</p>
Full article ">Figure 20
<p>Actuator node flowchart.</p>
Full article ">Figure 21
<p>Normal node flowchart.</p>
Full article ">Figure 22
<p>Server (broker) flowchart.</p>
Full article ">Figure 23
<p>The average message delay (in seconds).</p>
Full article ">Figure 24
<p>Average traffic per message (bytes).</p>
Full article ">Figure 25
<p>The multi-topic measured message delay (in milliseconds).</p>
Full article ">Figure 26
<p>The total traffic measured per multi-topic message in bytes.</p>
Full article ">Figure 27
<p>Data decoupling.</p>
Full article ">Figure 28
<p>One-to-many messaging.</p>
Full article ">Figure 29
<p>Multi-functional communication.</p>
Full article ">
20 pages, 393 KiB  
Review
Security of IoT Application Layer Protocols: Challenges and Findings
by Giuseppe Nebbione and Maria Carla Calzarossa
Future Internet 2020, 12(3), 55; https://doi.org/10.3390/fi12030055 - 17 Mar 2020
Cited by 100 | Viewed by 13023
Abstract
IoT technologies are becoming pervasive in public and private sectors and represent presently an integral part of our daily life. The advantages offered by these technologies are frequently coupled with serious security issues that are often not properly overseen or even ignored. The [...] Read more.
IoT technologies are becoming pervasive in public and private sectors and represent presently an integral part of our daily life. The advantages offered by these technologies are frequently coupled with serious security issues that are often not properly overseen or even ignored. The IoT threat landscape is extremely wide and complex and involves a wide variety of hardware and software technologies. In this framework, the security of application layer protocols is of paramount importance since these protocols are at the basis of the communications among applications and services running on different IoT devices and on cloud/edge infrastructures. This paper offers a comprehensive survey of application layer protocol security by presenting the main challenges and findings. More specifically, the paper focuses on the most popular protocols devised in IoT environments for messaging/data sharing and for service discovery. The main threats of these protocols as well as the Common Vulnerabilities and Exposures (CVE) for their products and services are analyzed and discussed in detail. Good practices and measures that can be adopted to mitigate threats and attacks are also investigated. Our findings indicate that ensuring security at the application layer is very challenging. IoT devices are exposed to numerous security risks due to lack of appropriate security services in the protocols as well as to vulnerabilities or incorrect configuration of the products and services being deployed. Moreover, the constrained capabilities of these devices affect the types of security services that can be implemented. Full article
(This article belongs to the Collection Featured Reviews of Future Internet Research)
Show Figures

Figure 1

Figure 1
<p>Example of access control vulnerability that allows an attacker to subscribe to all topics and receive all messages being published. The numbers refer to the temporal evolution of the MQTT interactions depicted in the figure.</p>
Full article ">Figure 2
<p>Example of SSDP amplification/reflection DDoS attack toward a server.</p>
Full article ">Figure 3
<p>Breakdown of the CVEs per year and protocol.</p>
Full article ">
13 pages, 2311 KiB  
Article
The Advent of the Internet of Things in Airfield Lightning Systems: Paving the Way from a Legacy Environment to an Open World
by Enrico Buzzoni, Fabio Forlani, Carlo Giannelli, Matteo Mazzotti, Stefano Parisotto, Alessandro Pomponio and Cesare Stefanelli
Sensors 2019, 19(21), 4724; https://doi.org/10.3390/s19214724 - 31 Oct 2019
Cited by 3 | Viewed by 3903
Abstract
This paper discusses the design and prototype implementation of a software solution facilitating the interaction of third-party developers with a legacy monitoring and control system in the airfield environment. By following the Internet of Things (IoT) approach and adopting open standards and paradigms [...] Read more.
This paper discusses the design and prototype implementation of a software solution facilitating the interaction of third-party developers with a legacy monitoring and control system in the airfield environment. By following the Internet of Things (IoT) approach and adopting open standards and paradigms such as REpresentational State Transfer (REST) and Advanced Message Queuing Protocol (AMQP) for message dispatching, the work aims at paving the way towards a more open world in the airfield industrial sector. The paper also presents performance results achieved by extending legacy components to support IoT standards. Quantitative results not only demonstrate the feasibility of the proposed solution, but also its suitability in terms of prompt message dispatching and increased fault tolerance. Full article
(This article belongs to the Special Issue Towards an Industrial Internet of Things (IIoT))
Show Figures

Figure 1

Figure 1
<p>An example of Airport Lights Control and Monitoring System (ALCMS) network architecture.</p>
Full article ">Figure 2
<p>Overall architecture of the proposed solution.</p>
Full article ">Figure 3
<p>The IRMS system.</p>
Full article ">Figure 4
<p>Examples of Web Logger GUI (<b>a</b>) and JSON response (<b>b</b>) for the Insulation Resistance Monitoring System (IRMS).</p>
Full article ">Figure 5
<p>End-to-end delay average and standard deviation with socket, ActiveMQ-only, and ActiveMQ and Web server.</p>
Full article ">Figure 6
<p>Tested cluster architectures: clients connected to the same (<b>a</b>) and different (<b>b</b>) replicas.</p>
Full article ">Figure 7
<p>End-to-end message delivery delay of two 120 s long experiments with message creation frequency set at 1 (<b>a</b>) and 750 (<b>b</b>) messages per second: broker cluster configuration with two replicas, a replica fails at 60 s and another starts at 70 s.</p>
Full article ">
25 pages, 2938 KiB  
Article
A Multi-Protocol IoT Platform Based on Open-Source Frameworks
by Charilaos Akasiadis, Vassilis Pitsilis and Constantine D. Spyropoulos
Sensors 2019, 19(19), 4217; https://doi.org/10.3390/s19194217 - 28 Sep 2019
Cited by 35 | Viewed by 8075
Abstract
Internet of Things (IoT) technologies have evolved rapidly during the last decade, and many architecture types have been proposed for distributed and interconnected systems. However, most systems are implemented following fragmented approaches for specific application domains, introducing difficulties in providing unified solutions. However, [...] Read more.
Internet of Things (IoT) technologies have evolved rapidly during the last decade, and many architecture types have been proposed for distributed and interconnected systems. However, most systems are implemented following fragmented approaches for specific application domains, introducing difficulties in providing unified solutions. However, the unification of solutions is an important feature from an IoT perspective. In this paper, we present an IoT platform that supports multiple application layer communication protocols (Representational State Transfer (REST)/HyperText Transfer Protocol (HTTP), Message Queuing Telemetry Transport (MQTT), Advanced Message Queuing Protocol (AMQP), Constrained Application Protocol (CoAP), and Websockets) and that is composed of open-source frameworks (RabbitMQ, Ponte, OM2M, and RDF4J). We have explored a back-end system that interoperates with the various frameworks and offers a single approach for user-access control on IoT data streams and micro-services. The proposed platform is evaluated using its containerized version, being easily deployable on the vast majority of modern computing infrastructures. Its design promotes service reusability and follows a marketplace architecture, so that the creation of interoperable IoT ecosystems with active contributors is enabled. All the platform’s features are analyzed, and we discuss the results of experiments, with the multiple communication protocols being tested when used interchangeably for transferring data. Developing unified solutions using such a platform is of interest to users and developers as they can test and evaluate local instances or even complex applications composed of their own IoT resources before releasing a production version to the marketplace. Full article
Show Figures

Figure 1

Figure 1
<p>Platform components</p>
Full article ">Figure 2
<p>Database model.</p>
Full article ">Figure 3
<p>Composition of the face-counting service.</p>
Full article ">Figure 4
<p>Composition of the fall-detection and route-monitoring service.</p>
Full article ">Figure 5
<p>End-to-end message delays vs. batch message traffic size.</p>
Full article ">Figure 6
<p>Parallel clients: 30, publish topics per client: 2, frequency of batch messaging: 1 s, batch message size: 50 B.</p>
Full article ">Figure 7
<p>Without AuthN/AuthZ; parallel clients: 30, publish topics per client: 2, frequency of batch messaging: 1 s, batch message size: 50 B.</p>
Full article ">Figure 8
<p>Parallel clients: 30, publish topics per client: 2, frequency of batch messaging: 1 s, batch message size: 50 B.</p>
Full article ">
17 pages, 4383 KiB  
Article
Software Defined Wireless Mesh Network Flat Distribution Control Plane
by Hisham Elzain and Yang Wu
Future Internet 2019, 11(8), 166; https://doi.org/10.3390/fi11080166 - 25 Jul 2019
Cited by 13 | Viewed by 9310
Abstract
Wireless Mesh Networks (WMNs), have a potential offering relatively stable Internet broadband access. The rapid development and growth of WMNs attract ISPs to support users’ coverage anywhere anytime. To achieve this goal network architecture must be addressed carefully. Software Defined Networking (SDN) proposes [...] Read more.
Wireless Mesh Networks (WMNs), have a potential offering relatively stable Internet broadband access. The rapid development and growth of WMNs attract ISPs to support users’ coverage anywhere anytime. To achieve this goal network architecture must be addressed carefully. Software Defined Networking (SDN) proposes new network architecture for wired and wireless networks. Software Defined Wireless Networking (SDWN) has a great potential to increase efficiency, ease the complexity of control and management, and accelerate technology innovation rate of wireless networking. An SDN controller is the core component of an SDN network. It needs to have updated reports of the network status change, as in network topology and quality of service (QoS) in order to effectively configure and manage the network it controls. In this paper, we propose Flat Distributed Software Defined Wireless Mesh Network architecture where the controller aggregates entire topology discovery and monitors QoS properties of extended WMN nodes using Link Layer Discovery Protocol (LLDP) protocol, which is not possible in multi-hop ordinary architectures. The proposed architecture has been implemented on top of POX controller and Advanced Message Queuing Protocol (AMQP) protocol. The experiments were conducted in a Mininet-wifi emulator, the results present the architecture control plane consistency and two application cases: topology discovery and QoS monitoring. The current results push us to study QoS-routing for video streaming over WMN. Full article
Show Figures

Figure 1

Figure 1
<p>Flat Distributed-Software Defined Wireless Mesh Network (FD-SDWMN) flat architecture.</p>
Full article ">Figure 2
<p>FD-SDWMN controller architecture. AMQP: Advanced Message Queuing Protocol.</p>
Full article ">Figure 3
<p>The discovery message. LLDP: Link Layer Discovery Protocol; OUI: Organizationally Unique Identifier.</p>
Full article ">Figure 4
<p>OpenFlow Discovery Protocol (OFDP) topology discovery simple scenario. SDN: Software Defined Networking.</p>
Full article ">Figure 5
<p>Messages flow for the aggregated topology discovery mechanism.</p>
Full article ">Figure 6
<p>LLDP packet format for quality of service (QoS) monitoring.</p>
Full article ">Figure 7
<p>The control plane adaptation: (<b>Left</b>) the congested situation: C1 and C3 use the forwarding link via C2; (<b>Right</b>) link disruption: C1 and C3 use the congested control link with adapting information exchange frequency.</p>
Full article ">Figure 8
<p>Monitoring information exchange adaptation. Different agent messages’ packets, the bootstrap and discovery stage at t = 9 s. The link was cut off at t = 33 s, C2↔C3 link is cut off. (<b>a</b>) C1 → C2; (<b>b</b>) C1 → C3; (<b>c</b>) C2 → C3; (<b>d</b>) C2 → C1; (<b>e</b>) C3 → C1; (<b>f</b>) C3 → C2.</p>
Full article ">Figure 9
<p>QoS monitoring during video streaming scenario.</p>
Full article ">Figure 10
<p>QoS monitoring over LLDP Frontend GUI at the controller A. (<b>a</b>) B.S4-eth2: Bandwidth; (<b>b</b>) B.S4-eth2: Delay; (<b>c</b>) B.S4-eth2: Jitter; (<b>d</b>) B.S4-eth2: Packet loss.</p>
Full article ">
19 pages, 3022 KiB  
Article
An IoT Based Architecture for Enhancing the Effectiveness of Prototype Medical Instruments Applied to Neurodegenerative Disease Diagnosis
by Alessandro Depari, Dhiego Fernandes Carvalho, Paolo Bellagente, Paolo Ferrari, Emiliano Sisinni, Alessandra Flammini and Alessandro Padovani
Sensors 2019, 19(7), 1564; https://doi.org/10.3390/s19071564 - 31 Mar 2019
Cited by 14 | Viewed by 4859
Abstract
Human errors are probably the most critical cause of the large amount of medical accidents. Medical cyber-physical systems (MCPS) have been suggested as a possible approach for detecting and limiting the impact of errors and wrong procedures. However, during the initial development phase [...] Read more.
Human errors are probably the most critical cause of the large amount of medical accidents. Medical cyber-physical systems (MCPS) have been suggested as a possible approach for detecting and limiting the impact of errors and wrong procedures. However, during the initial development phase of medical instruments, regular MCPS systems are not a viable approach, because of the high costs of repeating complex validation procedures, due to modifications of the prototype instrument. In this work, a communication architecture, inspired by recent Internet of Things (IoT) advances, is proposed for connecting prototype instruments to the cloud, to allow direct and real-time interaction between developers and instrument operators. Without loss of generality, a real-world use case is addressed, dealing with the use of transcranial magnetic stimulation (TMS) for neurodegenerative disease diagnosis. The proposed infrastructure leverages on a message-oriented middleware, complemented by historical database for further data processing. Two of the most diffused protocols for cloud data exchange (MQTT and AMQP) have been investigated. The experimental setup has been focused on the real-time performance, which are the most challenging requirements. Time-related metrics confirm the feasibility of the proposed approach, resulting in an end-to-end delay on the order of few tens of milliseconds for local networks and up to few hundreds of milliseconds for geographical scale networks. Full article
Show Figures

Figure 1

Figure 1
<p>(<b>a</b>) Example of a set of three stimulus trains in a diagnosis protocol: train i is MM, train i + 1 is REF and train i + 2 is EM. The width of magnetic stimuli is usually 1 ms, whereas the width of electrical stimuli is 200 µs. T<sub>ISI</sub> is usually between 1 ms and 100 ms, whereas T<sub>ITI</sub> is on the order of few seconds. (<b>b</b>) Time diagram of mTS and successive EMG signal, with the quantity of interest (MEP).</p>
Full article ">Figure 2
<p>The general problem of data exchange between TMSs and their authorized users.</p>
Full article ">Figure 3
<p>The architecture of the AMQP-based solutions. The Authentication &amp; Encryption tier is natively supported by the AMQP protocol.</p>
Full article ">Figure 4
<p>The architecture of the MQTT-based solutions. The Authentication &amp; Encryption tier has to be implemented at higher level since it is not directly managed by the MQTT Broker.</p>
Full article ">Figure 5
<p>The different timestamps collected for evaluating the proposed time-related metrics.</p>
Full article ">Figure 6
<p>Client dashboard for remote supervision of diagnosis protocol carried out with the prototype TMS instruments.</p>
Full article ">Figure 7
<p>Block diagram of the implemented experimental setup.</p>
Full article ">Figure 8
<p>Probability Density Function (PDF) estimate of the residual offset after NTP daemon corrected the local system clock of the devices involved in the experiments.</p>
Full article ">Figure 9
<p>Boxplot of the DIC and DCI performance metrics with local server. The plot shows a blue box from the 25 percentile to the 75 percentile (with the median line). The whiskers go from the 5 percentile up the 95 percentile.</p>
Full article ">Figure 10
<p>Boxplot of the DIC and DCI performance metrics with cloud server. The plot shows a blue box from the 25 percentile to the 75 percentile (with the median line). The whiskers go from the 5 percentile up the 95 percentile.</p>
Full article ">Figure 11
<p>Bar graph of the DIC and DCI performance metrics with cloud server. The whiskers go from the 5 percentile up the 95 percentile.</p>
Full article ">
1845 KiB  
Article
A Smart City Lighting Case Study on an OpenStack-Powered Infrastructure
by Giovanni Merlino, Dario Bruneo, Salvatore Distefano, Francesco Longo, Antonio Puliafito and Adnan Al-Anbuky
Sensors 2015, 15(7), 16314-16335; https://doi.org/10.3390/s150716314 - 6 Jul 2015
Cited by 28 | Viewed by 9155
Abstract
The adoption of embedded systems, mobile devices and other smart devices keeps rising globally, and the scope of their involvement broadens, for instance, in smart city-like scenarios. In light of this, a pressing need emerges to tame such complexity and reuse as much [...] Read more.
The adoption of embedded systems, mobile devices and other smart devices keeps rising globally, and the scope of their involvement broadens, for instance, in smart city-like scenarios. In light of this, a pressing need emerges to tame such complexity and reuse as much tooling as possible without resorting to vertical ad hoc solutions, while at the same time taking into account valid options with regard to infrastructure management and other more advanced functionalities. Existing solutions mainly focus on core mechanisms and do not allow one to scale by leveraging infrastructure or adapt to a variety of scenarios, especially if actuators are involved in the loop. A new, more flexible, cloud-based approach, able to provide device-focused workflows, is required. In this sense, a widely-used and competitive framework for infrastructure as a service, such as OpenStack, with its breadth in terms of feature coverage and expanded scope, looks to fit the bill, replacing current application-specific approaches with an innovative application-agnostic one. This work thus describes the rationale, efforts and results so far achieved for an integration of IoT paradigms and resource ecosystems with such a kind of cloud-oriented device-centric environment, by focusing on a smart city scenario, namely a park smart lighting example, and featuring data collection, data visualization, event detection and coordinated reaction, as example use cases of such integration. Full article
(This article belongs to the Special Issue Sensors and Smart Cities)
Show Figures


<p>Smart city as a closed-loop system.</p>
Full article ">
<p>Google Maps and Google Earth screenshots of Albert Park in Auckland, New Zealand.</p>
Full article ">
<p>Standard lamp used currently at the park <b>(Left);</b> possible replacement with a modern LED light <b>(Right).</b></p>
Full article ">
<p>Data collection and inference/reaction subsystem: architecture.</p>
Full article ">
<p>Maps screenshot: smart lampposts locations.</p>
Full article ">
<p>Horizon-IoT panel: real-time graphs (no events).</p>
Full article ">
<p>Horizon-IoT panel: lighting real-time graphs (including events).</p>
Full article ">
<p>Horizon-IoT panel: noise/events real-time graphs (second half of the page).</p>
Full article ">
Back to TopTop