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 23.705
Word version: 13.0.0
1…
5…
5
Key issues
6
Solutions
7
Evaluation
8
Conclusions
A
Combining RAN and CN-based Solutions for RAN user plane congestion management as a deployment option
$
Change History
5
Key issues
p. 8
5.1
Key issue #1: RAN user plane congestion mitigation
p. 8
5.1.1
General description and assumptions
p. 8
5.2
Key issue #2: RAN user plane congestion awareness
p. 8
5.2.1
General description and assumptions
p. 8
5.3
Key issue #3: Differentiated treatment for non-deducible service data flows in downlink direction in case of RAN user plane congestion
p. 9
5.3.1
General description and assumptions
p. 9
5.4
Key issue #4: Video delivery control for congestion mitigation
p. 10
5.4.1
General description and assumptions
p. 10
5.5
Key issue #5: Uplink traffic prioritization
p. 10
6
Solutions
p. 11
6.1
CN-based solutions for RAN user plane congestion management
p. 11
6.1.1
General architectural requirements
p. 11
6.1.2
General description, assumptions and principles
p. 12
6.1.3
High-level operation and procedures
p. 13
6.1.4
RAN congestion detection solutions
p. 14
6.1.4.1
General description, assumptions, and principles
p. 14
6.1.4.2
High-level operation and procedures
p. 14
6.1.5
RAN congestion reporting solutions
p. 15
6.1.5.1
Solution 1.5.1: RAN user plane congestion reporting by GTP-U extension
p. 15
6.1.5.1.1
General description, assumptions, and principles
p. 15
6.1.5.1.2
High-level operation and procedures
p. 16
6.1.5.1.3
Congestion information transfer from the GGSN/PGW to other core network entities
p. 16
6.1.5.1.4
Policy control of congestion mitigation
p. 18
6.1.5.1.5
Impact on existing entities and interfaces
p. 19
6.1.5.1.6
Solution evaluation
p. 20
6.1.5.2
Solution 1.5.2: C-plane signalling for RAN user plane congestion reporting
p. 20
6.1.5.2.1
Clarification of terminologies
p. 20
6.1.5.2.2
General description, assumptions, and principles
p. 20
6.1.5.2.3
High-level operation and procedures
p. 22
6.1.5.2.3.2
Case of UTRAN accessing EPC via S4
p. 26
6.1.5.2.3.3
PS handover consideration
p. 26
6.1.5.2.4
Impact on existing entities and interfaces
p. 26
6.1.5.2.5
Solution evaluation
p. 26
6.1.5.3
Solution 1.5.3: RPPF based RAN user plane congestion reporting
p. 27
6.1.5.3.1
General description, assumptions, and principles
p. 27
6.1.5.3.2
High-level operation and procedures
p. 27
6.1.5.3.3
Impacts on existing entities and interfaces
p. 29
6.1.5.3.4
Solution evaluation
p. 29
6.1.5.4
Solution 1.5.4: Integrated on-path and off-path RAN user plane congestion reporting
p. 29
6.1.5.4.1
General description, assumptions, and principles
p. 29
6.1.5.4.2
High-level operation and procedures
p. 29
6.1.5.4.3
Impacts on existing entities and interfaces
p. 33
6.1.5.5
Solution 1.5.5: off-path based RAN user plane congestion reporting
p. 34
6.1.5.5.1
General description, assumptions, and principles
p. 34
6.1.5.5.2
High-level operation and procedures
p. 34
6.1.5.5.3
Impacts on existing entities and interfaces
p. 37
6.1.5.5.4
Solution evaluation
p. 38
6.1.6
RAN congestion mitigation solutions
p. 38
6.1.6.1
Solution 1.6.1: Policy-based congestion mitigation
p. 38
6.1.6.1.1
General description, assumptions, and principles
p. 38
6.1.6.1.2
High-level operation and procedures
p. 38
6.1.6.1.4
Impact on existing entities and interfaces
p. 39
6.1.6.1.5
Solution evaluation
p. 40
6.2
RAN-based solutions for RAN user plane congestion management
p. 40
6.2.1
Solution 2.1: Flow priority-based traffic differentiation on the same QCI (FPI)
p. 40
6.2.1.1
General description, assumptions, and principles
p. 40
6.2.1.2
High-level operation and procedures
p. 42
6.2.1.3
Impact on existing entities and interfaces
p. 43
6.2.1.4
Solution evaluation
p. 44
6.2.2
Solution 2.2: Flow and bearer QoS differentiation by RAN congestion handling description (FQI)
p. 45
6.2.2.1
General description, assumptions, and principles
p. 45
6.2.2.2
High-level operation and procedures
p. 47
6.2.2.3
Impact on existing entities and interfaces
p. 48
6.2.2.4
Solution evaluation
p. 49
6.2.2.5
RAN impacts
p. 49
6.2.3
Solution 2.3: Enhancing existing bearer concepts
p. 49
6.2.3.1
Solution principles
p. 49
6.2.3.2
High-level operation and procedures
p. 50
6.2.3.3
Impact on existing entities and interfaces
p. 52
6.2.3.4
Solution evaluation
p. 52
6.2.4
Solution 2.4: Differentiation of IP flows based on flow level QCI
p. 53
6.2.4.1
General description, assumptions, and principles
p. 53
6.2.4.2
High-level operation and procedures
p. 53
6.2.4.3
Impact on existing entities and interfaces
p. 53
6.2.4.4
Solution evaluation
p. 54
6.3
UE-based solutions for RAN user plane congestion management
p. 54
6.3.1
Solutions for uplink congestion management
p. 54
6.3.2
Solutions for handling of unattended traffic
p. 54
6.3.2.1
Solution 3.2.1: Unattended traffic limitation in the UE in case of RAN congestion
p. 54
6.3.2.1.1
General description, assumptions, and principles
p. 54
6.3.2.1.2
High-level operation and procedures
p. 54
6.3.2.1.3
Impact on existing entities and interfaces
p. 55
6.3.2.1.4
Solution evaluation
p. 56
7
Evaluation
p. 56
7.1
Building Block 1 Evaluation
p. 56
8
Conclusions
p. 57
8.1
Interim conclusions
p. 57
8.1.1
Building Block 1 Key issues
p. 57
8.1.2
Building Block 1 Solutions
p. 57
8.2
Final conclusions
p. 57
8.2.1
Building Block 1 final conclusions
p. 57
A
Combining RAN and CN-based Solutions for RAN user plane congestion management as a deployment option
p. 58
A.1
General description, assumptions, and principles
p. 58
A.2
High-level operation and procedures
p. 59
A.3
Impact on existing entities and interfaces
p. 59
A.4
Solution evaluation
p. 60
$
Change History
p. 61