Content for TR 23.793 Word version: 16.0.0
4 Architectural requirements and assumptions
5 Key issues
6 Solutions
7 Conclusions
$ Change History
4 Architectural requirements and assumptions p. 9
5 Key issues p. 10
5.1 Key issue#1: Overall Architecture for traffic Steering/switching/splitting between Multiple Accesses p. 10
5.2 Key Issue#2: Steering between Multiple Accesses p. 10
5.2.1 Descriptions p. 10
5.3 Key Issue#3: Switching between Multiple Accesses p. 11
5.3.1 Descriptions p. 11
5.4 Key Issue#4: Splitting Over Multiple Accesses p. 11
5.4.1 Descriptions p. 11
5.5 Key Issue#5: Multi-access PDU sessions (Un-trusted access) p. 11
5.5.1 Descriptions p. 11
5.6 Key Issue #6: Key issue on differentiation of 3GPP RATs in ATSSS rule p. 12
5.6.1 Descriptions p. 12
6 Solutions p. 12
6.1 Solution 1: Proposed architecture framework for ATSSS p. 12
6.1.1 General p. 14
6.1.2 Functional Description p. 15
6.1.3 MA PDU and URSP p. 16
6.1.4 Architecture Description p. 17
6.1.5 Procedures p. 19
6.1.5.1 Multi Access PDU Session Establishment Procedure p. 19
6.1.5.2 User Plane Configuration between UE-AT3SF and UPu-AT3SF p. 19
6.1.5.3 Access Measurement Report Procedure p. 20
6.1.5.4 Round Trip Time (RTT) Evaluation Procedure p. 22
6.1.6 Control Plane Protocol Stack between UE-AT3SF and UPc-AT3SF p. 22
6.1.7 User Plane Protocol Stack options between UE-AT3SF and UPu-AT3SF p. 23
6.1.7.1 User Plane Convergence Method based on NULL Tunneling p. 23
6.1.7.2 User Plane Convergence Method based on GRE tunneling p. 24
6.1.7.3 User Plane Convergence Method using L3 Generic Multi-Access Solutions (GMA) p. 25
6.1.7.4 User Plane Convergence Method using L4 Multipath Solutions (MP-TCP, QUIC, MP-QUIC, SCTP, UDP generic) p. 26
6.1.8 Impacts On Existing Entities and Interfaces p. 33
6.2 Solution 2: Support of Multi-Access PDU Sessions p. 34
6.2.1 General p. 34
6.2.2 Establishment of Multi-Access PDU session with multiple PDU Session IDs p. 35
6.2.3 Establishment of Multi-Access PDU session with a single PDU Session ID p. 37
6.2.3.1 Separate Establishment p. 37
6.2.3.2 Combined Establishment p. 39
6.2.3.3 UE Requested MA-PDU Session Establishment p. 41
6.2.4 NW-Requested MA-PDU Session Establishment p. 44
6.2.5 Modify a Multi-Access PDU Session to single-access PDU session p. 46
6.2.6 Modification of Multi-Access PDU session p. 47
6.2.7 Release of a Multi-Access PDU Session p. 49
6.3 Solution 3: TFCP (Traffic Flow Control Protocol) based architecture framework for ATSSS p. 50
6.3.1 Architecture framework Description p. 51
6.3.1.1 ATSSS Policy Control function description p. 51
6.3.1.2 ATSSS Policy Enforcement function description p. 53
6.3.1.3 ATSSS function description for TFCP p. 54
6.3.1.4 ATSSS path performance measurement function description p. 56
6.3.2 Protocol Stacks p. 58
6.3.3 PDU Session Establishment Procedure p. 59
6.3.4 PDU Session Modification procedure p. 62
6.3.5 ATSSS Execution Procedure p. 64
6.3.6 Solution evaluation p. 67
6.4 Solution 4: Policy for Access Traffic Steering, Switching and Splitting p. 67
6.4.1 General p. 67
6.4.2 Content of ATSSS Policy p. 69
6.4.3 Traffic Distribution based on ATSSS Policy p. 71
6.5 Solution 5: Multipath TCP (MPTCP) proxy architecture p. 71
6.5.1 General p. 71
6.5.2 MPTCP proxy p. 72
6.5.3 Addition of MPTCP proxy to 5GC p. 72
6.5.4 MA-PDU session establishment procedure for MPTCP traffic p. 73
6.5.5 ATSSS and URSP rules for MPTCP p. 76
6.6 Solution 6: Architecture framework with ATSSS rules via NAS and generic user plane Reporting Control Protocol p. 79
6.6.1 Architecture framework Description p. 79
6.6.2 Functional Description p. 79
6.6.3 Procedures p. 79
6.6.3.1 ATSSS Policy Control (via NAS) p. 79
6.6.3.2 Measurement Configuration and Reporting Control Procedure (via User Plane) p. 80
6.6.3.3 Control plane protocol stack between UE-AT3SF and UP-AT3SF p. 82
6.6.4 Impacts on existing entities and interfaces p. 82
6.7 Solution 7: Traffic Steering using Access Network Performance Measurements p. 83
6.8 Solution 8: ATSSS rules for supporting 3GPP RAT differentiation p. 88
6.8.1 General p. 88
6.9 Solution 9: Solution for the UL CL case on the Multi-access PDU sessions p. 89
6.9.1 General p. 89
6.9.2 Architecture description p. 89
6.9.3 PDU session Establishment Procedure with additional UL CL and PDU session Anchor p. 90
6.9.4 Insert UL CL and additional PDU Session Anchor after PDU Session Establishment p. 92
6.10 Solution 10: ATSSS Solution using a MA-PDU Session p. 94
6.11 Solution 11: Interworking for Multi-Access PDU Session p. 98
6.11.1 General p. 98
6.11.2 Functional Description p. 98
6.11.2.1 Interworking with N26 from EPC to 5GC p. 98
6.11.2.2 Interworking without N26 from EPC to 5GC p. 100
6.11.2.3 Interworking with N26 from 5GS to EPS p. 100
6.11.2.4 Interworking without N26 from 5GS to EPS p. 100
6.11.3 Solution evaluation p. 100
6.12 Solution 12: QoS framework for Multi-Access PDU Session p. 100
6.12.1 General p. 100
6.12.2 AN Resource Allocation p. 101
6.12.3 Management of GBR QoS Flow p. 101
6.12.3.1 UL GBR QoS Flow p. 101
6.12.3.2 DL GBR QoS Flow p. 101
6.12.4 Notification control p. 102
6.13 Solution 13: PCC support for ATSSS p. 102
6.13.1 General p. 102
6.13.2 PCC rule p. 103
6.13.3 Impacts on existing entities and interfaces p. 106
6.14 Solution 14: N4 support for ATSSS p. 106
6.14.1 General p. 106
6.14.2 Solution description p. 106
6.14.3 Impacts on existing entities and interfaces p. 108
7 Conclusions p. 108
$ Change History p. 114
