|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Alphabets and language-specific information
(3GPP TS 23.038 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 1 ETSI TS 123 038 V15.0.0 (2018-09)
Reference
RTS/TSGC-0123038vF00
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 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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
If you find errors in the present document, please send your comment to one of the following services:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 2 ETSI TS 123 038 V15.0.0 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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 23.038 version 15.0.0 Release 15 3 ETSI TS 123 038 V15.0.0 (2018-09)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Abbreviations and definitions . 7
4 SMS Data Coding Scheme . 8
5 CBS Data Coding Scheme . 12
6 Individual parameters . 15
6.1 General principles. 15
6.1.1 General notes . 15
6.1.2 Character packing . 15
6.1.2.1 SMS Packing . 15
6.1.2.1.1 Packing of 7-bit characters . 15
6.1.2.2 CBS Packing . 16
6.1.2.2.1 Packing of 7-bit characters . 16
6.1.2.3 USSD packing . 17
6.1.2.3.1 Packing of 7 bit characters . 17
6.2 Character sets and coding . 20
6.2.1 GSM 7 bit Default Alphabet . 20
6.2.1.1 GSM 7 bit default alphabet extension table . 21
6.2.1.2 National Language Identifier . 23
6.2.1.2.1 Introduction . 23
6.2.1.2.2 Single shift mechanism . 23
6.2.1.2.3 Locking shift mechanism. 23
6.2.1.2.4 National Language Identifier . 23
6.2.1.2.5 Processing of national language characters . 24
6.2.2 8 bit data . 25
6.2.3 UCS2 . 25
Annex A (normative): National Language Tables . 26
A.1 Introduction . 26
A.2 National Language Single Shift Tables . 27
A.2.1 Turkish National Language Single Shift Table . 27
A.2.2 Spanish National Language Single Shift Table . 28
A.2.3 Portuguese National Language Single Shift Table . 29
A.2.4 Bengali National Language Single Shift Table . 29
A.2.5 Gujarati National Language Single Shift Table. 31
A.2.6 Hindi National Language Single Shift Table . 32
A.2.7 Kannada National Language Single Shift Table . 33
A.2.8 Malayalam National Language Single Shift Table . 34
A.2.9 Oriya National Language Single Shift Table . 35
A.2.10 Punjabi National Language Single Shift Table . 36
A.2.11 Tamil National Language Single Shift Table . 37
A.2.12 Telugu National Language Single Shift Table . 38
A.2.13 Urdu National Language Single Shift Table . 39
A.3 National Language Locking Shift Tables . 40
A.3.1 Turkish National Language Locking Shift Table . 40
A.3.2 Void . 41
A.3.3 Portuguese National Language Locking Shift Table . 41
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 4 ETSI TS 123 038 V15.0.0 (2018-09)
A.3.4 Bengali National Language Locking Shift Table . 41
A.3.5 Gujarati National Language Locking Shift Table . 43
A.3.6 Hindi National Language Locking Shift Table . 44
A.3.7 Kannada National Language Locking Shift Table . 45
A.3.8 Malayalam National Language Locking Shift Table . 46
A.3.9 Oriya National Language Locking Shift Table . 47
A.3.10 Punjabi National Language Locking Shift Table . 48
A.3.11 Tamil National Language Locking Shift Table . 49
A.3.12 Telugu National Language Locking Shift Table . 50
A.3.13 Urdu National Language Locking Shift Table . 51
Annex B (informative): Guidelines for creating language tables . 52
B.1 Introduction . 52
B.2 Template for Single Shift Language Tables . 52
B.3 Template for Locking Shift Language Tables . 54
Annex C (Informative): Example for locking shift and single shift mechanisms . 55
C.1 Introduction . 55
C.2 Example of single shift . 55
C.3 Example of locking shift . 55
Annex D (informative): Document change history . 57
History . 58
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 5 ETSI TS 123 038 V15.0.0 (2018-09)
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: 6 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 6 ETSI TS 123 038 V15.0.0 (2018-09)
1 Scope
The present document defines the character sets, languages and message handling requirements for SMS, CBS and
USSD and may additionally be used for Man Machine Interface (MMI) (3GPP TS 22.030 [2]).
The specification for the Data Circuit terminating Equipment/Data Terminal Equipment (DCE/DTE) interface
(3GPP TS 27.005 [8]) will also use the codes specified herein for the transfer of SMS data to an external terminal.
2 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 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] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".
[3] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD) - Stage 2".
[4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) ".
[5] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[6] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[7] Void.
[8] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE -
DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
[10] ISO/IEC 10646: "Information technology; Universal Multiple-Octet Coded Character Set (UCS)".
[11] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD); Stage 3".
[12] ISO 639: "Code for the representation of names of languages".
[13] 3GPP TS 23.042: "Compression algorithm for text messaging services".
[14] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[15] "Wireless Datagram Protocol Specification", Wireless Application Protocol Forum Ltd.
[16] ISO 1073-1 and ISO 1073-2 Alphanumeric character sets for optical recognition – Parts 1 and 2:
Character sets OCR-A and OCR-B, respectively - Shapes and dimensions of the printed image.
[17] 3GPP TS 31.102: "Characteristics of the USIM application"
[18] 3GPP TS 51.011 Release 4 (version 4.x.x): “Specification of the Subscriber Identity Module -
Mobile Equipment (SIM - ME) interface”
[19] 3GPP TS 24.294: "IMS Centralized Services (ICS) Protocol via I1 Interface".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 7 ETSI TS 123 038 V15.0.0 (2018-09)
3 Abbreviations and definitions
For the purposes of the present document, the following terms and definitions apply:
National Language Identifier: A code representing a specific language and thereby selecting a specific National
Language Table.
National Language Locking Shift Table: A national language table which replaces the GSM 7 bit default alphabet
table in the case where the locking shift mechanism as defined in subclause 6.2.1.2.3 is used.
National Language Single Shift Table: A national language table which replaces the GSM 7 bit default alphabet
extension table in the case where the single shift mechanism as defined in subclause 6.2.1.2.2 is used.
National Language Table: A table containing the characters of a specific national language.
For the purposes of the present document, the abbreviations used in the present document are listed in 3GPP TR 21.905
[14].
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 8 ETSI TS 123 038 V15.0.0 (2018-09)
4 SMS Data Coding Scheme
The TP-Data-Coding-Scheme field, defined in 3GPP TS 23.040 [4], indicates the data coding scheme of the TP-UD
field, and may indicate a message class. Any reserved codings shall be assumed to be the GSM 7 bit default alphabet
(the same as codepoint 00000000) by a receiving entity. The octet is used according to a coding group which is
indicated in bits 7.4. The octet is then coded as follows:
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 9 ETSI TS 123 038 V15.0.0 (2018-09)
Coding Group Bits Use of bits 3.0
7.4
00xx General Data Coding indication
Bits 5.0 indicate the following:
Bit 5, if set to 0, indicates the text is uncompressed
Bit 5, if set to 1, indicates the text is compressed using the compression algorithm defined
in 3GPP TS 23.042 [13]
Bit 4, if set to 0, indicates that bits 1 to 0 are reserved and have no message class
meaning
Bit 4, if set to 1, indicates that bits 1 to 0 have a message class meaning::
Bit 1 Bit 0 Message Class
0 0 Class 0
0 1 Class 1 Default meaning: ME-specific.
1 0 Class 2 (U)SIM specific message
1 1 Class 3 Default meaning: TE specific (see 3GPP TS 27.005 [8])
Bits 3 and 2 indicate the character set being used, as follows :
Bit 3 Bit2 Character set:
0 0 GSM 7 bit default alphabet
0 1 8 bit data
1 0 UCS2 (16bit) [10]
1 1 Reserved
NOTE: The special case of bits 7.0 being 0000 0000 indicates the GSM 7 bit default
alphabet with no message class
01xx Message Marked for Automatic Deletion Group
This group can be used by the SM originator to mark the message ( stored in the ME or
(U)SIM ) for deletion after reading irrespective of the message class.
The way the ME will process this deletion should be manufacturer specific but shall be
done without the intervention of the End User or the targeted application. The mobile
manufacturer may optionally provide a means for the user to prevent this automatic
deletion.
Bit 5.0 are coded exactly the same as Group 00xx
1000.1011 Reserved coding groups
1100 Message Waiting Indication Group: Discard Message
The specification for this group is exactly the same as for Group 1101, except that:
- after presenting an indication and storing the status, the ME may discard the contents
of the message.
The ME shall be able to receive, process and acknowledge messages in this group,
irrespective of memory availability for other types of short message.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 10 ETSI TS 123 038 V15.0.0 (2018-09)
Coding Group Bits Use of bits 3.0
7.4
1101 Message Waiting Indication Group: Store Message
This Group defines an indication to be provided to the user about the status of types of
message waiting on systems connected to the GSM/UMTS PLMN. The ME should present
this indication as an icon on the screen, or other MMI indication. The ME shall update the
contents of the Message Waiting Indication Status on the SIM (see 3GPP TS 51.011 [18])
or USIM (see 3GPP TS 31.102 [17]) when present or otherwise should store the status in
the ME. In case there are multiple records of EF this information shall be stored within
MWIS
the first record. The contents of the Message Waiting Indication Status should control the
ME indicator. For each indication supported, the mobile may provide storage for the
Origination Address. The ME may take note of the Origination Address for messages in
this group and group 1100.
Text included in the user data is coded in the GSM 7 bit default alphabet.
Where a message is received with bits 7.4 set to 1101, the mobile shall store the text of
the SMS message in addition to setting the indication. The indication setting should take
place irrespective of memory availability to store the short message.
Bits 3 indicates Indication Sense:
Bit 3
0 Set Indication Inactive
1 Set Indication Active
Bit 2 is reserved, and set to 0
Bit 1 Bit 0 Indication Type:
0 0 Voicemail Message Waiting
0 1 Fax Message Waiting
1 0 Electronic Mail Message Waiting
1 1 Other Message Waiting*
* Mobile manufacturers may implement the "Other Message Waiting" indication as an
additional indication without specifying the meaning.
1110 Message Waiting Indication Group: Store Message
The coding of bits 3.0 and functionality of this feature are the same as for the Message
Waiting Indication Group above, (bits 7.4 set to 1101) with the exception that the text
included in the user data is coded in the uncompressed UCS2 character set.
1111 Data coding/message class
Bit 3 is reserved, set to 0.
Bit 2 Message coding:
0 GSM 7 bit default alphabet
1 8-bit data
Bit 1 Bit 0 Message Class:
0 0 Class 0
0 1 Class 1 default meaning: ME-specific.
1 0 Class 2 (U)SIM-specific message.
1 1 Class 3 default meaning: TE specific (see 3GPP TS 27.005 [8])
GSM 7 bit default alphabet indicates that the TP-UD is coded from the GSM 7 bit default alphabet given in
clause 6.2.1. When this character set is used, the characters of the message are packed in octets as shown in
clause 6.1.2.1.1, and the message can consist of up to 160 characters. The GSM 7 bit default alphabet shall be supported
by all MSs and SCs offering the service. If the GSM 7 bit default alphabet extension mechanism is used then the
number of displayable characters will reduce by one for every instance where the GSM 7 bit default alphabet extension
table is used. 8-bit data indicates that the TP-UD has user-defined coding, and the message can consist of up to
140 octets.
UCS2 character set indicates that the TP-UD has a UCS2 [10] coded message, and the message can consist of up to
140 octets, i.e. up to 70 UCS2 characters. The General notes specified in clause 6.1.1 override any contrary
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 23.038 version 15.0.0 Release 15 11 ETSI TS 123 038 V15.0.0 (2018-09)
specification in UCS2, so for example even in UCS2 a character will cause the MS to return to the beginning of
the current line and overwrite any existing text with the characters which follow the .
When a message is compressed, the TP-UD consists of the GSM 7 bit default alphabet or UCS2 character set
compressed message, and the compressed message itself can consist of up to 140 octets in total.
When a mobile terminated message is class 0 and the MS has the capability of displaying short messages, the MS shall
display the message immediately and send an acknowledgement to the SC when the message has successfully reached
the MS irrespective of whether there is memory available in the (U)SIM or ME. The message shall not be automatically
stored in the (U)SIM or ME.
The ME may make provision through MMI for the user to selectively prevent the message from being displayed
immediately.
If the ME is incapable of displaying short messages or if the immediate display of the message has been disabled
through MMI then the ME shall treat the short message as though there was no message class, i.e. it will ignore bits 0
and 1 in the TP-DCS and normal rules for memory capacity exceeded shall apply.
When a mobile terminated message is Class 1, the MS shall send an acknowledgement to the SC when the message has
successfully reached the MS and can be stored. The MS shall normally store the message in the ME by default, if that is
possible, but otherwise the message may be stored elsewhere, e.g. in the (U)SIM. The user may be able to override the
default meaning and select their own routing.
When a mobile terminated message is Class 2 ((U)SIM-specific), an MS shall ensure that the message has been
transferred to the SMS data field in the (U)SIM before sending an acknowledgement to the SC. The MS shall return a
"protocol error, unspecified" error message (see 3GPP TS 24.011 [6]) if the short message cannot be stored in the
(U)SIM and there is other short message storage available at the MS. If all the short message storage at the MS is
already in use, the MS shall return "memory capacity exceeded". This behaviour applies in all cases except for an MS
supporting (U)SIM Application Toolkit when the Protocol Identifier (TP-PID) of the mobile terminated message is set
to "(U)SIM Data download" (see 3GPP TS 23.040 [4]).
When a mobile terminated message is Class 3, the MS shall send an acknowledgement to the SC when the message has
successfully reached the MS and can be stored, irrespectively of whether the MS supports an SMS interface to a TE,
and without waiting for the message to be transferred to the TE. Thus the acknowledgement to the SC of a TE-specific
message does not imply that the message has reached the TE. Class 3 messages shall normally be transferred to the TE
when the TE requests "TE-specific" messages (see 3GPP TS 27.005 [8]). The user may be able to override the default
meaning and select their own routing.
The message clas
...