Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 31.101  Word version:  16.1.0

Top   Top   Up   Prev   Next
0…   4…   8…   A…

 

8  Application and file structureWord‑p. 14

8.0  General

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

8.1  Contents of the EFs at the MF level

See clause 13.

8.1A  UICC application structure

The provisions of ETSI TS 102 221 [1] clause 8.1 apply.

8.2  File types

The provisions of ETSI TS 102 221 [1] clause 8.2 apply.

8.3  File referencing

The provisions of ETSI TS 102 221 [1] clause 8.3 apply.

8.4  Methods for selecting a file

The provisions of ETSI TS 102 221 [1] clause 8.4 apply.

8.5  Application characteristics

The provisions of ETSI TS 102 221 [1] clause 8.5 apply.

8.6  Reservation of file IDsWord‑p. 15

The provisions of ETSI TS 102 221 [1] clause 8.6 apply.

8.7  Logical channels

The provisions of ETSI TS 102 221 [1] clause 8.7 apply.

8.8  Shareable versus not-shareable files

The provisions of ETSI TS 102 221 [1] clause 8.8 apply.

8.9  Secure channels

The provisions of ETSI TS 102 221 [1] clause 8.9 apply.

9  Security features

The provisions of ETSI TS 102 221 [1] clause 9 apply.

9.1  Supported security features

The provisions of ETSI TS 102 221 [1] clause 9.1 apply.

9.2  Security architecture

The provisions of ETSI TS 102 221 [1] clause 9.2 apply.

9.3  Security environment

The provisions of ETSI TS 102 221 [1] clause 9.3 apply.

9.4  PIN definitions

The provisions of ETSI TS 102 221 [1] clause 9.4 apply.

9.5  PIN and key reference relation ship

The provisions of ETSI TS 102 221 [1] clause 9.5 apply.

9.6  User verification and file access conditions

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 ETSI TS 102 221 [1] clause 9.5.1. 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 ETSI TS 102 221 [1] clause 9.5.2. 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 ETSI TS 102 221 [1] clause 9.5.2.
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 ETSI TS 102 221 [1] clause 9 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 ETSI TS 102 221 [1] clause 9.4.1. 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 ETSI TS 102 221 [1] clause 9.2.7.
  • 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.
The security architecture as defined in ETSI TS 102 221 [1] clause 9 applies to terminals supporting 3GPP applications with the following definitions and requirements:
  • A terminal shall support the use of level 1 and level 2 user verification requirements as defined in ETSI TS 102 221 [1] clause 9.1.
  • A terminal shall support the multi-application capabilities as defined in ETSI TS 102 221 [1] clause 9.1.
  • A terminal shall support the replacement of a 3GPP application PIN with the Universal PIN, key reference '11', as defined in ETSI TS 102 221 [1] clause 9.4.1.
  • A terminal shall support the security attributes defined using tag's '8C', 'AB' and '8B' as defined in ETSI TS 102 221 [1] clause 9.2.4. In addition both the referencing methods indicated by tag '8B' shall be supported as defined in ETSI TS 102 221 [1] clause 9.2.7.
The access rule is referenced in the FCP using tag '8B'. The TLV object contains the file ID (the file ID of EFARR) and record number, or file ID (the file ID of EFARR), SEID and record number, pointer to the record in EFARR where the access rule is stored. Each SEID refers to a record number in EFARR. EFs having the same access rule use the same record reference in EFARR. For an example EFARR, see ETSI TS 102 221 [1] clause 13.4.
Up

10  Structure of commands and responsesWord‑p. 16

The provisions of ETSI TS 102 221 [1] clause 10 apply.

10.1  Command APDU structure

The provisions of ETSI TS 102 221 [1] clause 10.1 apply.

10.1.1  Coding of Class Byte

The provisions of ETSI TS 102 221 [1] clause 10.1.1 apply.

10.1.2  Coding of Instruction Byte

The provisions of ETSI TS 102 221 [1] clause 10.1.2 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 bytesWord‑p. 17

The provisions of ETSI TS 102 221 [1] clause 10.1.3 apply.

10.1.4  Coding of Lc byte

The provisions of ETSI TS 102 221 [1] clause 10.1.4 apply.

10.1.5  Coding of data part

The provisions of ETSI TS 102 221 [1] clause 10.1.5 apply.

10.1.6  Coding of Le byte

The provisions of ETSI TS 102 221 [1] clause 10.1.6 apply.

10.2  Response APDU structure

The provisions of ETSI TS 102 221 [1] clause 10.2 apply.

10.2.1  Status conditions returned by the UICC

The provisions of ETSI TS 102 221 [1] clause 10.2.1 apply.

10.2.1.1  Normal processing

The provisions of ETSI TS 102 221 [1] clause 10.2.1.1 apply.

10.2.1.2  Postponed processing

The provisions of ETSI TS 102 221 [1] clause 10.2.1.2 apply.

10.2.1.3  Warnings

The provisions of ETSI TS 102 221 [1] clause 10.2.1.3 apply.

10.2.1.4  Execution errors

The provisions of ETSI TS 102 221 [1] clause 10.2.1.4 apply.

10.2.1.5  Checking errors

The provisions of ETSI TS 102 221 [1] clause 10.2.1.5 apply.
10.2.1.5.1  Functions in CLA not supported
The provisions of ETSI TS 102 221 [1] clause 10.2.1.5.1 apply.
10.2.1.5.2  Command not allowed
The provisions of ETSI TS 102 221 [1] clause 10.2.1.5.2 apply.
10.2.1.5.3  Wrong parameters
The provisions of ETSI TS 102 221 [1] clause 10.2.1.5.3 apply.

10.2.1.6  Application errorsWord‑p. 18

The provisions of ETSI TS 102 221 [1] clause 10.2.1.6 apply.

10.2.2  Status words of the commands

The provisions of ETSI TS 102 221 [1] clause 10.2.2 apply with the following exceptions which are not required by 3GPP:
  • column 'GET CHALLENGE' of table 10.16

10.3  Logical channelsWord‑p. 19

The provisions of ETSI TS 102 221 [1] clause 10.3 apply.

11  Commands

11.1  Generic commands

The provisions of ETSI TS 102 221 [1] clause 11.1 apply.

11.1.1  SELECT

11.1.1.1  Functional description

The provisions of ETSI TS 102 221 [1] clause 11.1.1.1 apply.

11.1.1.2  Command parameters and data

The provisions of ETSI TS 102 221 [1] clause 11.1.1.2 apply.

11.1.1.3  Response Data

The provisions of ETSI TS 102 221 [1] clause 11.1.1.3 apply.

11.1.1.4  File control parameters

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 ETSI TS 102 221 [1] clause 11.1.1.4. Where options are indicated in ETSI TS 102 221 [1] clause 11.1.1.4, this clause specifies the values to be used in the FCP related to 3GPP applications.
11.1.1.4.1  File size
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.1 apply.
11.1.1.4.2  Total file size
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.2 apply.
11.1.1.4.3  File Descriptor
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.3 apply.
11.1.1.4.4  File identifier
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.4 apply.
11.1.1.4.5  DF name
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.5 apply.
11.1.1.4.6  Proprietary information
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.6 apply, with the exception of provisions relative to 'Platform to Platform CAT Secured APDU' and clause 11.1.1.4.6.10.
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 ETSI TS 102 221 [1] clause 11.1.1.4.6. 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 ETSI TS 102 221 [1] clause 11.1.1.4.6.3. 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.
Up
11.1.1.4.7  Security attributesWord‑p. 20
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.7 apply.
11.1.1.4.8  Short file identifier
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.8 apply.
11.1.1.4.9  Life cycle status integer
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.9 apply.
11.1.1.4.10  PIN status template DO
The provisions of ETSI TS 102 221 [1] clause 11.1.1.4.10 apply.

11.1.2  STATUS

The provisions of ETSI TS 102 221 [1] clause 11.1.2 apply.

11.1.3  READ BINARY

The provisions of ETSI TS 102 221 [1] clause 11.1.3 apply.

11.1.4  UPDATE BINARY

The provisions of ETSI TS 102 221 [1] clause 11.1.4 apply.

11.1.5  READ RECORD

The provisions of ETSI TS 102 221 [1] clause 11.1.5 apply.

11.1.6  UPDATE RECORD

The provisions of ETSI TS 102 221 [1] clause 11.1.6 apply.

11.1.7  SEARCH RECORD

The provisions of ETSI TS 102 221 [1] clause 11.1.7 apply.

11.1.8  INCREASE

The provisions of ETSI TS 102 221 [1] clause 11.1.8 apply.

11.1.9  VERIFY PIN

The provisions of ETSI TS 102 221 [1] clause 11.1.9 apply.

11.1.10  CHANGE PINWord‑p. 21

The provisions of ETSI TS 102 221 [1] clause 11.1.10 apply.

11.1.11  DISABLE PIN

The provisions of ETSI TS 102 221 [1] clause 11.1.11 apply.

11.1.12  ENABLE PIN

The provisions of ETSI TS 102 221 [1] clause 11.1.12 apply.

11.1.13  UNBLOCK PIN

The provisions of ETSI TS 102 221 [1] clause 11.1.13 apply.

11.1.14  DEACTIVATE FILE

The provisions of ETSI TS 102 221 [1] clause 11.1.14 apply.

11.1.15  ACTIVATE FILE

The provisions of ETSI TS 102 221 [1] clause 11.1.15 apply.

11.1.16  AUTHENTICATE

The provisions of ETSI TS 102 221 [1] clause 11.1.16 apply.

11.1.17  MANAGE CHANNEL

The provisions of ETSI TS 102 221 [1] clause 11.1.17 apply.

11.1.18  GET CHALLENGE

The provisions of ETSI TS 102 221 [1] clause 11.1.18 are not required by 3GPP.

11.1.19  TERMINAL CAPABILITY

The provisions of ETSI TS 102 221 [1] clause 11.1.19 apply.

11.1.20  MANAGE SECURE CHANNEL

The provisions of ETSI TS 102 221 [1] clause 11.1.20 apply.

11.1.21  TRANSACT DATA

The provisions of ETSI TS 102 221 [1] clause 11.1.21 apply.

11.1.22  SUSPEND UICC

The provisions of ETSI TS 102 221 [1] clause 11.1.22 apply.

11.2  CAT commands

The provisions of ETSI TS 102 221 [1] clause 11.2 apply.

11.3  Data Oriented commandsWord‑p. 22

The provisions of ETSI TS 102 221 [1] clause 11.3 apply.

12  Transmission oriented commands

The provisions of ETSI TS 102 221 [1] clause 12 apply.

13  Application independent files

There are five EFs at the Master File (MF) level specified in ETSI TS 102 221 [1] clause 13 (EFICCID; EFDIR, EFPL, EFARR and EFUMPC), which are all mandatory for 3GPP.
The DFCD at the Master File (MF) level specified in ETSI TS 102 221 [1] clause 13.5 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.
Up

14  Application independent protocol

14.1  Application independent protocol

The provisions of ETSI TS 102 221 [1] clause 14 apply with the following exceptions:
  • clause 14.6.2 of ETSI TS 102 221 [1] is replaced by clause 14.2.

14.2  CAT commands

During idle mode the terminal shall send STATUS commands to the UICC at intervals no longer than:
  • when the extended DRX cycle bit in the EFAD is set to 1: the maximum between the interval negotiated with the UICC (see TS 31.111) and the extended idle mode DRX cycle received from the network (see TS 24.008)
  • in all other cases: the interval negotiated with the UICC (see TS 31.111)
    During a call the UICC presence detection applies. The default value for the proactive polling is the same as for the presence detection procedure.
Up

15  Support of APDU-based UICC applications over USB

The provisions of ETSI TS 102 221 [1] clause 15 apply taking into account clauses 6A.3, 7A.4, 8, 9, 10, 11, 13 and 14 in the present document.

Up   Top   ToC