Mobile Notification Checking with Boot-Memory Power Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing power saving techniques in mobile communication devices are inadequate, leading to significant power consumption when checking for notifications.
Innovation Solution
A low power management process is implemented using boot memory of a processor, allowing user interface elements to be provided while deactivating operational layers such as the operating system and application layers, with notifications managed through a low power management process that utilizes boot memory and minimal processor activation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If traditional power saving modes are used, then some power consumption is reduced, but notification checking still consumes significant power
Solution Approach 1:
The system segments the operational layers into activated and deactivated states. The low power management process runs in a segmented state where only essential components are active while other operational layers remain deactivated, enabling notification checking with minimal power consumption.
Solution Approach 2:
Instead of fully activating all operational layers for notification checking, the system uses partial action by launching a low power management process that performs notification checking functionality without requiring complete system activation, thus reducing power consumption while maintaining essential functionality.
2Use of energy by moving object
If operational layers are deactivated to save power, then power consumption is reduced, but user interface functionality is limited
Solution Approach 1:
The low power management process acts as an intermediary between the deactivated operational layers and the user interface. It manages notifications and provides user interface elements without requiring full activation of operational layers, thus maintaining ease of operation while reducing power consumption.
Solution Approach 2:
The system prepares user interface elements and notification handling in advance through the low power management process before full system activation is needed. This preliminary action ensures that when users interact with notifications, the interface is already prepared, maintaining ease of operation without requiring complete system activation.
3Productivity
If full processor activation is used for notification checking, then notification handling is comprehensive, but power consumption increases
Solution Approach 1:
The system extracts the essential notification checking functionality from the full processor activation requirement. The low power management process isolates and executes only the necessary notification handling tasks without requiring comprehensive processor activation, thus reducing power consumption while maintaining essential notification handling capability.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The specification describes an apparatus for checking for one or more notifications, detecting at least one first user interaction and launching a low power management process in response to the detecting at least one notification and the at least one first user interaction. The low power management process uses at least part of a boot memory of a processor, and wherein the low power management process runs while at least one operational layer of the apparatus is deactivated. Further, the apparatus enables provisioning of one or more first user interface elements corresponding to the at least one detected notification.