XML-based template language for devices and services
View Patent ↗A universal plug and play (UPnP) device makes itself known through a set of processes-discovery, description, control, eventing, and presentation. Following discovery of a UPnP device, an entity can learn more about the device and its capabilities by retrieving the device's description. The description includes vendor-specific manufacturer information like the model name and number, serial number, manufacturer name, URLs to vendor-specific Web sites, etc. The description also includes a list of any embedded devices or services, as well as URLs for control, eventing, and presentation. The description is written by a vendor, and is usually based on a device template produced by a UPnP forum working committee. The template is derived from a template language that is used to define elements to describe the device and any services supported by the device. The template language is written using an XML-based syntax that organizes and structures the elements.
1. A method comprising:
creating a device template using a template language written in XML syntax;
defining, from the device template, a device description for a self-describing network device; and
automaticallly evaluating, via a computer software tool, whether the device description is well formed.
2. A method as recited in claim 1 , wherein the template language is derived from XML schema.
3. A method as recited in claim 1 , wherein the self-describing network device comprises a universal plug and play device.
4. A method as recited in claim 1 , further comprising storing the device description on a computer-readable medium.
5. A method as recited in claim 1 , further comprising:
creating a service template from a template language written in XML syntax; and
defining, from the service template, a service description for a service supported by the self-describing network device.
6. A method comprising:
creating a service template from a template language written in XML syntax;
defining, from the service template, a service description for a service supported by a self-describing network device; and
automaticallly evaluating, via a computer software tool, whether the device description is well formed.
7. A method as recited in claim 6 , wherein the template language is derived from XML schema.
8. A method as recited in claim 6 , wherein the self-describing network device comprises a universal plug and play device.
9. A method as recited in claim 6 , further comprising storing the service description on a computer-readable medium.
10. A method of describing a a self-describing network device, comprising:
storing a description of the self-describing network device, the description comprising a set of elements to describe the self-describing network device and an XML-based syntax that structures the set of elements such that, when the data structure is read by a computing device, the computing device can learn about the self-describing network device;
making the description available to the computing device; and
wherein the set of elements includes at least one of:
a first element to identify one or more versions of a template lenguage;
a second element to identify the self-describing network device; and
a third element to specify a base universal resource locator (URL).
11. A method as recited in claim 10 , wherein the storing comprises storing the description at the self-describing network device.
12. A method as recited in claim 10 , wherein the self-describing network device comprises a universal plug and play device.
13. A method as recited in claim 10 , wherein the second element includes at least one of:
a first subelement to specify a type of self-describing network device;
a second subelement to identify a user;
a third subelement to identify a manufacturer;
a fourth subelement to specify a URL of a website for the manufacturer;
a fifth subelement to provide a word description of the self-describing network device for the user;
a sixth subelement to specify a model name of the self-describing network device;
a seventh subelement to specify a model number of the self-describing network device;
an eighth subelement to specify a URL of a website for the self-describing network device;
a ninth subelement to specify a URL of a website for a presentation hosted by the self-describing network device;
a tenth subelement to specify a serial number of the self-describing network device;
an eleventh subelement to specify a universal device name of the self-describing network device;
a twelfth subelement to specify a universal product code of the self-describing network device;
a thirteenth subelement to specify any icons associated with the self-describing network device;
a fourteenth subelement to identify any of one or more services supported by the self-describing network device; and
a fifteenth subelement to identify any of one or more devices embedded within the self-describing network device.
14. A method as recited in claim 10 , further comprising storing a set of elements to describe at least one service supported by the self-describing network device.
15. A method as recited in claim 10 , wherein the sotoring comprises storing the description at the self-describing network device, the method further comprising storing a set elements to describe at least one sevice supported by the self-describing network device at a location remite from the self-describing network device.
16. A method of describing a self-describing network device, comprising:
storing a description of the self-describing network device, the description comprising a set of elements to describe the self-describing network device and an XML-based syntax that structures the set of elements such that, when the data structure is read by a computing device, the computing device can learn about the self-describing network device;
making the description available to the computing device; and
storing a set of elements to describe at least one service supported by the self-describing network device, wherein the set of elements to describe the service includes at least one of:
a first element to identify any of one or more actions performed by the service; and
a second element to identify any of one or more state variables in the service.
17. A method as recited in claim 16 , wherein the first element includes at least one subelement for each corresponding action, the subelement containing a name string to hold a name of the action and an argument list to hold parameters of the action.
18. A method as recited in claim 16 , wherein the second element includes at least one of:
a first subelement to identify a name of a state variable;
a second subelement to specify a data type of the state variable;
a third subelement to specify a default value of the state variable;
a fourth subelement to enumerate legal string values; and
a fifth subelement to define bounds of legal numeric values.
19. A data structure stored on a computer-readable medium, the data structure being constructed according to an XML-based template language, the data structured comprising:
a set of elements to describe a self-describing network device; and
an XML-based syntax that organizes and structures the set of elements such that, when the data structure is read by a computing device, the computing device can learn about the self-describing network device;
wherein the set of elements requires:
a first element to identify one or more versions of the template language; and
a second element to identify the self-describing network device.
20. A data structure stored on a computer-readable medium, the data structure being constructed according to an XML-based template language, the data structure comprising:
a set of elements to describe a self-describing network device; and
an XML-based syntax that organizes and structures the set of elements such that, when the data structure is read by a computing device, the camputing device can learn about the self-describing network device;
wherein the set of elements includes at least one of:
a first element to identify one or more versions of the template language;
a second element to identify the self-describing network device; and
a third element to specify abase universal resource locator (URL).
21. A data structure stored as recited in claim 20 , wherein the second element includes at least one of:
a first subelement to specify a type of self-describing network device;
a second subelement to identify a user;
a third subelement to identify a manufacturer;
a fourth subelement to specify a URL of a website for the manufacturer;
a fifth subelement to provide a word description of the self-describing network device for the user;
a sixth subelement to specify a model name of the self-describing network device;
a seventh subelement to specify a model number of the self-describing network device;
an eighth subelement to specify a URL of a website for the self-describing network device;
a ninth subelement to specify a URL of a website for a presentation hosted by the self-describing network device;
a tenth subelement to specify a serial number of the self-describing network device;
an eleventh subelement to specify a universal device name of the self-describing network device;
a twelfth subelement to specify a universal product code of the self-describing network device;
a thirteenth subelement to specify any icons associated with the self-describing network device;
a fourteenth subelement to identify any of one or more services supported by the self-describing network device; and
a fifteenth subelement to identify any of one or more devices embedded within the self-describing network device.
22. A data structure stored on a computer-readable medium, the data structure being constructed according to an XML-based template language, the data structure comprising:
a set of elements to describe a service supported by a self-describing network device; and
an XML-based syntax that organizes and structures the set of elements such that, when the data structure is read by a computing device, the computing device can learn about the service supported by the self-describing network device;
wherein the set of elements includes at least one of:
a first clement to identify any of one or more actions performed by the service; and
a second element to identify any of one or more state variables in the service.
23. A data structure stored as recited in claim 22 , wherein the first element includes at least one subelement for each corresponding action, the subelement containing at least one of a name string to hold a name of the action, an argument list to hold parameters of the action, and a data type of the parameters.
24. A data structure stored as recited in claim 22 , wherein the second element includes at least one of:
a first subelement to identify a name of a state variable;
a second subelement to specify a data type of the state variable;
a third subelement to specify a default value of the state variable;
a fourth subelenient to enumerate legal string values; and
a fifth subelement to define bounds of legal numeric values.
25. One or more computer-readable media, comprising stored thereon:
a first set of elements to describe a self-describing network device, the first set of elements being written in an XML syntax;
a second set of elements to describe a service supported by the self-describing network device, the second set of elements being written in an XML syntax; and
a code segment that, when executed, returns the first set of elements and at least a reference to the second set of elements to an entity requesting a description of the self-describing network device.
26. One or more computer-readable media as recited in claim 25 , wherein the first set of elements are stored on a computer-readable media located at the self-describing network device and the second set of elements are stored on a separate computer-readable medium located remotely from the self-describing network device, but accessible via a network.
27. One or more computer-readable media as recited in claim 25 , wherein the first set of elements includes at least one of:
a first element to identify one or more versions of the template language;
a second element to identify the self-describing network device; and
a third element to specify a base universal resource locator (URL).
28. One or more computer-readable media as recited in claim 25 , wherein the second element of the first set of elements includes at least one of:
a first subelement to specify a type of self-describing network device;
a second subelement to identify a user;
a third subelement to identify a manufanturer;
a fourth subelement to specify a URL of a website for the manufacturer;
a fifth subelement to provide a word description of the self-describing network device for the user;
a sixth subelement to specify a model name of the self-describing network device;
a seventh subelement to specify a model number of the self-describing network device;
an eighth subelement to specify a URL of a website for the self-describing network device;
a ninth subelement to specify a URL of a website for a presentation hosted by the self-describing network device;
a tenth subelement to specify a serial number of the self-describing network device;
an eleventh subelement to specify a universal device name of the self-describing network device;
a twelfth subelement to specify a universal product code of the self-describing network device;
a thirteenth subelement to specify any icons associated with the self-describing network device;
a fourteenth subelement to identify any of one or more services supported by the self-describing network device; and
a fifteenth subelement to identify any of one or mare devices embedded within the self-describing network device.
29. One or more computer-readable media as recited in claim 25 , wherein the second set of elements includes at least one of:
a first element to identify any of one or more actions performed by the service; and
a second element to identify any of one or more state variables in the service.
30. One or more computer-readable media as recited in claim 29 , wherein the first element of the second set of elements includes at least one subelement for each corresponding action, the subelement containing a name string to hold a name of the action and an argument list to hold parameters of the action.
31. One or more computer-readable media as recited in claim 29 , wherein the second element of the second set of elements includes at least one of;
a first subelement to identify a name of a state variable;
a second subelement to specify a data type of the state variable;
a third subelement to specify a default value of the state variable;
a fourth subelement to enumerate legal string values; and
a fifth subelement to define bounds of legal numeric values.
32. One or more computer-readable media as recited in claim 25 , wherein the code segment is configured to respond to an HTTP GET request by returning the description in a body of an HTTP response.
33. A self-describing network device comprising:
a memory;
a description of the self-describing network device stored in the memory, the description comprising a set of elements written in an XML syntax to describe the self-describing network device; and
a processor coupled to the memory to submit the description to a remote entity on a network;
wherein the set of elements comprises at least one of:
a first element to identify one or more versions of a template language;
a second element to identify the self-describing network device; and
a third element to specify a base universal resource locator (URL).
34. A self-describing network device as recited in claim 33 , wherein the description data comprises a first set of elements a first set of elements to describe the self-describing network device and a second set of elements to describe a service supported by the self-describing network device.
35. A self-describing network device as recited in claim 33 , wherein the second element includes at best one of:
a first subelement to specify a type of self-describing network device;
a second subelement to identify a user;
a third subelement to identify a manufacturer;
a fourth subelement to specify a URL of a website for the manufacturer;
a fifth subelement to provide a word description of the self-describing network device for the user;
a sixth subelement to specify a model name of the self-describing network device;
a seventh subelement to specify a model number of the self-describing network device;
an eighth subelement to specify a URL of a website for the self-describing network device;
a ninth subelement to specify a URL of a website for a presentation hosted by the self-describing network device;
a tenth subelement to specify a serial number of the self-describing network device;
an eleventh subelement to specify a universal device name of the self-describing network device;
a twelfth subelement to specify a universal product code of the self-describing network device;
a thirteenth subelement to specify any icons associated with the self-describing network device;
a fourteenth subelement to identify any of one or more services supported by the self-describing network device; end
a fifteenth subelement to identify any of one or more devices embedded within the self-describing network device.
36. A self-describing network device comprising:
memory
a description the self-describing network device stored in the memory, the description comprising a set of elements written in an XML syntax to describe the self-describing network device; and
a processor coupled to the memory to submit the description to a remote entity on a network;
wherein the set of elements includes at least one of:
a first element to identify any of one or more actions performed by a service supported by the self-describing network device; and
a second element to identify any of one or more state variables in the service.
37. A self-describing network device as recited in claim 36 , wherein the first element includes at least one subelement for each corresponding action, the subelement containing a name string to hold a name of the action and an argument list to hold parameters of the action.
38. A self-describing network device as recited in claim 36 , wherein the second element includes at least one of:
a first subelement to identify a name of a state variable;
a second subelement to specify a data type of the state variable;
a third subelement to specify a default value of the state variable;
a fourth subelement to enumerate legal string values; and
a fifth subelement to define bounds of legal numeric values.