Dynamic Location Server Initialization via Multicast Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In online gaming systems with multiple game servers, the initialization of additional location servers in a replication group often results in message omission or loss, as some messages received from game servers may not be stored in the location server during the initialization process, leading to increased system load and data inconsistencies.
Innovation Solution
A method and system for dynamically initializing a location server by registering the new server to a multicast group, transferring status update messages from a service server, and performing a message dump only after ensuring the new server can stably receive messages, thereby preventing message omission and optimizing the message pool by removing duplicates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If a location server is added to a replication group, then system load is alleviated, but message omission occurs during initialization
Solution Approach 1:
The patent applies preliminary action by establishing a stable message reception connection before initiating the message dump process. The system first verifies that the new location server can successfully receive messages from game servers, then proceeds to dump messages from the old server. This sequence prevents message omission by ensuring the new server is ready to receive messages before the dump begins.
Solution Approach 2:
The patent implements feedback mechanisms to monitor message reception stability during initialization. The system continuously checks whether the new location server can successfully receive messages and uses this feedback information to determine when to start the message dump process, ensuring complete message transfer without omission.
2Reliability
If message dump is performed during initialization, then data consistency is achieved, but message loss occurs for messages received after dump starts
Solution Approach 1:
The system performs preliminary verification of message reception stability before initiating the message dump. This preliminary action ensures that the new location server is fully capable of receiving messages, and the dump process is triggered only when reception stability is confirmed, preventing loss of messages received during the dump operation.
Solution Approach 2:
The patent applies dynamics by making the initialization process adaptive and flexible. The system dynamically adjusts the initialization sequence based on real-time message reception status, allowing the message dump to occur only when the new server is confirmed to be stable, thus avoiding message loss while maintaining data consistency.
3Adaptability or versatility
If location servers are added to replication group, then system scalability is improved, but initialization complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the initialization process into distinct, manageable phases: first establishing message reception stability, then performing the message dump, and finally optimizing the message pool. This segmentation reduces initialization complexity by breaking down the complex task into simpler, sequential steps that can be independently managed.
Solution Approach 2:
The system implements self-service mechanisms where the new location server automatically verifies its own message reception capability and triggers the message dump process without requiring manual intervention. This self-service approach simplifies the initialization process while maintaining scalability, as the system handles its own setup automatically.
Data Source
AI summary
A dynamic server initialization system and method includes a second location server requesting a first location server for a registration to a multicast group associated with a replication group, when the second location server is added to the replication group. The replication group comprises at least one location server. The status update messages received from a predetermined service server are transferred to the second location server, when the registration to the multicast group is completed. The second location server requests the first location server for a message dump when a predetermined reference time elapses. Subsequently, the status update messages which are maintained in a predetermined message pool of the first location server are dumped to the second location server according to the message dump request.