hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 3 Definitions of terms, symbols and abbreviations | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Fully Encrypted Media Flow: A media flow where both the media header and media payload are encrypted... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion> |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 4 Architectural Assumptions and Requirements | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 4.1 Architectural Assumptions | - The architecture, framework and the QoS model as specified in TS 23.501 [2], TS 23.502 [3], and TS 23.503 [4] are regarded as the baseline for this study for both 3GPP access and non-3GPP access. The procedures for XRM in 3GPP Rel-18 are described in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4].
- The functional sp... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 4.2 Architectural Requirements | The following architectural requirements are applicable to this study:
- Solutions shall build on the 5G System architectural principles as in TS 23.501 [2]. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5 Key Issues | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.1 Key Issue #1: Support of PDU set based QoS handling enhancement | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.1.1 Description | This key issue will study PDU set based QoS handling enhancements considering both control plane and user plane perspectives. In particular, this KI will address:
- whether, what and how PDU Set based handling (e.g. new standardized 5QI, enhancements to Alternative QoS profiles, FEC, etc.) and PDU Set information (incl... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.2 Key Issue #2: Support PDU Set information identification for end-to-end encrypted XRM traffic | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.2.1 Description | The usage of end-to-end encryption is broadly deployed in current networks to provide security and the same is expected for XRM applications.
This key issue proposes to study the enhancement of PDU Set information Identification for encrypted XRM in 5G networks.
The solutions should consider the following aspect:
- If ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.3 Key Issue #3: Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.3.1 Description | This key issue aims at addressing the following points:
- Study whether, how, and what PDU Set QoS information can be used for DSCP marking on the outer header of downlink packets of the PDU Set over N3/N9 in the transport network (i.e. to enable differentiated handling of transport packets carrying PDU Sets within QoS... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.4 Key Issue #4: Traffic detection and QoS flow mapping for multiplexed data flows | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.4.1 Description | XR and interactive media services are likely to send data traffic of different media components and with different QoS requirements. Several media streams could be multiplexed on the same end-to-end transport layer connection.
For example, in XR service, several media streams could be multiplexed on a single IP 5-tuple... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.5 Key Issue #5: QoS Handling when Traffic Characteristics Change Dynamically | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.5.1 Description | Certain Rel-18 XRM features work best when the traffic pattern is mostly static. However, the traffic pattern of an XR session change (i.e. it can be dynamic) based on the usage/applications.
One example case where the traffic pattern can change dynamically is the size of media frames vary due to scene changes that may... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.6 Key Issue #6: L4S for non-3GPP access networks and intermediate 5GS nodes | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.6.1 Description | As the use-cases and applications for XRM are not limited to 3GPP access, XRM devices and applications may use non-3GPP access as a means of communication.
The objective of this Key Issue is to extend the L4S mechanism to non-3GPP access networks and the potential impacts of such extension on the non-3GPP access-specif... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.7 Key Issue #7: Support for PDU Set in non-3GPP access. | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.7.1 Description | Support for PDU Set mechanisms are specified in clause 5.37.5 of TS 23.501 [2]. 5G system supports PDU Set based QoS handling in NG-RAN with the PSA UPF identifying PDUs that belong to PDU Sets based on Protocol Description for PDU Set identification and providing PDU Set Information to the RAN in the GTP-U header. Rel... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.8 Key Issue #8: Enhancement for UE with the tethered devices | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.8.1 Description | In some XR services, the end point for those XRM service is not the UE but is the tethered device behind the UE, e.g. AR glasses tethering the cell phone. The traffic from tethered devices may require differentiated QoS handling.
This key issue aims at addressing the following points:
- Study whether and how to identif... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.9 Key Issue #9: Enhancement for XR related network information exposure | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 5.9.1 Description | In Rel-18, the 5GS can expose the following information based on the QoS Monitoring to the AF: congestion information, data rate information and round trip delay, as described in clause 5.37.4 of TS 23.501 [2]. For congestion information, this parameter can be exposed via Nupf_EventExposure service from UPF to AF, or v... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6 Solutions | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Solutions
Key Issue #
<KI #1>
<KI#2>
<KI#3>
<KI#4>
<KI#5>
<KI#6>
<KI#7>
<KI#8>
<KI#9>
#1: PDU Set content ratio awareness at RAN
X
#2: Discarding of redundant PDUs (FEC) and reporting
X
#3: FEC mechanism and PSI based PDU Set QoS Handling Enhancement
X
#4: PDU Set FEC-bas... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1 Solution #1: PDU Set content ratio awareness at RAN | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.1 Key Issue mapping | This solution addresses key issue #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.2.1 Introduction | SA WG4 recently confirmed that "Commercial XR split rendering and cloud gaming services use Application Layer Forward Error Correction (FEC)." as documented clause 5.7.4 of TR 26.926 [12]. SA WG4 also illustrated the principles underpinning the use of AL-FEC by XR applications in clause 5.7.4 of TR 26.926 [12]:
- Appli... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.2.2 Definitions | The solution is based on the following definitions:
- Definitions
- Content ratio: The ratio of PDUs of a PDU Set that are needed at the UE to be able to reconstruct the original content.
- Obsolete PDUs: All PDUs of a PDU Set that have not been transmitted to the UE yet in a situation where already enough PDUs have be... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.2.3 Solution principles | The solution is based on the following principles:
- General
- When requesting or updating QoS for a DL flow, an AF may provide to PCF/NEF - together with PDU Set QoS parameters - the content ratio for the flow. An AF may provide either PSIHI or content ratio for a flow. The AF may additionally subscribe for receiving ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.3 Procedures | Existing procedures are re-used and extended with content ratio information and the indication that PDU Set content ratio awareness is supported. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.1.4 Impacts on services, entities and interfaces | AF:
- Provide content ratio to PCF
- Receive indication of support/non-support of PDU Set content ratio awareness from SMF
PCF:
- Receive content ratio from AF and provide content ratio to SMF as part of PCC rules
- Receive indication of support/non-support of PDU Set content ratio awareness from SMF and inform AF acco... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.2 Solution #2: Discarding of redundant PDUs (FEC) and reporting | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.2.1 Key Issue mapping | This solution is for Key Issue #1, which addresses the following aspects:
- How the AF can indicate to the 5GC that the UE can handle when FEC PDU(s) is missing when the UE has received sufficient of corresponding PDU(s) so that the FEC PDUs will not be used. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.2.2 Description | In Rel-18 we support PSER (PDU Set Error Rate) and PSIHI (PDU Set Integrated Handling Information) to allow NG-RAN to identify if all PDU in the PDU Set must be delivered. If some PDUs will not be delivered, then NG-RAN knows the rate of successfully delivered PDUs in a PDU Set that is needed for the receiver to be abl... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.2.3 Procedures | The Figure 6.2.3-1 shows the procedure for how the AF indicate that NG-RAN is allowed to discard FEC PDU(s):
Figure 6.2.3-1: Procedures for AF to indicate that it is allowed to discard FEC PDU(s)
The steps of Figure 6.2.3-1 are described as follows:
1. The AF informs the PCF that the UE application allows discarding of... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.2.4 Impacts on services, entities and interfaces | AF impacts:
- Provisioning that the UE application handles discarding of redundant FEC PDU(s), i.e. the 5GS is allowed to discard FEC PDU(s) regardless of congestion.
PCF impacts:
- PDU Session procedure with support of this indication and corresponding PCC rule.
NG-RAN impacts:
- NG RAN may perform discarding of PDU(s... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.3 Solution #3: FEC mechanism and PSI based PDU Set QoS Handling Enhancement | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.3.1 Key Issue mapping | This solution is for Key Issue #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.3.2 Description | For XR traffic, the application-level FEC mechanism can be activated to generate PDU Sets including both payload data and redundant data so that entire PDU Set can still be recovered in the event of PDU losses. Meanwhile, PDU Sets within a QoS Flow may have different PSI value, which can be used by NG-RAN to perform PD... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.3.3 Procedures | Figure 6.3.3-1: Procedures for provisioning the mapping information between FEC transmission ratio and PSI value to NG-RAN
1. The AF sends a request to reserve resources for an AF session using Nnef_AFsessionWithQoS_Create request message (UE address, AF Identifier, Flow description information or External Application ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.3.4 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing 3GPP nodes and functional elements.
AF:
- Need to determine and provide the mapping information between FEC transmission ratio and PSI value to the PCF.
NEF:
- Need to authorize the AF request.
PCF:
- Need to generate the corresponding PCC rules which contain the ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4 Solution #4: PDU Set FEC-based PDU Set QoS Handling | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.1 Key Issue mapping | This solution is for KI #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.2.1 FEC | Forward Error Correction (FEC) offers high degree of fault tolerance and decreases the packet error rate (PER) and can remove the ARQ and the latency of ARQ. But FEC adds data redundancy and increases the data rate and may increase the latency.
FEC has been used in MBMS-based services in 3GPP, e.g. MCVideo.
FEC is wide... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.2.2 Different Layer of Implementation FEC for PDU Sets | If a FEC is used at PDU Set granularity, this FEC is described as PDU Set FEC, and PDU Set FEC can be implemented in application layers for the packets of a PDU Set, the Application Layer FEC is an end-to-end FEC, i.e. FEC in the AS in the DN and application in the UE;
Application Layer on end-to-end PDU Set FEC, i.e. ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.2.3 Implementation of PDU Set FEC | The AF can indicate the PDU Set FEC mode and PDU Set FEC scheme used in the application layer to the PCF.
If the PDU Set FEC is implemented in the application layer, the PCF can decide to update the PSIHI of PDU Set QoS parameters based on the PDU Set FEC scheme of the application layer PDU Set FEC or based on its loca... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.3 Procedures | Figure 6.4.3.1-1: PDU Set FEC-based PDU Set QoS Handling
0. The PDU Session for the XRM service is established.
1. If the XRM AF does not locate at trusted domain, the AF sends the Nnef_AFsessionwithQoS_Create Request to the NEF. If the XRM AF locates at trusted domain, the AF sends the Npcf_PolicyAuthorization_Create ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.4.4 Impacts on services, entities and interfaces | AF/AS:
- Provides the PDU Set FEC information (e.g. and PDU Set FEC scheme) for the XRM Stream.
- Performs the end-to-end FEC scheme if the PDU Set FEC mode is application layer FEC for the XRM stream.
PCF:
- Updates the PSER, PSDB, and PSIHI based on the PDU Set FEC Information provided by AF or based on its local pol... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 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 | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.5.1 Key Issue mapping | The solution applies to Key Issue #1. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.5.2 Description | According to RAN agreement "In case of congestion, the gNB may use the PSI for PDU set discarding" as defined in TS 38.300 [31], the RAN side DL PDU Set QoS handling is more than the handling with DL PDU Set QoS parameters(PSER, PSDB and PSIHI), it also includes other PDU Set QoS handling, e.g. PSI based PDU Set discar... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.5.3 Procedures | NOTE 1: PSI based discarding is activated in case of congestion. During no congestion, activating PDU Set Information marking wastes the PSA UPF and N3/N9 resource since it is useless. It is assumed the PDU Set Information making activation is not needed if no PDU Set handling (e.g. no congestion).
Alternative 1: RAN c... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.5.4 Impacts on services, entities and interfaces | Alternative 1: RAN control
SMF:
- Trigger the PSA UPF to activate the DL PDU Set marking based on RAN's request. If PSA UPF doesn't support PDU Set marking, the SMF rejects RAN's request.
NG-RAN:
- When there is no DL PDU Set information marking of the packets but the NG-RAN needs PDU Set Information of the packets, th... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.6 Solution #6: Enhanced Alternative QoS Profiles for PDU set based QoS handling | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.6.1 Key Issue mapping | This solution mainly applies to Key Issue #1: Support of PDU set based QoS handling enhancement. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.6.2 Description | Alternative QoS Profiles mechanism has been specified in 3GPP to support flexible QoS adaptation for V2X and other services. However, in the existing 3GPP specifications, the current AQP mechanism doesn't contain PDU-set related QoS parameters and also there is no functions specified in 5GC and NG-RAN to support AQP fo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.6.3 Procedures | Figure 6.6-1 represents the procedure of the solution and the major steps are elaborated as follows.
Figure 6.6.-1: Procedure of Enhanced Alternative QoS profiles with PDU Set based QoS handling
1. AF may provide alternative QoS requirements which can be media type related. For audio and video media traffic from differ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.6.4 Impacts on services, entities and interfaces | AF:
- To provide PDU-set related QoS requirements considering the media types within the XR traffic as assistance information to PCF to enable PCF to general PCC rules for alternative QoS profiles related to PDU set based handling.
PCF:
- To receive the provided information from AF and generate PCC rules for alternativ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.7 Solution #7: Enhancing alternative QoS profile with UL and/or DL PDU set QoS parameters | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.7.1 Key Issue mapping | This solution targets KI#1, which is listed below:
This key issue will study PDU set based QoS handling enhancements considering both control plane and user plane perspectives. In particular, this KI will address:
- whether, what and how PDU Set based handling (e.g. new standardized 5QI, enhancements to Alternative QoS... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.7.2 Description | The present solution is based on the following principles:
The Alternative QoS Profile(s) can be optionally provided for a GBR QoS Flow with Notification control enabled from SMF to the NG-RAN. An Alternative QoS Profile represents a combination of QoS parameters PDB, PER, Averaging Window and GFBR to which the applica... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.7.3 Procedures | Figure 6.7.3-1 shows the procedure for provisioning the NG-RAN with alternative UL and/or DL PDU set QoS profile and enable the notification control for it.
Figure 6.7.3-1: Procedures for supporting alternative UL and/or DL PDU set QoS profile with notification control enabled
The steps of Figure 6.7.3-1 are described ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.7.4 Impacts on services, entities, and interfaces | AF:
- Provision the alternative UL and/or DL PDU set QoS Parameters sets in a prioritized order.
PCF:
- The PCF may enable PDU set QoS Notification Control for UL and DL respectively, and include the Alternative UL/DL PDU set QoS parameter sets in the PCC rule sent to the SMF.
SMF:
- The SMF sends a prioritized list of... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.8 Solution #8: Consistent PDU Set Handling between AF and 5GS | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.8.1 Key Issue mapping | This solution is related to two KIs:
- It addresses Key Issues #1 since it proposes to enhance PDU Set QoS handling, specifically how PDU Set information provided by the AF/AS can be enhanced.
- It is also related to Key Issue #4 since the additional information provided by the AF may indicate PDU Set processing for di... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.8.2 Description | Two scenarios for determining PDU Set information are supported in 3GPP Rel-18.
- The application uses an RTP header extension purposely defined for 5GS PDU Set handling, such as the RTP Header Extension (HE) defined by SA WG4 in TS 26.522 [20]. In this case the application determines "what is a PDU Set" (e.g. frame or... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.8.3 Procedures | Figure 6.8.3-1 shows the procedure for PDU Set QoS handling coordinated with AF.
Figure 6.8.3-1: Procedure for PDU Set QoS handling coordinated with AF
1. AF sends PDU Set Types, PDU Set Importance information and SDP (additional information) to the NEF.
NEF sends the additional information to the PCF.
2. When PDU Set ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.8.4 Impacts on services, entities and interfaces | AF:
- Provides SDP, PDU Set Types and PDU Set Importance to NEF/PCF.
PCF:
- Includes new information in PCC rules.
SMF:
- Includes new information in QoS Rules (for uplink) and N4 Session information (for downlink).
RAN:
- No Impact.
UPF:
- If DL PDU Set handling is supported: Performs PDU Set Type Detection and assign... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.9 Solution #9: PDU Set information identification for encrypted traffic | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.9.1 Key Issue mapping | This solution applies to Key Issue #2: Support PDU Set information identification for end-to-end encrypted XRM traffic and Key Issue #4: Traffic detection and QoS flow mapping for multiplexed data flows. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.9.2 Description | Media over QUIC (MoQ) is a simple low-latency media delivery solution for interactive media, live media and hybrid interactive and live media, the media will be mapped onto underlying QUIC mechanisms (QUIC streams and/or QUIC datagrams) and can be used over raw QUIC or WebTransport.
The basic data element of Media over... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.9.3 Procedures | For the XR traffic between UE and Application Server, the UPF of the PDU session acts as MoQ Relay and identifies PDU Set Information and demultiplex sub-flows based on metadata of MoQ. There will be a MoQ Transport connection between UE and MoQ Relay, also a MoQ Transport connection between the MoQ Relay and Applicati... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.9.4 Impacts on services, entities and interfaces | UPF:
- Implements the MoQ Relay functionality. Identifies PDU Set Information and demultiplex sub-flows based on received metadata of MoQ.
SMF:
- Updates UPF with N4 rule, which includes the Track id in the PDR.
PCF:
- Includes the Track id as part of Service data flow detection of PCC rule.
AF:
- Provides one or more ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10 Solution #10: PDU Set information identification based on MoQ | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10.1 Key Issue mapping | This solution addresses the Key issue #2 to Support PDU Set information identification for end-to-end encrypted XRM traffic. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10.2 Description | QUIC is a UDP-based, stream-multiplexing, encrypted transport protocol that is widely accepted. However, QUIC natively integrates TLS encryption technology, making it difficult for the network intermediate node to identify the application layer information such as PDU Set information.
Media over QUIC (MoQ) develops a s... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10.3 Procedures | The procedures is used for QUIC connection establishment with encrypted traffic during UE requested PDU Session Establishment procedure. The network could help to identify the PDU set information based on the AF provided assistance information. During PDU session Establishment procedure, SMF selects UPF supporting MoQ ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10.4 Detailed MoQ mechanism in UE, UPF and Application Server | The interaction among client, relay, and server is achieved by a subscription procedure defined in MoQ [9]:
Publishing through the relay starts with publisher sending ANNOUNCE control message with a Track Namespace to advertise where the receiver can route SUBSCRIBEs for tracks within the announced Track Namespace. Upo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.10.5 Impacts on services, entities and interfaces | AF/AS:
- Provide Encrypted Traffic Handling Assistance Information along with the Protocol description.
PCF:
- Determine PCC Rules based on Encrypted Traffic Handling Assistance Information and the Protocol Description.
SMF:
- Provide N4 rule to activate the MoQ relay functionality of UPF.
- Indicate UPF to establish Q... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11 Solution #11: RTP over QUIC based Encrypted Traffic Detection, Identification, and QoS flows mapping | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11.1 Key Issue mapping | This solution addresses Key Issue #2: "Support PDU Set information identification for end-to-end encrypted XRM traffic". |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11.2 Description | This solution is proposed to enable the support of PDU Set related handling for end-to-end encrypted traffic using RTP over QUIC (RoQ) [8]. RTP over QUIC allows RTP packets to be encapsulated within QUIC packets via QUIC streams and datagrams to transport real-time data within a QUIC connection for a specific IP flow (... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11.3.1 PDU Set based QoS handling for RTP over QUIC based encrypted traffic | Figure 6.11.3.1-1: Procedure for PDU Set based QoS handling for RTP over QUIC-based encrypted traffic
The process includes the following steps:
0. PDU Session Establishment procedure (defined in clause 4.3.2.2.1 of TS 23.502 [3]) are performed. A network slice type for XR service can be used for such a PDU Session.
1. ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.11.4 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing 3GPP nodes and functional elements. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12 Solution #12: Obfuscated Metadata to Classify Payload in Encrypted Media Packets | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.1 Key Issue mapping | This solution addresses aspects of:
Key Issue #2: PDU set information identification in an end-to-end encryption scenario.
Key Issue #4: Identify multiplexed traffic flows in QUIC (NOTE: QUIC streams/identifiers are fully encrypted).
Key Issue #5: Identify what characteristics are dynamically changed. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.2 Description | Some or all information needed for classifying into PDU sets are not available in media packets with encrypted payloads and headers (or header extensions). In this solution, the media server (or AS) provides explicit information for characterizing the media payload in the packet. In addition to encrypted headers/media ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3.1 E2E Sequence of Operations | This sequence of operations consists of a configuration phase where the media server derives multiple sets of "obfuscated codes" (OFC) /128-bit random codes corresponding to different levels of {importance, delay tolerance, start/middle/end} or relative priority of streams. The OFC are configured between two domains an... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3.2 Obfuscated Codes and Metadata | Obfuscated codes (OFC) are random numbers (128 bit) that are associated to sensitive application metadata. Application metadata consists of parameters that identifies the media data unit (MDU) to which the packet belongs and characterizes the QoS requirements on the network path that may be applied. A Media Data Unit (... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3.3 Initial Configuration of Obfuscated Codes, Metadata and Keys | The application domain configures groups of obfuscated codes (OFC), each associated to a set of metadata. The groups of OFC/associated metadata are configured between the AF and NEF/PCF as outlined in clause 6.12.3.1, step 1. The out-of-band, secure configuration of OFC before use in per-packet media packets allows the... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.12.3.4 Per-packet Transport of Metadata | The metadata provisioned in clause 6.12.3.3 may in principle use any transport that can carry the data. However, this solution proposes UDP options in an encapsulated packet as it provides a transport that is general for various types of media packets (UDP and TCP if needed) while providing low overhead. Since UDP opti... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.