Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 29.844
Word version: 14.0.0
1…
2…
2
References
3
Definitions, symbols and abbreviations
4
Architecture and requirements
5
Restoration
6
Load control
7
Overload control
8
Path management and path failure handling
9
Error handling on the user plane
$
Change History
2
References
p. 7
3
Definitions, symbols and abbreviations
p. 7
3.1
Definitions
p. 7
3.2
Abbreviations
p. 8
4
Architecture and requirements
p. 8
5
Restoration
p. 9
5.1
Introduction
p. 9
5.2
Solutions for SGW-C failure with and without restart
p. 9
5.2.1
Introduction
p. 9
5.2.2
SGW-C failure with restart
p. 10
5.2.2.1
SGW-C failure with restart - Solution #1
p. 10
5.2.2.1.1
Solution Description
p. 10
5.2.2.1.2
Evaluation and conclusion
p. 12
5.2.3
SGW-C failure without restart
p. 12
5.2.3.1
SGW-C failure without restart - Solution #1, clear resources
p. 12
5.2.3.1.1
Solution Description
p. 12
5.2.3.1.2
Evaluation and conclusion
p. 14
5.2.3.2
SGW-C failure without restart - Solution #2, restore PDN connection
p. 15
5.2.3.2.1
Solution Description
p. 15
5.2.3.2.2
Evaluation and conclusion
p. 16
5.3
Solutions for SGW-U failure with and without restart
p. 16
5.3.1
Introduction
p. 16
5.3.2
SGW-U Failure with Restart
p. 16
5.3.2.1
SGW-U Failure With Restart - Solution #1: SGW-C Recreating the User Plane Sessions in Restarted SGW-U on Reactive Basis
p. 16
5.3.2.1.1
Solution Description
p. 16
5.3.2.1.2
Solution Evaluation
p. 18
5.3.3
SGW-U Failure Without Restart
p. 19
5.3.3.1
SGW-U Failure Without Restart - Solution #1: SGW-C Recreating the User Plane Sessions in a New SGW-U, without change of GTP-U endpoint
p. 19
5.3.3.1.1
Solution Description
p. 19
5.3.3.1.2
Solution Evaluation
p. 19
5.3.3.2
SGW-U Failure Without Restart - Solution #2: SGW-C Recreating the User Plane Sessions in Other Existing SGW-U, with change of GTP-U endpoint
p. 20
5.3.3.2.1
Solution Description
p. 20
5.3.3.2.2
Solution Evaluation
p. 21
5.4
Solutions for PGW-C failure with and without restart
p. 21
5.4.1
Introduction
p. 21
5.4.2
PGW-C Failure With Restart
p. 22
5.4.2.1
PGW-C Failure With Restart Solution #1, Clear resources
p. 22
5.4.2.1.1
Solution Description
p. 22
5.4.2.1.2
Evaluation and conclusion
p. 23
5.4.3
PGW-C Failure Without Restart
p. 23
5.4.3.1
PGW-C Failure Without Restart Solution #1, clear resources
p. 23
5.4.3.1.1
Solution Description
p. 23
5.4.3.1.2
Evaluation and conclusion
p. 24
5.5
Solutions for PGW-U failure with and without restart
p. 24
5.5.1
Introduction
p. 24
5.5.2
PGW-U Failure With Restart
p. 24
5.5.2.1
PGW-U Failure With Restart - Solution#1: PGW-C Recreating the User Plane Sessions in Restarted PGW-U on Reactive Basis
p. 24
5.5.2.1.1
Solution Description
p. 24
5.5.2.1.2
Solution Evaluation
p. 26
5.5.3
PGW-U Failure Without Restart
p. 27
5.5.3.1
PGW-U Failure Without Restart - Solution #1: PGW-C Recreating the User Plane Sessions in a New PGW-U, without change of GTP-U endpoint
p. 27
5.5.3.1.1
Solution Description
p. 27
5.5.3.1.2
Solution Evaluation
p. 28
5.5.3.2
PGW-U Failure Without Restart - Solution #2: PGW-C Recreating the User Plane Sessions in Other Existing PGW-U, with change of GTP-U endpoint
p. 28
5.5.3.2.1
Solution Description
p. 28
5.5.3.2.2
Solution Evaluation
p. 29
5.6
Solutions for TDF-C failure with and without restart
p. 30
5.6.1
Introduction
p. 30
5.6.2
Solutions for TDF-C failure with restart
p. 30
5.6.2.1
TDF-C failure with restart Solution #1, clear resources
p. 30
5.6.2.1.1
Solution Description
p. 30
5.6.2.1.2
Evaluation and conclusion
p. 31
5.6.3
Solutions for TDF-C failure without restart
p. 31
5.6.3.1
TDF-C failure without restart Solution #1, clear resources
p. 31
5.6.3.1.1
Solution Description
p. 31
5.6.3.1.2
Evaluation and conclusion
p. 31
5.7
Solutions for TDF-U failure with and without restart
p. 32
5.7.1
Introduction
p. 32
5.7.2
TDF-U failure with restart
p. 32
5.7.2.1
TDF-U failure with restart Solution #1, TDF-C Recreating the User Plane Sessions in Restarted TDF-U on Reactive Basis
p. 32
5.7.2.1.1
Solution Description
p. 32
5.7.2.1.2
Solution Evaluation
p. 34
5.7.3
TDF-U failure without restart
p. 34
5.7.3.1
TDF-U failure without restart Solution #1, TDF-C Recreating the User Plane Sessions in a New TDF-U
p. 34
5.7.3.1.1
Solution Description
p. 34
5.7.3.1.2
Solution Evaluation
p. 35
5.8
Detection of a PFCP entity restart
p. 35
5.8.1
Introduction
p. 35
5.8.2
Solution 1 - Based on the timestamp of the restart
p. 35
5.9
Solutions for SGW-C partial failure
p. 36
5.9.1
Introduction
p. 36
5.9.2
Solution 1: storing FQ-CSID of control plane nodes in the user plane function
p. 36
5.9.2.1
Solution Description
p. 36
5.9.2.2
Evaluation and conclusion
p. 37
5.10
Solutions for PGW-C partial failure
p. 38
5.10.1
Introduction
p. 38
5.10.2
Solution 1: storing FQ-CSID of control plane nodes in the user plane function
p. 38
5.10.2.1
Solution Description
p. 38
5.10.2.2
Evaluation and conclusion
p. 39
5.11
Solutions for SGW-U partial failure
p. 40
5.11.1
Introduction
p. 40
5.11.2
Solution 1: storing FQ-CSID of user plane nodes in the control plane nodes
p. 40
5.11.2.1
Solution Description
p. 40
5.11.2.2
Evaluation and conclusion
p. 41
5.12
Solutions for PGW-U partial failure
p. 41
5.12.1
Introduction
p. 41
5.12.2
Solution 1: storing FQ-CSID of user plane nodes in the control plane nodes
p. 42
5.12.2.1
Solution Description
p. 42
5.12.2.2
Evaluation and conclusion
p. 43
5.13
Evaluation and conclusion
p. 43
5.13.1
Evaluation and conclusion on SGW-C and SGW-U failure
p. 43
5.13.2
Evaluation and conclusion on PGW-C and PGW-U failure
p. 43
5.13.3
Evaluation and conclusion on TDF-C and TDF-U failure
p. 44
5.13.4
Evaluation and conclusion on detection of a PFCP entity restart
p. 44
5.13.5
Evaluation and conclusion Partial failure
p. 44
6
Load control
p. 44
6.1
Introduction
p. 44
6.2
Solution 1 - UP function reporting its load to CP function at node level (as per GTP-C load control principles)
p. 45
6.3
Evaluation and conclusion
p. 45
7
Overload control
p. 45
7.1
Introduction
p. 45
7.2
Solution 1 - UP function reporting its overload to CP function at node level (as per GTP-C overload control principles)
p. 46
7.3
Evaluation and conclusion
p. 46
8
Path management and path failure handling
p. 46
8.1
Introduction
p. 46
8.2
Sx interface between SGW-C and SGW-U
p. 46
8.2.1
Solution 1 Echo Request/Echo Response
p. 46
8.3
Sx interface between PGW-C and PGW-U
p. 47
8.3.1
Solution 1 Echo Request/Echo Response
p. 47
8.4
Sx interface between TDF-C and TDF-U
p. 47
8.4.1
Solution 1
p. 47
8.5
Evaluation and conclusion
p. 48
9
Error handling on the user plane
p. 48
9.1
Introduction
p. 48
9.2
Error handling on missing sessions on the user plane
p. 48
9.2.1
Solution 1 UP function reports the error to the CP function and deletes the resources for the impacted rules.
p. 48
9.2.1.1
SGW-U and SGW-C
p. 48
9.2.1.2
PGW-U and PGW-C
p. 49
9.2.1.3
Evaluation
p. 49
9.3
User plane path failure detection and handling
p. 49
9.3.1
Introduction
p. 49
9.3.1.1
Solution 1 - Reporting the User Plane path failure to the CP function
p. 50
9.3.1.1.1
Description
p. 50
9.3.1.1.2
Evaluation
p. 50
9.4
Evaluation and conclusion
p. 51
9.4.1
Evaluation and conclusion on Error handling on missing sessions on the user plane
p. 51
9.4.2
Evaluation and conclusion on User plane path failure detection and handling
p. 51
$
Change History
p. 52