A service infrastructure for the Internet of Things based on XMPP

Bendel, Sven; Thomas, Sabu; Schuster, Daniel; Schill, Alexander; Ackermann, Ralf; Ameling, Michael

doi:10.1109/percomw.2013.6529522

Cited by 44 publications

(26 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This protocol uses TLS/SSL for security, and relies on TCP to ensure reliability. XMPP is most suited for real-time applications, with small message footprints and low latency in message exchange [64]. Although XMPP is preferred over CoAP in data-centric IoT scenarios due to offering the publish/subscribe mechanism, the lack of QoS provisioning might not be acceptable in mission-ciritical applications.…”

Section: A Iot Application Layer Protocolsmentioning

confidence: 99%

Implementation and analysis of QUIC for MQTT

Kumar

Dezfouli

2019

Computer Networks

View full text Add to dashboard Cite

Transport and security protocols are essential to ensure reliable and secure communication between two parties. For IoT applications, these protocols must be lightweight, since IoT devices are usually resource constrained. Unfortunately, the existing transport and security protocols -namely TCP/TLS and UDP/DTLS -fall short in terms of connection overhead, latency, and connection migration when used in IoT applications. In this paper, after studying the root causes of these shortcomings, we show how utilizing QUIC in IoT scenarios results in a higher performance. Based on these observations, and given the popularity of MQTT as an IoT application layer protocol, we integrate MQTT with QUIC. By presenting the main APIs and functions developed, we explain how connection establishment and message exchange functionalities work. We evaluate the performance of MQTTw/QUIC versus MQTTw/TCP using wired, wireless, and long-distance testbeds. Our results show that MQTTw/QUIC reduces connection overhead in terms of the number of packets exchanged with the broker by up to 56%. In addition, by eliminating half-open connections, MQTTw/QUIC reduces processor and memory usage by up to 83% and 50%, respectively. Furthermore, by removing the head-of-line blocking problem, delivery latency is reduced by up to 55%. We also show that the throughput drops experienced by MQTTw/QUIC when a connection migration happens is considerably lower than that of MQTTw/TCP.

show abstract

Section: A Iot Application Layer Protocolsmentioning

confidence: 99%

Implementation and analysis of QUIC for MQTT

Kumar

Dezfouli

2019

Computer Networks

View full text Add to dashboard Cite

show abstract

“…Regardless, the XMPP technology offers a great platform to implement M2M systems over it. There are already many communities, researchers or research groups who are studying the XMPP's potential on applications such as M2M or IoT fields [52], [10], [42], [46], [6], [53], [54], [7], [55], [56], [9], [57], [58], [59], [60], [61], [62].…”

Section: The Extensible Messaging and Presence Protocol (Xmpp)mentioning

confidence: 99%

“…The XMPP gateway permits the termination of a given client-to-server (C2S) session and the initiation of a new session to the target endpoint protocol. Gateways are most often used in this context to translate between instant messaging (IM) protocols (for example, XMPP to Internet Relay Chat) or translate XMPP and other protocols, such as Bluetooth to control Lego NXT and Wii Remote [10].…”

Section: A Xmpp Features and The Distributed Client-server Architecturementioning

confidence: 99%

Harnessing XMPP for Machine-to-Machine Communications & Pervasive Applications

Iivari

Väisänen

Alaya

et al. 2017

JCOMSS

View full text Add to dashboard Cite

An ever increasing number of interconnected embedded devices, or Machine-to-Machine (M2M) systems, are changing the way we live, work and play. M2M systems as a whole are typically characterized by the diversity in both the type of device and type of network access technology employed, and such systems are often still today task-specific and built for just one specific application. Smart lighting, remote monitoring and control of all kinds of consumer devices and industrial equipment, safety and security monitoring devices and smart health and fitness products, exemplify this revolution of intercommunicating machines. However, the differences in communication technologies and data formats among such devices and systems are leading to a huge complexity explosion problem and a strongly fragmented market, with no true interoperability. Due to these problems, the full potential of M2M technology has yet to be fulfilled. In this paper, we examine the suitability of the Extensible Messaging and Presence Protocol (XMPP) and experiment with its potential to rise to the challenge of machine-to-machine communications and meet the needs of modern pervasive applications. Experimental implementations and some proof-of-concept solutions are also presented.

show abstract

“…To address more complex scenarios the SO interaction primitives must support the Publish/Subscribe paradigm: e.g., [16] proposes the adoption of XMPP. The described platform defines the service by specifying how the data produced by an object (e.g., a sensor) is dispatched to interested objects or, in general, service components.…”

Section: Related Workmentioning

confidence: 99%

A Platform for Smart Object Virtualization and Composition

Stecca

Moiso

Fornasa

et al. 2015

IEEE Internet Things J.

View full text Add to dashboard Cite

One of the most challenging objectives of the Internet of Things (IoT) domain is the identification of interaction paradigms and communication standards to integrate smart objects (SOs), i.e., physical objects able to interact with the network. Such interaction paradigms and communication protocols belong to what can be called the IoT application layer, on which this paper focuses. This paper presents app execution platform (AEP), a platform that supports the design, deployment, execution, and management of IoT applications in the domain of smart home, smart car, and smart city. AEP was designed to coherently fulfill a set of requirements covered only partially or in a fragmented way by other IoT application platforms. AEP focuses on SO virtualization and on composite application (CA) orchestration and supports dynamic object availability

show abstract

A service infrastructure for the Internet of Things based on XMPP

Cited by 44 publications

References 6 publications

Implementation and analysis of QUIC for MQTT

Implementation and analysis of QUIC for MQTT

Harnessing XMPP for Machine-to-Machine Communications & Pervasive Applications

A Platform for Smart Object Virtualization and Composition

Contact Info

Product

Resources

About