XML-Based Driver Deployment on Write-Filtered Client Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for deploying and updating software applications and drivers on client devices are inefficient, particularly when dealing with multiple hardware platforms, as they require creating and transferring large disk images, which is time-consuming and impractical, and often result in driver conflicts and storage issues.
Innovation Solution
The use of an XML configuration file to automate the deployment and updating of applications and drivers on client devices, utilizing an update agent module that disables the write-filter to ensure persistent changes and efficiently installs only required drivers, reducing storage space and minimizing conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If disk images are created and transferred for deploying applications and drivers, then deployment can be automated, but the image files become very large and transfer time increases significantly
Solution Approach 1:
The patent segments the deployment process by separating application/software deployment from driver deployment. Applications are deployed using traditional imaging methods while drivers are deployed individually through XML configuration files. This segmentation allows the large image transfer to be avoided for driver updates, reducing overall transfer time while maintaining automation.
Solution Approach 2:
The patent implements preliminary action by having the update agent check for driver updates and retrieve XML configuration files before the actual driver installation occurs. This allows the system to prepare deployment parameters and select appropriate drivers in advance, reducing the time required during the actual deployment process.
2Reliability
If disk images are created for each hardware platform, then drivers can be properly installed, but the number of images to create and manage increases significantly
Solution Approach 1:
The patent applies local quality by making the driver selection process adaptive to each specific hardware platform. The XML configuration files contain platform-specific driver information, and the update agent automatically selects the appropriate drivers based on the local hardware characteristics. This eliminates the need to create separate images for each platform while ensuring driver compatibility.
Solution Approach 2:
The patent uses parameter changes by varying the driver selection parameters based on hardware platform detection. The system changes which drivers are installed by reading hardware-specific parameters from the XML configuration files, rather than requiring separate images for each platform configuration.
3Quantity of substance
If individual driver installation is performed on each device, then storage space is reduced, but the deployment process becomes prohibitively time-consuming
Solution Approach 1:
The patent implements self-service by enabling the client device's update agent to autonomously check for driver updates, retrieve XML configuration files, select appropriate drivers, and perform installations without manual intervention. This automation maintains high deployment speed while using individual driver installation to minimize storage requirements.
4Stability of the object's composition
If write-filter is enabled on client devices, then system stability is maintained, but application and driver changes do not persist across reboots
Solution Approach 1:
The patent applies preliminary action by disabling the write-filter before deploying applications and drivers, allowing the changes to be made persistently. After the deployment is complete, the write-filter is re-enabled to restore system stability. This temporal separation ensures both deployment persistence and system stability are achieved.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
The deployment and updating of applications and drivers on a client device having a write-filter is described. A first deployment extensible markup language (XML) configuration file is obtained for deploying a first application or driver at the client device. A first application or driver is deployed on the client device based on the first deployment XML configuration file, while the write-filter of the client device is disabled. The write-filter is enablable to prohibit a file stored on the client device with the write-filter enabled from persisting across a reboot of the device. Following the deployment, automatic updating is performed by determining whether an autoupdate is available, obtaining a second deployment XML configuration file for updating the first application or driver, and updating the first application or driver based on the second deployment XML configuration file, while the write-filter is disabled. The automatic updating may be repeated.