Connected Vehicle App Coordination Across Version Differences
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Connected vehicles with different versions of the same vehicle application struggle to interact effectively, as they may have different approaches to handling scenarios like a four-way stop sign at an intersection, leading to potential inaccuracies in estimating each other's future behavior, and traditional software patches are impractical in fast-paced driving scenarios.
Innovation Solution
A resolver system that modifies the functionality of vehicle applications onboard connected vehicles without software patches by forming a vehicular micro cloud, where the ego vehicle and remote vehicles share tasks to achieve the maximum possible functionality based on their hardware and software capabilities, using V2X messages to coordinate and synchronize their actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software patches are used to update vehicle applications, then version consistency is improved, but response time increases and practicality decreases in fast-paced driving scenarios
Solution Approach 1:
The system performs preliminary actions by having the ego vehicle pre-process V2X messages and pre-determine compatibility adjustments before interactions with remote vehicles are needed. This allows the system to have version compatibility solutions ready in advance, eliminating the need for time-consuming software patches during actual driving scenarios.
Solution Approach 2:
The system introduces an intermediary compatibility layer that translates and adapts V2X messages between different application versions. This intermediary mechanism allows vehicles with different versions to communicate effectively without requiring actual software updates, thus maintaining both version consistency and fast response times.
2Adaptability or versatility
If different versions of vehicle applications are used, then adaptability is improved, but cooperation effectiveness deteriorates due to functional differences
Solution Approach 1:
The system dynamically changes parameters by adjusting the interpretation and processing of V2X messages based on the version capabilities of the ego and remote vehicles. The ego vehicle modifies message parameters such as data formats, communication protocols, and functional interpretations to ensure compatibility across different versions while maintaining version diversity.
3Ease of operation
If version differences are allowed, then ease of operation is improved, but measurement precision deteriorates in estimating future behavior
Solution Approach 1:
The system implements feedback mechanisms where the ego vehicle continuously monitors and adjusts its interpretation of remote vehicle V2X messages based on observed behaviors and version differences. This feedback loop allows the system to compensate for version variations and improve the precision of future behavior predictions while maintaining version flexibility.
Data Source
AI summary
The disclosure includes embodiments for resolving vehicle application version differences for connected vehicles. A method includes determining a common vehicle application that is installed in both a remote connected vehicle and an ego vehicle and identifying version differences in a common vehicle application installed in both the ego vehicle and the remote connected vehicle. The method includes forming a vehicular micro cloud. The method includes determining a maximum possible functionality of the common vehicle application. The method includes determining a set of tasks to be completed to achieve the maximum possible functionality. The method includes assigning a first subset of the set of tasks to the ego vehicle and a second subset of the set of tasks to the remote connected vehicle. The method includes using the vehicular micro cloud to cause the ego vehicle to complete the first subset and the remote connected vehicle to complete the second subset.