XML Configuration for Windows Embedded Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Configuring and customizing Windows-based embedded images on client devices is inefficient due to the need for manual reinstallation of entire images, especially when frequent minor changes are required, which is impractical for large numbers of devices, as existing methods do not allow changes to persist across reboots without manual intervention.
Innovation Solution
A system that uses an XML configuration file to automatically retrieve and apply configuration changes to a Windows-based embedded image upon boot, allowing for persistent changes without reinstalling the entire image, utilizing a write-filter to manage state data and ensure changes are not permanent by default.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual installation of software or drivers and firmware update of the entire image is performed to apply changes that persist across reboot, then the changes can persist across reboot, but the process becomes time-consuming and impractical for large numbers of devices
Solution Approach 1:
The patent extracts only the necessary configuration data from the embedded image, storing it separately in a configuration file on non-volatile auxiliary storage. This allows the configuration to be applied without reinstalling the entire image, significantly reducing the time required while maintaining persistence across reboots.
Solution Approach 2:
The patent performs preliminary extraction of configuration data during image creation, storing it in a separate configuration file. This preliminary action enables rapid application of configurations later without requiring full image reinstallation, thus reducing time loss while ensuring reliability.
2Ease of manufacture
If entire customized image is downloaded and installed on client device to apply changes, then the changes can be applied, but bandwidth is excessively consumed especially when there are a large number of client devices
Solution Approach 1:
The patent segments the embedded image into two parts: the core image that remains on the device, and the configuration data that is extracted and stored separately in a configuration file. This segmentation allows configuration changes to be applied by transferring only the small configuration file rather than the entire image, dramatically reducing bandwidth consumption while maintaining ease of configuration application.
Solution Approach 2:
Instead of copying the entire customized image to each client device, the patent copies only the configuration data to a configuration file that can be efficiently transferred and applied. This copying approach reduces bandwidth consumption significantly while preserving the ability to apply configuration changes across multiple devices.
3Reliability
If write-filter is used to prevent state data loss, then changes are protected from being written over, but the device cannot permanently store configuration changes without additional mechanisms
Solution Approach 1:
The patent introduces a configuration file as an intermediary between the write-filtered embedded image and the configuration data. The configuration file is stored on non-volatile auxiliary storage that is not subject to the write-filter, allowing configuration changes to persist across reboots while the write-filter continues to protect the main embedded image from unintended modifications.
Solution Approach 2:
The patent applies different storage characteristics to different parts of the system: the embedded image remains on write-filtered storage for protection, while the configuration file is stored on non-volatile auxiliary storage that allows persistent writing. This local differentiation of storage qualities enables both data protection and configuration persistence simultaneously.
Data Source
Figure 1
Figure 2~5
Figure 3A~3B
AI summary
Examples of methods and apparatus are provided for configuring and customizing a specific-purpose local client having a windows-based embedded image using extensible markup language (XML) configuration and obviating reinstallation of an entire windows-based embedded image onto the specific-purpose local client. The apparatus may include a retrieval module of the specific-purpose local client configured to automatically locate a remote repository server containing an XML configuration file and automatically obtain the XML configuration file from the remote repository server each time the specific-purpose local client boots up. The apparatus may include an apply settings module of the specific-purpose local client configured to automatically apply a configuration change to the windows-based embedded image based on the XML configuration file each time the specific-purpose local client boots up. The configuration change persists across a reboot of the specific-purpose local client while obviating reinstallation of an entire windows-based embedded image onto the specific-purpose local client.