TSG-T3 USIM Adhoc						Tdoc T3z99020
14-16 th of September 1999
Turku, Finland

This paper still needs to be discussed.

1	Historical bytes:
The coding of historical bytes is described in clause 8 of ISO/IEC 7816-4.
According to this standard, the number of historical bytes is at most 15 bytes. If present, the historical bytes are made up of 3 fields:
-	a mandatory indicator (1 byte),
-	optional COMPACT-TLV data objects,
-	a conditional status indicator (3 bytes).
1.1	Category indicator:
In clause 8 of ISO/IEC 7816-4, this is the first historical byte and its value has a meaning.
-	‘00’ means that status information shall be present at the end of the historical bytes (not in TLV).
-	‘10’ means that the following byte is the DIR data reference.
-	‘80’ means that status information, if present, is contained in an optional COMPACT-TLV data object.
-	‘81’ to ‘8F’ are reserved for future use.
-	Other values are proprietary.
Remark:
We can define, for USIM applications, a category indicator proprietary. ‘99’ for example.

1.2	Optional COMPACT-TLV data objects:
The COMPACT-TLV data objects define in the clause 8 of ISO/IEC 7816-4 are:
1.2.1	Country/Issuer indicator (Optional)
When present, this data object denotes a country or an issuer. This data object is introduced by ‘1Y’ or ‘2Y’ (Y is equal to the number of following data).
1.2.2	Card service data (Mandatory)
This data object denotes the methods available in the card for supporting the services described in clause 9 of ISO/IEC 7816-4. This data object is introduced by either ‘31’.
-	Direct application selection by full DF name.
-	Selection by partial DF name.
-	Data objects available in DIR file.
-	File I/O services by Read Record command.
When this data object is not present, the card supports only the implicit application selection.
1.2.3	Initial access data (Optional)
This data object allows the retrieval of a string of data objects defined in ISO/IEC 7816. . This data object is introduced by ‘41’, ‘42’ or ‘45’
Any command APDU described in the clause 8.3 is assumed to be the first command sent after the ATR.
According to the length of the data object, the command is:
-	A Read Binary (Length = ‘1’).
-	A Read Binary by Short EF identifier (Length = ‘2’).
-	A Read Record by Short EF identifier (Length = ‘2’).
-	A command to perform (Length = ‘5’).
1.2.4	Card issuer’s data (Optional)
The card issuer defines the structure and coding of this data object. This data object is introduced by ‘5Y’ (Y is equal to the number of following data).
1.2.5	Pre-issuing data (Optional)
Structure and coding are not defined. It may be used for indicating:
-	card manufacturer,
-	integrated circuit type,
-	integrated circuit manufacturer,
-	ROM mask version,
-	Operating system version.

This data object is introduced by ‘6Y’ (Y is equal to the number of following data).
Most of time 7 bytes are required.

1.2.6	Card capabilities (Mandatory ????)
This data object is introduced by ‘71’, ‘72’ or ‘73’.
According to the length of this data object, the card has the software functions:
-	DF selection:
-	by full DF name
-	by partial DF name
-	by path
-	by file identifier
-	implicit
-	EF management:
-	short EF identifier supported
-	record number supported
-	record identifier supported
-	Logical channel assignment
-	by the card
-	by the interface device
-	maximum number of logical channels