Abstract
In this article, we focus on the usage of MQTT (Message Queuing Telemetry Transport) within Connected Vehicles (CVs). Indeed, in the original version of MQTT protocol, the broker is responsible “only” for sending received data to subscribers; abstracting then the underlying mechanism of data exchange. However, within CVs context, subscribers (i.e., the processing infrastructure) may be overloaded with irrelevant data, in particular when the requirement is real or near real-time processing. To overcome this issue, we propose MQTT-CV; a new variant of MQTT protocol, in which the broker is able to perform local processing in order to reduce the workload at the infrastructure; i.e., filtering data before sending them. In this article, we first validate formally the correctness of MQTT-CV protocol (i.e., the three components of the proposed protocol are correctly interacting), through the use of Promela language and its system verification tool; the model checker SPIN. Secondly, using real-world data provided by our car manufacturer partner, we have conducted real implementation and experiments. The obtained results show the effectiveness of our approach in term of data workload reduction at the processing infrastructure. The mean improvement, besides the fact that it is dependent of the target application, was in general about 10 times less in comparison to native MQTT protocol.
Highlights
N OWADAYS, the Internet of Things (IoT) concept [1] is prevalent in various sectors such as automotive, domotics, health care, etc
We can say that compared with state-ofthe-art solutions, the originality and contribution of the work presented in this paper are (1) the proposition of MQTTCV, (2) its specification with Promela language, and (3) its analysis/verification with the SPIN model checker
First, we have proposed a variant of MQTT, named MQTT-Connected Vehicles (CVs), which aims to alleviate automotive infrastructures in terms of data that will be sent to them by the broker
Summary
N OWADAYS, the Internet of Things (IoT) concept [1] is prevalent in various sectors such as automotive, domotics, health care, etc. An after-sales application could be interested to track vehicles that have their engine’s temperature exceeding a certain value In this case, as all data is processed at the infrastructure layer, the latter has to support a huge workload. The workload of the infrastructure can be substantially reduced at the expense of a negligible processing cost at the broker, as stated by our experiments This infrastructure workload reduction can have a significant impact on the overall performance of the system because of the huge number of CVs. because of the sensitivity of several automotive applications, we provide in this paper formal proofs of the correctness of our proposed protocol (i.e., the three components will behave as they are supposed to do).
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
