Vehicle I/O Access Mapping for Cross-Node Device Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The flexibility and reliability of accessing various I/O devices with different types of interfaces and vendors by a centralized controller in intelligent vehicles are poor, leading to inefficient and costly updates and cross-node access.
Innovation Solution
Implement object-oriented modeling to generate standard models of I/O devices, creating a mapping configuration file that allows a centralized controller to send resource access requests based on these models, facilitating data conversion and shielding physical port types, thus enabling flexible and reliable access without requiring updates based on vendor, vehicle model, or interface changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a centralized controller directly accesses various I/O devices with different interfaces and vendors, then the system structure is simple, but the flexibility and reliability of device access are poor
Solution Approach 1:
The patent introduces a standard model as an intermediary layer between the centralized controller and diverse I/O devices. This standard model abstracts different vendor-specific interfaces and protocols into a unified access interface, allowing the controller to access various devices without direct vendor-specific implementations, thereby improving flexibility and reliability while maintaining manageable system complexity
Solution Approach 2:
The patent creates a universal standard model that can represent multiple types of I/O devices from different vendors through a common interface. This standard model serves multiple functions: it provides a unified access method for the controller, enables vendor-agnostic device access, and maintains a mapping relationship with physical devices, thus achieving versatility without proportionally increasing system complexity
2Productivity
If the system directly accesses I/O devices without standardization, then the development process is straightforward, but updates and cross-node access become inefficient and costly
Solution Approach 1:
The patent performs preliminary action by pre-defining standard models that encapsulate vendor-specific interface characteristics before actual device access occurs. These standard models are created in advance and stored in a database, allowing the system to handle updates and cross-node access efficiently without requiring development work at runtime, thus improving productivity while keeping development manageable through reusable templates
Solution Approach 2:
The patent uses copying by creating standardized virtual representations (standard models) of physical I/O devices. These standard models are copied templates that can be instantiated multiple times for different devices of the same type, enabling efficient updates and cross-node access through template-based approaches rather than device-specific implementations, thereby improving productivity without significantly increasing development complexity
3Adaptability or versatility
If vendor-specific interface implementations are used for each I/O device, then device compatibility is achieved, but software reuse and development efficiency decrease
Solution Approach 1:
The patent implements universality by designing a standard model that can represent multiple vendor-specific device types through a common interface structure. The standard model maintains vendor compatibility through mapping relationships while providing a unified access method, enabling software reuse across different vendors without requiring separate vendor-specific access code for each device type
Solution Approach 2:
The standard model acts as an intermediary that translates between vendor-specific interface protocols and a unified access interface. This mediator layer preserves device compatibility by maintaining mapping relationships with various vendor interfaces while shielding the controller from vendor-specific complexities, thus achieving compatibility without proportionally increasing software complexity
Data Source
AI summary
An input/output (I/O) device access method includes a first centralized controller that 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 further 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 further sends the resource access request to the first I/O device based on the mapping configuration file.