Notification Identifier Attachment for Reliable Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing push notification systems face challenges in delivering notifications when an application is not operating, as the number of cacheable notifications is limited, leading to missed notifications and increased load on terminal apparatus and notification management servers.
Innovation Solution
A notification sending apparatus that attaches self notification identifiers and sent notification identifiers to each notification, allowing for efficient re-sending of missed notifications based on range specifying information received from the notification receiving apparatus.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If push notification is used to send notifications to terminal apparatus, then notification delivery is achieved when application is operating, but notifications are missed when application is not operating due to cache limitations
Solution Approach 1:
The notification management server performs preliminary actions by storing notification contents in association with identification information before the terminal apparatus needs them. When the application is offline, the server has already prepared the notifications in advance, enabling reliable re-delivery without requiring the application to actively fetch them.
Solution Approach 2:
The notification management server acts as an intermediary between the push notification server and the terminal apparatus. It receives notifications from the push notification server, stores them in association with identification information, and selectively delivers them to the terminal apparatus based on the application's operational state, thereby preventing notification loss.
2Reliability
If handshake communication is used to check notification receipt, then notification delivery status is confirmed, but communication load on terminal apparatus and notification management server increases
Solution Approach 1:
The terminal apparatus performs self-service by autonomously determining whether to request re-sending of notifications based on its own operational state. The application checks its own status and initiates re-send requests only when necessary, eliminating the need for continuous handshake communications with the notification management server.
Solution Approach 2:
Instead of continuous handshake communication, the system uses periodic action where the terminal apparatus requests re-sending of notifications at appropriate intervals or when coming online after being offline. This reduces communication load while maintaining reliable notification delivery confirmation.
3Reliability
If fetch notification is used instead of push notification, then notifications are received when application is offline, but communication load on terminal apparatus increases due to periodic send requests
Solution Approach 1:
The notification management server serves as an intermediary that receives notifications from the push notification server and stores them in association with identification information. This intermediary function allows the terminal apparatus to simply request re-sending of notifications without needing to periodically send fetch requests, thereby reducing the terminal's communication load.
Solution Approach 2:
The notification management server creates a copy of the notification contents and stores it in association with identification information. When the terminal apparatus needs notifications, it requests the copy from the server rather than fetching new notifications periodically, reducing unnecessary communication traffic from the terminal.
4Reliability
If cache is provided in terminal apparatus to hold notifications, then notifications are stored when application is not operating, but number of cacheable notifications is limited
Solution Approach 1:
The system moves the storage function from the terminal apparatus to the notification management server, changing the dimensional location of the cache. The server stores notifications in association with identification information, providing effectively unlimited storage capacity compared to the terminal's limited cache, while maintaining the ability to deliver notifications reliably.
Data Source
AI summary
A notification sending apparatus comprising: a self notification identifier attaching unit configured to attach a self notification identifier to each notification, the self notification identifier having at least a sending ordinal position identification function; a sent notification identifier attaching unit configured to attach, to each notification, the self notification identifier attached to a notification that was sent immediately before each notification, as a sent notification identifier; a sending unit configured to send a notification receiving apparatus the notifications, each of which is attached with the self notification identifier and the sent notification identifier; and a re-sending unit configured, upon receipt of a re-send request including a range specifying information from the notification receiving apparatus, to obtain at least one notification that has been sent and needs to be re-sent based on the range specifying information, and to re-send the at least one obtained notification to the notification receiving apparatus.