AUTOSAR Component Test Service for Runtime Environment Manipulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of control unit programs in vehicles requires more flexible and efficient testing methods to simulate and react to errors in communication processes between program components, especially in networked systems, where early identification of errors is crucial but existing solutions complicate the testing process with unnecessary complexity and require frequent configuration adjustments.

Innovation Solution

A development device and method that provides a component test service with an intervention interface according to the AUTOSAR standard, allowing manipulation of the runtime environment's size through a test scenario program component, enabling flexible testing of program components' reactions to errors without reconfiguring the simulation or control unit program, and allowing reuse of test scenario components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing testing solutions are used to simulate errors in communication processes, then error detection capability is improved, but device complexity increases due to unnecessary configuration adjustments and simulation reconfigurations

Engineering Contradiction:
Improveerror detection capabilityVSAvoidtesting process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the testing functionality from the complex simulation environment by introducing a standalone test scenario program component. This component can be integrated into the runtime environment without requiring reconfiguration of the entire simulation system, thereby simplifying the testing process while maintaining error detection capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The test scenario program component is designed as a universal element that can be reused across different testing scenarios and integrated into various runtime environments. This multi-functional component eliminates the need for separate configuration adjustments for each test case, reducing overall device complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If simulation reconfiguration is performed frequently to test different error scenarios, then testing flexibility is improved, but loss of time increases due to repeated configuration adjustments

Engineering Contradiction:
Improvetesting flexibilityVSAvoidconfiguration adjustment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The test scenario program component is prepared in advance with predefined error scenarios and testing logic. This preliminary preparation allows the component to be directly integrated into the runtime environment for immediate testing without requiring time-consuming reconfiguration adjustments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The testing system dynamically integrates the test scenario program component into the runtime environment as needed, rather than requiring static reconfiguration. This dynamic approach allows flexible switching between different test scenarios without time loss.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If test scenario components are customized for each specific test case, then measurement precision is improved, but device complexity increases due to lack of component reuse

Engineering Contradiction:
Improvetest scenario specificityVSAvoidcomponent management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The test scenario program component is designed as a universal template that can be configured for different test cases while maintaining its core structure. This allows the same component to serve multiple specific testing purposes, achieving measurement precision without increasing device complexity through customization of the entire component.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP2685382B1Method and device for producing and testing a control device program
Publication Date: 2019.10.16 DSPACE DIGITAL SIGNAL PROCESSING & CONTROL ENGINEERING GMBH
  • EP2685382B1 patent drawingFigure 1
  • EP2685382B1 patent drawingFigure 2

AI summary

The method involves creating an executable program of a control unit program component and a test scenario program component. A runtime environment is created. A component test service that offers an interface to the runtime environment pursuant to the automatic open system architecture (AUTOSAR) standard is provided as an intervention point for manipulating the quantity of the runtime environment. The access to the quantity of the runtime environment is permitted by test scenario program components through suitable code generation for the runtime environment. An independent claim is included for a development device for providing intervention point for manipulating quantity of runtime environment for testing control unit program component in test environment.