Automated Driver Update via Deployment Configuration File
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating software applications and drivers on multiple client devices with different hardware platforms are inefficient, requiring the creation of multiple disk images and time-consuming individual installations, especially when frequent updates are needed.
Innovation Solution
An automated system using a deployment configuration file that allows an update agent module to identify and update applications or drivers on client devices by retrieving a deployment configuration file, checking for higher versions, and installing updates while the write-filter is disabled, ensuring compatibility across various hardware platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If disk images are created for each hardware platform, then software can be installed on multiple devices, but the number of images increases and transfer size becomes very large
Solution Approach 1:
The patent segments the software installation into two parts: a base image that is common to all hardware platforms, and hardware-specific drivers that are installed separately after the base image is deployed. This eliminates the need to create separate disk images for each hardware platform, reducing the quantity of images from multiple platform-specific images to a single base image.
Solution Approach 2:
The patent extracts hardware-specific drivers from the disk image and handles them separately through automatic detection and installation after the base image is applied. This extraction allows the base image to be hardware-agnostic, reducing the number of images needed while maintaining adaptability to different hardware platforms.
2Adaptability or versatility
If disk images are created for each hardware platform, then software can be installed on multiple devices, but the transfer size becomes very large
Solution Approach 1:
The patent segments the software installation into two parts: a base image that is common to all hardware platforms, and hardware-specific drivers that are installed separately after the base image is deployed. This eliminates the need to create separate disk images for each hardware platform, reducing the quantity of images from multiple platform-specific images to a single base image.
Solution Approach 2:
The patent extracts hardware-specific drivers from the disk image and handles them separately through automatic detection and installation after the base image is applied. This extraction allows the base image to be hardware-agnostic, reducing the number of images needed while maintaining adaptability to different hardware platforms.
3Reliability
If individual installation is performed on each device, then hardware platform differences are avoided, but the installation time becomes prohibitively long
Solution Approach 1:
The patent performs preliminary installation of a base image that is compatible with all hardware platforms, then automatically detects and installs hardware-specific drivers afterward. This preliminary action allows bulk deployment to multiple devices simultaneously, dramatically improving installation speed while maintaining reliability through subsequent automatic hardware detection and driver installation.
Solution Approach 2:
The system enables self-service through automatic hardware detection and driver installation after the base image is deployed. Each device automatically identifies its hardware platform and installs the appropriate drivers without manual intervention, maintaining installation reliability while enabling rapid bulk deployment across multiple devices.
4Stability of the object's composition
If write-filter is enabled to protect the image, then device stability is maintained, but updates cannot persist across reboots
Solution Approach 1:
The patent temporarily disables the write-filter as a preliminary action during the driver installation process, allowing updates to be applied and persist across reboots. After installation completes, the write-filter is re-enabled to restore device stability. This time-limited disablement resolves the contradiction by allowing persistence only when necessary for updates.
Solution Approach 2:
The patent dynamically adjusts the write-filter state based on the installation phase: enabled during normal operation to maintain stability, temporarily disabled during updates to allow persistence, then re-enabled after updates complete. This dynamic adjustment resolves the contradiction between stability and update persistence.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
The automatic updating of an application or a driver on a client device is described. At least one deployment configuration file, including a deployment entry corresponding to a package for updating an application or a driver, is obtained at the client device. The deployment configuration file is stored on the client device in a memory location that is exempt from a write-filter restriction, wherein the write- filter restriction prohibits a file stored with the write-filter enabled from persisting across a reboot of the device. A check is performed to determine whether the deployment entry identifies an application or driver that is installed on the client device, and identifies a version of the application or driver that is higher than a version installed on the client device. The application or driver corresponding to the deployment entry is then updated on the client device using the package, while the write-filter is disabled.