Vehicle Data Collection Policies for Mixed-Network Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle communication networks face challenges with increasing data demands, regulatory complexities, and integration costs due to the segregation of network types, limited customization, and data management issues, particularly in mixed network environments.

Innovation Solution

The system employs configurable data collection by adjusting communication routing, implementing triggers, managing shared storage, and applying policies to enhance data collection and storage operations, including flexible policy implementation and data compression techniques.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional vehicle communication networks (CAN, LIN, FlexRay) are used, then robust and dedicated equipment with specific data protocols is available, but data collection costs increase and network integration is limited due to segregation of network types and limited customization

Engineering Contradiction:
Improvenetwork integrationVSAvoidnetwork types segregation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway as an intermediary device that bridges different vehicle network types (CAN, LIN, FlexRay, Ethernet). The gateway translates protocols and routes data between segregated network segments, enabling integrated data collection without requiring uniform network infrastructure across the vehicle. This resolves the contradiction by providing adaptability across network types while maintaining the simplicity of individual network segments.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements a universal data collection framework that can interface with multiple network types through standardized protocols and configurable routing. The gateway and data collection system perform multiple functions: protocol translation, data routing, filtering, and aggregation across different network domains, eliminating the need for separate dedicated systems for each network type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If higher performance buses are implemented to meet increasing data rate demands, then data collection capability improves, but integration costs and re-certification burdens increase

Engineering Contradiction:
Improvedata collection capabilityVSAvoidintegration costs
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The patent implements dynamic data routing and configurable collection parameters that can be adjusted at runtime without hardware changes. The system dynamically selects optimal data paths based on network conditions, device capabilities, and collection requirements, allowing high data rate capability through software configuration rather than requiring expensive hardware upgrades for every application scenario.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters (data rate, routing paths, collection frequency) through software configuration rather than hardware redesign. This allows the same physical infrastructure to support varying data collection capabilities by adjusting parameters, thereby avoiding integration costs and re-certification burdens associated with hardware changes.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If more devices and data rate demand increase, then vehicle features and connectivity improve, but latency increases and network burden increases

Engineering Contradiction:
ImproveconnectivityVSAvoidlatency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the data collection process into multiple stages: local data filtering at devices, selective routing through gateways, and prioritized transmission to destinations. This segmentation allows critical data to be processed locally without waiting for network transmission, reducing perceived latency while maintaining connectivity to all devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements feedback mechanisms where network conditions and device priorities are continuously monitored and used to dynamically adjust data routing decisions. This feedback loop optimizes latency by directing time-sensitive data through lowest-latency paths while maintaining overall connectivity as network conditions change.

Inventive Principle:
Principle #23Feedback

4Ease of operation

If data collection operations expand to meet consumer expectations for connectivity and reduced driver burden, then vehicle features improve, but regulatory compliance complexity increases

Engineering Contradiction:
Improvedriver burdenVSAvoidregulatory compliance
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements self-service data collection where the system automatically determines what data to collect, where to route it, and how to manage it based on pre-configured policies and real-time conditions. This automated self-service approach reduces driver burden by eliminating manual data collection tasks while managing regulatory compliance through systematic, auditable processes without requiring complex manual intervention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260045124A1System, method, and apparatus for configurable vehicle data collection
Publication Date: 2026.02.12 SONATUS INC
  • US20260045124A1 patent drawing
  • US20260045124A1 patent drawing
  • US20260045124A1 patent drawing

AI summary

An apparatus may include a policy acquisition circuit configured to interpret a vehicle policy data value comprising a data collection description. A device may include a policy processing circuit configured to generate parsed policy data corresponding to the data collection description, and to determine a memory allocation value in response to the parsed policy data. A device may include a policy execution circuit configured to collect vehicle data from one or more vehicle end points in response to the parsed policy data, and to store at least a portion of the collected vehicle data in response to the memory allocation value.