Host Reset Session Resumption Logic for Network Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques fail to conveniently maintain a TELNET session during a device reboot, leading to lost state and requiring re-authentication and re-execution of transactions, especially in TCP connections, which is inefficient and inconvenient.
Innovation Solution
A method and apparatus that store state information for a network connection before rebooting a device, allowing for seamless resumption of the connection by retrieving and applying this information after reboot, using a management interface and host reset session resumption logic to maintain connectivity without re-authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a device reboots normally, then the device can be reset and restarted, but the TELNET session is disconnected and state information is lost
Solution Approach 1:
The patent applies preliminary action by capturing and storing TCP session state information (including sequence numbers, acknowledgment numbers, and window sizes) before the device reboot occurs. This pre-captured state is then restored after reboot, allowing the session to resume without re-authentication. The state capture happens in advance of the disruption, preventing information loss.
Solution Approach 2:
The patent creates a copy of the TCP session state information and stores it in a persistent location that survives the reboot. This copy includes all necessary protocol state data that would otherwise be lost. After reboot, this copied state is restored to the TCP connection, enabling seamless session resumption without requiring the client to re-establish the entire session state.
2Ease of operation
If a new TCP connection is invoked after reboot, then the device can re-connect, but re-authentication is required and transactions must be re-executed
Solution Approach 1:
The patent performs preliminary capture of authentication state and transaction context before the reboot occurs. By storing this state information in advance, the system eliminates the need for re-authentication after reboot. The pre-captured state includes authentication credentials and transaction progress, allowing immediate resumption without time loss.
Solution Approach 2:
The patent changes the state parameters of the TCP connection by restoring saved values for sequence numbers, acknowledgment numbers, and window sizes. This parameter restoration allows the connection to resume exactly where it left off, rather than starting a new connection with default parameters. The authentication state parameters are also restored, eliminating re-authentication requirements.
3Reliability
If the TCP protocol is modified to include a migrate request, then session resumption is possible, but client device software must be modified
Solution Approach 1:
The patent introduces an intermediary mechanism on the server side that handles session state capture and restoration without requiring client modifications. The server acts as a mediator by independently managing the TCP state persistence and restoration, using standard TCP protocols that the client already understands. This intermediary approach enables session resumption while maintaining compatibility with existing client implementations.
Solution Approach 2:
The patent extracts the session state persistence functionality from the client device and relocates it to the server side. By taking out the complexity of state management from the client and implementing it server-side, the patent eliminates the need for client software modifications. The server independently captures, stores, and restores TCP state information using standard protocols, simplifying the overall system architecture.
Data Source
AI summary
Methods and apparatus are disclosed for transparently resuming the network connection after a reset or reboot. In one aspect a data processing apparatus comprises an operating system unit configured to create and store state information comprising one or more parameters for a network connection between a first computing device and a second computing device; a management interface unit configured to receive a request to reboot the first computing device; and host reset session resumption logic configured to store, in response to the request, the state information in a particular location in a memory of the first computing device, to initiate a reboot of the first computing device, to retrieve the state information from the particular location in memory, and to request resuming data communications over the network connection based on the retrieved state information.