Vehicle Control Architecture for Cross-Function ECU Expansion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle systems require significant resources and manpower for development and design, as well as hardware and software customization for each product type, making it difficult to add or expand functions after shipment, especially when products have different functions.
Innovation Solution
A vehicle system comprising a vehicle device with common functions and an external device that operates independently, connected via a communication line, allowing the vehicle device to execute secondary functions through the external device, and vice versa, enabling shared hardware and software configurations across different product types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hardware and software customization is performed for each product type, then product functionality is improved, but development resources and manpower increase significantly
Solution Approach 1:
The patent applies universality by creating a common hardware platform and core software architecture that can serve multiple product types. The vehicle control device uses a standardized ECU architecture that can be configured for different vehicle types (battery vehicles, hybrid vehicles, conventional vehicles) without requiring complete customization, thus improving development efficiency while maintaining product functionality.
Solution Approach 2:
The patent segments the vehicle control system into modular components: a common core ECU, optional communication modules, and configurable software packages. This segmentation allows the base hardware to be reused across product types while only the necessary modules are added or configured for specific functionalities, reducing overall development resources.
2Adaptability or versatility
If hardware and software customization is performed for each product type, then product functionality is improved, but the complexity of development and design increases
Solution Approach 1:
The standardized ECU architecture serves as a universal base for multiple product types, reducing development complexity. The same core hardware platform can be used for battery vehicles, hybrid vehicles, and conventional vehicles by simply configuring different software packages and optional modules, rather than designing separate systems for each.
Solution Approach 2:
The system employs dynamic configuration capabilities where software packages and communication modules can be selectively enabled or disabled based on product type requirements. This dynamic approach allows a single hardware platform to adapt to different functionalities without increasing physical complexity, as the differentiation is achieved through software configuration rather than hardware redesign.
3Adaptability or versatility
If separate development is performed for each product type, then specific product requirements are met, but resource requirements and manpower increase
Solution Approach 1:
The patent merges the development efforts by consolidating common functionalities into a shared ECU platform and core software architecture. Development resources are focused on creating this universal base once, rather than separately developing complete systems for each product type. Optional modules and configurable software packages are then added as needed, significantly reducing overall development resources and manpower.
Solution Approach 2:
The universal ECU platform and standardized architecture allow the same development work to serve multiple product types. A single development team can support battery vehicles, hybrid vehicles, and conventional vehicles using the same base platform, reducing the quantity of development resources required compared to separate development approaches.
4Adaptability or versatility
If functions are added or expanded after shipment, then product adaptability is improved, but the difficulty of modification increases
Solution Approach 1:
The system enables post-shipment function expansion through dynamic software configuration. New functions can be added by updating software packages or enabling/disabling existing modules without requiring hardware modifications. The standardized communication interfaces and modular architecture allow for relatively easy system updates and expansions after the product has been deployed.
Solution Approach 2:
The system is designed with preliminary configurability in mind, incorporating optional communication modules and configurable software packages that can be activated later. This preliminary setup of modular components and standardized interfaces makes future modifications easier, as the infrastructure for expansion is already in place during initial design, reducing the difficulty of post-shipment function additions.
Data Source
AI summary
A vehicle system includes: a vehicle device having a first function that is commonly implemented regardless of a type of the vehicle system; and an external device that operates alone and independently from the vehicle device, has a second function that is selectively implemented in accordance with the type, and is connected to the vehicle device via a communication line. The vehicle device is configured to execute the second function via the external device. The external device is configured to execute the first function via the vehicle device.