Bulk Notification System Parallel Processing Redundancy Removal
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for sending bulk notifications are inefficient, leading to increased time and redundant notifications as the number of users grows, and require either increasing server numbers or improving server performance, which is costly and time-consuming.
Innovation Solution
A bulk notification sending method that retrieves subscribers from a database, processes notifications in parallel, and uses a redundancy removal system to avoid sending duplicate notifications, employing asynchronous calls and delayed requests to improve efficiency and reduce network costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If notifications are sent sequentially to each user, then the system complexity is low, but the notification sending time increases linearly with the number of users
Solution Approach 1:
The patent divides the subscriber list into multiple groups and processes notifications for each group in parallel using multiple channels. This segmentation allows the system to send notifications simultaneously to different user groups rather than sequentially, thereby reducing total sending time while maintaining manageable system complexity through organized parallel processing.
Solution Approach 2:
The patent introduces a new dimension of parallel processing by utilizing multiple notification channels to send notifications simultaneously to different user groups. This transforms the single-threaded sequential approach into a multi-threaded parallel approach, effectively reducing notification sending time without proportionally increasing system complexity.
2Adaptability or versatility
If the same notification is sent through multiple channels to reach all users, then coverage is improved, but redundant notifications are sent to users subscribed to multiple channels
Solution Approach 1:
The patent performs preliminary actions by collecting subscriber information from multiple channels and identifying duplicate subscribers before sending notifications. This pre-processing step allows the system to eliminate redundant notification targets in advance, ensuring that each user receives only one notification even if they are subscribed to multiple channels, thereby reducing wasted notification resources while maintaining complete coverage.
3Productivity
If the number of servers is increased to improve notification sending performance, then the notification sending speed increases, but the system cost and complexity increase
Solution Approach 1:
The patent implements dynamic channel assignment and parallel processing within the existing server infrastructure. Instead of statically increasing server numbers, the system dynamically utilizes multiple notification channels and processes subscriber groups in parallel, achieving improved notification sending speed through efficient resource utilization rather than through adding more servers, thereby avoiding increased system cost and complexity.
4Productivity
If server performance is improved to enhance notification sending performance, then the notification processing capability increases, but the investment cost and time increase
Solution Approach 1:
The patent changes operational parameters such as notification channel selection, subscriber group division, and processing sequence optimization to enhance notification processing capability. Instead of investing in hardware performance improvements, the system achieves better productivity by optimizing software parameters and processing strategies, thereby improving capability without increasing implementation cost or time.
Data Source
AI summary
A bulk notification sending method includes, in response to sending a notification for providing content through a plurality of channels, retrieving subscribers of the channels connected to the content from a sending target database including information about subscribers for each channel; in response to a retrieved subscriber being a subscriber of a first channel among the channels, storing an identification value of the retrieved subscriber in each of a first storage for storing a sending target and a second storage for a redundancy removal and processing sending of a notification to the retrieved subscriber; and in response to the retrieved subscriber not being the subscriber of the first channel, retrieving the identification value of the retrieved subscriber from the second storage and determining whether to send the notification to the retrieved subscriber depending on whether the identification value of the retrieved subscriber is stored in the second storage.