WMC10_Research.docVIP

WMC Research Extract By Huiyang Cao From “Universal Serial Bus CDC Subclass Specification for Wireless Mobile Communication Devices” Overview This specification represents multi-function communication handset devices as composite devices. Each potential facility is modeled, if possible, using a pre-existing device class. This allows reuse of existing class drivers. Additional Communication Device subclasses are defined for new application areas specific to wireless handsets. The remainder of this specification is organized into the following outline. ? Assumptions and Constraints ? Functional Overview ? New class code values ? Functional Characteristics for each subclass, including: 1. Functional Topology 2. Descriptors 3. Management Elements 4. Notifications ? Device Requests ? Device Descriptors Assumptions and Constraints In this figure, the handset (or Mobile Equipment, “ME”) consists of an MT and one or more TAs. The Mobile Terminal (MT) has only a facility to access the air interface. It can be thought of as the radio transmitter and receiver. Each Terminal Adapter (TA) is provided with one call facility or management capability. When multiple applications need to be operated at the same time (i.e., Multi-call), the ME must have sufficiently many TAs to support all the applications or calls concurrently. The testable requirements focus on the content of the descriptors. 1. The Device descriptor shall have bDeviceClass set to Communication Class, and bDeviceSubclass and bDeviceProtocol set to zero. 2. Each Communication Class interface must be followed by the appropriate functional descriptors for that interface. These shall include the HEADER functional descriptor. 3. If a Communication Class interface has associated Data Class interface, a Union Functional descriptor must appear, specifying the Communication Class interface as the primary interface, and the Data Class interface(s) as subordinate interfaces. 4. No Data Class i