GSM_SMS_App Note_V1.0
sales@eddywireless.com
Quectel Cellular Engine
SMS Application
Note
GSM_SMS_Application_Note_V1.0
GSM SMS Application Note
Document Title:
GSM SMS Application Note
Revision:
1.0
Date:
2010-11-15
Status:
Release
Document Control ID:
GSM_SMS_Application_Note_V1.0
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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. 2010
GSM_SMS_Application_Note_V1.0
-1-
GSM SMS Application Note
Contents
Contents .................................................................................................................................................... 2
Table Index ............................................................................................................................................... 4
0. Revision history .................................................................................................................................... 5
1. Introduction .......................................................................................................................................... 6
1.1. Reference ....................................................................................................................................... 6
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
1.2. Overview ....................................................................................................................................... 8
1.2.1.
Select SMS Message Format (+CMGF) .......................................................................... 8
1.2.2.
Select TE Character Set (+CSCS) ................................................................................... 9
1.2.3.
Set Service Center Address (+CSCA) ........................................................................... 10
1.2.4.
Set Preferred Message Storage (+CPMS)...................................................................... 11
2. SMS in text mode ............................................................................................................................... 12
2.1. Write and Send Short Message .................................................................................................... 12
2.1.1.
Set Text Mode Parameter (+CSMP) .............................................................................. 12
2.1.2.
Send Message directly from Terminal (+CMGS) .......................................................... 13
2.1.3.
Write Short Message to Storage (+CMGW) .................................................................. 13
2.1.4.
Send Short Message from Storage (+CMSS) ................................................................ 14
2.2. Receive and Read Short Message ................................................................................................ 14
2.2.1.
Show Text Mode Parameters (+CSDH)......................................................................... 15
2.2.2.
New Message Indication (+CNMI) ............................................................................... 15
2.2.3.
Read Short Message (+CMGR) ..................................................................................... 17
2.2.4.
List Short Messages from Preferred Storage (+CMGL) ................................................ 19
2.3. Status Report ............................................................................................................................... 20
2.4. Delete Short Messages ................................................................................................................ 20
2.4.1.
Delete One or all Short Message (+CMGD) ................................................................. 20
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 .......................... 24
3. SMS in PDU mode ............................................................................................................................. 26
3.1. Write and Send Short Message .................................................................................................... 26
3.1.1.
Send Message direct from Terminal (+CMGS) ............................................................. 26
3.1.2.
Write Short Message to Storage (+CMGW) .................................................................. 26
3.2. Receive and Read Short Message................................................................................................ 27
3.2.1.
Read Short Messages (+CMGR) ................................................................................... 27
3.2.2.
List Short Messages from Preferred Storage (+CMGL) ................................................ 27
3.3. Status Report ............................................................................................................................... 28
3.4. Delete Short Messages ................................................................................................................ 28
3.5. Basic elements of the PDU .......................................................................................................... 28
GSM_SMS_Application_Note_V1.0
-2-
GSM SMS Application Note
3.5.1.
SMS-Submit PDU Packet (MO).................................................................................... 29
3.5.2.
SMS-Deliver PDU Packet (MT).................................................................................... 29
3.5.3.
SMS-Status Report Packet............................................................................................. 29
3.5.4.
Element descriptions ..................................................................................................... 29
3.6. Examples in PDU mode .............................................................................................................. 35
3.6.1.
Send English short message(GSM coding) and not require status report ...................... 35
3.6.2.
Send Chinese short message(UCS2 coding) and require status report .......................... 38
4. Other Commands with SMS ............................................................................................................... 41
4.1. Save and Restore SMS Settings .................................................................................................. 41
4.1.1.
Save SMS Settings (+CSAS)......................................................................................... 41
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
4.1.2.
Restore SMS Settings (+CRES) .................................................................................... 41
4.1.3.
Save other settings ......................................................................................................... 41
4.2. Concatenated Short Message ....................................................................................................... 42
4.3. Store Class 0 SMS to <mem3> When Received Class 0 SMS (+QCLASS0) ............................. 43
4.4. Configure SMS code mode (+QSMSCODE) .............................................................................. 44
4.5. Notify for SMS 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
GSM_SMS_Application_Note_V1.0
-3-
GSM SMS Application Note
Table Index
TABLE 1: REFERENCE ................................................................................................................................ 6
TABLE 2: RELATED AT COMMANDS ........................................................................................................... 6
TABLE 3: ABBREVIATIONS ......................................................................................................................... 7
TABLE 4: AT+CMGF SYNTAX................................................................................................................... 9
TABLE 5: AT+CSCS SYNTAX .................................................................................................................... 9
TABLE 6: AT+CSCA SYNTAX .................................................................................................................. 10
TABLE 7: AT+CPMS SYNTAX ................................................................................................................. 11
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
TABLE 8: AT+CSMP SYNTAX IN TEXT MODE .......................................................................................... 12
TABLE 9: AT+CMGS SYNTAX IN TEXT MODE.......................................................................................... 13
TABLE 10: AT+CMGW SYNTAX IN TEXT MODE ...................................................................................... 13
TABLE 11: AT+CMSS SYNTAX IN TEXT MODE ........................................................................................ 14
TABLE 12: AT+CSDH SYNTAX IN TEXT MODE ........................................................................................ 15
TABLE 13: AT+CNMI SYNTAX ............................................................................................................... 15
TABLE 14: AT+CMGR SYNTAX IN TEXT MODE ....................................................................................... 17
TABLE 15: AT+CMGL SYNTAX IN TEXT MODE ....................................................................................... 19
TABLE 16: AT+CMGD SYNTAX .............................................................................................................. 20
TABLE 17: AT+QMGDA SYNTAX IN TEXT MODE .................................................................................... 21
TABLE 18: AT+CMGS SYNTAX IN PDU MODE........................................................................................ 26
TABLE 19: AT+CMGW SYNTAX IN PDU MODE ...................................................................................... 26
TABLE 20: AT+CMGR SYNTAX IN PDU MODE ....................................................................................... 27
TABLE 21: AT+CMGL SYNTAX IN PDU MODE........................................................................................ 27
TABLE 22: SMS-SUBMIT PACKET ......................................................................................................... 29
TABLE 23: SMS-DELIVER PACKET ....................................................................................................... 29
TABLE 24: STATUS-REPORT PACKET ........................................................................................................ 29
TABLE 25: <TOA> .................................................................................................................................. 29
TABLE 26: <SCA>................................................................................................................................... 29
TABLE 27: <OA>/<DA>/<RA> .............................................................................................................. 30
TABLE 28: <FO> ELEMENTS .................................................................................................................... 30
TABLE 29: <PID> .................................................................................................................................... 32
TABLE 30: <DCS>................................................................................................................................... 32
TABLE 31: <VP> RELATIVE FORMAT ........................................................................................................ 33
TABLE 32: <SCTS> ................................................................................................................................. 34
TABLE 33: AT+CSAS SYNTAX................................................................................................................. 41
TABLE 34: AT+CRES SYNTAX................................................................................................................. 41
TABLE 35: AT+QCLASS0 SYNTAX ......................................................................................................... 43
TABLE 36: AT+QSMSCODE SYNTAX ..................................................................................................... 44
GSM_SMS_Application_Note_V1.0
-4-
GSM SMS Application Note
0. Revision history
Revision
Date
Author
Description
draft
2009-6-25
Willis YANG
Initial
1.0
2010-11-15
Joanna Li
Add details
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
GSM_SMS_Application_Note_V1.0
-5-
GSM 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
Document name
Remark
[1]
Mxx_ATC
Mxx AT Commands Set
[2]
GSM 07.05
Equipment interface for SMS and CBS
[3]
GSM 03.38
Alphabets and language-specific information
[4]
GSM 03.40
Technical realization of the Short Message Service
[5]
GSM 07.07
AT command set for GSM Mobile Equipment (ME)
[6]
GSM 04.11
PP SMS support on mobile radio interface
Table 2: Related AT commands
AT command
Description
Reference
AT+CMGF
SELECT SMS MESSAGE FORMAT
GSM07.05
AT+CSCS
SELECT TE CHARACTER SET
GSM07.07
AT+CSCA
SMS SERVICE CENTER ADDRESS
GSM07.05
AT+CSMP
SET SMS TEXT MODE PARAMETERS
GSM07.05
AT+CNMI
NEW SMS MESSAGE INDICATIONS
GSM07.05
AT+CMGW
WRITE SMS MESSAGE TO MEMORY
GSM07.05
AT+CMSS
SEND SMS MESSAGE FROM STORAGE
GSM07.05
AT+CMGS
SEND SMS MESSAGE
GSM07.05
AT+CMGR
READ SMS MESSAGE
GSM07.05
AT+CMGL
LIST SMS MESSAGES FROM PREFERRED
STORE
GSM07.05
AT+CMGD
DELETE SMS MESSAGE
GSM07.05
AT+QMGDA
DELETE ALL SMS MESSAGES
Quectel defined
AT+CSDH
SHOW SMS TEXT MODE PARAMETERS
GSM07.05
AT+CSAS
SAVE SMS SETTINGS
GSM07.05
AT+CRES
RESTORE SMS SETTINGS
GSM07.05
AT+CPMS
PREFERRED SMS MESSAGE STORAGE
GSM07.05
AT+QCLASS0
STORE CLASS 0 SMS
RECEIVED CLASS 0 SMS
AT+QSMSCODE
CONFIGURE SMS CODE MODE
GSM_SMS_Application_Note_V1.0
TO
SIM
WHEN
Quectel defined
Quectel defined
-6-
GSM SMS Application Note
AT+QEXTUNSOL
ENABLE/DISABLE
UNSOLICITED INDICATIONS
PROPRIETARY Quectel defined
Table 3: 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
SCTS
DT
VP
VPF
UDL
UD
UDHI
RP
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] GSM 03.38
Service Center Time Stamp
Discharge Time
Validity Period
Validity Period Format
User Data Length
User Data
User Data Header Indicator
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
GSM_SMS_Application_Note_V1.0
-7-
GSM SMS Application Note
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 SM services comprise 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 computer, and set the same baud rate as the module’s
(Default is auto bauding for module).
3. Make sure the Quectel module and the SIM card are assembled on EVB, then power on the
module.
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 [1] Mxx_ATC document for the meaning of error code <err>.
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
GSM_SMS_Application_Note_V1.0
-8-
GSM SMS Application Note
sending and receiving by some AT commands. In PDU mode, you must write your messages in
fixed hexadecimal format, which parameters are included in the PDU package.
The mode sets by command AT+CMGF. See table below.
Table 4: AT+CMGF Syntax
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=<
mode>
OK
AT+CMGF=0
Set PDU mode. It's default.
AT+CMGF=1
Set Text mode
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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 5: 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"
AT+CSCS=<chset>
OK
AT+CSCS="GSM"
OK
(default)
Parameter <chset>
"GSM"
"HEX"
GSM default alphabet, 7-bit coded ([3] GSM 03.38 subclause 6.2.1, or Appendix
5.3 in this document).
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)
"8859-1"
ISO 8859 Latin 1 character set
Note:
 For English message, recommend 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
GSM_SMS_Application_Note_V1.0
-9-
GSM SMS Application Note
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.
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Table 6: AT+CSCA Syntax
Command
Possible Response
AT+CSCA=?
OK
AT+CSCA?
+CSCA: <sca>,<tosca>
AT+CSCA=<sca>[,<tosca>]
OK
Parameters:
<sca>
<tosca>
SC Address in string format
Type of SCA in integer format
<tosca> uses <TOA> (Type of Address) decimal format (see [4]GSM 03.40 sub clause 9.1.2.5).
Example:
AT+CSCS?
+CSCS: "GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
OK
AT+CSCS="UCS2"
OK
AT+CSCA?
+CSCA: "002B0038003600310033003800300030003200310030003500300030",145
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
GSM_SMS_Application_Note_V1.0
- 10 -
GSM SMS Application Note
check it before sending short message.
1.2.4.
Set Preferred Message Storage (+CPMS)
AT+CPMS selects memory storages to be used for reading, writing, receiving and etc.
Table 7: 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>
,<mem3>]
+CPMS:
<used1>,<total1>,<used2>,<total2>,<used
3>,<total3>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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 300, and the maximum number in module is 200,
and SIM card is preferred. So if SIM card can store 150 messages, the module can only store 150
messages.
GSM_SMS_Application_Note_V1.0
- 11 -
GSM SMS Application Note
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.
2.1.1.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Set Text Mode Parameter (+CSMP)
AT +CSMP sets SMS parameters for text mode.
Table 8: 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,167,0,241
AT+CSMP=[<fo>[<
vp>[,pid>[,<dcs>]]]]
OK
Recommended <+CSCS> and <dcs> in text mode:
English
other language
want to store message
+CSCS="GSM"
<dcs>=241
+CSCS="UCS2"
<dcs>=25
want to immediately
display message and
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.
GSM_SMS_Application_Note_V1.0
- 12 -
GSM SMS Application Note
2.1.2.
Send Message directly from Terminal (+CMGS)
Table 9: AT+CMGS Syntax in text mode
Command
Possible Response
AT+CMGS=?
OK
AT+CMGS=<da>[,<tod
a>]<CR>
>text is entered
<ctrl-Z/ESC>
+CMGS: <mr>
or +CMS ERROR:
<err>
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
Send Chinese characters “ 测 试 ” to
13795403834:
AT+CSCS=”UCS2”
AT+CMGS=”
003100330037003900350034003000330038
00330034”
>6D4B8BD5 <Ctrl+Z>
Parameters:
<da>
<toda>
<mr>
[3]GSM 03.40 TP-Destination-Address in string format
Type of <da> in integer format, see Type Of Address
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 10: 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.
GSM_SMS_Application_Note_V1.0
- 13 -
GSM SMS Application Note
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 11: 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"
> teset <Ctrl+Z>
+CMGW: 54
//Write message successfully and the index is 54
OK
AT+CMSS=54
+CMSS: 122
//Send message to <da> "15021012496" which 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.
GSM_SMS_Application_Note_V1.0
- 14 -
GSM SMS Application Note
2.2.1.
Show Text Mode Parameters (+CSDH)
Table 12: 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
Parameter <show> value
0
1
not show (default)
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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 13: 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 GSM 03.38.
<mode> controls the processing of URC specified within this command.
<mode> values: refer to below figure ([2]GSM07.05 Section 3 Figure 2)
GSM_SMS_Application_Note_V1.0
- 15 -
GSM SMS Application Note
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
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
<mt> values:
The rules for storing received SMs depend on <dcs>, preferred memory storage <mem3> setting
(+CPMS) and this value
0
No SMS-DELIVER indications are routed to the TE.
1
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>
GSM_SMS_Application_Note_V1.0
- 16 -
GSM SMS Application Note
2
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 Command Show Text Mode
Parameters +CSDH).
Class 2 messages result in indication as defined in <mt>=1: +CMTI
3
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
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
<bm> value affects CBMs and so be ignored in this document.
<ds> value sets whether routing SMS-STATUS-REPORT.
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
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).
1
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]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 14: AT+CMGR Syntax in text mode
Command
Possible Response in Text Mode
AT+CMGR=?
OK
GSM_SMS_Application_Note_V1.0
- 17 -
GSM SMS Application Note
AT+CMGR=<ind
ex>[,<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>
<mode>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Integer type; value in the range of location numbers supported by the associated
memory
0
Normal. If status of the message is 'received unread', status in the storage
changes to 'received read'.
1
Not change status of the specified SMS record
Example:
Write and read
SM:
AT+CMGW
> test<CTRL+Z>
+CMGW: 6
OK
Receive and read
SM:
AT+CNMI=2,1,0,0,
0
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
OK
OK
+CMTI: "SM",3
AT+CMGR=3
+CMGR: "REC
UNREAD","+86150210124
96","","2010/08/18
17:29:12+32"
test
OK
Receive and display
SM directly:
AT+CNMI=2,2,0,0,
0
+CMT:
"+8615021012496",,"2010/0
8/18 17:32:02+32"
test
+CMTI: "SM",4
AT+CMGR=4
+CMGR: "REC
UNREAD","+8615021012496","","201
0/08/18
17:37:23+32",145,4,0,241,"+86138002
10500",145,4
test
+CMT:
"+8615021012496",,"2010/08/18
17:26:52+32",145,4,0,0,"+8613800210
500",145,4
test
Note:
 The difference of text mode and PDU mode: only the response format.
GSM_SMS_Application_Note_V1.0
- 18 -
GSM SMS Application Note
2.2.4.
List Short Messages from Preferred Storage (+CMGL)
Table 15: 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>[...]]
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
The execution command AT+CMGL returns messages with status value <stat> from preferred
message storage <mem1> to the TE.
Parameters:
Text value
<state>
<mode>
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
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"
+CMGL: 3,"REC
READ","+8615021012496","","2010/08/18
17:29:12+32",145,4
GSM_SMS_Application_Note_V1.0
- 19 -
GSM SMS Application Note
test
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
2.3. Status Report
Status report can be used to get information whether a short message is received by the target
address after it’s sent. If status report is needed, two parameters should be set in text mode:
1) AT+CNMI=2,1,0,1,0
//The forth parameter <ds> must be equals to 1
2) AT+CSMP=49,167,0,241 //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 example.
2.4. Delete Short Messages
2.4.1.
Delete One or all Short Message (+CMGD)
Table 16: 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>:
GSM_SMS_Application_Note_V1.0
- 20 -
GSM SMS Application Note
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Delete All Short Messages (+QMGDA)
Table 17: AT+QMGDA Syntax in text mode
Command
AT+QMGDA=?
Possible Response
+QMGDA: (listed of
supported <type>s)
+CMS ERROR: <err>
Example
Text mode:
+QMGDA:("DEL READ","DEL
UNREAD","DEL SENT","DEL
UNSENT","DEL INBOX","DEL ALL")
PDU mode:
+QMGDA:(1-6)
AT+QMGDA=<type>
OK
ERROR
+CMS ERROR:<err>
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: the parameter <type> value.
GSM_SMS_Application_Note_V1.0
- 21 -
GSM SMS Application Note
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 +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.1
+CSCA: "+8613800210500",145
OK
//Step 1: Check service center address
(same as step 1 of sender)
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
//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,241
// 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
GSM_SMS_Application_Note_V1.0
OK
OK
- 22 -
GSM SMS Application Note
AT+CSDH=1
//More information will
be displayed if it equals 1.
OK
//Step 3: Send English short message
AT+CMGS="13795403834"
// 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>
+CMGS: 140
OK
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
//Step 3: Receive and read short message
+CMTI: "SM",1
AT+CMGR=1
+CMGR: "REC
UNREAD","+8613651979176","","2010/09/0
1
11:11:47+32",145,4,0,241,"+8613800210500"
,145,5
Hello
OK
AT+CSCS="UCS2"
//if set character set as
“UCS2”, the message content will
be displayed in UCS2 format.
OK
AT+CMGR=1
+CMGR: "REC
READ","002B0038003600310033003600350
031003900370039003100370036","","2010/0
9/01
11:11:47+32",145,4,0,241,"002B0038003600
3100330038003000300032003100300035003
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.
GSM_SMS_Application_Note_V1.0
- 23 -
GSM SMS Application Note
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 241 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.
2.5.2.
Send Chinese short message(UCS2 coding) and require status report
For example: send “您好” (UCS2 coding “60A8597D”) to 13795403834
Sender: 13651979176
Receiver: 13795403834
//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
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
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. 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="0031003300370039003500340
0300033003800330034"
//
Send SMS: Enter the mobile phone
number in UCS2 coding as set in
+CSCS. Enter message content in
UCS2 format after “>” and end the
GSM_SMS_Application_Note_V1.0
- 24 -
GSM SMS Application Note
input by pressing Ctrl and “Z”
simultaneously.
> 60A8597D <Ctrl+Z>
+CMGS: 141
OK
//Step 3: Receive and read short message
+CMT: "+8613651979176",,"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,"+8613795403834",145,"2010/09/01
11:25:55+32","2010/09/01 11:25:55+32",0
Note 1:
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 short
message content 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.
GSM_SMS_Application_Note_V1.0
- 25 -
GSM SMS Application Note
3. SMS in PDU mode
3.1. Write and Send Short Message
3.1.1.
Send Message direct from Terminal (+CMGS)
Table 18: 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 19: 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
GSM_SMS_Application_Note_V1.0
- 26 -
GSM SMS Application Note
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.
3.2.1.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Read Short Messages (+CMGR)
Table 20: 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 21: 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
GSM_SMS_Application_Note_V1.0
- 27 -
GSM SMS Application Note
"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:
1) AT+CNMI=2,1,0,1,0 //The forth parameter <ds> must be equals to 1
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 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 [4]GSM 03.40 subclause 9 for details except element <DCS><UDL><UD> which
are defined in [3]GSM 03.38.
GSM_SMS_Application_Note_V1.0
- 28 -
GSM SMS Application Note
&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 22: 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
3.5.2.
SMS-Deliver PDU Packet (MT)
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Table 23: 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 24: Status-Report Packet
number
of octets
Element
1-12
1
1
2-12
7
7
1
1
1
1
1
0140
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 25: <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 GSM 04.08 subclause 10.5.4.7 Called party BCD number for details of TON (Type
of Number) and NPI (Numbering plan identification).
3.5.4.2. Service Center Address <SCA>
Table 26: <SCA>
GSM_SMS_Application_Note_V1.0
- 29 -
GSM SMS Application Note
Element
SCA length
Example(&h)
08
TOA
91
SCA
683108200105F0
Above example shows <sca> address “+8613800210500” (SCA of China Mobile in Shanghai).
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Original number
86 13 80 02 10 05 0(F)
after formatting
68 31 08 20 01 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 27: <OA>/<DA>/<RA>
Element
Example(&h)
Address length
TOA
OA/DA/RA
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 maybe fail to send.
 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) – It’s 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.
Table 28: <FO> elements
Bit
7
6
5
SMS-Submit
RP
UDHI
SRR
VPF
SMS-Deliver
RP
UDHI
SRI
-
GSM_SMS_Application_Note_V1.0
4
3
2
1
0
RD
MTI
MMS
MTI
- 30 -
GSM SMS Application Note
SMS-Status
Report
RP
UDHI
SRQ
-
MMS
MTI
<FO> parameters
Value
(bit)
Parameter
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
Status Report
Indication
0
A status report will not be returned to the SME
1
A status report will be returned to the SME
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
1
The SMS-Status-Report is the result of a
SMS-Command, e.g. an Enquiry
00
VP field 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
10
SMS-Status Report
10
SMS-Command (in the direction MS to SC)
RP
Reply Path
UDHI
SRI
SRR
SRQ
VPF
MMS
RD
MTI
Meaning
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Status Report
Qualifier
Validity Period
Format
More Messages
to Send
Reject
Duplicates
Message Type
Indicator
(in the direction MS to SC)
(in the direction SC to MS)
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
&h
&d
Bit 7
6
5
RP
UDHI
SRR
GSM_SMS_Application_Note_V1.0
4
3
VPF
2
RD
1
0
MTI
- 31 -
GSM SMS Application Note
0
00010001
11
17
0
0
10
No header
in UD
not request
status report
VP relative
format
0
1
10
No header
in UD
request
status report
VP relative
format
0
00110001
31
49
0
01
SMS-Submit
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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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 29: <PID>
<PID> value
&h
00
01
Protocol
&d
0
The SMS has to be treat as a short message
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] GSM 03.38 for details.
Table 30: <DCS>
bit7-4
00xx
( general data
coding
indication)
1111
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
0
default alphabet
0
1
8 bit alphabet
1
0
UCS2 (16 bit)
1
1
Reserved
0
GSM_SMS_Application_Note_V1.0
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
reserved
- 32 -
GSM SMS Application Note
(data coding
message class)
0
default alphabet
1
8-bit data
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’s 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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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.
Table 31: <VP> relative format
<VP> value
&h
00 to 8F
Validity period value
&d
0 to 143
(VP+1)*5 minutes
5 minutes to 12 hours
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
90 to A7
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).
GSM_SMS_Application_Note_V1.0
- 33 -
GSM SMS Application Note
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 32: <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.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
3.5.4.10. Discharge Time <DT>
The TP-Discharge-Time field indicates the time at which a 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 depends of alphabet defined in <DCS>.
bits per
character
SMS UDL
meaning
character table
Default(GSM 7-bit)
7
Number of
characters
see [3]GSM03.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
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).
General characters in English can be found in GSM alphabet table ([3] GSM 03.08 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 [3] GSM 03.08 subclause 6.1.2.1.1 for SMS point-to-point packing of 7-bit
characters.
GSM_SMS_Application_Note_V1.0
- 34 -
GSM SMS Application Note
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’s the number of
characters, not number of octets).
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
3.5.4.13. Status <ST>
ST indicates the status of a previously submitted SMS-SUBMIT when a status report has been
requested. It consists of one octet. If it equals to “00”&h, that 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.
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
OK
//Step 1: Check service center address
(same as step 1 of sender)
AT+CSCS="GSM"
OK
AT+CSCA?
+CSCA: "+8613800210500",145
//Step 2: Set PDU mode
AT+CMGF=0
// Set the short message
//Step 2: Set PDU mode and parameters
for receiving messages
GSM_SMS_Application_Note_V1.0
OK
- 35 -
GSM SMS Application Note
mode as PDU mode.
AT+CMGF=0
OK
// Set the short message
mode as PDU mode.
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",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
//Step 3: Send English short message
AT+CMGS=20
>
0011000D91683197453038F400000105C8329
BFD06 <Ctrl+Z>
+CMGS: 146
OK
//See below Note 1 for descriptions
//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
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:
GSM_SMS_Application_Note_V1.0
- 36 -
GSM SMS Application Note
&b
&h
00010001
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:
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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
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
04
0D9168315
6919771F6
00
0190102
1912523
05
C832
9BFD
06
Example
0891683108
200105F0
00
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
MMS
01
1
0
MTI
00
UDHI = 0: no header in UD
MMS = 1: No more messages are waiting for the MS in this SC
GSM_SMS_Application_Note_V1.0
- 37 -
GSM SMS Application Note
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
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
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
//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
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
//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
GSM_SMS_Application_Note_V1.0
- 38 -
GSM SMS Application Note
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>
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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
00
31
00
0D916831974
53038F4
00
08
01
04
60A8597
D
Example
19 = octets number of (<pdu>-<sca> = 31000D91683197453038F40008010460A8597D)
SCA = 00: Service center address is defined in AT command +CSCA.
FO = 31&h = 49&d:
&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 “您好”
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
GSM_SMS_Application_Note_V1.0
- 39 -
GSM SMS Application Note
Example
08916831082
00105F0
24
0D9168315
6919771F6
00
0190103
1424123
08
60A859
7D
04
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
-
2
1
MMS
00
0
MTI
01
00
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
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
SMS-Status Report PDU:
number of
octets
1-12
1
1
2-12
7
7
1
Element
SCA
FO
MR
RA
SCTS
DT
ST
0891683108
200105F0
06
93
0D9168319745
3038F4
01901031
429123
01901031
429123
00
Example
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
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
GSM_SMS_Application_Note_V1.0
- 40 -
GSM SMS Application Note
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.
4.1.1.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Save SMS Settings (+CSAS)
Table 33: 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 34: 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
+CPMS is saved automatically.
+QCLASS0 and +QSMSCODE are not able to save.
The following settings can be saved by command AT&W, restored by command ATZ, and return
to manufacturer defaults by command AT&F.
 +CMGF
 +CNMI
GSM_SMS_Application_Note_V1.0
- 41 -
GSM SMS Application Note


+CSDH
+CSCS
4.2. Concatenated Short Message
Quectel module supports concatenated short message. User is able to send and receive
concatenated short messages using the same normal format in text mode. Message will be divided
to 1 ~ 5 short messages when sending and merged to one message when receiving. Every short
message sets UDHL as 1 in <FO> field and adds header information in the UD field. See [4] GSM
03.40 subclause 9.2.3.24.1 for more details. See the example below.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
Example:
//Send a long 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,241
// Set parameters for sending short message in text mode
OK
AT+CMGS=”13795403834”
> Focusing on the wireless M2M market sector, Quectel designs and manufactures variety
wireless modules to fulfill different industrial standards and requirements. The Quectel
products have been applied in the wireless M2M sectors like telematics, telemetry, remote
control and monitoring, fleet management, wireless POS, security, healthcare, etc.
//The message length is 347, larger than the maximum length of a single short
message 152. So it will be divided to three messages (length 152+152+43) to
send, and merged when receiving.
+CMGS: 156
OK
//Receive a long message
+CMTI: "SM",3
//Indication of receiving three messages, saved to SIM card
+CMTI: "SM",4
+CMTI: "SM",5
AT+CMGF=1
OK
AT+CMGR=3
+CMGR: "REC UNREAD","+8613651979176","","2010/09/01 15:01:54+32"
Focusing on the wireless M2M market sector, Quectel designs and manufactures variety
wireless modules to fulfill different industrial standards and requirements. The Quectel
products have been applied in the wireless M2M sectors like telematics, telemetry, remote
GSM_SMS_Application_Note_V1.0
- 42 -
GSM SMS Application Note
control and monitoring, fleet management, wireless POS, security, healthcare, etc.
//Three parts are merged to display in the first message.
OK
AT+CMGR=4
+CMGR: "REC READ","+8613651979176","","2010/09/01 15:01:52+32"
irements. The Quectel products have been applied in the wireless M2M sectors like
telematics, telemetry, remote control and monitoring, fleet management
//Second part, 152 characters
OK
AT+CMGR=5
+CMGR: "REC READ","+8613651979176","","2010/09/01 15:01:54+32"
, wireless POS, security, healthcare, etc.
//Third part, 43 characters
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
OK
AT+CMGD=3
//If delete the first message, three messages of this long message will be deleted
OK
AT+CPMS?
+CPMS: "SM",2,50,"SM",2,50,"SM",2,50
OK
4.3. 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.
Table 35: 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
GSM_SMS_Application_Note_V1.0
- 43 -
GSM SMS Application Note
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
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
//Receive Class0 message when QCLASS0=0
AT+QCLASS0?
+QCLASS0: 0
OK
AT+CMGF=1
OK
AT+CNMI?
+CNMI: 2,1,0,0,0
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
+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.4. Configure SMS code mode (+QSMSCODE)
Some special characters are not included in the GSM alphabet table. Quectel module provides AT
command +QSMSCODE to code special characters in GSM 7-bit coding in text mode.
Table 36: AT+QSMSCODE syntax
Command
Possible Response
GSM_SMS_Application_Note_V1.0
- 44 -
GSM SMS Application Note
AT+QSMSCODE=?
+QSMSCODE:(0,1)
AT+QSMSCODE?
+QSMSCODE:<mode>
AT+QSMSCODE=<mode>
OK
ERROR
Parameter <mode>
0
Code mode according with NOKIA
1
Code mode according with SIEMENS (default)
Note:
 Set AT+CMGF=1, AT+CSCS=”GSM”, <dcs> (+CSMP) as GSM-7-bit coding before using
this command.
 Use the same setting for sender and receiver.
 This command is still not able to make sure all special characters are shown correctly. The
best method is to use UCS2 coding.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
4.5. Notify for SMS 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. 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:
GSM_SMS_Application_Note_V1.0
- 45 -
GSM SMS Application Note
+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
GSM_SMS_Application_Note_V1.0
- 46 -
GSM SMS Application Note
5. Appendix
5.1. Message service send and write procedures
[2] GSM 07.05 clause 3 Figure 4.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
GSM_SMS_Application_Note_V1.0
- 47 -
GSM SMS Application Note
5.2. Message receiving procedures
Refer to [2] GSM 07.05 Clause 3 Figure 3.
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
5.3. Default GSM alphabet
Refer to [3] GSM 03.08 subclause 6.2.1 Default alphabet.
GSM_SMS_Application_Note_V1.0
- 48 -
GSM SMS Application Note
l
e
t
l
c
a
e
i
t
u
n
Q ide
f
n
o
C
GSM_SMS_Application_Note_V1.0
- 49 -
GSM SMS Application Note
sales@eddywireless.com
Shanghai Quectel Wireless Solutions Co., Ltd.
Room 501, Building 13, No.99, Tianzhou Road, Shanghai, China 200233
Tel: +86 21 5108 6236
Mail: info@quectel.com
GSM_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