Vehicle Data Network Criticality-Based Traffic Prioritization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional on-board networks in vehicles, such as CAN and LIN, are bandwidth-limited and cannot handle the increased data traffic generated by autonomous driving functions, leading to potential failures in critical situations like urban environments with many bicycles and surrounding vehicles, where intense network traffic can hinder the nominal operation of autonomous driving functions.
Innovation Solution
A data network management system that determines the criticality level of network traffic and adapts data flows by using an adapted flow configuration table to prioritize critical functions over non-essential ones, allowing bandwidth allocation based on predefined criticality levels, and switches between different network interfaces like Ethernet, CAN, and LIN to ensure reliable operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If Ethernet networks are used to increase bandwidth for autonomous driving functions, then data transmission capacity is improved, but network complexity increases due to coexistence with traditional networks
Solution Approach 1:
The network is segmented into multiple interfaces (first interface and second interface) with different criticality levels. Critical traffic is routed through the first interface while non-critical traffic uses the second interface, allowing the system to handle high data volumes without overwhelming the entire network infrastructure.
Solution Approach 2:
The system dynamically determines criticality levels based on real-time network conditions and traffic characteristics. The criticality determination unit adapts the routing decisions according to the current state, allowing the network to flexibly respond to changing demands while maintaining manageable complexity.
2Reliability
If all data flows are transmitted without restriction to maintain nominal operation, then service availability is improved, but network congestion increases under intense traffic conditions
Solution Approach 1:
Different quality levels are applied to different data flows based on their criticality. Critical flows receive prioritized handling with guaranteed bandwidth through the first interface, while non-critical flows are subjected to rate limiting or suppression through the second interface, ensuring service availability for essential functions while managing overall network throughput.
Solution Approach 2:
The system changes the transmission parameters of data flows based on determined criticality levels. This includes modifying bandwidth allocation, priority queues, and routing decisions dynamically, allowing the network to maintain reliability for critical services while optimizing overall productivity under varying traffic conditions.
3Quantity of substance
If non-critical data flows are suppressed to reduce network traffic, then bandwidth availability for critical functions is improved, but service functionality deteriorates
Solution Approach 1:
The suppression of non-critical flows is dynamic rather than static. The system continuously monitors network conditions and adjusts the level of suppression accordingly, ensuring that bandwidth is released for critical functions only when necessary, while maintaining service functionality under normal operating conditions.
Solution Approach 2:
The system implements feedback mechanisms to monitor the impact of flow suppression on service functionality. This allows the network to adapt its suppression strategy based on actual service performance, ensuring that bandwidth reallocation does not unnecessarily degrade user experience or service quality.
Data Source
Figure 1~2
Figure 3
AI summary
The invention relates to a data network installed on board a vehicle, said network comprising a first (ECU1) and at least one second equipment (ECU2, ECU3, ECU4) connected by at least one data link, said equipments (ECU1, ECU2, ECU3, ECU4) being able to transmit a plurality of data streams (F1, …, F10), characterized in that: - The first equipment (ECU1) is configured to determine a level of criticality according to network monitoring data and to transmit said level of criticality to said second equipment (ECU2, ECU3, ECU4), - The second equipment (ECU2, ECU3, ECU4) being configured to load, in response to receiving said level of criticality, a predefined stream configuration table, associated with said level of criticality, said table indicating which data streams are transmitted by said second equipment (ECU2, ECU3, ECU4).