Technical System Validation Using Probabilistic Output Bounds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex technical systems with intricately linked components are challenging to validate or verify due to their stochastic and complex nature, making it difficult to predict and guarantee desired behavior, especially in systems of systems where complexity grows rapidly.

Innovation Solution

A computer-implemented method that determines the probability of a technical system fulfilling a desired criterion by obtaining models for components, their connections, validation measurements, and test outputs, and propagating discrepancies to establish upper or lower bounds of system outputs, allowing for verification and validation without the need for extensive real-world data collection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional validation methods are used for complex technical systems, then extensive real-world data collection is required, but the time and resources needed increase significantly

Engineering Contradiction:
Improvevalidation accuracyVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing validation during the design phase using simulated environments before deploying to real-world conditions. Test beds and simulations are set up in advance to validate system behavior, allowing issues to be identified and corrected early without requiring extensive real-world data collection later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating virtual copies of real-world environments through simulations and test beds. These digital twins or simulated environments replicate actual operating conditions, allowing validation to be performed on copies rather than requiring extensive physical testing with real systems in real-world settings.

Inventive Principle:
Principle #26Copying

2Reliability

If complex systems with intricately linked components are validated using traditional methods, then comprehensive coverage is achieved, but the complexity of validation processes increases rapidly

Engineering Contradiction:
Improvevalidation completenessVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the complex validation process into modular components: system-level validation, component-level validation, and interface validation. Each segment can be independently configured and executed, allowing comprehensive coverage of complex systems while managing validation complexity through structured organization of validation activities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses parameter changes by allowing dynamic configuration of validation parameters such as test cases, expected outcomes, and tolerance thresholds. The validation system can adjust parameters based on system complexity, enabling comprehensive validation of intricate systems while adapting the validation approach to match the specific complexity level of each system being validated.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If statistical validation frameworks are used for systems with changing parameter configurations, then adaptability is improved, but the computational requirements increase

Engineering Contradiction:
Improveparameter configuration flexibilityVSAvoidcomputational resources
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by pre-computing and storing validation results for common parameter configurations in databases. When validating systems with changing parameters, the framework can retrieve pre-computed results rather than performing full computational validation, reducing real-time computational requirements while maintaining adaptability to different parameter configurations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20230280705A1Method for validating or verifying a technical system
Publication Date: 2023.09.07 ROBERT BOSCH GMBH
  • US20230280705A1 patent drawing
  • US20230280705A1 patent drawing
  • US20230280705A1 patent drawing

AI summary

A computer-implemented method for verifying and/or validating whether a technical system fulfills a desired criterion with a predefined probability. The technical system emits output signals based on input signals supplied to the technical system. The method includes: obtaining models for components of the technical system and connections between the models; obtaining test outputs for the models based on test inputs of the models and the connections between the models; determining an upper or lower bound of an output of the technical system; verifying and/or validating whether the technical system fulfills the criterion with the predefined probability based on the determined upper or lower bound of the output.