1、 ETSI TS 102 222 V7.1.0 (2007-02)Technical Specification Integrated Circuit Cards (ICC);Administrative commandsfor telecommunications applications(Release 7)ETSI ETSI TS 102 222 V7.1.0 (2007-02) 2 Release 7 Reference RTS/SCP-T00368r1 Keywords GSM, smart card, UMTS ETSI 650 Route des Lucioles F-06921
2、 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.o
3、rg The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ET
4、SI printers of the 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 http:/portal.ets
5、i.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoi
6、ng restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by E
7、TSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 222 V7.1.0 (2007-02) 3 Release 7 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions, symbols an
8、d abbreviations .7 3.1 Definitions7 3.2 Symbols7 3.3 Abbreviations .8 4 Mapping principles.8 5 Security architecture.8 6 Description of the functions and commands 9 6.1 Coding of the commands9 6.2 TLV objects9 6.3 CREATE FILE.9 6.3.1 Definition and scope .9 6.3.2 Command message .10 6.3.2.1 Paramete
9、rs P1 and P210 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 message16 6.4 DELETE FILE .16 6.4.1 Defini
10、tion and scope .16 6.4.2 Command message .17 6.4.2.1 Parameters P1 and P217 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 message18 6.5 DEACTIVATE FILE .18 6.6 ACT
11、IVATE FILE.18 6.7 TERMINATE DF.18 6.7.1 Definition and scope .18 6.7.2 Command message .19 6.7.2.1 Parameters P1 and P219 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 resp
12、onse message19 6.8 TERMINATE EF .20 6.8.1 Definition and scope .20 6.8.2 Command message .20 6.8.2.1 Parameters P1 and P220 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 re
13、sponse message21 6.9 TERMINATE CARD USAGE.21 6.9.1 Definition and scope .21 6.9.2 Command message .21 6.9.2.1 Parameters P1 and P221 ETSI ETSI TS 102 222 V7.1.0 (2007-02) 4 Release 7 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 respon
14、se message .22 6.9.3.2 Status conditions returned in the response message22 6.10 RESIZE FILE.22 6.10.1 Definition and scope .22 6.10.2 Command message .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 S
15、tatus conditions returned in the response message26 7 Administrative files27 7.1 EFSUME(SetUpMenu Elements) .27 7.2 EFRMA(Remote Management Actions) .28 Annex A (informative): Change history .29 History 31 ETSI ETSI TS 102 222 V7.1.0 (2007-02) 5 Release 7 Intellectual Property Rights IPRs essential
16、or potentially essential to the present document 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 Es
17、sential, 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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETS
18、I. 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. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Sm
19、art 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 i
20、ncrease 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 s
21、ubstance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 102 222 V7.1.0 (2007-02) 6 Release 7 1 Scope The present document defines functions and syntax of a set of administrativ
22、e commands for a telecommunication card. The commands defined in the present document are compliant to the commands defined in the ISO/IEC 7816 9 series where corresponding commands in ISO/IEC are available. The commands described in the present document are using parts of the functionality of the c
23、ommands described in the ISO/IEC 7816-3 1. 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. The present document does not c
24、over the internal implementation within the UICC and/or the external equipment. 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 and/or editi
25、on number or version number) 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 TC SCP document, a non-specific reference implicitly refers to the latest version of that document in t
26、he same Release as the present document. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their
27、long term validity. 1 ISO/IEC 7816-3: “Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols“. 2 ISO/IEC 7816-4: “Identification cards - Integrated circuit cards - Part 4: Organisation, security and commands
28、for interchange“. 3 Void. 4 Void. 5 ETSI TS 102 221: “Smart cards; UICC-Terminal interface; Physical and logical characteristics (Release 6)“. 6 Void. 7 ETSI TS 101 220: “Smart cards; ETSI numbering system for telecommunication application providers (Release 6)“. 8 ETSI TS 102 223: “Smart cards; Car
29、d Application Toolkit (CAT) (Release 6)“. 9 ISO/IEC 7816 (all parts): “Identification cards - Integrated circuit cards“. ETSI ETSI TS 102 222 V7.1.0 (2007-02) 7 Release 7 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and defini
30、tions 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 cur
31、rent 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
32、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
33、 consisting of 2 bytes 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 termin
34、al and referenced by a record number or a record pointer 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 telecom
35、munication 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 ETSI ETSI TS 102 222 V7.1.0 (2007
36、-02) 8 Release 7 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: AC Access Condition ADF Application Dedicated File AM Access Mode AM_DO Access Mode Data Object APDU Application Protocol Data Unit ATR Answer To Reset BER Basic Encoding RuleCLA CLAss DF
37、Dedicated File (abbreviation formerly used for Data Field) EF Elementary File FCP File Control Parameters ID IDentifier IEC International Electrotechnical Commission INS INStruction ISO International Organization for Standardization Lc Length of command data sent by the application layer LCSI Life C
38、ycle Status Information Le maximum Length of data expected by the application layer LSB Least Significant Bit M Mandatory MF Master File MSB Most Significant Bit O Optional PIN Personal Identification Number RFU Reserved for Future Use SM Secure Messaging SW1/SW2 Status Word 1/Status Word 2 TLV Tag
39、Length Value 4 Mapping principles UICC Cards compliant to the present document shall follow the rules of TS 102 221 5 in clauses 7 and 10. 5 Security architecture The general coding of security attributes assigned to files by use of the CREATE FILE command is as described in TS 102 221 5. ETSI ETSI
40、TS 102 222 V7.1.0 (2007-02) 9 Release 7 6 Description of the functions and commands 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 C
41、LA INS CREATE FILE DELETE FILE DEACTIVATE FILE ACTIVATE FILE TERMINATE DF TERMINATE EF TERMINATE CARD USAGE RESIZE FILE 0X 0X 0X 0X 0X 0X 0X 8X E0 E4 04 44 E6 E8 FE D4 The coding of the value X for the CLA-bytes in table 1 shall be according to ISO/IEC 7816-4 2. All bytes specified as RFU shall be s
42、et 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, the Lc and data field must be adopted. Other commands may be needed in order to execute the commands listed above (e.g. EXTERNAL AUTHENTICATE). If s
43、uch 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 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
44、 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
45、 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. 6.3 CREATE FILE 6.3.1 Definition and scope This function allows the creation of a new file under the
46、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 di
47、rectory 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
48、current record pointer is on the last created record. After creation of an EF with BER TLV structure, the current tag pointer is undefined. ETSI ETSI TS 102 222 V7.1.0 (2007-02) 10Release 7 The memory space allocated shall be reserved for the created file. If an ADF is created, some instance has to
49、take care of the administration of the application, e.g. updating the EFDIRwith the application ID. The CREATE FILE command does not take care of this administration by its own. The DF Name tag shall only provided 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 c
