135 ETSI TS 102 221 V17.1.

0 (2022-02)

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:

• The structure of the data is defined in ETSI TS 102 223 [4].

Output:

• The structure of the data is defined in ETSI TS 102 223 [4].

11.2.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 '00'
Lc Length of the subsequent data field
Data Structure and coding defined in ETSI TS 102 223 [4]
Le Empty or maximum length of response data

Response data:

• Structure of the response data is defined in ETSI TS 102 223 [4] for CAT applications.

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:

• None.

Output:

• Data string containing a proactive command for the terminal (e.g. a CAT command).

11.2.3.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 '00'
Lc Not present
Data Not present
Le Length of expected data

Response data:

• Structure of the response data is defined in ETSI TS 102 223 [4] for CAT applications.

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

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:

• Data string containing the response.

Output:

• None.

11.2.4.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 '00'
Lc Length of the subsequent data field
Data Structure and coding defined in ETSI TS 102 223 [4]
Le Not present

11.3 Data Oriented commands

11.3.0 Overview and generic mechanism
This clause lists a group of data oriented 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.

The data transmitted is encapsulated in a BER-TLV data object structure and is formatted as follows:

Byte(s) Description Length

1 to T BER-TLV Tag 1 T 3
T+1 to T+L BER-TLV Length 1 L 4
T+L+1 to T+L+X BER-TLV Value X

The specific tag allocation scheme is beyond the scope of the present document.

However, the tag values, that shall be supported by the UICC and the terminal are defined as follows:

Tags of the context-specific class, coded on one to three bytes, shall be used for the TLV objects, i.e. tags shall be taken
out of the following ranges:

• '80' to '9E' and '9F 1F' to '9F 7F' and '9F 81 XX' to '9F FF XX' with 'XX' from '00' to 7F' for primitive objects;
and

• 'A0' to 'BE' and 'BF 1F' to 'BF 7F' and 'BF 81 XX' to 'BF FF XX' with 'XX' from '00' to 7F' for constructed
objects.

Terminals shall take into account that each tag value can only exist once in a file and thus an unused tag has to be used
to create a new object.

ETSI