3gpp tsg-sa wg2 meeting Document List

7.4.1.3	-----	------	Pooling/sharing of resources	----------	-	-	-	-	-	-	-
7.4.1.3	S2-060035	P-CR	Key issue Optimized MM	NEC, NTT DoCoMo, Motorola	23.882	-	-	-	-	Rel-7	SAE	Iu Flex concept is introduced for SAE mobility	Revised in S2-060480
7.4.1.3	S2-060087	P-CR	Support for multi-to-multi relationship between MME/UPEs and Node Bs	Ericsson	23.882	-	-	-	-	Rel-7	SAE	At the last SA WG2 / RAN WG2 / RAN WG3 meeting a contribution was presented outlining a proposal for a 2-node SAE / LTE architecture. The architecture is based on having a multi-to-multi relationship between the central nodes called ACGWs and the base stations called Node Bs. This solution will meet the requirement in clause 5 of TR 23.882 (v 0.9.0) stating that: "The SAE/LTE system shall support redundancy concepts / load sharing of network nodes, e.g. similar to today's Iu-flex mechanisms. Allnodes other than cell site node should be considered "distributed resources utilising load sharing/redundancy mechanisms". This contribution further elaborates on how to achieve a multi-to-multi relationship (called S1-flex) in a 2-node SAE / LTE architecture. A S1-flex solution is where a Node B is connected to multiple ACGWs. In the terminology of the converged SA WG2 architecture this would mean that there is a multi-to-multi configuration between the Node Bs, and the MME / UPE and Inter ASanchor functions. It is proposed to adopt text proposal in section 4 to 3GPP TR 23.882, to add the support of S1-flex as a key issue for SAE.	Revised in S2-060479
7.4.1.3	S2-060088	P-CR	Network Sharing aspects for a 2-node 3GPP SAE / LTE architecture	Ericsson	23.882	-	-	-	-	Rel-7	SAE	Introduces network sharing aspects for SAE/LTE	Revised in S2-060314
7.4.1.3	S2-060212	DISCUSSION	Selection of ACGW and MS re-distribution when ACGW Pool is configured	Huawei	23.882	-	-	-	-	Rel-7	SAE	ACGW is introduced in S2-052568 from Ericsson. If ACGW pool is configured and the attached ACGW is not identical with the edge ACGW in same pool, service packets are routed between ACGWs. This paper introduces a solution to re-distribute MS between ACGWs. By this solution, MS can be re-distributed to the target ACGW and routing data among ACGWs can be reduced.	Noted
7.4.1.3	S2-060295	P-CR	Adding load-sharing / redundancy above the cell site node	Lucent Technologies	23.883	-	-	-	-	-	SAE	In section 5 of TR 23.882 v0.9.0, on "Requirements on the Architecture", one of the requirements one can read is: "The SAE/LTE system shall support redundancy concepts / load sharing of network nodes, e.g. similar to today's Iu-flex mechanisms. All nodes other than cell site node should be considered "distributed resources utilising load sharing/redundancy mechanisms". This contribution aims at reflecting this requirement through some relevant sections of TR 23.882 v0.9.0.	Revised in S2-060482
7.4.1.3	S2-060314	P-CR	Network Sharing aspects for a 2-node 3GPP SAE / LTE architecture	Ericsson	23.882	-	-	-	-	Rel-7	SAE	In recent SA WG2 and RAN WG3 meetings a 2-node 3GPP SAE/LTE architecture were presented. The presented solution meets the SAE / LTE requirements on performance (e.g. UP/CP latency, mobility) and security (i.e. same or better than current UMTS level)without introducing any unnecessary complexity (e.g. Inter-Node B UP/CP interfaces). This contribution is focusing on the requirements on Network Sharing that is part of the SAE / LTE. (See requirements in TR 23.882 sub clause 5 – "The SAE/LTE systemshall support network sharing functionality…" – and in TR 22.978 subclause 5.1.1.9 second bullet). It is proposed to fulfil the requirements with a simplified Network Sharing architecture compared to Rel-6 Network Sharing. For example, only "supporting UEs" exist on the LTE radio and it should be possible to only support "MOCN configurations". Text proposal is made to TR 23.882 adding a new key issue on Network Sharing.	Revised in S2-060481
7.4.1.3	S2-060399	P-CR	Discussion on Redundancy and Load-sharing	China Mobile	23.882	-	-	-	-	-	SAE-	Redundancy is an important mechanism to attain high availability while load-sharing is a mechanism to use resources efficiently. Redundancy and load-sharing are always achieved by similar ways. Some solutions for redundancy and load-sharing are proposed and compared.	Revised in S2-060483
7.4.1.3	S2-060479	P-CR	Support for multi-to-multi relationship between MME/UPEs and Node Bs	Ericsson	23.882	-	-	-	-	Rel-7	SAE	At the last SA WG2 / RAN WG2 / RAN WG3 meeting a contribution was presented outlining a proposal for a 2-node SAE / LTE architecture. The architecture is based on having a multi-to-multi relationship between the central nodes called ACGWs and the base stations called Node Bs. This solution will meet the requirement in clause 5 of TR 23.882 (v 0.9.0) stating that: "The SAE/LTE system shall support redundancy concepts / load sharing of network nodes, e.g. similar to today's Iu-flex mechanisms. Allnodes other than cell site node should be considered "distributed resources utilising load sharing/redundancy mechanisms". This contribution further elaborates on how to achieve a multi-to-multi relationship (called S1-flex) in a 2-node SAE / LTE architecture. A S1-flex solution is where a Node B is connected to multiple ACGWs. In the terminology of the converged SA WG2 architecture this would mean that there is a multi-to-multi configuration between the Node Bs, and the MME / UPE and Inter ASanchor functions. It is proposed to adopt text proposal in section 4 to 3GPP TR 23.882, to add the support of S1-flex as a key issue for SAE.	For e-mail approval
7.4.1.3	S2-060480	P-CR	Key issue Optimized MM	NEC, NTT DoCoMo, Motorola	23.882	-	-	-	-	Rel-7	SAE	Mobility Management concepts of S2-060035	Revised in S2-060527
7.4.1.3	S2-060481	P-CR	Network Sharing aspects for a 2-node 3GPP SAE / LTE architecture	Ericsson	23.882	-	-	-	-	Rel-7	SAE	In recent SA WG2 and RAN WG3 meetings a 2-node 3GPP SAE/LTE architecture were presented. The presented solution meets the SAE / LTE requirements on performance (e.g. UP/CP latency, mobility) and security (i.e. same or better than current UMTS level)without introducing any unnecessary complexity (e.g. Inter-Node B UP/CP interfaces). This contribution is focusing on the requirements on Network Sharing that is part of the SAE / LTE. (See requirements in TR 23.882 sub clause 5 – "The SAE/LTE systemshall support network sharing functionality…" – and in TR 22.978 subclause 5.1.1.9 second bullet). It is proposed to fulfil the requirements with a simplified Network Sharing architecture compared to Rel-6 Network Sharing. For example, only "supporting UEs" exist on the LTE radio and it should be possible to only support "MOCN configurations". Text proposal is made to TR 23.882 adding a new key issue on Network Sharing.	Revised in S2-060512
7.4.1.3	S2-060482	P-CR	Adding load-sharing / redundancy above the cell site node	Lucent Technologies	23.883	-	-	-	-	-	SAE	In section 5 of TR 23.882 v0.9.0, on "Requirements on the Architecture", one of the requirements one can read is: "The SAE/LTE system shall support redundancy concepts / load sharing of network nodes, e.g. similar to today's Iu-flex mechanisms. All nodes other than cell site node should be considered "distributed resources utilising load sharing/redundancy mechanisms". This contribution aims at reflecting this requirement through some relevant sections of TR 23.882 v0.9.0.	For e-mail approval
7.4.1.3	S2-060483	P-CR	Discussion on Redundancy and Load-sharing	China Mobile	23.882	-	-	-	-	-	SAE	Redundancy is an important mechanism to attain high availability while load-sharing is a mechanism to use resources efficiently. Redundancy and load-sharing are always achieved by similar ways. Some solutions for redundancy and load-sharing are proposed and compared.	For e-mail approval
7.4.1.3	S2-060512	P-CR	Network Sharing aspects for a 2-node 3GPP SAE / LTE architecture	Ericsson	23.882	-	-	-	-	Rel-7	SAE	In recent SA WG2 and RAN WG3 meetings a 2-node 3GPP SAE/LTE architecture were presented. The presented solution meets the SAE / LTE requirements on performance (e.g. UP/CP latency, mobility) and security (i.e. same or better than current UMTS level)without introducing any unnecessary complexity (e.g. Inter-Node B UP/CP interfaces). This contribution is focusing on the requirements on Network Sharing that is part of the SAE / LTE. (See requirements in TR 23.882 sub clause 5 – "The SAE/LTE systemshall support network sharing functionality…" – and in TR 22.978 subclause 5.1.1.9 second bullet). It is proposed to fulfil the requirements with a simplified Network Sharing architecture compared to Rel-6 Network Sharing. For example, only "supporting UEs" exist on the LTE radio and it should be possible to only support "MOCN configurations". Text proposal is made to TR 23.882 adding a new key issue on Network Sharing.	For e-mail approval
7.4.1.3	S2-060527	P-CR	Key issue Optimized MM	NEC, NTT DoCoMo, Motorola	23.882	-	-	-	-	Rel-7	SAE	Mobility Management concepts of S2-060035	For e-mail approval