Documents for TSGN1 meeting #8, 25.-29.October 1999, Kobe, Japan	Yellow cells indicate an allocated but not available Tdoc	
Agenda item	Agenda item title	Tdoc 3GPP N1-99	Title	Spec.	Source	Result	
1	Opening					25.10.1999 at 9:40 (estimate)	
2	Approval of agenda; document allocation	B40	Agenda		N1 Chairman	Noted. This file is a.k.a. Kobe9910.rtf	
		B41	SA meeting report		MCC	Noted.	
		B42	TSGN Plenary #5 meeting report		MCC	Noted.	
		B43	TSGS #5 Highlights		MCC	Noted.	

3	Input Liaison statements						
		B44	freezing GSM Release 97 & Release 98		TSG-N	Noted.
TSGN Plenary revision of N1 & N2 originated LS with the same title.	
		B48	RAB requirements for CS data and architecture for CS data services		TSG-S2	Noted.
S2 answers N3 questions on RAB requirements.
Linked with B63, B75.	
		B49	SAT/MExE <-> CAMEL Interworking / Traceability		TSG-S1	Noted. No discussion, no volunteer rapporteurs for the work item.
N_SS ad-hoc must be involved also.
S1 answer our question on SAT transaction traceability. We can now do our part in N1.
Linked with C70.
The delegations are requested to start the work on N1 specifications.	
		B50	DRX Parameter IE in 24.008		SMG2 WPA	Attached CR agreed, copy in D24. LS back in D23
Discussion. 
Can the attached CR be agreed?
Reply needed.	
		B51	Issues with Multiple PDP Contexts		SMG2 WPA	Noted. 
SMG2 answer to SMG7 question on multiple PDP contexts.	
		B52	PLMN selection for GPRS mobiles 		SMG2 WPA	Noted. 
SMG2 response to N1 LS in TSGN1-99835. This was seen in TSGN #5 and consequently 03.22 CR A032 r2 was rejected.	
		B53	L3 segmentation		SMG2 WPA 	Withdrawn. 
This is an old revision of B57. 
SMG2 WPA say they have not yet studied the matter in detail but promise to do so later. Linked with B70.	
		B54	management of TLLI during P-TMSI reallocation procedure		SMG2 WPA	Noted.
Discussion is already ongoing on the mailing list and the delegations are invited to participate. At the moment N1 has got nothing further to add.	
		B55	addition of 3rd MNC digit in routing area identification		SMG2 WPA	Noted.
SMG2 agree our proposal to add the 3rd MNC digit to GPRS IEs.	
		B56	FLUSH-LL procedure defined in GSM 08.18 for GPRS		SMG2 WPA	Noted.
The discussion in SMG2 was reported to be still ongoing and N1 has got nothing to add for now.	
		B57	L3 segmentation		SMG2 WPA	Noted.
SMG2 WPA say they have not yet studied the matter in detail but promise to do so later. Linked with B70.	
		B58	LS on Service/Baseline Implementation Capabilities		SS Ad-hoc	Noted.
SS Ad-hoc comments to T2 on terminal capabilities. Linked with C69.	
		B59	addition of 3rd MNC digit in routing area identification		TSG-N2	Noted.
N2 agree to add the 3rd MNC digit to GPRS IEs and promise to deliver their CRs to SMG TC #30.	
		B60	on multicall and enhancement of call barring services		TSG-N2	Noted.
N2 need S1 guidance to proceed with multicall.	
		B61	Active Location Retrieval in CAMEL Phase 3		TSG-N2	Discussion
Reply in Tdoc C80.	
		B62	Combined mobility management		TSG-N2	Noted.
There's still outstanding work with combined MAP operations at N2 and they propose that other more important WIs are done first.
Linked with B79.	
		B63	RAB requirements for CS data		TSG-N3	Noted.
N3 is asking S1 and S2 guidance to define RABs for CS data. Not sent to N1.
Linked with B74 and B75.	
		B64	Response to N2 LS on Tandem Free and Out of Band Transcoder Control		TSG-N2	Noted.
Plenary agreed. Enhanced WI descr for Out-of-band transcoder control in Tdoc NP-99292, TR in NP-99288. CC: to TSGN	
		B65	Definitions for usage of Multi-mode/system terminals		TSG-R2	Noted.
R2 response to LS from T2 on terminology	
		B66	Uplink core network layer 3 message numbering		TSG-R2	Noted.
R2 say they see N1 proposal on L3 message numbering probably feasible and treat it as their working assumption. R2 promise to inform us on their progress.	
		B67	registration areas and on hierarchical tracking concept		TSG-R2	Noted.
R2 reply to S2 on RRC connection release timer.	
		B68	Common Identification for Relocation Co-ordination		TSG-R3	-	N1 sees that the proposed mechanism would work.
-	S1 may need to be involved because of the service requirement on emergency call with no SIM.
-	Reply in C81.
Reply needed.	
		B69	Security mode control procedure		TSG-R3	Noted.
Proposed reply by Fujitsu in Tdoc C11.	
		B70	L3 Segmentation			Noted. 
RAN3 answer our proposal to study L2 segmentation by saying that maximum payload size of about 4kB can be achieved. Linked with B53.	
		B71	Common Communication Mechanism to be used by the Cell Broadcast Service		TSG-S2	Noted.
S2 liaise their architecture solution for the Cell Broadcast Service. No N1 action is proposed. Linked with B85.	
		B72	Multimedia call control for R99		TSG-S2	Noted.
The LS was not seen but its contents was discussed in TSGN1 #7. N1 has already reacted to this.	
		B73	ciphering of the initial message		TSG-S2	Noted.
The LS was not treated but its contents was discussed in TSGN #7. Related CR in Tdoc ???	
		B74	RAB requirements for CS data and architecture for CS data services		TSG-S2	Withdrawn, this is an older revision of B48.
S2 answers N3 questions on RAB requirements.
Linked with B63, B75.	
		B75	UMTS and RAB parameter value ranges and granularity		TSG-S2	Noted.
Proposed reply in B98 by DoCoMo.
Also B96 and B97 are related.
S2 is asking reasonable values for RAB parameters
Linked with B63, B74.	
		B76	Liaison Statement to N2 on inter-3G MSC Handover		TSG-S2	Noted.
S2 have decided that for UMTS to UMTS Inter-MSC Handover the GSM E i/f transporting BSSAP messages with necessary modifications for GSM to UMTS Handover shall be used.	
		B77	Response to the LS on Location Area concept		TSG-S2	Noted.
S2 says that R99 RA / LA = R97 RA / LA. We already got this message during TSGN1 #7. Linked with B78.	
		B78	registration areas and on hierarchical tracking concept specification status in SA WG2			Noted.
We responded to this already from TSGN1 #7 causing S2 to rethink and send N1 the LS in B77.
Linked with B77.	
		B79	Combined procedures		TSG-S2	Noted.
S2 acknowledge N2 understanding that there are more important issues than this for R99.	
		B80	Iu UP protocol framing of NAS user data		TSG-S2	postponed, see this together with C68.
New proposal for QoS TR. N1 to check the mapping of QoS (and BC?) parameter mapping to RAB.	
		B81	SMG3 WPA / TSG-CN WG1 in reply to Liaison statement on type approval testing for error case handling (N1-99890)		TSG-T1	Noted.
T1 reply to our question on QoS test cases that the error cases we ask are not covered in 34.123. They also say that they can provide the TCs but those TCs will still be subject to voluntary certification.	
		B82	handover notifications		TSG-T2	Noted. 
It seems to be a question of knowing the properties of the current RAB, not the negotiated QoS. Not really an N1 issue.
It is possible to change the QoS without performing a HO procedure. Would this be interesting for MExE too?
MExE only wants to know about handovers in order to be able to monitor the current QoS, not to intervene with the HO procedures.
The required N1 action is to provide this information to MExE application. Linked with B84.	
		B83	5 or 6 digits IMSI HPLMN		TSG-T2	T2 are asking for the right criteria to use either 5 or 6 digits MNC from SIM card. 23.022 gives the answer. Check the number of MNC digits in downlink BCCH info and compare the BCCH MNC with the same number of digits on the SIM IMSI field. But how does this help MExE to decide what is the length of the IMSI MNC part on the SIM?
This works fine if you are registered to home PLMN but if you are not then this information is not available.
What is the HPLMN MNC needed for? All the MM procedures can be covered with the information that is already in 23.022.
Answer in C82.	
		B84	MExE support of QoS negotiation and handover notifications		TSG-T2	Noted.
R2 has asked the same question as we did and this is the same answer from T2 to R2 as N1 has got in B82. Linked with B82.	
		B85	CBS Responsibilities		TSG-T2	Noted.
T2 propose S2 that CBC should be evolved from GSM. Linked with B71.	
		B86	Definitions for usage of Multi-mode/system terminals		TSG-T2	Noted.
Linked with B65.	
		B87	Enhanced User Identity Confidentiality		TSG-S2	Discussion.
What is N1 role in this question?	
		C12	T1P1.5 LCS work plan		T1P1.5	Reply in Tdoc C92
T1P1 are proposing the LCS to 3GPP for R99. 	
		C66	Liaison Statement on Issues with Multiple PDP Contexts		SMG7 GPRS	Noted.
This question on GPRS TCs should have been answered by 11. October but we have not seen the LS before this meeting. SMG2 WPA answer in B51. 	
		C67	LS to S1 on 3G Services		CN3	Noted.
Two questions from N3 to S1, Is Modem/ISDN interworking WI needed at all and is PDP type X.25 still supported by CN.	
		C68	LS on Iu UP Protocol Framing of NAS User Data		CN3	Noted.
TSG-CN3 is of the opinion that it appears reasonable to have an Iu UP frame size dependent on the bearer capability to satisfy that service QoS.	
		C69	Response to LS on Service/Baseline Implementation Capabilities		CN3	Noted.
N3 comments on Service/Baseline Implementation capabilities. Linked with B58.	
		C70	Answer to LS on SAT/MExE  <-> CAMEL Interworking / Traceability		SMG9	Noted.
SMG9 indicate that they have not had time to progress Interworking between SAT/MExE and CAMEL and traceability of SAT/MExE actions. They are proposing SMG9 – N3 joint meeting. Linked with B49	
		C78	Information about current status on UE idle mode operation			Response in C83.
Preference of system is PLMN operator decision and it is also a parameter to the cell selection and re-selection procedure at MS. 
dHow to communicate this preference to the MS?
-	Store it on SIM & SAT update?
-	Downlink BCCH indication?
-	Some other downlink indication?
Is the MS allowed/requested/not allowed to use this knowledge of the preferred system for PLMN selection? (if not, then this piece of information becomes completely transparent to the CN protocols in the MS)
Should 23.022 be split to cell selection and PLMN selection parts in the long run?
If yes, what else is needed for R99 than PLMN selection part of 03.22? Cell selection is already well covered in 05- and 25-series.	
		C94	Liaison statement on 3G-H.324M		N2	Noted.
N2 acknowledge our decision to use H.324M over transparent BS and promise to draft the necessary 23.016 and 29.002 CRs to define a new bearer service. Also SS_ad-hoc is asked to consider the supplementary services.	
		C95	Response LS on Service and Baseline Implementation Capabilities		N2	Noted.
N2 acknowledge our LS on terminal capabilities and say they have done nothing. Will T2 take over this issue from now?	
		C96	Liaison statement on Multicall		N2	Noted.
N2 is working on multicall as basic service, not as SS. This means that no subscriber control and interrogation procedures will be provided. N2 is asking S1 to confirm this assumption.	
		C97	Response to LS on 5 or 6 digits IMSI HPLMN		N2	Noted. Our reply to T2 is in Tdoc C82.	
		D35	Liaison statement on Basic principles of QoS interoperations			Noted.	
		D37	Principles for secure GSM-UMTS interoperation			Noted.	
		D39	Reply to LS on Security Algorithm Information in UE Capability		R3	Noted.	
4	Maintenance of R98 and older releases						
4.1	Corrections						
		D12	Correction of Figure A.2 in Annex A	03.22	Ericsson	Agreed.
PCS 1900 Harmonization.
R98.	
		D13	Correction of Figure A.2 in Annex A	23.022	Ericsson	Agreed.
PCS 1900 Harmonization.
R99	
							
4.2	GPRS					Siemens volunteers to host GPRS Ad-hoc meeting if necessary right before TSGN1 #9 on Monday the 29.11.1999. -> this must be confirmed after TSGN1 #8 if it is needed.
GPRS ad-hoc meeting was not considered necessary as there were only 2 GPRS Tdocs in this meeting.
The latest versions of 23.121 and 23.060 were briefly revieved before discussing the other R99 packet contributions.	
		C31	Summary of 'agreed' Change Requests to GSM 04.08 SM/GMM	24.008	Rapporteur	Revised to C73.	
		C32	Summary of change requests to GSM 04.64	04.64	Rapporteur	Noted.	
		C73	Summary of 'agreed' Change Requests to GSM 04.08 SM/GMM	24.008	Rapporteur	Noted.
Revision of C31.	
		D24	DRX Parameter IE in 24.008		SMG2 WPA	Agreed
This CR was attached to LS in B50.	
		B90	Introduction of Reserved Service Labels in the APN	23.003	Ericsson	Revised to D26.
R99	
		C09	Service Request	24.008	Fujitsu	The working assumption to proceed with the PS SERVICE REQUEST – SERVICE ACCEPT principle was agreed.
R99 Packet data	
		C10	Introduction of Follow-on mechanism for PS	24.008	Fujitsu	Noted.
No objection against the principle the details of the CR still need some improvement.
Reference version, Work Item, affects!	
		C30	Network Requested PDP Context Activation	24.008	Vodafone	Revised to D00.
R99	
		C59	LLC SAPI handling	24.008	Fujitsu	Noted.
No objections agiainst the principle and this change will be incorporated in other SM CR later. (a revision of B88)
R99	
		C33	A-bit interpretation contradiction	04.64	Motorola	Agreed. (C4)
R97
Linked with C34, C35	
		C34	A-bit interpretation contradiction	04.64	Motorola	Agreed. (C4)
Cat. A rather than F.
R98
Linked with C33, C35	
		C35	A-bit interpretation contradiction	04.64	Motorola	Agreed. (C4)
Cat. A rather than F.
R99
Linked with C33, C34	
		D00	Network Requested PDP Context Activation		Vodafone	Revised to D25
Revision of C30.	
		D11	Service Request Procedure Description for Review		Fujitsu	Noted.
More comments are invited.	
		D25	Network Requested PDP Context Activation		Vodafone	Agreed
Revision of D00	
		D30	Clarification of DRX			Endorsed.
CRs which were attached in B50. These were already agreed by SMG2. 
Related with B50.	
		D31	Clarification of DRX			Copy of D31.	

4.3	Other Pre-99 WIs					T1P1.5 has now completed the following LCS CRs and TSs intended for approval in SMG#30 as part of GSM Release 98.

	CR for GSM 03.07	(CN2)
	CR for GSM 03.71	(CN1, CN2)
	CR for GSM 04.71	(CN1)
	CR for GSM 09.02	(CN2)
	CR for GSM 09.08	(CN1)
	GSM 09.31		(CN1)

T1P1.5 requests approval of the 09.08 CR by TSG CN1 and CN. T1P1.5 requests Email approval of the 03.07 and 09.02 CRs by TSG CN2 and CN. T1P1.5 requests endorsement of GSM 09.31 and the 04.71 CR by TSG CN1 and (via Email) by CN and requests endorsement of the 03.71 CR by TSG CN1 and (via Email) by CN2 and CN.

T1P1.5 expects to submit the remaining LCS CRs and TSs (not being submitted to SMG#30) to either SMG#30bis or SMG#31, and to seek approval for these in GSM Release 98.	
	LCS	C13	LCS CR for GSM 03.71	03.71	T1P1.5	Endorsed.	
		C14	LCS CR for GSM 04.71	04.71	T1P1.5	Endorsed.	
		C15	LCS CR for GSM 09.08	09.08	T1P1.5	N1 reviewed and agreed the CR. A question on the responsibility was raised and Ban confirmed that the specification is N2 responsibility. N2 have already seen and agreed this CR.	
		C16	LCS GTS 09.31	09.31	T1P1.5	Endorsed	
							
5 	Work Plan for TSGN WG1 for 1999					TSGN1 #8   25.-29.10.1999 (Japan/DoCoMo)
TSGN1 #9   30.11-3.12.1999 (Germany/Siemens)
TSGN #6 13.-15.12.1999 (Sophia Antipolis, France)
TSGN1 #10 11.-14.1.2000 (Japan/NEC)
SMG#31 14.-18.2.2000
TSGN1 #11 28.2.-2.3.2000 (Sweden/Telia)
TSGN#7  13.-15.3.2000
TSGN1 #12 15.-19.5.2000 (U.S./T1P1)
Proposal to move to next week 22.-26.5.1999 to align with N3 ???
TSGN#8  19.-21.6.2000
SMG#32 26.-28.6.2000
TSGN1 #13 11.-15.9.2000 (U.S./T1P1)
TSGN#9  25.-27.9.2000
SMG#33 6.-10.11.2000
TSGN1 #14 27.11 – 1.12.2000 
                                       (Tentative invitation Lucent)
TSGN#10 11.-13.12.2000

		B45	Rapporteurs for TSGN WG1 specifications		MCC	Noted.
The delegations are requested to provide rapporteurs. A rapporteur should be nominated to all specification under N1 responsibility.	
		B46	Specifications within TSG-N		TSG-N Chairman	Noted.
Should this be posted on a visible place on the website?	
		B47	Work Item list		MCC	Noted.
Should this be posted on a visible place on the website?	
		C51	3GPP calendar		MCC	Noted.	
		C54	working schedule of UMTS adaptation of GMM	24.008	NTT DoCoMo, NTT Commware	Noted.
The proposed principles were agreed.	
		C60	TR 30.801 v.1.0.0, Overall Project Plan		MCC	Noted.	
		C61	TR 30.802 v.1.0.0, Project plan on Bearer Services and QoS		MCC	Noted.
N1 rapporteur for 30.802 is Takashi Koshimizu.	
		C62	TR 30.804 v.1.0.0,Project plan on GSM/UMTS Interoperation and Mobility Management		MCC	Noted.

N1 rapporteur of 30.804 Hannu Hietalahti from Nokia.	
		C63	TR 30.808 v.1.0.0,Project plan on Packet Architecture and Circuit Architecture		MCC	Noted.	
		C64	TR 30.810 v.1.0.0,Project plan on Security		MCC	Noted.
N1 rapporteur of 30.810 Duncan Mills from Vodafone.	
		C65	TR 30.812 v.1.0.0,Project plan on Services and Service Platforms		MCC	Noted.	
		C75	Work Item list/questions and anwers on N1 work items		Chairman	Noted.	
		D08	Proposed change of N1 meeting schedule		NTT DoCoMo	Noted.
No changes were agreed to the meeting schedule.	
		D34	Proposed Plan toward UMTS-MM Adhoc, 22-24 November		NTT DoCoMo	Noted.
More time was requested for people to think about the working assumption but we still keep the deadline.	

6	Release 99						
6.1	Multicall						
		C19	Cause 'user busy' in Call Confirmed Message	24.008	Ericsson	Revised to C86	
		C52	Addition of the Stream Identifier Information Element	24.008	NTT Commware	Revised to C85	
		C53	Outline of the Stage 2 and stage 3 specifications for multicall	24.008	NTT Commware	Noted.
The architecture defined in existing basic call handling stage 2 specifications will be impacted and cosequently the work will be spread over multiple WGs. S2 needs to be kept up to date when changes are made.	
		C85	Addition of the Stream Identifier Information Element	24.008	NTT Commware	Agreed in principle with no major problems with the contents but the CR has been edited using revision marks from the previous CR, not from the reference specification and implementing it like this would not cause the effect N1 agreed.
Revision of C52.	
		C86	Cause 'user busy' in Call Confirmed Message	24.008	Ericsson	Agreed.
Revision of C19.	
		D02	Necessity of the introduction SI-IE to SM protocol in R99		NTT Commware	Revised to D21	
		D21	Necessity of the introduction SI-IE to SM protocol in R99		NTT Commware	Alternative 2 to use NSAPI instead of SI for PS was agreed as working assumption.
Revision of D02	
		D26	Cause 'user busy' in Call Confirmed Message	24.008	Ericsson	Agreed.
Revision of B90	
6.2	Multimedia call						
		B99	Technical Report on Multimedia Telephony		Nokia	Revised to C87
All TRs should be allocated a specification number. 	
		C76	Comments to the Technical Report for Multimedia (N1-99977)		Ericsson/ DoCoMo	The following changes were agreed to the TR:
•	Section 1 is already in TR in B99
•	Section 2 agreed to be moved to TR in General section
•	Reorganisation to "Agreed working assumptions" and "Open items" needs to be done.
•	3.1 the first assumption refers to 	
		C77	Comments to Multimedia Technical Report V 0.0.1 (N1-99B99)		Ericsson	The following changes were agreed to the TR:
•	It was agreed to include in the TR also those sections which are still under study but these must be clearly indicated to be not yet in the status of agreed working assumption.
•	Comments on section 3.2.2.1 are already incorporated in the TR.
•	3.2.2.2 just state the working assumption to enhance BC IE.
•	3.2.2.3. is moved to open items section
•	4.1 goes to open items section of the TR.
•	4.1.1 goes to open items section of the TR.
•	5. SS go to open items section of the TR.	
		C79	Basic multimedia call setup procedures		Ericsson/  DoCoMo	Noted.
The content s of this dicsussion paper is incorporated in the CRs that are presented to this TSGN1 #8 meeting.
•	Discussion on BC naming. N3 have been wondering whether BC for R99 should be renamed UMTS-BC. N1 are against this as that BC IE in R99 will also be part of GSM R99 implementation.	
		C87	Technical Report on Multimedia Telephony		Nokia	Noted.
Revision of B99.	
							
6.3	GSM / UMTS interworking					More time to work on this WI is needed, Nokia is willing to host an ad-hoc meeting in Finland 22.-24.November 1999.	
		C36	Project Plan for GSM/UMTS interworking and MM in UMTS		Chairman	Noted.
Chairman to report the contents of this Tdoc to the rapporteur of 30.804.	
		B88	Updating Session Management (SM) for R99	24.008	Nokia	Rejected.
Some main points:
•	The concept of secondary PDP context
•	GSM / UMTS applicable parts.	
		C17	Proposal for Needed Updates to 23.009	23.009	Ericsson	Noted.
•	One 23.009 to cover all or 03.09 for GSM HO and new UMTS spec for UMTS HO and GSM-UMTS HO?
•	How about SGSN?	
		C26	Uplink L3 sequence numbering	04.18	Vodafone	Rejected.
•	Intef-system HO?	
		C27	Uplink L3 sequence numbering	24.007	Vodafone	Revised to D14	
		C28	Uplink L3 sequence numbering	24.008	Vodafone	Revised to D15	
		C58	Principle for UMTS adaptation to GMM		NTT DoCoMo	Agreed the working assumption of including PMM states and state transitions in the GMM model rather than specifying a separate PMM.	
		D14	Uplink L3 sequence numbering	24.007	Vodafone	Agreed.
Revision of C27	
		D15	Uplink L3 sequence numbering	24.008	Vodafone	Agreed.
Revision of C28	

6.4	MS Classmark						
		B94	Proposal of Classmark 2 for UMTS	24.008	Nippon Telecommunications Consulting 	Revised to D05	
		C05	MS Classmark TR v042	24.008	Fujitsu	Noted.
Several changes were proposed, see the other documents under this WI.	
		C06	MS classmark related procedure descriptions	24.008	Fujitsu	withdrawn.	
		C07	Proposed Solution for MS Classmark Open Issues	24.008	Fujitsu	Working assumption that MS CM2 is included in LOCATION UPDATE REQUEST.	
		C08	Addition of Classmark for UMTS Interrogation procedure in MM	24.008	Fujitsu	Withdrawn, not needed after the working assumption made on C07 above.
Revised from N1-99980	
		C20	Comments to tdoc N1-99B09		Ericsson	Revised to C99.	
		C21	Contents of MS CN Classmark		Ericsson	Noted.	
		C23	Proposed solution for MS classmark open issues		Alcatel	Agreed working assumptions:
•	Alternative b, enquiry procedure, is chosen in section 12.2.1.3 in TR with the enquiry coming from RNC.
•	Figure in 12.2.2.2 in TR to be replaced with 1.4.1.2 from this Tdoc.
•	Section 12.2.3.1 is deleted from the TR.
•	12.3 in TR to be replaced with 1.5 in this doc with figure 4 updated.	
		C47	Classmark 3 handling at connection establishment		Nokia	Noted.	
		C48	Clarification on CN CM contents		Nokia	•	The text in 11.1 to be added to TR as such but the figure needs to be modified.
•	The text in 11.2.2 to be added to TR.	
		C49	Classmark handling in inter-system handover		Nokia	These points are already covered in Tdoc C23.	
		C99	Comments to tdoc N1-99B09		Ericsson	Noted.
The big decision is between R99 MS CM or different MS CM for R99 GSM and R99 UMTS. Another one between single MS CM for CN and separate PS and CS CM.
Revision of C20.	
		D04	MS Classmark TR v050		Nippon Telecommunication Consulting	Noted.

Revision of B94	
		D05	Proposal of Classmark 2 for UMTS	24.008	Nippon Telecommunications Consulting 	Agreed.

Revision of B94.	
							
6.5	L3 Segmentation					Study of L2 segmentation ongoing, RAN3 have answered that UTRAN is no problem, SMG2 promised to look at GSM RAN later.

WI needs to be moved to R2000. See B53 and B70	
							
6.6	Turbocharger						
		C22	Feasibility aspects of the Turbo Charger		Alcatel	Noted.	
		C50	Turbo Charger Technical Report version 0.0.3		Nortel Networks	Revised to D03	
		C84	Turbo charger hook for R99		Nortel	Noted.
•	Objection that the WI is still in feasibility study and  CRs to stage 3 can not be approved because of this.
•	Technical comment that in order to make R99 implementation Turbo compatible then at least the MS behaviour must be defined completely.	
		D03	Turbo Charger Technical Report version 0.0.3		Nortel	Not agreed. The latest additions to the scope of the WI from TSGN #5 in Kyongju have not been covered. These were considered too substantial to be left as open items.
Revision of C50	

6.7	EDGE					There's a problem with 03.22 CRs as they are on GSM 03.22 V.8.0.0 for R99.	
	Presented for information	C37	Introduction to CRs for COMPACT Cell Selection Part 1		SMG2 EDGE WS#11	Noted.	
	Presented for information	C38	CR GSM 02.11: COMPACT Cell Selection Part 1 	02.11	SMG2 EDGE WS#11	Noted.	
	Presented for information	C39	CR GSM 03.22: COMPACT Cell Selection Part 1	03.22	SMG2 EDGE WS#11	•	The PLMN selection changes in this CR are SMG3 WPA responsibility. 
•	SMG2 are proposing changes which are unacceptable as they put mandatory requirements on e.g. GSM 900 mobiles which do not support the optional EDGE classic or compact mode.
•	The note in 4.9 is wrong, it does not take dedicated SDCCH sysinfo into account. The note should be about broadcast sysinfo.	
	Presented for information	C40	CR GSM 05.08: COMPACT Cell Selection Part 1	05.08	SMG2 EDGE WS#11	Noted.	
	Presented for information	C41	CR GSM 11.11: COMPACT Cell Selection Part 1	11.11	UWCC	Noted.	
	Presented for information	C42	CR GSM 24.008: COMPACT Cell Selection Part 1	24.008	SMG2 EDGE WS#11	•	The section SMG2 are changing in this CR is TSGN1 responsibility.
•	UMTS PLMN selection is not covered at all. This is not just a GSM specification.	
	Presented for information	C43	Introduction to CRs for COMPACT Cell Selection Part 2		SMG2 EDGE WS#11	Noted.	
	Presented for information	C44	CR GSM 02.11: COMPACT Cell Selection Part 2 	02.11	SMG2 EDGE WS#11	Noted.	
	Presented for information	C45	CR GSM 03.22: COMPACT Cell Selection Part 2	03.22	SMG2 EDGE WS#11	•	The section that has been defined should be SMG3 WPA responsibility.	
	Presented for information	C46	CR GSM 11.11: COMPACT Cell Selection Part 2	11.11	UWCC	Noted.	

							
6.8	Security						
		C29	2G/3G security interoperability	24.008	Vodafone	Noted,
the originator invites comments.
(Tdoc number for revision to D16 was allocated but not used)	
		D10	Clarification of the Authentication enhancements		NTT Software	Noted.
NTT comments to Tdoc C29.	
		D16	2G/3G security interoperability	24.008	Vodafone	Not available
Was allocated to revise C29.	

6.9	CC related Items						
		B95	Proposal of UMTS Bearer Capability	24.008	Nippon Telecommunications Consulting 	Revised to C98.	
		C01	Transaction Identifier Extension	24.007	Fujitsu	Revised to C89.
carried over from TSGN1 #7, doc. From N1-99981
Linked with C02	
		C02	Extended Transaction Identifier Reject	24.008	Fujitsu	Revised to C90.
carried over from TSGN1 #7, doc. From N1-99979
Linked with C01	
		C18	Mapping of UMTS Bearer Capability IE into UMTS QoS RAB parameters for UMTS speech service		Ericsson	Noted.	
		C24	Clarification of DTMF Message Sequencing	23.014	Vodafone	Agreed.
WI to be changed to TEI
Linked with C88	
		C25	Clarification of DTMF Message Sequencing	24.008	Vodafone	Revised to C88	
		C88	Clarification of DTMF Message Sequencing	24.008	Vodafone	Revised to C91
Revision of C25
Linked with C24	
		C89	Transaction Identifier Extension	24.007	Fujitsu	Agreed.
Revision of C01.	
		C90	Extended Transaction Identifier Reject	24.008	Fujitsu	Revised to D28.
carried over from TSGN1 #7, doc. From N1-99979
Linked with C01
Revision of C02.	
		C91	Clarification of DTMF Message Sequencing	24.008	Vodafone	Agreed.
WI TEI.
Revision of C88.	
		C98	Proposal of UMTS Bearer Capability	24.008	Nippon Telecommunications Consulting 	agreed.
Revision of B95.	
		D01	Brief report of S1 and N3 meeting for Bearer Modification without pre-notification		NEC	Noted.
•	It was clarified that this is not a proposal to introduce the old GSM "followed by" or "alternate" teleservices but to analyse which combinations of teleservices would be good candidates for ICM without prenotification.
•	The discussion is still between S1 and N3. The contribution is for the information to N1.	
		D28	Extended Transaction Identifier Reject	24.008	Fujitsu	Agreed.
Linked with C01
Revision of C90	
6.10	Out-of-Band Transcoder Control						
		D32	Analysis of Impact on TS24.008 by Out Band Transcoder Control	24.008	NTT DoCoMo	Noted.
Proposed LS in D33.	

6.11	QoS						
		B89	Extension of Maximum N-PDU size (Max SDU size)		NTT DoCoMo	Noted. Could not be agreed as working assumption. More time to compare the alternatives is needed.
Some delegations had concerns about the following points:
-	Backwards compatibility is difficult to analyse as the negotiation procedure was not presented in detail.
-	The proposal seems to apply to UMTS single mode networks only as the GSM limitation can not be removed even from R99
-	Is the increased packet size intended for PS only or should it apply to CS also?
-	What is the current max. limit at RLC? Is the intention to increase this limit?	
		B96	Coding for QoS Parameters	24.008	NTT DoCoMo, NEC,
NTT Software	Noted. Could not be agreed as working assumption. More time to compare the alternatives is needed.
Proposal to replace the existing QoS with one that maps 1:1 to UTRAN RAB parameters. This would make GSM and UMTS QoS completely different. S2-R3-N1 will have to solve this question very urgently in order to get QoS as part of the R99.
B97 proposes to delete all of the existing SM QoS IE contents and to replace that with a new UTRAN related reflection of RAB.
Where is the mapping between RAB – BC and RAB – QoS defined? In which specification? For CS in 27.001

Linked CR in B97.	
		B97	Quality of Service modification	24.008	NTT DoCoMo, NTT Software	Rejected.
Linked with discussion paper in B96.	
		C72	MS and GSN-initiated PDP context modification	24.008	Ericsson	Revised to C74	
		C74	MS and GSN-initiated PDP context modification	24.008	Ericsson	Revised to D22
The principle was supported but this revision of the CR could not yet be agreed.
Revision of C72.	
		D22	MS and GSN-initiated PDP context modification	24.008	Ericsson	The CR was agreed in principle but for practical reasons the contents is to be merged with other SM related CRs in the GSM-UMTS ad-hoc meeting.
Revision of C74	

							
6.12	Other R99 Issues						
		B91	MS Classmark 3 Clarification	24.008	Nokia	Agreed. 
Additionally an LS asking SMG2 WPA to endorse the CR too is needed.
GSM 400	
		B92	Proposed 3rd Generation NAS information 	24.008	Nippon Telecommunications Consulting 	Noted.

Linked with B93	
		B93	Proposed 3rd Generation NAS information	24.008	Nippon Telecommunications Consulting 	Revised to D09

Linked with B92	
		C00	New TP-PID value for delivery of ANSI-136 short messages	23.040	UWCC	Noted.
Presented for information. 
The document has already been agreed by T1 who are the main responsible group. 
11.14 is not TSGN responsibility. 23.040 T1 main and N1 2nd responsibility.	
		C03	Realisation of Paging Response in MM	24.008	Fujitsu	The meeting decided to address the question by moving the existing RR PAGING RESPONSE message from 04.18 to 24.008. This means adopting the current GSM paging procedure as such, including the RR PD of the PAGING RESPONSE message. As the messge is significant to both radio access network and CN, not having it as part of UMTS specification is not acceptable.
24.008 and 04.18 CRs to be drafted and liaised to SMG2 WPA for them to endorse this change on specification under joint responsibility.	
		C04	Paging Response as a MM message	24.008	Fujitsu	Rejected.
Revised from N1-99978	
		C55	Proposed Using MM sublayer for 3G PS-SMS transfer	24.007
24.011		Noted.
Proposal to handle R99 UMTS SMS messages via MM layer. No change in R99 GSM needed as the LLC is still there.
This working assumption was agreed and it means that 23.121 needs to be changed to the same thinking.
Comments on the CRs are still invited.	
		C56	Using MM sublayer for 3G PS-SMS message transfer	24.007		Revised to D19.	
		C57	Using MM sublayer for 3G PS-SMS message transfer	24.011		Revised to D20.	
		C71	SIM application Toolkit (SAT) service description	22.038	S1	Noted.
The latest spec provided for information to quide the N1 part of SAT / MExE transaction traceability work.	
		D09	Proposed 3rd Generation NAS information	24.008	Nippon Telecommunications Consulting 	Revision of B93

Linked with B92	
		D19	Using MM sublayer for 3G PS-SMS message transfer	24.007		For information and comments.
Revision of C56.	
		D20	Using MM sublayer for 3G PS-SMS message transfer	24.011		For information and commnets,
Revision of C57.	
		D36	Paging response in UMTS 	24.008	Fujitsu	Revised to D41	
		D41	Paging response in UMTS	24.008	Fujitsu	Agreed.
Revision of D36	
7	Output Liaison Statements						
		B98	Proposed LS on Coding for QoS Parameters		NTT DoCoMo NTT Software/	Withdrawn.
Response to B75	
		C11	Proposed Liaison back to R3 on Security mode control procedure	24.008	Fujitsu	Revised to D06.
Reply to B69.	
		C80	Active Location Retrieval in CAMEL Phase 3		Richard's LS	Agreed.
Reply to B61.	
		C81	Common Identification for Relocation Co-ordination		Duncan's LS	Agreed.
Reply to B68.	
		C82	5 or 6 digits IMSI HPLMN		Hannu's LS	Agreed.
Reply to B83.	
		C83	Current status on UE idle mode opearation		Monica/Arnaud	Revised to D27
Reply to C78.	
		C92	LS on LCS to T1P1		Sonia's LS	Agreed.
Reply to C12.	
		C93	N1 Open questions on QoS		QoS drafting group	Agreed.
Initiated from N1	
		D06	Proposed Liaison back to R3 on Security mode control procedure	24.008	Fujitsu	Agreed.
Revision of C11.
Reply to B61	
		D07	LS on MS CM 3 clarification		Hannu	Agreed.
Asking SMG2 WPA to endorse the 24.008 CR 034 in Tdoc N1-99B91.
Tdoc N1-99B91 to be attached.	
		D18	LS out for paging???????		Fujitsu	Revised to D42	
		D23	LS on DRX CR		Monica	Agreed.
Agreed CR D24 to be attached.	
		D27	Current status on UE idle mode opearation		Monica/Arnaud	Agreed.
Reply to C78.
Revision of C83	
		D29	LS on Service/Baseline Implementation Capabilities		Kanno san	Rejected.
N1 can not assume the responsibility of Service / Baseline capabilities. This is TSGT issue, but TSGN WGs are willing to assist in their area of expertise. But T2 must the the owner of the document.
Response to B58.	
		D33	Liaison statement of Impact to TS24.008 by Out Band Transcoder Control		NTT DoCoMo	Revised to D40.

Related with D32.	
		D38	Response to Liaison Statement on Issues with Multiple PDP Contexts		Monica	Agreed.	
		D40	Liaison statement of Impact to TS24.008 by Out Band Transcoder Control		NTT DoCoMo	Agreed.

Revision of D33	
		D42	LS out for paging		Fujitsu	Agreed
Revision of D18	
							
8	A.O.B.						
		D17	Memory of N1#8 Kobe meeting		Yahagi san	For information	
			Thanks, Sayonara!