US 7,117,239 B1Grant
Reporting the state of an apparatus to a remote computer
Issue Date:2006-10-03
•37 Claims
•5 Drawing Sheets
Abstract
The state of an apparatus is reported to a remote computer using an embedded device in the apparatus. The embedded device detects the state, generates a message that reports the state using a self-describing computer language, and sends the message to the remote computer. The remote computer receives the message and extracts the state of the embedded device from the message.
Metadata
Assignee
- Axeda Corporation
Inventor
- James R. Hansen
Application Information
Application Number:US 09/708,384
Filing Date:2000-11-08
Priority Date:2000-07-28
Art Unit:2142
Classifications
IPC:
G06F15/16
Patent Drawings (5 sheets)
Description
CLAIM TO PRIORITY
[0001] This application is a continuation-in-part application of U.S. patent application Ser. No. 09/627,201, filed on Jul. 28, 2000 now U.S. Pat. No. 6,757,714 in the name of James R. Hansen.
BACKGROUND
[0002] This invention relates to using a device embedded in an apparatus (an “embedded device”) to report the state of the apparatus to a remote computer.
[0003] An apparatus may contain an embedded device, such as a controller, to monitor and control its operation. Any type of apparatus may have an embedded device, including, but not limited to, home appliances, such as washing machines, dishwashers, and televisions, and manufacturing equipment, such as robotics, conveyors and motors.
[0004] 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 devices over the internal network.
SUMMARY
[0005] In general, in one aspect, the invention is directed to using a device embedded in an apparatus to report the state of the apparatus to a remote computer. This aspect of the invention features detecting the state of the apparatus, generating a message that reports the state of the apparatus using a self-describing computer language, and sending the message to the remote computer. An example of a self-describing computer language is eXtensible Markup Language (XML). Examples of messages that may be sent include an electronic mail (e-mail) message and a hypertext transfer protocol (HTTP) command, both containing XML code.
[0006] By virtue of the device-generated message, the remote computer can obtain the state of the apparatus even if the remote computer cannot directly address the embedded device. Thus, computers that cannot communicate directly with the embedded device, such as computers that are not on the same internal network as the embedded device, can still obtain the status of the apparatus. Moreover, because the state is reported using a self-describing computer language, the remote computer can interpret the state without the aid of a person. As a result, processes, such as maintenance and the like, can be scheduled automatically for the apparatus and/or embedded device by the remote computer.
[0007] This aspect of the invention may include one or more of the following features. The state is indicative of an error condition in the apparatus. The error condition is a variable that deviates from an acceptable value or a predetermined range of acceptable values. The function of detecting the state includes receiving the state from the apparatus by, e.g., retrieving the state periodically from the apparatus. The function of detecting the state includes obtaining an identifier for the apparatus, the identifier relating to the state of the apparatus, and using the embedded device to read the state from the apparatus using the identifier.
[0008] This aspect of the invention may also include determining if the state of the apparatus has changed. The message is generated if the state of the apparatus has changed and is not generated otherwise. The function of determining if the state of the apparatus has changed includes comparing the state received from the apparatus to a previous state of the apparatus.
[0009] The message is generated using a predefined template by obtaining one or more variables relating to the apparatus and inserting the one or more variables into the template. The state of the apparatus may be included as part of a body of an e-mail message or as part of an attachment to the e-mail message. The state of the apparatus may be included as part of an HTTP command.
[0010] In general, in another aspect, the invention is directed to obtaining a state of an apparatus from a device, such as a controller, embedded in the apparatus. This aspect of the invention features receiving a message that reports the state of the apparatus using a self-describing computer language and extracting the state of the apparatus from the message.
[0011] This aspect of the invention may include one or more of the following features. The self-describing computer language is XML. The state of the apparatus is indicative of an error condition in the apparatus. The error condition is a variable that deviates from an acceptable value or a predetermined range of acceptable values. The state of the apparatus is passed to a customer relationship management system. The message may be included in an HTTP command or may be part of an e-mail.
[0012] In general, in another aspect, the invention features a system that includes first and second devices. The first device includes circuitry that generates a message reporting a state of an apparatus using a self-describing computer language. The second device is in communication with the first device. The second device includes circuitry that receives the electronic mail message from the first device.
[0013] This aspect of the invention may include one or more of the following features. The second device receives the message from the first device and extracts the state of the apparatus from the message. The first device is embedded in the apparatus and the second device is a remote computer. The message may be included in an HTTP command or may be part of an e-mail.
[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 remote computer and an apparatus having an embedded device;
[0016] FIG. 2 shows the format of a tag used to store state variables for the apparatus;
[0017] FIG. 3 is flowchart of a process performed by the embedded device to report the state of the apparatus to the remote computer;
[0018] FIG. 4 is a flowchart of an alternative process performed by the embedded device to report the state of the apparatus to the remote computer;
[0019] FIG. 5 is a flowchart of a process performed by the remote computer to interpret messages received from the embedded device; and
[0020] FIG. 6 is a block diagram of a network containing a remote computer and an apparatus having an embedded device the reports on the state of the apparatus using HTTP commands.
DESCRIPTION
[0021] FIG. 1 shows a network 10. Network 10 includes an apparatus 11 containing an embedded device 17, such as a controller (e.g., a microprocessor). Apparatus 11 is connected to an internal network 12, such as a LAN. A router or modem 14 interfaces internal network 12 to an external network 15, such as the Internet, that runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Connections may be, e.g., via Ethernet, wireless link, or telephone line. External network 15 contains remote computer 16, which may be a server, a personal computer (PC), or any other type of processing device. Other devices (not shown) may be included on internal network 12 and external network 15.
Processing in the Embedded Device
[0022] Apparatus 11 may be any type of device or may be included in any system having functions that are monitored and controlled by embedded device 17. Among other things, embedded device 17 executes software stored in memory 19 to generate and send, to remote computer 16, an e-mail message reporting the state of apparatus 11.
[0023] Software 20 includes an OPC (OLE for Process Control) server program 21, an XML (eXtensible Markup Language) processor program 24, and an e-mail program 25. E-mail program 25 is an SMTP-compliant (Simple Mail Transfer Protocol) program for sending e-mail from embedded device 17 to Internet addresses and for receiving e-mail from the Internet. E-mail program 25 operates as a mail transfer agent (MTA) for e-mail messages arriving at embedded device 17 and a mail delivery agent (MDA) for e-mail messages originating from embedded device 17. Other mail transfer protocols and programs may be also used by embedded device 17 in addition to, or instead of, those noted above.
[0024] XML processor program 24 is a program for generating XML code that reports the state of apparatus 11. XML is a self-describing computer language that defines variables and values relating to those variables. XML is self-describing in the sense that fields in the XML code identify variables and their values in the XML code. The template for XML used to generate an e-mail is as follows:
[0025] <name>temperature</name><value><##temperature##></value>,
[0026] where the “name” field identifies the name of a variable and the “value” field identifies the value of the variable that follows the “name” field. So, for the example given above, the variable is “temperature” and a value (e.g., 33.8) may be inserted for that variable as follows:
[0027] <name>temperature</name><value>33.8</value>.
XML processor program 24 generates XML code having the above syntax from a tag database 22 stored in memory 19.
[0028] Tag database 22 contains tags for use by XML processor program 24 in generating XML code. FIG. 2 shows an example of a format for a tag 26, although other formats may be used. Tag 26 contains a name field 27, a description field 29, a value field 30, a time stamp field 31, and an item identifier (ID) field 32. These fields are used to obtain, identify and store information relating to apparatus 11.
[0029] Name field 27 holds the name of a state variable for apparatus 11, such as “temperature”, and description field 29 provides further identification information, such as “temperature of fluid in a tank”. Value field 30 holds the value of the state variable and time stamp field 31 holds the time that the value in value field 30 was obtained. Value field 30 may include a variant, which is a construct that holds the value as an integer, a real number, a boolean, a character string, or some other type. Item ID field 32 holds an identifier that corresponds to hardware that is being monitored within apparatus 11. The identifier corresponds to a register location or to some other storage area of apparatus 11 that contains the value for field 30. For example, if embedded device 17 is in a robotics system, item ID field 32 might correspond to a register in the robotics system that contains a velocity or position of a robotic arm.
[0030] OPC server program 21 reads item IDs from field 32 and uses those item IDs to read variable values from corresponding hardware storage areas 34. OPC server program 21 implements an industrial automation protocol, such as MODBUS TCP, to communicate with the apparatus hardware. The system is not limited to use with the MODBUS protocol or with OPC server program 21; any drivers or computer programs may be used to read the state variable values from the hardware. Once a state variable value has been read, OPC server program 21 inserts the variable value into field 30 of the appropriate tag.
[0031] FIG. 3 shows a process 36 for reporting the state of apparatus 11 to remote computer 16 using e-mail. In this embodiment, process 36 is implemented by OPC server program 21, XML processor program 24, e-mail program 25, and system software (not shown) executing in embedded device 17. The system software may include an operating system or other programs that control the background operation of embedded device 17.
[0032] Process 36 detects (301) the state of apparatus 11. The state may be indicative of an error condition (described below) within apparatus 11 or it may simply be state variables of apparatus 11 that are obtained at a particular time. To detect the state of apparatus 11, OPC server program 21 polls the hardware in apparatus 11 periodically. To perform this polling, OPC server program 21 obtains (301a) an item ID from tag database 22 and reads (301b) the value of a state variable that corresponds to the item ID from the appropriate hardware storage location. Process 36 may report the value to the remote computer as is or, alternatively, process 36 may use the value to identify and report an error condition in the hardware. A process for reporting error conditions is described below.
[0033] Process 36 generates (302) an e-mail message reporting the value of state variable(s) for apparatus 11. Specifically, XML processor program 24 retrieves both the name of each state variable and the value of the state variable from the appropriate tag(s) in tag database 22. Other variables may also be retrieved from tag database 22 including the time stamp, description, and whatever other variables are stored in tag database 22. Which information is retrieved is pre-set in XML processor program 24. The retrieved variables are used by XML processor program 24 to generate XML code for an e-mail to remote computer 16.
[0034] XML processor program 24 may generate the XML code “on the fly”, meaning without the use of a template. In this case, a blank XML file is populated with the retrieved variables in XML format by XML processor program 24. Alternatively, XML processor program 24 may generate the XML code using a pre-defined and formatted template. The template may be obtained by XML processor program 24, e.g., from memory 19 or a remote storage location (not shown). For example, the template may contain formatting similar to that shown above, namely:
[0035] <name>temperature</name><value><##temperature##></value>.
[0036] To generate the XML code from the template, XML processor program 24 scans through the template and inserts state variable value(s) retrieved from tag database 22, where appropriate. XML processor program 24 may generate the XML code periodically, depending upon how often e-mails are to be sent to the remote computer. Alternatively, tag manager software (not shown) may be included to provide newly-received tag variables to XML processor program 24. In this case, XML processor program 24 generates the XML code when it receives the new tag variables.
[0037] The resulting XML code may be part of the body of an e-mail or it may part of an attachment to an e-mail. The e-mail also contains a unique identifier, such as a code (e.g., serial number or identifier), that identifies embedded device 17 to remote computer 16. E-mail program 25 obtains the XML code from XML processor program 24 and sends it to remote computer 16 as part of the e-mail message. E-mail program 25 obtains the code periodically, depending upon the frequency at which e-mails are to be sent to the remote computer. The frequency is set beforehand in embedded device 17. The address of the remote computer may be registered with e-mail program 25 beforehand. Typically, the address/remote computer will be that of an entity that requires information about apparatus 11. For example, the entity may be a manufacturer of the apparatus, a plant monitoring system, or the like. The e-mail program sends the message to router/modem 14, which transfers it via external network 15 to remote computer 16. Then, the e-mail message is processed as described below.
[0038] The foregoing describes the case where embedded device 17 simply reports the state of apparatus 11 to remote computer 16 periodically. Alternatively, embedded device 17 may report the state to remote computer 16 only when an error condition or “alarm” is detected.
[0039] FIG. 4 shows a process 40 by which embedded device 17 detects error conditions in apparatus 11 and sends an e-mail message to remote computer 16 when an error condition is detected. Process 40 detects (401) the state of apparatus 11, where, as above, “state” refers to tag variable values for apparatus 11. Detection (401) is performed in the same manner as process 36; therefore, a description is omitted here. Once process 36 has obtained the state of apparatus 11, process 36 determines (402) if that state represents an error condition.
[0040] To detect an error condition, process 40 may compare an obtained state variable value to a predetermined acceptable value or a range of predetermined acceptable values. If the state variable value is outside the range of, or deviates considerably from, the acceptable value(s), then process 40 knows that an error condition is present. Alternatively, process 40 may store each state variable value in memory 19 as it is obtained, and compare each newly-received state variable value to one or more stored state variable values. If the new state variable value deviates by more than a predetermined amount from the stored value(s), process 40 knows that an error condition is present/has occurred.
[0041] An error condition may be based on a single state variable value or it may be based on some combination of two or more state variable values. For example, if embedded device 17 is in manufacturing equipment that monitors both a level of fluid in a tank and a temperature of that fluid, an error condition may only be present if both the fluid level and the temperature exceed preset values. In this example, therefore, if only one state variable exceeds its corresponding preset value, then no error condition is present/has occurred.
[0042] If process 40 detects (402) an error condition, process 40 generates (403) an e-mail message and sends (404) the e-mail message to remote computer 16. The functions of generating and sending an e-mail message are performed as described above with respect to process 36; therefore, detailed descriptions are omitted here. When generating the e-mail message, e-mail program 25 may place the state variable(s) that caused the error condition in the “subject” line of the e-mail. If process 40 does not detect (402) an error condition, an e-mail message is not sent, whereafter process 40 returns to 401.
[0043] XML processor program 24 may maintain a log of error conditions in memory 19. This error condition “history” may be provided along with each new e-mail message. The history may relate to a particular state variable or to more than one state variable. For example, if the error condition pertains to temperature, XML processor program 24 may include the error condition history for temperature in the e-mail. If the error condition pertains to both temperature and tank level, XML processor program 24 may include the error condition history for both temperature and tank level in the e-mail. If a template is used to generate the e-mail message, portion(s) of that template may be reserved for error condition history.
[0044] Processes 36 and 40 can be combined to generate an e-mail periodically that reports the state of apparatus 11 to remote computer 16 even if no error conditions have been detected in apparatus 11, and that also flags any error conditions if any have been detected. XML processor program 24 adds an indicator or the like next to state variable values that correspond to error conditions.
[0045] Processes 36 and 40 may be executed by embedded device 17 to monitor and report on any type of state variables in any type of apparatus. For example, processes 36 and 40 may detect state variable values relating to conveyor belt speed, current and/or voltage in electronic devices, tank fluid levels, input/output sensors, and the like. Processes 36 and 40 may detect state variable values through a programmable logic controller (PLC) that is connected to one or more other devices. A PLC includes plug-in cards for each device that obtain and store device state variable values. OPC server program 21 communicates with these plug-in cards to obtain the device state variable values for generating e-mails as described above.
[0046] E-mails generated by processes 36 and 40 report the state of apparatus 11 using a self-describing computer language, such as XML; however, other types of self-describing computer languages may be used. In addition, other text and/or images may be included in the e-mails, if desired and appropriate under the circumstances. Described below is a process that is performed by remote computer 16 to interpret e-mails received from embedded device 17.
Processing in the Remote Computer
[0047] Remote computer 16 contains a controller 41 for executing software stored in memory 42. Among this software is e-mail program 44, XML parser 45, and customer relationship management (CRM) system software 46.
[0048] As in embedded device 17, e-mail program 44 is an SMTP-compliant program for receiving e-mail from embedded device 17 and other such devices. E-mail program 44 operates as a mail transfer agent (MTA) for e-mail messages arriving at remote computer 16 and a mail delivery agent (MDA) for e-mail messages originating from remote computer 16. E-mail program 44 uses the same protocol as e-mail program 25 in embedded device 17.
[0049] XML parser 45 parses XML code in a received e-mail to extract variable values, including an identifier for apparatus 11. XML parser 45 recognizes field names, such as “name” and “value” from above and extracts corresponding state variable values from those fields. That is, XML parser 45 knows the syntax of XML. Knowing this, XML parser 45 is able to extract variable names from the “name” fields, corresponding variable values from the “value” fields, and any other information in the XML code.
[0050] XML parser 45 passes the state variable values, along with appropriate identifiers, to customer relationship management system software 46 or whatever other software or database requires/uses those state variable values.
[0051] FIG. 5 shows how an e-mail from embedded device 17 is processed (43). Once an e-mail has been received (501) from embedded device 17, XML parser 45 extracts (502) the state variable values of apparatus 11 from the e-mail. For example, XML parser 45 may extract tank levels, temperature values, etc., of apparatus 11 monitored by embedded device 17. The state variable values may be indicative of error conditions in apparatus 11, as defined above, or simply state variables for apparatus 11 obtained at a given point in time.
[0052] XML parser 45 passes (503) the state variable values, i.e., the state of apparatus 11, to customer relationship management system software 46. Customer relationship management system software 46 uses these state variable values, e.g., to schedule maintenance for apparatus 11 if necessary, to provide software upgrades to apparatus 11, or for any other purpose. Because the XML code in the e-mail is readable by XML parser 45, reporting and scheduling by customer relationship management system software 46 can be done automatically. It is noted that e-mail program 44 may still forward an e-mail to a customer representative, technician, or the like, particularly if an e-mail contains human-readable text.
[0053] The software on remote computer 16 is not limited to that shown in FIG. 1 . For example, XML parser 45 may be replaced by a parser that is capable of parsing/reading other types of computer code, depending upon the code that is used in the received e-mail. Likewise, the parsed variables can be passed to software other than customer relationship management system software 46. For example, the variables can be stored in a database 47 for later use.
Alternative Embodiment
[0054] Referring to FIG. 6 , a network 60 is shown on which an alternative embodiment of the invention is implemented. Network 60 is identical to network 10, except that e-mail program 25 in apparatus 11 is replaced by Web client 61 and e-mail program 44 in remote computer 16 is replaced by Web server 62. This alternative configuration allows embedded device 17 to transfer messages to remote computer 16 as HTTP commands rather than e-mails.
[0055] The HTTP command may be an HTTP POST command, although other HTTP commands, such as an HTTP GET command, may instead be used. An example of an HTTP POST command that uses XML code to report the status of a fictitious “widget” apparatus is as follows:
POST/CONTROL HTTP/1.1
Host: www.acme.com
Content-Type: text/xml
Content-length: nnn
<?xml version=“1.0”?>
<root xmlns=“urn:schemas-upnp-org:device-1-0”>
-
- [0056] <specVersion>
- [0057] <major>1</major>
- [0058] <minor>0</minor>
- [0059] </specVersion>
- [0060] <device>
- [0061] <deviceType>urn:www-acme-com:device:Widget:3</deviceType>
- [0062] <friendlyName>Widget</friendlyName>
- [0063] <manufacturer>Acme Industries</manufacturer>
- [0064] <modelName>Widget</modelName>
- [0065] <modelNumber>3</modelNumber>
- [0066] <serialNumber>53266D</serialNumber>
- [0067] <UDN>uuid:4A89EA70-73B4-11d4-80DF-0050DAB7BAC5</UDN>
- [0068] </device>
</root>
<parameters> - [0069] <Airflow xsd:type=“integer”>378</Airflow>
- [0070] <Humidity xsd:type=“double”>46.7</Humidity>
- [0071] <Motor xsd:type=“integer”>1500</Motor>
- [0072] <Vent xsd:type=“integer”>4</Vent>
</parameters>
<alarms> - [0073] <Temperature>
- [0074] <description>Room temperature is above 83F</description>
- [0075] <severity>300</severity>
- [0076] <status>high</status>
- [0077] </Temperature>
</alarms>
- [0056] <specVersion>
[0078] 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 above POST command, the “manufacturer” field identifies a manufacturer, e.g., “Acme Industries”, and is delineated by “<manufacturer>” to indicate the start of the field and “</manufacturer>” to indicate the end of the field. XML is used in the HTTP command because it can be generated, parsed and read relatively easily by XML parser 45.
[0079] The HTTP POST command includes data identifying apparatus 11. This data 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. In the example post command, this data is formatted as:
[0080] <friendlyName>Widget</friendlyName>
[0081] <manufacturer>Acme Industries</manufacturer>
[0082] <modelName>Widget</modelName>
[0083] <modelNumber>3</modelNumber>
[0084] <serialNumber>53266D</serialNumber>
[0085] <UDN>uuid:4A89EA70-73B4-11d4-80DF-0050DAB7BAC5</UDN>
[0086] The HTTP POST command also provides the state of apparatus 11. The state includes operational parameters and alarm conditions for apparatus 11. In the above HTTP POST command, these are formatted as follows:
-
- [0087] <parameters>
- [0088] <Airflow xsd:type=“integer”>378</Airflow>
- [0089] <Humidity xsd:type=“double”>46.7</Humidity>
- [0090] <Motor xsd:type=“integer”>1500</Motor>
- [0091] <Vent xsd:type=“integer”>4</Vent>
- [0092] </parameters>
- [0093] <alarms>
- [0094] <Temperature>
- [0095] <description>Room temperature is above 83F</description>
- [0096] <severity>300</severity>
- [0097] <status>high</status>
- [0098] </Temperature>
- [0094] <Temperature>
- [0099] </alarms>
Thus, the state of the widget includes information on its airflow, humidity, motor and vent settings, temperature, severity of the temperature, and temperature status. Different information from that shown may be included in the HTTP POST command.
- [0087] <parameters>
[0100] Referring back to FIGS. 3 , 4 and 5, in this embodiment the operation of processes 36, 40 and 43 is identical to that described above, except that, in all steps, the e-mail message is replaced by an HTTP command. In apparatus 11, the HTTP command is generated by Web client 61 based on data provided by XML processor 24. This XML data is the same as that used above with e-mail program 25. Embedded device 17 sends the HTTP command to remote computer 16, where it is received by Web server 62 and then processed by XML parser 45. Thereafter, processing proceeds as above.
Architecture
[0101] Processes 36, 40 and 43 are not limited to use with the hardware/software configuration of FIG. 1 ; they may find applicability in any computing or processing environment. Processes 36, 40 and 43 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.
[0102] Processes 36, 40 and 43 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.
[0103] 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.
[0104] 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 36, 40 and 43.
[0105] Processes 36, 40 and 43 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 36, 40 and 43.
[0106] Other embodiments not described herein are also within the scope of the following claims. For example, e-mail or http messages sent from apparatus 11 to remote computer 16 may be queued (e.g., stored in memory 19) and then retrieved and sent out at a later time. Queuing messages reduces message loss resulting from intermittent system failures.
Claims
What is claimed is:
1. A method performed by a device associated with an apparatus to report a state of the apparatus to a remote computer, the device having a local network address that is unknown to the remote computer, the method comprising:
detecting the state of the apparatus, wherein detecting is performed by monitoring variables associated with the apparatus, wherein monitoring comprises (a) obtaining identifiers for variables associated with the apparatus, the identifiers corresponding to storage locations for the apparatus, and (b) reading the variables from the storage locations;
generating a message that reports the state of the apparatus to the remote computer, the message comprising a HyperText Transfer Protocol (HTTP) command, the message using eXtensible Markup Language (XML) to report the state, and the message containing a code that is unique to the device or apparatus, wherein generating is performed periodically or in response to a deviation in the state, and wherein generating comprises obtaining XML tags using the identifiers and incorporating the variables into fields delimited by XML tags that correspond to the variables; and
sending the message comprising the HTTP command to the remote computer, the message comprising a one-way communication to the remote computer, wherein sending comprises sending the message once the message is generated or queuing the message and sending the message at a later time.
2. The method of claim 1, wherein detecting the state comprises reading the variables periodically from the storage locations.
3. The method of claim 1, further comprising determining the deviation in the state.
4. The method of claim 3, wherein determining comprises comparing the state to a previous state of the apparatus.
5. The method of claim 1, wherein the XML tags are part of a predefined template, the message being generated by:
inserting the one or more variables into the template.
6. The method of claim 1, wherein the device is embedded in the apparatus.
7. The method of claim 1, wherein the message includes past states of the apparatus.
8. The method of claim 1, wherein the HTTP command comprises a POST command.
9. The method of claim 1, wherein the message comprises one or more of the following: data identifying a type of the device, a common name for the device, a manufacturer of the device, a model name of the device, a model number of the device, a serial number of the device, and a universal unique identifier for the device.
10. The method of claim 1, wherein the state comprises both an error condition and a measurement associated with the apparatus that is not an error condition.
11. The method of claim 1, wherein the storage locations comprise register locations corresponding to hardware associated with the apparatus.
12. One or more machine-readable media comprising instructions for execution by a device associated with an apparatus to report a state of the apparatus to a remote computer, the device having a local network address that is unknown to the remote computer, the instructions for causing the device to:
detect the state of the apparatus, wherein detecting is performed by monitoring variables associated with the apparatus, wherein monitoring comprises (a) obtaining identifiers for variables associated with the apparatus, the identifiers corresponding to storage locations for the apparatus, and (b) reading the variables from the storage locations;
generate a message that reports the state of the apparatus to the remote computer, the message comprising a HyperText Transfer Protocol (HTTP) command, the message using eXtensible Markup Language (XML) to report the state, the message containing a code that is unique to the device or apparatus, wherein generating is performed periodically or in response to a deviation in the state, and wherein generating comprises obtaining XML tags using the identifiers and incorporating the variables into fields delimited by XML tags that correspond to the variables; and
send the message comprising the HTTP command to the remote computer, the message comprising a one-way communication to the remote computer, wherein sending comprises sending the message once the message is generated or queuing the message and sending the message at a later time.
13. The one or more machine-readable media of claim 12, wherein detecting the state comprises reading the variables periodically from the storage locations.
14. The one or more machine-readable media of claim 12, further comprising instructions that cause the device to:
determine the deviation in the state.
15. The one or more machine-readable media of claim 14, wherein determining comprises comparing the state to a previous state of the apparatus.
16. The one or more machine-readable media of claim 12, wherein the XML tars are part of a predefined template, the message being generated by:
inserting the one or more variables into the template.
17. The one or more machine-readable media of claim 12, wherein the device is embedded in the apparatus.
18. The one or more machine-readable media of claim 12, wherein the HTTP command comprises a POST command.
19. The one or more machine-readable media of claim 12, wherein the message comprises one or more of the following: data identifying a type of the device, a common name for the device, a manufacturer of the device, a model name of the device, a model number of the device, a serial number of the device, and a universal unique identifier for the device.
20. The one or more machine-readable media of claim 12, wherein the state comprises both an error condition and a measurement associated with the apparatus that is not an error condition.
21. The one or more machine-readable media of claim 12, wherein the storage locations comprise register locations corresponding to hardware associated with the apparatus.
22. A device associated with an apparatus for reporting a state of the apparatus to a remote computer, the device having a local network address that is unknown to the remote computer, the device comprising circuitry configured to:
detect the state of the apparatus, wherein detecting is performed by monitoring variables associated with the apparatus, wherein monitoring comprises (a) obtaining identifiers for variables associated with the apparatus, the identifiers corresponding to storage locations for the apparatus, and (b) reading the variables from the storage locations;
generate a message that reports the state of the apparatus to the remote computer, the message comprising a HyperText Transfer Protocol (HTTP) command, the message using eXtensible Markup Language (XML) to report the state, and the message containing a code that is unique to the device or apparatus, wherein generating is performed periodically or in response to a deviation in the state, and wherein generating comprises obtaining XML tags using the identifiers and incorporating the variables into fields delimited by XML tags that correspond to the variables; and
send the message comprising the HTTP command to the remote computer, the message comprising a one-way communication to the remote computer, wherein sending comprises sending the message once the message is generated or queuing the message and sending the message at a later time.
23. The device of claim 22, wherein detecting the state comprises reading the variables periodically from the storage locations.
24. The device of claim 22, wherein the circuitry is configured to determine if the state of the apparatus has changed.
25. The device of claim 24, wherein determining if the state of the apparatus has changed comprises comparing the state to a previous state of the apparatus.
26. The device of claim 22, wherein the XML tags are part of a predefined template, the message being generated by:
inserting the one or more variables into the template.
27. The device of claim 22, wherein the circuitry comprises memory which stores executable instructions and a processor which executes the instructions.
28. The device of claim 22, wherein the circuitry comprises one or more of an application-specific integrated circuit and a programmable gate array.
29. The device of claim 22, wherein the device is embedded in the apparatus.
30. The device of claim 22, wherein the HTTP command comprises a POST command.
31. The device of claim 22, wherein the message comprises one or more of the following: data identifying a type of the device, a common name for the device, a manufacturer of the device, a model name of the device, a model number of the device, a serial number of the device, and a universal unique identifier for the device.
32. The device of claim 22, wherein the state comprises both an error condition and a measurement associated with the apparatus that is not an error condition.
33. The device of claim 22, wherein the storage locations comprise register locations corresponding to hardware associated with the apparatus.
34. A system comprising:
a first device comprising circuitry to generate a message reporting a state of an apparatus,
the message comprising a HyperText Transfer Protocol (HTTP) command, the message using eXtensible Markup Language (XML) to report the state, and the message containing an identifier that is unique to the apparatus,
the first device having a local network address that is unknown to a second device,
wherein reporting is performed following monitoring of variables associated with the apparatus,
wherein monitoring comprises (a) obtaining identifiers for variables associated with the apparatus, the identifiers corresponding to storage locations for the apparatus, and (b) reading the variables from the storage locations,
wherein generating is performed periodically or in response to a deviation in the state, and wherein generating comprises obtaining XML tags using the identifiers and incorporating the variables into fields delimited by XML tags that correspond to the variables, and
the message comprising a one-way communication to the remote computer, the first device sending the message once the message is generated or queuing the message and sending the message at a later time; and
the second device comprising circuitry to receive the message from the first device and to relay content from the message to an external system.
35. The system of claim 34, wherein the circuitry in the second device is configured to extract the state of the apparatus from the message.
36. The system of claim 34, wherein the first device is embedded in the apparatus and the second device comprises a remote computer.
37. The system of claim 34, wherein the message includes a history log providing past states of the apparatus.
Patent Citations (306)
| 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 | Examiner |
| 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. | Examiner |
| 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. | Examiner |
| 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 | Perholtz 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 | Examiner |
| 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 et al. | 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 | Crater 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 |
| US6023507(A) | 2000-02-01 | Wookey | 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 |
| US6088718(A) | 2000-07-01 | Altschuler et al. | Examiner |
| 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 |
| 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. | Applicant |
| US6286059(B1) | 2001-09-01 | Sugiura | Applicant |
| US6292828(B1) | 2001-09-01 | Williams | Examiner |
| US6304895(B1) | 2001-10-01 | Schneider 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. | Examiner |
| US6356933(B1) | 2002-03-01 | Mitchell et al. | Examiner |
| US6356949(B1) | 2002-03-01 | Katsandres et al. | Applicant |
| US6368284(B1) | 2002-04-01 | Bardy | Applicant |
| US6370582(B1) | 2002-04-01 | Lim et al. | Applicant |
| US6377162(B1) | 2002-04-01 | Delestienne et al. | Applicant |
| US6381557(B1) | 2002-04-01 | Babula et al. | Applicant |
| US6397212(B1) | 2002-05-01 | Biffar | Examiner |
| US6405310(B1) | 2002-06-01 | Simpson | Applicant |
| US6406426(B1) | 2002-06-01 | Reuss et al. | Applicant |
| US6415023(B1) | 2002-07-01 | Iggulden | Applicant |
| US6426798(B1) | 2002-07-01 | Yeung | Applicant |
| US6430711(B1) | 2002-08-01 | Sekizawa et al. | Applicant |
| US6434572(B1) | 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 |
| US6471521(B1) | 2002-10-01 | Dornbush et al. | Examiner |
| US6477117(B1) | 2002-11-01 | Narayanaswami et al. | Applicant |
| US6487513(B1) | 2002-11-01 | Eastvold et al. | Applicant |
| US6494831(B1) | 2002-12-01 | Koritzinsky | Applicant |
| US6510350(B1) | 2003-01-01 | Steen et al. | Examiner |
| US6523063(B1) | 2003-02-01 | Miller et al. | Examiner |
| US6523130(B1) | 2003-02-01 | Hickman et al. | Applicant |
| US6529848(B1) | 2003-03-01 | Sone | Applicant |
| US6549612(B1) | 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. | Applicant |
| US6564227(B1) | 2003-05-01 | Sakakibara et al. | Applicant |
| US6581092(B1) | 2003-06-01 | Motoyama et al. | Examiner |
| 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(B1) | 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. | Applicant |
| US6651190(B1) | 2003-11-01 | Worley et al. | Applicant |
| US6654720(B1) | 2003-11-01 | Graham et al. | Applicant |
| US6654726(B1) | 2003-11-01 | Hanzek | Examiner |
| US6670810(B1) | 2003-12-01 | Duncan et al. | Applicant |
| US6681349(B1) | 2004-01-01 | Sekizawa | Applicant |
| US6686838(B1) | 2004-02-01 | Rezvani et al. | Applicant |
| US6691106(B1) | 2004-02-01 | Sathyanarayan | Examiner |
| US6710893(B1) | 2004-03-01 | Hou et al. | Applicant |
| US6711618(B1) | 2004-03-01 | Danner et al. | Examiner |
| US6757714(B1) | 2004-06-01 | Hansen | Examiner |
| US6785015(B1) | 2004-08-01 | Smith et al. | Examiner |
| US6834298(B1) | 2004-12-01 | Singer et al. | Applicant |
| US6857013(B1) | 2005-02-01 | Ramberg et al. | Applicant |
| US6904593(B1) | 2005-06-01 | Fong et al. | Examiner |
| US2002/0006790(A1) | 2002-01-01 | Blumeenstock et al. | Applicant |
| US2002/0038320(A1) | 2002-03-01 | Brook | Applicant |
| US2002/0064138(A1) | 2002-05-01 | Saito et al. | Applicant |
| US2003/0118353(A1) | 2003-06-01 | Baller | 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/21336 | 1999-04-01 | Applicant | |
| WO99/21336 | 1999-04-01 | Applicant | |
| WO99/57649 | 1999-11-01 | Applicant | |
| WO9957649 | 1999-11-01 | Applicant | |
| WO99/57837 | 1999-11-01 | Applicant | |
| WO9957838 | 1999-11-01 | Applicant | |
| WO99/57838 | 1999-11-01 | Applicant | |
| WO/23894 | 2000-04-01 | Applicant | |
| WO2/10919 | 2002-02-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 (100)
- webMethods B2B Whitepaper; www.cs.wisc.edu/˜vganti/papers/b2b—wpB2Bintegration.html.Examiner
- virtual reality transfer protocol (vrtp); www.stl.nps.navy.mil/˜brutzman/vrtp.Examiner
- The Simple Times, vol. 7, No. 1, Mar. 1999; www.simple-times.org/pub/simple-times/issues/7-1.html.Examiner
- Math Markup Language (Chapter 4); www.w3.org/TR/REC-MathML/chap4—4.html.Examiner
- Memphis Educational Computer Connectivity Alliance (MECCA) www.mecca.org/˜ltague/nsfnocostextension.html.Examiner
- EBITS: Electronic Business & Information Technology for Society Research Consortium www.cs.dartmouth.edu/˜makedon/cs188/proposal.html.Examiner
- Distributed and scalable XML document processing architecture for E-commerce systems Cheung, D.; Lee, S.D.; Lee, T.; Song, W.; Tan, C.J.; Advanced Issues of E-Commerce and Web-Based Information Systems, 2000. WECWIS 2000. Second International Workshop on Jun. 8-9, 2000, pp. 152-157.Examiner
- A knowledge sharing and collaboration system model based on Internet Wu Gangshan; Huang Yuan; Shian-Shyong Tseng; Zhang Fuyan; Systems, Man, and Cybernetics, 1999. IEEE SMC '99 Conference Proceedings. 1999 IEEE International Conference on vol. 2, Oct. 12-15, 1999 pp. 148-152 vol. 2.Examiner
- A Evolution of Workflow Standards, IEEE 1999.Examiner
- Active hypertext for distributed Web applications Koppen, E.; Neumann, G.; Enabling Technologies: Infrastructure for Collaborative Enterprises, 1999. (WET ICE '99) Proceedings. IEEE 8th International Workshops on Jun. 16-18, 1999 pp. 297-302.Examiner
- http://www.upnp.org/download/UPnPDA10—20000613.htm (pp. 1-52).Applicant
- Office Action dated Nov. 17, 2003; from U.S. Appl. No. 09/627,201.Applicant
- CORBA and XML Integration in Enterprise Systems—Ennis (2000); www.iona.com/info/techcenter/ecoop2000apr17.pdf.Applicant
- Implementing Incremental Code Migration with XML, Emmerich, W. et al, IEEE, 4-11, Jun. 2000.Applicant
- XML-based Data System for Earth Science Applications, Suresh, R et al.; IEEE 2000 Internation, vol. 3, pp. 242-28, Jul. 2000.Applicant
- Office Action dated Jan. 29, 2004 in counterpart European Application No. 01 955 993.9-2211.Applicant
- Search Report from EP Application No. 01955993.9, dated Dec. 16, 2004.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
- “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/˜ltague/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 Solutioins,” 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, 24×7, HealthTech Publishing Company, Inc.Applicant
- Wigget, Jeremy, “Intraview: Roger Eastvold of Orasis Inc.,” 24×7, 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 Acces Protocol (SOAP) 1.1 Document No. XP002250270, May 8, 2000.Applicant
- XP-002253876, c:\epodata\sea\eplogf\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 Quarterly 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
- Summons to attend oral proceedings in corresponding European Application No. 01955993.9 dated Oct. 31, 2005.Applicant
- Result of Consultation of Nov. 24, 2005 and Nov. 25, 2005 from corresponding European Application No. 01955993.Applicant
- Submission in German dated Nov. 25, 2005 from corresponding European Application No. 01955993.9.Applicant
- Annex to EPO Form 2004 with claims for grant in Eurpoean Application No. 01955993.9.Applicant
- Oral Proceeding Minutes with European Application No. 01955993.9.Applicant
- Communication dated Apr. 26, 2005 in European Application No. 01955993.9.Applicant
- International Search Report PCT/US01/23651.Applicant
- Office Action dtd Jun. 22, 2004 from EPO App. 01996048.3.Applicant
- Office Action dtd Aug. 5, 2004 from EPO App. 01955993.9.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
- http://www.linuxjournal.com/article.php?sid=4195.Applicant
- “RomWebClient Embedded HTTP client 1-61 Toolkit” ALLEGROSOFT, 'Online! Jul. 9, 2000 (2000-07-091, 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
- 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
- Allegro Software product release 1-61 overview Greenhills Software Inc., ‘Online! Jun. 10, 2002 (2002-06-lo), pp. 1-1, XPOO2201939 Retrieved from the Internet: URL: http://www.ghs. com/partners/allegro/>’ retrieved on Jun. 10, 2002! the whole document.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