TSG-T3 (USIM) meeting #5		Tdoc T3-99137
Mariehamn, 31 May - 2 June, 1999

DRAFT Report of the 
3GPP TSG-T WG3 (USIM) meeting #4
hosted by NTT DoCoMo in
Tokyo, 19 - 21 April, 1999
Chairman:	Dr Klaus Vedder (Giesecke and Devrient)
Secretary:	Michael Sanders (ETSI)

1	Opening of the Meeting
The fourth meeting of the 3GPP TSG-T WG3 on USIM issues (hereafter referred to as T3) was opened by the Chairman, Dr. Klaus Vedder. The delegates were welcomed to Tokyo by Mr. Wakabayashi on behalf of the host NTT DoCoMo.
2	Roll Call of Delegates
The meeting was attended by 35 delegates from 11 countries. A list of the delegates can be found in Annex A of this report.
3	Input Documents / Agenda 
T3-99100 contains the first draft of the agenda. Several new documents and a new agenda item "USIM files and procedures" were added and a revised version was made available in T3-99118. The approved version can be found in annex B in this report.
4	Approval of the report of T3 #3 
T3-99099 contains the draft meeting report from TSG-T3 #3, held in Helsinki on the 16 - 18 March, 1999. After several clarifications, the report was approved. The secretary and chairman were mandated to editorially review the report and so the final version of the report is contained in T3-99119.
5	Results from other related meetings 
It was noted that there had been some discussion within TSG-SA about intercompatibility issues between GSM terminals and SIM and 3GPP terminals and USIMs. See section 10 for further information on this issue.
6	Liaisons from other groups
T3-99101 is an LS from T2 regarding terminal capabilities. It contains a set of fundamental definitions that T2 has found appropriate to use within this work. T2 requests all relevant WGs and SWGs to study these definitions and their implications carefully. After examination of the document, a reply was drafted in T3-99121. It states that T3 has currently no further requirements for terminals. It was approved for sending to T2.
T3-99104 is an LS from the ETSI committee, Human Factors (ETSI TC HF). They inform T3 and several other committees that they have published documents which might be of use to 3GPP. These documents have been written in order to improve the usability of telecommunications equipment for all users and, in particular, for people with special needs. A discussion on the topic concluded that it would be possible for T3 to specify special data fields on the USIM to meet the needs, but that service requirements would be needed from SA1 before any work could be started. An LS to SA1 (cc ETSI HF) in T3-99122 was drafted and approved informing these committees of these conclusions.
7	USIM and UICC requirements (3GPP 21.11)
T3-99112 contains 3GPP 21.11, version 1.3.0. This is based on version 1.2.0 with the addition of the two contributions (T3-99091 and T3-99092) which had been approved at the T3 #3 meeting in Helsinki.
A discussion then took place to determine the areas in which 3GPP 21.11 still required further work before it could be considered to be complete. The following issues were raised:
-	should the T=1 protocol be made mandatory in the UICC? The existing 3GPP 21.11 states that the support of T=1 is mandatory for the terminal but optional for the UICC. Two companies stated that they would object to the UICC requirement being changed from optional to mandatory. Eight companies indicated that they would prefer it to be mandatory.

	Gemplus and Schlumberger provided a discussion document on this issue in T3-99135. The discussion on this document centred mainly on the problem of the transmission of large amounts of data (e.g. at the beginning of a session when the ME reads subscriber related data to be stored in the ME) and the statement in the document that "the feasibility of an efficient implementation (for the SIM Application Toolkit) is not demonstrated today". Concern was expressed by several delegates about the latter. The question was raised whether, if T=1 was not going to be mandatory for the UICC for the support of the USIM, it should be mandatory for the ME. The Chairman then requested contributions for the next meeting from, in particular, IC card manufacturers on the advantages and disadvantages of the two protocols and the potential "dependency" of GSM 11.14 on one of them. The issue will also be raised at the next SMG9 plenary.

-	in subclause 9.1, it was questioned whether the GPRS EF should be mandatory for the USIM. It was concluded that it should be mandatory because GPRS would be an important part of 3GPP and because the EF only consumed a small amount of  memory anyway.

-	it was agreed to avoid the use of the word "level" in subclause 9.

Several other editorial changes were made and so a new version (v1.4.0) was produced in T3-99133. A final review of this document towards the end of the meeting revealed several editorial issues requiring correction and the following points requiring additional text. The latter were:
-	clause 9.1: clarification is required that an ME may only reject the USIM if the indicated supply current "is above the maximum value defined for use by the UICC for running the USIM";
-	"Language indication" is to be added in clause 10.1 to the USIM related information list;
-	in clause 10.2.5 "entry names" is to be replaced with "entries";
-	the text in clause 11.2 does, of course, not preclude the support of, for example, the PDC application on the UICC. A note will be added for clarification.

It was agreed that these changes should be incorporated into a new version (v1.5.0) by the T3 secretary after the meeting. This was done and version 1.5.0 was made available after the meeting as T3-99136. It was further agreed that this document (v1.5.0) should be submitted to TSG-T #3 (22 ‑ 23 April) for approval. 
Secretary's notes after T3 #4 meeting: 
-	In line with the 3GPP working procedures, reports and specifications forwarded to TSG-T for approval are changed to version 2.0.0. Thus, version 1.5.0 of 3GPP 21.11 in T3-99136 was submitted to TSG-T as v2.0.0 in TSG-T document TP-99085. There were no changes made between v1.5.0 and v2.0.0. TSG-T approved the document. This means that it will be released as v3.0.0. It also means that any further changes to 3GPP 21.11 must be done by submitting a change request to T3. If the change request is approved at T3, it must then be submitted to TSG-T for approval. If approved at TSG-T, an updated version of the specification will be made available shortly thereafter. Due to the new numbering procedures, it is likely that the document will be renumbered as 21.111. Furthermore, the 3GPP support team will do the necessary changes to the general clauses such as the Foreword. TSG-T also agreed to change the "status" of the document from "Technical Report" to "Technical Specification".

-	21.111 was the first, and so far only, 3GPP TSG-T document to be approved. The T3 Chairman thanked all T3 delegates for their efficient and co-operative work in producing this specification.

8	USIM and UICC Specification
The sub-sections below refer to the temporary specification numbers of 31.XX, 31.YY and 31.ZZ. More information about these numbers and the contents of these specifications can be found in section 9 of this report. 
8.1	Mechanical  /  electrical interface 
No specific documents were registered and received during the T3 #4 meeting on this issue. However, a splinter group during the T3 meeting did discuss these issues as part of the new deliverable "UICC physical and logical characteristics" (see section 9 below).
8.2	Security principles
Documents T3-99126 and T3-99127 were received late during the meeting. T3-99127 contains a requirement specification from the 3GPP security working group, SA3. It is entitled: S3.03 v0.2.0 "3G Security: Security Architecture". T3-99126 is a covering note for this specification from the S3.03 rapporteur. The note lists several open items and requests that T3 review and comment on the document with regard to USIM related issues.The documents will be discussed in detail at the next meeting.
T3-99103 proposes the addition of new text on the security features "authenticate" and "resynchronise" and the respective commands to "new GSM 11.11". The necessity for the text comes from the new (compared to GSM) requirements specified in S3.03. It was noted that SA3 are also still discussing a new method of local authentication which is likely to have an impact on the USIM. The proposal in T3‑99103 started a discussion on which of the two documents 3GPP 31.YY and 3GPP 31.ZZ should contain which security features.
It was agreed that USIM security issues and above document should be divided as follows:
-	general security characteristics (like file access conditions and the authenticate command) should be covered in 31.YY;
-	specific security issues should be covered in 31.ZZ.

During the meeting, a splinter group continued drafting work on 31.YY. The revised version of the specification was made available shortly afer the meeting in T3-99131. The splinter group concluded that the main open issues that still need to be addressed are:
-	is there a need to define a security environment?
-	what should be contents and coding of historical bytes?
-	should extended addressing be supported?
-	should the APDU format in table 9.1 in T3-99107 be used ?
-	Table 9.4: GSM commands begin with AX. Should the 3GPP commands start with 0X where appropriate?
-	should future commands be coded according to ISO/IEC (0X) or GSM (AX)?
-	what is the impact of logical channels on existing card platforms? Card manufacturers are requested to check this issue.

Within the splinter group, two particular action items were recorded. Schlumberger undertook to produce an input paper on the linking of USIM and GSM applications and sharing of EFs. Nokia undertook to produce an input paper on memory organisation scenarios based on figures 5.1 and 5.2 in T3-99107.
8.3	ADNs and usage of index files 
T3-99110 (an updated version of T3-99109) is a proposal for the implementation of a phonebook on the USIM. During a discussion on the document, the following points were noted:
-	if only transparent files are used, a power failure during update may cause the entire phone book to be destroyed and it was therefore agreed that transparent files should not be used;
-	as a working assumption, 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;
-	it was agreed that the EFADN should not be mandatory.

An updated version of the proposal taking into account the above (and other) comments was made available in T3-99134. However, the author felt that further elaboration was required before the feature should be fully incorporated into 3GPP 31.ZZ. An updated version of T3-99134 will therefore be made available before the May T3 ad hoc meeting.
8.4	File Management 
T3-99113 is a discussion document on the UPDATE access condition for EFMSISDN. It is proposed that the UPDATE access condition for EFMSISDN should be modified to ‘CHV1/ADM’ so that the operator can choose which condition is to be applied. The document was noted.
During the meeting, a splinter group continued drafting work on 31.ZZ. Regarding file management, the following points were noted:
-	file selection by path is now included;
-	application selection should be moved to 31.YY.

T3-99128 is a extract from UMTS 21.11 version 1.0.0. This describes two different methods of CHV management. It was considered to be to detailed for a requirements specification and was therefore deleted from UMTS 21.11. (see also T3-99051, which has not been fully discussed within T3). The two T3 ad hoc meetings in May should jointly discuss these two documents  and produce an output to the T3 plenary.
8.5	USIM files and procedures 
T3-99116 contains the first draft of 3GPP 31.ZZ, "USIM characteristics". The document was reviewed by a splinter group during the meeting. The following points were noted:
-	31.ZZ should specify all files under the directory DFUSIM.
-	all languages should be specified according to ISO/IEC and it was agreed that the EF should be changed to "Preferred Languages". The file ID would remain the same as EFELP as specified in GSM 11.11. It should be mandatory at the MF level, while an optional file "language indicator" at the USIM application level should contain the language used. Both should have READ access condition ALW.
-	EFBCCH - this EF requires further study, but will probably have to be replaced or supplemented with something more related to 3GPP.
-	EFPHASE will be replaced by EFAP as specified in T3-99129. The file ID will remain the same and this should not be a backwards compatibility problem as the new EF will be under the USIM.

The proposal for a Phone Book as described in T3-99134 was agreed in principle. An updated version of the document will be made available by the ad hoc meeting in May.
8.6	General issues 
T3-99105 contains GSM 11.11 v7.2.0 "SIM / ME interface for GSM". It was agreed that this document should be used as a basis for the further development of 31.YY and 31.ZZ.
T3-99107 contains the first draft of the logical characteristics of the UICC/USIM, 31.YY. As mentioned below in section 9 of this report, it was agreed that the name of this document should be changed to "UICC physical and logical characteristics" and that its scope should include the physical characteristics of the UICC. The document was reviewed during the meeting by a splinter group.
T3-99114 contains a proposal to define a new EF that would indicate the USIM phase in a single byte. It was proposed that the EF should a TLV object called "Application Profile" and placed under the application DF. The first byte would indicate the phase of the UICC and the remaining bytes would be reserved for future use. The revised document T3-99129 will be further discussed at the next meeting.
9	T3 Work Items
T3-99106 is a draft of the T3 work items created from the information available at the TSG-T #2 meeting in Ft Lauderdale. This information is available via internet, currently at http://www.etsi.org/EWPweb/. It is expected that this location will be moved to the 3GPP server in the near future. The document was noted.
At T3 #3 in Helsinki, it had been concluded that T3 should initially produce four documents:
-	"USIM and IC card requirements";
-	"UICC electrical and mechanical characteristics";
-	"UICC logical aspects";
-	"USIM specific aspects."

This structure was re-discussed at T3 #4. It was concluded that the work items should be reorganised into general aspects related to the UICC and specific aspects related to the USIM application. It was agreed to use the following:
-	3GPP 21.11 "USIM and IC card requirements"
-	3GPP 31.YY "UICC physical and logical characteristics" (incorporates the electrical and mechanical aspects)
-	3GPP 31.ZZ "USIM characteristics"

T3-99102, T3-99111, T399115 are draft  work item descriptions for the three T3 work items. They were discussed and then revised in line with the conclusions above. They were reissued as T3‑99123, T3‑99124 and T3‑99125. Some further editorial revisions were made and the 3 work items were combined into a single document, T3-99130. This document also reflects the revised (tight) timescales that were believed to be the shortest possible possible time required to achieve the set goals. It was agreed that this document should be submitted to TSG‑T #3 for approval.
10	Inter system compatibility issues
At T3 #4, an LS was sent to SA1 requesting clarification of the issue of cross-system compatibility. Although SA1 have not held a meeting since receiving the LS, they have discussed the issue. So far, SA1 has not changed this requirements.
An LS was drafted to SA1 in T3-99120. This was to inform SA1 that a resolution of the cross system compatibility issue is urgently required. However, as T3 would only be affected by a change of the second part of the requirement in clause 14.4 of UMTS 30.01 (v3.6.0), i.e. "that 3G terminals support 3G USIMs" and not by a change to the requirement that "3G terminals support existing (Phase 2) USIMs", the meeting concluded to mention the issue only via the T3 status report at TSG-T #3.
11	Any Other Business
11.1	Terminology
The use of the following terminology was agreed:
USIM	Universal Subscriber Identity Module
UICC	Not yet defined (was UMTS Integrated Circuit Card)

12	Meeting Plan
The meeting agreed the dates for T3 #5, T3 #6 and T3 #7, with the meeting in Miami (T3 #6) being subject to confirmation. Some other related meetings are also mentioned below for information:
It was agreed that two ad hoc sessions would be held just prior to the next Plenary.
Meeting	Date	Host	Location	
T3 ad hoc	27-28 May, 1999	Nokia	Copenhagen, Denmark	
T3 ad hoc	27-28 May, 1999	Nokia	Copenhagen, Denmark	
3GPP T3 #5	31 May - 2 June, 1999	Nokia	Åland Islands, Finland	
3GPP T3 #6	14 - 16 June, 1999	Nokia Inc.	Miami, USA	
3GPP T3 #7	5 - 7 July, 1999	Ericsson	Lund, Sweden	
----- Related meetings and other ad hoc groups (for information) ------	
ETSI SMG9 #18	01 - 04 June, 1999	Finnet, Nokia, Sonera, Telehallintokeskus	Åland Islands, Finland	
3GPP TSG-T #4	17 - 18 June, 1999		Miami, USA	
SMG Plenary #29	23 - 25 June, 1999		Miami, USA	
ETSI SMG9 #19	28 Sept. - 1 Oct.,1999	Giesecke & Devrient, Siemens	Munich, Germany	
3GPP TSG-T #5	7 - 8 Oct., 1999		Korea	
SMG Plenary #30	8 - 12 Nov., 1999	ETSI	Sophia Antipolis, France	
3GPP TSG-T #6	13 - 17 Dec., 1999			

13	Closing of the Meeting
The meeting was closed at 16:50. The chairman thanked the host NTT DoCoMo for the excellent organisation of the first (but not last !) 3GPP T3 meeting in Japan.

ANNEX A	List of delegates

NAME	ORGANISATION		EMAIL	
	-- ARIB Organisations --			
ALANARA Seppo	NOKIA	JP	Seppo.alanara@japan.nmp.nokia.com	
FURUSE Masahiro	NTT DoCoMo	JP	furuse@cet.yrp.nttdocomo.co.jp	
HONDA Yoshio	Nippon Ericsson	JP	yoshio.honda@ericsson.co.jp	
KANAMARU Yuichi	Mtorola Japan Ltd.	JP	kanamaru@cig.nml.mot.com	
KUWABARA Kenji	NEC Coproration	JP	k-kuwa@ccmail.mcd.yh.nec.co.jp	
ONO Kenichi	Panasonic	JP	kenono@pcd.mci.mei.co.jp	
SHIMURA Kazuo	Mitsubishi Electric	JP	shimura@csc.melco.co.jp	
TAHARA Mikio	Nippon Ericsson	JP	mikio.tahara@ericsson.co.jp	
WAKABAYASHI Tatsuaki	NTT DoCoMo	JP	waka@mdev.yrp.nttdocomo.co.jp	
WAKAKI Moto	Japan Telecom Co. Ltd	JP	wakaki@japan-telecom.co.jp	
	-- ETSI Organisations --			
AHLGREN Kristina	ERICSSON L.M.	SE	kristina.ahlgren@ecs.ericsson.se	
BARNES Nigel	MOTOROLA	GB	Nigel.Barnes@motorola.com	
BASQUIN Bruno	GEMPLUS Card International	FR	bruno.basquin@gemplus.com	
BOS Lieve	Alcatel Bell	BE	Lieve.bos@alcatel.be	
BRUSCHI Poalo	TELECOM ITALIA	IT	pbruschi@tim.it	
CAZIER Jean Lin	CEGETEL/SFR	FR	jean-lin.cazier@cegetel.fr	
CHAUTARD Vincent	Schlummberger K.K.	FR	Vincent@fuchinobe.skk.slb.com	
GASTON Loaento	SCHLUMBERGER SSS TEMES	FR	gaston@montrouge.tt.op.com	
GEMME Paolo	ITALTEL S.p.A.	IT	paolo.gemme@italtel.it	
HABBAL Owar	Schlummberger	FR	ohabbal@san-jose.tt.slb.com	
KOMINE Masaaki	GEMPLUS JAPAN	JP	komine-m@gemplus.co.jp	
LAMBINON Christophe	GEMPLUS JAPAN	JP	lambinon@gemplus.co.jp	
LINDHOLM Rune	NOKIA MOBILE PHONES	FI	rune.lindholm@nmp.nokia.com	
MARINGER Günter	Deutsche Telekom MobilNet	DE	guenter.maringer@t-mobil.de	
ONG Jennie	GEMPLUS	AM	Jennie.Ong@gemplus.com	
OREN-Pines Yaron	Philips		yaron.oren-pines@philips.com	
OTAKE Michinori	NISSEI SANGYO	JP	otakem@misseisg.co.jp	
RENAUD Nicolas	FRANCE TELECOM	FR	nicolas.renaud@cnet.francetelecom.fr	
RUANT Dorine	MITSUBISHI Electric	FR	ruant@mef.mee.com	
SANDERS Michael	ETSI	FR	michael.sanders@etsi.fr	
TAKANO Tomoharu	DAI NIPPON PRINTING 	JP	Takano-T4@mail.dnp.co.jp	
VEDDER Klaus	GIESECKE & DEVRIENT	DE	klaus.vedder@gdm.de	
VESTERGAARD Peter	NOKIA Mobile Phones Ltd	DK	peter.vestergaard@nmp.nokia.com	
	-- T1 Organisations --			
	-- TTA Organisations --			
PARK Sang-Keun	Samsung Electronics Co., Ltd	KR	skpark@khgw.info.samsung.co.kr	
RYU Joon S.	Samsung Electronics Co., Ltd	KR	joonryu@khgw.info.samsung.co.kr	

ANNEX B	Approved Agenda

	1	Opening of the Meeting	document(s)
	2	Roll Call of Delegates
	3	Input Documents / Agenda	118
	4	Approval of report from TSG-T3 #3	099
	5	Results from other related meetings	
	6	Liaisons from other groups	101,104
	7	USIM and UICC requirements (21.11)	112
	8	USIM and UICC Specification
		8.1	Mechanical / electrical interface	
		8.2	Security principles	103,126,127
		8.3	ADNs and usage of index files	110
		8.4	File Management	113
		8.5	USIM files and procedures	116
		8.6	General issues	105,107,114
	9	T3 Work Items	102,106,115
	10	Inter system compatibility issues	
	11	Any Other Business
	12	Meeting Plan
	13	Closing of the Meeting

ANNEX C	Access to 3GPP documents
This document briefly outlines some of the more important locations of information that all T3 members should be aware of. 
3GPP email lists:
To receive information about T3 issues, all delegates and other interested parties MUST register for email list 3GPP_TSG_T_WG3. This can be done by sending an email to LISTSERV@LIST.3GPP.ORG with the following single line of text in the body of the message:
subscribe  3GPP_TSG_T_WG3  YourFirstName  YourLastName

There are many other 3GPP email lists that may also be of interest. Go to http://www.3gpp.org/e‑mail.htm for further information.
If at any time you would like to confirm which lists you are currently a member of, just sent a message to  LISTSERV@LIST.3GPP.ORG with the following single line of text in the body of the message:
QUERY *

Email archives:
All 3GPP lists have an associated archive of every email sent via that list. Information on how to access the archive are sent to you when you subscribe to the list. This means that if you have temporary email problems, or have just joined the group, you can check to see if you have missed any messages. The easiest was to search the archive is first to request a list of all messages sent to the particular group you are interested in. For example, to get a list of message sent via the 3GPP_TSG_T_WG3 list between 1st March 1999 and the current date, send the following command to LISTSERV@LIST.3GPP.ORG:
search * in 3GPP_TSG_T_WG3 since March 1999
As well as a list of emails sent, you receive instructions about how to retrieve the emails.
Meeting invitations and meeting calendar:
The central location for all information relating to the 3GPP meeting calendar and the corresponding meeting invitations can be found at: http://www.3gpp.org/Meetings.htm
In particular, the meeting invitations to all WG3 meeting will be made available under the directory: ftp://ftp.3gpp.org/TSG_T/WG3_USIM/INVITATIONS/
Documents on the server:
All documents submitted to T3 meetings will be made available on the 3GPP document server in a directory (related to the number of the meeting) under: ftp://ftp.3gpp.org/TSG_T/WG3_USIM/ 
e.g. the documents for  T3 meeting #2 can be found at: ftp://ftp.3gpp.org/TSG_T/WG3_USIM/TSGT3_02

ANNEX D 	Document list
Tdoc	Title	Source	Status	
T3-99099	Draft report of T3#3 (March 16-18, Espoo)	Secretary (NB)	revised - see T3-99119	
T3-99100	Draft agenda for T3 #4 (April 19 - 21, Tokyo)	Secretary	revised - see T3-99118	
T3-99101	LS from T2 on Principles for the continued work with Terminal Capabilities	T2 (T2-99282)	discussed - see T3-99121	
T3-99102	Draft Work item description: USIM and UICC functional characteristics	T-Mobil	revised - see T3-99123	
T3-99103	Proposed text on authentication command for “new 11.11”, clauses 3, 8, 9 and 11	T-Mobil 	discussed	
T3-99104	LS from ETSI TC HF - Co-operation between TC HF and 3GPP	ETSI 	discussed - see T399122	
T3-99105	GSM 11.11 V7.2.0	ETSI	discussed	
T3-99106	T3 work Program - to be updated during T3#4 for submission to TSG-T#3	TSG-T secretary 	discussed	
T3-99107	3GPP 31.YY v0.1.0 - UICC / UE interface; Logical characteristics	Nokia / Ericsson	discussed	
T3-99108	Not issued		not issued	
T3-99109	Disscussion document: Proposal for Implementation of a "Phone Book" in  the USIM (Draft version is missing a diagram)	Nokia	revised - see T3-99110	
T3-99110	Disscussion document: Proposal for Implementation of a "Phone Book" in  the USIM (includes the diagram missing in T3-99109)	Nokia	revised - see T3-99134	
T3-99111	Draft Work item description: Physical and electrical characteristics	Nokia	not issued - see T399	
T3-99112	3GPP 21.11 V1.3.0 "USIM and IC card requirements for 3G systems"	Secretary	replaced by T3-99133	
T3-99113	Discussion document: UPDATE access condition for EFMSISDN	NTT DoCoMo & Japan Telecom	discussed	
T3-99114	Discussion document: proposed USIM version management	NTT DoCoMo & Japan Telecom	revised - see T3-99129	
T3-99115	Draft work item for Draft Work Item on USIM Interface Specifications 	Nippon Ericsson	revised - see T3-99125	
T3-99116	Contribution to USIM files and procedures	Nippon Ericsson	discussed	
T3-99117	Not issued 	withdrawn	not issued	
T3-99118	Agenda for T3 #4 (April 19 - 21, Tokyo)ChairmanapprovedT3-99119	Report of T3 #3 (March 16-18, Espoo)SecretaryapprovedT3-99120	Draft LS to TSG SA1 on GSM SIM behaviour in 3GPP terminalsT3 discussed - not approvedT3-99121	LS to TSG T2 on terminal capabilitiesT3approved -> T2	T3-99122	LS to TSG SA1 cc TC HF on Need for special field on the 3GPP-UICC regarding human factors T3approved -> SA1 and ETSI HF	T3-99123	Draft WI description for "USIM and IC card requirement" (3GPP 21.11)	T3	replaced by T3-99130	T3-99124	Draft WI description for "UICC physical and logical characteristics"	T3	replaced by T3-99130	T3-99125	Draft WI description for "USIM characteristics"T3	replaced by T3-99130	T3-99126	LS from S3.03 rapporteur "Request for feedbacl on S3.03"	S3.03 rapporteur	discussed	
T3-99127	S3.03 V.0.2.0 "3G Security: Security Architecture"	S3.03 rapporteur	noted	
T3-99128	Extract from UMTS 21.11 v on CHV handling	Secretary	noted	
T3-99129	USIM version management	Nippon Ericsson	discussed	
T3-99130	T3 work items	T3	agreed ->TSG-T for approval	
T3-99131	3GPP 31.YY V0.2.0 	T3	discussed	
T3-99132	Not issued 		not issued	
T3-99133	3GPP 21.11 V1.4.0 "USIM and IC card requirements for 3G systems"	T3	revised - see T3-99136	
T3-99134	Disscussion document: Proposal for Implementation of a "Phone Book" in  the USIM	Nokia	discussed	
T3-99135	Discussion document on T=1 protocol	Schlumberger / Gemplus	discussed	
T3-99136	3GPP 21.11 V1.5.0 "USIM and IC card requirements for 3G systems"	T3	agreed -> TSG-T for approval