Application Instance Manager for Power-Efficient Component Lifecycle
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional operating systems face challenges with power consumption and privacy concerns, especially in augmented reality (AR)/virtual reality (VR) devices, due to defined application lifecycles and lack of control over application components.
Innovation Solution
An application framework is introduced that decomposes applications into component parts, allowing for individual lifecycle management of instances, presenters, workers, and data providers. This framework includes an application instance manager and a presentation manager to control and optimize the components, reducing power consumption and enhancing privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If applications are decomposed into component parts with individual lifecycle management, then power consumption is reduced and privacy is improved, but device complexity increases
Solution Approach 1:
The application framework is segmented into distinct components (application instance manager, presentation manager, data providers, workers, presenters) that can be independently managed. Each component has its own lifecycle events (create, activate, suspend, destroy) allowing the system to selectively activate only the components needed for current tasks, reducing overall power consumption while maintaining manageable complexity through clear separation of concerns.
2Object-affected harmful factors
If applications are decomposed into component parts with individual lifecycle management, then privacy is improved by controlling data providers, but device complexity increases
Solution Approach 1:
Data access functionality is segmented into separate data provider components that can be independently controlled and monitored. Each data provider handles specific data types or sources, allowing the system to grant or revoke access permissions at the component level rather than application level, improving privacy control while organizing complexity into manageable, specialized units.
Solution Approach 2:
The application instance manager and presentation manager act as intermediary layers between applications and data providers. These managers control and mediate access to data providers, implementing privacy policies and authorization checks before data access is granted. This intermediary layer enhances privacy protection while centralizing the complexity of access control mechanisms.
3Ease of operation
If traditional application lifecycles are used where processes start and exit as units, then ease of operation is maintained, but power consumption increases
Solution Approach 1:
The monolithic application process is segmented into multiple independent components (presenters, workers, data providers) that can be individually activated and suspended. When an application is in the background or not actively used, only essential components remain active while others are suspended or destroyed, significantly reducing power consumption. The application instance manager coordinates these component lifecycles to maintain ease of operation through unified management interfaces.
Solution Approach 2:
The application framework implements dynamic lifecycle management where components transition between different states (created, activated, suspended, destroyed) based on current system conditions and user needs. This dynamic approach allows the system to adapt power consumption levels in real-time by activating or suspending components as applications move between foreground and background states, rather than maintaining fixed process lifecycles.
Data Source
AI summary
In one embodiment, an operating system of a computing system determines, by an application instance manager of the operating system, that a first instance corresponding to a first application is to be activated according to an instance database managed by the operating system, where the first application includes several application components, including the first instance and a presenter. The application instance manager invokes the first instance and the presenter, the presenter being managed by the first instance. The operating system determines that the presenter is configured to present data obtained by a data provider, the data provider being one of several application components of a second application. The data provider accesses data from a data store and populates a dataset defined by the second application. The presenter of the first application generates a user interface to present the data from the dataset defined by the second application.