Agenda Item: 		9.5 General issues

Source: 		NOKIA

Title:			Analysis of GSM 11.11 v7.1.0 chapters 8 & 9 for 3G

To:		TSG-T3

Introduction: The aim of this input paper is to analyse GSM 11.11 v7.1.0 chapters 8 and 9 to identify the changes required for 3GPP for a 3G USIM application.

The chapters are analysed on a high-level; i.e. comments are given to the relevant chapters. If a chapter is not referenced no changes are foreseen.

8 Description of the functions

General comment: in the ETSI WP GENERICS group work on general enhancement to commands are ongoing, this work is mainly on enhancing search commands and on defining administrative commands – this input paper should be regarded as an extension to this work and thus the new/enhanced commands emerging from the GENERICS groups work will not be addressed here.

8.16 RUN GSM ALGORITHM
In 3G it is likely that at least two authentication/ciphering key methods will be present, the “old” GSM A8/3 method and a new 3G method.

In 7816-4 the command with the instruction (INS) ‘88’ (the RUN GSM ALGORITHM command in GSM) is called “internal authenticate” and the parameter P1 is used to indicate the type of authentication to be used.

Since we will have more that one authentication method it is proposed that parameter P1 is used to indicate the type of authentication to be used.

In GSM 11.11 P1 is fixed to ‘00’, according to 7816-4, this means that the algorithm is known in advance, i.e. it is understood that there is only one algorithm available in the card.

8.17 SLEEP
As the SLEEP command is a phase 1 only command it should not appear in the specification since it is not the intention to support phase 1 terminals.

New commands
One new command is foreseen 

MANAGE CHANNEL command
As it is foreseen that logical channels will be introduced in the 3G there will be a need to introduce the MANAGE CHANNEL command as defined in 7816-4.

This command is used for opening and closing new logical channels between the ME and the UICC.

9 Description of the commands

9.1 Mapping principles
In 3G it is the intention to use both T=0 and T=1 as transport protocol between the terminal and the UICC, thus there will this be a need to redraw the different case scenarios listed in this chapter – or there must at least be a set of command response pairs similar to the ones already drawn for the T=0 case.

9.2 Coding of commands
In 3G there will be commands in addition to the ones listed in Table 9 – these will include the administrative commands as specified by the GENERICS group.

General comment: As it is the intention to use T=1 in addition to T=0 it may be necessary to change the general format of all commands from the T=0 based command style to the generic 7816-4 format – see the figure below:
Old command style
COMMAND	CLASS	INS	P1	P2	P3	
Command XX	'A0'	'XX'	'P1'	'P2'		
New command style
Header	Body	
COMMAND	CLASS	INS	P1	P2	[Lc] [Data field] [Le]	
Command XX	'YY'	'XX'	'P1'	'P2'		

Figure 1: Old and new command style.

Lc:		Length of the data field in the command.
Data field:	Data to be transmitted from the terminal to the UICC.
Le:		Length of the expected data in the response from the UICC.

In figure 1 it can also be seen that the CLASS byte has changed since it can not be fixed to ‘A0’, e.g. due to the introduction of the logical channels.

9.2.1 SELECT
Due to changes in e.g. the access conditions and new commands it may be possible that there will be changes to the response parameters returned by the UICC when the SELECT command has been send by the terminal.

9.2.2 STATUS
The same comment as to the SELECT command applies to the STATUS command.

9.2.16 RUN GSM ALGORITHM
See the comments to the same command under chapter 8.

9.2.17 SLEEP
See the comments to the same command under chapter 8.

9.2.18 GET RESPONSE
It should be noted that this command only applies when T=0 has been selected, i.e. it is not allowed to use the GET RESPONSE command when T=1 has been selected as the transport protocol.

9.3 Definitions and coding
Table 10 lists the access conditions that applies in GSM – in 3G it may be necessary to define some new conditions, this could especially be the case when OTA mechanisms are defined.

9.4.1 Response commands which are correctly executed
Some differences between 7816-4 and GSM 11.11 in the coding of the SW1 and SW2 words exist – this could/should be aligned?
One example is the more data to read response;
•	In GSM 11.11 SW1 is coded as ‘9F’
•	In 7816-4 SW1 is coded as ‘61’.

9.4.5 Security management
The note to the table should be removed since it refers to phase 1 SIM’s.