Vehicle Endpoint Automation Control for Indirect Function Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle management systems require direct vehicle access, impose significant risks and costs, and have limited functionality, especially with increasing vehicle complexity and the need for broader entity access to vehicle functions.

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.

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, update interruption risks, and management expenses

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

Solution Approach 1:

The patent introduces an intermediary update service provider that acts as a mediator between the vehicle owner and the vehicle controller. This intermediary receives update requests, determines appropriate update parameters, and transmits them to the vehicle controller without requiring direct access to the vehicle's internal systems. This resolves the contradiction by enabling functionality updates while maintaining vehicle reliability through controlled, indirect update mechanisms that avoid shutdown risks and interruption vulnerabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the vehicle update system into distinct functional components: the vehicle controller that manages actual updates, the update service provider that processes requests and determines parameters, and the vehicle owner who initiates requests. This segmentation allows update functionality to be implemented without requiring the entire vehicle system to be accessible or shut down, thereby maintaining reliability while enabling adaptability.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If full vehicle knowledge and authority are required to perform updates or changes, then vehicle control precision is maintained, but significant costs and limited functionality are imposed

Engineering Contradiction:
Improvevehicle control precisionVSAvoidentity access capability
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The update service provider serves as an intermediary that possesses vehicle knowledge and authority without requiring the entity performing the update (vehicle owner or third party) to have full vehicle knowledge. The intermediary translates high-level update requests into precise control parameters that the vehicle controller can execute, thereby maintaining control precision while expanding access capability to broader entities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a virtual representation or copy of the vehicle's update management functionality within the update service provider. This copy includes knowledge of vehicle parameters, controllers, and memory locations, allowing the intermediary to generate precise update commands without the external entity needing direct knowledge of the vehicle's internal architecture. This resolves the contradiction by decoupling knowledge requirements from access rights.

Inventive Principle:
Principle #26Copying

3Reliability

If multiple versions of software are kept available in case of update failure, then vehicle reliability is maintained, but significant management expense is imposed

Engineering Contradiction:
Improvevehicle operational reliabilityVSAvoidsoftware version storage requirement
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The update service provider acts as an intermediary that manages software version storage and retrieval externally, rather than requiring the vehicle to maintain multiple versions internally. The intermediary can store backup versions, manage rollback procedures, and coordinate update failures without consuming the vehicle's limited storage resources. This resolves the contradiction by externalizing the software version management burden, maintaining reliability while reducing the quantity of software versions that need to be physically present in the vehicle.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If vehicle complexity increases with more sensors, actuators, and controllers, then vehicle capability is enhanced, but the burden on vehicle communication networks increases

Engineering Contradiction:
Improvevehicle capabilityVSAvoidcommunication network burden
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The update service provider serves as an intermediary that simplifies communication with the complex vehicle network. Instead of requiring external entities to directly communicate with multiple sensors, actuators, and controllers across different networks, the intermediary receives high-level requests and translates them into appropriate commands for the specific vehicle architecture. This resolves the contradiction by shielding the vehicle's internal communication complexity from external interactions while maintaining enhanced vehicle capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12528442B2System, method, and apparatus for managing vehicle data collection
Publication Date: 2026.01.20 SONATUS INC
  • US12528442B2 patent drawing
  • US12528442B2 patent drawing
  • US12528442B2 patent drawing

AI summary

A system including a vehicle having a network comprising a plurality of end points and a controller, where the controller 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. 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 plan, where an end point of the plurality of end points is responsive to an automation command to implement an automated vehicle response.