Proactive Caching of Remote Maintenance Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise computing systems, the maintenance window is often dominated by the download phase of maintenance files, leaving insufficient time for installation and execution, which is inefficient and can disrupt primary production times.
Innovation Solution
A method where client devices download maintenance files during an initial phase and store them locally without installation, then install and execute them during a subsequent maintenance window upon receiving an instruction from the enterprise server, optimizing the maintenance window by separating the download and installation phases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the maintenance file is downloaded during the maintenance window, then the maintenance task can be completed, but the download phase consumes a large portion of the maintenance window time, leaving insufficient time for installation and execution
Solution Approach 1:
The patent applies preliminary action by downloading and caching the maintenance file before the actual maintenance window begins. The client device proactively retrieves the maintenance file during idle periods or in advance, stores it in local cache, and then quickly installs it when the maintenance window opens. This separates the time-consuming download phase from the maintenance window, allowing the installation phase to complete within the allocated time frame.
2Productivity
If the maintenance window is scheduled during off-peak time to avoid occupying the client device during production, then production times are protected, but the download phase still takes over half the maintenance window time, shortening the installation and execution period
Solution Approach 1:
The patent performs the download action in advance during off-peak periods or before the maintenance window, caching the file locally. This way, when the maintenance window is scheduled during off-peak production times, only the quick installation and execution phases need to occur, not the lengthy download phase. This preserves both production efficiency and adequate installation time.
Solution Approach 2:
The patent segments the maintenance process into distinct phases: a proactive download/caching phase and a subsequent installation/execution phase within the maintenance window. This segmentation allows the time-consuming download operation to be separated from the maintenance window allocation, enabling better time management and ensuring sufficient time for installation and execution during the scheduled maintenance period.
3Quantity of substance
If the maintenance file is large, then more comprehensive maintenance can be provided, but the download phase takes even longer, dominating the maintenance window and leaving minimal time for installation and execution
Solution Approach 1:
The patent addresses large maintenance files by performing the download and caching operation in advance, before the maintenance window begins. This allows comprehensive maintenance files to be retrieved during periods when the client device is not under time pressure, storing them in local cache. When the maintenance window opens, only the installation and execution of the already-downloaded file need to occur, eliminating the bottleneck of downloading large files during the constrained maintenance window.
Data Source
AI summary
A method and system for managing maintenance events in an enterprise computing environment. A client receives a maintenance file associated with a maintenance event from a server. The client device stores the maintenance file in local storage (e.g., cache), without installing the maintenance file. Subsequently, the client device receives an instruction from the server to install the previously downloaded and stored maintenance file.