Client-adjustable window size for connectionless transfer protocols

• US 9,049,175 B2
• Filed: 12/02/2010
• Issued: 06/02/2015
• Est. Priority Date: 12/02/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Russo, Richard T., Tyler, Aaron Matthew, Reddy, Chandan Rama, Ghosh, Manoj Krishna, Abdelhalim, Alaa H., Seielstad, Roger D., Gurevich, Peter A.
• Primary Examiner(s): Maung, Zarni
• Application Number:
  US12/959,233
• Publication Number:
  US 20120143993A1
• Time in Patent Office: 1,643 Days
• Field of Search: 709/203, 709217-218, 709223-229
• US Class Current: 1/1
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

Described herein are various principles for operating transfer protocols using adaptive flow control techniques. In accordance with some of these principles, a client may adaptively negotiate with a server regarding a window size to use when communicating datagrams using a connectionless content unit transfer protocol like the Trivial File Transfer Protocol (TFTP). In some implementations, a client may inform a server whether to increase or decrease a window size. In these implementations, the client may increase the window size upon determining that a previous window size has led to successful transfer of content without any loss of datagrams and the client may decrease the window size upon detecting a loss of a datagram. Because of the limited resources available in some environments in which these techniques may be used, in some implementations a window size may be increased by small amounts but may be decreased drastically upon detecting a loss.

Claims

1. A method for transmitting content units from a server computing device to at least one client, the method comprising:

receiving, by the server computing device, a request to transfer a content unit to a client with a connectionless transfer protocol;

negotiating, by the server computing device, an initial window size defined as a number of datagrams, with which to begin transferring the content unit to the client;

transmitting, by the server computing device, at least a portion of the content unit to the client using the connectionless transfer protocol and using the initial window size as a current window size;

receiving, by the server computing device, a request from the client to change the number of datagrams of the current window size;

in response to the received request, changing the number of datagrams of the current window size; and

transmitting, by the server computing device, at least another portion of the content unit to the client using the connectionless transfer protocol and using the changed current window size.

2. The method of claim 1, wherein the client is an unauthenticated client.

3. The method of claim 1, wherein the connectionless transfer protocol is a connectionless file transfer protocol.

4. The method of claim 3, wherein the connectionless file transfer protocol is the Trivial File Transfer Protocol (TFTP).

5. The method of claim 1, wherein the method further comprises:

in response to the request to transfer the content unit, transmitting to the client a software facility adapted to;

receive content of the content unit via the connectionless transfer protocol, and to

transmit the request to change the number of datagrams of the current window size.

6. The method of claim 5, wherein receiving the request to change the number of datagrams of the current window size includes:

receiving the request to change the number of datagrams of the current window size from the software facility.

7. The method of claim 1, wherein the method further comprises:

receiving a second request to transfer the content unit using the connectionless transfer protocol, the second request comprising an indication that the client is executing a software facility transferred to the client in response to the request to transfer the content unit.

8. A method for receiving content units distributed by a server, the method comprising:

transmitting, by a computing device, a request to the server to transfer, using a connectionless transfer protocol, a content unit;

negotiating, by the computing device, with the server, a window size, defined in terms of a quantity of datagrams, with which to begin transferring the content unit using the connectionless transfer protocol;

beginning reception, by the computing device, of a portion of the content unit using the connectionless transfer protocol;

determining, by the computing device, whether the portion of the content unit is successfully received by the computing device during a threshold duration of time; and

in response to a result of the determining, transmitting a request to the server to change the number of datagrams of the window size.

9. The method of claim 8, wherein the method further comprises:

additionally determining whether another portion of the content unit is successfully received by the computing device during the threshold duration of time; and

in response to a result of the additionally determining, transmitting another request to the server to change the number of datagrams of the window size.

10. The method of claim 8, wherein determining whether the portion of the content unit is successfully received comprises:

determining whether, during the threshold duration of time, any content of the content unit was received out of sequence.

11. The method of claim 10, wherein the method further comprises:

determining whether a predetermined amount of content is received in a proper sequence after transmission of the request to change the number of datagrams of the window size.

12. The method of claim 10, wherein transmitting the request to change the current window size comprises:

if it is determined that the portion of the content unit is successfully received during the threshold duration of time, then transmitting the request to change the window size includes requesting that the window size be increased by one datagram; and

if it is determined that the portion of the content unit is not successfully received during the threshold duration of time, then transmitting the request to change the window size includes requesting that the window size be reduced by more than one datagram.

13. The method of claim 8, wherein transmitting to the server the request to transfer comprises transmitting an indication that adjustable window sizes are supported by the computing device.

14. The method of claim 8, wherein negotiating with the server the initial window size includes instructing the server to use a particular number of datagrams as the window size.

15. The method of claim 8, wherein the method further comprises:

determining a maximum successful window size for the computing device.

16. The method of claim 15, wherein determining the maximum successful window size comprises:

during a test threshold duration of time following an increase to the window size, determining whether content of the content unit is successfully received;

if the content of the content unit is successfully received during the test threshold duration of time and the window size is greater than the maximum successful window size, increasing the maximum successful window size to the window size; and

if the content of the content unit is not successfully received during the test threshold duration of time and the window size is greater than the maximum successful window size, decreasing the maximum successful window size.

17. At least one computer-readable memory having computer-executable instructions stored therein for causing a computing device to perform operations for distributing files from a server to at least one client, the operations comprising:

receiving a request to transfer, using the Trivial File Transfer Protocol (TFTP), at least one file to a client;

negotiating with the client an initial window size, defined as a number of datagrams, with which to begin transferring the at least one file to the client using TFTP;

transmitting at least a portion of the at least one file using TFTP with the initial window size as a current window size;

receiving a request from the client to change the number of datagrams of the current window size; and

changing the number of datagrams of the current window size according to the request.

18. The at least one computer-readable memory of claim 17, wherein the operations further comprise:

in response to the request to transfer the at least one file, transmitting to the client a software facility adapted to;

receive content of the at least one file via TFTP; and

to

transmit the request to change the number of datagrams of the current window size.

19. The at least one computer-readable memory of claim 18, wherein the operations further comprise:

receiving a second request to transfer the at least one file using TFTP, the second request comprising an indication that the client is executing the software facility.

20. The at least one computer-readable memory of claim 19, wherein transmitting at least the portion of the at least one file comprises transmitting at least one operating system file in accordance with a Windows Deployment Services (WDS) protocol.