Model-Based Safety Testing Using Multi-Logic Requirement Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing model-based safety analysis methods for technical systems lack an efficient and automated means to evaluate safety requirements, particularly in complex systems with software and hardware components.

Innovation Solution

A method and device that convert safety requirements into formal expressions using selected formal logics based on properties, employing program solvers to check compliance, with the ability to adapt models for improved evaluation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If model-based safety analysis is performed manually or with basic automation, then evaluation completeness may be maintained, but evaluation speed and efficiency are insufficient

Engineering Contradiction:
Improveevaluation speedVSAvoidanalysis system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces manual model-based safety analysis with an automated computer-implemented method. The system automatically converts natural language safety requirements into formal logic expressions and uses program solvers to verify compliance, eliminating manual evaluation while maintaining thoroughness and significantly improving speed.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces formal logic expressions as an intermediary between natural language requirements and verification. This intermediary layer enables automated reasoning and solving, bridging the gap between human-readable requirements and machine-executable verification processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If multiple formal logics are used to cover different requirement properties, then coverage and precision improve, but system complexity increases

Engineering Contradiction:
Improverequirement verification precisionVSAvoidformal logic system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the verification process by applying different formal logics to different types of requirement properties. Boolean expressions use one logic type, temporal aspects use another, and probability aspects use a third. This segmentation allows precise handling of each property type while managing overall system complexity through modular processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of formal logic selection based on the properties of the requirements being verified. The system dynamically selects appropriate formal logics from a logic set based on whether the requirement involves Boolean expressions, temporal aspects, or probability, optimizing precision for each case.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If automated program solvers are employed for verification, then evaluation speed increases, but handling of complex formal expressions becomes challenging

Engineering Contradiction:
Improveverification speedVSAvoidformal expression complexity
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments complex safety requirements into smaller formal expressions that can be individually processed by program solvers. By breaking down large requirements into manageable formal logic components, the system maintains verification speed while reducing the difficulty of handling each individual expression.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses formal logic expressions as intermediaries that translate complex natural language requirements into a structured format suitable for automated solving. This intermediary representation makes complex requirements more tractable for program solvers while preserving the original meaning and verification goals.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12524621B2Method, device and computer program for testing a technical system based on a model
Publication Date: 2026.01.13 ROBERT BOSCH GMBH
  • US12524621B2 patent drawing
  • US12524621B2 patent drawing

AI summary

A computer-implemented method for testing an, in particular, safety-relevant, technical system, in particular including software and/or hardware components. The method includes the following steps: providing a model of the technical system; providing a set of requirements to the technical system; converting a particular requirement into at least one formal expression of at least one formal logic, the formal logic being selected from a logic set, which includes at least two formal logics, based on properties of the requirements; checking whether a particular requirement has been met by the model, the checking taking place by carrying out at least one program solver for a particular formal expression.