Notification Channel Hierarchy for Push Delivery Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in ensuring timely and reliable delivery of push notifications due to device settings, operating system limitations, server delays, message queue overloads, third-party service issues, and security/privacy concerns, leading to delayed or missed notifications that impact customer engagement and promotional success.
Innovation Solution
A method and system that utilize a hierarchy of communication channels, including Firebase Cloud Messaging (FCM) and Original Equipment Manufacturer (OEM) tokens, to transmit notifications, with failover mechanisms to ensure delivery through multiple channels, such as SMS or email, if primary channels fail.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single communication channel is used for push notification delivery, then the system complexity is low, but the reliability of notification delivery deteriorates due to single-point failures
Solution Approach 1:
The communication channel is segmented into multiple independent pathways: primary channel (FCM/OEM tokens) and secondary channel (SMS gateway). This segmentation allows the system to divide the notification delivery task across different communication protocols, ensuring that failure in one channel does not prevent delivery through the other.
Solution Approach 2:
The system implements beforehand cushioning by pre-configuring backup communication channels and establishing failover mechanisms in advance. When the primary push notification channel fails, the system automatically transitions to the secondary SMS channel, providing a cushion against delivery failures before they impact the user experience.
2Reliability
If multiple communication channels are implemented with failover mechanisms, then the reliability of notification delivery improves, but the device complexity increases
Solution Approach 1:
The system introduces an intermediary component (message queue system with failover logic) that manages the complexity of multiple communication channels. This intermediary handles channel selection, failure detection, and automatic switching between FCM/OEM tokens and SMS gateway, isolating the complexity from the core notification logic.
Solution Approach 2:
The communication system is designed with universality by creating a multi-functional notification delivery infrastructure that can operate through different protocols (push notifications via FCM/OEM, SMS via gateway). This universal design allows a single system to fulfill multiple delivery functions, reducing the need for separate specialized systems.
3Reliability
If push notifications are sent through primary channels (FCM/OEM tokens), then the delivery speed is fast, but the reliability deteriorates due to device settings and operating system limitations
Solution Approach 1:
The system implements dynamics by making the communication channel selection adaptive rather than static. The failover mechanism dynamically switches from the fast but unreliable push notification channels (FCM/OEM) to the slower but more reliable SMS gateway based on real-time delivery status, optimizing the balance between speed and reliability.
Solution Approach 2:
The system uses feedback from the primary channel's delivery status to trigger automatic switching to the secondary channel. When the push notification system reports failure or timeout, this feedback initiates the failover process to SMS, ensuring that delivery attempts continue through alternative pathways.
4Productivity
If message queues are overloaded during peak times, then the system can handle high volume, but the productivity of notification delivery deteriorates due to delays
Solution Approach 1:
The system addresses message queue overload by adding another dimension to the communication architecture - the SMS gateway channel operates independently from the push notification message queues. This dimensional addition allows notifications to bypass overloaded FCM/OEM queues by routing through the SMS gateway, maintaining productivity during peak times.
Data Source
AI summary
A method for transmitting a notification to a target user device via hierarchy of communication channel is disclosed. The method comprises receiving a request to send the notification to the target user device. Further, it is determined that the target user device is an opted-in device enabled to receive the notification. A FCM Token and an OEM token associated with the target user device is obtained. Further, the notification to the target user device using the OEM token via a first channel is transmitted. A failure in receiving the notification by the target user device via the first channel is detected. Further the notification is transmitted to the target user device using the FCM token via a second channel. A failure in receiving the notification via the second channel, by the target user device is detected. Further, the notification to the target user device using a third channel is transmitted.