3gpp tsg-sa wg2 meeting Document List

07.04	-----	------	3GPP System Architecture Evolution (SAE)	----------	-	-	-	-	-	-	-
07.04	S2-052468	LS In	Reply LS (from SA WG3) on Security Requirements for Long Term Evolved RAN/3GPP System Architecture Evolution	SA WG3 (S3-050602, Vodafone)	-	-	-	-	-	-	SAE	SA WG3 thanks SA WG2/RAN WG2/RAN WG3 for the LS on security requirements for LTE/SAE. SA WG3 provide response to the questions in the LS. SA WG3 ask the addressed groups: - Take note of the answers provided above. - Provide further information on thelikely error characteristics of an LTE/SAE system so that SA WG3 can determine whether a cost effective integrity protection mechanism for user plane data could be developed. - Provide further information about RAN network signalling so that corresponding security requirements can be identified. - Provide further information about CN signalling so that corresponding security requirements can be identified. - Provide a summary of the current architectural alternatives.	Noted
07.04	S2-052593	WITHDRAWN		ETRI	23.882	-	-	-	0.7.1	Rel-7	SAE	The correction of ambiguous sentence in TR 23.882.
07.04	S2-052594	WITHDRAWN		ETRI	23.882	-	-	-	0.7.1	Rel-7	SAE	The same definitions occurred twice unnecessarily in TR 23.882.
07.04	S2-052656	NOT RECEIVED		Orange	23.882	-	-	-	-	Rel-7	SAE	It discusses the base architecture for supporting inter-3GPP and non-3GPP access systems
07.04	S2-052657	P-CR	Inter-System Mobility Alternate Solutions for Annex E	Orange	23.882	-	-	-	-	Rel-7	SAE	This document describes an alternate solution for Inter-System Mobility Management that could go into Annex E of TR 23.882. The solution is described in the proposed text below and aims at fulfilling the requirements for seamless mobility included inSA WG1 All IP Network requirements (TS 22.258):	Not handled and should be re-submitted by the authors to the next meeting
07.04	S2-052658	P-CR	Clarification on the scope of service continuity support at SAE	Azaire Networks	23.882	-	-	-	-	Rel-7	SAE	This paper clarifies the scope of the service continuity at SAE so that it only considers the scenario 3 or higher type of interworking for any non-3GPP access networks.	Not handled and should be re-submitted by the authors to the next meeting
07.04	S2-052668	TR	TR 23.882 v0.7.1	Vodafone (rapporteur)	23.882	-	-	-	0.7.1	Rel-7	SAE	Same as S2H050400, the output of the SA 2 ad hoc in Seattle.	Approved for use for further updates
07.04	S2-052691	DISCUSSION / APPROVAL	Proposed process for building the Architecture	NTT DoCoMo	-	-	-	-	-	-	SAE	The agreed timeplan document, S2H050375, states that TR 23.882 will contain an architectural diagram showing the main functional entities and the interfaces to be standardised. However, the process of deciding the details of the architecture diagram,e.g. specific functional units and interfaces, has not been stated. This contribution proposes the work process for drawing the architectural diagram of the TR 23.882.	Noted
07.04	S2-052692	WITHDRAWN	WITHDRAWN	NTT DoCoMo	-	-	-	-	-	-	SAE	Introduction of co-rapporteurs	WITHDRAWN
07.04	S2-052697	DISCUSSION / APPROVAL	Proposed principle of the documentation for TR23.882	NTT DoCoMo	-	-	-	-	-	-	SAE	As stated in the agreed work process text in S2H050375 ("Priority is on agreeing functional architecture and interfaces with high level description, whereas selection of protocols has lower priority.") we should focus on the functional level discussion in the SAE work. However, in order to explain a proposed solution so it is easier to understand it might be necessary to include more detailed explanation of the protocols and messages included. However, very long and detailed contributions mightbe time consuming to compare and are difficult to capture in the TR if more than one alternative needs to be documented. In order to clarify this work process, this contribution proposes a principle of the documentation.	Noted
07.04	S2-052748	P-CR	Clarification on Interworking Requirements	Nokia	23.882	-	-	-	-	-	SAE	This contribution proposes addition to Interworking requirements in TR 23.882 to address the standalone deployment scenario.	Noted
07.04	S2-052783	DISCUSSION / APPROVAL	Converged architecture improvements and common semantics	Intel	-	-	-	-	-	-	-	Proposes enhancements to S2-052738 to then be used as baseline, and items as FFS SA2 work items.	Not handled and should be re-submitted by the authors to the next meeting
07.04	S2-052810	TS	Latest versions of the AIPN Stage 1 in TS 22.258	NTT DoCoMo	22.258	-	-	-	2.0.0	Rel-7	AIPN	Provided for information on latest AIPN Stage 1	Noted
07.04	S2-052811	[LS OUT]	LS to SA WG3 (Chris, VF)	SA WG2	-	-	-	-	-	-	-		Revised in S2-053002
07.04	S2-052812	DISCUSSION	Updated SAE Time Plan	Vodafone	-	-	-	-	-	-	-	This is a proposed time plan as developed at the Work Plan management evening session and was based on TD S2 052670.	Revised in S2-053013
07.04	S2-053002	[LS OUT]	draft LS on additional information on System Architecture Evolution	Vodafone [SA WG2]	-	-	-	-	-	-	-	SA WG2 have already sent an LS to SA WG3 in S2H050397. SA WG2 thank SA WG3 for initiating discussion of this LS via email, and (because of the meeting calendars) using email to directly raise "questions for clarification" back to SA WG2.	Revised in S2-053020
07.04	S2-053013	WORKPLAN	Updated SAE Time Plan	Vodafone	-	-	-	-	-	-	-	Revision of S2-052812	Approved
07.04	S2-053020	LS OUT	LS on additional information on System Architecture Evolution	SA WG2	-	-	-	-	-	-	-	SA WG2 have already sent an LS to SA WG3 in S2H050397. SA WG2 thank SA WG3 for initiating discussion of this LS via email, and (because of the meeting calendars) using email to directly raise "questions for clarification" back to SA WG2.	Approved
07.04 / 09.02	S2-052670	INFORMATION	SAE timeplan	SAE rapporteur (Vodafone)	-	-	-	-	-	-	SAE	Proposed Timeplan for progression of SAE work	Noted
07.04.1	-----	------	Combination of B1 and B2 into a single architectural concept (this is time plan line c). This continues to involve 7.4.1.1-7.4.1.4