92 ETSI TS 102 221 V17.1.

0 (2022-02)

For example, if the amount of available memory is 100 bytes, it means that the terminal can store a TLV object with a
2 byte tag, 1 byte length and 97 bytes of data.

11.1.1.4.6.5 File details

Indicator of the TLV coding supported by a BER TLV structured EF.

Byte(s) Description Value Length

1 Tag '84' 1
2 Length 1 1
3 File details value 1

• Coding of file access details value:

b8 b7 B6 b5 b4 b3 b2 b1 Meaning
- - - - - - - 1 DER coding only is supported
X X X X X X X - RFU

Additional bytes may be added to the value field in the future.

11.1.1.4.6.6 Reserved File size

Memory size which is reserved for this file and cannot be allocated by any other entity.

Byte(s) Description Value Length

1 Tag '85' 1
2 Length X, X 2 1
3 to 2+X Number of data bytes X

The most significant byte comes first in the value field.

The value shall include administrative overhead (if any) that is required to store TLV objects, but not the structural
information for the file itself. Thus the actually usable file size calculated according to clause 11.1.1.4.1 may be smaller.

If no memory is reserved for the file, the value of the "Reserved File size" object is set to zero.

11.1.1.4.6.7 Maximum file size

File size that shall not be exceeded.

Byte(s) Description Value Length

1 Tag '86' 1
2 Length X, X 2 1
3 to 2+X Number of data bytes X

The most significant byte comes first in the value field.

The value shall include administrative overhead (if any) that is required to store TLV objects, but not the structural
information for the file itself. Thus the actually usable file size calculated according to clause 11.1.1.4.1 may be smaller.

If no maximum file size is defined for the file, the maximum file size object is not present for a file, and all available
memory of the UICC may be allocated to that file.

11.1.1.4.6.8 Supported system commands

Byte(s) Description Value Length
1 Tag '87' 1
2 Length 1 1
3 Supported commands 1

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

• Coding of Supported commands field:

b8 b7 B6 b5 b4 b3 b2 b1 Meaning
- - - - - - - 1 TERMINAL CAPABILITY is supported
- - - - - - - 0 TERMINAL CAPABILITY not supported
X X X X X X X - RFU

Additional bytes may be added to the value field in the future.

The UICC shall set the indication "TERMINAL CAPABILITY is supported" to request the terminal to indicate its
capabilities with respect to support of additional power consumption using the TERMINAL CAPABILITY command.

11.1.1.4.6.9 Specific UICC environmental conditions

This TLV object indicates to the terminal the specific environmental conditions that the UICC supports. This TLV
object is mandatory if the UICC supports specific UICC environmental conditions. It is up to the terminal whether to
evaluate this object and how to behave.

Byte(s) Description Value Length

1 Tag '88' 1
2 Length '01' 1
3 Specific UICC environmental conditions byte (see 1
table 11.7a)

Table 11.7a: Specific UICC environmental conditions byte

b8 b7 b6 b5 b4 b3 b2 b1 Meaning
- - - - - X X X Temperature Class
0 0 0 Standard temperature range
- - - - - 0 0 1 Temperature class A
- - - - - 0 1 0 Temperature class B
- - - - 0 1 1 Temperature class C
1 X X RFU
- - - - X - - - High humidity
- - - - 0 - - - High humidity not supported
- - - - 1 - - - High humidity supported
X X X X - - - - RFU

11.1.1.4.6.10 Platform to Platform CAT Secured APDU

This TLV indicates to the terminal that the usage of a Platform to Platform CAT APDU secure channel is requested.

Byte(s) Description Value Length

1 Tag '89' 1
2 Length '01' 1
3 Platform to Platform CAT Secured APDU '01' 1

11.1.1.4.7 Security attributes

11.1.1.4.7.1 Compact format

Byte(s) Description Value Length
1 Tag '8C' 1
2 Length X 1
3 AM byte 1
4 to (X+2) SC bytes X-1

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

The value of the AM byte is defined in ISO/IEC 7816-4 [12]. 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-4 [12].

11.1.1.4.7.2 Expanded format

Byte(s) Description Value Length Comment
1 Tag 'AB' 1
2 Length V 1
3 AM DO tag '8X' (see note 1) 1
4 Length X 1
5 to (4+X) AM_DO (see note 2) X
Security Rule
5+X SC_DO tag (see note 2) 1
#1
6+X Length Y 1
(7+X) to SC_DO (see note 2) Y
(6+X+Y)
………………………………………………
………………………………………………
………………………………………………
V+2- AM DO tag '8X' (see note 1) 1
(4+W+Z)
V+2- Length W 1
(3+W+Z)
V+2- AM_DO (see note 2) W
Security Rule
(2+W+Z) to
#N
V+2-(2+Z)
V+2-(1+Z) SC_DO tag (see note 2) 1
V+2-Z Length Z 1
V+2-(Z-1) to SC_DO (see note 2) Z
V+2
NOTE 1: The value of 'X' is dependent on the usage of the AM_DO see ISO/IEC 7816-4 [12].
NOTE 2: The value of the AM_DO and the SC_DO is defined in ISO/IEC 7816-4 [12].

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) Description Value Length

1 Tag '8B' 1
2 Length 3 1
3 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 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.

ETSI