Policy-Driven Vehicle Data Collection Across Segmented Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional vehicle communication networks face challenges such as increased data demand, latency issues, and the need for higher performance buses, while also requiring segregation of network types and compatibility with legacy devices.
Innovation Solution
The implementation of a remote access execution circuit, property translation circuit, parameter acquisition circuit, parameter conditioning circuit, and converged network device (CND) to regulate communications between network zones, allowing for efficient data collection and management while maintaining network segregation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional vehicle communication networks are used, then network simplicity and legacy compatibility are maintained, but data collection efficiency and network performance deteriorate due to increased data demand and latency
Solution Approach 1:
A gateway device is introduced as an intermediary between traditional CAN bus networks and modern Ethernet networks. The gateway translates and routes data between these different network types, enabling efficient data collection from legacy devices while maintaining network segregation and avoiding the complexity of integrating all devices directly into a modern network architecture.
Solution Approach 2:
The vehicle network is segmented into distinct zones (e.g., driver information system zone, infotainment zone, telematics zone) separated by domain controllers and gateways. This segmentation allows each zone to operate independently with appropriate network types while maintaining overall system functionality, improving data collection efficiency without requiring complete network homogenization.
2Adaptability or versatility
If network types are segregated to maintain legacy compatibility, then compatibility with legacy devices is improved, but communication efficiency and data transfer speed deteriorate
Solution Approach 1:
Gateways serve as intermediaries that connect legacy CAN bus networks to high-speed Ethernet networks. These gateways maintain protocol compatibility for legacy devices while enabling efficient data transfer to modern systems, thus preserving legacy compatibility without sacrificing data transfer speed for critical data paths.
Solution Approach 2:
The architecture adds a hierarchical dimension by introducing multiple network layers (CAN bus layer for legacy devices, Ethernet layer for high-speed communication, and cloud layer for remote access). This dimensional approach allows data to be collected efficiently from legacy devices through the gateway and transmitted at high speed via Ethernet to processing or storage systems.
3Quantity of substance
If higher performance buses are implemented to meet data demand, then data collection capability is improved, but system complexity and integration cost increase
Solution Approach 1:
The system segments data collection functions across multiple domain controllers and gateways, each handling specific zones or device types. This segmentation allows high data collection capability to be achieved through distributed processing rather than requiring a monolithic high-performance bus throughout the entire vehicle, reducing overall system integration complexity.
Solution Approach 2:
Multiple network types (CAN, LIN, Ethernet) are merged into a unified architectural framework managed by domain controllers and gateways. This merging approach enables the system to leverage the strengths of each network type for specific purposes while presenting a unified interface for data collection, improving overall capability without proportionally increasing complexity.
Data Source
AI summary
An apparatus including a policy acquisition circuit structured to interpret a vehicle policy data value comprising at least one of a driver information description, a device condition description, an end point performance description, or a location description value; a policy processing circuit structured to generate, in response to and based at least in part on the vehicle policy data value, parsed policy data that comprises a vehicle data collection description; and a policy execution circuit structured to collect vehicle data from one or more end points of at least one network zone of a vehicle in response to the parsed policy data.