RECOVERY OF DISCONNECTED CHANNELS OVER A RELIABLE PROTOCOL

• US 20100049785A1
• Filed: 08/22/2008
• Published: 02/25/2010
• Est. Priority Date: 08/22/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Stoyanov, Vladimir K., Qiu, Kan
• Granted Patent: US 8,793,384 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 1/1607 Details of the supervisory signal
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0811 by checking connectivity

Abstract

Example embodiments of the present disclosure provide techniques for recovering from a channel failure at the protocol layer. At least a portion of data that is sent from a source to a target across the channel can be stored in a communication protocol layer buffer. In the event that the channel fails and is reestablished the target can send a signal indicating how much data it actually received. The signal can be used by the source to determine which portion of the data in the buffer was lost en route to the target and the lost portion can be resent.

Claims

1. A terminal server method comprising:

sending data to a client;

storing at least a portion of the sent data in a buffer;

determining that a connection to the client failed;

reestablishing a connection to the client;

receiving a signal from the client identifying an amount of data that was successfully received by the client;

determining that the client failed to receive a specific portion of the data stored in the buffer based on the signal received from the client; and

sending the specific portion of the data stored in the buffer to the client.

2. The method of claim 1, further comprising:

instantiating a remote desktop protocol stack instance in response to receiving a connection request from the client, wherein the buffer is included in a terminal server layer of the remote protocol stack instance.

3. The method of claim 1, further comprising:

storing information that identifies the amount of the data that was sent to the client.

4. The method of claim 1, wherein the data includes data from a plurality of data sources and the buffer includes a plurality of buffers, each buffer associated with a specific data source of the plurality of data sources.

5. The method of claim 1, further comprising:

sending a signal to the client identifying an amount of data that was successfully received from the client; and

receiving resent data from the client.

6. The method of claim 1, wherein reestablishing the connection to the client further comprises:

determining that the connection was reestablished within a predetermined amount of time.

7. The method of claim 1, wherein reestablishing the connection to the client further comprises:

sending a signal indicative of a request for data to a redirection driver associated with the source of the data.

8. The method of claim 7, wherein reestablishing the connection to the client further comprises:

sending, via the redirection driver, a signal indicative of a request for data to the source of the data.

9. A method comprising:

storing a copy of data sent to a client in a buffer of a data transfer protocol;

receiving a signal from the client identifying an amount of data that was received by the client; and

sending a specific portion of the data stored in the buffer to the client, wherein the specific portion of the data was selected based on the signal received from the client.

10. The method of claim 9, further comprising:

storing information identifying an amount of data sent to the client.

11. The method of claim 9, further comprising:

storing information identifying an amount of data received from the client.

12. The method of claim 9, wherein the data was generated by a redirection driver associated with a plug and play device.

13. The method of claim 9, wherein the data stored in the buffer includes multiplexed data from multiple data sources.

14. The method of claim 9, wherein the signal that identifies the amount of data that was successfully received by the client is included within a client reconnection request.

15. A client device comprising:

circuitry for sending information identifying an amount of data received from a terminal server prior to a failure of a communication channel; and

circuitry for receiving resent data from the terminal server, the resent data was selected from a terminal server layer buffer based on the information identifying the amount of the received data.

16. The client device of claim 15 further comprising:

circuitry for receiving a signal from the terminal sever identifying an amount of data that was successfully received by the terminal sever;

circuitry for determining that the terminal sever failed to receive at least a portion of data stored in a buffer based on the signal received from the terminal sever; and

circuitry for resending the at least a portion of the data to the terminal sever.

17. The client device of claim 15, further comprising:

circuitry for storing information that identifies the amount of the data that was sent to the terminal server.

18. The client device of claim 15, wherein the circuitry for reestablishing the connection to the terminal server further comprises:

circuitry for determining that the connection was reestablished within a predetermined amount of time.

19. The client device of claim 15, further comprising:

circuitry for instantiating a remote desktop protocol stack instance, wherein the buffer is included in a terminal server layer of the remote protocol stack instance.

20. The client device of claim 15, wherein circuitry for sending information identifying an amount of data received from a terminal server prior to a failure of a communication channel further comprises:

circuitry for sending information identifying the amount of data received from the terminal server in a client reconnection request.