Content for ETSI TS 102 221 PDF version: 17.1.0

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…

10.2 Response APDU 10.2.0 Structure 10.2.1 Status conditions returned by the UICC 10.2.1.0 Introduction 10.2.1.1 Normal processing 10.2.1.2 Postponed processing 10.2.1.3 Warnings 10.2.1.4 Execution errors 10.2.1.5 Checking errors 10.2.1.6 Application errors 10.2.2 Status words of the commands 10.3 Logical channels
...

The response APDU consists of an optional data field and a mandatory status part divided into two bytes; SW1 and SW2. The number of bytes received in the response APDU is denoted Lr (length of the response data field). The structure of the response APDU is shown in Table 10.6.

Table 10.6: Contents of Response APDU

Code	Length	Description
Data	Lr	Response data string
SW1	1	Status Byte 1
SW2	1	Status Byte 2

Coding of SW1 and SW2 is presented in clause 10.2.1.

10.2.1 Status conditions returned by the UICC p. 80

10.2.1.0 Introduction p. 80

Status of the card after processing of the command is coded in the status bytes SW1 and SW2. Clauses 10.2.1.1 to 10.2.1.6 specify the coding of the status bytes.

10.2.1.1 Normal processing p. 80

Table 10.7: Status byte coding - normal processing

SW1	SW2	Description
'90'	'00'	Normal ending of the command
'91'	'XX'	Normal ending of the command, with extra information from the proactive UICC containing a command for the terminal. Length 'XX' of the response data
'92'	'XX'	Normal ending of the command, with extra information concerning an ongoing data transfer session

10.2.1.2 Postponed processing p. 80

Table 10.8: Status byte coding - postponed processing

SW1	SW2	Error description
'93'	'00'	SIM Application Toolkit is busy. Command cannot be executed at present, further normal commands are allowed

10.2.1.3 Warnings p. 80

Table 10.9: Status byte coding - warnings

SW1	SW2	Description
'62'	'00'	No information given, state of non-volatile memory unchanged
'62'	'81'	Part of returned data may be corrupted
'62'	'82'	End of file/record reached before reading Le bytes or unsuccessful search
'62'	'83'	Selected file invalidated
'62'	'85'	Selected file in termination state
'62'	'F1'	More data available
'62'	'F2'	More data available and proactive command pending
'62'	'F3'	Response data available
'63'	'F1'	More data expected
'63'	'F2'	More data expected and proactive command pending
'63'	'CX'	Command successful but after using an internal update retry routine 'X' times Verification failed, 'X' retries remaining (see note)
NOTE: For the VERIFY PIN command, SW1SW2 indicates that the command was successful but the PIN was not correct and there are 'X' retries left. For all other commands it indicates the number of internal retries performed by the card to complete the command.

10.2.1.4 Execution errors p. 80

Table 10.10: Status byte coding - execution errors

SW1	SW2	Description
'64'	'00'	No information given, state of non-volatile memory unchanged
'65'	'00'	No information given, state of non-volatile memory changed
'65'	'81'	Memory problem

10.2.1.5 Checking errors p. 81

10.2.1.5.0 Base checking errors p. 81

Table 10.11: Status byte coding - checking errors

SW1	SW2	Description
'67'	'00'	Wrong length
'67'	'XX'	The interpretation of this status word is command dependent, except for SW2 = '00'
'6B'	'00'	Wrong parameter(s) P1-P2
'6D'	'00'	Instruction code not supported or invalid
'6E'	'00'	Class not supported
'6F'	'00'	Technical problem, no precise diagnosis
'6F'	'XX'	The interpretation of this status word is command dependent, except for SW2 = '00'

10.2.1.5.1 Functions in CLA not supported p. 81

Table 10.12: Status byte coding - functions in CLA not supported

SW1	SW2	Description
'68'	'00'	No information given
'68'	'81'	Logical channel not supported
'68'	'82'	Secure messaging not supported

10.2.1.5.2 Command not allowed p. 81

Table 10.13: Status byte coding - command not allowed

SW1	SW2	Description
'69'	'00'	No information given
'69'	'81'	Command incompatible with file structure
'69'	'82'	Security status not satisfied
'69'	'83'	Authentication/PIN method blocked
'69'	'84'	Referenced data invalidated
'69'	'85'	Conditions of use not satisfied
'69'	'86'	Command not allowed (no EF selected)
'69'	'89'	Command not allowed - secure channel - security not satisfied

10.2.1.5.3 Wrong parameters p. 81

Table 10.14: Status byte coding - wrong parameters

SW1	SW2	Description
'6A'	'80'	Incorrect parameters in the data field
'6A'	'81'	Function not supported
'6A'	'82'	File not found
'6A'	'83'	Record not found
'6A'	'84'	Not enough memory space
'6A'	'86'	Incorrect parameters P1 to P2
'6A'	'87'	Lc inconsistent with P1 to P2
'6A'	'88'	Referenced data not found

10.2.1.6 Application errors p. 82

Table 10.15: Status byte coding - application errors

SW1	SW2	Description
'98'	'50'	INCREASE cannot be performed, max value reached
'98'	'62'	Authentication error, application specific
'98'	'63'	Security session or association expired
'98'	'64'	Minimum UICC suspension time is too long
NOTE: Applications may define their own error codes.

10.2.2 Status words of the commands p. 83

Table 10.16 shows for each command the possible status conditions returned (marked by an asterisk *).

Table 10.16: Commands and status words

Status words	S E L E C T	S T A T U S	U P D A T E B I N A R Y	U P D A T E R E C O R D	R E A D B I N A R Y	R E A D R E C O R D	S E A R C H R E C O R D	I N C R E A S E	V E R I F Y P I N	C H A N G E P I N	D I S A B L E P I N	E N A B L E P I N	U N B L O C K P I N	D E A C T I V A T E F I L E	A C T I V A T E F I L E	A U T H E N T I C A T E	G E T C H A L L E N G E	T E R M I N A L P R O F I L E	E N V E L O P E	F E T C H	T E R M I N A L R E S P O N S E	M A N A G E C H A N N E L	R E T R I E V E D A T A	S E T D A T A	T E R M I N A L C A P A B I L I T Y	M A N A G E S E C U R E C H A N N E L	T R A N S A C T D A T A	S U S P E N D U I C C	G E T I D E N T I T Y
90 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
91 XX	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*		*
93 00																			*
98 50								*
98 62																*											*
62 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*			*	*	*	*	*
62 81					*	*
62 82					*	*	*
62 83	*													*
62 85	*																					*
62 F1																*							*			*	*
62 F2																							*				*
62 F3																*										*
63 F1																*								*		*
63 F2																								*
63 CX			*	*				*	*	*	*	*	*															*
64 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
65 00			*	*				*	*	*	*	*	*	*	*	*		*	*	*	*	*		*		*		*	*
65 81			*	*				*	*	*	*	*	*			*								*		*		*	*
67 XX	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
68 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
68 81	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
68 82	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
69 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*		*	*	*	*
69 81			*	*	*	*	*	*															*	*
69 82			*	*	*	*	*	*						*	*	*			*				*	*				*	*
69 83									*	*	*	*	*
69 84			*	*	*	*	*	*	*	*	*	*	*			*							*	*
69 85	*		*	*	*	*	*	*						*	*	*						*	*	*		*	*	*	*
69 86			*	*	*	*	*	*						*	*								*	*
69 89	*		*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*				*
6A 80							*							*	*								*	*	*	*	*	*
6A 81	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*						*	*	*	*	*	*	*	*	*
6A 82	*		*	*	*	*	*	*						*	*								*	*
6A 83				*		*	*
6A 84																								*			*	*
6A 86	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
6A 87	*													*	*
6A 88									*	*	*	*	*			*							*						*
6B 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
6E 00	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
6F XX	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*	*
92 XX																											*
98 63																										*	*
98 64																												*

The responses '91 XX', and '93 00' can only be given by a UICC to a terminal supporting CAT (see ETSI TS 102 223 [4]).

The behaviour of the terminal when receiving the response APDU from the ENVELOPE command with status word '6FXX', '62XX' and '63XX' is defined in clause 7.4.2.2.

10.3 Logical channels p. 85

Commands referring to a certain logical channel carry the respective logical channel number in:

the two least significant bits of the CLA byte defined in Table 10.3. Logical channels are numbered from 0 to 3. The basic logical channel (number 0) is permanently available;
the four least significant bits of the CLA byte defined in Table 10.4a. Logical channels are numbered from 4 to 19 (extended logical channels).

The MANAGE CHANNEL command shall be used to open and close a logical channel. The channel number is assigned by the UICC.