Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20040177124 A1
Publication typeApplication
Application numberUS 10/805,012
Publication dateSep 9, 2004
Filing dateMar 19, 2004
Priority dateJul 28, 2000
Also published asUS6757714
Publication number10805012, 805012, US 2004/0177124 A1, US 2004/177124 A1, US 20040177124 A1, US 20040177124A1, US 2004177124 A1, US 2004177124A1, US-A1-20040177124, US-A1-2004177124, US2004/0177124A1, US2004/177124A1, US20040177124 A1, US20040177124A1, US2004177124 A1, US2004177124A1
InventorsJames Hansen
Original AssigneeHansen James R.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Reporting the state of an apparatus to a remote computer
US 20040177124 A1
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 an electronic mail message that reports the state using a self-describing computer language, and sends the electronic mail message to the remote computer. The remote computer receives the electronic mail message and extracts the state of the embedded device from the message.
Images(6)
Previous page
Next page
Claims(58)
What is claimed is:
1. A computer-implemented method for using a device embedded in an apparatus to report the state of the apparatus to a remote computer, comprising:
detecting the state of the apparatus;
generating an electronic mail message that reports the state of the apparatus using a self-describing computer language; and
sending the electronic mail message to the remote computer.
2. The method of claim 1, wherein the state is indicative of an error condition in the apparatus.
3. The method of claim 2, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
4. The method of claim 1, wherein detecting the state comprises receiving the state from the apparatus.
5. The method of claim 1, wherein detecting the state comprises retrieving the state periodically from the apparatus.
6. The method of claim 1, wherein detecting the state comprises:
obtaining an identifier for the apparatus, the identifier relating to the state of the apparatus; and
reading the state from the apparatus using the identifier.
7. The method of claim 1, further comprising:
determining if the state of the apparatus has changed;
wherein the electronic mail message is generated if the state of the apparatus has changed.
8. The method of claim 7, wherein determining comprises comparing the state received from the apparatus to a previous state of the apparatus.
9. The method of claim 1, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
10. The method of claim 1, wherein the electronic mail message is generated using a predefined template, the electronic mail message being generated by:
obtaining one or more variables relating to the apparatus; and
inserting the one or more variables into the template.
11. The method of claim 1, wherein the state of the apparatus is included as part of a body of the electronic mail message.
12. The method of claim 1, wherein the state of the embedded device is included as part of an attachment to the electronic mail message.
13. A computer-implemented method for obtaining a state of an apparatus from a device embedded in the apparatus, comprising:
receiving an electronic mail message that reports the state of the apparatus using a self-describing computer language; and
extracting the state of the apparatus from the electronic mail message.
14. The method of claim 13, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
15. The method of claim 13, wherein the state is indicative of an error condition in the apparatus.
16. The method of claim 15, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
17. The method of claim 13, further comprising passing the state of the apparatus to a customer relationship management system.
18. A computer program stored on a computer-readable medium for reporting the state of an apparatus to a remote computer, the computer program comprising instructions that cause an embedded device in the apparatus to:
detect the state of the apparatus;
generate an electronic mail message that reports the state of the apparatus using a self-describing computer language; and
send the electronic mail message to the remote computer.
19. The computer program of claim 18, wherein the state is indicative of an error condition in the apparatus.
20. The computer program of claim 19, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
21. The computer program of claim 18, wherein detecting the state comprises receiving the state from the apparatus.
22. The computer program of claim 18, wherein detecting the state comprises retrieving the state periodically from the apparatus.
23. The computer program of claim 18, wherein detecting the state comprises:
obtaining an identifier for the apparatus, the identifier relating to the state of the apparatus; and
reading the state from the apparatus using the identifier.
24. The computer program of claim 18, further comprising instructions that cause the embedded device to:
determine if the state of the apparatus has changed;
wherein the electronic mail message is generated if the state of the apparatus has changed.
25. The computer program of claim 24, wherein determining comprises comparing the state received from the apparatus to a previous state of the apparatus.
26. The computer program of claim 18, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
27. The computer program of claim 18, wherein the electronic mail message is generated using a predefined template, the electronic mail message being generated by:
obtaining one or more variables relating to the apparatus; and
inserting the one or more variables into the template.
28. The computer program of claim 18, wherein the state of the apparatus is included as part of a body of the electronic mail message.
29. The computer program of claim 18, wherein the state of the apparatus is included as part of an attachment to the electronic mail message.
30. A computer program stored on a computer-readable medium for obtaining a state of an apparatus from a device embedded in the apparatus, the computer program comprising instructions that cause a processor to:
receive an electronic mail message that reports the state of the apparatus using a self-describing computer language; and
extract the state of the apparatus from the electronic mail message.
31. The computer program of claim 30, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
32. The computer program of claim 30, wherein the state is indicative of an error condition in the apparatus.
33. The computer program of claim 32, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
34. The computer program of claim 30, further comprising instructions that cause the processor to pass the state of the apparatus to a customer relationship management system.
35. A device embedded in an apparatus for reporting the state of an apparatus to a remote computer, the embedded device comprising circuitry which:
detects the state of the apparatus;
generates an electronic mail message that reports the state of the apparatus using a self-describing computer language; and
sends the electronic mail message to the remote computer.
36. The device of claim 35, wherein the state is indicative of an error condition in the apparatus.
37. The device of claim 36, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
38. The device of claim 35, wherein detecting the state comprises receiving the state from the apparatus.
39. The device of claim 35, wherein detecting the state comprises retrieving the state periodically from the apparatus.
40. The device of claim 35, wherein detecting the state comprises:
obtaining an identifier for the apparatus, the identifier relating to the state of the apparatus; and
reading the state from the apparatus using the identifier.
41. The device of claim 35, wherein:
the circuitry determines if the state of the apparatus has changed; and
the electronic mail message is generated if the state of the apparatus has changed.
42. The device of claim 41, wherein determining comprises comparing the state received from the apparatus to a previous state of the apparatus.
43. The device of claim 35, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
44. The device of claim 35, wherein the electronic mail message is generated using a predefined template, the electronic mail message being generated by:
obtaining one or more variables relating to the apparatus; and
inserting the one or more variables into the template.
45. The device of claim 35, wherein the state of the apparatus is included as part of a body of the electronic mail message.
46. The device of claim 35, wherein the state of the apparatus is included as part of an attachment to the electronic mail message.
47. The device of claim 35, wherein the circuitry comprises a memory which stores executable instructions and a processor which executes the instructions.
48. The device of claim 35, wherein the circuitry comprises one or more of an application-specific integrated circuit and a programmable gate array.
49. A first apparatus for obtaining a state of a second apparatus from a device embedded in the second apparatus, the first apparatus comprising circuitry which:
receives an electronic mail message that reports the state of the second apparatus using a self-describing computer language; and
extracts the state of the second apparatus from the electronic mail message.
50. The first apparatus of claim 49, wherein the self-describing computer language comprises eXtensible Markup Language (XML).
51. The first apparatus of claim 49, wherein the state is indicative of an error condition in the second apparatus.
52. The first apparatus of claim 51, wherein the error condition comprises a variable that deviates from an acceptable value or a predetermined range of acceptable values.
53. The first apparatus of claim 49, wherein the circuitry passes the state of the second apparatus to a customer relationship management system.
54. The first apparatus of claim 49, wherein the circuitry comprises a memory which stores executable instructions and a processor which executes the instructions.
55. The first apparatus of claim 49, wherein the circuitry comprises one or more of an application-specific integrated circuit and a programmable gate array.
56. A system comprising:
a first device comprising circuitry which generates an electronic mail message reporting a state of an apparatus using a self-describing computer language, and
a second device, in communication with the first device, the second device comprising circuitry which receives the electronic mail message from the first device.
57. The system of claim 56, wherein the circuitry in the second device extracts the state of the apparatus from the electronic mail message.
58. The system of claim 56, wherein the first device is embedded in the apparatus and the second device comprises a remote computer.
Description
BACKGROUND

[0001] 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.

[0002] 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.

[0003] 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

[0004] 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 an e-mail message that reports the state of the apparatus using a self-describing computer language, and sending the e-mail message to the remote computer. An example of a self-describing computer language is eXtensible Markup Language (XML).

[0005] Using e-mail, 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.

[0006] 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.

[0007] This aspect of the invention may also include determining if the state of the apparatus has changed. The e-mail 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.

[0008] The e-mail 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 the e-mail message or as part of an attachment to the e-mail message.

[0009] 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 an e-mail message that reports the state of the apparatus using a self-describing computer language and extracting the state of the apparatus from the e-mail message.

[0010] 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.

[0011] In general, in another aspect, the invention features a system that includes first and second devices. The first device includes circuitry that generates an electronic mail 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.

[0012] This aspect of the invention may include one or more of the following features. The second device receives the e-mail message from the first device and extracts the state of the apparatus from the e-mail message. The first device is embedded in the apparatus and the second device is a remote computer.

[0013] Other features and advantages of the invention will become apparent from the following description, including the claims and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014]FIG. 1 is a block diagram of a network containing a remote computer and an apparatus having an embedded device;

[0015]FIG. 2 shows the format of a tag used to store state variables for the apparatus;

[0016]FIG. 3 is flowchart of a process performed by the embedded device to report the state of the apparatus to the remote computer through e-mail;

[0017]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 through e-mail; and

[0018]FIG. 5 is a flowchart of a process performed by the remote computer to interpret e-mail messages received from the embedded device.

DESCRIPTION

[0019]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 or a wireless link. External network 15 contains remote computer 16, which may be server, 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.

[0020] Processing in the Embedded Device

[0021] 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.

[0022] 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.

[0023] 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:

<name>temperature</name><value><##temperature##></value>,

[0024] 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:

<name>temperature</name><value>33.8</value>.

[0025] XML processor program 24 generates XML code having the above syntax from a tag database 22 stored in memory 19.

[0026] 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.

[0027] Name field 27 holds the name of a state variable for apparatus 11, such as “temperatures”, 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.

[0028] 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.

[0029]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.

[0030] 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 (301 a) an item ID from tag database 22 and reads (301 b) 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.

[0031] 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.

[0032] 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:

<name>temperature</name><value><##temperature##></value>.

[0033] 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.

[0034] 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, 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. There, the e-mail message is processed in the manner is described below.

[0035] 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.

[0036]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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] Processing in the Remote Computer

[0045] 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.

[0046] 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.

[0047] 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.

[0048] XML parser 45 passes the state variable values, along with appropriate identifiers, to customer relationship management system software 46 or whatever other software requires/uses those state variable values.

[0049]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.

[0050] 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.

[0051] 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.

[0052] Architecture

[0053] 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.

[0054] 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.

[0055] 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.

[0056] Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable 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.

[0057] 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.

[0058] Other embodiments not described herein are also within the scope of the following claims.

Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7424736Mar 10, 2004Sep 9, 2008Combrio, Inc.Method for establishing directed circuits between parties with limited mutual trust
US7996767 *Aug 14, 2007Aug 9, 2011Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd.System and method for generating electronic patent application files
US8219853 *May 15, 2008Jul 10, 2012Siemens AktiengesellschaftMethod for localizing faulty hardware components and/or system errors within a production plant
US8543697Jul 21, 2006Sep 24, 2013Research In Motion LimitedSystem and method for communicating state management between a browser user-agent and a server
US8635254Aug 8, 2003Jan 21, 2014Axeda CorporationMaintaining independent states for multiple web browser instances
US8959200Jun 29, 2009Feb 17, 2015Ortho-Clinical Diagnostics, Inc.Event-based communication in a clinical diagnostic analyzer
WO2007009256A2 *Jul 21, 2006Jan 25, 2007Research In Motion LtdA method for communicating state information between a server and a mobile device browser with version handling
WO2009109684A1 *Feb 27, 2009Sep 11, 2009Media Patents, S. L.Method for monitoring or managing devices connected to a data network
Classifications
U.S. Classification709/206, 714/E11.173, 714/E11.179
International ClassificationG06F11/30, G06F11/273
Cooperative ClassificationG06F11/3013, G06F11/3068, G06F2201/875, G06F11/3086, G06F11/2294
European ClassificationG06F11/22R, G06F11/30R3, G06F11/30A3, G06F11/30R1
Legal Events
DateCodeEventDescription
Jan 28, 2005ASAssignment
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC., MASSACHUSET
Free format text: CHANGE OF NAME;ASSIGNOR:EMATION, INC.;REEL/FRAME:015634/0698
Effective date: 20020211
Jul 19, 2005ASAssignment
Owner name: JMI EQUITY FUND V (AI), L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16274/846
Owner name: JMI EQUITY FUND V, L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16274/846
Owner name: JMI EQUITY FUND V, L.P., MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Owner name: JMI EQUITY FUND V (AI), L.P., MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Owner name: JMI EQUITY FUND V (AI), L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16274/846
Effective date: 20050708
Owner name: JMI EQUITY FUND V, L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16274/846
Effective date: 20050708
Owner name: JMI EQUITY FUND V, L.P., MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Owner name: JMI EQUITY FUND V (AI), L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Owner name: JMI EQUITY FUND V, L.P.,MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Owner name: JMI EQUITY FUND V (AI), L.P., MARYLAND
Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846
Effective date: 20050708
Sep 19, 2005ASAssignment
Owner name: LAURUS MASTER FUND, LTD.,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16551/813
Owner name: LAURUS MASTER FUND, LTD.,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16551/813
Effective date: 20050831
Owner name: LAURUS MASTER FUND, LTD., NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016551/0813
Effective date: 20050831
Owner name: LAURUS MASTER FUND, LTD., NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016551/0813
Effective date: 20050831
Owner name: LAURUS MASTER FUND, LTD.,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016551/0813
Effective date: 20050831
Dec 8, 2005ASAssignment
Owner name: AXEDA IP, INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Owner name: AXEDA SYSTEMS INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC.,MASSACHUSETT
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Owner name: AXEDA IP, INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Effective date: 20051202
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC.,MASSACHUSETT
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Effective date: 20051202
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC.,MASSACHUSETT
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC., MASSACHUSET
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA IP, INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA SYSTEMS INC., MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA IP, INC., MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA IP, INC., MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA SYSTEMS INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16871/43
Effective date: 20051202
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC., MASSACHUSET
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA SYSTEMS INC.,MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Owner name: AXEDA SYSTEMS INC., MASSACHUSETTS
Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043
Effective date: 20051202
Dec 9, 2005ASAssignment
Owner name: AXEDA CORPORATION,MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16875/827
Owner name: AXEDA CORPORATION, MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016875/0827
Effective date: 20051202
Owner name: AXEDA CORPORATION,MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:16875/827
Effective date: 20051202
Owner name: AXEDA CORPORATION,MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016875/0827
Effective date: 20051202
Owner name: AXEDA CORPORATION, MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016875/0827
Effective date: 20051202
Oct 24, 2006ASAssignment
Owner name: SILICON VALLEY BANK,CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:18420/790
Owner name: SILICON VALLEY BANK, CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:018420/0790
Effective date: 20061011
Owner name: SILICON VALLEY BANK, CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:018420/0790
Effective date: 20061011
Owner name: SILICON VALLEY BANK,CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;US-ASSIGNMENT DATABASE UPDATED:20100203;REEL/FRAME:18420/790
Effective date: 20061011
Owner name: SILICON VALLEY BANK,CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:018420/0790
Effective date: 20061011
Jul 16, 2012ASAssignment
Owner name: AXEDA CORPORATION, MASSACHUSETTS
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:028558/0744
Effective date: 20120713
Jul 17, 2012ASAssignment
Owner name: AXEDA CORPORATION, MASSACHUSETTS
Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MMV CAPITAL PARTNERS INC.;REEL/FRAME:028563/0446
Effective date: 20120713