Vehicle Automation Management via Intermediary Control Descriptions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing vehicle management systems require direct vehicle access, impose significant risks and costs due to software updates, and have limited functionality, making it difficult to expand access to vehicle functions while ensuring safety and reliability.

Innovation Solution

A vehicle system with a network of end points, including a controller that interprets automation descriptions to provide automated actions and responses, allowing entities to interact with vehicle functions without full vehicle knowledge or direct access, using a service-oriented architecture for efficient data management and feature implementation.

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 vehicle functionality can be updated, but significant risks and costs are introduced including vehicle shutdown requirements, software update failures, and high management expenses

Engineering Contradiction:

Improvevehicle functionality update capabilityVSAvoidvehicle operational reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary automation management system that sits between external entities and vehicle controllers. This system uses standardized automation descriptions and action plans to mediate vehicle function changes, eliminating the need for direct vehicle access or traditional OTA updates. The intermediary layer translates high-level automation descriptions into controller-specific commands, reducing risks while maintaining update capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the vehicle control architecture into distinct layers: automation description layer, action plan layer, and execution layer. This segmentation allows functionality updates to be made at the automation description level without requiring changes to underlying vehicle controllers or software, thereby maintaining reliability while enabling adaptability.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If traditional vehicle update systems are implemented, then vehicle functionality can be changed, but full vehicle knowledge and authority are required which increases costs and limits access

Engineering Contradiction:

Improveentity access to vehicle functionsVSAvoidvehicle knowledge requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal automation description interface that can be used by multiple entities (manufacturers, dealers, service providers, consumers) without requiring entity-specific vehicle knowledge. The standardized action plan format serves multiple functions: it describes automation logic, translates to controller commands, and manages execution, eliminating the need for different systems for different entities.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses automation descriptions as abstract copies or representations of vehicle control logic, separate from the actual controller implementation. These automation descriptions can be created, modified, and distributed without requiring knowledge of the underlying vehicle hardware or controller architecture, reducing complexity barriers while enabling broad access.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If more entities are given access to vehicle functions, then broader functionality implementation is enabled, but cost and risk increase due to safety regulations, vehicle complexity, and data sensitivity

Engineering Contradiction:

Improvenumber of entities with vehicle accessVSAvoidsafety and security risk

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The automation management system acts as a trusted intermediary that enforces safety and security policies between multiple entities and vehicle controllers. It validates automation descriptions against safety requirements, manages authentication and authorization, and controls data access, enabling multiple entities to access vehicle functions while maintaining safety and security standards.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where automation execution results and vehicle state information are monitored and reported back to the management system. This enables real-time validation of automation actions, detection of safety issues, and enforcement of access policies, reducing risks associated with multiple entities having vehicle access.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12573245B2System, method, and apparatus for managing vehicle automation

Publication Date: 2026.03.10 SONATUS INC

AI summary

A controller including an automation definition circuit, an automation management circuit, and an automation command circuit. The automation definition circuit is structured to implement an automation user interface, provide at least one automation recipe to the user interface, and interpret an automation request in response to user communications with the automation user interface. The automation management circuit is structured to determine an automation description in response to the automation request. The automation command circuit is structured to provide the automation description to a controller of a vehicle, where the controller of the vehicle is configured to implement an automated vehicle response, responsive to the automation description.