ETSI TS 127 005 V17.0.0 (2022-04)
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) (3GPP TS 27.005 version 17.0.0 Release 17)
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) (3GPP TS 27.005 version 17.0.0 Release 17)
RTS/TSGC-0127005vh00
General Information
Buy Standard
Standards Content (Sample)
ETSI TS 127 005 V17.0.0 (2022-04)
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Use of Data Terminal Equipment - Data Circuit terminating
Equipment (DTE - DCE) interface for Short Message Service
(SMS) and Cell Broadcast Service (CBS)
(3GPP TS 27.005 version 17.0.0 Release 17)
---------------------- Page: 1 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 1 ETSI TS 127 005 V17.0.0 (2022-04)
Reference
RTS/TSGC-0127005vh00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2022.
All rights reserved.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 2 ETSI TS 127 005 V17.0.0 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 3 ETSI TS 127 005 V17.0.0 (2022-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
0 Scope . 7
0.1 References . 8
0.2 Abbreviations . 8
1 Reference configuration . 9
1.1 V.24 Interface Circuits . 9
1.1.1 Circuit definitions for the SMS Block mode . 9
1.1.2 Circuit definitions for the SMS Text and PDU modes . 10
2 SMS Block Mode . 10
2.1 Beginning and ending of SMS/CBS Block Mode . 10
2.1.1 Beginning SMS/CBS Block Mode . 10
2.1.2 Returning from SMS/CBS Block Mode To Default Mode . 11
2.2 Protocol description . 11
2.3 Requesting messages already held in the Mobile Termination . 12
2.3.1 Requesting List Of Messages. 13
2.3.2 Requesting Transfer Of Messages . 13
2.3.2.1 Requesting Transfer Of A Specific Message . 13
2.3.2.2 Requesting Transfer Of All Messages. 13
2.3.3 Requesting Diversion Of Incoming Messages . 14
2.3.3.1 Requesting SMS Messages . 14
2.3.3.2 Requesting CBS Messages . 14
2.3.3.3 Requesting indication of message arrival . 14
2.3.4 Requesting Transfer Into Mobile Termination . 15
2.3.5 Requesting Deletion Of Messages . 15
2.4 Message functional definitions and contents . 16
2.4.1 Commands Issued By The Terminal Equipment . 16
2.4.1.1 List Request. 17
2.4.1.2 Get Message . 17
2.4.1.3 Get First Message . 17
2.4.1.4 Get Next Message . 17
2.4.1.5 Transfer Inc SMS . 17
2.4.1.6 Indicate Inc SMS . 17
2.4.1.7 Transfer Inc CBS . 18
2.4.1.8 Insert SMS. 18
2.4.1.9 Delete message . 18
2.4.1.10 Unable to process . 18
2.4.1.11 End SMS Mode . 18
2.4.1.12 Acknowledge Message . 19
2.4.2 Responses/Indications Issued By The MT . 19
2.4.2.1 Message List . 19
2.4.2.2 Message . 19
2.4.2.3 Get Message Failure . 20
2.4.2.4 Inc Message. 20
2.4.2.5 Message Arrived . 20
2.4.2.6 Insert SMS Complete . 20
2.4.2.7 Insert SMS Failure . 20
2.4.2.8 Delete Message Complete . 21
2.4.2.9 Delete Message Failure . 21
2.4.2.10 Unable To Process . 21
2.4.2.11 End SMS Mode . 21
2.4.2.12 Request Confirmed. 21
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 4 ETSI TS 127 005 V17.0.0 (2022-04)
2.5 General message format and information elements coding . 21
2.5.1 Message Type . 21
2.5.2 Other Information Elements . 22
2.5.2.1 Short Message Reference . 22
2.5.2.2 SMS Transfer Type . 23
2.5.2.3 Indication Type . 23
2.5.2.4 Insert Type . 24
2.5.2.5 Short Message Index . 25
2.5.2.6 Short Message Data. 26
2.5.2.7 Cause . 28
2.5.2.8 Index Count . 29
2.5.2.9 CBS Transfer Type . 29
2.5.2.10 Page Index . 29
2.5.2.11 Last Short Message . 30
2.5.2.12 Confirm Type . 30
2.5.2.13 TP-Failure Cause . 31
2.5.2.14 SM-Deliver-Ack . 31
2.5.2.15 SM-Submit-Ack . 32
3 Text Mode . 32
3.1 Parameter Definitions . 32
3.2 General Configuration Commands . 35
3.2.1 Select Message Service +CSMS . 35
3.2.2 Preferred Message Storage +CPMS . 35
3.2.3 Message Format +CMGF . 36
3.2.4 Enter SMS Block Mode Protocol +CESP . 36
3.2.5 Message Service Failure Result Code +CMS ERROR . 37
3.2.6 Informative Examples . 37
3.3 Message Configuration Commands . 38
3.3.1 Service Centre Address +CSCA . 38
3.3.2 Set Text Mode Parameters +CSMP . 38
3.3.3 Show Text Mode Parameters +CSDH . 39
3.3.4 Select Cell Broadcast Message Types +CSCB . 39
3.3.5 Save Settings +CSAS . 40
3.3.6 Restore Settings +CRES . 40
3.3.7 Informative Examples . 41
3.4 Message Receiving and Reading Commands . 41
3.4.1 New Message Indications to TE +CNMI . 41
3.4.2 List Messages +CMGL . 46
3.4.3 Read Message +CMGR . 47
3.4.4 New Message Acknowledgement to ME/TA +CNMA . 47
3.4.5 Informative Examples . 48
3.5 Message Sending and Writing Commands . 49
3.5.1 Send Message +CMGS . 49
3.5.2 Send Message from Storage +CMSS . 50
3.5.3 Write Message to Memory +CMGW . 50
3.5.4 Delete Message +CMGD . 51
3.5.5 Send Command +CMGC . 52
3.5.6 More Messages to Send +CMMS . 52
3.5.7 Informative Examples . 53
4 PDU Mode . 53
4.0 General . 53
4.1 List Messages +CMGL . 54
4.2 Read Message +CMGR . 54
4.3 Send Message +CMGS . 54
4.4 Write Message to Memory +CMGW . 55
4.5 Send Command +CMGC . 56
4.6 New Message Acknowledgement to ME/TA +CNMA . 56
4.7 Send Message from Storage +CMSS . 57
Annex A (normative): Character Set Conversions for SMS Text Mode . 58
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 5 ETSI TS 127 005 V17.0.0 (2022-04)
Annex B (informative): Example of processing a data block . 61
B.1 Example state diagrams for the block receiver. 61
B.2 Example of coding and decoding a data block . 61
Annex C (informative): Change History . 68
History . 69
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 6 ETSI TS 127 005 V17.0.0 (2022-04)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 Indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the specification;
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 7 ETSI TS 127 005 V17.0.0 (2022-04)
0 Scope
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.
V.25ter
"command" state
and "on-line command" state
SMS SMS
Text PDU
Mode Mode
SMS Block Mode
Figure 0.1: Block, Text and PDU modes
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
3GPP TS 23.040 [3] or 3GPP TS 23.041 [4] 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 3GPP TS 23.038 [2] and
assume the coding scheme to be the GSM 7 bit default alphabet.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 27.005 version 17.0.0 Release 17 8 ETSI TS 127 005 V17.0.0 (2022-04)
0.1 References
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 refer
...


Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.