Vehicle Request Queue Cancellation Using Usage Conditions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing vehicle arbitration systems face challenges in managing a large number of requests from both onboard and external devices, leading to communication delays and the potential execution of unnecessary requests that may not be suitable for the vehicle's changing situation, causing user discomfort.

Innovation Solution

An onboard device and a center device are configured to receive operation requests and cancellation conditions, store these requests in queues, and determine whether to cancel them based on both application-defined and vehicle-state-related conditions, thereby avoiding the execution of unnecessary requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If operation requests are stored in queues for later execution, then request processing capacity is improved, but communication delays increase and requests may become unnecessary

Engineering Contradiction:

Improverequest processing capacityVSAvoidcommunication delays

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by storing operation requests in queues with associated cancellation conditions before execution. This allows the system to prepare for future execution while maintaining the ability to cancel requests if vehicle conditions change, thus improving processing capacity without permanently delaying critical operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system dynamically evaluates cancellation conditions associated with each queued request against current vehicle conditions before execution. This dynamic assessment allows the system to adaptively cancel requests that are no longer necessary, reducing effective communication delays for relevant operations while maintaining queue capacity for future processing.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If multiple requests from multiple application execution units are arbitrated and executed, then system versatility is improved, but device complexity increases

Engineering Contradiction:

Improvesystem versatilityVSAvoiddevice complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the arbitration process by introducing separate queues for different application execution units and implementing cancellation condition evaluation as a distinct preprocessing step. This segmentation simplifies the overall arbitration complexity by organizing requests into manageable segments with predefined cancellation criteria, while still supporting multiple application units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Cancellation conditions are preliminarily associated with each request during queue insertion, before arbitration occurs. This preliminary action simplifies the arbitration process by pre-filtering requests based on cancellation conditions, reducing the complexity of real-time decision-making during arbitration while maintaining support for multiple application execution units.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If requests are executed based on queue order, then processing efficiency is improved, but user comfort deteriorates due to execution of unnecessary requests

Engineering Contradiction:

Improveprocessing efficiencyVSAvoiduser comfort

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The system implements feedback by continuously monitoring vehicle conditions and comparing them against cancellation conditions associated with queued requests. This feedback mechanism allows the system to identify and cancel requests that are no longer necessary before execution, maintaining processing efficiency by only evaluating cancellation conditions for queued requests while preventing execution of unnecessary operations that would compromise user comfort.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

Cancellation conditions are preliminarily established for each request based on expected vehicle states. This preliminary action enables efficient processing by pre-defining cancellation criteria, allowing the system to quickly determine whether to execute or cancel requests without complex real-time analysis, thus maintaining processing efficiency while ensuring user comfort by avoiding unnecessary executions.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250187554A1Onboard device, center device, storage medium storing vehicle control program, and vehicle control method

Publication Date: 2025.06.12 DENSO CORP

AI summary

An onboard device mounted on a vehicle is configured to receive an operation request for the vehicle according to execution of application software and a first cancellation condition, which is a condition for canceling the operation request, from an application execution unit configured to execute the application software; store the operation request in a first queue; determine whether to cancel the operation request stored in the first queue according to the first cancellation condition and a second cancellation condition, which is a preset condition related to usage of the vehicle, for canceling the operation request; and delete the operation request from the first queue when it is determined that the operation request is to be canceled.