Search

Remote Patient Monitoring (RPM) is a healthcare solution that uses technology to monitor patients outside conventional healthcare settings. It is especially useful for people with chronic conditions or needing regular monitoring. One of the main reasons for the increase in the number of deaths each year is the increase in cardiovascular diseases, including hypertension. Online blood pressure monitoring offers many advantages but also potential challenges. This work reviews the key communication technologies and research challenges in the real-time transmission of measured blood pressure data. Delay in these systems is not tolerated as it involves human lives. To conduct the experimental studies, a prototype of an experimental intelligent system was created to study the delay and processor load of the RPI4 gateway. The measured blood pressure data is sent to the Things Board cloud using the AMQP and CoAP protocols. The experimental results are particularly useful for RPM system designers. The results of this research facilitate an informed decision on the choice of protocol that transmits the data from the gateway to the cloud in the process of designing remote patient monitoring systems. [ABSTRACT FROM AUTHOR]

Copyright of GeSec: Revista de Gestao e Secretariado is the property of Sindicato das Secretarias e Secretarios do Estado de Sao Paulo (SINSESP) and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Abstract This paper presents priority support in the Internet of Things to support the reliable and timely transmission of messages during emergencies. The Message Queuing Telemetry Transport protocol is a widely used IoT messaging protocol. However, it does not support the timely and fast delivery of emergency messages. In this regard, this paper proposes to classify the messages into three different queues. The RabbitMQ broker manages virtual queues based on the message type, such as First Come First Served, Critical, and Urgent. In addition, the proposed approach stores the messages in the MySQL database for further analysis. To confirm its efficacy, we compare the Urgent and Critical queues with the current First Come First Served technique in an experimental implementation. Wireshark packet analyzer is used to record packets while messages are being transmitted between clients and the broker to examine end-to-end latency, jitter, response time, and total time. The results show that the proposed approach performs better for high-priority emergency messages.

This paper presents priority support in the Internet of Things to support the reliable and timely transmission of messages during emergencies. The Message Queuing Telemetry Transport protocol is a widely used IoT messaging protocol. However, it does not support the timely and fast delivery of emergency messages. In this regard, this paper proposes to classify the messages into three different queues. The RabbitMQ broker manages virtual queues based on the message type, such as First Come First Served, Critical, and Urgent. In addition, the proposed approach stores the messages in the MySQL database for further analysis. To confirm its efficacy, we compare the Urgent and Critical queues with the current First Come First Served technique in an experimental implementation. Wireshark packet analyzer is used to record packets while messages are being transmitted between clients and the broker to examine end-to-end latency, jitter, response time, and total time. The results show that the proposed approach performs better for high-priority emergency messages. [ABSTRACT FROM AUTHOR]

In today’s world, the use of IoT devices is growing every day. For connecting IoT devices from various vendors and supporting a variety of IoT use cases, an interoperable protocol like AMQP is necessary. Researchers are striving to minimize delay because many IoT applications are sensitive to it. The transport layer protocol that is used underneath, such as TCP or UDP, is one of the main causes of the delay. Although TCP is slower than UDP because to the three-way handshake and the usage of TLS for security, it is more reliable than UDP. The Internet Engineering Task Force has introduced a new transport layer protocol called QUIC that combines the best features of UDP and TCP to offer quick and reliable communication. In this study, we integrated QUIC and AMQP1.0 using the Go programming language. The Docker tool was used to containerize the AMQP1.0 Broker, Sender, and Receiver implementations. The performance of AMQP1.0 over TCP and AMQP1.0 over QUIC was benchmarked in the NS3 simulator over various wireless networks including WiFi, 4G/LTE, and satellite. QUIC showed considerable improvement over lossy networks. The results showed that switching from TCP to QUIC at the transport level lowered Communication Time by 8.57% over Satellite network. Although Round Trip Time was almost same yet Start up Latency showed improvement of 52%, 38% and 34% in case of WiFi, 4G/LTE and Satellite respectively. In addition, the performance of AMQP1.0 over TCP and AMQP1.0 over QUIC has been evaluated over different Packet Loss values, the results show that AMQP1.0 over QUIC outperforms AMQP1.0 over TCP in all the cases. The testing results revealed that TCP performance was degraded by 20%, 16%, and 36% over WiFi, 4G/LTE, and satellite, respectively at Packet loss of 15%, while QUIC performance was only degraded by 4%, 8%, and 9% in each of these cases.

In today's world, the use of IoT devices is growing every day. For connecting IoT devices from various vendors and supporting a variety of IoT use cases, an interoperable protocol like AMQP is necessary. Researchers are striving to minimize delay because many IoT applications are sensitive to it. The transport layer protocol that is used underneath, such as TCP or UDP, is one of the main causes of the delay. Although TCP is slower than UDP because to the three-way handshake and the usage of TLS for security, it is more reliable than UDP. The Internet Engineering Task Force has introduced a new transport layer protocol called QUIC that combines the best features of UDP and TCP to offer quick and reliable communication. In this study, we integrated QUIC and AMQP1.0 using the Go programming language. The Docker tool was used to containerize the AMQP1.0 Broker, Sender, and Receiver implementations. The performance of AMQP1.0 over TCP and AMQP1.0 over QUIC was benchmarked in the NS3 simulator over various wireless networks including WiFi, 4G/LTE, and satellite. QUIC showed considerable improvement over lossy networks. The results showed that switching from TCP to QUIC at the transport level lowered Communication Time by 8.57% over Satellite network. Although Round Trip Time was almost same yet Start up Latency showed improvement of 52%, 38% and 34% in case of WiFi, 4G/LTE and Satellite respectively. In addition, the performance of AMQP1.0 over TCP and AMQP1.0 over QUIC has been evaluated over different Packet Loss values, the results show that AMQP1.0 over QUIC outperforms AMQP1.0 over TCP in all the cases. The testing results revealed that TCP performance was degraded by 20%, 16%, and 36% over WiFi, 4G/LTE, and satellite, respectively at Packet loss of 15%, while QUIC performance was only degraded by 4%, 8%, and 9% in each of these cases. [ABSTRACT FROM AUTHOR]

RabbitMQ, an implementation of Advanced Message Queuing Protocol (AMQP), is a very popular message middleware. It supports concurrency, guarantees sequential consistency, and enables independent applications and services to communicate. Consequently, it is of great significance to ensure the secure communication of RabbitMQ. Therefore, Kerberos, a network authentication protocol, is introduced to combine with RabbitMQ to address this security issue. In this paper, we apply formal methods to model and verify RabbitMQ with Kerberos. By utilizing UPPAAL, RabbitMQ is abstracted to timed automata. Further, we validate the constructed model with the simulator in UPPAAL. On this basis, we verify whether RabbitMQ meets some basic but essential properties, including Reachability of Data, Concurrency, Sequence Consistency and Heartbeat Mechanism. Additionally, the security property Secure Communication is verified as well. From the verification results via UPPAAL, it can be found that RabbitMQ can totally cater for these properties and it maintains secure communication under the umbrella of Kerberos. [ABSTRACT FROM AUTHOR]

One of the most important things in IoT system development is the right communication technologies and protocols. Communication of modern IoT systems can be divided into two main parts: device-to-cloud communication and communication between cloud microservices (application level). In this study, the authors designed a test-system environment for evaluating the performance of the existing transmitting protocols for the cloud microservices communication. The proposed environment allows emulate of IoT systems with low network latency which allows evaluating and comparing protocols performance. The authors provide tests for the most popular application-level protocols: HTTP, MQTT, AMQP, and GRPC. The performance evaluation was performed based on such metrics: throughput, concurrency, scalability, transmitting size, and init connection time. The obtained experimental results and testing environment can be used for the efficient design of microservice communication. [ABSTRACT FROM AUTHOR]

As the number of Internet of Things (IoT) devices proliferates, the magnitude and velocity of data continues to increase rapidly. IoT systems rely primarily on using messaging protocols for exchanging IoT data and there exists several protocols or frameworks that support distinct types of messaging patterns. Given that IoT devices typically have limited computational resources and processing power, choosing a lightweight, reliable, scalable, interoperable, extensible and secure messaging protocol becomes a very challenging task. As a result, it is not uncommon that IoT systems may employ multiple messaging protocols for supporting device heterogeneity and different message exchange patterns. In addition, basic similarities among existing several messaging protocols or frameworks that exist today for exchanging IoT data within IoT systems suggest the potential of interoperability. Given that IoT systems help facilitate the interconnectivity among distributed, heterogeneous entities, interoperability among existing messaging protocols will play an increasingly important role in simplifying the development and deployment of IoT systems. In this paper, we present a comprehensive review of the existing messaging protocols that can be used in deploying IoT systems. Throughout this paper, we highlight the protocols' distinctive approaches and applicability of using them across various IoT environments. In addition, we highlight challenges, strengths and weaknesses of these messaging protocols in the context of IoT.

This paper describes a concept for a resilient meteorological monitoring system for reading data from sensors by using AMQP in order to increase reliability of the data acquisition system. A set of sensors is connected to the Beaglebone Black and is located in the mountains of north of Thailand. Gathered data are queued on a local SoC and sent to a server located in Germany whenever a network connection is available. Further in the work implementation and test of such a system in Thailand is discussed. Special challenges in the implementation of the system is the presence of frequent thunderstorms and outages caused by them. To improve the reliability of data transmission free AMQP implementation is used. The protocol has been studied, tested, and programs have been created for transmitting data from sensors to a server in Germany using the Rabbit MQ to store the data in the case of connection failures. Besides that, memory usage problems were raised when using AMQP in single-board computers, such as Beaglebone Black. The main task of this work is to propose the most stable and reliable operation of the data transmission system.

This article concerns presentation and comparison of the performance of a set of the Internet Of Things protocols in the application layer and others that are used to link objects such as: Message Queuing Telemetry Transport (MQTT), Constrained Application Protocol (COAP), Extensible Messaging and Presence Protocol (EMPP), RESTFUL Services, Advanced Message Queuing Protocol (AMQP), and Websockets. This comparison will be carried out in terms of security, transport, architecture and quality of service (QoS). This work will enable us to specify the strong and weak points of each protocol. [ABSTRACT FROM AUTHOR]

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.

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.

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.

The internet of things (IoT) will enable a range of applications providing enhanced awareness and control of the physical environment. Current systems typically sense and actuate physical phenomena locally and then rely on a cloud-based publish/subscribe infrastructure for distribution of sensor and control data to end-users and external services. Despite the popularity of pub/sub solutions in this context, it is still unclear which features such a middleware should have to successfully meet the specific requirements of the IoT domain. Questions like how a large number of connected devices that only sporadically send small sensor data messages affect the throughput, and how much additional delay cloud-based pub/sub systems typically introduce, that are very important for practitioners, have not been tackled in a systematic way. In this work, we address these limitations by analyzing the main requirements of IoT platforms and by evaluating which of those features are supported by prominent open pub/sub solutions. We further carry out a performance evaluation in the public cloud using four popular pub/sub implementations: rabbitMQ (AMQP), mosquitto (MQTT), ejabberd (XMPP), and ZeroMQ. We study the maximum sustainable throughput and delay under realistic load conditions using traces from real sensors. While the core features are similar, the analyzed pub/sub systems differ in their filtering capabilities, semantic guarantees, and encoding. Our evaluation indicates that those differences can have a notable impact on throughput and delay of cloud-based IoT platforms. [ABSTRACT FROM AUTHOR]

Building a general architecture for the Internet of Things (IoT) is a very complex task, exacerbated by theextremely large variety of devices, link layer technologies, and services that may be involved in such asystem. In this paper, we identify the main blocks of a generic IoT architecture, describing their featuresand requirements, and analyze the most common approaches proposed in the literature for each block. Inparticular, we compare three of the most important communication technologies for IoT purposes, i.e., REST,MQTT, and AMQP, and we also analyze three IoT platforms: openHAB, Sentilo, and Parse. The analysis willprove the importance of adopting an integrated approach that jointly addresses several issues and is able toflexibly accommodate the requirements of the various elements of the system. We also discuss a use case whichillustrates the design challenges and the choices to make when selecting which protocols and technologies touse.