Huawei 目录 (Contents) MU609 HSPA LGA Module Application Guide (V100R002 05, English)

2017-01-12

• Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
• Trademarks and Permissions
• Notice
• DISCLAIMER
• Import and Export Regulations
• Privacy Policy
• Revision History
• 1 Overview
  • 1.1 Conventions and Definitions
    • 1.1.1 Conventions
    • 1.1.2 Definitions
  • 1.2 Organization of This Document
  • 1.3 Basic AT Command Processing Principles
    • 1.3.1 Ports
      • The MU609 supports two configurations with USB connection, and the second configuration will be selected as the default configuration on Linux/Android OS.
      • Step 1 Execute dmesg command.
      • Step 2 Find the mapping details between the ttyUSBx and the USB port.
        • Figure 1-1 Port sequence on Linux
    • 1.3.2 AT Command Processing Mechanism
      • Figure 1-2 AT command processing sequence diagram
    • 1.3.3 Recommended Timeout Mechanism for AT Commands Processed by a Host
      • Table 1-1 AT command timeout duration
      • 1. The host sends AT to the module.
      • 2. If the module returns failure information, go to step 5.
      • 3. If the module returns success information, the module is functioning normally.
      • 4. If the host times out (the host waits for a response for over 30 seconds) three times when waiting for the response from the module, go to step 5. Otherwise go to step 1.
      • 5. The host deems that the current module does not exist or is unavailable. Close the port, stop sending all AT commands, exit the procedure to determine whether the module is normal, and re-search for modules.
• 2 Initialization Application Scenarios
  • 2.1 Startup Indication ^SYSSTART
    • 2.1.1 Reference Process
    • 2.1.2 Troubleshooting
  • 2.2 Querying Basic Information
    • 2.2.1 Reference Process
    • 2.2.2 Troubleshooting
  • 2.3 Network Service Operations
    • 2.3.1 Reference Process
    • 2.3.2 Troubleshooting
• 3 Serial Port Configuration Application Scenarios
  • 3.1 Baud Rate Configuration
    • 3.1.1 Reference Process
    • 3.1.2 Troubleshooting
  • 3.2 DTR Hang Up Data Services
    • 3.2.1 Reference Process
    • 3.2.2 Troubleshooting
  • 3.3 DCD Pin Control
    • 3.3.1 Reference Process
    • 3.3.2 Troubleshooting
  • 3.4 Setting Hardware Flow Control
    • 3.4.1 Reference Process
    • 3.4.2 Troubleshooting
• 4 External Protocol Stack Application Scenarios
  • 4.1 Prerequisites
    • 4.1.1 Reference Process
    • 4.1.2 Troubleshooting
  • 4.2 Establishing Data Connections
    • 4.2.1 Troubleshooting
  • 4.3 Data Transmission
    • 1. Data can be transmitted after data service connections are established.
    • 2. According to 3GPP TS 25.306, HSDPA (FDD) terminals are classified into 24 categories. Different categories have different peak data rates. The following table lists common categories and their key parameters.
    • 3. According to the Radio Resource Control (RRC) version, the WCDMA/HSDPA/HSUPA/HSPA/DC_HSPA rate in theory are as follows:
  • 4.4 Switch Between Data Mode and Command Mode
    • 4.4.1 Reference Process
    • 4.4.2 Troubleshooting
  • 4.5 Disconnecting Data Service Connections
    • 4.5.1 Reference Process
      • 1. Terminating a data service connection from the TE: the TE sends a PPP Terminate packet to the UE to pull down the DTR signal. The UE disconnects the PPP connection, releases the wireless link resource, pulls down the CD signal, and returns NO CARRI...
      • 2. Terminating a data service connection from the UE: The TE sends an AT command to the UE to pull down the DTR signal. After receiving the AT command, the UE releases the connection to the network, pulls down the CD signal, and returns NO CARRIER. As...
      • 3. When disconnecting data service connections in Android RIL, the module must kill pppd to disconnect PPP connections before using AT+CGACT=0 to deactivate PDP contexts and release wireless link resources.
• 5 Internal Protocol Stack Application Scenarios
  • 5.1 Initializing Internet Services
    • 5.1.1 Reference Process
    • 5.1.2 Troubleshooting
  • 5.2 Creating a Listen Server
    • 5.2.1 Reference Process
    • 5.2.2 Troubleshooting
  • 5.3 Creating TCP/UDP Links
    • 5.3.1 Reference Process
    • 5.3.2 Troubleshooting
  • 5.4 Sending Data
    • 5.4.1 Reference Process
    • 5.4.2 Troubleshooting
  • 5.5 Closing TCP/UDP Links
    • 5.5.1 Reference Process
    • 5.5.2 Troubleshooting
  • 5.6 Transparent Transmission Mode
    • 5.6.1 Reference Process
    • 5.6.2 Troubleshooting
  • 5.7 Packet Statistics
    • 5.7.1 Reference Process
  • 5.8 TCP/UDP Link Change Indication
    • 5.8.1 Reference Process
• 6 Text Message Application Scenarios
  • 6.1 Pre-configuration (CPMS)
    • 6.1.1 Reference Process
    • 6.1.2 Troubleshooting
  • 6.2 Sending English Text Messages in PDU Format
    • 6.2.1 Reference Process
    • 6.2.2 Troubleshooting
  • 6.3 Sending Chinese Character Text Messages in Text Format
    • 6.3.1 Reference Process
    • 6.3.2 Troubleshooting
  • 6.4 Receiving Text Messages
    • 6.4.1 Reference Process
    • 6.4.2 Troubleshooting
  • 6.5 Segmenting and Reassembling Long Text Messages
    • 6.5.1 Segmenting
      • Figure 6-1 Relationships between character sets
    • 6.5.2 Reassembling
• 7 Phonebook Application Scenarios
  • 7.1 Memory Operations
    • 7.1.1 Reference Process
    • 7.1.2 Troubleshooting
  • 7.2 Writing/Deleting Phonebook Entries
    • 7.2.1 Reference Process
    • 7.2.2 Troubleshooting
  • 7.3 Reading Phonebook Entries
    • 7.3.1 Reference Process
    • 7.3.2 Troubleshooting
  • 7.4 Searching for Phonebook Entries
    • 7.4.1 Reference Process
    • 7.4.2 Troubleshooting
  • 7.5 Querying User Number
    • 7.5.1 Reference Process
    • 7.5.2 Troubleshooting
  • 7.6 Setting the TE's Character Sets
    • 7.6.1 Reference Process
    • 7.6.2 Troubleshooting
• 8 SIM Operation Application Scenarios
  • 8.1 PIN Operations
    • 8.1.1 Reference Process
    • 8.1.2 Troubleshooting
  • 8.2 CRSM Command
    • 8.2.1 Reference Process
    • 8.2.2 Troubleshooting
• 9 Sleeping and Waking Up Application Scenarios
  • 9.1 Hardware Interfaces
    • Table 9-1 Power management related pins
  • 9.2 Sequence Diagram
    • Figure 9-1 WAKE#/WAKEUP_OUT (when a NPN triode is externally connected to the WAKEUP_OUT pin) output sequence
    • Figure 9-2 WAKEUP_IN input sequence
    • Figure 9-3 SLEEP_STATUS output sequence
  • 9.3 Software Interfaces
    • 9.3.1 Principle
      • Figure 9-4 Currency state when the module is in sleep mode
      • Figure 9-5 Sleep procedure
    • 9.3.2 USB and Sleep
    • 9.3.3 UART and Sleep
    • 9.3.4 Module Wake-up
      • 1. The host sends data using USB/UART or pulls WAKEUP_IN up.
      • 2. Changes on the network, for example, an incoming text message, a signal change, a network working mode change, a network search, an IP data package (when a dial-up network connection is set up).
      • 3. Software system events such as a timer
      • 4. Abnormal events, for example, an antenna drops or a SIM card becomes loose.
    • 9.3.5 Host Woken up by Module
      • Wake-up Source
      • Remotely Waking up the Host Using USB
        • 1. The USB controller on the host supports USB remote wake-up and can wake up the host.
        • 2. The USB driver enables or disables remote wake-up by executing SET_FEATURE and CLEAR_FEATURE commands. Therefore, remote wake-up must be enabled on the USB driver before USB enters suspended mode.
        • 3. When the host receives the remote wake-up signal from the module, the host needs to send a full speed K signal that lasts at least 20 ms. When the USB controller resumes, the host must send the SOF token within 3 ms from the startup of the idle sta...
          • Figure 9-6 USB resume time sequence
          • Figure 9-7 Successful procedure of remote wake-up
      • WAKEUP_OUT Waking up the Host
      • Remote Wake-up Configuration
  • 9.4 Application Scenarios: System with USB Connection only
    • 9.4.1 Hardware Connection
    • 9.4.2 Software Procedure
    • 9.4.3 Advantages
  • 9.5 Application Scenarios: System with USB and WAKEUP_OUT
    • 9.5.1 Hardware Connection
    • 9.5.2 Software Procedure
    • 9.5.3 Advantages
  • 9.6 Application Scenarios: System with UART and WAKEUP_OUT
    • 9.6.1 Hardware Connection
    • 9.6.2 Software Procedure
      • Figure 9-8 Wake-up and hand-shaking using UART(CTS/RTS) and WAKEUP_OUT pins
    • 9.6.3 Advantages
  • 9.7 System with Other Connection Methods
• 10 Thermal Protection Application Scenarios
  • 10.1 Pre-configuration
    • 10.1.1 Troubleshooting
  • 10.2 Thermal Protection Process
• 11 GPS Application Scenarios
  • 11.1 Introduction to GPS
    • 11.1.1 GPS Positioning Methods
      • Table 11-1 GPS positioning methods
    • 11.1.2 GPS Ports
      • Figure 11-1 Control Interface and 3G GPS Interface detected after the module is connected to a computer
      • Figure 11-2 Data sent through the control interface and 3G GPS interface ports
  • 11.2 Standalone Positioning
  • 11.3 MSB Positioning Using the User Plane Protocol
  • 11.4 XTRA Positioning
  • 11.5 GNSS Positioning
• 12 Concurrent Service Application Scenarios
  • 12.1 Internal/External Protocol Stacks and Text Messaging
    • Table 12-1 Ports available to text messaging during data services
  • 12.2 Other Services
    • Table 12-2 Ports available to configuration, phonebook and PIN operations when the module is processing data services
• 13 STK Application Scenarios
  • 13.1 Unsolicited Report of STK Proactive Commands
    • 13.1.1 Reference Process
    • 13.1.2 Troubleshooting
  • 13.2 Querying the STK Main Menu
    • 13.2.1 Reference Process
    • 13.2.2 Troubleshooting
  • 13.3 STK Envelope Command
    • 13.3.1 Reference Process
    • 13.3.2 Troubleshooting
• 14 USSD Application Scenarios
  • 14.1 USSD Initialize and Configration
    • 14.1.1 Reference Process
    • 14.1.2 Troubleshooting
  • 14.2 Send the USSD Command in non-Transparent Mode
    • 14.2.1 Reference Process
    • 14.2.2 Troubleshooting
  • 14.3 Send the USSD Command in Transparent Mode
    • 14.3.1 Reference Process
    • 14.3.2 Troubleshooting
  • 14.4 Network Initiated USSD Operation
    • 14.4.1 Reference Process
    • 14.4.2 Troubleshooting
• 15 FOTA Application Scenarios
  • 15.1 FOTA Process
    • 15.1.1 Upgrade Module Firmware Over Air Through Delta Package
      • Figure 15-1 Upgrade module firmware over air through delta package
    • 15.1.2 Procedure for FOTA Implementation
      • Figure 15-2 FOTA data flow
  • 15.2 Setting FOTA Mode
    • 15.2.1 Reference Process
    • 15.2.2 Troubleshooting
  • 15.3 Setting FOTA Connection Parameters
    • 15.3.1 Reference Process
    • 15.3.2 Troubleshooting
  • 15.4 Manually Querying for Upgrade Firmware Version
    • 15.4.1 Reference Process
    • 15.4.2 Troubleshooting
  • 15.5 Periodically Querying the Version
    • 15.5.1 Reference Process
    • 15.5.2 Troubleshooting
  • 15.6 Manually Downloading the Version
    • 15.6.1 Reference Process
    • 15.6.2 Troubleshooting
  • 15.7 Automatically Downloading the Firmware
    • 15.7.1 Reference Process
    • 15.7.2 Troubleshooting
  • 15.8 Using the Resumable Data Transfer Function
    • 15.8.1 Reference Process
    • 15.8.2 Troubleshooting
  • 15.9 Manually Canceling the Download
    • 15.9.1 Reference Process
    • 15.9.2 Troubleshooting
  • 15.10 Manually Upgrading the Version
    • 15.10.1 Reference Process
    • 15.10.2 Troubleshooting
  • 15.11 Automatically Upgrading the Version
    • 15.11.1 Reference Process
    • 15.11.2 Troubleshooting
• 16 ECM Application Scenarios
  • 16.1 ECM Dialing
    • 16.1.1 Reference Process
      • 1. After the dial-up is successful, the module will establish the DHCP service automatically.
      • 2. The PC driver will get the dial-up state and send net_ready state to the network manage.
      • 3. The network manager sends the DHCP service discover.
      • 4. The module responses the service discover, and then sends the IP and DNS address which is obtained from the PDP active process to the network managing device.
    • 16.1.2 Troubleshooting
  • 16.2 Querying the Dial-up Connection State
    • 16.2.1 Reference Process
    • 16.2.2 Troubleshooting
  • 16.3 Disconnecting the Dial-up Connection
    • 16.3.1 Reference Process
    • 16.3.2 Troubleshooting
• 17 Local Upgrade Application Scenarios
  • 17.1 Starting the Local Upgrade
    • 17.1.1 Local Upgrade Flow Chart
      • Increment Upgrade Flow
        • Figure 17-1 Increment upgrade flow
      • Full Upgrade Flow
        • Figure 17-2 Full upgrade flow
    • 17.1.2 Test Steps
      • Tools and Test Steps
        • Step 1 Open the Hyper Terminal tool and choose the modem port number. (In this document, the modem port is COM25.)
        • Step 2 Set the parameters of the COM25 port.
        • Step 3 Run the AT^FWLOAD=1 command, and launch an increment upgrade.
        • Step 4 Choose the file which will be sent to the module and choose the 1K Xmodem protocol.
        • Step 5 Begin to transfer the local file to the module flash.
        • Step 6 After finishing the file transmission, start the upgrade. And the module will reset automatically to finish the upgrade.
      • Requirement of the AP
        • 1. AP should be able to access and load the upgrade files.
        • 2. AP should have a file transmission tool, this tool need to support 1K-Xmodem protocol.
      • Finding the PCUI port on Android and Linux System
        • Step 1 Enter /sys/bus/usb/drivers/option, and look out the following types of folders.
        • Step 2 Enter these folders, and view the bInterfaceProtocol value.
    • 17.1.3 Reference Process
    • 17.1.4 Troubleshooting
  • 17.2 Reporting the Local Upgrade State
    • 17.2.1 Reference Process
    • 17.2.2 Troubleshooting
• 18 Appendix
  • 18.1 Relative Documents
    • 1. The latest version of MU609 V100R002 of HUAWEI MU609 HSPA LGA Module AT Command Interface Specification
    • 2. 3GPP TS 27.007 AT command set for User Equipment (UE)
    • 3. 3GPP TS 27.005 Equipment (DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)
    • 4. 3GPP TS 23.040 Technical realization of the Short Message Service(SMS)
    • 5. 3GPP TS 31.102 Universal Subscriber Identity Module(USIM) application
    • 6. 3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network protocols; Stage 3
    • 7. 3GPP TS 29.002 Mobile Application Part (MAP) specification
    • 8. 3GPP TS 22.004 General on supplementary services
    • 9. ETSI TS 102.221 Smart Cards; UICC-Terminal interface; Physical and logical characteristics
  • 18.2 Acronyms and Abbreviations
    • Table 18-1 List of Abbreviations
    • Table 18-2 Phonebook-related abbreviations
  • 18.3 Exception Handling
    • 18.3.1 Module Reset
      • Step 1 Input AT+CGDCONT=1,"IP","1234"
      • Step 2 Input ATD*99#
    • 18.3.2 Module Going to Dump Status
    • 18.3.3 Module Data Service Disconnected
      • Step 1
      • Step 2
    • 18.3.4 User Configuration Lost