Push Notification Delivery Inactive Device Battery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Battery-powered computing devices face rapid battery life consumption when receiving push notifications, as they often transition from an inactive to an active state to deliver notifications, leading to unnecessary power usage.
Innovation Solution
A notification handler process selectively activates the device based on whether push notifications require user interaction, maintaining a 'red-list' of apps that do not require activation, storing notifications for these apps and only activating the device for apps that necessitate user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the device transitions to active state to deliver push notifications, then notifications are delivered to users, but battery life consumption increases rapidly
Solution Approach 1:
The patent segments push notifications into two categories: those that require device activation (interactive apps like VoIP, video conference) and those that do not (non-interactive apps like calendar, contacts). This segmentation allows the system to deliver notifications differently based on their nature, avoiding unnecessary activation for non-interactive apps and thus reducing battery consumption while maintaining reliable notification delivery for apps that need it.
Solution Approach 2:
The patent applies partial action by selectively activating the device only when necessary (for interactive apps) rather than activating it for all notifications. The system stores notifications for non-interactive apps without activation and only activates when an interactive notification arrives, using partial activation strategy to minimize energy consumption while ensuring complete notification delivery when needed.
2Use of energy by moving object
If the device remains in inactive state to conserve battery power, then battery life is prolonged, but notifications cannot be delivered to users
Solution Approach 1:
The notification handler process maintains a red-list of non-interactive apps in advance, allowing it to pre-determine which notifications can be stored without activation. This preliminary classification enables the system to remain inactive while still being prepared to deliver notifications appropriately when activation becomes necessary, balancing battery conservation with notification reliability.
Solution Approach 2:
The patent introduces an intermediary mechanism (the red-list and notification storage system) that mediates between the inactive state and notification delivery requirements. This intermediary allows the system to handle notifications differently based on their characteristics, enabling battery conservation while maintaining the ability to deliver notifications reliably through selective activation.
3Productivity
If all push notifications trigger device activation, then all notifications are delivered promptly, but unnecessary power consumption occurs for non-interactive apps
Solution Approach 1:
The patent applies local quality by treating different types of notifications differently based on their specific characteristics. Instead of uniform treatment, the system examines each notification's target app and applies appropriate handling: immediate activation for interactive apps needing prompt delivery, and storage without activation for non-interactive apps. This localized differentiation optimizes both delivery speed for necessary apps and energy efficiency for others.
Data Source
AI summary
A method performed by a notification handler process running on a device includes receiving a first push notification for a first application while the recipient device is inactive; determining that delivery of the first push notification would cause the device to become active without prompting a user of the device to interact with the first application; in response to determining what delivery of the first push modification would cause, locally storing the first push notification; receiving a second push notification for a second application while the recipient device is still inactive; determining that delivery of the second push notification would cause the device to become active prompting the user to interact with the second application; and in response to determining what delivery of the second push modification would cause, delivering the received second push notification to the second application and the stored first push notification to the first application.