|
TECHNICAL SPECIFICATION
Integrated Circuit Cards (ICC);
Administrative commands for
telecommunications applications
(Release 14)
---------------------- Page: 1 ----------------------
Release 14 2 ETSI TS 102 222 V14.0.0 (2018-07)
Reference
RTS/SCP-Tv140000
Keywords
GSM, smart card, 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 ----------------------
Release 14 3 ETSI TS 102 222 V14.0.0 (2018-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Mapping principles . 8
5 Security architecture . 9
6 Description of the functions and commands . 9
6.0 Overview . 9
6.1 Coding of the commands . 9
6.2 TLV objects . 9
6.3 CREATE FILE . 10
6.3.1 Definition and scope . 10
6.3.2 Command message . 10
6.3.2.0 Command coding . 10
6.3.2.1 Parameters P1 and P2 . 10
6.3.2.2 Data field sent in the command message . 11
6.3.2.2.1 Creating a DF/ADF . 11
6.3.2.2.2 Creating an EF . 13
6.3.3 Response message . 15
6.3.3.1 Data field returned in the response message . 15
6.3.3.2 Status conditions returned in the response message . 16
6.4 DELETE FILE . 16
6.4.1 Definition and scope . 16
6.4.2 Command message . 17
6.4.2.0 Command coding . 17
6.4.2.1 Parameters P1 and P2 . 17
6.4.2.2 Data field sent in the command message . 17
6.4.3 Response message . 17
6.4.3.1 Data field returned in the response message . 17
6.4.3.2 Status conditions returned in the response message . 18
6.5 DEACTIVATE FILE . 18
6.6 ACTIVATE FILE. 18
6.7 TERMINATE DF . 18
6.7.1 Definition and scope . 18
6.7.2 Command message . 19
6.7.2.0 Command coding . 19
6.7.2.1 Parameters P1 and P2 . 19
6.7.2.2 Data field sent in the command message . 19
6.7.3 Response message . 19
6.7.3.1 Data field returned in the response message . 19
6.7.3.2 Status conditions returned in the response message . 19
6.8 TERMINATE EF . 20
6.8.1 Definition and scope . 20
6.8.2 Command message . 20
6.8.2.0 Command coding . 20
6.8.2.1 Parameters P1 and P2 . 20
ETSI
---------------------- Page: 3 ----------------------
Release 14 4 ETSI TS 102 222 V14.0.0 (2018-07)
6.8.2.2 Data field sent in the command message . 20
6.8.3 Response message . 20
6.8.3.1 Data field returned in the response message . 20
6.8.3.2 Status conditions returned in the response message . 21
6.9 TERMINATE CARD USAGE. 21
6.9.1 Definition and scope . 21
6.9.2 Command message . 21
6.9.2.0 Command coding . 21
6.9.2.1 Parameters P1 and P2 . 22
6.9.2.2 Data field sent in the command message . 22
6.9.3 Response message . 22
6.9.3.1 Data field returned in the response message . 22
6.9.3.2 Status conditions returned in the response message . 22
6.10 RESIZE FILE . 22
6.10.1 Definition and scope . 22
6.10.2 Command message . 24
6.10.2.0 Command coding . 24
6.10.2.1 Data field sent in the command message . 24
6.10.3 Response message . 26
6.10.3.1 Data field returned in the response message . 26
6.10.3.2 Status conditions returned in the response message . 26
7 Administrative files . 27
7.1 EF (SetUpMenu Elements) . 27
SUME
7.2 EF (Remote Management Actions) . 27
RMA
Annex A (informative): Change history . 29
History . 31
ETSI
---------------------- Page: 4 ----------------------
Release 14 5 ETSI TS 102 222 V14.0.0 (2018-07)
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 Technical Committee Smart Card Platform (SCP).
The contents of the present document are subject to continuing work within TC SCP and may change following formal
TC SCP approval. If TC SCP modifies the contents of the present document, it will then be republished by ETSI with
an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
0 early working draft;
1 presented to TC SCP for information;
2 presented to TC SCP for approval;
3 or greater indicates TC SCP 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 document.
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: 5 ----------------------
Release 14 6 ETSI TS 102 222 V14.0.0 (2018-07)
1 Scope
The present document defines functions and syntax of a set of administrative commands for a telecommunication card.
The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 [i.2]
series where corresponding commands in ISO/IEC are available. The commands described in the present document are
using parts of the functionality of the commands described in the ISO/IEC 7816-3 [i.1].
The present document does not cover the internal implementation within the UICC and/or the external equipment.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
• In the case of a reference to a TC SCP document, a non specific reference implicitly refers to the latest version
of that document in the same Release as the present document.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] Void.
[2] ISO/IEC 7816-4: "Identification cards -- Integrated circuit cards -- Part 4: Organization, security
and commands for interchange".
[3] Void.
[4] Void.
[5] ETSI TS 102 221: "Smart Cards; UICC-Terminal interface; Physical and logical characteristics".
[6] Void.
[7] ETSI TS 101 220: "Smart Cards; ETSI numbering system for telecommunication application
providers".
[8] ETSI TS 102 223: "Smart Cards; Card Application Toolkit (CAT)".
[9] Void.
ETSI
---------------------- Page: 6 ----------------------
Release 14 7 ETSI TS 102 222 V14.0.0 (2018-07)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
• In the case of a reference to a TC SCP document, a non specific reference implicitly refers to the latest version
of that document in the same Release as the present document.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO/IEC 7816-3: "Identification cards -- Integrated circuit cards -- Part 3: Cards with contacts --
Electrical interface and transmission protocols".
[i.2] ISO/IEC 7816 (all parts): "Identification cards -- Integrated circuit cards".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Access Conditions (AC): set of security attributes associated to a file
ADMinistrative (ADM): access condition to an EF which is under the control of the authority which creates this file
administrative command: command modifying the internal properties of the file system of an UICC
current directory: latest directory (MF, DF or ADF) selected in the UICC
current EF: latest Elementary File (EF) selected in the UICC
current file: current EF, if an EF is selected, else the current directory
Dedicated File (DF): file containing Access Conditions (AC) and allocable memory
NOTE: It may be the parent of Elementary Files (EF) and/or Dedicated Files (DF).
directory: general name for MF, DF or ADF
Elementary File (EF): file containing Access Conditions (AC) and data
NOTE: It cannot be the parent of another file.
File IDentifier (ID): each file (MF, DF, ADF or EF) has a file identifier consisting of 2 bytes
Lc: length of command data sent by the application layer
Le: maximum length of data expected by the application layer
LL: length of data
Master File (MF): mandatory unique DF representing the root of the file structure and containing Access Conditions
(AC) and allocable memory
NOTE: It may be the parent of elementary files and/or dedicated files.
record: string of bytes handled as a whole by the UICC and terminal and referenced by a record number or a record
pointer
ETSI
---------------------- Page: 7 ----------------------
Release 14 8 ETSI TS 102 222 V14.0.0 (2018-07)
record number: sequential and unique number within an EF, which identifies a record within an EF
NOTE: It is managed by the UICC.
record pointer: pointer, which addresses one record in an EF
telecommunication card: UICC mainly used for telecommunication applications
3.2 Symbols
For the purposes of the present document, the following symbols apply:
' Single quotation is used to indicate hexadecimal notation.
'0' to '9' and 'A' to 'F' The sixteen hexadecimal digits
b8 . b1 Bits of one byte. b8 is the MSB, b1 the LSB
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AC Access Condition
ADF Application Dedicated File
AID Application IDentifier
AM Access Mode
AM_DO Access Mode - Data Object
APDU Application Protocol Data Unit
ATR Answer To Reset
BER Basic Encoding Rule
CLA CLAss
DF Dedicated File (abbreviation formerly used for Data Field)
DO Data Object
EF Elementary File
FCP File Control Parameters
FID File IDentifier
ICC Integrated Circuit Card
ID IDentifier
IEC International Electrotechnical Commission
INS INStruction
ISO International Organization for Standardization
LCSI Life Cycle Status Information
LSB Least Significant Bit
M Mandatory
MF Master File
MSB Most Significant Bit
O Optional
PIN Personal Identification Number
RFU Reserved for Future Use
SFI Short (elementary) File Identifier
SIM Subscriber Identity Module
SM Secure Messaging
SW1/SW2 Status Word 1/Status Word 2
TLV Tag Length Value
4 Mapping principles
UICC Cards compliant to the present document shall follow the rules of ETSI TS 102 221 [5] in clauses 7 and 10.
ETSI
---------------------- Page: 8 ----------------------
Release 14 9 ETSI TS 102 222 V14.0.0 (2018-07)
5 Security architecture
The general coding of security attributes assigned to files by use of the CREATE FILE command is as described in
ETSI TS 102 221 [5].
6 Description of the functions and commands
6.0 Overview
A UICC supporting the command set based on the present document shall support the command as defined in the
present document. However, it is up to the UICC to provide more functionality than described in the present document.
This clause gives a functional description of the commands, their respective responses, associated status conditions,
error codes and their coding.
6.1 Coding of the commands
Table 1: Coding of the commands
Command CLA INS
CREATE FILE '0X' or '4X' 'E0'
DELETE FILE '0X' or '4X' 'E4'
DEACTIVATE FILE '0X' or '4X' '04'
ACTIVATE FILE '0X' or '4X' '44'
TERMINATE DF '0X' or '4X' 'E6'
TERMINATE EF '0X' or '4X' 'E8'
TERMINATE CARD USAGE '0X' or '4X' 'FE'
RESIZE FILE '8X' or 'CX' 'D4'
The coding of the value X for the CLA-bytes in table 1 shall be according to ETSI TS 102 221 [5].
All bytes specified as RFU shall be set to '00' and all bits specified as RFU shall be set to 0.
These are the basic commands under the assumption of no Secure Messaging (SM). If SM is used:
• Secure Messaging indicators in CLA byte shall be set accordingly; and
• the Lc and data field shall be adopted.
Other commands may be needed in order to execute the commands listed above (e.g. EXTERNAL AUTHENTICATE).
If such commands are necessary, they shall be coded according to ISO/IEC 7816-4 [2].
6.2 TLV objects
All TLVs described in the present document are BER-TLVs as described in ETSI TS 101 220 [7] and shall be
supported by the UICC.
The sequence of mandatory TLV objects within the data field of any command specified in the present document shall
be as in the description of the command.
According to the requirements of the application, the mandatory list of TLVs may be appended by one of the Tags '85'
(Proprietary Information Primitive, see ISO/IEC 7816-4 [2]) or 'A5' (Proprietary Information Constructed, see
ISO/IEC 7816-4 [2]).
Tag '85' or Tag 'A5' may be appended by other TLVs described in the present document or by any ISO/IEC or
application dependent optional TLV object if necessary for a particular application.
ETSI
---------------------- Page: 9 ----------------------
Release 14 10 ETSI TS 102 222 V14.0.0 (2018-07)
6.3 CREATE FILE
6.3.1 Definition and scope
This function allows the creation of a new file under the current directory. The access condition for the CREATE FILE
function of the current directory shall be fulfilled.
When creating an EF with linear fixed or cyclic structure the UICC shall directly create as many records as allowed by
the requested file size.
After the creation of a DF, the current directory shall be on the newly created file. In case of an EF creation, the current
EF shall be on the newly created file and the current directory is unchanged. After creation of an EF with linear fixed
structure, the record pointer is not defined. After creation of an EF with cyclic structure, the current record pointer is on
the last created record. After creation of an EF with BER TLV structure, the current tag pointer is undefined.
The memory space allocated shall be reserved for the created file.
If an ADF is created, some instance has to take care of the administration of the application, e.g. updating the EF
DIR
with the application ID. The CREATE FILE command does not take care of this administration by its own. The DF
Name tag shall only provide in the command, if an ADF is created.
The CREATE FILE command shall initialize newly created EFs with 'FF'. The content of the whole newly created EF
shall consist of bytes of this value. If, for another application, other default values are required, this default behaviour
can be overwritten by specifying an appropriate TLV in the application dependent data TLV (tag '85' or 'A5') of the
CREATE FILE command.
6.3.2 Command message
6.3.2.0 Command coding
The CREATE FILE command message is coded according to table 2.
Table 2: CREATE FILE command message
Code Value
CLA See table 1
INS See table 1
P1 '00'
P2 '00'
Lc Length of the subsequent data field
Data field Data sent to the UICC
Le Not present
6.3.2.1 Parameters P1 and P2
P1 and P2 are set to '00' indicating: FileID and file parameters encoded in data.
ETSI
---------------------- Page: 10 ----------------------
Release 14 11 ETSI TS 102 222 V14.0.0 (2018-07)
6.3.2.2 Data field sent in the command message
6.3.2.2.1 Creating a DF/ADF
Table 3: Coding of the data field of the CREATE FILE command (in case of creation of a DF/ADF)
Value M/O/C Description Length
'62' M Tag: FCP Template 1 byte
LL Length of FCP Template (next byte to the end) 1 or 2 bytes
'82' M Tag: File Descriptor 1 byte
File Descriptor byte followed by Data Coding Byte
'02' Length of File Descriptor 1 byte
File Descriptor Byte indicating DF or ADF 1 byte
'21' Data Coding Byte 1 byte
'83' M Tag: File ID 1 byte
'02' Length of File ID 1 byte
File ID 2 bytes
'84' C (see Tag: DF Name (AID) 1 byte
note)
LL Length of DF Name (AID) 1 byte
DF Name (AID) 1 byte to 16 bytes
'8A' M Life Cycle Status Information (LCSI) 1 byte
'01' Length of the LCSI 1 byte
Life Cycle Status Information 1 byte
'8C' 'AB' M Tag: Security Attributes: one of the following: 1 byte
'8B' Compact
Expanded
Referenced
LL Length of Security Attributes 1 byte
Data for the Security Attributes W bytes
'81' M Tag: Total File Size 1 byte
LL, LL ≥ 2 Length of Total File S
...