METHOD AND SYSTEM FOR TRANSPORTING TELEMETRY DATA ACROSS A NETWORK

• US 20100241722A1
• Filed: 03/20/2009
• Published: 09/23/2010
• Est. Priority Date: 03/20/2009
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Seminaro, Michael D., Smirnov, Andrey A., Tallapaneni, Krishna Prasad, Harder, Alan Keith, Mar, Christopher Eugene
• Granted Patent: US 8,732,258 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications

Abstract

A method for transporting telemetry data involves receiving a request from a client in a first network. The client is registered with a data transport service executing in a second network. The request includes an authentication credential for the client, a message including telemetry data, and a message priority. The method further involves authenticating the request using the authentication credential. The method further involves parsing the request to obtain and subsequently execute a command for storing the message in a physical queue of the second network. The physical queue is associated with a back-end service executing in the second network. A virtual queue maintains entries for messages stored in the physical queue that were sent from the first network to the second network. Another virtual queue maintains entries for messages stored in the physical queue that were sent from the second network to the first network.

Claims

1. A method for transporting telemetry data across a network comprising:

receiving a first request from a first client application executing on a first client operatively connected to a first network, wherein the first client is registered with a data transport service executing on a first physical node operatively connected to a second network, and wherein the first request comprises a first authentication credential for the first client, a first message comprising telemetry data, and a first message priority for the first message;

authenticating the first request using the first authentication credential;

parsing the first request to obtain a first command for storing the first message in a physical queue associated with a back-end service, wherein the physical queue is located in a message repository operatively connected to the second network, and wherein the back-end service is executing on a second physical node operatively connected to the second network;

storing the first message in the physical queue; and

storing a first entry for the first message in a first virtual queue, wherein the first virtual queue is associated with the physical queue and the back-end service, wherein the first virtual queue comprises entries for messages received from the first client application, and wherein the first entry comprises the first message priority,

wherein a second virtual queue is associated with the physical queue and the back-end service, wherein the second virtual queue comprises entries for messages received from a second client application executing on a second client operatively connected to the second network, wherein the second client is registered with the data transport service, and wherein the second client application is associated with the back-end service.

2. The method of claim 1, further comprising:

receiving a second request from a first instance of a dispatch service executing on a third client operatively connected to the second network, wherein the third client is registered with the data transport service, wherein the first instance of the dispatch service is associated with the back-end service, and wherein the second request comprises a second authentication credential for the third client;

authenticating the second request using the second authentication credential;

parsing the second request to obtain a second command for retrieving a second message stored in the physical queue;

identifying the second message using the first virtual queue, wherein a second entry for the second message is stored in the first virtual queue, wherein the second entry comprises a second message priority for the second message, and wherein the second message priority is the highest message priority of any message priority in the first virtual queue;

retrieving the second message from the physical queue; and

sending a first response comprising the second message to the third client.

3. The method of claim 2, wherein the back-end service receives the second message from the first instance of the dispatch service.

4. The method of claim 2, wherein the first request and the second request are Hypertext Transport Protocol (HTTP) requests.

5. The method of claim 3, further comprising:

receiving a third request from the first instance of the dispatch service, wherein the third request comprises the second authentication credential;

authenticating the third request using the second authentication credential;

parsing the third request to obtain a third command for deleting the second message;

deleting the second message from the physical queue; and

deleting the second entry from the first virtual queue.

6. The method of claim 5, further comprising:

receiving a fourth request from the second client application, wherein the fourth request comprises a third authentication credential for the second client, a third message, and a third message priority for the third message;

authenticating the fourth request using the third authentication credential;

parsing the fourth request to obtain a fourth command for storing the third message in the physical queue;

storing the third message in the physical queue; and

storing a third entry for the third message in the second virtual queue, wherein the third entry comprises the third message priority.

7. The method of claim 6, further comprising:

receiving a fifth request from a second instance of the dispatch service executing on a fourth client operatively connected to the first network, wherein the fourth client is registered with the data transport service, and wherein the fifth request comprises a fourth authentication credential for the fourth client;

authenticating the fifth request using the fourth authentication credential;

parsing the fifth request to obtain a fifth command for retrieving a fourth message stored in the physical queue;

identifying the fourth message using the second virtual queue, wherein a fourth entry for the fourth message is stored in the second virtual queue, wherein the fourth entry comprises a fourth message priority for the fourth message,

and wherein the fourth message priority is the highest message priority of any message priority in the second virtual queue;

retrieving the fourth message from the physical queue; and

sending a second response comprising the fourth message to the fourth client.

8. The method of claim 7, further comprising:

receiving a sixth request from the second instance of the dispatch service, wherein the sixth request comprises the fourth authentication credential;

authenticating the sixth request using the fourth authentication credential;

parsing the sixth request to obtain a sixth command for deleting the fourth message;

deleting the fourth message from the physical queue; and

deleting the fourth entry from the second virtual queue.

9. The method of claim 1, wherein the first virtual queue only comprises messages received from clients located in a first geographic location, wherein the second virtual queue only comprises messages received from clients located in a second geographic location wherein the first client is located in the first geographic location.

10. The method of claim 1, wherein the authentication credential is selected from the group comprising a unique client identifier and a client-generated signature.

11. A system for transporting telemetry data across a network, comprising:

a first client operatively connected to a first network, wherein the first client hosts a first client application configured to;

send a first request to a data transport service executing on a first physical node operatively connected to a second network, wherein the first request comprises a first authentication credential for the first client, a first message comprising telemetry data, and a first message priority for the first message,

wherein the first client is registered with the data transport service;

the data transport service executing on the first physical node operatively connected to the second network, comprising;

a physical queue, wherein the physical queue is associated with a back-end service executing on a second physical node operatively connected to the second network;

a first virtual queue, wherein the first virtual queue is associated with the physical queue and the back-end service, and wherein the first virtual queue comprises entries for messages received from the first client application; and

a second virtual queue, wherein the second virtual queue is associated with the physical queue and the back-end service, wherein the second virtual queue comprises entries for messages received from a second client application executing on a second client operatively connected to the second network, wherein the second client is registered with the data transport service, and wherein the second client is associated with the back-end service;

wherein the data transport service is configured to;

receive the first request from the first client application;

authenticate the first request using the first authentication credential;

parse the first request to obtain a first command for storing the first message in the physical queue;

store the first message in the physical queue; and

store a first entry for the first message in the first virtual queue, wherein the first entry comprises the first message priority;

the back-end service executing on the second physical node operatively connected to the second network.

12. The system of claim 11, further comprising:

a third client operatively connected to the second network, wherein the third client hosts a first instance of a dispatch service configured to;

send a second request to the data transport service, wherein the second request comprises a second authentication credential for the third client,

wherein the third client is registered with the data transport service, and wherein the first instance of the data transport service is associated with the back-end service;

wherein the data transport service is further configured to;

receive the second request from the first instance of the dispatch service;

authenticate the second request using the second authentication credential;

parse the second request to obtain a second command for retrieving a second message stored in the physical queue, wherein the second message comprises telemetry data;

identify the second message using the first virtual queue, wherein a second entry for the second message is stored in the first virtual queue, wherein the second entry comprises a second message priority for the second message, and wherein the second message priority is the highest message priority of any message in the first virtual queue;

retrieve the second message from the physical queue; and

send a first response comprising the second message to the third client.

13. The system of claim 12, wherein the first instance of the dispatch service is further configured to:

send the second message to the back-end service; and

wherein the back-end service is configured to;

receive the second message from the first instance of the dispatch service; and

process the telemetry data of the second message.

14. The system of claim 13, wherein the first instance of the dispatch service is further configured to:

send a third request to the data transport service, wherein the third request comprises the second authentication credential; and

wherein the data transport service is further configured to;

receive the third request from the first instance of the dispatch service;

authenticate the third request using the second authentication credential;

parse the third request to obtain a third command for deleting the second message;

deleting the second message from the physical queue; and

deleting the second entry from the first virtual queue.

15. The system of claim 14, further comprising:

the second client operatively to the second network, wherein the second client hosts the second client application configured to;

send a fourth request to the data transport service, wherein the fourth request comprises the third authentication credential for the second client, a third message, and a third message priority for the third message; and

wherein the data transport service is further configured to;

receive the fourth request from the second client application;

authenticate the fourth request using the third authentication credential;

parse the fourth request to obtain a fourth command for storing the third message in the physical queue;

store the third message in the physical queue; and

store a third entry for the third message in the second virtual queue, wherein the third entry comprises the third message priority.

16. The system of claim 11, wherein the first virtual queue only comprises messages received from clients located in a first geographic location, wherein the second virtual queue only comprises messages received from clients located in a second geographic location wherein the first client is located in the first geographic location.

17. The system of claim 11, wherein the first request and the second request are Hypertext Transport Protocol (HTTP) requests.

18. The system of claim 11, wherein the authentication credential is selected from the group comprising a unique client identifier and a client-generated signature.

19. A computer-readable storage medium, comprising executable instructions to:

receive a first request from a first client application executing on a first client operatively connected to a first network, wherein the first client is registered with a data transport service executing on a first physical node operatively connected to a second network, and wherein the first request comprises a first authentication credential for the first client, a first message comprising telemetry data, and a first message priority for the first message;

authenticate the first request using the first authentication credential;

parse the first request to obtain a first command for storing the first message in a physical queue associated with a back-end service, wherein the physical queue is stored in a message repository operatively connected to the second network, and wherein the back-end service is executing on a second physical node operatively connected to the second network;

store the first message in the physical queue; and

store a first entry for the first message in a first virtual queue, wherein the first virtual queue is associated with the physical queue and the back-end service, wherein the first virtual queue comprises entries for messages received from the first client application, and wherein the first entry comprises the first message priority,

wherein a second virtual queue is associated with the physical queue and the back-end service, wherein the second virtual queue comprises entries for messages received from a second client application executing on a second client operatively connected to the second network, wherein the second client is registered with the data transport service, and wherein the second client application is associated with the back-end service,

wherein the first virtual queue only comprises messages received from clients located in a first geographic location, wherein the second virtual queue only comprises messages received from clients located in a second geographic location wherein the first client is located in the first geographic location,

wherein the first request and the second request are Hypertext Transport Protocol (HTTP) requests.

20. The computer-readable storage medium of claim 19, further comprising executable instructions to:

receive a second request from a first instance of a dispatch service executing on a third client operatively connected to the second network, wherein the third client is registered with the data transport service, wherein the first instance of the dispatch service is associated with the back-end service, and wherein the second request comprises a second authentication credential for the third client;

authenticate the second request using the second authentication credential;

parse the second request to obtain a second command for retrieving a second message stored in the physical queue;

determine the second message using the first virtual queue, wherein a second entry for the second message is stored in the first virtual queue, wherein the second entry comprises a second message priority for the second message, and wherein the second message priority is the greatest message priority of any message priority comprised by an entry stored in the first virtual queue;

retrieve the second message from the physical queue; and

send a first response comprising the second message to the third client.