• Home
• Company
• Support
• News
• Contact
• Legal

The MCCI® MCPC GL-004/005 drivers profit from MCCI's many years of experience developing USB technology for PCs, and they provide compatibility and flexibility to the designer of USB-based WCDMA terminal equipment.


As shown in the block diagram, the MCCI driver set consists of a central driver, which provides device-level management services for the handset. In addition, the handset driver identifies the Terminal Adapters (TAs) and other functions present in the phone. The handset driver identifies the appropriate link and mode to be used based on the phone's USB descriptors. It also identifies non-MCPC functions, such as Mass Storage class, and arranges for the appropriate function drivers to be loaded by Windows. In the above example, the handset provides four functions, three of which are supported by MCCI drivers, and one by Microsoft-supplied drivers.

The Handset Driver is an advanced WDM bus driver, which performs two functions:

1. It identifies the individual functions available on the phone, and provides enumeration and multiplexing services for the individual function drivers.
2. It simplifies installation on multiple Windows systems, by generating operating-system-specific device IDs.

MCCI further provides function drivers that support AT-command-based device management, data/fax modem emulation, OBEX synchronization, and special purpose diagnostic management.

Notes to block diagram:

1. The Device Management driver provides a separate API to the handset via a simulated serial port.
2. One copy of the data/fax driver is loaded for each Mobile Abstract Control logical terminal adapter that is to be used for data services. In addition to supporting high-speed data transfer via dial-up networking, MCCI drivers support legacy switched-circuit data communication applications such as WinFax and Procomm Plus.
3. The OBEX driver provides a separate API to the synchronization interface of the handset. At the OEM's option, this interface may be accessed either as a simulated serial port or as a special OBEX device class.
4. In this example, the handset exports a USB Mass-Storage Class interface, for access to MP-3 files stored on the handset. The MCCI Handset Driver automatically arranges to load the Microsoft Mass Storage class driver on Windows 2000, XP, and Vista.
5. Additional standard USB class drivers (for example, HID, audio class, vendor-specific functions) will be handled automatically, by parsing the descriptors. Mobile Direct Line control devices will be correctly enumerated but must be handled via a separate driver (not included in the base kit).

Specifications:

TABLE 1: MCCI GL-004/005 WCDMA Handset Driver

Operating systems	Windows 2000, XP, and Vista (supports remote wakeup)
Installation	Plug and Play (INF based)
Device Classes Supported for enumeration	CDC, MCPC GL-004/005, Audio, plus all single-interface classes
API	No specific API. Functionality can be tailored at runtime using SetupDI and the registry.
Number of simultaneous cell phones supported	Limited only by system resources.
Device Requirements	MCPC GL-004/005; Audio class; CDC 1.1; any Audio Class interfaces must be compatible with the limitations of the underlying operating system. Other single interface functions will also be enumerated correctly.
Number of Data Class Interfaces Supported	Up to 14 (due to limited number of endpoints in real USB silicon)
Language support and localization	Provided by customer
Technical Documentation	Functional Specification, including descriptor requirements and INF-based options. SetupDI interfacing document, for writing programs to manage the handset driver directly.

TABLE 2: MCCI Enhanced GL-004/005 WCDMA Data/Fax Port Drivers

Operating systems	Windows 2000, XP, and Vista
Installation	Plug and Play (INF based) or optional installer
Number of ports supported	Up to 128 (limited by Windows)
API	Standard UNIMODEM COM-port based interface. SET_LINK and ACTIVATE_MODE are handled automatically at OPEN/CLOSE time, in accordance with MCPC recommendations.
Device Requirements	Mobile Abstract Control Model. 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 interface.
Language support and localization	Provided by customer
Technical Documentation	Functional Specification, including descriptor requirements and INF-based options.
INF File Customization for AT Command Set	Provided by customer. MCCI provides an INF file based on a standard modem model

TABLE 3: MCCI Enhanced GL-004/005 WCDMA Device Management and OBEX Port Drivers

Operating systems	Windows 2000, XP, and Vista
Installation	Plug and Play (INF based), or optional MCCI installer
Number of ports supported	Up to 128 (limited by Windows)
API	Standard COMM port, including support for most 16-bit Windows apps and real-mode DOS apps via a port-mapping VxD. (Timing differences may uncover bugs in the applications.)
Device Requirements	Mobile Abstract Control Model. AT Command Device and OBEX devices must match MCPC recommendations.
Language support and localization	Provided by customer
Technical Documentation	Functional Specification, including descriptor requirements and INF-based options.
INF File Customization	Normally not required

TABLE 4: MCCI InstallRight™ Plus Device Install/Uninstall Support

Operating systems	Windows 2000, XP, and Vista
Installation	Three modes: install before plug; plug before install; install while plug
Uninstallation	Via Add/Remove Programs, or an icon.
Integration With Larger Installs	MCCI InstallRight can be launched as a captive .exe by a larger application install/uninstall application
Language support and localization	Provided by OEM

TABLE 5: General Information

Basic Delivery Format	Binary plus INF files, as drivers in checked and free format; via download from the MCCI secure web site.
Source Licenses	Available at extra fee.
Pass-through rights	Available at extra fee.
Branding	Drivers will bear the MCCI copyright, but will be rebranded using MCCI's standard rebranding technology for customer, for one device. Additional rebranding available at extra fee.
End-user Documentation	Customer's responsibility
Support	MCCI supports its direct customers via telephone and email. Resellers or manufacturers of products incorporating MCCI technology are responsible for supporting their own customers.