Vehicle Data Collection Automation via Endpoint Command Orchestration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle data management systems require direct access, are costly, and risky due to downtime and version management issues, with limited functionality and increased complexity from growing network demands and regulatory requirements, making it difficult for various entities to implement and interact with vehicle functions.

Innovation Solution

A system with a network of endpoints, including a controller with automation definition, management, and execution circuits, allowing for automated vehicle responses without direct vehicle access, enabling broader entity interaction and reducing costs by interpreting automation descriptions to provide automated action plans and commands.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If direct vehicle access or OTA software updates are used to update vehicle operational capabilities, then functionality can be changed, but vehicle downtime, update interruption risk, and management expenses increase

Engineering Contradiction:
Improvevehicle functionality change capabilityVSAvoidvehicle operational reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a cloud-based platform as an intermediary between vehicle users and the vehicle control system. This platform handles data collection, analysis, and command generation remotely, allowing functionality changes without direct vehicle access or software updates. The intermediary processes requests, generates appropriate commands, and transmits them to the vehicle, eliminating the need for downtime-prone OTA updates while maintaining the ability to change vehicle operational capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If more entities are given access to vehicle functions, then broader interaction is enabled, but system complexity and security risks increase

Engineering Contradiction:
Improveentity access to vehicle functionsVSAvoidsystem management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the vehicle system into distinct functional modules with defined interfaces. Each module handles specific operations (data collection, command execution, security verification) independently. This modular architecture allows multiple entities to access specific functions through standardized interfaces without increasing overall system complexity. The segmentation enables controlled access where different entities can interact with different modules based on their permissions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal platform that serves multiple entities with diverse needs through a single standardized interface. The cloud-based system provides multi-functional capabilities including data collection, analysis, command generation, and security verification, all accessible to different entities (manufacturers, dealers, service providers, consumers) through the same platform, thereby enabling broad access without proportionally increasing complexity.

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

3Productivity

If comprehensive data collection is implemented to support multiple entities and functions, then functionality and analytics are improved, but data security risks and management costs increase

Engineering Contradiction:
Improvedata analytics capabilityVSAvoiddata security risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by collecting and processing only the specific data needed for each function or entity, rather than uniformly collecting all possible data. The system determines data collection requirements based on the specific analytical needs of different entities and functions, thereby improving analytics capability for each use case while minimizing overall data collection volume and associated security risks.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20240326742A1System, method, and apparatus for managing vehicle data collection
Publication Date: 2024.10.03 SONATUS INC
  • US20240326742A1 patent drawing
  • US20240326742A1 patent drawing
  • US20240326742A1 patent drawing

AI summary

An apparatus for managing vehicle data collection. The apparatus includes a controller that includes an automation definition circuit, an automation management circuit, and an automation execution circuit. The automation definition circuit is structured to interpret an automation description from an external device. The automation management circuit is structured to provide an automated action plan in response to the automation description. The automation execution circuit is structured to provide an automation command in response to the automated action description. The automation command is structured to implement an automated vehicle response via an end point of a plurality of end points of a network of a vehicle.