winfax_winfax设置_xp系统升级win7系统

winfaxwinfax

The CDC Wireless Mobile Communication (WMC) 1.1 specification, maintained by USB-IF, allows cell phones to use USB to offer communication functions with other multi-media capabilities to PCs and PDAs. MCCI has off-the-shelf Windows eval drivers available for ACM and WMC DM products. Drivers for Mac OS are also available.

The MCCI® WMC drivers extend MCCI field-proven USB drivers for communication devices to allow GPRS, EDGE, DECT, -2000, UMTS, W, and other 2.5G and 3G terminal equipment to take full advantage of these new capabilities.

As shown in the block diagram, the WMC driver suite starts with a central driver, which provides device-level management services, and additionally enumerates the subfunctions of the phone. This central driver is able to enumerate any device complying with the WMC specification, including:

Data/Fax communication functions

Mobile Direct Line Model (MDLM) functions

Ethernet Control Model (LAN-frame based) functions

Mass Storage Class functions

Audio Class functions

Human Intece Device (HID) functions

Vendor Specific functions

Device Firmware Update (DFU) functions

See for further information.

MCCI further supplies high-performance drivers for data/fax, device management, object exchange, LAN frame exchange, and other purposes. These drivers all operate concurrently, and can be used simultaneously with operating-system supplied function drivers for mass storage, audio, HID and other functions.

Although the WMC specification was developed by leaders in the telecommunications industry, it is not limited to use with cell phones. Any USB application that combines a communication function (fax, modem, network) with another USB function (mass storage, audio, etc.) can take advantage of this specification.

MCCI completes the solution by providing the additional function drivers that are needed.

Notes to block diagram:

The Device Management function driver provides a separate API to the device; this API is normally used for status monitoring and display. The WMC specification specifies the use of AT commands over this intece, but the MCCI driver can transport any kind of data over this intece. MCCI drivers allow the designer to choose to use a simulated COMM. port, or to use a DeviceIoControl() intece, which hides the simulated COMM port from the user. See .

If a simulated COM port is used, then an additional emulated serial port will be used to provide legacy services.

The WMC Modem Driver provides high-performance data/fax services, matching the speed of 3G services. With a throughput of up to 3Mbps, this driver allows handset makers to deliver the full bandwidth of their hardware to the Windows host system, including Windows Mobile and Windows CE. Components in this group will be loaded for each Mobile Abstract Control logical terminal adapter that supports data services. See .

The WMC OBEX Driver provides a straightforward intece to the OBEX functions of the USB device. OBEX is typically used for phonebook synchronization and to save and restore the settings of the device on the PC. Again, the designer can choose to operate the OBEX port either as a simulated COMM port or use a DeviceIoControl() intece to hide the port from the user. See .

Mass Storage inteces are handled automatically, using Operating-System supplied drivers on Windows XP, Vista, Windows 7, and Windows 8.

Voice services will be handled using an Audio Intece, one intece per logical TA, as guided by the descriptors in the device. Call control for this audio intece will be handled by a separate mechanism (not shown in this diagram). These audio inteces will be associated with the other inteces in the logical TA according to the information in the descriptors.

Additional standard USB class drivers (for example, HID, audio class for the handset, vendor specific drivers for test and maintenance) are enumerated automatically by the WMC Handset Driver, which parses the device descriptors to determine which functions are present.

Specifications:

Table 1. MCCI WMC Bus Driver

CDC 1.x, including any of the mobile control models. Audio class; any Audio Class inteces must be compatible with the limitations of the underlying operating system. Other single intece functions will also be enumerated correctly.

Functional Specification, including descriptor requirements and INF-based options.

API document, for writing programs that use the management intece directly.

Table 2. MCCI Enhanced WMC FAX/Modem Port Drivers

Abstract Control Model, as given in CDC 1.1 and clarified by the WMC 1.1 specification. Device must support AT commands over data class pipe, as well as supporting encapsulated commands. COMM class notifications must correctly indicate the associated DATA class intece.

Most non-USB aware data and fax communication applications can be supported directly, including Procomm 4.6, Winfax, Dial-Up Networking, Hyperterm, and many others.

MCCI provides an INF file based on a standard V.25ter/V.251 modem model. MCCI can develop the INF file to match customer requirements, or can incorporate customer INF files into the customer-specific build.

Table 3. MCCI WMC OBEX Drivers

Table 4. MCCI WMC Device Management Port Drivers

WMC Device Management Model, as given in the WMC 1.1 specification. Device must provide a separate interrupt endpoint for RESPONSE_AILABLE notifications.

Table 5. MCCI Driver Preinstall/Uninstall Utility

Table 6. General Information

MCCI also offers a complete firmware implementation based on the MCCI USB DataPump® suitable for integrating into handset firmware. When our drivers and firmware are combined with the appropriate MCCI Catena® development cards, our customers have been able to develop end-to-end solutions well in advance of handset silicon availability, and to ship production implementations within weeks after receiving first silicon.

本文来自电脑杂谈，转载请注明本文网址：
http://www.pc-fly.com/a/shumachanpin/article-23590-1.html