Documents for TSGN1 meeting #10, Abiko, Japan	Yellow cells indicate an allocated but not available Tdoc	
Agenda item	Agenda item title	Tdoc 3GPP N1-00	Title	Spec.	Source	Result	
1	Opening					11.1.2000 at 9:30 (estimate)	
2	Agenda & Reports	0001	Agenda		N1 Chairman	Noted. This file is a.k.a. Abiko0001.rtf	
		0003	TSGN #6 meeting report		MCC	Noted.	
		0124	TSGS #6 meeting report		MCC	Noted.
Vocabulary specification 21.905 needs to be maintained by N1 too -> LS to propose additions.	
							
3	Input Liaison statements						
		0007	Reply to Liaison Statement on MS CM3 clarification CR	24.008	SMG2WPA to N1	Noted.
This LS was already treated as N1-99E53 in Bad Aibling. SMG2 proposal was endorsed.
Reply to our LS in Tdoc N1-99D07 regarding MS CM3 clarification 24.008 CR 034. SMG2A propose a revision of Tdoc N1-99B91.	
		0008	LS to SA1 cc CN1, SMG2 on urgent need for requirements on Idle Mode 		TSG-RAN to S1 CC: N1, SMG2	Noted.
TSG-RAN would apreciate if the result of MS Idle mode discussion in TSGS1 as well as all the available documentation on the subject could be provided to TSGR2 before its next meeting 17-21st of January 2000.	
		0009	LS on QoS mapping in case of HO from 3G to 2G system	27.001	N3 to S2, 
CC: N1	Noted.
N3 are informing S2 on the working assumption that the BSSMAP parameters needed for handover to GSM are generated using the standard GSM procedure by mapping the BC IE into BSSMAP parameters.	
		0010	Reply to LS to S1 on 3G Services		N3 to S1
CC:S2, T2, N1	Noted.
N3 has agreed the deletion of the work item of Modem / ISDN interworking.
This is reply to S1 LS in N1-000021.	
		0011	Response to LS (S2-99c45) on Usage of NSAPI, RB identity, RAB Id and TEID		RAN2 to S2
CC: R3, N1	Noted.
R2 would like to clarify the following terms:
SA2 definition:
Radio Bearer identity (RB identity) is used to identify the Uu interface logical channel associating with the Radio Access Bearer. 
RAN2 remark: Radio Bearer identity is used to identify the Uu interface Radio Bearer and not logical channel. RAN 2 proposes to change the sentence to: Radio Bearer identity (RB identity) is used to identify the Uu interface radio bearer(s) associating with the Radio Access Bearer.
SA2 definition:
In Packet Domain, a network allocates one Radio Access Bearer for one PDP context. In addition, one Uu interface logical radio bearer is allocated for one Radio Access Bearer.
RAN2 remark: This would prevent the use of RAB subflows in the Packet Domain. RAN2 proposes that the last sentence is changed to: In addition, one radio bearer is allocated for each RAB subflow of one RAB.
Linked with 0015.	
		0012	Response to LS from R2 on partial SRNS relocation		RAN2 to R3
CC: N1	Noted.
Linked with 0013 and 0016.	
		0013	Response to LS on Usage of Uu Interface Sequence Numbers in Relocation of SRNS and in Inter System Handovers		RAN2 to R3 
CC: S2, N1	Noted.
R2 response to LS on Usage of Uu Interface Sequence Numbers in Relocation of SRNS and in Inter System Handovers.	
		0014	Reply to LS on Security Algorithm Information in UE Capability 		RAN3 to N1
CC: S3, R2	Noted.
LS that answers our LS N1-99D06.
R3 have liaised to us on this before but changes have been introduced in 25.413 (RANAP Specification) which makes the need for UTRAN to receive UE Security Information from CN not longer necessary. This information is now instead received from the UE during RRC connection establishment. The solution in RANAP is thus now in line with the stated N1 working assumption that UE Security Information shall be regarded as radio related information and thus not included in classmark information for CN.
As was stated in the previous answer, RAN3 is not sure why N1 assumed that MS CLASSMARK 2 was to be put into the Location Update message. This is still not understood by RAN3, but can now hopefully be disregarded. If not, N1 has to come back with some more information regarding this.	
		0015	LS on usage of NSAPI, RB identity, RAB ID and TEID		RAN3 to S2, N1, N2, R3	Reply in Tdoc 135.
R3 clarifies the definition of NSAPI, RB identity, RAB ID and TEID.
Linked with 0011	
		0016	LS on partial SRNS relocation		RAN3 to R2
CC: N1	Noted.
Linked with 0012, 0013.	
		0017	Liaison statement to SA2 concerning HSCSD specifications	22.034	S1 to N1, N3
CC: S2	Reply in Tdoc 136
Reply needed.
S1 have updated 22.034 for GBS in GERAN and ask N1 to do the same for 23.034.	
		0018	SAT Handover notification and termination of  call		S1 to S3, N1
CC:T3, SMG9, SMG1/9 SAT ad-hoc group	Reply in Tdoc 137.
N1 reply is needed.
Clearing of user initiated calls from SAT.
-	What details of HO should be given to SAT?
-	What about emergency calls?
-	Which call should be cleared in case of multiple calls?
-	AoC does not currently affect packet access so VoIP calls will not be affected.
-	What about non-supporting mobiles?
-	Security in open IF (S3 issue)
-	N1 is wondering if there is an SAT if to indicate cell change in idle mode. If such an IF exists, why create a new one for dedicated mode?	
		0019	Liaison Statement response to ‘Liaison statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture’		S2 to S1, N1	Noted.
The attached S2-99D56 to be presented.
S2 forward the attached CR also to N1, as N1 is currently  specifying the Service Classmark.	
		0020	Liaison Statement concerning TI value extension		S2 to N1	Noted.
Already seen in N1-99F46.	
		0021	Reply to LS to S1 on 3G Services		S1 to N3
CC:S2, T2, N1	Noted.
1.	S1 have agreed the deletion of the work item of Modem / ISDN interworking as S1 do not see any market requirement in this area for R99.
2.	S1 sees no need for support of  <PDP type> “X.25” in release '99 and onwards, therefore S1 has agreed the deletion of X.25.
N3 reply is in N1-000010	
		0022	Liaison statement to N1 and N2 concerning QoS parameter mapping between R97/98 and R99		S2 to N1, N2
CC: SMG2A	Noted.
The attached CR to be presented.
At the S2 meeting #10 in Abiko, Japan a CR to 23.107 was approved which contains a set of mapping rules between the releases	
		0023	Liaison Statement on the concern about the definition of the Service Area identity	23.060	S2 to N1, N2
CC: R2, R3	Noted.
CR needed. Is there any N1 issue?
The concept of Service Area Identity (SAI) and Service Area Code (SAC) have been introduced in 23.060 and N1 is asked to do corresponding changes to stage 3.	
		0024	Response liaison on Radio Access Bearer attributes (update of S2-E27)		S2 to R2, R3
CC:N1, N3, S4	Noted.
S2 reply to R3 LS. S2 have also agreed 3 CRs which are attached.
Definition of Transfer Delay is clarified in an attached CR for 23.107.
The relation between the rate control in UTRAN and the QoS attributes of 23.107 is clarified in an attached CR for 23.107.
How to interpret the tables of value ranges is clarified in an attached CR for 23.107.	
		0025	Answer to LS on UE/MS idle mode operation from N1		S2 to N1, S1, SMG2, R2	Noted.
Relates to N1-99E54 which we have already treated.
S2 agree to split the MS idle mode spec to AS / NAS parts.	
		0026	Liaison Statement on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation		S2 to N1, N2, R3, SMG2	Reply in 138.
N1 reply needed. What is N2 role in this question?
One proposed outgoing LS in is tdoc 0110.	
		0027	Response LS on Session Management QoS parameters		S2 to N1, S4
CC:N3, R2, R3, SMG2A	Reply in 149.
Attached CRs to be presented.
The scope of the CR F37 was not quite clear. Does it cover secondary PDP contexts only? How about the case when MS supports only 1 PDP context in GPRS?
S2 attach two CRs to 23.107 which detail the mapping of SM level QoS attributes between release 97/98 SM QoS classes and release 99 QoS attributes.	
		0028	Liaison Statement clarifying terms related to the naming of PDP contexts created with the 'PDP Context Activation Procedure'  and with the 'Secondary PDP Context Activation Procedure'		S2 to N1, N2	Noted.
To be presented.
The possible impact on SM section in 24.008 needs to be checked.	
		0029	LS on Enhanced User Identity Confidentiality		S3 to N1	Reply in 150.
N1 reply needed.
Storing the HLR address to SIM/USIM makes it more difficult to move subscribers between HLRs.
Where is the encryption done? SIM / ME?
UMTS only or GSM too? If GSM is included then the max. length causes CM service request to be segmented. (which is not possible due to the message is part of SABM)
MSB / LSB of bit streams?
There seems to be a hole in the sceme as IMSI paging is still allowed.
The criteria for ME to use XEMSI or IMSI is unclear.
New concept is being introduced. In principle this should not be done after functional freezing of R99 WIs in TSGN #6.	
		0044	Information on Common Communication Mechanism to be used by the Cell Broadcast Service		T2 to R3
CC:R2, N1, N2	Noted.
No N1 impact.
This tdoc is the same as 0053.	
		0045	LS on Service/Baseline Implementation Capabilities		T2 to SS Ad-hoc
CC:N1, S1	Noted.
T2 is asking for N-SS Ad-hoc help on the SS related Service / Baseline Implementation Capabilities.
This tdoc is the same as 0054.	
		0046	Liaison Statement on SAPI in Direct Transfer message		R3 to N1, R2
CC: S2	Noted.
N1 reply needed but it was agreed that the companies interested in LCS discuss with their delegates as LCS is the only WI which may impact this decision. Otherwise it is OK, but a new SAPI for LCS purposes is being considered and if that happens then a new GSM SAPI should be reflected in UMTS too.
R3 propose that similarily to GSM SAPI 0 would be high priority and SAPI 3 lower. Is this OK for us?	
		0047	Liaison statement on BEARER MODIFICATION WITHOUT PRE-NOTIFICATION		S1 to N1, N3, S2	Noted.
Reply from S1 to N3 LS N3-99373.
S1 give examples of cases when BC modification needs to be done. 	
		0048	LS on addition of general bearer services	22.002	S1 to N1, N3, S2	Noted.
S1 have defined new bearer services for multimedia services in 22.002.	
		0049	LS on Requirements for Network Selection		S1 to R2, S2, SMG2A, N1, SMG9, T3	Reply in tdoc 155.
S1 reply to N1-99D27. S1 are introducing two new concepts, taking access technology and operatorr controlled PLMN selector list into account for PLMN selection. This is clearly against the rules we agreed in TSG #6 when R99 was functionally frozen.  This new feature would risk R99 schedule.
Should the MS default that a network not indicating the new system info on speech support is an old network supporting speech?
Search and replacing MS with UE does not work. ASCI supporting UE does not exist unless S1 want to define ASCI for UMTS, see references.
23.022 is cancelled. 23.122 which comes instead is an MS, not UE specification (the title).
Default radio access technology should be defined for backwards compatibility to the SIM cards which do not specify any radio access.
The distinction between GSM freq. bands does not work unless the intention is to change the multiband operation feature.
The attached CR is missing in this document –> to be distributed in separate document during the meeting.
Related S1 CR in Tdoc  0151.
T3 reply in LS in 0118.	
		0050	Reply to LS on Common Identification for Relocation Co-ordination		S1 to R3
CC: N1	Noted.
3GPP SA WG1 would like to clarify that currently no requirement exists for PS emergency calls.
No N1 impact.	
		0051	LS on RAB linking		R3 to S1, N1
CC: S2	Reply in tdoc  0152.
Is assignment and bearer allocation procedure needed for a group fo bearers?
Multicall is given as one example.
another copy of the LS in 0119.	
		0052	RAB pre-emption		R3 to S1, N1
CC: S2	The reply will be included in tdoc 0152 to the same recipients: S1 issue to decide, there are no CN protocol requirements on how to cope with the radio channel congestion.
R3 proposes a pre-emption mechanism and ask for N1 comment on the proposal.	
		0053	Information on Common Communication Mechanism to be used by the Cell Broadcast Service		T2 to R3
CC: N1, N2, R2	Noted.
No N1 issues involved.
This tdoc is the same as 0044.	
		0054	LS on Service/Baseline Implementation Capabilities		T2- SWG6 to SS Ad-hoc
CC:N1, S1	Noted.

This tdoc is the same as 0045.	
		0057	Liaison Statement concerning Transcoder Free operation		S2 to TSGN#6
CC: TSGS, N2	Noted.
Resending an S2 to N2 LS. No N1 impact.	
		0117	Capability configuration parameters		T3 to N1	Reply in tdoc 0153
Presentation of LS -> N1 reply is needed.
-	R96 already contains 15 octet BC and this is not reflected in the SIM card.
-	BC IE format is similar in R98 and R99 but new code points will be needed to existing fields for R99.	
		0118	LS on network selection issues		T3 to S1
CC: N1,R2, S2, SMG2A, SMG9	N1 will reply to 0049
T3 is waiting for S1 opinion.
Operator controlled / User controlled PLMN selector list?
Linked with 0151.
This is T3 reply to LS in 0049.	
		0119	Proposed LS on RAB linking		RAN3, Nortel	Noted. Duplicate copy of tdoc 0051.	
		0207	LS on Clarification of the cell reselection for a GPRS MS		SMG2 WPB	Noted. GPRS ad-hoc meeting should look at this LS.	
		0208	Liaison Statement on CR to 23.122 after split in SMG2 and CN1		SMG2	Reply in 209.
Received Friday afternoon with no time at all to review the attached CR. Chairman tasked to draft an LS to respond to SMG2 WPB that:
•	No serious objections were raised against the principle but N1 needs more time to study it and will come back to the issue in TSGN1 #11 28.2.-3.3.2000.
•	There is an open issue regarding the PLMN selector lists and N1 has sent a question on this  to S1 in tdoc N1-000201 and is expecting an answer which may impact the CR.
•	There is an error in 4.4.3.2 where User controlled PLMN selector list is defined twice.
•	The originator is invited to present the CR in the next TSGN1 meeting #11 as the change impacts specification under N1 responsibility.	

4	Maintenance of R98 and older releases					Request not to treat GPRS issues before Wednesday.
Due to large number of contributions all tdocs could not be treated. The remaining GPRS documents were forwarded to a GPRS ad-hoc meeting as this WI involves mostly European delegates and this way we minimise travelling.
The dates for the GPRS ad-hoc meeting was agreed to be 19.-20.1.2000 in Oslo. Motorola is willing to host the meeting. Hans Peter Naper is the contact person for the meeting.
The output of the meeting is proposed for email approval on both WG (N1) and SMG STC (SMG3 Plenary) level.
N1 level email approval procedure was agreed upon. Ban to check the possibility of SMG3 email plenary with the SMG3 Plenary chairman.	
4.1	Corrections						
		0035	Timer control for GPRS detach	04.08	Siemens/ Roland Gruber	Forwarded to GPRS ad-hoc
R97 GPRS CR	
		0036	Timer control for GPRS detach	04.08	Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc
R98 GPRS CR	
		0037	Timer control for GPRS detach	24.008	Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc
R99 GPRS CR	
		0059	Revised Proposed resolution of the different interpretations of the NITZ specifications		TSG SA#6 / MCC	noted. This SA document gives the reasons for NITZ CRs in tdoc N1-000194, 196, 197, 198.
Discussion
0050, 0060, 0061, 0062, 0063 are linked	
		0060	Clarification of NITZ time stamp coding	24.008	Nokia	Withdrawn.
WI: NITZ	
		0061	Clarification of NITZ time stamp coding	24.008	Nokia	Withdrawn.
WI: NITZ	
		0062	Clarification of NITZ time stamp coding	24.008	Nokia	Withdrawn.
WI: NITZ	
		0063	Clarification of NITZ time stamp coding	24.008	Nokia	Withdrawn.
WI: NITZ	
		0091	Removal of APN from REQUEST PDP CONTEXT ACTIVATION REJECT message	04.08	Vodafone/Siemens / Duncan Mills	Agreed.

R97, WI:GPRS	
		0092	Removal of APN from REQUEST PDP CONTEXT ACTIVATION REJECT message	04.08	Vodafone/Siemens / Duncan Mills	Agreed.

R98, WI:GPRS	
		0093	Removal of APN from REQUEST PDP CONTEXT ACTIVATION REJECT message	24.008	Vodafone/Siemens / Duncan Mills	Agreed.

R99, WI:GPRS	
		0094	Overall Description of GPRS Simple Class A mobiles	N/a	Vodafone / Duncan Mills	Provided for information, comments are invited.
WI:GPRS	
		0096	Correction of N-PDU IE Length in GMM messages Routing Area Update Accept and Routing Area Update Complete.	04.08	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0097	Correction of N-PDU IE Length in GMM messages Routing Area Update Accept and Routing Area Update Complete.	04.08	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0098	Correction of N-PDU IE Length in GMM messages Routing Area Update Accept and Routing Area Update Complete.	24.008	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0099	Usage of Combined Procedures during CM service reject	04.08	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0100	Usage of Combined Procedures during CM service reject	04.08	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0101	Usage of Combined Procedures during CM service reject	24.008	MOTOROLA/ Mahesh Perepa	Forwarded to GPRS ad-hoc	
		0102	Clarification of use of Mobile Reachable timer	04.08	MOTOROLA/ Mahesh Perepa		
		0103	Clarification of use of Mobile Reachable timer	04.08	MOTOROLA/ Mahesh Perepa		
		0104	Clarification of use of Mobile Reachable timer	24.008	MOTOROLA/ Mahesh Perepa		
		0105	Handling of Link failures in SM	04.08	MOTOROLA/ Mahesh Perepa		
		0106	Handling of Link failures in SM 	04.08	MOTOROLA/ Mahesh Perepa		
		0107	Handling of LLC failures in SNDCP during No Peer Response	04.65	MOTOROLA/ Mahesh Perepa		
		0108	Handling of LLC failures in SNDCP during No Peer Response	04.65	MOTOROLA/ Mahesh Perepa		
		0120	Clarification of N201 usage for segmentation/re-assembly	04.65	Alcatel	Withdrawn.
R97 GPRS CR, is R99 CR needed?	
		0121	Clarification of N201 usage for segmentation/re-assembly	04.65	Alcate	Withdrawn.
R98 GPRS CR, is R99 CR needed?	
		0128	XID negotiation while MS suspended, and collision with XID Reset	04.64	Siemens AG/ Roland Gruber	Agreed.
For SMG3 Plenary email approval -> SMG #31	
		0129	XID negotiation while MS suspended, and collision with XID Reset	04.64	Siemens AG/ Roland Gruber	Agreed.
For SMG3 Plenary email approval -> SMG #31	
		0130	XID negotiation while MS suspended, and collision with XID Reset	04.64	Siemens AG/ Roland Gruber	Agreed.
For SMG3 Plenary email approval -> SMG #31	
		0131	Status of 04.64 question list		Siemens AG/ Roland Gruber	Noted.
Any comments against this document are invited via email to Roland Gruber, Siemens.	
		0132	Clarification of NITZ time stamp coding	04.08	Ericsson/ Mark Fenton	Revised to 0194.	
		0157	Unsolicited UA or XID response	04.64	Motorola, Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0158	XID parameter length value	04.64	Motorola, Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0159	Ignore command frames with poll bit set to 0	04.64	Motorola, Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0160	XID negotiation failure after N200 retransmissions	04.64	Motorola, Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0161	SNCPC behaviour after N200 LLC retransmissions	04.65	Motorola, Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0162	Re-establishment after LL-Reset.ind	04.65	Siemens AG/ Roland Gruber	Forwarded to GPRS ad-hoc	
		0194	Clarification of NITZ time stamp coding	04.08	Ericsson/ Mark Fenton	Agreed.
R96. WI:NITZ
Revision of 0132	
		0196	Clarification of NITZ	04.08	Ericsson-Nokia/ Mark Fenton	Agreed.
R97. WI:NITZ	
		0197	Clarification of NITZ	04.08	Ericsson-Nokia/ Mark Fenton	Agreed.
R98. WI:NITZ	
		0198	Clarification of NITZ	24.008	Ericsson-Nokia/ Mark Fenton	Agreed.
R99. WI:NITZ	
							
5 	Work Plan for TSGN WG1 for 2000					TSGN1 #10 11.-14.1.2000 (Abiko, Japan/NEC)
GPRS Ad-Hoc  19.-20.1.2000 (Oslo/ Motorola)
Please note the additional meeting!!!
SMG#31 14.-18.2.2000
TSGN1 #11 28.2.-3.3.2000 (Umeå, Sweden/Telia)
Please note changed meeting date!!! 
TSGN#7  13.-15.3.2000
TSGN1 #12 22.-26.5.2000 (Hawaii, U.S./T1P1)
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 20.11 – 24.11.2000
Please note changed meeting date!!! 
                                       (Tentative invitation Lucent)
TSGN#10  6.-8.12.2000
Please note changed meeting date!!!	
		0002	TSGN1 Terms of Reference (ToR)		Chairman	Revised to 0165	
		0005	Open Issues for Release 99 List		MCC	Noted.	
		0006	TSG N Work Items Status List		MCC	Noted.	
		0067	Specifications within TSG-N after 
TSGN #6	-	MCC	Noted.	
		0068	3GPP Calendar	-	MCC	Noted.	
		0125	Working Plan to complete OoBTC in R99		NTT DoCoMo/ Naoki Tani	Noted.	
		0126	Working Plan to complete Multicall in R99		NTT DoCoMo/ Naoki Tani	Noted.	
		0165	TSGN1 Terms of Reference (ToR)		Chairman	Agreed.
Revision of 0002.	
		0174	Project Plan on location and cell broadcast services in UMTS (3G PD 30.806 version 1.2.1)	30.806	Nokia/Janne Muhonen	Noted.
Janne Muhonen / Nokia was nominated as N1 Rapporteur for the WI.	
							
6	Release 99						
6.1	Multicall						
		0030	Draft Stage 1.5 for Multicall		NTT Comware/ Kazuo Mitamura	N1 issues reviewed and the listed working assumptions were confirmed from N1 viewpoint.	
		0031	Addition of the Stream Identifier Information Element	24.008	NTT Comware/ Kazuo Mitamura	Revised to 0156.
•	The handling by the network of the first call attempt with SI not indicating value 1 needs to be defined.
•	MS requirements need to be moved from 5.2.1.2 to subclause defining MS behaviour.
•	Is it necessary to reserve SI values for SM?
•	In R99 SI is not a common IE and needs to be moved to CC IEs.
•	The value range for CC SI codepoints that is unallocated must be either taken in use to extend the SI range or alternatively error handling must be defined.	
		0082	Terminal Capability handling		NTT Comware	It was agreed that terminal multicall capability handling in terms of MS CM indication is N1 issue. 
Further discussion on the implementation.	
		0127	Multicall Basic Concept		NTT DoCoMo/ Naoki Tani	The first 3 proposals were agreed, the proposal to send an LS from N1 was objected.	
		0146	Multicall AdHoc Working Plan and the Milestone		DoCoMo/ koshimizu	Noted.
Discussion	
		0156	Addition of the Stream Identifier Information Element	24.008	NTT Comware/ Kazuo Mitamura	Revised to 0210
Revision of 0031.	
		0185	Additions to draft stage 1.5 on CW and NDUB for Multicall		Ericsson/Zdravko Jukic	Revised to 0192.
Discussion	
		0195	Remarks to TDoc 000031
(Addition of the Stream Identifier Information Element)		Siemens AG / Frank Schramm	Noted.
Related with LS in 0135 and 0156.
Discussion	
		0210	Addition of the Stream Identifier Information Element	24.008	NTT Comware/ Kazuo Mitamura	Agreed.	
							
6.2	Multimedia call		Functionally frozen for R99				
		0064	Changes to support a circuit switched multimedia call	24.008	Nokia	Revised to 0166.
Part of the CR contains requirements that are hidden inside the network and have nothing to do with the radio interface. These should be moved to another CR on 29-series.	
		0065	Multimedia telephony TR	23.972	Rapporteur	Revised to 203.
More time to study the proposal was needed due to late submission of the document.
V.140 usage was objected on the grounds that the new, yet non-existing protocol introduces a risk.
Maybe an LS to S2 to propose this as N1 working assumption and to ask for S2 to endorse it.
Due to fallback issues the proposal should be reviewed by N3 as well.	
		0066	Changes to support a circuit switched multimedia call	29.007	Nokia	Provided for review. 
Companies are invited to check this CR together with their N3 colleagues in order to establish a stable working assumption as soon as possible.	
		0154	Fallback procedure		DoCoMo/ Kushimizu	Noted.	
		0166	Changes to support a circuit switched multimedia call	24.008	Nokia	Agreed.
Revision number must be raised to 1.
Revision of 0064	
		0203	Multimedia TR 	23.972	Nokia /Timo kauhanen	Presented for information, comments are invited.
Revision of 0065.	

6.3	GSM / UMTS interworking		Functionally frozen for R99			Open Issues:
•	Call Control BC changes to allow negotiation of high speed TCH not only using GSM multislot configuration but also UTRAN.
•	Does Anonymous Access apply to UMTS or does it not?->0083, 0084.
•	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 specifications.
•	Selective RA update concept introduced. Is it necessary to inform the CN about the change of the system? (N1 can not proceed on this path if S2 does not decide on the Stage 2 first) -> N1-000168.
•	The coding of DRX parameters IE for UMTS needs to be defined.
•	The MS behaviour after diagnosing network authentication error should be specified.	
		0032	SMC-GP SDL modification to transfer SMS messages via GMM	24.011	NTT Comware/ Nobuyuki Uda	Revised to 167.
CR	
		0058	Proposed 3rd Generation NAS information	24.008	Nippon Telecommunications Consulting CO., LTD./ Tatsushi Nakahira	Revised to 148

CR	
		0071	System Information	24.008	Ericsson/ Monica Wifvesson	Revised to 173.
Octet border between 1st and 2nd LAC octet.
Work item must be GSM-UMTS interworking.	
		0072	P-TMSI re-allocation in the Service Request	24.008	Ericsson/ Monica Wifvesson	Rejected.
Proposal to collect comments before the next meeting.	
		0073	P-TMSI re-allocation in the Detach procedure	24.008	Ericsson/ Monica Wifvesson	Rejected.
Proposal to collect comments before the next meeting.	
		0074	Terminology clarifications in Selective Routing Area Update  procedure	24.008	Ericsson/ Monica Wifvesson	Revised to 0168.	
		0075	UMTS<->GSM Intersystem change within the same RA	24.008	Ericsson/ Monica Wifvesson	Withdrawn.
	
		0076	Synchronisation of READY timers	24.008	Ericsson/ Monica Wifvesson	Withdrawn.	
		0077	Paging for packet domain services and selective RAU updating	24.008	Nokia/ Jaakko Rajaniemi	Withdrawn (contents incorporated in 0090)	
		0078	Abnormal cases in Service Request procedure	24.008	Nokia/ Jaakko Rajaniemi	Revised to 0169.	
		0079	Lower layer failures and GMM	24.008	Nokia/ Jaakko Rajaniemi	Withdrawn	
		0080	Service Request procedure in the chapter 4.1.1.	24.008	Nokia/ Jaakko Rajaniemi	Agreed.	
		0083	Updating Session Management (SM) for R99	24.007	Ericsson	Rejected.
CR	
		0084	Removal of Anonymous Access	24.007	Ericsson	Agreed. 
CR, linked with 0085	
		0085	Removal of Anonymous access	24.008	Ericsson	Agreed.
CR, linked with 0084	
		0086	Clarification to the MS handling when receiving detach type 'IMSI detach'.	24.008	Ericsson	Rejected.
CR	
		0089	Handling of P-TMSI signature in the MS and the network	24.008	Ericsson/Per	Withdrawn
CR	
		0090	Paging response in 4.7.9	24.008	Ericsson	Revised to 0171.
tdoc 0077 is incorporated in this tdoc.	
		0122	Recovery from unsynchronised condition of PDP context state		Fujitsu	Noted.	
		0123	Coding of NAS Binding Info field	24.008	Fujitsu	Revised to 0172.
The definition of the field inside NAS binding information IE to be defined.
The encoding of the field in case of NSAPI and SI needs to be added.
The new IE should appear under a new subsection of section 10.
CR	
		0148	Proposed 3rd Generation NAS information	24.008	Nippon Telecommunications Consulting CO., LTD./Tatsushi Nakahira	The contents of this proposal need to be merged with tdoc 0173.

Revision of 0058.	
		0167	SMC-GP SDL modification to transfer SMS messages via GMM	24.011	NTT Comware/ Nobuyuki Uda	Agreed.
Revision of 0032	
		0168.	Terminology clarifications in Selective Routing Area Update  procedure	24.008	Ericsson/ Monica Wifvesson	Rejected.

Revision of 0074	
		0169	Abnormal cases in Service Request procedure	24.008	Nokia/ Jaakko Rajaniemi	Agreed.
Revision of 0078	
		0171	Paging response in 4.7.9	24.008	Ericsson	Agreed.
Revision of 0090	
		0172	Coding of NAS Binding Info field	24.008	Fujitsu	Revised to 211.
Related with 156.
Revision of 0123	
		0173	System Information	24.008	Ericsson/ Monica Wifvesson	Withdrawn

Revision of 0071	
		0191	PMMSMS-REL-Req deletion in MS side	24.007	NTT Comware
Nobuyuki Uda	Agreed.	
		0192	Additions to draft stage 1.5 on CW and NDUB for Multicall		Ericsson/Zdravko Jukic	Noted.
Discussion	
		0200	Terminology clarifications in Selective Routing Area Update  procedure	24.008	Siemens AG/Roland Gruber	Provided for information, comments are invited.	
		0211	Coding of NAS Binding Info field	24.008	Fujitsu	Agreed.
Revision of 172	
							
6.4	MS Classmark		Functionally frozen for R99				
		0081	Proposal of Classmark 1, 2, and MS network capability for UMTS	24.008	Siemens/ Robert Zaus	Rejected.	

6.5	Security		Security will be studied task by task according to 30.810 and decision on the R99 vs. R00 will be made on individual task basis in TSGN #7.			Due to Security ad-hoc meeting in Darmstadt 10.-11.01.2000 security WI is proposed for early treatment in TSGN1 #10.	
		0041	UMTS security parameters, Handling of Ciphering algorithm IE in UMTS	24.008	Ericsson/ Lars Ekeroth	Agreed.
CR	
		0042	UMTS security parameters, Correction of format for IE “Response from SIM”	24.008	Ericsson/ Lars Ekeroth	Agreed.
CR	
		0043	UMTS security parameters, Combined reject causes for CS and PS	24.008	Ericsson/ Lars Ekeroth	Revised to 186.
CR	
		0069	Clarifications on the MM and GMM Authentication procedures	24.008	Ericsson/ Monica Wifvesson	Revised to 0187.

CR	
		0070	Authentication Reject from MS	24.008	Ericsson/ Monica Wifvesson	Revised to 0188.

CR	
		0095	Amendments to L3 signalling to ensure integrity protection	24.008	Vodafone / Duncan Mills	Revised 0183.
The expected MS MM behaviour needs to be defined.
Some of the reject messages should be considered for integrity checking as well. (LU Rej. may cause a PLMN selection)	
		0109	Introduction of a new codepoint within the mobile identity IE, encrypted IMSI	24.008	T-Mobil	Postponed. Wait for reply to 0178
CR	
		0134	Alignment of the procedure “Authentication not accepted by the MS” in MM and GMM.	24.008	NTT Software/ Takeshi Igarashi	Revised to 0189.
Old reference version, the CR should be based on v. 3.2.1.	
		0147	Introduction of the encrypted IMSI	23.003	T-Mobil/Jacobsohn	Withdrawn	
		0183	Amendments to L3 signalling to ensure integrity protection	24.008	Vodafone / Duncan Mills	Withdrawn.
Revision of 0095.	
		0186	UMTS security parameters, Combined reject causes for CS and PS	24.008	Ericsson/ Lars Ekeroth	Agreed.
Revision of 0043	
		0187	Clarifications on the MM and GMM Authentication procedures	24.008	Ericsson/ Monica Wifvesson	Rejected.

Revision of 0069.	
		0188	Authentication Reject from MS	24.008	Ericsson/ Monica Wifvesson	Agreed.

Revision of 0070.	
		0189	Alignment of the procedure “Authentication not accepted by the MS” in MM and GMM.	24.008	NTT Software/ Takeshi Igarashi	Agreed.

Revision of 0134	
							
6.6	QoS		Functionally frozen for R99				
		0087	Abnormal cases for TFT handling, TFT IE maximum length	24.008	Ericsson	Revised to 0184	
		0088	Compact coding of QoS IE	24.008	Ericsson	Rejected.
CR	
		0184	Abnormal cases for TFT handling, TFT IE maximum length	24.008	Ericsson	Agreed.
Revision of 0087	

							
6.7	Out-of-Band Transcoder Control		Functionally frozen for R99				
		0033	Comments on Tdoc N1-99F40: Transport of Codec Information	24.008, (25.413 25.331)	Siemens/ Robert Zaus	Noted.

Discussion	
		0111	Transport of Codec Information	24.008	Ericsson/ Rouzbeh Farhoumand	Noted.	
		0112	BC enhancements to cover UMTS AMR speech codec and codec negotiation procedures	24.008	Ericsson/ Rouzbeh Farhoumand	Rejected.
	
		0113	New MAP procedure to enable negotiation of codecs & Transcoder control between MSC’s	29.002	Ericsson	Discussion document provided for information to collect comments before the next N2 meeting.	
		0139	Clarification of related works for Out of Band Transcoder Control in N1		DoCoMo/ koshimizu	Noted.	
		0140	Down Link Message for transport codec  information ( CC vs RRC)		DoCoMo/ koshimizu	Noted.	
		0141	Solution to the problem of inter MSC handover pointed by Siemens		DoCoMo/ koshimizu	Noted.
Discussion document, comments to tdoc 0163.	
		0142	Clarification of CODEC and TRANSCODER location		DoCoMo/ koshimizu	Noted.
Discussion document, comments on Ericsson proposal.	
		0143	Information Element for the Codec Negotiation		DoCoMo/ koshimizu	Noted.
Discussion.	
		0144	Clarification of Transcoder Setting		DoCoMo/ koshimizu	The proposed outgoing LS in tdoc 0193.
Discussion document. Proposal to send the figure in Annex A to N2, R2, R3 and S4 to inform our working assumption.	
		0145	Codec Selection at MSC (anchor vs target)		DoCoMo/ koshimizu	Noted.
Discussion.	
		0163	Outcome of the Informal Ad-hoc Session on Out-of-Band Transcoder Control	24.008
(25.413
25.331)
	Ericsson, NTTDoCoMo, Siemens/ Robert Zaus	•	The proposed working assumptions 1 – 4 were agreed.
•	New information element was agreed to be added to carry the information on the supported codecs in uplink direction.	
		0179	BC enhancements to cover UMTS AMR speech codec and codec negotiation procedures	24.008	NTT DoCoMo	Revised to 0190.
	
		0180	Explanation of Future Proof of by using BC IE for Codec information Transport		NTT DoCoMo	Noted.	
		0181	Inter MSC handover		NTT DoCoMo	Noted.
Discussion.	
		0190	BC enhancements to cover UMTS AMR speech codec and codec negotiation procedures	24.008	NTT DoCoMo	Withdrawn
Postponed, decide this together with 0112.
This is alternative approach to 0112.
Revision of 0179.	

6.8	CC related Items		NOTE: Agenda item, not a work item. Please consider the WI on your CR!			Chairman to draft the following liaison statement tdoc N1-000212 to S1:
•	N1 is not able to decide on emergency calls 
•	Provide both concepts for S1 to decide which one is more important in this tradeoff, support of roaming or flexibility to define operator specific emergency numbers.
•	S1 have made stage 1 requirement to encode the Called Party BCD number in Emergency Setup.
•	This requires that in roaming cases the visited MSC needs to know the emergency service numbers of the subscribers HPLMN or otherwise the emergency call must be routed to default emergency service in roaming case.
•	Emergency calls may be routed incorrectly if the serving visited MSC recognises the requested emergency number but has a different meaning for it than the subscribers HPLMN.
•	Do the service requirements cover also roaming case or should emergency calls in VPLMN be routed to default emergency center?
•	An alternative proposal has been presented in N1 but also this one could not be agreed.
•	The alternative proposal would standardise the emergency services and thus enable the support of the specified emergency services, if available, also in roaming cases.
•	Only the specified emergency categories can be used by the operators in this competing proposal.	
		0038	Addition of called party BCD number in Emergency SETUP message	24.008	NEC/ Hiroki Nakamura	Noted.
Proposal to add emergency centre Called Party BCD number to Emergency Setup to distinguish between different emergency calls.
Discussion	
		0039	Addition of called party BCD number in Emergency SETUP message	24.008	NEC/ Hiroki Nakamura	Rejected.
CR (WI:PCS 1900 Harmonization)	
		0115	Emergency call handling		Ericsson	Noted.
Proposal to add emergency call type to Emergency to distinguish between different emergency calls.
Discussion, linked with 0116.	
		0116	Emergency Call additions	24.008	Ericsson	Rejected.
CR, linked with 0115	
		0204	Time-plan for the category method		Ericsson/ Rouzbeh Farhoumand	Noted.	
		0206	Additional explanation for Emergency Setup procedure and routing	24.008	NEC /YAHAGI	Noted.	

6.9	R99 packet data		NOTE: Agenda item, not a work item. Please consider the WI on your CR!				
		0034	Extended Transaction Identifier	24.008	Siemens AG/ Robert Zaus	Rejected.
But the problem does not go away, we need to change either the error handling in 24.008 or the coding of the TI in 24.007.	
							
6.10	Other R99 Issues		NOTE: Agenda item, not a work item. Please consider the WI on your CR!				
		0055	Link Adaptation for ECSD	23.034	Ericsson	Withdrawn
WI:EDGE	
		0056	Modifications to Stage 2 service description due to EDGE	23.034	Nokia	Withdrawn
WI:EDGE	
		0114	GSM Cleanup – Removal of V.23	24.008	Ericsson	Agreed. For submission to TSGN #7.
WI:TEI	
		0151	Network Selection	22.011	S1	For Information. Noted. Comments in LS in tdoc 
WI:S1 do not specify any...
Linked with 0049 and 0118.	
		0133	Modifications to Stage 2 service description due to EDGE	23.034	Nokia/Janne Muhonen	Revised to 0177
WI:EDGE	
		0175	New version of 23.171, v1.1.0	23.171	Nokia/Janne Muhonen	Noted. 
For Information, WI: LCS	
		0176	Stage 2 Functional Specification of Location Services in UTRAN (3G TS 25.305 version 3.0.0)	25.305	Nortel Networks/ Sonia Doshi	Noted.

For Information, WI: LCS	
		0177	Modifications to Stage 2 service description due to EDGE	23.034	Nokia/Janne Muhonen	Agreed.For submission to TSGN #7.
CR, WI: EDGE
Revision of 0133.	
							
7	Release 2000						
7.1	New R2000 Work Item proposals		Can we define a packet WI for R2000 issues, i.e.is there going to be leftovers after GPRS, QoS and GSM – UMTS interworking?				

							
7.2	L3 Segmentation						

							
7.3	Turbocharger						

							
8	Output Liaison Statements						
		0110	Draft response Liaison Statement on usage of RANAP over MAP/E i/f for UMTS to UMTS inter-MSC SRNS relocation		Ericsson, NTT Docomo, Nortel	Rejected.
Response to S2-99F02 on "UMTS inter-MSC SRNS Relocation"
Proposed reply to 0026.
	
		0135	reply to LS on usage of NSAPI, RB identity, RAB ID and TEID		Uda san	Agreed.
Reply to 0015.	
		0136	Proposed response to Liaison statement concerning HSCSD specifications		Janne	Agreed. Contact details to be added.
Reply to 0017.	
		0137	SAT Handover notification and termination of  call		Hannu	Revised to 182.
Reply to 0018.	
		0138	Proposed Response Liaison Statement on Usage of RANAP over MAP/E i/f for UMTS to UMTS Inter-MSC SRNS Relocation		Rouzbeh	Contact person needs to be added.

Reply to 0026.	
		0149	LS on questions on the CR 10r1 to TS 23.107		Roland	Agreed. Contact details to be added.
Reply to 0027.	
		0150	LS on Enhanced User Identity Confidentiality – open questions		Dieter	Revised to 0178
Reply to 0029.	
		0152	Proposed response to LS on RAB linking		Richard	Agreed.
Reply to 0051.	
		0153	Proposed response to LS on Capability configuration parameters		Mark	Agreed.
Reply to 0117.	
		0155	Reply to LS on Requirements for Network Selection		Roland	Revised to 201
Reply to 0049 covering also 0118.	
		0164	Proposed LS to RAN 2, RAN 3, on the Transport of Codec Information during the Codec Negotiation between MS and MSC	24.008
(25.413
25.331)
	Siemens/ Robert Zaus	Agreed. Contact details to be added.	
		0170	Proposed LS on removal of Anonymous Access from Release 97 and 98		Roland	Agreed. Contact details to be agreed.
Related with CRs 0084 and 0085	
		0178	LS on Enhanced User Identity Confidentiality – open questions		Dieter	Revised to 202. Contact person to be added
Revision of 0150	
		0182	SAT Handover notification and termination of  call		Hannu	Agreed.
Revision of 0137.	
		0193	Draft LS on Iu Userplane Initialization at Inter  MSC-HO		Koshimizu san	Agreed.	
		0199	Draft response Liaison Statement on usage of RANAP over MAP/E i/f for UMTS to UMTS inter-MSC SRNS relocation		Siemens	Noted.	
		0201	Reply to LS on Requirements for Network Selection		Roland	Agreed.
The document number on the document needs to be corrected.
Revision of 0155, reply to 0049.	
		0202	LS on Enhanced User Identity Confidentiality – open questions		Dieter	Agreed.
Revision of 178.	
		0205	Response LS on on partial SRNS relocation		Ericsson/ Rouzbeh Farhoumand	Agreed.
Contact person needs to be added.	
		0209	LS to reply 209		Hannu	Agreed, chairman to provide the document after the meeting.
Reply to 0208.	
		0212	LS on emergency calls 		Hannu	Agreed, the chairman to provide the document after the meeting.	
							
9	A.O.B.						
		0213	Memories from Abiko			For information