Table of contents
TOC
Collapse the table of content
Expand the table of content

WMCDC OBEX Control Model (Multiple PDOs)

Last Updated: 2/15/2017

There are two ways to enumerate Object Exchange Protocol (OBEX) Control Model interface collections: the USB generic parent driver can group all of the OBEX interfaces together and create a single physical device object (PDO) for all of the OBEX interfaces, or the parent driver can create a separate PDO for each OBEX interface. For a description of the hardware IDs that the USB generic parent driver generates for OBEX interfaces that are grouped together, see WMCDC OBEX Control Model (Single PDO).

When the USB generic parent driver assigns separate PDOs to each OBEX interface, the PDOs have the following properties.

PropertyDescription

Reference

Universal Serial Bus CDC Subclass Specification for Wireless Mobile Communication Devices, version 1.0, Section 6.5.

Class of the master interface

Communication Interface Class (0x02).

Subclass of the master interface

OBEX (0x0B).

Protocol

None (0x00).

Enumerated

Yes.

Related interfaces

One data class interface that the union functional descriptor (UFD) references.

Hardware IDs

USB\Vid_%04x&Pid_%04x&Rev_%04x&Cdc_0B&MI_%02x
USB\Vid_%04x&Pid_%04x&Rev_%04x&Cdc_0B
USB\Vid_%04x&Pid_%04x&Cdc_0B&MI_%02x
USB\Vid_%04x&Pid_%04x&Cdc_0B

Compatible IDs

USB\Class_02&SubClass_0B&Prot_00
USB\Class_02&SubClass_0B
USB\Class_02

Special handling

The registry settings that are associated with the instance of the USB generic parent driver that manages the composite device determine whether OBEX interfaces are managed with a single PDO or multiple PDOs. For an explanation of the registry settings that specify how the USB generic parent driver enumerates OBEX interfaces, see Enumerating Interface Collections on Wireless Mobile Communication Devices.

Send comments about this topic to Microsoft

© 2017 Microsoft