Vehicle Software Update Gateway Using Cross-Platform Pseudo Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software update systems struggle to efficiently manage and update software across multiple platforms in a vehicle system, leading to scalability issues and complex arbitration requirements as the number of platforms increases.
Innovation Solution
A software update device and system that includes a first update control unit for one platform and a second update control unit that simulates and controls software updates for another platform, allowing flexible software updates across different platforms through pseudo execution and sequence management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each software update device independently updates software in one platform with arbitration performed by an update trigger, then software update control is achieved, but it becomes difficult to address multiple platforms with one software unit and scalability deteriorates
Solution Approach 1:
The software update device is designed to perform software updates for multiple different platforms (first platform, second platform, etc.) using a single device. The device includes multiple update control units, each capable of controlling software updates for specific platforms, enabling one device to serve multiple platform update needs without requiring separate dedicated update devices for each platform.
Solution Approach 2:
The patent employs a pseudo update execution unit that simulates a software unit on a different platform (second platform) as if it were on the first platform. This copying approach allows the first update control unit to manage updates for software units on the second platform through simulation, reducing the need for additional dedicated control units for each platform.
2Adaptability or versatility
If the number of platforms and update methods increase, then platform coverage improves, but additional control units must be added and arbitration becomes complicated
Solution Approach 1:
The patent introduces a sequence control unit as an intermediary between the first update control unit and the first software unit. This sequence control unit manages the update sequence and coordinates operations, simplifying the arbitration process when multiple platforms and update methods are involved. The sequence control unit handles the complexity of coordinating updates across different platforms without requiring complex arbitration logic in each update control unit.
3Quantity of substance
If a single software update device manages multiple platforms, then device quantity is reduced, but the complexity of managing different platforms increases
Solution Approach 1:
The software update device is segmented into multiple independent update control units, each responsible for specific platforms or software units. This segmentation allows the device to manage multiple platforms by dividing the management task into smaller, specialized units (first update control unit, second update control unit, etc.), reducing the overall complexity of platform management while maintaining multi-platform capability.
Solution Approach 2:
The pseudo update execution unit creates a simulated environment for software units on different platforms, allowing the update device to manage multiple platforms through simulation rather than requiring completely separate management systems for each platform. This copying approach simplifies the management of platform differences.
Data Source
AI summary
A software update device (gateway) 10 includes a first update control unit 140 that performs software update for a first software unit (for example, an ECU_A 13 and an ECU_B 16) and a second update control unit 150 that performs software update for a second software unit (for example, an ECU_C 17 and an ECU_D 19). Also, the first update control unit 140 includes a first sequence control unit 141 that transmits a control command directed to a first platform, and the second update control unit 150 includes a pseudo update execution unit 151 that simulates the second software unit as a software unit on the first platform and performs the software update for the second software unit on the basis of reception of a control command for the second software unit simulated on the first platform.