TSG-Terminals Working Group 3 (USIM) adhoc	TSGT3z99011
Copenhagen 26th - 27th May, 1999	Page 1

Source:	NTT DoCoMo 

Title:	Proposal for Phone Book Structure
________________________________________________________________

1.	Introduction
This document describes link method of phone book that is referred to T-doc T3-99134.
Proposal of T3-99134 is related to pointing to record number of each EF by EFIAP. But it is very complication and difficult for one entry of phone book structure.
We proposed simple structure of phone book.
 
2.	Proposal
We proposed one entry of phone book stored to same record number of each EF for simple structure. Phone book structure for this proposal is as follows.
-	The phone book structure is presented in the EFPBI. 
-	Second record of EFPBI shows structure for phone book extension. (e.g. more than 255 entry)  
-	A record of EFADN is master record of each entry.
-	Each EF contains the same amount of records as EFADN.
-	One entry of phone book stored to same record number of each EF.

As a result, It is not need backward pointers. And that is simple structure of phone book.  

3.	Figure of Phone Book Structure

Fig. 1 Example of EFPBI Structure
Record1	EFADN Identifier	
	EFPBC Identifier	
	EFANR Identifier	
	EFSNE Identifier	
Record2	EFADN2 Identifier	
	EFPBC2 Identifier	

Fig. 2 Example of each EF Relationship
No	EFADN		EFPBC		EFANR		EFSNE		
1	Record 1	->	Record 1	->	Record 1	->	Record 1	First entry of Phone Book stored record number 1 of EFADN, EFPBC, EFANR and EFSNE.	
2	Record 2	->	Record 2	->	Record 2	->	Record 2	same thing	
3	...		...		...		...		
...	...		...		...		...		
254	Record254		Record254		Record254		Record254	Max. 254 records.	

No	EFADN2		EFPBC2		
255	Record 1	->	Record 1	255th entry of Phone Book stored record number 1 of EFADN2 and EFPBC2.	
256	Record 2	->	Record 2		
...	...		...		
...	...		...		
508	Record254		Record254	Max. 254 records.