System and method for latency monitoring

• US 9,130,842 B2
• Filed: 08/30/2011
• Issued: 09/08/2015
• Est. Priority Date: 08/30/2011
• Status: Active Grant

• Current Assignee: Qatar Foundation
• Original Assignee: Qatar Foundation
• Inventors: Ponsford, Simon, Guerrero, Simon, Yip, William
• Primary Examiner(s): Owens, Douglas W
• Assistant Examiner(s): King, Monica C
• Application Number:
  US13/221,010
• Publication Number:
  US 20130054677A1
• Time in Patent Office: 1,470 Days
• Field of Search: 709/224
• US Class Current: 1/1
• CPC Class Codes: H04L 43/0852 Delays

Abstract

A method for monitoring remote access connection latency between a client device and a server device comprises using a virtual channel between the client device and the server device to determine a value for the latency in a network connection therebetween.

Claims

1. A method for monitoring remote access connection latency between a client device and a server device, comprising:

using a virtual channel over a remote display protocol to transmit data with a timestamp between the client device and the server device, wherein the timestamp is measured from a pre-specified time;

receiving the data with the timestamp at the server device;

determining a current timestamp value of the server device;

determining a latency value of the virtual channel of the remote display protocol in the network connection therebetween using the difference between the timestamp and the current timestamp value of the server device; and

displaying the latency value of the remote display protocol data in the network connection therebetween with a display device at the client.

2. A method as claimed in claim 1, wherein the virtual channel is used to transmit data representing the latency value between the client device and the server device using the network connection.

3. A method as claimed in claim 1, further comprising compiling a limited running list of historic latency values, and using the list to determine an average value for the latency between the client device and server device.

4. A method as claimed in claim 1, further comprising:

compiling a limited running list of historic latency values, and using the list to determine an average value for the latency between the client device and server device;

providing multiple threshold values representing respective different connection statuses;

assigning a status for the connection using the average value; and

incrementing or decrementing a counter associated with the connection statuses based on the assigned status to provide a current status for the connection.

5. A method as claimed in claim 1, further comprising:

compiling a limited running list of historic latency values, and using the list to determine an average value for the latency between the client device and server device;

providing multiple threshold values representing respective different connection statuses;

assigning a status for the connection using the average value;

incrementing or decrementing a counter associated with the connection statuses based on the assigned status to provide a current status for the connection; and

providing a profile list including multiple display parameters for a display device of the client device, wherein respective ones of the multiple display parameters map to respective ones of the connection statuses.

6. A method as claimed in claim 1, further comprising:

compiling a limited running list of historic latency values, and using the list to determine an average value for the latency between the client device and server device;

providing multiple threshold values representing respective different connection statuses;

assigning a status for the connection using the average value;

incrementing or decrementing a counter associated with the connection statuses based on the assigned status to provide a current status for the connection;

providing a profile list including multiple display parameters for a display device of the client device, wherein respective ones of the multiple display parameters map to respective ones of the connection statuses; and

adjusting a parameter of the display device on the basis of the current status and according to the profile list.

7. A method as claimed in claim 1, compiling a limited running list of historic latency values, and using the list to determine an average value for the latency between the client device and server device;

providing multiple threshold values representing respective different connection statuses;

assigning a status for the connection using the average value;

incrementing or decrementing a counter associated with the connection statuses based on the assigned status to provide a current status for the connection; and

providing a profile list including multiple display parameters for a display device of the client device,

wherein respective ones of the multiple display parameters map to respective ones of the connection statuses, and wherein the multiple display parameters include a resolution and colour depth for the display device.

8. A method as claimed claim 1, wherein the network connection is a TCP connection.

9. A method as claimed in claim 1, wherein the display is in a system tray.

10. A method as claimed in claim 1, wherein the display is in a dialog window.

11. A method as claimed in claim 1, wherein the display comprises an indicator with a current quality level classification of the latency value.

12. A client device comprising:

a client device component having a network interface configured to communicate with a server device over a remote display protocol virtual channel to receive data, the data representing a value of latency in a network connection for remote access between the client device and the server device;

wherein the client device component is operable to receive data from the server device over the virtual channel, the data representing a time period between a timestamp in a message received by the server device from the client device and a current timestamp value of the server device, wherein the timestamp is measured from a pre-specified time,

the client device component is further operable to transmit the message with the timestamp to the server device, and

the client device component is operable to display the latency value of the remote display protocol data in the network connection therebetween using a display device at the client.

13. A client device as claimed in claim 12, wherein the client device component is operable to receive a profile list including multiple display parameters for a display device of the client device, the parameters representing respective connection statuses.

14. A client device as claimed in claim 12, wherein the client device component is operable to receive a profile list including multiple display parameters for a display device of the client device, and to adjust a parameter of the display device on the basis of the current status and according to the profile list, the parameters representing respective connection statuses.

15. A client device as claimed in claim 12, wherein the client device component is operable to receive a profile list including multiple display parameters for a display device of the client device, the parameters representing respective connection statuses, and including a resolution and colour depth for the display device.