Short Message Service From 3GPP TS 27.005 V5.0.0.

Short Message Service

From 3GPP TS 27.005 V5.0.0

2003/07/16 V0.1

OutLineOutLine General Configuration Commands Enter SMS Block Mode Protocol Message Service Failure Result Code Message Configuration Commands Message Receiving and Reading Commands Message Sending and Writing Commands

2003/07/16 V0.1

General Configuration CommandsGeneral Configuration Commands

Select Message Service +CSMS

<service>:0 the syntax of SMS AT commands is compatible with GSM 07.05

Phase 2 version 4.7.0;

1 the syntax of SMS AT commands is compatible with GSM 07.05

Phase 2+ version;

<mt>, <mo>, <bm>:0 type not supported

1 type supported

2003/07/16 V0.1

General Configuration Commands (Cont.)General Configuration Commands (Cont.)

Example:

AT+CSMS=? (inquiry of available services in TA)

+CSMS: (0)

OK

AT+CSMS=0;

+CSMS: 1,1,1

OK

2003/07/16 V0.1


Preferred Message Storage +CPMS<mem1>: memory from which messages are read and deleted <mem2>: memory to which writing and sending operations are

made

<mem3>: memory to which received SMs are preferred to be

stored

"BM" : broadcast message storage

"ME" : ME message storage"MT" : any of the storages associated with ME"SM" : (U)SIM message storage"TA“: TA message storage"SR“: status report storage

2003/07/16 V0.1


Example:

AT+CPMS=?

+CPMS: ("BM","ME","SM"),("ME","SM"),("ME","SM")

OK

AT+CPMS="ME","ME","ME";

+CPMS: "ME",5,99,"ME",5,99,"ME",5,99 (five messages in ME, 99 total

space)

OK

2003/07/16 V0.1


Message Format +CMGF<mode>:

0 PDU mode (default when implemented) (entire TP data units used)

1 text mode(headers and body of the messages given as separate parameters).

Example:

AT+CMGF=?; +CMGF=1;

+CMGF: (0,1)

OK

2003/07/16 V0.1

Enter SMS Block Mode ProtocolEnter SMS Block Mode Protocol Enter SMS Block Mode Protocol

+CESP

2003/07/16 V0.1

Message Service Failure Result CodeMessage Service Failure Result Code Message Service Failure Result Code +CMS

ERROR<err> values used by common messaging commands:0...127 3GPP TS 24.011 [6] clause E.2 values 128...255 3GPP TS 23.040 [3] clause 9.2.3.22 values. 300 ME failure301 SMS service of ME reserved302 operation not allowed303 operation not supported304 invalid PDU mode parameter305 invalid text mode parameter310 (U)SIM not inserted311 (U)SIM PIN required312 PH-(U)SIM PIN required313 (U)SIM failure

2003/07/16 V0.1

314 (U)SIM busy315 (U)SIM wrong316 (U)SIM PUK required317 (U)SIM PIN2 required318 (U)SIM PUK2 required320 memory failure321 invalid memory index322 memory full330 SMSC address unknown331 no network service332 network timeout340 no +CNMA acknowledgement expected500 unknown error...511 other values in range 256...511 are reserved512... manufacturer specific

Message Service Failure Result Code (Cont.)Message Service Failure Result Code (Cont.)

2003/07/16 V0.1

Message Configuration CommandsMessage Configuration Commands Service Centre Address

+CSCA=<sca>[,<tosca>]

Example 1:

AT+CSCA?

+CSCA: "+358501234567",145

OK

Example from 388c:

(000052.8110)>A AT+CSCA?

(000052.8357)<A

+CSCA: "+8613800100500",145

(000052.8441)<A

OK

2003/07/16 V0.1

Message Configuration Commands(Cont.)Message Configuration Commands(Cont.)

Set Text Mode Parameters +CSMP=[<fo>[,<vp>[,<pid>[,<dcs>]]]]

Example:

AT+CSMP?

+CSMP: 17,167,0,0

2003/07/16 V0.1


Show Text Mode Parameters +CSDH=[<show>]

Example:

AT+CSDH=1 (show all headers in text mode)

OK

2003/07/16 V0.1


Select Cell Broadcast Message Types +CSCB=[<mode>[,<mids>[,<dcss>]]]

Example:

AT+CSCB=1 (all CBMs are accepted)

OK

2003/07/16 V0.1


Save Settings +CSAS[=<profile>]

2003/07/16 V0.1


Restore Settings +CRES[=<profile>]

Example:

AT+CRES (restore settings from non-volatile memory to volatile memory)

OK

2003/07/16 V0.1

Message Receiving and Reading CommandsMessage Receiving and Reading Commands

New Message Indications to TE +CNMI=[<mode>[,<mt>[,<bm>[,<ds>[,<bfr>]]]]]

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)

<mode>: controls the processing of unsolicited result codes specified within this command,

0 Buffer unsolicited result codes in the TA.

1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved. Otherwise forward them directly to the TE.

2 Buffer unsolicited result codes in the TA when TA-TE link is reserved and flush them to the TE after reservation. Otherwise forward them directly to the TE.

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

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)<mt>: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>

2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code:+CMT: <oa>, [<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>, <length>]<CR><LF><data> Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in <mt>=1.

3 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in <mt>=2. Messages of other data coding schemes result in indication as defined in <mt>=1.

2003/07/16 V0.1

Message Receiving and Reading CommandsMessage Receiving and Reading Commands

SMS-DELIVER result code and acknowledgement summary

<mt>

no class or class 1

class 0 or message waiting indication group (discard)

class 2 or message waiting indication group (store)

class 3

1 +CMTI [+CMTI1)] +CMTI +CMTI

2 +CMT & +CNMA3)

+CMT [& +CNMA2)]

+CMTI +CMT & +CNMA3)

3 +CMTI [+CMTI1)] +CMTI +CMT & +CNMA3)

1) result code is sent when ME does not have other display device than AT interface.2) acknowledgement command must be sent when +CSMS <service> value equals 1 and ME does not have other display device than AT interface.3) acknowledgement command must be sent when +CSMS <service> value equals 1.

2003/07/16 V0.1


The TP-Data-Coding-Scheme field, defined in GSM 03.40,

Coding Group Bits 3..0

Bit 1 Bit 0 Message Class:

0 0 Class 0

0 1 Class 1 Default meaning: ME-specific.

1 0 Class 2 SIM specific message.

1 1 Class 3 Default meaning: TE-specific (see GSM TS 07.05 [8])

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)<bm>:

0 No CBM indications are routed to the TE.

1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code:

+CBMI: <mem>,<index>

2 New CBMs are routed directly to the TE using unsolicited result code:

+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data> If ME supports data coding groups which define special routing also for messages other than class 3 (e.g. (U)SIM specific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in <bm>=1).

3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2. If CBM storage is supported, messages of other classes result in indication as defined in <bm>=1.

2003/07/16 V0.1


Table 3: <bm> parameter

<bm> Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2])

0 all schemes: as in 3GPP TS 23.038 [2]; if CBM storage is supported, store message to "BM" (or some manufacturer or data coding scheme specific memory)

1 all schemes: as <bm>=0 but send indication if message stored successfully

2 all schemes: route message to TE unless ME has detected a special routing to somewhere else (e.g. to (U)SIM; an indication may be sent if message stored successfully)

3 class 3: route message to TEothers: as <bm>=1 (if CBM memory storage is supported)

2003/07/16 V0.1


<ds>:

0 No SMS-STATUS-REPORTs are routed to the TE.

1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:

+CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>

2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code:

+CDSI: <mem>,<index>

2003/07/16 V0.1


<bfr>:

defines the handling method for buffered result codes when

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.

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)Example:

AT+CNMI=? (query new message unsolicited result code

modes)

+CNMI: (0-2),(0-3),(0-3),(0,1),(0,1)

OK

AT+CNMI=2,1,0,1,0 (send SM and status report indications to TE

OK when TA in command mode, otherwise buffer)

+CMTI: "ME",2 (new message received in index 2)

AT+CNMI=2,,2,,0 (CBMs will be sent to the TE)

OK

2003/07/16 V0.1


Example from 388C:

(000015.2778)>A AT+CNMI=000,000,002,000,000

(000015.3812)<A

OK

(000015.5282)>A AT+CNMI=000,002,000,000,000

(000015.5814)<A

OK

2003/07/16 V0.1


List Messages +CMGL[=<stat>]<stat>:

0 "REC UNREAD" received unread message (i.e. new message)

1 "REC READ" received read message

2 "STO UNSENT" stored unsent message (only applicable to SMs)

3 "STO SENT" stored sent message (only applicable to SMs)

4 "ALL" all messages (only applicable to +CMGL command)

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)SMS-SUBMITs and/or SMS-DELIVERs:

+CMGL: <index>,<stat>,<oa/da>,[<alpha>],[<scts>][,<tooa/toda>,<length>]<CR><LF><data>[<CR><LF>

SMS-STATUS-REPORTs:

+CMGL: <index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>[<CR><LF>

SMS-COMMANDs:

+CMGL: <index>,<stat>,<fo>,<ct>[<CR><LF>

CBM storage:

+CMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages><CR><LF><data>[<CR><LF>

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)<oa>: originating address<da>: destination address<alpha>: entry in phonebook<scts>: service center time stamp<mr>: message reference<ra>: receipient address<dt>: discharge-time<st>: status<ct>: command type<page>: page parameter bits 4-7<pages>: page parameter bits 0-3

2003/07/16 V0.1

Message Receiving and Reading Message Receiving and Reading Commands(Cont.)Commands(Cont.)SMS-DELIVER:

+CMGR: <stat>,<oa>,[<alpha>],<scts> [,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<CR><LF><data>

SMS-SUBMIT:+CMGR: <stat>,<da>,[<alpha>] [,<toda>,<fo>,<pid>,<dcs>,[<vp>],<sca>,<tosca>,<length>]<CR><LF><data>

SMS-STATUS-REPORT:+CMGR: <stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>

SMS-COMMAND:+CMGR: <stat>,<fo>,<ct> [,<pid>,[<mn>],[<da>],[<toda>],<length><CR><LF><cdata>]

CBM storage:+CMGR: <stat>,<sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data>

2003/07/16 V0.1


Example:

AT+CMGL="ALL" (read all SMs)

+CMGL: 1,"REC READ","+358501234567","Mr. Smith","95/07/03,17:45:03+04"

This is the body of the message.

+CMGL: 2,"STO UNSENT","+358501234567","Mr. Smith",

This is the body of the reply.

OK

2003/07/16 V0.1


Example:AT+CPMS="BM";+CMGL (select CBM memory for

reading; list all unread CBMs)+CMGL: 1,"REC UNREAD",100,40,1,3 (first page of

three page weather information)Weather in Finland 3rd of July 1995+CMGL: 2,"REC UNREAD",100,40,2,3 (second page of

three page weather information)Helsinki: cloudy, snow storms, -20 degrees Celsius, wind -14 m/s NE+CMGL: 3,"REC UNREAD",100,40,3,3 (third page of

three page weather information)Tampere: sunny, 40 degrees Celsius, wind 1 m/s SWOK

2003/07/16 V0.1


Read Message +CMGR=<index>

Example:

AT+CMGR=2 (read the message)

+CMGR: "REC UNREAD","+358507654321","Mr. Jones","95/07/03,17:38:15+04"

This is the Mr. Jones testing

OK

2003/07/16 V0.1


New Message Acknowledgement to ME/TA +CNMA

2003/07/16 V0.1

Message Sending and Writing CommandsMessage Sending and Writing Commands Send Message +CMGS=<da>[,<toda>]<CR>text is

entered<ctrl-Z/ESC>

Example:

AT+CMGS="+358501234567“ (start editing a message)

> This the first line. (edit first line and press carriage return)

> This is the last line.^Z (edit second line and send message by pressing control-Z)

+CMGS: 10 (success: message reference 10 returned from SMSC)

OK

2003/07/16 V0.1

Message Sending and Writing Message Sending and Writing Commands(Cont.)Commands(Cont.) Send Message from Storage +CMSS=<index>[,<da>[,<toda>]]

Example:

AT+CMSS=7 (send from storage)

+CMSS: 12 (success: reference value 12 sent from SC)

OK

2003/07/16 V0.1

Message Sending and Writing Message Sending and Writing Commands(Cont.)Commands(Cont.)

Write Message to Memory +CMGW[=<oa/da>[,<tooa/toda>[,<stat>]]]<CR>text is entered<ctrl-Z/ESC>

Example:

AT+CMGW="9501231234" (write message)

> This is the message body^Z

+CMGW: 7 (index number in storage returned)

OK

2003/07/16 V0.1


Delete Message +CMGD=<index>[,<delflag>]<delflag>: an integer indicating multiple message deletion request as

follows:0 (or omitted) Delete the message specified in <index> 1 Delete all read messages from preferred message storage, leaving

unread messages and stored mobile originated messages (whether sent or not) untouched

2 Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched

3 Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched.

4 Delete all messages from preferred message storage including unread messages

2003/07/16 V0.1


Example:

AT+CMGD=7 (delete message)

OK

2003/07/16 V0.1


Send Command +CMGC=<fo>,<ct>[,<pid>[,<mn>[,<da>[,<toda>]]]]<CR>

<ct>: command type

<mn>: message number

2003/07/16 V0.1


More Messages to Send +CMMS=[<n>]

controls the continuity of SMS relay protocol link. When feature is enabled (and supported by network) multiple messages can be sent much faster as link is kept open

2003/07/16 V0.1

PDU Mode The PDU mode uses the same commands and responses as the Text

Mode described However, the following commands and responses have a different

format– List Messages +CMGL – Read Message +CMGR – Send Message +CMGS – Write Message to Memory +CMGW – Send Command +CMGC – New Message Acknowledgement to ME/TA +CNMA

– Send Message from Storage +CMSS In the PDU mode, a complete SMS Message including all header

information is passed as a binary string. This binary string is composed of hexadecimal IA5 characters as defined in clause 3 above under

"Message Data Parameters".

2003/07/16 V0.1

Scenario of 388c—Read SIM SMS(002319.1072)>A AT+CMGL=4

(002319.4464)<A

+CMGL: 001,007,,027

(002319.4633)<A 0891683108100005F011FF00800000181534180E4783D95A30182CD682C16AB819AE8503

(002319.5621)<A

+CMGL: 002,001,,098

(002319.6387)<A

“PDU Data”(002319.6663)<A 155

(002319.6761)<A 6600218BE5776189C955660021

(002319.7627)<A

+CMGL: 003,001,,082

(002319.8207)<A

“PDU Data”

( TBC, See next page )

2003/07/16 V0.1

Scenario of 388c—Read SIM SMS(002319.9248)<A

+CMGL: 004,001,,126

(002319.9937)<A

“PDU Data”

(002320.0219)<A 651

(002320.0322)<A

“PDU Data”

(002320.1380)<A

+CMGL: 005,001,,052

(002320.1616)<A

“PDU Data”

(002320.2678)<A

+CMGL: 006,001,,148

(002320.3332)<A

“PDU Data”

(002320.3617)<A D67

(002320.3723)<A

“PDU Data”


2003/07/16 V0.1


+CMGL: 007,001,,144

(002320.5038)<A

“PDU Data”

(002320.5320)<A 453

(002320.5425)<A

“PDU Data”

(002320.6471)<A

+CMGL: 008,001,,050

(002320.6709)<A

“PDU Data”

(002320.7715)<A

+CMGL: 009,001,,056

(002320.8288)<A

“PDU Data”


2003/07/16 V0.1


+CMGL: 011,001,,046

(002320.9953)<A

“PDU Data”

(002321.1151)<A

+CMGL: 013,001,,060

(002321.2690)<A

“PDU Data”

(002321.2912)<A

OK

2003/07/16 V0.1

Scenario of 388c—Change SMS Storage

(000242.0486)>A AT+CNMI=000,001,000,000,000

(000243.1222)<A

OK

2003/07/16 V0.1

Scenario of 388c—Compose a new SMS, send to itself, receive and read it.

000638.1540)>A AT+CMEP?

(000638.1857)<A

+CMEP: 24

(000638.1922)<A

OK

(000638.3010)>A AT+CMGS=18

(000639.2268)<A

>

(000639.2303)>A 0891683108100005F011010B813119502669F00000A704D4F2940E

(000641.8945)<A

+CMGS: 000

(000641.9013)<A

OK

(000643.1090)<A

+CIEV: 3,1

(000643.1193)<A

+CMTI: "SM",010

(000643.7887)>A AT+CMGR=10

(000644.1312)<A

+CMGR: 003,,024

(000644.2015)<A 0891683108100005F0040D91683119502669F000003070812114512304D4F2940E

(000644.2118)<A

OK

2003/07/16 V0.1

Scenario of 388c—Compose a new SMS, send to a wrong number, receive a return message and read it.(001041.5792)>A AT+CMGS=18(001042.4935)<A > (001042.4971)>A 0891683108100005F011030B811111317616F40000A704F4F19C0E(001045.3500)<A +CMGS: 000

(001045.3569)<A OK

(001053.6298)<A +CMTI: "SM",014

(001053.6388)>A AT+CMGR=14(001053.8211)<A +CMGR: 003,,023

(001053.8578)<A 0891683108100005F02404A11111210830708121747223080074006300730074(001053.8681)<A OK

(001068.2865)>A AT+CMGL=0(001068.7655)<A +CMGL: 014,003,,023

(001068.7936)<A 0891683108100005F02404A111112108307

Short Message Service From 3GPP TS 27.005 V5.0.0.

Documents

Transcript of Short Message Service From 3GPP TS 27.005 V5.0.0.