Application Update Manager Eliminates Dedicated Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method of updating computer applications through a dedicated update server is costly and vulnerable to security threats, as it requires continuous maintenance and can lead to rapid dissemination of fraudulent updates across numerous devices.
Innovation Solution
An update system that eliminates the need for a dedicated update server by using an update manager to store and manage application release information internally, generating metadata for new releases, and utilizing a file store with read-only access for clients, ensuring secure and efficient updates without server bottlenecks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dedicated update server is used to manage application updates, then updates can be centrally controlled and distributed, but infrastructure costs increase and security vulnerabilities arise
Solution Approach 1:
The patent extracts the update management functionality from a centralized server and embeds it directly into the application executable file. The update manager component is integrated within the application itself, allowing the application to autonomously check for updates, download patches, and apply fixes without requiring a dedicated update server infrastructure.
Solution Approach 2:
The application performs update management operations autonomously through the embedded update manager. The system self-checks for updates by comparing version information, self-downloads update packages from file stores, and self-applies updates without requiring external server coordination or manual intervention, thereby eliminating the need for complex centralized infrastructure.
2Productivity
If a centralized update server is used, then update distribution is streamlined, but security risks increase due to potential fraudulent updates
Solution Approach 1:
The system performs preliminary verification by checking digital signatures and hash values of update packages before installation. The update manager validates the authenticity of downloaded updates against the original application version and publisher credentials, preventing fraudulent updates from being installed. This preliminary security check occurs locally on the user device rather than relying solely on server-side trust.
Solution Approach 2:
The patent introduces file stores as intermediary storage locations between the update source and the application. Updates are first stored in secure file stores with controlled access, and the update manager retrieves them from these intermediaries rather than directly from external sources. This intermediary layer adds a security buffer that prevents direct injection of fraudulent updates into the application execution flow.
3Reliability
If traditional update methods are used, then updates can be managed centrally, but update speed and efficiency are reduced due to server bottlenecks
Solution Approach 1:
The patent segments the update distribution system into multiple independent file stores rather than relying on a single centralized server. Each file store can independently store and serve update packages, allowing parallel update operations across multiple devices. This segmentation eliminates the single-point bottleneck and enables concurrent update downloads and installations, significantly improving deployment speed.
Solution Approach 2:
The system creates local copies of update packages in file stores that are accessible to multiple applications and devices. Instead of repeatedly fetching updates from a central server, the update manager retrieves updates from pre-cached copies in the file store, reducing network latency and server load. This copying mechanism accelerates update deployment while maintaining version control through the embedded update manager.
Data Source
AI summary
An update system is provided. The system includes a database for storing application release information for one or more previous versions of a computer applications and a current version of the computer application. The system further includes an update manager configured to: receive an application release request, the application release request comprising a release file and application release information associated with the current version of the computer application; store at least a portion of the application release information of the current version of the computer application in the database; retrieve application release information corresponding to the one or more previous versions of the computer application and the current version of the computer application from the database; automatically generate release metadata based at least in part on the retrieved application release information; and store the release metadata and the release file in a file store for retrieval and installation by a computer application executing on a user computing device.