Centralized Vehicle Storage With Interface Switching and Data Priority
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices in autonomous vehicles lack efficient data processing and cyber security measures to manage diverse vehicle data types and communication interfaces, necessitating a centralized storage solution that supports multiple vehicle communication protocols and prioritizes data access based on security and speed requirements.
Innovation Solution
A centralized storage device with a controller configured for SR-IOV functions, supporting multiple vehicle communication interfaces like Ethernet and CAN, and implementing data transfer protocols to manage data access based on priority and security levels, using NVMe-oF and CAN interfaces, and employing redundancy strategies like SLC and TLC to ensure data integrity and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a centralized storage device supports multiple vehicle communication interfaces (CAN, LIN, FlexRay, MOST, Ethernet), then the adaptability and versatility of the storage device is improved, but the device complexity increases due to the need for multiple interface circuits and conversion mechanisms
Solution Approach 1:
The patent introduces an interface switch as an intermediary component between the centralized storage device and multiple vehicle communication interfaces (CAN, LIN, FlexRay, MOST, Ethernet). The interface switch includes multiple interface circuits that convert different vehicle communication protocols into a unified internal protocol, allowing the storage device to support multiple interfaces without directly implementing complex multi-interface circuitry. This mediator approach resolves the contradiction by enabling broad interface compatibility while isolating the complexity within the switch component.
2Ease of operation
If the storage device processes different types of vehicle data (autonomous driving, navigation, infotainment) with equal priority, then the ease of operation is improved, but the productivity decreases due to lack of optimized data handling
Solution Approach 1:
The patent implements local quality by assigning different priority levels to different types of vehicle data processed by the storage device. The controller identifies data types (autonomous driving, navigation, infotainment, EDR) and applies differentiated processing priorities, where critical safety-related data receives higher priority than non-critical infotainment data. This allows the system to maintain simple operation while significantly improving productivity by optimizing data handling based on local data characteristics and requirements.
3Reliability
If the storage device implements uniform redundancy strategies for all data, then the reliability is improved, but the loss of substance increases due to unnecessary redundancy storage
Solution Approach 1:
The patent applies local quality by implementing differentiated redundancy strategies based on data characteristics and security requirements. The controller categorizes data into different security levels (e.g., autonomous driving data, navigation data, infotainment data) and applies appropriate redundancy measures to each category. Critical safety-related data receives higher redundancy protection, while non-critical data uses minimal or no redundancy. This resolves the contradiction by maintaining high reliability for critical data while minimizing unnecessary storage consumption for non-critical data.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
The present disclosure provides methods, apparatuses, and systems for centralized storage devices (100). In some embodiments, an in-vehicle electronic system includes a centralized storage device (100), and an interface switch (200) coupled to the centralized storage device (100) through a first interface (127), coupled to at least one domain control unit (DCU) through a first vehicle communication interface (CH11), and coupled to at least one electronic control unit (ECU) through a second vehicle communication interface (CH2). The interface switch (200) includes an interface circuit (270) configured to communicate according to the first interface (127), and an interface converter (210) configured to convert the first vehicle communication interface (CH11) into the first interface (270) and to convert the second vehicle communication interface (CH21) into the first interface (270).