Center ECU Package Architecture for Mixed ECU Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle control systems face challenges in efficiently updating application programs across ECUs of varying types and platforms due to differences in operating systems, requiring separate update methods for adaptive and classic platforms, which complicates the distribution of update data.
Innovation Solution
A centralized system generates integrated packages that accommodate both adaptive and classic platform ECUs, using a unified update method that includes software packages and verification data, enabling simultaneous update of mixed ECU types through a central ECU that relays data to individual ECUs based on their specific architectures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate update methods are used for adaptive and classic platform ECUs, then update compatibility is improved, but system complexity increases
Solution Approach 1:
The update package is segmented into multiple ECU-specific sub-packages, each tailored to specific ECU types (adaptive or classic platform). The center device identifies ECU types and distributes appropriate segments, enabling targeted updates without requiring completely separate update systems for different platforms.
Solution Approach 2:
A unified update package structure is designed that can serve multiple ECU types simultaneously. The package includes common components (manifest, verification data) and type-specific components (software packages for adaptive or classic platforms), allowing a single update mechanism to handle both adaptive and classic platform ECUs through a multi-functional package design.
2Productivity
If a unified update package is distributed to all ECUs, then distribution efficiency is improved, but update precision deteriorates
Solution Approach 1:
The unified update package is segmented into ECU-type-specific sub-packages containing only the relevant software updates for each ECU category. The manifest file includes segmentation information that enables the center device to identify and distribute only the necessary segments to each ECU, maintaining precision while using a unified distribution mechanism.
Solution Approach 2:
The manifest file acts as an intermediary between the unified update package and individual ECUs. It contains metadata about package contents, ECU type requirements, and verification data that enables the center device to precisely match update segments to appropriate ECUs, ensuring update precision without requiring separate distribution processes.
3Reliability
If multiple package structures are maintained for different platforms, then update reliability is improved, but device complexity increases
Solution Approach 1:
Multiple platform-specific package structures (adaptive platform with AUTOSAR AP and classic platform with AUTOSAR CP) are merged into a single unified update package. The package contains differentiated software segments for each platform type, along with unified verification data and manifest information, reducing the number of separate package management systems needed while maintaining platform-specific reliability requirements.
Solution Approach 2:
The update package structure is designed to be universal, supporting both adaptive and classic platform ECUs within the same package framework. The manifest file provides universal metadata structures that accommodate different platform types, and the verification data format is designed to work across platforms, enabling a single package structure to serve multiple functions and platform requirements.
Data Source
AI summary
A center device includes an individual vehicle information DB which stores device identity information and information regarding a software architecture of the relevant device together with a vehicle category for each of a plurality of ECUs. In a PKG structure DB, for each of the plurality of ECUs, information regarding a structure of a package to be distributed for data update is stored according to a type of each of the ECUs. Based on the information stored in the individual vehicle information DB and the PKG structure DB, a determination unit identifies a package to be distributed for a target vehicle having a target device whose data is updated among the plurality of ECUs, and a PKG generation unit generates a package including the information indicating the structure of the identified package.