Vehicle API Access Control Using Safety Level Authorization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle control systems fail to effectively restrict inappropriate access requests to APIs, particularly from authorized applications, leading to potential unsafe vehicle control operations, and the introduction of third-party applications may exacerbate this issue due to lack of knowledge among creators.

Innovation Solution

A vehicle control system with a coordination controller, policy storage, and access controller that determines access authorization based on a provision level and request level, ensuring only authorized functional blocks with sufficient safety levels can access safety-related functional interfaces, thereby preventing unexpected control and simplifying processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access control is not implemented, then applications can freely access APIs, but inappropriate access requests may cause unsafe vehicle control operations

Engineering Contradiction:
Improvevehicle control safetyVSAvoidaccess control system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

An access controller is introduced as an intermediary component between applications and APIs. The access controller receives access requests from applications, determines authorization based on provision level and request level comparison, and either transmits or discards the requests. This mediator prevents unsafe operations by blocking unauthorized access while maintaining system architecture simplicity through a centralized control point.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If third-party applications are introduced, then system versatility is improved, but inappropriate access requests may increase due to lack of creator knowledge

Engineering Contradiction:
Improveapplication ecosystem diversityVSAvoidaccess request safety
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system uses parameter-based authorization by comparing two key parameters: provision level (safety level guaranteed by the requesting application) and request level (safety level required by the target API). Third-party applications must declare their provision level, and the access controller automatically determines authorization by comparing this parameter against the API's request level requirement. This parameter-driven approach enables versatile application integration while maintaining safety through automated parameter comparison.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If authorization policy is set using provision level and request level, then access control precision is improved, but policy configuration complexity increases

Engineering Contradiction:
Improveaccess authorization precisionVSAvoidpolicy configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system establishes equipotentiality by creating a unified authorization policy framework where all applications and APIs operate under the same provision level and request level parameters. Instead of configuring individual access rules for each application-API pair, the system sets global parameter standards that automatically apply universally. The access controller simply compares these standardized parameters, eliminating the need for complex per-case policy configuration while maintaining high authorization precision.

Inventive Principle:
Principle #12Equipotentiality

Data Source

PatentUS20240411915A1Vehicle control system, access control device, and access control method
Publication Date: 2024.12.12 DENSO CORP
  • US20240411915A1 patent drawing
  • US20240411915A1 patent drawing
  • US20240411915A1 patent drawing

AI summary

A vehicle control system, an access control device or an access device control method determines whether to authorize access from a request source block to a request destination interface according to an authorization policy in response to an access request to the request destination interface, and transmits the access request to the request destination interface when access is authorized. The authorization policy is set using a provision level and a request level.