Integrity Level System for Subsystem Interference Prevention

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Complex system modeling tools face challenges in preventing unintended interference between subsystem blocks, which can lead to critical malfunctions, as the complexity of models increases, making it essential to ensure that non-critical subsystems do not inadvertently affect mission-critical ones.

Innovation Solution

The introduction of an integrity level system for subsystem blocks and their interfaces, combined with type-checking, to enforce rules that reduce interference by ensuring that computational behavior is only influenced by subsystems of equal or higher integrity levels, thereby preventing unintended interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the complexity of system models increases, then the modeling capability is improved, but the likelihood of unintended interference between subsystem blocks increases

Engineering Contradiction:

Improvemodeling capabilityVSAvoidinterference between subsystem blocks

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent divides the system into subsystem blocks with distinct integrity levels (e.g., high integrity for safety-critical subsystems, low integrity for non-critical subsystems). This segmentation allows the system to handle increased complexity while preventing interference between different subsystems by isolating them based on their integrity levels.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of integrity level checking and type-checking systems that mediate between subsystem blocks. These intermediaries detect and prevent unauthorized interactions between subsystems of different integrity levels, thereby maintaining reliability as complexity increases.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If non-critical subsystems are allowed to influence critical subsystems, then system flexibility is improved, but system safety is compromised

Engineering Contradiction:

Improvesystem flexibilityVSAvoidimpact on critical subsystems

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary anti-action by implementing integrity level annotations and type-checking mechanisms that prevent non-critical subsystems from influencing critical subsystems before any harmful interaction can occur. The system proactively blocks potentially harmful connections based on integrity level mismatches.

Inventive Principle:

Principle #9Preliminary anti-action

Solution Approach 2:

The patent assigns different integrity levels to different subsystem blocks, creating local quality distinctions. High integrity subsystems are isolated from low integrity subsystems, allowing the system to maintain flexibility in non-critical areas while protecting critical areas from harmful influences.

Inventive Principle:

Principle #3Local quality

3Reliability

If integrity level checking is implemented for all subsystem connections, then interference prevention is improved, but design time complexity increases

Engineering Contradiction:

Improveinterference preventionVSAvoiddesign time complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by annotating subsystem blocks with integrity levels during the design phase and implementing type-checking mechanisms that automatically verify connections. This preliminary setup ensures interference prevention is built into the model structure itself, reducing the need for additional verification steps during execution.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service through automatic type-checking and integrity level verification mechanisms that self-validate connections between subsystem blocks. The system automatically detects and reports integrity level mismatches without requiring manual intervention, thereby reducing design time complexity while maintaining reliable interference prevention.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8938710B2Preventing interference between subsystem blocks at a design time

Publication Date: 2015.01.20 MATHWORKS INC

AI summary

A method of preventing interference between subsystem blocks includes obtaining an integrity level for a first subsystem block, obtaining an integrity level for a second subsystem block, assigning an integrity level property to at least one input port of the first block, the integrity level property assigned to the input port of the first block being based on the integrity level defined for the first block, and assigning an integrity level property to at least one output port of the second block, the integrity level property assigned to the output port of the second block being based on the integrity level defined for the second block. The method further includes evaluating the integrity level property of at least one input/output pair to determine whether an inappropriate connection exists, and performing a first action when an inappropriate connection exists, or performing a second action when an appropriate connection exists.