Menu

ETSI · Technical Specification

TS 102 221v5.7.0

Smart cards; UICC-Terminal interface; Physical and logical characteristics

Specifies the physical, electrical and logical interface between a UICC and a terminal, including communication protocols, commands, files and procedures.

Version
v5.7.0
  1. v18.4.02026-05
  2. v18.3.02025-10
  3. v18.2.02024-06
  4. v18.1.02023-09
  5. v18.0.02023-05
  6. v17.4.02023-02
  7. v17.3.02022-11
  8. v17.2.02022-08
  9. v17.1.02022-02
  10. v17.0.02021-10
  11. v16.6.02021-10
  12. v16.5.02021-09
  13. v16.4.02021-04
  14. v16.3.02020-11
  15. v16.2.02020-05
  16. v16.1.02019-11
  17. v16.0.02019-07
  18. v15.5.02020-05
  19. v15.4.02019-11
  20. v15.3.02019-07
  21. v15.2.02019-05
  22. v15.1.02018-12
  23. v15.0.02018-07
  24. v14.2.02019-07
  25. v14.1.02018-07
  26. v14.0.02017-02
  27. v13.2.02017-02
  28. v13.1.02016-05
  29. v13.0.02015-09
  30. v12.1.02015-09
  31. v12.0.02014-12
  32. v11.1.02013-11
  33. v11.0.02012-06
  34. v10.0.02011-12
  35. v9.2.02010-10
  36. v9.1.02010-04
  37. v9.0.02010-02
  38. v8.5.02010-10
  39. v8.4.02010-02
  40. v8.3.02009-08
  41. v8.2.02009-06
  42. v8.1.02009-04
  43. v8.0.02008-08
  44. v7.18.02010-10
  45. v7.17.02010-02
  46. v7.16.02009-08
  47. v7.15.02009-06
  48. v7.14.02009-04
  49. v7.13.02009-01
  50. v7.12.02008-08
  51. v7.11.02008-07
  52. v7.10.02008-02
  53. v7.9.02007-07
  54. v7.8.02007-02
  55. v7.7.02006-10
  56. v7.6.02006-08
  57. v7.5.02006-05
  58. v7.4.02006-01
  59. v7.3.02005-10
  60. v7.2.02005-08
  61. v7.1.02005-05
  62. v7.0.02004-12
  63. v6.16.02010-10
  64. v6.15.02010-02
  65. v6.14.02007-07
  66. v6.13.02006-10
  67. v6.12.02006-05
  68. v6.11.02006-01
  69. v6.10.02005-10
  70. v6.9.02005-08
  71. v6.8.02005-05
  72. v6.7.02004-12
  73. v6.6.02004-09
  74. v6.5.02004-06
  75. v6.4.02004-03
  76. v6.3.02004-01
  77. v6.2.02003-09
  78. v6.1.02003-06
  79. v6.0.02003-02
  80. v5.10.02007-07
  81. v5.9.02005-10
  82. v5.8.02005-08
  83. v5.7.02004-12
  84. v5.6.02004-01
  85. v5.5.02003-09
  86. v5.4.02003-06
  87. v5.3.02003-02
  88. v5.2.02002-10
  89. v5.1.02002-07
  90. v5.0.02002-05
  91. v4.16.02007-07
  92. v4.15.02005-10
  93. v4.14.02005-08
  94. v4.13.02004-12
  95. v4.12.02004-01
  96. v4.11.02003-09
  97. v4.10.02003-06
  98. v4.9.02003-02
  99. v4.8.02002-10
  100. v4.7.02002-07
  101. v4.6.02002-05
  102. v4.5.02002-03
  103. v4.4.02001-10
  104. v4.3.02001-07
  105. v4.2.02001-04
  106. v4.1.02001-02
  107. v4.0.02001-01
  108. v3.18.02007-07
  109. v3.17.02005-10
  110. v3.16.02005-08
  111. v3.15.02004-12
  112. v3.14.02004-06
  113. v3.13.02004-01
  114. v3.12.02003-09
  115. v3.11.02003-06
  116. v3.10.02003-02
  117. v3.9.02002-10
  118. v3.8.02002-07
  119. v3.7.02002-05
  120. v3.6.02002-03
  121. v3.5.02001-10
  122. v3.4.02001-07
  123. v3.3.02001-04
  124. v3.2.02001-02
  125. v3.1.02001-01
  126. v3.0.02000-09
Issued
2004-12
Release
Release 5
Source
Original PDF · Publisher page

Some table cells in this version could not be converted. For the complete tables, see the original PDF.

Overview

This document defines the interface between a UICC and a terminal. It covers card form factors, operating conditions and contacts, electrical characteristics, activation and reset procedures, and communication protocols. It also specifies the UICC application and file model, security features, APDU command and response structures, commands, application-independent files, and related procedures. These specifications provide a common basis for terminals and UICCs to communicate; administrative procedures and initial card management are outside its scope.

  • UICC–terminal interface
  • APDU
  • T=0
  • ATR
  • PPS
  • logical channels

Overview generated automatically from the document's scope and outline. The document text is authoritative.

Changes since v5.6.0

40 clauses modified

Compared automatically clause by clause from the extracted text of both versions; differences only in layout, spacing or table cells are ignored. The documents are authoritative.

2 Referencesmodified

…stics of the USIM Application (3GPP TS 31.102 Release 5)". [3] ETSI TS 101 220: "Smart cards; ETSI numbering system for telecommunication application providers … (Release 5)".". [4] ETSI TS 102 223: "Smart cards; Card Application Toolkit (CAT)". [5] ITU-T Recommendation E.118: "The international telecommunication charge card". [6] ISO … …

3.1 Definitionsmodified

…d data sent by the application layer in a case 3 or 4 Command Le: maximum length of data Expected by the application layer in response to a case 2 or 4 Command … Lr: length of data sent back to the terminal by the UICC in response to a case 2 or 4 Command Luicc: exact Length of data available in the UICC to be returned in response to the case 2 or 4 Command received by the UICC Master File (MF): unique mandatory … …

3.3 Abbreviationsmodified

…n ADdress DF Dedicated File DO Data Object DST Digital Signature Template EDC Error Detection Code byte EF Elementary File etu elementary time unit f frequency … FCI File Control Information FCP File Control Parameters Fi clock rate conversion factor FID File IDentifier GSM Global System for Mobile communications I/O Input/Output I-block Information… …

6.2.2 Power consumption of the UICC during ATRmodified

…il the ATR is received and an application is selected. Table 6.2a: Power consumption that applies during ATR at maximum external clock frequency Symbol Voltage … Class Maximum Unit Class Icc A 10 mA Icc B 7,5 mA Icc C 5 mA Icc D RFU mA Icc E RFU mA Table 6.2b: Power consumption that applies during ATR at 4 MHz Symbol Voltage Class Maximum Unit Class Icc B 6 mA Icc C 4 mA Icc D RFU mA Icc E RFU mA NOTE: 4 MHz is the maximum clock speed specified in GSM for 3 V and below.

6.2.3 Application related electrical parametersmodified

…he application and get this information in the response of the command. Table 6.3: Maximum power consumption of the UICC during the UICC session Symbol Voltage … Class Maximum Unit Class Icc A 60 mA Icc B 50 mA Icc C 30 mA Icc D RFU mA Icc E RFU mA NOTE: All values assume the maximum external clock. Applications may specify their own maximum pow … ng application session at maximum clock speed is specified in table 6.4. Table 6.4: Minimum power supply by the terminal during the UICC session Symbol Voltage … Class Minimum Unit Class Icc A 10 mA Icc B 10 mA Icc C 10 mA Icc D RFU mA Icc E RFU mA NOTE: All values assume the maximum external clock.

7.2.2.3.2 Status bytesmodified

…mand. A normal ending of a command is indicating by SW1 SW2 = '90 00'. Table 7.2: Status byte coding Byte Value Action SW1 '6X' or '9X' (except '60', '61', and … '6C') The terminal shall wait for a further status word (SW2). '6C') The terminal shall return the status words (together with any appropriate data) to the application layer and shall wait for another C-APDU.

7.2.3.2 Block frame structuremodified

…ch block has the following structure. Table 7.3: Block frame structure Prologue field Information field Epilogue field NAD PCB LEN INF EDC 1 byte 1 byte 1 byte … 0-2540 byte to 254 bytes 1 byte The prologue field and the epilogue field are mandatory. The Information field is optional.

7.3.2 Transportation of a APDU using T=1modified

…esent) and the status are returned from the UICC to the transport layer of the terminal in the INF of an I-block. If the UICC returns a status which indicates: … normal processing ('61XX'); a warning ('62XX' or '63XX'); an application condition ('9XXX'); or a successful execution of the command ('9000'); then it shall also return data (if available… …

7.3.2.2 Case 2modified

…es. Terminal UICC  Application Layer (C-APDU) CLA INS P1 P2 Le Transport Layer (C-TPDU, INF) CLA INS P1 P2 Le Command Processing Transport Layer (R-TPDU, INF) … Lr bytes of DATA | SW1 | SW2  Lr bytes of DATA | SW1 | SW2 Application Layer (R-APDU) Lr bytes of DATA | SW1 | SW2 Figure 7.11 The R-APDU consists of either the INF of the I-block or the concatenation of the INF of successive I-blocks all received in the same response, which all shall be chained.

7.3.2.4 Case 4modified

…U) CLA INS P1 P2 Lc [Lc bytes of DATA] Le Transport Layer (C-TPDU, INF) CLA INS P1 P2 Lc [Lc bytes of DATA] Le Command Processing Transport Layer (R-TPDU, INF) … LeLr bytebytes of DATA | SW1 | SW2  LeLr bytebytes of DATA | SW1 | SW2 Application Layer (R-APDU) LeLr bytebytes of DATA | SW1 | SW2 Figure 7.13 The response consists of either the INF of an I-block received in the response or the concatenation of INF of successive I-bloc… …

8.6 Reservation of file IDsmodified

…HONEBOOK). Elementary files: - administrative use:  '6F XX' in the DFs '7F 4X'; '4F XX' in the DFs '5F 1X', '5F2X'.  '6F 1X' in the DFs '7F 10', '7F 20', '7F … 21';21'.  '4F 1X' in all 2nd level DFs.  '2F EX' in the MF '3F 00';00'. - operational use:  '6F 2X', '6F 3X', '6F 4X' in '7F 10' and '7F 2X';2X'.  '4F YX', where Y ranges from '2' to 'F' in all 2nd level DFs.  '2F05', '2F06' and '2F 1X' in the MF '3F 00'. - operational use ISO/IEC 7816-4 [12]:  '2F00'… …

9.2.2 Access modemodified

…ng to ISO/IEC 7816-9 [16]. For instructions not belonging to a group as defined in ISO/IEC 7816-9 [16] the access rights can be indicated using AM_DO tags '81' … -to '8F'. The value of the tag defining the AM_DO indicates what description of the command exists in the definition list to follow in the value part of the data o… …

9.5.1 Access condition mappingmodified

…y references. The usage of a key reference shall be in accordance with the group definition in table 9.2. Table 9.2: Access condition level coding Level Access … Conditioncondition 0 ALWays 1 User Verification (PIN) 2 (see note 1) 3 to 4 Reserved for Future Use 5 to 6 (see note 2) 7 NEVer NOTE 1: This level is reserved for a second level … level 2 key reference is only valid within the ADF/DF where it is indicated. Table 9.3: PIN mapping into key references Value Usage CRT Tag Len Key Ref Access … Conditioncondition Level Len Value Qualifier Len Val Tag Tag '90' '00' - - - - - - ALW 0 'A4' '06' '83' '01' '01' '95' '01' '08' PIN Appl 1 1 'A4' '06' '83' '01' '02' '95' '01' '… …

10.1.4 Coding of Lc bytemodified

…Lc is optional, in the command APDU, however if the Lc is present in the command APDU, data field consists of Lc subsequent bytes. The terminal may send from 1 … byte to 255 bytes of command data.

11.1.1.2 Command parameters and datamodified

… - 0 0 - First or only occurrence - - - - - - 0 1 - Last occurrence - - - - - - 1 0 - Next occurrence - - - - - - 1 1 - Previous occurrence NOTE 1: Whether the … FCIFCP information is returned or not depends on the type of APDU. NOTE 2: This only applies when P1 indicates SELECT by DF name. If P1 = '00' and the data field is e… …

11.1.1.3.1 Response for MF, DF or ADFmodified

…C1 DF name (AID) '84' 11.1.1.4.5 C2 Proprietary information 'A5' 11.1.1.4.6 C3 Life Cycle Status Integer '8A' 11.1.1.4.9 M Security attributes '86', '8B', '8C' … 11.1.1.4.7 C4 or 'AB' 11.1.1.4.7 C4 PIN Status Template DO 'C6' 11.1.1.4.10 M Total file size '81' 11.1.1.4.2 O M: Mandatory. O: Optional. C1: The File identifier is mandatory for a DF or the MF.… …

11.1.1.3.2 Response for an EFmodified

…1.4.3 M File Identifier '83' 11.1.1.4.4 M Proprietary information 'A5' 11.1.1.4.6 O Life Cycle Status Integer '8A' 11.1.1.4.9 M Security attributes '86', '8B', … 11.1.1.4.7 C1 '8C', or 'AB' 11.1.1.4.7 C1 File size '80' 11.1.1.4.1 M Total file size '81' 11.1.1.4.2 O Short file identifier (SFI) '88' 11.1.1.4.8 O M: Mandatory. O: Optional. C1: Exactly one shall be present.

11.1.1.4.3 File Descriptormodified

Byte(s) Description Status Value Length 1 Tag M '82' 1 2 Length M '02' or '05' 1 3 File descriptor byte (see table 11.5) M 1 4 Data coding byte M '21' 1 5 to 6 Record length C '0001' to 2 '00FF' 2 7 Number of records C '01' to 'FE' 1 M: Mandatory. C: These bytes are mandatory for linear fixed and cyclic files, otherwise they are not applicable. File desc… …

11.1.1.4.6.2 Application power consumptionmodified

…ort the power consumption indicated by the application. Byte(s) Description Value Length 1 Tag '81' 1 2 Length '03' 1 3 Supply voltage class at which the power … 1 consumption is measured 1 4 Application power consumption '01'-'3C''01' to '3C' 1 5 Power consumption Reference Frequency '0A'-'FF''0A' to 'FF' 1 The Power consumption Reference Frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is 1 MHz and 'FE' is 25,4 MHz. The value 'FF' … …

11.1.1.4.6.3 Minimum application clock frequencymodified

… of the TLV objects within the constructed TLV is relevant. Byte(s) Description Value Length 1 Tag '82' 1 2 Length '01' 1 3 Application minimum clock frequency … '0A'-'FF''0A' to 'FF' 1 The minimum clock frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is 1 MHz and 'FE' is 25,4 MHz. If this TLV object is not pre… …

11.1.1.4.7.3 Referenced to expanded formatmodified

If the length of the data following tag '8B' = '03' the following definition applies. Byte(s) Description Value Length 1 Tag '8B' 1 2 Length 3 1 3-43 to 4 EFARR File ID 2 5 EFARR Record number 1 If the length of the data following tag '8B' is '02' + X × '02' the following definition applies. Byte(s) Description Value Length 1 Tag '8B' 1 2 Length '02' + X × '02' 1 3-43 to 4 EFARR File ID 2 X+4 SEID 1 X+5 EFARR Record number NOTE: For each increment of X a new set of SEID and an EFARR Record numbers are introduced.

11.1.3.2 Command parametersmodified

…he offset 1 0 0 X X X X X SFI referencing used, b1 to b5 are the SFI and P2 is the offset to the first byte to read Response data: Byte(s) Description Length 1 … -to Le Data read Le

11.1.5.2 Command parametersmodified

…previous" P1 has no significance within the scope of the present document and shall be set to '00' by the terminal. Response data: Byte(s) Description Length 1 … -to Le Data read Le

11.1.7.2 Command parameters and datamodified

….12: Coding of P2 b8 b7 b6 b5 b4 b3 b2 b1 Meaning 0 0 0 0 0 - - - Currently selected EF X X X X X - - - Short File Identifier 1 1 1 1 1 - - - RFU - - - - - 0 X … XRFUX RFU (see note) - - - - - 1 0 XSimpleX Simple search. Usage of P1 as a record number - - - - - 1 0 0 Start forward search from record indicated in P1 - - - - - 1 0 1 Start backward search from record indica … ch from previous record", P1 has no significance within the scope of the present document and shall be set to '00'. Response data: Byte(s) Description Length 0 … -to Le Record number(s) Le NOTE: If Le is empty no record numbers will be returned.

11.1.8.2 Command parameters and datamodified

…ues are RFU. In this command, Lc is restricted to 0 < Lc < 128 and the maximum record length is limited to 127 bytes. Response data: Byte(s) Description Length … 1-X1 to X Value of the increased record X X + 1 -to X + Lc Value which has been added Lc NOTE: X denotes the length of the record.

11.1.9.3 Command parametersmodified

…'01' to '1F') The five least significant bits of parameter P2 specify the PIN key reference number (see clause 9.5.1). Command data: Byte(s) Description Length … 1-81 to 8 PIN value 8

11.1.10.2 Command parametersmodified

… '10' Data Old PIN value, new PIN value Le Not present NOTE: "Change PIN" is named "exchange reference data" in ISO/IEC 7816-8 [15]. Byte(s) Description Length … 1-81 to 8 Old PIN value 8 9 -to 16 New PIN value 8

11.1.11.2 Command parametersmodified

…eplacement - X X - - - - - '00' (other values are RFU) - - - X X X X X Global key reference data number ('01' to '1F') Command data: Byte(s) Description Length … 1-81 to 8 PIN value 8

11.1.12.2 Command parametersmodified

…ed for the VERIFY PIN command, see clause 11.1.9 Lc Length of the subsequent data = '08' Data PIN value Le Not present Command data: Byte(s) Description Length … 1-81 to 8 PIN value 8

11.1.13.3 Command parametersmodified

… VERIFY PIN command (see clause 11.1.9) Lc Empty or '10' Data Empty or UNBLOCK PIN value, new PIN value Le Not present Command data: Byte(s) Description Length … 1-81 to 8 UNBLOCK PIN value 8 9 -to 16 New PIN value 8

11.1.16.2 Command parameters and datamodified

…tes that no information on the key is given. The key is implicitly known in the context of the selected application. Command data: Byte(s) Description Length 1 … -to Lc Authentication related data (see note) Lc NOTE: The command data must be specified by each application specific document. Response data (generic): Byte(s) Description Length 1 -to Le Authentication related data (see note) Le NOTE: The response data must be specified by each application specific document.

11.1.18.2 Command parameters and datamodified

…NS As specified in clause 10.1.2 P1 '00' P2 '00' Lc Not present Data Not present Le Maximum length of response data Response data: Byte(s) Description Length 1 … -to Lr Random number Lr

13.1 EFDIRmodified

…datory SFI: Mandatory Record size: X bytes Update activity: low Access Conditions: READ ALW UPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length … 1-X1 to X Application template TLV object M X bytes The EF consists of one or more records, with each record able to hold one entry. Each entry in the EFDIR is an applica … us 1 Application template tag = '61' M 1 Length of the application template = '03'-'7F' M 1 Application Identifier tag = '4F' M 1 AID length = '01'-'10' M '01' … -to '10' AID value. For 3G applications, see TS 101 220 [3] M 1 Application label tag = '50' O 1 Application label length O note 1 Application label value O NOTE 1… …

13.2 EFICCID (ICC Identification)modified

…datory SFI: Optional File size: 10 bytes Update activity: low Access Conditions: READ ALW UPDATE NEV DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length 1 … -to 10 Identification number M 10 bytes Identification number: Contents: according to ITU-T Recommendation E.118 [5]. Purpose: card identification number. Coding: … …

13.3 EFPL (Preferred Languages)modified

…ndatory SFI: Mandatory File size: 2n bytes Update activity: low Access Conditions: READ ALW UPDATE PIN DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length … 1-21 to 2 1st language code (highest prior) M 2 bytes 3-43 to 4 2nd language code O 2 bytes 2n-1 -to 2n nth language code (lowest prior) O 2 bytes Coding: each language code is a pair of alpha-numeric characters, defined in ISO 639 [6]. Each alpha- numeric cha… …

13.4 EFARR (Access Rule Reference)modified

…ional SFI: Optional Record length: X bytes Update activity: low Access Conditions: READ ALW UPDATE ADM DEACTIVATE ADM ACTIVATE ADM Bytes Description M/O Length … 1-X1 to X Access Rule TLV data objects M X bytes This EF contains one or more records containing access rule information according to the referenced format as defined in… …

E.3 Expanded formatmodified

In the expanded format AM_DOs and SC_DOs are used to create the access rules. The expanded format access rule is indicated by tag 'AB' in the FCI.FCP. An access rule in this format is encoded with an AM_DO followed by a sequence of SC_DOs.

E.3.1 AM_DOmodified

The AM_DO is defined in ISO/IEC 7816-9 [16]. The content of the AM_DO is defined by the tag value. Tag '80' indicates that the AM_DO contains an AM byte. Tags '81'-'8F''81' to '8F' indicates that the AM_DO contains a command description. The content of the command description is dependent upon the tag value as defined in ISO/IEC 7816-9 [1… …

E.3.3 Access rule referencingmodified

…e an internal file, referenced implicitly, or may be referenced explicitly, e.g. by a file ID. The access rule stored in a file is indicated by tag '8B' in the … FCI.FCP. The value of this DO contains at least one record number, called ARR. The DO can contain: a single byte containing the record number of the rule, valid if the … …

L Change historymodified

…P-030219 139 F Correction of Security attributes length coding table 5.4.0 5.5.0 2003-12 SCP-15 SCP-030486 147 A Turnaround time requirement for T=0 5.5.0 5.6.0 … 2004-11 SCP-19 SCP-040414 167 A Corrections to References and replacement of FCI with FCP 5.6.0 5.7.0 SCP-040414 172 A Correction of description of response data structure for T=1 SCP-040414 176 A Delete status word '61XX' for T=1

Contents
  1. Foreword
  2. Introduction
  3. 1 Scope
  4. 2 References
  5. 3 Definitions, symbols, abbreviations and coding conventions
  6. 3.1 Definitions
  7. 3.2 Symbols
  8. 3.3 Abbreviations
  9. 3.4 Coding conventions
  10. 4 Physical characteristics
  11. 4.1 ID-1 UICC
  12. 4.2 Plug-in UICC
  13. Upper edge
  14. 4.3 Temperature range for card operation
  15. 4.4 Contacts
  16. 4.4.1 Provision of contacts
  17. 4.4.2 Contact activation and deactivation
  18. 4.4.3 Inactive contacts
  19. 4.4.4 Contact pressure
  20. 5 Electrical specifications of the UICC - Terminal interface
  21. 5.1 Class A operating conditions
  22. 5.1.1 Supply voltage Vcc (contact C1)
  23. 5.1.2 Reset (RST) (contact C2)
  24. 5.1.3 Programming voltage Vpp (contact C6)
  25. 5.1.4 Clock CLK (contact C3)
  26. 5.1.5 I/O (contact C7)
  27. 5.2 Class B operating conditions
  28. 5.2.1 Supply voltage Vcc (contact C1)
  29. 5.2.2 Reset (RST) (contact C2)
  30. 5.2.3 Clock CLK (contact C3)
  31. 5.2.4 I/O (contact C7)
  32. 5.3 Class C operating conditions
  33. 5.3.1 Supply voltage Vcc (contact C1)
  34. 5.3.2 Reset (RST) (contact C2)
  35. 5.3.3 Clock CLK (contact C3)
  36. 5.3.4 I/O (contact C7)
  37. 6 Initial communication establishment procedures
  38. 6.1 UICC activation and deactivation
  39. 6.2 Supply voltage switching
  40. 6.2.1 Supply voltage classes
  41. 6.2.2 Power consumption of the UICC during ATR
  42. 6.2.3 Application related electrical parameters
  43. 6.3 Answer To Reset content
  44. 6.3.1 Coding of historical bytes
  45. 6.3.2 Speed enhancement
  46. 6.4 PPS procedure
  47. 6.5 Reset procedures
  48. 6.5.1 Cold reset
  49. 6.5.2 Warm reset
  50. 6.5.3 Reaction to resets
  51. 6.6 Clock stop mode
  52. 6.7 Bit/character duration and sampling time
  53. 6.8 Error handling
  54. 6.9 Compatibility
  55. 7 Transmission protocols
  56. 7.1 Physical layer
  57. 7.2 Data link layer
  58. 7.2.1 Character frame
  59. 7.2.2 Transmission protocol T=0
  60. 7.2.3 Transmission protocol T=1
  61. 7.3 Transport layer
  62. 7.3.1 Transportation of an APDU using T=0
  63. 7.3.2 Transportation of a APDU using T=1
  64. 7.4 Application layer
  65. 7.4.1 Exchange of APDUs
  66. 7.4.2 CAT layer
  67. 8 Application and file structure
  68. 8.1 UICC application structure
  69. 8.2 File types
  70. 8.2.1 Dedicated files
  71. 8.2.2 Elementary files
  72. 8.3 File referencing
  73. 8.4 Methods for selecting a file
  74. 8.4.1 SELECT by File IDentifier referencing
  75. 8.4.2 SELECT by path referencing
  76. 8.4.3 Short File Identifier
  77. 8.5 Application characteristics
  78. 8.5.1 Explicit application selection
  79. 8.5.2 Application session activation
  80. 8.5.3 Application session termination
  81. 8.5.4 Application session reset
  82. 8.5.5 GSM/USIM application interaction and restrictions
  83. 8.6 Reservation of file IDs
  84. 8.7 Logical channels
  85. 9 Security features
  86. 9.1 Supported security features
  87. 9.2 Security architecture
  88. 9.2.1 Security attributes
  89. 9.2.2 Access mode
  90. 9.2.3 Security condition
  91. 9.2.4 Access rules
  92. 9.2.5 Compact format
  93. 9.2.6 Expanded format
  94. 9.2.7 Access rule referencing
  95. 9.3 Security environment
  96. 9.3.1 Definition of the security environment
  97. 9.3.2 Logical channels and security environment
  98. 9.4 PIN definitions
  99. 9.4.1 Universal PIN
  100. 9.4.2 Application PIN
  101. 9.4.3 Local PIN
  102. 9.4.4 PINs and logical channels
  103. 9.5 PIN and key reference relation ship
  104. 9.5.1 Access condition mapping
  105. 9.5.2 PIN status indication
  106. 10 Structure of commands and responses
  107. 10.1 Command APDU structure
  108. 10.1.1 Coding of Class Byte
  109. 10.1.2 Coding of Instruction Byte
  110. 10.1.3 Coding of parameter bytes
  111. 10.1.4 Coding of Lc byte
  112. 10.1.5 Coding of data part
  113. 10.1.6 Coding of Le byte
  114. 10.2 Response APDU structure
  115. 10.2.1 Status conditions returned by the UICC
  116. 10.2.2 Status words of the commands
  117. 10.3 Logical channels
  118. 11 Commands
  119. 11.1 Generic commands
  120. 11.1.1 SELECT
  121. 11.1.2 STATUS
  122. 11.1.3 READ BINARY
  123. 11.1.4 UPDATE BINARY
  124. 11.1.5 READ RECORD
  125. 11.1.6 UPDATE RECORD
  126. 11.1.7 SEARCH RECORD
  127. 11.1.8 INCREASE
  128. 11.1.9 VERIFY PIN
  129. 11.1.10 CHANGE PIN
  130. 11.1.11 DISABLE PIN
  131. 11.1.12 ENABLE PIN
  132. 11.1.13 UNBLOCK PIN
  133. 11.1.14 DEACTIVATE FILE
  134. 11.1.15 ACTIVATE FILE
  135. 11.1.16 AUTHENTICATE
  136. 11.1.17 MANAGE CHANNEL
  137. 11.1.18 GET CHALLENGE
  138. 11.2 CAT commands
  139. 11.2.1 TERMINAL PROFILE
  140. 11.2.2 ENVELOPE
  141. 11.2.3 FETCH
  142. 11.2.4 TERMINAL RESPONSE
  143. 12 Transmission oriented commands
  144. 12.1 T=0 specific commands
  145. 12.1.1 GET RESPONSE
  146. 13 Application independent files
  147. 13.1 EFDIR
  148. 13.2 EFICCID (ICC Identification)
  149. 13.3 EFPL (Preferred Languages)
  150. 13.4 EFARR (Access Rule Reference)
  151. 14 Application independent protocol
  152. 14.1 File related procedures
  153. 14.1.1 Reading an EF
  154. 14.1.2 Updating an EF
  155. 14.1.3 Increasing an EF
  156. 14.2 PIN related procedures
  157. 14.2.1 PIN verification
  158. 14.2.2 PIN value substitution
  159. 14.2.3 PIN disabling
  160. 14.2.4 PIN enabling
  161. 14.2.5 PIN unblocking
  162. 14.3 Application selection procedures
  163. 14.3.1 Application selection by use of the EFDIR file
  164. 14.3.2 Direct application selection
  165. 14.3.3 Direct application selection with partial AID
  166. 14.4 General application related procedures
  167. 14.4.1 Application session activation
  168. 14.4.2 UICC application interrogation
  169. 14.4.3 UICC application session termination
  170. 14.5 Miscellaneous procedures
  171. 14.5.1 UICC activation
  172. 14.5.2 UICC presence detection
  173. 14.5.3 UICC preferred language request
  174. 14.5.4 UICC logical channels
  175. 14.6 CAT related procedures
  176. 14.6.1 CAT Initialization procedure
  177. 14.6.2 Proactive polling
  178. 14.6.3 Support of commands
  179. 14.6.4 Support of response codes
  180. 14.6.5 Independence of applications and CAT tasks
  181. 14.6.6 Use of BUSY status response
  182. 14.6.7 Additional processing time
  183. Annex A (normative):
  184. UCS2 coding of Alpha fields for files residing on the UICC
  185. Annex B (informative): Main states of a UICC
  186. Annex C (informative):
  187. APDU protocol transmission examples
  188. C.1 Exchanges Using T=0
  189. C.1.1 Case 1 command
  190. C.1.2 Case 2 command
  191. C.1.3 Case 3 command
  192. C.1.4 Case 4 command
  193. C.1.5 Case 2 commands Using the '61' and '6C' procedure bytes
  194. C.1.6 Case 4 command Using the '61' procedure byte
  195. C.1.7 Case 4 command with warning condition
  196. Annex D (informative): ATR examples
  197. Annex E (informative):
  198. Security attributes mechanisms and examples
  199. E.1 Coding
  200. E.2 Compact format
  201. E.2.1 AM byte
  202. E.2.2 SC byte
  203. E.2.3 Examples
  204. E.3 Expanded format
  205. E.3.1 AM_DO
  206. E.3.2 SC_DO
  207. E.3.3 Access rule referencing
  208. E.3.4 Examples
  209. Annex F (informative):
  210. Example of contents of EFARR '2F06'
  211. F.1 Sample content of the EFARR
  212. Annex G (informative):
  213. Access Rules Referencing (ARR)
  214. G.1 Sample content of EFARR
  215. G.2 Example of access rule referencing with SE ID
  216. Annex H (normative): List of SFI Values
  217. H.1 List of SFI Values at the MF Level
  218. Annex I (informative): Resets and modes of operation
  219. Annex J (informative): Example of the use of PINs
  220. J.1 Application having several ADFs
  221. J.2 Two applications with two different security contexts
  222. Annex K (informative): Bibliography
  223. Annex L (informative): Change history
  224. History
  225. Intellectual Property Rights

Foreword

This Technical Specification (TS) has been produced by ETSI Project Smart Card Platform (SCP).

It is based on work originally done in the 3GPP in TSG-terminals WG3.

The contents of the present document are subject to continuing work within EP SCP and may change following formal EP SCP approval. If EP 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:

Introduction

The present document defines a generic Terminal/Integrated Circuit Card (ICC) interface.

The aim of the present document is to ensure interoperability between an ICC and a terminal independently of the respective manufacturer, card issuer or operator. The present document does not define any aspects related to the administrative management phase of the ICC. Any internal technical realization of either the ICC or the terminal is only specified where these are reflected over the interface.

Application specific details for applications residing on an ICC are specified in the respective application specific documents. The Universal Subscriber Identity Module (USIM)-application for 3G telecommunication networks is specified in TS 131 102 [2].

1 Scope

The present document specifies the interface between the UICC and the terminal.

The present document specifies:

The administrative procedures and initial card management are not part of the present document.

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 edition 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.

Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.

  1. ETSI TS 123 038: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Alphabets and language-specific information (3GPP TS 23.038 Release 5)".
  2. ETSI TS 131 102: "Universal Mobile Telecommunications System (UMTS); Characteristics of the USIM Application (3GPP TS 31.102 Release 5)".
  3. ETSI TS 101 220: "Smart cards; ETSI numbering system for telecommunication application providers ".
  4. ETSI TS 102 223: "Smart cards; Card Application Toolkit (CAT)".
  5. ITU-T Recommendation E.118: "The international telecommunication charge card".
  6. ISO 639: "Codes for the representation of names of languages".
  7. ISO/IEC 7810: "Identification cards - Physical characteristics".
  8. ISO/IEC 7811-1: "Identification cards - Recording technique - Part 1: Embossing".
  9. ISO/IEC 7816-1: "Identification cards - Integrated circuit(s) cards with contacts - Part 1: Physical characteristics".
  10. ISO/IEC 7816-2: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 2: Dimensions and location of the contacts".
[11]ISO/IEC 7816-3: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols".
[12]ISO/IEC 7816-4: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 4: Interindustry commands for interchange".
[13]ISO/IEC 7816-5: "Identification cards - Integrated circuit(s) cards with contacts - Part 5: Numbering system and registration procedure for application identifiers".
[14]ISO/IEC 7816-6: "Identification cards - Integrated circuit(s) cards with contacts - Part 6: Interindustry data elements".
[15]ISO/IEC 7816-8: "Identification cards - Integrated circuit(s) cards with contacts - Part 8: Security related interindustry commands".
[16]ISO/IEC 7816-9: "Identification cards - Integrated circuit(s) cards with contacts - Part 9: Additional interindustry commands and security attributes".
[17]ISO/IEC 10646-1: "Information technology - Universal multiple-octet coded Character Set (UCS) - Part 1: Architecture and basic multilingual plane".

3 Definitions, symbols, abbreviations and coding conventions

3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

access conditions: set of security attributes associated with a file

ADM: access condition to an EF which is under the control of the authority which creates this file

application: set of security mechanisms, files, data and protocols (excluding transmission protocols)

NOTE: An application can be a first level application and/or a second level application.

application DF: entry point to an application

application protocol: set of procedures required by the application

card session: link between the card and the external world starting with the ATR and ending with a subsequent reset or a deactivation of the card

channel session: link between the card and the external world during a card session on a given logical channel, starting with the opening of the logical channel and ending with the closure of the logical channel or the termination of the card session

class A operating conditions: terminal or a smart card operating at 5 V ± 10 %

class B operating conditions: terminal or a smart card operating at 3 V ± 10 %

class C operating conditions: terminal or a smart card operating at 1,8 V ± 10 %

current directory: latest MF, DF or ADF selected

current EF: latest EF selected

data object: information coded as TLV objects, i.e. consisting of a Tag, a Length and a Value part

Dedicated File (DF): file containing access conditions and, optionally, Elementary Files (EFs) or other Dedicated Files (DFs)

directory: general term for MF, DF and ADF

Elementary File (EF): file containing access conditions and data and no other files file: directory or an organized set of bytes or records in the UICC file identifier: 2 bytes which address a file in the UICC first level application: selectable application that is indicated in EF DIR under the MF (e.g. a USIM application) function: contains a command and a response pair GSM session: part of the card session dedicated to the GSM operation ID-1 UICC: UICC having the format of an ID-1 card NOTE: See ISO/IEC 7816-1 [9]. Lc: length of command data sent by the application layer in a case 3 or 4 Command Le: maximum length of data Expected by the application layer in response to a case 2 or 4 Command Lr: length of data sent back to the terminal by the UICC in response to a case 2 or 4 Command Luicc: exact Length of data available in the UICC to be returned in response to the case 2 or 4 Command received by the UICC Master File (MF): unique mandatory file containing access conditions and optionally DFs and/or EFs multi-application capable terminal: terminal that can support more than one first level application with possibly separate user verification requirements for each application multi-application card: card that can have more than one selectable application multi-session card: card that supports more than one concurrent selectable application session during a card session multi-verification capable UICC: card that can have more than one first level application and may support separate user verification requirements for each application normal USIM operation: relating to general, PIN related, 3G and or GSM security and subscription related procedures padding: one or more bits appended to a message in order to cause the message to contain the required number of bits or bytes 1,8 V technology smart card: smart card operating at 1,8 V ± 10 % and 3 V ± 10 % 1,8 V technology terminal: terminal operating the smart card - terminal interface at 1,8 V ± 10 % and 3 V ± 10 % plug-in UICC: second format of UICC proactive UICC: UICC, which is capable of issuing commands to the terminal NOTE: Part of CAT. record: string of bytes within an EF handled as a single entity record number: number, which identifies a record within an EF record pointer: pointer, which addresses one record in an EF second level application: application which can only be activated during the session of a first level application NOTE: A second level application may have an AID. This AID shall not be stored in EF(DIR) unless it is also a first level application. selectable application: application that is selectable by an AID according to the process described in ISO/IEC 7816-4 [12] over the terminal-UICC interface

selectable application session: link between the application and the external world during a card session starting with the application selection and ending with de-selection or termination of the card session

single verification capable UICC: card that only supports one user verification requirement for all first level applications

state H: high state on the I/O line (Vcc)

state L: low state on the I/O line (Gnd)

3 V technology smart card: smart card operating at 3 V ± 10 % and 5 V ± 10 %

3 V technology terminal: terminal operating the smart card - terminal interface at 3 V ± 10 % and 5 V ± 10 %

type 1 UICC: UICC which always enters the negotiable mode after a warm reset

type 2 UICC: UICC which always enters the specific mode after a warm reset

CAT Application Toolkit procedures: See TS 102 223 [4].

USIM session: selectable application session for a USIM application

3.2 Symbols

For the purposes of the present document, the following symbols apply:

GndGround
t FFall time
t RRise time
VccSupply Voltage
V IHInput Voltage (high)
V ILInput Voltage (low)
V OHOutput Voltage (high)
V OLOutput Voltage (low)
VppProgramming Voltage

3.3 Abbreviations

For the purposes of the present document, the following abbreviations apply:

ACAccess Condition
ACKACKnowledge
ADFApplication Dedicated File
AIDApplication IDentifier
ALWALWays
AMAccess Mode
AM-DOAccess Mode Data Object
APDUApplication Protocol Data Unit
ARRAccess Rule Reference
ATAuthentication Template
ATRAnswer To Reset
BCDBinary Coded Decimal
BERBasic Encoding Rules
BGTBlock Guard Time
BWTBlock Waiting Time
C-APDUCommand APDU
CATCard Application Toolkit
CCTCryptographic Checksum Template
CLACLAss
CLKCLocK
CRTControl Reference Template
CTConfidentiality Template
C-TPDUCommand TPDU
CWICharacter Waiting Integer
CWTCharacter Waiting Time
DADDestination ADdress
DFDedicated File
DOData Object
DSTDigital Signature Template
EDCError Detection Code byte
EFElementary File
etuelementary time unit
ffrequency
FCPFile Control Parameters
Ficlock rate conversion factor
FIDFile IDentifier
GSMGlobal System for Mobile communications
I/OInput/Output
I-blockInformation block
ICCIntegrated Circuit Card
IDIDentifier
IECInternational Electrotechnical Commission
IFSInformation Field Sizes
IFSCInformation Field Size for the UICC
IFSDInformation Field Size for the terminal
INFINFormation field
INSINStruction
ISOInternational Organization for Standardization
LCSILife Cycle Status Information
LENLENgth
LRC LSBLongitudinal Redundancy Check Least Significant Bit
MEMobile Equipment
MFMaster File
MSBMost Significant Bit
NADNode ADdress byte
NEVNEVer
OSIOpen System Interconnection
P2Parameter 1 2
P1Parameter
P3Parameter 3
PCB PDCProtocol Control Byte Personal Digital Cellular
PINPersonal Identification Number
PPSProtocol and Parameter Selection
PSPIN Status
PS_DOPIN Status Data Object
R-APDUResponse APDU
R-blockReceive-ready block
RFUReserved for Future Use
RSTReSeT
R-TPDUResponse TPDU
SADSource ADdress
S-blockSupervisory Block
SCSecurity Condition
SC_DOSecurity Condition Data Object
SESecurity Environment
SEIDSecurity Environment IDentifier
SFIShort (elementary) File Identifier Subscriber Identity Module
SIM SMSecure Message
SMS SMS-PPShort Message Service Short Message Service - Point to Point
TETRATErrestrial Trunked RAdio
TLV TPDUTag Length Value Transfer Protocol Data Unit
UCS2Universal Character Set 2
UEUser Equipment
USIMUniversal Subscriber Identity Module
VPPProgramming power input, optional use by the card
WIWaiting time Integer
WTXWaiting Time eXtension
WWTWork Waiting Time

3.4 Coding conventions

For the purposes of the present document, the following coding conventions apply:

In the UICC, all bytes specified as RFU shall be set to '00' and all bits specifies as RFU shall be set to 0. If the GSM and/or USIM application exists on a UICC or is built on a generic telecommunications card, then other values may apply for the non-GSM or non-USIM applications. The values will be defined in the appropriate specifications for such cards and applications. These bytes and bits shall not be interpreted by a terminal in a GSM or 3G session.

The coding of Data Objects in the present document is according to ISO/IEC 7816-6 [14].

4 Physical characteristics

Two physical types of UICCs are currently specified by the present document. These are the "ID-1 UICC" and the "Plug-in UICC". At least one of the card sizes shall be supported by a terminal that is compliant to the present document.

The physical characteristics of both types of UICCs shall be in accordance with ISO/IEC 7816-1 [9] and ISO/IEC 7816-2 [10] unless otherwise specified by the present document. The following additional requirements shall be applied to ensure correct operation in a Telecom environment.

4.1 ID-1 UICC

The physical characteristics of the ID-1 UICC shall conform to ISO/IEC 7816-1 [9] and ISO/IEC 7816-2 [10].

The terminal shall accept embossed ID-1 UICCs. The embossing shall be in accordance with ISO/IEC 7811-1 [8] and ISO/IEC 7811-3 (see bibliography). The contacts of the ID-1 UICC shall be located on the front (embossed face, see ISO/IEC 7810 [7]) of the card.

4.2 Plug-in UICC

The Plug-in UICC shall have a width of 25 mm, a height of 15 mm, a thickness the same as an ID-1 UICC and a feature for orientation.

Annex A of ISO/IEC 7816-2 [10] applies with the location of the reference points adapted to the smaller size. The three reference points P1, P2 and P3 measure 7,5 mm, 3,3 mm and 20,8 mm, respectively, from 0. The values in figure 2 of ISO/IEC 7816-2 [10] are replaced by the corresponding values of figure 4.1.

The physical characteristics of the Plug-in UICC (Plug-in card) are defined in the present document.

Upper edge

Figure 4.1: Plug-in UICC

4.3 Temperature range for card operation

The temperature range for full operational use shall be between -25°C and +70°C with occasional peaks of up to +85°C. "Occasional" means not more than 4 hours each time and not over 100 times during the life time of the card.

4.4 Contacts

4.4.1 Provision of contacts

4.4.1.1 Terminal

Contacting elements in the terminal in positions C4 and C8 are optional, and are not used by a Telecom application complying with the present document. They shall present a high impedance to the UICC. If it is determined that the UICC is a multi-application UICC, then these contacts may be used. Contact C6 need not be provided for Plug-in cards or any card if the terminal does not support class A operating conditions (see ISO/IEC 7816-3 [11]). If present, C6 shall present a high impedance to the UICC.

4.4.1.2 UICC

Contacts C4 and C8 need not be provided by the UICC. If provided, they shall not be connected internally in the UICC if the UICC only contains a Telecom application. Contact C6 shall not be bonded in the UICC for any function other than supplying Vpp. Contact C6 on a UICC not supporting class A operating conditions is RFU, see ISO/IEC 7816-3 [11].

4.4.2 Contact activation and deactivation

The terminal shall connect, activate and deactivate the UICC in accordance with the operating procedures specified in ISO/IEC 7816-3 [11].

For any voltage level, monitored during the activation sequence, or during the deactivation sequence following normal power-down, the order of the contact activation/deactivation shall be respected.

It is recommended that whenever possible, the deactivation sequence defined in ISO/IEC 7816-3 [11] should be followed by the terminal on all occasions when the terminal is powered down.

If the UICC clock is already stopped and is not restarted, the terminal may deactivate all the contacts in any order, provided that all signals reach low level before Vcc leaves high level. If the UICC clock is already stopped and is restarted before the deactivation sequence, then the deactivation sequence specified in ISO/IEC 7816-3 [11], clause 5.4 shall be followed.

When Vpp is connected to Vcc, as allowed in the present document for terminals supporting class A operation conditions only, then Vpp shall be activated and deactivated with Vcc, at the time of the Vcc activation/deactivation, as specified in the sequences of ISO/IEC 7816-3 [11], clauses 5.2 and 5.4.

4.4.3 Inactive contacts

The voltages on contacts C1, C2, C3, C6 and C7 of the terminal shall be in the range 0 V ± 0,4 V referenced to ground (C5) when the terminal is switched off with the power source connected to the terminal. The measurement equipment shall have a resistance of 50 kΩ when measuring the voltage on C2, C3, C6 and C7. The resistance shall be 10 kΩ when measuring the voltage on C1.

4.4.4 Contact pressure

The contact pressure shall be large enough to ensure reliable and continuous contact (e.g. to overcome oxidization and to prevent interruption caused by vibration). The radius of any curvature of the contacting elements shall be greater than or equal to 0,8 mm over the contact area.

Under no circumstances shall the contact force exceed 0,5 N per contact.

Care shall be taken to avoid undue point pressure to the area of the UICC opposite to the contact area. Such pressure is potentially damaging to the components within the UICC.

5 Electrical specifications of the UICC - Terminal interface

The electrical specification in the present document covers the supply voltage range from 4,5 V to 5,5 V, 2,7 V to 3,3 V and 1,62 V to 1,98 V. For each state (V OH , V IH , V IL and V OL ), a positive current is defined as flowing out of the entity (terminal or UICC) in that state. Vpp shall not be supported by the 3 V and 1,8 V technology terminal or the 3 V and 1,8 V technology UICC.

There are two states for the UICC while the power supply is on:

The clock duty cycle shall be between 40 % and 60 % of the period during stable operation. A clock cycle is defined at 50 % of Vcc from rising to rising edge or falling to falling edge. When switching clock frequencies terminals shall ensure that no pulse is shorter than 80 ns which is 40 % of the shortest allowed period.

5.1 Class A operating conditions

5.1.1 Supply voltage Vcc (contact C1)

The terminal shall operate the UICC within the following limits.

Table 5.1: Electrical characteristics of Vcc under normal operating conditions
SymbolMinimumMaximumUnit
Vcc4,55,5V

The current consumption of the UICC shall not exceed the value given in the tables in clause 6.2.2 during the ATR (including activation and deactivation).

When the UICC is in idle state (see below) the current consumption of the card shall not exceed 200 µA at 1 MHz and 25°C. If clock stop mode is enabled, then the current consumption shall also not exceed 200 µA while the clock is stopped.

The terminal shall source the maximum current requirements defined above. It shall also be able to counteract spikes in the current consumption of the card up to a maximum charge of 40 nAs with no more than 400 ns duration and amplitude of at most 200 mA, ensuring that the supply voltage stays in the specified range.

NOTE: A possible solution would be to place a capacitor (e.g. 100 nF, ceramic) as close as possible to the contacting elements.

5.1.2 Reset (RST) (contact C2)

The terminal shall operate the UICC within the following limits.

Table 5.2: Electrical characteristics of RST under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µAVcc - 0,7Vcc (see note)V
V OLI OLmax = -200 µA0 (see note)0,6V
t R t FC out = C in = 30 pF400µs

NOTE: To allow for overshoot, the voltage on RST shall remain between -0,3 V and Vcc + 0,3 V during dynamic operation.

5.1.3 Programming voltage Vpp (contact C6)

The UICC shall not require any programming voltage on Vpp. The terminal need not provide contact C6. If the terminal provides contact C6, then, in the case the terminal supports an ID-1 UICC under class A operating conditions only, the same voltage shall be supplied on Vpp as on Vcc, while in the case of Plug-in UICC the terminal need not provide any voltage on C6. Contact C6 may be connected to Vcc in any terminal supporting only class A operating conditions but shall not be connected to ground.

5.1.4 Clock CLK (contact C3)

The terminal shall support 1 MHz to 5 MHz. The terminal shall supply the clock. No "internal clock" UICC shall be used.

The duty cycle shall be between 40 % and 60 % of the period during stable operation.

The terminal shall operate the UICC within the following limits.

Table 5.3: Electrical characteristics of CLK under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µA0,7 x VccVcc (see note)V
V OLI OLmax = -200 µA0 (see note)0,5V
t R t FC out = C in = 30 pF9 % of period with a maximum of 0,5 µs
NOTE:To allow for overshoot the voltage on CLK shall remain between -0,3 V and Vcc + 0,3 V during dynamic operation.

5.1.5 I/O (contact C7)

Table 5.4 defines the electrical characteristics of the I/O (contact C7). The values given in the table allow the derivation of the values of the pull-up resistor in the terminal and the impedance of the drivers and receivers in the terminal and UICC.

Table 5.4: Electrical characteristics of I/O under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V IHI IHmax = ±20 µA (see note 2)0,7 x VccVcc + 0,3V
V ILI ILmax = +1 mA-0,30,15 x VccV
V OH (see note 1)I OHmax = +20µA3,8Vcc (see note 3)V
V OLI OLmax = -1 mA0 (see note 3)0,4V
t R t FC out = C in = 30 pF1µs

NOTE 1: It is assumed that a pull-up resistor is used in the interface device (recommended value: 20 kΩ).

NOTE 2: During static conditions (idle state) only the positive value can apply. Under dynamic operating conditions (transmission) short-term voltage spikes on the I/O line may cause a current reversal.

NOTE 3: To allow for overshoot the voltage on I/O shall remain between -0,3 V and Vcc + 0,3 V during dynamic operation.

5.2 Class B operating conditions

5.2.1 Supply voltage Vcc (contact C1)

The terminal shall operate the UICC within the following limits.

Table 5.5: Electrical characteristics of Vcc under normal operating conditions
SymbolMinimumMaximumUnit
Vcc2,73,3V

When the UICC is in idle state, the current consumption shall not exceed 200 µA at 1 MHz at +25°C. When the UICC is in clock stop mode, the current consumption shall not exceed 100 µA at +25°C.

The terminal shall be capable of sourcing the maximum current as defined in table 6.4. It shall also be able to counteract spikes in the current consumption of the card up to a maximum charge of 12 nAs with no more than 400 ns duration and an amplitude of at most 60 mA, ensuring that the supply voltage stays in the specified range.

5.2.2 Reset (RST) (contact C2)

The terminal shall operate the UICC within the following limits.

Table 5.6: Electrical characteristics of RESET (RST) under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µA0,8 x VccVcc (see note)V
V OLI OLmax = -200 µA0 (see note)0,2 x VccV
t R t FC in = C out = 30 pF400µs
NOTE:To allow for overshoot the voltage on RST should remain between -0,3 V and Vcc + 0,3 V during dynamic operations.

5.2.3 Clock CLK (contact C3)

The terminal shall support 1 MHz to 5 MHz. The terminal shall supply the clock. No "internal clock" UICC shall be used.

The duty cycle shall be between 40 % and 60 % of the period during stable operation.

The terminal shall operate the UICC within the following limits.

Table 5.7: Electrical characteristics of Clock (CLK) under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µA0,7 x VccVcc (see note)V
V OLI OLmax = -20 µA0 (see note)0,2 x VccV
t R t FC in = C out = 30 pF50ns
NOTE:To allow for overshoot the voltage on CLK should remain between -0,3 V and Vcc + 0,3 V during dynamic operations.

5.2.4 I/O (contact C7)

Table 5.8 defines the electrical characteristics of the I/O (contact C7). The values given in the table allow the derivation of the values of the pull-up resistor in the terminal and the impedance of the drivers and receivers in the terminal and UICC.

Table 5.8: Electrical characteristics of I/O under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V IHI IHmax = ±20 µA (see note 2)0,7 x VccVcc + 0,3V
V ILI ILmax = +1 mA-0,30,2 x VccV
V OH (see note 1)I OHmax = +20 µA0,7 x VccVcc (see note 3)V
V OLI OLmax = -1mA0 (see note 3)0,4V
t R t FC in = C out = 30 pF1µs

NOTE 1: It is assumed that a pull-up resistor is used on the interface device (recommended value: 20 kΩ).

NOTE 2: During static conditions (idle state) only the positive value can apply. Under dynamic operating conditions (transmissions) short-term voltage spikes on the I/O line may cause a current reversal.

NOTE 3: To allow for overshoot the voltage on I/O shall remain between -0,3 V and Vcc + 0,3 V during dynamic operation.

5.3 Class C operating conditions

5.3.1 Supply voltage Vcc (contact C1)

The terminal shall operate the UICC within the following limits.

Table 5.9: Electrical characteristics of Vcc under normal operating conditions
SymbolMinimumMaximumUnit
Vcc1,621,98V

When the UICC is in idle state, the current consumption shall not exceed 200 µA at 1 MHz at +25°C. When the UICC is in clock stop mode, the current consumption shall not exceed 100 µA at +25°C.

The terminal shall be capable of sourcing the maximum current as defined in table 6.4. It shall also be able to counteract spikes in the current consumption of the card up to a maximum charge of 12 nAs with no more than 400 ns duration and an amplitude of at most 60 mA, ensuring that the supply voltage stays in the specified range.

5.3.2 Reset (RST) (contact C2)

The terminal shall operate the UICC within the following limits.

Table 5.10: Electrical characteristics of RESET (RST) under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µA0,8 x VccVcc (see note)V
V OLI OLmax = -200 µA0 (see note)0,2 x VccV
t R t FC in = C out = 30 pF400µs
NOTE:To allow for overshoot the voltage on RST should remain between -0,3 V and Vcc + 0,3 V during dynamic operations.

5.3.3 Clock CLK (contact C3)

The terminal shall support 1 MHz to 5 MHz. The terminal shall supply the clock. No "internal clock" UICC shall be used.

The duty cycle shall be between 40 % and 60 % of the period during stable operation.

The terminal shall operate the UICC within the following limits.

Table 5.11: Electrical characteristics of Clock (CLK) under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V OHI OHmax = +20 µA0,7 x VccVcc (see note)V
V OLI OLmax = -20 µA0 (see note)0,2 x VccV
t R t FC in = C out = 30 pF50ns
NOTE:To allow for overshoot the voltage on CLK should remain between -0,3 V and Vcc + 0,3 V during dynamic operations.

5.3.4 I/O (contact C7)

Table 5.12 defines the electrical characteristics of the I/O (contact C7). The values given in the table allow the derivation of the values of the pull-up resistor in the terminal and the impedance of the drivers and receivers in the terminal and UICC.

Table 5.12: Electrical characteristics of I/O under normal operating conditions
SymbolConditionsMinimumMaximumUnit
V IHI IHmax = ±20 µA (see note 2)0,7 x VccVcc + 0,3V
V ILI ILmax = +1 mA-0,30,2 x VccV
V OH (see note 1)I OHmax = +20 µA0,7 x VccVcc (see note 3)V
V OLI OLmax = -1mA0 (see note 3)0,3V
t R t FC in = C out = 30 pF1µs

NOTE 1: It is assumed that a pull-up resistor is used on the interface device (recommended value: 20 kΩ).

NOTE 2: During static conditions (idle state) only the positive value can apply. Under dynamic operating conditions (transmissions) short-term voltage spikes on the I/O line may cause a current reversal.

NOTE 3: To allow for overshoot the voltage on I/O shall remain between -0,3 V and Vcc + 0,3 V during dynamic operation.

6 Initial communication establishment procedures

6.1 UICC activation and deactivation

The terminal shall activate and deactivate the contacts of the UICC according to clause 4.4.2. During activation supply voltage switching, as defined in clause 6.2, shall take place prior to any further activity not related to the supply voltage switching.

6.2 Supply voltage switching

The terminal shall initially activate the UICC with the lowest voltage class available. If no ATR is received, the UICC shall be deactivated and activated with the next higher class, if supported by the terminal. If an ATR is received at the first applied voltage class, the contents of the ATR shall be analysed by the terminal. If the operating class used by the terminal is not supported by the UICC, the terminal shall deactivate the UICC and activate it with a supply voltage class indicated by the UICC. If the ATR is corrupted, the terminal shall perform the procedure at least 3 times using the same operating class before rejecting the UICC. In case of 3 consecutive corrupted ATRs, the terminal may activate the UICC with the next higher class. The terminal is restricted not to use but the next higher class in the retrial attempt in this case.

6.2.1 Supply voltage classes

The supply voltage class shall be indicated in the ATR by the UICC (TA i , i > 2).

Table 6.1: Supply voltage classes indicated in ATR
SymbolMinimumMaximumUnitClassEncoding (Binary)
Vcc4,55,5VAxx xxx1
Vcc2,73,3VBxx xx1x
Vcc1,621,98VCxx x1xx
VccRFURFUVDxx 1xxx
VccRFURFUVEx1 xxxx

NOTE: Class A and B values are according to ISO/IEC 7816-3 [11]. Class C and D are a further evolution of values specified in ISO/IEC 7816-3 [11]. It is possible to support a range of classes. The support shall be consecutive e.g. AB, BC. A combination like AC is not allowed.

6.2.2 Power consumption of the UICC during ATR

The maximum power consumption of the UICC during ATR is specified in tables 6.2a and 6.2b. The UICC power consumption during the ATR shall conform to the voltage class indicated in the ATR. If the UICC supports several supply voltage classes, each class shall conform to the corresponding maximum ATR power consumption, as specified in tables 6.2a and 6.2b. This is required because the terminal is not aware of the power consumption of the UICC until the ATR is received and an application is selected.

Table 6.2a: Power consumption that applies during ATR at maximum external clock frequency
SymbolVoltage ClassMaximumUnit
IccA10mA
IccB7,5mA
IccC5mA
IccDRFUmA
IccERFUmA
Table 6.2b: Power consumption that applies during ATR at 4 MHz
SymbolVoltage ClassMaximumUnit
IccB6mA
IccC4mA
IccDRFUmA
IccERFUmA
NOTE:4 MHz is the maximum clock speed specified in GSM for 3 V and below.

6.2.3 Application related electrical parameters

The power consumption of a UICC depends upon the operating conditions and the application it is running. The power consumption of the UICC is restricted to the values indicated in tables 6.2a and 6.2b until an application is selected. An application is considered selected when the access condition is successfully verified. If no access condition is required for the application, the application is considered selected when an application related command is executed within the selected application. Selecting the application and performing a STATUS command is not considered to be the execution of an application command for these purposes.

The terminal retrieves the application power consumption requirements by selecting the application. It then gets back the application power consumption indication in the response of the SELECT command. It may as well issue a STATUS command within the application and get this information in the response of the command.

Table 6.3: Maximum power consumption of the UICC during the UICC session
SymbolVoltage ClassMaximumUnit
IccA60mA
IccB50mA
IccC30mA
IccDRFUmA
IccERFUmA
NOTE: All values assume the maximum external clock.

Applications may specify their own maximum power consumption values, up to the maximum specified in table 6.3.

If an application does not indicate its consumption, the terminal shall assume the maximum application power consumption is as specified in table 6.4.

The minimum power supply that the terminal shall be able to supply to the UICC during application session at maximum clock speed is specified in table 6.4.

Table 6.4: Minimum power supply by the terminal during the UICC session
SymbolVoltage ClassMinimumUnit
IccA10mA
IccB10mA
IccC10mA
IccDRFUmA
IccERFUmA
NOTE: All values assume the maximum external clock.

6.3 Answer To Reset content

The ATR is the first string of bytes sent from the UICC to the terminal after a reset has been performed. The ATR is defined in ISO/IEC 7816-3 [11].

The terminal shall be able to receive interface characters for transmission protocols other than T=0 and T=1, historical bytes and a check byte, even if only T=0 and T=1 are used by the terminal.

T=15 global interface parameters shall be returned by the UICC.

Example ATRs are listed in annex D of the present document.

6.3.1 Coding of historical bytes

The historical bytes indicate to the external world how to use the card. The information carried by the historical bytes of the UICC follows ISO/IEC 7816-4 [12].

The category indicator is the first byte sent by the UICC. Its value shall be '80' which means that the historical bytes are coded in COMPACT-TLV data objects.

The first information sent by the card shall be the "card data service" data object. This data object is introduced by tag '31'. The second information sent by the card shall be the "card capabilities" data object. This data object is introduced by tag '73'. The other data objects are optional.

6.3.2 Speed enhancement

The terminal and the UICC shall at least support (F,D) = (512,8) and (512,16) in addition to (372,1), the default values. However, other values may also be supported. If the terminal requests PPS using values other than those above then the PPS procedure shall be initiated accordingly. The value of the transmission factors F and D is given by the UICC in TA 1 of the ATR.

6.4 PPS procedure

The terminal and the UICC shall support the PPS procedure in order to use transmission parameters other than the default values. The alternative parameters are indicated in the ATR. The interpretation of these parameters is according to ISO/IEC 7816-3 [11]. The terminal shall select a value within the range indicated by the UICC as defined in ISO/IEC 7816-3 [11].

6.5 Reset procedures

Two types of resets are specified by the present document. Cold reset is the first reset occurring after activation of the contacts. Warm reset is any reset which is not a cold reset.

6.5.1 Cold reset

The cold reset is performed according to of ISO/IEC 7816-3 [11] and the UICC shall enter the negotiable mode. After a cold reset, the security status shall be reset.

6.5.2 Warm reset

The warm reset is performed according to of ISO/IEC 7816-3 [11] and the UICC shall enter either the negotiable or the specific mode. If the UICC enters the specific mode, it shall present the same protocol and interface parameters (Fi, Di) as in the session prior to the warm reset. The UICC shall respond with an identical ATR after every warm reset issued within the same session regardless of what application was active. After a warm reset, the security status shall be reset.

6.5.3 Reaction to resets

A UICC complying with the present document shall either be a "Type 1 UICC" or a "Type 2 UICC".

Figure 6.1 illustrates how the respective types of a UICC react to the cold or warm reset.

Figure 6.1: Reaction to resets

See annex I for details.

6.6 Clock stop mode

The UICC shall support the clock stop procedure as defined in this clause. The clock stop mode is indicated in TA i (i > 2) in T=15 in the ATR, see ISO/IEC 7816-3 [11]. For a UICC supporting only class A operating conditions, clock stop mode "not allowed" may be indicated, see clause 6.3. If the UICC supports any other operating conditions even together with class A, clock stop mode shall be supported and the indication shall be set accordingly. The terminal shall follow this indication independently of operating conditions indicated by the card.

The terminal shall wait at least 1 860 clock cycles after having received the last character, including the guard time (2 etu), of the response before it switches off the clock (if it is allowed to do so). It shall wait at least 744 clock cycles before it sends the first command after having started the clock.

6.7 Bit/character duration and sampling time

The bit/character duration and sampling time specified in ISO/IEC 7816-3 [11], clause 6.3.2 are valid for all communications.

6.8 Error handling

Following receipt of an ATR, which is not in accordance with the present document, e.g. because of forbidden ATR characters or too few bytes being transmitted, the terminal shall perform a Reset. The terminal shall not reject the UICC until at least three consecutive wrong ATRs are received.

During the transmission of the ATR, the error detection and character repetition procedure specified in ISO/IEC 7816-3 [11], clause 6.3.3, is optional for the terminal. For the subsequent transmission on the basis of T=0 this procedure is mandatory for the terminal.

For the UICC the error detection and character repetition procedure is mandatory for all communications using T=0.

6.9 Compatibility

Terminals operating under class A operating conditions only and that are compliant to the electrical parameters defined in clause 5.1 shall operate with a 3 V Technology smart card according to the present document.

For compatibility with existing terminals, UICCs that are used in applications where the supply voltage class indication is based on the STATUS response procedure (see clause 6.2.3) shall support this procedure in addition to the supply voltage class indication in the ATR as defined in the present document.

In case the UICC does not support any supply voltage indication, the UICC shall be treated as a 5 V only card by the terminal.

7 Transmission protocols

This clause defines the transmission protocols used to exchange data between the terminal and the UICC. The structure and processing of commands initiated by the terminal for transmission control and for specific control in asynchronous half duplex transmission protocols will be described.

Two different protocols are defined, the character based protocol T=0 and the block based protocol T=1.

Both protocols T=0 and T=1 are mandatory for the terminal. The UICC shall support either T=0 or T=1 or both protocols. The protocols shall be supported as specified in the present document.

The protocol starts after either the answer to reset or a successful PPS exchange. Other parameters provided in the ATR and relevant to a specific protocol are defined in the respective parts of this clause.

The protocol applies a layering principle of the OSI-reference model. Four layers are considered. The layers are:

Figure 7.1: Layers

7.1 Physical layer

Both protocols T=0 and T=1 shall use the physical layer and character frame as defined in clause 7.2.1.

7.2 Data link layer

This clause describes the timing, specific options and error handling for the protocols T=0 and T=1.

7.2.1 Character frame

A character that is transmitted over the I/O line is embedded in a character frame.

Before the transmission of a character, the I/O line shall be in state H. Depending upon the convention used, the logical '1' in a character is either represented by state H on the I/O line, direct convention, or state L on the I/O line, inverse convention.

A character consists of 10 consecutive bits (see figure 7.2):

The parity bit is set, in a way, that there is an even number of bits set to '1' including the parity bit in the character frame.

The time origin is fixed as the mean between the last observation of state H and the first observation of state L. The receiver shall confirm the existence of a start bit before 0,7 etu (receiver time). Then the subsequent bits shall be received at intervals of (n + 0,5 ± 0,2) etu (n being the rank of the bit). The start bit is bit 1.

Within a character, the time from the leading edge of the start bit to the trailing edge of the nth bit is (n ± 0,2) etu.

The interval between the leading edges of the start bits of two consecutive characters is comprised of the character duration (10 ± 0,2) etu, plus a guardtime. Under error free transmission, during the guardtime both the UICC and the terminal shall be in reception mode (I/O line in state H).

Figure 7.2: Character frame

The data shall always be passed over the I/O line with the most significant byte first. The order of bits within a byte (that is, whether the least significant or most significant bit is transferred first) is specified in character TS returned in the answer to reset (see ISO/IEC 7816-3 [11]).

7.2.2 Transmission protocol T=0

The T=0 is a half-duplex asynchronous character based transmission protocol.

All commands using the protocol T=0 are initiated from the terminal by sending a five byte header, which informs the UICC what to do. The terminal will always act as master and the UICC as a slave. The direction of the transmission is assumed to be known to both the UICC and the terminal.

7.2.2.1 Timing and specific options for characters in T=0

The minimum interval between the leading edge of the start bits of two consecutive characters shall be at least 12 etu.

The maximum interval between the start leading edge of any character sent by the UICC and the start leading edge of the previous character sent either by the UICC or the terminal is the WWT. The value of the WWT shall not exceed 960 × WI × Fi/f. WI is an integer received in the specific interface byte TC2. If no TC2 is available, default value of WI is 10. The clock rate conversion factor, Fi, and the baud rate conversion factor Di, may be indicated in TA1. If TA1 is absent the default values 372 and 1 respectively are used.

If the WWT is exceeded, the terminal shall initiate a deactivation within 960 etu.

7.2.2.2 Command header

A command is always initiated by the terminal which sends an instruction to the UICC in the form of a five byte-header called the command header. The command header is comprised of five consecutive bytes, CLA, INS, P1, P2, and P3.

These bytes together with any data to be sent with the command form the Command Transport Protocol Data Unit (C-TPDU) for T=0. The mapping of the C-APDU onto the C-TPDU is described in clause 7.3.

The terminal transmits the header to the UICC and waits for a procedure byte.

7.2.2.3 Command processing

When the UICC has received the command header, a response containing a procedure byte shall be sent to the terminal. Both the terminal and the UICC shall be able to keep track of the direction of the data flow and who has the access to the I/O-line.

7.2.2.3.1 Procedure bytes

The procedure byte indicates to the terminal what action it shall take next.

Procedure bytes are used to keep up the communication between the terminal and the UICC. They shall not be transmitted to the application layer.

The coding of the procedure byte and the action that shall be taken by the terminal is shown in table 7.1.

Table 7.1: Procedure byte coding
ByteValueAction
ACKEqual to INS byteAll remaining data bytes shall be transferred by the terminal, or the terminal shall be ready to receive all remaining data bytes from the UICC.
Equal to complement of INS byte _______ (INS)The next data byte shall be transferred by the terminal, or the terminal shall be ready to receive the next data byte from the UICC.
NULL'60'The NULL-byte requests no further data transfer and the terminal shall only wait for a character conveying a procedure byte. This behaviour provides additional work waiting time as defined in this clause.
SW1'61'The terminal shall wait for a second procedure byte then send a GET RESPONSE command header to the UICC with a maximum length of 'XX', where 'XX' is the value of the second procedure byte (SW2).
'6C'The terminal shall wait for a second procedure byte then immediately repeat the previous command header to the UICC using a length of 'XX', where 'XX' is the value of the second procedure byte (SW2).

After these actions, the terminal shall wait for a further procedure byte or status word.

7.2.2.3.2 Status bytes

The status bytes SW1 SW2 form an end sequence indicating the status of the UICC at the end of a command. A normal ending of a command is indicating by SW1 SW2 = '90 00'.

Table 7.2: Status byte coding
ByteValueAction
SW1'6X' or '9X' (except '60', '61', and '6C')The terminal shall wait for a further status word (SW2). The terminal shall return the status words (together with any appropriate data) to the application layer and shall wait for another C-APDU.

7.2.2.4 Error detection and correction

The error detection and correction procedure is mandatory for T=0 protocol except for the terminal during the ATR-procedure.

An error, from the receiver's point of view, is defined by an incorrect parity. The error is indicated on the I/O line, which is set to state L at (10,5 ± 0,2) etu after the leading edge of the start bit for the character. The I/O line shall be in state L for a maximum of 2 etu and a minimum of 1 etu. The transmitter shall check the I/O line for parity error indication at (11 ± 0,2) etu starting from the leading edge of the start bit, in the character being transmitted.

If the UICC or terminal as receiver detects a parity error in a character just received, it shall set the I/O line to state L at (10,5 ± 0,2) etu after the leading edge of the start bit for the character for a maximum of 2 etu to indicate the error to the sender - see figure 7.2.

If the transmitter detects an error indication at (11 ± 0,2) etu starting from the leading edge of the start bit, in the character being transmitted, the character shall be sent again after a minimum delay of 2 etu.

7.2.3 Transmission protocol T=1

The T=1 protocol is a half-duplex asynchronous block based transmission protocol. The protocol may be initiated as follows:

The communication starts with a block sent by the terminal to the UICC. The right to send a block keeps alternating between the terminal and the UICC. A block is the smallest data unit, which can be sent and can contain either application data or transmission control data. A check of the received data might be performed before further processing of the received data.

7.2.3.1 Timing and specific options for blocks sent with T=1

This clause defines options regarding timing, information file sizes and error detection parameters for blocks sent with T=1.

7.2.3.1.1 Information field size

The IFSC defines the maximum length of the information field of blocks that can be received by the UICC. The default value of the IFSC is 32 bytes another value may be indicated in TA3 of the ATR.

The IFSD defines the maximum length of the information field of blocks that the terminal can receive. IFSD has a default value of 32 bytes and may be adjusted during the card session. The maximum value of the IFSD is 254 bytes.

7.2.3.1.2 Character waiting integer

CWI is used to calculate CWT and shall be in the range from 0 to 5. The value is set in bits b4 to b1 in TB3.

7.2.3.1.3 Character waiting time

CWT is defined as the maximum delay between the leading edges of two consecutive characters in the block.

Figure 7.3: Character waiting time

The value of CWT may be calculated from the following equation: CWT = (11 + 2 CWI ) etu.

7.2.3.1.4 Block waiting time

BWT is defined as the maximum delay between the leading edge of the last character of the block received by the card and the leading edge of the first character of the next block sent by the card.

Figure 7.4: Block waiting time

BWT is used to detect an unresponsive card.

7.2.3.1.5 Block guard time

BGT is defined as the minimum delay between the leading edge of two consecutive characters sent in opposite directions. The value of BGT shall be 22 etu.

Figure 7.5: Block guard time

The delay between the last character of a block received by the UICC and the first character of the next block sent from the UICC shall be in the interval:

7.2.3.1.6 Waiting time extension

WTX is a parameter used to ask for more time to process a command.

7.2.3.1.7 Error detection code

The parameter TCi in the ATR is used to define which error detection code to use. LRC shall be used (b1=0). All other bits in TCi are RFU and shall be set to 0.

7.2.3.2 Block frame structure

The protocol consists of blocks, which are transmitted between the terminal and the UICC. Each block has the following structure.

Table 7.3: Block frame structure
Prologue fieldInformation fieldEpilogue field
NADPCBLENINFEDC
1 byte1 byte1 byte0 byte to 254 bytes1 byte

The prologue field and the epilogue field are mandatory. The Information field is optional.

7.2.3.2.1 Prologue field

The prologue field is divided into the following three mandatory fields:

7.2.3.2.1.1 Node address byte

The NAD-byte identifies the source and the intended destination of the block. The NAD may also be used to distinguish between different logical connections if they coexist as well as to provide Vpp state control (bit b8 and b4). Since b8 and b4 are not used, they shall be coded as '0'. Below is the structure of the NAD-byte.

Table 7.4: Node address byte
b8b7b6b5b4b3b2b1
UnusedDADUnusedSAD

In the first block sent from the terminal, a logical connection is set up based on the addresses in SAD and DAD. Subsequent blocks with an NAD containing the same pair of addresses are associated with the same logical connection.

Only the default value SAD = DAD = 0 shall be supported. All other combinations are RFU.

7.2.3.2.1.2 Protocol Control Byte

All information needed to control the transmission is transferred in the protocol control byte PCB. The coding of the PCB-byte specifies the type of block. In the T=1 protocol the following three different types of blocks are supported:

The tables below present the coding of the PCB-byte for each block-type, starting with the I-block.

Table 7.5: Coding of PCB for an I-block
b8b7b6b5b4b3b2b1
0Sequence number, N(S)Chaining, more-data bit, MRFU
Table 7.6: Coding of PCB for an R-block
b8b7b6b5b4b3b2b1
100Sequence number N(R)See table 7.5
Table 7.7: Bit b4 to b1 in the PCB-byte for the R-block
b4b3b2b1ValueMeaning
0000'0'Error free
0001'1'EDC and/or parity error
0010'2'Other errors
XXXX'X'Other values are RFU
Table 7.8: Coding of PCB for an S-block
b8b7b6b5b4b3b2b1
11XSee table 7.9
Table 7.9: Bits b5 to b1 of PCB for an S-block
b5b4b3b2b1ValueMeaning
00000'0'Resynchronization
00001'1'Information field
00010'2'Abortion
00011'3'Extension of BWT
00100'4'Error on VPP State (see note)
XXXXX'X'Other values are RFU
NOTE: Not used by UICCs and terminals conforming to the present document.

The coding of b6 indicates whether it is a request (b6 = 0) or a response (b6 = 1).

7.2.3.2.1.3 Length

The length byte codes the number of bytes in the Information field of the block. The number of bytes in the information field may vary in the range from 0 byte to 254 bytes, depending on the type of block.

The value LEN = '00' indicates that the information field is absent and the value 'FF' is RFU.

7.2.3.2.1.4 Information field

The information field, INF, is optional and it depends on the type of the block what the field will be used for.

Table 7.10: Information field
Type of blockINF used for
I-blockTransfer command and response APDUs.
R-blockNot used.
S-blockTransfers non application related information: · INF shall be present (single byte) to adjust IFS with WTX; · INF shall be absent to signal error on VPP, or managing chain abortion or resynchronization.
7.2.3.2.2 Epilogue field

The epilogue field contains the Error Detection Code-byte (EDC), which transfers the error detection code of the transmitted block.

The LRC as defined in ISO/IEC 7816-3 [11] shall be used.

7.2.3.2.3 Block notations
7.2.3.2.3.1

I-block

The I-blocks are denoted as follows: I(N(S), M) where:

7.2.3.2.3.2 R-block

The R-block is denoted as follows: R(N(R)), where:

7.2.3.2.3.3 S-block

S-blocks are always used in pairs. An S(request) is always followed by an S(response) block. The S-blocks are denoted as follows:

7.2.3.3 Error free operation

This clause describes the rules for error free operation with T=1.

7.2.3.4 Error handling for T=1

This clause contains a description of the rules used to control the error handling for the T=1 protocol.

The block component of the data link layer shall be able to handle errors like:

Resynchronization of the protocol may be attempted at three consecutive levels. If one level is unsuccessful, then the next level is tried.

7.2.3.4.1 Protocol initialization

After an ATR due to a Warm reset or successful PPS procedure, the communication between the terminal and the UICC can be initiated. But if the terminal fails to receive an error-free block, in the beginning of the protocol, a maximum of two more successive attempts to receive the block is allowed before resetting or a deactivation of the card takes place.

If the response on the first block sent by the terminal is not sent within BWT, the terminal shall send an R(0).

When the protocol has been initiated and the first block received by the UICC is invalid, the UICC responses with an R(0).

If the terminal fails to receive an error-free block during a card-session, a maximum of two further attempts is allowed before an S(RESYNCH request) is sent.

7.2.3.4.2 Block dependent errors

When an I-block has been sent and a BWT time-out occurs or an invalid block has been received (with the terminal), an R-block is sent, which requests with its N(R) for the expected I-block with N(S) = N(R).

When an R-block was sent and an invalid block is received or BWT time-out, the R-block shall be resent.

When an S(… request) has been sent and either a BWT time-out occurs (with the terminal) or the received response is not an S(… response), the S(… request) shall be resent. But if an S(… response) has been sent and either an invalid block is received or a BWT time-out occurs (with the terminal), an R-block shall be sent. The terminal shall not send an S(IFS request) before the R-block acknowledging a reception of the previous I-block sent by the card.

When the UICC sends an S(IFS request) and receives an invalid block, the S(IFS request) shall be resent maximum one extra time to receive an S(IFS response). After the second failure to receive an S(IFS response), the UICC shall stay in reception mode.

7.2.3.5 Chaining

Chaining allows the terminal or the UICC to transfer information, which is longer than IFSC or IFSD. If information longer than IFSC or IFSD is transferred, the information should be divided into pieces, each has a length ≤ IFSC or IFSD. Each piece should be sent in an I-block using the chaining function.

The value of the M-bit in the PCB byte of the I-block controls the chaining function according to:

When a receiver receives a more-data I-block, an R(N(R)) shall be sent. N(R) = N(S) of the expected I-block. At least one chained block should follow.

A physical error, e.g. buffer overrun, in the UICC can cause an error in a chaining process. To abort a chain an S(ABORT request) can be sent by either the sender or the receiver. The request shall be answered with an S(ABORT response). When the S(ABORT response) has been received an R-block may be sent to either the terminal or the UICC to give back the right to send to either.

7.2.3.5.1 Rules for chaining

For reasons of efficiency, it is not recommended to send empty I-blocks.

7.3 Transport layer

This clause describes how the APDU are transported between the terminal and the UICC. For definition of the cases for Data in APDUs see clause 7.4.

7.3.1 Transportation of an APDU using T=0

This clause describes the mapping of C-APDUs and R-APDUs for T=0 protocol, the APDU exchange and the use of the GET RESPONSE command for case 2 and case 4.

7.3.1.1 Mapping of APDUs to TPDUs

The mapping of the C-APDU onto the T=0 command header is dependent upon the case of the command. The mapping of the data (if present) and status returned by the UICC onto the R-APDU is dependent upon the length of the data returned.

Procedure bytes '61XX' and '6CXX' are returned by the UICC to control exchanges between the transport layer of the terminal and the UICC, and should never be returned to the application layer of the terminal. Command processing in the UICC is not complete if it has returned procedure bytes '61XX' or '6CXX'.

Normal status on completion of processing a command is indicated if the UICC returns status words '9000' to the transport layer of the terminal. The transport layer of the terminal shall discontinue processing of a command (i.e. pass the R-APDU to the application layer and wait for a further C-APDU from the application layer) on receipt of any status words (but not on receipt of procedure bytes '61xx' and '6Cxx') from the UICC. For case 4 commands only, immediately following successful transmission of command data to the UICC, the transport layer of the terminal shall continue processing the command if warning status bytes ('62xx' or '63xx') or application related status bytes ('9xxx' except '9000') are received.

The following descriptions of the mapping of data and status returned by the UICC onto the R-APDU are for information, and apply only after the UICC has completed processing of the command, successfully or otherwise, and all data (if present) has been returned by the UICC under the control of '61XX' and '6CXX' procedure bytes. Detailed use of the INS, INS, and '60' procedure bytes is not described.

The status returned by the UICC shall relate to the most recently received command. Where a GET RESPONSE command is used to complete the processing of a case 2 or case 4 command, any status returned by the UICC after receipt of the GET RESPONSE command shall relate to GET RESPONSE command, not to the case 2 or case 4 command which it completes.

7.3.1.1.1 Case 1

The C-APDU is mapped onto the C-TPDU by assigning the value '00' to the body part (P3 = '00').

Figure 7.6
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2
Transport Layer (C-TPDU)CLA INS P1 P2 P3 = '00'barb4rightCommand Processing
Transport Layer (R-TPDU)SW1||SW2barb4leftSW1||SW2
Application Layer (R-APDU)SW1||SW2

The flow of the exchange is as follows:

  1. The transport layer of the terminal shall send the T=0 command header to the UICC.
  2. On receipt of the command header the UICC, under normal or abnormal processing, shall return status to the transport layer of the terminal.

The UICC shall analyse the T=0 command header to determine whether it is processing a case 1 command or a case 2 command requesting all data up to the maximum length available.

  1. On receipt of status from the UICC, the transport layer of the terminal shall discontinue processing of the command.

See annex C for details of the exchanges between the transport layer of the terminal and the UICC.

The status words returned to the transport layer of the terminal from the UICC after completion of processing of the command are mapped onto the mandatory trailer of the R-APDU without change.

7.3.1.1.2 Case 2

The C-APDU is mapped onto the C-TPDU without any change.

Figure 7.7

The flow of the exchange is as follows:

  1. The transport layer of the terminal shall send the T=0 command header to the UICC.
  2. On receipt of the command header the UICC:
  3. under normal processing shall return data and status to the transport layer of the terminal. The UICC shall use procedure bytes '6Cxx' (and if required, procedure bytes '61xx') to control the return of data (see below); or
  4. under abnormal processing shall return status only to the transport layer of the terminal.
  5. On receipt of the data (if present) and status from the UICC, the transport layer of the terminal shall discontinue processing the command.

See annex C for details of the exchanges between the transport layer of the terminal and the UICC, including use of the '61XX' and '6CXX' procedure bytes.

The R-TPDU is mapped onto the R-APDU without any change.

The data (if present) and status returned to the transport layer of the terminal from the UICC after completion of processing of the command are mapped onto the R-APDU as follows:

7.3.1.1.3 Case 3

The C-APDU is mapped onto the C-TPDU without any change. Lc is a value between 1 and 255.

Figure 7.8
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2 Lc [Lc bytes of DATA]
Transport Layer (C-TPDU)CLA INS P1 P2 P3=Lc [Lc bytes of DATA]barb4rightCommand Processing
Transport Layer (R-TPDU)SW1||SW2barb4leftSW1||SW2
Application Layer (R-APDU)SW1||SW2

The flow of the exchange is as follows:

  1. The transport layer of the terminal shall send the T=0 command header to the UICC.
  2. On receipt of the command header, if the UICC:
  3. returns a procedure byte, the transport layer of the terminal shall send the data portion of the conditional body of the C-APDU to the UICC under the control of procedure bytes returned by the UICC; or
  4. returns status, the transport layer of the terminal shall discontinue processing of the command.
  5. If processing was not discontinued in step 2(b), the UICC shall return status following receipt of the conditional body of the C-APDU and completion of processing the command.
  6. On receipt of status from the UICC, the transport layer of the terminal shall discontinue processing the command.

See annex C for details of the exchanges between the transport layer of the terminal and the UICC.

The status words returned to the transport layer of the terminal from the UICC after completion of processing of the command, or the status words returned by the UICC that caused the transport layer of the terminal to discontinue processing of the command, are mapped onto the R-APDU without change.

7.3.1.1.4 Case 4

The C-APDU is mapped onto the C-TPDU by cutting off the last byte (Le) of the body.

Figure 7.9
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2 Lc [Lc bytes of DATA] Le
Transport Layer (C-TPDU)CLA INS P1 P2 P3=Lc [Lc bytes of DATA]barb4rightCommand Processing
SW1||SW2 (61XX, XX=Luicc)barb4leftSW1||SW2 (61XX)
Get Response, P3 = Luiccbarb4rightSupply of Response Data
Transport Layer (R-TPDU)Luicc byte of DATA||SW1||SW2barb4leftLuicc byte of DATA||SW1||SW2
Application Layer (R-APDU)Luicc byte of DATA||SW1||SW2

The flow of the exchange is as follows:

  1. The transport layer of the terminal shall send the T=0 command header to the UICC.
  2. On receipt of the command header, if the UICC:
  3. returns a procedure byte, the transport layer of the terminal shall send the data portion of the conditional body of the C-APDU to the UICC under the control of procedure bytes returned by the UICC; or
  4. returns status, the transport layer of the terminal shall discontinue processing of the command.
  5. If processing was not discontinued in step 2(b), following receipt of the conditional body of the C-APDU, the UICC:
  6. under normal processing, shall return procedure bytes '61xx' to the transport layer of the terminal requesting the transport layer of the terminal to issue a GET RESPONSE command to retrieve the data from the UICC; or
  7. under abnormal processing, shall return status only to the transport layer of the terminal.
  8. On receipt of the procedure bytes or status returned in step 3, if the UICC:
  9. returned '61xx' procedure bytes as in step 3(a), the transport layer of the terminal shall send a GET RESPONSE command header to the UICC with P3 set to a value less than or equal to the value contained in the 'xx' byte of '61xx' procedure bytes; or
  10. returned status as in step 3(b) that indicates a warning ('62xx' or '63xx'), or which is application related ('9xxx' but not '9000'), the transport layer of the terminal shall send a GET RESPONSE command with Le = '00'; or
  11. returned status as in step 3(b) other than that described in step 4(b), the transport layer of the terminal shall discontinue processing of the command.
  12. If processing was not discontinued in step 4(c), the GET RESPONSE command shall be processed according to the rules for case 2 commands.

The first R-TPDU from the UICC indicates that the UICC performed the command correct and that the UICC has more data of length Luicc bytes to transfer. The first R-TPDU is mapped without any changes onto the R-APDU.

See annex C for details of the exchanges between the transport layer of the terminal and the UICC, including use of the '61XX' and '6CXX' procedure bytes.

7.3.1.1.5 Use of procedure bytes '61xx' and '6Cxx'

The UICC returns procedure bytes '61xx 'and '6Cxx' to the transport layer of the terminal to indicate to it the manner in which it should retrieve the data requested by the command currently being processed. These procedure bytes are only used when processing case 2 and 4 commands using T=0.

Procedure bytes '61xx' instruct the transport layer of the terminal to issue a GET RESPONSE command to the UICC. P3 of the GET RESPONSE command header is set to 'xx'.

Procedure bytes '6Cxx' instruct the transport layer of the terminal to immediately resend the previous command header setting P3 = 'xx'.

Usage of these procedure bytes during error free processing with case 2 and 4 commands is as follows. In the case of an error, the UICC may return status indicating error or warning conditions instead of the '61xx' or '6Cxx' response.

7.3.1.1.5.1 Case 2 commands
  1. If the UICC receives a case 2 command header and Le = '00' (with Luicc < 256 bytes) or Le > Luicc, it shall return:
  2. procedure bytes '6C Luicc' instructing the transport layer of the terminal to immediately resend the command header with P3 = Luicc; or
  1. status indicating a warning or error condition (but not SW1 SW2 = '90 00').
  2. If the UICC receives a case 2 command header and Le = '00' (with Luicc = 256 bytes) or Le = Luicc, it shall return:
  3. data of length Le (= Luicc) under the control of the INS, INS, or '60' procedure bytes followed by the associated status; or
  4. procedure bytes '61xx' instructing the transport layer of the terminal to issue a GET RESPONSE command with a maximum length of 'xx', 'xx' being less than Luicc (this could happen if the card buffer size is smaller than Luicc); or
  5. status indicating a warning or error condition (but not SW1 SW2 = '90 00').
  6. If the UICC receives a case 2 command header and Le < Luicc it shall return:
  7. data of length Le under the control of the INS, INS, or '60' procedure bytes followed by procedure bytes '61xx' instructing the transport layer of the terminal to issue a GET RESPONSE command with a maximum length of 'xx'; or
  8. status indicating a warning or error condition (but not SW1 SW2 = '90 00').
7.3.1.1.5.2 Case 4 commands

If the UICC receives a case 4 command, after processing the data sent with the C-APDU, it shall return:

  1. procedure bytes '61 xx' instructing the transport layer of the terminal to issue a GET RESPONSE command with a maximum length of 'xx'; or
  2. status indicating a warning or error condition (but not SW1 SW2 = '90 00').

The GET RESPONSE command so issued is then treated as described for case 2 commands.

7.3.2 Transportation of a APDU using T=1

A C-APDU is sent from the application layer of the terminal to the transport layer of the terminal. The transport layer maps the C-APDU onto the INF of an I-block without change. The I-block is sent to the UICC. The Response data (if present) and the status are returned from the UICC to the transport layer of the terminal in the INF of an I-block. If the UICC returns a status which indicates:

then it shall also return data (if available) associated with the processing of the command. No data shall be returned with any other status.

The contents of the INF of the I-block are mapped onto the R-APDU without change and returned to the application layer of the terminal. The transportation of APDU messages with T=1 is mapped to the information of an I-block according to the four different cases described below. Each case is described in detail in clauses 7.3.2.1 to 7.3.2.4.

7.3.2.1 Case 1

C-APDU is mapped to the INF of the I-block without any changes:

Figure 7.10
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2
Transport Layer (C-TPDU, INF)CLA INS P1 P2barb4rightCommand Processing
Transport Layer (R-TPDU, INF)SW1||SW2barb4leftSW1||SW2
Application Layer (R-APDU)SW1||SW2

The response received from the INF in the I-block is mapped unchanged to the R-APDU.

7.3.2.2 Case 2

The C-APDU is mapped to the INF of an I-block without any changes.

Figure 7.11

The R-APDU consists of either the INF of the I-block or the concatenation of the INF of successive I-blocks all received in the same response, which all shall be chained.

7.3.2.3 Case 3

The C-APDU is mapped without any changes to either an INF or is concatenated onto several successive I-blocks, which all shall be chained.

Figure 7.12
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2 Lc [Lc bytes of DATA]
Transport Layer (C-TPDU, INF)CLA INS P1 P2 Lc [Lc bytes of DATA]barb4rightCommand Processing
Transport Layer (R-TPDU, INF)SW1||SW2barb4leftSW1||SW2
Application Layer (R-APDU)SW1||SW2

The INF of the I-block is mapped to the R-APDU without any changes.

7.3.2.4 Case 4

The C-APDU is mapped without any changes to either an INF or is concatenated onto several successive I-blocks, which all shall be chained.

Figure 7.13
TerminalUICC
Application Layer (C-APDU)CLA INS P1 P2 Lc [Lc bytes of DATA] Le
Transport Layer (C-TPDU, INF)CLA INS P1 P2 Lc [Lc bytes of DATA] Lebarb4right Command Processing
Transport Layer (R-TPDU, INF)Lr bytes of DATA||SW1||SW2barb4left Lr bytes of DATA||SW1||SW2
Application Layer (R-APDU)Lr bytes of DATA||SW1||SW2

The response consists of either the INF of an I-block received in the response or the concatenation of INF of successive I-blocks in response, which all shall be chained.

7.4 Application layer

The application protocol consists of an ordered set of exchanges between the application layer and the transport layer of the terminal. Application protocols are defined in subsequent parts of the present document.

Each step in an application layer exchange consists of a command-response pair, where the application layer of the terminal sends a command to the UICC via the transport layer of the terminal, and the UICC processes it and sends a response to application layer of terminal using the transport layer of the UICC and the transport layer of terminal. Each specific command (C-APDU) has a specific response (R-APDU). The commands and responses are called command messages and response messages. The structure of the C-APDU can be found in clause 10.2. The structure of the R-APDU can be found in clause 10.3.

Both command and response messages may contain data. Thus, four cases shall be managed by the transmission protocols via the transport layer, as shown in table 7.11.

Table 7.11: Definition of cases for data in APDUs
CaseCommand dataResponse data
1AbsentAbsent
2AbsentPresent
3PresentAbsent
4PresentPresent

7.4.1 Exchange of APDUs

Figure 7.14 shows the principle exchange of command/response pairs.

Terminal
C-APDU
C-APDU

barb4right

barb4left

barb4right

barb4left

Figure 7.14

7.4.2 CAT layer

The CAT layer uses application status words to indicate:

7.4.2.1 Proactive command

Where the status word SW1-SW2 is equal to '9000', the card can reply '91XX' to indicate that a proactive command is pending. The terminal uses the FETCH C-APDU to get the pending proactive command. The terminal sends to the UICC the response of the proactive command execution with the TERMINAL RESPONSE C-APDU.

The mechanism, described hereafter for a case 4 C-APDU, is independent from the transport protocol.

UICC

R-APDU

R-APDU

Figure 7.15

7.4.2.2 ENVELOPE Commands

The ENVELOPE C-APDU is used to transmit data to the CAT. For some BER-TLV (e.g. SMS-PP Data Download) contained in the body of this command, the card may send back data to be transmitted by the terminal on the acknowledgement channel (e.g. RP-ACK) or on the error channel (e.g. RP-ERROR). The BER-TLV objects are defined in TS 102 223 [4] and in access technology dependent specifications.

This command is case 4 and is described hereafter for the two options.

Case 4: positive acknowledgement

Figure 7.16a

The terminal shall consider the data field received as a positive acknowledgement and use the normal acknowledgement channel (e.g. RP-ACK) when the status word present in the R-APDU is '9000'.

Terminal
CLA INS='C2' P1 P2 Lc [Lc DATA] Le=00
Luicc DATA '63'||SW2='XX'
||SW1='62'or
Figure 7.16b

The terminal shall consider the data field received as a negative acknowledgement and use the error acknowledgement channel (e.g. RP-ERROR), when the status word present in the R-APDU is either '62XX' or '63XX'.

8 Application and file structure

This clause describes the application and logical structure for the UICC.

8.1 UICC application structure

An example of organization of applications in the UICC is listed in figure 8.1.

Figure 8.1: Example of an application structure

The present document does not impose any restrictions on the location of applications. All applications are uniquely identified by application identifiers that are obtained from EF DIR . These application identifiers are used to select the application.

EF DIR, EF PL and EF ICCID are all mandatory and reside directly under the Master File. See clause 13 of the present document for details.

DF TELECOM is optional. If present it resides under the MF and use the reserved FID '7F 10'. DF TELECOM contains application independent information.

8.2 File types

This clause defines the file types that apply to applications complying to the present document.

8.2.1 Dedicated files

A Dedicated File (DF) allows for a functional grouping of files. It can be the parent of DFs and/or EFs. DFs are referenced by file identifiers.

An Application DF (ADF) is a particular DF that contains all the DFs and EFs of an application.

8.2.2 Elementary files

8.2.2.1 Transparent EF

An EF with a transparent structure consists of a sequence of bytes. When reading or updating, the sequence of bytes to be acted upon is referenced by a relative address (offset), which indicates the start position (in bytes), and the number of bytes to be read or updated. The first byte of a transparent EF has the relative address '00 00'. The data length is indicated in the SELECT response of the EF.

8.2.2.2 Linear fixed EF

An EF with linear fixed structure consists of a sequence of records all having the same (fixed) length. The first record is record number 1. The length of a record as well as this value multiplied by the number of records are indicated in the SELECT response of the EF.

Figure 8.2: Structure of a linear fixed file
Record 1
Record 2
: :
Record n

There are several methods to access records within an EF of this type:

If an action following selection of a record is aborted (e.g. due to an unsuccessful execution of a command), then the record pointer shall remain set at the record at which it was set prior to the action.

It is not possible, at present, to have more than 254 records in a file of this type, and each record cannot be greater than 255 bytes.

8.2.2.3 Cyclic EF

Cyclic files are used for storing records in chronological order. When all records have been used for storage, then the next storage of data shall overwrite the oldest information.

An EF with a cyclic structure consists of a fixed number of records with the same (fixed) length. In this file structure there is a link between the last record (n) and the first record. When the record pointer is set to the last record n, then the next record is record 1. Similarly, when the record pointer is set to record 1, then the previous record is record n. The last updated record containing the newest data is record number 1, and the oldest data is held in record number n.

Figure 8.3: Structure of a cyclic file

For update operations only PREVIOUS record shall be used. For reading operations, the methods of addressing are Next, Previous, Current and Record Number.

If an action following selection of a record is aborted (e.g. due to an unsuccessful execution of a command), then the record pointer shall remain set at the record at which it was set prior to the action.

It is not possible, at present, to have more than 254 records in a file of this type, and each record cannot be greater than 254 bytes.

8.3 File referencing

A File Identifier (FID) is used to address or identify a specific file. The FID consists of two bytes and shall be coded in hexadecimal notation.

FIDs shall be subject to the following conditions:

A path is a concatenation of FIDs. The path starts from MF or the current DF, and ends with the identifier of the file itself. The order of the FIDs is always in the direction from father to child.

A Short File Identifier (SFI) is coded as 5 bits valued in the range from 1 to 30. No two files under the same parent shall have the same SFI.

A DF name is coded on 1 to 16 bytes. The DF name is the AID and shall be unique within a card.

The reserved FID '7FFF' can be used as a FID for the ADF of the current active application on a given logical channel.

8.4 Methods for selecting a file

After the UICC activation (as defined in clause 6.1) and the Answer To Reset (ATR), the Master File (MF) is implicitly selected and becomes the current directory. Each file may then be selected by using the SELECT function, using one of the 3 file referencing methods defined in this clause.

8.4.1 SELECT by File IDentifier referencing

Selecting a DF, an ADF or the MF sets the current directory. After such a selection there is no current EF. Selecting an EF sets the current EF and the current directory remains the DF, ADF or MF, which is the parent of this EF. The current EF is always a child of the current directory. Only the ADF of the current application can be selected by FID.

Any application specific command shall only be operable if it is specific to the Current Directory.

The following files may be selected, by File Identifier (FID) referencing, from the last selected file:

Figure 8.4 is an example of the logical structure for an application conforming to the present document.

Figure 8.4: Example of a logical structure

Table 8.1 gives all the valid selections for an application complying to the present document for the logical structure in figure 8.4, if the FID is used. Reselection of the last selected file is also allowed but not shown. In this example, it is considered that the current application (ADF1) has been previously selected by DF name. Therefore ADF1can be selected by using the FID '7FFF'.

Table 8.1: File selection
Last selected fileValid selections
MF DF1 ADF1 DF3 DF4 DF5 EF1 EF2 EF3 EF4 EF5 EF6 EF7ADF1, DF1, EF1, EF-DIR MF, ADF1, EF2, MF, DF3, DF4, EF3 MF, ADF1, DF4, DF5, EF4 MF, ADF1, DF3, EF5, EF6 MF, ADF1, DF3, EF7 MF, ADF1, DF1, EF-DIR MF, ADF1, DF1 MF, ADF1, DF3, DF4 MF, ADF1, DF3, DF4, DF5, MF, ADF1, DF3, DF4, EF6 MF, ADF1, DF3, DF4, EF5 MF, ADF1, DF3, DF5

8.4.2 SELECT by path referencing

A file, DF or EF, may be referenced by path, as defined in clause 8.3. Table 8.2 contains examples of selection by path from figure 8.4. In this example, it is considered that the current application (ADF1) has been previously selected by DF name. The implicit FID of ADF1 '7FFF' is used in table 8.2 (see clause 8.3).

Table 8.2: Examples of file selection by path
Last selected DFBeginning of the pathExample selections
anyMF'EF1', 'EF-DIR', 'DF1', 'DF1||EF2'
anyMF'7FFF||DF3', '7FFF||DF3||EF4', '7FFF||DF3||DF5', '7FFF||DF3||DF5||EF7' '7FFF||DF4', '7FFF ||DF4||EF5', '7FFF||DF4||EF6, '7FFF||EF3'
DF1Current DF'EF2'
DF3Current DF'DF5', 'DF5||EF7', 'EF4'
DF4Current DF'EF5', 'EF6'
DF5Current DF'EF7'

In the case of "select by path from MF", the terminal may use the special file-id '7FFF' (see clause 8.3) at the beginning of the path. It indicates that the path begins at the ADF of the current active application on this logical channel.

The following restriction apply:

8.4.3 Short File Identifier

Any EF within a DF can be implicitly selected without giving a SELECT command by applying one of the following commands at the DF or ADF level and giving a Short File Identifier (SFI) as a part of the command:

Support of SFI for a specific file is indicated if the FCP of the file contains a TLV DO with tag '88'. If the length is 0 it indicates that the file does not support referencing by SFI. If the TLV DO is not present in the FCP it indicates that the 5 least significant bits of the FID are used as SFI.

When the READ RECORD command contains a valid SFI, it sets the file as the current EF and resets the current record pointer. Subsequent records are read with the READ RECORD command without SFI.

When the UPDATE RECORD command contains a valid SFI, it sets the file as the current EF and resets the current record pointer. Subsequent records are updated with the UPDATE RECORD command without SFI.

When the INCREASE command contains a valid SFI, it sets the file as the current EF and resets the current record pointer. Subsequent records are increased with the INCREASE command without SFI.

When the SEARCH RECORD command contains a valid SFI, it sets the file as the current EF and resets the current record pointer. Subsequent records are searched with the SEARCH RECORD command without SFI.

8.5 Application characteristics

An application may be either explicitly or implicitly referenced.

An application is activated by explicit selecting it with the AID. This sets the application's ADF as the current ADF.

A current ADF can be referenced by FID with the implicit reference value '7FFF'.

8.5.1 Explicit application selection

8.5.1.1 SELECT by DF name

A selectable application, represented in the UICC by the AID, shall be referenced by a DF name coded on 1 to 16 bytes. Each name shall be unique within a UICC. A DF name can be used in the SELECT command to select a selectable application.

8.5.1.2 SELECT by partial DF name

A selectable application can also be selected using a partial DF name (when P1 = '04') using the P2 parameters first and only occurrence, next, previous or last as defined in ISO/IEC 7816-4 [12]. In this case, the DF name is right truncated. If several applications starting with the same byte content in the AID are present on the card, the application selected is depending upon the value specified in P2. If the "last" option is indicated in P2, the selected application is the last active application matching the partial DF name, even if it was during a previous card session.

Selection of an application using a partial DF name is optional for mono application cards, but a multi application card shall support it. The card shall indicate the support of this feature in the "card service data" and the "card capabilities" compact-TLV objects of the ATR historical bytes as specified in ISO/IEC 7816-4 [12].

The interpretation of next, previous and first is to be specified by the application. The application that is selected using these parameters shall match the partial DF name provided in the SELECT command. If the UICC does not support selection with partial DF name, the UICC shall respond with an appropriate response (e.g. command parameters not supported '6A86').

8.5.2 Application session activation

The application session is initiated when the terminal sends a SELECT command, with the application's AID, indicating in the command parameters that the application shall be activated.

An application may need an initialization procedure to be performed after its activation. This procedure is outside the scope of the present document but shall be described in the application specification. The procedure is used to bring the terminal and the application in the UICC to a well-defined state.

After having selected the application the UICC evaluates the security environment for this application. The SE is set according to the verification requirements for the application see table 9.1.

The verification status of the application PIN is updated according to the application's session activation procedure, as specified by the application.

The terminal may send to the UICC a specific STATUS command indicating that the initialization procedure of the application has been successfully executed.

There can only be one active selectable application session on a given logical channel. Therefore, in order to activate a new selectable application session in parallel to another, a new logical channel shall be opened.

A selectable application session may take place on several channel sessions.

8.5.3 Application session termination

An application may have a session termination procedure to be performed before the application is terminated. This procedure shall be described in the application specification. Before this procedure is executed, the terminal may send to the UICC a specific STATUS command indicating that the termination procedure of the application will start. After this termination procedure has been executed the terminal and the application are in a well-defined state.

An application session is then terminated if any of the following events occur on each logical channel that the application session has been activated on:

An application session is also terminated when the terminal performs a reset of the UICC.

The verification status of the application PIN is updated according to the application's session termination procedure, as specified by the application.

8.5.4 Application session reset

An application is reset if the application is reselected using the SELECT by DF name command with the AID corresponding to the currently active application, indicating in the command parameters that the application shall be activated.

Reset initializes the application session activation procedure. The security status of the application is updated according to the application's session activation procedure, as specified by the application.

8.5.5 GSM/USIM application interaction and restrictions

Activation of a USIM session excludes the activation of a GSM session. In particular, this implies that once a USIM application session has been activated, commands sent to the UICC with CLAss byte set to 'A0' shall return SW1SW2 '6E 00' (class not supported) to the terminal.

Similarly, activation of a GSM session excludes the activation of a USIM session.

At most one USIM session can be active at the same time.

8.6 Reservation of file IDs

The following FIDs are reserved by the present document:

'7F31' (DF IDEN ) is used in the iDEN specification.

In all the above, X ranges, unless otherwise stated, from '0' to 'F'.

8.7 Logical channels

Logical channels are defined in ISO/IEC 7816-4 [12]. There may be up to 3 logical channels in addition to the basic logical channel 0. Channel 0 is always available and open throughout the card session.

A UICC which supports logical channels indicates it in the ATR, together with the assignment methods and maximum number of logical channels it supports. The UICC supporting logical channels shall support:

Command interdependencies on one logical channel are independent of command interdependencies on another logical channel.

There is no interleaving of commands and their responses across logical channels; between the receipt of the command APDU and the sending of the response APDU to that command, only one logical channel is active.

In order to be accessed from several logical channels at the same time, a given file (EF, DF, ADF) shall be indicated as "shareable" in its file descriptor.

File access should be managed independently on each opened logical channel. In particular, a record-based file shall have a different record pointer for each opened logical channel.

Applications are responsible for keeping data consistency (in the card and the terminal) when accessing the same file from different logical channels.

NOTE: Special attention should be given to cyclic files, e.g. when the file is read in one channel and updated in another.

A logical channel is opened by using a MANAGE CHANNEL command, in which the card assigns a channel number and returns it in the response.

The logical channel remains open until it is explicitly closed by a MANAGE CHANNEL command, or if the UICC is deactivated.

When the open function is performed from the basic channel, then after a successful open, the MF shall be implicitly selected as the current DF. When the open function is performed from a logical channel which is not the basic one, then after a successful open, the current DF of the logical channel from which the command was issued shall be selected as the current DF. In both cases, no current EF is selected in the new logical channel.

Parameters of the MANAGECharacteristics of the new channel
CHANNEL commandCurrent DFADF of current active application (referred to by the special '7FFF' file-ID)
CLA=00 (from the basic channel)MFUndefined
CLA≠00 (from the non-basic channel)The same current DF as the one where the open channel is performedADF the application active in the logical channel where the open channel was performed

Once a new channel is opened, the current DF and the current file are independent per each logical channel.

If the MANAGE CHANNEL command is performed on a DF or ADF that is not shareable, the card shall respond with an appropriate error message. The response shall indicate that the command is not allowed. No new channel is opened.

9 Security features

Every application that conforms to the present document may define security features in addition to the mandatory features defined in this clause.

9.1 Supported security features

A terminal that conforms to the present document and is designed for a multi-application UICC shall recognize the security attribute tags specified in the present document.

A single application terminal conforming to the present document shall support one of the access rules format specified in the present document. The application specifies which format is used.

A multi-application capable terminal that is designed to support a multi-verification capable UICC shall, from the security context point of view, support the usage of the level 1 verification requirements (PIN) and the level 2 verification requirements (PIN2). The coding is defined in table 9.3. The terminal shall, in addition, support the usage of a universal PIN as defined in the present document.

A multi-verification capable UICC conforming to the present document shall, from the security context point of view, support more than one level 1 user verification requirement (PIN). The specific key reference for the level 1 PIN is specified by each application in accordance with table 9.3. In addition, the application may specify a level 2 user verification requirement (PIN2). A multi-verification capable UICC shall support the use of a universal PIN. A multi-verification capable UICC shall support access rules defined in security attributes indicated in tag '8B' (i.e. referenced to expanded format).

A single verification capable UICC shall, from the security context point of view, support one level 1 user verification requirement (PIN) as defined in table 9.3. In addition the application may specify a level 2 user verification requirement as a second application verification requirement (PIN2). A single verification capable UICC may contain one or more selectable applications if there are no security aspects to be considered between the different selectable applications. From the security point of view only one level 1 verification requirement (PIN) is assigned to all ADFs/DFs and files on the UICC. In addition, a level 2 user verification requirement (PIN2) may be assigned for each application. From the security and access rules point of view the UICC is seen as a single application card. The coding of the level 1 and level 2 user verification requirement shall be according to table 9.3.

9.2 Security architecture

An application on a UICC conforming to the present document shall specify a level 1 key reference as the user verification (PIN). In addition the application may specify a level 2 key reference as a second user verification requirement (PIN2). The coding of the level 1 and level 2 user verification requirement shall be according to table 9.3. In addition, an application may specify the usage of a universal PIN as a replacement for the application PIN.

In order to perform commands other than SELECT and STATUS/GET RESPONSE, the security condition for the file shall be met. A security condition data object contains the conditions to be met in order to perform certain commands on a selected ADF/DF/EF.

If the UICC can not determine the access condition for the requested access to a file, then the requested access to this file shall not be granted and the card shall return an error Status Word '6982' (Security status not satisfied).

The security architecture consists of the following parts:

The following clauses define the parts constituting the security architecture.

9.2.1 Security attributes

The security attributes are attached to an ADF/DF/EF and they are part of the FCP. The security attributes are indicated in the FCP using tag '8B', tag '8C' or tag 'AB' depending upon the format used, see ISO/IEC 7816-9 [16].

9.2.2 Access mode

The access mode byte/data object (AM byte/AM_DO) defines for which group/type of command(s) the security condition apply. The interpretation of the AM byte/AM_DO is file dependent (i.e. different for a DF/ADF and an EF), see ISO/IEC 7816-9 [16]. The command type/group is defined and coded according to ISO/IEC 7816-9 [16].

For instructions not belonging to a group as defined in ISO/IEC 7816-9 [16] the access rights can be indicated using AM_DO tags '81' to '8F'. The value of the tag defining the AM_DO indicates what description of the command exists in the definition list to follow in the value part of the data object. The coding of bit b4 to b1 in the AM_DO tag is defined in ISO/IEC 7816-9 [16].

The security conditions for bits not set to '1' in the AM byte are set to NEVer by default.

9.2.3 Security condition

The Security Condition (SC) indicates which security related procedures (user PIN verification) shall be satisfied before a command may be performed on a file. The SC is coded according to ISO/IEC 7816-9 [16].

9.2.4 Access rules

The access rule defines the security conditions for access to a file for each command/command group indicated in the AM-byte/AM_DO. The security condition is indicated in the SC-byte(s)/SC_DO(s) following the AM-byte/AM_DO. The access rule is coded by using one ore more AM-bytes/AM_DOs each followed by one or more security conditions that are to be satisfied for the appropriate access.

The access rules may be coded in a compact or an expanded format. Furthermore, it is possible to combine one or more SCs to one AM such that at least one SC (the OR relation) shall be fulfilled before the command can be executed. It is possible to combine the SC such that more than one SC has to be fulfilled (the AND relation).

An access rule is a set of requirement(s) that shall be met in order to perform operations on a file. An access rule contains one or more security attributes, the AM byte/AM_DO in the attribute indicates what commands can be performed and the SC byte/SC_DO indicates what SC shall be met to be able to perform the commands indicated in the AM byte/AM_DO. The content of each AM byte (in compact format) or AM_DO (in expanded format) shall be unique within the same access rule. SC_DOs OR and AND relations shall contain at least two access conditions. The terminal shall ignore an AM/SC combination which is syntactically incorrect or with unknown instructions.

The CRT tags for SC_DOs are defined in ISO/IEC 7816-9 [16]. The SC required to perform commands indicated in the AM byte/AM_DO may be a simple condition or a logical OR or AND condition of several SC_DOs. The constructed TLV object containing AM bytes/AM_DOs and SC bytes/SC_DOs is an access rule. An access rule can be indicated in the FCP in one of the following ways:

9.2.5 Compact format

The compact format is indicated by tag '8C' in the FCP. In the compact format an access rule consists of an AM byte and one or more SC bytes as defined in ISO/IEC 7816-9 [16].

The AM byte conveys two types of information. The interpretation of the AM byte itself (coded on b8), and the number of SC bytes following, this is equal to the number of bits set to '1' in bits b7 to b1 in the AM byte. If b8 in the AM byte is set to '0' the interpretation of bits b7 to b1 is as defined in ISO/IEC 7816-9 [16]. If b8 in the AM byte is set to '1' the usage of bits b7 to b4 is proprietary.

When multiple sets of an AM byte and one or more corresponding SC bytes are present in the value field they present an OR condition.

EXAMPLE 1: The access rule for READ always for an EF is coded using the compact format as follows.

TagLAMSC
'8C''02''01''00'

EXAMPLE 2: The access rule for UPDATE user PIN verification and READ always for an EF is coded using the compact format as follows.

TagLAMSCSC
'8C''03''03''10''00'

9.2.6 Expanded format

The expanded format is indicated by tag 'AB' in the FCP. This tag indicates a constructed data object. In the expanded format an access rule consists of one AM_DO followed by a sequence of SC_DOs. The contents of the AM_DO is defined by the tag that it is indicated with, see ISO/IEC 7816-9 [16]. Tag '80' indicates that the AM_DO contains an AM byte. The sequence of SC_DOs following the AM-DO is relevant for all commands specified in the AM_DO. The different SC_DOs can form an OR or an AND condition as defined in ISO/IEC 7816-9 [16]. The information following tag 'AB' in the FCP can contain a lot of data if the rule is complex. This information is part of the FCP that is transmitted over the interface in the response to a SELECT or a STATUS command. The structure of the security attribute in expanded format is as follows.

TaglengthAM_DO tag AM_DOSC_DO tagSC_DOAM_DO tag AM_DOSC_DO tag SC_DO
'AB'See ISO/IECSeeISO/IECSee ISO/IECSee ISO/IEC
7816-9 [16]7816-9 [16]7816-9 [16]7816-9 [16]

An example using the expanded format coding is given in annex E.

9.2.7 Access rule referencing

Access rules may be shared between files in the UICC by referencing. This is accomplished by storing the security attributes in the expanded format in a linear fixed file, the Access Rule Reference(EF ARR ) in the UICC. The structure of the EF ARR file is as follows.

Record Number (ARR)Record Content (Access Rule)
'01'AM_DO⎜⎜SC_DO 1⎜⎜SC_DO 2⎜⎜AM_DO⎜⎜SC_DO 3⎜⎜SC_DO 4 ….
'02'AM_DO⎜⎜SC_DO 1⎜⎜AM_DO⎜⎜SC_DO 5⎜⎜SC_DO 6 ….

The referenced format is indicated in the FCP following tag '8B'. The access rule is stored in a file, EF ARR . This file is a linear fixed file. Referencing is based on the following two methods:

The second possibility allows the usage of different access rules in different security environments. When referencing EF ARR is based on the file ID, the rules for the location of the access rules are as follows:

NOTE: There may be several EF ARR containing access rules under the same DF. They are distinguished and referred to by their respective file-IDs.

The structure of the access rule referencing DO is as follows.

TagLengthValue
'8B''03'File ID, record number
'8B''02' + n x '02'File ID, SE ID n1 , Record number X, SE ID n2 , Record number Y, etc.

Each record in EF ARR contains a sequence of AM_DOs followed by SC_DOs. The content of the record is the rule that applies for access to the selected file. The content of a sample EF ARR file is given in annex F. The option with the SE ID referencing shall be used in an application where several security environments exist.

9.3 Security environment

The security environment is a mechanism to specify for the card system the security functions that are available to provide protection to commands for a specific application of the card according to ISO/IEC 7816-8 [15]. The security environment for a multi-application UICC is defined as a container for each activated application on the UICC. In case of a single application card the security environment is valid for the whole UICC. In the referenced format it is possible to indicate different access rules as a function of the SE that is in use.

9.3.1 Definition of the security environment

In case the referenced format contains SEID as the referencing method the terminal shall evaluate the SEID and perform the appropriate user verification accordingly.

The following properties are mapped to SE01 and SE00.

SE IDProperties
'00'(The global Application PIN is disabled AND the Universal PIN is disabled) OR (The global Application PIN is disabled AND the Universal PIN is enabled and used)
'01'The global Application PIN is enabled OR (the global Application PIN is disabled AND the Universal PIN is enabled but not used)

The above requirements are derived from table 9.1. A multi-application capability UICC shall support the use of SE00 and SE01 in order to allow application verification requirement to be replaced by the Universal PIN. A multi-application capability terminal shall support SEID referencing in EF ARR .

Table 9.1: PIN mapping into SE
PIN to verifyUniversal PIN status
EE APPL_PIN SE01NE APPL_PIN SE01
APPL_PIN statusNEUUPUniversal_PIN SE00NO PIN SE00
DUUPNO PIN SE01NO PIN SE00
Key:UUP: Use Universal PIN (usage qualifier set to '08'). DUUP: Do not Use Universal PIN (usage qualifier set to '00').

The Security Environment when no application is active on a given logical channel (SE_No_Active_Application) is set as follows: all application PINs assigned on the UICC are considered as APPL_PIN; if at least one of the application PINs is disabled, the SE is SE#00 except for the case where the Universal PIN is enabled but the default usage qualifier (see clause 9.5.2) is set to "do not use" as defined in table 9.1 (DUUP). This Security Environment is valid under the MF and under its child DFs/EFs as long as no application is active.

The Security Environment when an application is active on a given logical channel (SE_Active_Application) is determined as in table 9.1 with the APPL_PIN being the Application PIN of the active application. This Security Environment is valid under the ADF/MF and their child DFs/EFs.

9.3.2 Logical channels and security environment

A UICC supporting logical channels has the security environment set during the application activation and is valid for the logical channel on which the application is activated. The security environment remains the same on this logical channel until a new application is selected or the status of the PIN status DO has changed, i.e. the application or universal PIN status has been changed from disabled to enabled or vice versa.

The security environment of an application running on a logical channel is inherited when a new channel is opened from the non-basic channel. It is evaluated as after the ATR and set as the SE_No_Active_Application when the new channel is opened from the basic channel.

Any command issued on a logical channel affecting the SE setting only affects the SE on the channel where the command was issued and other channels with inherited security from this channel. The SE change on a channel with inherited security also changes the SE on the channel from which the security status was inherited.

9.4 PIN definitions

The following clauses define the types of PIN that shall exist on a UICC, namely the Universal PIN and the application PIN, as well as other types of access conditions needed by the UICC/an application.

9.4.1 Universal PIN

A Universal PIN is a PIN that is used in a multi-application environment to allow several applications to share one common PIN. The Universal PIN is a global access condition that has been assigned a key reference value '11'. This key reference value shall not be used for anything else but to indicate the Universal PIN.

In order to give access to several applications on a multi-application UICC, a terminal conforming to the present document shall support the usage of the Universal PIN. A multi-application UICC according to the present document shall support the usage of a Universal PIN.

If an application allows the use of the Universal PIN as replacement PIN, the Universal PIN shall be part of the access condition for this application on a multi-application UICC that complies to the present document. In case of a single verification capable UICC the Universal PIN shall not be used.

The Universal PIN does not belong to any application, e.g. its verification status cannot be reset by the application activation or termination procedures.

9.4.2 Application PIN

An application PIN is a PIN that uses a global key reference (defined as level 1 in table 9.2) as defined in table 9.3. The application PIN allows access to any file on the UICC where it is referenced in the access rules. i.e. this PIN has global access rights with respect to files. It becomes an application PIN based on where it is assigned, and it belongs to the corresponding application Security Environment. Its verification status can be reset by the application activation or termination procedure. An application, from the security context point of view, may consist of one or more ADFs/DFs. In this case the ADFs/DFs are seen as one application from the security and access rules point of view. All operations performed on a PIN (enable/disable/replace) covering several ADFs/DFs affects the applications where the PIN is used and the access rules where the corresponding key reference is used.

9.4.3 Local PIN

A local PIN is a PIN that uses a local key reference which is only valid within the ADF/DF where it is indicated in the FCP. It means that 2 ADFs can use the same local key reference number with two different values and two different status (enabled, disabled, verified, blocked), one for each ADF. The verification status of a local PIN is maintained when performing file selection. A local PIN shall be indicated in the FCP of child DFs. A local PIN is defined as level 2 in table 9.2 and coded as defined in table 9.3. A local PIN referenced in an ADF or a DF, which is not DF TELECOM , does not give access to DF TELECOM .

An ADF shall use only one application PIN and one local PIN. If replacement of the application PIN by the Universal PIN is authorized, the ADF shall also use the Universal PIN. Table 9.3 indicates how application PINs and local PINs shall be paired (the global key reference '01' is paired with the local key reference '81', the global key reference '02' is paired with the local key reference '82', etc.).

A local PIN can be assigned to a DF which is not part of an ADF. In this case, a key reference indicating a second application PIN as defined in table 9.3 shall be used.

9.4.4 PINs and logical channels

The PIN status of the Universal PIN and of application PINs is global in the UICC. The PIN status of local PINs exists within the ADF/DF where it is specified.

The PIN status of the Universal PIN, application PINs, and local PIN is independent from the logical channels. This means that when a PIN is verified in one logical channel, it is also verified in all other channels. Also when a PIN is enabled in one logical channel it is enabled in all other channels.

9.5 PIN and key reference relation ship

This clause describes the relationship between the user verification requirement (PIN) and referencing to a PIN in the VERIFY, CHANGE, DISABLE/ENABLE VERIFICATION and UNBLOCK commands.

9.5.1 Access condition mapping

Access condition mapping, using SC_DOs, is done using the expanded format with the entries coded as CRT values, i.e. tag 'A4' is used. The CRT is a constructed TLV DO containing a usage qualifier TLV DO (tag '95') and a Key reference TLV DO (tag '83').

The access condition groups are defined according to table 9.2. Each group is divided into several key references. The usage of a key reference shall be in accordance with the group definition in table 9.2.

Table 9.2: Access condition level coding
LevelAccess condition
0ALWays
1User Verification (PIN)
2(see note 1)
3 to 4Reserved for Future Use
5 to 6(see note 2)
7NEVer
NOTE 1:This level is reserved for a second level of user verification (PIN2) that may be defined by an application.
NOTE 2:Allocation of these levels and the respective requirements for their fulfilment are the responsibility of the appropriate administrative authority.

The levels indicated in table 9.2 are used in the present document to refer to a specific group of access conditions.

A key reference shall only be assigned for the purpose as it is defined in table 9.3, e.g. a level 1 key reference is always to be used for an application or a set of applications that share the same access conditions. A level 2 key reference is only valid within the ADF/DF where it is indicated.

Table 9.3: PIN mapping into key references
ValueAccess condition
CRT TagLenKey Ref TagLenValueUsage Qualifier TagLenValLevel
'90''00'------ALW0
'A4''06''83''01''01''95''01''08'PIN Appl 11
'A4''06''83''01''02''95''01''08'PIN Appl 2
'A4''06''83''01''03''95''01''08'PIN Appl 3
'A4''06''83''01''04''95''01''08'PIN Appl 4
'A4''06''83''01''05''95''01''08'PIN Appl 51
'A4''06''83''01''06''95''01''08'PIN Appl 6
'A4''06''83''01''07''95''01''08'PIN Appl 7
'A4''06''83''01''08''95''01''08'PIN Appl 8
'XX''06''83''01''09''95''01''08'RFU
'A4''06''83''01''0A''95''01''08'ADM15
'A4''06''83''01''0B''95''01''08'ADM2
'A4''06''83''01''0C''95''01''08'ADM3
'A4''06''83''01''0D''95''01''08'ADM4
'A4''06''83''01''0E''95''01''08'ADM5
'A4''06''83''01''11''95''01''08'PIN Universal PIN1
'XX''06''83''01''12-1E''95''01''08'RFU (Global)3
'A4''06''83''01''81''95''01''08'Second PIN Appl 12
'A4''06''83''01''82''95''01''08'Second PIN Appl 2
'A4''06''83''01''83''95''01''08'Second PIN Appl 3
'A4''06''83''01''84''95''01''08'Second PIN Appl 4
'A4''06''83''01''85''95''01''08'Second PIN Appl 52
'A4''06''83''01''86''95''01''08'Second PIN Appl
'A4''06''83''01''87''95''01''08'6 Second PIN Appl 7
'A4''06''83''01''88''95''01''08'Second PIN Appl 8
'A4''06''83''01''89''95''01''08'RFU
'A4''06''83''01''8A''95''01''08'ADM66
'A4''06''83''01''8B''95''01''08'ADM7
'A4''06''83''01''8C''95''01''08'ADM8
'A4''06''83''01''8D''95''01''08'ADM9
'A4''06''83''01''8E''95''01''08'ADM10
'XX''06''83''01''90-9E''95''01''08'RFU (Local)4
'97''00' into use.------NEV7
NOTE: The CRT value 'XX' for RFU key references is specified at the time when the value is taken

A single verification capable UICC (from the security context point of view) shall use key reference '01' as PIN and key reference '81' as PIN2. A multi-verification capable UICC shall use key references in the range of '01' to '08' as PIN and may use key references in the range from '81' to '88' as PIN2. In addition a multi-verification capable UICC shall support the use of key reference '11' as a universal PIN, see clause 9.3.1 for the definition of a universal PIN. Multiple applications (from the security context point of view) on a UICC shall not share any key references except for key reference '11', which is used as the universal PIN.

9.5.2 PIN status indication

The status of a PIN that is used by an application for user verification is stored in the PS Template DO and shall be indicated in the FCP in a response to the SELECT or STATUS command issued at the application/DF level. The PIN status information is indicated in the FCP in the PS template DO using tag 'C6'. The PS template DO conveys two types of data, first the PS_DO indicated by tag '90' that indicates the status of the PIN(s) enabled/disabled. The PS_DO is followed by one or more key reference data objects indicated by tag '83'. The PIN status may be encoded over several bytes. For each bit set to '1' the corresponding key reference (PIN) is enabled. The PS_DO is coded using a bitmap list. Bit b8 in the most significant byte corresponds to the first key reference indicated by tag '83' following the PS_DO. Bits b7 to b1 are mapped to consecutive key references indicated by tag '83'. A key reference data object may be preceded by a usage qualifier data object. The usage qualifier data object indicated by tag '95' is mandatory for the universal PIN, see clause 9.4.1 and optional for other PINs. This usage qualifier indicates whether an enabled PIN needs to be verified for access. If there is no usage qualifier, or if the associated data object is empty, in front of a key reference, this indicates that this key reference does not support this feature, and it shall always be verified if enabled. The content of the PS_DO usage qualifier is defined in table 9.4. From table 9.4, the value to be used for user PIN verification is '08'.The usage qualifier of the Universal PIN is defined in the context of an application and may have different value in different applications.

The default usage qualifier of the Universal PIN after the ATR is set to "do not use" if all application PINs are enabled or if at least one of the applications where the application PIN is disabled has the Universal PIN usage qualifier set to "do not use". When no application is active on a given logical channel, the Universal PIN usage qualifier is evaluated as after the ATR.

Table 9.4: Usage qualifier coding for PS_DO
b8b7b6b5b4b3b2b1Meaning
00000000the verification requirement is not used for verification
1-------- use verification (DST, CCT) - use encipherment (CT) - use external authentication (AT)
-1------- use computation (DST, CCT) - use decipherment (CT) - use internal authentication (AT)
--1------ use SM response (CCT, CT, DST)
---1----- use SM command (CCT, CT, DST)
----1---- use the PIN for verification (Key Reference data user knowledge based)
-----1--- use user authentication, biometric based
------xxRFU (default = 00)

The PS template DO is constructed as indicated in tables 9.5 and 9.6.

Table 9.5: PS Template DO structure
PS Template DO TagLPS-DO TagLV PS-byte(s)Key-reference tagL VKey-reference tagLV
'C6''90''83''01''83''01'
Table 9.6: PS Template DO structure when PS_DO usage qualifier is used
PS Template DO TagLPS-DO TagLV PS-byte(s)Usage Qualifier tagLV Key-reference tagL VKey-reference tag LV
'C6''90''95''01''83''01''83''01'

10 Structure of commands and responses

This clause defines the command and response APDUs supported by the UICC.

10.1 Command APDU structure

This clause states a generic structure of an application protocol data unit - APDU - that is used by the application protocol on the top of the transmission protocol for sending a command to the card.

A command APDU consists of a header and a body part. The contents of the command APDU are depicted in table 10.1 where the header consists of the CLA, INS, P1 and P2 bytes that are mandatory for a command APDU and an optional body part that can contain the Lc, Data and Le. Parameters are further explained in clauses 10.1.1 to 10.1.6.

Table 10.1: Contents of command APDU
CodeLengthDescriptionGrouping
CLA1Class of instructionHeader
INS1Instruction code
P11Instruction parameter 1
P21Instruction parameter 2
Lc0 or 1Number of bytes in the command data fieldBody
DataLcCommand data string
Le0 or 1Maximum number of data bytes expected in response of the command

Four cases of C-APDU structure are possible as defined in table 10.2.

Table 10.2: Cases of C-APDUs
CaseStructure
1CLA INS P1 P2
2CLA INS P1 P2 Le
3CLA INS P1 P2 Lc Data
4CLA INS P1 P2 Lc Data Le

10.1.1 Coding of Class Byte

The most significant nibble of the Class byte (b8 to b5) codes the type of the command as stated in table 10.2. Bits b4 and b3 are used for indication of secure messaging format (see table 10.4). Bits b2 and b1 indicates the logical channel used. Logical channels are numbered from 0 to 3. If the card supports the logical channel mechanism, the maximum number of available logical channels is indicated in the card capabilities data object of historical bytes of an ATR (refer to ISO/IEC 7816-4 [12]). If the card capabilities data object is missing, logical channel b2 = b1 = 0 is supported only.

An application on a UICC supporting logical channels utilizing secure messaging shall either exclude the class byte from the signature calculation for the message verification or set it to a default value. The terminal may change the logical channel on which the application is executed compared to the logical channel used for the secure messaging verification signature.

Table 10.3: Coding of class byte
b8b7b6b5b4b3b2b1ValueMeaning
0000----'0X'The coding is according to ISO/IEC 7816-4 [12]
1010----'AX'Coded as ISO/IEC 7816-4 [12] unless stated otherwise
1000----'8X'Structured as ISO/IEC 7816-4 [12], coding and meaning is defined in the present document
----XX---Secure Messaging indication (see table 10.4)
------XX-Logical channel number (see clause 10.3)
Table 10.4: Coding of Security Messaging Indication
b4b3Meaning
00No SM used between terminal and card
01Proprietary SM format
1xSecure messaging according to ISO/IEC 7816-4 [12] used
10Command header not authenticated
11Command header authenticated

By default no secure messaging is supported by the card, i.e. b4 = b3 = 0, unless it is stated otherwise by an application.

10.1.2 Coding of Instruction Byte

Table 10.5 depicts coding of instruction byte of the commands.

Table 10.5: Coding of Instruction Byte of the Commands for a telecom application
COMMANDCLAINS
Command APDUs
SELECT FILE0X'A4'
STATUS8X'F2'
READ BINARY0X'B0'
UPDATE BINARY0X'D6'
READ RECORD0X'B2'
UPDATE RECORD0X'DC'
SEARCH RECORD0X'A2'
INCREASE8X'32'
VERIFY0X'20'
CHANGE PIN0X'24'
DISABLE PIN0X'26'
ENABLE PIN0X'28'
UNBLOCK PIN0X'2C'
DEACTIVATE FILE0X'04'
ACTIVATE FILE0X'44'
AUTHENTICATE0X'88'
GET CHALLENGE0X'84'
TERMINAL PROFILE80'10'
ENVELOPE80'C2'
FETCH80'12'
TERMINAL RESPONSE80'14'
MANAGE CHANNEL0X'70'
Transmission oriented APDUs GET RESPONSE0X'C0'

10.1.3 Coding of parameter bytes

The value of the parameters P1 and P2 depends on the command. If the parameter is not used, the value is set to '00'. Coding of the parameter bytes is presented in the command definition clauses.

10.1.4 Coding of Lc byte

The number of data bytes present in the data field of the command APDU is presented in the parameter Lc. Lc is optional, in the command APDU, however if the Lc is present in the command APDU, data field consists of Lc subsequent bytes. The terminal may send from 1 byte to 255 bytes of command data.

10.1.5 Coding of data part

When present in a command or response APDU the structure of the data field is specific to each command.

10.1.6 Coding of Le byte

The maximum number of bytes expected in the data part of the response APDU is presented in the parameter Le, which is optional. This means that if the terminal does not expect any data in the response APDU Le is absent from the command APDU. However, if Le is present in the command APDU, the data field of the response APDU is expected to consist of Le bytes.

Le set to '00' indicates that the terminal expects to receive at most the maximum number of bytes, i.e. 256, in the response ADPU. The UICC may return any number of bytes in the range 1 to 256.

10.2 Response APDU structure

The response APDU consists of an optional data field and a mandatory status part divided into two bytes; SW1 and SW2. The number of bytes received in the response APDU is denoted Lr (length of the response data field). The structure of the response APDU is shown in table 10.6.

Table 10.6: Contents of Response APDU
CodeLengthDescription
DataLrResponse data string
SW11Status byte 1
SW21Status byte 2

Coding of SW1 and SW2 is presented in clause 10.2.1.

10.2.1 Status conditions returned by the UICC

Status of the card after processing of the command is coded in the status bytes SW1 and SW2. This clause specifies the coding of the status bytes.

10.2.1.1 Normal processing

Table 10.7: Status byte coding - normal processing
SW1SW2Description
'90''00' -Normal ending of the command
'91''XX' -Normal ending of the command, with extra information from the proactive UICC containing a command for the terminal. Length 'XX' of the response data

10.2.1.2 Postponed processing

Table 10.8: Status byte coding - postponed processing
SW1SW2Error description
'93''00' -SIM Application Toolkit is busy. Command cannot be executed at present, further normal commands are allowed

10.2.1.3 Warnings

Table 10.9: Status byte coding - warnings
SW1SW2Description
'62''00'-No information given, state of non volatile memory unchanged
'62''81'-Part of returned data may be corrupted
'62''82'-End of file/record reached before reading Le bytes
'62''83'-Selected file invalidated
'63''CX'- -Command successful but after using an internal update retry routine 'X' times Verification failed, 'X' retries remaining (see note)
NOTE:For the VERIFY PIN command, SW1SW2 indicates that the command was successful but the PIN was not correct and there are 'X' retries left. For all other commands it indicates the number of internal retries performed by the card to complete the command.

10.2.1.4 Execution errors

Table 10.10: Status byte coding - execution errors
SW1SW2Description
'64''00' -No information given, state of non-volatile memory unchanged
'65''00' -No information given, state of non-volatile memory changed
'65''81' -Memory problem

10.2.1.5 Checking errors

Table 10.11: Status byte coding - checking errors
SW1SW2Description
'67''00' -Wrong length
'67''XX' -The interpretation of this status word is command dependent, except for SW2 = '00'
'6B''00' -Wrong parameter(s) P1-P2
'6D''00' -Instruction code not supported or invalid
'6E''00' -Class not supported
'6F''00' -Technical problem, no precise diagnosis
'6F''XX' -The interpretation of this status word is command dependent, except for SW2 = '00'
10.2.1.5.1 Functions in CLA not supported
Table 10.12: Status byte coding - functions in CLA not supported
SW1SW2Description
'68''00' -No information given
'68''81' -Logical channel not supported
'68''82' -Secure messaging not supported
10.2.1.5.2 Command not allowed
Table 10.13: Status byte coding - command not allowed
SW1SW2Description
'69''00' -No information given
'69''81' -Command incompatible with file structure
'69''82' -Security status not satisfied
'69''83' -Authentication/PIN method blocked
'69''84' -Referenced data invalidated
'69''85' -Conditions of use not satisfied
'69''86' -Command not allowed (no EF selected)
10.2.1.5.3 Wrong parameters
Table 10.14: Status byte coding - wrong parameters
SW1SW2Description
'6A''80' -Incorrect parameters in the data field
'6A''81' -Function not supported
'6A''82' -File not found
'6A''83' -Record not found
'6A''86' -Incorrect parameters P1-P2
'6A''87' -Lc inconsistent with P1-P2
'6A''88' -Referenced data not found

10.2.1.6 Application errors

Table 10.15: Status byte coding - application errors
SW1SW2Error description
'98''50'- INCREASE cannot be performed, max value reached
'98''62'- Authentication error, application specific
NOTE:Applications may define their own error codes.

10.2.2 Status words of the commands

Table 10.16 shows for each command the possible status conditions returned (marked by an asterisk *).

Table 10.16: Commands and status words
Status WordsSELECTSTATUSUPDATE BINARYUPDATE RECORDREAD BINARYREAD RECORDSEARCH RECORDINCREASEVERIFY PINCHANGE PINDISABLE PINENABLE PINUNBLOCK PINDEACTIVATE FILEACTIVATE FILEAUTHENTICATEGET CHALLENGETERMINAL PROFILEENVELOPEFETCHTERMINAL RESPONSEMANAGE CHANNEL
90 00**********************
91 XX**********************
93 00 98 50 98 62 62 62 62 63 64 6562 00 * 81 82 83 * CX 00 * 00* ** * * * * ** * * * * ** * * * ** * * * * ** * * * ** * * * * * ** * * * * ** * * * * ** * * * * ** * * * * ** * * * * ** * * * ** * * * ** * * * * ** * ** * * ** * * * ** * * ** * * ** * * *
65 81 67 XX 68 00* *** ** ** ** ** **** ** ** ** ******** **
68 81 68 82* ** * ** ** ** ** ** ** ** ******* ** ** ** ** **
69 81 69 82 69 83* *** * ** ** ****** ** ** ** **** * ***
69 84 69 85 69 6A 6A86 80 81 * 82 *** * ** * ** ** * ** * * ** * * ** **** *** * * * ** * * * ** ******* *
6A 6A 83 6A 86*** *** ** *************
**
6A 87***
****
6A 88****
6B 00******
***
***
****
**** ***** *******
6E 00*********
**
6F XX****************
****

The responses '91 XX', and '93 00' can only be given by a UICC to a terminal supporting CAT (see TS 102 223 [4]).

10.3 Logical channels

Commands referring to a certain logical channel carry the respective logical channel number in the two least significant bits of the CLA byte. Logical channels are numbered from 0 to 3. The basic logical channel (number 0) is permanently available.

The MANAGE CHANNEL command shall be used to open and close a logical channel. The channel number is assigned by the UICC.

11 Commands

11.1 Generic commands

This clause lists the basic command and response APDU formats that are used by applications residing on a UICC. It is up to each application to determine which commands it uses. If an application does not support a command, it shall return the appropriate status word, see clause 10.2.

11.1.1 SELECT

11.1.1.1 Functional description

This function selects a file according to the methods described in clause 8.4. After a successful selection the record pointer is undefined.

Input:

Output:

11.1.1.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Selection control, see table 11.1
P2Selection control, see table 11.2
LcLength of subsequent data field or empty
DataFile ID, DF name, or path to file, according to P1
LeEmpty, '00', or maximum length of data expected in response
Table 11.1: Coding of P1
b8b7b6b5b4b3b2b1Meaning
00000000Select DF, EF or MF by file id
00000001Select child DF of the current DF
00000011Select parent DF of the current DF
00000100Selection by DF name (see note)
00001000Select by path from MF
00001001Select by path from current DF
NOTE:This is selection by AID.
Table 11.2: Coding of P2
b8b7b6b5b4b3b2b1Meaning
-XX-----Application session control (see note 2)
-00------ Activation/Reset
-10------ Termination
0--001--Return FCP template
0--011--No data returned
------XXSelection by AID control
------00- First or only occurrence
------01- Last occurrence
------10- Next occurrence
- NOTE- 1:- Whether- the FCP-- information1 returned1 or- Previous occurrence not depends on the type of APDU.
NOTE 2: This only applies when P1 indicates SELECT by DF name.

If P1 = '00' and the data field is empty, then P2 shall be set to '0C' ("No data returned"). Then the MF is set as the Current Directory.

To avoid ambiguities when P1 = '00', the following search order applies when selecting a file with a File ID (FID) as a parameter:

When P1 ≠ '04', bits b2 and b1 of P2 have no meaning and shall be set to 0.

When P1 = '04' (i.e. for selection by AID), a right truncated AID can be specified in the data field.

11.1.1.3 Response Data

Byte(s)DescriptionLength
1FCP template tag = '62'1
2 (to 3)Length of FCP template1 or 2
3 or 4 to L rFCP templateX

The response data contains the File Control Parameters (FCP) template of the selected file. The contents of the FCP depend on the selected file. See below for the list of TLV that are returned in each case.

The value part of the FCP template data object consists of data objects, as shown in clause 11.1.1.3.1. It is mandatory for data objects to be provided in the order given in the description of each response. New data objects can be added to the end of the response data. The terminal shall ignore data objects with tags it does not support.

11.1.1.3.1 Response for MF, DF or ADF

This clause lists the TLVs in the order returned when an MF, DF or ADF is selected.

Table 11.3: Response for MF, DF, or ADF with FCP template
DescriptionTagClauseStatus
File Descriptor'82'11.1.1.4.3M
File Identifier'83'11.1.1.4.4C1
DF name (AID)'84'11.1.1.4.5C2
Proprietary information'A5'11.1.1.4.6C3
Life Cycle Status Integer'8A'11.1.1.4.9M
Security attributes'86', '8B', '8C' or 'AB'11.1.1.4.7C4
PIN Status Template DO'C6'11.1.1.4.10M
Total file size'81'11.1.1.4.2O
M:Mandatory.
O:Optional.
C1:The File identifier is mandatory for a DF or the MF. For a ADF the File identifier is optional.
C2:DF name is mandatory for only ADF.
C3:Proprietary information is mandatory for the MF. For a DF/ADF the Proprietary information is optional.
C4:Exactly one shall be present.
11.1.1.3.2 Response for an EF

This clause lists the TLVs in the order returned when an EF is selected.

Table 11.4: Response for an EF with FCP template
DescriptionTagClauseStatus
File Descriptor'82'11.1.1.4.3M
File Identifier'83'11.1.1.4.4M
Proprietary information'A5'11.1.1.4.6O
Life Cycle Status Integer'8A'11.1.1.4.9M
Security attributes'86', '8B', '8C', or 'AB'11.1.1.4.7C1
File size'80'11.1.1.4.1M
Total file size'81'11.1.1.4.2O
Short file identifier (SFI)'88'11.1.1.4.8O
M:Mandatory.
O:Optional.
C1:Exactly one shall be present.

11.1.1.4 File control parameters

11.1.1.4.1 File size
Byte(s)DescriptionValueLength
1Tag'80'1
2Length'02'1
3 to 4Number of allocated data bytes in the file, excluding structural information2

The range of file size is between '0000' and 'FFFF' and the most significant byte comes first in the value field.

For transparent EF, file size is the length of the body part of the EF, and for linear fixed or cyclic EF, it is the record length multiplied by the number of records of the EF.

11.1.1.4.2 Total file size
Byte(s)DescriptionValueLength
1Tag'81'1
2LengthX, X ≥ 21
3 to X+2Number of allocated data bytes in the file, including structural information if anyX
NOTE:If the file is an EF then X=2.

The most significant byte comes first in the value field.

For an EF, the range of total file size is between '0000' and 'FFFF'.

For an EF, the "total file size" represents the allocated memory for the content and the structural information (if any) of this EF.

For a DF, the "total file size" represents the sum of the "total file sizes" of all the EFs and DFs contained in this DF plus the amount of available memory in this DF. The size of the structural information of the selected DF itself is not included.

11.1.1.4.3 File Descriptor
Byte(s)DescriptionStatusValueLength
1TagM'82'1
2LengthM'02' or '05'1
3File descriptor byte (see table 11.5)M1
4Data coding byteM'21'1
5 to 6Record lengthC'0001' to '00FF'2
7Number of recordsC'01' to 'FE'1
M: C:Mandatory. These bytes are mandatory for linear fixed and cyclic files, otherwise they are not applicable.
· File descriptor.

Contents: File descriptor specifies the file accessibility, and the file type and structure.

Coding: See table 11.5.

Table 11.5: File descriptor byte
b8b7b6b5b4b3b2b1Meaning
0X------File accessibility
00------Not shareable file
01------Shareable file
0-XXX---File type
0-000---Working EF
0-001---Internal EF
0-010---RFU
0-011---
0-100---
0-101---
0-110---
0-111---DF or ADF
0----XXXEF structure
0----000No information given
0----001Transparent
0----010Linear fixed
0----011RFU
0----100
0----101
0----110Cyclic
0----111RFU
1XXXXXXXRFU

Coding: The data coding byte is coded according to table 86 in ISO/IEC 7816-4 [12]. The actual value shall not be checked nor used by the terminal.

Contents: Record length specifies the length of a record when a record structured file has been selected.

Coding: The record length shall be present if a record structured file (i.e. for linear fixed or cyclic files) is selected. In this case it indicates the length the records on 2 bytes. Most significant byte comes first in the value field.

Contents: Number of records specifies the number of records in a record structured file.

files) is selected. In this case it indicates the number of records on 1 byte.

11.1.1.4.4 File identifier
Byte(s)DescriptionValueLength
1Tag'83'1
2Length'02'1
3 to 4File identifier2
11.1.1.4.5 DF name
Byte(s)DescriptionValueLength
1Tag'84'1
2Length1 ≤ X ≤ 161
3 to 2+XDF nameX

DF name is a string of bytes, the AID, which is used to uniquely identify an application dedicated file in the card.

11.1.1.4.6 Proprietary information

This is a constructed TLV object.

Byte(s)DescriptionLength
1Proprietary information constructed Tag = 'A5'1
2Length1
3 to 2+XProprietary data, constructedX

The following TLV objects are defined for the proprietary template (tag 'A5'). Additional private TLV objects (bits b7 and b8 of the first byte of the tag set to '1') may be present after the TLV objects defined in this clause.

EXAMPLE: A manufacturer, issuer, or application provider specific TLV object may be present. If more than one TLV object with the same tag is indicated in this constructed TLV they shall be grouped together as the order in which they appear is used to specify the usage.
DescriptionTagStatusClause
UICC characteristics'80'C111.1.1.4.6.1
Application power consumption'81'C211.1.1.4.6.2
Minimum application clock frequency'82'C311.1.1.4.6.3
Amount of available memory'83'C411.1.1.4.6.4
C1: C2: C3: C4:The UICC characteristics are mandatory for the MF. Application power consumption, is optional for ADFs. This TLV object shall not befor the for anor an EF. an ADF, DFADF, it is optional. MF, it is optional.

An application may supply more than one application power consumption or minimum application clock frequency Data Object.

11.1.1.4.6.1 UICC characteristics
Byte(s)DescriptionValueLength
1Tag'80'1
2Length'01'1
3UICC characteristics byte (see table 11.6)1
Table 11.6: UICC characteristics byte
b8b7b6b5b4b3b2b1Meaning
----XX-1Clock stop allowed
----00-1No preferred level
----01-1High level preferred
----10-1Low level preferred
----11-1RFU
----XX-0Clock stop not allowed
----00-0Never
----01-0Unless at high level
----10-0Unless at low level
----11-0RFU
---X----Supply voltage class A
--X-----Supply voltage class B
-X------Supply voltage class C
X-----X-RFU (shall be set to 0)

If bit b1 is coded '1', stopping the clock is allowed at high or low level. In this case bit b3 and b4 give information about the preferred level (high or low, respectively) at which the clock may be stopped.

If b1 is coded '0', the clock may be stopped only if the mandatory condition b3 = '1' (i.e. stop at high level) or b4 = '1' (i.e. stop at low level) is fulfilled. If all 3 bits are coded '0', then the clock shall not be stopped.

A supply voltage class, as defined in clause 6.2.1, is supported if the bit is coded as a '1'. If the voltage class is not supported the bit is coded as '0'.

11.1.1.4.6.2 Application power consumption

The application power consumption is indicated by tag '81' within the constructed TLV object. The first byte indicates the supply voltage at which the power consumption is measured. The coding of this byte is the same as for the supply voltage class indication in the ATR, see table 6.1. Unused bits are set to RFU. The second byte indicates the power consumption in mA. Bits b8 to b7are RFU. Bits b6 to b1 indicates the power consumption of the application in mA. The power consumption is measured at the frequency indicated in the 'Power consumption reference frequency' field for the application, averaged over 1 ms or at the maximum clock frequency supported by the UICC if no indication is given. The terminal shall ignore the application power consumption values '00' and 'FF'. A value higher than 3C shall not be interpreted by the terminal and is not to be used. The terminal may still accept the application.

The terminal shall evaluate the power consumption value given in the response. If the power supply class indicated in the response is not the currently used the terminal shall recalculate the value to the currently used supply voltage class. The terminal shall accept the application if the recalculated value is within the specification limits set for the currently used supply voltage class. The terminal may accept an application that exceeds the specified value if it can support the power consumption indicated by the application.

Byte(s)DescriptionValueLength
1Tag'81'1
2Length'03'1
3Supply voltage class at which the power consumption is measured1
4Application power consumption'01' to '3C'1
5Power consumption Reference Frequency'0A' to 'FF'1

The Power consumption Reference Frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is 1 MHz and 'FE' is 25,4 MHz. The value 'FF' indicates that no reference frequency is indicated.

11.1.1.4.6.3 Minimum application clock frequency

The application minimum clock frequency is indicated by tag '82' within the constructed TLV object. This TLV object indicates to the terminal the minimum clock frequency required by the application. It is up to the application to specify a value that is required for commands or procedures to be executed within the required time. An application may indicate one or more application minimum clock frequencies if required. In case that more than one TLV object is indicated it is up to the application to specify for what purpose the different values are used, i.e. the order of the TLV objects within the constructed TLV is relevant.

Byte(s)DescriptionValueLength
1Tag'82'1
2Length'01'1
3Application minimum clock frequency'0A' to 'FF'1

The minimum clock frequency is coded in Hexadecimal format. The resolution is 0,1 MHz, i.e. '0A' is 1 MHz and 'FE' is 25,4 MHz. If this TLV object is not present or the value is 'FF', no minimum application clock frequency is indicated.

11.1.1.4.6.4 Amount of available memory

Amount of memory which is available for DFs or EFs creation under the selected DF (and ADFs under the MF)

Byte(s)DescriptionValueLength
1Tag'83'1
2LengthX, X ≥ 21
3 to 2+XNumber of data bytesX

The most significant byte comes first in the value field.

11.1.1.4.7 Security attributes
11.1.1.4.7.1 Compact format
Byte(s)DescriptionValueLength
1Tag'8C'1
2LengthX1
3AM byte1
4 to (X+2)SC bytesX-1

The value of the AM byte is defined in ISO/IEC 7816-9 [16]. The amount of SC bytes depends upon the value of the AM byte. There shall be a SC byte present for each bit set to '1' in the AM byte except for b8. The value of the SC byte is defined in ISO/IEC 7816-9 [16].

11.1.1.4.7.2 Expanded format
Byte(s)DescriptionValueLengthComment
1Tag'AB'1
2LengthV1
3AM DO tag'8X' (see note 1)1
4LengthX1
5 to (4+X)AM_DO(see note 2)XSecurity Rule
5+XSC_DO tag(see note 2)1#1
6+XLengthY1
(7+X) to (6+X+Y)SC_DO(see note 2)Y
……………………………………………… ……………………………………………… ………………………………………………
V+2- (4+W+Z)AM DO tag'8X' (see note 1)1Rule #N
V+2- (3+W+Z)LengthW1
V+2- (2+W+Z) to V+2-(2+Z)AM_DO(see note 2)WSecurity
V+2-(1+Z)SC_DO tag(see note 2)1
V+2-ZLengthZ1
V+2-(Z-1) to V+2SC_DO(see note 2)Z
NOTE 1: The value of 'X' is dependent on the usage of the AM_DO see ISO/IEC 7816-9 [16].

NOTE 2: The value of the AM_DO and the SC_DO is defined in ISO/IEC 7816-9 [16].

11.1.1.4.7.3 Referenced to expanded format

If the length of the data following tag '8B' = '03' the following definition applies.

Byte(s)DescriptionValueLength
1Tag'8B'1
2Length31
3 to 4EF ARR File ID2
5EF ARR Record number1

If the length of the data following tag '8B' is '02' + X × '02' the following definition applies.

Byte(s)DescriptionValueLength
1Tag'8B'1
2Length'02' + X × '02'1
3 to 4EF ARR File ID2
X+4SEID1
X+5EF ARR Record number
NOTE:For each increment of X a new set of SEID and an EF ARR Record numbers are introduced.
11.1.1.4.8 Short file identifier
Byte(s)DescriptionValueLength
1Tag'88'1
2Length'00' or '01'1
3Short file identifier0 or 1

If the TLV is not present, the SFI value is the 5 least significant bits (bits b5 to b1) of the file identifier.

If the TLV is present but empty (i.e. length is 0), the SFI is not supported for the selected file.

If the length of the TLV is 1, the SFI value is indicated in the 5 most significant bits (bits b8 to b4) of the TLV value field. In this case, bits b3 to b1 shall be set to 0.

11.1.1.4.9 Life cycle status integer
Byte(s)DescriptionValueLength
1Tag'8A'1
2Length11
3Life Cycle Status Integer, see table 11.71
Table 11.7: Coding of life cycle status integer
b8b7b6b5b4b3b2b1Meaning
00000000No information given
00000001Creation state
00000011Initialization state
000001-1Operational state - activated
000001-0Operational state - deactivated
000011--Termination state
≠ 0XXXXProprietary
Any other valueRFU
11.1.1.4.10 PIN status template DO

This TLV object contains the PIN status information for a DF/ADF and which PINs are used for access to the DF/ADF and its children. PIN is indicated in this data object using the key reference tag '83' as defined in ISO/IEC 7816-4 [12]. The content of the constructed PIN status TLV Data Object tag 'C6' depends on the length (see below).

Byte(s)DescriptionValueLength
1Tag'C6'1
2Length1
3PS_DO tag'90'1
4LengthX1
X+4PS_DOX
X+5Usage qualifier DO tag (see note 2)'95'1
X+6Length'01'1
X+7Usage qualifier, see clause 9.5.21
X+8Key reference tag'83'1
X+9Length'01'1
X+10Key reference (PIN)see table 9.31
NOTE 1: NOTEThere may be one or more key reference tags following the PS_DO. 2: This TLV DO is mandatory if the Key reference DO value is '11' indicating the Universal PIN, otherwise it is optional.

The usage qualifier DO indicates if the key reference data object (PIN) following it is to be used for verification or not. If this data object is present it shall precede the key reference data object it is associated with.

For the PS_DO coding see clause 9.5.2. For each bit set to '1' in the PS byte, the corresponding key reference in the PS Template, DO is enabled. The number of key reference tags (tag '83') indicates how many different PINs are used for access in the selected DF and its children.

11.1.2 STATUS

11.1.2.1 Functional description

This function returns information concerning the current directory or current application.

In addition, according to the application specification, it may be used to indicate to the application in the UICC that its session activation procedure has been successfully executed or that its termination procedure will be executed.

NOTE: These indications may be used to synchronize the applications in the terminal and in the UICC.

Input:

Output:

11.1.2.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Indication of application status (see table 11.8)
P2See table 11.9
LeEmpty, '00', or maximum length of data expected in response
Table 11.8: Coding of P1
b8b7b6b5b4b3B2b1Meaning
00000000No indication
00000001Current application is initialized in the terminal
00000010The terminal will initiate the termination of the current application
Table 11.9: Coding of P2
b8b7b6b5b4b3b2b1Meaning
00000000Response parameters and data are identical to the response parameters and data of the SELECT command
00000001The DF name TLV-object of the currently selected application is returned
00001100No data returned
Any other value RFU

11.1.3 READ BINARY

11.1.3.1 Functional description

This function reads a string of bytes from the current transparent EF. This function shall only be performed if the READ access condition for this EF is satisfied.

Input:

Output:

11.1.3.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1See table 11.10
P2Offset low
LcNot present
DataNot present
LeNumber of bytes to be read
Table 11.10: Coding of P1
b8B7b6b5b4b3b2b1Meaning
0XXXXXXXb7 to b1 is the offset to the first byte to read - P2 is the low part of the offset
100XXXXXSFI referencing used, b1 to b5 are the SFI and P2 is the offset to the first byte to read

Response data:

Byte(s)DescriptionLength
1 to LeData readLe

11.1.4 UPDATE BINARY

11.1.4.1 Functional parameters

This function updates the current transparent EF with a string of bytes. This function shall only be performed if the UPDATE access condition for this EF is satisfied. An update can be considered as a replacement of the string already present in the EF by the string given in the update command.

Input:

Output:

11.1.4.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1See table 11.10
P2Offset low
LcLength of the subsequent data field
DataString of data to be updated
LeNot present

Coding of parameter P1 and P2 are identical to the coding of P1 and P2 in the READ BINARY command.

11.1.5 READ RECORD

11.1.5.1 Functional description

This function reads one complete record in the current linear fixed or cyclic EF. The record to be read is described by the modes below. This function shall only be performed if the READ access condition for this EF is satisfied. The record pointer shall not be changed by an unsuccessful READ RECORD function.

Four modes are defined:

CURRENT: The current record is read. The record pointer is not affected.

ABSOLUTE: The record given by the record number is read. The record pointer is not affected.

NEXT:

The record pointer is incremented before the READ RECORD function is performed and the pointed record is read. If the record pointer has not been previously set within the selected EF, then READ RECORD (next) shall read the first record and set the record pointer to this record.

If the record pointer addresses the last record in a linear fixed EF, READ RECORD (next) shall not cause the record pointer to be changed, and no data shall be read.

If the record pointer addresses the last record in a cyclic EF, READ RECORD (next) shall set the record pointer to the first record in this EF and this record shall be read.

PREVIOUS: The record pointer is decremented before the READ RECORD function is performed and the pointed record is read. If the record pointer has not been previously set within the selected EF, then READ RECORD (previous) shall read the last record and set the record pointer to this record.

If the record pointer addresses the first record in a linear fixed EF, READ RECORD (previous) shall not cause the record pointer to be changed, and no data shall be read.

If the record pointer addresses the first record in a cyclic EF, READ RECORD (previous) shall set the record pointer to the last record in this EF and this record shall be read.

Input:

Output:

11.1.5.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Record number
P2Mode, see table 11.11
LcNot present
DataNot present
LeNumber of bytes to be read
Table 11.11: Coding of P2
b8b7b6b5b4b3b2b1Meaning
00000---Currently selected EF
XXXXX---Short File identifier (from 1 to 30)
-----010Next record
-----011Previous record
-----100Absolute/current mode, the record number is given in P1 with P1='00' denoting the current record

For the modes "next" and "previous" P1 has no significance within the scope of the present document and shall be set to '00' by the terminal.

Response data:

Byte(s)DescriptionLength
1 to LeData readLe

11.1.6 UPDATE RECORD

11.1.6.1 Functional description

This function updates one specific, complete record in the current linear fixed or cyclic EF. This function shall only be performed if the UPDATE access condition for this EF is satisfied. The UPDATE can be considered as a replacement of the relevant record data of the EF by the record data given in the command. The record pointer shall not be changed by an unsuccessful UPDATE RECORD function.

The record to be updated is described by the modes below. Four modes are defined of which only PREVIOUS is allowed for cyclic files:

CURRENT: The current record is updated. The record pointer is not affected.

ABSOLUTE: The record given by the record number is updated. The record pointer is not affected.

NEXT:

The record pointer is incremented before the UPDATE RECORD function is performed and the pointed record is updated. If the record pointer has not been previously set within the selected EF, then UPDATE RECORD (next) shall set the record pointer to the first record in this EF and this record shall be updated. If the record pointer addresses the last record in a linear fixed EF, UPDATE RECORD (next) shall not cause the record pointer to be changed, and no record shall be updated.

PREVIOUS: For a linear fixed EF the record pointer is decremented before the UPDATE RECORD function is performed and the pointed record is updated. If the record pointer has not been previously set within the selected EF, then UPDATE RECORD (previous) shall set the record pointer to the last record in this EF and this record shall be updated. If the record pointer addresses the first record in a linear fixed EF, UPDATE RECORD (previous) shall not cause the record pointer to be changed, and no record shall be updated.

For a cyclic EF the record containing the oldest data is updated, the record pointer is set to this record and this record becomes record number 1.

Input:

Output:

11.1.6.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Record number
P2Mode, see table 11.11
LcLength of the subsequent data field
DataString of data to be updated
LeNot present

Coding of parameter P2 is identical to the coding of P2 in READ RECORD command.

For the modes "next" and "previous" P1 has no significance and shall be set to '00' by the terminal.

11.1.7 SEARCH RECORD

11.1.7.1 Functional description

This function searches through a linear fixed or cyclic EF to find record(s) containing a specific pattern. This function shall only be performed if the READ access condition for this EF is satisfied. The search starts:

The response is either empty or contains the, up to the Le specified number of, record number(s) of the records that matches the search in the selected EF.

If one or more matches are found the record pointer shall be set to the first record where the search pattern was found.

Input:

Output:

11.1.7.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Record number ('00' indicates: current record)
P2See table 11.12
LcLength of the subsequent data field
Data- Simple search: search string - Enhanced search: search indication (2 bytes) followed by search string - Proprietary search: proprietary data
LeEmpty or maximum length of response data
Table 11.12: Coding of P2
b8b7b6b5b4b3b2b1Meaning
00000---Currently selected EF
XXXXX---Short File Identifier
11111---RFU
-----0XXRFU (see note)
-----10XSimple search. Usage of P1 as a record number
-----100Start forward search from record indicated in P1
-----101Start backward search from record indicated in P1
-----110Enhanced search - see table 11.13
-----111Proprietary search
NOTE:This value is reserved by ISO/IEC 7816-9 [16].
Table 11.13: Coding of the first byte of the search indication for enhanced search mode
b8b7b6b5b4b3b2b1Meaning
00000---The search starts in the record from the offset (absolute position) given in the second byte of the search indication
00001---The search starts in the record after the first occurrence of the value contained in the second byte of the search indication
-----0XXRFU (see note)
-----1XXUsage of value of P1 as a record number
-----100Start forward search form record indicated in P1
-----101Start backward search form record indicated in P1
-----110Start forward search from next record
-----111Start backward search form previous record
Any other valueRFU
NOTE:This value is reserved by ISO/IEC 7816-9 [16].

For the modes "forward search from next record" and "backward search from previous record", P1 has no significance within the scope of the present document and shall be set to '00'.

Response data:

Byte(s) DescriptionLength
0 to Le Record number(s)Le
NOTE:If Le is empty no record numbers will be returned.

11.1.8 INCREASE

11.1.8.1 Functional description

This function adds the value given by the terminal to the value of the last increased/updated record of the current cyclic EF, and stores the result into the oldest record. The record pointer is set to this record and this record becomes record number 1. This function can only be used if this EF has an INCREASE access condition assigned and this condition is fulfilled. The INCREASE access condition is indicated in the access rules using AM_DO tag '84'. Tag '84' indicates that the INS code for the INCREASE command is indicated as the value in the TLV object (instruction code '32'). The INCREASE command can only be used on files that refer to an access rule where this INS code is indicated as part of the rule.

The function does not perform the increase if the result would exceed the maximum value of the record (represented by all bytes set to 'FF').

Input:

Output:

11.1.8.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1See table 11.14
P2'00'
LcLength of the subsequent data field
DataValue to be added
LeLength of the response data
Table 11.14: Coding of P1
b8b7b6b5b4b3b2b1Meaning
00000000Increase the currently selected EF
100XXXXXSFI referencing used, b1 to b5 are the SFI
NOTE:All other values are RFU.

In this command, Lc is restricted to 0 < Lc < 128 and the maximum record length is limited to 127 bytes.

Response data:

Byte(s)DescriptionLength
1 to XValue of the increased recordX
X + 1 to X + LcValue which has been addedLc
NOTE:X denotes the length of the record.

11.1.9 VERIFY PIN

11.1.9.1 Functional description

11.1.9.1.1 PIN verification

This function initiates the comparison in the UICC of the PIN verification data sent from the terminal with the PIN reference data stored in the card. The security status set as a result of the verification is valid regardless on which logical channel the verification is performed. The verification process is subject to the following conditions being fulfilled:

If the access condition for a function to be performed on the last selected file is PIN, then a successful verification of the relevant PIN is required prior to the use of the function on this file unless the PIN is disabled.

If the PIN presented is correct, the number of remaining PIN attempts for that PIN shall be reset to its initial value 3.

If the PIN presented is false, the number of remaining PIN attempts for that PIN shall be decremented, regardless on which logical channel the VERIFY PIN command was issued. The UICC shall return SW1 SW2 = '63C2' after the first false PIN presentation. The UICC shall return SW1 SW2 = '63C1' after the second consecutive false PIN presentation, not necessarily in the same card session. After the third consecutive false PIN presentation, not necessarily in the same card session, the respective PIN shall be blocked and the UICC shall return SW1 SW2 = '63C0'. Any subsequent VERIFY PIN command applied to this blocked PIN shall then return SW1 SW2 = '6983'. The access condition can never be fulfilled until the UNBLOCK PIN function has been successfully performed on the respective PIN.

Input:

Output:

11.1.9.1.2 PIN retry counter

The VERIFY PIN with empty data field is used to retrieve the PIN retry counter from the UICC. This function is performed whether or not the relevant PIN is disabled or blocked (e.g. by 3 consecutive wrong PIN presentations).

The VERIFY PIN command is sent to the UICC with parameter P2 indicating the PIN for which the retry counter value is to be retrieved with an empty data field. The number of retries, if any, is indicated in the response by SW1 SW2 = '63CX', where X indicates the number of retries left.

A VERIFY PIN command with empty data field applied to a blocked PIN shall return SW1 SW2 = '63C0' or SW1 SW2 = '6983'.

Input:

Output:

void

11.1.9.3 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2Qualifier of the reference data, see table 11.15
LcEmpty or '08'
DataEMPTY or PIN value
LeNot present
Table 11.15: Coding of P2
b8b7b6b5b4b3b2b1Meaning
00000000Not supported
0-------Global reference data (e.g. MF specific PIN)
1-------Specific reference data (e.g. DF specific/application dependent PIN)
-XX-----'00' (other values are RFU)
---XXXXXReference data number ('01' to '1F')

The five least significant bits of parameter P2 specify the PIN key reference number (see clause 9.5.1).

Command data:

Byte(s)DescriptionLength
1 to 8PIN value8

11.1.10 CHANGE PIN

11.1.10.1 Functional description

The Change PIN command is used to initiate the comparison of the verification data with the PIN, and then to conditionally replace the existing PIN with the new PIN sent to the UICC in the command. Once successfully changed on a logical channel, the new value is immediately available to all channels.

This function assigns a new value to the relevant PIN subject to the following conditions being fulfilled:

The old and new PIN shall be presented.

If the old PIN presented is correct, the number of remaining PIN attempts for that PIN shall be reset to its initial value 3 and the new value for the PIN becomes valid.

If the old PIN presented is false, the number of remaining PIN attempts for that PIN shall be decremented and the value of the PIN is unchanged. After 3 consecutive false PIN presentations, not necessarily in the same card session, the respective PIN shall be blocked and the access condition can never be fulfilled until the UNBLOCK PIN function has been performed successfully on the respective PIN.

Input:

Output:

11.1.10.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2As specified for the VERIFY PIN command, see clause 11.1.9
LcLength of the subsequent data field = '10'
DataOld PIN value, new PIN value
LeNot present
NOTE: "Change PIN" is named "exchange reference data" in ISO/IEC 7816-8 [15].
Byte(s)DescriptionLength
1 to 8Old PIN value8
9 to 16New PIN value8

11.1.11 DISABLE PIN

11.1.11.1 Functional description

The Disable PIN command is used to switch off the requirement to compare the PIN verification data with the PIN reference data. The command also allows an indication whether to use an alternative global key reference, if enabled, or not when the application PIN is disabled. For universal PIN definition see clause 9.4.1. Usage of an alternative global key reference for user verification is indicated in parameter P1. If an alternative global key reference is used as a replacement for the application PIN, the usage qualifier in the PS_DO template data object for the alternative global key reference is set to "use" = '08'. The verification of the alternative global key reference shall be performed instead of the application PIN verification to get access to the application.

The UICC shall perform a validation of the SE after the successful execution of this command as the current SE may have changed and this shall affect the access to files.

NOTE 1: The access rules for the application must cater for the case that an alternative global key reference replaces the application PIN. It is the responsibility of the application to specify this.

The successful execution of this function has the effect that files protected by PIN are now accessible as if they were marked "ALWAYS", except in the case where the alternative global key reference is to be used as a replacement for the disabled PIN. In this case the access condition for files containing only a reference to the disabled PIN is the alternative global key reference. For files having more than one global key reference indicated in the access rules the access condition is "ALWAYS" after disabling on of the key references used in the access rules. The function DISABLE PIN shall not be executed by the selected application when PIN is already disabled or blocked.

NOTE 2: Every application must specify whether this function is applicable to all PINs defined for the application.

If the PIN presented is correct, the number of remaining PIN attempts shall be reset to its initial value 3 and PIN shall be disabled.

If the PIN presented is false, the number of remaining PIN attempts shall be decremented and PIN remains enabled. After 3 consecutive false PIN presentations, not necessarily in the same card session, the PIN shall be blocked and the access condition can never be fulfilled until the UNBLOCK PIN function has been successfully performed on PIN.

Input:

Output:

11.1.11.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1See table 11.16
P2As specified for the VERIFY PIN command, see clause 11.1.9
LcLength of the subsequent data = '08'
DataPIN value
LeNot present
Table 11.16: Coding of P1
b8b7b6b5b4b3b2b1Meaning
00000000Verification data present in data field
00000001Reserved by ISO/IEC 7816-8 [15]
1-------Verification data present, and use reference data number as verification replacement
-XX-----'00' (other values are RFU)
---XXXXXGlobal key reference data number ('01' to '1F')

Command data:

Byte(s)DescriptionLength
1 to 8PIN value8

11.1.12 ENABLE PIN

11.1.12.1 Functional description

The Enable PIN command is used to switch on the requirement to compare the PIN verification data with the PIN reference data. It is the reverse function of DISABLE PIN. If an alternative global key reference has been used as a replacement for the application PIN, the usage of the alternative global key reference as a replacement shall be disabled upon enabling the PIN for which the alternative global key reference has been a replacement (setting the usage qualifier in the PS_DO template data object for the alternative global key reference to do not use = '00').

The UICC shall perform a validation of the SE after the successful execution of this command as the current SE may have changed and this shall affect the access to files.

The function ENABLE PIN shall not be executed by the selected application when PIN is already enabled or blocked.

Every application shall specify whether this function is applicable to all PINs defined for the application.

If the PIN presented is correct, the number of remaining PIN attempts shall be reset to its initial value 3 and PIN shall be enabled.

If the PIN presented is false, the number of remaining PIN attempts shall be decremented and PIN remains disabled. After 3 consecutive false PIN presentations, not necessarily in the same card session, PIN shall be blocked and may optionally be set to "enabled". Once blocked, the PIN can only be unblocked using the UNBLOCK PIN function. If the PIN is blocked and "disabled", the access condition shall remain granted. If the PIN is blocked and "enabled", the access condition can never be fulfilled until the UNBLOCK PIN function has been successfully performed on PIN.

Input:

Output:

11.1.12.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2As specified for the VERIFY PIN command, see clause 11.1.9
LcLength of the subsequent data = '08'
DataPIN value
LeNot present

Command data:

Byte(s)DescriptionLength
1 to 8PIN value8

11.1.13 UNBLOCK PIN

11.1.13.1 Functional description

11.1.13.1.1 PIN unblocking

This function is used to reset the PIN retry counter to its initial value and then to conditionally set a new PIN value. This function may be performed whether or not the relevant PIN is blocked (e.g. by 3 consecutive wrong PIN presentations). This unblocking process is subject to the following condition being fulfilled:

If the UNBLOCK PIN presented is correct, the value of the PIN, presented together with the UNBLOCK PIN, is assigned to that PIN, the number of remaining UNBLOCK PIN attempts for that UNBLOCK PIN is reset to its initial value 10 and the number of remaining PIN attempts for that PIN is reset to its initial value 3. After a successful unblocking attempt the PIN is enabled and the relevant access condition level is satisfied the new PIN value is available for all channels.

If the presented UNBLOCK PIN is false, the number of remaining UNBLOCK PIN attempts for that UNBLOCK PIN, regardless on which logical channel the UNBLOCK PIN command was issued, shall be decremented. The UICC shall return SW1 SW2 = '63C9', '63C8', … '63C1' for up to the ninth consecutive false UNBLOCK PIN presentation, not necessarily in the same card session. After the tenth consecutive false UNBLOCK PIN presentation, not necessarily in the same card session, the respective UNBLOCK PIN shall be blocked and the UICC shall return SW1 SW2 = '63C0'. Any subsequent UNBLOCK PIN command applied to this blocked UNBLOCK PIN shall then return SW1 SW2 = '6983'. A false UNBLOCK PIN shall have no effect on the status of the respective PIN itself.

Input:

Output:

11.1.13.1.2 UNBLOCK PIN retry counter

The UNBLOCK PIN command with empty data field is used to retrieve the UNBLOCK PIN retry counter from the UICC. This function may be performed whether or not the relevant PIN is blocked (e.g. by 3 consecutive wrong PIN presentations) and whether or not the UNBLOCK PIN is blocked.

The UNBLOCK PIN command is sent to the UICC with parameter P2 indicating the PIN for which the UNBLOCK PIN retry counter value is to be retrieved with an empty data field. The number of retries, if any, is indicated in the response by SW1 SW2 ='63CX', where X indicates the number of retries left.

An UNBLOCK PIN command with empty data field applied to a blocked UNBLOCK PIN shall return SW1 SW2 = '63C0' or SW1 SW2 = '6983'.

Input:

Output:

11.1.13.2 Void

11.1.13.3 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2As specified for the VERIFY PIN command (see clause 11.1.9)
LcEmpty or '10'
DataEmpty or UNBLOCK PIN value, new PIN value
LeNot present

Command data:

Byte(s)DescriptionLength
1 to 8UNBLOCK PIN value8
9 to 16New PIN value8

11.1.14 DEACTIVATE FILE

11.1.14.1 Functional description

This function initiates a reversible deactivation of an EF. After a DEACTIVATE FILE function the respective flag in the file LCSI_DO shall be changed accordingly. This function shall only be performed if the DEACTIVATE FILE access condition for the EF is satisfied.

In case of successful execution of the command, the EF on which the command was applied becomes the current EF.

After an unsuccessful execution, the current EF and current DF shall remain the same as prior to the execution.

A deactivated file shall no longer be available within the selected application for any function except for the SELECT and the ACTIVATE FILE functions.

Input:

Output:

11.1.14.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1selection control, see table 11.17
P200
LcLength of subsequent data field or empty
DataFile ID or path to file, according to P1
LeNot present
Table 11.17: Coding of P1
b8b7b6b5b4b3b2b1Meaning
00000000Select EF by file id
00001000Select by path from MF
00001001Select by path from current DF
NOTE:All other values are RFU.

If P1 = P2 = '00' and the data field is empty, then the command applies on the current EF.

11.1.15 ACTIVATE FILE

11.1.15.1 Functional description

This function reactivates a deactivated EF. After an ACTIVATE FILE function the respective flag in the file LCSI_DO shall be changed accordingly. This function shall only be performed if the ACTIVATE FILE access condition for the EF is satisfied.

In case of successful execution of the command, the EF on which the command was applied becomes the current EF.

After an unsuccessful execution, the current EF and current DF shall remain the same as prior the execution.

Input:

Output:

11.1.15.2 Command parameters

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1As specified for the DEACTIVATE command (see clause 11.1.14.2)
P200
LcLength of subsequent data field or empty
DataFile ID or path to file, according to P1
LeNot present

If P1 = P2 = '00' and the data field is empty, then the command applies on the current EF.

11.1.16 AUTHENTICATE

11.1.16.1 Functional description

An appropriate application shall be selected in the UICC before issuing this command. The function initiates the computation of authentication data by the UICC using a challenge sent from the terminal and a secret stored in the UICC.

Input:

Output:

11.1.16.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2See table 11.18
LcLength of the subsequent data field
DataAuthentication related data
LeLength of the response data
Table 11.18: Coding of P2
b8b7b6b5b4b3b2B1Meaning
00000000No information given
0-------Global reference data (e.g. MF specific KEY)
1-------Specific reference data (e.g. DF specific/application dependent KEY)
-XX-----'00' (other values are RFU)
---XXXXXReference data number ('01' to '1F')

Command data:

Byte(s)Description Length
1 to Lc Authenticationrelated data (see note) Lc
NOTE:The command data must be specified by each application specific document.

Response data (generic):

Byte(s)Description Length
1 to Le Authentication related data (see note)Le
NOTE:The response data must be specified by each application specific document.

11.1.17 MANAGE CHANNEL

11.1.17.1 Functional description

This command opens and closes logical channels. The open function opens a new logical channel other than the basic channel '0'. The UICC shall support channel number assignment by the UICC. The close function explicitly closes a logical channel. When a channel has been successfully closed, the channel can be reassigned. The basic logical channel '0' is always available and cannot be closed.

Input:

· none.

Output:

11.1.17.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1Logical channel operation code, see table 11.19
P2See table 11.20
LcNot present
DataNot present
LeNot present or length of expected data
Table 11.19: Coding of P1
b8b7b6b5b4b3b2b1Meaning
00000000Open logical channel
10000000Close logical channel
NOTE:All other values are RFU.
Table 11.20: Coding of P2
b8b7b6b5b4b3b2b1Meaning
00000000if P1='00': Logical channel to be internally assigned by the UICC if P1≠'00': reserved
00000001Logical channel number 1
00000010Logical channel number 2
0 NOTE0 1:0 other0 values0 are0 RFU.11Logical channel number 3

NOTE 2: values '01', '02', '03' are valid only with P1='80'.

Response data:

Byte(s)DescriptionLength
1Logical channel number1

Response data shall only be returned if the value of the parameters P1-P2 of the command is '0000'.

11.1.18 GET CHALLENGE

11.1.18.1 Functional description

This function is used to create a random number. The generated random number is associated with the logical channel specified in the GET CHALLENGE command CLA. The maximum length of the random number returned by the UICC is specified by the Le parameter in the command parameters data.

The quality of the random number generated by this command is determined by the application and is outside the scope of the present document.

The generated random number may be used internally by the UICC in procedures specified by the application. The validity of the random number is at least for the next command, on the same logical channel, following the GET CHALLENGE command if not specified differently by the application. The random number referenced is always the latest generated on the logical channel specified in the CLA by the command referencing the usage of a generated random number.

Input:

Output:

11.1.18.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcNot present
DataNot present
LeMaximum length of response data

Response data:

Byte(s)DescriptionLength
1 to LrRandom numberLr

11.2 CAT commands

11.2.1 TERMINAL PROFILE

11.2.1.1 Functional description

This function is used by the terminal to transmit its CAT capabilities to the applications present on the UICC.

Input:

Output:

11.2.1.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcLength of the subsequent data field
DataStructure and coding defined in TS 102 223 [4]
LeNot present

11.2.2 ENVELOPE

11.2.2.1 Functional description

This function is used to transfer CAT information from the UE to the UICC.

Input:

Output:

11.2.2.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcLength of the subsequent data field
DataStructure and coding defined in TS 102 223 [4]
LeEmpty or maximum length of response data

Response data:

11.2.3 FETCH

11.2.3.1 Functional description

This function is used to transfer a proactive command from the UICC to the terminal (e.g. from a CAT application). Input:

Output:

11.2.3.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcNot present
DataNot present
LeLength of expected data

Response data:

11.2.4 TERMINAL RESPONSE

11.2.4.1 Functional description

This function is used to transfer from the terminal to the UICC the response to a previously fetched proactive command (e.g. a CAT command).

Input:

Output:

11.2.4.2 Command parameters and data

CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcLength of the subsequent data field
DataStructure and coding defined in TS 102 223 [4]
LeNot present

12 Transmission oriented commands

This clause lists all transport specific commands. Currently there is only one such command.

12.1 T=0 specific commands

12.1.1 GET RESPONSE

12.1.1.1 Functional description

The command is used to transmit APDUs from the card to the terminal, which otherwise could not be transferred by the protocol.

The response data depends on the preceding command. Response data is available when it is indicated in the procedure byte, see table 7.1, or status byte, see table 7.2. If the command GET RESPONSE is executed, it is required that it is executed immediately after the command it is related to (no other command shall come between the command/response pair and the command GET RESPONSE). If the sequence is not respected, the selected application shall send the status information "technical problem, no precise diagnosis" as a reaction to the GET RESPONSE.

The response data itself is defined in the clause for the corresponding command.

Because there is no interleaving of commands between logical channels, the terminal shall send the GET RESPONSE command on the same logical channel before sending a command APDU in another logical channel. Otherwise, the response is lost.

12.1.1.2 Command parameters

Table 12.1: Parameters for GET RESPONSE
CodeValue
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcNot present
DataNot present
Le'00' or value of SW2 of the previous command

Response parameters and data:

NOTE: Since the MF is implicitly selected after UICC activation, GET RESPONSE is also allowed as the first command after activation for only GSM ME. 3G ME should send SELECT MF or STATUS command with FCP response.

13 Application independent files

13.1 EFDIR

EF DIR is a linear fixed file under the MF and is under the responsibility of the issuer.

Table 13.1: EF DIR at MF-level
Identifier: '2F00'Structure: Linear fixedMandatory
SFI: Mandatory
Record size: X bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
BytesDescriptionM/OLength
1 to XApplication template TLV objectMX bytes

The EF consists of one or more records, with each record able to hold one entry. Each entry in the EF DIR is an application template Data Object (DO) as defined in ISO/IEC 7816-5 [13]. An application template DO is a constructed BER-TLV object with a maximum length of 127 bytes and has a mandatory AID DO. Within the scope of the present document, all other DOs are optional.

In table 13.2 the coding of the mandatory DOs and the optional DOs that has special meaning to the present document. All other DOs are according to ISO/IEC 7816-5 [13].

Table 13.2: Coding of an application template entry
LengthDescriptionStatus
1Application template tag = '61'M
1Length of the application template = '03'-'7F'M
1Application Identifier tag = '4F'M
1AID length = '01'-'10'M
'01' to '10'AID value. For 3G applications, see TS 101 220 [3]M
1Application label tag = '50'O
1Application label lengthO
note 1Application label valueO

NOTE 1: The application label is a DO that contains a string of bytes provided by the application provider to be shown to the user for information, e.g. operator name. The value part of the application label shall be coded according to annex A. In ISO/IEC 7816-5 [13] the application label is limited to 16 bytes, this does not apply to the present document it is however recommended that the number of bytes does not exceed 32.

NOTE 2: Other DOs from ISO/IEC 7816-5 [13] may, at the application issuer's discretion, be present as well.

13.2 EFICCID (ICC Identification)

This EF provides a unique identification number for the UICC.

Table 13.3: EF ICCID at MF-level
Identifier: '2FE2'Structure: transparentMandatory
SFI: Optional
File size: 10 bytesUpdate activity: low
Access Conditions:
READALW
UPDATENEV
DEACTIVATEADM
ACTIVATEADM
BytesDescriptionM/OLength
1 to 10Identification numberM10 bytes

Purpose: card identification number.

Byte 1:

Byte 2:

etc.

b8 B7 b6 b5 b4 b3 b2 b1

LSB of Digit 1

:

:

MSB of Digit 1

LSB of Digit 2

:

:

MSB of Digit 2

13.3 EFPL (Preferred Languages)

This EF contains the codes for up to n languages. This information, determined by the user/operator, defines the preferred languages of the user, for the UICC, in order of priority.

Table 13.4: EF PL at MF-level
Identifier: '2F 05'Structure: transparentMandatory
SFI: Mandatory
File size: 2n bytesUpdate activity: low
Access Conditions:
READALW
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
BytesDescriptionM/O Length
1 to 21 st language code (highest prior)M 2 bytes
3 to 42 nd language codeO 2 bytes
2n-1 to 2nnth language code (lowest prior)O 2 bytes

Coding: each language code is a pair of alpha-numeric characters, defined in ISO 639 [6]. Each alphanumeric character shall be coded on one byte using the SMS default 7-bit coded alphabet as defined in TS 123 038 [1] with bit 8 set to 0.

Unused language entries shall be set to 'FF FF'.

13.4 EFARR (Access Rule Reference)

This EF contains the access rules for files located under the MF in the UICC. If the security attribute tag '8B' is indicated in the FCP it contains a reference to a record in this file.

Table 13.5: EF ARR at MF-level
Identifier: '2F06'Structure: Linear fixedOptional
SFI: Optional
Record length: X bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
BytesDescriptionM/OLength
1 to XAccess Rule TLV data objectsMX bytes

This EF contains one or more records containing access rule information according to the referenced format as defined in ISO/IEC 7816-9 [16]. Each record represents an access rule. Unused bytes in the record are set to 'FF'.

14 Application independent protocol

14.1 File related procedures

14.1.1 Reading an EF

Reading of an EF can be done in two different ways.

  1. If the short file identifiers are used the following procedure applies:
  2. if short file identifiers are used, EFs that support SFI within the Current Directory can be read without explicitly selecting the EF. The terminal selects the DF or ADF and sends a READ command. This contains the short file identifier of the EF to be read and the location of the data to be read. If the access condition for READ is fulfilled, the application sends the requested data contained in the EF to the terminal. If the access condition is not fulfilled, no data will be sent and an error code will be returned.
  3. If the short file identifiers are not used the following procedure applies:
  4. the terminal selects the EF and sends a READ command. This contains the location of the data to be read. If the access condition for READ is fulfilled, the application sends the requested data contained in the EF to the terminal. If the access condition is not fulfilled, no data will be sent and an error code will be returned.

14.1.2 Updating an EF

Updating of an EF can be done in two different ways:

  1. If the short file identifiers are used the following procedure applies:
  2. if short file identifiers are used, EFs that support SFI within the Current Directory can be updated without explicitly selecting the EF. The terminal selects the DF or ADF and sends an UPDATE command. This contains the short file identifier of the EF and the location of the data to be updated and the new data to be stored. If the access condition for UPDATE is fulfilled, the application updates the selected EF by replacing the existing data in the EF with that contained in the command. If the access condition is not fulfilled, the data existing in the EF will be unchanged, the new data will not be stored, and an error code will be returned.
  3. If the short file identifiers are not used the following procedure applies:
  4. the terminal selects the EF and sends an UPDATE command. This contains the location of the data to be updated and the new data to be stored. If the access condition for UPDATE is fulfilled, the application updates the selected EF by replacing the existing data in the EF with that contained in the command. If the access condition is not fulfilled, the data existing in the EF will be unchanged, the new data will not be stored, and an error code will be returned.

14.1.3 Increasing an EF

Increasing of an EF can be done in two different ways:

  1. If the short file identifiers are used the following procedure applies:
  2. if short file identifiers are used, EFs that support SFI within the Current Directory can be increased without explicitly selecting the EF. The terminal selects the DF or ADF and sends an INCREASE command. This contains the short file identifier of the EF and the value which has to be added to the contents of the last updated/increased record. If the access condition for INCREASE is fulfilled, the application increases the existing value of the EF by the data contained in the command, and stores the result. If the access condition is not fulfilled, the data existing in the EF will be unchanged and an error code will be returned.
  1. If the short file identifiers are not used the following procedure applies:
  2. the terminal selects the EF and sends an INCREASE command. This contains the value which has to be added to the contents of the last updated/increased record. If the access condition for INCREASE is fulfilled, the application increases the existing value of the EF by the data contained in the command, and stores the result. If the access condition is not fulfilled, the data existing in the EF will be unchanged and an error code will be returned.
  3. NOTE: The identification of the data within an EF to be acted upon by the above procedures is specified within the command. For the procedures in clauses 14.1.1 and 14.1.2 this data may have been previously identified using a SEARCH RECORD command, e.g. searching for an alphanumeric pattern.

14.2 PIN related procedures

A successful completion of one of the following procedures grants the access right of the corresponding PIN for an application session. This right is valid for all files within the application protected by this PIN.

After a third consecutive unsuccessful completion of one of the following procedures associated to the same PIN, not necessarily in the same application session, the PIN becomes "blocked" and if the PIN status is set "enabled", the access right previously granted by this PIN is lost immediately.

An access right is not granted if any of the following procedures are aborted.

14.2.1 PIN verification

The terminal checks the PIN and the following procedures apply:

14.2.2 PIN value substitution

The terminal checks the PIN and the following procedures apply:

14.2.3 PIN disabling

PIN enabling and disabling/disabling and replacement may be disallowed by an application. If it is allowed then the following procedures shall be followed:

Disabling and replacement

Disabling, no replacement

14.2.4 PIN enabling

PIN enabling and disabling may be disallowed by an application. If it is allowed then the following procedures shall be followed:

14.2.5 PIN unblocking

The execution of the PIN unblocking procedure is independent of whether or not the PIN is "blocked".

The terminal checks if the UNBLOCK PIN is "blocked". If the UNBLOCK PIN is "blocked", the procedure ends and is finished unsuccessfully.

If the UNBLOCK PIN is not "blocked", the terminal uses the UNBLOCK PIN function. If the UNBLOCK PIN presented by the terminal is equal to the corresponding UNBLOCK PIN of the application, the relevant PIN becomes "unblocked" and the procedure is finished successfully. If the UNBLOCK PIN presented by the terminal is not equal to the corresponding UNBLOCK PIN of the application, the procedure ends and is finished unsuccessfully.

14.3 Application selection procedures

14.3.1 Application selection by use of the EFDIR file

Application selection by use of the EF DIR file is the procedure where the terminal reads the content of the EF DIR file and presents the list of applications to the user whom can then make select one or more applications to activate.

The terminal performs the read procedure with EF DIR and presents the applications that it supports to the user who may make a selection. If only one supported application is found this may be implicitly selected.

14.3.2 Direct application selection

An application may be selected, without reading the content of the EF DIR file, by performing the SELECT procedure with the AID of the application to be selected.

14.3.3 Direct application selection with partial AID

See clause 8.5.1.2.

14.4 General application related procedures

14.4.1 Application session activation

The terminal performs the SELECT function with the AID of the selected application as a parameter.

If the SELECT function ends successfully the selected application's initialization procedure is executed. If the initialization procedure ends successfully the UICC enters the operation state. If the initialization procedure does not end successfully, the UICC remains in the application management state and sends an indication to the user that it was not possible to activate the selected application.

14.4.2 UICC application interrogation

The list of applications residing in the UICC can be read at anytime when the UICC is not inactive.

Request:

The terminal performs the read procedure with EF DIR .

14.4.3 UICC application session termination

An application session can be terminated at any time when the UICC is not inactive.

14.5 Miscellaneous procedures

14.5.1 UICC activation

After activation of the UICC, as defined in clause 4.5, the terminal requests the Preferred Language (EF PL ). If the terminal supports CAT, it shall perform the CAT initialization procedure. The terminal then performs an application selection procedure according to clause 14.3.

14.5.2 UICC presence detection

If an application present on the UICC has the requirement to ensure that the UICC has not been removed during a card session the following procedure applies. The terminal sends, at frequent intervals, a STATUS command on the UICC-terminal interface. The STATUS command shall be issued within a period of inactivity on the UICC-terminal interface. The period of inactivity and the conditions under which the presence detection takes place is specified by the applications active during the card session. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If no response data is received to this STATUS command the terminal shall take the appropriate actions after the work waiting time (T=0) or block waiting time (T=1) has expired as specified by the applications active. If the DF indicated in an error free response to a STATUS command is not the same as that which was indicated in the previous response, or accessed by the previous command, then the terminal shall take appropriate actions as specified by the applications active during the card session. This procedure shall be used in addition to a mechanical or other device used to detect the removal of a UICC.

14.5.3 UICC preferred language request

Request:

Update:

The terminal performs the read procedure with EF PL .

The terminal performs the update procedure with EF PL .

14.5.4 UICC logical channels

A UICC may offer the possibility to run several selectable applications in parallel. This is done with the logical channels mechanism. Only one selectable application can run at a given time in a given logical channel.

14.6 CAT related procedures

The higher level procedures, and contents and coding of the commands, are given in TS 102 223 [4]. Procedures relating to the transmission of commands and responses across the terminal-UICC interface are given in this clause. A UICC or terminal supporting CAT shall conform to the requirements given in this clause.

14.6.1 CAT Initialization procedure

A terminal supporting CAT shall send the TERMINAL PROFILE C-APDU. A UICC supporting CAT shall return the response status words (SW1 SW2) '90 00' or '91 XX'. If any other value is returned, the terminal shall assume that CAT is not supported. In case of proactive command pending, the terminal shall then start the proactive polling procedure with the default value.

14.6.2 Proactive polling

During idle mode the terminal shall send STATUS commands to the UICC at intervals no longer than the interval negotiated with the UICC (see TS 102 223 [4]). During a call the UICC presence detection applies. The default value for the proactive polling is the same as for the presence detection procedure.

14.6.3 Support of commands

A terminal supporting CAT shall support the commands TERMINAL PROFILE, ENVELOPE, FETCH and TERMINAL RESPONSE.

14.6.4 Support of response codes

A terminal supporting CAT shall support the response status words (SW1 SW2) '91 XX' and '93 00'.

These responses shall never be used if the terminal does not support CAT.

14.6.5 Independence of applications and CAT tasks

Application and CAT operation shall be logically independent, both in the UICC and in the terminal. Specifically, this means:

14.6.6 Use of BUSY status response

If for any reason the CAT task of the UICC cannot process an ENVELOPE command issued by the terminal at present (e.g. other CAT processes are already running), the UICC can respond with a status response of '93 00'. The terminal may re-issue the command at a later stage.

The BUSY status response has no impact on e.g. USIM operation.

14.6.7 Additional processing time

The Transport Protocol provides a mechanism for the UICC to obtain additional processing time (i.e. NULL procedure byte for T=0 and Work Waiting time extension (WTX) for T=1) before supplying the response part of a command-response pair, during which time the terminal is unable to send further commands to the UICC.

If a CAT activity in the UICC runs for too long, this may prevent the terminal from sending e.g. USIM commands which are time-critical, e.g. INTERNAL AUTHENTICATE. A MORE TIME command is defined in TS 102 223 [4], which ensures that the CAT task in the UICC gets additional processing time, while at the same time freeing the UICC/terminal interface. The MORE TIME command should be used in preference to the transport protocol specific mechanisms for obtaining additional processing time.

Annex A (normative):

UCS2 coding of Alpha fields for files residing on the UICC

If 16 bit UCS2 characters as defined in ISO/IEC 10646-1 [17] are used in an alpha field, the coding can take one of three forms. If the terminal supports UCS2 coding of alpha fields in the UICC, the terminal shall support all three coding schemes for character sets containing 128 characters or less; for character sets containing more than 128 characters, the terminal shall at least support the first coding scheme. If the alpha field record contains GSM default alphabet characters only, then none of these schemes shall be used in that record. Within a record, only one coding scheme, either the GSM default alphabet (see TS 123 038 [1]), or one of the three described below, shall be used.

  1. If the first byte in the alpha string is '80', then the remaining bytes are 16 bit UCS2 characters, with the more significant byte (MSB) of the UCS2 character coded in the lower numbered byte of the alpha field, and the less significant byte (LSB) of the UCS2 character is coded in the higher numbered alpha field byte, i.e. byte 2 of the alpha field contains the more significant byte (MSB) of the first UCS2 character, and byte 3 of the alpha field contains the less significant byte (LSB) of the first UCS2 character (as shown below). Unused bytes shall be set to 'FF', and if the alpha field is an even number of bytes in length, then the last (unusable) byte shall be set to 'FF'.

EXAMPLE 1:

Byte 1Byte 2Byte 3Byte 4Byte 5Byte 6Byte 7Byte 8Byte 9
'80'Ch1 MSBCh1 LSBCh2 MSBCh2 LSBCh3 MSBCh3 LSB'FF''FF'
  1. If the first byte of the alpha string is set to '81', then the second byte contains a value indicating the number of characters in the string, and the third byte contains an 8 bit number which defines bits 15 to 8 of a 16 bit base pointer, where bit 16 is set to zero, and bits 7 to 1 are also set to zero. These sixteen bits constitute a base pointer to a "half-page" in the UCS2 code space, to be used with some or all of the remaining bytes in the string. The fourth and subsequent bytes in the string contain codings as follows; if bit 8 of the byte is set to zero, the remaining 7 bits of the byte contain a GSM Default Alphabet character, whereas if bit 8 of the byte is set to one, then the remaining seven bits are an offset value added to the 16 bit base pointer defined earlier, and the resultant 16 bit value is a UCS2 code point, and completely defines a UCS2 character.

EXAMPLE 2:

Byte 1Byte 2Byte 3Byte 4Byte 5Byte 6Byte 7Byte 8Byte 9
'81''05''13''53''95''A6''XX''FF''FF'

In the above example:

  1. If the first byte of the alpha string is set to '82', then the second byte contains a value indicating the number of characters in the string, and the third and fourth bytes contain a 16 bit number which defines the complete 16 bit base pointer to a "half-page" in the UCS2 code space, for use with some or all of the remaining bytes in the string. The fifth and subsequent bytes in the string contain codings as follows; if bit 8 of the byte is set to zero, the remaining 7 bits of the byte contain a GSM Default Alphabet character, whereas if bit 8 of the byte is set to one, the remaining seven bits are an offset value added to the base pointer defined in bytes three and four, and the resultant 16 bit value is a UCS2 code point, and defines a UCS2 character.

EXAMPLE 3:

Byte 1Byte 2Byte 3Byte 4Byte 5Byte 6Byte 7Byte 8Byte 9
'82''05''05''30''2D''82''D3''2D''31'

In the above example:

Annex B (informative): Main states of a UICC

A UICC complying with the present document has the following states of operation:

Figure B.1: UICC states

Annex C (informative):

APDU protocol transmission examples

C.1 Exchanges Using T=0

The following examples illustrate exchanges of data and procedure bytes between the terminal and the UICC.

Note the following:

The examples in clauses C.1.1.1 to C.1.1.4 illustrate typical exchanges using case 1 to 4 commands. The examples in the clauses C.1.1.5 and C.1.1.6 illustrate the more extensive use of procedure bytes '61 XX' when used with case 2 and 4 commands. The example in clause C.1.1.7 illustrates a warning condition with a case 4 command.

C.1.1 Case 1 command

A C-APDU of {CLA INS P1 P2} is passed from the terminal to the UICC (note that P3 of the C-TPDU is set to '00').

An R-APDU of {90 00} is returned from the UICC to the terminal.

C.1.2 Case 2 command

In this first example, a C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc < 256 bytes.

An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.

In this second example, a C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc = 256 bytes.

An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.

C.1.3 Case 3 command

A C-APDU of {CLA INS P1 P2 Lc [Data(Lc)]} is passed from the terminal to the UICC.

An R-APDU of {90 00} is returned from the UICC to the terminal.

C.1.4 Case 4 command

A C-APDU of {CLA INS P1 P2 Lc [Data (Lc)] Le = 00} is passed from the terminal to the UICC.

An R-APDU of {[Data(Luicc)] 90 00} is returned from the UICC to the terminal.

The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.5 Case 2 commands Using the '61' and '6C' procedure bytes

A C-APDU of {CLA INS P1 P2 Le = 00} is passed from the terminal to the UICC with Luicc < 256 bytes.

TerminalUICC
[CLA INS P1 P2 P3=00]
C-TPDUbarb4rightbarb4left 6C Luicc
[CLA INS P1 P2 Luicc] barb4rightbarb4left 61 XX
GET RESPONSE[0X C0 00 00 YY] barb4rightC0 [Data(YY)] 61 ZZ
[0X C0 00 00 ZZ] barb4rightC0 [Data(ZZ)] 90
barb4left 00

Where YY ≤ XX,

An R-APDU of {[Data(YY + ZZ)] 90 00} is returned from the UICC to the terminal.

The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.6 Case 4 command Using the '61' procedure byte

A C-APDU of {CLA INS P1 P2 Lc [Data Lc] Le = 00} is passed from the terminal to the UICC.

TerminalUICC
C-TPDU[CLA INS P1 P2 P3=Lc] barb4right
barb4left [INS]
[Data(Lc)] barb4right
barb4left 61 XX
GET RESPONSE[0X C0 00 00 XX] barb4right
barb4left C0 [Data(XX)] 61 YY
[0X C0 00 00 YY]barb4right
barb4left C0 [Data(YY)] 90 00

An R-APDU of {[Data(XX + YY)] 90 00} is returned from the UICC to the terminal.

The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

C.1.7 Case 4 command with warning condition

A C-APDU of {CLA INS P1 P2 Lc [Data Lc] Le = 00} is passed from the terminal to the UICC.

TerminalUICC
C-TPDU[CLA INS P1 P2 P3=Lc]barb4right
barb4left[INS]
[Data(Lc)]barb4right
barb4left62 XX
GET RESPONSE[0X0 C0 00 00 00]barb4right
barb4left6C Luicc
[0X C0 00 00 Luicc]barb4right
barb4leftC0 [Data(Luicc)] 90 00

An R-APDU of {[Data(Luicc)] 62 XX} is returned from the terminal to the UICC containing the data returned together with the warning status bytes.

The GET RESPONSE command is sent on the same logical channel as the C-TPDU.

Annex D (informative): ATR examples

This annex gives examples of ATRs that can be returned by a UICC after a reset.

EXAMPLE 1: Cold reset for a T=0 protocol only UICC.
CharacterValueDescription
TS'3B' or '3F'Indicates direct or inverse convention
T0'97'TA1 and TD1 are present 7 bytes of historical bytes
TA1'95'Clock rate conversion factor FI=9 (F=512) Baud rate adjustment factor DI=5 (D=16)
TD1'80'TD2 only is present
TD2'1F'TA3 only is present Global interface bytes following
TA3'42'Clock stop supported (low electrical state) 3V UICC
T1'80'
T2'31'Card data services
T3'A0'SELECT by AID supported EFDIR present
T4'73'Card capabilities
T5'BE'SFI supported
T6'21'Data Coding Byte
T7'00'No extended Lc and Le No Logical channels supported
TCK'XX'Check byte
EXAMPLE 2: Cold reset for a T=0 and T=1 protocol UICC.
CharacterValueDescription
TS'3B' or '3F'Indicates direct or inverse convention
T0'97'TA1, and TD1 are present 7 bytes of historical bytes
TA1'95'Clock rate conversion factor FI=9 (F=512) Baud rate adjustment factor DI=5 (D=16)
TD1'80'Only TD2 is present Protocol T=0 supported by UICC
TD2'B1'TA3, TB3 and TD3 are present Protocol T=1 supported by UICC
TA3'FE'IFSC is 254 bytes long
TB3'00'Block Waiting Integer=0 Character Waiting Integer=0
TD3'1F'Only TA4 is present Global interface bytes following
TA4'42'Clock stop supported (low electrical state) 3V UICC
T1'80'
T2'31'Card data services
T3'A0'SELECT by AID supported EFDIR present
T4'73'Card capabilities
T5'BE'SFI supported
T6'21'Data Coding Byte
T7'00'No extended Lc and Le No Logical channels supported
TCK'XX'Check byte
EXAMPLE 3: Warm reset (specific mode) and T=1 protocol requested by the UICC.
CharacterValueDescription
TS'3B' or '3F'Indicates direct or inverse convention
T0'97'TA1, and TD1 are present 7 bytes of historical bytes
TA1'95'Clock rate conversion factor FI=9 (F=512) Baud rate adjustment factor DI=5 (D=16)
TD1'91'TA2 and TD2 are present Protocol T=1 supported by UICC
TA2'81'Protocol T=1 used in specific mode Parameters indicated by the interface bytes, and card is not able to change mode
TD2'B1'TA3, TB3 and TD3 are present Protocol T=1 supported by UICC
TA3'FE'IFSC is 254 bytes long
TB3'00'Block Waiting Integer=0 Character Waiting Integer=0
TD3'1F'Only TA4 is present Global interface bytes following
TA4'42'Clock stop supported (low electrical state)
T1'80'
T2'31'Card data services
T3'A0'SELECT by AID supported EF DIR present
T4'73'Card capabilities
T5'BE'SFI supported
T6'21'Data Coding Byte
T7'00'No extended Lc and Le No Logical channels supported
TCK'XX'Check byte

Annex E (informative):

Security attributes mechanisms and examples

E.1 Coding

Two codings are defined:

The security conditions for bits not set to '1' in the AM byte are set to NEVer by default.

E.2 Compact format

The compact format access rule is indicated by tag '8C' in the FCP. An access rule in this format is encoded with:

E.2.1 AM byte

The AM byte conveys two types of information:

If b8 in the AM byte is set to '0' the AM byte is followed by a number of SC bytes equal to the number of bits set to '1' in the AM byte (excluding b8). Each SC bytes codes the conditions relevant to a set of commands, in the same order (b7 to b1) as in the AM byte. When b8 is set to '1' the usage of b7 to b4 is proprietary.

When multiple sets of an AM byte and one or more corresponding SC bytes are present in the value field of the DO, tag '8C', they represent an OR condition.

E.2.2 SC byte

The SC byte specifies which security mechanisms are necessary to conform to the access rules, see ISO/IEC 7816-9 [16]. The 4 most significant bits (b8 to b5) indicate the required security condition. An SE may be specified in bits b4 to b1. If an SE is specified, the mechanisms that may be defined in it for external authentication, user authentication and command protection shall be used, if indicated by bits b4 to b1.

If bit b8 is set to '1' all conditions in bits b7 to b5 shall be satisfied. If bit b8 is set to '0' at least one of the conditions set in bits b7 to b5 shall be satisfied. If b7 is set to '1', the CRT of the SE indicated in bits b4 to b1 describes whether secure messaging shall apply to the command APDU, the response APDU or both.

E.2.3 Examples

For EFs with the access condition ALW for READ and UPDATE the security attribute would look as follows:

TagLAMSCSC
'8C''03''03''00''00'

For EFs with the access condition ALW for READ and NEV for all other access conditions the security attribute would look as follows:

TagLAMSC
'8C''02''01''00'

For EF DIR and EF ICC the access rule would be as follows. READ is set to ALW and UPDATE, DEACTIVATE and ACTIVATE is set to ADM. The ADM condition is indicated as a user authentication. The key reference is implicitly known.

TagLAMSCSCSCSC
'8C''05''1B''90''90'90''00'

E.3 Expanded format

In the expanded format AM_DOs and SC_DOs are used to create the access rules. The expanded format access rule is indicated by tag 'AB' in the FCP. An access rule in this format is encoded with an AM_DO followed by a sequence of SC_DOs.

E.3.1 AM_DO

The AM_DO is defined in ISO/IEC 7816-9 [16]. The content of the AM_DO is defined by the tag value. Tag '80' indicates that the AM_DO contains an AM byte. Tags '81' to '8F' indicates that the AM_DO contains a command description. The content of the command description is dependent upon the tag value as defined in ISO/IEC 7816-9 [16]. Tag '9C' indicates that the AM_DO contains a proprietary state machine description.

When multiple sets of an AM_DO and one or more corresponding SC_DOs are present in the value field of the DO, tag 'AB', they represent an OR condition.

E.3.2 SC_DO

The SC_DO is defined in ISO/IEC 7816-9 [16]. The SC_DO definition contains an OR and an AND template. Several SC_DOs may be attached to a particular operation.

E.3.3 Access rule referencing

Access rules in expanded format (AM_DOs and SC_DOs) may be stored in a linear fixed EF, each record contain one or more rules, as defined in ISO/IEC 7816-9 [16]. The access rule file may be an internal file, referenced implicitly, or may be referenced explicitly, e.g. by a file ID. The access rule stored in a file is indicated by tag '8B' in the FCP. The value of this DO contains at least one record number, called ARR. The DO can contain:

E.3.4 Examples

The access rule for EF PL would look as follows. The READ and SEARCH access condition is ALWays. The UPDATE access condition is application1 PIN or application2 PIN.

TagLAM_DO TagLVOR TagLSC_DO TagLKey Ref TagLV UsageQualifier Tag LVSC_DO TagLKey Ref TagLVUsage QualifierLVAM_DO Tag LV SC_DO TagL
'AB''1A''80''01''02''A0''10''A4''06''83''01''01'95''01' '08''A4''06''83''01' '02''95''01''08' '01''80''01' '90''00'

Annex F (informative):

Example of contents of EFARR '2F06'

F.1 Sample content of the EFARR

This annex contains an example of the contents of EF ARR '2F06'.

Table F.1: Access rule references for files located at the MF level
SCDO: CRTSecurity ConditionLenValue
ARR RecordApplic ableAccess ConditionAM DOLENValueTagKey Ref TagLenValueUsage Qualifier TagLenValue
01EFREAD UPDATE/ DE-ACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''90' 'A4'ALW Level 5'00' '06''83''01''0X''95''01''YY'
02EFREAD DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '18'''90' 'A4'ALW Level 5'00' '06''83''01''0X''95''01''YY'
03EFREAD UPDATE DEACTIVATE/ ACTIVATE'80' '80' '80''01' '01' '01''01' '02' '18''90' 'A4' 'A4'ALW PIN Level 5'00' '06' '06''83' '83''01' '01''01' '0X''95' '95''01' '01''01' 'YY'

The value X in table F.1 shall be according to level 5 in table 9.3. The value 'YY' in table F.1 shall be in accordance with ISO/IEC 7816-9 [16].

As an example, those records could be used as follows: the first record of EF ARR can be the access rule of EF DIR , the second record of EF ARR can be the access rule of EF ICCID , the third record of EF ARR can be the access rule of EF PL .

Annex G (informative):

Access Rules Referencing (ARR)

G.1 Sample content of EFARR

This annex contains a set of access rule examples that are stored in EF ARR . The access rules are referenced using tag'8B' in the FCP.

The following definitions apply:

Table G.1: Application Access Rule References
ARR RecordApplic ableAccess ConditionAM DOLENValueSCDO: CRT TagSecurity ConditionLenKey RefLenValueValue Usage QualifierLenValue
01EFREAD'80''01''01''90'ALW'00'Tag ---Tag ---
02EFREAD UPDATE DEACTIVATE/ ACTIVATE'80' '80' '80''01' '01' '01''01' '02' '18''90' 'A4' 'A4'ALW PIN Appl 1 global Level 5/Level 6'00' '06' '06''83' '83''01' '01''01' 'YZ''95' '95''01' '01''08' 'XX'
03EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''A4' 'A4'PIN Appl 1 global Level 5/Level 6'06' '06''83' '83''01' '01''01' 'YZ''95' '95''01' '01''08' 'XX'
04EFREAD/UPDATE DEACTIVATE/ ACTIVATE'80' '80''01' '01''03' '18''A4' 'A4'PIN Appl 1 global Level 5/Level 6'06' '06''83' '83''01' '01''01' 'YZ''95' '95''01' '01''08' 'XX'
05EFREAD UPDATE DEACTIVATE/ ACTIVATE'80' '80' '80''01' '01' '01''01' '02' '18''A4' 'A4' 'A4'PIN Appl 1 global PIN2 Appl 1 local Level 5/Level 6'00' '06' '06''83' '83' '83''01' '01' '01''01' '81' 'YZ''95' '95' '95''01' '01' '01''08' '08' 'XX'
06EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''90' 'A4'ALW Level 5/Level 6'00' '06''83''01''YZ''95''01''XX'
07EFREAD/UPDATE/ ACTIVATE DEACTIVATE'80' '80''01' '01''13' '08''A4' 'A4'PIN Appl 1 global Level 5/Level 6'06' '06''83' '83''01' '01''01' 'YZ''95' '95''01' '01''08' 'XX'
08EFREAD/UPDATE/ ACTIVATE/ DEACTIVATE'80''01''1B''A4'Level 5/Level 6'06''83''01''YZ''95''01''XX'
09EFREAD/UPDATE DEACTIVATE/ ACTIVATE INCREASE'80' '80''01' '01''03' '18''A4' 'A4'PIN Appl 1 global Level 5/Level 6'06' '06''83' '83''01' '01''01' 'YZ''95' '95''01' '01''08' 'XX'
10EFREAD/UPDATE DEACTIVATE/ ACTIVATE INCREASE'84' '80' '80''01' '01' '01''32' '03' '18''A4' 'A4' 'A4'PIN Appl 1 global PIN Appl 1 global Level 5/Level 6'06' '06' '06''83' '83' '83''01' '01' '01''01' '01' 'YZ''95' '95' '95''01' '01' '01''08' '08' 'XX'
11EFREAD UPDATE DEACTIVATE/ ACTIVATE'84' '80' '80' '80''01' '01' '01' '01''32' '01' '02' '18''A4' '90' 'A4' 'A4'PIN2 Appl 1 global ALW Universal PIN Level 5/Level 6'06' '00' '06' '06''83' '83' '83''01' '01' '01''81' '11' 'YZ''95' '95' '95''01' '01' '01''08' '08' 'XX'
12EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''A4' 'A4'Universal PIN Level 5/Level 6'06' '06''83' '83''01' '01''11' 'YZ''95' '95''01' '01''08' 'XX'
13EFREAD/UPDATE DEACTIVATE/ ACTIVATE'80' '80''01' '01''03' '18''A4' 'A4'Universal PIN Level 5/Level 6'06' '06''83' '83''01' '01''11' 'YZ''95' '95''01' '01''08' 'XX'
14EFREAD UPDATE DEACTIVATE/ ACTIVATE'80' '80' '80''01' '01' '01''01' '02' '18''A4' 'A4' 'A4'Universal PIN PIN2 Appl 1 local Level 5/Level 6'00' '06' '06''83' '83' '83''01' '01' '01''11' '81' 'YZ''95' '95' '95''01' '01' '01''08' '08' 'XX'
15EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''90' 'A4'ALW Level 5/Level 6'00' '06''83''01''YZ''95''01''XX'
16EFREAD/UPDATE/ ACTIVATE DEACTIVATE'80' '80''01' '01''13' '08''A4' 'A4'Universal PIN Level 5/Level 6'06' '06''83' '83''01' '01''11' 'YZ''95' '95''01' '01''08' 'XX'
17EFREAD/UPDATE/ ACTIVATE/ DEACTIVATE'80''01''1B''A4'Level 5/Level 6'06''83''01''YZ''95''01''XX'
18EFREAD/UPDATE DEACTIVATE/ ACTIVATE'80' '80''01' '01''03' '18''A4' 'A4'Universal PIN Level 5/Level 6'06' '06''83' '83''01' '01''11' 'YZ''95' '95''01' '01''08' 'XX'
INCREASE READ/UPDATE DEACTIVATE/'84' '80''01' '01''32''A4' 'A4'Universal PIN Universal PIN'06' '06''83' '83''01' '01''11' '11''95' '95''01' '01''08' '08'
19EFACTIVATE INCREASE'80' '84''01' '01''03' '18' '32''A4' 'A4'Level 5/Level 6 PIN2 Appl 1 global'06' '06''83' '83''01' '01''YZ' '81''95' '95''01' '01''XX' '08'
Table G.2: DF Telecom Access Rule References
ARR RecordApplic ableAccess ConditionAM DOLVSCDO CRTSecurityLSCDO CRT TagVSCDO CRT TagValue
TagConditionLKey Ref TagLVValue Usage Qualifier TagLL Key Ref TagLVUsage Qualifier TagLV
01EFREAD'80''01''01''90'ALW'00'--------- ---
02EFREAD UPDATE DEACTIVATE/ ACTIVATE'80' '80' '80''01' '01' '01''01' '02' '18''90' 'A0' 'A4'ALW PIN Appl 1 global OR PIN Appl 2 Level 5'00' '10' '06''A4''06''83' '83''01' '01''01' '0Z''95' '95''01' '01''08' 'XX''A4''06' '83''01' '02''95''01''08'
03EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''A0' 'A4'PIN Appl 1 global OR PIN Appl 2 Level 5'10' '06''A4''83' '83''01' '01''01' '0Z''95' '95''01' '01''08' 'XX''A4''06''83''01' '02''95''01''08'
04EFREAD/UPDATE DEACTIVATE/ ACTIVATE'80' '80''01' '01''03' '18''A0' 'A4'PIN Appl 1 global OR PIN Appl 2 Level 5'10' '06''A4''83' '83''01' '01''01' '0Z''95' '95''01' '01''08' 'XX''A4''06''83' '01''02''95''01''08'
05EFREAD UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01' '01''01' '1A'''90' 'A4'ALW Level 5'00' '06''83''01''0Z''95''01''XX'
06EFREAD/ UPDATE/ ACTIVATE DEACTIVATE'80' '01''01''13''A0'PIN Appl 1 global OR PIN Appl 2'10''A4''83''01''01''95''01''08''A4''06' '83''01' '02''95''01''08'
07EFREAD/UPDATE/ DEACTIVATE/ ACTIVATE'80' '80''01''08' '1B''A4' 'A4'Level 5 Level 5'06' '06''83' '83''01' '01''0Z' '0Z''95' '95''01' '01''XX' 'XX'

G.2 Example of access rule referencing with SE ID

This clause describes an example of the usage of the access rule referencing method using SE ID. Table G.1 is considered to be the EF(ARR) file for this example.

Assume an application uses PIN Application 1 Global as its application PIN. In addition, this application allows the replacement of its application PIN by the Universal PIN. EF(example) is an elementary file part of this application and has the following access conditions:

The security attributes returned after the selection of EF(example) then contains a reference to record 2 of table G.1 for SE 01 and a reference to record 11 of table G.1 for SE 00.

Annex H (normative): List of SFI Values

This annex lists SFI values assigned in the present document.

H.1 List of SFI Values at the MF Level

File IdentifierSFIDescription
'2FE2''02'ICC Identification (EF ICCId )
'2F05''05'Preferred Languages (EF PL )
'2F06''06'Access Rules Reference (EF ARR )
'2F00''1E'Application Directory (EF DIR )

All other SFI values are reserved for future use.

Annex I (informative): Resets and modes of operation

This annex contains figures that illustrate selection and switching of modes of operation of the "Type 1 UICC" and "Type 2 UICC".

Figure I.1: Modes of operation of a "Type 1 UICC"
Figure I.2: Modes of operation of a "Type 2 UICC"

Annex J (informative): Example of the use of PINs

J.1 Application having several ADFs

From the security context point of view, 2 ADFs using the same application PIN are part of the same application. Each ADF then refers to the same local key reference number whose value and status is specific to each ADF. Figure J.1 illustrates it.

Figure J.1

J.2 Two applications with two different security contexts

From the security context point of view, two applications use two different application PINs. Then the local PINs of the applications use two different key reference numbers, each one paired with its associated application PIN. Figure J.2 illustrates this scenario.

Figure J.2

Annex K (informative): Bibliography

Annex L (informative): Change history

The table below indicates changes that have been incorporated into the present document since it was created by EP SCP.

Change history
DateMeetingEP SCP Doc.CRRvCatSubject/CommentOldNew
2000-08SCP-029-00-0289--First draft created. Technical content is identical to 3GPP TS 31.101 V3.2.00.0.0
2000-08SCP-029-00-0342001FCorrection and clarification of the provision of Contact C60.0.03.0.0
9-00-0343002FClarifications of Electrical characteristics
9-00-0307003FClarification of the SELECT command with "special" file-IDs
9-00-0293004FClarification of GET RESPONSE command usage
9-00-0346005FATR: Correction of Data Coding Byte
9-00-0348006F Correction of the file descriptor information and PS Template DO
9-00-0352007FCorrection to S-Block dependent errors and T=1 ATR example
9-00-0359008FSELECT command response
9-00-0364009FClarifications and corrections to usage of SFI and reservation of file IDs
9-00-0366010FClarification of access rules and ADF
9-00-0367011FClarification of the location of EF(ARR).
9-00-0368012FClarifications to the SEARCH RECORD command
9-00-0369013FClarifications and corrections to clause 6
9-00-0373014FClarification to the INCREASE command
9-00-0374015FClarifications and corrections transmission protocols in clause 7
9-00-0375016FClarification to VERIFY PIN
9-00-0383017FApplication selection using partial DF name
9-00-0385018FCorrection of P1 of ACTIVATE and DEACTIVATE commands
9-00-0387019FDefinition of SFIs
9-00-0391 9-00-0393020 021FCollection of corrections and clarifications.
9-00-0394F Support of TERMINAL PROFILE by an UICC
022FCorrections to References and clarifications to definitions
9-00-0396023FCorrection of PIN related procedure
9-00-0397024FClarifications and corrections to the security architecture in clause 9
2000-12SCP-039-00-0398 9-00-0463025 026F FAlignment of table for commands and status words Clarification to the requirement for the warm reset3.0.04.0.0
9-00-0454027FCorrections and clarifications on multi-verification capable UICC Changing UICC current consumption values for 3V and 1.8V for
9-00-0456028B
release 4
9-00-0459029FCorrection to SFI values Clarification of EFARR access conditions
9-00-0467 9-00-0451030 0311F FCorrection of T=1 ATR example
9-00-0452032FModification on using 'UICC characteristics byte' in FCP - TAG '80'
9-00-0453033FModification on using Proprietary information in FCP - TAG '81'
terminal
9-00-0465034FSupport for minimum clock frequency indication to the
2001-02SCP-049-00-0466 SCP-010041035 037F ACorrection of implicit MF selection Reservation of File ID '7F31' for iDEN Specifications4.0.04.1.0
SCP-010040039AClarification of selection by path
SCP-010054043ACorrection of the minimum pulse width during clock frequency switching
SCP-010056045AClarification of the access rules referencing
SCP-010060047AClarification on block dependent errors
SCP-010062 049A
SCP-010063050AIndication of amount of available memory Clarification of selection by path (empty data fields)
2001-04SCP-05SCP-010121051BAddition of GET CHALLENGE command4.1.04.2.0
SCP-0101360521CApplicability of commands to applications
SCP-010133054ACorrection to total file size for DFs
SCP-010139055BAddition of logical channels
SCP-010145056BModification of security environment for
2001-07SCP-06SCP-010177058Alogical channels Correction of EF(ARR) example in annex F4.2.04.3.0
2001-10SCP-07SCP-010210 060 SCP-010293064A FClarification and correction regarding the Universal PIN Clarification on Local PIN status4.3.04.4.0
SCP-010295066ALocation of local PIN
SCP-010296 067FCorrection regarding Logical Channels
SCP-010301069ACorrection of definition of application and second level application
SCP-010303071AAddition of an example on Access Rule referencing
DateMeetingEP SCP Doc.CRRvCatSubject/CommentOldNew
2002-01SCP-08SCP-010290062AClarification and correction regarding the Universal PIN and Global PINs4.4.04.5.0
SCP-010372073FCorrection to status words for the MANAGE CHANNEL command
SCP-010383075AInconsistency in the VERIFY PIN and UNBLOCK PIN commands definition
SCP-010385076AUse of GET RESPONSE with case 2 and case 4 commands
2002-03SCP-09SCP-020041078FCorrection of Errors in SELECT FILE by File Referencing Example4.5.05.0.0
SCP-020043080FCorrect SELECT command parameter definitions
SCP-020042079CUICC presence detection procedure and usage modification
2002-06SCP-10SCP-0201840871FCorrection to status words for the commands STATUS, ACTIVATE FILE, DEACTIVATE FILE, GET CHALLENGE and MANAGE CHANNEL5.0.05.1.0
SCP-020158084FCorrection to Update Record
090FCorrection of Procedure Byte '6Cxx' for case 2 commands with Le = '00'
093FSFI for EF(ICCID) and EF(ARR)
081FAdditions to Abbreviations section
2002-09SCP-11SCP-020210096AStatus word 6700 for Select command5.1.05.2.0
SCP-0202501001ACorrections and clarifications to PIN handling
SCP-020210103FClarification of default SE and default Usage Qualifier
SCP-020253106AClarification of VERIFY PIN and UNBLOCK PIN
2003-01SCP-12SCP-030050109FIntroduction of the reference to the CAT specification5.2.05.3.0
SCP-030050115FClarification of Proprietary Information field in FCP
SCP-030061119DRemove UICC as an abbreviation to align with 3GPP TR 21.905
1
SCP-030059112FCorrections and clarifications
2003-05SCP-13SCP-0301581271FClarification of application session termination5.3.05.4.0
SCP-030111130FDelete special FID "3FFF"
SCP-030111123FClarification on use of "7FFF" for ADF selection
2003-09SCP-14SCP-030219139FCorrection of Security attributes length coding table5.4.05.5.0
2003-12SCP-15SCP-030486147ATurnaround time requirement for T=05.5.05.6.0
2004-11SCP-19SCP-040414167ACorrections to References and replacement of FCI with FCP5.6.05.7.0
SCP-040414172ACorrection of description of response data structure for T=1
SCP-040414176ADelete status word '61XX' for T=1

History

Document history
V5.0.0May 2002Publication
V5.1.0July 2002Publication
V5.2.0October 2002Publication
V5.3.0February 2003Publication
V5.4.0June 2003Publication
V5.5.0September 2003Publication
V5.6.0January 2004Publication
V5.7.0December 2004Publication

Intellectual Property Rights

IPRs essential 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 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 (http://webapp.etsi.org/IPR/home.asp).

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.

© European Telecommunications Standards Institute. Converted automatically from the published PDF; layout, figures and tables may differ from the original. The authoritative version is the original: https://www.etsi.org/deliver/etsi_ts/102200_102299/102221/05.07.00_60/ts_102221v050700p.pdf.