Compliance Testing Automation via Data Containers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing compliance testing techniques require significant manual effort and are not easily adaptable to different device configurations, as they are often tied to specific device manufacturers and configuration data formats, necessitating separate tests and code modifications for each device type and format change.
Innovation Solution
A method for performing compliance testing that involves receiving and storing configuration state information in a data container, using queries and compliance rules to determine device compliance, and automatically generating remedial actions, with metadata facilitating format independence and ease of modification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If compliance tests are coded in source code for a particular device or configuration data format, then the compliance test can be executed on that specific device, but additional compliance tests must be written for each different device manufacturer and type
Solution Approach 1:
The patent creates a universal compliance testing system that can test multiple device types and manufacturers using a single framework. The system uses configuration data containers and parameter-based compliance rules that can be adapted to different devices without rewriting the entire compliance test, allowing one system to serve multiple functions across diverse device landscapes
Solution Approach 2:
The patent segments the compliance testing system into distinct components: configuration data containers that hold device-specific parameters, compliance rules that define requirements, and a testing engine that executes tests. This segmentation allows individual components to be modified or added without affecting the entire system, reducing the complexity of managing compliance tests for multiple device types
2Reliability
If compliance test source code is modified to accommodate changes in configuration data format, then the test remains accurate for the new format, but significant manual effort and code modification are required
Solution Approach 1:
The patent uses parameter-based compliance rules that reference configuration data by name rather than hardcoding format-specific syntax. When configuration data formats change, only the parameter values in the configuration data container need to be updated, not the compliance test logic itself. This allows the system to adapt to format changes while maintaining test accuracy with minimal modification effort
Solution Approach 2:
The patent introduces a configuration data container as an intermediary layer between the device-specific configuration data and the compliance testing engine. This container standardizes the data structure and provides a uniform interface for compliance rules, isolating the testing logic from format-specific variations and reducing the manual effort required to accommodate format changes
3Measurement precision
If separate compliance tests are written for each device manufacturer and type, then each test can be tailored to that specific device, but the overall testing process requires significant manual effort
Solution Approach 1:
The patent creates a universal compliance testing system that can test multiple device types and manufacturers using a single framework. The system uses configuration data containers and parameter-based compliance rules that can be adapted to different devices without rewriting the entire compliance test, allowing one system to serve multiple functions across diverse device landscapes
Solution Approach 2:
The patent enables the compliance testing system to automatically adapt to different device types by loading appropriate configuration data containers and applying relevant compliance rules. The system self-configures based on the target device rather than requiring manual programming for each device type, significantly reducing the time and effort required to write and maintain compliance tests
Data Source
AI summary
Described are techniques for performing compliance testing. Configuration state information is received for one or more devices managed using a configuration management system. The configuration state information is stored in a data container. One or more compliance tests are executed using the configuration state information to determine if the one or more devices are compliant. The one or more compliance tests are defined using one or more queries and one or more compliance rules. The one or more queries are used for retrieving a portion of said configuration state information from said data container and generating one or more result sets. The one or more compliance rules specifying compliance criteria are used for determining whether the one or more result sets include configuration state information which is compliant.