Why MQTT Has Become the De Facto Standard for the Connected Car
The automotive industry is seeing increasing demands to offer connectivity solutions to consumers. Digitalization and connectivity have been top priorities for automotive executives for the last several years. In fact, connected car market size is projected to grow to US$ 225.16 billion by 2027, an average growth rate of 17.1% from 2019.
The growth of this demand is being driven by:
- consumers expecting a more connected experience while driving in their car
- increased efficiencies in fleet management solutions
- new mobility services, like car and ride sharing
- and in the near future, vehicle to infrastructure (V2X) initiatives that improve the safety and convenience through smarter road infrastructure and also advanced driving infrastructure and autonomous driving.
To offer an integrated connectivity solution, most OEMs and tier 1 suppliers have launched or are developing their next generation connected car platforms. At HiveMQ, we have had the privilege of working with many of these leading companies since they are using MQTT and HiveMQ at the core of their connected car platform. In fact, we have noticed a trend that MQTT is fast becoming the de facto standard for connecting vehicles with the cloud.
It is interesting to understand why MQTT has risen to dominance in the automotive industry. Some OEM and suppliers have had connectivity solutions available in their automobiles for many years. First generation connectivity solutions were often based on SMS and HTTP. Unfortunately, these technologies were not built for the connected car use case. HTTP depends on consistent network connectivity, while connected cars operate over mobile networks which are notoriously unreliable. SMS does not provide the real-time messaging experience that is required for a connected car service. For one company, unlocking a car door from a mobile phone took upwards of 30 seconds using SMS and HTTP. Clearly not acceptable for consumers that expect immediate responsiveness in their digital experiences. Finally, SMS and HTTP were prohibitively expensive due to their high requirements for network bandwidth.
Further Reading: MQTT Enables IIoT Security Best Practices within the Purdue Model
It turns out that MQTT is ideally suited for the connected car use case. Unlike HTTP, MQTT can keep a persistent session between an MQTT client and MQTT broker. So when a car moves through a dead zone in a cellular network, the session still exists once the network has reconnected. This means there is no requirement for the costly HTTP handshake to re-establish a connection. MQTTs publish/subscribe protocol is ideally suited for broadcasting messages out to a fleet of cars. HTTP is able to handle sending vehicle telemetry data to the cloud but cloud to vehicle messaging is very complicated. With MQTT, a connected car platform can broadcast a message to a single vehicle or a fleet of vehicles. Finally, MQTT is much more efficient in network bandwidth. Some of our customers report a 30% reduction in network traffic due to the smaller MQTT payload size and the decrease in the request/response pattern of HTTP.
MQTT is so widely adopted in the connected car industry that we predict by the end of 2022, over 50% of new vehicles produced will be connected using MQTT. HiveMQ customers are leading the way. Find out more about what’s best for IIoT: An integration hub or an MQTT broker?
About the author
This article was written by Ian Skerrett, Head of Marketing, HiveMQ. Senior marketing and product management executive with over 25 years experience in the software industry. He helps companies build successful marketing and communication strategies for complex products. Specific focus on IoT and Open Source Software.