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.11.1999 at 9:30 (estimate)	
2	Approval of agenda; document allocation	B40	Agenda		N1 Chairman	Noted. This file is a.k.a. Kobe9910.rtf	
		B42	TSGN Plenary #5 meeting report		MCC		
		B43	TSGS #5 Highlights		MCC		

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	
S1 answer our question on SAT transaction traceability. We can now do our part in N1.	
		B50	DRX Parameter IE in 24.008		SMG2 WPA	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 	Noted. 
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	Discussion.
Reply needed?	
		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	Discussion
Reply needed?	
		B57	L3 segmentation		SMG2 WPA	Withdrawn.
Copy of B53.	
		B58	LS on Service/Baseline Implementation Capabilities		SS Ad-hoc	Noted.
SS Ad-hoc comments to T2 on terminal capabilities.	
		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 needed?	
		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	
Reply needed.	
		B69	Security mode control procedure		TSG-R3	
Reply needed.	
		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	Discussion
Response needed?
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	
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	
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	
Reply needed.
T2 are asking for the right criteria to use either 5 or 6 digits MNC from SIM card. 03.22 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?	
		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?	
							
4	Maintenance of R98 and older releases						
4.1	Corrections						

							
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.	
		C31	Summary of 'agreed' Change Requests to GSM 04.08 SM/GMM		Rapporteur		
	03.60 / 23.060						

	04.07/ 24.007						

	04.08 / 24.008						

	04.64						

	04.65 / 24.065						

	09.18 / 29.018						

							

4.3	Other Pre-99 WIs						
	LCS	C12	T1P1.5 LCS work plan		T1P1.5		

							
5 	Work Plan for TSGN WG1 for 1999					TSGN1 #8   25.-29.11.1999 (Japan/DoCoMo)
TSGN1 #9   11.-14.1.2000 (Germany/Siemens)
TSGN #6 13.-15.12.1999 (  )
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

		B46	Specifications within TSG-N		TSG-N Chairman	
Should this be posted on a visible place on the website?	
		B47	Work Item list		MCC	
Should this be posted on a visible place on the website?	

							
6	Release 99						
6.1	Multicall						

							
6.2	Multimedia call						

							
6.3	GSM / UMTS interworking						
		C36	Project Plan for GSM/UMTS interworking and MM in UMTS		Chairman		

6.4	MS Classmark						

							
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						

							
6.7	EDGE						

							
6.8	Security						

							
6.9	CC related Items						

							
6.10	Out-of-Band Transcoder Control						

							
6.11	QoS						

							
6.12	Other R99 Issues						

							
7	Output Liaison Statements						

							

							
8	A.O.B.