Vehicle Communication Protocol Split for Low-Latency Driving Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems for connected cars face issues with high connection latency, scalability, and cost due to synchronous protocols like HTTP, which affect safety and efficiency in automatic driving applications, especially in poor communication environments.
Innovation Solution
A communication system using a combination of HTTP, MQTT, and TCP protocols for different types of data transmission, with MQTT ensuring delivery guarantee and topic assignment for importance, and TCP for large data division and synchronization, to ensure rapid and secure information exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTP protocol is used for communication between vehicle and server, then connection continuity is maintained, but communication latency increases and scalability deteriorates
Solution Approach 1:
The patent segments the communication protocol into two distinct parts: HTTP for position information transmission and MQTT for driving control and environment information. This segmentation allows each protocol to be optimized for its specific function, resolving the contradiction between connection continuity (HTTP's strength) and communication latency (MQTT's strength).
Solution Approach 2:
The communication system implements multi-functionality by supporting both HTTP and MQTT protocols simultaneously. The server and vehicle terminal can selectively use the appropriate protocol based on the type of information being transmitted, making the system universally adaptable to different communication needs while optimizing for both reliability and low latency.
2Adaptability or versatility
If HTTP protocol is used for all communication data, then compatibility is maintained, but communication cost increases due to larger data size
Solution Approach 1:
The patent applies local quality by using different protocols for different data types: HTTP for position information and MQTT for driving control information. This localized protocol selection optimizes communication efficiency for each specific data type while maintaining overall system compatibility, thereby reducing unnecessary communication costs.
3Device complexity
If simple configuration without relay apparatus is used, then device complexity is reduced, but system flexibility deteriorates
Solution Approach 1:
The patent implements dynamic protocol selection where the vehicle terminal and server can switch between HTTP and MQTT protocols based on real-time communication needs. This dynamic adaptability provides system flexibility without requiring complex relay apparatus, as the protocols are selected and switched dynamically at the communication layer.
Data Source
AI summary
Provided is a communication system in which transmission and reception of information is performed between a server and a communication apparatus mounted on a vehicle or a client terminal owned by an occupant of the vehicle via a base station. A client terminal includes a first communication module and a second communication module. A server includes a third communication module and a fourth communication module. The first communication module transmits position information of a vehicle to the third communication module in accordance with HTTP as a communication protocol. The fourth communication module transmits driving control information specific to the vehicle and surrounding environment information specific to the vehicle that are generated to the second communication module in accordance with MQTT as a communication protocol, with a MQTT topic assigned with an ID and with a delivery guarantee function added depending on the degree of importance of the information.