hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3.5 Classifying and Mapping into PDU sets | The above clauses describe how application metadata can be transported from the media server to the UPF. However, the application metadata needs to be used to map into PDU sets.
Figure 6.12.3.5-1: Example of Obfuscated codes in media packets
Figure 6.12.3.5-1 shows an example of obfuscated codes and other metadata (ref... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.4 Impacts on services, entities and interfaces | AF:
- Extensions to provide application metadata to OFC configuration to the NEF (or directly to the PCF).
NEF:
- Receives multiple sets of application metadata to OFC configuration from the AF.
PCF:
- Receives multiple sets of application metadata to OFC configuration from the NEF (or directly from the AF). Creates PC... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.13 Solution #13: Multiple DSCP markings per QoS Flow | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.13.1 Key Issue mapping | This solution addresses Key Issues #3 (Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network). |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.13.2 Description | Illustrated in Figure 6.13.2-1 is a solution for multiple DSCP markings per QoS Flow.
Figure 6.13.2-1: Multiple transport level marking per QoS Flow
The following are the salient features of this solution:
- The FAR includes a Transport Level Marking List that contains a list of PDU Set Importance values, each of which... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.13.3 Procedures | There are no changes to existing procedures; only a new parameter (Transport Level Marking List) in the FAR. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.13.4 Impacts on services, entities and interfaces | SMF impact:
- Ability to send a Transport Level Marking List in the FAR associated with a QoS Flow carrying PDU Sets and/or End of Data Burst indication. In the alternative solution, SMF instructs UPF via FAR to assign per PDU Set DSCP values for downlink traffic, either based on UPF's determination or from a specific ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.14 Solution #14: Extending Packet Filter Set to identify multiplexed traffic flows within a single transport connection | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.14.1 Key Issue mapping | This solution addresses Key Issues #4(Traffic detection and QoS flow mapping for multiplexed data flows). |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.14.2 Description | When several media streams are multiplexed on the same transport layer connection, e.g. when Transport protocol like IETF QUIC [11] is used, current Packet Filter Set can be extended by adding stream info to identify the media streams within a single transport connection. The stream info, for example, could be Connecti... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.14.3 Procedures | The procedure to identify multiplexed traffic flows is described in Figure 6.14.3-1.
Figure 6.14.3-1: Procedure to identify multiplexed traffic flows
1. AF provides service information to the PCF by invoking Npcf_PolicyAuthorization_Create Request or Npcf_PolicyAuthorization_Update Request service operation as describe... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.14.4 Impacts on services, entities and interfaces | PCF impact:
- providing PCC rule(s) with extended Packet Filters to SMF.
SMF impact:
- providing N4 rule(s) with extended Packet Filters to UPF.
- providing QoS rule(s) with extended Packet Filters to UE.
UPF impact:
- performs DL traffic filtering based on the IP/UDP/N6 tunnel header and the extended Packet Filters.
U... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.15 Solution #15: Traffic Detection and QoS mapping for XR and Media services. | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.15.1 Key Issue mapping | This solution applies to Key Issue #4: Traffic detection and QoS flow mapping for multiplexed data flows. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.15.2 Description | XR and media traffic may be composed of multiple media streams including audio, video and haptic etc. These media stream may have different characteristics and different QoS requirements. This solution proposes to enable the support of traffic detection and QoS mapping for XR and media traffic with multiple media strea... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.15.3 Procedures | 1. AF provides QoS requirements for different media streams or media types (e.g. audio, video, haptic) and also the encapsulation protocol parameters to 5GS.
a) AF can provide high granularity QoS requirements considering the different media types e.g. audio, video, haptic etc. e.g. RTP payload type 96 and 97 stands fo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.15.4 Impacts on services, entities and interfaces | UPF:
- Perform traffic detection and QoS mapping according to SMF configuration.
SMF:
- Configure UPF with N4 rule, QoS profile and QoS rules to NG-RAN and UE for traffic detection and QoS mapping.
PCF:
- Generate the PCC rules according to the inputs from AF.
AF:
- Provide QoS requirements for different media streams ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.16 Solution #16: AS based trigger of data boost handling with reflective QoS | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.16.1 Key Issue mapping | This solution is for Key Issue #5, to support dynamic change (via user plane) in traffic characteristics provided by the application in the DN. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.16.2 Description | The xR traffic patterns, based on user interactions may vary greatly. For example, an xR application may require the UE to send a picture/video (10MB file), a short speech (100kB file), and locality info like geolocation/temperature/time (10kB file) to the AS. While in other cases, only a short speech (100kB file) and ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.16.3 Procedures | Figure 6.16.3.1-1: AS requests 5GS to upgrade QoS using reflective QoS feature
0. UE is authorized to use multiple 5QI based on network policy (e.g. 5QI-6 and 5QI-10) when registered to the network.
Those QoS flows are established during PDU session establishment procedure as defined in TS 23.501 [2].
UE and Network su... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.16.4 Impacts on services, entities and interfaces | AS/AF:
- Based on application requirements, include expediate request in the metadata to 5GC over N6.
UPF:
- Based on metadata received from AS via N6 and N4 rules, invoke Reflective QoS feature by selecting an established QoS Flow with a higher quality 5QI.
PCC/SMF:
- Indication to use Reflective QoS in the QER associ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17 Solution #17: L4S in non-3GPP access networks | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.1 Key Issue mapping | This solution proposes a solution for KI #6. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.2.1 General | L4S (Low Latency, Low Loss and Scalable Throughput) is described in IETF RFC 9330 [14], IETF RFC 9331 [15] and IETF RFC 9332 [19]. It exposes congestion information by marking ECN bits in the IP header of the user IP packets between the UE and the application server to trigger application layer rate adaptation. In 5G S... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.2.2 Support of ECN marking for L4S in wireline node(s) | For wireline cable access network e.g. DOCSIS, provides support for low-latency services through the dual-queue approach, by separating queue-building and non-queue-building traffic [18]. DOCSIS, such as Low Latency DOCSIS (LLD), also supports ECN marking for L4S, where L4S traffic would be managed separately from othe... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.2.3 Supporting of ECN marking for L4S in wireless N3IWF deployments | It is most probable that if congestion is experienced in the uplink, it is related to the wireless link (i.e. WiFi AP). 3GPP does not have responsibility for the AP specification but can relay any congestion notification that the WiFi AP provides to the inner most IP layer at the N3IWF. This is accomplished by leveragi... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.2.4 Supporting of ECN marking for L4S in wireless TNAN deployments | Trusted (i.e. TNAN) access support for L4S is similar to un-trusted, although 3GPP has responsibility for specifying NWt with can leverage IETF RFC 6040 [47] and draft RFC draft-ietf-tsvwg-ecn-encap-guidelines-22 [16] as described in clause 6.17.2.3.
Figure 6.17.2.4-1: Congestion in uplink detected at TNAP of non-3GPP ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.3.1 Procedures in wireline 5G access network | Figure 6.17.3.1-1: High-level procedure of the solution for W-AGF and 5G-RG
1. Steps 1-2a specified in clause 7.3.1.1 of TS 23.316 [17], with the difference that the 5G-RG 5GSM Core Network Capability included in the PDU Session Establishment Request within the N1 SM container indicates whether the 5G-RG supports ECN m... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.3.2 Procedures in untrusted non-3GPP access | Figure 6.17.3.2-1: High-level procedure for untrusted non-3GPP access
1. Steps 1-2a specified in clause 4.12.5 of TS 23.502 [3], with the difference that the N2 SM information carries information that the AMF shall forward to the N3IWF which includes: For each QoS Flow, an ECN marking for L4S indicator in the case of E... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.3.3 Procedures in trusted non-3GPP access | Figure 6.17.3.3-1: High-level procedure for trusted non-3GPP access
1. Steps 1-2a specified in clause 4.12.5 with the modifications specified in clause 4.12a.5 of TS 23.502 [3], with the difference that the N2 SM information carries information that the AMF shall forward to the TNGF which includes: For each QoS Flow, a... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.4 Impacts on services, entities and interfaces | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.4.1 Wireline non-3GPP 5G access network | SMF:
- Indication of ECN marking for L4S to 5G-RG over N1.
- Configuration of QoS profiles to W-AGF including L4S handling.
W-AGF:
- Mapping of L4S-enabled QoS profile to L4S-enabled W-UP resource.
- Supports ECN marking for L4S like NG-RAN node as specified in TS 23.501 [2].
5G-RG:
- Mapping of L4S-enabled QoS rule to... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.17.4.2 Wireless non-3GPP 5G access network | Table 6.17.4.2-1 summarizes the alternative solutions described in clauses 6.17.2.3 and 6.17.2.4.
Table 6.17.4.2-1: Summary of alternative solutions
Congestion
ECN Support (i.e. Marking or Copying) for L4S performed by
Comments
Detected in
UE
N3IWF
TNGF
PSA UPF
UL @ UE
N/A
N/A
N/A
N/A
Not Applicable
UL @ AP
Figure 6.17... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18 Solution #18: PDU Set handling in wireline/wireless non-3GPP access | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.1 Key Issue mapping | This solution proposes a solution for the following issue in KI #7:
- Support PDU set QoS in wireline access (e.g. W-AGF), non-3GPP intermediate access nodes (N3IWF, TNGF), UE. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.2.1 General | To support PDU Set based QoS handling in the non-3GPP access nodes (UE/5G-RG, N3IWF, TNGF, W-AGF), PDU Set QoS Parameters and PDU Set Information need to be provided to the non-3GPP access nodes.
The proposed solution has the following principles:
- PDU Set QoS Parameters specified for NG-RAN may be supported in non-3G... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.2.2 Supporting PDU Set based QoS handling in non-3GPP access nodes | The PDU Set based QoS handling by the non-3GPP access nodes is determined by PDU Set QoS Parameters in the QoS profile of the QoS Flow and PDU Set Information provided by the PSA UPF.
For QoS Flows with PDU Set based QoS handling enabled, PDU Set QoS Parameters are determined by the PCF (based on information provided b... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.3.1 Procedures in wireline 5G access network | Figure 6.18.3.1-1: High-level procedure of the solution for W-AGF and 5G-RG
1. Steps 1-2a specified in clause 7.3.1.1 of TS 23.316 [17].
2a. The N2 SM information carries information that the AMF shall forward to the W-AGF which includes: at least one PDU Set QoS parameter to activate PDU Set QoS handling for a given Q... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.3.2 Procedures in untrusted non-3GPP access | Figure 6.18.3.2-1: High-level procedure for untrusted non-3GPP access
1. Steps 1-2a specified in clause 4.12.5 of TS 23.502 [3], with the difference that the N2 SM information carries information that the AMF shall forward to the N3IWF which includes: at least one PDU Set QoS parameter to activate PDU Set QoS handling ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.3.3 Procedures in trusted non-3GPP access | Figure 6.18.3.3-1: High-level procedure for trusted non-3GPP access
1. Steps 1-2a specified in clause 4.12.5 with the modifications specified in clause 4.12a.5 of TS 23.502 [3], with the difference that the N2 SM information carries information that the AMF shall forward to the TNGF which includes: at least one PDU Set... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.18.4 Impacts on services, entities and interfaces | SMF:
- Sending Protocol Description associated with QoS Rule to 5G-RG over N1.
W-AGF:
- Mapping of PDU Set-enabled QoS profile to corresponding W-UP resources.
- Supporting PDU Set based QoS.
N3IWF/TNGF:
- Mapping of PDU Set-enabled QoS profile to corresponding access resources.
- Supporting PDU Set based QoS.
5G-RG:
-... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19 Solution #19: Alternative PDU Set QoS parameters to support differentiated QoS handling and Alternative QoS/Alternative PDU Set QoS Exposure | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.1 Key Issue mapping | This solution is for KI #1 PDU Set based QoS handling enhancement for XR/media services, and KI #9 enhancement for XR related network information exposure. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.2.1 Alternative PDU Set QoS parameters to support differentiated QoS handling | This solution enhanced alternative QoS mechanism to support PDU Set QoS parameters between AF and the 5GS. The existing Alternative QoS profile could be enhanced to support alternative PDU Set QoS parameter Set(s) including PSDB and PSER. AF provides one or more Requested Alternative PDU Set QoS Parameter Sets (includi... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.2.2 Alternative QoS/PDU set QoS Notification Exposure | Alternative QoS/PDU Set QoS Notification through Control Plane. AF may subscribe the Alternative QoS/PDU set QoS Notification to NEF/PCF. If the NG-RAN determines that the QoS profile (including the PDU Set QoS parameters) cannot be fulfilled, NG-RAN shall send a notification towards SMF. And the NG-RAN shall check whe... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.3.1 Procedures of alternative PDU Set QoS handling | The procedure of alternative PDU Set QoS handling is described in Figure 6.19.3.1-1.
Figure 6.19.3.1-1: High level procedure of alternative PDU Set QoS handling
1. The AF provides Alternative Service Requirements to the NEF using Nnef_AFsessionWithQoS_Create request, including one or more Requested Alternative QoS/PDU ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.3.2 Procedures of network information exposure via user plane | The procedure of network information exposure via user plane is described in Figure 6.19.3.2-1.
Figure 6.19.3.2-1: Network information exposure via user plane
1. The AF provides Alternative Service Requirements to the NEF using Nnef_AFsessionWithQoS_Create request, including one or more Requested Alternative QoS Parame... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.3.3 Procedures of network information exposure via control plane | The NG-RAN may also send the Notification together with the reference to the SMF via control plane. Alternatively, after receiving the Notification together with the reference from the RAN, the UPF may be instructed to send them to the SMF via the N4 interface. As legacy, the SMF provides the Notification to the AF via... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.19.4 Impacts on services, entities and interfaces | AF:
- Provides the QoS requirements which include additional one or more Requested Alternative PDU Set QoS Parameter Sets (e.g. PSDB, PSER), the corresponding reference to each PDU Set QoS Parameter Set.
- Subscribes to receive Alternative QoS Notifications via user plane when the QoS targets can no longer (or can agai... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.20 Solution #20: Nominal PSDB | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.20.1 Key Issue mapping | This solution addresses key issue #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.20.2 Description | Periodic XR traffic may not necessarily be truly periodic. One reason is that the application server may not send media traffic at equidistant time intervals due to e.g. differences in scene complexity. In case of a simple scene, the application server may be done rendering an image in less time than it takes to render... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.20.3 Procedures | Existing procedures are re-used. PDU Set QoS in existing procedures is extended by NPSDB. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.20.4 Impacts on services, entities and interfaces | AF:
- Provide Nominal PSDB to PCF.
PCF:
- Receive Nominal PSDB from AF and provide Nominal PSDB to SMF as part of PCC rules.
SMF:
- Receive Nominal PSDB from PCF and provide Nominal PSDB to RAN.
NG-RAN:
- Support receiving Nominal PSDB for a QoS flow and support enforcing Nominal PSDB. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.21 Solution #21: Enhancing PDU Set QoS Handling with Dynamic FEC Related Information Marking in GTP-U | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.21.1 Key Issue mapping | This solution addresses Key Issue #1, "Support of PDU set based QoS handling enhancement". |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.21.2 Description | The XRM traffic may undergo Forward Error Correction, where source data packets are used to generate additional data, called repair packets. Repair packets are generated according to the FEC scheme and transmitted with the source data packets. The repair packets help in the detection and correction of errors in the dat... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.21.3 Procedures | Figure 6.21.1-1: Setting up with FEC Assistance Information
1. The AF invokes Nnef_AFsessionWithQoS_Create to the NEF. The message includes Flow description(s).
For each flow description, the AF may provide Assistance Information that
- indicates whether traffic that matches the Flow Descriptor (e.g. SSRC of source pac... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.21.4 Impacts on services, entities and interfaces | AF:
- Provides Assistance Information to the NEF (or to the PCF directly).
NEF:
- Receives Assistance Information from the AF.
- Provides Assistance Information to the PCF.
PCF:
- Receives Assistance Information from the NEF (or directly from the AF).
- Creates PCC Rules that indicate include the Assistance Information... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22 Solution #22: The handling UL PDU Set QoS parameters | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.1 Key Issue mapping | This solution addresses key issue #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.2 Description | As approved in RAN R2-2312136, the PDU Set QoS handling depends on UE's indication via UAI: when PDU Set identification is possible for a QoS flow, this is indicated to the gNB by the UE.
In the uplink, the UE needs to be able to identify PDU Sets and Data Bursts dynamically, including PSI. How this is done is left up ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.3.1 Alternative1 | Figure 6.22.3.1-1: Procedure
1. When the NG RAN knows the UL PDU Set handling is possible for a QoS flow, the NG RAN notifies UL PDU Set handling is possible for a QoS flow to the SMF.
2. The SMF may update the QoS profile for the QoS flow to provide UL PDU Set QoS to the NG RAN upon knowing the PDU Set handling is pos... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.3.2 Alternative2 | Figure 6.22.3.2-1: Procedure
1. The SMF provides UL PDU Set QoS to the NG RAN for a QoS flow as legacy.
2. Upon reception of the UL PDU Set QoS, if the UL PDU Set handling is not possible for a QoS flow, the NG RAN notifies to the SMF that the UL PDU Set is not fulfilled due to UL PDU Set handling is not possible for a... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.22.4 Impacts on services, entities and interfaces | Alternative1
NG RAN:
- When the NG RAN knows the UL PDU Set handling is possible for a QoS flow, the NG RAN notifies UL PDU Set handling is possible for a QoS flow to the SMF.
SMF:
- Upon knowing the PDU Set identification is possible for a QoS flow, provide UL PDU Set QoS to the NG RAN.
NOTE: Before knowing that UL PD... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.23 Solution #23: PDU set discard based on PDU sets correlation info from AS/AF | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.23.1 Key Issue mapping | This solution is for Key Issue #1, which enhances the PDU set based QoS handling by using the additional information (i.e. PDU set correlation info) provided by AS/AF for better congestion handling. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.23.2 Description | For real time application, the stale data if received by the device may not be useful for rendering and is only wasting the battery on the UE due to transceiver usage and computation processing. Considered that AR glass is limited in form factor, any radio transmission that does not produce any meaningful outcome to en... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.23.3 Procedures | Rel 18 procedure for sending PDU Set information to RAN is reused (i.e. via additional information carried by RTP extension header over N6 and GTP-U extension header over N3).
This solution proposes to introduce PDU Set correlation information as part of PDU Set information. PDU Set correlation information:
Identifies ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.23.4 Impacts on services, entities and interfaces | AS/AF:
- If required, include PDU Set correlation info as part of the PDU Set Information.
NOTE: RTP extension header will need to be extended by SA4.
SMF/PCF:
- The "action to be performed" (e.g. discarding) for independent and dependent PDU set is signalled to RAN as new information element via N2 container.
UPF:
- M... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24 Solution #24: PDU set identification when an end-to-end XR session is fully encrypted using a tunnelled connection over N6 | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.1 Key Issue mapping | This solution addresses key issue #2. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.2 Description | The transport of multimedia application data (e.g. AR/VR/XR, interactive and streaming services, web applications) is often conveyed over RTP protocol.
For supporting XR media over 3GPP, 3GPP defined extensions to the RTP headers allowing an XR media application server to provide additional information to assist the 3G... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.3.1 General procedure | Details steps of the procedure are shown in Figure below:
Figure 6.24.3.1-1: General procedure for supporting PDU set identification for fully encrypted media packets
1. An AF requests to establish an AF session with QoS by invoking the Nnef_AFSessionWithQoS Create service operation as described in clause 4.15.6.6 of T... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.3.2 Using Connect-UDP | The architecture when using Connect-UDP protocol between the UPF and AS is shown in Figure 6.24.3.2-1.
Figure 6.24.3.2-1: Using Connect-UDP or HTTP/3 proxy for proxying fully encrypted media packets via N6
The main procedure using QUIC/Connect-UDP is as follows:
1. An AF when requesting an AF session towards the 3GPP n... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.24.4 Impacts on services, entities and interfaces | UPF:
- UPF supporting an encapsulation protocol, e.g. Connect-UDP. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.25 Solution #25: Preconfigured N6 tunnelling and GTP-U header extension for conveyance of PDU Set-related information | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.25.1 Key Issue mapping | This solution addresses Key Issues #2 (Support PDU Set information identification for end-to-end encrypted XRM traffic). |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.25.2 Description | This solution assumes that there is a set of preconfigured N6 tunnels between the UPF serving as a PDU Session Anchor (PSA) in the 5GS on one hand and a trusted 5G-XR Application Server (5G-XR AS) on the other hand, as illustrated in Figure 6.25.2-1.
Figure 6.25.2-1: 5G-XR support with N6 tunnels
The following are the ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.25.3 Procedures | The UE wishing to access XR services requests a PDU Session using a preconfigured DNN/S-NSSAI.
Based on the requested DNN/S-NSSAI the SMF selects a UPF with preconfigured GTP-U tunnel(s) on N6.
The rest of the mechanisms in this solution (i.e. copying PDU Set information from the N6 tunnelling header into GTP-U headers... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.25.4 Impacts on services, entities and interfaces | UPF impact:
- Ability to copy PDU Set-related information from the N6 tunnelling header into the GTP-U header extension inside the Frame format for the PDU Session user plane protocol defined in clause 5.5.2 of TS 38.415 [36].
- Ability to use the PDU Set-related information received in the N6 tunnelling header e.g. fo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26 Solution #26: PDU Set identification for end-to-end encrypted traffic | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.1 Key Issue mapping | This solution addresses Key Issue #2: "Support XRM metadata identification for end-to-end encrypted XRM traffic". |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.2 Description | This solution proposes to enable the support of PDU Set related handling for end-to-end encrypted traffic, first with a general tunnelling framework and then using QUIC as transport protocol and XRM metadata with XRM metadata in UDP tunnel packets as in-band communication between 5GS and the content-provider AS. The en... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.3 General framework | The solution proposes to have a framework where fully encrypted packets from an application server are tunnelled via an encapsulation protocol between the UPF and the Application Server over the N6 reference point as shown in Figure 6.26.3-1.
Figure 6.26.3-1: General framework for supporting PDU set identification for ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.3.1 General procedure | Details steps of the procedure are shown in Figure below:
Figure 6.26.3.1-1: General procedure for supporting PDU set identification for fully encrypted media packets
1. An AF requests to establish an AF session with QoS by invoking the Nnef_AFSessionWithQoS Create service operation as described in clause 4.15.6.6 of T... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.4 PDU Set based QoS handling using UDP-connect | The solution is based on the following principles:
- To receive PDU Set information from the AS in a secure way, the UPF establishes a UDP tunnel to the AS by sending an HTTP request with the "connect-udp" upgrade token to an HTTP proxy integrated in the AS and indicating the capability to receive XRM metadata associat... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.4.1 PDU Set based QoS handling for end-to-end encrypted XRM traffic | Figure 6.26.4.1-1: Procedure for PDU Set based QoS handling for QUIC-based encrypted traffic
The process includes the following steps:
1. PDU Session Establishment procedure (defined in clause 4.3.2.2.1 of TS 23.502 [3]) is performed.
2. The AF sends Nnef_AFsessionWithQoS_Create request to the PCF/NEF as defined in cla... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.26.5 Impacts on services, entities and interfaces | AF:
- Provides the Protocol Description with an indication of HTTP datagrams for PDU Set Information within Nnef_AFsessionWithQoS_Create request.
- Provides the FQDN address of the target AS within Nnef_AFsessionWithQoS_Create request.
PCF:
- Receives the Protocol Description and the FQDN of the AS from the AF.
- Gener... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.27 Solution #27: Differentiated Handling for Transporting Encrypted XRM traffics Using Metadata over N6 | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.27.1 Key Issue mapping | This solution addresses Key Issue #2: "Support PDU Set information identification for end-to-end encrypted XRM traffic", Key Issue #3: "Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network", and Key Issue #4: "Traffic detection and QoS flow mapping for multiplexed data flows". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.