Vehicle I/O Access Modeling for Flexible Centralized Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automotive electrical and electronic architectures face challenges with poor flexibility and reliability when accessing diverse I/O devices due to the need for adjustments based on different vendors, vehicle models, and interface types, especially in centralized controller systems.
Innovation Solution
Implementing object-oriented modeling to generate standard models of I/O devices and a mapping configuration file, allowing centralized controllers to send resource access requests based on these models, thereby converting data and facilitating access without requiring adjustments for different vendors or interface types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a centralized controller directly accesses various I/O devices with different interface types, then the controller can control all devices, but flexibility and reliability are poor due to the need for adjustments based on different vendors, vehicle models, and interface types
Solution Approach 1:
The patent introduces a gateway as an intermediary component between the centralized controller and diverse I/O devices. The gateway performs protocol conversion and data transformation, mediating between different interface types and the controller's standard interface. This resolves the contradiction by enabling the controller to access various devices without direct complexity, as the gateway handles the adaptation to different vendors, vehicle models, and interface types.
Solution Approach 2:
The system is segmented into distinct functional layers: the centralized controller layer, the gateway layer, and the I/O device layer. The gateway layer is further segmented into protocol adaptation modules and device driver modules. This segmentation isolates the complexity of interfacing with diverse devices from the controller, improving flexibility while managing complexity through modular architecture.
2Reliability
If a centralized controller directly accesses various I/O devices with different interface types, then the controller can control all devices, but reliability is poor due to the need for adjustments based on different vendors, vehicle models, and interface types
Solution Approach 1:
The gateway acts as a reliable intermediary that standardizes access to diverse I/O devices. It implements unified protocol conversion and error handling mechanisms, ensuring reliable communication regardless of the specific vendor, vehicle model, or interface type. This improves reliability by centralizing the complexity management in the gateway, which can maintain consistent access patterns across all devices.
Solution Approach 2:
The gateway is designed as a universal interface that can handle multiple I/O device types, protocols, and communication standards through its multi-functional architecture. It provides standardized data formats and control mechanisms that work across different vendors and vehicle models, improving reliability by eliminating the need for device-specific access logic in the controller.
3Adaptability or versatility
If different interface types are supported directly by the controller, then various I/O devices can be accessed, but development difficulty increases and software reuse decreases
Solution Approach 1:
The gateway serves as an intermediary that handles all interface-specific development complexity. It implements protocol adaptation layers and device drivers for different interface types (CAN, LIN, Ethernet, etc.), allowing the controller to use a single standardized interface. This reduces development difficulty by concentrating interface-specific code in the gateway, where it can be independently developed, tested, and reused across different vehicle models and applications.
Solution Approach 2:
The gateway implements a universal interface architecture that supports multiple I/O device types through a common control mechanism. This enables software reuse by allowing the same controller software to work with different devices by simply changing the gateway's configuration or device driver, rather than modifying the controller's access logic for each device type.
4Adaptability or versatility
If standardized models are introduced for I/O devices, then flexibility and reliability improve, but system complexity increases due to the mapping configuration layer
Solution Approach 1:
The patent creates standardized virtual models (copies) of I/O devices that represent their essential functions and data formats. These standardized models serve as abstraction layers that simplify controller access while maintaining the ability to represent diverse physical devices. The mapping configuration links these standardized models to actual devices, but the models themselves provide a uniform interface that improves flexibility without requiring the controller to handle device-specific complexities.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Embodiments of this application disclose an I/O device access method and apparatus. The method includes: A first centralized controller performs object-oriented modeling on various I/O devices in a vehicle, to generate standard models of the various I/O devices, and generate a mapping configuration file between the various I/O devices and the standard models. The first centralized controller generates a resource access request based on an access operation of a user, where the resource access request includes a first standard model of a first I/O device accessed by the user. The first centralized controller sends the resource access request to the first I/O device based on the mapping configuration file. According to the embodiments of this application, flexibility and reliability of accessing different types of I/O devices by a centralized controller can be improved.