Why MQTT Is Essential for Building Connected Cars
Guest WriterGuest Writer
The automotive industry is embracing the idea of inventing the truly connected car. They see the opportunity and benefits of leveraging telemetry data gathered from vehicles to create new revenue opportunities and build more robust customer experiences. However, successfully launching a connected car service that can scale to support millions of cars across vast distances and in a whole range of environmental conditions can present some serious challenges.
For most connected car services, bi-directional communication between the car and the cloud is a requirement, even though some edge processing can make connected cars more independent of the cloud. Connect vehicles send telemetry data to the cloud and enable applications like predictive maintenance, assisted driving, emergency response, etc. Similarly, the vehicle needs to be able to receive messages from the cloud to respond to remote commands like remote door locking and unlocking, remote activation of horn or lights, changing traffic environments, etc.
Implementing the car to cloud communication could be handled with standard web messaging protocols like HTTP. However, given that the IP addresses of vehicles would be unstable as they shift from cellular network to network, the cloud to car communication may require a different kind of communication system.
Besides the bi-directional messaging challenge, there are a number of other unique technical challenges for connected car services:
Many companies have attempted to implement a connected car service using HTTP and SMS. To establish a connection with the car, the cloud platform would send an SMS to the vehicle that includes a URL to initiate an HTTP request/response connection. However, this pattern has proven to be unreliable and typically results in sluggish user experiences. In some cases, a remote command being sent from a mobile phone app would take up to 30 seconds to complete the request. 30 seconds to unlock your car doors from a mobile app is not the type of user experience car companies want to deliver to their customers.
MQTT's publish/subscribe protocol is well designed to address the challenges of connected car services and is well suited for moving data between the car and cloud platforms.
Car companies, tier 1 suppliers and startups needed to find a new style of architecture for their connected car services. Many of these companies are now turning to the MQTT publish/subscribe architecture for implementing their services. MQTT has become the defacto IoT standard for connected devices and moving data from the device to the cloud.
It turns out MQTT addresses many of the challenges of creating scalable and reliable connected car services, for instance:
MQTT addresses many of the issues of building a connected car service. Car companies such as BMW are already using MQTT to provide reliable messaging for their car-sharing application. If you'd like to learn more about using MQTT to build connected vehicles, check out this resource.
Written by Ian Skerrett, Head of Marketing at HiveMQ.
The Most Comprehensive IoT Newsletter for Enterprises
Showcasing the highest-quality content, resources, news, and insights from the world of the Internet of Things. Subscribe to remain informed and up-to-date.
New Podcast Episode
Recent Articles