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

2. 2003/07/16 V0.1 OutLine 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

3. 2003/07/16 V0.1 General Configuration Commands Select Message Service +CSMS : 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 ;,, : 0 type not supported 1 type supported

4. 2003/07/16 V0.1 General Configuration Commands (Cont.) Example: AT+CSMS=?(inquiry of available services in TA) +CSMS: (0) OK AT+CSMS=0; +CSMS: 1,1,1 OK

5. 2003/07/16 V0.1 General Configuration Commands (Cont.) Preferred Message Storage +CPMS : memory from which messages are read and deleted : memory to which writing and sending operations are made : 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

6. 2003/07/16 V0.1 General Configuration Commands (Cont.) 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

7. 2003/07/16 V0.1 General Configuration Commands (Cont.) Message Format +CMGF : 0PDU 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

8. 2003/07/16 V0.1 Enter SMS Block Mode Protocol Enter SMS Block Mode Protocol +CESP

9. 2003/07/16 V0.1 Message Service Failure Result Code Message Service Failure Result Code +CMS ERROR values used by common messaging commands: 0...1273GPP TS 24.011 [6] clause E.2 values 128...2553GPP TS 23.040 [3] clause 9.2.3.22 values. 300ME failure 301SMS service of ME reserved 302operation not allowed 303operation not supported 304invalid PDU mode parameter 305invalid text mode parameter 310(U)SIM not inserted 311(U)SIM PIN required 312PH-(U)SIM PIN required 313(U)SIM failure

10. 2003/07/16 V0.1 314(U)SIM busy 315(U)SIM wrong 316(U)SIM PUK required 317(U)SIM PIN2 required 318(U)SIM PUK2 required 320memory failure 321invalid memory index 322memory full 330SMSC address unknown 331no network service 332network timeout 340no +CNMA acknowledgement expected 500unknown error...511other values in range 256...511 are reserved 512...manufacturer specific Message Service Failure Result Code (Cont.)

11. 2003/07/16 V0.1 Message Configuration Commands Service Centre Address +CSCA= [, ] 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

12. 2003/07/16 V0.1 Message Configuration Commands(Cont.) Set Text Mode Parameters +CSMP=[ [, [, [, ]]]] Example: AT+CSMP? +CSMP: 17,167,0,0

13. 2003/07/16 V0.1 Message Configuration Commands(Cont.) Show Text Mode Parameters +CSDH=[ ] Example: AT+CSDH=1(show all headers in text mode) OK

14. 2003/07/16 V0.1 Message Configuration Commands(Cont.) Select Cell Broadcast Message Types +CSCB=[ [, [, ]]] Example: AT+CSCB=1(all CBMs are accepted) OK

15. 2003/07/16 V0.1 Message Configuration Commands(Cont.) Save Settings +CSAS[= ]

16. 2003/07/16 V0.1 Message Configuration Commands(Cont.) Restore Settings +CRES[= ] Example: AT+CRES (restore settings from non-volatile memory to volatile memory) OK

17. 2003/07/16 V0.1 Message Receiving and Reading Commands New Message Indications to TE +CNMI=[ [, [, [, [, ]]]]]

18. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : controls the processing of unsolicited result codes specified within this command, 0Buffer unsolicited result codes in the TA. 1Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved. Otherwise forward them directly to the TE. 2Buffer 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. 3Forward 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

19. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : 0No SMS-DELIVER indications are routed to the TE. 1If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CMTI:, 2SMS-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:, [ ], [,,,,,,, ] Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in =1. 3Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in =2. Messages of other data coding schemes result in indication as defined in =1.

20. 2003/07/16 V0.1 Message Receiving and Reading Commands SMS-DELIVER result code and acknowledgement summary 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[+CMTI 1) ]+CMTI 2+CMT & +CNMA 3) +CMT [& +CNMA 2) ] +CMTI+CMT & +CNMA 3) 3+CMTI[+CMTI 1) ]+CMTI+CMT & +CNMA 3) 1) result code is sent when ME does not have other display device than AT interface. 2) acknowledgement command must be sent when +CSMS value equals 1 and ME does not have other display device than AT interface. 3) acknowledgement command must be sent when +CSMS value equals 1.

21. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) 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])

22. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : 0No CBM indications are routed to the TE. 1If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CBMI:, 2New CBMs are routed directly to the TE using unsolicited result code: +CBM:,,,, 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 =1). 3Class 3 CBMs are routed directly to TE using unsolicited result codes defined in =2. If CBM storage is supported, messages of other classes result in indication as defined in =1.

23. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) Table 3: parameter 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 =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 TE others: as =1 (if CBM memory storage is supported)

24. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : 0No SMS-STATUS-REPORTs are routed to the TE. 1SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: +CDS:,,[ ],[ ],,, 2If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: +CDSI:,

25. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : defines the handling method for buffered result codes when 0TA buffer of unsolicited result codes defined within this command is flushed to the TE when 1...3 is entered (OK response shall be given before flushing the codes). 1TA buffer of unsolicited result codes defined within this command is cleared when 1...3 is entered.

26. 2003/07/16 V0.1 Message Receiving and Reading 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

27. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) 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

28. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) List Messages +CMGL[= ] : 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)

29. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) SMS-SUBMITs and/or SMS-DELIVERs: +CMGL:,,,[ ],[ ][,, ] [ SMS-STATUS-REPORTs: +CMGL:,,,,[ ],[ ],,, [ SMS-COMMANDs: +CMGL:,,, [ CBM storage: +CMGL:,,,,, [

30. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) : originating address : destination address : entry in phonebook : service center time stamp : message reference : receipient address : discharge-time : status : command type : page parameter bits 4-7 : page parameter bits 0-3

31. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) SMS-DELIVER: +CMGR:,,[ ], [,,,,,,, ] SMS-SUBMIT: +CMGR:,,[ ] [,,,,,[ ],,, ] SMS-STATUS-REPORT: +CMGR:,,,[ ],[ ],,, SMS-COMMAND: +CMGR:,, [,,[ ],[ ],[ ], ] CBM storage: +CMGR:,,,,,

32. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) 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

33. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) 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 SW OK

34. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) Read Message +CMGR= 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

35. 2003/07/16 V0.1 Message Receiving and Reading Commands(Cont.) New Message Acknowledgement to ME/TA +CNMA

36. 2003/07/16 V0.1 Message Sending and Writing Commands Send Message +CMGS= [, ] text is entered 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

37. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) Send Message from Storage +CMSS= [, [, ]] Example: AT+CMSS=7(send from storage) +CMSS: 12(success: reference value 12 sent from SC) OK

38. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) Write Message to Memory +CMGW[= [, [, ]]] text is entered Example: AT+CMGW="9501231234"(write message) > This is the message body^Z +CMGW: 7(index number in storage returned) OK

39. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) Delete Message +CMGD= [, ] : an integer indicating multiple message deletion request as follows: 0 (or omitted)Delete the message specified in 1Delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched 2Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched 3Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched. 4Delete all messages from preferred message storage including unread messages

40. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) Example: AT+CMGD=7(delete message) OK

41. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) Send Command +CMGC=, [, [, [, [, ]]]] :command type : message number

42. 2003/07/16 V0.1 Message Sending and Writing Commands(Cont.) More Messages to Send +CMMS=[ ] 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

43. 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".

44. 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 )

45. 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” ( TBC, See next page )

46. 2003/07/16 V0.1 Scenario of 388c—Read SIM SMS (002320.4341)<A +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” ( TBC, See next page )

47. 2003/07/16 V0.1 Scenario of 388c—Read SIM SMS (002320.9736)<A +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

48. 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

49. 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

50. 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