7.4.4
|
-----
|
------
|
Mobility between 3GPP and non-3GPP access (key issue: k)
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.4
|
S2-060051
|
P-CR
|
Mobility support between pre-SAE/LTE 3GPP and non-3GPP access system without Mobile IP
|
Azaire Networks
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper proposes the architecture and the mechanism to support the seamless service continuity between pre-SAE/LTE 3GPP and WLAN without using Mobile IP.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060052
|
DISCUSSION
|
Extendibility of 3GPP-WLAN interworking architecture to support SAE and other wireless ANs
|
Azaire Networks
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper shows how the 3GPP-WLAN interworking architecture can be extended to also support the SAE and other wireless access technologies, e.g. WiMAX.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060055
|
DISCUSSION
|
Discussion on S2 reference point
|
Azaire Networks
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper discusses the points that need to be clarified when the Wi (especially Mobile IP) is supported in S2.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060077
|
P-CR
|
Integrated Mobility Architecture
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
Proposes concepts for Inter-Access mobility arch.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060095
|
P-CR
|
Proposed architecture for inter access system handover between 3GPP and non-3GPP access systems
|
NTT DoCoMo
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Proposes a candidate solution for inter access system handover with information flow
|
Revised in S2-060484
|
7.4.4
|
S2-060122
|
P-CR
|
Mobility between pre-SAE/LTE 3GPP and non 3GPP access systems – Roaming Scenarios using Mobile IP
|
LG Electronics
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Currently the scenarios with GGSN and/or PDG located in the VPLMN are left FFS in TR 23.882. This document highlights the scenarios with GGSN and/or PDG located in the VPLMN and proposes to update the corresponding description in TR 23.882.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060123
|
P-CR
|
Some editorial corrections of TR 23.882
|
LG Electronics
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
First, this contribution proposes editorial corrections for TR 23.882
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060131
|
P-CR
|
Inter access system handover between 3GPP and non 3GPP access systems
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes to combine currently proposed alternatives to the key issue.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060164
|
P-CR
|
Inter-System Mobility Alternate Solutions for Annex E
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
(Postponed from last meeting). This document describes an alternate solution for Inter-System Mobility Management that could go into Annex E of TR 23.882.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060165
|
P-CR
|
Inter Access System Handover between 3GPP and non 3GPP Access Systems Alternate Solutions for section 7.7.3
|
Orange
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document describes an alternate solution for Inter-Access System Handover between 3GPP and non 3GPP Access Systems that could go into section 7.7.3. of TR 23.882.
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060261
|
P-CR
|
Harmonised mobility management: inter 3GPP-non 3GPP access system mobility
|
Telecom Italia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes a mobility management scheme for 3GPP and non 3GPP access system (I-WLAN) mobility.
|
Revised in S2-060485
|
7.4.4
|
S2-060484
|
P-CR
|
Proposed architecture for inter access system handover between 3GPP and non-3GPP access systems
|
NTT DoCoMo
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Proposes a candidate solution for inter access system handover with information flow
|
Not handled. To be re-submitted by Authors
|
7.4.4
|
S2-060485
|
P-CR
|
Harmonised mobility management: inter 3GPP-non 3GPP access system mobility
|
Telecom Italia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes a mobility management scheme for 3GPP and non 3GPP access system (I-WLAN) mobility.
|
Not handled. To be re-submitted by Authors
|
7.4.5
|
-----
|
------
|
One or multiple APNs
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.5
|
S2-060105
|
DISCUSSION
|
Support of Multiple APNs in SAE
|
CATT
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper discusses the effects on Multiple APNs when IP based IMS emergency session should be supported in SAE.
|
Noted
|
7.4.5
|
S2-060132
|
P-CR
|
Use of APNs and IP Gateways in the evolved system
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes clarifications to the key issue Support for Multiple APNs.
|
Revised in S2-060457
|
7.4.5
|
S2-060173
|
P-CR
|
APN use for architecture B
|
Nortel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Describes how APN is used for Architecture B and keep open the possibility to have one or more APNs per UE
|
Noted
|
7.4.5
|
S2-060179
|
P-CR
|
Use cases for multiple APNs
|
Vodafone
|
23.882
|
-
|
-
|
-
|
-
|
-
|
-
|
Discusses this key issue
|
Noted
|
7.4.5
|
S2-060245
|
P-CR
|
Alternative Solutions for Key Issue Support of Multiple APNs
|
Siemens
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Describes alternatives that provide concurrent PDN connectivity for a UE.
|
Noted
|
7.4.5
|
S2-060262
|
P-CR
|
Support of multiple APNs in SAE
|
Telecom Italia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution discusses the need to support multiple APN in SAE to access different services
|
Noted
|
7.4.5
|
S2-060282
|
P-CR
|
Multiple APNs – Key Issue Description
|
Alcatel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes modifications to section 7.10.1 "Description of key issue – support of multiple APNs". In particular it proposes to replace multiple APNs by "multiple access to PDNs/Services" per TS 23.003. It introduces IPv4/IPv6 PDN access issues and roaming issues.
|
Noted
|
7.4.5
|
S2-060283
|
P-CR
|
Multiple APNs – Key Issue Solutions
|
Alcatel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution is intended to describe the potential solutions if the need for access to multiple Packet Data Networks (PDNs) / Services identified by APNs or with different administrative operator, private or corporate network domains via severalIP Gateways is confirmed. It also study the way a UE can access both IPv4 and IPv6 services.
|
Noted
|
7.4.5
|
S2-060284
|
P-CR
|
Multiple APNs – Comparison of alternative solutions
|
Alcatel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution is intended to compare the potential solutions for access to multiple Packet Data Networks (PDNs) / Services described in the companion tdoc "Multiple APNs – Key Issue Solutions".
|
Not handled. To be re-submitted by Authors
|
7.4.5
|
S2-060296
|
WITHDRAWN
|
On Multiple APNs support
|
Lucent Technologies
|
23.883
|
-
|
-
|
-
|
-
|
-
|
SAE
|
On Multiple APNs support
|
WITHDRAWN
|
7.4.5
|
S2-060301
|
WITHDRAWN
|
|
Samsung
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document analyzes support of multiple APNs in the evolved system and its impact with inter-AS handover.
|
|
7.4.5
|
S2-060457
|
P-CR
|
Use of APNs and IP Gateways in the evolved system
|
Nokia, Siemens, Telecom Italia, Lucent, NTT DoCoMo, NEC, Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
The key issue Support for Multiple APNs was created at the SA WG2 Yokosuka meeting. However, there seem to be many alternatives for approaching the issue. This contribution aims at clarifying the principles of how APNs would be used in the SAE accesssystem, and how this relates to IP Gateways. There are also implications to the key issue Default IP Access Service, but the changes in this contribution are limited to removing those FFSs listed under Default IP Access Service that should be addressed under this key issue.
|
Revised in S2-060486
|
7.4.5
|
S2-060486
|
P-CR
|
Use of APNs and IP Gateways in the evolved system
|
Nokia, Siemens, Telecom Italia, Lucent, NTT DoCoMo, NEC, Ericsson, ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
The key issue Support for Multiple APNs was created at the SA WG2 Yokosuka meeting. However, there seem to be many alternatives for approaching the issue. This contribution aims at clarifying the principles of how APNs would be used in the SAE accesssystem, and how this relates to IP Gateways. There are also implications to the key issue Default IP Access Service, but the changes in this contribution are limited to removing those FFSs listed under Default IP Access Service that should be addressed under this key issue.
|
Approved
|
7.4.5
|
S2-060487
|
[LS OUT]
|
[Draft] LS on use cases of IP connectivity with multiple PDNs
|
China Mobile
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
SA WG2 is working on key issue description of concurrent IP connectivity with multiple PDNs and the agreed text in SA WG2 is in S2-060486. SA WG2 has considered following use cases currently. It should be noticed that the combination of use cases hasbeen considered by SA WG2.
|
Revised in S2-060549
|
7.4.5
|
S2-060549
|
LS OUT
|
LS on use cases of IP connectivity with multiple PDNs
|
SA WG2
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
SA WG2 is working on key issue description of concurrent IP connectivity with multiple PDNs and the agreed text in SA WG2 is in S2-060486. SA WG2 has considered following use cases currently. It should be noticed that the combination of use cases hasbeen considered by SA WG2.
|
Approved
|
|
