140 ETSI TS 102 221 V17.1.

0 (2022-02)

11.3.2.2 Command parameters and data

Code Value
CLA As specified in clause 10.1.1
INS As specified in clause 10.1.2
P1 '00'
P2 See table 11.35
Lc Length of the subsequent data field
Data BER-TLV data object, or tag field only in case of deletion
Le Not present

Command data:

• For P2 encoding first block: tag, length and nothing of the value field, or part or all of the value field of the
object to create or replace. Tag only of the object to delete.

• For P2 encoding next block: next part of the value field of the object being created or replaced.

• For P2 encoding retransmit previous block: replacing data set in the previous command.

Response data:

• None.

12 Transmission oriented commands

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.

ETSI
 141 ETSI TS 102 221 V17.1.0 (2022-02)

12.1.1.2 Command parameters

Table 12.1: Parameters for GET RESPONSE

Code Value
CLA As specified in clause 10.1.1
INS As specified in clause 10.1.2
P1 '00'
P2 '00'
Lc Not present
Data Not present
Le '00' or value of SW2 of the previous command

Response parameters and data:

• the response data is defined in each clause of the corresponding command.

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
EFDIR is a linear fixed file under the MF and is under the responsibility of the issuer.

Table 13.1: EFDIR at MF-level

Identifier: '2F00' Structure: Linear fixed Mandatory

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 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
application template Data Object (DO) as defined in ISO/IEC 7816-4 [12]. 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-4 [12].

ETSI
 142 ETSI TS 102 221 V17.1.0 (2022-02)

Table 13.2: Coding of an application template entry

Length Description Status

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. See ETSI TS 101 220 [3] M
1 Application label tag = '50' O
1 Application label length O
Note 1 Application label value O
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. It is recommended that the number of
bytes in the application label does not exceed 32.
NOTE 2: Other Dos from ISO/IEC 7816-4 [12] 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: EFICCID at MF-level

Identifier: '2FE2' Structure: transparent Mandatory

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 Recommendation ITU-T E.118 [5].

Purpose: card identification number.

Coding: BCD, left justified and padded with 'F'. The order of digits is coded as below:

Byte 1:
b8 B7 b6 b5 b4 b3 b2 b1
LSB of Digit 1
:
:
MSB of Digit 1
LSB of Digit 2
:
:
MSB of Digit 2

ETSI