Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Huawei Industrial Base, Bantian, Longgang, Shenzhen 518129, People’s Republic of China
Tel: +86-755-28780808 Global Hotline: +86-755-28560808 Website: www.huawei.com
E-mail: mobile@huawei.com
Please refer color and shape to product. Huawei reserves the right to make changes or improvements to any
of the products without prior notice.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
The product described in this manual may include copyrighted software of Huawei Technologies Co., Ltd and
possible licensors. Customers shall not in any manner reproduce, distribute, modify, decompile, disassemble,
decrypt, extract, reverse engineer, lease, assign, or sublicense the said software, unless such restrictions
are prohibited by applicable laws or such actions are approved by respective copyright holders under
licenses.
Trademarks and Permissions
, , and
Other trademarks, product, service and company names mentioned are the property of their respective
owners.
are trademarks or registered trademarks of Huawei Technologies Co., Ltd.
Notice
Some features of the product and its accessories described herein rely on the software installed, capacities
and settings of local network, and may not be activated or may be limited by local network operators or
network service providers, thus the descriptions herein may not exactly match the product or its accessories
you purchase.
Huawei Technologies Co., Ltd reserves the right to change or modify any information or specifications
contained in this manual without prior notice or obligation.
NO WARRANTY
THE CONTENTS OF THIS MANUAL ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE
LAWS, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS
MANUAL.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO CASE SHALL HUAWEI
TECHNOLOGIES CO., LTD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR
CONSEQUENTIAL DAMAGES, OR LOST PROFITS, BUSINESS, REVENUE, DATA, GOODWILL OR
ANTICIPATED SAVINGS.
Import and Export Regulations
Customers shall comply with all applicable export or import laws and regulations and will obtain all necessary
governmental permits and licenses in order to export, re-export or import the product mentioned in this
manual including the software and technical data therein.
Personal Identification Number (PIN), Personal Unlock Key
(PUK), or password
Term
Definition
Connected
Indicates that a link has been set up between two
modules or a module and a terminal.
Registered
Indicates that the module is registered with a
LTE/UMTS/GSM network.
Module
HUAWEI LTE module
This document is intended to provide references for customers to choose appropriate
command sequences to start using the ME909u-521 module in a faster manner. This
document also contains examples and relevant description.
This document will be updated based on customers' requirements.
The ME909u-521 module provides three ports to interact with its host:
MODEM port: simulated using USB, for AT command interaction and
establishing data connection.
Port name: HUAWEI Mobile Connect-3G Modem
PCUI port: simulated using USB, for AT command interaction only.
Port name: HUAWEI Mobile Connect-3G PCUI Interface
ECM port: simulated using USB, for establishing communication connection.
Port name: CDC Ethernet Control Model (ECM)
The ME909u-521 also provides a port for debugging:
DIAG port: Simulated using USB, for DIAG (diagnostic) command interaction
(mainly used to debug modules at present).
Port name: HUAWEI Mobile Connect-3G Application Interface
A host controls a module using AT commands. If AT commands are unavailable, a
module can be deemed as unavailable.
1.3.2 AT Command Processing Mechanism
A module processes AT commands from the ports (MODEM, PCUI) in series. An AT
command can be processed when and only when the previous AT command
processing has been completed. If the module is processing an AT command, a new
AT command from the same port will be ignored and other commands from other
ports will be buffered until the current AT command is processed.
This rule also applies to COM ports converted from USB ports.
The processing of an AT command starts when the AT command is entered from the
TE, and ends when the UE (the module) returns all the results in response the
command.
Before the results ofAT+COPS
is returned, enter any characters
(such as"AT"), the module will
terminate the processing of
AT+COPS and returnOK. The
entered characters are used to
abort the command only.
AT Command
Timeout Duration
General AT commands
30s
AT+CMSS/AT+CMGS (used to send text
messages)
60s
AT+COPS=? (used to search for networks)
120s
Some commands can be executed when SIM card is inserted. It would return to SIM
failure if SIM card is not inserted. For more information, see Property Description of
related AT in HUAWEI ME909u-521 LTE LGA Module AT Command Interface Specification.
Example:
AT+CREG?
+CME ERROR: SIM failure
Note:
SIM failure indicate that SIM card is not inserted.
1.3.3 Recommended Timeout Mechanism for AT Commands
Processed by a Host
A module processes AT commands in series. Do not send another AT command
before the result for the current command is returned or the current command times
out (except when the current command is an abortive AT command). The following
table lists AT command timeout durations (starting from the time when an AT
command arrives at a port).
Table 1-1 AT command timeout duration
After an AT command times out, it is recommended that the host check whether the
module is functioning normally. The following procedure is provided for your
reference:
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.
Short Message Service (SMS) is a text messaging service using a service center(SC)
to transfer short text messages between GSM MEs and Short Message Entities
(SMEs). ME909u-521 only supports protocol data unit (PDU) mode message.
A message must contain the following information before it is sent:
5 SMS Application Scenarios
For a PDU mode message:
Length of TPDU package
Message content: To compose or send a PDU mode message, the message
must contain all the message attributes and be encoded in PDU format. A PDU
consists of the following:
−Service Center Address (SCA): composed of the address length, SCA type
and SCA reverse byte.
−First octet: contains the message type indicator, TP-RP, TP-UDHI, TP-SRR,
TP-VPF, TP-RD, and TP-MTI.
− Short text message statement.
− Destination address: consisting of the destination address, address length
and destination address type.
− Protocol identifier.
− Data encoding scheme.
− Validity duration.
− Data length.
− User data: consisting of the user data header and the data encoded in PDU
format.
Figure 5-1 shows an example of data encoded in PDU format of submitted type.
Use the AT+CMGF command to set short message format: AT+CMGF=0 sets the
short message format to PDU.
The SMSC address provided by the service provider must be specified. In PDU mode,
the SMSC address is contained in the PDU packets. Therefore, in PDU mode, the
AT+CSCA command is optional.
To use the SMS features specified in the GSM 07.05 Phase 2+, the AT+CSMS
command must be used to enable the features.
Use the AT+CNMI command to set the unsolicited indications.
Use the AT+CPMS command to select the preferred short message storage (SIM or
ME). The ME909u-521 supports only the SM (SIM card) storage.
Use the AT+CGSMS command to select the MO SMS bearer domain (PS or CS
domain). For ME909u-521, the CS domain is the preferred MO bearer domain.
address. The value of SMSC address is the setting
of +CSCA command.
+CMGS: 168
OK
The message is successfully sent.
AT+CMGS=18
>0891683108608805F93100
0B813109731147F40000FF0
4F4F29C0E\x1A
Send a PDU message with the correct service
center address.
+CMGS: 169
OK
The message is successfully sent.
AT+CMGS=18
>0891683108608805F03100
0B813109731147F40011FF0
4F4F29C0E\x1A
Send a PDU message with the wrong service
center address.
+CMS ERROR: Network out
of order
The message is unsuccessfully sent.
Messages in PDU format must be converted using external tools or users' software.
Tools for encoding and parsing messages in PDU format are available on the Internet.
The format of short messages can refer to
the AT+CMGR command.
Message State
PDU Mode
Received unread messages
0
Received read messages
1
Stored unsent messages
2
Stored sent messages
3
5.4.1 Reference Process
There are two methods to read short messages:
Method 1: Use the AT+CMGL command to list the messages that are in
specified state and stored in the preferred message storage. The following table
describes the message states. If the message sate is received unread
messages, the REC UNREAD state will be changed to REC READ after the
AT+CMGL command is executed.
+CMGL:<index1>,0,,<length>
<pdu> (messages in PDU format)
......
+CMGL:<indexn>,0,,<length>
<pdu> (messages in PDU format)
OK
PDU format
+CMGR:n,,<length>
<pdu> (messages in PDU format)
OK
End
AT+CMGL=0
AT+CMGR=n
Method 2: Use the AT+CMGR command to read a message from a specified
storage location in the message storage. If the message is a received unread
message, its state will be changed to REC READ after it is read using the
AT+CMGR command.
You can use the AT+CMGL command to list all short messages so that you can view
the messages' storage locations.
Either all messages stored in the preferred message storage or a message
stored in the specified storage location in the preferred message storage can be
deleted.
All read or unread messages that have been received can be deleted.
If no messages are stored in the preferred message storage, "OK" is returned
when the action to delete messages is completed.
Meanings of the DelFlag value:
−1: Delete all read messages in the preferred message storage, and keep the
The index is invalid. Check
that index 1 is within the
supported range.
AT+CPBR=<index1>,
<index2>
+CME ERROR: invalid
index
The index is invalid. Check
that index 1 and index 2 are
within the supported range and
that index 1 is not greater than
index 2.
AT+CPBR=<index1>
+CME ERROR: not
found
No entries are found in the
storage locations in index 1.
Check that there have been
entries successfully written into
these locations.
AT+CPBR=<index1>,
<index2>
+CME ERROR: not
found
No entries are found in the
storage locations between
index 1 and index 2. Check
that there have been entries
successfully written into these
locations.
Command
Description
AT+CPBR=?
Query the ranges of parameters related to the
phonebook entries.
+CPBR: (1-250),24,14
OK
AT+CPBW="5","13903702
805",,"test"
Write a phonebook record.
OK
AT+CPBW=1
Delete the entry in index 1 in the phonebook.
OK
6.3.3 Writing/Deleting Phonebook Entries
6.3.4 Reference Process
There are two methods to edit phonebook entries using the AT+CPBW command:
Write an entry to a specified location. This method edits the location where a
phonebook entry exists or writes a new entry to a vacant location.
exists in the location,
the entry will be overwritten.
End
Scenario
Possible Error
Information
Solution
Error information is
returned in response to
one of the previous
+CME ERROR: SIM
busy
Phonebook initialization has
not completed. Try again
later.
Write a new phonebook entry to the next location of a location that already has a
phonebook entry. This method does not require a specified storage location. The
AT+CPBW command can be used to edit phonebook entries of the "SM" or "ON"
type.
Error information is
returned in response to
one of the previous
commands.
+CME ERROR: SIM
busy
Phonebook initialization has
not completed. Try again
later.
+CME ERROR: SIM PIN
required
Enter the correct PIN.
+CME ERROR: SIM
PUK required
Enter the correct PUK.
Command
Description
AT+CSCS=?
Query the character sets supported by the
UE.
+CSCS: ("IRA","GSM","UCS2")
OK
AT+CSCS?
Query the current character set.
+CSCS: "IRA"
OK
AT+CPBR=1
Read the first phonebook entry. The TE
character set is the International
Reference Alphabet (IRA). The content of
the first entry's name field is "HUAWEI".
name field is
004800550041005700450049, which is
"HUAWEI" in the IRA.
OK
AT+CPBR=1
Read the first phonebook entry. The TE
character set is UCS alphabet. The
content of the first entry's name field is
004800550041005700450049 ("HUAWEI"
in the IRA).
Enter the correct PIN. The
original PIN is provided by
the operator.
+CME ERROR: SIM
PUK required
Incorrect PINs have been
entered three times and the
SIM card is blocked. Run
AT+CPIN="<PUK>","<pwd>
" to enter the PUK to unblock
the SIM card. The PUK is
provided by the operator and
cannot be changed by users.
If incorrect PUKs are entered
10 times, the SIM card will be
permanently blocked.
Changes the PIN.
AT+CPWD="SC","<oldpwd
>","<newpwd>"
+CME ERROR:
incorrect password
<oldpwd> must be the
current PIN. Like the PIN
authentication, if incorrect
PINs are entered three times,
the PUK will be required. If
incorrect PUKs are entered
10 times, the SIM card will be
permanently blocked.
Command
Description
AT+CRSM=176,12258,0,0,10
Read the file EFiccid with a transparent
structure. (12258 is 0X2FE2, the
EFiccid file's FID).
+CRSM: 144,0,"<record>"
OK
After the command is processed
successfully, the EFiccid file's content
(<record>) is returned.
AT+CRSM=178,28476,1,4,176,,"7F10"
Use an absolute path to read the first
entry from the EFsms file on the SIM
card's DFtelecom folder.
+CRSM: 144,0,"<record>"
OK
<record> is the content of the first entry.
The length of <record> is 176 bytes.
<response> is the response data of
EFiccid. For details about <response>,
refer to the ETSI TS 102.221 protocol.
AT+CRSM=214,28421,0,0,2,"0012"
Update the content of the transparent
structure EFli file on the SIM card.
+CRSM: 144,0,""
OK
Update succeeded.
AT+CRSM=220,28476,1,4,176,"1111",
"7F10"
Update the content of the linear fixed
structure EFsms file on the SIM card.
+CRSM: 144,0,""
OK
Update succeeded.
AT+CRSM=242
Obtain the current directory information.
+CRSM: 108,"<length>","<status>"
OK
<length> indicates <status>’s length in
byte.
<status> indicates the current directory
status by hexadecimal.
Notes:
To read or update a file, appropriate commands must be used according to the file's
structure type (for details, refer to the description of file properties in the 3GPP TS 31.102
protocol). For transparent structure files, use 176 (Read Binary) and 214 (Update Binary).
For linear fixed structure files, use 178 (Read Record) and 220 (Update Record).
If <pathid> is not contained in the command, the module will prefer to access the files with
the same FID in the current directory.
Files can be accessed only when the access criteria are met. Otherwise the SIM card will
return PSWs indicating that the access authentication failed. If an EF file's read privilege is
PIN protected and the module does not have the PIN authenticated, PSWs indicating that
the access authentication failed will be returned after the +CRSM command is used to read
the EF file.
To use the +CRSM command to access the file content on the SIM card, the parameters
contained in the command must strictly meet the requirements in the ETSI TS 10.2221 and
3GPP TS 31.102. For detailed requirements, refer to the ETSI TS 102.221 and 3GPP TS
As an embedded component in the host, the module also consumes power, which
increases the power consumption of the integrated product. Therefore, the most
important task of power management is to reduce the power consumption of the
integrated product by enabling the module's sleep mode when necessary.
The host and the module need to wake each other up from sleep if communication is
required. Therefore, another task of power management is to provide a wake-up
control mechanism for the host and module.
Power management involves three parts: the host system software (including the
USB driver/UART driver/GPIO driver/sleep mechanism functions), connection
hardware between the host and module, and the module's software wake-up
mechanism.
This chapter is mainly concerned with the module's software wakeup mechanism,
including the wake-up principle, how USB related events impact on the waking up of
the module and remotely waking up the module, and how the module remotely wakes
up the host.
This chapter briefly describes the power management related connection hardware
between the host and module.
This chapter does not describe the host system software. For example, if the host
runs on a Windows or Mac system, Huawei will provide a USB driver program
corresponding to the module. If the host runs on an Android system, Huawei will
provide HUAWEI Module Android RIL Integration Guide for users to configure the
USB-based wakeup function of the module. If the host runs on a Linux system, power
management is supported only when the Linux Kernel version is 2.6.35 or later.
This document describes typical module application scenarios. A host can be
designed based on the actual system features and the application scenarios of the
module to reduce power consumption of both the module and integrated product.
After the host is designed as recommended by this document, the module's power
consumption and the whole unit's power consumption can meet the performance
requirements. For details, see related description in the product manual.
When a wake-up source arrives, this
pin output a low-level-voltage pulse
lasting for 1s during which if other
wake-up sources arrive, the module
will ignore the later wake-up requests.
In other words, the module will not
output a second pulse during this 1s.
Figure 8-1
LGA
WAKEUP_OUT
Output
When a wake-up source arrives, this
pin output a high-level-voltage pulse
lasting for 1s during which if other
wake-up sources arrive, the module
will ignore the later wake-up requests.
In other words, the module will not
output a second pulse during this 1s.
Figure 8-2
LGA
WAKEUP_IN
Input
When the pin carries a high-level
voltage, the states of the module are
as follows:
The module will be prohibited to enter
sleep mode if the module is awake.
The module will be woken up if the
module is in sleep mode.
When the pin carries a low-level
voltage, the module is allowed to enter
sleep mode. (By default, the pin is set
to INPUT/PD, which is, the software
detects a low-level voltage on the pin
when the pin is not connected.)
Figure 8-3
LGA
SLEEP_STATUS
Output
Indicate the state of the module.
When the pin carries a high-level
voltage, the module is in working
mode. When the pin carries a lowlevel voltage, the module is in sleep
mode.
Figure 8-4
The module communicates with the host using mainly USB or UART. For details
about pins related to power management, see Table 8-1 .
For corresponding interface numbers and reference design for the pins, see
Hardware Guide for each product.
The module runs on a multi-task software system. The sleep task is granted with the
lowest priority and assigned to detect whether the module can enter sleep mode.
Other tasks (such as the RF, SIM card, USB) have voting rights. They vote to decide
whether the module can enter sleep mode. When no other tasks are running, the
sleep task is executed. If the sleep task detects that all other tasks agree on the
module's sleep, the module enters sleep mode, as shown in Figure 8-5 . At this time,
the baseband chip reduces the work frequency, and the RF enters the Discontinuous
Reception (DRX) mode.
Figure 8-5 Currency state when the module is in sleep mode
T 2(S EELP )
T 1(W ak eup)
For more information about the module's sleep procedure, see Figure 8-6
Note:
The module's sleep mode is different from working mode or flight mode set using the
AT+CFUN command. The RF will be turned off when the module enters LPM mode using the
command AT+CFUN=0 while the RF will enter DRX mode without being turned off when the
module is in sleep mode. For more details, refer to HUAWEI ME909u-521 LTE LGA Module AT
Command Interface Specification.
The module enters sleep mode automatically when the sleep task detects that all
other tasks agree on the module's sleep. The sleep period of the module depends on
the current working state and circumstance. The period may last for several seconds,
or up to several minutes.
USB is an important communication channel between the module and the host.
According to the USB protocol, normally a hub or a root hub periodically sends Start
of Frame (SOF) data packages (one data package per ms using full-speed USB and
one package per 125 µs using high-speed USB). Through this mechanism, USB
always votes to stop the module from entering sleep mode.
When the USB driver provided by Huawei detects that the module and the host have
not exchanged data in 5 seconds, the USB driver will enable the port's suspend
feature, stopping SOF data packages being sent and suspending the USB controller.
This enables the USB to vote to agree the module's sleep.
If the USB driver used is developed by users or is integrated with external application, ensure
that the USB driver supports the USB suspend features (including selective suspend and
global suspend, as defined in the USB standard.)
8.3.3 UART and Sleep
UART is an important communication channel between the module and the host. If
the host uses UART (a TTL level Interface), it can connect to the module's UART
directly. If the host uses RS232, it can connect to the module's UART through a
conversion chip such as MAX232.
Note:
If the module is in sleep state, the host send data to module only by UART that can’t wakeup
the module. It must be used with WAKEUP_IN pin.
8.3.4 Module Wake-up
RF periodically wakes up the module based on the DRX cycle (depending on the
actual configuration of the network system), as shown in Figure 8-5 .
Other aperiodic events include:
1. The host sends data using USB or pulls WAKEUP_IN up.
2. Changes on the network, for example, an incoming call, 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.
8.3.5 Host Woken up by Module
Wake-up Source
A wake-up source is a module event that can wake up the host, for example, an
incoming voice call, a text message, data (PPP data, TCP/UDP data from the
network), and unsolicited messages.
Remotely Waking up the Host Using USB
When the host is in sleep mode and the USB controller is in suspended mode, if the
module needs to send data to the host (for example, a wake-up source has arrived),
the module sends a remote wake-up signal that lasts 3 ms to inform the host to start
USB resume (as shown in Figure 8-7 ). To complete the procedure, the following
conditions must be met:
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
FS idle FSK HS idle uSOF
D+
D-
HS HubHS Device
Start of
Resume
Signaling
3ms
Device sees
first activity
Start of
Resume
Signaling
>20ms
<3.0ms
Signaling
Signaling
<1.33us
Device
Resumed
if remote
wake up
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 state. Otherwise, the module enters suspended mode again,
as shown in Figure 8-7 .
Figure 8-7 USB resume time sequence
Figure 8-8 Successful procedure of remote wake-up
WAKEUP_OUT Waking up the Host
The module will output a 1s pulse using WAKE# as shown in Figure 8-1 or
WAKEUP_OUT as shown in Figure 8-2 when a wake-up source arrives. The host
wakes itself up after detecting the level change.
Configure the module to make sure
that incoming calls, text messages,
data, and unsolicited messages can
remotely wake up the host using
USB.
OK
AT^CURC=?
Query the parameter range of
CURC.
^CURC: (0-2)
OK
AT^CURC=2,820,1FFFFFFFFFFFFFFF
The host wakes up from sleep if any
of the following occurs: The SIM
card state changes such as the SIM
card is removed (^SIMST); the
number of text messages exceeds
the limit (^SMMEMFULL). Other
unsolicited messages are saved in
The power consumption of the host increases if it is frequently woken up. The host
can configure the module's wake-up sources using ^WAKEUPCFG and ^CURC
command so as to reduce the power consumption.
The ^WAKEUPCFG command can be used to choose wake-up sources and the
wake-up channel (USB or WAKEUP_OUT). The ^CURC command can choose
unsolicited messages. For more details, refer to AT Command Interface Specification.
8.4 Application Scenarios: System with USB Connection
only
A host running Android, with support for USB suspend, USB remote resume, voice
calling, and text messages.
the cache when the host is in sleep
mode, and reported to the host
when it wakes up.
OK
Command
Description
AT^WAKEUPCFG=?
Query the parameter range of
WAKEUPCFG.
^WAKEUPCFG: (0-1),(0-3),(0-15)
OK
AT^WAKEUPCFG=1,1,14
Configure the module to make sure
that text messages, data, and
unsolicited messages can remotely
wake up the host using the
WAKEUP_OUT pin.
OK
AT^CURC=?
Query the parameter range of CURC.
^CURC: (0-2)
OK
AT^CURC=2,820,1FFFFFFFFFFFFFFF
The host wakes up from sleep if
either of the following occurs: The
SIM card state changes, such as the
SIM card is removed (^SIMST); the
8.4.3 Advantages
With software configuration, while the system requirements (calling and text
messages) are met, the number of times the host is woken up by unsolicited
messages, and consequently the power consumption, are reduced.
8.5 Application Scenarios: System with USB and
WAKEUP_OUT
A host running Android, with support for text messages, but not USB remote resume
or voice calling.
8.5.1 Hardware Connection
The host must connect to the module using USB and WAKEUP_OUT pins
number of text messages exceeds
the limit (^SMMEMFULL). Other
unsolicited messages are saved in
the cache when the host is in sleep
mode, and reported to the host when
it wakes up.
When the host is awake, unsolicited
messages are reported to the host.
OK
8.5.3 Advantages
A solution is provided for systems not supporting USB remote resume.
With software configuration, while the system requirements (calling and text
messages) are met, the number of times the host is woken up by unsolicited
messages, and consequently the power consumption, are reduced.
8.6 System with Other Connection Methods
If the host can be connected to the module only using UART, refer to the HUAWEI
ME909 Series LTE LGA Module Brief Hardware Guide. If the host can connect to the
module using USB/UART/WAKEUP_OUT and can support USB remote wake-up and
UART remote wake-up, prioritize USB remote wake-up over WAKEUP_OUT remote
wake-up. For details about the software procedure, refer to the earlier sections while
considering the host system feature.
Enable the thermal protection
unsolicited indication when the
module is working or in sleep
mode.
OK
^THERM: 1
When the temperature is higher
than the temperature protection
threshold, the module enables
thermal protection: The module
turns off its RF and reports to the
host.
^THERM: 0
When the temperature is lower than
the temperature protection
hysteresis threshold, the module
disables thermal protection: turns
on its RF and reports to the host.
9.1 Pre-configuration
9.1.1 Troubleshooting
None
9.2 Thermal Protection Process
When the module's temperature is lower than 99°C , the module works normally.
When the module's temperature is higher than 99°C , the module enables
thermal protection: turns off its RF transmission and presents the ^THERM: 1
indication. When the module's temperature is lower than 85°C , the module
disables thermal protection: turns on its RF transmission, and presents the
^THERM: 0 indication.
Notes:
During an emergency call, if thermal protection is enabled, the module will present an
indication but will not take thermal protection actions such as turning off its RF or shutting
down.
After thermal protection is enabled, users cannot make emergency calls.
Thermal protection is designed to protect the module from being damaged by
overtemperature. To work in high temperature environments, both the module and its
peripheral components must be able to resist the same temperature.
The ME can be reset or restarted using the AT+CFUN command. After the restart,
the module must register with the network and authenticate its SIM card’s PIN.
10.1.2 Troubleshooting
None
10.2 Power Off ME
10.2.1 Reference Process
After the command is received, the module will only do the preparative work of
power-off such as deregister. The host should cut off the power in order to finish the
power-off operation.