Terminal Device Server Node Selection Parallel Connection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network access methods for terminal devices often result in decreased speed and user experience due to the lack of efficient server node selection, where clients retry connections after a predetermined duration without automatically switching to another server node if the initial one fails to respond.
Innovation Solution
A method where a terminal device sends connection requests to server nodes at specific intervals, establishing a connection with the first responsive node and skipping subsequent responses from different nodes, thereby reducing resource consumption and delay.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client sends connection requests to multiple server nodes sequentially with retries, then the reliability of network access is improved, but the network access speed and user experience deteriorate
Solution Approach 1:
The system performs preliminary actions by sending connection requests to multiple server nodes simultaneously rather than sequentially. The client initiates parallel connection attempts to several server nodes at the same time, obtaining response information from each node concurrently. This allows the system to identify the fastest responding server node in advance, ensuring both reliable network access (by having multiple options) and fast access speed (by selecting the quickest response).
Solution Approach 2:
The system dynamically adjusts the connection establishment process by selecting the server node based on actual response timing rather than following a fixed sequential retry pattern. The client monitors response information from multiple server nodes in real-time and dynamically switches to the fastest responding node, optimizing network access speed while maintaining reliability through adaptive selection.
2Device complexity
If the client waits for the preset duration before retrying another server node, then the device complexity is reduced, but the loss of time increases
Solution Approach 1:
The system maintains continuous useful action by simultaneously obtaining response information from multiple server nodes without idle waiting periods. Instead of pausing to wait for preset durations between retries, the client continuously receives and processes response information from all server nodes in parallel, eliminating wasted time while keeping the connection management logic relatively simple.
Solution Approach 2:
The system skips the traditional sequential retry process with preset waiting durations. By rushing through the connection establishment process simultaneously across multiple server nodes and selecting the fastest response, the system eliminates unnecessary time delays while maintaining manageable complexity through a straightforward selection mechanism.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A server node selection method and a terminal device are provided. In the method, a terminal device first sends a connection request to one server node, and then sends a connection request to another server node after a time interval T. The terminal device first sends a connection request to a first server node. If the terminal device receives, within first preset duration T, response information fed back by the first server node, the terminal device does not need to send a connection request to another server node. This helps save resources. In addition, the terminal device may establish a connection to a server node corresponding to received first response information, and does not need to wait for a feedback from another server node. This helps reduce a delay of establishing a connection between the terminal device and a server node.