Automatic creation of protocol dependent control path for instrument application

• US 20050267977A1
• Filed: 04/15/2004
• Published: 12/01/2005
• Est. Priority Date: 04/15/2004
• Status: Active Grant

• Current Assignee: Agilent Technologies, Inc.
• Original Assignee: Agilent Technologies, Inc.
• Inventors: Berg, Nathan A., Ting, Sara, Tillotson, Timothy Nephi
• Granted Patent: US 7,519,719 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• 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/08 Protocols for interworking; Protocol conversion

Abstract

A method and system for creating a protocol dependent control path for instrument applications. In a representative embodiment, identifications of a client, of an instrument application, of a client specific protocol, and of an application specific protocol are obtained. The client is configured to invoke the application and to communicate using the client specific protocol. The application is configured to communicate using the application specific protocol. Then a control path between the client and the application is automatically created. In another representative embodiment, a system for creating the protocol dependent control path for instrument applications includes a management logic module configured to obtain identification of the client, to obtain identification of the instrument application, to obtain identification of the client specific protocol, to obtain identification of the application specific protocol, and to automatically create the control path between the client and the application.

Claims

1. A method for creating a protocol dependent control path for instrument applications, comprising:

obtaining identification of a client, wherein the client is configured to invoke an instrument application, wherein the client is configured to communicate using a client specific protocol, and wherein the application is configured to communicate using a application specific protocol;

obtaining identification of the application;

obtaining identification of the client specific protocol;

obtaining identification of the application specific protocol; and

automatically creating a control path between the client and the application.

2. The method as recited in claim 1, further comprising:

recording the identification of the client;

recording the identification of the application;

recording the identification of the client specific protocol; and

recording the identification of the application specific protocol.

3. The method as recited in claim 1, wherein the application specific protocol differs from the client specific protocol.

4. The method as recited in claim 1, further comprising:

repeating the method steps of claim 1 for the client and a second application, wherein the second application is configured to communicate using a second application specific protocol and wherein the second application specific protocol differs from the application specific protocol.

5. The method as recited in claim 1, further comprising:

repeating the method steps of claim 1 for a second client and the application, wherein the second client is configured to communicate using a second client specific protocol and wherein the second client specific protocol differs from the client specific protocol.

6. The method as recited in claim 1, further comprising:

repeating the method steps of claim 1 for a second client and a second application, wherein the second client is configured to communicate using a second client specific protocol, wherein the second application is configured to communicate using a second application specific protocol, and wherein the second client specific protocol differs from the client specific protocol.

7. The method as recited in claim 1, wherein the second application specific protocol differs from the application specific protocol.

11. The computer readable memory as recited in claim 8, the instructions further comprising:

repeating the method steps of claim 1 for the client and a second application, wherein the second application is configured to communicate using a second application specific protocol and wherein the second application specific protocol differs from the application specific protocol.

12. The computer readable memory as recited in claim 8, the instructions further comprising:

repeating the method steps of claim 1 for a second client and the application, wherein the second client is configured to communicate using a second client specific protocol and wherein the second client specific protocol differs from the client specific protocol.

13. The computer readable memory as recited in claim 8, the instructions further comprising:

repeating the method steps of claim 1 for a second client and a second application, wherein the second client is configured to communicate using a second client specific protocol, wherein the second application is configured to communicate using a second application specific protocol, and wherein the second client specific protocol differs from the client specific protocol.

8. A computer readable memory device embodying a computer program of instructions executable by the computer, the instructions comprising:

obtaining identification of a client, wherein the client is configured to invoke an instrument application, wherein the client is configured to communicate using a client specific protocol, and wherein the application communicates using a application specific protocol;

obtaining identification of the application;

obtaining identification of the client specific protocol;

obtaining identification of the application specific protocol; and

automatically creating a control path between the client and the application.

9. The computer readable memory as recited in claim 8, the instructions further comprising:

recording the identification of the client;

recording the identification of the application;

recording the identification of the client specific protocol; and

recording the identification of the application specific protocol.

10. The computer readable memory as recited in claim 8, wherein the application specific protocol differs from the client specific protocol.

14. The computer readable memory as recited in claim 8, wherein the second application specific protocol differs from the application specific protocol.

15. A system comprising:

a management logic module configured to obtain identification of a client, to obtain identification of an instrument application, to obtain identification of the client specific protocol, to obtain identification of the application specific protocol, and to automatically create a control path between the client and the application, wherein the client is configured to invoke the application, wherein the client is configured to communicate using a client specific protocol, wherein the application is configured to communicate using a application specific protocol, and wherein the application specific protocol differs from the client specific protocol.

16. The system as recited in claim 15, wherein the control path comprises:

a communication logic module configured to receive communications from the client which conform to the client specific protocol, to translate such communications into communications to which the application is configured to understand and to which the application is configured to appropriately react, and to transfer the translated communications to the application.

17. The system as recited in claim 16, wherein the communication logic module comprises:

a server logic module configured to receive the communications from the client; and

a translator logic module configured to receive the communications from the server logic module and to translate the received communications into communications to which the application is configured to understand and to which the application is configured to appropriately react, and to transfer the translated communications to the application.

18. The system as recited in claim 16, wherein the system further comprises:

the application, wherein the application comprises a virtual instrument and an application component logic module and wherein the virtual instrument is configured to receive communications from the communication logic module and to perform any additional translation of the communications into communications to which the application component logic module is configured to understand and to which the application component logic module is configured to appropriately react, and to transfer such communications to the application component logic module.

19. The system as recited in claim 16, wherein the system further comprises:

an additional communication logic module configured to receive additional communications from an additional client which conform to an additional client specific protocol, to translate such additional communications into communications to which an additional application is configured to understand and to which the additional application is configured to appropriately react, and to transfer the translated additional communications to the additional application.

20. The system as recited in claim 16, wherein the system further comprises:

an additional communication logic module configured to receive additional communications from an additional client which conform to an additional client specific protocol, to translate such additional communications into communications to which the application is configured to understand and to which the application is configured to appropriately react, and to transfer the translated additional communications to the application.