M10 ATC - Quectel

M10 ATC - Quectel
U10
Quectel Cellular Engine
U10 SMS
Application Note
U10_SMS_Application_Note_V1.0
U10 SMS Application Note
Document Title:
U10 SMS Application Note
Revision:
1.0
Date:
2012-04-13
Status:
Released
Document Control ID:
U10_SMS_Application_Note_V1.0
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
General Notes
Quectel offers this information as a service to its customers, to support application and
engineering efforts that use the products designed by Quectel. The information provided is
based upon requirements specifically provided for Quectel by the customers. Quectel has not
undertaken any independent search for additional relevant information, including any
information that may be in the customer’s possession. Furthermore, system validation of this
product designed by Quectel within a larger electronic system remains the responsibility of
the customer or the customer’s system integrator. All specifications supplied herein are
subject to change.
Copyright
This document contains proprietary technical information which is the property of Quectel
Limited. The copying of this document, distribution to others, and communication of the
contents thereof, are forbidden without express authority. Offenders are liable to the payment
of damages. All rights are reserved in the event of a patent grant or registration of a utility
model or design. All specification supplied herein are subject to change without notice at any
time.
Copyright © Quectel Wireless Solutions Co. Ltd. 2012
U10_SMS_Application_Note_V1.0
-1-
U10 SMS Application Note
Contents
Contents ............................................................................................................................................ 2
Table Index........................................................................................................................................ 4
0. Revision history ............................................................................................................................ 6
1. Introduction ................................................................................................................................... 7
1.1. Reference ..................................................................................................................................... 7
1.2. Overview ...................................................................................................................................... 9
1.2.1.Select SMS Message Format (+CMGF) ............................................................................ 10
1.2.2. Select TE Character Set (+CSCS) ..................................................................................... 10
1.2.3. Set service center address (+CSCA) ................................................................................. 11
1.2.4. Set preferred message storage (+CPMS) .......................................................................... 12
2. SMS in text mode ........................................................................................................................ 13
2.1. Write and send short message ................................................................................................... 13
2.1.1. Set text mode parameter (+CSMP) ................................................................................... 13
2.1.2. Send message directly from terminal (+CMGS) .............................................................. 14
2.1.3. Write short message to storage (+CMGW) ...................................................................... 14
2.1.4. Send short message from storage (+CMSS) ..................................................................... 15
2.2. Receive and read short message ............................................................................................... 15
2.2.1. Show text mode parameters (+CSDH) ............................................................................. 16
2.2.2. New message indication (+CNMI) ................................................................................... 16
2.2.3. Read short message (+CMGR).......................................................................................... 18
2.2.4. List short messages from preferred storage (+CMGL) .................................................... 19
2.3. Status report ............................................................................................................................... 20
2.4. Delete short messages ............................................................................................................... 21
2.4.1. Delete One or all Short Message (+CMGD) .................................................................... 21
2.4.2. Delete all short messages (+QMGDA) ............................................................................. 21
2.5. Examples in text mode .............................................................................................................. 22
2.5.1. Send English short message(GSM coding) and not require status report ...................... 22
2.5.2. Send Chinese short message(UCS2 coding) and require status report ........................... 25
3. SMS in PDU mode ...................................................................................................................... 27
3.1. Write and Send Short Message ................................................................................................. 27
3.1.1. Send Message direct from Terminal (+CMGS)................................................................ 27
3.1.2. Write short message to storage (+CMGW) ...................................................................... 27
3.2. Receive and read short message ............................................................................................... 28
3.2.1. Read Short Messages (+CMGR) ....................................................................................... 28
3.2.2. List short messages from preferred storage (+CMGL) .................................................... 28
3.3. Status report ............................................................................................................................... 29
3.4. Delete short messages ............................................................................................................... 29
3.5. Basic elements of the PDU ....................................................................................................... 29
3.5.1. SMS-Submit PDU packet (MO)........................................................................................ 30
3.5.2. SMS-Deliver PDU packet (MT)........................................................................................ 30
3.5.3. SMS-Status Report Packet ................................................................................................. 30
3.5.4. Element descriptions .......................................................................................................... 30
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
-2-
U10 SMS Application Notes
3.6. Examples in PDU mode ............................................................................................................ 36
3.6.1. Send English short message(GSM coding) and not require status report ...................... 37
3.6.2. Send Chinese short message(UCS2 coding) and require status report ........................... 39
4. Other Commands with SMS ....................................................................................................... 43
4.1. Save and restore SMS settings .................................................................................................. 43
4.1.1. Save SMS settings (+CSAS) ............................................................................................. 43
4.1.2. Restore SMS Settings (+CRES) ........................................................................................ 43
4.1.3. Save other settings.............................................................................................................. 43
4.2. Store Class 0 SMS to <mem3> when received Class 0 SMS (+QCLASS0)......................... 44
4.3. Notify SMS is full (+QEXTUNSOL) ...................................................................................... 45
5. Appendix ..................................................................................................................................... 47
5.1. Message service send and write procedures ............................................................................ 47
5.2. Message receiving procedures .................................................................................................. 48
5.3. Default GSM alphabet............................................................................................................... 48
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
-3-
U10 SMS Application Notes
Table Index
TABLE 1: REFERENCE................................................................................................................... 7
TABLE 2: RELATED AT COMMANDS .......................................................................................... 7
TABLE 3: TERMS AND ABBREVIATIONS................................................................................... 8
TABLE 4:TYPES OF AT COMMANDS AND RESPONSES .......................................................... 9
TABLE 5: AT+CMGF SYNTAX .................................................................................................... 10
TABLE 6: AT+CSCS SYNTAX ...................................................................................................... 10
TABLE 7: AT+CSCA SYNTAX...................................................................................................... 11
TABLE 8: AT+CPMS SYNTAX ..................................................................................................... 12
TABLE 9: AT+CSMP SYNTAX IN TEXT MODE ......................................................................... 13
TABLE 10: AT+CMGS SYNTAX IN TEXT MODE ...................................................................... 14
TABLE 11: AT+CMGW SYNTAX IN TEXT MODE..................................................................... 14
TABLE 13: AT+CSDH SYNTAX IN TEXT MODE....................................................................... 16
TABLE 14: AT+CNMI SYNTAX ................................................................................................... 16
TABLE 15: AT+CMGR SYNTAX IN TEXT MODE ..................................................................... 18
TABLE 16:: AT+CMGL SYNTAX IN TEXT MODE ..................................................................... 19
TABLE 17: AT+CMGD SYNTAX.................................................................................................. 21
TABLE 18: AT+QMGDA SYNTAX IN TEXT MODE .................................................................. 21
TABLE 19: AT+CMGS SYNTAX IN PDU MODE ........................................................................ 27
TABLE 20: AT+CMGW SYNTAX IN PDU MODE....................................................................... 27
TABLE 21: AT+CMGR SYNTAX IN PDU MODE........................................................................ 28
TABLE 22: AT+CMGL SYNTAX IN PDU MODE ........................................................................ 28
TABLE 23: SMS-SUBMIT PACKET ............................................................................................. 30
TABLE 24: SMS-DELIVER PACKET ........................................................................................... 30
TABLE 25: STATUS-REPORT PACKET ....................................................................................... 30
TABLE 26: <TOA> ......................................................................................................................... 30
TABLE 27: <SCA> ......................................................................................................................... 31
TABLE 28: <OA>/<DA>/<RA>..................................................................................................... 31
TABLE 29: <FO> ELEMENTS ...................................................................................................... 32
TABLE 30: <PID> .......................................................................................................................... 33
TABLE 31:<DCS> .......................................................................................................................... 33
TABLE 32: <VP> RELATIVE FORMAT ....................................................................................... 35
TABLE 33: <SCTS> ....................................................................................................................... 35
TABLE 34: AT+CSAS SYNTAX .................................................................................................... 43
TABLE 35: AT+CRES SYNTAX .................................................................................................... 43
TABLE 36: AT+QCLASS0 SYNTAX............................................................................................. 44
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
-4-
U10 SMS Application Notes
Figure Index
FIGURE 1: <MODE> PARAMETER ............................................................................................. 17
FIGURE 2: MESSAGE SERVICE SEND AND WRITE PROCEDURES ..................................... 47
FIGURE 3: MESSAGE RECEIVING PROCEDURES .................................................................. 48
FIGURE 4: DEFAULT GSM ALPHABET ..................................................................................... 49
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
-5-
U10 SMS Application Notes
0. Revision history
Revision
Date
Author
Description
1.0
2012-03-23
Joanna Li
Initial
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
-6-
U10 SMS Application Note
1. Introduction
This document describes how to use Point to Point Short Message Service (SMS) through Hyper
Terminal by AT commands which Quectel’s module provides. The Cell Broadcast Service (CBS)
is not included in this document.
1.1. Reference
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Table 1: Reference
SN
[1]
[2]
[3]
[4]
[5]
[6]
[7]
Document name
Remark
U10_ATC
U10 AT Commands Set
3GPP TS 27.005 (GSM 07.05)
Equipment interface for SMS and CBS
3GPP TS 23.038 (GSM 03.38)
Alphabets and language-specific information
3GPP TS 23.040 (GSM 03.40)
Technical realization of the Short Message Service
3GPP TS 27.007 (GSM 07.07)
AT commands set for WCDMA Mobile Equipment
(ME)
3GPP TS 24.011 (GSM 04.11)
PP SMS support on mobile radio interface
3GPP TS 24.008 (GSM 04.08)
Mobile radio interface Layer 3 specification; Core
network protocols; Stage 3
Table 2: Related AT commands
AT command
Description
Reference
AT+CMGF
SELECT SMS MESSAGE FORMAT
3GPP TS 27.005
AT+CSCS
SELECT TE CHARACTER SET
3GPP TS 27.007
AT+CSCA
SMS SERVICE CENTER ADDRESS
3GPP TS 27.005
AT+CSMP
SET SMS TEXT MODE PARAMETERS
3GPP TS 27.005
AT+CNMI
NEW SMS MESSAGE INDICATIONS
3GPP TS 27.005
AT+CMGW
WRITE SMS MESSAGE TO MEMORY
3GPP TS 27.005
AT+CMSS
SEND SMS MESSAGE FROM STORAGE
3GPP TS 27.005
AT+CMGS
SEND SMS MESSAGE
3GPP TS 27.005
AT+CMGR
READ SMS MESSAGE
3GPP TS 27.005
AT+CMGL
LIST SMS MESSAGES FROM PREFERRED
STORE
3GPP TS 27.005
AT+CMGD
DELETE SMS MESSAGE
3GPP TS 27.005
AT+QMGDA
DELETE ALL SMS MESSAGES
Quectel defined
AT+CSDH
SHOW SMS TEXT MODE PARAMETERS
3GPP TS 27.005
AT+CSAS
SAVE SMS SETTINGS
3GPP TS 27.005
AT+CRES
RESTORE SMS SETTINGS
3GPP TS 27.005
AT+CPMS
PREFERRED SMS MESSAGE STORAGE
3GPP TS 27.005
AT+QCLASS0
STORE CLASS 0 SMS TO SIM WHEN
RECEIVED CLASS 0 SMS
Quectel defined
U10_SMS_Application_Note_V1.0
-7-
U10 SMS Application Notes
AT+QEXTUNSOL
ENABLE/DISABLE
PROPRIETARY Quectel defined
UNSOLICITED INDICATIONS
Table 3: Terms and abbreviations
Abbreviation
Description
SMS
Short Message Service
SME
Short Message Entity
SMSC/SC
Short Message Service Center
MO
Mobile Originated
MT
ME
MS
TE
TA
PDU
TP
URC
TOA
TON
NPI
FO
MR
OA
DA
RA
PID
DCS
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Mobile Terminated
Mobile Equipment
Mobile Station, Mobile Equipment plus a SIM card
Terminal Equipment
Terminal Adaptor
Protocol Data Unit
Transfer Layer Protocol
Unsolicited Result Code
Type of Address
Type of Number
Numbering Plan Identification
First Octet
Message Reference
Originator Address
Destination Address
Recipient Address
Protocol Identifier
Data Coding Scheme. Refer to [3]3GPP TS 23.038 (GSM 03.38)
SCTS
Service Center Time Stamp
DT
Discharge Time
VP
VPF
Validity Period
Validity Period Format
UDL
User Data Length
UD
User Data
UDHI
User Data Header Indicator
RP
Reply Path
SRI
Status Report Indication
SRR
Status Report Request
SRQ
Status Report Qualifier
RD
Reject Duplicate
ST
Status
PI
Parameter Identifier
MTI
Message Type Indicator
U10_SMS_Application_Note_V1.0
-8-
U10 SMS Application Notes
MMS
More Messages to Send
&b
Binary Format
&h
Hexadecimal Format
&d
Decimal Format
1.2. Overview
The SMS provides a way to transfer short messages between Mobile Stations (MS) via a Service
Center (SC). The SMS service comprises three basic services:
 SMS-Submit (SM-Mobile Originated): the module sends a SM to the SC.
 SMS-Deliver (SM-Mobile Terminated): the module receives a SM from the SC.
 SMS Status Report: the message which indicates whether a MO message is received by
destination address correctly.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Note:
Preparation before using Hyper Terminal:
1. Connect the EVB of the module to PC through a serial cable.
2. Start the Hyper Terminal procedure on the computer, and set the same baud rate as the
module’s. (Default is autobauding for module).
3. Make sure the Quectel module and the SIM card are assembled on EVB, then power on the
module.
Table 4:Types of AT Commands and responses
Test Command
AT+<x>=?
This command returns the list of parameters and
value ranges set with the corresponding Write
Command or by internal processes.
Read Command
AT+<x>?
This command returns the currently set value of the
parameter or parameters.
Write Command
AT+<x>=<…>
This command sets the user-definable parameter
values.
 AT commands are case-insensitive, but the parameters may be case-sensitive. And press
Enter (<CR>) to execute command.
 In the examples of this document, the blue text are the commands or parameters which user
should input in Hyper Terminal, and text after “//” are descriptions, others are responses for
your input or URC.
 Possible response maybe ERROR, +CME ERROR: <err>, or +CMS ERROR: <err>.
Please refer to the document [1] Uxx_ATC document for the meaning of error code <err>.
U10_SMS_Application_Note_V1.0
-9-
U10 SMS Application Notes
1.2.1. Select SMS Message Format (+CMGF)
There are two modes when using AT commands to send, receive, list, read and write message: text
mode and PDU mode. In text mode, you can write your message as text and set parameters for
sending and receiving by some AT commands. In PDU mode, you must write your messages in
fixed hexadecimal format, of which parameters are included in the PDU package.
The mode sets by command AT+CMGF. See table below.
Table 5: AT+CMGF Syntax
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Command
Possible Response
Example
Comment
AT+CMGF=?
+CMGF: (list of supported
<mode>s)
+CMGF: (0,1)
List of supported modes
AT+CMGF?
+CMGF: <mode>
+CMGF: 0
Return current mode
AT+CMGF=0
Set PDU mode. It is default.
AT+CMGF=1
Set Text mode
AT+CMGF=<
mode>
OK
Section 2 introduces how to send and read SM and status report in text mode. Section 3 introduces
AT commands in PDU mode. Section 4 introduces other AT commands related with SM.
1.2.2. Select TE Character Set (+CSCS)
AT+CSCS sets character set <chset> used by the TE. The TA can then convert character strings
correctly between the TE and ME. The character set will affect transmission and reception of
SMS.
Table 1: AT+CSCS Syntax
Command
Possible Response
Example
AT+CSCS=?
+CSCS: (list of
supported <chset>s)
+CSCS:
("GSM","HEX","IRA","PCCP437","UCS2","
8859-1")
AT+CSCS?
+CSCS: <chset>
+CSCS: "GSM" (default)
AT+CSCS=<chset>
OK
AT+CSCS="GSM"
OK
Parameter <chset>
"GSM"
GSM default alphabet, 7-bit coded ([3]3GPP TS 23.038 (GSM 03.38) subclause
6.2.1, or Appendix 5.3 in this document).
"HEX"
Character strings consist only of hexadecimal numbers from 00 to FF.
"IRA"
International reference alphabet (ITU-T T.50)
"PCCP437"
PC character set Code
"UCS2"
UCS2 alphabet. 16-bit universal multiple-octet coded character set (ISO/IEC
10646)
U10_SMS_Application_Note_V1.0
- 10 -
U10 SMS Application Notes
"8859-1"
ISO 8859 Latin 1 character set
Note:
 For English message, recommended to select “GSM” in most cases. And for other
languages, it’s better to select “UCS2”. Unicode of characters can be found easily by some
tools, for example, Windows charmap.exe, or Excel Symbol dialog. Please go to unicode.org
for more information about Unicode and UCS2. Also you can find mappings from
GSM/PCCP437/8859-1 to unicode.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
1.2.3. Set service center address (+CSCA)
Service Center (SC) is responsible for the relaying and store-and-forwarding of a short message.
To use the SMS function, you have to declare the number of the SMSC in the MS (Mobile
Station). However, SMSC is provided by network provider, and saved in SIM card as factory
setting. It is highly recommended that you do NOT change it at any time. And it’s better to
check it before sending short message.
Table 2: AT+CSCA Syntax
Command
Possible Response
AT+CSCA=?
OK
AT+CSCA?
+CSCA: <sca>,<tosca>
AT+CSCA=<sca>[,<tosca>]
OK
Parameters:
<sca>
SC Address in string format
<tosca>
Type of SCA in integer format
<tosca> uses <TOA> (Type of Address) decimal format (see [4] 3GPP TS 23.040 (GSM 03.40)
sub clause 9.1.2.5).
Example:
AT+CSCS?
+CSCS: "GSM"
OK
AT+CSCA?
+CSCA: "+8613010314500",145
OK
AT+CSCS="UCS2"
OK
AT+CSCA?
+CSCA: "002B0038003600310033003000310030003300310034003500300030",145
U10_SMS_Application_Note_V1.0
- 11 -
U10 SMS Application Notes
OK
Note:
 Recommended to store every address in International numbering format to avoid problems
while roaming.
 Ask your local network provider for the right SMSC number.
 It is highly recommended that you do NOT change it at any time. And it’s better to check it
before sending short message.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
1.2.4. Set preferred message storage (+CPMS)
AT+CPMS selects memory storages used for reading, writing, receiving and etc.
Table 3: AT+CPMS Syntax
Command
Possible Response
Example
AT+CPMS=
?
+CPMS: (list of supported <mem1>s),(list
of supported <mem2>s) ,(list of supported
<mem3>s)
+CPMS: ("SM", "ME", "MT"),
("SM", "ME", "MT"), ("SM",
"ME", "MT")
AT+CPMS?
+CPMS:
<mem1>,<used1>,<total1>,<mem2>,<use
d2>,<total2>,<mem3>,<used3>,<total3>
+CPMS:
"SM",10,50,"SM",10,50,"SM",10
,50
AT+CPMS=
<mem1>[,<
mem2>[,<me
m3>]]
+CPMS:
<used1>,<total1>,<used2>,<total2>,<used
3>,<total3>
Parameters
<mem1>/<mem2>/<mem3>
Memory storage <memx>:
Messages to be read and deleted from <mem1>.
Messages will be written and sent to <mem2>.
Received messages will be placed in <mem3> if routing to PC is
not set (see +CNMI)
<memx>'s value can be storage of “SM” (SIM), “ME”, or
“MT”(SM+ME).
<used1>/<used2>/<used3>
Number of messages currently stored in <memx> in integer
format
<total1>/<total2>/<total4>
Maximum number of messages that can be stored in <memx> in
integer format
Note:
 The maximum number of short messages is 650, and the maximum number in SIM card is
200, and the number in the module is 450.
U10_SMS_Application_Note_V1.0
- 12 -
U10 SMS Application Notes
2. SMS in text mode
2.1. Write and send short message
Two methods can be used to send a short message. The first method is to send message directly by
+CMGS, the second is to write message to storage (+CMGW), then forward it to destination by
+CMSS. Before sending short message, some parameters should be set by AT command +CSMP.
l
e
l
t
e
l
c
l
t
a
a
e
i
c
t
i
e
u
t
n
u
QQ iddeen
f
i
n
f
n
o
o
C
C
2.1.1. Set text mode parameter (+CSMP)
AT+CSMP sets SMS parameters for text mode.
Table 4: AT+CSMP Syntax in text mode
Command
Possible Response
Example
AT+CSMP=?
+CSMP: (list of supported <fo>s),(list of
supported <vp>s),(list of supported
<pid>s),(list of supported <dcs>s)
+CSMP:
(17,49),(0-255),(0-255),(0255)
AT+CSMP?
+CSMP: <fo>,<vp>,<pid>,<dcs>
+CSMP: 17,71,0,0
AT+CSMP=[<fo>[,
<vp>[,pid>[,<dcs>]]
]]
OK
Recommended <+CSCS> and <dcs> in text mode:
English
other language
Store message
+CSCS="GSM"
<dcs>=0
+CSCS="UCS2"
<dcs>=25
Immediately display
message and DO not
store message
+CSCS="GSM"
<dcs>=240
+CSCS="UCS2"
<dcs>=24
Note:
 When writing message, +CSCS and <dcs> should match each other. For example, if you
select UCS2 character set by +CSCS, but set 7-bit coding schema in <dcs>, then messy code
may be gotten by SMS receiver.
 The meaning of parameter <fo>,<vp>,<pid>,<dcs> is the same as which is in the PDU
mode. Their value and meaning are listed in the following section 3.5:Basic elements of the
PDU. And the difference is that decimal format is used in the parameters of +CSMP in text
mode while hexadecimal format is used in PDU mode.
U10_SMS_Application_Note_V1.0
- 13 -
U10 SMS Application Notes
2.1.2. Send message directly from terminal (+CMGS)
Table 5: AT+CMGS Syntax in text mode
Command
Possible Response
AT+CMGS=?
OK
Example
Send English characters “TEST” to
13795403834:
AT+CSCS=”GSM”
AT+CMGS=”13795403834”
>TEST <Ctrl+Z>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
AT+CMGS=<da>[,<tod
a>]<CR>
>text is entered
<ctrl-Z/ESC>
+CMGS: <mr>
or +CMS ERROR:
<err>
Send Chinese characters “ 测 试 ” to
13795403834:
AT+CSCS=”UCS2”
AT+CMGS=”
003100330037003900350034003000330038
00330034”
>6D4B8BD5 <Ctrl+Z>
Parameters:
<da>
[4] 3GPP TS 23.040 (GSM 03.40) TP-Destination-Address in string format
<toda>
Type of <da> in integer format, see Type Of Address
<mr>
See below section 3.5 Basic elements of the PDU
<Ctrl+Z> (Press Ctrl and Z simultaneously) is used to finish the inputting and begin to send short
message. Esc is used to cancel the operation.
Note:
 If +CSCS=”UCS2”, <da> should be input in UCS2 format.
2.1.3. Write short message to storage (+CMGW)
Table 6: AT+CMGW Syntax in text mode
Command
Possible Response
AT+CMGW=?
OK
AT+CMGW=<oa/da>[,<tooa/toda>[,<stat>]]<CR>
> <text is entered >
<ctrl-Z/ESC>
+CMGW: <index>
or +CMS ERROR: <err>
Parameters:
 <da> <toda> and message text are the same as the AT command +CMGS.
 <stat>: By default message status will be set to “STO UNSENT”, but parameter <stat>
allows “STO SENT” to be given.
U10_SMS_Application_Note_V1.0
- 14 -
U10 SMS Application Notes
The message written by +CMGW will be stored in <mem2> (see +CPMS). The correct write
command will return the index in <mem2>, and then this message can be sent by AT command
+CMSS as below.
2.1.4. Send short message from storage (+CMSS)
Table 7: AT+CMSS Syntax in text mode
Command
Possible Response
AT+CMSS=?
OK
AT+CMSS=<index>[,<da>[,<toda>]]
+CMSS: <mr>
OK
or +CMS ERROR: <err>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Example:
AT+CMGW="15021012496"
> test <Ctrl+Z>
+CMGW: 54
//Write message successfully and the index is 54
OK
AT+CMSS=54
+CMSS: 122
//Send message to <da> "15021012496" which is set in CMGW
OK
AT+CMSS=54,"13795403834"
//Send message to new <da> "13795403834" instead of the
one stored with the message
+CMSS: 123
OK
Note:
 If <da> is given in this command, it shall be used instead of the one stored with the message,
that is, the message will be sent to <da> in this command.
 No difference in PDU mode and text mode for +CMSS.
2.2. Receive and read short message
When short message is received, how to handle it (how to display URC, where to save) will be
decided by AT command +CNMI and message class type defined in <dcs>. User can read message
content from URC or +CMGR/+CMGL if saved. +CSDH will decide which information will be
displayed in text mode.
U10_SMS_Application_Note_V1.0
- 15 -
U10 SMS Application Notes
2.2.1. Show text mode parameters (+CSDH)
Table 8: AT+CSDH Syntax in text mode
Command
Possible Response
Example
AT+CSDH=?
+CSDH: (list of supported <show>s)
+CSDH: (0, 1)
AT+CSDH?
+CSDH: <show>
+CSDH: 0
AT+CSDH=[<show>]
OK
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Parameter <show> value
0
1
not show (default)
show
<show> defines whether to show header values defined in AT commands +CSCA and +CSMP
(<sca>, <tosca>, <fo>, <vp>, <pid> and <dcs>) nor <length>, <toda> or <tooa> in +CMT,
+CMGL, +CMGR result codes for SMS-DELIVERs and SMS-SUBMITs in text mode
Note:
 This command only affects text mode.
2.2.2. New message indication (+CNMI)
Table 9: AT+CNMI Syntax
Command
Possible Response
Example
AT+CNMI=?
+CNMI: (list of supported <mode>s),(list of
supported <mt>s),(list of supported <bm>s),(list of
supported <ds>s),(list of supported <bfr>s)
+CNMI:
(0-3), (0-3),
(0,2,3),
(0,1), (0,1)
AT+CNMI?
+CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>
+CNMI:
2,1,0,0,0
(default)
AT+CNMI=[<mode>[,<
mt>[,<bm>
[,<ds>[,<bfr>]]]]]
OK
or
ERROR
TA selects the procedure for how the receiving of new messages from the network is indicated to
the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF),
message receiving should be done as specified in 3GPP TS 23.038.
<mode> controls the processing of URC specified within this command.
<mode> values: refer to the figure below ([2]3GPP TS 27.005 (GSM 07.05) Section 3 Figure 2)
U10_SMS_Application_Note_V1.0
- 16 -
U10 SMS Application Notes
0
Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can
be buffered in some other place or the oldest indications may be discarded and replaced
with the new received indications.
1
Discard indication and reject new received message unsolicited result codes when
TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to
the TE.
2
Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line
data mode) and flush them to the TE after reservation. Otherwise forward them directly
to the TE. (Recommended, default)
3
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Forward unsolicited result codes directly to the TE. TA-TE link specific inband
technique used to embed result codes and data when TA is in on-line data mode.
ME
received messages and indications
<mode> value
0
COMMAND
MODE
DATA MODE
1
TA
2
Buffer
3
+CMTI, +CMT, +CBMI, +CBM, +CDSI, +CDS unsolicited result codes
TE
Figure 1: <mode> parameter
<mt> values:
The rules for storing received SMs depend on <dcs>, preferred memory storage <mem3> setting
(+CPMS) and this value.
0
1
2
3
No SMS-DELIVER indications are routed to the TE.
If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to
the TE using unsolicited result code: +CMTI: <mem>,<index>
SMS-DELIVERs (except class 2) are routed directly to the TE using unsolicited result
code: +CMT: [<alpha>],<length><CR><LF><pdu> (PDU mode enabled)
or
+CMT: <oa>, [<alpha>],<scts>
[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<CR><LF><data>
(text mode enabled; about parameters in italics, refer to Command Show Text Mode
Parameters +CSDH).
Class 2 messages result in indication as defined in <mt>=1: +CMTI
Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined
in <mt>=2: +CMT
Messages of other classes result in indication as defined in <mt>=1: +CMTI
<bm> value affects CBMs and so it is ignored in this document.
U10_SMS_Application_Note_V1.0
- 17 -
U10 SMS Application Notes
<ds> value sets whether to route SMS-STATUS-REPORT or not
0
No SMS-STATUS-REPORTs are routed to the TE.
1
SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:
+CDS: <length><CR><LF><pdu> (PDU mode enabled)
or
+CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st> (Text mode enabled)
<bfr> values:
0
1
TA buffer of unsolicited result codes defined within this command is flushed to the TE
when <mode> 1...3 is entered (OK response shall be given before flushing the codes).
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
TA buffer of unsolicited result codes defined within this command is cleared when
<mode> 1...3 is entered
Note:
 It’s strongly recommended to set <mode> as 2, in this way, the message indication will not
be lost. It’s the default setting.
 As to <mt>, if user wants to store the message, set it as 1 (AT+CNMI=2,1 default), then get
URC +CMTI: <mem>,<index> and read the message AT+CMGR=<index>. If user wants
to read the message directly, set it as 2 (AT+CNMI=2,2), then get the message content from
URC +CMT.
 Please refer to [2]3GPP TS 27.005 (GSM 07.05) Clause 3 Figure 3 or appendix 5.2 in this
document for message receiving procedures.
2.2.3. Read short message (+CMGR)
Table 10: AT+CMGR Syntax in text mode
Command
Possible Response in Text Mode
AT+CMGR=?
OK
AT+CMGR=<in
dex>[,<mode>]
For SMS-DELIVER in Text Mode:
+CMGR:
<stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<l
ength>]<CR><LF><data>
For SMS-SUBMIT in Text Mode:
+CMGR:
<stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<l
ength>]<CR><LF><data>
TA returns short message with location value <index> from message storage <mem1> (+CPMS)
to the TE.
<index>
Integer type; value in the range of location numbers supported by the associated
memory
<mode>
0
Normal. If status of the message is 'received unread', status in the storage
changes to 'received read'.
U10_SMS_Application_Note_V1.0
- 18 -
U10 SMS Application Notes
1
Not change status of the specified SMS record
Example:
Write and read
SM:
AT+CMGW
> test<CTRL+Z>
+CMGW: 6
OK
AT+CSDH=0
AT+CSDH=1
AT+CMGR=6
+CMGR: "STO
UNSENT","",""
test
AT+CMGR=6
+CMGR: "STO
UNSENT","","",0,49,0,0,71,"",0,4
test
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
OK
+CMTI: "SM",3
AT+CMGR=3
+CMGR: "REC
UNREAD","+86150210124
96","","2010/08/18
17:29:12+32"
test
Receive and read
SM:
AT+CNMI=2,1,0,0,
0
OK
Receive and display
SM directly:
AT+CNMI=2,2,0,0,
0
+CMT:
"+8615021012496",,"2010/0
8/18 17:32:02+32"
test
OK
+CMTI: "SM",4
AT+CMGR=4
+CMGR: "REC
UNREAD","+8615021012496","","201
0/08/18
17:37:23+32",145,4,0,241,"+86130103
14500",145,4
test
+CMT:
"+8615021012496",,"2010/08/18
17:26:52+32",145,4,0,0,"+8613010314
500",145,4
test
Note:
 The difference of text mode and PDU mode: only the response format.
2.2.4. List short messages from preferred storage (+CMGL)
Table 11: AT+CMGL Syntax in text mode
Command
Possible Response
AT+CMGL=?
OK
or +CMS ERROR: <err>
AT+CMGL=<sta
t>[,<mode>]
for SMS-SUBMITs and/or SMS-DELIVERs:
+CMGL:
<index>,<stat>,<oa/da>,[<alpha>],[<scts>][,<tooa/toda>,<length>]<CR>
<LF><data>[<CR><LF>
+CMGL:
<index>,<stat>,<da/oa>,[<alpha>],[<scts>][,<tooa/toda>,<length>]<CR>
<LF><data>[...]]
U10_SMS_Application_Note_V1.0
- 19 -
U10 SMS Application Notes
The execution command AT+CMGL returns messages with status value <stat> from preferred
message storage <mem1> to the TE.
Parameters:
Text value
<state>
PDU value
Description
"REC UNREAD"
0
Received unread messages (default)
"REC READ"
1
Received read messages
"STO UNSENT"
2
Stored unsent messages
"STO SENT"
3
Stored sent messages
"ALL"
4
All messages
0
0
Normal
1
1
Not change status of the specified SMS record
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
<mode>
Example:
AT+CSDH=0
OK
AT+CMGL="ALL"
+CMGL: 1,"STO
UNSENT","15021012496","",
test
AT+CSDH=1
OK
AT+CMGL="ALL"
+CMGL: 1,"STO
UNSENT","15021012496","",,129,4
test
+CMGL: 2,"STO
SENT","15021012496","",
test
+CMGL: 2,"STO
SENT","15021012496","",,129,4
test
+CMGL: 3,"REC
READ","+8615021012496","","2010/08/18
17:29:12+32"
test
+CMGL: 3,"REC
READ","+8615021012496","","2010/08/18
17:29:12+32",145,4
test
+CMGL: 4,"REC
READ","+8615021012496","","2010/08/18
17:37:23+32"
test
+CMGL: 4,"REC
READ","+8615021012496","","2010/08/18
17:37:23+32",145,4
test
OK
OK
Note:
 The difference of text mode and PDU mode: the parameter <state> value and response
format.
2.3. Status report
Status report can be used to get information whether a short message is received by the target
U10_SMS_Application_Note_V1.0
- 20 -
U10 SMS Application Notes
address after it is sent. If status report is needed, two parameters should be set in text mode:
1) AT+CNMI=2,1,0,1,0
2) AT+CSMP=49,167,0,241
// The forth parameter <ds> must be equals to 1
// The first parameter <fo> must be equals to 49
When the message is received, sender will get URC in text mode as below:
+CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>
Please refer to section 2.5 for the example.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
2.4. Delete short messages
2.4.1. Delete One or all Short Message (+CMGD)
Table 12: AT+CMGD Syntax
Command
Possible Response
AT+CMGD=?
+CMGD:(Range of SMS on
preferred storage <mem1>
can be deleted)
AT+CMGD=<index>[,<delflag>]
OK
+CMS ERROR:<err>
Example
+CMGD: (1-50)
TA deletes message(s) from preferred message storage <mem1> (+CPMS). If <delflag> is omitted
or equals to 0, it will delete message of location <index>. If <delflag> is present and not set to 0,
<index> is ignored and TA deletes all messages of one or more types. See table below.
Parameter <delflag>:
0 or omitted
Delete the message specified in <index>
1
Delete all read messages
2
Delete all read and sent messages
3
Delete all read, sent, and unsent messages
4
Delete all messages
Note:
 No difference for text mode and PDU mode.
2.4.2. Delete all short messages (+QMGDA)
Table 13: AT+QMGDA Syntax in text mode
Command
Possible Response
U10_SMS_Application_Note_V1.0
Example
- 21 -
U10 SMS Application Notes
AT+QMGDA=?
Text mode:
+QMGDA:("DEL READ","DEL
UNREAD","DEL SENT","DEL
UNSENT","DEL INBOX","DEL ALL")
+QMGDA: (listed of
supported <type>s)
+CMS ERROR: <err>
PDU mode:
+QMGDA:(1-6)
AT+QMGDA=<type>
OK
ERROR
+CMS ERROR:<err>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
TA deletes all messages with type value <type> from preferred message storage <mem1>
(+CPMS).
<type> parameters:
Text mode
PDU mode
Description
"DEL READ"
1
Delete all read messages
"DEL UNREAD"
2
Delete all unread messages
"DEL SENT"
3
Delete all sent SMS
"DEL UNSENT"
4
Delete all unsent SMS
"DEL INBOX"
5
Delete all received SMS
"DEL ALL"
6
Delete all SMS
Note:
 The difference of text mode and PDU mode is the parameter <type> value.
2.5. Examples in text mode
User can send the short message in TEXT mode as follows.
2.5.1. Send English short message(GSM coding) and not require status report
For example: send “Hello” to +18621176031
Sender: +8618621090849
Receiver: +8618621176031
Step 1: Check service center address
AT+CSCS=“GSM”
//Set the character
mode as GSM mode.
OK
AT+CSCA? //Check the address of short
message service center. For
china unicom in Shanghai, the
CSA is "+8613010314500". If
this address is wrong, the short
message can NOT be sent
Step 1: Check service center address (same
as step 1 of sender)
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613010314500",145
U10_SMS_Application_Note_V1.0
OK
- 22 -
U10 SMS Application Notes
successfully. And so this
address should be set to the
correct one by
AT+CSCA=<sca> and save it
by AT+CSAS.1
+CSCA: "+8613010314500",145
OK
Step 2: Set for sending English short
message in text mode
AT+CMGF=1
// Set the short message
mode as TEXT mode:
OK
AT+CSCS=“GSM” // (Optional because it
has been set in above
step 1). Set the
character mode as
GSM mode.
OK
AT+CSMP=17,167,0,0 // Set the related
parameters for sending short
message in text mode: FO, VP, PID
and DCS2. DCS and +CSCS should
match each other. To send
English message, set +CSCS as
“GSM” and <dcs> as GSM 7-bit
coding.
OK
AT+CNMI=2,1,0,0,0 // Not require status
report: <FO> of
+CSMP = 17 or <ds>
of +CNMI =0
OK
Step 2: Set for receiving English short
message in text mode
AT+CMGF=1
// Set the short message
mode as TEXT mode:
OK
AT+CSCS=“GSM” //Set the character mode
as GSM mode. If it
sets as “UCS2”, the
message content will be
displayed in UCS2
format.
OK
AT+CNMI=2,1,0,0,0 // Set parameters for
new message
indication. 1 – get
indication +CMTI
OK
AT+CPMS?
//Check if short message
storage is full. If it has
been full, delete some
messages by AT
command +CMGD or
+QMGDA.
+CPMS: "SM",0,50,"SM",0,50,"SM",0,50
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
OK
AT+CSDH=1
//More information will
be displayed if it equals 1.
OK
Step 3: Send English short message
AT+CMGS="18621176031" // Send SMS:
Enter the mobile phone number
directly. Enter message content
after “>” and end the input by
pressing Ctrl and “Z”
simultaneously.
>Hello<Ctrl+Z>
U10_SMS_Application_Note_V1.0
- 23 -
U10 SMS Application Notes
+CMGS: 140
OK
Step 3: Receive and read short message
+CMTI: "SM",1
AT+CMGR=1
+CMGR: "REC
UNREAD","+8618621090849","","2010/09/0
1
11:11:47+32",145,4,0,241,"+8613010314500"
,145,5
Hello
l
e
l
t
e
l
c
l
t
a
a
e
i
c
t
i
e
u
t
n
u
QQ iddeen
f
i
n
f
n
o
o
C
C
OK
AT+CSCS="UCS2"
//if set character set as
“UCS2”, the content
of message will be
displayed in UCS2
format.
OK
AT+CMGR=1
+CMGR: "REC
READ","002B0038003600310038003600320
031003000390030003800340039","","2010/0
9/01
11:11:47+32",145,4,0,241,"002B0038003600
3100330030003100300033003100340035003
00030",145,5
00480065006C006C006F
OK
Note 1:
The short message service center is provided by network provider, and saved in SIM card as
factory setting. It is highly recommended that you do not change it at any time. And it’s better to
check it before sending short message.
Note 2:
The meaning represented by them is the same as the PDU mode parameters. The difference is that
the parameter must be input in decimal mode. The parameter 0 means that the short message
content is default in GSM coding and sent to <mem3> to store. If changed into 240, means that
the short message content is in GSM coding and sent to the destination terminal directly.
U10_SMS_Application_Note_V1.0
- 24 -
U10 SMS Application Notes
2.5.2. Send Chinese short message(UCS2 coding) and require status report
For example: send “您好” (UCS2 coding “60A8597D”) to 18621176031
Sender: 18621090849
Receiver: 18621176031
Step 1: Check service center address
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613010314500",145
Step 1: Check service center address
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613010314500",145
OK
OK
l
e
l
t
e
l
c
l
t
a
a
e
i
c
t
i
e
u
t
n
u
QQ iddeen
f
i
n
f
n
o
o
C
C
Step 2: Set for sending Chinese short
message in text mode
AT+CMGF=1
// Set the short message
mode as TEXT mode:
OK
AT+CSCS=“UCS2” //Set the character mode
as UCS2 mode.
OK
AT+CSMP=49,167,0,25 // Set the related
parameters for sending short
message in text mode: FO, VP, PID
and DCS1.DCS and +CSCS should
match each other. To send Chinese
message, set +CSCS as “UCS2”
and <dcs> as UCS2 coding.
OK
AT+CNMI=2,1,0,1,0 // Require status report:
<FO> of +CSMP = 49, <ds> of
+CNMI = 1
OK
Step 2: Set for receiving Chinese short
message in text mode
AT+CMGF=1
// Set the short message
mode as TEXT mode:
OK
AT+CNMI=2,2,0,0,0 // Set parameters for
new message
indication. When the
second parameter is
set as 2 , get
indication +CMT
with message content
OK
AT+CPMS? // Check if short message
storage is full. If it has been
full, delete some messages by
AT command +CMGD or
+QMGDA.
+CPMS: "SM",1,50,"SM",1,50,"SM",1,50
OK
AT+CSDH=0 // Less information will be
displayed when it equals 0.
OK
Step 3: Send Chinese short message
AT+CMGS="0031003800360032003100310
0370036003000330031"
//
Send SMS: Enter the mobile phone
number in UCS2 coding as set in
+CSCS. Enter message content in
UCS2 format after “>” and end the
input by pressing Ctrl and “Z”
simultaneously.
> 60A8597D <Ctrl+Z>
U10_SMS_Application_Note_V1.0
- 25 -
U10 SMS Application Notes
+CMGS: 141
OK
Step 3: Receive and read short message
+CMT: "+8618621090849",,"2010/09/01
11:14:52+32"
60A8597D
AT+CPMS?
//The short message is not
saved
+CPMS: "SM",1,50,"SM",1,50,"SM",1,50
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
OK
Step4: Get status report
+CDS:
6,141,"+8618621176031",145,"2010/09/01
11:25:55+32","2010/09/01 11:25:55+32",0
Note:
The meaning represented by them is the same as the PDU mode parameters. And the difference is
that the parameters must be input in decimal mode. The parameter 25 means that the content of
the short message is UCS2 coding and sends to <mem3> to store. If changed into 24, means that
the short message content is UCS2 coding and sends to destination terminal directly.
U10_SMS_Application_Note_V1.0
- 26 -
U10 SMS Application Notes
3. SMS in PDU mode
3.1. Write and Send Short Message
3.1.1. Send Message direct from Terminal (+CMGS)
Table 14: AT+CMGS Syntax in PDU mode
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Command
Possible Response
AT+CMGS=?
OK
AT+CMGS=<length>
<CR>
PDU
is
given
<ctrl-Z/ESC>
+CMGS: <mr>
or +CMS ERROR:
<err>
Example
Send English characters “TEST” to
13795403834:
AT+CMGS=19
>
0011000D91683197453038F400F10104D4E29
40A<Ctrl+Z>
Send Chinese characters “测试” to
13795403834:
AT+CMGS=19
>0011000D91683197453038F4000801046D4B
8BD5 <Ctrl+Z>
Note:
 <pdu> includes all parameters for sending a message, such as the target address, type of
address, message content and settings of <+CSMP> in text mode. The structure of <pdu> is
represented in section 3.5.1SMS-Submit PDU Packet (MO)
 <length> must match the actual length of <pdu>.
 <length> equals to the number of octets of <pdu> excluding <SCA>. See section 3.5.1
Submit PDU packet.
3.1.2. Write short message to storage (+CMGW)
Table 15: AT+CMGW Syntax in PDU mode
Command
Possible Response
AT+CMGW=?
OK
AT+CMGW=<length>[,<stat>]<CR>
PDU is given <ctrl-Z/ESC>
+CMGW: <index>
+CMS ERROR: <err>
The parameter and <pdu> content are the same as above command <+CMGS>, but the message
will be saved to storage <mem2> (+CPMS) and not be sent.
The stored message can be sent by AT command +CMSS. There is no difference between PDU
U10_SMS_Application_Note_V1.0
- 27 -
U10 SMS Application Notes
mode and text mode.
3.2. Receive and read short message
For PDU mode, the command syntax of +CNMI and +CMGR are the same as text mode. The
difference is response format of URC +CMTI, +CMT, +CDS, +CMGR.
The AT command +CSDH is invalid for pdu mode because these text mode parameters will be
included in <pdu>. Refer to section 3.5.2 SMS-Deliver PDU Packet (MT) for <pdu> structure and
meaning.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
3.2.1. Read Short Messages (+CMGR)
Table 16: AT+CMGR Syntax in PDU mode
Command
Possible Response
Example
AT+CMGR=<index>[,
<mode>]
+CMGR:
<stat>,[<alpha>],<length
><CR><LF><pdu>
AT+CMGR=5
+CMGR: 0,,24
0891683108200105F0040D916851200
12194F600F10180817144302304F4F2
9C0E
OK
See next AT command +CMGL for <stat> and <mode> value and meaning in PDU mode.
3.2.2. List short messages from preferred storage (+CMGL)
Table 17: AT+CMGL Syntax in PDU mode
Command
Possible Response
AT+CMGL=?
OK
Or +CMS ERROR: <err>
AT+CMGL=<sta
t>[,<mode>]
+CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu><CR><LF>
+CMGL: <index>,<stat>,[alpha],<length><CR><LF><pdu>[...]]
The execution command +CMGL returns messages with status value <stat> from preferred
message storage <mem1> to the TE.
Parameters:
Text value
<state>
PDU value
Description
"REC UNREAD"
0
Received unread messages (default)
"REC READ"
1
Received read messages
U10_SMS_Application_Note_V1.0
- 28 -
U10 SMS Application Notes
"STO UNSENT"
2
Stored unsent messages
"STO SENT"
3
Stored sent messages
"ALL"
4
All messages
0
0
Normal
1
1
Not change status of the specified SMS record
<mode>
Example:
AT+CMGL=4
+CMGL: 1,2,,18
0011FF0B815120012194F600004704F4F29C0E
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
+CMGL: 2,3,,18
00117E0B815120012194F600004704F4F29C0E
+CMGL: 3,1,,24
0891683108200105F0040D91685120012194F600F10180817192212304F4F29C0E
+CMGL: 4,1,,24
0891683108200105F0040D91685120012194F600F10180817173322304F4F29C0E
OK
3.3. Status report
If status report is needed, two parameters should be set:
//The forth parameter <ds> must be equals to 1
1) AT+CNMI=2,1,0,1,0
2) <SRR> in <FO> field of PDU package must be set as 1.
When the message is received, sender will get URC in PDU mode as below:
+CDS:<length><CR><LF><pdu>
Please refer to section 3.6 for the example.
3.4. Delete short messages
Same as text mode, user can delete one or more short messages by AT command +CMGD, or
delete all short messages with <type> by AT command +QMGDA. The difference is <type> value
in command +QMGDA, see above section 2.4.
3.5. Basic elements of the PDU
Please refer to the document [4] 3GPP TS 23.040 (GSM 03.40) subclause 9 for details except
element <DCS><UDL><UD> which are defined in [3] 3GPP TS 23.038 (GSM 03.38).
U10_SMS_Application_Note_V1.0
- 29 -
U10 SMS Application Notes
&b/&h/&d is appended to the digital number to stand for binary/hexadecimal/decimal format in
this document.
3.5.1. SMS-Submit PDU packet (MO)
Table 18: SMS-SUBMIT packet
number of octets
1-12
1
1
2-12
1
1
0,1 or 7
1
0-140
Element
SCA
FO
MR
DA
PID
DCS
VP
UDL
UD
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
3.5.2. SMS-Deliver PDU packet (MT)
Table 19: SMS-DELIVER Packet
number of octets
1-12
1
2-12
1
1
7
1
0-140
Element
SCA
FO
OA
PID
DCS
SCTS
UDL
UD
3.5.3. SMS-Status Report Packet
Table 20: Status-Report packet
number
of octets
1-12
1
1
2-12
7
7
1
1
1
1
1
0140
Element
SCA
FO
MR
RA
SC
TS
DT
ST
PI
PID
DC
S
UD
L
UD
The last elements from PI to UD are optional.
3.5.4. Element descriptions
3.5.4.1. Type of Address <TOA>
Table 21: <TOA>
&b
&h
&d
0001
81
129
Unknown
001
0001
91
145
International number, beginning with “+”continued
with the country code.
010
0001
A1
161
National number
1
TON
NPI
1
000
1
1
Description
Please refer to the document [7] 3GPP TS 24.008 (GSM 04.08) subclause 10.5.4.7 Called party
BCD number for details of TON (Type of Number) and NPI (Numbering plan identification).
U10_SMS_Application_Note_V1.0
- 30 -
U10 SMS Application Notes
3.5.4.2. Service Center Address <SCA>
Table 22: <SCA>
Element
SCA length
TOA
SCA
Example(&h)
08
91
683108200105F0
Above example shows <sca> address “+8613010314500” (SCA of China Unicom in Shanghai).
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Parameters:
SCA length = 8 = 1 (octets length of TOA) + 7 (octets length of SCA)
TOA = 91: The address is international number (Begin with “+”).
SCA = 683108200105F0: Service Center Address. Number formatting rule:
1) One octet includes two BCD-digit Fields.
2) If the digits number is odd, the last digit shall be filled with“F&h”.
3) Switch every two digits from beginning.
Original number
86 13 01 03 14 50 0(F)
after formatting
68 31 10 30 41 05 F0
Note:
 When sending message (SMS-Submit), if <SCA> sets as “00”, the address of AT command
<+CSCA> will be used. It is highly recommended that you do NOT change it at any time.
And it’s better to check it before sending short message.
3.5.4.3. Originator/Destination/Recipient Address <OA>/<DA>/<RA>
Table 23: <OA>/<DA>/<RA>
Element
Address length
TOA
OA/DA/RA
Example(&h)
0D
91
683197453038F4
Parameters:
Address length = 0D&h = 13&d = number of digits of <OA>/<DA>/<RA> (8613795403834)
<OA>/<DA>/<RA>: the address format is the same as above field <SCA>
Note:
 If TOA does not match with address, short message sending maybe fail.
 Recommended to store every address in International numbering format to avoid problems
while roaming.
3.5.4.4. First Octet <FO>
First Octet includes some properties of the message, for example, the message type (MTI) , which
is a SMS Submit, SMS Deliver or SMS Status report; request status report or not (SRR) when
send a message; present VP (Validity Period) or not and its format(VPF), etc.
U10_SMS_Application_Note_V1.0
- 31 -
U10 SMS Application Notes
Table 24: <FO> elements
Bit
7
6
5
4
3
SMS-Submit
RP
UDHI
SRR
VPF
SMS-Deliver
RP
UDHI
SRI
SMS-Status
Report
RP
UDHI
SRQ
2
1
0
RD
MTI
-
MMS
MTI
-
MMS
MTI
<FO> parameters
Value
(bit)
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Parameter
Meaning
0
Reply Path is not set
1
Reply Path is set
User Data
Header
Indicator
0
The UD (User Data) field contains only the short
message
1
The beginning of the UD field contains a Header in
addition to the short message
SRI
Status Report
Indication
0
A status report will not be returned to the SME
1
A status report will be returned to the SME
SRR
Status Report
Request
0
A status report is not requested
1
A status report is requested
0
The SMS-Status-Report is the result of a SMS-Submit
SRQ
Status Report
Qualifier
1
The SMS-Status-Report is the result of a
SMS-Command, e.g. an Enquiry
00
VP field is not present
01
Enhanced VP format
10
Relative VP format, VP comprises 1 octet, an integer
represented
11
Absolute VP format, VP comprises 7 octets
0
More messages are waiting for the MS in this SC
1
No more messages are waiting for the MS in this SC
0
Instruct the SC to accept a SMS-SUBMIT for an SM
still held in the SC which has the same TP-MR and the
same TP-DA as a previously submitted SM from the
same OA.
1
Instruct the SC to reject an SMS-SUBMIT for an SM
still held in the SC which has the same MR and the same
DA as the previously submitted SM from the same OA.
In this case, an appropriate FCS value will be returned in
the SMS-SUBMIT-REPORT.
00
SMS-Deliver (in the direction SC to MS)
01
SMS-Submit (in the direction MS to SC)
10
SMS-Status Report (in the direction SC to MS)
10
SMS-Command (in the direction MS to SC)
RP
UDHI
VPF
MMS
RD
MTI
Reply Path
Validity Period
Format
More Messages
to Send
Reject
Duplicates
Message Type
Indicator
U10_SMS_Application_Note_V1.0
- 32 -
U10 SMS Application Notes
Example of <FO> for SMS-Submit:
When sending short message in text mode, we should set <fo> as 17 or 49 in AT command
+CSMP. The following table shows their meanings:
&b
00010001
&h
&d
11
Bit 7
6
5
RP
UDHI
SRR
0
0
17
4
3
2
1
0
VPF
RD
MTI
0
10
0
01
No header
in UD
not request
status report
VP relative
format
0
1
10
No header
in UD
request
status report
VP relative
format
SMS-Submit
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
0
00110001
31
49
0
01
SMS-Submit
3.5.4.5. Message Reference <MR>
MR is an integer (0..255) for representing a reference number of the SMS-submit submitted to the
SMSC by the MS, used to identify whether the received SMS is duplicated or not.
3.5.4.6. Protocol Identifier <PID>
The PID is the information element by which the transport layer either refers to the higher layer
protocol being used, or indicates interworking with a certain type of telematic device.
Table 25: <PID>
<PID> value
Protocol
&h
&d
00
0
The SMS has to be treat as a short message
01
1
The SMS has to be treat as a telex
3.5.4.7. Data Coding Scheme <DCS>
<DCS> identifies the coding scheme within the User Data (UD). It comprises one octet and may
indicate the message class, alphabet, etc. Please refer to [3] 3GPP TS 23.038 (GSM 03.38) for
details.
Table 26:<DCS>
bit7-4
00xx
( general data
coding
indication)
5
4
3
2
1
0
Meanings
0
The text is uncompressed
1
The text is compressed using the GSM standard
compression algorithm
0
Bit 1,0 are reserved and have no message class
1
Bit 1,0 have a message class meaning
0
U10_SMS_Application_Note_V1.0
0
Default alphabet
- 33 -
U10 SMS Application Notes
0
1
8 bit alphabet
1
0
UCS2 (16 bit)
1
1
Reserved
0
0
Class 0 immediate display
0
1
Class 1 default meaning: ME specific
1
0
Class 2 SIM specific message
1
1
Class 3 default meaning: TE specific
0
Reserved
0
Default alphabet
1
8-bit data
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
1111
(data coding
message class)
0
0
Class 0 immediate display
0
1
Class 1 default meaning: ME specific
1
0
Class 2 SIM specific message
1
1
Class 3 default meaning: TE specific
Message Class indicates how to store message when it is received. Class 0 message is displayed
directly in the destination terminal, not stored. If you want to store it in SIM, you can use AT
command +QCLASS0.
Default alphabet indicates the user data is coded from the 7-bit alphabet.
Example
&b
&h
&d
Character Coding
Message Class
00000000
00
0
7-bit
No class
00001000
08
8
UCS2
No class
00011000
18
24
UCS2
Class 0 (immediate display)
00011001
19
25
UCS2
Class 1 (ME-specific)
11110000
F0
240
7-bit
Class 0 (immediate display)
11110001
F1
241
7-bit
Class 1 (ME-specific)
In text mode, module uses relative decimal format in +CSMP.
3.5.4.8. Validity Period <VP>
<VP> identifies the time period for which the short message is valid in the SMSC. Its format is
defined in <VPF> of <FO> field.
When <VPF> is relative format (<VPF>=10&b), <VP> comprises 1 octet, which illustrates the
period between the time when SC receives the SM and SC discards the SM.
U10_SMS_Application_Note_V1.0
- 34 -
U10 SMS Application Notes
Table 27: <VP> relative format
<VP> value
Validity period value
&h
&d
00 to 8F
0 to 143
(VP+1)*5 minutes
5 minutes to 12 hours
90 to A7
144 to 167
12 hours + (VP-143)*30 minutes
12.5 hours to 24 hours
A8 to C4
168 to 196
(VP-166)*1 day
2 days to 30 days
C5 to FF
197 to 255
(VP-192)*1 week
5 weeks to 63 weeks
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
In text mode, module uses relative decimal format in +CSMP.
When <VPF> is absolute format (<VPF>=11&b), <VP> comprises 7 octets, it defines the absolute
expire time when SC discards the SM. The representation is identical to the representation of the
TP-SCTS (Service Center Time Stamp).
3.5.4.9. Service Centre Time Stamp <SCTS>
<SCTS> indicates time when the SMSC received the message. It’s given in semi-octet
representation in the following way.
Table 28: <SCTS>
Year
Month
Digits(Semi-octets)
2
2
Example
01
80
Day
Hour
Minute
Second
Time Zone
2
2
2
2
2
12
41
14
80
23
The Time Zone expressed in quarters of an hour, between the local time and GMT. The above
example shows time 10-08-21 14:41:08+32, GMT +08.
3.5.4.10. Discharge Time <DT>
The TP-Discharge-Time field indicates the time at which the previously submitted SMS-SUBMIT
was successfully delivered to or attempted to deliver to the recipient SME or disposed of by the
SC.
3.5.4.11. Length of User Data <UDL>
UDL indicates the length of UD. It is related with the alphabet defined in <DCS>.
bits per
character
SMS UDL
meaning
character table
Default(GSM 7-bit)
7
Number of
characters
see [3]3GPP TS 23.038 (GSM 03.38)
8-bit data
8
Number of octets
user specific
Number of octets
ISO/IEC10646 “Universal
Multiple-Octet Coded Character Set
(UCS)”
<dcs>
UCS2
16
U10_SMS_Application_Note_V1.0
- 35 -
U10 SMS Application Notes
Note:
For GSM 7-bit coding, UDL equals to the number of characters, it does NOT equal to the number
of octets.
3.5.4.12. User Data <UD>
If <UDHI> equals 0 (no header in <UD>) and message is not compressed, the maximum
individual Short Message sizes of 160 7-bit characters, 140 8-bit characters, or 70 16-bit
characters (1120 bits = 160*7 = 140*8 = 70*16).
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
General characters in English can be found in GSM alphabet table ([3]3GPP TS 23.038 (GSM
03.38) subclause 6.2.1. Default alphabet or appendix 5.3 in this document), and so can be encoded
using GSM 7-bit encoding. Characters in languages such as Arabic, Chinese, Korean, Japanese or
Cyrillic alphabet languages (e.g. Russian, Serbian, Bulgarian, etc) must be encoded using the
16-bit UTF-16 character encoding.
Please refer to the document [3] 3GPP TS 23.038 (GSM 03.38) subclause 6.1.2.1.1 for SMS
point-to-point packing of 7-bit characters.
Example: SMS point-to-point packing of 7-bit characters
User data: 12345678
Character
1
2
3
4
5
6
7
8
GSM coding(hex)
31
32
33
34
35
36
37
38
GSM coding(bit)
0110
001
0110
010
0110
011
0110
100
0110
101
0110
110
0110
111
0111
000
Transfer last bits to
previous character
0011
0001
1101
1001
1000
1100
0101
0110
1011
0011
1101
1101
0111
0000
Result in hex format
31
D9
8C
56
B3
DD
70
So for string “12345678”, UD = “31D98C56B3DD70” and UDL=8 (note it is the number of
characters, not number of octets).
3.5.4.13. Status <ST>
ST indicates the status of the previously submitted SMS-SUBMIT when a status report has been
requested. It consists of one octet. If it equals to “00”&h, which means short message has been
received.
3.6. Examples in PDU mode
User can send the English and Chinese short message in PDU mode as follows.
U10_SMS_Application_Note_V1.0
- 36 -
U10 SMS Application Notes
3.6.1. Send English short message(GSM coding) and not require status report
For example: send “Hello” to +8613795403834
Sender: +8613651979176
Receiver: +8613795403834
Step 1: Check service center address
AT+CSCS=“GSM”
//Set the character
mode as GSM mode.
OK
AT+CSCA?
//Check the address
of short message service center. For
china mobile in Shanghai, the CSA is
"+8613800210500". If this address is
wrong, the short message can NOT
be sent successfully. And so this
address should be set to the correct
one by AT+CSCA=<sca> and save it
by AT+CSAS.
+CSCA: "+8613800210500",145
Step 1: Check service center address
(same as step 1 of sender)
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
OK
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Step 2: Set PDU mode
AT+CMGF=0
// Set the short message
mode as PDU mode.
OK
OK
Step 2: Set PDU mode and parameters for
receiving messages
AT+CMGF=0
// Set the short message
mode as PDU mode.
OK
AT+CNMI=2,1,0,0,0 // Set parameters
for new message indication. When
the second parameter is set as 1,
get indication +CMTI.
OK
AT+CPMS?
//Check if short message
storage is full. If it has been full,
delete some messages by AT
command +CMGD or +QMGDA.
+CPMS: "SM",1,50,"SM",1,50,"SM",1,50
OK
Step 3: Send English short message
AT+CMGS=20
>
0011000D91683197453038F400000105C8329
BFD06 <Ctrl+Z>
+CMGS: 146
OK
//See below Note 1 for descriptions
U10_SMS_Application_Note_V1.0
- 37 -
U10 SMS Application Notes
Step 3: Receive and read short message
+CMTI: "SM",2
AT+CMGR=2
+CMGR: 0,,25
0891683108200105F0040D9168315691977
1F600000190102191252305C8329BFD06
OK
//See below Note 2 for descriptions
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Note 1: Descriptions for SMS-SUBMIT PDU:
AT+CMGS=20
> 0011000D91683197453038F400000105C8329BFD06 <Ctrl+Z>
SMS-SUBMIT PDU:
Number of
octets
1-12
1
1
2-12
1
1
0,1 or
7
1
0-140
Element
SCA
FO
MR
DA
PID
DCS
VP
UDL
UD
Example
00
11
00
0D91683197
453038F4
00
00
01
05
C8329
BFD06
20 = octets of (<pdu>-<sca> = 11000D91683197453038F400000105C8329BFD06)
SCA = 00: Service center address is defined in AT command +CSCA.
FO = 11&h = 17&d:
&b
00010001
&h
11
&d
Bit 7
6
5
RP
UDHI
SRR
VPF
RD
MTI
0
0
0
10
0
01
No header
in UD
not request
status report
VP relative
format
17
4
3
2
1
0
SMS-Sub
mit
SRR = 0: A status report is not requested
VPF = 10, VP = 01: validity period is (VP+1)*5 = 10 minutes
DA = 0D91683197453038F4: Receiver is +8613795403834
DCS = 00: GSM 7-bit coding.
UDL = 05: length of characters “Hello”
UD = C8329BFD06:
Character
H
e
l
l
o
GSM coding(hex)
48
65
6C
6C
6F
GSM coding(bit)
1001000
1100101
1101100
1101100
1101111
Transfer last bits to previous
character
11001000
00110010
10011011
11111101
00000110
C8
32
9B
FD
06
Result in hex format
Note 2: Descriptions for SMS-Deliver PDU
AT+CMGR=2
+CMGR: 0,,25
U10_SMS_Application_Note_V1.0
- 38 -
U10 SMS Application Notes
0891683108200105F0040D91683156919771F600000190102191252305C8329BFD06
OK
SMS-DELIVER PDU:
number of
octets
1-12
1
2-12
1
1
7
1
0-140
Element
SCA
FO
OA
PID
DCS
SCTS
UDL
UD
Example
0891683108
200105F0
04
0D9168315
6919771F6
00
0190102
1912523
05
C832
9BFD
06
00
l
e
l
t
e
l
c
l
t
a
a
e
i
c
t
i
e
u
t
n
u
QQ iddeen
f
i
n
f
n
o
o
C
C
SCA = 0891683108200105F0: Service center address is +8613800210500
OA = 0D91683156919771F6: Sender is +8613651979176
FO = 04:
Bit
7
6
5
SMS-Deliver
RP
UDHI
SRI
Example
0
0
0
4
3
-
00
2
1
MMS
01
0
MTI
00
UDHI = 0: No header in UD
MMS = 1: No more messages are waiting for the MS in this SC
3.6.2. Send Chinese short message(UCS2 coding) and require status report
For example: send “您好” (UCS2 coding “60A8597D”) to 13795403834
Sender: +8613651979176
Receiver: +8613795403834
Step 1: Check service center address
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
Step 1: Check service center address
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
OK
OK
Step 2: Set PDU mode
AT+CMGF=0
// Set the short message
mode as PDU mode.
OK
AT+CNMI=2,1,0,1,0
// Require status
report: <SRR> in <FO> field of pdu
package must be set as 1 and <ds>
of +CNMI = 1
OK
U10_SMS_Application_Note_V1.0
Step 2: Set PDU mode and parameters for
receiving messages
AT+CMGF=0
// Set the short message
mode as PDU mode.
OK
AT+CNMI=2,2,0,0,0 // Set parameters for
new message indication. 2 – get
indication +CMT with message
content
OK
AT+CPMS?
//Check if short message
- 39 -
U10 SMS Application Notes
storage is full. If it has been full,
delete some messages by AT
command +CMGD or +QMGDA.
+CPMS: "SM",2,50,"SM",2,50,"SM",2,50
OK
Step 3: Send Chinese short message
AT+CMGS=19
>
0031000D91683197453038F40008010460A8
597D <Ctrl+Z>
+CMGS: 147
OK
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
//See below Note 1 for descriptions
Step 3: Receive and read short message
+CMT: ,24
0891683108200105F0240D91683156919771
F60008019010314241230460A8597D
//See below Note 2 for descriptions
AT+CPMS?
//The short message is not
saved
+CPMS: "SM",2,50,"SM",2,50,"SM",2,50
OK
Step4: Get status report
+CDS: 26
0891683108200105F006930D916831974530
38F4019010314291230190103142912300
//See below Note 3 for descriptions
Note 1: Descriptions for SMS-SUBMIT PDU:
AT+CMGS=19
> 0031000D91683197453038F40008010460A8597D <Ctrl+Z>
SMS-SUBMIT PDU:
number of
octets
1-12
1
1
2-12
1
1
0,1 or
7
1
0-140
Element
SCA
FO
M
R
DA
PID
DCS
VP
UDL
UD
Example
00
31
00
0D916831974
53038F4
00
08
01
04
60A8597
D
19 = octets number of (<pdu>-<sca> = 31000D91683197453038F40008010460A8597D)
SCA = 00: Service center address is defined in AT command +CSCA.
FO = 31&h = 49&d:
U10_SMS_Application_Note_V1.0
- 40 -
U10 SMS Application Notes
&b
&h
&d
Bit 7
6
5
RP
UDHI
SRR
0
00110001
31
49
4
3
2
1
0
VPF
RD
MTI
0
01
0
1
10
No
header
in UD
request
status
report
VP relative
format
SMS-Submit
SRR = 1: A status report is requested
VPF = 10, VP = 01: validity period is (VP+1)*5 = 10 minutes
DA = 0D91683197453038F4: Receiver is +8613795403834
DCS = 08: UCS2 coding.
UDL = 04: Number of UD octets “60A8597D”
UD = 60A8597D: UCS2 coding for “您好”
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Note 2: Descriptions for SMS-Deliver PDU
+CMT: ,24
0891683108200105F0240D91683156919771F60008019010314241230460A8597D
SMS-DELIVER PDU:
number of
octets
1-12
1
2-12
1
1
7
1
0-140
Element
SCA
FO
OA
PID
DC
S
SCTS
UD
L
UD
Example
08916831082
00105F0
24
0D9168315
6919771F6
00
08
0190103
1424123
04
60A859
7D
24 = Octets number of <pdu> - <SCA>
(240D91683156919771F60008019010314241230460A8597D)
SCA = 0891683108200105F0: Service center address is +8613800210500
OA = 0D91683156919771F6: Sender is +8613651979176
FO = 24:
Bit
7
6
5
SMS-Deliver
RP
UDHI
SRI
Example
0
0
1
4
3
-
00
2
MMS
01
1
0
MTI
00
UDHI = 0: No header in UD
SRI = 1: A status report will be returned to the SME
MMS = 1: No more messages are waiting for the MS in this SC
Note 3: Descriptions for SMS-Status Report PDU
+CDS: 26
0891683108200105F006930D91683197453038F4019010314291230190103142912300
U10_SMS_Application_Note_V1.0
- 41 -
U10 SMS Application Notes
SMS-Status Report PDU:
number of
octets
1-12
1
1
2-12
7
7
1
Element
SCA
FO
MR
RA
SCTS
DT
ST
Example
0891683108
200105F0
06
93
0D9168319745
3038F4
01901031
429123
01901031
429123
00
26= octets number of <pdu> - <SCA>
(06930D91683197453038F4019010314291230190103142912300)
SCA = 0891683108200105F0: Service center address is +8613800210500
MR = 93 &h = 147: same as response <MR> of AT command +CMGS
RA = 0D91683197453038F4: Receiver is +8613795403834
ST = 0: short message has been received.
FO = 06:
Bit
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
7
6
5
SMS-Status
report
RP
UDHI
SRQ
Example
0
0
0
4
3
-
00
2
MMS
01
1
0
MTI
10
UDHI = 0: No header in UD
SRQ = 0: The SMS-Status-Report is the result of a SMS-Submit
MMS = 1: No more messages are waiting for the MS in this SC
U10_SMS_Application_Note_V1.0
- 42 -
U10 SMS Application Notes
4. Other Commands with SMS
4.1. Save and restore SMS settings
The settings of +CSCA and +CSMP can be saved to SIM card by AT command +CSAS and
restored by AT command +CRES. Other commands are described in section 4.1.3.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
4.1.1. Save SMS settings (+CSAS)
Table 29: AT+CSAS syntax
Command
Possible Response
AT+CSAS=?
+CSAS: (list of supported <profile>s)
AT+CSAS=[<profile>]
OK
ERROR
Example
+CSAS: (0-3)
Parameter:
<profile>
0-3
Manufacturer specific profile number where settings are to be saved
Execution command saves active message service settings to a non-volatile memory. A TA can
contain several profiles of settings. Settings specified in AT commands Service Centre Address
+CSCA and Set Message Parameters +CSMP are saved.
4.1.2. Restore SMS Settings (+CRES)
Table 30: AT+CRES syntax
Command
Possible Response
AT+CRES=?
+CRES: (list of supported <profile>s)
AT+CRES=[<profile>]
OK
ERROR
Example
+CRES: (0-3)
TA restores SMS settings from non-volatile memory to active memory.
4.1.3. Save other settings
The setting of +CPMS is saved automatically.
The setting of +QCLASS0 is not able to be saved.
The following settings can be saved by command AT&W, restored by command ATZ, and return
to manufacturer defaults by command AT&F.
 +CMGF
U10_SMS_Application_Note_V1.0
- 43 -
U10 SMS Application Notes



+CNMI
+CSDH
+CSCS
4.2. Store Class 0 SMS to <mem3> when received Class 0 SMS (+QCLASS0)
As normal class0 message (set in <dcs>) will be displayed immediately in the terminal. Using AT
command +QCLASS0, Quectel module can store this kind of message.
l
e
l
t
e
l
c
l
t
a
a
e
i
c
t
i
e
u
t
n
u
QQ iddeen
f
i
n
f
n
o
o
C
C
Table 31: AT+QCLASS0 syntax
Command
Possible Response
AT+QCLASS0=?
+QCLASS0: (0, 1)
AT+QCLASS0?
+QCLASS0: <mode>
AT+QCLASS0=[<mode>]
OK
ERROR
Parameter <mode>
0
Disable to store Class 0 SMS to <mem3> when received Class 0 SMS (default)
1
Enable to store Class 0 SMS to <mem3> when received Class 0 SMS
Example:
//Send class 0 message
AT+CMGF=1
// Set the short message mode as TEXT mode
OK
AT+CSCS=“GSM”
// Set the character mode as GSM mode.
OK
AT+CSMP=17,167,0,240
// Set parameters for sending short message in text mode.
<DCS>=240 stands for a class0 message
OK
AT+CMGS=”13795403834”
>TEST CLASS0 MESSAGE<Ctrl+Z>
+CMGS: 160
OK
//Receive Class0 message when QCLASS0=0
AT+QCLASS0?
+QCLASS0: 0
OK
AT+CMGF=1
OK
AT+CNMI?
+CNMI: 2,1,0,0,0
U10_SMS_Application_Note_V1.0
- 44 -
U10 SMS Application Notes
OK
+CMT: "+8613651979176",,"2010/09/01 15:35:34+32"
TEST CLASS0 MESSAGE
//Message is displayed directly and not stored
//Receive Class0 message when QCLASS0=1 (Send the same message as above)
AT+QCLASS0=1
OK
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
+CMTI: "SM",3
//Message is stored.
AT+CMGR=3
+CMGR: "REC UNREAD","+8613651979176","","2010/09/01 15:37:56+32"
TEST CLASS0 MESSAGE
OK
4.3. Notify SMS is full (+QEXTUNSOL)
+QEXTUNSOL is provided to enable/disable proprietary unsolicited indications. User can use this
command to get the notification for SMS full as the following format.
AT+QEXTUNSOL=”SM” ,<mode>
<SM> stands for additional SMS Information and displays additional information about SMS
events in the form of Unsolicited messages of the following format.
+TSMSINFO: <CMS error info>
where <CMS error info> is a standard CMS error in the format defined by the AT+CMEE
command i.e. either a number or a string.
<mode> parameter
0
Disable (default)
1
Enable
2
Query
Example:
AT+QEXTUNSOL=”SM”,1
OK
AT+CPMS?
+CPMS: "SM",49,50,"SM",49,50,"SM",49,50
OK
+CMTI: "SM",50
//Short messages are full, get below URC:
U10_SMS_Application_Note_V1.0
- 45 -
U10 SMS Application Notes
+TSMSINFO: 322
//Restart module
+TSMSINFO: 322
+TSMSINFO: 3513
// Memory full
// Memory full
// Unread records on SIM
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
U10_SMS_Application_Note_V1.0
- 46 -
U10 SMS Application Notes
5. Appendix
5.1. Message service send and write procedures
Refer to the document [2] 3GPP TS 27.005 (GSM 07.05) clause 3 Figure 4.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
SMS-SUBMIT
send from storage +CMSS
SM STORAGES
volatile memory
write +CMGW
SMS-SUBMIT
write +CMGW
SMS-SUBMIT
add text mode
parameters (+CSMP)
and SMSC address
(optionally add
SMSC address)
in text mode,
add SMSC address
(optional in PDU mode)
SMS-COMMAND
ME
text mode send +CMGS
and write +CMGW
PDU mode send +CMGS
and write +CMGW
send command +CMGC
TA
TE
Figure 2: Message service send and write procedures
U10_SMS_Application_Note_V1.0
- 47 -
U10 SMS Application Note
5.2. Message receiving procedures
Refer to the document [2] 3GPP TS 27.005 (GSM 07.05) Clause 3 Figure 3.
<ds>=2
new status report indication +CDSI
<mt>=1 or
<mt>=2 (class 2) or
<mt>=3 (class not 3)
SM STORAGES
new MT SM indication +CMTI
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
<mt>=0 or <mt>=1 or
<mt>=2 (class 2) or
<mt>=3 (class not 3)
SMS-DELIVER
<mt>=2 (class not 2) or
<mt>=3 (class 3)
BUFFER
<ds>=0 or
<ds>=2
SMS-STATUS-REPORT
new MT SM +CMT
<ds>=1
CBM with allowed message identifier
and data coding scheme (refer +CSCB)
status report +CDS
<bm>=2 or
<bm>=3 (class 3)
<bm>=0 or <bm>=1 or
<bm>=3 (class not 3)
new CBM +CBM
<bm>=1 or
<bm>=3 (class not 3)
new CBM indication +CBMI
CBM STORAGES
ME
TA
TE
Figure 3: Message receiving procedures
5.3. Default GSM alphabet
Refer to the document [3] 3GPP TS 23.038 (GSM 03.38) subclause 6.2.1 GSM 7 bit Default
Alphabet.
b4
b7
0
0
0
0
1
1
1
1
b6
0
0
1
1
0
0
1
1
b5
0
1
0
1
0
1
0
1
0
1
2
3
4
5
6
7
b3
b2
b1
0
0
0
0
0
1
0
1
@
£

_
SP
!
0
1
¡
A
P
Q
¿
a
p
q
0
0
1
0
2
$

"
2
B
R
b
r
0
0
1
1
3
¥

#
3
C
S
c
s
0
1
0
0
4
è

¤
4
D
T
d
t
0
1
0
1
5
é

%
5
E
U
e
u
0
1
1
0
6
ù

&
6
F
V
f
v
0
1
1
1
7
ì

'
7
G
W
g
w
1
0
0
0
8
ò

(
8
H
X
h
x
1
0
0
1
9
Ç

)
9
I
Y
i
y
0
0
U10_SMS_AN_V1.0
- 48 -
U10 SMS Application Notes
1
0
1
0
10
LF

*
:
J
Z
j
z
1
0
1
1
11
Ø
1)
+
;
K
Ä
k
ä
1
1
0
0
12
ø
Æ
,
<
L
Ö
l
ö
1
1
0
1
13
CR
æ
-
=
M
Ñ
m
ñ
1
1
1
0
14
Å
ß
.
>
N
Ü
n
ü
1
1
1
1
15
å
É
/
?
O
§
o
à
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Figure 4: Default GSM alphabet
U10_SMS_Application_Note_V1.0
- 49 -
U10 SMS Application Notes
Quectel Wireless Solutions Co., Ltd.
Room 501, Building13, No.99, Tianzhou Road, Shanghai, China 200233
Tel: +86 21 51086236
Mail: info@quectel.com
U10_SMS_Application_Note_V1.0
- 50 -
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising