7.4.1
|
-----
|
------
|
LTE idle mobility (key issue: d)
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.1
|
S2-060086
|
P-CR
|
Idle Mobility and Tracking Area Concept in SAE / LTE
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
This contribution proposes a high-level solution for how the idle mode mobility and tracking area concept should be look like in SAE / LTE. The solution is to a large extent independent of the detailed SAE architecture assumptions and uses the terminology of the converged SAE architecture in 3GPP TR 23.882. This contribution has also been submitted to the RAN WG3 #50 meeting, with text proposal in section to 23.882.
|
Revised in S2-060393
|
7.4.1
|
S2-060129
|
P-CR
|
Mobility Management in LTE_IDLE state
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document presents the LTE_IDLE state mobility management principles and procedures. The contents of this contribution have also been submitted to RAN WG3 #50 meeting, because at the RAN WG3 meeting #48bis Nokia agreed to submit a more comprehensive document on further details of the mobility management in LTE_IDLE state for E-UTRAN. Thus the contribution also contains changes to the TR 23.882 that according to the work split between the working groups is the responsibility of the RAN WGs.
|
Some parts in S2-060395. MM parts for LTE/SAE meeting
|
7.4.1
|
S2-060146
|
DISCUSSION / APPROVAL
|
Paging method between E-UTRA and UTRA/ GERA
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This paper proposes a solution for the issue under the concept of Equivalent RA and SGSN Proxy between E-UTRAN and UTRAN/GERAN.
|
Revised in S2-060307
|
7.4.1
|
S2-060147
|
WITHDRAWN
|
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution clarifies the concept for the equivalent routeing area.
|
|
7.4.1
|
S2-060148
|
DISCUSSION / APPROVAL
|
Equivalent Routing Area Identifying
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
this document proposes to set up a "RAI pool" in MS and UP-GW/CP-GW to identify an Equivalent Routing Area.
|
Revised in S2-060308
|
7.4.1
|
S2-060208
|
P-CR
|
Inter 3GPP Access System Mobility in Idle State
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
Because a SAE-capable UE may not have a basic IP bearer within 2G/3G system in idle state before a change from 2G/3G to SAE/LTE taking place. Therefore, no always-on IP connectivity can be enabled after a SAE-capable UE enters into SAE/LTE system inthe above case if the present solution applied. This paper presents an amended solution for Inter 3GPP Access System Mobility in idle State to overcome the above flaw.
|
Revised in S2-060503
|
7.4.1
|
S2-060307
|
DISCUSSION / APPROVAL
|
Paging method between E-UTRA and UTRA/ GERA
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes a solution for the issue under the concept of Equivalent RA and SGSN Proxy between E-UTRAN and UTRAN/GERAN.
|
Revised in S2-060477
|
7.4.1
|
S2-060308
|
DISCUSSION / APPROVAL
|
Equivalent Routing Area Identifying
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes to set up a "RAI pool" in MS and UP-GW/CP-GW to identify an Equivalent Routing Area.
|
Revised in S2-060502
|
7.4.1
|
S2-060316
|
P-CR
|
Mobility Management in LTE_IDLE state
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
S2-060129 presents the LTE_IDLE state mobility management principles and procedures. This document aims to add an MM state transition procedure to S2-060129. Also some clarifications are added.
|
Update procedures part separated out in S2-060395.
|
7.4.1
|
S2-060393
|
P-CR
|
Idle Mobility and Tracking Area Concept in SAE / LTE
|
Ericsson
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
This contribution proposes a high-level solution for how the idle mode mobility and tracking area concept should be look like in SAE / LTE. The solution is to a large extent independent of the detailed SAE architecture assumptions and uses the terminology of the converged SAE architecture in 3GPP TR 23.882. This contribution has also been submitted to the RAN WG3 #50 meeting, with text proposal in section to 23.882.
|
Approved
|
7.4.1
|
S2-060395
|
P-CR
|
Mobility Management in LTE_IDLE state
|
Nokia
|
24.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document presents the LTE_IDLE state mobility management principles and procedures. It is a new version of S2-060129 updated based on the discussions in SA WG2#50 to only contain the signalling flow for updating the Tracking Area in LTE_IDLE.
|
Revised in S2-060523
|
7.4.1
|
S2-060396
|
WITHDRAWN
|
Inter 3GPP Access System Mobility in Idle State
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
Because a SAE-capable UE may not have a basic IP bearer within 2G/3G system in idle state before a change from 2G/3G to SAE/LTE taking place. Therefore, no always-on IP connectivity can be enabled after a SAE-capable UE enters into SAE/LTE system inthe above case if the present solution applied. This paper presents an amended solution for Inter 3GPP Access System Mobility in idle State to overcome the above flaw.
|
WITHDRAWN
|
7.4.1
|
S2-060398
|
WITHDRAWN
|
Equivalent Routing Area Identifying
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes to set up a "RAI pool" in MS and UP-GW/CP-GW to identify an Equivalent Routing Area.
|
WITHDRAWN
|
7.4.1
|
S2-060477
|
P-CR
|
Paging method between E-UTRA and UTRA/ GERA
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes a solution for the issue under the concept of Equivalent RA and SGSN Proxy between E-UTRAN and UTRAN/GERAN.
|
Approved
|
7.4.1
|
S2-060502
|
P-CR
|
Equivalent Routing Area Identifying
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes to set up a "RAI pool" in MS and UP-GW/CP-GW to identify an Equivalent Routing Area.
|
Revised in S2-060525
|
7.4.1
|
S2-060503
|
P-CR
|
Inter 3GPP Access System Mobility in Idle State
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
Because a SAE-capable UE may not have a basic IP bearer within 2G/3G system in idle state before a change from 2G/3G to SAE/LTE taking place. Therefore, no always-on IP connectivity can be enabled after a SAE-capable UE enters into SAE/LTE system inthe above case if the present solution applied. This paper presents an amended solution for Inter 3GPP Access System Mobility in idle State to overcome the above flaw.
|
Revised in S2-060524
|
7.4.1
|
S2-060523
|
P-CR
|
Mobility Management in LTE_IDLE state
|
Nokia
|
24.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document presents the LTE_IDLE state mobility management principles and procedures. It is a new version of S2-060129 updated based on the discussions in SA WG2#50 to only contain the signalling flow for updating the Tracking Area in LTE_IDLE.
|
Approved
|
7.4.1
|
S2-060524
|
P-CR
|
Inter 3GPP Access System Mobility in Idle State
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
Because a SAE-capable UE may not have a basic IP bearer within 2G/3G system in idle state before a change from 2G/3G to SAE/LTE taking place. Therefore, no always-on IP connectivity can be enabled after a SAE-capable UE enters into SAE/LTE system inthe above case if the present solution applied. This paper presents an amended solution for Inter 3GPP Access System Mobility in idle State to overcome the above flaw.
|
For e-mail approval
|
7.4.1
|
S2-060525
|
P-CR
|
Equivalent Routing Area Identifying
|
ZTE
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document proposes to set up a "RAI pool" in MS and UP-GW/CP-GW to identify an Equivalent Routing Area.
|
Approved
|
|
