US 6,370,570 B1Grant
Method and apparatus for making a hypermedium interactive
Issue Date:2002-04-09
•22 Claims
•2 Drawing Sheets
Abstract
A system and method of making a hypermedium page interactive. In one embodiment the system includes a hyperlink on the hypermedium page displayed on a client node; a hyperlink configuration file (corresponding to the hyperlink on the client node) located on a network server node; and a client agent located on the client node. In response to a user selecting the hyperlink on the hypermedium page, the client agent establishes a communications link from the client agent to an application execution server agent on an application server using the information located in the configuration file obtained from the network server node. In response to the creation of the communications link between the application execution server agent and the client agent, the application executes on the application execution server and the user is capable of interactively using the application running on the application execution node from the client node. Data input and display occurs at the client node under the control of the client agent.
Metadata
Assignee
- Citrix Systems, Inc.
Inventors
- Jeff Muir
- Andrew L. Stergiades
Application Information
Application Number:US 09/247,220
Filing Date:1999-02-10
Priority Date:1995-11-13
Art Unit:7
Classifications
IPC:
G06F 1516
Field of Search:
709217709218709219709203709201709229707501707513707 10345335345333345346711132
Patent Drawings (2 sheets)
Description
Related Application
[0002] This application is a continuation of U.S. patent application “Method and Apparatus for Making a Hypenmedium Interactive,” Ser. No. 08/556,623 filed Nov. 13, 1995.
Field of the Invention
[0003] The invention relates generally to the field of computer communications and more specifically to the field of remote application processing.
Background of the Invention
[0004] A hypermedium is a graphical display which contains a series of graphic and textual images which are referred to as hyperlinks. Each hyperlink typically corresponds to additional information which is available to a user of the hypermedium. For example a hypermedium display might be an encyclopedic article about flight. If the graphical display of the article includes a picture of a rocket, and if the user is able to obtain information about the engine of the rocket by selecting (typically by using a pointing device referred to as a computer mouse) a portion of the display showing the engine, the portion of the picture containing the rocket engine is referred to as a hyperlink. That is, the portion of the picture containing the engine is a link to information about the engine. The activation of a hyperlink causes the hypermedium to request a data file of the desired information from the program actually controlling the hypermedium.
[0005] When a hypermedium is used in conjunction with a network, for example the world wide web or the internet a user on a client node on the network first accesses what is termed a home page or a web page. This home page or web page is obtained from another node on the net, termed a network server, and is displayed on the client node by a program termed a network browser or web browser. In such a case, when the user selects the hyperlink (in the previous example, the portion of the display showing the rocket engine) a request is made to the network browser for the data file containing the requested information. The network browser on the user's node establishes communication with the network node, the data server, having data corresponding to the requested hyperlink. In this case the node having information about the rocket engine contains the information required by the hyperlink.
[0006] Although hypermedium has been used to transfer information to a user in the manner just discussed, it is desirable to be able to use a hypermedium display to interactively execute applications such as database programs located on another computer, an application execution server, on the network. The present invention relates to a method and apparatus to accomplish this task.
Summary of the Invention
[0007] The invention relates to a system of making a hypermedium page interactive to thereby permit an application to be executed on one node and the results displayed and data entered on another node. In one embodiment the system includes a client node, a network server node and an application execution server node interconnected by a communication link. A hyperlink on the hypermedium page is displayed on the client node and a hyperlink configuration file (corresponding to the hyperlink on the client node) is located on the network server node. In one embodiment, a client agent is located on the client node and a server agent is located on the application execution server node. A communication link is created by the client agent between the client agent on the client node and the server agent on the application execution server node in response to data in the hyperlink configuration file. The system also includes an application on the application execution server node which executed on the application execution server node in response to the communications link between the client agent and the server agent. The application running on the application execution node then communicates with the client agent through the server agent. The client agent on the client node is responsible for receiving data input from the user and transferring the data to the application on the application execution node and receiving data from the application on the application execution node and displaying data output to the user on the client node.
[0008] The invention also relates to a method of making a hypermedium page interactive. The method includes the steps of selecting a hyperlink on the hypermedium page displayed on a client node; retrieving (from a server node to the client node) a hyperlink configuration file corresponding to the hyperlink and starting a client agent on the client node. The method further includes the steps of creating a communications link between a server agent on an application execution server and the client agent; starting the application on the application execution server in response to the connection; communicating data between the client agent on the client node and application on the application execution node; and managing the display and input of data on the client node.
Brief Description of the Drawings
[0009] Other features and benefits of the invention can be more clearly understood with reference to the specification and the accompanying drawings in which:
[0010] FIG. 1 is a block diagram of an embodiment of the system of the invention; and
[0011] FIG. 2 is a flow chart of the operation of system of the invention shown in FIG. 1.
Detailed Description of the Invention
[0012] Referring to FIG. 1, and in brief overview, an embodiment of an interactive hypermedium system of the invention includes a client node 10, a network server node 18 and an application execution server node 24 interconnected by a communications link 32, herein referred to without any loss of generality as a network or web. Although only one client node 10, network server node 18 and application execution server node 24, are shown in FIG. 1 for clarity, an actual network may include many such nodes. Alternatively, the services provided by each of the nodes listed may be combined in one or more nodes. For example, the application execution server and the network server may in fact be the same node. In the extreme it is possible for all functions to be performed by the same node, although such would not typically be the case. In addition, although only one application 36 is shown on the application execution server 24, in reality, an application execution server node 24 typically includes many applications 36. Each node on the network or web 32 includes a processor, which may vary significantly from other processors on the web 32 in terms of computing power and associated hardware. Further, the applications 36 available for execution on each node may be different.
[0013] A user on a client node wishing to run the application program 36 which is located on the application execution server 24 on the web 32 does so through a graphical user interface 40, which is herein referred to without any loss of generality as a hypermedium, located on the client node 10. The graphical interface is displayed on a graphical display device 42. Data is entered by the users through a mouse 46 and a keyboard 50 located on the client node 10. The graphical display or page 44 which the user first views on the hypermedium 40 is referred to herein without any loss of generality as the home page or web page of the application 36. A page 44 or home page of the hypermedium 40 includes a graphic link 48 or textual link 56 herein referred to without any loss of generality as a hyperlink. The web page is displayed by a process 64 referred to herein without any loss of generality as a network browser 64 executing on the client node 10.
[0014] The network browser 64 obtains the first page or web page 44 from a network server node 18 and displays the web page 44 on the hypermedium 40 for the user to view on the graphical display device 42. When the user selects an application program 36 to execute (by selecting a graphical 48 or textual 56 hyperlink using the mouse 46 or keyboard 50) the network browser 64 obtains a network configuration file 68 corresponding to the selected application 36 from a predetermined network server 18 and starts a client agent 72 which will communicate with the selected application 36. This will be discussed in more detail below.
[0015] The client agent 72 reads the configuration file 68 and establishes a communications link to a server agent 80 on the application execution server 24 specified by the configuration file 68. In one embodiment, the configuration file 68 includes the name of the application and the node location of the application 36 corresponding to the hyperlink 48, 56. The configuration file may also contain optional information such as authentication or authorized user information. Server agent 80 performs the operations necessary (such as authentication) to permit the client agent 72 access to the application 36, and once access is permitted, starts the application 36 requested by the user. Once the application 36 is executing on the application execution server, the application 36 communicates through the server agent 80 directly with the client agent 72 without intervention by the network browser 64. The client agent 72 is then responsible for receiving data from the user through the mouse 46 and keyboard 50 and transmitting it to the application program 36 on the application execution server 24. Similarly, the client agent 72 is responsible for receiving data from the application 36 on the application execution server 24 and displaying the data in an application display window 74 on the graphical display device 42 on the client node 10. It should be noted that the application display window 74 may be located within the boundaries or outside the boundaries of the hypermedium 40. When the application 36 is completed the server agent 80 instructs the client agent 72 to disconnect the communication link 32 between the client agent 72 and the server agent 80 and the server agent waits for the next connection.
[0016] FIG. 2 depicts the operation of the system in more detail. Initially, the client agent 72 is registered (Step 1) with the network browser 64 of the client node 10 and an entry is made in the network browser's registration file 88 (FIG. 1). This entry permits the network browser 64 to start the client agent 72 whenever a given file type is requested by the hyperlink 48, 56 of the hypermedium 40. In this case the client agent 72 is designed to permit a user on the client node 10 to execute and interact with a remote application 36 on an application execution server node 24. The client agent 72 would be registered with the network browser 64 such that whenever a hyperlink 48, 56 requested the given file type (for example RMT for remote execution) from network browser 64, the network browser 64 would start the client agent 72 which would permit remote execution and interaction with an application 36 resident on an application execution server 24. The invoking of the client agent 72 is discussed in more detail below.
[0017] Next, when a user wishes to execute an application from a hypermedium environment, for example a database program, the hypermedium 40 is displayed in a manner that is well known to those skilled in the art. When the user selects a hyperlink 48, 56 on the page 44 of the hypermedium (Step 2) by using the mouse 46 or keyboard 50 on the client node 10, a request is made to the network browser 64 for the corresponding data file (Step 3). In this example, the filetype (.RMT) is requested.
[0018] The network browser 64 obtains the corresponding configuration file 68 from the network server 18 which is specified in the file request made by the hyperlink 48, 56 to the network browser 64 (Step 4). The network browser 64 then compares the obtained configuration file 68 with the registration file 88 of client agent names which it maintains (Step 5). If the client agent 72 specified by the configuration file 68 is found in the registration file 88, the client agent 72 is started (Step 6).
[0019] The invoked client agent 72 reads the configuration file 68 (Step 7), and based upon the information in the configuration file 68, begins to establish a communication link with the server agent 80 on the application execution server 24 (Step 8), in this case the sales database application execution server (generally 24).
[0020] Considering the process of beginning the communications link of step 8 (FIG. 2) in more detail, communication begins with the server agent 80 monitoring communication activity on the network 32. At this point, no protocol assumptions are made by the server agent 80 beyond those necessary for the transport layer. Similarly, the client agent 72 also makes no assumption of the communications protocol beyond that required by the transport layer. Once the server agent 80 determines that a client agent 72 is attempting to communicate with it, the server agent 80 transmits a message to the client agent 72 indicating that service is available.
[0021] Once the client agent 72 determines that service is available on the application execution server node 24, the client agent 72 transmits a message to the server agent 80 indicating that it is ready to proceed with the communication protocol. Once the server agent 80 has responded that it to is ready to continue the communication protocol, the client agent 72 enables the protocol necessary for it to run the application 36. In response to the message from the client agent 72, the server agent 80 also enables the required protocol. The server agent 80 then transmits a message using the required protocol indicating that the client agent's request has been received and accepted.
[0022] In response the client agent 72 and the server agent 80 exchange a set of messages which negotiate the parameters under which communications will occur. Once negotiations are complete, the client agent 72 and the server agent 80 are able to communicate as necessary for the application 36 to be run by the user.
[0023] Once the communications protocol has been established and the server agent 80 has authenticated the client agent 72 (Step 9) (for example determining that the user has permission to read and write to the database) the application 36 (Step 10) is run on the application execution server 24. At this point application 36 running on the application execution server 24 is communicating via the server agent 80 with the client agent 72 on the client node 10. The client agent 72 is now responsible for transmitting data input by the user using the mouse 46 and keyboard 50 to the application 36 running on the application execution server 24. Further, the client agent 72 is responsible for receiving data for display from the application 36 and displaying that data in the application window 74 on the graphical display device 42 of the client node 10.
[0024] It should be noted that the underlying presentation protocol which passes data to a transport layer such as TCP/IP must be capable of transferring graphical information. Examples of such protocols which may be used for interactive hypermedia communication include public domain X-WINDOWS protocol and the proprietary ICA protocol of Citrix Systems Inc.
[0025] Thus the above described system permits a user on a client node 10, which may have very limited resources, to start and interact with an application program 36 located on another application execution server node 24. The application 36 then runs on the application execution server node 24 and the data is input and the results displayed on the client node 10.
[0026] These and other examples of the concept of the invention illustrated above are intended by way of example and the actual scope of the invention is to be determined solely from the following claims.
Claims
What is claimed is:
1. A method of making a hypermedium page interactive, the hypermedium page displayed by a network browser, comprising the steps of:
a) activating a hyperlink on the hypermedium page, the hyperlink corresponding to an application program;
b) accessing a hyperlink configuration file associated with the hyperlink, the hyperlink configuration file identifying a client agent and a network address for a server storing the application program;
c) starting the client agent identified in the hyperlink configuration file to obtain the network address from the hyperlink; configuration file;
d) establishing communications by the client agent with a server agent located on the server associated with the network address obtained from the hyperlink configuration file; and
e) executing the application program on the server in response to a signal from the server agent, the server agent providing the signal in response to a communication from the client agent.
2. The method of claim 1, wherein step d) is performed without intervention by the network browser.
3. The method of claim 1, wherein step e) is performed without intervention by the network browser.
4. The method of claim 1, wherein step c) further comprises starting the client agent by the network browser upon a successful match of an entry in the hyperlink configuration file with an identifier associated with the client agent in a registration file accessible by the network browser.
5. The method of claim 1, wherein the client agent operates independently of the network browser after the network browser starts the client agent.
6. The method of claim 1 further comprising f) employing a presentation protocol for communication over the communication link.
7. The method of claim 1 further comprising:
f) transmitting data by the server agent to the client agent and the application program without intervention by the network browser; and
g) displaying, without intervention by the network browser, data received by the client agent from the server agent.
8. The method of claim 1 further comprising f) registering the client agent with the network browser.
9. A method of remotely launching an application program, the method comprising:
activating a hyperlink displayed by the network browser, the hyperlink corresponding to the application program;
accessing, in response to the activation of the hyperlink, a hyperlink configuration file, the hyperlink configuration file identifying a client agent and a network location both associated with the application program; and
executing the client agent to obtain the network location from the hyperlink configuration file and to issue a signal to the network location to launch the application program.
10. The method of claim 9 further comprising establishing communications by the client agent with a server agent located at the network location identified in the hyperlink configuration file, wherein the client agent establishes the communications without intervention by the network browser.
11. The method of claim 10, wherein the executing step further comprises transmitting the signal from the client agent to the server agent, the server agent responding by starting the application program.
12. The method of claim 10 further comprising establishing, by the client agent without intervention by the network browser, communications with the application program using die electronic address obtained from the hyperlink configuration file.
13. The method of claim 12 further comprising employing a presentation protocol for communication over the communication link.
14. The method of claim 9, wherein the accessing step further comprises the step of starting the client agent by the network browser.
15. The method of claim 9 further comprising transmitting data representative of user inputs from the client agent to the application program without intervention by the network browser.
16. The method of claim 9 further comprising registering the client agent with the network browser.
17. A method of remotely interactiong with an application program on a network server, the method comprising:
activating a hyperlink displayed by a network browser;
accessing a hyperlink configuration file associated with the hyperlink, the hyperlink configuration file including an electronic address associated with the application program, wherein the electronic address is accessible by a client agent; and
executing the client agent to obtain the electronic address from the hyperlink configuration file and to issue a signal to the electronic address to launch the application program on the network server.
18. The method of claim 17 further comprising:
establishing a communication link between the client agent and the application program without intervention by the network browser; and
displaying, without intervention by the network browser, data received by the client agent from the application program executing on the network server.
19. The method of claim 18 further comprising employing a presentation protocol for communication over the communication link.
20. The method of claim 17 further comprising establishing, by the client agent without intervention by the network browser, communications with the application program using the electronic address obtained from the hyperlink configuration file.
21. The method of claim 17, wherein the executing step further comprises establishing communications with the application program by the client agent, the client agent transmitting signals to a server agent located at the electronic address in the hyperlink configuration file, the server agent responding to the received signals by launching and communicating with the application program.
22. The method of claim 17 further comprising registering the client agent with the network browser.
Patent Citations (75)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4499499(A) | 1985-02-01 | Brickman et al. | Applicant |
| US4887204(A) | 1989-12-01 | Johnson et al. | Applicant |
| US4937784(A) | 1990-06-01 | Masai et al. | Applicant |
| US5014221(A) | 1991-05-01 | Mogul | Applicant |
| US5031089(A) | 1991-07-01 | Liu et al. | Applicant |
| US5175852(A) | 1992-12-01 | Johnson et al. | Applicant |
| US5202971(A) | 1993-04-01 | Henson et al. | Applicant |
| US5233701(A) | 1993-08-01 | Nakata | Applicant |
| US5249290(A) | 1993-09-01 | Heizer | Applicant |
| US5297249(A) | 1994-03-01 | Bernstein et al. | Examiner |
| US5325527(A) | 1994-06-01 | Cwikowski et al. | Applicant |
| US5329619(A) | 1994-07-01 | Page et al. | Applicant |
| US5341477(A) | 1994-08-01 | Pitkin et al. | Applicant |
| US5341478(A) | 1994-08-01 | Travis, Jr. et al. | Applicant |
| US5367688(A) | 1994-11-01 | Croll | Applicant |
| US5414457(A) | 1995-05-01 | Kadowaki et al. | Applicant |
| US5473599(A) | 1995-12-01 | Li et al. | Applicant |
| US5485460(A) | 1996-01-01 | Schrier et al. | Applicant |
| US5499343(A) | 1996-03-01 | Pettus | Applicant |
| US5515508(A) | 1996-05-01 | Pettus et al. | Applicant |
| US5526492(A) | 1996-06-01 | Ishida | Applicant |
| US5530852(A) | 1996-06-01 | Meske, Jr. et al. | Applicant |
| US5537546(A) | 1996-07-01 | Sauter | Applicant |
| US5548726(A) | 1996-08-01 | Pettus | Applicant |
| US5553242(A) | 1996-09-01 | Russell et al. | Applicant |
| US5557732(A) | 1996-09-01 | Thompson | Applicant |
| US5557748(A) | 1996-09-01 | Norris | Applicant |
| US5561769(A) | 1996-10-01 | Kumar et al. | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5572674(A) | 1996-11-01 | Ernst | Applicant |
| US5579469(A) | 1996-11-01 | Pike | Applicant |
| US5583992(A) | 1996-12-01 | Kudo | Applicant |
| US5596745(A) | 1997-01-01 | Lai et al. | Applicant |
| US5606493(A) | 1997-02-01 | Duscher et al. | Applicant |
| US5623656(A) | 1997-04-01 | Lyons | Applicant |
| US5644720(A) | 1997-07-01 | Boll et al. | Applicant |
| US5657390(A) | 1997-08-01 | Elgamal et al. | Applicant |
| US5680549(A) | 1997-10-01 | Raynak et al. | Applicant |
| US5701451(A) | 1997-12-01 | Rogers et al. | Applicant |
| US5706437(A) | 1998-01-01 | Kirchner et al. | Applicant |
| US5710918(A) | 1998-01-01 | Lagarde et al. | Applicant |
| US5721876(A) | 1998-02-01 | Yu et al. | Applicant |
| US5734865(A) | 1998-03-01 | Yu | Applicant |
| US5754830(A) | 1998-05-01 | Butts et al. | Applicant |
| US5761507(A) | 1998-06-01 | Govett | Applicant |
| US5761656(A) | 1998-06-01 | Ben-Shachar | Examiner |
| US5764908(A) | 1998-06-01 | Shoji et al. | Applicant |
| US5764915(A) | 1998-06-01 | Heimsoth et al. | Applicant |
| US5802258(A) | 1998-09-01 | Chen | Applicant |
| US5802306(A) | 1998-09-01 | Hunt | Applicant |
| US5812784(A) | 1998-09-01 | Watson et al. | Applicant |
| US5826027(A) | 1998-10-01 | Pedersen et al. | Applicant |
| US5828840(A) | 1998-10-01 | Cowan et al. | Applicant |
| US5838906(A) | 1998-11-01 | Doyle et al. | Applicant |
| US5838910(A) | 1998-11-01 | Domenikos et al. | Applicant |
| US5838916(A) | 1998-11-01 | Domenikos et al. | Applicant |
| US5872973(A) | 1999-02-01 | Mitchell et al. | Examiner |
| US5938733(A) | 1999-08-01 | Heimsoth et al. | Applicant |
| US5941949(A) | 1999-08-01 | Pedersen | Applicant |
| US5941988(A) | 1999-08-01 | Bhagwat et al. | Applicant |
| US5951694(A) | 1999-09-01 | Choquier et al. | Applicant |
| US5961586(A) | 1999-10-01 | Pedersen | Applicant |
| US5978848(A) | 1999-11-01 | Maddalozzo, Jr. et al. | Applicant |
| US6088515(A) | 2000-07-01 | Muir et al. | Examiner |
| US6108715(A) | 2000-08-01 | Leach et al. | Examiner |
| US6157944(A) | 2000-12-01 | Pedersen | Applicant |
| EP381645 | 1990-08-01 | Applicant | |
| EP384339 | 1990-08-01 | Applicant | |
| EP483576 | 1992-05-01 | Applicant | |
| EP540151 | 1993-05-01 | Applicant | |
| EP648038 | 1995-04-01 | Applicant | |
| EP732834 | 1996-09-01 | Applicant | |
| JP6332782 | 1994-12-01 | Applicant | |
| WO98/52320 | 1998-11-01 | Applicant | |
| WO98/52344 | 1998-11-01 | Applicant |
Non-Patent Literature (19)
- Branwyn, Gareth “MOSAIC: Quick Tour for Windows”, Ventana Press, pp. 5-7, 57, 124-126, 61-64, 91-104, and 124-126, 1994.Applicant
- T. Tessier; Dr. Dobb's Journal; “Using Javascript to Create; Interactive Web Pages A Cross-Platform Object Scripting Language”21, No. 3:84-97 (Mar. 1, 1996).Applicant
- A. Singleton; Byte; “Wired On The Web”; 21 No. 1:77-78, 80 (Jan. 1, 1996).Applicant
- P. Davis; Database; “An Interactive Hypermedia Map Viewer”; 18, No. 2:65-67 (Apr./May, 1995).Applicant
- J.M. Chu et al.; Behavior Research Methods, Instruments&Computers; “Creating a Hypertext Markup Language Documents for an Information Server”; 27, No. 2:200-205 (Jan. 1, 1995).Applicant
- S. Putz, “Interactive information services using world-wide web hypertext,” Computer Networks &ISDN Systems, Elsevier Science B.V., vol. 27, p. 273-280, 1994.Applicant
- A. Hoff, “Java and Internet Programming,” Dr. Dobb's Journal, pp. 56, 58, 60-61 and 101-102, Aug. 1995.Applicant
- Jellinek, Herb. “The Animator Applet (1.0.2)-example 1,” 199.185.96.71/java/Animator/example1.html, printed Jun. 1, 1999.Applicant
- Windows NT Networking Guide: Microsoft Windows NT Resource Kit, pp. 79-87, (1995).Applicant
- Schemers, III, R.J. “Ibnamed: a load balancing name server written in Perl—Update,” www-leland.stanford.edu/˜docs/ibnamed/ibnamed.html, pp. 1-5, (Sep. 17, 1995).Applicant
- van Hoff, Arthur. “Java and Internet Programming,” Dr. Dobb's Journal, pp. 56, 58, 60-61, 101-102, (Aug., 1995).Applicant
- Adler, Richard M. “Distributed Coordination Models for Client/Server Computing,” Computer Magazine, pp. 14-22, (Apr., 1995).Applicant
- Putz, Steve. “Interactive Information Services Using Word-Wide Web Hypertext, ” Computer Networks and ISDN Systems, Elsevier Science B.V., vol. 27, pp. 273-280, (1994).Applicant
- Droms, R. “Dynamic Host Configuration Protocol,” Network Working Group Request for Comments: 1541, pp. 1-39, (Oct., 1993).Applicant
- “Allocation of Equivalent Communication Buffer Sizes in SQLJRA Remote Protocol,” IBM Technical Disclosure Bulletin, vol. 36, No. 1, pp. 29-31, (Jan., 1993).Applicant
- “OS/2 EE Database manager SQLJRA Remote Protocol,” IBM Technical Disclosure Bulletin, vol. 36, No. 1, pp. 33-36, (Jan., 1993).Applicant
- Tanenbaum, Andrew S. “Networking in Unix,” Computer Networks, pp. 434-435, (1989).Applicant
- Holtzman, Jeff. “Merge 386: Run Unix and DOS together on an 80386,” Byte, pp. cover, 207-208, 211-212, (Dec., 1988).Applicant
- Mann, Bruce E. et al. “Terminal Servers on Ethernet Local Area Networks,” Digital Technical Journal, No. 3, pp. 73-87, (Sep., 1986).Applicant