Vehicle Swarm Data Aggregator for ADAS Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current method of transmitting data from vehicle driver assistance systems to an external backend computer using the pull principle results in high query volumes, increased latency, and data protection challenges due to continuous data reporting and direct GPS position sharing.

Innovation Solution

Implementing a method where ADAS data is stored in a vehicle-side swarm data aggregator, summarized, and transmitted only when needed, with anonymization and analysis triggered by a parameterizable analysis algorithm, reducing data transfer volume and optimizing data protection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous data reporting and direct GPS position sharing are used, then data availability and real-time monitoring are improved, but data transfer volume and latency increase

Engineering Contradiction:
Improvedata availabilityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-processes and stores ADAS data in a vehicle-side swarm data aggregator before external requests occur. This preliminary action allows the backend computer to quickly retrieve and analyze relevant data without waiting for continuous real-time reporting, thereby reducing latency while maintaining data availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts only the necessary GPS position information and specific ADAS data relevant to the analysis request, rather than transmitting all continuous data streams. This selective extraction reduces data transfer volume and processing latency while preserving the reliability needed for safety-critical analysis.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If all ADAS data is transmitted to the backend computer, then comprehensive analysis capability is improved, but data transfer volume and processing load increase

Engineering Contradiction:
Improveanalysis capabilityVSAvoiddata transfer volume
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by storing and pre-processing different types of ADAS data (geoinformation, traffic data, event data, status data) with different levels of detail and retention periods based on their specific characteristics and potential analytical value. This allows comprehensive analysis capability while optimizing data transfer volume by only transmitting relevant data.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments ADAS data into four distinct categories (geoinformation, traffic data, event data, status data) with different storage and transmission characteristics. This segmentation enables selective transmission of only the data segments relevant to specific analysis requests, reducing overall data transfer volume while maintaining comprehensive analysis capability when needed.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If GPS position data is shared directly with external users, then location-based service quality is improved, but data protection and privacy security worsen

Engineering Contradiction:
Improveservice qualityVSAvoidprivacy risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The backend computer acts as an intermediary between the vehicle's GPS position data and external users. It receives position information, processes it in the context of safety-critical analysis needs, and provides location-based services without directly exposing raw position data to external users. This maintains service quality while protecting privacy through controlled mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Speed

If data is stored in vehicle-side swarm data aggregator with decay time, then fast reaction time is achieved, but data retention period is limited

Engineering Contradiction:
Improvereaction timeVSAvoiddata retention period
Core Design Contradiction:
SpeedVSDuration of action of stationary object

Solution Approach 1:

The system implements dynamic data retention with decay time, where data is stored in the vehicle-side swarm data aggregator for a limited period and automatically removed after expiration. This dynamic approach enables fast reaction times for recent events while managing storage resources efficiently, and allows historical analysis by retrieving data from multiple vehicles' aggregators as needed.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3844936B1Requesting, analysing and transmitting data from driver assistance systems on a vehicle to an external user
Publication Date: 2022.08.10 VOLKSWAGEN AG
  • EP3844936B1 patent drawingFigure 1~2

AI summary

The invention relates to a method and an apparatus for requesting, analysing and transmitting data from driver assistance systems on a vehicle, hereinafter referred to as DAS data, to an external user, the method comprising the following steps: the sensors of the vehicle's driver assistance systems determining DAS data, - saving the DAS data in a vehicle-side swarm data aggregator, the DAS data in the swarm data aggregator being furnished with a disintegration time, - creating a summary of the DAS data saved in the swarm data aggregator, - transmitting the summary of the DAS data to a swarm memory of an external backend computer, - an analysis device of the backend computer analysing the summary of the DAS data, - the analysis device requesting the DAS data saved in the swarm data aggregator if the analysis of the summary shows that relevant DAS data is present in the swarm data aggregator, - transmitting the DAS data from the swarm data aggregator on the vehicle to the swarm memory of the backend computer on the basis of the request, and - transferring the DAS data from the swarm memory to the external user for further use.