Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  ETSI TS 102 221   PDF version:  17.1.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   7…   7.3…   8…   9…   10…   10.2…   11…   11.1.2…   11.1.9…   11.1.14…   11.1.19…   11.1.20…   11.1.21…   11.2…   11.3…   12…   13…   14…   15   A   B   C…   D   E…   F…   G…   H…   I   J…   K…   L…   M…

 

11.1.21  TRANSACT DATAp. 127

11.1.21.1  General functional descriptionp. 127

This command transports large amounts of data on APDU based communication with different data formats.
This command is either a case 2 or case 3 command depending on P1 b3 as described below. It becomes a case 1 command when P1 b2 is set (session abort).
P1 defines the data transfer session number and is also used for requesting retransmission and for session abort. The session number allows up to four transfer sessions to be interleaved.
The P2 parameter contains the number of remaining data blocks going from terminal to the UICC in this transaction.
If the UICC successfully receives an encrypted block that is not the last block then the UICC may respond with SW1 SW2 set to '92 XX' indicating normal ending of the command. The UICC may indicate that it wants to return data related to this or another data transfer session with status words SW1 SW2 indicating the session number with 'More data blocks pending'.
If the UICC successfully receives the last block then SW1 SW2 shall indicate 'Data transaction ongoing'.
If the UICC has been requested to send a block to the terminal, b3 in P1 is set to '0', and this is not the last block to be retrieved to the terminal, then SW1 SW2 shall indicate 'More data blocks pending'.
Both the terminal and the UICC can abort the data transfer session.
A data transfer session is ongoing until it is aborted by the UICC or terminal or completed in normal circumstances. Upon session abort by the terminal, the Connection SA remains open and all data related to the current transaction are lost.
If the UICC indicates a proactive command the terminal can send a command like STATUS that allows SW1 SW2 to be '91 XX' in a different session. The interrupted transaction is resumed afterwards.
Up

11.1.21.2  Command parameters and datap. 128

If in P1 b3=0:
Code Value
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1 See Table 11.30
P2 See Table 11.31
LcNot Present
Data As specified in Table 11.32
LeLength of response data
If in P1 b3=1:
Code Value
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1 See Table 11.30
P2 See Table 11.31
LcLength of data
Data As specified in Table 11.32
LeNot present
Command data:
  • Secure channel number coding (P1):
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
XX------Session number
--000---RFU
-----X--Command Data control
1:
Command contains data
0:
No command data
------X-Abort session
0 -
Continue session
1 -
Abort session
-------XRetransmit latest response
0 -
next data block
1 -
Retransmit latest response
NOTE:
When b3=1 b1 has no meaning and shall be set to 0.
  • Block Management coding (P2):
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
XXXXXXXXRemaining data blocks from terminal to UICC
If P2 is different from 0 then the APDU shall contain data. Once P2 has reached zero the terminal shall not start sending more data in the same session as long as the UICC is producing response data.
Data coding:
  • The data transmitted is encapsulated in a BER-TLV data object structure and is formatted as follows:
Byte(s) Description Length
1 to TBER-TLV Tag1 ≤ T ≤ 3
T+1 to T+LBER-TLV Length1 ≤ L ≤ 2
T+L+1 to T+L+XBER-TLV ValueX
The length of the TLV objects shall be coded one or two bytes:
Number of bytes First byte Following bytes Encoded length value
1'00' to '7F'none0 to 127
2'81''80' to 'FF'128 to 255
Defined tags:
'80':
Secure channel data tag.
All other values are RFU.
Therefore, for the transmission of secure channel data, the transmitted data shall be coded in the following way:
Byte(s) Description Length
1Secure channel data Tag1
2 or 2 to 3Length1 or 2
(3 to 3+X) or (4 to 4+X) TRANSACT DATA command data as specified in ETSI TS 102 484 [20]X
The same tag value shall be used within one transfer session. All data within subsequent TRANSACT DATA commands within the same session shall use the same tag as the first TRANSACT DATA command in the session.
Response status words:
  • The normal response to the TRANSACT DATA APDU is '92 XX': Data transaction ongoing. The encoding of SW2 can be seen in Table 11.33.
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
000-----RFU
---X----Retransmit control
0 -
Send next block
1 -
Re-send previous block
----X---Proactive message:
0 -
No proactive message
1 -
Proactive message pending
-----XX-Session number - The session number from P1 the pending data block is a response to
-------XData available control
0 -
No more pending data blocks. Transaction complete
1 -
More data blocks pending. Terminal shall send another 'TRANSACT DATA' APDU to retrieve that data
The session is aborted by the UICC if status words '6A 84' - Not enough memory space is returned.
Response data:
  • The UICC may indicate that it wants to respond with data to each command APDU as long as this is part of the same session. This means that not all data to the UICC has to be sent before the UICC can start responding with data.
Response data shall be encoded within TLV objects with the same tag and format as the one used in the data in the TRANSACT DATA APDU command.
Up

11.1.22  SUSPEND UICCp. 130

11.1.22.1  Functional descriptionp. 130

This function is used to store the internal status of the UICC so that the power supply to the UICC can be switched off, and to subsequently restore the UICC status. The mechanism therefore allows restoring to a new card session certain states saved at suspension of a previous card session.
The terminal does not issue the command if the UICC suspension mechanism is not indicated as supported by the UICC in the UICC Maximum Power Consumption file (EFUMPC).
The terminal shall not use this mechanism if it supports an interface in addition to the interface defined in the present document (e.g. the UICC-CLF interface as defined in ETSI TS 102 613 [19]).
The following P1 values are defined:
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
-------0Suspend the UICC
-------1Resume the UICC
XXXXXXX-RFU (shall be set to 0)
Up

11.1.22.2  UICC suspensionp. 131

11.1.22.2.1  Introductionp. 131
Clause 11.1.22.2 defines the SUSPEND UICC function and coding when P1 = 'Suspend the UICC'.
11.1.22.2.2  Functional descriptionp. 131
When the UICC receives the command to suspend, it stores the complete UICC status to a non-volatile memory. The UICC status includes all data that is required to resume the UICC in the exact same condition, so that it is equivalent as if the power supply was not removed. This includes, but is not limited to:
  • the status of selected applications on each logical channel;
  • the security context related to PIN verification status for each application;
  • for each logical channel, the selected EF with:
    • for a transparent EF: offset,
    • for a linear fixed EF and cyclic EF: record pointer, for a BER TLV structure EF: the current operation (if any), current tag pointer (including the current offset in the data object), the offset and length of data which was transferred in the previous block;
  • the status of toolkit applications.
The UICC shall reject the command with status word '6985' during an active proactive UICC session, or if there is any open BIP channel, or if a secure channel (including those defined in the present document or in ETSI TS 102 225 [21] and ETSI TS 102 226 [29]) is in use. The UICC may use the status word '6985' to reject the command due to internal reasons.
The UICC shall reject the command with status word '9864' if the minimum duration requested by the terminal is too large to be accepted.
The UICC generates a random Resume token of 8 bytes and stores it with the complete status in its non-volatile memory. The UICC also indicates the maximum time duration for which it can be suspended, using a value between the minimum and the maximum proposed by the terminal.
Upon reception of the response indicating successful execution of the SUSPEND UICC command, the terminal shall deactivate the contacts of the UICC, following the sequence specified in clause 4.5.2.
Input:
  • Minimum duration of the suspension proposed by the terminal
  • Maximum duration of the suspension proposed by the terminal
Output:
  • Maximum duration of the suspension negotiated by the UICC, in the range proposed by the terminal
  • Resume token
Up
11.1.22.2.3  Command parameters and datap. 132
Code Value
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2'00'
LcLength of the subsequent data field = '04'
DataMinimum and maximum duration of the suspension proposed by terminal
LeLength of the response data = '0A'
Command data:
Byte(s) Description Length
1 to 2Minimum duration of the suspension proposed by the terminal.2
3 to 4Maximum duration of the suspension proposed by the terminal.2
Response data:
Byte(s) Description Length
1 to 2Maximum duration of the suspension negotiated by the UICC2
3 to 10Resume token8
Where all durations in the command and in the response are encoded as:
Byte(s) Description Length
1Time unit:
  • 0: seconds
  • 1: minutes
  • 2: hours
  • 3: days
  • 4: 10 days
1
1Length of time, expressed in units.1
Up

11.1.22.3  UICC resumep. 132

11.1.22.3.1  Introductionp. 132
Clause 11.1.22.3 defines the SUSPEND UICC function and coding when P1 = 'Resume the UICC'.
11.1.22.3.2  Functional descriptionp. 132
This function is used to restore the status of the UICC that was previously stored to non-volatile memory of the UICC using the SUSPEND UICC command with P1 = 'Suspend the UICC'. The UICC shall delete the stored UICC status after execution of the command, irrespective of the result.
Only the following commands can be issued by the terminal before resuming the UICC, with the status resulting from the use of these commands being lost after a successful resume:
  • SELECT with P1 ≠ '04'
  • READ BINARY
  • READ RECORD
  • TERMINAL CAPABILITY
If the UICC receives any other command, it deletes the stored status and continues with its current status.
The UICC rejects the RESUME UICC command if it does not have a valid status to resume returning status word '6985'.
The UICC compares the Resume token passed by the terminal with the token stored in the non-volatile memory. The UICC responds with an error if the Resume token passed by the terminal does not match, returning status word '6982'. The UICC restores the previous status and return '9000' if the Resume token passed by the terminal is validated.
If the terminal sent a TERMINAL CAPABILITY command before suspending the UICC, it shall send the TERMINAL CAPABILITY command with same content before resuming the UICC.
Input:
  • Resume token
Output:
  • None
Up
11.1.22.3.3  Command parameters and datap. 133
Code Value
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'01'
P2'00'
LcLength of the subsequent data field = '08'
DataResume token
LeNot present
Command data:
Byte(s) Description Length
1 to 8Resume token8
Up

11.1.23  GET IDENTITYp. 133

11.1.23.1  Functional descriptionp. 133

An appropriate application shall be selected in the UICC before issuing this command. The function initiates the computation of identity data by the UICC.
Input:
  • Identity command data.
Output:
  • Identity response data.

11.1.23.2  Command parameters and datap. 133

Code Value
CLAAs specified in clause 10.1.1
INSAs specified in clause 10.1.2
P1'00'
P2 See Table 11.34b
LcLength of the subsequent data field
DataCommand related data
LeLength of the response data
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
00000000No information given
0-------Global reference data
1-------Specific reference data
Command data (generic):
Byte(s) Description Length
1 to LcIdentity related data (see note)Lc
NOTE:
The command data shall be specified by each application specific document.
Response data (generic):
Byte(s) Description Length
1 to LeIdentity related data (see note)Le
NOTE:
The response data shall be specified by each application specific document.
Up

11.1.24  EXCHANGE CAPABILITIESp. 134

See ETSI TS 103 666-1 [34].
This clause does not apply to platforms which are not an SSP as described in ETSI TS 103 666-1 [34].

Up   Top   ToC