Automated Test Bench Provisioning for Cross-Domain ECU Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The provisioning and utilization of test benches for software testing in vehicle-related systems are inefficient, time-consuming, and burdensome, particularly for cross-domain tests, due to geographical restrictions, limited hardware resources, and manual configuration, leading to delays and increased costs.

Innovation Solution

A system and method for managing test benches that automatically obtain and generate test configurations based on user inputs, deploy software and hardware components, and create virtual vehicle models, enabling on-demand access and real-time reconfiguration of test benches across distributed resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration and provisioning of test benches is used, then flexibility in configuring specific hardware components is maintained, but time consumption and operational burden increase significantly

Engineering Contradiction:
ImproveManual configuration easeVSAvoidTime consumption
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service through automated test bench provisioning where the platform automatically configures hardware and software resources based on test requirements without manual intervention. The automated system provisions test benches by selecting available hardware components, configuring software environments, and establishing connections based on stored test case specifications.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual mechanical configuration operations are replaced with automated computational processes. The system uses software-based automation to provision hardware resources, configure test environments, and manage connections instead of manual physical setup, thereby reducing time consumption while maintaining configuration flexibility.

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

2Reliability

If physical testing facilities with fixed hardware resources are used, then hardware availability is ensured, but geographical restrictions and access complexity increase

Engineering Contradiction:
ImproveHardware availabilityVSAvoidAccess complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates virtual copies of physical hardware resources through software emulation and virtualization. Instead of requiring physical access to specific testing facilities, users can access virtualized hardware resources remotely through the platform, eliminating geographical restrictions while maintaining hardware availability through virtual instances of required components.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system transitions from physical, geographical constraints to a virtual, network-based dimension. Hardware resources are accessed through a centralized platform that provides remote access via network connections, transforming the access model from physical presence requirements to digital connectivity, thereby reducing access complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Productivity

If limited hardware resources are deployed in testing facilities, then facility resource utilization is maximized, but adaptability to different vehicle variants and test requirements decreases

Engineering Contradiction:
ImproveResource utilizationVSAvoidTest configuration adaptability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic resource allocation where hardware and software resources are dynamically assigned based on real-time test requirements. Instead of fixed facility configurations, the platform can dynamically provision different hardware combinations, software environments, and test configurations to match various vehicle variants and test cases, maintaining high resource utilization while enhancing adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The platform provides universal access to diverse hardware and software resources through a unified virtualized environment. A single platform can support multiple vehicle variants, test types, and hardware configurations simultaneously, allowing one system to serve multiple functions and adapt to different test requirements without requiring separate dedicated facilities for each variant.

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

4Ease of operation

If manual management of test benches is used, then detailed control over test configurations is maintained, but operational burden and coordination complexity increase

Engineering Contradiction:
ImproveConfiguration controlVSAvoidManagement complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements automated feedback loops that monitor test bench status, resource availability, and test progress. This feedback enables the automated provisioning system to adjust configurations in real-time, manage resource allocations dynamically, and coordinate multiple test components automatically, reducing management complexity while maintaining detailed control through automated decision-making based on feedback information.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250208982A1System and method for managing a test bench for a cross-domain test
Publication Date: 2025.06.26 WOVEN BY TOYOTA INC
  • US20250208982A1 patent drawing
  • US20250208982A1 patent drawing
  • US20250208982A1 patent drawing

AI summary

Provided are a system, method, and device for facilitating provisioning and/or utilization of a test bench for a cross-domain test for testing software of an embedded system. According to embodiments, the method may be implemented by at least one processor and may include: obtaining a test bench configuration associated with the software; obtaining information of a plurality of test artifacts associated with the test bench configuration; and generating, based on the plurality of test artifacts, a test bench associated with the cross-domain test, wherein the software of the embedded system comprises an in-vehicle electronic control unit (ECU).