Transport accelerator systems and methods

Patent metadata

Field	Value
Publication number	US-2016006805-A1
Application number	US-201414500588-A
Country	US
Kind code	A1
Filing date	Sep 29, 2014
Priority date	Jul 3, 2014
Publication date	Jan 7, 2016
Grant date	—

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.

First claim

What is claimed is:

1 . A method for networked communications, the method comprising:
generating, by a transport accelerator of a client device, an HTTP request associated with a chunk request derived from a fragment request; and receiving a signal, by the transport accelerator, from a client application of the client device, wherein the signal comprises a signal to at least one of:
cancel one or more 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 a fragment associated with the fragment request from which the chunk request was derived.

2 . The method of claim 1 , wherein the signal comprises a signal to cancel one or more 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 derived from the fragment request from which the chunk request was derived, the method further comprising:
sending, by the transport accelerator, an HTTP request associated with the fragment 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 the entirety of the fragment associated with the fragment request from which the chunk request was derived, the method further comprising:
receiving the entirety of the fragment without sending an HTTP request associated with the fragment request.

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

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

7 . A method for networked communications, the method comprising:
receiving from a transport accelerator of a client device, by a client application of the client device, an HTTP request associated with a chunk request derived from a fragment request; sending to a server over a TCP connection, by the client application, the HTTP request associated with the chunk request; receiving from the server over the TCP connection, by the client application, an HTTP response to the HTTP request associated with the chunk request, wherein the HTTP response is compliant with a handshaking procedure; and sending to the transport accelerator, by the client application and in response to the received HTTP response, a signal, wherein the signal comprises a signal to at least one of:
cancel one or more 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 a fragment associated with the fragment request from which the chunk request was derived.

8 . The method of claim 7 , wherein the signal comprises a signal to cancel one or more chunk requests derived from the fragment request from which the chunk request was derived, the method further comprising:
receiving from the transport accelerator, by the client application and in response to the signal, an HTTP request associated with the fragment request.

9 . The method of claim 8 , further comprising:
altering the received HTTP request associated with the fragment request, by the client application, to comply with the handshaking procedure.

10 . The method of claim 8 , wherein the signal comprises a signal to indicate that the response to the chunk request will include the entirety of the fragment associated with the fragment request from which the chunk request was derived, the method further comprising:
receiving the entirety of the fragment from the server without sending an HTTP request associated with the fragment request.

11 . The method of claim 10 , further comprising:
delivering the entirety of the fragment to the transport accelerator.

12 . The method of claim 7 , 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.

13 . The method of claim 12 , 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.

14 . The method of claim 12 , wherein the at least one of an HTTP response code, HTTP header, or HTTP header value is modified by the client 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.

15 . A method for networked communications, the method comprising:
generating, by a transport accelerator of a client device, an HTTP request associated with a chunk request derived from a fragment request, wherein generating the HTTP request includes generating transport acceleration metadata identifying a fragment associated with the fragment request from which the chunk request was derived; and sending, by the transport accelerator, the HTTP request associated with the chunk request.

16 . The method of claim 15 , wherein sending the HTTP request includes sending the HTTP request to a client application of the client device.

17 . The method of claim 15 , wherein sending the HTTP request includes 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.

18 . The method of claim 15 , 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.

19 . The method of claim 15 , further comprising:
receiving, by the transport accelerator, a full response body for the fragment in response to the HTTP request associated with the chunk request.

20 . The method of claim 15 , wherein generating the HTTP request 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.

Assignees

• Qualcomm Inc

Inventors

• Ulupinar Faith
• Purkayastha Punyaslok
• Walker Robert
• Mao Yinian
• Kelley Brian Harold

Classifications

• H04L69/166

  IP fragmentation; TCP segmentation · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/1095 Primary

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title