Device Driver Verification via Centralized Health Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of managing and verifying device drivers across numerous computing devices, due to their variety and number, makes it difficult to ensure proper operation and troubleshoot issues, leading to potential system failures and user dissatisfaction.

Innovation Solution

A system and method for collecting and analyzing device driver data using a driver verifier function that captures information based on predefined rules, categorizes it, and provides insights into driver health, allowing for early detection and correction of errors before they impact users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If device drivers are manually tracked and verified across numerous computing devices, then operational accuracy can be maintained, but the complexity and time required for tracking and verification increases significantly

Engineering Contradiction:
Improvedriver operation verificationVSAvoidtracking and verification system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically collecting driver data from computing devices using a driver verifier function, categorizing the data based on attributes, and analyzing driver health without requiring manual intervention. The centralized server autonomously manages the verification process across multiple devices, eliminating the need for manual tracking while maintaining verification accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A centralized server acts as an intermediary between computing devices and the verification system. The server receives driver data from multiple devices, processes and categorizes the information, and provides centralized analysis. This intermediary approach simplifies the complexity by consolidating verification operations in a single location rather than requiring distributed manual verification across all devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If comprehensive driver data is collected from all computing devices, then driver health analysis accuracy improves, but the amount of data to be processed and analyzed increases

Engineering Contradiction:
Improvedriver health analysisVSAvoiddriver data volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts only the essential and relevant attributes from the collected driver data for categorization and analysis. Rather than processing all raw data in detail, the driver verifier function identifies and extracts key attributes that indicate driver health status. This extraction approach maintains analysis precision while reducing the volume of data that requires intensive processing.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by categorizing driver data based on specific attributes that are relevant to particular driver types or devices. Different data attributes are analyzed with different levels of detail appropriate to their significance. This targeted approach ensures precise analysis of critical parameters while minimizing processing of less important data, thereby maintaining measurement precision without proportionally increasing processing burden.

Inventive Principle:
Principle #3Local quality

3Reliability

If driver verification is performed in real-time across multiple devices, then system reliability improves, but the processing time and computational resources required increase

Engineering Contradiction:
Improvedriver operation monitoringVSAvoiddata processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by continuously collecting and pre-processing driver data in the background using the driver verifier function. Data is categorized and prepared for analysis before explicit verification is needed. This preliminary processing reduces the time required for actual verification operations, as the data is already organized and ready for rapid analysis when verification is triggered.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuity of useful action by implementing continuous, automated data collection and monitoring across all computing devices. The driver verifier function operates continuously in the background, constantly gathering driver data and maintaining an updated view of driver health across the network. This continuous operation eliminates gaps in monitoring while distributing processing over time, reducing peak computational demands and overall processing time.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS10467082B2Device driver verification
Publication Date: 2019.11.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10467082B2 patent drawing
  • US10467082B2 patent drawing
  • US10467082B2 patent drawing

AI summary

Systems and methods are described for verifying functionality of a computing device. A set of rules are sent to a computing device identifying a device driver. Data is received from the one device that is indicative of collected driver data of the computing device. The data is collected by a driver verifier function executing on the computing device. The driver verifier function is configured to capture information associated with the identified device driver identified by the set of rules. The received data is parsed to categorize the data with previously collected driver data of other computing devices. The data is categorized based on attributes of the collected driver data. The categorized data is provided for analysis of the driver health on the computing device.