Instant Message Session Continuity via Automatic Server Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Instant Messaging (IM) systems face service interruptions and excessive load pressure when a login server becomes unavailable, requiring users to re-login and re-establish sessions, leading to data loss and simultaneous high load on new servers.
Innovation Solution
Implementing a process where clients automatically switch to a new login server by using a login allocation server to identify available servers, storing and verifying client property information, and maintaining IM sessions through caching and reconnection requests, ensuring seamless session continuity without data loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users manually re-login to a new login server when the current server becomes unavailable, then service continuity is maintained, but user time is lost and operation complexity increases
Solution Approach 1:
The system performs preliminary actions by storing session information in advance on multiple login servers. When a server becomes unavailable, the client can immediately switch to a pre-configured alternative server without requiring user re-login, thus resolving the contradiction between service continuity and time loss
Solution Approach 2:
The system implements self-service by automatically detecting login server availability and performing seamless server switching without user intervention. The client automatically reconnects to an available login server using stored session information, eliminating the need for manual re-login operations
2Reliability
If all disconnected clients simultaneously retry to log in to another login server, then service recovery is achieved, but excessive load pressure is imposed on the login server
Solution Approach 1:
Session information is prepared in advance and distributed across multiple login servers. When disconnection occurs, clients can immediately connect to alternative servers that already have their session data ready, avoiding simultaneous login requests and reducing server load while ensuring service recovery
Solution Approach 2:
The system uses an intermediary mechanism where session information is cached on alternative login servers before actual connection switching occurs. This intermediary layer allows clients to switch servers without creating simultaneous login traffic, thus protecting the target server from excessive load while enabling service recovery
3Reliability
If users are redirected to the login interface when the login server becomes unavailable, then authentication security is maintained, but service interruption occurs and user experience deteriorates
Solution Approach 1:
Authentication credentials and session information are verified and stored in advance on multiple login servers. When a server fails, the client can immediately use pre-verified credentials to connect to an alternative server without returning to the login interface, maintaining both security and user experience
Solution Approach 2:
The system dynamically switches between multiple login servers based on availability while maintaining consistent authentication security. The client can adaptively connect to different servers using pre-established session information, ensuring both security requirements and ease of operation are satisfied
Data Source
AI summary
Maintaining an Instant Message (IM) session includes sending a login request to a first login server from a client; establishing the IM session and transferring Instant Messages between the client and the first login server; detecting an interruption in the transfer of the Instant Messages; obtaining an address of a second login server from a login allocation server; sending a reconnection request from the client to the second login server; and in the event that the reconnection request is accepted by the second login server, exchanging Instant Messages between the client and the second login server.