Activation of a USIM session excludes the activation of a GSM session. In particular, this implies that once a USIM application session has been activated, commands sent to the UICC with CLAss byte set to 'A0' shall return SW1SW2 '6E 00' (class not supported) to the terminal. Similarly, activation of a GSM session excludes the activation of a USIM session. At most one USIM session can be active at the same time.

The UICC/terminal interface shall support the interface specified in ETSI TS 102 221 [1]. In addition, the UICC/terminal interface may support the Inter-Chip USB interface defined in ETSI TS 102 600 [7]. 3GPP ICC based applications (e.g. USIM, USIM Application Toolkit, ISIM, SIM) are supported over both interfaces (see Figure 1).

The UICC/terminal interface shall comply with all requirements stated in ETSI TS 102 221 [1]. Where options are indicated in ETSI TS 102 221 [1], the present document specifies which options are to be used for a ETSI TS 102 221 [1] UICC/terminal interface where the UICC supports a 3GPP application.

If the Inter-Chip USB UICC/terminal interface is supported, it shall comply with ETSI TS 102 600 [7]. Where options are indicated in ETSI TS 102 600 [7], the present document specifies which options are to be used for an Inter-Chip USB UICC/terminal interface where the UICC supports a 3GPP application. The protocol stack for APDU-level exchanges that are described in ETSI TS 102 600 [7] allow the transmission of APDUs. USB UICCs and USB UICC-enabled terminals shall comply with the functionality of the ETSI TS 102 221 [1] interface. Where options are indicated in ETSI TS 102 221 [1], the present document specifies which options are to be used for APDU-based applications where the UICC supports a 3GPP application. The mapping of APDU into TPDU (see ETSI TS 102 221 [1] clause 7.3.1.1) and transmission oriented commands (see ETSI TS 102 221 [1] clause 12) do not apply in the USB context as the APDU commands and responses are transmitted over USB as encoded at the application layer (i.e. C-APDU and R-APDU are directly encapsulated). In the context of UICC applications running over USB, the card activation and deactivation process, the cold and warm reset procedures and the request for additional processing time as described in ETSI TS 102 221 [1] shall be performed by USB commands as described in ETSI TS 102 600 [7]. Any reference to the above procedures shall be interpreted in a USB context according to ETSI TS 102 600 [7]. When an ATR is received then the corresponding provisions and error handling procedures of ETSI TS 102 221 [1] apply.

See clause 6A.3.2.

See clause 6A.2.

See clause 11.1.1.4.

See clause 6A.3.

Class A operating conditions as specified in ETSI TS 102 221 [1] clause 5.1 is not required by 3GPP then MEs, except GSM ME, shall not support class A on the ME - UICC interface.

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

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

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

The provisions of ETSI TS 102 221 [1] clause 6.2 apply. In addition, a UICC holding a 3GPP application shall support at least two consecutive voltage classes as defined in ETSI TS 102 221 [1] clause 6.2.1, e.g. AB or BC. If the UICC supports more than two classes, they shall all be consecutive, e.g. ABC

The provisions of ETSI TS 102 221 [1] clause 6.3 apply. In addition, no extra guard time, indicated in TC1 in the ATR, needs to be supported when sending characters from the terminal to the card. The terminal may reject a UICC indicating values other than 0 or 255 in TC1.

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

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

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

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

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

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

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

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

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

The provisions of ETSI TS 102 221 [1] clause 7.4 apply. In addition, when involved in administrative management operations, a 3GPP application interfaces with appropriate equipment. These operations are outside the scope of the present document. When involved in network operations a 3GPP application interfaces with a terminal with which messages are exchanged. A message can be a command or a response.

• A 3GPP Application command/response pair is a sequence consisting of a command and the associated response.
• A 3GPP Application procedure consists of one or more 3GPP Application command/response pairs which are used to perform all or part of an application oriented task. A procedure shall be considered as a whole, that is to say that the corresponding task is achieved if and only if the procedure is completed. The terminal shall ensure that, when operated according to the manufacturer's manual, any unspecified interruption of the sequence of command/response pairs which realise the procedure, leads to the abortion of the procedure itself.
• A 3GPP application session is the interval of time starting at the completion of the 3GPP application initialisation procedure and ending either with the start of the 3GPP session termination procedure, or at the first instant the link between the UICC and the terminal is interrupted.

During the 3GPP network operation phase, the terminal plays the role of the master and the 3GPP application plays the role of the slave. A 3GPP application specification may specify some commands defined in ETSI TS 102 221 [1] as optional or define additional commands. The 3GPP application shall execute all applicable commands in such a way as not to jeopardise, or cause suspension, of service provisioning to the user. This could occur if, for example, execution of the AUTHENTICATE is delayed in such a way which would result in the network denying or suspending service to the user.