Message Queue Partitioning for Security Payload Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional push and pull models for notification delivery in cloud environments face issues such as delays and increased costs due to the need for frequent queries, and availability problems with target services, particularly when dealing with large volumes of security payloads.
Innovation Solution
A queuing system that partitions security payloads based on retry numbers and intervals, allowing for balanced distribution across partitions, ensuring successful delivery by retrying transmission attempts when initial attempts fail, and adjusting retry intervals dynamically to manage load and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a pull model is used for notification delivery, then the client can control the trigger for delivery, but delays and added expense occur due to frequent polling queries
Solution Approach 1:
The patent introduces a message queue as an intermediary component between the push notification system and the client. The message queue stores undelivered notifications and manages retry logic, allowing the system to push notifications asynchronously without requiring synchronous polling from the client. This eliminates delivery delays while maintaining client control through the polling interface.
Solution Approach 2:
The system performs preliminary actions by pre-processing and queueing push notifications before the client needs them. When a notification is generated, it is immediately pushed to the message queue with retry metadata, so that when the client polls, the notification is already prepared and available for delivery, eliminating wait time.
2Speed
If a push model is used for notification delivery, then delivery speed is improved, but availability problems with the target service cause delivery failures
Solution Approach 1:
The patent implements beforehand cushioning by introducing a message queue that acts as a buffer between the push notification system and the target client service. When the client service is unavailable, notifications are queued instead of being lost. The system then retries delivery when the service becomes available, cushioning against availability problems while maintaining fast delivery when possible.
Solution Approach 2:
The system implements feedback mechanisms by tracking delivery status and retry counts in the message queue. When push delivery fails due to service unavailability, the system receives feedback about the failure, queues the notification with retry metadata, and automatically retries when conditions improve, thereby improving reliability without sacrificing speed.
3Ease of operation
If millions or billions of polling queries are made daily, then client control is maintained, but added expense occurs
Solution Approach 1:
The patent enables self-service by allowing the message queue to autonomously manage notification delivery without requiring active client polling. The system pushes notifications to the queue and handles delivery automatically based on client availability, eliminating the need for millions of polling queries while preserving client control through the polling interface.
Solution Approach 2:
The message queue serves as an intermediary that decouples the push notification system from client polling operations. Instead of clients directly polling for notifications (requiring millions of queries), the queue manages the interaction, storing notifications and delivering them when clients poll, dramatically reducing the number of queries needed while maintaining client control.
Data Source
AI summary
An apparatus includes a network interface and a processing unit. The network interface transmits a security payload. The processing unit determines a first partition of a queuing service for the security payload at a first time, at least in part based on a determination that an initial attempt to transmit the security payload failed. The processing unit also instructs a retrieval of the security payload from the first partition to perform a first retry attempt to transmit the security payload, at least in part based on a determination that a first retry interval since the first time has elapsed.