Connected Vehicle App Version Coordination Before Shared Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Connected vehicles often experience compatibility issues due to mismatched application versions, which can lead to improper coordination of maneuvers when different vehicles have incompatible software applications.
Innovation Solution
A system and method that determine the expected presence of vehicles at a location and compare their application versions, adjusting them as necessary to ensure compatibility by upgrading, downgrading, or replicating versions using vehicle-to-vehicle or vehicle-to-everything communication to maintain consistent application versions before an event.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If vehicles receive over-the-air updates independently, then each vehicle can be updated without service interruption, but application version mismatches occur between vehicles
Solution Approach 1:
The system performs preliminary actions by determining the expected presence of vehicles at event locations before updates are applied. It identifies vehicles that will be present within a predetermined distance of an event location, compares their application versions, and coordinates updates in advance. This preliminary coordination ensures version compatibility is established before vehicles actually meet at the event, preventing compatibility issues during critical operations.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring application versions across the vehicle fleet and comparing versions between vehicles expected to interact. When version mismatches are detected, the system provides feedback to coordinate updates, ensuring that vehicles maintain compatible versions. This feedback loop maintains reliability while allowing independent over-the-air updates.
2Reliability
If application versions are synchronized across all vehicles, then compatibility is maintained, but update flexibility and responsiveness are reduced
Solution Approach 1:
The system applies local quality by coordinating application updates based on local vehicle presence and event-specific requirements rather than enforcing uniform synchronization across the entire fleet. It determines updates needed for specific vehicles based on their expected presence at particular event locations, allowing different vehicles to have different update timings while maintaining compatibility where needed. This enables flexible, targeted updates that adapt to local conditions.
Solution Approach 2:
The system performs preliminary version comparison and coordination actions before vehicles reach event locations. By anticipating which vehicles will be present and comparing their versions in advance, the system can coordinate updates proactively, maintaining compatibility without requiring all vehicles to be synchronized at all times. This preliminary action enables both flexibility in update timing and reliability in version compatibility.
3Reliability
If version comparison and coordination is performed for all vehicle pairs, then complete compatibility is ensured, but computational complexity and communication overhead increase
Solution Approach 1:
The system segments the vehicle fleet into groups based on expected presence at specific event locations. Rather than performing version comparisons for all possible vehicle pairs across the entire fleet, it divides the problem into location-specific segments, comparing versions only among vehicles expected to be present within a predetermined distance of each event location. This segmentation dramatically reduces computational complexity while ensuring compatibility for vehicles that actually need to interact.
Solution Approach 2:
The system performs version comparisons and coordination actions preliminarily, before vehicles reach event locations. By determining expected presence and comparing versions in advance, the system avoids the need for complex real-time comparisons when vehicles are already at the event. This preliminary action simplifies the overall system complexity by handling version coordination proactively rather than reactively.
Data Source
AI summary
A method may include determining whether a plurality of vehicles, each having an application installed are expected to be present within a predetermined distance of a location of an event. The method may further include comparing versions of the applications among the plurality of vehicles and, in response to determining that the plurality of vehicles are expected to be present within the predetermined distance of the location and determining that the versions of the applications among the plurality of vehicles are different, adjusting a version of the application installed in one or more of the plurality of vehicles.