Vehicle Data Collection Across Policy-Governed Network Zones
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional vehicle communication networks face challenges with increasing device connectivity, data demand, latency, and regulatory compliance, leading to complex data management and increased costs due to the growing number of entities accessing vehicle data, which are not well-equipped to handle evolving network architectures and data access protocols.
Innovation Solution
A system comprising a remote access execution circuit, property translation circuit, parameter acquisition circuit, and parameter conditioning circuit to manage and regulate data access and communication between network zones, including a converged network device (CND) to enforce policies and manage actuator commands, while utilizing a policy acquisition circuit for selective data storage and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If more devices are connected to vehicle communication networks, then device connectivity and functionality are improved, but network complexity and data management burden increase
Solution Approach 1:
The patent segments the vehicle communication network into multiple network zones (first network zone and second network zone) with distinct communication protocols. The converged network device acts as a gateway between these zones, allowing each zone to operate with its own optimized protocol while maintaining overall system connectivity and managing complexity through structural division.
Solution Approach 2:
The converged network device serves as an intermediary between different network zones with incompatible communication protocols. It translates and bridges communications between zones, enabling diverse devices to connect without requiring all devices to support a single unified protocol, thus improving connectivity while managing complexity.
2Reliability
If data transmission requirements increase to meet performance and safety needs, then system performance is improved, but communication network burden and costs increase
Solution Approach 1:
The patent applies different communication protocols to different network zones based on their specific requirements. High-performance, low-latency protocols are used in zones requiring real-time control, while simpler protocols are used in zones with different requirements. This localized optimization meets performance needs without uniformly increasing network burden across the entire system.
3Adaptability or versatility
If more entities access vehicle data, then data utilization and functionality are improved, but data management complexity and regulatory compliance burden increase
Solution Approach 1:
The patent implements a unified data access interface that serves multiple entities with different data requirements through a single standardized protocol. This universal interface simplifies data management by providing a consistent access method regardless of the number or type of entities requesting data, thereby reducing management complexity despite increased data utilization capability.
4Adaptability or versatility
If legacy devices are maintained in the system, then system compatibility and deployment flexibility are improved, but network architecture complexity increases
Solution Approach 1:
The patent segments the network into zones that can operate with different protocols, allowing legacy devices using older protocols to remain in one zone while newer devices using advanced protocols operate in another zone. This segmentation enables coexistence of legacy and modern devices without requiring the entire network to support all protocol versions, managing architecture complexity through division.
Solution Approach 2:
The converged network device acts as a protocol translator and intermediary between legacy devices and modern network components. It converts communications between different protocol formats, enabling legacy devices to access the network without requiring changes to their hardware or software, thus maintaining compatibility while managing architectural complexity.
Data Source
AI summary
An apparatus including a vehicle event graphical user interface (GUI) configured to interpret a trigger description value from a user, the trigger description value including a trigger condition; a request circuit configured to determine a response action value in response to the trigger description value, the response action value including at least one of a vehicle data identifier configured to identify vehicle data to be captured in response to the trigger condition or an alert execution description to be transmitted in response to the trigger condition; and a cloud interface configured to receive at least one of: at least a portion of the identified vehicle data; or an alert response value determined in response to the alert execution description.