Software Distribution via Vehicle-to-Vehicle Network
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for distributing software to motor vehicles are inefficient, as traditional manual updates are time-consuming and unreliable, while over-the-air updates require extensive and costly server and infrastructure capabilities that are underutilized.
Innovation Solution
The software is split into multiple parts, distributed across a network-connected data server, and then transmitted between motor vehicles, with each vehicle acting as a temporary server to exponentially spread the software, reducing server capacity needs and enabling efficient distribution to a large number of vehicles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a server and data distribution infrastructure is used to distribute software over the air to all vehicles, then software distribution can reach all target vehicles, but the server and infrastructure become idle and unused until the next software update, requiring extensive and costly capabilities to handle peak demand
Solution Approach 1:
The software is divided into multiple parts that are distributed to different first generation motor vehicles. Each part is independently distributable and can be reassembled at the target vehicle, allowing the distribution load to be segmented across multiple vehicles rather than requiring a single powerful server to handle the complete software package.
Solution Approach 2:
Each motor vehicle that receives a part becomes a temporary distribution server for that part to other vehicles. This self-service mechanism allows vehicles to actively participate in the distribution process, reducing the burden on the central data server and eliminating the need for extensive server infrastructure capable of handling all distribution simultaneously.
2Device complexity
If manual updating of each motor vehicle is performed individually during servicing or repair, then software can be updated without requiring extensive server infrastructure, but the process takes an undesirably long time and is not guaranteed to reach all target vehicles
Solution Approach 1:
By segmenting the software into multiple parts and distributing them through multiple first generation vehicles simultaneously, the overall distribution process becomes parallel rather than sequential. This dramatically increases distribution productivity compared to manual updating while avoiding the need for extensive server infrastructure.
Solution Approach 2:
The approach merges the advantages of both manual updating (no extensive server infrastructure needed) and over-the-air distribution (ability to reach all vehicles efficiently). By combining vehicle-to-vehicle communication with part-based distribution, the system achieves fast distribution across the entire fleet without requiring a powerful central server.
3Productivity
If the software is divided into multiple parts and distributed through vehicle-to-vehicle connections, then distribution speed and capacity utilization are optimized, but each vehicle must receive and store multiple parts before assembly
Solution Approach 1:
A coordination server receives acknowledgments from vehicles that have received parts and uses this feedback information to manage the distribution process. The coordination server tracks which vehicles have which parts and coordinates the assembly process, reducing the complexity burden from individual vehicles to a centralized management system that handles only metadata and coordination, not the actual software distribution load.
Solution Approach 2:
The coordination server acts as an intermediary between the data server and the fleet of vehicles. It manages the complex coordination of part distribution and assembly without requiring the data server to handle individual vehicle communications or the vehicles to independently manage the entire distribution logic, thus reducing overall system complexity.
Data Source
AI summary
The present invention relates to a method for distributing a software (2) to a plurality of motor vehicle (4, 7), as well as a corresponding system, motor vehicle (4, 7), and data storage medium. The software (2) is divided into multiple parts (3), which are delivered from a data server (1) to a set of first generation motor vehicles (4). For each part (3), the respective motor vehicle (4, 7) sends an acknowledgement of receipt to a coordination server (6), which then sends out a notification of availability for the part (3) to a second generation motor vehicle (7). This second generation motor vehicle (7) downloads the part (3) from the motor vehicle (7) that previously sent the acknowledgement of receipt. This process iteratively continues until all of the plurality of motor vehicles (4, 7) have received all parts (3) of the software (2).