CDMA-One and CDMA-2000


Handset Drivers




MCCI® CDMA handset drivers provide compatibility, performance, flexibility, and stability to the designer of CDMA-One and CDMA-2000 terminal equipment.

CDMA driver block diagram

The technology supports single function and multi-function handsets. The drivers can be licensed in single-function or multi-function form, allowing OEMs to trade off cost against performance across their product line.

Compatibility is assured by MCCI's five years experience in supplying this technology for USB modems, serial port adapters, and communication devices. MCCI's leading role in the USB standards community has allowed us to make drivers that implement not only the letter but the spirit of the USB standards underlying advanced communication. The MCCI base handset driver allows for a single install across all Windows PC operating systems, reducing support costs. MCCI drivers have been extensively tested with a wide range of legacy applications, for example Procomm and WinFax Pro, and they provide better performance and higher stability than the corresponding operating-system drivers.

MCCI drivers are an integral part of many well known and highly successful USB products. With deployment in the millions of units, MCCI drivers have demonstrable field proven reliability. All MCCI drivers are built on a proven core foundation of software technology representing 20 labor-years of engineering development effort. In addition, MCCI drivers have undergone thousands of hours of rigorous testing culminating in the acquisition of strategically desirable USB-IF and WHQL certifications for our customers products. As a result, the MCCI CDMA drivers provide a high level of reliability and stability.

At the same time, the MCCI drivers provide very high performance: up to 5 megabits per second throughput for Internet traffic. These data rates are more than adequate for 1xRTT and 1xEV/DO services.

MCCI drivers support any CDC-compliant USB devices. Evaluation drivers are available off-the-shelf for testing with popular CDMA chipsets.

Multifunction support allows data-communication functions to be combined with Mass Storage, synchronization, diagnostic and other functions. Competing approaches require either reconfiguring the handset, or else using an extra serial cable for the synchronization functions. MCCI multi-function drivers allow elimination of the extra cables, or handset configuration steps; instead, all of the capabilities of the handset can be presented to the Windows system concurrently. For example, the user can be on-line, and at the same time update the MP-3 files stored on the handset.

As shown in the block diagrams, the drivers consist of a central driver, which provides device-level management services, and additionally enumerates the subfunctions of the phone, allowing use of the MCCI standard CDC 1.1-compatible Abstract Control Model modem drivers for data communication emulation.

In addition, to support multi-function handsets, the central driver can optionally detect and load drivers for other functions of the phone. Microsoft's Mass Storage class driver and Audio class drivers can be used concurrently with data transfers. In addition, to support vendor-specific diagnostics and synchronization access, MCCI provides serial-emulation drivers. These drivers allow existing diagnostic and synchronization applications to access the CDMA handset just as if an additional COM port were connected between the handset and the PC.

Figure 1 shows the block diagram of the single-function version of the drivers on Windows 2000, XP, and Vista. Figure 2 shows the multi-function configuration on Windows 2000, XP, and Vista.

Figure 1. Single Function Drivers, Windows 2000, XP, and Vista


Notes to Figure 1:
  1. The CDMA Handset driver is loaded by Windows based on a vendor ID/product ID match. On Windows 2000-family operating systems, the driver arranges for Windows to load the WDM driver as a modem-class device. No user intervention is required to select the appropriate drivers for the Windows version; the drivers are self-configuring.
  2. The Enhanced CDMA Data Driver is loaded as a modem class device. No additional wrapper is needed to emulate a high-performance modem.
Figure 2. Multifunction Example on Windows 2000, XP, and Vista


Notes to Figure 2:
  1. The multifunction CDMA Handset driver is loaded by Windows based on a vendor ID/product ID match. The driver then parses the descriptors of the device, and (in this example) detects three functions: the Abstract Control Model data transfer function, the diagnostic driver function, and the mass storage function.
    The driver arranges for Windows to load the WDM CDMA Data driver as a Modem class device; and Diagnostic Data WDM drivers as a Port class device. No user intervention is required to select the appropriate drivers for the Windows version; the drivers are self-configuring.
  2. The same drivers used in the single function case are used to handle data transfer in the multifunction case. This simplifies maintenance.
  3. The MCCI diagnostic driver is loaded (as a Ports-class) device to operate the diagnostic interface. The API is completely compatible with the normal COM port API, so existing programs can be immediately reused. If the OEM prefers, the diagnostic driver can be loaded outside of Ports class; in this case, application programs may have to be rewritten, but there is much more flexibility for operating the port.
  4. The standard Microsoft Mass-Storage class driver is used on Windows 2000, XP, and Vista.
  5. Additional functions may be added to the phone, (for example HID class or Audio class) up to the limit of the hardware resources of the phone's USB interface hardware. The driver detects them automatically, by parsing the descriptors.
Specifications:

Table 1. MCCI CDMA-2000 Handset Driver
Operating systems Windows 2000, XP, and Vista
Device Classes Supported for enumeration CDC, Audio, plus all single-interface classes
API No specific API at this level
Number of simultaneous handsets supported Limited only by system resources.
Device Requirements CDC 1.1; device class must be 0x02 (Communication). In multifunction mode, any Audio Class and Mass Storage Class interfaces must be compatible with the limitations of the underlying operating system.
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.


Table 2. MCCI Enhanced CDC Data Class and VCOMM Port Drivers
Operating systems Windows 2000 (WDM only), Windows XP (WDM only), Windows Vista
Installation Plug and Play (INF based)
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 Abstract Control Model. Device must support AT commands over data class pipe. COMM class notifications must correctly indicate the associated DATA class interface. A CDC UNION descriptor must be supplied and must be correct.
Throughput Up to 5 megabits per second, limited by device
Language support and localization Provided by customer
Technical Documentation
  • Functional Specification, including descriptor requirements and INF-based options.
  • Install/Uninstall document
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 Diagnostic and VCOMM Port Drivers
Operating systems Windows 2000, XP, and Vista
Installation Plug and Play (INF based)
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.) All existing serial-port diagnostic applications should work unchanged with the virtual COM port created by this driver.
Device Requirements Vendor specific. The diagnostic interface must provide one BULK-IN and one BULK-OUT endpoint. INF files must be modified to match the interface explicitly.
Language support and localization Provided by customer
Technical Documentation
  • Functional Specification, including descriptor requirements and INF-based options.
  • Install/Uninstall document


Table 4. General Information
Basic Delivery Format Binary plus INF files, as drivers in checked and free format; via download from the MCCI secure web site.
Warranty 90 days
Source Licenses Available at extra fee.
Pass-through rights Available at extra fee.
Automatic Install/Uninstall Framework 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.


Back to top