Test Unit Nesting Shorter Cases in Idle Periods

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current testing methods for communications devices under new standards like 5G result in lengthy idle times, leading to inefficient use of testing resources due to the need to wait during idle periods, especially when testing machine type communications devices.

Innovation Solution

A test unit and method that utilize a test case database to nest shorter test cases within the idle time of longer test cases, allowing simultaneous testing of multiple devices and optimizing resource use through a signaling unit and signal splitter, ensuring accurate measurements by processing only relevant signals.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a single device is tested sequentially with long idle periods, then measurement accuracy is maintained, but testing efficiency and resource utilization deteriorate

Engineering Contradiction:
Improvemeasurement accuracyVSAvoidtesting efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements nesting by running shorter test cases within the idle time periods of longer test cases. The test case execution manager monitors idle periods and dynamically initiates nested test cases, allowing multiple test cases to be executed concurrently on the same device without interfering with the primary test sequence, thereby maintaining measurement accuracy while improving testing efficiency

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent eliminates idle waiting time by continuously utilizing device idle periods for executing additional test cases. The test case execution manager ensures that whenever a device enters an idle state during a long test case, shorter test cases are immediately scheduled and executed, transforming previously wasted idle time into productive testing opportunities

Inventive Principle:
Principle #20Continuity of useful action

2Measurement precision

If the testing equipment waits during idle periods, then single-device testing accuracy is maintained, but equipment time utilization deteriorates

Engineering Contradiction:
Improvetesting accuracyVSAvoidequipment idle time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system eliminates equipment idle time by continuously scheduling and executing test cases during device idle periods. The test case execution manager monitors device states and ensures that testing activities continue uninterrupted by utilizing idle time for nested test cases, thereby converting equipment wait time into productive testing time

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system automatically utilizes device idle periods for executing additional test cases without requiring external intervention. The test case execution manager autonomously detects idle states and schedules appropriate test cases, allowing the testing system to serve itself by transforming idle time into productive testing opportunities

Inventive Principle:
Principle #25Self-service

3Productivity

If multiple test cases are nested during idle time, then resource efficiency improves, but test case management complexity increases

Engineering Contradiction:
Improveresource efficiencyVSAvoidtest case management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The test case execution manager implements feedback mechanisms by continuously monitoring device states and idle period durations. Based on this feedback, the manager dynamically selects and schedules appropriate nested test cases, adjusting the testing strategy in real-time to optimize resource efficiency while managing complexity through adaptive decision-making

Inventive Principle:
Principle #23Feedback

4Reliability

If long idle times are tested for standard conformance, then compliance accuracy is ensured, but testing duration and resource consumption increase

Engineering Contradiction:
Improvestandard conformanceVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The patent applies nesting by executing shorter test cases within the idle periods of long test cases that verify standard conformance. This allows the system to maintain comprehensive compliance checking while reducing overall testing duration by utilizing previously idle time for additional validation tests

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The system maintains continuous testing activity by executing nested test cases during idle periods of long conformance tests. This ensures that standard conformance is thoroughly verified while minimizing total testing time, as the nested test cases run concurrently without interfering with the primary conformance validation

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10387282B2Test unit and test method for efficient testing during long idle periods
Publication Date: 2019.08.20 ROHDE & SCHWARZ GMBH & CO KG
  • US10387282B2 patent drawing
  • US10387282B2 patent drawing
  • US10387282B2 patent drawing

AI summary

A test unit for testing a plurality of communications devices is provided. The test unit comprises a test case database, which stores a first test case (including a first test case idle time) and a second test case. The second test case is shorter than the first test case idle time. The test unit comprises a signaling unit. The test unit comprises a test case execution manager, which reads from the test case database the first and second test case and controls the signaling unit to perform measurements according to the first test case on the first device under test until a beginning of the first test case idle time, and controls the signaling unit to perform measurements according to the second test case on the second device under test during the first test case idle time.