Processing of datagrams with unknown identifiers

Abstract

Aspects of the present disclosure provide mechanisms for processing datagrams, such as datagrams with unknown context IDs, by UEs and / or network entities of a 3GPP network employing multipath QUIC (MPQUIC) functionality during a Packet Data Unit (PDU) session. For example, a 3GPP network may pre-determine a transmission mode for datagrams sent within a PDU session via a policy control function (PCF) of the network, and transmit the transmission mode to a UE and a network entity establishing the PDU session.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more particularly to processing datagrams with unknown identifiers. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which can support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Additionally, the wireless communication system can support wireless communication across a variety of wireless access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] Some wireless communication systems support Multipath QUIC (MPQUIC), a higher-level guidance function that enables the steering, handover, and / or partitioning of User Datagram Protocol (UDP) traffic between the UE and the User Plane Function (UPF) of the core network. Some standards organizations (such as the 3rd Generation Partnership Project (3GPP)) define this function via the Access Traffic Steering, Handover, Partition (ATSSS) feature.

[0004] MPQUIC provides several transport modes for datagrams within UDP traffic or UDP streams. 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"), each of which can define a payload for the datagram (e.g., a Hypertext Transfer Protocol (HTTP) datagram). In some cases, MPPQUIC can be used as a bootstrapping function to establish a Multiple Access (MA) Protocol Data Unit (PDU) session. In these cases, if the transport mode used for the datagram is the first datagram mode, the datagram can have a context identifier (ID) indicating a value used for the first datagram mode (e.g., a value set to zero). Additionally, the datagram can have a payload including a 32-bit integer sequence number that defines the transmission order of the datagram payload. Furthermore, the datagram can have a UDP payload containing UDP packets to be sent. In other cases, if the transport mode is the second datagram mode, the datagram can have a context ID indicating a value used for the second datagram mode (e.g., a non-zero integer). Additionally, datagrams can have UDP payloads. Summary of the Invention

[0005] The article “a” preceding an element is non-restrictive and is understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein (including in the claims), the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of the following,” or “one or more of the following,” or “one or both of the following”) indicates an inclusive list, such that a list of at least one of, for example, A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference 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 this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Additionally, as used herein (including in the claims), “set” may include one or more elements.

[0006] This disclosure relates to methods, apparatus, and systems for supporting the processing of datagrams with unknown identifiers in UDP streams for services or applications supported by wireless communication systems.

[0007] Some implementations of the methods and apparatus described herein may also include network functions for wireless communication, the network functions including: at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and configured such that the network function: establishes a PDU session for a UE, wherein the PDU session includes a UDP stream for a service or application, receives rules of a transmission mode associated with the UDP stream, receives datagrams including an unknown identifier and a payload, and processes the payload of the received datagrams according to the transmission mode of the UDP stream.

[0008] 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.

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

[0010] In some implementations of the methods and apparatus described herein, the UDP stream is a Service Data Stream (SDF) and is bootstrapped as a multipath-enabled QUIC bootstrapping function across 3GPP access and non-3GPP access.

[0011] In some implementations of the methods and apparatus described herein, a context identifier is assigned for the transport mode associated with the QUIC bootstrap function that enables multipathing of UDP streams.

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

[0013] 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 rules of transport modes associated with UDP streams from a session management function (SMF).

[0014] In some implementations of the methods and apparatus described herein, in order to process datagrams, at least one processor is configured to cause the UPF to receive datagrams.

[0015] In some implementations of the methods and apparatus described herein, the datagram is a Hypertext Transfer Protocol (HTTP) datagram used as part of the format of a QUIC datagram frame.

[0016] In some implementations of the methods and apparatus described herein, at least one processor is further configured to enable network functions to: assign context identifiers to datagrams based on transport modes, and receive additional datagrams for UDP streams used for services or applications, the additional datagrams having context identifiers different from those assigned to the datagrams.

[0017] Some implementations of the methods and apparatus described herein may also include methods performed by network functions, the methods comprising: establishing a PDU session for a UE, wherein the PDU session includes a UDP stream for a service or application; receiving rules of a transport mode associated with the UDP stream; receiving a datagram including an unknown identifier and a payload; and processing the payload of the received datagram according to the transport mode of the UDP stream.

[0018] 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.

[0019] In some implementations of the methods and apparatus described herein, the UDP stream is an SDF and is bootstrapped across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

[0020] In some implementations of the methods and apparatus described herein, the datagram is an HTTP datagram used as part of the format of a QUIC datagram frame.

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

[0022] Some implementations of the methods and apparatus described herein may further include: a UE for wireless communication, the UE comprising: at least one memory and at least one processor coupled to the at least one memory and configured such that the UE: establishes a PDU session with a UPF for transmitting a UDP stream for a service or application; receives rules for bootstrapping, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access as a QUIC bootstrapping function with a transport mode, wherein the transport mode is a datagram mode for the service or application received from an SMF; and uses the QUIC bootstrapping function with the transport mode received from the SMF as rules to transmit one or more datagrams of the UDP stream for the service or application.

[0023] In some implementations of the methods and apparatus described herein, the PDU session is an MA PDU session, in which traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

[0024] In some implementations of the methods and apparatus described herein, one or more datagrams include an unknown context ID, and at least one processor is further configured such that the UE: processes the payload of one or more datagrams regardless of the unknown context ID.

[0025] Some implementations of the methods and apparatus described herein may further include: a processor for wireless communication, the processor comprising: at least one controller coupled to at least one memory and configured such that the processor: establishes a PDU session with a UPF for transmitting a UDP stream for a service or application; receives rules for bootstrapping, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access as a QUIC bootstrapping function with a transport mode, wherein the transport mode is a datagram mode for the service or application received from an SMF; and uses the QUIC bootstrapping function with the transport mode received from the SMF as rules to transmit the UDP stream for the service or application.

[0026] In some implementations of the methods and apparatus described herein, the PDU session is a multiple access (MA) PDU session, in which traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function. Attached Figure Description

[0027] Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are shown.

[0028] Figure 2 Example diagrams of datagrams according to various aspects of this disclosure are shown.

[0029] Figure 3 Example diagrams depicting call flows according to various aspects of this disclosure are shown.

[0030] Figure 4 Examples of user equipment (UE) according to various aspects of this disclosure are shown.

[0031] Figure 5 Examples of processors according to various aspects of this disclosure are shown.

[0032] Figure 6 Examples of network devices (NEs) according to various aspects of this disclosure are shown.

[0033] Figure 7 A flowchart of a method performed by an NE according to various aspects of this disclosure is shown.

[0034] Figure 8 A flowchart of a method performed by a UE according to various aspects of this disclosure is shown. Detailed Implementation

[0035] Some wireless communication systems may not support mechanisms (e.g., functions, configurations, parameters) for processing datagrams with unknown context IDs during a PDU session. Therefore, these datagrams may be discarded (e.g., dropped) or abandoned (e.g., unused) during a PDU session, potentially leading to inefficient performance for one or more nodes (e.g., UEs, base stations, network entities in the core network) and / or low Quality of Service (QoS) for one or more services or applications supported by one or more nodes (e.g., UEs, base stations, network entities in the core network).

[0036] Various aspects of this disclosure relate to the processing (e.g., processing, managing, receiving, transmitting) of datagrams, particularly through wireless communication systems including one or more nodes (e.g., UEs, base stations, network entities of the core network) that support MPQUIC functionality as a bootstrapping function for various services, applications, etc. For example, a policy control function (PCF) of the wireless communication system can determine the transmission pattern for datagrams associated with a PDU session and transmit (e.g., transmit, output) the determined transmission pattern to one or more nodes (e.g., UEs, base stations, network entities, user plane functions (UPFs) such as those for establishing PDU sessions). Since the determined transmission pattern is known to the UE, base station, and network entity (such as the UPF) (e.g., indicated, signaled to the UE), the datagram can be processed (e.g., processed, received, buffered, utilized) during the PDU session regardless of the value of the datagram's context ID (e.g., whether it is identified or unknown).

[0037] The network (e.g., a base station, a network entity in the core network) can implicitly register all or any selected values ​​for the context ID of datagrams used in the transmission mode of a PDU session. In doing so, the network can process (e.g., buffer, receive, not discard) datagrams with unknown context IDs received for UDP streams. Additionally, the network (e.g., a base station, a network entity in the core network) can assign the same context ID to datagrams sent by nodes (e.g., UEs or UPFs) within a UDP stream (e.g., an SDF). Furthermore, the network (e.g., a base station, a network entity in the core network) can maintain the value of the context ID within the UDP stream. Therefore, the network can enhance its efficiency and / or QoS during a PDU session by processing datagrams, regardless of the datagram's context ID and other benefits.

[0038] Figure 1Examples of a wireless communication system 100 according to various aspects of this disclosure are shown. 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 wireless access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network (such as a 5G network), an advanced 5G (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless 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).

[0039] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, network functions, network entities, radio access networks (RANs), Node Bs, eNodeBs (eNBs), next-generation Node Bs (gNBs), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, sending signaling) via a Uu interface.

[0040] NE 102 can provide a geographic coverage area for which NE 102 can support services for one or more UE 104s within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NE 102s.

[0041] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or Machine Type Communication (MTC) device, etc.

[0042] UE 104 may be able to support direct wireless communication with other UE 104s via a communication link. For example, 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) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0043] NE 102 can support communication with CN 106, or with another NE 102, or both. For example, NE 102 can connect to other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some implementations, NE 102 can communicate directly with each other. In some other implementations, NE 102 can communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC can communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0044] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnects 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 entities 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 CN 106.

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

[0046] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, NE 102 and UE 104 can support different resource structures. For example, NE 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, NE 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and in other suitable radio access technologies, NE 102 and UE 104 can support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 can support various frame structures based on one or more sets of parameters.

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

[0048] Time intervals for resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration of, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0049] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can respectively utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe may depend on the parameter set. For a regular cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may include 12 symbols. The relationships between the number of symbols per time slot, time slots per subframe, and time slots per frame for both the normal and extended cyclic prefixes can depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0050] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. By way of example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a, or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, NE 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0051] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with a first parameter set (e.g., μ = 0) that includes a 15 kHz subcarrier spacing; a second parameter set (e.g., μ = 1) that includes a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ = 2) that includes a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., μ = 2) that includes a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ = 3) that includes a 120 kHz subcarrier spacing.

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

[0053] Figure 2 Example diagrams of a datagram 200 according to various aspects of this disclosure are shown. The 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. The payload 210 may be a UDP payload containing UDP packets for transmission, and depending on the transmission mode, may include a 32-bit integer sequence number that defines the transmission order of the payload for the datagram (e.g., for datagram mode 1).

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

[0055] In some cases, one or more nodes associated with a UDP stream and / or PDU session (e.g., UE, base station, network entities in the core network), such as the UE and UPF, can obtain transport mode information associated with the MPQUIC bootstrapping function from ATSSS rules and N4 rules received by the SMF. This MPQUIC bootstrapping function is used to transport UDP streams across 3GPP access and non-3GPP access (e.g., for a specific service / application). The SMF can receive Policy and Charging Control (PCC) rules for the PCF and transform (e.g., map, associate) the received PCC rules into ATSSS rules and N4 rules. In some cases, the bootstrapping function and associated transport modes are explicitly used by the UE and UPF.

[0056] When the bootstrapping function includes or employs MPQUIC, the associated transport mode for the service / application is determined by the PCF and transmitted to the UE and UPF via the SMF, regardless of or independent of any context ID value within the transmitted datagram. Therefore, the network provides transport mode information to the UE and UPF before processing any datagram during the UPD stream for the service / application, implicitly registering all datagrams (e.g., datagrams with the same or different context IDs) to the UDP stream for the service / application (e.g., SDF). As described herein, in some cases, the UE and UPF may process (e.g., receive, buffer, process) and not discard (e.g., drop) datagrams, even when the context ID used for the datagram is unknown to the UE and UPF, or other processing peers.

[0057] Figure 3 Example diagrams of a call flow procedure 300 according to various aspects of this disclosure are shown. The call flow procedure 300 can implement various aspects of this disclosure described herein. For example, the call flow procedure 300 may include UE 310, AMF 320, SMF 330, PCF 340, and 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 between UE 310, AMF 320, SMF 330, PCF 340, and / or UPF 350 may be performed in different orders or at different times. Some operations may also be omitted, or other operations may be added. Although the UE 310, AMF 320, SMF 330, PCF 340, and / or UPF 350 are shown performing the operation of the call flow procedure 300, some aspects of some operations may also be performed by other entities of the call flow procedure 300, or entities not shown in the call flow procedure 300, or any combination thereof.

[0058] In step 1, UE 310 may output (e.g., send) a PDU session establishment request to AMF 320. The PDU session establishment request may trigger a PDU session establishment procedure. For example, UE 310 may output the PDU session establishment request to AMF 320 within a Non-Access Stratum (NAS) message used for the PDU session establishment procedure. Alternatively, UE 310 may send the PDU session establishment request to AMF 320 via a base station (not shown). The PDU session establishment request may include one or more Information Elements (IEs) within a NAS message. The PDU session establishment procedure can be used to establish a MAPDU session.

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

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

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

[0062] In step 6, SMF 330 can determine (e.g., identify, derive) ATSSS rules for UE 310. For example, SMF 330 can determine (e.g., identify, derive) ATSSS rules for UE 310 based on PCC rules. ATSSS rules can be provided (e.g., sent, output) to UE 310 for controlling traffic steering, handover, and partitioning of uplink communications (e.g., packets, PDUs). Additionally, SMF 330 can determine (e.g., identify, derive) N4 rules for UPF 350. For example, SMF 330 can determine (e.g., identify, derive) N4 rules for UPF 350 based on PCC rules. N4 rules can be provided (e.g., sent, output) to UPF 350 for controlling traffic steering, handover, and partitioning of downlink communications (e.g., packets, PDUs).

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

[0064] In step 8, the UPF 350 may send an N4 session response message to the 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, the UPF 350 may allocate (e.g., assign) 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 the SMF 330.

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

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

[0067] In step 11, a UDP stream is established between one or more of UE 310, AMF 320, SMF 330, PCF 340, and / or UPF 350. For example, uplink and downlink data are established for an MA PDU session, where UDP packets are transmitted between UE 310, AMF 320, SMF 330, PCF 340, and / or UPF 350. UE 310 may use ATSSS rules for the MPQUIC bootstrapping function and associated transport modes, which are identified by a context ID.

[0068] As described herein (and according to 3GPP TS24.501), if the transport mode is Datagram Mode 2, UE 310 may set the context ID to zero; otherwise, UE 310 uses a non-zero context ID (according to IETF RFC 9298). In this case, the context ID is an even value because UE 310 is considered a client. For sending UDP streams for the same SDF, UPF 350 may also use a non-zero odd value for the context ID (according to IETF RFC 9298) as a proxy.

[0069] Therefore, UE 310 or UPF 350 can treat any chosen value for the context ID as implicitly or previously registered for the transport mode. Furthermore, when a value for the context ID is registered, according to IETF RFC 9298, the same context ID can be used by UE 310 and UPF 350 for the same UDP stream (e.g., SDF), and it does not have to be an odd or even value because the transport mode is implicitly registered.

[0070] Furthermore, during the lifetime of a UDP stream used for a service / application (e.g., SDF), UE 310 and UPF 350 can use the same value for the context ID for different datagrams within that SDF. However, if a new and unknown value for the context ID (e.g., for a new datagram) is received for the UDP stream during its lifetime, UE 310 and UPF 350 can treat the unknown context ID (e.g., an unknown identifier for a datagram) as (e.g., an identifier) ​​registered for that UDP stream and process the datagram accordingly (e.g., buffer or receive the datagram).

[0071] Figure 4 An example of a UE 400 according to various aspects of this disclosure is shown. UE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).

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

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

[0074] Memory 404 may include volatile or non-volatile memory. Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 402, cause UE 400 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium such as 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 the transfer of computer programs from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0075] In some implementations, processor 402 and memory 404 coupled to processor 402 can be configured to cause UE 400 to perform one or more functions described herein (e.g., instructions stored in memory 404 are executed by processor 402). For example, according to the examples disclosed herein, processor 402 can support wireless communication at UE 400. UE 400 can be configured to support components for: establishing a PDU session with UPF for sending UDP streams for services or applications; receiving rules for bootstrapping, switching, and partitioning UDP streams across 3GPP access and non-3GPP access as a QUIC bootstrapping function with a transport mode, wherein the transport mode is a datagram mode for services or applications received from SMF; and using the QUIC bootstrapping function with a transport mode received from SMF as rules to send one or more datagrams for services or applications.

[0076] Controller 406 can manage input and output signals used by UE 400. Controller 406 can also manage peripheral devices not integrated into UE 400. In some implementations, controller 406 can utilize, for example... Or other operating systems. In some implementations, controller 406 may be implemented as part of processor 402.

[0077] In some implementations, UE 400 may include at least one transceiver 408. In other implementations, UE 400 may have more than one transceiver 408. Transceiver 408 may represent a wireless transceiver. Transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

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

[0079] Transmitter chain 412 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing it 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 similar digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). 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 a wireless medium. Transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0080] Figure 5 An example of a processor 500 according to various aspects of this disclosure is shown. Processor 500 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 500 may include a controller 502 configured to perform various operations according to the examples described herein. Processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. One or more of these components may be electronically communicateable or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0081] Processor 500 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 500) 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.).

[0082] Controller 502 can be configured to manage and coordinate various operations of processor 500 (e.g., sending, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 500 to support various operations according to the examples described herein. For example, controller 502 can operate as a control unit of processor 500, generating control signals that manage the operations 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.

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

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

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

[0086] One or more ALU 506s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 506s may reside within or on a processor chipset (e.g., processor 500). In some other implementations, one or more ALU 506s may reside outside the processor chipset (e.g., processor 500). One or more ALU 506s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 506s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 506s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 506s can support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 506s to handle conditional operations, comparisons, and bitwise operations.

[0087] Processor 500 may support wireless communication according to the examples disclosed herein. For example, processor 500 may be configured or operable to support components for: establishing a PDU session with the UPF for sending UDP streams for services or applications; receiving rules for bootstrapping, switching, and partitioning UDP streams across 3GPP access and non-3GPP access as a QUIC bootstrapping function with a transport mode, wherein the transport mode is a datagram mode for services or applications received from the SMF; and using the QUIC bootstrapping function with a transport mode received from the SMF as rules to send one or more datagrams for UDP streams for services or applications.

[0088] Figure 6 Examples of NE 600 according to various aspects of this disclosure are shown. NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, memory 604, controller 606, or transceiver 608, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).

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

[0090] Processor 602 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, ASICs, FPGAs, or any combination thereof). In some implementations, processor 602 may be configured to operate memory 604. In some other implementations, memory 604 may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory 604 to cause NE 600 to perform various functions of this disclosure.

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

[0092] In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured such that NE600 performs one or more functions described herein (e.g., instructions stored in memory 604 are executed by processor 602).

[0093] For example, processor 602 may support wireless communication at NE 600 according to the examples disclosed herein. NE 600 may be configured to support the following components: establishing a PDU session for the UE, wherein the PDU session includes a UDP stream for a service or application; receiving rules for a transport mode associated with the UDP stream; receiving datagrams including an unknown identifier and a payload; and processing the payload of the received datagrams according to the transport mode of the UDP stream. Operation of 708 may be performed according to the examples described herein. In some implementations, aspects of the operation of 708 may be provided by reference to [reference]. Figure 6 The NE described is used to execute.

[0094] Controller 606 can manage input and output signals used by NE 600. Controller 606 can also manage peripheral devices not integrated into NE 600. In some implementations, controller 606 may utilize, for example... Or other operating systems. In some implementations, controller 606 may be implemented as part of processor 602.

[0095] In some implementations, NE 600 may include at least one transceiver 608. In other implementations, NE 600 may have more than one transceiver 608. Transceiver 608 may represent a wireless transceiver. Transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

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

[0097] Transmitter chain 612 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing it 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 similar digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). 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 a wireless medium. Transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0098] Figure 7 A flowchart of a method according to various aspects of this disclosure is shown. The operation of this method can be implemented by the NE described herein. In some implementations, the NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0099] At 702, the method may include: establishing a PDU session for the UE, wherein the PDU session includes a UDP stream for a service or application. The operation at 702 can be performed according to the examples described herein. In some implementations, aspects of the operation at 702 may be derived from references... Figure 6 The NE described is used to execute.

[0100] At position 704, the method may include receiving a rule for the transport mode associated with the UDP stream. The operation of position 704 can be performed according to the examples described herein. In some implementations, aspects of the operation of position 704 may be derived from references... Figure 6 The NE described is used to execute.

[0101] At 706, the method may include receiving a datagram including an unknown identifier and a payload. The operation of 706 can be performed according to the examples described herein. In some implementations, aspects of the operation of 706 may be derived from references... Figure 6 The NE described is used to execute.

[0102] At 708, the method may include processing the payload of the received datagram according to the transport mode of the UDP stream. The operation at 708 can be performed according to the examples described herein. In some implementations, aspects of the operation at 708 may be derived from references... Figure 6 The NE described is used to execute.

[0103] It should be noted that the method described in this paper describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0104] Figure 8 A flowchart of a method according to various aspects of this disclosure is shown. The operation of this method can be implemented by a UE as described herein. In some implementations, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions.

[0105] At 802, the method may include: establishing a PDU session with the UPF for sending a UDP stream for a service or application. The operation of 802 can be performed according to the examples described herein. In some implementations, aspects of the operation of 802 can be found in the references. Figure 4 The described UE is used to execute.

[0106] At 804, the method may include: receiving rules for cross-3GPP access and non-3GPP access bootstrapping, handover, and UDP stream segmentation as a QUIC bootstrapping function with a transport mode, wherein the transport mode is a datagram mode received from the SMF for service or application. The operation of 804 can be performed according to the examples described herein. In some implementations, aspects of the operation of 804 may be provided by reference to [reference]. Figure 4 The described UE is used to execute.

[0107] At 806, the method may include: sending one or more datagrams for a service or application using a QUIC bootstrapping function having a transport mode received from the SMF as a rule. The operation of 806 can be performed according to examples as described herein. In some implementations, aspects of the operation of 806 may be provided by references... Figure 4 The described UE is used to execute.

[0108] It should be noted that the method described in this paper describes one possible implementation, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0109] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0110] Some additional examples will be provided:

[0111] Example 1. A network function for wireless communication includes: at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and configured such that the network function: establishes a PDU session for a UE, wherein the PDU session includes a UDP stream for a service or application, receives rules of a transmission mode associated with the UDP stream, receives datagrams including an unknown identifier and a payload, and processes the payload of the received datagrams according to the transmission mode of the UDP stream.

[0112] Example 2. Based on the network function in Example 1, the unknown identifier is an unknown context identifier that indicates the format of the payload.

[0113] Example 3. Based on the network function in Example 1, the PDU session is an MA PDU session.

[0114] Example 4. Based on the network function of Example 1, the UDP stream is a Service Data Stream (SDF) and is bootstrapped across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

[0115] Example 5. Based on the network function in Example 4, assign a context identifier for the transport mode associated with the QUIC bootstrap function that enables multipathing of UDP streams.

[0116] Example 6. Based on the network function in Example 1, the transmission mode is either datagram mode 1 or datagram mode 2.

[0117] Example 7. Based on the network function of Example 1, the network function is a user plane function (UPF), and at least one processor is configured to cause the UPF to receive rules of transport modes associated with the UDP stream from the session management function (SMF).

[0118] Example 8. According to the network function of Example 1, in order to process datagrams, at least one processor is configured to cause the UPF to receive datagrams.

[0119] Example 9. Based on the network function in Example 1, a datagram is a Hypertext Transfer Protocol (HTTP) datagram used as part of the format of a QUIC datagram frame.

[0120] Example 10. According to the network function of Example 1, at least one processor is further configured to enable the network function to: assign a context identifier to a datagram based on the transport mode, and receive additional datagrams for a UDP stream of a service or application, the additional datagrams having a context identifier different from the context identifier assigned to the datagram.

[0121] Example 11. A method performed by a network function, the method comprising: establishing a PDU session for a UE, wherein the PDU session includes a UDP stream for a service or application, receiving a rule of a transport mode associated with the UDP stream, receiving a datagram including an unknown identifier and a payload, and processing the payload of the received datagram according to the transport mode of the UDP stream.

[0122] Example 12. Following the method of Example 11, the unknown identifier is an unknown context identifier that indicates the format of the payload.

[0123] Example 13. Following the method of Example 11, the UDP stream is an SDF and is bootstrapped across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

[0124] Example 14. Following the method of Example 11, the datagram is an HTTP datagram that is used as part of the format of a QUIC datagram frame.

[0125] Example 15. The method according to Example 11 further includes: assigning a context identifier to a datagram based on the transport mode, and receiving other datagrams for a UDP stream used for a service or application, the other datagrams having a context identifier different from the context identifier assigned to the datagram.

[0126] Example 16. A UE for wireless communication, the UE comprising: at least one memory and at least one processor coupled to the at least one memory and configured such that the UE: establishes a PDU session with a UPF for transmitting a UDP stream for a service or application; receives rules for bootstrapping, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access as a QUIC bootstrapping function having a transport mode, wherein the transport mode is a datagram mode for the service or application received from an SMF; and uses the QUIC bootstrapping function having a transport mode received from an SMF as rules to transmit one or more datagrams of the UDP stream for the service or application.

[0127] Example 17. Following the method of Example 16, the PDU session is an MA PDU session in which traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

[0128] Example 18. According to the method of Example 16, one or more datagrams include an unknown context ID, and at least one of the processors is further configured such that the UE: processes the payload of one or more datagrams regardless of the unknown context ID.

[0129] Example 19. A processor for wireless communication, the processor comprising: at least one controller coupled to at least one memory and configured such that the processor: establishes a PDU session with a UPF for transmitting a UDP stream for a service or application; receives rules for bootstrapping, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access as a QUIC bootstrapping function having a transport mode, wherein the transport mode is a datagram mode for the service or application received from an SMF; and transmits the UDP stream for the service or application using the QUIC bootstrapping function having a transport mode received from the SMF as rules.

[0130] Example 20. According to the processor of Example 19, the PDU session is a multiple access (MA) PDU session, in which traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

Claims

1. A network function for wireless communication, configured as follows: Establish a Protocol Data Unit (PDU) session, the PDU session including a User Datagram Protocol (UDP) stream; Rules for receiving the transmission mode associated with the UDP stream; Receive datagrams including unknown identifiers and payloads; and The payload of the received datagram is processed according to the transmission mode of the UDP stream.

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

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

4. The network function of claim 1, wherein the UDP stream is a Service Data Stream (SDF) and is bootstrapping as a multipath-enabled QUIC bootstrapping function across 3GPP access and non-3GPP access.

5. The network function of claim 4, wherein a context identifier is assigned for the transport mode associated with the multipath-enabled QUIC bootstrapping function of the UDP stream.

6. The network function according to claim 1, wherein the transmission mode is datagram mode 1 or datagram mode 2.

7. The network function of claim 1, wherein the network function is a user plane function (UPF) configured to receive, from a session management function (SMF) the rules of the transport mode associated with the UDP stream.

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

9. The network function according to claim 1 is further configured as follows: Based on the transmission mode, a context identifier is assigned to the datagram; and Receive other datagrams from the UDP stream, the other datagrams having a context identifier different from the context identifier assigned to the datagram.

10. A method performed by a network function, the method comprising: Establish a Protocol Data Unit (PDU) session, the PDU session including a User Datagram Protocol (UDP) stream; Rules for receiving the transmission mode associated with the UDP stream; Receive datagrams that include unknown identifiers and payloads; as well as The payload of the received datagram is processed according to the transmission mode of the UDP stream.

11. The method of claim 10, wherein the unknown identifier is an unknown context identifier indicating the format of the payload.

12. The method of claim 10, wherein the UDP stream is a Service Data Stream (SDF) and is bootstrapping as a multipath-enabled QUIC bootstrapping function across 3GPP access and non-3GPP access.

13. The method of claim 10, wherein the datagram is a Hypertext Transfer Protocol (HTTP) datagram used as part of the format of a QUIC datagram frame.

14. The method of claim 10, further comprising: Based on the transmission mode, a context identifier is assigned to the datagram; as well as Receive other datagrams from the UDP stream, the other datagrams having a context identifier different from the context identifier assigned to the datagram.

15. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the UE: Establish a Packet Data Unit (PDU) session with the User Plane Function (UPF) for sending User Datagram Protocol (UDP) streams; The rules for receiving, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access are used as a QUIC boot function with a transport mode, wherein the transport mode is datagram mode. as well as Use the QUIC bootstrap function with the aforementioned transport mode to send one or more datagrams of the UDP stream.

16. The UE of claim 15, wherein the PDU session is a multiple access (MA) PDU session, wherein traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC guidance function.

17. The UE of claim 15, wherein the one or more datagrams include an unknown context identifier, and wherein the at least one processor is further configured to cause the UE to: Process the payload of the one or more datagrams regardless of the unknown context identifier.

18. A method for wireless communication by a user equipment (UE), the method comprising: Establish a Packet Data Unit (PDU) session with the User Plane Function (UPF) for sending User Datagram Protocol (UDP) streams; The rules for receiving, switching, and partitioning the UDP stream across 3GPP access and non-3GPP access are used as a QUIC boot function with a transport mode, wherein the transport mode is datagram mode. as well as Use the QUIC bootstrap function with the aforementioned transport mode to send one or more datagrams of the UDP stream.

19. The method of claim 18, wherein the PDU session is a multiple access (MA) PDU session, wherein traffic is guided across 3GPP access and non-3GPP access as a multipath-enabled QUIC bootstrapping function.

20. The method of claim 18, wherein the one or more datagrams include an unknown context identifier, and the method further comprises: Process the payload of the one or more datagrams regardless of the unknown context identifier.

Images