Cross-Domain Access Exception Handling for Vehicle Safety

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In autonomous and assisted driving systems, cross-domain access between high and low security level domains can lead to system exceptions in the high security level domain if an exception occurs in the low security level domain.

Innovation Solution

A method and apparatus for cross-domain access that involves transmitting an access request, detecting the bus transmission status, generating an interrupt signal based on the status, and performing exception handling to restore access, ensuring normal operation of the high security level domain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cross-domain access is implemented between high and low security level domains, then data accessibility and system functionality are improved, but system reliability deteriorates because exceptions in the low security level domain can propagate to the high security level domain

Engineering Contradiction:
Improvedata accessibilityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

An exception management module is introduced as an intermediary between the low security level domain and high security level domain. This module intercepts exceptions from the low security level domain, performs classification and processing, and prevents unhandled exceptions from propagating to the high security level domain, thus maintaining system reliability while preserving cross-domain accessibility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The exception management module implements a feedback mechanism by monitoring bus transmission status, detecting exceptions, and responding with appropriate handling actions. This closed-loop feedback system ensures that exceptions are detected and processed in real-time, preventing their propagation to higher security domains

Inventive Principle:
Principle #23Feedback

2Productivity

If frequent cross-domain access occurs between high and low security level domains, then system functionality is improved, but the risk of exception propagation increases, worsening system reliability

Engineering Contradiction:
Improvesystem functionalityVSAvoidexception propagation risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The exception management module performs preliminary actions by setting up exception detection and handling mechanisms before cross-domain access operations occur. This proactive approach ensures that exceptions are managed as they arise, preventing their propagation to the high security level domain even during frequent access operations

Inventive Principle:
Principle #10Preliminary action

3Reliability

If exception handling mechanisms are added to prevent exception propagation, then system reliability is improved, but device complexity increases

Engineering Contradiction:
Improveexception prevention capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Exception handling functionality is extracted into a separate, dedicated exception management module. This modular approach isolates the complexity of exception handling from the main cross-domain access logic, making the system easier to manage and maintain while ensuring reliable exception prevention

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4557152A1Method and apparatus for cross-domain access, device, and medium
Publication Date: 2025.05.21 BEIJING HORIZON INFORMATION TECH CO LTD
  • EP4557152A1 patent drawingFigure 1~2
  • EP4557152A1 patent drawingFigure 3
  • EP4557152A1 patent drawingFigure 4

AI summary

Disclose are a method and an apparatus for cross-domain access, a device, and a medium. The method includes: transmitting an access request of a first component at a first security level to a second component at a second security level; detecting a bus transmission status of the second; generating an interrupt signal based on the bus transmission status, taking a preset result indicating the bus transmission status is in a preset status as an access result corresponding to the access request transmitted by the second component; performing exception handling corresponding to the interrupt signal, to restore access of the first component to the second. The access request of the first component can be ended normally, while no exception occurs due to effects of an exception of the bus transmission status of the second component; exception handling can be performed to restore cross-domain access of the first component to the second.