# Patent

## Title
XML-based template language for devices and services

## Abstract

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.

## Background
RELATED APPLICATION DATA
This is a continuation of U.S. patent application Ser. No. 09/811,362, entitled “An XML-Based Template Language for Devices and Services,” which was filed on Mar. 16, 2001, and issued as U.S. Pat. No. 6,910,068 on Jun. 21, 2005, which is a continuation-in-part of U.S. patent application Ser. No. 09/496,318, entitled “Dynamic Self-Configuration For Ad Hoc Peer Networking”, filed Feb. 1, 2000, now U.S. Pat. No. 6,892,230 which is based on provisional application No. 60/139,137 filed Jun. 11, 1999, and provisional application No. 60/160,235 filed Oct. 18, 1999. This also claims priority to provisional application No. 60/190,943, filed Mar. 21, 2000, which is hereby incorporated by reference.


TECHNICAL FIELD
This invention relates generally to dynamic connectivity among distributed devices and services, and more particularly relates to providing a capability for devices to automatically self-configure to interoperate with other peer networking devices on a network, such as in a pervasive computing environment.
BACKGROUND AND SUMMARY
The cost of computing and networking technologies have fallen to the point where computing and networking capabilities can be built into the design of many electronic devices in the home, the office and public places. The combination of inexpensive and reliable shared networking media with a new class of small computing devices has created an opportunity for new functionality based mainly on the connectivity among these devices. This connectivity can be used to remotely control devices, to move digital data in the form of audio, video and still images between devices, to share information among devices and with the unconstrained World Wide Web of the Internet (hereafter “Web”) and to exchange structured and secure digital data to support things like electronic commerce. The connectivity also enables many new applications for computing devices, such as proximity-based usage scenarios where devices interact based at least in part on geographical or other notions of proximity. A prevalent feature of these connectivity scenarios is to provide remote access and control of connected devices and services from another device with user interface capabilities (e.g., a universal remote controller, handheld computer or digital assistant, cell phones, and the like). These developments are occurring at the same time as more people are becoming connected to the Internet and as connectivity solutions are falling in price and increasing in speed. These trends are leading towards a world of ubiquitous and pervasive networked computing, where all types of devices are able to effortlessly and seamlessly interconnect and interact.
In the above ubiquitous and pervasive networked computing scenarios, the devices desirably can interoperate on an ad hoc peer-to-peer networking connectivity basis. Such a peer networking connectivity model enables any networked device to initiate a communication with any other networked device, without having established a prior relationship or maintaining a persistent relationship between the devices. This peer networking connectivity also allows multiple devices to establish one or more connections with a single device, and it allows for a device to be capable of both initiating and accepting connections to/from other devices.
The prevalent model for device connectivity, however, has been that of host-peripheral connectivity, typified by the personal computer and its many peripheral devices (e.g., data storage drives, user input devices, displays, printers, scanners, etc.) connected via various buses (e.g., PCI, VESA, AGP, Microchannel, ISA, EISA, USB), ports (e.g., serial, parallel), and connectors (e.g., PS/2 connector). This host-peripheral connectivity model is characterized in that the host and peripherals typically have persistent relationships and stable configurations. This persistent relationship is created, by example, through a set-up and configuration process through which appropriate driver software is installed by a user or administrator onto the host for use in controlling the peripheral, and updating the host's configuration to include peripheral device settings. Such persistent configured relationships with a user installation/configuration experience are generally inappropriate to the ubiquitous and pervasive computing environment where portable and mobile devices desirably can instantly connect and interact with other computing devices in their environment without having established prior or persistent relationships.
More specifically, two common computing networks where many of these small, network-capable computing devices are expected to be used include the home and small office. Such networks are commonly not actively managed by experienced administrators. In fact, due to the lack of networking experience of a large majority of the users of these networks, lengthy, complex and/or involved user installation and setup experiences pose a significant impediment to adoption and penetration of such networks and devices into homes and small offices.
Further, the establishment of persistent relationships with other devices in the configuration of these small, network-capable computing devices is inappropriate to many usage scenarios. For example, portable computing devices (such as a handheld computer or digital assistant, cell phones, and the like) may be used to access information (such as transportation departure/arrival times, store locations, etc.) from other devices on networks in public places (such as malls and airports). Not only would a user installation/configuration experience upon each such use pose an inconvenience, but the establishment of persistent configuration information poses configuration management issues and consumes device resources. As another example, devices (such as printers, scanners, monitors and etc.) on an office or home network may interact with many portable computing devices (such as the laptops, cameras, and other equipment of the mobile professional) that are introduced into its network. Again, in device connectivity models requiring establishing persistent device relationship configurations, such one-time and occasional relationships between these devices would results in configuration instability requiring management and maintenance of ever-changing persistent device configurations. Due to the time and cost (or lack on active administration of these devices, any requirement to manage and maintain changing persistent device configurations on networked devices is undesirable.
Accordingly, there is a need for a device connectivity model that supports ad hoc peer networking among computing devices with preferably zero user installation or configuration experience and without persistent device configuration.
In accordance with a technology described herein, a universal plug and play (UPnP) device makes itself known and available for communication with other entities on a network through a set of processes—discovery, description, control, eventing, and presentation (herein also termed “self-bootstrapping”). Following discovery of a UPnP device, an entity can learn more about the device and its capabilities, or interact with the device, by retrieving the device's description from a URL provided by the device in an initial discovery message.
The description is expressed in XML and 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 standard device template produced by a UPnP forum working committee. The template is derived from a template language that utilizes standard XML constructions. The template language includes a first set of elements to describe the UPnP device and a second set of elements to describe any services supported by the device. The template language is written using an XML-based syntax that organizes and structures the first and second sets of elements.
Additional features and advantages will be made apparent from the following detailed description of the illustrated embodiment, which proceeds with reference to the accompanying drawings.



BRIEF DESCRIPTION OF THE DRAWINGS
FIGS. 1 and 2 are block diagrams of a device architecture per Universal Plug and Play using user control points, controlled devices and bridges for connectivity between devices.
FIG. 3 is a block diagram of a device model per Universal Plug and Play.
FIG. 4 is a block diagram illustrating example devices conforming to the device model of FIG. 3.
FIG. 5 is a block diagram illustrating device state synchronization using a state table and eventing.
FIG. 6 is a block diagram of layers in a self-bootstrapping process including addressing, naming, discovery and description layers per the device control model of FIG. 3.
FIG. 7 is a block diagram illustrating device addressing.
FIG. 8 is a block diagram of a programmatic interface-to-network messaging adapter or Rehydrator in the device control model of FIG. 3.
FIG. 9 is a general data flow diagram of the Rehydrator of FIG. 8 in the device control model of FIG. 3.
FIG. 10 is a block diagram of an implementation design of the Rehydrator of FIG. 8.
FIGS. 11 and 12 are block diagrams illustrating an internal software architecture of the user control point and controlled device in the device control model of FIG. 3.
FIG. 13 is a block diagram illustrating an internal software architecture of a combined bridge and user control point in the device control model of FIG. 3.
FIG. 14 is a data flow diagram illustrating a typical browsing protocol sequence in the device control model of FIG. 3.
FIG. 15 is a listing showing a layout of a description document in the device control model of FIG. 3.
FIG. 16 is a listing of an exemplary icon list of a Description Document in the device control model of FIG. 3.
FIG. 17 is a listing of an exemplary service control protocol declaration in a Description Document in the device control model of FIG. 3.
FIGS. 18, 19, and 20 are a listing of an XML schema for a contract in the device control model of FIG. 3.
FIGS. 21 and 22 are a listing of an XML schema for a Service Control Protocol Declaration Language used in the device control model of FIG. 3.
FIG. 23 is a block diagram of an exemplary implementation of an eventing model used in the device control model of FIG. 3.
FIG. 24 is a data flow diagram illustrating subscription, notification and unsubscription in the eventing model of FIG. 23.
FIG. 25 is a block diagram of a computer system that may be used in the device control model of FIG. 3.
FIG. 26 is a block diagram of a device having embedded computing and networking capability per Universal-Plug-and-Play (UPnP) standards that may be used in combination with the computer system of FIG. 25 in the device control model of FIG. 3.
FIG. 27 is a block diagram of a software architecture per UPnP standards in the embedded computing device of FIG. 26
FIG. 28 is a data flow diagram of a process for automatic network introduction of the embedded computing device of FIG. 26 into an ad hoc computer network environment per the UPnP protocol.
FIG. 29 is a data flow diagram of a process for automatic network introduction of the embedded computing device of FIG. 26 into a configured computer network environment per the UPnP protocol.
FIG. 30 is a block diagram of a software architecture of a client device per UPnP standards having embedded computing and networking capability that may be used in the device control model of FIG. 3.
FIG. 31 is a block diagram of an exemplary home or office pervasive computing environment having a variety of computers as per FIG. 25 and embedded computing devices as per FIG. 26 interconnected per UPnP standards that may be used in the device control model of FIG. 3.
FIGS. 32 through 44 are program listings of interfaces used in the Rehydrator implementation design of FIG. 10.
FIGS. 45-47 are an XML format listing that depicts an exemplary contract for interacting with a stock quote Service.
FIGS. 48-51 are an XML format listing that depicts an XML schema for defining Contracts.



DETAILED DESCRIPTION
The following detailed description is directed toward self-bootstrapping or automatic dynamic self-configuring of devices for ad hoc peer networking with other devices on a computing network that avoid user installation experience, persistent relationship configurations, and software driver downloads. In one described implementation, this self-bootstrapping is used in a device architecture 100 (FIG. 1), connectivity model, and device control protocol proposed by Microsoft Corporation, called Universal Plug and Play (“UPnP”).
Universal Plug and Play
Universal Plug and Play (UPnP) is an open network architecture that is designed to enable simple, ad hoc communication among distributed devices and services from many vendors. UPnP leverages Internet technology and can be thought of as an extension of the Web model of mobile Web browsers talking to fixed Web servers to the world of peer-to-peer connectivity among mobile and fixed devices. UPnP embraces the zero configuration mantra of Plug and Play (PnP) but is not a simple extension of the PnP host/peripheral model.
The cost, size and battery consumption of computing technology—including processing, storage and displays—continues to fall. This trend is enabling the evolution of stand-alone, single or limited function computing devices such as digital cameras, audio playback devices, smart mobile phones and handheld computers. Concurrent with this, the economical storage and transmission of digital audio, video and still images is enabling highly flexible models for managing entertainment content.
While many of these devices are capable of useful stand-alone operation, seamless connectivity with the PC can enhance the value to the customer of both stand-alone devices and the PC. Good examples of this synergy are digital image capture combined with PC image manipulation, storage and email transfer/Web publishing and information synchronization between a PC and a handheld computer or smart mobile phone.
Since many of these devices, and the PC itself, are mobile, a suitable communication architecture must enable a highly dynamic connectivity model and must enable peer-to-peer operating among arbitrary combinations of devices.
The Internet has created a widespread awareness of the value of simple, universal communication that is independent of the underlying transmission technology and independent of technology from any single vendor.
UPnP makes it possible to initiate and control the transfer of bulk data (e.g. files) or A/V data streams from any device on the network, to any device on the network, under the control of any device on the network. UPnP enables the ad hoc addition or removal of devices on the network, and it enables multiple controlling devices to remain in sync with each other.
UPnP reuses existing protocols and technology whenever possible. The transition to this highly connected (and connectable) world will not occur overnight. UPnP builds on existing Internet protocols, but accommodates devices that cannot run the complete UPnP protocol suite. UPnP provides an architecture that enables legacy devices to communicate with UPnP devices.
IP internetworking has been chosen as a UPnP baseline due to its proven ability to span different physical media, to enable real world multiple vendor interoperation and to achieve synergy with the Internet and home and office intranets. Internet synergy enables applications such as IP telephony, multiple player games, remote control of home automation and security, Internet based electronic commerce, in addition to simple email and Web browsing. UPnP's scope includes remote control of devices and bulk data transfer, and can be easily extended to specify A/V streaming.
UPnP's media independence enables a great deal of flexibility in the packaging of products. UPnP enables an A/V system to be controlled through an A/C power communications technology, while the transmission of A/V streams among the components is analog or digital. One of the controllers of this system could be on the television, while another is on a PC, and yet another connected via radio or infrared.
Unlike Plug and Play, Universal Plug and Play is built on top of networking and enables ad hoc peer-to-peer connectivity. Networking, in this context, describes a style of connectivity that enables any networked device to initiate a communication with any other networked device, without having established a prior relationship or maintaining a persistent relationship between the devices. Networking also allows multiple devices to establish one or more connections with a single device, and it allows for a device to be capable of both initiating and accepting connections to/from other devices. The PnP, or host/peripheral, model is suitable whenever there is a natural persistent relationship between two devices (e.g. a keyboard, mouse and display maintain and a persistent relationship with a host computer). Even though networking does not mandate low level persistent relationships, it provides the needed anchors (addresses) for applications to choose to maintain associations as a convenience for the customer (e.g. remembering commonly used networked printers).
In order to achieve multiple vendor peer-to-peer interoperation among devices, vendors desirably agree on common technology and standards up to the highest level of desired functional interoperation.
UPnP leverages formal protocol contracts to enable peer-to-peer interoperation. Protocols contracts enable real-world multiple-vendor interoperation.
UPnP provides a device-driven auto-configuration capability that preserves the experience that customers have on the Web. Today, it is possible to navigate around the Web without loading programs beyond the browser itself. UPnP enables the browser to be extended to control devices. Because UPnP devices are controlled with explicit protocols, the browser must somehow learn how to talk to UPnP devices. This learning process is driven entirely from the device itself and is accomplishing entirely by uploading an XML document that describes the capabilities of the device. The architectural component that enables device-driven auto-configuration is called the Rehydrator. The job of the Rehydrator is to convert between APIs and protocols.
There are some scenarios where the Web UI model is not sufficient for a rich customer experience. It would not be convenient to have a separate Web interface for each light switch in a house. To support a rich user interface and to enable the aggregation of devices into a single UI, UPnP enables application control in addition to browser control of devices. This is achieved simply by enabling applications to call the same Rehydrator APIs that the browser does. Applications can also directly generate and consume the raw UPnP control protocols, provided they are not interested in the device-driven auto-configuration enabled by the Rehydrator.
UPnP assumes that there will be more than one device with UI that wants to control other devices in any given network, and it provides a simple mechanism that enables these control points to remain in sync. This mechanism can easily support device front panels and wireless remotes that do not run UPnP protocols. The UPnP control model is third-party control; any device can transfer bulk data (e.g. files) or A/V data streams from any device on the network, to any device on the network, under the control of any device on the network.
Terminology
The detailed description that follows uses the terminology defined below.
Module. A component of a device, software program, or system that implements some “functionality”, which can be embodied as software, hardware, firmware, electronic circuitry, or etc.
User Control Point. The set of modules that enable communication with a UPnP Controlled Device. User Control Points initiate discovery and communication with Controlled Devices, and receive Events from Controlled Devices. User Control Points are typically implemented on devices that have a user interface. This user interface is used to interact with Controlled Devices over the network. The modules minimally include a Discovery Client, a Description Client, a Rehydrator, an Event Subscription Client and an Event Sink,. User Control Points may also include Visual Navigation, a Web browser and an application execution environment. User Control Points can add value to the network by aggregating the control of multiple Controlled Devices (the universal remote) or they can implement a function as simple as initiating the transfer of data to or from a Controlled Device. Examples of devices that could be User Control Points are the personal computer (PC), digital television (DTV), set-top box (STB), handheld computer and smart mobile phone, and the like. Nothing prevents a single device from implementing the functionality of a User Control Point and one or more Controlled Devices at the same time.
Controlled Device. The set of modules that perform certain tasks (e.g., printing) and communicate with a User Control Point. Controlled Devices respond to discovery requests, accept incoming communications from User Control Points and may send Events to User Control Points. Devices that support Controlled Device functionality may also support local user interfaces such as front panel displays or wireless remotes. The modules minimally include a Discovery Server, a Description Server, a Control Server, an Event Subscription Server and an Event Source. Controlled Devices may also include a Presentation (e.g., Web) Server. Examples of devices that could be Controlled Devices are the VCR, DVD player or recorder, heating/ventilation/air-conditioning equipment (HVAC), lighting controller, audio/video/imaging playback device, handheld computer, smart mobile phone and the PC, and the like. Nothing prevents a single device from implementing the functionality of a User Control Point and one or more Controlled Devices at the same time.
Bridge. A set of modules that enables Bridged and Legacy Devices to interact with native UPnP devices. The bridge itself exposes a collection of UPnP Controlled Devices to User Control Points. The Bridge maps between native UPnP Device Control Protocols and the underlying protocols or other control methods exposed by the Bridged and Legacy Devices. Optionally, such a device could expose UPnP Controlled Devices to Legacy Devices in the manner required by the Legacy Devices. Nothing prevents a single device from implementing the functionality of a User Control Point, one or more Controlled Devices and a Bridge at the same time.
Service Provider. A module used by a UPnP Bridge that translates between UPnP protocols and the protocols used by Bridged and Legacy Devices. No Service Providers are required for communication among native UPnP devices.
Bridged Device. A device that cannot participate in UPnP at the native protocol level, either because the device does not have sufficient resources or because the underlying media is unsuitable to run TCP and HTTP. Examples of devices that could be Bridged Devices are power line-controlled A/V equipment, light switches, thermostats, wristwatches and inexpensive toys. Bridged Devices are UPnP complaint and are exposed to other UPnP devices through a UPnP Bridge.
Legacy Device. Any non-UPnP compliant device that must be exposed to other UPnP devices through a UPnP Bridge.
Device Model. The UPnP model of Controlled Devices. The Device Model includes the addressing schemes, Description Document, Devices and Services hierarchy and the functional description of Services.
Device Control Protocol (DCP). A complete set of UPnP protocols and schemas used to interact with a UPnP Controlled Device.
Device Definition. The formal definition of a Device Type. A Device Definition includes a Device Type Identifier, the fixed elements in the Description Document, the required set of Service Definitions in the Root Device, and the hierarchy of required Devices and Service Definitions.
Service Definition. The formal definition of a Service Type. A Service Definition includes a Service Type Identifier, definition of the Service State Table (SST), definition of the Service Command Set, the Service Control Protocol (SCP) and Service Control Protocol Declaration (SCPD).
Device. In the context of the Device Model, a container for Services. A Device generally models a physical entity such as a VCR, but can also represent a logical entity. A PC emulating the traditional functions of a VCR would be an example of a logical device. Devices can contain other Devices. An example would be a TV/VCR packaged into a single physical unit. UPnP enables the association of user interface (display icon and root Web page) with every Device, including Root Device.
Root Device. The topmost Device in a hierarchy of nested Devices. A Device with no nested Devices is always a Root Device.
Device Type. A relatively high level classification of Devices with common functionality. Device Type is intended to enable Devices to be simply and automatically grouped for search and/or presentation. An example of a Device Type is “VCR”. Device Types are formally defined in terms of a required set of Service Definitions of minimum version that a compliant Device must support. UPnP supports searches for all Devices of a specified Device Type.
Device Type Identifier. A unique identifier that identifies a Device Definition. This identifier adheres to the format of a Uniform Resource Identifier (URI). See, T. Berners-Lee, R. Fielding, L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax”, which can be found at http://www.ietf.org/rfc/rfc2396.txt.
Device Friendly Name. A human readable string that is usually initialized by vendors at the time of manufacturer of a Device. Every Device, including Root Devices, has a Device Friendly Name. A typical Device Friendly Name will contain manufacturer and model information, and especially when interpreted by humans, can be used to enable a more precise identification of a UPnP Device from the set of discovered Devices. Once identified, the Unique Device Name (UDN) can be used to unambiguously identify the same Device in the future. UPnP enables Device Friendly Names to be changed by User Control Points. The Device Friendly Name should not be used as device identifier.
Unique Device Name (UDN). The fundamental identifier of a Device. Every Device, including Root Devices, has exactly one UDN. The UDN is globally unique and permanent, even across power cycles and physical location changes. The UDN is the only UPnP device identifier guaranteed never to change. UPnP enables searches for devices by UDN.
Description Document. A structured unit of data that is used by a User Control Point or UPnP Bridge to learn the capabilities of a Controlled Device. Description Documents are retrieved from the Description Server on a UPnP Controlled Device. There is one Description Document for every Root Device that describes the Root Device and all non-Root Devices. Description Documents adhere to XML grammar. To support localization, multiple Description Documents can exist. A User Control Point requests the preferred localized Description Document by using the standard HTTP “accept-language” header.
Service. The fundamental UPnP controllable entity (but not the finest level of control). An example of a Service is “Clock”. Services are defined with a mandatory common base set of functionality. Vendors can extend the base set with proprietary extensions provided the base functionality is implemented. Service Definitions are versioned and later versions are constrained to be supersets of previous versions. UPnP enables searches for all Devices that contain a specified Service of a minimum version. This search would find all clocks, regardless of their packaging. A search for Device Type “Clock” would be used to find only stand-alone clocks.
Service Type. A classification of Services by their function.
Service Type Identifier. A unique identifier that identifies a Service Definition. This identifier adheres to the format of a Uniform Resource Identifier (URI). See, T. Berners-Lee, R. Fielding, L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax”, which can be found at http://www.ietf.org/rfc/rfc2396.txt.
Service State Table (SST). A logical table consisting of rows of [Variable, Type, Legal Values, Default Value, Current Value] that represents the current electrical, mechanical and/or logical state of a Service. SST instances are stored on the Controlled Device itself and are the ultimate authority of the state of the Service. All local user interface, such as front panels or wireless remotes are required to update the SST on UPnP compliant devices.
SST Definition:
Service Command Set. A set of Commands that can be invoked on a Service. Commands generally result in changes in the Current Value field of one or more rows of a SST. Commands are logically represented in the format Command (Variable=New Value, Variable=New Value, . . . ). Services must accept or reject the complete set of changes to a SST. There is a mandatory standard Query Command that is used to retrieve the Current Value of any row of a SST.
Service Command Set Definition:
Service Control Protocol (SCP). The protocol used to invoke Commands against a Service and to return results. There is exactly one SCP per Service Definition. SCPs adhere to the grammar of SCP XML schema. SCPs can be generated by an automated tool that accepts a SST Definition and a Command Set Definition as input.
Service Control Protocol Declaration (SCPD). A formal representation of the schema of a Service. The SCPD declares the rows of a Service's SST and the associated Command Set. SCPDs are uploaded from Controlling Devices in their Description Documents and enable User Control Points or Bridges to invoke Commands on the Service without any prior or persistent knowledge of the capabilities (or schema) of the Service. There is exactly one SCPD per Service Definition. SCPDs adhere to XML grammar. SCPDs can be generated by an automated tool that accepts a SST Definition and a Command Set Definition as input.
Event. An unsolicited message generated by a Controlled Device and delivered to one or more User Control Points. Events are used to maintain a consistent view of the state of Service across all interested User Control Points. UPnP leverages the GENA event architecture (see “Generic Event Notification”) to transport event messages. All events are delivered using TCP/IP for reliability.
Generic Event Notification Architecture (GENA). An event transport protocol. GENA leverages TCP/HTTP as a transport. GENA has been submitted as an Internet Draft to the IETF. See, J. Cohen, S. Aggarwal, Y. Goland, “General Event Notification Architecture Base: Client to Arbiter”, which can be found at http://www.ietf.org/internet-drafts/draft-cohen-gena-client-00.txt.
Simple Service Discovery Protocol (SSDP). A simple network device discovery protocol. UPnP uses SSDP to allow User Control Points to find Controlled Devices and Services. SSDP operates in a default, completely automatic multicast UDP/IP based mode in addition to a server-based mode that uses TCP/IP for registrations and query. Transitions between the default dynamic mode and server-based mode are automatic and transparent to upper level software. SSDP enables every Controlled Device to control the lifetime that its Description URL is cached in all User Control Points. This enables a Controlled Device to remain visible to User Control Points for a relatively long time (through power cycles), in addition to enabling a Controlled Device to appear and disappear very quickly, all under the control of the Controlled Device. SSDP and related Multicast and Unicast UDP HTTP Messages specifications have been submitted as Internet Drafts to the IETF. See, Y. Goland, “Multicast and Unicast UDP HTTP Messages”, which can be found at http://www.ietf.org/internet-drafts/draft-goland-http-udp-00.txt; and Y. Goland, T. Cai, P. Leach., Y. Gu, S. Albright, “Simple Service Discovery Protocol/1.0”, which can be found at http://www.ietf.org/internet-drafts/draft-cai-ssdp-v1-02.txt.
Client. In the context of UPnP, Client refers to a module that initiates a TCP/HTTP connection to a peer HTTP server.
Server. In the context of UPnP, Server refers to an HTTP server. This is a module that accepts incoming TCP/HTTP connections and either returns a Web page or forwards the payload data to another module. Client and Server describe only the direction of initiation of TCP/HTTP connections. There is no relationship between the low level concepts of Client and Server and the high level concepts of User Control Point and Controlled Devices. Logically, User Control Points always discover and initiate communication with Controlled Devices, but this communication requires Client and Server functionality on both sides.
Hostname. A Hostname is the Domain Name System (DNS) or NetBIOS Name Service (NBNS) that, when resolved to an IP address, represents a network interface that can be used to establish TCP/IP level connectivity to User Control Points, Controlled Devices or Bridges. Hostnames can be used to provide persistent network level addressing on a network where IP addresses are dynamically assigned and of unknown lifespan or to integrate with an existing managed network. UPnP provides an algorithm for seeding a device's hostname from its UDN at manufacturing time.
Uniform Resource Locator (URL). A format for expressing Web addresses. URLs minimally contain an identification of the protocol family that the URL is valid for, a Hostname, and a path. UPnP uses URLs as addresses whenever the module accepting the incoming connection is an HTTP server.
Description URL. The URL returned from a Controlled Device or Bridge in response to any UPnP SSDP query. This URL always points to a Description Server on the Controlled Device. An HTTP GET can be issued on this URL to retrieve the Description Document. This URL is valid as an address for the lifetime of the Hostname embedded in the URL.
Discovery Server. The module that runs in a Controlled Device or Bridge that responds to SSDP queries. This Server is unique in that it must support UDP/HTTP in addition to TCP/HTTP.
Discovery Client. The module that runs in a User Control Point that initiates SSDP queries.
Description Server. The module that runs in a Controlled Device or Bridge that responds to HTTP GETs and returns Description Documents. This service consists of a TCP/HTTP server than can retrieve and return a Description Document from persistent storage (like a filesystem).
Visual Navigation. User Control Point functionality that displays the icons of discovered Devices and enables the transfer of control to a browser or application to interact with the Controlled Device. In Windows, Visual Navigation could be implemented as a folder of icons.
Presentation URL. A URL that can be used by a User Control Point to navigate to the Presentation Server of a Controlled Device. This URL is returned in the Description Document and is valid as an address for the lifetime of the Hostname embedded in the URL. All Devices, including non-Root Devices, can have an associated Presentation URL.
Presentation Server. A Web Server in most common cases. The module that runs in a Controlled Device that responds to HTTP GETs or Presentation URLs and returns user interface using Web technologies (JavaScript, Jscript®, ECMAScript, VBScript, ActiveX®, Java Applet, etc.).
Browser. A Presentation Client. A Web browser extended with a Rehydrator.
Control URL. A URL that can be used by a User Control Point to navigate to the Control Server of a Controlled Device or Bridge. This URL is returned in the Description Document and is valid as an address for the lifetime of the Hostname embedded in the URL. All Services have an associated Control URL.
Control Server. The module that runs in a Controlled Device or Bridge that responds to Commands invoked on a Service by a User Control Point. Commands are encoded and sent using the SCP specified in the Service Definition. This service consists of a TCP/HTTP server that passes control to the native control logic of a Service, updates the SST and generates an event if the SST changes.
Rehydrator. In UPnP, a Control Client. A User Control Point module that translates between native operating system APIs and SCPs and events. The Rehydrator uploads SCPDs from Controlled Devices and Bridges and generates appropriate SCPs in response to application API requests to invoke Commands.
Event Subscription URL. A URL that can be used by a User Control Point to navigate to the Event Subscription Server of a Controlled Device or Bridge. This URL is returned in the Description Document and is valid as an address for the lifetime of the Hostname embedded in the URL. All Services have an associated Event Subscription URL.
Event Subscription Server. The module that runs in a Controlled Device or Bridge that responds to GENA SUBSCRIBE requests from User Control Points. A SUBSCRIBE informs the Controlled Device or Bridge of the User Control Point's desire to receive future events. This service consists of a TCP/HTTP server that adds the User Control Point's Event Sink URL to the list of destinations to be NOTIFY'd whenever the SST associated with the Service changes.
Event Subscription Client. The module that runs in a User Control Point that sends GENA SUBSCIBE messages to the Event Subscription Server.
Event Sink URL. A URL, supplied by a User Control Point, that is used as an address to send event NOTIFYs to. This URL is valid as an address for the lifetime of the Hostname embedded in the URL. There is no explicit relationship between Event Sink URLs and Subscription Identifiers.
Subscription Identifier (SID). A header in the GENA NOTIFY message that identifies the source of an event. In UPnP, the SID can be considered as an alias for the Event Source instance.
Event Sink. The module that runs in a User Control Point that accepts incoming GENA event NOTIFYs. This service consists of a TCP/HTTP server that passes the event information to interested applications running on the User Control Point.
Event Source. The module that runs in a Controlled Device or Bridge that sends GENA NOTIFYs to the Event Sink Servers of SUBSCRIBES User Control Points.
Domain Name System (DNS). A distributed system of servers that locates the IP addresses of other computers on a network based on their hierarchical names.
NetBIOS Name Server (NBNS). A server that locates the IP addresses of other computers on a network based on their flat NetBIOS computer names.
Multicast DNS (MDNS). A peer-to-peer translation scheme that does not require involvement of DNS servers.
UPnP Technologies Overview
An overview of technologies utilized in UPnP follows.
Device Discovery: Simple Service Discovery Protocol (SSDP)
TCP/IP provides the ability to initiate a connection with a specified application running on a specific device, provided both the network address of the device (IP address) and the application address (port) are known. Generally, application addresses (ports) are standardized and widely known, but the problem of learning the IP address of a device remains.
Simple Service Discovery Protocol (SSDP) is a protocol that enables devices to learn of the existence of potential peer devices and the required information (an IP address) needed to establish TCP/IP connections to them. The successful result of an SSDP search is a Uniform Resource Locator (URL). The Hostname embedded in the URL can be resolved to an IP address that can be used to make a connection to the discovered device. The name to address resolution is outside of the functionality of SSDP.
SSDP specifies a default, completely automatic, best-effort multicast UDP-based operating mode, in addition to a server mode that uses TCP for registration and query. Fall-forward to server mode and fallback to the default dynamic mode can occur automatically and transparently as a server is added or removed from a network. Server mode can be used to reduce network traffic, to implement searches based on location or policy and to integrate with a directory system.
SSDP requires that all devices specify a maximum lifetime that SSDP level knowledge of the device will remain cached in other network devices. If a device does not refresh the cache of other network devices before this interval expires, the device will be assumed to have disappeared from the network. This interval can be chosen to be larger than a typical power down cycle to enable device visibility to persist for a relatively long time, or a smaller interval can be chosen to enable more dynamic visibility control. In all cases, devices that are abruptly removed from the network will eventually disappear from all networked devices.
In response to an SSDP search, UPnP devices return a Description URL in the SSDP Location and optionally the Alternate Location (AL) SSDP headers. An example location header is a follows:

    
    
        Location: http://device.local/description/path/description.xml
    
    


In this example, the device.local is the Hostname of the Controlled Device, and the “description/path/description.xml” element of the URL is the path and name of the Description Document on the device.
Eventing: Generic Eventing Notification (GENA)
Eventing, in the context of UPnP, is the ability for a device to initiate a connection at any time to one or more devices that have expressed a desire to receive events from the source device. Events are used to enable synchronization among multiple devices organized into a many to one relationship. UPnP events are mainly used for asynchronous notifications of state changes.
TCP/IP provides the fundamental support for the connections that carry event information reliably. Generic Event Notification (GENA) adds conventions for establishing relationships between interested devices and an addressing scheme to enable the unambiguous delivery of events. GENA leverages HTTP addressing and encapsulation.
User Control Points, Controlled Devices and Bridges
With reference now to FIGS. 1 and 2, UPnP is an application-level distributed network architecture where the logical nodes on the network are User Control Points 104-105, Controlled Devices 106-107 and Bridges 120. These classifications refer to functionality rather than physical entities. The functionality of UPnP User Control Points 104-105, Controlled Devices 106-107 and Bridges 120 can be packaged into physical entities (e.g., multiple function devices 102-103) in any combination.
The primary distinction between a User Control Point 104-105 and a Controlled Device 106-107 is that the User Control Point is always the communication initiator. After the initial communication, User Control Points can receive events from Controlled Devices.
Controlled Devices 106-107 are responsible for storing and updating the state of Services. User Control Points are required to synchronize to the state on Controlled Devices and to share state directly among themselves.
User Control Points typically have user interface that is used to access one or more Controlled Devices on the network. Controlled Devices typically only have local user interfaces.
Bridges 120 (FIG. 2) expose devices that do not expose native UPnP protocols as native UPnP Controlled Devices. The Bridge itself looks to other UPnP User Control Points like a set of Controlled Devices.
The following table lists the modules in the User Control Points 104-105 and Controlled Devices 106-107, along with their functions.











User Control Point
Controlled Device










Function
Module
Function
Module





Initiate discovery
Discovery Client
Respond to
Discovery


of Controlled

discovery
Server


Devices.

requests.


Retrieve
Description Client
Provide
Description


Description

Description
Server


Documents.

Documents.


Display a folder
Visual Navigation


of icons per


discovered


Device and allow


transfer of


control to a


selected device.


View user
Web Browser
Provide user
Presentation


interface exposed

inteface for
(Web) Server


by a Controlled

remote User


Device.

Control Points.


Execute
Application


applications.
Execution



Environment


Invoke
Rehydrator
Accept incoming
Control Server


Commands on a

Commands in
plus native


Controlled Device

SCPs and
control logic


by sending

execute them.


Service Control


Protocols in


response to local


API calls.


Inform a
Event
Accept requests
Event


Controlled Device
Subscription
for Events and
Subscription


of a desire to
Client
remember them.
Server


receive Events.


Receive an Event.
Event Sink
Send an Event.
Event Source









Device Model
The UPnP Device Model 200 shown in FIG. 3 is the model of a UPnP Controlled Device or Bridge that is emulating native Controlled Devices. The Device Model includes the addressing scheme, eventing scheme, Description Document schema, Devices and Services schema and hierarchy, and the functional description of modules. The UPnP Device Model extends beyond simple API or a command and control protocol definitions to enable multiple User Control Points to have a consistent view of Controlled Devices. This requires that the state of running services be formally modeled and that all state changes be visible to User Control Points. Central to the distributed UPnP architecture is the rule that Controlled Devices are the ultimate authority for the state of Services running on them.
Service
The fundamental controllable entity in UPnP is a Service 210-217. Every running instance of a Service includes:

    
    
        A Service State Table (SST) 230, which represents the current state of the Service.
    
    


The SST 230 can be used to represent the operational mode of device or to act as an information source or sink for structured data or simple files. The SST of a VCR 254 (FIG. 4) could represent the current transport mode, tuner channel selection, input and output switch selections, audio and video decoding format and current timer program. The SST of clock 251 (FIG. 4) would likely represent the current time. The SST of an image rendering device could implement a video frame-buffer that can accept raw pixel information or formatted JPG files. The SST of an audio or video playback device could implement a transfer buffer or queue of material to be played. The SST of PDA could implement a collection of formatted data that has changed and needed to be synchronized with another device, in addition to a transfer buffer for accepting incoming formatted data.
The logical structure of a SST published in the Service Definition, but the actual storage format of an instance of a SST is entirely up the device. The only interaction with a SST is through a formal application level network protocol.

    
    
        A Control Server 232, which accepts incoming Commands expressed in the Service's Service Control Protocol (SCP). The Control Server passes the command to the Service's native command processing logic and waits for command completion. When the command is completed successfully, the SST is updated, an event is generated, and a successful response is returned to the User Control Point. In the event of an illegal command or unsuccessful command, no changes are made to the SST and a failure response is returned. The Command and response sequence is payload to a TCP/HTTP request/response.
        An Event Subscription Server and Event Source 234. The Event Subscription Server accepts incoming GENA SUBSCRIBE messages from User Control Points and adds them to a list of User Control Points interested in SST change events from the Service. The Event Source initiates a TCP/HTTP connection to each interested User Control Point and sends a GENA NOTIFY each time the Service's DST changes. The NOTIFY payload includes the changed contents of the DST.
        A Control URL that identifies the Control Server.
        An Event URL that identifies the Event Subscription Server.
    
    


The formal definition of a Service (Service Definition) includes:

    
    
        The definition of the SST. SST layouts are logically specified in terms of rows of [Variable, Type, Legal Values, Default Value]. The actual instance of a SST would also include a Current Value field in every row.
        The definition of the Service Command Set that can be invoked against the Service's SST. Commands are logically specified in terms of Command (Variable=New Value, Variable=New Value, . . . ). If a Command results in more than a single Variable change, the updates are atomic and the Command will fail if it is illegal to make the specified change to any one Variable.
        The definition of a structured unit of data called a Service Control Protocol Declaration (SCPD). SCPD is used to advertise the layout (schema) of the SST and Command Set of the Service to a User Control Point or Bridge. The SCPD enables the User Control Point to invoke Commands (through the Rehydrator) on the Controlled Device without any prior or persistent knowledge of the capabilities of the device. The SCPD is uploaded from the Controlling Device as part of the Description Document. Generation of the SCPD for a Service based on its SST definition and Command Set definition can be fully automated.
        The definition of a network protocol used to invoke Commands against the SST associated with a Service and to return results. The SCP can be generated from the SCPD. The Rehydrator's job is to convert SCPDs into SCPs. The reason for a formal SCP specification is to enable the implementation of the Control Server itself and to enable simple peer-to-peer device interoperation using only published protocols.
        An identifier, called the Service Type Identifier, that identifies a unique Service Definition. Service Definitions are versioned in controlled manner. Every later version of a Service must be proper superset of the previous version.
    
    


Device
According to the device model 200 shown in FIG. 3, a UPnP Device 202-205 (e.g., multiple function devices 102-103 of FIG. 1 and bridged devices 122-123 of FIG. 2) is a logical container of one or more Services 210-217. Generally a Device represents a physical entity such as a VCR. Typical Services in the VCR Device example might be “TRANSPORT”, “TUNER”, “TIMER” and “CLOCK”. While Devices are often physical entities, a PC emulating the traditional functions of a VCR could also be modeled in the same way as the stand-alone VCR. Devices can contain other Devices. An example would be a TV/VCR 250 (FIG. 4) packaged into a single physical unit. A Device (e.g., devices 202-203) may also be a logical container of other Devices. The top-most Device in a hierarchy of nested Devices 203-205 is called the Root Device 202. A Device with no nested Devices is always a Root Device.
The UPnP Device Model was designed to be general and flexible. It should be possible to model an entire Nuclear Power Plant as a single Service or as a deeply nested hierarchy of Devices and Services. In general, a Service 210-217 is cohesive set of functions that enables flexible packaging into a variety of Devices. Services can be versioned independently of Devices.
All Devices, including Root Devices belong to one or more Device Types. Device Types are intended to enable instances of Devices to be simply and automatically grouped for presentation. An example of a Device Type is “VCR” 254 (FIG. 4). Device Types are formally defined in terms of a minimal set of versioned Services that a Device of Device Type must support. Device Types are not formally versioned. Device Type is a relatively high level grouping. A Device of Device Type only ensures that minimal set of Services of a minimal version is present. There can be other Services, higher versioned Services and Services with vendor extensions present on such a Device.
UPnP enables SSDP level searches for a unique instance of a Device (by UDN), all Devices of type Device Type and all Devices that contain at least one Service Type of minimum version. The result of an SSDP search is always a URL that points to the Description Document contained in the Root Device. In the event that matching Device is not the Root Device, the Description Document has a tree of nested Devices that can be traversed to find the matching Device.
Every Device includes:

    
    
        One or more Device Types.
        One or more Services.
        Optionally, one or more Devices.
        Optionally, a Presentation (Web) Server 220-223 that can be used to expose Device user interface. Every Presentation Server has an associated Presentation URL.
        A globally unique identifier called the Unique Device Name (UDN). The UDN is the fundamental identifier of an instance of a Device. Every Device, including Root Devices, has exactly one UDN.
    
    


Every Root Device 202 also includes the Description Document 226 and Description Server 228 for all Devices under and including itself.
The formal definition of a Device (Device Definition 226) includes:

    
    
        The fixed elements of the Description Document that describe the Device.
        The required hierarchy of Devices and Service Definitions.
    
    


There can be many Device Definitions that belong to a single Device Type.
Device Types
The formal definition of a Device Type includes:

    
    
        A Device Type Identifier.
        The required hierarchy of Devices and Service Definitions of minimum versions.
    
    


Service State Table
A Service State Table (SST) logically consists of rows of:
Variable, Type, Legal Values, Default Value, Current Value
Although entries of the Service State Table in UPnP consist of these five items, the state table alternatively can contain fewer or additional items. Generally, each entry will minimally consist of a Variable name or identifier, and its current value.
The following table lists various Types available in UPnP.












Type
Description
Example







String
A sequence of UNICODE characters.



Number
A number, with no limit on digits; may
15, 3.14,



potentially have a leading sign,
−123.456E+10



fractional digits, and optionally an



exponent. Punctuation as in US



English.


Boolean
TRUE or FALSE.


DateTime
A date in ISO8601 format, with
19941105T08:15:



optional time and optional zone.
5+03



Fractional seconds may be as precise



as nanoseconds. See, “Data elements



and interchange formats - Information



interchange - Representation of dates



and times”, which can be found at



http://www.iso.ch/markete/8601.pdf.


ByteBlock
An unstructured sequence of bytes.









The ByteBlock is essentially a data buffer. In one use, a variable of this type can be used to effect transfer of a file from the Controlled Device to the User Control Point. The file to be transferred is kept in the Service State Table as the current value of this variable. On a change in the file, the file is transferred to any subscribing User Control Point in an event notification.
The reason for representing Services this way is to ensure that the state of a Service is easily available in a common way to multiple User Control Points.
An SST can be used to represent to current operational mode of device, act as an information source or sink and/or simply be a repository for commands. The SST of a VCR Service could represent the current transport mode, tuner channel selection, input and output switch selections, audio and video decoding format and current timer program. Alternatively, the VCR 254 could be represented as a Transport Service 260, Tuner Service, I/O Switch Service, A/V Decoding Configuration Service and Programmable Timer Service 261.
The SST of a clock 251 would likely represent the current time. Additionally an alarm clock could include Service Variables to configure the clock.
The SST of an image rendering device could implement a video frame-buffer that can accept raw pixel information or formatted JPG files. The SST of an audio or video playback device could implement a transfer buffer or queue of material to be played. The SST of PDA could implement a collection of formatted data that has changed and needed to be synchronized with another device, in addition to a transfer buffer for accepting incoming formatted data.
User Control Point Synchronization
In accordance with an device state and eventing model illustrated in FIG. 5, UPnP rules require that every change to an SST generate a corresponding event to announce the change to the all interested User Control Points.
UPnP Self-Bootstrapping
With reference to FIG. 6, UPnP self-bootstrapping 350 is an integrated set of technologies organized as layers of a stack that include addressing 352, naming 354, discovery 356, and description 358 layers. The technologies in these layers is discussed in detail below. At the addressing layer 352, UPnP utilizes the Dynamic Host Configuration Protocol (DHCP) and AutoIP protocol for device addressing described below, which operate to dynamically assign an address to a UPnP device when introduced on a network. At the naming layer 354, UPnP utilizes the Domain Name System (DNS) and multicast DNS protocols and/or the NetBIOS Name Service (NBNS) protocol to provide services to refer to devices using names according to a naming convention. At the discovery layer 356, UPnP utilizes the Simple Service Discovery Protocol (SSDP) protocol by which a UPnP device can discover other devices present on the network. At the description layer 358, UPnP utilizes XML-based schema to describe device structures and operational functions exposed by a UPnP Controlled Device and XML message-based protocols for their invocation. The UPnP user control points can use this XML-based schema description to invoke and thereby control the UPnP Controlled Device at a usage layer 360.
Device Addressing
With reference now to FIG. 7, UPnP is built on top of HTTP and leverages the native address format of the Web, Uniform Resource Locators (URLs), beyond the basic network addressing. URLs minimally contain an identification of the application protocol family (“http”) that the URL is valid for, a Hostname and a path. In the context of UPnP, the path part of a URL can represent either a filesystem path or simply an identifier of the local system module and context that can process incoming messages.
While UPnP modules are described as HTTP servers, there is no requirement that implementations be based on actual Web servers. In most cases, the job of the HTTP server is simply to accept the incoming connection, look at the local destination part of the address (the path) and forward the payload to another module. UPnP enables, but does not require, that all HTTP Servers be based on a common software implementation or runtime instance. Controlled Devices and Bridges can include a TCP port specification as part of a URL to override the default value of 80.
The successful result of a SSDP level search in UPnP is always one or more Description URLs. These URLs can be used to navigate to the Description Document of a Controlled Device or Bridge. A User Control Point uploads the Description Document and extracts the URLs of the Servers running on the Controlled Device or Bridge.
All URLs returned in the Description Document have a lifetime equal to the lifetime of the Hostname embedded in them. User Control Points can store these URLs as addresses without going through a search sequence first. Once they have been advertised in a Description Document, Controlled Device and Bridges cannot arbitrarily change Server URLs.
Whenever a Hostname changes, all URLs associated with all Devices addressed by that Hostname are invalidated. The UDN is the only UPnP identifier guaranteed never to change. Any persistent associations maintained by applications should at least store the UDN to able to unambiguously identify the target Device.
The lifetime of a Description URL is determined by Controlled Device or Bridge that advertises it. If a Controlled Device or Bridge allows an SSDP advertisement of a Description URL to expire, the URL is invalidated.
User Control Points use the Event Subscription URL returned by the Controlled Device or Bridge to connect to the Event Subscription Server. This server does the housekeeping of remembering all User Control Points that are interested in receiving Events on a Service. The Event Subscription Server needs an address to send the events back to. This address is called the Event Sink URL, and is supplied to the Controlled Device or Bridge in the GENA SUBSCRIBE message. The lifetime of an event subscription, and the Event Sink URL, is determined by the timeout on the SUBSCRIBE message.
Further details of UPnP addressing are listed in the following table.










UPnP Addresses








URL
Function





Description
Points to the Description Server and


URL
Document path on a Root Device. This URL



is returned by the Description Server as



part of the discovery process.


Presentation
Points to a Presentation (Web) Server on a


URL
Controlled Device. There is one Presentation



URL per Device, including Root Devices. This



URL can be entered into the address bar of a



Web browser to navigate to the root Web page



of a Device. This URL is returned in the



Description Document.


Control URL
Points to the Control Server implementing a



Service on a Controlled Device. There is one



Control URL per instance of a Service. This



URL is returned in the Description Document.


Event
Points to an Event Subscription Server on


Subscription
a Controlled Device. This URL is returned in the


URL
Description Document.


Event Sink URL
Points to an Event Sink (an HTTP Server)



on a User Control Point. This URL is specified



by the User Control Point in the GENA SUBSCIBE



message.









Device Discovery and Identification
UPnP enables SSDP searches for a unique Root or non-Root Device by UDN, devices of a specified Device Type and devices containing a Service of a specified Service Type.










UPnP SSDP Level Searches and Results








Search for
Returns





A unique Root
A single Description URL pointing to the


Device (by
Description Server and Document path on


UDN)
the Root Device.


A unique non-
A single Description URL pointing to the


Root Device (by
Description Server and Document path on


UDN)
the Root Device that contains the non-



Root Device.


Type of Device
A set of Description URLs pointing to the



Description Servers/Document paths of all



Root Devices that match the Device Type, or



contain a non-Root Device that matches the



Device Type.


Type of Service
A set of Description URLs pointing to the



Description Servers/Document paths of all



Root Devices that contain a matching Service,



or contain a non-Root Device that contains a



matching Service.









SSDP specifies Service Type (ST), Notification type (NT), and Unique Service Name (USN) header fields for queries and for announcements. UPnP uses the ST or NT header to carry one of the UPnP defined identifiers. A unique USN is required for each unique SSDP announcement.
Multiple instances of the same Service Type within a Controlled Device 106-107 or Bridge 120 are not independently announced.
UPnP search identifiers are used during the discovery process. The result of a successful discovery is one or more Description URLs. The format for search identifiers is:












upnp:searchtype: [ allformat | UDNformat | srvformat


| devformat ]








searchtype
= [ UDN | SrvType | DevType | all ]


allformat
= all







UDNformat = UDN:namespace:uniqueid


namespace = [ GUID | IEEEMAC | 1394]


srvformat = SrvType:servicetype:version


devformat = DevType:devicetype










UPnP Search Identifiers










Format
Example













all
upnp:all
upnp:all


Unique Device
upnp:UDN:namespace:uniqueid
upnp:UDN:IEEEMAC:0C0099123456


Name (UDN)


Device Type
upnp:DevType:devicetype
upnp:DevType:vcr


Service Type
upnp:SrvType:servicetype:ver
upnp:SrvType:clock:1









SSDP specifies that SSDP announcements must be made for all SSDP searchable values. The SSDP announcements with “all” as the notification header value must carry the Root Device UDN as the USN header value. SSDP announcements for Device Types must carry the UDN of the Root Device concatenated with the Device Type URI as the USN header value. SSDP announcements for a Service Type will carry the UDN of the Root Device concatenated with the Service Type URI value as the USN header value. SSDP announcements of UDNs will repeat the UDN value as the USN header.










UPnP SSDP Announcements










UPnP




Notification


Announcement
Type
SSDP USN






“all”
Root Device UDN


Unique Root
Root Device UDN
Root Device UDN


Device


Unique non-Root
Non-Root Device
Non-Root Device UDN


Device
UDN


Device Type
Device Type
Root Device UDN +



Identifier
Device Type Identifier


Service Type
Service Type
Root Device UDN +



Identifier
Service Type Identifier









UPnP Bridges 120 (FIG. 2) announce Bridged Devices 122-123 and associated Services using SSDP. The identifiers associated with the Bridged Devices are unique for the device, and they do not duplicate identifiers for Controlled Devices and Services directly available on the Bridge itself. This means that a Bridge that is also a Controlled Device must announce Bridged Devices and local Controlled Devices independently, with appropriate unique identifiers, Description Documents and associated URLs.
Description
The UPnP Description Document 226 (FIG. 3) provides the information necessary to identify, describe, connect and control a UPnP Controlled Device 106-107 or Bridge 120 from a User Control Point 104-105.
The Description Document is an XML document. UPnP defines the use of HTTP and XML for the Description Document and wire protocols. UPnP adheres to the schema declaration rules of XML-Data and processing rules of Y. Goland, “Flexible XML Processing Profile.”
The top level XML elements are separated into three categories: per Device, per Service and shared.
Rehydrator
With reference now to FIG. 8, all (UPnP) Controlled Devices 106-107 (FIG. 1) or Bridges 120 (FIG. 2) expose one or more Services 210-217 (FIG. 3) that can be controlled remotely. Controlling such Services involves a message exchange between a User Control Point 104 and the device 106. This message exchange happens according to a specific Service Control Protocol (SCP) 402, which specifies the content and sequence of the messages exchanged.
User Control Points 104 are not required to have any prior knowledge of the SCPs 402 required to control the Services on the various devices. Therefore, a Controlled Device or Bridge must be able to describe to a User Control Point the protocols required to control its Services, such that the User Control Point will be able to implement these protocols dynamically. This requires a standard way of declaring Service Control Protocols in a concise and unambiguous fashion. UPnP introduces a technique for declaring Service Control Protocols using a series of XML documents.
A Rehydrator 410 is a module that exposes a suitable API to applications and either invokes Commands on a Service or queries the state of that Service, or receives and responds to events. The primary job of the Rehydrator is to map between API calls and the Service Control Protocol sequence that invokes the Command.
As part of the Service Definition 406, a Service State Table 230 and Command Set 408 are defined. These things can be combined in a deterministic way defined by UPnP to produce a Service Control Protocol Definition (SCPD) 406, which includes a Service Control Declaration 404 and a Service Control Protocol 402. The SCPD 406 is a representation of the schema of a Service. It is possible to reconstruct the SST, Command Set and SCP from the SCPD.
The SCPD is directly embedded into the Description Document 226 of a Controlled Device. When the Description Document is uploaded into the User Control Point 104, the Rehydrator 410 can extract the SCPD from it. At this point, the Rehydrator has enough information to issue Service specific SCPs 402.
General Operation of the Rehydrator
More generally with reference to FIG. 9, the Rehydrator 410 operates as a universal adapter to provide a programmatic interface to any service-specific protocol of a remote computing device. The Rehydrator 410 simply obtains a data description or declaration of the methods, properties and events of the remote service, as well as a definition of the protocol of network data messages through which the Rehydrator invokes the methods, queries or sets the properties, and receives event notifications. In UPnP, this data description takes the form of the Description Document 226, which contains a Contract 412. The Contract defines network data packets 413 (e.g., XML data), request/response patterns, and protocol (e.g., GENA, HTTP, SSDP) via which the packets are exchanged. This information is sufficient for the Rehydrator to exchange the appropriate network data packets to interact with the Controlled Device Service, including to invoke commands, query and set properties, and receive and respond to events, without download of any executable code to the User Control Point 104 device and with a zero installation or configuration experience.
The Description Document 226 also includes a declaration of the methods, properties and events for the Service. Based on this declaration, the Rehydrator produces a corresponding programmatic interface for use by applications at the User Control Point. The programmatic interface is an application programming interface that can be in the form of an object integration interface of an object-oriented programming model, such as Microsoft COM, CORBA, Java classes, and scripting engine name extensions. In the example illustrated in FIG. 9, the Rehydrator 410 exposes a COM object integration interface (“IClock” interface 414), with methods getTime( ) and setTime( ), for a Controlled Device having a “Clock” Service with GetTime and SetTime commands. The Rehydrator 410 converts calls of an application program 416 to the IClock interface 414 into the network data messages specified in the Contract to invoke the corresponding commands of the Clock Service. The Rehydrator 410 likewise creates suitable further programmatic interfaces for other Services (e.g., Services 210-217 of FIG. 3) based on the Description Document of their respective Controlled Devices.
Accordingly, the Rehydrator operates as a universal proxy object with data-driven conversion of programmatic interfaces to network data messages. Further, the Rehydrator produces the programmatic interface at the User Control Point based solely on an XML data description. This operation allows the Rehydrator to produce just-in-time transient interfaces to remote device Services without the complexity of code downloads and installation or configuration. Upon a later release of the interface by the application, the Rehydrator destroys the interface without need to de-install or clean up persistent configuration data in a registry or configuration file of the operating system or object execution run-time.
Rehydrator Implementation
Summary. With reference to FIG. 10, a preferred implementation 440 of the Rehydrator 410 is as an internal Microsoft Windows component that routes service control requests from the UPnP API to devices. Applications wishing to control a service on a UPnP device obtain a Service object through the UPnP API and use the methods of this object to query the state variables of the service and invoke its actions. Those methods use the Rehydrator API to turn the service control requests into network messages that travel to the UPnP device. In this sense, the Rehydrator performs a mapping between API calls and network protocols.
Basic Functionality. The preferred implementation of the Rehydrator is able to translate a service control call to the UPnP API into the appropriate network messages defined by the Service Control Protocol.
Asynchronous Event Notification. The preferred implementation of the Rehydrator is able to notify UPnP API clients of any asynchronous events generated by the devices they are controlling. Event notification is done by means of the event interfaces defined below.
Error Reporting. For a variety of reasons, state variable queries and action invocations may fail. The preferred implementation of the Rehydrator is able to provide a way to communicate the success or failure status of such operations to the parties initiating them.
Rehydrator Implementation Design. As illustrated in FIG. 10, the preferred implementation of the Rehydrator is used in two ways. First, the Device Finder 450 uses it to create Service objects 460. Then, these Service objects use it to carry out service control operations (querying state variables and invoking actions).
Creating Service Objects. When the Device Finder 450 creates a Device object, it invokes the Rehydrator 410 to create Service objects 460 for each of the service instances on that device. Each service instance supports a particular Service Control Protocol and the Rehydrator needs a description of this protocol in order to create a properly hydrated Service object.
The Service Control Protocol is declared in two separate XML documents: the DCPD and the Contract. The Rehydrator needs the information in both documents. These two documents are passed to the Rehydrator as IXMLDOMDocument interface pointers in the RehydratorCreateServiceObject( ) API call.












HRESULT


RehydratorCreateServiceObject(








IN
IXMLDOMDocument *pDCPD,












IN
IXMLDOMDocument

 *pContractDocument,












OUT
IUPnPService

**pNewServiceObject);










This API returns a pointer to an IUPnPService interface on a newly created Service object. In addition to the creating the Service object, the Rehydrator sets up its internal data structures so that it can properly handle requests to control the service. Specifically, it creates a list of the properties and actions exported by the service. Since all service instances of the same service type export the same properties and the same actions, this information is kept only once for each service type and is indexed by Service Type Identifier.
The Rehydrator stores the information that is specific to a particular service instance as private data within the Service object itself. This includes the control URL and information about the control server 232 (such as the HTTP verbs it supports). The Service Type Identifier is the link between the Service object that represents one instance of a service type and the Rehydrator internal data structures that contain information common to all instances of that service type. The Service Type Identifier is stored as a private data member in the Service object.
Querying Service Properties. Applications can query the values of service properties by invoking the IUPnPService::GetProperty( ) method on a Service object. Internally, this method makes a call to the RehydratorQueryStateVariable( ) function.















HRESULT



RehydratorQueryStateVariable(













IN
LPCTSTR
lpcszVerb,




IN
LPCTSTR
lpcszControlURL,




IN
LPCTSTR
lpcszSTI,




IN
LPCTSTR
lpcszVarName,




OUT
VARIANT
*pValue);










The first two in parameters to this function supply the service instance specific information: the HTTP verb to use and the control URL to which the network messages will be targeted. The third parameter is the Service Type Identifier that will be used to locate the Service Control Protocol information in the Rehydrator's internal data structures. The fourth parameter is the name of the variable that is being queried (the Rehydrator will validate this against is internal list of state variables exported by the service) and the final parameter is the address of a VARIANT structure in which the Rehydrator will place the variable's value.
This function will generate an HTTP request to the control server on the device. The body of this request will be an XML fragment containing a XOAP-encoded request for the variable's value. The following is an example of such a request (the exact header and payload format of this message is defined in the service contract):















M-POST /clockService HTTP/1.1



Host: spather-xeon:8586



Content-Type: text/xml



Man: “http://www.microsoft.com/protocols/ext/XOAP”;



ns=01



01-MethodName: queryStateVariable



01-MessageType: Call



Accept-Language: en-gb, en;q=0.8



Referer: http://myhouse/VCR1Presentation



Content-Length: 84



User-Agent: Mozilla/4.0 (compatible; MSIE 5.01;



Windows NT 5.0)



Connection: Keep-Alive



<queryStateVariable>









<variableName>currentTime</variableName>









</queryStateVariable>










The control server will respond to this message with another XML fragment: the XOAP-encoded method response. The following is an example of such a response:















HTTP/1.1 200 OK



Connection: Close



Cache-Control: private



Date: Mon Oct 11 12:13:38 PDT 1999



Expires: Mon Oct 11 12:13:38 PDT 1999



Content-Type: text/xml



Content-Length: 62



Man: “http://www.microsoft.com/protocols/ext/XOAP”;



ns=01



01-MessageType: CallResponse



<queryStateVariableResponse>









<_return>12:13:28</_return>









</queryStateVariableResponse>










The rehydrator will extract the return value from this XML fragment, place it in the VARIANT structure whose address was passed as the last parameter to RehydratorGetServiceProperty( ) and then return.
Invoking Service Actions. The process of invoking a service action is very similar to querying a state variable. An application calls IUPnPService::InvokeAction( ) on a Service object, passing it the name of an action to invoke, and an array of arguments to the action. Internally, IUPnPService::InvokeAction( ) calls RehydratorInvokeServiceAction( ), declared as shown below.















HRESULT



RehydratorInvokeServiceAction(











IN
LPCTSTR
lpcszVerb,



IN
LPCTSTR
lpcszControlURL,



IN
LPCTSTR
lpcszSTI,



IN
LPCTSTR
lpcszActionName,



IN
SAFEARRAY
saActionArgs,











OUT
LONG
*pStatus);










As was the case for querying state variables, the service instance specific information is passed in the first two parameters, followed by the Service Type Identifier in the third. The action name and an array of arguments are passed as the next two parameters, and the final parameter is the address of a variable in which to store the status of the operation.
RehydratorlnvokeServiceAction( ) will send an HTTP request to the control server identified by the second parameter. As before, the body of this message will be an XML fragment containing a XOAP-encoded method call. An example HTTP request to invoke an action is shown below.















M-POST /clockService HTTP/1.1



Host: spather-xeon:8586



Content-Type: text/xml



Man: “http://www.microsoft.com/protocols/ext/XOAP”;



ns=01



01-MethodName: invokeAction



01-MessageType: Call



Accept-Language: en-gb, en;q=0.8



Referer: http://myhouse/VCR1Presentation



Content-Length: 119



User-Agent: Mozilla/4.0 (compatible; MSIE 5.01;



Windows NT 5.0)



Connection: Keep-Alive



<SerializedStream main=“invokeAction”>









<invokeAction id=“invokeAction”>









<actionName>setCurrentTime</actionName>



<actionArg>15:41:29</actionArg>









</invokeAction>









</SerializedStream>










The encoding of the body of this message is again specified in the service contract. The Rehydrator will wait for the HTTP response to this request, which would look something like the example below.















HTTP/1.1 200 OK



Connection: Close



Cache-Control: private



Date: Mon Oct 11 15:22:38 PDT 1999



Expires: Mon Oct 11 15:22:38 PDT 1999



Content-Type: text/xml



Content-Length: 50



Man: “http://www.microsoft.com/protocols/ext/XOAP”;



ns=01



01-MessageType: CallResponse



<invokeActionResponse>









<_return>0</_return>









</invokeActionResponse>










After receiving a response such as this, the Rehydrator will extract the return value, place it in the out parameter it was passed, and then return.
FIGS. 32 through 44 are program listings defining various interfaces used in the preferred implementation of the Rehydrator, including an IUPNPDevice Interface, an IUPNPPropertyBag Interface, an IUPNPService Interface, an IUPNPDevices Interface, and an IUPNPServices Interface.
Description Document
With reference to FIG. 14, User Control Points 104 can retrieve a Description Document 226 by issuing an HTTP GET on a Description URL. This URL is returned in the location header of either an SSDP announcement or an SSDP query response.
The HTTP GET must include an accept-language header that is used to request the preferred language of the response. If the requested language is not supported, a Description Document in the default language supported by the Controlled Device or Bridge may be returned.
An HTTP GET is used to retrieve sub elements of a Description Document that are expressed as URLs.
URL Handling
URLs embedded in Description Documents 226 take one of 3 forms: a fully qualified URL or a relative URL.
Fully qualified URLs take the form:















http://devicename/pathname










The devicename part of the URL is a Hostname or IP address and the pathname is a filesystem path or equivalent. A fully qualified URL is used “as is” to establish an HTTP connection to a device.
A relative URL does not contain the “:” character and is of the form:















pathname



/pathname










Relative URLS are a compact representation of the location of a resource relative to an absolute base URL. All relative URLs in a Description Document are appended to the value of the Description Document element <URLbase> to form fully qualified URLs.
Binary Data
Some elements of a Description Document are binary. XML does not directly support the embedding of binary data. In order to include binary data directly in a Description Document, one must convert the data to text using the Base 64 encoding scheme. This tends to increase the size of the data by 25% on the average. Much of this overhead can be eliminated if the binary data is passed by reference instead of by value. To reference binary data, a URL to the data is provided in a Description Document. The binary data can be retrieved by doing a HTTP GET with that URL.
As an example, consider the <image> element in the following Description Document:















<iconList>









<icon>









<size>16</size>



<imageType>PNG</imageType>



<color>1</color>



<depth>8</depth>



<image>









“http://device.local/iconpath/icon.png”/>









</icon>









</iconList>










The icon would be retrieved with an HTTP GET of the following format:















GET iconpath/icon.png HTTP 1.1



Host: device.local










The HTTP response would look like:















HTTP/1.1 200 OK



Content-Type: image/png



Content-length: ###



<binary color icon data in the PNG format>










Description Document Layout
The basic layout of the Description Document 226 is shown in FIG. 15.
The following table lists Description Document elements that are sub-elements to the root element.













Root
The XML root element of a UPnP Description



Document.


specVersionMajor
The major version of the UPnP Architectural



Reference that this Description Document was



created against. This value must be 1.


specVersionMajor
The minor version of the UPnP Architectural



Reference that this Description Document was



created against. This value must be 0.


URLBase
An optional element used to construct fully



qualified URLs. Relative URLS are appended to



the value of <URLBase> to create fully qualified



URLs. If this element is present, it must agree



with the HTTP Base header.


manufacturer
A required element that contains a textual



manufacturer name.


manufacturerURL
An optional element containing a URL that points



to the Web page of the manufacturer.


modelName
A required element containing a textual product



name.


modelDescription
A required element containing a textual product



description.


modelNumber
An optional element containing a textual product



model number.


modelURL
An optional element containing a URL that points



to the Web page of the product.


UPC
An optional element containing the product



Universal Product Code (UPC).


serialNumber
An optional element containing a textual item



serial number.









The Description Document elements listed in the following table are associated with devices.













rootDevice
A required sub element of the root. This element



is a container for one or more service elements



and the elements that describe the rootDevice.


device
An optional sub element of the root or another



device element. This element contains the same



kinds of elements as a rootDevice element.


UDN
A required sub element of every rootDevice or



device element containing the Unique Device Name.


friendlyName
A required sub element of every rootDevice



or device element containing a textual friendly



name. This element can be updated remotely.


deviceType
A required sub element of every rootDevice or



device element containing a standardized Device



Type Identifier.


presentation
An optional sub element of a rootDevice or


URL
device element containing a Presentation URL.


iconList
A required sub element of every rootDevice or



device element. This element is a container for



one or more icon elements. UPnP requires a base



set of six icons that must exist in the iconList.



All devices must support PNG icon image formats



of three sizes, 16 by 16, 32 by 32 and 48 by 48



pixels in both color and black and white at 8



bit depth. Additional formats and sizes,



including JPEG, GIF, BMP, ICON and VML, may be



supported by adding them to the list.


icon
A required sub element of every iconList element.



This element is a container for the elements that



define an icon.


size
A required sub element of every icon element. There



must be icon elements with associated size elements



with the values 16, 32 and 48. Other icons may specify



other sizes.


color
A required sub element of every icon element with



value 0 or 1. Each icon of size 16, 32 or 48 must



exist in color and black and white.


depth
A required sub element of every icon element. All



required icons must exist with a value of 8.


imageType
A required sub element of every icon element that



identifies the format of the binary icon: png, jpeg,



vml, gif, bmp, or ico.


image
A required sub element of every icon element that



references a binary icon.







The following elements of the Description Document are


associated with Services.








service
An optional sub element of the rootDevice or another



device element. This element is a container for the



Service Definition.


serviceType
A required sub element of every service element



containing a standardized Service Type Identifier.


controlURL
A required sub element of every service containing



a Control URL


eventSubURL
A required sub element of every service containing



an Event Subscription URL.


SCPD
A required sub element of every service. The SCPD



is a container for the standardized Service Control



Protocol Declaration associated the Service.









FIG. 16 shows an exemplary icon list in a Description Document 226.
Service Control Protocol and SCP Declaration
As part of the Service Definition 406 shown in FIG. 8, a Service State Table 230 and Command Set 408 are defined. The SCPD 406 is a representation of the schema of a Service. It is possible to reconstruct the SST 230, Command Set 408 and SCP 402 from the SCPD deterministically.
The declaration of such a protocol must specify the list of Variables that can be queried, the set of Commands that can be invoked, as well as the wire protocol (the content and sequence of network messages) required to carry out these operations. SCPD is specified in two XML documents. The first or Service Control Definition document 404, written in a language called Service Control Protocol Declaration Language (SCPDL), declares the list of state Variables and Commands associated with the Service Type to be controlled by the protocol. The second or Service Control Protocol document 402 is written in Contract Definition Language (CDL) and declares the wire protocol that will be used to query the values of the state variables and invoke the actions associated with the service.
Declaring the Service State Table and Command Set
A SCPDL document 404 is used to specify the list of state Variables that a SCP can query and the set of Commands that it can invoke. SCPDL is an XML schema, a set of rules for writing XML documents (Service Control Protocol Declarations).
FIG. 17 shows an exemplary SCPDL document. This XML document consists of a root <scpd> element containing two sub-elements, <serviceStateTable> and <actionList>. Within the <serviceStateTable> element is a <stateVariable> element for each state variable associated with the service. The Service in this example is a TV tuner with has only one state variable, currentChannel. The elements within the <stateVariable> element specify the name, data type and allowed values for the state variable. Had the Service more state variables, they would be represented by additional <stateVariable> elements within the <deviceStateTable> element.
The <actionList> element contains an <action> element for every action associated with the Service. The elements within an <action> element specify the name of the action and any arguments the action may take. In this case, the service supports two actions that do not take arguments, ChannelUp and ChannelDown, and another, SetChannel, that takes a new channel number as an argument. The <argument> element and the elements nested within it define the argument. The <relatedStateVariable> element within <argument> specifies the name of one of the state variables to which the argument is related. In the UPnP Device Model, all arguments to actions must correspond directly to some state variable.
Declaring the Contract
The Contract is a specification of the wire protocol that will be used to query state Variables, invoke Commands and carry notifications or events. This contract specifies the type of protocol used, the network endpoint to which messages are sent, the contents of those messages, the contents of the expected responses and the contents of events. Contracts are written in Contract Definition Language (CDL).
All UPnP SCPs will use essentially the same contract. A specific contract applies to a single Service instance (since it specifies the network endpoint to which messages are sent and network endpoints are specific to service instances). However, other than the network endpoint definition, all contracts for all Service instances should be the same.
FIGS. 18-20 show an exemplary Contract. This Contract defines two methods: queryStateVariable and invokeAction. These methods are invoked by exchanging XML messages with a Control Server on a UPnP Controlled Device or Bridge. The Contract completely defines the header and payload of each message. By passing the appropriate arguments to these methods, any of the state Variables declared in the SCPDL declaration can be queried and any of the actions invoked.
FIGS. 21 and 22 show an XML schema for the SCPDL.
Basic UPnP Eventing Architecture
With reference to FIG. 23, the UPnP architecture 200 (FIG. 3) requires that clients of the UPnP API be enabled to receive notifications reliably from UPnP services 210-217 as their states change. Since state changes are relatively common, the eventing subsystem is efficiency and performance is a major consideration in this design. FIG. 23 and the following discussion describe the Basic UPnP Eventing Architecture 600, which encompasses both the controlled device (CD) 106 and user control point (UCP) 104 sides of the eventing service. It also includes the support APIs for both a low-level service interaction and a higher level COM-based wrapper of those APIs. The latter enables automation controllers like Visual Basic and JScript 602 to receive event notifications.
What is an Event?
Property change events are defined as any change in the value of a row of the Device State Table (DST) 230 (FIG. 3) for a service 210-217. This change will be reflected as a property change notification. For example, if a “VCR” device has a “VCR Transport” service, one row in that service's DST may be TapeState and the value could be TapePresent. If the tape is ejected, the new value would be TapeAbsent. This state change would be reflected as a notification sent to all subscribers.
What is a Notification?
A UPnP event notification is an XML message sent over HTTP/TCP to each and every subscriber to a particular UPnP service. The content of the XML is defined below. The important contents of this message are the unique identifier for the subscription, the property name, new value, and property type.
Notification Processing
In UPnP, the listener to Notifications is the SSDP service itself. SSDP already listens on another multicast address for “alive” and “byebye” messages sent by UPnP devices. The same listener will listen on a TCP port for notifications sent. All subscriptions sent from that UCP contain the same callback URL and so all notifications will be directed to that URL. When a notification arrives the SSDP service will examine the NT header of the message and determine if it is an event notification. If so, the message is parsed further to determine if it should be forwarded on to subscribers (which must exist). GENA defines the format of the HTTP message, what headers can be used, and what they can be used for.
GENA
GENA is the protocol of communication that, in a preferred embodiment, UPnP devices use to send event notifications. Therefore, UPnP devices that wish to notify UCPs of state changes are recommended to use GENA. Notification subscribers will never be required to interact with a UPnP device directly and so they are not required to use GENA. The eventing API will encapsulate this complexity. Other appropriate event transport protocols may be used, such as publish/subscribe systems.
Receiving Notifications
Applications written in C (C Application 604) will be able to utilize the SSDP C API 610 to receive callbacks when notifications are processed by the SSDP service. This is analogous to SSDP clients registering for notifications that services have become available. When a UCP registers for a notification, it passes as a parameter the URL of the service for which it is interested in receiving notifications. This URL is obtained from the description document for that service. (When a service is registered on a UPnP device, it uses this same URL to listen for subscription requests).
When a notification message is received by the SSDP service listener, the SID header is checked against the list of subscribers it maintains. If a subscriber is found, the callback function for that subscriber is invoked, with one of the parameters being the contents of the notification message. The notification client that implements the callback function can process this message in any appropriate way.
Notifications in the UPnP API
The UPnP API 410 is a consumer of the basic C interface provided by the SSDP C API 610 component. In order to integrate seamlessly, the registration of notifications is handled by the Service Object 612 inside the UPnP Object Model. Service objects will register for notifications when they are created. This ensures that the DST is maintained by the UPnP API and is kept up to date. They will implement the callback function required by the registration function. If this callback function is invoked, it will pass on that notification to UCPs. The UCPs can be written in C, C++, VB, or script code, so the mechanism for passing on notifications can be different.
Script Support
A feature of the illustrated eventing system is that it supports script languages such as VBScript and JavaScript 602. For VBScript, this is made possible by providing a property on the Service object that, when set, contains the IDispatch pointer for a VBScript function or subroutine that will be the event handler. When the Service object's notification callback is invoked, it checks to see if this IDispatch pointer was set, and if so, it calls IDispatch::Invoke on DISPID 0 of that interface to call the VBScript subroutine. An equivalent mechanism is implemented for JScript.
Eventing Subsystem Terminology
UCP—User control point. Any piece of software that searches for devices and controls them.
CD—controlled device. A hardware or software device that announces its availability thru SSDP and allows control by UCPs.
Subscriber—A UCP who wishes to be notified of event changes.
Notifying Resource (or simply “Resource”)—For the purposes of this document, this will always be a service contained within a UPnP CD 106.
Event Source—a service that provides events. UPnP services are event sources. All notifying resources are event sources and vice versa.
Event—message generated when a change in a resource's state occurs.
Property—a single entry in the service's state table whose DefaultValue can change. Properties and events always have a one to one correspondence.
Subscribing To Resources
Integrating With The UPnP API
The UPnP API 410 exposes several interfaces with which a consumer can find and enumerate devices, control services, and get properties on devices and services. To allow the integration of events into this model, we add a new property to the IUPnPService interface called EventHandler. When this property is set, it tells the Service object 612 that its client is interested in receiving notifications for that service. The SSDP API RegisterNotification( ) API is called when the Service object is created so that it can maintain a local copy of the DST for that service. The Service object knows the URL of the service and therefore it can provide this as a parameter to RegisterNotification( ). RegisterNotification( ) is also provided a callback function which is a static member of the Service object class. This function will be invoked for each and every notification sent by that particular UPnP service.
The Notification Callback
The Service object 612 includes a static member function called EventNotifyCallback( ) which is invoked for each notification sent by the UPnP service. The callback is passed the entire HTTP message contents in a structure which is a parameter to the function. The prototype looks like this:















static VOID



CUPnPService::EventNotifyCallback(SSDP_CALLBACK_TYP



E ssdpType,



SSDP_MESSAGE *pssdpMsg,









LPVOID pcontext);










The ssdp Type parameter should always be SSDP_PROPCHANGE. The pssdpMsg parameter contains the relevant information about the event. The key piece of information is the body of the XML message. The body contains information about what property changed, what its new value is and what type it is, among other information. The pContext parameter will always be the this pointer of the Service object. This allows the code to call a method to fire the event to the UCP. The callback will parse the XML body using the XML DOM services. Property changes are iterated and the local DST is updated to reflect these changes. After this processing is done, an event notification may be fired for each property that was changed to the owner of the subscription if one exists. Depending on what environment the owner is written in (C++ or script, etc. . . . ), a different mechanism for firing the event may be employed.
A special case for this process is the very first notification received after a subscription is established. This notification contains the entire set of properties and their values and is used to locally sync up the DST. Events will not be fired to clients of the UPnP API in this case.
Firing Notifications
When the EventNotifyCallback( ) function is called, the local copy of the DST for the service is updated. After this, an event needs to be fired if a subscriber exists. A subscriber exists if the put_EventHandler( ) method was called, either from VBScript, C++ code, or another source. To abstract away this complexity, a new interface called IUPnPEvents is needed.
This interface currently has one method called NotifyEvent( ) which takes several parameters. When put_EventHandler( ) function is called, its argument is an IUnknown. This pointer is QueryInterface'd( ) for IDispatch first, and if it succeeds, then IDispatch::Invokeo is called with DISPID 0 to invoke the default method. This allows VBScript 602 to be called. If that fails, however, it is Queried for IUPnPEvents, and if that succeeds, the NotifyEvent( ) method is called with the same parameters as for Invoke( ). The handles C++ UCPs effectively.
Subscribing with C++
To subscribe to a UPnP service from C++, a UCP instantiates a UPnP service object, issues QueryInterface( ) to it for IUPnPEvents, and calls the IUPnPEvents::SetEventCallback( ) function. This function takes 2 parameters, a callback function pointer and a context pointer.
Subscribing With VBScript
To subscribe to a UPnP service's events, all that needs to be done by a script 602 is to create a function or subroutine as a handler function and set the pointer of that function to the EventHandler property of the Service object. Now, anytime an event is fired, this VBScript function or subroutine will be called. In VBScript, this is written as the following:















Dim UPnPAPI



Set UPnPAPI = CreateObject (“UPnPAPI.1”)



Devices = UPnPAPI.FindDevices( . . . )



For each device in Devices









For each service In devices.services









If service.dcpi = “clock.v1”









Service.EventHandler =









GetRef(“clock_PropertyChanged”)









End if









Next service









Next device



Sub clock_PropertyChanged(prop, value)









MsgBox “The time has changed. It is now “ &









value & “.”



End Sub










In this example, the script enumerates all devices, looking for any device that supports the “Clock” interface. When it finds a device that supports that interface, it enumerates that device's services looking for the one that has the “clock.v1” interface. Once it finds that service, it sets that service's EventHandler property to the VBScript subroutine called “clock_PropertyChanged”. This name is arbitrary.
Sending and Receiving Notifications
GENA Client API
GENA clients are actually UPnP services. A GENA client creates a new event source when it is initialized. The GENA client API 620 facilitates this. It also provides a way for GENA clients to send their notification messages. It is also important to note that the HTTP server that lives on the UPnP device is also a client of this API. The GENA client API consists of the following functions:
RegisterUpnpEventSource( )
The RegisterUpnpEventSource( ) API gives a GENA client the ability to register itself as an event source. The prototype is as follows:















BOOL RegisterUpnpEventSource(



LPTSTR szRequestUri,



DWORD cProps,



UPNP_PROPERTY *rgProps



);










Parameters: szRequestUri [in] an arbitrary Request-Uri that SUBSCRIBE requests will be sent to. When a SUBSCRIBE request arrives at the given URI, it is acknowledged and the subscriber is added to the list of notification recipients. Note that this URI should match the URI provided in the description for this service. CProps [in] the number of properties that this event source provides. RgProps [in] Array of UPNP_PROPERTY structures which contain information about each property. The property information is derived from the DST for the event source.
Return Value: The function returns a TRUE if successful. If the given URL has already been registered as an event source, the return value is FALSE and GetLastError( ) returns ERROR_ALREADY_EXISTS.
Notes: The initial state of the event source needs to be given to the API so that it can effectively maintain the up-to-date state of the event source.
DeRegisterUpnpEventSource( )
The DeRegisterUpnpEventSource( ) API gives a GENA client the ability to deregister itself as an event source. The prototype is as follows:















VOID DeRegisterUpnpEventSource(









LPCTSTR szRequestUri









);










Parameters: szRequestUri [in] an arbitrary Request-Uri that SUBSCRIBE requests will be sent to. When a SUBSCRIBE request arrives at the given URI, it is acknowledged and the subscriber is added to the list of notification recipients. Note that this URI should match the URI provided in the description for this service.
UPNP Property















typedef struct _UPNP_PROPERTY {









LPTSTR szName;



LPTSTR szValue;



LPTSTR szType;









} UPNP_PROPERTY;










Where szName is the name of the property, szValue is the current value of property, and szType is the type of property (string, integer, etc. . . . ).
SubmitUpnpPropertyEvent( )
The SubmitUpnpPropertyEvent( ) API allows the GENA client to submit a UPnP property change event to be sent to subscribers as a notification. The prototype is as follows:















BOOL SubmitUpnpPropertyEvent (



LPCTSTR szRequestUri,



DWORD dwFlags,









DWORD cProps,



UPNP_PROPERTY *rgProps









);










Parameters: “szRequestUri [in]” identifies the event source to which this event belongs. This is the same Request-Uri passed to RegisterUpnpEventSource( ). “DwFlags [in]” is unused. “CProps [in]” is the number of events that are being submitted. “RgProps [in]” is an array of UPNP_PROPERTY structures which contain information about each event.
Return Value: If the function fails, the return value is FALSE. The get extended error information, call the GetLastError( ) function.
Notes: When a series of properties is submitted for event notification, the local version of the property state for the given event source is updated with the list of properties passed in. SubmitUpnpPropertyEvent( ) calls SubmitEvent( ) after it has generated an XML body.
SubmitEvent( )
The SubmitEvent( ) API allows the GENA client to submit an unstructured event to be sent to subscribers as a notification. The prototype is as follows:















BOOL SubmitEvent(



LPCTSTR szRequestUri,



DWORD dwFlags,









LPCTSTR szHeaders,



LPCTSTR szEventBody









);










Parameters: SzRequestUri [in] identifies the event source to which this event belongs. This is the same Request-Uri passed to RegisterUpnpEventSource( ). DwFlags [in] Unused. SzHeaders [in] null-terminated text string containing the headers for the event, each separated by CRLF. SzEventBody [in] null-terminated text string containing the body of the event message
Return Value: If the function fails, the return value is FALSE. The get extended error information, call the GetLastError( ) function.
Notes: If no subscribers exist, the function does nothing. If one or more subscribers exist, a message is sent to each subscriber. SubmitEvent( ) will always send to all subscribers.
UPnP Controlled Device Event Architecture
In UPnP, every UPnP service 210-211 that supports property change event notifications is to be a GENA client. Therefore, when the service is initialized, it must register itself as a GENA event source. It will do this with the RegisterUpnpEventSource( ) API. This returns a handle which can be used in subsequent APIs.
RegisterUpnpEventSource( ) takes a URL and an array of properties as parameters. Inside the API, an entry in an array of structures is initialized and the index is returned as the handle. The structure contains the source URL as one of the members. A second member of the structure, an array of destination URLs, is left uninitialized. This is filled in each time as subscriber is added for that event source. Another member of the structure is the list of properties that this event source provides. This is effectively a cached copy of the DST for the event source. As events are submitted, the local properties are updated.
When SubmitUpnpPropertyEvent( ) is called, each property submitted replaces the corresponding property already maintained by the API. If no subscribers exist, the request to submit an event is ignored. If one or more subscribers exist, their callback URLs are looked up in the list of subscribers for the given event source and a NOTIFY message is constructed and sent to each URL, one at a time, in order of subscription.
If an event is submitted and no response is received (or a CD-side error occurs), the CD continues to attempt to send to the UCP. If the subscription timeout expires, then the subscription is removed. If the UCP becomes available again, it will re-subscribe because it will notice the sequence numbers are not contiguous.
When an HTTP server 626 receives a SUBSCRIBE message, it passes it along to a function which parses the message for the necessary information. The Request-URI identifies the service that is to be subscribed to. The callback URL is obtained from the “Callback” header. Since the Callback header can contain multiple URLs, it picks the first “http://” URL it finds. It then adds the subscriber to the list of subscribers for this event source. A unique subscription identifier is constructed which it will send back to the subscriber in the HTTP response to the SUBSCRIBE request.
If no event source matches the Request-URI from the subscription message, the HTTP server should return “404 Not Found”.
When a subscription is added, the local copy of the DST is sent as a NOTIFY message. This special NOTIFY message contains sequence number 0 which informs the UCP that this is an initial state population event and not a notification where every event has changed.
When a CD receives an UNSUBSCRIBE message, it checks the “SID” header to obtain the subscription identifier. It looks up the subscriber ID in the list of subscribers for that event source and removes the destination URL entry associated with it.
GENA Server API
GENA servers 630 are generally going to be UPnP UCPs. A GENA server is anything that receives and processes NOTIFY messages to handle notifications from resources and sends SUBSCRIBE and UNSUBSCRIBE messages to receive notifications from resources. These APIs leverage the already existing SSDP APIs. The following are the changes to the APIs:
RegisterNotification( )
The RegisterNotification( ) allows a UPnP UCP to request notification when an event occurs for a given UPnP service. The prototype is as follows:
















HANDLE RegisterNotification(




NOTIFY_TYPE nt,
// SSDP_ALIVE |




SSDP_PROPCHANGE



| ??



LPTSTR szResourceType,
// based on




NOTIFY_TYPE, unused



if



// SSDP_PROPCHANGE is used.



LPTSTR szEventUrl,



ServiceCallbackFunc fnCallback,



void *pContext



);










Parameters: Nt [in] An enumeration that determines the type of notification requested. The values are: SSDP_ALIVE—a service has become available, and SSDP_PROPCHANGE—a property has changed on the service. SzResourceType [in] A null-terminated string specifying the resource type desired. For SSDP_ALIVE, this is the service type, for SSDP_PROPCHANGE this is unused. SzEventUrl [in] A null-terminated string specifying the URL that a subscription request should be sent to. FnCallback [in] A pointer to a function that will be called each time a notification is received. The function pointer is defined in the SSDP spec. PContext [in] This parameter is included as a parameter when invoking the client-supplied callback function.
Return Value: If the function succeeds, the return value is a handle used in a subsequent call to the DeregisterEventNotification( ) function. If the function fails, the return value is INVALID_HANDLE_VALUE error code. To get extended error information, call GetLastError.
ServiceCallbackFunc















typedef enum _SSDP_CALLBACK_TYPE {









SSDP_FOUND = 0,



SSDP_ALIVE = 1,



SSDP_BYEBYE = 2,



SSDP_DONE = 3,



SSDP_PROPCHANGE = 4,









} SSDP_CALLBACK_TYPE, * PSSDP_CALLBACK_TYPE;










UPnP UCP Architecture
When a UPnP UCP wishes to subscribe to notifications for a particular UPnP service, it calls the RegisterNotification( ) API. It passes to this API a notification type that identifies the type of notification being requested, a URL to which a subscription should be sent, and a callback function and context for use when the notification is received.
RegisterNotification( ) will compose a SUBSCRIBE message, using the data passed in, and send that to the URL specified by the caller. The Callback header of the SUBSCRIBE message will be composed on the fly, as an arbitrary URL for notifications to be sent to for this subscription. This callback URL will likely be a constant since the server API will always know how to handle requests sent to this URL. It will then send the SUBSCRIBE message and await a response.
RegisterNotification( ) in the SSDP API does not currently send HTTP requests, but it can be modified to do so. It also needs to await a response which it will also be modified to do so.
When the response is received, the Subscription-ID header contains a SID which is associated with the callback function specified by the caller.
Immediately after the response is received, the UCP should expect an initial NOTIFY message that contains the complete set of properties maintained by the CD. This becomes the local cached DST on the UCP side. From this point on, all modifications to the table are made via NOTIFY messages. This initial NOTIFY message will have sequence number 0 that indicates it is an initial property set and not an update. The UCP can use this information in any way it sees fit. This ensures the UCP's state table is always in sync with the one on the CD.
When a message is received by the HTTP server on the UPnP UCP, it is passed to a function which determines the method name and Request-URI. If this is a NOTIFY message, the headers are parsed and packaged up into a structure. The callback function that was specified to RegisterNotification( ) is called with that structure as one of the parameters. UCPs who implement the callback function can find the headers and body of the NOTIFY message and do additional processing based on the notification type.
This all requires that the SSDP HTTP server listen on a TCP socket in addition to the UDP multicast port it already listens to. However, once a NOTIFY message is received, it is processed in the same way regardless of from which connection it originated.
Handling Failures
The following are subscription/notification failures that can occur and their solutions:
Leaked Subscriptions
To protect against subscriptions that exist on the controlled device, but no longer on the UCP, we institute the timeout feature of GENA subscriptions. The scenario is this: A UCP subscribes to a CD, then the UCP reboots. Meanwhile, the CD is still trying to send notifications to that UCP. If the UCP never comes back, the subscription would be leaked because the UCP never told the CD that it was going away. So to correct this, each subscription request includes an arbitrary timeout value which indicates to the CD that the UCP will be re-subscribing every n seconds indicated in the timeout header of the subscription request. If the timeout expires on the CD, the subscription is removed. The UCP is required to re-subscribe before the timeout period has elapsed. If it fails to do so, the subscription will be terminated by the CD.
Some time before the timeout expires on the UCP, a re-subscribe message should be sent. The re-subscribe message is similar to the subscribe message, but it does not contain an NT or Callback header. If the UCP is unable to re-subscribe within the timeout period, the subscription will be terminated by the CD. If the UCP sends a re-subscribe after the CD has terminated the subscription, the CD will return “412 Precondition Failed”.
Reboot of a Controlled Device
If a controlled device reboots, information about all of its subscribers would be lost. To prevent this, the subscriber information will be persisted across reboots of the device. Because the subscription info contains a timeout member, the absolute expiration time will be used when the subscription information is persisted. That way, when the device comes back up, it can check the timeout for each subscriber and if that time has passed, the subscription will be removed.
Network Error Sending Event Notifications
If a controlled device receives an error sending an event notification to a subscriber, it will NOT cease to send notifications. It will continue to send notifications and receive errors until the subscription expires. The problem for the UCP is that it will have missed a number of event notifications and so its state table will be out of sync. To correct this, each event notification message will contain a 32-bit sequence number that starts at 0 and increments for each message sent to a subscriber. If a subscriber receives a notification with a sequence number that is not exactly one more than the previous notification, it will know that it has lost events and will ignore all future notifications until it receives one with sequence number 0 again. Events with sequence number 0 indicate that the event is an “initial state” event.
Once it realizes that is has lost one or more events, the UCP will send an UNSUBSCRIBE message, followed by a SUBSCRIBE message. This is not the same as a re-subscription because re-subscriptions do not cause the CD to start the sequence over at 0. In this case, the active unsubscribe/subscribe will cause the CD to restart the sequence at 0 and send the entire state table with the first notification message.
The SUBSCRIBE Message
When a UPnP UCP wishes to subscribe to event notifications for a UPnP service 210-211, it will form a SUBSCRIBE message of the following format:















SUBSCRIBE service1 HTTP/1.1



Host: vcr.local:200



NT: upnp:event



Callback: <http://remote1.local:923/upnp>



Timeout: Second-600










The response is as follows::















HTTP/1.1 200 O.K.



SID: uuid:kj9d4fae-7dec-11d0-a765-00a0c91e6bf6



Timeout: Second-600










This example of a GENA SUBSCRIBE request and response demonstrates a subscription to event notifications for “service1.” The host is “vcr.local.” All notifications for this service will be sent to the callback URL http://remotel.local:923/upnp. In the response, the “Subscription-ID” header provides the subscriber with an identifier to use when it wants to unsubscribe to this resource. The “Timeout” header indicates that the subscriber will send a re-subscription request before 10 minutes have elapsed. If the device does not receive this request within that period of time, it will remove the subscription.
The Re-SUBSCRIBE Message
When a UPnP UCP wishes to re-subscribe to event notifications for a UPnP service, it will form a SUBSCRIBE message of the following format:















SUBSCRIBE service1 HTTP/1.1



Host: vcr.local:200



SID: uuid:kj9d4fae-7dec-11d0-a765-00a0c91e6bf6



Timeout: Second-600










The response would be as follows::















HTTP/1.1 200 O.K.



SID: uuid:kj9d4fae-7dec-11d0-a765-00a0c91e6bf6



Timeout: Second-600










Note that the NT and Callback headers are absent, but the SID header exists. This tells the CD 106 which subscription is being renewed and restarts the timeout. When the CD receives this message, it will persist the subscriptions to disk (or other persistent data storage medium), updating the absolute timeout based on the current time and a new timeout sent by the UCP (if it was different).
The NOTIFY Message
When a resource wishes to send an event notification, it will form a NOTIFY message of the following format:















NOTIFY upnp HTTP/1.1



Host: remote1.local:923



NT: upnp:event



NTS: upnp:propertychanged



SID: uuid:kj9d4fae-7dec-11d0-a765-00a0c91e6bf6



Seq: 123



Content-Length: xxx



Content-Type: text/xml



<event XML schema>










The response is as follows::















HTTP/1.1 200 O.K.










This example of a GENA NOTIFY request and response demonstrates that a “upnp:propertychanged” event is being sent to http://remote1.local:923/upnp. The USN header identifies “vcr.service1” as the event source. The XML contains the property name, value, and type. The “Seq” header indicates the sequence number of the notification. Sequence number 0 indicates the initial state update for the subscriber.
Property Change Event XML Schema
A UPnP property change event will be of the following form:















<U:propertyset xmlns:U=“upnp”>









<U:propcount>2</U:propcount>









<U:property>



<U:foo>









<U:type>string</U:type>



goodbye









</U:foo>



</U:property>



<U:property>



<U:bar>









<U:type>integer</U:type>



27









</U:bar>



</U:property>



</U:propertyset>










Here, a property named “foo” is of type “string” and has a value of “goodbye” and a property named “bar” has a type of “integer” and has a value of 27. The XML will be contains a list of multiple properties that have changed, along with a count to make it easy to determine this.
The UNSUBSCRIBE Message
When a UPnP UCP wishes to unsubscribe to event notifications for a UPnP service, it will form an UNSUBSCRIBE message of the following format:















UNSUBSCRIBE service1 HTTP/1.1



Host: vcr.local:200



SID: uuid:kj9d4fae-7dec-11d0-a765-00a0c91e6bf6










The response would be as follows::















HTTP/1.1 200 O.k.










This example of a GENA UNSUBSCRIBE request and response demonstrates that the UCP is no longer interested in receiving event notifications from http://vcr.local/service1:200.
Step By Step: UCP to CD & Back
This section will take a step by step approach to what happens on both sides (UCP & CD) of an event notification. The description starts at the initialization of a UPnP device. FIG. 24 illustrates the subscription, notification, and unsubscription process.

    1. A UPnP device called “vcr” initializes.
    
        a. It sets itself up to be an HTTP server by doing the following:
        
            i. It binds to a TCP socket using its IP address and an arbitrary port number. This address/port pair will be referenced by all incoming URL requests.
            ii. It listens for incoming connection requests on that socket and sets itself up to accept any incoming connections.
        
        
        b. It sets itself up to be an HTTP client by doing the following:
        
            i. Calls InternetOpen( ) to get a handle to the internet session
        
        
        c. For each service it exposes, it does the following:
        
            i. It calls the SSDP API RegisterUpnpEventSource( ) to let the SSDP server know that it will be accepting subscriptions and sending event notifications. At this point, it has no subscribers. Note that this is called before the service has announced itself so that it can be ready to accept subscriptions immediately. RegisterUpnpEventSource( ) sends no network traffic on the wire. It is a local initialization only. RegisterUpnpEventSource( ) does the following:
            
                1. Adds a structure to the list of event sources containing the following:
                
                    a. A URL to which subscribers will send subscription requests
                    b. A list of destination URLs. A notification message will be sent to each destination URL.
                    c. The state table for the event source. This structure contains the property name, value, and type for each property supported by the service.
                
                
            
            
            ii. It calls the SSDP API RegisterService( ) to let the world know that it has become available. RegisterService( ) will send out an SSDP “alive” message on the multicast channel that will be heard by any device running the SSDP service.
        
        
        d. It starts sending events immediately, even without subscribers. Each event submission updates the local state table. This submission needs to be atomic with regard to adding subscribers, so between the time the SubmitEvent( ) API is called, and the time the local state table is updated, no subscriptions can be added or removed.
    
    
    2. Meanwhile, a UPnP UCP initializes.
    
        a. It initializes its HTTP server, passively listening on a TCP port.
        b. If the UCP started up before the UPnP device initialized, it won't see any services become available. When the device finally starts, the UCP will be notified.
        c. Once the UPnP services have been announced the UCP will be able to access one or more of them.
        d. The UCP drives the UPnP API to instantiate a UPnP Service Object.
        e. The UPnP Service Object does the following when it is instantiated:
        
            i. It obtains the event subscription URL from the description for that service.
            ii. It calls the SSDP API RegisterNotification( ) specifying SSDP_PROPCHANGE as the event type, the event subscription URL, a callback function pointer (which is a static member function of the class), and a context pointer (which is the “this” pointer of the class). RegisterNotification( ) does the following:
            
                1. It makes an LRPC call to the SSDP service. The rest happens on the service side.
                2. If this is the first time it is called for SSDP_PROPCHANGE notifications, RegisterNotification( ) will call InternetOpen( ) to get a handle to an internet session. This handle is shared among all local UPnP UCPs.
                3. It calls InternetConnect( ) passing the server name given in the URL it was passed.
                4. It calls HttpOpenRequest( ) passing in the rest of the URL it was passed.
                5. The handles returned by these functions are saved with the structure that maintains the subscription.
                6. It composes a SUBSCRIBE message, using the data passed in, by calling HttpAddRequestHeaders( ). It adds the “NT”, “Callback”, and “Timeout” headers. The Callback header of the SUBSCRIBE message will be composed on the fly, as an arbitrary URL for notifications to be sent to for this subscription. The server name is the local IP address, and the port is the same one referred to by step 2a above.
                7. It calls HttpSendRequest( ) to send the request to the CD. This is a synchronous function that will return when the request has been responded to by the CD.
                8. It calls HttpQueryInfo( . . . , HTTP_QUERY_CUSTOM, . . . ) to get the “Subscription-Id” header. The resulting SID will be stored with the subscription structure.
                9. It calls HttpQueryInfo( . . . , HTTP_QUERY_CUSTOM, . . . ) to get the “Timeout” header. The resulting timeout value will be stored with the subscription structure.
                10. A timer is started for re-subscription based on the timeout value returned in the response. When the timer goes off, the re-subscription will be sent.
                11. The SID, callback function pointer, and timeout values are stored in a structure that maintains the list of local subscriptions.
            
            
        
        
    
    
    3. Back on the UPnP CD, the subscription request is received by the HTTP server. The following occurs:
    
        a. The request is parsed into URI, NT, Callback, and Timeout fields.
        b. The NT field must match “upnp:event”. If it doesn't, the CD responds with “412 Precondition Failed.”
        c. The URI identifies the event source. The URI is converted into a URL and matched with the list of event sources registered on the CD. If no match is found, the CD responds with “404 Not Found”.
        d. If a match is found, the following occurs:
        
            i. The Callback URL is added to a list of subscriber URLs.
            ii. The Timeout value is processed and an absolute time is stored with the event source data. If this time expires and a re-subscribe message has not been received, the subscription is removed.
            iii. A new SID is created, and stored with the subscriber in the event source.
            iv. A sequence number is initialized to 0.
            v. A subscription response is composed, including an echo of the Timeout header and the SID just created.
            vi. The response is sent.
            vii. If the response is sent successfully, the list of event sources is persisted to disk for recovery purposes.
            viii. A timer is started using the same timeout value as the header echoed to the UCP. When this timer elapses, the subscription is removed. If the CD receives a re-subscribe request, this timer will be reset. In an ideal world, the timer will never elapse.
            ix. An initial event notification is sent to initialize the UCP's state table. The following describes that process:
            
                1. InternetOpen( ) is called if an existing internet session handle does not exist.
                2. InternetConnect( ) is called, passing the server name specified in the callback URL for this subscription.
                3. HttpOpenRequest( ) is called, passing in the rest of the callback URL.
                4. A NOTIFY message is composed, using the data passed in, by calling HttpAddRequestHeaders( ). It adds the “NT”, “NTS”, “SID”, “Seq”, “Content-Length”, and “Content-Type” headers.
                
                    a. The NT header will always be “upnp:event”. The NTS header will always be “UPnP:propertychange”.
                    b. The SID header contains the SID stored in the event source structure
                    c. The Seq header will always be 0.
                    d. The Content-Length header will be the number of bytes in the XML body.
                    e. The Content-Type header will always be “text/xml”.
                    f. The body of the message is composed from the list of properties stored within the event source structure:
                     i. Write the <propertyset> opening tag.
                     ii. Write the <propcount>n</propcount> tag. Where n is the number of total properties.
                     iii. For each property:
                     1. Write the <property> opening tag.
                     2. Write the <prop> opening tag, where prop is the name of the property.
                     3. Write the <type>type</type> tag, where type is the stringized type name of the property type.
                     4. Write the property value.
                     5. Write the </prop> closing tag.
                     6. Write the </property> closing tag
                     iv. Write the </propertyset> closing tag
                
                
                5. It calls HttpSendRequestEx( ), then InternetWriteFile( ), then HttpEndRequest( ) to send the request to the CD.
                6. The response is ignored except for debugging purposes.
            
            
        
        
    
    
    4. The UPnP CD now is ready to send an event notification. It does this by calling the SubmitUpnpPropertyEvent( ) API. The following occurs inside that API:
    
        a. The event source handle is converted to an event source structure.
        b. The properties that have changed as a result of the event are passed into the function and updated in the local list of properties stored with the event source.
        c. For each subscriber, the following occurs:
        
            i. InternetConnect( ) is called, passing the server name specified in the callback URL for this subscription.
            ii. HttpOpenRequest( ) is called, passing in the rest of the callback URL.
            iii. A NOTIFY message is composed, using the data passed in, by calling HttpAddRequestHeaders( ). It adds the “NT”, “NTS”, “SID”, “Seq”, “Content-Length”, and “Content-Type” headers.
            
                1. The NT header will always be “upnp:event”. The NTS header will always be “UPnP:propertychange”.
                2. The SID header contains the SID stored in the event source structure
                3. The sequence number for the event source is incremented and the Seq header is created with this value.
                4. The Content-Length header will be the number of bytes in the XML body.
                5. The Content-Type header will always be “text/xml”.
                6. The body of the message is composed from the list of properties stored within the event source structure:
                
                    a. Write the <propertyset> opening tag.
                    b. Write the <propcount>n</propcount> tag. Where n is the number of total properties.
                    c. For each property that has been submitted:
                     i. Write the <property> opening tag.
                     ii. Write the <prop> opening tag, where prop is the name of the property.
                     iii. Write the <type>type</type> tag, where type is the stringized type name of the property type.
                     iv. Write the property value.
                     v. Write the <Iprop> closing tag.
                     vi. Write the </property> closing tag
                    d. Write the </propertyset> closing tag
                
                
            
            
            iv. SubmitEvent( ) is called, passing the event source handle, the handle to the headers created by 4c (i) thru 4c (iii) above, and the body created in step 4c (iii)6. SubmitEvent( ) does the following:
            
                1. It calls HttpSendRequestEx( ), then InternetWriteFile( ) on the body, then HttpEndRequest( ) to send the request to the CD.
                2. The response is ignored except for debugging purposes.
            
            
        
        
    
    
    5. The UPnP UCP receives the notification message. The message is processed as follows:
    
        a. The HTTP server receives a NOTIFY message with a Request-URI and several other headers.
        b. The NOTIFY message is parsed, looking at the “NT” header first. If this header contains “upnp:event”, then the message is further processed for event notifications as follows:
        
            i. The message is parsed for the NTS header. If that contains “upnp:propertychanged”, then the message is parsed further as follows:
            
                1. The message is parsed for the SID header. The SID indicates to the UPnP control point which subscription this message applies to.
                2. The message is parsed for the “Seq” header. If this header contains a value of 0, the UCP knows this is an initial state populate request. If the local sequence number is exactly one less than the Seq header, the local sequence number is updated (incremented), and the message is processed further.
                3. The Request-URI can be ignored, since the HTTP server knows all NOTIFY messages with an NT header of “upnp:event” are sent to the same Request-URI.
                4. If the Seq header contains a number that is not exactly one more than the local sequence number, the UCP knows it has missed an event. In this state, it needs to unsubscribe and re-subscribe to the event source in order to re-sync its state.
                5. The SID is matched against the list of subscriptions maintained on the UCP. When the SID is matched, its associated callback function is invoked.
                6. The callback function is passed an SSDP_MESSAGE structure which contains all the relevant headers and the body of the XML message received.
                7. The callback function is implemented by the UPnP API, as a static member of the Service object. When this function is called, the following occurs:
                
                    a. The body of the message is parsed using the XML DOM services.
                    b. As properties are enumerated, their values are stored in the local state table for the service.
                    c. An event is fired to all high-level clients of the UPnP API. This event contains the list of properties that have changed and their new values.
                
                
            
            
        
        
    
    
    6. The re-subscription timer for one of the UCPs subscriptions expires. The following occurs:
    
        a. A re-subscribe message is composed. This message is very similar to a subscribe message except in doesn't include an NT or Callback header, but it does have a SID header.
        b. The request is sent to the CD.
        c. The response contains the new timeout value.
        d. The timer is reset with this timeout.

UCP State Synchronization Models

    
    


CD-Initiated NeedsSync Method
This method begins with the CD sending its initial state to the subscriber the first time an event is submitted by the service. UCPs will subscribe to the service first, then receive notifications for events as they occur. The first event will happen to be the initial state of the service. The UCP state table will always be in sync with this method.
When the CD sends a notification to a subscriber and receives an error. In this case, it marks the subscriber as “NeedsSync” and the next time an event is submitted, all events are sent to the subscriber. The problem with this is that the API needs to keep track of which subscribers need syncing and which ones don't. The client of this API (the UPnP service) would need to send separate messages to each subscriber and know which ones needed all events and which ones just wanted the ones that changed.
UCP-Initiated Sync
This method states that the UCP should subscribe to event notifications, then call a function that obtained the state from the service. This means that any events that were received in the meantime would need to be matched against the incoming set of events and replaced if they were older. This method leads to synchronization issues where the UCP may receive events that are newer but when it queries for the state, it gets an older view of the table. This requires using sequence numbers to determine which information is newer. If the view of the table received by the query is too old, it has to be discarded. Alternatively, the properties that were not received by event notification would not be overwritten, but all other properties would be. Using sequence numbers make this more complicated.
CD-Initiated Sync
This preferred method takes a simpler approach. Any time the UCP subscribes to a service, the service will immediately afterwards, send the entire contents of the state table with the first notification. This precludes the UCP from making a query for the state table. Subsequent events update the local state table on the UCP. If the connection is lost, the UCP will lose its subscription. If the UCP realizes it has not received an event after a certain amount of time has elapsed, it will re-subscribe. At that point, the CD will re-send the entire state table again, and the UCP is ensured to be up to date.
Exemplary Computer Hardware
FIG. 25 and the following discussion are intended to provide a brief, general description of a suitable computer which may be used in the above described UPnP device control model. This conventional computer 820 (such as personal computers, laptops, palmtops or handheld-PCs, set-tops, servers, mainframes, and other variety computers) includes a processing unit 821, a system memory 822, and a system bus 823 that couples various system components including the system memory to the processing unit 821. The processing unit may be any of various commercially available processors, including Intel x86, Pentium and compatible microprocessors from Intel and others, including Cyrix, AMD and Nexgen; Alpha from Digital; MIPS from MIPS Technology, NEC, IDT, Siemens, and others; and the PowerPC from IBM and Motorola. Dual microprocessors and other multi-processor architectures also can be used as the processing unit 821.
The system bus may be any of several types of bus structure including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of conventional bus architectures such as PCI, VESA, AGP, Microchannel, ISA and EISA, to name a few. The system memory includes read only memory (ROM) 824 and random access memory (RAM) 825. A basic input/output system (BIOS), containing the basic routines that help to transfer information between elements within the computer 820, such as during start-up, is stored in ROM 824.
The computer 820 further includes a hard disk drive 827, a magnetic disk drive 828, e.g., to read from or write to a removable disk 829, and an optical disk drive 830, e.g., for reading a CD-ROM disk 831 or to read from or write to other optical media. The hard disk drive 827, magnetic disk drive 828, and optical disk drive 830 are connected to the system bus 823 by a hard disk drive interface 832, a magnetic disk drive interface 833, and an optical drive interface 834, respectively. The drives and their associated computer-readable media provide nonvolatile storage of data, data structures, computer-executable instructions, etc. for the computer 820. Although the description of computer-readable media above refers to a hard disk, a removable magnetic disk and a CD, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, and the like, may also be used in the exemplary operating environment.
A number of program modules may be stored in the drives and RAM 825, including an operating system 835, one or more application programs 836, other program modules 837, and program data 838.
A user may enter commands and information into the computer 820 through a keyboard 840 and pointing device, such as a mouse 842. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 821 through a serial port interface 846 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 847 or other type of display device is also connected to the system bus 823 via an interface, such as a video adapter 848. In addition to the monitor, computers typically include other peripheral output devices (not shown), such as speakers and printers.
The computer 820 operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 849. The remote computer 849 may be a server, a router, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 820, although only a memory storage device 850 has been illustrated in FIG. 25. The logical connections depicted in FIG. 25 include a local area network (LAN) 851 and a wide area network (WAN) 852. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
When used in a LAN networking environment, the computer 820 is connected to the local network 851 through a network interface or adapter 853. When used in a WAN networking environment, the computer 820 typically includes a modem 854 or other means for establishing communications (e.g., via the LAN 851 and a gateway or proxy server 855) over the wide area network 852, such as the Internet. The modem 854, which may be internal or external, is connected to the system bus 823 via the serial port interface 846. In a networked environment, program modules depicted relative to the computer 820, or portions thereof, may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to acts and symbolic representations of operations that are performed by the computer 820, unless indicated otherwise. Such acts and operations are sometimes referred to as being computer-executed. It will be appreciated that the acts and symbolically represented operations include the manipulation by the processing unit 821 of electrical signals representing data bits which causes a resulting transformation or reduction of the electrical signal representation, and the maintenance of data bits at memory locations in the memory system (including the system memory 822, hard drive 827, floppy disks 829, and CD-ROM 831) to thereby reconfigure or otherwise alter the computer system's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, or optical properties corresponding to the data bits.
Exemplary Embedded Computing Device
FIGS. 26 and 27 are intended to provide a brief, general description of a suitable embedded computing device 900 which may be used in the illustrated implementation of the invention. The embedded computing device 900 can be any variety of device incorporating electronics to control operational functions (operational circuitry 906), and in which computing and networking capabilities are embedded. For example, devices in which computing and networking functions can be embedded include communications devices (e.g., telephones, cell phones, audio and video conferencing systems, 2-way radios, etc.), office equipment (printers, fax machines, copiers, dictation, etc.), audio-video equipment (audio and video recorders and players, including televisions, radio receivers, compact disk (CD), digital video disk (DVD), camcorders, etc.), entertainment devices (set-top boxes, game consoles, etc.), environment control equipment (thermostats, heating/ventilation/air-conditioning equipment, light switches, etc.), security systems, home appliances (coffee makers, dishwashers, clothes washer/dryer), automobiles, public facilities equipment (signs, traffic signals, etc.), manufacturing equipment, and many others.
With reference to FIG. 26, the device 900 includes a processing unit 902, and a memory 904 to provide embedded computing capability. The processing unit 902 has hardware interfaces to the operational circuitry 906 that operates devices functions. The processing unit 902 can be a microprocessor or micro-controller, such as are available from Intel, Motorola, IBM, and others. The memory 904 preferably incorporates RAM and ROM to hold software and data for basic operating code as well as for user applications.
The device 900 also includes a network adapter 908 for connecting with a network media 910 that is interconnected with the computer network in which the authoritative names registry (described below) is implemented in accordance with the invention. The network adapter 908 can be a network interface card (or chip set integrated on a single board with the processing unit 902) appropriate to the particular network media 910. The network media can be any of various wired or wireless network media, including Ethernet, IEEE 1394 (a.k.a. firewire), radio frequency (including satellite, cell, pager, commercial signal sideband, etc.), power line carrier (PLC), phone line, and television cable, among others.
With reference now to FIG. 27, the embedded computing device 100 (FIG. 26) has a software architecture 120 that conforms to the above described UPnP device control model. UPnP provides a mechanism for the embedded computing device to operate in the Internet, as well as networks that have no administrator and no connection to the Internet, and hence no access to configuration services like the Dynamic Host Configuration Protocol (DHCP). DHCP is a mechanism for providing devices with configuration information needed to access the Internet. The mechanism functions through the use of a multicast request for configuration information that is generally responded to with an IP address and DNS server location. Additional information can only be returned in the response.
In non-configured (ad-hoc) networks, UPnP uses the AutoIP protocol. AutoIP is an enhancement to DHCP that allows devices to claim IP addresses in the absence of a DHCP server or similar IP configuration authority. IP addresses are claimed from a reserved range that is not allowed to be transmitted on the open Internet; thus they are only good for the local network. The embedded computing device 100 claims an address by randomly generating an address in the reserved range and then making an ARP request to see if anyone else has already claimed that address. AutoIP systems will continually check for the presence of a DHCP server so that if one should ever come online, all the AutoIP devices will attempt to switch their IP addresses to one provided by the DHCP server. This allows a network to operate in isolation, be connected to the Internet with DHCP support and then to be returned to isolation. This type of scenario will be common in homes that use dial-up access.
UPnP also uses the Internet Domain Name System (DNS) for addressing the embedded computing device 900. The DNS is a mapping system that translates human readable domain names, like microsoft.com, into their equivalent IP address. Most corporate intranets implement an internal version of the same technology to provide the same services. In small networks, such as at home or in small business, DNS servers may not exist. Multicast DNS allows DNS requests to be multicast. This allows a machine to see requests for its own name and respond to them. Like AutoIP, Multicast DNS is only used when a DNS server is not available. (For more information, see B. Woodcock, Zocolo, and B. Manning, “Multicast Discovery of DNS Services,” which can be found at http://search.ietf.org/internet-drafts/draft-manning-multicast-dns-01.txt.)
UPnP implements a peer discovery mechanism that uses the Simple Service Discovery Protocol (SSDP) for discovery of devices on IP networks. SSDP is based on profiles. A single identifier specifies a profile that defines a contract between the client and service (e.g., operational functions provided by the embedded computing device). By identifying itself with the profile, the service advertises compliance with the associated contract.
Using a single identifier makes it possible to implement an extremely simple discovery system. Clients send out a User Datagram Protocol (UDP) multicast packet containing the identifier of the desired service on some standard channel. Services listen on the standard channel, read the request, see whether they provide the service, and respond if so.
UPnP also provides a Directories mechanism to allow discovery to scale—to the entire Internet if needed. When present, a directory will read all incoming service requests and respond to them itself. This requires that all services (e.g., the embedded computing device 900) register with the directory so that the directory is able to properly answer on their behalf. The directory is also responsible for communicating with other directories in order to determine whether the service is available within the local network, the WAN and potentially the Internet.
To simplify the discovery protocol, directories are treated as proxies. A proxy is a service that accepts requests and takes responsibility for finding the proper response. When a client comes online, it will perform discovery for the proxy. If the proxy is present, then the client will send all future discovery requests to the proxy. If the proxy isn't present, then the client will send all discovery requests to the reserved discovery multicast channel. Regardless of the presence of a proxy, the client's request format and procedures will always be the same. The only difference will be the address to which the client sends its requests. For services, the difference between a proxied and unproxied network is their need to answer discovery requests. On a proxied network, services need do nothing once they have registered with the proxy. On an unproxied network, they answer discovery requests directly.
SSDP uses the UDP- and Transmission Control Protocol (TCP)-based Hyptertext Transport Protocol (HTTP) to provide for service discovery. SSDP uses a Uniform Resource Identifier (URI) to represent the service and the OPTIONS method to provide for discovery. SSDP also will provide support for proxies. These proxies, which are really just fronts for directories, redirect discovery requests to themselves. It is the proxy's job to collect announce requests in order to determine what services are available as well as to communicate with other proxies in order to provide for scalable service discovery.
The discovery process returns only the basic information needed to connect to the embedded computing device. Once a service has discovered its peers, the service often needs to find out more information in order to work best with them. The description process returns a schema providing descriptive data about the service.
A schema is a structured data definition that defines a set of structured values that provide descriptive information about a service. UPnP uses the Extensible Markup Language (XML) for schema, because XML's self-describing structured data format provides the level of expressiveness and extensibility needed by a universal schema and data format.
Accordingly, UPnP supports automatic network introduction, meaning that devices and their related services have the ability to be self-describing and allow automatic configuration. When a device is plugged into the computer network, the device automatically configures itself and acquires a TCP/IP address. The device then announces its presence to other devices already on the network using a simple discovery protocol based on the Internet HTTP protocol and is immediately ready to share its services with any device that requests them.
With UPnP, device developers are not required to develop specific device drivers to operate under UPnP. The task of preparing a device for operation in this network environment thus is fairly simple. Moreover, in configured networks, dynamic detection allows an operating system to immediately begin using added devices or stop using removed devices without rebooting.
UPnP Devices support automatic discovery, identification, and configuration to achieve interoperability in the home environment, but must also operate correctly in a managed corporate network. Devices can be networked instead of being attached directly to a PC, and devices are all autonomous citizens on the network, able to talk with each other and exchange information. UPnP provides a unified way of performing directory services with automatic configuration. Capability for simple discovery mechanism used in the home environment provides the ability for any device to become a node on the global Internet. Additionally, directory services can be leveraged if they are available in the corporate environment.
UPnP provides a common set of interfaces for accessing devices and services, enabling the operational unification of diverse media types. Communications protocols for Universal Plug and Play are based on industry standards, especially key Internet standards such as TCP/IP, HTML, XML, HTTP, DNS, LDAP, and others. Individual implementations for particular networks and buses are built on established protocols.
As shown in FIG. 27, the software architecture 920 of the embedded computing device 900 (FIG. 26) includes the following software code modules that implement UPnP: device functions 922, simple discovery 924, Hypertext Transport Protocol (HTTP) 925, Transmission Control Protocol/Internet Protocol (TCP/IP) stack 926, Dynamic Host Configuration Protocol (DHCP) with AutoIP extension 928, Domain Name System (DNS) with Multicast DNS extension 930, and physical media 910 (also shown in FIG. 26). The device functions 922 is a software code module to implement the device's functionality. For example, where the embedded computing device is a VCR, the device functions code can include code to implement start, stop, pause, record and other functions that the VCR can perform.
The simple discovery 924 is a software code module (about 4 Kbytes) that implements a simple discovery procedure (described below) for automatic network introduction under the UPnP protocol.
The simple discovery procedure additionally provides an Extensible Markup Language (XML) format device description, which is downloaded to clients that access the device to allow activation of device functionality from the client. XML is a textual, tag-based markup language. It was originally designed to be the “Webby” simplification of SGML (Standard Generalized Markup Language), and is therefore intended to be used to create “vocabularies” of tags that can be used to apply semantic markup to documents, such as who the author was, what constitutes a paragraph (semantically, not from a display point of view), when the author last had breakfast, and so on. (For more information, see A. Layman, E. Jung, E. Maler, H. Thompson, J. Paoli, J. Tigue, N. H. Mikula, S. De Rose, “XML-Data”, which can be found at http://www.w3.org/TR/1998/NOTE-xml-data-0105; and MSDN Online, XML Data Center at http://msdn.microsoft.com/xml/default.asp.) In the context of UPnP, XML is used to provide the description of services and capabilities of the embedded computing device. The embedded computing device makes its features visible to clients by providing its XML device description, which the client can use to activate device functions 922. For example, if the device is a camera, the client's browser can direct the camera to zoom in/out or adjust contrast using the mechanism of XML.
The XML device description can provide links (via a uniform resource locator or URL address) to an accompanying XSL format style sheet. The XSL style sheets are used to present the data in different ways, i.e., the style sheets are applied to present different views of the same data. For example, if the device contains a file system, one style sheet can show the file selections; another shows the file sizes in some sort of diagram; yet another style sheet could make thumbnails of these image files.
The HTTP 925 is a software code modules (about 20 Kbytes) that implements the standard HTTP protocol, which is an open standard mechanism for client/server message-based communication. HTTP provides for proxying, content negotiation and security. (For more information, see R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee, “Hypertext Transfer Protocol-HTTP/1.1”, which can be found at http://www.ietf.org/rfc/rfc2068.txt.) The TCP/IP stack 926 implements the standard TCP/IP networking protocols for communication on the computer network. The Internet Protocol (IP) is the foundation protocol of the Internet. It defines how a single message is sent from a source through zero or more routers to its final destination. It covers issues such as message length, message fragmentation, addressing, and routing concerns. The Transmission Control Protocol (TCP) is an IP-based protocol that provides support for the reliable, ordered delivery of messages over IP. Additionally, User Datagram Protocol (UDP) and Internet Group Management Protocol (IGMP) multicast send/listen capability are included in the implementation.
The AutoIP 928 is a software code module also used for automatic network introduction via AutoIP in the UPnP protocol. AutoIP uses a predefined set of IP addresses and, when a device is connected to the network, it pings an address in this address space. If it gets no replies, the device assumes that the address is available and assigns it to itself. To make this functionality even more useful it is combined with Multicast DNS, in which the device itself holds its own name. Thus it is not even necessary to determine what IP address the device assigned to itself, because its name can always be used instead. An IP Multicast is a mechanism for sending a single message to multiple recipients. IP multicasting is especially useful for discovery operations where one does not know exactly who has the information one seeks. In such cases, one can send a request to a reserved IP multicast address. Any services that can provide the requested information will also subscribe to the multicast request and thus be able to hear the information request and properly respond. Multicast DNS is a proposal to the IETF on rules for making normal DNS requests using multicast UDP. (For more information, see B. Woodcock, B. Manning, “Multicast Discovery of DNS Services”, which can be found at http://www.ietf.org/internet-drafts/draft-manning-multicast-dns-01.txt.)
The DHCP 930 is a software code module that implements the Dynamic Host Configuration Protocol (DHCP), which is a mechanism for providing devices with configuration information needed to access the Internet. The mechanism functions through the use of a multicast request for configuration information that is generally responded to with an IP address and DNS server location. Additional information can only be returned in the response.
FIGS. 28 and 29 show processes 934, 940 per the UPnP protocol for automatic network introduction of the embedded computing device 900 (FIG. 26) into an ad hoc (where the device does not have a configured IP address) and a configured computer network environment, respectively. The automatic network introduction process establishes an appropriate configuration (e.g., with an IP address) of the embedded computing device upon connection to a server computer on a computer network, so as to enable access to the device from a client. The processes 934, 940 involve five phases: AutoIP, announce, discovery, response to discovery, and device description.
At the AutoIP phase, the AutoIP module 928 of the embedded computing device 900 uses a predefined set of IP addresses and, when the device is connected to the network, it pings an address in this address space. If no reply is received, the device 900 assumes that the address is available and assigns it to itself. Alternatively, the device 900 may combine AutoIP with Multicast DNS, and itself hold its own name. In which case, it is not necessary to determine what IP address the device assigned to itself, because its name can always be used instead.
At the announce phase, the embedded computing device 900 sends out a small multicast packet so that other devices can find it on the network. The multicast message packet essentially says, “I am here, I am, (say), a camera, and you can reach me at this IP address or URL.”
At the discovery phase, the embedded computing device 900 listens for a discovery packet coming from a simple discovery client, i.e., the device announces itself, then listens for discovery. The discovery packet also is sent out by multicast.
At response to discovery, the embedded computing device 900 listens to the multicast address and then parses the information from a Simple Discovery request to decide if the request is for its kind of device. If so, the device 100 then sends back a response packet containing the following information: the IP address or URL where it can be reached; identification of its own device type; and the discovery packet ID so the requesting client knows which request is being answered.
Both the Announce and Discovery packets also contain a link or a URL to an XML file that is used by the embedded computing device at the device description phase to describe itself (i.e., its functionality). This XML data contains all the facts about the device. XML can also have URLs that point to appropriate style sheets (XSL files) that are used for optimal presentation. The XSL style sheets are used to present the data in different ways, i.e., the style sheets are applied to present different views of the same data. For example, if the device contains a file system, one style sheet can show the file selections; another shows the file sizes in some sort of diagram; yet another style sheet could make thumbnails of these image files.
Exemplary Client
With reference now to FIG. 30, a client that accesses and uses the embedded computing device 900 over the computer network has an exemplary client software architecture 950, which includes software code modules for applications 952, simple discovery 954, XML 955, LDAP 956, TCP/IP stack 958 and a network interface card (NIC) 960 that provides a physical connection to the computer network. The applications 952 is a software code module that provides a user interface features for locating desired devices (e.g., embedded computing device 900) and services on the computer network, and also user interface features to interact with the located device or service. The applications 952 can include an Internet browser, such as the Microsoft Internet Explorer, that can present the XML device description in accordance with an associated XSL style sheet for interaction with the embedded computing device and activation of its operational functionality.
The simple discovery 954 is a module that implements the above-described simple discovery per the UPnP protocol. The XML 955 is a module that processes the XML device description and XSL style sheets for presentation in the application's user interface. The LDAP 956 implements the standard LDAP directory protocol for name look-up. The TCP/IP stack 958 implements the TCP/IP protocol for communications over the computer network.
Illustrative Pervasive Computing Environment
FIG. 31 illustrates a pervasive computing environment 1000, such as may be installed in a home, office or public place, which includes a large number of embedded computing devices, such as the illustrated device 900 (FIG. 26). The pervasive computing environment 1000 includes personal computers 1002, 1004 (e.g., of the type shown in FIG. 25) connected via a local area network (LAN) 1006. The PC 1002 is connected via a universal serial bus 1016 to a telephone modem 1010, XDSL interface 1011 or a cable modem 1012, which in turn provide a connection with the computer network, e.g., the Internet.
Various embedded computing devices also connect to the computer network via various network connections to the PCs 1002, 1004. These include an audio device 1014 (e.g., speakers, radio tuner, microphone), and printer 1015 which connect to the PC 1004 through a USB 1017. Also, a digital camera 1020, a handheld PC (H/PC) 1021 and another personal computing device 1022 connect via an infrared port (IRDA) 1024, which also attaches to the PC 1004 through the USB 1017. Also, lighting switches 1030 and like home appliances are connected via an A/C power line-based networking 1032 to the PC 1002. Further, a chain of IEEE 1394 cables 1048 connect a digital TV 1040, DVD player 1041, digital video camcorder (DV/DVC) 1042, an audio device 1043 (e.g., CD player/recorder, radio receiver, amplifier, and like audio system component), and a game console 1044. Devices, such as a portable telephone 1050 and remote control 1051, have a radio frequency network connection with the PC 1004.
With their various inter-networked connections, the embedded computing devices are “visible” and accessible from a client device 950 (FIG. 31) also connected to the computer network.
Contract Definition Language
Overview
Contracts describe the public behavior of UPnP devices, and alternatively of other entities on the Web (reachable via HTTP, mostly) or other computer network that react to and emit messages. The Contract is written in a Contract Definition Language (CDL). The messages for the most part are structured documents, e.g., in XML. The messages may also be HTML pages, streaming media, images or other datatypes.
The contract will describe the following attributes:

    
    
        end-point (well-defined name)
        protocol
        messaging patterns
        delivery characteristics
        payloads
    
    


All of these attributes may not be present in the contract as some of them (the end-point, for instance) may not be available at development time.
Protocol Description
Entities on the Web can be accessed using multiple protocols: HTTP, GENA, SMTP, FTP, MSMQ, . . . This section discusses how the protocol bindings are explicitly declared. The templates for describing the protocol use the format:















<protocol>









<HTTP>



// HTTP specific settings go here



</HTTP>









</protocol>



<protocol>









<HTTP>



// GENA specific settings go here



</HTTP>









</protocol>










The “protocol” element may have an “id” attribute. This is useful when multiple messaging patterns will use the same protocol definition. This will be covered in more detail below.
For the sake of convenience, we only cover HTTP-based protocols here. Extending this model to cover the other protocols is straightforward.
HTTP
GET















<protocol>









<HTTP version=“1.0”>









<GET/>









<URL> http://neteye.local/fullsize.jpg









</URL>









</HTTP></protocol>










GET with query string















<protocol>









<HTTP version=“1.1”>









<GET/>



<URL> http://search.yahoo.com/bin/search



</URL>



<QUERY name=“pattern” required=“yes” />



<QUERY name=“limit” value=“50” required=“no”









/>









<QUERY name=“xml” value=“yes” required=“yes”









/>



</HTTP>



</protocol>










This description indicates that the following are valid URLs:

    
    
        http://search.yahoo.com/bin/search?pattern=Rio+player&limit=50&xml=yes
        http://search.yahoo.com/bin/search?xml=yes&pattern=Rio+player
    
    


The reason for not associating the query variables with the GET verb is because it is valid to send a POST message to a URL containing query variables.
The “value” attribute for the “QUERY” element implies that the value is static—it is to be treated as a part of the URL. Declaring it this way allows the appropriate construction of the query string to be handled by the caller. POST















<protocol>









<HTTP version=“1.1”>









<URL>









http://www.amazon.com/exec/obidos/generic-



quicksearch-query </URL>









<POST>










<PARAM name=“mode”
default=“blended”









required=“yes” />









<PARAM name=“keyword-query”









required=“yes” />










<PARAM name=“zipcode”
value=“98112”









required=“yes” />









</POST>









</HTTP>









</protocol>










The default attribute indicates that the parameter's value can be changed.
M-POST















<protocol id=“protocolDef”>









<HTTP version=“1.1”>









<URL> http://investor.msn.com/stockquotes.xsp









</URL>









<QUERY name=“symbol” required=“yes” />



<M-POST>









<MAN> http://www.upnp.org/service-control/m-










post
</MAN>









</M-POST>



<HEADER name=“Content-Type” value=“text/xml” />









</HTTP>









</protocol>










The M-POST and the enclosed MAN elements declare the mandatory extension mechanism to be used. The optional extension mechanism can also be handled in this way.
The “HEADER” element allows the declaration of HTTP headers to be used.
GENA
Payload Description
Below is an example of an XML payload description.















<schema xmlns=“urn:schema-microsoft-com:xml-data”









xmlns:dt=“urn:schema-microsoft-









com:datatypes”>



//



// symbol: a ticker symbol



//



<ElementType name=“symbol” dt:type=“string” />



//



// symbols: array of “symbol” elements



//



<ElementType name=“symbols”>









<element type=“symbol” maxOccurs=“*” />









</ElementType>



//



// stockQuote: quote details



//



<ElementType name=“stockQuote”>









<element type=“company” />



<element type=“ticker” />



<element type=“previousClose” />



<element type=“openingTrade” />



<element type=“lastTrade” />



<element type=“volume” />









</ElementType>



<ElementType dt:type=“string” name=“company” />



<ElementType dt:type=“string” name=“ticker” />



<ElementType dt:type=“string” name=“previousClose”



/>



<ElementType dt:type=“string” name=“openingTrade”



/>



<ElementType dt:type=“string” name=“lastTrade” />



<ElementType dt:type=“string” name=“volume” />



//



// stockQuotes: array of “stockQuote” elements



//



<ElementType name=“stockQuotes”>









<element name=“stockQuote” maxOccurs=“*” />









</Element>



//



// error: error info



//



<ElementType name=“error”>









<element type=“reason” />









</ElementType>



<ElementType dt:type=“string” name=“reason” />



</schema>










Using this declaration, the below are valid XML fragments:















<symbol> MSFT </symbol>



<symbols>










<symbol> MSFT
</symbol>



<symbol> IBM
</symbol>



<symbol> AOL
</symbol>



<symbol> YHOO
</symbol>



<symbol> AMZN
</symbol>









</symbols>



<stockQuote>









<company>Microsoft%20Corporation</company>



<ticker>MSFT</ticker>



<previousClose>84%2011/16</previousClose>



<openingTrade>85%201/16</openingTrade>



<lastTrade>84%205/16</lastTrade>



<volume>28.66%20Mil</volume>









</stockQuote>










Messaging Patterns
The messaging pattern declaration acts as an anchor for pulling together the protocol, delivery characteristics and the payload information. The messaging pattern declarations can include these types.

    
    
        Request/response
        Solicit/response
        One way
    
    


Request/response (RR). The RR pattern is named. The two samples below are equivalent mechanisms for declaring the protocol to be used for the RR messaging pattern. The linking mechanism is useful when multiple RR pairs use the same protocol data. This is the case for UPnP. Also, a service may employ multiple protocols for achieving the same “method”-call. The “is” attribute accepts a list of ID-Refs—implying that either of the protocols are equally suitable for accessing the functionality.















<RequestResponse name=“getImage”>









<protocol>









<HTTP version=“1.0”>









<GET/>



<URL> http://172.30.184.20/fullsize.jpg









</URL>









</HTTP>









</protocol>



. . .









</RequestResponse>



<protocol id=“protocolDef1”>









<HTTP version=“1.0”>









<GET/>



<URL> http://172.30.184.20/fullsize.jpg </URL>









</HTTP>









</protocol>



<RequestResponse name=“get Image”>









<protocol is=“protocolDef1” />



. . .









</RequestResponse>










The payloads for request, response and error, in case of XML data, are identified by the names of the elements referenced by the “is” attribute. The schema information is assumed to be in the same document. Below are examples using the two schemes:















<RequestResponse name=“getQuote”>









// protocol declaration goes here










<in
is=“symbol” />



<out
is=“stockQuote” />



<error
is=“error” />









</RequestResponse>



<RequestResponse name=“getQuote”









xmlns:f=“http://electrocommerce.org/finance.xml”



xmlns:c=“http://electrocommerce.org/common.xml”









>









// protocol declaration goes here










<in
is=“f:symbol” />



<out
is=“f:stockQuote” />



<error
is=“c:error” />









</RequestResponse>










The CDL described herein keeps the element declarations in the “schema” block rather than sprinkle them in with the messaging pattern definitions. The reasons for this are:

    
    
        Re-use of element declarations is easy.
        We can re-use fragment validation support as is.
        Keeping schemas in one place is consistent with the use of in-line schemas in SQLI2 and ADO.
    
    


In case the request or response are not XML documents but HTML documents, or binary files, the following syntax will be used. The contained element defines the nature of the data. The use of MIME is not in the HTTP-specific sense but in the “nature of the payload” sense. The presence of the “is” attributes indicates that the MIME type is “text/xml.”















<RequestResponse name=“getImage”>









. . .



<out>









<mime type=“image/jpeg”/>









</out>



. . .









</RequestResponse>










Delivery Characteristics
The contract may specify the delivery characteristics (sometimes also referred to as quality of service) required or supported by the server. Examples are:

    
    
        Ordered, best-effort
        Guaranteed delivery
        Fire-and-forget
        Exactly once
        At least once
        Transactional
    
    


EXAMPLE
FIGS. 45-47 depict an exemplary contract for interacting with a stock quote Service.
FIGS. 48-51 depict an XML schema for defining Contracts.
Having described and illustrated the principles of our invention with reference to an illustrated embodiment, it will be recognized that the illustrated embodiment can be modified in arrangement and detail without departing from such principles. It should be understood that the programs, processes, or methods described herein are not related or limited to any particular type of computer apparatus, unless indicated otherwise. Various types of general purpose or specialized computer apparatus may be used with or perform operations in accordance with the teachings described herein. Elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa.
In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.
UPnP Template Language
UPnP forum working committees define UPnP device templates to describe various devices and services. The templates are written in a UPnP template language, which evolved in part from the Contract Definition Language described in the previous section. The template language defines well-formed templates for devices and services. It is written in XML syntax and is derived from XML Schema. Because the UPnP template language, UPnP device templates, and UPnP device descriptions are all machine-readable, automated tools can automatically check to ensure that the templates and descriptions have all required elements, are correctly nested, and have values of the correct data types.
To describe the UPnP template language, it is useful to once again visit the general UPnP device architecture in terms of a set of processes—discovery, description, control, eventing, and presentation—that utilize the following protocol stack.













Protocol Stack









UPnP vendor



UPnP Forum



UPnP Device Architecture



SSDP/GENA/SOAP



HTTPMU



UDP



IP










At the highest layer, messages logically contain only UPnP vendor-specific information about their devices. Moving down the stack, vendor content is supplemented by information defined by UPnP forum working committees, which is written in the template language.
Messages are formatted using the Simple Service Discovery Protocol (SSDP), General Event Notification Architecture (GENA), and Simple Object Access Protocol (SOAP). The above messages are delivered via HTTP, either a multicast or unicast variety running over UDP, or the standard HTTP running over TCP. Ultimately, all messages above are delivered over IP.
To briefly recap the UPnP networking process, given an IP address, the first step is discovery. When a device is added to the network, the UPnP discovery protocol allows that device to advertise its services to control points on the network. Similarly, when a control point is added to the network, the UPnP discovery protocol allows that control point to search for devices of interest on the network. The fundamental exchange in both cases is a discovery message containing a few, essential specifics about the device or one of its services, e.g., its type, identifier, and a pointer to more detailed information. The UPnP discovery protocol is based on the Simple Service Discovery Protocol (SSDP).
The second step in UPnP networking is description. After a control point has discovered a device, the control point still knows very little about the device. For the control point to learn more about the device and its capabilities, or to interact with the device, the control point retrieves the device's description from the URL provided by the device in the discovery message. Devices may contain other, logical devices, as well as functional units, or services. The UPnP description for a device is expressed in XML and 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. How devices are described using the template language is explained below in more detail.
The third step in UPnP networking is control. After a control point has retrieved a description of the device, the control point has the bare essentials for device control. To learn more about the service, a control point retrieves a detailed UPnP description for each service. The description for a service is also expressed in XML and includes a list of the commands, or actions, the service responds to, and parameters, or arguments, for each action. The description for a service also includes a list of variables, which model the state of the service at run time and are described in terms of their data type, range, and event characteristics. To control a device, a control point sends an action request to a device's service by sending a suitable control message to the URL for control URL for the service (provided in the device description). Control messages are also expressed in XML using the Simple Object Access Protocol (SOAP). In response to the control message, the service provides a simple acknowledgement; unlike function calls, no service-specific value is returned. The effects of the action, if any, are modeled by changes in the variables that describe the run-time state of the service.
The fourth step in UPnP networking is eventing. A UPnP description for a service includes a list of actions the service responds to and a list of variables that model the state of the service at run time. The server publishes updates when these variables change, and a control point may subscribe to receive this information. The server publishes updates by sending event messages, which contain the names of one of more state variables and the current value of those variables. These messages are also expressed in XML and formatted using the General Event Notification Architecture (GENA). A special initial event message is sent when a control point first subscribes; this event message contains the names and values for all evented variables and allows the subscriber to initialize its model of the state of the service. To support scenarios with multiple control points, eventing is designed to keep all control points equally informed about the effects of any action. Therefore, all subscribers are sent all event messages, subscribers receive event messages for all evented variables (not just some), and event messages are sent no matter why the state variable changed (either in response to a requested action or because the state the service is modeling changed).
The fifth step in UPnP networking is presentation. If a device has a URL for presentation, then the control point can retrieve a page from this URL, load the page into a browser, and depending on the capabilities of the page, allow a user to control the device and/or view device status. The degree to which each of these can be accomplished depends on the specific capabilities of the presentation page and device.
UPnP Template Language for Devices
The template language can be applied to create descriptions for both devices and the services. The template language as it pertains to devices is described in this section. A following section addresses the template language as it pertains to services.
After a control point has discovered a device, the control point still knows very little about the device. It only knows the information that was in the discovery message (e.g., the device's (or service's) UPnP type, the device's universally-unique identifier, and a URL to the device's UPnP description). For the control point to learn more about the device and its capabilities, or to interact with the device, the control point retrieves the device's description from the URL provided by the device in the discovery message.
The UPnP description for a device includes vendor-specific, manufacturer information like the model name and number, serial number, manufacturer name, URLs to vendor-specific Web sites, etc. (details below). The description also includes a list of any embedded devices or services, as well as URLs for control, eventing, and presentation. The device vendor writes the description for the device. The description is in XML syntax and is usually based on a standardized device template produced by a UPnP forum working committee.
A single physical device may include multiple logical devices. Multiple logical devices can be modeled as a single root device with embedded devices (and services) or as multiple root devices (perhaps with no embedded devices). In either case, there is one UPnP description for each root device, with embedded device descriptions as needed.
Retrieving the UPnP description for a device is simple: the control point issues an HTTP GET request on the URL in the discovery message, and the device returns the description document. The protocol stack, method, headers, and body for the response and request are explained in detail below.
Vendors can differentiate their devices by extending services, including additional UPnP services, or embedding additional UPnP devices. When a control point retrieves a particular device's description, these added features are exposed to the control point for control, eventing, and presentation.
The following subsection A explains how devices are described, explaining details of vendor-specific information, embedded devices, and URLs for control, eventing, and presentation. Subsections B and C explain UPnP device templates and the UPnP template language as it pertains to describing devices. Finally, subsection D explains in detail how a control point retrieves a description from a device.
A. Device Description
The UPnP description for a device contains several pieces of vendor-specific information, definitions of embedded devices and services, and URLs for control, eventing, and presentation of the device. To illustrate these, below is a listing with placeholders (in italics) for actual elements and values. Some of these placeholders would be specified by a UPnP forum working committee (underlined) or by a UPnP vendor (bold). Elements of the template language are bolded and underlined. Immediately following the listing is a detailed explanation of the elements, attributes, and values.












<?xml version=“1.0”?>


<root xmlns=“urn:schemas-upnp-org:device:1:0”>









<specVersion>









<major>1</major>



<minor>0</major>









</specVersion>



<URLBase> </URLBase>



<device>









<deviceType>urn: schemas-upnp-org: device: device-







type</deviceType>









<friendlyName> </friendlyName>



<modelDescription> 







 </modelDescription>









<modelName> </modelName>



<modelNumber> </modelNumber>



<modelURL> </modelURL>



<manufacturer> </manufacturer>



<manufacturerURL> 







 </manufacturerURL>









<serialNumber> </serialNumber>



<UDN>uuid:schemas-upnp-org:device:



device-type:UUID</UDN>



<UPC> </UPC>



<iconList>









<icon>









<mimetype> </mimetype>



<width> </width>



<height> </height>



<depth> </depth>



<url> </url>









</icon>



 









</iconList>



<serviceList>









<service>









<serviceType>









urn:schemas-upnp-org:service:service-type:service- 







version









</serviceType>



<serviceId> </serviceId>



<SCPDURL> </SCPDURL>



<controlURL> </controlURL>



<eventSubURL> </eventSubURL>









</service>



Declarations for other services defined by a UPnP Forum



working committee (if any) go here



   



 









</serviceList>



<deviceList>









Description of embedded devices defined by a UPnP



Forum working committee (if any) go here



   



 









</deviceList>



<presentationURL> </presentationURL>









</device>







</root>









Listed below are details for each of the elements, attributes, and values appearing in the listing above. All elements and attributes are case sensitive; HTTP specifies case sensitivity for URLs; other values are not case sensitive except where noted. The order of elements is insignificant. Except where noted: required elements occur exactly once (no duplicates), and recommended or optional elements may occur at most once.

    xml
    
        Required for all XML documents. Case sensitive.
    
    
    root
    
        Required. Must have urn:schemas-upnp-org:device:1:0 as the value for the xmlns attribute; this references the UPnP Template Language (described below). Case sensitive. Contains all other elements describing the root device, i.e., contains the following sub elements:
        specVersion
        
            Required. Contains the following sub elements:
            major
            Required. Major version of the UPnP Device Architecture. Must be 1.
            minor
            Required. Minor version of the UPnP Device Architecture. Must be 0.
        
        
        URLBase
        
            Optional. Defines the base URL. Used to construct fully-qualified URLs. All relative URLs that appear elsewhere in the description are appended to this base URL. If URLBase is empty or not given, the base URL is the value of the LOCATION header in the discovery message. Specified by UPnP vendor. Single URL.
        
        
        device
        
            Required. Contains the following sub elements:
            deviceType
            
                Required. UPnP device type.
                
                    For standard devices defined by a UPnP forum working committee, must begin with urn:schemas-upnp-org:device: followed by a device type suffix (as shown in the listing above).
                    For non-standard devices specified by UPnP vendors, must begin with urn:, followed by a domain name owned by the vendor, followed by :device:, followed by a device type suffix, i.e., urn: domain-name: device: device-type.
                
                
                Single URI.
            
            
        
        
        friendlyName
        
            Required. Short description for end user. Should be localized (cf. ACCEPT-LANGUAGE header). String. Should be <64 characters.
        
        
        manufacturer
        
            Required. Manufacturer's name. Specified by UPnP vendor. String. Should be <64 characters.
        
        
        manufacturerURL
        
            Optional. Web site for Manufacturer. May be relative to base URL. Specified by UPnP vendor. Single URL.
        
        
        modelDescription
        
            Recommended. Long description for end user. Should be localized (cf. ACCEPT-LANGUAGE header). Specified by UPnP vendor. String. Should be <128 characters.
        
        
        modelName
        
            Required. Model name. Specified by UPnP vendor. String. Should be <32 characters.
        
        
        modelNumber
        
            Recommended. Model number. Specified by UPnP vendor. String. Should be <32 characters.
        
        
        modelURL
        
            Optional. Web site for model. May be relative to base URL. Specified by UPnP vendor. Single URL.
        
        
        presentationURL
        
            Recommended. URL to presentation hosted by device (cf. section on Presentation). May be relative to base URL. Specified by UPnP vendor. Single URL.
        
        
        serialNumber
        
            Recommended. Serial number. Specified by UPnP vendor. String. Should be <64 characters.
        
        
        UDN
        
            Required. Universal Device Name. Universally-unique identifier for the device, whether root or embedded.
            
                For standard devices defined by a UPnP forum working committee, must begin with uuid:schemas-upnp-org:device: followed by the device type, colon; UPnP vendor specifies UUID suffix (as shown in the listing above).
                For non-standard devices specified by UPnP vendors, must begin with uuid:, followed by a domain name owned by the vendor, followed by :device:, followed by the device type, colon, followed by a UUID suffix, i.e., uuid:domain-name:device:device-type:UUID.
            
            
            Single URI.
        
        
        UPC
        
            Optional. Universal Product Code. 12-digit, all-numeric code that identifies the consumer package. Managed by the Uniform Code Council. Single UPC.
        
        
        iconList
        
            Required if and only if device has one or more icons. Contains the following sub elements:
            icon
            
                Recommended. Icon to depict device in a control point UI. Recommend one icon in each of the following sizes (width×height×depth): 16×16×1, 16×16×8, 32×32×1, 32×32×8, 48×48×1, 48×48×8. Contains the following sub elements:
                mimetype
                
                    Required. Icon's MIME type (cf. RFC 2387). Single MIME image type.
                
                
                width
                
                    Required. Horizontal dimension of icon in pixels. Integer.
                
                
                height
                
                    Required. Vertical dimension of icon in pixels. Integer.
                
                
                depth
                
                    Required. Number of color bits per pixel. Integer.
                
                
                url
                
                    Required. Pointer to icon image. (XML does not support embedding of binary data. See note below.) Retrieved via HTTP. May be relative to base URL. Specified by UPnP vendor. Single URL.
                
                
            
            
        
        
        service List
        
            Required. Contains the following sub elements:
            service
            
                Required. Repeated once for each service defined by a UPnP forum working committee. If UPnP vendor differentiates device by adding additional, standard UPnP services, repeated once for additional service. Contains the following sub elements: controlURL
                
                    Required. URL for control (cf. section on Control). May be relative to base URL. Specified by UPnP vendor. Single URL.
                
                
                eventSubURL
                
                    Required. URL for eventing (cf. section on Eventing). May be relative to base URL. Specified by UPnP vendor. Single URL.
                
                
                SCPDURL
                
                    Required. URL for service description (nee Service Control Protocol Definition URL). (cf. section on Control.) May be relative to base URL. Specified by UPnP vendor. Single URL.
                
                
                serviceId
                
                    Required. Service identifier. Must be unique within this device description. <format TBD>. Defined by a UPnP Forum working committee. Single URI.
                
                
                serviceType
                
                    Required. UPnP service type.
                     For standard service types defined by a UPnP Forum working committee, must begin with urn:schemas-upnp-org:service: followed by a service type suffix (as shown in the listing above).
                     For non-standard service types specified by UPnP vendors, must begin with urn:, followed by a domain name owned by the vendor, followed by :service:, followed by a service type suffix, i.e., urn:domain-name:service:service-type:service-version.
                    Single URI.
                
                
            
            
        
        
        deviceList
        
            Required if and only if root device has embedded devices. Contains the following sub elements:
            device
            
                Required. Repeat once for each embedded device defined by a UPnP Forum working committee. If UPnP vendor differentiates device by embedding additional UPnP devices, repeat once for each embedded device. Contains sub elements as defined above for root sub element device.
            
            
        
        
    
    


For future extensibility, when processing XML like the listing above, devices and control points may ignore any unknown elements and any subelements or content as specified by the Flexible XML Processing Profile (FXPP).
XML does not support directly embedding binary data, e.g., icons in UPnP descriptions. Binary data may be converted into text (and thereby embedded into XML) using an XML data type of either bin.base64 (a MIME-style base 64 encoding for binary data) or bin.hex (hexadecimal digits represent octets). Alternatively, the data can be passed indirectly, as it were, by embedding a URL in the XML and transferring the data in response to a separate HTTP request; the icon(s) in UPnP descriptions are transferred in this latter manner.
B. UPnP Device Template
The listing of the preceding subsection A illustrates the relationship between a UPnP device description and a UPnP device template. As explained above, the description for a device is written by the vendor, in XML, according to a device template produced by a UPnP forum working committee as a way to standardize devices.
By appropriate specification of placeholders, the listing above can be either a UPnP device template or a UPnP device description. Recall that some placeholders (underlined) would be defined by a UPnP forum working committee, i.e., the UPnP device type identifier, required UPnP services, and required UPnP embedded devices (if any). If these were defined, the listing would be a UPnP device template, codifying the standard for this type of device. UPnP device templates are one of the key deliverables from UPnP forum working committees.
Taking this one step further, the remaining placeholders (bolded) in the listing in subsection A would be specified by the vendor (i.e., vendor-specific information). If these placeholders were specified (as well as the others), the listing would be a device description, suitable to be delivered to a control point to enable control, eventing, and presentation.
Put another way, the UPnP device template defines the overall type of device, and each UPnP device description instantiates that template with vendor-specific information. The first is created by a UPnP forum working committee; the latter, by a UPnP vendor.
C. Device Template Language
The UPnP template language well-formed templates for devices and services. This subsection C provides is a listing and explanation of the language as it pertains to devices. A following section entitled “UPnP template language for Services” explains the UPnP template language as it pertains to services.
The UPnP template language is written in XML syntax and is derived from XML Schema (Part 1: Structures, Part 2: Datatypes). XML Schema provides a set of XML constructions that express language concepts like required vs. optional elements, element nesting, and data types for values (as well as other properties not of interest here). The UPnP template language uses these XML Schema constructions to define elements such as specVersion, URLBase, and deviceType, which are found in the above listing. Because the UPnP template language is constructed using another, precise language, it is unambiguous. Additionally, because the UPnP template language, UPnP device templates, and UPnP device descriptions are all machine-readable, automated tools can automatically check to ensure the latter two have all required elements, are correctly nested, and have values of the correct data types.
Below is the UPnP template language for devices as defined by the UPnP device architecture. The elements it defines are used in UPnP device templates; they are bolded and underlined both below as in the listing above. The listing below is where these elements are defined and the listing above is where they are used. Immediately following this is a brief explanation of the XML Schema elements, attributes, and values used.















<?xml version=“1.0” ?>



<Schema name=“urn:schemas-upnp-org:device:1:0”









xmlns=“urn:schemas-microsoft-com:xml-data”



xmlns:dt=“urn:schemas-microsoft-com:datatypes”>









<ElementType name=“root” content=“eltOnly”>









<element type=“specVersion” />



<element type=“URLBase” minOccurs=“0” />



<element type=“device” />









</ElementType>



<ElementType name=“specVersion”>









<element type=“major” />



<element type=“minor” />









</ElementType>



<ElementType name=“major” dt:type=“int” />



<ElementType name=“minor” dt:type=“int” />



<ElementType name=“URLBase” dt:type=“uri” />



<ElementType name=“device” content=“eltOnly”>









<element type=“UDN” />



<element type=“friendlyName” />



<element type=“deviceType” />



<element type=“presentationURL” minOccurs=“0” />



<element type=“manufacturer” />



<element type=“manufacturerURL” minOccurs=“0” />



<element type=“modelName” />



<element type=“modelNumber” minOccurs=“0” />



<element type=“modelDescription” minOccurs=“0” />



<element type=“modelURL” minOccurs=“0” />



<element type=“UPC” minOccurs=“0” />



<element type=“serialNumber” minOccurs=“0” />



<element type=“iconList” />



<element type=“serviceList” />



<element type=“deviceList” minOccurs=“0” />









</ElementType>



<ElementType name=“UDN” dt:type=“uri” />



<ElementType name=“friendlyName” dt:type=“string” />



<ElementType name=“deviceType” dt:type=“uri” />



<ElementType name=“presentationURL” dt:type=“uri” />



<ElementType name=“manufacturer” dt:type=“string” />



<ElementType name=“manufacturerURL” dt:type=“uri” />



<ElementType name=“modelName” dt:type=“string” />



<ElementType name=“modelNumber” dt:type=“string” />



<ElementType name=“modelDescription” dt:type=“string” />



<ElementType name=“modelURL” dt:type=“uri” />



<ElementType name=“UPC” dt:type=“string” />



<ElementType name=“serialNumber” dt:type=“string” />



<ElementType name=“iconList” content=“eltOnly”>









<element type=“icon” maxOccurs=“*” />









</ElementType>



<ElementType name=“icon” content=“eltOnly”>









<element type=“mimetype” />



<element type=“width” />



<element type=“height” />



<element type=“depth” />



<element type=“url” />









</ElementType>



<ElementType name=“mimetype” dt:type=“string” />



<ElementType name=“width” dt:type=“int” />



<ElementType name=“height” dt:type=“int” />



<ElementType name=“depth” dt:type=“int” />



<ElementType name=“url” dt:type=“uri” />



<ElementType name=“deviceList” content=“eltOnly”>









<element type=“device” maxOccurs=“*” />









</ElementType>



<ElementType name=“serviceList” content=“eltOnly”>









<element type=“service” maxOccurs=“*” />









</ElementType>



<ElementType name=“service” content=“eltOnly”>









<element type=“serviceType” />



<element type=“serviceId” />



<element type=“controlURL” />



<element type=“eventSubURL” />



<element type=“SCPDURL” />









</ElementType>



<ElementType name=“serviceType” dt:type=“uri” />



<ElementType name=“serviceId” dt:type=“uri” />



<ElementType name=“controlURL” dt:type=“uri” />



<ElementType name=“eventSubURL” dt:type=“uri” />



<ElementType name=“SCPDURL” dt:type=“uri” />









</Schema>










ElementType

Defines an element in the new, derived language. name attribute defines element name. dt:type attribute defines the data type for the value of element in the new, derived language.
Element
References an element for the purposes of declaring nesting. minOccurs attribute defines minimum number of times the element must occur; default is minOccurs=1; optional elements have minOccurs=0. maxOccurs attribute defines maximum number of times the element must occur; default is maxOccurs=1; elements that can appear one or more times have maxOccurs=*.
D. Retrieving a Device Description
As explained above, after a control point has discovered a device, it still knows very little about the device. To learn more about the device and its capabilities, the control point must retrieve the UPnP description for the device using the URL provided by the device in the discovery message. This is an HTTP-based process and uses the following subset of the overall UPnP protocol stack.
At the highest layer, description messages contain vendor-specific information, e.g., device type, service type, and required services. Moving down the stack, vendor content is supplemented by information from a UPnP forum working committee, e.g., model name, model number, and specific URLs. Messages from the layers above are hosted in UPnP-specific protocols. In turn, the above messages are delivered via HTTP over TCP over IP.
Using this protocol stack, retrieving the UPnP description for a device is simple: the control point issues an HTTP GET request to the URL in the discovery message, and the device returns its description in the body of an HTTP response. The headers and body for the response and request are explained in detail below.
First, a control point sends a request with method GET in the following format. Values in italics are placeholders for actual values.















GET path to device description HTTP/1.1



HOST: host for device description:port for device description



ACCEPT-LANGUAGE: language preferred by control point










There is no message body for request to retrieve a description.
Listed below are details for the request line and headers appearing in the request. All header values are case sensitive except where noted.
Request Line
GET
Method defined by HTTP.
Path to Device Description


    
    
        Path component of device description URL (LOCATION header in discovery message). Single, relative URL.

HTTP/1.1

    
    


HTTP Version.
Headers
HOST


    
    
        Required. Domain name or IP address and optional port components of device description URL (LOCATION header in discovery message). If the port is empty or not given, port 80 is assumed.

ACCEPT-LANGUAGE

        Recommended. Preferred language(s) for device description. If no description is available in this language, device may return a description in a default language. RFC 1766 language tag(s).
    
    


After a control point sends a request, the device sends a response in the following format, where values in italics are placeholders for actual values.















HTTP/1.1 200 OK



CONTENT-LENGTH: bytes in body



CONTENT-TYPE: text/xml



DATE: when responded



SERVER: OS / version, UPnP / 1.0, product / version










The body of this response is a UPnP device description as explained in detail above.
Listed below are details for the headers appearing in the response. All header values are case sensitive except where noted.
Headers
CONTENT-LENGTH


    
    
        Required. Length of body in bytes. Integer.

CONTENT-TYPE

        Required. Must be text/xml.

DATE

        Recommended. When response was generated. RFC 1123 date.

SERVER

        Required. Concatenation of OS name, slash, OS version, UPnP/1.0, product name, slash, and product version. String.

UPnP Template Language for Services

    
    


After a control point has (1) discovered a device and (2) retrieved a description of the device, the control point has the bare essentials for device control. To learn more about a particular service supported by the device, a control point retrieves a detailed UPnP description for each service.
A UPnP description for a service includes a list of the commands, or actions, the service responds to, and parameters, or arguments, for each action. A service description also includes a list of variables. These variables model the state of the service at run time, and are described in terms of their data type, range, and event characteristics. This section explains the description of actions, arguments, state variables, and properties of those variables.
Like the UPnP description for a device, the UPnP description for a service is written by the vendor. The description is in XML syntax and is based on a standard service template. As with the device template, the service template is produced by a UPnP forum working committee, and they derive the template from the UPnP template language, augmenting it with human language where necessary. As explained above, the UPnP template language is derived from standard constructions in XML. This section explains the format for a UPnP service description, UPnP service templates, typical augmentations in human language, and the part of the UPnP template language that covers services.
To control a device, a control point requests a device's service to perform an action. To do this, a control point sends a suitable control message to the control URL for the service (provided in the device description). In response, the service provides a simple acknowledgement; unlike function calls, no service-specific value is returned. The effects of the action, if any, are modeled by changes in the variables that describe the run-time state of the service. When these state variables change, events are published to all interested control points. This section explains the protocol stack for, and format of, control messages.
To prevent a race condition between events headed for control points and requested actions headed for a service, control messages may include a key. With each new event message a service generates, the service increments the key, and includes that key in the event message. When a control point sends a control message, it may choose to include a key. If a control message includes a key, the service checks to see if the key is current, i.e., if no events have been sent since this key was issued. If the key is current (or if there was no key in the control message), then the service acknowledges the action request. If the key is not current, the service fails the action request. This section briefly explains the event key.
To determine the current value of a state variable, a control point may poll the service. Similar to requesting an action, a control point sends a suitable query message to the control URL for the service. In response, the service provides the value of the variable. This section also explains the format of these query messages.
The remainder of this section first explains how services are described in subsection A, explaining details of actions, arguments, state variables, and properties of those variables. In subsections B and C, UPnP service templates, typical ways to augment service descriptions with human language, and the UPnP template language as it pertains to services are explained. In subsection D, how a control point retrieves a service description is described.
A. Service Description
The UPnP description for a service defines actions and their arguments, and state variables and their data type, range, and event characteristics. Each action may have zero or more arguments. Each argument should correspond to a state variable. This direct-manipulation programming model reinforces simplicity.
To illustrate these points, below is a listing with placeholders (in italics) for actual elements and values. For a standard UPnP service, some of these placeholders would be defined by a UPnP forum working committee (underlined) or specified by a UPnP vendor (bolded). For a vendor-unique service, all of these placeholders would be specified by a UPnP vendor. Elements of the template language defined by the UPnP device architecture are bolded and underlined for later reference. Immediately following the listing is a detailed explanation of the elements, attributes, and values.












<?xml version=“1.0”?>


<scpd xmlns=“urn:schemas-upnp-org:service:1:0”>









 actionList 









 action 









 name action name /name 



 argumentList 









 argument 









 name formal parameter name /name 



 relatedStateVariable state variable







name /relatedStateVariable 









 /argument 









 Declarations for other arguments defined by UPnP



 Forum







working committee (if any) go here









 /argumentList 









 /action 



Declarations for other actions defined by UPnP



Forum







working committee (if any) go here









   







 









 /actionList 



 serviceStateTable 









 stateVariable 









 name variable name /name 



 dataType variable data type /dataType 



 defaultValue   /defaultValue 



 allowedValueRange 









 minimum   /minimum 



 maximum   /maximum 



 step   /step 









 /allowedValueRange 









 /stateVariable 



Declarations for other state variables defined



by UPnP







Forum working committee (if any) go here









 







 









 /serviceStateTable 







</scpd>









Listed below are details for each of the elements, attributes, and values appearing in the listing above. All elements and attributes are case sensitive; values are not case sensitive except where noted. Except where noted, the order of elements is insignificant. Except where noted, required elements occur exactly once (no duplicates), and recommended or optional elements may occur at most once.

    xml
    
        Required for all XML documents. Case sensitive.
    
    
    scpd
    
        Required. Must have urn:schemas-upnp-org:service:1:0 as the value for the xmlns attribute; this references the UPnP Template Language (explained below). Case sensitive. Contains all other elements describing the service, i.e., contains the following sub elements:
        actionList
        
            Required if and only if the service has actions. Contains the following sub elements:
            action
            
                Required for each action defined by a UPnP Forum working committee. If UPnP vendor differentiates service by adding additional actions, required for each additional action. Contains the following sub elements:
                name
                
                    Required. Name of action. String. Should be <32 characters.
                
                
                argumentList
                
                    Required if and only if parameters are defined for action. Repeat once for each parameter. Contains the following sub elements:
                    argument
                     Required. Contains the following sub elements:
                     name
                     Required. Name of formal parameter. Should be name of a state variable that models an effect the action causes.
                     String. Should be <32 characters.
                     relatedStateVariable
                     Required. Must be the name of a state variable.
                
                
            
            
        
        
    
    
    serviceStateTable
    
        Required if and only if the service has state variables. Contains the following sub elements:
        stateVariable
        Required for each state variable defined by a UPnP Forum working committee. If UPnP vendor differentiates service by adding additional state variables, required for each additional variable. sendEvents attribute defines whether event messages will be generated when the value of this state variable changes; non-evented state variables have sendEvents=no; default is sendEvents=yes. Contains the following sub elements:
        name
        
            Required. Name of state variable. Defined by a UPnP Forum working committee for standard state variables; specified by UPnP vendor for extensions. String. Should be <32 characters.
        
        
        dataType
        
            Required. Defined by a UPnP Forum working committee for standard state variables; specified by UPnP vendor for extensions. Must be one of the following values:
            i4
            
                Fixed point, integer number. May have a leading sign. May have leading zeros. (No currency symbol.) (No grouping of digits to the left of the decimal, e.g., no commas.) Must be between −2147483648 and 2147483647, i.e., 4 byte, long integer. (Same as i4 data type defined by XML Schema, Part 2: Datatypes.)
            
            
            r8
            
                Floating point number. Mantissa (left of the decimal) and/or exponent may have a leading sign. Mantissa and/or exponent may have leading zeros. Decimal character in mantissa is a period, i.e., whole digits in mantissa separated from fractional digits by period. Mantissa separated from exponent by E. (No currency symbol.) (No grouping of digits in the mantissa, e.g., no commas.) Must be between −1.79769313486232E308 and −4.94065645841247E-324 for negative values, and between 4.94065645841247E-324 and 1.79769313486232E308 for positive values, i.e., IEEE 64-bit (8-byte) double. (Same as r8 data type defined by XML Schema, Part 2: Datatypes).
            
            
            string
            
                Unicode string. (Same as string data type defined by XML.)
            
            
            dateTime
            
                Date and Time in ISO 8601 format (Same as dateTime data type defined by XML Schema, Part 2: Datatypes.)
            
            
            boolean
            
                0, false, or no for false; 1, true, or yes for true. (Same as boolean data type defined by XML Schema, Part 2: Datatypes.)
            
            
            bin.hex or bin.bin64
            
                Hexadecimal representation of binary data. (Same as bin.base64 and bin.hex data types defined by XML Schema, Part 2: Datatypes.)
            
            
        
        
        defaultValue
        
            Recommended. Expected, initial value. Defined by a UPnP Forum working committee or delegated to UPnP vendor. Must match data type. Must satisfy allowedValueList or allowedValueRange constraints.
        
        
        allowedValueList
        
            Recommended. Enumerates legal string values. Prohibited for data types other than string. At most one of allowedValueRange and allowedValueList may be specified. Sub elements are ordered (e.g., see NEXT_STRING_BOUNDED). Contains the following sub elements:
            allowedValue
            
                Required. A legal value for a string variable. Defined by a UPnP Forum working committee for standard state variables;
                specified by UPnP vendor for extensions. String. Should be <32 characters.
            
            
        
        
        allowedValueRange
        
            Recommended. Defines bounds for legal numeric values; defines resolution for numeric values. Prohibited for data types other than i4 and r8. At most one of allowedValueRange and allowedValueList may be specified. At least one of the following sub elements must be included. Contains the following sub elements:
            minimum
            
                Required. Inclusive lower bound. Defined by a UPnP Forum working committee or delegated to UPnP vendor. Single i4 or r8.
            
            
            maximum
            
                Required. Inclusive upper bound. Defined by a UPnP Forum working committee or delegated to UPnP vendor. Single i4 or r8.
            
            
            step
            
                Recommended. Size of an increment operation, i.e., value of s in the operation v=v+s. Defined by a UPnP Forum working committee or delegated to UPnP vendor. Single i4 or r8.
            
            
        
        
    
    


For future extensibility, when processing XML like the listing above, devices and control points ignore any unknown elements and any sub elements or content as specified by the Flexible XML Processing Profile (FXPP).
Note that it is logically possible for a service to have no actions but have state variables and eventing; such a service would be an autonomous information source. Conversely, it is also logically possible for a service to have no state variables (and no eventing) but have actions; such a service might be stateless and cause short-term environmental effects.
Services standardized by UPnP forum working committees are versioned. Every later version of a service is a superset of the previous version, i.e., it includes all actions and state variables exactly as they are defined by earlier versions of the service. The UPnP service type remains the same across all versions of a service whereas the service version must be larger for later versions.
B. UPnP Service Template
The listing above also illustrates the relationship between a UPnP service description and a UPnP service template. As explained above, the UPnP description for a service is written by a UPnP vendor, in XML, following a UPnP service template. A UPnP service template is produced by a UPnP forum working committee as a way to standardize devices.
By appropriate specification of placeholders, the listing above can be either a UPnP service template or a UPnP service description. Recall that some placeholders would be defined by a UPnP forum working committee (underlined), i.e., actions and their parameters, and states and their data type, range, and event characteristics. If these were specified, the listing above would be a UPnP service template, codifying the standard for this type of service. Along with UPnP device templates, UPnP service templates are one of the key deliverables from UPnP forum working committees.
Taking this one step further, the remaining placeholders in the listing above would be specified by a UPnP vendor (bolded), i.e., additional, vendor-specified actions and state variables. If these placeholders were specified (as well as the others), the listing would be a UPnP service description, suitable for effective control of the service within a device.
Put another way, the UPnP service template defines the overall type of service, and each UPnP service description instantiates that template with vendor-specific additions. The first is created by a UPnP forum working committee; the latter, by a UPnP vendor.
C. Service Template Language
The paragraphs above explain UPnP service descriptions and illustrate how one would be instantiated from a UPnP Service Template. Like UPnP device templates, UPnP service templates are produced by UPnP forum working committees, and these templates are derived from the UPnP template language. This template language defines well-formed templates for devices and services. Below is a listing of this language as it pertains to services. The elements it defines are used in UPnP service templates. The elements are bolded and underlined here and in the listing above. Below is where these elements are defined, whereas above is where they are used.
Immediately following this is a brief explanation of the XML Schema elements, attributes, and values used. The reference to XML Schema at the end of the section has further details.












<?xml version=“1.0”?>


<Schema name=“urn:schemas-upnp-org:service:1:0”









xmlns=“urn:schemas-microsoft-com:xml-data”



xmlns:dt=“urn:schemas-microsoft-com:datatypes”>









<ElementType name=“name” content=“textOnly” dt:type=“string”







/>









<ElementType name=“defaultValue” content=“textOnly”







dt:type=“string” />









<ElementType name=“minimum” content=“textOnly”







dt:type=“number” />









<ElementType name=“maximum” content=“textOnly”







dt:type=“number” />









<ElementType name=“step” content=“textOnly” dt:type=“number”







/>









<ElementType name=“allowedValueRange” content=“eltOnly”







model=“closed”>









<element type=“minimum” />



<element type=“maximum” />



<element type=“step” minOccurs=“0” />









</ElementType>



<ElementType name=“allowedValue” content=“textOnly” />



<ElementType name=“allowedValueList” content=“eltOnly”







model=“closed”>









<element type=“allowedValue” minOccurs=“1” maxOccurs=“*”







/>









</ElementType>



<ElementType name=“dataType” content=“textOnly”







dt:type=“string” />









<ElementType name=“stateVariable” content=“eltOnly”







model=“closed”>









<element type=“name” />



<element type=“dataType” />



<element type=“defaultValue” minOccurs=“0” maxOccurs=“1”







/>









<group minOccurs=“0” maxOccurs=“1” order=“one”>









<element type=“allowedValueList” />



<element type=“allowedValueRange” />









</group>



<AttributeType name=“sendEvents” />



<attribute default=“yes” type=“sendEvents” required=“no”







/>









</ElementType>



<ElementType name=“serviceStateTable” content=“eltOnly”







model=“closed”>









<element type=“stateVariable” minOccurs=“1” maxOccurs=“*”







/>









</ElementType>



<ElementType name=“relatedStateVariable” content=“textOnly”







dt:type=“string” />









<ElementType name=“argument” content=“eltOnly”







model=“closed”>









<element type=“name” />



<element type=“relatedStateVariable” />









</ElementType>



<ElementType name=“argumentList” content=“eltOnly”







model=“closed”>









<element type=“argument” minOccurs=“1” maxOccurs=“*” />









</ElementType>



<ElementType name=“action” content=“eltOnly” model=“closed”>









<element type=“name” />



<element type=“argumentList” minOccurs=“0” maxOccurs=“*”







/>









</ElementType>



<ElementType name=“actionList” content=“eltOnly”







model=“closed”>









<element type=“action” minOccurs=“0” maxOccurs=“*” />









</ElementType>



<ElementType name=“scpd” content=“eltOnly” model=“closed”>









<element type=“serviceStateTable” />



<element type=“actionList” />









</ElementType>







</Schema>









    attribute
    
        References an attribute in the new, derived language for the purposes of declaring in which elements it may appear. Like any XML element, the AttributeType element may have attributes of its own. Using the required attribute within this element indicates whether the attribute must be present; optional attributes have required=no.
    
    
    AttributeType
    
        Defines an attribute in the new, derived language. Like any XML element, the AttributeType element may have attributes of its own. Using the name attribute within this element defines the name of the attribute as it will be used in the derived language.
    
    
    element
    
        References an element for the purposes of declaring nesting. minOccurs attribute defines minimum number of times the element must occur; default is minOccurs=1; optional elements have minOccurs=0. maxOccurs attribute defines maximum number of times the element must occur; default is maxOccurs=1; elements that can appear one or more times have maxOccurs=*.
    
    
    ElementType
    
        Defines an element in the new, derived language. name attribute defines element name. dt:type attribute defines the data type for the value of element in the new, derived language. model attribute indicates whether elements in the new, derived language can contain elements not explicitly specified here; when only previously specific elements may be used, model=closed. content attribute indicates what content may contain; elements that contain only other elements have content=eltOnly; elements that contain only strings have content=textOnly.
        group
        
            Organizes content into a group to specify a sequence. minOccurs attribute defines minimum number of times the group must occur. maxOccurs attribute defines maximum number of times the group must occur. order attribute constrains the sequence of elements; when at most one element is allowed, order=one.
        
        
    
    


D. Augmenting the UPnP Template Language
As is the case with describing devices, some properties of services are difficult to capture in the XML Schema formalism. For services in particular, it is useful to describe the effect actions have on state variables. This procedural information is awkward to describe in a declarative language like XML, so below is a recommended vocabulary for UPnP forum working committees to use when defining service actions or for UPnP vendors to use when they wish to document the effects of extra actions.

    Assign (v, a)
    
        Variable v becomes the value of argument a, i.e., v=a. v and a must be the same data type. <why both this and SET?>
    
    
    DECREMENT (v)
    
        Equivalent to INCREMENT (v) with allowedValueRange step treated as—step.
    
    
    DECREMENT_BOUNDED (v)
    
        Equivalent to INCREMENT_BOUNDED (v) with allowedValueRange step treated as—step.
    
    
    DECREMENT_WRAP (v)
    
        Equivalent to INCREMENT_WRAP (v) with allowedValueRange step treated as—step.
    
    
    INCREMENT (v)
    
        Variable v becomes the value of v plus allowedValueRange step, i.e., v=v+step. Equivalent to DECREMENT (v) with allowedValueRange step treated as—step. v must be either i4 or r8 and must have an allowedValueRange definition.
    
    
    INCREMENT_BOUNDED (v)
    
        Variable v becomes the value of v plus allowedValueRange step, i.e., v=v+step.
        If step is greater than 0 and if v plus step would be greater than allowedValueRange maximum, then v becomes maximum.
        If step is less than 0 and if v plus step would be less than allowedValueRange minimum, then v becomes minimum.
        Equivalent to DECREMENT_BOUNDED (v) with allowedValueRange step treated as—step. v must be either i4 or r8 and must have an allowedValueRange definition.
    
    
    INCREMENT_WRAP (v, c)
    
        Variable v becomes the value of v plus allowedValueRange step, i.e., v=v+step.
        If step is greater than 0, and if v plus step would be greater than allowedValueRange maximum, then v becomes minimum plus step minus 1, i.e., v=minimum+step−1; if step is 1, this simplifies to v=minimum.
        If step is less than 0 and if v plus step would be less than allowedValueRange minimum, then v becomes maximum plus step plus 1, i.e., v=maximum+step+1; if step is −1, this simplifies to v=maximum.
        Equivalent to DECREMENT_WRAP (v) with allowedValueRange step treated as—step. v must be either i4 or r8 and must have an allowedValueRange definition.
    
    
    NEXT_STRING_BOUNDED (v)
    
        Variable v becomes the next allowedValue after the current value of v. If v was already the last allowedValue, then v does not change. v must be a string data type and must have an allowedValueList definition.
    
    
    NEXT_STRING_WRAP (v)
    
        Variable v becomes the next allowedValue after the current value of v. If v was already the last allowedValue, then v becomes the first allowedValue. v must be a string data type and must have an allowedValueList definition.
        PREV_STRING_BOUNDED (v)
        Variable v becomes the previous allowedValue before the current value of v.
    
    


If v was already the first allowedValue, then v does not change. v must be a string data type and must have an allowedValueList definition.

    PREV_STRING_WRAP (v)
    
        Variable v becomes the previous allowedValue before the current value of v.
        If v was already the first allowedValue, then v becomes the last allowedValue. v must be a string data type and must have an allowedValueList definition.
    
    
    SET (v, c)
    
        Variable v becomes the value of constant c, i.e., v=c. v and c must be the same data type.
    
    
    TOGGLE (v)
    
        Variable v becomes the boolean negation of the value of v, i.e., v=NOT v. v must be boolean.
    
    


E. Retrieving a Service Description
As explained above, after a control point has discovered a device and has retrieved a device description, it may need to learn more about the services provided by the device. Nearly identical to the process for retrieving a device description, a control point may retrieve a service description using a description URL in the description (vs. discovery) message.
CONCLUSION
Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.

## Claims

1. A system comprising:
means for creating a device template using a template language written in XML syntax;
means for defining, from the device template, a device description for a self-describing network device; and
means for automatically evaluating, via a computer software tool, whether the device description is well formed.

2. A system as recited in claim 1, wherein the template language is derived from XML schema.

3. A system as recited in claim 1, wherein the self-describing network device comprises a universal plug and play device.

4. A system as recited in claim 1, further comprising means for storing the device description on a computer-readable medium.

5. A system as recited in claim 1, further comprising:
means for creating a service template from a template language written in XML syntax; and
means for defining, from the service template, a service description for a service supported by the self-describing network device.

6. A system comprising:
means for creating a service template from a template language written in XML syntax;
means for defining, from the service template, a service description for a service supported by a self-describing network device; and
automatically evaluating, via a computer software tool, whether the service description is well formed.

7. A system as recited in claim 6, wherein the template language is derived from XML schema.

8. A system as recited in claim 6, wherein the self-describing network device comprises a universal plug and play device.

9. A system as recited in claim 6, further comprising means for storing the service description on a computer-readable medium.

10. A system, comprising:
means for storing a description of a 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, wherein the set of elements includes at least one of:
a first element to identify one or more versions of a template language used to define the description;
a second element to identify the self-describing network device; and
a third element to specify a base universal resource locator (URL); and

means for making the description available to the computing device.

11. A system as recited in claim 10, wherein the storing means comprises computer-readable media located at the self-describing network device.

12. A system as recited in claim 10, wherein the self-describing network device comprises a universal plug and play device.

13. A system 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 system as recited in claim 10, further comprising means for storing a set of elements to describe at least one service supported by the self-describing network device.

15. A system as recited in claim 14, 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.

16. A system as recited in claim 15, 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.

17. A system as recited in claim 15, 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.

18. A system as recited in claim 10, wherein the storing means comprises computer-readable media located at the self-describing network device, and further comprising means for storing a set of elements to describe at least one service supported by the self-describing network device at a location remote from the self-describing network device.

19. A system comprising:
storage means for storing a first set of elements to describe a self-describing network device and a second set of elements to describe a service supported by the self-describing network device, the first and second set of elements being written in an XML syntax;
processing means for returning 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.

20. A system as recited in claim 19, wherein the storage means comprises a first computer-readable media located at the self-describing network device to store the first set of elements and a second computer-readable media located remotely from the self-describing network device, but accessible via a network, to store the second set of elements.

21. A system as recited in claim 19, wherein the first set of elements includes 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).

22. A system as recited in claim 19, 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 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.

23. A system as recited in claim 19, 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.

24. A system as recited in claim 23, 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.

25. A system as recited in claim 23, 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.

26. A system as recited in claim 19, wherein the processing means responds to an HTTP GET request by returning the first set of elements and at least the reference to the second set of elements in a body of an HTTP response.

27. A computer-readable medium comprising computer-executable instructions that, when executed, perform acts comprising:
create a device template using a template language written in XML syntax;
define, from the device template, a device description for a self-describing network device; and
automatically evaluate, via a computer software tool, whether the device description is well formed.

28. A computer-readable medium as recited in claim 27, wherein the template language is derived from XML schema.

29. A computer-readable medium as recited in claim 27, wherein the self-describing network device comprises a universal plug and play device.

30. A computer-readable medium as recited in claim 27, further comprising computer-executable instructions that, when executed, cause the device description to be stored on a computer-readable medium.

31. A computer-readable medium as recited in claim 27, further comprising computer-executable instructions that, when executed, perform acts comprising:
create a service template from a template language written in XML syntax; and
define, from the service template, a service description for a service supported by the self-describing network device.

32. A computer-readable medium comprising computer-executable instructions that, when executed, perform acts comprising:
create a service template from a template language written in XML syntax;
define, from the service template, a service description for a service supported by a self-describing network device; and
automatically evaluate, via a computer software tool, whether the service description is well formed.

33. A computer-readable medium as recited in claim 32, wherein the template language is derived from XML schema.

34. A computer-readable medium as recited in claim 32, wherein the self-describing network device comprises a universal plug and play device.

35. A computer-readable medium as recited in claim 32, further comprising computer-executable instructions that, when executed, cause the service description to be stored on a computer-readable medium.

36. Computer-readable media comprising computer-executable instructions that, when executed, perform acts comprising:
store a first set of elements to describe a self-describing network device and a second set of elements to describe a service supported by the self-describing network device, the first and second set of elements being written in an XML syntax;
responsive to a request for a description of the self-describing network device, return the first set of elements and at least a reference to the second set of elements.

37. Computer-readable media as recited in claim 36, wherein the first set of elements are stored at the self-describing network device and the second set of elements are stored remotely from the self-describing network device.

38. Computer-readable media as recited in claim 36, wherein the first set of elements includes 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).

39. Computer-readable media as recited in claim 38, 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 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.

40. Computer-readable media as recited in claim 36, 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.

41. Computer-readable media as recited in claim 40, 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.

42. Computer-readable media as recited in claim 40, 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.

43. Computer-readable media as recited in claim 36, wherein the request is an HTTP GET request, and the first set of elements and at least the reference to the second set of elements are returned in a body of an HTTP response.