Hosting a Graphical Program Execution System on an Embedded Device

• US 20100293528A1
• Filed: 10/02/2009
• Published: 11/18/2010
• Est. Priority Date: 05/18/2009
• Status: Active Grant

• Current Assignee: National Instruments Corporation (Emerson Electric Company)
• Original Assignee: National Instruments Corporation (Emerson Electric Company)
• Inventors: Smith, Malcolm I., Austin, Paul F., Reeve, Brock J., Kudukoli, Ramprasad
• Granted Patent: US 8,271,944 B2
• Time in Patent Office: Days
• US Class Current: 717/113
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/0284 Time or distance, e.g. usage of parking meters or taximeters
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

System and method for performing program-related operations over a network via a web browser. A network connection is established between a server computer and a client computer over a network. A universal resource identifier (URI) is sent from the client computer to the server computer over the network, where the URI indicates a program, e.g., a graphical program (GP), or at least a portion of a graphical program interactive development environment (GPIDE), e.g., a graphical program editor, an execution engine, a static or dynamic analyzer, and/or compiler. The at least a portion of the GPIDE is received from the server computer over the network in response to the URI, and executed in a web browser of the client computer to perform some specified functionality with respect to the GP.

Claims

1. A computer-accessible memory medium that stores program instructions executable by a processor to:

establish a network connection with an embedded device over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, and wherein the embedded device stores a graphical program (GP) and a graphical program execution engine (GP execution engine), wherein the embedded device does not require a display;

receive the GP execution engine from the embedded device over the network in response to the URI; and

execute the GP in a web browser via the GP execution engine to;

control the embedded device in response to user input to the GP executing in the web browser;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browser.

2. The memory medium of claim 1, wherein the GP execution engine comprises an interpreter, and wherein to execute the GP in the web browser via the GP execution engine, the GP execution engine is executable to interpret the GP in the web browser.

3. The memory medium of claim 1, wherein to control the embedded device in response to user input to the GP executing in the web browser, the GP is executable to send commands to the embedded device over the network in response to the user input.

4. The memory medium of claim 1, wherein the GP is executable in the web browser via the GP execution engine to:

access one or more web services over the network;

or

invoke execution of one or more programs or subprograms on other devices over the network.

5. The memory medium of claim 1, wherein the GP is executable in the web browser via the GP execution engine to communicate with the embedded device via one or more of:

shared variables;

or

web services.

6. The memory medium of claim 1, wherein the embedded device is configured to perform one or more of:

a measurement task;

a control task;

a simulation task;

or

an automation task.

7. The memory medium of claim 1, wherein the GP execution engine is configured to execute in a sandbox, wherein the sandbox comprises a secure execution environment for the GP execution engine, and wherein to execute the GP in a web browser via the GP execution engine, the program instructions are executable to:

execute the GP in the sandbox via the GP execution engine.

8. The memory medium of claim 7, wherein the sandbox is implemented by a plugin, and wherein to execute the GP in the sandbox via the GP execution engine, the program instructions are executable to execute the GP in the plugin via the GP execution engine.

9. The memory medium of claim 1, wherein to execute the GP in a web browser via the GP execution engine, the program instructions are executable to:

display a graphical user interface (GUI) of the GP in the web browser on a display, wherein the GUI is configured to;

display results of the GP execution;

or

receive user input specifying input to the GP.

10. The memory medium of claim 1, wherein the GP is embedded in a web page, wherein the URI references the web page, thereby indicating the GP, and wherein to receive the GP execution engine from the embedded device over the network in response to the URI, the program instructions are executable to:

receive the web page from the embedded device over the network, including the GP and the GP execution engine; and

wherein to execute the GP in a web browser via the GP execution engine, the program instructions are further executable to;

display the web page on a display; and

display results of executing the GP in the web page on the display.

11. The memory medium of claim 1, wherein the embedded device further stores a graphical program editor/execution engine (GPEEE), and wherein the program instructions are further executable to:

receive the GPEEE from the embedded device over the network in response to the URI;

execute the GPEEE in the web browser to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP in the web browser;

wherein the program instructions are further executable to;

deploy the edited GP to the embedded device, wherein the edited GP is executable to perform updated one or more functions, and wherein the edited GP is downloadable from the embedded device and executable by client computers to;

control the embedded device in response to user input to the GP executing in web browsers of the client computers;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browsers of the client computers.

12. The memory medium of claim 1, wherein the graphical program comprises a graphical data flow program (GDFP), and wherein the GP execution engine comprises a graphical data flow program execution engine.

13. A computer-implemented method, comprising utilizing a computer to perform:

establishing a network connection with an embedded device over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, and wherein the embedded device stores a graphical program (GP) and a graphical program execution engine (GP execution engine), wherein the embedded device does not require a display;

receiving the GP execution engine from the embedded device over the network in response to the URI; and

executing the GP in a web browser via the GP execution engine to;

control the embedded device in response to user input to the GP executing in the web browser;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browser.

14. A computer-accessible memory medium that stores:

a graphical program execution engine (GP execution engine) for executing graphical programs;

a graphical program (GP), wherein the GP is executable to perform one or more functions; and

program instructions executable by an embedded device to;

establish a network connection with a client computer over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, and wherein the embedded device does not require a display;

send the GP and the GP execution engine to the client computer over the network in response to the URI, wherein the GP is executable in a web browser on the client system via the GP execution engine to;

control the embedded device in response to user input to the GP executing in the web browser;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browser.

15. The memory medium of claim 14, wherein the GP execution engine comprises an interpreter, and wherein in being executable in a web browser via the GP execution engine, the GP is interpretable in the web browser by the GP execution engine.

16. The memory medium of claim 14,

wherein to control the embedded device in response to user input to the GP executing in the web browser, the GP is executable to send commands to the embedded device over the network in response to the user input;

and

wherein the program instructions are further executable to;

receive the commands; and

configure the embedded device to operate in accordance with the commands.

17. The memory medium of claim 14, wherein the GP is executable in the web browser to:

access one or more web services over the network;

or

invoke execution of one or more programs or subprograms on other devices over the network.

18. The memory medium of claim 14, wherein the GP is executable in the web browser to communicate with the embedded device via one or more of:

shared variables;

or

web services.

19. The memory medium of claim 14, wherein the embedded device is configured to perform one or more of:

a measurement task;

a control task;

or

a simulation task;

or

an automation task.

20. The memory medium of claim 14, wherein the embedded device is coupled to one or more other devices over the network, and wherein the embedded device is configured to perform a task using the one or more devices.

21. The memory medium of claim 14, wherein the GP execution engine is configured to execute in a sandbox, wherein the sandbox comprises a secure execution environment for the GP execution engine, and wherein the GP being executable in a web browser via the GP execution engine comprises the GP being executable in the sandbox via the GP execution engine.

22. The memory medium of claim 21, wherein the sandbox is implemented by a plugin, wherein the GP being executable in the sandbox via the GP execution engine comprises the GP being executable in the plugin via the GP execution engine.

23. The memory medium of claim 14, wherein to execute the GP in a web browser via the GP execution engine, the program instructions are executable to:

display a graphical user interface (GUI) of the GP in the web browser on a display, wherein the GUI is configured to;

display results of the GP execution;

or

receive user input specifying input to the GP.

24. The memory medium of claim 14, wherein the GP is embedded in a web page, wherein the URI references the web page, thereby indicating the GP, and wherein to receive the GP execution engine from the embedded device over the network in response to the URI, the program instructions are executable to:

receive the web page from the embedded device over the network, including the GP and the GP execution engine; and

wherein to execute the GP in a web browser via the GP execution engine, the program instructions are further executable to;

display the web page on a display; and

display results of executing the GP in the web page on the display.

25. The memory medium of claim 14, wherein the memory medium further stores a graphical program editor/execution engine (GPEEE), and wherein the program instructions are further executable to:

send the GPEEE to the client computer over the network in response to the URI, wherein the GPEEE is executable in the web browser to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP in the web browser;

wherein the program instructions are further executable to;

deploy the edited GP to the embedded device, wherein the edited GP is executable to perform updated one or more functions, and wherein the edited GP is downloadable from the embedded device and executable by client computers to;

control the embedded device in response to user input to the GP executing in web browsers of the client computers;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browsers of the client computers.

26. The memory medium of claim 14, wherein the graphical program comprises a graphical data flow program (GDFP), and wherein the GP execution engine comprises a graphical data flow program execution engine.

27. A computer-implemented method, comprising utilizing an embedded device to perform:

the embedded device establishing a network connection with a client computer over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, wherein the embedded device does not require a display, and wherein the embedded device stores;

a graphical program execution engine (GP execution engine) for executing graphical programs; and

a graphical program (GP), wherein the GP is executable to perform one or more functions; and

the embedded device sending the GP and the GP execution engine to the client computer over the network in response to the URI, wherein the GP is executable in a web browser on the client system via the GP execution engine to;

control the embedded device in response to user input to the GP executing in the web browser;

or

monitor activity or performance of the embedded device, including analyzing and displaying output from the embedded device in the web browser.

28. A computer-accessible memory medium that stores program instructions executable by a processor to:

establish a network connection with an embedded device over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, wherein the embedded device stores a graphical program (GP), wherein the embedded device executes the GP to perform one or more functions, wherein the embedded device further stores a graphical program editor/execution engine (GPEEE), and wherein the embedded device does not require a display;

receive the GP and the GPEEE from the embedded device over the network in response to the URI;

execute the GPEEE in the web browser to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP in the web browser; and

wherein the program instructions are further executable to;

deploy the edited GP to the embedded device, wherein the edited GP is executable by the embedded device to perform updated one or more functions.

29. The memory medium of claim 28, wherein the embedded device further comprises an interpreter, and wherein to be executable by the embedded device, the GP is interpretable by the interpreter on the embedded device.

30. The memory medium of claim 28, wherein the embedded device is configured to execute the GP to perform one or more of:

a measurement task;

a control task;

a simulation task;

or

an automation task.

31. The memory medium of claim 28, wherein the GPEEE is configured to execute in a sandbox, and wherein to execute the GPEEE in the web browser, the program instructions are executable to:

execute the GPEEE in the sandbox.

32. The memory medium of claim 28, wherein the sandbox is implemented by a plugin, and wherein to execute the GPEEE in the sandbox, the program instructions are executable to execute the GPEEE in the plugin.

33. The memory medium of claim 28, wherein to execute the GPEEE in the web browser, the program instructions are executable to:

display a graphical user interface (GUI) of the GPEEE in the web browser on a display, wherein the GUI is configured to;

display the GP in the web browser; and

receive user input to edit, compile or interpret, execute, or debug the GP in the web browser.

34. The memory medium of claim 28, wherein the GP is embedded in a web page, wherein the URI references the web page, thereby indicating the GP, and wherein to receive the GPEEE from the embedded device over the network in response to the URI, the program instructions are executable to:

receive the web page from the embedded device over the network, including the GP and the GPEEE; and

wherein to execute the edited GP in a web browser via the GPDE, the program instructions are further executable to;

display the web page on a display; and

display results of executing the GP in the web page on the display.

35. The memory medium of claim 28, wherein the graphical program comprises a graphical data flow program (GDFP), and wherein the GPEEE comprises a graphical data flow program development environment (GDFPDE).

36. The memory medium of claim 28, wherein the program instructions are further executable to:

debug the edited GP from the web browser by monitoring its execution on the embedded device.

37. A computer-implemented method, comprising utilizing a computer to perform:

establishing a network connection with an embedded device over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, wherein the embedded device stores a graphical program (GP), wherein the embedded device executes the GP to perform one or more functions, wherein the embedded device further stores a graphical program editor/execution engine (GPEEE), and wherein the embedded device does not require a display;

receive the GP and the GPEEE from the embedded device over the network in response to the URI;

executing the GPEEE in the web browser to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP in the web browser; and

deploying the edited GP to the embedded device, wherein the edited GP is executable by the embedded device to perform updated one or more functions.

38. A computer-accessible memory medium that stores:

a graphical program editor/execution engine (GPEEE);

a graphical program (GP), wherein the GP is executable by an embedded device to perform one or more functions; and

program instructions executable by the embedded device to;

establish a network connection with a client computer over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, and wherein the embedded device does not require a display;

send the GP and the GPEEE to the client computer over the network in response to the URI, wherein the GPEEE is executable in a web browser on the client system to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP; and

wherein the program instructions are further executable to;

receive the edited GP from the client computer;

execute the edited GP to perform updated one or more functions.

39. The memory medium of claim 38, wherein the embedded device further comprises an interpreter, and wherein to be executable by the embedded device, the GP is interpretable by the interpreter on the embedded device.

40. The memory medium of claim 38, wherein the embedded device is configured to execute the GP to perform one or more of:

a measurement task;

a control task;

a simulation task;

or

an automation task.

41. The memory medium of claim 38, wherein the GPEEE is configured to execute in a sandbox, and wherein the GPEEE being executable in a web browser comprises the GPEEE being executable in the sandbox.

42. The memory medium of claim 41, wherein the sandbox is implemented by a plugin, and wherein the GPEEE being executable in the sandbox comprises the GPEEE being executable in the plugin.

43. The memory medium of claim 38, wherein the GPEEE is executable in the web browser to:

display a graphical user interface (GUI) in the web browser on a display, wherein the GUI is configured to;

display the GP in the web browser; and

receive user input to edit, compile or interpret, execute, or debug the GP in the web browser.

44. The memory medium of claim 38, wherein the GP is embedded in a web page, wherein the URI references the web page, thereby indicating the GP, and wherein to send the GPEEE to the client computer over the network in response to the URI, the program instructions are executable to:

send the web page to the client computer over the network, including the GP and the GPEEE; and

wherein the GPEEE being executable in a web browser comprises the GPEEE being executable to;

edit, compile or interpret, execute, or debug the GP in the web page on the display.

45. The memory medium of claim 38, wherein the graphical program comprises a graphical data flow program (GDFP), and wherein the GPEEE comprises a graphical data flow program development environment (GDFPDE).

46. The memory medium of claim 38, wherein the program instructions are further executable by the embedded device to:

communicate with the GPEEE executing on the client computer to enable debugging of the edited GP during execution of the edited GP on the embedded device.

47. A computer-implemented method, comprising utilizing an embedded device to perform:

the embedded device establishing a network connection with a client computer over a network via a universal resource identifier (URI) associated with the embedded device, wherein the embedded device comprises a web server, and wherein the embedded device does not require a display, and wherein the embedded device stores;

a graphical program editor/execution engine (GPEEE); and

a graphical program (GP), wherein the GP is executable by an embedded device to perform one or more functions;

the embedded device sending the GP and the GPEEE to the client computer over the network in response to the URI, wherein the GPEEE is executable in a web browser on the client system to;

display the GP in the web browser;

receive user input indicating one or more edit operations to be performed on the GP;

edit the GP in the web browser in accordance with the one or more edit operations, thereby generating an edited GP;

display the edited GP source code in the web browser; and

compile or interpret, execute, and debug the edited GP; and

the embedded device receiving the edited GP from the client computer; and

the embedded device executing the edited GP to perform updated one or more functions.