Independent UI Lifecycle States for Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern data processing systems face inefficiencies in managing system resources, as applications can linger in the background and continue to use resources even when not in use, leading to unnecessary memory usage and resource allocation issues.
Innovation Solution
The creation of multiple user interface instances with separate lifecycle states for each display resource, allowing for independent management of system resources, such as display and memory, enabling the application to reduce resource usage by deallocating memory and restricting access when an application transitions to a background state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single lifecycle state is maintained for the entire application, then resource management is simple, but applications continue to use system resources even when not in use, leading to resource waste
Solution Approach 1:
The patent segments the application lifecycle into multiple independent states (foreground active, foreground inactive, background active, background inactive) that can be applied to different UI instances separately. This allows the system to track and manage resource usage for each UI instance independently, enabling applications to reduce or stop resource usage when specific UI instances are not in use, while maintaining simple management within each state
2Productivity
If multiple UI instances are created with separate lifecycle states, then resource management efficiency improves, but system complexity increases
Solution Approach 1:
The system creates separate UI instances (e.g., first UI instance, second UI instance) each with its own lifecycle state management. This segmentation allows independent control of resource allocation for each UI instance, improving resource management efficiency by enabling selective memory deallocation and resource restriction based on individual UI instance states rather than managing all UIs under a single application lifecycle state
Solution Approach 2:
The lifecycle states are designed to be dynamic and independently changeable for each UI instance. Each UI instance can transition between foreground active, foreground inactive, background active, and background inactive states independently, allowing the system to adapt resource allocation dynamically based on the specific state of each UI instance without requiring complex coordinated management across all instances
3Reliability
If applications linger in background state, then application state is preserved, but memory usage increases unnecessarily
Solution Approach 1:
The patent applies partial action by allowing applications to maintain their state at a reduced level when UI instances are in background inactive state. Instead of fully preserving all application state and resources, the system selectively deallocates memory and restricts resource access for specific UI instances that are not in use, while maintaining the capability to restore state when needed. This partial preservation approach reduces memory usage while maintaining sufficient application state for future restoration
Data Source
AI summary
Methods and systems are disclosed that create user interface (UI) instances for corresponding input/output resources, such as display resources, and each of these UI instances have separate lifecycle states or information maintained by the respective UI instances. System processes for the display resources (e.g. different displays or different windows for the same display devices) can control access to their respective display resource and can report changes in the lifecycle states to their respective UI interface.