Five documents were left for email approval: N1-99B35 and N1-99B36 N1-99942, N1-99943, N1-99944.
Email approval procedure: Any objection against the proposed CRs must be emailed to the chairman (hannu.hietalahti@nokia.com) by 24.September 1999 12:00 French time. If no objections are made then the documents are automatically considered approved.

The outcome of Email approval procedure 24.9.1999: Tdocs N1-99942, 943, 944, N1-99B35 and B36 are all rejected. The question of the MCC 302 must be solved and CRs should be prepared for the TSGN Plenary #5.

Some of the documents had to be postponed and these will need to be given sufficient priority in the next meeting to have them treated then.

Documents for TSGN1 meeting #7, 13.-17.September 1999, Makuhari, 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					13.9.1999 at 9:30	
2	Approval of agenda; document allocation	910	Agenda		N1 Chairman	Noted.	
		911	Approved Agenda		N1 Chairman	not available	
		912	Handover and SRNS relocation meeting report (23.8.99, Sophia Antipolis)		MCC		
		913	Allocation of Tdocs to agenda items		N1 Chairman	Noted. This file is a.k.a. Makuhari9909.rtf	
							
3	Input Liaison statements				

Ton of bricks ->	What is happening to LSs nowadays? 
We spotted 3 missing LSs (at least from S2) during this meeting? At least one of them did cover an issue we discussed in the meeting with no chance of reaching a decision with no knowledge of an already existing architecture decision!!!!!!!!!!!!!!!!!!!!!!!!!
(N1-99B31)	
		917	Response liaison on Clarification of RAB Sub Flows concept and associated definitions		3GPP RAN WG3 	Noted.	
		918	Definitions for usage of Multi-mode/system terminals		3GPP TSG T2 SWG5	Noted.	
		A29	LS on addition of APN Parameter in NW-requested PDP context activation procedure.			Answer in Tdoc A74. 
Related 24.008 CR in 922.	
		A31	Liaison Statement - Cover letter for TR21.904, Terminal Capabilities Report, interim version
TR21.904 			Answer in A75.	
		A58	Liaison statement from T1P1.5 on location services		T1P1.5		
		A64	LS on CBS Functionality and Responsobility		TSG T WG2	Answer in A88.	
		A65	LS about Signalling		TSG T WG2	Answer in A89	
		A66	Proposal LS on QoS paramaters		TSG T WG2	Noted.	
		A67	LS Cover letter for TR21.904, Terminal Capabilities Report, interim version		TSG T WG2
SWG's	Noted.
The same as A73	
		A68	Liaison Statement on addition of APN parameter in Network-requested PDP context activation procedure		TSG S WG2	Noted. This is the same document as in A29.	
		A69	LS on Location Area concept		TSG S WG2	Answer in Tdoc A90.
•	Backwards compatibility to old mobiles must be achieved.
•	Comment that the changes to R97 and R98 should be minimised when designing the backwards compatibility.
•	The changes on R99 GSM would be minimised if we choose alternative 1.
•	Choosing one of the 3 alternatives is not right as that would mean choosing whether there is Gs IF or not. We do not want to decide upon this.
•	The requirements in 23.121 will mean rewriting the MM almost completely. Why do the ULA and URA need to be completely independent?
•	From N1 viewpoint it looks that either we fulfill the current requirement in 23.121 and fail to meet the schedule for R99 by a significant margin or the requirements are adjusted to allow the principle of being able to use the existing GSM background for MM.	
		A73	LS Cover letter for TR21.904, Terminal Capabilities Report, interim version		TSG T WG2
SWG's	Noted.
The same doc as A67	
		A91	On 24.007 and 24.011 responsibility		S2	•	Chairman to contact the chairman of S2 to acknowledge the 24.007 and 24.011 responsibility
•	and to say that  we have started the work but we can not give any concrete results yet.	
		B11	Liaison statement to N1 on the revised work item description for out-of-band transcoder control		N2	Noted.
Incoming LS delivered on the last day of the meeting and reviewed very briefly. The following impact on 24.008 were noted:
•	BC negotiation
•	N3 will be involved also
•	The status of the WI and whether it is intended for R99 or R00 should be clarified.
•	The chairman to bring this up in the TSGN Plenary.	
		B12	LS to SA and N1 (CC) on required network functionality for usage of SIM in 3G mobiles		N2	Noted.	
		B24	LS on combined mobility management		N2B	Noted.
Related with S2-99947	
		B31	LS on ciphering of the first MM message		S2	Noted.
There has already been a contribution in TSGN1 #6 to this direction but it could not be agreed then. The matter should be revisited in the next TSGN1 meeting.	
							
4	Maintenance of R98 and older releases						
4.1	Corrections	914	MCC for Canada Added	23.022	7 Layers AG
	Rejected.
revisit later, call home first what to say about the R98 version -> OK, still time to change, the CR should be approved.
Cover page must indicate changes to ME and CN.
R99, linked with 915 and 916	
		915	MCC for Canada Added	03.22	7 Layers AG
	Rejected.
revisit later, call home first what to say about this.
R98, linked with 914 and 916	
		916	MCC for Canada Added	03.22	7 Layers AG	Rejected, Harmonization of PCS1900 was a R98 WI, this is not needed.
By the way, the 3-digit MNC should not appear in R97 version of 03.22 at all -> check this!
R97, linked with 914 and 915	
		B07	Connection of figure A.2 in Annex A	03.22	Ericsson	Rejected.
Difficulty with the drawing tools, paper copy gives the change drawn in the diagram.
The same as B08 for R99
R98	
		B08	Connection of figure A.2 in Annex A	23.022	Ericsson	REjected
Difficulty with the drawing tools, paper copy gives the change drawn in the diagram.
the same as B07 for R98
R99	
		B21	MCC for Canada Added	23.022	Ericsson	Revised to B35
R99	
		B22	MCC for Canada Added	03.22	Ericsson	Revised to B36
R98	
		B25	Coding Scheme in Network Name IE	04.08	Siemens	Agreed.
Clarification of the existing text. No change of implementation should be required, but the manufacturers are invited to check whether this is how they understood it before.
R96	
		B26	Coding Scheme in Network Name IE	04.08	Siemens	Agreed.
R97	
		B27	Coding Scheme in Network Name IE	04.08	Siemens	Agreed.
R98	
		B28	Coding Scheme in Network Name IE	24.008	Siemens	Agreed.
R99	
		B21	MCC for Canada Added	23.022	Ericsson	For Email approval
R99, Revision of B21 	
		B22	MCC for Canada Added	03.22	Ericsson	For Email Approval
R98, revision of B22	
		B35	MCC for Canada Added	23.022	Ericsson	Rejected
Revision of B21
R99	
		B36	MCC for Canada Added	03.22	Ericsson	Rejected
Revision of B22
R98	

							
							
4.2	GPRS					GPRS status report:
•	All 23.060 CRs will be forwarded by the secretary to S2 for endorsement as it is their spec.
•		
		919	Summary of 'agreed' Change Requests to GSM 04.08 SM/GMM	04.08	Ericsson	Noted.
Document provided for Information by the rapporteur of 04.08 GPRS part.	
		957	Summary of Change Requests to GSM 03.60 and UMTS 23.060	03.60,
23.060	Rapporteur	Noted.
	
		958	Summary of Change Requests to GSM 04.64	04.64	Rapporteur	Noted.	
		A03	Freezing Release 97		Nokia	Revised to A21.
The conditions should apply to R97 and R98 too.	
		A04	clarifications on old and new TLLIs		Alcatel	Noted.
Problem in how to understand the specification defining the allocation of a new TLLI. N1 interpretation was being sought. Our opinion is given in LS in Tdoc A23	
		A05	problem with when to restart Timer Ready		Alcatel	Withdrawn	
		A19	Network initiated Detach "IMSI detach"		Siemens	Noted.	
		A21	Freezing Release 97 and R98		N1	Revised to A25.
Revision of A03.	
		A25	Freezing of Release 97 and R98		N1	Agreed.
•	Chairman to take this Tdoc to TSGN Plenary and ask for endorsement and an LS to be sent to the other TSGs. 
•	LS to to propose this to SMG2 WPA, N2 and N3 will be sent in Tdoc A24.
•	Freezing of R98 is not clear.
•	Revision of A21.	
							
		967	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Revised to A26.
R97, linked with 968 and 969	
		968	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Revised to A27.
R98, linked with 967 and 969	
		969	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	23.060	Siemens	Revised to A28.
R99, linked with 967 and 968	
		975	Removal of BB Protocol (attached	03.60	Nortel	Revised to A70.
R97	
		A26	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Revised to A99
Revision of 967.
R97, linked with A27 and A28	
		A27	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Revised to B00
Revision of 968.
R98, linked with A26 and A28.	
		A28	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	23.060	Siemens	Revised to B01
Revision of 969.
R99, linked with A26 and A27	
		A70	Removal of BB Protocol	03.60	Nortel, Motorola	Rejected.
R97, linked with A71 and A72
Revision of 975	
		A71	Removal of BB Protocol	03.60	Nortel, Motorola	Rejected.
R98, linked with A70 and A72	
		A72	Removal of BB Protocol	23.060	Nortel, Motorola	Rejected.
R99, linked with A70 and A71	
		A99	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Agreed.
Revision of A26
R97, linked with B00 and B01	
		B00	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	03.60	Siemens	Agreed.
Revision of A27
R98, linked with A99 and B01.	
		B01	Clarification on multiplexing of several NSAPIS onto one LLC SAPI	23.060	Siemens	Agreed.
Revision of A28
R99, linked with A99 and B00	
							
		992	Addition of LL-STATUS_IND	04.07	Matsushita	Agreed.
R97, linked with 993 and 994 which were then revised to A51 and A52. (992 was not available in the beginning and it was revised once already before the first presentation)	
		993	Addition of LL-STATUS_IND	04.07	Matsushita	To be revised A51
R98, linked with 992 and 994 -> revised to A52.	
		994	Addition of LL-STATUS_IND
	24.007	Matsushita	To be revised A52
R99, linked with 992 and 993 -> revised to A51.	
		A51	Addition of LL-STATUS_IND	04.07	Matsushita	Agreed.
The CR number to be checked.
R98, linked with A52 and 992
Revision of 993.	
		A52	Addition of LL-STATUS_IND
	24.007	Matsushita	Agreed.
R99, linked with A51 and 992
Revision of 994	

		922	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Revised to B02
R98, linked with 923 and 924.	
		923	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Revised to B03
R97, linked with 922 and 924.	
		924	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Revised to B04
R99, linked with 922 and 923.	
		930	CR clash in sec. 4.7.3.2.6	04.08	Siemens	Agreed.
R97 CR, linked with 931 and 932, which were revised to A37 and A38.	
		931	CR clash in sec. 4.7.3.2.6	 04.08	Siemens	Revised to A37.
R98, linked with 930 and 932	
		932	CR clash in sec. 4.7.3.2.6	24.008	Siemens	Revised to A38
R99, linked with 930 and 931	
		933	CR clash in sec. 4.7.3.2.3.2 and 4.7.5.2.3.2	04.08	Siemens	Agreed.
Ban to take care of the note for the editor when implementing the CR.
R97, linked with 934 and 935	
		934	CR clash in sec. 4.7.3.2.3.2 and 4.7.5.2.3.2	04.08	Siemens	Agreed.
Ban to take care of the note for the editor when implementing the CR.
R98, linked with 933 and 935	
		935	CR clash in sec. 4.7.3.2.3.2 and 4.7.5.2.3.2	24.008	Siemens	Agreed.
The CR should be categorised as A = corresponds to 2G correction.
R99, linked with 933 and 934	
		936	T3212 restart after RAU reject	04.08	Siemens	Revised to A39
R97, linked with 937 and 938	
		937	T3212 restart after RAU reject	04.08	Siemens	Revised to A40.
R98, linked with 936 and 938	
		938	T3212 restart after RAU reject	24.008	Siemens	Revised to A41.
R99, linked with 936 and 937	
		939	New State GMM-REGISTERED.IMSI-DETACH-INITIATED	04.08	Siemens	Agreed.
R97, linked with 940 and 941	
		940	New State GMM-REGISTERED.IMSI-DETACH-INITIATED	04.08	Siemens	Agreed.
R98, linked with 939 and 941	
		941	New State GMM-REGISTERED.IMSI-DETACH-INITIATED	04.08	Siemens	Agreed.
R99, linked with 939 and 940	
		945	Deactivate AA PDP context request message	04.08	Siemens	Agreed.
R97, linked with 946 and 947	
		946	Deactivate AA PDP context request message	04.08	Siemens	Agreed.
R98, linked with 945 and 947	
		947	Deactivate AA PDP context request message	24.008	Siemens	Agreed.
R99, linked with 945 and 946	
		948	Coding Scheme in Network Name IE	04.08	Siemens	Revised to A61
R97, linked with 949 and 950	
		949	Coding Scheme in Network Name IE	04.08	Siemens	Revised to A62
R98, linked with 948 and 950	
		950	Coding Scheme in Network Name IE	24.008	Siemens	Revised to A63
R99, linked with 948 and 949	
		A10	GMM context and non GPRS SIMs	04.08	Alcatel	Withdrawn.
R97, linked with A11	
		A11	GMM context and non GPRS SIMs	04.08	Alcatel	Withdrawn.
R98, linked with A10	
		A37	CR clash in sec. 4.7.3.2.6	04.08	Siemens	Agreed.
Revision of 931, linked with 930, A38	
		A38	CR clash in sec. 4.7.3.2.6	 24.008	Siemens	Agreed.
Revision of 932, linked with 930, A37.	
		A39	T3212 restart after RAU reject	04.08	Siemens	Agreed.
Postponed to Friday 
Revision of 936, linked with A40, A41	
		A40	T3212 restart after RAU reject	04.08	Siemens	Agreed.
Postponed to Friday
Revision of 937, linked with A39, A41	
		A41	T3212 restart after RAU reject	24.008	Siemens	Agreed.
Postponed to Friday
Revision of 938, linked with A39, A40	
		A61	Coding Scheme in Network Name IE	04.08	Siemens 	Rejected.
The principle of making this clarification gained the support of the meeting but R96 CR should be provided as well. 
Need more time to check the MS and MSC CS and PS implementation before agreeing this.
Revision of 948	
		A62	Coding Scheme in Network Name IE	04.08	Siemens 	Rejected.
Revision of 949	
		A63	Coding Scheme in Network Name IE	24.008	Siemens 	Rejected.
Revision of 950	
		A76	Network initiated detach type “IMSI detach	04.08	Siemens	Rejected.
R97, related with A77 and A78	
		A77	Network initiated detach type “IMSI detach	04.08	Siemens	Not available.
R98, related with A76 and A78	
		A78	Network initiated detach type “IMSI detach	24.008	Siemens	Not available.
R99, related with A76 and A77	
		A85	T3212 restart after GPRS detach	04.08	Siemens	Agreed.
Postponed, wait for decision on Friday. If it can not be approved then it must be rejected.
R97, linked with A86 and A87	
		A86	T3212 restart after GPRS detach	04.08	Siemens	Agreed.
Postponed, wait for decision on Friday. If it can not be approved then it must be rejected.
R98, linked with A85 and A87	
		A87	T3212 restart after GPRS detach	24.008	Siemens	Agreed.
Postponed, wait for decision on Friday. If it can not be approved then it must be rejected.
R99, linked with A85 and A86	
		B02	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Agreed. 
No R98 or R97 is needed.
Revision of 922
R99, linked with B03 and B04	
		B03	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Agreed.
Revision of 923
linked with B02 and B04	
		B04	Addition of Access Point Name in Request PDP Context Activation
message	04.08	NTT DoCoMo	Agreed.
Revision of 924
linked with B02 and B03.	
							
		951	Clarification on the behaviour of an unused SAP	04.64	Siemens	Revised to A42
R97, linked with 952 and 953	
		952	Clarification on the behaviour of an unused SAP	04.64	Siemens	Revised to A43
R98, linked with 951 and 953	
		953	Clarification on the behaviour of an unused SAP	04.64	Siemens	Revised to A44.
R99, linked with 951 and 952	
		954	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Revised to A95
R97, linked with 955 and 956	
		955	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Revised to A96
R98, linked with 954 and 956	
		956	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Revised to A97
R99, linked with 954 and 955	
		964	Lost XID Response	 04.64 	Motorola	Agreed.
R97, linked with 965 and 966	
		965	Lost XID Response	04.64 	Motorola	Agreed.
R98, linked with 964 and 966	
		966	Lost XID Response
	04.64	Motorola	Agreed.
R99, linked with 964 and 965	
		984	Assignment of multiple TLLI values	04.64	Matsushita	Agreed.
R97, linked with 985 and 986	
		985	Assignment of multiple TLLI values	04.64	Matsushita	Agreed.
R98, linked with 984 and 986	
		986	Assignment of multiple TLLI values	04.64	Matsushita	Technical contents was agreed but must be Revised to A49 to align CR number.
Wrong reference version, 24.064 does not exist. The CR should be on 04.64 V. 8.0.0.
This is CR #5 against 24.065 -> The secretary to check the tdocs with the other 4 CRs against 24.064.
R99, linked with 984 and 985	
		987	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	To be revised to A46
Related with 990 and 992.
R97, linked with 988 and 989	
		988	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	To be revised to A53.
R98, linked with 987 and 989 and 993	
		989	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	To be revised to A50.
R99, linked with 987 and 988	
		A42	Clarification on the behaviour of an unused SAP	04.64	Siemens	Agreed.
Revision of 951, linked with A43, A44	
		A43	Clarification on the behaviour of an unused SAP	04.64	Siemens	Agreed.
Revision of 952, linked with A42, A44	
		A44	Clarification on the behaviour of an unused SAP	04.64	Siemens	Agreed.
Revision of 953, linked with A42, A43	
		A46	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	Agreed.
R97, linked with A53, A50, A47
Revision of 987	
		A49	Assignment of multiple TLLI values	04.64	Matsushita	Agreed.
R99, linked with 984 and 985
Revision of 986.	
		A50	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	Agreed.
R99, linked with A46 and A53, A47
Revision of 989.	
		A53	Failure of Layer-3 XID negotiation in ADM mode	04.64	Matsushita	Agreed.
R98, linked with A46 and A50, A47 A48
Revision of 988	
		A95	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Agreed.
Revision of 954
R97, linked with A96 and A97	
		A96	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Revised to B05.
Revision of 955
R98, linked with A95 and A97	
		A97	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Agreed.
Revision of 956
R99, linked with A95 and A96	
		B05	Clarification on the TLLI assign, change and un-assign procedure	04.64	Siemens	Agreed.
Revision of A96.
Linked with A95 and A97.	
							
		942	Collision handling	04.65	Siemens	for email approval -> Rejected
Possibly to be presented in the TSGN Plenary #5 by the Chairman.
R97, linked with 943 and 944	
		943	Collision handling	04.65	Siemens	For Email Approval -> Rejected
Possibly to be presented in the TSGN Plenary #5 by the Chairman.
R98, linked with 942 and 944	
		944	Collision handling	 24.065	Siemens	For Email Approval -> Rejected
Possibly to be presented in the TSGN Plenary #5 by the Chairman.
Cover page details & Tdoc number?
R99, linked with 942 and 943	
		960	XID Negotiation During PDP Context Deactivation and Modification	04.65	Motorola	Agreed.
This proposal adds signalling load to cover a complicated case. For the simple case of single PDP context the implicit mechanism would be more efficient.
R97, 960, 961, 962, 963, 982, 983 and A54, A92 are related.	
		961	XID Negotiation During PDP Context Deactivation and Modification	04.65	Motorola	Agreed.
This proposal adds signalling load to cover a complicated case. For the simple case of single PDP context the implicit mechanism would be more efficient.
960, 961, 962, 963, 982, 983 and A54, A92 are related.
R98, linked with 960	
		962	XID Collision Corrections	04.65	Motorola	Rejected.
This proposal adds signalling load to cover a complicated case. For the simple case of single PDP context the implicit mechanism would be more efficient.
960, 961, 962, 963, 982, 983 and A54 , A92are related.
R97, linked with 963	
		963	XID Collision Corrections	04.65	Motorola	Rejected.
This proposal adds signalling load to cover a complicated case. For the simple case of single PDP context the implicit mechanism would be more efficient.
960, 961, 962, 963, 982, 983 and A54 , A92are related.
R98, linked with 962	
		976	V.42 bis compression	 04.65	Ericsson	Agreed.
R99 variant of the CR will be required. The originator to provide it. -> A57.
R97, linked with 995	
		982	Handling of compression entities in case of a LL Reset Indication	 04.65	Matsushita	Rejected.
960, 961, 962, 963, 982, 983 and A54, A92 are related.
R97, linked with 983	
		983	Handling of compression entities in case of a LL Reset Indication	 04.65	Matsushita	Rejected.
960, 961, 962, 963, 982, 983 and A54, A92 are related.
R98, linked with 982	
		990	Failure of Layer-3 XID negotiation	04.65	Matsushita	Revised to A47
R97, linked with 991	
		991	Failure of Layer-3 XID negotiation	04.65	Matsushita	To be revised to A48.
R98, linked with 990	
		995	V.42 bis compression	04.65	Ericsson	Agreed.
R99 variant of the CR will be required. The originator to provide it. –> Tdoc A57.
R98, linked with 976	
		A47	Failure of Layer-3 XID negotiation	04.65	Matsushita	Agreed.
R97, linked with A48, A46
Revision of 990.	
		A48	Failure of Layer-3 XID negotiation	04.65	Matsushita	Agreed.
R98, linked with A47.
Revision of 991.	
		A54	Clarification of handling of compression entities	04.65	Matsushita	Rejected.
960, 961, 962, 963, 982, 983 and A54, A92 are related.	
		A55	Handling of compression entities in case of a LL Reset Indication	24.065	Matsushita 	Rejected.	
		A56	Failure of Layer-3 XID negotiation	24.065	Matsushita	Agreed.
Related with A46, A47, A50, A53 and others.	
		A57	V.42 bis compression	24.065	Ericsson	Agreed.
R99, linked 976, 995	
		A92	Discussion paper on the deletion of compression entities in 04.65		Matsushita	Noted.
960, 961, 962, 963, 982, 983 and A54, A92 are related.	
		B06	XID Negotiation During PDP Context Deactivation and Modification
	24.065 	Motorola	Agreed.	
							
		A79	Explicit IMSI detach, abnormal case SGSN side	  09.18	Siemens	Agreed.
R97, linked with A80 and A81	
		A80	Explicit IMSI detach, abnormal case SGSN side	09.18	Siemens	Agreed.
R98, linked with A79 and A81	
		A81	Explicit IMSI detach, abnormal case SGSN side	29.018	Siemens	Agreed.
R99, linked with A79 and A80	
		A82	SGSN reaction upon a RAU request after VLR failure	09.18	Siemens	Rejected
R97, linked with A84 and A83	
		A83	SGSN reaction upon a RAU request after VLR failure	09.18	Siemens	
R98, linked with A82 and A84	
		A84	SGSN reaction upon a RAU request after VLR failure	29.018	Siemens	
R99, linked with A82 and A83	

							
							
4.3	Other Pre-99 WIs						
	LCS	A59	CR fo r GSM03.71 for LCS-Phase2		Nortel	Presented for information, Noted.	
		B10	Location services phase2 overview presentation 		Nortel	Noted.	

5 	Work Plan for TSGN WG1 for 1999						
		920	TSG CN Specifications allocation		MCC	For information	
		921	Study items and milestones for UMTS R99		NTT DoCoMo		
		928	3GPP meeting calendar		MCC	TSGN1 #10 11.-14.1.2000
SMG#31 14.-18.2.2000
TSGN1 #xx 28.2.-2.3.2000
TSGN#7  13.-15.3.2000
TSGN1 #xx 15.-19.5.2000 (U.S./T1P1)
TSGN#8  5.-7.6.2000
SMG#32 26.-28.6.2000
TSGN1 #xx 11.-15.9.2000 (U.S. / T1P1)
TSGN#9  25.-27.9.2000
SMG#33 6.-10.11.2000
TSGN1 #xx 27.11 – 1.12.2000
TSGN#10 11.-13.12.2000

							
6	R99 Stage 3						
6.1	Multicall					•	Some points still to be clarified and PS side mostly not covered yet but sufficient working assumptions to present the first CRs. Nothing approved yet.
•	Stage 2 to be studied?	
		970	Information in Handover Request for Multicall		Ericsson	Noted	
		A12		24.008	NTT	Rejected.
•	Discussion on whether multicall should apply to GSM too. This can not be done now, but should be considered. 
•	The service requirements seem to be missing for GSM and will need to be defined.
•	A more general question on how to specify the features that can only be supported via UTRAN in common CN specification? -> the possibility to make the signalling mandatory part of R99 but leave the support of the feature optional or conditional.
•	SI concept was agreed to be applicable to CS and PS. This proposal is on CS only, PS should be studied too.
•	A rapporteur for the 24.008 part of the WI was proposed -> Koshimizu san is a candidate.	
		B23	Addition of the Stream Identifier Information Element	24.008	NTT	Reject.	
6.2	Multimedia call					•	CS Multimedia working assumption is to build it on top of a bearer service (asynchronous transparent data) but with specified multimedia codec (H.324M/H.245) defined for compatibility between different implementations.
•	Upon hearing the news that S2 have decided to use H.323 for PS services the joint meeting made working assumption that H.324M is to be used for CS video calls. 
•	> LS in N3-99224 to S1 and S2 to ack PS / H323 and indicate CS / H.324M.
•	The proposal of a new data rate 32kBit/s was discussed but consensus was could be reached yet.
•	Working assumptions allow us to present the CRs in the next meeting.
•	The open issues regarding MM will also have an impact on multimedia. The 23.110 to be studied for the UTRAN services.	
		971	Low rate 3G-H324		Ericsson	Noted.	
		972	3G-H324M as a bearer service		Ericsson	Noted.	
		973	Proposal for additional point codes in UMTS Bearer Capability Information
Element		Ericsson	Agreed.	
		977	Technical Report for Multimedia		Nokia	Noted.
•	Support for the general idea of collecting the requirements.
•	Doesn't the TR for multimedia already exist in S1?
•	The interworking between H.324M and H.323 must be defined. The current proposal was to leave this out of the R99. The work on H.324M is in progress by ITU but part the interworking issues may require the attention of TSGN. The requirement for the H.324M and H.323 to interwork was agreed but the schedule is still open.
•	Why can't single numbering scheme be used? -> In UMTS network this would work, but when you get a call from PSTN with no BC info at all, then the MS probably would default on speech call. This limitation is not acceptable for all delegations, so the possibility for its removal should be studied.	

							

6.3	GSM / UMTS interworking					•	This task in on critical path in R99 schedule.
•	N1 had several fundamental questions to take to the latest HO joint meeting 23.8.1999. Many of these are still open.
•	Change of URA / ULA relation from GSM RA / LA causes a major redesign which can not be done in time for R99. -> liaising to S2 if they realy insist on this?	
		A22	Questions and comments on LLC removal and UMTS impact on CN Protocols		N1 chairman	Noted.
RAN3 was expected to send a LS to N1 after their meeting. What happened?	
6.4	MS Classmark					Working assumptions:
•	The following working assumptions should be moved to the TR and presented preferably during this meeting. If that is not possible then email distribution is recommended.
•	GSM MS CM2 becomes UMTS CN CM.
•	GSM MS CM2 has got only 3 spare bits left, so this is just a starting point and an extension must be defined.
•	Where is the RAN CM information for other RANs stored? MS or RAN or CN? -> MS CM for UTRAN in RAN and GSM RAN CM in MSC (as is done now in GSM)
•	Single RAN CM or one for each RAN? This depends on where the RAN CM is stored. One big lump leaves no chance for interrogation of the data for the other RAN only if it is needed. But this is a TSGR issue anyway. -> We propose separate ones for each RAN for modularity.
Open issues:
•	In which L3 messages is CN CM information to be sent?
•	In which messages is the RAN CM information to be sent?
•	What is the criteria for the MS to send different CN / RAN CM information? -> The requirements for single mode network are reasonably clear: CN CM is sent always and the RAN CM based on the serving RAN. -> additionally the RAN CM for the other RAN in multimode network needs to be known. Does the MS send this always or only after enquiry or DL indication by the network? If so, is it RNC/BSS or MSC which initiates the enquiry?	
		974	Principles on Classmark Information Handling		Ericsson	Noted.	
		980	Rational for defining Classmark interrogation procedure in MM		Fujitsu	Withdrawn.
CR related to discussion paper in A07.	
		A07	Rational for defining Classmark interrogation procedure in MM		Fujitsu	Noted.
Discussion paper related to CR in 980.	
		A08	Ciphering Algorithm Information in UE Capability		Fujitsu	Noted.
LS to RAN2 	
		A09	MS Classmark		Dolphin	Withdrawn	
		A60	Classmark handling between UMTS and GSM 		Nokia	Noted.	
		B09	Classmark handling ;between UMTS and GSM		Fujitsu	Noted.	
							
6.5	L3 Segmentation					•	The first discussions on the principles.	
		959	L3 Message Segmentation, feasibility study		Nokia	Noted.
•	Why not do L2 segmentation? LS to SMG2, R2 and R3 in A93.
•	Progress is not a good option for carrying the extension, it's downlink only. 
•	MS CM2 is the one to use for this kind of CN related information, not CM3.
•	MM specific information could be sufficient to give the downlink indication to the mobile that the serving CN is R99 level.
•	CCBS interaction -> SETUP container in CCBS Recall must be solved too.	

6.6	Turbocharger					•	Feasibility study phase	
		A06	Feasibility aspects of the Turbo Charger
		Alcatel	Withdrawn	
							
6.7	EDGE					EDGE:
•	Some of our CRs will impact 08-series and SMG2 WPA. These need to be seen by SMG2
•	No major open items or questions
•	Possibly some further CRs still needed.	
		996	due to asymmetry for ECSD	22.034	Nokia	withdrawn	
		997	due to asymmetry for ECSD	23.034	Nokia	Revised to B18.	
		998	due to asymmetry for ECSD	24.008	Nokia	Revised to B16.	
		999	IMPACTS OF MS RADIO ACCESS CAPABILITY INFORMATION ON SIGNALLING MESSAGES 		Nokia	Noted.	
		A00	MS RADIO ACCESS CAPABILITY IE DUE TO EDGE	24.008	Nokia	Revised to B17.	
		A01	MS RADIO ACCESS CAPABILITY IE	08.18	Nokia	For information	
		B16	due to asymmetry for ECSD	24.008	Nokia	Agreed.
Revision of 998.	
		B17	MS RADIO ACCESS CAPABILITY IE DUE TO EDGE	24.008	Nokia	Agreed.
Revision of A00	
		B18	due to asymmetry for ECSD	23.034	Nokia	Agreed.
Revision of 997	

6.8	Other R99 issues						
		925	Clarification of DTMF message sequence		Vodafone	Not available	
		926	DTMF message sequence	24.008	Vodafone	Not available	
		927	DTMF message sequence	23.014	Vodafone	Not available	
		978	Paging Response as a MM message	24.008	Fujitsu	•	Proposal to use the existing RR paging procedure for R99 GSM and the new MM paging procedure for UTRAN.
•	Two alternatives exist, either this approach which introduces a new MM Paging Response message or enhancing the CM SERVICE REQUEST with more information. 
•	Should the MM Paging procedure cover just UTRAN acceess or GSM R99 too? -> 
•	If GSM R99 changes paging to MM then 
•	R99 mobiles will still have to implement R98 paging to communicate to old networks
•	R99 GSM networks will still have to implement R98 paging to communicate to old mobiles.
•	Hannu, put this to the N1 status report for Plenary.
•	The interaction of RR and MM paging timers.	
		979	Extended Transaction Identifier Reject	24.008	Fujitsu	
Linked with 981.	
		981	Transaction Identifier Extension
	24.007	Fujitsu	
Linked with 979	
		A02	The authentication and key agreement
		NTT Software Corporation		
		A13	3G PS-SMS		NTT	Noted.
Proposal to route the packet SMSs via GMM.
We should see 23.121 on this question too.
04.11 was transferred to 3GPP and seems to become the N1 responsibility. The SMS protocol itself would be in a stable state but the LLC removal causes some redesign to be needed.	
		A14	Multicall	24.007	NTT	For information
Comment that GPRS and GSM will not be deleted from R99. The UMTS packet access should be added to the specifications. The intention is not to replace the existing GSM but add something new. One problem to be solved is that lot of the terminology and concepts like MS Class A, B and C have got no scope outside GPRS.
Hannu, take this to the next Plenary.	
		A15	Multicall, CR001	24.011	NTT	For Information	
		A16	Location Area Concept		NTT	Withdrawn	
		A17	Multicall, CR002	24.011	NTT	For Information	
		A18	3G TS33.102, V3.1.0, Security Architecture		Nokia	Noted, for information	
		A20	3G Project co-ordination aspects, Project plan for security		Nokia	Noted, provided for Information
•	The entire CN or just UMTS? -> R99!	
		A30	Codec negotiation procedure		NTT DoCoMo	•	R99 or R00?
•	N2 must be involved in the discussion. This contribution is based on out-of-band transcoder control TR from N2.
•	Related to WI out-of-band transcoder control. If this WI gets moved from R99 to R00 then the complete design will not be needed for R99. However, the radio interface negotation for the codecs should be defined in R99 to avoid compatibility problems when adding new codecs later.
•	N1 prefer alternative 1, which looks like the current GSM for the mobiles indicate all of the codecs they support and the MSC/VLR makes the choice of which one to use.
•	Should RR or CC message be used for indicating the codecs in downlink direction? -> no requirement for CC level indication of codec could be seen. 
•	The proposed mechanism does not seem to apply to the negotiation of multimedia codec.
Send a LS to N2 indicating the working assumptions or chairman to report this in the pleary?	
		A32	Proposed text of TS24.008 for in-call modification 	24.008	NEC	Noted.	
		A33	Changing the Call Mode	24.008	NEC 	Noted.	
		A34	Proposed text of TS23.108 for in-call modification	23.108	         NEC	Noted. Tdocs A32-A35 define one possibility for introducing ICM with no pre-notification to the specification if we get the go-ahead from S1 and N3.
	
		A35	In-call modification	23.108	NEC	Noted.	
		A36	Proposed action to S1 for in-call modification without pre-notification		NEC	Noted.
Questions:
1.	Is there an approved WI covering ICM? 
-> to be checked
2.	What is the outcome of MODIFY_REJECT
-> resume the previous BC
3.	Is there a subscription check at the ICM time?
-> the subscription is checked at negotiation time	

							
							
7	Output Liaison Statements						
		929	Bearer Modification without pre-notification			Noted. No need to send any more, this has already been dealt with in N1 – N3 joint meeting.	
		A23	clarifications on old and new TLLIs			Agreed.
Linked with A04.	
		A24	Liaison Statement on freezing of R97 and R98			Agreed.
Linked with A25.	
		A45	Response to LS on Service/Baseline Implementation Capabilities		TSG-CN WG1	Revised to B14	
		A74	LS on addition of APN Parameter in NW-requested PDP context activation procedure.			
Answer to LS in A29.
Related 24.008 CR in 922.	
		A75	Liaison Statement - Cover letter for TR21.904, Terminal Capabilities Report, interim version
TR21.904 			
Answer to LS in A31.	
		A88	LS on CBS Functionality and Responsibility			Agreed.
Answer to LS in A64.	
		A89	LS about Signalling			Revised to B15
Answer to A65	
		A90	LS on Location Area Concept.			To be revised to B13
Answer to A69.	
		A93	LS on L3 Message Segmentation			Agreed with editorial correction to highlight that we want to increase the capacity from 251, not to 251.
Related to tdoc 959.	
		A94	Comments on clarifications on old and new TLLIs			Agreed, to be attached to LS in A23.	
		B13	LS on Location Area Concept.			Revised to B20
Answer to question in A69.
Revision of A90.	
		B14	Response to LS on Service/Baseline Implementation Capabilities			Revised to B33
Revision of A45	
		B15	LS about Signalling			Agreed.
Revision of A89.
Answer to A65	
		B19	LS on EDGE			Agreed.
Related with B17, B18.	
		 B20	LS on Location Area Concept.			Agreed.
Answer to question in A69.
Revision of B13	
		B29	LS on multiplexing of several NSAPIS onto one LLC SAPI			Agreed.
Related with B01	
		B30	LS on ciphering algorithm			Withdrawn	
		B32	LS on classmark split			Revised to B34	
		B33	Response to LS on Service/Baseline Implementation Capabilities			Agreed. only editorial change to the previous version.
Revision of B14	
		B34	LS on classmark split			Agreed.
Revision of B32.	
							
		N3-99224	Liaison Statement on 3G-H.324M			Revised to A98
LS from Joint N1 & N3 meeting	
		A98	LS on 3G-H.324M			Agreed. 
This LS was also reviewed by N3 and it will be sent by N1 secretary.
Revision of N3-99224.	
							
8	A.O.B.