TSG-Terminals Working Group 3 (USIM) #7	TdocT3-99200
Lund 5th – 7th July, 1999	

Source:	NTT DoCoMo 

Title:	Proposed UID (Unique Identifier) structure 
_________________________________________________________________________

1.	Introduction
In the last T3 meeting in Miami, the liaison from TSG-T2 (Tdoc T399168) described as follows. 

The proposed UID length (2 bytes) might be too short to use for expected usage, and recommends that it should be larger than 2 bytes. Therefore, we proposed UID structure for that recommendation. 	

UID is one of the phone book components, so it should be included phone book entry. However, three different phone book structures are proposed. We propose general structure of UID contents in this document. 

2.	Proposal
Each entry of phone book needs a UID, and it should be include to EFUID. Basically the UID values are never reused and the initial value of UID is ‘1’. If phone book entry has more than 255 records then two or more EFUID exist.
Last used UID stored EFLUID. This means current maximum (last assigned) value of UID. When user create a new record, ME can decide the value of new UID without checking out all existing values of UID in the phone book entries.

3.	Contents
EFUID (Unique identifier for phone book entry)

This EF contains UIDs of phone book entries for synchronization between USIM and ME (or PC). 
This value is increased by 1, each time new entry is created. Each record of EFUID should be associated to each entry of phone book.

Identifier: 'xxxx'	Structure: liner fixed	Optional	
File size: X byte	Update activity: low	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1
	INVALIDATE	CHV2
	REHABILITATE	CHV2
	
Bytes	Description	M/O	Length	
1-X	UID	M	X byte	

-	UID
 Contents:
   Unique identifier for each entry of phone book.
 Coding:
   binary. Bit = 8 of first octet is MSB of UID. Bit = 1 of last octet is LSB of UID.
   All bits = 1 means not used UID. All bits = 0 is express to owner information. 
   First used UID value is ‘1’. 

First octet of UID
		b8	b7	b6	b5	b4	b3	b2	b1	
										
		MSB
2(8X-1)	
2(8X-2)	
2(8X-3)	
2(8X-4)	
2(8X-5)	
2(8X-6)	
2(8X-7)	
2(8X-8)	

       Last octet of UID
		b8	b7	b6	b5	b4	b3	b2	b1	

27	
26	
25	
24	
23	
22	
21	LSB
20	
       For instance, ‘00’ ‘01’ ‘30’ represents 28+25+24 = 304

EFLUID(Last used UID)

This EF contains last used UID. This value means current maximum (latest assigned) value of UID. When user create a new entry, ME assigns a new UID, the value is last used UID increased by 1. And ME stores this new value to EFLUID.

The provision of this EF is associated with EFUID. Both files shall be present together, or both absent from the USIM.

Identifier: 'xxxx'	Structure: liner fixed	Optional	
File size: X byte	Update activity: low	
Access Conditions:
	READ	CHV1
	UPDATE	CHV1
	INVALIDATE	CHV2
	REHABILITATE	CHV2
	
Bytes	Description	M/O	Length	
1-X	Last used UID	M	X byte	

-	Last used UID
 Contents:
   Last used UID.
 Coding:
   see the coding of EFUID.

  The value of length (X) must be equal to length (X) of EFUID.