App Provider Notification System Using Proprietary Push Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing notification systems, such as Apple Push Notification (APN) and Google Cloud Messaging (GCM), require third-party push tokens for delivering communications, which can be insecure and inefficient, especially when handling high volumes or node failures.
Innovation Solution
An app provider system with a load balancer and a cluster of nodes that facilitates secure and efficient communication delivery between client devices without relying on third-party push tokens, using a reactor module, processor module, and distributed routing tables to manage connections and message queues, and employing replication and fallback mechanisms for node failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If third-party push tokens (APN, GCM) are used for notification delivery, then notification delivery is enabled, but security and efficiency deteriorate when handling high volumes or node failures
Solution Approach 1:
The patent extracts the notification delivery mechanism from third-party services (APN, GCM) and implements a proprietary push token system within the app provider's own infrastructure. This allows the system to control the entire notification lifecycle, improving security and reliability while reducing dependency on external services that may fail or have security vulnerabilities.
Solution Approach 2:
The patent introduces an intermediary component (the app provider's notification service) that sits between the app and the device. This intermediary manages push tokens, handles routing, and coordinates delivery, thereby reducing the complexity of direct third-party integrations and improving overall system reliability through centralized control.
2Reliability
If third-party push tokens are used, then notification delivery is achieved, but security deteriorates
Solution Approach 1:
The patent removes the security vulnerabilities associated with third-party push tokens by extracting the notification delivery function from external services. The system generates and manages its own push tokens, eliminating exposure to third-party security issues while maintaining full notification delivery capability.
3Productivity
If a fixed number of nodes are used in the cluster, then system simplicity is maintained, but productivity decreases when accommodating high volumes
Solution Approach 1:
The patent implements a dynamic node cluster where the number of nodes can be adjusted based on workload demands. The system can automatically add or remove nodes from the cluster, allowing it to scale productivity up or down as needed without requiring permanent infrastructure for peak loads, thus managing complexity while accommodating high volumes.
4Ease of manufacture
If third-party notification services are relied upon, then implementation is simplified, but reliability deteriorates during node failures
Solution Approach 1:
The patent implements failover mechanisms and redundancy in the node cluster before failures occur. When a node fails, the system has pre-configured backup nodes that can immediately take over, cushioning against service interruptions. This approach maintains reliability during failures while keeping implementation manageable through automated failover logic.
Data Source
AI summary
The present disclosure describes systems and methods for an app provider to deliver information—such as notifications, alerts, messages, and other data—between client devices without the use of a third-party push token. When receivers are connected to the app provider system, the app provider will deliver a notification and the communication to the receivers without the use of a third-party push token. When receivers are not connected to the app provider system, the app provider may cache communications and notifications until the next time the receiver connects to the app provider.