USB Driver Developers Guide Rev 5

AirCard/AirPrime USB Driver Developers Guide
2130634 Rev 5
Preface
Important Notice
Due to the nature of wireless communications, transmission and reception of data can never be guaranteed. Data may be delayed, corrupted (i.e., have errors) or be totally lost. Although significant delays or losses of data are rare when wireless devices such as the Sierra Wireless modem are used in a normal manner with a well-constructed network, the Sierra Wireless modem should not be used in situations where failure to transmit or receive data could result in damage of any kind to the user or any other party, including but not limited to personal injury, death, or loss of property. Sierra Wireless accepts no responsibility for damages of any kind resulting from delays or errors in data transmitted or received using the Sierra Wireless modem, or for failure of the Sierra Wireless modem to transmit or receive such data. Do not operate the Sierra Wireless modem in areas where blasting is in progress, where explosive atmospheres may be present, near medical equipment, near life support equipment, or any equipment which may be susceptible to any form of radio interference. In such areas, the Sierra Wireless modem MUST BE POWERED OFF. The Sierra Wireless modem can transmit signals that could interfere with this equipment. Do not operate the Sierra Wireless modem in any aircraft, whether the aircraft is on the ground or in flight. In aircraft, the Sierra Wireless modem MUST BE POWERED OFF. When operating, the Sierra Wireless modem can transmit signals that could interfere with various onboard systems.
Note: Some airlines may permit the use of cellular phones while the aircraft is on the ground and the door is open. Sierra Wireless modems may be used at this time.
Safety and Hazards
The driver or operator of any vehicle should not operate the Sierra Wireless modem while in control of a vehicle. Doing so will detract from the driver or operator's control and operation of that vehicle. In some states and provinces, operating such communications devices while in control of a vehicle is an offence.
Limitation of Liability
The information in this manual is subject to change without notice and does not represent a commitment on the part of Sierra Wireless. SIERRA WIRELESS AND ITS AFFILIATES SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL, GENERAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY THIRD PARTY. Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its affiliates aggregate liability arising under or in connection with the Sierra Wireless product, regardless of the number of events, occurrences, or claims giving rise to liability, be in excess of the price paid by the purchaser for the Sierra Wireless product.
Rev 5 Nov.11
Proprietary and Confidential
AirCard / AirPrime USB Driver Developers Guide
Patents
This product may contain technology developed by or for Sierra Wireless Inc. This product includes technology licensed from QUALCOMM 4G. This product is manufactured or sold by Sierra Wireless Inc. or its affiliates under one or more patents licensed from InterDigital Group.
Copyright Trademarks
2011 Sierra Wireless. All rights reserved. AirCard is a registered trademark of Sierra Wireless. Sierra Wireless, AirPrime, AirLink, AirVantage, Watcher, and the Sierra Wireless logo are trademarks of Sierra Wireless. Windows and Windows Vista are registered trademarks of Microsoft Corporation. Macintosh and Mac OS X are registered trademarks of Apple Inc., registered in the U.S. and other countries. QUALCOMM is a registered trademark of QUALCOMM Incorporated. Used under license. Other trademarks are the property of their respective owners.
Contact Information
Sales Desk:
Phone: Hours: E-mail:
1-604-232-1488 8:00 AM to 5:00 PM Pacific Time [email protected]
Post:
Sierra Wireless 13811 Wireless Way Richmond, BC Canada V6V 3A4 1-604-231-1109 www.sierrawireless.com
Fax: Web:
Consult our website for up-to-date product descriptions, documentation, application notes, firmware upgrades, troubleshooting tips, and press releases: www.sierrawireless.com
Revision History
Revision number 1.3 1.4 Release date Jun 2007 Sep 2007 Changes - Added MC8785 / AC885E / AC885U - Updated idProduct values - Added vendor commands: Get TRU-Install Information, Set TRU-Install Mode
2130634
Preface
Revision number 1.5
Release date Feb 2008
Changes - Removed old products, added C885 - Updated USB descriptors for MC8785V / AC885E / C885 - Updated USB architecture for MC8785V / AC885E / C885 - Updated descriptions on non-MUX and MUX mode for MC8785V / AC885E / C885 - Added MC5727 - Removed AC597U - Changed document title (removed Embedded Module, added Compass - Added MC8790, AC8790V, C597, C888 - Reorganized and updated Table 1-1, Supported devices (by QUALCOMM chipset), on page 15 - Updated Mux, Non-Mux, and Hybrid-Mux sections in Chapter 2 to reflect details of new devices, including NMEA and Mass Storage - Added Mass Storage section - Split and updated USB descriptor information into multiple tables in Appendix A - Added MC8791V and MC8792V - Added AC402, MC5727V, and MC5728V - Added QUALCOMM DM Data Logging on page 103 - Added an Index on page 113 - Added List of Tables. - Added a summary table (previously was text) to the beginning of USB descriptors chapter. - Changed formatting (width/alignment) of tables - Added USB 306 / C889 - Added Direct IP content - Removed MC8785V - Added AC501, USB 307 - Updated Table 2-12, UMTS devices Direct IPNon-MUX endpoints, on page 49 and Table 2-12, UMTS devices Direct IPNon-MUX endpoints, on page 49 - Updated MC8700/USB306 USB descriptors - Updated Direct IP description (interfaces used) - Added MC8795V, MC8700, AC 310U - Removed MC5725/25V, MC8785V - Combined USB Architecture chapter and USB Descriptors appendix - Added SL5010 and SL5011. - Removed MC8775, MC8775V, MC8780, and MC8781. - Edits to the Patents section. - Added a List of Figures. - Added MDM6270/QSC6270 (SL808X) - Removed MDM6280, MSM6800, MSM6800A, MSM7200/7200A/7201/720A - Added QMI content
1.6 1.8
Apr 2008 Sep 2008
1.9 1.10
Sep 2008 Feb 2009
1.11 1.12
May 2009 Jul 2009
2.0
May 2010
May 2011
4 5
June 2011 November 2011
Rev 5 Nov.11
2130634
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Document organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 USB architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 USB standards compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 USB endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Supported driver architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Default operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Activating / Deactivating MUX mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 AirCard/AirPrime USB architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 CDMA module-specific USB architectures. . . . . . . . . . . . . . . . . . . . . . . . . . 22 CDMA devicesNon-MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 CDMA devicesMUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 CDMA devicesHybrid-MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 UMTS module-specific USB architectures . . . . . . . . . . . . . . . . . . . . . . . . . . 32 UMTS devices (legacy VID/PID)Non-MUX . . . . . . . . . . . . . . . . . . . . .33 UMTS devices (legacy VID/PID)MUX . . . . . . . . . . . . . . . . . . . . . . . . . 44 UMTS devices (DIP VID/PID)Non-MUX . . . . . . . . . . . . . . . . . . . . . . . 47 UMTS devices (QMI VID/PID)Non-MUX . . . . . . . . . . . . . . . . . . . . . . . 59 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 USB protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Rev 5 Nov.11
Data services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 AT/PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 HIP (Host Interface Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 CnS (Control and Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DM (QUALCOMM Diagnostic Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . 68 NMEA (National Marine Electronics Association) . . . . . . . . . . . . . . . . . . 69 Data 1, Data 2, Data 3 (Additional PPP) . . . . . . . . . . . . . . . . . . . . . . . . . 70 Mass Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Direct IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 QMI (NET interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Vendor-specific commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Command availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Set Device Power State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Set Mode Non-MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Set Mode MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Get Mode MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Get NDIS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Get NDIS Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Get Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Set Mode NMEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Get Mode NMEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Set Host Power State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Get TRU-Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Set TRU-Install Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Get Config Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Set Config Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Set Device Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Set Host Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Supported CDC USB commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 QUALCOMM DM Data Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Handling DM for logging purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2130634
Contents
Pass-thru application considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Direct IP mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Performance considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Direct IP drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Direct IP interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Direct IP communication / session setup . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Switching between PPP and Direct IP modes . . . . . . . . . . . . . . . . . . . . . . 107 Configuring USB interface composition in Direct IP mode . . . . . . . . . . . . . 107 QMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 QMI drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 QMI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 QMI communication / session setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Switching between QMI and Direct IP modes . . . . . . . . . . . . . . . . . . . . . . 109 Configuring USB interface composition in QMI mode . . . . . . . . . . . . . . . . 110 User-developed USB Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 User-developed drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Handshaking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Host USB driver requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Rev 5 Nov.11
10
2130634
List of Tables
Supported devices (by QUALCOMM chipset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 MUX mode activation/deactivation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Supported architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 CDMA devicesNon-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 CDMA devices (non-MUX)USB descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 CDMA devicesMUX endpoints/DLCI assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 CDMA devicesHybrid-MUX endpoints/DLCI assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 UMTS devices (legacy VID/PID)Non-MUX endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 UMTS devices (legacy VID/PID)USB descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 MSM6290 (C888/C889) (TRU-Install mode)USB descriptors . . . . . . . . . . . . . . . . . . . . . . . . 42 UMTS devices (legacy VID/PID)MUX endpoints/DLCI assignments . . . . . . . . . . . . . . . . . . . 44 ExampleInterface-dependent endpoint assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 UMTS devices Direct IPNon-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 UMTS devices (DIP VID/PID)Device/Configuration Descriptors . . . . . . . . . . . . . . . . . . . . . . 52 UMTS devices (DIP VID/PID)HIP descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . . . 53 UMTS devices (DIP VID/PID)DM descriptors (Interface/Endpoint). . . . . . . . . . . . . . . . . . . . . 53 UMTS devices (DIP VID/PID)AT descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . . . . 54 UMTS devices (DIP VID/PID)MDM1 descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . 55 UMTS Mass Storage-capable devices (DIP VID/PID)MS descriptors (Interface/Endpoint) . . 55 UMTS devices (DIP VID/PID)DIP1 descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . . 56 UMTS devices (DIP VID/PID)DIP2 descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . . 57 UMTS devices (DIP VID/PID)DIP3 descriptors (Interface/Endpoint) . . . . . . . . . . . . . . . . . . . 58 UMTS devices (QMI VID/PID)Non-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 UMTS devices (QMI VID/PID)USB descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 AT/PPP data channel endpoints (by chipset and mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 HIP data channel endpoints (by chipset and mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 DM data channel endpoints (by chipset and mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 NMEA data channel endpoints (by chipset and mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Data 1/Data 2/Data 3 data channel endpoints (by chipset and mode). . . . . . . . . . . . . . . . . . . . . 70 Mass Storage data channel endpoints (by chipset and mode) . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Direct IP data channel endpoints (by chipset) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 QMI data channel endpoints (by chipset). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Command availability by chipset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Set Device Power StateSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Set Mode Non-MUXSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Rev 5 Nov.11
11
Set Mode MUXSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Set Mode MUXData stage (OUT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Get Mode MUXSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Get Mode MUXData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Get NDIS SupportSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Get NDIS SupportData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Get NDIS PreferenceSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Get NDIS PreferenceData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Get AttributesSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Get AttributesData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Set Mode NMEASetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Get Mode NMEASetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Get Mode NMEAData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Set Host Power StateSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Get TRU-Install InformationSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Get TRU-Install InformationData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Set TRU-Install ModeSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Get Config ItemSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Get Config ItemData stage (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Configuration information details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Set Config ItemSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Set Config ItemData stage (OUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Configuration information details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Set Device ResetSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Set Host InfoSetup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Set Host InfoData stage (OUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuration informationFeature Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Configuration informationHost Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Configuration informationService pack version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuration informationHost and system up time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Supported commands/requests by chipset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Supported class-specific notifications by chipset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
12
2130634
List of Figures
Figure 2-1: CDMA devicesNon-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 2-2: CDMA devicesMUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 2-3: CDMA devicesHybrid-MUX endpoints/DLCI assignments . . . . . . . . . . . . . . . . . . 31 Figure 2-4: UMTS devices (legacy VID/PID)Non-MUX endpoints . . . . . . . . . . . . . . . . . . . . . 35 Figure 2-5: UMTS devices (legacy VID/PID)MUX endpoints/DLCI assignments . . . . . . . . . . 46 Figure 2-6: UMTS devices Direct IPNon-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Figure 2-7: UMTS devices (QMI VID/PID)Non-MUX endpoints . . . . . . . . . . . . . . . . . . . . . . . 60 Figure C-1: Recommended setup for logging QUALCOMM DM data . . . . . . . . . . . . . . . . . . . 103 Figure C-2: Handling of DM messages by your USB driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Figure D-1: Direct IPReceive Link Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Figure D-2: Direct IPHost/modem synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Rev 5 Nov.11
13
14
2130634
1: Introduction
The Sierra Wireless AirCard mobile broadband devices and AirPrime intelligent embedded modules listed in Table 1-1 include USB interfaces for communication with host devices. Each devices USB interface is based on the identified QUALCOMM chipset. Table 1-1: Supported devices (by QUALCOMM chipset) a
Chipset MDM6085 MDM6200 Network CDMA GSM Devices Device type PID Network standards
Data-only equivalent of QSC6085. See QSC6085 row (next page) for details. SL8090 SL8091 SL8092 SL8093 SL SL SL SL 0x683C (Legacy) 0x683D (Legacy) 0x683E (Legacy) 0x68A3 (Direct IP)b GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA
MDM6270 MDM8200
GSM GSM
Data-only equivalent of QSC6270. See QSC6270 row (next page) for details. AC503 AirCard USB 308c AirCard USB 309a AirCard 310Ua MC8700 USB 306 USB 307 2-in-1 PC/E U U U MC U U U U MC MC U U MC U U MC MC 0x68A2 (QMI) 0x68A3 (Direct IP) 0x68AA (Direct IP)b GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA/HSPA+/LTE 0x68A3 (Direct IP) GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA/HSPA+ 0x68A3 (Direct IP) GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA/HSPA+ 0x68A3 (Direct IP) GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA/HSPA+
MDM8200A
GSM
AC318U AC326U MC8704 MC8705
MDM8220
GSM
AC312U AC319U MC8801
MDM9200
GSM
AC313U AC320U MC7700 MC7710
Rev 5 Nov.11
15
Table 1-1: Supported devices (by QUALCOMM chipset) a (Continued)

Chipset MDM9600 Network GSM/CDMA Devices MC7750 Device type MC PID 0x68A2 (QMI) Network standards CDMA 1X/HDR/ eHRPD/LTE (HSPA capability to be available in a future firmware revision) MSM6290 GSM AC501 AC504 C888 C889 U 2-in-1 PC/E U U 0x6890 (Legacy) 0x68A3 (Direct IP) 0x68AA (Direct IP)b 0x6890 (Legacy) 0x0FFF (TRU-Install) 0x68A3 (Direct IP) 0x68AA (Direct IP)b MC8790 MC8790V MC8791V MC8792V MC8795V USB301 USB302 QSC6085 MDM6085 (Data-only) CDMA AC250U AC402 AC598U MC5728V SL5010 SL5011 QSC6270 MDM6270 (Data-only) GSM SL8080 SL8081d SL8082 SL8083d SL8084 SL8085d MC MC MC MC MC U U U 2-in-1 PC/E U MC SL SL SL SL SL SL SL SL 0x6890 (Legacy) 0x68A3 (Direct IP) 0x68AA (Direct IP)b 0x0301 0x0027 0x0025 0x0028 0x0300 0x0300 0x683C (Legacy) 0x683D (Legacy) 0x683E (Legacy) 0x68A3 (Direct IP) 0x68AA (Direct IP)b GSM/GPRS/EDGE/ WCDMA/HSDPA IS-95A/CDMA 1X 1xEV-DO Rev-0/ Rev-A 0x683C (Legacy) 0x68A3 (Direct IP) 0x68AA (Direct IP)b GSM/GPRS/EDGE/ WCDMA/HSDPA/ HSUPA
a. EExpressCard; MCMini Card; PCPC Card; UUSB; 2n1 PC/E2-in-1 PC Card/ExpressCard; SLSL module b. Direct IP PID 0x68A3 is the standard Direct IP PID. 0x68AA is carrier-specific. c. AirCard USB 308, AirCard USB 309, and AirCard 310U may be referred to as USB308, USB309, and USB310 in this document.
16
2130634
Introduction
d. SL8081, SL8083, and SL8085 may use either MDM6270 or QSC6270 chipsets.
Purpose of this guide

Note: Sierra Wireless provides drivers and a connection manager appli cation (Watcher ) for Windows XP and Windows Vista .
This guide is intended for use when designing non-Windows drivers for these devices. It describes the following information: Services (protocols) available over the USB connection (AT/PPP, HIP, CnS, DM, NMEA, Mass storage, Direct IP, QMI) The physical USB interface (device and endpoint descriptors) Supported driver architectures (non-MUX mode, MUX mode, hybrid-MUX mode) Commands used over the USB interface to control the modules state
Document organization
This guide includes the following sections:
Introduction (this section)
USB architecture on page 19 Describes the physical interface, supported driver architectures, and device endpoint descriptor information. Services on page 65 Describes available data transfer services (protocols). Vendor-specific commands on page 73 Describes commands that can be used to control the modules state. Supported CDC USB commands on page 101 Describes support for CDC USB commands, requests, and notifications. QUALCOMM DM Data Logging on page 103 Contains information for OEMs who need to implement DM logging. Direct IP mode on page 105 Describes Direct IP interface, performance, communications setup, and configuation. QMI on page 109 Describes the NET interface used to support QMI. User-developed USB Drivers on page 111 Provides information for developers who are creating their own drivers for Sierra Wireless MC- and SL-series embedded modules.
Rev 5 Nov.11
17
Related documents
Related and supporting documents and products include: Table 1-2: Related documentation
Document title AirCard / AirPrime UMTS Devices Supported AT Command Reference (Document 2130617) AT Command Set for User Equipment (UE) (Release 6) CDMA 1xEV-DO CnS Reference (Document 2130754) AT Command Reference (Document 2130620) Related content Standard and proprietary AT commands supported by Sierra Wireless UMTS devices For descriptions of standard AT commands, see AT Command Set for User Equipment (UE) (Release 6). Standard AT commands CnS (Control and Status) messages for use with Sierra Wireless CDMA devices Standard AT commands supported by Sierra Wireless CDMA AirCards and MiniCards. See also AT Command Set for User Equipment (UE) (Release 6) (above). Standard AT commands supported by Sierra Wireless SL501x devices. See also AT Command Set for User Equipment (UE) (Release 6) (above). Proprietary AT commands for Sierra Wireless CDMA devices For UMTS-specific commands, see AirPrime MC/SL-series (UMTS/LTE) Extended AT Command Reference (Document 2130616). CnS (Control and Status) messages for use with Sierra Wireless UMTS devices. Proprietary AT commands for Sierra Wireless UMTS MC- and SLseries devices. For CDMA-specific commands, see the Extended AT Command Reference (Document 2130621). 3GPP technical specification describing the 27.010 multiplexer protocol The document (3GPP TS 27.010) can be downloaded from www.3gpp.org. This specification can be downloaded from www.usb.org.
CDMA SL501x AT Command Reference (Document 4110801)
Extended AT Command Reference (Document 2130621)
AirPrime UMTS MC and SL Series CnS Reference (Document 2130602) AirPrime MC / SL-series (UMTS / LTE) Extended AT Command Reference (Document 2130616) Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release 6) Universal Serial Bus Class Definitions for Communication Devices, Version 1.1 Universal Serial Bus Specification, Rev 2.0
This specification can be downloaded from www.usb.org.
18
2130634
2: USB architecture
This chapter describes supported driver architectures for data transfer, the physical USB interfaces for each architecture by chipsets, and the USB descriptor information for those chipsets.
Note: UMTS devices use Sierra Wireless Direct IP VID/PID (common to all devices supporting Direct IP), and some of these devices can switch between Direct IP and either a legacy VID/PID (unique to each device) or a QMI VID/PID (common to all devices supporting QMI).
USB standards compliance

The devices listed in Table 1-1 on page 15 comply with the following USB standards: USB 2.0 (backwards compatible with USB 1.1) USB slave only Standard USB flow control Standard USB power managementSuspends the USB bus (when idle) to conserve power. Data transfer rates: Low-speed (1.5 Mb/s) Full-speed (12 Mb/s) UMTS devices: High-speed (480 Mb/s)
The architecture for these devices is described in the Universal Serial Bus Class Definitions for Communication Devices, Version 1.1 (CDC) specification, available from www.usb.org. To support advanced power management, a modified (noncomposite) endpoint/interface model combines the Communication and Data Interface pipes with two proprietary pipes (HIP and NMEA/ Data1) into one vendor-specific interface.
Note: These devices do not claim any CDC classes in the descriptors and do not support functional descriptors. As a result, these devices are not normally compatible with native CDC-ACM drivers.
USB endpoints
USB endpoints are uniquely addressable portions of a USB device used to transfer information between the host and module. Each defined endpoint is a unidirectional link from the modem to the host (IN) or from the host to the modem (OUT).
Rev 5 Nov.11
19
In this document: Each endpoint is referred to by a logical endpoint number and direction for ease of reading (for example, 2-IN or 3-OUT). Actual (physical) endpoint information is detailed in chipset-specific USB descriptor tables. Where bidirectional communication is required for a specific data service, two BULK endpoints are used. Some data services also use an INTERRUPT endpoint for data flow control.
Note: When developing your drivers, you must use the actual physical endpoints.
Supported driver architectures

AirCard and AirPrime modules support one or more driver architectures, depending on their chipset and, for some modules, the VID/PID (Vendor ID/ Product ID) being used: Non-multiplexing (non-MUX) modeEach supported service channel (see Services on page 65) is enabled over its own set of endpoints. Multiplexing (MUX) modeBased on the 3GPP 27.010 multiplexer protocol, MUX mode defines a framework for supporting several simultaneous sessions over a single asynchronous serial interface (all service channels are carried over a single set of endpoints). If supported, Mass Storage is implemented over a second set of endpoints. Hybrid-MUX modeThis is a proprietary architecture (supported by CDMA modules) intended to reduce overhead on data packets and to improve performance. The following service channels are implemented over unique endpoint sets: Data/AT Mass Storage All other services (MUXed)
Note: Driver Implementation for MUX and hybrid-MUX protocols requires a detailed understanding of the 27.010 requirements. See Terminal Equipment to User Equipment (TEUE) multiplexer protocol (Release 6) for the full protocol specification.
Default operating mode

UMTS AirCard and AirPrime modules always start in non-MUX mode. CDMA AirCard and AirPrime modules start in hybrid-MUX mode (if supported by the host systems drivers) or non-MUX mode.
20
2130634
USB architecture
Activating / Deactivating MUX mode

After a USB connection has been established between the host and the module, activate and deactivate MUX mode using the methods shown in Table 2-1. Table 2-1: MUX mode activation /deactivation methods
Chipseta MDM6085 QSC6085 Activate MUX mode Deactivate MUX mode
Vendor-specific USB commandsb AT!CMUX command Vendor-specific USB commandsb AT!CMUX command AT+CMUX command
Vendor-specific USB commandsa Use the Close Down Service Request over the 27.010 Control channel (see Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release 6), section 5.1.7 for details).
MDM6200 MDM6270 MSM6290 c QSC6270 c
a. For a list of devices using these chipsets, see Table 1-1 on page 15. b. See Vendor-specific commands on page 73 for applicable commands. c. Device must be using a legacy VID/PID. MUX mode is not supported when using Direct IP VID/PID.
AirCard/AirPrime USB architectures

Table 2-2: Supported architectures
hybrid MUX PID nonMUX Chipseta Legacy Direct IP QMI MUX
Notes
CDMA MDM6085 QSC6085 UMTS / LTE MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MDM9600 MSM6290 QSC6270 b b b b b b bc bc c bc N/A non-MUX: Composite architecture N/A Each service type enabled over its own interface N/A (Direct IP only) Endpoint assignments depend on which services are enabled N/A N/A N/A N/A N/A N/A non-MUX: Proprietary, non-composite architecture
N/A
N/A
Each service type enabled over specific endpoints
a. For a list of devices using these chipsets, see Table 1-1 on page 15. b. Device uses different PIDs for composite MUX (0x683C), composite non-MUX (0x683D), and non-composite MUX (0x683E). c. MUX mode available only if device uses legacy VID/PID.
Rev 5 Nov.11
21
CDMA module-specific USB architectures

Sierra Wireless CDMA AirCard and AirPrime modules (detailed in Table 1-1 on page 15) implement the following chipset-specific USB architectures: CDMA devicesNon-MUX (See page 23.) CDMA devicesMUX (See page 28.) CDMA devicesHybrid-MUX (See page 30.)
22
2130634
USB architecture
CDMA devicesNon-MUX
This section describes non-MUX mode for CDMA devices.
Device features Details
Chipsets
MDM6085 QSC6085 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-3, CDMA devicesNon-MUX endpoints, on page 23 Figure 2-1, CDMA devicesNon-MUX endpoints, on page 24 Table 2-4, CDMA devices (non-MUX)USB descriptors, on page 25
Architecture
Descriptors
CDMA devicesNon-MUX architecture

Table 2-3: CDMA devicesNon-MUX endpoints
Interface Endpoint 0 (Control) Supported service Management element Purpose: 0-OUT is used to emulate control line signals.
0 1 IN (Interrupt)
For details, see SetControlLineState in Universal Serial Bus Class Definitions for Communication Devices, Version 1.1.
Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
2 IN / OUT (Bulk) 4 IN / OUT (Bulk)
For details, see SerialState in the Universal Serial Bus Class Definitions for Communication Devices, Version 1.1.
Primary data channel (AT/PPP) HIP (carrying CnS) If required, OEMs can consult with Sierra Wireless to discuss how to change the default data service.
Supported service types (device-dependent): DM, HIP (carrying CnS), and HIP (carrying CnS and DM).
NMEA DM
Note: You can customize port mappings for these devices in non-MUX mode using the AT!SERIALPORTMAP command. For details, see Extended AT Command Reference (Document 2130621).
Rev 5 Nov.11
23
Host Device
The host-side driver accepts and interprets incoming and outgoing data for each supported service (AT, HIP, DM, NMEA). Each service uses a different set of USB endpoints. AT Management element
MDM6085 / QSC6085
USB interface 0 Control
Notification element
Interface 0 1 IN
Interrupt Note: Used for out-of-band signaling.
Interface 0 2 IN 2 OUT
AT AT and PPP
HIP (carrying CnS)
HIP (carrying CnS)
NMEA
NMEA
DM
DM
endpoints
Figure 2-1: CDMA devicesNon-MUX endpoints
24
2130634
USB architecture
CDMA devicesNon-MUX descriptors

Table 2-4: CDMA devices (non-MUX) USB descriptors
Descriptor Device Descriptor Field identifier bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct Value 0x12 0x01 0x0110 USB spec 01.10 0x00 IFCs supply own 0x00 0x00 0x40 0x1199 Sierra Wireless Inc. (Default values) 0x0025 AC598U 0x0027 AC402 0x0028 MC5728V 0x0300 SL5010/SL5011 0x0301 AC250U bcdDevice 0x0001 Release 00.01 iManufacturer 0x01 iProduct 0x02 iSerialNumber 0x00 bNumConfigurations 0x01 1 configuration bLength 0x09 bDescriptorType 0x02 wTotalLength 0x0043 67 bytes bNumInterfaces 0x01 1 interface bConfigurationValue 0x01 iConfiguration 0x00 bmAttributes 0xE0 Self poweredremote wakeup MaxPower 0x00 0 mA bLength 0x09 bDescriptorType 0x04 bInterfaceNumber 0x00 bAlternateSetting 0x00 bNumEndpoints 0x09 bInterfaceClass 0xFF Vendor-specific device class bInterfaceSubClass 0xFF Vendor-specific device subclass bInterfaceProtocol 0xFF Vendor-specific iInterface 0x03 bLength 0x07 bDescriptorType 0x05 bEndpointAddress 0x81 ep #1, IN bmAttributes 0x03 Transfer Type: Interrupt wMaxPacketSize 0x0010 bInterval 0x80 128 ms
Configuration Descriptor (Index 0x00)
Interface Descriptor (Number 0x00 Alternate Setting 0x00)
Endpoint Descriptor (0x81)
Rev 5 Nov.11
25
Table 2-4: CDMA devices (non-MUX) USB descriptors (Continued)

Descriptor Endpoint Descriptor (0x82) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x82 0x02 0x0040 0x00 0x07 0x05 0x02 0x02 0x0040 0x00 0x07 0x05 0x84 0x02 0x0040 0x00 0x07 0x05 0x04 0x02 0x0040 0x00 0x07 0x05 0x85 0x02 0x40 0x00 0x07 0x05 0x05 0x02 0x40 0x00 0x07 0x05 0x88 0x02 0x40 0x00
ep #2, IN Transfer Type: Bulk 0 ms
ep #2, OUT Transfer Type: Bulk 0 ms
26
2130634
USB architecture
Table 2-4: CDMA devices (non-MUX) USB descriptors (Continued)

Descriptor Endpoint Descriptor (0x08) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bString bLength bDescriptorType bString bLength bDescriptorType bString bLength bDescriptorType wLANGID[0] bLength bDescriptorType bString Value 0x07 0x05 0x08 ep #8, OUT 0x02 Transfer Type: Bulk 0x40 0x00 0 ms 60 03 (Default value) Sierra Wireless, Incorporated 62 0x03 Sierra Wireless Device 30 0x03 Data Interface 4 0x03 0x0409 EnglishUnited States 0x08 0x03 (Six consecutive bytes) 0x0031 MUX supported 0x0030 Hybrid not supported 0x0031 NMEA supported
Manufacturer String Descriptor
Product String Descriptor Interface String Descriptor String Descriptor 0 (Language Descriptor) Port Configuration String Descriptor (0xF0)
Rev 5 Nov.11
27
CDMA devicesMUX
This section describes MUX mode for CDMA devices.
Chipsets
MDM6085 QSC6085 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-5, CDMA devicesMUX endpoints/DLCI assignments, on page 28 Figure 2-2, CDMA devicesMUX endpoints, on page 29
Architecture
CDMA devicesMUX architecture

Table 2-5: CDMA devicesMUX endpoints / DLCI assignments
Interface Endpoints 0 (Control) Supported service Management element Purpose: 0-OUT is used to emulate control line signals.
0 1 IN (Interrupt)
2 IN / OUT (Bulk)
For details, see SerialState in Universal Serial Bus Class Definitions for Communication Devices, Version 1.1.
Data DLCI Channels: 027.010 Control 1AT/PPP 2DM 3HIP (carrying CnS) 4NMEA (enabled by default on AC402/MC5728V/SL5010/ SL5011)
28
2130634
USB architecture
Host Device
The host device implements MUX/DeMUX to extract data from each DLCI channel. The representation of DLCIs is the responsibility of the host platform driver. They are typically presented as COM ports but could be presented in other ways. USB interface Management element 0
MDM6085 / QSC6085
Control
Notification element
Interface 0 1
Interrupt Note: Used for out-of-band signaling.
27.010 MUX
27.010 MUX
27.010 Control
27.010 Control
AT AT and PPP DM
1 Interface 0 2 IN 2 OUT
AT AT and PPP HIP DM CnS
HIP (carrying CnS) NMEA
endpoints
HIP (carrying CnS) NMEA
4
DLCI
4
DLCI
Figure 2-2: CDMA devicesMUX endpoints
Rev 5 Nov.11
29
CDMA devicesHybrid-MUX
This section describes hybrid-MUX mode for CDMA devices.
Chipsets
MDM6085 QSC6085 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-6, CDMA devicesHybrid-MUX endpoints/DLCI assignments, on page 30 Figure 2-3, CDMA devicesHybrid-MUX endpoints/DLCI assignments, on page 31
Architecture
CDMA devicesHybrid-MUX architecture

Table 2-6: CDMA devices Hybrid-MUX endpoints / DLCI assignments
0 1 IN (Interrupt)
Data (AT/PPP) Data DLCI Channels: 027.010 Control 2DM 3HIP (carrying CnS) 4NMEA (Only on GPS-enabled devices. Enabled by default on AC402/MC5728V/SL5010/SL5011.)
30
2130634
USB architecture
Host Device
The host device implements Hybrid MUX/DeMUX to extract data from each DLCI channel. The representation of DLCIs is the responsibility of the host platform driver. They are typically presented as COM ports but could be presented in other ways. USB interface Management element Notification element 0
MDM6085 / QSC6085
Control
Interface 0 1
Interrupt Note: Used for out-of-band signaling. AT AT and PPP
AT
27.010 MUX
27.010 MUX
27.010 Control
DM
27.010 Control
DM
HIP (carrying CnS)
endpoints
HIP (carrying CnS) HIP CnS NMEA (GPS-enabled devices only)
NMEA
4
DLCI
4
DLCI
Figure 2-3: CDMA devicesHybrid-MUX endpoints/DLCI assignments
Rev 5 Nov.11
31
UMTS module-specific USB architectures

Sierra Wireless UMTS AirCard and AirPrime modules (detailed in Table 1-1 on page 15) implement the following chipset-specific USB architectures: UMTS devices (legacy VID/PID)Non-MUX (See page 33.) UMTS devices (legacy VID/PID)MUX (See page 44.) UMTS devices (DIP VID/PID)Non-MUX (See page 47.) UMTS devices (QMI VID/PID)Non-MUX (See page 59.)
32
2130634
USB architecture
UMTS devices (legacy VID/PID)Non-MUX

This section describes non-MUX mode for UMTS devices using a legacy VID/ PID.

Chipsets
MDM6200 MDM6270 MSM6290 QSC6270 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-7, UMTS devices (legacy VID/PID)Non-MUX endpoints, on page 33 Figure 2-4, UMTS devices (legacy VID/PID)Non-MUX endpoints, on page 35 Table 2-8, UMTS devices (legacy VID/PID)USB descriptors, on page 36 Table 2-9, MSM6290 (C888/C889) (TRU-Install mode)USB descriptors, on page 42
Architecture
Descriptors
UMTS devices (legacy VID/PID)Non-MUX architecture

Table 2-7: UMTS devices (legacy VID / PID) Non-MUX endpoints
0 1 2 3 1 IN / OUT (Bulk) 2 IN / OUT (Bulk) 3 IN / OUT (Bulk) 4 IN (Interrupt) HIP
For details, see SetControlLineState in the Universal Serial Bus Class Definitions for Communication Devices document.
QUALCOMM DM diagnostics NMEA Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
5 IN / 4 OUT (Bulk) AT
Rev 5 Nov.11
33
Table 2-7: UMTS devices (legacy VID / PID) Non-MUX endpoints (Continued)
Interface 4 Endpoint 6 IN (Interrupt) Supported service Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
7 IN / 5 OUT (Bulk) 5 (MSM6290 only) 8 IN (Interrupt)
Data 1 (PDP context 1) Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
9 IN / 6 OUT (Bulk) 6 (MSM6290 only) 10 IN (Interrupt)
Data 2 (PDP context 2) Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
11 IN / 7 OUT (Bulk) 7 (MSM6290 only) 12 IN / 8 OUT (Bulk) Note: TRU-Install mode uses Interface 0 (endpoints 1-IN and 1-OUT).
Data 3 (PDP context 3) (C8XX only) Mass storage (when enabled) You can access the microSD device in TRU-Install mode (Interface 0) and modem mode (Interface 7).
In TRU-Install mode, the TRU-Install CD-ROM and SD disk are presented as two logical unit numbers (LUNs).
Note: In these products, each COM port has its own interface and their endpoint assignments are found in the USB interface descriptor. Do not use the AT!NVPORTMAP command with these products.
34
2130634
USB architecture
Host Device
Management element
USB interface Control channel 0
MDM6200 / MDM6270 / MSM6290 / QSC6270

Control
HIP (carrying CnS)
Interface 0 1 IN 1 OUT Interface 1 2 IN 2 OUT Interface 2 3 IN 3 OUT Interface 3 4 IN 5 IN 4 OUT Interface 4 6 IN 7 IN 5 OUT
HIP (carrying CnS)
DM
DM
NMEA
NMEA
Notification element AT
Interrupt (Out-of-band signaling) AT
Notification element Data 1 (PDP context 1)
Interrupt (Out-of-band signaling) Data 1 (PDP context 1)
(MSM6290 only) Interface 5 8 IN 9 IN 6 OUT
(MSM6290 only) Interface 6 10 IN 11 IN 7 OUT
Note: In TRUInstall mode, the micro-SD device uses Interface 0 (endpoints 1-IN and 1-OUT).
MS Driver
(MSM6290 [C8XX] only) Interface 7 12 IN 8 OUT
MS (Mass Storage)
endpoints
Figure 2-4: UMTS devices (legacy VID/PID)Non-MUX endpoints
Rev 5 Nov.11
35
UMTS devices (legacy VID/PID)Non-MUX descriptors

Table 2-8: UMTS devices (legacy VID / PID) USB descriptors
Descriptor Device Descriptor Field identifier bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct Value 0x12 0x01 0x0200 0x00 0x00 0x00 0x40 0x1199 0x683C
USB spec version 2
Max packet size for endpoint 0 = 64 Sierra Wireless Inc. MC8790, MC8790V, MC8791V, MC8792V, MC8795V 0x683D SL8080, SL8081, SL8082, SL8083, SL8084, SL8085 SL8090, SL8091, SL8092, SL8093 0x6890 AC501, AC504, C888, C889, USB301, USB302 bcdDevice 0x0006 iManufacturer 0x03 iProduct 0x02 iSerialNumber 0x00 bNumConfigurations 0x01 bLength 0x09 bDescriptorType 0x02 wTotalLength 0x00C6 bNumInterfaces 0x05 SL8080, SL8081, SL8082, SL8083, SL8084, SL8085 SL8090, SL8091, SL8092, SL8093 0x07 AC501, AC504, MC8790, MC8790V, MC8791V, MC8792V, MC8795V, USB301, USB302 0x07 C888, C889 (Mass Storage not enabled) 0x08 C888, C889 (Mass Storage enabled) bConfigurationValue 0x01 iConfiguration 0x00 bmAttributes 0xE0 MaxPower 0x00
36
2130634
USB architecture
Table 2-8: UMTS devices (legacy VID / PID) USB descriptors (Continued)
Descriptor Interface Descriptor (Number 0x00 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x00 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x81 0x02 0x0200 0x20 0x07 0x05 0x01 0x02 0x0200 0x20 0x09 0x04 0x01 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x82 0x02 0x0200 0x20 0x07 0x05 0x02 0x02 0x0200 0x20
Number of endpoints used by this interface is 2, excluding endpoint 0. Vendor-specific device class Vendor-specific device subclass
ep #1, IN Transfer Type: Bulk Must be high speed device 32 ms
ep #1, OUT Transfer Type: Bulk Must be high speed device 32 ms
Rev 5 Nov.11
37
Descriptor Interface Descriptor (Number 0x02 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x02 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x83 0x02 0x0200 0x20 0x07 0x05 0x03 0x02 0x0200 0x20 0x09 0x04 0x03 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x84 0x03 0x0040 0x05 0x07 0x05 0x85 0x02 0x0200 0x20
Number of endpoints used by this interface is 3, excluding endpoint 0.
ep #4, IN Transfer Type: Interrupt 5 ms
38
2130634
USB architecture
Descriptor Endpoint Descriptor (0x04) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface Value 0x07 0x05 0x04 0x02 0x0200 0x20 0x09 0x04 0x04 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x86 0x03 0x0040 0x05 0x07 0x05 0x87 0x02 0x0200 0x20 0x07 0x05 0x05 0x02 0x0200 0x20 0x09 0x04 0x05 0x00 0x03 0xFF 0xFF 0xFF 0x00
Number of endpoints used by this interface is 3, excluding endpoint 0. Vendor-specific device class
(MSM6290 only) Interface Descriptor (Number 0x05 Alternate Setting 0x00)
Rev 5 Nov.11
39
Descriptor (MSM6290 only) Endpoint Descriptor (0x88) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x88 0x03 0x0040 0x05 0x07 0x05 0x89 0x02 0x0200 0x20 0x07 0x05 0x06 0x02 0x0200 0x20 0x09 0x04 0x06 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8A 0x03 0x0040 0x05 0x07 0x05 0x8B 0x02 0x0200 0x20 0x07 0x05 0x07 0x02 0x0200 0x20
(MSM6290 only) Endpoint Descriptor (0x89)
(MSM6290 only) Interface Descriptor (Number 0x06 Alternate Setting 0x00)
(MSM6290 only) Endpoint Descriptor (0x8A)
(MSM6290 only) Endpoint Descriptor (0x8B)
40
2130634
USB architecture
Descriptor (C888 / C889 Mass Storage enabled) Interface Descriptor (Number 0x07 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bString bLength Value 0x09 0x04 0x07 0x00 0x02 0x08 0x06
(C888 / C889 Mass Storage enabled) Endpoint Descriptor (0x08)
(C888 / C889 Mass Storage enabled) Endpoint Descriptor (0x8C)
Manufacturer String Descriptor
Product String Descriptor
bDescriptorType bString
0x50 0x00 0x07 0x05 0x08 ep #8, OUT 0x02 Transfer Type: Bulk 0x0200 0x00 0x07 0x05 0x8C ep #12, IN 0x02 Transfer Type: Bulk 0x0200 0x00 60 0x03 (Default value) Sierra Wireless, Incorporated 0x14 MC8790, MC8790V, MC8791V, MC8792V, MC8795V SL8080, SL8081, SL8082, SL8083, SL8084, SL8085 SL8090, SL8091, SL8092, SL8093 0x16 AC501, AC504 C888, C889 USB301, USB302 0x03 Mini Card M8790, MC8790V, MC8791V, MC8792V, MC8795V HSPA Modem AC501, AC504, C888, C889 USB301, USB302 SL8080, SL8081, etc. SL8080, SL8081, SL8082, SL8083, SL8084, SL8085 SL8090, SL8091, SL8092, SL8093
Number of endpoints used by this interface is 2, excluding endpoint 0. Interface implements the Mass Storage class Interface implements the SCSI Transparent subclass Interface uses the Bulk-only protocol
Rev 5 Nov.11
41
Descriptor String Descriptor 0 (Language Descriptor) Port Configuration String Descriptor (0xF0) Field identifier bLength bDescriptorType wLANGID[0] bLength bDescriptorType bString Value 4 0x03 0x0409 EnglishUnited States 0x08 0x03 (Six consecutive bytes) 0x0031 MUX supported 0x0030 Hybrid not supported 0x0030 NMEA not enabled
MSM6290 descriptors (TRU-Install mode)

Table 2-9: MSM6290 (C888 / C889) (TRU-Install mode) USB descriptors
Descriptor Device Descriptor Field identifier bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct bcdDevice iManufacturer iProduct iSerialNumber bNumConfigurations bLength bDescriptorType wTotalLength bNumInterfaces bConfigurationValue iConfiguration bmAttributes MaxPower bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface Value 0x12 0x01 0x0200 0x00 0x00 0x00 0x40 0x1199 0x0FFF 0x0000 0x02 0x01 0x03 0x01 0x09 0x02 0x0020 0x01 0x01 0x00 0xE0 0x00 0x09 0x04 0x00 0x00 0x02 0x08 0x06 0x50 0x00
USB spec version 2
Max packet size for endpoint 0 = 64 Sierra Wireless Inc.
Number of endpoints used by this interface is 2, excluding endpoint 0. Mass Storage class SCSI Transparent subclass Bulk-Only protocol
42
2130634
USB architecture
Table 2-9: MSM6290 (C888 / C889) (TRU-Install mode) USB descriptors

Descriptor Endpoint Descriptor (0x01) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x01 0x02 0x0200 0x00 0x07 0x05 0x81 0x02 0x0200 0x20
ep #1, OUT Transfer Type: Bulk Must be high speed device
Rev 5 Nov.11
43
UMTS devices (legacy VID/PID)MUX

This section describes MUX mode for UMTS devices using a legacy VID/PID.

Chipsets
MDM6200 MDM6270 MSM6290 QSC6270 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-10, UMTS devices (legacy VID/PID)MUX endpoints/DLCI assignments, on page 44 Figure 2-5, UMTS devices (legacy VID/PID)MUX endpoints/DLCI assignments, on page 46
Architecture
UMTS devices (legacy VID/PID)MUX architecture

Table 2-10: UMTS devices (legacy VID/PID) MUX endpoints / DLCI assignments
0 1 IN / OUT (Bulk)
HIP (carrying CnS), DM, NMEA, AT, Data DLCI Channels: 0Control 1Primary AT/PPP 2DM 3HIP (carrying CnS) 4NMEA (GPS-enabled devices only) 5Data 1 (PDP context 1) 6Data 2 (PDP context 2) 7Data 3 (PDP context 3) Note: NMEA must be enabled by Sierra Wireless, and may not be the default shipping configuration.
1 2 3
2 IN / 2 OUT (Bulk) 3 IN / 3 OUT (Bulk) 4 IN (Interrupt) 5 IN / 4 OUT (Bulk)
Not used Not used Not used Not used
44
2130634
USB architecture
Table 2-10: UMTS devices (legacy VID/PID) MUX endpoints / DLCI assignments
Interface 4 Endpoints 6 IN (Interrupt) 7 IN / 5 OUT (Bulk) 5 8 IN (Interrupt) 9 IN / 6 OUT (Bulk) 6 10 IN (Interrupt) 11 IN / 7 OUT (Bulk) 7 12 IN / 8 OUT (Bulk) Note: TRU-Install mode uses interface 0. Supported service Not used Not used Not used Not used Not used Not used (C8XX only) Mass storage (when enabled) You can access the microSD device in TRU-Install mode (Interface 0) and modem mode (Interface 7).
Rev 5 Nov.11
45
Host Device
USB interface Management element 0
MDM6200 / MDM6270 / MSM6290 / QSC6270
Control
27.010 MUX
27.010 MUX
27.010 Control AT
27.010 Control AT
1 2 1 IN 1 OUT
DM
DM
HIP
HIP
NMEA
HIP NMEA (GPS-enabled CnS devices only) Data 1 PDP Context 1
Data 1 PDP Context 1
Data 2 PDP Context 2 Data 3 PDP Context 3
Data 2 PDP Context 2 Data 3 PDP Context 3
DLCI
DLCI
Note: DLCI channel support varies between device types / PIDs.
Note: When in TRU-Install mode, the micro-SD device uses Interface 0 (endpoints 1-IN and 1-OUT).
MS Driver
(C8XX only) Interface 7 12 IN 8 OUT endpoints
MS (Mass Storage)
Figure 2-5: UMTS devices (legacy VID/PID)MUX endpoints/DLCI assignments
46
2130634
USB architecture
UMTS devices (DIP VID/PID)Non-MUX

This section describes non-MUX mode for UMTS devices using the Direct IP VID/PID.

Chipsets
MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-12, UMTS devices Direct IPNon-MUX endpoints, on page 49 Figure 2-6, UMTS devices Direct IPNon-MUX endpoints, on page 51 Table 2-13, UMTS devices (DIP VID/PID)Device/ Configuration Descriptors, on page 52 Table 2-14, UMTS devices (DIP VID/PID)HIP descriptors (Interface/Endpoint), on page 53 Table 2-15, UMTS devices (DIP VID/PID)DM descriptors (Interface/Endpoint), on page 53 Table 2-16, UMTS devices (DIP VID/PID)AT descriptors (Interface/Endpoint), on page 54 Table 2-17, UMTS devices (DIP VID/PID)MDM1 descriptors (Interface/Endpoint), on page 55 Table 2-18, UMTS Mass Storage-capable devices (DIP VID/ PID)MS descriptors (Interface/Endpoint), on page 55 Table 2-19, UMTS devices (DIP VID/PID)DIP1 descriptors (Interface/Endpoint), on page 56 Table 2-20, UMTS devices (DIP VID/PID)DIP2 descriptors (Interface/Endpoint), on page 57 Table 2-21, UMTS devices (DIP VID/PID)DIP3 descriptors (Interface/Endpoint), on page 58
Architecture
Descriptors
Rev 5 Nov.11
47
Dynamic endpoint assignment for Direct IP VID/PID

The default interface configuration for modems using the Direct IP VID/PID is SKU-dependent and includes some combination of these interfaces:
Interface 0 1 2 3 4 7 9 10 11 Service HIP DM (Diagnostic Monitoring) NMEA AT MDM1 (Modem port 1) DIP1 (Direct IP 1) MS (Mass Storage) DIP2 (Direct IP 2) DIP3 (Direct IP 3)
Typical interface configurations include: HIP/DM/AT/MS/DIP1 HIP/DM/AT/MDM1/DIP1/MS HIP/DM/AT/DIP1/DIP2/DIP3/MS
The modems configuration can be further customized by enabling or disabling the NMEA, DM, or MS interfaces. Because endpoint numbers are assigned dynamically to enabled interfaces, the endpoints associated with a given interface may be different when any of these interfaces are disabled. Endpoint numbers are assigned sequentially to enabled interfaces, starting with: 0x81 for Interrupt or Bulk IN endpoints 0x01 for Bulk OUT endpoints
For example, Table 2-11 shows the endpoints assigned to each interface in the configuration HIP/DM/AT/MS/DIP1 when MS is enabled or disabled. When MS is enabled, it uses endpoints 0x85 (5-IN) and 0x04 (4-OUT). However, when MS is disabled, the next interface (DIP1) uses those endpoints.
Table 2-11: Example Interface-dependent endpoint assignments

Endpoints (assigned sequentially to enabled services) HIP (Int 0) MS enabled 0x81 0x01 MS disabled 0x81 0x01 DM (Int 1) 0x82 0x02 0x82 0x02 AT (Int 3) 0x83 0x84 0x03 0x83 0x84 0x03 MS (Int 4) 0x85 0x04 n/a n/a DIP1 (Int 7) 0x86 0x87 0x05 0x85 0x86 0x04
48
2130634
USB architecture
UMTS devices (DIP VID/PID)Non-MUX architecture

Table 2-12: UMTS devices Direct IP Non-MUX endpoints a
Interface Endpoint 0 (Control) Supported service Management element Purpose: 0-OUT is used to emulate control line signals and send encapsulated commands. 0-IN is used to receive encapsulated commands.
For details, see SetControlLineState, SendEncapsulatedCommand, and GetEncapsulatedCommand in Universal Serial Bus Class Definitions for Communication Devices, Version 1.1.
0 1 2 3
IN / OUT (Bulk) IN / OUT (Bulk) IN / OUT (Bulk) IN (Interrupt)
HIP QUALCOMM DM diagnostics NMEA Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
IN / OUT (Bulk) 4b IN (Interrupt)
AT/PPP Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
IN / OUT (Bulk) 7 IN (Interrupt)
MDM1 (Modem port 1 (PDP context 1))/PPP (Also called Data1) Notification element Purpose: Used by Direct IP to send notification indication to host. (ECM) Direct IP (DIP1) (AC3XXU/C888/C889/USB 3XX) Mass storage (when enabled) You can access the microSD device in both TRU-Install mode and modem mode (Interface 9).
IN / OUT (Bulk) 9c IN / OUT (Bulk) Note: TRU-Install mode uses Interface 9 (endpoints 1-IN and 1-OUT).
10 c
IN (Interrupt)
Notification element Purpose: Used by Direct IP to send notification indication to host. (ECM) Direct IP (DIP2)
IN / OUT (Bulk)
Rev 5 Nov.11
49
Table 2-12: UMTS devices Direct IP Non-MUX endpoints a (Continued)

Interface 11 c Endpoint IN (Interrupt) Supported service Notification element Purpose: Used by Direct IP to send notification indication to host. (ECM) Direct IP (DIP3)
IN / OUT (Bulk)
Note: In these products, each COM port has its own interface; their endpoint assignments are found in the USB interface descriptor. Do not use the AT!NVPORTMAP command with these products.
a. The modems default interface configuration is SKU-dependent and includes some combination of the listed interfaces. b. Not available on MDM6270/QSC6270-based devices. c. Not available on MDM6200/MDM6270/QSC6270-based devices.
50
2130634
USB architecture
Host Device
USB interface Management element Control channel 0 Interface 0 BULK IN BULK OUT Interface 1 BULK IN BULK OUT Interface 2 BULK IN BULK OUT
MDM6200 / MDM6270 / MDM8200 / MDM8200A / MDM8220 / MDM9200 / MSM6290 / QSC6270
Control
HIP (carrying CnS)
HIP (carrying CnS)
DM
DM
Notification element NMEA
Interrupt (Notification indication) NMEA
Notification element AT
Interface 3 INTERRUPT BULK IN BULK OUT Interface 4 (Not on MDM6270/QSC6270) INTERRUPT BULK IN BULK OUT
Interrupt (Out-of-band signaling) AT data / PPP
Notification element MDM1
Interrupt (Out-of-band signaling) MDM1 / PPP
Notification element (ECM) Direct IP
Interface 7 INTERRUPT BULK IN BULK OUT Interface 9 (Not on MDM6200/MDM6270/ QSC6270) BULK IN BULK OUT Interface 10 (Not on MDM6200/MDM6270/ QSC6270) INTERRUPT BULK IN BULK OUT
Interrupt (Notification indication) Direct IP data
Mass Storage
(AC3XXU / C888 / C889 / USB 3XX) Mass Storage
Interrupt (Notification indication) (DIP2) Direct IP data
Interface 11 (Not on MDM6200/MDM6270/ QSC6270) INTERRUPT BULK IN BULK OUT
Interrupt (Notification indication) (DIP3) Direct IP data
Figure 2-6: UMTS devices Direct IPNon-MUX endpoints
Rev 5 Nov.11
51
UMTS devices (DIP VID/PID)Non-MUX descriptors

Table 2-13: UMTS devices (DIP VID/PID) Device / Configuration Descriptors
Descriptor Device Descriptor Field identifier bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct Value 0x12 0x01 0x0200 USB spec version 2 0x00 0x00 0x00 0x40 Max packet size for endpoint 0 = 64 0x1199 Sierra Wireless Inc. 0x68A3 (Standard Direct IP PID) 0x68AA (Carrier-specific Direct IP PID) bcdDevice 0x0006 iManufacturer 0x03a iProduct 0x02a iSerialNumber 0x00a bNumConfigurations 0x01 bLength 0x09 bDescriptorType 0x02 wTotalLength Calculated automatically as the sum of the bLength fields in: Configuration Descriptor Each enabled Interface Descriptor and associated Endpoint Descriptors bNumInterfaces 0x030x08 Configuration supports 3 to 8 interfaces Actual value depends on provisioned configuration and state (enabled/disabled) of NMEA, DM, and MS interfaces. bConfigurationValue 0x01 iConfiguration 0x01 bmAttributes 0xA0 AC501, AC503, AC504, C8XX, USB 30X 0xE0 MC77XX MC87XX SL808X SL809X MaxPower 0xFA AC501, AC503, AC504, C8XX, USB 30X 0x00 MC77XX MC87XX SL808X SL809X
a. iManufacturer, iProduct, and iSerial values are SKU-dependent and may vary from the values shown here.
52
2130634
USB architecture
Table 2-14: UMTS devices (DIP VID/PID) HIP descriptors (Interface / Endpoint)
Descriptor Interface Descriptor (Number 0x00 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x00 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x02 0x0200 0x20 0x07 0x05 0x0n 0x02 0x0200 0x20
Endpoint Descriptor (0x8 n Sequentially assigned, beginning at 0x81 for first enabled interface)
ep #8n, INa Transfer Type: Bulk Must be high speed device 32 ms
ep #n, OUTa Transfer Type: Bulk Must be high speed device 32 ms
a. The number of endpoints (n) is listed in the bNumInterfaces field of the Configuration Descriptor (Index 0x00) on page 52.
Table 2-15: UMTS devices (DIP VID/PID) DM descriptors (Interface / Endpoint)

Descriptor Interface Descriptor (Number 0x01 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x01 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x02 0x0200 0x20
ep #n, INa Transfer Type: Bulk Must be high speed device 32 ms
Rev 5 Nov.11
53
Table 2-15: UMTS devices (DIP VID/PID) DM descriptors (Interface / Endpoint) (Continued)
Descriptor Endpoint Descriptor (0x0 n Sequentially assigned, beginning at 0x01 for first enabled interface) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x0n 0x02 0x0200 0x20
Table 2-16: UMTS devices (DIP VID/PID) AT descriptors (Interface / Endpoint)

Descriptor Interface Descriptor (Number 0x03 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x03 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x03 0x0040 0x05 0x07 0x05 0x8n 0x02 0x0200 0x20 0x07 0x05 0x0n 0x02 0x0200 0x20
ep #n, INa Transfer Type: Interrupt
54
2130634
USB architecture
Table 2-17: UMTS devices (DIP VID / PID) MDM1 descriptors (Interface / Endpoint) a
Descriptor Interface Descriptor (Number 0x04 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x04 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x03 0x0040 0x05 0x07 0x05 0x8n 0x02 0x0200 0x20 0x07 0x05 0x0n 0x02 0x0200 0x20
ep #n, INb Transfer Type: Interrupt
ep #n, INb Transfer Type: Bulk Must be high speed device 32 ms
ep #n, OUTb Transfer Type: Bulk Must be high speed device 32 ms
a. Not supported by MDM6270/QSC6270-based devices. b. The number of endpoints (n) is listed in the bNumInterfaces field of the Configuration Descriptor (Index 0x00) on page 52.
Table 2-18: UMTS Mass Storage-capable devices (DIP VID / PID) MS descriptors (Interface / Endpoint) a
Descriptor Interface Descriptor (Number 0x09 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface Value 0x09 0x04 0x09 0x00 0x02 0x08 0x06 0x50 0x00
Number of endpoints used by this interface is 2, excluding endpoint 0. Mass Storage class SCSI Transparent subclass Bulk-Only protocol
Rev 5 Nov.11
55
Table 2-18: UMTS Mass Storage-capable devices (DIP VID / PID) MS descriptors (Interface / Endpoint) a (Continued)
Descriptor Endpoint Descriptor (0x0 n Sequentially assigned, beginning at 0x01 for first enabled interface) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x0n 0x02 0x0200 0x20 0x07 0x05 0x8n 0x02 0x0200 0x20
a. Not supported by MDM6200/MDM6270/QSC6270-based devices. b. The number of endpoints (n) is listed in the bNumInterfaces field of the Configuration Descriptor (Index 0x00) on page 52.
Table 2-19: UMTS devices (DIP VID / PID) DIP1 descriptors (Interface / Endpoint)
Descriptor Interface Descriptor (Number 0x07 Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x07 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x03 0x0040 0x05 0x07 0x05 0x8n 0x02 0x0200 0x20
ep #n, INa Transfer Type: Interrupt
56
2130634
USB architecture
Table 2-19: UMTS devices (DIP VID / PID) DIP1 descriptors (Interface / Endpoint) (Continued)
Descriptor Endpoint Descriptor (0x0 n Sequentially assigned, beginning at 0x01 for first enabled interface) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x0n 0x02 0x0200 0x20
Table 2-20: UMTS devices (DIP VID / PID) DIP2 descriptors (Interface / Endpoint) a
Descriptor Interface Descriptor (Number 0x0A Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x0A 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x03 0x0040 0x05 0x07 0x05 0x8n 0x02 0x0200 0x20 0x07 0x05 0x0n 0x02 0x0200 0x20
Rev 5 Nov.11
57
Table 2-21: UMTS devices (DIP VID / PID) DIP3 descriptors (Interface / Endpoint) a
Descriptor Interface Descriptor (Number 0x0B Alternate Setting 0x00) Field identifier bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x09 0x04 0x0B 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x8n 0x03 0x0040 0x05 0x07 0x05 0x8n 0x02 0x0200 0x20 0x07 0x05 0x0n 0x02 0x0200 0x20
58
2130634
USB architecture
UMTS devices (QMI VID/PID)Non-MUX

This section describes non-MUX mode for UMTS devices using a QMI VID/PID.
Chipsets MDM9200 MDM9600 For a list of devices using these chipsets, see Table 1-1 on page 15. Table 2-22, UMTS devices (QMI VID/PID)Non-MUX endpoints, on page 59 Figure 2-7, UMTS devices (QMI VID/PID)Non-MUX endpoints, on page 60 Table 2-23, UMTS devices (QMI VID/PID)USB descriptors, on page 61
Architecture
Descriptors
UMTS devices (QMI VID/PID) non-MUX architecture

Table 2-22: UMTS devices (QMI VID / PID) Non-MUX endpoints
0 2 3 1 IN / OUT (Bulk) 2 IN / OUT (Bulk) 3 IN (Interrupt)
For details, see SetControlLineState in the Universal Serial Bus Class Definitions for Communication Devices document.
QUALCOMM DM diagnostics NMEA Notification element Purpose: Send asynchronous notification of modem status (for example, DSR, DCD, and RI) to the host.
4 IN / 3 OUT (Bulk) 8 5 IN (Interrupt)
AT (MDM) Modem port providing full-featured AT command support. Notification element Purpose: Used to send notification indications for to host. NET QMI network interface
6 IN / 4 OUT (Bulk)
Rev 5 Nov.11
59
Host Device
Management element
USB interface Control channel 0
MDM9200 / MDM9600
Control
DM
Interface 0 1 IN 1 OUT Interface 2 2 IN 2 OUT Interface 3 3 IN 4 IN 3 OUT Interface 8 5 IN 6 IN 4 OUT
DM
NMEA
NMEA
Notification element AT (MDM)
Interrupt (Out-of-band signaling) AT (MDM)
Notification element NET (QMI control/data)
Interrupt (Out-of-band signaling) NET (QMI control/data)
endpoints
Figure 2-7: UMTS devices (QMI VID/PID)Non-MUX endpoints
60
2130634
USB architecture
UMTS devices (QMI VID/PID) non-MUX descriptors

Table 2-23: UMTS devices (QMI VID / PID) USB descriptors
Descriptor Device Descriptor Field identifier bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct bcdDevice iManufacturer iProduct iSerialNumber bNumConfigurations bLength bDescriptorType wTotalLength bNumInterfaces bConfigurationValue iConfiguration bmAttributes MaxPower bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x12 0x01 0x0200 0x00 0x00 0x00 0x40 0x1199 0x68A2 0x0006 0x03 0x02 0x04 0x01 0x09 0x02 0x0073 0x04 0x01 0x01 0xE0 0x00 0x09 0x04 0x00 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x81 0x02 0x0200 0x20
USB spec version 2
Max packet size for endpoint 0 = 64 Sierra Wireless Inc.
Rev 5 Nov.11
61
Table 2-23: UMTS devices (QMI VID / PID) USB descriptors (Continued)
Descriptor Endpoint Descriptor (0x01) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x01 0x02 0x0200 0x20 0x09 0x04 0x02 0x00 0x02 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x82 0x02 0x0200 0x20 0x07 0x05 0x02 0x02 0x0200 0x20 0x09 0x04 0x03 0x00 0x03
0xFF 0xFF 0xFF 0x00 0x07 0x05 0x83 ep #3, IN 0x03 Transfer Type: Interrupt 0x0040 0x05 5 ms
62
2130634
USB architecture
Table 2-23: UMTS devices (QMI VID / PID) USB descriptors (Continued)
Descriptor Endpoint Descriptor (0x04) Field identifier bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bInterfaceNumber bAlternateSetting bNumEndpoints bInterfaceClass bInterfaceSubClass bInterfaceProtocol iInterface bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Value 0x07 0x05 0x84 0x02 0x0200 0x20 0x07 0x05 0x03 0x02 0x0200 0x20 0x09 0x04 0x08 0x00 0x03 0xFF 0xFF 0xFF 0x00 0x07 0x05 0x85 0x03 0x0040 0x05 0x07 0x05 0x86 0x02 0x0200 0x20 0x07 0x05 0x04 0x02 0x0200 0x20
Rev 5 Nov.11
63
64
2130634
3: Services
This chapter describes the services (logical protocols) supported by the AirCard and AirPrime devices for the transfer of data and control information. These services include (dependent on device type): Control on page 65 Interrupt on page 65 AT/PPP on page 66 HIP (Host Interface Protocol) on page 67 CnS (Control and Status) on page 67 DM (QUALCOMM Diagnostic Monitoring) on page 68 NMEA (National Marine Electronics Association) on page 69 Data 1, Data 2, Data 3 (Additional PPP) on page 70 Mass Storage on page 71 Direct IP on page 71
USB protocols
Control
The standard control channel (management element) is implemented on endpoint 0 (as required by the USB and ACM specifications). This supports the use of selected USB interface and power management, ACM, and Sierra Wireless proprietary commands and requests. For a list of supported CDC / ACM messages, see Supported CDC USB commands on page 101.
Interrupt
USB interrupt channels (notification elements) are implemented on the following endpoints: MDM6200/MDM6270/QSC6270 (using legacy VID/PID)4, 6 MSM6290 (using legacy VID/PID)4, 6, 8, 10 All UMTS devices with Direct IP VID/PIDEndpoints vary depending on modem configuration. Two interrupt channels are used for the AT and ECM services. All other modules1
This is part of the typical Communication Interface Class for a CDC device and supports the notifications in the ACM specification and proprietary notifications defined by Sierra Wireless.
Rev 5 Nov.11
65
Data services
AT/PPP
The AT/PPP data channel is implemented using the endpoints listed in Table 3-1 for devices using the specified chipsets.
Table 3-1: AT / PPP data channel endpoints (by chipset and mode)
Non-MUX endpoints Chipseta Data MDM6085 QSC6085 (Legacy VID/PID) MDM6200 MDM6270 MSM6290 QSC6270 (Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 (QMI VID/PID) MDM9200 MDM9600 (Interface 0) 2-IN 2-OUT (Interface 3) 5-IN 4-OUT Flow control 1-IN Data (Interface 0; 2-IN/2-OUT) DLCI-1 (Interface 0; 1-IN/1-OUT) DLCI-1 Flow control DLCI-0 Data (Interface 0) 2-IN 2-OUT Flow control 1-IN MUX endpoints Hybrid-MUX endpoints
4-IN
DLCI-0
N/A
(Interface 3) IN/OUT (Bulk)
IN (Interrupt)
N/A
N/A
Note: Endpoints vary depending on which services have been implemented.
(Interface 3) 4-IN 3-OUT
3-IN
N/A
N/A
Note: Interface 3 is a MDM interface featuring full AT command support.

a. For a list of devices using these chipsets, see Table 1-1 on page 15.
Note: The Heatherington escape method (TIES) is not supported.
The AT/PPP data channel supports the transfer of AT commands for module control, and TCP/IP (or other transport protocol) data via PPP for network communication. For lists of supported AT commands, see: CDMA devices AT Command Set for User Equipment (UE) (Release 6) AT Command Reference (Document 2130620) Proprietary and Confidential 2130634
66
Services
Extended AT Command Reference (Document 2130621) (for AirCards and MiniCards) CDMA SL501x AT Command Reference (Document 4110801) (for SLseries devices) UMTS devices AirCard/AirPrime UMTS Devices Supported AT Command Reference (Document 2130617)
HIP (Host Interface Protocol)

HIP is a proprietary protocol developed to multiplex different information types over a single interface (for example, carrying CnS commands and DM logging data). The HIP data channel is implemented using the endpoints listed in Table 3-2 for devices using the specified chipsets.
Table 3-2: HIP data channel endpoints (by chipset and mode)
Non-MUX endpoints Chipset a Data MDM6085 QSC6085 (Legacy VID/PID) MDM6200 MDM6270 MSM6290 QSC6270 (Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 (Interface 0) 4-IN 4-OUT (Interface 0) 1-IN 1-OUT Flow control Data (Interface 0; 2-IN/2-OUT) DLCI-3 (Interface 0; 1-IN/1-OUT) DLCI-3 Flow control DLCI-0 Data (Interface 0; 4-IN/4-OUT) DLCI-3 Flow control 1-IN MUX endpoints Hybrid-MUX endpoints
DLCI-0
N/A
N/A
N/A
For details on the HIP protocol, refer to CDMA 1xEV-DO CnS Reference (Document 2130754), HIP Basics chapter, or AirPrime UMTS MC and SL Series CnS Reference (Document 2130602), Chapter 3: HIP Basics.
CnS (Control and Status)

CnS objects (commands) are used to manage the modules configuration, and to provide status reporting and monitoring of the device.
Rev 5 Nov.11
67
These objects are transported between the host and module by embedding them in HIP messages (see HIP (Host Interface Protocol) on page 67). For details on CnS objects, refer to CDMA 1xEV-DO CnS Reference (Document 2130754) or AirPrime UMTS MC and SL Series CnS Reference (Document 2130602).
DM (QUALCOMM Diagnostic Monitoring)

The QUALCOMM DM logging data provides information about the operation of the wireless protocol stack, and other diagnostic information for firmware developers. It can be used for configuration, logging, testing, and debugging of the embedded module. For details on implementing protocol stack logging to access QUALCOMM DM information, refer to AirPrime UMTS MC and SL Series CnS Reference (Document 2130602). The DM data channel is implemented using the endpoints listed in Table 3-3 for devices using the specified chipsets. For additional information on logging DM data, see QUALCOMM DM Data Logging on page 103.
Table 3-3: DM data channel endpoints (by chipset and mode)

Non-MUX endpoints Chipseta Data MDM6085 QSC6085 (Legacy VID/PID) MDM6200 MDM6270 MSM6290 QSC6270 (Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 (QMI VID/PID) MDM9200 MDM9600 (Interface 0) 8-IN 8-OUT (Interface 1) 2-IN 2-OUT Flow control Data (Interface 0) 2-IN/2-OUT DLCI-2 (Interface 0) 1-IN/1-OUT DLCI-2 Flow control DLCI-0 Data (Interface 0) 4-IN/4-OUT DLCI-2 N/A Flow control MUX endpoints Hybrid-MUX endpoints
N/A
N/A
N/A
N/A
68
2130634
Services
NMEA (National Marine Electronics Association)

The NMEA data channel is used to transfer GPS receiver data (NMEA-0183 formatted sentences) between the module and the host for use in LocationBased Services (LBS) applications. The NMEA data channel is implemented using the endpoints listed in Table 3-4 for GPS-enabled devices using the specified chipsets.
Table 3-4: NMEA data channel endpoints (by chipset and mode)
Non-MUX endpoints Chipseta Data MDM6085 QSC6085 (Legacy VID/PID) MDM6200 MDM6270 MSM6290 QSC6270 (Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 (QMI VID/PID) MDM9200 MDM9600 (Interface 0) 5-IN 5-OUT (Interface 2) 3-IN 3-OUT Flow control Data (Interface 0) 2-IN/2-OUT DLCI-4 (Interface 0) 1-IN/1-OUT DLCI-4 Flow control DLCI-0 Data (Interface 0) 4-IN/4-OUT DLCI-4 Flow control 1-INS MUX endpoints Hybrid-MUX endpoints
DLCI-0
N/A
N/A
N/A
N/A
N/A
Note: The modems default shipping configuration may include NMEA support. For those modems that support NMEA, the default NMEA channel is ON for MDM6085- and QSC6085-based devices, and OFF for all others.
Rev 5 Nov.11
69
Data 1, Data 2, Data 3 (Additional PPP)

The Data 1, Data 2, and Data 3 data channels are implemented using the endpoints listed in Table 3-5 for devices using the specified chipsets.
Table 3-5: Data 1/Data 2/Data 3 data channel endpoints (by chipset and mode)
Non-MUX endpoints Chipseta Data (Legacy VID/PID) MSM6290 (Interface 4) Data 1: 7-IN/5-OUT (Interface 5) Data 2: 9-IN/6-OUT (Interface 6) Data 3: 11-IN/7-OUT (Direct IP VID/PID) MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 (Interface 4) MDM1 (Data 1): IN/OUT (Bulk) Flow control (Interface 4) Data 1: 6-IN (Interface 5) Data 2: 8-IN (Interface 6) Data 3: 10-IN (Interface 4) IN N/A Data (Interface 0) 1-IN/1-OUT Data 1: DLCI-5 Data 2: DLCI-6 Data 3: DLCI-7 Flow control DLCI-0 MUX endpoints
These channels are used to establish additional data connections to the remote network. These connections may have one or more of the following properties: A different quality of service than the other connections A different APN (Access Point Name) ATDT and ATI are the only supported AT commands
Limitations of these channels include:
70
2130634
Services
Mass Storage
(C888/C889/USB 306/USB 307/AC USB 308/AC USB 309/AC 310U) In modem mode (non-MUX, MUX), the module can be configured to add a mass storage device using the endpoints listed in Table 3-6 for devices using the specified chipsets.
Table 3-6: Mass Storage data channel endpoints (by chipset and mode)
Chipseta (Legacy VID / PID) MSM6290 b (Direct IP VID / PID) MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 a Modem mode endpoints (Non-MUX, MUX) Interface 7 12-IN 8-OUT Interface 9 IN/OUT (Bulk) Note: Endpoints vary depending on which services have been implemented. TRU-Install mode endpoints Interface 0 1-IN 1-OUT Interface 9 1-IN 1-OUT
a. For a list of devices using these chipsets, see Table 1-1 on page 15. b. Device must be configured to support Mass Storage.
Note: You can access the microSD device in both the TRU-Install and modem modes. In TRU-Install mode, the TRU-Install CD-ROM and SD disk are presented as two logical unit numbers (LUNs).
Direct IP
(UMTS devices using Direct IP VID/PID) Direct IP mode provides a means of achieving higher throughput rates and improved CPU efficiency on HSPA+ networks compared to data transfers using PPP. The Sierra Wireless driver achieves this by transporting IP packets over USB without using PPP. Direct IP is available in non-Mux mode as described in Table 3-7 on page 72. Endpoints are dynamically assigned based on the interfaces that are enumerated. For details about Direct IP mode on Sierra Wireless modems, see Direct IP mode on page 105.
Rev 5 Nov.11
71
Table 3-7: Direct IP data channel endpoints (by chipset)

Chipseta (Direct IP VID / PID) MDM6200 b MDM6270 b MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 b Non-MUX interfaces DIP1Interface 7c DIP2Interface 10 DIP3Interface 11 IN/OUT (Bulk) IN (Notification) Note: Endpoints vary depending on which services have been implemented.
a. For a list of devices using these chipsets, see Table 1-1 on page 15. b. DIP2/DIP3 are not supported by MDM6200, MDM6270, QSC6270. c. DIP1 is the default interface for configurations supporting multiple DIP interfaces.
QMI (NET interface)

(UMTS devices using QMI VID/PID) Devices operating in QMI mode (Qualcomms propietary framework) use the NET interface to transfer data packets over USB rather than using PPP. QMI is available in non-Mux mode as described in Table 3-8 on page 72. For details about QMI support on Sierra Wireless modems, see the Linux QMI SDK Application Developers Guide.
Table 3-8: QMI data channel endpoints (by chipset)

Chipseta (QMI VID / PID) MDM9200 MDM9600 NETInterface 8 6-IN/4-OUT (Bulk) 5-IN (Notification) Non-MUX interfaces
72
2130634
A: Vendor-specific commands
The modems state can be controlled using vendor-specific commands over the USB control interface as an alternative to using AT commands. As described in Universal Serial Bus Specification, Rev 2.0, each control transfer includes the following: Setup stage (host to module) An optional Data stage (information being transferred host to module, or module to host) Status stage (opposite direction from the previous stage).
Command availability
Table A-1: Command availability by chipseta
(Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270
Command / Description
MDM6085 QSC6085
(Legacy VID/PID) MDM6200 MDM6270 MSM6290 QSC6270
(QMI VID/ PID) MDM9200 MDM9600
Set Device Power State on page 75 Powers the modem on or off Set Mode Non-MUX on page 76 Tears down the 27.010 MUX protocol on the selected channel Set Mode MUX on page 77 Sets up the 27.010 MUX protocol on the selected channel Get Mode MUX on page 79 Tells the module to return the 27.010 MUX protocol status for a selected channel Get NDIS Support on page 81 Tells the module to indicate if the NDIS driver is supported Get NDIS Preference on page 82 Tells the module to indicate if the NDIS driver is established or disabled Get Attributes on page 83 Query the attributes of the firmware image
Rev 5 Nov.11
73
Table A-1: Command availability by chipseta (Continued)

Command / Description
MDM6085 QSC6085
Set Mode NMEA on page 85 Start or stop the NMEA channel Get Mode NMEA on page 86 Query the current status of the NMEA channel Set Host Power State on page 87 Indicate the current power state of the host device Get TRU-Install Information on page 88 Indicate which software installation packages are stored on the module Set TRU-Install Mode on page 90 Request mode of operation (massstorage device or modem) Get Config Item on page 91 Set Config Item on page 93 Set Device Reset on page 95 Set Host Info on page 96
e e f g h
a. b. c. d. e. f. g. h.
For a list of devices using these chipsets, see Table 1-1 on page 15. MC devices only All devices except AC595/AC595U AC/USB devices only; not supported by MC/SL devices MDM9200 - TRU-Install and SD only MDM9200 MDM6200, MDM8200, MDM8220, MDM9200 MDM6270/QSC6270, MDM8200A, MSM6290
In boot-and-hold mode, only the following commands are supported: CDMA devices: Get Attributes on page 83 GSM / UMTS devices: Get Mode MUX on page 79 Set Mode MUX on page 77 Get NDIS Support on page 81 Get NDIS Preference on page 82 Get Attributes on page 83 Proprietary and Confidential 2130634
Note: There are no commands available in boot-and-hold mode for UMTS devices using Direct IP VID/PID.
74
Vendor-specific commands
Set Device Power State

Power the modem on or off. Stages: SetupHost tells modem to power on or off. Status(IN)Modem indicates completion of requested operation.
Setup stage
Direction: Host to modem Purpose: Tell modem to power on or off. Details: The following table describes the outgoing packet structure.
Table A-2: Set Device Power State Setup stage

Offset 0 1 2 Size (bytes) 1 1 2 Field Request type Request Value Value 0x40 0x00 State 0x0000 (D0 state, modem power on)
4 6 2 2 Index Length
0x0003 (D3 state, modem power off)
0x0000 0x0000
Status stage (IN)

Direction: Modem to host Purpose: Notify host that the requested operation has completed. Details: Modem returns a zero-length packet when the requested operation has completed.
Rev 5 Nov.11
75
Set Mode Non-MUX

Tear down the 27.010 MUX protocol on a selected channel. Stages: SetupHost tells modem to use non-MUX protocol on a specific channel. Status (IN)Modem indicates completion of requested operation.
Setup stage
Direction: Host to modem Purpose: Tell modem to use non-MUX protocol on a specific channel. Details: The following table describes the outgoing packet structure.
Table A-3: Set Mode Non-MUX Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0x40 0x01 0x0000 (not used) Channel selection 0x0000 Data

6 2 Length
0x0001 Control 0x0002 NMEA
0x0000 (not used)
Status stage (IN)

76
2130634
Set Mode MUX

Set up the 27.010 MUX protocol on a selected channel. Stages: SetupHost tells modem to use MUX protocol on a specific channel. Data (OUT)Host indicates MUX parameters to be used. Status (IN)Modem indicates completion of requested operation.
Note: The modem moves from Non-MUX mode to Transition mode when it receives the Set Mode MUX request. The modem then moves from Transition mode to MUX mode when it is ready to receive MUX (27.010) framed messages on the requested interface.
Setup stage
Direction: Host to modem Purpose: Tell modem to use MUX protocol on a specific channel. Details: The following table describes the outgoing packet structure.
Table A-4: Set Mode MUX Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0x40 0x02 0x0000 (not used) Channel selection 0x0000 Data

6 2 Length
0x0001 Control (Places all CDMA devices into Hybrid-MUX mode.) 0x0002 NMEA
0x0012 (length of data in Data stage)
Data stage (OUT)

Direction: Host to modem Purpose: Indicate MUX mode parameters. Details: The following table describes the outgoing packet structure.
Rev 5 Nov.11
77
Table A-5: Set Mode MUX Data stage (OUT)

Offset 0 2 4 6 8 10 12 14 16 Size (bytes) 2 2 2 2 2 2 2 2 2 Field Mode Frame type Port speed Maximum frame size ACK timer Maximum number of retransmissions Response timer Wakeup timer Window size Value See Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release 6)
Status stage (IN)

78
2130634
Get Mode MUX

Request the current 27.010 MUX protocol status of a specific channel. Stages: SetupHost tells modem to report the status of a specific channel. Data (IN)Modem indicates the channels current protocol status. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report the status of a specific channel. Details: The following table describes the outgoing packet structure.
Table A-6: Get Mode MUX Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0xC0 0x03 0x0000 (not used) Channel selection 0x0000 Data

6 2 Length
0x0001 Control (For CDMA devices, this indicates hybrid-MUX mode.) 0x0002 NMEA
0x0002 (length of data in Data stage)
Data stage (IN)

Direction: Modem to host Purpose: Indicate the requested channels current 27.010 MUX protocol status. Details: The following table describes the incoming packet structure.
Table A-7: Get Mode MUX Data stage (IN)

Offset 0 Size (bytes) 2 Field Mode Value Mode 0x0000 Init
0x0001 Non-MUX 0x0002 Transition 0x0003 MUX
Rev 5 Nov.11
79
Status stage (OUT)

Direction: Host to modem Purpose: Notify modem that the Data stage was received. Details: Host sends a zero-length packet after receiving the Data stage.
80
2130634
Get NDIS Support

Request that the modem indicate if the NDIS driver is supported. Stages: SetupHost tells modem to report NDIS support status. Data (IN)Modem indicates whether the NDIS driver is supported. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report whether the NDIS driver is supported. Details: The following table describes the outgoing packet structure.
Table A-8: Get NDIS Support Setup stage

Offset 0 1 2 4 6 Size (bytes) 1 1 2 2 2 Field Request type Request Value Index Length Value 0xC0 0x04 0x0000 (not used) 0x0000 (not used) 0x0002 (length of data in Data stage)
Data stage (IN)

Direction: Modem to host Purpose: Indicate whether the NDIS driver is supported. Details: The following table describes the incoming packet structure.
Table A-9: Get NDIS Support Data stage (IN)

Offset 0 Size (bytes) 2 Field Supported Value NDIS support 0x0000 Not supported
0x0001 Supported 0x00FF Unknown (keep polling, modem not ready to respond)
Status stage (OUT)

Direction: Host to modem Purpose: Notify modem that the Data stage was received. Details: Host sends a zero-length packet after receiving the Data stage. Rev 5 Nov.11 Proprietary and Confidential 81
Get NDIS Preference

Request that the modem indicate whether or not the NDIS interface is supported. Stages: SetupHost tells modem to report whether the NDIS interface is supported. Data (IN)Modem indicates whether the NDIS interface is supported. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report whether the NDIS interface is supported. Details: The following table describes the outgoing packet structure.
Table A-10: Get NDIS Preference Setup stage

Data stage (IN)

Direction: Modem to host Purpose: Indicate whether the NDIS interface is supported. Details: The following table describes the incoming packet structure.
Table A-11: Get NDIS Preference Data stage (IN)

Offset 0 Size (bytes) 2 Field Preference Value NDIS preferred 0x0000 Not preferred
0x0001 Preferred 0x00FF Unknown (keep polling, modem not ready to respond)
Status stage (OUT)

Direction: Host to modem Purpose: Notify modem that the Data stage was received. Details: Host sends a zero-length packet after receiving the Data stage. 82 Proprietary and Confidential 2130634
Get Attributes
Request that the modem return firmware image attributes. Stages: SetupHost tells modem to report firmware attributes. Data (IN)Modem reports firmware attributes. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report firmware attributes. Details: The following table describes the outgoing packet structure.
Table A-12: Get Attributes Setup stage

Offset 0 1 2 4 6 Size (bytes) 1 1 2 2 2 Field Request type Request Value Index Length Value 0xC0 0x06 0x0000 (not used) 0x0000 (not used) 0x0002 (Length of data in Data stage)
Data stage (IN)

Direction: Modem to host Purpose: Report the firmware images attributes. Details: The following table describes the incoming packet structure.
Rev 5 Nov.11
83
Table A-13: Get Attributes Data stage (IN)

Offset 0 Size (bytes) 2 Field Attributes Value 16-bit field with each bit representing an attribute of the firmware image Bit 0 (Running image type) 0 = Boot 1 = Application
Bit 1 (Advanced Power Management support) 0 = Not supported by firmware 1 = Supported by firmware Bit 2 (27.010 Flow Control Available)this value is only meaningful when module is operating in MUX mode. 0 = Not available 1 = Available Bit 3-15: Unused (default value = 0)
Status stage (OUT)

84
2130634
Set Mode NMEA

Start or stop the NMEA data stream over the endpoint used for the NMEA channel. Stages: SetupHost tells modem to start or stop the stream. Status (IN)Modem indicates completion of requested operation.
Setup stage
Direction: Host to modem Purpose: Tell modem to start or stop the NMEA data stream. Details: The following table describes the outgoing packet structure.
Table A-14: Set Mode NMEA Setup stage

Offset 0 1 2 Size (bytes) 1 1 2 Field Request type Request Value Value 0x40 0x07 NMEA mode 0x0000 Stop
0x0001 Start
0x0000 (not used) 0x0000 (not used)
Status stage (IN)

Rev 5 Nov.11
85
Get Mode NMEA

Request that the modem indicate if NMEA streaming is stopped or started. Stages: SetupHost tells modem to report whether NMEA streaming is stopped or started. Data (IN)Modem indicates the current status of NMEA streaming. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report whether NMEA streaming is stopped or started. Details: The following table describes the outgoing packet structure.
Table A-15: Get Mode NMEA Setup stage

Data stage (IN)

Direction: Modem to host Purpose: Indicate the current status of NMEA streaming. Details: The following table describes the incoming packet structure.
Table A-16: Get Mode NMEA Data stage (IN)

Offset 0 Size (bytes) 2 Field Mode Value NMEA mode 0x0000 Stopped
0x0001 Started
Status stage (OUT)

Direction: Host to modem Purpose: Notify modem that the Data stage was received. Details: Host sends a zero-length packet after receiving the Data stage. 86 Proprietary and Confidential 2130634
Set Host Power State

Notify the modem of the current power state of the host device. Stages: SetupHost tells modem whether the host is awake or suspended. Status (IN)Modem indicates that it received the power state information.
Setup stage
Direction: Host to modem Purpose: Tell modem whether the host is awake or suspended. Details: The following table describes the outgoing packet structure.
Table A-17: Set Host Power State Setup stage

Offset 0 1 2 Size (bytes) 1 1 2 Field Request type Request Value Value 0x40 0x09 State 0x0000 Host device is awake
0x0001 Host device is suspended
0x0000 (not used) 0x0000 (not used)
Status stage (IN)

Direction: Modem to host Purpose: Notify host that the power state information was received. Details: Modem returns a zero-length packet after it receives the information from the host.
Rev 5 Nov.11
87
Get TRU-Install Information

Request that the modem indicate which installation packages are stored on a TRU-Install enabled device. When the host receives this information, it can determine whether to fully enumerate the device as a mass-storage device to load the installation package, or to re-enumerate as a modem because the package has already been loaded. Stages: SetupHost tells modem to report installation package information. Data (IN)Modem returns the first portion of the CWE header, which indicates the installation package types. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to report installation package information. Details: The following table describes the outgoing packet structure.
Table A-18: Get TRU-Install Information Setup stage

Offset 0 1 2 4 6 Size (bytes) 1 1 2 2 2 Field Request type Request Value Index Length Value 0xC0 0x0A 0x0000 (not used) 0x0000 (not used) 0x003C (length of data in Data stage)
Data stage (IN)

Direction: Modem to host Purpose: Return the first portion of the CWE header, which indicates the installation package types. Details: The following table describes the incoming packet structure.
88
2130634
Table A-19: Get TRU-Install Information Data stage (IN)

Offset 0 Size (bytes) 60 Field Version Value CWE Header, first 60 bytes Byte 0: Revision number
Windows package details Bytes 12: Product code Bytes 34:Version Mac package details Bytes 56: Product code Bytes 78:Version Bytes 959: Reserved
Status stage (OUT)

Rev 5 Nov.11
89
Set TRU-Install Mode

(TRU-Install enabled modems only) Request that the device enumerate as a mass storage device (to install software) or as a modem (for normal use).
Note: The command is ignored if the modem does not support TRU-Install, or if it is in a state where the requested mode is not allowed (for example, boot-and-hold mode).
Stages: SetupHost tells modem how it should enumerate. Status (IN)Modem indicates completion of requested operation.
Setup stage
Direction: Host to modem Purpose: Tell modem how to enumerate. Details: The following table describes the outgoing packet structure.
Table A-20: Set TRU-Install Mode Setup stage

Offset 0 1 2 Size (bytes) 1 1 2 Field Request type Request Value Value 0x40 0x0B TRU-Install mode requested 0x0000 Mass storage

0x0001 Modem 0x0002 Reserved
0x0000 (not used) 0x0000 (length of data in Data stage)
Status stage (IN)

90
2130634
Get Config Item

Request that the modem indicate whether a specific configuration item is supported or enabled. Stages: SetupHost tells modem to indicate whether a specific configuration item is supported or enabled. Data (IN)Modem indicates support/enable status of requested configuration item. Status (OUT)Host indicates that it received the Data stage information.
Setup stage
Direction: Host to modem Purpose: Tell modem to return the status of a specific configuration item. Details: The following table describes the outgoing package structure.
Table A-21: Get Config Item Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0xC0 0x0C 0x0000 Configuration item requesteda: 0x0000TRU-Install

6 2 Length
0x0001SD 0x0002NDIS (Windows only) 0x0003AutoConnect
VariableMaximum length of data stage that the host expects to receive 0x0400 (1024 bytes) maximum
a. Availability of specific configuration item types is device/SKU-dependent.
Data stage (IN)

Direction: Modem to host Purpose: Return the status of the specified configuration item. Details: The following table describes the incoming packet structure.
Rev 5 Nov.11
91
Table A-22: Get Config Item Data stage (IN)

Offset 0 Size (bytes) Variable (minimum 2 bytes) Field Configuration information Value Data is dependent on configuration item requested. See Table A-23 for details.
Table A-23: Configuration information details

Configuration item Index 0x0000 Name TRU-Install 0 2 Supported Offset Size (bytes) Field Value
0x0000Not supported 0x0001Supported 0x0000Disabled 0x0001Enabled 0x0000Not supported 0x0001Supported 0x0000Disabled 0x0001Enabled 0x0000Not supported 0x0001Supported 0x0000Disabled 0x0001Enabled 0x0000Not supported 0x0001Supported 0x0000Disabled 0x0001Enabled
Enabled
0x0001
SD
Supported
Enabled
0x0002
NDIS
Supported
Enabled
0x0003
AutoConnect
Supported
Enabled
Status stage (OUT)

92
2130634
Set Config Item

Configure a specific configuration item.
Note: The device must be reset for any configuration changes to take effect. (Use Set Device Reset on page 95.)
Stages: SetupHost tells module which items will be configured. Data (Out)Host tells module to enable / disable specific configuration items. Status (In)Module indicates that the request has completed.
Setup stage
Direction: Host to module Purpose: Tell modem to set the characteristics of a specific configuration item. Details: The following table describes the outgoing package structure.
Table A-24: Set Config Item Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0x40 0x0D 0x0000 Configuration item requesteda: 0x0000TRU-Install

6 2 Length
0x0001SD 0x0002NDIS (Windows only) 0x0003AutoConnect
Length of the Data stage (OUT). The length is dependent on the configuration item requested.
a. Availability of specific configuration item types is device/SKU-dependent.
Data stage
Direction: Host to module Purpose: Indicate new details for a specific configuration item. Details: The following table describes the outgoing package structure.
Rev 5 Nov.11
93
Table A-25: Set Config Item Data stage (OUT)

Offset 0 Size (bytes) Variable (minimum 2 bytes) Field Configuration information Value Data is dependent on configuration item requested. See Table A-23 for details.
Table A-26: Configuration information details

Configuration item Index 0x0000 Name TRU-Install 0 2 Enable state Offset Size (bytes) Field Value
0x0000Disable 0x0001Enable 0x0000Disable 0x0001Enable 0x0000Disable 0x0001Enable 0x0000Disable 0x0001Enable
0x0001
SD
Enable state
0x0002
NDIS
Enable state
0x0003
AutoConnect
Enable state
Status stage (IN)

Direction: Module to host Purpose: Notify host that the requested operation has completed. Details: Module sends a zero-length packet when the requested operation has completed.
94
2130634
Set Device Reset

Tell the modem to reset.
Note: This command must be issued after using Set Config Item on page 93 so that new settings will take effect.
Stages: SetupHost tells modem to reset. Status (In)Modem indicates that device has been reset.
Setup stage
Direction: Host to modem Purpose: Tell modem to reset so that it will enumerate with new configuration settings. Details: The following table describes the outgoing packet structure.
Table A-27: Set Device Reset Setup stage

Offset 0 1 2 4 6 Size (bytes) 1 1 2 2 2 Field Request type Request Value Index Length Value 0x40 0x0E 0x0000 0x0000 0x0000
Status stage (IN)

Direction: Modem to host Purpose: Notify host that the device has been reset. Details: Modem returns a zero-length packet after the device resets.
Rev 5 Nov.11
95
Set Host Info

Tell the module details about the host configuration. Stages: SetupHost indicates which configuration information is being sent to the modem. Data (Out)Host sends the configuration details. Status (In)Modem indicates that requested operation has completed.
Setup stage
Direction: Host to modem Purpose: Tell modem which host configuration details are being identified. Details: The following table describes the outgoing packet structure.
Table A-28: Set Host Info Setup stage

Offset 0 1 2 4 Size (bytes) 1 1 2 2 Field Request type Request Value Index Value 0x40 0x0F 0x0000 Configuration type 0x0000Feature configuration

6 2 Length
0x0001Host type 0x0002Service pack version 0x0003Host and system up time 0x0004Reserved
Length of Data stage (OUT)
Data stage (Out)

Direction: Host to modem Purpose: Indicate details about identified configuration type. Details: The following table describes the outgoing packet structure.
Table A-29: Set Host Info Data stage (OUT)

Offset 0 Size (bytes) Variable Field Configuration information Value Data is dependent on configuration item requested. See Table A-23 for details.
96
2130634
Table A-30: Configuration information Feature Configuration

Offset 0 Size (bytes) 2 Bit 0 Field Feature bitmap NMEA listening Value
0(Default) Host does not listen to the NMEA port 1Host listens to the NMEA port 0Host does not require !RESET restart indication 1Host requires !RESET restart indication Not used
Bit 1
Restart indication
Bit2-15
Reserved
Table A-31: Configuration information Host Type

Offset 0 Size (bytes) 1 Field OS type Value
0x00Windows 0x01Linux 0x02Windows CE 0x03Windows Mobile 0x04Mac 0xFFOther/unknown Windows
OS version
Rev 5 Nov.11 Proprietary and Confidential
0x40Windows NT 4.0 0x50Windows 2000 0x51Windows XP 0x60Windows Vista 0x61Windows 7 0x30CE 3.0 0x40CE 4.0 0x50CE 5.0 0x60CE 6.0 0x30Mobile 2003 0x50Mobile 5.0 0x60Mobile 6.0 0x61Mobile 6.1 0x65Mobile 6.5 0x70Mobvile 7.0 0xFF
Windows CE
Windows Mobile
Linux/Mac/Other/Unknown
97
Table A-31: Configuration information Host Type (Continued)

Offset 2 Size (bytes) 1 Field Processor type Value
0x00x86 0x01x64 0x02MIPS 0x03ARM 0xFFOther
Reserved
Not used
Table A-32: Configuration information Service pack version

Offset 0 Size (bytes) 1 Field Service pack version Value
0x00Service pack 0 0x01Service pack 1 0x02Service pack 2 etc.
Table A-33: Configuration information Host and system up time

Offset 0 Size (bytes) 8 Field System up Time1 System up Time2 Value Number of seconds since the system was started. Shown in network byte order (big-endian) Windows 7 Number of seconds that the system has been awake since it was started.
Shown in network byte order (big-endian)
All other O/S: Reserved 16 2 Host time (Year) Host time (Month) Host time (Day) Host time (Hour) Host time (Minute) Host time (Second) Year Shown in network byte order (big-endian) Month (112) Day (131) Hour (023) Minute (059) Second (059)
18 19 20 21 22
1 1 1 1 1
98
2130634
Table A-33: Configuration information Host and system up time

Offset 23 Size (bytes) 1 Field Host time (Timezone) Value Offset from UTC (in 15 minute increments) Examples: -2 = UTC - 30 minutes

24 1 Host time (Daylight savings)
-1 = UTC - 15 minutes 0 = UTC 1 = UTC + 15 minutes 2 = UTC + 30 minutes
Time adjustment when daylight savings is in effect 0x00No adjustment
0x01Plus one hour 0x02Plus two hours
Status stage (IN)

Direction: Module to host Purpose: Notify host that the requested operation has completed. Details: Module sends a zero-length packet when the requested operation has completed.
Rev 5 Nov.11
99
100
2130634
B: Supported CDC USB commands

The devices described in this document support various CDC USB commands, requests, and class-specific notifications. The following tables describe the support provided by the devices. Message support status in these tables is represented by: Supported: Fully implemented on the indicated device. EEmpty: Blankly implementedthe modem responds to the request but doesnt actually perform it. Not supported: Not implemented at any level.
Table B-1: Supported commands / requests by chipseta

Request
Code
MDM6085 QSC6085
SEND_ENCAPSULATED_COMMAND GET_ENCAPSULATED_RESPONSE SET_COMM_FEATURE GET_COMM_FEATURE CLEAR_COMM_FEATURE SET_LINE_CODING
00h 01h 02h 03h 04h 20h
E E E E E
E E E E E
(ECM interface) (ECM interface)

E E E

(MDM9200) TBD TBD
(MDM9200)
GET_LINE_CODING
21h
(MDM9200)
SET_CONTROL_LINE_STATE
22h
(MDM9200) TBD
SEND_BREAK
23h
Rev 5 Nov.11
101
Table B-2: Supported class-specific notifications by chipseta

(Direct IP VID/PID) MDM6200 MDM6270 MDM8200 MDM8200A MDM8220 MDM9200 MSM6290 QSC6270 E
Request
Code
MDM6085 QSC6085
NETWORK_CONNECTION RESPONSE_AVAILABLE SERIAL_STATE CONNECTION_SPEED_CHANGE
00h 01h 20h 2Ah
TBD TBD TBD TBD
102
2130634
C: QUALCOMM DM Data Logging

This section provides guidelines for OEMs whose devices are running an operating system other than Windows and who need to implement DM logging capability (for carrier certification requirements or field troubleshooting) to support logging tools such as QUALCOMM's QXDM, Spirent's UDM, or Sierra Wireless' SwiLog Plus tool. The recommended setup is to implement a "pass-thru" of the modems DM interface to an external interface (on the non-Windows host device) connected to a Windows computer running a Windowsbased logging tool mentioned above. See the following figure.
Non-Windows device with embedded Sierra Wireless modem Sierra Wireless modem
DM interface
Windows computer running DM logging software
Embedded CPU
Pass-through of the modem's DM interface
Figure C-1: Recommended setup for logging QUALCOMM DM data
Handling DM for logging purposes

Note: This section applies only to modems that are configured to have DM messages pass over the HIP interfacefor example, when USB endpoint 4 is configured for CnS and QUALCOMM DM over HIP.
The host USB driver must handle the HIP encapsulation and deencapsulation of DM messages; for more information on encapsulation and on HIP in general, see the HIP Basics and HIP format chapters in the CDMA 1xEV-DO CnS Reference (Document 2130754).Your driver must do the following: 1. Using the Message ID, determine whether the message is a DM message. DM messages have a Message ID of: 0x2D (Modem Protocol Stack Indication), or 0x6D (Host Protocol Stack Indication) Perform the following step only if the message is a DM message. 2. If the message is from SWILOG (Message ID = 0x2D), encapsulate the message in a HIP packet, and transmit the packet to
Rev 5 Nov.11
103
the modem. If the message is to SWILOG (Message ID = 0x6D), remove the encapsulation data and pass the DM message to SWILOG.
Read the Message ID
Message ID = 0x2D or 0x6D?
No
End
(Not a DM message; do nothing)
Yes
Message ID = 0x2D?
No (i.e. Message ID = 0x6D - the message is to SwiLog)
Yes (the
message is from SwiLog)
Add HIP encapsulation
Remove the HIP encapsulation
Send the message to the modem
Send the DM message to SWILOG
Figure C-2: Handling of DM messages by your USB driver
Pass-thru application considerations

The following are general characteristics of the pass-thru application: It does not need to fragment the message into smaller HIP messages before passing it alongit simply passes the HIP packet, unchanged, from one device to the other. SWILOG uses 2 Kb buffers. The modems DM buffer has a finite size - if the buffers are not read and the buffer capacity is reached, the oldest packets are dropped, ensuring that the newest data is always available. This could occur if the majority of log items are enabled, particularly if a physical serial port is used as the interface. Typically, traffic from the host is sent in bursts.
104
2130634
D: Direct IP mode
This section describes issues pertaining to modems supporting Direct IP mode. See Direct IP on page 71 for a description of this service. For more detailed information about Direct IP mode, refer to the Direct IP Integration Guide (Document #2131327) (contact your Sierra Wireless representative).
Performance considerations
You can use the Direct IP interface on HSPA and HSPA+ networks. The following are performance considerations for both network types: Direct IP on HSPA+ networks Direct IP vs. PPPDirect IP throughput rates will be at least as high as PPP rates on HSPA+ networks. CPU usage may also be lower for Direct IP vs. PPP. Direct IP on HSPA networks Direct IP vs. PPPThere should be no significant difference in data rate between the two services. CPU usage may also be lower for Direct IP vs. PPP.
Direct IP drivers
To obtain and install Linux driver files providing Direct IP support for your modem, refer to the Linux SDK Integration Guide (Document #2131103) (contact your Sierra Wireless representative).
Direct IP interface
Direct IP is implemented using custom ECM (Ethernet Control Module) interfaces7, 10, and 11, depending on the devices default interface configuration, as described in Direct IP on page 71. As shown in Table 2-11 on page 48, the default Direct IP interface (DIP1, Interface 7) is implemented over three endpointsthe endpoint numbers are determined based on which interfaces are enumerated: Bulk IN and Bulk OUTThese endpoints are used to transfer data from the modem to the host (IN), and from the host to the modem (OUT). InterruptThis endpoint is used to notify the host of interface events.
Rev 5 Nov.11
105
Direct IP communication / session setup

Note: The modem must have at least one profile created before a connection can be made. Use AT!SCPROF (see AirCard/AirPrime UMTS Devices Supported AT Command Reference (Document 2130617)), AT+CGDCONT, and AT$QCPDPP (see AirPrime MC/ SL-series (UMTS/LTE) Extended AT Command Reference (Document 2130616)) to create and configure profiles.
To set up a Direct IP data session (start the connection):

Note: For a detailed explanation of HIP messaging and the Link Status Indication, refer to HIP Basics and Unsolicited HIP messages in the AirPrime UMTS MC and SL Series CnS Reference (Document 2130602).
Via ATUse AT!SCACT=1,<profile> where <profile> has the required APN. (1 activates the session, 0 terminates the session) Via CnSUse the CnS object Manage Packet Session (0x7004).
To receive a control message (such as a Link Status Indication or HIP Sync) from the modem: 1. Receive a notification indication over the Direct IP interfaces Interrupt endpoint. 2. Send a GET_ENCAPSULATED_RESPONSE request over the USB CDC command endpoint (endpoint 0). The modem returns the control message as the payload of the response. To send a control message (such as a HIP Sync) to the modem: 1. Send a SEND_ENCAPSULATED_COMMAND request over the USB CDC command endpoint (endpoint 0) with the control message as the payload of the request.
Examples
Host
(Interface 7) RESPONSE_AVAILABLE
Modem
Modem notifies host that control message is available, using the Direct IP interfaces Interrupt endpoint.
Host requests control message from modem.
(Endpoint 0) GET_ENCAPSULATED_RESPONSE
Modem replies with control message (HIP Link Status Indication) as payload of this command.
Figure D-1: Direct IPReceive Link Status Indication
106
2130634
Direct IP mode
Host
(Endpoint 0) SEND_ENCAPSULATED_COMMAND
Modem
Host sends HIP Sync command as payload of this command
Figure D-2: Direct IPHost/modem synchronization
Switching between PPP and Direct IP modes

This section applies to modems supporting both PPP and Direct IP modes. (See Table 1-1 on page 15 for devices with Direct IP and legacy PIDs.)
Switch a modem from PPP mode to Direct IP mode

1. Run AT!UDPID=68A3. (0x68A3 is the standard Direct IP PID. You can also use a carrier-specific Direct IP PID if appropriate.) 2. Reset the modem.
Switch a modem from Direct IP mode to PPP mode

1. Run AT!UDPID=<pid> where <pid> is the default PID used by the modem. (For example, 683C is the PID used for MC8790V modems.) 2. Reset the modem.
Note: To show the devices current PID, use AT!UDPID?. To show available PIDs, use AT!UDPID=?.
Configuring USB interface composition in Direct IP mode

To display or customize the set of interfaces presented by the modem in Direct IP mode, use the AT!UDUSBCOMP command: AT!UDUSBCOMP=? shows available interface configurations AT!UDUSBCOMP? shows the current configuration AT!UDUSBCOMP=<xx> sets the current configuration (<xx>). (You must reset the modem after changing the current configuration for the change to take effect.)
The modems default interface configuration is SKU-dependantsee UMTS devices (DIP VID/PID)Non-MUX descriptors on page 52 for lists of possible interfaces and typical interface configurations.
Rev 5 Nov.11
107
108
2130634
E: QMI
This section applies to modems supporting both QMI and Direct IP modes. (See Table 1-1 on page 15 for devices with QMI and Direct IP PIDs.) For more detailed information about QMI mode, refer to QMI (NET interface) on page 72, and the Linux QMI SDK Application Developers Guide (contact your Sierra Wireless representative).
QMI drivers
To obtain and install Linux serial and network driver files providing QMI support for your modem, refer to the Linux QMI SDK Application Developers Guide.
QMI interface
As shown in Table 2-22 on page 59, the QMI interface (NET, Interface 8) is implemented over three endpoints: Bulk (6-IN and 4-OUT) These endpoints are used to transfer data from the modem to the host (IN), and from the host to the modem (OUT). Interrupt (5-IN)This endpoint is used to notify the host of interface events.
QMI communication / session setup

QMI data sessions are set up and managed using API functions available in the QMI SDKAT messages are not used for this purpose. For details on identifying and using QMI API functions for managing data data sessions, refer to the Linux QMI SDK Application Developers Guide.
Switching between QMI and Direct IP modes

Switch a modem from QMI mode to Direct IP mode
1. Run AT!UDPID=68A3. (0x68A3 is the standard Direct IP PID. You can also use a carrier-specific Direct IP PID if appropriate.) 2. Reset the modem. Rev 5 Nov.11 Proprietary and Confidential 109
Switch a modem from Direct IP mode to QMI mode

1. Run AT!UDPID=68A2 (0x68A2 is the QMI PID.) 2. Reset the modem.
Note: To show the devices current PID, use AT!UDPID?. To show available PIDs, use AT!UDPID=?.
Configuring USB interface composition in QMI mode

To display or customize the set of interfaces presented by the modem in QMI mode, use the AT!UDUSBCOMP command: AT!UDUSBCOMP=? shows available interface configurations AT!UDUSBCOMP? shows the current configuration AT!UDUSBCOMP=<xx> sets the current configuration (<xx>). (You must reset the modem after changing the current configuration for the change to take effect.)
The modems default interface configuration is SKU-dependantsee UMTS devices (QMI VID/PID) non-MUX descriptors on page 61 for lists of possible interfaces and typical interface configurations.
110
2130634
F: User-developed USB Drivers

User-developed drivers
This section applies to developers who are creating their own drivers for Sierra Wireless MC- and SL-series embedded modules.
Handshaking
The host must act as a USB host device to interface with the module. The module uses the USB standard Suspend and Resume functions to control sleep and wakeup states. For details, refer to Universal Serial Bus Specification, Rev 2.0.
Suspend
The module supports USB Selective Suspend mode. When the module enters suspend mode, it shuts down the USB clock to save power. While in the suspend state: The module provides power to the D+/- interface to signal its current state to the host device. The host must maintain input voltage (VCC)
Refer to Universal Serial Bus Specification, Rev 2.0 for critical timing parameters for the suspend state.
Resume
USB activity may be resumed by either the USB host or by the module. If the host initiates USB activity: 1. USB transceiver detects the change in bus activity and triggers the USB_RESUME interrupt to the module's processor. 2. Module enables its USB clock and responds to the host. If the module initiates USB communication (Remote Wakeup): 1. Module enables its USB clock. 2. Module enables the USB transceiver. 3. Module sends the resume signal for at least 20 ms. Refer to Universal Serial Bus Specification, Rev 2.0 for critical timing parameters for the resume state.
Rev 5 Nov.11
111
Host USB driver requirements

The USB driver on the host device must meet these critical requirements: The host USB driver must support remote wakeup, resume, and suspend operations as described in Universal Serial Bus Specification, Rev 2.0. The host USB driver must support serial port emulation. The module implements both 27.010 multiplexing and USB-CDC.
When the host doesnt have any valid data to send, the host USB driver should NOT send any SOF tokens (start-of-frames) to the module. These tokens keep the module awake and cause unnecessary power consumption.
112
2130634
Index
Symbols
%%Get TRU-Install Information, 95 data stream, NMEA query status, 86 start or stop, 85 debugging, 68 device power state, 75 Diagnostic Monitoring (QUALCOMM DM), 68, 103 Direct IP control message, receive, 106 control message, send, 106 data session, setup, 106 description, 105 drivers, 105 HIP sync, process, 107 interface, endpoints, 105, 109 Link Status Indication, process, 106 DLCI control channel assignments, hybrid-MUX mode MDM6085, 30 MSM6800, 30 MSM6800A, 30 QSC6085, 30 DLCI control channel assignments, MUX mode MDM6085, 28 MSM6800, 28 MSM6800A, 28 QSC6085, 28 DM (QUALCOMM Diagnostic Monitoring), 68, 103 documents, reference, 18 driver architecture, supported, 20 DM data, handling, 103 NDIS enabled or disabled, 82 supported or not, 81 drivers, CDC-ACM, 19
Numerics
27.010 MUX protocol query (Get), 79 set up, 77 tear down, 76
A
Access Point Name (APN), 70 advanced power management, 19, 84 APN (Access Point Name), 70 architecture, supported driver, 20 architecture, USB, 19 AT commands, 66 AT/PPP data channel, 66
B
boot-and-hold mode supported commands, 74
C
CDC USB commands, 101 CDC-ACM drivers, 19 class-specific notifications, 102 CLEAR_COMM_FEATURE command, 101 CnS (Control and Status), 67 commands CDC USB, 101 vendor-specific, 73 Communication Interface Class, 65 configuration items, get, 91 configuration items, set, 93 CONNECTION_SPEED_CHANGE notification, 102 Control and Status (CnS), 67 control channel, standard, 65
E
endpoints, hybrid-MUX mode MDM6085, 30 MSM6800, 30 MSM6800A, 30 QSC6085, 30 endpoints, MUX mode MSM6800, 28 MSM6800A, 28 QSC6085, 28 endpoints, non-MUX mode MDM6085, 23 QSC6085, 23 endpoints, USB overview, 19
D
Data 1, Data 2, Data 3 data channels, 70 data channel AT/PPP, 66 Data 1, Data 2, Data 3, 70 DM, 68 HIP (Host Interface Protocol), 67 NMEA, 69
F
firmware image attributes, 83 full-speed standard, compliance, 19
Rev 5 Nov.11
113
Document SubTitle
G
Get Config Item, 91 Get Mode MUX, 79 Get Mode NMEA, 86 Get NDIS Preference, 82 Get NDIS Support, 81 Get TRU-Install Information, 88 GET_COMM_FEATURE command, 101 GET_ENCAPSULATED_RESPONSE command, 101 GET_LINE_CODING command, 101 GPS, 69
H
handshaking USB, 111 Heatherington escape method, 66 high-speed standard, compliance, 19 HIP (Host Interface Protocol) data channel, 67 description, 67 Host Interface Protocol (HIP) data channel, 67 description, 67 host power state set, 87 hybrid-MUX mode, endpoints, 30
I
interrupt channels, 65
L
LBS (Location-Based Services), 69 Location-Based Services (LBS), 69 logging of QUALCOMM DM Data, 103 logical protocols, 65 low-speed standard, compliance, 19
MDM6270 USB descriptors legacy VID/PID, 36, 61 MDM8200 USB descriptors, 52 63 modem power state, 75 MSM6200 USB descriptors legacy VID/PID, 36, 61 MSM6290 USB descriptors legacy VID/PID, 36, 61 TRU-Install mode, 42 MSM6290 (DIP VID/PID) USB descriptors, 52 63 MSM6800 DLCI control channel assignments hybrid-MUX mode, 30 MUX mode, 28 endpoints hybrid-MUX mode, 30 MUX mode, 28 MSM6800A DLCI control channel assignments hybrid-MUX mode, 30 MUX mode, 28 endpoints hybrid-MUX mode, 30 MUX mode, 28 MSM7200A USB descriptors TRU-Install mode, 42 MSM7201A USB descriptors TRU-Install mode, 42 MUX mode activating/deactivating, 21 get, 79 set, 77 MUX protocol, 27.010 query (Get), 79 set up, 77 tear down, 76
M
Mac package details (TRU-Install), 89 management element, 65 mass storage device, 71 See also TRU-Install. MDM6085 DLCI control channel assignments hybrid-MUX mode, 30 MUX mode, 28 endpoints hybrid-MUX mode, 30 MUX mode, 28 non-MUX mode, 23 USB descriptors, 25
N
National Marine Electronics Association (NMEA) data stream query status, 86 start or stop, 85 description, 69 NDIS preference, 82 supported or not, 81 NETWORK_CONNECTION notification, 102
114
2130634
Index
NMEA (National Marine Electronics Association) data stream query status, 86 start or stop, 85 description, 69 non-MUX mode endpoints MDM6085, 23 MDM6270, 33 Mdm6270, 59 MDM8200 (DIP VID/PID), 49 MSM6200, 33, 59 MSM6290, 33, 59 MSM6290 (DIP VID/PID), 49 QSC6085, 23 QSC6270, 33, 59 set, 76 notification elements, 65 notifications, class-specific, 102
QSC6270 USB descriptors legacy VID/PID, 36, 61 QUALCOMM Diagnostic Monitoring (DM), 68, 103 quality of service (QoS), 70 QXDM, 103
R
reference documents, 18 RESPONSE_AVAILABLE notification, 102 resume mode, USB, 111
S
SEND_BREAK command, 101 SEND_ENCAPSULATED_COMMAND command, 101 SERIAL_STATE notification, 102 services, 65 Set Config Item, 93 Set Device Power State, 75 Set Host Information, 96 Set Host Power State, 87 Set Mode MUX, 77 Set Mode NMEA, 85 Set Mode Non-MUX, 76 Set TRU-Install Mode, 90 SET_COMM_FEATURE command, 101 SET_CONTROL_LINE_STATE command, 101 SET_LINE_CODING command, 101 Spirents UDM, 103 stack, wireless protocol, 68 standard control channel, 65 standards compliance, USB, 19 suspend mode, USB, 111 SwiLog Plus, 103
P
package details (TRU-Install), 89 power modem on/off, 75 power state host, set, 87 modem, set, 75 PPP Data 1, Data 2, Data 3 data channels, 70 data channel, 66 protocol 27.010 MUX query (Get), 79 set up, 77 tear down, 76 HIP (Host Interface Protocol). See HIP (Host Interface Protocol). logical, 65 protocol stack, wireless, 68
Q
QMI data session, setup, 109 description, 109 drivers, 109 QoS (quality of service), 70 QSC6085 DLCI control channel assignments hybrid-MUX mode, 30 MUX mode, 28 endpoints hybrid-MUX mode, 30 MUX mode, 28 non-MUX mode, 23 USB descriptors, 25
T
TCP/IP, 66 TIES, 66 TRU-Install endpoints used, 71 query, 88, 95 set mode, 90
U
UDM (Spirent), 103 USB handshaking, 111 host driver requirements, 112 resume mode, 111 suspend mode, 111 user-developed drivers, 111
Rev 5 Nov.11
115
Document SubTitle
USB commands, CDC, 101 USB descriptors MDM6085, 25 MDM6200 legacy VID/PID, 36, 61 MDM6270 legacy VID/PID, 36, 61 MDM8200, 52 63 MSM6290 legacy VID/PID, 36, 61 TRU-Install mode, 42 MSM6290 (DIP VID/PID), 52 63 MSM7200A TRU-Install mode, 42 MSM7201A TRU-Install mode, 42 QSC6085, 25 QSC6270 legacy VID/PID, 36, 61
V
vendor-specific commands, 73
W
Windows package details (TRU-Install), 89 wireless protocol stack, 68
116
2130634

USB Driver Developers Guide Rev 5

Uploaded by

Copyright:

Available Formats

USB Driver Developers Guide Rev 5

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

USB Driver Developers Guide Rev 5

Uploaded by

Copyright:

Available Formats

AirCard/AirPrime USB Driver Developers Guide

Safety and Hazards

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Phone: Hours: E-mail:

1-604-232-1488 8:00 AM to 5:00 PM Pacific Time [email protected]

Proprietary and Confidential

Revision number 1.5

Release date Feb 2008

Apr 2008 Sep 2008

Sep 2008 Feb 2009

May 2009 Jul 2009

June 2011 November 2011

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Proprietary and Confidential

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Proprietary and Confidential

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Proprietary and Confidential

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Proprietary and Confidential

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Proprietary and Confidential

AC318U AC326U MC8704 MC8705

AC312U AC319U MC8801

AC313U AC320U MC7700 MC7710

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Table 1-1: Supported devices (by QUALCOMM chipset) a (Continued)

Proprietary and Confidential

Purpose of this guide

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

CDMA SL501x AT Command Reference (Document 4110801)

Extended AT Command Reference (Document 2130621)

This specification can be downloaded from www.usb.org.

Proprietary and Confidential

USB standards compliance

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

Supported driver architectures

Default operating mode

Proprietary and Confidential

Activating / Deactivating MUX mode

MDM6200 MDM6270 MSM6290 c QSC6270 c

AirCard/AirPrime USB architectures

Each service type enabled over specific endpoints

Proprietary and Confidential

AirCard / AirPrime USB Driver Developers Guide

CDMA module-specific USB architectures

Proprietary and Confidential

CDMA devicesNon-MUX architecture

2 IN / OUT (Bulk) 4 IN / OUT (Bulk)

5 IN / OUT (Bulk) 8 IN / OUT (Bulk)

Proprietary and Confidential