Comparison of the CUPUS middleware and MQTT protocol for smart city services

Abstract

Publish/subscribe messaging pattern is often used as a communication mechanism in data-oriented applications and is becoming wide-spread, especially due to the expansion of the Internet of Things (IoT) services and applications. In addition to MQTT, which is one of the commonly used publish/subscribe protocols in the context of IoT, there are a number of other message queuing solutions, either open or proprietary. We have designed a CloUd-based PUblish/Subscribe (CUPUS) middleware solution within the framework of the FP7 project OpenIoT <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">1</sup> that has developed an open-source cloud platform for the IoT. CUPUS is one of the core OpenIoT components which enables flexible integration of wearable sensors and mobile devices as data sources within the OpenIoT platform. In this paper we compare MQTT and CUPUS in the context of smart city application scenarios. Smart city services pose different key-requirements on IoT publish/subscribe solutions and thus we propose a taxonomy to identify vital features of IoT publish/subscribe middleware. The comparison shows that CUPUS is more appropriate for mobile environments with frequent context changes, while it can filter out unrequired data on devices prior to being reported to backend cloud servers. The MQTT protocol proves to be suitable for Wireless Sensor Networks (WSNs) and heterogeneous environments due to its small code footprint, low bandwidth usage and standardized interfaces. Finally we evaluate the two solutions in terms of message footprint in a real-world scenario, latency and delivery semantics.