Use a QUIC-aware proxy to handle encrypted XRM traffic.
By using QUIC session metadata to mark the DSCP bit in the outer header of IP packets in 5G networks, the problem of differentiated processing of PDU sets under end-to-end encrypted traffic is solved, improving resource utilization efficiency and service quality.
Patent Information
- Application Number
- CN202580027622.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-03-29
- Filing Date
- 2025-03-31
- Publication Date
- 2026-11-17
AI Technical Summary
In 5G networks, existing technologies cannot effectively differentiate and process transport-level packets carrying PDU sets within QoS streams, especially in the case of end-to-end encrypted traffic, leading to resource waste and inefficient scheduling.
By receiving and processing rule sets carrying end-to-end encrypted traffic in the network functions of the core network, and using the metadata of the QUIC session to mark the DSCP bit in the outer header of IP packets, differentiated processing of PDU sets can be achieved.
It achieves effective differentiation of PDU sets, improves resource utilization efficiency, and ensures the quality of XRM service with high data rate and low latency requirements.
Smart Images

Figure CN123125941A_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 572,176, filed March 29, 2024, entitled "Handling Encrypted XRM Traffics using QUIC Aware Proxying," the entire contents of which are expressly incorporated herein by reference. Technical Field
[0003] This disclosure generally relates to wireless communications, and more specifically to the differentiated handling of transport-level packets carrying a set of packet data units (PDUs) within a Quality of Service (QoS) stream in a wireless communication network. Background Technology
[0004] This background description is provided for the purpose of presenting the general context of this disclosure. The work of the currently named inventors (to the extent described in this background section) and aspects of this description that may not be considered prior art at the time of filing are neither expressly nor implicitly acknowledged as prior art to this disclosure.
[0005] Base stations operating according to the fifth-generation (5G) New Radio (NR) requirements support significantly greater bandwidth than fourth-generation (4G) base stations. In some cases, base stations can transmit data associated with extended reality (XR) to user devices or user equipment (UEs), which refers to technologies such as augmented reality (AR), virtual reality (VR), mixed reality (MR), and cloud gaming. These technologies generally involve quasi-periodic streaming and are associated with high data rates and low latency requirements.
[0006] The 3rd Generation Partnership Project (3GPP) recently proposed that 5G systems (5GS) begin to offer support for advanced media services, such as High Data Rate Low Latency (HDRLL) services, Augmented Reality (AR) / Virtual Reality (VR) / Extended Reality (XR) services, and haptic / multimodal communication services. XR and media services can also be referred to as "XRM services." Generally, 3GPP has proposed enhancements to network openness for supporting interaction between 5GS and XRM applications, as well as enhancements to Quality of Service (QoS) and policies for XR and media service transmission.
[0007] In current 5GS, a QoS flow represents the finest granularity of QoS differentiation within a PDU session. 5G QoS features correspond to the 5G QoS identifier (5QI). 5GS treats each packet in a QoS flow according to the same QoS requirements. However, it has been proposed that the Session Management Function (SMF) control the QoS flow and pre-configure or establish the QoS flow via the Protocol Data Unit (PDU) session establishment process or the PDU session modification process.
[0008] The characteristics of a QoS flow include a QoS profile, which the SMF can provide to the AN (Access Network) via the Access and Mobility Management Function (AMF) through the N2 reference point, or the AN can pre-configure the QoS profile. The characteristics of a QoS flow further include one or more QoS rules and optionally associated QoS flow-level QoS parameters, which the SMF can provide to the User Equipment (UE) via the AMF through the N1 reference point, or the UE can derive these rules and parameters by applying reactive QoS control. Furthermore, the characteristics of a QoS flow include one or more uplink (UL) and downlink (DL) packet detection rules (PDR), which the SMF can supply to the User Plane Function (UPF).
[0009] However, XRM services may rely on PDU sets, which are groups of packets carrying payloads (such as frames, slices, or tiles). More specifically, a PDU set consists of one or more PDUs carrying a payload (e.g., a frame or video slice for XRM services) of a single information unit generated at the application layer, which have the same importance requirements at the application layer. The application layer typically requires all PDUs in the PDU set to process the corresponding information unit. However, in some cases, when some PDUs are lost, the application layer can recover portions of the information unit.
[0010] The media layer decodes and processes packets within such a PDU set as a whole because packets within a PDU set have inherent dependencies on each other at the media layer. For example, the media layer can only decode a frame / video slice if all packets or a minimum number of packets carrying the frame / video slice have been successfully delivered. As another example, a client application can only decode frames within a GOP (Group of Pictures) after successfully receiving all frames that a particular frame depends on.
[0011] Because XRM services typically require high data rates and low latency, the 5GS QoS framework needs enhancements to support different QoS treatments for PDU sets. Without considering such dependencies between packets within a PDU set, 5GS might perform scheduling inefficiently. For example, 5GS might drop some packets but attempt to deliver others that client applications using the same PDU set cannot use, thus unnecessarily wasting radio resources. Similarly, considering the characteristics of PDU sets, audio samples, haptic applications, and remote control operations can benefit from 5GS. As another example, PDU sets can carry different content (e.g., I / B / P frames, slices / tiles within I / B / P frames, etc.), and therefore allow 5GS to process packets belonging to less important PDU sets (e.g., PDUs) differently, to utilize resources more efficiently.
[0012] Most XRM services use streaming protocols based on Real-time Transport Protocol (RTP), Secure RTP (SRTP), or HTTP for streaming. For end-to-end encryption, DTLS or TLS is further applied to the RTP / SRTP or HTTP-based protocols, respectively.
[0013] According to one possible approach, the network device maps media service data streams (associated with a set of IP 5-tuples) to a QoS stream and uses the same transport-level tag (i.e., differentiated service code point (DSCP) tag) to map all transport packets associated with the same QoS stream. Since these packets have the same DSCP value in the outer IP header, transport-level packets carrying the PDU set within the QoS stream are treated equally in the transport network. Therefore, in 5G networks, there is no differentiated treatment for transport-level packets carrying the PDU set within the QoS stream.
[0014] Although DSCP marking can be performed in IP packet headers based on PDU set importance (PSI) information included in the media packet header (e.g., the RTP extension header as defined in 3GPP TS26.522 v0.1.1 (2023-08)), this approach requires the assumption that the media packet header information necessary for PDU set identification is not encrypted, and that the PSA UPF can identify the PDU set and use the PDU set information to perform GTP-U header marking.
[0015] Although several further approaches have been considered, it remains unclear how network devices can utilize DSCP tags for end-to-end encrypted traffic in the downlink direction to differentiate transport layer packets carrying PDU sets within QoS flows. Summary of the Invention
[0016] Generally, network devices can implement the techniques disclosed herein to support the use of, for example, specific PDU set QoS information to mark DSCP bits in the outer header of downlink packets of the PDU set for differentiated processing of transport packets carrying the PDU set within the QoS flow.
[0017] An example embodiment of the technology disclosed herein is a method implemented in a network function (NF) of a core network (CN). The method includes: receiving a set of rules for processing downlink Internet Protocol (IP) traffic carrying end-to-end (e2e) encrypted traffic; receiving IP packets associated with the IP traffic and metadata associated with the IP packets that includes one or more of the following: (i) Fast User Data Protocol (UDP) Internet Connection (QUIC) priority information, or (ii) a QUIC association identifier (ID) for a QUIC session; and performing Differentiated Service Code Point (DSCP) transport-level marking on packet data units (PDUs) including IP packets, based on the set of rules and the metadata, the PDU being associated with a set of PDUs.
[0018] Another example embodiment of these technologies is one or more apparatuses, including processing hardware and configured to implement the methods described above. Attached Figure Description
[0019] Figure 1 This is a block diagram of an example wireless communication system, such as 5GS, that uses the techniques of this disclosure to support directional PDU set processing;
[0020] Figure 2 This is a block diagram of an example protocol stack. Figure 1 The UE can communicate with the protocol stack. Figure 1 Communicate with the RAN;
[0021] Figure 3 It is a service-based 5GS architecture representation, including the overall non-roaming reference architecture of the 5GS policy and charging control framework;
[0022] Figure 4 It is a reference-point-based 5GS architecture representation, including the overall non-roaming reference architecture of 5GS policy and charging control framework;
[0023] Figure 6 This is a high-level messaging diagram for an example scenario where the UE uses XRM services that utilize PDU sets for processing.
[0024] Figure 7 This is a diagram of transport layer packets with RTP packets from the application server to the 5G network;
[0025] Figure 8 shows an example of e2e encrypted XRM traffic that uses the QUIC transport layer protocol to make a QUIC payload contain an RTP packet.
[0026] Figure 9 This is an example method in the Policy Control Function (PCF) for generating policy and charging control (PCC) rules for handling e2e encrypted traffic;
[0027] Figure 10 It is used for configuration in the Session Management Function (SMF) Figure 9 An example method for differentiated transport-level processing of traffic;
[0028] Figure 11 It is used in User Face Functions (UPF) Figure 9 An example method for differentiated transport-level processing of traffic;
[0029] Figure 12 This is a message passing diagram for an example scenario where the core network (CN) of a cellular communication system uses the Fast User Data Protocol (UDP) Internet Connection (QUIC) transport layer protocol to provide QoS provisioning for downlink e2e encrypted XRM traffic.
[0030] Figure 13 This is a message passing diagram for an example scenario. In this example scenario, the PCF receives the associated QUIC session ID (CQS-ID) and the priority of the QUIC session from the application function (AF), and the SMF generates a mapping list of priorities and DSCP values.
[0031] Figure 14 This is a message passing diagram for an example scenario. In this example scenario, the PCF receives the CQS-ID and the priority of the QUIC session from the AF, and the SMF generates a mapping list of CQS-ID and DSCP values.
[0032] Figure 15 This is a message passing diagram for an example scenario where the PCF receives an indication of the CQS-ID and transport level tag from the AF, and the SMF generates DSCP auxiliary information with the indication of the transport level tag.
[0033] Figure 16 This is a message passing diagram for an example scenario where the PCF receives an indication of the CQS-ID and transport level tag from the AF, and the SMF generates DSCP auxiliary information with an indication of the transport level tag set to an inactive value and the DSCP value of the mapped CQS-ID.
[0034] Figure 17This is a message passing diagram for an example scenario where the PCF receives the CQS-ID and the priority of the QUIC session from the AF, and the SMF generates DSCP auxiliary information with a transport level marker ground indication set to an inactive value and the DSCP value of the mapped CQS-ID or the mapped priority of the QUIC session.
[0035] Figure 18 This is a message passing diagram for an example scenario. In this example scenario, the PCF receives the CQS-ID and the priority of the QUIC session from the AF, the SMF generates a mapping between the priority and the DSCP value, and the UPF generates a UDP datagram with an HTTP datagram containing metadata with the CQS-ID and a QUIC packet.
[0036] Figures 19A to 19C This is a block diagram of example UDP datagrams encapsulated in different corresponding formats for HTTP datagrams; and
[0037] Figure 20 This is a flowchart of an example method in the network function (NF) of the core network. Detailed Implementation
[0038] As discussed below, to support PDU set identification for e2e encrypted traffic, one or more network functions (NFs) in the core network establish an N6 UDP tunnel between the UPF (operating as an HTTP client) and the application server (AS). This N6 UDP tunnel has a common-bit UDP proxy for HTTP. The UDP proxy can convert received HTTP datagrams into UDP packets and vice versa, until the network closes the UDP tunnel. In this way, HTTP datagrams effectively support in-band communication for providing metadata with PDU set information and corresponding QUIC packets between the 5GS and the AS.
[0039] As used herein, the term "fully encrypted media stream" refers to a media stream in which both the media header and media payload are encrypted end-to-end. The fully encrypted header and payload are not visible in the network. Examples include QUIC-based RTP (RoQ) and QUIC-based Media (MoQ) (draft-ietf-moq-transport). Partially encrypted media streams: Media streams in which some media headers (e.g., the basic header) are not encrypted. Other media headers (e.g., extended headers) and the media payload are encrypted end-to-end. The end-to-end encrypted payload and header are not visible in the network. Examples include SRTP (RFC 3711) (RFC 6904, RTP cryptex (RFC9335)) with partially encrypted header extensions.
[0040] DSCP marking can be performed in IP packet headers based on PDU set importance (PSI) information included in the media packet header (e.g., the RTP extension header as defined in TS26.522). This solution assumes that the media packet header information necessary for PDU set identification is not encrypted, and that the PSA UPF can identify the PDU set and use the PDU set information to perform GTP-U header marking.
[0041] Considering that the media packet header information (such as RTP extension headers) necessary for PDU set identification is partially or fully encrypted in end-to-end encrypted traffic, a mechanism can be implemented that enables applications to provide DSCP auxiliary information to 5GC to assign DSCP values to media streams using metadata indicated in the UDP options of the corresponding QUIC packets based on XRM traffic, where both metadata and QUIC packets are encapsulated in UDP datagrams.
[0042] For PDU set identification of end-to-end encrypted traffic, an N6 UDP tunnel can be established between the PSA UPF (acting as an HTTP client) and the application server (AS). This N6 UDP tunnel has a common-bit UDP proxy for HTTP. The UDP proxy can convert received HTTP datagrams into UDP packets and vice versa, until the UDP tunnel is closed. Therefore, HTTP datagrams are used for in-band communication to provide metadata with PDU set information and corresponding QUIC packets between the 5GS and the AS.
[0043] Example system and protocol stack
[0044] First refer to Figure 1 The example wireless communication system 100 may implement one or more of the techniques disclosed herein for supporting user handling of traffic, particularly uplink traffic from a UE. The example wireless communication system 100 includes UEs 102A and 102B, base station (BS) 104, base station 106, and a core network (CN) 110, such as a fifth-generation (5G) core (5GC). Base stations 104 and 106 may operate in a RAN 105 connected to CN 110. CN 110 may also be implemented as a sixth-generation (6G) core or another suitable core network.
[0045] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, then cell 124 is an NR cell. If base station 124 is an ng-eNB, then cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, then cell 126 is an NR cell, and if base station 126 is an ng-eNB, then cell 126 is an E-UTRA cell. Cells 124 and 126 can be located in the same Radio Access Network Notification Area (RNA) or in different RNAs. Cells 124 and 126 can partially overlap, allowing UE 102A or 102B to select, reselect, or switch from one cell to the other. Generally, RAN 105 can include any number of base stations, and each base station can cover one, two, three, or any other suitable number of cells. UE 102 can at least support a 5G NR (or simply "NR") air interface to communicate with base stations 104 and 106. Each of base stations 104 and 106 can be connected to CN 110 via an interface (e.g., an S1 or NG interface). Base stations 104 and 106 can also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).
[0046] The following text is for reference only. Figure 3 and Figure 4 This section discusses several NFs that constitute CN 110. One or more of the NFs of CN 110 implement the user consent checking technology discussed below for UE102A and / or UE102B.
[0047] Although not in order to avoid clutter Figure 1 As shown, CN 110 may include processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable storage medium storing instructions executed by the one or more general-purpose processors. Alternatively, the processing hardware may include dedicated processing units. The processing hardware may be configured to implement the techniques of this disclosure to achieve 5GS support for advanced media services.
[0048] Base station 104 is equipped with processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable storage (not shown) storing instructions executed by the one or more general-purpose processors. Alternatively, the processing hardware may include dedicated processing units.
[0049] UE 102A is equipped with processing hardware 130A, which may include one or more general-purpose processors such as a CPU, and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or dedicated processing units. UE 102A also includes a transceiver 132A for communicating with RAN 105 via a radio interface. Further, UE 102A includes memory 134A storing a PDU controller 140A. UE 102B may have a similar implementation. Furthermore, UE 102A can also execute various applications (not shown), to which the PDU controller 140A provides downlink data, and the PDU set controller 140A efficiently receives uplink data from these applications and forwards the uplink data to CN 110 via RAN 105.
[0050] CN 110 can connect to various services, including a data server (not shown) that transmits and receives PDUs from UEs 102A and 102B, and a third-party application 150 that can request information specifically related to UEs 102A and 102B, or a group of UEs including UEs 102A and 102B, subject to privacy controls. CN 110 implements one or more user privacy protection techniques, discussed in more detail below, to determine whether to provide the requested information to the third-party application 150. Further, in some cases, the request for information related to UE privacy originates within CN 110, i.e., from an AF operating within CN 110.
[0051] Figure 2 An example protocol stack 200 is illustrated in a simplified manner. UE 102A or 102B can communicate with an eNB / ng-eNB 230 or gNB 232 (e.g., one or more of base stations 104, 106) based on this example protocol stack. In example stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRA MAC sublayer 204A, which in turn provides a logical channel to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A provides an RLC channel to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides data delivery services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can then be adapted to the Service Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer. Figure 2 (Not shown in the image) provides data transfer services. In some implementations, UE 102A or 102B supports both EUTRA and NR stacks, such as... Figure 2 As shown, this is to support handover between EUTRA and NR base stations and / or support DCs via EUTRA and NR interfaces. Further, as... Figure 2 As shown, UE 102A or 102B can support the layering of NRPDCP 210 on EUTRA RLC 206A, and the layering of SDAP sublayer 212 on NR PDCP sublayer 210.
[0052] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 receive packets that may be referred to as Service Data Units (SDUs) (e.g., from Internet Protocol (IP) layers that are directly or indirectly layered on PDCP layers 208 or 210), and output packets that may be referred to as Protocol Data Units (PDUs) (e.g., to RLC layers 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as “packets”, except where the difference between SDUs and PDUs is relevant.
[0053] On the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide signaling radio bearer (SRB) or RRC sublayer ( Figure 2 (Not shown) to exchange, for example, RRC messages or Non-Access Stratum (NAS) messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide data radio bearers (DRBs) to support data exchange. The data exchanged on NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.
[0054] Example network architecture
[0055] The techniques discussed below can be used in Figure 1 Systems and / or Figure 3 and Figure 4 Implemented in the core network.
[0056] Figure 3 yes Figure 1The system can implement a service-based example CN architecture representation 300. In representation 300, the overall non-roaming reference architecture of the 5GS Policy and Charging Control (PCC) framework includes components shown using solid lines, and other components shown using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. Components outside the PCC framework include Network Slice Selection Function (NSSF) 302, Network Repository Function (NRF) 306, Unified Data Management (UDM) 308, Edge Application Server Discovery Function (EASDF) 310, Network Slice Specific Authentication and Authorization Function (NSAAF) 312, Authentication Server Function (AUSF) 314, Service Communication Broker (SCP) 316, and Network Slice Admission Control Function (NSACF) 318. The non-PCC architecture further includes UE 102, RAN 105, and Data Network (DN) 330.
[0057] The PCC framework in Architecture 300 includes Unified Data Repository (UDR) 352, Network Open Function (NEF) 354, Network Data Analysis Function (NWDAF) 356, Application Function (AF) 358, Policy Control Function (PCF) 360, Charging Function (CHF) 362, Access and Mobility Management Function (AMF) 364, Session Management Function (SMF) 366, and User Plane Function (UPF) 370.
[0058] In the discussion below, the PDU Session Anchor User Plane Function (PSA UPF) may be referred to simply as UPF. However, it should be understood that UPF 370 is not necessarily the only instance of UPF, nor is it limited to PSA UPF functionality.
[0059] In some deployments, AF 358 operates either within or outside of trusted domain 311 (i.e., in a non-trusted domain). Trusted domain 311 is typically located within CN 110 and includes components such as UDM 308, UDR 352, PCF 360, AMF 364, SMF 366, and UPF 370. Generally, AFs operating outside trusted domain 311 can only access CN110's network functions via NEF 354, while AFs operating within trusted domain 311 can directly access at least some of CN 110's network functions, or in some deployments, can access these functions via NEF 354.
[0060] Figure A-4 is a 5GS architecture representation based on a reference point 400. In Figure A-4, the non-roaming reference architecture of the 5GS PCC frame is shown as blocks and connections with solid lines, while components and connections outside the PCC frame are shown with dashed lines.
[0061] For clarity, Figure 5 This illustrates an advanced scenario where UE 102A or 102B obtains data services. During the registration process, the AMF determines whether UE 102 is authorized to use data services based on the UE's service capabilities and the service authorization included in the subscription data received from UDM 308 (e.g., as specified in Clause 5.7 of TS 23.501). After successful registration, UE 102A or 102B performs a PDU session establishment procedure (e.g., as described in Clause 4.3.2.2 of TS 23.502). UE 102A or 102B or the network may initiate a PDU session modification procedure (e.g., as described in Clauses 4.3.3.2 and 4.3.3.3 of TS 23.502) for an existing PDU session. UE 102A or 102B may repeat procedure 530 for multiple PDU sessions associated with the same or different DNNs and S-NSSAIs.
[0062] Example structure of a PDU encapsulating a UDP payload
[0063] like Figure 6 As shown, a UPF such as UPF 370 can generate a transport layer packet 650 based on an IP packet 601 received from AS 331. This transport layer packet can be a PDU within a specific QoS flow. The IP packet 601 includes an IP header 610 and a UDP datagram—including a UDP header 612 and a UDP payload 615, but excluding UDP options fields. The UDP payload 614 includes an RTP packet 640 associated with an RTP session 605. The RTP packet 640 includes an RTP header 641 and an RTP payload 642, such as an I / P / B frame 610. According to... Figure 6 The method allows UPF to generate IP packet 601A based on RTP packet 640, and generate an outer IP header 652 and a GTP-U header 653 of transport layer packet 650 to encapsulate the inner IP packet 601B corresponding to IP packet 601A. Figure 6 In this scenario, the UDP payload 614 can be unencrypted, and the UPF can generate the outer IP header 652 and GTP-U header 653 based on the UDP payload 614 (e.g., using the RTP header 641).
[0064] Figure 7An example layer of the UDP-based QUIC protocol is shown, which application servers and CNs can support for handling PDU-based sets of end-to-end encrypted traffic. IP packet 701 includes an IP header 710 and a UDP datagram, which in turn includes a UDP header 712, a UDP payload 714, and UDP options 716. The UDP payload 714 can encapsulate the QUIC packet. In the example implementation, UDP option 714 includes metadata with the necessary RTP session information for mapping to a QUIC stream. UPF 370 can use UDP option 716 for PDU-based set identification.
[0065] The UDP payload 714 may include QUIC packets 722 of a QUIC stream 720 with a specific QUIC connection. The RTP session 702 in this example includes a single QUIC stream 720. The QUIC packet 722 includes a QUIC header 730 and a QUIC payload 732, which encapsulates one or more RTP packets sharing the same RTP attributes (e.g., I / P / B media frame type). Figure 7 In the example, QUIC payload 732 includes a single RPT packet, which includes an RTP header and an RTP payload.
[0066] According to method 800 shown in Figure 8, when downlink encrypted XRM traffic is transmitted from AS 331, UPF 370 can use the metadata included in IP packet 801 to differentiate PDUs. For example, UPF 370 can detect IP flows with encrypted XRM traffic and identify PDUs in the PDU set based on: (i) unencrypted metadata in the UDP option field of IP packet 1001 for the corresponding QUIC packet on the user plane, and (ii) downlink XRM traffic information on the control plane. UPF 370 can receive downlink XRM traffic information from SMF 366 as part of an N4 session configuration that may include Packet Detection Rules (PDR), Forwarding Action Rules (FAR), and QoS Enforcement Rules (QER).
[0067] Then, the UPF 370 can set the DSCP bit in the outer IP header 852 of PDU 1051 in the identified PDU set for transport-level marking. Therefore, PDU 1051 is a transport layer packet. The UPF 370 can use DSCP auxiliary information to determine the DSCP bit, which can be included in the N4 session configuration. The IP payload of IP packet 1001 can encapsulate QUIC packets with downlink XRM traffic.
[0068] Furthermore, the UPF 370 can perform PDU set-based processing by: (i) identifying PDUs in the PDU set based on the RTP extended header (when the IP payload of IP packet 801 is not encrypted) or based on unencrypted metadata included in the UDP options (regardless of whether the IP payload of IP packet 801 is encrypted); and (ii) marking in the GTP-U header using one or both of the following: (1) PDU set information for the identified PDUs associated with a particular PDU set, or (2) metadata within the UDP options indicating the priority or other information of the QUIC session for partially or fully encrypted XRM traffic. When XRM traffic is unencrypted, the UPF 370 can obtain PDU set information from the RTP extended header. When XRM traffic is encrypted, the UPF 370 can obtain PDU set information from the UDP options field.
[0069] Example technologies for supporting differentiated processing of e2e encrypted traffic
[0070] Figures 9 to 11 Several example methods are shown in the core network for enabling PDU set-based processing of PDU set identification and labeling, as well as differentiated processing of transported downlink e2e encrypted XRM traffic. Generally, Figures 9 to 18 and Figure 20 Similar events in the diagram are labeled with similar reference numerals that share two least significant figures, where differences are discussed where appropriate. For example, event 1339 is similar to events 1439 and 1539, event 1339 is similar to event 1439, and box 2039, etc.
[0071] Figure 9 Example method 900 is provided, which a PCF such as PCF 360 can implement to generate rules for handling e2e encrypted traffic. At box 910, the PCF receives an AF request message from an AF such as AF 358, which requests QoS configuration for e2e encrypted XRM traffic. The AF request message may include auxiliary information for handling downlink e2e encrypted XRM traffic to support (i) PDU-based handling of downlink e2e encrypted XRM traffic, and (ii) differentiated handling when transmitting downlink e2e encrypted XRM traffic.
[0072] At box 921, the PCF generates PCC rules containing auxiliary information for handling downlink e2e encrypted XRM traffic. To this end, the PCF enables PDU-based handling of downlink e2e encrypted XRM traffic based on the auxiliary information. For example, the auxiliary information may include QoS requirements containing PDU-based parameters. The PCF further enables differentiated handling of transported downlink e2e encrypted XRM traffic based on the auxiliary information (such as indications of differentiated handling of transports or priority of QUIC sessions). At box 926, the PCF provides the PCC rules to an SMF such as SMF 366.
[0073] Figure 10 This is example method 100, which an SMF (such as SMF 366) can implement to configure differentiated transport-level handling of downlink e2e encrypted XRM traffic. At box 1026, the SMF receives PCC rules, which are configured by the PCF based on auxiliary information of the downlink XRM traffic received from the AF, as referenced above. Figure 9 The following is discussed. Next, at box 1031, the SMF performs QoS binding for the PCC rules. At box 1032, the SMF determines to enable differentiated transport-level handling across one or more QoS flows for downlink XRM traffic in the 5GC. To this end, the SMF determines DSCP auxiliary information. At box 1039, the SMF provides N4 rules (PDR, FAR, QER) to the UPF and intermediate UPF via the N4 interface.
[0074] Next, Figure 11 Example method 100 is shown, which can be implemented by a PSA UPF (or simply UPF) (such as UPF 370) to support differentiated transport-level handling of downlink e2e encrypted XRM traffic.
[0075] At box 1139, the UPF receives N4 rules from the SMF. As described above, N4 rules may include PDR, FAR, and QER for downlink XRM traffic. At box 1131, the UPF enables PDU set-based processing of PDU set identifiers and tags for e2e encrypted XRM traffic. Specifically, at box 1132, the UPF can operate as an HTTP client to establish a UDP tunnel with an AS (e.g., AS331) as a cobit UDP proxy for HTTP, which can convert received HTTP datagrams into UDP packets and vice versa. At box 1160, the UPF can receive HTTP datagrams containing metadata and corresponding e2e QUIC packets from the AS. Next, at box 1180, based on the N4 rule and the HTTP datagram including metadata and QUIC packets associated with e2e encrypted XRM traffic, the UPF can (i) perform PDU set identification by detecting IP flows with encrypted XRM traffic and identifying PDUs based on the PDU set, and (ii) perform GTP-U marking on the identified PDUs belonging to the PDU set.
[0076] At boxes 1190 and 1163, the UPF can enable differentiated handling of transport downlink e2e encrypted XRM traffic. Specifically, at box 1190, the UPF can perform DSCP bit marking in the outer IP header of the identified PDU belonging to the PDU set, using transport-level DSCP marking based on the N4 rule of DSCP auxiliary information, where, for example, an IP payload received from the AS encapsulates a UDP datagram with an HTTP datagram containing metadata and QUIC packets of downlink XRM traffic. At box 1163, the UPF forwards the IP packets encapsulated with QUIC packets to the RAN (e.g., RAN 105) for PDU set-based QoS handling.
[0077] refer to Figure 11 The metadata discussed may include, for example, a downlink CQS-ID (alternatively abbreviated as QUIC Session Association (QSC-ID)). XRM applications can generate this downlink CQS-ID as a variable-length or fixed-length hash value for each IP flow, QUIC connection (based on the QUIC connection ID), and QUIC flow (based on the QUIC flow ID) for privacy and security protection. The QSC-ID is unique to the XRM application, and a QUIC session can be associated with an IP flow having a QUIC connection, or with an IP flow having a QUIC flow within a QUIC connection.
[0078] Metadata may further include the priority of the QUIC session identified by the QSC-ID or an indication of differentiated handling of transports, as discussed in the example scenario below. Furthermore, metadata may include one or more of the following elements contained in the RTP extended header of the RTP packet (encapsulated in an encrypted QUIC packet): (i) the PDU set sequence number; (ii) an indication of the last PDU in the PDU set; (iii) the PDU sequence number within the PDU set; (iv) the PDU set size in bytes; or (v) the PDU set importance, which identifies the relative importance of the PDU set relative to other PDU sets within the QoS flow.
[0079] A QUIC session can be associated with an IP flow that has a QUIC connection, or with an IP flow that has a QUIC flow within a QUIC connection. For example, an XRM application can use different IP flows (represented by different IP 5-tuples) for different QUIC connections, and if each QUIC connection contains only one QUIC flow, then each QUIC session associated ID is generated for each IP flow. As another example, an XRM application can use the same IP flows (represented by some IP 5-tuples) for all QUIC connections, and if each QUIC connection contains only one QUIC flow, then each QUIC session associated ID is generated for each QUIC connection. As another example, an XRM application can use the same IP flows for all QUIC connections, and if each QUIC connection contains only one QUIC flow, then each QUIC session associated ID is generated for each QUIC connection. As another example, an XRM application can use different IP streams for different sets of QUIC connections. If each QUIC connection contains only one QUIC stream, then each QUIC session association ID is generated for each IP stream and QUIC connection. As yet another example, an XRM application can use different IP streams for different sets of QUIC connections. If each QUIC connection contains more than one QUIC stream, then each QUIC session association ID is generated for each IP stream, QUIC connection, and QUIC stream.
[0080] The above reference Figure 10 and Figure 11 The N4 rules under discussion may include PDR, FAR, and QER.
[0081] The PDR contains packet detection information having at least one of the following: (i) a QoS flow ID (QFID) assigned by SMF 366; (ii) a set of packet filters and a protocol description based on the IP header of the IP packet, such as as indicated in TS 23.501, and one or more additional DL QSC-IDs that may be associated with one or more components of the traffic description, such as IP flow, QUIC connection, and QUIC flow; and (iii) a protocol description indicating the use of a transport layer protocol (e.g., QUIC-based RTP (RoQ) or QUIC-based media) for downlink e2e encrypted XRM traffic, and the use of an N6 UDP tunnel for an HTTP datagram proxy with metadata and QUIC packets for the XRM traffic.
[0082] FAR may include indications of the use of an N6 UDP tunnel for HTTP datagrams and a fully qualified domain name (FQDN) for the AS, as well as DSCP auxiliary information, which may include: (i) a mapping list of priority values and DSCP values for QUIC sessions (option 1), (ii) a mapping list of QSC-IDs and DSCP values (option 2), or (iii) a specific DSCP value for a QUIC session identified by a specific QSC-ID (option 3).
[0083] QER may include: a PDU set information tag indicator that instructs UPF 370 to tag the GTP-U header for the identified PDU in the PDU set; and / or a DSCP tag indicator that instructs UPF to tag the outer IP header with DSCP bits for the identified PDU in the PDU set according to FAR. FAR may be based on PSI for unencrypted XRM traffic and / or metadata for e2e encrypted XRM traffic.
[0084] For example, the SMF 366 can be configured with N4 rules as follows. For the handling of PDU-based sets of downlink e2e encrypted XRM traffic, the SMF can generate a PDR that includes: (i) a packet filter with QSC-ID information, which the UPF can use to identify PDUs for the PDU-based set of encrypted XRM traffic in which the metadata contains the QSC-ID; (ii) a protocol description with information indicating the use of a transport layer protocol (e.g., QUIC-based RTP (RoQ) or QUIC-based media) for the downlink e2e encrypted XRM traffic, and an N6 UDP tunnel using a UDP proxy for HTTP datagrams containing the metadata and QUIC packets of the XRM traffic.
[0085] The SMF can determine the FAR, which includes indications of the N6 UDP tunnel used for HTTP datagrams and the FQDN used for the AS. Further, the SMF can determine the QER, which includes a PDU set information tag indicator that instructs the UPF to tag the GTP-U header of the PDUs identified in the PDU set.
[0086] For differentiated handling of transmitted downlink e2e encrypted XRM traffic, the SMF may (i) determine the QER and the FAR including the DSCP flag indicator based on the marking of the outer IP header with DSCP bits according to the FAR, to enable or disable differentiated handling of transmitted XRM traffic, and (ii) determine the FAR, which includes DSCP auxiliary information for encrypted XRM traffic.
[0087] For example, for differentiated handling of downlink e2e encrypted XRM traffic, when the UPF receives an N4 rule including DSCP auxiliary information from an SMF (in N4) message, the UPF can identify the corresponding QUIC session based on the QSC-ID matching the metadata of the XRM traffic, included in the extended packet filter set in the PDR. Based on the FAR with DSCP auxiliary information and the QER / FAR with DSCP tagging indicators, for a matching QSC-ID QUIC session based on the PDR, the UPF can tag the DSCP bit in the outer IP header of the identified PDU according to the DSCP value. This value corresponds to the priority value indicated in the metadata, based on the DSCP auxiliary information which has a mapping list of priority values and DSCP values for the QUIC session.
[0088] Example Scenario
[0089] Figure 12 This is the message passing diagram for example scenario 1200, in which CN 110 provides QoS configuration for downlink e2e encrypted XRM traffic. UE 102 performs a 1202 PDU session establishment procedure, which can be similar to the procedure described in clause 4.3.2.2.1 of TS 23.502. AF 358 receives auxiliary information from AS 331 to request QoS configuration for the e2e encrypted XRM traffic.
[0090] AF 358 sends a PDU session establishment message, which includes a set of PDUs with certain parameters. To this end, AF358 sends an Nnef_AFsessionWithQoS_Create request or Nnef_AFsessionWithQoS_Update request message to PCG 360 / NEF 354, providing the following information: (i) QoS requirements, which may include QoS parameters based on a PDU set for downlink XRM traffic; (ii) a traffic description indicating IP flow information (e.g., IP 5-tuples) for downlink XRM traffic, and an additional traffic description indicating a downlink QSC-ID; (iii) a protocol description indicating the transport layer protocol (e.g., QoQ or QUIC-based media) for downlink e2e encrypted XRM traffic, and an indication of using an N6UDP tunnel for an HTTP datagram with metadata and QUIC packets for the XRM traffic, wherein one or more context IDs may be provided for the HTTP datagram carrying specific content; and (iv) a priority value for the QUIC session identified by the QSC-ID.
[0091] Downlink QSC-IDs can be based on one or more components describing the traffic, such as IP flows (each IP flow is represented by an IP5 tuple), QUIC connections, and QUIC flows, for example, to be associated with specific QoS requirements of a QoS flow. QSC-IDs are unique within the XRM application. Different QUIC sessions can be associated with QUIC connections in different IP flows, different QUIC connections within a single IP flow, or different QUIC flows within a single QUIC connection in an IP flow.
[0092] PCF 360 determines that 1220 enables PDU-based processing of e2e encrypted XRM traffic and generates PCC rule 1221 based on information provided by AF and / or local policies (e.g., as described in Clause 6.1.3.27.4 of TS 23.503). PCF 360 uses SM policy association establish / modify messages to forward the PCC rule 1226 of the e2e encrypted XRM traffic to SMF366.
[0093] SMF 366 binds PCC rule 1231 to the QoS flow, determines the applicable QoS profile, and specifies the N4 rule as follows: (see reference above) Figure 11 The discussion focuses on the PDU-based processing and differentiation of downlink e2e encrypted XRM traffic. SMF 266 guideline 1232 UPF 370 and implementation 1233 are also referenced above. Figure 11The PDU-based processing discussed. Then, SMF 366 configures QoS profile 1240 for RAN 105 via AMF 364. SMF 366 also sends the QoS rules from NAS message 1241 to UE 102 via AMF 364 and RAN 105.
[0094] When initiating an e2e QUIC connection to AS 331, UE 102 sends a 1250 uplink packet to UPF 370 to enable end-to-end encryption of XRM traffic. Based on the FAR with indications of an N6 tunnel for using a UDP proxy for HTTP datagrams and an FQDN for AS 331, UPF 370 detects an uplink packet addressed to AS 331 by 1251, which has an address and port number matching the FAR for e2e encrypted XRM; requests 1251 to establish a UDP tunnel with the target AS 331 as a UDP proxy for HTTP / 3 sessions; and forwards the e2e QUIC connection establishment request to AS 331.
[0095] AS 331 determines that 1252 uses HTTP datagrams with a capsule protocol to send the metadata and corresponding QUIC packets for the XRM traffic. AS 331 then sends 1260 IP packets encapsulating UDP datagrams containing HTTP datagrams with the XRM traffic metadata and QUIC packets. In some implementations, AS 331 may, for example, use one of the options considered in the discussion of metadata above to encapsulate the metadata and QUIC packets within the same UDP datagram.
[0096] Based on metadata and QUIC packet information obtained from the encapsulated UDP datagram, the UPF 370 can perform 1280 PDU set identification based on the PDR and PDU set information in the metadata, and mark it using the PDU set information in the GTP-U header. The UPF 370 can further perform 1290 outer IP header DSCP bit marking based on the PDR and FAR, and perform 1290 QoS implementation based on QER.
[0097] The UPF 370 forwards 1263 (XRM) IP packets over the transport network, and the router transmits IP packets with traffic differentiation based on DSCP bits. Then, the RAN 105 sends 1270 XRM packets to the UE 102 based on QoS handling based on the downlink PDU set and on the QoS parameters based on the PDU set in the GTP-U header and QoS profile.
[0098] Next, Figures 13 to 18 Several example implementations of differentiated processing of encrypted XRM traffic transmitted downlink are shown.
[0099] first, Figure 13 Example scenario 300 is illustrated. AF 358 sends an AF request message 1311 to PCF 360 / NEF 354, which includes the CQS-ID and the priority of the QUIC session. PCF 360 generates a PCC rule based on the information included in the received AF request message 1311 and sends the PCC rule 1326 to SMF 366. SMF 366 enables 1331 differentiated handling of encrypted XRM traffic transmitted downlink. SMF 366 further generates 1332 a priority and DSCP value mapping list based on operator policies, SMF configuration of DSCP values, and priority values of all QUIC sessions applying XRM. SMF 366 also generates 1337 an N4 rule with DSCP auxiliary information, which includes the priority and DSCP value mapping list.
[0100] SMF 366 provides UPF 370 with rule 1339 N4. AS 331 sends IP packets encapsulated in 1361 UDP datagrams, which contain HTTP datagrams with metadata (including CQS-ID and priority of the QUIC session) and QUIC packets for downlink XRM traffic. Based on DSCP auxiliary information, including a mapping list of priority and DSCP values, UPF 370 identifies 1381 PDUs based on the CQS-ID in the metadata and obtains the DSCP value of the mapped priority value of the QUIC session indicated in the 1381 metadata. UPF 370 marks the 1391 DSCP bit in the outer IP header based on the obtained DSCP value.
[0101] Figure 14 This is the message passing diagram for example scenario 1400. This scenario is generally similar to... Figure 13 The differences will be discussed below. Events 1411, 1426, 1431, and 1439 are similar to events 1311, 1326, 1331, and 1339 discussed above, respectively. However, here, the SMF generates a mapping list of CQS-ID and DSCP values for 1433 based on the operator's policy, the SMF configuration of the DSCP value, and the priority values of all QUIC sessions applied by the XRM. Then, SMF 366 generates N4 rule 1437 with DSCP auxiliary information, which includes the mapping list of CQS-ID and DSCP values.
[0102] AS 331 sends an IP packet containing a 1462-byte encapsulated UDP datagram with an HTTP datagram containing metadata (CQS-ID) for downlink XRM traffic and a QUIC packet. Based on DSCP auxiliary information (a mapping list of CQS-ID and DSCP values), UPF 370 identifies the 1482-byte PDU based on the CQS-ID in the metadata and obtains the DSCP value of the mapped CQS-ID for the QUIC session indicated in the 1482-byte metadata. UPF 370 then marks the 1491-byte DSCP bit in the outer IP header based on the obtained DSCP value.
[0103] Figure 15 Example scenario 1500 is shown, which is generally similar to... Figure 13 or Figure 14 In this scenario, let's consider the differences. Events 1526, 1531, 1539, and 1563 are similar to events 1326 / 1426, 1331 / 1431, 1339 / 1439, and 1463 discussed above, respectively.
[0104] AF 358 sends an AF request message (1512) to PCF 360 / NEF 354, which includes an indication of the CQS-ID and transport level tag. PCF 360, based on the information received in AF request message 1512, generates a PCC rule and sends it (1526) to SMF 366. SMF 366 generates an N4 rule (1538) with DSCP auxiliary information, including an indication of the transport level tag. SMF 366 and UPF 370 identify PDU 1583 based on the metadata and the N4 rule, using the CQS-ID from the metadata. Based on the DSCP auxiliary information (indication of transport level markers) and the priority of the QUIC session receiving 1563 in the metadata, the UPF 370 reports the priority of the QUIC session in the 1583 metadata to the SMF 366 for generating a priority-to-DSCP value mapping list based on operator policies, SMF configuration of DSCP values, and priority values of all QUIC sessions applied by XRM. The SMF 366 and UPF 370 further obtain the 1583 DSCP auxiliary information, which includes an indication of a transport level marker set to "inactive" and the DSCP value of the mapped priority of the QUIC session.
[0105] Based on the obtained DSCP value, the UPF 370 uses a DSCP value of 1583 obtained from the SMF 366 to mark 1592 DSCP bits in the outer IP header. When the transport level marking indicator is set to "inactive," the UPF 370 uses the same DSCP value for the outer IP header of IP packets for QUIC sessions.
[0106] Figure 16 This is the message passing diagram for example scenario 1600, which is generally similar to... Figure 15 Examples of these scenarios are presented below, with differences considered below. Events 1612, 1626, 1631, 1639, 1661, and 1692 are similar to events 1512, 1526, 1531, 1539, 1561, and 1592 discussed above, respectively.
[0107] Here, based on metadata and N4 rules, UPF 370 and SMF 366 perform the following operations: (i) identify the PDU in the PDU set based on the CQS-ID in the metadata; (ii) report the priority of the QUIC session in the metadata to SMF 366 based on the DSCP auxiliary information, including the indication of the transport level tag and the priority of the QUIC session received in the metadata, for generating a mapping list of CQS-ID and DSCP values based on the operator policy, the SMF configuration of the DSCP value, and the priority values of all QUIC sessions applied by XRM; and (iii) obtain the DSCP auxiliary information, which includes the indication of the transport level tag set to "inactive" and the DSCP value of the mapped CQS-ID.
[0108] Figure 17 This is the message passing diagram for example scenario 1700, which is generally similar to... Figures 13 to 16In this scenario, let's consider the differences. Events 1711, 1726, 1731, 1739, and 1762 are similar to events 1311, 1526, 1531, 1539, and 1462 discussed above, respectively. Here, UPF 370 and SMF 366 perform the following operations based on metadata and N4 rules: (i) identifying the PDU based on the CQS-ID in the metadata; (ii) reporting the CQS-ID and QUIC session priority in the metadata to SMF 366 based on DSCP auxiliary information including an indication of the transport level tag and the priority of the received QUIC session in the metadata, for generating a mapping list of CQS-ID and DSCP values or a mapping list of priority and DSCP values based on operator policies, SMF configuration of DSCP values, and priority values of all QUIC sessions applied by XRM; and (iii) obtaining DSCP auxiliary information including an indication of a transport level tag set to "inactive", the DSCP value of the mapped CQS-ID, or the DSCP value of the mapped priority of the QUIC session.
[0109] The UPF 370 marks 1794 DSCP bits in the outer IP header based on the obtained DSCP value. When the transport level marking indicator is set to "inactive," the UPF 370 uses the same DSCP value for the outer IP header of IP packets for QUIC sessions.
[0110] Figure 18 This is the message passing diagram for example scenario 1800, which is generally similar to... Figures 13 to 16 In this scenario, let's consider the differences. SMF 366 generates a mapping list of 1835 priorities and DSCP values based on operator policies, SMF configuration of DSCP values, and priority values of all QUIC sessions for XRM applications. SMF 366 generates an N4 rule (1839) with DSCP auxiliary information, including the DSCP value, in the FAR. AS 331 sends an IP packet (1862) encapsulating a UDP datagram containing an HTTP datagram with metadata (CQS-ID) and QUIC packets for downlink XRM traffic. Based on the DSCP auxiliary information including the DSCP value, UPF 370 identifies the 1895 PDU based on the CQS-ID in the metadata and marks the 1895 DSCP bit in the outer IP header of the identified PDU based on the DSCP value obtained from the FAR.
[0111] Now for reference Figures 19A to 19CThe technology for delivering metadata and corresponding QUIC packets for e2e encrypted XRM traffic, for example using RTP or other media transport protocols, can be based on a QUIC-aware UDP proxy for HTTP datagrams, wherein AS 331 can encapsulate HTTP datagrams in UDP datagrams 1914A, 1914B, or 1914C to carry different payloads identified by a specific context ID, and can be designed with a dedicated capsule protocol for delivering metadata and corresponding e2e encrypted QUIC packets in the following options.
[0112] exist Figures 19A to 19C In the example, metadata may include the information discussed above (QSC-ID, QUIC session priority, PDU set information, etc.).
[0113] According to the reference Figures 19A to 19C The first method discussed is AS 331, which generates HTTP datagrams with the capsule protocol. This method can, for example, be used with... Figure 13 , Figure 15 or Figure 16 The technology combination. In particular, based on the QUIC-aware UDP proxy for HTTP datagrams, AS 331 can encapsulate HTTP datagrams in UDP datagrams and can support the capsule protocol, which is used to deliver metadata and corresponding e2e encrypted QUIC packets in the following options.
[0114] according to Figure 19A As shown in option (a), a UDP datagram encapsulates an HTTP datagram 1923 and a QUIC packet 1922. According to option a.1, AS 331 reuses existing capsule-type QUIC datagrams, and PDU set information is included in the encrypted QUIC datagram. The application-specific CQS-ID and the priority of the QUIC session can be included as part of the PDU set information contained in the RTP extension header of the RTP packet encapsulated in the encrypted QUIC packet. The HTTP header of the HTTP datagram may include the following information: Context ID: 0x00, which is defined in IETF RFC 9297 and registered with IANA.
[0115] According to option a.2, AS 331 uses a new (dedicated, private) context ID for capsule-type QUIC datagrams in HTTP datagrams, where PDU set information is included in the encrypted QUIC datagram, and the HTTP header of the HTTP datagram may include the following information: (i) Context ID: a new (dedicated, private) ID for the HTTP datagram containing information identifying the PDU set for e2e encrypted XRM traffic and PDU set information; (ii) CQS-ID for PDU set identification; and (iii) the priority of the QUIC session within the application.
[0116] according to Figure 19B Option B, as shown, encapsulates two HTTP datagrams in UDP datagram 1914B: an HTTP datagram 1925 with a new (dedicated, private) capsule type for QUIC datagrams containing PDU set information; and an HTTP datagram 1926 with a capsule type set to 0x00 for QUIC datagrams containing XRM payloads.
[0117] The HTTP header of the first HTTP datagram 1925 may include the following information: a context ID, which may be a new (proprietary, dedicated) ID for the HTTP datagram containing information identifying the PDU set for e2e encrypted XRM traffic; a CQS-ID; and the priority of the QUIC session within the application. The HTTP header of the second QUIC datagram 1926 may include the following information: a context ID: 0x00, which is defined in IETF RFC 9297 and registered with IANA.
[0118] according to Figure 19C Option C shown: UDP datagram 1914C encapsulates a single HTTP datagram 1927. This single HTTP datagram has a new capsule protocol for encapsulating two QUIC datagrams, including: a first QUIC datagram containing PDU set information, and a second QUIC datagram containing an XRM payload. The HTTP header of the HTTP datagram may include the following information: Context ID: a new ID for the HTTP datagram containing information for PDU set identification and QUIC packets for e2e encrypted XRM traffic; CQS-ID; and the priority of the QUIC session within the application.
[0119] Another method can be, for example, with Figure 14 and Figure 17The method is based on a QUIC-aware UDP proxy for HTTP datagrams. AS 331 can encapsulate HTTP datagrams within UDP datagrams and can be designed with a new capsule protocol for delivering metadata and corresponding e2e encrypted QUIC packets in the following options.
[0120] According to option A (see...) Figure 19A C) A UDP datagram encapsulates an HTTP datagram and a QUIC packet. Specifically, according to option a.1, AS 331 reuses existing capsule-type QUIC datagrams, and PDU set information is included in the encrypted QUIC datagram. The associated QUIC session ID (CQS-ID) may be included as part of the PDU set information contained in the RTP extension header of the RTP packet encapsulated in the encrypted QUIC packet. The HTTP header of the HTTP datagram may include the following information: Context ID: 0x00, which is defined in IETF RFC 9297 and registered with IANA.
[0121] According to option a.2, AS 331 uses a new context ID for capsule-type QUIC datagrams in HTTP datagrams, where PDU set information is included in the encrypted QUIC datagram, and the HTTP header of the HTTP datagram may include the following information: Context ID: a new (private, exclusive) ID for the HTTP datagram containing information for PDU set identification and PDU set information for e2e encrypted XRM traffic; and a CQS-ID for PDU set identification.
[0122] According to option B (see...) Figure 19B The UDP datagram encapsulates two HTTP datagrams: one with a new capsule type for QUIC datagrams containing PDU set information, and the other with a capsule type set to 0x00 for QUIC datagrams containing XRM payloads. The HTTP header of the first HTTP datagram may include: a context ID, which may be a new (private, exclusive) ID for the HTTP datagram containing information for identifying the PDU set for e2e encrypted XRM traffic; and a CQS-ID.
[0123] The HTTP header of the second QUIC datagram may include the following information: Context ID: 0x00, which is defined in IETF RFC 9297 and registered with IANA.
[0124] According to option C (see...) Figure 19C A UDP datagram encapsulates an HTTP datagram. This HTTP datagram has a new (dedicated, proprietary) capsule protocol for encapsulating two QUIC datagrams: a first QUIC datagram containing PDU set information and a second QUIC datagram containing an XRM payload. The HTTP header of the HTTP datagram may include the following information: Context ID: a new ID for the HTTP datagram containing information for PDU set identification and QUIC packets for e2e encrypted XRM traffic; and CQS-ID.
[0125] Figure 20 This is a flowchart of example method 2000 in an NF (e.g., UPF 370) of a core network such as CN 110. At box 2039, the NF receives a set of rules for processing downlink IP traffic carrying e2e encrypted traffic. At box 2060, the NF receives IP packets associated with the IP traffic and metadata associated with the IP packets that includes one or more of the following: (i) QUIC priority information or (ii) the QSC-ID (or CQS-ID) of the QUIC session. At box 2090, based on the rule set and metadata, the NF performs Differentiated Service Code Point (DSCP) transport-level marking on packet data units (PDUs) including IP packets, associated with a set of PDUs.
[0126] The following descriptions can be applied to the descriptions above.
[0127] User devices (e.g., UE 102) that can implement the technologies disclosed herein can be any suitable device capable of wireless communication, such as smartphones, tablet computers, laptop computers, mobile game consoles, point-of-sale (POS) terminals, health monitoring devices, drones, cameras, media streaming dongles or other personal media devices, wearable devices (such as smartwatches), wireless hotspots, femtocells, or broadband routers. Furthermore, in some cases, the user device can be embedded in electronic systems such as the main unit of a vehicle or an advanced driver assistance system (ADAS). Additionally, the user device can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.
[0128] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in a certain way. A hardware module may include a dedicated circuit system or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or a circuit system (e.g., included within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., by software configuration) may be driven by cost and time considerations.
[0129] As used herein, the term “or” should be interpreted as inclusive, or means any one or any combination thereof, unless otherwise expressly indicated, mutually exclusive, or indicated by the context. Thus, in this document, expressing “A or B” means “A, B, or both A and B”.
[0130] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. The software can be executed by one or more general-purpose processors or one or more dedicated processors.
Claims
1. A method in the network function (NF) of a core network (CN), the method comprising: Receive a set of rules for processing downlink Internet Protocol IP traffic carrying end-to-end e2e encrypted traffic; Receive IP packets associated with the IP traffic and metadata associated with the IP packets that includes one or more of the following: (i) Fast User Data Protocol (UDP) Internet Connection QUIC priority information, or (ii) QUIC association identifier ID of the QUIC session; as well as Based on the rule set and the metadata, Differentiated Service Code Point (DSCP) transport-level marking is performed on Packet Data Units (PDUs) including the IP packets, the PDUs being associated with a set of PDUs.
2. The method of claim 1, further comprising: The priority of the QUIC session is determined based on the associated ID.
3. The method as described in claim 1 or 2, wherein: The associated ID corresponds to a single Internet Protocol (IP) stream.
4. The method as described in claim 1 or 3, wherein: The associated ID is unique for Extended Reality and Media Services (XRM) applications.
5. The method as described in any of the preceding claims, wherein: The rule set includes group detection rules (PDR) with QUIC association IDs.
6. The method as described in any of the preceding claims, wherein: The rule set includes forwarding action rules (FARs) with DSCP auxiliary information, which includes a mapping between priority and DSCP value.
7. The method of claim 6, wherein, The DSCP auxiliary information includes one of the following: (i) The mapping of the priority value of the QUIC session to the corresponding DSCP value. (ii) Mapping QUIC associated IDs to corresponding DSCP values, or (iii) The DSCP value of the QUIC session.
8. The method of claim 6 or 7, wherein: The rule set includes Quality of Service (QoS) enforcement rules (QERs) with DSCP markers, which instruct the NF to create the outer header of the IP packet based on the DSCP auxiliary information.
9. The method as described in any of the preceding claims, wherein: The metadata further includes a PDU set importance PSI indicator for the PDU set.
10. The method as claimed in any of the preceding claims, wherein: The IP packet is a UDP datagram encapsulating Hypertext Transfer Protocol (HTTP) datagrams and QUIC packets.
11. The method of claim 10, wherein: The UDP datagram includes Real-Time Transport Protocol (RTP) extension fields, and The QUIC priority information and the QUIC association ID are included in the RPT extended field.
12. The method of claim 10, wherein: The header of the HTTP datagram includes (i) a context ID for identifying the PDU set, (ii) the QUIC priority information, and (iii) the QUIC association ID.
13. The method according to any one of claims 1 to 9, wherein: The IP packet is a UDP datagram, which encapsulates (i) a first HTTP datagram, which includes a first QUIC datagram containing PDU set information; and (ii) a second HTTP datagram, which includes a second QUIC datagram containing an XRM payload.
14. The method according to any one of claims 1 to 9, wherein: The IP packet is a UDP datagram encapsulating a single HTTP datagram, the single HTTP datagram including (i) a first QUIC datagram containing PDU set information and (ii) a second QUIC datagram containing an XRM payload.
15. One or more apparatuses, including processing hardware and configured to implement the method as described in any of the preceding claims.
