Vehicle ECU Middleware Mapping for Flexible Device Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hierarchical software architectures like AUTOSAR, changing device connections, signal modes, or information modes requires modifying the source code that invokes application programming interfaces (APIs) for device drivers, increasing software development man-hours.
Innovation Solution
An in-vehicle equipment controller with a middleware layer that includes a rewritable mapping table specifying communication packet relationships, allowing changes in connection destinations without modifying application interface code, and a vehicle control system with zone ECUs and a central processing unit that utilize this controller to reduce software development man-hours.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a hierarchical software architecture like AUTOSAR is used, then software structure and standardization are improved, but software development man-hours increase when device connections or signal modes are changed
Solution Approach 1:
The patent segments the software architecture into distinct layers (application layer, middleware layer, device driver layer) with a mapping table positioned in the middleware layer. This segmentation allows the mapping table to be independently modified without affecting other software components, thereby reducing development man-hours while maintaining architectural stability.
Solution Approach 2:
The mapping table acts as an intermediary between the application layer and the device driver layer. It absorbs the complexity of device connection changes, allowing applications to communicate with devices through standardized interfaces while the mapping table handles the variability of actual device connections, thus reducing the need to modify application code when devices change.
2Adaptability or versatility
If source code is modified to adapt to changed device connections or signal modes, then system adaptability is improved, but software development complexity increases
Solution Approach 1:
The patent extracts the device connection mapping information from the application source code and places it in a separate mapping table in the middleware layer. This extraction allows adaptability changes to be made by modifying only the mapping table content rather than altering application source code, thereby maintaining system adaptability while reducing software development complexity.
Solution Approach 2:
The mapping table stores connection parameters (device IDs, signal modes, I/O configurations) that can be changed without modifying the software structure. By changing these parameters in the mapping table, the system adapts to different device connections and signal modes, achieving adaptability while keeping development complexity low.
Data Source
AI summary
To reduce software development man-hours when vehicle models are developed an in-vehicle equipment controller includes a CPU and memory. The CPU has, as a software configuration, an application layer, a middleware layer, and a device driver. In the middleware layer, a first communication packet on the application side and a second communication packet on a device driver side are installed. In the middleware layer, a communication path between the application layer and the device driver is generated based on a mapping table stored in the memory.