Driver Dependency Tracking via Information Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software update services and application stores lack a mechanism to effectively identify and manage complex software dependencies, leading to issues with legacy application deployment packages not conforming to modern frameworks, such as Windows 10S, and failing to track dependencies for driver packages.

Innovation Solution

A method for dynamically deploying driver dependencies involves determining components in an application package, generating driver packages, updating information files to include dependencies, and storing these packages in a repository, allowing for the identification and installation of missing dependencies in an information handling system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If driver packages are deployed without dependency tracking mechanisms, then deployment process is simple, but deployment reliability fails due to missing dependencies

Engineering Contradiction:
Improvedeployment reliabilityVSAvoiddeployment process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by generating an information file that declares dependencies before the driver package is actually installed. This allows the dependency to be identified and installed in advance, ensuring deployment reliability without adding complex real-time tracking mechanisms during the installation process itself.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The information file acts as an intermediary between the driver package and the dependency management system. It carries dependency information from the driver package to the software update service, enabling reliable dependency tracking without requiring direct complex interactions between all system components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If legacy application deployment packages are used, then ease of operation is maintained, but adaptability to modern frameworks deteriorates

Engineering Contradiction:
Improveframework compatibilityVSAvoiddeployment operation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The information file format serves multiple functions: it works with legacy application deployment packages while also being compatible with modern frameworks like Windows 10S. This universal approach allows the same mechanism to handle both old and new deployment scenarios, improving framework compatibility without sacrificing the simplicity that made legacy packages easy to operate.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If driver packages include detailed dependency information, then dependency tracking precision improves, but package size increases

Engineering Contradiction:
Improvedependency tracking precisionVSAvoidpackage information volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The dependency information is extracted from the driver package and placed in a separate information file. This extraction allows for precise dependency tracking while keeping the actual driver package size minimal, as only the essential driver code remains in the package while the detailed dependency declarations are in the separate information file.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11093256B2System and method for dynamically installing driver dependencies
Publication Date: 2021.08.17 DELL PROD LP
  • US11093256B2 patent drawing
  • US11093256B2 patent drawing
  • US11093256B2 patent drawing

AI summary

A method for deploying dependencies includes determining a first component included in an application package and generating a first driver package for the first component that includes an information file. The method also includes updating the information file to include a dependency of the first component and storing the first driver package to a repository. The first driver package includes first binaries to install the first component. The method further includes downloading the first driver package to an information handling system and determining the dependency of the first component by parsing the information file. If the second component is the dependency, the method determines whether the second component is installed in the information handling system. If the second component is not installed, the method adds the second component to a device manager to trigger a download and installation of a second driver package for the second component.