I/O Control Code Filter for Device Testing Efficiency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The inefficiency of testing computing devices due to the large number of potential IOCTLs and IRPs, leading to excessive resource consumption and difficulty in recreating tests for complex devices with numerous settings and configurations.

Innovation Solution

Implementing an I/O filter function to capture and record relevant IOCTLs and IRPs that cause specific actions without errors, allowing for their reuse in testing similar devices, thereby reducing the need to execute all possible combinations and saving time and resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all possible IOCTLs and IRPs are executed during device testing, then comprehensive device functionality is verified, but testing time and computing resources are excessively consumed

Engineering Contradiction:

Improvedevice functionality verificationVSAvoidtesting time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and isolates only the relevant IOCTLs and IRPs that are actually used by the device under test, separating them from the complete set of possible IOCTLs and IRPs. This is achieved by monitoring device operations and capturing the specific control codes and request packets that the device responds to, thereby eliminating unnecessary testing operations while maintaining comprehensive verification of actual device functionality

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary analysis during device operation to identify and record the relevant IOCTLs and IRPs before formal testing begins. By pre-capturing the device's actual I/O control patterns during normal operation or initial characterization, the system prepares a filtered test sequence in advance, avoiding the need to execute all possible IOCTLs and IRPs during the actual testing phase

Inventive Principle:

Principle #10Preliminary action

2Reliability

If all possible IOCTLs and IRPs are executed during device testing, then comprehensive device functionality is verified, but computing resources are excessively consumed

Engineering Contradiction:

Improvedevice functionality verificationVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by executing only the subset of IOCTLs and IRPs that are relevant to the specific device under test, rather than performing exhaustive testing of all possible control codes. This partial testing approach is sufficient to verify device functionality while significantly reducing computing resource consumption compared to complete exhaustive testing

Inventive Principle:

Principle #16Partial or excessive action

3Adaptability or versatility

If tests are customized for each device configuration, then test relevance is improved, but test recreation effort increases

Engineering Contradiction:

Improvetest relevanceVSAvoidtest recreation effort

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent creates reusable templates or models of device-specific IOCTL and IRP sequences that can be copied and applied to similar devices. By capturing the actual I/O control patterns from a reference device and storing them as standardized test templates, the system enables rapid reproduction of relevant tests for devices of the same type or class without manually recreating test sequences for each individual device

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent develops universal testing approaches that can handle multiple device configurations and types through a single framework. The system captures device-specific characteristics and adapts a universal test template to work across different configurations, allowing the same basic testing methodology to be applied universally while maintaining relevance to each specific device through automated adaptation

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10922249B2Input/output control code filter

Publication Date: 2021.02.16 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Systems and methods are described for verifying functionality of a computing device. A plurality of I/O control codes usable to configure specified actions for a device under test is received. The I/O control codes that were completed without generating an error are determined. The I/O control codes that completed without generating an error and associated binding information are recorded. The I/O control codes that completed without generating an error and associated binding information are stored in a format usable for subsequent replay of the stored I/O control codes.