Dynamic Configuration Modification for Push Notification Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Push messaging systems inefficiencies include mobile devices needing to remain awake to receive messages, leading to battery drain and unnecessary server workload, as existing systems lack accurate status updates about device activity.
Innovation Solution
Modifying configuration values on remote computing devices based on location, user behavior, and device usage patterns to optimize push notification delivery, allowing for efficient scheduling and reducing unnecessary message delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If push messaging is used to deliver messages unprompted, then message delivery speed is improved, but device battery consumption increases and server workload increases
Solution Approach 1:
The system dynamically changes the status update interval parameter based on device activity state. When the device is active, status updates are sent more frequently to enable timely message delivery. When the device is inactive, the status update interval is extended, reducing communication frequency and energy consumption. This parameter adaptation resolves the contradiction by optimizing the balance between message delivery speed and battery consumption based on actual device state.
2Reliability
If the message server sends messages to devices continuously, then message delivery reliability is improved, but server workload increases unnecessarily
Solution Approach 1:
The system implements a feedback mechanism where the mobile device sends status updates to the message server indicating its activity state. The server uses this feedback information to intelligently determine when to deliver messages. Instead of continuous delivery attempts, the server waits for appropriate status updates before delivering messages, thereby maintaining reliability while significantly reducing unnecessary server workload.
3Reliability
If the mobile device checks continuously for new messages, then message delivery reliability is improved, but device battery consumption increases
Solution Approach 1:
Instead of continuous checking, the system uses periodic status updates sent from the mobile device to the message server. The device periodically reports its activity state, and the server uses this information to determine when messages can be delivered. This periodic action maintains message delivery reliability while dramatically reducing device battery consumption compared to continuous checking.
Data Source
AI summary
Implementations may include automatically initiating modification of one or more configuration values of a remote computing device, the configuration values determining how status messages are sent from the remote computing device. The status messages may be sent either at the prompting of a messaging server or, alternatively, autonomously by the computing device. The status message may indicate the state of the computing device, for example, one or more of “awake,”“active,”“idle,” etc., a current battery level, whether the computing device is fully charged or is plugged into an external power source, whether the radio is currently active, current location, the type of network on which the computing device is being used (e.g., Wi-Fi, 3G, 3G). The modifications to the configuration values may be based on, among other things, location, user behavior, or device usage patterns, thus enabling efficient scheduling of push notification delivery based on the modified configurations.