Method for flow control and for reliable communication in a collaborative environment

• US 10,474,514 B2
• Filed: 06/26/2017
• Issued: 11/12/2019
• Est. Priority Date: 08/15/2011
• Status: Active Grant

• Current Assignee: Resolutionmd Incorporated
• Original Assignee: Calgary Scientific Inc.
• Inventors: Thomas, Monroe M., McFadzean, David, Stephure, Matt, Robinson, Kevin
• Primary Examiner(s): Dollinger, Tonia L
• Assistant Examiner(s): Nguyen, Steven C
• Application Number:
  US15/632,539
• Publication Number:
  US 20170357541A1
• Time in Patent Office: 869 Days
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

Flow control of messages to/from clients and services in a remote access system. Within the remote access system a layered architecture may be provided that includes a client layer at a client device, a service layer associated with a service, and a server layer that is a communications proxy for messages sent between the client device and the service. The service layer may have a receive queue for messages received from the client device and a send queue of messages destined for the client device. The server layer may include an outbound queue of messages destined for the client device. Full duplex communications between the client layer and the server layer may be implemented using a service protocol in a first channel for communication between the client layer and the server layer and a second channel for communication between the server layer and the client layer.

Claims

1. A method of providing reliable communications, comprising:

providing a client layer that remotely accesses a service over a network connection;

providing a server layer that proxies communications between the client layer and the service;

facilitating full duplex communications between the client layer and the server layer by implementing a service protocol in a first channel for communication between the client layer and the server layer, and the service protocol in a second channel for communication between the server layer and the client layer;

communicating first sequence acknowledgement messages over the first channel that include a first sequence number of a last message received from the server;

communicating, in response to the first sequence acknowledgment messages, second sequence acknowledgement messages over the second channel that include a second sequence number of a last message received from the client;

detecting a failure of communication on the first channel or the second channel by sending keep alive messages from the service to the client layer and from client layer to the service, and if one of the client layer or service does not receive the keep alive messages within a predetermined period of time, determining that the first channel or the second channel on which the keep alive messages have not been received has failed; and

upon detecting the failure on the first channel or the second channel, reestablishing communication using the service protocol and either a last first sequence number received by the server layer or a last second sequence number received by the client layer.

2. The method of claim 1, wherein the service protocol is Hypertext Transfer Protocol (HTTP) or Hyper Text Transfer Protocol Secure (HTTPS).

3. The method of claim 2, further comprising:

sending an infinite request from the client layer to the server layer on the first channel; and

sending an infinite response from server to the client on the second channel.

4. The method of claim 1, further comprising:

applying independent message sequence numbers to each message sent between the client layer and the server layer to indicate an order in which each message is sent;

sending a message from the client layer or the server layer; and

leaving the message in an outbound client queue at the client layer or in a service send queue in the server layer, respectively.

5. The method of claim 4, further comprising:

receiving a subsequent message from the server layer or the client layer, the subsequent message annotated with a sequence number of a last message successfully received from the client layer or the server layer; and

removing messages having smaller sequence numbers than the sequence number from the outbound client queue and the service send queue.

6. The method of claim 1, further comprising:

resending any messages previously sent that remain in an outbound client queue of the server layer or in a service send queue in client layer when the failure is detected.

7. A method for reliable messaging between a service and a client, comprising:

listening, at the client, for periodic keep alive messages that are communicated by the service on a first half-duplex channel;

listening, at the service, for periodic keep alive messages that are communicated by the client on a second half-duplex channel;

communicating messages between the client and the sever over the first half-duplex channel and the second half-duplex channel, wherein each message contains a unique message sequence number;

communicating a sequence acknowledgement message between the client and the service in response to the messages over the first half-duplex channel and the second half-duplex channel, the sequence acknowledgement message containing the unique message sequence number that was last successfully received by the service and the client;

detecting a communication failure on the first half-duplex channel or the second half-duplex channel if the periodic keep alive messages are not received at the client after a predetermined period of time in order to determine that the first half-duplex channel or the second half-duplex channel on which the keep alive messages have not been received has failed;

reestablishing, by the client, communication with the service over a new first half-duplex channel or a new second half-duplex channel in accordance with the detecting; and

communicating, by the service, messages over the first half-duplex channel or the new first half-duplex channel beginning with a unique sequence number that is after a unique sequence number associated with a last sequence acknowledgement message received by the service.

8. The method of claim 7, further comprising:

waiting, at the service, for the client to reestablish communication over the new first half-duplex connection or the second half-duplex channel.

9. The method of claim 7, further comprising using the unique sequence number to indicate an order in which each message is sent relative to all other messages.

10. The method of claim 7, further comprising:

queuing messages from the client to the server in a client outbound queue; and

removing a message from the client outbound queue after the sequence acknowledgement message containing the unique message sequence number of the message is received at the client.

11. The method of claim 7, further comprising:

queuing messages from the server to the client in a service outbound queue; and

removing a message from the service outbound queue after the sequence acknowledgement message containing the unique message sequence number of the message is received at the service.

12. The method of claim 7, wherein the first half-duplex channel is an infinite response channel established using Hypertext Transfer Protocol (HTTP) or Hyper Text Transfer Protocol Secure (HTTPS).

13. A method for reliable messaging between a service and a client, comprising:

listening, at the client, for periodic keep alive messages that are communicated by the service on a first half-duplex channel;

listening, at the service, for periodic keep alive messages that are communicated by the client on a second half-duplex channel;

communicating messages from the client to the service over the second half-duplex channel in response to associated previous messages communicated from the service to the client, wherein each message contains a unique message sequence number;

detecting a communication failure on the first half-duplex channel or the second half-duplex channel if the periodic keep alive messages are not received at the client after a predetermined period of time in order to determine that the first half-duplex channel or the second half-duplex channel on which the keep alive messages have not been received has failed;

reestablishing, by the client, communication with the service over a new first half-duplex channel or new second half-duplex channel in accordance with the detecting; and

resuming communicating messages from the client to the service over the second half-duplex channel or the new second half-duplex channel in accordance with a last unique message sequence number received by the client.

14. The method of claim 13, further comprising using the unique sequence number to indicate an order in which each message is sent relative to all other messages.

15. The method of claim 13, further comprising:

queuing messages from the client to the server in a client outbound queue; and

removing a message from the client outbound queue after the sequence acknowledgement message containing the unique message sequence number of the message is received at the client.

16. The method of claim 13, wherein the first half-duplex channel is an infinite response channel established using Hypertext Transfer Protocol (HTTP) or Hyper Text Transfer Protocol Secure (HTTPS).

17. The method of claim 13, further comprising:

communicating a sequence acknowledgement message from the service to the client over the first half-duplex channel,

wherein the sequence acknowledgement message contains a unique message sequence number that was last successfully received by the service.

18. The method of claim 17, further comprising, resuming communicating messages from the client to the service beginning with a unique sequence number that is after a unique sequence number associated with a last sequence acknowledgement message received from the service.