Validating Network Inventory Software via Historical Data Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Testing complex communication network equipment inventorying software is challenging due to rapid changes in network inventory and software development, making it difficult to determine if output changes are from software or inventory changes.

Innovation Solution

A method and system for validating communication network inventory software by processing data sets with different software versions to produce authoritative and trial data stores, comparing them for matching results, and designating errors in the software, with features like processing statistics and notification reports for anomalous durations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software versions are frequently updated to improve functionality, then software capabilities are enhanced, but it becomes difficult to determine whether output changes are caused by software errors or inventory changes

Engineering Contradiction:
Improvesoftware capabilitiesVSAvoiderror detection difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system performs preliminary actions by processing historical inventory data sets with both the first version and second version of the software before comparing results. This allows establishing baseline expectations of what correct output should look like, enabling subsequent detection of actual software errors versus legitimate inventory changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary validation process that compares trial data store results against authoritative data store results. This intermediary comparison mechanism acts as a mediator to distinguish whether differences in output are due to software errors or legitimate inventory changes, solving the detection difficulty.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive validation testing is performed to improve software reliability, then error detection capability is enhanced, but processing time and computational resources increase

Engineering Contradiction:
Improvesoftware validation reliabilityVSAvoidvalidation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial action by selecting specific historical data sets for validation testing rather than testing all possible scenarios. This provides sufficient validation to detect software errors while avoiding the excessive processing time that would result from comprehensive testing of every possible inventory state.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary validation by processing historical data that represents past inventory states. This preliminary action establishes expected results in advance, allowing quick comparison against current software output and enabling fast detection of deviations without requiring time-consuming comprehensive testing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9928055B1Validating development software by comparing results from processing historic data sets
Publication Date: 2018.03.27 T MOBILE INNOVATIONS LLC
  • US9928055B1 patent drawing
  • US9928055B1 patent drawing
  • US9928055B1 patent drawing

AI summary

A system for validating wireless communication network inventory software. The system comprises a processor, a non-transitory memory, and an application stored in the memory. When executed by the processor, the application processes a first data set with the first version of the software system to produce an authoritative data store, processes the first data set with a second version of the software system to produce a first trial data store, and processes a second data set with the second version of the software system to produce a second trial data store, wherein the second data set comprises later data than the first data set, and responsive to determining that the first trial data store matches the authoritative data store and determining that the second trial data store does not match the authoritative data store, designates the second data set changed.