Driver Installation Control Using Hardware-Software State Maps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing driver update processes in information technology assets fail to consider the complex interactions between hardware and software components, leading to frequent installation failures and high support costs, as they rely on limited testing and reactive remediation.

Innovation Solution

A system that generates a state map of hardware and software components on IT assets, using Bayesian machine learning to predict driver installation failures proactively, thereby controlling the installation process based on conditional probabilities to prevent failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If driver updates are deployed without considering hardware and software component interactions, then deployment speed is improved, but installation failure rate increases

Engineering Contradiction:
Improvedriver update deployment speedVSAvoiddriver installation success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary analysis of hardware and software component interactions before driver installation. It generates state maps characterizing component presence and determines conditional probabilities of installation failure in advance, allowing proactive prevention of failures before they occur during actual driver deployment

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system cushions against potential installation failures by identifying risk factors (specific hardware/software component combinations) and controlling or preventing driver installation on affected systems before the failure can occur, thereby protecting the deployment process from failures

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If comprehensive hardware and software component analysis is performed, then installation reliability is improved, but system complexity increases

Engineering Contradiction:
Improvedriver installation success rateVSAvoidstate map generation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the complex analysis task into distinct components: generating state maps for each IT asset, identifying hardware and software components separately, determining conditional probabilities for each component, and combining these analyses to control driver installation decisions

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces state maps as intermediary data structures that characterize hardware and software component presence. These state maps serve as intermediaries between raw monitoring data and the final driver installation decisions, simplifying the overall analysis process

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12541352B2Controlling installation of drivers based on hardware and software components present on information technology assets
Publication Date: 2026.02.03 DELL PROD LP
  • US12541352B2 patent drawing
  • US12541352B2 patent drawing
  • US12541352B2 patent drawing

AI summary

An apparatus comprises a processing device configured to obtain monitoring data characterizing presence of hardware and software components on information technology assets, to generate a state map characterizing which of the hardware and software components were present on each information technology asset when installation of a given driver was attempted and whether the installation of the given driver was successful. The processing device is also configured to determine, based on the state map, conditional probabilities of installation failure for the given driver associated with presence of respective ones of the hardware and software components, to identify hardware and software components present on an additional information technology asset, and to control whether the given driver is installed on the additional information technology asset based on the conditional probabilities of installation failure for the given driver associated with the identified hardware and software components present on the additional information technology asset.