Vehicle Software Update via Platform-Specific Containers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for software updates in vehicles with multiple electronic control units (ECUs) of different platforms are complex and lack standardization, making it difficult to provide consistent and reliable updates across various hardware and software platforms.
Innovation Solution
A method for updating software in vehicles that involves a controller receiving a container with multiple layers, including a software application layer, installation layer, and library layer, which are specifically designed for different ECU platforms. The controller determines the appropriate ECU platform and initiates the installation of the software application package using the installation program.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional software update methods are used for vehicles with multiple ECU platforms, then updates can be applied to specific ECUs, but the process becomes complex and lacks standardization across different platforms
Solution Approach 1:
The software update system is segmented into platform-specific containers that each encapsulate the necessary software packages, installation programs, and configuration information for a specific ECU platform. This segmentation allows the controller to selectively deploy appropriate containers to target ECUs without managing the complexity of multiple update formats simultaneously.
Solution Approach 2:
The container acts as an intermediary layer between the centralized controller and the diverse ECU platforms. Each container serves as a self-contained package that translates and adapts the update instructions into platform-specific formats, enabling standardized update communication across heterogeneous platforms while hiding the underlying platform differences.
2Manufacturing precision
If platform-specific update packages are maintained for each ECU type, then update precision can be maintained, but the quantity of update files and management overhead increases
Solution Approach 1:
The container format serves as a universal package structure that can encapsulate software updates for multiple different ECU platforms within a single standardized format. The controller can use a unified container management approach to handle updates for various platforms, reducing the number of separate update mechanisms while maintaining platform-specific precision through contained customization.
3Reliability
If comprehensive testing is performed before software installation, then reliability is improved, but the time required for installation increases
Solution Approach 1:
The container includes pre-packaged installation programs and configuration information that are prepared in advance during the software development cycle. The controller can directly execute these pre-tested installation programs without performing comprehensive testing at installation time, thereby maintaining reliability while reducing installation time.
Data Source
AI summary
A method of installing software in a vehicle including a controller and a number of electronic control units (ECUs) of different platforms. The method includes, at the controller, receiving a container associated with a platform of the different platforms used by at least one electronic control unit (ECU) of the number of ECUs. The container includes a number of container layers. The number of container layers includes at least a software application layer with a software application package installable at the platform. The method includes, at the controller, determining the at least one ECU using the platform among the number of ECUs. The method includes, at the controller, initiating installing the software application package at the at least one ECU.