Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 23.714
Study on
Control and User Plane Separation
of EPC nodes

3GPP‑Page   fToC↓   Partial Content →
V14.0.0 (Wzip)  2016/06  87 p.
Rapporteur:
Mr. Schramm, Mirko
Huawei Technologies Co. Ltd.

full Table of Contents for  TR 23.714  Word version:  14.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 7
2References  p. 7
3Definitions and abbreviations  p. 7
3.1Definitions  p. 7
3.2Abbreviations  p. 8
4Architectural considerations  p. 8
4.1Architectural assumptions and requirements  p. 8
4.2Baseline architecture  p. 8
4.3Existing functionality of S-GW, P-GW and TDF  p. 9
5Key issues  p. 12
5.1Key issue 1 - Functionality split into user plane and control plane functions  p. 12
5.1.1Description  p. 12
5.2Key Issue 2 - Selection mechanism for user plane functional entities  p. 12
5.3Key Issue 3 - Change of user plane session identity (due to other than UE mobility scenarios)  p. 12
5.3.1Description  p. 12
5.3.2Solution requirements  p. 12
5.4Key Issue 4 - Relocation of user plane functional entity due to UE mobility  p. 13
6Solutions  p. 13
6.1Solutions to key issue 1  p. 13
6.1.1Solution 1: Functional split for SGW, PGW and TDF  p. 13
6.1.1.1Overview  p. 13
6.1.1.2Functional split of SGW  p. 13
6.1.1.3Functional split of PGW  p. 16
6.1.1.4Functional split of TDF  p. 18
6.1.1.5Considerations for GTP-U IP address and TEID allocation  p. 20
6.1.1.5.1Description  p. 20
6.1.1.5.2Solution 1: F-TEID-u allocation / release in the user plane function  p. 20
6.1.1.5.3Solution 2: F-TEID-u allocation / release in the control plane function  p. 20
6.1.1.5.4Solution 3: Control plane function providing pre-allocated GTP-U IP address and TEID to the user plane function (during restoration scenario)  p. 20
6.1.1.5.5Evaluations  p. 21
6.1.1.5.6Conclusions  p. 21
6.1.1.6Considerations for online charging, offline charging and usage monitoring  p. 21
6.1.1.6.1Description  p. 21
6.1.1.6.2Solution 1: Charging and usage monitoring handling in the control plane function  p. 22
6.1.1.7Consideration for SGW Service Area and TAI list alignment due to control plane and user plane split of SGW  p. 23
6.1.1.7.1Description  p. 23
6.1.1.7.2Solutions  p. 23
6.1.1.7.3Evaluation  p. 25
6.1.1.7.4Conclusion  p. 26
6.1.1.8Considerations for UE IP address management  p. 26
6.1.1.8.1Description  p. 26
6.1.1.8.2Solution 1: UE IP address management performed by the control plane function  p. 26
6.1.1.8.3Evaluation  p. 28
6.1.1.8.4Conclusion  p. 28
6.1.1.9Considerations for the functionality supported by the user plane function  p. 28
6.1.1.9.1Description  p. 28
6.1.1.9.2Solution 1: Protocol based advertisement of supported functionality by the user plane function  p. 29
6.1.1.10Considerations for supporting extended buffering for the UE in power saving mode  p. 29
6.1.1.10.1Description  p. 29
6.1.1.10.2Solution 1: Supporting extended buffering for the UE in power saving mode in the control plane function  p. 29
6.1.1.10.3Solution 2: Supporting extended buffering for the UE in power saving mode in the user plane function  p. 30
6.1.1.10.4Evaluation  p. 31
6.1.1.10.5Conclusion  p. 32
6.1.1.11Considerations for 3GPP specific information at the user plane function  p. 33
6.1.1.11.1Description  p. 33
6.1.1.11.2Solution 1: Not providing subscriber's or UE's permanent identity to the user plane function  p. 33
6.1.1.12Considerations for performing LI functionality  p. 34
6.1.1.12.1Description  p. 34
6.1.1.12.2Solution 1: Terminating the LI related reference points in the control plane function  p. 34
6.1.1.12.3Solution 2: Lawful interception architecture with the X3 reference points terminating at the user plane function  p. 36
6.1.1.12.4Evaluation  p. 37
6.1.1.12.5Conclusion  p. 38
6.1.1.13Considerations for control of user plane forwarding  p. 39
6.1.1.13.1Description  p. 39
6.1.1.13.2Solution 1: Uniform handling of user plane forwarding to cater for multiple forwarding scenarios  p. 39
6.1.1.14Procedures over Sx Reference Points  p. 43
6.1.1.14.1Sx Management Procedures  p. 43
6.1.1.14.2Sx Session Management Procedures  p. 44
6.1.1.14.3Sx reporting procedure  p. 46
6.1.1.14.4Conclusion  p. 47
6.1.1.15Parameters for Sx Reference Points  p. 47
6.1.1.15.1Parameters related to general UP function management  p. 48
6.1.1.15.2Parameters related to Sx session management  p. 48
6.1.1.15.3Conclusion  p. 52
6.1.1.16Application of Sx session management procedures to existing procedures  p. 52
6.1.1.17Consideration for activation/deactivation of predefined PCC/ADC rules  p. 57
6.1.1.17.1Description  p. 57
6.1.1.17.2Solution 1: Activation/deactivation either in control plane only or in both control plane and user plane  p. 58
6.1.1.17.3Evaluation & Conclusion  p. 58
6.1.2Solution 2: Functional split for combined S/P-GW (key issue #1)  p. 58
6.2Solutions to key issue 2: Selection mechanism for user plane functional entities  p. 59
6.2.1Solution 1 - User plane selection by the control plane of the corresponding functional entity  p. 59
6.2.1.1Description  p. 59
6.2.1.1.1General  p. 59
6.2.1.1.2Entity performing user plane selection  p. 59
6.2.1.1.3Parameters considered during selection mechanism  p. 59
6.2.1.1.4How to realize the selection mechanism  p. 60
6.2.1.1.5Triggers for selection of user plane  p. 60
6.2.1.2Impacts on existing nodes and functionality  p. 60
6.2.1.3Solution Evaluation  p. 61
6.2.2Solution 2 - Combined control plane function selects combined user plane function  p. 61
6.2.2.1Description  p. 61
6.2.2.1.1General  p. 61
6.2.2.1.2Entity performing user plane selection  p. 62
6.2.2.1.3Parameters considered during selection mechanism  p. 62
6.2.2.1.4How to realize the selection mechanism  p. 62
6.2.2.1.5Triggers for selection of user plane  p. 63
6.2.2.2Impacts on existing nodes and functionality  p. 63
6.2.2.3Solution Evaluation  p. 63
6.2.3Evaluation  p. 63
6.2.4Conclusion  p. 63
6.2.4.1Selection of the user plane function  p. 63
6.2.4.2Selection of the collocated PGW and SGW control plane function  p. 64
6.3Solutions to key issue 3: Change of user plane session identity (due to other than UE mobility scenarios)  p. 64
6.3.1Solution 1 - Control plane changing the user plane session identity  p. 64
6.3.1.1Description  p. 64
6.3.1.1.1General  p. 64
6.3.1.1.2Change of user plane session identity  p. 64
6.3.1.1.3SGW: Call flows for control plane changing user plane session identity  p. 64
6.3.1.1.4PGW: Call flows for control plane changing user plane session identity  p. 66
6.3.1.1.5TDF: Call flows for control plane changing user plane session identity  p. 66
6.3.1.2Impacts on existing nodes and functionality  p. 66
6.3.1.3Solution Evaluation  p. 66
6.3.2Solution 2 - SGW-C triggers MME to perform UP session identity change  p. 67
6.3.2.1Description  p. 67
6.3.2.2Impacts on existing nodes and functionality  p. 68
6.3.2.3Solution Evaluation  p. 68
6.3.3Evaluation  p. 68
6.3.4Conclusion  p. 68
6.4Solutions to key issue 4 - Relocation of user plane functional entity due to UE mobility  p. 68
6.4.1Solution 1- Service area alignment of SGW control plane with SGW user plane  p. 68
6.4.1.1General  p. 68
6.4.1.2Descriptions  p. 69
6.4.1.3Call flows  p. 70
6.4.1.3.1S1 based handover with SGW change  p. 70
6.4.1.4Solution Evaluation  p. 72
6.4.2Solution 2 - SGW user plane change triggered during two subsequent procedures  p. 72
6.4.2.1Service Request  p. 72
6.4.3Solution 3 - SGW user plane change during mobility procedure  p. 73
6.4.3.1Service Request  p. 73
6.4.3.2X2-based handover  p. 74
6.4.3.2.1Without Serving GW control plane relocation  p. 74
6.4.3.2.2With Serving GW control plane relocation  p. 74
6.4.3.3S1-based handover  p. 74
6.4.3.3.1Without Serving GW control plane relocation  p. 74
6.4.3.3.2With Serving GW control plane relocation  p. 75
6.4.3.4Impacts on existing nodes and functionality  p. 75
6.4.3.5Solution Evaluation  p. 75
6.4.4Evaluation  p. 75
6.4.5Conclusion  p. 76
7Overall evaluation  p. 76
8Conclusions  p. 76
AExample for interaction between CP and UP function  p. 78
A.1During attach procedure  p. 78
BExample for attributes exchanged between the CP and UP function  p. 81
B.1During the UPlane Session Establishment procedure  p. 81
B.1.1UPlane Session Establishment Request  p. 81
B.1.2Policy Rule  p. 81
B.1.3Bearer Info  p. 82
B.1.4Usage Reporting Rule  p. 84
B.2During the Usage Report generated by UP function  p. 85
$Change History  p. 87

Up   Top