Transport accelerator systems and methods

• US 9,930,097 B2
• Filed: 09/29/2014
• Issued: 03/27/2018
• Est. Priority Date: 07/03/2014
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Ulupinar, Fatih, Purkayastha, Punyaslok, Walker, Robert, Mao, Yinian, Kelley, Brian Harold
• Primary Examiner(s): Abedin, Normin
• Application Number:
  US14/500,588
• Publication Number:
  US 20160006805A1
• Time in Patent Office: 1,275 Days
• Field of Search: 709217
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/166 IP fragmentation; TCP segmentation

Abstract

According to some aspects, a transport accelerator of a client device may generate a chunk request that is derived from a fragment request and that has transport acceleration metadata. The transport acceleration metadata may indicate that the request is from a transport accelerator and/or indicate a fragment associated with the fragment request. The transport accelerator may receive a signal to cancel one or more chunk requests and/or wait to receive a full fragment. A client application of the client device may generate the signal upon receipt of an HTTP response from a server that complies with a handshaking procedure.

Claims

1. A method for networked communications, the method comprising:

receiving, by a transport accelerator of a client device from a user agent of the client device, a fragment request, wherein the fragment request is for a data fragment comprising a portion of data being requested by the user agent, wherein the transport accelerator is disposed in a data path between the user agent and a data transport protocol compatibility application of the client device, and wherein the data transport protocol compatibility application is disposed in a data path between the transport accelerator and an input/output element of the client device through which the data being requested by the user agent is to be received;

generating, by the transport accelerator a plurality of chunk requests derived from the fragment request, wherein each chunk request of the plurality of chunk requests is for a different subdivision of the portion of data of the data fragment of the fragment request;

sending, by the transport accelerator to the data transport protocol compatibility application, a chunk request of the plurality of chunk requests as an HTTP request;

receiving, by the transport accelerator from the data transport protocol compatibility application, a signal to signal at least one of;

cancel one or more chunk requests of the plurality of chunk requests derived from the fragment request from which the chunk request was derived;

or

indicate that a response to the chunk request will include an entirety of the data fragment of the fragment request from which the chunk request was derived; and

receiving, by the transport accelerator from the data transport protocol compatibility application, entire data fragment for the fragment request including the subdivision of data of the chunk request, wherein the entire data fragment was received by the data transport protocol compatibility application via the input/output element using an alternative transport protocol to a protocol of the HTTP request for the chunk request sent by the transport accelerator to the data transport protocol compatibility application.

2. The method of claim 1, wherein the signal comprises a signal to cancel one or more chunk requests of the plurality of chunk requests derived from the fragment request from which the chunk request was derived, the method further comprising:

cancelling, by the transport accelerator, the one or more chunk requests in response to the signal.

3. The method of claim 1, wherein the signal comprises a signal to cancel one or more chunk requests of the plurality of chunk requests derived from the fragment request from which the chunk request was derived, the method further comprising:

sending, by the transport accelerator, the fragment request as an HTTP request in response to the signal.

4. The method of claim 1, wherein the signal comprises a signal to indicate that the response to the chunk request will include an entirety of the data fragment of the fragment request from which the chunk request was derived, the method further comprising:

receiving the entirety of the data fragment without sending the fragment request as an HTTP request.

5. The method of claim 1, wherein the HTTP request includes transport acceleration metadata indicating that the HTTP request is sent by a transport accelerator.

6. The method of claim 1, wherein the HTTP request includes transport acceleration metadata indicating the fragment associated with the fragment request from which the chunk request was derived in its entirety.

7. The method of claim 1, wherein the signal received by the transport accelerator from the data transport protocol compatibility application comprises the signal to indicate that a response to the chunk request will include an entirety of the data fragment of the fragment request from which the chunk request was derived.

8. A method for networked communications, the method comprising:

receiving, by a data transport protocol compatibility application of a client device from a transport accelerator of the client device, a chunk request as an HTTP request, wherein the chunk request is a chunk request of a plurality of chunk requests derived from a fragment request, wherein the fragment request is for a data fragment comprising a portion of data being requested by a user agent, wherein each chunk request of the plurality of chunk requests is for a different subdivision of the portion of data of the data fragment of the fragment request, wherein the transport accelerator is disposed in a data path between the user agent and the data transport protocol compatibility application, and wherein the data transport protocol compatibility application is disposed in a data path between the transport accelerator and an input/output element of the client device through which the data being requested by the user agent is to be received;

sending by the data transport compatibility application to a server over a TCP connection via the input/output element, the chunk request as the HTTP request;

receiving, by the data transport protocol compatibility application from the server over the TCP connection via the input/output element, an HTTP response to the HTTP request associated with the chunk request, wherein the HTTP response is compliant with a handshaking procedure associated with an alternative data transport protocol connection to the TCP connection used for the HTTP request;

sending, by the data transport protocol compatibility application to the transport accelerator in response to the HTTP response, a signal to signal at least one of;

cancel one or more chunk requests of the plurality of chunk requests derived from the fragment request from which the chunk request was derived;

or

indicate that a response to the chunk request will include an entirety of the data fragment of the fragment request from which the chunk request was derived;

receiving, by the data transport protocol compatibility application from the server, entire data fragment for the fragment request including the subdivision of data of the chunk request using the alternative data transport protocol connection to the TCP connection used for the HTTP request; and

delivering, by the data transport protocol compatibility application to the transport accelerator, the entire data fragment.

9. The method of claim 8, wherein the signal comprises a signal to cancel one or more chunk requests of the plurality of chunk requests derived from the fragment request from which the chunk request was derived, the method further comprising:

receiving, for the data transport protocol compatibility application from the transport accelerator in response to the signal, the fragment request as an HTTP request.

10. The method of claim 9, further comprising:

altering, by the data transport protocol compatibility application, the HTTP request for fragment request to comply with the handshaking procedure.

11. The method of claim 9, wherein the signal comprises a signal to indicate that the response to the chunk request will include the entirety of the data fragment of the fragment request from which the chunk request was derived, the method further comprising:

receiving the entirety of the data fragment from the server without sending an HTTP request for the fragment request.

12. The method of claim 11, further comprising:

delivering the entirety of the data fragment to the transport accelerator without receiving an HTTP request for the fragment request.

13. The method of claim 8, wherein sending the signal to the transport accelerator includes sending, to the transport accelerator, at least one of an HTTP response code, HTTP header, or HTTP header value.

14. The method of claim 13, wherein the at least one of an HTTP response code, HTTP header, or HTTP header value is the same as another at least one of an HTTP response code, HTTP header, or HTTP header value received in the HTTP response from the server.

15. The method of claim 13, wherein the at least one of an HTTP response code, HTTP header, or HTTP header value is modified by the data transport protocol compatibility application to be different from another at least one of an HTTP response code, HTTP header, or HTTP header value received in the HTTP response from the server.

16. The method of claim 8, wherein the signal sent by the data transport protocol compatibility application to the transport accelerator in response to the HTTP response comprises the signal to indicate that a response to the chunk request will include an entirety of the data fragment of the fragment request from which the chunk request was derived.

17. A method for networked communications, the method comprising:

receiving, by a transport accelerator of a client device from a user agent of the client device, a fragment request, wherein the fragment request is for a data fragment comprising a portion of data being requested by the user agent, wherein the transport accelerator is disposed in a data path between the user agent and a data transport protocol compatibility application of the client device, and wherein the data transport protocol compatibility application is disposed in a data path between the transport accelerator and an input/output element of the client device through which the data being requested by the user agent is to be received;

generating, by the transport accelerator, a plurality of chunk requests derived from the fragment request, wherein each chunk request of the plurality of chunk requests is for a different subdivision of the portion of data the data fragment of the fragment request;

generating, by the transport accelerator, transport acceleration metadata identifying the data fragment of the fragment request from which the chunk request was derived;

sending, by the transport accelerator to the data transport protocol compatibility application, the HTTP request for the chunk request and including the metadata identifying the data fragment; and

receiving, by the transport accelerator from the data transport protocol compatibility application, entire data fragment for the fragment identified in the metadata including the subdivision of data of the chunk request, wherein the entire data fragment was received by the data transport protocol compatibility application using an alternative transport protocol to a protocol of the HTTP request for the chunk request sent by the transport accelerator to the data transport protocol compatibility application.

18. The method of claim 17, wherein the transport acceleration metadata included with the HTTP request includes metadata indicating that the HTTP request is sent by the transport accelerator.

19. The method of claim 17, further comprising:

sending the HTTP request to a server, wherein the server is configured to pre-fetch an entirety of the fragment in response to detecting the transport acceleration metadata identifying the fragment.

20. The method of claim 17, further comprising:

receiving, by the transport accelerator and in response to the HTTP request associated with the chunk request, at least one of one or more status codes or one or more headers.

21. The method of claim 17, further comprising:

receiving, by the transport accelerator, a full response body for the fragment in response to the HTTP request for the chunk request.

22. The method of claim 17, wherein generating the transport acceleration metadata includes at least one of:

generating transport acceleration metadata indicating that the HTTP request is sent by a transport accelerator;

or

generating transport acceleration metadata identifying the HTTP request.