Content for TR 23.700-60 Word version: 18.0.0
5 Key Issues p. 20
5.1 Key Issue #1: Policy control enhancements to support multi-modality flows coordinated transmission for single UE p. 20
5.1.1 Description p. 20
5.2 Key Issue #2: Support the Application Synchronization and QoS Policy Coordination for Multi-modal Traffic among Multiple UEs p. 20
5.2.1 Description p. 20
5.3 Key Issue #3: 5GS information exposure for XR/media Enhancements p. 21
5.3.1 Description p. 21
5.4 Key Issue #4: PDU Set integrated packet handling p. 21
5.4.1 Description p. 21
5.5 Key Issue #5: Differentiated PDU Set Handling p. 22
5.5.1 Description p. 22
5.6 Key Issue #6: Uplink-downlink transmission coordination to meet Round-Trip latency requirements p. 23
5.6.1 Description p. 23
5.7 Key Issue #7: Policy enhancements for jitter minimization p. 23
5.7.1 Description p. 23
5.8 Key Issue #8: Enhancements to power savings for XR services p. 23
5.8.1 Description p. 23
5.9 Key Issue #9: Trade-off of QoE and Power Saving Requirements p. 24
5.9.1 Description p. 24
6 Solutions p. 25
6.0 Mapping of Solutions to Key Issues p. 25
6.1 Solution #1: Tactile and multi-modality traffic flows coordination transmission for one UE p. 28
6.1.1 Key Issue mapping p. 28
6.1.2 Description p. 28
6.1.3 Procedures p. 29
6.1.4 Impacts on services, entities and interfaces p. 30
6.2 Solution #2:Group policy for Multi-modal Traffic among Multiple UEs p. 30
6.2.1 Key Issue mapping p. 30
6.2.2 Description p. 30
6.2.3 Procedures p. 31
6.2.4 Impacts on services, entities and interfaces p. 32
6.3 Solution #3: Same PCF selection for Multiple UEs with XRM services p. 32
6.3.1 Key Issue mapping p. 32
6.3.2 Description p. 32
6.3.3 Procedures p. 33
6.3.4 Impacts on services, entities and interfaces p. 34
6.4 Solution #4: QoS policy coordination for multiple UEs' QoS flows p. 34
6.4.1 Key Issue mapping p. 34
6.4.2 Description p. 34
6.4.3 Procedures p. 35
6.4.3.1 Procedures of AF session With QoS establishment for multi-modal QoS flow p. 35
6.4.3.2 Procedures of AF session With QoS revoke for multi-modal QoS flow p. 39
6.4.4 Impacts on services, entities and interfaces p. 40
6.5 Solution #5: Exposure of the UE data rate, normal data transmission interruption event and congestion information p. 40
6.5.1 Key Issue mapping p. 40
6.5.2 Description p. 40
6.5.3 Procedures p. 43
6.5.3.1 Procedure for subscribing information p. 43
6.5.3.2 Procedure for notify of information via user plane p. 45
6.5.3.3 Procedure for notify of information via control plane p. 46
6.5.4 Impacts on services, entities and interfaces p. 46
6.6 Solution #6:Mean bit rate change report p. 47
6.6.1 Key Issue mapping p. 47
6.6.2 Description p. 47
6.6.3 Procedures p. 48
6.6.3.1 Non-GBR QoS Notification Control Report p. 48
6.6.3.2 Non-GBR QoS Notification Control p. 49
6.6.4 Impacts on services, entities and interfaces p. 49
6.7 Solution #7: Identification and importance of packets in PDU set p. 50
6.7.1 Key Issue mapping p. 50
6.7.2 Description p. 50
6.7.3 Procedures p. 52
6.7.3.1 Identifying Packets of a PDU Set p. 52
6.7.3.2 Classifying Importance of Packets in PDU Set p. 53
6.7.3.2.1 Mapping RTP/payload header values to PPM p. 55
6.7.3.2.2 Mapping HTTP transport payload to PPM p. 55
6.7.3.2.3 Provisioning Application Information p. 55
6.7.3.3 Protocol Extensions p. 57
6.7.4 Impacts on services, entities and interfaces p. 57
6.8 Solution #8: Introduction of PDU Set information in RTP extension header and related QoS parameters p. 58
6.8.1 Key Issue mapping p. 58
6.8.2 Description p. 58
6.8.2.1 Solution to identify a PDU-Set on N6/in UPF p. 58
6.8.2.2 New information associated with PDU-Set p. 59
6.8.2.3 New QoS parameters associated with PDU-Set p. 60
6.8.3 Procedures p. 61
6.8.3.1 Initial CP based configuration of 5GS p. 61
6.8.3.2 In-band signalling of PDU Set information p. 62
6.8.4 Impacts on services, entities and interfaces p. 62
6.9 Solution #9: GTP extension header for PDU Set Sequence Number, and, Number of PDUs in the PDU Set p. 63
6.9.1 Key Issue mapping p. 63
6.9.2 Description p. 63
6.9.3 Procedures p. 64
6.9.4 Impacts on services, entities and interfaces p. 65
6.10 Solution #10: Different bearers for PDUs with different importance levels p. 65
6.10.1 Key Issue mapping p. 65
6.10.2 Description p. 65
6.10.3 Procedures p. 66
6.10.4 Impacts on services, entities and interfaces p. 67
6.11 Solution #11: Handling PDU Set within QoS flow p. 68
6.11.1 Key Issue mapping p. 68
6.11.2 Description p. 68
6.11.3 Procedures p. 69
6.11.4 Impacts on services, entities and interfaces p. 71
6.12 Solution #12: PDU Set integrated QoS handling p. 71
6.12.1 Key Issue mapping p. 71
6.12.2 Description p. 71
6.12.3 Procedures p. 71
6.12.3.1 PDU Set integrated packet handling p. 71
6.12.3.2 PDU Set identification and marking on UPF p. 73
6.12.3.2.1 Identification of PDU Set as a video frame p. 73
6.12.3.2.2 Identification of PDU Set as a H.264 video slice p. 74
6.12.3.2.3 PDU Set marking in GTP-U header p. 75
6.12.3.2.4 Identification of PDU Set as a H.265 video slice p. 75
6.12.3.2.5 Identification of PDU Set as a H.266 video slice p. 76
6.12.3.3 PDU Set integrated packet processing p. 77
6.12.4 Impacts on services, entities and interfaces p. 78
6.13 Solution #13: DL data handling p. 78
6.13.1 Key Issue mapping p. 78
6.13.2 Description p. 78
6.13.3 Procedures p. 80
6.13.3.1 Procedure for policy allocation p. 80
6.13.3.2 Procedure for RAN load report via user plane p. 82
6.13.4 Impacts on services, entities and interfaces p. 82
6.14 Solution #14: PDU Set integrated packet handling p. 83
6.14.1 Introduction p. 83
6.14.2 Functional Description p. 84
6.14.3 Procedures p. 88
6.14.4 Impacts on services, entities and interfaces p. 90
6.15 Solution #15: Leverage RTP layer info for PDU Set handling p. 90
6.15.1 Key Issue mapping p. 90
6.15.2 Description p. 90
6.15.3 Procedures p. 91
6.15.4 Impacts on services, entities and interfaces p. 92
6.16 Solution#16 : RTP/SRTP based PDU Set identification p. 92
6.16.1 Key Issue mapping p. 92
6.16.2 Description p. 93
6.16.3 Procedures p. 93
6.16.3.1 Enhancements to IP Packet Filter Set p. 93
6.16.3.2 Conditions for IP packets based on RTP p. 94
6.16.3.3 Condition for IP Packets based on SRTP p. 94
6.16.4 Impacts to existing nodes p. 95
6.17 Solution #17: Sub QoS Flow based QoS and PCC Architecture p. 95
6.17.1 Key Issue mapping p. 95
6.17.2 Description p. 95
6.17.2.1 Sub QoS Flow based QoS Architecture p. 95
6.17.2.2 The differences between the Sub QoS Flow based QoS Architecture and pre-Rel-18 QoS Architecture p. 96
6.17.2.3 Sub QoS Rules based PCC Architecture p. 97
6.17.3 Procedures p. 99
6.17.4 Impacts on services, entities and interfaces p. 100
6.18 Solution #18: PDU Set Identification and Marking p. 100
6.18.1 Key Issue mapping p. 100
6.18.2 Description p. 100
6.18.2.1 How the UE/UPF detects the PDU Sets p. 101
6.18.2.1.1 What information are provided to the 5GS to identify the PDU Sets? p. 101
6.18.2.1.2 How the UE/UPF detects the start/end and importance of a PDU Set over RTP/SRTP p. 102
6.18.2.1.3 How the UE/UPF detect the start/end and importance of a PDU Set without using RTP/SRTP p. 103
6.18.2.2 How the UPF marks the PDU Sets in N3/N9 interface? p. 104
6.18.3 Procedures p. 105
6.18.4 Impacts on services, entities and interfaces p. 105
6.19 Solution #19: Application-aware QoS p. 105
6.19.1 Key Issue mapping p. 105
6.19.2 Description p. 105
6.19.3 Procedures p. 105
6.19.3.1 General p. 105
6.19.3.2 PDU Session establishment procedure considering application QoS policy p. 106
6.19.3.3 PDU set level QoS policies and QoS handling p. 107
6.19.4 Impacts on services, entities and interfaces p. 107
6.20 Solution #20: UPF based PDU Set identification p. 108
6.20.1 Key Issue mapping p. 108
6.20.2 Description p. 108
6.20.2.1 Overall framework p. 108
6.20.2.2 PDU Set identification based on N3 PDU Set metadata p. 109
6.20.3 Procedures p. 110
6.20.4 Impacts on services, entities and interfaces p. 110
6.21 Solution #21: PDU Set ID in the GTP-U header p. 110
6.21.1 Key Issue mapping p. 110
6.21.2 Description p. 111
6.21.3 Procedures p. 111
6.21.4 Impacts on existing entities and interfaces p. 111
6.22 Solution #22: N6 tunnelling and GTP-U header extension for conveyance of PDU Set-related information p. 112
6.22.1 Key Issue mapping p. 112
6.22.2 Description p. 112
6.22.3 Procedures p. 114
6.22.4 Impacts on services, entities and interfaces p. 114
6.23 Solution #23: PDU set related packet handling enhancements p. 114
6.23.1 Key Issue mapping p. 114
6.23.2 Description p. 114
6.23.3 Procedures p. 115
6.23.4 Impacts on services, entities and interfaces p. 116
6.24 Solution #24: Support differentiated QoS Handling for different PDU Sets p. 117
6.24.1 Key Issue mapping p. 117
6.24.2 Description p. 117
6.24.3 Procedures p. 118
6.24.3.1 Processing of PDU Sets based on different importance/dependency information p. 118
6.24.3.2 PDU Set Importance/dependency information identification on UPF p. 119
6.24.4 Impacts on services, entities and interfaces p. 124
6.25 Solution #25: PDU Set QoS Profile, QoS Flow parameters and QoS Characteristics p. 124
6.25.1 Key Issue mapping p. 124
6.25.2 Description p. 124
6.25.2.1 Overall framework p. 124
6.25.2.2 New type of QoS Profile p. 126
6.25.2.3 New per-PDU Set QoS characteristics p. 126
6.25.3 Procedures p. 128
6.25.4 Impacts on services, entities and interfaces p. 128
6.26 Solution #26: Provisioning XR traffic configuration to 5GS p. 129
6.26.1 Key Issue mapping p. 129
6.26.2 Description p. 129
6.26.3 Procedures p. 131
6.26.4 Impacts on services, entities and interfaces p. 131
6.27 Solution #27: RT latency split for two QoS flows used for UL and DL respectively p. 132
6.27.1 Key Issue mapping p. 132
6.27.2 Description p. 132
6.27.3 Procedures p. 133
6.27.4 Impacts on services, entities and interfaces p. 134
6.28 Solution #28: RAN split RT latency for single QoS flow p. 134
6.28.1 Key Issue mapping p. 134
6.28.2 Description p. 134
6.28.3 Procedures p. 135
6.28.4 Impacts on services, entities and interfaces p. 136
6.29 Solution #29: Two Way Delay Budget p. 136
6.29.1 Introduction p. 136
6.29.2 Functional Description p. 137
6.29.3 Procedures p. 137
6.29.4 Impacts on services, entities and interfaces p. 138
6.30 Solution #30: Policy enhancements to minimize jitter p. 138
6.30.1 Key Issue mapping p. 138
6.30.2 Description p. 138
6.30.3 Procedures p. 139
6.30.3.1 Procedure for network exposure of network latency or jitter to AF p. 139
6.30.3.2 Procedure for AF to provision jitter requirements to 5GC p. 140
6.30.4 Impacts on services, entities and interfaces p. 140
6.31 Solution #31: 5GS Policy enhancements to minimize the jitter p. 141
6.31.1 Key Issue mapping p. 141
6.31.2 Description p. 141
6.31.3 Procedures for jitter calculation p. 141
6.31.4 Impacts on services, entities and interfaces p. 143
6.32 Solution #32: Periodicity Jitter Control for XRM Service p. 143
6.32.1 Key Issue mapping p. 143
6.32.2 Description p. 143
6.32.3 Procedures p. 144
6.32.3.1 Periodicity Jitter Provision procedure p. 144
6.32.3.2 Periodicity Jitter Report procedure p. 145
6.32.4 Impacts on services, entities and interfaces p. 145
6.33 Solution #33: support of CDRX enhancement for power saving handling p. 146
6.33.1 Key Issue mapping p. 146
6.33.2 Description p. 146
6.33.3 Procedures p. 147
6.33.4 Impacts on services, entities and interfaces p. 148
6.34 Solution #34: 5GC and UE Assistance to RAN for CDRX Optimization p. 148
6.34.1 Key Issue mapping p. 148
6.34.2 Description p. 149
6.34.3 Procedures p. 149
6.34.3.1 XR Communication Pattern Provided via 3rd Party Application Server p. 149
6.34.3.2 UE Configured with multiple CDRX Configurations p. 150
6.34.3.3 UE Configured with Adaptable CDRX Configuration p. 151
6.34.4 Impacts on services, entities and interfaces p. 153
6.35 Solution #35: Provision of conditional QoS profile(s) p. 153
6.35.1 Key Issue mapping p. 153
6.35.2 Description p. 153
6.35.3 Procedures p. 154
6.35.4 Impacts on services, entities and interfaces p. 155
6.36 Solution #36: Handling multiple QoS flows of one UE together p. 155
6.36.1 Key Issue mapping p. 155
6.36.2 Description p. 155
6.36.3 Procedures p. 156
6.36.4 Impacts on services, entities and interfaces p. 157
6.37 Solution#37 : Policy coordination for multiple UEs in multiple PCFs p. 157
6.37.1 Key Issue mapping p. 157
6.37.2 Description p. 158
6.37.3 Procedures p. 158
6.37.3.1 Procedures for group policy data configuration p. 158
6.37.3.2 Procedures for AF request targeting an individual UE policy to the relevant PCF p. 159
6.37.4 Impact on existing entities and interfaces p. 160
6.38 Solution #38: Flow Association Using a Coordination Identifier p. 160
6.38.1 Key Issue mapping p. 160
6.38.2 Description p. 160
6.38.3 Procedures p. 161
6.38.3.1 Initiation of the Service by the 3rd Party Application p. 161
6.38.3.2 Discovery of the Service by a UE Application p. 161
6.38.3.3 Initiation of Service Traffic by a UE Application p. 162
6.38.4 Impacts on services, entities and interfaces p. 162
6.39 Solution #39: URSP enhancement for same PDU session selection of XRM service p. 163
6.39.1 Key Issue mapping p. 163
6.39.2 Description p. 163
6.39.3 Procedures p. 163
6.39.4 Impacts on services, entities and interfaces p. 163
6.40 Solution #40: Application layer-based media synchronization p. 164
6.40.1 Key Issue mapping p. 164
6.40.2 Description p. 164
6.40.3 Procedures p. 164
6.40.4 Impacts on services, entities and interfaces p. 164
6.41 Solution #41: Use of ECN bits for L4S to enable codec/rate adaptation to meet requirements for services p. 165
6.41.1 Key Issue mapping p. 165
6.41.2 Description p. 165
6.41.2.1 Use of ECN bits in NG-RAN for L4S p. 165
6.41.2.2 Enablement of using ECN bits marking for L4S p. 166
6.41.3 Procedures p. 166
6.41.4 Impacts on services, entities and interfaces p. 166
6.42 Solution #42: Exposure of round-trip delay to support XR/media enhancements p. 166
6.42.1 Key Issue mapping p. 166
6.42.2 Description p. 166
6.42.3 Procedures p. 167
6.42.4 Impacts on services, entities and interfaces p. 168
6.43 Solution #43: Information Exposure to AF for XR/media Enhancements p. 169
6.43.1 Key Issue mapping p. 169
6.43.2 Description p. 169
6.43.3 Procedure for information exposure p. 171
6.43.4 Impacts on services, entities and interfaces p. 173
6.44 Solution #44: XRM AF driven Quick QoS Notification Control p. 173
6.44.1 Key Issue mapping p. 173
6.44.2 Description p. 173
6.44.3 Procedures p. 175
6.44.4 Impacts on services, entities and interfaces p. 176
6.45 Solution #45: Information Exposure to AF for XR/media Enhancements p. 176
6.45.1 Key Issue mapping p. 176
6.45.2 Description p. 176
6.45.3 Procedure for information exposure for estimated QoS p. 177
6.45.4 Impacts on services, entities and interfaces p. 178
6.46 Solution #46: Use of ECN marking for L4S for scalable congestion control and meet requirements for services p. 178
6.46.1 Key Issue mapping p. 178
6.46.2 Description p. 178
6.46.2.1 Use of ECN for Uplink p. 178
6.46.2.2 Use of ECN for Downlink p. 180
6.46.2.3 Enabling use of ECN p. 181
6.46.3 Procedures p. 182
6.46.4 Impacts on services, entities and interfaces p. 182
6.47 Solution #47: Delay Difference and Delay Notifications and Reports p. 182
6.47.1 Key Issue mapping p. 182
6.47.2 Description p. 182
6.47.3 Procedures p. 182
6.47.4 Impacts on services, entities and interfaces p. 184
6.48 Solution #48: Enhanced Notification of Rata Adaptation Request p. 184
6.48.1 General p. 184
6.48.2 Functional Description p. 185
6.48.3 Procedures p. 185
6.48.4 Impacts on services, entities and interfaces p. 186
6.49 Solution #49: PDU set integrated handling for UPF/UE p. 186
6.49.1 Key Issue mapping p. 186
6.49.2 Description p. 186
6.49.3 Procedures p. 187
6.49.4 Impacts on services, entities and interfaces p. 188
6.50 Solution #50: Relative QoS within a PDU Set p. 188
6.50.1 Key Issue mapping p. 188
6.50.2.1 PDU-Set information p. 188
6.50.2.2 New QoS parameter p. 188
6.50.3 Impacts on services, entities and interfaces p. 189
6.51 Solution #51: Handling of the PDU Set p. 189
6.51.1 Key Issue mapping p. 189
6.51.2 Description p. 189
6.51.3 Procedures p. 190
6.51.4 Impacts on services, entities and interfaces p. 191
6.52 Solution #52: Consolidated Solution for PDU Set based QoS framework p. 191
6.52.1 Key Issue mapping p. 191
6.52.2 Description p. 192
6.52.2.0 General principles p. 192
6.52.2.1 PDU set information detected by the UPF p. 192
6.52.2.2 PDU Set information identification by the UPF p. 193
6.52.2.3 PDU Set information provided by the UPF to the RAN p. 193
6.52.2.4 QoS parameters for PDU Set Based QoS handling p. 194
6.52.2.5 QoS parameters provided by the AF to the CN p. 194
6.52.3 Procedures p. 195
6.52.4 Impacts on services, entities and interfaces p. 196
6.53 Solution #53: PDU Set transmission coordination between RAN and UPF p. 196
6.53.1 Key Issue mapping p. 196
6.53.2 Description p. 196
6.53.3 Procedures p. 197
6.53.4 Impacts on services, entities and interfaces p. 198
6.54 Solution #54: Identification and processing of PDU set by interworking between Application and 5GS p. 198
6.54.1 Key Issue mapping p. 198
6.54.2 Description p. 198
6.54.3 Procedures p. 199
6.54.4 Impacts on existing entities and interfaces p. 200
6.55 Solution #55: PDU Set based services using MASQUE p. 201
6.55.1 Key Issue mapping p. 201
6.55.2 Description p. 201
6.55.3 Procedures p. 203
6.55.4 Impacts on services, entities, and interfaces p. 204
6.56 Solution #56: PDU Set integrated packet handling with QoS differentiation p. 205
6.56.1 Introduction p. 205
6.56.2 Description of Solution Components p. 206
6.56.3 Procedures p. 208
6.56.4 Impacts on services, entities and interfaces p. 209
6.57 Solution #57: Negotiation of details of marking mechanisms for AS to UPF communication p. 209
6.57.1 Key Issue mapping p. 209
6.57.2 Description p. 209
6.57.3 Procedures p. 210
6.57.4 Impacts on services, entities and interfaces p. 212
6.58 Solution #58: Support for application packet information for CDRX enhancements p. 212
6.58.1 Key Issue mapping p. 212
6.58.2 Description p. 212
6.58.2.1 General p. 212
6.58.2.2 Application packet periodicity p. 213
6.58.2.3 Application packet jitter range p. 213
6.58.2.4 Introduction of new information for enhanced CDRX operation p. 214
6.58.3 Procedures p. 214
6.58.3.1 CP based initial configuration of the 5GS p. 214
6.58.3.2 In-band signalling based update of the set of periodicities p. 214
6.58.4 Impacts on services, entities and interfaces p. 214
6.59 Solution #59: Assistance information needed for power savings in NG-RAN p. 215
6.59.1 Introduction p. 215
6.59.2 Functional Description p. 215
6.59.3 Procedures p. 216
6.59.4 Impacts on services, entities and interfaces p. 216
6.60 Solution #60: End of Burst Indication p. 217
6.60.1 Key Issue mapping p. 217
6.60.2 Description p. 217
6.60.3 Procedures p. 217
6.60.4 Impacts on services, entities and interfaces p. 218
6.61 Solution #61: Policy Determination Considering UE Battery Level p. 218
6.61.1 Key Issue mapping p. 218
6.61.2 Description p. 218
6.61.3 Procedures p. 219
6.61.3.1 AM Policy Association Establishment and Modification p. 219
6.61.3.2 SM Policy Association Establishment and Modification p. 220
6.61.4 Impacts on services, entities and interfaces p. 221
6.62 Solution#62: Policy control and exposure for multi-modality services p. 221
6.62.1 Key Issue mapping p. 221
6.62.2 Description p. 221
6.62.3 Procedures p. 223
6.62.4 Impacts on services, entities and interfaces p. 224
6.63 Solution#63: Group QoS coordination and network interaction enhancement6.63.1 Key Issue mapping p. 224
6.63.2 Description p. 224
6.63.3 Procedures p. 225
6.63.3.1 Audio-Video synchronization p. 225
6.63.3.2 Enhanced interaction between AF and 5GS for Single UE p. 225
6.63.3.3 Enhanced interaction between AF and 5GS for Multiple UEs p. 226
6.63.4 Impacts on services, entities and interfaces p. 227
6.64 Solution #64: NEF based coordination across multiple PCFs for multi-modal flow groups with multiple UEs p. 227
6.64.1 Key Issue mapping p. 227
6.64.2 Description p. 227
6.64.3 Procedures p. 228
6.64.4 Impacts on services, entities and interfaces p. 231
6.65 Solution #65: QoS enhancement to support the synchronized delivery of multiple QoS flows p. 231
6.65.1 Key Issue mapping p. 231
6.65.2 Description p. 231
6.65.3 Procedures p. 233
6.65.3.1 Enhanced interaction between AF and 5GS for QoS policy coordination among multiple QoS flows p. 233
6.65.3.2 Procedure to distribute coordination group ID and group level treatment policy in 5GS p. 234
6.65.3.3 Procedure to handle group level treatment requirements in RAN p. 236
6.65.3.4 Procedure to provide RAN additional information about all QoS flows to be considered for joint admission p. 236
6.65.4 Impacts on services, entities and interfaces p. 236
6.66 Solution #66: multi-modality support p. 237
6.66.1 Key Issue mapping p. 237
6.66.2 Description p. 237
6.66.3 Procedures p. 237
6.66.3.1 General p. 237
6.66.3.2 PDU session establish procedures for multi-modality communication p. 238
6.66.4 Impacts on services, entities and interfaces p. 241
6.67 Solution #67: Supporting ECN mark for L4S in 5GS for XR/media Enhancements p. 241
6.67.1 Key Issue mapping p. 241
6.67.2 Description p. 241
6.67.3 Impacts on services, entities and interfaces p. 242
6.68 Solution #68: PDU set handling enhancements for different kinds of packets p. 242
6.68.1 Key Issue mapping p. 242
6.68.2 Description p. 242
6.68.3 Procedures p. 244
6.68.4 Impacts on services, entities and interfaces p. 244
6.69 Solution #69: PDU set handling capability of RAN node p. 244
6.69.1 Key Issue mapping p. 244
6.69.2 Description p. 244
6.69.3 Procedures p. 245
6.69.3.1 Notification upon PDU session establishment procedure p. 245
6.69.3.2 Notification upon handover p. 246
6.69.4 Impacts on services, entities and interfaces p. 246
6.70 Solution #70: PDU Set with FEC Data p. 247
6.70.1 Key Issue mapping p. 247
6.70.2.1 PDU-Set information p. 247
6.70.2.2 New QoS parameter p. 247
6.70.3 Impacts on services, entities and interfaces p. 247
6.71 Solution #71: RT latency fulfilment based on UL/DL AQP Adaptation p. 247
6.71.1 Key Issue mapping p. 247
6.71.2 Description p. 248
6.71.3 Procedures p. 248
6.71.4 Impacts on services, entities and interfaces p. 249
6.72 Solution #72: Improvements to jitter range assistance information to RAN for configuring CDRX p. 249
6.72.1 Key Issue mapping p. 249
6.72.2 Description p. 249
6.72.3 Procedures p. 250
6.72.3.1 Jitter range initial configuration p. 250
6.72.3.2 Jitter range update configuration p. 251
6.72.4 Impacts on services, entities and interfaces p. 251
6.73 Solution #73: Notification to XR AF of CDRX parameters reflecting UE's CDRX preference p. 252
6.73.1 Key Issue mapping p. 252
6.73.2 Description p. 252
6.73.3 Procedures p. 252
6.73.4 Impacts on services, entities and interfaces p. 253
6.74 Solution #74: power mode based QoS adjustment p. 254
6.74.1 Key Issue mapping p. 254
6.74.2 Description p. 254
6.74.3 Procedure p. 255
6.74.4 Impacts on services, entities and interfaces p. 255
6.75 Solution #75: QoS Enhancement to Support Trade-off of QoE and Power Consumption p. 256
6.75.1 Key Issue mapping p. 256
6.75.2 Description p. 256
6.75.3 Procedures p. 256
6.75.4 Impacts on services, entities and interfaces p. 256
7 Overall Evaluation p. 257
7.1 Evaluation for Key Issue #7 p. 257
7.2 Evaluation for Key Issue #8 p. 257
7.3 Overall Evaluation for Key Issue #9 p. 258
8 Conclusions p. 259
8.1 Conclusions for Key Issue#1 p. 259
8.2 Conclusions for Key Issue#2 p. 260
8.3 Conclusions for Key Issue#3: 5GS information exposure for XR/media Enhancements p. 260
8.4 Conclusions for KI#4 and KI#5 p. 261
8.4.1 Control plane enhancements for supporting PDU Set in downlink p. 262
8.4.2 User plane enhancements for supporting PDU Set in downlink p. 263
8.4.2.1 PDU Set Information p. 263
8.4.2.2 PDU Set Information identification on UPF and supported N6 protocols p. 263
8.4.2.3 Delivering PDU Set Information to RAN p. 263
8.4.3 PDU Set based QoS handling p. 263
8.5 Void
8.6 Conclusions for Key Issue#6: Uplink-downlink transmission coordination to meet Round-Trip latency requirements p. 263
8.7 Conclusions for Key Issue #7: policy enhancements to minimize jitter p. 264
8.8 Conclusions for Key Issue #8 p. 264
8.9 Conclusions for Key Issue #9: Trade-off of QoE and Power Saving Requirements p. 265
$ Change history p. 266
