Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

UPnP device-hosting services and UPnP control points are included. In a UPnP-based network, a target device can assume one or more of the following roles:

  • It can function as a dedicated, controlled UPnP device that is connected to the network in a home- or business-network scenario.

  • It can function as a control point that discovers and controls the available UPnP devices on the network.

  • It can function as a UPnP bridge that acts as a proxy for non-UPnP devices.

If a device is connected to more than one network, UPnP can be disabled on selected networks by altering various registry settings. For more information, see UPnP Registry Settings.

The UPnP implementation uses the following functionality:

  • TCP/IP

  • HTTPD Web Server

  • XML and MSXML

  • Simple Service Discovery Protocol (SSDP)

  • General Event Notification Architecture (GENA)

  • SOAP

Note:
For information about differences between the UPnP implementation available for Windows Mobile devices and the UPnP implementation available for Windows Embedded CE devices, see UPnP in Windows Mobile Devices.

APIs

The following APIs are available for the creation of UPnP-based applications.

  • UPnP Control Point API. A COM-based UPnP control point API for applications.

  • UPnP Device Host API. A COM-based UPnP device host API for service providers and devices.

  • UPnP AV Framework. A C++ framework for creating devices that implement the UPnP Audio/Video (AV) DCP.

See Also