1、lay Extensions foA WINDOWS RALLY SPECIFICATIONPnPX: Plug and Play Extensions forWindowsAugust 30, 2010AbstractThis specification describes the Plug and Play Extensions (PnPX) for the WindowsVista and Microsoft Windows Server Code Name “Longhorn” operating systems. It provides requirements and guidel
2、ines for hardware manufacturers to create devices that are installable with PnPX. PnPX is a key component of the Microsoft Windows Rally set of technologies. The current version of this paper is maintained on the Web at: Disclaimer: This document is provided “as-is”. Information and views expressed
3、in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, refer
4、ence purposes. 2010 Microsoft Corporation. All rights reserved.ContentsIntroduction to PnPX 3PnPX Services 3Default Startup Type for PnPX Services 4WindowsVista 4Windows Server 4Network Explorer Device Discovery and PnP-X 4Windows Vista 4Windows Server 4WSD Device Installation Process 4Using PnPX 5C
5、reating a PnPX Device 5Creating a WSD-Compliant Device 6WSD Device Metadata Requirements 6Sample INF File for WSD Devices 8Sample Metadata Message for WSD Devices 10Creating a SSDP-Compliant Device 11SSDP Device Metadata Requirements 12Sample SSDP Discovery Response Message 14Sample INF File for SSD
6、P Devices 14Sample Device Description File for SSDP Devices 16Querying Device Metadata 17PnPX Reference 18PnPX Category Definitions 18pnpx-ssdp Schema Reference 20pnpx-ssdp Schema Elements 20X_compatibleId (X_PnpXType) Element 20X_deviceCategory (X_PnpXType) Element 20X_hardwareId (X_PnpXType) Eleme
7、nt 21X_PnpX Element 21pnpx-ssdp Schema Complex Types 21X_PnpXType Complex Type 22pnpx-wsd Schema Reference 22pnpx-wsd Schema Elements 23CompatibleId Element 23DeviceCategory Element 23HardwareId Element 24pnpx-wsd Schema Simple Types 24CompatibleIdType Simple Type 24DeviceCategoryType Simple Type 24
8、HardwareIdType Simple Type 25References 25Introduction to PnPX This guide provides information about the Plug and Play Extensions (PnPX) component of the Microsoft Windows Rally set of technologies. This document provides guidelines for creating devices that are installable with PnPX for WindowsVist
9、a. PnPX is an extension of Plug and Play (PnP) in WindowsVista that integrates network-connected devices into the Windows PnP subsystem. PnPX allows network-connected devices to appear as devices inside Windows and provides an installation experience that is similar to attaching a physically connect
10、ed device.Just as PnP in Windows operates over a specific set of buses, PnPX in WindowsVista has been defined to operate over network protocols for virtually connected devices. This includes: Universal Plug and Play (UPnP)capable devices Device Profile for Web Services (DPWS)capable devices (see For
11、 more information about Windows Rally technologies and other resources discussed here, see PnPX discovers devices attached to a virtual PnPX network bus. The IP bus enumerator is used to discover PnPX devices. This enumerator discovers DPWS-capable devices and UPnP devices connected to a LAN. Device
12、 discovery takes place when Network Explorer is launched. The user must explicitly choose to install the device. The Found New Hardware Wizard appears if user intervention is required to install a device driver.Devices appear in Device Manager after discovery and installation. The devices can then b
13、e enumerated for use by other Windows applications by calling the Function Discovery API to query the PnP subsystem. Each device is associated with a function instance. These function instances can be queried by using the IFunctionDiscovery:CreateInstanceQuery and the IFunctionDiscovery:CreateInstan
14、ceCollectionQuery methods.See also on the MSDN Web site: Function DiscoveryPnPX ServicesPnPX uses two services to enable device discovery: PnP installation and device presence management. These services are the following: IP Bus Enumerator. The IP Bus Enumerator (IPBusEnum) is a Windows service that
15、 handles the installation of PnPX devices. IPBusEnum monitors a list of devices currently present on the system. When a device is installed, IPBusEnum sends a request to the PnP component to create the device devnode. When a device is removed, IPBusEnum receives a notification message from the PnP c
16、omponent and then sends a request to remove the device from the list of present devices.PnPX devices can be installed only when the IPBusEnum service is running. Function Discovery Provider Host. The Function Discovery Provider Host (FDPHost) service hosts the discovery providers for PnPX. This incl
17、udes the built-in discovery providers for the Simple Services Discovery Protocol (SSDP) and Web Services on Devices (WSD) WSDiscovery protocol.Default Startup Type for PnPX ServicesThe default start type for the PnPX services differs for the Windows client and server operating systems.WindowsVistaTh
18、e IPBusEnum and FDPHost services are set to Manual start on the WindowsVista client operating systems. These services will start and stop automatically as the operating system needs them.Windows ServerThe IPBusEnum service is set to Disabled on the Microsoft Windows Server operating systems. Server
19、administrators wanting to enable PnPX on Windows Server must start the IPBusEnum service. This can be done through the Services control panel application or on the command line via the following:C:net start IPBusEnumThe FDPHost service is set to Manual start on the Windows Server operating systems.
20、This service starts and stops automatically as the operating system needs it.Network Explorer Device Discovery and PnP-XNetwork Explorer displays the list of discovered devices to the user. Which devices are discovered by default differs based on whether the operating system is Windows Vista or Wind
21、ows Server.Windows VistaIn Windows Vista, both WSD- and UPnP-based PnP-X devices are discovered and displayed in Network Explorer.Windows ServerIn Windows Server, only WSD-based PnP-X devices are discovered and displayed in Network Explorer. The UPnP discovery service (SSDPSrv) does not run by defau
22、lt in Windows Server. Server administrators wanting to enable discovery of UPnP-based PnP-X devices must start the SSDPSrv service. This can be done through the Control Panel Services application or on the command line via the following:C:net start SSDPSrvWSD Device Installation ProcessThe following
23、 procedure describes the WSD device installation process:1. The user launches the Network Explorer. 2. The Network Explorer queries the WSD Provider (and other providers) for a list of devices and displays the devices to the user. 3. The user chooses to install the device. 4. The IPBusEnum service i
24、s notified of the new device installation request and queries the WSD Provider for device metadata. 5. The WSD Provider queries the device for metadata. 6. The device sends a metadata message to the WSD Provider in response. 7. The WSD Provider parses the metadata message and returns the results to
25、IPBusEnum. 8. Based on the metadata, IPBusEnum creates a physical device object (PDO) for the device and passes the PDO to the PnP component. 9. PnP searches for the INF file associated with the device. 10. Based on the data in the INF file, PnP attempts to select a compatible device driver. 11. If
26、a compatible device driver is available on the system, the driver is loaded and the device is installed. Otherwise, the Found New Hardware Wizard appears and the user must locate and install the driver manually. See also in this document: Creating a WSD-Compliant DeviceUsing PnPXIndependent hardware
27、 vendors (IHVs) can create devices that are compatible with the PnPX architecture. Application developers can query PnPX device metadata by using the Function Discovery API. For more information, see “Querying Device Metadata” later in this sectionCreating a PnPX DeviceA PnPX device is a device that
28、 can be discovered by one of the following Function Discovery providers: The WSD Provider The SSDP Provider A custom provider developed to discover the PnPX deviceIn most cases, the built-in WSD and SSDP providers can be used for device discovery, which simplifies development. If the device communic
29、ates by using a custom protocol, then a custom provider is required. For more information about writing a custom provider, see “Function Discovery Providers” at MSDN ().The Web Services protocol offers two advantages. First, the WSD provider can discover devices on multiple subnets. Second, the WS d
30、evice description document has more elements for a more detailed device description. Creating a WSD-Compliant DeviceDevice manufacturers must implement the following, in addition to base device functionality: Device Profile for Web Services (DPWS) support. To view the DPWS specification, see pnpx-ws
31、d schema support. Specifically, the device must read metadata from a SOAP message containing pnpx-wsd schema elements and create a set of hardware IDs and compatible IDs from the XML. The device must send SOAP messages containing device metadata. The required elements are described in “WSD Device Metadata Requirements” in this document. This file includes both WSD and pnpx-wsd schema elements. The device must implement all WSD messages as described in the DPWS specification. These messages are required for d
copyright@ 2008-2022 冰豆网网站版权所有
经营许可证编号:鄂ICP备2022015515号-1