Content for TR 23.700-70 Word version: 19.0.0
5 Key Issues
6 Solutions
7 Overall Evaluation
8 Conclusions
A How does source packet associates repair packet in Flex FEC
$ Change history
5 Key Issues p. 13
5.1 Key Issue #1: Support of PDU set based QoS handling enhancement p. 13
5.1.1 Description p. 13
5.2 Key Issue #2: Support PDU Set information identification for end-to-end encrypted XRM traffic p. 13
5.2.1 Description p. 13
5.3 Key Issue #3: Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network p. 13
5.3.1 Description p. 13
5.4 Key Issue #4: Traffic detection and QoS flow mapping for multiplexed data flows p. 14
5.4.1 Description p. 14
5.5 Key Issue #5: QoS Handling when Traffic Characteristics Change Dynamically p. 14
5.5.1 Description p. 14
5.6 Key Issue #6: L4S for non-3GPP access networks and intermediate 5GS nodes p. 15
5.6.1 Description p. 15
5.7 Key Issue #7: Support for PDU Set in non-3GPP access. p. 15
5.7.1 Description p. 15
5.8 Key Issue #8: Enhancement for UE with the tethered devices p. 15
5.8.1 Description p. 15
5.9 Key Issue #9: Enhancement for XR related network information exposure p. 16
5.9.1 Description p. 16
6 Solutions p. 17
6.0 Mapping of Solutions to Key Issues p. 17
6.1 Solution #1: PDU Set content ratio awareness at RAN p. 19
6.1.1 Key Issue mapping p. 19
6.1.2 Description p. 19
6.1.3 Procedures p. 22
6.1.4 Impacts on services, entities and interfaces p. 22
6.2 Solution #2: Discarding of redundant PDUs (FEC) and reporting p. 23
6.2.1 Key Issue mapping p. 23
6.2.2 Description p. 23
6.2.3 Procedures p. 23
6.2.4 Impacts on services, entities and interfaces p. 24
6.3 Solution #3: FEC mechanism and PSI based PDU Set QoS Handling Enhancement p. 25
6.3.1 Key Issue mapping p. 25
6.3.2 Description p. 25
6.3.3 Procedures p. 26
6.3.4 Impacts on services, entities and interfaces p. 27
6.4 Solution #4: PDU Set FEC-based PDU Set QoS Handling p. 28
6.4.1 Key Issue mapping p. 28
6.4.2 Description p. 28
6.4.2.1 FEC p. 28
6.4.2.2 Different Layer of Implementation FEC for PDU Sets p. 28
6.4.2.3 Implementation of PDU Set FEC p. 28
6.4.3 Procedures p. 29
6.4.4 Impacts on services, entities and interfaces p. 29
6.5 Solution #5: PDU Set Handling and Information marking to support RAN's other PDU Set QoS handling different from the handling with for PSDB/PSER/PSIHI p. 30
6.5.1 Key Issue mapping p. 30
6.5.2 Description p. 30
6.5.3 Procedures p. 30
6.5.4 Impacts on services, entities and interfaces p. 31
6.6 Solution #6: Enhanced Alternative QoS Profiles for PDU set based QoS handling p. 31
6.6.1 Key Issue mapping p. 31
6.6.2 Description p. 31
6.6.3 Procedures p. 32
6.6.4 Impacts on services, entities and interfaces p. 33
6.7 Solution #7: Enhancing alternative QoS profile with UL and/or DL PDU set QoS parameters p. 33
6.7.1 Key Issue mapping p. 33
6.7.2 Description p. 33
6.7.3 Procedures p. 34
6.7.4 Impacts on services, entities, and interfaces p. 35
6.8 Solution #8: Consistent PDU Set Handling between AF and 5GS p. 36
6.8.1 Key Issue mapping p. 36
6.8.2 Description p. 36
6.8.3 Procedures p. 37
6.8.4 Impacts on services, entities and interfaces p. 38
6.9 Solution #9: PDU Set information identification for encrypted traffic p. 38
6.9.1 Key Issue mapping p. 38
6.9.2 Description p. 38
6.9.3 Procedures p. 39
6.9.4 Impacts on services, entities and interfaces p. 40
6.10 Solution #10: PDU Set information identification based on MoQ p. 40
6.10.1 Key Issue mapping p. 40
6.10.2 Description p. 40
6.10.3 Procedures p. 42
6.10.4 Detailed MoQ mechanism in UE, UPF and Application Server p. 43
6.10.5 Impacts on services, entities and interfaces p. 44
6.11 Solution #11: RTP over QUIC based Encrypted Traffic Detection, Identification, and QoS flows mapping p. 44
6.11.1 Key Issue mapping p. 44
6.11.2 Description p. 44
6.11.3 Procedures p. 46
6.11.4 Impacts on services, entities and interfaces p. 47
6.12 Solution #12: Obfuscated Metadata to Classify Payload in Encrypted Media Packets p. 47
6.12.1 Key Issue mapping p. 47
6.12.2 Description p. 48
6.12.3 Procedures p. 48
6.12.3.1 E2E Sequence of Operations p. 48
6.12.3.2 Obfuscated Codes and Metadata p. 49
6.12.3.3 Initial Configuration of Obfuscated Codes, Metadata and Keys p. 51
6.12.3.4 Per-packet Transport of Metadata p. 51
6.12.3.5 Classifying and Mapping into PDU sets p. 51
6.12.4 Impacts on services, entities and interfaces p. 52
6.13 Solution #13: Multiple DSCP markings per QoS Flow p. 53
6.13.1 Key Issue mapping p. 53
6.13.2 Description p. 53
6.13.3 Procedures p. 53
6.13.4 Impacts on services, entities and interfaces p. 54
6.14 Solution #14: Extending Packet Filter Set to identify multiplexed traffic flows within a single transport connection p. 54
6.14.1 Key Issue mapping p. 54
6.14.2 Description p. 54
6.14.3 Procedures p. 55
6.14.4 Impacts on services, entities and interfaces p. 55
6.15 Solution #15: Traffic Detection and QoS mapping for XR and Media services. p. 56
6.15.1 Key Issue mapping p. 56
6.15.2 Description p. 56
6.15.3 Procedures p. 56
6.15.4 Impacts on services, entities and interfaces p. 57
6.16 Solution #16: AS based trigger of data boost handling with reflective QoS p. 58
6.16.1 Key Issue mapping p. 58
6.16.2 Description p. 58
6.16.3 Procedures p. 59
6.16.4 Impacts on services, entities and interfaces p. 60
6.17 Solution #17: L4S in non-3GPP access networks p. 60
6.17.1 Key Issue mapping p. 60
6.17.2 Description p. 60
6.17.2.1 General p. 60
6.17.2.2 Support of ECN marking for L4S in wireline node(s) p. 61
6.17.2.3 Supporting of ECN marking for L4S in wireless N3IWF deployments p. 62
6.17.2.4 Supporting of ECN marking for L4S in wireless TNAN deployments p. 66
6.17.3 Procedures p. 70
6.17.3.1 Procedures in wireline 5G access network p. 70
6.17.3.2 Procedures in untrusted non-3GPP access p. 71
6.17.3.3 Procedures in trusted non-3GPP access p. 72
6.17.4 Impacts on services, entities and interfaces p. 72
6.18 Solution #18: PDU Set handling in wireline/wireless non-3GPP access p. 74
6.18.1 Key Issue mapping p. 74
6.18.2 Description p. 74
6.18.2.1 General p. 74
6.18.2.2 Supporting PDU Set based QoS handling in non-3GPP access nodes p. 74
6.18.3 Procedures p. 76
6.18.3.1 Procedures in wireline 5G access network p. 76
6.18.3.2 Procedures in untrusted non-3GPP access p. 77
6.18.3.3 Procedures in trusted non-3GPP access p. 78
6.18.4 Impacts on services, entities and interfaces p. 79
6.19 Solution #19: Alternative PDU Set QoS parameters to support differentiated QoS handling and Alternative QoS/Alternative PDU Set QoS Exposure p. 79
6.19.1 Key Issue mapping p. 79
6.19.2 Description p. 79
6.19.2.1 Alternative PDU Set QoS parameters to support differentiated QoS handling p. 79
6.19.2.2 Alternative QoS/PDU set QoS Notification Exposure p. 80
6.19.3 Procedures p. 81
6.19.3.1 Procedures of alternative PDU Set QoS handling p. 81
6.19.3.2 Procedures of network information exposure via user plane p. 82
6.19.3.3 Procedures of network information exposure via control plane p. 83
6.19.4 Impacts on services, entities and interfaces p. 85
6.20 Solution #20: Nominal PSDB p. 86
6.20.1 Key Issue mapping p. 86
6.20.2 Description p. 86
6.20.3 Procedures p. 88
6.20.4 Impacts on services, entities and interfaces p. 88
6.21 Solution #21: Enhancing PDU Set QoS Handling with Dynamic FEC Related Information Marking in GTP-U p. 88
6.21.1 Key Issue mapping p. 88
6.21.2 Description p. 88
6.21.3 Procedures p. 90
6.21.4 Impacts on services, entities and interfaces p. 91
6.22 Solution #22: The handling UL PDU Set QoS parameters p. 92
6.22.1 Key Issue mapping p. 92
6.22.2 Description p. 92
6.22.3 Procedures p. 93
6.22.3.1 Alternative1 p. 93
6.22.3.2 Alternative2 p. 94
6.22.4 Impacts on services, entities and interfaces p. 94
6.23 Solution #23: PDU set discard based on PDU sets correlation info from AS/AF p. 95
6.23.1 Key Issue mapping p. 95
6.23.2 Description p. 95
6.23.3 Procedures p. 95
6.23.4 Impacts on services, entities and interfaces p. 96
6.24 Solution #24: PDU set identification when an end-to-end XR session is fully encrypted using a tunnelled connection over N6 p. 96
6.24.1 Key Issue mapping p. 96
6.24.2 Description p. 96
6.24.3 Procedures p. 98
6.24.3.1 General procedure p. 98
6.24.3.2 Using Connect-UDP p. 100
6.24.4 Impacts on services, entities and interfaces p. 103
6.25 Solution #25: Preconfigured N6 tunnelling and GTP-U header extension for conveyance of PDU Set-related information p. 103
6.25.1 Key Issue mapping p. 103
6.25.2 Description p. 104
6.25.3 Procedures p. 105
6.25.4 Impacts on services, entities and interfaces p. 105
6.26 Solution #26: PDU Set identification for end-to-end encrypted traffic p. 105
6.26.1 Key Issue mapping p. 105
6.26.2 Description p. 106
6.26.3 General framework p. 106
6.26.3.1 General procedure p. 108
6.26.4 PDU Set based QoS handling using UDP-connect p. 109
6.26.5 Impacts on services, entities and interfaces p. 114
6.27 Solution #27: Differentiated Handling for Transporting Encrypted XRM traffics Using Metadata over N6 p. 114
6.27.1 Key Issue mapping p. 114
6.27.2 Description p. 114
6.27.3 Procedures p. 116
6.27.4 Impacts on services, entities and interfaces p. 116
6.28 Solution #28: QoS Flow Mapping Considering the PSI for Multiplexed Data Flows p. 116
6.28.1 Key Issue mapping p. 116
6.28.2 Description p. 116
6.28.3 Procedures p. 117
6.28.4 Impacts on services, entities and interfaces p. 117
6.29 Solution #29: KI#4 Support for multiplexed media traffic using RTP header inspection p. 118
6.29.1 Key Issue mapping p. 118
6.29.2 Description p. 119
6.29.2.1 Background p. 119
6.29.2.2 Solution Description p. 119
6.29.2.3 Detection of protocols and media streams p. 120
6.29.2.4 Extensions needed to 3GPP specifications p. 122
6.29.3 Procedures p. 124
6.29.4 Impacts on services, entities and interfaces p. 125
6.30 Solution #30: Support of dynamic change of traffic burst size p. 126
6.30.1 Key Issue mapping p. 126
6.30.2 Description p. 126
6.30.3 Procedures p. 126
6.30.4 Impacts on services, entities and interfaces p. 127
6.31 Solution #31: Identifying Traffic Flows from the Tethered Devices p. 127
6.31.1 Key Issue mapping p. 127
6.31.2 Description p. 127
6.31.3 Procedures p. 128
6.31.4 Impacts on services, entities and interfaces p. 129
6.32 Solution #32: Tethered traffic handling by reusing N5CW and trusted WLAN access p. 129
6.32.1 Key Issue mapping p. 129
6.32.2 Description p. 129
6.32.3 Proposed architecture reusing N5CW access p. 130
6.32.4 Procedures p. 131
6.32.5 Impacts on services, entities and interfaces p. 132
6.33 Solution #33: Available Data Rate Monitoring and Exposure p. 132
6.33.1 Key Issue mapping p. 132
6.33.2 Description p. 132
6.33.3 Procedures p. 133
6.33.3.1 Exposure of Available Data Rate via User Plane p. 133
6.33.3.2 Available Data Rate Exposure via Control Plane p. 134
6.33.4 Impacts on services, entities and interfaces p. 134
6.34 Solution #34: PDU Set Performance exposure p. 135
6.34.1 Key Issue mapping p. 135
6.34.2 Description p. 135
6.34.2.1 General p. 135
6.34.2.2 PDU Set Delay p. 135
6.34.2.3 PDU Set Loss Rate Measurement and Reporting p. 136
6.34.3 Procedures p. 136
6.34.4 Impacts on services, entities and interfaces p. 137
7 Overall Evaluation p. 138
8 Conclusions p. 138
8.1 Conclusions for Key Issue #1 p. 138
8.1.1 Conclusion for KI#1_other PDU Set handling p. 138
8.1.2 Conclusion for KI#1_QoS Notification without AQP p. 138
8.1.3 Conclusion for KI#1_AQP p. 138
8.1.4 Conclusion for KI#1_AL-FEC p. 139
8.2 Conclusions for Key Issue #2 p. 139
8.3 Conclusions for Key Issue #3 p. 141
8.4 Conclusions for Key Issue #4 p. 142
8.5 Conclusions for Key Issue #5 p. 143
8.6 Conclusions for Key Issue #6 p. 143
8.7 Conclusions for Key Issue #7 p. 144
8.8 Conclusions for Key Issue #8 p. 144
8.9 Conclusions for Key Issue #9 p. 145
A How does source packet associates repair packet in Flex FEC p. 146
$ Change history p. 148
