Method and apparatus for dynamic data flow control using prioritization of data requests

• US 8,296,451 B2
• Filed: 01/17/2012
• Issued: 10/23/2012
• Est. Priority Date: 02/07/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Corporation
• Original Assignee: Parallel Networks, LLC (epicRealm Licensing LP)
• Inventors: Lowery, Keith A., Davidson, David K., Saxena, Avinash C.
• Primary Examiner(s): BOUTAH, ALINA A
• Application Number:
  US13/351,779
• Publication Number:
  US 20120117147A1
• Time in Patent Office: 280 Days
• Field of Search: 709/203, 709217-219, 709223-226, 709/229, 709/235, 725/2, 725/27, 715/741, 707781-782, 711/113
• US Class Current: 709/229
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A data center determines whether requested content is available at the data center. The content is available when the content is both present at the data center and current. When the requested content is available at the data center, the data center returns the requested content to the browser. When the requested content is locally unavailable at the data center, the requested content is retrieved from an origin server. When retrieval of the content is delayed, the request is prioritized and placed in a queue for handling by the origin server based on the priority of the request. A status page may be communicated to the browser to inform a user of the delay and provide alternate content and status information related to the request determined as a function of the request or the current state of the origin server.

Claims

1. A method for flow controlling data requests in a computer network, comprising:

receiving an initial request message from a flow controlled device, the initial request message being associated with a data request from a requesting browser for data at a protected source;

sending an initial response message to the flow controlled device, the initial response message indicating whether the flow controlled device has permission to send the data request to the protected source;

sending a request to send message to the flow controlled device subsequent to sending an initial response message that indicates the flow controlled device does not have permission to send the data request to the protected source, the request to send message indicating that the flow controlled device has permission to send the data request to a protected server;

receiving a response status message from the flow controlled device, in response to sending request to send message, the response status message indicating how many data requests were received and processed.

2. The method of claim 1, wherein the initial request message includes a request identifier associated with the data request.

3. The method of claim 2, wherein the initial request message includes the data request.

8. The method of claim 1, further comprising:

storing the data request in a queue in response to permission not being granted;

assigning a priority value to the data request.

9. The method of claim 8, further comprising:

servicing a particular data request in the queue having the highest priority value.

10. The method of claim 9, wherein data requests in the queue having a same priority value are serviced in a first in first out order.

11. The method of claim 1, wherein the request to send message includes one or more request identifiers.

12. The method of claim 1, further comprising:

receiving an ownership transfer message from a new flow controlled device, the ownership transfer message indicating that the flow controlled device is no longer active, the ownership transfer message including the request identifier;

determining whether there is a data request stored for the request identifier;

sending an ownership assignment message to the new flow controlled device in response to the ownership transfer message upon determining there is a data request stored for the request identifier, the ownership assignment message providing an association between the request identifier and the data request.

13. The method of claim 12, further comprising:

sending an ownership query message in response to determining there is no data request stored for the request identifier;

receiving an ownership query response message from a flow control server that has the data request stored for the request identifier.

20. The system of claim 12, the flow control server further operable to:

send an ownership query message in response to determining there is no data request stored for the request identifier;

receive an ownership query response message from a flow control server that has the data request stored for the request identifier.

4. A system for flow controlling data requests in a computer network, comprising:

a protected source for storing data;

a flow controlled device operable to receive a data request from a requesting browser, the data request requesting data from the protected source;

a flow control server operable to;

receive an initial request message from the flow controlled device, the initial request message being associated with the data request from the requesting browser for data at the protected source;

send an initial response message to the flow controlled device, the initial response message indicating whether the flow controlled device has permission to send the data request to the protected source;

send a request to send message to the flow controlled device subsequent to sending an initial response message that indicates the flow controlled device does not have permission to send the data request to the protected source, the request to send message indicating that the flow controlled device has permission to send the data request to a protected server;

receive a response status message from the flow controlled device, in response to sending request to send message, the response status message indicating how many data requests were received and processed.

5. The method of claim 4, wherein the initial response message includes a pause value indicating a length of time before the status page is to be sent to the browser.

6. The method of claim 4, wherein the initial response message includes a refresh value indicating a length of time before the status page at the browser is to send a request identifier to the flow controlled device.

7. The method of claim 4, wherein the uniform resource locator is selected from a plurality of uniform resource locators based on one or more of the data being requested, the type of request, the priority of the data request, the load on the protected source, and bandwidth available to the requesting browser.

14. A system for flow controlling data requests in a computer network, comprising:

a protected source for storing data;

a flow controlled device operable to receive a data request from a requesting browser, the data request requesting data from the protected source;

a flow control server operable to;

receive an initial request message from the flow controlled device, the initial response message being associated with the data request from the requesting browser for data at the protected source;

send an initial response message to the flow controlled device, the initial response message indicating whether the flow controlled device has permission to send the data request to the protected source;

send a request to send message to the flow controlled device subsequent to sending an initial response message that indicates the flow controlled device does not have permission to send the data request to the protected source, the request to send message indicating that the flow controlled device has permission to send the data request to the protected server;

receive a response status message from the flow controlled device, the response status message indicating how many data requests were received and processed.

15. The system of claim 14, wherein the initial request message includes:

a request identifier associated with the data request;

the data request.

16. The system of claim 15, wherein the initial response message includes:

a uniform resource locator of a status page to be sent to the requesting browser associated with the flow controlled device;

a pause value indicating a length of time before the status page is to be sent to the browser;

a refresh value indicating a length of time before the status page at the browser is to send a request identifier to the flow controlled device.

17. The system of claim 16, wherein the uniform resource locator is selected from a plurality of uniform resource locators based on one or more of the data being requested, the type of request, the priority of the data request, the load on the protected source, and bandwidth available to the requesting browser.

18. The system of claim 14, the flow control server further operable to:

storing the data request in a queue in response to permission not being granted;

assigning a priority value to the data request;

servicing a particular data request in the queue having the highest priority value.

19. The system of claim 14, the flow control server further operable to:

receive an ownership transfer message from a new flow controlled device, the ownership transfer message indicating that the flow controlled device is no longer active, the ownership transfer message including the request identifier;

determine whether there is a data request stored for the request identifier;

send an ownership assignment message to the new flow controlled device in response to the ownership transfer message upon determining there is a data request stored for the request identifier, the ownership assignment message providing an association between the request identifier and the data request.