Distributed Test Architecture Modular Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Test and Measurement systems are monolithic, limiting the ability to support multiple, simultaneously different measurement and stimulus capabilities, requiring costly and time-consuming reconfiguration for changing test requirements and being tightly integrated with specific hardware and software, restricting flexibility and increasing the risk of false failures.

Innovation Solution

A distributed architecture system with a hardware-agnostic Test Operating System, virtual instrumentation layer, and separate Test Executable Layer, allowing for modular communication between applications and devices, enabling support for various stimulus and measurement capabilities without reconfiguration, and running on diverse hardware and software platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If a monolithic system architecture is used, then system stability and simplicity are improved, but the ability to support multiple different measurement and stimulus capabilities simultaneously deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidcapability support
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system is divided into separate functional modules including a control module, stimulus module, measurement module, and data processing module. Each module can be independently configured and operated, allowing multiple different measurement and stimulus capabilities to run simultaneously without requiring complete system reconfiguration. The control module manages multiple stimulus modules and measurement modules as separate entities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The control module is designed with universal functionality to manage multiple types of stimulus modules and measurement modules simultaneously. The system provides a unified interface that can control different capabilities (fiber optic, copper, wireless, etc.) through a single control unit, eliminating the need for multiple specialized systems.

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

2Adaptability or versatility

If the system is reconfigured to support different capabilities, then adaptability is improved, but test time and opportunity for false failures increase

Engineering Contradiction:
Improvecapability supportVSAvoidtest time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

By segmenting the system into independent modules, each capability can be maintained as a separate operational unit. The control module can switch between or run multiple modules simultaneously without requiring complete system shutdown and reconfiguration, significantly reducing test time and eliminating the need to reconfigure the entire system for each test type.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system enables continuous testing operations by allowing multiple stimulus and measurement modules to operate simultaneously or be quickly switched between. The control module maintains continuous operation without requiring system shutdown, ensuring that testing can proceed without interruption and reducing overall test time.

Inventive Principle:
Principle #20Continuity of useful action

3Device complexity

If monolithic software architecture is used, then system simplicity is improved, but the ability to run on different hardware bases deteriorates

Engineering Contradiction:
Improvesystem simplicityVSAvoidhardware compatibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The software architecture is segmented into a control software layer and hardware driver layers. The control software remains architecture-neutral and can run on different operating systems and hardware platforms, while hardware-specific functionality is isolated in separate driver modules that can be loaded or unloaded as needed, maintaining simplicity while enabling hardware versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The control module acts as an intermediary layer between the user interface and hardware-specific drivers. This mediator layer provides a unified control interface that is independent of underlying hardware or operating system differences, allowing the same control software to operate across multiple hardware bases through standardized communication protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2912564B1Distributed test system architecture
Publication Date: 2021.02.24 AFL COMM LLC
  • EP2912564B1 patent drawingFigure 1
  • EP2912564B1 patent drawingFigure 2
  • EP2912564B1 patent drawingFigure 3

AI summary

The present invention is related to a method of connecting a first device comprising a processor and an application and a second device comprising a processor and an application, a distributed architecture system for facilitating modular communication between a plurality of applications, a plurality of devices, and a plurality of applications and devices, and a computer readable medium storing a program for causing a processor to connect a plurality of applications, a plurality of devices, and a plurality of applications and devices.