Server Cluster Push Notification Service Load Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional server cluster configurations for push notification services result in high load and costs due to the need for maintaining constant connection sessions, which are not efficiently managed, leading to increased expenses and potential service inefficiencies.
Innovation Solution
A server cluster architecture that separates the management of connections between mobile terminals and push servers from the delivery of push notification events, allowing for efficient allocation and reallocation of push servers based on predetermined criteria, reducing the load on the management server cluster and enhancing system efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a conventional general server cluster system is used for push notification service, then the system can provide push notification functionality, but the load on the load balance server extremely increases, resulting in additional expenses
Solution Approach 1:
The patent divides the server cluster into two distinct types: management servers that handle connection sessions and push servers that deliver notifications. This segmentation allows the load balance server to only manage push server allocation rather than maintaining all connection sessions, significantly reducing its load while maintaining service reliability
Solution Approach 2:
The patent introduces management servers as intermediary components between the load balance server and mobile terminals. These management servers act as mediators that handle the heavy burden of connection session maintenance, allowing the load balance server to focus solely on distributing notification delivery requests to appropriate push servers
2Ease of operation
If all requests maintain a connection session during a heartbeat interval, then the push notification service can be provided, but the cost for maintaining the connection session becomes high
Solution Approach 1:
The patent separates connection session management from notification delivery by assigning connection maintenance to management servers and notification delivery to push servers. This allows connection sessions to be maintained efficiently without requiring the notification delivery system to sustain unnecessary connection overhead
Solution Approach 2:
Management servers automatically manage connection sessions with mobile terminals, handling heartbeat intervals and connection maintenance without requiring continuous intervention from the load balance server or push servers, thereby reducing overall system resource consumption
3Productivity
If a conventional server cluster configuration is used, then the system can operate, but it does not meet the specific requirements of the push notification server due to inefficiency
Solution Approach 1:
The patent creates a specialized server cluster architecture with distinct management servers and push servers, each optimized for their specific functions. This segmentation enables the system to meet push notification service requirements efficiently while maintaining high productivity through specialized role assignment
Solution Approach 2:
The patent assigns different functional qualities to different server types: management servers are optimized for connection management while push servers are optimized for notification delivery. This local quality differentiation allows each component to operate at peak efficiency for its specific purpose, meeting the specialized requirements of push notification services
Data Source
AI summary
A server cluster and method for providing a push notification service are provided. The method includes searching for, by a management server cluster, a first push server corresponding to predetermined search criteria from among a plurality of push servers upon receiving a request to connect with a push server from a mobile terminal; providing, by the management server cluster, connection information regarding the found first push server to the mobile terminal; and delivering, by the first push server, upon generation of a notification event after connecting with the mobile terminal, event information corresponding to the push notification event to the connected mobile terminal.