Direct IP. Direct IP Integration Guide Rev 1.0 Distribution under NDA only

Transcription

1 Direct IP Direct IP Integration Guide Rev 1.0 Distribution under NDA only

2

3 Preface Important Notice Safety and Hazards 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. 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 Rev 1.0 Review B 10 Jan Distribution under NDA only 3

4 Direct IP Integration Guide 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. Copyright Trademarks Contact Information 2010 Sierra Wireless. All rights reserved. AirCard and Heart of the Wireless Machine are registered trademarks of Sierra Wireless. Watcher is a trademark of Sierra Wireless, registered in the European Community. Sierra Wireless, the Sierra Wireless logo, the red wave design, and the red tipped antenna are trademarks of Sierra Wireless. Windows is a registered trademark of Microsoft Corporation. QUALCOMM is a registered trademark of QUALCOMM Incorporated. Used under license. Other trademarks are the property of their respective owners. Sales Desk: Phone: Post: Hours: Sierra Wireless Wireless Way Richmond, BC Canada V6V 3A4 Fax: Web: 8:00 AM to 5:00 PM Pacific Time sales@sierrawireless.com Consult our website for up to date product descriptions, documentation, application notes, firmware upgrades, troubleshooting tips, and press releases: 4 Distribution under NDA only

5 Preface Revision History Revision number Release date Changes 1.0 Jan 2010 Created document Rev 1.0 Review B 10 Jan Distribution under NDA only 5

6 Direct IP Integration Guide 6 Distribution under NDA only

7 Table of Contents Direct IP Introduction Document structure USB Architecture Direct IP USB Architecture Managing device configurations Customizing configurations USB descriptors Host Device Communication Message types Control messages Data messages Host device interactions Synchronization Device Reset System (host) Shutdown Data transfer Direct IP Data Sessions Manage profiles (PDP contexts) Enable/disable auto-connect Activate/terminate data sessions Device Operation Driver and host device messages Direct IP driver Rev Jan Distribution under NDA only 7

8 Direct IP Integration Guide Direct IP HIP message format Direct IP control and data messages Restart Indication WWAN RSSI Indication WWAN RSSI Registration response Link Status Indication Distribution under NDA only

9 1: Direct IP Introduction The Direct IP network interface allows applications to communicate directly with Sierra Wireless devices. (In Linux systems, this is done via the Sierra Wireless Direct IP network driver sierra_net.) On HSPA and HSPA+ networks, use of the Direct IP interface achieves high throughput rates and improves CPU efficiency by transporting IP packets over USB without using PPP. This guide describes essential integration information for host driver developers; additional Direct IP related information is included in the documents listed in Table 1 1, below. 1 Note: Throughout this guide, reference is made to Sierra Wireless Linux drivers sierra and sierra_net. For other operating systems, use the information in this document to aid in the development of your own drivers. Contact your Sierra Wireless account representative for instructions on obtaining the document suite appropriate for your device from Table 1-1: Direct IP-related documents Reference Doc Number Title Direct IP-related details [R-1] Mini Card/AirCard/Compass USB Driver Developer s Guide Direct IP USB architecture and descriptors, session setup, communication [R-2] Linux SDK Integration Guide Driver installation, and connection setup/teardown [R-3] UMTS Linux SDK Developer s Guide Direct IP driver in relation to software architecture [R-4] MC87xx Modem CnS Reference HIP and CnS messages [R-5] MC87xx Modem Extended AT Command Reference [R-6] UMTS Modems Supported AT Command Reference AT commands referenced in this document AT commands referenced in this document [R-7] GPP AT Command Set for User Equipment AT commands referenced in this document Rev Jan Distribution under NDA only 9

10 Direct IP Integration Guide Document structure This guide discusses the following key integration information: USB Architecture, page 11 Host Device Communication, page 17 Direct IP Data Sessions, page 21 Device Operation, page Distribution under NDA only

11 2: USB Architecture 2 Direct IP USB Architecture Sierra Wireless devices support several interface configurations (as detailed in Table 2 2 on page 13). The USB architecture for the default Direct IP configuration (configuration 3) is shown in Figure 2 1. This figure displays the USB interfaces used for each service available on the device. For a list of all possible interfaces, see Table 2 1 on page 12. Detailed information about the Direct IP USB architecture is available in the Mini Card/AirCard/Compass USB Driver Developer s Guide [R 1]. As shown in Figure 2 1, applications using CnS, QXDM, GPS, AT commands, and PPP clients communicate with the device using a serial driver (for example, Sierra Wireless Linux driver sierra). Applications using the Direct IP network interface use a separate driver (for example, Sierra Wireless Linux driver sierra_net) to communicate with the device. For instructions on obtaining and installing the Sierra Wireless Linux drivers, refer to the Linux SDK Integration Guide or follow the instructions at app/answers/detail/a_id/641. For other operating systems, use the information in this document to aid in the development of your own drivers. Rev Jan Distribution under NDA only 11

12 Direct IP Integration Guide Figure 2-1: Direct IP USB architecture, default configuration (3) Table 2-1: USB interfaces Interface Endpoints 1 Function driver used Num Name Description Bulk IN Bulk OUT Interrupt over interface 0 HIP SWI data link protocol support for device/call management services OBEX 1 DM Diagnostic service OBEX 2 NMEA GPS service OBEX 3 AT Data services (AT commands or PDP context using IP/PPP) ACM 4 PDP1 PDP context using IP/PPP ACM 7 DIP1 PDP context using IP/HIP ECM 9 MS Mass storage 10 DIP2 PDP context using IP/HIP ECM 11 DIP3 PDP context using IP/HIP ECM 1. Endpoint assignments are identified in the USB interface descriptors, and vary depending on which interfaces are enabled. 12 Distribution under NDA only

13 Direct IP USB Architecture Table 2-2: Standard USB device configurations Supported interfaces Config ID 1 HIP DM 2 NMEA 2 AT PDP1 PDP2 PDP3 DIP1 DIP2 DIP3 MS Configuration ID 1 is deprecated and is no longer supported. 2. These interfaces can be enabled or disabled if desired. See Customizing configurations on page 13 for details. Managing device configurations Sierra Wireless devices support multiple device configurations (as shown in Table 2 2). To display supported configurations: 1. Use the command AT!UDUSBCOMP=?, which returns each configuration and indicates if they are supported. To display the current configuration: 1. Use the command AT!UDUSBCOMP?, which returns the current configuration ID. To switch the current configuration: 1. Use the command AT!USUSBCOMP=<new configurationid> to indicate the desired configuration. 2. Use the command AT!RESET to reset the device and have it use the requested configuration. Customizing configurations All configurations in Table 2 2 on page 13 support the NMEA, DM, and MS interfaces. These interfaces can be individually enabled or disabled using the following command (see Table 2 3 for parameter details): AT!CUSTOM = <customsetting>, <value> Table 2-3: Parameters for customizing configurations Parameter Value Description <value> 0 Disable the <customsetting> 1 Enable the <customsetting> Rev Jan Distribution under NDA only 13

14 Direct IP Integration Guide Table 2-3: Parameters for customizing configurations Parameter Value Description <customsetting> GPSENABLE Custom setting to include the NMEA interface (GPS service) USBDMDISABLE USBMSENABLE Custom setting to exclude the DM interface (Diagnostic service) Custom setting to include the mass storage interface Note: These customizations are used to change the default interfaces for a given configuration. For example, for GPSENABLE and USBMSENABLE, <value = 1> is used to include the interfaces. (Both interfaces are excluded by default.). For USBDMDISABLE, <value = 1> is used to exclude the DM interface, which is normally included by default. USB descriptors Descriptors for devices operating in Direct IP mode are detailed in the Mini Card/AirCard/Compass USB Driver Developer s Guide [R 1]. Examples of these descriptors include: Direct IP USB descriptor This descriptor (Table 2 4) is common to all Sierra Wireless devices operating in Direct IP mode. Table 2-4: Direct IP USB descriptor Field identifier Value bcdusb bdeviceclass bdevicesubclass bdeviceprotocol bmaxpacketsize0 idvendor idproduct bcddevice 0x0200 0x00 0x00 0x00 0x40 0x1199 0x68A3 (All Sierra Wireless devices use this product ID to indicate Direct IP support) 0x Distribution under NDA only

15 USB descriptors Table 2-4: Direct IP USB descriptor (Continued) Field identifier Value Interface descriptors During enumeration, one descriptor for each of the configuration s enabled interimanufacturer iproduct iserialnumber bnumconfigurations 0x03 0x02 0x00 0x01 Configuration descriptor One descriptor for each configuration in Table 2 2 on page 13. During enumeration, one of these descriptors is sent to the host, identifying the current configuration. The descriptor indicates the number of interfaces enumerated for that configuration. (As described in Customizing configurations on page 13, some interfaces may be specifically enabled or disabled.) Table 2 5 shows the descriptor for the default configuration (3) with NMEA and MS disabled. Table 2-5: Configuration descriptor (ID 3) Field identifier Value wtotallength bnuminterfaces bconfigurationvalue iconfiguration bmattributes MaxPower 0x0091 0x05 (Default configuration has NMEA and MS disabled.) 0x01 0x01 (String descriptor index corresponding to Sierra Configuration ) 0xA0 (Adapter products Bus Powered Remote Wakeup) 0xE0 (Embedded products Bus Powered, Self Powered, Remote Wakeup) 0xFA (Adapter products 500 ma) 0x00 (Embedded products 0 ma) Rev Jan Distribution under NDA only 15

16 Direct IP Integration Guide faces is sent to the host. Table 2 6 shows the descriptor for the HIP interface. Table 2-6: Interface descriptor (HIP) Field identifier Value binterfacenumber balternatesetting bnumendpoints binterfaceclass binterfacesubclass binterfaceprotocol iinterface 0x00 0x00 0x02 0xFF 0xFF 0xFF 0x00 16 Distribution under NDA only

17 3: Host Device Communication 3 Message types Two message types are transported between the host and device using Sierra s link layer HIP protocol control messages and data messages (user data). See MC87xx Modem CnS Reference [R 4] for HIP details. Control messages Messages are passed between the host and device as follows: The host sends messages over endpoint 0 using the SEND_ENCAPSULATED_COMMAND management element request. The device sends messages by first sending a RESPONSE_AVAILABLE notification element over the Direct IP interface s INTERRUPT endpoint. The host then retrieves the message over endpoint 0 using the GET_ENCAPSULATED_RESPONSE management element request. The control messages (in both directions) are encapsulated within HIP frames. See Table 6 1 on page 27 for a list of supported Direct IP control messages. The host driver should ignore any unrecognized messages. Data messages Messages (user data) are passed between the host and device over the Direct IP interface s BULK OUT and BULK IN endpoints the host sends to the device over the BULK OUT endpoint, and the device sends data to the host over the BULK IN endpoint. These messages are encapsulated within HIP frames. See Table 6 1 on page 27 for a list of supported Direct IP data messages. The host driver should ignore any unrecognized messages. Rev Jan Distribution under NDA only 17

18 Direct IP Integration Guide Host device interactions The following state diagrams (Figure 3 1 and Figure 3 2) represent interactions between the host and device (synchronization, device reset, host shutdown, and data transfer) using control messages. MDM Data Link Sync Indication (not received) MDM Data Link Sync Indication (ignored) Device Power Up Device is reset (No message to host) Device Ready Downlink Direct IP Data Indication (to Host) System Shutdown Indication (from Host) MDM Data Link Sync Indication (from Host) Restart Indication (to Host) Device Idle MDM Data Link Sync Indication (from Host) Device Received 1 st Sync Figure 3-1: Device operation state diagram MDM Data Link Sync Indication (to Device) Host Idle Host Down Restart Indication (from Modem) System Shutdown Indication (to Device) Host Ready Uplink Direct IP Data Indication (to Device) Figure 3-2: Host operation state diagram 18 Distribution under NDA only

19 Host device interactions Synchronization The host and device must be synchronized (using the MDM DATA LINK SYNC INDICATION) before exchanging any other Direct IP HIP messages, as shown in Figure 3 3 and in the following procedure: 1. The host, in Host Idle state, initiates the synchronization process by sending two MDM DATA LINK SYNC INDICATIONs to the device. 2. The device must be in the Device Idle state to accept the first indication. When the second indication is accepted, the device changes to the Device Ready state. Note: If the host doesn t receive a RESTART_INDICATION after two seconds, it should restart this process. Device 3. The device sends a Restart Indication to the host. When the host receives the indication, it moves into the Host Ready state. The host and device are now synchronized and will remain so until either the device resets or the host sends a System Shutdown Indication. The synchronization procedure must then be repeated before further messages can be exchanged. Host State = Unpowered or Power Up Modem Data Link Sync Indication Modem Data Link Sync Indication State = Idle State = Idle Host waits for 2 seconds for a Restart Indication, then reattempts to synchronize. State = Received 1 st Sync State = Ready Modem Data Link Sync Indication Modem Data Link Sync Indication Restart Indication State = Ready Other HIP messages Other HIP messages Figure 3-3: Synchronization process Device Reset When the device resets, it transitions through the Device Power Up and Device Idle states. Rev Jan Distribution under NDA only 19

20 Direct IP Integration Guide The synchronization procedure must be repeated before further messages can be exchanged with the host. System (host) Shutdown When the host application terminates or when the network driver is unloaded, the System Shutdown Indication should be sent to the device. This causes both the device and host to transition to their Idle states. The synchronization procedure must be repeated before further messages can be exchanged. Data transfer After the host and device have synchronized (both are in their Ready states), data is transferred between them using the Uplink and Downlink Direct IP Data Indications. 20 Distribution under NDA only

21 4: Direct IP Data Sessions 4 Direct IP data sessions can be managed using either CnS objects or AT commands, as described in the following sections: Manage profiles (PDP contexts) on page 21 Enable/disable auto connect on page 22 Activate/terminate data sessions on page 22 Table 4-1: CnS objects used for profile management 1 Manage profiles (PDP contexts) You can manage defined profiles using either the CnS objects in Table 4 1, or the AT commands in Table 4 2. CnS object ID Description Return Profile Summary 0x7001 Returns a summary of all packet session profiles stored on the device and sets the default user profile. Read Profile 0x7002 Returns basic, QoS, DNS, or TFT information for a defined profile. Write Profile 0x7003 Writes basic, QoS, DNS, or TFT information for a defined profile. Manage Profile Username and Password 0x7004 Reads or writes the username and/or password for a defined profile. 1. See the MC87xx Modem CnS Reference [R-4] for details Table 4-2: AT commands used for profile management Command AT$QCPDPP 1 AT!SCPROF 1 AT!SCPROFDEL 2 AT!SCDFTPROF 2 AT!SCDNS 2 AT!SCPADDR 2 +CGEQMIN 3 +CGEQNEG 3 Description Set authentication requirements (username, password) for PDP-IP packet data calls for each supported profile. Set/report a profile s read-only flag. Erase profile information. Set/return default profile ID. Set/return profile ID DNS addresses. Return IP address for specified profile. 3G QoS Profile (Minimum acceptable) 3G QoS Profile (Negotiated) Rev Jan Distribution under NDA only 21

22 Direct IP Integration Guide Table 4-2: AT commands used for profile management (Continued) Command Description +CGEQREQ 3 +CGQMIN 3 +CGQREQ 3 3G QoS Profile (Requested) QoS profile (Minimum acceptable) QoS profile (Requested) 1. See the UMTS Modems Supported AT Command Reference [R-6] for details. 2. See the MC87xx Modem Extended AT Command Reference [R-5] for details. 3. See the GPP AT Command Set for User Equipment [R-7] for details. Enable/disable auto-connect To configure the default profile to auto connect a Direct IP data session when the device registers on the network, enable the profile s auto connect flag using either of the following methods: Using CnS objects Use the CnS object Write Profile (0x7003). For details, see the MC87xx Modem CnS Reference [R 4]. Using AT commands Use the AT command!scprof. For details, see the UMTS Modems Supported AT Command Reference [R 6]. When the UE has attached to the network, a PDP context activation is attempted using the default (auto connect) profile s settings. When the PDP context is active, a Link Status Indication is sent to the host. See Link Status Indication on page 29 for details. Activate/terminate data sessions To activate or terminate a Direct IP data session, use either of the following methods: Using CnS objects Use the CnS object Write Profile (0x7003). For details, see the MC87xx Modem CnS Reference [R 4]. Using AT commands Use the AT command!scact. For details, see the UMTS Modems Supported AT Command Reference [R 6]. 22 Distribution under NDA only

23 5: Device Operation 5 Sierra Wireless devices that support Direct IP operate either in Direct IP mode or Traditional (non Direct IP) mode, based on the device PID (Product ID). Devices operating in traditional mode can be temporarily switched into Direct IP mode by changing their device PIDs to the Direct IP PID. Table 5 1 describes the PIDs of devices supporting Direct IP. Table 5-1: Direct IP-supporting device PIDs 1 Device PID Device mode Device composition 683C Traditional Composite 6890 Traditional Composite 683D Traditional Composite 683E Traditional Non-composite 68A3 Direct IP Composite 1. This list is subject to change see Display all supported PIDs (below) for instructions on how to use AT commands to display the list of Direct IP-supporting devices. Note: The AT commands in this chapter must first be unlocked using a password that you can obtain from your Sierra Wireless account representative. Before using the procedures below to change device PIDs to enter Direct IP mode, you should make note of the device s original PID. Display the current device PID 1. Display the current PID: Type AT!UDINFO?. Display all supported PIDs 1. If not already done, unlock protected AT commands: Type AT!ENTERCND=<password>. 2. Display the list of supported PIDs: Type AT!UDPID=?. Switch from Traditional mode to Direct IP mode 1. If not already done, unlock protected AT commands: Type AT!ENTERCND=<password>. Rev Jan Distribution under NDA only 23

24 Direct IP Integration Guide 2. Select the Direct IP PID: Type AT!UDPID = 68A3. 3. Reset the device (to use the requested PID): Type AT!RESET. Switch from Direct IP mode to Traditional mode 1. If not already done, unlock protected AT commands: Type AT!ENTERCND=<password>. 2. Select your device s traditional mode PID: Type AT!UDPID = <pid> where <pid> is the traditional PID. (If you don t remember the original PID, see Display all supported PIDs and find the correct PID for your device.) 3. Reset the device (to use the requested PID): Type AT!RESET. 24 Distribution under NDA only

25 6: Driver and host device messages 6 Direct IP driver The Sierra Wireless Direct IP driver (sierra_net) for Linux systems resembles a standard Ethernet interface, with the following exceptions: DHCP support The driver performs the DHCP function. ARP support The driver performs the ARP function, but the host stack can turn it off. Note: The maximum transmission unit (MTU) for Direct IP is 1500 bytes. Ethernet headers These headers do not need to be populated. See Direct IP HIP message format below for details on Ethernet frames carried within HIP messages. HIP packet aggregation Each USB transfer (from device to host, or host to device) carries a single HIP packet. For more details about the Direct IP driver, refer to the Linux SDK Integration Guide [R 2]. Direct IP HIP message format Control and data messages are transferred between the host and device using Sierra Wireless HIP message frames. Each HIP message frame includes a header (standard or extended) and payload, where the payload is a modified Ethernet frame that carries details of the specific message and, if appropriate, an IP packet. Rev Jan Distribution under NDA only 25

26 Direct IP Integration Guide HIP frame (standard or extended header plus payload) Message Header (Standard: 4 bytes Extended: 6 bytes) Message payload (optional) (Variable length, modified Ethernet frame) Standard message header Reserved (5 bits) Message payload length (11 bits) Reserved (1 bit) Message identifier (7 bits) Message specific identifier (8 bits) Extended message header Reserved (2 bits) Message payload length (14 bits) Reserved (1 bit) Short message identifier (7 bits) Message specific identifier (8 bits) Reserved (6 bits) Extended message identifier (10 bits) This field indicates the header format being used. (Extended if 3F or 7F, otherwise Standard) Figure 6-1: HIP message header formats For Direct IP, the following restrictions or considerations apply to HIP and Ethernet frames: The (Short) Message identifier field indicates which header format is used. If the value is 0x3F or 0x7F, then the header is 6 bytes long (extended); otherwise, the header is 4 bytes long (standard). Data messages use extended HIP frames Control messages use standard HIP frames Ethernet frame headers do not need to be populated DHCP functionality is provided by the driver. (If DHCP functionality is moved into the firmware in the future, then the frame header will have to be populated with appropriate source and destination addresses.) The MTU size for Direct IP is 1500 bytes. That is, the payload of a single Ethernet frame must be 1500 bytes or less. If more than 1500 bytes of data is to be transferred, multiple HIP messages must be used. For details on using HIP messages, see the MC87xx Modem CnS Reference [R 4]. 26 Distribution under NDA only

27 Direct IP control and data messages Table 6-1: Supported Direct IP messages Direct IP control and data messages Table 6 1 lists all of the control and data messages that are supported for Direct IP. Detailed listings of possible values for the Message specific parameter and Message payload fields appear after the table for specific messages. HIP message Name ID Exten. ID Implementation Req d Message specific parameter Message payload Description Control messages MDM DATA LINK SYNC INDICATION 0X20 N/A Yes Unused None Message used to synchronize the host and device. RESTART INDICATION 0x62 N/A Yes Return Code. See Restart Indication on page 28. Optional nullterminated ASCII string for debugging Sent from device to host when device enters DEVICE READY state SYSTEM SHUTDOWN INDICATION 0x26 N/A Yes Unused None Unsolicited message sent from host to notify device that the host is shutting down (power removal) LINK STATUS INDICATION 0x78 N/A Yes Context Index Number (0 for products not supporting multiple instances) See CnS Reference ([R4]) for payload format. Unsolicited message sent from device to host to inform of a change in packet session status. WWAN RSSI INDICATION 0x75 N/A No Unused RSSI. See WWAN RSSI Indication on page 29 Unsolicited message sent from device to host notifying of a change in RSSI. WWAN REGISTRATION REQUEST 0x0C N/A No Unused None Message sent from host to device to register for WWAN RSSI indications. Rev Jan Distribution under NDA only 27

28 Direct IP Integration Guide Table 6-1: Supported Direct IP messages (Continued) HIP message Name ID Exten. ID Implementation Req d Message specific parameter Message payload Description WWAN REGISTRATION RESPONSE Data messages 0x48 N/A No Unused Return code. See WWAN RSSI Registration response on page 29 Confirmation sent from device to host indicating that host is registered to receive WWAN RSSI indications. UPLINK DIRECT IP DATA INDICATION 0x3F 0x002 Yes Network driver instance (1 byte) User data Message used to transfer data from the host to the device DOWNLINK DIRECT IP DATA INDICATION 0x7F 0x202 Yes Network driver instance User data Message used to transfer data from the device to the host Restart Indication Message specific parameter Return code. Possible values are: 0x00 Device application firmware running (sent by application firmware). The accompanying message payload is an ASCII string identifying the version number of the device s application software. 0x01 Failed to start application, no application detected (sent by boot loader). 0x02 Failed to start application, corrupted application detected (sent by boot loader). 0x03 Waiting in Boot & Hold state for program download (sent by boot loader when detecting Boot & Hold condition). 0x04 RAM test failed Message payload The message payload is an optional, NULL terminated ASCII string that provides additional information. (For example, debugging information, the device application software version number, etc.) 28 Distribution under NDA only

29 Direct IP control and data messages WWAN RSSI Indication Message payload: The message payload is the RSSI value in decibels, represented as a 4 byte integer in network byte order. To calculate the RSSI value in dbm with respect to a noise level of 110 dbm, use the following calculation: RSSI(dBm) = RSSI 110 dbm Note: P(dBm) = 10log(P/10 3 Watts) where P is the power level in Watts WWAN RSSI Registration response Message payload: The message payload is a return code. Possible values are: 0x00 WWAN Registration successful Link Status Indication Message specific parameter: Context index number: 0 PDP1 Message payload The message payload is the link status information. For the detailed structure of the message payload, refer to the Link Status Indication section of the MC87xx Modem CnS Reference [R 4]. Rev Jan Distribution under NDA only 29

30 Direct IP Integration Guide 30 Distribution under NDA only

31

32