TS 27.005
Use of DTE-DCE Interface
for SMS and CBS
V18.0.0 (PDF)
2024/03 … p.
V17.0.0
2022/03 70 p.
V16.0.0
2020/06 70 p.
V15.0.0
2018/06 69 p.
V14.0.0
2017/03 70 p.
V13.0.0
2015/12 70 p.
V12.0.0
2014/09 70 p.
V11.0.0
2011/12 70 p.
V10.0.1
2011/10 70 p.
V9.0.1
2011/10 70 p.
V8.0.1
2011/10 70 p.
V7.0.0
2006/03 70 p.
V6.0.1
2005/01 70 p.
V5.0.1
2005/01 70 p.
V4.2.1
2005/01 70 p.
V3.2.0
2002/06 70 p.
GSM Rel-98 v7.0.1
1999/08 66 p.
GSM Rel-97 v6.0.0
1998/10 65 p.
GSM Rel-96 v5.5.0
1997/12 68 p.
GSM Phase-2 v4.8.1
1996/11 68 p.
- Rapporteur:
- Mr. Aghili, Behrouz
InterDigital Communications
full Table of Contents for TS 27.005 Word version: 17.0.0
0 Scope
1 Reference configuration
2 SMS Block Mode
3 Text Mode
4 PDU Mode
A Character Set Conversions for SMS Text Mode
B Example of processing a data block
$ Change History
0 Scope p. 7
The present document defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.
Clause 2 defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible.
Clause 3 defines a character-based interfaced based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in V.25ter. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages.
Clause 4 defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE.
In all three modes, the terminal is considered to be in control for SMS/CBS transactions.
The present document considers the mobile termination to be a single entity. Other 3GPP/GSM Technical Specifications describe the split of functionality between the mobile equipment and (U)SIM.
The three "modes" referred to above, are represented in Figure 0.1.
The "Block mode" is a self contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25ter "command" state or "on-line command" state.
The "Text" and "PDU" modes are not in themselves V.25ter states but are simply sets of commands which will operate in either the V.25ter "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically returned to the V.25ter "command" state or "on-line command" state. Whilst in the V.25ter command state, the MS is available to handle incoming and outgoing calls such as Data or Facsimile.
In the "Block mode" and "PDU" mode a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where TS 23.040 or TS 23.041 defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the Text Mode the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in TS 23.038 and assume the coding scheme to be the GSM 7 bit default alphabet.
0.1 References p. 8
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] Void.
[2]
TS 23.038: "Alphabets and language-specific information".
[3]
TS 23.040: "Technical realization of the Short Message Service (SMS) ".
[4]
TS 23.041: "Technical realization of the Cell Broadcast Service (CBS)".
[5]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[6]
TS 24.011: "Short Message Service (SMS) support on mobile radio interface".
[7]
TS 24.012: "Cell Broadcast Service (CBS) support on the mobile radio interface".
→ to date, withdrawn by 3GPP
[8]
→ to date, withdrawn by 3GPP
TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[9]
TS 27.007: "AT command set for User Equipment (UE)".
[10]
TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface".
[11]
ITU-T Recommendation V.25ter: "Serial asynchronous automatic dialling and control".
[12]
ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)".
[13]
ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[14]
ITU-T Recommendation E.163: "Numbering plan for the international telephone service".
[15]
TR 21.905: "Vocabulary for 3GPP Specifications".
[16]
TS 31.102: "Characteristics of the USIM application".
0.2 Abbreviations p. 8
For the purposes of the present document, the abbreviations given in TR 21.905 and the following] apply.
EVPF
Enhanced Validity Period Format
1 Reference configuration p. 9
The User Equipment (UE) consists of the mobile equipment (ME) and the (U)SIM. Messages may be stored in either, but the present document does not distinguish between messages stored in the (U)SIM or in the ME. The management of message storage in the two parts of the UE is a matter for the UE implementation.
1.1 V.24 Interface Circuits p. 9
The operation of the ITU-T Recommendation V.24 blue book interface circuits for SMS is shown in Table 1.1.
| V.24 CIRCUIT | DESCRIPTION | TE to MT | MT to TE |
|---|---|---|---|
| CT102 | signal ground | x | x |
| CT103 | TXD | x | |
| CT104 | RXD | x | |
| CT105 | RTS | x | |
| CT106 | CTS | x | |
| CT107 | DSR | x | |
| CT108.2 | DTR | x | |
| CT109 | DCD | x | |
1.1.1 Circuit definitions for the SMS Block mode p. 9
CT103
All commands from the TE to the MT are transferred across this circuit. Inband flow control is not permitted during Block Mode.
CT104
All responses/indications from the MT to the TE are transferred across this circuit. Inband flow control is not permitted during Block Mode.
CT105
This circuit allows the TE to flow control the MT when in the Block Mode and at other times if hardware flow control is enabled.
CT106
This circuit allows the MT to flow control the TE when in the Block Mode and at other times if hardware flow control is enabled.
CT107
This circuit shall be set to the ON condition before entry into the Block Mode, and shall remain in the ON condition during Block Mode. If the TE detects that this circuit returns to the OFF condition during the block mode then the TE shall return CT108.2 to the OFF condition and exit the Block Mode.
CT108.2
This circuit shall be set in the ON condition before the AT+CESP command is sent from the TE to begin the Block Mode, and shall be maintained in the ON condition during the Block Mode. It shall be returned to the OFF condition after the command 'END SMS MODE' has been accepted and acknowledged by the MT. If the MT detects that this circuit returns to the OFF condition during the Block Mode then the MT shall exit the Block Mode.
CT109
This circuit shall be set to the ON condition before entry into the Block Mode and remain in the ON condition during the Block Mode. If the TE detects that this circuit returns to the OFF condition during the Block Mode then the TE shall return CT108.2 to the OFF condition and shall exit the Block Mode.
1.1.2 Circuit definitions for the SMS Text and PDU modes p. 10
Only circuits CT102, CT103 and CT104 are mandatory for the Text and PDU modes. The functionality and operation of other circuits shall be in accordance with V.25ter.
2 SMS Block Mode p. 10
2.1 Beginning and ending of SMS/CBS Block Mode p. 10
2.1.1 Beginning SMS/CBS Block Mode p. 10
2.1.2 Returning from SMS/CBS Block Mode To Default Mode p. 11
2.2 Protocol description p. 11
2.3 Requesting messages already held in the Mobile Termination p. 12
2.3.1 Requesting List Of Messages p. 13
2.3.2 Requesting Transfer Of Messages p. 13
2.3.2.1 Requesting Transfer Of A Specific Message p. 13
2.3.2.2 Requesting Transfer Of All Messages p. 13
2.3.3 Requesting Diversion Of Incoming Messages p. 14
2.3.3.1 Requesting SMS Messages p. 14
2.3.3.2 Requesting CBS Messages p. 14
2.3.3.3 Requesting indication of message arrival p. 14
2.3.4 Requesting Transfer Into Mobile Termination p. 15
2.3.5 Requesting Deletion Of Messages p. 15
2.4 Message functional definitions and contents p. 16
2.4.1 Commands Issued By The Terminal Equipment p. 16
2.4.1.1 List Request p. 17
2.4.1.2 Get Message p. 17
2.4.1.3 Get First Message p. 17
2.4.1.4 Get Next Message p. 17
2.4.1.5 Transfer Inc SMS p. 17
2.4.1.6 Indicate Inc SMS p. 17
2.4.1.7 Transfer Inc CBS p. 18
2.4.1.8 Insert SMS p. 18
2.4.1.9 Delete message p. 18
2.4.1.10 Unable to process p. 18
2.4.1.11 End SMS Mode p. 18
2.4.1.12 Acknowledge Message p. 19
2.4.2 Responses/Indications Issued By The MT p. 19
2.4.2.1 Message List p. 19
2.4.2.2 Message p. 19
2.4.2.3 Get Message Failure p. 20
2.4.2.4 Inc Message p. 20
2.4.2.5 Message Arrived p. 20
2.4.2.6 Insert SMS Complete p. 20
2.4.2.7 Insert SMS Failure p. 20
2.4.2.8 Delete Message Complete p. 21
2.4.2.9 Delete Message Failure p. 21
2.4.2.10 Unable To Process p. 21
2.4.2.11 End SMS Mode p. 21
2.4.2.12 Request Confirmed p. 21
2.5 General message format and information elements coding p. 21
2.5.1 Message Type p. 21
2.5.2 Other Information Elements p. 22
2.5.2.1 Short Message Reference p. 22
2.5.2.2 SMS Transfer Type p. 23
2.5.2.3 Indication Type p. 23
2.5.2.4 Insert Type p. 24
2.5.2.5 Short Message Index p. 25
2.5.2.6 Short Message Data p. 26
2.5.2.7 Cause p. 28
2.5.2.8 Index Count p. 29
2.5.2.9 CBS Transfer Type p. 29
2.5.2.10 Page Index p. 29
2.5.2.11 Last Short Message p. 30
2.5.2.12 Confirm Type p. 30
2.5.2.13 TP-Failure Cause p. 31
2.5.2.14 SM-Deliver-Ack p. 31
2.5.2.15 SM-Submit-Ack p. 32
3 Text Mode p. 32
3.1 Parameter Definitions p. 32
3.2 General Configuration Commands p. 35
3.2.1 Select Message Service +CSMS p. 35
3.2.2 Preferred Message Storage +CPMS p. 35
3.2.3 Message Format +CMGF p. 36
3.2.4 Enter SMS Block Mode Protocol +CESP p. 36
3.2.5 Message Service Failure Result Code +CMS ERROR p. 37
3.2.6 Informative Examples p. 37
3.3 Message Configuration Commands p. 38
3.3.1 Service Centre Address +CSCA p. 38
3.3.2 Set Text Mode Parameters +CSMP p. 38
3.3.3 Show Text Mode Parameters +CSDH p. 39
3.3.4 Select Cell Broadcast Message Types +CSCB p. 39
3.3.5 Save Settings +CSAS p. 40
3.3.6 Restore Settings +CRES p. 40
3.3.7 Informative Examples p. 41
3.4 Message Receiving and Reading Commands p. 41
3.4.1 New Message Indications to TE +CNMI p. 41
3.4.2 List Messages +CMGL p. 46
3.4.3 Read Message +CMGR p. 47
3.4.4 New Message Acknowledgement to ME/TA +CNMA p. 47
3.4.5 Informative Examples p. 48
3.5 Message Sending and Writing Commands p. 49
4 PDU Mode p. 53
4.0 General p. 53
4.1 List Messages +CMGL p. 54
4.2 Read Message +CMGR p. 54
4.3 Send Message +CMGS p. 54
4.4 Write Message to Memory +CMGW p. 55
4.5 Send Command +CMGC p. 56
4.6 New Message Acknowledgement to ME/TA +CNMA p. 56
4.7 Send Message from Storage +CMSS p. 57
A (Normative) Character Set Conversions for SMS Text Mode p. 58
B Example of processing a data block p. 61
B.1 Example state diagrams for the block receiver p. 61
B.2 Example of coding and decoding a data block p. 61
$ Change History p. 68
