Retrieving data from a server

Abstract

A system includes a server and a controller embedded in a device. Both the server and the embedded controller are capable of communicating over a computer network. The embedded controller sends a command to the server over the computer network that identifies an instance of the device. In response, the server identifies the instance of the device based on the command, retrieves data that is specific to the instance of the device, and sends the data to the embedded controller over the computer network.

Description

BACKGROUND

This invention relates to a controller embedded in a device (an “embedded controller”) that retrieves data from a remote server for a specific instance of the device.

A device may contain an embedded controller, such as a microprocessor, to monitor and control its operation. Any type of device may have an embedded controller, including, but not limited to, home appliances, such as washing machines, dishwashers, and televisions, and manufacturing equipment, such as robotics, conveyors and motors.

Embedded controllers, also referred to as “embedded devices”, are often connected to an internal network, such as a local area network (LAN), with an interface to the Internet. Other devices on the internal network may communicate with the embedded controllers over the internal network. However, the embedded controllers are not generally addressable from the Internet. To address this problem, the embedded device may initiate communications with an addressable external device. That is, the embedded device may access the external device (e.g., a server) periodically to obtain necessary data.

SOAP is a standard for encoding function calls, such as remote procedure calls (RPCs), in XML. SOAP defines rules, i.e., a syntax, for encoding the function calls in XML. The body of a SOAP command is defined, at its start, by <SOAP-ENV:BODY> and, at its end, by </SOAP-ENV:BODY>. Code in between these two commands includes the function to be performed by the SOAP command. A SOAP command may include other data as well, such as header information.

SUMMARY

In general, in one aspect, the invention is directed to a controller embedded in a device for retrieving data from a server. The controller sends a command to the server that identifies an instance of the device and receives, from the server and in response to the command, data that is specific to the instance of the device. The data identifies additional data to retrieve for the device.

This aspect of the invention may include one or more of the following. The command may include an operational parameter for the device and the data may include an updated value for the operational parameter. The command may include plural operational parameters for the device and the data may include updated values that differ from current values of the operational parameters.

The data may include a list of operational parameters. In this case, the embedded controller sends a second command to the server, which includes operational parameters from the list, and receives, from the server and in response to the second command, updated values of one or more of the operational parameters included in the second command. The data may include a list of operations to be performed by the controller. In this case, the embedded controller parses the operations from the list and performs the operations from the list.

The data may include a configuration file for the device. The command identifies the instance of the device by a device type and/or one or more of a serial number and a universal unique identifier. The embedded controller sends the command to the server periodically. The server runs the Hypertext Transfer Protocol and the command contains Extensible Markup Language code. The device receives the data via the Hypertext Transfer Protocol.

The command may include a first operational parameter for the device and the data may include a second operational parameter that is unrelated to the first operational parameter. The data may include a uniform resource locator. The uniform resource locator is used to obtain additional data that relates to the device. The data may include an indication that additional data for the device is present at the server. A second command is sent to the server to retrieve the additional data. The server retrieves the additional data in response to the second command. Parameters in the command determine a content of the data. The data may be encrypted when the data is received and then decrypted. The data may contain a digital signature when the data is received, which is then authenticated. The data may include a list of operations to be performed by the controller. The list of operations includes Simple Object Access Protocol calls that are scripted using Extensible Markup Language.

In general, in another aspect, the invention is directed to a server for sending data over a network to a controller embedded in a device. The server receives a command from the embedded controller, identifies an instance of the device from information in the command, retrieves data that is specific to the instance of the device, and sends the data to the embedded controller. The data identifies additional data for the embedded controller to retrieve.

This aspect of the invention may include one or more of the following features. The command may include a device type and/or one or more of a serial number and a universal unique identifier. The instance of the device may be identified based on the device type and/or one or more of the serial number and the universal unique identifier. The server may parse the device type and one or more of the serial number and universal unique identifier from the command prior to identifying the instance of the device.

The command may include an operational parameter for the device. The data may include an updated value of the operational parameter. The data may include a list of operational parameters for the device. The server receives a second command from the embedded controller, which includes an operational parameter from the list of operational parameters, obtains an updated value of the operational parameter, and sends the updated value of the operational parameter to the embedded controller.

The data may include a list of operations to be performed by the embedded controller. The data may include a configuration file for the device. The server may receive the data specific to the instance of the device and store the data in memory, from which it is retrieved. The data specific to the instance of the device may be received via a Web page generated by the server. The server may run the Hypertext Transfer Protocol and the command may contain Extensible Markup Language code. The data may be stored in a queue and retrieved from the queue.

In general, in another aspect, the invention is directed to a system that includes a controller embedded in a device that is capable of communicating over a computer network, and a server that is capable of communicating over the computer network. The embedded controller sends a command to the server over the computer network that identifies an instance of the device and, in response, the server (i) identifies the instance of the device based on the command, (ii) retrieves data that is specific to the instance of the device, and (iii) sends the data to the embedded controller over the computer network. The data identifies additional data for the embedded controller to retrieve.

This aspect of the invention may include one or more of the following features. The embedded controller is not remotely-addressable from the computer network. The computer network is the Internet. The server runs the Hypertext Transfer Protocol and the command may contain Extensible Markup Language code.

Heretofore, SOAP commands were only available as individual, discrete commands. This is impractical for device-initiated communication, particularly if the device is unaware of any timing issues relating to execution of the SOAP commands. The invention therefore scripts one or more SOAP commands in XML and provides the XML script to a device, such as an embedded controller, for execution. The XML script is executed by the embedded controller, much like a computer program, to control execution of the SOAP commands. For example, timing and sequence of execution of the SOAP commands may be specified in the XML script.

The invention also defines variables in the XML script, which may be passed to and from the SOAP commands. This facilitates the combination of SOAP commands in XML script and provides an advantage over the use of traditional SOAP commands, which are limited to passing “hard-coded” numerical values (i.e., non-variables).

In general, in one aspect, the invention is directed to a computer-implemented system for processing a simple object access protocol (SOAP) command. The system includes interpreting an XML script to perform a function contained in the XML script, the XML script containing the SOAP command, parsing the SOAP command from the XML script, and passing the SOAP command to a SOAP interpreter for execution. This aspect of the invention may include one or more of the following features.

Plural SOAP commands may be contained in the XML script. The plural SOAP commands may be passed to the SOAP interpreter. The plural SOAP commands may be executed in a sequence specified by the XML script. At least one of an argument and a return value may be received from the SOAP command following execution of the SOAP command. The argument may be stored as a variable in the XML script.

The XML script may declare a variable. A value of the variable may be passed as an argument to the SOAP command prior to executing the SOAP command. The function may be a conditional statement. The conditional statement may be an If-Then statement or an If-Then-Else statement. The function may be a control statement that affects a sequence of execution of the XML script and/or the SOAP command. The control statement may be a loop. The function may be an exception handler that affects a sequence of execution of the XML script and/or the SOAP command when an error condition exists. The function may be a statement that controls relative or absolute time to execute the SOAP command. Parsing may be performed by an XML interpreter and executing may be performed by the SOAP interpreter. The XML interpreter may pass the SOAP command to the SOAP interpreter and the SOAP interpreter may pass an output of the SOAP command to the XML interpreter.

In general, in another aspect, the invention is directed to a computer-implemented system for generating extensible markup language (XML) script that contains a simple object access protocol (SOAP) command. The system includes receiving code that defines a function and the SOAP command and translating the code to XML script that performs the function and contains the SOAP command. This aspect of the invention may include one or more of the following features.

The XML script may be provided to a device. The device may include a controller that executes the XML script. The code may contain plural SOAP commands and functions. The XML script may contain the plural SOAP commands and functions. The XML script may declare a variable. A value of the variable value may be passed as an argument to the SOAP command in the XML script.

The function may be a conditional statement. The conditional statement may be an If-Then statement or an If-Then-Else statement. The function may be a control statement that affects a sequence of execution of the XML script and/or the SOAP command. The control statement may be a loop. The function may be an exception handler that that affects a sequence of execution of the XML script and/or the SOAP command when an error condition exists. The function may be a statement that controls a relative or absolute time to execute the SOAP command.

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

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a network containing a server and a device having an embedded controller;

FIG. 2 is a flowchart showing a process by which the embedded controller retrieves data for the device from the server;

FIG. 3 is a flowchart showing an alternative process by which the embedded controller retrieves data for the device from the server;

FIG. 4 is a block diagram of a network containing a server and a device having an embedded controller;

FIG. 5 is a flowchart showing a process for translating human-readable code into XML script;

FIG. 6 is a flowchart showing a process by which the embedded controller retrieves XML script for the device from the server; and

FIG. 7 is a flowchart showing a process by which the embedded controller executes the XML script.

DESCRIPTION

FIG. 1 shows a network 10. Network 10 includes a device 11 containing an embedded controller 17. Device 11 is any type of apparatus or system having functions that are monitored and controlled by embedded controller 17.

Device 11 is connected to an internal network 12, such as a LAN. A router or modem 14 couples internal network 12 to an external network 15, such as the Internet/World Wide Web (Web). External network 15 runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Network connections are via Ethernet, telephone line, wireless, or other transmission media.

External network 15 contains a server 19, which is a computer or any other processing device. Server 19 communicates with embedded controller 17 over external network 15 and internal network 12. Embedded controller 17 has a local IP (Internet Protocol) address that can be resolved within internal network 12. However, this local IP address may not be recognizable by devices on external network 15, such as server 19. As such, server 19 may not be able to directly address device 11.

Embedded Controller

Embedded controller 17 runs software 20, which includes web client application 21 and operating software 22. Web client application 21 includes a TCP/IP protocol stack that allows embedded controller 17 to communicate over external network 15. Device operating software 22 provides an interface between Web client application 21 and a database 24. Through device operating software 22, embedded controller 17 retrieves data stored in database 24 and stores data in database 24.

Database 24 is stored in a memory 25 on device 11 or internal to embedded controller 17. Database 24 stores data, including operational parameters, configuration files, and identification information for device 11.

The operational parameters constitute settings and/or control instructions for the device 11, which are implemented by embedded controller 17. The types of operational parameters that are stored in database 24 depend on the nature of device 11. For example, if device 11 is a heating/cooling system, the operational parameters may include temperature levels, humidity levels, airflow controls, vent/duct open/close controls, and fan motor speed settings. A configuration file is a file that contains a set of one or more operational parameters for an instance of device 11.

What is meant by “instance” is the specific identity of device 11 as distinguished from other identical devices. The identification information stored in database 24 identifies the instance of device 11. This identification information includes, but is not limited to, data identifying the type of the device, a common (or “friendly”) name for the device, the manufacturer of the device, the model name of the device, the model number of the device, the serial number of the device, and a universal unique identifier (UUID) for the device.

The device type specifies a uniform resource locator (URL) for the device, which includes the name of the device. This information identifies a Web site that is associated with, and generated by, server 19 for the device. For example, a device type might be:

• • www.SonyVideo.com/television/Wega/XBR400for a Sony® Wega® XBR400® television that includes an embedded controller. The common name of the device is how the device is known in the vernacular, e.g., “television”. The manufacturer identifies the manufacturer of the device, e.g., Sony®. The model name identifies the particular model of the device, e.g., Wega®. The model number identifies the model number of the device, e.g., XBR400®. The serial number identifies the serial number of a particular instance of the device, e.g., 53266D. The UUID is a universal identifier for the instance of the device, e.g., 4A89EA70-73B4-11d4-80DF-0050DAB7BAC5. Of the data shown above, only the serial number and the UUID are unique to the instance of device 11.Server

Server 19 is a computer that runs HTTP (Hypertext Transfer Protocol). Server 19 includes a controller 27, such as a microprocessor, for executing software to perform the functions described below. To avoid confusion in terminology, the following reads as though those functions are performed by server 19, even though software in controller 27 of server 19 performs the functions.

Server 19 executes Web server software 29 to communicate over external network 15. Web server software 29 also hosts a Web page associated with device 11. The Web page (not shown) is displayed on computer 13 of a user, such as the owner of device 11, who may input updated operational parameters for the device. These input updated operational parameters are transmitted to Web server software 29 over external network 15. Web server software 29 stores the updated parameters in database 30.

Web server software 29 stores and retrieves data in database 30 using application logic 32. Application logic 32 is software for accessing database 30 using the CGI (Common Gateway Interface) protocol. CGI is a well-known protocol for accessing a database. The operational parameters can be stored in database 30 individually or as part of a configuration file for an instance of device 11.

Database 30 is stored in a memory 31, which is inside of, or external to, server 19. Database 30 stores data associated with device 11, including the operational parameters noted above. Other data that may be stored for device 11 is described below.

The Data Transfer Process

Embedded controller 17 executes software 20 to retrieve data, such as operational parameters, from remote server 19. Server 19 executes software 34 to send the data to embedded controller 17. FIG. 2 shows these processes in detail. The left half of FIG. 2, titled “Embedded Controller” shows process 40 performed by embedded controller 17, and the right half of FIG. 2, titled, “Server”, shows process 41 performed by server 19.

Process 40 generates and sends (201) a command to server 19. The command, or a modified version thereof, is sent by embedded controller 17 to server 19 periodically. It is through this command that embedded controller 17 polls server 19 to determine if there are any new/updated operational parameters for device 11.

The command includes data identifying device 11. The data identifies the specific instance of device 11 and includes a device type field and one or both of a device serial number field and a device UUID. The command may also include the common name field, the manufacturer name field, the model name field, and the model number field, as set forth above.

The command may be either an HTTP GET command or an HTTP post command. The data included in those commands is similar, with the difference being that the HTTP GET command retrieves a document, such as a configuration file, that contains operational parameters and the HTTP POST command retrieves individual operational parameters. An example of an HTTP GET command is shown in Appendix A and an example of an HTTP POST command is shown in Appendix B.

The HTTP POST and GET commands shown in Appendices A and B contain XML (eXtensible Markup Language) commands. XML is a self-describing computer language in the sense that fields in the XML code identify variables and their values in the XML code. For example, as shown in the Appendices, the “manufacturer” field identifies a manufacturer, e.g., Sony®, and is delineated by “<manufacturer>” to indicate the start of the field and “</manufacturer>” to indicate the end of the field. XML is used because it can be generated, parsed and read relatively easily by server 19 and embedded controller 17.

As noted, the GET command is used to retrieve a document from server 19. The document to be retrieved corresponds to the fields in the GET command, in particular to the device type, serial number and/or UUID fields. By contrast, the POST command is used to retrieve individual operational parameters. The operational parameters that are to be retrieved are listed in the POST command itself. Changing these parameters changes the information the server provides to the embedded controller. By way of example, as shown in Appendix B, the operational parameters include airflow, humidity, motor and vent values for the fictitious “widget” device. The current values of these parameters are specified in the POST command shown in Appendix B as follows:

• • <parameters>
    • <Airflow xsd:type=“integer”>378</Airflow>
    • <Humidity xsd:type=“double”>46.7</Humidity>
    • <Motor xsd:type=“integer”>1500</Motor>
    • <Vent xsd:type=“integer”>4</Vent>
  • </parameters>The updated values of these parameters are returned by server 19 to embedded controller 17 in a reply POST command. The updated values of these parameters are specified in the POST command shown in Appendix B as follows:
  • <parameters>
    • <Motor xsd:type=“integer”>1250</ Motor >
    • <Vent xsd:type=“integer”>2</Vent>
  • </parameters>

As shown, both the POST and GET commands include the URL of the device in the device type field. As described below, this directs server 19 to a Web site associated with device 11 and, thereafter, in the case of a GET Command, to retrieve a specific Web page that is generated for the device by server 19 or any other device in communication with network 15. It is noted that, since the POST command retrieves parameters, not a document like the GET command, the POST command need not include a URL of the device.

Referring back to FIG. 2, process 41 (in server 19) receives (202) the command from embedded controller 17. Process 41 identifies the command as either a POST or GET command based on a header, such as “POST/CONTROL HTTP/1.1” (see the headers in Appendices A and B), in the command. Process 41 uses an XML parser to parse (203) the various identifying fields, such as device type, serial number, and UUID, from the command.

Process 41 identifies (204) the instance of device 11 based on the information parsed from the command. That is, process 41 uses the device type, serial number, and UUID field information to identify the instance.

If the Command is a POST Command

The remaining identification information from the command is used to narrow the search through database 30 down to data for the specific instance of device 11. The device serial number and/or UUID are used to retrieve operational parameters specific to device 11.

Once the appropriate data has been identified (204), process 41 retrieves (205) that data using application logic 32. Process 41 compares the values of the operational parameters to those included in the POST command. If the values are the same, process 41 returns an indication that there are no new/updated values for device 11. If the values of the operational parameters are different, process 41 adds the appropriate updated value fields to the POST command and sends (206) the POST command, with the updated operational parameters, back to embedded controller 17. Thus, only those operational parameters that differ from their original values are returned to embedded controller 17 in the POST command.

If the Command is a GET Command

As was the case above with the POST command, the remaining identification information from the command is used to narrow the search through database 30 down to data for the specific instance of device 11. In particular, the device serial number and/or UUID are used to retrieve (205) a configuration file that is specific to device 11. Process 41 sends (206) the configuration file to embedded controller 17. The configuration file may be a Web page identified by the URL in the device type field. This Web page is generated by server 19 using parameters stored in database 30 and then sent to device 11. It is noted that the complete Web page itself need not be stored. Alternatively, the GET command may retrieve separate configuration files and Web pages.

Process 40 in embedded controller 17 receives (207) the data (operational parameters or configuration file) from server 19 in response to sending (201) the command. Process 40 uses the data to update/reset device 11. For example, if device 11 is a heating system, a new operational parameter may be a new temperature setting for its thermostat. In this example, embedded controller 17 sets the new temperature accordingly. If the device is a television, a new operational parameter may indicate that certain pay television stations are now available. In this case, embedded controller 17 performs any appropriate decoding/descrambling functions on the television signal.

For both the POST and GET commands, the reply from server 19 to embedded controller 17 may contain a URL. The URL directs embedded controller 17 to a Web site that contains additional information, e.g., operational parameters and the like, for device 11. Embedded controller 17 may then retrieve any necessary information from that Web site. Additionally, the reply may contain an indication that server 19 contains additional data for embedded controller 17 to retrieve. In this case, embedded controller issues a new POST or GET command, whichever is appropriate based on the additional data identified in the reply, and processes 40,41 described herein are repeated to retrieve the additional data from server 17. The initial command and/or reply may be encrypted by server 11 and decrypted by embedded controller 17. Any of a number of commercially-available encryption technologies may be used. Server 17 may also incorporate a digital signature into the reply. Embedded controller 17 authenticates the digital signature when it receives the reply, thereby authenticating the reply.

Process 41 may also add value fields to the POST or GET command that are unrelated to the fields originally included in the POST or GET commands output by controller 17. For example, if the data retrieved (205) by process 41 includes additional parameters that require updating and that were not included in an original POST command, process 41 adds the necessary fields and parameters to the POST command that it returns to embedded controller 17. In this regard, server 11 may store data to be delivered to controller 17 in a queue. When controller 17 next contacts server 11, the data from the queue may be transferred to controller 17, regardless of whether the data corresponds to data in the original command.

ALTERNATIVE EMBODIMENT

FIG. 3 shows alternative embodiments of processes 40,41. In processes 40,41, the GET and POST commands request the same parameters each time the commands are issued. The parameters requested are “hard-coded” in the software that implements process 40. This embodiment provides a way to change the parameters that are requested without altering the software that generates the request/command.

Referring to FIG. 3, process 45 in embedded controller 17 begins by sending (301) a command to server 19. The command, in this case, is an HTTP GET command, since it is requesting a document, not individual operational parameters. The document is an XML document that contains a list of operational parameters to be updated. Using this document, embedded controller 17 can change the operational parameters that it periodically updates.

Process 46 in server 19 receives (302) the command from embedded controller 17, parses (303) the command using an XML parser to obtain the information specific to the instance of device 11, and identifies (304) the appropriate document based on this information. As before, the information that identifies the instance of device 11 includes, among other things, the device type, its serial number, and its UUID. Process 46 retrieves (305) the document containing the list of operational parameters to be updated, and sends (306) the document back to embedded controller 17.

Process 45 in embedded controller 17 receives (307) the document from server 19, parses (308) the operational parameters to be updated from the document, and formulates (309) a POST command to send to server 19. The command is formulated using a command template (not shown), into which process 45 inserts the operational parameters parsed from the document. Process 45 sends this second command to the server. At this point, processes 45 and 46 operate (310) in the same manner as processes 40 and 41, respectively, when used with a POST command. Accordingly, the details of processes 40,41 are not repeated here.

This alternative embodiment may be generalized further. For example, rather than simply retrieving a list of operational parameters, embedded controller 17 may retrieve, from server 19, a list of operations that it is to perform. For example, that list may contain operational parameters to be updated, times at which the updates are to occur, a schedule of diagnostic tests, and the like. Any operation that may be performed by embedded controller 17 may be included on the list.

The operations in the list may be Simple Object Access Protocol (SOAP) calls that are scripted using XML. Briefly, SOAP is a recognized standard for performing remote procedure calls. Scripting of SOAP calls using XML is described in U.S. patent application Ser. No. 10/123,960, now U.S. Pat. No. 7,178,149, filed concurrently herewith and entitled “XML Scripting of SOAP Commands”, the contents of which are hereby incorporated by reference into this application as if set forth herein in full.

The process for retrieving the list of operations is identical to processes 45 and 46, save for the contents of the list itself. The actions that embedded controller takes once it has the list (i.e., 310) depend on the contents of the list. For example, the list might specify that parameters are to be updated every hour and may also contain a list of the parameters to be updated. The list may contain XML commands, which can be parsed by embedded controller 17. Thus, embedded controller 17 reads the commands in the list and performs the appropriate operations with respect to device 11.

Architecture

Processes 40,41 and 45,46 are not limited to use with the hardware/software configuration of FIG. 1; they may find applicability in any computing or processing environment. Processes 40,41 and 45,46 may be implemented in hardware (e.g., an ASIC {Application-Specific Integrated Circuit} and/or an FPGA {Field Programmable Gate Array}), software, or a combination of hardware and software.

Processes 40,41 and 45,46 may be implemented using one or more computer programs executing on programmable computers that each includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.

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.

Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform processes 40,41 and 45,46.

Processes 40,41 and 45,46 may also be implemented as a computer-readable storage medium, configured with a computer program, where, upon execution, instructions in the computer program cause the computer to operate in accordance with processes 40,41 and 45,46.

The invention is not limited to use with the protocols and standards described above. For example, Web server 19 may use Java Servlets, ASP (Active Server Pages), and/or ISAPI (Internet Server Application Programming Interface) to communicate with application logic 32, instead of, or in addition to, CGI. The commands sent by embedded controller 17 and/or server 19 (e.g., in 201, 301, 310) are not limited to HTTP GET and POST commands. Any commands and/or requests for requesting and receiving data may be used.

The data transferred to embedded controller 17 by server 19 is not limited to operational parameters or configuration files. The data may include, for example, a schedule of actions to be performed by device 11 that is based on information pertaining the owner of the device. For example, owner preferences may be stored in database 30. The instance-specific data may be used by server 19 to correlate the owner of the device to the appropriate preferences. These preferences then may be transmitted back to device 11 to control the operation thereof.

The original parameters sent by embedded controller 17 to server 19 may be used by server 19 to calculate new, updated parameters based on data stored in database 30. Thus, the invention is not limited to simply retrieving updated data, but may also include calculating new data based on currently-available data.

The documents and commands described above are not limited to XML format. Any computer language may be used for the commands. The documents may be in any format, for example, HTML (Hypertext Markup Language) documents may be used. In addition, the invention is not limited to use with the Web, Web servers, and the like. The servers and embedded controllers described herein may be the same type of general-purpose computer appropriately programmed, or different devices.

Xml Scripting of Soap Commands

This invention relates generally to scripting simple object access protocol (SOAP) commands using extensible markup language (XML) and to providing the resulting XML script to a device for execution.

FIG. 4 shows a network 410. Network 410 includes a device 411 containing an embedded controller 417. Device 411 is any type of apparatus or system having functions that are monitored and controlled by embedded controller 417.

Device 411 is connected to an internal network 412, such as a LAN. A router or modem 414 couples internal network 412 to an external network 415, such as the Internet/World Wide Web (Web). External network 415 runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Network connections are via Ethernet, telephone line, wireless, or other transmission media.

External network 415 contains a server 419, which is a computer or any other processing device. Server 419 communicates with embedded controller 417 over external network 415 and internal network 412. Embedded controller 417 has a local IP (Internet Protocol) address that can be resolved within internal network 412. However, this local IP address may not be recognizable by devices on external network 415, such as server 419. As such, server 419 may not be able to directly address device 411.

Embedded Controller

Embedded controller 417 runs software 420, which includes Web client application 421 and operating software 422. Web client application 421 includes a TCP/IP protocol stack that allows embedded controller 417 to communicate over external network 415. Device operating software 422 provides an interface between Web client application 421 and a database 424 in memory 425. Through device operating software 422, embedded controller 417 retrieves data stored in database 424 and stores data in database 424.

Software 420 also includes an XML interpreter 423 and a SOAP interpreter 426. XML interpreter 423 is a module that receives XML script, parses the script, and performs the functions identified by the script. As background, XML is a self-describing computer language, meaning that fields in XML code identify variables and their values in the XML code. For example, a “data” field is delineated by “<data>” to indicate the start of the field and “</data>” to indicate the end of the field. XML is used because it can be generated, parsed and understood relatively easily.

Among the functions in the XML script may be an instruction to identify a SOAP command and to pass the SOAP command to SOAP interpreter 426 for processing. An example of another function includes a statement that controls relative or absolute time to execute the SOAP command. SOAP interpreter 426 receives SOAP commands from XML interpreter 423 and executes those commands. Examples of SOAP commands that can be executed by the embedded controller or agent include setting the value of a variable, uploading or downloading a file, restarting the software, or any action specific to the apparatus.

Database 424 stores data, such as operational parameters, XML script, and identification information for the instance of device 411. What is meant by “instance” is the specific identity of device 411 as distinguished from other identical devices. The identification information stored in database 424 identifies the instance of device 411. This identification information may include 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, or a universal unique identifier (UUID) for the device.

The device type is the name of the device. The common name of the device is how the device is known in the vernacular, e.g., “television”. The manufacturer identifies the manufacturer of the device, e.g., Sony®. The model name identifies the particular model of the device, e.g., Wega®. The model number identifies the model number of the device, e.g., XBR400®. The serial number identifies the serial number of a particular instance of the device, e.g., 53266D. The UUID is a universal identifier for the instance of the device, e.g., 4A89EA70-73B4-11d4-80DF-0050DAB7BAC5. Of the data shown above, generally only the serial number and the UUID are unique to the instance of device 411.

The identification data stored in database 424 is used by embedded controller 417 to retrieve XML script specific to the instance of device 411 (or for a particular type of device 411) from server 419. A device-initiated process for retrieving the XML script is described below.

Server

Server 419 is a computer that runs an HTTP (Hypertext Transfer Protocol) Web server computer program. Server 419 includes a controller 427, such as a microprocessor, for executing software to perform the functions described below. To avoid confusion in terminology, the following reads as though those functions are performed by server 419, even though software in controller 427 of server 419 performs the functions.

Server 419 executes Web server software 429 to communicate over external network 415. Web server software 429 also hosts a Web page associated with device 411. The Web page (not shown) is displayed on computer 433 of a user, such as the owner of device 411, who may select some actions to be sent to the device. For example, a remote operator may want to update three operational variables, which requires three SOAP commands. These three SOAP commands are wrapped in an XML script that executes the commands as a single operation. The XML script, along with any input updated operational parameters (if desired) are transmitted to Web server software 429 over external network 415. Web server software 429 stores the XML script in database 430 of memory 431. An example of a process for updating operational parameters is described in U.S. patent application Ser. No. 09/667,737, filed Sep. 22, 2000, the contents of which are incorporated into this application by reference as if set forth herein in full.

Web server software 429 stores and retrieves XML script from database 430 using application logic 432. Application logic 432 is software for accessing database 430 using Java servlets and a JDBC (Java Data Base Connectivity) database driver. The XML script can be stored in database 430 individually or as part of a configuration file for an instance of device 411.

Computer

Computer 433 is personal computer (PC) or other machine that includes a processor 436, a memory 437, and a storage medium 438 (see view 455). Storage medium 438 stores computer programs 439, which are executed by processor 436 out of memory 437. Computer programs 439 include a Web client application 443 containing a TCP/IP protocol stack for communicating over the Internet, a Web browser 444 such as Microsoft® Internet Explorer® for accessing Web pages, an operating system (OS) 445 such as Microsoft® Windows98®, and executable instructions 446 for implementing process 550, which is shown in FIG. 5.

Process 550 generates XML script containing one or more SOAP commands from user-generated code provided to computer 433. The code may be input by the user via a graphical user interface (GUI) (not shown), for example, or it may be retrieved from a storage medium or over network 15.

The code has a syntax that can be understood and interpreted by instructions 446. For example, the code may be a commonly-understood computer language, such as BASIC or “C”, or a form of pseudo-code specific to the invention. The code defines functions, such as conditional statements (e.g., If-Then or If-Then-Else statements), control statements (e.g., do While or do Until loops), or exception handlers, meaning fail-safe mechanisms that are triggered in the code in the event that an instruction in the code fails. The functions affect the sequence of execution of the resulting XML code and/or SOAP commands.

An example of user-generated C/C++ code is set forth below:

int local = 8;

int total = 0;

while ( total < 10 )

{

• • total =SomeFunction(total);
  • AnotherFunction(local);

}

This code initializes integer variables “local” and “total” to values of “8” and “0” respectively. The code includes a “While” loop, meaning that the loop between the brackets “{ }” is continually executed while the value of total is less than “10”, whereafter processing within the loop is discontinued. Within the loop, the value of “total” is set equal to the result of a SOAP command called “SomeFunction” processing the previous value of “total” and another SOAP command called “AnotherFunction” processing “local”.

Process 550 receives (501) code, such as that shown above, that defines one or more functions (e.g., a “While” loop) and one or more SOAP commands (e.g., “SomeFunction” and “AnotherFunction”). Process 550 translates (502) the code to XML script that, when interpreted, performs the functions and contains the SOAP commands. To perform the translation, process 550 may compile the code, interpret the functions in the compiled code, and generate appropriate XML script from the compiled code. An appropriate compiler may be included within instructions 446 for this purpose. The format of the SOAP commands may be static and known to the compiler, or the format may be determined dynamically from a WSDL (Web Services Description Language) document. WSDL is a standard for describing SOAP commands. WSDL is itself an XML document that can be interpreted automatically. WSDL defines the set of functions available and the format of each of the SOAP commands.

WSDL usually describes the functionality for a particular device or Web service. By reading WSDL, a program can display functions to a user, then create SOAP command(s) for the function(s) selected by the user. By way of example, there may be one thousand devices, all with individual settings, and it is desired to set all of the devices to 6% lower power usage. Using traditional SOAP commands, the server must be able to address each device, obtain each device's current setting, calculate 94% of its value, then write that new value back to each device, all through issuing individual SOAP commands. Using a SOAP script, the same script can be sent to all of the devices because the variable is evaluated locally at each device. As the population of monitored devices grows, this kind of distributed processing becomes more useful.

Continuing with the example set forth above, process 550 translates (502) the code into the following XML script:

<Root>

• • <Variables>
    • <local type=“integer”>8</local>
    • <total type=“integer”>0</total>
  • </Variables>
  • <Script>
    • <While condition=“total < 10”>
      • <SOAP-ENV:Body>
        • <SomeFunction>
        • <Count>total</Count>
        • </SomeFunction>
      • </SOAP-ENV:Body>
      • <Return variable=“total”/>
      • <SOAP-ENV:Body>
        • <AnotherFunction>
        •  <Input>local</Input>
        • </AnotherFunction>
      • </SOAP-ENV:Body>
    • </While>
  • </Script>

</Root>

The XML script contains the same functions and SOAP commands as the original C/C++ code input by the user. For example, the “While” loop is expressed as

• • <While condition=“total < 10”>and </While>and the SOAP commands are expressed as
  • <SOAP-ENV:Body>
    • <SomeFunction>
    • <Count>total</Count>
    • </SomeFunction>
  • </SOAP-ENV:Body>and
  • <SOAP-ENV:Body>
    • <AnotherFunction>
    • <Input>local</Input>
    • </AnotherFunction>
  • </SOAP-ENV:Body>The expression “<Return variable=“total”/>” returns the value of the variable “total” to the XML script. Thus, the output of the SOAP command may be passed back to the XML script as an argument in the SOAP command and used as a variable in the XML script. Also, the XML script may be written so that a variable, such as “total”, is passed as an argument to a SOAP command.

An example of XML script containing a conditional “IF” statement is set forth in Appendix A attached hereto. An example of XML script containing an exception handler is set forth in Appendix B attached hereto.

After the code has been translated (502) to XML script, process 550 provides (503) the XML script to server 419 over network 415. Process 550 may send the XML script to server 419 through a Web interface, along with identification information that specifies the instance of device 411 for which the XML script is intended. Web server software 429 on server 419 receives the XML script over network 415 and application logic 432 stores the XML script in database 430, along with its associated identification information.

Device-Initiated Retrieval of the XML Script

Embedded controller 417 executes software 420 to retrieve the XML script intended for device 411 from remote server 419. In response, server 419 executes software 434 to send the XML script to embedded controller 417. FIG. 6 shows these processes in detail. The left half of FIG. 6, titled “Embedded Controller” shows process 640 performed by embedded controller 417, and the right half of FIG. 6, titled, “Server”, shows process 641 performed by server 419.

Process 640 generates and sends (601) a command to server 419. The command, or a modified version thereof, is sent by embedded controller 417 to server 419 periodically. It is through this command that embedded controller 417 polls server 419 to determine if there is any new/updated XML script for device 411 on server 419.

The command includes XML data identifying device 411. The data identifies the specific instance of device 411 and may include a device type field and one or both of a device serial number field and a device UUID. The command may also include a common name field, a manufacturer name field, a model name field, and a model number field, which specify the information set forth above for the device.

The command may be either an HTTP GET command or an HTTP post command. The data included in those commands is similar, with the difference being that the HTTP GET command retrieves a document, such as a file containing the XML script, and the HTTP POST command retrieves information, such as the XML script itself.

Process 641 (in server 419) receives (602) the HTTP command from embedded controller 417. Process 641 identifies the command as either a POST or GET command based on a header, such as “POST/CONTROL HTTP/1.1” (for a POST command), in the command. Process 641 uses an XML parser to parse (603) the various identifying fields, such as device type, serial number, and UUID, from the command.

Process 641 identifies (604) the instance of device 411 based on the information parsed from the command. That is, process 641 uses the device type, serial number, and UUID field information to identify the instance of device 411.

If the Command is a POST Command

The identification information from the command, in particular the device serial number and/or UUID, is used to search through database 430 for XML script specific to device 411. Once the appropriate XML script has been identified (604), process 641 retrieves (605) that XML script from database 430 using application logic 432. Process 641 determines if the XML script has been updated since it was last retrieved. This may be done by examining a revision number or date included in a header associated with the XML script. If the XML script has been updated, process 641 adds the updated XML script to the reply portion of POST command and sends (606) the POST command, with the updated XML script, back to embedded controller 417.

If the Command is a GET Command

As was the case above with the POST command, the identification information from the command is used to search through database 430 for XML script for the specific instance of device 411. In particular, the device serial number and/or UUID are used to retrieve (605) a configuration file that is specific to device 411. The configuration file contains the XML script for device 411. Process 641 sends (606) the configuration file to embedded controller 417.

Process 640 receives (607) the XML script containing one or more SOAP commands from server 419 in response to the HTTP command. Process 640 (in particular Web client application 421 in device 411) provides the XML script to XML interpreter 423, where the XML script is executed.

Referring to FIG. 7, a process 752 is shown for executing the XML script in embedded controller 417. Process 752 is implemented by executable instructions in XML interpreter 423 and SOAP interpreter 426.

XML interpreter 423 interprets (701) the XML script to perform the functions contained therein. For example, if there are any conditional statements, control statements, or exception handlers defined by the XML script, XML interpreter performs those functions on the appropriate commands and variables contained in the XML script.

During processing, XML interpreter 423 parses (702) the XML script to identify any SOAP commands contained in the XML script. Identified SOAP commands are passed to SOAP interpreter 426, which executes (703) the SOAP commands. Results of the SOAP commands may be passed back to the XML interpreter 423 for further processing. Likewise, variables may be passed from the XML script to the SOAP commands.

Using XML script in this manner, embedded controller 417 is able to execute multiple SOAP commands in response to a single device-initiated query. Thus, device 411 can perform reconfiguration operations or the like using multiple SOAP commands without maintaining communication with an external device, such as server 419, during the reconfiguration process. The XML script can specify (future) times at which the SOAP commands are to be executed, thus providing the device with further control over its own operation. SOAP interpreter 426 implements the SOAP standard to interpret and execute function calls. As more devices and software systems have support for SOAP, device 11 will be able to execute a script that controls multiple devices by calling their SOAP services.

Architecture

Processes 640, 641, 550 and 752 are not limited to use with the hardware/software configuration of FIG. 4; they may find applicability in any computing or processing environment. Processes 640, 641, 550 and 752 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.

Processes 640, 641, 550 and 752 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.

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.

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 640, 641, 550 and 752.

Processes 640, 641, 550 and 752 may also be implemented as an article of manufacture, such as one or more machine-readable storage media (e.g., compact or floppy disc), each configured with a computer program, where, upon execution, instructions in the computer program cause a machine (e.g., a computer) to operate in accordance with one or more of processes 640, 641, 550 and 752.

The invention is not limited to use with the protocols and standards described above. For example, Web server may use Java Servlets, ASP (Active Server Pages), ISAPI (Internet Server Application Programming Interface), or .NET interfaces to communicate with application logic 432. The HTTP commands sent by embedded controller 417 and/or server 419 are not limited to HTTP GET and POST commands. Any commands and/or requests for requesting and receiving data may be used.

The invention is not limited to the protocols and architecture described with respect to FIG. 4. Similarly, the invention is not limited to device-initiated transfers of the XML script. For example, computer 433 may transmit the XML script directly to embedded controller 417 (rather than by way of server 419) via e-mail, file transfer protocol (FTP), message queues, or any other type of data transfer mechanism. These other transfer protocols may also be used with device-initiated transfers. Server 419 may generate the XML script and transmit it directly to controller 417. The XML script may be used on any machine, and is not limited to use with embedded controllers. RPCs other than SOAP calls may be scripted using XML and the resulting XML script may be processed in the manner described herein. SOAP commands other than those described herein may be used. The processes described herein may be implemented using circuitry such as programmable logic, logic gates, a processor, and/or a memory.

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

APPENDIX A

Get Command

GET /Widget/config.xml 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”>

<specVersion>

• • <major>1</major>
  • <minor>0</minor>

</specVersion>

<device>

• • <deviceType>urn:www-acme-com:device:Widget:3</deviceType>
  • <friendlyName>Widget</friendlyName>
  • <manufacturer>Acme Industries</manufacturer>
  • <modelName>Widget</modelName>
  • <modelNumber>3</modelNumber>
  • <serialNumber>53266D</serialNumber>
  • <UDN>uuid:4A89EA70-73B4-11d4-80DF-0050DAB7BAC5</UDN>

</device>

</root>

APPENDIX B

Post Command

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”>

<specVersion>

• • <major>1</major>
  • <minor>0</minor>

</specVersion>

<device>

• • <deviceType>urn:www-acme-com:device:Widget:3</deviceType>
  • <friendlyName>Widget</friendlyName>
  • <manufacturer>Acme Industries</manufacturer>
  • <modelName>Widget</modelName>
  • <modelNumber>3</modelNumber>
  • <serialNumber>53266D</serialNumber>
  • <UDN>uuid:4A89EA70-73B4-11d4-80DF-0050DAB7BAC5</UDN>

</device>

</root>

<parameters>

<Airflow xsd:type=“integer”>378</Airflow>

<Humidity xsd:type=“double”>46.7</Humidity>

<Motor xsd:type=“integer”>1500</Motor>

<Vent xsd:type=“integer”>4</Vent>

</parameters>

And the response containing parameters that have been modified:

HTTP/1.1 200 OK

Connection: close

Content-Type: text/xml

Content-length: nnn

Date: Fri, 13 Jun. 2000 13:43:05 GMT

<?xml version=“1.0”?>

<parameters>

<Motor xsd:type=“integer”>1250</ Motor >

<Vent xsd:type=“integer”>2</Vent>

</parameters>

Claims

1. A method performed by a controller associated with an instance of a device for retrieving data from a server, comprising: polling the server by sending a message to the server periodically, the message containing information that distinguishes the instance of the device from all other instances of the device for which the server stores data, the information comprising non-address information; andreceiving, from the server and in response to the message, data that is specific to the instance of the device, the data that is specific to the instance of the device comprising eXtensible Markup Language (XML) script containing plural Simple Object Access Protocol (SOAP) commands, the XML script defining a process to be executed by the controller, the process defining timing and sequence of execution of the plural SOAP commands and handling passage of variables among the plural SOAP commands.

2. The method of claim 1, wherein the message includes an operational parameter for the device and the data that is specific to the instance of the device comprises an updated value for the operational parameter.

3. The method of claim 2, wherein the message includes plural operational parameters for the device and the data that is specific to the instance of the device comprises updated values that differ from current values of the operational parameters.

4. The method of claim 1, wherein the data that is specific to the instance of the device comprises a configuration file for the device.

5. The method of claim 1, wherein the message identifies the instance of the device by a device type and/or one or more of a serial number and a universal unique identifier.

6. The method of claim 1, wherein the data that is specific to the instance of the device is received at the device via the Hypertext Transfer Protocol.

7. The method of claim 1, wherein the message includes a first operational parameter for the device and the data that is specific to the instance of the device includes a second operational parameter that is unrelated to the first operational parameter.

8. The method of claim 1, wherein: the data that is specific to the instance of the device is encrypted; andthe method further comprises decrypting the data that is specific to the instance of the device.

9. The method of claim 1, wherein: the data that is specific to the instance of the device contains a digital signature; andthe method further comprises authenticating the digital signature.

10. A system comprising: a controller associated with an instance of a device, the controller being capable of communicating over a computer network; anda server that is capable of communicating over the computer network;wherein the controller is configured to send a message to the server over the computer network that identifies the instance of the device, the message containing information that distinguishes the instance of the device from all other instances of the device for which the server stores data, the information comprising non-address information; andwherein the server is configured to (i) identify the instance of the device based on the message, (ii) retrieve data that is specific to the instance of the device, the data that is specific to the instance of the device comprising eXtensible Markup Language (XML) script containing plural Simple Object Access Protocol (SOAP) commands, the XML script defining a process to be executed by the controller, the process defining timing and sequence of execution of the plural SOAP commands and handling passage of variables among the plural SOAP commands, and (iii) send the data that is specific to the instance of the device to the controller over the computer network.

11. The system of claim 10, wherein the controller is not remotely-addressable from the computer network.

12. The system of claim 10, wherein the computer network comprises the Internet.

13. One or more non-transitory machine-readable media storing a computer program, the computer program being executable by a controller associated with a device to retrieve data from a server, the computer program comprising instructions that cause the controller to: poll the server by sending a message to the server periodically, the message containing information that distinguishes the instance of the device from all other instances of the device for which the server stores data, the information comprising non-address information; andreceive, from the server and in response to the message, data that is specific to the instance of the device, the data that is specific to the instance of the device comprising eXtensible Markup Language (XML) script containing plural Simple Object Access Protocol (SOAP) commands, the XML script defining a process to be executed by the controller, the process defining timing and sequence of execution of the plural SOAP commands and handling passage of variables among the plural SOAP commands.

14. The one or more non-transitory machine-readable media of claim 13, wherein the message includes an operational parameter for the device and the data that is specific to the instance of the device comprises an updated value for the operational parameter.

15. The one or more non-transitory machine-readable media of claim 14, wherein the message includes plural operational parameters for the device and the data that is specific to the instance of the device comprises updated values that differ from current values of the operational parameters.

16. The one or more non-transitory machine-readable media of claim 13, wherein the data that is specific to the instance of the device comprises a configuration file for the device.

17. The one or more non-transitory machine-readable media of claim 13, wherein the message identifies the instance of the device by a device type and/or one or more of a serial number and a universal unique identifier.

18. The one or more non-transitory machine-readable media of claim 13, wherein the data is received at the device via the Hypertext Transfer Protocol.

19. The one or more non-transitory machine-readable media of claim 13, wherein the message includes a first operational parameter for the device and the data includes a second operational parameter that is unrelated to the first operational parameter.

20. The one or more non-transitory machine-readable media of claim 13, wherein: the data that is specific to the instance of the device is encrypted; andthe computer program further comprises instructions that cause the controller to decrypt the data that is specific to the instance of the device.

21. The one or more non-transitory machine-readable media of claim 13, wherein: the data that is specific to the instance of the device contains a digital signature; andthe computer program further comprises instructions that cause the controller to authenticate the digital signature.

22. An apparatus, associated with an instance of a device, for retrieving data from a server, comprising: memory which stores executable instructions; anda controller which executes the instructions to: poll the server by sending a message to the server periodically, the message containing information that distinguishes the instance of the device from all other instances of the device for which the server stores data, the information comprising non-address information; andreceive, from the server and in response to the message, data that is specific to the instance of the device, the data that is specific to the instance of the device comprising eXtensible Markup Language (XML) script containing plural Simple Object Access Protocol (SOAP) commands, the XML script defining a process to be executed by the controller, the process defining timing and sequence of execution of the plural SOAP commands and handling passage of variables among the plural SOAP commands.

23. The apparatus of claim 22, wherein the message includes an operational parameter for the device and the data that is specific to the instance of the device comprises an updated value for the operational parameter.

24. The apparatus of claim 23, wherein the message includes plural operational parameters for the device and the data that is specific to the instance of the device comprises updated values that differ from current values of the operational parameters.

25. The apparatus of claim 22, wherein the data that is specific to the instance of the device comprises a configuration file for the device.

26. The apparatus of claim 22, wherein the message identifies the instance of the device by a device type and/or one or more of a serial number and a universal unique identifier.

27. The apparatus of claim 22, wherein the data is received at the apparatus via the Hypertext Transfer Protocol.

28. The apparatus of claim 22, wherein the message includes a first operational parameter for the device and the data that is specific to the instance of the device includes a second operational parameter that is unrelated to the first operational parameter.

29. The apparatus of claim 22, wherein: the data that is specific to the instance of the device is encrypted; andthe controller executes instructions to decrypt the data that is specific to the instance of the device.

30. The apparatus of claim 22, wherein: the data that is specific to the instance of the device contains a digital signature; andthe controller executes instructions to authenticate the digital signature.