WO2003012642A2

WO2003012642A2 - System and method for communicating with a remote computer

Info

Publication number: WO2003012642A2
Application number: PCT/US2001/040888
Authority: WO
Inventors: David Allison; Osman Ismael; Martin Patterson; Pavani Diwanji
Original assignee: Sun Microsystems, Inc.
Priority date: 2000-06-12
Filing date: 2001-06-08
Publication date: 2003-02-13
Also published as: GB2395031A; GB0300193D0; WO2003012642A3

Abstract

Systems and methods consistent with the present invention allow a remote computer to communicate with a client computer over a standard networking protocol link. Although the client computer does not transmit any instructions along with the transferred data, the remote computer can invoke particular processes using the transferred data. To enable this functionality, the remote computer includes a rules database defining various processes to be performed for each type of data it may receive from the client computer. Accordingly, once the remote computer determines the type of data it received, the remote computer will invoke the particular process defined by the corresponding rule for the determined data type.

Description

SYSTEM AND METHOD FOR COMMUNICATING WITH A REMOTE COMPUTER

BACKGROUND OF THE INVENTION Field of the Invention The present invention relates to systems and methods for communicating with a remote computer and, more particularly, to systems and methods for communicating with a remote computer using a standard networking protocol link. Description of the Related Art Hand-held computing systems, such as a palm-connected organizer, are becoming more and more common each day. To expand the functionality of these hand-held devices, they often include the capability to communicate with a client computer over a dedicated data link. Communication sessions between the hand-held device and the client computer are typically achieved using a file transfer program stored on both computer devices.

The file transfer program controls all data communications between the two devices. These controls include controlling all communications with the file system of the client computer (e.g., Microsoft Windows) and synchronizing all communications transferred over the dedicated data link. Further, the transfer program must format all files and commands transferred between the two computers.

These commands may include instructing the hand-held computer to invoke a certain process using the transferred data. For example, when the hand-held computer functions as a personal messaging device, the client computer may instruct the remote computer to update its calendar or appointment files based on certain transferred calendar data.

Requiring a separate file transfer program creates several drawbacks when using hand-held computers. First, the hand-held computing device can only communicate with a computer already loaded with the proper file transfer program. Thus, the hand-held computer cannot freely communicate with other client computers available to the user. Second, the particular file transfer program may only allow the hand-held computer to communicate with a certain type of computer, such as an IBM PS/2 personal computer.

SUMMARY OF THE INVENTION Systems and methods consistent with the present invention address the problems with the prior art systems by allowing a client computer to communicate with a remote computer over a standard networking protocol link, while the remote computer invokes various processes using data transferred from the client computer.

In accordance with the purposes of the invention as embodied and broadly described herein, a method performed by a computer for communicating with an external processing system comprises the steps of receiving an object from the external processing system without indicating a function to be performed in connection with the object, determining an object type of the received object, and manipulating the received object by performing a function on the object based on the determined object type. Both the foregoing general description and the following detailed description are exemplary and are intended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings provide a further understanding of the invention and, together with the detailed description, explain the principles of the invention. In the drawings:

Fig. 1 illustrates a computer system consistent with the present invention for communicating with a remote computer;

Fig. 2 shows a flow diagram of a method for transmitting data to a remote computer consistent with the present invention;

Fig. 3 a flow diagram of a method for receiving data at a remote computer consistent with the present invention; and

Fig. 4 illustrates a remote computer consistent with the present invention functioning as a personal messaging system. DETAILED DESCRIPTION Overview

Systems and methods consistent with the present invention allow a remote computer to communicate with a client computer over a standard networking protocol link. Although the client computer does not transmit any instructions along with the transferred data, the remote computer can invoke particular processes using the transferred data. To enable this functionality, the remote computer includes a rules database defining various processes to be performed for each type of data it may receive from the client computer. Accordingly, once the remote computer determines the type of data it received, the remote computer will invoke the particular process defined by the corresponding rule for the determined data type. System Organization

Fig. 1 is a block diagram of a computer system 100 consistent with the present invention. As shown in Fig. 1, computer system 100 includes a client computer 110 and a remote computer 120, each communicating over a link 130. Although client computer 110 is preferably a personal computer, other computer systems may be used, such as a network computer, workstation, or mainframe computer. Further, remote computer 120 is preferably part of an embedded data processing system, such as a hand-held personal messaging system. However, remote computer 120 may be part of any data processing system, such as those found in personal digital assistants, personal computers, network computers, workstations, and even mainframe computers.

Client computer 110 further includes a portal 112 located on the desktop of the operating system resident on computer 110. Portal 112 preferably comprises an icon providing a shortcut to a memory location at remote computer 120. Portal 112 is preferably implemented using a mapped network drive. By dragging and dropping an object onto portal 112, a user causes computer 110 to transfer that object over link 130 to the mapped memory location of remote computer 120.

In systems consistent with the invention, link 130 may be either a system bus, a cable connection, a wireless network (e.g, via an infrared link), a local area network, or a wide area network. In all cases, all data transferred over link 130 is performed according to a standard networking protocol, such as the Common Internet Filing System (CIFS) protocol. More information about the CIFS protocol can be found at the web site www.cifs.com. hereby incorporated by reference. Further, while client computer 110 and remote computer 120 communicate with one another under the CIFS protocol, remote computer 120 can invoke certain processes on any transferred data. Thus, from the viewpoint of client computer 110, remote computer 120 behaves the same as any standard peripheral storage device even though it performs various processes on the transferred data.

Remote computer 120 further includes a server 122, a memory 124, and a rules database 126. Server 122 receives the object transferred from client computer 110 over link 130. A CIFS protocol handler (not shown) transmits to computer 110 any response or acknowledgement required by the protocol. Further, in systems consistent with the invention, the CIFS protocol handler is programmed to allow the user to view or otherwise access only certain data stored in memory 124. In this way, a user of client computer 110 cannot access secure objects (e.g. configuration files) stored in memory 124.

Upon receipt of a transferred object, remote computer 120 may use the received object to invoke additional processes according to a predefined set of rules stored in rules database 126. Rules database 126 preferably contains a predefined set of rules defining processes or functions for server 122 to perform based upon the type of object received from client computer 1 10. The number and type of rules stored in rules database 126 will depend upon the particular application for which remote computer 120 is used. An example set, however, is provided below in the section describing a exemplary embodiment for when remote computer 120 functions as a personal messaging system. System Operation

Fig. 2 shows a flow diagram of a method consistent with the present invention for transmitting data to remote computer 120. As shown in Fig. 2, the transmission method begins by the user selecting an object located on computer 110 (step 210). For example, the user may point to a particular object with a mouse (not shown) and then left-click on the object's icon to select it. The user then uses the mouse to drag the selected object to portal 112 (step 220). Once the icon of the selected object is superimposed over portal 1 12, the user drops the object into portal 112 by releasing the left button of the mouse (step 230).

Dropping the selected object onto portal 112 causes client computer 1 10 to transfer the object to remote computer 120 over link 130. In systems consistent with the invention, client computer 110 does not require any special functionality to transfer the object to remote computer 120. Client computer 110 simply transfers the object to remote computer 120 the same as it would transfer the object to any memory location that is peripheral to computer 110. In following, computer 110 transfers the selected object to remote computer 120 according to a standard protocol, preferably the CIFS protocol.

Fig. 3 shows a flow diagram of a method consistent with the present invention for receiving an object at remote computer 120. As shown in Fig. 2, the receiving method begins by receiving the object (step 310) and transmitting to client computer 110 any response required by the transfer protocol of link 130 (step 320). As described above, server 122 preferably includes a CIFS protocol handler for determining and invoking any required responses to computer 110 during the communication process.

Remote computer 120 then determines an object type of the received object (step 330). The determined object type may relate, for example, to the type of information contained in the object or the type of software application that created the object. Accordingly, in systems consistent with the invention, computer 120 preferably determines the object's type based on the contents of the object or based on the object's file extension.

Remote computer 120 then performs a particular process using the received object based on the determined object type (step 340). To this end, server 122 searches rules database 126 to locate a particular rule associated with the determined object type. Each rule stored in database 126 defines, for each object type, a particular process that computer 120 will perform. For example, given the object type, remote computer 120 may instantiate the object, publish the object by making it available to a web browser, or store the object in a designated file directory. In this way, remote computer 120 invokes particular processes on the transferred data without requiring specialized instructions or commands from client computer 110. Exemplary Embodiment

For purposes of illustration, provided below is an exemplary system consistent with the present invention with remote computer 120 functioning as a personal messaging system. Fig. 4 illustrates a block diagram of a remote computer 400 that can function as a personal messaging system. As shown in Fig. 4, remote computer 400 includes a server 410, a memory 420, a rules database 430, an http server 440, a facsimile database 450, a calendar database 460, and a voice-mail database 470. A user may send message data to remote computer 400 from client computer

110. Using rules database 430, remote computer 400 may then invoke certain processes on the transferred message data depending upon the type of information received. For example, remote computer 400 may automatically organize in one-hand held device a user's voice mail, electronic mail, facsimile transmissions, and personal appointments. Moreover, the user can simply transfer such information to remote computer 400 from any client computer without the need for a specialized file transfer program. Upon receipt, remote computer 400 automatically processes the information to maintain a current and organized personal messaging system.

Described below are examples of rules stored in rules database 430 for various object types.

1. HTML File - Define a rule instructing server 410 to store the file in a location accessible by http server 440. For example, a user drags an HTML object to portal 112, causing client computer 110 to transmit the object to remote computer 400 over link 130. Sever 410 receives the HTML object and, according to the appropriate rule in rule database 430 for HTML files, server 410 stores the HTML object in a particular location accessible by http server 440. In this way, remote computer 400 publishes the HTML object, such that a user of any client computer having a web browser could then access the published file over a network.

2. Http Link - Define a rule instructing http server 440 to access the identified network location and copy the contents of the file to memory 420. The user could then view the copied web page through a display on remote computer 400. 3. Facsimile Data File - Define a rule instructing server 410 to store the file in facsimile database 450. The user could then access the facsimile contained in the file through a display (not shown) on remote computer 400.

4. Calendar Data File - Define a rule instructing server 410 to store the file in calendar database 460. By doing so, a calendar program running on server 410 may then update the user's schedule according to the stored calendar data file.

5. Voice Data File - Define a rule instructing server 410 to store the file in voice mail database 470. The user could then access the voice mail message contained in the file through a speaker (not shown) on remote computer 400. 6. Configuration Update File - Define a rule instructing server 410 to perform a configuration operation on remote computer 400. For example, the rule may instruct server 410 to reboot remote computer 400 to install the configuration file. Conclusion Systems and methods consistent with the present invention allow communication with a remote computer over a standard networking protocol link. The foregoing description of preferred embodiments of the present invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, the described implementation includes software but the present invention may be implemented as a combination of hardware and software or in hardware alone. Further, the invention may be implemented with both object-oriented and non-object- oriented programming systems. Although aspects of the present invention are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, an Internet connection, or other forms of RAM or ROM. The scope of the invention is defined by the claims and their equivalents.

Claims

WHAT IS CLAIMED IS:

1. A method for communicating with an external processing system, comprising the steps performed by a computer of: receiving an object from the external processing system without an indication of a function to be performed in connection with the object; determining an object type of the received object; and manipulating the received object by performing a function on the object based on the determined object type.

2. The method of claim 1 , wherein the determining step further includes the substep of: determining the object type based on contents of the object.

3. The method of claim 1, wherein the determining step further includes the substep of: determining the object type based on a file extension of the object.

4. The method of claim 1, wherein the function includes one of the following types of functions: instantiating the object, publishing the object, and storing the object.

5. The method of claim 1 , wherein the receiving step further includes the following substep: receiving an object according to the CIFS protocol.

6. The method of claim 1 , further including the step of: transmitting a response to the external processing system according to the

CIFS protocol.

7. A computer for communicating with an external processing system, the computer comprising: a memory having program instructions; and a processor, responsive to the programming instructions, configured to: receive an object from the external processing system without an indication of a function to be performed in connection with the object; determine an object type of the received object; and manipulate the received object by performing a function on the object based on the determined object type.

8. The computer of claim 7, wherein the processor is further configured to: determine the object type based on contents of the object.

9. The computer of claim 7, wherein the processor is further configured to: determine the object type based on a file extension of the object.

10. The computer of claim 7, wherein the processor is further configured to: perform one of the following types of functions: instantiating the object, publishing the object, and storing the object.

1 1. The computer of claim 7, wherein the processor is further configured to: receive an object according to the CIFS protocol.

12. The computer of claim 7, wherein the processor is further configured to: transmit a response to the external processing system according to the CIFS protocol.

13. A computer-readable medium containing instructions for controlling a data processing system to perform a method for communicating with an external processing system, the method comprising the steps of: receiving an object from the external processing system without an indication of a function to be performed in connection with the object; determining an object type of the received object; and manipulating the received object by performing a function on the object based on the determined object type.

14. The method of claim 13, wherein the determining step further includes the substep of: determining the object type based on contents of the object.

15. The method of claim 13, wherein the determining step further includes the substep of: determining the object type based on a file extension of the object.

16. The method of claim 13 , wherein the function includes one of the following types of functions: instantiating the object, publishing the object, and storing the object.

17. The method of claim 13, wherein the receiving step further includes the following substep: receiving an object according to the CIFS protocol.

18. The method of claim 13, further including the step of: transmitting a response to the external processing system according to the

CIFS protocol.

19. A method for communicating with an external processing system, comprising the steps performed by a computer of: receiving an object from the external processing system without an indication of a function to be performed in connection with the object; determining whether the received object corresponds to one of the following object types: html data type, http data type, facsimile data type, calendar data type, and voice data type; and manipulating the received object by performing a function on the object based on the determined object type, wherein the manipulating step further includes the substep of: storing the received object in a particular database corresponding to the determined object type.

20. A computer for communicating with an external processing system, the computer comprising: a memory having program instructions; and a processor, responsive to the programming instructions, configured to: receive an object from the external processing system without an indication of a function to be performed in connection with the object; determine whether the received object corresponds to one of the following object types: html data type, http data type, facsimile data type, calendar data type, and voice data type; and manipulate the received object by performing a function on the object based on the determined object type, wherein the processor is further configured to: store the received object in a particular database corresponding to the determined object type.

21. A computer-readable medium containing instructions for controlling a data processing system to perform a method for communicating with an external processing system, the method comprising the steps of: receiving an object from the external processing system without an indication of a function to be performed in connection with the object; determining whether the received object corresponds to one of the following object types: html data type, http data type, facsimile data type, calendar data type, and voice data type; and manipulating the received object by performing a function on the object based on the determined object type, wherein the manipulating step further includes the substep of: storing the received object in a particular database corresponding to the determined object type.