US 7,185,014 B1Grant
Retrieving data from a server
Issue Date:2007-02-27
•74 Claims
•4 Drawing Sheets
Abstract
A system includes a server and a controller embedded in a device. Both the server and the embedded controller are capable of communicating over a computer network. The embedded controller sends a command to the server over the computer network that identifies an instance of the device. In response, the server identifies the instance of the device based on the command, retrieves data that is specific to the instance of the device, and sends the data to the embedded controller over the computer network.
Metadata
Assignee
- Axeda Corporation
Inventor
- James R. Hansen
Application Information
Application Number:US 09/667,737
Filing Date:2000-09-22
Priority Date:2000-09-22
Art Unit:2165
Classifications
IPC:
G06F17/30
Patent Drawings (4 sheets)
Description
BACKGROUND
[0001] This invention relates to a controller embedded in a device (an “embedded controller”) that retrieves data from a remote server for a specific instance of the device.
[0002] A device may contain an embedded controller, such as a microprocessor, to monitor and control its operation. Any type of device may have an embedded controller, including, but not limited to, home appliances, such as washing machines, dishwashers, and televisions, and manufacturing equipment, such as robotics, conveyors and motors.
[0003] Embedded controllers, also referred to as “embedded devices”, are often connected to an internal network, such as a local area network (LAN), with an interface to the Internet. Other devices on the internal network may communicate with the embedded controllers over the internal network. However, the embedded controllers are not generally addressable from the Internet.
SUMMARY
[0004] In general, in one aspect, the invention is directed to a controller embedded in a device for retrieving data from a server. The controller sends a command to the server that identifies an instance of the device and receives, from the server and in response to command, data that is specific to the instance of the device.
[0005] This aspect of the invention may include one or more of the following. The command may include an operational parameter for the device and the data may include an updated value for the operational parameter. The command may include plural operational parameters for the device and the data may include updated values that differ from current values of the operational parameters.
[0006] The data may include a list of operational parameters. In this case, the embedded controller sends a second command to the server, which includes operational parameters from the list, and receives, from the server and in response to second command, updated values of one or more of the operational parameters included in the second command. The data may include a list of operations to be performed by the controller. In this case, the embedded controller parses the operations from the list and performs the operations from the list.
[0007] The data may include a configuration file for the device. The command may identify the instance of the device by a device type and/or one or more of a serial number and a universal unique identifier. The embedded controller may send the command to the server periodically. The server may run the Hypertext Transfer Protocol and the command may contain Extensible Markup Language code.
[0008] In general, in another aspect, the invention is directed to a server for sending data over a network to a controller embedded in a device. The server receives a command from the embedded controller, identifies an instance of the device from information in the command, retrieves data that is specific to the instance of the device, and sends the data to the embedded controller.
[0009] This aspect of the invention may include one or more of the following features. The command may include a device type and/or one or more of a serial number and a universal unique identifier. The instance of the device may be identified based on the device type and/or one or more of the serial number and the universal unique identifier. The server may parse the device type and one or more of the serial number and universal unique identifier from the command prior to identifying the instance of the device.
[0010] The command may include an operational parameter for the device. The data may include an updated value of the operational parameter. The data may include a list of operational parameters for the device. The server receives a second command from the embedded controller, which includes an operational parameter from the list of operational parameters, obtains an updated value of the operational parameter, and sends the updated value of the operational parameter to the embedded controller.
[0011] The data may include a list of operations to be performed by the embedded controller. The data may include a configuration file for the device. The server may receive the data specific to the instance of the device and store the data in memory, from which it is retrieved. The data specific to the instance of the device may be received via a Web page generated by the server. The server may run the Hypertext Transfer Protocol and the command may contain Extensible Markup Language code.
[0012] In general, in another aspect, the invention is directed to a system that includes a controller embedded in a device that is capable of communicating over a computer network, and a server that is capable of communicating over the computer network. The embedded controller sends a command to the server over the computer network that identifies an instance of the device and, in response, the server (i) identifies the instance of the device based on the command, (ii) retrieves data that is specific to the instance of the device, and (iii) sends the data to the embedded controller over the computer network.
[0013] This aspect of the invention may include one or more of the following features. The embedded controller is not remotely-addressable from the computer network. The computer network is the Internet. The server runs the Hypertext Transfer Protocol and the command may contain Extensible Markup Language code.
[0014] Other features and advantages of the invention will become apparent from the following description, including the claims and drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] FIG. 1 is a block diagram of a network containing a server and a device having an embedded controller;
[0016] FIG. 2 is a flowchart showing a process by which the embedded controller retrieves data for the device from the server; and
[0017] FIG. 3 is a flowchart showing an alternative process by which the embedded controller retrieves data for the device from the server.
DESCRIPTION
[0018] FIG. 1 shows a network 10. Network 10 includes a device 11 containing an embedded controller 17. Device 11 is any type of apparatus or system having functions that are monitored and controlled by embedded controller 17.
[0019] Device 11 is connected to an internal network 12, such as a LAN. A router or modem 14 couples internal network 12 to an external network 15, such as the Internet/World Wide Web (Web). External network 15 runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Network connections are via Ethernet, telephone line, wireless, or other transmission media.
[0020] External network 15 contains a server 19, which is a computer or any other processing device. Server 19 communicates with embedded controller 17 over external network 15 and internal network 12. Embedded controller 17 has a local IP (Internet Protocol) address that can be resolved within internal network 12. However, this local IP address may not be recognizable by devices on external network 15, such as server 19. As such, server 19 may not be able to directly address device 11.
Embedded Controller
[0021] Embedded controller 17 runs software 20, which includes web client application 21 and operating software 22. Web client application 21 includes a TCP/IP protocol stack that allows embedded controller 17 to communicate over external network 15. Device operating software 22 provides an interface between Web client application 21 and a database 24. Through device operating software 22, embedded controller 17 retrieves data stored in database 24 and stores data in database 24.
[0022] Database 24 is stored in a memory 25 on device 11 or internal to embedded controller 17. Database 24 stores data, including operational parameters, configuration files, and identification information for device 11.
[0023] The operational parameters constitute settings and/or control instructions for the device 11, which are implemented by embedded controller 17. The types of operational parameters that are stored in database 24 depend on the nature of device 11. For example, if device 11 is a heating/cooling system, the operational parameters may include temperature levels, humidity levels, airflow controls, vent/duct open/close controls, and fan motor speed settings. A configuration file is a file that contains a set of one or more operational parameters for an instance of device 11.
[0024] What is meant by “instance” is the specific identity of device 11 as distinguished from other identical devices. The identification information stored in database 24 identifies the instance of device 11. This identification information includes, but is not limited to, data identifying the type of the device, a common (or “friendly”) name for the device, the manufacturer of the device, the model name of the device, the model number of the device, the serial number of the device, and a universal unique identifier (UUID) for the device.
[0025] The device type specifies a uniform resource locator (URL) for the device, which includes the name of the device. This information identifies a Web site that is associated with, and generated by, server 19 for the device. For example, a device type might be:
-
- [0026] www.SonyVideo.com/television/Vega/XBR400
for a Sony® Vega® XBR400® television that includes an embedded controller. The common name of the device is how the device is known in the vernacular, e.g., “television”. The manufacturer identifies the manufacturer of the device, e.g., Sony®. The model name identifies the particular model of the device, e.g., Vega®. The model number identifies the model number of the device, e.g., XBR400®. The serial number identifies the serial number of a particular instance of the device, e.g., 53266D. The UUID is a universal identifier for the instance of the device, e.g., 4A89EA70-73B4-11d4-80DF-005DAB7BAC5. Of the data shown above, only the serial number and the UUID are unique to the instance of device 11.
Server
- [0026] www.SonyVideo.com/television/Vega/XBR400
[0027] Server 19 is a computer that runs HTTP (Hypertext Transfer Protocol). Server 19 includes a controller 27, such as a microprocessor, for executing software to perform the functions described below. To avoid confusion in terminology, the following reads as though those functions are performed by server 19, even though software in controller 27 of server 19 performs the functions.
[0028] Server 19 executes Web server software 29 to communicate over external network 15. Web server software 29 also hosts a Web page associated with device 11. The Web page (not shown) is displayed on the computer of a user, such as the owner of device 11, who may input updated operational parameters for the device. These input updated operational parameters are transmitted to Web server software 29 over external network 15. Web server software 29 stores the updated parameters in database 30.
[0029] Web server software 29 stores and retrieves data in database 30 using application logic 32. Application logic 32 is software for accessing database 30 using the CGI (Common Gateway Interface) protocol. CGI is a well-known protocol for accessing a database. The operational parameters can be stored in database 30 individually or as part of a configuration file for an instance of device 11.
[0030] Database 30 is stored in a memory 31, which is inside of, or external to, server 19. Database 30 stores data associated with device 11, including the operational parameters noted above. Other data that may be stored for device 11 is described below.
The Data Transfer Process
[0031] Embedded controller 17 executes software 20 to retrieve data, such as operational parameters, from remote server 19. Server 19 executes software 34 to send the data to embedded controller 17. FIG. 2 shows these processes in detail. The left half of FIG. 2 , titled “Embedded Controller” shows process 40 performed by embedded controller 17, and the right half of FIG. 2 , titled, “Server”, shows process 41 performed by server 19.
[0032] Process 40 generates and sends (201) a command to server 19. The command, or a modified version thereof, is sent by embedded controller 17 to server 19 periodically. It is through this command that embedded controller 17 polls server 19 to determine if there are any new/updated operational parameters for device 11.
[0033] The command includes data identifying device 11. The data identifies the specific instance of device 11 and includes a device type field and one or both of a device serial number field and a device UUID. The command may also include the common name field, the manufacturer name field, the model name field, and the model number field, as set forth above.
[0034] The command may be either an HTTP GET command or an HTTP post command. The data included in those commands is similar, with the difference being that the HTTP GET command retrieves a document, such as a configuration file, that contains operational parameters and the HTTP POST command retrieves individual operational parameters. An example of an HTTP GET command is shown in Appendix A and an example of an HTTP POST command is shown in Appendix B.
[0035] The HTTP POST and GET commands shown in Appendices A and B contain XML (extensible Markup Language) commands. XML is a self-describing computer language in the sense that fields in the XML code identify variables and their values in the XML code. For example, as shown in the Appendices, the “manufacturer” field identifies a manufacturer, e.g., Sony®, and is delineated by “<manufacturer>” to indicate the start of the field and “</manufacturer>” to indicate the end of the field. XML is used because it can be generated, parsed and read relatively easily by server 19 and embedded controller 17.
[0036] As noted, the GET command is used to retrieve a document from server 19. The document to be retrieved corresponds to the fields in the GET command, in particular to the device type, serial number and/or UUID fields. By contrast, the POST command is used to retrieve individual operational parameters. The operational parameters that are to be retrieved are listed in the POST command itself. For example, as shown in Appendix B, the operational parameters include airflow, humidity, motor and vent values for the fictitious “widget” device. The current values of these parameters are specified in the POST command shown in Appendix B as follows:
-
- [0037] <parameters>
- [0038] <Airflow xsd:type=“integer”>378</Airflow>
- [0039] <Humidity xsd:type=“double”>46.7</Humidity>
- [0040] <Motor xsd:type=“integer”>1500</Motor>
- [0041] <Vent xsd:type=“integer”>4</Vent>
- [0042] </parameters>
The updated values of these parameters are returned by server 19 to embedded controller 17 in a reply POST command. The updated values of these parameters are specified in the POST command shown in Appendix B as follows: - [0043] <parameters>
- [0044] <Motor xsd:type=“integer”>1250</ Motor >
- [0045] <Vent xsd:type=“integer”>2</Vent>
- [0046] </parameters>
- [0037] <parameters>
[0047] As shown, both the POST and GET commands include the URL of the device in the device type field. As described below, this directs server 19 to a Web site associated with device 11 and, thereafter, in the case of a GET Command, to retrieve a specific Web page that is generated by server 19 for the device. It is noted that, since the POST command retrieves parameters, not a document like the GET command, the POST command need not include a URL of the device.
[0048] Referring back to FIG. 2 , process 41 (in server 19) receives (202) the command from embedded controller 17. Process 41 identifies the command as either a POST or GET command based on a header, such as “POST/CONTROL HTTP/1.1” (see the headers in Appendices A and B), in the command. Process 41 uses an XML parser to parse (203) the various identifying fields, such as device type, serial number, and UUID, from the command.
[0049] Process 41 identifies (204) the instance of device 11 based on the information parsed from the command. That is, process 41 uses the device type, serial number, and UUID field information to identify the instance.
[0050] If the Command is a POST Command
[0051] The remaining identification information from the command is used to narrow the search through database 30 down to data for the specific instance of device 11. The device serial number and/or UUID are used to retrieve operational parameters specific to device 11.
[0052] Once the appropriate data has been identified (204), process 41 retrieves (205) that data using application logic 32. Process 41 compares the values of the operational parameters to those included in the POST command. If the values are the same, process 41 returns an indication that there are no new/updated values for device 11. If the values of the operational parameters are different, process 41 adds the appropriate updated value fields to the POST command and sends (206) the POST command, with the updated operational parameters, back to embedded controller 17. Thus, only those operational parameters that differ from their original values are returned to embedded controller 17 in the POST command.
[0053] If the Command is a GET Command
[0054] As was the case above with the POST command, the remaining identification information from the command is used to narrow the search through database 30 down to data for the specific instance of device 11. In particular, the device serial number and/or UUID are used to retrieve (205) a configuration file that is specific to device 11. Process 41 then sends (206) the configuration file to embedded controller 17. The configuration file may be a Web page identified by the URL in the device type field. This Web page is generated by server 19 using parameters stored in database 30 and then sent to device 11. It is noted that the complete Web page itself need not be stored. Alternatively, the GET command may retrieve separate configuration files and Web pages.
[0055] Process 40 in embedded controller 17 receives (207) the data (operational parameters or configuration file) from server 19 in response to sending (201) the command. Process 40 then uses the data to update/reset device 11. For example, if device 11 is a heating system, a new operational parameter may be a new temperature setting for its thermostat. In this example, embedded controller 17 sets the new temperature accordingly. If the device is a television, a new operational parameter may indicate that certain pay television stations are now available. In this case, embedded controller 17 performs any appropriate decoding/descrambling functions on the television signal.
Alternative Embodiment
[0056] FIG. 3 shows alternative embodiments of processes 40,41. In processes 40,41, the GET and POST commands request the same parameters each time the commands are issued. The parameters requested are encoded in the software to implement process 40. This embodiment provides a way to change the parameters that are requested without altering the software that generates the request/command.
[0057] Referring to FIG. 3 , process 45 in embedded controller 17 begins by sending (301) a command to server 19. The command, in this case, is an HTTP GET command, since it is requesting a document, not individual operational parameters. The document is an XML document that contains a list of operational parameters to be updated. Using this document, embedded controller 17 can change the operational parameters that it periodically updates.
[0058] Process 46 in server 19 receives (302) the command from embedded controller 17, parses (303) the command using an XML parser to obtain the information specific to the instance of device 11, and identifies (304) the appropriate document based on this information. As before, the information that identifies the instance of device 11 includes, among other things, the device type, its serial number, and its UUID. Process 46 retrieves (305) the document containing the list of operational parameters to be updated, and sends (306) the document back to embedded controller 17.
[0059] Process 45 in embedded controller 17 receives (307) the document from server 19, parses (308) the operational parameters to be updated from the document, and formulates (309) a POST command to send to server 19. The command is formulated using a command template (not shown), into which process 45 inserts the operational parameters parsed from the document. Process 45 sends this second command to the server. At this point, processes 45 and 46 operate (310) in the same manner as processes 40 and 41, respectively, when used with a POST command. Accordingly, the details of processes 40,41 are not repeated here.
[0060] This alternative embodiment may be generalized further. For example, rather than simply retrieving a list of operational parameters, embedded controller 17 may retrieve, from server 19, a list of operations that it is to perform. For example, that list may contain operational parameters to be updated, times at which the updates are to occur, a schedule of diagnostic tests, and the like. Any operation that may be performed by embedded controller 17 may be included on the list.
[0061] The process for retrieving the list of operations is identical to processes 45 and 46, save for the contents of the list itself. The actions that embedded controller takes once it has the list (i.e., 310) depend on the contents of the list. For example, the list might specify that parameters are to be updated every hour and may also contain a list of the parameters to be updated. The list may contain XML commands, which can be parsed by embedded controller 17. Thus, embedded controller 17 reads the commands in the list and performs the appropriate operations with respect to device 11.
Architecture
[0062] Processes 40,41 and 45,46 are not limited to use with the hardware/software configuration of FIG. 1 ; they may find applicability in any computing or processing environment. Processes 40,41 and 45,46 may be implemented in hardware (e.g., an ASIC {Application-Specific Integrated Circuit} and/or an FPGA {Field Programmable Gate Array}), software, or a combination of hardware and software.
[0063] Processes 40,41 and 45,46 may be implemented using one or more computer programs executing on programmable computers that each includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.
[0064] Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. Also, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language.
[0065] Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform processes 40,41 and 45,46.
[0066] Processes 40,41 and 45,46 may also be implemented as a computer-readable storage medium, configured with a computer program, where, upon execution, instructions in the computer program cause the computer to operate in accordance with processes 40,41 and 45,46.
[0067] The invention is not limited to use with the protocols and standards described above. For example, Web server may use Java Servlets, ASP (Active Server Pages), and/or ISAPI (Internet Server Application Programming Interface) to communicate with application logic 32, instead of, or in addition to, CGI. The commands sent by embedded controller 17 and/or server 19 (e.g., in 201, 301, 310) are not limited to HTTP GET and POST commands. Any commands and/or requests for requesting and receiving data may be used.
[0068] The data transferred to embedded controller 17 by server 19 is not limited to operational parameters or configuration files. The data may include, for example, a schedule of actions to be performed by device 11 that is based on information pertaining the owner of the device. For example, owner preferences may be stored in database 30. The instance-specific data may be used by server 19 to correlate the owner of the device to the appropriate preferences. These preferences then may be transmitted back to device 11 to control the operation thereof.
[0069] The original parameters sent by embedded controller 17 to server 19 may be used by server 19 to calculate new, updated parameters based on data stored in database 30. Thus, the invention is not limited to simply retrieving updated data, but may also include calculating new data based on currently-available data.
[0070] The documents and commands described above are not limited to XML format. Any computer language may be used for the commands. The documents may be in any format, for example, HTML (Hypertext Markup Language) documents may be used. In addition, the invention is not limited to use with the Web, Web servers, and the like. The servers and embedded controllers described herein may be the same type of general-purpose computer appropriately programmed, or different devices.
[0071] Other embodiments not described herein are also within the scope of the following claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method performed by a controller that monitors and/or controls an apparatus, the method comprising:
polling a server by sending a message to the server periodically, the message containing information that distinguishes the apparatus from other like apparatuses, the message for establishing a connection between the server and the controller through which the instructions are sent;
receiving, from the server and in response to the message, one or more of plural instructions that are supported by the controller; and
using one or more of the instructions to affect at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
2. The method of claim 1, wherein the message comprises an operational parameter for the apparatus and at least one of the instructions comprises an updated value for the operational parameter.
3. The method of claim 2, wherein the message comprises plural operational parameters for the apparatus and at least one of the instructions comprises updated values that differ from current values of the operational parameters.
4. The method of claim 1, wherein at least one of the instructions comprises a list of operations to be performed by the controller; and
using one or more of the instructions comprises:
parsing the operations from the list; and
performing the operations from the list.
5. The method of claim 1, wherein at least one of the instructions comprises a configuration file for the apparatus.
6. The method of claim 1, wherein the message identifies the apparatus by a type and/or one or more of a serial number and a universal unique identifier.
7. The method of claim 1, wherein the message comprises a hypertext transfer protocol (HTTP) message.
8. The method of claim 7, wherein the message comprises an HTTP command that contains Extensible Markup Language code.
9. The method of claim 1, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
10. A method performed by a server for sending instructions over a network to a controller that monitors and/or controls an apparatus, the method comprising:
receiving a message from the controller periodically, the message containing information that distinguishes the apparatus from other like apparatuses, the message for establishing a connection between the server and the controller through which instructions are sent;
identifying the apparatus from the information in the message;
retrieving one or more instructions that are specific to the apparatus, the one or more instructions comprising one or more of plural instructions that are supported by the controller; and
sending the one or more instructions from the server to the controller, the one or more instructions for affecting at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
11. The method of claim 10, wherein:
the information in the message comprises a type and/or one or more of a serial number and a universal unique identifier; and
the apparatus is identified based on the type and/or one or more of the serial number and the universal unique identifier.
12. The method of claim 11, further comprising:
parsing the type and one or more of the serial number and universal unique identifier from the message prior to identifying the apparatus.
13. The method of claim 10, wherein:
the message comprises an operational parameter for the device; and
the one or more instructions comprises an updated value of the operational parameter.
14. The method of claim 10, wherein the one or more instructions comprises a list of operations to be performed by the apparatus.
15. The method of claim 10, wherein the one or more instructions comprises a configuration file for the apparatus.
16. The method of claim 10, further comprising:
receiving data specific to the apparatus; and
storing the data in memory as part of the plural instructions;
wherein the one or more instructions are retrieved from the memory.
17. The method of claim 16, wherein the data specific to the apparatus is received via a Web page generated by the server.
18. The method of claim 10, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
19. The method of claim 10, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
20. A system comprising:
a controller that monitors and/or controls an apparatus, the controller being capable of communicating over a computer network; and
a server that is capable of communicating over the computer network;
wherein (A) the controller polls the server periodically by sending a message to the server over the computer network, the message for establishing a connection between the server and the controller through which the instructions are sent, the message containing information that distinguishes the apparatus from other like apparatuses; and, in response to the message, (B) the server (i) identifies the apparatus based on the information in the message, (ii) retrieves one or more of plural instructions that are supported by the controller, and (iii) sends the one or more instructions to the controller over the computer network, the one or more instructions for affecting at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
21. The system of claim 20, wherein the server cannot initiate communication to the controller because the controller is not addressable from the computer network.
22. The system of claim 20, wherein the computer network comprises the Internet.
23. The system of claim 20, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
24. The system of claim 20, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
25. A computer program stored on one or more machine-readable media, the computer program being executable by a controller that monitors and/or controls an apparatus, the computer program comprising code to cause the controller to:
poll a server by sending a message to the server periodically, the message containing information that distinguishes the apparatus from other like apparatuses, the message for establishing a connection between the server and the controller through which the instructions are sent;
receive, from the server and in response to the message, one or more of plural instructions that are supported by the controller; and
use one or more of the instructions to affect at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
26. The computer program of claim 25, wherein the message comprises an operational parameter for the apparatus and at least one of the instructions comprises an updated value for the operational parameter.
27. The computer program of claim 26, wherein the message comprises plural operational parameters for the apparatus and at least one of the instructions comprises updated values that differ from current values of the operational parameters.
28. The computer program of claim 25, wherein at least one of the instructions comprises a list of operations to be performed by the controller; and
wherein using at least one of the instructions comprises:
parsing the operations from the list; and
performing the operations from the list.
29. The computer program of claim 25, wherein at least one of the instructions comprises a configuration file for the apparatus.
30. The computer program of claim 25, wherein the information in the message identifies the apparatus by a type and/or one or more of a serial number and a universal unique identifier.
31. The computer program of claim 25, wherein the message comprises a hypertext transfer protocol (HTTP) message.
32. The computer program of claim 25, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
33. The computer program of claim 25, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
34. A computer program stored on one or more machine-readable media, the computer program being executable by a server to send instructions over a network to a controller that monitors and/or controls an apparatus, the computer program comprising code to cause the server to:
receive a message from the controller periodically, the message containing information that distinguishes the apparatus from other like apparatuses, the message for establishing a connection between the server and the controller through which instructions are sent;
identify the apparatus from the information in the message;
retrieve one or more instructions that are specific to the apparatus, the one or more instructions comprising one or more of plural instructions that are supported by the controller; and
send the one or more instructions to the controller, the one or more instructions for affecting at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
35. The computer program of claim 34, wherein:
the information in the message comprises a type and/or one or more of a serial number and a universal unique identifier; and
the apparatus is identified based on the type and/or one or more of the serial number and the universal unique identifier.
36. The computer program of claim 35, further comprising code to cause the server to:
parse the type and one or more of the serial number and universal unique identifier from the message prior to identifying the apparatus.
37. The computer program of claim 34, wherein:
the message comprises an operational parameter for the apparatus; and
the one or more instructions comprises an updated value of the operational parameter.
38. The computer program of claim 34, wherein the one or more instructions comprises a list of operations to be performed by the apparatus.
39. The computer program of claim 34, wherein the one or more instructions comprises a configuration file for the apparatus.
40. The computer program of claim 34, further comprising code to cause the server to:
receive the data specific to the apparatus; and
store the data in memory as part of the plural instructions;
wherein the one or more instructions are retrieved from the memory.
41. The computer program of claim 40, wherein the data specific to the apparatus is received via a Web page generated by the server.
42. The computer program of claim 34, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
43. The computer program of claim 34, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
44. A device to monitor and/or control an apparatus, the device comprising:
a controller which is configured to execute code to:
poll a server by sending a message to the server periodically, the message containing information that distinguishes the apparatus from other like apparatuses, the message for establishing a connection between the server and the controller through which the instructions are sent;
receive, from the server and in response to the message, one or more of plural instructions that are supported by the controller; and
use one or more of the instructions to affect at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the server cannot initiate communication to the controller to send instructions to the controller.
45. The device of claim 44, wherein the message comprises an operational parameter for the apparatus and at least one of the instructions comprises an updated value for the operational parameter.
46. The device of claim 45, wherein the message comprises plural operational parameters for the apparatus and at least one of the instructions comprises updated values that differ from current values of the operational parameters.
47. The device of claim 44, wherein at least one of the instructions comprises a list of operations to be performed by the controller; and
wherein using at least one of the instructions comprises:
parsing the operations from the list; and
performing the operations from the list.
48. The device of claim 44, wherein at least one of the instructions comprises a configuration file for the apparatus.
49. The device of claim 44, wherein the information in the message identifies the apparatus by a type and/or one or more of a serial number and a universal unique identifier.
50. The device of claim 44, wherein the message comprises a hypertext transfer protocol (HTTP) message.
51. The device of claim 44, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
52. The device of claim 44, wherein the server cannot initiate communication because the controller has a network address that the server cannot resolve.
53. A device for sending data over a network to a remote controller that monitors and/or controls an apparatus, the device comprising:
a local controller configured to execute code to:
identify the apparatus from the information in the message;
retrieve one or more instructions that are specific to the apparatus, the one or more instructions comprising one or more of plural instructions that are supported by the remote controller; and
send the one or more instructions to the remote controller, the one or more instructions for affecting at least one of:
a configuration of the apparatus in response to an instruction that is configured to affect the configuration of the apparatus,
an operation of the apparatus in response to an instruction that is configured to affect the operation of the apparatus, and
an operation of the remote controller in response to an instruction that is configured to affect the operation of the controller;
wherein, due to network addressing, the local controller cannot initiate communication to the remote controller to send instructions to the controller.
54. The device of claim 53, wherein:
the information in the message comprises a type and/or one or more of a serial number and a universal unique identifier; and
the apparatus is identified based on the type and/or one or more of the serial number and the universal unique identifier.
55. The device of claim 54, wherein the local controller executes code to:
parse the type and one or more of the serial number and universal unique identifier from the command prior to identifying the apparatus.
56. The device of claim 53, wherein:
the message comprises an operational parameter for the apparatus; and
the one or more instructions comprises an updated value of the operational parameter.
57. The device of claim 53, wherein the one or more instructions comprises a list of operations to be performed by the apparatus.
58. The device of claim 53, wherein the one or more instructions comprises a configuration file for the apparatus.
59. The device of claim 53, wherein:
the local controller executes code to:
receive data specific to the apparatus; and
store the data in memory as part of the plural instructions.
60. The device of claim 59, wherein the data specific to the apparatus is received via a Web page generated by the device.
61. The device of claim 53, wherein the message comprises a hypertext transfer protocol (HTTP) command that contains Extensible Markup Language (XML) code.
62. The device of claim 53, wherein the local controller cannot initiate communication because the remote controller has a network address that the local controller cannot resolve.
63. A method performed by a controller that monitors and/or controls an apparatus, the method comprising:
polling a server for messages periodically, wherein polling comprises initiating communication with the server by sending a first message to the server, the first message for identifying the apparatus and for establishing a connection between the server and the controller through which the instructions are sent;
receiving a first reply message from the server in response to the first message, the first reply message identifying a parameter;
sending a second message to the server in response to the first reply message, the second message containing the parameter identified in the first reply message;
receiving a second reply message containing an updated version of the parameter; and
using the updated version of the parameter to affect at least one of:
a configuration of the apparatus if the parameter relates to the configuration of the apparatus,
an operation of the apparatus if the parameter relates to operation of the apparatus, and
an operation of the controller if the parameter relates to operation of the controller;
wherein the server cannot initiate communication to the controller because the server cannot resolve a network address of the controller.
64. The method of claim 63, further comprising adjusting a time interval at which polling the server takes place.
65. The method of claim 63, wherein the server cannot resolve a network address of the controller because the server and the controller are on different networks.
66. The method of claim 63, wherein the first message and the second message comprise Hypertext Transfer Protocol commands.
67. A computer program stored on one or more machine-readable media, the computer program comprising code that is executable by a controller configured to monitor and/or control an apparatus, the code causing the controller to:
poll a server for messages periodically, wherein polling comprises initiating communication with the server by sending a first message to the server, the first message for identifying the apparatus and for establishing a connection between the server and the controller through which the instructions are sent;
receive a first reply message from the server in response to the first message, the first reply message identifying a parameter;
send a second message to the server in response to the first reply message, the second message containing the parameter identified in the first reply message;
receive a second reply message containing an updated version of the parameter; and
use the updated version of the parameter to affect at least one of:
a configuration of the apparatus if the parameter relates to the configuration of the apparatus,
an operation of the apparatus if the parameter relates to operation of the apparatus, and
an operation of the controller if the parameter relates to operation of the controller;
wherein the server cannot initiate communication to the controller because the server cannot resolve a network address of the controller.
68. The computer program of claim 67, further comprising code to cause the controller to adjust a time interval at which polling the server takes place.
69. The computer program of claim 67, wherein the server cannot resolve a network address of the controller because the server and the controller are on different networks.
70. The computer program of claim 67, wherein the first message and the second message comprise Hypertext Transfer Protocol commands.
71. A device comprising:
a controller that monitors and/or controls an apparatus, the controller executing code to:
poll a server for messages periodically, wherein polling comprises initiating communication with the server by sending a first message to the server, the first message for identifying the apparatus and for establishing a connection between the server and the controller through which the instructions are sent;
receive a first reply message from the server in response to the first message, the first reply message identifying a parameter;
send a second message to the server in response to the first reply message, the second message containing the parameter identified in the first reply message;
receive a second reply message containing an updated version of the parameter; and
use the updated version of the parameter to affect at least one of:
a configuration of the apparatus if the parameter relates to the configuration of the apparatus,
an operation of the apparatus if the parameter relates to operation of the apparatus, and
an operation of the controller if the parameter relates to operation of the controller;
wherein the server cannot initiate communication to the controller because the server cannot resolve a network address of the controller.
72. The device of claim 71, wherein the controller executes code to adjust a time interval at which polling the server takes place.
73. The device of claim 71, wherein the server cannot resolve a network address of the controller because the server and the controller are on different networks.
74. The device of claim 71, wherein the first message and the second message comprise Hypertext Transfer Protocol commands.
Patent Citations (311)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4086434(A) | 1978-04-01 | Bocchi | Applicant |
| US4412292(A) | 1983-10-01 | Sedam et al. | Applicant |
| US4497037(A) | 1985-01-01 | Kato et al. | Applicant |
| US4583834(A) | 1986-04-01 | Seko et al. | Applicant |
| US4853946(A) | 1989-08-01 | Elliott et al. | Applicant |
| US4962368(A) | 1990-10-01 | Dobrzanski et al. | Applicant |
| US4964065(A) | 1990-10-01 | Hicks et al. | Applicant |
| US4965946(A) | 1990-10-01 | Hegedus et al. | Applicant |
| US4996703(A) | 1991-02-01 | Gray | Applicant |
| US5038319(A) | 1991-08-01 | Carter et al. | Applicant |
| US5057866(A) | 1991-10-01 | Hill, Jr. et al. | Applicant |
| US5077582(A) | 1991-12-01 | Kravette et al. | Applicant |
| US5084875(A) | 1992-01-01 | Weinberger et al. | Applicant |
| US5129080(A) | 1992-07-01 | Smith | Applicant |
| US5138377(A) | 1992-08-01 | Smith et al. | Applicant |
| US5184179(A) | 1993-02-01 | Tarr et al. | Applicant |
| US5204699(A) | 1993-04-01 | Birnbaum et al. | Applicant |
| US5212645(A) | 1993-05-01 | Wildes et al. | Applicant |
| US5214772(A) | 1993-05-01 | Weinberger et al. | Applicant |
| US5216461(A) | 1993-06-01 | Maekawa et al. | Applicant |
| US5220380(A) | 1993-06-01 | Hirata et al. | Applicant |
| US5224157(A) | 1993-06-01 | Yamada et al. | Applicant |
| US5243382(A) | 1993-09-01 | Takano et al. | Applicant |
| US5257069(A) | 1993-10-01 | Hirata et al. | Applicant |
| US5261061(A) | 1993-11-01 | Ju | Applicant |
| US5270775(A) | 1993-12-01 | Suzuki | Applicant |
| US5282127(A) | 1994-01-01 | Mii | Applicant |
| US5291244(A) | 1994-03-01 | Kajiwara et al. | Applicant |
| US5293196(A) | 1994-03-01 | Kaneko et al. | Applicant |
| US5297034(A) | 1994-03-01 | Weinstein | Applicant |
| US5297256(A) | 1994-03-01 | Wolstenholme et al. | Applicant |
| US5300980(A) | 1994-04-01 | Maekawa et al. | Applicant |
| US5303005(A) | 1994-04-01 | Takano et al. | Applicant |
| US5305055(A) | 1994-04-01 | Ebner et al. | Applicant |
| US5305199(A) | 1994-04-01 | LoBiondo et al. | Applicant |
| US5307263(A) | 1994-04-01 | Brown | Applicant |
| US5325156(A) | 1994-06-01 | Ulinski | Applicant |
| US5333286(A) | 1994-07-01 | Weinberger et al. | Applicant |
| US5335048(A) | 1994-08-01 | Takano et al. | Applicant |
| US5339168(A) | 1994-08-01 | Evanitsky et al. | Applicant |
| US5342037(A) | 1994-08-01 | Martin | Applicant |
| US5347346(A) | 1994-09-01 | Shimizu et al. | Applicant |
| US5359391(A) | 1994-10-01 | Kuroyanagi et al. | Applicant |
| US5361265(A) | 1994-11-01 | Weinberger et al. | Applicant |
| US5365310(A) | 1994-11-01 | Jenkins et al. | Applicant |
| US5367667(A) | 1994-11-01 | Wahlquist et al. | Applicant |
| US5369469(A) | 1994-11-01 | Leo et al. | Applicant |
| US5369471(A) | 1994-11-01 | Yamada | Applicant |
| US5369472(A) | 1994-11-01 | Raj et al. | Applicant |
| US5373349(A) | 1994-12-01 | Ito | Applicant |
| US5384622(A) | 1995-01-01 | Hirata et al. | Applicant |
| US5386271(A) | 1995-01-01 | Maekawa et al. | Applicant |
| US5392095(A) | 1995-02-01 | Siegel | Applicant |
| US5398257(A) | 1995-03-01 | Groenteman | Applicant |
| US5404199(A) | 1995-04-01 | Hirata et al. | Applicant |
| US5412779(A) | 1995-05-01 | Motoyama | Applicant |
| US5414494(A) | 1995-05-01 | Aikens et al. | Applicant |
| US5420667(A) | 1995-05-01 | Kaneko et al. | Applicant |
| US5424808(A) | 1995-06-01 | Maekawa et al. | Applicant |
| US5424844(A) | 1995-06-01 | Koyanagi et al. | Applicant |
| US5428551(A) | 1995-06-01 | Trainor et al. | Applicant |
| US5442541(A) | 1995-08-01 | Hube et al. | Applicant |
| US5444517(A) | 1995-08-01 | Nagashima | Applicant |
| US5444851(A) | 1995-08-01 | Woest | Applicant |
| US5446522(A) | 1995-08-01 | Tahara et al. | Applicant |
| US5452057(A) | 1995-09-01 | Imaizumi et al. | Applicant |
| US5459552(A) | 1995-10-01 | Ohira | Applicant |
| US5463775(A) | 1995-10-01 | DeWitt et al. | Applicant |
| US5469353(A) | 1995-11-01 | Pinsky et al. | Applicant |
| US5488454(A) | 1996-01-01 | Fukada et al. | Applicant |
| US5491535(A) | 1996-02-01 | Hirata et al. | Applicant |
| US5493364(A) | 1996-02-01 | Kuroyanagi et al. | Applicant |
| US5517491(A) | 1996-05-01 | Nanni et al. | Applicant |
| US5543892(A) | 1996-08-01 | Hirata et al. | Applicant |
| US5548376(A) | 1996-08-01 | Kikuno | Applicant |
| US5550957(A) | 1996-08-01 | Davidson, Jr. et al. | Applicant |
| US5555191(A) | 1996-09-01 | Hripcsak | Applicant |
| US5561501(A) | 1996-10-01 | Honma | Applicant |
| US5572672(A) | 1996-11-01 | Dewitt et al. | Applicant |
| US5586254(A) | 1996-12-01 | Kondo et al. | Applicant |
| US5594529(A) | 1997-01-01 | Yamashita et al. | Applicant |
| US5600403(A) | 1997-02-01 | Inoo | Applicant |
| US5603060(A) | 1997-02-01 | Weinberger et al. | Applicant |
| US5603323(A) | 1997-02-01 | Pflugrath et al. | Applicant |
| US5619024(A) | 1997-04-01 | Kolls | Applicant |
| US5631724(A) | 1997-05-01 | Sawada et al. | Applicant |
| US5636008(A) | 1997-06-01 | LoBiondo et al. | Applicant |
| US5636333(A) | 1997-06-01 | Davidson, Jr. et al. | Applicant |
| US5638427(A) | 1997-06-01 | Flemming et al. | Applicant |
| US5640495(A) | 1997-06-01 | Colbert et al. | Applicant |
| US5642202(A) | 1997-06-01 | Williams et al. | Applicant |
| US5642208(A) | 1997-06-01 | Takahashi et al. | Applicant |
| US5655084(A) | 1997-08-01 | Pinsky et al. | Applicant |
| US5659794(A) | 1997-08-01 | Caldarale et al. | Applicant |
| US5673190(A) | 1997-09-01 | Kahleck et al. | Applicant |
| US5675744(A) | 1997-10-01 | Tsujii | Applicant |
| US5677775(A) | 1997-10-01 | Yamaguchi et al. | Applicant |
| US5694528(A) | 1997-12-01 | Hube | Applicant |
| US5699494(A) | 1997-12-01 | Colbert et al. | Applicant |
| US5708908(A) | 1998-01-01 | Hirata et al. | Applicant |
| US5708909(A) | 1998-01-01 | Yamashita et al. | Applicant |
| US5715393(A) | 1998-02-01 | Naugle | Applicant |
| US5715496(A) | 1998-02-01 | Sawada et al. | Applicant |
| US5715823(A) | 1998-02-01 | Wood et al. | Applicant |
| US5720015(A) | 1998-02-01 | Martin et al. | Applicant |
| US5727135(A) | 1998-03-01 | Webb et al. | Applicant |
| US5732212(A) | 1998-03-01 | Perholz et al. | Applicant |
| US5736965(A) | 1998-04-01 | Mosebrook et al. | Applicant |
| US5740801(A) | 1998-04-01 | Branson | Applicant |
| US5745268(A) | 1998-04-01 | Eastvold et al. | Applicant |
| US5748907(A) | 1998-05-01 | Crane | Applicant |
| US5752125(A) | 1998-05-01 | Yamashita et al. | Applicant |
| US5752128(A) | 1998-05-01 | Yamashita | Applicant |
| US5752917(A) | 1998-05-01 | Fuchs | Applicant |
| US5761529(A) | 1998-06-01 | Raji et al. | Applicant |
| US5764918(A) | 1998-06-01 | Poulter | Applicant |
| US5768516(A) | 1998-06-01 | Sugishima | Applicant |
| US5772585(A) | 1998-06-01 | Lavin et al. | Applicant |
| US5774052(A) | 1998-06-01 | Hamm et al. | Applicant |
| US5786994(A) | 1998-07-01 | Friz et al. | Applicant |
| US5787149(A) | 1998-07-01 | Yousefi et al. | Applicant |
| US5787278(A) | 1998-07-01 | Barton et al. | Applicant |
| US5790793(A) | 1998-08-01 | Higley | Applicant |
| US5790977(A) | 1998-08-01 | Exekiel | Applicant |
| US5798738(A) | 1998-08-01 | Yamada | Applicant |
| US5801964(A) | 1998-09-01 | McCarthy | Applicant |
| US5809237(A) | 1998-09-01 | Watts et al. | Applicant |
| US5812397(A) | 1998-09-01 | Pech et al. | Applicant |
| US5812874(A) | 1998-09-01 | Yamashita et al. | Applicant |
| US5818603(A) | 1998-10-01 | Motoyama | Applicant |
| US5819015(A) | 1998-10-01 | Martin et al. | Applicant |
| US5819110(A) | 1998-10-01 | Motoyama | Applicant |
| US5822221(A) | 1998-10-01 | Groenteman | Applicant |
| US5828943(A) | 1998-10-01 | Brown | Applicant |
| US5835816(A) | 1998-11-01 | Sawada et al. | Applicant |
| US5844550(A) | 1998-12-01 | Trainor et al. | Applicant |
| US5845230(A) | 1998-12-01 | Lamberson | Applicant |
| US5857967(A) | 1999-01-01 | Frid et al. | Applicant |
| US5862404(A) | 1999-01-01 | Onaga | Applicant |
| US5865745(A) | 1999-02-01 | Schmitt et al. | Applicant |
| US5872635(A) | 1999-02-01 | Akiyama | Applicant |
| US5873009(A) | 1999-02-01 | Yamashita et al. | Applicant |
| US5873659(A) | 1999-02-01 | Edwards et al. | Applicant |
| US5878746(A) | 1999-03-01 | Lemelson et al. | Applicant |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5884072(A) | 1999-03-01 | Rasmussen | Applicant |
| US5887216(A) | 1999-03-01 | Motoyama | Applicant |
| US5890029(A) | 1999-03-01 | Hirata et al. | Applicant |
| US5894416(A) | 1999-04-01 | Kuroyanagi et al. | Applicant |
| US5897235(A) | 1999-04-01 | Honma | Applicant |
| US5901286(A) | 1999-05-01 | Danknick et al. | Applicant |
| US5905906(A) | 1999-05-01 | Goffinet et al. | Applicant |
| US5909493(A) | 1999-06-01 | Motoyama | Applicant |
| US5911095(A) | 1999-06-01 | Atsumi et al. | Applicant |
| US5917405(A) | 1999-06-01 | Joao | Applicant |
| US5933675(A) | 1999-08-01 | Sawada et al. | Applicant |
| US5935060(A) | 1999-08-01 | Iliff | Applicant |
| US5956487(A) | 1999-09-01 | Venkatraman et al. | Applicant |
| US5956698(A) | 1999-09-01 | Lachese et al. | Applicant |
| US5968116(A) | 1999-10-01 | Day et al. | Applicant |
| US5970149(A) | 1999-10-01 | Johnson | Applicant |
| US5975737(A) | 1999-11-01 | Carter et al. | Applicant |
| US6003061(A) | 1999-12-01 | Jones et al. | Applicant |
| US6003078(A) | 1999-12-01 | Kodimer et al. | Applicant |
| US6006045(A) | 1999-12-01 | Miyawaki | Applicant |
| US6009284(A) | 1999-12-01 | Weinberger et al. | Applicant |
| US6012088(A) | 2000-01-01 | Li et al. | Applicant |
| US6014631(A) | 2000-01-01 | Teagarden et al. | Applicant |
| US6014691(A) | 2000-01-01 | Brewer et al. | Applicant |
| US6021284(A) | 2000-02-01 | Serizawa et al. | Applicant |
| US6022315(A) | 2000-02-01 | Iliff | Applicant |
| US6023223(A) | 2000-02-01 | Baxter, Jr. | Applicant |
| US6025925(A) | 2000-02-01 | Davidson, Jr. et al. | Applicant |
| US6031964(A) | 2000-02-01 | Anderson | Applicant |
| US6042111(A) | 2000-03-01 | Rivers et al. | Applicant |
| US6060994(A) | 2000-05-01 | Chen | Applicant |
| US6061603(A) | 2000-05-01 | Papadopoulos et al. | Applicant |
| US6064915(A) | 2000-05-01 | Kaneko et al. | Applicant |
| US6091915(A) | 2000-07-01 | Takagishi | Applicant |
| US6098116(A) | 2000-08-01 | Nixon et al. | Applicant |
| US6101407(A) | 2000-08-01 | Groezinger | Applicant |
| US6108492(A) | 2000-08-01 | Miyachi | Applicant |
| US6112035(A) | 2000-08-01 | Kuroyanagi et al. | Applicant |
| US6112256(A) | 2000-08-01 | Goffinet et al. | Applicant |
| US6115489(A) | 2000-09-01 | Gupta et al. | Applicant |
| US6119934(A) | 2000-09-01 | Kolls | Applicant |
| US6122463(A) | 2000-09-01 | Nagatani | Applicant |
| US6130999(A) | 2000-10-01 | Serizawa et al. | Applicant |
| US6139177(A) | 2000-10-01 | Venkatraman et al. | Applicant |
| US6152365(A) | 2000-11-01 | Kolls | Applicant |
| US6167448(A) | 2000-12-01 | Hemphill et al. | Applicant |
| US6181331(B1) | 2001-01-01 | Trainor et al. | Applicant |
| US6189113(B1) | 2001-02-01 | Rabb et al. | Applicant |
| US6196735(B1) | 2001-03-01 | Inamine | Applicant |
| US6221011(B1) | 2001-04-01 | Bardy | Applicant |
| US6230199(B1) | 2001-05-01 | Revashetti et al. | Applicant |
| US6246485(B1) | 2001-06-01 | Brown et al. | Applicant |
| US6256668(B1) | 2001-07-01 | Slivka et al. | Applicant |
| US6260148(B1) | 2001-07-01 | Aggarwal et al. | Applicant |
| US6260248(B1) | 2001-07-01 | Cramer et al. | Applicant |
| US6282454(B1) | 2001-08-01 | Papadopoulos et al. | Examiner |
| US6282711(B1) | 2001-08-01 | Halpern et al. | Applicant |
| US6286038(B1) | 2001-09-01 | Reichmeyer et al. | Applicant |
| US6286059(B1) | 2001-09-01 | Sugiura | Applicant |
| US6292828(B1) | 2001-09-01 | Williams | Applicant |
| US6304895(B1) | 2001-10-01 | Schneider et al. | Applicant |
| US6308099(B1) | 2001-10-01 | Fox et al. | Applicant |
| US6311024(B1) | 2001-10-01 | Serizawa et al. | Applicant |
| US6312378(B1) | 2001-11-01 | Bardy | Applicant |
| US6317783(B1) | 2001-11-01 | Freishtat et al. | Applicant |
| US6317848(B1) | 2001-11-01 | Sorens et al. | Applicant |
| US6325540(B1) | 2001-12-01 | Lounsberry et al. | Applicant |
| US6343320(B1) | 2002-01-01 | Fairchild et al. | Applicant |
| US6356949(B1) | 2002-03-01 | Katsandres et al. | Applicant |
| US6368284(B1) | 2002-04-01 | Bardy | Applicant |
| US6370582(B1) | 2002-04-01 | Lim et al. | Examiner |
| US6377162(B1) | 2002-04-01 | Delestienne et al. | Applicant |
| US6381557(B1) | 2002-04-01 | Babula et al. | Applicant |
| US6397212(B1) | 2002-05-01 | Biffar | Applicant |
| US6405310(B1) | 2002-06-01 | Simpson | Applicant |
| US6406426(B1) | 2002-06-01 | Reuss et al. | Applicant |
| US6415023(B2) | 2002-07-01 | Iggulden | Applicant |
| US6426798(B1) | 2002-07-01 | Yeung | Applicant |
| US6430711(B1) | 2002-08-01 | Sekizawa | Applicant |
| US6434572(B2) | 2002-08-01 | Derzay et al. | Applicant |
| US6437692(B1) | 2002-08-01 | Petite et al. | Applicant |
| US6446192(B1) | 2002-09-01 | Narasimhan et al. | Applicant |
| US6449633(B1) | 2002-09-01 | Van et al. | Applicant |
| US6457038(B1) | 2002-09-01 | Defosse | Applicant |
| US6462831(B1) | 2002-10-01 | Akiyama | Applicant |
| US6466971(B1) | 2002-10-01 | Humpleman et al. | Applicant |
| US6477117(B1) | 2002-11-01 | Narayanaswami et al. | Applicant |
| US6487513(B1) | 2002-11-01 | Eastvold et al. | Applicant |
| US6493871(B1) | 2002-12-01 | McGuire et al. | Applicant |
| US6494831(B1) | 2002-12-01 | Koritzinsky | Applicant |
| US6510350(B1) | 2003-01-01 | Steen et al. | Applicant |
| US6523130(B1) | 2003-02-01 | Hickman et al. | Applicant |
| US6529848(B2) | 2003-03-01 | Sone | Applicant |
| US6549612(B2) | 2003-04-01 | Gifford et al. | Applicant |
| US6560611(B1) | 2003-05-01 | Nine et al. | Applicant |
| US6560656(B1) | 2003-05-01 | O'Sullivan et al. | Examiner |
| US6564227(B2) | 2003-05-01 | Sakakibara et al. | Applicant |
| US6581092(B1) | 2003-06-01 | Motoyama et al. | Applicant |
| US6581094(B1) | 2003-06-01 | Gao | Applicant |
| US6587812(B1) | 2003-07-01 | Takayama | Applicant |
| US6598011(B1) | 2003-07-01 | Koritzinsky et al. | Applicant |
| US6601159(B1) | 2003-07-01 | Smith et al. | Applicant |
| US6604212(B2) | 2003-08-01 | Sekizawa et al. | Applicant |
| US6611863(B1) | 2003-08-01 | Banginwar | Applicant |
| US6631407(B1) | 2003-10-01 | Mukaiyama et al. | Applicant |
| US6636899(B1) | 2003-10-01 | Rabb et al. | Applicant |
| US6651110(B1) | 2003-11-01 | Caspers et al. | Examiner |
| US6651190(B1) | 2003-11-01 | Worley et al. | Examiner |
| US6654720(B1) | 2003-11-01 | Graham et al. | Applicant |
| US6670810(B2) | 2003-12-01 | Duncan et al. | Applicant |
| US6681349(B2) | 2004-01-01 | Sekizawa | Applicant |
| US6686838(B1) | 2004-02-01 | Rezvani et al. | Applicant |
| US6691106(B1) | 2004-02-01 | Sathyanarayan | Applicant |
| US6710893(B1) | 2004-03-01 | Hou et al. | Applicant |
| US6711618(B1) | 2004-03-01 | Danner et al. | Applicant |
| US6757714(B1) | 2004-06-01 | Hansen | Applicant |
| US6832373(B2) | 2004-12-01 | O'Neill | Applicant |
| US6834298(B1) | 2004-12-01 | Singer et al. | Applicant |
| US6857013(B2) | 2005-02-01 | Ramberg et al. | Applicant |
| US2002/0006790(A1) | 2002-01-01 | Blumenstock et al. | Applicant |
| US2002/0038320(A1) | 2002-03-01 | Brook | Applicant |
| US2002/0064138(A1) | 2002-05-01 | Saito et al. | Applicant |
| US2002/0138567(A1) | 2002-09-01 | Ogawa | Applicant |
| US2002/0174085(A1) | 2002-11-01 | Nelson et al. | Applicant |
| US2002/0178241(A1) | 2002-11-01 | Eriksson | Applicant |
| US2003/0061403(A1) | 2003-03-01 | Miyata et al. | Applicant |
| US2003/0118353(A1) | 2003-06-01 | Baller | Applicant |
| US2003/0200285(A1) | 2003-10-01 | Hansen et al. | Applicant |
| EP1191744(A2) | 2002-03-01 | Applicant | |
| JP60-263162 | 1985-12-01 | Applicant | |
| JP6-062130 | 1994-03-01 | Applicant | |
| JP6062130 | 1994-03-01 | Applicant | |
| JP7325513 | 1995-12-01 | Applicant | |
| JP9163008 | 1997-06-01 | Applicant | |
| JP10190922 | 1998-07-01 | Applicant | |
| JP10224372 | 1998-08-01 | Applicant | |
| JP10-295788 | 2000-04-01 | Applicant | |
| JP2000-122952 | 2000-04-01 | Applicant | |
| JP200122952 | 2000-04-01 | Applicant | |
| WO98/20439 | 1998-05-01 | Applicant | |
| WO98/20439 | 1998-05-01 | Applicant | |
| WO98/33302 | 1998-07-01 | Applicant | |
| WO98/38910 | 1998-09-01 | Applicant | |
| WO98/38910 | 1998-09-01 | Applicant | |
| WO98/41943 | 1998-09-01 | Applicant | |
| WO98/41943 | 1998-09-01 | Applicant | |
| WO99/1336 | 1999-04-01 | Applicant | |
| WO99/21336 | 1999-04-01 | Applicant | |
| WO99/21336 | 1999-04-01 | Applicant | |
| WO99/57649 | 1999-11-01 | Applicant | |
| WO99/57649 | 1999-11-01 | Applicant | |
| WO99/57837 | 1999-11-01 | Applicant | |
| WO99/57838 | 1999-11-01 | Applicant | |
| WO99/57838 | 1999-11-01 | Applicant | |
| WO/23894 | 2000-04-01 | Applicant | |
| WO/23894 | 2000-04-01 | Applicant | |
| WO2/10919 | 2002-02-01 | Applicant | |
| WO2/21239 | 2002-03-01 | Applicant | |
| WO2/21299 | 2002-03-01 | Applicant | |
| WO2/21414 | 2002-03-01 | Applicant | |
| WO2/21414 | 2002-03-01 | Applicant | |
| WO2/21415 | 2002-03-01 | Applicant | |
| WO2/21777 | 2002-03-01 | Applicant | |
| WO2/25501 | 2002-03-01 | Applicant | |
| WO2/25501 | 2002-03-01 | Applicant | |
| WO98/33302 | 2002-03-01 | Applicant |
Non-Patent Literature (91)
- Database WIP, Section EI, Week 200156, Abstract, Document No. XP002253876 (Korea Electronics & Telecom Res. Inst.) Derwent Publications, Ltd., London, GB, Mar. 5, 2001.Applicant
- Box, et al., Simple Object Acces Protocol (SOAP) 1.1, Document No. XP002250270, May 8, 2000.Applicant
- Edward Steinfeld, “Making the Change” Document No. XP002201937, Apr. 2000, Circuit Cellar Online.Applicant
- International Search Report—PCT/US03/11707.Applicant
- http://www.linuxjournal.com/article.php?sid=4195.Applicant
- Steinfeld “From Standalone To Internet Appliance” circuit cellar online, ′online! Apr. 2000, pp. 1-7, XP002201937 retrieved from the internet: <url: http://www.chipcenter.com/circuitcell ar/apriloo/pdf/co4ooespdf.pdf>43,48, 'retrieved on 2002-06-1o.Applicant
- “RomWebClient Embedded HTTP client 1-61 Toolkit” ALLEGROSOFT, ′Online! Jul. 9, 2000, pp. 1-2, XPOO2201938 Retrieved from the Internet: <URL: http://web. archive.org/web/2000070920 4234/http://www.allegrosoft.com/romwebclient. html> retrieved on Jun. 12, 2002 the whole document.Applicant
- Allegro Software product release 1-61 overview Greenhills Software Inc., ′Online! Jun. 10, 2002, pp. 1-1, XPOO2201939 Retrieved from the Internet: URL: http://www.ghs. com/partners.allegro/<'retrieved on Jun. 10, 2002! the whole document.Applicant
- Incremona, A., “Remote Service Diagnostics for Imaging Equipment: Today and Tomorrow,” Advanced Imaging, 12(9):90(2) (1997).Applicant
- Lassman, M. et al., “Modern Nuclear Medical Diagnostics with Efficient Gamma Cameras,” Electromedica, 66(2):43-51 (1998).Applicant
- International Search Report PCT/US01/29787.Applicant
- “RomWebClient Embedded HTTP client 1-61 Toolkit” ALLEGROSOFT, ′Online! Jul. 9, 2000 (2000-07-091, pp. 1-2, Retrieved from the Internet: <URL: http://web. archive.org/web/2000070920 4234/http://www.allegrosoft.com/romwebclient. html> retrieved on Mar. 29, 2004, 2 pps.Applicant
- Allegro Software product release 1-61 overview Greenhills Software Inc., ′Online! Jun. 10, 2002 (2002-06-1o), pp. 1-1, Retrieved from the Internet: URL: http://www. ghs.com/partners/allegro/<'retrieved on Mar. 29, 2004, 1 pg.Applicant
- International Search Report PCT/US01/45198.Applicant
- International Search Report PCT/US01/23651.Applicant
- http://www.upnp.org/download/UPnPDA10—20000613.htm (pp. 1-52).Applicant
- Steinfeld, Edward, “Internet-appliance technology automates test equipment”, EDN Magazine, pp. 157-169 (2000).Applicant
- Williams, Tom, “Java Goes To Work Controlling Networked Embedded Systems”, Computer Design, 35:9:36-37 (1996).Applicant
- Office Action from European Patent Office, in Application. No. 01 955 993.9-2211; dated Jan. 29, 2004.Applicant
- Office Action dated Nov. 17, 2003, in U.S. Appl. No. 09/627,201.Applicant
- Ennis, D., “CORBA and XML Integration in Enterprise Systems”, IONA Technologies, Inc., www.iona.com/info/techcenter/ecoop2000apr17.pdf (2000).Applicant
- Emmerich, W. et al., “Implementing Incremental Code Migration with XML”, ISCE 2000, ACM, pp. 397-406 (2000).Applicant
- Suresh, R. et al., “XML-based Data System for Earth Science Applications”, IEEE, pp. 1214-1216 (2000).Applicant
- WebMethods B2B Whitepaper; www.cs.wisc.edu/˜vganti/papers/b2b—wpB2Bintegration.html.Applicant
- Virtual Reality Transfer Protocol (VRTP); www.stl.nps.navy.mil/˜brutzman/vrtp.Applicant
- The Simple Times, vol. 7, No. 1, Mar. 1999; www.simple-times.org/pub/simple-times/issues/7-1.html.Applicant
- Office Action dated Mar. 6, 2006, in U.S. Appl. No. 10/124,181.Applicant
- “Siemens Medical, BJC Health System Extend deal to multivendor service,” Medical Imaging News, vol. 6, No. 26, Jun. 27, 1997.Applicant
- Mar. 8, 2005 Office Action from application 01 973 431.8.Applicant
- Math Markup Language (Chapter 4): www.w3.org/TR/REC-MathML/chap4—4.html.Applicant
- Memphis Educational Computer Connectivity Alliance (MECCA) www.mecca.org/˜Itague/nsfnocostextension.html.Applicant
- EBITS: Electronic Business & Information Technology for Society Research Consortium www.cs.dartmouth.edu/˜makedon/cs188/proposal.html.Applicant
- Xerox 190 Copier, Electronic Data Interface Operator Guide, ver. 1.0, 1989.Applicant
- Lindley, David, “Xerox unveils copier that phones for help,” Rochester Democrat and Chronicle, Mar. 28, 1990.Applicant
- Rytting, Todd, “Dispensing the Goods, Embedded Style,” Circuit Cellar Online, Oct. 1999.Applicant
- Ennis, Darach, “Cobra and XML Integration in Enterprise Systems,” Trinity College Dublin, IONA Technologies Inc.Applicant
- Emmerich et al., “Implementing Incremental Code Migration with XML,” University College London, 2000.Applicant
- Suresh et al., “XML-Based Data Systems for Earth Science Applications,” Raytheon Information Technology and Scientific Services, Lanham, MD, 2000.Applicant
- Oct. 6, 1998, “Frequently Asked Questions about the Extensible Markup Language—The XML FAQ” Version 1.41 (http://www.oasis.open.org/cover/xmlFAQ141-19981006.html).Applicant
- Jun. 20, 1997, Layman, et al., “XML-Data,” Position Paper from Microsoft Corp. (http://www.oasis-open.org/cover/xml-data9706223.html).Applicant
- Pfeiffer, R., “Tutorial 2: Writing XML Documents,” 1999.Applicant
- Luh, James C., “With several specs complete, XML enters widespread development,” Internet World, Jan. 4, 1999.Applicant
- Kimball, Ralph, “XML Will Make it Easier,” Intelligent Enterprise (http://www.intelligententerprise.com/010507/webhouse1—1.jhtml).Applicant
- Kovar, Joseph, “Xerox Unveils Expanded Channel Lineup; Also Plans to Introduce E-Mail, Queue Management Software,” PC Expo, Jun. 18, 1999.Applicant
- EmWare Press Release: “Motorola, Mitsubishi and National Semiconductor Join emWare's Embed The Internet Alliance,” Chicago, IL, Mar. 2, 1999.Applicant
- EmWare Press Release: “emWare's emLink (TM) Used to Internet-enable Welch Allyn's Vital Signs Monitor,” Chicago, IL Mar. 2, 1999.Applicant
- EmWare Press Release: “emWare, IBM Demonstrate Next Phase in Establishing Worldwide Access to Embedded Devices,” Chicago, IL Mar. 2, 1999.Applicant
- EmWare Press Release: “Invensys Selects emWare EMIT Device-Networking Software to Add Remote Monitoring and Control Capabilities to its Controller Products,” Salt Lake City, Utah Jun. 14, 1999.Applicant
- EmWare Press Release: “emWare Delivers EMIT 3.0 SDK Pro-A Complete Device Networking Kit for Developing End-to-end, Embedded Device Networking Solutions,” Salt Lake City, Utah May 24, 1999.Applicant
- EmWare Press Release: “emWare Announces Support for Sun Microsystems Jini Technology,” Salt Lake City, Utah Feb. 17, 1999.Applicant
- Trewitt, G., “Digital Network Systems Laboratory, NSL Technical Note TN-14, Using Tcl to Process HTML Forms”.Applicant
- Jennyc, Kenn S., “Linking Enterprise Business Systems to the Factory Floor,” The Hewlett-Packard Journal, Article 9, May 1998.Applicant
- Walsh, Norman, “XSL The Extensible Style Language: Styling XML Documents,” New Architect Daily, Jan. 1999.Applicant
- Pfeiffer, R., “XML Tutorials for Programmers: Tutorial 2: Writing XML Documents,” (http://imb.com/xml).Applicant
- Winer, Dave, “XML-RPC Specification,” (http://XML-RPC.com), Jun. 15, 1999.Applicant
- Layman, A, et al., “XML-Data,” Microsoft Position Paper, Jun. 20, 1997 (http://www.oasis-open.org/cover/xml-data9706223.html).Applicant
- Sep. 1995, Medical Imaging, East Providence, RI.Applicant
- Eastvold, Roger, “Tiss and Tell,” Medical Imaging, Sep. 1995.Applicant
- Nov. 1996, 24x7, HealthTech Publishing Company, Inc.Applicant
- Wigget, Jeremy, “Intraview: Roger Eastvold of Orasis Inc.,” 24x7, Nov. 1996.Applicant
- Dec. 27, 1995, SCAN Diagnostic Imaging, vol. 8, No. 24.Applicant
- Winter 1992, Field of View, vol. 2, No. 3, Toshiba America Medical System, Inc.Applicant
- Reagan, Kelly, “Technology for the Soul,” OC Metro, Sep. 1, 1995.Applicant
- “Remote Diagnostics: Strategic weapon in the war for multi-vendor service contracts,” Tech Assessment, vol. 3, No. 12, Dec. 1995.Applicant
- Eastvold, Roger, “Services: The Next Generation,” The Professional Journal, vol. 20, No. 4.Applicant
- Apr. 22, 2005 Literature Search by Keyword: CyberTAC.Applicant
- Steinfeld, E., “Making the Change from Standalone to Internet Appliance,” Circuit Cellar Online, Apr. 2000, pp. 1-7.Applicant
- Allegro, RomWebClient Embedded HTTP client Toolkit: ALLEGROSOFT, Circuit Cellar Online, Sep. 7, 2000, pp. 1-2, XP-002201983, URL:http://web.archive.orgweb/20000709204234/http://www.allegrosoft.com/romwebclient.html.Applicant
- “Allegro Software product release overview,” Greenhills Software Inc., Jun. 10, 2002, p. 1, URL:http://www.ghs.com/partners/allegro/.Applicant
- European Office Action mailed Jun. 6, 2005 for Application No. 01955993.9-2211/1305712.Applicant
- Questra Preliminary Invalidity Contentions dated Apr. 29, 2005.Applicant
- Box et al., Simple Object Acess Protocol (SOAP) 1.1 Document No. XP002250270, May 8, 2000.Applicant
- XP-002253876, c:\epodata\sea\eplog\internal.log.Applicant
- Issue 77: The Next Bang: The Expolosive Combination of Embedded Linuz, XML, and Instant Mess, http://www.linuxjournal.com/article.php?sid=4195, pp. 1-15.Applicant
- CyberTAC & RadScape Presentation, May 1997.Applicant
- CyberTAC from Virtual Impact Systems, Inc. Presentation.Applicant
- CyberTAC Remote Support System Presentation.Applicant
- Questra Applications Data Sheet.Applicant
- CyberTAC Design Presentation.Applicant
- Orasis Medical Services, Inc., Business Plan Copy No. 001, Nov. 1995.Applicant
- McBride, R.A., “Security Considerations for Active Messages,” ACM SIGICE Bulletin, vol. 22 (2), Oct. 1996.Applicant
- Hanckmann, J., “Telescript: the emerging standard for intelligent messaging,” Philips Telecommunications Review, vol. 52(1).Applicant
- Lassman, M. et al., “Modern Nuclear Medical Diagnostics with Efficient Gamma Cameras,” Electromedica 66(2):43-51 (1998).Applicant
- Incremona, A. “Remote Service Diagnostics for Imaging Equipment: Today and Tomorrow,” Advanced Imaging, 12(9):90(2) (1997).Applicant
- “The Simple Times, The Quaterly Newsletter of SNMP Technology, Comment, and Events,” vol. 7, No. 1, Mar. 1999; wwww.simple-times.org/pub/simple-times/issues/7-1.html.Applicant
- Tom Williams, “Java Goes to Work Controlling Networked Embedded Systems,” Computer Designes, Pennwell Publ. Littleton, MA 35:9:36-37, Aug. 1996.Applicant
- Edward F. Steinfeld, “Internet-appliance technology automates test equipment,” EDN Magazine, pp. 157-169, Oct. 2000, www.edbmag.com.Applicant
- Database WIP, Section EI, Week 200156, Abstract, Document No. XP002253876 (Korea Electronics & Telecom Res Inst.) Derwent Publications, Ltd., London, GB, Mar. 5, 2001.Applicant
- WebMethods B2B Whitepaper; www.cs.wisc.edu/˜vganti/papers/b2b—wpB2Bintegration.html.Applicant
- Virtual Reality Transfer Protocol (VRTP); www.stl.nps.navy.mil/˜brutzman/vrtp.Applicant
- Lerner, R., “Introducing SOAP,” Linux Journal, pp. 62-70, Mar. 2001.Applicant