7.4.6
|
-----
|
------
|
Separation of C/U-plane key (issue: n)
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.6
|
S2-060126
|
P-CR
|
CP and UP separation in Core Network
|
Motorola
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes to add a section to TR 23.882 and a solution option to capture the key issue of CP and UP separation. The contribution proposes to create two entities in the core-network (AGW-CP, AGW-UP).
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060133
|
P-CR
|
MME, UPE and Inter-AS Anchor in the evolved architecture
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes clarifications to MME and UPE definitions and to the grouping of evolved core network functions.
|
Revised in S2-060458
|
7.4.6
|
S2-060172
|
P-CR
|
Standardized interface between MME and UPE in SAE
|
Nortel
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Argues in favour of a standardized interface between MME and UPE
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060242
|
P-CR
|
Discussion on Control and User Plane Split
|
China Mobile
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE-
|
Advantages of separation of control plane and user plane are proposed.
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060246
|
DISCUSSION
|
Discussion on Separation of C- and U-Plane Functions
|
Siemens
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Discusses advantage and drawbacks of separating SAE entities into C- and U-plane entities.
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060251
|
DISCUSSION
|
Grouping of Core Network Entities
|
Siemens
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Analyses different possible combinations of these functional entities in network nodes. Advantages and disadvantages are listed and discussed.
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060302
|
P-CR
|
Analysis of CP/UP gateway separation
|
Samsung
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This document analyzes pros and cons of UP/CP separation and propose a combined MME/UPE for simplicity.
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060458
|
P-CR
|
MME, UPE and Inter-AS Anchor in the evolved architecture
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
This contribution proposes clarifications to MME and UPE definitions and to the grouping of evolved core network functions.
|
Not handled. To be re-submitted by Authors
|
7.4.6
|
S2-060489
|
P-CR
|
UPE, MME and Inter-AS Anchor definitions
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Contributions proposing various architecture solution alternatives to the grouping of evolved packet core functions have been presented in the SAE discussions. In this discussion it is important to agree on what the commonly used logical entities UPE, MME and Inter-AS Anchor contain in terms of evolved packet core functions. This contribution proposes to define those entities by allocating the functions presented in S2-060488 to them.
|
Revised in S2-060504
|
7.4.6
|
S2-060504
|
P-CR
|
UPE, MME and Inter-AS Anchor definitions
|
Nokia
|
23.882
|
-
|
-
|
-
|
-
|
-
|
SAE
|
Contributions proposing various architecture solution alternatives to the grouping of evolved packet core functions have been presented in the SAE discussions. In this discussion it is important to agree on what the commonly used logical entities UPE, MME and Inter-AS Anchor contain in terms of evolved packet core functions. This contribution proposes to define those entities by allocating the functions presented in S2-060488 to them.
|
For e-mail approval
|
7.4.7
|
-----
|
------
|
Update of the Architecture in 4.2 (e.g. due the resolution of the key issues above)
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.7
|
S2-060213
|
DISCUSSION/ APPROVAL
|
Analyse of the Interface between UTRAN and Evolved Packet Core
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
This paper first analyses the usage of the interface between UTRAN and evolved packet core and proposes that the interface between UTRAN and evolved packet core should be added in Figure 4.2-1.
|
Not handled. To be re-submitted by Authors
|
7.4.7
|
S2-060214
|
DISCUSSION/ APPROVAL
|
Implementation of the Interface between UTRAN and Evolved Packet Core
|
Huawei
|
23.882
|
-
|
-
|
-
|
-
|
Rel-7
|
SAE
|
This paper introduces the implementation of the interface between UTRAN and the Evolved Packet Core.
|
Not handled. To be re-submitted by Authors
|
7.4.8
|
-----
|
------
|
Update RAN-CN split e.g. due to progress in the meeting, due to security related decisions (R2/R3/SA3 meeting) etc..
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.4.8
|
S2-060106
|
DISCUSSION
|
The Location of IP Header Compression Function in SAE
|
CATT
|
-
|
-
|
-
|
-
|
-
|
-
|
SAE
|
In this paper, the IP header compression function located in CN and in RAN is discussed separately.
|
Not handled. To be re-submitted by Authors
|
7.5
|
-----
|
------
|
Communication Service ID [ServID]
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
7.5
|
S2-060070
|
P-CR
|
Administration of IMS communication service identifiers
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Clean up of requirements for administration of Serv Id
|
Merged proposal in S2-060465
|
7.5
|
S2-060071
|
P-CR
|
Addressing of “other means to identify IMS communication services”
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Concludes that there have been no other alternative proposals for Serv Id and as such the TR is updated to reflect that
|
Approved
|
7.5
|
S2-060072
|
P-CR
|
Clarification to Figure 5-1
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Updates the diagram 5.1 with the proper default notation
|
Approved
|
7.5
|
S2-060074
|
P-CR
|
Conclusion to TR 23.816
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Proposes to conclude the work with the findings already documented in the TR
|
Revised in S2-060470
|
7.5
|
S2-060075
|
[CR]
|
Proposed CR0547 to 23.228: Introduction of IMS application reference to TS 23.228 (Rel-7)
|
Ericsson
|
23.228
|
0547
|
-
|
B
|
7.2.0
|
Rel-7
|
ServID
|
Introduces the Application reference to the TS
|
Revised in S2-060469
|
7.5
|
S2-060098
|
P-CR
|
Propose Service Id Format
|
Motorola
|
23.816
|
-
|
-
|
-
|
-
|
-
|
-
|
This contribution proposes to utilize the IETF RFC 2506 "Media Feature Tag Registration Procedure" for defining the service id format for IMS communication service.
|
Revised in S2-060466
|
7.5
|
S2-060099
|
Approval
|
Proposal Service Id Administrative
|
Motorola
|
-
|
-
|
-
|
-
|
-
|
-
|
ServID
|
This contribution proposes to utilize the IETF RFC 2506 “Media Feature Tag Registration Procedure” for defining the service id and register the service id with the Internet Assigned Numbers Authority (IANA) as a centralized database for IMS communication service.
|
Merged proposal in S2-060465
|
7.5
|
S2-060149
|
P-CR
|
Amendments to requirements
|
Nokia
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
This contribution adds requirements on interoperability related issues
|
Revised in S2-060467
|
7.5
|
S2-060233
|
[CR]
|
Proposed CR0565 to 23.228: Clarification for requirement of IMS communication service identifier on interworking conditions (Rel-7)
|
Huawei
|
23.228
|
0565
|
-
|
B
|
7.2.0
|
Rel-7
|
ServID
|
For taking into account to support interworking with other networks when IMS communication service identifier is adopted in IM CN subsystem.
|
Noted
|
7.5
|
S2-060465
|
P-CR
|
Administration of IMS communication service identifiers
|
Ericsson, Motorola
|
23.816
|
-
|
-
|
-
|
-
|
-
|
ServID
|
An important aspect of the identification of the IMS communication services is the administration of the IMS communication service identifier values. Section 6.1 of TR 23.816 describes some of the requirements for the administration of the IMS communication service identifier and so far the actual means to perform the administration have not been addressed. While the final mechanism for the administration of the IMS communication service identifier is a stage 3 issue, the TR should provide someassistance in this manner by at least identifying some possibilities. This contribution addresses the issue of the administration of the IMS communication services.
|
For e-mail approval
|
7.5
|
S2-060466
|
P-CR
|
Propose Service Id Format
|
Motorola
|
23.816
|
-
|
-
|
-
|
-
|
-
|
ServID
|
This contribution proposes to indicate the IETF RFC 2506 "Media Feature Tag Registration Procedure" for defining the service id format for IMS communication service.
|
Approved
|
7.5
|
S2-060467
|
P-CR
|
Amendments to requirements
|
Nokia
|
23.816
|
-
|
-
|
-
|
-
|
-
|
ServID
|
This contribution adds requirements on interoperability related issues
|
For e-mail approval
|
7.5
|
S2-060468
|
CR
|
Proposed CR0567 to 23.228: Architectural requirements for the IMS communication identifier (Rel-7)
|
Nokia
|
23.228
|
0567
|
-
|
F
|
7.2.0
|
Rel-7
|
ServID
|
Summary of change: The list of architectural requirements is appended with points to cover interoperability and interworking aspects.
|
For e-mail approval
|
7.5
|
S2-060469
|
CR
|
Proposed CR0547R1 to 23.228: Introduction of IMS application reference to TS 23.228 (Rel-7)
|
Ericsson
|
23.228
|
0547
|
1
|
B
|
7.2.0
|
Rel-7
|
ServID
|
Introduces the Application reference to the TS
|
Approved
|
7.5
|
S2-060470
|
P-CR
|
Conclusion to TR 23.816
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Proposes to conclude the work with the findings already documented in the TR
|
Revised in S2-060550
|
7.5
|
S2-060550
|
P-CR
|
Conclusion to TR 23.816
|
Ericsson
|
23.816
|
-
|
-
|
-
|
-
|
Rel-7
|
ServID
|
Proposes to conclude the work with the findings already documented in the TR
|
Approved
|
|
