7.4
|
-----
|
------
|
3GPP System Architecture Evolution [SAE]
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4
|
S2-060031
|
LS In
|
Reply LS (from SA WG3) on Security Aspects of Long Term Evolved RAN/3GPP System Architecture Evolution
|
SA WG3 (S3-050843, Vodafone)
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
At SA WG3#41 several company contributions on security aspects of LTE/SAE were presented and discussed. Many of the contributions provide an initial study into the security threats and requirements. Some of the contributions also provide an indication of the types of security solutions that could be considered. Based on the discussion at SA WG3#41, some agreements were reached which are reflected below in the responses to the LSs from SA WG2. SA WG2 are asked to take the response from SA WG3 into account.
|
Noted
|
7.4
|
S2-060049
|
P-CR
|
Operator Controlled QoS
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
It is proposed to simplify QoS and the resource reservation architecture. An operator controlled QoS mechanism which is supported by a network centric QoS configuration and filter instalment in the UE entity is presented.. Updates to the Key isse forQoS concepts is proposed.
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060050
|
P-CR
|
Simplified QoS model by using a class based approach
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
The possibilities for a simplified QoS architecture by using a class based approach is explained. Updates to the Key isse for QoS concepts is proposed.
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060053
|
P-CR
|
Clarification on the scope of service continuity support at SAE
|
Azaire Networks, NTT DoCoMo
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper intends to clarify the scope of service continuity support at SAE.
|
Revised in S2-060391
|
7.4
|
S2-060084
|
LS In
|
LS from SA WG3: Security implications of RAN LTE control plane architectural alternatives
|
SA WG3 (S3-050874, Vodafone, Nortel)
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
SA WG3 believe that there are still no security showstoppers that would prevent any of the proposed architectures from being selected. An important factor when comparing the options is the level of security required to protect the RRC protocol. If, according to the working assumption in the previous paragraph, RRC needs a high level of confidentiality or integrity protection, then option 2 is preferable from a security point of view, but both options 1 and 3 could be adequately secured, possiblyat a higher cost compared with securing option 2. If it turns out that RRC does not need a high level of confidentiality or integrity protection, or even that RRC requires no additional protection, then SA WG3 would not have any strong preference over which option is selected. This was copied to SA WG2 for information.
|
Noted
|
7.4
|
S2-060116
|
LS In
|
Reply LS (from SA WG3) on Security Requirements for Long Term Evolved RAN/3GPP System Architecture Evolution
|
SA WG3 (S3-050842, Nokia)
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
SA WG3 would like to inform RAN WG2 and RAN WG3 that SA WG3 is fine with having a joint meeting with RAN WG2 and RAN WG3. An appropriate date could be Tuesday 10th January in the afternoon and Wednesday 11th January in the morning. This was copied toSA WG2 for information.
|
Noted
|
7.4
|
S2-060128
|
P-CR
|
Clarification of Functions in the evolved core network
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution clarifies the descriptions of evolved core network functions.
|
Revised in S2-060392
|
7.4
|
S2-060166
|
DISCUSSION / APPROVAL
|
SAE Requirements for Interworking with CS Domain and Services
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
System Architecture System studies the evolution of packet switched domain/network of 3GPP systems and its interworking with non-3GPP access systems. On the other hand, services supported via CS domain/network have been and will continue to be of significance to operators as well as to end users. In addition, many important work items have also been studied in 3GPP for efficient support of interworking, mobility and service combinations between CS domain and the PS domain such as VCC and CSI andthey are expected to continue to work with the evolved System Architecture. As an important consideration of migration and evolution for System Architecture, it is proposed to include the support of CS switched services and its interworking as wellas mobility with the PS system in the SAE requirements.
|
Revised in S2-060501
|
7.4
|
S2-060167
|
P-CR
|
The Base Scenarios for inter-3GPP and non-3GPP System Mobility
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
As an important deployment and operation principle for mobility between 3GPP and non-3GPP access system, 3GPP systems should be the anchor point for mobility control and traffic forwarding for handover/mobility to/from the non-3GPP access systems. This contribution proposes to include the base scenario for mobility between 3GPP and non-3GPP access systems to comply with this principle.
|
Revised in S2-060507
|
7.4
|
S2-060168
|
NOT USED
|
Spare
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
NOT USED
|
|
7.4
|
S2-060175
|
TR
|
TR23.882 v0.9.0
|
Vodafone
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Latest version
|
Noted
|
7.4
|
S2-060176
|
Workplan
|
Timeplan for SAE
|
Vodafone
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Latest version.
|
Revised in S2-060389
|
7.4
|
S2-060183
|
REPORT
|
Outcome of joint R2-R3-S3 meeting 10-11/1/06
|
Vodafone (SAE rapporteur)
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
this provides the outcome of the joint meeting as documented in R3-060081.
|
Noted
|
7.4
|
S2-060236
|
P-CR
|
Gi reference point clarification for SAE architecture
|
Azaire Networks
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper clarifies the Gi reference point to cover other access networks.
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060240
|
P-CR
|
Key issue – IP versions
|
China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE-
|
IP versions will introduce interoperability problems and one solution is proposed.
|
Revised in S2-060394
|
7.4
|
S2-060243
|
P-CR
|
Discussion on Redundancy
|
China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE-
|
Opening the discussion of redundancy.
|
Revised in S2-060399
|
7.4
|
S2-060252
|
P-CR
|
Discussion on PCEF Allocation
|
Siemens
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Discusses the two alternatives for the allocation of the Policy and Charging Enforcement Function (PCEF).
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060285
|
P-CR
|
SAE inter node security
|
Alcatel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
User access security is already treated in SAE. This contribution is intend to outline the need to introduce also network security communications means inside SAE
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060289
|
WITHDRAWN
|
Network Sharing aspects for a 2-node 3GPP SAE / LTE architecture
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution is focusing on the requirements on Network Sharing that is part of the SAE/LTE. It is proposed to fulfil the requirements with a simplified Network Sharing architecture compared to Rel-6 Network Sharing.
|
WITHDRAWN
|
7.4
|
S2-060312
|
LS In
|
LS on involvement of ASGW during handover preparation
|
RAN WG3 (R3-060086, Nortel)
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
RAN WG3 has analysed call flows of intra-access mobility in active mode for LTE during RAN WG3#50. In particular RAN WG3 has discussed some solutions for the handover preparation phase where the source eNodeB directly contacts the target eNodeB in order to reserve some resources before the actual handover execution. The question arose regarding to which extend the ASGW must be involved during this phase. ASGW is defined as the entity comprising MME, UPE and inter-access anchor independently of how they are distributed. RAN WG3 concluded that network resources are involved and not only radio resources but possibly also resources between eNodeB and ASGW must be granted. RAN WG3 also identified an interdependency of that issue to the inter-access mobility in LTE_ACTIVE case and to the question whether the ASGW is changed during intra-access mobility in LTE_ACTIVE. This particular conclusion was made also by analogy with the SGSN involvement in the 3g inter-SGSN relocation in release 6. However, for the intra-ASGW handover, RAN WG3 would appreciate the opinion of SA WG2 since in some proposed solutions the handover preparation procedure was directly between the two eNodeBs without involving the ASGW. However it was felt by some companies that the ASGW would need to be involved also in this scenario, for example because of the resource allocation process between the ASGW and the target eNodeB. Another example could be to enable to re-negotiate the QoS at target side taking into account service consideration. SA WG2 may see some other reasons. RAN WG3 also assumes that the intra-ASGW scenario is the most expected scenario due to the flex nature of the ASGW-eNodeB interface and consequently the answer is of great importance. RAN WG3 ask SA WG2 to provide back their opinion on the possible involvement of the ASGW in the handover preparation phase of the intra-ASGW scenario and the reasons behind.
|
Postponed to meeting #51
|
7.4
|
S2-060319
|
P-CR
|
Proposed update to TR 23.882 documenting outcome of joint R2-R3-S3 meeting 10-11/1/06
|
Vodafone (SAE rapporteur)
|
23.882
|
-
|
-
|
-
|
0.9.0
|
Rel-7
|
SAE
|
Following the outcome of the joint RAN WG2-RAN WG3-SA WG3 meeting on the security issues for SAE/LTE, it is proposed that the revision marked changes are made to TR 23.882 v0.9.0.
|
Approved
|
7.4
|
S2-060389
|
WORK PLAN
|
Updated Timeplan for SAE
|
Drafting Group Chairman (Vodafone)
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Updated latest version.
|
Revised in S2-060546
|
7.4
|
S2-060391
|
P-CR
|
Clarification on the scope of service continuity support at SAE
|
Azaire Networks, NTT DoCoMo
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper intends to clarify the scope of service continuity support at SAE.
|
Noted
|
7.4
|
S2-060392
|
P-CR
|
Clarification of Functions in the evolved core network
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
A list of functions in the evolved core network has been presented in the previous SA WG2 meetings, for the purpose of grouping these functions in the proposed architecture alternatives. This contribution proposes changes to the descriptions of the functions.
|
Revised in S2-060488
|
7.4
|
S2-060394
|
P-CR
|
Key issue – Mobility between IP versions
|
China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
IP versions will introduce interoperability problems.
|
Revised in S2-060500
|
7.4
|
S2-060488
|
P-CR
|
Clarification of Functions in the evolved core network
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
A list of functions in the evolved core network has been presented in the previous SA WG2 meetings, for the purpose of grouping these functions in the proposed architecture alternatives. This contribution proposes changes to the descriptions of the functions.
|
Approved
|
7.4
|
S2-060500
|
P-CR
|
Key issue – Mobility between IP versions
|
China Mobile, Huawei, Nokia?
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Abstract of the contribution: Different IP versions will introduce interoperability problems. Requirements are proposed regarding IPv4 and IPv6 interworking.
|
Revised in S2-060554
|
7.4
|
S2-060501
|
DISCUSSION / APPROVAL
|
SAE Requirements for Interworking with CS Domain and Services
|
Orange SA, TeliaSonera, 3G, China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
System Architecture System studies the evolution of packet switched domain/network of 3GPP systems and its interworking with non-3GPP access systems. On the other hand, services supported via CS domain/network have been and will continue to be of significance to operators as well as to end users. In addition, many important work items have also been studied in 3GPP for efficient support of interworking, mobility and service combinations between CS domain and the PS domain such as VCC and CSI andthey are expected to continue to work with the evolved System Architecture. As an important consideration of migration and evolution for System Architecture, it is proposed to include the support of CS switched services and its interworking as wellas mobility with the PS system in the SAE requirements.
|
Revised in S2-060522
|
7.4
|
S2-060507
|
P-CR
|
The Base Scenarios for inter-3GPP and non-3GPP System Mobility
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
As an important deployment and operation principle for mobility between 3GPP and non-3GPP access system, 3GPP systems should be the anchor point for mobility control and traffic forwarding for handover/mobility to/from the non-3GPP access systems. This contribution proposes to include the base scenario for mobility between 3GPP and non-3GPP access systems to comply with this principle.
|
Not handled. To be re-submitted by Authors
|
7.4
|
S2-060522
|
DISCUSSION / APPROVAL
|
SAE Requirements for Interworking with CS Domain and Services
|
Orange SA, TeliaSonera, 3G, China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
System Architecture System studies the evolution of packet switched domain/network of 3GPP systems and its interworking with non-3GPP access systems. On the other hand, services supported via CS domain/network have been and will continue to be of significance to operators as well as to end users. In addition, many important work items have also been studied in 3GPP for efficient support of interworking, mobility and service combinations between CS domain and the PS domain such as VCC and CSI andthey are expected to continue to work with the evolved System Architecture. As an important consideration of migration and evolution for System Architecture, it is proposed to include the support of CS switched services and its interworking as wellas mobility with the PS system in the SAE requirements.
|
Revised in S2-060532
|
7.4
|
S2-060532
|
DISCUSSION / APPROVAL
|
SAE Requirements for Interworking with CS Domain and Services
|
Orange SA, TeliaSonera, 3, China Mobile, Telecom Italia, T-Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
System Architecture System studies the evolution of packet switched domain/network of 3GPP systems and its interworking with non-3GPP access systems. On the other hand, services supported via CS domain/network have been and will continue to be of significance to operators as well as to end users. In addition, many important work items have also been studied in 3GPP for efficient support of interworking, mobility and service combinations between CS domain and the PS domain such as VCC and CSI andthey are expected to continue to work with the evolved System Architecture. As an important consideration of migration and evolution for System Architecture, it is proposed to include the support of CS switched services and its interworking as wellas mobility with the PS system in the SAE requirements.
|
Revised to S2-060547
|
7.4
|
S2-060546
|
WORK PLAN
|
Updated Timeplan for SAE
|
Drafting Group Chairman (Vodafone)
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Updated latest version.
|
Approved
|
7.4
|
S2-060547
|
DISCUSSION / APPROVAL
|
SAE Requirements for Interworking with CS Domain and Services
|
Orange SA, TeliaSonera, 3, China Mobile, Telecom Italia, T-Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
System Architecture System studies the evolution of packet switched domain/network of 3GPP systems and its interworking with non-3GPP access systems. On the other hand, services supported via CS domain/network have been and will continue to be of significance to operators as well as to end users. In addition, many important work items have also been studied in 3GPP for efficient support of interworking, mobility and service combinations between CS domain and the PS domain such as VCC and CSI andthey are expected to continue to work with the evolved System Architecture. As an important consideration of migration and evolution for System Architecture, it is proposed to include the support of CS switched services and its interworking as wellas mobility with the PS system in the SAE requirements.
|
Noted
|
7.4
|
S2-060554
|
P-CR
|
Key issue – Mobility between IP versions
|
China Mobile, Huawei, Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Abstract of the contribution: Different IP versions will introduce interoperability problems. Requirements are proposed regarding IPv4 and IPv6 interworking.
|
For e-mail approval
|
|
