Email Notification Architecture for Battery-Constrained Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Devices operating under restrictive OS policies cannot maintain continuous background processes for email monitoring, preventing timely notifications of new messages due to limitations on background application execution.
Innovation Solution
A networked environment with a monitoring service and notification brokering service that maintains subscription information and device access tokens, allowing for near-real-time notifications even when the client application is not actively running by querying the email service and sending notifications through push services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the device runs the application as an active or background process to monitor the email inbox, then the device can detect new messages in near real-time, but battery consumption increases and device performance is degraded
Solution Approach 1:
Instead of having the client application continuously monitor the inbox (traditional approach), the patent inverts the architecture by having the email service provider push notifications to the client application only when new messages are delivered. This eliminates the need for continuous background monitoring while maintaining real-time notification capability.
Solution Approach 2:
The patent implements periodic polling at extended intervals (e.g., every 15 minutes) instead of continuous monitoring, combined with event-driven push notifications. This hybrid approach ensures that even when push notifications are unavailable, the system can detect new messages at periodic intervals with minimal battery consumption.
2Use of energy by stationary object
If the operating system restricts background process execution to optimize battery consumption, then battery life is extended, but the application cannot monitor the inbox and notify users of new messages
Solution Approach 1:
The patent introduces a notification service as an intermediary between the email service provider and the client application. This notification service receives push notifications from the email service and delivers them to the client application, enabling reliable message notification without requiring the application to run continuously in the background.
Solution Approach 2:
The system performs preliminary actions by establishing subscription relationships and notification channels in advance. The client application subscribes to inbox notifications, and the notification service is pre-configured to deliver messages, so that when new emails arrive, the notification infrastructure is already in place to deliver them immediately without requiring active background processes.
3Loss of information
If the application periodically queries the email service to check for new messages, then new messages can be detected, but the device consumes additional energy and increases network traffic
Solution Approach 1:
The patent implements a feedback mechanism where the email service provider actively notifies the client application when new messages are delivered. This push-based feedback system eliminates the need for continuous polling queries, as the system receives automatic notifications only when relevant information changes (i.e., when new messages arrive).
Data Source
AI summary
Disclosed are various examples for communicating notifications for received email messages. A monitoring service monitors inboxes to which clients are subscribed. When a message arrives in a subscribed inbox, the monitoring service sends a notification to a notification brokering service. The notification brokering service then forwards the notification to the appropriate notification service for communication to a subscribed client.