Proposed work order:
(to be reviewed on Monday)	
Monday	1.	Opening	
	2.	Approval of the agenda	
	3.	Input LS	
	4.9	Indication of the optional and conditional items	
	4.7	Service continuity between 2G and 3G	
	4.12	Ciphering	
	4.13	Ciphering of initial MM message	
			
Tuesday	4.8	Basic call handling changes	
	4.2	2G MM / GMM evolution to 3G	
			
Wednesday	4.2	2G MM / GMM evolution to 3G continues	
	4.5	MS CM changes	
	4.3	Impact of LLC removal on SMS	
	4.4	Impact of LLC removal on SMS	
	5 	Work Plan for TSGN WG1 for 1999	

			

Documents for TSGN1 Ad-hoc meeting	Yellow cells indicate an allocated but not available Tdoc	
Agenda item	Agenda item title	Tdoc IW-99 	Title	Spec.	Source	Result	
1	Opening					22.11.1999 at 9:30 (estimate)	
2	Approval of agenda; document allocation	006	Agenda		Chairman	Noted. This file is a.k.a. Oulu9911.rtf	

							

3	Input Liaison statements						
		001	Principles for secure GSM-UMTS interoperation		TSG-S2	FYI: Principles for secure GSM-UMTS interoperation
Noted.	
		002	Liaison statement on Basic principles of QoS interoperations		TSG S2	FYI: QoS Principles.
1.	S2 agreed that QoS profiles and attributes of GPRS R99 are the same as those of UMTS R99, which is specified in TS 23.107 version 3.0.0 “QoS concept and architecture”(attached as S2-99A19). Also, the relevant CR to 23.060 was approved. (See the attached file: S2-99B72).
2.	S2 is working on the basic principles for the interworking between UMTS/GPRS R99 QoS profile and GPRS pre-R99 QoS profile. The results will be sent out as soon as they are available.
3.	S2 is currently discussing the detailed QoS mapping between GPRS/UMTS R99 and GPRS pre-R99. The results will be sent out as soon as they available.
Noted.	
		003	LS on Inter System Handover for the PS domain	23.060	SA2	FYI: Inter system HO
Changes which introduce the separation in Intra and Inter SGSN Inter System handover where the
•	Intra SGSN handover covers Cell changes and RA updates within a combined 2G+3G-SGSN node and the 
•	Inter SGSN handover covers Inter SGSN RA updates
Conversion of RLC Sequence Numbers to SNDCP N-PDU sequence numbers and vice versa: SA2 kindly asks to investigate arising roll over problems when comparing the derived numbers.
Noted.	
		004	LS on CBC-RNC Protocol Responsibility 		SA2	Protocol responsibilities for CBS, not relevant for the ad-hoc?
Noted.	
		010	liaison on support of QoS negotiation and handover notification		RAN2	FYI: QoS negotiation and handover notification to MExE. Not relevant for the ad-hoc?
Noted.	
		011	LS on UMTS PLMN selection (response to N1-99C78)		RAN2	PLMN selection for R99, RAN 2 propose either revising 23.022 or drafting a new specification. Not relevant to ad-hoc?
Noted.	
		017	Reply to Liaison on “N1 Open Questions on QoS		RAN2	FYI: RAN2 say that inter-working of QoS between GPRS and UMTS is the work item of other groups. In addition RAN-WG2 believes that mapping of RAB QoS onto Radio Bearer should not be specified.
Noted.	

4	GSM-UMTS related issues						
4.1	Impact of LLC removal on GMM 
New service primitives in MM/RAN IF			24.007			

4.2	2G MM / GMM evolution to 3G
New functional requirements on MM + GMM to make it MM + GMM + PMM			24.008
29.018		Decisions on the terminology:
•	A vocabulary will be defined
•	All CRs must be written to comply with the vocabulary
•	Additionally the unchanged sections outside the "technical" CRs will be aligned with the vocabulary by the delegations as follows:
•	Ericsson: GMM
•	Siemens: SM
•	Nokia: MM
•	Ericsson: CC
•	PS = common GSM-GPRS and UMTS-PS
•	GPRS = GSM packet data only
•	UMTS-PS = UMTS packet data only
•	PS MS must be defined. Where is GPRS MS defined.
•	(GSM only), (GPRS only), (UMTS only), (UMTS-PS only)
•	CKSN or Key Set Identifier: it was decided to keep the CKSN.	
	6.	014	Introduction of Follow-on mechanism for PS	24.008	Fujitsu/ Fumihiko Yokota	•	Impact of the change on the cover page!
•	Is the whole procedure necessary? At least it is not needed in GPRS.	
	2.	015	GMM State Model for UMTS	24.008	Fujitsu/ Fumihiko Yokota	This CR implements the principles of 018.
•	The terminology with PS, GSM-GPRS and UMTS-PS should be extended to the whole GMM section
•	Stage 1 or stage 2 CR is needed to define the PS MS.
•	Is it too late to change the name of 23.060.
•	Proposed new state GMM-SERVICE-REQUEST-INITIATED still needs to be studied to see if substates are needed.
•	The criteria whether to send additional SERVICE REQUEST for the subsequent connections must be clarified.
•	GMM-REGISTERED.NOT-CONNECTED state is not needed but the same functionality will be achieved by agreeing 021 instead.
Linked with 018, 021	
	2.	018	Principle for UMTS adaptation to GMM		NTT DoCoMo/ Takashi Koshimizu	•	After the removal of LLC, establishment of signaling link is needed before sending /receiving some signaling at the stage after Attach.
•	“Iu Release” triggers the states transition of “PMM-Connected to PMM-IDLE “ since Ready Timer is not defineded for UMTS.
•	Addition of SRNS relocation procedure
•	UMTS-GPRS Intersystem handover
Linked with 015, 021	
	4..	020	READY Timer not applicable for UMTS	24.008	Ericsson/ Monica	•	Principle agreed but additionally the treatment for the "empty value" for UMTS must be defined with the message description CRs.	
	2.	021	PMM-IDLE mode and PMM-CONNECTED mode for UMTS	24.008	Ericsson/ Monica	•	Reachable timer conditions should be considered as well, this is covered in 023.
•	signalling connection needs to be defined
•	Precise trigger events for state transitions need to be defined.
Linked with 015, 018, 022.	
	3.	022	Periodic RA Update Timer function and Mobile Reachable Timer function for UMTS and clarification that the substate SUSPENDED is applicable for GSM only	24.008	Ericsson/ Monica	•	No problem with the basic principle but the state transition conditions (events) need to be defined more precisely in 021

Linked with 021	
	7.	023	P-TMSI reallocation procedure	24.008	Ericsson/ Monica	•	SERVICE REQUEST collision with P-TMSI reallocation needs to be clarified.
•	Section f) is unnecessary and needs to be removed?
•	SERVICE REQUEST must not contain P-TMSI reallocation.	
	8.	024	Detach procedure	24.008	Ericsson/ Monica	•	The priniciple of adding P-TMSI and P-TMSI Signature to DETACH REQUEST agreed.
•	The PDU encoding to be clarified.
•	The GMM part in case of lower layer failure is defined in abnormal procedures. It should be checked whether release of the radio resources is well covered in the other specification. 
•	Addition of P-TMSI and P-TMSI signature need to be made mandatory for all R99 implementation. However, the IE can not be "M" as this would trigger the error handling in a R99 SGSN serving an old GPRS mobile.
Linked with 026, 027, 032.	
	9.	025	UMTS <--> GPRS Intersystem change (handover)	24.008	Ericsson/ Monica	•	Selective RA update concept introduced. Is it necessary to inform the CN about the change of the system?
•	SA2 to decide on the Stage 2 first.
Linked with 038.	
	5.	026	Change of network mode of operation	24.008	Ericsson/ Monica	See 024, 032
Linked with 024, 027, 032	
	5.	027	MS modes of operation in UMTS	24.008	Ericsson/ Monica	See 024, 032
Linked with 024, 026, 032	
		028	Correction of the LAI stored in the forbidden location area list	24.008	Ericsson/ Monica	Withdrawn	
	5.	032	UMTS adaptation to section 4.7.1	24.008	NTT Comware/ Nobuyuki Uda	Revised to 059.
•	The priniciple of adding P-TMSI and P-TMSI Signature to DETACH REQUEST agreed.
•	The PDU encoding to be clarified.
•	The beginning of this CR with 024, 026 and 027 needs to be provided to the TSGN1 #9.
•	The applicability of section 4.7.1.2 to UMTS –PS and GPRS needs to be clarified.
•	4.7.1.3. P-TMSI Signature deletion must be clarified.
Linked with 024, 026, 027	
	10.	033	UMTS adaptation to paging procedure	24.008	NTT Comware/ Nobuyuki Uda	•	The vocabulary to be aligned with 058.
•	CKSN versus Key Set Identifier decision impacts this CR too.	
	11.	037	Attach procedure for R99	24.008	Nokia	•	RA change criteria for MS needs to be defined for UM TS case.
•	Aborting RR procedure needs to be checked whether it has been defined.
•	The vocabulary to be aligned with 058.
•	CKSN versus Key Set Identifier decision impacts this CR too.	
	9.	038	RAU procedure for R99	24.008	Nokia	•	This proposal is according to the current working assumption defined in 23.060 by S2. 
•	Similarily to 025 the section 4.7.5.1 is subject to the S2 decision.
•	CKSN or Key Set Identifier?
•	The vocabulary to be aligned with 058.
Linked with 025.	
	10.	039	Paging procedure for R99 	24.008	Nokia	•	There is another CR from NTT on the same section -> CRs to be merged.	
	12.	040	GMM procedures	24.008	Nokia	•	Yes, but make it MM specific procedure
•	RR connection can not be used on the PS side.	
	13.	041	Alignment of chapters 4.3 – 4.6 for R99	24.008	Nokia	•	The vocabulary to be aligned with 058.
•	ciphering mode setting vs. security mode setting procedure. One is used in GSM the other in UMTS  -> use both with the right references.	
	14.	042	Attach, RAU, CM service request CM re-establishment request and LU messages for R99	24.008	Nokia	•	CKSN or Key Set Identifier: it was decided to keep the CKSN.
•	The vocabulary to be aligned with 058.
•	Text needs to be added to define the usage of the optional IEs in the PDUs.
•	MS identity presence? It must be there for UMTS but can not be made mandatory for compatibility reasons.
•	Is MS network capability needed at all now?
•	GPRS frame length to be checked, do the additional IEs mean the PDU will be segmented.
•	The coding of DRX parameters IE for UMTS needs to be defined.	
	1.	046	RR connection vocabulary	24.008	Ericsson	•	Could not be agreed yet, problem with RR connection having been defined already in RAN area.	

							
4.3	Impact of LLC removal on SMS
New service primitives in SMS/MM IF			24.007			
		029	Proposed Using MM sublayer for 3G PS-SMS transfer 	24.007 24.011	NTT Comware/ Nobuyuki Uda	•	There is sufficient information available in the lower layers to distinguish between CS and PS messages. -> proposal to add a new PD to distinguish between CS-SMS and PS-SMS was not supported by the meeting.
•	The originator  propose alternative 2 (connection establishment before data sending) but alternative 1 (just sending data messages) was preferred.
•	SERVICE REQUEST for some UMTS cases  should be brought into the CRs.	
		030	Using MM sublayer for PS-SMS message transfer	24.007	NTT Comware/ Nobuyuki Uda	Revised to 052.

Linked with 051.	
		052	Using MM sublayer for PS-SMS message transfer	24.007	NTT Comware/ Nobuyuki Uda	•	Section 11 of the CR is based on the assumption that a new PD will be used. That part of the CR can not be discussed with no decision made on this issue.
•	Question on whether it is right to copy the structure of the CS primitives to PS SMS. The messages intended for connection establishment
Linked with 051.
Revision of 030.	

4.4	Impact of LLC removal on SMS
Functional requirements on the SMS and MM protocols.			24.008
24.011
23.121			
		009	Addition of P-TMSI & P-TMSI signature to GPRS attach message	24.008	Vodafone/ Duncan Mills	Withdrawn.	
		031	Using MM sublayer for PS-SMS message transfer	24.011	NTT Comware/ Nobuyuki Uda	Revised to 053.	
		053	Using MM sublayer for PS-SMS message transfer	24.011	NTT Comware/ Nobuyuki Uda	•	The principle of keeping the existing text but identifying the common items, UMTS items and GSM items was proposed rather than block copying lots of similar paragraphs for GSM and UMTS case.
•	Vocabulary needs to be aligned with 058.

Revision of 031.	

							
4.5	MS CM changes			24.008			
		012	Addition of MS Classmark 2 in Location Updating Request	24.008	Fujitsu/ Fumihiko Yokota	Withdrawn	
		016	TR 23.814 v.0.5.1	24.008	Fujitsu/ Fumihiko Yokota	Noted.	
		049	Ciphering, MS network capability and UMTS – GPRS handover	24.008	Alcatel	Noted.	
							
4.6	Stage 2
Packet stage 2 is in 23.121 and 23.060.
Do we want to have some arrow diagrams in CS stage 2 also?			23.121
23.060

23.009			

							
							
4.7	Service continuity between 2G and 3G			24.008
what else ???			
		034	Interoperability of QoS parameters	23.107	NTT Comware/ Nobuyuki Uda	Noted.	
		035	QoS Enhancements	24.008	NTT Software/ Takeshi Igarashi	Noted.	
		036	QoS coding for R97 and R99	24.008	Nokia	•	The complete QoS contents must always be sent
•	One QoS IE was preferred instead of keeping the existing QoS and adding UMTS QoS for R99.
•	coding rules must also be added to indicate that the encoder shall always encode both old and new QoS part but the receiver may only use the part it understands.
•	The originator to provide a CR to TSGN1 #9 to cover this QoS change.
•	Jaakko and Koshimizu san to provide a joint contribution for this meeting to review later
Revised to 048.	
		048	QoS coding for R97 and R99	24.008	NTT DoCoMo, Nokia	Withdrawn. 
Take 036 instead.
Revision of 036.	
							
4.8	Basic call handling changes			
23.003
23.009			
		019	Proposal for updates to 23.009	23.009	Ericsson/ Zdravko	•	Cover page: just one category, and the CR revision number must be increased for each published revision.
•	Quite substantial changes, how to review these online during a meeting? Some questions were asked to understand the proposal. 
•	Comments on the proposal are invited so that the originator can finalise the proposal as soon as possible.
•	Fig. 20 in section 8.1.3.1 is confusing and difficult to understand.	

							
4.9	Indication of the optional and conditional items
There should be textual or other indication if a definition is limited to GSM only or UMTS only. This approach has already been taken by S2 in 23.060.			23.022
23.034 24.007 24.008 
27.001
etc.		•	The terminology changes we decided upon should be added as tasks to the GSM-UMTS interworking task list.
	
		005	Updating Session Management (SM) for R99	24.008	Nokia / Mohan Sivanandan	The previous version was seen in TSGN1 #8 in Kobe. Several changes have been made  since then according to the feedback that has been received.
TERMINOLOGY:
•	Indicating conditional items like "In GPRS...", "In UMTS..." and "In GSM..." was agreed. This terminology needs to be added to the vocabulary of the 24.008.
•	Multimode mobile was assumed to mean one which can access both GSM and UTRAN cells. This can not be defined in 24.008 terminology but a global definition is needed.
•	The term MS was assumed to cover both GSM MS and UMTS UE. The term needs to be added to 24.008 vocabulary.
•	The necessity of NSAPI in the SM messages related with the secondary PDP context was questioned by Siemens. 
•	23.060 CR drafted by Siemens. The delegations are requested to check whether they could agree with this counter proposal.
•	QoS evolution should contain the old QoS octets plus the new R99 octets added at the end of the same IE. The new part must be included by a R99 implementation but the old part must also contain valid values.
•	Modify PDP context and Modify PDP context accept messages should be applicable to both directions. Additionally a downlink PDP context modify reject should be defined.
•	No similar reject mechanism is needed for PDP context deactivation.
•	Optional format V IEs at the end of messages will not work. 
•	PDP address in 9.5.9 can not be conditional but it should be made optional.
•	To be issued to TSGN1 #9 with these changes by the originator.
Revised to 047.	
		043	Parallel handling of multiple user application flows	24.008	Ericsson	Revised to 057.
•	This CR would require SM to support CSN.1 coding. The traditional table format was preferred.
•	Definition for unused (Spare?) code points needs to be added.	
		044	Secondary PDP context in 24.008	24.008	Siemens	Withdrawn	
		045	Secondary PDP context in 23.060	23.060	Siemens	Withdrawn	
		047	Updating Session Management (SM) for R99	24.008	Nokia / Mohan Sivanandan	Revised to 056.

Revision of 005.	
		051	Resource reservation for ActivePDP context	24.008	NTT Commware	•	What should happen when e.g. a new cell can not offer all the resources that would be required for simultanous PDP contexts with different QoS? -> the network should perform a PDP context modification and if that is not possible (when the requested minimum QoS can not be supported) then the PDP context should be deactivated.
Linked with 052.	
		054	Usage of TI in secondary PDP context activation procedure	23.060	Siemens	Noted.
	
		055	Proposed LS to S2 on Usage of TI in secondary PDP context activation procedure 		Siemens	Not available	
	2.	056	Updating SM for R99	24.008	Siemens, Nokia, Ericsson, NTT DoCoMo	•	The applicability of TFT on any PDP context or just secondary context needs to be clarified.
•	The vocabulary defined in Tdoc 058 must be taken into account for the next revision.
•	The handling of PDP context modification reject to be clarified, what responses (QoS's) are allowed for the network.
•	IEIs for the optional IEs need to be added.
•	The relation of primary and secondary PDP context need to be defined.

Revision of 047.	
		057	Parallel handling of multiple user application flows	24.008	Ericsson	
Revision of 043.	
	1.	058	24.008 Vocabulary 	24.008	Ericsson, Siemens, Nokia	•	All CRs to the TSGN1 #9 must be aligned with this terminology.
•	The usage of GPRS for GSM PS and UMTS-PS is confusing but changing it completely is a big task. GPRS is already defined as  General PS. According to stage 2 it is not GSM related but general. 
•	The description of (GSM only) and In GSM,... should be aligned. Similarily (UMTS only) and In UMTS,...
•	Hannu to take this CR to the TSGN1 #9.	
		059	UMTS adaptation to section 4.7.1	24.008	NTT Comware/ Nobuyuki Uda	

Revision of 032.	
		060	P-TMSI signature in SERVICE ACCEPT	24.008	NTT Comware/
Nobuyuki Uda		

4.10	Suspend / Resume procedures
the procedures are needed for GSM R99. Are they needed for UMTS too or do they become conditional?			23.060
24.008			

							
							
4.11	Paging as CN message
GPRS GMM expects an indication of incoming paging to request for PAGING RESPONSE sending. The same principle will apply to UTRAN but are the service primitives the same?			23.060 24.008			

							
							
4.12	Ciphering
Indication of Ciphering key and algorithm(s) to mobile.			(23.108) 23.060 24.008			
		008	Adaption of MM/GMM messages to incorporate UMTS security parameters	24.008	Vodafone/ Duncan Mills	Revised to 050.
•	RR connection versus signalling connection between the MS and the Core Network? -> define the term "RR connection" for GSM and UMTS separately.
•	USIM versus SIM? -> the decision was made to use SIM all over 24.008. Statement that SIM may be considered to be one that supports also the UMTS specific procedures and parameters such as longer authentication parameteres.
•	The MS behaviour after diagnosing network authentication error should be specified.
•	Ciphering Key Sequence Number renaming is a problem, why not leave it as it is.	
		050	Adaption of MM/GMM messages to incorporate UMTS security parameters	24.008	Vodafone/ Duncan Mills	

Revision of 008	

4.13	Ciphering of initial MM message
No LLC -> no algorithm -> no ciphering for the initial PS GMM message.
S2 decision to add new message.			23.060 24.008			
		013	Service Request	24.008	Fujitsu/ Fumihiko Yokota	•	GMM-REGISTERED.SERVICE-REQUEST-NEEDED
•	Is reattempt mechanism needed for the failure case? -> No reattempts at this level as we could see several cases where upper layer has repetitions and nobody could convince us that there would be a case where the reattempt would be useful.
•	The cases when the SERVICE REQUEST shall be sent must be made clear. The intention is that no SERVICE REQUEST is sent when a ciphered connection already exists.
•	4.7.x "for last two cases..." must be reworded.
•	How to distinguish between different simultaneous bearers for the same terminal?
•	The criteria for using the service request procedure should be clarified in the CR text to match what has been said on the cover page.
•	Optional IEs need a description for the condition when they must be included.	

							
4.14	Different subscriber identities
			23.060?
24.008		COMPLETE

IMSI will apply to both 2G and 3G,
no N1 action needed.
(S2-99633)	
							
4.15	New User Plane protocols, PDCP, BMC
TSGR#6 recently agreed on the introduction of PDCP and BMC.			24.007 24.008		COMPLETE

The interface was removed after the decision to include PDCP in RAN.	

							
							
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 22.-26.5.2000 (U.S./T1P1)
Please note that meeting #12 has been moved by one week 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 (Lucent)
TSGN#10 11.-13.12.2000	
		007	GSM-UMTS Interworking project plan		Chairman	Noted.	

6	A.O.B.