Full-Duplex Bi-Directional Communication Over a Remote Procedure Call Based Communications Protocol, And Applications Thereof

• US 20140297731A1
• Filed: 06/17/2014
• Published: 10/02/2014
• Est. Priority Date: 11/08/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: ZHU, Wenbo, YU, Kevin
• Granted Patent: US 9,258,345 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures

Abstract

Systems and methods for reducing the cost but increasing the performance caused in streaming data between a client and a server are described herein. Embodiments of the present invention relate to reducing the cost but increasing the performance by the traditional data streaming where two TCP connections, one for each direction of traffic is used. Further embodiments allow a server in communication with one or more clients using a RPC based communication protocol to bi-directional stream not on two TCP connections but a single TCP connection. In one embodiment, this is achieved by transmitting from the client to the server an initial handshake. If the server receives the handshake, then the client streams a request stream to the server and the server streams a response stream to the client simultaneously over the same single TCP connection establishing full-duplex streaming.

Claims

1. A computer implemented method for providing a full-duplex capable client to establish a full-duplex bi-directional communication stream, comprising:

initiating full-duplex communication over a single protocol connection between the full-duplex capable client and a server via a network, wherein the full-duplex capable client is configured to engage the server by sending an initial handshake to the server, the initial handshake including a request and a body;

receiving an acceptance of the initial handshake, wherein the acceptance of the initial handshake by the server establishes communication between the full-duplex capable client and the server;

streaming a client request stream by the full-duplex capable client to the server following the acceptance of the initial handshake by the server via the network over the single protocol connection;

accepting a response stream from the server over the single protocol connection while the full-duplex capable client streams the client request stream over the single protocol connection; and

enabling the full-duplex bi-directional communication stream over the remote procedure call based communication protocol when the client request stream and the response stream communicate over the single protocol connection simultaneously.

2. The method of claim 1, wherein the single protocol connection uses a reliable streaming protocol.

3. The method of claim 1, further comprising:

streaming additional pipelined client requests to the server over the single protocol connection; and

receiving additional pipelined responses from the server over the single protocol connection;

4. The method of claim 1, further comprising:

receiving a stream termination response from the server the single protocol connection; and

immediately terminating the full-duplex bi-directional communication stream.

5. The method of claim 1, further comprising:

receiving an error response from the server over the single protocol connection;

sending a stream termination request to the server over the single protocol connection; and

terminating the full-duplex bi-directional communication stream.

6. A computer implemented method for providing a full-duplex capable server to establish a full-duplex bi-directional communication stream, comprising:

finalizing full-duplex communication over a single protocol connection between the full-duplex capable server and a client via a network, wherein the full-duplex capable server is configured to accept an initial handshake from the client, the initial handshake including a request and a body;

responding to the initial handshake request by sending an acceptance of the initial handshake, wherein the acceptance of the initial handshake by the full-duplex capable server establishes communication between the full-duplex capable server and the client;

transferring a request stream received by the full-duplex capable server to a server application;

streaming a server response stream to the client that comprises an application response to the request stream by the server application via the network over the single protocol connection; and

enabling a full-duplex bi-directional communication stream over the remote procedure call based communication protocol when the server response stream and the request stream use the single protocol connection simultaneously.

7. The method of claim 6, wherein the single protocol connection uses a reliable streaming protocol.

8. The method of claim 6, further comprising:

transferring additional pipelined client requests received by the full-duplex capable server to the server application; and

streaming additional pipelined server responses to the client that comprise application responses to the additional pipelined client requests by the server application via the network over the single protocol connection.

9. The method of claim 6, further comprising:

streaming a stream termination response to the client over the single protocol connection; and

terminating the full-duplex bi-directional communication stream.

10. The method of claim 6, further comprising:

streaming an error response to the client over the single protocol connection;

receiving a stream termination request from the client; and

terminating the full-duplex bi-directional communication stream.

11. A system for providing a full-duplex capable client to establish a full-duplex bi-directional communication stream, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

initiate full-duplex communication over a single protocol connection between the full-duplex capable client and a server via a network, wherein the full-duplex capable client is configured to engage the server by sending an initial handshake to the server, the initial handshake including a request and a body;

receive an acceptance of the initial handshake, wherein the acceptance of the initial handshake by the server establishes communication between the full-duplex capable client and the server;

stream a client request stream by the full-duplex capable client to the server following the acceptance of the initial handshake by the server via the network over the single protocol connection;

accept a response stream from the server over the single protocol connection while the full-duplex capable client streams the client request stream over the single protocol connection; and

enable the full-duplex bi-directional communication stream over the remote procedure call based communication protocol when the client request stream and the response stream communicate over the single protocol connection simultaneously.

12. The system of claim 11, wherein the single protocol connection uses a reliable streaming protocol.

13. The system of claim 11, the at least one processor further configured to:

stream additional pipelined client requests to the server over the single protocol connection; and

receive additional pipelined responses from the server over the single protocol connection;

14. The system of claim 11, the at least one processor further configured to:

receive a stream termination response from the server over the single protocol connection; and

immediately terminate the full-duplex bi-directional communication stream.

15. The system of claim 11, the at least one processor further configured to:

receive an error response from the server over the single protocol connection;

send a stream termination request to the server over the single protocol connection; and

terminate the full-duplex bi-directional communication stream.

20. The system of claim 15 the at least one processor further configured to:

stream an error response to the client over the single protocol connection;

receive a stream termination request from the client; and

terminate the full-duplex bi-directional communication stream.

16. A system for providing a full-duplex capable client to establish a full-duplex bi-directional communication stream, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

finalize full-duplex communication over a single protocol connection between the full-duplex capable server and a client via a network, wherein the full-duplex capable server is configured to accept an initial handshake from the client, the initial handshake including a request and a body;

respond to the initial handshake request by sending an acceptance of the initial handshake, wherein the acceptance of the initial handshake by the full-duplex capable server establishes communication between the full-duplex capable server and the client;

transfer a request stream received by the full-duplex capable server to a server application;

stream a server response stream to the client that comprises an application response to the request stream by the server application via the network over the single protocol connection; and

enable a full-duplex bi-directional communication stream over the remote procedure call based communication protocol when the server response stream and the request stream use the single protocol connection simultaneously.

17. The system of claim 16, wherein the single protocol connection uses a reliable streaming protocol.

18. The system of claim 16, the at least one processor further configured to:

transfer additional pipelined client requests received by the full-duplex capable server to the server application; and

stream additional pipelined server responses to the client that comprise application responses to the additional pipelined client requests by the server application via the network over the single protocol connection.

19. The system of claim 16, the at least one processor further configured to:

stream a stream termination response to the client over the single protocol connection; and

terminate the full-duplex bi-directional communication stream.

21. A computer implemented method, comprising:

initiating full-duplex communication over a single protocol connection between the full-duplex capable client and a server via a network, wherein the full-duplex capable client is configured to engage the server by sending an initial handshake to the server, the initial handshake including a request and a body;

waiting for a time-out period to determine that an acceptance of the initial handshake by the server is absent; and

initializing a fallback communication method, wherein the fallback communication method is a bi-directional, dual TCP connection method.

22. The method of claim 21 wherein the fallback communication method is a hanging GET method.

23. The method of claim 21, wherein the fallback communication method is a long polling method.

24. The method of claim 21, wherein the fallback communication method is a long-lived request method

25. A system, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

initiate full-duplex communication over a single protocol connection between the full-duplex capable client and a server via a network, wherein the full-duplex capable client is configured to engage the server by sending an initial handshake to the server, the initial handshake including a request and a body;

wait for a time-out period to determine that an acceptance of the initial handshake by the server is absent; and

initialize a fallback communication method, wherein the fallback communication method is a bi-directional, dual TCP connection method.

26. The system of claim 25, wherein the fallback communication method is a hanging GET method.

27. The system of claim 25, wherein the fallback communication method is a long polling method.

28. The system of claim 25, wherein the fallback communication method is a long-lived request method.