Handling datagrams with unknown identity

Abstract

To provide handling of datagrams with unknown identity.SOLUTION: Various aspects of the present disclose provide mechanisms for handling datagrams, such as datagrams having an unknown context ID, by a UE and / or network entity of a 3GPP network that employs Multipath QUIC (MPQUIC) functionality during a packet-data-unit (PDU) session. For example, the 3GPP network may predetermine the transport mode of datagrams transmitted within a PDU session by the network's policy control functions (PCFs) and convey the transport mode to the UE and network entities that established the PDU session.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to wireless communications, and more particularly to handling datagrams with unknown identities. [Background technology]

[0002] A wireless communication system may include one or more network communication devices, such as base stations, that may support wireless communication for one or more user communication devices, which may also be known as user equipment (UE) or other suitable terminology. A wireless communication system may support wireless communication with one or more user communication devices by utilizing wireless communication system resources (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0003] Some wireless communication systems may support a Multipath QUIC (MPQUIC) feature, which is an upper layer steering function that enables steering, switching, and / or splitting of User Datagram Protocol (UDP) traffic between a UE and a User Plane Function (UPF) of the core network. Some standardization bodies, such as the 3rd Generation Partnership Project (3GPP), define such a function by the Access Traffic Steering, Switching, and Splitting (ATSSS) feature.

[0004] MPQUIC provides multiple transport modes for UDP traffic or datagrams within a UDP flow. These transport modes include a first datagram mode (also referred to as "datagram mode 1") and a second datagram mode (also referred to as "datagram mode 2"), and each datagram mode may define the payload of the datagram (e.g., a HyperText Transfer Protocol (HTTP) datagram). In some cases, a multi-access (MA) protocol data unit (PDU) session may be established using MPQUIC as a steering function. In these cases, if the transport mode of a datagram is the first datagram mode, the datagram may have a context identifier (ID) indicating the value of the first datagram mode (e.g., a value set to zero). Furthermore, the datagram may have a payload that includes a 32-bit integer sequence number that defines the transmission order of the datagram payload. In addition, the datagram may have a UDP payload that includes the UDP packet to be transmitted. Otherwise, if the transport mode is the second datagram mode, the datagram may have a context ID that indicates the value of the second datagram mode (e.g., a non-zero integer). In addition, the datagram may have a UDP payload. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 24.501 [Non-patent document 2] IETF RFC 9298 Summary of the Invention [Means for solving the problem]

[0006] The article "a" before an element is understood to refer, without limitation, to "at least one" of those elements or "one or more" of those elements. The terms "a," "at least one," "one or more," and "at least one of one or more" may be interchangeable. As used herein, including the claims, "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of" or "one or both of") indicates an inclusive list, such as, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the disclosure. In other words, as used herein, the phrase "based on" shall be interpreted similarly to the phrase "based at least in part on." Furthermore, as used herein, including the claims, a "set" may include one or more elements.

[0007] The present disclosure relates to methods, apparatus, and systems that support handling of datagrams with unknown identities within UDP flows for services or applications supported by a wireless communication system.

[0008] Some implementations of the methods and apparatus described herein may further include a network function for wireless communications, the network function including at least one memory and at least one processor coupled to the at least one memory and configured to cause the network function to establish a PDU session for the UE, the PDU session including a UDP flow for a service or application, receive transport mode rules associated with the UDP flow, receive a datagram including an unknown identifier and payload, and handle the payload of the received datagram in accordance with the transport mode of the UDP flow.

[0009] In some implementations of the methods and apparatus described herein, the unknown identifier is an unknown context identifier that indicates the format of the payload.

[0010] In some implementations of the methods and apparatus described herein, the PDU session is an MA PDU session.

[0011] In some implementations of the methods and apparatus described herein, the UDP flow is a service data flow (SDF) and is steered across 3GPP and non-3GPP accesses as a multipath-enabled QUIC steering function.

[0012] In some implementations of the methods and apparatus described herein, a context identifier is assigned to a transport mode associated with multipath-aware QUIC steering functionality for UDP flows.

[0013] In some implementations of the methods and apparatus described herein, the transport mode is datagram mode 1 or datagram mode 2.

[0014] In some implementations of the methods and apparatus described herein, the network function is a user plane function (UPF), and at least one processor is configured to cause the UPF to receive transport mode rules associated with the UDP flow from a session management function (SMF).

[0015] In some implementations of the methods and apparatus described herein, to handle the datagrams, at least one processor is configured to cause a UPF to receive the datagrams.

[0016] In some implementations of the methods and apparatus described herein, the datagrams are HyperText Transfer Protocol (HTTP) datagrams used as part of the format of a QUIC datagram frame.

[0017] In some implementations of the methods and apparatus described herein, the at least one processor is further configured to cause the network function to assign a context identifier to the datagram based on the transport mode and to receive other datagrams of the UDP flow for the service or application that have a context identifier different from the context identifier assigned to the datagram.

[0018] Some implementations of the methods and apparatus described herein may further include a method performed by a network function, the method including the steps of establishing a PDU session for a UE, the PDU session including a UDP flow for a service or application; receiving transport mode rules associated with the UDP flow; receiving a datagram including an unknown identifier and payload; and handling the payload of the received datagram in accordance with the transport mode of the UDP flow.

[0019] In some implementations of the methods and apparatus described herein, the unknown identifier is an unknown context identifier that indicates the format of the payload.

[0020] In some implementations of the methods and apparatus described herein, UDP flows are SDF and are steered across 3GPP and non-3GPP accesses as a multipath-aware QUIC steering function.

[0021] In some implementations of the methods and apparatus described herein, the datagrams are HTTP datagrams used as part of the format of a QUIC datagram frame.

[0022] In some implementations of the methods and apparatus described herein, the method further includes assigning a context identifier to the datagram based on the transport mode, and receiving other datagrams of the UDP flow for the service or application that have a context identifier different from the context identifier assigned to the datagram.

[0023] Some implementations of the methods and apparatus described herein may further include a UE for wireless communication, the UE including at least one memory; and at least one processor coupled to the at least one memory and configured to cause the UE to: establish a PDU session with a UPF to transmit a UDP flow for a service or application; receive rules for steering, switching, and splitting of the UDP flow across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, where the transport mode is a datagram mode for the service or application received from the SMF; and send one or more datagrams of the UDP flow for the service or application using the QUIC steering function using the transport mode received as the rule from the SMF.

[0024] In some implementations of the methods and apparatus described herein, the PDU session is an MA PDU session in which traffic is steered across 3GPP and non-3GPP accesses as a multipath-aware QUIC steering function.

[0025] In some implementations of the methods and apparatus described herein, one or more datagrams include an unknown context ID, and the at least one processor is further configured to cause the UE to handle the payload of the one or more datagrams regardless of the unknown context ID.

[0026] Some implementations of the methods and apparatus described herein may further include a processor for wireless communications, the processor including at least one controller coupled to at least one memory and configured to cause the processor to establish a PDU session with a UPF to transmit a UDP flow for a service or application; receive rules for steering, switching, and splitting of UDP flows across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, where the transport mode is datagram mode for the service or application received from the SMF; and transmit the UDP flow for the service or application using the QUIC steering function using the transport mode received as the rule from the SMF.

[0027] In some implementations of the methods and apparatus described herein, the PDU session is a multiple access (MA) PDU session in which traffic is steered across 3GPP access and non-3GPP access as a multipath-enabled QUIC steering function. [Brief explanation of the drawings]

[0028] [Figure 1] FIG. 1 illustrates an example of a wireless communication system according to aspects of the present disclosure. [Figure 2] FIG. 2 is an exemplary diagram of a datagram according to an aspect of the present disclosure. [Figure 3] FIG. 2 is an exemplary diagram illustrating a call flow procedure according to an aspect of the present disclosure. [Figure 4] FIG. 1 illustrates an example of a user equipment (UE) according to an aspect of the present disclosure. [Figure 5] FIG. 1 illustrates an example processor according to aspects of the present disclosure. [Figure 6]FIG. 1 illustrates an example of network equipment (NE) according to an aspect of the present disclosure. [Figure 7] 1 is a flowchart of a method performed by an NE according to an aspect of the present disclosure. [Figure 8] 1 is a flow diagram of a method performed by a UE according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0029] Some wireless communication systems may not support mechanisms (e.g., capabilities, configurations, parameters) for handling datagrams with unknown context IDs during a PDU session. As a result, these datagrams may be discarded (e.g., dropped) or otherwise become obsolete (e.g., unused) during the PDU session, which may lead to inefficient performance for one or more nodes (e.g., UE, base station, network entities of the core network) and / or poor quality of service (QoS) for one or more services or applications supported by the one or more nodes (e.g., UE, base station, network entities of the core network).

[0030] Various aspects of the present disclosure relate, inter alia, to handling (e.g., processing, managing, receiving, transmitting) datagrams by a wireless communication system including one or more nodes (e.g., a UE, a base station, a network entity of a core network) that support MPQUIC functionality as a steering function for various services, applications, etc. For example, a Policy Control Function (PCF) of the wireless communication system may determine a transport mode for datagrams associated with a PDU session and communicate (e.g., transmit, output) the determined transport mode to one or more nodes (e.g., a UE, a base station, a network entity such as a User Plane Function (UPF) that established the PDU session). Because the determined transport mode is known (e.g., indicated, signaled) to the network entity such as the UE, the base station, the UPF, etc., datagrams may be handled (e.g., processed, received, buffered, utilized) during the PDU session regardless of the value of their Context ID (e.g., whether identified or unknown).

[0031] A network (e.g., a base station, a network entity of a core network) may implicitly register all or any selected values ​​of the context ID of datagrams for the transport mode of a PDU session. In doing so, the network may handle (e.g., buffer, receive, not discard) datagrams with unknown context IDs received for a UDP flow. Furthermore, the network (e.g., a base station, a network entity of a core network) may allocate the same context ID for datagrams sent by a node (e.g., a UE or a UPF) within a UDP flow (e.g., an SDF). In addition, the network (e.g., a base station, a network entity of a core network) may maintain the value of the context ID within the UDP flow. Thus, the network may increase network efficiency and / or QoS by handling datagrams during a PDU session regardless of their context ID, among other benefits.

[0032] 1 illustrates an example of a wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0033] One or more NEs 102 may be distributed throughout a geographic region to form the wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terminology. The NEs 102 and UEs 104 may communicate via communication links that may be wireless or wired. For example, the NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0034] An NE 102 may provide a geographic coverage area in which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, the NE 102 and the UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the NE 102, e.g., a satellite associated with a non-terrestrial network (NTN), may be mobile. In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, although different geographic coverage areas may be associated with different NEs 102.

[0035] One or more UEs 104 may be dispersed throughout the geographic region of the wireless communication system 100. The UEs 104 may include or be referred to as remote units, mobile devices, wireless devices, remote devices, subscriber devices, transmitter devices, receiver devices, or some other suitable terminology. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, among other examples. Additionally or alternatively, the UEs 104 may be referred to as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communication (MTC) devices, among other examples.

[0036] The UE 104 may be capable of supporting direct wireless communication with other UEs 104 via a communication link. For example, the UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or cellular-V2X deployments, the communication link may be referred to as a sidelink. The UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0037] An NE 102 may support communication with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NEs 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some implementations, the NEs 102 may communicate directly with each other. In some other implementations, the NEs 102 may communicate indirectly with each other (e.g., via the CN 106). In some implementations, one or more NEs 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio head, smart radio head, or transmission-reception point (TRP).

[0038] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) or 5G core (5GC) that may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and user plane entities that route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0039] The CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N3, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the CN 106 via the NE 102. The CN 106 may route traffic (e.g., control information, data, etc.) between the UE 104 and the application server using the established session (e.g., an established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0040] In the wireless communication system 100, the NEs 102 and UEs 104 may perform various operations (e.g., wireless communications) using resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In some implementations, the NEs 102 and UEs 104 may support different resource structures. For example, the NEs 102 and UEs 104 may support different frame structures. In some implementations, such as 4G, the NEs 102 and UEs 104 may support a single frame structure. In some other implementations, such as 5G, among other suitable radio access technologies, the NEs 102 and UEs 104 may support different frame structures (i.e., multiple frame structures). The NEs 102 and UEs 104 may support different frame structures based on one or more numerologies.

[0041] One or more numerologies may be supported in the wireless communication system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth carrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0042] Time intervals of resources (e.g., communication resources) may be organized by frames (also called radio frames). Each frame may have a duration, e.g., 10 milliseconds (ms). In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0043] Additionally or alternatively, time intervals of resources (e.g., communication resources) may be organized by slots. For example, a subframe may include a certain number (e.g., amount) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, respectively, may utilize 1 slot per subframe, 2 slots per subframe, 4 slots per subframe, 8 slots per subframe, and 16 slots per subframe, respectively. Each slot may include a certain number (e.g., amount) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., amount) of slots in a subframe may depend on the numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for normal cyclic prefix and extended cyclic prefix may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframe and slot.

[0044] In the wireless communication system 100, the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications on one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by NEs 102 and UEs 104, among other equipment or devices, for its short-range, high-data-rate capabilities.

[0045] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., μ=0) including a subcarrier spacing of 15 kHz, a second numerology (e.g., μ=1) including a subcarrier spacing of 30 kHz, and a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology (e.g., μ=2) including a subcarrier spacing of 60 kHz, and a fourth numerology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0046] As described herein, the wireless communication system 100 may employ a mechanism for handling datagrams during a PDU session (e.g., a UDP flow) that implicitly registers the datagram to the UDP flow regardless of the datagram's context ID value.

[0047] 2 shows an example diagram of a datagram 200 according to an aspect of the present disclosure. Datagram 200, which may be an HTTP datagram (e.g., an HTTP datagram used as part of the format of a QUIC datagram frame), includes a payload 210 and a context ID 220. Payload 210 may be a UDP payload containing a UDP packet to send and, depending on the transport mode, may include a 32-bit integer sequence number that defines the transmission order of the datagram payloads (e.g., for datagram mode 1).

[0048] The context ID 220 depends on the transport mode of the associated service or application and includes a value that provides the semantic or format of the payload 210. For example, when the transport mode is datagram mode 2, the value is set to zero, and when the transport mode is datagram mode 1, the value is set to a non-zero integer. In some cases, the context ID 220 (e.g., value) is unknown to the network (e.g., an unknown identifier).

[0049] In some cases, one or more nodes (e.g., UE, base station, network entity of the core network) associated with the UDP flow and / or PDU session, such as the UE and UPF, may obtain transport mode information associated with the MPQUIC steering function for transmission of the UDP flow (e.g., for a particular service / application) across 3GPP and non-3GPP accesses from the ATSSS and N4 rules received from the SMF. The SMF may receive policy and charging control (PCC) rules from the PCF and translate (e.g., map, associate) the received PCC rules into ATSSS and N4 rules. In some cases, the steering function and associated transport mode are explicitly used by the UE and UPF.

[0050] When the steering function includes or employs MPQUIC functionality, the associated transport mode of a service / application is determined by the PCF and communicated to the UE and UPF via the SMF, regardless of or independent of any context ID value in the transmitted datagrams. Thus, the network provides the UE and UPF with transport mode information before handling any datagrams in the UDP flow of the service / application, and implicitly registers all datagrams (e.g., datagrams with the same or different context IDs) to the UDP flow (e.g., SDF) of the service / application. As described herein, in some cases, the UE and UPF can handle (e.g., receive, buffer, process) and not discard (e.g., discard) a datagram even when the datagram's context ID is unknown to the UE and UPF or other handling peer node.

[0051] 3 shows an example diagram of a call flow procedure 300 according to an aspect of the present disclosure. The call flow procedure 300 may implement various aspects of the present disclosure described herein. For example, the call flow procedure 300 may include a UE 310, an AMF 320, an SMF 330, a PCF 340, and a UPF 350, which may be examples of the UE, AMF, SMF, PCF, and UPF described herein. In the following description of the call flow procedure 300, operations among the UE 310, the AMF 320, the SMF 330, the PCF 340, and / or the UPF 350 may be performed in a different order or at different times. Some operations may be omitted, or other operations may be added. Although the UE 310, the AMF 320, the SMF 330, the PCF 340, and / or the UPF 350 are shown performing the operations of the call flow procedures 300, some aspects of some operations may be performed by other entities in the call flow procedures 300, or by entities not shown in the call flow procedures 300, or any combination thereof.

[0052] In step 1, the UE 310 may output (e.g., send) a PDU session establishment request to the AMF 320. The PDU session establishment request may trigger a PDU session establishment procedure. For example, the UE 310 may output the PDU session establishment request to the AMF 320 in a Non-Access Stratum (NAS) message for the PDU session establishment procedure. Alternatively, the UE 310 may send the PDU session establishment request to the AMF 320 via a base station (not shown). The PDU session establishment request may include one or more information elements (IEs) in the NAS message. The PDU session establishment procedure may be for establishing an MA PDU session.

[0053] In step 2, the AMF 320 may generate and send a request message to the SMF 330. The request message may be a NAS request message (e.g., Nsmf_PDUSession_CreateSMContext request) that may include one or more IEs to request a session management (SM) context from the SMF 330. In step 3, the SMF 330 may generate and send to the AMF 320 a NAS response message (e.g., Nsmf_PDUSession_CreateSMContext response) that may include an SM context ID.

[0054] In step 4, the SMF 330 may send a request message to establish an SM policy association to the PCF 340. The request message (e.g., an Npcf_SMPolicyControl_Create message) may include information related to the PDU session for the UE 310.

[0055] In step 5, the PCF 340 may send a response message (e.g., Npcf_SMPolicyControl_Create response) to the SMF 330 indicating the SMF policy association.

[0056] In step 6, the SMF 330 may determine (e.g., identify, derive) ATSSS rules for the UE 310. For example, the SMF 330 may determine (e.g., identify, derive) ATSSS rules for the UE 310 according to the PCC rules. The ATSSS rules may be provided (e.g., transmitted, output) to the UE 310 to control traffic steering, switching, and segmentation of uplink communications (e.g., packets, PDUs). Further, the SMF 330 may determine (e.g., identify, derive) N4 rules for the UPF 350. For example, the SMF 330 may determine (e.g., identify, derive) N4 rules for the UPF 350 according to the PCC rules. The N4 rules may be provided (e.g., transmitted, output) to the UPF 350 to control traffic steering, switching, and segmentation of downlink communications (e.g., packets, PDUs).

[0057] In step 7, the SMF 330 may send an N4 session request message to the UPF 350, which may initiate an N4 session establishment procedure with the UPF 350. The N4 session request message may include or indicate the N4 rules (e.g., determined by the SMF 330) of the MA PDU session. In response to the N4 session request message, the UPF 350 may activate (e.g., enable) the MPQUIC functionality for the MA PDU session. In some cases, the UPF 350 may activate the MPQUIC functionality for the MA PDU session based at least in part on the N4 rules (e.g., determined by the SMF 330) of the MA PDU session.

[0058] In step 8, UPF 350 may send an N4 session response message to SMF 330. The N4 session response message may include or indicate an MPQUIC link-specific multipath address / prefix, MPQUIC proxy information, or both. For example, UPF 350 may assign (e.g., allocate) an MPQUIC link-specific multipath address / prefix for the UE and indicate the MPQUIC link-specific multipath address / prefix and / or MPQUIC proxy information to SMF 330.

[0059] In step 9, the SMF 330 may send a PDU session accept message to the AMF 320. The SMF 330 may include an MA PDU session accept indication in the Namf_Communication_N1N2MessageTransfer message, which may indicate to the AMF 320 that the N2 SM information included in the message should be sent (e.g., forwarded) to the UE 310. The AMF 320 may classify (e.g., mark, register) the PDU session as an MA PDU session based on the received MA PDU session accept indication.

[0060] In step 10, the AMF 320 may send a PDU Session Establishment Accept message, and the UE 310 may receive the PDU Session Establishment Accept message (e.g., directly or via a base station (not shown)), where the PDU Session Establishment Accept message indicates to the UE 310 that the requested MA PDU session has been successfully established. Additionally, the message may include or indicate the ATSSS rules for the MA PDU session (e.g., derived by the SMF 330), the MPQUIC link-specific multipath address / prefix of the UE 310, and MPQUIC proxy information.

[0061] In step 11, a UDP flow is established between one or more of the UE 310, the AMF 320, the SMF 330, the PCF 340, and / or the UPF 350. For example, uplink and downlink data is established for an MA PDU session, with UDP packets traveling between the UE 310, the AMF 320, the SMF 330, the PCF 340, and / or the UPF 350. The UE 310 may use the ATSSS rules for the MPQUIC steering function and the associated transport mode identified by the context ID.

[0062] As described herein (and according to 3GPP TS 24.501), if the transport mode is datagram mode 2, the UE 310 may set the context ID to zero; otherwise, the UE 310 uses a non-zero context ID (according to IETF RFC 9298). In such a case, the context ID is an even value because the UE 310 is considered a client. To send UDP flows of the same SDF, the UPF 350 can use a non-zero odd value for the context ID (according to IETF RFC 9298) and act as a proxy.

[0063] Therefore, the UE 310 or the UPF 350 may consider any selected value of the context ID as being implicitly or previously registered for the transport mode. Furthermore, when a value of the context ID is registered, the same context ID may be used by the UE 310 and the UPF 350 for the same UDP flow (e.g., SDF) in accordance with IETF RFC 9298 and need not be an odd or even value because the transport mode is implicitly registered.

[0064] Additionally, during the lifetime of a UDP flow (e.g., SDF) of a service / application, the UE 310 and the UPF 350 may use the same value for the context ID for different datagrams within that SDF. However, if during the lifetime of a UDP flow of a service / application, a new, unknown value for the context ID (e.g., for a new datagram) is received for the UDP flow, the UE 310 and the UPF 350 may consider (e.g., identify) the unknown context ID (e.g., an unknown identifier for the datagram) as registered for that UDP flow and handle the datagram accordingly (e.g., buffer or receive the datagram).

[0065] 4 illustrates an example of a UE 400 according to aspects of the present disclosure. The UE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations or components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0066] The processor 402, memory 404, controller 406, or transceiver 408, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry), which may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device configured as or otherwise supporting means for performing the functions described in this disclosure, or any combination thereof.

[0067] The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to cause the UE 400 to perform various functions of the present disclosure.

[0068] The memory 404 may include volatile or nonvolatile memory. The memory 404 may store computer-readable and computer-executable code, including instructions that, when executed by the processor 402, cause the UE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 404 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0069] In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to cause the UE 400 to perform one or more of the functions described herein (e.g., by the processor 402 executing instructions stored in the memory 404). For example, the processor 402 may support wireless communication in the UE 400 according to examples disclosed herein. The UE 400 may be configured to support means for establishing a PDU session with the UPF to transmit a UDP flow for a service or application, receiving rules for steering, switching, and splitting the UDP flow across 3GPP and non-3GPP accesses as a QUIC steering function using a transport mode, where the transport mode is a datagram mode for the service or application received from the SMF, and transmitting one or more datagrams of the UDP flow for the service or application using the QUIC steering function using the transport mode received as the rule from the SMF.

[0070] The controller 406 may manage input and output signals for the UE 400. The controller 406 may also manage peripheral devices not integrated into the UE 400. In some implementations, the controller 406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 406 may be implemented as part of the processor 402.

[0071] In some implementations, the UE 400 may include at least one transceiver 408. In some other implementations, the UE 400 may have two or more transceivers 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

[0072] The receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the received signal by reversing the modulation technique applied during transmission of the signal to obtain transmitted data. The receiver chain 410 may include at least one decoder for decoding the demodulated signal for processing to receive transmitted data.

[0073] The transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal over the air or wireless medium.

[0074] FIG. 5 illustrates an example processor 500 according to aspects of the present disclosure. The processor 500 may be an example of a processor configured to perform various operations in accordance with examples described herein. The processor 500 may include a controller 502 configured to perform various operations in accordance with examples described herein. The processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506. One or more of these components may electronically communicate or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0075] Processor 500 may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, obtain, retrieve, send, output, transfer, store, determine, identify, access, write, read) in accordance with examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor 500)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0076] Controller 502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, reading) of processor 500 to cause processor 500 to support various operations in accordance with examples described herein. For example, controller 502 may act as a control unit for processor 500, generating control signals that manage the operation of various components of processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0077] The controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instructions to be executed to cause the processor 500 to support various operations in accordance with examples described herein. The controller 502 may be configured to track memory addresses of instructions associated with the memory 504. The controller 502 may be configured to decode the instructions to determine the operations to be performed and the associated operands. For example, the controller 502 may be configured to interpret the instructions and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples described herein. Additionally or alternatively, the controller 502 may be configured to manage the flow of data within the processor 500. The controller 502 may be configured to control the transfer of data between registers, an arithmetic logic unit (ALU), and other functional units of the processor 500.

[0078] The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500) or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500). In some other implementations, the memory 504 may reside outside the processor chipset (e.g., remote from the processor 500).

[0079] The memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. The controller 502 and / or the processor 500 may be configured to execute the computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions. For example, the processor 500 and / or the controller 502 may be coupled to or to the memory 504, and the processor 500, the controller 502, and the memory 504 may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors, and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured, individually or collectively, to perform various functions herein.

[0080] The one or more ALUs 506 may be configured to support various operations according to the examples described herein. In some implementations, the one or more ALUs 506 may reside within or on a processor chipset (e.g., processor 500). In some other implementations, the one or more ALUs 506 may reside external to the processor chipset (e.g., processor 500). The one or more ALUs 506 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, the one or more ALUs 506 may receive input operands and an operation code that determines the operation to be performed. The one or more ALUs 506 may be comprised of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, for processing and manipulating data through operations. Additionally or alternatively, one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), which allows one or more ALUs 506 to handle conditional operations, comparisons, and bit operations.

[0081] Processor 500 may support wireless communication according to examples disclosed herein. For example, processor 500 may be configured or operable to support means for establishing a PDU session with a UPF to transmit a UDP flow for a service or application, receiving rules for steering, switching, and splitting the UDP flow across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, where the transport mode is a datagram mode for the service or application received from the SMF, and transmitting one or more datagrams of the UDP flow for the service or application using the QUIC steering function using the transport mode received as the rule from the SMF.

[0082] 6 illustrates an example of a NE 600 according to an aspect of the present disclosure. The NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0083] The processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry), which may include a processor, digital signal processor (DSP), application specific integrated circuit (ASIC), or other programmable logic device configured as or otherwise supporting means for performing the functions described in this disclosure, or any combination thereof.

[0084] The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the NE 600 to perform various functions of the present disclosure.

[0085] The memory 604 may include volatile or nonvolatile memory. The memory 604 may store computer-readable and computer-executable code, including instructions that, when executed by the processor 602, cause the NE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 604 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0086] In some implementations, the processor 602 and the memory 604 coupled to the processor 602 may be configured to cause the NE 600 to perform one or more of the functions described herein (e.g., by the processor 602 executing instructions stored in the memory 604).

[0087] For example, the processor 602 may support wireless communications in the NE 600 according to examples disclosed herein. The NE 600 may be configured to support means for establishing a PDU session for a UE, where the PDU session includes a UDP flow for a service or application, receiving transport mode rules associated with the UDP flow, receiving datagrams including unknown identifiers and payloads, and handling the payload of the received datagrams according to the transport mode of the UDP flow. The operations of 708 may be performed according to examples described herein. In some implementations, aspects of the operations of 708 may be performed by the NE as described with reference to FIG. 6.

[0088] The controller 606 may manage input and output signals for the NE 600. The controller 606 may also manage peripheral devices not integrated into the NE 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0089] In some implementations, the NE 600 may include at least one transceiver 608. In some other implementations, the NE 600 may have two or more transceivers 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0090] The receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the received signal by reversing the modulation technique applied during transmission of the signal to obtain transmitted data. The receiver chain 610 may include at least one decoder for decoding the demodulated signal for processing to receive transmitted data.

[0091] The transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal over the air or wireless medium.

[0092] 7 illustrates a flow diagram of a method according to an aspect of the present disclosure. The operations of the method may be performed by an NE as described herein. In some implementations, the NE may execute a set of instructions to control functional elements of the NE to perform the described functions.

[0093] At 702, the method may include establishing a PDU session for a UE, the PDU session including a UDP flow for a service or application. The operations of 702 may be performed according to examples described herein. In some implementations, aspects of the operations of 702 may be performed by an NE as described with reference to FIG. 6.

[0094] At 704, the method may include receiving transport mode rules associated with the UDP flow. The operations of 704 may be performed according to examples described herein. In some implementations, aspects of the operations of 704 may be performed by an NE as described with reference to FIG. 6.

[0095] At 706, the method may include receiving a datagram including an unknown identifier and a payload. The operations of 706 may be performed according to examples described herein. In some implementations, aspects of the operations of 706 may be performed by an NE as described with reference to FIG. 6.

[0096] At 708, the method may include handling the payload of the received datagram according to a transport mode of the UDP flow. The operations of 708 may be performed according to examples described herein. In some implementations, aspects of the operations of 708 may be performed by an NE as described with reference to FIG. 6.

[0097] It should be noted that the methods described herein describe possible implementations, and that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0098] 8 illustrates a flow diagram of a method according to an aspect of the present disclosure. The operations of the method may be performed by a UE as described herein. In some implementations, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions.

[0099] At 802, the method may include establishing a PDU session with a UPF to transmit a UDP flow related to a service or application. The operations of 802 may be performed according to examples described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to FIG. 4.

[0100] At 804, the method may include receiving rules for steering, switching, and splitting UDP flows across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, where the transport mode is a datagram mode for the service or application received from the SMF. The operations of 804 may be performed according to examples described herein. In some implementations, aspects of the operations of 804 may be performed by a UE as described with reference to FIG. 4.

[0101] At 806, the method may include transmitting one or more datagrams of a UDP flow for the service or application using a QUIC steering function using the transport mode received as a rule from the SMF. The operations of 806 may be performed according to examples described herein. In some implementations, aspects of the operations of 806 may be performed by the UE as described with reference to FIG. 4.

[0102] It should be noted that the methods described herein describe possible implementations, and that the acts and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0103] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0104] 100 Wireless Communication System 102 NE 104UE 106CN 200 datagrams 210 Payload 220 Context ID 300 Call Flow Steps 310 UE 320 AMF 330 SMF 340 PCF 350 UPF 400 UE 402 processor 404 Memory 406 Controller 408 Transceiver 410 receiver chain 412 Transmitter Chain 500 processors 502 Controller 504 memory 506 ALU 600 NE 602 processor 604 memory 606 Controller 608 Transceiver 610 Receiver Chain 612 Transmitter Chain

Claims

1. A network function for wireless communications, comprising: At least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor controls the network function to: Establishing a Protocol Data Unit (PDU) session for a user equipment (UE), the PDU session including a User Datagram Protocol (UDP) flow for a service or application; receiving a transport mode rule associated with the UDP flow; receiving a datagram containing an unknown identifier and payload; handling the payload of the received datagram according to the transport mode of the UDP flow; A network function configured to:

2. The network function of claim 1 , wherein the unknown identifier is an unknown context identifier that indicates a format of the payload.

3. The network function of claim 1 , wherein the PDU session is a multiple access (MA) PDU session.

4. 2. The network function of claim 1, wherein the UDP flow is a service data flow (SDF) and is steered across 3GPP and non-3GPP accesses as a multipath-enabled QUIC steering function.

5. 5. The network function of claim 4, wherein a context identifier is assigned to the transport mode associated with the multipath-aware QUIC steering function of the UDP flow.

6. The network function of claim 1 , wherein the transport mode is datagram mode 1 or datagram mode 2.

7. 2. The network function of claim 1, wherein the network function is a User Plane Function (UPF), and the at least one processor is configured to cause the UPF to receive the rules for the transport mode associated with the UDP flow from a Session Management Function (SMF).

8. The network function of claim 1 , wherein to handle the datagram, the at least one processor is configured to cause the UPF to receive the datagram.

9. 2. The network function of claim 1, wherein the datagram is a HyperText Transfer Protocol (HTTP) datagram used as part of a QUIC datagram frame format.

10. The at least one processor may configure the network function to: assigning a context identifier to the datagram based on the transport mode; receiving other datagrams of the UDP flow for the service or application having a context identifier different from the context identifier assigned to the datagram; The network functionality of claim 1 further configured to:

11. 1. A method performed by a network function, comprising: establishing a Protocol Data Unit (PDU) session for a User Equipment (UE), the PDU session including a User Datagram Protocol (UDP) flow for a service or application; receiving a transport mode rule associated with the UDP flow; receiving a datagram containing an unknown identifier and payload; handling the payload of the received datagram according to the transport mode of the UDP flow; A method comprising:

12. The method of claim 11 , wherein the unknown identifier is an unknown context identifier that indicates a format of the payload.

13. The method of claim 11, wherein the UDP flow is a service data flow (SDF) and is steered across 3GPP and non-3GPP accesses as a multipath-aware QUIC steering function.

14. 12. The method of claim 11, wherein the datagram is a HyperText Transfer Protocol (HTTP) datagram used as part of the format of a QUIC datagram frame.

15. assigning a context identifier to the datagram based on the transport mode; receiving other datagrams of the UDP flow for the service or application having a context identifier different from the context identifier assigned to the datagram; 12. The method of claim 11, further comprising:

16. A user equipment (UE) for wireless communications, comprising: At least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor causes the UE to: establishing a packet data unit (PDU) session with a user plane function (UPF) to transmit a user datagram protocol (UDP) flow related to the service or application; receiving rules for steering, switching, and splitting the UDP flow across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, wherein the transport mode is a datagram mode for the service or application received from a Session Management Function (SMF); sending one or more datagrams of the UDP flow for the service or the application using the QUIC steering function using the transport mode received as the rule from the SMF; A UE configured to cause

17. 17. The UE of claim 16, wherein the PDU session is a multiple access (MA) PDU session in which traffic is steered across 3GPP access and non-3GPP access as a multipath-enabled QUIC steering function.

18. The one or more datagrams include an unknown context ID, and the at least one processor causes the UE to:

17. The UE of claim 16, further configured to cause handling of a payload of the one or more datagrams without regard to the unknown context ID.

19. 1. A processor for wireless communications, comprising: at least one controller coupled to at least one memory, the at least one controller configured to cause the processor to: establishing a packet data unit (PDU) session with a user plane function (UPF) to transmit a user datagram protocol (UDP) flow related to the service or application; receiving rules for steering, switching, and splitting the UDP flow across 3GPP access and non-3GPP access as a QUIC steering function using a transport mode, wherein the transport mode is a datagram mode for the service or application received from a Session Management Function (SMF); transmitting the UDP flow for the service or the application using the QUIC steering function using the transport mode received as the rule from the SMF; a processor configured to cause the

20. 20. The processor of claim 19, wherein the PDU session is a multiple access (MA) PDU session in which traffic is steered across 3GPP access and non-3GPP access as a multipath-enabled QUIC steering function.

Images