TSG-Terminals Working Group 3 (USIM) #5	TdocT3-99145
Mariehamn 31st May – 2nd June, 1999	

Source:	NTT DoCoMo 

Title:	Proposed USIM compatibility for 2nd generation mobile equipment
_________________________________________________________________________

1.	Introduction
The issue of USIM compatibility for 2nd generation mobile equipment is described in TSG-T3#4 Tokyo meeting report following.

It was proposed that it should be the responsibility of the UICC to ensure that the links should be destroyed if a GSM ME updates a USIM phone book entry. It was agreed that compatibility issues should be discussed at the next T3 / SMG9 meeting.	

This document describes UICC function for solving the above issue.

2.	Proposal
Phone book for USIM is composed several EF (e.g. EFADN, EFADN1, EFEXT1, EFEXT1-2, EFPBI, EFIAP, EFIAP1, etc.). 2nd generation equipment can use EFADN and EFEXT1. But 2nd generation equipment can’t use several new EFs (e.g. EFADN1, EFEXT1-2, EFPBI, EFIAP, EFIAP1, etc.).
Therefore, If USIM applied to 2nd generation equipment, then it has two problems that are as follows.
-	If an entry of phone book deletes by 2nd generation equipment, then it remains a record of each EF (except EFADN and EFEXT1) in relation to the record of EFADN.
-	If an entry of phone book deletes and cleats a new entry to same record by 2nd generation equipment, then it can’t cleats a record each EF except EFADN and EFEXT1. In order to an entry of phone book are inconsistent.

We proposed function of UICC with phone book for USIM compatibility with 2nd generation mobile equipment.

UICC must have following function.
-	If record of EFADN deleted by mobile equipment (e.g. 2nd generation terminal user), then UICC initialises record of each EF (e.g. EFIAP, EFPBC, etc.) in relation to the record of EFADN. Deleted mean is all octets of record set to “FF”. Initialises mean is all octets of record set to defied value.  But if record of EFEXT1 deleted or modified then UICC nothing to do.