Agenda item	Agenda item title	Tdoc 3GPP N2?00	Document Title	Source	S
W
G	Result	
1	Opening, approval of agenda	-0001	3GPP TSG-N WG2, Kyoto, Japan, 17 – 21 January 2000: Proposed meeting agenda	N2 Chairman	P	Agreed with amendment that SPAN3 will meet on Tuesday and Wednesday.	
2	Document allocation	-0002	3GPP TSG-N WG2, Kyoto, Japan, 17 – 21 January 2000: Proposed allocation of documents to agenda items	N2 Chairman	P	Approved (after many additions/changes). For output LSs it will be necessary to indicate name and information of contact person to speed up delivery and consideration	
3	Review of reports of previous meetings						
3.1	N2, Phoenix	-0003	Meeting report of 3GPP TSG-N WG2, Phoenix, AZ, USA, 15 – 19 November 1999	MCC	P	Noted	
3.2	CN plenary, Nice	-0006	Summary report on CN plenary meeting number 6, Nice, 13 – 15 December 1999	N2 Chairman	P	Noted	
3.3	S3/N2 security ad hoc, Darmstadt	-0007	Summary report on ad hoc meeting of S3 with N2 experts on outstanding security issues for UMTS R99, Darmstadt, 10 ‑ 11 January 2000	N2 Chairman	P	Noted	
3.4	MNP ad/hoc		Report of the MNP ad/hoc meeting of experts 12 Madrid 2000	MCC	P	Postponed for treatment in N2B.	
4	Input liaison statements: allocation to subgroups	A0067	Response Liaison Statement on Active Location Retrieval in CAMEL Ph 3	N1	P	To N2A	
		A0068	LS on the Prioritisation of VHE Service Capability Features	S1	P	To N2A	
		B0005	LS on location and control of speech codec	S2	P	To N2B	
		B0006	Proposed answer Liaison Statement to SA WG2 on "Basic principles of QoS interoperation	S2	P	To N2B	
		B0007	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)	S1	P	To N2B	
		B0020	LS on TrFO, Codec List and TFO Status	S4	P	To N2B	
		B0021	LS on Emergency calls using IMEI as UE identifier	N1	P	To N2B	
		B0022	LS on Common Communication Mechanism to be used by the Cell Broadcast Service	R3	P	To N2B. Sent in copy to N2, although the text indicates that we should take some action. An LS in response will be drafted by Ericsson	
		B0023	LS on usage of NSAPI, RB identity, RAB ID and TEID	R3	P	To N2B	
		B0024	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)”	S1	P	To N2B	
		B0025	LS on usage of NSAPI, RB identity, RAB ID and TEID	S2	P	To N2B	
		B0026	Liaison statement to N1 and N2 concerning QoS parameter mapping between R97/98 and R99	S2	P	To N2B	
		B0027	Liaison Statement on the concern about the definition of the Service Area identity	S2	P	Investigation on the RANAP Protocol Spec to find a definition of SAI and SAC will be performed by NTT Comware. CR 23.003 needed to incorporate such definition (see Tdoc 0121) Then changes can be drafted to MAP, CAP and GTP. 	
		B0028	Liaison Statement on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	S2	P	To N2B	
		B0029	Liaison Statement on CDR creation for non-charging liable subscriptions	S2	P	To N2B	
		B0030	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	P	To N2B	
		B0031	Liaison statement on the application of IST to emergency calls	SMG10 and S3	P	To N2B	
		B0032	Response to Liaison statement from TSG-CN2 on Required Super-charger Enhancements	T1	P	To N2B	
		B0033	Response to liaison statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture	T2/SWG1 (MExE)	P	To N2B	
		B0034	LS on Information on Common Communication Mechanism to be used by the Cell Broadcast Service	T2	P	To N2B	
		B0070	Liaison Statement concerning Transcoder Free operation	S2	P	To N2B	
		B0071	Answer to liaison statement from N2 regarding the establishment of a QoS taskforce	S2	P	To N2B	
5	Work item management	-0004	Handling of ETSI Public comments on Draft ETSI EN 301 668-1 V1.1.1 (1999-07)	Alcatel	P	Protocol spec derived from GSM 09.78 for CAMEL phase 2, presented as a delta against ETSI INAP CS-1. Recommendation is to have a formal public enquiry resolution meeting to be conducted during March 27-31. Accepted by the SPAN3 Chairman. This shall be confirmed by the joint N2A/SPAN3 group.	
		-0005	Handling of ETSI Public comments on Draft ETSI EN 301 668-2 V1.1.1 (1999-07)	Alcatel	P	This is the PICS proforma derived from GSM 09.78 for CAMEL phase 2, presented as a delta against ETSI INAP CS-1. The PE resolution meeting shall be conducted during March 27-31. Accepted by the SPAN3 Chairman. This shall be confirmed by the joint N2A/SPAN3 group.	
		A0070	Requirements for finalising the content of CAMEL Phase 3	N & N2 Chairmen	A 	(Presented in the plenary.) Issues not in the list provided with the contribution should not be considered by N2A unless N2A has nothing else left to do for the items included in the list. Noted for guidance for N2A discussions.	
		B0001	Towards the completion of the GLR specifications	NTT DoCoMo	B	(Presented in the plenary.) Clarification that there is no open issue with regard to interaction with CCBS. The conclusions in this document were accepted. The technical documents referred to in B0001 are to be dealt with in N2B.	
		B0039	Coordination plan to complete Multicall in R99 (Ver.1)	NTT DoCoMo	B	Clarified that the top portion of the excel file is in line with the agreement of the WGs chairmen. Modifications to the bottom section are necessary because S1 has not clarified the Multicall concept. Although S1 has not resolved the open issues they are responsible for, N2 should continue with activities relevant to our group.
Email discussion should take place on SS-ad-hoc exploder in order to concentrate the discussion in a single place.
The host for the N2B ad-hoc was unable to also host the Multicall ad-hoc. It may be possible, however, to have the N2B ad-hoc moved to Sophia Antipolis. It was agreed to attempt to move the N2B ad-hoc to Sophia Antipolis. 
AP Ian (disclosed): Send an urgent email to Franco as soon as he returns to his hotel room in order to see if this can be accomplished. No strong arguments against the meeting in Milan
(Refer to B0040 for final discussion.)	
		B0040	Multicall basic concept	NTT DoCoMo	B	Discussed in parallel to B0039 and B0090.
Clarification of the term “Network Environment” was addressed. It was stated that “providing multiple bearers” is an example of a “Network Environment.” A better name for this, however, seems “Network Capability” rather than “Network Environment.”
Should Multicall be considered as a network-function or a supplementary service? Ericsson argued that Multicall is not a basic service, so it must be a supplementary service.
France Telecom pointed out that Multicall is a subscribe-able service that may not be available to all subscribers: this implies that it should be a supplementary service rather than a network function. Also, there is already a model defined for user interaction that can be reused for Multicall.
Vodafone said they do not care about name as long as in the end the feature works. Ericsson agreed that the most important issue is that this is completed in such a way that there is no need for major changes after the release and found it as essential to offer the subscriber the option to control the subscription data for multicall.
It was agreed that, for the purpose of producing specifications, N2B should treat Multicall as a supplementary service. This does not mean that Multicall actually needs to be a supplementary service. (In other words, SS specs would be used as a model for creating the specs for Multicall.) The work will stay with N2B and not be transferred to the SS ad-hoc.	
		B0076	Finalising R99 Work	NTT DoCoMo	P	Proposes a methodology to determine which work to concentrate on until TSG plenaries in March: those features, which SA#6 identified as part of R99 plus essential fixes. Principles were endorsed. Nokia asked whether similar rules were proposed at the N1 meeting last week; it wasn't, but it will be done at the next meeting in February. NTT DoCoMo pointed out that N2 should recommend whether extend timescales or defer to R2000, with items which are not resolved at CN #7: this was accepted. Principles endorsed by N2. Care should be taken when presenting output to CN plenary to clarify which items could not be resolved and whether they should be considered “non essential."	
		B0090	Time plan for Multicall	LM Ericcson	B	Presented at the same time as B0039 in order to reach a common agreement of the two documents. Proposes to press in S1 to clarify the stage 1 requirement, but Ericsson clarified that some work can be done this week, in advance of the clarification by S1. NTT DoCoMo pointed out that the time plan assumes a particular definition of what Multicall is (basic service/supplementary service/network feature); this issue is raised in B0040.
(Refer to B0040 for final discussion.)	
		B0075	Working plan to complete OoBTC in R99	NTT DoCoMo	B	No questions for clarification. 
Some members felt that this time frame may be too ambitious. Open issues should be resolved using the time scale presented in the document. The target date for the OoBTC Stage 2 should be the 14-16 February N2B meeting.
From the contribution:
-	N2 clarifies the requirement of the Inter MSC link, which type of bearer can be applied.
NEC indicated that the current Stage 2 relies on the capabilities of BICC, therefore this is not an open issue for N2. This issue depends on what is defined in the ITU document, not on this Stage 2 document. Discussion of this issue was deferred to the later documents on OoBTC.
It was asked whether there be any other open issues not addressed in this contribution. There were no open issues identified that need to be added to this particular contribution.	

6	Release 99						
6.1	CAMEL Phase 3						
6.1.1	Input liaison statements	A0067	Response Liaison Statement on Active Location Retrieval in CAMEL Ph 3	N1	A	See N2A report	
		A0068	LS on the Prioritisation of VHE Service Capability Features	S1	A	See N2A report	
		A0070	Requirements for finalising the content of CAMEL Phase 3	N & N2 Chairmen	A	See N2A report	
		A0094	CAMEL3/CAMEL4 stage 1 separation of features	Nokia	A	See N2A report	
6.1.2	Stage 2	A0002	CR 23.018-A028 on User Interaction in Monitoring State	Ericsson	A	Also to N2B. Revised to A0113 by adding handling of ETC or CTR after answer. Nokia wanted to remove the handling for all states except Wait_For_Clear; agreed. Ericsson also pointed out that it would be a network operator option whether to hold the B party while the user interaction takes place or to keep the B party connected. Alcatel also wanted to eliminate the option so that N2 do not have to undo it for R2000. This will be specified in 23.078! Revised version will be sent to N2B in Milan.	
		A0003	CR 23.078-034 on Correction to some SDLs in chapter 4	Vodafone Airtouch	A	See N2A report.	
		A0004	CR 23.078-035 on Correction of Translation Information Flag in the VLR for DTN	Vodafone Airtouch	A	See N2A report.	
		A0005	CR 23.078-036 on Call Completion Treatment Indicator	Vodafone Airtouch	A	See N2A report.	
		A0006	CR 23.078-037 on Clarification on CUG handling	Vodafone Airtouch	A	See N2A report.	
		A0007	CR 23.078-038 on Clarification of SS Invocation Notification	Vodafone Airtouch	A	See N2A report.	
		A0008	CR 23.078-039 on Alignment of Chapters 10 and 11	Vodafone Airtouch	A	See N2A report.	
		A0009	CR 23.078-040 on Correction of SS Invocation Notification for CCBS	Vodafone Airtouch	A	See N2A report.	
		A0012	CR 23.078-041 on Introduction of call gapping	France Télécom	A	See N2A report.	
		A0014	CR 23.078-042 on Technical and editorial corrections to ATSI, ATM, NCSD	Ericsson	A	See N2A report.	
		A0015	CR 23.078-043 on Technical and editorial corrections to Location Services and Any Time Interrogation	Ericsson	A	See N2A report.	
		A0016	CR 23.078-044 on Technical and editorial corrections to circuit switched call handling	Ericsson	A	See N2A report.	
		A0017	CR 23.078-045 on Technical and editorial corrections to USSD	Ericsson	A	See N2A report.	
		A0018	CR 23.078-046 on Technical and editorial corrections to GPRS	Ericsson	A	See N2A report.	
		A0019	CR 23.078-047 on Technical and editorial corrections to SMS	Ericsson	A	See N2A report.	
		A0020	CR 23.078-048 on Inclusion of O-CSI trigger criteria in Resume Call Handling	Ericsson	A	See N2A report.	
		A0024	CR 23.008-012 on Introduction of 'Notification to CSE flag' to ODB	NTT Commware	A	Also to N2B; revised in A0105	
		A0025	CR 23.082-003 on Introduction of 'Notification to CSE flag' to CF	NTT Commware	A	Rev in A0106	
		A0026	CR 23.088-001 on Introduction of 'Notification to CSE flag' to CB	NTT Commware	A	Rev in A0107	
		A0027	CR 23.078-049 on AnyTimeSubscriptionInterrogation operation and AnyTimeModification operation.	NTT Commware	A	Rev in A0108	
		A0028	CR 23.078-o50 on Addition to SDL of user interaction in Waiting_for_Instructions_for_DS	NTT DoCoMo, NEC	A	See N2A report.	
		A0029	CR 23.078-051 on Correction of SDL related CAMEL Phase3 for D-CSI	NEC	A	See N2A report.	
		A0030	CR 23.078-052 on Addition to description of D-CSI in MO Calls	NEC	A	See N2A report.	
		A0031	CR 23.078-053 on Addition to description of SDL related to CAMEL Phase3	NEC	A	See N2A report.	
		A0032	CR 23.078-054 on Dialled services - clarification on different SSFs	Nokia	A	See N2A report.	
		A0033	CR 23.078-055 on Reporting of T_Busy when absent subscriber	Nokia	A	See N2A report.	
		A0035	CR 23.078-056 on GPRS interworking to reduced number of TCAP dialogues	Nokia	A	See N2A report.	
		A0037	CR 23.018-031 on Transmission of CSIs to GMSC from the HLR(SRI-ack)&VMSC(RCH)	Nokia	A	Withdrawn.	
		A0038	CR 23.078-057 on Transmission of CSIs to GMSC from the HLR(SRI-ack)&VMSC(RCH)	Nokia	A	See N2A report.	
		A0056	CR 23.078-058 on CCBS treatment indicator to Forw OBCSM and gateway BSCMs	Nokia	A	See N2A report.	
		A0058	Notification control on ODB	NTT Commware	A	See N2A report.	
		A0059	CR 23.078-059 on Addition of  gsmSRF disconnect handling in CCF SDL	NTT DoCoMo	A	See N2A report.	
		A0060	CR 23.078-059 on Correction of gsmSSF SDL in Wait_For_Request state	NTT DoCoMo	A	See N2A report.	
		A0061	CR 23.078-059 on Addition of SCI handling in Waiting for Instructions For DS state	NTT DoCoMo	A	See N2A report.	
		A0062	CR 23.078-059 on Correction of SDL and IF for Dialled Service in Call Forwarding	NTT DoCoMo	A	See N2A report.	
		A0063	CR 23.018-032 on Inclusion of D-CSI/N-CSI check in HLR/VLR	NTT DoCoMo	A	Also to N2B. Revised to A0149	
		A0069	Clarification of N-CSI in Core NW	NTT DoCoMo	A	See N2A report.	
		A0071	CR 23.018-033 on Initialisation of Backward Call indicator	Siemens	A	(Moved to plenary.) Problem also exists for R97 and R98 but correction presented only for R99. CR endorsed by N2 plenary. No further discussion in N2A or N2B no needed. Will be submitted as a R99 correction to CN#7.	
		A0072	CR 23.018-034 on Correction of the result of the procedure CAMEL_ICH_MSC_INIT	Siemens	A	Endorsed by N2B.	
		A0073	CR 23.078-064 on Addition of Connected number treatment indicator	Siemens	A	See N2A report.	
		A0074	CR 23.078-065 on Addition of D-CSI in Insert Subscriber Data information flow	Siemens	A	See N2A report.	
		A0075	CR 23.078-066 on Addition of Int_Error in DP_O/T_Answer states	Siemens	A	See N2A report.	
		A0076	CR 23.078-067 on Addtion of ‘Start Tccd’ in the procedure Handle_ACR	Siemens	A	See N2A report.	
		A0077	CR 23.078-068 on Correction of the decision box after receiving Int_DP_O_Answer and Int_DP_T_Answer in the procedure gsmSSF	Siemens	A	See N2A report.	
		A0078	CR 23.078-069 on Correction of the description in the creation of a new leg in CF	Siemens	A	See N2A report.	
		A0079	CR 23.078-070 on Correction of the description of BCSM relationships	Siemens	A	See N2A report.	
		A0080	CR 23.078-071 on Correction of the direction of Int_Continue after sending Int_T-Abandon (additional CR to 23.078-033)	Siemens	A	See N2A report.	
		A0081	CR 23.078-072 on Corrections of the process gsmSSF	Siemens	A	See N2A report.	
		A0082	CR 23.078-073 on Editorial changes for legs	Siemens	A	See N2A report.	
		A0083	CR 23.078-074 on Explicit treatment of Int_Continue_with_Argument	Siemens	A	See N2A report.	
		A0084	CR 23.078-075 on Evaluation of D-CSI in ORLCF	Siemens	A	See N2A report.	
		A0085	CR 23.078-076 on Extension of the description of the O_No_Answer	Siemens	A	See N2A report.	
		A0086	CR 23.078-077 on gsmSSF DP handling in CF	Siemens	A	See N2A report.	
		A0087	CR 23.078-078 on Improvement the GPRS FSMs	Siemens	A	See N2A report.	
		A0088	CR 23.078-079 on Inclusion of Release transaction in CAMEL_OCH_MSC_INIT	Siemens	A	See N2A report.	
		A0091	Correction of CF Notification (collective CR to 03.78, 3.18, 3.79)	Siemens	A	Also to N2B. Aimed at correcting problem with indefinite looping for CAMEL controlled forwarding. In ORA3 the first test should be "Result=GSM_FTN?" In CAMEL_MT_GMSC_INIT, the 2 results "CAMEL_FTN & GSM_FTN need to be swapped. In ORA sheet 4, the RH exit from the test "Result?" should be "Reconnect".
Siemens put this forward as category C1 (essential correction) but Ericsson has reservations. Later withdrawn, so this set of CRs is accepted by N2 as category C1. Siemens will need to:
-	revise the 03.18 CR;
-	revise the 03.78 CR;
-	draft mirror CRs for R98 on 03.18, 03.78 & 03.79;
-	Draft mirror CRs on 23.018, 23.078 & 23.079 (non-trivial!)
The 03.79 & 23.079 CRs are approved by N2
The 03.18 & 23.018 CRs will go to N2B in Milan
The 03.78 & 23.078 CRs will go to the N2A ad hoc.
Noted that the CRs should all have the same reason for change: to cure a problem with indefinite looping for forwarded calls subject to CAMEL control.	
		A0096	CR 23.078-081 on Improved SDLs in GPRS interworking	Siemens	A	See N2A report	
		A0097	CR 23.078-082 on Correction of the description of the SGSN	Siemens	A	See N2A report.	
		A0098	CR 23.078-083 on Correction of gsmSSF on O/D/N-CSI triggering	Alcatel	A	See N2A report.	
		A0099	CR 23.078-084 on Correction of references occurring in the SDL figures	Alcatel	A	See N2A report.	
		A0100	CR 23.078-085 on Inclusion of CAMEL Phase 1 procedures as targets for references in 3G TS 23.018	Vodafone Airtouch	A	See N2A report.	
		A0101	CR 23.078-086 on modelling of unsuccessful DPs	Alcatel	A	See N2A report.	
		A0102	CR 23.078-087 on Called Party Number at DP_analysed information or in case of unsuccessful DPs	Alcatel	A	See N2A report.	
		A0103	CR 23.078-088 on alignment of O_BCSM and T_BCSM picture with CAMEL phase2	Alcatel	A	See N2A report	
		A0104	CR 23.078-089 on Correction of Dialled service triggering criteria	NTT DoCoMo	A	See N2A report.	
		A0105	CR 23.008-012r1 on Introduction of 'Notification to CSE flag' to ODB	NTT Commware	A	Revision of A0024; also to N2B. Revised to A0128 (which was endorsed with changes to the)	
		A0106	CR 23.082-003r1 on Introduction of 'Notification to CSE flag' to CF	NTT Commware	A	Revision of A0027	
		A0107	CR 23.088-001r1 on Introduction of 'Notification to CSE flag' to CB	NTT Commware	A	Revision of A0026	
		A0108	CR 23.078 049r1 on AnyTimeSubscriptionInterrogation operation and AnyTimeModification operation.	NTT Commware	A	Revision of A0027	
6.1.3	Stage 3	A0010	CR 29.078-014 on Correction of SII2 description, to align with stage 2	Vodafone Airtouch	A	See N2A report.	
		A0011	CR 29.002-079 on Correction of SS Invocation Notification for CCBS	Vodafone Airtouch	A	Also to N2B. Revised to A0145.	
		A0013	CR 29.078-015 on Introduction of call gapping	France Télécom	A	See N2A report.	
		A0021	CR 29.078-016 on General technical and editorial corrections	Ericsson	A	See N2A report.	
		A0022	CR 29.002-082 on Inclusion of O-CSI trigger criteria in Resume Call Handling	Ericsson	A	Also to N2B, identifies the need for the service description to be updated, as well as the ASN.1. Revised version may come tomorrow, or to Milan. Endorsed by N2A	
		A0023	CR 29.002-080 on Corrections to ATSI, ATM, NCSD	Ericsson	A	Also to N2B	
		A0034	CR 29.078-017 on SMS related stage 3 issues	Nokia	A	See N2A report	
		A0036	CR 29.078-018 on Corrections to GSRS related ASN.1 definitions and TCAP dialogues	Nokia	A	See N2A report.	
		A0039	CR 29.002-081 on Transmission of CSIs to GMSC from the HLR(SRI-ack)&VMSC(RCH)	Nokia	A	Withdrawn.	
		A0040	CR 29.078-019 on Clean up the clause 4.1.2 Example physical scenarios	Nokia	A	See N2A report	
		A0041	CR 29.078-020 on Clean up the clause 4.1.2 CAP protocol architecture	Nokia	A	See N2A report	
		A0042	CR 29.078-021 on Clean up the clause 4.1.3 CAP addressing	Nokia	A	See N2A report	
		A0043	CR 29.078-022 on Adding of the clause 'Definition And Usage Of LegID'	Nokia	A	See N2A report	
		A0044	CR 29.078-023 on Corrections to Compatibility mechanism	Nokia	A	See N2A report	
		A0045	CR 29.078-024 on Corrections to the clause 4.2 SACF/MACF rules	Nokia	A	See N2A report.	
		A0046	CR 29.078-025 on Correction to the FCI freeFormatData parameter	Nokia	A	See N2A report.	
		A0047	CR 29.078-026 on Corrections to the gsmSSF/gsmSCF related ASN.1s	Nokia	A	See N2A report.	
		A0048	CR 29.078-027 on Remove the PA and P&CUI connectedParty and Display Info	Nokia	A	See N2A report.	
		A0049	CR 29.078-028 on Correction of the CallInformationRequest arguments	Nokia	A	See N2A report.	
		A0050	CR 29.078-028 on Corrections to the 'MO SMS Control' related ASN.1s	Nokia	A	See N2A report.	
		A0051	CR 29.078-028 on Corrections to the clause 10 Error procedures	Nokia	A	See N2A report.	
		A0052	CR 29.078-028 on Adding of the ActivityTest to gsmSRF-gsmSCF AC	Nokia	A	See N2A report.	
		A0053	CR 29.078-028 on Corrections to the clause 11 operation procedure	Nokia	A	See N2A report.	
		A0054	CR 29.078-028 on Clean-up the clause 12 Services assumed ...	Nokia	A	See N2A report.	
		A0055	CR 29.078-028 on Connect and ContinueWithArgument CCBS treatment indicator	Nokia	A	See N2A report.	
		A0064	CR 29.078-035 on Correction of CAP and INAP compatibility	NTT DoCoMo	A	See N2A report.	
		A0065	CR 29.078-036 on ASN.1 notation of cause parameter	NTT DoCoMo	A	See N2A report.	
		A0066	CR 29.078-037 on Services assumed from SCCP	NTT DoCoMo	A	See N2A report.	
		A0089	CR 29.078-038 on Addition of Connected number treatment indicator	Siemens	A	See N2A report.	
		A0090	CR 29.078-039 on Collective changes in 29.078	Siemens	A	Doc list shows this as CR 040	
		A0093	CR 23.078-080 on CAMEL3 Stage 2 LocationNumber for IDP in MO calls	Nokia	A	Mirror of A0092	
		A0095	CR 29.078-040 on Specifying time unit for 'firstDigitTimeOut' and 'interDigitTimeOut'	Ericsson	A	See N2A report.	
		A0109	CR 29.002-088 on AnyTimeSubscriptionInterrogation operation and AnyTimeModification operation	NTT Commware	A	Also to N2B. Rejected in favour of A023.	
		A0145	CR 29.002-079r1 on Correction of SS Invocation Notification for CCBS	Vodafone AirTouch	A	Also to N2B. Will be reviewed for possible improvement and endorsement in N2B at Milan	
6.2	GPRS	B0004	CR 23.018-029 on Parallel handling of multiple PDP contexts	Ericsson Spain	B	Withdrawn	
		B0006	Proposed answer Liaison Statement to SA WG2 on "Basic principles of QoS interoperation	S2	B	Noted. No action from N2 needed.	
		B0007	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)	S1	B	This is already dealt with by CRs to 23.060. Noted.	
		B0011	CR 29.060-033 on Addition of Radio Priority to the MM Context and PDP Context IEs	Motorola Norway	B	This CR proposes to include the Radio Priority in the GSM MM Context and the PDP Context IE. Ericsson proposed to postpone this CR for further study, particularly in respect to the introduction of GSM specific information in the PDP Context IE, which is applicable to 2G and 3G. Postponed	
		B0012	CR 29.060-034 on Removal of redundant information from the PDP Context IE	Motorola Norway	B	Withdrawn	
		B0013	CR 29.060-035 on Addition of Packet Flow Id to the PDP Context IE	Motorola Norway	B	A question was raised if this addition is only applicable to 2nd generation networks. It was clarified that even though 23.060 is divided into 2G and 3G, 29.060 is not. This is the only location to place this Id. Revised in Tdoc B0099, as CR 29.060-A035r1.
Decision of this contribution postponed after offline discussion.	
		B0014	CR 29.060-036 on Change the attribution of the PDP Context IE	NEC	B	Text to be added to clarify the conditional aspect. Revised to B0095.	
		B0015	CR 29.060-037 on Add cause value	NEC	B	Agreed in N2B.	
		B0016	CR 29.060-038 on Addition of NSAPI to GGSN-initiated Update PDP Context	Fujitsu	B	Agreed in N2B.	
		B0026	LS to N1 and N2 concerning QoS parameter mapping between R97/98 and R99	S2	B	CR 23.107-001r3 was submitted as Tdoc B0106 (source S2). Noted.	
		B0030	LS 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	B	Noted. Ericsson kindly offered to prepare the necessary CR to TS 29.060 clarifying the terms relating to the naming of PDP Contexts activated using the PDP Context Activation and Secondary PDP Context Activation procedures. A review of the CR (Tdoc B0107) was postponed to the end of the meeting. A response to the LS will depend of the outcome of the CR.	
		B0037	CR 29.002-094 on QoS- Subscribed field enhancements	Siemens	B	This CR proposes to extend the Ext-QoS-Subscribed parameter from 15 to 16 octets to include the allocation/retention priority. Nokia noted that NTT drafted a similar CR in Tdoc B0081 proposing a parameter of 18 octets in length. Siemens clarified that NTT are proposing to include the original QoS-Subscribed parameter in the Ext-QoS-Subscribed. The QoS-Subscribed parameter is mandatory. N2B agreed that the Ext-QoS-Subscribed should be an extension to the QoS-Subscribed in the body of the message. It was proposed to add a comment to clarify how the Ext-QoS-Subscribed is populated. It was agreed to include the clarification in the ASN.1. This task was performed offline. The revision is presented in Tdoc B0108.	
		B0038	CR 29.060-039 on Alignments of Message Type value	NTT Software	B	Ericsson pointed out that Tdoc B0060 proposes similar changes and was presented instead. Consequently, Tdoc B0038 is
 Superseded by Tdoc B0060.	
		B0043	CR 29.060-051 on Ordering of repeated Information Elements in GTP for R'99	Nortel Networks	B	R99 mirror of B0042. Agreed	
		B0044	CR 29.060-040 on Improving charging efficiency	Nokia	B	Agreed. This CR proposes improvements to the charging efficiency by indicating in GTP the type of charging to be applied e.g. Pre-Paid, Hot Billing etc. Nokia clarified that these flags are set and only used by the HPLMN. Nortel Networks will check in TS 23.060 that the VPLMN is always required to send CDRs, regardless of the flags set.	
		B0045	CR 29.060-041 on Subscriber and equipment trace for PS domain	Nokia	B	A companion CR against TS 23.060 is to be presented to TSG-S2 next week. Companies were invited to track approval of this CR otherwise misalignment may occur between TS 23.060 and TS 29.060. Tdoc B0045 describes that the trace facility enables subscriber administration and network management to trace the activities of various entities when specific events occur within the PLMN. The facility may be used for subscriber observation, e.g. following a customer complaint, or suspicion of equipment malfunction by the operator, or at the request of the police. According to TS 29.002, trace information is sent at trace activation from the HLR to the SGSN. Specifically to enable GGSN trace, this CR proposed that the SGSN should send the trace information to the GGSN. The trace information is sent in the Create PDP Context Request or in the Update PDP Context Request from the SGSN to the GGSN.
NEC requested clarification as to whether Trace is considered to be a 3G feature. GSM 12.08 describes Tracing but has not been transferred to 3GPP and does not incorporate applicability of the Trace feature to GPRS. The chairman proposed sending an LS to S5 pointing out this issue. Nokia will draft an LS to S5 (cc S2). This is captured in Tdoc B0109, "Trace specification for UMTS". The meeting accepted that Trace is applicable to 2G and 3G specs.
This CR was revised to Tdoc B0110, removing the word "Note" on pg. 5, and was approved without further presentation.	
		B0048	CR 29.060-042 on Necessity of the function of the calculation an SGSN IP address from the target ID	NTT Commware	B	This contribution proposes to include the possibility to use a logical name of the target Id to determine the appropriate SGSN IP address for the forward SRNS Relocation procedure. Agreed	
		B0049	CR 23.003-014 on Necessity of the function of the calculation an SGSN IP address from the target ID	NTT Commware	B	Agreed	
		B0050	CR 29.060-043 on QoS Profile IE modification	NTT Software	B	Revised to B0078	
		B0051	CR 29.060-044 on The addition of the conditional description of the GTP parameters	NTT Software	B	Revised to B0079	
		B0053	CR 29.002-085 on Ext-QoS-Subscribed modification	NTT Software	B	Revised to B0081	
		B0056	CR 29.060-057 on Removal of X.25	Ericsson Norway	B	This contribution proposes to remove X.25 as a possible backbone transport. Ericsson clarified that there had been some discussion as to whether TCP should also be removed since apparently it supports X.25. Individual companies are invited to pursue this issue. Agreed with editorial correction on cover.	
		B0057	CR 29.060-045 on Removal of Anonymous Access	Ericsson Norway	B	Requires editorial correction to cover sheet and inclusion of the message type identifiers as spare (reserved for future use) in sect. 7. It was considered inappropriate to draft companion CRs to R97 & R98 since these releases are frozen. It was further concluded that handover problems should not arise since Anonymous Access sessions are never handed-over. Revision prepared in Tdoc B0111 as CR 29.060-A45r1 and approved.	
		B0058	CR 29.060-046 on Authentication Clarification	Ericsson Norway	B	Identified correction:
•	Change figure 45 title from Security to Authentication
•	Highlight changes in figure 31 & 32
•	Update sentence above figure 31 to indicate that only the "value parts" are imported from GSM 04.08
•	Update subject on the front cover to reflect content of CR.
•	Change "presented" to "shall be present".
Revision prepared in Tdoc B0112 and approved without further review. CR 29.060-A046r1 with new title "Clarification of Authentication Type and Import of Parameters".	
		B0059	CR 29.060-047 on New relocation message	Ericsson Norway	B	Nortel Networks asked whether support for this message is optional or mandatory; Ericsson replied that it is mandatory if IuR is not provided. NEC believes it is not needed at all. Ericsson believes that the message is needed for hard handover when there is no Iur interface.
Postponed to Milan. Ericsson Norway has drafted an LS on Stage 2 description of hard handover (151). 	
		B0060	CR 29.060-048 on Clarification of Information Elements	Ericsson Norway	B	This CR corrects duplicate use of particular IE Type identifiers and re-orders the sections into TV and TLV sections. Approved.	
		B0061	CR 29.060-048 on Clarification of Information Elements	Ericsson Norway	B	Withdrawn. Never actually submitted to the meeting.	
		B0064	CR 29.060-050 on Protocol Type in GTP header	Ericsson Norway	B	NTT DoCoMo raised concern that GTP' is never used for the user plane. Revision drafted in B0119 as CR 29.060-050r1, clarifying that the Protocol Type is used to distinguish GTP from GTP' and that a value of '0' indicates GTP. Agreed without further presentation.	
		B0069	CR 29.002-090 on Improving GPRS charging efficiency	Nokia	B	It was agreed that the definition of the Charging Characteristic in sect. 7 should be removed since this is never referred to in the service primitives. The hyphen between charging and characteristic in the ASN.1 should also be removed. A revision was prepared in Tdoc B0113 and approved without further review.	
		B0072	CR 29.060-052 on Method for GTP extension headers support	Lucent Technologies	B	Update cover sheet to indicate functional modification. Ericsson and Nokia opposed the specification of the timer to block the sending of unsupported extensions and felt that the proposed solution to identify unsupported extension headers is over specification. Nortel Networks suggested use of negative logic by sending a cause, which indicates the extensions not supported. Postponed for further discussion.	
		B0078	20.060-043r1 on QoS Profile IE modification	NTT Software	B	Revision of B0050. Lucent Technologies proposed to remove the upper bound on the QoS profile. The intention is to make the GTP protocol more future proof. N2B agreed. Consequently, the only restriction on the QoS Profile length is the limitation of the encoding length of the QoS profile to 1 octet, namely 255. To avoid confusion, it was agreed to include the allocation/retention priority as the first octet of the QoS Profile. New text was proposed in subclause 7.7.6 between carry and the value in the first line reading "the allocation/retention priority octet, which is specified in TS 23.107, followed by". This was agreed.
The revision was presented in Tdoc B114.	
		B0079	CR 29.060-044r1 on The addition of the conditional description of the GTP parameters	NTT Software	B	Revision of B0051. It was agreed that when the Reordering Req'd parameter is not needed (i.e. when R99 QoS is being used) the receiving entity shall ignore this parameter. A revision was prepared in B0115 (by replacing "isn't used" with "shall be ignored by the sender") and approved without further presentation.	
		B0081	CR 29.002-085r1 on Ext-QoS-Subscribed modification	NTT Software	B	Revision of B0053: rejected. See Tdoc B0108.	
		B0082	CR 23.008-014 On addition of priority information to subscriber data	NTT Software	B	This CR concerns the addition of the allocation/retention priority for the CS-Domain. It was agreed to remove the second sentence in subclause 2.16.1 and clarify that the subscriber data describes the CS-domain. A revision was prepared in Tdoc B0116.	
		B0083	CR 23.016-011 On addition of priority information to subscriber data	NTT Software	B	This change request concerns the addition of the allocation/retention priority for the CS-Domain. Approved in principle but checks to be performed against v3.3.0 of the specification. A revision was rafted in Tdoc B 0117 and was approved without further presentation.	
		B0084	CR 29.060-054 on The addition of the description about the value of TEID	NTT Software		According to Lucent the role of TEID has been already specified sufficiently in 29.060, which makes the CR somehow redundant. The Chairman basically shared this concern. Ericsson remarked some good points in the CR principles, but clarifications in the text are also necessary. Postponed for further study and refinement.	
		B0085	CR 29.060-055 Addition of QoS parameter to PDU notification request	Cisco Systems	B	The Quality of Service Profile can be passed back to SGSN to indicate what type of resources needed for the network initiated service. SGSN can compare the network requested QoS with the user’s subscription data to determine if the PDP context activation is needed. Nokia clarified that S2 has not seen the companion stage 2 CR and that this will be presented next week.
It was requested that Cisco System prepare a CR against TS 23.107 to define a null vale for the Allocation/Retention Priority. This can subsequently be used when an Allocation/ Retention Priority is not required or the originator is not responsible for assigning the ARP.
Approved on the condition that the CR against TS 23.060 is approved by S2.	
		B0095	CR 29.060-036 on Change the attribution of the PDP Context IE	NEC	B	Revision of B0014. It clarifies the conditions for the presence of the PDP Context IE in the Forward Relocation Req. Approved	
		B0099	CR 29.060-035r1 on Addition of Packet Flow Id to the PDP Context IE	Ericsson	B	Postponed to check status of parameter in TS 23.060.	
		B0106	CR 23.107-001r3 concerning QoS parameter mapping between R97/98 and R99	S2	B	This is the attachment to Tdoc B0026. Noted. MAP and GTP are already believed to support the necessary capability.	
		B0107	CR 29.060-056 on Naming of primary and secondary contexts	Ericsson	B	Approved	
		B0109	Liaison Statement to S5 & S2 on Trace Specification for UMTS	Nokia	B	Change wording: CN2 believe appropriate to transfer GSM 12.08 to 3GPP and update it with GPRS and UMTS relevant information. Revised in Tdoc B0118 and approved without further review.	
		B0108	CR 29.002-094r1 on QoS- Subscribed field enhancements	Siemens	B	Revision of Tdoc B0037. The Allocation/Retention Priority is not defined in TS 23.107; instead it will be defined in TS 29.002. It was agreed to use binary encoding for this octet. Furthermore, the historical lower bound of 3 octets was reduced to 1 octet. Revised in Tdoc B0120 and approved without further review.	
		B0114	CR 29.060-043r2 on QoS Profile IE modification	NTT Software		As indicated by NTT DoCoMo, text at the beginning of 7.7.25 needs to be revised. Revised v3 in Tdoc 152. It was also agreed to strike out a sentence about pre release 99 QoS, since this version of the protocol does not carry a pre release 99 QoS in the same section. Lucent also observed that the number of necessary octets is more than currently specified. Consequently, too many revisions to handle it here. Postponed to Milan.	
6.3	Handover	B0024	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)”	S1	B	Already covered in the GPRS section (duplication of B007). Considered as withdrawn.	
		B0028	Liaison Statement on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	S2	B	Proposes to use RANAP encapsulated in MAP for inter-MSC handover. Usage of RANAP or BSSAP is out of the scope of N2. Nokia however observed that use of RANAP implies a lot of editing work on N2B side. Ericsson is prepared to the editing work, with a predictable time scale of 2 weeks, starting discussion soon. Discussion can be extended in Milan, in order to stabilise some conclusion for the next N2 plenary.
N2 should respond that we are not fully confident that changes can be delivered in time for CN#07	
		B0089	CR 29.010-003 UMTS / GSM Interworking	Ericsson	B	Introduction of two new chapters and some other changes. Due to a rather late submission, the Chairman identified the need for a more detailed review. RANAP experts, furthermore, should have a look at it. It would be prudent that also RAN3 reviews the CR. Ericsson will revise the CR for the next N2B meeting and will also draft an LS to R3.	
		B0125	Proposed Response LS on Usage of RANAP over MAP/E i/f for UMTS to UMTS Inter-MSC SRNS Relocation	N1	B	N1 see technical advantage in the use of RANAP. An LS will be drafted (N2B00126) by the Chairman in response.	
		B0124	Answer to liaison statement from N2 "LS on Open Issues on 3G to 2G Handover (packet Switched domain)"	S2	B	No action was proposed and the LS was noted.	
		B0126	Proposed LS to S2 on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	Vodafone AirTouch	B	Handled in plenary and approved	
		B0127	Proposed LS to RAN3 on interworking between RANAP and MAP	Ericsson	B	Handled in plenary and approved	
		B0151	Proposed LS to S2 on stage 2 description of hard handover	Ericsson	B	Handled in plenary and approved	
6.4	Location management: restructuring of specifications						
6.5	Multicall 	B0017	Draft Stage 1.5 for Multicall	NTT Commware	B	NTT DoCoMo stressed the need for very stable Stage 2 specification, in order to progress in the N2 context. An evening session of no more than one hour and a half was suggested, but Multicall is not the only hot issue to be discussed. A show of hands indicated a small participation from non-Japanese delegates. 
NTT Commmware will draft an LS to S1 (131).	
		B0093	Decision and comments on draft Stage 1.5 for Multicall in N1#10	NTT Commware		Noted	
		B0077	Toward Multicall Stage 2	NTT Commware	B	The Chairman, who recalled the importance assigned by regulators, especially in Europe, to this type of calls, stressed the importance of emergency calls in a multicall context. This is the only area in B77 that needs to be carefully studied (e.g., the HLR might instruct the mobile terminal to drop one of the calls in progress). The idea of offering a call as a waiting call, if the terminal is unable to accept it, was found interesting as well.
NTT DoCoMo wanted to deal in a separate CR with the requirement for the VLR to instruct the MSC to clear existing calls when it sends the Complete Call for an emergency call set-up, rather than covering this in the Multicall CR to 23.018. Japanese have concern that an emergency call should not produce a generalised call clearing. NEC pointed out that the current access signalling means that if the MS uses a stream identifier>1 (because it sends the emergency set-up when it has an existing call) to an MSC not capable of multicall, then the MSC will reject set-up and the emergency call will not work…
On the MT handling, it seems that the N1 proposal for not giving an indication in the classmark of the number of calls the MS can handle will cause us a lot of grief… N1 should be asked whether they are proposing to deal with this at the moment. This area was left inconclusive.
With the above mentioned exceptions the document can be accepted as the basis for the specification of Multicall Stage 2.	
		B0131	LS to S1 on service requirements for multicall	NTT Commware		Revised to 0152 and approved.	
		B0123	TS 22.125 Multicall Stage 1	S1		For information	
		Ad hoc session				The first problem identified in the N2B session concerned the handling of Emergency calls. The Chairman proposed a very simple approach: when an emergency call arrives, the VLR instructs the MSC to release all the calls in progress. Brutal, but simple and effective. Clearly, there is a parallel with the GSM case, where the MS is able to support one active call at a time (and if the user tries to set up a second call, the MS simply ignores it).
23.018 should cover the aspect properly, and a CR describing the behaviour in the presence of an emergency call should be drafted.
If the MS wishes to generate an emergency call and all resources are currently busy, the network can instruct the MS to release one traffic channel, i.e. what is needed to set up the emergency call.	
6.6	Multimedia calls						
6.7	Out-of-band transcoder control	B0003	Proposal to send a LS to R3 on Out of band Transcoder control	NTT DoCoMo	B	The LS requests R3 to study how the Iu user plane protocol can be used to control switch-in or switch-out of transcoders as the call configuration changes (e.g. set-up or collapse of multiparty). Nortel Networks asked whether this relies on the transcoders being located in the serving MSC; it does, so for transcoders in the GMSC core network protocols (this is Release 2000) need to be developed. Nortel Networks had doubt about whether it is N2's job to ask R3 to do this work. However NTT DoCoMo pointed out that the stage 2 is N2B's responsibility, & if N2 modify the stage 2 so that it requires work in R3, then the LS should be sent to them. NTT DoCoMo will draft the LS (B0132).	
		B0005	LS on location and control of speech codec	S2	B	Noted that the LS was originated rather long time ago. Nortel Networks observed that the LS was re-sent to N2 in B0070, which is then to be considered a superset of B0005.	
		B0020	LS on TrFO, Codec List and TFO Status	S4	B	Noted for the moment. An LS to S4 will be drafted during the Milan meeting.	
		B0054	Lack of information on mapping 3GPP CODEC type and Bearer attribution 	NEC	B	Withdrawn	
		B0070	LS concerning Transcoder Free operation	S2	B	The work done in N2 after drafting the original LS was not recognised, apparently. A list of issues has been sent us asking for clarification. NEC volunteered to draft an LS (B0133) that will cover N2B's conclusions: S2 has agreed to accept that for R99 the transcoder is located in the VMSC, for Release 2000 the location is FFS. S2 would also like that N2 considers interworking between GSM and UMTS as a study item. The response would be that transcoding occurs at the boundary between 2G and 3G networks.
Point 3: the ITU-T work on BICC is functionally stable.
Point 4: we have already discussed the impact of S2 work with N1 and S4. A third interested group, R3, has been also identified (Nortel Networks) and a dialogue will be set up with them as well.	
		B0096	New procedure for the allocation of the transcoder	NTT DoCoMo		Nortel observed that a revision to OoBTC would be needed if the principles of the document are accepted and even if requested more time to study the proposal, accepted that an LS to R3 is sent out. NTT DoCoMo will draft it (Tdoc B0131).
The Chairman suggested that the closing date for comments by e-mail is the 4th of February (12:00 UTC)	
		B0091	Clarification of the OoBTC Stage 2	Nortel Networks	B	Presented in detail. More discussion seems to be needed and e-mail discussion with deadline February 4th 12:00 UTC was agreed.	
		B0140	The additional case of TrFO break	NTT DoCoMo	B	NEC declared to be happy with the principles of the document, so comments are expected again by e-mail, same deadline as above.	
		B0132	Proposed Liaison statement to R3 on OoBTC	NTT DoCoMo	B	Handled in plenary and Revised to N2-000012	
		B0133	Proposed Liaison statement to S2 on Transcoder Free operation	NEC	B	Handled in plenary.	
6.8	Security issues	B0031	Liaison Statement on the application of IST to emergency calls	SMG10 and S3	B	S3 has decided not to follow N2B recommendation on Emergency Calls but to go their way. The LS was noted.	
		B0067	CR 29.002-089 on Security interworking between release 99 and pre-99 MSC/VLRs	Nokia	B	Agreed for the time being based on the working assumption that N1 has not been able to produce a solution to the problem identified by Nokia Agreement will be confirmed in Milan.	
		B0068	Security interworking between R99 and pre-99 MSC/VLRs for roaming USIMs	Nokia		This contains the problem statement: if a 3G MS roams from a 2G MSC/VLR to a 3G MSC/VLR. There is uncertainty over whether N1 have agreed a solution based on MS classmark; N2B agree this solution, subject to confirmation that N1 have not been able to fix it. Principle accepted	
		B0101	CR 23.003-015r1 on Introduction of EMSI	T-Mobil		Presented by T-Mobil. Concerns from Nortel Networks and others about the need for alignment of encrypt/decrypt algorithms between SIM & UIDN – mistaken assumption that the ME is involved in the encryption process. Presented for information, with the objective of approval in Milan.	
		B0102	CR 23.012-003 on Introduction of Enhanced User ID Confidentiality	T-Mobil		New section 2.6 was introduced. Other changes were illustrated as well. Nokia identified possible problem with the location update timer in the MS and also raised concern over whether N1 will be able to complete their work in time for TSG #7. NTT DoCoMo pointed out the need to do work in T1 (?). T-Mobil will check with S3 colleagues whether they are following this up. Two areas with misalignments were identified in the discussion and a revision will be provided for the Milan meeting. Ericsson raised concerns on emergency call handling in case the encrypted IMSI cannot be decrypted.	
		B0103	CR 23.018-036 on Introduction of Enhanced User ID Confidentiality	T-Mobil		Concerns from France Telecom will be addressed directly to T-Mobil. Clarified that this CR, and the others, was presented here to review them and approve them by the next meeting.	
		B0104	CR 23.060-xxx on Introduction of Enhanced User ID Confidentiality	T-Mobil		Not within N2 remit, hence presented here for information. Specific comments can be delivered to T-Mobil off line.	
		B0105	CR 29.002-092 on Introduction of Enhanced User ID Confidentiality	T-Mobil		Presented for information, approved expected by the next meeting.	
		B0106	Security interworking between release 99 and pre-99 MSC/VLRs for roaming USIMs	Nokia	B		
		B0128	LS on a mechanism for reporting authentication failures from VLR/SGSN to HLR	S3		New mechanism defined by S3, this will require a new message to the HLR. Nokia and Nortel believe it is very difficult to produce a CR in time for approval to CN#07. The view was generally supported, although Vodafone (from an Operator's perspective) showed their disappointment for the position. Nokia observed that the issue has a significant impact on GLR as well.
The response to the S3 Chairman will highlight that several vendors indicated that, although the work will be initiated, a complete set of stable CRs is not realistic for CN#07. The Chairman will draft the LS. The drafting work to the GLR spec. was expected on the Japanese side, although nobody volunteered.	
		B130	An overview of a mechanism for protection of MAP signalling	Mannesmann/T-Mobil		The aim of the contribution is to give a first sight of the approach to take in drafting CRs to 29.002 (mostly) as well as to 23.012 and 23.078.NEC asked whether protection is mandatory. T-Mobil responded that the protocol to support protection is mandatory, but the function of applying the protection is subject to bilateral agreement between operators. Nortel networks had concern that S3 may come up with a radically different approach for R2000. NTT DoCoMo raised concerns that N2B should not risk destabilising the core specifications by introducing late changes.	
		B134	LS to S3 on reporting authentication failures	Chairman		LS approved by N2B, to be ratified by N2A as well. Since it was ratified with a minor correction (indications of the originator), it will be sent out.	
		B135	LS on enhanced User confidentiality	N1	B	Concerns raised are largely on the access interface. It was enough to note the document.	
		B122		Vodafone		Quick presentation. Delegates were encouraged to study the document off line and react. Application context versions have to be updated for Release 99. Presented for information and comments by e-mail.	
6.9	Signalling reduction techniques						
6.9.1	The GLR						
		B0002	Proposed modifications of TS 23.119 	NTT DoCoMo	B	Three corrections were proposed, including one to LCS. TS 23.119 is not yet under change control, changes can be incorporated more easily, in order to produce v. 1.1.0. 	
		B0009	The interaction between the GLR and Super-Charger	Fujitsu	B	Revised to B0074	
		B0010	GTP specification for GLR	Fujitsu	B	Mostly editorial changes to refine the text. The document was found to be ready to be raised to v.2.0.0, provided that the closing N2 plenary accepts it.	
		B0018	The addition of SDL diagrams to GLR Stage2 specification	NTC	B	Revised to B0073	
		B0035	TS 29.120 v1.0.1 (MAP for the GLR)	NTT Commware	B	NTT Commware offered to include in the document any change raising from the authentication failure events. Revised to include material from B0074 to make v1.1.0, which will go to Milan.	
		B0073	The addition of SDL diagrams to GLR Stage2 specification	NTC	B	Revision of B0018, presented by NTC. The SDLs diagrams, together with the changes in B00002 can be included in the GLR stage 2 document. 	
		B0074	The interaction between the GLR and Super-Charger	Fujitsu	B	Revision of B0009. Nortel expressed favour for the contribution, although highlighted the need for a revision. The material in the document was agreed for inclusion into GLR stage 2. It was also agreed to submit a document in Milan with all the agreed changes, and there it will be decided whether to upgrade it to ver. 2.0.0.	
6.9.2	The Supercharger	B0032	Response to Liaison Statement from TSG-CN2 on Required Super-charger Enhancements	T1	B	No impact on N2 specification. Noted.	
6.10	Other Release 99						
6.10.1	Pre-paging	B0008	CR 23.018-030 on Correction of the SDL diagram for Pre-paging	NTC	B	Addition of one task box in an SDL diagram. Agreed.	
6.10.2	LCS	B0019	CR 23.007-004 on Support of VLR and HLR Data Restoration procedures with LCS	T1P1.5	B	Agreed	
							
		B0046	CR 29.002-083 on Privacy notification/ verification for call related privacy class	Nokia/T1P1.5	B	R99 mirror of B0047. Chapter 7 was changed and the other modifications were illustrated. Agreed.	
							
6.10.3	Emergency calls	B0021	LS on Emergency calls using IMEI as UE identifier	N1	B	Ericsson will draft an LS (B0138) to confirm the N1 view that there is no mechanism to locate a ME when only the IMEI is known.	
		B0138	LS to N1 on Emergency calls using IMEI as UE identifier	Ericsson	B	Handled in plenary and approved	
6.10.4	Cell broadcast	B0022	LS on Common Communication Mechanism to be used by the Cell Broadcast Service	R3	B	In copy to N2. Noted	
		B0034	LS on Information on Common Communication Mechanism to be used by the Cell Broadcast Service	T2	B	In copy to N2. Noted.	
6.10.5	NSAPI	B0023	LS on usage of NSAPI, RB identity, RAB ID and TEID	R3	B	Needs study to see whether MAP carrying RANAP (for CS) & GTP (for PS) will transport the NAS binding information.	
		B0025	LS on usage of NSAPI, RB identity, RAB ID and TEID	S2	B	Action required drafting a corresponding CR to 29.060, but NTT DoCoMo indicated that N2-99k78 was duly taking into account the requirements expressed. The view was shared. Noted	
6.1.0.6	SoLSA	B0065	CR 23.008-013 on Correction of LSA Information	Ericsson/Nokia	B	Mirror CR to Release 98 (B0086). Agreed.	
		B0066	CR 23.016-010 on Correction of LSA information	Ericsson/Nokia	B	Mirror CR to Release 98 (B0087). Agreed.	
		B0100	CR 29.002-087 on Correction of LSA information	Ericsson/Nokia	B	(Number changed to B0100 because of Tdoc numbering problem). Agreed. NTT DoCoMo raised a concern over the reference to GSM 08.08; this is because 29.002 serves both GSM R99 and UMTS R99, but SoLSA is only a GSM R99 feature.	
6.10.7	Charging	B0029	Liaison Statement on CDR creation for non-charging liable subscriptions	S2	B	The requirements had already been taken into account by N2. However Lucent and Nokia will jointly draft an LS (0139) to ask S2 to clarify in the Stage 2.	
6.10.8	SAT/MExE	B0033	Response to liaison statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture	T2/SWG1 (MExE)	B	Noted.	
		B0129	LS on 5 or 6 digits IMSI HPLMN	T2		MCCs defined in E.212 are rather stable, since they are defined by ITU-T. T2 should be reassured that the concern over frequent update of MCCs is not well founded. The Chairman will draft an LS (B0141) on the stability of combination of MCC and MNC.	
		B0141	Proposed LS to T2 on 5 or 6 digits IMSI HPLMN	Vodafone AirTouch	B	Handled in plenary and approved	
6.10.9	QoS Enhancement	B0052	CR 29.002-084 on Addition of CS Allocation/retention priority	NTT DoCoMo/ NTT Software	B	Revised to B0080	
		B0071	Answer to LS from N2 regarding the establishment of a QoS taskforce	S2	B	Noted. The work of the Task Force on QoS (reported by Lucent) is near completion and progress has been made since the original draft of the LS from S2	
		B0080	CR 29.002-084r1 on Addition of CS Allocation/retention priority	NTT DoCoMo, NTT Software	B	Revision of B0052. NTT Software presented the CR. New section 7.6.3.x added. Reference should be made to TS 23.107 and second sentence should be formulated as It corresponds to the allocation/retention priority, which is defined in TS 23.107. Further revised to B0142.	
		B0142	CR 29.002-084r2 on Addition of CS Allocation/retention priority	NTT DoCoMo, NTT Software	B	Agreed.	
6.10.10	TEI	B0055	CR 29.002-086 on various editorial corrections	Ericsson	B	Major editorial mop-up; accepted with revision to B0144 by adding correction of reference to Q.669 to become Q.699; direct to closing plenary. Ericsson reminded that we haven't heard back from S2 about the request to take over the architectural info from 29.002. He will draft a kicker (B0145)	
		B0092	CR 29.002-094 on Addition of forgotten modification in section 4	Siemens	B	Siemens clarified that the original CR came from T1P1. Alcatel and Ericsson reminded that N2 in Phoenix took a positive decision to exclude the changes from chapter 4. Siemens expressed the concern that by suspending work on chapter 4 we come to the danger that it will become more and more outdated and the work to realign it consequently greater.	
	TEI	B0121	CR 23.003-016 on definition of Service Area Identification	NTT Commware		The proposal needs to be linked to an appropriate CR. Principle: move the definition of the service area specification into 23.003. Principle accepted, as well as the technical concept. Agreed.
NTT Commware will draft the Liaison Statement (B0146) to R3.
NTT Commware volunteered in producing the Change request against MAP. Ericsson Norway expressed their opinion that no change is necessary to GTP.	
7	Release 2000						
7.1	CAMEL phase 4	A0057	CR 23.078-??? on Proposed Stage 2 SDL Architecture to support CPH	Nokia	A		
							
8	Maintenance of GSM Phase 2+						
8.1	CAMEL Phase 2	A0092	CR 03.78-A149 on CAMEL2 Stage 2 LocationNumber for IDP in MO calls	Nokia	A		
8.2	ASCI phase 2	B0036	CR 09.02-A283 on Priorisation of MAP application context related to VGCS/VBS	Siemens	B	Category C3 (not essential but accepted by all relevant manufacturers): all other manufacturers present in the meeting accepted it. Agreed. Mirror CRs to be provided.	
8.3	GPRS	B0041	CR 09.60-A080 on Ordering of repeated Information Elements in GTP for R97 	Nortel Networks	B	Agreed	
		B0042	CR 09.60-A081 on Ordering of repeated Information Elements in GTP for R98	Nortel Networks	B	R98 mirror of B0041. Agreed	
		B0062	CR 09.60-A031r3 on Use of a 3-digit MNC in the TID for R'97	Nortel Networks	B	Postponed. Comments to be made by 7th Feb.	
		B0063	CR 09.60-A082 on Use of a 3-digit MNC in the TID for R'98	Nortel Networks	B	Postponed. Comments to be made by 7th Feb.	
							
8.4	LCS	B0047	CR 09.02-A285 on Privacy notification/verification for call related privacy class	Nokia/T1P1.5	B	Agreed.	
		B0097	CR 09.02-A282 on Correction of SS codes for LCS	Siemens	B	Mirror CR to 29.002 is necessary and an LS to T1P1.5, with the CR attached, indicating the clash of Code allocation.
Need also a corresponding CR (29.002-093) to Release 99 (B0137), both by Siemens. CR will not be presented in N2B. On further study, there is no need for the R99 CR, so B0137 is withdrawn	
		B0136	Proposed LS to T1P1.5 on correction of SS codes for LCS	Siemens	B	Approved with editorial refinements.	
							
8.5	SoLSA	B0086	CR 03.08-A030 Correction of LSA Information	Ericsson	B	Two new chapters were included. The CR should be included in the category of essential corrections (not editorial) that urgently need to be made. Consequently, category will be C1.	
		B0087	CR 03.16-A040 Correction of LSA Information	Ericsson	B	Coupled with the previous CR as a part of the same package. Agreed.	
		B0088	CR 09.02-A281 Correction of LSA Information	Ericsson	B	Agreed as well, see above.	
9	Any other business	B0153				Vodafone volunteered in taking care of 23.015

		N2-000009	Meeting report from the MNP meeting in Madrid		B	Ericsson Spain presented it. The report is to be considered closed and the report is noted.	
10	Approval of output documents						
10.1	Liaison statements	B0118	Proposed LS to S5 (cc S2) on trace specification for UMTS	N2B	P	Approved in plenary	
		B0131	Proposed LS to S1 on Multicall	N2B	P	Revised to 152	
		B0136	Proposed LS to T1P1.5 on correction of SS codes for LCS	N2B	P	Approved in plenary	
		B0126	Proposed LS to S2 on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	Vodafone AirTouch	P	Approved with editorial changes	
		B0127	Proposed LS to RAN3 on interworking between RANAP and MAP	Ericsson	P	Approved	
		B0132	Proposed Liaison statement to R3 on OoBTC	NTT DoCoMo	P	Revised to N2-000012	
		B0133	Proposed Liaison statement to S2 on Transcoder Free operation	NEC	P	Approved with minor amendments	
		B0138	LS to N1 on Emergency calls using IMEI as UE identifier	Ericsson	P	Approved	
		B0139	Liaison Statement on CDR creation for non-charging liable subscriptions	Lucent/Nokia	P	Approved	
		B0141	Proposed LS to T2 on 5 or 6 digits IMSI HPLMN	Vodafone AirTouch	P	Approved	
		B0145	Proposed LS to S2 on transfer of architectural information from TS 29.002	Ericsson	P	Approved	
		B0146	Proposed LS to R3, S2 & R2 on Definition of SAI	NTT Commware	P	Approved	
		B0151	Proposed LS to S2 on description of hard handover in TS 23.06	Ericsson	P	Approved	
		B0152	Proposed LS to S1 on Multicall	NTT Commware	P	Further revised to N2-000014	
		-0012	Proposed Liaison statement to R3 on OoBTC	NTT DoCoMo	P	Approved	
		-0014	Proposed LS to S1 on Multicall	NTT Commware	P	Approved	
		-0015	Proposed LS to N1 on access signalling and MS behaviour for Multicall	Vodafone AirTouch	P	Revised to -0016, which was approved	
							
10.2	New specifications	B0010	GTP specification for GLR	N2B	P	Request to raise to version 2 for approval by CN #7. Approved	
							
10.3	CRs handled in subgroups	N2-000010	N2 Chairman 	N2B	P	Concerns were expressed by T-Mobil about CRs contained in Tdoc B044 and B113. According to T-Mobil introduction of these functionality must be done properly. Involvement of SA5 was encouraged. Ericsson indicated that a Liaison Statement (B0029) in this respect has been sent to S2.
Lucent, on the basis of the several issues raised, proposed to postpone them to Milan, but Nokia reacted that the objection does not impact the CRs.	
							
11	Review of dates and hosts for future meetings					The N2B meeting and the multicall meeting are given authority to send CRs and LSs to other groups without formal approval from other groups.
Still a clear indication about the venue for the March meeting is missing most likely San Diego or Austin, Texas.
May meeting: Siemens in Rotenburg, near Bad hersfeld
July in Budapest, on invitation from Nokia.
September in the USA
November, Paris on Alcatel invitation.
For 2001, there might be an invitation to Australia and Canada.
Action Point Franco Settimo: to transfer to Milan Tdocs N2-99G91 and N2-99J61.	

Annex A

List of Temporary Documents
Tdoc n 3GPP	Title	Source	Status	
N2B000001	Towards the completion of the GLR specifications	NTT DoCoMo	Conclusions accepted	
N2B000002	Proposed modifications of TS 23.119	NTT DoCoMo	Accepted	
N2B000003	Proposal to send a LS to R3 on Out of band Transcoder control	NTT DoCoMo	LS drafted	
N2B000004	CR 23.018-029 on Parallel handling of multiple PDP contexts	Ericsson Spain	Withdrawn	
N2B000005	LS on location and control of speech codec	S2		
N2B000006	Proposed answer Liaison Statement to SA WG2 on "Basic principles of QoS interoperation	S2	Noted	
N2B000007	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)	S1	Noted	
N2B000008	CR 23.018-030 on Correction of the SDL diagram for Pre-paging	NTC	Agreed	
N2B000009	The interaction between the GLR and Super-Charger	Fujitsu	Revised to 0074	
N2B000010	GTP specification for GLR v.1.0.0	Fujitsu	To the CN plenary	
N2B000011	CR 29.060-033 on Addition of Radio Priority to the MM Context and PDP Context IEs	Motorola Norway	Postponed	
N2B000012	CR 29.060-034 on Removal of redundant information from the PDP Context IE	Motorola Norway	Withdrawn	
N2B000013	CR 29.060-035 on Addition of Packet Flow Id to the PDP Context IE	Motorola Norway	Revised to B099	
N2B000014	CR 29.060-036 on Change the attribution of the PDP Context IE	NEC	Revised to B095	
N2B000015	CR 29.060-037 on Add cause value	NEC	Agreed	
N2B000016	CR 29.060-038 on Addition of NSAPI to GGSN-initiated Update PDP Context	Fujitsu	Agreed	
N2B000017	Draft Stage 1.5 for Multicall	NTT Commware	LS (0131) drafted	
N2B000018	The addition of SDL diagrams to GLR Stage2 specification	NTC	Revised to 0073	
N2B000019	CR 23.007-004 on Support of VLR and HLR Data Restoration procedures with LCS	T1P1.5	Agreed	
N2B000020	LS on TrFO, Codec List and TFO Status	S4	Noted	
N2B000021	LS on Emergency calls using IMEI as UE identifier	N1	LS (0138) drafted	
N2B000022	LS on Common Communication Mechanism to be used by the Cell Broadcast Service	R3	Noted	
N2B000023	LS on usage of NSAPI, RB identity, RAB ID and TEID	R3	FFS	
N2B000024	Reply to: “LS on Open Issues on 3G to 2G Handover (packet Switched domain)”	S1	Withdrawn	
N2B000025	LS on usage of NSAPI, RB identity, RAB ID and TEID	S2	Noted	
N2B000026	Liaison statement to N1 and N2 concerning QoS parameter mapping between R97/98 and R99	S2	Noted	
N2B000027	Liaison Statement on the concern about the definition of the Service Area identity	S2		
N2B000028	Liaison Statement on usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	S2		
N2B000029	Liaison Statement on CDR creation for non-charging liable subscriptions	S2	LS (0139) drafted	
N2B000030	LS 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	CR drafted	
N2B000031	Liaison statement on the application of IST to emergency calls	SMG10 and S3	Noted	
N2B000032	Response to Liaison statement from TSG-CN2 on Required Super-charger Enhancements	T1	Noted	
N2B000033	Response to liaison statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture	T2/SWG1 (MExE)	Noted	
N2B000034	LS on Information on Common Communication Mechanism to be used by the Cell Broadcast Service	T2	Noted	
N2B000035	TS 29.120 v1.0.1	NTT Commware	To be revised for Milan	
N2B000036	CR 09.02-A283 on Prioritization of MAP application context related to VGCS/VBS	Siemens	Agreed
	
N2B000037	CR 29.002-094 on QoS- Subscribed field enhancements	Siemens	Revised to B0108	
N2B000038	CR 29.060-039 on Alignments of Message Type value	NTT Software	Superseded by B0060	
N2B000039	Coordination plan to complete Multicall in R99 (Ver.1)	NTT DoCoMo		
N2B000040	Multicall basic concept	NTT DoCoMo		
N2B000041	CR 09.60-A080 on Ordering of repeated Information Elements in GTP for R'97 	Nortel Networks	Agreed	
N2B000042	CR 09.60-A081 on Ordering of repeated Information Elements in GTP for R'98	Nortel Networks	Agreed	
N2B000043	CR 29.060-051 on Ordering of repeated Information Elements in GTP for R99	Nortel Networks	Agreed	
N2B000044	CR 29.060-040 on Improving charging efficiency	Nokia	Agreed	
N2B000045	CR 29.060-041 on Subscriber and equipment trace for PS domain	Nokia	Revised to 110	
N2B000046	CR 29.002-083 on Privacy notification/verification for call related privacy class	Nokia/T1P1.5	Agreed	
N2B000047	CR 09.02-A285 on Privacy notification/verification for call related privacy class	Nokia/T1P1.5	Agreed	
N2B000048	CR 29.060-042 on Necessity of the function of the calculation an SGSN IP address from the target ID	NTT Commware	Agreed	
N2B000049	CR 23.003-014 on Necessity of the function of the calculation an SGSN IP address from the target ID	NTT Commware	Agreed	
N2B000050	CR 29.060-043 on QoS Profile IE modification	NTT Software	Revised to 0078	
N2B000051	CR 29.060-044 on The addition of the conditional description of the GTP parameters	NTT Software	Revised to 0079	
N2B000052	CR 29.002-084 on Addition of CS Allocation/retention priority	NTT DoCoMo, NTT Software	Revised to 0080	
N2B000053	CR 29.002-085 on Ext-QoS-Subscribed modification	NTT Software	Revised to 0081	
N2B000054	Lack of information on mapping 3GPP CODEC type and Bearer attribution 	NEC	Withdrawn	
N2B000055	CR 29.002-086 on various editorial corrections	Ericsson	Revised to 0144	
N2B000056	CR 29.060-057 on Removal of X.25	Ericsson Norway	Agreed	
N2B000057	CR 29.060-045 on Removal of Anonymous Access	Ericsson Norway	Revised to 0111	
N2B000058	CR 29.060-046 on Authentication Clarification	Ericsson Norway	Revised to 0112	
N2B000059	CR 29.060-047 on New relocation message	Ericsson Norway	Postponed	
N2B000060	CR 29.060-048 on Clarification of Information Elements	Ericsson Norway	Agreed	
N2B000061	CR 29.060-049 on Recovery IE in Echo Response	Ericsson Norway	Withdrawn	
N2B000062	CR 09.60-A031r3 on Use a 3-digit MNC in the TID for R'97	Nortel Networks	Postponed	
N2B000063	CR 09.60-A082 on Use of a 3-digit MNC in the TID for R'98	Nortel Networks	Postponed	
N2B000064	CR 29.060-050 on Payload Type in GTP header	Ericsson Norway	Revised to 0119	
N2B000065	CR 23.008-013 on Correction of LSA Information	Ericsson/Nokia	Agreed	
N2B000066	CR 23.016-010 on Correction of LSA information	Ericsson/Nokia	Agreed	
N2B000066	CR 29.002-087 on Correction of LSA information	Ericsson/Nokia	Replaced (see 100)	
N2B000067	CR 29.002-089 on Security interworking between release 99 and pre-99 MSC/VLRs	Nokia	To be confirmed in Milan	
N2B000068	Security interworking between release 99 and pre-99 MSC/VLRs for roaming USIMs	Nokia	Principles accepted	
N2B000069	CR 29.002-090 on Improving GPRS charging efficiency (WI=GPRS)	Nokia	Revised to 0113	
N2B000070	Liaison Statement concerning Transcoder Free operation	S2	LS (0133) drafted	
N2B000071	Answer to LS from N2 regarding the establishment of a QoS taskforce	S2	Noted	
N2B000072	CR 29.060-052 on Method for GTP extension headers support	Lucent Technologies	Postponed	
N2B000073	The addition of SDL diagrams to GLR Stage2 specification	NTC	Accepted	
N2B000074	The interaction between the GLR and Super-Charger(rev.1)	Fujitsu	Postponed to Milan	
N2B000075	Working Plan to complete OoBTC in R99	NTT DoCoMo		
N2B000076	Finalizing R99 works	NTT DoCoMo		
N2B000077	Towards multicall Stage 2	NTT Commware	Accepted with amendments	
N2B000078	CR 29.060-043r1 on QoS Profile IE modification	NTT Software	Revised to 0114	
N2B000079	CR 29.060-044r1 on The addition of the conditional description of the GTP parameters	NTT Software	Revised to 0115	
N2B000080	CR 29.002-084r1 on Addition of CS Allocation/retention priority	NTT DoCoMo/NTT Software		
N2B000081	CR 29.002-085r1 on Ext-QoS-Subscribed modification	NTT Software	Rejected	
N2B000082	CR 23.008-014 on The addition of priority information to subscriber data.	NTT Software	Revised to 0116	
N2B000083	CR 23.016-011 on The addition of priority information	NTT Software	Revised to 0117	
N2B000084	CR 29.060-054 on The addition of the description about the value of TEID	NTT Software	Postponed	
N2B000085	CR 29.060-055 on Addition of QoS parameter to PDU Notification Request	Cisco Systems	Agreed conditionally	
N2B000086	CR 03.08-A030 on Correction of LSA Information	Ericsson/Nokia	Agreed	
N2B000087	CR 03.16-A040 on Correction of LSA information	Ericsson/Nokia	Agreed	
N2B000088	CR 09.02-A281 on Correction of LSA information	Ericsson/Nokia	Agreed	
N2B000089	CR 29.010-003 on UMTS/GSM Interworking	Ericsson	To be revised
LS drafted	
N2B000090	Contribution related to Multicall: Multicall Time Plan	Ericsson		
N2B000091	Clarification of the OoBTC Stage 2	Nortel Networks	To be revised	
N2B000092	CR 29.002-094 on Addition of forgotten modifications in section 4	Siemens	Withdrawn	
N2B000093		NTT Commware	Noted	
N2B000094	N2B time plan	Chairman		
N2B000095	CR 29.060-036r1 on Change the attribution of the PDP Context IE	NEC	Agreed	
N2B000096	New procedure for the allocation of the transcoder	NTT DoCoMo	LS (0131) drafted	
N2B000097	CR 09.02-A282 on Correction of SS codes for LCS	Siemens	Agreed	
N2B000098	Revised N2B time plan	N2 Chairman		
N2B000099	CR 29.060-035r1 on Addition of Packet Flow Id to the PDP Context IE	Ericsson Norway	Postponed	
N2B000100	CR 29.002-087 on Correction of LSA information	Ericsson/Nokia	Agreed	
N2B000101	CR 23.003-015r1 on Introduction of EMSI	T-Mobil	Postponed to Milan	
N2B000102	CR 23.012-003 on Introduction of Enhanced User ID Confidentiality	T-Mobil	Postponed to Milan	
N2B000103	CR 23.018-036 on Introduction of Enhanced User ID Confidentiality	T-Mobil	Postponed to Milan	
N2B000104	CR 23.060-xxx on Introduction of Enhanced User ID Confidentiality	T-Mobil	Noted	
N2B000105	CR 29.002-092 on Introduction of Enhanced User ID Confidentiality	T-Mobil	To be revised	
N2B000106	CR 23.107-001r3 on QoS mapping rules	S2	Noted	
N2B000107	CR 29.060-056 on Change of naming when referring to primary and secondary contexts	Ericsson Norway	Agreed	
N2B000108	CR 29.002-094r1 on QoS- Subscribed field enhancements	Siemens	Revised to 0120	
N2B000109	Liaison Statement to S5 & S2 on Trace Specification for UMTS	Nokia	Revised to 0118	
N2B000110	CR 29.060-041r1 on Subscriber and equipment trace for PS domain	Ericsson	Agreed	
N2B000111	CR 29.060-045r1 on Removal of Anonymous Access	Ericsson	Agreed	
N2B000112	CR 29.060-046r1 on Clarification of Authentication Type and Import of Parameters	Ericsson	Agreed	
N2B000113	CR 29.002-090r1 on Improving GPRS charging efficiency	Nokia	Agreed	
N2B000114	CR 29.060-043r2 on QoS Profile IE modification	NTT Software	Postponed	
N2B000115	CR 29.060-044r2 on The addition of the conditional description of the GTP parameters	NTT Software	Agreed	
N2B000116	CR 23.008-014r1 on The addition of priority information to subscriber data	NTT Software	Revised to 0143	
N2B000117	CR 23.016-011r1 on The addition of priority information	NTT Software	Agreed	
N2B000118	Liaison Statement to S5 & S2 on Trace Specification for UMTS	Nokia	Approved	
N2B000119	CR 29.060-050r1 on Payload Type in GTP header	Ericsson Norway	Agreed	
N2B000120	CR 29.002-094r2 on QoS- Subscribed field enhancements	Siemens	Agreed	
N2B000121	CR 23.003-016 on definition of Service Area Identification	NTT Commware	Agreed	
N2B000122		Vodafone	For information	
N2B000123	TS 22.125 Multicall Stage 1	TSG S1	Noted	
N2B000124	Answer to liaison statement from N2 "LS on Open Issues on 3G to 2G Handover (packet Switched domain)"	S2	Noted	
N2B000125	Proposed Response Liaison Statement on Usage of RANAP over MAP/E i/f for UMTS to UMTS Inter-MSC SRNS Relocation	N1	LS drafted (0126)	
N2B000126	Response to Proposed Response Liaison Statement on Usage of RANAP over MAP/E i/f for UMTS to UMTS Inter-MSC SRNS Relocation	Vodafone AirTouch	Approved	
N2B000127	LS on Interworking between RANAP and MAP to R3	Ericsson	Approved	
N2B000128	LS on a mechanism for reporting authentication failures from VLR/SGSN to HLR	S3		
N2B000129	LS on 5 or 6 digits IMSI HPLMN	S1 MeXE	LS (0141) drafted	
N2B000130	An overview of a mechanism for protection of MAP signalling	Mannesmann		
N2B000131	LS to S1on Multicall from NTT Commware	NTT Commware	Revised to 152	
N2B000132	LS to R3 on Out of Band Transcoder Control	NTT DoCoMo	Revised to N2-000012	
N2B000133	LS to S2 on Transcoder Free Operation	NEC	Approved	
N2B000134	LS to S3 on reporting authentication failures	Chairman	Approved	
N2B000135	LS on Enhnaced User identity confidentiality - Open questions	N1	Noted	
N2B000136	LS to T1P1.5 on reporting SS codec mismatch in GSM 09.02 in release 99 for LCS	Siemens	Approved	
N2B000137	Mirror 3G CR to Correction of SS codes for LCS CR 29.002-	Siemens	Withdrawn	
N2B000138	LS Emergency calls using IMEI as UE identifier	Ericsson	Approved	
N2B000139	LS on CDR creation for non-charging liable subscriptions	Lucent/Nokia	Approved	
N2B000140	The additional case of TrFO break	NTT DoCoMo		
N2B000141	LS to T2 on 5 or 6 digits MCC	Vodafone/AirTouch	Approved	
N2B000142	CR 29.002-084r2 on Addition of CS Allocation/retention priority	NTT Software	Agreed	
N2B000143	CR 23.008-014r2 on The addition of priority information to subscriber data	NTT Software	Agreed	
N2B000144	CR 29.002-086r1 on various editorial corrections	Ericsson	Agreed	
N2B000145	LS to S2 on move of architectural information from TS 29.002 to a separate specification	Ericsson 	Approved	
N2B000146	LS to R3 on Definition of Service Area Identification	NTT Commware	Approved	
N2B000147	CR 09.02-A284 on Prioritization of MAP application context related to VGCS/VBS 	Siemens	Agreed	
N2B000148	CR 29.002-094 on Prioritization of MAP application context related to VGCS/VBS	Siemens	Agreed	
N2B000149	LS to TSG N1 on access signalling and mobile station behaviour for Multicall	Vodafone AirTouch	Withdrawn	
N2B000150	LS on Functions of Key Distribution and Key Administration for MAP security	S3	Postponed to Milan	
N2B000151	LS on hard handover	Ericsson	Approved	
N2B000152	LS to S1on Multicall (Revision of B0131)	NTT Commware	Revised to N2-000014	
N2B000153	Changes to existing text in 3G Technical Specifications	MCC	Noted	
				
N2-000001	Draft Agenda	Chairman	Agreed with changes	
N2-000002	Tdoc allocation to agenda items	Chairman	Amended	
N2-000003	Phoenix Report	MCC	Noted	
N2-000004	Handling of ETSI Public comments on Draft ETSI EN 301 668-1 V1.1.1 (1999-07)	Alcatel		
N2-000005	Handling of ETSI Public comments on Draft ETSI EN 301 668-2 V1.1.1 (1999-07)	Alcatel		
N2-000006	Summary report on CN plenary meeting number 6, Nice, 13 – 15 December 1999	N2 Chairman	Noted	
N2-000007	Summary report from the joint meeting S3/N2 for security issues	N2 Chairman	Noted	
N2-000008	Draft meeting report on MNP (Madrid)	MCC	Revised	
N2-000009	Final meeting report on MNP (Madrid)	MCC	Noted	
N2-000010	Output documents from N2B for approval by N2	N2 Chairman		
N2-000011	Status of Change Requests from N2A	MCC		
N2-000012	LS to R3 on Out of Band Transcoder Control (revision of N2B000132)	NTT DoCoMo	Approved	
N2-000013	Revision of 011	MCC		
N2-000014	Revision of N2B000152	NTT Commware	Approved	
N2-000015	LS to TSG N1 on access signalling and mobile station behaviour for Multicall	Vodafone AirTouch	Revised to N2-000016	
N2-000016	LS to TSG N1 on access signalling and mobile station behaviour for Multicall	Vodafone AirTouch	Approved	

Annex B

LIST OF PARTICIPANTS

Name	Organisation	Tel	e-mail	
AIKAWA Shinichiro	Fujitsu	+81 44 754 4196	Aikawa@ss.ts.fujitsu.co.jp	
ALLEN Nicholas	Nortel Networks	+44 1628 434493	nallen@nortelnetworks.com	
BRUCH Diemo	Alcatel SEL	+49 711 821 47594	D.Bruch@alcatel.de	
CASATI Alessio	Lucent Technologies 	+44 1793 883861	acasati@lucent.com	
DRONNE François	France Télécom	+33 145296274	francois.dronne@cnet.francetelecom.fr	
EVENOU Jean-Alain	Alcatel France	+33 130773992	Jean-Alain.Evenou@alcatel.fr	
GRECH Michel	Lucent Technologies	+44 1793 736110	grech@lucent.com 	
HABERMANN Steffen	T-Mobil, 
N2A Chairman	+49 228 936 3324	Steffen.habermann@t-mobil.de	
HAERENS Frans	Alcatel Bell	+32 3 240 9034	frans.haerens@alcatel.be	
HAMEL Eric	France Télécom	+33 145296863	eric.hamel@cnet.francetelecom.fr	
HELLMAN Monica	ETSI MCC
N2A Secretary	+33 4 92 94 42 31	monica.hellman@etsi.fr	
HOMANN Christian	Alcatel SEL AG	+49 711 821 45632	C.Homann@alcatel.de	
HU Yun-Chao	Ericsson,
N2B Chairman	+46 8 508 78153	yun-chao.hu@era.ericsson.se	
HUMPHREY Jane	Marconi Communications	+44 1202 853757	Jane.humphrey@marconicomms.com	
IGARASHI Takeshi	NTT Software	+81-45-317-7018	rassy@po.ntts.co.jp	
IIO Masami	NTT	+81 422 59 4701	iio.masami@lab.ntt.co.jp	
ISHIHARA Masakazu	NEC	+81 471 85 7168	ishihara@mcs.abk.nec.co.jp	
KAIN Albert	Siemens AG	+ 43 5 1707 21319	Albert.Kain@siemens.at	
KEUTMANN Heinz-Peter	Ericsson LM	+49 2407 575 132	Heinz-Peter.Keutmann@eed.ericsson.se	
KIKUCHI Masahiro	NTT Communicationware	+81 43 211 2708	kikuchi.masahiro@promote.nttcom.co.jp	
KYMÄLÄINEN Kimmo	Sonera Corp.	+358 405 300 848	Kimmo.Kymalainen@sonera.com	
LANTELME Isabelle	Alcatel	+33 1 3077 0133	isabelle.lantelme@alcatel.fr	
LÓPEZ Luis	Ericsson LM	+34 91 339 2656	luis.lopez-soria@ece.ericsson.se	
MÄKINEN Teemu	Nokia	+358 40 5077283	Teemu.Makinen@Nokia.com	
MITAMURA Kazuo	NTT Communicationware	+81 43 211 2708	mitamura.kazuo@promote.nttcom.co.jp	
MIYAGAWA Sumio	Siemens KK	+81 3 5423 6745	Miyagawa@twics.com	
MOILANEN Iris	Sonera Corp.	+358 2040 71250	iris.moilanen@sonera.com	
MUHONEN Ahti	Nokia	+358 405318469	Ahti. Muhonen@Nokia.com	
NAKADA Kazuhiko	NTT	+81 422 59 2945	nakada.kazuhiko@lab.ntt.co.jp	
NOLDUS Rogier	Ericsson	+31 161 249400	rogier.noldus@etm.ericsson.se	
NORIMATSU Toshio
	NTT Communicationware	+81 43 211 2708	norimatsu.toshio@promote.nttcom.co.jp
	
OLTEDAL Einar	Ericsson	+47 37293762	Einar.oltedal@eto.ericsson.se	
PALVIAINEN Keijo	Nokia	+358 9 51169669	Keijo.Palviainen@Nokia.com	
PARK Ian David Chalmers	Vodafone AirTouch, N2 Chairman	+44 1635 67352	ian.park@vf.vodafone.co.uk
ian_park_vf@compuserve.com	
PIERRE Jean-Paul	Alcatel	+33130770735	Jean-paul.pierre@alcatel.fr	
RUSSELL Nick	Vodafone Airtouch	+44 1635 682699	nick.russell@vf.vodafone.co.uk	
SAHARA Koji	NTT	+81 422 59 7603	sahara.koji@lab.ntt.co.jp	
SAWADA Masahiro	NTT DoCoMo	+81 468 40 3332	masahiro@nw.yrp.nttdocomo.co.jp	
SCHMITT Peter	Siemens	+49 6621 169 152	peter.schmitt@icn.siemens.de	
SCHNEYER Sean	Ericsson Inc	+1 972 583 8329	Sean.Schneyer@ericsson.com	
SETTIMO Franco	ETSI MCC,
N2 Secretary	+33 4 9294 42 38
+39 348 999 85 84	franco.settimo@etsi.fr	
SHIBATA Takaho	NTT	+81 422 59 4778	shibata.takaho@lab.ntt.co.jp	
SOEJIMA Miyuki	NTC	+81 44 900 7313	miyuki@mob.ntc.co.jp	
TAMURA Toshiyuki	NEC	+81 471 85 6954	Tamurato@e1sf.ncos.nec.co.jp	
TANI Naoki	NTT DoCoMo	+81 468 40 3332	tani@nw.yrp.nttdocomo.co.jp	
TIAINEN Vesa	Nokia	+358951169712	Vesa.tiainen@nokia.com	
TORABI Moh	Lucent Technologies	+1 949 636 2116	torabi@lucent.com	
TSAO WEN-Lin	CiscoSystems	+1 408 527-7647	wtsao@cisco.com	
WAKABAYASHI Kiyohisa	Nokia Japan	+813 5510 0900	kiyohisa.wakabayashi@nokia.com	
WILD Peter	Mannesmann	+492115333798	peter.wild@d2mannesmann.de	
YAMAZAKI Hiroshi	NEC	+81 471 85 7168	yamazaki@mcs.abk.nec.co.jp	

Annex C

LIST OF AGREED CHANGE REQUESTS

Tdoc N2B00	Subject	Title	
0008	Pre-paging	CR 23.018-030 on Correction of the SDL diagram for Pre-paging	
0015	GPRS	CR 29.060-037 on Add cause value	
0016	GPRS	CR 29.060-038 on Addition of NSAPI to GGSN-initiated Update PDP Context	
0019	LCS	CR 23.007-004 on Support of VLR and HLR Data Restoration procedures with LCS	
0036	ASCI	CR 09.02-A283 on Prioritization of MAP application context related to VGCS/VBS	
0041	GPRS (R97)	CR 09.60-A080 on Ordering of repeated Information Elements in GTP for R'97 	
0042	GPRS (R98)	CR 09.60-A081 on Ordering of repeated Information Elements in GTP for R'98	
0043	GPRS	CR 29.060-051 on Ordering of repeated Information Elements in GTP for R'99	
0044	GPRS	CR 29.060-040 on Improving charging efficiency	
0046	LCS	CR 29.002-083 on Privacy notification/verification for call related privacy class	
0047	LCS (R98)	CR 09.02-A285 on Privacy notification/verification for call related privacy class	
0048	GPRS	CR 29.060-042 on Necessity of the function of the calculation an SGSN IP address from the target ID	
0049	GPRS	CR 23.003-014 on Necessity of the function of the calculation an SGSN IP address from the target ID	
0056	GPRS	CR 29.060-057 on Removal of X.25	
0060	GPRS	CR 29.060-048 on Clarification of Information Elements	
0065	SoLSA	CR 23.008-013 on Correction of LSA Information	
0066	SoLSA	CR 23.016-010 on Correction of LSA information	
0086	SoLSA	CR 03.08-A030 on Correction of LSA information	
0087	SoLSA	CR 03.16-A040 on Correction of LSA information	
0088	SoLSA	CR 09.02-A281 on Correction of LSA information	
0095	GPRS	CR 29.060-036r1 on Change the attribution of the PDP Context IE	
0097	LCS	CR 09.02-A282 on Correction of SS codes for LCS	
0100	SoLSA	CR 29.002-087 on Correction of LSA information	
0107	GPRS	CR 29.060-056 on PDP naming convention	
0110	GPRS	CR 29.060-014r1 on subscriber & equipment trace for UMTS	
0111	GPRS	CR 29.060-045r1 on Removal of Anonymous access	
0112	GPRS	CR 29.060-046r1 on Authentication Clarification	
0113	GPRS	CR 29.002-090r1 on Improving GPRS charging efficiency	
0115	GPRS	CR 29.060-044r2 on The addition of the conditional description of the GTP parameters	
0117	QoS enhancements	CR 23.016-011r1 on Addition of priority information to subscriber data	
0119	GPRS	CR 29.060-050r1 on Protocol Type in GTP header	
0120	QoS enhancements	CR 29.002-094r2 on QoS-Subscribed field enhancements	
0121	TEI	CR 23.003-016 on definition of Service Area Identification	
0142	QoS enhancements	CR 29.002-084r2 on Addition of CS Allocation/retention priority	
0143	QoS enhancements	CR 23.008-014r2 on Addition of priority information to subscriber data	
0144	TEI	CR 29.002-086r1 on various editorial corrections	
0147	ASCI	CR 09.02-A284 on Prioritization of MAP application context related to VGCS/VBS	
0148	ASCI	CR 29.002-094 on Prioritization of MAP application context related to VGCS/VBS	

Annex D

LIST OF APPROVED LIAISON STATEMENTS

Tdoc N2	Destination group(s)	Subject	
-000012	RAN3	Out of Band Transcoder Control	
-000014	S1	Multicall	
-000016	N1	Access signalling and mobile station behaviour for multicall	
B000118	S5 (cc S2)	Trace specification for UMTS	
B000126	S2	Usage of RANAP over MAP/E at intra UMTS inter MSC handover/relocation	
B000127	RAN3	Interworking between RANAP and MAP	
B000133	S2	Transcoder Free Operation	
B000134	S3	Reporting authentication failures	
B000136	T1P1	Correction of SS codes for LCS	
B000138	N1	Emergency calls using IMEI as UE identifier	
B000139	S2	CDR creation for non-charging liable subscriptions	
B000141	T2	5 or 6 digits IMSI HPLMN	
B000145	S2	Transfer of architectural information from TS 29.002	
B000146	R3, S2, R2	Definition of SAI	
B000151	S2	Hard handover	

Annex E

LIST OF NEW TECHNICAL SPECIFICATIONS AND REPORTS

Tdoc N2B00	Subject	Title	
0010	The GLR	TS 29.119: GPRS Tunneling Protocol (GTP) specification for GLR