Content for TS 31.101 Word version: 18.1.0
8 Application and file structure
9 Security features
10 Structure of commands and responses
11 Commands
12 Transmission oriented commands
13 Application independent files
14 Application independent protocol
15 Support of APDU-based UICC applications over USB
8 Application and file structure |R6| p. 14
8.0 General |R7| p. 14
The provisions of clause 8.0 of ETSI TS 102 221 apply.
This clause specifies general requirements for EFs for 3GPP applications.
EFs contain data items. A data item is a part of an EF which represents a complete logical entity. The 3GPP application specification defines the access conditions, data items and coding for each file.
EFs or data items having an unassigned value, or which are cleared by the terminal, shall have their bytes set to 'FF'. After the administrative phase all data items shall have a defined value or have their bytes set to 'FF', unless specified otherwise in other 3GPP specifications. For example, for a deleted LAI in the EFLOCI file defined in TS 31.102, the last byte takes the value 'FE' (refer to TS 24.008). If a data item is modified by the allocation of a value specified in another 3GPP TS, then this value shall be used and the data item is not unassigned.
EFs are mandatory (M), optional (O), or conditional (C). A conditional file is mandatory if required by a supported feature, as defined by the 3GPP application (e.g. PBR in TS 31.102). The file size of an optional EF may be zero. All implemented EFs with a file size greater than zero shall contain all mandatory data items. Optional data items may either be filled with 'F', or, if located at the end of an EF, need not exist.
When the coding is according to ITU-T Recommendation T.50 [5], bit 8 of every byte shall be set to 0.
8.1 Contents of the EFs at the MF level p. 14
See clause 13.
8.1A UICC application structure |R7| p. 14
The provisions of clause 8.1 of ETSI TS 102 221 apply.
8.2 File types |R7| p. 14
The provisions of clause 8.2 of ETSI TS 102 221 apply.
8.3 File referencing |R7| p. 14
The provisions of clause 8.3 of ETSI TS 102 221 apply.
8.4 Methods for selecting a file |R7| p. 14
The provisions of clause 8.4 of ETSI TS 102 221 apply.
8.5 Application characteristics |R7| p. 15
The provisions of clause 8.5 of ETSI TS 102 221 apply.
8.6 Reservation of file IDs |R7| p. 15
The provisions of clause 8.6 of ETSI TS 102 221 apply.
8.7 Logical channels |R7| p. 15
The provisions of clause 8.7 of ETSI TS 102 221 apply.
8.8 Shareable versus not-shareable files |R7| p. 15
The provisions of clause 8.8 of ETSI TS 102 221 apply.
8.9 Secure channels |R7| p. 15
The provisions of clause 8.9 of ETSI TS 102 221 apply.
8.10 Logical secure elements |R18| p. 15
The provisions of clause 8.10 of ETSI TS 102 221 apply.
9 Security features |R7| p. 16
The provisions of clause 9 of ETSI TS 102 221 apply.
9.1 Supported security features p. 16
The provisions of clause 9.1 of ETSI TS 102 221 apply.
9.2 Security architecture p. 16
The provisions of clause 9.2 of ETSI TS 102 221 apply.
9.3 Security environment p. 16
The provisions of clause 9.3 of ETSI TS 102 221 apply.
9.4 PIN definitions p. 16
The provisions of clause 9.4 of ETSI TS 102 221 apply.
9.5 PIN and key reference relation ship p. 16
The provisions of clause 9.5 of ETSI TS 102 221 apply.
9.6 User verification and file access conditions p. 16
A 3GPP application uses 2 PINs for user verification, PIN and PIN2. PIN2 is used only in the ADF. The PIN and PIN2 are mapped into key references as defined in clause 9.5.1 of ETSI TS 102 221. The Universal PIN shall be associated with a usage qualifier, and other key references may also be associated with a usage qualifier as defined in clause 9.5.2 of ETSI TS 102 221. The PIN status is indicated in the PS_DO, which is part of the FCP response when an ADF/DF is selected. The coding of the PS_DO is defined in clause 9.5.2 of ETSI TS 102 221.
PIN and PIN2 are coded on 8 bytes. Only (decimal) digits (0-9) shall be used, coded in ITU-T T.50 [5] with bit 8 set to zero. The minimum number of digits is 4. If the number of digits presented by the user is less than 8 then the ME shall pad the presented PIN with 'FF' before sending it to the 3GPP application.
The coding of the UNBLOCK PINs is identical to the coding of the PINs. However, the number of (decimal) digits is always 8.
The security architecture as defined in clause 9 of ETSI TS 102 221 applies to 3GPP applications with the following definitions and additions:
- A 3GPP application may reside on either a single-verification capable UICC or a multi-verification capable UICC.
- A 3GPP application residing on a multi-verification capable UICC shall support the replacement of its application PIN with the Universal PIN, key reference '11', as defined in clause 9.4.1 of ETSI TS 102 221. Only the Universal PIN is allowed as a replacement.
- A multi-verification capable UICC holding a 3GPP application shall support the referenced format using SEID as defined in clause 9.2.7 of ETSI TS 102 221.
- Every file related to a 3GPP application shall have a reference to an access rule stored in EFARR.
- Disabling of PIN2 is allowed if supported by the 3GPP application, unless indicated otherwise.
- A terminal shall support the use of level 1 and level 2 user verification requirements as defined in clause 9.1 of ETSI TS 102 221.
- A terminal shall support the multi-application capabilities as defined in clause 9.1 of ETSI TS 102 221.
- A terminal shall support the replacement of a 3GPP application PIN with the Universal PIN, key reference '11', as defined in clause 9.4.1 of ETSI TS 102 221.
- A terminal shall support the security attributes defined using tag's '8C', 'AB' and '8B' as defined in clause 9.2.4 of ETSI TS 102 221. In addition both the referencing methods indicated by tag '8B' shall be supported as defined in clause 9.2.7 of ETSI TS 102 221.
10 Structure of commands and responses |R7| p. 17
The provisions of clause 10 of ETSI TS 102 221 apply.
10.1 Command APDU structure p. 17
The provisions of clause 10.1 of ETSI TS 102 221 apply.
10.1.1 Coding of Class Byte p. 17
The provisions of clause 10.1.1 of ETSI TS 102 221 apply.
10.1.2 Coding of Instruction Byte p. 17
The provisions of clause 10.1.2 of ETSI TS 102 221 apply except for the coding of the Instruction byte of the following commands which are not required by 3GPP:
- GET CHALLENGE
10.1.3 Coding of parameter bytes p. 18
The provisions of clause 10.1.3 of ETSI TS 102 221 apply.
10.1.4 Coding of Lc byte p. 18
The provisions of clause 10.1.4 of ETSI TS 102 221 apply.
10.1.5 Coding of data part p. 18
The provisions of clause 10.1.5 of ETSI TS 102 221 apply.
10.1.6 Coding of Le byte p. 18
The provisions of clause 10.1.6 of ETSI TS 102 221 apply.
10.2 Response APDU structure p. 18
The provisions of clause 10.2 of ETSI TS 102 221 apply.
10.2.1 Status conditions returned by the UICC p. 18
The provisions of clause 10.2.1 of ETSI TS 102 221 apply.
10.2.1.1 Normal processing p. 18
The provisions of clause 10.2.1.1 of ETSI TS 102 221 apply.
10.2.1.2 Postponed processing p. 18
The provisions of clause 10.2.1.2 of ETSI TS 102 221 apply.
10.2.1.3 Warnings p. 18
The provisions of clause 10.2.1.3 of ETSI TS 102 221 apply.
10.2.1.4 Execution errors p. 18
The provisions of clause 10.2.1.4 of ETSI TS 102 221 apply.
10.2.1.5 Checking errors p. 18
The provisions of clause 10.2.1.5 of ETSI TS 102 221 apply.
10.2.1.5.1 Functions in CLA not supported p. 18
The provisions of clause 10.2.1.5.1 of ETSI TS 102 221 apply.
10.2.1.5.2 Command not allowed p. 18
The provisions of clause 10.2.1.5.2 of ETSI TS 102 221 apply.
10.2.1.5.3 Wrong parameters p. 18
The provisions of clause 10.2.1.5.3 of ETSI TS 102 221 apply.
10.2.1.6 Application errors p. 19
The provisions of clause 10.2.1.6 of ETSI TS 102 221 apply.
10.2.2 Status words of the commands p. 19
The provisions of clause 10.2.2 of ETSI TS 102 221 apply with the following exceptions which are not required by 3GPP:
- column 'GET CHALLENGE' of Table 10.16
10.3 Logical channels p. 19
The provisions of clause 10.3 of ETSI TS 102 221 apply.
11 Commands |R7| p. 19
11.0 Introduction |R18| p. 19
The provisions of clause 11.0 of ETSI TS 102 221 apply.
11.1 Generic commands p. 20
The provisions of clause 11.1 of ETSI TS 102 221 apply.
11.1.1 SELECT p. 20
11.1.1.1 Functional description p. 20
The provisions of clause 11.1.1.1 of ETSI TS 102 221 apply.
11.1.1.2 Command parameters and data p. 20
The provisions of clause 11.1.1.2 of ETSI TS 102 221 apply.
11.1.1.3 Response Data p. 20
The provisions of clause 11.1.1.3 of ETSI TS 102 221 apply.
11.1.1.4 File control parameters p. 20
This clause defines the contents of the data objects which are part of the FCP information where there is a difference compared to the values as specified in clause 11.1.1.4 of ETSI TS 102 221. Where options are indicated in clause 11.1.1.4 of ETSI TS 102 221, this clause specifies the values to be used in the FCP related to 3GPP applications.
11.1.1.4.1 File size p. 20
The provisions of clause 11.1.1.4.1 of ETSI TS 102 221 apply.
11.1.1.4.2 Total file size p. 20
The provisions of clause 11.1.1.4.2 of ETSI TS 102 221 apply.
11.1.1.4.3 File Descriptor p. 20
The provisions of clause 11.1.1.4.3 of ETSI TS 102 221 apply.
11.1.1.4.4 File identifier p. 20
The provisions of clause 11.1.1.4.4 of ETSI TS 102 221 apply.
11.1.1.4.5 DF name p. 20
The provisions of clause 11.1.1.4.5 of ETSI TS 102 221 apply.
11.1.1.4.6 Proprietary information p. 20
The provisions of clause 11.1.1.4.6 of ETSI TS 102 221 apply, with the exception of provisions relative to 'Platform to Platform CAT Secured APDU' and clause 11.1.1.4.6.10 of ETSI TS 102 221.
The Minimum application clock frequency data object is indicated by tag '82' in the proprietary constructed data object in the FCP information, identified by tag 'A5', as defined in clause 11.1.1.4.6 of ETSI TS 102 221. This data object specifies the minimum clock frequency to be provided by the terminal during the 3GPP application session. The value indicated in this data object shall not exceed 3 MHz, corresponding to '1E'. The terminal shall use a clock frequency between the value specified by this data object and the maximum clock frequency for the UICC as defined in clause 11.1.1.4.6.3 of ETSI TS 102 221. If this data object is not present in the FCP response or the value is 'FF' then the terminal shall assume that the minimum clock frequency is 1 MHz.
11.1.1.4.7 Security attributes p. 20
The provisions of clause 11.1.1.4.7 of ETSI TS 102 221 apply.
11.1.1.4.8 Short file identifier p. 21
The provisions of clause 11.1.1.4.8 of ETSI TS 102 221 apply.
11.1.1.4.9 Life cycle status integer p. 21
The provisions of clause 11.1.1.4.9 of ETSI TS 102 221 apply.
11.1.1.4.10 PIN status template DO p. 21
The provisions of clause 11.1.1.4.10 of ETSI TS 102 221 apply.
11.1.2 STATUS p. 21
The provisions of clause 11.1.2 of ETSI TS 102 221 apply.
11.1.3 READ BINARY p. 21
The provisions of clause 11.1.3 of ETSI TS 102 221 apply.
11.1.4 UPDATE BINARY p. 21
The provisions of clause 11.1.4 of ETSI TS 102 221 apply.
11.1.5 READ RECORD p. 21
The provisions of clause 11.1.5 of ETSI TS 102 221 apply.
11.1.6 UPDATE RECORD p. 21
The provisions of clause 11.1.6 of ETSI TS 102 221 apply.
11.1.7 SEARCH RECORD p. 21
The provisions of clause 11.1.7 of ETSI TS 102 221 apply.
11.1.8 INCREASE p. 21
The provisions of clause 11.1.8 of ETSI TS 102 221 apply.
11.1.9 VERIFY PIN p. 21
The provisions of clause 11.1.9 of ETSI TS 102 221 apply.
11.1.10 CHANGE PIN p. 21
The provisions of clause 11.1.10 of ETSI TS 102 221 apply.
11.1.11 DISABLE PIN p. 21
The provisions of clause 11.1.11 of ETSI TS 102 221 apply.
11.1.12 ENABLE PIN p. 21
The provisions of clause 11.1.12 of ETSI TS 102 221 apply.
11.1.13 UNBLOCK PIN p. 22
The provisions of clause 11.1.13 of ETSI TS 102 221 apply.
11.1.14 DEACTIVATE FILE p. 22
The provisions of clause 11.1.14 of ETSI TS 102 221 apply.
11.1.15 ACTIVATE FILE p. 22
The provisions of clause 11.1.15 of ETSI TS 102 221 apply.
11.1.16 AUTHENTICATE p. 22
The provisions of clause 11.1.16 of ETSI TS 102 221 apply.
11.1.17 MANAGE CHANNEL p. 22
The provisions of clause 11.1.17 of ETSI TS 102 221 apply.
11.1.18 GET CHALLENGE p. 22
The provisions of clause 11.1.18 of ETSI TS 102 221 are not required by 3GPP.
11.1.19 TERMINAL CAPABILITY p. 22
The provisions of clause 11.1.19 of ETSI TS 102 221 apply.
11.1.20 MANAGE SECURE CHANNEL p. 22
The provisions of clause 11.1.20 of ETSI TS 102 221 apply.
11.1.21 TRANSACT DATA p. 22
The provisions of clause 11.1.21 of ETSI TS 102 221 apply.
11.1.22 SUSPEND UICC |R14| p. 22
The provisions of clause 11.1.22 of ETSI TS 102 221 apply.
11.1.23 GET IDENTITY |R18| p. 22
The provisions of clause 11.1.23 of ETSI TS 102 221 apply.
11.1.24 EXCHANGE CAPABILITIES |R18| p. 22
The provisions of clause 11.1.24 of ETSI TS 102 221 apply.
11.1.25 MANAGE LSI |R18| p. 22
The provisions of clause 11.1.25 of ETSI TS 102 221 apply.
11.2 CAT commands p. 23
The provisions of clause 11.2 of ETSI TS 102 221 apply.
11.3 Data Oriented commands p. 23
The provisions of clause 11.3 of ETSI TS 102 221 apply.
12 Transmission oriented commands |R7| p. 23
The provisions of clause 12 of ETSI TS 102 221 apply.
13 Application independent files |R7| p. 23
The provisions of clause 13.0 of ETSI TS 102 221 apply.
There are five EFs at the Master File (MF) level specified in clause 13 of ETSI TS 102 221 (EFICCID; EFDIR, EFPL, EFARR and EFUMPC), which are all mandatory for 3GPP.
The DFCD at the Master File (MF) level specified in clause 13.5 of ETSI TS 102 221 is optional for 3GPP.
The EFDIR file contains the Application Identifiers (AIDs) and the Application Labels of the 3GPP applications present on the card as mandatory elements. The AIDs of 3GPP applications are defined in Annex O. The 3GPP applications can only be selected by means of the AID selection. The EFDIR entry shall not contain a path object for application selection. It is recommended that the application label does not contain more than 32 bytes.
14 Application independent protocol |R7| p. 23
14.1 Application independent protocol |R13| p. 23
The provisions of clause 14 of ETSI TS 102 221 apply with the following exceptions:
- clause 14.6.2 of ETSI TS 102 221 is replaced by clause 14.2.
14.2 CAT commands |R13| p. 23
During idle mode the terminal shall send STATUS commands to the UICC at intervals no longer than:
During a call the UICC presence detection applies. The default value for the proactive polling is the same as for the presence detection procedure.
In case of a UICC supporting LSEs, the terminal shall perform the proactive polling on every LSI where CAT was successfully initialized with the interval negotiated on each specific LSI.
15 Support of APDU-based UICC applications over USB |R7| p. 24
The provisions of clause 15 of ETSI TS 102 221 apply taking into account clauses 6A.3, 7A.4, 8, 9, 10, 11, 13 and 14 in the present document.
