Protocol Server Subset Response Validation for Storage Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current storage protocol conformance testing methods are inefficient due to the high number of validation points required, particularly in protocols like Fibre Channel Protocol (FCP), which can reach over twenty, and lack effective control over complex scenarios such as group behavior and time constraints, leading to incomplete verification of storage interface operations.

Innovation Solution

A computer-implemented method involving a protocol server that receives a source code file containing test case definition files (TCDF) with parameters, preparation steps, and test case blocks, executes these steps on a system under test (SUT), and compares responses against certificates to generate test results, thereby filtering and validating a subset of responses for improved processing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If all responses are validated against all validation points, then measurement precision is improved, but processing time increases

Engineering Contradiction:
Improvevalidation completenessVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts and validates only the necessary subset of responses based on actual test case execution paths rather than validating all possible responses. The validation system identifies which validation points are actually reached during test execution and only validates responses corresponding to those points, eliminating redundant validation operations while maintaining complete coverage of actual test scenarios.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial validation by validating only the portion of responses that are actually generated during test execution. Instead of performing excessive validation on all possible responses, the system performs validation on the exact subset needed, reducing processing time while ensuring all actual test outcomes are properly verified.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If the number of validation points is increased to cover all scenarios, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol conformance verificationVSAvoidtest system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the validation process into distinct test case blocks, each with its own set of relevant validation points. Rather than maintaining a single large set of all possible validation points, the system divides validation into modular segments corresponding to specific test cases, making the overall system more manageable and easier to configure while maintaining comprehensive coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary configuration of test cases with their specific validation point requirements before execution. This allows the system to pre-identify which validation points are needed for each test case, reducing the complexity of runtime decision-making and enabling more efficient validation without requiring a comprehensive set of all possible validation points to be actively managed.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive validation of all responses is performed, then measurement precision is improved, but productivity decreases

Engineering Contradiction:
Improveresponse verification accuracyVSAvoidtesting efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent extracts and validates only the necessary subset of responses based on actual test case execution paths rather than validating all possible responses. The validation system identifies which validation points are actually reached during test execution and only validates responses corresponding to those points, eliminating redundant validation operations while maintaining complete coverage of actual test scenarios.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent dynamically adjusts the validation parameters based on the specific test case being executed. Rather than using a fixed comprehensive validation set, the system changes the validation parameters to match the actual test scenario, validating only the relevant responses and validation points needed for that specific test case, thereby improving both accuracy and efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11275675B2Validation of a subset of a plurality of responses during protocol testing
Publication Date: 2022.03.15 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11275675B2 patent drawing
  • US11275675B2 patent drawing
  • US11275675B2 patent drawing

AI summary

A computer-implemented method according to one embodiment includes receiving, by a protocol server, a source code file. The source code file includes a TCDF. The TCDF includes parameters for a test case, preparation steps related to the test case, and a plurality of test case blocks. Each test case block of the plurality of test case blocks includes a set of testing steps and a certificate. The source code file is output by the protocol server to a SUT with an instruction for the SUT to execute the source code file in order to implement the set of testing steps for each of the plurality of test case blocks. A plurality of responses are received by the protocol server from the SUT. Each of the responses are compared against the certificates of the test case blocks. A test result is generated by the protocol server based on the comparisons.