After activation of the UICC the terminal requests the Preferred Language (EFPL
). The terminal shall execute the power negotiation procedure. If the terminal supports CAT, it shall perform the CAT initialization procedure. The terminal then performs an application selection procedure according to clause 14.3
If an application present on the UICC has the requirement to ensure that the UICC has not been removed during a card session the following procedure applies. The terminal sends, at frequent intervals, a STATUS command on the UICC-terminal interface. The STATUS command shall be issued within a period of inactivity on the UICC-terminal interface. The period of inactivity and the conditions under which the presence detection takes place is specified by the applications active during the card session. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If no response data is received to this STATUS command the terminal shall take the appropriate actions after the work waiting time (T = 0) or block waiting time (T = 1) has expired as specified by the applications active. If the DF indicated in an error free response to a STATUS command is not the same as that which was indicated in the previous response, or accessed by the previous command, then the terminal shall take appropriate actions as specified by the applications active during the card session. This procedure shall be used in addition to a mechanical or other device used to detect the removal of a UICC.
The terminal performs the read procedure with EFPL
The terminal performs the update procedure with EFPL
A UICC may offer the possibility to run several selectable applications in parallel. This is done with the logical channel mechanism. Only one selectable application can run at a given time in a given logical channel.
The terminal shall attempt to select and read the UICC Maximum Power Consumption file (EFUMPC
If the file is present, the UICC is aware of the maximum power consumption values for Release 12 and higher. Else it is only aware of the values for pre-Release 12.
If the UICC supports the TERMINAL CAPABILITY command (which is mandatory for Release 12 and higher), the terminal shall send a TERMINAL CAPABILITY command indicating the maximum available power supply of the terminal within the range that the UICC is aware of.
UICC suspension can be used by the terminal to suspend the UICC when access is not required for long periods of time, in order to reduce the overall power consumption. When the UICC is suspended, the terminal deactivates the contacts of the UICC, following the sequence specified in clause 4.5.2
The procedure can be used only when it is indicated as supported by the UICC in the UICC Maximum Power Consumption file (EFUMPC
The terminal shall maintain the logical status as before the suspension and it shall resume the UICC for any event for which it had previously registered: this includes events registered with SET UP EVENT LIST or TIMER MANAGEMENT proactive command, as specified in ETSI TS 102 223 
When the terminal needs to resume the UICC, it first performs the initial communication establishment procedures, as described in clause 6
. The terminal can optionally check if the content of the EFICCID
matches the value used before the UICC was suspended. The terminal sends the SUSPEND UICC command with P1 = '01' and the Resume token received when the UICC was suspended earlier. The resume operation does not have impact on the parameters negotiated as part of the initial communication establishment procedures.