Application Manager Component Restart Handling via Resource Status Copying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing environments face disruptions and resource management challenges when the application manager component stops or terminates, particularly due to the need for redundant systems or complex state management across applications, which can lead to resource inefficiencies and application downtime.
Innovation Solution
A computer-implemented method where the application manager component obtains and stores information to rebuild resource status, allowing applications to continue running even if the application manager component stops or restarts, by using a repository to store information about resource usage and access requests, enabling efficient synchronization and minimizing memory usage without requiring duplicate systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundant systems are used to ensure continuous operation during application manager component failure, then system reliability is improved, but device complexity and memory requirements increase
Solution Approach 1:
Instead of maintaining a complete redundant copy of the application manager component in memory, the patent creates a simplified representation by copying only the essential resource status information to applications. This allows the system to recover functionality after restart without requiring duplicate system instances, thus improving reliability while avoiding the complexity and memory overhead of full redundancy.
Solution Approach 2:
The patent segments the application manager component's functionality by separating the core resource management logic from the status representation. Only the critical status information is copied to applications, while the full application manager component is restarted fresh. This segmentation allows recovery without requiring complete system duplication, reducing device complexity and memory requirements.
2Reliability
If redundant systems are used to ensure continuous operation during application manager component failure, then system reliability is improved, but memory requirements increase
Solution Approach 1:
The patent applies copying by creating a lightweight copy of only the necessary status information (resource usage state, access requests, priorities) and providing it to applications. This eliminates the need for memory-intensive duplicate application manager instances while ensuring applications can continue operating with accurate status information during and after the component restart.
Solution Approach 2:
Instead of maintaining expensive, long-lived redundant system instances in memory, the patent uses a temporary status representation that is created just before restart and discarded after use. This disposable approach provides sufficient reliability during the critical restart period without the ongoing memory cost of permanent redundancy.
3Reliability
If a persistent storage file is used to save global state of resource usage, then system reliability is improved, but device complexity and adaptability decrease
Solution Approach 1:
The patent copies the in-memory resource status representation directly to applications before restart, eliminating the need for persistent storage files. This approach maintains reliability by ensuring status information is preserved during restart while avoiding the complexity of file I/O operations, format management, and synchronization mechanisms required by persistent storage systems.
Solution Approach 2:
The applications themselves maintain and manage their own status information copies, eliminating the need for a centralized persistent storage system. Each application independently tracks its resource status using the provided status representation, making the system more adaptable to format changes without requiring coordinated updates to a shared storage schema.
4Reliability
If a persistent storage file is used to save global state of resource usage, then system reliability is improved, but adaptability to format changes decreases
Solution Approach 1:
The patent copies status information in a simple, application-level representation rather than using a centralized persistent storage format. This allows each application to interpret and process status information according to its own requirements, making the system highly adaptable to format changes. When the application manager component updates its internal representation, applications can continue using their existing interpretation logic without requiring coordinated format migration.
Solution Approach 2:
Applications independently manage and interpret their own status representations, making each application responsible for its own data format compatibility. This self-service approach allows individual applications to adapt to format changes independently, enhancing overall system adaptability compared to a centralized persistent storage system where all components must be updated together.
Data Source
AI summary
An application manager component executing on a device obtains a request from an application to use a resource common to a plurality of applications. Based on obtaining the request, information to be used to rebuild status of the resource should it be determined that status rebuild of the resource is to be performed is provided to the application. Further, based on a restart of the application manager component, the information to be used to rebuild the status of the resource is obtained by the application manager component. The information is used to rebuild the status of the resource.